View previous topic :: View next topic |
Author |
Message |
g.tomassoni n00b

Joined: 13 Aug 2005 Posts: 51
|
Posted: Tue Nov 28, 2006 10:56 am Post subject: sys-fs/udev-103 |
|
|
Dears,
I have a couple of "stable" gentoo boxes which recently got to be upgraded to sys-fs/udev-103.
These boxes are connected to internet through two SpeedTouch ADSL USB modems, which were used to load their firmware thanks to sys-apps/coldplug-20040920-r1 and sys-apps/hotplug-20040923-r2 .
After reading some infos about this upgrade from the gentoo lists, I applied the upgrade by previously unmerging sys-apps/coldplug-20040920-r1 .
Suddenly, my boxes turned out not to be able to upload the SpeedTouch firmware.
An excerpt of the /var/log/messages from a staging box about this is the following:
Code: | Nov 28 11:15:47 grandfa usb 1-1: new full speed USB device using uhci_hcd and address 5
Nov 28 11:15:51 grandfa speedtch 1-1:1.0: speedtch_upload_firmware: read BLOCK4 from modem failed (-110)!
Nov 28 11:15:51 grandfa speedtch 1-1:1.0: speedtch_heavy_init: firmware upload failed (-110)! |
On the speedtch device driver list this kind of error is reported as being due to two programs both attempting to upload the firmware ad the same time.
After some tests, I found that both the new udevd AND an hotplug daemon were attempting to upload the firmware. I then attempted first stopping the hotplug daemon, but it didn't help (?!?!). Unmerging the sys-apps/hotplug package didn't helped, too.
I had to unmerge also sys-apps/hotplug-base-20040401, remove /etc/hotplug and /etc/hotplug.d, then issue a:
which basicly reinstalled both sys-apps/hotplug-base and sys-fs/udev-103.
Now udevd seems to be able to upload the firmware both at boot and at hot-plug time.
The only, annoing, thing left out is that now I get this message in /var/log/messages:
Code: | Nov 28 11:24:00 grandfa usb 1-1: new full speed USB device using uhci_hcd and address 8
Nov 28 11:24:01 grandfa udevd-event[21873]: run_program: exec of program '/sbin/firmware_helper' failed
Nov 28 11:24:02 grandfa udevd-event[21911]: run_program: exec of program '/sbin/firmware_helper' failed
|
I can't find any /sbin/firmware_helper piece of code and I'm pretty shure it is not needed at all, so I edited /etc/udev/rules.d/51-firmware.rules and placed a great, simple '#' in front of the line invoking the '/sbin/firmware_helper' script.
This seems to work, but I would like to know what the '/sbin/firmware_helper' tools is meant to. It seems to me that udev is pretty capable to deal with this stuff by itself, so what should this script/exe do and which is the package supplying it?
Thanks,
giampaolo |
|
Back to top |
|
 |
PaulBredbury Watchman


Joined: 14 Jul 2005 Posts: 7310
|
Posted: Tue Nov 28, 2006 11:02 am Post subject: |
|
|
Use my replacement ebuild for udev, which stops firmware.sh from messing up the loading of the SpeedTouch firmware. |
|
Back to top |
|
 |
g.tomassoni n00b

Joined: 13 Aug 2005 Posts: 51
|
Posted: Tue Nov 28, 2006 11:12 am Post subject: |
|
|
PaulBredbury wrote: | Use my replacement ebuild for udev, which stops firmware.sh from messing up the loading of the SpeedTouch firmware. |
It seems to me there is no need to twiddle the udev-103 stuff: firmware loading works reliably now.
And, by the way, my kernel uses CONFIG_USB_SPEEDTOUCH=m...
Do you have any counter-evidence? |
|
Back to top |
|
 |
PaulBredbury Watchman


Joined: 14 Jul 2005 Posts: 7310
|
Posted: Tue Nov 28, 2006 11:21 am Post subject: |
|
|
Yeah, my own experiences and those of others on that thread. My hair would not have as many grey hairs if I'd thrown my SpeedTouch modems out of the window when I first laid eyes on them
Anyway, read page 7 of the thread, especially my link to the race condition. Continue the discussion on that thread, rather than here. |
|
Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|