Tested with kernel 3.13.1
Result:
Begins to boot, hangs during kernel loading, reports no hard disk found, then crashes and reboots.
Tested with kernel 3.13.1
Result:
Begins to boot, hangs during kernel loading, reports no hard disk found, then crashes and reboots.
Excellent. I am now testing this against other systems I had failing to boot the previous kernel or register.
Works. Just curious, what kernel version would this be considered?
Also, I assume Steam is up to date. Steam had an known issue mid to late last year that caused orphan files in many systems. They released an update that resolved the issue and cleaned up after its self.
Dell Vostro 220
BIOS: 1.3.0
FOG: 0.32
Kernel: 3.8.8
Begins to boot, but quickly fails:
tps:65010: no chip?
acpiphp_ibm: ibm_acpiphp_init: acpi_walk_namespace failed
cr_bllcd: INTEL CARILLO RANCH LPC not found.
Could not find Carillo Ranch MCH device.
uvesafb: failed to execute /sbin/v86d
uvesafb: make sure that the v86d helper is installed and executable
uvesafb: Getting VBE info block failed (eax=0x4f00, err=-2)
uvesafb: vbe_init() failed with -22
The following screen is scrambled. This occurs in every FOG boot option I have tried.
Dell PowerEdge R515
BIOS: 2.2.1
All other firmware current.
FOG: 0.32
Kernel: 3.8.8
Boots, but fails to recognize most of the hardware, and fails to connect through the network interface once the kernel is booted.
I have experienced this as well with a couple of odd Dell systems, and in the end it came down to issues with the network card driver. Some sort of firmware or BIOS mismatch compared to what the kernel wanted to see if I understand correctly. Considering this has exclusively been with newer Dell systems, I am not that shocked.
This couldn’t be a firewall thing could it?
I was never able to get my Ubuntu install to behave with any flavor of FOG, so I went back to Debian. Some issues arose and I realized I am not yet qualified for Linux software beta testing.