to boot Slackware 12.1 can I install grub

james2b · 11-01-2008, 03:12 AM

I have a fresh install of Slackware 12.1 and during install I choose not to put in the lilo boot loader, and did not see a option for grub. So can I just install a full grub to boot it and not use lilo ? I have it installed on a external eSATA hard drive, and I multi-boot with windows XP and several other Linux using one main grub boot menu.lst located on the internal drive. How about the Super Grub disk to do this, thanks.

khronosschoty · 11-01-2008, 03:32 AM

Here is a full tutorial on grub
http://www.dedoimedo.com/computers/grub.html

Quote:

Originally Posted by james2b;3328022disk

and I multi-boot with windows XP and several other Linux using one main grub boot menu.lst located on the internal drive.

I have never really worked with grub. However you said you multi-boot with several different Linux distros.
Any way you will need to boot into one of those distros and update the grub menu to include Slackware. the tutorial I gave a link to gives a very good description. I recommend following that since I have very little exp with grub. I was at first going to attempt to say then I changed my mind, because I like I said have little exp. I hope that helps.

Side note:

Any way it does not matter it looks like there is tons of stuff on the net. I came across some one who had the exact same question here is that link.

http://www.unix.com/unix-dummies-que...stro-grub.html

pinniped · 11-01-2008, 03:41 AM

If you already have other Linux installations and Grub installed, then just don't install a bootloader. You will need to add your boot entries to the existing boot/grub/menu.lst file - that is all. To do that you will need to boot to an existing Linux installation, then mount the other Linux partition and look at what the names of the initramfs and kernel files are (and also the name of the partition).

james2b · 11-01-2008, 03:49 AM

Allright then, but when I looked in the Slackware /boot folder (from using one of my other Linux), it only has a vmlinuz kernel, but not that other initrd.img file, so do I need both to boot it by adding this into my main grub menu file?

khronosschoty · 11-01-2008, 04:09 AM

Quote:

Originally Posted by james2b

Allright then, but when I looked in the Slackware /boot folder (from using one of my other Linux), it only has a vmlinuz kernel, but not that other initrd.img file, so do I need both to boot it by adding this into my main grub menu file?

No you may not have a " initrd.img" it depends on what kernel you chose to use. The default kernel, in so far as I know,
does ---> not <--- come with a " initrd.img". The vmlinuz is all you should need.

saikee · 11-01-2008, 04:34 AM

Slackware is one of the easiest Linux to boot because it doesn't use initrd.

If it is in the say 2nd partition of your 3rd disk then it will be known to Grub as (hd1,2), as Grub counts from zero, and sdc3 in Linux then it can be fired up in your existing Grub menu.lst by these lines

Code:

title Slackware in (hd1,2)
root (hd1,2)
kernel /boot/vmlinuz ro root=/dev/sdc3

You can check its whereabout in root console with any Linux by

Code:

fdisk -l
grub
geometry (hd0)
geometry (hd1)
geometry (hd2)
quit

Adjust the partition or device name to suit your case.

Nylex · 11-01-2008, 04:41 AM

Quote:

Originally Posted by saikee

Slackware is one of the easiest Linux to boot because it doesn't use initrd.

That's if you're using the huge kernel. If you're using the generic kernel, I believe you'll need to use an initrd containing at least the module for your root partition's filesystem (certainly if you're using ext3, this is the case).

james2b · 11-01-2008, 05:04 AM

There are 4 vmlinuz kernels to choose from in the /boot folder, so I did try the vmlinuz-generic-2.6.24.5 with the correct root, ( added this to my main grub menu.lst in Ubuntu), and it booted to this error; No file system could mount root, tried: romfs, and this line also; Kernel panic-not syncing: VFS: unable to mount root fs on unknown block (8,2) , which locked up the PC, and had to press the power button.

Nylex · 11-01-2008, 05:07 AM

As I stated above, you need an initrd to use the generic kernel. Read the README.initrd file in /boot for more information.

khronosschoty · 11-01-2008, 06:33 AM

Quote:

Originally Posted by james2b

There are 4 vmlinuz kernels to choose from in the /boot folder, so I did try the vmlinuz-generic-2.6.24.5 with the correct root, ( added this to my main grub menu.lst in Ubuntu), and it booted to this error; No file system could mount root, tried: romfs, and this line also; Kernel panic-not syncing: VFS: unable to mount root fs on unknown block (8,2) , which locked up the PC, and had to press the power button.

by default Slackware will install all the kernels. That is if you choose install everything. So ether you need to create a "initrd.img" or you need to boot from (use) the "kernel-huge-smp". My guess is that Slackware is set to use the "kernel-huge-smp" or you have not progressed far enough to set up a initrd If you want to use a different kernel then the "kernel-huge-smp" Then you need to set up a "initrd" in that case this may prove useful. http://slackware.osuosl.org/slackware/README.initrd it is a how to written by Patrick Volkerding

brianL · 11-01-2008, 06:42 AM

Get this script:
http://www.slackware.com/~alien/tool...d_generator.sh
if you want to use the generic kernel. Run it and it will show you the correct command to run to build an initrd.

onebuck · 11-01-2008, 06:57 AM

Hi,

Code:

excerpt from 'CHANGES_AND_HINTS.TXT';
As stated earlier, it is recommended that you use one of the generic kernels
  rather than the huge kernels; the huge kernels are primarily intended as 
  "installer" and "emergency" kernels in case you forget to make an initrd.
  For most systems, you should use the generic SMP kernel if it will run, 
  even if your system is not SMP-capable.  Some newer hardware needs the 
  local APIC enabled in the SMP kernel, and theoretically there should not be
  a performance penalty with using the SMP-capable kernel on a uniprocessor 
  machine, as the SMP kernel tests for this and makes necessary adjustments.
  Furthermore, the kernel sources shipped with Slackware are configured for
  SMP usage, so you won't have to modify those to build external modules
  (such as NVidia or ATI proprietary drivers) if you use the SMP kernel.

  If you decide to use one of the non-SMP kernels, you will need to follow the
  instructions in /extra/linux-2.6.24.5-nosmp-sdk/README.TXT to modify your
  kernel sources for non-SMP usage.  Note that this only applies if you are
  using the Slackware-provided non-SMP kernel - if you build a custom kernel,
  the symlinks at /lib/modules/$(uname -r)/{build,source} will point to the
  correct kernel source so long as you don't (re)move it.

I would suggest that you read the documentation that PV and Team have provided; Announce 12.1, Slackware-Howto, CHANGES_AND_HINTS.TXT, UPGRADE.TXT. Plus the other text files relevant to your needs.

james2b · 11-01-2008, 11:54 PM

I changed to the vmlinuz-huge-smp kernel and with; root=/dev/sda5 in my main grub boot loader menu file, and it did boot up fine. Except it boots to only run level 3, text mode, so how do I enable automatic GUI boot? And the only user available was root, so during the install I don't think it asks to create a standard user, so how can I add a new user ?thanks

Woodsman · 11-02-2008, 12:27 AM

Quote:

so how do I enable automatic GUI boot? And the only user available was root, so during the install I don't think it asks to create a standard user, so how can I add a new user ?

Perhaps the following will help:

Configuring Slackware for a GUI Startup - Part I
Configuring Slackware for a GUI Startup - Part II
Configuring Slackware for a GUI and a Command Line Startup
Adding User Accounts