From: Tilman Schmidt <tilman@imap.cc>
To: Eugeniy Meshcheryakov <eugen@debian.org>
Cc: linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Q: support for AVM Fritz! WLAN USB in kernel 2.6.25+
Date: Sat, 02 Aug 2008 01:30:31 +0200 [thread overview]
Message-ID: <48939C97.5030608@imap.cc> (raw)
In-Reply-To: <20080731224357.GA9741@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 8000 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
next prev parent reply other threads:[~2008-08-01 23:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 14:52 Q: support for AVM Fritz! WLAN USB in kernel 2.6.25+ Tilman Schmidt
2008-07-31 15:25 ` Johannes Berg
2008-07-31 16:34 ` Tilman Schmidt
2008-07-31 16:50 ` John W. Linville
2008-07-31 22:13 ` Tilman Schmidt
2008-07-31 22:43 ` Eugeniy Meshcheryakov
2008-08-01 23:30 ` Tilman Schmidt [this message]
2008-08-02 8:28 ` Felipe Balbi
2008-08-02 21:58 ` Tilman Schmidt
2008-08-02 23:12 ` Felipe Balbi
2008-08-03 0:45 ` Tilman Schmidt
2008-08-03 0:57 ` Felipe Balbi
2008-08-03 3:43 ` Greg KH
2008-08-03 9:11 ` Felipe Balbi
2008-08-03 21:10 ` Kamil Dzida
2008-08-01 19:04 ` Daniel Gimpelevich
2008-07-31 16:38 ` Greg KH
2008-07-31 21:34 ` Tilman Schmidt
2008-07-31 21:50 ` Greg KH
2008-07-31 22:55 ` Tilman Schmidt
2008-07-31 23:26 ` Felipe Balbi
2008-08-01 8:45 ` Tilman Schmidt
2008-08-01 8:50 ` Felipe Balbi
2008-08-01 8:58 ` Tilman Schmidt
2008-08-01 9:05 ` Felipe Balbi
2008-08-01 9:25 ` Tilman Schmidt
2008-08-01 8:45 ` Felipe Balbi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48939C97.5030608@imap.cc \
--to=tilman@imap.cc \
--cc=eugen@debian.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).