LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware - Installation (http://www.linuxquestions.org/questions/slackware-installation-40/)
-   -   Dual - boot Slackware and Backtrack hang (http://www.linuxquestions.org/questions/slackware-installation-40/dual-boot-slackware-and-backtrack-hang-802805/)

ripp3r 04-19-2010 04:15 AM

Dual - boot Slackware and Backtrack hang
 
Hi guys,

I've slackware 64 bit installed in partition sda1.

The BT4's installation is in sda3.

Now, if I install GRUB from BT4, I can boot BT4 without problem... but I can't boot Slackware (I can see it, but if I start nothing happens, just black screen).

Same with Slackware, after installing LILO and added BT4 I can boot slackware but not backtrack (this time, I start BT and it hangs on USB devices, I have nothing attacched and it seems like it stops at the card reader).

I've acer aspire 5735z

I used BT for a long time without problem, this is the first time that I dual - boot.

here's my LILO.conf
Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sda
compact     
  bitmap = /boot/slack.bmp
  bmp-colors = 255,0,255,0,255,0
  bmp-table = 60,6,1,16
  bmp-timer = 65,27,0,255
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
prompt
timeout = 50
vga = 791
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda1
  label = slack64
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda3
  label = BT4
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends

Hope you can help!

Thanks

onebuck 04-19-2010 09:02 AM

Hi,

Which do you desire to use? Lilo or Grub?

In your 'lilo.conf' above you are booting the same kernel for both.

Do a 'man lilo.conf' to get an idea of how to chainload. I prefer the 'man lilo.conf' from the cli on Slackware since it has more examples.

Hint: 'other' would be one way.

I would also add that a search here on LQ would get you loads of information on this very problem.

:hattip:

ripp3r 04-20-2010 08:57 AM

Quote:

Originally Posted by onebuck (Post 3940340)
Hi,

Which do you desire to use? Lilo or Grub?

In your 'lilo.conf' above you are booting the same kernel for both.

Hi,

Thanks for your reply.

I like lilo so I would like to stay with it.

Excuse me, but in my lilo.conf file I've:

Code:

# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda1
  label = slack64
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends

As you can see it's on SDA1

The other is on SDA3:
Code:

# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda3
  label = BT4
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends


And anyway, if they're the same... why one hangs and the other no?!


Thanks

onebuck 04-20-2010 01:43 PM

Hi,

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sda

This is the boot device and your /boot contains the kernels that you wish to start. You are booting one of the kernels for one and when you attempt to boot the other the proper kernel is not in the '/boot'.

If you want to have dual boot then I suggest that you use the 'other' option for lilo. Just write in the stanza for your '/etc/lilo.conf';

Code:

### other boot stanza
other=/dev/sda3
label = BT4
#end of stanza

Be sure to rerun 'lilo' to update the bootloader.

If you want to use the Slackware '/boot' then you can use the '/mnt' to mount your BT4 and copy the BT4 kernel to the '/boot' then create a initrd if necessary. Then create a stanza for that within '/etc/lilo.conf'. After which you will run 'lilo' again

Code:

#stanza
image = /mnt/BT4/boot/vmlinuz-bt4
 initrd = /mnt/BT4/boot/initrd.img-bt4 <<You will have to create if needed
  root = /dev/sda3
  label = BT4
  read-only


ripp3r 04-30-2010 04:29 AM

Quote:

Originally Posted by onebuck (Post 3941707)
Hi,

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sda

This is the boot device and your /boot contains the kernels that you wish to start. You are booting one of the kernels for one and when you attempt to boot the other the proper kernel is not in the '/boot'.

If you want to have dual boot then I suggest that you use the 'other' option for lilo. Just write in the stanza for your '/etc/lilo.conf';

Code:

### other boot stanza
other=/dev/sda3
label = BT4
#end of stanza

Be sure to rerun 'lilo' to update the bootloader.

If you want to use the Slackware '/boot' then you can use the '/mnt' to mount your BT4 and copy the BT4 kernel to the '/boot' then create a initrd if necessary. Then create a stanza for that within '/etc/lilo.conf'. After which you will run 'lilo' again

Code:

#stanza
image = /mnt/BT4/boot/vmlinuz-bt4
 initrd = /mnt/BT4/boot/initrd.img-bt4 <<You will have to create if needed
  root = /dev/sda3
  label = BT4
  read-only


hi sorry but I had some problem...

Can you please explain me what you mean by:

Quote:

then create a initrd if necessary
I copied /dev/sda3/BT4/boot/vmlinuz-2.6.30.9
to /boot/ (in my slackware)

then the lilo.conf appear to be like so:

Code:

append=" vt.default_utf8=0"
boot = /dev/sda
compact

  bitmap = /boot/slack.bmp
  bmp-colors = 255,0,255,0,255,0
  bmp-table = 60,6,1,16
  bmp-timer = 65,27,0,255

prompt
timeout = 1200
change-rules
  reset
vga = 791

# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/root
  label = Linux
  read-only
# Linux bootable partition config ends

#other boot stanza
other=/dev/sda3
label = BT4
#end of stanza

#stanza
image = /mnt/sda3/boot/vmlinuz-bt4
 initrd = /mnt/sda3/boot/initrd.img-bt4 <<You will have to create if needed
  root = /dev/sda3
  label = BT4
  read-only

Now what I don't understand is:

if I do a LS in /mnt/sda3, I don't see anything, maybe should I change the image path with something like:

Code:

image = /dev/sda3/boot/.......
And again, what is initrd? I don't think I need it... I found this page
http://members.toast.net/art.ross/rute/node35.html


Thanks

onebuck 04-30-2010 07:45 AM

Hi,

Quote:

excerpt from 'man initrd';

NAME
initrd - boot loader initialized RAM disk
DESCRIPTION
The special file /dev/initrd is a read-only block device. Device /dev/initrd is a RAM disk that is initialized (e.g. loaded) by the boot loader before the kernel is started. The kernel then can use the the block device /dev/initrd's contents for a two phased system boot-up.

In the first boot-up phase, the kernel starts up and mounts an initial root file-system from the contents of /dev/initrd (e.g. RAM disk initialized by the boot loader). In the second phase, additional drivers or other modules are loaded from the initial root device's contents. After loading the additional modules, a new root file system (i.e. the normal root file system) is mounted from a different device.
BOOT-UP OPERATION
When booting up with initrd, the system boots as follows:

1. The boot loader loads the kernel program and /dev/initrd's contents into memory.

2. On kernel startup, the kernel uncompresses and copies the contents of the device /dev/initrd onto device /dev/ram0 and then frees the memory used by /dev/initrd.

3. The kernel then read-write mounts device /dev/ram0 as the initial root file system.

4. If the indicated normal root file system is also the initial root file-system (e.g. /dev/ram0 ) then the kernel skips to the last step for the usual boot sequence.

5. If the executable file /linuxrc is present in the initial root file-system, /linuxrc is executed with uid 0. (The file /linuxrc must have executable permission. The file /linuxrc can be any valid executable, including a shell script.)

6. If /linuxrc is not executed or when /linuxrc terminates, the normal root file system is mounted. (If /linuxrc exits with any file-systems mounted on the initial root file-system, then the behavior of the kernel is UNSPECIFIED. See the NOTES section for the current kernel behavior.)

7. If the normal root file has directory /initrd, device /dev/ram0 is moved from / to /initrd. Otherwise if directory /initrd does not exist device /dev/ram0 is unmounted. (When moved from / to /initrd, /dev/ram0 is not unmounted and therefore processes can remain running from /dev/ram0. If directory /initrd does not exist on the normal root file-system and any processes remain running from /dev/ram0 when /linuxrc exits, the behavior of the kernel is UNSPECIFIED. See the NOTES section for the current kernel behavior.)

8. The usual boot sequence (e.g. invocation of /sbin/init) is performed on the normal root file system. ...

If you look at '/boot/README.initrd';

Quote:

excerpt '/boot/README.initrd';

Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
Wed Jun 17 01:49:18 CDT 2009

This document describes how to create and install an initrd, which may be
required to use the 2.6 kernel. Also see "man mkinitrd".

1. What is an initrd?
2. Why to I need an initrd?
3. How do I build the initrd?
4. Now that I've built an initrd, how do I use it?

Read the '/boot/README.initrd' file to fully understand the needs or usage.


Just a few more useful links;

SlackwareŽ Essentials
SlackwareŽ Basics
Linux Documentation Project
Rute Tutorial & Exposition
Linux Command Guide
Bash Reference Manual
Advanced Bash-Scripting Guide
Linux Newbie Admin Guide
LinuxSelfHelp
Getting Started with Linux

The above links and others can be found at 'Slackware-Links' . More than just SlackwareŽ links!


All times are GMT -5. The time now is 05:02 AM.