Problem boot with debian with duos 512mb

Duo
1 
I downloaded the image for debian (duos_sd.img.lz4) for duos 512mb but it is giving this problem when booting:

[ 1.231543] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 1.237686] Bluetooth: HIDP socket layer initialized
[ 1.243340] Loading compiled-in X.509 certificates
[ 1.280791] cviteka-adc sound_adc: cviteka_adc_probe, dev name=sound_adc
[ 1.287797] cviteka-adc sound_adc: cviteka_adc_probe start devm_snd_soc_register_card
[ 1.301182] cviteka-dac sound_dac: cviteka_dac_probe, dev name=sound_dac
[ 1.320715] mmc0: Problem setting drive strength!
[ 1.326428] ALSA device list:
[ 1.329857] dw-apb-uart 4140000.serial: forbid DMA for kernel console
[ 1.351780] Waiting for root device /dev/mmcblk0p2ā€¦
[ 1.432175] random: fast init done
[ 1.705113] mmc0: new ultra high speed DDR50 SDHC card at address aaaa
[ 1.712640] mmcblk0: mmc0:aaaa SS16G 14.8 GiB
[ 1.720339] mmcblk0: p1 p2
[ 1.725603] EXT4-fs (mmcblk0p2): couldnā€™t mount RDWR because of unsupported optional features (10000)
[ 1.735170] EXT4-fs (mmcblk0p2): couldnā€™t mount as ext3 due to feature incompatibilities
[ 1.744291] EXT4-fs (mmcblk0p2): couldnā€™t mount RDWR because of unsupported optional features (10000)
[ 1.753851] EXT4-fs (mmcblk0p2): couldnā€™t mount as ext2 due to feature incompatibilities
[ 1.762954] EXT4-fs (mmcblk0p2): couldnā€™t mount RDWR because of unsupported optional features (10000)
[ 1.781872] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
[ 1.789468] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
[ 2.259435] random: crng init done
[ 3.722511] mmc0: Problem setting drive strength!
[ 5.541792] blk_update_request: I/O error, dev mmcblk0, sector 205721 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[ 5.553059] Buffer I/O error on dev mmcblk0p2, logical block 115, lost async page write
[ 5.919484] blk_update_request: I/O error, dev mmcblk0, sector 206153 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
[ 5.930775] Buffer I/O error on dev mmcblk0p2, logical block 169, lost async page write
[ 5.939085] Buffer I/O error on dev mmcblk0p2, logical block 170, lost async page write
[ 6.302384] blk_update_request: I/O error, dev mmcblk0, sector 220497 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[ 6.313649] Buffer I/O error on dev mmcblk0p2, logical block 1962, lost async page write
[ 6.680691] blk_update_request: I/O error, dev mmcblk0, sector 221233 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0
[ 6.691954] Buffer I/O error on dev mmcblk0p2, logical block 2054, lost async page write
[ 6.700356] Buffer I/O error on dev mmcblk0p2, logical block 2055, lost async page write
[ 6.708775] JBD2: recovery failed
[ 6.712242] EXT4-fs (mmcblk0p2): error loading journal
[ 6.717967] VFS: Cannot open root device ā€œmmcblk0p2ā€ or unknown-block(179,2): error -5
[ 6.726186] Please append a correct ā€œroot=ā€ boot option; here are the available partitions:
[ 6.734843] b300 15558144 mmcblk0
[ 6.734848] driver: mmcblk
[ 6.741916] b301 102400 mmcblk0p1 00000000-01
[ 6.741920]
[ 6.748985] b302 815934 mmcblk0p2 00000000-02
[ 6.748988]
[ 6.756039] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
[ 6.764765] ā€”[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2) ]ā€”

1 Like
2

I guess you better try a different media and verify the integrity of the image you downloaded.

3 
I tried with 3 different cards, it even works perfectly with the original Milk Duos images
1 Like
4

Good. You got your suspect.

5 
I meant that with the original image on the milkv duos 512mb website it worked perfectly with buildroot, but the debian image here caused this error
6

Can you give us some more information?

e.g.

I assume you mean @Fishwaldo ā€˜s duos_sd.img.lz4 image .. is this correct? You have the switch set to RiscV? How did you copy the image to the card? Did you copy from a Windoze machine or a linux machine? etc. etc.

(I use @Fishwaldo ā€˜s image on my duos machines and they have worked for me - I copy images using dd on a linux machine)

1 Like
7

This is the culpit

[ 1.725603] EXT4-fs (mmcblk0p2): couldnā€™t mount RDWR because of unsupported optional features (10000)
[ 1.735170] EXT4-fs (mmcblk0p2): couldnā€™t mount as ext3 due to feature incompatibilities
[ 1.744291] EXT4-fs (mmcblk0p2): couldnā€™t mount RDWR because of unsupported optional features (10000)

This should be valid for RiscV or AArch64 ISA

The kernel tries to mound, but there are missing ext capabilities, which is odd.Maybe they are some bits flipped via download or transferto the sdcard. IIRC lz4 compression is not pretected by crc.

Please add link to you image and the sha1sum from your downloaded image

For me there some other thing (maybe unrelated) caught my eye

[ 1.320715] mmc0: Problem setting drive strength!

For this I must dig into downstream, upstream and into the TRM

1 Like
8

i used @Fishwaldo duos_sd.img.lz4 image and a I tried with 3 diferents cards an is the same error as above.

1 Like
9

i use this image: https://github.com/Fishwaldo/sophgo-sg200x-debian/releases/download/v1.4.0/duos_sd.img.lz4, and i used balena etcher for copy on sd card

1 Like
10

Hereā€™s what I dd to my cheap 64GB TF card (the .img one):

0196faf802a586b14bc7f9e257a299e6  v1.4_duos_sd.img
3a9728f3b46aec60eefde6f1a6e11cb7  v1.4_duos_sd.img.lz4

debian@duos:~$ uptime
17:17:55 up 6 min, 2 users, load average: 0.06, 0.17, 0.11

11 
How did you get the information for this sha key? i use this: 
sha1sum duos_sd.img
b58601b1c866f226ed46996c6c4a2062630e6d7f  duos_sd.img
1 Like
12

It was sha256sum, thatā€™s why it differs. And yes, the sha1sum matches. I used the very same image by the link above, so that we both confirm trying the same image.

Maybe you could try without balena-etcher? Iā€™m not an expert, but at least you can try something else.

13

Sometimes the card itself makes some ā€œhickupsā€, due the internal controller

I reconcomend to wipe the sd card, with linux this is easy

sudo dd if=/dev/zero of=/dev/your_sd_card bs=1M status=progress

1 Like
14

ok, I will try. but the interesting thing is that Iā€™ve already tried 3 different types of cards and if I use this image: Releases Ā· milkv-duo/duo-buildroot-sdk-v2 Ā· GitHub it works perfectly . even since debian is not working Iā€™m trying to compile duo-buildroot-sdk-v2, to add some packages e.g. wireguard etc. but still without success, itā€™s giving an error, but in this case Iā€™ll create another topic for this case

1 Like
15

Have you searched for the error message in this forum or there in the Issues section of V1/V2 projects on Github?