[Solved Mostly] ZEN-mini on HP-mini - wifi unknown issue

[wwwauthor]

Hp mini #110

Issue:

wifi is there but can not for the life of me connect to my network. I do however believe it is an encryption issue as i am able to connect to several neighbor's of which are using open networks.

With that said, also if I boot up with the live usb(zen-mini) I am able to connect to my encrypted connection.

I welcome any help.

Info:

Code:

uname -r
2.6.33.4-pclos1.bfs

cat /etc/issue
ZEN-mini release 2010 (PCLinuxOS) for i586
Kernel 2.6.33.4-pclos1.bfs on a Dual-processor i686 / \l


lshw | egrep BCM
                product: BCM4312 802.11b/g LP-PHY

lspci -vv | grep "Network controller"
01:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)


lsmod | grep wl
wl                   1267871  0
lib80211                4749  2 lib80211_crypt_tkip,wl

lsmod | grep rfkill
rfkill                 13919  1 hp_wmi

cat /etc/modprobe.conf | grep alias
alias pci:v000014E4d00004315sv0000103Csd00001507bc02sc80i00 wl
alias eth1 wl
alias pci:v00001969d00001062sv0000103Csd0000308Fbc02sc00i00 atl1c
alias eth0 atl1c


cat /var/log/prcsys.log | grep "not found"
Configuring wireless regulatory domain  nl80211 not found.

cat /var/log/prcsys.log | grep eth1
Bringing up interface eth1:  Error for wireless request "Set Encode" (8B2A) :
    SET failed on device eth1 ; Invalid argument.



iwlist eth1 scan
eth1      Scan completed :
          Cell 01 - Address: <snip 50+ lines>
   Lots of neighbor's

[Joble]

I don't know if this will help or not but 80211 not found.  If you need it, and I'm not sure you do, it may be blacklisted in /etc/modprobe.d/blacklist  if it is, you might want to put a # in front of it and reboot to see if that helps.  If it does not help, or makes things worse, then just go back in and remove the #

[wwwauthor]

sorry forgot to add that one to the list of code
as you can see no reference to 80211 at all.

Code:

cat /etc/modprobe.d/blacklist
blacklist ssb

[Hootiegibbon]

wwwauthor,

Can you try the following in a Konsole

iwlist scanning

iwlist channel

Thanks

Jase

[wwwauthor]

as i showed in the code i included > iwlist scan works
scan scanning is same thing < if it isn't it produces exact same output.
iwlist channel works also

Code:

iwlist channel | grep eth1
eth1     11 channels in total; available frequencies :
<snip>

[Hootiegibbon]

wwwauthor,

Looks like nl80211 is missing from your loaded modules can you confirm by

lsmod |grep nl80211

if this returns no result then start up PCC >network and internet delete your existing interface (dont remake it yet)

then return to a su to root and

modprobe nl80211
depmod -a

Then return to PCC > Networking & internet create new interface.

See if that helps

Jase

[wwwauthor]

Code:

lsmod |grep nl80211
#nothing.

iw list
nl80211 not found

modprobe nl80211
FATAL: Module nl80211 not found.

depmod -a
#nothing

did as you told me with the other steps, still nothing.
thanks for trying though.

[Hootiegibbon]

ok - do you have the dkms-broadcom-wl package installed - and did it rebuild when you rebooted into the new kernel

Jase

[wwwauthor]

yup it did recompile on new kernel.

I have a habit of disabling plymouth, i prefer seeing what my systems do.

btw. Some smart cookie, put the auto install of "dkms-broadcom-wl" in network manager when you click on your wifi card.

[Joble]

btw. Some smart cookie, put the auto install of "dkms-broadcom-wl" in network manager when you click on your wifi card.

Hmm, not sure what that means.  If it's good I would have to say either Tex or siamer did it.  If it's bad, I would have to say either Tex or siamer did it.

* Joble runs for cover.

[wwwauthor]

  It was a complement!

[wwwauthor]

lol too funny,

removed it all *broadcom-wl including config files.
rebooted, and reinstalled *broadcom-wl

edit.
btw at this point i checked and still no wifi for my network

cont.
booted the live usb logged in as root copied /etc/ndiswrapper/*

rebooted
connection to my network now works.
Network Center still throws up an error connection failed! but it lies!

I am sure the issue is far deeper then ndis but hey it works.

[Joble]

ndis always reports failure, at lest on my machines.  I guess I don't understand how we went from broadcom.wl to ndis in the first place.  If you needed help with ndiswrapper, well, I think I might have been able to help with that.  Or not.

[wwwauthor]

i never used ndiswrapper.. i will assume the broadcom is handled by it.