[Bug 546561] New: AVM Fritz!WLAN USB N not supported
http://bugzilla.novell.com/show_bug.cgi?id=546561 Summary: AVM Fritz!WLAN USB N not supported Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 8 Platform: x86 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: schaefer.frank@gmx.net QAContact: jsrain@novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-3.1 Firefox/3.5.3 The USB-WLAN-devices AVM Fritz!WLAN USB N (057c:8401) AVM Fritz!WLAN USB N 2.4 (057c:8402) are supported by the ar9170-driver included in the kernel since 2.6.31. openSUSE 11.2 M8 lacks support for these devices: 1.) firmware missing: 1-stage-firmware-file ar9170.fw is needed. It has been released under GPLv2. See http://linuxwireless.org/en/users/Drivers/ar9170.fw 2.) YaST doesn't detect / show the device and configuration is not possible These devices are the most popular/widespread WLAN-sticks here in Germany. Therefore support by openSUSE 11.2 is very desirable. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=546561
User aj@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c1
Andreas Jaeger
http://bugzilla.novell.com/show_bug.cgi?id=546561
User schaefer.frank@gmx.net added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c2
--- Comment #2 from Frank Schäfer
http://bugzilla.novell.com/show_bug.cgi?id=546561
User vbotka@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c3
Vladimir Botka
http://bugzilla.novell.com/show_bug.cgi?id=546561
User schaefer.frank@gmx.net added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c4
Frank Schäfer
http://bugzilla.novell.com/show_bug.cgi?id=546561
User vbotka@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c5
Vladimir Botka
@subject: submit-request #22443 state changed: new -> declined State of submit-request #22443 was changed by michal-m: new -> declined Comment: Please don't modify the upstream tarball, add the firmware as another source file instead.
This is clear.
Also the ar9170.fw file you added is some html page instead of the firmware.
I do not understand what you mean here. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=546561
User mmarek@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c6
Michal Marek
http://bugzilla.novell.com/show_bug.cgi?id=546561
User schaefer.frank@gmx.net added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c7
--- Comment #7 from Frank Schäfer
http://bugzilla.novell.com/show_bug.cgi?id=546561
User vbotka@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c8
Vladimir Botka
Latest firmware-package-version ar9170-firmware-1.1-3.1 works fine (still uses the wrong module-name in %post-script).
Could you be more specific in "the wrong module-name in %post-script". What is wrong ? Package ar9170-open-firmware (Project driver:wireless) is scheduled. If it works I will submit it to the Factory. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=546561
User schaefer.frank@gmx.net added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c9
Frank Schäfer
http://bugzilla.novell.com/show_bug.cgi?id=546561
User vbotka@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c10
Vladimir Botka
As I said, the module is called ar9170usb. %post-script modprobes for ar9170 which causes the mentioned errors: FATAL: Module ar9170 not found. BTW, package-description uses the wrong name, too.
Thank you. Both driver:wireless/ar9170-open-firmware and ar9170-firmware are updated. If it is ok now I will submit them to the Factory.
Concerning ifup/ifdown-configuration with YaST: the device needs to be added to the hwinfo-database, right ?
Let us ask the sysconfig maintainer. Marius, these USB-WLAN-devices [1] are using ar9170usb. Is any hwinfo-database update needed ? [1] AVM Fritz!WLAN USB N (057c:8401) AVM Fritz!WLAN USB N 2.4 (057c:8402) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=546561
User schaefer.frank@gmx.net added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c11
Frank Schäfer
Thank you. Both driver:wireless/ar9170-open-firmware and ar9170-firmware are updated. If it is ok now I will submit them to the Factory.
Works perfect now.
Let us ask the sysconfig maintainer. Marius, these USB-WLAN-devices [1] are using ar9170usb. Is any hwinfo-database update needed ?
Marius, could you please check the other devices covered by the ar9170-driver (see http://linuxwireless.org/en/users/Drivers/ar9170), too ? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=546561
Vladimir Botka
http://bugzilla.novell.com/show_bug.cgi?id=546561
User mt@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c12
Marius Tomaschewski
(In reply to comment #9)
As I said, the module is called ar9170usb. %post-script modprobes for ar9170 which causes the mentioned errors: FATAL: Module ar9170 not found. BTW, package-description uses the wrong name, too.
Thank you. Both driver:wireless/ar9170-open-firmware and ar9170-firmware are updated. If it is ok now I will submit them to the Factory.
Concerning ifup/ifdown-configuration with YaST: the device needs to be added to the hwinfo-database, right ?
Let us ask the sysconfig maintainer. Marius, these USB-WLAN-devices [1] are using ar9170usb. Is any hwinfo-database update needed ?
[1] AVM Fritz!WLAN USB N (057c:8401) AVM Fritz!WLAN USB N 2.4 (057c:8402)
All what sysconfig is using is the WIRELESS_WPA_DRIVER allowing to specify the wpa_supplicant driver and a static mapping in ifup-wireless when unset: test -n "$WIRELESS_WPA_DRIVER" && \ WPA_DRIVER="$WIRELESS_WPA_DRIVER" || \ case "${DRIVER}" in prism54) WPA_DRIVER=prism54 PREFER_WPA_SUPPLICANT=no ;; rt61|rt73) WPA_DRIVER=ralink ;; ipw2200|ipw2100|ipw3945|hostap_*) WPA_DRIVER=wext ;; ndiswrapper|*.sys) WPA_DRIVER=wext ;; rt2500usb|rt2500pci) WPA_DRIVER=wext ;; rt61pci|rt73usb|rt2400pci) WPA_DRIVER=wext ;; iwlagn|iwl3945|iwl4965) WPA_DRIVER=wext ;; zd1211rw) WPA_DRIVER=wext ;; ath5k|ath9k|ath_pci) WPA_DRIVER=wext ;; b43|b43legacy|ssb) WPA_DRIVER=wext ;; p54pci|p54usb) WPA_DRIVER=wext ;; at76*) WPA_DRIVER=wext ;; *) WPA_DRIVER=unsupported PREFER_WPA_SUPPLICANT=no ;; esac if need_wpa_supplicant ; then info_mesg "configuration requires wpa_supplicant" if [ "$WPA_DRIVER" = "unsupported" ]; then message "`printf " %-9s warning: WPA configured but may be unsupported" $INTERFACE`" message "`printf " %-9s warning: by this device" $INTERFACE`" info_mesg "using WPA driver 'wext' for interface $INTERFACE" WPA_DRIVER=wext fi start_wpa_supplicant elif [ "$PREFER_WPA_SUPPLICANT" = "yes" ]; then if applicable_wpa_supplicant ; then start_wpa_supplicant else info_mesg "setting up $INTERFACE w/o wpa_supplicant" old_setup fi else old_setup fi -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=546561
User mt@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c13
--- Comment #13 from Marius Tomaschewski
http://bugzilla.novell.com/show_bug.cgi?id=546561
User mt@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c14
Marius Tomaschewski
http://bugzilla.novell.com/show_bug.cgi?id=546561
User mt@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c15
--- Comment #15 from Marius Tomaschewski
test -n "$WIRELESS_WPA_DRIVER" && \ WPA_DRIVER="$WIRELESS_WPA_DRIVER" || \ case "${DRIVER}" in
^^^^^^^^^ BTW: The hardware driver name is from here: DRIVER="`( cd -P /sys/class/net/$INTERFACE/device/driver; echo ${PWD##*/}; )`" -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=546561
User mzugec@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c16
Michal Zugec
http://bugzilla.novell.com/show_bug.cgi?id=546561
User schaefer.frank@gmx.net added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c17
Frank Schäfer
http://bugzilla.novell.com/show_bug.cgi?id=546561
User schaefer.frank@gmx.net added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c18
--- Comment #18 from Frank Schäfer
http://bugzilla.novell.com/show_bug.cgi?id=546561
User vbotka@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c19
Vladimir Botka
Vladimir, should I add this mapping to ifup-wireless?
ar9170*) WPA_DRIVER=wext ;; or is here another wpa_supplicant driver required?
I do not have the HW. Frank, does wext work for you ? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=546561
Vladimir Botka
http://bugzilla.novell.com/show_bug.cgi?id=546561
User schaefer.frank@gmx.net added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c20
--- Comment #20 from Frank Schäfer
http://bugzilla.novell.com/show_bug.cgi?id=546561
Frank Schäfer
http://bugzilla.novell.com/show_bug.cgi?id=546561
User mt@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c21
Marius Tomaschewski
http://bugzilla.novell.com/show_bug.cgi?id=546561
User schaefer.frank@gmx.net added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c22
Frank Schäfer
http://bugzilla.novell.com/show_bug.cgi?id=546561
User mt@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c23
--- Comment #23 from Marius Tomaschewski
http://bugzilla.novell.com/show_bug.cgi?id=546561
User mt@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c24
Marius Tomaschewski
http://bugzilla.novell.com/show_bug.cgi?id=546561
User vbotka@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c25
Vladimir Botka
http://bugzilla.novell.com/show_bug.cgi?id=546561
User mt@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=546561#c26
--- Comment #26 from Marius Tomaschewski
[3] # osc ls driver:wireless ar9170-open-firmware
OK, thanks, it IMO makes no sense to request submission of the sysconfig patch to 11.2; it will stay in Base:System/sysconfig, except I'll get an explicit go from somewhere (Coolo). It is just about to skip the "may be unsupported" warning. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=546561
https://bugzilla.novell.com/show_bug.cgi?id=546561#c27
Uwe Drechsel
https://bugzilla.novell.com/show_bug.cgi?id=546561
https://bugzilla.novell.com/show_bug.cgi?id=546561#c28
--- Comment #28 from Uwe Drechsel
participants (1)
-
bugzilla_noreply@novell.com