On Wed, 06 May 2015 11:40:56 -0500
Bruce Dubbs <[email protected]> wrote:

> Hazel Russman wrote:
> > Like several people on this list, I have been getting annoying messages at
> > boot time about nonexistent storage devices on empty usb ports. An earlier
> > post by Bruce Dubbs suggested a simple edit of
> > /lib/udev/rules.d/50-udev-default.rules to prevent this. On my LFS7.6 system
> > with systemd, this edit worked very well.
> >
> > However on LFS7.7 with sysvinit, it does not work. Not only do the messages
> > remain, but the change somehow screws up xorg's evdev driver so that neither
> > the mouse nor the keyboard work any more. This means that not only can I not
> > use X but I can't even get back to a console to correct the problem!
> >
> > At first I thought I might have made a typo during the edit, so I tried 
> > again
> > by copying the previously edited file from LFS7.6 (where it works perfectly
> > well) to LFS7.7. It turns out the effect is real, though it only shows up
> > after rebooting with the modified file; simply shutting down and restarting 
> > X
> > under the new rules doesn't cause problems.
> >
> > A diff run shows that the only difference between the old and the new files
> > is the position of the line ACTION!="add", GOTO="default_permissions_end".
> >
> > Can anyone explain this?
> 
> Does it work if you use the unmodified 50-udev-default.rules?
Yes. The file that comes with LFS works perfectly, except for the spurious 
warnings.
> The rules that are skipped by the change are:
> 
> 1. SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", \
>     IMPORT{builtin}="usb_id", \
>     IMPORT{builtin}="hwdb --subsystem=usb"
> 
> 2. SUBSYSTEM=="input", ENV{ID_INPUT}=="", \
>     IMPORT{builtin}="input_id"
> 
> 3. ENV{MODALIAS}!="", \
>     IMPORT{builtin}="hwdb --subsystem=$env{SUBSYSTEM}"
> 
> There are 4 IMPORT{builtin} commands there that the change skips, but only if 
> the action is not "add".  These just set variables that I'm pretty sure are 
> only 
> applicable to the current rule. Unless these rules have some sort of global 
> side 
> effect, I don't see how the change could cause your problem.
> 
>    -- Bruce
> -- 
> http://lists.linuxfromscratch.org/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
> 
> Do not top post on this list.
> 
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
> 
> http://en.wikipedia.org/wiki/Posting_style


-- 
Hazel Russman <[email protected]>
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style

Reply via email to