Can only boot in recovery mode

Hello all,

I’m fairly new to linux, and very new to opensuse, but I cannot figure out why I cannot boot in the normal mode. What is different about recovery mode? When I try to boot in the normal mode the screen goes black and nothing happens. Any ideas?

Probably a graphics driver issue.
Recovery mode uses a generic video driver that should work with all graphics chips/cards.

So, first question: what graphics chip are you using?
Maybe post the output of:

/sbin/lspci

or

/usr/sbin/hwinfo --gfxcard

I suppose you didn’t install any graphics drivers manually?

Running

/sbin/lspci 

gives me this (I’m assuming the only relevant information is what concerns the display):

00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 09)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 09)

and running

 /usr/sbin/hwinfo --gfxcard 

gives me this:

08: PCI 02.0: 0300 VGA compatible controller (VGA)
[Created at pci.319]
Unique ID: _Znp.Bg2Pelut2yD
SysFS ID: /devices/pci0000:00/0000:00:02.0
SysFS BusID: 0000:00:02.0
Hardware Class: graphics card
Model: “Intel Mobile 4 Series Chipset Integrated Graphics Controller”
Vendor: pci 0x8086 “Intel Corporation”
Device: pci 0x2a42 “Mobile 4 Series Chipset Integrated Graphics Controller”
SubVendor: pci 0x1025 “Acer Incorporated [ALI]”
SubDevice: pci 0x0212
Revision: 0x09
Memory Range: 0xd0000000-0xd03fffff (rw,non-prefetchable)
Memory Range: 0xc0000000-0xcfffffff (ro,non-prefetchable)
I/O Ports: 0x50f0-0x50f7 (rw)
IRQ: 44 (no events)
I/O Ports: 0x3c0-0x3df (rw)
Module Alias: “pci:v00008086d00002A42sv00001025sd00000212bc03sc00i00”
Driver Info #0:
Driver Status: i915 is active
Driver Activation Cmd: “modprobe i915”
Config Status: cfg=no, avail=yes, need=no, active=unknown

09: PCI 02.1: 0380 Display controller
[Created at pci.319]
Unique ID: ruGf.i6Q1YbBYKZ3
SysFS ID: /devices/pci0000:00/0000:00:02.1
SysFS BusID: 0000:00:02.1
Hardware Class: graphics card
Model: “Intel Mobile 4 Series Chipset Integrated Graphics Controller”
Vendor: pci 0x8086 “Intel Corporation”
Device: pci 0x2a43 “Mobile 4 Series Chipset Integrated Graphics Controller”
SubVendor: pci 0x1025 “Acer Incorporated [ALI]”
SubDevice: pci 0x0212
Revision: 0x09
Memory Range: 0xd3400000-0xd34fffff (rw,non-prefetchable)
Module Alias: “pci:v00008086d00002A43sv00001025sd00000212bc03sc80i00”
Config Status: cfg=no, avail=yes, need=no, active=unknown

Primary display adapter: #8

Oh and no I have not installed anything manually.

You have an intel chip. You shouldn’t have to install anything manually in that case.

Have you installed all updates yet?
There were some issues with the shipped intel driver tha have been fixed shortly after the release.

And to verify that it is indeed the graphics driver:

  • can you switch to text mode by pressing “Ctrl+Alt+F1”?
  • does adding “nomodeset” to the boot options work?
    Press ‘e’ at the boot menu, search for the line starting with “linux”, and append “nomodeset” at the end. Then press ‘F10’ to boot.
    This will disable the intel driver, much like recovery mode, but recovery mode also changes some other settings (CPU and powermanagement related ones e.g.) as well.

Appending nomodeset does indeed work, however when I reboot it goes back to normal. How can I make that permanent? Or is there something better to do?

On 2014-09-06 09:26, wolfi323 wrote:
>
> UnderhandedOverhead;2663042 Wrote:
>> I’m fairly new to linux, and very new to opensuse, but I cannot figure
>> out why I cannot boot in the normal mode. What is different about
>> recovery mode? When I try to boot in the normal mode the screen goes
>> black and nothing happens. Any ideas?
> Probably a graphics driver issue.
> Recovery mode uses a generic video driver that should work with all
> graphics chips/cards.

Wait, it is “recovery mode”, not “Failsafe mode”. Graphic failure should
not dump you into recovery mode: it should dump you just on normal
text mode. A corrupted or missing partition can dump you to recovery mode.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

Add it in YaST->Boot Loader->Boot Loader Options, or in /etc/default/grub and run “sudo grub2-mkconfig /boot/grub2/grub.cfg”.
But that will disable the intel driver completely.
It was mainly meant as a temporary work-around to get into the system, and to check whether the graphics driver really is the problem.

Or is there something better to do?

Hopefully, yes.
First, install all updates, as already mentioned.
Maybe this would fix it already.

sudo zypper up

If it still doesn’t work, please boot to “recovery mode” (“advanced options” in the boot menu)/add “nomodeset” after a failed boot, and post the file /var/log/Xorg.0.log.old.

zypper did update a lot of things, unfortunately it did not solve the problem.
This is the content of xorg.0.log.old. I have only posted what seems to be the relevant information as the file was too long. I can post the rest if necessary. Sorry I’m kind of stumbling around all of this at the moment.
27.839]
X.Org X Server 1.12.3
Release Date: 2012-07-09
27.839] X Protocol Version 11, Revision 0
27.839] Build Operating System: openSUSE SUSE LINUX
27.839] Current Operating System: Linux linux-z53h.site 3.4.63-2.44-desktop #1 SMP PREEMPT Wed Oct 2 11:18:32 UTC 2013 (d91a619) x86_64
27.839] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.4.63-2.44-desktop root=UUID=ee216024-0221-4288-b8d8-6ad02468bd32 video=1366x768 resume=/dev/disk/by-id/ata-Hitachi_HTS543225L9A300_080916FB2D00LJG3K59B-part4 splash=silent quiet showopts
27.839] Build Date: 19 December 2013 01:41:37PM
27.839]
27.839] Current version of pixman: 0.24.4
27.839] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
27.839] Markers: (–) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
27.839] (==) Log file: “/var/log/Xorg.0.log”, Time: Sat Sep 6 16:43:42 2014
27.840] (==) Using config directory: “/etc/X11/xorg.conf.d”
27.840] (==) Using system config directory “/usr/share/X11/xorg.conf.d”
27.840] (==) No Layout section. Using the first Screen section.
27.840] (==) No screen section available. Using defaults.
27.840] (
) |–>Screen “Default Screen Section” (0)
27.840] (**) | |–>Monitor “<default monitor>”
27.840] (==) No monitor specified for screen “Default Screen Section”.
Using a default monitor configuration.
27.840] (==) Automatically adding devices
27.840] (==) Automatically enabling devices
27.840] (WW) The directory “/usr/share/fonts/URW/” does not exist.
27.840] Entry deleted from font path.
27.856] (WW) The directory “/usr/share/fonts/misc/sgi” does not exist.
27.856] Entry deleted from font path.
27.856] (==) FontPath set to:
/usr/share/fonts/misc:unscaled,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/cyrillic:unscaled,
/usr/share/fonts/truetype/,
built-ins
27.856] (==) ModulePath set to “/usr/lib64/xorg/modules/updates,/usr/lib64/xorg/modules”
27.856] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
27.856] (II) Loader magic: 0x7ccae0
27.856] (II) Module ABI versions:
27.856] X.Org ANSI C Emulation: 0.4
27.856] X.Org Video Driver: 12.0
27.856] X.Org XInput driver : 16.0
27.856] X.Org Server Extension : 6.0
27.857] (–) PCI:*(0:0:2:0) 8086:2a42:1025:0212 rev 9, Mem @ 0xd0000000/4194304, 0xc0000000/268435456, I/O @ 0x000050f0/8
27.857] (–) PCI: (0:0:2:1) 8086:2a43:1025:0212 rev 9, Mem @ 0xd3400000/1048576
27.858] (II) Open ACPI successful (/var/run/acpid.socket)
27.858] (II) “extmod” will be loaded by default.
27.858] (II) “dbe” will be loaded by default.
27.858] (II) “glx” will be loaded by default.
27.858] (II) “record” will be loaded by default.
27.858] (II) “dri” will be loaded by default.
27.858] (II) “dri2” will be loaded. This was enabled by default and also specified in the config file.
27.858] (II) LoadModule: “dri2”
27.869] (II) Loading /usr/lib64/xorg/modules/extensions/libdri2.so
27.869] (II) Module dri2: vendor=“X.Org Foundation”
27.869] compiled for 1.12.3, module version = 1.2.0
27.869] ABI class: X.Org Server Extension, version 6.0
27.869] (II) Loading extension DRI2
27.869] (II) LoadModule: “glamoregl”
27.870] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
27.872] (II) Module glamoregl: vendor=“X.Org Foundation”
27.872] compiled for 1.12.3, module version = 0.4.0
27.872] ABI class: X.Org ANSI C Emulation, version 0.4
27.872] (II) LoadModule: “extmod”
27.872] (II) Loading /usr/lib64/xorg/modules/extensions/libextmod.so
27.872] (II) Module extmod: vendor=“X.Org Foundation”
27.872] compiled for 1.12.3, module version = 1.0.0
27.872] Module class: X.Org Server Extension
27.872] ABI class: X.Org Server Extension, version 6.0
27.872] (II) Loading extension MIT-SCREEN-SAVER
27.872] (II) Loading extension XFree86-VidModeExtension
27.872] (II) Loading extension XFree86-DGA
27.872] (II) Loading extension DPMS
27.872] (II) Loading extension XVideo
27.872] (II) Loading extension XVideo-MotionCompensation
27.872] (II) Loading extension X-Resource
27.872] (II) LoadModule: “dbe”
27.873] (II) Loading /usr/lib64/xorg/modules/extensions/libdbe.so
27.873] (II) Module dbe: vendor=“X.Org Foundation”
27.873] compiled for 1.12.3, module version = 1.0.0
27.873] Module class: X.Org Server Extension
27.873] ABI class: X.Org Server Extension, version 6.0
27.873] (II) Loading extension DOUBLE-BUFFER
27.873] (II) LoadModule: “glx”
27.873] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
27.873] (II) Module glx: vendor=“X.Org Foundation”
27.873] compiled for 1.12.3, module version = 1.0.0
27.873] ABI class: X.Org Server Extension, version 6.0
27.873] (==) AIGLX enabled
27.873] (II) Loading extension GLX
27.873] (II) LoadModule: “record”
27.874] (II) Loading /usr/lib64/xorg/modules/extensions/librecord.so
27.874] (II) Module record: vendor=“X.Org Foundation”
27.874] compiled for 1.12.3, module version = 1.13.0
27.874] Module class: X.Org Server Extension
27.874] ABI class: X.Org Server Extension, version 6.0
27.874] (II) Loading extension RECORD
27.874] (II) LoadModule: “dri”
27.874] (II) Loading /usr/lib64/xorg/modules/extensions/libdri.so
27.874] (II) Module dri: vendor=“X.Org Foundation”
27.874] compiled for 1.12.3, module version = 1.0.0
27.874] ABI class: X.Org Server Extension, version 6.0
27.874] (II) Loading extension XFree86-DRI
27.874] (==) Matched intel as autoconfigured driver 0
27.874] (==) Matched fbdev as autoconfigured driver 1
27.874] (==) Matched vesa as autoconfigured driver 2
27.874] (==) Assigned the driver to the xf86ConfigLayout
27.874] (II) LoadModule: “intel”
27.875] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
27.890] (II) Module intel: vendor=“X.Org Foundation”
27.890] compiled for 1.12.3, module version = 2.20.3
27.890] Module class: X.Org Video Driver
27.890] ABI class: X.Org Video Driver, version 12.0
27.890] (II) LoadModule: “fbdev”
27.891] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
27.891] (II) Module fbdev: vendor=“X.Org Foundation”
27.891] compiled for 1.12.3, module version = 0.4.2
27.891] ABI class: X.Org Video Driver, version 12.0
27.891] (II) LoadModule: “vesa”
27.891] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
27.891] (II) Module vesa: vendor=“X.Org Foundation”
27.891] compiled for 1.12.3, module version = 2.3.1
27.891] Module class: X.Org Video Driver
27.891] ABI class: X.Org Video Driver, version 12.0
27.891] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
Ivybridge Server (GT2)
27.892] (II) FBDEV: driver for framebuffer: fbdev
27.892] (II) VESA: driver for VESA chipsets: vesa
27.892] (++) using VT number 7

27.895] (WW) Falling back to old probe method for fbdev
27.895] (II) Loading sub module "fbdevhw"
27.895] (II) LoadModule: "fbdevhw"
27.895] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
27.895] (II) Module fbdevhw: vendor="X.Org Foundation"
27.895]     compiled for 1.12.3, module version = 0.0.2
27.895]     ABI class: X.Org Video Driver, version 12.0
27.895] (WW) Falling back to old probe method for vesa
27.895] drmOpenDevice: node name is /dev/dri/card0
27.895] drmOpenDevice: open result is 9, (OK)
27.895] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
27.895] drmOpenDevice: node name is /dev/dri/card0
27.895] drmOpenDevice: open result is 9, (OK)
27.895] drmOpenByBusid: drmOpenMinor returns 9
27.895] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
27.895] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
27.895] (==) intel(0): Depth 24, (--) framebuffer bpp 32
27.895] (==) intel(0): RGB weight 888
27.895] (==) intel(0): Default visual is TrueColor
27.895] (--) intel(0): Integrated Graphics Chipset: Intel(R) GM45
27.896] (**) intel(0): Relaxed fencing enabled
27.896] (**) intel(0): Wait on SwapBuffers? enabled
27.896] (**) intel(0): Triple buffering? enabled
27.896] (**) intel(0): Framebuffer tiled
27.896] (**) intel(0): Pixmaps tiled
27.896] (**) intel(0): 3D buffers tiled
27.896] (**) intel(0): SwapBuffers wait enabled
27.896] (==) intel(0): video overlay key set to 0x101fe
27.896] (II) intel(0): Output LVDS1 has no monitor section
28.004] (II) intel(0): found backlight control interface /sys/class/backlight/acpi_video0
28.024] (II) intel(0): Output VGA1 has no monitor section
28.053] (II) intel(0): Output DP1 has no monitor section
28.053] (II) intel(0): EDID for output LVDS1
28.053] (II) intel(0): Manufacturer: LGD  Model: d801  Serial#: 0
28.053] (II) intel(0): Year: 2008  Week: 0
28.053] (II) intel(0): EDID Version: 1.3
28.053] (II) intel(0): Digital Display Input
28.053] (II) intel(0): Max Image Size [cm]: horiz.: 34  vert.: 19
28.053] (II) intel(0): Gamma: 2.20
28.053] (II) intel(0): No DPMS capabilities specified
28.053] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 
28.053] (II) intel(0): First detailed timing is preferred mode
28.053] (II) intel(0): redX: 0.640 redY: 0.353   greenX: 0.319 greenY: 0.572
28.053] (II) intel(0): blueX: 0.148 blueY: 0.102   whiteX: 0.313 whiteY: 0.329
28.053] (II) intel(0): Manufacturer's mask: 0
28.053] (II) intel(0): Supported detailed timing:
28.053] (II) intel(0): clock: 72.3 MHz   Image Size:  344 x 194 mm
28.053] (II) intel(0): h_active: 1366  h_sync: 1414  h_sync_end 1446 h_blank_end 1526 h_border: 0
28.053] (II) intel(0): v_active: 768  v_sync: 771  v_sync_end 776 v_blanking: 790 v_border: 0
28.053] (II) intel(0):  LG Display
28.053] (II) intel(0):  LP156WH1-TLC1
28.053] (II) intel(0): EDID (in hex):
28.053] (II) intel(0):     00ffffffffffff0030e401d800000000
28.053] (II) intel(0):     00120103802213780ade05a35a519226
28.053] (II) intel(0):     1a505400000001010101010101010101
28.053] (II) intel(0):     0101010101013e1c56a0500016303020
28.053] (II) intel(0):     350058c2100000190000000000000000
28.053] (II) intel(0):     00000000000000000000000000fe004c
28.053] (II) intel(0):     4720446973706c61790a2020000000fe
28.053] (II) intel(0):     004c503135365748312d544c4331004f
28.053] (II) intel(0): EDID vendor "LGD", prod id 55297
28.053] (II) intel(0): Printing DDC gathered Modelines:
28.053] (II) intel(0): Modeline "1366x768"x0.0   72.30  1366 1414 1446 1526  768 771 776 790 -hsync -vsync (47.4 kHz eP)
28.053] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
28.053] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
28.053] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
28.053] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
28.053] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
28.053] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
28.053] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
28.053] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
28.053] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
28.053] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
28.053] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
28.053] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
28.053] (II) intel(0): Printing probed modes for output LVDS1
28.053] (II) intel(0): Modeline "1366x768"x60.0   72.30  1366 1414 1446 1526  768 771 776 790 -hsync -vsync (47.4 kHz eP)
28.053] (II) intel(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz d)
28.053] (II) intel(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz d)
28.053] (II) intel(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz d)
28.053] (II) intel(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz d)
28.069] (II) intel(0): EDID for output VGA1
28.101] (II) intel(0): EDID for output DP1
28.101] (II) intel(0): Output LVDS1 connected
28.101] (II) intel(0): Output VGA1 disconnected
28.101] (II) intel(0): Output DP1 disconnected
28.101] (II) intel(0): Using exact sizes for initial modes
28.101] (II) intel(0): Output LVDS1 using initial mode 1366x768

No, this is the log from the current boot, which is to recovery mode.

Xorg.0.log.old is not a backup file, it’s the log file from the previous boot.
What do you mean with you can’t open it? Is it empty?
Then X would not even start, i.e. the system would hang before that.

“Recovery mode” is the same as “failsafe mode”.

Graphic failure should not dump you into recovery mode: it should dump you just on normal text mode. A corrupted or missing partition can dump you to recovery mode

No. A corrupted or missing partition will dump you to “emergency mode”.

“Recovery mode” is what you manually select at the boot menu, under “Advanced Options”, it was called “failsafe” in grub1.
You do not get dumped there.

I guess you confused this thread with a different one? :wink:

Oh, you edited your post apparently?
You can use a sharing/pasting site like http://susepaste.org for providing the whole content.

But it shouldn’t be necessary:

27.839] 

X.Org X Server 1.12.3
Release Date: 2012-07-09
27.839] X Protocol Version 11, Revision 0
27.839] Build Operating System: openSUSE SUSE LINUX
27.839] Current Operating System: Linux linux-z53h.site 3.4.63-2.44-desktop #1 SMP PREEMPT Wed Oct 2 11:18:32 UTC 2013 (d91a619) x86_64
27.839] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.4.63-2.44-desktop root=UUID=ee216024-0221-4288-b8d8-6ad02468bd32 video=1366x768 resume=/dev/disk/by-id/ata-Hitachi_HTS543225L9A300_080916FB2D00LJG3K59B-part4 splash=silent quiet showopts
27.839] Build Date: 19 December 2013 01:41:37PM
27.839]
27.839] Current version of pixman: 0.24.4
27.839] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
27.839] Markers: (–) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
27.839] (==) Log file: “/var/log/Xorg.0.log”, Time: Sat Sep 6 16:43:42 2014

You are running Xorg 1.12.3 on kernel 3.4.63.
What openSUSE version is this about?
Those versions are from 12.2, which is unsupported since January already.

And what updates did you install now?
openSUSE 12.2 doesn’t get any updates any more for over half a year.

Please post your repo list:

zypper lr -d

OS: Linux 3.4.63-2.44-desktop x86_64
System: openSUSE 12.2 (x86_64)
KDE: 4.8.5 (4.8.5) "release 2

I think I installed this in january of last year and haven’t really bothered with it since then. But I’d really like to get it to work.

Is there a way to tell what updates I just did? Here is my list of repos

| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service

–±--------------------------±-----------------------------------±--------±--------±---------±-------±--------------------------------------------------------------------------------±-------
1 | openSUSE-12.2-1.6 | openSUSE-12.2-1.6 | Yes | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-MATSHITADVD-RAM_UJ890AS_UH43_172936,/dev/sr0 |
2 | repo-debug | openSUSE-12.2-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/12.2/repo/oss/ |
3 | repo-debug-update | openSUSE-12.2-Update-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/update/12.2/ |
4 | repo-debug-update-non-oss | openSUSE-12.2-Update-Debug-Non-Oss | No | Yes | 99 | NONE | http://download.opensuse.org/debug/update/12.2-non-oss/ |
5 | repo-non-oss | openSUSE-12.2-Non-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/12.2/repo/non-oss/ |
6 | repo-oss | openSUSE-12.2-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/12.2/repo/oss/ |
7 | repo-source | openSUSE-12.2-Source | Yes | Yes | 99 | yast2 | http://download.opensuse.org/source/distribution/12.2/repo/oss/ |
8 | repo-update | openSUSE-12.2-Update | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/12.2/ |
9 | repo-update-non-oss | openSUSE-12.2-Update-Non-Oss | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/12.2-non-oss/ |

You would probably better off with upgrading to a current, supported version (12.3 or 13.1).
See here for how to do that:
https://en.opensuse.org/SDB:System_upgrade (online upgrade in the running system)
https://en.opensuse.org/SDB:Offline_upgrade (offline upgrade, i.e. by booting from an installation medium)

This in itself will probably fix your problem already.

But IIUYC, this is a virgin installation anyway. So you could just as well install a current version from scratch.

Is there a way to tell what updates I just did? Here is my list of repos

Since you only have the standard 12.2 repos, this likely have been all official updates ever released for 12.2.
Apparently you didn’t update your system for quite some time, as I said there are no more new updates since January.

In yast -software management you can view the update/install history

On 2014-09-06 16:16, wolfi323 wrote:

> robin_listas;2663077 Wrote:
>> Wait, it is “recovery mode”, not “Failsafe mode”.
> “Recovery mode” is the same as “failsafe mode”.

Not really :slight_smile:

It is a specific target in systemd, with different features and
limitations than the state you reach by choosing “failsafe” in grub.

AKA emergency mode.

>> Graphic failure should not dump you into recovery mode: it should dump
>> you just on normal text mode. A corrupted or missing partition can
>> dump you to recovery mode
> No. A corrupted or missing partition will dump you to “emergency mode”.

Exactly. That one.

> “Recovery mode” is what you manually select at the boot menu, under
> “Advanced Options”, it was called “failsafe” in grub1.
> You do not get dumped there.

Exactly. That one. In my grub menu it is labelled “failsafe”, I just
looked. And it is different from what systemd calls “rescue or recovery
mode”.


/usr/lib/systemd/system/rescue.service
/usr/lib/systemd/system/rescue.target

> I guess you confused this thread with a different one? :wink:

Nope :slight_smile:

I’m sorry, but different people call these modes differently, and change
names with time. You must do educated guesses and find out what mode the
user is really in.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

On 2014-09-06 16:36, UnderhandedOverhead wrote:
>
> wolfi323;2663106 Wrote:
>>
>> What openSUSE version is this about?
>
>
> OS: Linux 3.4.63-2.44-desktop x86_64
> System: openSUSE 12.2 (x86_64)
> KDE: 4.8.5 (4.8.5) "release 2
>
>
>
> I think I installed this in january of last year and haven’t really
> bothered with it since then. But I’d really like to get it to work.

Then scratch it, and install openSUSE 13.1 on top.
Assuming you don’t have any file you want to keep… If you do, ask again.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

On 2014-09-06 16:16, wolfi323 wrote:

> I guess you confused this thread with a different one? :wink:

Maybe I did :-???


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

Wrong.
Have a look into /usr/lib/systemd/system/: There’s an emergency.target, and a rescue.target, but no recovery.target.

Recovery Mode is a menu entry in grub2’s boot menu, in Advanced Options.

> “Recovery mode” is what you manually select at the boot menu, under
> “Advanced Options”, it was called “failsafe” in grub1.
> You do not get dumped there.

Exactly. That one. In my grub menu it is labelled “failsafe”, I just
looked. And it is different from what systemd calls “rescue or recovery
mode”.

systemd does not call anything “recovery mode”.

# grep -Ri recovery /usr/lib/systemd/
#

There’s a rescue mode (rescue.target) and an emergency mode (emergency.target).

But they have nothing to do with grub2’s recovery mode menu entry.

That’s what I’m saying.

It is behind the times. Install openSUSE 13.1 (or at least 12.3). That will probably solve your problem (and a few others you would otherwise encounter).