http://qa.mandrakesoft.com/show_bug.cgi?id=2525
------- Additional Comments From [EMAIL PROTECTED] 2003-03-25 07:20 ------- On Mon, 2003-03-24 at 07:51, costavi wrote: I've encountered this on a few systems ... small number but I'm dealing with enough variety of systems that I have run across it ... there is a switch in the kernel build. The switch is under general and it is called Use Real mode APM BIOS call to power off. On the systems I've rebuilt it on this has solved the problem. The trouble is if the stock kernel cam with this switched on (it can't be done as a module) it causes more problems than it solves for systems that don't need it. This is a kernel switch designed for buggy bios's that don't shut down properly. Since MDK has to build for the majority. It can't be a default. But... it is there for those who need it. James ------- 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
