You are not logged in.
I currently have arch Linux dual booted on my computer with windows 7 and one problem I am currently having is that the internet connection works in windows and when I boot into arch it works, but if I booted arch then restart into windows, the hardware is stuck in a state that Arch put it in when I booted into it. Reading online about this was suggested to disable wake on lan, but I have it off and that has not solved it. Is there a way to get Arch to release control of the ethernet device on my system so that Windows will not have problems?
Offline
What ethernet card are you using and which driver?
Offline
So you have to power cycle the machine for it to work again in Windows?
I'd see if there are updates available for Windows driver.
I wonder if it would help if you enabled booting from network in BIOS, maybe the BIOS will switch the adapter to some state usable by Windows.
As for disabling WoL, maybe they meant disabling it with ethtool on Linux - did you do that?
Offline
I am using the r8169 driver and my network hardware is "Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)" I have disabled WOL currently with the ethtool so should I try installing a newer realtek driver from realteks website for linux?
Offline
It sounds like the Linux driver is putting the network card into a strange state that a cold boot should clear.
I'd love to see the output of 'lspci -nnvk' with respect to your ethernet controller as well as the output of 'ip addr'.
Do you see anything about the ethernet controller in dmesg?
Offline
Output of ip addr:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether
inet 192.168.0.10/24 brd 192.168.0.255 scope global dynamic enp3s0
valid_lft 2722sec preferred_lft 2722sec
inet6 fe80:: scope link
valid_lft forever preferred_lft forever
Output of lspci:
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
Subsystem: Dell Device
Flags: bus master, fast devsel, latency 0, IRQ 35
I/O ports at d000 [size=256]
Memory at dc104000 (64-bit, prefetchable) [size=4K]
Memory at dc100000 (64-bit, prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 01
Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
Capabilities: [d0] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [160] Device Serial Number
Kernel driver in use: r8169
Kernel modules: r8169
Also the only thing I see in dmesg about the ethernet controller is the loading on system startup and what driver it is using.
Last edited by bo19 (2016-02-04 05:45:23)
Offline
@bo19,
Please use code tags for your output. Also, run the lspci command as root.
Offline
I found this based on that information:
https://en.opensuse.org/SDB:Realtek_8169_driver_problem
It says you should enable WoL on Windows as one of the possible work arounds.
Last edited by katsuki (2016-02-08 16:56:34)
Offline