Bug 610352

Created attachment 365794 [details]
System description

/var/log/boot.msg with kernel bootup log
dmidecode
hwinfo
/proc/cpuinfo
/proc/interrupts

Created attachment 365796 [details]
/var/log/Xorg.0.log from the factory installer

Minor correction, with i915.modeset=0 factory works, but that's really a hack, isn't it.

Created attachment 365802 [details]
Log from boot with KMS enabled, and defective Xorg

Optional comment: I was expecting the optional criss-cross pattern to show up, but it looks like Xorg is configured to use a black background these days. Anyway, I started xterm on the same $DISPLAY to confirm that Xorg outputs a picture - or not.

So apparently at least fbdev driver works. Could you try with 'nomodeset' and "intellegacy" driver in /etc/X11/xorg.conf.d/50-device.conf?

Factory Net-Installer:

nomodeset + intel: same as i915.modeset=0 (works)

modeset + intellegacy: there is no 50-device.conf inside the image of /factory/repo/oss/boot/i386/root.


openSUSE 11.2 Xorg 7.5_1.8.0 + xorg-x11-driver-video-intel-legacy-2.9.1-1.1.i586:

nomodeset + intel: works

nomodeset + intellegacy: kills the machine (hard lockup, no interrupts enabled)

modeset + intellegacy: screen remains without graphics

(In reply to comment #6)
> Factory Net-Installer:
> 
> nomodeset + intel: same as i915.modeset=0 (works)

You mean nomodeset + fbedev (nomodeset + intel is not possible since intel
requires KMS).

> modeset + intellegacy: there is no 50-device.conf inside the image of
> /factory/repo/oss/boot/i386/root.

No idea what you're talking about. I'm talking about an installed system. During installation fbdev is used anyway. You don't talk about a LiveCD here, do you? At least I didn't see it mentioned anywhere.

> openSUSE 11.2 Xorg 7.5_1.8.0 +
> xorg-x11-driver-video-intel-legacy-2.9.1-1.1.i586:

There is no need to run intellegacy on openSUSE 11.2, since the intel driver
on 11.2 doesn't required KMS yet.

>You mean nomodeset + fbedev

Yes. Or actually VESA(2), since that's what shows up in Xorg.0.log a lot.

>I'm talking about an installed system.
>During installation fbdev is used anyway.

All attached logs here are from the installer _only_. (I didn't get to install it yet because I ran into this issue.) No LiveCD.

* This is /factory/repo/oss/boot/i386/{linux,initrd} PXE-booted
* selecting Settings > "Shell Enabled Before YaST"
* either continue with yast, or manually start X from sh to trigger.

So you disabled kernel framebuffer and stumble across a not-working vesa driver?

Does installation work with fbdev driver (by adding kernel framebuffer)?

By default, the system boots in 80x25 text mode. I suppose this is because only the CD-ROM bootloader defaults to passing vga=0x31X behind my back.

1. With KMS, the kernel switches to graphics mode once udev gets to load the kernel module. The mode looks like 1280x1024, but text is confined to an 80x25/80x30 area in the upper left. The installer uses the "intel" driver, as evidenced by attachment to comment #4. This fails to produce a picture.

2. With i915.modeset=0 or nomodeset, boot proceeds in 80x25 mode until yast2, where the Factory installer/Xorg chooses VESA (with an appropriate resolution; was either 1024x768 or 1280), as seen in attachment to comment #2. This works.

3. Booting with vga=0x317 nomodeset: kernel switches to graphics mode on early boot. /var/log/Xorg.0.log indicates Xorg is using FBDEV(0). Looks like 1024x768. This works too.

4. Booting with vga=0x317: kernel switches to graphics mode on early boot (vesafb) 1024x768. Once udev loads, everything goes exactly like (1). Fails.

(In reply to comment #11)
> By default, the system boots in 80x25 text mode. I suppose this is because 
> only the CD-ROM bootloader defaults to passing vga=0x31X behind my back.

Sure, if you configure PXE boot way ...

> 1. With KMS, the kernel switches to graphics mode once udev gets to load the
> kernel module. The mode looks like 1280x1024, but text is confined to an
> 80x25/80x30 area in the upper left. The installer uses the "intel" driver, as
> evidenced by attachment to comment #4. This fails to produce a picture.

No idea why we now have KMS during installation active. We didn't want this.
Also apparently the /etc/X11/xorg.conf is not available during installation,
which should make sure that fbdev driver is used instead of the native driver.
Not your fault, of course ...
 
> 2. With i915.modeset=0 or nomodeset, boot proceeds in 80x25 mode until yast2,
> where the Factory installer/Xorg chooses VESA (with an appropriate resolution;
> was either 1024x768 or 1280), as seen in attachment to comment #2. This works.

Ok. So vesa driver does work.
 
> 3. Booting with vga=0x317 nomodeset: kernel switches to graphics mode on early
> boot. /var/log/Xorg.0.log indicates Xorg is using FBDEV(0). Looks like
> 1024x768. This works too.

So fbdev driver does work as well.

> 4. Booting with vga=0x317: kernel switches to graphics mode on early boot
> (vesafb) 1024x768. Once udev loads, everything goes exactly like (1). Fails.

KMS already break the graphics. fbdev driver cannot work any longer after
KMS is initialized.

I see 3 issues here:

1) KMS doesn't work on Intel 855GM.
2) KMS during installation is our default.
3) /etc/X11/xorg.conf is no longer available during installation.

I'll try to verify these issues here.

Mixed results here. Indeed KMS gets enabled on intel, i.e. intel-agp, i915, drm, drm_kms_helper gets loaded, but as driver "fbdev" is used (/etc/X11/xorg.conf exists and specifies fbdev as first driver option). Same applies to NVIDIA (nouveau, see also http://en.opensuse.org/Bugs:Most_Annoying_Bugs_11.3_dev) and ATI (radeon).

I asked Steffen to remove the modules below kernel/drivers/gpu/drm (apart from drm, which is apparently required by vboxvideo).

Hmm. /lib/udev/rules.d/79-kms.rules should already make sure that no DRM modules
are loaded.

(In reply to comment #14)
> Hmm. /lib/udev/rules.d/79-kms.rules should already make sure that no DRM
> modules are loaded.

(which is part of initrd from installation)

From which package is this rule?

(In reply to comment #17)
> From which package is this rule?

--> udev (it's already available during installation)

(In reply to comment #13)
> I asked Steffen to remove the modules below kernel/drivers/gpu/drm (apart from
> drm, which is apparently required by vboxvideo).

That's now submitted to openSUSE:Factory.

40928  State:new     By:snwint       When:2010-05-31T18:41:20
        submit: system:install:head/installation-images -> 
                openSUSE:Factory       
        Descr:  - libopenssl moved to /lib*
                - sndirsch: remove kms support (bnc #610352)

I cannot reproduce the bug that the native driver is used during
installation. fbdev is always used (verified with intel, nvidia, and radeon
graphics).