Mark McCorkell wrote: > I switched back to the standard set of Debian modules for the time > being, as I don't have the time or experience (yet!) to resolve the > issue but I did find this rather long discussion > (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401916) indicating > that it's been an ongoing concern for quite a while. Maybe you can dig > around in there and find something useful. > > -- > Mark.
This somehow explains why I have written my own scripts to create initrd. Still with recent updates (after lenny=stable) I have problems with my tv card and the usb initialization of the port that it's connected to. I have to reboot so that it may work. I was thinking it's because udev but never find time to investigate. Curiously the debian own initrd is even working worse than my one, so may be I'll investigate further. I remember someone reported that he has to reboot to get his usb drive settled, because of power or somekind of other issue. So the question is if one should include the hole udev staff in initrd? thanks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
