Slackware :: Two Generic Kernels In /boot Directory?
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
ADVERTISEMENT
Oct 4, 2010
I'm running Fedora 12 - Linux 2.6.32.21 with a boot partion on /dev/sdb3 of a hard disk.
I downloaded a vanilla kernel version 2.6.35.4 and have built it and run it successfully. I built this kernel to play with building device drivers.
My grub configuration uses the same root filesystem for my fedora installation as my vanilla 2.6.35.4 kernel; both use the LVM root filesystem. (/dev/sd4 /dev/sdb5 /dev/sdb6)
When I'm running fedora 12 (2.6.32.21) I can see the files in /boot which contains my kernel, system-map, initramfs, grub directory, etc. I also see my vanilla kernel 2.6.35.4 and it's associated support files (map, initramfs, etc.)
My question is when I boot into my vanilla 2.6.35.4 kernel and I look in /boot, I only see my vanilla kernel and it's associated support files. No grub, no fedora kernel. If I do a df -a, I see that /dev/sdb3 is not mounted like it is when I'm running my fedora kernel. I'm confused as to what is going on here. Can anyone shed some light on this?
View 5 Replies
View Related
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
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
View Related
Apr 14, 2011
Tonight I installed ubuntu 10.10 (32 bit) on an external usb harddrive with a dvd I burned and I used my older desktop. I disconnected all internal and external drives first so everything had to be put on the usb drive I selected (only option available). I used the option to load extra software, use the entire hard drive, and let the software do it's thing. I basically had no options where to put things and it didn't have much choice.
When I boot the usb drive on my laptop (win 7 64 bit) by telling the bios to boot to it first... I get an error: modprobe: FATAL Could not load /lib/modules 2.6.35-22 generic modules No such file or directory. This message appears twice and then it does boot into ubuntu and seems to work fine. I'm new to this OS so that is an uneducated guess but the things I have done seem to be working. So exactly what is this error referring too? Is there a way to fix the problem or do I just ignore it.
View 9 Replies
View Related
Apr 29, 2010
I've installed glibc and downloaded 2.6.33.3 tar ball from kernel.org.
I created a symlink /usr/src/linux -> /drive/linux-2.6.33.3
But there's something missing because when I run
make mrproper
make config
I get errors about not finding headers:
asm/socket.h
It seems like I am missing some other symlink, I've tried creating other links, like /usr/include/asm -> /drive/linux-2.6.33.3/arch/x86/asm
View 5 Replies
View Related
Sep 1, 2010
Does it mean that a 64 bit version is not multi-core?
View 11 Replies
View Related
May 9, 2010
When trying to install my WiFi card's driver on Ubuntu 9.1, I run the make command and get the following error:make: *** /lib/modules/2.6.31-20-generic/build: No such file or directory
View 1 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 3, 2010
Where can I get a copy of the 2.6.33.4 config that comes with Slackware? Also, can I get a binary of the kernel, the one that comes with Slackware 13.1?
View 14 Replies
View Related
Jun 2, 2011
I have installed Slack 13.37 for test on VMware. I installed just all - also all avalible distro. kernel imiges:
Code:
vmlinuz-generic-2.6.37.6
vmlinuz-generic-smp-2.6.37.6-smp
vmlinuz-huge-2.6.37.6
vmlinuz-huge-smp-2.6.37.6-smp
and the default is vmlinuz-huge-smp-2.6.37.6-smp.
Im trying to switch to vmlinuz-generic-2.6.37.6 So, what I did:
fs = ext4
root fs = /dev/sda1
Code:
/boot# mkinitrd -c -k 2.6.37.6 -m ext4 -f ext4 -r /dev/sda1
Edited lilo: pointing new image, lilo command executed. Every time I start new kernel i got this error: [URL]
View 14 Replies
View Related
Apr 3, 2011
I've always booted Slackware with an initrd until recently. With my new installation of Slack Current (13.37), I didn't bother to create an initrd because of the constantly updating/transient nature of the current branch at the moment.My question is this: when 13.37 does go final in a few days, should I go back to my normal practice of booting with an initrd? Also, I think I understand how the initial ramdisk works, but is it really needed with the more modern kernels?
View 14 Replies
View Related
Jun 2, 2010
To clarify: I have two kernels, (a) one that "works" and (b) another that I am experimenting with. Each has it's own modules directory tree (in /lib/modules) and they are mutually incompatible ie kernel (a) will only work with module tree (a) and similarly for (b). I have two boot entries in lilo.conf which can be selected from the boot menu.
Now the problem is, what if something goes wrong when I boot to (b)? I'd like to be able to return to the safe option (a), but the current module tree is (b) and it won't work with kernel (a). I could use the Slack installationCD and rename the module directory (I presume this would work)but is there a simpler way, whereby I can select the correct module tree at boot time (or set it in lilo.conf)?
View 3 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 19, 2011
Because of slower machines would use this kernel? Does it mean better performance on such machines?I'm talking about kernel-generic and kernel-huge. This produces 1000 wakeups/sec.In smp kernel CONFIG_NO_HZ is set (fortunately )
View 7 Replies
View Related
Mar 2, 2011
I am running LiLo for the first time from my MBR..I seem to like it very much ..In fact i want LiLo to load other Kernels (Ubuntu 10.10) Also I was surprised when it detected my drive and activated the LBA32option...GRUB2 also had a problem accessing my drive beyond the BIOS limit (149GB is seen by BIOS wheras I have 160GB) I am not sure but want to see if LiLo can succeed in reading partition beyond 1024 cylinder limit. How do I modify lilo.conf to add Ubuntu Kernel and Image?
View 6 Replies
View Related
May 26, 2011
I'm trying to decide which kernel to install in my Slackware 13.37 installation. What is the difference between huge.s and the hugemps.s kernels ? Does one do something the other does not ? I'm installing Slackware because I've read it has no Pulsemedia baked into it. I hope neither kernel has any of that stuff.
View 2 Replies
View Related
Mar 4, 2011
Im sure that this issue is pretty old and you get some results from forums when you google it, but I cant seem to find the solution : When I boot my system ( its duel boot , win7 / Slackware 13.1 ) the message : L 99 99 99 pops up. I know this has to do with the MBR, When I looked online this is what people were told to do:
[Code]///
View 6 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, 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
Feb 27, 2010
I've just installed a Slackware64-13.0 test machine with alienBOB's multilib packages. I'm running the stock kernel generic-2.6.29.6 with an initrd set up using mkinitrd.confEverything is fine except that I cannot build a right initrd for kernels 2.6.30, both the /testing one or a custom build: if I try, it will panic at boot with the "couldn't find a valid RAM disk image" error.On the same hardware, without multilib support, I was able to correctly build and boot 2.6.30 initrds.
View 11 Replies
View Related
Apr 8, 2011
recently I upgraded to test Ubuntu Natty. It's very unstable, so I don't recommend you trying it yet.
Anyways, the thing is that when I upgraded it build two new kernels 2.6.38-8-generic-pae and 2.6.38-8-generic. For some reason when I boot with 2.6.38-8-generic-pae nothing happens, and I can boot only with 2.6.38-8-generic. So I have a couple of questions:
1) What's the difference between the pae kernel and the generic kernel
2) Does anybody else experience this problem?
View 9 Replies
View Related
Sep 10, 2010
I'm unable to boot my box since the first 2.6.34 kernel arrived.I hoped the second will fix the problem but it didn't.The display just enters in the power save mode after a second and that's it.The system boots fine with the 2.6.33.8-149.fc13.i686 kernel.The lspci result is:
Code:
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
[code]....
View 3 Replies
View Related
Mar 2, 2010
Instaled ubuntu 9.10 and i like it more than win xp because you can setup it in your way. Now my problem is when i compile older kernel with my setup and restart ubuntu i get grub with no loads like config is gone or something so i cant boot any of default kernels. I folowed this guide for compile [URL]... because i want to create lan hlds server with 1000hz kernel and have best response and latency server. can anyone confirm is this guide working with this 9.10 version or problem is that i cant set older kernel with newest ubuntu? Compiled few times and annoyed to wait again 2h just to try some other explanations i found on internet.
View 1 Replies
View Related
Mar 10, 2010
yesterday I removed old kernels via. the synaptic manager- I'm 100% certain I did not removed the latest stable kernel, and the version before- I did however removed the oldest two. Now after restart I'm dead in the water- i cant get past the initial boot- the screen goes black. I i'm running ubuntu 9.10 double-booted with windows vista, and right now I cant even get into vista...
Let's say that I messed up with removing old kernels, and removed sth, that shouldn't be removed- but how does this mess up vista?
View 3 Replies
View Related
Mar 15, 2010
I can't boot any kernels now, even old ones...
View 8 Replies
View Related
Sep 17, 2010
I seem to be having a problem booting into ubuntu 10.04 (and 9.10 before I upgraded a while back). It's been ongoing for a while now, but I can't seem to actually even get to the login screen. Some kernels just give me a blank screen, and others hang at the ubuntu logo (http://i.cbsi.com.au/story_media/339...ic-koala_1.jpg). It seems to be totally random, and I can't seem to even narrow down which kernels do what. It seems to be a game every time I reboot. Perhaps it has something to do with the beta 2.6.32-rc6 kernel I installed (by clicking on the .deb) a while back? I'm not too sure how to uninstall it, but I first installed it I think back at 9.04, and it always seems to be the first option in grub. Can I clean out my old kernels somehow? Or is that dangerous?
Maybe it's caused by graphics drivers? "Safe mode" doesn't seem to work any better though. And I can't get to the TTY terminals by <ctrl><alt><1-6> either, which would suggest to me that it isn't a graphics issue? I don't see the login screen, nor do I always see the splash screen.
View 9 Replies
View Related
