LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices


Reply
  Search this Thread
Old 03-19-2008, 01:36 PM   #1
tomrue
LQ Newbie
 
Registered: Jan 2006
Location: New York State
Distribution: Fedora 8
Posts: 9

Rep: Reputation: 0
Wireless problem: Fedora 8 not seeing wlan0 using ndiswrapper


I recently set up Fedora8 to dual-boot on my Gateway laptop.
Everything seems to work fine, to the point that I have even
considered formatting the Windows partition for some extra Linux
space, except for wireless connectivity. I've googled this to death.
It seems to be a common problem, but one for which there is a
solution. Unfortunately, none of the suggestions that I've found have
worked for me. I don't know if this is because I've implemented them
incorrectly, or if my specs are different.

I've got ndiswrapper installed, but System-Config-Network is unable to
find it, coming back repeatedly with the same error, "ndiswrapper
device wlan0 does not seem to be present, delaying initialization."

I am relatively new to Fedora, but have run a FreeBSD web-server for a
couple of years, mostly from command line. I imagine that there is
a .conf file somewhere that needs tweaking, but I haven't been able to
find it.

Any suggestions on how to fix this would be much appreciated.

Here are some of my relevant notes (as well as some details that may
not be relevant). If you need further details, post here or e-mail me.
Thanks.

==

[ Broadcom 802.11g Network Adapter ]

Network Adapter Properties:
Network Adapter Broadcom 802.11g Network Adapter
Interface Type Ethernet
Hardware Address 00-90-4B-D8-40-8C
Connection Name Wireless Network Connection
Connection Speed 54 Mbps
MTU 1500 bytes
DHCP Lease Obtained 3/16/2008 9:30:13 PM
DHCP Lease Expires 3/17/2008 9:30:13 PM
Bytes Received 35176 (34.4 KB)
Bytes Sent 4597 (4.5 KB)

Network Adapter Addresses:
IP / Subnet Mask 192.168.1.101 / 255.255.255.0
Gateway 192.168.1.1
DHCP 192.168.1.1

Network Adapter Manufacturer:
Company Name Broadcom Corporation
Product Information broadcom.com/entnetgigmac.html
Driver Download broadcom.com/entnetgigmac.html
[ VIA Rhine II Fast Ethernet Adapter ]

Network Adapter Properties:
Network Adapter VIA Rhine II Fast Ethernet Adapter
Interface Type Ethernet
Hardware Address 00-03-25-14-CF-FE
Connection Name Local Area Connection
Connection Speed 100 Mbps
MTU 1500 bytes
DHCP Lease Obtained 3/16/2008 9:30:01 PM
DHCP Lease Expires 3/17/2008 9:30:01 PM
Bytes Received 39981 (39.0 KB)
Bytes Sent 11422 (11.2 KB)

Network Adapter Addresses:
IP / Subnet Mask 192.168.1.103 / 255.255.255.0
Gateway 192.168.1.1
DHCP 192.168.1.1

Network Adapter Manufacturer:
Company Name VIA Technologies, Inc.
Product Information via.com.tw/en/Networking/networking.jsp
Driver Download viaarena.com/?PageID=71#lan

/lib/modules/2.6.24.3-12.fc8/kernel/drivers/net/via-rhine.ko

==================================================

$ /sbin/lspci -vb

00:00.0 Host bridge: VIA Technologies, Inc. VT8385 [K8T800 AGP] Host
Bridge (rev 01)
Subsystem: VIA Technologies, Inc. VT8385 [K8T800 AGP] Host
Bridge
Flags: bus master, 66MHz, medium devsel, latency 8
Memory at e0000000 (32-bit, prefetchable)
Capabilities: <access denied>
Kernel driver in use: agpgart-amd64

00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/
K8T890 South] (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00002000-00002fff
Memory behind bridge: d0100000-d01fffff
Prefetchable memory behind bridge: d8000000-dfffffff
Capabilities: <access denied>

00:0a.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller
(rev 01)
Subsystem: Rioworks Unknown device 2032
Flags: bus master, medium devsel, latency 168, IRQ 255
Memory at ffe7f000 (32-bit, non-prefetchable)
Bus: primary=00, secondary=02, subordinate=05, sec-latency=176
Memory window 0: 50000000-53fff000 (prefetchable)
Memory window 1: 54000000-57fff000
I/O window 0: 00003000-000030ff
I/O window 1: 00003400-000034ff
16-bit legacy interface ports at 0001
Kernel driver in use: yenta_cardbus

00:0c.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
Wireless LAN Controller (rev 03)
Subsystem: Unknown device 17f9:0002
Flags: fast devsel, IRQ 9
Memory at d0000000 (32-bit, non-prefetchable)
Kernel modules: ssb

00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 80) (prog-if 00 [UHCI])
Subsystem: Rioworks Unknown device 2032
Flags: bus master, medium devsel, latency 64
I/O ports at 1c80
Capabilities: <access denied>
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd

00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 80) (prog-if 00 [UHCI])
Subsystem: Rioworks Unknown device 2032
Flags: bus master, medium devsel, latency 64
I/O ports at 1ca0
Capabilities: <access denied>
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd

00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 80) (prog-if 00 [UHCI])
Subsystem: Rioworks Unknown device 2032
Flags: bus master, medium devsel, latency 64
I/O ports at 1cc0
Capabilities: <access denied>
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd

00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-
if 20 [EHCI])
Subsystem: Rioworks Unknown device 2032
Flags: bus master, medium devsel, latency 64
Memory at d0002800 (32-bit, non-prefetchable)
Capabilities: <access denied>
Kernel driver in use: ehci_hcd
Kernel modules: ehci-hcd

00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
Subsystem: VIA Technologies, Inc. VT8235 ISA Bridge
Flags: bus master, stepping, medium devsel, latency 0
Capabilities: <access denied>
Kernel modules: i2c-viapro, via-ircc

00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/
VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP
PriP])
Subsystem: Rioworks Unknown device 2032
Flags: bus master, medium devsel, latency 64
I/O ports at 1ce0
Capabilities: <access denied>
Kernel driver in use: pata_via
Kernel modules: pata_via

00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/
8235/8237 AC97 Audio Controller (rev 50)
Subsystem: Rioworks Unknown device 2032
Flags: medium devsel, IRQ 10
I/O ports at 1000
Capabilities: <access denied>
Kernel driver in use: VIA 82xx Audio
Kernel modules: snd-via82xx

00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem
Controller (rev 80)
Subsystem: Rioworks Unknown device 2032
Flags: medium devsel, IRQ 10
I/O ports at 1400
Capabilities: <access denied>
Kernel driver in use: VIA 82xx Modem
Kernel modules: snd-via82xx-modem

00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II]
(rev 74)
Subsystem: VIA Technologies, Inc. VT6102 [Rhine II] Embeded
Ethernet Controller on VT8235
Flags: bus master, medium devsel, latency 64, IRQ 9
I/O ports at 1800
Memory at d0002c00 (32-bit, non-prefetchable)
Capabilities: <access denied>
Kernel driver in use: via-rhine
Kernel modules: via-rhine

00:13.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host
Controller (rev 80) (prog-if 10 [OHCI])
Subsystem: VIA Technologies, Inc. IEEE 1394 Host Controller
Flags: bus master, medium devsel, latency 64, IRQ 10
Memory at d0002000 (32-bit, non-prefetchable)
I/O ports at 1c00
Capabilities: <access denied>
Kernel driver in use: firewire_ohci
Kernel modules: firewire-ohci

00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/
Opteron] HyperTransport Technology Configuration
Flags: fast devsel
Capabilities: <access denied>

00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/
Opteron] Address Map
Flags: fast devsel

00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/
Opteron] DRAM Controller
Flags: fast devsel

00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/
Opteron] Miscellaneous Control
Flags: fast devsel
Kernel driver in use: k8temp
Kernel modules: k8temp

01:00.0 VGA compatible controller: ATI Technologies Inc RV350
[Mobility Radeon 9600 M10] (prog-if 00 [VGA controller])
Subsystem: Rioworks Unknown device 2032
Flags: bus master, fast Back2Back, 66MHz, medium devsel,
latency 66, IRQ 9
Memory at d8000000 (32-bit, prefetchable)
I/O ports at 2000
Memory at d0100000 (32-bit, non-prefetchable)
Capabilities: <access denied>
Kernel modules: radeonfb

==================================================

FROM DMESG:

b43-phy0: Broadcom 4306 WLAN found

b43-phy0 debug: Found PHY: Analog 2, Type 2, Revision 2
b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
phy0: Selected rate control algorithm 'pid'
Broadcom 43xx driver loaded [ Features: PMLR, Firmware-ID: FW13 ]
b43-phy0: Broadcom 4306 WLAN found
b43-phy0 debug: Found PHY: Analog 2, Type 2, Revision 2
b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
phy0: Selected rate control algorithm 'pid'
Broadcom 43xx driver loaded [ Features: PMLR, Firmware-ID: FW13 ]

sudo b43-fwcutter -w /lib/firmware/b43/ <driver.sys>

linuxwireless.org/en/users/Drivers/b43#devicefirmware

b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found or load
failed.
b43-phy0 ERROR: You must go to linuxwireless.org/en/users/Drivers/b43#devicefirmware
and download the latest firmware (version 4).
input: b43-phy0 as /devices/virtual/input/input14
b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found or load
failed.

==
 
Old 03-19-2008, 02:48 PM   #2
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 420Reputation: 420Reputation: 420Reputation: 420Reputation: 420
Welcome to LQ!

It looks as if you have a conflict going on there. There is a native linux driver for Broadcom chipsets called b43 or b43legacy depending on your chipset, and Fedora definitely includes those drivers. The problem is that Fedora doesn't distribtute the firmware needed for those drivers to actually function (and neither does any other distro). And if the b43/b43legacy driver is loaded at the same time as ndiswrapper, you've got a conflict over the hardware. The Linux Wireless site has a good page detailing everything you need to do to get b43/b43legacy running. If you want to use ndiswrapper instead for some reason, you'll need to blacklist b43/b43legacy so it doesn't load.
 
Old 03-19-2008, 09:46 PM   #3
tomrue
LQ Newbie
 
Registered: Jan 2006
Location: New York State
Distribution: Fedora 8
Posts: 9

Original Poster
Rep: Reputation: 0
Thanks for the reply. I did

$ yum erase ndiswrapper

and followed the instructions at http://linuxwireless.org/en/users/Drivers/b43 as suggested. (I followed these same steps, from this same page, a few days ago, too.) Still no luck tonight, after a second attempt.

I suspect I am configuring the network connection incorrectly?? It is unfamiliar to me and I haven't been able to figure it out.

I just posted some screen caps of my Network Configuration utility at http://tomrue.net/?q=wireless , if you could advise me. As you can see, the wireless connection claims it is "Active". But when I unplug the network cable, both connections (wireless and wired) go inactive. What am I doing wrong? Any suggestions?

Thanks again.

Tom
 
Old 03-20-2008, 07:31 AM   #4
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 420Reputation: 420Reputation: 420Reputation: 420Reputation: 420
Sorry, but the link you posted is just giving me a blank screen.

However, there are a few things that you can check to see what might be happening:

-Did the firmware files actually get copied to /lib/firmware
-Do you see the card in the output of iwconfig?
- Do you see the card in the output of ifconfig?
(Actually posting both of the above could be useful)

- Is b43 complaining about anything in the log files (/var/log/syslog, /var/log/messages, dmesg)

Quote:
00:0c.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
Wireless LAN Controller (rev 03)
I'm not entirely sure, but based on this output, you may need to use b43legacy instead of b43 (and it will require different firmware, but the linuxwireless site explains how to do it as well). You might give it a go and see if it works. In theory, the kernel should be selecting the correct driver if both are present, but then again, it might not.
 
Old 03-20-2008, 09:29 AM   #5
tomrue
LQ Newbie
 
Registered: Jan 2006
Location: New York State
Distribution: Fedora 8
Posts: 9

Original Poster
Rep: Reputation: 0
Hmm, I wonder about the blank screen. It comes up fine for me in Firefox on Fedora 8, as well as in MSIE on that other OS.

Here are direct links to the images:
http://tomrue.net/files/images/Screenshot-0.png
http://tomrue.net/files/images/Screenshot-1.png
http://tomrue.net/files/images/Screenshot-2.png
http://tomrue.net/files/images/Screenshot-3.png

I was getting "Command Not Found" from iwconfig and then added /sbin/ to the path with
$ export PATH=/sbin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/home/tom/bin/
and now get:
[root@aphrodite tom]# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
and:


[root@aphrodite tom]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:03:25:14:CF:FE
inet addr:192.168.1.103 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::203:25ff:fe14:cffe/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1481 errors:0 dropped:0 overruns:0 frame:0
TX packets:1365 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:767049 (749.0 KiB) TX bytes:169555 (165.5 KiB)
Interrupt:18 Base address:0xcc00

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6083 errors:0 dropped:0 overruns:0 frame:0
TX packets:6083 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3285501 (3.1 MiB) TX bytes:3285501 (3.1 MiB)
In /var/log/messages, I see this (not sure what it means, but it doesn't mention b43):
[root@aphrodite log]# tail messages
Mar 20 10:04:06 aphrodite setroubleshoot: SELinux is preventing consoletype (consoletype_t) "getattr" to pipe (initrc_t). For complete SELinux messages. run sealert -l 8c497512-5ff7-40b2-8610-cfcdddaa8679
Mar 20 10:04:06 aphrodite setroubleshoot: SELinux is preventing consoletype (consoletype_t) "ioctl" to pipe (initrc_t). For complete SELinux messages. run sealert -l a550cf3c-b721-4a2a-a353-607693f9e471
Mar 20 10:04:06 aphrodite setroubleshoot: SELinux is preventing consoletype (consoletype_t) "getattr" to pipe (initrc_t). For complete SELinux messages. run sealert -l 8c497512-5ff7-40b2-8610-cfcdddaa8679
Mar 20 10:04:06 aphrodite setroubleshoot: SELinux is preventing consoletype (consoletype_t) "ioctl" to pipe (initrc_t). For complete SELinux messages. run sealert -l a550cf3c-b721-4a2a-a353-607693f9e471
Mar 20 10:05:24 aphrodite gdl_fs_crawler: E 03-20 10:05:23 5170 gdl_fs_crawler sconstest.cc:38] not in a valid building path. can not find the root dir.
Mar 20 10:05:54 aphrodite gdl_fs_crawler: E 03-20 10:05:53 5234 gdl_fs_crawler sconstest.cc:38] not in a valid building path. can not find the root dir.
Mar 20 10:06:22 aphrodite gdl_fs_crawler: E 03-20 10:06:21 5276 gdl_fs_crawler sconstest.cc:38] not in a valid building path. can not find the root dir.
Mar 20 10:06:51 aphrodite gdl_fs_crawler: E 03-20 10:06:50 5321 gdl_fs_crawler sconstest.cc:38] not in a valid building path. can not find the root dir.
Mar 20 10:07:24 aphrodite gdl_fs_crawler: E 03-20 10:07:23 5367 gdl_fs_crawler sconstest.cc:38] not in a valid building path. can not find the root dir.
Mar 20 10:07:54 aphrodite gdl_fs_crawler: E 03-20 10:07:53 5417 gdl_fs_crawler sconstest.cc:38] not in a valid building path. can not find the root dir.
From "/var/log/syslog" it tells me that the file doesn't exist. However, "/var/log/boot.log" says repeatedly (again with no "b43" complaints):
[root@aphrodite log]# tail boot.log
Mar 19 20:48:15 aphrodite NET[8556]: /sbin/dhclient-script : updated /etc/resolv.conf
Mar 19 21:54:45 aphrodite NET[14288]: /sbin/dhclient-script : updated /etc/resolv.conf
Mar 19 21:55:15 aphrodite NET[14466]: /sbin/dhclient-script : updated /etc/resolv.conf
Mar 19 21:55:54 aphrodite NET[14769]: /sbin/dhclient-script : updated /etc/resolv.conf
Mar 19 21:58:54 aphrodite NET[15248]: /sbin/dhclient-script : updated /etc/resolv.conf
Mar 19 21:59:30 aphrodite NET[15554]: /sbin/dhclient-script : updated /etc/resolv.conf
Mar 19 22:01:31 aphrodite NET[15902]: /sbin/dhclient-script : updated /etc/resolv.conf
Mar 19 22:02:07 aphrodite NET[16169]: /sbin/dhclient-script : updated /etc/resolv.conf
Mar 20 09:49:12 aphrodite NET[2835]: /sbin/dhclient-script : updated /etc/resolv.conf
Mar 20 10:04:04 aphrodite NET[5025]: /sbin/dhclient-script : updated /etc/resolv.conf
This is the contents of /lib/firmware:

atmel_at76c502_3com.bin
atmel_at76c502_3com-wpa.bin
atmel_at76c502.bin
atmel_at76c502d.bin
atmel_at76c502d-wpa.bin
atmel_at76c502e.bin
atmel_at76c502e-wpa.bin
atmel_at76c502-wpa.bin
atmel_at76c503-i3861.bin
atmel_at76c503-i3863.bin
atmel_at76c503-rfmd-acc.bin
atmel_at76c503-rfmd.bin
atmel_at76c504_2958-wpa.bin
atmel_at76c504a_2958-wpa.bin
atmel_at76c504.bin
atmel_at76c504c-wpa.bin
atmel_at76c505a-rfmd2958.bin
atmel_at76c505-rfmd2958.bin
atmel_at76c505-rfmd.bin
atmel_at76c506.bin
atmel_at76c506-wpa.bin
b43
b43legacy
bcm43xx_initval01.fw
bcm43xx_initval02.fw
bcm43xx_initval03.fw
bcm43xx_initval04.fw
bcm43xx_initval05.fw
bcm43xx_initval06.fw
bcm43xx_initval07.fw
bcm43xx_initval08.fw
bcm43xx_initval09.fw
bcm43xx_initval10.fw
bcm43xx_microcode11.fw
bcm43xx_microcode2.fw
bcm43xx_microcode4.fw
bcm43xx_microcode5.fw
bcm43xx_pcm4.fw
bcm43xx_pcm5.fw
broadcom-wl-4.80.53.0
broadcom-wl-4.80.53.0.tar.bz2
broadcom-wl-4.80.53.0.tar.bz2.1
COPYING.atmel-firmware
COPYRIGHT
COPYRIGHT-usb.atmel-firmware
ipw2100-1.3.fw
ipw2100-1.3-i.fw
ipw2100-1.3-p.fw
ipw2200-bss.fw
ipw2200-ibss.fw
ipw2200-sniffer.fw
ipw-2.4-boot.fw
ipw-2.4-bss.fw
ipw-2.4-bss_ucode.fw
ipw-2.4-ibss.fw
ipw-2.4-ibss_ucode.fw
ipw-2.4-sniffer.fw
ipw-2.4-sniffer_ucode.fw
iwlwifi-3945-1.ucode
iwlwifi-3945.ucode
iwlwifi-4965-1.ucode
iwlwifi-4965.ucode
LICENSE.ipw2100
LICENSE.ipw2200
ql2100_fw.bin
ql2200_fw.bin
ql2300_fw.bin
ql2322_fw.bin
ql2400_fw.bin
README
README.atmel-firmware
README-usb.atmel-firmware
rt2561.bin
rt2561s.bin
rt2661.bin
rt73.bin
zd1211

Last edited by tomrue; 03-20-2008 at 09:32 AM.
 
Old 03-20-2008, 01:59 PM   #6
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 420Reputation: 420Reputation: 420Reputation: 420Reputation: 420
There are a couple of things that bother me out of that. First is the lack of a wireless device in the iwconfig output. That suggests that either the driver isn't loaded or the wrong driver is loaded. Check the output of lsmod and see if b43 is there. If it isn't, try loading it:

modprobe b43

And then check iwconfig to see if there is a wireless card. However, if b43 is in the lsmod output, that suggests it doesn't work with your card and you need to try b43legacy. In that case you'll first have to remove b43 from memory:

modprobe -r b43
modprobe b43legacy


Again, after doing that check if you have a wireless device in iwconfig. I can't tell from your /lib/firmware if both b43 and b43legacy firmware files are there. It kind of looks that way, but if you didn't install them, you might need to.

The other thing that disturbs me is the first screenshot you posted. It looks as if eth0 is set up to be both a wired and a wireless device and that just doesn't sound right to me. It also looks as if your wired card (the VIA) isn't represented at all as active. It certainly is present on the second screenshot as eth1. I wonder if you don't have some sort of odd conflict going on. It might be worthwhile redoing this so that there is only one eth0 and one eth1, with one being wireless and the other being wired (it won't matter if the wireless is eth0 or eth1). The fact that eth0 shows up in ifconfig with a valid IP address suggests that it is actually the wired card, not the wireless one.

Last edited by Hangdog42; 03-20-2008 at 02:00 PM.
 
Old 03-20-2008, 04:13 PM   #7
tomrue
LQ Newbie
 
Registered: Jan 2006
Location: New York State
Distribution: Fedora 8
Posts: 9

Original Poster
Rep: Reputation: 0
Okay, I've updated the screen caps:

http://tomrue.net/files/images/Screenshot-0.png
http://tomrue.net/files/images/Screenshot-1.png
http://tomrue.net/files/images/Screenshot-2.png
http://tomrue.net/files/images/Screenshot-3.png

and these settings, I think, look better.

I haven't been able to determine the reason, but modprobe isn't working for me. It's present in /sbin/, and /sbin/ is in my path, but it comes back with "bash: modprobe: command not found". I read somewhere that modprobe needs to be set in the environment, but I haven't been able to find the command line to accomplish that. Is that correct?

Currently, when I deactivate eth0 and attempt to activate wlan0, I get:
Determining IP information for eth0...dhclient(6880) is already running - exiting.
This version of ISC DHCP is based on the release available
on ftp.isc.org. Features have been added and other changes
have been made to the base software release in order to make
it work better with this distribution.
Please report for this software via the Red Hat Bugzilla site: http://bugzilla.redhat.com
exiting.
failed.
Oh, and yes, the legacy firmware is in /lib/firmware, along with the other.

This one problem seems has been the only serious difficulty I've had with Fedora 8 thus far. I do appreciate your help.

Thanks.

Last edited by tomrue; 03-20-2008 at 04:14 PM.
 
Old 03-20-2008, 06:05 PM   #8
bbfuller
Member
 
Registered: Dec 2007
Location: UK
Distribution: Mageia, MX, Manjaro, OpenSuSE, PCLinuxOS
Posts: 214

Rep: Reputation: 35
Hello tomrue

You've gone a long way down the track here. I can tell you though that you can get the broadcom 4306 working with the b43 driver because mine does.

I also have a broadcom 4318 running using the same driver and I would like to offer you a few thoughts.

My 4318 worked directly I had cut the correct b43 firmware after install back in October. My 4306 has only started working though since the updated Fedora kernel and b43 parts that were released some time between then and January. I didn't try my 4306 for every update so I can only tell you that it was about then it happened.

My suggestion is that if you can get a wired connection to the machine, and if you haven't already, get it updated.

Mine doesn't use the legacy driver.

It appears to make a difference which firmware you cut depending on which level of updates you have.

The original Fedora fwcutter used the broadcom-wl-4.80.53.0.tar.bz2 package and the wl_apsta.o file within the kmod directory.

The new Fedora fwcutter uses the broadcom-wl-4.150.10.5.tar.bz2 package and the wl_apsta_mimo.o file within the driver directory.

Though the newer of the two b43 drivers is happy with the previously cut firmware.

Your card probably won't appear in the Network application of the Gnome, System - Administration menu. Neither of my broadcoms do.

If it does then in the same application it should be highlighted and the Edit button on the toolbar clicked. It should be set so that "Activate device when computer starts" is not ticked and so that "Controlled by NetworkManager" is.

NetworkManager is probably on the top Gnome Panel in the notification area to the right. Depending on what you installed from it is not always running though.

If it is not running then Gnome Administration menu - System - Services will give you the opportunity to get it running and save the onfiguration so that it always runs.

If it is already running then it could explain your problem.

Fedora has those two methods of controlling a card. The Network Configuration that your screenshots show and NetworkManager. Unfortunately if they are both running then they conflict with each other.
 
Old 03-20-2008, 06:12 PM   #9
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 420Reputation: 420Reputation: 420Reputation: 420Reputation: 420
Quote:
I read somewhere that modprobe needs to be set in the environment, but I haven't been able to find the command line to accomplish that. Is that correct?
No, modprobe doesn't need any special environment settings, but you may need to be root to run it. You could also try specifying the full path on the command line in case there is something goofy about your PATH.

Quote:
Currently, when I deactivate eth0 and attempt to activate wlan0, I get:
To be honest, I have no idea what that warning is about. I'm guessing that it is a dhclient shutdown error, but it really isn't clear. Can you acually deactivate eth0? You could also try to bring eth0 down on the command line:

ifdown eth0
ifup wlan0
 
Old 03-20-2008, 06:27 PM   #10
tomrue
LQ Newbie
 
Registered: Jan 2006
Location: New York State
Distribution: Fedora 8
Posts: 9

Original Poster
Rep: Reputation: 0
I don't understand why it is that my PATH reverts to a state without /sbin/, which I added this morning. Is env set by a .conf file during the boot process?

For reasons unclear to me, files that (I believe) should be executable, such as ifdown or ifup, bring a "command not found" error -- even with the full path specified, as well as when I cd into /sbin/ itself and try invoking from there. I've tried as su, and as a regular user. I've even tried while logged in as root.

I'm really puzzled by this. As I said, I'm very pleased with Fedora. However, since this is a laptop I'm running it on, I hate to sacrifice its wireless functionality.

Thanks very much for your replies on this thread. It does seem like something for which there must be a solution, given the widespread positive reviews that I've read about Fedora.
 
Old 03-20-2008, 07:50 PM   #11
tomrue
LQ Newbie
 
Registered: Jan 2006
Location: New York State
Distribution: Fedora 8
Posts: 9

Original Poster
Rep: Reputation: 0
bbfuller:

Thanks for the encouraging description of your experience on what sounds like a similar system.

I have a working wired connection on the laptop. It is a fresh install of Fedora 8 and all updates that the system has told me about are installed. I only struggling with getting the wireless to work. Wired works fine -- faster, in fact, tha in

It appears that I have what you say is the older version, with wl_apsta_mimo.o in the kmod directory.

I do have the NetworkManager service running, in addition to what you see in the screenshots. In addition, I also have NetworkManagerDispatcher service running. Should I disable that?

I have unticked "Activate device when computer starts" and ticked "Controlled by NetworkManager", but it's still not working. I will try rebooting.

Tom
 
Old 03-21-2008, 05:49 AM   #12
bbfuller
Member
 
Registered: Dec 2007
Location: UK
Distribution: Mageia, MX, Manjaro, OpenSuSE, PCLinuxOS
Posts: 214

Rep: Reputation: 35
Hello tomrue

No whoops of joy so I'd suppose that didn't work either.

I can only say that of the people I've talked to about various broadcom wireless cards those who have mixed the methods (ndiswrapper and b43) have been the ones who have had the trouble.

You would think that uninstalling ndiswrapper would remove all of it's previous influence but I've not found that to be the case.

The reason I'm so confident about the 4306, in case I didn't say earlier, is that I did a complete reinstall on that machine yesterday and it's back working again. The system had acquired some rubbish from other experiments and I wanted to make some space on the disc to install Sabayon.

Given the ease with which Fedora can be installed, if you have the time, could I suggest you give that a try. Unless you've done a lot of other configuring of course.

The steps I would recommend after install are:

Update installation to newest by wired connection.

Acquire the broadcom-wl-4.150.10.5.tar.bz2 package and cut the wl_apsta_mimo.o file.

Start NetworkManager (if necessary) from Gnome System Menu - Administration - Services. Depending on which source you install from NM is not always automatically started.

Restart machine, go to Gnome System Menu - Administration - Network. If your wireless card is listed there then make sure it's not set to activate at start. If it was, set it not to. I would restart the machine again then. Otherwise, or afterwards, look at the top Gnome Panel in the Notification area to the right and see if you get the opportunity to control the card.
 
Old 03-21-2008, 07:23 AM   #13
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 420Reputation: 420Reputation: 420Reputation: 420Reputation: 420
Quote:
I don't understand why it is that my PATH reverts to a state without /sbin/, which I added this morning. Is env set by a .conf file during the boot process?
Usually the PATH is set in a couple of ways (although keep in mind I use Slackware which may be a touch different). You can globally set the PATH in using the /etc/profile file. This is generally not a good idea for a couple of reasons. First, you can't customize for each user (and this might open up security issues even on a single user machine) and second, upgrades to the system might overwrite your changes. The more conventional way is to set your path in your ~/.bash_profile file. That file is run when you log in (as opposed to .bashrc which runs whenever you open a console). Using .bash_profile is safe since system upgrade will never touch it and the changes are limited to that single user.
Quote:
For reasons unclear to me, files that (I believe) should be executable, such as ifdown or ifup, bring a "command not found" error -- even with the full path specified, as well as when I cd into /sbin/ itself and try invoking from there. I've tried as su, and as a regular user. I've even tried while logged in as root.
OK, I should have suggested this before, but given this I'm guessing that SELinux settings are causing a problem. I would turn off SELinux completely for now and see if that makes a difference.
 
Old 03-21-2008, 08:21 AM   #14
tomrue
LQ Newbie
 
Registered: Jan 2006
Location: New York State
Distribution: Fedora 8
Posts: 9

Original Poster
Rep: Reputation: 0
Hi bbfuller.

You're right: Mudville as yet has seen no joy. I'm hoping not to strike out. Last night I considered a reinstall, but didn't quite reach that point. Yes, I've done a fair amount of other configuring. But yum is so easy to use that it wouldn't be a big deal to put everything back (+ wireless, I hope).

Actually, the only other problem I've had (which I forgot to mention yesterday when I said this wireless issue was the only one I've encountered) was tweaking grub for dual boot. But I've done that before, and though it took a while, I pretty much knew where I was headed and eventually got it. This wireless thing has taken days and still isn't fixed.

I'm considering at least backing up my /var/log/.. tree; /boot/..; /home/..; and maybe some other files and folders, so I remember what problems I encountered on this first try, what apps I yum'd, and to save my data.

I think I saw a non-destructive option during initial setup. If I'm correct on that, how "non-destructive" is it really?

Any other precautions you'd suggest?

One final question, if you know the answer and have time to reply soon: How can I rsync (or something like it) my full Fedora partitions to a server on my internal LAN?

Ideally, I'd like to mirror what I have in uncompressed form -- not a tarball. If you're unsure, or can't reply quickly, that's okay. I appreciate the advice you and HangDog42 have offered on this thread. With all this experimentation, I'm getting a better feel for this distro -- which I'm finding does have some significant, if small, differences from FreeBSD. This forum has been a big help. Fortunately for me, I've been on vacation this week, so I've had the time. As long as I get F8 fully working (which I believe I will), I'll undoubtedly return to LQ again in the future.

Respecting backups, the system at issue here is a dual-booted Gateway laptop, currently containing F8 and WinXP, wired to a Linksys wireless router. Also on the LAN is a WinXP laptop (my wife's, who won't consider anything but an MS OS); a FreeBSD web-server situated across the room from where I sit, which most likely has enough free disc space to contain a full system Fedora backup -- at least temporarily; and a spare FreeBSD server with a small HD, connected to an external HD containing a full backup of the main BSD server. Also, I haven't tried using the DVD burner on this laptop under F8, but I believe it's working.

Thanks again for your help.

Tom


--
tomrue {AT} gmail {DOT} com
http://tomrue.net
 
Old 03-21-2008, 10:04 AM   #15
bbfuller
Member
 
Registered: Dec 2007
Location: UK
Distribution: Mageia, MX, Manjaro, OpenSuSE, PCLinuxOS
Posts: 214

Rep: Reputation: 35
Hello Tom,

Three questions there:

I'm not sure I'd want to try a non-destructive over-install if that were possible, my suggestion would be to be as destructive as possible so that you ae certain you've got rid of all possible previous attempts at wireless.

As to grub and dual boot. I've never had to tweak it for that. The machines I have dual booting I just leave all of the default options in place during the install and Grub sets itself up. The only machine I have to worry about is the one where I keep six different distributions that I like to keep an eye on. Most often the grub installer doesn't recognise other linux installations and then I have to add stanzas to it. What problem did you have with dual boot?

The path statement for your environment gets cobbled together from more than one source while you boot. If you wanted to add something to it for an individual user you could edit the file:

Code:
/home/<yourusername>/.bash_profile
you will see in there the code to take a pre-existing path statement and add to it before exporting it again as the users environment path.

I'd be wary of adding whole areas like sbin to it permanently. It's not there originally as a matter of security policy and by adding it you run the risk of compromising Linux's legendary security.

Rsync I use as well. I use it over samba for no other reason than that's the way I first got it working and I've never bothered to experiment further.

I just run it off a script and it copies the files in the specified directories to a specified directory on the remote machine. I've never bothered to try to use it to restore as the only times I replace the data are after a re-install when I've just picked the parts I want manually. Here is the script:

Code:
mount -t cifs //abc/backup /mnt -o username=root
rsync -av --delete /home/bbfuller /mnt
rsync -av --delete /root /mnt
rsync -av --delete /bin/abackup /mnt
rsync -av --delete /bin/phil /mnt
rsync -av --delete /bin/mysqlbackup /mnt
rsync -av --delete /bin/repocreate /mnt
umount /mnt
As you can see, I use it for roots and my home directories and then three scripts I keep in bin. Including the backup one itself which is 'abackup'
They all end up in the directory 'backup' on the remote machine 'abc'.

Hope that at least gives you some things to ponder on.

I'll be looking for progress reports or questions.

Bernard

Last edited by bbfuller; 03-21-2008 at 10:06 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Wireless wlan0/ndiswrapper problem Glj12 Linux - Wireless Networking 14 08-16-2006 12:19 AM
Wireless network problems, ndiswrapper installed will not create wlan0 jackuss_169 Linux - Wireless Networking 6 08-14-2006 11:29 AM
[Gentoo] Ndiswrapper Problem - Failed to configure wireless for wlan0 freek sanders Linux - Software 8 11-11-2005 02:12 AM
Wireless Linksys -G type loading with dhclient wlan0 after ndiswrapper is loaded but Wireless-G-DSL Linux - Hardware 1 04-01-2005 09:45 PM
Broadcom wireless with ndiswrapper: ifconfig wlan0 works; ifup wlan0 fails orangechicken Linux - Wireless Networking 2 04-17-2004 05:39 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking

All times are GMT -5. The time now is 05:30 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration