SIS ethernet driver question

[jasonaraymond at yahoo.com (Jason A. Raymond)]

discuss-request at blu.org wrote:
> 
> Send Discuss mailing list submissions to
>         discuss at blu.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://www.blu.org/mailman/listinfo/discuss
> or, via email, send a message with subject or body 'help' to
>         discuss-request at blu.org
> 
> You can reach the person managing the list at
>         discuss-admin at blu.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Discuss digest..."
> 
> Today's Topics:
> 
>    1. Re: New Cluster...problems recognizing ethernet adapter (Matthew J. Brodeur)
>    2. RE: Re: New Cluster...problems recognizing ethernet adapter (kgleason at ma.ultranet.com)
>    3. RE: Re: New Cluster...problems recognizing ethernet adapter (Matthew J. Brodeur)
>    4. Re: New Cluster...problems recognizing ethernet adapter (Christoph Doerbeck A242369)
>    5. RE: Re: New Cluster...problems recognizing ethernet adapter (kgleason at ma.ultranet.com)
> 
> --__--__--
> 
> Message: 1
> Date: Mon, 15 Apr 2002 13:31:02 -0400 (EDT)
> From: "Matthew J. Brodeur" <mbrodeur at NextTime.com>
> To: BLU Discuss List <Discuss at blu.org>
> Subject: Re: New Cluster...problems recognizing ethernet adapter
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Mon, 15 Apr 2002, kgleason at ma.ultranet.com wrote:
> 
> > getting it up and rolling. The motherboard is a 1Ghz K7S5A with an
> > onboard ethernet LAN. The card uses a Sis900 PCI Fast ethernet adapter
> > and works well under Windows98 but is not being recognized under Red Hat
> > Linux 6.2 (necessary version because I'm using Scyld's beowulf cluster
> 
> > I did find a copy of RTL8139 in /lib/modules/2.2.17-33.beobeoboot/net
> > and also found a copy of sis900.o in /lib/modules/22.17-33.beo/net.
> 
>    What do you mean by not recognized in Linux?  Has a NIC been detected
> and it's not loading properly, or was nothing detected?  Have you tried
> loading the sis900 module (modprobe sis900), and if so what errors did you
> get?  The output of "/sbin/lspci" might also be helpful in this search.
> 
> - --
>      -Matt
> 
> Time and tide wait for no man.
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iD8DBQE8uw5Zc8/WFSz+GKMRAgGrAKCLSN5xg1zoMrJPMtk+0tjDdJfLowCfWZwE
> zicD+WV0wvhBFbfHKD21+O0=
> =hWX6
> -----END PGP SIGNATURE-----
> 
> --__--__--
> 
> Message: 2
> Subject: RE: Re: New Cluster...problems recognizing ethernet adapter
> From: "kgleason at ma.ultranet.com" <kgleason at ma.ultranet.com>
> Date: Mon, 15 Apr 2002 18:41:14 -0400
> To: "mbrodeur at nexttime.com" <mbrodeur at nexttime.com>,
>         "discuss at blu.org" <discuss at blu.org>
> Reply-To: kgleason at ma.ultranet.com
> 
> No NIC was detected at startup.
> Tried to do modprobe sis900 then ifup eth0 but that didn't work either.
> I can't remember if I ever had this type problem before.
> 
> Do you have to move the object file sis900.o to another directory before it can be recognized at startup.
> Isn't there a way that I can assign that file at startup after Lilo? If so, then I don't know how.
> 
> Next time I'm on the system I'll try to copy the exact sequence and response but in the meantime...
> 
> Kevin
> 
> --------------------------------------------------------------------
> mail2web - Check your email from the web at
> http://mail2web.com/ .
> 
> --__--__--
> 
> Message: 3
> Date: Tue, 16 Apr 2002 08:43:15 -0400 (EDT)
> From: "Matthew J. Brodeur" <mbrodeur at NextTime.com>
> To: BLU Discuss List <discuss at blu.org>
> Subject: RE: Re: New Cluster...problems recognizing ethernet adapter
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Mon, 15 Apr 2002, kgleason at ma.ultranet.com wrote:
> 
> > No NIC was detected at startup.
> > Tried to do modprobe sis900 then ifup eth0 but that didn't work either.
> 
>    Hmmm, next time check the end of /var/log/messages or the output of the
> "dmesg" command for clues.  If the module has failed to load you'll
> usually get errors at the terminal.  Otherwise, any abnormalities will
> probably only show up in the logs.
>    Has eth0 been configured on this machine?  If the appropriate
> information doesn't exist in "/etc/sysconfig/network-scripts/ifcfg-eth0"
> then ifup won't work.  You can either use ifconfig to manually configure
> the interface, or run netconfig to create the config file for you.
> 
> > Do you have to move the object file sis900.o to another directory before
> > it can be recognized at startup. Isn't there a way that I can assign
> > that file at startup after Lilo? If so, then I don't know how.
> 
>    The module file should live in /lib/modules/[kernel-version], where the
> version is exactly what 'uname -r' returns on that system.  Network
> modules should be in a subdirectory called 'net'.  On a fully updated
> RH6.2 system sis900.o is in:
> /lib/modules/2.2.19-6.2.16/net
>    I *think* you're asking how to associate the sis900 module with the
> interface eth0, so that when the init scripts bring up networking the
> module gets loaded automagically.  In that case you'll need the following
> line in "/etc/modules.conf":
> alias eth0 sis900
> 
>    This is assuming that the sis900 driver is the correct one, and
> actually works.  If it turns out to be a different module, just use that
> name instead on the alias line.  Don't forget the "lspci" command if
> you're still stumped on which driver to use.  That should tell you what
> the NIC is calling itself, which someone (hopefully) can translate into an
> appropriate module name.
> 
> - --
>      -Matt
> 
> Facts are stubborn, but statistics are more pliable.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iD8DBQE8vBxmc8/WFSz+GKMRAsh5AJ9vQs9wAPp4ShIzjTZsm77nT/qPNACbBHMl
> ErtRn/enzAz6Tufc9robYz0=
> =2QTv
> -----END PGP SIGNATURE-----
> 
> --__--__--
> 
> Message: 4
> To: discuss at blu.org
> Subject: Re: New Cluster...problems recognizing ethernet adapter
> Date: Tue, 16 Apr 2002 09:11:28 -0400
> From: Christoph Doerbeck A242369 <cdoerbec at cso.fmr.com>
> 
> I have a system with a SisXXX network card (nice $6 item :-).  It's worked
> fine for months, although I did get frequent errors relating to SMP interrupt
> funk (not quite clear as to why).  I eventually swapped it out for a 3com.
> 
> But, I do remember that in order to get it to work on a RH62 system, I had
> to update the kernel to the very latest and greatest RH had pushed out.  The
> driver was NOT part of the out-of-the-box RH62 kernel.  Try updating your
> kernel...
> 
> Depending on how big your headache is going to be, perhaps you better off
> buying other network cards.  Plus, correct me if I'm wrong, but your network
> is the life blood of your cluster.  You sure you want to use the bottom
> of the barrel. Check the beowolf mail-lists and see what's worked well for
> other folks.
> 
> "kgleason at ma.ultranet.com" wrote:
> > I just bought a new cluster for the college lab and am in the process of gett
> > ing it up and rolling. The motherboard is a 1Ghz K7S5A with an onboard ethern
> > et LAN. The card uses a Sis900 PCI Fast ethernet adapter and works well under
> >  Windows98 but is not being recognized under Red Hat Linux 6.2 (necessary ver
> > sion because I'm using Scyld's beowulf cluster CDROM). I looked through the d
> > ocumentation with the motherboard and it said that it worked with non-K7S5A b
> > oards using RTL8139.o. I checked the windows side and saw it uses the Sis900
> > software
> > I did find a copy of RTL8139 in /lib/modules/2.2.17-33.beobeoboot/net and als
> > o found a copy of sis900.o in /lib/modules/22.17-33.beo/net.
> >
> > How do I get one of these to be recognized by my network?
> >
> > Kevin
> >
> > --------------------------------------------------------------------
> > mail2web - Check your email from the web at
> > http://mail2web.com/ .
> >
> > _______________________________________________
> > Discuss mailing list
> > Discuss at blu.org
> > http://www.blu.org/mailman/listinfo/discuss
> >
> 
> --__--__--
> 
> Message: 5
> Subject: RE: Re: New Cluster...problems recognizing ethernet adapter
> From: "kgleason at ma.ultranet.com" <kgleason at ma.ultranet.com>
> Date: Tue, 16 Apr 2002 09:27:34 -0400
> To: "cdoerbec at cso.fmr.com" <cdoerbec at cso.fmr.com>,
>         "discuss at blu.org" <discuss at blu.org>
> Reply-To: kgleason at ma.ultranet.com
> 
> Its those Sis900 NICs at fault. Last night I installed a 3Com card and it was recognized right off the bat. Still, I have=
>  five systems with Sis900 built-in  NICS and a low budget. RH says it has a bugfix for 62 because the sis900 didn't work =
> right out of the box. Now having trouble trying to locate the correct bugfix.
> 
> Kevin
> 
> Original Message:
> -----------------
> From: Christoph Doerbeck A242369 cdoerbec at cso.fmr.com
> Date: Tue, 16 Apr 2002 09:11:28 -0400
> To: discuss at blu.org
> Subject: Re: New Cluster...problems recognizing ethernet adapter
> 
> I have a system with a SisXXX network card (nice $6 item :-).  It's worked
> fine for months, although I did get frequent errors relating to SMP interrupt
> funk (not quite clear as to why).  I eventually swapped it out for a 3com.
> 
> But, I do remember that in order to get it to work on a RH62 system, I had
> to update the kernel to the very latest and greatest RH had pushed out.  The
> driver was NOT part of the out-of-the-box RH62 kernel.  Try updating your
> kernel...
> 
> Depending on how big your headache is going to be, perhaps you better off
> buying other network cards.  Plus, correct me if I'm wrong, but your network
> is the life blood of your cluster.  You sure you want to use the bottom
> of the barrel. Check the beowolf mail-lists and see what's worked well for
> other folks.
> 
> "kgleason at ma.ultranet.com" wrote:
> > I just bought a new cluster for the college lab and am in the process of gett
> > ing it up and rolling. The motherboard is a 1Ghz K7S5A with an onboard ethern
> > et LAN. The card uses a Sis900 PCI Fast ethernet adapter and works well under
> >  Windows98 but is not being recognized under Red Hat Linux 6.2 (necessary ver
> > sion because I'm using Scyld's beowulf cluster CDROM). I looked through the d
> > ocumentation with the motherboard and it said that it worked with non-K7S5A b
> > oards using RTL8139.o. I checked the windows side and saw it uses the Sis900
> > software
> > I did find a copy of RTL8139 in /lib/modules/2.2.17-33.beobeoboot/net and als
> > o found a copy of sis900.o in /lib/modules/22.17-33.beo/net.
> >
> > How do I get one of these to be recognized by my network?
> >
> > Kevin
> >
> > --------------------------------------------------------------------
> > mail2web - Check your email from the web at
> > http://mail2web.com/ .
> >
> > _______________________________________________
> > Discuss mailing list
> > Discuss at blu.org
> > http://www.blu.org/mailman/listinfo/discuss
> >
> 
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://www.blu.org/mailman/listinfo/discuss
> 
> --------------------------------------------------------------------
> mail2web - Check your email from the web at
> http://mail2web.com/ .
> 
> --__--__--
> 
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://www.blu.org/mailman/listinfo/discuss
> 
> End of Discuss Digest


A question on the SiS chipset in RH 6.2 ....would there be any
experimental driver support within the kernel options , and/or
experimental module options to compile into a new kernel ? I've had to
add support for other nics by recompiling these options with 2.2.17
builds, and even after a kernel update, STILL having to re-compile ...
maybe there is further documentation in /usr/src/linux somewhere...???

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com