Making boot options automatic

[meo]

Hi all!

Have tried to find out in the wiki etc. but no luck. Would like to make following boot codes to be issued automatic: noicons tce=sdb1 xvesa=1024x600x32 . Any hints will be appreciated. Thanks beforehand!!!

Have fun with TC,
meo

[gerald_clark]

You need to edit the config file for the boot-loader you are using.

[meo]

Hi!

Have done that with the ones that I have bootloaders on. This is regarding a usb stick that is made bootable with bootlace. Would a change to the menu.lst do the trick?

Have fun with TC,
meo

[gerald_clark]

Never heard of bootlace.

[vitex]

Have done that with the ones that I have bootloaders on. This is regarding a usb stick that is made bootable with bootlace. Would a change to the menu.lst do the trick?

Add whatever bootcodes you need to the "kernel" line of your grub4dos menu.lst.

[meo]

Hi again vitex!

Thanks a lot, will try tomorrow.

Have fun helping us selflearned enthusiasts,
meo

[meo]

Hi!

This is my menu.lst:

find --set-root /tinycore.iso
map --mem /tinycore.iso (hd32)
map --hook
root (hd32)
chainloader (hd32)

Where should I put the boot options? Thankful for any hints.

Have fun fooling around with TC,
meo

[gerald_clark]

You are chainloading a different bootloader.
You need to configure the one you are chainloading.

[vitex]

This is my menu.lst:

find --set-root /tinycore.iso
map --mem /tinycore.iso (hd32)
map --hook
root (hd32)
chainloader (hd32)

Where should I put the boot options? Thankful for any hints.

I thought that you had unpacked the Tiny Core ISO and were booting with an explicit kernel command line.  Instead you are booting the TC ISO directly using grub4dos ISO emulation, and the kernel parameters are still in the isolinux configuration file on the ISO.

The simplest way that I know to change those parameters is to use qremaster

http://forum.tinycorelinux.net/index.php/topic,8522.msg45715.html#msg45715

Boot a Tiny Core system, download qremaster and the ISO to which you want to add the bootcodes, and then execute:

./qremaster tinycore.iso test.iso noicons= tce=sdb1 xvesa=1024x600x32

to build the new ISO test.iso from tinycore.iso with your bootcodes added.  (Of course qremaster can also be used to add extensions and files to the ISO as well.)

[meo]

Hi for the last time this night vitex!

Thanks a lot for your help!!! Now I don't have to use any boot codes. The reason for this setup is that it is so easy to upgrade. I just have to replace the old iso-file with the most recent. So this setup I use with alfa and rc releases to try them out. Thanks again! Now i know what to do when the next update in the 4.0 series comes.

Have fun helping out in the TC community,
meo

[gerald_clark]

Is replacing 2 files that much harder than replacing 1 file?

[maro]

Is replacing 2 files that much harder than replacing 1 file?

In particular if one considers that in the case of the TC 3.x series where the kernel (i.e. 'bzImage') IIRC never changed.

So someone else might need to check my "complex" calculation: It meant that for the case where I just wanted to upgrade from one TC 3.x release to another one I ended up replacing a single ca. 8 MBytes file (i.e. 'tinycore.gz') with a different one (instead of replacing a ca. 11 MBytes ISO file with a different one).

OOPS, was that even a smaller download requirement for the former approach ??

[SamK]

Would like to make following boot codes to be issued automatic: noicons tce=sdb1 xvesa=1024x600x32 . Any hints will be appreciated.

This is my menu.lst:

find --set-root /tinycore.iso
map --mem /tinycore.iso (hd32)
map --hook
root (hd32)
chainloader (hd32)

If I understand your question correctly reply #10 of this topic may help:
http://forum.tinycorelinux.net/index.php/topic,10430.msg57531.html#msg57531


The basic idea was to provide a generic method that illustrates how to create a bootable usb flash drive having multiple partitions. It boots various distros directly from their ISOs stored in the root directory, and also has a separate data partition.  One by-product of this was a means of automatically passing boot codes to TC rather than manually entering them at each boot-up.  Have a look at the code box.

At the time of that post, TC would not boot using the direct mapping method of GRUB4DOS and required the memory mapping mode to be used.  Subsequent releases of the TC ISO (up to 3.8.4) are able to use the direct mapping method.  To do so (in the code box) replace   map --mem ...   with   map ....
   

[meo]

Hi SamK!

You might be right but I only use an old usb stick (Sandisk titanium 512 MB) for the single purpose of trying out alfa and rc releases. I'm using the same media for extensions so there isn't much space left when I have downloaded (or installed with a script) the ones I want to use. Thanks for your suggestion! Will look in to it a little further when I got some more time.

Have fun tweaking TC,
meo

[SamK]

...I only use an old usb stick (Sandisk titanium 512 MB) for the single purpose of trying out alfa and rc releases. I'm using the same media for extensions so there isn't much space left when I have downloaded (or installed with a script) the ones I want to use.

I'm not sure I understand your meaning and may be missing the point you are making. 

The reference to the previous post was not to suggest you change your current USB set-up to a multi-boot device, rather it was to provide a working example of how to automatically supply the boot codes when using bootlace+GRUB4DOS to directly boot a TC ISO.  Is this not your objective?  The principle will work just as well on a single partition bootable USB drive.

All that is required are small amendments to your menu.lst which will not occupy much space.

Current menu.lst

This is my menu.lst:

find --set-root /tinycore.iso
map --mem /tinycore.iso (hd32)
map --hook
root (hd32)
chainloader (hd32)

Where should I put the boot options?

Change it to something like this:

Code: [Select]

find --set-root /tinycore.iso
map --mem /tinycore.iso (hd32)
map --hook
root (hd32)
kernel /boot/bzImage quiet waitusb=5 noicons tce=sdb1 xvesa=1024x600x32
initrd /boot/tinycore.gz

OR - if it a recent stable version of TC

Code: [Select]

find --set-root /tinycore.iso
map /tinycore.iso (hd32)
map --hook
root (hd32)
kernel /boot/bzImage quiet waitusb=5 noicons tce=sdb1 xvesa=1024x600x32
initrd /boot/tinycore.gz