[SOLVED] Error booting the new release (kernel image "whichsys.c32")

DSpider · 2012-07-24 16:48:10

In an effort to update the "Without overwriting the USB drive" article on the Arch wiki, I found myself unable to boot from it.

Here's what I did (all were ran with sudo):

# mount -o loop /media/Backup/archlinux-*.iso /mnt/iso
# mount /dev/sdc1 /mnt/usb
# cp -r /mnt/iso/arch /mnt/usb

# extlinux --install /mnt/usb/arch/boot/syslinux
/mnt/usb/arch/boot/syslinux is device /dev/sdc1

# dd bs=440 conv=notrunc count=1 if=/usr/lib/syslinux/mbr.bin of=/dev/sdc
1+0 records in
1+0 records out
440 bytes (440 B) copied, 0.0114489 s, 38.4 kB/s

# parted /dev/sdc toggle 1 boot
Information: You may need to update /etc/fstab.

And here's what I'm getting:

SYSLINUX 4.05 EDD 0x4f5727e3 Copyright (C) 1994-2011 H. Peter Alvin et al
Could not find kernel image: boot/syslinux/whichsys.c32
boot: _

If I press Tab, I can see:

 select pxe sys

If I type either one and press enter...

boot: select
Could not find kernel image: boot/syslinux/whichsys.c32
boot: sys
Could not find kernel image: boot/syslinux/archiso_sys_choose.cfg

What am I doing wrong? This is not my first rodeo with Syslinux... It's probably worth noting that labelling it "ARCH_201207" or not doesn't really matter (at this point); I should be getting the install menu since the bootloader is installed fine. Could it have something to do with the APPEND line from syslinux.cfg?

Last edited by DSpider (2012-07-24 23:26:49)

DSpider · 2012-07-24 17:54:08

Using "dd" on the same image works:

# dd if=/media/Backup/archlinux-2012.07.15-netinstall-dual.iso of=/dev/sdc
757760+0 records in
757760+0 records out
387973120 bytes (388 MB) copied, 133.171 s, 2.9 MB/s

But it's strange, it uses the same directory structure... I don't get it.

djgera · 2012-07-24 20:33:09

OH NO! something changed in syslinux-4.05, since this structured was unified (was working with 4.04) :s Researching...

It works with hybrid-mbr because ISOLINUX is used.

DSpider · 2012-07-24 20:40:56

Should I file a bug report?

Edit: Or at least, is there a workaround till the next release (next month) ?

Last edited by DSpider (2012-07-24 20:43:39)

djgera · 2012-07-24 20:57:57

If you want, anyway I am the maintainer of archiso...

yes, you can workaround

sed -i "s|../../|/arch|" /mnt/arch/boot/syslinux/syslinux.cfg

djgera · 2012-07-24 21:00:52

git commit reference: https://projects.archlinux.org/archiso. … 77c9a262a2

djgera · 2012-07-24 21:45:18

The issue is when using FAT filesystem, does not happen on other like EXT4. Should be fixed in next syslinux version.

http://www.syslinux.org/archives/2012-June/017752.html

DSpider · 2012-07-24 23:26:27

djgera wrote:

If you want, anyway I am the maintainer of archiso...

Then there's no need; it has been brought to your attention.

Confirmed that it only happens on FAT (well, FAT32... I don't plan on testing it with FAT16; that fs is from 1987). And while "APPEND /arch" works both on FAT32 and EXT4, I think I like "../../" better, because I think it can work with an "Arch Linux" top dir, as long as I install Syslinux there:

# extlinux --install "/mnt/usb/Arch Linux/boot/syslinux"

But I think that's a subject for a different topic. On the first try it has issues with the aitab file... Perhaps I'll start a new thread tomorrow after a few trial-and-error approaches.

Thanks. Marked as solved.

Last edited by DSpider (2012-07-25 11:22:56)

djgera · 2012-07-24 23:39:41

Spaces in filenames is not a good idea...

Carharttjimmy · 2012-08-17 20:08:25

Hi, I am getting an error just like this, but the work around does not work. What should I do?

It keeps saying that it could not find the kernel image.

Last edited by Carharttjimmy (2012-08-17 20:27:57)

djgera · 2012-08-17 20:18:59

Please post each steps are you doing.

Carharttjimmy · 2012-08-17 20:28:34

I was using pendrive linux and after being directed to another image writer, it works.

I was using a windows machine to burn the media.

dbourgeo · 2013-02-20 14:37:41

I still had to set "APPEND=/arch" instead of "APPEND=../.." (going by memory here, but I did what the proposed solution was that was posted above).

I tried to create a FAT32 USB Stick to boot from, using the manual method like the original poster.

This was for the ARCH_201302 release.

DSpider · 2013-02-20 17:01:22

It means that you haven't read the instructions and that you probably just skimmed through it.

https://wiki.archlinux.org/index.php/US … _USB_drive

If the syslinux package on your distribution is older than version 4.06, as a workaround for FAT32 filesystems (unnecessary for EXT4), the APPEND line from syslinux.cfg should also be replaced:
$ sed -i "s|../../|/arch|" syslinux.cfg

Edit: Don't just run the above command. The prerequisite for the command is:

$ cd /media/somefolder/arch/boot/syslinux    #Where somefolder is the USB drive's mount point. Do not skip this step.

(Or you could specify the entire path):

$ sed -i "s|../../|/arch|" /media/somefolder/arch/boot/syslinux/syslinux.cfg

Last edited by DSpider (2013-02-20 17:07:09)

dbourgeo · 2013-02-20 22:18:22

My system won't boot right now, so I created the usb image from an old CD I had lying around. I have it labelled "ARCH 2011-08-19". I guess it is safe to say that is old enough to run into this problem (I can't boot it right now to find out, as I am cloning a disk). I did get the USB to boot no problem after I made the change.

Just now: I looked it up here on archlinux.org, it did have the 4.04 version of syslinux. So, the problem is still solved.

For some reason I thought syslinux 4.06 was more ancient than the CD -- I did read that note. Sorry for the confusion.

Thanks!

Last edited by dbourgeo (2013-02-20 22:21:07)

Arch Linux

#1 2012-07-24 16:48:10

[SOLVED] Error booting the new release (kernel image "whichsys.c32")

#2 2012-07-24 17:54:08

Re: [SOLVED] Error booting the new release (kernel image "whichsys.c32")

#3 2012-07-24 20:33:09

Re: [SOLVED] Error booting the new release (kernel image "whichsys.c32")

#4 2012-07-24 20:40:56

Re: [SOLVED] Error booting the new release (kernel image "whichsys.c32")

#5 2012-07-24 20:57:57

Re: [SOLVED] Error booting the new release (kernel image "whichsys.c32")

#6 2012-07-24 21:00:52

Re: [SOLVED] Error booting the new release (kernel image "whichsys.c32")

#7 2012-07-24 21:45:18

Re: [SOLVED] Error booting the new release (kernel image "whichsys.c32")

#8 2012-07-24 23:26:27

Re: [SOLVED] Error booting the new release (kernel image "whichsys.c32")

#9 2012-07-24 23:39:41

Re: [SOLVED] Error booting the new release (kernel image "whichsys.c32")

#10 2012-08-17 20:08:25

Re: [SOLVED] Error booting the new release (kernel image "whichsys.c32")

#11 2012-08-17 20:18:59

Re: [SOLVED] Error booting the new release (kernel image "whichsys.c32")

#12 2012-08-17 20:28:34

Re: [SOLVED] Error booting the new release (kernel image "whichsys.c32")

#13 2013-02-20 14:37:41

Re: [SOLVED] Error booting the new release (kernel image "whichsys.c32")

#14 2013-02-20 17:01:22

Re: [SOLVED] Error booting the new release (kernel image "whichsys.c32")

#15 2013-02-20 22:18:22

Re: [SOLVED] Error booting the new release (kernel image "whichsys.c32")

Board footer