Bug 112624 - No suitable Network driver for MSI 915P/G Neo2 motherboard
Summary: No suitable Network driver for MSI 915P/G Neo2 motherboard
Status: RESOLVED DUPLICATE of bug 98928
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Beta 2
Hardware: i686 SUSE Other
: P5 - None : Critical
Target Milestone: ---
Assignee: Karsten Keil
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-24 07:31 UTC by Heiko Münkel
Modified: 2005-08-25 11:04 UTC (History)
0 users

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Heiko Münkel 2005-08-24 07:31:24 UTC
The motherboard MSI 915P/G Neo2 has a Syskonnect Gigabit Ethernet 984x
compatible chip which doesnt't work with the sk98lin driver in the kernel of
SUSE Linux 10.0 beta 2. On the website
http://www.syskonnect.com/syskonnect/support/driver/zip/linux/ is a newer
version of the driver (install-8_23.tar.bz), which works fine with the specified
card.
Comment 1 Olaf Kirch 2005-08-24 11:04:06 UTC
Hi, 
 
our current kernel of the day should contain the new sky2 driver, which 
supports the Yukon2 chipset from SysKonnect. Can you give this kernel a 
try please? 
 
the KOTD can be downloaed from ftp://ftp.suse.com/pub/people/mantel/kotd 
Comment 2 Heiko Münkel 2005-08-24 21:00:33 UTC
(In reply to comment #1)
> Hi, 
>  
> our current kernel of the day should contain the new sky2 driver, which 
> supports the Yukon2 chipset from SysKonnect. Can you give this kernel a 
> try please? 
>  
> the KOTD can be downloaed from ftp://ftp.suse.com/pub/people/mantel/kotd 

I'll try it until Friday.
Comment 3 Karsten Keil 2005-08-25 11:04:22 UTC
Unfortunatly the sky2 driver still has problems under load, it stops 
receiving, I'm debuging this now. 
Since it's all the same Yukon2 problem, I'll handle it in one bug now. 

*** This bug has been marked as a duplicate of 98928 ***