Thanks for all the tips. Roky, sorry about the water damage....I am married too, totally understand. Going to reinstall and try again. Any tips for when I do that, gonna keep my scripts. Why do I need to update the Debian keyring evertime I reinstall the OS?
the ISO image that I have is"antiX-M8.5-486, squeeze/sid......testing/unstable. Is there a stable version? Is this one of my problems with dist upgrade?
topic title: Wifi with a Broadcom 4306 on HP Pavillion 5202
-
Posts: 20
- Joined: 05 Apr 2011
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#17
You are better off downloading the antiX-M11-686 version. Though it is in testing, it has minor bugs that 99% of users won't notice.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.mepisimo.com/antix/Released/"
linktext was:"http://www.mepisimo.com/antix/Released/"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.mepisimo.com/antix/Released/"
linktext was:"http://www.mepisimo.com/antix/Released/"
====================================
-
Posts: 4,164
- Joined: 20 Feb 2009
#18
apt-get dist-upgrade in 8.5 currently pulls in tons of upgraded libraries compared to AntiX 11 which is currently up to date with Debian Testing. Probably why you are stumbling through dist-upgrade. So go with Antis recommendation and go with AntiX 11. I would do a reinstall on my EEEPCs except for the fact I have been tweaking the crap out of them and everything is working good and I keep em current as a rolling release. So I am sticking with 8.5 for now because it was a hard road to keep my limited drive space from filling to capacity, editing fstab on my EEEPC 900 plus moving /home to secondary 16gig ssd drive.
I do however have AntiX 11 (a Beta and a RC1) running on 2 of my other boxes and it has been pretty much painless. Less download for dist-upgrade for example.
Later when time permits, I will be doing a reinstall (if I ever find the time).
If I was just starting out though. I would go with AntiX 11.
I've been running 8.5 on my EEEPCs for a long time now. I can tell you there is a lot of mileage between AntiX 8.5 and AntiX 11 (because I run both).Is this one of my problems with dist upgrade?
apt-get dist-upgrade in 8.5 currently pulls in tons of upgraded libraries compared to AntiX 11 which is currently up to date with Debian Testing. Probably why you are stumbling through dist-upgrade. So go with Antis recommendation and go with AntiX 11. I would do a reinstall on my EEEPCs except for the fact I have been tweaking the crap out of them and everything is working good and I keep em current as a rolling release. So I am sticking with 8.5 for now because it was a hard road to keep my limited drive space from filling to capacity, editing fstab on my EEEPC 900 plus moving /home to secondary 16gig ssd drive.
I do however have AntiX 11 (a Beta and a RC1) running on 2 of my other boxes and it has been pretty much painless. Less download for dist-upgrade for example.
Later when time permits, I will be doing a reinstall (if I ever find the time).
If I was just starting out though. I would go with AntiX 11.
-
Posts: 20
- Joined: 05 Apr 2011
#19
Thanks anti. I just installed the newer version and it looks nice. Everything seems to work, but, the wifi. The computer recognizes the card and shows the driver (right outta the box __{{emoticon}}__ ). Went to connect to Iceape and nothing. Then it says that I can't get an IP address. I am guessing that would be at router issue then?
-
Posts: 20
- Joined: 05 Apr 2011
#20
New problem in my quest for wireless internet on my laptop. The newest version of Antix is great. Now I have to get my home network when I scan.....I know that there are about 5-8 wireless signals around me, when does ceni no see any of them? I have the driver and Antix recognizes all the harware. When I try retilt, it wont load, saying" cant find channel/frequency code -22".Someone please help, I am going nuts trying to make this laptop a practical tool.
-
Posts: 4,164
- Joined: 20 Feb 2009
#21
Open terminal and post contents of
and
and also
post each output separately and use the code tags so I don't have to clean up the post. I will be grouting tile today so may be awhile before I can look at outputs.
Code: Select all
ifconfig -a
Code: Select all
su -c"hwinfo --wlan"
Code: Select all
su -c"hwinfo --netcard"
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#22
You might need to reinstall the firmware.
Code: Select all
apt-get update && apt-get install firmware-b43-installer
-
Posts: 20
- Joined: 05 Apr 2011
#23
Rok-I will post results tonight when I get home from school.
Anti- I already have b43cutter installed....but I will see if it helps
Anti- I already have b43cutter installed....but I will see if it helps
-
Posts: 20
- Joined: 05 Apr 2011
#24
ifconfig -a
su -c"hwinfo --wlan"
su -c"hwinfo --netcard"
thanks Rok
Code: Select all
eth0 Link encap:Ethernet HWaddr 00:02:3f:25:54:a7
inet addr:192.168.15.3 Bcast:192.168.15.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1749 errors:0 dropped:0 overruns:0 frame:0
TX packets:2095 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:816405 (797.2 KiB) TX bytes:585221 (571.5 KiB)
Interrupt:19 Base address:0xa000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:100 (100.0 B) TX bytes:100 (100.0 B)
wlan0 Link encap:Ethernet HWaddr 00:90:4b:55:9a:94
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Code: Select all
12: PCI 202.0: 0282 WLAN controller
[Created at pci.318]
UDI: /org/freedesktop/Hal/devices/pci_14e4_4320
Unique ID: y9sn.0pBc6W7rE27
Parent ID: qscc.S+4MMSCCLf5
SysFS ID: /devices/pci0000:00/0000:00:14.4/0000:02:02.0
SysFS BusID: 0000:02:02.0
Hardware Class: network
Model:"Hewlett-Packard Company Broadcom 802.11b/g WLAN"
Vendor: pci 0x14e4"Broadcom"
Device: pci 0x4320"BCM4306 802.11b/g Wireless LAN Controller"
SubVendor: pci 0x103c"Hewlett-Packard Company"
SubDevice: pci 0x12f4"Broadcom 802.11b/g WLAN"
Revision: 0x03
Driver:"b43-pci-bridge"
Driver Modules:"ssb"
Device File: wlan0
Features: WLAN
Memory Range: 0xe8200000-0xe8201fff (rw,non-prefetchable)
IRQ: 18 (no events)
HW Address: 00:90:4b:55:9a:94
Link detected: no
WLAN channels: 1 2 3 4 5 6 7 8 9 10 11
WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462
WLAN encryption modes: WEP40 WEP104 TKIP CCMP
WLAN authentication modes: open sharedkey wpa-psk wpa-eap
Module Alias:"pci:v000014E4d00004320sv0000103Csd000012F4bc02sc80i00"
Driver Info #0:
Driver Status: ssb is active
Driver Activation Cmd:"modprobe ssb"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #8 (PCI bridge)
Code: Select all
12: PCI 202.0: 0282 WLAN controller
[Created at pci.318]
UDI: /org/freedesktop/Hal/devices/pci_14e4_4320
Unique ID: y9sn.0pBc6W7rE27
Parent ID: qscc.S+4MMSCCLf5
SysFS ID: /devices/pci0000:00/0000:00:14.4/0000:02:02.0
SysFS BusID: 0000:02:02.0
Hardware Class: network
Model:"Hewlett-Packard Company Broadcom 802.11b/g WLAN"
Vendor: pci 0x14e4"Broadcom"
Device: pci 0x4320"BCM4306 802.11b/g Wireless LAN Controller"
SubVendor: pci 0x103c"Hewlett-Packard Company"
SubDevice: pci 0x12f4"Broadcom 802.11b/g WLAN"
Revision: 0x03
Driver:"b43-pci-bridge"
Driver Modules:"ssb"
Device File: wlan0
Features: WLAN
Memory Range: 0xe8200000-0xe8201fff (rw,non-prefetchable)
IRQ: 18 (no events)
HW Address: 00:90:4b:55:9a:94
Link detected: no
WLAN channels: 1 2 3 4 5 6 7 8 9 10 11
WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462
WLAN encryption modes: WEP40 WEP104 TKIP CCMP
WLAN authentication modes: open sharedkey wpa-psk wpa-eap
Module Alias:"pci:v000014E4d00004320sv0000103Csd000012F4bc02sc80i00"
Driver Info #0:
Driver Status: ssb is active
Driver Activation Cmd:"modprobe ssb"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #8 (PCI bridge)
root@antiX1:/home/zachary# ^C
root@antiX1:/home/zachary# su -c"hwinfo --netcard"
20: PCI 202.0: 0282 WLAN controller
[Created at pci.318]
UDI: /org/freedesktop/Hal/devices/pci_14e4_4320
Unique ID: y9sn.0pBc6W7rE27
Parent ID: qscc.S+4MMSCCLf5
SysFS ID: /devices/pci0000:00/0000:00:14.4/0000:02:02.0
SysFS BusID: 0000:02:02.0
Hardware Class: network
Model:"Hewlett-Packard Company Broadcom 802.11b/g WLAN"
Vendor: pci 0x14e4"Broadcom"
Device: pci 0x4320"BCM4306 802.11b/g Wireless LAN Controller"
SubVendor: pci 0x103c"Hewlett-Packard Company"
SubDevice: pci 0x12f4"Broadcom 802.11b/g WLAN"
Revision: 0x03
Driver:"b43-pci-bridge"
Driver Modules:"ssb"
Device File: wlan0
Features: WLAN
Memory Range: 0xe8200000-0xe8201fff (rw,non-prefetchable)
IRQ: 18 (433 events)
HW Address: 00:90:4b:55:9a:94
Link detected: no
WLAN channels: 1 2 3 4 5 6 7 8 9 10 11
WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462
WLAN encryption modes: WEP40 WEP104 TKIP CCMP
WLAN authentication modes: open sharedkey wpa-psk wpa-eap
Module Alias:"pci:v000014E4d00004320sv0000103Csd000012F4bc02sc80i00"
Driver Info #0:
Driver Status: ssb is active
Driver Activation Cmd:"modprobe ssb"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #16 (PCI bridge)
21: PCI 203.0: 0200 Ethernet controller
[Created at pci.318]
UDI: /org/freedesktop/Hal/devices/pci_10ec_8139
Unique ID: rBUF.hFfOY6n6P69
Parent ID: qscc.S+4MMSCCLf5
SysFS ID: /devices/pci0000:00/0000:00:14.4/0000:02:03.0
SysFS BusID: 0000:02:03.0
Hardware Class: network
Model:"Realtek RTL-8139/8139C/8139C+"
Vendor: pci 0x10ec"Realtek Semiconductor Co., Ltd."
Device: pci 0x8139"RTL-8139/8139C/8139C+"
SubVendor: pci 0x103c"Hewlett-Packard Company"
SubDevice: pci 0x006b
Revision: 0x10
Driver:"8139too"
Driver Modules:"8139too"
Device File: eth0
I/O Ports: 0xa000-0xafff (rw)
Memory Range: 0xe8204000-0xe82040ff (rw,non-prefetchable)
IRQ: 19 (3856 events)
HW Address: 00:02:3f:25:54:a7
Link detected: yes
Module Alias:"pci:v000010ECd00008139sv0000103Csd0000006Bbc02sc00i00"
Driver Info #0:
Driver Status: 8139too is active
Driver Activation Cmd:"modprobe 8139too"
Driver Info #1:
Driver Status: 8139cp is active
Driver Activation Cmd:"modprobe 8139cp"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #16 (PCI bridge)
-
Posts: 20
zbrown1029 - Joined: 05 Apr 2011
#25
anti- I did what you asked. It said that"firmware-b43-installer is already the newest version."
-
Posts: 516
- Site Admin
- Joined: 01 Oct 2007
#26
zbrown1029,
Will you post the results of the following from terminal as a user
lspci -nn
you might want to try the following
comment out these lines: in /etc/modprobe.d/b43.conf as root. (to comment out put a # in front of them)
ssb true
b43 true
then as root:
modprobe ssb && modprobe b43
then restart ceni.
and see if you get the wireless going
cheers,
ohh
Will you post the results of the following from terminal as a user
lspci -nn
you might want to try the following
comment out these lines: in /etc/modprobe.d/b43.conf as root. (to comment out put a # in front of them)
ssb true
b43 true
then as root:
modprobe ssb && modprobe b43
then restart ceni.
and see if you get the wireless going
cheers,
ohh
-
Posts: 20
- Joined: 05 Apr 2011
#27
results from"lspci -nn"
Oldhead - wierd part now.....I do not have a file with that name now. I cant locate it, ever since I upgraded to Antix11
Code: Select all
00:00.0 Host bridge [0600]: ATI Technologies Inc Radeon 9100 IGP Host Bridge [1002:5833] (rev 02)
00:01.0 PCI bridge [0604]: ATI Technologies Inc Radeon 9100 IGP AGP Bridge [1002:5838]
00:13.0 USB Controller [0c03]: ATI Technologies Inc OHCI USB Controller #1 [1002:4347] (rev 01)
00:13.1 USB Controller [0c03]: ATI Technologies Inc OHCI USB Controller #2 [1002:4348] (rev 01)
00:14.0 SMBus [0c05]: ATI Technologies Inc SMBus [1002:4353] (rev 16)
00:14.1 IDE interface [0101]: ATI Technologies Inc Dual Channel Bus Master PCI IDE Controller [1002:4349]
00:14.3 ISA bridge [0601]: ATI Technologies Inc Device [1002:434c]
00:14.4 PCI bridge [0604]: ATI Technologies Inc IXP200 3COM 3C920B Ethernet Controller [1002:4342]
00:14.5 Multimedia audio controller [0401]: ATI Technologies Inc IXP150 AC'97 Audio Controller [1002:4341]
00:14.6 Modem [0703]: ATI Technologies Inc IXP AC'97 Modem [1002:434d] (rev 01)
01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS300M AGP [Radeon Mobility 9100IGP] [1002:5835]
02:02.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03)
02:03.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10)
02:04.0 CardBus bridge [0607]: Texas Instruments PCI1520 PC card Cardbus Controller [104c:ac55] (rev 01)
02:04.1 CardBus bridge [0607]: Texas Instruments PCI1520 PC card Cardbus Controller [104c:ac55] (rev 01)
02:07.0 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43)
02:07.1 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43)
02:07.2 USB Controller [0c03]: NEC Corporation USB 2.0 [1033:00e0] (rev 04)
-
Posts: 516
- Site Admin
- Joined: 01 Oct 2007
#28
zbrown,
Need to know what version of antiX11 your using,
post results from user in terminal of
inxi -F
thanks,
ohh
Need to know what version of antiX11 your using,
post results from user in terminal of
inxi -F
thanks,
ohh
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#29
ohh, etc/modprobe.d/b43.conf is removed in M11 recent. It is supposedly not needed.
zbrown1029, try
apt-get install --reinstall firmware-b43-installer
and follow the steps about modprobe
zbrown1029, try
apt-get install --reinstall firmware-b43-installer
and follow the steps about modprobe
-
Posts: 4,164
- Joined: 20 Feb 2009
#30
Your ifconfig -a shows a wlan0 so something is driving that broadcom card or it/wlan0 would not show in ifconfig -a.
I am not skilled with broadcom cards. From your readout I had you post. You can see that ssb is the module driving the broadcom card. I don't know what the proper driver and firmware for broadcoms are because broadcom only recently started releasing open source drivers for their new stuff (I think, like I said, not a expert with these cards).
All I know is pivera,eriefisher, and maybe OHH run these wireless cards and are used to setting them up to be connected. That was why I had you post the ouputs I requested so everyone could see what is going on with your wireless card.
I usually have to shift into my stubborn mode and experiment,troubleshoot,dig dig dig, till blue in the face and when I find my solution for wireless I post it here in the forum. I include terminal readouts in uploaded zip files and try to give as much info as I can be smart enough to supply. If you get this sorted. Keep that in Mind. So other members can benefit from your trials and tribulations. You may have a Eureka moment where everything clicks together in your head and you will think"durn. that was simple". I have had those moments.
Hang in there, Rok
I am not skilled with broadcom cards. From your readout I had you post. You can see that ssb is the module driving the broadcom card. I don't know what the proper driver and firmware for broadcoms are because broadcom only recently started releasing open source drivers for their new stuff (I think, like I said, not a expert with these cards).
All I know is pivera,eriefisher, and maybe OHH run these wireless cards and are used to setting them up to be connected. That was why I had you post the ouputs I requested so everyone could see what is going on with your wireless card.
I usually have to shift into my stubborn mode and experiment,troubleshoot,dig dig dig, till blue in the face and when I find my solution for wireless I post it here in the forum. I include terminal readouts in uploaded zip files and try to give as much info as I can be smart enough to supply. If you get this sorted. Keep that in Mind. So other members can benefit from your trials and tribulations. You may have a Eureka moment where everything clicks together in your head and you will think"durn. that was simple". I have had those moments.
Hang in there, Rok