Fedora Installation :: Dual Boot With FC10 - XP Hangs
Mar 3, 2009
I installed fedora on my second hdd, the other one had xp before fedora, now in grub it shows xp as other and wont boot into it, just hangs there. SDC is an external drive and sdb is the xp drive as you can tell by the filesystem.
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x836db2c4 .....
I did a fresh install of Fedora Core 10 32bit on my Caompaq Presario AMD 64 laptop which originally only had Vista ultimate 64bit. When I go in to grub and choose windows I get a screen that says:
Windows failed to start... File: windowssystem32winload.exe Status: 0xc0000225 Info: The selected entry could not be loaded because the application is missing or corrupt.
I upgraded from FC10 to FC11 yesterday.I had no problems using FC11 after I looked into the bootloader (not intuitive - Ha!).Tried to boot up this morning; and things seemed to work well until I tried to call up Firefox (added a few themes yesterday).The window pops open; but the computer freezes on the spot with an alarm (generic "beep", w/o the finishing "p").Tried it with Epiphany; and I get the same results with the exception of actually getting to the Home Page.Yum works for the most part - I reinstalled Firefox (no effect); but couldn't reinstall epiphany (keeps saying "there is no such package - did you mean 'epiphany'". No typos on my part - go figure). Doing Software/Package Updates (via System Menu) freezes the box as well.Did it with the system monitor on. It doesn't appear to be related to CPU Usage.
Had a FC10 liveUSB and used it for awhile (e.g. to check out the forums). After giving my ISP some grief about downloading speed, immediately received a note from their Abuse Department, saying that my machine had been infected with a virus and had been sending spam emails (post upgrade to FC11).
I have just installed Karmic on a dual boot system with XP and Ubuntu on separate drives.This set up worked ok with Jaunty. When the boot menu comes up, selecting Linux results in a successful boot. Selecting "Windows XP home edition (on /dev/sda1)" results in the screen changing to blank with the word "Grub" in the top left corner and no further progress.No error codes associated with this message. I've tried suggestions I've seen in various threads but have had no success.
Below is the contents of menu.lst:
# menu.lst - See: grub(, info grub, update-grub( # grub-install(, grub-floppy(, # grub-md5-crypt, /usr/share/doc/grub # and /usr/share/doc/grub-doc/.
I have successfully installed Ubuntu 10.10 on two older computers, one a laptop using wubi, and the other an older Dell 8250 using an install CD with a dual boot on one drive. Now I'm trying to install Ubuntu 10.10 32 bit to my Windows 7 64 machine which has one C: drive with one partition and plenty of free space, with the goal of installing Ubuntu to a logical second partition on an external hard drive attached with a USB connection.
Unfortunately, after I boot from CD and start the install, I can't get past the install screen titled "Preparing to install Ubuntu", on which I have checked "Download updates while installing" and "Install third party software". I have three green checks for the install criteria and am connected to the internet. After I click "Forward", the spinning "busy" mouse icon continues to spin for about 20 minutes (I haven't gone longer than this) but does not progress me to the next screen. I can quit the install by clicking on "Quit".
I recently setup a file sharing server with FC10 running Samba...
I got it running perfectly and it ran great for a few weeks. I was working on the machine today and tried to reboot it and noticed that it was stuck on FC10's new boot screen. I pressed the esc key and saw that the boot process was stuck on the smb service...
I don't get any errors and the machine doesn't freeze up or anything, it just hangs on the smb service and won't continue with the boot...
Is there anyway that I can get the system to skip the smb service so that I can get into the system? I don't know what's changed or what's causing this sudden hang in the system at boot.
I tried the ubuntu live CD to attempt to go in and edit the /etc/rc5.d scripts to try and skip the smb service start but I am not sure where to look for it...
I've been using ubuntu for a couple of years rather successfully on my dual-boot Vista/Ubuntu. It upgraded to 8.0(4?) LTS, 10.04LTS and I kept it there until this afternoon I followed the instructions on the ubuntu site to open up a terminal and update-manager --somearg to provide me with a nice little "Upgrade" button on the update manager. I clicked said button per the instructions, let it do it's downloading and whatever else it does. The last step of the installation is a system reboot. I let it do that, and then my grub menu comes up as more-or-less this:
If I select the top one, I get: Code: Starting up ... with a blinking cursor under the S for a LONG time (used the power switch after ~40 mins). I tried the second 2.6.32-32 option for recovery mode. It spit a bunch of gibberish to the screen for a couple seconds and then stopped, presumably doing the same thing, just with 100% more gibberish. I tried booting into Vista, that worked fine. Just to reiterate, I've not yet seen a 10 LTS login screen or desktop, and can't get one yet (just a "Starting up ...") Just to add, I did try searching, but since the only info I had to go on was 8 LTS to 10 LTS upgrade, and "Starting up ...", well those are just hard keywords to get any meaningful info.
I am trying to boot kubutu from FC10's grub. FC10 is in MBR, installed kubuntu without grub. Is that a problem for me now? I mean, should I need to install kubutu grub in order to boot from FC10 grub? I tried with these methods but nothing works:
title Kubuntu 8.10 Linux chainloader +1 title Kubuntu 8.10 Linux
I have an Intel DG33TL MB, Intel Core 2 Quad Q9650, 8GB SuperTalent DDR2-800, and 4 Seagate 500GB hard disks. The disks are connected to a 3Ware 9650SE-4LPML and set for RAID0. I partitioned the drive in the following manner: 900GB for XP-Pro x64 (first install), 100 GB XP-Pro (installed second), and the remaining for FC10. After installing FC10 x64 using downloaded DVD .iso I am getting the following error on reboot:
Code: Reading all physical volumes. This may take a while... Volume group "VolGroup00" not found.
How to get the Linksys: Wireless-N PCI Adapter with Dual-Band (WMP600N) working under FC10 with WEP encryption and linking up to a 54Mb/s Network. Hardware : D945GCLF2 with Intel atom330, 2G memory. As I got to this in a roundabout way, I would recommend that you follow the following steps and see if somewhere along the line your wireless starts working.
1: Get the latest driver from Ralink: [URL] In my case 2009_0918_RT2860_Linux_STA_v2.2.0.0.tar.bz2 (the line starting with RT2860PCI) Unpack, read the README_STA file and follow the instructions. Do: make && make install After this I could only get a wireless connection by doing:
I upgraded to FC10 from FC8 and my Gnome-panel no longer spans both screens in my dual monitor configuration. This worked fine in FC8, and I can't seem to figure out how to make this config work in FC10.
I've tried Xinerama and Twinview, and various configurations in xorg.conf, and cannot seem to make it happen.
How to make both my panels (top and bottom) go across both screens?
HW config is: AMD Athlon 64 X2 5000+ Black Edition, MSI 785GTM-E45, 2X 1Gb Kingston HyperX PC2-8500. I have set up GRUB to dualboot openSUSE 11.2 and WindowsXP. Initially i had set up system with defaults: CPU@2600MHz (200X13) and therefore RAM@800MHz. Both openSUSE 11.2 and WindowsXP worked just fine. Memtest86 found no problems.
But after a while i decided to change this setup to: CPU@2500MHz (250X10) and therefore RAM@1000MHz, as it promised better overall performance. And now Windows still boots and works better then before. Memtest86 still can't find any problem. But openSUSE 11.2 hangs at boot. I've suspected cpufreq governor, but changing from Ondemand to Conservative in /sys/devices/system/cpu/cpu0/cpufreq doesn't help.
I'm running Ubuntu 10.04 and a small Windows 7 partition (cuz I can't get Ubuntu to run my MSI TV@nywhere plus card but that's another issue).I can log into Windows fine. If I choose Ubuntu, however, the boot process will go thru a few screen flickers. Then one of two things happens:1) I get a scrambled up pixelated image (not sure what it is) for about 3 second, then it goes into the login screen and I can log in normally.2) I get the scrambled up pixelated image and it hangs. This happens about 4 times out of 5 when rebooting.
I do have an nVidia card and a beta driver (they published it the 21st, I believe, of this month) but this happened long before that. It's happened ever since I installed any of the drivers (I've tried a couple different versions, hoping to fix this) for my card.
My system is a frankenputer: Phenom II quad core 3.0 cpu nVidia GeForce BFG 6600 4G DDR3 500G drive
Note: I do have 3D rendering when I finally get into the desktop. Everything works great, except that when I'm playing my mmorpg, Regnum Online, it freezes the entire computer and I have to reboot (not sure if that has anything to do with it or not).In case it's needed, this is my grub:(Second note: I'm sorry for the length of the post but I don't know how to upload documents/files to show)
# from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ###
I have just completed a dual boot installation of FC10. The install was done from CD's I downloaded from the Fedora website. The installation (seemed to have) went fine, and the machine still boots into XP if selected from the menu. The Fedora installation does not complete the boot process. I have three bars that move across the bottom of the screen, and the Fedora 10 graphic tuns white, and then the system hangs. I have let it sit at this screen for as long as 30 minutes. The screen will blank occasionally, but returns to the same place if I hit a key on the keyboard.
I have it installed on an old HP E800 netserver, running dual P3-866mHz processors, 2GB ram, a ATI Radeon 7000 video card, and three 36GB SCSI drives, non-raid. I know FC10 will run on this machine, as I have a friend running it on another E800 without any problems. This machine does have on-board video that is disabled only by plugging a different video card in (Phoenix BIOS).
This is one of those newbie questions about where I look to find error messages so that I can understand what the issues might be. My Fedora 12 setup invariably always hangs whenever I login following a cold boot. I login to x/g-nome, the screen clears and the initial background appears and then that's it.
I've been getting out of this by switching to another TTY (CTRL + ALT + 2), login as root and issue "shutdown -r now". System re-boots and I can login normally. I can see a stream of messages, I think relating to x scroll up the screen rapidly after the shutdown command. I'm not fast enough on the Pause button to read them. My question(s) then is... is there somewhere I can look to see what those messages might be? From the symptoms described initially, anyone have any thoughts on what the issue is likely to be?
I have just upgraded my F11 x86_64 system using the DVD ISO.
After rebooting as requested: 1) Cupsd fails to start - it can't find libaudit.so.1 (this doesn't worry me in itself). 2) Boot process proceeds until starting hald. This gets an OK response, but then the process hangs. No further output appears on the console. Pressing [ENTER] just causes a blank line to appear on the console. Pressing CTRL-ALT-DEL causes a reboot, and the same symptoms re-occur.
I'm tempted to boot with the rescue disk, save a few critical data directories, then start afresh with a clean install, but is there anything I can do to salvage the upgrade?
I currently dual-boot Windows Vista and Suse 11.2 on my Gateway desktop machine. I'd like to try out Fedora in a triple-boot situation.
My trouble is that the F13 Live CD hangs during boot. I've checked the hashes of the downloaded ISO files, and done burns on multiple media. During booting with the Live CD, my box hangs and I have to use the physical power button to turn off the box.
I've tried the 64-bit KDE spin (my preferred choice), the 64-bit GNOME version, and also the 32-bit KDE spin, and all of them hang at the same point. Removing the "quiet" boot option shows that it hangs after setting up my built-in card reader. When I installed Suse 10.3 on this same machine, I had to use the flags "acpi=off" and "brokenmodules=pata_it821x". Would the syntax be the same if I wanted to try with those boot options with the F13 Live CD?
Using the ISO files in VirtualBox inside my working Suse install works just fine.
I recently upgraded through 'YUM' from Fedora 14 to Fedora 15. The upgrade appeared to be successful until it re booted, ever since then it hangs at Code: Started SYSV: Enable monthly update of smolt. I have downloaded the ISO and burned it to DVD on another system which I used to try to rescue the installation, so far to no avail. My system specs are in my signature below (Laughlin is what I upgraded from).
I'm attempting to install F12 64 bit. I currently have F10 running on this system. I'd like to do a clean install. I'm using the DVD. I boot the computer with the DVD in. I choose the first option (Install or upgrade). It starts the boot process and then it hangs. [URL]
After asking at #Fedora I was given the advice to boot with `intel_iommu=off`. That gets me slightly further in the process. It gets to the point where anaconda is starting. Then all heck breaks loose. It appears the monitor loses the signal from the computer (power light turns red just like if the computer was off). The caps lock and the scroll lock lights on the keyboard blink about once a second. The DVD drive continues to spin for about a minute and then stops. Since I have no display, I have no idea what's going on.
I was using Ubuntu 9.10, until I got a new graphics card (Nvidia GeForce 9800 GT). After I got that upgrade, Ubuntu no longer supported that card for some reason, so I decided to try Linux Mint since it was a close relative to Ubuntu. Still no support for the video card.
I've always wanted to try Fedora so I decided to grab the x86_64 live cd and burn it. I stick it into my disk drive and it boots where it shows me the options to "Boot" "Verify and Boot" "Boot from Hard Disk" and one other option.
I tried the Boot option, and after selecting that, everything stalls, and my display turns off (not the entire monitor, just the display). I tried Verify and Boot, and still no luck.
I have also tried the i686 live cd and the same issue. It can not be the way I am burning it, cause I've gotten other live cd's to work with the same method of burning. Is it that Fedora does not support the card?
I am trying to get the GNOME version up and running.
Sometimes (but not every time), when booting my Dell Inspiron 530, eth0 will not come up right away. I can boot and log in to Gnome, and the NetworkManager applet shows that the ethernet cable is unplugged. After sitting for 5-10 minutes, it will link up and everything works. If I unplug the network cable and plug it back in, it comes right up. But once it's linked, it works fine and never disconnects after that. I've tried switching to a different port on my switch and a new ethernet cable. So I suspect it's some sort of weird kernel problem. I checked /var/log/messages and the only thing that looks weird is:
Oct 17 07:51:49 obi-wan kernel: e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k6 Oct 17 07:51:49 obi-wan kernel: e1000e: Copyright (c) 1999-2008 Intel Corporation. Oct 17 07:51:49 obi-wan kernel: e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level,
[Code].....
But I have a second Inspiron 530 that has the same entry and it works fine. Has anybody seen a problem like this? I've looked around and so far can't find out the exact issue. I've upgraded NetworkManager to the latest version for FC10
We (2 persons) are experiencing a total freeze on first boot after installing fc10 from the 6 CD distro set, and yes, we used the same discs but ran the validate check on each. One machine is a rather ancient Acer G7500G which had previously been running FC3 happily; the other is a very new Dell Notebook (now running FC9 happily). The freeze occurs after the progress bar turns all white. Pressing escape shows that the volume group(s) have been found and are now "active", but that's all she wrote.
The systems can be mounted in repair mode and I notice that there is no "functions" file in /etc/rc.d/init.d but this may be normal for FC10.
The Del owner have officially given up, but before I throw FC10 out and go to 9 also, I though the question was worth asking: has anyone installed FC10 from the CD distro as opposed to the DVD distro successfully?
I currently have XP installed on a NetBook (Samsung NC10), and would like to run Fedora on it. I'm currently looking at putting Fedora onto a flash memory card to test it works OK on the hardware, before installing it to the hard disk. The problem I've got is that the boot sector is occupied by WDE software (TrueCrypt). Will this pose a problem for dual-booting XP with Fedora, or will GRUB move the boot loader in the usual way?
I'm bonding the two NICs on my FC10 server to create a bonded LAG between it and my Cisco Catalyst switch, but during kernel init, the system always give me a notice that "bond0 doesn't appear to exist" so it skips it.Once I log in, I can always open Network Manager and the bond0 interface goes from "Inactive" to "Active" and bond0 immediately works, and I can restart the appropriate network services and everything is fine. But any idea why this bonding wouldn't be initializing during boot up? The ports on the Cisco are configured for hard set speed and duplex and portfast is turned off on them.Is there a guide for best practices for creating LAGs (bonded interfaces) between FC10 and Cisco switches?
I've been upgrading all our servers from FC8 to FC10. One thing that is no longer there are the start up script messages, being replaced by the white and blue line at the bottom.
I like seeing the bootup messages when I reboot (rarely) to make sure nothing went wrong and not having to go into boot.log to check it.
Code: Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using metadata type lvm2 2 logical volume(s) in volume group "VolGroup00" now active Welcome to Fedora
I am using FC10. how do I change the resolution of the "Boot Up" screen? My monitor is 1024x768 capable but my boot screen is 1280x1024. I don't get anything until it finally loads X Windows. When my machine is booting up I cannot see the screen because my monitor can't handle it. When I hook it up to my other monitor (1280x1024 capable) I can see the boot up screen. I'd like to be able to see the boot screen in case there are any errors I need to se. How do I change it?
I just set up a dual boot on a system with fedora 12 and XP. XP in on one hard drive (sda) and Fedora on a second hard drive (sdb).
I installed grub on the Fedora disk so as to not touch the windows disk at all.
Prior to installation, in the bios, I set the Fedora disk (sdb) first in the boot sequence, and then XP (sda) so that the grub loader would boot up by default. (If I set the windows drive first then the system bypasses grub and loads straight into windows.)
My system can now boot up into Fedora fine, but if I select windows from the grub loader menu I just get a blinking cursor - windows will not boot.What do I have to do so that grub can boot into XP?
Have had a clean perfectly working copy of 2.6.31.6-166 for months and after two updates to 2.6.31.12-174.2.3 and 2.6.31.12-174.2.19, neither of the newer kernel versions will allow machine to boot properly. Start-up hangs at the preload daemon with a flickering screen. To use machine, must use grub chooser and choose the original base kernel.
Running on Tyan h2000m board, opteron 2356, Nvidia 9800 GTX+ and 12GB of dram with SELinux security enabled.
I performed a clean install of Fedora 15 from DVD and it goes fine until the end when the install program says to reboot the computer. Once I do that, the computer hangs before Grub loads, i.e. just after all of the BIOS messages, so there isn't any error message to indicate what is wrong. I had no issues with Fedora 14.