OpenSUSE Install :: System Freezes After GRUB (Normal Or Failsafe) Boot Splash Screen
Apr 17, 2011
I noticed that after making my build in suse studio my system freezes immediately after GRUB ( Normal or Failsafe) boot splash screen. I also noticed that this happens only with the specified kernel below. I'm not sure when using Kernel 2.6.37, one had the same problem. I never used it. The original kernel 2.6.34 had no problems such as the one I have described. My systems has no further problems only that it takes several restarts to go past the "Freeze". Below is a list of my system specs:
Kernel-pae 184.108.40.206-4.1 from Kernel Stable.
GRUB 0.97-174.1 from openSUSE 11.4
xorg-x11-server 7.6_1.9.3-142.1 from X11:xorg 11.3 repo.
The GRUB from openSUSE 11.4 has been very stable and non-problematic. I will be buying an Intel core i5-2500K in a few months that's why I need the latest kernel and XOrg-X11-server. What could be causing the freezing?
I have 11.2 installed on my laptop but have a bit of an issue. When I boot it normally, it will not use my full screen, instead it only uses about a 5"x5" box in the center and displays there, but when i boot into failsafe, it uses the full screen.
I just installed OpenSUSE 11.4 on a completely blank machine, empty disks, etc. using a Network Install. The install appeared to run OK, but when it rebooted to do the configuration, it hung. I tried a manual reboot a couple of times, then booted in FailSafe mode - came up OK and ran through the auto-config. Now, it still boots up ok in FailSafe, but in normal mode I get the wallpaper on the screen, but it hangs there.
In summary, after updating from 11.2 through 11.3 to 11.4, normal boot works fine, failsafe mode hangs with two fatal errors - "Module atiixp not found" and "Module ide-pci-generic not found". i would like to fix this a) so I have a recovery position b) so I learn a little more. As 11.2 has gone out of support I decided to embark on the upgrades to 11.3 then 11.4 using the zypper method described on this site. I think failsafe boot worked ok with the original 11.2 install, but I never had to use it in anger, so I can't be 100% sure. I did not test failsafe in 11.3, just checked that the typical cd set of applications seemed ok before proceeding with the upgrade to 11.4.
I have an AMD processor, chip set and an ATI 3800 series graphics card, so I added the ATI repositories for 11.3 and 11.4 as i worked through the upgrades. At 11.4 there were some graphics glitches during normal and failsafe boot which were successfully fixed by adding "nomodeset" to both boot options. Normal boot works fine but failsafe boot hangs with the error messages above. Searching for failsafe boot errors is unhelpful since, in all cases I have checked, normal boot fails too. I did try removing "Xfailsafe" from the failsafe options which produced no change.
I am guessing that, in failsafe mode, the ATI drivers are not loaded into the kernel and the idea is to default to some safer drivers which, in my case, are not present for some reason. However, there seems to be little information on the origin or purposes of atiixp so I don't know how to go about fixing this. I have not really researched the generic pci driver issue, but I am guessing that this is a fall back when the expected atiixp is missing.
I am new to Linux. When I installed some applications and something through package manager,Now I get two added options in boot loader with identical names like failsafe and normal. what is that?multiple kernel?
Last week I successfully installed Ubuntu/Gnome onto a 3 year old Toshiba Vista laptop which worked mostly brilliantly. Today I am trying to install it onto a 4 year old Toshiba XP laptop, but am having problems.
Laptop specs: Intel 1.50GHz 488MB RAM 60GB HDD, partitioned by Ubuntu on install into 30GB/30GB, both partitions over 75% free space The laptop, though old, still functions in XP, and the main reason we're switching it to Linux is that it has issues managing wireless, plus it's fun to do so - learning experience and all. The other laptop has better specs - multiply everything by 2 but Windows was much less reliable as, after all, it is Vista, and switching to Linux there was a necessity.
The Ubuntu is 10.10 and it's the same live cd I used to install it onto the other laptop. It's installed alongside Windows XP and the install proceeded without issue. However when booting in normal mode it becomes unresponsive very quickly - sometimes as soon as the five pips on the loading screen become orange, the last time it lasted a whole 2 minutes before becoming unresponsive.
In failsafe graphics boot it runs without issue. The update manager tells me it's up to date, and I have installed Wine through SPM while typing this. It's behaving as I'd expect it to, with tiny lags on scrolling sometimes (perhaps related to being in failsafe graphics).
Is there some setting (graphics?) I should change to allow it to cope in normal mode? I'm aware 488MB RAM is slightly under the recommended amount, but it evidently can cope in failsafe so would appear to be enough to function?
I've got this really huge problem, which I really want to solve, because otherwise I might even switch back to ubuntu. So here we go. Yesterday, I had a problem with mounting nfts hard drives and solved (you guys solved it actually) it by adding ntfs to the /etc/filesystems file. (I doubt, that it has anything to with that, but it might, so I will just tell you everything I did) I added an ATI driver repository as well, which is probably the key to this problem.(or at least something with drivers) --> not sure if I installed anything
So however, the problem is now, that the screen tells me, the signal would die just before the log in screen appears. ("No signal" --> screen goes to standby --> can't wake it up again--> no opensuse for me) I'm now running the system in some sort of safe mode and it works, but I think, that it is using my on board graphic card and not the actual "radeon hd 5600", which provides much better quality. just looked it up, yes it is using the crappy one (on board) So here's the question: First of all why does this error occur(worked fine before) and secondly how can I fix it?
I have never been able to see the splash screen, something that I'd like. I have checked the options on the bootloader and it says "splash=silent" (that's disabled?). I found it confusing, because the ubuntu kernel boots with "splash" but when I try that option on OpenSuSE 11.2 it doesn't.Also when I shut down the laptop the screen goes crazy, only the two top cms shows "something" which are blinking and crazy green and white console words moving from one place to another so fast I can't even been able to read what it actually says.Either way, the laptop shuts down without any problem (?). I think is the normal shutdown process (without splash) but it's a bit perturbing. I've had had a couple of kind of "aesthetics" issues, but far from critical. My overall experience with OpenSuSE after 4 or 5 years being "debianized" have been very nice .
I played with the graphics in kde4 and seem to have losy my installation. i have tried the rescue system option, recover system options and in desperation (i was just about to reinstall) tried booting in failsafe mode, and it worked!
where do i go to find out what the problem is regarding the normal boot mode? i think my pc is starting to resent the continual use of the reset button!
i changed the boot up resolution in the boot up loader to 1366*768 (native res of my monitor) the boot option is still set to quiet splash however, instead of showing the progress bar, it would now always display the complete boot up log ( the list of starting services and such) i then manually changed the boot option from to 1024*768 at boot loader screen, and teh splash would show up, but then on next boot up if i stick with 1366*768, it doesnt work again
The system frequently freezes the screen. The mouse is still moveable but there is no reaction on any click. Keyboard does not work either (pushing Num-Lock does not toggle the Num-Lock light on the keyboard). However, Alt-Print-b works for a reboot. The only other way out is to turn of the computer.I had this effect some time ago where I thought it was a problem due to the NVIDIA graphics driver. Since then, I changed back to the standard VESA driver and thought the problem would be gone. Just a thought
I toggled through the log files in /var/log which had the file date/time of the crash but I could not find any hint.Which log files could I look as well to dig for the problem? Or any idea for such an effect?
I love opensuse as it's much snappier than MINT. But my system 11.3 is freezing while booting. I pressed ESC during splash and can see messages on the screen. The last message is ATA3 Exception EMASK. I have uploaded the /var/boot.msg here klogd 1.4.1, log source = ksys - Suse Freeze - CuQAd3dg - Pastebin. There are no other log files!
If I re-install Grub 2 from the live CD should that reset all the personalisations such as as splash screen and colours in the Grub splash to default? In my case they are not resetting. I would expect them to revert to the default black/white you get when initially installing the OS. the Grub timeout to be a lot less than its supposed to be? e.g. the default timeout setting of 5 seconds is more like 2 or 3 in reality, and when I set my prefered value to 2 seconds it results in being about 1/4 sec or so.
I've been running openSuse 11.2 for a while on my notebook.Today I turned it off at work and came home. When I tried to turn it on, it boots, shows a black screen written 'GRUB' and then NOTHING. It doesn't complete the boot process.
How do I do that ? Currently I have Kubuntu/Mint KDE installed as my main and only OS so the GRUB splash is disabled by default, how do I enable that (so I'm able to change the boot commands to go to single user mode).?
I started another thread about this to get help booting into openSUSE after Fedora rewrote my bootloader and deleted all other entries. I managed to fix it but I never did find out why the following commands caused my system to boot to the grub shell instead of the grub menu.
Code: grub root (hd0,3) setup (hd0) quit reboot
Can anyone explain to me why these commands caused my system to boot directly to a grub shell? It's as if there were no /boot/grub/menu.lst files for it to use, but after I got everything back to normal, the files were still there.
If it helps, this is how the drive was setup before and now, except Fedora was on /dev/sda4 and has since been deleted.
Code: Device Boot Start End Blocks Id System /dev/sda1 1 262 2104483+ 82 Linux swap / Solaris /dev/sda2 263 13316 104856255 83 Linux /dev/sda3 * 13317 14621 10482412+ 83 Linux
Running Suse 10.3, desktop box, Asus M2NPV-VM, Athlon 64 3800+, two HDD RAID 1 config. I was getting 'bad block' errors when logging into Root, ran a search for fsck to try and fix the problem. Found out not a good idea to run while the system is mounted, tried to boot from install DVD, could not boot to a command prompt, tried to open the Repair tool, got a 'repair failed' message. Rebooted again to the HDD, but now it hangs, tried to go to Failsafe mode, same thing.
Was able to boot to Recovery mode, but not sure where to go from here. I also noted when booting to the HDD in 'verbose' mode it was showing a lot of 'irrecoverable error's on the boot logs concerning the HDD.
A little while ago i bought a magazine with the openSUSE 11.1 distro on it but couldn't install it so i gave up. I am attempting to have another go. The problem is that the os will work fine when booted from CD in fail safe mode and can be installed from there but when out of fail safe mode the system begins to boot but freezes and will do nothing more.
LIVECD of 11.3 Gnome works fine in my old PC. I installed several times and each time system freezes/crashes during boot. I am linux newbie, so, I am trying to figure out my problems. In Livecd I noticed Hardware info list's my SATA disk as IDE. Driver Modules: "ata_piix"Attached to: #24 (IDE interface). Is it right? I have posted Hardware information output in 01: None 00.0: 10105 BIOS [Created at bios.186] - Suse 11.3 install problem My machine specs are: Intel DG31PR motherboard, Intel core2duo, 3 GB DDR2 Ram, 250 GB SATA harddisk
i had to reinstall suse coz i mounted my partition to /usr instead of /home. And now i installed some drivers for nvidia gt 320M and restarted the system but it goes blank after the splash screen. how do i get back to the default settings i had? i have a builtin camera in my Acer ASPIRE 4741G laptop. I installed amsn but it only shows a blank screen if i try my webcam.
Today I found out how to change theme in OpenSuse 11.3 64 bit. I'm running KDE 4.4. Naturally I went to KDE-Look.org and trawled it through for eye-candy. I got this HAL-9000 boot splash: HAL-9000 KDE-Look.org
Its a .gz file and uncompressed its called .xpm, I think its just an image, that I should put somewhere, but I don't know where. I tried the bootloader settings through yast, though it didn't tell me anything.
Secondly I got a screensaver, which I'm supposed to compile and install: KCometen4 KDE-Look.org
I tried following these instructions, as best as I could:
KCometen4 also comes with a simple configure script that should work for a generic local install. If it doesn't suit your needs, you will need to edit the cmake settings by hand.
Quick installation steps:
Cmake's equivalent to 'make distclean' is 'rm -rf build'.
If you do a local installation, you might not see KCometen4 in the Screen Saver Settings module. In that case, you will need to do one of two things.
First, you can set the $KDEDIRS environment variable in your X session startup script so it includes your local installation prefix:
Or second, you can set this for all users by adding your local installation prefix to /etc/kde4rc:
After that, you may need to manually refresh the system configuration cache by running 'kbuildsycoca4'. KCometen4 should now appear in Screen Saver Settings.
So I installed kdebase-workspace-devel but I couldn't find libqt-opengl-dev, but it didn't seem to be a problem, according to the console output:
It mentions some Q_WS_WIN, Q_WS_QWS and Q_WS_MAC, that it doesn't find. Could that be the problem.
I tried to see if the new screensaver got into the screensaver menu, it didn't.
I've run into a strange problem recently. My primary OS right now is Windows 7, and OpenSUSE is secondary. I had GRUB as the bootloader, and everything seemed fine, but I ran into one problem in Windows 7: one program refused to work correctly with ATI forced anti-aliasing on, but it is needed by others (or else edges look jagged).So I decided to install ATI Tray Tools. But it seems that Windows 7 is being evil and won't let install drivers that their creators didn't pay Microsoft for (thank goodness that's not the case in Linux). That means I had to use a driver overrider program, and that means that it had to change the Windows 7 BCD options. And that's where bootloaders kick in. It seems that Windows 7 is too lazy to check for its BCD on other than active partitions, so it doesn't allow the overrider to function.
So what I did was change GRUB to boot Windows 7 with makeactive flag. The problem now is - it won't deactivate! I no longer get GRUB's boot screen, it just boots to BCD directly. So my question is - is there a way to deactivate (or, rather, reactivate the /boot partition) after Windows 7 shuts down or restarts automatically? Obviously I don't want to use GPartEd each time I want to boot to Linux.
I rebooted it as a package (GRASS GIS) wouldn't open properly, the splash screeen appeared but it appears to freeze and does not get to the login screen. I have tried to boot in safe mode but pressing ESC at grub doesn't work and Ctrl+Alt+F1 also fails to invoke anything. I can connect remotely via ssh. I have tried to remove Gnome desktop so I can just go straight to commandline but it still brings up the splash screen, I removed desktop using sudo apt-get remove gnome-desktop it said it did.
So why did this happen, last night I logged in via ssh and x-win server started a screen and did some work, the x-win server I lost my internet connection so putty aborted, this morning I couldn't connect to the screen so I did screen -wipe then rebooted as another package kept exiting.
any help much appreciated, this has happened at a vital time during my PhD and I need ubuntu back asap! In the meanwhile I am working via ssh with a slow Internet connection so not ideal!
I have finally successfully triple-booted Snow Leopard, Windows XP, and Ubuntu 10 on an iMac but I have 1 problem: Whenever I am in Ubuntu and select "Restart," it goes to the splash screen and loads 2 of the dots and then freezes and hangs there forever. If I do "Shutdown," it works properly. Note: I am using rEFIt as the triple boot loader. GRUB installed on sda3 with Ubuntu.
I upgraded a week or so ago to 10.04, and everything was working fine. Then suddenly a few days ago the computer froze at the splash screen on startup. Thinking it was just some sort of neurotic, temporary issue, I restart again, but no luck -- same problem.
In terms of what I changed before the problem happened, I don't recall changing any system settings. On possibility is my changing things to skip the login screen and go strait to my account, but I believe I had done that a few shutdown/restarts before.