Slackware :: Newer Kernels And The Need For Initrd?
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?
I'm running FC 13. I believe that the base install is kernel 18.104.22.168-147.x86_64. That is the last version of the kernel that I have installed that includes an initramfs file. Neither 22.214.171.124-56 nor 126.96.36.199-68 installed an initramfs file. Since my root volume is in LVM, I can't boot with those kernels. I saw in another post that doing a "yum install kernel" would install the missing files. I tried that and it tells me that kernel-188.8.131.52-68.fc13.x86_64 is already installed and latest version.
I ultimately want to upgrade to FC 15 because I've got a new nVidia video card and need driver 270.41.06 for fc15. My fear is that if I upgrade I might not get the initramfs files in the new versions of FC and end up with an unusable system. Is there a way to add the initramfs files for the newer kernels and/or will I have the files after an upgrade?
I've just installed a Slackware64-13.0 test machine with alienBOB's multilib packages. I'm running the stock kernel generic-184.108.40.206 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.
I can boot xubuntu fine in kernel 220.127.116.11, but nothing newer. When I try to boot in a later kernel, I get a bunch of scrolling text, followed by a text based login prompt that doesn't work.I've been running xubuntu on this computer since version 8.04. I've had this problem since I upgraded to version 10.04. I figured an update would fix it, so I just made do. I figured for sure when the next upgrade came out it would be fixed, but I upgraded to 11.04 and still have the same problem. I figured somebody else would have had this problem by now and posted a solution, but I haven't found one, either on this forum or even on a google search.
It's an old compaq with 236 megs of memory.I just noticed that, while ubuntu used to require at least 256 megs of memory, and xubuntu was for older computers with as few as 192, I believe, xubuntu now requires 256. Is that my problem? Should I be looking at a different distro now?
Are there any official, almost-official or maybe even reasonably stable kernel repositories with new kernels for opensuse 11.2? I recently changed my laptop for a new one which has some issues, which then again are solved in 2.6.33 (and even in 2.6.32 with some tweaking). I would by any means try to avoid kernel recompilation.
What seems like forever ago now I tried to install Linux on this Intel 82855GME chipset laptop I was given. I started off with Fedora because it's what I'm most familiar with, unfortunately the live disk would crash at GDM so I could never get anywhere with it. Even doing a console based install would crash, but it at least pointed me in the right direction, it seemed the kernel was crashing for some reason (see image)Fedora livedisk crashlivedisk-error.jpg (95.96 KiB) Viewed 695 times
I'm running kind of a mix between Wheezy and the occasional package from Sid. I've got the 2.6.32 kernel installed, as well as 2.6.38 and 2.6.39.
With the first kernel (2.6.32), my sound is normal, everything works fine. With the latter two, even using the same driver, my sound is quiet even with the volume up all the way, not to mention that somehow the available volume controls change along with this update. I was wondering if anyone else has experienced something similar, and if they managed to fix it or work around it without just booting into the older kernel?
I have a rather old webcam, a Logitech quickcam messenger. This webcam was working fine with older linux kernel version, I think < 2.6.27. The gspca driver that makes this peripheral working has been merged into kernel sources, and I think that my webcam stopped working with this merge. I am a Slackware user, and until version 12.2 my webcam was working (I manually compiled and installed drivers). If I well remember, with version 13.0 (kernel 2.6.29) the video was full of strange artifacts, and with Slackware 13.1 (kernel 2.6.33) the webcam does not work at all. I am performing these tests with skype, that had videocalls fully working before gspca was merged into the kernel tree, while now I can only make phone calls.
This are the informations given by dmesg:
Code: usb 3-3: new full speed USB device using ohci_hcd and address 6 usb 3-3: New USB device found, idVendor=046d, idProduct=08da usb 3-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 gspca: probing 046d:08da
Is removing previous older kernels "vmlinuz", when updates do get a newer version an easy task, or do the more recent Linux like Ubuntu 9.10 do that automatically, and only keep a few older previous kernels ?
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 18.104.22.168 -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
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".
ROOTDEVNAME="/dev/sdr2"# Name of root device LINUXVER="22.214.171.124-smp"# Linux modules version CLIBVER="2.12.1"# C library version ROOTDIR="/boot/initrd-tree"# Location of root filesystm
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.
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..
getting profiles to work with the newer seamonkey? I found that after the initial upgrade from 1.1.18 to 2.0.0 user profiles weren't migrated/imported, so I backed the upgrade out.
Now with 2.0.3 and a bunch of new vulnerabilities I re-installed and still can't get a profile migration.. I resorted to giving up on the idea all together, but even when I erased ~/.mozilla I still can't get any profiles to work with 2.0.x at all.
Any attempt to start up a second instance with a new profile (-P) brings up the same profile already in use in the first instance, and switching profiles via "profile manager" from a running seamonkey will close the previously open profile to open the next one ....
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 )
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?
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.
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 ?
I'm writing a story for LWN on Slackware 13.37 this week. I'd like to hear from current Slackware users: How are you using it, and why you're using it? What appeals to you about Slackware Linux instead of Ubuntu, Fedora, openSUSE, Debian, etc.? Slackware tends to move a bit more slowly than other distributions to adopt newer features (like, say, GRUB) -- is this a pro or con for you? How long have you been running Slackware?
Any other thoughts about Slackware? If you respond, indicate in the post how you'd like to be attributed if I use your response in the story. (e.g., sign your name or indicate that I should use your forum username, etc.)
I have HandBrake 0.9.4 installed from Slackbuilds.org, but a new version came out yesterday that I want to install, but it isn't up on slackbuilds yet. Can I install it from source without doing anything to the old install?
When I installed it from slackbuilds, the slackbuild script also installed all the external multimedia libraries that I need. If I use removepkg (or whatever the command is) to remove the old HandBrake before installing the new one, will that also remove the multimedia packages that were installed along with handbrake? They were all built into the same .tgz
On my work computer so I can't do anything with it right now anyway, so maybe a slackbuild will be up when I get home.
The 2.6.37 kernel has proved disappointing for me on one lap top at least. The KMS disregards any boot-up parameters and bringing X on seems to be a big struggle for the lap top. The logon screen for run level 3 appears for several seconds before the lap top starts up the GUI logon. Worst of all, applications seem to take twice as long as they used to to get started.
No doubt there are some tweeks I could do but the main problem seems to be that the lap top is not powerful enough to cope with the KMS. I am even considering downgrading back to Slackware 13.1 (which this laptop had no trouble coping with).
Before doing this I thought I would try the 126.96.36.199 kernel and see if this overcame any problems. An initial trial looked promising but evidently there is more to using a new kernel than unpacking the huge 2.6.38 kernel and re-running lilo. I was unable to get past the login screen because many of the 2.6.38 directories don't exist.
Can I set up a laptop so that I can choose which kernel I want to use at boot-up time or do I have to make a total commitment with one kernel only?
I heard somewhere that by creating custom initrd image and default compiled kernel image, we can do PXE linux installation. can anyone please guide me 'what content will be placed inside initrd?'I know the process of creating custom initrd file .
I have an encrypted root and encrypted boot drive... To avoid entering a passphrase multiple times I'd like to add a keyfile for my root drive to my initrd... I've done this in Arch and it was relatively simple but I've hit a road block in debian finding the analog processes...
Code: Select all#Part 1) Generate the keyfile, give it suitable permissions and add it as a LUKS key:
I do not find any initramfs-188.8.131.52-112.fc13.i686.PAE.img in my /boot folder after I updated Fedora 13 after a fresh installation. The vmlinuz file is present in the /boot folder.he grub.conf file does not show any initrd entry too.
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.