Bug 137263
| Summary: | Prism54 fails to upload firmware only on boot | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Neil Gierman <ngierman> | ||||||
| Component: | initscripts | Assignee: | Bill Nottingham <notting> | ||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 3 | CC: | hcamp, notting, rvokal | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i386 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | 7.93.5-1 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2004-11-04 05:45:59 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 130887 | ||||||||
| Attachments: |
|
||||||||
Created attachment 105821 [details]
dump of dmesg
dmesg dump _including_ removal and reinsertion of prism54 at the end.
a) where is your firmware file located b) can you attach your /var/log/messages instead? It will be somewhat more accurate than just dmesg FYI the location for firmwares changed to /lib/firmware... isn't that the bug, that hotplug is disabled in ifup?? comment from the mailing list:
Would you mind if I added a comment to your bug? I what I would as is
regarding the following snippet of
/etc/rc.d/init.d/network (lines 87-90)
oldhotplug=`sysctl kernel.hotplug 2>/dev/null | \
awk '{ print $3 }' 2>/dev/null`
sysctl -w kernel.hotplug="/bin/true" > /dev/null 2>&1
which is where hotplugging is specifically disabled, making the
loading of the firmware impossible.
That can be demonstrated by commenting out (#) the sysctl -w ... line
and rebooting.
Does using udev negate the comment #2 in the #113462 about
unilaterally "enabling" hotplug?
Also lines (182-186) from
/etc/sysconfig/network-scripts/network-functions in is_available()
HOTPLUG=`cat /proc/sys/kernel/hotplug`
echo "/etc/hotplug/firmware.agent" > /proc/sys/kernel/hotplug
modprobe $1 > /dev/null 2>&1 || {
echo "$HOTPLUG" > /proc/sys/kernel/hotplug
return 1
don't seem to help.
firmware is located in /lib/firmware. According to /etc/hotplug/firmware.agent, that is the correct place (it does load the firmware correctly at the end of the boot cycle, just not durring boot). /var/log/messages attached. Created attachment 105832 [details]
/var/log/messages
includes a few reboots.
Just upgraded to initscripts-7.93.2-1 that was added to yum last night and still same symptoms. Hm, I can't reproduce it on a prism54 card here; it does not load it on bootup, but that's because the device isn't automatically brought up. When the interface is opened, it loads fine. Will run some more tests. Oops, found it. Fixed in 7.93.5-1. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020 Firefox/0.10.1 Description of problem: Since upgrading from FC2 to FC3test3 my Netgear WG11 (Prism54) will not load automatically on boot. dmesg shows the failure was "failed to upload firmware". Simply rmmod'ing and modprobing prism54 after hotplug and pcmcia are up will load the firmware fine and the card is active (I have since added rmmod prism54;modprobe prism54 to my rc.local and "band-aid's the priblem). Another bug (113462) on RH9 was open but is now listed as closed with the resolution of Rawhide, and my comment about FC3test3 was refered to a bug in udev that was supposed to be fixed. As of 039-6, I still have the same symptoms. Others on fedora-test-list have commented about the same bug/symptom. Version-Release number of selected component (if applicable): udev-039-6 How reproducible: Always Steps to Reproduce: 1. Boot machine with prism54 card inserted 2. 3. Actual Results: lights on card are not active, dmesg shows failure uploading firmware, eth1 not a device Expected Results: green light on card solid, amber light flashing with activity, no errors in dmesg, eth1 up Additional info: dmesg dump attached