| Autor |
Nachricht |
|
|
Titel: Yet Another BCM43XX Wireless Issue
 Verfasst am: 22.09.2006, 07:32 Uhr
|
|
Anmeldung: 22. Sep 2006
Beiträge: 4
|
|
I thought I was the only one with a wireless issue regarding the BCM43XX chipsets. I am dead wrong. I was in the #Kanotix chat room, and they guys there helped me out wonderfully on my widescreen, and sound issues. The only issue I'm having now is with my wireless network card.
Here's what I've done so far...
Code:
alucardromero@AlucardLaptop:~$ ndiswrapper -l
Installed drivers:
bcmwl5 driver installed, hardware present
fwlan driver installed
I can't get rid of "fwlan", I have no idea why. Now, since it says "Hardware Present" I do this...
Code:
alucardromero@AlucardLaptop:~$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11b/g ESSID:"AlucardRomero" Nickname:"Broadcom 4318"
Mode:Managed Frequency=2.462 GHz Access Point: Invalid
Bit Rate=11 Mb/s Tx-Power=18 dBm
RTS thr:off Fragment thr:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Even though it says all of my network info, I can't access any network resources or the internet. I have the right driver according ndiswrapper, and I'm not far from the router (it sits behind the laptop at a questioning "11Mb/sec". The little green light on the front of the laptop lights up, but no cigar. I'm totally stumbled and confused, is there something I did wrong? I don't mind the 11Mb/sec since my internet only comes in at 384Kb/sec, so that I'm not particularly concerned with that.
Now, I must mention that I got it working ONCE. I had to reboot because of 915resolution and all that good stuff. All I'm aiming for is that the wireless card just works. If anybody needs any more info please, let me know.
Also, I just want to sincerely thank the guys that helped me out in the chat room, you guys are marvelous and deserve spicy hot women with wings (no pun intended...  )
Any help on this issue is greatly appreciated.
- Alucard Romero |
|
|
| |
|
|
|
 |
|
|
|
Titel: RE: Yet Another BCM43XX Wireless Issue
Verfasst am: 22.09.2006, 09:26 Uhr
|
|
Anmeldung: 15. Mai 2005
Beiträge: 191
Wohnort: Frankfurt am Main
|
|
Could you please post your /etc/network/interfaces and what's the result of "ifup eth1" ?
I've written down my experience with an BCM4306 here: http://kanotix.org/index.php?module=pnW ... dcom1450en
Good luck! |
_________________
Auch wenn das Leben auf der Erde teuer sein mag: eine jährliche Rundreise um die Sonne ist gratis mit dabei.
|
| |
|
|
|
|
|
|
|
Titel: RE: Yet Another BCM43XX Wireless Issue
Verfasst am: 22.09.2006, 11:32 Uhr
|
|
Anmeldung: 16. Aug 2004
Beiträge: 1905
|
|
| bcm43xx works rather well natively (without ndiswrapper) with kernel 2.6.18 (see kernel downloads) and works with 2.6.17 currently shiped on recent release candidates, all you need to do is installing bcm43xx-fwcutter and supply the needed formware from your windows drivers as we can't legally distribute it. |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: Yet Another BCM43XX Wireless Issue
Verfasst am: 22.09.2006, 14:54 Uhr
|
|
Anmeldung: 31. Jul 2004
Beiträge: 249
|
|
|
|
|
|
|
|
|
Titel:
Verfasst am: 22.09.2006, 23:41 Uhr
|
|
Anmeldung: 22. Sep 2006
Beiträge: 4
|
|
Kernel/Distro info...
Code:
root@AlucardLaptop:/home/alucardromero# uname -a
Linux AlucardLaptop 2.6.17.13-kanotix-2 #1 SMP PREEMPT Tue Sep 12 12:38:45 CEST 2006 i686 GNU/Linux
ifup eth1 rendered this...
Code:
root@AlucardLaptop:/home/alucardromero# ifup eth1
Error for wireless request "Set Encode" (8B2A) :
invalid argument "Penis".
Failed to bring up eth1.
Yes, my WEP key is Penis.
spiralnebelverdreher, I'm checking out that link right now.
I extracted the firmware in the same directory as the .inf file.
EDIT!!!
A new discovery.
I managed to get it working, but I don't know if this will last.
I used network card configuration, put in the wireless info, used DHCP broadcast, THEN I used "ifup eth1" and this is what is outputted...
Code:
root@AlucardLaptop:/home/alucardromero# ifup eth1
Internet Software Consortium DHCP Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.
Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html
Listening on LPF/eth1/00:14:a5:57:10:2f
Sending on LPF/eth1/00:14:a5:57:10:2f
Sending on Socket/fallback/fallback-net
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPOFFER from 192.168.2.1
DHCPREQUEST on eth1 to 255.255.255.255 port 67
DHCPACK from 192.168.2.1
bound to 192.168.2.3 -- renewal in 988514948 seconds.
sed: can't read /etc/ntp.conf: No such file or directory
Really really strange. ... or was this the way it was supposed to be done?[/code] |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 23.09.2006, 02:37 Uhr
|
|
Anmeldung: 08. Dez 2005
Beiträge: 300
|
|
| that seems to be the normal result of bringing up the interface. Can you access the net after bringing up the wireless? |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 23.09.2006, 06:10 Uhr
|
|
Anmeldung: 22. Sep 2006
Beiträge: 4
|
|
Yep, I can access it. Awesome stuff.
Thanks for the help guys. I really appreciate it. |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 23.09.2006, 16:13 Uhr
|
|
Anmeldung: 08. Dez 2005
Beiträge: 300
|
|
|
AlucardRomero hat folgendes geschrieben::
Yep, I can access it. Awesome stuff.
Thanks for the help guys. I really appreciate it.
Great..happy surfing using your wireless connection  |
|
|
| |
|
|
|
|
|
|
|
Titel:
Verfasst am: 08.10.2006, 22:20 Uhr
|
|
Anmeldung: 22. Sep 2006
Beiträge: 4
|
|
Okay, I'm back with a little issue.
When I start up, I have to type "ifup eth1" twice. The first time it doesn't catch anything but it enables the interface (the little green light lights up). But the second time is usually when it actually connects.
Is there an option (or a way) that I can be connected to the net upon boot rather than just an activated interface?
EDIT: Well, I tried a somewhat quicker way. I use "ifconfig eth1 up" and then "ifup eth1" and it connects. A bit quicker than waiting for a failed DHCP error, but I know there has to be a way where I'm connected to whatever network I have configured upon boot. |
|
|
| |
|
|
|
|
|
|
|
Titel: Broadcom
Verfasst am: 10.10.2006, 19:29 Uhr
|
|
Anmeldung: 22. Mar 2006
Beiträge: 82
Wohnort: dayton, oh usa
|
|
Briefly, if you have a newer kernel, you can get the native driver working
1) Install bcm43xx-fwcutter
2) Run it against your bcmwl5.sys (or similar name) file from Windows
3) If still having problems, blacklist ndiswrapper
If you want to use ndiswrapper -
1) Add
blacklist bcm43xx
to /etc/modprobe.d/blacklist (as root)
2) Put all of the Windows drivers (.inf and .sys) in a linux folder
3) Navigate to that folder and
ndiswrapper -i bcmwl5.inf (or similar name)
ndiswrapper -m
reboot
set up in knxcc
4) Other possible problems -- make sure you are using correct drivers, and using 32-bit drivers for 32-bit install
64-bit drivers for 64-bit install
5) If it still doesn't work
ndiswrapper -l
ndiswrapper -e to remove all other drivers (if any others are installed)
good driver should show driver present, hardware present
ndiswrapper nearly always sets up connection on wlan0
Mike
Check on http://www.ubuntuforums.org
Search "dapper broadcom native howto" or
"dapper broadcom ndiswrapper howto" |
|
|
| |
|
|
|
|
|
|
|
Titel: Re: Broadcom
Verfasst am: 11.10.2006, 08:25 Uhr
|
|
Anmeldung: 18. Jul 2005
Beiträge: 293
Wohnort: EST US
|
|
|
mdmarmer hat folgendes geschrieben::
4) Other possible problems -- make sure you are using correct drivers, and using 32-bit drivers for 32-bit install
64-bit drivers for 64-bit install
That's exactly my problem. I can't find the 32-bit driver, but the 64-bit one.
I've tried the 2005-04-64 liveCD (and fromiso cheat) but it freezes a new HP Pavilion dv6000z. My guess is I have to wait for 2006-01-64 |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: Re: Broadcom
Verfasst am: 11.10.2006, 12:54 Uhr
|
|
Anmeldung: 22. Mar 2006
Beiträge: 82
Wohnort: dayton, oh usa
|
|
|
|
|
|
|
|
|
Titel: Re: RE: Re: Broadcom
Verfasst am: 12.10.2006, 03:40 Uhr
|
|
Anmeldung: 18. Jul 2005
Beiträge: 293
Wohnort: EST US
|
|
Thank you, mdmarmer. I think the second link will work for me.
mdmarmer hat folgendes geschrieben::
You can also use Kanotix-64 lite from Dec. 2005 and upgrade with h2's script
Yeah, I've tried to boot it with every single option on Grub (acpi=on/off no/dma, etc). KDE starts up fine but it freeze with a few clicks you make. I've booted it with cheat 3. It fisnish booting, it gives me the prompt and after a few commands (once it didn't even let me finish to type a command) and a loud beep sounds. I have to press the power bottom to turn it off (not even the SysRq sequence would reboot it) |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: Re: RE: Re: Broadcom
Verfasst am: 12.10.2006, 15:50 Uhr
|
|
Anmeldung: 22. Mar 2006
Beiträge: 82
Wohnort: dayton, oh usa
|
|
If you have problems booting a BIOS upgrade may help -- HP site probably has one
In my experience the cheatcode that helps is noapic
or
noapic nolapic
Mike |
|
|
| |
|
|
|
|
|
|
|
Titel: Re: RE: Re: RE: Re: Broadcom
Verfasst am: 12.10.2006, 20:31 Uhr
|
|
Anmeldung: 18. Jul 2005
Beiträge: 293
Wohnort: EST US
|
|
|
mdmarmer hat folgendes geschrieben::
noapic nolapic
never tried nolapic. I'll let you know what happends |
|
|
| |
|
|
|
|
|
|
|
Titel: RE: Re: RE: Re: RE: Re: Broadcom
Verfasst am: 12.10.2006, 20:41 Uhr
|
|
Anmeldung: 16. Aug 2004
Beiträge: 1905
|
|
| Regarding bcm43xx kernel >= 2.6.18.1-rc1 is to be preferred and might fix random freezes. |
|
|
| |
|
|
|
|
|
|
