https://bugzilla.novell.com/show_bug.cgi?id=185165 lnelson15@houston.rr.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnelson15@houston.rr.com ------- Comment #24 from lnelson15@houston.rr.com 2006-10-09 21:14 MST ------- Just an aside, I have an ABIT VT-7 with a VIA VT6103 shown as a VT6102 in YAST Control Center Hardware information and DMESG output. The ETHO interface goes through a Netgear WGT624 router setup to serve IP and act as a de facto DHCP server. I have all my 4 versions of SUSE/Novell Linux on this box. As I have progressed up the install ladder from NLD 9 SP3, SUSE Enterprise Linux Desktop 10, SUSE Linux Desktop (Eval copy) and SUSE Linux Desktop 10.1 retail box, the ETHO interface has gone from the no issue to a severe issue. NLD9 has no network issues on ETHO. SLED seems to be okay. SLE 10 installed without the network manager and all other settings as install defaults the ETHO just seems to lose it's connection with the world haphazdly (i.e. I am not sure when it will bail....it just does sometime during a session. The SLE 10.1 version ETH0 setup with our without NetManager bails in short order also. When the NetManager tries to get an IP from the DHCP section of the router, the response is slow and I end up with one of the 168 addresses (usually doled out when no connection is found). I am not sure where to start with a resolution for the SLE 10.1 ( I have it uninstalled presently as my patience was thin looking for the problem with limited overall Linux skills in the sense of how the hardware is handle. I have looked at a lot of the log files mentioned here on bugzilla for similar issues but I am not really sure what I am looking for in relation to the ETHO interface bailing). I actually will probably move SLE 10.1 to another box but I hate walk away from a problem this severe. This post is just FYI. I am not sure where to place the bug issue with SLE 10.1 at this moment. I still am not sure where the issue is, just that my Rhine II (VT6103 discrete component on the mobo) ethernet interface is dropping out rather rapidly and cannot reconnect without rebooting. Usually when I reboot because of the network interface loss, the sound goes into a weird looping with whatever is playing at the moment as the desktop is being cleared off by the OS...some sort of odd IRQ problem maybe??? Best regards, Lee Nelson lnelson15@houston.rr.com PS I followed the SLE 10.1 Alpha and Beta process at opensuse.org, downloading and testing alot of the versions and did not notice this issue. I may have been doing it on a different box. Time has passed since this Spring....(In reply to comment #0)

In SUSE 10.0 everything works great. No matter how I install 10.1 either upgrade or new install the network and sound don't work. They are found and can configure them.

On boot I see a message where it is trying to load the network card. "SIOCSIFFLAGS Device or Resource Busy"

In var\log\messages I found a line where it tries to load the network that said: setup_irq: IRQ handler mismatch

I have a soyo sy-kt400 dragon ultra platinum edition. The built in ethernet is Via VT6102 Rhine II embeded ethernet on VT8235.

I have done one upgrade and 4 new installs. Each time I just selected the Gnome setup. Didn't add any other software.

I am using the retail version of 10.0 and 10.1.

Please let me know if there is anything I can do to help track down this bug.

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.