The distribution I eventually installed was BunsenLabs Linux version Helium / i386, and it's running nicely. The other user with the problem also said he had set this to "Start" when the issue happened. I suspect that the alleged block corruption error message happens when this option is set to "Start". In BIOS, set option "OS Installation" to "Finished". Because only after that, the card reader will appear in the selection list of possible boot devices when changing the boot order. For that, you first have to configure it in BIOS as the first mass storage device, and the internal mass storage device as the second one. In BIOS, set up the SD card reader as the first boot device. Indeed I was able to successfully boot from the internal SD card reader after the following steps: So I thought, these cannot be real block defects on my SD card then, it must be something else. I found the exact same sector and block numbers reported elsewhere, where another user has the same issue of installing on the Asus Eee PC 4G (701). buffer I/O error on device sdc, logical block 496254
end_request : I/O error, dev sdc, sector 3970032 There, I would see something like: sd 2:0:0:0: timing out command, waited 180s Symptoms include: when you press Esc while the "Ubuntu text with dotted progress bar" is displayed, you get to the text-mode boot log. I had the very same issue as the OP, while trying to install Lubuntu 18.04 LTS. Is Ubuntu 10.10 compatible with my Eee PC at all? How to boot it correctly?
Selecting either of these commands leading to the same result - after some background work the main loading indicator is displayed ("Ubuntu" text with dotted progress bar under it), and it's progressing forever without any effect.
I've got an old Eee PC 701 4G with the following specifications:
0 kommentar(er)
