Skip to contentSkip to conversation

SiS900 driver after v.1.07.11 (==Linux 2.4.5) won't allow connect.

DISCUSSION Mike 2 participants 4 messages Jan 8, 2002

lore
Share & tools
lore

Mike

author
#0 lore raw

Hello,

I've got this weird problem, I know the problem is mine 'cuz the latest in 2.4.17 doesn't work either, and I don't think Linus would keep a bad copy of widely-used code in his kernel, right? ;-)
Anyway, the hardware in question is an ECS K7S5A motherboard with a SiS735 chipset and on-board LAN. The only Realtek chip I see on the mainboard is one marked "RTL8201L".

WHAT HAPPENS WHEN IT WORKS (flawlessly):
With a modular kernel 2.4.5 I simply 'modprobe sis900' and presto...I follow that with 'dhcpcd' and I'm on the 'net. Here's what syslog says:
SiS900.c: v.1.07.11 4/10/2001
PCI: Assigned IRQ3 for device 00:03.0
eth0: Unknown PHY transceiver found at address 1 <<<-------!!!!
eth0: Using transceiver found at address1 as default
eth0: SiS900 PCI Fast Ethernet at 0xdc00, IRQ3, <MAC-address here>
logger: (dhcpcd) IP changed to <IP-address here>

WHAT HAPPENS WHEN IT FAILS:
With a modular kernel 2.4.6 or 2.4.13 or 2.4.17 I 'modprobe sis900' and get:
SiS900.c: v.1.08.01 9/25/2001 <<<--------Some kernels differ accordingly in version and date. All >=1.08 fail.
PCI: Assigned IRQ3 for device 00:03.0
eth0: Realtek RTL8201 PHY transceiver found at address 1
eth0: Using transceiver found at address1 as default
eth0: SiS900 PCI Fast Ethernet at 0xdc00, IRQ3, <MAC-address here>

I follow this with 'dhcpcd' and syslog says:
Media Link ON 10mbps half-duplex
....And my prompt hangs there until dhcpcd time-outs after 3 or 5 minutes...

What am I missing here? Should I add some stuff to the 'modprobe sis900' string now??
And yeah, I've read all the relevant (?!) docs in the kernel sources. Also, linux-2.4.17/Documentation/networking/sis900.txt only goes up to v.1.07, shouldn't it reflect the current revision (1.08.01)??

I hope it's possible to just copy the old 2.4.5 source into the 2.4.17 dir (as you can tell: I've never done this) and compile. TIA for any help and greets!
-Mike

author
#1 lore raw

Heh, just read about the 2.4.18pre1 sis900 patch, I wonder if that'll be what it takes...I'm compiling it now.
Will reply with results.
Gtreets, Mike

Quoted 44 lines · I wrote:

Hello,

I've got this weird problem, I know the problem is mine 'cuz the latest in 2.4.17 doesn't work either, and I don't think Linus would keep a bad copy of widely-used code in his kernel, right? ;-)
Anyway, the hardware in question is an ECS K7S5A motherboard with a SiS735 chipset and on-board LAN. The only Realtek chip I see on the mainboard is one marked "RTL8201L".

WHAT HAPPENS WHEN IT WORKS (flawlessly):
With a modular kernel 2.4.5 I simply 'modprobe sis900' and presto...I follow that with 'dhcpcd' and I'm on the 'net. Here's what syslog says:
SiS900.c: v.1.07.11 4/10/2001
PCI: Assigned IRQ3 for device 00:03.0
eth0: Unknown PHY transceiver found at address 1 <<<-------!!!!
eth0: Using transceiver found at address1 as default
eth0: SiS900 PCI Fast Ethernet at 0xdc00, IRQ3, <MAC-address here>
logger: (dhcpcd) IP changed to <IP-address here>

WHAT HAPPENS WHEN IT FAILS:
With a modular kernel 2.4.6 or 2.4.13 or 2.4.17 I 'modprobe sis900' and get:
SiS900.c: v.1.08.01 9/25/2001 <<<--------Some kernels differ accordingly in version and date. All >=1.08 fail.
PCI: Assigned IRQ3 for device 00:03.0
eth0: Realtek RTL8201 PHY transceiver found at address 1
eth0: Using transceiver found at address1 as default
eth0: SiS900 PCI Fast Ethernet at 0xdc00, IRQ3, <MAC-address here>

I follow this with 'dhcpcd' and syslog says:
Media Link ON 10mbps half-duplex
....And my prompt hangs there until dhcpcd time-outs after 3 or 5 minutes...

What am I missing here? Should I add some stuff to the 'modprobe sis900' string now??
And yeah, I've read all the relevant (?!) docs in the kernel sources. Also, linux-2.4.17/Documentation/networking/sis900.txt only goes up to v.1.07, shouldn't it reflect the current revision (1.08.01)??

I hope it's possible to just copy the old 2.4.5 source into the 2.4.17 dir (as you can tell: I've never done this) and compile. TIA for any help and greets!
-Mike

author
#2 lore raw
In reply to Mike

Darn, same problem as before; it gives me "Media Link ON 10mbps half-duplex" but now atleast dhcpcd doesn't fail.
What's worse: I pinged my nameserver across the street and lost 10% of 19 pings. Dunno if "half-baked-duplex" is what does that...but I'm still forced to use 2.4.5 for now. :'-(

Quoted 51 lines · I wrote:

Heh, just read about the 2.4.18pre1 sis900 patch, I wonder if that'll be what it takes...I'm compiling it now.
Will reply with results.
Gtreets, Mike

Quoted 44 lines · I wrote:

Hello,

I've got this weird problem, I know the problem is mine 'cuz the latest in 2.4.17 doesn't work either, and I don't think Linus would keep a bad copy of widely-used code in his kernel, right? ;-)
Anyway, the hardware in question is an ECS K7S5A motherboard with a SiS735 chipset and on-board LAN. The only Realtek chip I see on the mainboard is one marked "RTL8201L".

WHAT HAPPENS WHEN IT WORKS (flawlessly):
With a modular kernel 2.4.5 I simply 'modprobe sis900' and presto...I follow that with 'dhcpcd' and I'm on the 'net. Here's what syslog says:
SiS900.c: v.1.07.11 4/10/2001
PCI: Assigned IRQ3 for device 00:03.0
eth0: Unknown PHY transceiver found at address 1 <<<-------!!!!
eth0: Using transceiver found at address1 as default
eth0: SiS900 PCI Fast Ethernet at 0xdc00, IRQ3, <MAC-address here>
logger: (dhcpcd) IP changed to <IP-address here>

WHAT HAPPENS WHEN IT FAILS:
With a modular kernel 2.4.6 or 2.4.13 or 2.4.17 I 'modprobe sis900' and get:
SiS900.c: v.1.08.01 9/25/2001 <<<--------Some kernels differ accordingly in version and date. All >=1.08 fail.
PCI: Assigned IRQ3 for device 00:03.0
eth0: Realtek RTL8201 PHY transceiver found at address 1
eth0: Using transceiver found at address1 as default
eth0: SiS900 PCI Fast Ethernet at 0xdc00, IRQ3, <MAC-address here>

I follow this with 'dhcpcd' and syslog says:
Media Link ON 10mbps half-duplex
....And my prompt hangs there until dhcpcd time-outs after 3 or 5 minutes...

What am I missing here? Should I add some stuff to the 'modprobe sis900' string now??
And yeah, I've read all the relevant (?!) docs in the kernel sources. Also, linux-2.4.17/Documentation/networking/sis900.txt only goes up to v.1.07, shouldn't it reflect the current revision (1.08.01)??

I hope it's possible to just copy the old 2.4.5 source into the 2.4.17 dir (as you can tell: I've never done this) and compile. TIA for any help and greets!
-Mike

#3 lore raw
In reply to Mike

try a temp. solution,
but keep trying to get this fixed

copy the last drivers from the kernel that works into the new kernel tree. that's what I do, because the drivers (kernel 2.4.4+) is incompatible with my switch

Rune Petersen
----- Original Message -----
From: Mike <[email protected]>
To: LKML <[email protected]>
Cc: <[email protected]>; Jeff Garzik <[email protected]>
Sent: Tuesday, January 08, 2002 8:21 AM
Subject: Re: SiS900 driver after v.1.07.11 (==Linux 2.4.5) won't allow connect.

Quoted 1 line

Darn, same problem as before; it gives me "Media Link ON 10mbps

half-duplex"

Quoted 3 lines

but now atleast dhcpcd doesn't fail.
What's worse: I pinged my nameserver across the street and lost 10% of 19 pings. Dunno if "half-baked-duplex" is what does that...but I'm still

forced

Quoted 15 lines

to use 2.4.5 for now. :'-(

Quoted 10 lines · I wrote:

Heh, just read about the 2.4.18pre1 sis900 patch, I wonder if that'll be what it takes...I'm compiling it now.
Will reply with results.
Gtreets, Mike

Quoted 3 lines · I wrote:

Hello,

I've got this weird problem, I know the problem is mine 'cuz the

latest

Quoted 1 line
Quoted 1 line
Quoted 1 line

in 2.4.17 doesn't work either, and I don't think Linus would keep a

bad

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

copy of widely-used code in his kernel, right? ;-) Anyway, the hardware in question is an ECS K7S5A motherboard with a SiS735 chipset and on-board LAN. The only Realtek chip I see on the mainboard is one marked "RTL8201L".

WHAT HAPPENS WHEN IT WORKS (flawlessly):
With a modular kernel 2.4.5 I simply 'modprobe sis900' and presto...I follow that with 'dhcpcd' and I'm on the 'net. Here's what syslog

says:

Quoted 9 lines
Quoted 9 lines
Quoted 9 lines

SiS900.c: v.1.07.11 4/10/2001
PCI: Assigned IRQ3 for device 00:03.0
eth0: Unknown PHY transceiver found at address 1 <<<-------!!!!
eth0: Using transceiver found at address1 as default
eth0: SiS900 PCI Fast Ethernet at 0xdc00, IRQ3, <MAC-address here>
logger: (dhcpcd) IP changed to <IP-address here>

WHAT HAPPENS WHEN IT FAILS:
With a modular kernel 2.4.6 or 2.4.13 or 2.4.17 I 'modprobe sis900'

and

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

get:
SiS900.c: v.1.08.01 9/25/2001 <<<--------Some kernels differ

accordingly

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

in version and date. All >=1.08 fail.
PCI: Assigned IRQ3 for device 00:03.0
eth0: Realtek RTL8201 PHY transceiver found at address 1
eth0: Using transceiver found at address1 as default
eth0: SiS900 PCI Fast Ethernet at 0xdc00, IRQ3, <MAC-address here>

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

I follow this with 'dhcpcd' and syslog says:
Media Link ON 10mbps half-duplex
....And my prompt hangs there until dhcpcd time-outs after 3 or 5 minutes...

What am I missing here? Should I add some stuff to the 'modprobe

sis900'

Quoted 15 lines
Quoted 9 lines
Quoted 9 lines

string now??
And yeah, I've read all the relevant (?!) docs in the kernel sources. Also, linux-2.4.17/Documentation/networking/sis900.txt only goes up to v.1.07, shouldn't it reflect the current revision (1.08.01)??

I hope it's possible to just copy the old 2.4.5 source into the 2.4.17 dir (as you can tell: I've never done this) and compile. TIA for any help and greets!
-Mike

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/