SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Slackware 12.1 is installed and is the only one
i can boot into
i also have Debain Etch installed before Slackware
here is what my partitions look like
cfdisk (util-linux-ng 2.13.1)
Disk Drive: /dev/hda
Size: 80026361856 bytes, 80.0 GB
Heads: 255 Sectors per Track: 63 Cylinders: 9729
Name Flags Part Type FS Type [Label] Size (MB)
-----------------------------------------------------------------------
hda1 Primary Linux ext3 67998.39
hda2 Primary Linux swap 1998.
hda3 Primary Linux swap 1003.49
hda4 Boot Primary Linux ext3 9023.14
_____________
Debian has hda1 and hda2
Slackware has hda3 and hda4
_____________________________
my lilo.conf from Slackware looks like this
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/hda
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255
# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt
# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 800x600x256
vga = 771
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda4
label = Slackware
read-only
when adding Debian as above to lilo.conf
i get this error:
bash-3.1# lilo
Warning: LBA32 addressing assumed
Added Slackware *
Fatal: open /boot/vmlinuz-2.6.18-6-k7: No such file or directory
bash-3.1#
___________________________________
when i boot into /dev/hda1 i get:
directorys:
bin boot cdrom dev etc home initrd lib lost+found media mnt opt proc root sbin selinux srv sys tmp usr var
a Gzip. file
initrd.img
a link to boot file:
vmlinuz
inside the boot directory:
grub dirctory, text document config-2.6.18-6-k7, Gzip file initrd.img-2.6.18-6-k7,
text document System.map-2.6.18-6-k7, unkown type vmlinuz-2.6.18-6-k7
HELP
Here's how I multiboot:
* Make a dir to mount your debian root partition: mkdir /mnt/debian
* Add to /etc/fstab that partition: /dev/hda(NUMBER) /mnt/debian ext3 defaults 1 1 <--depends on your file system, etc.
(NUMBER= where your debian /boot dir is located)
* as root: mount -a (to mount all partitions)
* edit /etc/lilo.conf
* Add something like:
Are you sure that you have the correct path to your Kernel for the Debian install on drive /dev/hda1? Maybe chroot to /dev/hda1 and double check that is the correct kernel image. Just a thought.
Lilo is telling you it can't find the debian kernel. You need to boot into Slackware and, as root, mount the debian root partition and copy the debian kernel from the /boot directory of the debian install to the /boot directory of the slackware install. Then when you run lilo -t (and then lilo) you will not get the error "Fatal: open /boot/vmlinuz-2.6.18-6-k7: No such file or directory". Now slackware's lilo will find the debian kernel and continue the boot process.
one more question
in KDE or any other Desktop
when i run either (/sbin/shutdown -h now) or
(/sbin/shutdown -r now) all i get is a black
screen that i can't get out of,
the keyboard and mouse won't work.
HELP
Sorry to say but i have to hard boot everytime
that happens and i think because i use EXT3
it seems to be ok.
I just realized that I might have fooled you, it can be that you actually booting debian with your slackware kernel. If so, sorry if I messed it up for you. I edited my post with a link to another thread that can be an better solution.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.