My machine is running in Pentium(R) 4 CPU 1.7Ghz, Nvidia legacy Riva tnt/tnt2 and a 512mb ram. I have a Network adapter, Realtek RTL8139 Family PCI Fast Ethernet NIC. I have installed Ubuntu in my Window Xp, and used the ACPI workaround to install ubuntu on my PC. Now that I have installed Ubuntu, when I try to boot ubuntu, it always hang before it start to boot.
View 5 RepliesAll connections on my computer start loading and then hang: it happens when running apt-get update (a few repositories load successfully and then it hangs at a random one) and when loading web pages with the browser (it says "Connecting...", then "Waiting for....", sometimes some part of the page loads, and then it hangs).
This happens both with my wired and my wireless connection. It does not happen on Windows on the same computer.
Any idea on what it might be?
I upgraded my ubuntu 64 bit from 10.04 to 10.10 using the update manager on my Laptop ASUS, F80Series, 4Gb Ram, CPU Duo T8100. Ubuntu 10.10 could never boot: it always gets stuck. I tried the "recovery mode". The last two messages written, before getting stuck are:
[1.729408 ] NET: Registered Protocol Family 1
[1.730110] Registered Taskstat Version 1
Upgraded dual boot XP / Ubuntu 2.6.31-22 (still works) to 2.6.32-22, which hangs on boot. "2.6.32-22 recovery mode"(and "continue" dies at "Checking battery state". Ctrl Alt F3 gets a prompt and the login works.
The machine is a Thinkpad g40, which has worked on 9.10, except for wireless distance issues (the G40 has the Atheros AR5211, which seems to be a problem, at least per the forums, and my distance limits experience)
I get the same mount and chroot messages, followed by scrolling msgs, and then a blank screen on attempting to boot 2.6.32-22. And, as indicated, 2.6.31-22 boots and the apps I checked work fine. On the upgrade, there were several msgs about non supported apps and a grub question, which I (naively) answered as use the package version (and was somewhat surprised when dual boot still worked - but impressed and happy
I cloned my hard drive prior to the upgrade, so can revert to 9.10, but would like to run 10.04 LTS. Any suggestions. or should I wait for a while to upgrade?
I have 2 NVidia graphics cards, a GTX275 and a GT210. My system boots just fine in 32-bit Windows 7, so I know it isn't a hardware problem.Linux boots fine with either the GTX275 or the GT210 installed, but hangs after the file system check if both are installed. My motherboard has 3 pci-e slots, an x1, x4, and an x16. I've tried various configurations, all fail except 1 graphics card installed in either of these slots. I got my system to boot a couple of times with both cards installed in Xbuntu 9.10. Then this problem randomly happened.
System Specs:
Ubuntu 10.04 Beta, 2.6.32-16 Kernel
MSI N275GTX Twin-Frozr 896MB
MSI N210GT 512MB (got it for VDPAU on an HDTV )[code].....
I'm not inclined to believe the problem is here. I don't even get a bootsplash, let alone XServer to start. The system hangs after a flurry of HDD activity. Checked partition, and it's ok.
/var/log/boot.log
Code:
fsck from util-linux-ng 2.17.2
/sbin/fsck.xfs: XFS file system.
I'll say up front I'm still new to Ubuntu, so if I've missed anything obvious please forgive me. I chose to upgrade my 9.10 installation to 10.04 via the update manager. Especially since I was going to be gone for long periods of time, this seemed like a good idea.
Downloading went fine, but I had to leave for a two day trip once I clicked install. When I returned, I noticed the machine was still on the purple loading screen with four dots. When I shut it down and rebooted, it got to the same screen. Pressing escape to show the text behind the screen showed two fails and one oddity:
(1) Setting sensors limits "Rather than invoking init scirpts through /etc/init.d, use the service( utility, e.g. service S49console-setup start
Since the script you are attempting to invoke has been converted to an upstart job, you may also use the start( utility, e.g. start S49console-setup start: Unkown job: S49consile-setup"
(2) Starting VirtualBox kernel modules No suitable module for running kernels found
[Code]...
I was having this issue with my server when I tried upgrading (fresh install) to 10.04 from 9.04. But to test it out after going back to 9.04 I installed 10.04 server in a virtual machine and found the same issues. I was using the AMD64 version for everything. In the virtual machine I chose openssh and samba server in the initial configuration. After the install I ran a dist-upgrade and installed mdadm. I then created an fd partition on 3 virtual disks and created a RAID5 array using the following command:
Code: sudo mdadm --create --verbose /dev/md0 --level=5 --raid-devices=3 /dev/sd[b-d]1
This is the same command I ran on my physical RAID5 quite a while ago which has been working fine ever since. After running a --detail --scan >> mdadm.conf (and changing the metadata from 00.90 to 0.90) I rebooted and found that the array was running with only one drive which was marked as a spare. On the physical server I kept having this issue with one drive which would always be left out when I assembled the array and would work fine after resyncing until I rebooted. After I rebooted the array would show the remaining 6 drives (of 7) as spares.
I updated mdadm to 3.1.1 using a deb from debian experimental and the RAID was working fine afterward. But then the boot problems started again. As soon as I added /dev/md0 to the fstab the system would hang on boot displaying the following before hanging:
[Code]....
I have Fedora 13 installed on a new PC and have two types of intermittent boot hangups. What logs exist within Fedora 13 that may help me identify the cause or causes of these hangups? Todate, a reboot gets over the problems but I wish to get this sorted whilst the PC is still under warranty.
View 6 Replies View RelatedI'm migrating from XP to Ubunta 11.04. My PC: Toshiba Sat A30-921 L/top CPU: Pentium(R) 42.84GHz RAM: 512Mb Display Adapter: ATI Radeon 9000 IGP K/board: std 102/103 PS2 Pointing Device: Alps PCMCIA Adapter: ENE CB1410 Cardbus Controller Wireless Adapter: D-LINK GDWA 610
The installation went well from start to finish. Made it dual boot with XP. Hooked in the Eth cable & went online right away. Then enabled the W/less network adapter - all OK. Using 'Classic', so it's just normal screen after boot. Problem is random 'Freeze' or 'Hang Ups'. It's hung 12 - 14 times in 2 days! K/brd T/pad frozen out. Only recovery is to use master power switch & reboot. NEVER hung in XP in 7 years! (done other bad things though) Does Ubunta have switch like Cntrl + Alt + Delete in Win?
Tried many combinations but to no avail. I've tried quite a few Linux flavours (from Live CD) & they all displayed the same fault!! Before it hangs, I've been able to browse around Ubunta Apps: Places: System: Firefox: Internet: etc. Where do I start to track the problem down? I'm vaguely familiar (XP) with Terminal & cmd line processor but dont know any of the codes used.
I had to replace the motherboard, processor, memory on a machine because the old motherboard died. It worked fine under the old board but the new board (Gigabyte 880GA-UD3H) is causing Fedora 11 (and the Fedora 14 Live CD) to fail when initializing an Adaptec AHA-3940UW SCSI adapter.
I was able to display the boot messages and found that the first channel on the adapter is fine, but the second channel causes the boot to hang. The messages are:
aic7xxx 0000:05:04.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
scsi6 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
<Adaptec 3940 Ultra SCSI adapter>
aic7880: Ultra Wide Channel A, SCSI Id=7, 16/254 SCBs
aic7xxx 0000:05:05.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
Anyone ever see anything like this on bootup?
[url]
The display freezes/hangs, but the kernel is still kind of responsive because I can hit Ctrl-Alt-Del and after many seconds it reboots.
I can get it (Slackware 13.0) to boot this same kernel just fine from CD; it's only the normal bootup, after the install finishes, that this happens.
I enabled netconsole so I could see the messages, shown below, but there are no errors reported. The display corrupts and hangs at the "TCP cubic registered" message which appears to be unrelated to anything video-wise.
Code:
On boot I get
** Warning -- SELinux relabel is required. ***
*** Disabling security enforcement. ***
*** Relabeling could take a very long time, ***
*** depending on file system size. ***
On the next screen the boot hangs. There is a solution posted here: [URL] it states I booted my VM from a rescue CD ISO, mounted the root directory, and:
# cd /mnt/local
# rm -f .autorelabel
Once this is done you may want to consider upgrading your VM to more -current that has this fixed. I've booted using a knoppix CD, but I don't know how to mount the root directory to try the fix.
I've been having problems with start_udev on my machine post kernel 2.6.18-162 on my CentOS machine. A previous install would work on the old kernelut not the newer ones. I recently did a completely fresh install of CentOS 5.5o see if maybe there was a orruption in my install when it upgraded,t I still have the problem of udev hanging on startup.Using the rescue option on the disk, I've managed to track the problem down to the 50-udev.rules file. Through trial and error, I moved all the .rules files out of the rules.d directory, and added them back one at a time to see which one(s) caused the system to hang, and which ones it carried on booting as normal with. The only one that causes it to hang is the 50-udev.rules.
From what I can tell, this rules file is responsible for letting udev check various pieces of hardware. I think that it is failing whent runs modprobe on a pci device address.Only problem is I don't understand the rules file syntax, so I don't know if I can simply comment out or change a line in this file to skip the device that its looking for.Can anybody help me track down the specific device/line that is doing this?(I've kept the file out of the folder for now and my system appears to continue operating, but I get the occasional problem that for all I know could be due to udev not having a complete start up).
Fedora hanging during boot when new drives are connected.
I'm running an FC12 install on a 750gig Samsung SATA drive. BIOS is set for drives to be AHCI
I've got 3 other identical 750's, two of which have never been used (as in never been written to). None of the drives have any jumpers set on them, as I've read that SATA handles that. At some point, all 4 drives were connected, and I had formatted one of the drives and backed some data up to it. But a reboot left me with FC hanging on load and the solution was to unplug all 3 other drives. I left it alone for a month.
Troubleshooting this weekend, I found with just my active drive and one of the untouched drives connected, FC still hangs. What I mean by hanging is that the blue background appears with the un-filled 'F' logo which filles diagnally under normal conditions. Mine will not begin to fill, and keyboard commands are not recognized.
It almost resembles a master/slave problem, but I thought that was gotten rid of with SATA. I tried setting the BIOS to use IDE-compatibility mode and set the order of the drives but the problem was the same, though I did not try any jumper arrangements.
I've down loaded the live CD for SUSE 11.3 and, using isohybrid and dd, I put the contents onto a USB stick and made it bootable. All good so far.
I then installed SUSE on one of the partitions on my hard disk (Windows is also on the disk). I set 4GB for SWAP, 16 GB for ROOT and the rest ~270 for /HOME.
I set the bootloader to be installed in the MBR.
The installation completed with no problems indicated.
I was asked to reboot and did so, removing the usb stick so that 11.3 would boot.
The reboot failed! I was presented with a black screen and nothing else happened.
I tried again, selecting openSUSE 11.3 from the boot menu. - Again a black screen shortly after pressing enter.
I can boot in Failsafe mode and then login with text prompt. I can't boot into runlevel 3 (same problem - black screen)
Does anyone know whether this is a problem with network configuration or graphics?
I have a notebook with ATI Radeon Mobility HD 5650 graphics card and
ATHEROS ar8132 ethernet controller.
After a kernel update action, it seems that I'm unable to boot a system anymore. First off, after installing the kernel, and trying to shutdown to boot to the new kernel, the system replied with INIT: no more processes left in this runlevel. Kernel update was performed from to the following versions 2.6.18-128.el5.img -> 2.6.18-164.11.1.el5.img . The system is a VMWare virtual machine. When trying to reboot, the system passes GRUB, starts initializing and after loading the dm it stops for a few seconds at the message Waiting for new devices, show the following message:
Setting up new root fs no fstab.sys, mounting internal defaults. After this and a few other messages, it displays : INIT: version 2.85 booting INIT - No more processes left in this runlevel INIT: Id "x" respawning too fast : disabled for 5 minutes And then it just hangs. This is the output of my inittab:
[code]...
The system boots into failsafe, but still shows the errors mentioned.
New install of Fedora 12 64-bit from DVD on an Optiplex 740 (AMD) with 8GB memory I had to use the mem= option to get the install past the EDD probe, but it seemed to install successfully. Now on boot it goes all the way through the "filling icon" progress meter, then switches to a completely black screen with an X pointer cursor that responds to mouse movement, but nothing else happens. Ctrl-Alt-F{2-5} do not switch to a console login, so the system's inaccessible.
View 10 Replies View RelatedNow, all of a sudden, after I restarted after a system update, My dell desktop inspiron hangs on boot. The kernel is: 2.6.34.8-68.fc13.i686. Not only that, but the system won't boot for any of the remaining previous kernels.
View 6 Replies View Relatedi have just upgraded from f14 to f15 using preupgrade. i am now still waiting for the first boot to finish. the screen is stuck for more than an hour and the last line written was:
Started LSB: Start up the OpenSSH server daemon. and there is a blinking cursor.
I just finished installing CentOS 5.2 x86_64 on a Dell Dimension 3100 (Pentium 4 with 64-bit support). On the first boot, after completing the final config steps (firewall, SELinux, time server, etc), the boot hangs on "Starting xend:". I have completed a successful installation on another Dell machine (different processor), with the same installation options (I recorded all of the steps and followed them for the second installation).
My boot commands in grub are:
root (hd0,0)
kernel /xen.gz-2.6.18-128.el5
module /vmlinuz-2.6.18-128.el5xen ro root=LABEL=/1 rhgb quiet
module /initrd-2.6.18-128.el5xen.img
New to Linux and am wanting to install ubuntu 9.10 or 10.04 on a single separate 80gb drive. I have Windows installed on 2 80gb drives in Raid0 (nvidia controller) .I have installed 9.10 but Win7 will not load from the bootloader : gives me the error invalid signature. I've looked around and tried a few things to get it to load with no success.. is the Raid0 the issue?
If I try to install 10.04 it will hang and eventually errors out, I believe on the raid drive because it comes up with dev/mapper/nvidia_hhfbdccf1..
I installed F11 x86 from the DVD onto one of my machines using a total of 4 partitions:
1. /boot
2. /
3. /home
4. swap
I then created an image of the first 3 partitions with fsarchiver and restored it onto a second machine (with different hardware). Grub was loaded onto the second machine as well without a problem. The new cloned install will get past grub fine but the kernel hangs. After removing 'rhgb quiet' from the boot options, I can see that the last message outputted to the console is something about the PS/2 mouse - this doesn't make sense as the mouse is working perfectly fine.
Additionally, I can still reboot using ctrl-alt-delete so the kernel/CPU must still be responsive. I have tried troubleshooting the various pieces of hardware, so I'm guessing it's something with the clone. All the cloned filesystems appear to be fully intact; the partition UUID's are all the same. I've even tried changing the UUID's both in grub and /etc/fstab to hardcoded /dev/sdaX , but this does not fix anything.
Recently, I decided to migrate from SuSE 11.2 to 11.4. My 11.2 installation was working fine with two VLANs and several VMs. I went the route of installing 11.4 from scratch rather than upgrading 11.2.
The installation went smoothly. Afterwards, I ran Yast and changed eth0 to a bonding interface. Then I added two VLANs that used the bonding interface. When I restarted the computer, I saw the following on the console: "Waiting for mandatory devices vlan3005 __NSC__". Then after a 30 second countdown:
"vlan3005 no interface found". The solution to that problem was to add "ETHERDEVICE='eth0'" to /etc/sysconfig/network/ifcfg-eth0.3005". Upon restarting the computer, I could see that DHCP started this time but didn't get an IP address and continued in the background while the rest of the console messages scrolled by. At the point where X kicks in and I should have gotten a GUI login window, the screen goes dark. I cannot get to a console (CTRL-ALT-F1 or F2) or any other GUI login window (CTRL-ALT-F7 F8 or F9).
The computer was completely unresponsive. I could not ssh in to it from another host nor could I ping it. I let it sit for a few minutes but nothing ever appeared on the console. There were no blinking lights on the keyboard. I had to power the computer off. I turned off VLAN trunking on the switch port and the computer booted up fine, without network access, of course. I checked the logs but could find no clues as to what happened. I suspect a kernel problem. However, before I proceed further, I thought I would post my problem here and see if anyone has had a similar problem and perhaps a solution.
when my pc boots and shuts down my monitor goes into 'input out of range' mode for a bit between the gui and the text only phases of boot/shutdown.is there a way to fix this? or where to start troubleshooting?also, when it shuts down it hangs after coming back to the text only part
View 4 Replies View RelatedI installed a fresh copy of Slackware 13.1 (stable) on one of my media servers and I am experiencing something strange.... When I power up the machine, I see the kernel booting, no errors, until it gets to the point where it says:
And then randomly freeze there.... Well the machine is not totally frozen because the cursor still blinks. But it will never continue... Like I said, this happens on a random basis... After a reset, it might go through or simply stall at the same spot.
I remember after installing Slack 13.1, I rebooted the machine but forgot to remove the DVD from the player, so the install routine started up, and froze at the same point when it was loading the kernel for the setup programs...
My mobo is a MSI k9N platinum.
I never had this problem before.... (well I never used 13.1 before). Since I got this machine, I used slack 12.2 and slack 13-current with success.
This problem makes the machine extremely unreliable because I intent to use it as a backup and media server, so chances I will WOL the machine and use it remotely... if that happens.
I've installed Ubuntu on my new desktop alongside Windows 7 (each OS is on a separate drive), I seem to have run into a small problem. Let me start with what I did:
- Unplugged 1TB drive from the PSU, BIOS was not seeing my formatted (and thus empty) 500GB drive and I couldn't put it into the boot order at all with the 1TB turned on.
- Loaded up the boot CD and was able to install Ubuntu 10.1 on my 500GB drive.
- Did a bit of configuring, shut my PC off and plugged my 1TB (with Windows 7) drive back in. I tried to see if I could now see my Ubuntu drive in BIOS but nothing is there - just the Windows drive is in the list of available drives to boot from (along with DVD-ROM and USB).
This is where I've run into my problem. What I want is to have a nice GRUB boot menu at the start like any other dual-boot system but just have the two operating systems on separate drives altogether.I did it this way because I was having issues with the advanced partition menu on the boot CD so just went ahead and followed the KISS method by unplugging the Windows drive.
I was told by a friend that if I put my Ubuntu drive into the first position in my boot order and the Windows drive in the second, then I could boot into Ubuntu and run a GRUB update command (he told me to google it) and that would create the necessary GRUB that had the entries for Windows 7 and Ubuntu.Both operating systems are 64-bit, I imagine that might make a difference in whatever help you guys can offer me. I love the hell out of both OS's and want to be able to use them interchangeably.
I have a roughly 3-year old PC that I put together from parts (listed below) that has been running great with various flavors of Linux as the sole operating system. It is currently running Ubuntu 10.4. A couple of months ago, it started to have intermittent problems booting. The machine will hang before it gets to the Ubuntu "boot" screen with the dots that show progress as the machine boots. If I look at the power on messages from the BIOS, it fails at different points in the process - sometimes during the memory test, sometimes during the search for IDE drives. It fails about 2 out of every 5 attempts to boot. It sometimes takes 2-3 tries at booting before it actually works. Sometimes when it does boot, the Ethernet jack doesn't work and I see errors in syslog about there not being a carrier.
There are no syslog entries when the machine does not boot.The machine is plugged into a UPS. The UPS indicates that it is running at 13% of capacity at 123V/60Hz. I'm in the US.Once the machine boots normally, it will stay up without issues for days.I've checked the 4GB of RAM (I added 2GB to the original 2GB several months ago) using the memory testing application on the System Rescue CD and no errors were found.I've replaced the motherboard battery, which seemed to help for a few weeks, but then the problem returned.I've checked the hard drive for errors using the SMART diagnostics tool in System -> Administration -> Disk Utility and buy running fsck.The interior of the case is not very dusty and all the fans appear to be working.Are there things I can do to investigate and fix this issue other than starting to replace components - starting with the motherboard and the power supply?The parts of the machine:
CPU INTEL|C2D E6850 3G 65N 4M R - Retail (Qty=1, Price=$279.99)
CASE ANTEC|P180B BLACK RT - Retail (Qty=1, Price=$114.99)
MB GIGABYTE GA-P35-DS3L P35+ICH9 - Retail (Qty=1, Price=$111.99)
[code]....
I 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 RelatedRunning ubuntu 9.04 and have mpd installed and running good. I just cant seem to get it to start at boot. I want it to run on a headless system so don't want to have to login to start it. I have successfully done this on another system but I cannot remember how I did it and cant seem to find.
View 7 Replies View RelatedSo for the last few days gdm ans not started on boot up. tty7 is a blank screen and I'm automatically put in tty1. There I can log in and run gdm manually.
It has a started automatically a few times with out me doing any changes, but most of the times not. So far I haven't found out what the cause is but I've found some similar (the same?) problems:
[URL]
I'm running 10.04 64-bit if it matters.