sis900 and fedora troubles

sis900 and fedora troubles

[Damian]

1) I'm having trouble with the sis900 chipset on an Acer Aspire 3000
Laptop using Fedora Core 4, which I believe uses 2.6.11. The NIC is
detected perfeclty by fedora but it fails to initialize. When I set it
for dhcp the dhcp request simply times out. I have tried this laptop
with ubuntu linux and it works perfectly out of the box so I cannot
explain why it wouldn't work in fedora.

2) 
Error: Determining IP information for eth0... failed. (redhat gui
network config)

Error: eth0: Transmit timeout, status 00000005 000002
(/var/log/messages)

3) dmesg: card is detected.

I am so very sorry I can't give you more output, but the laptop is
virtually connectionless. All I can tell you is that Ubuntu ran the card
fine but Fedora for some reason doesn't. Any info is highly appreciated.

Damian

Re: sis900 and fedora troubles

[Francois Romieu]

Damian <res0d26i@verizon.net> :
[...]
> I am so very sorry I can't give you more output, but the laptop is
> virtually connectionless. All I can tell you is that Ubuntu ran the card
> fine but Fedora for some reason doesn't. Any info is highly appreciated.

The exact revisions for both kernels are needed as a start. The complete
dmesg would be welcome as well (if it gets truncated, the missing bits
are probably stored in some distro-specific localtion, see /var/log for 
instance).

So far it is not even clear if it should be bugzilled in Fedora or in Ubuntu
(anyway, if changes can not be tested due to the lack of connection... :o/ ).

--
Ueimor

Re: sis900 and fedora troubles

[Daniele Venzano]

Il giorno 26/giu/05, alle ore 10:50, Francois Romieu ha scritto:

> The exact revisions for both kernels are needed as a start. The  
> complete
> dmesg would be welcome as well (if it gets truncated, the missing bits
> are probably stored in some distro-specific localtion, see /var/log  
> for
> instance).
>
> So far it is not even clear if it should be bugzilled in Fedora or  
> in Ubuntu
> (anyway, if changes can not be tested due to the lack of  
> connection... :o/ ).

I asked Damian (but forgot to CC the list) to check the sis900 driver  
version strings printed by the two configurations. I fear that Fedora  
is still using an old version of sis900, as I remember to have fixed  
a similar issue on the same hardware.

--
Daniele Venzano
http://www.brownhat.org