Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

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!
Tasklist

FS#3509 - udev 71-2,3 affects ipw2200

Attached to Project: Arch Linux
Opened by jp fielding (jp_fielding) - Sunday, 20 November 2005, 13:05 GMT
Last edited by Judd Vinet (judd) - Wednesday, 23 November 2005, 18:51 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

udev 71-1 had no issues. since udev 71-2, it has caused issues with this driver, driver loads, but not the firmware i believe. this still holds with 71-3.

with ipw2200, my device usually comes up as eth1, but if i use the rules from 71-1 with 71-3, it does come up as eth0.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Thursday, 24 November 2005, 06:35 GMT
Reason for closing:  Fixed
Comment by Tobias Powalowski (tpowa) - Monday, 21 November 2005, 10:42 GMT
try new initscripts, that should solve the eth problem.
Comment by jp fielding (jp_fielding) - Monday, 21 November 2005, 13:31 GMT
updated this morning from 0.7.1-9 -> 0.7.1-10 of the initscripts, the eth1 as eth0 problem still exists. (along with the original problem udev loading)
Comment by Tobias Powalowski (tpowa) - Monday, 21 November 2005, 15:30 GMT
Could you check if commenting this at the end of udev.rules helps?

# FIRMWARE
ACTION=="add", SUBSYSTEM=="firmware", ENV{FIRMWARE}=="*", RUN+="/sbin/firmware_helper"

what is eth0 in your system, internal network card or what, just tell me the module of eth0, thanks
Comment by jp fielding (jp_fielding) - Monday, 21 November 2005, 15:36 GMT
yes, removing that line is what lets it work at all. if that line is in, nothing loads. that's what using the 0.7.1-9 bought me over 0.7.1-10. that line is the only (significant) between those rules files.
Comment by Judd Vinet (judd) - Wednesday, 23 November 2005, 18:51 GMT
Re-opened by jp_fielding:

sorry, forgot the part about including my ethernet module b44. i'm up to date in testing/current/extra and the module ordering
problem still exists. should i continue to report that here, or is that a separate issue? thanks, jp
Comment by Tobias Powalowski (tpowa) - Wednesday, 23 November 2005, 19:44 GMT
sorry i don't understand your problem?

b44 is not loaded or what is your problem?
or is ipw loaded before b44 or what?
please be more precise
Comment by jp fielding (jp_fielding) - Wednesday, 23 November 2005, 19:52 GMT
actually, sorry, i just realized that when i converted over to hwdetect, i didn't put b44 back into my modules array. so it was getting loaded, but only after ipw2200. your question jiggled my memory.

thanks,
jp
Comment by Tobias Powalowski (tpowa) - Wednesday, 23 November 2005, 19:58 GMT
well could you send me the output from
hwdetect --show-modules-order?
to see when hwdetect loads ipw thanks.
greetings
Comment by jp fielding (jp_fielding) - Wednesday, 23 November 2005, 21:28 GMT
sure thing:

MODULES ORDER: cdrom agpgart intel-agp hw_random rtc tpm tpm_atmel tpm_infineon tpm_nsc evdev pcspkr serio_raw pci_hotplug shpchp nvidia snd-mixer-oss snd-pcm-oss snd-page-alloc snd-timer snd snd-ac97-bus snd-ac97-codec snd-intel8x0 snd-intel8x0m soundcore ide-cd ide-core ide-disk generic piix b44 mii ieee80211 ieee80211_crypt ipw2200 pcmcia_core rsrc_nonstatic yenta_socket usbhid usbcore ehci-hcd uhci-hcd eth1394 ieee1394 ohci1394 sbp2

hmm. i was used to hotplug and (thinking i had to) loading ipw2200. i'm guessing the issue is actually the opposite. if i load them by hand, then i need to load them in the proper order. if i load ipw2200 by hand, and let hwdetect do the rest, ipw2200 gets loaded first. so either way.... it appears to be user error.

sorry,
jp
Comment by Tobias Powalowski (tpowa) - Thursday, 24 November 2005, 06:35 GMT
yes modules in MODULES are loaded before hwdetect takes action, so please keep that in mind :)
good to see that now everything works.
greetings
tpowa

Loading...