I'm having problems booting up my Fedora 14 system. I see the Fedora splash screen (the one with the egg-like logo that colorizes as it loads); the logo fills up completely and then everything hangs - all I see is the egg logo, and nothing else is ever displayed. I also can't get to any of the ttys via the CTRL-F1 sequences.
I can boot into single user mode just fine. The install scripts all run just fine. The system itself is actually up an running, so I suspect this is either something in the KDE startup, or after init processes all of the start up scripts.
I'm assuming this isn't a startup script problem, because I see a "started XXX" message for every service in the rc.5 directory - in other words, all the startup scripts ran from rc.5.
So, how do I find out what is hanging? I'm not seeing anything in /var/log/messages, and pstree didn't tell me much about what init was doing.
I used to be able to follow inittab to see all the things it did at boot, but since inittab was stripped of everything it used to do a few releases ago, I don't know what init is doing anymore.
I have some trouble booting the current KDE Live Cd (11.2) on my Laptop. I tried USB and CD both. The laptop hangs on the bios bootscreen and I cant select any further option like a boot device. No problem I have with an Ubuntu CD.
What is the best method for debugging the booting process? Is there a cheatcode (tried debug and failsafe). Slackware 13.1 with standard linux kernel 2.6.35.8. I having a problem with a dell server 2860 booting my build. It is hanging on
[Code]....
Booting my previous kernel 2.6.27.27(different disk with different initrd.gz) it loads the same as above but continues with
Code: loading iSCSI transport class v2.0-870 iscsi registered transport tcp I'm stumped it the problem is with the ata_piix module or the iSCSI transport module or some firmware I might be missing. I booted other pcs without issue.
I am in a situation to boot fedora 15 live cd in to command line mode, not graphical mode, for some testing purpose. how to change argument during booting mode
I am working on Fedora core 4 with kernel verion 2.6.11.. I am running a Manager process which spawns child process. If a child process exits , the SIGCHLD signal is processed in parent process and it is forked again. When the parent process receives a SIGTERM signal it first tries to kill the child process using SIGTERM signal . if the child process dosen't get stopped then kill it using SIGKILL. Now,the Parent process sometimes gets hanged and the strace shows : futex(0x98535e0, FUTEX_WAIT, 2, NULL <unfinished ...>
My Fedora setup is working great so far, and I don't really have any complaints. I installed it on a portable hard drive, connected over USB. Thing is, I installed my system with the LiveCD, and I wanted to download the full DVD for a friend because of his needs for his system. When I try to download the full DVD (whether over Firefox or Transmission), the system hangs by suddenly showing a screen with the Fedora logo in the middle and a light blue background, the same as in boot up. Also, my caps lock blinks in a consistent fashion like a metronome. The same happens whether I try to download to the portable hard drive or to a FAT32 partition on my laptop's actual hard drive. Is there any way to fix this, or can I be calmed by the fact that it just happens because it's installed on a portable hard drive? This problem isn't happening on Ubuntu (which is installed on my laptop's hard drive), where I am downloading from right now.
I've been having trouble with my desktop ever since I upgraded from F 11 to F 13 last night. Finally, however, I got the proper version of the nVidia drivers installed. However, it's stopped completing boot. I've edited grub at boot to get it to show the boot messages and find that the last thing it reports is success in registering the binary for Windows applications. After that, it just sits there, doing nothing. I can go to an alternate console an d log in, but that's all.
If I log in and run startx, it fails.It reports that it was unable to load the nvidia module and "no screens found." Does anybody know what I should do next?I've removed both kmod-nvidia and akmod and am going strictly with the nouveau drivers.I've booted, used Ctrl-Alt-F2 to get a console, logged in as root and run the setup program to configure X to run that way, then returned to the main console and logged in as myself. Shortly after my wallpaper shows up, and long before I have a working desktop, it goes white and stays that way. Aside from getting a different video card (The old one worked Just Fine right up until I upgraded.) what else can I do?
I installed adobe reader quite some time back. It was working fine. Nowadays it gets stuck up and then the screen fades out and then after some seconds it gets back to normal. What could be the problem.
two months ago i bought a fujitsu siemens pc (pentium 4)and installed ubuntu 8.04. initially the computer was very slow and you couldnt run many applications at once, in the end it just becomes very slow and even hangs. it could take years to open open office word processor, so i thought it had a problem with the RAM. it initially had a RAM of 256MB, so i bought another 256MB and made it 512. it started to work very fast and it could open word so fast, i could run many applications at once until recently when it began to hang again even when there is only one application running, but it still is very fast, though it hangs often, is there a solution for this problem? i am oftenly forced to restart the machine and its boring.
I have just installed Fedora12 x86 64. On booting more often than not it hangs just before completing the login screen.I will try some of the options in the wiki. In the mean time has anyone else experienced this and resolved it.The odd thing is although the keyboard is not on, (num lock light goes out as boot starts and only comes back on if it has fully booted), the mouse will move around the screen but the click has no effect.Note the same behaviour was shown on the x86 64 live cd which I needed to install to enable me to create a bootable usb stick from the x86 64 DVD.
When I went to start up the computer, the kernel usually hung at the same place on boot up, although sometimes it booted just fine. The default kernel is 2.6.31.9-174.fc12.x86_64. It's boot up arguments are:
I also have kernel 2.6.32.7-37.fc12.x86_64, 2.6.31.6-145.fc12.x86_64, 2.6.31.5-127.fc12.x86_64. I have seen the same behavior out of all four of them. Last night I ran Memtest86+ all night. It took eight passes with no memory errors. As far as hard disks go, I have two Seagate Barracuda 1.5 TB drives operating as software RAID 1 (mirroring). One of the drives does have three bad sectors. The motherboard is an Asus P6T6 WS. This morning I plugged in the GP diagnostic chip that came with it, but I'm not seeing a whole lot useful there, except that now it is just displaying "FF" non stop.
I did some poking around on the web, and it looks like "FF" is supposed to mean that the CPU isn't properly seated, which makes no sense because the system monitor software is detecting all four cores perfectly, and I have no other odd behaviors anywhere else. At this point I'm rather at a loss to understand what could be causing the difficulties. Sometimes any of the four kernels boots fine, and sometimes they don't. The funny thing is that on the blue "boot progress bar" all four kernels hang at exactly the same spot if they hang at all. After doing some more poking around, I'm relatively sure that "FF" does NOT mean that the processor isn't seated correctly. I'm going to try contacting Asus and see how far I get towards getting some good info on what the diagnostic codes mean.
a few weeks ago i installed Ubuntu 9.10 on my PC on which i was previously using Ubuntu 8.10. However after the installation of the new version, my machine keeps hanging all the time,like i can use it for 20 minutes and it hangs and completely freezes, so i have to force a shutdown in order to restart and it does so very often, i don't know where the problem really is. The PC is Pentium 4, 40GB hard disk, 512MB RAM, processor speed of 1.8 GHz.
I am trying to install Fedora Core 10 64bit on my Desktop... i've been running FC7 on it until now.The installer continues until the Anaconda GUI, and I am able to click next on language select, then when I click to select "U. S. English" as the keyboard layout and press NEXT, the installer hangs. I ran the disk verification at the start and it passed, so can't be a corrupted installation disk.I can move to the other terminals away from the Anaconda GUI Installer, and in one
Code: INFO: moving (1) to step welcome INFO: moving (1) to step language
Almost every other time I run yum update, I'm getting mirror problems - this is losing all my confidence in Fedora for several reasons: a) it's wasting time - what should be 1-2 minute updates are taking 5-10 minutes and often (like tonight) not even completing b) since it keeps hanging and switiching mirrors during downloads I wonder if the updates are coming thru okay c) the fact this is not being seriously addressed makes me wonder re Fedora quality. Add to that the constant and real annoying kernel errors popping up re network manager and sierra wireless (even when my sprint card is not plugged in).
I installed Fedora 12, 64 bit on my Dell Latitude D820 laptop with Core2 Duo processor(7200 speed) and 2 gigabyte Memory.
I have updated the yum. I have enabled the rpm repositories.
It is very weird that my system suddenly works very slowly and hangs. every time I login after a while the CPU usage goes up to the end with out any reason!
Before this I had installed Fedora 12, 32 bit and I had the exact same problem.
I have installed Fedora 6, 7, 8, 9, 10 and 11 on my laptop before and I had non of these problems with them.
The interesting point is that after hanging my system works constantly slow even when I restart my system! It is slow even in booting the BIOS and start up and choosing the kernel page!
The only remedy to get rid of the slow working for a while is to Shut down the system completely and turn it on again. Restarting do not make it work normally just shutting down makes it normal for a while.
A little while ago I moved to F14 from Ubuntu; I've been ok, but recently sudo has been causing me trouble :/It seems to hang, but eventually produces some output indicating that it has been waiting for me to input a password; but it hasn't prompted me for one.
Acer veriton 5000 pentium4 1.7mhz 2Gb ram. double booted with win2k.I had no trouble upgrading from Ubuntu 8.04 to 9.04. For some reason 9.04 would not upgrade to 9.10 so I installed from disc, with minor hics. Now works well but randomly hangs with no warning and I have to switch-off and restart to continue. Very annoying. I do not get any error alert it just hangs and when rebooted carries on quite unperturbed.
Additional info. on booting in recovery mode got following:: 754677 Render error detected eir??????
I had dual boot Win Xp and CentOs Linux. I have small harddisk and needed more space, so I removed CentOS linux with partition manager and rebooted. Now I can not boot my XP. All I can see is GRUB prompt. Keyboard do not respond except CTRL ALT DEL. I know I have to fixmbr. But I can not boot from my bootable XP CD. I can boot from CentOS linux DVD and enter into linux rescue mode. From that I typed "grub" entered into grub. Then I tried
After doing this I can no longer log in, it just hangs on the brown screen after logging in... it also asks me for my password twice before authenticating?
I'm running a Debian installation from which I installed zomeminder using Synaptic Package manager. I fixed several issues with deprecated functions and other miscellaneous stuff. Finally have it working fairly well.However, not quite....zoneminder keeps hanging up as a review the captures in iceweasel. I click on the id field in the table and the event view shows up. After I review several, clicking the delete button on each to move forward Iceweasel hang up with the pinwheel spinning. If I completely close out iceweasel I can then start reviewing again.The following error message appears in the apache2/error.log.
[Tue Jul 26 18:59:36 2011] [error] [client 127.0.0.1] socket_sendto( /tmp/zms-644018s.sock ) failed: No such file or directory, referer: http://localhost/zm/?view=watch&mid=1 [Tue Jul 26 18:59:36 2011] [error] [client 127.0.0.1] array (
I upgraded to Fedora 12 right after release, everything was working fine until update on previous weekend. Looks like it updated Wacom drivers and kernel. Now what I have. I hotplug my tablet in USB, and everything seems fine, I can position a cursor and press buttons, but after I press some button it hangs (LEDs on tablet are responding) I must remove Stylus from proximity in order to make it respond again (while stylus is away LED on tablet switches off for a fraction of second).
If I move mouse during tablet hanging, applications barely respond and if they are it is like mouse button is pressed (selecting text). I tried wacdump, and it's reporting everything's fine (X,Y, Tilt, Pressure everything shows up). I couldn't find evidence that wacom driver is controlling it, but I assume if wacdump is reporting then it is. I have: Kernel 2.6.31.6-145.fc12.x86_64 linuxwacom.x86_64 0.8.2.2-15.fc12
I didn't touch xorg.conf in sense of tablet, but it worked for me in F11 and until now. I'm trying to make least manual configurations possible. Through exploring /proc/bus/usb/devices and kernel messages I confirmed that wacom drives is handling the tablet. And I noticed that in X's log
(II) config/hal: Adding input device Wacom Intuos3 9x12 (**) Wacom Intuos3 9x12: always reports core events (**) Wacom Intuos3 9x12 device is /dev/input/event8 (**) Wacom Intuos3 9x12 (Wacom Intuos3 9x12) is not a pad (**) Wacom Intuos3 9x12 is in absolute mode (**) WACOM: suppress value is 2 (**) Wacom Intuos3 9x12: reading USB link (**) Wacom Intuos3 9x12: threshold = 61 (**) Wacom Intuos3 9x12: max x = 60960 (**) Wacom Intuos3 9x12: max y = 45720 (**) Wacom Intuos3 9x12: max z = 1023 (**) Option "BaudRate" "9600" (**) Wacom Intuos3 9x12: serial speed 9600 (II) XINPUT: Adding extended input device "Wacom Intuos3 9x12" (type: Wacom Stylus) (EE) Wacom Intuos3 9x12: Top/Bottom area overlaps with another devices. (EE) Couldn't init device "Wacom Intuos3 9x12" (II) UnloadModule: "wacom" (EE) config/hal: NewInputDeviceRequest failed (1)
I've encountered quite similar error in openSUSE when was configuring tablet manually in xorg.conf. As I can see problem is with "pad" device, which I disabled in openSUSE in order to make X running. So why is it not working?
I have a Compaq CQ40-616TU Laptop. I have installed fedora 11 64 bit more then 20 times and facing the same problems. The Problems are
1) After booting into the fedora it get hanged up and blue screen with the logo of fedora. 2) Some time it shows message that "Could not update /var/lib/gdm/.IC Eauthirity" 3) I have also updated through yum but still facing the same problem 4) I have also tried fedora 12 but during installation process it shows message that no suitable hardware found.
I am using a linux kernel 2.6.36 using mips architecture. I have succesfully booted the machine through Flash memory, but it is not booting through nfs. It is getting stuck at the stage where the image starts loading. In short the vmlinux.img file is being copied properly to nfsroot but the image is not loading.
I was not sure which forum to post this in, so will go with general. I am not absolutely new to Linux, but it has been a long, long time, so please assume I am a novice.I recently installed Fedora 15 on the same disk with my Windows 7 installation,and assumed that I would be able to dual boot. But no joy. Here is the pertinent info from fdisk. Guess /dev/sda3 is my Windows partition.
Device Boot Start End Blocks Id System /dev/sda1 * 63 112454 56196 6 FAT16 /dev/sda2 112640 20269055 10078208 7 HPFS/NTFS/exFAT /dev/sda3 20269056 523837439 251784192 7 HPFS/NTFS/exFAT /dev/sda4 523837440 976773119 226467840 5 Extended /dev/sda5 523839488 524863487 512000 83 Linux /dev/sda6 524865536 976773119 225953792 8e Linux LVM
I added the following to /etc/grub.conf
title Other rootnoverify (hd0,2) chainloader +1
But Windows 7 will not boot. Obviously I have something wrong, but do not know where to start. So if someone could point me in the right direction I would be humbly grateful.
I attempted to install slackware 13 on my laptop and was moderately successful. However in the process of attempting to configure it I appear to have messed something up. After reading about the problems I'm having I decided it would probably be easier to remove the current installation and start over.
I am now trying to install fedora from the dvd, but for some reason the computer will not boot the dvd. I have set the bios to boot from the drive first, and have tried burning the dvd twice, but every time the dvd spins up and shortly thereafter the computer loads lilo. Have I simply burned the dvd wrong twice? I used disk manager on mac os x and the disc reads just fine on the mac that burned it, but still no luck booting.
I'm trying to get it on my own computer at home to work on. I have an iMac, and I also have a disc with Fedora on it (along with sabayon and slax and a few others). I tried booting my computer from the disc, but when I got to the localhost login bit, I couldn't get any further. I have searched for this query already, but seemingly all the answers assume that it was installed beforehand. I haven't installed anything, just put in the disc and changed the settings to 'boot from disc' before restarting the computer. Am I missing something? Also as a separate query, how do I partition the hard drive so I can run Fedora alongside Leopard? And what is the story with virtual machines?
I have Fedora 8 and it was working without any errors, during the shutdown some messages error appears ... Field ... when I reboot Fedora 8 again and when the system is rebooting " Uncompressing Linux .... Ok, booting the Kernel Red hat nash version 6.0.19 starting" at this point it hangs. Since one month back, I removed the default gcc and reinstall old version of gcc for installing NS2.28. It was working without any problem or error.
From time to time I have no connection to the net after booting the machine. This is a wired connection that goes through a switch, then a router to a DSL modem. When there is no automatic connection, I can't connect manually either However if I re-boot the connection works normally.
The Network Connection indicates eth0 and eth1 are both set at "Auto" Strangely the "Last Used" column indicates "Never" for both even when I am actually connected, and on line.
