Posts made by Chuck Sites

[SIZE=3]Chalk one up either to flaky hardware or Gremlins! I was testing this issue further and decided to test the power cycle again, but this time I did a deep power cycle; (power the machine down, pull the plug from the power supply, wait, plug it back in, power back on). Before I was just doing a front button power cycle. Well, that seems to fix it! [/SIZE]

[SIZE=3]Just so you know I’m not mad, this is from dmesg when the network card would block;[/SIZE]

Linux Kernel 3.13.6

e1000e: Intel PRO/1000 Network Driver - 2.3.2-K
e1000e: Copyright 1999-2013
e1000e: 0000:00:19.0 Interupt Throttling Rate(ints/sec) set to dynamic conservative mode
e1000e: 0000:00:19.0 eth0 10/100 speed disabling TSO
Sending DHCP request … timed out!
IP-Config: Reopening network devices
e1000e: eth0 NIC Link is Up 100 Mbs Full Duplex, Flow Control: Rx//Tx

Anyway I suspect that the deep power cycle cleaned the memory of Intel chip and forced it to reload. So now it’s working perfect and I can’t reproduce the problem.

So add deep power the machine down, pull the plug from the power supply, wait, plug it back in, power back on cycle to your bag of tricks to try with the Dell Vostros 400s.

Case closed.

Hi All. I’m a big fan of FOG. I hope to contribute back some.

I’m running FOG 0.33B from the latest svn update with my own patches to allow it to run on Mageia4. It’s all working very well and I love the new ipxe method. Very slick.

I have a problem though with the current bzImage on a Dell Vostros 400. These Dells use an on-board intel
82562V-2 10/100 chipset. When it net boots bzImage it scrambles this chip (firmware bug?) and makes the network un-usable (even through a power-cycle). It is unscrambled only until after to boots into windows 7! It’s bizarre, but true. So I had fog boot bzImage into debug mode and at the command line, you can see in (‘dmesg’)
the intel e100 driver entry, the e1000 entry and then an e1000e entry and initialization. The ethernet port is hung
completely, pings don’t work etc. Another complete boot into windows 7 clears the problem.

To prove the issue with bzImage, I used another FOG 3.2 (using kernel 2.6.29.1) and it had no problem the 82562V2 chipset, and worked just fine.

Does anyone have any advise on what may-be happening? Is wrong firmware being put into this chip? Would building a kernel without the E1000e.

Thanks.