Re: [SLE] sis900 support in SuSE 9.1 is broken!

• Previous message: Erik Jakobsen: "Re: [SLE] CD Ripping Problems"
• In reply to: Marcos Vinicius Lazarini: "Re: [SLE] sis900 support in SuSE 9.1 is broken!"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

To: suse-linux-e@suse.com
Date: Thu, 19 Aug 2004 07:10:50 +0100

On Wednesday 18 Aug 2004 21:56, Marcos Vinicius Lazarini wrote:
> On Tue, 17 Aug 2004, peter Nikolic wrote:
> > On Tuesday 17 Aug 2004 17:25, Marcos Lazarini wrote:
> > > peter Nikolic wrote:
> > > > On Tuesday 17 Aug 2004 04:40, Marcos Vinicius Lazarini wrote:
> > > > > Hi,
> > > > >
> > > > > I was trying to install SuSE Linux Pro 9.1 using the ftp-version
> > > > > into an old Celeron Machine, with a sis900 Ethernet NIC. After
> > > > > running into a *lot* of trouble to make the sis900 Network Card
> > > > > work (logs were complaining about ISA Bridge), I discovered that
> > > > > it's support is broken in kernels from 2.6.3 to 2.6.5 (perhaps
> > > > > 2.6.6 also) here:
> > > > > http://teg.homeunix.org/sis900.html
> > > > > (Just to mention, last updated kernel from SuSE 9.1 uses 2.6.5)
> > > > > I could not find any reference thee this problem in the list's
> > > > > archives.
> > > > >
> > > > > In that page there is a patch to the kernel-source, but I was
> > > > > looking for a more easily maintained version - so I don't have to
> > > > > recompile the kernel myself to fix the security holes.
> > > > >
> > > > > My question: is it possible to restore sis900 support (using the
> > > > > simple patch in the page above) in the next update of the kernel
> > > > > image? Who can I mail to ask this change to be made in the next
> > > > > versions?
> > > > >
> > > > >
> > > > > Regards,
> > > > > Marcos Lazarini
> > > > > NICS Admin @ Unicamp - Brazil
> > > >
> > > > Hi ..
> > > >
> > > > I think sis900 support is just fine ..
> > > > 0000:00:04.0 Ethernet controller: Silicon Integrated Systems [SiS]
> > > > SiS900 10/100 Ethernet (rev 90) works just fine here never misses a
> > > > beat yast found it on install ok ..
> > > >
> > > > Try the latest Suse kernel 2.6.5-7.104-default the sis900 is ok and
> > > > aas far as i know the holes that existed have been plugged .
> > > >
> > > > Pete.
> > > >
> > > > --
> > > > Linux user No: 256242
> > > > Machine No: 139931
> > > > G6NJR Pete also MSA registered "Quinton 11"
> > > > A Linux Only area Happy bug hunting M$ clan
> > > > PGN
> > >
> > > That's the point. I have a board with different revision number.
> > >
> > > # lspci
> > > ...
> > > 0000:00:01.1 Ethernet controller: Silicon Integrated Systems [SiS]
> > > SiS900 10/100 Ethernet (rev 81)
> > > ...
> > >
> > > BTW, the module is installed but never used:
> > > # lsmod
> > > Module Size Used by
> > > ....
> > > sis900 19716 0
> > > ...
> > >
> > >
> > > I'll try to summarize what I found:
> > > Until kernel 2.6.3, sis900 had PCI device ID 0x10390008 (do cat
> > > /proc/bus/pci/devices to check yours). But this ID prevents SMBus to
> > > work correctly; to fix, they changed the PCI ID to 0x10390018 in
> > > versions 2.6.3 and after.
> > > According to the link above, the sis900 module was changed to detect
> > > the new PCI ID only after version 2.6.6.
> > >
> > > Right now, I'm waiting to finish the (long) compilation of my patched
> > > kernel (2.6.5-7.104-default) to see if it works.
> > >
> > > I also tried Knoppix, using the 2.6.6 kernel, and got the same problem.
> > >
> > >
> > > Regards,
> > > Marcos Lazarini
> >
> > Huimmmmmmm cant even make much sense of the listing at the moment
> > it is not making much sense right now still I'll look in the morning
> > when i wake up a bit just one thing is your eth on the MoBo or a PCI
> > card..?.
> > --
> > Linux user No: 256242
> > Machine No: 139931
> > G6NJR Pete also MSA registered "Quinton 11"
> > A Linux Only area Happy bug hunting M$ clan
> > PGN
>
> It's a PCChips board, with video-sound-modem-network on-board.
I've had worse used to use PC Chips myself not to many problems then a few
years ago always used to dissable the onboard video and use an PCI video card
seemed to work a lot better non of the system mem used for video
> (yeah, I
> know, it's terrible... you don't imagine how many linux-drivers-related
> problems this incredible piece-of-art chalenged us here)
>
> Good news! I'm writing this e-mail at the problematic machine, and the
> the patch to the kernel fixed my problem!
>
> But, checking my theory, I think the problem is not with the PCI ID from
> the sis900; it is related with the ID of the so called 'ISA Bridge' used
> by this module, and now (with a working system on my hands) my opinion is
> that the PCI ID of this 'ISA Bridge' was changed - that's explain (to me)
> why the module can be loaded without problems, but it refuses to its job.
>
> Below is a fragment of the /var/log/messages, generated using the
> instalation kernel:
> Aug 17 12:09:22 berimbau kernel: sis900.c: v1.08.07 11/02/2003
> Aug 17 12:09:22 berimbau kernel: PCI: Found IRQ 11 for device 0000:00:01.1
> Aug 17 12:09:22 berimbau kernel: PCI: Sharing IRQ 11 with 0000:00:0f.1
> Aug 17 12:09:22 berimbau kernel: eth0: Can not find ISA bridge
May 29 10:43:01 ds9 kernel: sis900.c: v1.08.07 11/02/2003
May 29 10:43:01 ds9 kernel: eth0: Realtek RTL8201 PHY transceiver found at
address 1.
May 29 10:43:01 ds9 kernel: eth0: Using transceiver found at address 1 as
default
May 29 10:43:01 ds9 kernel: eth0: SiS 900 PCI Fast Ethernet at 0xd400, IRQ 10,
00:0b:6a:27:fc:df.
take no notice of the date it is the same for the up-todate kernel i checked.

>
> (perhaps with a more detailed analysis of the kernel-source, someone
> should be able to conclude this)
>
>
> The fact is: my board is 'network-less' with the actual kernel-version
> used in SuSE 9.1!!!!!!!
>
Sounds more like a problem on board with IRQ's ect must admit i had no
problems with this one built onto this ASROCK MoBo (cheap version of an ASUS
from what i read) you have things like Plug&Play aware O/S Installed turned
OFF in the bios (more like Plug&Pray).
 
> Don't need to say that I'm not very happy to have
> to compile the kernel after each security update (not to mention the
> almost 6h compilation time), otherwise I would be using Gentoo Linux.
6 Hours Ouchh! not nice ..
>
> Is there any way we can solve this problem?? Help will be greatly
> appreciated.
>
>
> Regards,
> Marcos Lazarini

As you say it appears to be an issue with the particular ISA bridge in use on
that MoBo , I am not shure if playing with the resources in the bios may not
help like assigning an Fixed IRQ to the network chip or the ISA Bridge if it
can be done , Other than that it is down to supiouer (SP) brains than me to
solve it properly ..

Pete .

-- 
Linux user No: 256242
Machine    No: 139931
G6NJR  Pete  also MSA registered  "Quinton 11"
A Linux Only area  Happy bug hunting M$ clan
	PGN
 
-- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com

• Previous message: Erik Jakobsen: "Re: [SLE] CD Ripping Problems"
• In reply to: Marcos Vinicius Lazarini: "Re: [SLE] sis900 support in SuSE 9.1 is broken!"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]