http://qa.mandrakesoft.com/show_bug.cgi?id=2525

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|2.4.21-0.13mdk              |2.4.21-0.11mdk



------- Additional Comments From [EMAIL PROTECTED]  2003-03-24 16:51 -------
The problem is still valid with kernel 2.4.21-0.11mdk of mandrake 9.1-RC2, and
it is solved with the
"acpi=off" in the "append=.." line in lilo.conf, but then I am not able to switch
the computer off via software "halt" command, even if the apm deamon is runnig
correctly and the apm module is loaded at boot time. I always need to switch the
power off by hand after system halt.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date: 
description: 
I installed mandrake 9.1-rc1 on a pentium4 with sis55xx chipset motherboard from
Asus, and a sis900 ethernet card included in the motherboard. This machine is
connetted to another PC through an ethernet cable, to make a home local network.
Both Pcs have local assigned IP addresses 192.168.1.1(-> the "server") and
192.168.1.2(->the P4 with Mandrake). Apparently all devices are correctly
configured and the the eth0 interface is up, as the "ifconfig" command shows.
But a "ping" command on the other PC (192.168.1.1) does not give any result, it
does not see the other PC. Moreover, error messages of the form "Watchdog:
Network..timed out" continue to accumulate at the bottom of the "dmesg" output.
At first I wondered if it was a problem of network configuration, but it is not.
I tried to install and compile the official 2.4.20 kernel from the linux
sources, reinstalled LILO with this kernel and rebooted and everything worked
fine, I was also able to go to the internet through the other PC internet
connection. Then I installed the 2.4.21pre4-6mdk sources and compiled them with
the same configuration I used for 2.4.20 and again the network refused to work.
So the network did not work with the "custom" 2.4.21pre4-6mdk kernel I built,
neither with the precompiled 2.4.21pre4-6mdk kernel present in the distribution.

Thanks for any possible solution (for now I am using the 2.4.20 kernel)
Vincenzo

Reply via email to