Make sure you specify /dev/wsmouse and not the actual mouse type when setting up X.. Matthew --- newbie-request@XFree86.Org wrote: > Send submissions to > newbie@XFree86.Org > > To subscribe or unsubscribe via the World Wide Web, > visit > http://XFree86.Org/mailman/listinfo/newbie > or, via email, send a message with subject or body > 'help' to > newbie-request@XFree86.Org > > You can reach the person managing the list at > newbie-admin@XFree86.Org > > When replying, please edit your Subject line so it > is more specific > than "Re: Contents of Newbie digest..." > > > Today's Topics: > > 1. XFree86 4.2 on a Dell Inspiron 8200 (Chris > Simpson) > 2. Re: Again Logitech and wheel (Lionel Lecoq) > 3. Re: MSI KT266 Pro2 + powered by ATI Radeon > 7500 + XFree 4.2 => X shutdown = PC Crash (bip bip) > (yann FUSERO) > 4. Re: MSI KT266 Pro2 + powered by ATI Radeon > 7500 + XFree 4.2 => X shutdown = PC Crash (bip bip) > (yann FUSERO) > 5. Re: RE: pkg_info | grep -i kde (Ted Spradley) > 6. Dell Inspiron 8000: Modeline request for > 800x600 on LCD (Ryurick M. Hristev) > 7. Re: MSI KT266 Pro2 + powered by ATI Radeon > 7500 + XFree 4.2 => X shutdown = PC Crash (bip bip) > (Hubert Yoshizaki) > 8. Re: Can't get Trident graphics working (Alan > Hourihane) > 9. help : X-server (4.2) still crashes with > Galeon (amitm) > 10. Prblm: Configure ATI Mobile M4 with XFree86 > 4.2.0. (Ola Theander) > 11. Re: Prblm: Configure ATI Mobile M4 with > XFree86 4.2.0. (Ryurick M. Hristev) > 12. Re: Can't get Trident graphics working (Hubert > Yoshizaki) > 13. Re: Prblm: Configure ATI Mobile M4 with > XFree86 4.2.0. (Bill Winegarden) > 14. Re: Prblm: Configure ATI Mobile M4 with > XFree86 4.2.0. (Ryurick M. Hristev) > 15. help me.. about libbitmap.a (Yu-Chan Park) > 16. OpenBSD3.0 XWin Problems (FiX{x}XeR) > 17. RE: OpenBSD3.0 XWin Problems > (=?iso-8859-1?Q?Fredrik_W=E4nglund?=) > 18. Changing amount of colors in x? (Isak Lyberth) > 19. RE: Prblm: Configure ATI Mobile M4 with > XFree86 4.2.0. (Ola Theander) > 20. Re: OpenBSD3.0 XWin Problems (FiX{x}XeR) > 21. Re: XFree-4.2 (marc brady) > 22. Monitor PanaSync S110 Help (FiX{x}XeR) > 23. RE: Prblm: Configure ATI Mobile M4 with > XFree86 4.2.0. (Ryurick M. Hristev) > > --__--__-- > > Message: 1 > From: "Chris Simpson" <csimpson@telocity.com> > To: <newbie@XFree86.Org> > Date: Thu, 18 Apr 2002 13:58:42 -0500 > Subject: [Newbie]XFree86 4.2 on a Dell Inspiron 8200 > Reply-To: newbie@XFree86.Org > > This is a multi-part message in MIME format. > > ------=_NextPart_000_0009_01C1E6E1.25F41DB0 > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > I just got this laptop yesterday, and I installed > Red Hat 7.2 today. I = > can't get XFree86 4.2 (which I installed today) to > work right. I'm = > running Xconfigurator, and I can't seem to find the > right monitor = > setting or something. My video card is a GeForce > 440 Go, and it's got = > 64MB RAM on it. I'm using the GeForce driver that > comes with XFree86 = > 4.2. ANY help would be MUCH appreciated!!! > > Thanks in advance!!! > > Chris=20 > > ------=_NextPart_000_0009_01C1E6E1.25F41DB0 > Content-Type: text/html; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 > Transitional//EN"> > <HTML><HEAD> > <META http-equiv=3DContent-Type > content=3D"text/html; = > charset=3Diso-8859-1"> > <META content=3D"MSHTML 6.00.2713.1100" > name=3DGENERATOR> > <STYLE></STYLE> > </HEAD> > <BODY bgColor=3D#ffffff> > <DIV><FONT face=3DArial size=3D2>I just got this > laptop yesterday, and I = > installed=20 > Red Hat 7.2 today. I can't get XFree86 4.2 > (which I installed = > today) to=20 > work right. I'm running Xconfigurator, and I > can't seem to find = > the right=20 > monitor setting or something. My video card is > a GeForce 440 Go, = > and it's=20 > got 64MB RAM on it. I'm using the GeForce > driver that comes with = > XFree86=20 > 4.2. ANY help would be MUCH > appreciated!!!</FONT></DIV> > <DIV><FONT face=3DArial size=3D2></FONT> </DIV> > <DIV><FONT face=3DArial size=3D2>Thanks in > advance!!!</FONT></DIV> > <DIV> </DIV> > <DIV><FONT face=3DArial > size=3D2>Chris</FONT> </DIV></BODY></HTML> > > ------=_NextPart_000_0009_01C1E6E1.25F41DB0-- > > > --__--__-- > > Message: 2 > Date: Thu, 18 Apr 2002 12:01:19 -0700 (PDT) > From: Lionel Lecoq <lionel_lecoq@yahoo.com> > Subject: Re: [Newbie]Again Logitech and wheel > To: newbie@XFree86.Org > Reply-To: newbie@XFree86.Org > > Usually > Option "ZaxisMapping" "4 5" > works > Lionel > --- Peeter Vois <Peeter.Vois@mail.ee> wrote: > > Hi, > > > > Looks like I was little too stupid when I bought > Logitech Mouse: > > > > PS2/USB,Optical,3buttons,wheel,M-BD69 > > > > This thing works, but the wheel does not work. I > readed the messages > > from many places but did not help. This mouse just > will not send out > > the wheel movement messages. The somewhere > suggested IMPS/2 driver did > > not work: the mouse moved to upper right corner > quickly and the wheel > > was still not functioning. > > > > Has anybody Ideas how to make it working or can > give me tips how to hack > > this thing a little? > > > > I'll be searching further... > > > > Peeter Vois > > _______________________________________________ > > > > Newbie@XFree86.Org > > *** To unsubscribe , or change message options, > see: > > http://XFree86.Org/mailman/listinfo/newbie > > __________________________________________________ > Do You Yahoo!? > Yahoo! Tax Center - online filing with TurboTax > http://taxes.yahoo.com/ > > --__--__-- > > Message: 3 > From: yann FUSERO <yann.fusero1@libertysurf.fr> > To: newbie@XFree86.Org, ofeeley@yahoo.com > Subject: Re: [Newbie]MSI KT266 Pro2 + powered by ATI > Radeon 7500 + XFree 4.2 => X shutdown = PC Crash > (bip bip) > Date: Thu, 18 Apr 2002 17:44:33 +0200 > Reply-To: newbie@XFree86.Org > > > > Le Mercredi 17 Avril 2002 18:00, ofeeley@yahoo.com a > écrit : > > My problem is that DRI is anabled according to > glxinfo and there is a > > wonderfully high fps according to glxgears and > Tuxracer will run.....and > > then freeze. The soundtrack repeats one note > again and again and again. > > for me DRI works OK glxgears gives me 1260 fps ! > but TuxRacer works well, no freeze > > > > > I think it's caused by ACPI functions in the > bios but I could'n't find > > > any satisfaying bios settings. > > > > Why do you think it's ACPI? I'm not offering an > opinion here, just > > wondering if you have some diagnostic lead that I > should investigate. > If I disable ACPI functions after lilo prompt, if I > choose Linux my PC > freezes during boot (but no "bip" at this time, just > no life on the screen) > > > > I'll let you know if I have any luck. > hope we can find a solution to our problems > > Yann > > --__--__-- > > Message: 4 > From: yann FUSERO <yann.fusero1@libertysurf.fr> > To: newbie@XFree86.Org, "Hubert Yoshizaki" > <hyoshiza@onebox.com> > Subject: Re: [Newbie]MSI KT266 Pro2 + powered by ATI > Radeon 7500 + XFree 4.2 => X shutdown = PC Crash > (bip bip) > Date: Thu, 18 Apr 2002 17:40:38 +0200 > Reply-To: newbie@XFree86.Org > > Salut Hubert > > > I don't think this is going to help you much but > anyhow, > > I have an AGP Powercolor 32MB DDR Dark Wizard (ATI > Radeon 7000) with > > Suse 7.3 using Xfree86 4.2. When I enable DRI and > try glxgears it would > > always crash my system. X works fine. In my case, > I seemed to have a > > problem with my motherboard (some DMA issue with > my Harddrive I think). > > What I did to fix it (extreme I know...) was to > switch motherboards with > > my other machine (from a SOYO to an Asus P5A-B). I > wouldn't expect yours > > to be the same problem. > > Is your problem totally solved by changing the > mother board ? > What scares me is that I have dual boot and my PC > works fine under Winblows > 98SE ! > For me linux is less stable than win98SE !! ;-) > > > Your config file looks fine (assuming you do have > a Vision Master 400 > > (Iiyama), and that your mode lines are correct. > that's ok ! > > > Does X crash or does it crash only when you run > something that is 3D > > accelerated? (e.g. glxgears, tuxracer etc.) > 3D acceleration work slike a charm, X works like a > charm my only problem is > that I can't leave X without a PC crash. > > > Does X crash if you have dri and glx disabled? If > it does then probably > > something to do with your general X config. > it works also with 3D accel disabled. > > > I hope find a solution that is less drastic as > mine (I had a feeling > > something was wrong with my motherboard for a > while since it gave me > > alot of headache with other stuff). > I hope too. > I'll try to play with DMA settings but I hope this > problem won't cost me any > piece of hardware. > > > thanks > > Yann > > --__--__-- > > Message: 5 > Date: Thu, 18 Apr 2002 14:53:31 -0500 > From: Ted Spradley <tsprad@spradley.org> > To: newbie@XFree86.Org > Subject: Re: [Newbie]RE: pkg_info | grep -i kde > Organization: S & S Computing > Reply-To: newbie@XFree86.Org > > On Wed, 17 Apr 2002 15:52:41 -0700 > "Patrick Soltani" <psoltani@ultradns.com> wrote: > > > Please let me know if any experience with xwrapper > and how to set it > > up so that the users can also use the machine > using startx and their > > local accounts. > > Why not use xdm? > > -- > Remember, more computing power was thrown away last > week than existed in > the world in 1982. -- > http://www.tom.womack.net/computing/prices.html > > --__--__-- > > Message: 6 > Date: Fri, 19 Apr 2002 08:32:05 +1200 (NZST) > From: "Ryurick M. Hristev" > <r.hristev@phys.canterbury.ac.nz> > To: newbie@XFree86.Org > Subject: [Newbie]Dell Inspiron 8000: Modeline > request for 800x600 on LCD > Reply-To: newbie@XFree86.Org > > Hello, > > I have a Dell Inspiron 8000 and I am trying to setup > the tv > output. This machine have an ATI Rage 128 Mobility > MF > and a 15' SXGA 1400x1050 LCD screen. > > So far the 'atitvout' works in text mode but not in > X > (at 1400x1050). Apparently it is necessary to lower > the > resolution at 800x600 or below. > > No modeline I tried worked so far, all give some > sort of horizontal > "warping" (for lack of better words to describe it). > > I've tried also to build one as described in > XFree86-Video-Timings-HOWTO > but so far ESR lost me somwhere at SH1, SH2 and SV2 > :-( > > Dell supplies one modeline which works, described > as: > HorizSync 31.5 - 90.0 > VertRefresh 60.0 > Modeline "1400x1050" 108.000 1400 1448 1462 > 1688 1050 1050 1053 1066 > > There is something else strange: X reports the clock > being able to go from 17 to 270 but all 800x600 > modes > (in the logs) were reported at 108. > > Is there anybody able to help me or explain ? > > TIA > > Cheers, > -- > Ryurick M. Hristev > mailto:r.hristev@phys.canterbury.ac.nz > Computer Systems Manager > University of Canterbury, Physics & Astronomy Dept., > New Zealand > > > > --__--__-- > > Message: 7 > Date: Thu, 18 Apr 2002 17:36:22 -0400 > Subject: Re: [Newbie]MSI KT266 Pro2 + powered by ATI > Radeon 7500 + XFree 4.2 => X shutdown = PC Crash > (bip bip) > From: "Hubert Yoshizaki" <hyoshiza@onebox.com> > To: newbie@XFree86.Org > Reply-To: newbie@XFree86.Org > > Hi there Yann, > Just to note, my problem was an extreme case > particular to only me. Changing > the motherboard is the 'Last' thing you would want > to do if at all. The > 'Only' reason i did so was because of my radeon > problems and various > other problems. The bad board is now running my > Windoze machine...and > surprise surprise...Windows is crashing even more > frequently then before...never > thought that was possible ;) > > If it runs fine in Windows 9x then I would look > elsewhere. > Looking at your problem again... > if your X generally works fine with your hand > written then I would keep > using it. :) > As for your Sax2 problem I have no idea. > As for your 'shutting down x causes crash' > problem... If you try shutting > down your system without X, what happens? Never > encountered that before. > > Anyone have any ideas? > > > ---- yann FUSERO <yann.fusero1@libertysurf.fr> > wrote: > > Salut Hubert > > > > > I don't think this is going to help you much but > anyhow, > > > I have an AGP Powercolor 32MB DDR Dark Wizard > (ATI Radeon 7000) with > > > Suse 7.3 using Xfree86 4.2. When I enable DRI > and try glxgears it > > would > > > always crash my system. X works fine. In my > case, I seemed to have > > a > > > problem with my motherboard (some DMA issue with > my Harddrive I think). > > > What I did to fix it (extreme I know...) was to > switch motherboards > > with > > > my other machine (from a SOYO to an Asus P5A-B). > I wouldn't expect > > yours > > > to be the same problem. > > > > Is your problem totally solved by changing the > mother board ? > > What scares me is that I have dual boot and my PC > works fine under > > Winblows > > 98SE ! > > For me linux is less stable than win98SE !! ;-) > > > > > Your config file looks fine (assuming you do > have a Vision Master > > 400 > > > (Iiyama), and that your mode lines are correct. > > that's ok ! > > > > > Does X crash or does it crash only when you run > something that is > > 3D > > > accelerated? (e.g. glxgears, tuxracer etc.) > > 3D acceleration work slike a charm, X works like a > charm my only problem > > is > > that I can't leave X without a PC crash. > > > > > Does X crash if you have dri and glx disabled? > If it does then probably > > > > > something to do with your general X config. > > it works also with 3D accel disabled. > > > > > I hope find a solution that is less drastic as > mine (I had a feeling > > > something was wrong with my motherboard for a > while since it gave > > me > > > alot of headache with other stuff). > > I hope too. > > I'll try to play with DMA settings but I hope this > problem won't cost > > me any > > piece of hardware. > > > > > > thanks > > > > Yann > > _______________________________________________ > > > > Newbie@XFree86.Org > > *** To unsubscribe , or change message options, > see: > > http://XFree86.Org/mailman/listinfo/newbie > > > > --__--__-- > > Message: 8 > Date: Thu, 18 Apr 2002 08:43:53 +0100 > From: Alan Hourihane <alanh@fairlite.demon.co.uk> > To: newbie@XFree86.Org > Subject: Re: [Newbie]Can't get Trident graphics > working > Reply-To: newbie@XFree86.Org > > Upgrade to XFree86 4.2.0 and re-report any problems > here. > > On Tue, Apr 16, 2002 at 01:26:16 -0400, John Malick > wrote: > > I think I'm just abou there but the graphics comes > up clearly with a > > sync issue. There are vertical colored lines from > top to bottom and you > > can just barely make out the gnome session. > > > > My graphics card is the Tridend card with 9668 > chipset and 2MB video > > ram. My monitor is a multsync monitor, no brand > name. Acutally the only > > name on it is Leo but it supports anywhere from > 30-50Khz and 40-70Hz .. > > > > My XFree86 server is 4.0.1a. > > > > Does anyone have a working XF86Config file for > this Trident card that > > they can shoot over to me? > > > > Thank You > > > > _______________________________________________ > > > > Newbie@XFree86.Org > > *** To unsubscribe , or change message options, > see: > > http://XFree86.Org/mailman/listinfo/newbie > > --__--__-- > > Message: 9 > Date: Thu, 18 Apr 2002 13:33:32 +0530 > From: "amitm" <amitm@infy.com> > To: <newbie@xfree86.org> > Subject: [Newbie]help : X-server (4.2) still > crashes with Galeon > Reply-To: newbie@XFree86.Org > > Hi, > > I upgraded to XFree86 4.2 on my machine. Since I was > having with font display on my Gnome apps I pointed > the /usr/X11R6/lib/X11/fonts to the fonts directory > from my previous (XFree 4.03) installation. > > I thought this might solve the problem I have been > having whenever I access new.bbc.co.uk with Galeon > and the X-server used to crash. Unfortunately, it > has not solved the problem. I thought that whatever > happens, X is not expected to crash. > > /var/log/XFree86.0.log is appended below. > > > XFree86 Version 4.2.0 / X Window System > (protocol Version 11, revision 0, vendor release > 6600) > Release Date: 18 January 2002 > If the server is older than 6-12 months, or if your > card is > newer than the above date, look for a newer version > before > reporting problems. (See http://www.XFree86.Org/) > Build Operating System: Linux 2.4.9-13smp i686 [ELF] > > 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: Thu > Apr 18 11:58:44 2002 > (==) Using config file: "/etc/X11/XF86Config-4" > (==) ServerLayout "XFree86 Configured" > (**) |-->Screen "Screen0" (0) > (**) | |-->Monitor "DELL E551" > (**) | |-->Device "Intel 810" > (**) |-->Input Device "Mouse0" > (**) |-->Input Device "Keyboard0" > (**) Option "XkbLayout" "us" > (**) XKB: layout: "us" > (==) Keyboard: CustomKeycode disabled > (**) FontPath set to "unix/:7100" > (==) RgbPath set to "/usr/X11R6/lib/X11/rgb" > (==) ModulePath set to "/usr/X11R6/lib/modules" > (--) using VT number 3 > > (II) Open APM successful > (II) Module ABI versions: > XFree86 ANSI C Emulation: 0.1 > XFree86 Video Driver: 0.5 > XFree86 XInput driver : 0.3 > XFree86 Server Extension : 0.1 > XFree86 Font Renderer : 0.3 > (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.2.0, module version = 1.0.0 > Module class: XFree86 Font Renderer > ABI class: XFree86 Font Renderer, version 0.3 > (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.2.0, module version = 0.1.0 > ABI class: XFree86 Video Driver, version 0.5 > (II) PCI: Probing config type using method 1 > (II) PCI: Config type is 1 > (II) PCI: stages = 0x03, oldVal1 = 0x00000000, > mode1Res1 = 0x80000000 > (II) PCI: PCI scan (all values are in hex) > (II) PCI: 00:00:0: chip 8086,7124 card 1028,00b4 rev > 03 class 06,00,00 hdr 00 > (II) PCI: 00:01:0: chip 8086,7125 card 1028,00b4 rev > 03 class 03,00,00 hdr 00 > (II) PCI: 00:1e:0: chip 8086,2418 card 0000,0000 rev > 02 class 06,04,00 hdr 01 > (II) PCI: 00:1f:0: chip 8086,2410 card 0000,0000 rev > 02 class 06,01,00 hdr 80 > (II) PCI: 00:1f:1: chip 8086,2411 card 8086,2411 rev > 02 class 01,01,80 hdr 00 > (II) PCI: 00:1f:2: chip 8086,2412 card 8086,2412 rev > 02 class 0c,03,00 hdr 00 > (II) PCI: 00:1f:3: chip 8086,2413 card 8086,2413 rev > 02 class 0c,05,00 hdr 00 > (II) PCI: 00:1f:5: chip 8086,2415 card 1028,00b4 rev > 02 class 04,01,00 hdr 00 > (II) PCI: 01:0c:0: chip 10b7,9200 card 1028,00b4 rev > 78 class 02,00,00 hdr 00 > (II) PCI: End of PCI scan > (II) LoadModule: "scanpci" > (II) Loading /usr/X11R6/lib/modules/libscanpci.a > (II) Module scanpci: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 0.1.0 > ABI class: XFree86 Video Driver, version 0.5 > (II) UnloadModule: "scanpci" > (II) Unloading /usr/X11R6/lib/modules/libscanpci.a > (II) Host-to-PCI bridge: > (II) PCI-to-ISA bridge: > (II) PCI-to-PCI bridge: > (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: > 0x08 (VGA_EN is set) > (II) Bus 0 I/O range: > [0] -1 0x00000000 - 0x0000ffff (0x10000) IX[B] > (II) Bus 0 non-prefetchable memory range: > [0] -1 0x00000000 - 0xffffffff (0x0) MX[B] > (II) Bus 0 prefetchable memory range: > [0] -1 0x00000000 - 0xffffffff (0x0) MX[B] > (II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: > 0x06 (VGA_EN is cleared) > (II) Bus 1 I/O range: > [0] -1 0x0000e000 - 0x0000e0ff (0x100) IX[B] > [1] -1 0x0000e400 - 0x0000e4ff (0x100) IX[B] > [2] -1 0x0000e800 - 0x0000e8ff (0x100) IX[B] > [3] -1 0x0000ec00 - 0x0000ecff (0x100) IX[B] > (II) Bus 1 non-prefetchable memory range: > [0] -1 0xfd000000 - 0xfeffffff (0x2000000) MX[B] > (II) Bus 1 prefetchable memory range: > (II) Bus -1: bridge is at (0:31:0), (0,-1,0), BCTRL: > 0x08 (VGA_EN is set) > (II) Bus -1 I/O range: > (II) Bus -1 non-prefetchable memory range: > (II) Bus -1 prefetchable memory range: > (--) PCI:*(0:1:0) Intel i810e rev 3, Mem @ > 0xf8000000/26, 0xff000000/19 > (II) Addressable bus resource ranges are > [0] -1 0x00000000 - 0xffffffff (0x0) MX[B] > [1] -1 0x00000000 - 0x0000ffff (0x10000) IX[B] > (II) OS-reported resource ranges: > [0] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B) > [1] -1 0x00100000 - 0x3fffffff (0x3ff00000) > MX[B]E(B) > [2] -1 0x000f0000 - 0x000fffff (0x10000) MX[B] > [3] -1 0x000c0000 - 0x000effff (0x30000) MX[B] > [4] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B] > [5] -1 0x0000ffff - 0x0000ffff (0x1) IX[B] > [6] -1 0x00000000 - 0x000000ff (0x100) IX[B] > (II) Active PCI resource ranges: > [0] -1 0xfdfffc00 - 0xfdfffc7f (0x80) MX[B] > [1] -1 0xff000000 - 0xff07ffff (0x80000) MX[B](B) > [2] -1 0xf8000000 - 0xfbffffff (0x4000000) MX[B](B) > [3] -1 0x0000ec80 - 0x0000ecff (0x80) IX[B] > [4] -1 0x0000dc80 - 0x0000dcbf (0x40) IX[B] > [5] -1 0x0000d800 - 0x0000d8ff (0x100) IX[B] > [6] -1 0x0000dcd0 - 0x0000dcdf (0x10) IX[B] > [7] -1 0x0000ff80 - 0x0000ff9f (0x20) IX[B] > [8] -1 0x0000ffa0 - 0x0000ffaf (0x10) IX[B] > (II) Active PCI resource ranges after removing > overlaps: > [0] -1 0xfdfffc00 - 0xfdfffc7f (0x80) MX[B] > [1] -1 0xff000000 - 0xff07ffff (0x80000) MX[B](B) > [2] -1 0xf8000000 - 0xfbffffff (0x4000000) MX[B](B) > [3] -1 0x0000ec80 - 0x0000ecff (0x80) IX[B] > [4] -1 0x0000dc80 - 0x0000dcbf (0x40) IX[B] > [5] -1 0x0000d800 - 0x0000d8ff (0x100) IX[B] > [6] -1 0x0000dcd0 - 0x0000dcdf (0x10) IX[B] > [7] -1 0x0000ff80 - 0x0000ff9f (0x20) IX[B] > [8] -1 0x0000ffa0 - 0x0000ffaf (0x10) IX[B] > (II) OS-reported resource ranges after removing > overlaps with PCI: > [0] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B) > [1] -1 0x00100000 - 0x3fffffff (0x3ff00000) > MX[B]E(B) > [2] -1 0x000f0000 - 0x000fffff (0x10000) MX[B] > [3] -1 0x000c0000 - 0x000effff (0x30000) MX[B] > [4] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B] > [5] -1 0x0000ffff - 0x0000ffff (0x1) IX[B] > [6] -1 0x00000000 - 0x000000ff (0x100) IX[B] > (II) All system resource ranges: > [0] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B) > [1] -1 0x00100000 - 0x3fffffff (0x3ff00000) > MX[B]E(B) > [2] -1 0x000f0000 - 0x000fffff (0x10000) MX[B] > [3] -1 0x000c0000 - 0x000effff (0x30000) MX[B] > [4] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B] > [5] -1 0xfdfffc00 - 0xfdfffc7f (0x80) MX[B] > [6] -1 0xff000000 - 0xff07ffff (0x80000) MX[B](B) > [7] -1 0xf8000000 - 0xfbffffff (0x4000000) MX[B](B) > [8] -1 0x0000ffff - 0x0000ffff (0x1) IX[B] > [9] -1 0x00000000 - 0x000000ff (0x100) IX[B] > [10] -1 0x0000ec80 - 0x0000ecff (0x80) IX[B] > [11] -1 0x0000dc80 - 0x0000dcbf (0x40) IX[B] > [12] -1 0x0000d800 - 0x0000d8ff (0x100) IX[B] > [13] -1 0x0000dcd0 - 0x0000dcdf (0x10) IX[B] > [14] -1 0x0000ff80 - 0x0000ff9f (0x20) IX[B] > [15] -1 0x0000ffa0 - 0x0000ffaf (0x10) IX[B] > (II) LoadModule: "dbe" > (II) Loading > /usr/X11R6/lib/modules/extensions/libdbe.a > (II) Module dbe: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 1.0.0 > Module class: XFree86 Server Extension > ABI class: XFree86 Server Extension, version 0.1 > (II) Loading extension DOUBLE-BUFFER > (II) LoadModule: "GLcore" > (II) Loading > /usr/X11R6/lib/modules/extensions/libGLcore.a > (II) Module GLcore: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 1.0.0 > ABI class: XFree86 Server Extension, version 0.1 > (II) LoadModule: "dri" > (II) Loading > /usr/X11R6/lib/modules/extensions/libdri.a > (II) Module dri: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 1.0.0 > ABI class: XFree86 Server Extension, version 0.1 > (II) Loading sub module "drm" > (II) LoadModule: "drm" > (II) Loading /usr/X11R6/lib/modules/linux/libdrm.a > (II) Module drm: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 1.0.0 > ABI class: XFree86 Server Extension, version 0.1 > (II) Loading extension XFree86-DRI > (II) LoadModule: "glx" > (II) Loading > /usr/X11R6/lib/modules/extensions/libglx.a > (II) Module glx: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 1.0.0 > ABI class: XFree86 Server Extension, version 0.1 > (II) Loading sub module "GLcore" > (II) LoadModule: "GLcore" > (II) Reloading > /usr/X11R6/lib/modules/extensions/libGLcore.a > (II) Loading extension GLX > (II) LoadModule: "extmod" > (II) Loading > /usr/X11R6/lib/modules/extensions/libextmod.a > (II) Module extmod: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 1.0.0 > Module class: XFree86 Server Extension > ABI class: XFree86 Server Extension, version 0.1 > (II) Loading extension SHAPE > (II) Loading extension MIT-SUNDRY-NONSTANDARD > (II) Loading extension BIG-REQUESTS > (II) Loading extension SYNC > (II) Loading extension MIT-SCREEN-SAVER > (II) Loading extension XC-MISC > (II) Loading extension XFree86-VidModeExtension > (II) Loading extension XFree86-Misc > (II) Loading extension XFree86-DGA > (II) Loading extension DPMS > (II) Loading extension FontCache > (II) Loading extension TOG-CUP > (II) Loading extension Extended-Visual-Information > (II) Loading extension XVideo > (II) Loading extension XVideo-MotionCompensation > (II) LoadModule: "v4l" > (II) Loading > /usr/X11R6/lib/modules/drivers/linux/v4l_drv.o > (II) Module v4l: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 0.0.1 > ABI class: XFree86 Video Driver, version 0.5 > (II) LoadModule: "i810" > (II) Loading > /usr/X11R6/lib/modules/drivers/i810_drv.o > (II) Module i810: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 1.1.0 > Module class: XFree86 Video Driver > ABI class: XFree86 Video Driver, version 0.5 > (II) LoadModule: "mouse" > (II) Loading > /usr/X11R6/lib/modules/input/mouse_drv.o > (II) Module mouse: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 1.0.0 > Module class: XFree86 XInput Driver > ABI class: XFree86 XInput driver, version 0.3 > (II) v4l driver for Video4Linux > (II) I810: Driver for Intel i810 chipset: i810, > i810-dc100, i810e, i815, > i830M > (II) Primary Device is: PCI 00:01:0 > (--) Assigning device section with no busID to > primary device > (--) Chipset i810e found > (II) resource ranges after xf86ClaimFixedResources() > call: > [0] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B) > [1] -1 0x00100000 - 0x3fffffff (0x3ff00000) > MX[B]E(B) > [2] -1 0x000f0000 - 0x000fffff (0x10000) MX[B] > [3] -1 0x000c0000 - 0x000effff (0x30000) MX[B] > [4] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B] > [5] -1 0xfdfffc00 - 0xfdfffc7f (0x80) MX[B] > [6] -1 0xff000000 - 0xff07ffff (0x80000) MX[B](B) > [7] -1 0xf8000000 - 0xfbffffff (0x4000000) MX[B](B) > [8] -1 0x0000ffff - 0x0000ffff (0x1) IX[B] > [9] -1 0x00000000 - 0x000000ff (0x100) IX[B] > [10] -1 0x0000ec80 - 0x0000ecff (0x80) IX[B] > [11] -1 0x0000dc80 - 0x0000dcbf (0x40) IX[B] > [12] -1 0x0000d800 - 0x0000d8ff (0x100) IX[B] > [13] -1 0x0000dcd0 - 0x0000dcdf (0x10) IX[B] > [14] -1 0x0000ff80 - 0x0000ff9f (0x20) IX[B] > [15] -1 0x0000ffa0 - 0x0000ffaf (0x10) IX[B] > (II) resource ranges after probing: > [0] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B) > [1] -1 0x00100000 - 0x3fffffff (0x3ff00000) > MX[B]E(B) > [2] -1 0x000f0000 - 0x000fffff (0x10000) MX[B] > [3] -1 0x000c0000 - 0x000effff (0x30000) MX[B] > [4] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B] > [5] -1 0xfdfffc00 - 0xfdfffc7f (0x80) MX[B] > [6] -1 0xff000000 - 0xff07ffff (0x80000) MX[B](B) > [7] -1 0xf8000000 - 0xfbffffff (0x4000000) MX[B](B) > [8] 0 0x000a0000 - 0x000affff (0x10000) MS[B] > [9] 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] > [10] 0 0x000b8000 - 0x000bffff (0x8000) MS[B] > [11] -1 0x0000ffff - 0x0000ffff (0x1) IX[B] > [12] -1 0x00000000 - 0x000000ff (0x100) IX[B] > [13] -1 0x0000ec80 - 0x0000ecff (0x80) IX[B] > [14] -1 0x0000dc80 - 0x0000dcbf (0x40) IX[B] > [15] -1 0x0000d800 - 0x0000d8ff (0x100) IX[B] > [16] -1 0x0000dcd0 - 0x0000dcdf (0x10) IX[B] > [17] -1 0x0000ff80 - 0x0000ff9f (0x20) IX[B] > [18] -1 0x0000ffa0 - 0x0000ffaf (0x10) IX[B] > [19] 0 0x000003b0 - 0x000003bb (0xc) IS[B] > [20] 0 0x000003c0 - 0x000003df (0x20) IS[B] > (II) Setting vga for screen 0. > (II) Loading sub module "vgahw" > (II) LoadModule: "vgahw" > (II) Loading /usr/X11R6/lib/modules/libvgahw.a > (II) Module vgahw: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 0.1.0 > ABI class: XFree86 Video Driver, version 0.5 > (**) I810(0): Depth 16, (--) framebuffer bpp 16 > (==) I810(0): RGB weight 565 > (==) I810(0): Default visual is TrueColor > (II) Loading sub module "vbe" > (II) LoadModule: "vbe" > (II) Loading /usr/X11R6/lib/modules/libvbe.a > (II) Module vbe: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 1.0.0 > ABI class: XFree86 Video Driver, version 0.5 > (II) Loading sub module "int10" > (II) LoadModule: "int10" > (II) Loading /usr/X11R6/lib/modules/linux/libint10.a > (II) Module int10: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 1.0.0 > ABI class: XFree86 Video Driver, version 0.5 > (II) I810(0): initializing int10 > (II) I810(0): Primary V_BIOS segment is: 0xc000 > (II) I810(0): VESA BIOS detected > (II) I810(0): VESA VBE Version 2.0 > (II) I810(0): VESA VBE Total Mem: 1024 kB > (II) I810(0): VESA VBE OEM: Intel810(TM) Graphics > Chip Accelerated VGA BIOS > (II) I810(0): VESA VBE OEM Software Rev: 2.20 > (II) I810(0): VESA VBE OEM Vendor: Intel Corporation > (II) I810(0): VESA VBE OEM Product: i810 Graphics > Controller > (II) I810(0): VESA VBE OEM Product Rev: Hardware > Version 0.0 > (II) Loading sub module "ddc" > (II) LoadModule: "ddc" > (II) Loading /usr/X11R6/lib/modules/libddc.a > (II) Module ddc: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 1.0.0 > ABI class: XFree86 Video Driver, version 0.5 > (II) I810(0): VESA VBE DDC supported > (II) I810(0): VESA VBE DDC Level 2 > (II) I810(0): VESA VBE DDC transfer in appr. 1 sec. > (II) I810(0): VESA VBE DDC read successfully > (II) I810(0): Manufacturer: DEL Model: a000 > Serial#: 842088775 > (II) I810(0): Year: 2000 Week: 47 > (II) I810(0): EDID Version: 1.2 > (II) I810(0): Analog Display Input, Input Voltage > Level: 0.700/0.300 V > (II) I810(0): Sync: Separate > (II) I810(0): Max H-Image Size [cm]: horiz.: 27 > vert.: 20 > (II) I810(0): Gamma: 2.87 > (II) I810(0): DPMS capabilities: StandBy Suspend > Off; RGB/Color Display > (II) I810(0): First detailed timing is preferred > mode > (II) I810(0): redX: 0.619 redY: 0.350 greenX: > 0.305 greenY: 0.600 > (II) I810(0): blueX: 0.154 blueY: 0.064 whiteX: > 0.280 whiteY: 0.311 > (II) I810(0): Supported VESA Video Modes: > (II) I810(0): 720x400@70Hz > (II) I810(0): 640x480@60Hz > (II) I810(0): 640x480@75Hz > (II) I810(0): 800x600@60Hz > (II) I810(0): 800x600@75Hz > (II) I810(0): 1024x768@60Hz > (II) I810(0): Manufacturer's mask: 0 > (II) I810(0): Supported Future Video Modes: > (II) I810(0): #0: hsize: 640 vsize 480 refresh: 85 > vid: 22833 > (II) I810(0): #1: hsize: 800 vsize 600 refresh: 85 > vid: 22853 > (II) I810(0): Supported additional Video Mode: > (II) I810(0): clock: 49.5 MHz Image Size: 270 x > 202 mm > (II) I810(0): h_active: 800 h_sync: 816 h_sync_end > 896 h_blank_end 1056 h_border: 0 > (II) I810(0): v_active: 600 v_sync: 601 v_sync_end > 604 v_blanking: 625 v_border: 0 > (II) I810(0): Serial No: 618GT0BE21AG > (II) I810(0): Monitor name: DELL E551 > (II) I810(0): Ranges: V min: 50 V max: 120 Hz, H > min: 30 H max: 54 kHz, PixClock max 70 MHz > (--) I810(0): Chipset: "i810e" > (--) I810(0): Linear framebuffer at 0xF8000000 > (--) I810(0): IO registers at addr 0xFF000000 > (II) I810(0): I810CheckAvailableMemory: 206844k > available > (**) I810(0): Will alloc AGP framebuffer: 16384 > kByte > (==) I810(0): Using gamma correction (1.0, 1.0, 1.0) > (II) I810(0): DELL E551: Using hsync range of > 30.00-54.00 kHz > (II) I810(0): DELL E551: Using vrefresh range of > 50.00-120.00 Hz > (II) I810(0): Clock range: 12.00 to 163.00 MHz > (II) I810(0): Not using default mode "320x175" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "320x200" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "360x200" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "320x240" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "320x240" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "320x240" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "320x240" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "400x300" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "400x300" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "400x300" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "400x300" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "400x300" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1024x768" > (unknown reason) > (II) I810(0): Not using default mode "512x384" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "512x384" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1024x768" > (hsync out of range) > (II) I810(0): Not using default mode "512x384" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1024x768" > (hsync out of range) > (II) I810(0): Not using default mode "512x384" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1024x768" > (hsync out of range) > (II) I810(0): Not using default mode "512x384" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1152x864" > (hsync out of range) > (II) I810(0): Not using default mode "576x432" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1280x960" > (hsync out of range) > (II) I810(0): Not using default mode "640x480" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1280x960" > (hsync out of range) > (II) I810(0): Not using default mode "640x480" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1280x1024" > (hsync out of range) > (II) I810(0): Not using default mode "640x512" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1280x1024" > (hsync out of range) > (II) I810(0): Not using default mode "640x512" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1280x1024" > (hsync out of range) > (II) I810(0): Not using default mode "640x512" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1600x1200" > (hsync out of range) > (II) I810(0): Not using default mode "800x600" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1600x1200" > (bad mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "800x600" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1600x1200" > (bad mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "800x600" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1600x1200" > (bad mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "800x600" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1600x1200" > (bad mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "800x600" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1792x1344" > (bad mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "896x672" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1792x1344" > (bad mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "896x672" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1856x1392" > (bad mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "928x696" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1856x1392" > (bad mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "928x696" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1920x1440" > (bad mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "960x720" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1920x1440" > (bad mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "960x720" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "416x312" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1400x1050" > (hsync out of range) > (II) I810(0): Not using default mode "700x525" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1400x1050" > (hsync out of range) > (II) I810(0): Not using default mode "700x525" (bad > mode clock/interlace/doublescan) > (II) I810(0): Not using default mode "1600x1024" > (hsync out of range) > (II) I810(0): Not using default mode "800x512" (bad > mode clock/interlace/doublescan) > (--) I810(0): Virtual size is 800x600 (pitch 1024) > (**) 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): Display dimensions: (270, 200) mm > (--) I810(0): DPI set to (75, 76) > (II) Loading sub module "fb" > (II) LoadModule: "fb" > (II) Loading /usr/X11R6/lib/modules/libfb.a > (II) Module fb: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 1.0.0 > ABI class: XFree86 ANSI C Emulation, version 0.1 > (II) Loading sub module "xaa" > (II) LoadModule: "xaa" > (II) Loading /usr/X11R6/lib/modules/libxaa.a > (II) Module xaa: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 1.0.0 > ABI class: XFree86 Video Driver, version 0.5 > (II) Loading sub module "ramdac" > (II) LoadModule: "ramdac" > (II) Loading /usr/X11R6/lib/modules/libramdac.a > (II) Module ramdac: vendor="The XFree86 Project" > compiled for 4.2.0, module version = 0.1.0 > ABI class: XFree86 Video Driver, version 0.5 > (II) I810(0): XvMC is Disabled: use XvMCSurfaces > config option to enable. > (II) do I need RAC? No, I don't. > (II) resource ranges after preInit: > [0] 0 0xff000000 - 0xff07ffff (0x80000) MS[B] > [1] 0 0xf8000000 - 0xfbffffff (0x4000000) MS[B] > [2] -1 0xffe00000 - 0xffffffff (0x200000) MX[B](B) > [3] -1 0x00100000 - 0x3fffffff (0x3ff00000) > MX[B]E(B) > [4] -1 0x000f0000 - 0x000fffff (0x10000) MX[B] > [5] -1 0x000c0000 - 0x000effff (0x30000) MX[B] > [6] -1 0x00000000 - 0x0009ffff (0xa0000) MX[B] > [7] -1 0xfdfffc00 - 0xfdfffc7f (0x80) MX[B] > [8] -1 0xff000000 - 0xff07ffff (0x80000) MX[B](B) > [9] -1 0xf8000000 - 0xfbffffff (0x4000000) MX[B](B) > [10] 0 0x000a0000 - 0x000affff (0x10000) > MS[B](OprD) > [11] 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD) > [12] 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD) > [13] -1 0x0000ffff - 0x0000ffff (0x1) IX[B] > [14] -1 0x00000000 - 0x000000ff (0x100) IX[B] > [15] -1 0x0000ec80 - 0x0000ecff (0x80) IX[B] > [16] -1 0x0000dc80 - 0x0000dcbf (0x40) IX[B] > [17] -1 0x0000d800 - 0x0000d8ff (0x100) IX[B] > [18] -1 0x0000dcd0 - 0x0000dcdf (0x10) IX[B] > [19] -1 0x0000ff80 - 0x0000ff9f (0x20) IX[B] > [20] -1 0x0000ffa0 - 0x0000ffaf (0x10) IX[B] > [21] 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) > [22] 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) > drmOpenDevice: minor is 0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is -1, (No such device) > drmOpenDevice: Open failed > drmOpenDevice: minor is 0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is -1, (No such device) > drmOpenDevice: Open failed > drmOpenDevice: minor is 0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is -1, (No such device) > drmOpenDevice: Open failed > drmOpenDevice: minor is 1 > drmOpenDevice: node name is /dev/dri/card1 > drmOpenDevice: open result is -1, (No such device) > drmOpenDevice: Open failed > drmOpenDevice: minor is 2 > drmOpenDevice: node name is /dev/dri/card2 > drmOpenDevice: open result is -1, (No such device) > drmOpenDevice: Open failed > drmOpenDevice: minor is 3 > drmOpenDevice: node name is /dev/dri/card3 > drmOpenDevice: open result is -1, (No such device) > drmOpenDevice: Open failed > drmOpenDevice: minor is 4 > drmOpenDevice: node name is /dev/dri/card4 > drmOpenDevice: open result is -1, (No such device) > drmOpenDevice: Open failed > drmOpenDevice: minor is 5 > drmOpenDevice: node name is /dev/dri/card5 > drmOpenDevice: open result is -1, (No such device) > drmOpenDevice: Open failed > drmOpenDevice: minor is 6 > drmOpenDevice: node name is /dev/dri/card6 > drmOpenDevice: open result is -1, (No such device) > drmOpenDevice: Open failed > drmOpenDevice: minor is 7 > drmOpenDevice: node name is /dev/dri/card7 > drmOpenDevice: open result is -1, (No such device) > drmOpenDevice: Open failed > drmOpenDevice: minor is 8 > drmOpenDevice: node name is /dev/dri/card8 > drmOpenDevice: open result is -1, (No such device) > drmOpenDevice: Open failed > drmOpenDevice: minor is 9 > drmOpenDevice: node name is /dev/dri/card9 > drmOpenDevice: open result is -1, (No such device) > drmOpenDevice: Open failed > drmOpenDevice: minor is 10 > drmOpenDevice: node name is /dev/dri/card10 > drmOpenDevice: open result is -1, (No such device) > drmOpenDevice: Open failed > drmOpenDevice: minor is 11 > drmOpenDevice: node name is /dev/dri/card11 > drmOpenDevice: open result is -1, (No such device) > drmOpenDevice: Open failed > drmOpenDevice: minor is 12 > drmOpenDevice: node name is /dev/dri/card12 > drmOpenDevice: open result is -1, (No such device) > drmOpenDevice: Open failed > drmOpenDevice: minor is 13 > drmOpenDevice: node name is /dev/dri/card13 > drmOpenDevice: open result is -1, (No such device) > drmOpenDevice: Open failed > drmOpenDevice: minor is 14 > drmOpenDevice: node name is /dev/dri/card14 > drmOpenDevice: open result is -1, (No such device) > drmOpenDevice: Open failed > drmOpenDevice: minor is 0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 7, (OK) > (II) I810(0): [drm] created "i810" driver at busid > "PCI:0:1:0" > (II) I810(0): [drm] added 8192 byte SAREA at > 0xcbb80000 > (II) I810(0): [drm] mapped SAREA 0xcbb80000 to > 0x40018000 > (II) I810(0): [drm] framebuffer handle = 0xf8000000 > (II) I810(0): [drm] added 1 reserved context for > kernel > (EE) I810(0): [dri] I810DRIScreenInit failed because > of a version mismatch. > [dri] i810.o kernel module version is 1.1.0 but > version 1.2 or greater is needed. > [dri] Disabling DRI. > (EE) I810(0): [drm] failed to remove DRM signal > handler > (II) I810(0): [drm] removed 1 reserved context for > kernel > DRIUnlock called when not locked > (II) I810(0): [drm] unmapping 8192 bytes of SAREA > 0xcbb80000 at 0x40018000 > (==) 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 56.3 MHz [ 0x3b > 0xb 0x30 ] [ 61 13 3 ] > (II) I810(0): chose watermark 0x22108000: (tab.freq > 56.3) > (II) I810(0): Adding 768 scanlines for pixmap > caching > (II) I810(0): Allocated Scratch Memory > (II) I810(0): Using XFree86 Acceleration > Architecture (XAA) > Screen to screen bit blits > Solid filled rectangles > 8x8 mono pattern filled rectangles > Indirect CPU to Screen color expansion > Solid Horizontal and Vertical Lines > Offscreen Pixmaps > Setting up tile and stipple cache: > 28 128x128 slots > 6 256x256 slots > (==) I810(0): Backing store disabled > (==) I810(0): Silken mouse enabled > (**) Option "dpms" > (**) I810(0): DPMS enabled > (==) I810(0): Direct rendering disabled > (II) Initializing built-in extension MIT-SHM > (II) Initializing built-in extension XInputExtension > (II) Initializing built-in extension XTEST > (II) Initializing built-in extension XKEYBOARD > (II) Initializing built-in extension LBX > (II) Initializing built-in extension XC-APPGROUP > (II) Initializing built-in extension SECURITY > (II) Initializing built-in extension XINERAMA > (II) Initializing built-in extension XFree86-Bigfont > (II) Initializing built-in extension RENDER > (**) Option "Protocol" "PS/2" > (**) Mouse0: Protocol: "PS/2" > (**) Option "CorePointer" > (**) Mouse0: Core Pointer > (**) Option "Device" "/dev/mouse" > (**) Option "Emulate3Buttons" "on" > (**) Mouse0: Emulate3Buttons, Emulate3Timeout: 50 > (**) Option "ZAxisMapping" "4 5" > (**) Mouse0: ZAxisMapping: buttons 4 and 5 > (**) Mouse0: Buttons: 5 > (II) Keyboard "Keyboard0" handled by legacy driver > (II) XINPUT: Adding extended input device "Mouse0" > (type: MOUSE) > pgetbl_ctl: 0xdc90001 pgetbl_err: 0x0 > ipeir: 0 iphdr: 50c00004 > LP ring tail: 1f18 head: 1e38 len: f001 start 2ac000 > eir: 0 esr: 0 emr: 3d > instdone: ff3a instpm: 0 > memmode: 4 instps: 810 > hwstam: 0 ier: 0 imr: 0 iir: 0 > space: 65304 wanted 65528 > > Fatal server error: > lockup > > > When reporting a problem related to a server crash, > please send > the full server output, not just the last messages. > This can be found in the log file > "/var/log/XFree86.0.log". > Please report problems to xfree86@xfree86.org. > > pgetbl_ctl: 0xdc90001 pgetbl_err: 0x0 > ipeir: 0 iphdr: 50c00004 > LP ring tail: 1f20 head: 1e38 len: f001 start 2ac000 > eir: 0 esr: 0 emr: 3d > instdone: ff3a instpm: 0 > memmode: 4 instps: 810 > hwstam: 0 ier: 0 imr: 0 iir: 0 > space: 65296 wanted 65528 > > FatalError re-entered, aborting > lockup > > > --__--__-- > > Message: 10 > From: Ola Theander <ola.theander@connective.se> > To: "'newbie@XFree86.Org'" <newbie@XFree86.Org> > Date: Thu, 18 Apr 2002 15:49:47 +0200 > Subject: [Newbie]Prblm: Configure ATI Mobile M4 with > XFree86 4.2.0. > Reply-To: newbie@XFree86.Org > > Dear subscribers. > > I've recently upgraded to XFree86 on my Dell > Inspiron 8000 laptop, hoping to > solve a problem that sometimes occur when I shut > down my KDE 2.2.1 > installation to get back to the shell. The problem > is that KDE hangs and the > items on the screen fades away in some strange > graphics effect. It looks > pretty much like burning paper. After this the KDE > is totally locked. The > only thing that helps is to turn off the power. > > In a posting I received regarding the above problem > I was given the > suggestion that I should upgrade my XFree86 server > since this is, according > to the author of the letter, a problem with XFree86 > and APM. Since I'm > running SuSE 7.3 Professional I downloaded the > upgrade rpm:s from their site > and started the upgrade. The upgrade went fine as > far as I can tell but I > have a problem with the XF86Config file. I've only > managed to use the > generic vesa driver. If I try the r128 driver, the > XFree86 server won't > start, complaining that there is no suitable screen. > I figure that this > might have to do with the refresh rates and > resolution settings. > > I've generated a XF86Config file by running > xf86config, using generic driver > options. Then I toggled the options regarding the > driver to r128. The > problem is that if I use the r128 driver the server > can't find a suitable > screen. If I use VESA everything seems to work OK. > The only thing I change > is the driver name on line 370-371 in the XF86Config > file. > > The XFree86 configuration- and log files when the > r128 and the vesa driver > respectively can be viewed by the following links: > > XF86Config: > http://www.nada.kth.se/~u1sx5mht/XFreeQ1/XF86Config > r128 log: > http://www.nada.kth.se/~u1sx5mht/XFreeQ1/XFree86_r128log > vesa log: > http://www.nada.kth.se/~u1sx5mht/XFreeQ1/XFree86_vesalog > > Technical data for my computer: > > Name: Dell Inspirion 8000 > Graphics adapter: ATI Mobilitiy M4 (detected by SAX2 > as a ATI Rage 128 > Mobility MF) Memory on the adapter: 32 MB > Screen: 15" TFT, 1600x1200x60Hz recommended > resolution. > > I'm hoping that any of you out there can point me in > the right direction. > > Kind regards, Ola Theander > > --__--__-- > > Message: 11 > Date: Fri, 19 Apr 2002 13:59:00 +1200 (NZST) > From: "Ryurick M. Hristev" > <r.hristev@phys.canterbury.ac.nz> > Subject: Re: [Newbie]Prblm: Configure ATI Mobile M4 > with XFree86 4.2.0. > To: "'newbie@XFree86.Org'" <newbie@XFree86.Org> > Reply-To: newbie@XFree86.Org > > On Thu, 18 Apr 2002, Ola Theander wrote: > > > Dear subscribers. > > > > I've recently upgraded to XFree86 on my Dell > Inspiron 8000 laptop, hoping to > > solve a problem that sometimes occur when I shut > down my KDE 2.2.1 > > installation to get back to the shell. The problem > is that KDE hangs and the > > items on the screen fades away in some strange > graphics effect. It looks > > pretty much like burning paper. After this the KDE > is totally locked. The > > only thing that helps is to turn off the power. > > 1. What FlashBIOS are you using ? > Early ones were quire buggy, the latest A18 & A19 > seems to have a problem > with the fans. It probably pays to upgrade to A17 > if you have an earlier > one (I had similar problems with earlier BIOSes) > > 2. With respect to X modes: Dell offers > atimp310.rpm, atimp312.rpm > and atimp314.rpm which contains each a > XF86Config-4 for > various screen resolutions. > > Cheers, > -- > Ryurick M. Hristev > mailto:r.hristev@phys.canterbury.ac.nz > Computer Systems Manager > University of Canterbury, Physics & Astronomy Dept., > New Zealand > > > --__--__-- > > Message: 12 > Date: Thu, 18 Apr 2002 11:01:03 -0400 > Subject: Re: [Newbie]Can't get Trident graphics > working > From: "Hubert Yoshizaki" <hyoshiza@onebox.com> > To: newbie@XFree86.Org > Reply-To: newbie@XFree86.Org > > Hi there, > Don't know if someone answered this one already but > in anycase, > seems to me that you have a config problem (no duh > ;). > I would try a lower resolution with slower refresh > frequency. Go with > something modest then go upwards. > > Hubert > > > > > > ---- John Malick <john@starinc.com> wrote: > > I think I'm just abou there but the graphics comes > up clearly with > > a > > sync issue. There are vertical colored lines from > top to bottom and > > you > > can just barely make out the gnome session. > > > > My graphics card is the Tridend card with 9668 > chipset and 2MB video > > > > ram. My monitor is a multsync monitor, no brand > name. Acutally the > > only > > name on it is Leo but it supports anywhere from > 30-50Khz and 40-70Hz > > .. > > > > My XFree86 server is 4.0.1a. > > > > Does anyone have a working XF86Config file for > this Trident card that > > > > they can shoot over to me? > > > > Thank You > > > > _______________________________________________ > > > > Newbie@XFree86.Org > > *** To unsubscribe , or change message options, > see: > > http://XFree86.Org/mailman/listinfo/newbie > > > > --__--__-- > > Message: 13 > From: Bill Winegarden <basic@netidea.com> > To: newbie@XFree86.Org > Subject: Re: [Newbie]Prblm: Configure ATI Mobile M4 > with XFree86 4.2.0. > Date: Thu, 18 Apr 2002 19:48:19 -0700 > Reply-To: newbie@XFree86.Org > > Hi, > Just following the thread......I have an I8K > running LM8.2 . When I upgraded > from 8.1 (XFree86 4.2.0) I could not get any > resolutions other than > 1400x1050. So I set up all my font sizes to > compensate. > Are the listed rpms good on 8.2? Have you tried > them? > > tia, > Bill W. > > > On Thursday 18 April 2002 06:59 pm, you wrote: > > On Thu, 18 Apr 2002, Ola Theander wrote: > > > Dear subscribers. > > > > > > I've recently upgraded to XFree86 on my Dell > Inspiron 8000 laptop, hoping > > > to solve a problem that sometimes occur when I > shut down my KDE 2.2.1 > > > installation to get back to the shell. The > problem is that KDE hangs and > > > the items on the screen fades away in some > strange graphics effect. It > > > looks pretty much like burning paper. After this > the KDE is totally > > > locked. The only thing that helps is to turn off > the power. > > > > 1. What FlashBIOS are you using ? > > Early ones were quire buggy, the latest A18 & > A19 seems to have a > > problem with the fans. It probably pays to upgrade > to A17 if you have an > > earlier one (I had similar problems with earlier > BIOSes) > > > > 2. With respect to X modes: Dell offers > atimp310.rpm, atimp312.rpm > > and atimp314.rpm which contains each a > XF86Config-4 for > > various screen resolutions. > > > > Cheers, > > --__--__-- > > Message: 14 > Date: Fri, 19 Apr 2002 16:10:16 +1200 (NZST) > From: "Ryurick M. Hristev" > <r.hristev@phys.canterbury.ac.nz> > Subject: Re: [Newbie]Prblm: Configure ATI Mobile M4 > with XFree86 4.2.0. > To: newbie@XFree86.Org > Reply-To: newbie@XFree86.Org > > On Thu, 18 Apr 2002, Bill Winegarden wrote: > > > Just following the thread......I have an I8K > running LM8.2 . When I upgraded > > from 8.1 (XFree86 4.2.0) I could not get any > resolutions other than > > 1400x1050. So I set up all my font sizes to > compensate. > > Are the listed rpms good on 8.2? Have you tried > them? > > The listed rpms contain just the XF86Config-4 files > with just one modeline. > > I am myself after a 800x600 modeline which would > work on the I8k LCD, > as I think is related to the tv output I am trying > to make it work. > > Cheers, > -- > Ryurick M. Hristev > mailto:r.hristev@phys.canterbury.ac.nz > Computer Systems Manager > University of Canterbury, Physics & Astronomy Dept., > New Zealand > > > --__--__-- > > Message: 15 > From: "Yu-Chan Park" <super@linuxone.co.kr> > To: <newbie@XFree86.Org> > Date: Fri, 19 Apr 2002 14:45:23 +0900 > Subject: [Newbie]help me.. about libbitmap.a > Reply-To: newbie@XFree86.Org > > Hello.. > > If i execute my Xserver which version is 4.1.0 then > error occurred libbitmap.a which is > unresolved . > > why is it occurred? > > My XFree86.0.log as follow.. > > XFree86 version is 4.1.0 > Xaw3d is 1.5 > binutils is 2.11.90.0.8 > Mesa is 3.4.2 > > Thanks.. > =========================================== > > XFree86 Version 4.1.0 (Unofficial Build: 4.1.0-35) / > X Window System > (protocol Version 11, revision 0, vendor release > 6510) > Release Date: 2 June 2001 > If the server is older than 6-12 months, or if your > card is > newer than the above date, look for a newer version > before > reporting problems. (See > http://www.XFree86.Org/FAQ) > Build Operating System: Linux 2.4.18-24 i686 [ELF] > Build Host: ip50.inside.linuxone.co.kr > > Module Loader present > (==) Log file: "/var/log/XFree86.0.log", Time: Thu > Apr 18 17:51:45 2002 > (==) Using config file: "/etc/X11/XF86Config-4" > Markers: (--) probed, (**) from config file, (==) > default setting, > (++) from command line, (!!) notice, (II) > informational, > (WW) warning, (EE) error, (NI) not > implemented, (??) unknown. > (==) ServerLayout "XFree86 Configured" > (**) |-->Screen "Screen0" (0) > (**) | |-->Monitor "SAM1057" > (**) | |-->Device "Trident TGUI9660 (generic)" > (**) |-->Input Device "Mouse0" > (**) |-->Input Device "Keyboard0" > (**) Option "XkbDisable" > (**) XKB: disabled > (==) Keyboard: CustomKeycode disabled > (WW) The directory > "/usr/X11R6/lib/X11/fonts/CIDkeyed/" does not exist. > Entry deleted from font path. > (**) FontPath set to > "/usr/X11R6/lib/X11/fonts/mookhyang/,/usr/X11R6/lib/X11/fonts/korean/,/usr/X11R6/lib/X11/fonts/misc/:unscaled,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/cyrillic/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/local/,/usr/X11R6/lib/X11/fonts/latin2/Type1/,/usr/X11R6/lib/X11/fonts/japanese/,/usr/X11R6/lib/X11/fonts/844-ksc-pcf/,/usr/X11R6/lib/X11/fonts/sgi/misc/,/usr/share/fonts/default/TrueType/,/usr/share/fonts/default/Type1/,/usr/share/AbiSuite/fonts/,/usr/share/fonts/ja/TrueType/,/usr/share/fonts/ISO8859-7/misc/:unscaled,/usr/share/fonts/ISO8859-7/75dpi/:unscaled,/usr/share/fonts/ISO8859-7/100dpi/:unscaled,/usr/share/fonts/ISO8859-7/misc/,/usr/share/fonts/ISO8859-7/Type1/,/usr/share/fonts/ISO8859-7/75dpi/,/usr/share/fonts/ISO8859-7/100dpi/,/usr/share/fonts/KOI8-R/misc/:unscaled,/usr/sh! > are/fonts/KOI8-R/75dpi/:unscaled,/usr/s(==) RgbPath > set to "/usr/X11R6/lib/X11/rgb" > (==) ModulePath set to "/usr/X11R6/lib/modules" > (--) using VT number 7 > > (II) Open APM successful > (II) Module ABI versions: > XFree86 ANSI C Emulation: 0.1 > XFree86 Video Driver: 0.4 > XFree86 XInput driver : 0.2 > XFree86 Server Extension : 0.1 > XFree86 Font Renderer : 0.2 > (II) Loader running on linux > (II) LoadModule: "bitmap" > (II) Loading > /usr/X11R6/lib/modules/fonts/libbitmap.a > Not loading .rodata.str1.1 > Not loading .rodata.str1.32 > Not loading .rodata.cst8 > Not loading .rodata.str1.1 > Not loading .rodata.str1.32 > Not loading .rodata.str1.1 > Not loading .rodata.cst8 > Not loading .rodata.str1.1 > Not loading .rodata.str1.32 > Not loading .rodata.str1.1 > (II) Symbol .LC2 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC2 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC0 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC9 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC19 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC71 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC71 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC71 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC3 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC0 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC67 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC0 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC0 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC0 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC0 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC0 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC0 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC0 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC0 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC1 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC0 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > Symbol .LC0 from module > /usr/X11R6/lib/modules/fonts/libbitmap.a is > unresolved! > > Fatal server error: > Caught signal 11. Server aborting > > > When reporting a problem related to a server crash, > please send > the full server output, not just the last messages. > This can be found in the log file > "/var/log/XFree86.0.log". > Please report problems to xfree86@xfree86.org. > > --__--__-- > > Message: 16 > Date: Fri, 19 Apr 2002 09:02:32 +0400 > From: FiX{x}XeR <fixxxer@caddeon.net> > To: newbie@XFree86.Org > Subject: [Newbie]OpenBSD3.0 XWin Problems > Reply-To: newbie@XFree86.Org > > This is a multi-part message in MIME format. > > --Boundary_(ID_8c4oSeTS3icuvc6Gx+B2wQ) > Content-type: text/plain; charset=iso-8859-1 > Content-transfer-encoding: 7BIT > > Hi, > I just installed OpenBSD. To tell the truth I am a > complete newbie. So what I did was to try to > configure the Xwin by typing xf86config. I did not > know anything about my monitor. Only thing I know is > it is PanaSyncS110 21". Since I dont know anything I > choose something from the menu. The configration was > fine. Now comes the tricky part. I wrote startx and > it started it fits the screen and all that was ok. > But my mouse I could not move it. If I move it, it > always goes to top of the screen and all that. I > have an Intelli Mouse and I am sure that I chose > that when I was configureing it. > (Note: And the colors was like 16bit. It sucked. I > have Geforce2 MX which is 320 in the list.) > Best Regards > > --Boundary_(ID_8c4oSeTS3icuvc6Gx+B2wQ) > Content-type: text/html; charset=iso-8859-1 > Content-transfer-encoding: 7BIT > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 > Transitional//EN"> > <HTML><HEAD> > <META http-equiv=Content-Type content="text/html; > charset=iso-8859-1"> > <META content="MSHTML 6.00.2713.1100" > name=GENERATOR> > <STYLE></STYLE> > </HEAD> > <BODY bgColor=#ffffff> > <DIV><FONT face=Arial size=2>Hi,</FONT></DIV> > <DIV><FONT face=Arial size=2>I just installed > OpenBSD. To tell the truth I am a > complete newbie. So what I did was to try to > configure the Xwin by typing > xf86config. I did not know anything about my > monitor. Only thing I know is it is > PanaSyncS110 21". Since I dont know anything I > choose something from the menu. > The configration was fine. Now comes the tricky > part. I wrote startx and it > started it fits the screen and all that was ok. But > my mouse I could not move > it. If I move it, it always goes to top of the > screen and all that. I have an > Intelli Mouse and I am sure that I chose that when I > was configureing it. > </FONT></DIV> > <DIV><FONT face=Arial size=2>(Note: And the colors > was like 16bit. It sucked. I > have Geforce2 MX which is 320 in the > list.)</FONT></DIV> > <DIV><FONT face=Arial size=2>Best > Regards</FONT></DIV></BODY></HTML> > > --Boundary_(ID_8c4oSeTS3icuvc6Gx+B2wQ)-- > > --__--__-- > > Message: 17 > Subject: RE: [Newbie]OpenBSD3.0 XWin Problems > Date: Fri, 19 Apr 2002 10:02:41 +0200 > From: =?iso-8859-1?Q?Fredrik_W=E4nglund?= > <Fredrik.Wanglund@datavis.se> > To: <newbie@XFree86.Org> > Reply-To: newbie@XFree86.Org > > I think there is a lot of postings on this topic.. > > Try to disable gpm before you start X. > > put '/etc/init.d/gpm stop' or 'killall gp' in your > startx-script > > > -----Original Message----- > From: FiX{x}XeR [mailto:fixxxer@caddeon.net] > Sent: Fri 19-Apr-02 07:02 > To: newbie@XFree86.Org > Cc: > Subject: [Newbie]OpenBSD3.0 XWin Problems > > Hi, > I just installed OpenBSD. To tell the truth I am a > complete newbie. So what I did was to try to > configure the Xwin by typing xf86config. I did not > know anything about my monitor. Only thing I know is > it is PanaSyncS110 21". Since I dont know anything I > choose something from the menu. The configration was > fine. Now comes the tricky part. I wrote startx and > it started it fits the screen and all that was ok. > But my mouse I could not move it. If I move it, it > always goes to top of the screen and all that. I > have an Intelli Mouse and I am sure that I chose > that when I was configureing it. > (Note: And the colors was like 16bit. It sucked. I > have Geforce2 MX which is 320 in the list.) > Best Regards > > > > > --__--__-- > > Message: 18 > Date: Fri, 19 Apr 2002 14:19:32 +0200 > From: "Isak Lyberth" <ily@cip-global.com> > To: <newbie@XFree86.Org> > Subject: [Newbie]Changing amount of colors in x? > Reply-To: newbie@XFree86.Org > > Wich file do I need to edit to change the amount of > colors in x? > I have a toshiba Satelite 4000CDS with OpenBSD > installed and it runs > 4.2.0. > The basic XF86Config is created by xf86cfg, but I > cant seem to change > the amount of colors in that. > If I use xf86config the mouse screws up. So I just > need to know what to > edit in wich file > > Regards > Isak Lyberth > Corporate Information Partners > Postbox 183, Havneparken 14a > DK - 7100 Vejle > -------------------------------------- > Reception: +45 7640 9940 (Monday to Thursday 8.30 to > 16.00 and Fridays > 8.30 to 15.30 CET) > Fax: +45 7640 9941 > -------------------------------------- > E-mail: > Isak.Lyberth@cip-global.com<mailto:Isak.Lyberth@cip-global.com> > > WEB: <http://www.cip-global.com/> > Building Solutions for Better Decisions (tm) > The information transmitted is intended only for the > person or entity to > which it is addressed and may contain confidential > and/or privileged > material. > Any review, retransmission, dissemination or other > use of, or taking of > any action in reliance upon, this information by > persons or entities > other than > the intended recipient is prohibited. If you > received this in error, > please contact the sender and delete the material > from any computer. > > > --__--__-- > > Message: 19 > From: Ola Theander <ola.theander@connective.se> > To: "'newbie@XFree86.Org'" <newbie@XFree86.Org> > Subject: RE: [Newbie]Prblm: Configure ATI Mobile M4 > with XFree86 4.2.0. > Date: Fri, 19 Apr 2002 19:09:53 +0200 > Reply-To: newbie@XFree86.Org > > Hi Ryurick. > > Thanks for your answer. I guess you referring to the > Dell BIOSes when you > mention A17 etc? I'll check the version I have. > > Regarding the XF86Config files from Dell, I've tried > the one that's for my > screen resolution (1600x1200) but it was the same > problem, i.e. the start up > process complained that no suitable screens where > found. I've had it working > with properly with XFree86 4.1.0, but the upgrade > process trashed my > XF86Config file since the computer locked with the > fade effect mentioned in > my earlier letter at an unfortunate moment, and I > don't know what settings I > had with 4.1.0 since I used the automatic > configuration made by the SuSE > install. Perhaps it might be something else than the > XF86Config file that's > wrong but the installation of version 4.2.0 appeared > to go well. > > Kind regards, Ola Theander > > > -----Original Message----- > > From: Ryurick M. Hristev > [mailto:r.hristev@phys.canterbury.ac.nz] > > Sent: den 19 april 2002 03:59 > > To: 'newbie@XFree86.Org' > > Subject: Re: [Newbie]Prblm: Configure ATI Mobile > M4 with > > XFree86 4.2.0. > > > > > > On Thu, 18 Apr 2002, Ola Theander wrote: > > > > > Dear subscribers. > > > > > > I've recently upgraded to XFree86 on my Dell > Inspiron 8000 laptop, > > > hoping to solve a problem that sometimes occur > when I shut > > down my KDE > > > 2.2.1 installation to get back to the shell. The > problem is > > that KDE > > > hangs and the items on the screen fades away in > some > > strange graphics > > > effect. It looks pretty much like burning paper. > After this > > the KDE is > > > totally locked. The only thing that helps is to > turn off the power. > > > > 1. What FlashBIOS are you using ? > > Early ones were quire buggy, the latest A18 & > A19 seems to > > have a problem > > with the fans. It probably pays to upgrade to > A17 if you > > have an earlier > > one (I had similar problems with earlier > BIOSes) > > > > 2. With respect to X modes: Dell offers > atimp310.rpm, atimp312.rpm > > and atimp314.rpm which contains each a > XF86Config-4 for > > various screen resolutions. > > > > Cheers, > > -- > > Ryurick M. Hristev > mailto:r.hristev@phys.canterbury.ac.nz > > Computer Systems Manager > > University of Canterbury, Physics & Astronomy > Dept., New Zealand > > > > _______________________________________________ > > > > Newbie@XFree86.Org > > *** To unsubscribe , or change message options, > see: > > http://XFree86.Org/mailman/listinfo/newbie > > > > --__--__-- > > Message: 20 > Date: Fri, 19 Apr 2002 20:29:53 +0400 > From: FiX{x}XeR <fixxxer@caddeon.net> > Subject: Re: [Newbie]OpenBSD3.0 XWin Problems > To: newbie@XFree86.Org > Reply-To: newbie@XFree86.Org > > As I said "I am a complete newbie". > I think you ment editing the startx file > so what I did was > vi startx > and in startx I added the line '/etc/init.d/gpm > stop' > When I write startx it says '/etc/init.d/gpm' no > such directory... > ----- Original Message ----- > From: "Fredrik Wänglund" > <Fredrik.Wanglund@datavis.se> > To: <newbie@XFree86.Org> > Sent: Friday, April 19, 2002 12:02 PM > Subject: RE: [Newbie]OpenBSD3.0 XWin Problems > > > > I think there is a lot of postings on this topic.. > > > > Try to disable gpm before you start X. > > > > put '/etc/init.d/gpm stop' or 'killall gp' in your > startx-script > > > > > > -----Original Message----- > > From: FiX{x}XeR [mailto:fixxxer@caddeon.net] > > Sent: Fri 19-Apr-02 07:02 > > To: newbie@XFree86.Org > > Cc: > > Subject: [Newbie]OpenBSD3.0 XWin Problems > > > > Hi, > > I just installed OpenBSD. To tell the truth I am a > complete newbie. So > what I did was to try to configure the Xwin by > typing xf86config. I did not > know anything about my monitor. Only thing I know is > it is PanaSyncS110 21". > Since I dont know anything I choose something from > the menu. The > configration was fine. Now comes the tricky part. I > wrote startx and it > started it fits the screen and all that was ok. But > my mouse I could not > move it. If I move it, it always goes to top of the > screen and all that. I > have an Intelli Mouse and I am sure that I chose > that when I was > configureing it. > > (Note: And the colors was like 16bit. It sucked. I > have Geforce2 MX which > is 320 in the list.) > > Best Regards > > > > > > > > _______________________________________________ > > > > Newbie@XFree86.Org > > *** To unsubscribe , or change message options, > see: > > http://XFree86.Org/mailman/listinfo/newbie > > > --__--__-- > > Message: 21 > From: marc brady > <mandrakeexpert@expressindustrial.com.au> > To: Newbie@XFree86.Org > Date: Fri, 19 Apr 2002 01:32:18 -0400 > Subject: [Newbie]Re: XFree-4.2 > Reply-To: newbie@XFree86.Org > > On Friday 19 April 2002 01:03 am, you wrote: > > > > > > > On Friday 19 April 2002 01:02 am, you wrote: > > > can some one please look at this and help me > with this error > > > > > > thank you > > > > > > marc brady > > > > > > cleaning in ./nls > > > make:entering unknown directory > > > make: *** nls:not a file or directory. Stop > > > make: leaving unknown directory > > > make{1}:**** {clean} error 2 > > > make{1}: leaving directory /usr/src/xc > > > make: *** [World] Error 2 > > > > > > any one have a clue???? > > --__--__-- > > Message: 22 > Date: Fri, 19 Apr 2002 20:31:27 +0400 > From: FiX{x}XeR <fixxxer@caddeon.net> > To: newbie@XFree86.Org > Subject: [Newbie]Monitor PanaSync S110 Help > Reply-To: newbie@XFree86.Org > > This is a multi-part message in MIME format. > > --Boundary_(ID_VKBqjyb48AfBsU/tX6rbnQ) > Content-type: text/plain; charset=iso-8859-1 > Content-transfer-encoding: 7BIT > > Hi, > I need help with configuring this monitor Panasonic > PanaSyncS110 21". > While I am configuring Xwindows what should my > configuration be? > The range and stuff.. > Thanx > > --Boundary_(ID_VKBqjyb48AfBsU/tX6rbnQ) > Content-type: text/html; charset=iso-8859-1 > Content-transfer-encoding: 7BIT > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 > Transitional//EN"> > <HTML><HEAD> > <META http-equiv=Content-Type content="text/html; > charset=iso-8859-1"> > <META content="MSHTML 6.00.2713.1100" > name=GENERATOR> > <STYLE></STYLE> > </HEAD> > <BODY bgColor=#ffffff> > <DIV><FONT face=Arial size=2>Hi, </FONT></DIV> > <DIV><FONT face=Arial size=2>I need help with > configuring this monitor Panasonic > PanaSyncS110 21".</FONT></DIV> > <DIV><FONT face=Arial size=2>While I am configuring > Xwindows what should my > configuration be?</FONT></DIV> > <DIV><FONT face=Arial size=2>The range and > stuff..</FONT></DIV> > <DIV><FONT face=Arial > size=2>Thanx</FONT></DIV></BODY></HTML> > > --Boundary_(ID_VKBqjyb48AfBsU/tX6rbnQ)-- > > --__--__-- > > Message: 23 > Date: Sat, 20 Apr 2002 06:29:20 +1200 (NZST) > From: "Ryurick M. Hristev" > <r.hristev@phys.canterbury.ac.nz> > Subject: RE: [Newbie]Prblm: Configure ATI Mobile M4 > with XFree86 4.2.0. > To: "'newbie@XFree86.Org'" <newbie@XFree86.Org> > Reply-To: newbie@XFree86.Org > > On Fri, 19 Apr 2002, Ola Theander wrote: > > > I guess you referring to the Dell BIOSes when you > > mention A17 etc? > > Yes. > > > and I don't know what settings I > > had with 4.1.0 since I used the automatic > configuration made by the SuSE > > install. > > Well what can I say, the backup of /etc directory at > least > is a good idea, you could do it from crontab at > least on the HD :-) > > Cheers, > -- > Ryurick M. Hristev > mailto:r.hristev@phys.canterbury.ac.nz > Computer Systems Manager > University of Canterbury, Physics & Astronomy Dept., > New Zealand > > > > --__--__-- > > _______________________________________________ > > Newbie@XFree86.Org > http://XFree86.Org/mailman/listinfo/newbie > > > End of Newbie Digest __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/
