Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
![Reply](https://www.linuxquestions.org/questions/images/buttons/reply.gif) |
04-23-2014, 07:54 PM
|
#1
|
Member
Registered: Sep 2009
Posts: 252
Rep:
|
Unable to access wired or wireless ethernet connections
I have a dv6 laptop that has been working fine up until today. I cannot access the internet wired or wireless. I tried different cables. No dice. Could this be a driver issue?
What can I do to check if it is that I can post back? If it is driver related how can I update it seeing that I am running Linux?
I tried booting from a Puppy Linux CD, booted from my Peppermint 4, Ubuntu 14.04 partitions as well from my HD with the same result.
|
|
|
04-23-2014, 08:10 PM
|
#2
|
LQ Addict
Registered: Nov 2013
Location: Tokyo
Distribution: Mostly Ubuntu and Centos
Posts: 6,316
|
Quote:
Originally Posted by rmcellig
I have a dv6 laptop that has been working fine up until today. I cannot access the internet wired or wireless. I tried different cables. No dice. Could this be a driver issue?
What can I do to check if it is that I can post back? If it is driver related how can I update it seeing that I am running Linux?
I tried booting from a Puppy Linux CD, booted from my Peppermint 4, Ubuntu 14.04 partitions as well from my HD with the same result.
|
What do you mean by "the internet doesn't work"? Can you access any local computers? Can you ping your router? Can you access the internet from other computers? Can you ping localhost? If you see that the internet is accessible in principle, it's likely something is wrong with your network configuration.
Simple steps to start troubleshooting your network configuration (not necessarily in this order, and probably not complete): - The commands ifconfig or ip a tell what state your network interfaces are in. What do they say?
- Basic network configuration is in the file /etc/network/interfaces on Ubuntu (don't know how it's done on Puppy). What does it look like?
- Your wired interface is named in the interfaces file. Probably eth0. Do you see anything in the system log /var/log/syslog about eth0?
|
|
|
04-23-2014, 08:19 PM
|
#3
|
Member
Registered: Sep 2009
Posts: 252
Original Poster
Rep:
|
All other computers on my LAN access the internet with no problems.
I cannot access any shared devices on the HP either. I will post back the results from the list of things to check.
|
|
|
04-23-2014, 08:34 PM
|
#4
|
Member
Registered: Sep 2009
Posts: 252
Original Poster
Rep:
|
Here is the requested info:
Code:
randy@cb11:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 60:eb:69:0f:9d:24
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:1774 errors:0 dropped:5 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:185361 (181.0 KiB) TX bytes:0 (0.0 B)
Interrupt:40 Base address:0xa000
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:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:300 (300.0 B) TX bytes:300 (300.0 B)
randy@cb11:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 60:eb:69:0f:9d:24 brd ff:ff:ff:ff:ff:ff
randy@cb11:~$
network file:
This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
syslog:
Apr 23 18:11:53 cb11 NetworkManager[2536]: <info> disable requested (sleeping: no enabled: yes)
Apr 23 18:11:53 cb11 NetworkManager[2536]: <info> sleeping or disabling...
Apr 23 18:11:53 cb11 NetworkManager[2536]: <info> (eth0): now unmanaged
Apr 23 18:11:53 cb11 NetworkManager[2536]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Apr 23 18:11:53 cb11 NetworkManager[2536]: <info> (eth0): cleaning up...
Apr 23 18:11:53 cb11 NetworkManager[2536]: <info> (eth0): taking down device.
Apr 23 18:11:55 cb11 NetworkManager[2536]: <info> enable requested (sleeping: no enabled: no)
Apr 23 18:11:55 cb11 NetworkManager[2536]: <info> waking up and re-enabling...
Apr 23 18:11:55 cb11 NetworkManager[2536]: <info> (eth0): now managed
Apr 23 18:11:55 cb11 NetworkManager[2536]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Apr 23 18:11:55 cb11 NetworkManager[2536]: <info> (eth0): bringing up device.
Apr 23 18:11:55 cb11 NetworkManager[2536]: <info> (eth0): preparing device.
Apr 23 18:11:55 cb11 NetworkManager[2536]: <info> (eth0): deactivating device (reason 'managed') [2]
Apr 23 18:11:55 cb11 kernel: [ 2275.294055] r8169 0000:03:00.0: eth0: link down
Apr 23 18:11:55 cb11 kernel: [ 2275.294979] ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 23 18:12:00 cb11 NetworkManager[2536]: <info> disable requested (sleeping: no enabled: yes)
Apr 23 18:12:00 cb11 NetworkManager[2536]: <info> sleeping or disabling...
Apr 23 18:12:00 cb11 NetworkManager[2536]: <info> (eth0): now unmanaged
Apr 23 18:12:00 cb11 NetworkManager[2536]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Apr 23 18:12:00 cb11 NetworkManager[2536]: <info> (eth0): cleaning up...
Apr 23 18:12:00 cb11 NetworkManager[2536]: <info> (eth0): taking down device.
Apr 23 18:12:05 cb11 NetworkManager[2536]: <info> enable requested (sleeping: no enabled: no)
Apr 23 18:12:05 cb11 NetworkManager[2536]: <info> waking up and re-enabling...
Apr 23 18:12:05 cb11 NetworkManager[2536]: <info> (eth0): now managed
Apr 23 18:12:05 cb11 NetworkManager[2536]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Apr 23 18:12:05 cb11 NetworkManager[2536]: <info> (eth0): bringing up device.
Apr 23 18:12:05 cb11 kernel: [ 2284.611951] r8169 0000:03:00.0: eth0: link down
Apr 23 18:12:05 cb11 NetworkManager[2536]: <info> (eth0): preparing device.
Apr 23 18:12:05 cb11 NetworkManager[2536]: <info> (eth0): deactivating device (reason 'managed') [2]
Apr 23 18:12:05 cb11 kernel: [ 2284.612849] ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 23 18:12:27 cb11 shutdown[4048]: shutting down for system halt
Apr 23 18:12:28 cb11 init: Switching to runlevel: 0
Apr 23 18:12:29 cb11 minissdpd[3079]: received signal 15, good-bye
Apr 23 18:12:29 cb11 bluetoothd[2508]: Terminating
Apr 23 18:12:29 cb11 avahi-daemon[2441]: Got SIGTERM, quitting.
Apr 23 18:12:29 cb11 kernel: [ 2308.672601] colord-sane[3151]: segfault at 98 ip 00007f9fcced37cc sp 00007f9fccea9b88 error 6 in libdbus-1.so.3.7.2[7f9fcceab000+44000]
Apr 23 18:12:29 cb11 NetworkManager[2536]: <info> caught signal 15, shutting down normally.
Apr 23 18:12:29 cb11 NetworkManager[2536]: <warn> quit request received, terminating...
Apr 23 18:12:29 cb11 NetworkManager[2536]: <info> (eth0): now unmanaged
Apr 23 18:12:29 cb11 NetworkManager[2536]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36]
Apr 23 18:12:29 cb11 NetworkManager[2536]: <info> (eth0): cleaning up...
Apr 23 18:12:29 cb11 NetworkManager[2536]: <info> (eth0): taking down device.
Apr 23 18:12:29 cb11 NetworkManager[2536]: <info> exiting (success)
|
|
|
04-23-2014, 09:05 PM
|
#5
|
Member
Registered: Sep 2009
Posts: 252
Original Poster
Rep:
|
My ping results:
Code:
randy@cb11:~$ ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_req=1 ttl=64 time=0.039 ms
64 bytes from 127.0.0.1: icmp_req=2 ttl=64 time=0.037 ms
64 bytes from 127.0.0.1: icmp_req=3 ttl=64 time=0.036 ms
64 bytes from 127.0.0.1: icmp_req=4 ttl=64 time=0.043 ms
64 bytes from 127.0.0.1: icmp_req=5 ttl=64 time=0.037 ms
64 bytes from 127.0.0.1: icmp_req=6 ttl=64 time=0.042 ms
64 bytes from 127.0.0.1: icmp_req=7 ttl=64 time=0.041 ms
64 bytes from 127.0.0.1: icmp_req=8 ttl=64 time=0.034 ms
64 bytes from 127.0.0.1: icmp_req=9 ttl=64 time=0.036 ms
64 bytes from 127.0.0.1: icmp_req=10 ttl=64 time=0.042 ms
64 bytes from 127.0.0.1: icmp_req=11 ttl=64 time=0.036 ms
64 bytes from 127.0.0.1: icmp_req=12 ttl=64 time=0.035 ms
64 bytes from 127.0.0.1: icmp_req=13 ttl=64 time=0.036 ms
64 bytes from 127.0.0.1: icmp_req=14 ttl=64 time=0.036 ms
64 bytes from 127.0.0.1: icmp_req=15 ttl=64 time=0.037 ms
64 bytes from 127.0.0.1: icmp_req=16 ttl=64 time=0.035 ms
64 bytes from 127.0.0.1: icmp_req=17 ttl=64 time=0.035 ms
64 bytes from 127.0.0.1: icmp_req=18 ttl=64 time=0.033 ms
64 bytes from 127.0.0.1: icmp_req=19 ttl=64 time=0.038 ms
64 bytes from 127.0.0.1: icmp_req=20 ttl=64 time=0.035 ms
^[64 bytes from 127.0.0.1: icmp_req=21 ttl=64 time=0.038 ms
64 bytes from 127.0.0.1: icmp_req=22 ttl=64 time=0.034 ms
64 bytes from 127.0.0.1: icmp_req=23 ttl=64 time=0.034 ms
64 bytes from 127.0.0.1: icmp_req=24 ttl=64 time=0.033 ms
q64 bytes from 127.0.0.1: icmp_req=25 ttl=64 time=0.042 ms
64 bytes from 127.0.0.1: icmp_req=26 ttl=64 time=0.038 ms
64 bytes from 127.0.0.1: icmp_req=27 ttl=64 time=0.033 ms
64 bytes from 127.0.0.1: icmp_req=28 ttl=64 time=0.034 ms
64 bytes from 127.0.0.1: icmp_req=29 ttl=64 time=0.046 ms
64 bytes from 127.0.0.1: icmp_req=30 ttl=64 time=0.043 ms
64 bytes from 127.0.0.1: icmp_req=31 ttl=64 time=0.036 ms
64 bytes from 127.0.0.1: icmp_req=32 ttl=64 time=0.038 ms
64 bytes from 127.0.0.1: icmp_req=33 ttl=64 time=0.031 ms
|
|
|
04-23-2014, 10:01 PM
|
#6
|
LQ Addict
Registered: Nov 2013
Location: Tokyo
Distribution: Mostly Ubuntu and Centos
Posts: 6,316
|
Quote:
Originally Posted by rmcellig
Code:
randy@cb11:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 60:eb:69:0f:9d:24
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:1774 errors:0 dropped:5 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:185361 (181.0 KiB) TX bytes:0 (0.0 B)
Interrupt:40 Base address:0xa000
|
Note how eth0 has no IP address. The loopback interface lo, on the other hand, has one:
Quote:
Code:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
|
Quote:
syslog:
Code:
[...]
Apr 23 18:11:55 cb11 NetworkManager[2536]: <info> (eth0): deactivating device (reason 'managed') [2]
Apr 23 18:11:55 cb11 kernel: [ 2275.294055] r8169 0000:03:00.0: eth0: link down
Apr 23 18:11:55 cb11 kernel: [ 2275.294979] ADDRCONF(NETDEV_UP): eth0: link is not ready
|
Your network devices are managed by NetworkManager. I don't see any other device mentioned than eth0 - are you sure your WLAN interface is enabled at all?
r8169 0000:03:00.0: eth0: link down indicates that there is something wrong with the ethernet interface. You get such a message when the cable is disconnected, for example, but it could also be that the wrong driver is used. r8169 is the driver for a Realtek 8169 interface.
What interface does your PC have? You can figure this out from the BIOS (most reliable) or by checking the quickspecs for dv6 on the HP web site.
It would also be interesting to see other r8169 messages in your syslog, or messages containing the word Realtek.
|
|
|
04-23-2014, 10:34 PM
|
#7
|
Member
Registered: Sep 2009
Posts: 252
Original Poster
Rep:
|
WLAN must be enabled because my other computers work fine accessing the internet.
|
|
|
04-23-2014, 11:29 PM
|
#8
|
LQ Addict
Registered: Nov 2013
Location: Tokyo
Distribution: Mostly Ubuntu and Centos
Posts: 6,316
|
Quote:
Originally Posted by rmcellig
WLAN must be enabled because my other computers work fine accessing the internet.
|
I mean WLAN on your notebook. I don't know the dv6, but my notebook (also HP) has a button that switches WLAN off. And I am sure this can be done from the BIOS as well. From the limited information I have, it seems to me that your kernel doesn't see a WLAN device. Or perhaps it's missing the driver.
How to find out? One would have to look through syslog for messages indicating an unknown device, or a configuration failure.
Something I forgot: lspci -v would be another useful tool. It dumps a verbose listing of all devices on your PCI bus and should tell you what wired or wireless devices currently exist. lspci -k shows what drivers are connected to the devices (and lspci -vk does both). This is what I get on my system:
Code:
$ lspci -k
[....]
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
Subsystem: ASUSTeK Computer Inc. P8P67 and other motherboards
Kernel driver in use: r8169
Kernel modules: r8169
[....]
|
|
|
04-23-2014, 11:52 PM
|
#9
|
LQ Guru
Registered: Feb 2003
Location: Virginia, USA
Distribution: Debian 12
Posts: 8,370
|
Take a look in your BIOS and see if your network chip or card is enabled.
----------------------
Steve Stites
|
|
|
04-24-2014, 05:59 AM
|
#10
|
Member
Registered: Sep 2009
Posts: 252
Original Poster
Rep:
|
randy@cb11:~$ lspci -v
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
Subsystem: Hewlett-Packard Company Device 144c
Flags: bus master, fast devsel, latency 0
Capabilities: <access denied>
Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device 144c
Flags: bus master, fast devsel, latency 0, IRQ 42
Memory at b0000000 (64-bit, non-prefetchable) [size=4M]
Memory at a0000000 (64-bit, prefetchable) [size=256M]
I/O ports at 4050 [size=8]
Expansion ROM at <unassigned> [disabled]
Capabilities: <access denied>
Kernel driver in use: i915
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
Subsystem: Hewlett-Packard Company Device 144c
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at b4404000 (64-bit, non-prefetchable) [size=16]
Capabilities: <access denied>
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) (prog-if 20 [EHCI])
Subsystem: Hewlett-Packard Company Device 144c
Flags: bus master, medium devsel, latency 0, IRQ 16
Memory at b440a000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci_hcd
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
Subsystem: Hewlett-Packard Company Device 144c
Flags: bus master, fast devsel, latency 0, IRQ 43
Memory at b4400000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 00003000-00003fff
Memory behind bridge: b3400000-b43fffff
Prefetchable memory behind bridge: 00000000b0400000-00000000b13fffff
Capabilities: <access denied>
Kernel driver in use: pcieport
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
I/O behind bridge: 00002000-00002fff
Memory behind bridge: b2400000-b33fffff
Prefetchable memory behind bridge: 00000000b1400000-00000000b23fffff
Capabilities: <access denied>
Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) (prog-if 20 [EHCI])
Subsystem: Hewlett-Packard Company Device 144c
Flags: bus master, medium devsel, latency 0, IRQ 21
Memory at b4409000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=32
Capabilities: <access denied>
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)
Subsystem: Hewlett-Packard Company Device 144c
Flags: bus master, medium devsel, latency 0
Capabilities: <access denied>
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05) (prog-if 01 [AHCI 1.0])
Subsystem: Hewlett-Packard Company Device 144c
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 41
I/O ports at 4048 [size=8]
I/O ports at 405c [size=4]
I/O ports at 4040 [size=8]
I/O ports at 4058 [size=4]
I/O ports at 4020 [size=32]
Memory at b4408000 (32-bit, non-prefetchable) [size=2K]
Capabilities: <access denied>
Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
Subsystem: Hewlett-Packard Company Device 144c
Flags: medium devsel, IRQ 19
Memory at b4406000 (64-bit, non-prefetchable) [size=256]
I/O ports at 4000 [size=32]
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05)
Subsystem: Hewlett-Packard Company Device 144c
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at b4407000 (64-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
Kernel driver in use: intel ips
02:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)
Subsystem: Hewlett-Packard Company Device 145c
Flags: fast devsel, IRQ 16
Memory at b3400000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
Subsystem: Hewlett-Packard Company Device 144c
Flags: bus master, fast devsel, latency 0, IRQ 40
I/O ports at 2000 [size=256]
Memory at b1404000 (64-bit, prefetchable) [size=4K]
Memory at b1400000 (64-bit, prefetchable) [size=16K]
Expansion ROM at b1410000 [disabled] [size=64K]
Capabilities: <access denied>
Kernel driver in use: r8169
7f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
Subsystem: Hewlett-Packard Company Device 144c
Flags: bus master, fast devsel, latency 0
7f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
Subsystem: Hewlett-Packard Company Device 144c
Flags: bus master, fast devsel, latency 0
7f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
Subsystem: Hewlett-Packard Company Device 144c
Flags: bus master, fast devsel, latency 0
7f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
Subsystem: Hewlett-Packard Company Device 144c
Flags: bus master, fast devsel, latency 0
7f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
Subsystem: Hewlett-Packard Company Device 144c
Flags: bus master, fast devsel, latency 0
7f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
Subsystem: Hewlett-Packard Company Device 144c
Flags: bus master, fast devsel, latency 0
randy@cb11:~$
randy@cb11:~$ lspci -k
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
Subsystem: Hewlett-Packard Company Device 144c
Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
Subsystem: Hewlett-Packard Company Device 144c
Kernel driver in use: i915
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
Subsystem: Hewlett-Packard Company Device 144c
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
Subsystem: Hewlett-Packard Company Device 144c
Kernel driver in use: ehci_hcd
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
Subsystem: Hewlett-Packard Company Device 144c
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)
Kernel driver in use: pcieport
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05)
Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
Subsystem: Hewlett-Packard Company Device 144c
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)
Subsystem: Hewlett-Packard Company Device 144c
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05)
Subsystem: Hewlett-Packard Company Device 144c
Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
Subsystem: Hewlett-Packard Company Device 144c
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05)
Subsystem: Hewlett-Packard Company Device 144c
Kernel driver in use: intel ips
02:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)
Subsystem: Hewlett-Packard Company Device 145c
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
Subsystem: Hewlett-Packard Company Device 144c
Kernel driver in use: r8169
7f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
Subsystem: Hewlett-Packard Company Device 144c
7f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
Subsystem: Hewlett-Packard Company Device 144c
7f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
Subsystem: Hewlett-Packard Company Device 144c
7f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
Subsystem: Hewlett-Packard Company Device 144c
7f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
Subsystem: Hewlett-Packard Company Device 144c
7f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
Subsystem: Hewlett-Packard Company Device 144c
randy@cb11:~$
|
|
|
04-24-2014, 06:31 AM
|
#11
|
Member
Registered: Sep 2009
Posts: 252
Original Poster
Rep:
|
I just rebooted my computer into Linux Mint 16 and was able to get a wireless connection with full access to the internet.
I still need to get the actual wired internet connection going. I don't carry this laptop around. It sits stationary in my house all the time and I would much rather use a hard wireed connection like the rest of the computers on my LAN.
|
|
|
04-25-2014, 02:18 AM
|
#12
|
LQ Addict
Registered: Nov 2013
Location: Tokyo
Distribution: Mostly Ubuntu and Centos
Posts: 6,316
|
Quote:
Code:
randy@cb11:~$ lspci -k
[...]
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
Subsystem: Hewlett-Packard Company Device 144c
Kernel driver in use: r8169
|
Well, according to the Realtek web site, that looks like the right driver for this device.
It's a pity I don't have direct access to your PC. I would have another look at the syslog file (perhaps you can just attach it to your next reply?).
Another test I would perform is disabling NetworkManager, thereby removing one potential source for error, setting up a static IP address for the wired connection and seeing what, if any, error messages pop up.
Are you able to set up a static IP address? I don't know if Ubuntu has a GUI for that task; it can however be done by modifying the /etc/network/interfaces file. You would then temporarily stop NetworkManager ( service NetworkManager stop, I believe) and initialize your interface with ifup eth0. I would then hope you get an error message, or a new message in the syslog, which would give us more clues. Or perhaps it would just work, which might indicate a problem with NetworkManager.
|
|
|
04-25-2014, 05:02 AM
|
#13
|
Member
Registered: Sep 2009
Posts: 252
Original Poster
Rep:
|
For some reason, I now have full internet access wired and wireless. I also did something drastic but I think its a good idea. A while ago I ordered the system restore CD's from HP. After all these years I decided to use them so that the HP is now exactly like it was when I first got it. The OS is Windows 7. So from here I plan on installing Linux again into a couple of partitions which I will use more than win7 but at least I have windows on it in case something goes wonky or in those very rare instances where I need to use Windows.
I would like to thank everyone in this thread for your very informative suggestions which I learned a lot from. Very impressed!!
|
|
|
All times are GMT -5. The time now is 08:31 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|