Ubuntu Installation :: Upgrading Kernel On A Live-cd?
Mar 15, 2010
I am building a live-cd using live-helper on Karmic (9.10). The process executes fine and I am able to build a live cd of ~200MB in size with minimal and xfce. But things does not work if I try to upgrade the kernel with the one of them from [URL] site. Ubuntu kernel team publishes the kernel for testing and I would like to upgrade the kernel for testing. But when I upgrade the kernel from inside the live-helper's interactive shell, it upgrades fine and iso gets created. While booting, it loads the kernel and errors out with the following message:
Code:
(initramfs) mount: mounting aufs on /root failed: No such device.
aufs mount failed.
I am running initramfs after installing the new kernel (a .deb file) using dpkg.
What else should I need to do for getting this to work?
I'd like to upgrade the kernel in the ISO of a Ubuntu 9.10-based CD with proprietary applications, burn a new CD with this modified ISO, boot up with it, upgrade + add + remove modules and applications, and finally save the running system into a new ISO file which would now have the latest and greatest.
I have a couple of questions: 1. How can I download the kernel manually? Where can I find the latest vmlinuz + initrd files for Ubuntu 9.10?
2. Is it just a matter of replacing those two files, or are there other dependencies I should update in the rest of the ISO, eg. isolinuxisolinux.cfg: Change initrd.gz to initrd.lz, etc.?
I've upgraded the generic kernel of my Xubuntu Karmic AMD64 persistent USB installation with the ubuntustudio realtime kernel (2.6.31.9.10). The thing is that the generic kernel is still loading as default and I don't have the option on the boot menu to choose the new one. I don't know how to edit this Grub2 version (grub-pc 1.97 beta 4).I haven't found a GUI package for this either.
I've never compiled a kernel before and I'm in need of the 2.6.28 kernel (two words: macbook aluminium).
I guess my biggest question is, will this guide work well for F10? I would hate to get half-way through it just to find out that F10 does something different than F08 or F09. Is there anything that you experts can see right away that would possibly be disastrous? If things do come to worse, I can simply select the previous kernel at GRUB boot right?
Or will the Fedora team be releasing the update soon through the package manager? Is there a way I can activate the development version and only get the kernel update?
Wow -everything works with alpha-3 version with a fresh install. Sound, wireless modem, processor speed scaling, sound controls, touch pad, all cores running,power management, battery, fans, etc. NVidia driver is also working. I tried multiple other distro installs - opensuse, Fedora, and ubuntu 10.04 - none worked. Also tried upgrading from 10.04 to 10.10 which didn't work either. also tried upgrading to 2.6.35 kernel which didn't work either.
I'm running a toshiba satellite a505-6030 with an i7 core, nvidia graphics gforce 310M. i didn't have to pass any arguments to grub either . First boot seemed to stall, rebooted machine, and it's been working perfectly since.
I have a hand-built kernel in Lenny. It's much smaller and faster than the stock kernel and doesn't need an initrd, but I am not sure how to upgrade it in a way that will be compatible with the new udev package. The recommended procedure is to upgrade the kernel and udev together and then reboot before doing the rest of the upgrade, but obviously I can't do that.
There seem to be two possible procedures I could follow:
1) Upgrade kernel sources and rebuild and install the kernel, then reboot and upgrade udev. But then the new kernel would be booting with the old udev and I don't know if that would work.
2) Upgrade, rebuild and install the kernel, then upgrade udev without rebooting, ignoring the warning messages. Finally reboot into the new kernel.
after upgrading to lucid lynx ubuntu doesn't boot with the new kernels 2.6.32-22-generic and 2.6.32-23-generic (also in recovery mode). But it's does boot with the previous 2.6.31-21-generic kernel. At the time i was hoping to wait it out, but a new kernel has come and the problem persisted. I've been trying to find a solution for this but somehow, amid lots of failed boot blank black screen threads, i didn't relate to any solution. The boot seems to go well until a pixelated logo appears (before the login screen), then goes to a blank black screen and there it stays stuck with no remedy. Looking into dmesg logs - albeit some differences between 2.6.31-21 and the newer 2.6.32-23 - the failed boot seems proper in both logs. In Xorg logs the differences are bigger but i cannot pinpoint a source for this problem.
I am using ubuntu 8.04 and i am trying to make iso image cd with running kernel. i know that there is documentation in ubuntu website in"how to make live cd" but the thing is this is my custom kernel. i have my own configuration. so i want this kernel to be work in live cd.
I would like to update my Kernel from 2.6.31.14 (from liveCD) to the 2.6.31.17, because of my modem problem (huawei e 169).>UBUNTU 9.10< I know that I can do it trough synaptic- but the problem is when I restart my pendrive, the kernel want be recognized. I think I have change something in some boot documents- but it looks here everything a little bit different than with HDD install:there is no menu.lst , etc.
My hardware isn't yet well supported on linux, so I'm looking for a live CD with 3.18 (3.19 came with a bad regression that still isn't fixed; and I need it to be a live CD so I can test before installing).
I noticed that the latest weekly build of stretch comes with 4.2. Can I find one with 3.18 somewhere?
I'm fairly new to linux Red Hat. We are running Rhel 3 on our VM's. We ran into a issue, (Bug 121801 - athlon-smp kernel does not support >4GB of RAM. what the stepos are to upgrade the existing kernel to the new i686? .
I have one machine where I have several versions installed on different partitions. The base partition (/dev/hda1) is Slack 12.1. On a spare partition (/dev/hdc4) I had installed Slackware64-current. Last week I slackpkg upgraded and installed the 2.6.32.2 kernel, and now that partition will not boot. I know that with the new kernels the hd* designation has been removed, and have already redone that fstab (accessing it from a different boot) to reflect the sd*. Here is the slack64 section of my lilo.conf:
Code: # Linux bootable partition config begins image = /other/spare4/boot/vmlinuz
i am trying to upgrade to ubuntu 10.04 from 8.04, and am getting this warning:"Upgrading may reduce desktop effects, and performance in games and other graphically intensive programs.This computer is currently using the AMD 'fglrx' graphics driver. No version of this driver is available that works with your hardware in Ubuntu 10.04 LTS.Do you want to continue?"should i continue? i have no idea what a 'fglrx graphics driver' is
I'd like to install the 2.6.35 kernel while keeping Lucid (just not in the mood right now to get used to a new release). Can someone point me to a tutorial on how to go about this?
As seen in the screenshot, my update manager won't let me mark the proposed kernel updates for installation.I have heard that I would be able to mark them after a few days have passed ( I don't know the reason, though). Well, now it's been 3 weeks that I have them as "proposed updates" and I still can't mark them.I decided to run apt-get upgrade in the terminal and here is the output:
Code:
~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done
I have an Ubuntu 8.04 server running 2.6.24-23-server. I have a godaddy account and I am trying to upgrade my os version to 10.04, which requires a kernel upgrade. I have tried ksplice but kernel 2.6.24-23-server is not supported. I have heard about screen sessions but I have not found it possible to reboot one screen while having the other screen stay persistent if it is possible.So the main question is how to update Ubunut 8.04 to Ubuntu 10.04 with out rebooting the entire server? Rebooting is completely not an option at the moment.
I upgraded my Ubuntu 11.04 laptop to kernel 3.0.1 and when I try to start Conky using my custom conkyrc, the conky process dies. I played around with it and discovered (through trial and error testing) that the code for the CPU temperature crashes conky. It worked before the upgrade. how I can get the CPU temp monitoring working again in kernel 3.0.1? Here is the code that is crashing conky:
we want to upgrade the kernel on Fedora 12 .but problem is , while doing 'make install' , it gives error as 'mkinitrd' is not available .which is required during 'make install'how to run 'make install' command on Fedora 12 without 'mkinitrd' utility.
I haven't used Linux very much, so I'm not sure how to do this. I'm presently running the 2.6.24-26 version of the Linux kernel on Ubuntu. However, I need to upgrade to 2.6.32. I have the source files (arch, block, firmware, drivers, kernel, include, etc), but I have no idea how to change the source of the kernel, or if there's an easier/automatic way to do this, and I specifically need the 2.6.32 version.
I upgraded, using package manager, to the latest kernel (2.6.35.10-72); I upgraded also kmod-nvidia and kmod-wl to the latest version, and the upgrade worked.After restarting the PC, though, it wouldn't boot Fedora: it stops at:"setting hostname for <my laptop's name>:[OK]"then it simply hangs there. It doesn't move, it doesn't boot, it doesn't ask for a login and it doesn't let me use command line.I can, however, boot and run Fedora fine if I select the previous kernel from the GRUB menu.Anybody can give me a hint to find the cause of the problem?
Was upgrading to the newest kernel in RHEL5 from 2.6.18-164 to 2.6.18-164.10.1 but when I rebooted the machine it gave me these errors.
Unable to access resume device(/dev/VolGroup00/LogVol01) mount: could not find filesystem /dev/root setuproot: moving /dev failed: no such file or directory setuproot: error mounting /proc no such file or directory setuproot: error mounting /sys no such file or directory switchroot: mount failed: no such file or directory kenel panic - not syncing Attempted to kill init!
So I rebooted the machine and picked the old kernel to boot up (2.6.18-164) and everything came back up fine. I don't understand why it keeps failing when trying to boot to the new kernel. I am using the yum upgrade command, is there a different command I should be using?
1. Upgrade the kernel and kernel-modules packages normally.
That sounds simple except that day-to-day, I don't run a stock Slackware kernel. I compile and run my own and always have. As I look back on my history with Slackware, I don't think I've ever upgraded kernel packages once I got a system up and running. When there's been big changes (2.4 to 2.6, for example), I've done a full re-install.
Most recently when I made the jump to 64bit, I did a full install using the huge.s kernel and once everything worked, I downloaded the current source from kernel.org and was on my way. I haven't booted huge.s since that day.
I do, of course, know how to upgrade my own custom kernel, but I like having huge.s installed as a backup. If I upgrade gcc/glibc, compile a new custom kernel and update lilo.conf/fstab without upgrading huge.s, then I will be left with only one working kernel.
So, my question is: is it simply a matter of running upgradepkg on the 6 kernel packages (headers, modules, firmware, generic, huge and source)? or is there more to it than that..ie, what about the system maps and symlinks in /boot?
I use Debian Stretch (testing). After upgrading to kernel 4.4 the system doesn't see my main soundcard at all -- so, no sound. And now I also get this message every boot:
Code: Select allmodprobe: module microcode not found in modules.dep
I have a Thinkpad which uses a Realtek Wifi controller. I read that with the 2.6.32 kernel, the driver is now part of the kernel by default. I have pardus 2009.2 installed and would like to upgrade the kernel from 2.6.31 to 2.6.32 But i cant find this kernel in the default repositories.
