those files, they are not in the good directory (i think) they should be in lib slash b43 but they are in lib slash firmware slash b43 (sorry keyboard problem), when I go into the filemanager, the b43 folder have a red x on it and I can’t do anything, I can’t copy the file, move or anyway.
The word REQUESTING made me think of that… my fault. I think i read too much stuff lately im just lost…!!!
then firmware is loaded… ?!
lo Interface doesn’t support scanning.
eth1 Interface doesn’t support scanning.
eth0 Interface doesn’t support scanning.
wmaster0 Interface doesn’t support scanning.
wlan0 No scan results
pan0 Interface doesn’t support scanning.
I did try whatever I found on the forum that seems logical to try. I also tried the sprom fix but problems occur.
./ssb-sprom -i sprom.old -P
Corrupt input data (crc: 0x60, expected: 0x00)
everything was working until that.
I don’t know what else to show… ive found something a file…
b43-phy0: Broadcom 4306 WLAN found
usb usb6: New USB device found, idVendor=1d6b, idProduct=0001
usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb6: Product: OHCI Host Controller
usb usb6: Manufacturer: Linux 2.6.27.21-0.1-pae ohci_hcd
usb usb6: SerialNumber: 0000:03:00.0
ohci_hcd 0000:03:00.1: enabling device (0000 -> 0002)
vendor=8086 device=2448
ohci_hcd 0000:03:00.1: PCI INT B -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
ohci_hcd 0000:03:00.1: setting latency timer to 64
ohci_hcd 0000:03:00.1: OHCI Host Controller
ohci_hcd 0000:03:00.1: new USB bus registered, assigned bus number 7
ohci_hcd 0000:03:00.1: irq 11, io mem 0xf8001000
phy0: Selected rate control algorithm ‘pid’
usb usb7: configuration #1 chosen from 1 choice
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 2 ports detected
Broadcom 43xx driver loaded Features: PMLR, Firmware-ID: FW13 ]
pci 0000:00:02.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
pci 0000:00:02.0: setting latency timer to 64
[drm] Initialized i915 1.6.0 20060119 on minor 0
pci 0000:00:02.1: setting latency timer to 64
[drm] Initialized i915 1.6.0 20060119 on minor 1
[drm:i915_getparam] ERROR Unknown parameter 5
[drm:i915_getparam] ERROR Unknown parameter 5
ADDRCONF(NETDEV_UP): eth0: link is not ready
input: b43-phy0 as /devices/virtual/input/input10
firmware: requesting b43/ucode5.fw
firmware: requesting b43/pcm5.fw
firmware: requesting b43/b0g0initvals5.fw
firmware: requesting b43/b0g0bsinitvals5.fw
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
ADDRCONF(NETDEV_UP): wlan0: link is not ready
I did skip some line in that, I think they were not usefull… I think everything related to b43 or phy0 or wlan is there…
Zaskar wrote:
> Akoellh;1986081 Wrote:
>> And what exactly makes you think this?
>>
>> If they were in the wrong directory, you would get an error message on
>> loading b43.
>
>
> The word REQUESTING made me think of that… my fault. I think i read
> too much stuff lately im just lost…!!!
>
> then firmware is loaded… ?!
YES, firmware is loaded - v410.2160, which is a good vintage.
> lo Interface doesn’t support scanning.
> eth1 Interface doesn’t support scanning.
> eth0 Interface doesn’t support scanning.
> wmaster0 Interface doesn’t support scanning.
> wlan0 No scan results
> pan0 Interface doesn’t support scanning.
Everything looks good. Did you scan as root? Scans as a general user are passive
the interface just listens. As root, the interface probes for AP’s.
Huh I don’t know if I did the command as root, I don’t know how to see if im root or user… Everything looks good except I can’t scan… it’s still in light gray, showing it doesn’t work
Maybe it’s just NOT ON, how I can see if my wireless is enabled
you need to have a root password; do you remember setting a root password when you set up linux; ( you should have both a USER password and a ROOT password; the ROOT allows you to install files etc)
the hope is:
the diagnostic script might help you fix the problem yourself
if not:
you can post back detailed information to the forum, so experts like Axel or Larry Finger can help you;
— Which type of your network connection should be tested?
— (1) Wired connection
— (2) Wireless connection (WLAN)
— Please answer with 1-2:2
— What’s the type of networktopology?
— (1) WLAN access point <—> LinuxClient
— (2) WLAN HW router <—> LinuxClient
— (3) WLAN access point <—> LinuxRouter <—> LinuxClient
— (4) WLAN HW router <—> LinuxRouter <—> LinuxClient
— Please answer with 1-4:1
— Analyzing system for common network configuration errors…
!!! CND0120E: Network card wlan0 has no IP address
!!! CND0380E: No WLANs detected on interface wlan0. Hardware and/or driver not configured properly
!!! CND0230W: IPV6 enabled
!!! CND0240E: knetworkmanager for network configuration enabled but network card configuration for wlan0,eth0 detected
!!! CND0360E: Wireless connection tested with an existing wired connection on interface eth1. Unplug the cable and execute the script again
— Collecting networkconfiguration information …
— Go to Fehlermeldungen/Errormessages | collectNWData.sh Fehlermeldungen to get more detailed instructions about the error/warning messages and how to fix the problems
— If you still don’t have success then post the contents of file collectNWData.txt in your favorite Linux forum. For an alternative read Webseiten für Text- und Bilderuploads/Websites for text and image uploads | collectNWData.sh
!!! CND0120E: Network card wlan0 has no IP address
!!! CND0380E: No WLANs detected on interface wlan0. Hardware and/or driver not configured properly
!!! CND0230W: IPV6 enabled !!! CND0240E: knetworkmanager for network configuration enabled but network card configuration for wlan0,eth0 detected
!!! CND0360E: Wireless connection tested with an existing wired connection on interface eth1. Unplug the cable and execute the script again
I did read all the error message on the script’s web site… those 4 errors… but yet I don,t really know what to do, i’ll try this afternoon when I,ll be awake.
I am nost definitely not a wireless expert; but when I copy and paste your latest script into a word processor, I cannot find the word “error” anywhere;
I suspect when one of the wireless gurus read it, they are going to say you are good to go; to configure;
!!! CND0120E: Network card wlan0 has no IP address
!!! CND0380E: No WLANs detected on interface wlan0. Hardware and/or driver not configured properly
!!! CND0230W: IPV6 enabled
!!! CND0240E: knetworkmanager for network configuration enabled but network card configuration for wlan0,eth0 detected
Those are the errors, when it finish by E it means error, W mean warning.
