Ive loaded 64studio (hda6) grub in MBR, and fed10 grub on its partition (hda8), but from Studio it seems i cant Mount fed10 files to look at the Kernel path from MBR. (studio did not auto pick it up, like it did for Mandriva on hda7)
Does anyone know what it is ? something like kernel /boot/vmlinuz.....and Initrd(hd0,7)/boot.initrd.img .....then i can Edit menu.Lst in MBR grub.
I've downloaded 2.6.36-rc8 vanilla kernel, then I copied .config file from my current working kernel 2.6.32.21-168.fc12.x86_64, then I've configured, compiled and installed kernel like this:
Code:
make gconfig
make -j4 all (or make all)
make modules_all
make install
The last command edits my grub.conf file and writes this:
[Code]....
I checked my .config and ACPI, and File Systems are built into kernel and not loaded as modules... And, I have LVM but my /boot partition isn't in it, so I don't HAVE to use initrd, right? How can I boot from a vanilla kernel without initrd ?
I am unable to boot my Fedora 14 after last nights kernel update. When I start the boot up and hit F2 the system fails after outputting the line : Starting vservers of type 'default'. At some point the console displays an error message :
serial8250 : Too much work for irq17
How do I restore my previous version? I know some people have suggested in the past - just modify the grub.conf but how? When I boot off the cd I only get access to the liveuser disk. I need to have access to my own /boot/grub/grub.conf file.
I was finally able to install Fedora 11 x64 after choosing to only install packages from the repository on the install DVD. Prior to that when I had chosen tio install from the default online repositories, the install itself failed with a Python exception ( see my other post ). Now, however, once I boot after the install I eventually receive a kernel panic message, and failure. The exact same thing happened with CentOS 5.3 x64 after a flawless install. So unless someone knows what might be going on I will assume that Fedore, Red hat, and offshoots for x64 bit systems are just not for me. I have been able to successfully install the latest Mandriva and SUSE x64 Linux distros so whatever Red Hat/Fedora has done just does not work on my system.
View 3 Replies View RelatedI got a new laptop, this is the one: [URL] and decided that I wanted to go with Fedora instead of Ubuntu with this computer. The laptop runs win 7 64 bit so I'm trying to go with Fedora 64 but it will not boot. I first installed Fedora 12 64 bit from the DVD install and it would go to grub fine but when I boot the fedora os It just stops in the middle of the boot script. When it stops, the last 4 lines are:
kernel_init=0x1fd/0x257
child_rip+0xa/0x20
? kernel_init+0x0/0x257
? child_rip+0x0/x20
I hadn't messed with it for a few weeks and yesterday I saw that 13 was out, so I downloaded and burnt the Fedora 13 64 bit CD. I popped it in, booted the computer and it did the same crap. It didn't stop at the same line but it was around a line with:
? kernel_init
So I guess the kernel isn't loading properly or something. Do ya'll think I would be better off using the 32 bit?
In /proc/scsi/scsi, we can see the scsi host no. (scsi identifier no.). for e.g. Host: scsi4 Channel: 00 Id: 01 Lun: 00 In above e.g., scsi identifier no. is 4. Whenever we modprobe a particular module associated with scsi devices, we can see new entry in/proc/scsi/scsi with a greater identifier no. When we do rmmod on that module, the entry from /proc/scsi/scsi wipes off but still the counter of scsi identifier no. doesn't decreases. is is there any way to reset or decrement this counter so that next time when I do modprobe on scsi related module, it will assign no.s starting with 0 ? I found that during registering a scsi device, scsi_register() method gets value from "next_host" (which is a static int initialized to 0) and then increments next_host counter. Also, during scsi_unregister(), it decrements next_host counter. rmmod internally calls scsi_unregister(). So, if it is true then why the scsi host id. doesn't decrement during rmmod?
View 2 Replies View RelatedHow can I create a multi bootable (with menu) cd/dvd that contains a number of live cds? Is there any "easy" way of doing this? Isolinux is the way to go I guess, but is there any tool available for this?
View 2 Replies View RelatedI'm trying to install Fedora onto a computer that has Windows XP on the first of two SATA drives. Windows 7 is on the second drive.
I installed Fedora no problems on a 14 gig free space I created on the first drive and told it where and what my other OS's were. Fine so far. I didn't tell it to overwrite the MBR on the XP (first) drive. I took the second option which I "think" put the boot loader on the fedora partition.
All good - till I rebooted and I just saw my Windows 7 loader with my options for XP and Windows 7 but no Fedora.
So, if I overwrite the MBR on the first drive, will that mean I can't access my Windows 7 installation?
How SHOULD I set up the boot loader?
Is there an easy way to upgrade kernel to 2.6.38?
Or do i have to compile a custom kernel?
The only error message I am able to retrieve is in the GDM 0.log as follows:
AUDIT: Sat Mar 7 17:58:27 2009: 5034 X: client 9 rejected from local host ( uid=500 gid=500 pid=5066 )
I downloaded 64-bit version of Fedora 11 and burned the iso on my dvd. When I rebooted the machine it booted up from the dvd but it showed an error message that kernel "image not found". And it stops there itself. Can someone show me some way except downloading the iso again?
View 1 Replies View RelatedI am running fedora 12, x64. How can I upgrade fed12 as such? (apart from compiling the kernel myself)
View 3 Replies View RelatedGoogle answers attempted:
# grep lm /proc/cpuinfo
# uname -m
# file /sbin/init
# file /usr/bin/file
I don't think none of the above gives deterministic answer. Since I have 32-bit & 64-bit different system all of above spit out the same info.
I upgraded my F13 kernel from 2.6.33 to 2.6.34. But, the newer kernel isn't booting. It starts the booting process and then goes idle. how shall I troubleshoot?
View 2 Replies View RelatedI've managed to get some sound through the system with kernel 2.6.40.1. I use multiple sound cards, I have problems with keeping the same order. I added in etc/modprobe.conf The list of sound devices, putting my D66 card as device 3, Rebooted and cat /proc/asound/cards showed all fore devices in the correct order. I got audio through one of the apps , and started to try and get another ,wsjt, to function.
[Code]....
I have been running F14 as a 32-bit system (original m/b was 32-bit). Now the system is on a 64-bit dual-core processor board and I'd like to change from the 32-bit kernel to 64-bit. I downloaded a 64-bit kernel (kernel-2.6.35.6-45.fc14.86_64.rpm) and attempted to install it. It won't install and Package Installer returns a message of the sort that says this file "has incompatible architecture.
Valid architectures are ['athlon', 'i686', 'i586', 'i486'....]". My processor is an Athlon 64 x2. Is it possible to do what I want to do (I only want the kernel at the moment)? Is there some Fedora file I need to modify to allow the system to install the 64-bit kernel for this m/b? Do I need another file (or files) installed before I install the kernel?
So I'm new to modifying Grub, and I've recently setup my laptop to contain all of Windows 7, XP, and the Fedora 13 beta on a single drive.Grub is currently setup to boot to Fedora, and the Windows 7 boot loader, and from there I can boot to XP.I'd like to set it up however, to have XP boot "directly" (i.e. bypass the 7 bootloader and go straight for the XP loader).The current setup is:
Partition 1: 7 ntfs on sda1 (primary)
Partition 2: sda2 (extended containing sda5 XP ntfs)
Partition 3: sda3 ext4 containing /boot
[code]....
I am currently booting 4 flavors of Linux - Ubuntu 10.04, Xubuntu 10.04, Linux Mint 9 KDE RC and Linux Mint 9 Gnome. There is so little difference between Ubuntu Gnome with the right packages installed and Linux Mint 9 it is redundant and I would like to replace it with Fedora 13 and try that out for a while. I understand that Fedora still uses a legacy Grub while the others are all using Grub2. I also understand that the two bootloaders do not get along. Is there a way to do that? How? If I have Fedora install its legacy Grub to the Fedora partition will Grub2 see Fedora and update itself properly? I'm open to starting clean if that would simplify things.
View 4 Replies View RelatedCurrently I'm running 3 operating systems on my machine; Windows XP, Windows 7 and Fedora 14. I've installed them in the following order: XP -> Win7 -> Fedora14, with the idea that this would work fine regarding operating system selection at boot time.
But unfortunately, I just installed Fedora, and now I'm unable to boot Windows 7/XP. When I select the "Other" option in the Grub menu, I get the following error: Code: Error 21: selected disk does not exist To provide as much info as possible, here is a boot info script log:
[Code]...
I have a new work laptop (Dell M6400) that I currently have F10 i386 on. I would like to take advantage to the 64bit processor, but don't know if I need to completely re-install my F10, or if I just have to add the proper 64 bit kernel and applications.
View 4 Replies View RelatedI am running a vmware on a 64 bit fedora 9. I have already installed kernel header, but the vmware could not find the kernel header, and ask to input the kernel header path. I added /usr/include to the vmware, it complained not a right kernel header.
View 1 Replies View RelatedThe -162 kernel upgrade just released failed to boot in my x86-64 system. Additionally, both previous kernels failed in (probably) the same way. The progress icon proceeded all the way to its 'f' image, and then hung. I touched escape key, and found several disturbing messages among a dozen or so lines --
mdadm: No arrays found in config file or automatically. A dynamic linking error occurred: /lib64/multipath/libcheckdirectio.so: no such file or directory awk: cmd. line:1: fatal: cannot open file `/etc/inittab` for reading (Invalid Argument). Init: rcS post-stop process (807) terminated with status 2s. I got into rescue mode with my install disk, then looked for libcheckdirectio.so in /mnt/sysimage/lib64 but it was not there. Also, locate -d /mnt/sysimage/mlocate/mlocate.db/libcheckdirectio.so found nothing.
Ran chroot and executed the fakd diagnostic (which I had not seen before) and rebooted. Same problem - although now the screen is telling me SELinux is requiring a targeted policy relabel. My dual-boot-to-vista system has been erratic (requiring fsck several times, and confounding the Vista partition to require file checks), primarily since a large install of Eclipse and multiple plug-ins AFAICR.
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:
[Code]...
there is no sound in Fedora14 after kernel update (kernel-2.6.35.11-83.fc14). when use kernel-2.6.35.10-74.fc14 , I can listen to music.
View 14 Replies View RelatedMy main systems runs Fedora 14 x64 with the latest updates (I can't check anymore, but I believe it has the .13.91 x64 kernel). Since this afternoon it became unsuable. First, Opera Browser crashed and the crash report app of the browser showed up. Clicking one of the options there resulted to X crash, if I understood what really went on. No input, mouse or kb, I couldn't go to tty etc. I had to do a hard reset. Next boot proceeded normally up to the point that GNOME desktop is fully loaded. ABRT began reporting numerous kernel oops.
Rebooted again (noticed that init.d fails, so hard reset again) and tried past two kernel versions, same results.
Yum crashes and so does everything. I tried to revert all recent updates with yum history, but yum crashed.
Last update was May 22, and it updated kmod-nvidia.
Quote:
uname -a
Linux innovator 2.6.35.13-91.fc14.x86_64 #1 SMP Tue May 3 13:23:06 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
initial crash
Package: kernel
[code]...
before the reboot Opera 11.11 had crashed and it's own bug report tool came up. Clicking the "do not report this error now" option probably crashed X, because the screen went black and no input was possible (no mouse or keybord, so I couldn't go to tty either. Had to do a hard reset) Bug Reports:Kernel oops report was uploaded
One of the numerous crashes
Package: kernel
Latest Crash:Τρι 24 Μάι 2011 09:19:56 μμ
[code]...
In an attempt to ameliorate some other problems (lm_sensors, and loopback), and based on several forum entries, I decided to update the default f15 kernel (2.6.38.35) using kernel-2.6.39-1.fc16.x86_64.rpm from rawhide. It seemed to install without problems and when I rebooted it seemed to hang just before completing the boot process. The on screen boot messages ended with:
Started Display Manager
Started LSB: daemon for libvirt ........
Starting LSB: suspend/resume libvirt guests on shutdown/boot
[ 12 ......
about a dozen similar lines ending with
[25.030991 hci_cmd_timer: hci0 command tx timeout
then it apparently hangs
However, at that point I can log into to a console using Cntl-Alt-f2, so most, if not all, the crucial boot processes seem to have completed. There is an issue with the nVidia driver that I will deal with by modifying /boot/grub/grub.conf to re-enable nouveau, but I am stumped by what is causing the hang up. There is a certain amount of traffic regarding a similar problem with Ubuntu 11.04, but no solution other than it seems to be related to a BIOS bug (NFI)
what sub-system uses the "hci_cmd_timer" and why it might interfere with the boot process? Has anyone else run into a similar problem with f15?
Is there a better way to get an updated kernel in f15? I do want to keep all the Red Hat patches and back ports, so reluctant to build a kernel from scratch from upstream sources at kernel.org (and maybe just a bit apprehensive ;-})
Currently I'm running 3 operating systems on my machine (in order of installation); Windows XP, Windows 7 and Fedora 14. Unfortunately, after I installed Fedora I'm no longer able to boot Windows 7/XP. When I select the "Other" option in the Grub menu, I get the following error:
Code:
Error 21: Selected disk does not exist
To provide more info, here is a boot info script result:
Code:
Boot Info Script 0.55 dated February 15th, 2010
Boot Info Summary:
=> Windows is installed in the MBR of /dev/sda
=> Grub 0.97 is installed in the MBR of /dev/sdb and looks on the same drive in partition #3 for /grub/stage2 and /grub/grub.conf.
=> Windows is installed in the MBR of /dev/sdc .....
mdadm: No arrays found in config file or automatically
Keep trying update the packages (36 in total) and every time I keep getting this error
ERROR with rpm_check_debug vs depsolve:
kernel-x86_64 is needed by kmod-nvidia-2.6.26.6-49.fc8-173.14.12-5.fc8.2.x86_64
kernel-x86_64 is needed by kmod-nvidia-2.6.26.8-57.fc8-173.14.12-5.fc8.3.x86_64
Please report this error at [URL]
I just tried to update to kernel 2.6.27.15-170.2.24.fc10 (x86_64) at the suggestion of the gnome update widget, and the process hung. A bunch of other things were updating at the same time, many of which were related to audacity or wine.
I'm not sure just what was being updated, because the option to review which updates are available does not work - when I click on it, nothing happens, but when I take the other choice (install all updates), I take pot luck. It would be nice to be able to choose which programs to update, and to be able to upgrade the kernel independently, but I don't seem to be able to do that at the moment.
I'm currently using FC 9 - 2.6.27 x86_64. (In my Hp - nx6320 laptop with- Intel centrino Duo processor). I have downloaded linux-2.6.30.2. How do I install this with i386/i686 configuration set. All that I want is a 32 bit - linux-2.6.30, because NCTUns 5.0 works only with the 32-bit kernel. I have tried following:
Code:
make ARCH=i386 menuconfig
After this, I see the architecture set to "X86_32 = Y" in the .config file. But later, after I run
Code:
make bzImage
The configuration restarts asking to select Y/N for various packages and modules. I have no much idea on what to select and what not to, in order to retain X86_32 set. I end up with the new .config file with contents as below after the make bzImage command.
Code:
#X86_32 is not set
X86_64 = y
Again it is going to be built as a X86_64 bit kernel.
How to install the kernel as 32-bit along with the existing FC-9 64 bit kernel.