Overclock.net banner
1 - 4 of 4 Posts

·
Linux Lobbyist
Joined
·
2,040 Posts
Discussion Starter · #1 ·
Kind of stumped. It boots fine in a VM, it boots fine on my main rig using the same USB drive. But when I try to boot it on my target system I get an unintelligible ISOLINUX error that I've never seen before;

Code:

Code:
ISOLINUX HEADER
WARNING: MISSING SYMBOL IN CONFIGURATION FILE: [GARBLED TEXT HERE]
WARNING UNKNOWN SYMBOL IN CONFIGURATION FILE: [GARBLED TEXT HERE]
WARNING: MISSING SYMBOL IN CONFIGURATION FILE: [GARBLED TEXT HERE]
Something along those lines - the garbled text looks like the line art characters for drawing things in terminals. Furthermore if I use "dd" or win32ImageWriter (effectively DD with a GUI) to write the image it just hangs with the standard ISOLINUX header - no errors. I'm presuming this has to do with the fact that this is the only UEFI system in my house - and this is an archaic version of ISOLINUX. Should I be fine tossing a 6.x binary in there (it's currently running a 4.0 binary)
 

·
Registered
Joined
·
152 Posts
I realise this is a late reply, but the fix for the ISOLINUX hanging at boot (without errors) is usually to disable any COM ports in the bios, as the isolinux.cfg file is set to listen on the serial console if it exists (frustrating!)
 
1 - 4 of 4 Posts
Top