Trouble booting from SD card with latest kernels
1 Attachment(s)
I have an eeepc (dual atom cpu running in 32-bit) that I am booting from an SD card with slackware current on it. When booting with one of the 5.17 kernels, the boot hangs for a few minutes before continuing to the prompt. The 5.15 and older kernels do not show this behaviour at all. I'm using the huge kernels and initrd images to boot from. I wasn't able to upload the dmesg file from the computer, so I'm including a URL to the file here: http://komary.net/dmesg. The problem appears to be with udevd timing out while handling devices.
The system seems to be working normally when it gets to the end of the boot. So, this is more of an annoyance than a serious problem. However, I would like to get it booting normally again rather than waiting five minutes for it to become usable. Does anyone have any idea of what may be wrong? I can provide more info if desired. Edit: I am attaching the dmesg file to this post for those who do not wish to follow the URL to the external server. |
Quote:
Where "file" could be anything ... or anywhere.. |
If it is a very common excuse, then maybe the site should improve its uploading code. I tried to upload multiple times, but no useful information is returned when the upload fails to help one succeed on the next attempt. The dmesg file is 740 lines long, which I thought was too long to paste into a post here. Do you have any actual advice on how this should have been done rather than making snide comments?
|
SDCards are error prone. I would download the kernel to disk and diff them, or check md5sums.
|
Quote:
If you use your own host, there's nothing stopping you from: 1.1 harvesting peoples IP addresses. 1.2 changing the content to something malicious once the mods have checked the file. 1.3 serving ads, which is against the rules on LQ. 1.4 posting whatever content that is agains the LQ rules. Regarding attachment and code: 2.1 If you're unable to attach, then ask why you're unable to attach. 2.2 If you're unable to use code tags because of length, use multiple code tags. Yet, you ignore all this and opt to serve us a link which may be OK now and may not be OK 24H from now. So excuse me for making a remark, but you ask for a lot of trust here man. Like you deliver a package, and inside there's a note saying "your package is buried 5 blocks away".. |
Maybe a built-in driver in the huge kernel in use is not the best for your ETPS/2 Elantech Touchpad, or something like that. To make sure I would try a generic kernel + initrd instead.
|
Quote:
I suspect that this is due to a change in what is required in the initrd tree compared to previous versions of the kernel, but I don't know that for sure. Maybe I need to include modules for the problematic hardware in the initrd, perhaps because the huge kernel no longer includes the drivers? It's hard to know if this is because kernel 5.17 changed somehow, or if kernel-huge-smp is configured differently. |
Quote:
|
When I try to upload the dmesg file, I get the following error message: "dmesg: Invalid file". Previously, I tried gzipping it and uploading that, but that also failed in the same way. I'm running the firefox browser that comes with slackware-current. Any suggestions as to why I cannot upload the file successfully?
|
Quote:
|
No issue here. Anyway you can get it just typing: wget http://komary.net/dmesg Forget it, I misunderstood your message #9
|
Quote:
Code:
dmesg >/tmp/dmesg.txt Code:
cp /var/log/messages /tmp/messages.txt |
Quote:
|
1 Attachment(s)
I installed the generic kernel and still got the udevd hangs during boot. Now that I know about the extension, I've successfully attached the dmesg file for this latest boot to this post.
|
It seems that the SD card be in a Alcor Micro Corp 636 Multi Flash Reader (hint: idVendor=058f, idProduct=6366). This is confirmed as an USB device is seen (/deb/sdb) instead of as SD card (/dev/mmcblk).
I would try to insert it directly in a SD port (if available and the PC can boot off an SD card directly), or use another USB adapter. I suggest that because an internet search with the argument "058f 6366 boot hangs" leads to several threads saying that this thingy works with some kernels but not others. |
All times are GMT -5. The time now is 08:24 AM. |