[opensuse-kernel] e100 not finding PHY after rebooting from Windows
Hi all, probably not really a topic for opensuse-kernel, but you guys can hopefully tell me whom to contact... Hardware: * lenovo ideacentre q150, atom d525, nvidia ion2 chipset * ethernet: e100 82552 Software: * opensuse 12.1 (with or without KOTD does not matter) * no proprietary nvidia drivers (nouveau does just fine) * no BIOS update available Problem: * ethernet e100 works fine if cold booted from *power plug removed*, fails if rebooted from Windows. Shutting down windows and powering up does not help, only removing the power supply does help * debug=16 shows that all register reads in the botched case are something like 0x????FFFF and finally the PHY is "unknown" and thus the interface does not work. The latest e100 driver from the intel site is > 5 years old and has a lower version number than the one in the kernel, so I did not even try it. Once I'm home again I can wire up the machine and provide the different entries from the working and non-working case after "modprobe e100 debug=16" I'm grateful for any hints :-) -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Problem: * ethernet e100 works fine if cold booted from *power plug removed*, fails if rebooted from Windows. Shutting down windows and powering up
You mean to say you need to reboot the modem.
Once I'm home again I can wire up the machine and provide the different entries from the working and non-working case after "modprobe e100 debug=16"
You are just doing a power down in the case of positive scenario is what you mean. I think the most advisable thing to do is to look at vendor documentation for your modem both offline and online or google for "modem reboot required linux/windows". The interesting things that I found are below. https://wiki.archlinux.org/index.php/Configuring_Network#Realtek_no_link_.2F... https://wiki.archlinux.org/index.php/Configuring_Network -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Hi Sujit, Am 27.12.2011 09:30, schrieb Sujit Karatparambil:
Problem: * ethernet e100 works fine if cold booted from *power plug removed*, fails if rebooted from Windows. Shutting down windows and powering up
You mean to say you need to reboot the modem.
(it's not a modem, it's a small sized desktop with atom CPU) No, rebooting from Windows into Linux does break ethernet (on linux, rebooting back into windows the ethernet works just fine). I need to remove power (just shutting down is not enough!) and then boot directly into linux to make ethernet work.
Once I'm home again I can wire up the machine and provide the different entries from the working and non-working case after "modprobe e100 debug=16"
You are just doing a power down in the case of positive scenario is what you mean.
I think the most advisable thing to do is to look at vendor documentation for your modem both offline and online or google for "modem reboot required linux/windows".
The interesting things that I found are below.
https://wiki.archlinux.org/index.php/Configuring_Network#Realtek_no_link_.2F... https://wiki.archlinux.org/index.php/Configuring_Network
It's an intel chip, (a very old one btw) and thus I don't think it is related, but I'll try playing with the Wake on LAN settings to see if they change anything. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
It's an intel chip, (a very old one btw) and thus I don't think it is related, but I'll try playing with the Wake on LAN settings to see if they change anything.
Yes but have you upgraded the driver. Any upgrade on the windows. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 2011/12/27 17:06 (GMT+0530) Sujit Karatparambil composed:
It's an intel chip, (a very old one btw) and thus I don't think it is related, but I'll try playing with the Wake on LAN settings to see if they change anything.
Yes but have you upgraded the driver. Any upgrade on the windows.
I would think the driver for the ancient e100 82552 chip would have fully matured in antiquity. IIRC, the "newest" drivers for my many e100 82552 chips are at least 7 years old. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
participants (3)
-
Felix Miata -
Stefan Seyfried -
Sujit Karatparambil