I'm trying to boot Fedora Core 5 Test 3 from either CD or DVD,
(which uses ISOLINUX), and I get the error messages:
Unknown keyword in config file
Could not find kernel image: linux
boot:
There are at least two other people in the world with the same
problem. Unfortunately, all of the rest of the Fedora test
community doesn't seem to have a problem with it, so its not
a high profile issue with the Fedora development team.
1/ If you enter a label, or let it timeout, you get the
"Could not find kernel image:" error response.
2/ After searching the syslinux mailing list, I've discovered that
if I manually type in the command line at the boot prompt,
it works. Since the default label in the file is 'linux',
I can boot this media by typing:
vmlinuz initrd=initrd.img
3/ The media uses "ISOLINUX 3.10 2005-08-24"
4/ An older version of Fedora Core that uses "ISOLINUX 3.08
2005-05-19"
works fine on the same hardware.
5/ I have no way of knowing what was on the mkisofs command line.
6/ The config file is fundamentally the same size and contents
in the older Fedora release, and the directory structure
is identical.
Collecting the comments from the various emails on the mailing
list, I've seen:
a) comments must have at least one space
b) 'append' statements must not cross line boundaries
c) make sure there are no line feeds at the end of lines
d) your cfg file is too big, there might be a problem
reading more than 8192 byte cfg files.
e) all the files must be in the same directory.
f) the kernel filename must not be greater than 8.3
Unfortunately, none of these seem to apply to what I find on
the Fedora Core 5, Test 3 media.
This is the config file:
default linux
prompt 1
timeout 600
display boot.msg
F1 boot.msg
F2 options.msg
F3 general.msg
F4 param.msg
F5 rescue.msg
label linux
kernel vmlinuz
append initrd=initrd.img
label text
kernel vmlinuz
append initrd=initrd.img text
label ks
kernel vmlinuz
append ks initrd=initrd.img
label local
localboot 1
label memtest86
kernel memtest
append -
Note: There _is_ a blank line at the end of the file.
The directory "/isolinux" on the media looks like this:
(as seen with "norock,nojoliet")
[root at localhost isolinux]# ll
total 6527
-r-xr-xr-x 1 root root 2048 Feb 16 15:09 boot.cat
-r-xr-xr-x 1 root root 292 Feb 16 14:49 boot.msg
-r-xr-xr-x 1 root root 919 Feb 16 14:49 general.msg
-r-xr-xr-x 1 root root 5051201 Feb 16 14:49 initrd.img
-r-xr-xr-x 1 root root 10584 Feb 16 14:49 isolinux.bin
-r-xr-xr-x 1 root root 366 Feb 16 14:49 isolinux.cfg
-r-xr-xr-x 1 root root 94600 Feb 16 14:49 memtest
-r-xr-xr-x 1 root root 788 Feb 16 14:49 options.msg
-r-xr-xr-x 1 root root 517 Feb 16 14:49 param.msg
-r-xr-xr-x 1 root root 490 Feb 16 14:49 rescue.msg
-r-xr-xr-x 1 root root 11035 Feb 16 14:49 splash.lss
-r-xr-xr-x 1 root root 2659 Feb 16 15:09 trans.tbl
-r-xr-xr-x 1 root root 1505560 Feb 16 14:49 vmlinuz
[root at localhost isolinux]#
So what can be wrong that only affects the three of us,
and not anyone else?
Comments and hypothesis are welcome.
(Note: I have no way of building a new ISO/media to test,
unless someone can give a quick (and easy) howto for
the Fedora Core dataset.)
TIA
Fulko
Fulko Hew wrote: 7>> I'm trying to boot Fedora Core 5 Test 3 from either CD or DVD, > (which uses ISOLINUX), and I get the error messages: > > Unknown keyword in config file > Could not find kernel image: linux > boot: > > > There are at least two other people in the world with the same > problem. Unfortunately, all of the rest of the Fedora test > community doesn't seem to have a problem with it, so its not > a high profile issue with the Fedora development team. >[...]> > So what can be wrong that only affects the three of us, > and not anyone else? > > Comments and hypothesis are welcome. > > (Note: I have no way of building a new ISO/media to test, > unless someone can give a quick (and easy) howto for > the Fedora Core dataset.) >Most likely the common denominator is that your particular BIOS misreads the isolinux.cfg file, getting garbage; thus it falls back to the default configuration (which is equivalent to an isolinux.cfg containing the single line "default linux".) The difference versus the older version of Fedora probably has more to do with the new disc having things in slightly different locations on the disc versus the older one. Note that 3.11 is the current version, not 3.10. The most helpful thing you could do is to find out if you and the other users have anything in particular in common (motherboard, BIOS, CD-ROM player, SCSI card if applicable, etc.) with your hardware. -hpa
Peter Jones <pjones at redhat.com> on 03/09/2006 03:41 PM wrote:> On Wed, 2006-03-01 at 19:43 -0800, H. Peter Anvin wrote: > > > >> The most helpful thing you could do is to find out if you and the > > >> other users have anything in particular in common (motherboard,BIOS,> > >> CD-ROM player, SCSI card if applicable, etc.) with your hardware. > > > > > > They are completely different systems, CD-ROMs, and BIOS. > > > But their BIOSs could have similar issues. > > > > List, please?This is what (I thought) I had already reported to Mr Anvin via an independent communications I've had in an attempt to help Fedora Core testing.> So far I've got reports of this on: > > eMachines T5026 > Delphin Clevo 2700t (bios from SystemSoft according to DMI) > fujistu-siemens amilo L1300 (notebook) > Acer Aspire 2023WLMiIt also happens on my Compal Cl-50.> Interestingly, at least on one emachines device, entering: > > /isolinux/vmlinuz initrd=/isolinux/initrd.img > > The CD will boot just fine.This also works on the Compal. I was the one who originally suggested the workaround. Actually, this also works: vmlinuz initrd=initrd.img> (Sorry about not getting 3.11 into the tree for FC5; it's been a very, > very busy release)
--- sorry, this is a possible duplicated message --- Peter Jones <pjones at redhat.com> on 03/09/2006 03:41 PM wrote:> On Wed, 2006-03-01 at 19:43 -0800, H. Peter Anvin wrote: > > > >> The most helpful thing you could do is to find out if you and the > > >> other users have anything in particular in common (motherboard,BIOS,> > >> CD-ROM player, SCSI card if applicable, etc.) with your hardware. > > > > > > They are completely different systems, CD-ROMs, and BIOS. > > > But their BIOSs could have similar issues. > > > > List, please?This is what (I thought) I had already reported to Mr Anvin via an independent communications I've had in an attempt to help Fedora Core testing.> So far I've got reports of this on: > > eMachines T5026 > Delphin Clevo 2700t (bios from SystemSoft according to DMI) > fujistu-siemens amilo L1300 (notebook) > Acer Aspire 2023WLMiIt also happens on my Compal Cl-50.> Interestingly, at least on one emachines device, entering: > > /isolinux/vmlinuz initrd=/isolinux/initrd.img > > The CD will boot just fine.This also works on the Compal. I was the one who originally suggested the workaround. Actually, this also works: vmlinuz initrd=initrd.img> (Sorry about not getting 3.11 into the tree for FC5; it's been a very, > very busy release)
On Wed Mar 1 17:15:35 PST 2006 Fulko Hew fhew3 at cogeco.ca wrote:> > I'm trying to boot Fedora Core 5 Test 3 from either CD or DVD, > (which uses ISOLINUX), and I get the error messages: > > Unknown keyword in config file > Could not find kernel image: linux > boot:I also see: Missing parameter in config file. invalid compressed format (err=2) When trying to launch Fedora Core 5.0 i386 from an IDE cdrom. I've downloaded the ISO images from mirrors.voyager.net about a week ago. I should do an md5sum to check that I'm working with valid media. I'm also running into this problem with a Micron client Pro. A Pentium II machine. The problem exists with and without my Adaptec SCSI card. Also using the Fedora Core 5 final release for i386. I have tried some of the earlier suggestions like: /isolinux/vmlinuz initrd=/isolinux/initrd.img This gets me a little further along, but then I receive a message proclaiming.... Uncompressing Linux... invalid compressed format (err=2) --System Halted In both cases I didn't have any IDE hard drive in the system. I'm booting from an IDE CDROM This box is notorious for not working well with IDE hard drives over 8 gigabytes in size. I get around this by having a boot drive with less than 8 gigabytes and making sure the BIOS doesn't try to detect the secondary IDE drive where most of my filesytems live. (I am talking about another machine of the same make and model which does have IDE hard drives). I have lots of these machines - Micron ClientPro. I get them for $25 each from a computer recycler in town. I just tried attaching a 4.3 Gigabyte IDE drive only and had the same failure. I'll google around a little bit more tonight to see if I can find a hack to get this to work. Thanks for SysLinux! I've seen it's name many times when I've booted Linux! Sincerely, Joe Baker Burlington Wisconsin