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.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

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.

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.

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!