Re: SOLVED: 1400x1050 on a Dell 510m

2004-06-13 Thread Alain Poirier
855resolution v0.3 is released.

I tried to put a better vbios detection routine in it. And,
if it doesn't detect the correct vbios type, then the new option
'-f x' permits to force it.

Regards,

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


Re: SOLVED: 1400x1050 on a Dell 510m

2004-05-30 Thread Alain Poirier
Hi,

So, there are at least 2 kinds of different VBIOS structures :
the more common "type 1" structure was described by Andrew Tipton,
(http://www.leog.net/fujp_forum/topic.asp?TOPIC_ID=5371)
and the "type 2" is what the 0.1 version of 855resolution knows
how to patch (VBIOS structure of, at least, the Dell 510m).

The 0.2 version of 855resolution is now available. I modularized
it around plugins to be able to patch differents VBIOS.
I don't know how to compute the several resolution values of
the "type 1". If you know how, please, look into the file
plugins/plugin1.c to put the formulas. So, for the moment, this
0.2 version is only a test. But perhaps it could work because the
LCD screens don't use the different frequence values.

Can you test it (http://perso.wanadoo.fr/apoirier/) ?

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


Re: SOLVED: 1400x1050 on a Dell 510m

2004-05-28 Thread Alain Poirier
Christian Zietz wrote:
> Sounds impressive. But I think it won't work on a Dell Inspiron 500m
> (V-BIOS 2945). My 500m doesn't have a 1400x1050 display to test but when
> running "855resolution -l" I get a list similar to the one L. Jensen posted.
>
> I did a little debugging and it seems like the list of modes
> 855resolution looks for exists in my video BIOS version, too. At least
> the mode numbers and the bits/pixel values are correct.
Yes, perhaps the bios structures are not so differents. As you say, the
mode structures have the same mode, bits/pixels fields and also length
(5 bytes). So, as only 3 bytes left, I don't see how they couldn't be
a pointer of some type to the resolution structure.

> But the pointers in that list that are supposed to point to the resolution
> data are pointing to nonsensical values instead. I couldn't figure out how
> to fix this.
In fact I don't think they are pointing to nonsensical values : if you look
at the L. Jensen's mail, we can see that resolutions stay coherentes. For
example the modes 30, 41 and 51, which are all 640x400, are _always_ displayed
with the (bogus) resolution of 3856x1536. The pointers for these modes are
the same.

So, to me, the pointers are correct but the resolution bytes (nibbles in fact) 
are not the same than on my 510m.

To find the resolution byte, I dumped the differents structure for all the
possible resolution and look at 1/ where the resolution x and y values, in
hexa, could be 2/ how 2 different resolutions structure difer

> Another question: May I put a link to the 855resolution page on my
> 8x5patch/855wrap web page?
Yes. No problem (as I even borrowed your naming scheme ;)

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


SOLVED: 1400x1050 on a Dell 510m

2004-05-28 Thread Alain Poirier
Hi,

I just finished to write a little soft to patch
the VBIOS on a Dell 510m and to get the 1400x1050
resolution.

I don't know if it works on other systems.

The soft '855resolution' can be found at
http://perso.wanadoo.fr/apoirier/

Hope that help.

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


Re: i855GM: New BIOS breaks i810-driver - solved

2004-02-20 Thread Alain Poirier
Le vendredi 20 Février 2004 01:33, Alan Hourihane a écrit :
> Alain,
>
> Can you try the int10 emulator ?
>
> To do this, (re)move this file out of the way.
>
> /usr/X11R6/lib/modules/linux/libint10.a
>
> Then XFree86 will use
>
> /usr/X11R6/lib/modules/libint10.a
>
> Which is the emulator. Does it still lockup with that BIOS call ?

I tried and got the exact same lockup.

-

Section "Module"
Load"dbe"

SubSection  "extmod"
Option  "omit xfree86-dga"
EndSubSection

Load"type1"
Load"freetype"
Load"glx"
Load"dri"
Load"synaptics"
EndSection

Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"

#FontPath   "/usr/X11R6/lib/X11/fonts/local"
FontPath"/usr/X11R6/lib/X11/fonts/misc"
FontPath"/usr/X11R6/lib/X11/fonts/75dpi:unscaled"
FontPath"/usr/X11R6/lib/X11/fonts/100dpi:unscaled"
FontPath"/usr/X11R6/lib/X11/fonts/Type1"
#FontPath   "/usr/X11R6/lib/X11/fonts/CID"
#FontPath   "/usr/X11R6/lib/X11/fonts/Speedo"
FontPath"/usr/X11R6/lib/X11/fonts"
#FontPath   "/usr/X11R6/lib/X11/fonts/truetype"
FontPath"/usr/X11R6/lib/X11/fonts/TTF"
FontPath"/usr/local/share/fonts/TTF"
EndSection

Section "InputDevice"
Identifier  "Keyboard"
Driver  "keyboard"

Option  "AutoRepeat""500 30"


Option  "XkbRules"  "xfree86"
Option  "XkbModel"  "pc105"
Option  "XkbLayout" "fr"
#Option "XkbVariant""fr-latin1"
EndSection

Section "InputDevice"
Identifier  "Mouse"
Driver  "mouse"

Option  "Protocol"  "ImPS/2"
#Option "Device""/dev/input/mice
Option  "Device""/dev/misc/psaux"

Option  "Emulate3Buttons"
Option  "ZAxisMapping"  "4 5"
EndSection

Section "Monitor"
Identifier  "LCD"
EndSection

Section "Device"
Identifier  "Device"
Driver  "i810"

#VideoRam   32768
VideoRam8192
#Option "hw cursor" "off"
#Option "no_accel"
EndSection

Section "Screen"
Identifier  "Screen"
Device  "Device"
Monitor "LCD"

DefaultDepth 24

SubSection "Display"
Depth   24
Modes   "1280x1024"
EndSubsection
EndSection

Section "ServerLayout"
Identifier  "Main Layout"

Screen  "Screen"
InputDevice "Mouse" "CorePointer"
InputDevice "Keyboard" "CoreKeyboard"
EndSection

Section "DRI"
Mode0666
EndSection

-

This is a pre-release version of XFree86, and is not supported in any
way.  Bugs may be reported to [EMAIL PROTECTED] and patches submitted
to [EMAIL PROTECTED]  Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs).

XFree86 Version 4.3.0.1
Release Date: 15 August 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.6.3-love1 i686 [ELF] 
Build Date: 20 February 2004
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: Sat Feb 21 12:20:10 2004
(==) Using config file: "/etc/X11/XF86Config"
(==) ServerLayout "Main Layout"
(**) |-->Screen "Screen" (0)
(**) |   |-->Monitor "LCD"
(**) |   |-->Device "Device"
(**) |-->Input Device "Mouse"
(**) |-->Input Device "Keyboard"
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc105"
(**) XKB: model: "pc105"
(**) Option "XkbLayout" "fr"
(**) XKB: layout: "fr"
(==) Keyboard: CustomKeycode disabled
(WW) `fonts.dir' not found (or not valid) in "/usr/X11R6/lib/X11/fonts".
Entry deleted from font path.
(Run 'mkfontdir' on "/usr/X11R6/lib/X11/fonts").
(**) FontPath set to 
"/usr/X11R6/lib/X11/fonts/misc,/usr/X11R6/lib/X11/fonts/75dpi:unscaled,/usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/Type1,/usr/X11R6/lib/X11/fonts/TTF,/usr/local/share/fonts/TTF"
(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(==) ModulePath set to "/usr/X11R6/lib/modules"
Using vt 7
(--) using VT number 7

(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(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.1, module version = 1.0.0
Module class: XFree86 Font Renderer
ABI class: XFree86 Font Render

Re: i855GM: New BIOS breaks i810-driver - solved

2004-02-19 Thread Alain POIRIER
Hi,

> > Christian Zietz writes:
> > Hi,
> > 
> > as developer of 855patch I get a lot of feedback from people using
> > XFree86 on computers with i855GM graphics.
> > It seems like new notebooks by Dell feature a new video BIOS from Intel
> > (iirc Build 3066) which finally implements the int 0x10 0x5f11 function
> > to set the amount of video RAM and thus making 855patch obsolete.
> > 
> > But the i810-driver refuses to work on systems with that BIOS version. I
> > had several independent reports of users who just get a completely green
> > screen when starting XFree86. I had a look on a log file and found
> > nothing unusual. The XFree86 VESA driver however works but just in low
> > resolutions/color depths as there is no way to allocate more video RAM
> > there.
> > 
> > As I've been absent of this list: Is this already a known issue?
> > 
>
> I haven't heared anyting about this issue yet.
> The first question that comes to my mind is:
> What happens if a low resolution mode that works with VESA 
> is set on the i8xx driver?
>
> Egbert.

I've got this problem with the new Dell 510m model : with the normal i810
driver, we've got only a total green screen.

The problem comes from the call to INT 10h, 0x5f64 in the 
GetDisplayInfo() function. It never returns.

As this function is only informative, I commented out its call in
I830DetectDisplayDevice() (XFree86 4.3.0.1) :

...
static Bool
I830DetectDisplayDevice(ScrnInfoPtr pScrn)
{
   I830Ptr pI830 = I830PTR(pScrn);
   int pipe, n;
   DisplayType i;

#if 0
   for (i = 0; i < NumKnownDisplayTypes; i++) {
  if (GetDisplayInfo(pScrn, 1 << i, &pI830->displayAttached[i],
 &pI830->displayPresent[i],
 &pI830->displaySize[i].x2,
 &pI830->displaySize[i].y2)) {
 xf86DrvMsg(pScrn->scrnIndex, X_INFO,
"Display Info: %s: attached: %s, present: %s, size: "
"(%d,%d)\n", displayDevices[i],
BOOLTOSTRING(pI830->displayAttached[i]),
BOOLTOSTRING(pI830->displayPresent[i]),
pI830->displaySize[i].x2, pI830->displaySize[i].y2);
  }
   }
#endif

   pI830->configuredDevices = GetDisplayDevices(pScrn);
   if (pI830->configuredDevices == -1) {
  xf86DrvMsg(pScrn->scrnIndex, X_INFO,
 "Failed to detect active display devices\n");
  return FALSE;
   }
...

Now all is working fine (except the fact that the 1500x1040 resolution
is still not reconized by the bios).

I hope this help.

Regards

PS : not more need to use 855Patch with this bios.
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel