Mint 13 no interent access ethernet & wirless

[bbb13]

hello to everyone!

i own a Sony Vaio VPCEJ1L1E laptop. After a fresh install everything worked great. ethernet was working properly at my house. i went to another house, connected through ethernet, everything great. but i after i returned home, ethernet was connecting, but i didnt had internet access. same thing with wireless, connected but no internet access. the other pc's in home work flawlessly, so the routher is not an issue. this happened to me to both Cinnamon and MATE editions. i used to work ubuntu 12.04 before Mint at the same laptop without any networking problems. I also have another partition with Opensuse 12.1 LXDE and internet works great there. i tried this: viewtopic.php?f=49&t=80757 but with no luck. i do have the RTL8111/8168B. here's some info:

ifconfig

Code: Select all

eth0      Link encap:Ethernet  HWaddr 78:84:3c:e2:5b:e8 
          inet addr:192.168.60.4  Bcast:192.168.60.255  Mask:255.255.255.0
          inet6 addr: fe80::7a84:3cff:fee2:5be8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:111 errors:0 dropped:0 overruns:0 frame:0
          TX packets:292 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8565 (8.5 KB)  TX bytes:35586 (35.5 KB)
          Interrupt:42 Base address:0x6000

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:16436  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:240 (240.0 B)  TX bytes:240 (240.0 B)

lspci

Code: Select all

00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b4)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1055 (rev a1)
01:00.1 Audio device: NVIDIA Corporation HDMI Audio stub (rev a1)
07:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
0d:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5116 PCI Express Card Reader (rev 01)
13:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)

any advice appreciated!

[AlbertP]

Please run inxi -N in terminal and post the output. By the way, the r8169 driver is mostly fixed in 13 so you don't really need r8168 anymore.

[bbb13]

inxi -N

Code: Select all

Network:   Card-1: Atheros AR9285 Wireless Network Adapter (PCI-Express) driver: ath9k
           Card-2: Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller driver: r8168


[AlbertP]

You are using the r8168 driver now. Maybe it helps to switch back to r8169 again? That driver should be working fine in 13. You can go to the folder where you stored the r8168 source, right-click > Open in Terminal and run sudo make uninstall to remove the driver.

[shayamoonstone]

I had the same problem in Linux Mint 13, where the internet access worked for awhile, but then I couldn't get on, even though it shows that it's been connected in the XFCE notification area. However, I had figured out what the culprit was- there was a shellscript in /sbin that's called 'resolvconf' in which I removed, as well as symlinking the /etc/resolve.conf file to /run/resolvconf/resolv.conf. This had cleared up the problem (at least for me anyways). I do believe this is a bug in Mint 13, because I also had to manually create the /etc/resolv.conf file myself, in order for the networking to work properly.

[heavy metal]

I had the same issue, fixed it uninstalling network manager and installing Wicd!

[shayamoonstone]

cool beans

[bbb13]

for now i just did a clean install (again) to fix it, i hope they release an update so i'm not gonna go into trouble of resolv.conf stuff. nevertherless this is a huge and stupid bug, and they should fix it fast.

[AlbertP]

for now i just did a clean install (again) to fix it, i hope they release an update so i'm not gonna go into trouble of resolv.conf stuff. nevertherless this is a huge and stupid bug, and they should fix it fast.

Most people have no problem connecting to the net so it's maybe not an issue of very high priority.

Perhaps you can find the bug on Launchpad.net (at Ubuntu) and say that the issue affects you as well. Doing that will increse the bug's importance and the attention it gets from the package maintainers.

[bbb13]

for now i just did a clean install (again) to fix it, i hope they release an update so i'm not gonna go into trouble of resolv.conf stuff. nevertherless this is a huge and stupid bug, and they should fix it fast.

Most people have no problem connecting to the net so it's maybe not an issue of very high priority.

Perhaps you can find the bug on Launchpad.net (at Ubuntu) and say that the issue affects you as well. Doing that will increse the bug's importance and the attention it gets from the package maintainers.

this bug never affected me before Mint as i was using 11.10 for a almost whole year and 12.04 since its official release date