Slackware :: How To Modify Grub To Boot Using Generic Kernel
Feb 16, 2011
My Slackware boots using the huge kernel. I am not using LILO; I am using GRUB from the extras directory on the DVD. I followed the tutorial @ [URL] up to the point where it discusses modifying LILO. My /boot/grub/menu.lst reads, in part:
# Linux bootable partition config begins
title Slackware Linux on (/dev/sda7)
root (hd0,6)
kernel /boot/vmlinuz root=/dev/sda7 ro vga=normal
# Linux bootable partition config ends
This boots the huge kernel. What changes must I make to the above menu.lst entry to boot using the generic kernel?
View 3 Replies
ADVERTISEMENT
Jan 4, 2011
I am trying to figure out how to load the generic kernel in Grub2.
I have run the /usr/hare/mkinitrd/mkinitrd_command_generator.sh and ran the output:
Code:
Why this will not load.
View 10 Replies
View Related
Jun 15, 2011
One thing I always do is switch to the vmlinuz-generic(-smp) kernel in /etc/lilo.conf and build an initrd (see /boot/README.initrd for details). The "huge" kernel used by default is only meant for installing and not recommended for everyday use. It has a lot of drivers you don't need built-in and uses more RAM than the "generic" kernels.
still trying to find my feet and get to know Slackware. In one of my previous threads, 'things to do after installing' i was told the above message. When i installed, it used the huge kernel, but i'm unsure if that was the one that got installed. when i start slackware up, above the login screen it say, �wecome to Linux 2.6.37.6-smp (tty1)� I was wondering how to swich to the generic smp kernel, do I just change the vmlinuz to the desired, in lilo?
View 9 Replies
View Related
Sep 6, 2010
I did the kernel update via Update Manager today. Unfortunately , after this , disaster happened whereby sh.grub> prompt appeared on screen.
I got no idea how to rescue or repair the grub. I installed Ubuntu 9.10 in my E: under Windows 7 partition and labeled as "ubuntu". It has dual boot capability.
View 6 Replies
View Related
Apr 8, 2010
I've changed for huge kernel to a generic+initrd setup per the instructions in the README.initrd file however my machine fails to boot using that method. I get the following errors:
/boot/initrd.gz: Loading kernel modules from initrd image:
mount: mouting /dev/sda2 on /mnt failed: No such device
ERROR: No /sbin/init found on rootdev (or not mounted)
1. I've created the initrd using the results from /usr/share/mkinitrd/mkinitrd_command_generator.sh
mkinitrd -c -k 2.6.33.1 -f ext4 -r /dev/sda2 -m usbhid:ehci-hcd:ext4 -o /boot/initrd.gz
2. my root fs is ext4 on /dev/sda2
3. I've changed all necessary links in /boot
4. I've changed my /etc/lilo to:
image = /boot/vmlinuz
initrd = /boot/initrd.gz
root = /dev/sda2
label = Linux-Generic
read-only
View 12 Replies
View Related
Sep 19, 2010
I am going to change my hardware soon, just a new motherboard and cpu, same sound card,gfx card and other stuff. Will it boot and run ok ( like a live cd/dvd) until I have time to do a reinstall or does it have specific ports the hardware is installed on now?
View 6 Replies
View Related
Mar 20, 2011
I was interested in the idea of the btrfs subvolumes, so I made a virtual machine and installed Slackware as per the instructions here: [URL] It all went very well, but when I tried to switch from the huge kernel to the generic kernel and use the initrd.gz generated from step 29 (except that I used 2.6.37.4-smp instead of whatever's there) in lilo.conf, it failed to boot. I also noticed that in the instructions themselves, the poster doesn't actually add the initrd.gz to lilo.conf, so I'm guess the huge kernel has everything it needs to boot properly.
View 13 Replies
View Related
May 3, 2011
I've installed Slackware64 on a Toshiba Qosmio laptop (booting with ext4, SAMSUNG HM500JI HDD, 3 GB Ram, Intel Core 2 Duo Processor, Intel chipset and graphics).The system boots the huge kernel just fine. But after booting with the generic kernel AND after having prepared a mkinitrd with the mkinitrd generator, the boot process crashes at ~4sec with a panic.
View 14 Replies
View Related
Mar 15, 2011
i'm attempting to configure the vmware server on the above mentioned system,without luck.i can't get the vmmon to compile. I have tried this out-dated guide [URL] but no luck. I have setup made the necessary links as explained in this guide [URL] I haven't managed to try out the any-any patch since no link to the patch is alive anymore.Since slack 13.37 is using 2.6.37.3 kernel I wonder if anyone has found a way to compile the vmware modules on these recent kernels.
View 12 Replies
View Related
Jul 4, 2010
I recently updated the kernel to the newest version(2.6.32-23-generic) using the update manager and now I am unable to boot in to my Lucid installation.
My setup is LVM on top of a RAID 0 array. My computer had been running in this configuration since Lucid was released.
The Error Code I get on Boot is to the effect of: /dev/mapper/ubuntu-os is not available.. and then I get kicked in to Busy Box.
Once in Busy Box if I try to use mdadm to mount the RAID array I get this error:
If I boot in to the live CD I can mount all of the partitions and LVM volumes, so it does not appear to be a failed drive or volume.
I have looked in the mdadm.conf, lvm config and grub config files and searched the "Google" for an answer with no-avail...
Ultimately I would like to find a solution which doesn't involve a re-installation.
View 6 Replies
View Related
Jul 4, 2011
I just did a full install of Slackware64 on my netbook. Everything was sweet until I tried switching to the generic kernel. Even before this, I noticed when I ran the mount command it listed not sda3, which really is the root partition, but /dev/root as the root partition. This also appears in mtab, but not fstab. So yeah, here are the errors when I try booting into the generic kernel:
Code: mounting /dev/sda3 on /mnt failed: No such device No /sbin/init found on rootdev (or not mounted) bin/sh: cant access tty: job control turned off
I've tried rebuilding the mkinitrd_command_generator.sh script several times, as well as lilo.conf. But no success I've looked at some similar old threadss here but most of them are related to slackware 12 and older, so I don't know if these issues are related or not.
View 8 Replies
View Related
Nov 30, 2010
This week my ubuntu 10.10 was updated via update center. I obtained the new kernel headers 2.6.35-23-generic but now I can't boot using this kernel version and I have to select manually 2.6.35-22-generic in grub. I can see the ubuntu plymouth splash screen but it never rise gnome. where are the boot logs and how to activate them, In /var/log/ I have "boot" file but is empty and in "boot.log" I cant see any usefull information (I have BOOTLOGD_ENABLE=yes in /etc/defaul/bootlogd).
View 4 Replies
View Related
Sep 4, 2010
lately I compiled the 2.6.35 kernel and met the following problem: the kernel I get it is a generic kernel so I have two generic kernels. I want to have a possibility to boot both kernels: the new and the old one. I cannot resolve the problem of a creating initrd as mkinitrd run for the new kernel would overwrite the initrd.gz generated for the old kernel. So , I make a new directory where I put this new kernel. Is there a way to have both kernels together in /boot ?
View 3 Replies
View Related
Jul 1, 2011
I'm currently trying to setup Slackware 13.7 on a server, using software RAID 1. I'm using the README_RAID.TXT document at the root of the Slackware disc as a reference. Anyway, here's what I have so far.
/dev/md1 -> /boot partition
/dev/md2 -> swap partition
/dev/md3 -> / partition
Code:
[root@raymonde:~] # fdisk -l /dev/sd{a,b}
Disk /dev/sda: 41.1 GB, 41110142976 bytes
255 heads, 63 sectors/track, 4998 cylinders, total 80293248 sectors
Units = sectors of 1 * 512 = 512 bytes
[code]....
I created an initrd image using mkinitrd -F, added an according stanza to /etc/lilo.conf and ran 'lilo' after that. Now I can boot on the vanilla huge kernel all right. But I can't seem to boot on the generic kernel. Whenever I try to do this, the boot process stops short on the following error message:
Code:
mount: mounting /dev/md3 on /mnt failed: Device or resource busy
ERROR: no /sbin/init found on rootdev
View 5 Replies
View Related
Aug 24, 2010
I've previously had a dual boot Vista/Ubuntu machine that was working fine. Fast forward, I'm not able to boot into Vista at all and decide to reformat, return to factory settings after which I'll simply reinstall Ubuntu to get my functioning dual-boot back. I reformat the drive, everything seems to work fine and when I reboot I'm met by the GRUB screen rather then the Vista bootloader screen I expected. I select the Vista option and rather than starting to boot, seeing the Windows splash and then breaking (as it's been doing for a few weeks leading up to my decision to reformat), I'm promptly given a message that it can't find the disk 5252-ACFA (that Vista was previously on). After further inspection, my Ubuntu partition is still in tact and untouched, so I think the 'reformat' simply reformatted the Vista partition not the entire HD as I'd wanted. How do I modify GRUB to point to the new correct Vista boot?
View 4 Replies
View Related
Mar 3, 2009
I recently installed a 64-bit version of centOS 5 alongside a 32-bit version, which I use. Turns out the 64-bit version absolutely will not boot and I'm stuck with it as my default boot option. Since the grub being used resides on the 64-bit half, I cant edit the menu file but I know theres a way to do this without it, through grub itself. I have about 29 render nodes now with this problem, and whenever they need to be rebooted I have to hook a monitor up to each one and hold its hand through the boot process. How to change the grub menu through grub itself, basically just change the default boot option and then have it stay that way?
View 5 Replies
View Related
Jun 20, 2010
I installed a fresh copy of Slackware 13.1 (stable) on one of my media servers and I am experiencing something strange.... When I power up the machine, I see the kernel booting, no errors, until it gets to the point where it says:
And then randomly freeze there.... Well the machine is not totally frozen because the cursor still blinks. But it will never continue... Like I said, this happens on a random basis... After a reset, it might go through or simply stall at the same spot.
I remember after installing Slack 13.1, I rebooted the machine but forgot to remove the DVD from the player, so the install routine started up, and froze at the same point when it was loading the kernel for the setup programs...
My mobo is a MSI k9N platinum.
I never had this problem before.... (well I never used 13.1 before). Since I got this machine, I used slack 12.2 and slack 13-current with success.
This problem makes the machine extremely unreliable because I intent to use it as a backup and media server, so chances I will WOL the machine and use it remotely... if that happens.
View 10 Replies
View Related
Jan 5, 2010
I updated my kernel in slackware current but can't install lilo, when i was with my old kernel it gave an error about not finding the sda drives (they were named hda before the upgrade).I booted into the slackware 13.0 dvd and modified fstab and lilo.conf replacing hda with sda but lilo still gives an error of not finding sda drives.How can i install lilo so i can boot into my sistem??
View 14 Replies
View Related
Nov 1, 2010
I've a multiboot machine and I recently installed Slackware64-13.1 on sda33. I added menu entry in SUSE boot loader and configured menu list as per [URL].. it returns GrUB error 15. Here is my menu list entry for Slackware -
Code:
###Don't change this comment - YaST2 identifier: Original name: other###
title Slackware64-13.1
root (hd0,32)
kernel /boot/vmlinuz root=/dev/sda33 ro hdd=scsi
savedefault
[Code]...
View 15 Replies
View Related
May 2, 2015
After some updates Jessie 8 my boot grub shows now 2 kernel versions to boot from.
3.16.0-4-amd64
3.16-3-amd64
- How do I know which one is the newest and if happy with it, how to remove the older one?
View 9 Replies
View Related
Jul 16, 2010
today I updated my Slackware 13.0 to 13.1. Unfortunately it didn't boot any longer. I probably forgot to run "lilo" before restarting. However, I reinstalled Slackware and I installed grub instead of lilo I'm more familiar with it..
This was my first menu.lst config:
Quote:
title Linux (uuid)
root(hd0,0)
kernel /vmlinuz root=UUID=6a8096a3-3915-4ef2-8984-976e42d04cfc ro vga=0x031b
While booting it stopped and printed this message:
Quote:
Kernel panic - not syncing: VFS; Unable to mount root fs on unknown-block
Then I compared it to other Linux system on different computers and I noticed that every of them, who are using uuids, using an initrd as well. So I created one and now it boots properly.
I just wonder, why? Why does it need an initrd to boot by using uuids?
View 2 Replies
View Related
Feb 13, 2011
I have been running Ubuntu 10.04 under Windows 7 (Is this call WUBI?) without any problems for a while. My other machines only run Ubuntu (9.04 & 10.04). I decided to give it a try to the latest Ubuntu 10.10. After going through the successful installation and then rebooting, I am getting the following error message once I select 'Ubuntu' in the boot up menu right after the BIOS screen: Booting ' Ubuntu 10.10, kernel 2.6.35-25-generic'
[Code]...
View 7 Replies
View Related
Feb 24, 2010
I want to compile a custom kernel, because I need a path for a device. Here is what I've done:
Code:
$ cd /media/work/temp/
$ apt-get build-dep --no-install-recommends linux-image-$(uname -r)
$ apt-get source linux-image-$(uname -r)
$ cd linux-2.6.31
[Code].....
View 1 Replies
View Related
Aug 26, 2010
What is the difference between those kernels that you can install from this PPA:
[URL]
ppa:kernel-ppa/ppa
...which currently has 2.6.35-19.25-generic
AND
[URL]
...which currently has 2.6.35.3-maverick (even has later version 2.6.36-rc2-maverick)
AND
[URL]
...which currently has 2.6.35.3 (even has later versions 2.6.36-rc2 and 2.6.36-rc2-git4)
Are they the same? Which is newer? Is 2.6.35-19-generic = 2.6.35.3?
View 6 Replies
View Related
Jun 27, 2011
Just installed the patches/upgrades for the 2.6.35.30 kernel. Ubuntu will not boot without me typing "y" and hitting enter and later hitting the enter key again. Just have a blank screen unless I do this. Discovered what to do by booting into recovery mode. Had to make a display selection. Just guess at the enter key the second time the boot process stopped. I new to Ubuntu so don't know where to look in the logs to provide additional information to help trouble shoot the problem. If some one can guide me as to where to look I'll post log info. Hope this is the right place to post this. If I need to make a bug report let me know.
Forgot to add: HP Pavalion dv5000 (dv5020us to be specific). AMD Turion64 processor. ATI Radeon Mobility 200M video.
View 7 Replies
View Related
Mar 7, 2010
I was previously using kernel-huge until a slackware update caused some problems for me, so I switched over to kernel-generic but now I'm wondering if it uses both of my cpus on my dual core processor.
View 1 Replies
View Related
Apr 2, 2010
I'd like to compile a generic kernel for my netbook on my desktop. They are both F12 64bit. On my desktop can I do:
make xconfig
make
make modules_install
Then copy the folder to my netbook then:
make install? Is there a better way? I don't really want to make .rpms.
View 1 Replies
View Related
May 6, 2010
I reported a bug at [URL].., then I had been asked to test the latest generic kernel in order to test whether the bug exist in latest kernel or not. I had read the information at [URL]... I installed the most current version of generic kernel. After that, I restart my computer and try to use the latest installed kernel. Then, the laptop freeze. Then, I restart my computer by turning off and on again, select the older kernel, successfully boot into Ubuntu to post this thread. What can I do since I am required to test the latest generic kernel?
View 2 Replies
View Related
Sep 2, 2010
I installed Mint 9 and directly after installation there were updates to download and install, which I did. One of the updates is a newer kernel, 2.6.32-24-generic.
When I manually install the nVidia driver 256.44 and restart gdm it works. When I reboot I land in low resolution, have to remove and re-install the older (195.36) driver through "Hardware Drivers". Somehow the new kernel and the latest nVidia don't match together. Am I the only one suffering from this or are there more people with this problem,and what to do about it?
View 1 Replies
View Related
Jan 9, 2011
I just noticed I'm not running with the latest kernel.
This box was originally installed as Ubuntu 10.04, then upgraded to 10.10.
I just recently noticed that, even though kernel 2.6.35-24-generic is installed, this box seems to insist on booting up with 2.6.32-24-generic.
Looking at /boot/menu.lst, it looks ok. (default is 0, and first kernel in list is 2.6.35-24. 2.5.32-24 is the *last* one in the list!)
View 3 Replies
View Related
