Re: Xorg and CueCat problems
Rick Knight schrieb: I have been trying for some time to get my PS/2 Cuecat device to work with Linux and X. Just last night I was able to determine that the problem seems to be with X and not with Linux. If I scan in an Xterm window or within my X app (Readerware) I get a bunch of beeps and sometimes a line feed. The CueCat sends Alt+F10 before sending data. Maybe something (X, window manager etc.) gets confused by a simulated Alt+F10 keypress. CU Christian -- Christian Zietz - CHZ-Soft - [EMAIL PROTECTED] WWW: http://www.chzsoft.com.ar/ PGP-Key-ID: 0x6DA025CA ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: Resolution problems with i810 driver, Intel 915GM 855resolution
Michael Jastram schrieb: Next, Writing is enabled by setting bits 0, 1, 4 and 5, as documented in section 4.8.17 (page 70). In fact, this enables two, not just one PAM register for R/W. But which ones? I don't understand where 0xcfe comes from! CONFIG_DATA starts at 0xcfc (4.6.2., page 57); which of the 14 PAM Registers are we writing to? Addressing these registers works as follows: The lower eight bits of the data written to 0xcf8 form the register, the lowest two bits are ignored (assumed 0), though. Then four consecutive registers appear at ports 0xcfc to 0xcff. For example: If you write 0x805a to 0xcf8 the registers 0x58 to 0x5b can be accessed. (Ignoring the two least significant bits of 0x5a gives 0x58.) So writing to 0xcfe affects register 0x5a which is responsible for the memory range from 0xc to 0xc where the video BIOS resides. But I just received an email from Steve Tomljenovic: He already ported 855resolution to the i915. You can find his 915resolution at: http://www.geocities.com/stomljen/ Christian -- Christian Zietz - CHZ-Soft - [EMAIL PROTECTED] WWW: http://www.chzsoft.com.ar/ PGP-Key-ID: 0x6DA025CA ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: Resolution problems with i810 driver, Intel 915GM 855resolution
Michael Jastram schrieb: That would be really cool - because I have no idea where the magic numbers come from, and which ones would be appropriate for the 915GM. I looked at the outl/outb documentation, but obviously the values are hardware specific. Can you, or anybody on the list, give me some pointers? The registers to change are documented in the datasheet of the specific chipset by Intel. You'll have to look for the PAM registers (at least that's what they're called for i8xx-chipsets). CU Christian -- Christian Zietz - CHZ-Soft - [EMAIL PROTECTED] WWW: http://www.chzsoft.com.ar/ PGP-Key-ID: 0x6DA025CA ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: External CRT works on 1024x768 but LCD not. Please Help!!!
Nqnsome schrieb: Sorry to ask that but, if the BIOS is broken, why, under WindowsXp, the LCD works in 1024x768? Why, with X11, the CRT works in 1024x768? I still suppose that your BIOS only recognizes the LCD as a 800x600 one, while the CRT is recognized correctly as being able to display 1024x768. The Windows XP driver doesn't care about the BIOS but bypasses it. X on the other hand needs the BIOS to set the resolution because the information on how to do that without the BIOS is not publicly available. CU Christian -- Christian Zietz - CHZ-Soft - [EMAIL PROTECTED] WWW: http://www.chzsoft.com.ar/ PGP-Key-ID: 0x6DA025CA ___ Devel mailing list Devel@XFree86.Org http://XFree86.Org/mailman/listinfo/devel
Re: Driver i810 ignores modes created by 855resolution
Nqnsome schrieb: Why it only finds the old 640x480 mode after patching? What happens to the new (patched) 1024x768 mode? In some previous post you already found out that ModeAttributes value for the 1024x768 mode is 0x9a which (among other things) means that the mode is not supported by present hardware configuration. I think the same happens with the new patched mode. If the mode is marked as not supported, XFree86 won't list it as built-in mode since it can't be set by calling the video BIOS. I don't know why your BIOS always marks this mode as not supported. I had this once with an embedded system which was only configured for a 800x600 LCD. Maybe the company who built your laptop configured the BIOS for a 800x600 LCD, too but hooked up a 1024x768 one. CU Christian -- Christian Zietz - CHZ-Soft - [EMAIL PROTECTED] WWW: http://www.chzsoft.com.ar/ PGP-Key auf Anfrage oder ueber http://www.keyserver.net/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Driver (i810) ignores modeline directives in Config File
Hi, PLATTNER Christoph schrieb: But starting the X server, I could find the line (II) I810(0): Monitor0: Using hsync range of 31.50-70.00 kHz (II) I810(0): Monitor0: Using vrefresh range of 50.00-100.00 Hz (II) I810(0): Not using mode 1152x864 (no mode of this name) [...] Are there changes in Xfree, that only the built in can be used ? That's because the i810-driver has to use the video BIOS to set a video mode (i.e. resolution and color depth) because there is no publicly available documentation on how to set modes bypassing the BIOS. So only video modes known to the BIOS can be set. For the i855-chipset there is a utility called 855resolution to add custom video modes to the video BIOS. Maybe it'll work with i865, too: http://perso.wanadoo.fr/apoirier/ CU Christian -- Christian Zietz - CHZ-Soft - [EMAIL PROTECTED] WWW: http://www.chzsoft.com.ar/ PGP-Key auf Anfrage oder ueber http://www.keyserver.net/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: SOLVED: 1400x1050 on a Dell 510m
Hi, Alain Poirier schrieb: The 0.2 version of 855resolution is now available. [...] Can you test it (http://perso.wanadoo.fr/apoirier/) ? As I wrote earlier, I don't have 1400x1050 on my Dell Inspiron 500m but 855resolution now reports the correct values and I was able to undefine the 1024x768 mode and redefine it later so I think it should work on a 500m, too. I put a link on the 855patch page so maybe there will be some more testers soon. CU Christian -- Christian Zietz - CHZ-Soft - [EMAIL PROTECTED] WWW: http://www.chzsoft.com.ar/ PGP-Key auf Anfrage oder ueber http://www.keyserver.net/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: SOLVED: 1400x1050 on a Dell 510m
Hi, Alain Poirier schrieb: 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 Using a debugger, I found out that there is a offset from the pointer in the table to the actual resolution data. The offset is 6 + (n * 0x1C) bytes, where n was 0 or 1 for me (500m, BIOS 2945) although I currently don't know how n is set. The x-resolution is a unsigned short (2 bytes) 4 bytes from the offset calculated above, the y-resolution is at 16 bytes. CU Christian -- Christian Zietz - CHZ-Soft - [EMAIL PROTECTED] WWW: http://www.chzsoft.com.ar/ PGP-Key auf Anfrage oder ueber http://www.keyserver.net/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: SOLVED: 1400x1050 on a Dell 510m
Hi, Alain Poirier schrieb: I just finished to write a little soft to patch the VBIOS on a Dell 510m and to get the 1400x1050 resolution. 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. 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. Another question: May I put a link to the 855resolution page on my 8x5patch/855wrap web page? CU Christian -- Christian Zietz - CHZ-Soft - [EMAIL PROTECTED] WWW: http://www.chzsoft.com.ar/ PGP-Key auf Anfrage oder ueber http://www.keyserver.net/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: i810 driver 1400x1050 problem -- bios replacement
Hi, Christian Zietz schrieb: [X-Server for 845/855/865 provided by Intel] But the server crashes every time when starting KDE. Meanwhile I succeeded running the driver. The crash which I reported earlier was caused by another mis-configuration I did when testing the driver. Some information: - Running on the LCD of an Inspiron 500m with a resolution of 1024x768 (native resolution) - V-BIOS 2945 (unmodified) - XFree86 4.3 - kernel 2.4.24 patched according to the instructions provided with the driver - I had to remove the VideoRam configuration option for the server to work. - The driver made by Intel doesn't support DRI so 3D-software runs very slowly. (tested with tuxracer) - Once the server crashed my system so badly that I had to do a hard reset. Summary: Since I don't need dual head or cloning I'll stay with the i810 driver. Christian -- Christian Zietz - CHZ-Soft - [EMAIL PROTECTED] WWW: http://www.chzsoft.com.ar/ PGP-Key auf Anfrage oder ueber http://www.keyserver.net/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: i810 driver 1400x1050 problem -- bios replacement
Hi, L. Jensen schrieb: The driver runs on the external monitor by default. It needs Option PrimaryPort LVDS to start on the local lcd. With that option I was able start XFree86 with a resolution of 1024x768 on my LCD. (That's its native resolution.) But the server crashes every time when starting KDE. I wonder if anybody will get the driver working without problems. CU Christian -- Christian Zietz - CHZ-Soft - [EMAIL PROTECTED] WWW: http://www.chzsoft.com.ar/ PGP-Key auf Anfrage oder ueber http://www.keyserver.net/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: i810 driver 1400x1050 problem -- bios replacement
Hi, S Streif schrieb: Which information related to the structure of the video bios do you have so far? All that I know about the configuration data is documented in the comments included in the *.bsf files provided with the V-BIOS. The configuration is stored in blocks, every block starts with its number (1 byte) and its size (2 bytes). Do you know someone working at this problem? Sorry, I don't. Does someone else on this list? I just found similar programs/tools which you can download from: Unfortunately they are specific to CT 65545 chipset. CU Christian -- Christian Zietz - CHZ-Soft - [EMAIL PROTECTED] WWW: http://www.chzsoft.com.ar/ PGP-Key auf Anfrage oder ueber http://www.keyserver.net/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: i810 driver 1400x1050 problem -- bios replacement
Hi, S Streif schrieb: And a driver for Linux (very new, update date: March 30, 2004; maybe not officially released yet): ftp://download.intel.com/design/intarch/SWSUP/IEGDLinux.tgz EVERYBODY: This is really big news! A binary XFree86 driver for 8x5 embedded graphics mady by Intel which apparently supports 1400x1050 as well as dual head. Sadly, I couldn't get it running. It always crashes with signal 11. Maybe someone else with the appropriate hardware could try. CU Christian -- Christian Zietz - CHZ-Soft - [EMAIL PROTECTED] WWW: http://www.chzsoft.com.ar/ PGP-Key auf Anfrage oder ueber http://www.keyserver.net/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: i810 driver 1400x1050 problem -- bios replacement
Hi, S Streif schrieb: The main difference between both bioses is the different size (new: 0x80 kB, old 0x67 kB) which could stem from further extensions as (hopefully) additional modeline entries etc. I had a look at BIOS 3166 which was provided together with the Windows driver and it did not contain support for more video modes. (The size info has nothing to say, actually. It was set to 0x80 in BIOS 3166, too. The area reserved for the Video-BIOS is 64 kiB.) According to Intel they won't support 1400x1050 in their Video-BIOSes. They say it's the job of the OEMs to modify the BIOS supplied by Intel accordingly. Could this be a true drop-in replacement? I wrote a program to load the BIOS and replace the old one (NO, it will NOT be released). The problem is: The new BIOS is not configured correctly for the hardware. It worked more or less in my case, but I think this could lead to whole lot of problems. Could this replacement lead to any hardware damages etc.? Sure, in the worst case. As I wrote, the BIOS not configured properly. CU Christian -- Christian Zietz - CHZ-Soft - [EMAIL PROTECTED] WWW: http://www.chzsoft.com.ar/ PGP-Key auf Anfrage oder ueber http://www.keyserver.net/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: i810 driver 1400x1050 problem -- bios replacement
Hi, S Streif schrieb: But to be sure that we are talking about the same file: The video bios file I am talking about is mtg_3240.dat (3240 stands for the build number). It is included in a zip file in the windows driver installation file. This zip file's name is vbios852-855.zip (i855 is my chip set). Same for me, only that it was mtg_3166.dat. I knew that. However, my hope was that the other files included in this vbios*.zip file are part of the OEM utility program BMP which is used to modify certain parameters in the original bios Do you know where to get this program? This would be a start. Although adding a video mode is not just a matter of giving h and v resolution. You must provide some sort of parameter string and I found no documentation for that. I hoped that the other files in this vbios*.zip file are the necessary modifications for the implementation of a 1400x1050 video mode. As far as I figured out they are plug-ins for additional hardware (TV-out etc.) and configuration files for use with BMP. Problem is, not all configuration parameters are documented. (see above) Which laptop are you using? Dell Inspiron 500m with a 1024x768 display and V-BIOS 2945 preinstalled. I will bear this warnings in my mind. Anyway, I want to try the bios replacement. If you really want to try: Yes, you can load the new BIOS at 0xC. But you have to make this area writable first. Documentation for that can be found in the 855GM datasheet from Intel. And probably you'll have to initialize the new BIOS by calling 0xC0003 in real mode. This call crashed for me so I had to patch some bytes of the BIOS image. You see: It's not really easy and I think the bytes to patch are different in every version. CU Christian -- Christian Zietz - CHZ-Soft - [EMAIL PROTECTED] WWW: http://www.chzsoft.com.ar/ PGP-Key auf Anfrage oder ueber http://www.keyserver.net/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: i855GM: New BIOS breaks i810-driver
Hi, I just forgot to say, that BIOS build 3197 is newer than the one installed on the new Dell machines (build 3066). So if it was an error by Intel they already fixed it. CU Christian ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: i855GM: New BIOS breaks i810-driver
Hi, Alan Hourihane schrieb: Is there a string 'DELL' or similar in the BIOS that we can use the function xf86ReadBIOS() to detect this buggy BIOS and skip using this function call in this case ? No, there is no reference to Dell in the BIOS. I'm not even sure if they configure the BIOS. I just know that there is the possibility to do so and that the faulty table is in an area where some values can be configured by the OEM. So it doesn't need to be a bug introduced by Dell, it's just one possible explanation. But I suppose that all computers made by Dell affected by this bug use BIOS build 3066. So you could scan for 3066Intel(r), although I don't think this would be a good idea. Dell could release a BIOS update or other computers from other companies with a different build number could be affected, too. So, why not continue to use a configuration option? I don't see any problems caused by not calling this particular function. CU Christian PS: Some video BIOS developer must be a fan of Star Wars. A string I found in all BIOS versions I had a look at was Use the force Luke. ;-) -- Christian Zietz - CHZ-Soft - [EMAIL PROTECTED] WWW: http://chzsoft.com.ar/ - Fido: Christian [EMAIL PROTECTED]:2437/74.9 PGP-Key auf Anfrage oder ueber http://wwwkeys.de.pgp.net (Port 11371) ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: i855GM: New BIOS breaks i810-driver - solved
Hi, Thank you Alain for sorting out this problem and Alan for commiting a patch. Would it be possible to offer binaries or a small, easy to build source package? I think many of the users affected by that problem can't build or don't want to build the whole XFree86 from source. CU Christian ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
i855GM: New BIOS breaks i810-driver
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? CU Christian ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: i855 and 1400x1050
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. - 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. Christian ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Solution for 855GM video memory issue
Hi, I made a small webpage for 855patch that summarizes the important information: http://www.chzsoft.com.ar/855patch.html Christian ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Solution for 855GM video memory issue
Hi, Egbert Eich schrieb: One could verify if the current value in this location really matches the value reported by the BIOS. I wrote a new version of 855patch which does just that. So it should be safer to use than before. Everyone interested is invited to try it out: http://www.chzsoft.com.ar/855patch.tar.gz I would like to know if the people from the desktop department from Intel would be happy with such a solution. If so, I'd add the code. If you know whom to ask at Intel please do so. For me as an unknown, unimportant developer it'll probably be much harder to contact the right person. Christian -- Christian Zietz - CHZ-Soft - [EMAIL PROTECTED] WWW: http://chzsoft.com.ar/ - Fido: Christian [EMAIL PROTECTED]:2437/74.9 PGP-Key auf Anfrage oder ueber http://wwwkeys.de.pgp.net (Port 11371) ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Solution for 855GM video memory issue
Hi, PLEASE CC any answers to [EMAIL PROTECTED] as I'm not subscribed to the list. first, my problem as summarized by David H. Dawes: It appears that some 855GM-based laptops only pre-allocate 1MB of video memory, and don't provide any BIOS configuration options for increasing this. Although the XFree86 driver will allocate more (if the correct agpgart kernel support is present), the mechanism used to inform the video BIOS of the additional allocation doesn't seem to be implemented on these laptops. This results in the video BIOS refusing to program video modes that require more than 1MB (actually 832KB). As far as I know there hasn't been any solution for this. So I spent my day digging through Intel datasheets and disassembling the Video BIOS and came up with a hack that works for me: The Video BIOS stores the memory size it thinks it is allocated at a certain location in RAM. This location is write-protected by default but can me made writable by setting the appropiate chipset registers. That's what I do and then I can set the memory size so XFree86 works with higher resolutions and color depths. Since I don't have the XFree86 sources to patch, I implemented this hack in a separate program called 855patch. It takes the desired video memory size in KB as argument. Note that it only tells the BIOS what memory size to expect but does NOT actually allocate the memory. So you'll have to set the VideoRAM option in the XF86Config Device section to at least the size you used when calling 855patch (more is fine) or your system will probably crash. The hack works nicely on my Dell Inspiron 500m laptop (Intel Video BIOS version 2945) and the mechanism I described is also implemented in version 2973 I downloaded from Intel.com. So I suggest you try it, if you have the problem described above. I'd be very glad if this snippet - if it works on other systems - found it's way to XFree86 sources. Disclaimer: Obviously I can't guarantee that it'll work for you. So don't blame me if something bad happens. Download: http://www.chzsoft.com.ar/855patch.c Christian Zietz, now able to run XFree86 in 1024x768x16bpp ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
