3

i'm on ubuntustudio and i want to format my hd and try kubuntu (install in my acer notebook, no partion, no double operating system problem, only istall it) i've downloaded iso file ( kubuntu-10.10-desktop-i386.iso ), insert usb pen drive, then: system > administration > startup disk creator erased usb pen content, and "make startup disk" finally, reboot computer with pen inside usb port

normal boot didn't start (as expected) but only black screen with this signal:

SYSLINUX 4.03 2010-10-22 EDD Copyright (c) 1994-2010, H. Peter Anvin et al
unknown keyword in configuration file
boot:

i've tried different usb pen stick and different iso files (ubuntu, kubuntu, netbook edition).. always same problem (sometimes only the first line without "unknow keyword in conf file" error)

some advice?? sorry for my bad english

Tim
  • 33,500
nkint
  • 2,065

5 Answers5

4

In 10.10 there is a bug in usb-creator that may cause your problems. Try creating your stick using UNetbootin, as was just suggested.

There are reports that you can fix the bug by opening syslinux.cfg on the USB drive and replace the following line:

ui gfxboot bootlogo

with

gfxboot bootlogo
Takkat
  • 144,580
2

Okay, the problem is that you didn't format your USB to FAT32.

Ringtail
  • 16,285
Amanda
  • 21
1

You could try using UNetbootin, another tool for the same purpose of making bootable usb drives. It's in the repositories as unetbootin.

Egil
  • 14,522
0

Actually, what worked for me [Dell Power Edge Server R220] was to copy the iso to usb in the following manner

I inserted usb drive then ran dmesg | tail to know the /dev/sd<x> drive.

If this drive has partitions then make sure you unmount invidual partitions sudo fdisk -l /dev/sd<x> first sudo umount /dev/sd<x1>; sudo umount /dev/sd<x2>; ... etc.

Then format this as follows sudo mkfs.msdos -I /dev/sd<x>

Now copy over the iso sudo dd if=<iso name>.iso of=/dev/sd<x> bs=1M && sync

-1

I solved this problem by copying syslinux.cfg from one folder near the kernel to the base of the Key. In fact I once displaced it and the boot went one step further but syslinux.cfg was then missing to the boot. So I had to copy it back.