(Solved) Wireless connection

[jmyersWVa]

I recently had my HP 6550b laptop go dead. I got a HP 6570b as a replacement. I moved the HD to the new machine. Drive has Mepis 12/MX-14/15/16. Mepis 12 is the only one that the wireless doesn't work. (Wired does) Doing a little research in synaptic, I discovered a difference in the installed/not installed. MX-14/15/16 only have "Broadcom-sta-dkms". Mepis 12 only has "Broadcom-sta-common". Should I remove Broadcom-sta-common completly from Mepis 12 & install the dkms (which shows support for new PC),or just install it?

[dolphin_oracle]

Just install it.

[jmyersWVa]

Just install it.

Thanks D.O
Will attempt in a bit. Brocolli & Carrots in the Bamboo steamer. :)

Jerry

[jmyersWVa]

Just install it.

D.O
Just Installing it was a "No Go". It changed the installed/not stuff, but still didn't work. Wondering if it is the old 3.19 Kernel installed ! Just a WAG.

[Stevo]

It should have built and installed on the MEPIS 12 3.9 kernel--it may have needed a reboot to automatically load the "wl" driver module.

What do you get if you run

Code: Select all

su -c 'modprobe wl'

to manually load it?

And we should confirm what chipset is in the new machine--what does

Code: Select all

lspci

say about it?

[jmyersWVa]

It should have built and installed on the MEPIS 12 3.9 kernel--it may have needed a reboot to automatically load the "wl" driver module.

What do you get if you run

Code: Select all

su -c 'modprobe wl'

to manually load it?

And we should confirm what chipset is in the new machine--what does

Code: Select all

lspci

say about it?

Stevo
As soon as can get back on the wired M12 machine, I'll post.

Thanks Stevo

[jmyersWVa]

It should have built and installed on the MEPIS 12 3.9 kernel--it may have needed a reboot to automatically load the "wl" driver module.

What do you get if you run

Code: Select all

su -c 'modprobe wl'

to manually load it?

And we should confirm what chipset is in the new machine--what does

Code: Select all

lspci

say about it?

Stevo
As soon as can get back on the wired M12 machine, I'll post.

Thanks Stevo

Code: Select all

jerry@mepis1:~$ lspci
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4)
00:1c.3 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 4 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
03:00.0 Network controller: Broadcom Corporation BCM43228 802.11a/b/g/n
jerry@mepis1:~$ 

[Stevo]

OK, did a wireless interface get created? What's the result of

Code: Select all

su -c 'ifconfig -a'

We can also see if the wl module is being loaded

Code: Select all

lsmod | grep -i wl

and where it exists on your system

Code: Select all

su -c 'updatedb && locate wl.ko'

[jmyersWVa]

OK, did a wireless interface get created? What's the result of

Code: Select all

su -c 'ifconfig -a'

We can also see if the wl module is being loaded

Code: Select all

lsmod | grep -i wl

and where it exists on your system

Code: Select all

su -c 'updatedb && locate wl.ko'

Stevo. Ifconfig only shows the wired. The lsmod returns nothing. The updatedb returns error (or something) However, trying some due diligence, checking the same on mx versions may have given a clue. Booting back to Mepis (wired) & checking the Broadcom-sta I (Version was 5. something.) After the fact, I selected to view "Versions" from the properties. It showed a 6.30.223.248-2mcr120+1 (mepis) & the current 5.100.82.112-8 (old stable). I was never offered the new version as far as I know. Sometime today,after work,I'm gonna try & force it. (If it's really there) If it ain't, Its in Testing (I think)

Thanks for the push
Jerry

[kmathern]

...After the fact, I selected to view "Versions" from the properties. It showed a 6.30.223.248-2mcr120+1 (mepis) & the current 5.100.82.112-8 (old stable). I was never offered the new version as far as I know. Sometime today,after work,I'm gonna try & force it. (If it's really there) If it ain't, Its in Testing (I think)

Thanks for the push
Jerry

If I recall correctly I think some of the pinning Warren did in Mepis 12's /etc/apt/preferences* or /etc/apt/apt.conf* files causes our Community Repo (packages with a "mcr120" in the version number) to not show up as the latest version when using Synaptic's default distro setting.

I think if you change the preference to "Prefer versions from: mepis" that the CR versions will show up as the latest version.