Bug 144742

Created attachment 64450 [details]
hwinfo -gfxcard [run under SUSE 10.0]

Please also attach your xorg.conf and the yast logs.

Created attachment 64564 [details]
xorg.conf and YaST logs

Sorry I forgot: Please attach the xorg-log (/var/log/Xorg.0.log)

Created attachment 64648 [details]
XOrg logfile

I'm not sure but some of the messages seem familiar.
Stefan: Is this a known issue?

> (EE) Failed to load module "glx" (module does not exist, 0)

This is *not* fatal and can be ignored. The logfile looks ok. The Xserver start didn't fail. I wonder why the "vesa" has been used. AFAIK Intel 865G supports kernel framebuffer. Therefore "fbdev" should have been used instead.
Our YaST team needs to investigate, why the installation didn't start in X11 mode.

Marcus: Can you help here? If not, please reassign it back to us or to someone who can help, thanks.

If you don't mind provide the log file:

  /var/log/YaST2/y2start.log

Thanks

Created attachment 64964 [details]
y2start.log

The log said:

Stage [call]: ===================================
    |-- No Framebuffer available: Using vesa driver

why is there no framebuffer available on this box ?
next is:

Stage [call]: ========================
    |-- Wished medium is: QT
    |-- Selected medium is: QT
    |-- TestX: color or dimensions doesn't fit
    |-- X-Server couldn't be started, falling back to ncurses

for details why the X-Server couldn't start you should provide a
X11 log file from that stage: /var/log/Xorg.*.log
I assume a vesa driver problem here which can be avoided by booting
with active framebuffer (vga=0x<mode number>)

Hi,
I have provided the Xorg.0.log already. I will test the vga option (vga=317 for this box) and provide a new log.

yes but the log you attached seems to be from a working server

(II) Setting vga for screen 0
...

this means the server starts, so there is no information from a
server which couldn't start ??

Created attachment 65001 [details]
new Xorg.0.log (setup started with vga=0x317)

Maybe the X11 server crashed directly after starting like Stefan wrote it before? It looks like there was a X server starting.

- the log is still vesa based, so it seems there is no framebuffer
  available in 1024x768 which I don't understand because the VESA BIOS
  has that mode... strange hardware ? 

- if the server crashed I normally would expect some signal message at
  the end of the log file, but in this case the log didn't show any error

maybe this is a vesa driver bug ?
Stefan ?

gfx hardware:

Hardware Class: graphics card
Model: "Dell 865 G"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x2572 "865 G"
SubVendor: pci 0x1028 "Dell"
SubDevice: pci 0x0151 
Revision: 0x02 

I can't believe this all. Maybe you did boot in the installed system with the vga option?

Probably I made a mistake, because if I test it now and type vga=0x317 I get an error "You passed an undefined mode number". Under 10.0 the bootloader shows the option "1024x786", "800x600", "VESA" and "Textmode". Under 10.1 it shows only "VESA" and "Textmode".

Great. This means that this problem is unrelated to X11. :-)

Not exactly. :-)

Though i865 does does support a framebuffer, the BIOS is normally (at least with Dell) configured for 832k video memory, which is not enough for
anything useful.

10.0 listed 8bit modes, too, if no 16bit modes were found. But that was wrong
as yast doesn't support 8bit anyway.

So, the way to go is via vesa driver. Maybe it has difficulties with
the low memory, too?

Ouch. That's bad news. :-(

Just tested and yast works with 8 bit after all. I've added 8 bit fb modes.

Good news, will beta3 contain this 8bit framebuffer?

Yes. Until then boot with vga=0x305.

Okay, vga=0x305 works and X starts. Thanks!