Thanks for your feedback, Miklós. I'm closing the bug report since your issue is resolved and I can't reproduce it, 
looks like a race condition or a bug with old ISOs, if someone can reproduce I'd be happy to find a way around this 
issue in grml2usb.

regards,
Mika

On 13-03-12 16:17, Michael Prokop wrote:

> Can you reproduce this issue booting on a different computer with
> the same (broken for you) usb installation?

 Yes.

> Did you use an empty usb device for installation? If not, has there
> possibly been a Linux installation already on that device?

 It was not an empty device. There was an old grml on it which caused the
 problem: now I made a clean filesystem on the device, and grml2usb produced a
 system on it which boots fine without any keyboard intervention or config
 file editing. I suspect there were some warnings when I ran grml2usb which
 were erroneously ignored by me.

> Did you run grml2usb on the 2013.02 live system?

 No.

>  If not, which system are you running grml2usb on and which version of
> grml2usb are you using? What command line did you use for grml2usb?

 I ran grml2usb 0.13.4 on a debian 6.0.7 system:
grml2usb grml64-full_2013.02.iso /dev/sdb1


 Sorry for the false alarm, and thanks a lot for GRML. It is COOL.

 Regards,
 Miklós
--

* PASZTOR Miklos wrote in grml's BTS on 20130312 / 16:50:

>  I have been an enthusiastic grml user for some time.

>  With the latest (2013.02) version after a grml2usb the image will not boot
>  without keyboard intervention.

>  I fixed this with adding the following line to
>  /boot/syslinux/syslinux.cfg:

> DEFAULT grml64-full

>  You may want to fix this also.

Hm, there should be 'default grml' inside
/boot/syslinux/grml64_full_default.cfg (which itself gets sourced
via defaults.cfg -> grmlmain.cfg -> distri.cfg -> vesamenu.cfg ->
isolinux.cfg / syslinux.cfg).

I can't reproduce this issue here, it works just fine for me™.

So to dig deeper into this issue:

Can you reproduce this issue booting on a different computer with
the same (broken for you) usb installation?

Did you use an empty usb device for installation? If not, has there
possibly been a Linux installation already on that device?

Did you run grml2usb on the 2013.02 live system? If not, which
system are you running grml2usb on and which version of grml2usb are
you using? What command line did you use for grml2usb?

Can you reproduce this issue on a different usb device as well?
If so, can you please provide us a copy of the resulting
/boot/syslinux/ directory?

regards,
-mika-

Hi,

 I have been an enthusiastic grml user for some time.

 With the latest (2013.02) version after a grml2usb the image will not boot
 without keyboard intervention.

 I fixed this with adding the following line to
 /boot/syslinux/syslinux.cfg:

DEFAULT grml64-full

 You may want to fix this also.

 Thanks a lot!

 Miklós
--