Hi, I dug around a little bit on the FC2 (working) setup and FC3 (broken) setup for WG511. I enabled DEBUG in /etc/hotplug.d/default/default.hotplug and observed the messages that show up in /var/log/messages when I insert the card in the cardbus slot. It seems the FC2 kernel invokes the hotplug system for a lot of things. Here is a log snippet: Nov 23 19:47:46 yoda default.hotplug[2512]: arguments (pci) env (PCI_SLOT_NAME=0000:02:00.0 PCI_ID=1260:3890 OLDPWD=/ DEVPATH=/devices/pci0000:00/0000:00:0a.0/0000:02:00.0 PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION=add PWD=/etc/hotplug PCI_SUBSYS_ID=1385:4800 HOME=/ SHLVL=2 DEBUG=yes PCI_CLASS=28000 SEQNUM=298 _=/bin/env) Nov 23 19:47:46 yoda default.hotplug[2512]: invoke /etc/hotplug/pci.agent () Nov 23 19:47:47 yoda pci.agent[2512]: Setup prism54 for PCI slot 0000:02:00.0 Nov 23 19:47:47 yoda default.hotplug[2538]: arguments (net) env (OLDPWD=/ DEVPATH=/class/net/eth1 PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION=add PWD=/etc/hotplug HOME=/ SHLVL=2 INTERFACE=eth1 DEBUG=yes SEQNUM=299 _=/bin/env) Nov 23 19:47:47 yoda default.hotplug[2538]: invoke /etc/hotplug/net.agent () Nov 23 19:47:47 yoda net.agent[2538]: invoke ifup eth1 Nov 23 19:47:47 yoda kernel: PCI: Enabling device 0000:02:00.0 (0000 -> 0002) Nov 23 19:47:47 yoda default.hotplug[2596]: arguments (firmware) env (OLDPWD=/ DEVPATH=/class/firmware/0000:02:00.0 FIRMWARE=isl3890 PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION=add PWD=/etc/hotplug HOME=/ SHLVL=2 DEBUG=yes SEQNUM=301 _=/bin/env) Nov 23 19:47:47 yoda default.hotplug[2596]: invoke /etc/hotplug/firmware.agent () Nov 23 19:47:47 yoda default.hotplug[2609]: arguments (firmware) env (OLDPWD=/ DEVPATH=/class/firmware/0000:02:00.0 FIRMWARE=isl3890 PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION=remove PWD=/etc/hotplug HOME=/ SHLVL=2 DEBUG=yes SEQNUM=302 _=/bin/env) Nov 23 19:47:47 yoda default.hotplug[2609]: invoke /etc/hotplug/firmware.agent () Nov 23 19:47:49 yoda dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67 Nov 23 19:47:49 yoda dhclient: DHCPACK from 192.168.0.1 Nov 23 19:47:49 yoda dhclient: bound to 192.168.0.101 -- renewal in 266678 seconds. END OF DUMP Now if I do the same thing in FC3, here is what I get: Nov 23 19:40:22 neo default.hotplug[3844]: arguments (net) env (OLDPWD=/ DEVPATH=/class/net/eth1 PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION=add PWD=/etc/hotplug HOME=/ SHLVL=2 INTERFACE=eth1 DEBUG=yes SEQNUM=316 _=/bin/env) Nov 23 19:40:22 neo default.hotplug[3844]: invoke /etc/hotplug/net.agent () Nov 23 19:40:22 neo net.agent[3844]: invoke ifup eth1 Nov 23 19:40:22 neo kernel: PCI: Enabling device 0000:02:00.0 (0000 -> 0002) Nov 23 19:40:22 neo default.hotplug[3870]: arguments (pci) env (PCI_SLOT_NAME=0000:02:00.0 PCI_ID=1260:3890 OLDPWD=/ DEVPATH=/devices/pci0000:00/0000:00:0a.0/0000:02:00.0 PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION=add PWD=/etc/hotplug PCI_SUBSYS_ID=1385:4800 HOME=/ SHLVL=2 DEBUG=yes PCI_CLASS=28000 SEQNUM=315 _=/bin/env) Nov 23 19:40:22 neo default.hotplug[3870]: invoke /etc/hotplug/pci.agent () Nov 23 19:40:22 neo pci.agent[3870]: Setup prism54 for PCI slot 0000:02:00.0 Nov 23 19:40:22 neo kernel: ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 17 (level, low) -> IRQ 169 For some reason, the FC3 kernel doesn't invoke the hotplug system with "firmware" as argument. There is also difference between the two w.r.t to the sequence of invocations. I don't know why this should be the case. Any ideas?? Regards/Kedar. On Tue, 23 Nov 2004 11:54:43 -0800, Kedar Patankar <kedarnp@xxxxxxxxx> wrote: > Hi, > > I have an emachines M6805 laptop with WG511 cardbus wireless card. I > have an FC2 installation on this puppy and it works like a champ using > WEP. I am trying to install FC3 on this laptop and I can't get the > wireless card to work. I copied the f/w I am using under FC2 (which I > got from the XP driver) to /lib/firmware and inserted the line "alias > eth1 islpci_cb" to /etc/modprobe.conf. I also tried out the f/w > available from prism54.org. But the whole thing is dead - I don't see > any activity on the card - no blinking LEDs - nothing. > > Has anyone else managed to get WG511 working under FC3? Or is it an > x86_64 specific problem? I do remember people mentioning success with > WG511 on FC3-T3 on prism54.org > > Any ideas? > > Regards/Kedar. >
