Commit 782e70c6fc2290a0395850e8e02583b8b62264d8, which went into
2.6.25, broke AVM's closed-source driver for this device:
ID 057c:62ff AVM GmbH WLAN USB v1.1 (cdrom mode)
ID 057c:6201 AVM GmbH WLAN USB v1.1
Is there an open source alternative for that driver, or do systems
with that device have to stay with kernel 2.6.24?
Thanks,
Tilman
--
Tilman Schmidt E-Mail: [email protected]
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Unge?ffnet mindestens haltbar bis: (siehe R?ckseite)
On Thu, Jul 31, 2008 at 04:52:41PM +0200, Tilman Schmidt wrote:
> Commit 782e70c6fc2290a0395850e8e02583b8b62264d8, which went into
> 2.6.25, broke AVM's closed-source driver for this device:
>
> ID 057c:62ff AVM GmbH WLAN USB v1.1 (cdrom mode)
> ID 057c:6201 AVM GmbH WLAN USB v1.1
>
> Is there an open source alternative for that driver, or do systems
> with that device have to stay with kernel 2.6.24?
Please ask AVM, they have known about this for over 2 years now.
There is nothing we can do about closed source kernel modules, that is
between you and the company producing it.
good luck,
greg k-h
On Thu, 2008-07-31 at 16:52 +0200, Tilman Schmidt wrote:
> Commit 782e70c6fc2290a0395850e8e02583b8b62264d8, which went into
> 2.6.25, broke AVM's closed-source driver for this device:
>
> ID 057c:62ff AVM GmbH WLAN USB v1.1 (cdrom mode)
> ID 057c:6201 AVM GmbH WLAN USB v1.1
>
> Is there an open source alternative for that driver, or do systems
> with that device have to stay with kernel 2.6.24?
Never heard of any such driver, what chip does it contain?
johannes
On Thu, Jul 31, 2008 at 06:34:04PM +0200, Tilman Schmidt wrote:
> Johannes Berg schrieb:
>> On Thu, 2008-07-31 at 16:52 +0200, Tilman Schmidt wrote:
>>> Commit 782e70c6fc2290a0395850e8e02583b8b62264d8, which went into
>>> 2.6.25, broke AVM's closed-source driver for this device:
>>>
>>> ID 057c:62ff AVM GmbH WLAN USB v1.1 (cdrom mode)
>>> ID 057c:6201 AVM GmbH WLAN USB v1.1
>>>
>>> Is there an open source alternative for that driver, or do systems
>>> with that device have to stay with kernel 2.6.24?
>>
>> Never heard of any such driver, what chip does it contain?
>
> I don't know. How can I find out?
> (Preferably without cracking the thing open. ;-)
>
> http://acx100.sourceforge.net/matrix.html claims "Chipset TNETW1450"
> and "support should be quite easy" - but that entry is two years old
> and the "Model" link doesn't work, so I'm not sure how far that can
> be trusted.
Did the acx100 driver work with your card?
John
--
John W. Linville
[email protected]
On Thu, Jul 31, 2008 at 11:34:26PM +0200, Tilman Schmidt wrote:
> On Thu, 31 Jul 2008 09:38:43 -0700, Greg KH wrote:
> > On Thu, Jul 31, 2008 at 04:52:41PM +0200, Tilman Schmidt wrote:
> >> Commit 782e70c6fc2290a0395850e8e02583b8b62264d8, which went into
> >> 2.6.25, broke AVM's closed-source driver for this device:
> >>
> >> ID 057c:62ff AVM GmbH WLAN USB v1.1 (cdrom mode)
> >> ID 057c:6201 AVM GmbH WLAN USB v1.1
> >>
> >> Is there an open source alternative for that driver, or do systems
> >> with that device have to stay with kernel 2.6.24?
> >
> > Please ask AVM, they have known about this for over 2 years now.
>
> Please let's keep the politics out of this. I know who wrote that
> patch, I know the agenda behind it and the discussion accompanying it.
> Conversely, I'm sure you know fully well that I have no way of putting
> that question to any relevant person at AVM, and even if I had, it would
> achieve exactly nothing at all. I am not interested in such fruitless
> political discussions. I have a simple question, to which I would like
> a simple answer.
There's no "politics" here at all.
And why wouldn't you go ask AVM, they are the ones producing the driver
for this hardware, how could it be our responsibility to get their code
to work properly, when we have absolutely no way to do so?
This is between you and AVM. I really suggest contacting the company.
I have talked to them in the past and they seem willing to help out
where they can.
thanks,
greg k-h
Johannes Berg schrieb:
> On Thu, 2008-07-31 at 16:52 +0200, Tilman Schmidt wrote:
>> Commit 782e70c6fc2290a0395850e8e02583b8b62264d8, which went into
>> 2.6.25, broke AVM's closed-source driver for this device:
>>
>> ID 057c:62ff AVM GmbH WLAN USB v1.1 (cdrom mode)
>> ID 057c:6201 AVM GmbH WLAN USB v1.1
>>
>> Is there an open source alternative for that driver, or do systems
>> with that device have to stay with kernel 2.6.24?
>
> Never heard of any such driver, what chip does it contain?
I don't know. How can I find out?
(Preferably without cracking the thing open. ;-)
http://acx100.sourceforge.net/matrix.html claims "Chipset TNETW1450"
and "support should be quite easy" - but that entry is two years old
and the "Model" link doesn't work, so I'm not sure how far that can
be trusted.
Thanks,
Tilman
--
Tilman Schmidt E-Mail: [email protected]
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Unge?ffnet mindestens haltbar bis: (siehe R?ckseite)
On Thu, 31 Jul 2008 09:38:43 -0700, Greg KH wrote:
> On Thu, Jul 31, 2008 at 04:52:41PM +0200, Tilman Schmidt wrote:
>> Commit 782e70c6fc2290a0395850e8e02583b8b62264d8, which went into
>> 2.6.25, broke AVM's closed-source driver for this device:
>>
>> ID 057c:62ff AVM GmbH WLAN USB v1.1 (cdrom mode)
>> ID 057c:6201 AVM GmbH WLAN USB v1.1
>>
>> Is there an open source alternative for that driver, or do systems
>> with that device have to stay with kernel 2.6.24?
>
> Please ask AVM, they have known about this for over 2 years now.
Please let's keep the politics out of this. I know who wrote that
patch, I know the agenda behind it and the discussion accompanying it.
Conversely, I'm sure you know fully well that I have no way of putting
that question to any relevant person at AVM, and even if I had, it would
achieve exactly nothing at all. I am not interested in such fruitless
political discussions. I have a simple question, to which I would like
a simple answer.
> There is nothing we can do about closed source kernel modules, that is
> between you and the company producing it.
I did not ask anyone to do anything about any closed source kernel module.
Your killing of non-GPL USB drivers is an irreversible fait accompli I
won't waste my time to discuss. I really honestly just want to know if
there is a way to use this device with a 2.6.25 or later kernel.
Thanks,
Tilman
On Thu, 31 Jul 2008 14:50:55 -0700, Greg KH wrote:
> On Thu, Jul 31, 2008 at 11:34:26PM +0200, Tilman Schmidt wrote:
>> Please let's keep the politics out of this. I know who wrote that
>> patch, I know the agenda behind it and the discussion accompanying it.
>> Conversely, I'm sure you know fully well that I have no way of putting
>> that question to any relevant person at AVM, and even if I had, it would
>> achieve exactly nothing at all. I am not interested in such fruitless
>> political discussions. I have a simple question, to which I would like
>> a simple answer.
>
> There's no "politics" here at all.
Oh, please ... You aren't seriously trying to tell me there's a *technical*
reason for changing EXPORT_SYMBOL to EXPORT_SYMBOL_GPL, are you?
Again, I am not interested in discussing that decision. It's been taken,
and I accept it. But let's call a spade a spade.
> And why wouldn't you go ask AVM, they are the ones producing the driver
> for this hardware, how could it be our responsibility to get their code
> to work properly, when we have absolutely no way to do so?
That's not true. Reverting commit 782e70c6fc2290a0395850e8e02583b8b62264d8
would be enough. But again, I am not asking for that. My question isn't
about getting AVM's closed source driver to work with kernel 2.6.25+.
I just want to know whether there is an open source alternative, nothing
more.
> This is between you and AVM. I really suggest contacting the company.
> I have talked to them in the past and they seem willing to help out
> where they can.
Obviously even you weren't able to convince them to convert their driver
for this device to something compatible with post 2.6.24 kernels. How
then could I possibly hope to achieve anything? I have no contractual
relationship with AVM. I don't know anybody in that company. I don't work
for anyone they would recognize. All I can do is contact the regular
consumer support people who don't even know what I am talking about and
keep asking me to boot Windows, where the device obviously works, so all
is well, no? After all, it does say "System requirements: Windows" on the
box.
But all this is just the fruitless discussion I wanted to avoid. With
your kind permission I'll stop this here and concentrate instead on the
subthread which actually deals with my question.
Thanks,
Tilman
On Fri, Aug 01, 2008 at 02:26:41AM +0300, ext Felipe Balbi wrote:
> It's like we completely removed any possibility of closed source
> drivers.
I meant, it's *not* like we completely removed any possibility of closed
source drivers, we just don't want them _in_ the kernel.
--
balbi
Hi Greg,
On Sat, Aug 02, 2008 at 08:43:41PM -0700, Greg KH wrote:
> I'd be glad to do that, anyone have a link to it?
http://sourceforge.net/project/showfiles.php?group_id=75380&package_id=75880
I suppose it's better to get the mac80211 version.
--
balbi
On Fri, 1 Aug 2008 11:50:22 +0300, Felipe Balbi wrote:
> On Fri, Aug 01, 2008 at 10:45:00AM +0200, ext Tilman Schmidt wrote:
>> -MODULE_LICENSE ("Proprietary");
>> +MODULE_LICENSE ("GPL");
[...]
>> I guess you can spot the problematic part.
>
> You can't change the module_license and publish it, dude :-p
Well done, dude. You spotted it first try. Just as I expected. :-p
--
Tilman Schmidt E-Mail: [email protected]
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Unge?ffnet mindestens haltbar bis: (siehe R?ckseite)
On Sat, Aug 02, 2008 at 11:58:02PM +0200, Tilman Schmidt wrote:
> Aug 2 19:06:16 compaq kernel: read firmware upload result
> Aug 2 19:06:16 compaq kernel: TNETW1450 firmware upload successful!
> Aug 2 19:06:16 compaq kernel: initializing max packet templates
> Aug 2 19:06:16 compaq kernel: acx: issue_cmd(): USB read error -75
hmm... an overflow here.
It's probably timing issue as well.
> Aug 2 19:06:16 compaq kernel: acx: issue_cmd(cmd:ACX1xx_CMD_INTERROGATE) FAILED
> Aug 2 19:06:16 compaq kernel: wlan%d: interrogate(type:ACX1xx_IE_MEMORY_CONFIG_OPTIONS) FAILED
> Aug 2 19:06:16 compaq kernel: dump queue head (from card):
> Aug 2 19:06:16 compaq kernel: len: 20
> Aug 2 19:06:16 compaq kernel: tx_memory_block_address: 80000B80
> Aug 2 19:06:16 compaq kernel: rx_memory_block_address: DF313D34
> Aug 2 19:06:16 compaq kernel: tx1_queue address: 10
> Aug 2 19:06:16 compaq kernel: rx1_queue address: E080FBBD
> Aug 2 19:06:16 compaq kernel: get_mask 0x00004182, set_mask 0x00000000
> Aug 2 19:06:16 compaq kernel: don't know how to get sensitivity for radio type 0x1B
> Aug 2 19:06:16 compaq kernel: got sensitivity value 0
> Aug 2 19:06:16 compaq kernel: got antenna value 0x4A
> Aug 2 19:06:16 compaq kernel: got regulatory domain 0x30
> Aug 2 19:06:16 compaq kernel: get_mask 0x00000000, set_mask 0x00000000 - after update
> Aug 2 19:06:16 compaq kernel: new ratevector: 82 84 0B 0C 12 16 18 24 2C 30 48 60 6C
> Aug 2 19:06:16 compaq kernel: setting RXconfig to 2010:0FDD
> Aug 2 19:06:16 compaq kernel: acx: === chipset TNETW1450, radio type 0x1B (An unknown radio used by TNETW1450 USB adapters), form factor 0x00 (unspecified), EEPROM version 0x05: uploaded firmware 'Rev 2.4.0.72' ===
> Aug 2 19:06:16 compaq kernel: registering network device
> Aug 2 19:06:16 compaq kernel: creating /proc entry driver/acx_wlan0
> Aug 2 19:06:16 compaq kernel: creating /proc entry driver/acx_wlan0_diag
> Aug 2 19:06:16 compaq kernel: creating /proc entry driver/acx_wlan0_eeprom
> Aug 2 19:06:16 compaq kernel: creating /proc entry driver/acx_wlan0_phy
> Aug 2 19:06:16 compaq kernel: acx: USB module v0.3.37 loaded successfully
> Aug 2 19:06:16 compaq kernel: usb 2-2: New USB device found, idVendor=057c, idProduct=6201
> Aug 2 19:06:16 compaq kernel: usb 2-2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> Aug 2 19:06:16 compaq kernel: usb 2-2: Product: WLAN USB Device
> Aug 2 19:06:16 compaq kernel: usb 2-2: Manufacturer: AVM GmbH
> Aug 2 19:06:16 compaq kernel: usb 2-2: SerialNumber: 001C4AF1E469
> Aug 2 19:06:16 compaq ifup: wlan0
> Aug 2 19:06:16 compaq ifup: No configuration found for wlan0
hmm... what does lsusb -v -d 057c:6201 reports to you ?
> The device was reported in iwconfig as:
>
> wlan0 IEEE 802.11b+/g+ ESSID:"STAF1E469" Nickname:"acx v0.3.37"
> Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
> Bit Rate:54 Mb/s Tx-Power=15 dBm
> Retry min limit:7 RTS thr:off
> Encryption key:off
> Power Management:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> but didn't work. In particular "iwlist wlan0 scan" failed with the message:
>
> wlan0 Interface doesn't support scanning : Resource temporarily unavailable
Did you try setting the parameters by hand ?
# iwconfig wlan0 essid <ESSID> key <KEY>
and then
# dhclient wlan0
> Aug 2 20:14:05 compaq kernel: usb 2-2: reset high speed USB device using ehci_hcd and address 12
> Aug 2 20:14:20 compaq kernel: usb 2-2: device descriptor read/64, error -110
It's probably affected by timing as well. That driver sure needs some
rework. Btw, are you using the mac80211 version or the other one ?
--
balbi
On Fri, Aug 01, 2008 at 10:45:00AM +0200, ext Tilman Schmidt wrote:
> -MODULE_LICENSE ("Proprietary");
> +MODULE_LICENSE ("GPL");
You can't change the module_license and publish it, dude :-p
anyways, I contacted the company yesterday night, let's see what they
reply.
--
balbi
On Sun, 3 Aug 2008 02:12:06 +0300, Felipe Balbi wrote:
> hmm... what does lsusb -v -d 057c:6201 reports to you ?
compaq:/home/ts # lsusb -vvd 057c:
Bus 002 Device 002: ID 057c:6201 AVM GmbH WLAN USB v1.1
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x057c AVM GmbH
idProduct 0x6201 WLAN USB v1.1
bcdDevice 1.00
iManufacturer 3
iProduct 2
iSerial 1 TI964E1FA4C100TNETW
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
bNumConfigurations 0
Device Status: 0x0000
(Bus Powered)
compaq:/home/ts #
>> The device was reported in iwconfig as:
>>
>> wlan0 IEEE 802.11b+/g+ ESSID:"STAF1E469" Nickname:"acx v0.3.37"
>> Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
>> Bit Rate:54 Mb/s Tx-Power=15 dBm
>> Retry min limit:7 RTS thr:off
>> Encryption key:off
>> Power Management:off
>> Link Quality:0 Signal level:0 Noise level:0
>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>>
>> but didn't work. In particular "iwlist wlan0 scan" failed with the message:
>>
>> wlan0 Interface doesn't support scanning : Resource temporarily unavailable
>
> Did you try setting the parameters by hand ?
>
> # iwconfig wlan0 essid <ESSID> key <KEY>
>
> and then
>
> # dhclient wlan0
compaq:/home/ts # iwconfig wlan0 essid MYESSID
compaq:/home/ts # iwconfig wlan0
wlan0 IEEE 802.11b+/g+ ESSID:"MYESSID" Nickname:"acx v0.3.37"
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power=15 dBm
Retry min limit:7 RTS thr:off
Encryption key:off
Power Management:off
Link Quality=0/100 Signal level=100/100 Noise level=100/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
compaq:/home/ts # iwlist wlan0 scan
wlan0 No scan results
compaq:/home/ts #
Next step would be running wpa_supplicant, because my WLAN uses WPA, but:
# wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf
rapidly floods my console with messages
ioctl[SIOCSIWENCODEEXT]: Operation not supported
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
and the syslog with
Aug 3 01:55:47 compaq kernel: get_mask 0x00000000, set_mask 0x00040000
Aug 3 01:55:47 compaq kernel: important setting has been changed. Need to update packet templates, too
Aug 3 01:55:47 compaq kernel: updating packet templates
Aug 3 01:55:47 compaq kernel: updating WEP key settings
Aug 3 01:55:47 compaq kernel: setting WEP key 0 as default
Aug 3 01:55:47 compaq kernel: acx_set_status(1):SCANNING
Aug 3 01:55:47 compaq kernel: start_scan: seems like previous scan is still running. Not starting anew. Please report
Aug 3 01:55:47 compaq kernel: get_mask 0x00000000, set_mask 0x00000000 - after update
until I hit ctrl/C.
# dhclient wlan0
just repeats
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
a couple of times with increasing interval values and finally tells me
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
> It's probably affected by timing as well. That driver sure needs some
> rework.
Yeah, looks like it. I posted a report to the project's Sourceforge
"ACX100 USB" forum, too.
Thanks,
Tilman
Hi,
1 серпня 2008 о 00:13 +0200 Tilman Schmidt написав(-ла):
> So as soon as the AVM driver switches the stick from storage mode (where it
> offers Windows drivers for installation) to WLAN mode, the acx module shows
> up.
>
> Anything I should try?
If you see some new device like /dev/cdrom? or /dev/sr? after inserting
the stick (and without closed source driver), try to run 'eject' on it.
Hopefully this device will disappear and stick will switch to WLAN mode.
Then try to load acx module. If it works, then it is possible to do this
automatically with udev. This works with my UMTS modem.
Regards,
Eugeniy Meshcheryakov
I'm sorry if I came across as arrogant or ironic. I thought
I was playing along with the tone you had set, but obviously
I got it wrong. Please accept my apologies.
Again, I did not and do not ask for help with the closed source
driver. I just want to know if there is an open source one I
can use.
EOD? Please?
Thanks,
TIlman
--
Tilman Schmidt E-Mail: [email protected]
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Unge?ffnet mindestens haltbar bis: (siehe R?ckseite)
On Sat, Aug 02, 2008 at 01:30:31AM +0200, Tilman Schmidt wrote:
> The acx module also loads all by itself, but complains about missing
> firmware and throws two backtraces:
<snip>
> Ok, next step I guess is trying to find that firmware image 'tiacx111usbc1B' on
> the temporarily appearing pseudo CD-ROM drive or on the real CD-ROM that came
> with the device. Trouble is I don't really know what I am looking for. The
> real CD-ROM contains several instances of a file named Fwusb1b.bin, could that
> be it? And if so, where should I copy it so that the acx driver will find it?
Try with that one, copy to /lib/firmware, if it doesn't work try with
the one from [1].
[1] http://www.cmartin.tk/acx/fw.tar.bz2
--
balbi
Hi,
On Sun, Aug 03, 2008 at 02:45:11AM +0200, Tilman Schmidt wrote:
> Next step would be running wpa_supplicant, because my WLAN uses WPA, but:
>
> # wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf
>
> rapidly floods my console with messages
>
> ioctl[SIOCSIWENCODEEXT]: Operation not supported
> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
>
> and the syslog with
>
> Aug 3 01:55:47 compaq kernel: get_mask 0x00000000, set_mask 0x00040000
> Aug 3 01:55:47 compaq kernel: important setting has been changed. Need to update packet templates, too
> Aug 3 01:55:47 compaq kernel: updating packet templates
> Aug 3 01:55:47 compaq kernel: updating WEP key settings
> Aug 3 01:55:47 compaq kernel: setting WEP key 0 as default
> Aug 3 01:55:47 compaq kernel: acx_set_status(1):SCANNING
> Aug 3 01:55:47 compaq kernel: start_scan: seems like previous scan is still running. Not starting anew. Please report
> Aug 3 01:55:47 compaq kernel: get_mask 0x00000000, set_mask 0x00000000 - after update
I'm wondering if that driver already supports wpa. If you have any time,
please try out with a WEP and open networks to see what happens.
> # dhclient wlan0
>
> just repeats
>
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
>
> a couple of times with increasing interval values and finally tells me
>
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping.
Yeah, it couldn't associate with the access point.
> > It's probably affected by timing as well. That driver sure needs some
> > rework.
>
> Yeah, looks like it. I posted a report to the project's Sourceforge
> "ACX100 USB" forum, too.
Maybe that driver could be sent to -stagging tree from been cleaned up
and later integrated.
--
balbi
On Sun, Aug 03, 2008 at 03:57:16AM +0300, Felipe Balbi wrote:
> > Yeah, looks like it. I posted a report to the project's Sourceforge
> > "ACX100 USB" forum, too.
>
> Maybe that driver could be sent to -stagging tree from been cleaned up
> and later integrated.
I'd be glad to do that, anyone have a link to it?
thanks,
greg k-h
John W. Linville schrieb:
> Did the acx100 driver work with your card?
Not on its own, no. But if I interpret the kernel messages correctly, it is
actually involved in driving the device when the AVM driver is present.
This is how it looks when the device is inserted:
Jul 29 08:19:00 compaq kernel: usb 2-2: new high speed USB device using ehci_hcd and address 2
Jul 29 08:19:00 compaq kernel: usb 2-2: configuration #1 chosen from 1 choice
Jul 29 08:19:00 compaq kernel: usb 2-2: New USB device found, idVendor=057c, idProduct=62ff
Jul 29 08:19:00 compaq kernel: usb 2-2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 29 08:19:00 compaq kernel: usb 2-2: Product: WLAN USB Device
Jul 29 08:19:00 compaq kernel: usb 2-2: Manufacturer: AVM GmbH
Jul 29 08:19:00 compaq kernel: usb 2-2: SerialNumber: 001C4AF1E469
Jul 29 08:19:01 compaq kernel: fwlanusb: AVM FRITZ!WLAN USB Stick driver, revision 1.00.00
Jul 29 08:19:01 compaq kernel: fwlanusb: (fwlanusb built on Jul 28 2008 at 02:39:48)
Jul 29 08:19:01 compaq kernel: fwlanusb: -- 32 bit driver --
Jul 29 08:19:01 compaq kernel: fwlanusb: Loading...
Jul 29 08:19:01 compaq kernel: fwlanusb: Found FRITZ!Wlan device in cdrom mode.
Jul 29 08:19:01 compaq kernel: fwlanusb: Doing fast eject.
Jul 29 08:19:01 compaq kernel: usb 2-2: USB disconnect, address 2
Jul 29 08:19:01 compaq kernel: usbcore: registered new interface driver fwlanusb
Jul 29 08:19:01 compaq kernel: fwlanusb: Loaded.
Jul 29 08:19:01 compaq kernel: Initializing USB Mass Storage driver...
Jul 29 08:19:01 compaq kernel: usbcore: registered new interface driver usb-storage
Jul 29 08:19:01 compaq kernel: USB Mass Storage support registered.
Jul 29 08:19:02 compaq kernel: usb 2-2: new high speed USB device using ehci_hcd and address 3
Jul 29 08:19:02 compaq kernel: usb 2-2: configuration #1 chosen from 1 choice
Jul 29 08:19:02 compaq kernel: fwlanusb: Found FRITZ!Wlan device.
Jul 29 08:19:02 compaq kernel: fwlanusb: Driver 'fwlanusb' attached to fwlanusb-stack version [Protokollstack=1.00.00]. (176)
Jul 29 08:19:02 compaq kernel: usb 2-2: reset high speed USB device using ehci_hcd and address 3
Jul 29 08:19:02 compaq kernel: acx: this driver is still EXPERIMENTAL
Jul 29 08:19:02 compaq kernel: acx: reading README file and/or Craig's HOWTO is recommended, visit http://acx100.sf.net in case of further questions/discussion
Jul 29 08:19:02 compaq kernel: acx: compiled to use 32bit I/O access. I/O timing issues might occur, such as non-working firmware upload. Report them
Jul 29 08:19:02 compaq kernel: acx: running on a little-endian CPU
Jul 29 08:19:02 compaq kernel: acx: PCI/VLYNQ module v0.3.37 initialized, waiting for cards to probe...
Jul 29 08:19:02 compaq kernel: USB module v0.3.37 initialized, probing for devices...
Jul 29 08:19:03 compaq kernel: fwlanusb: Config manager successully created and started.
Jul 29 08:19:03 compaq kernel: usb 2-2: New USB device found, idVendor=057c, idProduct=6201
Jul 29 08:19:03 compaq kernel: usb 2-2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 29 08:19:03 compaq kernel: usb 2-2: Product: WLAN USB Device
Jul 29 08:19:03 compaq kernel: usb 2-2: Manufacturer: AVM GmbH
Jul 29 08:19:03 compaq kernel: usb 2-2: SerialNumber: 001C4AF1E469
Jul 29 08:19:03 compaq kernel: usbcore: registered new interface driver acx_usb
Jul 29 08:19:03 compaq ifup: wlan0
Jul 29 08:19:03 compaq ifup: No configuration found for wlan0
So as soon as the AVM driver switches the stick from storage mode (where it
offers Windows drivers for installation) to WLAN mode, the acx module shows
up.
Anything I should try?
Thanks,
Tilman
On Fri, Aug 01, 2008 at 10:58:17AM +0200, ext Tilman Schmidt wrote:
> On Fri, 1 Aug 2008 11:50:22 +0300, Felipe Balbi wrote:
>> On Fri, Aug 01, 2008 at 10:45:00AM +0200, ext Tilman Schmidt wrote:
>>> -MODULE_LICENSE ("Proprietary");
>>> +MODULE_LICENSE ("GPL");
> [...]
>>> I guess you can spot the problematic part.
>>
>> You can't change the module_license and publish it, dude :-p
>
> Well done, dude. You spotted it first try. Just as I expected. :-p
If you wanna be ironic, really choose someone else. You could have
been trying to reach the company way before I did.
I'm giving up my free time to help people who want to be helped. If you
wanna play the ironic, choose someone else or some other mailing list.
I'm pretty sure people here are serious about their work so as I am.
Instead of playing arrogant, try to play nicely and people will like to
help you.
Once again, if you have problems with a closed source driver, there is
NOTHING we can do about it, go complain with your hw vendor and stop
wasting our time with irony.
--
balbi
On Fri, 01 Aug 2008 00:13:49 +0200, Tilman Schmidt wrote:
> So as soon as the AVM driver switches the stick from storage mode (where
> it offers Windows drivers for installation) to WLAN mode, the acx module
> shows up.
If it still uses acx in some way, an ACX chipset is involved, so any free
or open driver for the device would be one that handles those. Now, you
have some research to do.
On Fri, Aug 01, 2008 at 12:55:11AM +0200, Tilman Schmidt wrote:
> Oh, please ... You aren't seriously trying to tell me there's a *technical*
> reason for changing EXPORT_SYMBOL to EXPORT_SYMBOL_GPL, are you?
You really have no idea what you're talking about. If manufacturers
really don't wanna write gpl code, they have really sane api via
usbdev_fs.h or libusb to do it.
It's like we completely removed any possibility of closed source
drivers.
> That's not true. Reverting commit 782e70c6fc2290a0395850e8e02583b8b62264d8
> would be enough. But again, I am not asking for that. My question isn't
> about getting AVM's closed source driver to work with kernel 2.6.25+.
> I just want to know whether there is an open source alternative, nothing
> more.
Did you read the commit message?
"Over two years ago, the Linux USB developers stated that they believed
there was no way to create a USB kernel driver that was not under the
GPL. This patch moves the USB apis to enforce that decision.
There are no known closed source USB drivers in the wild, so this patch
should cause no problems."
So a) it wasn't an over-the-night decision. It was stated publicly and
given a 2 years period for everybody to know about what would happen and
b) "there are no know closed source usb drivers in the wild",
unfortunately, it looks like nobody knew about AVM's closed source
driver.
And after all, that driver isn't even closed source. I can see in the
files' header the driver is lgpl (that's actually the first lgpl driver
i see :-p)
> > This is between you and AVM. I really suggest contacting the company.
> > I have talked to them in the past and they seem willing to help out
> > where they can.
>
> Obviously even you weren't able to convince them to convert their driver
> for this device to something compatible with post 2.6.24 kernels. How
> then could I possibly hope to achieve anything? I have no contractual
> relationship with AVM. I don't know anybody in that company. I don't work
> for anyone they would recognize. All I can do is contact the regular
> consumer support people who don't even know what I am talking about and
> keep asking me to boot Windows, where the device obviously works, so all
> is well, no? After all, it does say "System requirements: Windows" on the
> box.
Again, you can get the sources under lgpl, which means you can change
the code and fix it up.
With a few changes to the source file, I could make it build. Don't have
the device to test, but I assure you it's pretty simple changes.
--
balbi
On Sat, 2 Aug 2008 11:28:52 +0300, Felipe Balbi wrote:
> On Sat, Aug 02, 2008 at 01:30:31AM +0200, Tilman Schmidt wrote:
>> The acx module also loads all by itself, but complains about missing
>> firmware and throws two backtraces:
[...]
>> real CD-ROM contains several instances of a file named Fwusb1b.bin, could that
>> be it? And if so, where should I copy it so that the acx driver will find it?
>
> Try with that one, copy to /lib/firmware,
The first attempt with that firmware failed with the messages:
Aug 2 19:01:35 compaq kernel: read firmware upload result
Aug 2 19:01:40 compaq kernel: acx: issue_cmd(cmd:ACX1xx_CMD_WAKE) FAILED
Aug 2 19:01:40 compaq kernel: initializing max packet templates
Aug 2 19:01:46 compaq kernel: acx: issue_cmd(cmd:cmd) FAILED
Aug 2 19:01:46 compaq kernel: wlan%d: acx_s_init_packet_templates() FAILED
Aug 2 19:01:46 compaq kernel: acx: init_mac() FAILED
Aug 2 19:01:46 compaq kernel: acx_usb: probe of 2-2:1.0 failed with error 1
I guess that fits in with the messages the ACX module would emit when loaded:
Aug 2 19:01:35 compaq kernel: acx: this driver is still EXPERIMENTAL
Aug 2 19:01:35 compaq kernel: acx: reading README file and/or Craig's HOWTO is recommended, visit http://acx100.sf.net in case of further questions/discussion
Aug 2 19:01:35 compaq kernel: acx: compiled to use 32bit I/O access. I/O timing issues might occur, such as non-working firmware upload. Report them
On the second attempt, the firmware upload succeeded, but more errors
followed:
Aug 2 19:06:16 compaq kernel: read firmware upload result
Aug 2 19:06:16 compaq kernel: TNETW1450 firmware upload successful!
Aug 2 19:06:16 compaq kernel: initializing max packet templates
Aug 2 19:06:16 compaq kernel: acx: issue_cmd(): USB read error -75
Aug 2 19:06:16 compaq kernel: acx: issue_cmd(cmd:ACX1xx_CMD_INTERROGATE) FAILED
Aug 2 19:06:16 compaq kernel: wlan%d: interrogate(type:ACX1xx_IE_MEMORY_CONFIG_OPTIONS) FAILED
Aug 2 19:06:16 compaq kernel: dump queue head (from card):
Aug 2 19:06:16 compaq kernel: len: 20
Aug 2 19:06:16 compaq kernel: tx_memory_block_address: 80000B80
Aug 2 19:06:16 compaq kernel: rx_memory_block_address: DF313D34
Aug 2 19:06:16 compaq kernel: tx1_queue address: 10
Aug 2 19:06:16 compaq kernel: rx1_queue address: E080FBBD
Aug 2 19:06:16 compaq kernel: get_mask 0x00004182, set_mask 0x00000000
Aug 2 19:06:16 compaq kernel: don't know how to get sensitivity for radio type 0x1B
Aug 2 19:06:16 compaq kernel: got sensitivity value 0
Aug 2 19:06:16 compaq kernel: got antenna value 0x4A
Aug 2 19:06:16 compaq kernel: got regulatory domain 0x30
Aug 2 19:06:16 compaq kernel: get_mask 0x00000000, set_mask 0x00000000 - after update
Aug 2 19:06:16 compaq kernel: new ratevector: 82 84 0B 0C 12 16 18 24 2C 30 48 60 6C
Aug 2 19:06:16 compaq kernel: setting RXconfig to 2010:0FDD
Aug 2 19:06:16 compaq kernel: acx: === chipset TNETW1450, radio type 0x1B (An unknown radio used by TNETW1450 USB adapters), form factor 0x00 (unspecified), EEPROM version 0x05: uploaded firmware 'Rev 2.4.0.72' ===
Aug 2 19:06:16 compaq kernel: registering network device
Aug 2 19:06:16 compaq kernel: creating /proc entry driver/acx_wlan0
Aug 2 19:06:16 compaq kernel: creating /proc entry driver/acx_wlan0_diag
Aug 2 19:06:16 compaq kernel: creating /proc entry driver/acx_wlan0_eeprom
Aug 2 19:06:16 compaq kernel: creating /proc entry driver/acx_wlan0_phy
Aug 2 19:06:16 compaq kernel: acx: USB module v0.3.37 loaded successfully
Aug 2 19:06:16 compaq kernel: usb 2-2: New USB device found, idVendor=057c, idProduct=6201
Aug 2 19:06:16 compaq kernel: usb 2-2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Aug 2 19:06:16 compaq kernel: usb 2-2: Product: WLAN USB Device
Aug 2 19:06:16 compaq kernel: usb 2-2: Manufacturer: AVM GmbH
Aug 2 19:06:16 compaq kernel: usb 2-2: SerialNumber: 001C4AF1E469
Aug 2 19:06:16 compaq ifup: wlan0
Aug 2 19:06:16 compaq ifup: No configuration found for wlan0
The device was reported in iwconfig as:
wlan0 IEEE 802.11b+/g+ ESSID:"STAF1E469" Nickname:"acx v0.3.37"
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power=15 dBm
Retry min limit:7 RTS thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
but didn't work. In particular "iwlist wlan0 scan" failed with the message:
wlan0 Interface doesn't support scanning : Resource temporarily unavailable
(No accompanying kernel message.)
> if it doesn't work try with the one from [1].
>
> [1] http://www.cmartin.tk/acx/fw.tar.bz2
That archive contains several firmware images but none that seems to fit
the device. Specifically, the module asks for tiacx111usbc1B, but the
archive only has tiacx100usb, no tiacx111usb*, and the radio module IDs
(last two characters) for ACX111 include 16, 17 and 19, but not 1B.
Also, http://acx100.sourceforge.net/wiki/Firmware has this not very
encouraging note:
* The new TNETW1450 (USB 2.0 capable chipset) isn't fully supported by our driver yet (useful support probably available soon).
[This is as of Feb. 2006 - still not supported?]
Btw, about two times out of three, after plugging it in, the device even
fails to activate in Mass Storage mode, endlessly reporting:
Aug 2 20:14:05 compaq kernel: usb 2-2: reset high speed USB device using ehci_hcd and address 12
Aug 2 20:14:20 compaq kernel: usb 2-2: device descriptor read/64, error -110
(ie. ETIMEDOUT) and never switching to WLAN mode. Unplugging and plugging
back in a couple of times succeeds eventually.
Anything else I should test?
Thanks,
Tilman
On Fri, 1 Aug 2008 00:43:57 +0200, Eugeniy Meshcheryakov wrote:
> If you see some new device like /dev/cdrom? or /dev/sr? after inserting
> the stick (and without closed source driver),
I do. The stick initially announces itself as:
Aug 2 01:00:21 compaq kernel: usb 2-4: New USB device found, idVendor=057c, idProduct=62ff
Aug 2 01:00:21 compaq kernel: usb 2-4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Aug 2 01:00:21 compaq kernel: usb 2-4: Product: WLAN USB Device
Aug 2 01:00:21 compaq kernel: usb 2-4: Manufacturer: AVM GmbH
Aug 2 01:00:21 compaq kernel: usb 2-4: SerialNumber: 001C4AF1E469
Aug 2 01:00:21 compaq kernel: usb-storage: device found at 7
Aug 2 01:00:21 compaq kernel: usb-storage: waiting for device to settle before scanning
Aug 2 01:00:22 compaq kernel: scsi 3:0:0:0: CD-ROM FRITZ! WLAN selfinstall 1.00 PQ: 0 ANSI: 0 CCS
Aug 2 01:00:22 compaq kernel: sr1: scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray
Aug 2 01:00:22 compaq kernel: sr 3:0:0:0: Attached scsi CD-ROM sr1
Aug 2 01:00:22 compaq kernel: sr 3:0:0:0: Attached scsi generic sg2 type 5
Aug 2 01:00:22 compaq kernel: usb-storage: device scan complete
and gets automounted by hal:
Aug 2 01:00:23 compaq gnome-keyring-daemon[3186]: adding removable location: volume_label_FRITZ_WLAN_USB_Stick_selfinstall at /media/FRITZ!WLAN USB Stick selfinstall
Aug 2 01:00:23 compaq hald: mounted /dev/sr1 on behalf of uid 1000
> try to run 'eject' on it.
> Hopefully this device will disappear and stick will switch to WLAN mode.
I don't even have to eject it. After about 90 secs it disconnects all by
itself:
Aug 2 01:01:52 compaq kernel: usb 2-4: USB disconnect, address 7
Aug 2 01:01:52 compaq hald[1667]: forcibly attempting to lazy unmount /dev/sr1 as enclosing drive was disconnected
Aug 2 01:01:52 compaq kernel: scsi 3:0:0:0: rejecting I/O to dead device
Aug 2 01:01:52 compaq gnome-keyring-daemon[3186]: removing removable location: volume_label_FRITZ_WLAN_USB_Stick_selfinstall
Aug 2 01:01:52 compaq hald: unmounted /dev/sr1 from '/media/FRITZ!WLAN USB Stick selfinstall' on behalf of uid 0
and then reconnects as:
Aug 2 01:01:54 compaq kernel: usb 2-4: New USB device found, idVendor=057c, idProduct=6201
Aug 2 01:01:54 compaq kernel: usb 2-4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Aug 2 01:01:54 compaq kernel: usb 2-4: Product: WLAN USB Device
Aug 2 01:01:54 compaq kernel: usb 2-4: Manufacturer: AVM GmbH
Aug 2 01:01:54 compaq kernel: usb 2-4: SerialNumber: 001C4AF1E469
> Then try to load acx module. If it works, then it is possible to do this
> automatically with udev. This works with my UMTS modem.
The acx module also loads all by itself, but complains about missing
firmware and throws two backtraces:
Aug 2 01:01:54 compaq kernel: acx: this driver is still EXPERIMENTAL
Aug 2 01:01:54 compaq kernel: acx: reading README file and/or Craig's HOWTO is recommended, visit http://acx100.sf.net in case of further questions/discussion
Aug 2 01:01:54 compaq kernel: acx: compiled to use 32bit I/O access. I/O timing issues might occur, such as non-working firmware upload. Report them
Aug 2 01:01:54 compaq kernel: acx: running on a little-endian CPU
Aug 2 01:01:54 compaq kernel: acx: PCI/VLYNQ module v0.3.37 initialized, waiting for cards to probe...
Aug 2 01:01:54 compaq kernel: USB module v0.3.37 initialized, probing for devices...
Aug 2 01:01:54 compaq kernel: wait for device ready
Aug 2 01:01:54 compaq kernel: requesting firmware image 'tiacx111usbc1B'
Aug 2 01:01:54 compaq kernel: acx: firmware image 'tiacx111usbc1B' was not provided. Check your hotplug scripts
Aug 2 01:01:54 compaq kernel: acx: issue_cmd(cmd:ACX1xx_CMD_WAKE) FAILED
Aug 2 01:01:54 compaq kernel: Pid: 3739, comm: modprobe Tainted: G N 2.6.25.11-0.1-default #1
Aug 2 01:01:54 compaq kernel: [<c01071d9>] dump_trace+0x63/0x227
Aug 2 01:01:54 compaq kernel: [<c0107c8a>] show_trace+0x15/0x29
Aug 2 01:01:54 compaq kernel: [<c02e66d8>] _etext+0x5b/0x65
Aug 2 01:01:54 compaq kernel: [<e0bd1bed>] acxusb_s_issue_cmd_timeo_debug+0x2e7/0x31c [acx]
Aug 2 01:01:54 compaq kernel: [<e0bd2042>] acxusb_e_probe+0x420/0x602 [acx]
Aug 2 01:01:54 compaq kernel: [<e088ccec>] usb_probe_interface+0xc6/0x108 [usbcore]
Aug 2 01:01:54 compaq kernel: [<c024c315>] driver_probe_device+0xa0/0x136
Aug 2 01:01:54 compaq kernel: [<c024c406>] __driver_attach+0x5b/0x91
Aug 2 01:01:54 compaq kernel: [<c024bcf1>] bus_for_each_dev+0x36/0x5e
Aug 2 01:01:54 compaq kernel: [<c024c1ba>] driver_attach+0x14/0x16
Aug 2 01:01:54 compaq kernel: [<c024b6f6>] bus_add_driver+0x9d/0x1ba
Aug 2 01:01:54 compaq kernel: [<c024c57c>] driver_register+0x47/0xa7
Aug 2 01:01:54 compaq kernel: [<e088cee1>] usb_register_driver+0x66/0xc0 [usbcore]
Aug 2 01:01:54 compaq kernel: [<e07af0bd>] acxusb_e_init_module+0x2b/0x2d [acx]
Aug 2 01:01:54 compaq kernel: [<e07af01a>] acx_e_init_module+0x1a/0x2a [acx]
Aug 2 01:01:54 compaq kernel: [<c01434d1>] sys_init_module+0x198b/0x1ab8
Aug 2 01:01:54 compaq kernel: [<c01059e4>] sysenter_past_esp+0x6d/0xa9
Aug 2 01:01:54 compaq kernel: [<ffffe430>] 0xffffe430
Aug 2 01:01:54 compaq kernel: =======================
Aug 2 01:01:54 compaq kernel: initializing max packet templates
Aug 2 01:01:54 compaq kernel: acx: issue_cmd(cmd:cmd) FAILED
Aug 2 01:01:54 compaq kernel: Pid: 3739, comm: modprobe Tainted: G N 2.6.25.11-0.1-default #1
Aug 2 01:01:54 compaq kernel: [<c01071d9>] dump_trace+0x63/0x227
Aug 2 01:01:54 compaq kernel: [<c0107c8a>] show_trace+0x15/0x29
Aug 2 01:01:54 compaq kernel: [<c02e66d8>] _etext+0x5b/0x65
Aug 2 01:01:54 compaq kernel: [<e0bd1bed>] acxusb_s_issue_cmd_timeo_debug+0x2e7/0x31c [acx]
Aug 2 01:01:54 compaq kernel: [<e0bc6d70>] acx_s_init_max_template_generic+0x75/0x80 [acx]
Aug 2 01:01:54 compaq kernel: [<e0bc6dc0>] acx_s_init_packet_templates+0x45/0x183 [acx]
Aug 2 01:01:54 compaq kernel: [<e0bccf50>] acx_s_init_mac+0x8c/0x6c0 [acx]
Aug 2 01:01:54 compaq kernel: [<e0bd204d>] acxusb_e_probe+0x42b/0x602 [acx]
Aug 2 01:01:54 compaq kernel: [<e088ccec>] usb_probe_interface+0xc6/0x108 [usbcore]
Aug 2 01:01:54 compaq kernel: [<c024c315>] driver_probe_device+0xa0/0x136
Aug 2 01:01:54 compaq kernel: [<c024c406>] __driver_attach+0x5b/0x91
Aug 2 01:01:54 compaq kernel: [<c024bcf1>] bus_for_each_dev+0x36/0x5e
Aug 2 01:01:54 compaq kernel: [<c024c1ba>] driver_attach+0x14/0x16
Aug 2 01:01:54 compaq kernel: [<c024b6f6>] bus_add_driver+0x9d/0x1ba
Aug 2 01:01:54 compaq kernel: [<c024c57c>] driver_register+0x47/0xa7
Aug 2 01:01:54 compaq kernel: [<e088cee1>] usb_register_driver+0x66/0xc0 [usbcore]
Aug 2 01:01:54 compaq kernel: [<e07af0bd>] acxusb_e_init_module+0x2b/0x2d [acx]
Aug 2 01:01:54 compaq kernel: [<e07af01a>] acx_e_init_module+0x1a/0x2a [acx]
Aug 2 01:01:54 compaq kernel: [<c01434d1>] sys_init_module+0x198b/0x1ab8
Aug 2 01:01:54 compaq kernel: [<c01059e4>] sysenter_past_esp+0x6d/0xa9
Aug 2 01:01:54 compaq kernel: [<ffffe430>] 0xffffe430
Aug 2 01:01:54 compaq kernel: =======================
Aug 2 01:01:54 compaq kernel: wlan%d: acx_s_init_packet_templates() FAILED
Aug 2 01:01:54 compaq kernel: acx: init_mac() FAILED
Aug 2 01:01:54 compaq kernel: acx_usb: probe of 2-4:1.0 failed with error 1
Aug 2 01:01:54 compaq kernel: usbcore: registered new interface driver acx_usb
Aug 2 01:01:54 compaq firmware.sh[3744]: Cannot find firmware file 'tiacx111usbc1B'
Ok, next step I guess is trying to find that firmware image 'tiacx111usbc1B' on
the temporarily appearing pseudo CD-ROM drive or on the real CD-ROM that came
with the device. Trouble is I don't really know what I am looking for. The
real CD-ROM contains several instances of a file named Fwusb1b.bin, could that
be it? And if so, where should I copy it so that the acx driver will find it?
Thanks,
Tilman
Felipe Balbi <me@...> writes:
>
> Hi Greg,
>
> On Sat, Aug 02, 2008 at 08:43:41PM -0700, Greg KH wrote:
> > I'd be glad to do that, anyone have a link to it?
>
> http://sourceforge.net/project/showfiles.php?group_id=75380&package_id=75880
>
> I suppose it's better to get the mac80211 version.
>
WAIT! (sorry)
As far as I remember ACX project was was meant to be merged long time ago, but
it was halted because it's unknown legal status. The developers did not use
"clean room" while reverse engineering. This means that the same people who
reverse engineered the proprietary Texas Instruments driver wrote the linux
driver. No one says that the developers copied some TI code but after problems
with S.C.O. Group, Mr. Linville doesn't want any future trouble. Pulling ACX
code to any common tree without consulting Mr. Linville first is a bad idea.
Felipe, Greg,
Please accept that I am not interested in discussing the merits of
commit 782e70c6fc2290a0395850e8e02583b8b62264d8. You seem to have
a great urge to explain these, and you are of course free to do so
whenever you want, but it is completely irrelevant to my question.
My only concern is to evaluate my options for using this device
with recent Linux releases, and I'll therefore limit my reply to
those of your statements which appear pertinent to that.
On Fri, 1 Aug 2008 02:26:41 +0300, Felipe Balbi wrote:
> And after all, that driver isn't even closed source. I can see in the
> files' header the driver is lgpl (that's actually the first lgpl driver
> i see :-p)
I think you are mistaken. Only the glue code to recompile for the
target kernel is LGPLed, the binary file which gets linked to it
obviously isn't. Consequently, line 49 of fritz/src/main.c says,
in no unclear words:
MODULE_LICENSE ("Proprietary");
But even if you were right it wouldn't help, because LGPL drivers
aren't permitted to use the USB API either.
> With a few changes to the source file, I could make it build. Don't have
> the device to test, but I assure you it's pretty simple changes.
Sure thing. In fact, that's what I did before posting my question.
For reference, here's the complete minimal patch needed to make
AVM's fwlanusb-1.00.00.tar.gz driver work on an openSUSE 11.0
system with kernel 2.6.25.11:
diff -rup fritz/src/defs.h fritz.patched/src/defs.h
--- fritz/src/defs.h 2007-07-05 15:00:00.000000000 +0200
+++ fritz.patched/src/defs.h 2008-07-11 17:47:08.000000000 +0200
@@ -60,7 +60,7 @@
#define UNUSED_ARG(x) (x)=(x)
-typedef unsigned long uintptr_t;
+//typedef unsigned long uintptr_t;
/*---------------------------------------------------------------------------*\
\*---------------------------------------------------------------------------*/
diff -rup fritz/src/main.c fritz.patched/src/main.c
--- fritz/src/main.c 2007-07-05 15:00:00.000000000 +0200
+++ fritz.patched/src/main.c 2008-07-11 17:48:45.000000000 +0200
@@ -46,7 +46,7 @@
/*---------------------------------------------------------------------------*\
\*---------------------------------------------------------------------------*/
-MODULE_LICENSE ("Proprietary");
+MODULE_LICENSE ("GPL");
MODULE_DESCRIPTION ("Driver for " PRODUCT_LOGO);
/*---------------------------------------------------------------------------*\
diff -rup fritz/src/wext.c fritz.patched/src/wext.c
--- fritz/src/wext.c 2007-07-05 15:00:00.000000000 +0200
+++ fritz.patched/src/wext.c 2008-07-28 02:37:10.000000000 +0200
@@ -68,7 +68,7 @@ static int fwlanusb_get_name (
struct net_device *dev, struct iw_request_info *info,
union iwreq_data *wrqu, char *extra) {
- strcpy(wrqu->name, "IEEE 802.11b/g");
+ snprintf(wrqu->name, IFNAMSIZ, "IEEE 802.11b/g");
return 0;
}
I guess you can spot the problematic part.
Thanks,
Tilman
--
Tilman Schmidt E-Mail: [email protected]
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Unge?ffnet mindestens haltbar bis: (siehe R?ckseite)