I have a Vista/Kubuntu dualboot, with grub2 as my loader. Because i have read that Windows likes to ignore something else present on the system and overwrite everything with itself. So i installed Vista, then Kubuntu.Now i want to upgrade my Vista to Win7. My question is - what should i do in order to keep my current dualboot intact (Grub2 as a loader, and kubuntu fully functional). I fear Win7 might even never ask me about keeping my kubuntu dualboot, just overwrite everything. PS: My bootinfoscript output
Code: Boot Info Script 0.55 dated February 15th, 2010 ============================= Boot Info Summary: ==============================
A forum that I visit with Firefox has a message that says the following: Quote: I've detected a bestlifeusa.ru script that tries to run of this server, I've reported this, but I'm pretty sure most of you get this one too, I was just protected so I'm fine - you may not be so lucky, so I'm asking you guys to get your system checked immediately.
If you use firefox - install the No Script extention after you have cleaned your system for all worms, viruses and spyware. And make sure that the bestlifeusa.ru script can't execute on your system from this site. If you don't have any "anti script" "no script" "script stopping" system installed with your browser, you will likely not notice this script, I suspect it's a spy-script that spies on you - and you most certainly have it! I think the measures recommended might be Windows oriented.
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'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?
I 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:
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
What is the recommended way to do updates when running sid (especially those involving updates of xorg or desktop environments as they should not be running at that time)? I imagine this would be safe:
1. # apt-get update 2. # apt-get dist-upgrade -d 3. Switch to a text mode terminal (say, tty1). 4. # /etc/init.d/kdm stop 5. # apt-get dist-upgrade
just returned to fedora from a stint with xp for development with xp embedded (acutally pretty cool) before i get all cozy with settings and install programs, etc, etc, what is the upgrade procedure for 13? does all of this go for naught, or are settings kept if you upgrade with yum? i hope the answer is what i want it to be!
Have decided to stop using Hylafax and our two serial modems on our server running Clarkconnect 4.1 (RHE4.1)What file will I go to to edit so the program and two devices don't start up?I disconneted the devices and the log file is full of the attempts to get the modems working
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
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
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:
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.
I would like to install Fedora 11 on an ASUS P5L-VM 1394 motherboard with a 3 GHz Pentium 4 CPU. This is an LGA775 socket mobo with a Intel 945G chipset. Two SATA hard drives are plugged into SATA ports. An IDE DVD drive is plugged into the IDE/ATA port. Using the 32 bit Fedora 11 installation disk, I have seen two cases:
1) No hard drive recognized. When i get to the disk configuration screen, there are no options to choose from.
2) By monkeying around with the BIOS settings or switching the SATA ports the disks are connected to, I can get an alternative mode in which no drivers are found for the DVD drive either.
Currently, a version of Ubuntu is installed. UPDATE: The board was purchased in a P3-PH4C barebones, which for unknown reasons requires a different BIOS issue than the regular P5L-VM 1394. Updating to the most recent BIOS does not resolve the problem. One the installation procedure fails to recognize the hard drives, going into a shell and examining the boot up log shows that the kernel recognized both hard drives. So it's down to why the installation procedure is not recognizing them.
Can 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?