After doing a reinstall, and then upgrading, I have a problem: as the boot script comes to ATD, it hangs. Someone suggested doing an interactive start ---- and it worked! Just say no to ATD, and boot goes well. Of course, I don't really want to do that each time. How do I remove it? That is, get it out of the init.d or rc.d boot procedure
View 4 Replies
I have been using F10 since its release and have not had any trouble until now. During my last session, I ran an update. Today when I boot my desktop (single boot btw), it hangs just after the boot loader. The only sort of warning is:
eth0: link up, 100Mbps, full-duplex, 1pa 0x45E1
I have browsed the forums to no avail. Other have the same issue, but with no posted solution. I have tried disabling NetworkManager, but I think it may be the service that runs after NetworkManager.
i've installed nvidia driver by
Code:
yum install akmod-nvidia
every thing went ok , but after reboot the system hangs right after
[code]...
Boot-up hangs at black screen with blinking cursor in upper left corner for over 2 minutes before continuing. I select F 14 with grub hit the enter key and go straight to a black screen with blinking cursor. Hitting the esc key does nothing until boot-up actually starts. Afterwards, boot-up is perfect. I had this problem a few upgrades ago and the fix was simple but I can't remember what I did. I've searched every phrase I can think of and can't find a thread that addresses my problem.
I have a F 13 kernel on my machine and have no problem booting it.
Dual-boot, F 14 and windows 7, 64 bit.
Whenever I boot fedora core 13 it starts Plymouth and a txt progress bar starts at the bottom. Whenever it gets to 100% it flickers a little bit then does nothing. The system doesn't hang I can still crrl-alt-delete and it shows the processes stopping. When it displays the programs starting it gets to jexec and nothing happens.
View 1 Replies View RelatedI 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).
In F10 the boot sequence hangs just after loading anacron. I booted with interactive mode and after saying 'yes' to starting anacron I'm prompted to start 'local'. When I say yes, my system hangs.
I've seen quite a few posts regarding very similar issues that people were having. None of them seem to have a clear cut solution.
Some posts mentioned about the wrong video drivers, however I've been using the same video drivers for a couple of months now and never experienced this problem.
I looked at /etc/rc.local and all it has in it is 'touch /var/lock/sybsys/local'
I also looked at the file above and there is nothing in it.
Any ideas/solutions? Everything was working just fine the other day. so I'm completely baffled.
Running kernel-PAE-2.6.29.6-217.2.7.fc11.i686
Boot hangs on 'starting atd'
Select 217.2.3 and it boots OK.
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.
After Gnome logon it may hangs in any moment (window scroll, app start, opening url)
If sound was playing in that moment it continuously repeats last sample (about 1 second length), but do not respond to mouse move/click or keyboard. If to let it stay in this state nothing change - sound sample still repeats and no response to input. I need to reboot it by reset button. Sometime when I press reset nothing happen then after couple of seconds computer turns off, after 1-2 sec on and then starts booting.
During first 15-20 minutes after booting it may hangs multiple times but after that it works without problems.
Tried do not logon 20 minutes after boot - do not help, it hangs anyway. Only helps logon and do nothing for awhile.
This behavior have started after F12 installation. F13 installation changed nothing, only F11 worked perfectly.
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 am installing Fedora 15 as a guest machine on virtual box. the installation completes fine, but it gets hanged on the date and time screen during first boot. Even on clicking "Forward" button it doesn't work and just gets stuck there.
I am using windows 7 as the host machine and I have given 1 GB ram and 8 GB hard disk to guest fedora OS.
Before the installation, I checked the media also it was shown to be correct. The media I am using is virtual clone drive for DVD ISO image. VirtualBox version 4.1.2 was used.
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'm using Fedora 12 on my Thinkpad X200 and had no major problems since Installation of the Release Candidate. Unfortunately, since a week Fedora makes trouble when booting:
The system boots some times without any problems, some other times it hangs in the following way:
Code:
Gdracut: Mounted root filesystem /dev/sda1
dracut: Switching root
Welcome to ^[[0;34mFedora
Press 'I' to enter interactive startup
[Code]....
I moved my /var partition using Gparted Live CD version 0.8.0-3. Everything went fine. But when I boot my Fedora 14, I get error message (something like "name_count maxed, losing inode data"). Maybe there are other error messages as well, but they scroll away very quickly. Is there any way to slow them down?
But the boot hangs after starting udev and setting host name to localhost.localdomain. It just hangs there. If I press the [Caps Lock] key, it toggles the Caps Lock LED. If I boot the installation DVD in Rescue mode, it mounts all partitions without problems, and the data is there.
I have been trying to work out how to set up Fedora 15 to automatically mount an NFS share at boot time. I can mount the share interactively using 'mount -t nfs server:/usr/local /usr/local'. When I put the entry in /etc/fstab, it stops the machine booting. It tries to give me a shell ('Enter root password for shell or press Control-D to exit') or something close to that. However, I cannot enter the maintenance mode, it hangs. Same thing with pressing control-D, it hangs and doesn't get any further.
I rescued the system by booting off a CD, mounting root, and removing the nfs entry from fstab. After that it booted fine. The entry I had in the fstab is: nfsserver:usr/local /usr/localnfsro,hard,bg,intr,comment=systemd.automount0 0
I put the 'comment=systemd.automount' entry in because of some related searches I did in forums.
My Redhat box hangs on boot up after "SELinux: Disbled at runtime" Code: raid1: raid set md0 active with 2 out of 2 mirrors
[Code]...
I'm a bit of a nube with Linux. Have had it installed and Acer Veriton for a while but after last yum update it now hangs on the blue screen with the F bubble in the middle. I can login remotely OK but am not sure what to look for. It seems to be something X11 related but I'm not sure. I would post the relevant logs but am not sure which ones are associated with this problem.
View 5 Replies View RelatedIf 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.
Ever since the kernel update to 2.6.34.6-47.fc13.x86_64, my boot process hangs at about startx time. I boot cleanly at runlevel 3 in either this or the previous 2.6.33.8 kernel. If I execute startx from here (in either kernel), the system hangs at the same place. During the early troubleshooting, I read in another thread (250929) about installing xorg-x11-drv-catalyst, which I did using yum. This led to the failure of the 2.6.33 kernel; yum remove did not fix this. I have carefully followed the instructions in the fglrx HOWTO (updated a week ago by Hlingler) as they relate to a PAE kernel (including reinstalling mesa-libGL), and that fixed earlier difficulties. Hence, I felt I needed a new thread.
dmesg tells me
Code:
microcode: CPU0: patch_level=0x2000032
platform microcode: firmware: requesting amd-ucode/microcode_amd.bin
Linux video capture interface: v2.00
piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
microcode: CPU1: patch_level=0x2000032
platform microcode: firmware: requesting amd-ucode/microcode_amd.bin
microcode: Microcode Update Driver: v2.00 .....
But the program itself reports
Code:
# microcode_ctl -h
This program is for updating the microcode on Intel processors belonging to the IA32 family - PentiumPro upwards (x86-64 included). It depends on the Linux kernel driver. The website urbanmyth.org/microcode (mentioned by yum info microcode_ctl) clearly indicates that Intel has taken over this microcodecode distribution, and suggests that it is no longer valid for AMD processors.
I found a reference to a kernel configuration flag CONFIG_MICROCODE_AMD (as a plausible subsititute for CONFIG_MICROCODE_INTEL) that possibly belongs in a script in /etc/init.d - but the above context leads me to suspect this is not true any more. In any event, those flags are not mentioned anywhere in my init.d scripts - in fact nowhere in the entire /etc tree. My microcode file exists, and is dated March 23. How do I get it installed? Or is this completely unrelated to my hanging boot problem, as suggested by the "platform microcode" line in the dmesg output? If so, where should I be looking?
I have a problem with the kernel update to 2.6.34.6. Up until 2.6.33.x my system boots fine, but with this update the boot stops at the moment that the mouse cursor should become visible. To resolve the problem, I've gone back to 2.6.33.x and removed the 2.6.34 kernel but I wonder what happens with the next kernel update.
Anyone else having this problem?
I have a very strange problem with Fedora 13 on my home PC. When booting it just hangs at random points in the boot process. When it happend the first time, I thought the PC probably is completed frozen, but then I discovered that hitting the return button got the boot process going on again, but just step by step. That means on every boot I have to keep hitting the return button until gnome starts up, that's very annoying. So for any reason the boot process seems to switch to interactive mode somehow...
I already removed the kernel boot options rhgb and quiet to see, where exactly this happens in the boot process. But as I said, it seems to be completely random. Sometimes it's when "Starting udev", sometimes, when setting up eth card, when starting atd, and so on. It's different every time.
By the way, a similar thing happens when shutting down. It can take up to half an hour until the PC really shuts down. But it's usually going faster if I just keep hitting return after issueing the shutdown command (which actually looks a bit dull). But the PC finally shuts down at some point. That's not the case when booting up. I thought, maybe there's some kind of timeout problem. But even waiting for two hours, the PC does not startup without keeping hammering the return button
I have installed Fedora 11 and have been using it for about a 4 months now. Everything has been working just fine until this morning when I booted up the computer and it hung at the blue screen with the F bubble in the middle. I waited about 10 minutes without any change to the system. I held down the power button to power off and tried starting the computer again with the same result.
View 3 Replies View RelatedHave 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.
View 3 Replies View RelatedRecently i've upgraded my fedora 11 to 12 using the preupgrade command and now I have a problem booting! when i start the interactive boot it hangs after trying to run the service local, it looks as if its trying to boot because the cursor blinks really fast then blinks normally after a few seconds. no error was stated during the event. what seems to be the problem here?
View 3 Replies View Related
