OpenSUSE Install :: Cannot Boot To Failsafe Mode In Suse 10.3
Oct 27, 2010
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.
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 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!
So after research decided to go with OpenSuse 11.4 distro.
Installation had no problems but when I try to boot into the normal mode it just gets stuck on the screen that has a loading bar. The loading bar never makes any progress. After having waited for 15min I shut down and booted from failsafe mode. That worked fine twice only and then it prompts me in the command screen for login and password. After I input both it tells me to enjoy but Im still stuck at prompt screen, never loads GUI.
Im now booting windows on my acer Aspire 5633wlmi. It has a Intel Core 2 duo t5500 processor which I understand is 64 bit. So the version of Linux I downloaded was the 64 bit one.
I have just upgraded from 11.2 to 11.3 using zypper dup (with all the necessary pre steps). After upgrading X does not start with normal boot, only starts with failsafe mode selected. Otherwise the system boots and works in normal mode, only X doesn't start. I have tried to remove and reinstall the radeon driver, but no success. Tried Xorg -configure, with no success.I post my former (11.2) and actual xorg.conf files. Could you help in getting things work normally. If only possible I would like to avoid making a clean install.
last week I did an update and it may or may not be tied to the fact that now I can only login to Failsafe Gnome mode. I'm running Ubuntu 9.10 - Karmic Koala. I've had Ubuntu for a year but I'm not that familiar with it.
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.
This started a few days ago and I checked back through recently installed packages and nothing looks related. If I boot into ubuntu normally, plymouth looks a mess, but then things boot fine but while the mouse is showing and ubuntu goes about with connecting to networks and so on, but it doesn't register the and input from the mouse or keyboard. It will sleep if you press the power button, but its no more responsive after waking up.
If I boot into recovery mode, and use the failsafe graphics option then everything runs fine. Apart from 3D graphics being pretty slow, which I can kind of understand. I get the same behaviour on all of the last three kernels. I'm running the latest maverick on an HP 6715b. i386 version although the processor is 64 bit compatible. 2Gb RAM.
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:
openSUSE 11.3 Kernel-pae 18.104.22.168-4.1 from Kernel Stable. GRUB 0.97-174.1 from openSUSE 11.4 Upstart 0.6.5-33.1 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 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 just installed Ubuntu 10.10 on a machine with a dodgey graphics card. This machine will break on normal graphics mode but run fine in failsafe graphics mode. I need this machine to be able to be controlled remotely and this is where the problem comes in.
If this machine is being controlled remotely, it may need to be rebooted remotely. Rebooting it into failsafe mode at the moment consists of two prompts: one to put it into failsafe, and the other to "keep it for one session". Does anyone know how to reconfigure Grub or whatever else so it will automatically go into Failsafe Graphics mode without any user interaction? (BTW, where it asked me to "keep for one session" or "reconfigure now", I clicked reconfigure and it didn't do anything. So I need to do it manually)
I just installed 11.3 RC1, but I can only run in failsafe mode. Installation went fine and I'm not having any problems except that when my computer gets ready to launch my login screen it just display garbled graphics. I have tried multiple resolutions and the x11failsafe option, all with a no-go. I did see this error message pop up at the time of garbled graphics on one login: [GPU LOCKUP, switching to software fbcom]
new bought cheap PC, with pleasure installed 11.3 and then I tried to install Ubuntu 10.04... on grub startmenu see I now only SuSE Failsafe. I want my trusted SuSE ro seen, can not find an handy solution on forums.
I've installed my the ATI drivers as per this link: SDB:ATI drivers - openSUSEHowever when trying to reboot on normal mode the OS opens only tty1 (terminal 1?), you know, the one with green theme background. Fortunately I was able to reboot and log with failsafe. Any ideas why this is happening and how I can fix it?
Whatever settings I use in the power manager, (Ubuntu default Gnome Power Manager) nothing appears to change. Screen brightness does not change when moving the slider, but is reduced after 5 or 10 minutes (haven't timed it. Probably whatever is default) of inactivity, even though the reduce screen brightness checkbox is unchecked. The latter is pretty annoying when watching online TV streams, especially since the video also exits full screen mode when the screen brightness is reduced.
The weird thing is, as the title implies, that when booting in recovery mode with FailsafeX the power settings seems to work. At least the screen brightness varies as the slider is moved I should probably mention that it is possible even in normal mode to adjust the screen brightness by using the buttons for adjusting screen brightness on my laptop (Fn + arrow up/down)
I'm trying to dual-boot Windows 7 with openSuSE 11.4, i was told that i should install SuSE after windows 7 as it takes care of the boot-loader and automatically detects my windows installation and not vice-versa, But that is not true in my case.
So i had 2 hard disks one had windows 7 installed and one was empty so i decided that i should get openSuSE 11.4 on the empty hard disk and dual-boot it with windows 7 (that i already had installed). Downloaded the DVD, put it on a USB and installed SuSE on the other hard disk normally, it detected my windows installation on my main hard disk but i didn't touch that, only formatted my other hard disk to ext4
After the installation it booted automatically into SuSE, but now every time on a fresh restart the system boots automatically into windows. Methods i have already tried to resolve this and it didn't work:
1. Booted from the DVD and selected an "Upgrade" not "New Installation" so i could boot again into my SuSE installation which did work, checked my "Boot Loader" options from YaST and checked the "Boot from MBR" option instead of the "Boot from root partition" option, That Did NOT work.
2. Used the same method to Boot into SuSE with the "Upgrade" Option opened up the terminal and tried to install grub manually again using this link
Just a little disappointed. I downloaded the 11.4 Gnome by about midnight, checked the CD for integrity,and started the Live CD, and it worked quite well. Installed it, but troubles started. OpenSuse 11.4 won't boot up in the normal mode, but would boot up in the safe mode only. I am now writing from the safe mode, but would like to boot up normally. It get stuck after the first verbose page. And not a move from there. The laptop is Lenovo T400, Core2Duo with 4GB RAM, screen 1440x900. No problem with any other distros up to now.
my linux pc is connected to a lcd monitor with native resolution 1280x1024.The font at the textconsoles is too small for me.
I changed the entry "vga=..."in the file /boot/grub/menu.lst to "vga=0x0314".During the first few seconds the screen-resolution matches the setting of the vga-mode, but after then the vga-mode automatically switches to 1280x1024 (only at the textconsoles).The x-server is configured to 800x600 which is the resolution I want.I also tried vga=normal and vga=788. In older suse-version 10 and lower never had this problem.
I started having this issue two days after installing openSUSE. When I try to boot it on battery (that is, without a energy plug) the laptop just turn off right at the beginning. I have other OS's installed and they are working properly and booting when in battery mode. I haven't got a clue of what I need to check to fix this, can anyone help me out? My laptop is a vostro V13.
I installed 11.2/Gnome on Compac Presario laptop - 1.6 gHz AMD processor, 1.25 GB ram and ATI graphics. 74 GB hard drive newly partitioned with Win XP on 55 GB and Suse 11.2 on remainder. Had to fix grub and it now boots into Win ok. On openSUSE boot it stays in console and I can't get a GUI. After login/password I get "Error accessing systemtap module preloadtrace: operation not permitted" I get a GUI and access to yast, system and other stuff if I boot in Failsafe mode. I did a search here but didn't come up with anything - TIA - d
ps Above in boot sequence it says "gdm: WARNING: Gdm display: display lasted 0.073955 seconds" This was repeated twice with different values then "WARNING: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors"
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.
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 am big fan of SUSE.. waited like anything for 11.4 release .. but i am in trouble now .. installed 11.4 on Acer 4820TG (switchabe graphics with ATI mobility radeon 5650).. after booting it fails with the attached error while works fine in failsafe mode. Let me know if u need any of the details i am available online for some 5 hours.
Gnome is falling apart and I've had a lot of nagging problems that I couldn't overcome.I'm thinking of wiping the OpenSuse partitions and doing a clean install without wiping the windows partition.I initially setup using the 11.0/XP dual boot FAQ in the How To forum.I have my Home directory backed up on an external HD. Might try KDE next go-round or KDE & Gnome as separate users. I have 11.2 i586 installation DVD.
I've installed fglrx drivers with 1click install on openSuse11.3. If I try to boot in "normal mode" I end up in black screen. However if I boot in safe mode, then login and startx, everything works ok
Code: ~> fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: ATI Technologies Inc. OpenGL renderer string: ATI Mobility Radeon HD 4300 Series OpenGL version string: 3.3.10151 Compatibility Profile Context Shows fglrx works OK, as well as overall performance is pretty good.
I've done Code: aticonfig --initial radeon drivers is also blacklisted but running (if it means something) Code: # depmod -a; lsmod | grep radeon radeon 868858 0 ttm 64561 1 radeon drm_kms_helper 32944 1 radeon drm 221516 3 radeon,ttm,drm_kms_helper i2c_algo_bit 6728 1 radeon
I had mounted the pen drive then dismounted. I found out that by putting the pendrive into my sat receiver recorder with Ext3 mad the machine go crazy and I have had to sort that out before this! To say my wife was mad as hell is an understatement, but this was what I was told to do on AVForum.But now this leaves me in a predicament. I have no OpenSues booting. It goes through all the loading and then it asks me for the password with all the script showing and not the desktop. It says repair boot after this. Is there a simple way to resolve it? I think it was looking for the pendrive. Well I had to reformat that back to FAT.
I have just downloaded a mirror copy of SUse 11.2 and formatted my hard drive, so i can install the linux OP. But it seems like that it is not readable or better to say the boot from CD-rom does not work! Am i on the right track here? How do i go by installing a Linux on a fresh hard drive?
i am not able to start gnome desktop though most gnome applications work in icewm and xfce4 newly installed. the system config edit button i cannot understand what keys where to edit? how do we reinstall gnome fully? by the way my system is
intel 845 mother board[gigabyte] LG Studioworks 520Si monitor. 250 80 Gb disks 512mb mem LG dvd writer
I burned the live version of OpenSUSE 11.3 (Gnome, 32bit) to a CD to test the compatibility of an HP Pavilion p6510f. Although Xubuntu 10.4 booted up fine, OpenSUSE did not. A message about RAID would appear (too briefly to read) and then the computer would reboot.I checked in the BIOS and found that the SATA drive has 3 modes: IDE, RAID and AHCI. The hard drive was set to RAID.
When I changed the hard drive mode to IDE, I was able to run the OpenSUSE live CD; but the change ruined my Windows installation. Windows doesn't boot under IDE or RAID mode. (I have reset the mode to RAID and am restoring the Windows installation.) Is there an option/argument that I can pass to the kernel so that OpenSUSE will work under RAID mode? (Since Xubuntu 10.4 was able to do it, I'm assuming OpenSUSE should be able to.)
Everything went wrong no sound, no scsi to scanner, printers, and kde only using failsafe. So, did a new install and still probskde stops half way through saying it there is no file in /lib/modules/2.6.31-5-0.1-desktop
Fixed prob by creating a copy of 2.6.31-8.0-desktop kde only starts with x11failsafe On failsafe boot (from GRUB) load of messages daying can not find disks then mess Doing Fastboot At least I've got sound though printer still a prob Any ideas how to fix the kde start up?
config ASUS M4A78-E, AMD xenon III 550, 4GB mem SUSE 11.2 standard KDE, network install
pm-hibernate and pm-suspend only work the first time after booting into runlevel 5. This behavior is reproducable. pm-hibernate starts out correctly but then hangs the system bevore it gets to save the image from memory to disk. The computer locks up and does not power down.
pm-suspend: on wake up there is no signal on the screen (pm-suspend called from X environment or text terminal shows same result). I spent some time reading information on s2ram s2disk and added the follwing options:
S2RAM_OPTS="-f" in /etc/pm/config.d/00meine.config (display adapter is GForce4 nvidia with the closed source nvidia driver for accel) splash = n in /etc/suspend.conf - to get some more information during the suspend / hibernate.
Any ideas to get pm-hibernate / pm-suspend to work more than one time after boot??? Hibernate would be a great start for daily work and for energy saving.
horstausdemwald PS: In runlevel 3 pm-hibernate works various times from a text terminal. Under the same condition pm-suspend leads to a scrambled text terminal after resuming (some help on this: using vga=normal in Grub). The computer continues to work - though without visual aid - when the text terminal is scarambled. For example Runlevel 5 can be called blindly from the text terminal.
Now after my experiments with Open Indiana on another partition, I have rewrite my Suse Grub, that was as in / suse partition as in MBR. Suse partition is intact as well as files in /boot/grub, but in MBR is boot loader of Open Indiana as primary. How can I get back Suse boot loader. On Installation media under Rescue system I didn't find any option for re-installation of boot loader.
P. S. Now I can run Suse completely in Gui without any problem, because, I made some changes, in Open Indiana boot loader, but I would like return a Suse Grub.
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.
I have SUSE 11.3 on an Acer Aspire 3620 (laptop). When it boots up, it gets stuck and doesn't complete the process. Can't use safe boot either because I can't get past the login- when I type the password, no keystrokes appear, regardless of the key I strike. Here's how I got into this situation and a little more description of the problem. After my laptop got some nasty bugs that damaged Windows XP so badly that I couldn't use the rescue disk (that I so obediently made per instructions), I bought several linux flavors on Live CD/DVD and decided to go with SUSE. I had been using the Live DVD for about a month and everything worked well so I installed it last weekend (SUSE only -no dual operating system). Everything went well for a couple of days and I even used Yast to get Adobe Flash. Then I plugged in my MP3 Player to recharge it and quirky things started happening.
Once, the computer went in to standby and I couldn't get to the login screen - I started pushing all the keys and something worked. That evening I closed the laptop (so it should have gone to suspend) with the MP3 player attached still, and pulled it out, probably as the computer was going through the motions or shortly thereafter. (My player and usb stick suffer no ill consequences if not ejected properly.) Since then I have not been able to boot up. I powered down several times and tried. It seems to start normally with the green screen and little reptile appearing as the monitoring bar grows. Then it goes black, except the cursor's spinning wheel indicating activity. Then comes back to the green screen, with the bar still increasing and nearly making it to completion. Then the black screen and cursor-- forever. Eventually I can hear that the harddrive is no longer spinning.
Also, when the black screen appears, there is an error message that says that the configuration settings for Gnome Power Manager were not installed properly, which I highly doubt since I had no trouble in the installation, but maybe that is pointing the right direction to the problem. Anyway, now I am back to Live DVD, so that I can surf for the answer to this problem. Least that works! Before installing, when I was using SUSE as a live DVD, it sometimes was a little quirky when I inserted the MP3 Player and USB Stick- sometimes wouldn't recognize them, sometimes would, sometimes wouldn't/couldn't unmount. Firefox also would start crashing after alot of use, but I could reboot and things were fine, so I thought this might just be due to the fact that it was Live and not Installed.
I installed it with the default, KDE. I read another post somewhere with a similar problem in which the author says KDE is very bad with inserted media but I wouldn't know if that's true or not. This is the first time I've used linux, apart from a little bit of experience at work. It really has it's ups and downs, when it was working, it was so exciting, when I got hung up so soon, disappointing. The only thing I can think of to do now is reinstall and tip-toe around being extra careful about the quirks when connecting devices. Not very practical though. Thanks for listening to this long story. Will be trying to get it fixed in the evenings after work EST.
PS IF you can bear to read another line. The live DVD I bought was rather badly scratched and scuffed in my opinion. Although there were no installation errors that I could see, would this have had an unknown immeasurable effect that could account for weird behavior?
I've installed FreeBSD (sdc1) and DesktopBSD (sdc4). When I try to boot DesktopBSD it boots FreeBSD.here is menu.lst
###Don't change this comment - YaST2 identifier: Original name: other### title FreeBSD 8.1 rootnoverify (hd2,0) chainloader +1 ###Don't change this comment - YaST2 identifier: Original name: other### title DesktopBSD-1.7-amd64
I guess the chainloader boots 1st ufs slice and ignores the other. I've installed GrUB in FreeBSD and when I try to boot with different menu 'configfile /boot/grub/menu.lst' it returns error 17. This is probably due to inability reading ufs.
I was a window vista user. I wanted to install suse into my laptop so i shirk a free partition (around 70-80GB free partition) to install suse.After I had installed suse, I found out that I fail to boot my window vista operation system. It had gave me several choices...
I've been running a Suse 11.2 and ubuntu 9.04 on an internal HDD in separate partitions for about 6 months on an Acer aspire with 756 meg ram. I installed Suse first then Ubuntu as I couldn't work out how to alter the partitions and keep Ubuntu when installing Suse first. Yesterday when I tried to boot Suse I got the message Error 15 no file found. I went into boot edit for and Suse this is what I found.
Id like to be able to fix this so I don't lose either OS as I use them both for different things and until I learn all about Suse and can make a live cd of OS, I really love it but am not prepared to dump ubuntu. I've put a lot of time into both and don't want to start again. I've got a Suse studio account and really want to create my own dedicated Video/audio KDE Suse. I'm new to dealing with grub and the terminal other than cut and paste, so may be a bit dim until I can understand them.