Re: SOLVED: 1400x1050 on a Dell 510m

2004-05-30 Thread Alessandro Temil
Hi,
I succeded in mixing Alain's and 1280patch code and setting 1400x1050 
mode on an acer TM661 with bios v.3a19.
The brutal and still unpolished mix can be found here:

http://www.temil.com/855resolution.c
It looks like video bioses below build 3 prefer 1280 patch-style code 
for setting the modeline, but plain 1280patch segfaulted on my machine 
so i had to ibridate the two patches.

regards,
Alessandro
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: i810 driver 1400x1050 problem -- bios replacement

2004-04-14 Thread Alessandro Temil
S Streif wrote:

I tried it on my Acer TM661LCI, without success. XWindow starts without any
error message and I can see the trash bin icon.
However, the trash icon is very big and the screen is flickering and is
fuzzy.
I tried with different resolutions -- no difference.
It might be necessary to modify the video bios with the vbios tool. Because it
is written in the driver's info file
( ftp://download.intel.com/design/intarch/SWSUP/IEGDLinux.htm ):
Please be sure to download the Video BIOS as well.

Any ideas?

Bye,
Stefan
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
I tried those drivers on my Acer TM661Lci but it was a no-go.
I patched kernel 2.4.24 sources with those provided by Intel, and 
followed all the instructions on the RELNOTES file.
I also set the PrimaryPort option on LVDS as read on this thread but 
all i got was dark screen.
PrimaryPort option seems to have some effect as it causes the screen 
to blink before turning black again.

Anyone succeded with this driver?

Regards,
Alessandro Temil
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: i810 driver 1400x1050 problem -- bios replacement

2004-04-14 Thread Alessandro Temil
Btw, i post the XFree86.0.log i got using the driver.
It looks like everything is working, i don't see any fatal error 
message, but as i stated before the screen remains blank.

Regards,

Alessandro Temil

XFree86 Version 4.3.0
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.20 i686 [ELF] 
Build Date: 01 March 2003
Before reporting problems, check http://www.XFree86.Org/
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/XFree86.0.log, Time: Wed Apr 14 15:55:42 2004
(==) Using config file: /etc/X11/XF86Config
(==) ServerLayout XFree86 Configured
(**) |--Screen Screen0 (0)
(**) |   |--Monitor Monitor0
(**) |   |--Device Card0
(**) |--Input Device Mouse0
(**) |--Input Device Keyboard0
(==) Keyboard: CustomKeycode disabled
(**) |--Input Device UsbMouse
(**) FontPath set to 
/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/
(**) RgbPath set to /usr/X11R6/lib/X11/rgb
(**) ModulePath set to /usr/X11R6/lib/modules
(++) using VT number 7

(WW) Open APM failed (/dev/apm_bios) (No such device)
(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.2
XFree86 Video Driver: 0.6
XFree86 XInput driver : 0.4
XFree86 Server Extension : 0.2
XFree86 Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: bitmap
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor=The XFree86 Project
compiled for 4.3.0, module version = 1.0.0
Module class: XFree86 Font Renderer
ABI class: XFree86 Font Renderer, version 0.4
(II) Loading font Bitmap
(II) LoadModule: pcidata
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor=The XFree86 Project
compiled for 4.3.0, module version = 1.0.0
ABI class: XFree86 Video Driver, version 0.6
(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,3580 card 1025,0035 rev 02 class 06,00,00 hdr 80
(II) PCI: 00:00:1: chip 8086,3584 card 1025,0035 rev 02 class 08,80,00 hdr 00
(II) PCI: 00:00:3: chip 8086,3585 card 1025,0035 rev 02 class 08,80,00 hdr 80
(II) PCI: 00:02:0: chip 8086,3582 card 1025,0035 rev 02 class 03,00,00 hdr 80
(II) PCI: 00:02:1: chip 8086,3582 card 1025,0035 rev 02 class 03,80,00 hdr 80
(II) PCI: 00:1d:0: chip 8086,24c2 card 1025,0035 rev 03 class 0c,03,00 hdr 80
(II) PCI: 00:1d:1: chip 8086,24c4 card 1025,0035 rev 03 class 0c,03,00 hdr 00
(II) PCI: 00:1d:2: chip 8086,24c7 card 1025,0035 rev 03 class 0c,03,00 hdr 00
(II) PCI: 00:1d:7: chip 8086,24cd card 1025,0035 rev 03 class 0c,03,20 hdr 00
(II) PCI: 00:1e:0: chip 8086,2448 card , rev 83 class 06,04,00 hdr 01
(II) PCI: 00:1f:0: chip 8086,24cc card , rev 03 class 06,01,00 hdr 80
(II) PCI: 00:1f:1: chip 8086,24ca card 1025,0035 rev 03 class 01,01,8a hdr 00
(II) PCI: 00:1f:3: chip 8086,24c3 card 1025,0035 rev 03 class 0c,05,00 hdr 00
(II) PCI: 00:1f:5: chip 8086,24c5 card 1025,0035 rev 03 class 04,01,00 hdr 00
(II) PCI: 00:1f:6: chip 8086,24c6 card 1025,0035 rev 03 class 07,03,00 hdr 00
(II) PCI: 02:02:0: chip 14e4,4401 card 1025,0035 rev 01 class 02,00,00 hdr 00
(II) PCI: 02:04:0: chip 8086,1043 card 8086,2527 rev 04 class 02,80,00 hdr 00
(II) PCI: 02:06:0: chip 1217,7113 card 3401, rev 20 class 06,07,00 hdr 82
(II) PCI: 02:06:1: chip 1217,7113 card 3c01, rev 20 class 06,07,00 hdr 82
(II) PCI: 02:07:0: chip 104c,8026 card 1025,0035 rev 00 class 0c,00,10 hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,4), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1  0   0x - 0x (0x1) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1  0   0x - 0x (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1  0   0x - 0x (0x0) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 2: bridge is at (0:30:0), (0,2,2), BCTRL: 0x0004 (VGA_EN is cleared)
(II) Bus 2 I/O range:
[0] -1  0   0x3000 - 0x30ff (0x100) IX[B]
[1] -1  0   0x3400 - 0x34ff (0x100) IX[B]
[2] -1  0   0x3800 - 0x38ff (0x100) IX[B]
[3] -1  0   0x3c00 - 0x3cff (0x100) IX[B]
(II) Bus 2 non-prefetchable memory range:
[0] -1  0   0xe020 - 0xe07f (0x60) MX[B]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(II) PCI-to-CardBus bridge:
(II

Re: i855 and 1400x1050

2003-09-09 Thread Alessandro Temil
Thomas Winischhofer wrote:
Alessandro Temil wrote:

Egbert Eich wrote:

   David
  Here you are, i attached both i810 and vesa driver XFree86.0.log.
  (by the way, i'm new of this mailing list, if it doesn't allow 
messages   with attachments i'll repost them inlined asap.)
This moring i wrote to intel asking for the specifications, i 
hope to   get a reply soon.
 
Neither the VESA nor the i8xx driver lists any 1400x1050 mode.

Egbert.
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


I know, that's why we need to program directly the video chip, as the 
windows driver does.


Seems so. I found no trace of a 1400x1050 mode in the BIOS. However, it 
seems to support different panel types (brands, models) of that very 
resolution.

If the reason for not implementing a mode for the native resolution in 
the BIOS is that the chip can be connected to many different video 
bridges, this is simply dumb. That way they need a huge windows driver, 
taking care of all that, which furthermore needs to be updated 
permanently if a new machine comes out... SiS folks haven't updated 
their Windows driver since February, and it works with about every 
machine in existance (due to the BIOS of all machines containing info on 
all supported modes for their host machine)

A register dump from a windows driver would be the only way, I guess...

Thomas

Do you have any suggestion for what program/debugger/whatelse to use to 
get this dump?

Alessandro

___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: i855 and 1400x1050

2003-09-06 Thread Alessandro Temil
Thomas Winischhofer wrote:
Alessandro Temil wrote:

David Dawes wrote:

On Fri, Sep 05, 2003 at 11:25:35AM -0700, Tim Roberts wrote:

On Fri, 05 Sep 2003 20:04:19 +0200, Alessandro Temil wrote:


Christian Zietz wrote:

The problem is: The current i810 driver does not only read the 
available
resolutions from the BIOS but also uses the BIOS to set the video 
mode.
So if the BIOS doesn't know of 1400x1050, it won't set it.
I think there are two solutions:
- Change the BIOS to know of 1400x1050. This should be easy for
manufacturer of the notebook but considerably harder than my 855patch
(for the video memory issue) for anyone else.


It is possible that the BIOS actually knows the mode, but has no VESA 
number for it. I have seen this at least on SiS hardware: SiS BIOSes 
maintain two mode number lists, one with internal mode numbers, one for 
VESA mode numbers. As the i810 BIOS, it has no VESA number for 1400x1050.

A closer look at the BIOS would perhaps help... if it turns out the BIOS 
has in internal mode number, one could change the mode switching from 
VESA to (direct) int10 and use the internal mode number(s).

Thomas

I'm not sure to have the necessary knowledge, but may give a try, do you 
know any good bios dumper/disassembler that runs under linux that you 
would suggest for this task?

If someone else with more experience on this should want to help, the 
bios can be downloaded from acer support site and the laptop model is 
travelmate 661LCi (but i know at least dell inspiron 500m and latitude 
D400 are affected by the same problem, so their bioses should be good too)

Alessandro

___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


i855 and 1400x1050

2003-09-05 Thread Alessandro Temil
Hi everybody

	I'm a linux Xfree86 user, and my laptop has an LCD screen with 
1400x1050 native resolution. the internal video chipset is an intel 
855GM. After some hours of trying i figured out there's no way of 
getting that resolution under XFree86, due to the fact that the current 
i810 driver reads the available resolutions from the bios and completely 
ignores the modelines in the XF86Config file.

I'm inquiring if there is any plan to overcome this limitation.

I'm a cs student and have some knowledge in system programming, so i'm 
available to help the developent of this 'patch', should this be needed, 
and i'm also available to test/debug beta versions.

I'd be grate to be contacted by people that are actually taking care of 
the i810 driver developement.

Best Regards

Alessandro Temil

___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: i855 and 1400x1050

2003-09-05 Thread Alessandro Temil
Christian Zietz wrote:
Hi,

Alessandro Temil schrieb:


	I'm a linux Xfree86 user, and my laptop has an LCD screen with 
1400x1050 native resolution. the internal video chipset is an intel 
855GM. After some hours of trying i figured out there's no way of 
getting that resolution under XFree86, due to the fact that the current 
i810 driver reads the available resolutions from the bios and completely 
ignores the modelines in the XF86Config file.


The problem is: The current i810 driver does not only read the available
resolutions from the BIOS but also uses the BIOS to set the video mode.
So if the BIOS doesn't know of 1400x1050, it won't set it.
I think there are two solutions:
- Change the BIOS to know of 1400x1050. This should be easy for
manufacturer of the notebook but considerably harder than my 855patch
(for the video memory issue) for anyone else.
I know this but at the moment i'm getting weak support from the 
manufacturer (acer), as they say they give no support to linux
(my try to explain the difference that passes from a linux driver bug 
and a bios bug had little effect, as you can imagine)
- Rewrite the i810 driver so it bypasses the BIOS like the Windows
driver does. I'm not aware whether Intel would provide the required
documentation to the the open source community.
This was the thing i'm inquiring on. Intel seemed to be more 
collaborative, they promptly replied that the problem was submitted to 
the software engineers, but after that i had no more news. I'll write 
them asking for the documentation, i don't think there is any broken 
industrial secret with publishing the correct register addresses that 
drive the video mode change, i hope to get some response soon.

Best Regards

Alessandro

___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel