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.
View 1 RepliesRunning 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.
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'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?
When I turn on my desktop and log in to Lucid Lynx, I can only use it with "Failsafe GNOME" turned on. If the Normal GNOME is on instead, it literally freezes every single time, within about 4secs-1 minute of use. is there a way I can boot up in failsafe GNOME without clicking it every time?
View 4 Replies View Relatedmy when i boot my ubuntu 8.10 i get only xterm failsafe ,however failsafe Gnome does open , i have tried several solutions from the web such as deleting .profile file and some other solutions but none works.here's my .xsession-errors file
Code:
/etc/gdm/Xsessin: beginning session setup...
/etc/gdm/Xsession: Executing default failed ,will try to run x-terminal-emulator
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!
Older machine here that I upgraded to 10.04 after a clean install of 9.10 some months ago. When booting into GNOME, the desktop image flashes on the screen and the second the bars on top and bottom try to appear the system boots out of the desktop and returns to the log on screen. I assume this is a crash of Xserver, but just guessing. Per another page I ran: lspci | grep VGAand returned:
01:00.0 VGA compatible controller: VIA Technologies, Inc. KM400/KN400/P4M800 [S3 UniChrome] (rev 01)
I know - old machine Typing this from failsafe mode, would be great to hear from someone as to what I can do to get this working in normal mode again.
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)
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)
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 a problem with my computer since it's behaving good in failsafe but is bad in normal mode for example I get no wireless in normal mode.
View 1 Replies View RelatedI 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.
View 7 Replies View RelatedAfter using my computer a few days ago, I tried to turn it on again yesterday, and I was unable to boot. After some Googling (on my mobile) and a few Grub bash commands, I was able to boot, but now I cannot log in. Neither normal Gnome nor XTerm work, and Failsafe is all that I can log into. Above that, every time I log in, I get the following message:
Quote: Error activating XKB configuration. It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap utilities)
- X server with incompatible libxkbfile implementation
X server version data: The X.Org Foundation 10604000
If you report this situation as a bug, please include:
- The result of xprop -root | grep XKB
- The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
[Code]....
This happen on a samsung NC10 (graphic chip: Intel 945GME). When I boot linux + gnome3 and no external screen is attached to my laptop, then, gnome 3 boots with the gnome shell (gnome 3 shell). If, at this stage (when logged in), I plug an external monitor to the laptop (and configure it using the monitor config tool), then I can run gnome 3 shell on my external monitor as well... BUT:
If I log in when the external screen is already plugged in, then gnome boots in fallback mode... with other words: Gnome3 seems to be able to run the graphic+screen with gnome 3, but the "fallback" detection seems not to beleive so...
Recently I changes settings on Ubuntu Desktop and I choose gnome failsafe login, hence everything loads nice except when the user accounts is load it only appears the background and the terminal. Is there anyway to have the desktop back the way it was with the complete gui interface?
View 1 Replies View Relatedwhen i called up the login screen to change to automatic login, i apparently changed my preference from GNOME to Failsafe GNOME (knew i made an extra click but didn't know where, dumb, i know). with Failsafe the network manager applet and all the other default prefs disappeared. the worst is that i can't connect to wireless without the nm.
these are preferences, right? you should be able to go right back anytime and change them but now when i go settings > admin > login the window is locked. only the unlock button is lit up and that won't budge. so as the thread title says, how do i unlock login preference window and/or disable Failsafe Gnome?
I recently installed Wheezy from a DVD (that was written almost a year and half ago) to my desktop. The DVD install was a minimal one, so after installation I updated the system and installed gnome. But after reboot, my gnome always falls back to gnome-classic.
Code: Select all$ gnome-shell --version
GNOME Shell 3.4.2
$ cat /etc/issue
Debian GNU/Linux 7
l
May be some firmware is missing, so I installed firmware-linux, firmware-linux-free, firmware-linux-nonfree, firmware-realtek, firmware-atheros (last two following a boot time warning). That did not solve the problem, so I just did Code: Select all$ sudo apt-get install firmware-* That also did not solve the problem.
Then I looked into my .xsession-errors file:
Code: Select all/etc/gdm3/Xsession: Beginning session setup...
localuser:somesh being added to access control list
openConnection: connect: No such file or directory
cannot connect to brltty at :0
gnome-session-is-accelerated: No hardware 3D support.
[code]...
I also installed "libgl1-mesa-dri-experimental" from another post I found in this forum.But gnome still falls back to gnome-classic.My hardware is: Core i5-4440, Intel onboard graphics, realtek audio and network.
I'm using gnome shell 3.4.2.1 from the stable debian repository. 2 problems with the gnome-tweak-tool:
1) The extensions list is empty, even when the gnome-shell-extensions package is installed
2) in the non-classic mode only, setting made in the tool have no effect: e.g. Shell->Show date in clock does not toggle the date in the clock.
[URL]
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 installed on my workstation the opensuse 11.2! After the reboot when I enter the username/password, nothing occurs... On the other hand, it's running well with the failsave, why??
Code:
title openSUSE 11.2 - 2.6.31.5-0.1
root (hd0,1)
kernel /boot/vmlinuz-2.6-etc... root=/dev/disk/by-id/ata-etc...
resume=/dev/disk/by-id/ata-etc....
splash=silent quiet showopts vga=0x317
initrd /boot/initrd-2.6.31.5-0.1-default
[Code]...
What is the Failsafe Session Type that you can select from the KDM login screen supposed to do ? With Squeeze RC1, if I attempt to log in to a failsafe session, I am returned to the KDM login screen. This does not seem very failsafe to me but then I am not a desktop expert. With Lenny (5.0.7), I get a single console window, which, I guess, at least gives one a chance of fixing whatever may be stopping the normal KDE session from starting.
View 8 Replies View RelatedI have Ubuntu 10.04 it works perfectly fine, until I boot with no screen. Then I get the "low graphics mode" and I cant remote desktop into it...
View 1 Replies View RelatedIn 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 have a dual boot xp -ubuntu - AGP ati 2600 series radeon. Intel 8300 dell. The message comes up after login "ubuntu is running in low-graphics mode". I hit ok and I get 5 choices and none of them work.
1) run ubuntu in low-graphics mode.
2) reconfigure graphics.
3) troubleshoot the error.
4) exit to console login.
5) restart X.
I have installed Ubuntu 9.10 on my Dell GX240. I have severe difficulty logging in. If I try to login on GNOME or GNOME fail safe mode , I just cant get in . I keep getting the login screen again. I am able to go into terminal mode. Sometimes I have to try upto 100 times to login in GNOME or failsafe mode. Once I am in everything is fine. Is there a way to do some troublshooting? Also transfer to USB sticks is very slow - sometimes as slow as 1MB per min. Is this normal with Ubuntu?
View 3 Replies View RelatedI tried to make Compiz work using the experimental 3D support of the free Nvidia driver, because I am suffering from a bug in the proprietary driver (click here for launchpad entry). The free driver I mean is the one that shows up as "Experimental 3D support for NVIDIA cards" in the "Additional Drivers" manager (note: for some reason, this option will only present itself when no proprietary driver is currently active).
Now the strange thing is: the driver does not provide 3d support, and behaves generally awful (lots of glitches and so on) when I boot my system normally. But when instead I boot from the grub menu into recovery mode, then select "failsafe graphics", and then select "restart X", the whole thing works perfectly! So now I am running the experimental 3d driver, I have compositing working, 3d animations on docky. Somehow, the failsafe boot sequence does something right that my normal boot sequence does not. When I reboot in normal mode, everything is screwed up again.
I have no idea what statistics about my system I should include here, because I really have no idea what could possibly be wrong. I am running 32bits Natty in Classic mode, on an Ahtlon Dual Core 4850e machine, with a GeForce 6150 LE graphics card. These are the normal and recovery entries in my grub.cfg:
Code:
menuentry 'Ubuntu, with Linux 2.6.38-8-generic-pae' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
[code]....
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?
View 3 Replies View RelatedI 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 2.6.38.2-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?
just upgraded to gnome 3.0.1 but it started in fallback mode ...! and i really don't know where to go next Here is my kernel version
Code: OpenSuSe 11.4 Linux linux-6rb4.site 2.6.37.6-0.5-default #1 SMP 2011-04-25 21:48:33 +0200 i686 i686 i386 GNU/Linux Here is hardware
System : LapTop HP G62
Processor : Intel® Coreâ„¢ i3 CPU M 350 @ 2.27GHz Ă— 4
Graphic : Intel® Ironlake Mobile GEM 20100330 DEVELOPMENT x86/MMX/SSE2