Bug 136003 - i810 driver refuses 1400x1050 until touched by sax2
Summary: i810 driver refuses 1400x1050 until touched by sax2
Status: VERIFIED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: SaX2 (show other bugs)
Version: Alpha 3
Hardware: i586 Linux
: P2 - High : Normal (vote)
Target Milestone: ---
Assignee: Forgotten User ZhJd0F0L3x
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-30 08:29 UTC by Marian Jancar
Modified: 2007-06-05 11:20 UTC (History)
2 users (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
logs and configs (21.76 KB, application/x-bzip2)
2005-11-30 08:31 UTC, Marian Jancar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marian Jancar 2005-11-30 08:29:24 UTC
After boot it starts with 1280x1024 as maximal resolution, X server restart doesn't help, only after running sax2 (that doesn't modify the config!) and X server restart it allows the native 1400x1050. I suspect it to be something in the sax2 detection routines what enables the resolution, and strangely the BIOS knows it prior to running the sax, there is no need to reprogam it using 855resolution.

fujiwara-no-sai:/etc/X11/log # 855resolution -l
855resolution version 0.4, by Alain Poirier

Chipset: Unknown (id=0x25908086)
VBIOS type: 2
VBIOS Version: 1220

Mode 30 : 640x480, 8 bits/pixel
Mode 32 : 800x600, 8 bits/pixel
Mode 34 : 1024x768, 8 bits/pixel
Mode 38 : 1280x1024, 8 bits/pixel
Mode 3a : 1600x1200, 8 bits/pixel
Mode 3c : 1400x1050, 8 bits/pixel
Mode 41 : 640x480, 16 bits/pixel
Mode 43 : 800x600, 16 bits/pixel
Mode 45 : 1024x768, 16 bits/pixel
Mode 49 : 1280x1024, 16 bits/pixel
Mode 4b : 1600x1200, 16 bits/pixel
Mode 4d : 1400x1050, 16 bits/pixel
Mode 50 : 640x480, 32 bits/pixel
Mode 52 : 800x600, 32 bits/pixel
Mode 54 : 1024x768, 32 bits/pixel
Mode 58 : 1280x1024, 32 bits/pixel
Mode 5a : 1600x1200, 32 bits/pixel
Mode 5c : 1400x1050, 32 bits/pixel
fujiwara-no-sai:/etc/X11/log # lspci
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 04)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 04)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d4)
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 04)
00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 04)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 04)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 04)
06:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
06:04.0 Network controller: Intel Corporation PRO/Wireless 2915ABG MiniPCI Adapter (rev 05)
06:05.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 8b)
06:05.1 Class 0805: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 11)
fujiwara-no-sai:/etc/X11/log # lspci -n
00:00.0 Class 0600: 8086:2590 (rev 03)
00:02.0 Class 0300: 8086:2592 (rev 03)
00:02.1 Class 0380: 8086:2792 (rev 03)
00:1d.0 Class 0c03: 8086:2658 (rev 04)
00:1d.1 Class 0c03: 8086:2659 (rev 04)
00:1d.7 Class 0c03: 8086:265c (rev 04)
00:1e.0 Class 0604: 8086:2448 (rev d4)
00:1e.2 Class 0401: 8086:266e (rev 04)
00:1e.3 Class 0703: 8086:266d (rev 04)
00:1f.0 Class 0601: 8086:2641 (rev 04)
00:1f.1 Class 0101: 8086:266f (rev 04)
00:1f.3 Class 0c05: 8086:266a (rev 04)
06:01.0 Class 0200: 10ec:8139 (rev 10)
06:04.0 Class 0280: 8086:4223 (rev 05)
06:05.0 Class 0607: 1180:0476 (rev 8b)
06:05.1 Class 0805: 1180:0822 (rev 11)
Comment 1 Marian Jancar 2005-11-30 08:31:12 UTC
Created attachment 59063 [details]
logs and configs
Comment 2 Stefan Dirsch 2005-11-30 09:26:41 UTC
Could you attach /etc/sysconfig/videobios? Thanks.

I cannot find a BIOS 1400x10250 mode in 1280-Xorg.0.log*, only in 1400-Xorg.0.log. I assume 1400-Xorg.0.log is the one after calling sax2. For whatever reasons the i810 driver only detects a valid 1400x1050 mode, when 855resolution has been used to overwrite Mode 3c.
Comment 3 Marian Jancar 2005-11-30 09:49:54 UTC
You are right, sax2 overwrites the resolution, I didn't realize before.

fujiwara-no-sai:~ # cat /etc/sysconfig/videobios
## Path:        System/Hardware/Graphicscard
## Description: Additional options for graphics cards
## Type:        yesno
## Default:     no
#
# Should the Intel(R) video BIOS be patched to let the X Server run with
# resolutions unknown to the BIOS? Warning, this is potentially dangerous,
# read the documentation in /usr/share/doc/packages/855resolution.
#
VIDEOBIOS_PATCH="no"

## Type:        string
## Default:
#
# The options passed to 855resolution, usually 3 numbers:
# the video mode to patch, X and Y resolution.
#
VIDEOBIOS__PARAMETERS=""
fujiwara-no-sai:~ #


fujiwara-no-sai:~ # 855resolution -l
855resolution version 0.4, by Alain Poirier

Chipset: Unknown (id=0x25908086)
VBIOS type: 2
VBIOS Version: 1220

Mode 30 : 640x480, 8 bits/pixel
Mode 32 : 800x600, 8 bits/pixel
Mode 34 : 1024x768, 8 bits/pixel
Mode 38 : 1280x1024, 8 bits/pixel
Mode 3a : 1600x1200, 8 bits/pixel
Mode 3c : 1920x1440, 8 bits/pixel
Mode 41 : 640x480, 16 bits/pixel
Mode 43 : 800x600, 16 bits/pixel
Mode 45 : 1024x768, 16 bits/pixel
Mode 49 : 1280x1024, 16 bits/pixel
Mode 4b : 1600x1200, 16 bits/pixel
Mode 4d : 1920x1440, 16 bits/pixel
Mode 50 : 640x480, 32 bits/pixel
Mode 52 : 800x600, 32 bits/pixel
Mode 54 : 1024x768, 32 bits/pixel
Mode 58 : 1280x1024, 32 bits/pixel
Mode 5a : 1600x1200, 32 bits/pixel
Mode 5c : 1920x1440, 32 bits/pixel
fujiwara-no-sai:~ # sax2
SaX: initialization already done
SaX: call [ sax2 -r ] if your system has changed !

SaX: startup
SaX: importing current configuration...
fujiwara-no-sai:~ # 855resolution -l
855resolution version 0.4, by Alain Poirier

Chipset: Unknown (id=0x25908086)
VBIOS type: 2
VBIOS Version: 1220

Mode 30 : 640x480, 8 bits/pixel
Mode 32 : 800x600, 8 bits/pixel
Mode 34 : 1024x768, 8 bits/pixel
Mode 38 : 1280x1024, 8 bits/pixel
Mode 3a : 1600x1200, 8 bits/pixel
Mode 3c : 1400x1050, 8 bits/pixel
Mode 41 : 640x480, 16 bits/pixel
Mode 43 : 800x600, 16 bits/pixel
Mode 45 : 1024x768, 16 bits/pixel
Mode 49 : 1280x1024, 16 bits/pixel
Mode 4b : 1600x1200, 16 bits/pixel
Mode 4d : 1400x1050, 16 bits/pixel
Mode 50 : 640x480, 32 bits/pixel
Mode 52 : 800x600, 32 bits/pixel
Mode 54 : 1024x768, 32 bits/pixel
Mode 58 : 1280x1024, 32 bits/pixel
Mode 5a : 1600x1200, 32 bits/pixel
Mode 5c : 1400x1050, 32 bits/pixel
fujiwara-no-sai:~ #
Comment 4 Stefan Dirsch 2005-11-30 10:06:50 UTC
Yes.

-Mode 3c : 1920x1440, 8 bits/pixel
+Mode 3c : 1400x1050, 8 bits/pixel
[...]
-Mode 4d : 1920x1440, 16 bits/pixel
+Mode 4d : 1400x1050, 16 bits/pixel

[...]
-Mode 5c : 1920x1440, 32 bits/pixel
+Mode 5c : 1400x1050, 32 bits/pixel

Seems all the three modes for 1400x1050 in 8/16/32bit color deppth are rewritten by 855resolution.

But IMHO SaX2 should have written VIDEOBIOS_PATCH/VIDEOBIOS__PARAMETERS in /etc/sysconfig/videobios as well.
Comment 5 Marcus Schaefer 2005-11-30 12:00:19 UTC
VIDEOBIOS__PARAMETERS is a bug it must be named 

  VIDEOBIOS_PARAMETERS=...

you can fix this yourself by editing the file /etc/sysconfig/videobios.
The bug has been introduced and fixed by Stefean Seyfried seife@suse.de :-)
Comment 6 Marian Jancar 2005-11-30 12:45:16 UTC
It would be also nice to be able to set more resolutions (more color depts for example), if I understand it correctly VIDEOBIOS_PARAMETERS is just passed to the 855resolution and so it can set just one.

Another nice thing would be to add the capability to reprogram the modes to the i810 driver and to the kernel intelfb, and the cpability to actualy switch the mode on the 915 do the intelfb. As this is quite obvious idea, is there anybody working on that, or are there any reasons why nodody did it so far? I would really like to get this working :)
Comment 7 Stefan Dirsch 2005-11-30 13:25:47 UTC
Please don't mix up bugreports with feature requests. Thanks. Closing as fixed.
Comment 8 Marian Jancar 2005-11-30 14:08:17 UTC
Thats not request, just a thought and question. I will probably look into this myself if I find some time, it doesn't seem difficult, I just want to investigate the field, I am new into this as I have got the notebook few days ago.