At Terminal not Graphic login point.

Using openSUSE 11.4 x86_64.

During start up, reach OS choice prompt then IF select title Desktop – openSUSE 11.4 - 2.6.37.6-0.11 find only reaches terminal login, rather than the graphic login to the Gnome desktop.

With title Failsafe – openSUSE 11.4 - 2.6.37.6-0.11 login works OK.

When at boot menu, IF add to command line: x11failsafe it opens to Gnome desktop graphic login point.

Like a better long term solution ?


linux-fy2u:~ # cat /boot/grub/menu.lst
# Modified by YaST2. Last modification on Sun Feb  5 16:01:08 EST 2012
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader

timeout 8
##YaST - generic_mbr
gfxmenu (hd0,1)/boot/message
##YaST - activate
default 0

###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 11.4 - 2.6.37.6-0.11
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.37.6-0.11-desktop root=/dev/disk/by-id/ata-ST500DM002-1BC142_Z2ABSE1G-part2 resume=/dev/disk/by-id/ata-ST500DM002-1BC142_Z2ABSE1G-part1 splash=silent quiet showopts vga=0x317
    initrd /boot/initrd-2.6.37.6-0.11-desktop

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.4 - 2.6.37.6-0.11
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.37.6-0.11-desktop root=/dev/disk/by-id/ata-ST500DM002-1BC142_Z2ABSE1G-part2 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x317
    initrd /boot/initrd-2.6.37.6-0.11-desktop
linux-fy2u:~ # 

Add “nomodeset” to the first boot entry.

###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 11.4 - 2.6.37.6-0.11
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.37.6-0.11-desktop root=/dev/disk/by-id/ata-ST500DM002-1BC142_Z2ABSE1G-part2 \
resume=/dev/disk/by-id/ata-ST500DM002-1BC142_Z2ABSE1G-part1 splash=silent quiet showopts **nomodeset** vga=0x317

Several times tried adding nomodeset during the re-start OS selection process, this never made a difference.

Soon as added x11failsafe it went to the Gnome user login start.

The Xorg log ?

linux-xfp4:~ # grep -i '(ww)'   /var/log/Xorg.0.log
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    13.331] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
    13.331] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    13.417] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist.
    13.481] (WW) Warning, couldn't open module vboxvideo
    13.498] (WW) Warning, couldn't open module vmwgfx
    13.623] (WW) Falling back to old probe method for cirrus
    13.630] (WW) Falling back to old probe method for vesa
linux-xfp4:~ # 

Must run back later
.

What’s your graphic card? Please post the output of this command:

hwinfo --gfxcard

That looks like xorg.conf.install. The setup could not identify your graphics card… at all?! … or you are on a virtual machine?

On 2012-02-06 10:16, paulparker wrote:
>
> Several times tried adding nomodeset during the re-start OS selection
> process, this never made a difference.
>
> Soon as added x11failsafe it went to the Gnome user login start.

If I remember right, x11failsafe uses the same xorg file used for the
installation system, different from the running system. Have you somehow
created a xorg.conf file?

If yes, rename it to disable.
If not, create it as copy of /etc/X11/xorg.conf.install


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

This a desktop without virtual - excluding chance of such as side effects from attempts to set up server things so could learn how to access files from another pc…

linux-xfp4:~ # hwinfo --gfxcard
30: PCI 105.0: 0300 VGA compatible controller (VGA)             
  [Created at pci.318]
  Unique ID: ul7N.Bj7y3mEqNmD
  Parent ID: vSkL.+dNxfBU_RY0
  SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:05.0
  SysFS BusID: 0000:01:05.0
  Hardware Class: graphics card
  Model: "ATI Radeon HD 3000 Graphics"
  Vendor: pci 0x1002 "ATI Technologies Inc"
  Device: pci 0x9616 "ATI Radeon HD 3000 Graphics"
  SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
  SubDevice: pci 0x8388 
  Driver: "radeon"
  Driver Modules: "drm"
  Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable)
  I/O Ports: 0xd000-0xdfff (rw)
  Memory Range: 0xfebe0000-0xfebeffff (rw,non-prefetchable)
  Memory Range: 0xfea00000-0xfeafffff (rw,non-prefetchable)
  IRQ: 18 (608 events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v00001002d00009616sv00001043sd00008388bc03sc00i00"
  Driver Info #0:
    XFree86 v4 Server Module: radeonhd
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #10 (PCI bridge)

Primary display adapter: #30
linux-xfp4:~ # 

linux-xfp4:~ # l -tr /etc/X11/xorg.conf*
-rw-r--r-- 1 root root  849 Nov 15 10:52 /etc/X11/xorg.conf.install
-rw-r--r-- 1 root root   87 Dec 17 10:28 /etc/X11/xorg.conf.original-0
-rw-r--r-- 1 root root  706 Dec 17 10:28 /etc/X11/xorg.conf
-rw-r--r-- 1 root root  706 Dec 30 13:39 /etc/X11/xorg.conf.fglrx-postun


Away now to try catch up some lost sleep…back on tomorrow.

Open a terminal and type the following:

su -l 
zypper ar [noparse]http://download.opensuse.org/repositories/home:/please_try_again/openSUSE_11.4/[/noparse]  PTA 
zypper refresh -r PTA 
zypper in atiupgrade
/usr/bin/atiupgrade

It will take some time to download and install all the stuff and build the driver. When it is complete, reboot! It should be OK.

Doing now…

RESOLVED… start up proceeded as expect it should, many thanks.

Puzzled as to why this problem… and whether answered correctly the questions during the process - saved terminal output to file. [must run now for an appointment, back in hour or two].

Do you want to reject the key, trust temporarily, or trust always? [r/t/a/?] (r): t

Should above question be answered a ?
If yes, how do we change our answer ?

Should we retain repository PTA ?

linux-xfp4:~ # zypper lr
#  | Alias                            | Name                             | Enabled | Refresh
---+----------------------------------+----------------------------------+---------+--------
 1 | PTA                              | PTA                              | Yes     | No     
 2 | Updates-for-openSUSE-11.4-11.4-0 | Updates for openSUSE 11.4 11.4-0 | Yes     | Yes    
 3 | libdvdcss                        | libdvdcss                        | Yes     | Yes    
 4 | openSUSE-11.4-11.4-0             | openSUSE-11.4-11.4-0             | Yes     | No     
 5 | packman                          | packman                          | Yes     | Yes    
 6 | repo-debug                       | openSUSE-11.4-Debug              | No      | Yes    
 7 | repo-debug-update                | openSUSE-11.4-Update-Debug       | No      | Yes    
 8 | repo-non-oss                     | openSUSE-11.4-Non-Oss            | Yes     | Yes    
 9 | repo-oss                         | openSUSE-11.4-Oss                | Yes     | Yes    
10 | repo-source                      | openSUSE-11.4-Source             | No      | Yes    
linux-xfp4:~ # 

I would. So you could get atiupgrade updates. It is sometimes necessary to modify the script. But you might not have to use it anymore if you don’t intend to update the ATI driver. If you’re happy with this one, you don’t have to. You can also disable the repo without removing it:

zypper mr -d PTA

And reenable it at a later point:

zypper mr -e PTA

Yes, “a” is the right answer. You have to accept the key to be able to refresh and use the repo. To view and remove keys, you can use the script posted here: List, export and remove RPM GPG keys.You don’t need to remove my key though.

I you wonder if you should accept keys or not, I suggest reading this post About Feature 3212047 and trust. and signing up for feature 312047.

Sorry perhaps not clear due my rushing of to an appointment.

How do we change the t into an a ?

If you trusted the key temporarily, I would assume that it would ask you again. Then you can say “a”. I’m just guessing, but it seems logical.

I have a very similar problem:

  • When I connect the VDU directly to the PC, everything works fine.
  • When I connect via the KVM switch (D-Link DKVM-4K, no graphic desktop.
  • If I add either x11failsafe or nomodeset to the boot string the graphic desktop starts. From what I read in the post, I assume this forces the read of the xorg.conf.install.

Is there a down side to permanently adding one of the above to the bootstring permanently?
Will copying xorg.conf.install to xorg.conf not bite me in the backside at a later stage?

More info:
Other PC’s running openSUSE 11 works just fine via the KVM switch.
Not a virtual machine.

Output of hwinfo --gfxcard:

 # hwinfo --gfxcard
10: PCI 02.0: 0300 VGA compatible controller (VGA)              
  [Created at pci.319]
  Unique ID: _Znp.TF_4IGugN40
  SysFS ID: /devices/pci0000:00/0000:00:02.0
  SysFS BusID: 0000:00:02.0
  Hardware Class: graphics card
  Model: "Intel VGA compatible controller"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x0102 
  SubVendor: pci 0x1462 "Micro-Star International Co., Ltd."
  SubDevice: pci 0x7680 
  Revision: 0x09
  Memory Range: 0xfe000000-0xfe3fffff (rw,non-prefetchable)
  Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable)
  I/O Ports: 0xf000-0xf03f (rw)
  IRQ: 40 (no events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v00008086d00000102sv00001462sd00007680bc03sc00i00"
  Driver Info #0:
    Driver Status: i915 is active
    Driver Activation Cmd: "modprobe i915"
  Config Status: cfg=no, avail=yes, need=no, active=unknown

Primary display adapter: #10

What do I change in the neat little zypper script to download the correct drivers for a “Intel VGA compatible controller” ?

Sorry, the above hwinfo --gfxcard output is with nomodeset in the boot string. The output of hwinfo --gfxcard WITHOUT nomodeset in the boot string:

10: PCI 02.0: 0300 VGA compatible controller (VGA)
  [Created at pci.319]
  Unique ID: _Znp.TF_4IGugN40
  SysFS ID: /devices/pci0000:00/0000:00:02.0
  SysFS BusID: 0000:00:02.0
  Hardware Class: graphics card
  Model: "Intel VGA compatible controller"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x0102
  SubVendor: pci 0x1462 "Micro-Star International Co., Ltd."
  SubDevice: pci 0x7680
  Revision: 0x09
  Driver: "i915"
  Driver Modules: "drm"
  Memory Range: 0xfe000000-0xfe3fffff (rw,non-prefetchable)
  Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable)
  I/O Ports: 0xf000-0xf03f (rw)
  IRQ: 40 (1378 events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v00008086d00000102sv00001462sd00007680bc03sc00i00"
  Driver Info #0:
    Driver Status: i915 is active
    Driver Activation Cmd: "modprobe i915"
  Config Status: cfg=no, avail=yes, need=no, active=unknown

Primary display adapter: #10

On 2012-02-13 14:56, stefaug wrote:
>
> I have a very similar problem:
>
> - When I connect the VDU directly to the PC, everything works fine.
> - When I connect via the KVM switch (D-Link DKVM-4K, no graphic
> desktop.

Too bad.

> - If I add either x11failsafe or nomodeset to the boot string the
> graphic desktop starts. From what I read in the post, I assume this
> forces the read of the xorg.conf.install.

Yes, that’s it.

> Is there a down side to permanently adding one of the above to the
> bootstring permanently?

Dunno.

> Will copying xorg.conf.install to xorg.conf not bite me in the backside
> at a later stage?

This is better, I think. No later problems, there should not. It will
probably mean slower graphics. But it could be even better if you can
generate a xorg.conf corresponding to the configuration detected when you
connect directly. I think there is a command line to generate it, but I
don’t know from memory.

>
> More info:
> Other PC’s running openSUSE 11 works just fine via the KVM switch.
> Not a virtual machine.

There is no such thing as openSUSE 11.

> What do I change in the neat little zypper script to download the
> correct drivers for a “Intel VGA compatible controller” ?

It is internal to the kernel, I think.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)