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
After upgrading to Maverick, I have noticed that when I'm streaming from a site on the Internet with mplayer in wave format, my processor pegs at near 100%. I have to nice it to get it to relent, but this is a new issue for the upgrade. Streaming mp3 doesn't register very much.
While upgrading to 10.10, I opted to keep my apache conf files as they were (since I forgot to back them up before starting) and now apache isn't happy at all. At first it just wasn't working, so I backed up my entire /etc/apache2 dir, ran
Code: 'sudo apt-get purge apache2' and then deleted all references and left over config files, then ran
Code: 'sudo apt-get install apache2' and still apache wasn't working - in fact it did not seem to properly/completely reinstall with all dependencies.
Next I went through in Synaptic and removed a bunch of stuff myself, tried another apt-get purge and install, and still nada. Next I tried:
Code: 'sudo aptitude purge apache2' which seemed to run a little more robustly. So naturally next I ran
Code: 'sudo aptitude install apache2' and though it seemed to install everything appropriately, apache was not started and trying to run
Code: 'sudo service apache2 start' I get an unrecognised service error.
When trying to directly run
Code: 'sudo /usr/sbin/apache2' I get
Code: 'apache2: Could not open configuration file /etc/apache2/apache2.conf: No such file or directory'
Which is true, it does not exist but I don't understand why it's not reinstalling properly. Luckily this is just a local test server and I don't need to right now, but it would be good to get it back up and running. Could this really be all because I didn't replace my old files with the new conf files?
Since upgrading to maverick, I no longer have a shade animation. It was working splendidly in Lucid, but now, if I trigger the shade, it just snaps up. No nice, smooth rollup that I like. Screenshot attached of my compiz animation settings page.
I am unable to shutdown ubuntu after upgrading it to Maverick Meerkat.
I can do Ctrl + Alt + F4 and then Ctrl + Alt + Del but it does not let me use the taskbar button. When I press the shutdown button it just takes me to login page.
I've been having a problem with intermittent stuttering in video and audio playback since upgrading to Maverick (it also happened when I briefly installed Lucid). It started out as the odd skip every 20 minutes or so but now it can happen 5 or 6 times in 10 minutes when watching a film. I've tried:
reformatting and clean installing using a half-dozen players installing every codec I could think of (only after the normal ones wouldn't help) diangosing my 3 hard drives (the problem occurs on them all and they're not in a RAID setup) changing then changing back my video drivers disabling pulseaudio and ubuntuone-sync (these were not installed in my previous, working setup) looking at every relevant log file (mplayer, smplayer, demsg...) I know of running ubuntu's testing utilities I'm out of ideas. Going back to Jaunty is the only solution I'm pretty sure will work but it's not exactly ideal. It will be a few months a least before I'm able to install a completely new distro.
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'm looking to install an older kernel in Maverick - something like 2.6.32 maybe? Just wondering if there's a way to do it without compiling myself. I upgraded my system without checking everything. I use it as a MythTV box and the 2.6.35 kernel breaks my remote control in a manner that appears to be unfixable at the moment, if the forums on the problem are right. I figure an older kernel will get me out of the jam, but I'm not sure how to go about it (there aren't any in the standard repos).
when i was in office, something funny happened. my laptop power chord seemed to be disconnected and was running on battery power. i was away from desk and by the time i came back, laptop had gone to sleep may b due to battery getting drained.i packed up and came home, plugged in and booted but ubuntu seemed to give lots of erros and didnt boot. i went to my win partition, burnt the iso i had earlier downloaded and kept on win partition for safety. i booted off the cd and issued sudo fsck command from terminal. fsck did its job and gave a clean chit for my dev/sda5 (where ubuntu 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?
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 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.
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'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 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'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?
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 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.
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
