IF, and that’s a big IF, Mint include the proprietary nVidia drivers in the ISO then they’re taking a risk … nVidia could sue.
It used to be that Mint thought they were small enough for things like this to go unnoticed … Ubuntu on the other hand doesn’t take the risk, instead it uses jockey to detect an nVidia card and offer to download and install the drivers … so it’s a “user” decision, and not an Ubuntu one.
Distributing the nVidia proprietary drivers would almost definitely require a license.
Mark Greaves (PCNetSpec) post:17:
OK, with the netbook connected to your router with an ethernet cable (so it has an active interweb connection), open a terminal and run:
sudo apt-get install b43-fwcutter firmware-b43-lpphy-installer
When that’s finished … REBOOT
Did wireless come to life … ie. if you click the networkmanager icon in the system tray (by clock) does it list your network ?
Hi Mark - nearly there! Your instructions are fine but need 1 small edit. After ‘reboot’, but before ‘click on network manager’, remove ethernet cable . Leaving the cable connected, network manager shows no wireless networks available. Unplug and all available networks appear.
The mini is now finding the network ok and is password secured. Problem now is it won’t connect to a webpage - google in this case.
I had this problem when I changed the main pc to Mint. I’m on Virgin cable and their Superhub will not allow you to change the server addresses - the hub is locked to Virgin’s own. I prefer to use Opendns servers. On the mini, changing the server addresses in network manager>edit doesn’t work, the Virgin addresses still appear as primary and secondary. Deleting and re-setting makes no difference, even after a reboot. I’ve set the parameters exactly the same as the main pc. I vaguely recall having to change a file (resolv.conf?) to override the Virgin servers. (main pc shows Opendns addresses only).
Any ideas?
Rich
I should add, the disc is just spinning merrily trying to connect to google!
Are you able to ping google by IP but not domain ?
what’s the output from:
ping -c 5 google.com
and
ping -c 5 173.194.41.167
Huh ? … there must be output ?
[EDIT]
OK, if your DNS servers are invalid in network manager it seems ping just hangs
Try this -
Right-click on the networkmanager icon in the system tray.
select “Edit Connections” … highlight your wireless connection in the list, and click the “Edit” button … enter your Linux password when prompted.
on the IPv6 tab, set:-
Method: Ignore
on the IPv4 tab set:-
[b]Method: Automatic (DHCP)
DNS servers: 208.67.222.222, 208.67.220.220[/b]
Now SAVE the connection.
Log off and on again (or reboot) … does the interweb work now ?
Sorry! I meant nothing back from either command - 100% packet loss, time 4032ms.
Unfortunately, I can’t post the full results without a lot of copying/pasting to a memory stick and transferring the data from one m/c to the other!
OK, are you saying the internet works with a wired connection, but not wireless ?
Mark Greaves (PCNetSpec) post:27:
OK, are you saying it works with a wired connection, but not wireless ?
Yes. The wireless is enabled and the internal scanner picks up several networks locally but will not connect to any. (The mini sits just 12" from my Superhub) ‘Connection information’ now shows connection to Virgin, with the Opendns server settings in place but will not open any pages. The spinner simply spins… ??? Before I changed the server settings, it did exactly the same with the Virgin settings.
What’s the output from:
lspci -nn -d 14e4:
?
[EDIT]
If nothing is returned, try:
lspci -vnn | grep -i net
–
01:00.0 Network controller [0280] Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
I’d just spotted your previous edit and I redid all the settings as you advised. Weirdly, it picked up a BT hotspot but not the Superhub?? Though I can’t go any further unless I pay credits but the site does open…
lspci -vnn | grep -i net returns
1st part - same as above + Ethernet controller [0200] Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller [11ab:4354]
I’m having to type this in manually…
OK, it’s a 4315 not a 4312 as it advertised itself in lshw
there are 2 ways of making this work … the wl drivers, or the non-free firmware
Let’s try the easiest first
plug back into your router with an ethernet cable, and run these commands:
sudo apt-get update
then
sudo apt-get upgrade
when finished, REBOOT
with it still cabled to the router, run:
sudo apt-get remove --purge b43-fwcutter firmware-b43-lpphy-installer
then
sudo apt-get install linux-firmware-nonfree
then
sudo modprobe -r b43 && sudo modprobe b43
now unplug your ethernet cable and try wireless/interweb
–
Mark Greaves (PCNetSpec) post:31:
OK, it’s a 4315 not a 4312 as it advertised itself in lshw
there are 2 ways of making this work … the wl drivers, or the non-free firmware
Let’s try the easiest first
plug back into your router with an ethernet cable, and run these commands:
sudo apt-get update
then
sudo apt-get upgrade
when finished, REBOOT
with it still cabled to the router, run:
sudo apt-get remove --purge b43-fwcutter firmware-b43-lpphy-installer
then
sudo apt-get install linux-firmware-nonfree
then
sudo modprobe -r b43 && sudo modprobe b43
now unplug your ethernet cable and try wireless/interweb
–
Done, but no different! Back on cable to post this…
Last command returns -
~ $ sudo modprobe -r b43 && sudo modprobe b43
OK still on the cable run:
sudo apt-get install linux-headers-generic build-essential dkms
when that’s done, run:
sudo apt-get install bcmwl-kernel-source
when that’s done, unload the b43 driver with:
sudo modprobe -r b43
and load the wl driver with:
sudo modprobe wl
now try wireless.
[EDIT]
BTW, if that works it may not survive a reboot … but we can fix that.
So if it works, but wireless stops working after a reboot … get wireless working again with:
sudo modprobe -r b43 && sudo modprobe wl
and let me know you needed to do that, and I’ll explain how to make it permanent.
–
Mark Greaves (PCNetSpec) post:33:
OK still on the cable run:
sudo apt-get install linux-headers-generic build-essential dkms
when that’s done, run:
sudo apt-get install bcmwl-kernel-source
when that’s done, unload the b43 driver with:
sudo modprobe -r b43
and load the wl driver with:
sudo modprobe wl
now try wireless.
BTW, if that works it may not survive a reboot … but we can fix that.
So if it works, but wireless stops working after a reboot … get wireless working again with:
sudo modprobe -r b43 && sudo modprobe wl
and let me know you needed to do that, and I’ll explain how to make it permanent.
Still no joy - either before or after a reboot.
Mark, I can’t thank you enough for your time and effort on this… I’ll call it day for now and try again tomorrow. I need to find a dark place to lie down… :
–
One of those MUST work…
Delete your wireless connection and try recreating it.
What’s the output from:
sudo lshw -C network
and
ifconfig
and
iwconfig
and
sudo iwlist scanning
and
rfkill list
BTW, you can do all that with the cable plugged in
Mark Greaves (PCNetSpec) post:35:
One of those MUST work…
Delete your wireless connection and try recreating it. Done - no change
What’s the output from:
sudo lshw -C network
*-network
and
ifconfig
~ $ ifconfig
eth1 Link encap:Ethernet HWaddr 00:24:2b:ae:ff:08
lo Link encap:Local Loopback
and
iwconfig
~ $ iwconfig
eth0 no wireless extensions.
eth1 IEEE 802.11abg ESSID:“virginmedia6365863”
and
sudo iwlist scanning
~ $ sudo iwlist scanning
eth0 Interface doesn’t support scanning.
eth1 Scan completed :
katharine@katharine-mini ~ $
and
rfkill list
~ $ rfkill list
BTW, you can do all that with the cable plugged in
All done as per - hope this sheds light! Am on cable with mini at present
Edit: I’ve tried deleting all other ‘found’ networks to see if that had an effect but no change there either.
Can you run:
sudo modprobe -r wl
then
sudo modprobe b43
then send the output from those commands in my last posting again
katharine@katharine-mini ~ $ sudo modprobe -r wl
Edit: Sorry Mark, I’m not clear on this one - did you want the ethernet cable unplugged for this, or doesn’t it matter?
Updated info -
katharine@katharine-mini ~ $ sudo modprobe -r wl
lo Link encap:Local Loopback
wlan0 Link encap:Ethernet HWaddr 00:24:2b:ae:ff:08
katharine@katharine-mini ~ $ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
katharine@katharine-mini ~ $ sudo iwlist scanning
lo Interface doesn’t support scanning.
eth0 Interface doesn’t support scanning.
katharine@katharine-mini ~ $ rfkill list
If you pull the network cable now, do you have access? That info suggests that you are connected to “virginmedia6365863”, which I guess is your hub
