All comments:35Replies

  1. Chris4arm Member 2022-2-23 18:01:02

    mara Posted at 2022-2-23 17:01
    try the official ubuntu image

    It runs... a short time :
    it displays the Firefly splash screen one or 2 times and, once, it displayed the desktop then freezed. The other times black screen.
    How to check the integrity of the image ?

  2. mara Senior member 2022-2-23 18:09:11

    Chris4arm Posted at 2022-2-23 12:01
    It runs... a short time :
    it displays the Firefly splash screen one or 2 times and, once, it displ ...

    it is enough that it unzipped without errors

  3. Chris4arm Member 2022-2-23 22:41:28

    mara Posted at 2022-2-23 18:09
    it is enough that it unzipped without errors

    Ok, so I've done some more tests.

    Note : the "Ubuntu Desktop" partition is full (1.8G/1.9G)
    When the Desktop is displayed it freezes on the first mouse click ! Strange for an official image !
    So, on the last boot, I ignored the desktop and connect through ssh and, yes, bluetooth is there !
    But it's another useless image !
    My goal was to build an Armbian server (who don't crash)   to replace another (old) one without Bluetooth...

  4. mara Senior member 2022-2-23 23:21:16

    Chris4arm Posted at 2022-2-23 16:41
    Ok, so I've done some more tests.

    Note : the "Ubuntu Desktop" partition is full (1.8G/1.9G)

    when I get my sample back I'll try to see what and how, but my priorities are slarm64/crux-arm.

  5. Chris4arm Member 2022-2-23 23:33:56

    Chris4arm Posted at 2022-2-23 22:41
    Ok, so I've done some more tests.

    Note : the "Ubuntu Desktop" partition is full (1.8G/1.9G)

    Precisions about official Ubuntu image tests :
    I've found a lot of i/o errors about mmcblk0 :

    1. Feb 23 14:48:18 firefly kernel: mmc0: tried to reset card
    2. Feb 23 14:48:18 firefly kernel: mmcblk0: error -84 transferring data, sector 25432116, nr 44, cmd response 0x900, card status 0x0
    3. Feb 23 14:48:18 firefly kernel: blk_update_request: I/O error, dev mmcblk0, sector 25432125
    4. Feb 23 14:48:18 firefly kernel: blk_update_request: I/O error, dev mmcblk0, sector 25432128
    5. Feb 23 14:48:18 firefly kernel: blk_update_request: I/O error, dev mmcblk0, sector 25432136
    6. Feb 23 14:48:18 firefly kernel: blk_update_request: I/O error, dev mmcblk0, sector 25432144
    7. Feb 23 14:48:18 firefly kernel: blk_update_request: I/O error, dev mmcblk0, sector 25432152
    8. Feb 23 14:48:18 firefly kernel: EXT4-fs warning (device mmcblk0p8): ext4_end_bio:330: I/O error -5 writing to inode 109 (offset 0 size 28672 starting block 3179020)
    9. Feb 23 14:48:18 firefly kernel: buffer_io_error: 62 callbacks suppressed
    10. Feb 23 14:48:18 firefly kernel: Buffer I/O error on device mmcblk0p8, logical block 35845
    11. Feb 23 14:48:18 firefly kernel: Buffer I/O error on device mmcblk0p8, logical block 35846
    12. Feb 23 14:48:18 firefly kernel: Buffer I/O error on device mmcblk0p8, logical block 35847
    13. Feb 23 14:48:18 firefly kernel: Buffer I/O error on device mmcblk0p8, logical block 35848
    14. Feb 23 14:48:18 firefly kernel: Buffer I/O error on device mmcblk0p8, logical block 35849
    15. Feb 23 14:48:18 firefly kernel: Buffer I/O error on device mmcblk0p8, logical block 35850
    16. Feb 23 14:48:18 firefly kernel: Buffer I/O error on device mmcblk0p8, logical block 35851
    17. Feb 23 14:48:18 firefly kernel: mmcblk0: error -84 transferring data, sector 25468944, nr 8, cmd response 0x900, card status 0x0
    18. Feb 23 14:48:19 firefly kernel: blk_update_request: I/O error, dev mmcblk0, sector 25468951
    19. Feb 23 14:48:19 firefly kernel: EXT4-fs warning (device mmcblk0p8): ext4_end_bio:330: I/O error -5 writing to inode 83 (offset 4096 size 4096 starting block 3183619)
    20. Feb 23 14:48:19 firefly kernel: Buffer I/O error on device mmcblk0p8, logical block 40450
    21. Feb 23 14:48:19 firefly kernel: mmcblk0: error -84 transferring data, sector 25432160, nr 32, cmd response 0x900, card status 0x0
    22. Feb 23 14:48:20 firefly kernel: mmc0: tried to reset card
    23. Feb 23 14:48:20 firefly kernel: mmcblk0: error -84 transferring data, sector 25432162, nr 30, cmd response 0x900, card status 0x0
    24. Feb 23 14:48:20 firefly kernel: blk_update_request: I/O error, dev mmcblk0, sector 25432165
    25. Feb 23 14:48:20 firefly kernel: blk_update_request: I/O error, dev mmcblk0, sector 25432168
    26. Feb 23 14:48:20 firefly kernel: blk_update_request: I/O error, dev mmcblk0, sector 25432176
    27. Feb 23 14:48:20 firefly kernel: EXT4-fs warning (device mmcblk0p8): ext4_end_bio:330: I/O error -5 writing to inode 98 (offset 0 size 12288 starting block 3179023)
    28. Feb 23 14:48:20 firefly kernel: Buffer I/O error on device mmcblk0p8, logical block 35852
    29. Feb 23 14:48:20 firefly kernel: Buffer I/O error on device mmcblk0p8, logical block 35853
    30. Feb 23 14:48:20 firefly kernel: blk_update_request: I/O error, dev mmcblk0, sector 25432184
    31. Feb 23 14:48:20 firefly kernel: EXT4-fs warning (device mmcblk0p8): ext4_end_bio:330: I/O error -5 writing to inode 105 (offset 0 size 4096 starting block 3179024)
    32. Feb 23 14:48:21 firefly kernel: JBD2: Detected IO errors while flushing file data on mmcblk0p8-8
    33. Feb 23 14:48:42 firefly kernel: JBD2: Detected IO errors while flushing file data on mmcblk0p8-8
    34. Feb 23 14:50:30 firefly kernel: mmcblk0: error -84 transferring data, sector 25428016, nr 40, cmd response 0x900, card status 0x0
    35. Feb 23 14:50:31 firefly kernel: mmc0: tried to reset card
    36. Feb 23 14:50:31 firefly kernel: mmcblk0: error -84 transferring data, sector 25428034, nr 22, cmd response 0x900, card status 0x0
    37. Feb 23 14:50:31 firefly kernel: blk_update_request: I/O error, dev mmcblk0, sector 25428041
    38. Feb 23 14:50:31 firefly kernel: blk_update_request: I/O error, dev mmcblk0, sector 25428048
    39. Feb 23 14:50:31 firefly kernel: EXT4-fs warning (device mmcblk0p8): ext4_end_bio:330: I/O error -5 writing to inode 109 (offset 28672 size 16384 starting block 3178507)
    40. Feb 23 14:50:31 firefly kernel: buffer_io_error: 2 callbacks suppressed
    41. Feb 23 14:50:31 firefly kernel: Buffer I/O error on device mmcblk0p8, logical block 35335
    42. Feb 23 14:50:31 firefly kernel: Buffer I/O error on device mmcblk0p8, logical block 35336
    43. Feb 23 14:50:31 firefly kernel: Buffer I/O error on device mmcblk0p8, logical block 35337
    44. Feb 23 14:50:31 firefly kernel: Buffer I/O error on device mmcblk0p8, logical block 35338
    45. Feb 23 14:50:35 firefly kernel: JBD2: Detected IO errors while flushing file data on mmcblk0p8-8
    46. Feb 23 14:51:05 firefly kernel: JBD2: Detected IO errors while flushing file data on mmcblk0p8-8
    47. Feb 23 14:52:10 firefly kernel: mmcblk0: error -84 transferring data, sector 25432176, nr 8, cmd response 0x900, card status 0x0
    48. Feb 23 14:52:11 firefly kernel: mmc0: tried to reset card
    49. Feb 23 14:52:15 firefly kernel: JBD2: Detected IO errors while flushing file data on mmcblk0p8-8
    50. Feb 23 14:53:55 firefly kernel: JBD2: Detected IO errors while flushing file data on mmcblk0p8-8
    51. Feb 23 14:54:42 firefly kernel: mmcblk0: error -84 transferring data, sector 25432176, nr 8, cmd response 0x900, card status 0x0
    Copy the code


    I specify this SD card is a fresh Samsung EVO Plus UHS-I which is read and written without errors on my PC...

  6. mara Senior member 2022-2-27 08:25:00

    Chris4arm Posted at 2022-2-23 17:33
    Precisions about official Ubuntu image tests :
    I've found a lot of i/o errors about mmcblk0 :

    I fixed the boot with both the official bootloader and the transfer of the system to eMMC.

1234 Jump to Page

Reply

You need to log in before you can reply Login | Register