LinuxQuestions.org - udev update question (from Current Changelog)

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - udev update question (from Current Changelog) (https://www.linuxquestions.org/questions/slackware-14/udev-update-question-from-current-changelog-343394/)

udev update question (from Current Changelog)

I was reading over the changelong for Current, and I'm a little confused by PV's comment for the latest udev update.

Quote:

a/udev-062-i486-1.tgz: Upgraded to udev-062.
This seems to be broken with regard to ALSA devices... I'd suggest
anyone using a 2.6 kernel "chmod 644 /etc/rc.d/rc.udev" unless you want
to help locate and report bugs. It's also possible that this has
something to do with the ever-changing syntax used in the udev.rules
config file. If you find any problems that can be attributed to that,
fixes would be appreciated. For now, rc.udev will be off by default.

My questions:
(1) I do use ALSA, so should I avoid this update?
(2) If this update turns rc.udev off, won't I be throwing out the baby with the bathwater if I apply this update?

Thanks for your help.

Re: udev update question (from Current Changelog)

Quote:

Originally posted by dhave
I was reading over the changelong for Current, and I'm a little confused by PV's comment for the latest udev update.
My questions:
(1) I do use ALSA, so should I avoid this update?
(2) If this update turns rc.udev off, won't I be throwing out the baby with the bathwater if I apply this update?

Thanks for your help.

1) Its preferable to use ALSA instead of OSS. If you need OSS then use the OSS emulation found in ALSA.

2) I'm not sure of this new update, but for me, udev 054 works well. So i'm personally not going to upgrade udev.

And on a side note, good work on pkgtool.. It is a bit faster now.

Thanks for your reply, xushi. I think I'll hold off on the udev update, too. I was curious, though, what effect it would have on ALSA, which I am using instead of OSS. If I have time next week I'll try to do some testing and see if that turns up anything useful. I've had one or two glitches with udev updates in the past, so I'm a little wary.

Like you, I'm also glad PV returned Jim Hawkin's optimized pkgtool script to Current. By your comment, I was afraid you thought I was one of its authors. I was just doing some unsolicited public relations for it by promoting it on this forum. I had seen how much it speeds things up and, also, I've used it for six months without any problems at all. I think it was Stuart Winter or Jim himself who contacted Pat about adding it back to Current.

I upgraded udev, and indeed it broke alsa.

I then followed PV's suggestion to chmod 644 rc.udev but then the system wouldn't boot, ending with a message saying something like
Failed to open /dev/hda8 (which is my root partition)
fsck.reiserfs for /dev/hda8 exited with signal 6

I downgraded udev to 054 and all is well again.

Does anyone have clue why fsck didn't work anymore?

And why come out with a newer version of udev if it's already known not to function?

Cheers, Leon.

hehe, sorry, i meant to say

And on a side note, good work has been done on pkgtool.. It is much faster now.
:D

Quote:

Originally posted by LJSBrokken
And why come out with a newer version of udev if it's already known not to function?

Because the current tree is for testing, not production. If you want to run current you should expect something like this from time to time. If you have problems, you should try and figure them out, fix them if possible, and report back to PV and company your results. This is how "stuff" goes from current to stable release.

This is also why I run stable (10.1) at the moment. I'm not saying that current is "unstable", it's just "untested". Most people run current with little or no problems, but every once in a blue moon something like this happens.

Later,
MMYoung

Yeah makes sense ;)
I guess -current is always so 'stable' that it caught me by surprise this time.

I do find it odd that he would put this in current when it's broken. I've been trying to build newer versions of udev ever since 55 and they all break alsa... :mad: Current has always been 'stable' to my knowledge and this move confuses me, especially when he knows that it's broken.... Hmmm... Oh well... I just figured alsa is standard with pretty much everyone and that was the whole reason he was waiting to upgrade; until he could get this ironed out...

udev really needs to get a sense of order to it. Seems like it's in constant flux and nothing has really stabilized...

Quote:

Originally posted by LJSBrokken
And why come out with a newer version of udev if it's already known not to function?

If you read Pat's log, you will know:
....... It's also possible that this has something to do with the ever-changing syntax used in the udev.rules config file. ...................

the syntax is not finalized.....

dare not to upgrade udev packages.

BTW, pkgtool is great now. noticeable performance up!

I keep forgetting that 2.4 is the kernel that comes with 10.1..... If we are running a 2.4 kernel then disabling udev really doesn't matter... :rolleyes: Thats why he put a 'broken' udev into current. It's not really broken. Not until 2.6.xx makes it into current.

On a side note, I found a fix for udev and mailed it off to Pat. So... It could be fixed soon.

I've also upgraded udev to 062 and ALSA didn't find the soundcard. After downgrading to 054, it works again well. So if you have troubles with ALSA, downgrading is very problably solution.

2_jong357: thnx for finding patch and moving it to Patric

Well, I don't think you'll find it anytime soon in current. I always run 2.6.xx... As a result, I tend to forget that 10.1 comes with 2.4 as I caught myself doing from above... My work around will break hotplug with 2.4 kernels as Pat pointed out in his reply email.... Thats why you won't see a fix in current. Atleast not mine... ;) So.... If you only run a 2.6.xx kernel, and are not worried about breaking hotplug with 2.4 all you need to do is call upon udevsend to handle hotplug events in the startup script. Put this line right above where udevstart is called.

Code:

echo /sbin/udevsend > /proc/sys/kernel/hotplug

It seems there will be a 10.2 "to put a finishing touch on the whole 2.4 kernel series".... Then 2.4.xx is getting kicked to the curb for 11.0... (I hope that wasn't a state secret or anything...)

Well, anyway.... The above addition to rc.udev works on a 2.6 kernel.... I'm running udev-063 right now with no changes to anything in his source directory except calling upon udevsend in rc.udev...

Quote:

Originally posted by jong357
It seems there will be a 10.2 "to put a finishing touch on the whole 2.4 kernel series".... Then 2.4.xx is getting kicked to the curb for 11.0... (I hope that wasn't a state secret or anything...)

Well, anyway.... The above addition to rc.udev works on a 2.6 kernel.... I'm running udev-063 right now with no changes to anything in his source directory except calling upon udevsend in rc.udev...

While udevsend can be used as a handler for hotplug events, it will hopefully not become the default, even when Slackware switches to 2.6, because many people want to keep udev out of the loop. It is certainly more elegant to run udevsend when hotplug events take place. E.g. via the to-be depracated /etc/hotplug.d.

Thanks a lot for the workaround, jong357. I'll probably use it, as I run only 2.6.x kernels.

One question, though: what's the downside of just not updating udev, at least for now? Are there significant new features in the post-54 releases of udev that make updating worthwhile?

Quote:

Originally posted by GlowGlow
While udevsend can be used as a handler for hotplug events, it will hopefully not become the default, even when Slackware switches to 2.6, because many people want to keep udev out of the loop. It is certainly more elegant to run udevsend when hotplug events take place. E.g. via the to-be depracated /etc/hotplug.d.

Do you think that "wanting to keep udev out of the loop" is more of a resistance to change type thing, or is it due to some type of hardware problem? I'm really interested to know, because for me, personally, udev it a much better way of handling /dev population than the old way of just pretty much putting something in /dev for every device known to man. Not saying it didn't work, as it work well, but udev is more "elegant", as you put it, IMHO.

Just wondering,
MMYoung

Quote:

Originally posted by dhave
One question, though: what's the downside of just not updating udev, at least for now? Are there significant new features in the post-54 releases of udev that make updating worthwhile?

I don't see any "downside" for not updating udev, other than the downside of your alsa devices actually working if you don't :D. Any other "significat features" would be made "moot" (to me anyway) if sound didn't work. However, there may be some enhancements that would be good for a sever, where sound (much less alsa) would be of less importance.

Later,
MMYoung

Well, too often people just upgrade to upgrade and don't know if they need to or not. I'm guilty of occassionally doing "Ooooo, Look! A new version of xyz" where xyz is some back water irrelevant package even.... I suppose udev is along those lines. 054 was working just fine. This post and the changelog made me curious tho... So, I had to try and upgrade for no good reason really... ;) The changelog is quite extensive, but as with most things, will probably only effect a few people....

Code:

Summary of changes from v062 to v063

============================================



Anton Farygin:

  fix typo in GROUP value application



Greg Kroah-Hartman:

  add 'make tests' as I'm always typing that one wrong...

  Really commit the udev_run_devd changes...

  Fixed udev_run_devd to run the /etc/dev.d/DEVNAME/ files too

  fix position of raw rules in gentoo config file



Hannes Reinecke:

  dasd_id: add s390 disk-label prober

  fix usb_id and let scsi_id ignore "illegal request"



Kay Sievers:

  volume_id: remove s390 dasd handling, it is dasd_id now

  trivial fixes for *_id programs

  IMPORT: add {parent} to import the persistent data of the parent device

  allow multiple values to be matched with KEY=="value1|value2"

  udevd: set incoming socket buffer SO_RCVBUF to maximum

  remember mapped rules state

  ata_id: check for empty serial number

  compile dasd only on s390



Ville Skyttä:

  correct default mode documentation in udev





Summary of changes from v061 to v062

============================================



Kay Sievers:

  fix symlink values separated by multiple spaces

  update RELEASE-NOTES

  fix typo in group assignment

  fix default-name handling and NAME="" rules

  add WAIT_FOR_SYSFS key to loop until a file in sysfs arrives

  fix unquoted strings in udevinitsend



Summary of changes from v060 to v061

============================================



Greg Kroah-Hartman:

  Sync up the Debian rules files

  fix cdrom symlink problem in gentoo rules

  Fix ChangeLog titles



Kay Sievers:

  update RELEASE-NOTES

  we want to provide OPTFLAGS

  rename ALARM_TIMEOUT to UDEV_ALARM_TIMEOUT

  udevd: optimize env-key parsing

  don't resolve OWNER, GROUP on precompile if string contains %, $

  set default device node to /dev

  create udevdb files only if somehting interesting happened

  pack parsed rules list

  replace useless defines by inline text

  move rule matches to function

  add usb_id program to generate usb-storage device identifiers

  add IEEE1394 rules to the gentoo rule file

  fake also kernel-name if we renamed a netif

  allow OPTIONS to be recognized for /sys/modules /sys/devices events

  switch gentoo rules to new operators





Summary of changes from v059 to v060

============================================



Greg Kroah-Hartman:

  Fix the gentoo udev rules to allow the box to boot properly



Gustavo Zacarias:

  Udev doesn't properly build with $CROSS



Kay Sievers:

  Keep udevstart from skipping devices without a 'dev' file



Marco d'Itri:

  #define NETLINK_KOBJECT_UEVENT





Summary of changes from v058 to v059

============================================



Greg Kroah-Hartman:

  Update the gentoo rule file

  Fix udevinfo for empty sysfs directories

  Fix makefile to allow 'make release' to work with git



Hannes Reinecke:

  udev: fix netdev RUN handling

  udevcontrol: fix exit code



Kay Sievers:

  prepare RELEASE-NOTES

  add ID_TYPE to the id probers

  add -x to scsi_id to export the queried values in env format

  store the imported device information in the udevdb

  rename udev_volume_id to vol_id and add --export option

  add ata_id to read serial numbers from ATA drives

  IMPORT allow to import program returned keys into the env

  unify execute_command() and execute_program()

  IMPORT=<file> allow to import a shell-var style config-file

  allow rules to be compiled to one binary file

  fix the fix and change the file to wait for to the "bus" link

  fix udevstart and let all events trvel trough udev

  prepare for module loading rules and add MODALIAS key

  remove device node, when type block/char has changed

  Makefile: remove dev.d/ hotplug.d/ from install target

  udevcontrol: add max_childs command

  udevd: control log-priority of the running daemon with udevcontrol

  udeveventrecorder: add small program that writes an event to disk

  klibc: add missing files

  udevinitsend: handle replay messages correctly

  udev man page: add operators

  udevd: allow starting of udevd with stopped exec-queue

  klibc: version 1.0.14

  udev: handle all events - not only class and block devices

  volume_id: use udev-provided log-level

  udev: clear lists if a new value is assigned

  udev: move dev.d/ handling to external helper

  udev: allow final assignments :=

  udevd: improve timeout handling

  Makefile: fix DESTDIR

  udevd: add initsend

  udevd: add udevcontrol

  udevd: listen for netlink events



Stefan Schweizer:

  Dialout group fix for capi devices in the gentoo rules file



Summary of changes from v057 to v058

============================================



Daniel Drake:

  o Writing udev rules docs update



Darren Salt:

  o update cdsymlinks to latest version



Greg Kroah-Hartman:

  o remove detach_state files from the sysfs test tree

  o Update permissions on test scripts so they will run properly now

  o hopefully fix up the symlinks in the test directory

  o Removed klibc/klibc.spec as it is autogenerated

  o Added symlinks thanks to Kay's script and git hacking

  o add Red Hat/Fedora html documenation

  o Update Red Hat default udev rules



Kay Sievers:

  o selinux: fix handling during creation of symlinks

  o Fedora udev.rules update

  o libsysfs: version 2.0

  o klibc: version 1.0.7



Masanao Igarashi:

  o Fix libsysfs issue with relying on the detach_state file to be



Summary of changes from v056 to v057

============================================



<tklauser:access.unizh.ch>:

  o fix stupid all_partitions bug



Kay Sievers:

  o add test for make -j4 to build-check

  o klibc: version 1.0.6

  o update Debian rules

  o apply default permissions only for devices that will need it

  o adapt RELEASE-NOTES

  o udev_volume_id: fix endianess macros

  o udev-test.pl: add test for DEVNAME export to RUN environment

  o update the man page to reflect the recent changes

  o export DEVNAME to RUN-key executed programs

  o fix make -j4 and the local klibc-install

  o update RELEASE-NOTES

  o add RUN key to be able to run rule based notification

  o fix udevtest to print the error if logging is disabled

  o move execute_program to utils + add action to init_device

  o correct correction for error path for PROGRAM execution

  o correct error path for PROGRAM execution

  o klibc: version 1.0.5

  o check for strlen()==0 before accessing strlen()-1

  o allow to match against empty key values

  o read %s{}-sysfs values at any device in the chain

  o udev_rules.c: don't change sysfs_device while walking up the device chain

  o klibc: strlcpy/strlcat - don't alter destination if size == 0

  o fix klibc's broken strlcpy/strlcat

  o udevinfo: print SYSFS attribute the same way we match it

  o remove untrusted chars read from sysfs-values or returned by PROGRAM

  o udevinfo: print errors to stderr instead of stdout

  o klibc: version 1.0.4

  o support log-priority levels in udev.conf

  o test-suite: remove UDEV_TEST, it's not needed anymore

  o libsysfs: remove trailing slash on SYSFS_PATH override





Summary of changes from v055 to v056

============================================



<tklauser:access.unizh.ch>:

  o fix header paths in udev_libc_wrapper.c



Kay Sievers:

  o udev-test.pl: use more common user/group names

  o klibc: remove SCCS directories from the temporary klibc install

  o udev-test.pl: add a test where the group cannot be found in /etc/passwd

  o udev-test.pl: add check for textual uid/gid

  o fix bad typo that prevents the GROUP to be applied

  o udevd: don't delay events with TIMEOUT in the environment

  o klibc: use klcc wrapper instead of our own Makefile

  o change call_foreach_file to return a list





Summary of changes from v054 to v055

============================================



<jkluebs:luebsphoto.com>:

  o This patch causes the remove handler to check that each symlink actually points to the correct devnode and skip it if it does not.



<pebenito:gentoo.org>:

  o udev selinux fix



<tklauser:access.unizh.ch>:

  o The following patch fixes some warnings when compiling volume_id from udev with the -Wall compiler flag. Define _GNU_SOURCE for strnlen() and correct the path to logging.h

  o The following patch fixes a warning when compiling chassis_id from udev with the -Wall compiler flag. There are too much conversions in the format string of sscanf(). One %d can be dropped.



Greg Kroah-Hartman:

  o fix raid rules

  o added frugalware udev ruleset

  o merge selinux and Kay's symlink fixes together



Hannes Reinecke:

  o volume_id: Fix label/uuid reading for reiserfs



Kay Sievers:

  o add udevstart to the RELEASE-NOTES

  o volume_id: version 43

  o clarify the shortcomings of %e

  o correct rule match for devices without a physical device

  o remove unneeded code, libsysfs does this for us

  o add final release note

  o add ENV{} key to match agains environment variables

  o simplify sysfs_pair handling

  o add a test and simplify debug statement

  o support =, ==, !=, += for the key match and assignment

  o add OPTION="last_rule" to skip any later rule

  o rename namedev_dev to udev_rule

  o correct enum device_type

  o remove udevstart on make clean

  o volume_id: version 42

  o volume_id: version 41

  o remove unneeded include

  o The path to dlist.h is not correct

  o udevinfo -d: use '=' as separator, cause ':' may be a part of the devpath

  o klibc: version 1.0.3

  o add RELEASE-NOTES file

  o test suite: move "driver" link to physical device

  o remove PLACE key match

  o don't lookup "root" in the userdb

  o fix ia64 compile

  o fix segfaulting udev while DRIVER matching

  o cleanup list.h

  o klibc: version 0.214

  o rename device_list->list to device_list->node

  o replace strncpy()/strncat() by strlcpy()/strlcat()

  o split udev and udevstart

  o udev_volume_id: version 39

  o rename LOG to USE_LOG in all places

  o remove Makefile magic for klibc integration

  o klibc_fixups: remove no longer needed stuff

  o udev_volume_id: volume_id v38

  o use numeric owner/group as default values to avoid parsing userdb

  o fix up segfaulting binaries with new klibc

  o udevinfo -d: speed-up device dump

  o klibc: version 0.211

  o klibc_fixups: remove unneeded stuff

  o replace weird defines by real code

  o udev-test.pl: remove useless tests

  o allow unlimitied count of symlinks

  o unmap db-file after use

  o remove typedef for call_foreach_file() handler function

  o correct udev_init_device

  o rename attributes to options

  o kill stupid gcc4 warning

  o trivial clenaup of namedev code

  o klibc: check for gcc4

  o klibc: update v0.205



Thierry Vignaud:

  o gentoo rule update for raid devices

Quote:

Originally posted by jong357
Well, too often people just upgrade to upgrade and don't know if they need to or not. I'm guilty of occassionally doing "Ooooo, Look! A new version of xyz" where xyz is some back water irrelevant package even....

Yep, that's my case, too. I usually try to heed PV's warnings, but sometimes I don't, or sometimes I don't fully understand. So, rather than holding off until I get full info, I usually forge ahead -- and then have to come here to get help cleaning up the mess afterward. But that's how you learn, right?

Quote:

I suppose udev is along those lines. 054 was working just fine. This post and the changelog made me curious tho... So, I had to try and upgrade for no good reason really... ;) The changelog is quite extensive, but as with most things, will probably only effect a few people....

Nothing really jumped off the page at me, but I haven't gone over it carefully enough. I'm sure in good time the kinks will be worked out. Meanwhile, on this one I can be patient. I think.

BTW, thanks for the reminder that Current isn't really a 2.6.x kernel config. That's very easy to forget.

Quote:

Originally posted by MMYoung
Do you think that "wanting to keep udev out of the loop" is more of a resistance to change type thing, or is it due to some type of hardware problem? I'm really interested to know, because for me, personally, udev it a much better way of handling /dev population than the old way of just pretty much putting something in /dev for every device known to man. Not saying it didn't work, as it work well, but udev is more "elegant", as you put it, IMHO.

Good question. For me personally, it deviates too much from the 'keep it simple stupid' paradigm. udev adds an unecessary layer of complexity. Besides that I do not feel that it is finished yet, e.g. the rule syntax changes every few weeks/months. But I can see that others find it comfortable, so I do not necessarily object to having it as a part of Slackware, but I would object to having it as a mandatory aspect of the system (and would write an e-mail to PV to argue for making it optional again).

I like udev but it gave me some problems when trying to use alsa as modules in my kernel. I got sound working simply by building it into the kernel. (monolithic) I'm really having problems with gstreamer though. I cant change tracks on cd's without gnome-cd freezing. Also when I change my multimedia prefs. to alsasink, the test button produces a very choppy test tone.

Quote:

Originally posted by GlowGlow
Good question. For me personally, it deviates too much from the 'keep it simple stupid' paradigm. udev adds an unecessary layer of complexity. Besides that I do not feel that it is finished yet

Right... He didn't come out and say it in his email, but I could tell that Pat felt the same way but ended with a "perhaps that's the way of the future" type of comment. I really don't think you'll see udev in the drivers seat in Slackware for quite some time. No worries... ;) If you've used Slack for any length of time and follow the changelog and various comments made by him, it's evident he doesn't jump the gun on anything.

Personally, I have no problem with using it. It's young, yes. Constantly changing, yes. It still works tho and thats good enough for me.

How do I tell my version of udev? I recently used slapt-get upgrade and am having some sound problems

Code:

udevinfo -V

I guess you guys have seen that Pat has switched to udev-058 in today's Current updates. This is his changelog entry:

Quote:

a/udev-058-i486-1.tgz: Switched to udev-058, as newer versions still have
problems (these are probably caused by the elimination of the
/etc/hotplug.d/ directory, as this used to contain a link to udevstart).
It was pointed out that udev-062 and udev-063 do create the missing
devices if you run udevstart after boot (and possibly after plugging in
new devices), but udev-058 is working fine without any kludges and seems
to be the most stable version to use with 2.6.12.* kernels. Also, made
a fix in /etc/udev/scripts/make_extra_nodes to set a default LANG before
calling /bin/ls to look for cdrom and dvd devices (not all LANG settings
will produce the same number of fields with ls, which can break cd/dvd
symlinks). Thanks to Lukasz Stelmach for pointing out this bug.

Quote:

Originally posted by dhave I guess you guys have seen that Pat has switched to udev-058 in today's Current updates.

Unfortunately, alsa doesn't like udev-058, either -- at least not on my system. I'm back with good old reliable udev-054.

FWIW, I'm running kernel 2.6.12.2 with alsa-driver-1.0.9b_2.6.12.2-i486-1.

Quote:

Originally posted by jong357
Right... He didn't come out and say it in his email, but I could tell that Pat felt the same way but ended with a "perhaps that's the way of the future" type of comment. I really don't think you'll see udev in the drivers seat in Slackware for quite some time. No worries... ;)

I do not worry about Patrick's choices. Rather the upstream depracation of hotplug.d and the new policy that udev should handle hotplug events. Then there is hotplug-ng, almost completely written in C, throwing away the flexibility of a scripted hotplug. I do not really like the upstream policy, an I am not exactly sure what they want to turn it in.

Quote:

If you've used Slack for any length of time and follow the changelog and various comments made by him, it's evident he doesn't jump the gun on anything.

I have used Slackware since 1994, so I have no worries about that :).

May I know where can I get udev-054-i486-3.tgz?

udev-58 does not work for my sound. But USB drive works fine
udev-62 works fine for my sound. But not for USB drive.

On udev-58, me get this error when execute alsamixer.

Code:

alsamixer: function snd_ctl_open failed for default: No such file or directory

Does this have anything to do with the "new" glibc?

Quote:

Originally posted by carboncopy
May I know where can I get udev-054-i486-3.tgz?

After a bit of Googling, I found it here:

http://linux.jetstreamgames.co.nz/sl...t/slackware/a/

You'd better hurry, though, because if this site gets updated, udev-54 will disappear.

Thankd dhave.

Sound is back BUT USB drive is gone.

How can I update the udev rule for the following device:

Code:

 Bus 001 Device 006: ID ffff:ffff  

Device Descriptor:

  bLength                18

  bDescriptorType        1

  bcdUSB              2.00

  bDeviceClass            0 (Defined at Interface level)

  bDeviceSubClass        0 

  bDeviceProtocol        0 

  bMaxPacketSize0        64

  idVendor          0xffff 

  idProduct          0xffff 

  bcdDevice            1.00

  iManufacturer          0 

  iProduct                1 USB Flash Drive

  iSerial                2 123456789ABCDEF

  bNumConfigurations      1

  Configuration Descriptor:

    bLength                9

    bDescriptorType        2

    wTotalLength          32

    bNumInterfaces          1

    bConfigurationValue    1

    iConfiguration          0 

    bmAttributes        0x80

    MaxPower              500mA

    Interface Descriptor:

      bLength                9

      bDescriptorType        4

      bInterfaceNumber        0

      bAlternateSetting      0

      bNumEndpoints          2

      bInterfaceClass        8 Mass Storage

      bInterfaceSubClass      6 SCSI

      bInterfaceProtocol    80 Bulk (Zip)

      iInterface              0 

      Endpoint Descriptor:

        bLength                7

        bDescriptorType        5

        bEndpointAddress    0x81  EP 1 IN

        bmAttributes            2

          Transfer Type            Bulk

          Synch Type              None

          Usage Type              Data

        wMaxPacketSize    0x0040  bytes 64 once

        bInterval              0

      Endpoint Descriptor:

        bLength                7

        bDescriptorType        5

        bEndpointAddress    0x02  EP 2 OUT

        bmAttributes            2

Here's the latest from Patrick regarding udev, from today's (22july05) changelog:

Quote:

a/udev-058-i486-2.tgz: Added a line to udev.rules to (hopefully) help
with the ALSA issues:
KERNEL="controlC[0-9]", NAME="snd/%k", MODE="0666"
Now, it would seem to me that the already-existing line:
KERNEL="controlC[0-9]*", NAME="snd/%k", MODE="0666"
...should have already covered this. It works with previous versions
of udev just fine, and this seems to me to be a udev bug. Oh well,
give it a test and let me know if it's still causing any problems, in
which case I'll probably go back to 054 for the Slackware 10.2 release.
I'd rather not spend the next couple of months dorking around with
udev problems and not getting a Slackware release out because of it.
Thanks to Andris Pavenis for the one line udev.rules fix.

My initial tests show that the fixed udev-058 listed in the 22july05 Current changelog plays nicely with alsa, at least on my system.

The fixed package name is udev-058-i486-2.tgz.

PV said in the changelog that he'd like to hear from people who are working on this problem, in hopes that the udev glitches can be taken care of more permanently.

Yep, it looks like udev-058-i486-2.tgz is working... I upgraded to it on my Armada laptop and all is well (so far).

...but, I'm keeping the 054 handy, just in case...