If I turn off the quiet mode in the boot options, it does throw up some errors (e.g. SQASHFS), and then stops after "starting abrt daemon".
On an AMD Athelon. It worked fine of F9, but started playing up, so I'm looking at upgrading.
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 have fedora 12 32 bits installed on a Macbook pro (intel core duo) I did "yum update" this morning, I have restarted the system and got the following message:Starting abrt daemon: abrtd: Failed to start: got sig 2 FAILEDI have browsed in the web but I cannot find useful information. Then I typed:$rpm -qa | grep abrt
abrt-libs-1.0.0-1.fc12.i686
abrt-libs-1.0.3-1.fc12.i686
abrt-addon-kerneloops-1.0.3-1.fc12.i686
[code]...
why does hal daemon hangs? but if i try the interactive booting and disable the hal upon starting,it will boot up. so maybe i can just disable this every time it boots, how can i do this?
View 2 Replies View RelatedI installed Centos 5.5 yesterday and discovered that the hal daemon was failing to start on boot.
The messages showed that the hal daemon was hanging because nss_ldap could not connect to the ldap server. It eventually failed and the system came up multiuser without it.
When I started looking into the problem I discovered that hald was being started quite early in the boot process. It's sequence number was 26 (if I remember correctly). This was even before nscd.
If I chkconfiged it off and booted, I could start it successfully once the system was up.
I changed the sequence number to 98 and bring it up relatively close to the end of the boot process.
This works and it starts normally.
Is starting it as early as 26 in the boot process done for a reason? It seems to me that it should definitely not be started before nscd. Does it matter that I moved it to the end of the boot process?
Process and problem description:
1. downloaded ubuntu-10.10-rc-desktop-amd64.iso and burned to CD.
2. re-booted.
3. "ubuntu" is displayed center screen with five dots below text (sequencing white and red).
4. screen jumps to alternating horizontal bars (green & purple plus green & pink sections) about 1/4 inch high.
5. cd activity light stops blinking.
6. no standard desktop ever appears.
System:
- Asus A8N-VM CSM with integrated nVidia C51PV [GeForce 6150] display
- AMD Athlon(tm) 64 3200+ CPU
- 2.5GB DDR 333 MHz memory
Has anyone else run across this? Obviously, trying to convince a friend to switch to ubuntu using this CD would not be good.
I've followed this guide [URL] after rebooting the system hang at:
starting ati external events daemon [OK]
This line start blinking for a while, then nothing happen. I am using a radeon hd 4225. (I'm booting with acpi=off).
I downloaded Fedora 10 LiveCD, then stick it in to my computer. It seems to start up nicely, but then I get this error:
Loading vmlinuz0..........
Loading initrd0.img...........
.......ready.
This kernel requires the following features not present on the CPU: cmov
Unable to boot - please use a kernel appropriate for your CPU.
So much for an LTS release being stable. I try to boot from a LiveCD and it hangs on "Checking battery state..." I searched the forum for a solution but didn't really find anything. This is an old desktop machine with Intel onboard graphics -- nothing too fancy and nothing it should have a problem with. Yet it's not working.
View 1 Replies View RelatedI just bought a new Toshiba Satellite C650D which has AMD processor. For some rescuing, I wanted to put ubuntu live CD. Ubuntu starts with some screen but then it converts to text mode and just sit there. I have checked md5sum of the iso file I got , before burning it on the CD. After burning the image, I also checked the directory structure on the iso file and the CD. They are fine. Currently I am writing this from XP. How do I use Ubuntu Live CD.
For burning, I used infrarecorder with 'Burn Image' option. I had installed debian and win xp with the same CD , so I can't see the problem with the CD. Anyway, I tried doing this with different CD and the same problem appears.
The CD's are memorex
CD-RW 700 MB 4X multi speed.
And I don't get the ubuntu boot screen at all. Some screen with ubuntu symbol appears and then text mode with some information about the hardware and it hangs there.
I downloaded F10 x86_64 live Developer Spin ISO file from fedora project spins website and burned it onto a DVD...Now when I try to boot from it, I get a menu as usual. Here I select the 'boot' option. Now it shows a 'loading' page with a progress bar and 'Fedora 10' written on the right side [as usual].. After that, on the next page I get the following error..
error: unexpectedly disconnected from boot status daemon I somehow did a reboot, and again the same problem. Microsoft XP and another Fedora are already installed on the same system..
I've lost my boot manager ,can't boot from harddisk ! I've installed F11 x86_64 kde livecd on a partition aside with FC10 and windows xp, created a /boot ext3 partition + a " / " ext4 root partition and a swap partition shared with F10.I've tried to restore booting windows xp with the windoze restore cd with the "fixmbr" tool, but it did'nt fix i
View 4 Replies View RelatedI have an i5 sandy bridge PC with a gigabyte H67M mobo. I have been running maverick amd64 till yesterday. On maverick graphic acceleration didn't work so I decided to upgrade. After upgrade my computer hangs during bootup (with ubuntu logo on screen). I cannot see messages on screen, wasn't ESC key for that? Live CD seems to boot but also hangs computer after loading purple login wallpaper before login dialog is shown. To me it seems a graphic card regression issue since intel mobo graphic card wasn't working fine on maverick too. Also tried to manage with fail-safe graphic mode but this also hangs computer. Is there any log where I can see errors during last bootup from maverick live-cd?
View 9 Replies View RelatedDownloaded the F10 live CD. Booted to it, got past the white, blue, and dark blue loading bar then my screen would be covered in black and white lines. No sign of the GUI except for a mouse cursor. ctrl+alt+backspace would cause the display to blink off and then come back on to the same thing. ctrl+alt+f2 would bring me to a terminal, logged in as root, but from there I couldn't do anything. startx would tell me I had x running on another screen.
hitting tab when booting the livecd and adding "xdriver=vesa" and "nomodeset" to the boot line. That works. I get to the desktop at native res with desktop effects. Killer. I tried to install; install went flawless, rebooted to my HDD and the same issue, black and white bars. When booted to my HDD, however, ctrl+alt+f2 doesn't bring me to a terminal, it causes my monitor to go into sleep mode and my computer becomes unresponsive so I can't do anything from the command line.
Here's what I'm getting at : how do I get my installed version of F10 to do the "xdriver=vesa" and "nomodeset" args that the livecd can do?
My machine is a home built machine I bought off of a friend. P4 2.4 ghz, GB RAM, 2 80GB HDDs, Radeon x1600.
Is it still possible to use LiveCD to boot into rescue mode and run fsck?
I just want to run fsck on my hard disk and make sure all is well.
Does fsck provide and logs or records of what it found?
Is it possible to run fsck without LiveCD?
I am trying to install Fedora on my computer but I am getting a kernel panic at liveCD boot after boot menu. It occurs to me for F13 and F14 (all x64, F14 x86 seems to boot fine but I'm trying to host a x64 guest OS on it so I need to get the x64 version to work)
My system specs:
Dual Opteron 265
4GB RAM
Asus K8N-DL (nVidia nForce Pro 2000, BIOS 1010)
I also tried to install F14 in some other computer (which worked flawlessly) and put the HDD into the computer in question, which gave me the same kernel panic.
I've burned the installation media on several different types of media, and i'm getting an error after the 3 bars load (first screen). I've tried the verify and boot option, and it's fine. I'm trying Fedora 10 on a studio xps 1340. The error messageet isCE hpet increasing min_delta_ns to xxxxx nsec twice, thenForce XPAon: 0about 15 times, thenCE hpet increasing min_delta_ns to xxxxx nsec a few more times, this pattern alternates and the xxxxx keeps increasing, starting at something like 10000 and jumping by 50000 each time it reposts.
View 14 Replies View RelatedI've just installed Fedora (F13) for the first time, on a new HDD, to give myself a dual-boot system. So currently I have:
So, at the appropriate stage in the install menu, there is an option for where to install GRUB, and a drop-down to choose which drive is the primary BIOS boot drive.
However, in both cases, no other drive except my new sdc is visible. So, I can install GRUB to MBR of sdc, or to first sector of boot partition - but no option to put it to my primary boot drive MBR on sda.
Likewise, in the GRUB configuration page, if I go to Add another OS, the only option it gives me is my new Fedora install. It doesn't list the Vista OS on sda at all.
The result is that I can boot to either OS by changing the boot drive priority in BIOS.
I guess my question is this:
- is this expected behaviour from the installer, meaning that I'll need to configure GRUB manually somehow? (gulp ) or
- did I do something wrong in the install process? or
- is this some weird bug manifesting itself?
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 tried running (yum update, also yum install vlc) and i get these error
Code:
Error: Package: abrt-1.0.7-1.fc12.i686 (updates-testing)
Requires: librpm.so.0
Removing: rpm-libs-4.7.1-6.fc12.i686 (@anaconda-InstallationRepo-200911081854.i386)
[code]....
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'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.
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.
View 3 Replies View RelatedAfter installing Fedora 15 from LiveUSB and rebooting it just hangs on a black screen with a blinking cursor (underscore) in the top left of the screen. If it's reached grub, it isn't responding to any commands, and mashing several key combinations (such as ctrl-alt-f1) will produce a beep usually emitted only by the BIOS (hinting that it may never be making its way to grub).
The only particularly interesting thing about the install is that by default it wanted to boot itself from the MBR on my primary-master (Windows) disk. Instead I selected the option to boot from "the first partition in sdb1", which is my primary-slave (Linux) disk, (the first partition being /boot). This way I can change which OS boots by changing the boot order in my BIOS, and so avoiding bootloader wars.
I was trying to get a daemon to load on boot, I stupidly added it to rc.local and it just hangs. I would love to put in a live CD and edit out the line but the volume is encrypted and I cannot get it to mount.
Is there a way I can cancel the daemon from loading or get to the grub menu (not readily visible since I am single boot) and then boot into a console?