And a nice comment by linuxscreenshots:http://www.linuxscreenshots.org/?releas ... 0MX-14.1.1
HenryVery clean interface. I'm a fan of the side dock position
Post by Utopia » Thu Jun 19, 2014 4:07 pm
And a nice comment by linuxscreenshots:http://www.linuxscreenshots.org/?releas ... 0MX-14.1.1
HenryVery clean interface. I'm a fan of the side dock position
Post by Gordon Cooper » Thu Jun 19, 2014 9:40 pm
Post by Richard » Thu Jun 19, 2014 9:56 pm
Thanks for the suggestion Jerry. Quoting the original post since it was about 3 pages back.Jerry3904 wrote:Hmmm: driver is associated but no AP is recognized.Richard wrote:Put it on a USB with dd. Boots fine, runs great,
but can not connect to Broadcom wireless, OOTB:Code: Select all
richard@mx14:/WIN/Dropbox $ inxi -n Network: Card-1: Atheros AR8132 Fast Ethernet driver: atl1c IF: eth0 state: down mac: 00:26:22:2b:f4:05 Card-2: Broadcom BCM4312 802.11b/g LP-PHY driver: wl IF: wlan0 state: up mac: 0c:60:76:54:98:82 richard@mx14:/WIN/Dropbox
Please paste back the output ofCan you manually associate it with AP using as root?:Code: Select all
iwconfig wlan0
Code: Select all
iwconfig wlan0 essid [name of your AP]
Code: Select all
sudo iwconfig wlan0
wlan0 No such device
Code: Select all
sudo iwconfig wlan0 "Hotel Radazul 3A"
iwconfig: unknown command "Hotel Radazul 3A"
Post by fu-sen » Thu Jun 19, 2014 10:06 pm
Post by Richard » Thu Jun 19, 2014 10:41 pm
@Jerry3904,Jerry3904 wrote:Could you run an experiment for me with that machine that does not connect OOTB using a Broadcom chipset?Richard wrote:Put it on a USB with dd. Boots fine, runs great,
but can not connect to Broadcom wireless, OOTB:Code: Select all
richard@mx14:/WIN/Dropbox $ inxi -n Network: Card-1: Atheros AR8132 Fast Ethernet driver: atl1c IF: eth0 state: down mac: 00:26:22:2b:f4:05 Card-2: Broadcom BCM4312 802.11b/g LP-PHY driver: wl IF: wlan0 state: up mac: 0c:60:76:54:98:82 richard@mx14:/WIN/Dropbox
1) install the experimental MX Network Assistant:
https://github.com/AdrianTM/mx-network/ ... 1_i386.deb
2) on the Troubleshooting tab, click first the Scan hardware button, then the Linux drivers button. Copy and save the output somewhere so you can post it later.
3) use the blacklist button to get rid of "wl"
4) see if you can connect now OOTB
Thanks--let me know what you find out.
Post by Gordon Cooper » Fri Jun 20, 2014 3:18 am
Post by m_pav » Fri Jun 20, 2014 8:02 am
Post by jdmeaux1952 » Fri Jun 20, 2014 8:15 am
That answered my question and my remarks. Thanks all around for the explanation.m_pav wrote:SMART attribute 187 can be ignored, it only reports an error generated by the hard disks onboard RAM memory, such errors are usually repaired in the blink of an eye and it was an unforeseen side effect of introducing a SMART data check on hard disks selected for installation. .
Post by Adrian » Fri Jun 20, 2014 8:33 am
Post by Stevo » Fri Jun 20, 2014 9:55 am
Lazarus 1.2.2 is in the MEPIS 12 testing CR. Make sure that it's enabled under Repositories in Synaptic.Gordon Cooper wrote:A comment - not a criticism, I realise there's a lot of work yet to be done. Comment is that
looking with 14.1.1 at Synaptic, there seem to be files missing that were there in MX-14.
Lazarus 1.2.2 for example.
Other tests on 14.1.1 have gone well.
Gordon.