Krishna Murphy, Thanks for the tip, but setting the hsync and vrefresh didn't help. It turns out I just need "X_VIDEORAM = 4096" instead. So, that gets the i810 driver to work for 37 machines at our office.
As a note, there's a different set of machines here that also use the i810 driver, but they have a different problem. Their X server crashes when Firefox loads certain web pages such as http://nadaguides.com, but setting the video RAM and network swap doesn't make any difference. On the other hand, the set of i810 machines that need the videoram setting can load http://nadaguides.com without problems. http://marc.theaimsgroup.com/?l=ltsp-discuss&m=114858956013207&w=2 > > I don't know how significant it is, but it looks like the trouble you're > having is somewhat like I experienced with a video driver. I was able to > eliminate the ultra-high refresh rates like those here: > > (--) I810(0): Virtual size is 1024x768 (pitch 1024) > (**) I810(0): *Default mode "1024x768": 78.8 MHz, 60.1 kHz, 75.1 Hz > (II) I810(0): Modeline "1024x768" 78.80 1024 1040 1136 1312 768 769 772 > 800 +hsync +vsync > (**) I810(0): *Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz > (II) I810(0): Modeline "800x600" 56.30 800 832 896 1048 600 601 604 631 > +hsync +vsync > (**) I810(0): *Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz > (II) I810(0): Modeline "640x480" 36.00 640 696 752 832 480 481 484 509 > -hsync -vsync > > Using the clue I got on this list: > ________________________________________________________________________________________ > > On Tue, 30 May 2006, Phil Davey wrote: > > On Mon, 29 May 2006, Krishna Murphy wrote: > >> Anyway, I saw that it was calculating the requested resolution (800x600) >> modeline incorrectly, indeed 85.1 Hz as detected. So I commented out the >> first >> two screen requests and it is up in 1024x768 mode. I guess I need to >> calculate >> or determine from external resources what the actual modelines should be. >> > > These lines in lts.conf, with suitable numbers for your monitor, should fix > it. > > X_HORZSYNC = "24-80" > X_VERTREFRESH = "55-75" > ________________________________________________________________________________ > > Hope that helps! > > -Krishna > > On Wed, 31 May 2006, Andrew Ziem wrote: > > I have several systems that won't start with the i810 driver. Instead, I just > get this: > > (==) I810(0): Write-combining range (0xf8000000,0x4000000) > (II) I810(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is > 0x0000 > (II) I810(0): Setting dot clock to 78.9 MHz [ 0x15 0x5 0x20 ] [ 23 7 2 ] > (II) I810(0): chose watermark 0x2210e000: (tab.freq 78.8) > (II) I810(0): xf86BindGARTMemory: bind key 2 at 0x00000000 (pgoffset 0) > (WW) I810(0): xf86BindGARTMemory: binding of gart memory with key 2 > at offset 0x0 failed (Device or resource busy) > > Fatal server error: > AddScreen/ScreenInit failed for driver 0 > > The whole x.org log is available here: > http://www.filelodge.com/files/room18/463092/xorg-i810_addscreenfailed.log > > These systems are Dell GX-110 (Pentium III) running LTSP 4.2 update 1. > > Note: This problem is not related to my previous, unresolved i810 crashing > problem, which only happens on other systems. > http://marc.theaimsgroup.com/?l=ltsp-discuss&m=114858956013207&w=2 > > Andrew _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
