So hi,
I've been happily using Mint as my first try on linux for a few months now. Recently (2 weeks or less) I upgraded from 17.1 to 17.2, always on the MATE desktop.
Today, sadly, my browsers stopped reaching out the internet, while Transmission is happily seeding my torrents. Unfortunately I got no ethernet options here.
My computer is an old (2006 I believe) HP dv2000 laptop, when I first installed Mint I did a fresh 17.1 MATE install, and proceeded with the 10 things to after install
This is my mintWifi output:
-------------------------
* I. scanning WIFI PCI devices...
-- Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
==> PCI ID = 8086:4222 (rev 02)
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
wlan0 IEEE 802.11abg ESSID:"--------"
Mode:Managed Frequency:2.437 GHz Access Point: F4:EC:38:F4:01:70
Bit Rate=36 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=36/70 Signal level=-74 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:1 Invalid misc:324 Missed beacon:0
lo no wireless extensions.
eth0 no wireless extensions.
-------------------------
* IV. querying ifconfig...
eth0 Link encap:Ethernet HWaddr 00:16:d3:0d:13:78
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)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:1304 errors:0 dropped:0 overruns:0 frame:0
TX packets:1304 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:85422 (85.4 KB) TX bytes:85422 (85.4 KB)
wlan0 Link encap:Ethernet HWaddr 00:13:02:45:9a:21
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:2ff:fe45:9a21/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16215 errors:0 dropped:0 overruns:0 frame:0
TX packets:23197 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3544661 (3.5 MB) TX bytes:23523306 (23.5 MB)
-------------------------
* V. querying DHCP...
RTNETLINK answers: File exists
-------------------------
* VI. querying nslookup google.com...
;; connection timed out; no servers could be reached
All browsers stopped working on wifi but transmission is ok!
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
All browsers stopped working on wifi but transmission is ok!
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
-
uberdorf
Re: All browsers stopped working on wifi but transmission is
I'm no expert, but I suspect a driver issue. That is a really old wireless card, and with the newer kernel in 17.2 linux may have dropped the firmware support for that card since you may be one of the few people left still using it. You have a few options to try...
1. go back to 17.1 (which I don't recommend)
2. try finding a driver for it and manually installing it (could be a lot of frustration for obsolete technology)
3. I would just buy a USB wireless adapter and upgrade to wireless N. Panda wireless adapters from amazon work great, and are less than $20. I've also had some success with the cheapest Belkin USB wireless adapters from Walmart. Not much luck with Netgear USB wireless adapters for me on linux, they overheat for me and don't last long. I don't know about other brands. There are also PCI wireless adapters like the one you currently have, but I have no brand recommendation for them because I don't have experience with them. Here is the link to a Panda wireless adapter which I have used with 17.2 Mint Mate, so I know it works well. http://www.amazon.com/Panda-300Mbps-Wir ... B00EQT0YK2
1. go back to 17.1 (which I don't recommend)
2. try finding a driver for it and manually installing it (could be a lot of frustration for obsolete technology)
3. I would just buy a USB wireless adapter and upgrade to wireless N. Panda wireless adapters from amazon work great, and are less than $20. I've also had some success with the cheapest Belkin USB wireless adapters from Walmart. Not much luck with Netgear USB wireless adapters for me on linux, they overheat for me and don't last long. I don't know about other brands. There are also PCI wireless adapters like the one you currently have, but I have no brand recommendation for them because I don't have experience with them. Here is the link to a Panda wireless adapter which I have used with 17.2 Mint Mate, so I know it works well. http://www.amazon.com/Panda-300Mbps-Wir ... B00EQT0YK2
-
CylonCenturion
Re: All browsers stopped working on wifi but transmission is
could be a DNS issueWoods wrote:So hi,
I've been happily using Mint as my first try on linux for a few months now. Recently (2 weeks or less) I upgraded from 17.1 to 17.2, always on the MATE desktop.
Today, sadly, my browsers stopped reaching out the internet, while Transmission is happily seeding my torrents. Unfortunately I got no ethernet options here.
My computer is an old (2006 I believe) HP dv2000 laptop, when I first installed Mint I did a fresh 17.1 MATE install, and proceeded with the 10 things to after install
This is my mintWifi output:
-------------------------
* I. scanning WIFI PCI devices...
-- Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
==> PCI ID = 8086:4222 (rev 02)
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
wlan0 IEEE 802.11abg ESSID:"--------"
Mode:Managed Frequency:2.437 GHz Access Point: F4:EC:38:F4:01:70
Bit Rate=36 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=36/70 Signal level=-74 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:1 Invalid misc:324 Missed beacon:0
lo no wireless extensions.
eth0 no wireless extensions.
-------------------------
* IV. querying ifconfig...
eth0 Link encap:Ethernet HWaddr 00:16:d3:0d:13:78
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)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:1304 errors:0 dropped:0 overruns:0 frame:0
TX packets:1304 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:85422 (85.4 KB) TX bytes:85422 (85.4 KB)
wlan0 Link encap:Ethernet HWaddr 00:13:02:45:9a:21
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:2ff:fe45:9a21/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16215 errors:0 dropped:0 overruns:0 frame:0
TX packets:23197 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3544661 (3.5 MB) TX bytes:23523306 (23.5 MB)
-------------------------
* V. querying DHCP...
RTNETLINK answers: File exists
-------------------------
* VI. querying nslookup google.com...
;; connection timed out; no servers could be reached
what DNS servers do you use, and did you experience this issue before?
Re: All browsers stopped working on wifi but transmission is
So, I just woke up this morning and it is back working, without even restarting the PC.
Answering the last question, my DNS servers are:
104.194.4.156
104.255.68.107
127.0.1.1
and no, this was the only time, but yeah, Firefox mentioned the DNS.
Answering the last question, my DNS servers are:
104.194.4.156
104.255.68.107
127.0.1.1
and no, this was the only time, but yeah, Firefox mentioned the DNS.