From: Dave Sampson <samper.d@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: firmware hotpluging (ACX100 PCMCIA)
Date: Fri, 13 Apr 2007 17:37:18 +0000 [thread overview]
Message-ID: <461FBFCE.5000709@gmail.com> (raw)
Alright we have made changes that gave new udev monitor response see
bellow... but still no glorry
what I did
1. Checked tha ACX howto and found that there was no mention of the
missing firmware mentioned in UDEV
FIRMWARE=tiacx100c0D
2. Googled the firmware and found that there has been a change in naming conventions. Found this page
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/22238
saying that the missing firmware is renamed from RADIO11.bin so I went a got it from here
ftp://ftp.dlink.com/Wireless/dwl520+/Driver/dwl520+_drivers_307.zip <ftp://ftp.dlink.com/Wireless/dwl520+/Driver/dwl520+_drivers_307.zip> and creating the necessary file tiacx100c0D from RADIO11.BIN(from this package).
3. Then when I pluged in the card again the computer crashed
4. rebooted with pcmcia card out and logged in
5. plugged card in
6. results of dmesg (what's up with the kernel bug?)
====kernel BUG at drivers/pci/bus.c:127!
invalid opcode: 0000 [#1]
SMP
last sysfs file: /class/net/eth0/carrier
Modules linked in: ndiswrapper(U) acx(U) autofs4 hidp rfcomm l2cap bluetooth sunrpc nf_conntrack_netbios_ns ipt_REJECT nf_conntrack_ipv4 xt_state nf_conntrack nfnetlink iptable_filter ip_tables ip6t_REJECT xt_tcpudp ip6table_filter ip6_tables x_tables dm_multipath video sbs ibm_acpi i2c_ec dock button battery asus_acpi backlight ac ipv6 lp floppy joydev i2c_sis96x pcspkr i2c_core irda snd_intel8x0m snd_intel8x0 snd_ac97_codec ac97_bus snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm crc_ccitt snd_timer snd soundcore snd_page_alloc ohci1394 ieee1394 8139too 8139cp mii parport_pc ide_cd parport cdrom serio_raw dm_snapshot dm_zero dm_mirror dm_mod ext3 jbd ehci_hcd ohci_hcd uhci_hcd
CPU: 0
EIP: 0060:[<c04f0e4f>] Tainted: P VLI
EFLAGS: 00010246 (2.6.20-1.2933.fc6 #1)
EIP is at pci_bus_add_devices+0x61/0xfa
eax: cb2ad008 ebx: cb2ad000 ecx: ffffffff edx: 00000046
esi: edc07400 edi: edc07414 ebp: 00000002 esp: c1858f4c
ds: 007b es: 007b ss: 0068
Process pccardd (pid: 302, ti¡858000 taskÌc102b0 task.ti¡858000)
Stack: c06bc175 c06bd01b cb2ad13c edc07400 edc0740c edeb6028 c057c2b3 c1858f84
edeb6028 00000000 00000080 00000000 c05793a4 c06cf40b c06cf3fc 00000000
edeb61b4 edeb6028 edeb61b4 edeb6028 c0579855 c06fb280 c183de5c 00000000
Call Trace:
[<c057c2b3>] cb_alloc+0x97/0xa9
[<c05793a4>] socket_insert+0xbd/0xe3
[<c0579855>] pccardd+0x141/0x1ea
[<c04226ab>] default_wake_function+0x0/0xc
[<c0579714>] pccardd+0x0/0x1ea
[<c04377c7>] kthread+0xb0/0xd9
[<c0437717>] kthread+0x0/0xd9
[<c0404b33>] kernel_thread_helper+0x7/0x10
===========Code: c1 6b c0 e8 ad 6d f3 ff 8b 5b 08 83 eb 08 8b 43 08 0f 18 00 90 8d 7b 08 8d 46 14 39 c7 75 b8 8b 5e 14 e9 81 00 00 00 39 1b 75 04 <0f> 0b eb fe 8b 43 14 85 c0 74 6f 39 00 75 25 b8 0c e3 70 c0 e8
EIP: [<c04f0e4f>] pci_bus_add_devices+0x61/0xfa SS:ESP 0068:c1858f4c
====
7. results of udevmonitor --env
Where to now?
NOTE: The driver may be trying to load one or all of drivers for acx
wither acx_pci, just acx or ,acx_usb
===========UEVENT[1176485253.076367] add@/devices/pci0000:00/0000:00:0c.0/0000:02:00.0
ACTION≠d
DEVPATH=/devices/pci0000:00/0000:00:0c.0/0000:02:00.0
SUBSYSTEM=pci
SEQNUMÇ9
PHYSDEVBUS=pci
PCI_CLASS(000
PCI_ID\x104C:8400
PCI_SUBSYS_ID\x1186:3B00
PCI_SLOT_NAME\000:02:00.0
MODALIAS=pci:v0000104Cd00008400sv00001186sd00003B00bc02sc80i00
UEVENT[1176485253.076525] add@/class/firmware/0000:02:00.0
ACTION≠d
DEVPATH=/class/firmware/0000:02:00.0
SUBSYSTEM=firmware
SEQNUMÉ0
FIRMWARE=tiacx100c0D
TIMEOUT\x10
UEVENT[1176485253.119705] remove@/class/firmware/0000:02:00.0
ACTION=remove
DEVPATH=/class/firmware/0000:02:00.0
SUBSYSTEM=firmware
SEQNUMÉ1
FIRMWARE=tiacx100c0D
TIMEOUT\x10
UDEV [1176485253.122710] remove@/class/firmware/0000:02:00.0
UDEV_LOG=3
ACTION=remove
DEVPATH=/class/firmware/0000:02:00.0
SUBSYSTEM=firmware
SEQNUMÉ1
FIRMWARE=tiacx100c0D
TIMEOUT\x10
UDEVD_EVENT=1
UDEV [1176485253.217456] add@/devices/pci0000:00/0000:00:0c.0/0000:02:00.0
UDEV_LOG=3
ACTION≠d
DEVPATH=/devices/pci0000:00/0000:00:0c.0/0000:02:00.0
SUBSYSTEM=pci
SEQNUMÇ9
PHYSDEVBUS=pci
PCI_CLASS(000
PCI_ID\x104C:8400
PCI_SUBSYS_ID\x1186:3B00
PCI_SLOT_NAME\000:02:00.0
MODALIAS=pci:v0000104Cd00008400sv00001186sd00003B00bc02sc80i00
UDEVD_EVENT=1
UEVENT[1176485255.171408]
remove@/devices/pci0000:00/0000:00:0c.0/0000:02:00.0
ACTION=remove
DEVPATH=/devices/pci0000:00/0000:00:0c.0/0000:02:00.0
SUBSYSTEM=pci
SEQNUMÉ2
PHYSDEVBUS=pci
PCI_CLASS(000
PCI_ID\x104C:8400
PCI_SUBSYS_ID\x1186:3B00
PCI_SLOT_NAME\000:02:00.0
MODALIAS=pci:v0000104Cd00008400sv00001186sd00003B00bc02sc80i00
UDEV [1176485255.175766]
remove@/devices/pci0000:00/0000:00:0c.0/0000:02:00.0
UDEV_LOG=3
ACTION=remove
DEVPATH=/devices/pci0000:00/0000:00:0c.0/0000:02:00.0
SUBSYSTEM=pci
SEQNUMÉ2
PHYSDEVBUS=pci
PCI_CLASS(000
PCI_ID\x104C:8400
PCI_SUBSYS_ID\x1186:3B00
PCI_SLOT_NAME\000:02:00.0
MODALIAS=pci:v0000104Cd00008400sv00001186sd00003B00bc02sc80i00
UDEVD_EVENT=1
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: ------------[ cut here ]------------
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: invalid opcode: 0000 [#1]
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: SMP
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: CPU: 0
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: EIP: 0060:[<c04f0e4f>] Tainted: P VLI
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: EFLAGS: 00010246 (2.6.20-1.2933.fc6 #1)
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: EIP is at pci_bus_add_devices+0x61/0xfa
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: eax: cb2ad008 ebx: cb2ad000 ecx: ffffffff edx: 00000046
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: esi: edc07400 edi: edc07414 ebp: 00000002 esp: c1858f4c
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: ds: 007b es: 007b ss: 0068
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: Process pccardd (pid: 302, ti¡858000 taskÌc102b0
task.ti¡858000)
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: Stack: c06bc175 c06bd01b cb2ad13c edc07400 edc0740c
edeb6028 c057c2b3 c1858f84
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: edeb6028 00000000 00000080 00000000 c05793a4
c06cf40b c06cf3fc 00000000
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: edeb61b4 edeb6028 edeb61b4 edeb6028 c0579855
c06fb280 c183de5c 00000000
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: Call Trace:
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: [<c057c2b3>] cb_alloc+0x97/0xa9
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: [<c05793a4>] socket_insert+0xbd/0xe3
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: [<c0579855>] pccardd+0x141/0x1ea
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: [<c04226ab>] default_wake_function+0x0/0xc
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: [<c0579714>] pccardd+0x0/0x1ea
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: [<c04377c7>] kthread+0xb0/0xd9
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: [<c0437717>] kthread+0x0/0xd9
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: [<c0404b33>] kernel_thread_helper+0x7/0x10
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: ===========
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: Code: c1 6b c0 e8 ad 6d f3 ff 8b 5b 08 83 eb 08 8b 43 08
0f 18 00 90 8d 7b 08 8d 46 14 39 c7 75 b8 8b 5e 14 e9 81 00 00 00 39 1b
75 04 <0f> 0b eb fe 8b 43 14 85 c0 74 6f 39 00 75 25 b8 0c e3 70 c0 e8
Message from syslogd@mobile at Fri Apr 13 13:27:35 2007 ...
mobile kernel: EIP: [<c04f0e4f>] pci_bus_add_devices+0x61/0xfa SS:ESP
0068:c1858f4c
===========
Kay Sievers wrote:
> On Fri, 2007-04-13 at 12:07 -0400, Dave Sampson wrote:
>
>> The bellow output is what udev monitor --env spits back when I plug in
>> my PCMCIA card (which essentialy loads the module at the same time). I
>> really need to learn more about udev, cause it is a big black box.
>>
>
> You get this event:
> UEVENT[1176480087.807781] add@/class/firmware/0000:02:00.0
> ACTION≠d
> DEVPATH=/class/firmware/0000:02:00.0
> SUBSYSTEM=firmware
> SEQNUM\x1037
> FIRMWARE=tiacx100c0D
>
> Do you have that file on your box?:
> /lib/firmware/tiacx100c0D
>
>
>> Furthermore I don't wish to complicate matters but I notice that it
>> creates device wlan0.. is there a way to make it create a ethX device. I
>> know its a wireless device so that is convention, but the application i
>> am trying to get going (kismet) thinks that acx will mount as a
>> /dev/ethx. If its an easy answer great, if not then lets focus on the
>> firmware first.
>>
>
> Most distros create persistent network names, by writing rules for every
> discovered device and assing the same name after reboot. You would just
> need to edit the rules file and set a different name.
>
> Kay
>
>
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDfiVDEV
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
reply other threads:[~2007-04-13 17:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=461FBFCE.5000709@gmail.com \
--to=samper.d@gmail.com \
--cc=linux-hotplug@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).