What are the precautions and procedure do i need to follow while upgrading the Kernel?
Please let me know the complete details of a procedure of upgrading a kernel in a production environment?
Is it possible to load a new kernel while in a chrooted environment. Say I have one linux distro and want to chroot into another and load its kernel
View 1 Replies View RelatedI have successfully installed a Ubuntu chroot (Maverick) on a running Linux appliance (an old Thecus N5200PRO box) which has been running various services for me quite happily.
When I attempted to add a webcam (for snapshotting) to this mix, I've come up against a problem. Since the chroot by default uses the kernel of the Thecus appliance, there appears to (understandably) be no support for the Logitech UVC webcam in the appliances' kernel; consequently inside or outside the chroot I can't access the UVC webcam.
I think I can get around this in a simple way if I can run a standard Ubuntu Maverick 32-bit kernel in the chroot.
Does anyone know how to chroot with alternative kernels, or quite simply, how to get a UVC webcam accessible on a Thecus N5200PRO?
Other details:
lsmod output
Output of uname -a:
Linux cube 2.6.23N5200 #1 PREEMPT Wed Jul 29 14:13:22 CST 2009 i686 GNU/Linux
lsusb -t output
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.
View 2 Replies View RelatedI'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? .
View 3 Replies View RelatedI 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
[code]....
This is my first time to set up a production web server and I got some few questions on our migrations:
1. Our website from the Web Hosting company already gaining 5000000 hits/month and 35000 unique visitors/month, problem is we only have 2x4mb dedicated line here in the office and one IBM x3650 m3 for our LAMP, you think guys its enough to handle that kind of traffic if we start moving our web server here in the office?
2. If I register www.example.com to GoDaddy for example, do I still need to setup a DNS (BIND) server on our side?
3. This is my current Apache config:
Apache/2.2.3 (CentOS) DAV/2 mod_fcgid/2.3.6 mod_auth_kerb/5.1 PHP/5.1.6 mod_python/3.2.8 Python/2.4.3 mod_ssl/2.2.3 OpenSSL/0.9.8e-fips-rhel5 mod_perl/2.0.4 Perl/v5.8.8 with PHP eAccelerator.
Anything to share to increase the performance of the web server?
What types of request for Samba & NFS comes in production support?
View 4 Replies View RelatedI am proposing moving from the mainframe to Linux. Problem is that I am not aware of a scheduling product that is available to handle the production code. Currently using CA7. Is there anything out there that accomplishes the same thing? As you can tell, I am NEW to Linux!
View 1 Replies View Relatedwe 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.
View 9 Replies View RelatedWhen upgrading kernel via RPM, do I just need to download the RPM, and then do:
rpm -ivh file.rpm ?
Is kernel-headers needed?
Do I want to use force on either?
Example:
# wget ftp://ftp.pbone.net/mirror/ftp.cento...1.el5.i686.rpm
# rpm -ivh kernel-2.6.18-238.12.1.el5.i686.rpm
This morning I noticed that there was an update to the kernel ready in the Update Manager, to version 2.6.35-25. I let Update Manager do its thing and I restarted my computer when it prompted me to.If I select 2.6.35-25-generic in Grub, Ubuntu boots just fine, all the way to the login screen. However, after entering my password, it looks like Gnome is going to load, but it never does. All I see is the default wallpaper and nothing else; the system locks up and does not respond to any input; and the fans start spinning at full-speed. My only option at this point is to do a hard shutdown. I have no problems if I select the kernel I was using previously: 2.6.35-24-generic
View 9 Replies View RelatedMy problem is that I can't setup a diskless environment with CentOS 5.4 (server) and CentOS 3.9 (hosts). On the host, I've recompiled the CentOS 3.9 kernel, with these mods:
- added kernel level IP autoconfiguration;
- added NFS file system support;
- added Root file system on NFS;
- added e1000 driver (the host has a gigabit network card);
Then, I have followed the guide at this link: [URL]
But in my dhcpd.conf I'he put other parameters:
ddns-update-style interim;
allow bootp;
allow booting;
subnet 192.168.195.0 netmask 255.255.255.0 {
range192.168.195.70 192.168.195.90;
option routers192.168.195.254;
option subnet-mask255.255.255.0;
option domain-name"lnf.infn.it";
option domain-name-servers192.168.195.254;
option time-offset-18000; # Eastern Standard Time
default-lease-time21600;
max-lease-time43200;
filename"linux-install/pxelinux.0";
next-server192.168.195.254;
}
host dante79 {
option host-name"dante79";
hardware ethernet00:20:38:01:C3:7C;
fixed-address192.168.195.79;
}
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?
View 2 Replies View RelatedI'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?
View 3 Replies View RelatedAs 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
[code]....
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?
Code:
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
My new Thinkpad often overheat and shutting down suddenly.Today I download the F14 DVD and upgrade my F13 with it.
View 6 Replies View RelatedI 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.
View 1 Replies View RelatedI 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:
[Code]....
What are the precautions and procedure do i need to follow while upgrading the Kernel?
Please let me know the complete details of a procedure of upgrading a kernel in a production environment?
After updating to 2.6.32.14-127.fc12 kernel my computer is slow.
View 4 Replies View RelatedCan I use the config for my current kernel (the jessie 3.16 one), and use it to build a more recent kernel (3.18)? Do I just copy across the config and try and build with it, or is there some tool that will bring across the existing config but also set up reasonable defaults for any new options in the newer kernel, and any other migrations that might need to be applied?
View 4 Replies View RelatedI have an issue with kernel-2.6.31.9-174.fc12.x86_64. I ran the updates on Christmas Eve and it updated from kernel-2.6.31.6-166.fc12.x86_64 to kernel-2.6.31.9-174.fc12.x86_64. When I rebooted, I no longer received the Fedora Bubble boot screen. It comes up with the Fedora boot bar (across the bottom). Also, I receive failures during boot with the following:
[Code]...
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.
