* SOLVED: SuSE 10.0 udev stuck with bogus name / rule entry
@ 2006-06-13 3:05 Ken Ryan
0 siblings, 0 replies; only message in thread
From: Ken Ryan @ 2006-06-13 3:05 UTC (permalink / raw)
To: linux-hotplug
Kay Sievers wrote:
> On Fri, 2006-06-09 at 21:40 -0400, Ken Ryan wrote:
>> On Fri, 9 Jun 2006, Kay Sievers wrote:
>>> Try to run:
>>> udevtest /block/hda/hda1
>>>
>>> What does it print?
>
>> # udevinfo -q all -p /sys/block/hda/hda1
>> F: /block/hda/hda1
>> N: ttyS0 <------- Huh?
>
> That must be a broken rule.
>
>> # udevtest /block/hda/hda1 block
>> udev_rules_get_name: no node name set, will use kernel name 'hda1'
>
> The rules in the root filesystem seems to be ok.
>
> Try to run mkinitrd. You may still have the broken rules that create ttyS0
> for all devices in the initramfs image.
>
> Kay
Thank you! That did the trick! All looks like it's back in order!
I didn't realize udev rules got copied into initrd, but in retrospect
that makes sense (I dunno I guess it took a virgin copy from somewhere,
but of course there's no reason it should do that).
Thanks again!
ken
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2006-06-13 3:05 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-06-13 3:05 SOLVED: SuSE 10.0 udev stuck with bogus name / rule entry Ken Ryan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).