CentOS 5 :: CentOS 5.4 Hangs Just Before Desktop Loads?
Apr 1, 2010
My Dell poweredge server running CentOS 5.4 and booting kernel-2.6.18-164.15.1.el5. All boot processes seem okay and the graphical screens for CentOS operate, but just before the desktop loads the screen goes blank and the arrow/cursor is being circled by small spheres. This remains indefinitely. While the arrow is being circled, here are the results of 'getinfo.sh device'
Quote:==================== BEGIN uname -rmi ====================
2.6.18-164.15.1.el5 i686 i386
==================== END uname -rmi ====================
i am trying to install centos 5.5 x86_64 as a guest OS in vmware server 2.0.2 using netinstall iso. Installation runs fine until the point, when it tries to install selinux-policy-targeted-2.4.6-279.el5.noarch, the whole virtual pc hangs at this.any ideas? i tried to google few things about this, but i have found nothing. this has happened 3 times in row, whole virtual pc always hangs at the same package. i dont have any other problems with vmware, gentoo runs and installs fine in it.i would prefer to do installation using netinstall.iso, it would take a lot of time to download all cds or whole dvd and all i require is a very basic set of packages.
I have encountered the same problem as indicated in this post: "udev hang after upgrade from 5.3 to 5.4"[URL]... I'm testing the upgrade path to centos 5.4 on several virtual machines prior to upgrading our production systems. I have upgraded centos 5.2 --> centos 5.4 and centos 5.3 to centos 5.4. In both cases udev hangs after the upgrade. The following message is displayed on the console: "Starting udev: Wait timeout. Will continue in the background [FAILED]"
I found another related post: "udev hangs on boot for a long time, suspect pam_console_apply"[URL]..So, I booted by VMs using the "udevdebug" option to grub and received the same error message - "udevd-event [###]: run_program: Waiting ## seconds for output of '/sbin/pam_console_apply /dev/..."
In my /etc/ldap.conf file "bind_policy hard" is commented out. I added a line "bind_policy soft" as described in the post and my VMs booted fine. NOTE: This problem is not encountered with a fresh install of CentOS 5.4 and the "bind_policy hard" option in the /etc/ldap.conf is commented out as in the upgraded systems. What is really causing this problem and how do I get it addressed? I have a couple hundred systems to update from various releases of CentOS 5 to the latest current version 5.4. It would be nice to get this bug squashed..
I used yum 5 days ago when I installed mplayer and some dependencies. And now I manage to use Yum and it is not working, I cant find out what is happening but yum loads the plugins and then freezes and is no reaction to ctrl-c or something to stop it so I am have to kill it dna finally got no result from any update processes. Also I manage to clean cache or even to run yum. I checked the logs and it writes nothing about this ,neither an error or something to make me understand whats happening. Tried to install with rpm but the same thing happens. It just freezes...
I am a novice with linux but I pick up stuff pretty quick so far I have been able to figure everything else out except this, I have read all the documentation on apache 2 and getting virtual hosts to work and it appears I have everything setup right but yet I still can't get it to work, I have googgled my brains out and I still can not figure out whats going on here is my setup.I have two websites that I am trying to get to load[URL]I have webmin installed and I'm using their utilities to setup virtualhost. heres how it looks in my http config:NameVirtualHost 188.8.131.52:80 ( I have tryed * in place of my external ip)
i find this is an issue which might be tiresome for everyone except for those experts. Esp. for the computers which are dual booting(both windows xp and centos installed in the same computer), that when we are in CentOS we need to switch onto windows immediately. and vice versa. i see this is possible only by shutting down the centos/windows and then restarting onto the other OS.
Can anyone tell me the the solution to work simultaneously both xp and centos without the need of shutting down and restarting There maybe or may not be the solution...but i find the pleasure to know if there is for example, remote desktop connection in windows xp, is there any solution, we can work on windows via centos or vice versa ( in the same machine),
I am trying to install CentOS 5.2 on an HP rp5700 desktop unit. These units were originally sold as a Point of Sales unit I believe, but HP also markets it as a high life cycle server for SMB market.I tried to load CentOS on this unit via CD (created from downloaded ISO of course). It presents the initial CentOS banner page and waits for the obligatory "enter" to continue. It begins the boot process up to discovering the PCI stuff and just locks up, no response. I have to power down to restart.Since this does not even get to the point of installing. I am at a loss what to do next. Has anyone had a similar issue with other PCs.The boot stops at the lineACPI: PCI Root Bridge [PCI0] (0000:00)
I'm currently in the last steps of migrating a CentOS mailserver to the x64 version.However, under the old 32 bit version, I was using XRDP to access the Centos box from my Windows boxes.However I can't seem to find the XRDP package in the standard repos so this is prompting me to look at possible alternatives (XRDP was incompatible with my windows 7 box anyway soI had to RDP to another server of ours running 2003 to RDP into the mailserver which was far from ideal).Basically, I'd like to be able to seamlessly access the Centos box with a standard RDP client.
I know VNC Server/Clients would be an option but RDP gives me the freedom of any windows box being able to access the server on the same adress/port without installing software on any windows box I encounter.Are there any viable alternatives to XRDP ?There's no "add-on" to VNC server that could enable it to accept RDP connections ?
I am running Centos VM on Windows Virtual PC. I have installed the GNOME desktop environment using yum groupinstall 'X Window System' 'GNOME Desktop Environment'and then when i did gave startx command, the desktop environment was not at all clear. As I am new to this, i am not sure how to use it too.
now i want to remove to due to upgrade the system using the latest centos system, but now i cant remove it, try to format my desktop also cannot. when im entering the bios its show GNU GRUB. im also need to install xp for my new study project..
I need to set a new centos on an "old" box : PIV 1.8 1.5Gb
The Centos will run on a 40 Gb PATA Hard Drive set as main drive, The Box runs a another SATA Drive with 2 different windows installations.
The installer first hanged on the loading ata_piix driver screen so I restarted with the irqpoll option to complete the wizard. But I'm now stopped on the last X screen : starting installation process please wait.
I have changed the hard drive, the DVD drive, the Centos DVD, tried with a 5.3 and 5.4 with no success.
I'm attempting to install CentOS 5.3 on my IBM IntelliStation Z Pro 6221/37G, powered by some extra equipments as nVidia NV44 GeForce 6200 video card, MV88SX6041 SATA II Controller, 2x1GB DRAM.
The problem: CentOS 5.3 DVD i386 didn't install, the screen becomes unreadable because of vertical bars just after anaconda start running. Choosing at boot time different "linux resolutions" did not help, as well as the "text mode" still useless because Logical Volumes need to be created/handled and the graphical interface is mandatory.
Same result booting CentOS 5.2 Live CD. This sounds really strange to me. I checked iso images against their md5sum and are ok. Centos 5.3 x86_64 does not boot yet :"Your CPU does not support long mode", evem they are 2 x Xeon 2.8GHz / 512KB
I have a strange issue. The only time I have trouble with yum is when awstats is included in an update. When it is, it always hangs on it when it gets to it. Yum will not complete. I have to cancel out... kill the yum pid and do it again. Tonight I did a yum-complete-transaction to do some unfinished actions - one included the removal of an old awstats - it hung on that.
I'm not sure what's going on with this install, but I started with a fresh install on a 250GB IDE disk, assigning /dev/hda1 to linux, and the rest (/dev/hda2) to swap. when it tries to boot.. I just get GRUB hang. Should I have installed a small FAT32 partition in the first sectors of the disk for the bootloader?
The bios in this machine is very old (Dell 410 precision) and Dell offers no updates, so I suspect this has something to do with how the old bios is trying to boot, but ?? not sure how to fix it. try lilo, or alternate bootloader???? Just looking for a fix to the boot problem. I would prefer to boot from the disk, booting from cd/floppy/pxe not so desirable.
I have a centos 5.5 server which hangs with yum update. i did a yum clean all. removed the rpm en /_.rd een did a rebuild. In the logs there are no errors. If there is another update except these to he works just fine. Disk space is enough free. Any ideas? i am runnung yum update as root . when i do a full report of yum i get this:
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.
I am trying to boot the CentOS live cd off of usb. I used unetbootin to put CentOS on my 8gb usb drive after downloading the DVD iso. During boot it loads the image and continues until it reaches this point.
>Linux agpgart interface v0.101 (c) Dave Jones >Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
After this it hangs and won't continue. I am using a Compaq evo n800w and the bios is just updated to the latest version.
I had a spare computer (Dell Optiplex GX270) which I had installed Centos 5 on and have been setting up asterisk (telephony) on it. My main computer has broken down and I need to load Windows XP back on to the Optiplex.
I put the Windows XP disk in the drive and directed the bios to boot from the cd. I get the message "Please wait while windows inspects your current hardware configuration" and then after about 10 seconds the screen goes blank (the cd also slows down and then stops) and then the systems seems to just hang.
If I take the cd out and boot from the hard drive Centos loads normally; therefore I'm assuming my problem is not a defective hard drive.
I've spent quite a bit of time searching online for a solution and although there seems to be several different situations where the above can occur, I'guessing that my ssues are related to either partions/mbr and or the bios/cmos. I'm really new to Linux and not knowledgable on partitions and cmos so I'm hoping someone could help me out here.
I've checked in the bios and could not find an option to restore the settings to factory defaults. Should I pull the csmos datterry out? Does this restore the bios settings to factory defaults?
With the 5.3 CDS I started an install got through to 98% of CD 3 but I was called away. Came back this morning and the box was on, but had frozen. Every time I reboot, cold boot, I come up with black screen. Vers 0.97 <grub> Minimal BASH-like line editing is supported. TAB etc. Is there a way I can get to CD 4 and continue the install, or am I back to the top again?
I recently installed CentOS 5.3 on a Dell PowerEdge 1800 server that used to have Microsoft Windows SBS 2003 on it. Everything seemed to be going fine until a few days ago. Here's the sum of it all...
- System seems to randomly hang, at which it becomes unavailable on the network (can't be pinged, monitor won't come back on, and you can't wake it up... have to reboot, the scroll lock and caps lock keys flash at the same time) - Received this error message...
Uhhuh. NMI received for unknown reason a0. You probably have a hardware problem with your RAM chips. Dazed and confused, but trying to continue.
...it doesn't crash at this point though. I ran memtest86 twice and did not experience any problems. I updated the BIOS to the newest version, which contained a few bug fixes, but still experienced the same problems
I am facing the following issue. My application runs perfectly in red hat linux(32bit, 64bit physical m/c and 32 bit vmWare m/c) and in one version of centOS(32bit physical m/c - don't remember the version:Sorry). However when I am running the same application in CentOS 5.4 (64bit version) I face the following issues -
a. the application gets stuck in the conditional wait even though the signal is sent after the application has moved to conditional wait. b. vsftpd service start fails from within the application even though the service starts and stops peroperly from console.
i have 5.4 installed on a super-micro server motherboard (has two gigabit ether ports). when i boot while its initializing everything it gets to the "starting eth0" and just stays there?
right before it boots up and says press any key for options i press a key and choose "centos (2.6.18-164.el5)" and it boots up fine but when i choose "centos (2,6,18-164.el5xen)" the problem occurs. and that is the default boot option.