From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ken Ryan Date: Thu, 08 Jun 2006 18:37:44 +0000 Subject: SuSE 10.0 udev stuck with bogus name / rule entry Message-Id: <44886E78.3000801@leesburg-geeks.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org Hello. I'm trying to recover from a failed attempt at creating a udev rule. I'm running SuSE 10.0, pretty well up to date via YOU. At one point I tried to make world-access permissions for /dev/ttyS0 stick by writing a udev rule. I clearly did not do it correctly. Worse, I did not keep the rule as I wrote it. The problem now, though, is udev is incapable of sorting out non-static devices. This includes /dev/hda*, so the boot process crashes. I do have a laptop configured with 10.0, and I did some comparing of file contents. I have verified that the boot scripts, udev rules, and udev binaries are, at this instant in time, correct (they match the working system). My bogus changes are fully reverted. Now, when I run udevinfo -q all -p /sys/block/hda/hda1 (for example) all of the lines returned look fine EXCEPT the N: line. It says N: ttyS0 for all my hd* devices, loop devices, ram devices, etc. These also appear in the files in /dev/.udevdb - ALL of the files in there contain the above N: line instead of the proper line. The system fails some fscks, so drops me to single mode. If I then run "/etc/init.d/boot.udev force-reload" I get the proper entries created. When I shut down and restart, however, I'm back to square 1. So it seems that somewhere it is remembering something about my bogus ttyS0 rule and screqing up the detection process. I searched the /etc and /var trees for any mention of ttyS0; everywhere that comes up makes perfect sense for serial-port things. I would appreciate any suggestions on what to try or where else to look. BTW, none of my log files are getting updated. I presume it's because of those missing /dev entries. So I can't see any output from udevd there. I haven't yet gotten a serial console kicking, though since I don't see any abnormal messages on the boot screens I'm not sure it'll help (note I keep the boot splash turned off so I can see the boot messages; I've also booted into "failsafe" and normal modes with equivalent results). Thanks in advance! ken p.s. I'm not subscribed to the list but I'll check back on marc. I'd appreciate if responses are CCed to me though. _______________________________________________ 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