Blank login screen

English Install/Boot/Login
#1

Hello all,

I have installed openSUSE 11.4 on my notebook (HP Pavilion DV5-2040br) with success, but after restart I got a blank login screen (nothing to see).
If I turn off login policy, and put my user to login automatically, everything goes fine. The screen blink some times but KDE starts.
If I turn it on again, the login screen does not appear… But I know that login screen is there because if I type my user name and password KDE loads up and the screen appears again (with loading bar, after login).
Could you help me with this issue? It seems to be something related to framebuffer turning off and Intel driver turning on… Maybe login screen is loaded on framebuffer and I can’t see that… I’m really lost on this…

Thanks.

#2

Tried failsafe boot? Sounds like a video problem. What video card/chip do you have?

#3

Hi,

What is your graphic card ? At GRUB login, do as you see in this picture (pass the nomodeset parameter) : File:Nomodeset-example.jpg - openSUSE

#4

My video card is described as “Integrated HD Intel graphics”.
If I try to boot using “Fail safe” mode everything goes fine… But 3D acceleration does not work.

#5

Did you try booting as in the link I refer to you earlier?

#6

When I pass nomodeset as kernel parameter I could not load 3D acceleration.

#7

That is normal. So I presume you log in normally in KDE with the nomodeset parameter ?

Can you give us the output of this command please :

 hwinfo --gfxcard | grep -i -e model -e driver
#8

Hello All,

Sorry for my delay… I was out for a while…
Follow the result for “hwinfo --gfxcard | grep -i -e model -e driver”:

Model: “Intel Arrandale Integrated Graphics Controller”
Driver: “i915”
Driver Modules: “drm”
Driver Info #0:
Driver Status: i915 is active
Driver Activation Cmd: “modprobe i915”

As I told before, after driver loads everything appears fine, but I need to use login without authentication. By this way KDE loads driver and shows me desktop! Before that, from GRUB selection until KDE loads my screen is blank.

#9

Could someone help this good soul lost in the dark (really dark, because my login screen still blank :))… I’m wondering if could be something related to KMS changes… I know nothing about KMS! Or maybe related to some forgot module on initrd image…

#10

The Intel Arrandale i915 has caused a number of openSUSE users some pain.

I recommend you install the application Midnight Commander (mc) such that you can get a text editor when in a text mode by typing ‘mc’ (no quotes). That way if you get stranded in a text mode because of an edit we have had you do, you can remove the edit and recover. :slight_smile:

Now after installing ‘mc’, change the /etc/X11/xorg.conf.d/50-device.conf file to:


Section "Device"
  Identifier "Default Device"

  #Driver "radeon"
  Driver "intel"

  ## Required magic for radeon/radeonhd drivers; output name
  ## (here: "DVI-0") can be figured out via 'xrandr -q'
  #Option "monitor-DVI-0" "Default Monitor"

EndSection

and save the change, and reboot, using the boot code ‘nomodeset’ in this case.

My guess is it will fail to load, and you will need to boot to failsafe (or press ‘3’ as a boot code) to boot to a text mode.

In which case, try the Intellegacy driver (an old Intel driver) by changing the /etc/X11/xorg.conf.d/50-device.conf file to:


Section "Device"
  Identifier "Default Device"

  #Driver "radeon"
  Driver "intellegacy"

  ## Required magic for radeon/radeonhd drivers; output name
  ## (here: "DVI-0") can be figured out via 'xrandr -q'
  #Option "monitor-DVI-0" "Default Monitor"

EndSection

Reboot and text. Try with and without nomodeset in this case.

Note in a text mode you can reboot with root permissions with the command:


shutdown -r now

and you can halt the pc with the command:


shutdown -h now

Note we are all unpaid volunteers/enthusiasts here. We have different day jobs (with nothing to do with Linux) that pays for our food and rent. We are like you in that we also can not immediately reply. So please have patience if we don’t reply within a day or so.

#11

I have the same graphic chip in a Lenovo T410s, which up until recently, worked great with opensuse 12.2

The laptop LCD and the external VGA behavior is almost irrelevant, the issue appears to be xrandr finds no devices,
which is why I am posting here, perhaps just to share or exchange info. By the way, the current behavior is:

laptop open - boots fine, LCD works - VGA not - Fn+F7 does nothing
laptop closed - boots fine, VGA works, LCD not Fn+F7 does nothing

Pressing Fb+F7 results in ~/.xsession.errors, probably a result of what xrandr shows.

=== new config Configuration ===
Clone: false
Output: Unknown attached to default
status: on
width: 1280
height: 800
rate: 76
primary: true
position: 0 0
=== Applying Configuration Configuration ===
Clone: false
Output: Unknown attached to default
status: on
width: 1280
height: 800
rate: 76
primary: true
position: 0 0

/usr/sbin/hwinfo --gfxcard
08: PCI 02.0: 0300 VGA compatible controller (VGA)
[Created at pci.319]
Unique ID: _Znp.u4GoGlTTvQ4
SysFS ID: /devices/pci0000:00/0000:00:02.0
SysFS BusID: 0000:00:02.0
Hardware Class: graphics card
Model: “Intel Arrandale Integrated Graphics Controller”
Vendor: pci 0x8086 “Intel Corporation”
Device: pci 0x0046 “Arrandale Integrated Graphics Controller”
SubVendor: pci 0x17aa “Lenovo”
SubDevice: pci 0x21c1
Revision: 0x02
Memory Range: 0xf2000000-0xf23fffff (rw,non-prefetchable)
Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable)
I/O Ports: 0x1800-0x1807 (rw)
IRQ: 16 (no events)
I/O Ports: 0x3c0-0x3df (rw)
Module Alias: “pci:v00008086d00000046sv000017AAsd000021C1bc03sc00i00”
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: #8

xrandr -q
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1280 x 800, current 1280 x 800, maximum 1280 x 800
default connected 1280x800+0+0 0mm x 0mm
1280x800 76.0*
1440x900_75.00 (0x13f) 136.8MHz
h: width 1440 start 1536 end 1688 total 1936 skew 0 clock 70.6KHz
v: height 900 start 903 end 909 total 942 clock 75.0Hz

I re-installed opensuse 12.2 from the original DVD, and upon boot, both LCD and external VGA worked fine.

Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 304mm x
190mm
1440x900 60.1*+ 49.3
1024x768 60.0
800x600 60.3 56.2
640x480 59.9
VGA1 disconnected 1440x900+0+0 (normal left inverted right x axis y axis) 0mm x
0mm
1440x900_75.00 75.0*
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
0.929788] intel_idle: MWAIT substates: 0x1120

I then enabled the update repos, and updated with zypper, which I’ve done in the past on several occasions, with great success.

however; after this update - the issue returned.

What I’m missing is exactly how xrand gets the devices VGA1 and LVDS1 - the /var/log/Xorg.0.log states

12.705] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.

If anyone has any info on how xrandr learns the devices, I’d appreciate it, the latest 12.2 updates seem to cause this only on this PC
with this chipset. I’m now playing with intel drivers, and will report back.

#12

What I’m missing is exactly how xrand gets the devices VGA1 and LVDS1 - the /var/log/Xorg.0.log states

12.705] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.

If anyone has any info on how xrandr learns the devices, I’d appreciate it, the latest 12.2 updates seem to cause this only on this PC
with this chipset. I’m now playing with intel drivers, and will report back.

It (udev) replies on the driver to correctly report the info via sysfs, so there is a likely regression here. You should submit a bug report.