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.
I am new to install slackware, i am using scientific linux 6 and first, I don't know how to detect the wireless network and I don't know how to write the grub in my sl, I define the kernel to /boot/vmlinuz, which is a symbolic link, linking to the large single user mode, how can I use different kernels and it's easy to load the kernel but the config file, how should i edit the grub.conf
You can use the /boot/vmlinuz sym link for one of the systems, but to boot the other system you will need to use the full name of that particular kernel.
Yes, but when I switch the kernel to for instance vmlinuz-generic-2.6.37*, it tells me impossible to find the root directory, I think that's because it didn't load the right configure file, config-generic-2.6.37*,and the System.map-generic-2.6.37*...
Is your /boot file system on a separate partition or part of each operating system's file system? If /boot is part of each operating system's file system, then the menu.lst/grub.conf needs to be defined as such.
For example, if Slackware is installed on /dev/sda1 and /boot is part of that file system partition, then the location in grub to the Slackware kernel is something like this:
kernel (hd0,0)/boot/vmlinuz-2.6.33.15-smp-1
If SL6 is on the same drive but partition sda2, then the kernel location for that system would look something like this:
kernel (hd0,1)/boot/vmlinuz-2.6.33.15-smp-1
If /boot is a separate partition, say the first partition, then the configuration would look something like this:
kernel (hd0,0)/vmlinuz-2.6.33.15-smp-1
The menu.lst/grub.conf kernel directive is different from the root directive. The kernel directive provides the location of the kernel file. The root directive provides the location of the operating system.
Thus, if Slackware is located on sda1 and SL6 on sda2, the respective root directives would be like this:
root=/dev/sda1
root=/dev/sda2
The kernel and root locations are not necessarily the same place. For example, on my systems I use a separate partition for /boot. Therefore my kernel files are all located in a different location than the operating system partitions.
If you use any of the kernels name *generic*, then you nee to use an initrd with it since the kernel does not include any filesystem support. The initrd will load the correct kernel modules to add that support at boot-time.
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda3
# initrd /initrd-[generic-]version.img
#boot=/dev/sda
default saved
timeout=30
fallback 0
splashimage=(hd0,0)/grub/splash.xpm.gz
title Scientific Linux (2.6.32-131.0.15.el6.i686)
root (hd0,0)
kernel /vmlinuz-2.6.32-131.0.15.el6.i686 ro root=UUID=972b0fcb-ae43-4e62-8772-e40c34100101 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=auto rhgb quiet
initrd /initramfs-2.6.32-131.0.15.el6.i686.img
savedefault
title Slackware Linux
root (hd0,5)
kernel (hd0,5)/boot/vmlinuz ro root=/dev/sda6
savedefault fallback
*Read* the file README.initrd for instructions on how to *create* the initrd that you need. In fact AlienBob supplied a script (command) which can generate the command-line needed to generate your initrd using the mkinitrd command. There are surely many threads in this forum section which will guide you to boot using a generic kernel.
As I said, the generic kernels do not include file-system support (ext3,ext4, etc). The initrd you create matches the filesystem you have on '/' and includes and loads the kernel module for that filesystem.
Thank you for answering my question, I have solved the grub problem according to your post.
Here's my solution
first, login as root
second, install the mkinitrd if you haven't have it yet, it's in /slackware/a of the disc.
third, use mkinitrd to create your initrd.gz
last, load the initrd.gz in your grub.
hope it help the others
and i find it's still necessary to login as a user in cli first. slackware doesn't provide a gui login interface.
but, I still can get to the wireless network, the driver is ok, but I don't know how to connect to the network around me.
"slackware doesn't provide a gui login interface" It does, if you have installed the kde series and edit /etc/inittab to use default runlevel 4 instead of 3.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
