Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#2127 - latest udev (0.50-2) breaks many devices

Attached to Project: Arch Linux
Opened by Jan de Groot (JGC) - Wednesday, 02 February 2005, 23:23 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Critical
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


The latest udev package breaks many things:
- sound doesn't get registered anymore
- v4l devices don't get registered anymore
- printers don't get listed in /dev/lp/ anymore

Besides these, I think some other things might be broken too.
This task depends upon

Closed by  Jan de Groot (JGC)
Friday, 04 February 2005, 07:33 GMT
Reason for closing:  Fixed
Additional comments about closing:  Problem fixed in latest version
Comment by Judd Vinet (judd) - Wednesday, 02 February 2005, 23:26 GMT
Hmm, I don't have a printer or a v4l device on this machine. But my snd/ and sound/ devices are fine.

Can you elaborate or tell me how to reproduce?
Comment by Judd Vinet (judd) - Wednesday, 02 February 2005, 23:31 GMT
Here are the new rules added by tpowa. I don't see anything that would affect those devices.
Comment by hans (kryo) - Thursday, 03 February 2005, 01:20 GMT
I get a "/dev/pts busy or already mounted" message during "mounting filesystems" stage of bootup with udev 0.50-2.
Comment by Judd Vinet (judd) - Thursday, 03 February 2005, 01:28 GMT
That's harmless, i'll have it out of there by 050-3.

I've modified start_udev to try to umount pts and shm before it rebuilds all the device nodes, then re-mount them afterwards. This should save the additional step required when running start_udev manually:

# /etc/start_udev
# mount /dev/pts
# mount /dev/shm
Comment by Jan de Groot (JGC) - Thursday, 03 February 2005, 08:59 GMT
After downgrading to 0.50-1 and killing udevd and starting /sbin/udevstart, all devices registered correctly. Could it be something with the bootup scripts that doesn't work? The problem happened after rebooting, which hadn't been done after upgrading to 0.50-1, so the problem could be in that release too.

The problem persisted after every reboot with 0.50-2, haven't had time to check if 0.50-1 has the problem too.
Comment by Judd Vinet (judd) - Thursday, 03 February 2005, 21:02 GMT
050-3 is going up now. Please check if that one breaks as well.
Comment by John Reynolds (johnr) - Thursday, 03 February 2005, 22:28 GMT
I just upgraded to .50-3, seems to solve my problem.