SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
During boot I experience a long (~15 seconds) delay usually immediately after i915 drm is initialized, everything seems to just freeze. After the delay I get the following messages, then it continues to boot normally.
On first boot I thought it was associated with the display driver but now I think it is the wireless device and the timing is just coincidental. I expect it needs a module or udev rule to get past it, but I am not udev guru enough to know what to do with it.
On first boot I thought it was associated with the display driver but now I think it is the wireless device [...]
The udevd message seems to confirm the issue was with your wireless device (pci 05:04.0 is the wifi card according to the lspci fragment you provided).
I have the same issue here. Also with the wifi controller, although this is a Broadcom BCM43225 (driver is brcmsmac).
It has been reported several times here in previous threads. IIRC, it can be avoided by hand-loading the kernel module before udevd tries to do it.
For the moment I just reverted to udev-165 (from 13.37) which works fine on my PC
Another workaround is to create initrd with that particular module. Udev will throw few warnings/errors, but as far as I tried, they are harmless. At least it works for my ipw2200 wireless module.
Don't know why, but adding the brcmsmac didn't solved mine when I tried before. The module wouldn't load automatically and I had to add it manually if I had it on initrd.
The udev problem in my case seems to be with CRDA, but this is just a guess...
...
It has been reported several times here in previous threads.
...
Quote:
Originally Posted by astrogeek
...
I was hoping to understand the "why" a little better, but no time today.
...
Have no time? Searching this forum takes few minutes.
If someone else finds the same problem and step into this thread, just believe philanc and do a search to find detailes in this forum about cause and cure.
Have no time? Searching this forum takes few minutes.
If someone else finds the same problem and step into this thread, just believe philanc and do a search to find detailes in this forum about cause and cure.
Actually, I had done more than a cursory look in these forums, and found several threads for both the i915 driver and the wireless, but nothing that I found really helpful to understanding the ipw2200 problem. I had thought that I would add the module to the initrd on next boot, but was looking for a better understanding of it more than a quick fix. In the end, I have a quick fix but still lack any good understanding of why it fails with udev.
It might well be due to my own slow rate of understanding the obvious, but I did not find a useful cause/cure for it here.
I was hoping to understand the "why" a little better, but no time today. Anyone know of a good, useful overview of udev and the rules files?
Due to changes in udev, some modules that needs to load firmware just timeout now. See http://www.spinics.net/lists/linux-w.../msg83448.html. We either need to revert udev back to old behaviour or patch ipw2200 and other similar acting modules for new udev.
Due to changes in udev, some modules that needs to load firmware just timeout now. See http://www.spinics.net/lists/linux-w.../msg83448.html. We either need to revert udev back to old behaviour or patch ipw2200 and other similar acting modules for new udev.
Now THAT looks helpful! I'll digest it later today!
Then, the extent of my previous udev knowledge was mostly gained from ordering my net and USB device names - sketchy at best. In looking into this I read the ArchWiki article here https://wiki.archlinux.org/index.php/Udev which has all the answers, including the vagaries of rules files and blacklisting - read it!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.