[K12OSN] Re: K12OSN Digest, Vol 6, Issue 67

[Angus Carr]

This sounds like a problem I had with a laptop (Toshiba SatPro 4600) in 
FC2. Try adding "acpi=off" in the command line to the kernel. I did this 
in grub.conf.
Have a look in bugzilla.redhat.com for my name and you'll find a bug 
report.

In Toshiba's case, it was a buggy BIOS returning something wrong to 
acpi, and somehow that broke the NIC. It worked fine once I turned acpi off.

It's worth a try.

Angus Carr.

>Message: 1
>Date: Fri, 13 Aug 2004 23:32:18 -0400 (EDT)
>From: jam at mcquil.com
>Subject: Re: [K12OSN] Network problems w/4.1.0
>To: "Support list for opensource software in schools."
>	<k12osn at redhat.com>
>Message-ID:
>	<Pine.LNX.4.44.0408132331480.14966-100000 at BigDog.mcquil.com>
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>Jim,
>
>Any chance that the server nics are being detected in a different order, 
>therefore requiring you swap the 2 network cables ?
>
>Jim McQuillan
>jam at LTsp.org
>
>
>
>On Fri, 13 Aug 2004, Jim Kronebusch wrote:
>
>  
>
>>> I just upgraded my test 3.1.2 server to 4.1.0 (blew it away and installed 
>>> fresh).  But now I cannot get any clients to boot from it (doesn't get past 
>>> looking for DHCP address) and cannot ping past the local interface to the 
>>> external network.  I have tried 6 different NIC's and am currently using a 
>>> Intel Pro 100 and a LNE100TX.  I have reloaded 4.1.0 with all of the defaults 
>>> 3 times now (once disabling the firewall just in case) and still no luck.  I 
>>> have also gone back to 3.1.2 just to be sure I wasn't going insane and it 
>>> worked perfect with the same NIC's and the same clients.  Any ideas?  I just 
>>> ordered a server for a new school that my company is donating a lab too and I 
>>> wanted to test 4.1.0 with the clients we are giving them before the server 
>>> showed up.  But that isn't looking good at this point.
>>> 
>>> Right now I have a clean install of 4.1.0 with the Intel Pro 100 and a 
>>> LNE100TX installed and firewalling off.  Let me know if anyone has a 
>>> suggestion to try.  Or a tool to figure out why I cannot leave the box with a 
>>> simple ping request (error is "Destination Unreachable").
>>> 
>>> Thanks,
>>> 
>>> Jim Kronebusch
>>> Cotter Tech Department
>>> 507-453-5188
>>