@all,

Thank you for your answers.

I did more tests tonight and the "media toolbox" method works well.

So I'm now booting by default on OS 4.1.

But boot menu still doesn't work.

So to answer to your questions:
- DH5 is bootable.
- DH0 has priority -1 and DH5 has 10. So for me, DHO has the highest priority (?)
- All lines of my kicklayout file link to 4.0 (or to 4.1) depending on version they are related to.
- Both configs are on the same partition (DH0).
- I have exactly one empty line between the two configurations in the Kicklayout file.

I really don't see what I'm doing wrong here. That's why I copy/paste my Kicklayout file. You may see something I don't

======
; $VER: Kicklayout_AmigaOne 51.7 (9.12.2006)
; Kernel configuration for the AmigaOne
;
;
;
; This file describes how the "Kickstart" image should look like,
; i.e. it describes which modules should be pre-loaded and available
; at boot time.
;
;
; Format:
; ~~~~~~
; The file lists one or more configurations.
;
; Each configuration starts with the LABEL keyword, followed by the
; name of the configuration. The name can be used to specify the
; configuration in the bootloader tool (see Documentation/kernel/
; bootloader.txt). Note that empty lines end one configuration and
; start the next, which means that you must be careful not to leave
; an empty line anywhere unless you are defining multiple configurations.
;
; Each configuration must have exactly one line with the EXEC keyword.
; This specifies the filename of the main kernel to use. This kernel is
; the absolute minimum required to boot. It contains, among other things,
; exec.library.
;
; The following lines define additional modules to be loaded into the
; kickstart image. Each of these lines starts with the MODULE keyword
; followed by the filename of the module.
;
;
;
; Configuration name
LABEL AmigaOS4.0
; Exec name
EXEC Kickstart/4.0/loader
;
; PPC native modules
;
MODULE Kickstart/4.0/kernel
MODULE Kickstart/4.0/FastFileSystem
MODULE Kickstart/4.0/SmartFilesystem
MODULE Kickstart/4.0/a1floppy.device.kmod
MODULE Kickstart/4.0/a1ide.device.kmod
MODULE Kickstart/4.0/battclock.resource.kmod
MODULE Kickstart/4.0/biosversion.resource.kmod
MODULE Kickstart/4.0/bootmenu.kmod
MODULE Kickstart/4.0/CDFileSystem
MODULE Kickstart/4.0/con-handler.kmod
MODULE Kickstart/4.0/console.device.kmod
MODULE Kickstart/4.0/diskboot.kmod
MODULE Kickstart/4.0/diskboot.config
MODULE Kickstart/4.0/diskcache.library.kmod
MODULE Kickstart/4.0/dos.library.kmod
MODULE Kickstart/4.0/elf.library.kmod
MODULE Kickstart/4.0/env-handler.kmod
MODULE Kickstart/4.0/FileSystem.resource.kmod
MODULE Kickstart/4.0/gadtools.library.kmod
MODULE Kickstart/4.0/gameport.device.kmod
MODULE Kickstart/4.0/graphics.library.kmod
MODULE Kickstart/4.0/hunk.library.kmod
MODULE Kickstart/4.0/input.device.kmod
MODULE Kickstart/4.0/intuition.library.kmod
MODULE Kickstart/4.0/it8212ide.device.kmod
MODULE Kickstart/4.0/keyboard.device.kmod
MODULE Kickstart/4.0/keymap.library.kmod
MODULE Kickstart/4.0/layers.library.kmod
MODULE Kickstart/4.0/lsi53c8xx.device.kmod
MODULE Kickstart/4.0/newlib.library.kmod
MODULE Kickstart/4.0/nonvolatile.library.kmod
MODULE Kickstart/4.0/nvram.resource.kmod
MODULE Kickstart/4.0/ps2.resource.kmod
MODULE Kickstart/4.0/ram-handler.kmod
MODULE Kickstart/4.0/ramdrive.device.kmod
MODULE Kickstart/4.0/ramlib.kmod
MODULE Kickstart/4.0/shell.kmod
MODULE Kickstart/4.0/sii0680ide.device.kmod
MODULE Kickstart/4.0/sii3112ide.device.kmod
MODULE Kickstart/4.0/sii3114ide.device.kmod
MODULE Kickstart/4.0/sii3512ide.device.kmod
MODULE Kickstart/4.0/strap.kmod
MODULE Kickstart/4.0/timer.device.kmod
MODULE Kickstart/4.0/rtg.library
MODULE Kickstart/4.0/PCIGraphics.card
MODULE Kickstart/4.0/ATIRadeon.chip
MODULE Kickstart/4.0/3dfxVoodoo.chip
MODULE Kickstart/4.0/petunia.library.kmod
MODULE Kickstart/4.0/usbresource.library
MODULE Kickstart/4.0/usbsys.device
MODULE Kickstart/4.0/uhci.usbhcd
MODULE Kickstart/4.0/hub.usbfd
MODULE Kickstart/4.0/bootmouse.usbfd
MODULE Kickstart/4.0/bootkeyboard.usbfd

;
;
; Configuration name
LABEL AmigaOS4.1
; Exec name
EXEC Kickstart/4.1/loader
;
; PPC native modules
;
MODULE Kickstart/4.1/BootDevice
MODULE Kickstart/4.1/kernel
MODULE Kickstart/4.1/FastFileSystem
MODULE Kickstart/4.1/SmartFilesystem
MODULE Kickstart/4.1/JXFileSystem
MODULE Kickstart/4.1/a1floppy.device.kmod
MODULE Kickstart/4.1/a1ide.device.kmod
MODULE Kickstart/4.1/battclock.resource.kmod
MODULE Kickstart/4.1/biosversion.resource.kmod
MODULE Kickstart/4.1/bootmenu.kmod
MODULE Kickstart/4.1/bootimage
MODULE Kickstart/4.1/CDFileSystem
MODULE Kickstart/4.1/con-handler.kmod
MODULE Kickstart/4.1/console.device.kmod
MODULE Kickstart/4.1/diskboot.kmod
MODULE Kickstart/4.1/diskboot.config
MODULE Kickstart/4.1/diskcache.library.kmod
MODULE Kickstart/4.1/dos.library.kmod
MODULE Kickstart/4.1/elf.library.kmod
MODULE Kickstart/4.1/env-handler.kmod
MODULE Kickstart/4.1/FileSystem.resource.kmod
MODULE Kickstart/4.1/gadtools.library.kmod
MODULE Kickstart/4.1/gameport.device.kmod
MODULE Kickstart/4.1/graphics.library.kmod
MODULE Kickstart/4.1/hunk.library.kmod
MODULE Kickstart/4.1/input.device.kmod
MODULE Kickstart/4.1/intuition.library.kmod
MODULE Kickstart/4.1/it8212ide.device.kmod
MODULE Kickstart/4.1/keyboard.device.kmod
MODULE Kickstart/4.1/keymap.library.kmod
MODULE Kickstart/4.1/layers.library.kmod
MODULE Kickstart/4.1/lsi53c8xx.device.kmod
MODULE Kickstart/4.1/newlib.library.kmod
MODULE Kickstart/4.1/nonvolatile.library.kmod
MODULE Kickstart/4.1/nvram.resource.kmod
MODULE Kickstart/4.1/ps2.resource.kmod
MODULE Kickstart/4.1/ram-handler.kmod
MODULE Kickstart/4.1/ramdrive.device.kmod
MODULE Kickstart/4.1/ramlib.kmod
MODULE Kickstart/4.1/shell.kmod
MODULE Kickstart/4.1/sii0680ide.device.kmod
MODULE Kickstart/4.1/sii3112ide.device.kmod
MODULE Kickstart/4.1/sii3114ide.device.kmod
MODULE Kickstart/4.1/sii3512ide.device.kmod
MODULE Kickstart/4.1/strap.kmod
MODULE Kickstart/4.1/timer.device.kmod
MODULE Kickstart/4.1/rtg.library
MODULE Kickstart/4.1/PCIGraphics.card
MODULE Kickstart/4.1/ATIRadeon.chip
MODULE Kickstart/4.1/3dfxVoodoo.chip
MODULE Kickstart/4.1/3DLabsPermedia2.chip
MODULE Kickstart/4.1/petunia.library.kmod
MODULE Kickstart/4.1/usbresource.library
MODULE Kickstart/4.1/usbsys.device
MODULE Kickstart/4.1/uhci.usbhcd
MODULE Kickstart/4.1/hub.usbfd
MODULE Kickstart/4.1/bootmouse.usbfd
MODULE Kickstart/4.1/bootkeyboard.usbfd
MODULE Kickstart/4.1/massstorage.usbfd
MODULE Kickstart/4.1/ohci.usbhcd
======

My Amiga is now booting by default on OS 4.1, so it doesn't really matter as I could change to OS4.0 by MediaToolbox when I need to test my own products under previous OS4 version (that was what I need).

But if we find, it would be great

Anyway, thanks for your help!

Glames

_________________
Glames / Boing Attitude :)

@Glames

Quote:

Glames wrote: @all, Thank you for your answers. I did more tests tonight and the "media toolbox" method works well. So I'm now booting by default on OS 4.1. But boot menu still doesn't work. So to answer to your questions: - DH5 is bootable. - DH0 has priority -1 and DH5 has 10. So for me, DHO has the highest priority (?)

That's maybe your problem right there. A higher number equals a higher boot priority. So, since ten is higher than minus one, you are booting the wrong partition, and slb never sees your fancy kickstart dirs and kicklayout file, but just the default ones on your 4.1 installation.

Quote:

- All lines of my kicklayout file link to 4.0 (or to 4.1) depending on version they are related to. - Both configs are on the same partition (DH0). - I have exactly one empty line between the two configurations in the Kicklayout file.

Yep, the rest looks fine, at least at a glance.

Quote:

My Amiga is now booting by default on OS 4.1, so it doesn't really matter as I could change to OS4.0 by MediaToolbox when I need to test my own products under previous OS4 version (that was what I need).

I don't understand everybody saying it's better and/or easier to use Media Toolbox to change priorities. Once you have set up the BootDevice method, there's really no work and all comfort with it, and once you get used to selecting your configuration in UBoot during a cold restart, you will wonder how you have been able to live without it.

The only work it creates is if you ever need to update some Kickstart modules, then you of course have to make sure you update in all the right places. But except for us betatesters, that's not likely to happen very often.

@Glames

Quote:

So to answer to your questions: - DH5 is bootable. - DH0 has priority -1 and DH5 has 10. So for me, DHO has the highest priority (?)

This definitley your problem.

To quote EntilZha (Thomas, the kernel guy)
Quote:

You can have two partitions with 4.0 and 4.1, but of course, slb can only load kickstart modules from one disk.

In your system you are trying to boot from the partition that doesn't have your amended kicklayout on. You should swap boot priorities, and then test.

_________________
Peter Swallow.
A1XEG3-800 [IBM 750FX PowerPC], running OS4.1FE, using ac97 onboard sound.

"There are 10 types of people in the world: those who understand binary, and those who don't."

@All
wasnt possible to run OS4.0 with OS4.1 kernel?
OS4.1 kernel Wasnt backcompatible?

I loaded one time os4.0 with 4.1 kernel and works(well dont tested it al long...)...

_________________
Simone"Tuxedo"Monsignori, Perugia, ITALY.