My system hangs at boot time when loading hardware drivers for about a minute. dmesg
Code:
[ 11.865604] iTCO_vendor_support: vendor-support=0
[ 11.888580] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.03 (30-Apr-2008)
[code]....
My system hangs at boot time when loading hardware drivers for about a minute. It hangs here:
Code: dmesg
[ 8.196035] udevd version 124 started
[ 8.533233] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[code]....
When booting Fedora 11, my system hangs for a very long time on starting udev. Sometimes I get an I/O error. However, my hardware is fine. I do eventually get in to the system.
View 7 Replies View RelatedWhy is my computer taking around a minute to boot? 10.04 for me is slower at booting than 8.04 is. 10.04 is taking about 10 seconds to get to the login screen, then almost a minute after that before it gets to a fully loaded desktop.
View 7 Replies View RelatedI got a new ASUS EeePC 1015PEM with Windows 7 with the intention to install OpenSuse 11.3 onto it for having a dual booting netbook with enough disk space.I'm installing from an external DVD drive, the checksums of the ISO were ok as well.However, the OpenSuse installer fails at starting up after selecting the action. It hangs, no matter what menu entry I chose, at "loading basic drivers", forever.Because this isn't necessarily an unknown problem I've tried some of the predefined kernel options of the main installer menu. Then I tried some manually entered kernel boot options that helped me in some other installations:
acpi=off, apm=off, CPUFreq=noNone of them seem to have an effect on the installers behaviorI hope that there is people who managed to solve this problem with an actual EeePC model... because I really don't know what I could any more. It's kind of frustrating to not even get past the kernel launch I haven't tried any other distros installation discs, but I don't even intend to. I want OpenSuse because I'm running it on our firms machines as well and don't like shifting between systems.
I've just installed the new Fedora 11 (just released) through a Live CD having 3 partitions created:
"/boot" - ext3,
"/" - lvm (part 1)
swap - lvm (part 2)
now, I want to add my new Fedora system entry to my "central" lilo.conf, resident on another linux distribution. So, i've done
[Code]...
my lilo fedora entry boots fine but... at the middle of "after boot" loading the system hangs and stops the usual driver detection, etc (normally, it hangs on the CDROM detection or USB 2.0 camera detection).
I wanted to know if there is variant of RollbackRX (www.rollbackrx.com.au) freeware or payable. RollbackRX used to Backup/Restore whole system changes in less than 1 minute before OS boot. And it does not consume a lot of free space.
View 9 Replies View RelatedI am having difficulty loading fedora 14 with nvidia 7300gt. I have lots of text on the screen but I cannot enter anything then system hangs there only. The same system runs fine with windows XP The same system runs fine when I use onboard graphic card and disable nvidia. I installed the fedora 14 by disabling nvidia graphic card and used onboard grphic card. I had exactly the same problem with ubuntu, I was not even able to boot from live cd with nvidia. Now I want to use my nvidia graphic card for fedora.
View 9 Replies View RelatedI am trying a new install of opensuse 11.2 64 on my computer. I have tried all the F key options at the bottom of the installation screen but when loading the installation hangs at "Loading basic drivers..."I get the same issue with the 32 bit version of 11.2 and the 64 bit version of 11.1.The 32bit of 11.1 proceeds to install only to crash out with error 3030 when it tries to format an lvm parition.
View 9 Replies View RelatedI am using Ubuntu 9.10. Every time I try to reboot my system it hangs. Shutdowns work properly. I've done multiple re-installations. Nothing I've tried fixes the problem. Does anyone have any suggestions?
View 4 Replies View RelatedI have installed "open-SUSE 11.4" on a "500GB Free Agent External Hard Drive". I didn't have any problem in booting since last week that I booted it from my laptop. Also I did it before several times from then when I try to boot it e.g. from an "Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz" PC the time between loading INITRD and starting boot sequence messages lasts nearly 30 minutes!(i didn't actually measure it but it take a long time in the same order). after starting boot sequence which is showed on monitor everything looks normal. e.g copy of files would be done by speeds between 2MB/s to 30 MB/s depending on the targets.I used to use the external hard derive to boot from different laptops and PC's from start but I didn't have such a problem anytime.
View 1 Replies View RelatedI've recently been having a lot of trouble trying to install a ralink 3062 driver on my ubuntu 11.04 desktop. There are quite a few excellent tutorials on this website. [URL]... In my case, however, adding the conflicting drivers to /etc/modprobe.d/blacklist.conf didn't prevent them being loaded at boot-time, so I could not make the change permanent. I eventually found a workaround online which I thought I'd share here. Once you have updated your blacklist and module list, use Quote:
sudo update-initramfs -u
I'm a beginner so I'm not sure, but I think the problem is that initramfs loads the conflicting modules into memory before the system comes to reading the blacklist and module files. Once you've done this, restart your system and you shouldn't have any further problems. P.s. As far as I know this only works (but should only be a problem for kernel 2.6 and later)
I've got the last Debian stable release, the amd64-DVD-1 file , and copy it to my USB stick, using win32diskimager, as recommended in the installation guide.
It seems to go all fine, but when I rebooted, after entering the passphase it started a fsck "from util-linux 2.25.2", then it says:
"/dev/mapper/Debian-root: clean" and stuck there. i gave it quite a bit of time, tried to reinstall it and also got into the rescue mode of the installer,
I just installed Ubuntu Lucid yesterday, and I'm dual-booting with Windows 7. (They're on separate physical drives if that's relevant.) I've discovered that whenever I restart the computer, it doesn't matter if it's from Windows or Ubuntu or just hitting the reset button, it hangs at "Loading Operating System." If I start it cold, though, it usually works fine. I tried Googling but I couldn't seem to find anybody else with this problem. I'm guessing it's a GRUB problem? Does anybody know how to fix it?
View 1 Replies View RelatedStill cannot watch a flash video in full screen for more than 1 minute before it freezes/hangs. Ridiculous that this bug has been around for YEARS and no one took the time to fix it for new versions.
View 8 Replies View RelatedEver 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 just joined the forum today. I'm not a linux beginner per se (about 4 years experience, now running Ubuntu Lucid on my laptop and windoze-free) and I built the desktop PC I'm typing this on six years ago. However, this is my first HTPC build and my first KnoppMyth install, and I've probably done something foolish.
This was an attempt at a fresh KnoppMyth 5.5 install on a virgin system. Hardware details:
MB: GIGABYTE|GA-880GMA-UD2H R
CPU: AMD|PH II X4 925 AM3 RT
RAM: 2Gx2|GSKILL F3-10666CL7D-4GBRH
HD: 1T|WD 7K 64M SATAIII WD1002FAEX - OEM
CD: BLU-RAY BURNER LG | WH10LS30 OEM - OEM
[Code]..
Basically, I just wish I had never bothered with KM5.5 and I want a do-over to go back to the beginning and put the LinHES 6.03 CD in and just do the installation. Since I can't do this, I'd like to at least be able to wipe everything I did and start fresh. Recall that I couldn't boot from CDROM even before I made the daft remove of LILO. The only time I successfully booted from CD was the very first time I turned on the machine to install KM5.5
I installing Fedora 12. I did ALL the same as in the installation guide, GRUB installed into MBR. And after installation and rebooting - nothing happens, after BIOS messages there is nothing - computer hangs. GRUB seems to be not installedI have 2 hard disks. At first I tried to install on the 2-nd drive(it is slave). Afterward I detach one disk and try with only one hard disk(it is master). Nothing changes - computer hangs.
View 3 Replies View RelatedI'm hoping someone knows about this one... I'm running the latest CentOS 5.4 with kernel 2.6.18-164.15.1.el5 (x86_64).When I boot the machine, it gets to the udev starting bit, hangs for like 5 minutes, then prints a message "Failed, will continue in the background." Then it boots OK after that.I tried booting again with the kernel option (from grub) "udevdebug", and what I saw when it tried again was a million messages saying it was waiting for "/sbin/pam_console_apply" to return, but I guess it wasn't returning... ;) Again, after 5 minutes, it gave up and finished booting.Now, this host is an LDAP client.
I figured that may have something to do with it as it is likely that pam_console_apply tries to make an LDAP lookup, which is wrong, because networking hasn't even started yet. If I disable LDAP (by removing ldap lookups in nsswitch.conf), I get no pam_console_apply errors from udev and it boots quickly. But that's a bummer, I need LDAP on this box, and I don't want my boot time to be 7-8 minutes. ;)Presumably before, when LDAP was enabled and it waited 5 minutes and then notified me that it will "continue in the background", that it was eventually successful after networking started. LDAP otherwise works fine on this box, just like all the other servers we have.This is new behavior, I've not seen it with CentOS 5.3 and below. Has anyone seen this? Any hints on what I can do to avoid it? It seems like a pam bug or something, but I don't know for sure.
I did a fresh install of Ubuntu 10.04 on a desktop. I then did the system updates and on the reboot the system now hangs at the splash screen before the login screen. I only get a blinking cursor on the text-based terminals. I don't see the grub menu, I assume because Ubuntu is the only OS on this machine. So I can't boot to single user or text-only mode.
View 3 Replies View RelatedI recently installed Fedora - it seems like a nice interface and I want to experience the system before deciding whether I want to keep using it over my ever reliable Crunchbang, which gives me absolutely no grief whatsoever. However, it is nice to use an attractive interface now and again.So, here's my problem - I opted to install the ATI drivers when alerted to the restricted ones by the pop-up. I took note of how to disable them again if there were problems with the display after reboot. There was a problem with the display (black screen) and I can't get the command entered at boot time because the only command line environment I have an option for is GRUB. Grib does not recognize any of the 'aticonfig --initial -f' command that ATI instructed me to use to get things back to normal. How do I do this? I prsume others have been there and will know how to guide me. - getting the graphical interface to display better graphics. I want the eye candy that desktop effects give. I am hoping Fedora won't let me down here because I could simply continue to use Ubuntu which only gives one problem with the window resize delay.
View 3 Replies View RelatedI've been having a problem on my AMD based machine, 4cpu, gigabyte ga-ma78gm-s2h Mobo, 8GB mem, two 2 terabyte Sata HDs.One thing I've found is that any kernel after 2.6.32-17 has a randomness at boot time whether the system will completely boot or not.
For instance just today I downloaded and installed 2.6.32-24
It fails to boot (I've tried cold boot, warm boot).Running its repair also fails to completely boot.My experience is that if I keep trying it "may" eventually boot but I believe there was some change after 2.6.32-17-generic that's causing the problem.Because as with 2.6.32.23... which also fails to complete bootup many times... eventually my guess is that 2.6.32.24 will also boot "sometimes".But why does 2.6.32.17 always boot for me? Something changed and its not my setup.
We have 2 applications set as S96 and S98 at rc3.d and rc5.d simultaneously. Both applications create a system V shared memory segment by calling shmget.If the system boot at runlevel 5, both applications can obtain their shared memory segment id correctly, i.e. 98305 and 131074 individually. While there is a root owned segment id 32768 takes first seat on the list. This is the id list:
root, 32768
S96_app, 98305
S98_app, 131074
[code]....
I started out with Kubuntu RC, then installed ubuntu-desktop and updated all the way to the current state of packages.Anyway, from the moment I installed the RC, from time to time the boot splash appears, the dots light up/turn off and then the booting hags. No key seems to work.I the do a hard reset and everything works just fine.As not to open another thread:- how can I see the Ubuntu splash screen? (currently I can see the Kubuntu one)- how can I turn the splash off and have it boot in text mode?
View 3 Replies View RelatedI'm running Debian Squeeze on a Dell Studio Laptop, and this morning my computer woke up and gnome was randomly frozen. I dismissed this as a random error and proceeded to hard-reboot the computer. It now will not boot at all. After multiple attempts, every time the boot process hangs on "Starting GNOME display manager gdm3." I even left it there for 2 hours while I was gone to see if it would get past the hang. It did not, and was still stopped at that same line when I got back. get my system back. I have a live CD available to perform maintenance if anyone has an idea of what's wrong.
View 7 Replies View RelatedMy system was working fine. I followed a thread online to try to get samba to share better, installed "winbind" and now I can't get passed "Checking System Files" on boot up.
Upon boot, "Checking System Files":
Starting Firestarter firewall .... fails.
Starting samba daemons _ .... Just hangs there forever
Is there a way to get back into my system so that I can uninstall winbind, firestarter, or samba if need be?
So my Ubuntu 9.10 install has been hanging on boot lately. At first I thought it was a problem with the 2.6.31-20 kernel, because that is the default boot option in GRUB2. It seemed things worked fine if I instead chose the 2.6.31-19 kernel, but I had that hang yesterday too.I also had 2.6.31-20 boot just fine yesterday. Once. Next time I tried it - system hang.
What I mean by "hang" is,I would see the GRUB OS selection screen (I have 2 versions of Windows and 2 versions of Ubuntu on this machine),select the first choice (Ubuntu with the 2.6.31-20 kernel),see the "pulsating white Ubuntu logo" briefly,then a bunch of scrolling text, then...blank screen.Then nothing.I let it sit for a few minutes to a few hours when it did this, but nothing further happened.Then yesterday, I decided to let it sit the whole time I was at work, approximately 9 hours.I came home to a screen with the white Ubuntu logo and the following error message:
Code:
One or more of the mounts listed in /etc/fstab cannot yet be mounted:
swap: waiting for UUID=3fba81a3-de14-4f56-9e7b-ace95d933a0e
/proc/bus/usb: waiting for none[code]....
So it looks like I have a disk partition that refuses to mount sometimes.Gparted for some reason wouldn't tell me the UUIDs of swap partitions.They also don't show up in /dev/disk/by-uuid. Using the bootinfo script, I found out that 3fba81a3-de14-4f56-9e7b-ace95d933a0e is the 4 GB swap partition associated with my Ubuntu 9.10 install.The disk that partition is on is rated "healthy" by Disk Utility, with only a few bad sectors. The HDD is about 7 years old, so it's in remarkably good shape.What could cause this swap partition to not mount during boot, and how do I fix it?
I've just installed Ubuntu 10.04 netbook remix on an acer Aspire One D250, specs below: Processor Name: Intel Atom N270
Processor Speed: 1.6 GHz
RAM: 1 GB
Graphics Card: Intel Graphics Media Accelerator 950
Storage Capacity: 160 GB
I had to resize the win partition, making a new partition for Ubuntu of about 15GB. I then installed the system. Everything went without problems. I was able to boot once, and verified that everything worked as intented.
However, after that, 90% of the times I reboot the bootup process hangs at a blank screen (with a blinking underscore), immediately after grub selection. If I select "recovery mode" in grub I can see the bootup messages, but the process hangs, all except one time, right after:
Code:
[2.304418] ata2: DUMMY
[2.304487] ata3: SATA max UDMA/133 abar m1024@0x58344000 port 0x58344200 irq28
[2.304584] ata4: DUMMY
and does nothing more. There are no error messages or hints to the source of the problem, to my eyes.I've noticed that sometimes even the loading screen of the live cd will hang indefinitely, leaving me no choice other than a hard-reboot.
The rare times that the system does boot normally, everything works normally. I've tried installing using both the ext4 and ext3 filesystems. I couldn't find anything like this on the forums. Am I doing something wrong? Do you need more details?
In the last few weeks I upgraded my Ubuntu from 8.04 to 8.10 to 9.04. No problems, everything went well. But yesterday I tried to upgrade from 9.04 to 9.10. Everything seemed to go OK until the upgrade was finished and I had to reboot. After the reboot, no Ubuntu anymore... I get GRUB, but when I continue to boot the latest kernel, I don't see any harddisk activity anymore after about 2 seconds.
Here on the forums I read that one should run the boot_info_script when having boot problems, so I already did. I booted the system with a 8.04 live USB stick. And here is the result of the boot_info_script:
[Code]...
I am having dual boot system(windows 7 and Fedora 12).When i switch on my system.It show the the timer 3 sec in order to get boot selection window(means window which asks that what to start fedora 12 or windows 7).I want to increase this time from 3 to 10 sec.
[URL]