Was helping a friend the other day with a similiar problem... problem was resolved by disabling acpi during boot stage. acpi=off should do it. If it's a problem with the routines for acpi. Pagan On Wednesday 28 May 2003 10:53, bis9170@cox.net wrote:
Hi all:
I was running SuSE 8.2 fine with my older ASUS motherboard and Athlon 1.2GHz. Over the weekend, I purchased a Azza motherboard and an Athlon 2.2GHz, and installed it into my system. I was happy to see SuSE not hickup one bit with the new heart-and-soul. But when I had to shutdown my system and restart it, that's when things got weird.
First thing was SuSE "found new hardware", i.e. my generic 10/100 Network card. It wanted to assign this "second NIC" eth1. At the same time, my eth0 card would not respond to any pings on my internal network, nor could it ping anything but itself (192.168.0.2). Tried using the fake eth1, to no avail.
I've swapped NIC cards, and have moved the card to different PCI slots. The motherboard does not have an integrated NIC, so there should be no conflicts there.
I've reloaded from scratch, and while SuSE picks up on my NIC, it still doesn't ping external to itself, or respond to any pings from the network. And ever since I've reloaded from scratch, my SoundBlaster Live! Pro is not even being recognized anymore.
Do you think I have a BIOS/motherboard issue, or am I missing something more basic/obvious...? Thanks.
V/R, Todd