Slackware :: Generic Kernel And Initrd Not Working
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
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 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
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
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
Nov 1, 2010
I just removed a proprietary (fglrx ) driver which didnt work out well.Now all my updates hanging on: Setting up initramfs-tools (0.98.1ubuntu6) ...update-initramfs: deferring update (trigger activated)Setting up linux-image-2.6.36-020636-generic (2.6.36-020636.201010210905) ...Running depmod.update-initramfs: Generating /boot/initrd.img-2.6.36-020636-genericAnd I dont know how to solve it...besides a clean install.
View 9 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
Jul 13, 2009
I'm I seeing this wrong or is the initrd file in kernel-2.6.27.25-170.2.72.fc10.x86_64 a zero byte file and that's why I can't boot with it( get this "kernel panic not syncing VFS unable to mount root fs on known -block (0,0)" message)
View 2 Replies
View Related
Mar 12, 2009
The RHEL 4 update 7 installation CD installs the kernel with version 2.6.9-78.EL and therefore must contain corresponding vmlinuz and initrd.img. However I would like to have an all modules initrd that is used during installation but for a different version (2.6.9-78.0.13.EL). Is there a way in which I could obtain/make such an initrd?
View 3 Replies
View Related
Jun 23, 2011
I'm trying to bring my Slackware system back to life as my XP HDD is dying... I've got everything working except for my audio. I got a new motherboard (ASRock P43DE3) and it has a VIA VT1708S as the onboard audio. Is there any way I can get this working without rebuilding the kernel?
View 5 Replies
View Related
Dec 17, 2009
i upgraded from 11.1 to 11.2. Unfortunately the new kernel does not work with my sata/southbridge (i googled and figured its a known issue). So i tried to boot a 11.1 64bit rescue system to install the older kernel and the corresponding initrd. The problem is, that i cant find the kernel and initrd on the rescue system.
View 2 Replies
View Related
Jan 21, 2009
I had to uninstall f10 from my system because it would lock up my system anywhere from 1 to 5 minutes into using it and noone could tell me why.
NOW, I put 9 back on my system and after it updates everything, it locks up again. it does give me the option of the new kernel and the original install's kernel and if I choose the original to boot with, I don't have any problems.
SO, is there any way to fix it, OR to exclude the kernel and initrd from being updated?
View 3 Replies
View Related
Oct 17, 2010
I've downloaded 2.6.36-rc8 vanilla kernel, then I copied .config file from my current working kernel 2.6.32.21-168.fc12.x86_64, then I've configured, compiled and installed kernel like this:
Code:
make gconfig
make -j4 all (or make all)
make modules_all
make install
The last command edits my grub.conf file and writes this:
[Code]....
I checked my .config and ACPI, and File Systems are built into kernel and not loaded as modules... And, I have LVM but my /boot partition isn't in it, so I don't HAVE to use initrd, right? How can I boot from a vanilla kernel without initrd ?
View 11 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
Mar 26, 2010
I need to install Ubuntu on approximately 50-60 netbooks. None of them have CD drives, and I don't want to have to install them individually, walking around with a USB stick. I figured the fastest way to install on so many machines is to use a combination of apt-cacher (http://www.debuntu.org/how-to-set-up...ith-apt-cacher) and netbooting. I have successfully booted one machine to test, but as soon as the kernel comes up, support for the network interface is gone. Specifically, the "atl1c" module is not included on the netboot initrd image. Also, I would like to try to use preseeding, and I need to get that onto the initrd as well.
So, to summarize my question: How can I create a custom install kernel and initrd? I have a feeling it's related to the "debian-installer" category in the package repository, but I have not found any good documentation about doing this.
View 2 Replies
View Related
May 18, 2010
Need to know how to create a custom initrd boot splash for slack current
it would be nice to have a seperate one for bootup/shutdown
anyone know how-to or where to find good info?
View 2 Replies
View Related
Nov 8, 2010
I've recently updated my Slackware 13.1 system to the Slackware current. Although I have created my "initrd" image without specifying the "-u" option to "mkinitrd" it still starts up "udev".
That is causing me some difficulty because I am using "dmraid" to detect my RAID arrays. I had created my own device names such as "/dev/sdr2" for my root partition. With 13.1 I had no problem, since "udev" was not started by the "initrd" unless the "-u" option was provided. The current version seems to start up "udev" even without that option.
Is there a way to disable "udev" in the "initrd", or is there a way to specify custom "udev" rules for an "initrd"? I tried placing a "10-local.rules" file in the "etc/udev/rules.d" directory of the "initrd-tree" but that file had no effect on the device names generated by "udev" during the "initrd".
Here is my script that creates the "initrd".
Code:
ROOTDEVNAME="/dev/sdr2"# Name of root device
LINUXVER="2.6.35.7-smp"# Linux modules version
CLIBVER="2.12.1"# C library version
ROOTDIR="/boot/initrd-tree"# Location of root filesystm
[code]....
It will be helpful for me to understand "udev" issues related to an "initrd" because I will eventually try to use "mdadm" instead of "dmraid". So far I have only been able to get my system to boot from the RAID array using "dmraid" and I often run into new problems when I update Linux. Still, Slackware has proven to have the best support for booting from my RAID array because of the user community, documentation and flexibility.
View 1 Replies
View Related
May 18, 2010
When I compile a custom kernel with this command: make-kpkg --initrd kernel_image kernel_headers and then install the .deb, there's no initrd in /boot and I have to create it manually. I've thought that the --initrd option should take care about this, but somehow it doesn't.
It behaves like this for about two years at least (since I've compiled my first kernel). Of course, it's no big deal to create it manually, I was just wondering whether do I do anything wrong or whether should I fill a bug report..
View 1 Replies
View Related
May 31, 2010
The 2.6.33.4 kernel (using huge-smp) does not work for my laptop. It tries to boot, but after the line (Freeing init...) the screen goes blank. No logs since the filesystem is not yet mounted (I think). I've blogged about it already (posted it here, investigated myself, etc) for the previous versions of the kernel. I've been following every updates on -current and most of the thing works well except for the kernel. The kernel that works out of the box for my machine was 2.6.33. Previous kernel that works was 2.6.29.6. Then it went 2.6.33.1, 2.6.33.2 however, I need to compile using the config of 2.6.33 to make it work on .1 and .2. Now, I tried the same thing on 2.6.33.4 but some cryptic error occurred while loading the kernel.
That all were using huge-smp kernel. Now I tried to compile a generic-smp kernel (of course with initrd). (I did not install kernel modules yet). It works and it boots. However, since there are no kernel modules, it freezes after starting xfce at runlevel 3. So my guess is that somehow, my previous problems were either config related or module related. I though that if I will as well compile the kernel module, it may work, but as I look at source/k it seems that the source for kernel modules are coming the install package from slackware/a packages. Sorry, just a newbie.
View 10 Replies
View Related
Sep 21, 2010
Suddenly, after installing, boot was failed.
[Code]...
i was surprise, because in initrd-2.6.34.7-0.2-default all was ok.
View 2 Replies
View Related
Feb 25, 2010
So I'm building a custom kernel cuz I want the fbcondecor patch in my kernel. I use the same .config that 2.6.32 debian kernel package comes with. This kernel runs perfectly. I pass --initrd to make-kpkg when building the package but no initrd is built when I install it so I have to make it using "mkinitramfs -o /boot/initrd.img-2.6.33 2.6.33" to get it to boot. Now when I try to build the nvidia drivers it complains it can't find the source. I did build kernel_headers and installed them also the source is in /usr/src/linux. I also tried to specify the path by passing --kernel-source-path= to the nvidia script but no change. What is going on? I've done this fifty times before and never had any problems. Has there been some changes to how debian kernel packages are built? EDIT: Just thought I'd add some info about the steps I took.
Code:
tar xjvf linux-2.6.33.tar.bz2
ln -s linux-2.6.33 linux
cd linux
patch -p1 < ../fbcondecor-0.9.6-2.6.33-rc7.patch
cp /boot/config-2.6.32-trunk-686 ./.config
make menuconfig Loaded .config then I removed support for maxtorfb, tile blitting and some sirrusfb thing, nothing thats relevant to my system. Changed cpu from Pentium 4 to Core 2 and added framebuffer decor
support from my patch, exited and saved. Then:
[Code]....
EDIT2: I have now tried to build 2.6.32.8 in the same way with the same strange results, anyone have any thoughts as to what I'm doing wrong just throw it at me, I'm getting desperate and running out of ideas. I've checked all the kernel source symlinks and everything looks good.
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
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
