Bug#635840: TP-Link TL-WN821N v2 doesn't work with kernel 3.0
Hi, does the firmware source code link here http://linuxwireless.org/en/users/Drivers/carl9170.fw#Firmware_source_code to https://github.com/chunkeey/carl9170fw helps for building the firmware in to a debian package? Bye -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635840: TP-Link TL-WN821N v2 doesn't work with kernel 3.0
Hi
On Wednesday 31 August 2011, Ben Hutchings wrote:
On Fri, 2011-08-12 at 21:55 +0200, Stefan Lippers-Hollmann wrote:
On Friday 12 August 2011, Ben Hutchings wrote:
On Mon, 2011-08-01 at 19:36 -0300, Willian Gustavo Veiga wrote:
[...]
Given that the licensing for carl9170fw is a bit special[1] for a
firmware image targetted at a different architecture and not easy to
fulfill in a way that avoids wget on the buildds or code duplication,
I've started some preliminary packaging for it at:
Vcs-Svn: svn://svn.berlios.de/fullstory/firmware-carl9170/trunk
Vcs-Browser:
http://svn.berlios.de/svnroot/repos/fullstory/firmware-carl9170/trunk/
While this should meet upstream license conditions in wording and
spirit and may pass ftp-master checking, its strong dependencies
on packaging structures of binutils-source, newlib-source and the
versioned gcc-$(GCC_VER)-source make it rather fragile and high
maintenance, not to say downright ugly (looking at the list of
build-depends). This packaging compiles the sh-2 cross-compiling
environment at build-time, as introducing a newlib based sh-2
cross-compiling toolchain for this single package is hardly a preferred
option for Debian and binutils/ newlib/ gcc maintainers.
[...]
I suggest that you ask the FTP team whether they consider it necessary
for the package to be built in this way.
In case of carl9170fw, license compliance isn't the only reason that
made me building it and its toolchain from source. carl9170fw upstream
doesn't provide binary firmware images and neither release (source-)
tarballs for carl9170fw, the only distribution is through git tags on
git://git.kernel.org/pub/scm/linux/kernel/git/chr/carl9170fw.git
http://git.kernel.org/pub/scm/linux/kernel/git/chr/carl9170fw.git
https://git.kernel.org/pub/scm/linux/kernel/git/chr/carl9170fw.git
which means any packager will regularly have to build the firmware on
his own, in order to make it available for distribution. Binaries made
available from
http://wireless.kernel.org/en/users/Drivers/carl9170#Firmware-1
are rarely updated and often only from third parties (it's a wiki).
While using the upstream provided toolchain target works well (and is
much faster for subsequent builds, as the toochain won't have to get
rebuilt all the time), I chose this route of using
{binutils,newlib,gcc-4.6}-source in order to get carl9170fw into main,
instead of contrib.
firmware-free includes source code but does not actually use it at
package build time. It is rather taken on trust that the source code
can actually be built, though you have prompted me to actually check
this...
In case of carl9170fw, the upstream toolchain target works reliably and
is kept up to date with upstream toolchain changes, so maybe it would
qualify for the same treatment as shipped PDF files or similar
documentation, if it can be rebuilt, but isn't as part of the standard
buildsystem. However the git/source-only distribution for carl9170fw
didn't actually make me look into this.
Regards
Stefan Lippers-Hollmann
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635840: TP-Link TL-WN821N v2 doesn't work with kernel 3.0
On Fri, 2011-08-12 at 21:55 +0200, Stefan Lippers-Hollmann wrote: Hi On Friday 12 August 2011, Ben Hutchings wrote: On Mon, 2011-08-01 at 19:36 -0300, Willian Gustavo Veiga wrote: Ben, probably you're right. I've missed some information, sorry about that: # dmesg [ 312.484057] usb 1-5: new high speed USB device number 9 using ehci_hcd [ 312.664228] usb 1-5: New USB device found, idVendor=0cf3, idProduct=1002 [ 312.664233] usb 1-5: New USB device strings: Mfr=16, Product=32, SerialNumber=48 [ 312.664237] usb 1-5: Product: USB2.0 WLAN [ 312.664239] usb 1-5: Manufacturer: ATHER [ 312.664241] usb 1-5: SerialNumber: 12345 [ 312.780058] usb 1-5: reset high speed USB device number 9 using ehci_hcd [ 312.954434] usb 1-5: firmware not found. This driver requires the wireless controller to run different firmware, which must be installed as /lib/firmware/carl9170-1.fw. That file should be included in the firmware-free package, but it isn't yet. See http://linuxwireless.org/en/users/Drivers/carl9170#Firmware-1. Given that the licensing for carl9170fw is a bit special[1] for a firmware image targetted at a different architecture and not easy to fulfill in a way that avoids wget on the buildds or code duplication, I've started some preliminary packaging for it at: Vcs-Svn: svn://svn.berlios.de/fullstory/firmware-carl9170/trunk Vcs-Browser: http://svn.berlios.de/svnroot/repos/fullstory/firmware-carl9170/trunk/ While this should meet upstream license conditions in wording and spirit and may pass ftp-master checking, its strong dependencies on packaging structures of binutils-source, newlib-source and the versioned gcc-$(GCC_VER)-source make it rather fragile and high maintenance, not to say downright ugly (looking at the list of build-depends). This packaging compiles the sh-2 cross-compiling environment at build-time, as introducing a newlib based sh-2 cross-compiling toolchain for this single package is hardly a preferred option for Debian and binutils/ newlib/ gcc maintainers. [...] I suggest that you ask the FTP team whether they consider it necessary for the package to be built in this way. firmware-free includes source code but does not actually use it at package build time. It is rather taken on trust that the source code can actually be built, though you have prompted me to actually check this... Ben. signature.asc Description: This is a digitally signed message part
Bug#635840: TP-Link TL-WN821N v2 doesn't work with kernel 3.0
Hi
On Friday 12 August 2011, Ben Hutchings wrote:
On Mon, 2011-08-01 at 19:36 -0300, Willian Gustavo Veiga wrote:
Ben, probably you're right. I've missed some information, sorry about that:
# dmesg
[ 312.484057] usb 1-5: new high speed USB device number 9 using ehci_hcd
[ 312.664228] usb 1-5: New USB device found, idVendor=0cf3, idProduct=1002
[ 312.664233] usb 1-5: New USB device strings: Mfr=16, Product=32,
SerialNumber=48
[ 312.664237] usb 1-5: Product: USB2.0 WLAN
[ 312.664239] usb 1-5: Manufacturer: ATHER
[ 312.664241] usb 1-5: SerialNumber: 12345
[ 312.780058] usb 1-5: reset high speed USB device number 9 using ehci_hcd
[ 312.954434] usb 1-5: firmware not found.
This driver requires the wireless controller to run different firmware,
which must be installed as /lib/firmware/carl9170-1.fw. That file
should be included in the firmware-free package, but it isn't yet. See
http://linuxwireless.org/en/users/Drivers/carl9170#Firmware-1.
Given that the licensing for carl9170fw is a bit special[1] for a
firmware image targetted at a different architecture and not easy to
fulfill in a way that avoids wget on the buildds or code duplication,
I've started some preliminary packaging for it at:
Vcs-Svn: svn://svn.berlios.de/fullstory/firmware-carl9170/trunk
Vcs-Browser:
http://svn.berlios.de/svnroot/repos/fullstory/firmware-carl9170/trunk/
While this should meet upstream license conditions in wording and
spirit and may pass ftp-master checking, its strong dependencies
on packaging structures of binutils-source, newlib-source and the
versioned gcc-$(GCC_VER)-source make it rather fragile and high
maintenance, not to say downright ugly (looking at the list of
build-depends). This packaging compiles the sh-2 cross-compiling
environment at build-time, as introducing a newlib based sh-2
cross-compiling toolchain for this single package is hardly a preferred
option for Debian and binutils/ newlib/ gcc maintainers.
Please regard this as an initial attempt to solve this issue and feel
free to re-use this or parts of it at your convenience. While I'd
volunteer to co-maintain this (or derivatives of this packaging), it
still needs an active Debian uploader due to its rather high
maintenance requirements (adaptions to future {binutils,newlib}-source
versions or bumping the versioned build-requirements whenever old
gcc-$(GCC_VER)-source versions get removed from the archive).
Warning, system requirements for building this package are quite high:
- ~140 MB build-dependencies
- ~3.4 GB temporary build space
- a good half hour compilation time (mostly spent on the toolchain) on
fast computers, allowing parallel building through DEBBUILDOPTS helps
significantly.
+ build-tested on amd64 and kfreebsd-amd64, providing bit-identical
results
+ functionality confirmed with 0cf3:9170 Atheros Communications, Inc.
AR9170 802.11n on kernel 3.0.1.
Regards
Stefan Lippers-Hollmann
[1] GPL-2: The source code for a work means the preferred form of the
work for making modifications to it. For an executable work,
complete source code means all the source code for all modules
it contains, plus any associated interface definition files,
plus the scripts used to control compilation and installation
of the executable.
signature.asc
Description: This is a digitally signed message part.
Bug#635840: TP-Link TL-WN821N v2 doesn't work with kernel 3.0
On Thu, 2011-07-28 at 19:46 -0300, Willian Gustavo Veiga wrote: [...] dmesg doesn't give any useful information about how my device was registered. [...] You might think that, but I would like to see the log messages anwyay. Ben. signature.asc Description: This is a digitally signed message part
Bug#635840: TP-Link TL-WN821N v2 doesn't work with kernel 3.0
Ben, probably you're right. I've missed some information, sorry about that: # dmesg [ 312.484057] usb 1-5: new high speed USB device number 9 using ehci_hcd [ 312.664228] usb 1-5: New USB device found, idVendor=0cf3, idProduct=1002 [ 312.664233] usb 1-5: New USB device strings: Mfr=16, Product=32, SerialNumber=48 [ 312.664237] usb 1-5: Product: USB2.0 WLAN [ 312.664239] usb 1-5: Manufacturer: ATHER [ 312.664241] usb 1-5: SerialNumber: 12345 [ 312.780058] usb 1-5: reset high speed USB device number 9 using ehci_hcd [ 312.954434] usb 1-5: firmware not found. # tail -f /var/log/messages Aug 1 19:26:43 willian kernel: [ 288.333154] usb 1-3: USB disconnect, device number 3 Aug 1 19:27:07 willian kernel: [ 312.484057] usb 1-5: new high speed USB device number 9 using ehci_hcd Aug 1 19:27:07 willian kernel: [ 312.664228] usb 1-5: New USB device found, idVendor=0cf3, idProduct=1002 Aug 1 19:27:07 willian kernel: [ 312.664233] usb 1-5: New USB device strings: Mfr=16, Product=32, SerialNumber=48 Aug 1 19:27:07 willian kernel: [ 312.664237] usb 1-5: Product: USB2.0 WLAN Aug 1 19:27:07 willian kernel: [ 312.664239] usb 1-5: Manufacturer: ATHER Aug 1 19:27:07 willian kernel: [ 312.664241] usb 1-5: SerialNumber: 12345 Aug 1 19:27:07 willian kernel: [ 312.780058] usb 1-5: reset high speed USB device number 9 using ehci_hcd Aug 1 19:27:07 willian mtp-probe: checking bus 1, device 9: /sys/devices/pci:00/:00:03.3/usb1/1-5 Aug 1 19:27:08 willian mtp-probe: bus: 1, device: 9 was not an MTP device Thank you very much. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635840: TP-Link TL-WN821N v2 doesn't work with kernel 3.0
On Mon, 2011-08-01 at 19:36 -0300, Willian Gustavo Veiga wrote: Ben, probably you're right. I've missed some information, sorry about that: # dmesg [ 312.484057] usb 1-5: new high speed USB device number 9 using ehci_hcd [ 312.664228] usb 1-5: New USB device found, idVendor=0cf3, idProduct=1002 [ 312.664233] usb 1-5: New USB device strings: Mfr=16, Product=32, SerialNumber=48 [ 312.664237] usb 1-5: Product: USB2.0 WLAN [ 312.664239] usb 1-5: Manufacturer: ATHER [ 312.664241] usb 1-5: SerialNumber: 12345 [ 312.780058] usb 1-5: reset high speed USB device number 9 using ehci_hcd [ 312.954434] usb 1-5: firmware not found. This driver requires the wireless controller to run different firmware, which must be installed as /lib/firmware/carl9170-1.fw. That file should be included in the firmware-free package, but it isn't yet. See http://linuxwireless.org/en/users/Drivers/carl9170#Firmware-1. Ben. signature.asc Description: This is a digitally signed message part
Bug#635840: TP-Link TL-WN821N v2 doesn't work with kernel 3.0
Package: linux-2.6 Version: 3.0.0-1 Severity: normal Tags: sid I cannot raise up my wireless interface using kernel 3.0: # ifconfig wlan0 up wla0n: ERROR while getting interface flags: No such device With kernel 2.6.39 I'm able to run the same command and get a stable connection (using wpa_supplicant). I've used ar9170usb module but now it was removed and replaced by carl9170 (http://linuxwireless.org/en/users/Drivers/ar9170) # lsusb Bus 001 Device 003: ID 0cf3:1002 Atheros Communications, Inc. TP-Link TL-WN821N v2 [Atheros AR9001U-(2)NG] dmesg doesn't give any useful information about how my device was registered. Thank you and sorry about my english. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: OEM product_name: product_version: chassis_vendor: OEM chassis_version: bios_vendor: OEM bios_version: 1.09 board_vendor: OEM board_name: N/A board_version: N/A ** Network interface configuration: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback ** PCI devices: 00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 671MX [1039:0671] Subsystem: Elitegroup Computer Systems Device [1019:5050] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 32 Region 0: Memory at a000 (32-bit, non-prefetchable) [size=256M] Capabilities: access denied Kernel driver in use: agpgart-sis 00:01.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] SiS AGP Port (virtual PCI-to-PCI bridge) [1039:0003] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 16 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 9000-9fff Memory behind bridge: b000-b00f Prefetchable memory behind bridge: c000-cfff Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] SiS968 [MuTIOL Media IO] [1039:0968] (rev 01) Subsystem: Elitegroup Computer Systems Device [1019:5a00] Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 00:02.5 IDE interface [0101]: Silicon Integrated Systems [SiS] 5513 [IDE] [1039:5513] (rev 01) (prog-if 80 [Master]) Subsystem: Elitegroup Computer Systems Device [1019:5a00] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 128 Interrupt: pin ? routed to IRQ 16 Region 0: I/O ports at 01f0 [size=8] Region 1: I/O ports at 03f4 [size=1] Region 2: I/O ports at 0170 [size=8] Region 3: I/O ports at 0374 [size=1] Region 4: I/O ports at 1080 [size=16] Capabilities: access denied Kernel driver in use: pata_sis 00:03.0 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) (prog-if 10 [OHCI]) Subsystem: Elitegroup Computer Systems Device [1019:5a00] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32 (2ns max) Interrupt: pin A routed to IRQ 20 Region 0: Memory at b0104000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci_hcd 00:03.1 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) (prog-if 10 [OHCI]) Subsystem: Elitegroup Computer Systems Device [1019:5a00] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32 (2ns max)
