Re: XFree86 4.0.1 with Intel I810
Greetings Theppitak; I have two guesses to the source of your problem. The first possibility is the "vbe" module is not being loaded, but the i810 driver is trying to load something that deals with vbe. Try adding the following to your Module section: Load "vbe" The second possibility is your kernel version has a different AGPGART interface than X expects. I currently run X4.0.1-1 on Linux 2.4.0-test10 with good results. I have heard that recent versions of 2.2 (2.2.17 or so?) also work well. You need to compile AGP support into your kernel (either directly in, or as a module, I believe. I would suggest module to help keep the size of the kernel small), and your kernel needs to be recent enough. (Also ensure the /dev/agpgart file is a character file with reasonable permissions. :) There is another possibility that something else entirely is the cause, in which case I wish you luck. :) * Theppitak Karoonboonayanan <[EMAIL PROTECTED]> [001107 03:22]: > Section "Module" > > # This loads the DBE extension module. > > Load"dbe" # Double buffer extension > > # This loads the miscellaneous extensions module, and disables > # initialisation of the XFree86-DGA extension within that module. > SubSection "extmod" > Option"omit xfree86-dga" # don't initialise the DGA extension > EndSubSection > > # This loads the Type1 and FreeType font modules > Load"type1" > Load"freetype" > > # This loads the GLX module > #Load "glx" > > EndSection > (II) Loading /usr/X11R6/lib/modules/libramdac.a > (II) Module ramdac: vendor="The XFree86 Project" > compiled for 4.0.1d, module version = 0.1.0 > Symbol VBEInit from module /usr/X11R6/lib/modules/drivers/i810_drv.o is > unresolved! > Symbol vbeDoEDID from module /usr/X11R6/lib/modules/drivers/i810_drv.o is > unresolved! > (==) Depth 24 pixmap format is 32 bpp > (==) I810(0): Write-combining range (0xd000,0x200) > (II) I810(0): Setting dot clock to 36.0 MHz [ 0x10 0x1 0x40 ] [ 18 3 4 ] > (II) I810(0): chose watermark 0x2210c000: (tab.freq 36.0) > (WW) AGPIOC_ACQUIRE failed (Inappropriate ioctl for device) > (EE) GARTInit: AGPIOC_INFO failed (Inappropriate ioctl for device) > > Fatal server error: > AddScreen/ScreenInit failed for driver 0 -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: screen size
* Pierfrancesco Caci <[EMAIL PROTECTED]> [001107 09:45]: > Is there a way to force this setting or alternatively the DPI setting? DPI can be changed (at least in some fashion) by changing /etc/X11/xinit/xserverrc, or by passing arguments to the server via "startx -- -dpi ..." startx(1), xinit(1), Xserver(1), XFree86(1) have information on possible arguments that can be passed. As for size, the only mention I found is that it queries the hardware for this information. I don't think you can over-ride that directly, only through the DPI setting. -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: X3.6/4 (woody) ct-Driver lockups
* Dan Christensen <[EMAIL PROTECTED]> [001107 09:39]: > My machine also freezes completely when I try the new X. I have the > same card, the CT6, in my Transmonde laptop, and the machine dies > when I run startx or "/etc/init.d/xdm start". Several people have reported that having a fontserver listed in their XF86Config-4 files (such as "unix:/7100" (or is it "unix/:7100"?)) causes X to hang, crash, or both. (I forget which combinations people have seen.) Try removing the reference to a font server (or install a font server :) from your XF86Config-4 file. -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XFree86 4.0.1 with Intel I810
Greetings Theppitak; I have two guesses to the source of your problem. The first possibility is the "vbe" module is not being loaded, but the i810 driver is trying to load something that deals with vbe. Try adding the following to your Module section: Load "vbe" The second possibility is your kernel version has a different AGPGART interface than X expects. I currently run X4.0.1-1 on Linux 2.4.0-test10 with good results. I have heard that recent versions of 2.2 (2.2.17 or so?) also work well. You need to compile AGP support into your kernel (either directly in, or as a module, I believe. I would suggest module to help keep the size of the kernel small), and your kernel needs to be recent enough. (Also ensure the /dev/agpgart file is a character file with reasonable permissions. :) There is another possibility that something else entirely is the cause, in which case I wish you luck. :) * Theppitak Karoonboonayanan <[EMAIL PROTECTED]> [001107 03:22]: > Section "Module" > > # This loads the DBE extension module. > > Load"dbe" # Double buffer extension > > # This loads the miscellaneous extensions module, and disables > # initialisation of the XFree86-DGA extension within that module. > SubSection "extmod" > Option"omit xfree86-dga" # don't initialise the DGA extension > EndSubSection > > # This loads the Type1 and FreeType font modules > Load"type1" > Load"freetype" > > # This loads the GLX module > #Load "glx" > > EndSection > (II) Loading /usr/X11R6/lib/modules/libramdac.a > (II) Module ramdac: vendor="The XFree86 Project" > compiled for 4.0.1d, module version = 0.1.0 > Symbol VBEInit from module /usr/X11R6/lib/modules/drivers/i810_drv.o is unresolved! > Symbol vbeDoEDID from module /usr/X11R6/lib/modules/drivers/i810_drv.o is unresolved! > (==) Depth 24 pixmap format is 32 bpp > (==) I810(0): Write-combining range (0xd000,0x200) > (II) I810(0): Setting dot clock to 36.0 MHz [ 0x10 0x1 0x40 ] [ 18 3 4 ] > (II) I810(0): chose watermark 0x2210c000: (tab.freq 36.0) > (WW) AGPIOC_ACQUIRE failed (Inappropriate ioctl for device) > (EE) GARTInit: AGPIOC_INFO failed (Inappropriate ioctl for device) > > Fatal server error: > AddScreen/ScreenInit failed for driver 0 -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XFree86 4.0.1 doesn't detect Permedia2 chip
Michael, not having a Permedia card, I can't promise great results. However, I have an idea... * Michael Neuffer <[EMAIL PROTECTED]> [001107 00:31]: > (II) GLINT: driver for 3Dlabs chipsets: gamma, ti_pm2, ti_pm, pm3, pm2v, > pm2, pm, 300sx, 500tx, mx > (WW) GLINT: No matching Device section for instance (BusID PCI:0:13:0) found > (EE) No devices detected. > > Fatal server error: > no screens found Based on the WW line, I suggest adding a device section to you XF86Config-4 (or modifying the one you have) to say something similar to what mine says: Section "Device" Identifier "G400_0" Driver "mga" VendorName "Matrox" BoardName "MGA G400 AGP" BusID "PCI:1:0:0" Screen 0 EndSection Note the "BusID" line. :) HTH -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: XFree86 4.0.1 doesn't detect Permedia2 chip
Michael, not having a Permedia card, I can't promise great results. However, I have an idea... * Michael Neuffer <[EMAIL PROTECTED]> [001107 00:31]: > (II) GLINT: driver for 3Dlabs chipsets: gamma, ti_pm2, ti_pm, pm3, pm2v, > pm2, pm, 300sx, 500tx, mx > (WW) GLINT: No matching Device section for instance (BusID PCI:0:13:0) found > (EE) No devices detected. > > Fatal server error: > no screens found Based on the WW line, I suggest adding a device section to you XF86Config-4 (or modifying the one you have) to say something similar to what mine says: Section "Device" Identifier "G400_0" Driver "mga" VendorName "Matrox" BoardName "MGA G400 AGP" BusID "PCI:1:0:0" Screen 0 EndSection Note the "BusID" line. :) HTH -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [andrew_pmk@hotmail.com: Forward Backspace (**annoying**)]
Andrew, you are in luck! The FAQ.gz file shipped with Debian's packaging of XFree86 is *EXTREMELY* detailed in this regard. On my system, this FAQ is located at /usr/share/doc/xfree86-common/FAQ.gz. Look about 513 lines into the thing. Of course, if this isn't the location of the FAQ or the description on your machine, you will have to get creative with "grep" and "zgrep" to find "backspace" in the documentation that came with your .deb package of X. If you want more information about the whole backspace/delete issue, try typing "backspace delete X" into your search engine of choice. Sure, the first few hits on Google aren't in my primary language, but it has options to limit the search to my primary language. I don't know about yours, of course, but my guess says it might. If not, altavista is a good second choice. A third place to look for information is the xmodmap(1x) manual page -- it looks like it was written to handle just this situation. (Though its whatis information doesn't list either. Pity.) And, as a last bit of information -- please do not mail Branden directly. He gets more than enough email and doesn't have enough hours in the day to answer them all. Please use the debian-user list in the future, as it is the proper forum for your question, and its much larger distribution is likely to give pointers to documentation much faster than Branden could ever hope to. Hope this helps. * Branden Robinson <[EMAIL PROTECTED]> [001106 20:54]: > Someone please direct this person to the Debian X FAQ (or quote it for > him), which has a very long section on troubleshooting this very issue. > > You don't know how proud it makes me to see those FAQ's I write go unread, > year after year... > > - Forwarded message from Andrew MacKinnon <[EMAIL PROTECTED]> - > > From: "Andrew MacKinnon" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Forward Backspace (**annoying**) > Date: Mon, 06 Nov 2000 15:22:40 EST > Delivered-To: [EMAIL PROTECTED] > Delivered-To: [EMAIL PROTECTED] > X-Originating-IP: [24.150.3.4] > Message-ID: <[EMAIL PROTECTED]> > X-OriginalArrivalTime: 06 Nov 2000 20:22:40.0443 (UTC) > FILETIME=[4FB700B0:01C0482F] > Delivered-To: [EMAIL PROTECTED] > > I have recently installed a new version of libc and xfree86-common and > strangely, the backsspace key behaves like a delete key. This only happens > in X11 not text mode and it is annoyingg. This happens with rxvt/xterm > (debian) and netscape (not debian). > _ > Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. > > Share information about yourself, create your own public profile at > http://profiles.msn.com. > > > - End forwarded message - > > -- > G. Branden Robinson| I have a truly elegant proof of the > Debian GNU/Linux | above, but it is too long to fit into > [EMAIL PROTECTED] | this .signature file. > http://deadbeast.net/~branden/ | -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: [andrew_pmk@hotmail.com: Forward Backspace (**annoying**)]
Andrew, you are in luck! The FAQ.gz file shipped with Debian's packaging of XFree86 is *EXTREMELY* detailed in this regard. On my system, this FAQ is located at /usr/share/doc/xfree86-common/FAQ.gz. Look about 513 lines into the thing. Of course, if this isn't the location of the FAQ or the description on your machine, you will have to get creative with "grep" and "zgrep" to find "backspace" in the documentation that came with your .deb package of X. If you want more information about the whole backspace/delete issue, try typing "backspace delete X" into your search engine of choice. Sure, the first few hits on Google aren't in my primary language, but it has options to limit the search to my primary language. I don't know about yours, of course, but my guess says it might. If not, altavista is a good second choice. A third place to look for information is the xmodmap(1x) manual page -- it looks like it was written to handle just this situation. (Though its whatis information doesn't list either. Pity.) And, as a last bit of information -- please do not mail Branden directly. He gets more than enough email and doesn't have enough hours in the day to answer them all. Please use the debian-user list in the future, as it is the proper forum for your question, and its much larger distribution is likely to give pointers to documentation much faster than Branden could ever hope to. Hope this helps. * Branden Robinson <[EMAIL PROTECTED]> [001106 20:54]: > Someone please direct this person to the Debian X FAQ (or quote it for > him), which has a very long section on troubleshooting this very issue. > > You don't know how proud it makes me to see those FAQ's I write go unread, > year after year... > > - Forwarded message from Andrew MacKinnon <[EMAIL PROTECTED]> - > > From: "Andrew MacKinnon" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Forward Backspace (**annoying**) > Date: Mon, 06 Nov 2000 15:22:40 EST > Delivered-To: [EMAIL PROTECTED] > Delivered-To: [EMAIL PROTECTED] > X-Originating-IP: [24.150.3.4] > Message-ID: <[EMAIL PROTECTED]> > X-OriginalArrivalTime: 06 Nov 2000 20:22:40.0443 (UTC) FILETIME=[4FB700B0:01C0482F] > Delivered-To: [EMAIL PROTECTED] > > I have recently installed a new version of libc and xfree86-common and > strangely, the backsspace key behaves like a delete key. This only happens > in X11 not text mode and it is annoyingg. This happens with rxvt/xterm > (debian) and netscape (not debian). > _ > Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. > > Share information about yourself, create your own public profile at > http://profiles.msn.com. > > > - End forwarded message - > > -- > G. Branden Robinson| I have a truly elegant proof of the > Debian GNU/Linux | above, but it is too long to fit into > [EMAIL PROTECTED] | this .signature file. > http://deadbeast.net/~branden/ | -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Configure monitor section in XF86Config file
Patrick, I don't want to sound rude; however, you gave so little information that attempts to help you are really pretty pointless. You haven't said what version of Debian, what version of XFree86, what you have tried and why that failed, whether or not Dexter worked (if you are using 4.0.1), etc. I am therefore assuming you are fairly new to the whole idea, and give some suggested entry-level readings: If you are using 3.3.x: http://www.xfree86.org/FAQ/ If you are using 4.0.1: http://www.xfree86.org/4.0.1/README.html http://www.xfree86.org/4.0.1/RELNOTES.html /usr/share/doc/xfree86-common/README.Debian.gz /usr/share/doc/xfree86-common/README.gz /usr/share/doc/xfree86-common/FAQ.gz Also useful: manpages for X, XFree86, XF86Config I don't know anything about the Mac platform -- you may need to do some tweaking to your kernel in order for X to run. On my dual-celeron system, I had to do some tweaking to get OpenGL support, but you may not need to tweak the kernel at all. If, on the other hand, this email is just indicitive of a need for more sleep, here is my monitor section for 4.0.1 for one of my monitors; hopefully it will provide enough information for you to tweak, in case you are using 4.0.1 as well. Section "Monitor" Identifier "Mitsubishi" VendorName "MEL" ModelName"42c0" HorizSync30.0 - 105.0 VertRefresh 70.0 - 152.0 Option "DPMS" EndSection Best of luck. * Patrick Atlas <[EMAIL PROTECTED]> [001105 15:04]: > I need information about how configure the monitor section in the XF86Config > file for the Xfree86 windows server. > > My computer is a MAC QUADRA 800 (68k), the monitor, an Apple AudioVision: > HorizSync 35 kHz, VertRefresh 66,7 Hz, 640X480 -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: Configure monitor section in XF86Config file
Patrick, I don't want to sound rude; however, you gave so little information that attempts to help you are really pretty pointless. You haven't said what version of Debian, what version of XFree86, what you have tried and why that failed, whether or not Dexter worked (if you are using 4.0.1), etc. I am therefore assuming you are fairly new to the whole idea, and give some suggested entry-level readings: If you are using 3.3.x: http://www.xfree86.org/FAQ/ If you are using 4.0.1: http://www.xfree86.org/4.0.1/README.html http://www.xfree86.org/4.0.1/RELNOTES.html /usr/share/doc/xfree86-common/README.Debian.gz /usr/share/doc/xfree86-common/README.gz /usr/share/doc/xfree86-common/FAQ.gz Also useful: manpages for X, XFree86, XF86Config I don't know anything about the Mac platform -- you may need to do some tweaking to your kernel in order for X to run. On my dual-celeron system, I had to do some tweaking to get OpenGL support, but you may not need to tweak the kernel at all. If, on the other hand, this email is just indicitive of a need for more sleep, here is my monitor section for 4.0.1 for one of my monitors; hopefully it will provide enough information for you to tweak, in case you are using 4.0.1 as well. Section "Monitor" Identifier "Mitsubishi" VendorName "MEL" ModelName"42c0" HorizSync30.0 - 105.0 VertRefresh 70.0 - 152.0 Option "DPMS" EndSection Best of luck. * Patrick Atlas <[EMAIL PROTECTED]> [001105 15:04]: > I need information about how configure the monitor section in the XF86Config > file for the Xfree86 windows server. > > My computer is a MAC QUADRA 800 (68k), the monitor, an Apple AudioVision: > HorizSync 35 kHz, VertRefresh 66,7 Hz, 640X480 -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xlibmesa and fsv (gtkglarea)
* Daniele Cruciani <[EMAIL PROTECTED]> [001104 21:14]: > I've got this problem : fsv do not display string on box. I've never tried fsv. Until today, I hadn't heard of it. :) What happens with "gears" and "glxinfo"? -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: YAXF4SC (Yet Another XFree 4 Server Crash)
* Scott Fenton <[EMAIL PROTECTED]> [001104 20:47]: > Nope, not it. There is a mouse section in that config. I've attached > it, if that helps. Oh, and BTW, you don't need to add me to the foward > list. I've been watching debian-x since just before XF4 sprang on the > scene. Thanks. :) Ok, then my last thought (I had two last thoughts, but upon further reflection, adding "CorePointer" in your ServerLayout section shouldn't help :) is to ensure that /dev/ttyS0 has proper permissions. -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: YAXF4SC (Yet Another XFree 4 Server Crash)
* Scott Fenton <[EMAIL PROTECTED]> [001104 20:15]: > Found after configuring with dexter, the server dies with the message "failed > to initalize core devices". Log file is attached [...] > (WW) System lacks support for changing MTRRs [...] Have you compiled MTRR support into your kernel? That may or may not help performance. [...] > No core pointer [...] Take a look at the generated /etc/X11/XF86Config-4 file -- my guess is your mouse section is missing, or something similar. The following works for my mouse, Logitech's cheapest three-button/wheel mouse: Section "ServerLayout" Identifier "Single" Screen "Screen0" InputDevice "Mouse0" "CorePointer" # <-- you need a line like this InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "InputDevice" # <-- and a whole section like this. Identifier "Mouse0" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/mouse" Option "ZAxisMapping" "4 5" EndSection HTH -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: xlibmesa and fsv (gtkglarea)
* Daniele Cruciani <[EMAIL PROTECTED]> [001104 21:14]: > I've got this problem : fsv do not display string on box. I've never tried fsv. Until today, I hadn't heard of it. :) What happens with "gears" and "glxinfo"? -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: YAXF4SC (Yet Another XFree 4 Server Crash)
* Scott Fenton <[EMAIL PROTECTED]> [001104 20:47]: > Nope, not it. There is a mouse section in that config. I've attached > it, if that helps. Oh, and BTW, you don't need to add me to the foward > list. I've been watching debian-x since just before XF4 sprang on the > scene. Thanks. :) Ok, then my last thought (I had two last thoughts, but upon further reflection, adding "CorePointer" in your ServerLayout section shouldn't help :) is to ensure that /dev/ttyS0 has proper permissions. -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: YAXF4SC (Yet Another XFree 4 Server Crash)
* Scott Fenton <[EMAIL PROTECTED]> [001104 20:15]: > Found after configuring with dexter, the server dies with the message "failed to >initalize core devices". Log file is attached [...] > (WW) System lacks support for changing MTRRs [...] Have you compiled MTRR support into your kernel? That may or may not help performance. [...] > No core pointer [...] Take a look at the generated /etc/X11/XF86Config-4 file -- my guess is your mouse section is missing, or something similar. The following works for my mouse, Logitech's cheapest three-button/wheel mouse: Section "ServerLayout" Identifier "Single" Screen "Screen0" InputDevice "Mouse0" "CorePointer" # <-- you need a line like this InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "InputDevice" # <-- and a whole section like this. Identifier "Mouse0" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/mouse" Option "ZAxisMapping" "4 5" EndSection HTH -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: X leaves console unusable on exit (Was re: Problems with 4.0.1 servers now in unstable: crash on -configure,screenfreeze on start)
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [001103 23:59]: > Using dexter as suggested in another thread, I got X to run (at least > from the startx script), but if I exit, it still leaves the console in > an unusable state. Oik. I was getting this for a little while with my g400, matrox driver. The only fix was quite magical -- the passing of time. Of course, Branden updated from vx to vy in the meantime, but who knows what that effected. Does magic sysrq bring the machine back? (Is the machine in such a place that magic sysrq can be used?) > As a sidenote, in dexter I selected 1280x1024 resolution as my > monitor's maximum... which it then refused to let me pick as a screen > mode. What is going on there? My bet -- your video card can't run the 1280x1024 res at the mode levels suggested by the monitor res you chose. (Monitors can be very picky. Sometimes, on monitors claiming 75Hz, 74.9Hz is too far.) Try to use the expert menu items, and try dropping your horizontal or vertical rates a bit. Best of luck. [btw, branden -- should all such posts now be forwarded to [EMAIL PROTECTED] -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: X leaves console unusable on exit (Was re: Problems with 4.0.1 servers now in unstable: crash on -configure,screenfreeze on start)
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [001103 23:59]: > Using dexter as suggested in another thread, I got X to run (at least > from the startx script), but if I exit, it still leaves the console in > an unusable state. Oik. I was getting this for a little while with my g400, matrox driver. The only fix was quite magical -- the passing of time. Of course, Branden updated from vx to vy in the meantime, but who knows what that effected. Does magic sysrq bring the machine back? (Is the machine in such a place that magic sysrq can be used?) > As a sidenote, in dexter I selected 1280x1024 resolution as my > monitor's maximum... which it then refused to let me pick as a screen > mode. What is going on there? My bet -- your video card can't run the 1280x1024 res at the mode levels suggested by the monitor res you chose. (Monitors can be very picky. Sometimes, on monitors claiming 75Hz, 74.9Hz is too far.) Try to use the expert menu items, and try dropping your horizontal or vertical rates a bit. Best of luck. [btw, branden -- should all such posts now be forwarded to debian-user@?] -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: I broke my G400 DRI
Ok, resolution time -- once this thing hits the ftp servers, people will want to know how to use it. So, everyone take note, it took me for fscking ever to figure out what was wrong. and if this saves you two minutes, go give someone a kiss or something. hehe. I WAS MISSING MY AGPGART DEVICE. I was missing my agpgart device. I was missing /dev/agpgart. Yup. Thanks to Nicholas for the tip about xlibmesa* and xlibosmesa* -- I was missing at least one of those, maybe two. I don't remember any more. :( *sigh* fighting several problems at once wasn't fun. Now I think I have a better feeling for what Branden has accomplished. Many thanks for making this so much easier. :) So, in the future -- remember to look for that /dev/agpgart interface. (If it is missing, you can use MAKEDEV to build it.) -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: I broke my G400 DRI
Ok, resolution time -- once this thing hits the ftp servers, people will want to know how to use it. So, everyone take note, it took me for fscking ever to figure out what was wrong. and if this saves you two minutes, go give someone a kiss or something. hehe. I WAS MISSING MY AGPGART DEVICE. I was missing my agpgart device. I was missing /dev/agpgart. Yup. Thanks to Nicholas for the tip about xlibmesa* and xlibosmesa* -- I was missing at least one of those, maybe two. I don't remember any more. :( *sigh* fighting several problems at once wasn't fun. Now I think I have a better feeling for what Branden has accomplished. Many thanks for making this so much easier. :) So, in the future -- remember to look for that /dev/agpgart interface. (If it is missing, you can use MAKEDEV to build it.) -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I broke my G400 DRI
Greetings everyone. I broke my G400's DRI. I honestly don't recall changing anything, but once upon a time it worked, and now it does not. The error I keep getting is rather simple: $ glxinfo X Error of failed request: 80 Major opcode of failed request: 0 () Serial number of failed request: 49153 Current serial number in output stream: 25 I don't know quite what to check next. So, I am hoping some nice kind soul out there can help me bring my G400's GL back to life. I am currently using Matrox's mga_drv.o (605779 bytes). Using the XFree86 supplied driver didn't change much, I don't recall. (Though those numbers may have been different.) I am running Linux Kernel 2.4.0-test7 (mainly since I have heard problems of DRM v1 / v2 problems with test9). I get this problem with the agpgart and mga modules loaded. Removing those modules before starting X will not give this error, but q3demo runs in software mode, and j3d (the reason why I am working on this now rather than just putting it off :) causes an X crash when I close the j3d window. I am starting up in 16 bit depth. I am starting up with only one monitor running. (Though the error is the same with both monitors. :) If anyone has suggestions, I would love to hear them. Thanks. :) -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' Section "ServerLayout" Identifier "Dual" Screen "Screen0" RightOf "Screen1" Screen "Screen1" InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" Option "Xinerama" EndSection Section "ServerLayout" Identifier "Single" Screen "Screen0" InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" FontPath "/usr/X11R6/lib/X11/fonts/freefont/" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/PEX/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:noscale" FontPath "/usr/X11R6/lib/X11/fonts/misc/:noscale" EndSection Section "Module" Load "ddc" Load "bitmap" Load "speedo" Load "vbe" Load "int10" #Load "GLcore" SubSection "extmod" Option "omit xfree86-dga" EndSubSection Load "dbe" Load "dri" Load "extmod" Load "glx" Load "pex5" Load "record" Load "xie" Load "freetype" Load "type1" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/mouse" Option "ZAxisMapping" "4 5" EndSection Section "Monitor" Identifier "Mitsubishi" VendorName "MEL" ModelName"42c0" HorizSync30.0 - 105.0 VertRefresh 70.0 - 152.0 Option "DPMS" #ModeLine "640x480" 45.8 640 672 768 864 480 488 494 530 -HSync -VSync EndSection Section "Monitor" Identifier "Sony" HorizSync60.5 - 82.0 VertRefresh 65.0 - 100.0 Option "DPMS" EndSection Section "Device" Identifier "G400_0" Driver "mga" VendorName "Matrox" BoardName "MGA G400 AGP" BusID "PCI:1:0:0" Screen 0 EndSection Section "Device" Identifier "G400_1" Driver "mga" VendorName "Matrox" BoardName "MGA G400 AGP" BusID "PCI:1:0:0" Screen 1 EndSection Section "Screen" Identifier "Screen0" Device "G400_0" Monitor"Mitsubishi" DefaultDepth 16 SubSection "Display" Depth 1 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection Section "Screen" Identifier "Screen1" Device "G400_1" Monitor"Sony" DefaultDepth 16
I broke my G400 DRI
Greetings everyone. I broke my G400's DRI. I honestly don't recall changing anything, but once upon a time it worked, and now it does not. The error I keep getting is rather simple: $ glxinfo X Error of failed request: 80 Major opcode of failed request: 0 () Serial number of failed request: 49153 Current serial number in output stream: 25 I don't know quite what to check next. So, I am hoping some nice kind soul out there can help me bring my G400's GL back to life. I am currently using Matrox's mga_drv.o (605779 bytes). Using the XFree86 supplied driver didn't change much, I don't recall. (Though those numbers may have been different.) I am running Linux Kernel 2.4.0-test7 (mainly since I have heard problems of DRM v1 / v2 problems with test9). I get this problem with the agpgart and mga modules loaded. Removing those modules before starting X will not give this error, but q3demo runs in software mode, and j3d (the reason why I am working on this now rather than just putting it off :) causes an X crash when I close the j3d window. I am starting up in 16 bit depth. I am starting up with only one monitor running. (Though the error is the same with both monitors. :) If anyone has suggestions, I would love to hear them. Thanks. :) -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' Section "ServerLayout" Identifier "Dual" Screen "Screen0" RightOf "Screen1" Screen "Screen1" InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" Option "Xinerama" EndSection Section "ServerLayout" Identifier "Single" Screen "Screen0" InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" FontPath "/usr/X11R6/lib/X11/fonts/freefont/" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/PEX/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:noscale" FontPath "/usr/X11R6/lib/X11/fonts/misc/:noscale" EndSection Section "Module" Load "ddc" Load "bitmap" Load "speedo" Load "vbe" Load "int10" #Load "GLcore" SubSection "extmod" Option "omit xfree86-dga" EndSubSection Load "dbe" Load "dri" Load "extmod" Load "glx" Load "pex5" Load "record" Load "xie" Load "freetype" Load "type1" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/mouse" Option "ZAxisMapping" "4 5" EndSection Section "Monitor" Identifier "Mitsubishi" VendorName "MEL" ModelName"42c0" HorizSync30.0 - 105.0 VertRefresh 70.0 - 152.0 Option "DPMS" #ModeLine "640x480" 45.8 640 672 768 864 480 488 494 530 -HSync -VSync EndSection Section "Monitor" Identifier "Sony" HorizSync60.5 - 82.0 VertRefresh 65.0 - 100.0 Option "DPMS" EndSection Section "Device" Identifier "G400_0" Driver "mga" VendorName "Matrox" BoardName "MGA G400 AGP" BusID "PCI:1:0:0" Screen 0 EndSection Section "Device" Identifier "G400_1" Driver "mga" VendorName "Matrox" BoardName "MGA G400 AGP" BusID "PCI:1:0:0" Screen 1 EndSection Section "Screen" Identifier "Screen0" Device "G400_0" Monitor"Mitsubishi" DefaultDepth 16 SubSection "Display" Depth 1 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection Section "Screen" Identifier "Screen1" Device "G400_1" Monitor"Sony" DefaultDepth 16
Re: Question about FontPath
* Branden Robinson <[EMAIL PROTECTED]> [001101 21:16]: > Can anyone else repro this problem? Does the X server get hung up if it's > looking for a font server that isn't there? I tried and failed to make my X server hang. I ran `apt-get remove xfs', added FontPath "unix/:7100" to the top of my Files section of my XF86Config-4 file, and restarted X. The only problem I notice is that my sawmill menu fonts aren't nearly as clean as they used to be. (It just looks like a different font, perhaps. I don't know why. :) (I take that back. Fonts in mozilla aren't good either.) All the same, no crash. No hang. -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: Question about FontPath
* Branden Robinson <[EMAIL PROTECTED]> [001101 21:16]: > Can anyone else repro this problem? Does the X server get hung up if it's > looking for a font server that isn't there? I tried and failed to make my X server hang. I ran `apt-get remove xfs', added FontPath "unix/:7100" to the top of my Files section of my XF86Config-4 file, and restarted X. The only problem I notice is that my sawmill menu fonts aren't nearly as clean as they used to be. (It just looks like a different font, perhaps. I don't know why. :) (I take that back. Fonts in mozilla aren't good either.) All the same, no crash. No hang. -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
xinerama not working
*sigh*. I know it is lame to followup one's own email. It must be even more lame to followup one's own email that one has already deleted, thus breaking the threading mechanism of many mailers. Apologies. Well, startx +xinerama would never work, because I am stupid. I did an upgrade to phase2v29. The problem persisted. Once I remembered that I am stupid, and typed "startx -- +xinerama", Xinerama works again. Which still makes me wonder what happened to the loading of Xinerama automatically that I have become so used to? Here is the bits of my XF86Config-4 file that might affect the situation: Section "ServerLayout" Identifier "Dual" Screen "Screen0" RightOf "Screen1" Screen "Screen1" InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" Option "Xinerama" EndSection Section "ServerLayout" Identifier "Single" Screen "Screen0" InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection The XF86Config(5) manpage suggests that the first one found is the one used -- has that changed? Thanks all -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
xinerama gone?
Ok. Mozilla caused my X phase2v27 to crash miserably a few minutes ago. Restarting X gave me a bit of a surprise -- no more xinerama. I have Option "Xinerama" in my /etc/X11/XF86Config-4 file, the same place it has been for weeks. I tried giving +xinerama on the command line. (That brought me into failsafe mode.) (BTW -- I am using Matrox's mga_drv.o file of Sep 23 on my Matrox G400Max.) It properly starts both monitors -- but I have no clue how to start a window manager on the second monitor, so it really doesn't do me much good. What on earth did I screw up? -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
xinerama not working
*sigh*. I know it is lame to followup one's own email. It must be even more lame to followup one's own email that one has already deleted, thus breaking the threading mechanism of many mailers. Apologies. Well, startx +xinerama would never work, because I am stupid. I did an upgrade to phase2v29. The problem persisted. Once I remembered that I am stupid, and typed "startx -- +xinerama", Xinerama works again. Which still makes me wonder what happened to the loading of Xinerama automatically that I have become so used to? Here is the bits of my XF86Config-4 file that might affect the situation: Section "ServerLayout" Identifier "Dual" Screen "Screen0" RightOf "Screen1" Screen "Screen1" InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" Option "Xinerama" EndSection Section "ServerLayout" Identifier "Single" Screen "Screen0" InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection The XF86Config(5) manpage suggests that the first one found is the one used -- has that changed? Thanks all -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
xinerama gone?
Ok. Mozilla caused my X phase2v27 to crash miserably a few minutes ago. Restarting X gave me a bit of a surprise -- no more xinerama. I have Option "Xinerama" in my /etc/X11/XF86Config-4 file, the same place it has been for weeks. I tried giving +xinerama on the command line. (That brought me into failsafe mode.) (BTW -- I am using Matrox's mga_drv.o file of Sep 23 on my Matrox G400Max.) It properly starts both monitors -- but I have no clue how to start a window manager on the second monitor, so it really doesn't do me much good. What on earth did I screw up? -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: I am a stupid idiot for posting a FAQ, but...
* Buddha Buck <[EMAIL PROTECTED]> [001030 18:39]: > The bright ones here will be saying "Oh gods, he's going to ask about > libGLU, isn't he?" What I *REALLY* want to know is why KDE (including konqueror) worked fine for several days! For a short time it didn't require libGLU? For a short time Branden supplied libGLU? I don't know. Both answers worry me. -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: [lqw@gmx.de: xfree86 4.0.1 on potato]
You are in luck! Charl P. Botha has gone before you, and already solved this problem. He was kind enough to write an entire HOWTO about the situation, and posted its URL to the debian-x archives. I decided that something was obviously wrong if you couldn't find it, so I added the thread and the HOWTO itself to Google's list of URLs to index. I don't know how long it will take until they get around to doing the index, but in the meantime, the URL will do it for you: http://cpbotha.net/building_brandens_phase2_debs_on_potato.HOWTO In the meantime, I gotta suggest that maybe this isn't a great idea, but Charl hasn't posted to the list complaining of problems, at least not that I recall. :) * Branden Robinson <[EMAIL PROTECTED]> [001030 16:41]: > - Forwarded message from lqw <[EMAIL PROTECTED]> - > > From: lqw <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: xfree86 4.0.1 on potato > Date: Tue, 31 Oct 2000 00:47:41 + > Delivered-To: [EMAIL PROTECTED] > Delivered-To: [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.17 i686) > X-Accept-Language: en > > hi branden > > i am using debian potato and am desparately trying to find some hints on > how to get xfree86 4.0.1 running on it. > i ended in renaming the old installation of x and compiling the new one > from the sources. > so far it works but is missing some files, which are located in the old > folders and i got problems > using the opengl-drivers for my riva tnt. > can you please give me some hints on how to build a .deb package of > xfree 4.0.1 from the sources, i > could`nt find anything on the web so far. > > thanks a lot > > gernot poerner > > > - End forwarded message - > > -- > G. Branden Robinson| I've made up my mind. Don't try to > Debian GNU/Linux | confuse me with the facts. > [EMAIL PROTECTED] | -- Indiana Senator Earl Landgrebe > http://deadbeast.net/~branden/ | -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: [motyl@stan.chemie.unibas.ch: Re: Bug#75875: NOT all is fixed xserver-common: xfree86-1 does not compile]
Tomasz, in every package's life, there are some contemporary packages. It works best to use the versions of those packages when trying to compile software, especially for anything as complex as X. Would you expect Windows 16 executables to build against Win32 libraries? Or a.out binaries to run on an ELF-only machine? For the same reason, software written with older versions of the C libraries won't compile under newer versions of the C libraries. Perhaps the good people at FSF should have bumped the minor version on glibc for their changes; check -policy for more information on this. But, they didn't, so we get the deal with it. I would suggest either upgrading your whole system to woody and using the woody version of XF 3.3.6, or using XF 4.0.1. Another option is to use potato, and the version of XF 3.3.6 that shipped with potato. If you want to contact xfree86.org with a source patch, perhaps they will be more amenable to the idea. Thanks Tomasz. * Branden Robinson <[EMAIL PROTECTED]> [001030 05:19]: > Someone knock him around with a cluebat for me? I see no reason why I must > support woody's libc in potato's packages. > > A fix for the problem he reports has been in the woody XF3 .debs for weeks. > > - Forwarded message from Tomasz Motylewski <[EMAIL PROTECTED]> - > > From: Tomasz Motylewski <[EMAIL PROTECTED]> > To: Branden Robinson <[EMAIL PROTECTED]> > Subject: Re: Bug#75875: NOT all is fixed xserver-common: xfree86-1 does not > compile > Date: Mon, 30 Oct 2000 13:46:02 +0100 (CET) > Delivered-To: [EMAIL PROTECTED] > Delivered-To: [EMAIL PROTECTED] > In-Reply-To: <[EMAIL PROTECTED]> > Message-ID: <[EMAIL PROTECTED]> > > > > > In file included from connection.c:79: > > > /usr/include/stdlib.h:700: parse error before `int' > > > > > > So, still same errors with misc.h and abs(). > > > > So don't compile against glibc 2.1.94. > > Are you interested in fixing this bug? If so I will prepare the > patch. Someone will need to do it sooner or later. > > Also, what about bug 56633? Are you interested in patch for this? > > Who is working on XFree86-4.0 for Debian at the moment? > > Best regards, > -- > Tomasz Motylewski > > > - End forwarded message - > > -- > G. Branden Robinson|It's not a matter of alienating authors. > Debian GNU/Linux |They have every right to license their > [EMAIL PROTECTED] |software however we like. > http://deadbeast.net/~branden/ |-- Craig Sanders, in debian-devel -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: [nutcase@gmx.de: xfree 4.0.1 via apt]
Nutcase, please don't bother Branden. He gets far too much email as it is. Before installing the 4.0.1 .debs, please check the debian-x archives for Branden's mini-faq. Reading it will likely save you some trouble. (Though Branden, it has been several weeks since I last saw one posted to the list -- is it time for a going-over and re-release of the mini-faq? :) Once you have read that, and some of the introductory notes on xfree86.org, feel free to add this line to your /etc/apt/sources.list file: deb http://samosa.debian.org/~branden woody/i386/ * Branden Robinson <[EMAIL PROTECTED]> [001030 05:19]: > - Forwarded message from nutcase <[EMAIL PROTECTED]> - > > From: nutcase <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: xfree 4.0.1 via apt > Date: Mon, 30 Oct 2000 12:24:32 +0100 > Delivered-To: [EMAIL PROTECTED] > Delivered-To: [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.17 i686) > X-Accept-Language: de, en > > hello, > > i am a relative linux-newbie, and an absolute newbie with deb-packages. > so can you eventually tell me, if xfree86 v4.0.1 is apt-getable? > If so, please tell me what i have to insert into my sources.list, that > ypt can find it itself. > > thank you > > nutcase > > > - End forwarded message - > > -- > G. Branden Robinson|You don't just decide to break Kubrick's > Debian GNU/Linux |code of silence and then get drawn away > [EMAIL PROTECTED] |from it to a discussion about cough > http://deadbeast.net/~branden/ |medicine. -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: I am a stupid idiot for posting a FAQ, but...
* Buddha Buck <[EMAIL PROTECTED]> [001030 18:39]: > The bright ones here will be saying "Oh gods, he's going to ask about > libGLU, isn't he?" What I *REALLY* want to know is why KDE (including konqueror) worked fine for several days! For a short time it didn't require libGLU? For a short time Branden supplied libGLU? I don't know. Both answers worry me. -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [lqw@gmx.de: xfree86 4.0.1 on potato]
You are in luck! Charl P. Botha has gone before you, and already solved this problem. He was kind enough to write an entire HOWTO about the situation, and posted its URL to the debian-x archives. I decided that something was obviously wrong if you couldn't find it, so I added the thread and the HOWTO itself to Google's list of URLs to index. I don't know how long it will take until they get around to doing the index, but in the meantime, the URL will do it for you: http://cpbotha.net/building_brandens_phase2_debs_on_potato.HOWTO In the meantime, I gotta suggest that maybe this isn't a great idea, but Charl hasn't posted to the list complaining of problems, at least not that I recall. :) * Branden Robinson <[EMAIL PROTECTED]> [001030 16:41]: > - Forwarded message from lqw <[EMAIL PROTECTED]> - > > From: lqw <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: xfree86 4.0.1 on potato > Date: Tue, 31 Oct 2000 00:47:41 + > Delivered-To: [EMAIL PROTECTED] > Delivered-To: [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.17 i686) > X-Accept-Language: en > > hi branden > > i am using debian potato and am desparately trying to find some hints on > how to get xfree86 4.0.1 running on it. > i ended in renaming the old installation of x and compiling the new one > from the sources. > so far it works but is missing some files, which are located in the old > folders and i got problems > using the opengl-drivers for my riva tnt. > can you please give me some hints on how to build a .deb package of > xfree 4.0.1 from the sources, i > could`nt find anything on the web so far. > > thanks a lot > > gernot poerner > > > - End forwarded message - > > -- > G. Branden Robinson| I've made up my mind. Don't try to > Debian GNU/Linux | confuse me with the facts. > [EMAIL PROTECTED] | -- Indiana Senator Earl Landgrebe > http://deadbeast.net/~branden/ | -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [motyl@stan.chemie.unibas.ch: Re: Bug#75875: NOT all is fixed xserver-common: xfree86-1 does not compile]
Tomasz, in every package's life, there are some contemporary packages. It works best to use the versions of those packages when trying to compile software, especially for anything as complex as X. Would you expect Windows 16 executables to build against Win32 libraries? Or a.out binaries to run on an ELF-only machine? For the same reason, software written with older versions of the C libraries won't compile under newer versions of the C libraries. Perhaps the good people at FSF should have bumped the minor version on glibc for their changes; check -policy for more information on this. But, they didn't, so we get the deal with it. I would suggest either upgrading your whole system to woody and using the woody version of XF 3.3.6, or using XF 4.0.1. Another option is to use potato, and the version of XF 3.3.6 that shipped with potato. If you want to contact xfree86.org with a source patch, perhaps they will be more amenable to the idea. Thanks Tomasz. * Branden Robinson <[EMAIL PROTECTED]> [001030 05:19]: > Someone knock him around with a cluebat for me? I see no reason why I must > support woody's libc in potato's packages. > > A fix for the problem he reports has been in the woody XF3 .debs for weeks. > > - Forwarded message from Tomasz Motylewski <[EMAIL PROTECTED]> - > > From: Tomasz Motylewski <[EMAIL PROTECTED]> > To: Branden Robinson <[EMAIL PROTECTED]> > Subject: Re: Bug#75875: NOT all is fixed xserver-common: xfree86-1 does not > compile > Date: Mon, 30 Oct 2000 13:46:02 +0100 (CET) > Delivered-To: [EMAIL PROTECTED] > Delivered-To: [EMAIL PROTECTED] > In-Reply-To: <[EMAIL PROTECTED]> > Message-ID: <[EMAIL PROTECTED]> > > > > > In file included from connection.c:79: > > > /usr/include/stdlib.h:700: parse error before `int' > > > > > > So, still same errors with misc.h and abs(). > > > > So don't compile against glibc 2.1.94. > > Are you interested in fixing this bug? If so I will prepare the > patch. Someone will need to do it sooner or later. > > Also, what about bug 56633? Are you interested in patch for this? > > Who is working on XFree86-4.0 for Debian at the moment? > > Best regards, > -- > Tomasz Motylewski > > > - End forwarded message - > > -- > G. Branden Robinson|It's not a matter of alienating authors. > Debian GNU/Linux |They have every right to license their > [EMAIL PROTECTED] |software however we like. > http://deadbeast.net/~branden/ |-- Craig Sanders, in debian-devel -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [nutcase@gmx.de: xfree 4.0.1 via apt]
Nutcase, please don't bother Branden. He gets far too much email as it is. Before installing the 4.0.1 .debs, please check the debian-x archives for Branden's mini-faq. Reading it will likely save you some trouble. (Though Branden, it has been several weeks since I last saw one posted to the list -- is it time for a going-over and re-release of the mini-faq? :) Once you have read that, and some of the introductory notes on xfree86.org, feel free to add this line to your /etc/apt/sources.list file: deb http://samosa.debian.org/~branden woody/i386/ * Branden Robinson <[EMAIL PROTECTED]> [001030 05:19]: > - Forwarded message from nutcase <[EMAIL PROTECTED]> - > > From: nutcase <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: xfree 4.0.1 via apt > Date: Mon, 30 Oct 2000 12:24:32 +0100 > Delivered-To: [EMAIL PROTECTED] > Delivered-To: [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.17 i686) > X-Accept-Language: de, en > > hello, > > i am a relative linux-newbie, and an absolute newbie with deb-packages. > so can you eventually tell me, if xfree86 v4.0.1 is apt-getable? > If so, please tell me what i have to insert into my sources.list, that > ypt can find it itself. > > thank you > > nutcase > > > - End forwarded message - > > -- > G. Branden Robinson|You don't just decide to break Kubrick's > Debian GNU/Linux |code of silence and then get drawn away > [EMAIL PROTECTED] |from it to a discussion about cough > http://deadbeast.net/~branden/ |medicine. -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nvidia kernel module and GLX
* Matthew Sackman <[EMAIL PROTECTED]> [001029 13:31]:
> Duplicate symbol RivaEnterLeave in /usr/X11R6/lib/modules/drivers/nv_drv.o
> Also defined in /usr/X11R6/lib/modules/drivers/nvidia_drv.o
Matt, this is purely speculation; try moving nv_drv.o or nvidia_drv.o
to nv_drv.o.XFREE86 or nvidia_drv.o.XFREE86 -- whichever of the two was
supplied by XFree86. If that doesn't fix things, move it back, and move
the other one away to nv_drv.o.NVidia or nvidia_drv.o.NVidia. See what
that does.
If neither fixes your problem, then perhaps another post would be in
order, this time with much more details -- kernel version, platform,
your XF86Config{-4} file, whether or not putting "twm" into your
.xsession causes a window manager to start, etc.
(BTW -- this will show my ignorance in a real hurry -- should that be
"exec twm" or just "twm" in the .xsession? Rest of list? :)
--
``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really
impressed down here, I can tell you.''
Re: nvidia kernel module and GLX
* Matthew Sackman <[EMAIL PROTECTED]> [001029 13:31]:
> Duplicate symbol RivaEnterLeave in /usr/X11R6/lib/modules/drivers/nv_drv.o
> Also defined in /usr/X11R6/lib/modules/drivers/nvidia_drv.o
Matt, this is purely speculation; try moving nv_drv.o or nvidia_drv.o
to nv_drv.o.XFREE86 or nvidia_drv.o.XFREE86 -- whichever of the two was
supplied by XFree86. If that doesn't fix things, move it back, and move
the other one away to nv_drv.o.NVidia or nvidia_drv.o.NVidia. See what
that does.
If neither fixes your problem, then perhaps another post would be in
order, this time with much more details -- kernel version, platform,
your XF86Config{-4} file, whether or not putting "twm" into your
.xsession causes a window manager to start, etc.
(BTW -- this will show my ignorance in a real hurry -- should that be
"exec twm" or just "twm" in the .xsession? Rest of list? :)
--
``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really
impressed down here, I can tell you.''
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[branden@deadbeast.net: [aa@lithic.org: fonts packages]]
Aaron, try installing xutils per the recommendation in xfonts-75dpi. - Forwarded message from Branden Robinson <[EMAIL PROTECTED]> - Envelope-to: [EMAIL PROTECTED] Delivery-date: Sat, 28 Oct 2000 16:06:10 -0700 Resent-Date: Sat, 28 Oct 2000 16:01:50 -0700 (PDT) X-Envelope-Sender: [EMAIL PROTECTED] Date: Sat, 28 Oct 2000 18:03:56 -0500 To: debian-x@lists.debian.org Subject: [EMAIL PROTECTED]: fonts packages] Mail-Followup-To: debian-x@lists.debian.org User-Agent: Mutt/1.2.5i From: [EMAIL PROTECTED] (Branden Robinson) Resent-Message-ID: <[EMAIL PROTECTED]> Resent-From: debian-x@lists.debian.org X-Mailing-List: archive/latest/1231 X-Loop: debian-x@lists.debian.org Precedence: list Resent-Sender: [EMAIL PROTECTED] Resent-Bcc: Sounds like a FAQ and/or some outdated 4.0 test packages. libXfont is not built shared, and hasn't been for a while. - Forwarded message from Aaron Brick <[EMAIL PROTECTED]> - From: Aaron Brick <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: fonts packages Date: Sat, 28 Oct 2000 15:16:31 -0700 Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> User-Agent: Mutt/1.0.1i hi branden, are the woody xfonts-* known to be broken? i'm having trouble with a lack of mkfontdir and libXfont, and dpkg complaining a lot. please let me know if i should a) go away, b) submit more information, or c) downgrade. thanks! aaron. - | | | | | | | | | | - - - - - - aaron brick - -[EMAIL PROTECTED]- - - - - - | | | | | | | | | | - - End forwarded message - -- G. Branden Robinson|A celibate clergy is an especially good Debian GNU/Linux |idea, because it tends to suppress any [EMAIL PROTECTED] |hereditary propensity toward fanaticism. http://deadbeast.net/~branden/ |-- Carl Sagan - End forwarded message - -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
[branden@deadbeast.net: [aa@lithic.org: fonts packages]]
Aaron, try installing xutils per the recommendation in xfonts-75dpi. - Forwarded message from Branden Robinson <[EMAIL PROTECTED]> - Envelope-to: sarnold@localhost Delivery-date: Sat, 28 Oct 2000 16:06:10 -0700 Resent-Date: Sat, 28 Oct 2000 16:01:50 -0700 (PDT) X-Envelope-Sender: [EMAIL PROTECTED] Date: Sat, 28 Oct 2000 18:03:56 -0500 To: [EMAIL PROTECTED] Subject: [[EMAIL PROTECTED]: fonts packages] Mail-Followup-To: [EMAIL PROTECTED] User-Agent: Mutt/1.2.5i From: [EMAIL PROTECTED] (Branden Robinson) Resent-Message-ID: Resent-From: [EMAIL PROTECTED] X-Mailing-List: <[EMAIL PROTECTED]> archive/latest/1231 X-Loop: [EMAIL PROTECTED] Precedence: list Resent-Sender: [EMAIL PROTECTED] Resent-Bcc: Sounds like a FAQ and/or some outdated 4.0 test packages. libXfont is not built shared, and hasn't been for a while. - Forwarded message from Aaron Brick <[EMAIL PROTECTED]> - From: Aaron Brick <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: fonts packages Date: Sat, 28 Oct 2000 15:16:31 -0700 Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> User-Agent: Mutt/1.0.1i hi branden, are the woody xfonts-* known to be broken? i'm having trouble with a lack of mkfontdir and libXfont, and dpkg complaining a lot. please let me know if i should a) go away, b) submit more information, or c) downgrade. thanks! aaron. - | | | | | | | | | | - - - - - - aaron brick - -[EMAIL PROTECTED]- - - - - - | | | | | | | | | | - - End forwarded message - -- G. Branden Robinson|A celibate clergy is an especially good Debian GNU/Linux |idea, because it tends to suppress any [EMAIL PROTECTED] |hereditary propensity toward fanaticism. http://deadbeast.net/~branden/ |-- Carl Sagan - End forwarded message - -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[branden@deadbeast.net: [crond@online.no: xlibmesa3 deb]]
Tore, libGLU is not currently packaged upstream. Until it is, Branden is not going to package the libGLU himself, and I can't blame him. Until they merge it into their build system, Debian won't have it either. - Forwarded message from Branden Robinson <[EMAIL PROTECTED]> - Envelope-to: [EMAIL PROTECTED] Delivery-date: Fri, 27 Oct 2000 21:02:27 -0700 Resent-Date: Fri, 27 Oct 2000 21:00:58 -0700 (PDT) X-Envelope-Sender: [EMAIL PROTECTED] Date: Fri, 27 Oct 2000 23:03:05 -0500 To: debian-x@lists.debian.org Subject: [EMAIL PROTECTED]: xlibmesa3 deb] Mail-Followup-To: debian-x@lists.debian.org User-Agent: Mutt/1.2.5i From: [EMAIL PROTECTED] (Branden Robinson) Resent-Message-ID: <[EMAIL PROTECTED]> Resent-From: debian-x@lists.debian.org X-Mailing-List: archive/latest/1229 X-Loop: debian-x@lists.debian.org Precedence: list Resent-Sender: [EMAIL PROTECTED] Resent-Bcc: FAQ! - Forwarded message from Tore Anderson <[EMAIL PROTECTED]> - From: Tore Anderson <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: xlibmesa3 deb Date: Fri, 27 Oct 2000 22:22:54 +0200 (CEST) Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> X-Mailer: Nextel Epostleser X-Real-User: crond X-Client-Addr: 148.122.184.99 Hello. I am using your deb's for XF4.0.1 - and they are working excellent. :) However, one thing bugs me. The xlibmesa3 package does not include libGLU - and all the other packages in Woody which provide libGLU conflicts with it. So I'm in a no-win situation - I need your version because it has the DRI strings. (And I really prefer to have a full-debianized system - much more tidy) So my question is obviously if you are going to include libGLU in you package and eventually when that will be? Apart from that, my X is as perfect as it can be - keep up the good work! :) Cheers, Tore - End forwarded message - -- G. Branden Robinson|Reality is what refuses to go away when Debian GNU/Linux |I stop believing in it. [EMAIL PROTECTED] |-- Philip K. Dick http://deadbeast.net/~branden/ | - End forwarded message - -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
[branden@deadbeast.net: [crond@online.no: xlibmesa3 deb]]
Tore, libGLU is not currently packaged upstream. Until it is, Branden is not going to package the libGLU himself, and I can't blame him. Until they merge it into their build system, Debian won't have it either. - Forwarded message from Branden Robinson <[EMAIL PROTECTED]> - Envelope-to: sarnold@localhost Delivery-date: Fri, 27 Oct 2000 21:02:27 -0700 Resent-Date: Fri, 27 Oct 2000 21:00:58 -0700 (PDT) X-Envelope-Sender: [EMAIL PROTECTED] Date: Fri, 27 Oct 2000 23:03:05 -0500 To: [EMAIL PROTECTED] Subject: [[EMAIL PROTECTED]: xlibmesa3 deb] Mail-Followup-To: [EMAIL PROTECTED] User-Agent: Mutt/1.2.5i From: [EMAIL PROTECTED] (Branden Robinson) Resent-Message-ID: Resent-From: [EMAIL PROTECTED] X-Mailing-List: <[EMAIL PROTECTED]> archive/latest/1229 X-Loop: [EMAIL PROTECTED] Precedence: list Resent-Sender: [EMAIL PROTECTED] Resent-Bcc: FAQ! - Forwarded message from Tore Anderson <[EMAIL PROTECTED]> - From: Tore Anderson <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: xlibmesa3 deb Date: Fri, 27 Oct 2000 22:22:54 +0200 (CEST) Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> X-Mailer: Nextel Epostleser X-Real-User: crond X-Client-Addr: 148.122.184.99 Hello. I am using your deb's for XF4.0.1 - and they are working excellent. :) However, one thing bugs me. The xlibmesa3 package does not include libGLU - and all the other packages in Woody which provide libGLU conflicts with it. So I'm in a no-win situation - I need your version because it has the DRI strings. (And I really prefer to have a full-debianized system - much more tidy) So my question is obviously if you are going to include libGLU in you package and eventually when that will be? Apart from that, my X is as perfect as it can be - keep up the good work! :) Cheers, Tore - End forwarded message - -- G. Branden Robinson|Reality is what refuses to go away when Debian GNU/Linux |I stop believing in it. [EMAIL PROTECTED] |-- Philip K. Dick http://deadbeast.net/~branden/ | - End forwarded message - -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Questions about r128 server
* Joshua Shagam <[EMAIL PROTECTED]> [001027 14:32]: > The magic thingy you need is in your XF86Config file, add > > Option "DPMS" "on" > > to your Monitor section. While this is nicely documented in the XF86Config manpage, it won't solve the original author's question. I suggest to the original author (whose name I have trimmed without thinking) that the post should be directed towards [EMAIL PROTECTED] It is a driver-level question, beyond the intents of the debian-x list (the debian packaging of X4) -- I don't mind these questions coming up on this list, mainly since *someone* in debian needs to know some of the wierdness of X4 in order to help the other users (on debian-user) in the near future. But, I think it is now obvious this list doesn't know why the OP cannot get their Dell to go to DPMS mode, when the DPMS option is on, and xset dpms is used to tell it to go to sleep. :( OP -- two last thoughts: try xset dpms 10 0 0 as well as xset dpms 0 10 0 and xset dpms 0 0 10. Maybe the dell screen just doesn't understand one or more of the sleep states. Or, try checking the source code for your driver modules. Maybe they documented in there their choices. Best of luck. -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: Questions about r128 server
* Joshua Shagam <[EMAIL PROTECTED]> [001027 14:32]: > The magic thingy you need is in your XF86Config file, add > > Option "DPMS" "on" > > to your Monitor section. While this is nicely documented in the XF86Config manpage, it won't solve the original author's question. I suggest to the original author (whose name I have trimmed without thinking) that the post should be directed towards [EMAIL PROTECTED] It is a driver-level question, beyond the intents of the debian-x list (the debian packaging of X4) -- I don't mind these questions coming up on this list, mainly since *someone* in debian needs to know some of the wierdness of X4 in order to help the other users (on debian-user) in the near future. But, I think it is now obvious this list doesn't know why the OP cannot get their Dell to go to DPMS mode, when the DPMS option is on, and xset dpms is used to tell it to go to sleep. :( OP -- two last thoughts: try xset dpms 10 0 0 as well as xset dpms 0 10 0 and xset dpms 0 0 10. Maybe the dell screen just doesn't understand one or more of the sleep states. Or, try checking the source code for your driver modules. Maybe they documented in there their choices. Best of luck. -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [branden@deadbeast.net: [bequw@stanford.edu: future of xlibs question]]
* Branden Robinson <[EMAIL PROTECTED]> [001025 00:06]: > > And phase 3? > NOW who's not reading the documentation? Tut, tut. Heh, you are making changes faster than I can download and test them! :) BTW -- nice work with it all. :) -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: [branden@deadbeast.net: [bequw@stanford.edu: future of xlibs question]]
* Branden Robinson <[EMAIL PROTECTED]> [001025 00:06]: > > And phase 3? > NOW who's not reading the documentation? Tut, tut. Heh, you are making changes faster than I can download and test them! :) BTW -- nice work with it all. :) -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [branden@deadbeast.net: [bequw@stanford.edu: future of xlibs question]]
* Branden Robinson <[EMAIL PROTECTED]> [001024 21:47]: > We're getting close to 4.0.1-1. That message had to come out sometime. And phase 3? -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
[branden@deadbeast.net: [bequw@stanford.edu: future of xlibs question]]
Brian, please do not bother Branden directly, he gets too much of that already. BTW, what happened to "I obey."? [Branden, perhaps you should change it to require, "I promise I will not email Branden, so help me God". :] To answer your direct question, GLU will be supported once upstream supports it. It is currently the only C++ file in the whole distribution, and they are trying to find some nice way for it to be handled in their current build system for all their platforms. I don't envy them their work. Until that time, a work-around has been posted to this list, check the archives if you need libGLU support Right Away. Thanks - Forwarded message from Branden Robinson <[EMAIL PROTECTED]> - Envelope-to: [EMAIL PROTECTED] Delivery-date: Tue, 24 Oct 2000 20:44:02 -0700 Resent-Date: Tue, 24 Oct 2000 20:41:20 -0700 (PDT) X-Envelope-Sender: [EMAIL PROTECTED] Date: Tue, 24 Oct 2000 22:43:25 -0500 To: debian-x@lists.debian.org Subject: [EMAIL PROTECTED]: future of xlibs question] Mail-Followup-To: debian-x@lists.debian.org User-Agent: Mutt/1.2.5i From: [EMAIL PROTECTED] (Branden Robinson) Resent-Message-ID: <[EMAIL PROTECTED]> Resent-From: debian-x@lists.debian.org X-Mailing-List: archive/latest/1198 X-Loop: debian-x@lists.debian.org Precedence: list Resent-Sender: [EMAIL PROTECTED] Resent-Bcc: - Forwarded message from Brian Alexander Quistorff <[EMAIL PROTECTED]> - From: Brian Alexander Quistorff <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: future of xlibs question Date: Tue, 24 Oct 2000 17:07:12 -0700 (PDT) Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Authentication-Warning: myth2.Stanford.EDU: bequw owned process doing -bs Message-ID: <[EMAIL PROTECTED]> Dear Branden, I'm a debian user who uses your xlib packages and wanted to know if they will support GLU anytime soon? Thanks for the packages they work great otherwise. Brian Quistorff - End forwarded message - -- G. Branden Robinson|I suspect Linus wrote that in a Debian GNU/Linux |complicated way only to be able to have [EMAIL PROTECTED] |that comment in there. http://deadbeast.net/~branden/ |-- Lars Wirzenius - End forwarded message - -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: [branden@deadbeast.net: [bequw@stanford.edu: future of xlibs question]]
* Branden Robinson <[EMAIL PROTECTED]> [001024 21:47]: > We're getting close to 4.0.1-1. That message had to come out sometime. And phase 3? -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[branden@deadbeast.net: [bequw@stanford.edu: future of xlibs question]]
Brian, please do not bother Branden directly, he gets too much of that already. BTW, what happened to "I obey."? [Branden, perhaps you should change it to require, "I promise I will not email Branden, so help me God". :] To answer your direct question, GLU will be supported once upstream supports it. It is currently the only C++ file in the whole distribution, and they are trying to find some nice way for it to be handled in their current build system for all their platforms. I don't envy them their work. Until that time, a work-around has been posted to this list, check the archives if you need libGLU support Right Away. Thanks - Forwarded message from Branden Robinson <[EMAIL PROTECTED]> - Envelope-to: sarnold@localhost Delivery-date: Tue, 24 Oct 2000 20:44:02 -0700 Resent-Date: Tue, 24 Oct 2000 20:41:20 -0700 (PDT) X-Envelope-Sender: [EMAIL PROTECTED] Date: Tue, 24 Oct 2000 22:43:25 -0500 To: [EMAIL PROTECTED] Subject: [[EMAIL PROTECTED]: future of xlibs question] Mail-Followup-To: [EMAIL PROTECTED] User-Agent: Mutt/1.2.5i From: [EMAIL PROTECTED] (Branden Robinson) Resent-Message-ID: Resent-From: [EMAIL PROTECTED] X-Mailing-List: <[EMAIL PROTECTED]> archive/latest/1198 X-Loop: [EMAIL PROTECTED] Precedence: list Resent-Sender: [EMAIL PROTECTED] Resent-Bcc: - Forwarded message from Brian Alexander Quistorff <[EMAIL PROTECTED]> - From: Brian Alexander Quistorff <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: future of xlibs question Date: Tue, 24 Oct 2000 17:07:12 -0700 (PDT) Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Authentication-Warning: myth2.Stanford.EDU: bequw owned process doing -bs Message-ID: <[EMAIL PROTECTED]> Dear Branden, I'm a debian user who uses your xlib packages and wanted to know if they will support GLU anytime soon? Thanks for the packages they work great otherwise. Brian Quistorff - End forwarded message - -- G. Branden Robinson|I suspect Linus wrote that in a Debian GNU/Linux |complicated way only to be able to have [EMAIL PROTECTED] |that comment in there. http://deadbeast.net/~branden/ |-- Lars Wirzenius - End forwarded message - -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[branden@deadbeast.net: [dstar@pele.cx: XFree86 4.01 status]]
Soon enough. However, bothering Branden will only make the process slower. - Forwarded message from Branden Robinson <[EMAIL PROTECTED]> - Envelope-to: [EMAIL PROTECTED] Delivery-date: Tue, 24 Oct 2000 13:46:30 -0700 Resent-Date: Tue, 24 Oct 2000 13:44:58 -0700 (PDT) X-Envelope-Sender: [EMAIL PROTECTED] Date: Tue, 24 Oct 2000 15:46:28 -0500 To: debian-x@lists.debian.org Subject: [EMAIL PROTECTED]: XFree86 4.01 status] Mail-Followup-To: debian-x@lists.debian.org User-Agent: Mutt/1.2.5i From: [EMAIL PROTECTED] (Branden Robinson) Resent-Message-ID: <[EMAIL PROTECTED]> Resent-From: debian-x@lists.debian.org X-Mailing-List: archive/latest/1194 X-Loop: debian-x@lists.debian.org Precedence: list Resent-Sender: [EMAIL PROTECTED] Resent-Bcc: - Forwarded message from Shalon Wood <[EMAIL PROTECTED]> - From: Shalon Wood <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: XFree86 4.01 status Date: 24 Oct 2000 12:47:38 -0500 Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Authentication-Warning: pele.cx: dstar set sender to [EMAIL PROTECTED] using -f Message-ID: <[EMAIL PROTECTED]> User-Agent: Gnus/5.0806 (Gnus v5.8.6) Emacs/20.5 I noticed that you released phase 2 .debs about two months ago. Any idea when phase 3 will happen? Thanks Shalon Wood -- - End forwarded message - -- G. Branden Robinson|Q: How does a Unix guru have sex? Debian GNU/Linux |A: unzip;strip;touch;finger;mount;fsck; [EMAIL PROTECTED] | more;yes;fsck;fsck;fsck;umount;sleep http://deadbeast.net/~branden/ | - End forwarded message - -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
[branden@deadbeast.net: [dstar@pele.cx: XFree86 4.01 status]]
Soon enough. However, bothering Branden will only make the process slower. - Forwarded message from Branden Robinson <[EMAIL PROTECTED]> - Envelope-to: sarnold@localhost Delivery-date: Tue, 24 Oct 2000 13:46:30 -0700 Resent-Date: Tue, 24 Oct 2000 13:44:58 -0700 (PDT) X-Envelope-Sender: [EMAIL PROTECTED] Date: Tue, 24 Oct 2000 15:46:28 -0500 To: [EMAIL PROTECTED] Subject: [[EMAIL PROTECTED]: XFree86 4.01 status] Mail-Followup-To: [EMAIL PROTECTED] User-Agent: Mutt/1.2.5i From: [EMAIL PROTECTED] (Branden Robinson) Resent-Message-ID: Resent-From: [EMAIL PROTECTED] X-Mailing-List: <[EMAIL PROTECTED]> archive/latest/1194 X-Loop: [EMAIL PROTECTED] Precedence: list Resent-Sender: [EMAIL PROTECTED] Resent-Bcc: - Forwarded message from Shalon Wood <[EMAIL PROTECTED]> - From: Shalon Wood <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: XFree86 4.01 status Date: 24 Oct 2000 12:47:38 -0500 Delivered-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Authentication-Warning: pele.cx: dstar set sender to [EMAIL PROTECTED] using -f Message-ID: <[EMAIL PROTECTED]> User-Agent: Gnus/5.0806 (Gnus v5.8.6) Emacs/20.5 I noticed that you released phase 2 .debs about two months ago. Any idea when phase 3 will happen? Thanks Shalon Wood -- - End forwarded message - -- G. Branden Robinson|Q: How does a Unix guru have sex? Debian GNU/Linux |A: unzip;strip;touch;finger;mount;fsck; [EMAIL PROTECTED] | more;yes;fsck;fsck;fsck;umount;sleep http://deadbeast.net/~branden/ | - End forwarded message - -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Matrox driver devlopment
Scott, my gut feeling says you should talk with xpert@xfree86.org and the nice person, Ben, at Matrox's Support Forum. I have found him to be, at the least, interested in helping, and occasionally quite helpful. * Scott Bronson <[EMAIL PROTECTED]> [001024 11:05]: > I found the XFree 4.x mga driver sources on www.matrox.com. I glanced > over them and I think I see some easy 2D wins I could get in there > and hack on them a bit, but I'm worried about duplicating effort. > > Can anyone tell me where Matrox driver development is going on? > I didn't find anything on xfree.org. -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: Matrox driver devlopment
Scott, my gut feeling says you should talk with [EMAIL PROTECTED] and the nice person, Ben, at Matrox's Support Forum. I have found him to be, at the least, interested in helping, and occasionally quite helpful. * Scott Bronson <[EMAIL PROTECTED]> [001024 11:05]: > I found the XFree 4.x mga driver sources on www.matrox.com. I glanced > over them and I think I see some easy 2D wins I could get in there > and hack on them a bit, but I'm worried about duplicating effort. > > Can anyone tell me where Matrox driver development is going on? > I didn't find anything on xfree.org. -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: VSZ memory of X
Hmm. Just last night, I decided it was time to go to sleep once my X got up to 192M of VSZ and 120M RSS. While quitting, my machine hung. :-/ Sysrq was good enough to sync and unmount, but not reboot. Oh well. Has anyone else noticed strange memory use with recent phase2 .debs? * Christian Hammers <[EMAIL PROTECTED]> [001022 10:57]: > Hi > > My X uses 80M of VSZ but only 8M of RSS memory. The eight megabytes seams > reasonably for an X server but why is the VSZ part so high? Does every > program that runs under X request it from X and so raises X's memory > statistic? > > I'm asking because I have only 64M and trying to save every bit... > > bye, > > -christian- > > -- > Christian HammersWESTEND GmbH - Aachen und Dueren Tel 0241/701333-0 > [EMAIL PROTECTED] Internet & Security for ProfessionalsFax 0241/911879 >WESTEND ist CISCO Systems Partner - Premium Certified > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
Re: VSZ memory of X
Hmm. Just last night, I decided it was time to go to sleep once my X got up to 192M of VSZ and 120M RSS. While quitting, my machine hung. :-/ Sysrq was good enough to sync and unmount, but not reboot. Oh well. Has anyone else noticed strange memory use with recent phase2 .debs? * Christian Hammers <[EMAIL PROTECTED]> [001022 10:57]: > Hi > > My X uses 80M of VSZ but only 8M of RSS memory. The eight megabytes seams > reasonably for an X server but why is the VSZ part so high? Does every > program that runs under X request it from X and so raises X's memory > statistic? > > I'm asking because I have only 64M and trying to save every bit... > > bye, > > -christian- > > -- > Christian HammersWESTEND GmbH - Aachen und Dueren Tel 0241/701333-0 > [EMAIL PROTECTED] Internet & Security for ProfessionalsFax 0241/911879 >WESTEND ist CISCO Systems Partner - Premium Certified > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xfonts-* should depend on xutils
* Branden Robinson <[EMAIL PROTECTED]> [001020 16:08]: > Or I can update the X task packages to haul in xutils, which has always > been my intention. Sounds perfect to me; anyone mucking with the task-x-window is going to need xutils. Anyone who is going to roll their own is rolling their own. :)
Re: xfonts-* should depend on xutils
* Branden Robinson <[EMAIL PROTECTED]> [001020 16:08]: > Or I can update the X task packages to haul in xutils, which has always > been my intention. Sounds perfect to me; anyone mucking with the task-x-window is going to need xutils. Anyone who is going to roll their own is rolling their own. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xfonts-* should depend on xutils
Branden has made the decision that xutils isn't needed on all systems.
He suggests that reading the package description for xfonts-* will say
what is needed.
Considering the number of people that have asked about this, perhaps
this should be re-thought? Or, perhaps, a package
"x-most-people-should-install-this" should be made available with
dependencies upon one of {xfonts-100dpi,xfonts-75dpi} and xutils.
Thanks
* Adam McKenna <[EMAIL PROTECTED]> [001020 13:15]:
> Title says it all... I was getting errors that mkfontdir couldn't be found
> after installing xfonts-100dpi, xfonts-scalable.. etc.
>
> Thanks to some people in #debian-devel, I found out I needed to install
> xutils.
Re: xfonts-* should depend on xutils
Branden has made the decision that xutils isn't needed on all systems.
He suggests that reading the package description for xfonts-* will say
what is needed.
Considering the number of people that have asked about this, perhaps
this should be re-thought? Or, perhaps, a package
"x-most-people-should-install-this" should be made available with
dependencies upon one of {xfonts-100dpi,xfonts-75dpi} and xutils.
Thanks
* Adam McKenna <[EMAIL PROTECTED]> [001020 13:15]:
> Title says it all... I was getting errors that mkfontdir couldn't be found
> after installing xfonts-100dpi, xfonts-scalable.. etc.
>
> Thanks to some people in #debian-devel, I found out I needed to install
> xutils.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: DRI problem with Voodoo3 and quake 3
Joel, how well does "glxinfo" run? I too noticed this with q3a, and glxinfo also dies in a similar manner. Since I don't have time to play games at the moment, I didn't investigate further -- I figured I broke something. :) I am still running kernel 2.4.0-test7 with my MGA 400 Max, matrox's driver. * Joel Fuster <[EMAIL PROTECTED]> [001019 17:55]: > Hello, > > I've searched high and low to see if someone else has had this problem, > but no luck, so I'm posting this here. > > This is my setup: > > linux 2.4.0-test9 > X 4.0.1 packages, phase2v19 > Glide v3.10 for DRI > Voodoo 3 3000 AGP > > I've recently started having a problem running Quake 3, the following is > what happens when I start it: > > - R_Init - > ...loading libGL.so: Initializing OpenGL display > ...setting mode 4: 800 600 > Using XFree86-VidModeExtension Version 2.0 > XF86DGA Mouse (Version 2.0) initialized > XFree86-VidModeExtension Activated at 800x600 > Xlib: sequence lost (0x1 > 0x1d) in reply type 0x0! > X Error of failed request: BadAtom (invalid Atom parameter) > Major opcode of failed request: 0 () > Atom id in failed request: 0x400 > Serial number of failed request: 0 > Current serial number in output stream: 29 > > > > ...and it quits. It used to work fine with a previous version of the > X4.0.1 packages, but unfortunately I don't remember which version it was > that started not working. At one point I was using the tdfx_dri.o > module from the X 4.0.1 I had compiled myself before the phase2 packages > began including it, and that worked fine. But now it does this same > thing with either one I try. If I go back entirely to my compiled X, > though, quake 3 works (though at half-speed, but that's something else > entirely I think). > > Something odd, I just tried some other GL apps, (some GL xscreensavers, > terminus, chromium-bsu) and they seem to be working fine... I've no > idea why only quake 3 would refuse to work... > > I'd really appreciate it if anyone had any ideas or suggestions... > > Joel Fuster > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Re: DRI problem with Voodoo3 and quake 3
Joel, how well does "glxinfo" run? I too noticed this with q3a, and glxinfo also dies in a similar manner. Since I don't have time to play games at the moment, I didn't investigate further -- I figured I broke something. :) I am still running kernel 2.4.0-test7 with my MGA 400 Max, matrox's driver. * Joel Fuster <[EMAIL PROTECTED]> [001019 17:55]: > Hello, > > I've searched high and low to see if someone else has had this problem, > but no luck, so I'm posting this here. > > This is my setup: > > linux 2.4.0-test9 > X 4.0.1 packages, phase2v19 > Glide v3.10 for DRI > Voodoo 3 3000 AGP > > I've recently started having a problem running Quake 3, the following is > what happens when I start it: > > - R_Init - > ...loading libGL.so: Initializing OpenGL display > ...setting mode 4: 800 600 > Using XFree86-VidModeExtension Version 2.0 > XF86DGA Mouse (Version 2.0) initialized > XFree86-VidModeExtension Activated at 800x600 > Xlib: sequence lost (0x1 > 0x1d) in reply type 0x0! > X Error of failed request: BadAtom (invalid Atom parameter) > Major opcode of failed request: 0 () > Atom id in failed request: 0x400 > Serial number of failed request: 0 > Current serial number in output stream: 29 > > > > ...and it quits. It used to work fine with a previous version of the > X4.0.1 packages, but unfortunately I don't remember which version it was > that started not working. At one point I was using the tdfx_dri.o > module from the X 4.0.1 I had compiled myself before the phase2 packages > began including it, and that worked fine. But now it does this same > thing with either one I try. If I go back entirely to my compiled X, > though, quake 3 works (though at half-speed, but that's something else > entirely I think). > > Something odd, I just tried some other GL apps, (some GL xscreensavers, > terminus, chromium-bsu) and they seem to be working fine... I've no > idea why only quake 3 would refuse to work... > > I'd really appreciate it if anyone had any ideas or suggestions... > > Joel Fuster > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Error during start X with i810 VGA card. :(
Chung, (or is it Ha-Nyung?) I believe the DRI/AGP features require a much newer kernel. If you try kernel 2.4.0-test*, being sure to build with agpgart support, I think your system will work with 4.0.1. But I can't be sure. :) Best of luck. * Chung, Ha-Nyung <[EMAIL PROTECTED]> [001016 06:14]: > > Currently, I update X to 4.0.1 phase2, maybe correct?, in woody. > I'm using Compaq Deskpro with VGA card using i810 chipset. > With XF86 3.3.6, I have no problem using X with this machine, > but after updating I got the error during startx. > /var/log/XFree86.0.log file is following... > > > XFree86 Version 4.0.1c / X Window System > (protocol Version 11, revision 0, vendor release 6400) > Release Date: 28 August 2000 > 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) > Operating System: Linux 2.2.17pre10 i686 [ELF] > Module Loader present > (==) Log file: "/var/log/XFree86.0.log", Time: Mon Oct 16 21:48:03 2000 > (==) Using config file: "/etc/X11/XF86Config-4" > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (??) unknown. > (==) ServerLayout "Default Layout" > (**) |-->Screen "Default Screen" (0) > (**) | |-->Monitor "Generic Monitor" > (**) | |-->Device "Generic Graphics Device" > (**) |-->Input Device "Generic Keyboard" > (**) Option "XkbRules" "xfree86" > (**) XKB: rules: "xfree86" > (**) Option "XkbModel" "pc104" > (**) XKB: model: "pc104" > (**) Option "XkbLayout" "us" > (**) XKB: layout: "us" > (**) |-->Input Device "Generic Mouse" > (**) FontPath set to > "/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi:unscaled,/usr/lib/X11/fonts/75dpi:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/sun" > (==) RgbPath set to "/usr/X11R6/lib/X11/rgb" > (==) ModulePath set to "/usr/X11R6/lib/modules" > (--) using VT number 7 > > (II) Module ABI versions: > XFree86 ANSI C Emulation: 0.1 > XFree86 Video Driver: 0.3 > XFree86 XInput driver : 0.1 > XFree86 Server Extension : 0.1 > XFree86 Font Renderer : 0.1 > (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.0.1c, module version = 1.0.0 > Module class: XFree86 Font Renderer > ABI class: XFree86 Font Renderer, version 0.1 > (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.0.1c, module version = 0.1.0 > ABI class: XFree86 Video Driver, version 0.3 > (II) PCI: Probing config type using method 1 > (II) PCI: Config type is 1 > (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 > (II) PCI: PCI scan (all values are in hex) > (II) PCI: 00:00:0: chip 8086,7124 card , rev 03 class 06,00,00 hdr 00 > (II) PCI: 00:01:0: chip 8086,7125 card 0e11,b191 rev 03 class 03,00,00 hdr 00 > (II) PCI: 00:1e:0: chip 8086,2418 card , rev 02 class 06,04,00 hdr 01 > (II) PCI: 00:1f:0: chip 8086,2410 card , 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:5: chip 8086,2415 card 0e11,b189 rev 02 class 04,01,00 hdr 00 > (II) PCI: 01:09:0: chip 8086,1229 card 8086,0009 rev 05 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.0.1c, module version = 0.1.0 > ABI class: XFree86 Video Driver, version 0.3 > (II) UnloadModule: "scanpci" > (II) Unloading /usr/X11R6/lib/modules/libscanpci.a > (II) Host-to-PCI bridge: > (II) Bus -1: bridge is at (0:0:0), (-1,-1,0), BCTRL: 0x00 (VGA_EN is cleared) > (II) Bus -1 I/O range: > [0] -1 0x - 0x (0x1) IX[B] > (II) Bus -1 non-prefetchable memory range: > [0] -1 0x - 0x (0x0) MX[B] > (II) Bus -1 prefetchable memory range: > [0] -1 0x - 0x (0x0) MX[B] > (II) PCI-to-ISA bridge: > (II) Bus -1: bridge is at (0:31:0), (0,-1,0), BCTRL: 0x00 (VGA_EN is cleared) > (II) Bus -1 I/O range: > (II) Bus -1 non-prefetchable memory range: > (II) Bus -1 prefetchable memory range: > (II) PCI-to-PCI bridge: > (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 0x1000 - 0x10ff (0x100) IX[B] > [1] -1 0x1400 - 0x14ff (0x100) IX[B] > [2] -1 0x1800 - 0x0
Re: debian large fonts anti-aliasing
Check you /etc/X11/XF86Config file. I bet you have references to the 75 and 100 dpi fonts in your fontpath before the font server. Also try adding :noscale to the end of the 75dpi and 100dpi font directories. HTH * Fabricio Matheus Goncalves <[EMAIL PROTECTED]> [001016 09:28]: > > OS: Debian Gnu/Linux 2.2 > > Aplication: xfs (XFree86) 3.3.6-11 > > Problem: In redhat with the same XFree version (3.3.6) it can display nice > large fonts. > Now using debian that fonts show broken, a think that is missing > anti-aliasing, but i dont know. > When i point my debian X to use a redhat xfs running at another computer > all works fine. > So i try install redhat xfs using alien to convert package, but the result > is yet broken fonts. > Im very confuse, and didnt find any reference to this kind of throuble. > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Re: Error during start X with i810 VGA card. :(
Chung, (or is it Ha-Nyung?) I believe the DRI/AGP features require a much newer kernel. If you try kernel 2.4.0-test*, being sure to build with agpgart support, I think your system will work with 4.0.1. But I can't be sure. :) Best of luck. * Chung, Ha-Nyung <[EMAIL PROTECTED]> [001016 06:14]: > > Currently, I update X to 4.0.1 phase2, maybe correct?, in woody. > I'm using Compaq Deskpro with VGA card using i810 chipset. > With XF86 3.3.6, I have no problem using X with this machine, > but after updating I got the error during startx. > /var/log/XFree86.0.log file is following... > > > XFree86 Version 4.0.1c / X Window System > (protocol Version 11, revision 0, vendor release 6400) > Release Date: 28 August 2000 > 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) > Operating System: Linux 2.2.17pre10 i686 [ELF] > Module Loader present > (==) Log file: "/var/log/XFree86.0.log", Time: Mon Oct 16 21:48:03 2000 > (==) Using config file: "/etc/X11/XF86Config-4" > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (??) unknown. > (==) ServerLayout "Default Layout" > (**) |-->Screen "Default Screen" (0) > (**) | |-->Monitor "Generic Monitor" > (**) | |-->Device "Generic Graphics Device" > (**) |-->Input Device "Generic Keyboard" > (**) Option "XkbRules" "xfree86" > (**) XKB: rules: "xfree86" > (**) Option "XkbModel" "pc104" > (**) XKB: model: "pc104" > (**) Option "XkbLayout" "us" > (**) XKB: layout: "us" > (**) |-->Input Device "Generic Mouse" > (**) FontPath set to >"/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi:unscaled,/usr/lib/X11/fonts/75dpi:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/sun" > (==) RgbPath set to "/usr/X11R6/lib/X11/rgb" > (==) ModulePath set to "/usr/X11R6/lib/modules" > (--) using VT number 7 > > (II) Module ABI versions: > XFree86 ANSI C Emulation: 0.1 > XFree86 Video Driver: 0.3 > XFree86 XInput driver : 0.1 > XFree86 Server Extension : 0.1 > XFree86 Font Renderer : 0.1 > (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.0.1c, module version = 1.0.0 > Module class: XFree86 Font Renderer > ABI class: XFree86 Font Renderer, version 0.1 > (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.0.1c, module version = 0.1.0 > ABI class: XFree86 Video Driver, version 0.3 > (II) PCI: Probing config type using method 1 > (II) PCI: Config type is 1 > (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 > (II) PCI: PCI scan (all values are in hex) > (II) PCI: 00:00:0: chip 8086,7124 card , rev 03 class 06,00,00 hdr 00 > (II) PCI: 00:01:0: chip 8086,7125 card 0e11,b191 rev 03 class 03,00,00 hdr 00 > (II) PCI: 00:1e:0: chip 8086,2418 card , rev 02 class 06,04,00 hdr 01 > (II) PCI: 00:1f:0: chip 8086,2410 card , 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:5: chip 8086,2415 card 0e11,b189 rev 02 class 04,01,00 hdr 00 > (II) PCI: 01:09:0: chip 8086,1229 card 8086,0009 rev 05 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.0.1c, module version = 0.1.0 > ABI class: XFree86 Video Driver, version 0.3 > (II) UnloadModule: "scanpci" > (II) Unloading /usr/X11R6/lib/modules/libscanpci.a > (II) Host-to-PCI bridge: > (II) Bus -1: bridge is at (0:0:0), (-1,-1,0), BCTRL: 0x00 (VGA_EN is cleared) > (II) Bus -1 I/O range: > [0] -1 0x - 0x (0x1) IX[B] > (II) Bus -1 non-prefetchable memory range: > [0] -1 0x - 0x (0x0) MX[B] > (II) Bus -1 prefetchable memory range: > [0] -1 0x - 0x (0x0) MX[B] > (II) PCI-to-ISA bridge: > (II) Bus -1: bridge is at (0:31:0), (0,-1,0), BCTRL: 0x00 (VGA_EN is cleared) > (II) Bus -1 I/O range: > (II) Bus -1 non-prefetchable memory range: > (II) Bus -1 prefetchable memory range: > (II) PCI-to-PCI bridge: > (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 0x1000 - 0x10ff (0x100) IX[B] > [1] -1 0x1400 - 0x14ff (0x100) IX[B] > [2] -1 0x1800 - 0x0
Re: debian large fonts anti-aliasing
Check you /etc/X11/XF86Config file. I bet you have references to the 75 and 100 dpi fonts in your fontpath before the font server. Also try adding :noscale to the end of the 75dpi and 100dpi font directories. HTH * Fabricio Matheus Goncalves <[EMAIL PROTECTED]> [001016 09:28]: > > OS: Debian Gnu/Linux 2.2 > > Aplication: xfs (XFree86) 3.3.6-11 > > Problem: In redhat with the same XFree version (3.3.6) it can display nice > large fonts. > Now using debian that fonts show broken, a think that is missing > anti-aliasing, but i dont know. > When i point my debian X to use a redhat xfs running at another computer > all works fine. > So i try install redhat xfs using alien to convert package, but the result > is yet broken fonts. > Im very confuse, and didnt find any reference to this kind of throuble. > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [codedj@echo.ru: X11]
Eugene, if you feel like being extremely brave, you can try the testing .debs Branden has made available. They seem to work for me, but if you need something known to be solid, continue using 3.3.x. Take a look in the debian-x archives for Branden's mini-faq. You will be sorry if you do not read it first. If you are still feeling like you want to give it a shot, add this line to your apt sources.list: deb http://samosa.debian.org/~branden woody/i386/ As for packages for specific video cards, do not expect those. Most of why XFree86 wrote version 4.0 is to get rid of video-card specific/OS specific X servers. Now, there is an X server binary for each OS/cpu, which loads the modules describing how to drive the video cards. Thus, the individual drivers are rather small. (vga_drv.o is 14k; the largest xfree86-supplied driver is 256k. Vendor-supplied ones may be larger, my Matrox supplied driver is 600k.) All told, they add something like three megs. The hassle, and duplication of code, means Branden will probably never supply video-card specific packages. However, some vendors may (and probably should :) provide .debs that will install their own drivers. The size of those would be expected to be under a megabyte or so. But, of course, I don't speak for Branden. All I know, if I were asked to do his job, I would never consider video-card specific packages. * Branden Robinson <[EMAIL PROTECTED]> [001015 19:18]: > - Forwarded message from Evgeny Chukreev <[EMAIL PROTECTED]> - > > From: Evgeny Chukreev <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: X11 > Date: Thu, 12 Oct 2000 14:06:52 +0700 > Delivered-To: [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > User-Agent: Mutt/1.0i > > Hello Branden! > > When can I expect a release of X's version 4.0.X compiled to "deb" > package? I mean separate packages for each videocard (I don't want to > download one large package sized 10 Megabytes). > > P.S. Where did http://www.debian.org/~branden page move? > P.P.S. Sorry for stylistic mistakes (I am russian). > > Best regards, Eugene > > - End forwarded message - > > -- > G. Branden Robinson|A celibate clergy is an especially good > Debian GNU/Linux |idea, because it tends to suppress any > [EMAIL PROTECTED] |hereditary propensity toward fanaticism. > http://deadbeast.net/~branden/ |-- Carl Sagan
Re: [codedj@echo.ru: X11]
Eugene, if you feel like being extremely brave, you can try the testing .debs Branden has made available. They seem to work for me, but if you need something known to be solid, continue using 3.3.x. Take a look in the debian-x archives for Branden's mini-faq. You will be sorry if you do not read it first. If you are still feeling like you want to give it a shot, add this line to your apt sources.list: deb http://samosa.debian.org/~branden woody/i386/ As for packages for specific video cards, do not expect those. Most of why XFree86 wrote version 4.0 is to get rid of video-card specific/OS specific X servers. Now, there is an X server binary for each OS/cpu, which loads the modules describing how to drive the video cards. Thus, the individual drivers are rather small. (vga_drv.o is 14k; the largest xfree86-supplied driver is 256k. Vendor-supplied ones may be larger, my Matrox supplied driver is 600k.) All told, they add something like three megs. The hassle, and duplication of code, means Branden will probably never supply video-card specific packages. However, some vendors may (and probably should :) provide .debs that will install their own drivers. The size of those would be expected to be under a megabyte or so. But, of course, I don't speak for Branden. All I know, if I were asked to do his job, I would never consider video-card specific packages. * Branden Robinson <[EMAIL PROTECTED]> [001015 19:18]: > - Forwarded message from Evgeny Chukreev <[EMAIL PROTECTED]> - > > From: Evgeny Chukreev <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: X11 > Date: Thu, 12 Oct 2000 14:06:52 +0700 > Delivered-To: [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > User-Agent: Mutt/1.0i > > Hello Branden! > > When can I expect a release of X's version 4.0.X compiled to "deb" > package? I mean separate packages for each videocard (I don't want to > download one large package sized 10 Megabytes). > > P.S. Where did http://www.debian.org/~branden page move? > P.P.S. Sorry for stylistic mistakes (I am russian). > > Best regards, Eugene > > - End forwarded message - > > -- > G. Branden Robinson|A celibate clergy is an especially good > Debian GNU/Linux |idea, because it tends to suppress any > [EMAIL PROTECTED] |hereditary propensity toward fanaticism. > http://deadbeast.net/~branden/ |-- Carl Sagan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
config file problems?
Greetings all. I just apt-get upgraded my system, and watched these messages roll past. Has anyone else seen them, and if so, is this something that Branden should know about or does know about? (Back to the `I don't support upgrades between the testing versions'?) Preparing to replace xbase-clients 4.0.1-0phase2v15 (using .../xbase-clients_4.0.1-0phase2v17_i386.deb) ... Unpacking replacement xbase-clients ... dpkg - warning, overriding problem because --force enabled: trying to overwrite `/etc/X11/app-defaults/XF86Cfg', which is also in package xserver-xfree86 dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/X11R6/bin/xf86cfg', which is also in package xserver-xfree86 dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/X11R6/man/man1/xf86cfg.1x.gz', which is also in package xserver-xfree86 Thanks!
config file problems?
Greetings all. I just apt-get upgraded my system, and watched these messages roll past. Has anyone else seen them, and if so, is this something that Branden should know about or does know about? (Back to the `I don't support upgrades between the testing versions'?) Preparing to replace xbase-clients 4.0.1-0phase2v15 (using .../xbase-clients_4.0.1-0phase2v17_i386.deb) ... Unpacking replacement xbase-clients ... dpkg - warning, overriding problem because --force enabled: trying to overwrite `/etc/X11/app-defaults/XF86Cfg', which is also in package xserver-xfree86 dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/X11R6/bin/xf86cfg', which is also in package xserver-xfree86 dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/X11R6/man/man1/xf86cfg.1x.gz', which is also in package xserver-xfree86 Thanks! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [debian-x] Hardware GL with a G400
* Gordon Heydon <[EMAIL PROTECTED]> [001013 20:20]: > but what about the libGLU and libGL libraries? don't you need those. At > the moment I have the Utah ones is that enough. Well, yes, you do. XF86 4.0.1 currently provides libGL. Shortly they will begin providing libGLU. (It is a technical issue -- it is the only file in their distribution that uses C++.)
Re: [debian-x] Hardware GL with a G400
* Gordon Heydon <[EMAIL PROTECTED]> [001013 20:20]: > but what about the libGLU and libGL libraries? don't you need those. At > the moment I have the Utah ones is that enough. Well, yes, you do. XF86 4.0.1 currently provides libGL. Shortly they will begin providing libGLU. (It is a technical issue -- it is the only file in their distribution that uses C++.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Hardware GL with a G400
Gordon, you are in luck, this was my situation exactly. Go to matrox.com, find their drivers section, and download their linux driver. It should be one file. Be sure to take a look at their readme, it is good enough to get you installed. (except for the bit about groups and DRI don't bother with setting a group for DRI.) You will need a recent kernel. I use 2.4.0-test7. I built my kernel with agpgart and mga modules available. They may or may not be needed. I'd bet agpgart is required, mga isn't. There are two ways of getting Matrox's mga_drv.o into use -- replace XFree86's version in /usr/X11R6/lib/modules/drivers/ with matrox's (clunky, will get overwritten with each new xf86 upgrade unless you use dpkg diversions...) -or- (the recommended way) is to use a direct path in your /etc/X11/XF86Config-4 file to load the new module. I haven't gone this route (lazy) but suggest you do. Sadly, I don't know the syntax for this, so I suggest you look for all of Branden's postings in the archives for more information about this. (Perhaps he mentioned it in a thread with someone from nvidia...) Once things are in place, modprobe agpgart, modprobe mga, and startx. I have attached my XF86Config file for reference... * Gordon Heydon <[EMAIL PROTECTED]> [001013 00:14]: > Hello, > > This is a simple question, can anyone tell me how to or better point me > in the direction of some documentation on how to get hardware 3gl going > with my dual head g400 (I am only using 1 head at the moment) with the > Xfree 4.0.1 debs found here. > > Thanks in advance > > Gordon. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > Section "ServerLayout" Identifier "Dual" Screen "Screen0" RightOf "Screen1" Screen "Screen1" InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" Option "Xinerama" EndSection Section "ServerLayout" Identifier "Single" Screen "Screen0" InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" FontPath "/usr/X11R6/lib/X11/fonts/freefont/" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/PEX/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:noscale" FontPath "/usr/X11R6/lib/X11/fonts/misc/:noscale" EndSection Section "Module" Load "GLcore" Load "dbe" Load "dri" Load "extmod" Load "glx" Load "pex5" Load "record" Load "xie" Load "freetype" Load "type1" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/mouse" Option "ZAxisMapping" "4 5" EndSection Section "Monitor" Identifier "Mitsubishi" VendorName "MEL" ModelName"42c0" HorizSync30.0 - 105.0 VertRefresh 70.0 - 152.0 Option "DPMS" #ModeLine "640x480" 45.8 640 672 768 864 480 488 494 530 -HSync -VSync EndSection Section "Monitor" Identifier "Sony" HorizSync60.5 - 82.0 VertRefresh 65.0 - 100.0 Option "DPMS" EndSection Section "Device" Identifier "G400_0" Driver "mga" VendorName "Matrox" BoardName "MGA G400 AGP" BusID "PCI:1:0:0" Screen 0 EndSection Section "Device" Identifier "G400_1" Driver "mga" VendorName "Matrox" BoardName "MGA G400 AGP" BusID "PCI:1:0:0" Screen 1 EndSection Section "Screen" Identifier "Screen0" Device "G400_0" Monitor"Mitsubishi" DefaultDepth 16 SubSection "Display" Depth 1 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection E
Re: Hardware GL with a G400
Gordon, you are in luck, this was my situation exactly. Go to matrox.com, find their drivers section, and download their linux driver. It should be one file. Be sure to take a look at their readme, it is good enough to get you installed. (except for the bit about groups and DRI don't bother with setting a group for DRI.) You will need a recent kernel. I use 2.4.0-test7. I built my kernel with agpgart and mga modules available. They may or may not be needed. I'd bet agpgart is required, mga isn't. There are two ways of getting Matrox's mga_drv.o into use -- replace XFree86's version in /usr/X11R6/lib/modules/drivers/ with matrox's (clunky, will get overwritten with each new xf86 upgrade unless you use dpkg diversions...) -or- (the recommended way) is to use a direct path in your /etc/X11/XF86Config-4 file to load the new module. I haven't gone this route (lazy) but suggest you do. Sadly, I don't know the syntax for this, so I suggest you look for all of Branden's postings in the archives for more information about this. (Perhaps he mentioned it in a thread with someone from nvidia...) Once things are in place, modprobe agpgart, modprobe mga, and startx. I have attached my XF86Config file for reference... * Gordon Heydon <[EMAIL PROTECTED]> [001013 00:14]: > Hello, > > This is a simple question, can anyone tell me how to or better point me > in the direction of some documentation on how to get hardware 3gl going > with my dual head g400 (I am only using 1 head at the moment) with the > Xfree 4.0.1 debs found here. > > Thanks in advance > > Gordon. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > Section "ServerLayout" Identifier "Dual" Screen "Screen0" RightOf "Screen1" Screen "Screen1" InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" Option "Xinerama" EndSection Section "ServerLayout" Identifier "Single" Screen "Screen0" InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" FontPath "/usr/X11R6/lib/X11/fonts/freefont/" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/PEX/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:noscale" FontPath "/usr/X11R6/lib/X11/fonts/misc/:noscale" EndSection Section "Module" Load "GLcore" Load "dbe" Load "dri" Load "extmod" Load "glx" Load "pex5" Load "record" Load "xie" Load "freetype" Load "type1" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/mouse" Option "ZAxisMapping" "4 5" EndSection Section "Monitor" Identifier "Mitsubishi" VendorName "MEL" ModelName"42c0" HorizSync30.0 - 105.0 VertRefresh 70.0 - 152.0 Option "DPMS" #ModeLine "640x480" 45.8 640 672 768 864 480 488 494 530 -HSync -VSync EndSection Section "Monitor" Identifier "Sony" HorizSync60.5 - 82.0 VertRefresh 65.0 - 100.0 Option "DPMS" EndSection Section "Device" Identifier "G400_0" Driver "mga" VendorName "Matrox" BoardName "MGA G400 AGP" BusID "PCI:1:0:0" Screen 0 EndSection Section "Device" Identifier "G400_1" Driver "mga" VendorName "Matrox" BoardName "MGA G400 AGP" BusID "PCI:1:0:0" Screen 1 EndSection Section "Screen" Identifier "Screen0" Device "G400_0" Monitor"Mitsubishi" DefaultDepth 16 SubSection "Display" Depth 1 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection
Re: dexter
* Branden Robinson <[EMAIL PROTECTED]> [001010 21:20]: > If you have already written a 4.x XF86Config file, I suggest moving it to > /etc/X11/XF86Config-4. I do not support upgrades between versions of these > experimental packages; that is the main problem that people are seeing. Hey, this is just what I was looking for. :) Thanks Branden!
dexter
Hey, Dexter looks pretty cool; my one suggestion is it should have a ``I have a working XF86Config file already'' option near the front of it, or ``install a default and useless XF86Config file for me''. If you want them hidden behind an ``expert'' button, that would be fine by me. Somehow, I have this feeling that my setup is a bit too strange to expect dexter to handle it well (dualhead g400 using matrox's driver). (When I don't have homework to work on, I shall give dexter a proper test drive. :) Thanks Branden (and others, if others need thanking. :)
Re: dexter
* Branden Robinson <[EMAIL PROTECTED]> [001010 21:20]: > If you have already written a 4.x XF86Config file, I suggest moving it to > /etc/X11/XF86Config-4. I do not support upgrades between versions of these > experimental packages; that is the main problem that people are seeing. Hey, this is just what I was looking for. :) Thanks Branden! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Unidentified subject!
Chris, I have a logitech corded wheel mouse (the underside claims it is a model M-C48, but I *think* its retail name is ``first mouse+'') ps/2, that works quite well under XF864.0.1. I do not have gpm installed. Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/mouse" Option "ZAxisMapping" "4 5" EndSection /dev/mouse is a symlink to /dev/psaux. I am running an ABIT dual celeron machine, g400max with the matrox supplied drivers. HTH * Chris Hanlon <[EMAIL PROTECTED]> [001010 19:00]: > Debian XFree86 4.0.x test notes > > I have being using 4.0.x on debian woody with the following hardware + > software setup since Phase2 debs started to show up. > > Voodoo 3 2000 (pci) video card > Logitech cordless wheel mouse (ps/2) > Abit KA7 motherboard (RX and TY bios) > Samsung SyncMaster 955SL monitor > > 2.4.0-test[1,5,6,8,9] kernel > I have the following notes > > Mouse problems > -- > The mouse jumps allover the place and clicks randomly if I'm running X as a > regular user and gpm is running > > The mouse will not move if I run X as root and gpm is running. > > The mouse occasionally clicked (while moving) until I upgraded my > bios to the TY bios. BTW. The TY bios fixes a "win95 only" ps/2 mouse bug. > > My XF86Config-4 says the following > > Section "InputDevice" > Identifier "Mouse0" > Driver "mouse" > Option "Protocol" "MouseManPlusPS/2" > Option "Device" "/dev/psaux" > EndSection > > DEXTER > -- > Dexter wouldn't run as /etc/X11/dexter-tmp didn't exist. This stoped > phase2v14 xserver-xfree86 debs from installing. > > Dexter wouldn't detect my mouse (I with gpm on and gpm off, I tried linking > /dev/mouse to both /dev/gpmdata and /dev/psaux ie. ln -sf /dev/psaux > /dev/mouse. > > Dexter doesn't list any refresh rates between 60 and 85 for the resolution > 1280x1024 (I use 79 (75 will do but 60 is yukky and 85 doesn't work)). > > -- > Is anyone else having similar mouse problems? Does anyone have a similar > mouse working corectly > > Chris > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
dexter
Hey, Dexter looks pretty cool; my one suggestion is it should have a ``I have a working XF86Config file already'' option near the front of it, or ``install a default and useless XF86Config file for me''. If you want them hidden behind an ``expert'' button, that would be fine by me. Somehow, I have this feeling that my setup is a bit too strange to expect dexter to handle it well (dualhead g400 using matrox's driver). (When I don't have homework to work on, I shall give dexter a proper test drive. :) Thanks Branden (and others, if others need thanking. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Unidentified subject!
Chris, I have a logitech corded wheel mouse (the underside claims it is a model M-C48, but I *think* its retail name is ``first mouse+'') ps/2, that works quite well under XF864.0.1. I do not have gpm installed. Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/mouse" Option "ZAxisMapping" "4 5" EndSection /dev/mouse is a symlink to /dev/psaux. I am running an ABIT dual celeron machine, g400max with the matrox supplied drivers. HTH * Chris Hanlon <[EMAIL PROTECTED]> [001010 19:00]: > Debian XFree86 4.0.x test notes > > I have being using 4.0.x on debian woody with the following hardware + > software setup since Phase2 debs started to show up. > > Voodoo 3 2000 (pci) video card > Logitech cordless wheel mouse (ps/2) > Abit KA7 motherboard (RX and TY bios) > Samsung SyncMaster 955SL monitor > > 2.4.0-test[1,5,6,8,9] kernel > I have the following notes > > Mouse problems > -- > The mouse jumps allover the place and clicks randomly if I'm running X as a > regular user and gpm is running > > The mouse will not move if I run X as root and gpm is running. > > The mouse occasionally clicked (while moving) until I upgraded my > bios to the TY bios. BTW. The TY bios fixes a "win95 only" ps/2 mouse bug. > > My XF86Config-4 says the following > > Section "InputDevice" > Identifier "Mouse0" > Driver "mouse" > Option "Protocol" "MouseManPlusPS/2" > Option "Device" "/dev/psaux" > EndSection > > DEXTER > -- > Dexter wouldn't run as /etc/X11/dexter-tmp didn't exist. This stoped > phase2v14 xserver-xfree86 debs from installing. > > Dexter wouldn't detect my mouse (I with gpm on and gpm off, I tried linking > /dev/mouse to both /dev/gpmdata and /dev/psaux ie. ln -sf /dev/psaux > /dev/mouse. > > Dexter doesn't list any refresh rates between 60 and 85 for the resolution > 1280x1024 (I use 79 (75 will do but 60 is yukky and 85 doesn't work)). > > -- > Is anyone else having similar mouse problems? Does anyone have a similar > mouse working corectly > > Chris > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: strange looking fonts.
* Olaf Meeuwissen <[EMAIL PROTECTED]> [001009 22:58]: > > What I would imagine to fix your problem is to edit your > > /etc/X11/XF86Config file. I bet the 100dpi fonts are listed before the > > 75 dpi fonts. If so, swap their order and restart X. > You could also just purge the xfonts-100dpi package ;-) Of course, this is a much better idea, since if they are listed second, they aren't likely to be used, and just take up space that could be used for something more useful. :)
Re: strange looking fonts.
Russell, the debian-x mail list (in recent times anyway) is more intended for developers and ginuea pigs of XF86 4.0. debian-users is more appropriate. What I would imagine to fix your problem is to edit your /etc/X11/XF86Config file. I bet the 100dpi fonts are listed before the 75 dpi fonts. If so, swap their order and restart X. If this doesn't fix it, then perhaps mucking with the X server's idea of the DPI of the display is the only way to go. * Russell Davies <[EMAIL PROTECTED]> [001008 17:08]: > Hi, > I'm a long time unix user -- I've just recently installed > debian on my home system, basically my problem boils down to > fonts not looking "right" in X, where right is defined as to > what I usually expect with my combination of software. > > I use twm and X everywhere, on solaris, bsd, linux -- debian is > the first instance where the fonts have looked different, they > seem to be oversized -- it happens on all applications, the > fonts in netscape look bigger, in title bars. (I installed > netsccape-4.75 from the usual sources, so it's not a netscape > specific font problem). > > Has anyone else experienced this? Is it something to do with the > Xserver itself? (I'm using the SVGA server for a riva tnt). > Any suggestions, explanations would be appreciated. > > regards, > Russell. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Re: [AKennedy@bursteinlabs.com: GeForce2 divers for XFree86 4.x/Debian]
Yeah, me too. Andrew, your best and easiest bet is to see if nvidia has a tarball, or a single file, the way matrox does. It is very easy with matrox, and if they don't offer something so simple, then I suggest you write them, and ask them to try the matrox drivers. :) * Branden Robinson <[EMAIL PROTECTED]> [001007 18:33]: > Someone with an appropriate NVidia card want to do this? > > I think he's probably talking about NVidia's non-free driver(s). > > - Forwarded message from Andrew Kennedy <[EMAIL PROTECTED]> - > > From: "Andrew Kennedy" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Subject: GeForce2 divers for XFree86 4.x/Debian > Date: Sat, 7 Oct 2000 15:46:00 -0700 > Delivered-To: [EMAIL PROTECTED] > Delivered-To: [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > > >I was wondering if you could be kind enough to repackage the geforce2 >drivers that are in RPM format into deb packages. I have had no luck >getting them to install properly. GeForce2 cards really only support >XFree86 4.x. I really love debian's advantages over other >distributions but if I can't get X to run it is hard to say this is >the right distibution. =) So the reality is that I am holding out >for debian's XFree86 4.x release but in the meantime I want to play >around with your test packages (which installed fine btw). Also, if >you were going to do this could you make sure to package the SMP >version also (I have 2 cpu's). Thanks, I really would appreciate if >you did this. If not, I understand. Get the final out! =) > > > >Andrew Kennedy > > > >[1]http://www.nvidia.com/Products/OpenLinuxDwn.nsf/b99b7f622d429347882 >568c800771b6c?OpenView&Start=1&Count=30&Expand=2#2 > > References > >1. > http://www.nvidia.com/Products/OpenLinuxDwn.nsf/b99b7f622d429347882568c800771b6c?OpenView&Start=1&Count=30&Expand=2#2 > > - End forwarded message - > > -- > G. Branden Robinson|A celibate clergy is an especially good > Debian GNU/Linux |idea, because it tends to suppress any > [EMAIL PROTECTED] |hereditary propensity toward fanaticism. > http://deadbeast.net/~branden/ |-- Carl Sagan
Re: [AKennedy@bursteinlabs.com: GeForce2 divers for XFree86 4.x/Debian]
Yeah, me too. Andrew, your best and easiest bet is to see if nvidia has a tarball, or a single file, the way matrox does. It is very easy with matrox, and if they don't offer something so simple, then I suggest you write them, and ask them to try the matrox drivers. :) * Branden Robinson <[EMAIL PROTECTED]> [001007 18:33]: > Someone with an appropriate NVidia card want to do this? > > I think he's probably talking about NVidia's non-free driver(s). > > - Forwarded message from Andrew Kennedy <[EMAIL PROTECTED]> - > > From: "Andrew Kennedy" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Subject: GeForce2 divers for XFree86 4.x/Debian > Date: Sat, 7 Oct 2000 15:46:00 -0700 > Delivered-To: [EMAIL PROTECTED] > Delivered-To: [EMAIL PROTECTED] > Message-ID: <000a01c030b0$5e733600$6501a8c0@drewd> > > >I was wondering if you could be kind enough to repackage the geforce2 >drivers that are in RPM format into deb packages. I have had no luck >getting them to install properly. GeForce2 cards really only support >XFree86 4.x. I really love debian's advantages over other >distributions but if I can't get X to run it is hard to say this is >the right distibution. =) So the reality is that I am holding out >for debian's XFree86 4.x release but in the meantime I want to play >around with your test packages (which installed fine btw). Also, if >you were going to do this could you make sure to package the SMP >version also (I have 2 cpu's). Thanks, I really would appreciate if >you did this. If not, I understand. Get the final out! =) > > > >Andrew Kennedy > > > >[1]http://www.nvidia.com/Products/OpenLinuxDwn.nsf/b99b7f622d429347882 >568c800771b6c?OpenView&Start=1&Count=30&Expand=2#2 > > References > >1. >http://www.nvidia.com/Products/OpenLinuxDwn.nsf/b99b7f622d429347882568c800771b6c?OpenView&Start=1&Count=30&Expand=2#2 > > - End forwarded message - > > -- > G. Branden Robinson|A celibate clergy is an especially good > Debian GNU/Linux |idea, because it tends to suppress any > [EMAIL PROTECTED] |hereditary propensity toward fanaticism. > http://deadbeast.net/~branden/ |-- Carl Sagan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Trouble with DRI on G200
* David Engel <[EMAIL PROTECTED]> [001006 08:08]: > I'm trying to get DRI working on my Matrox G200 and not having much > luck. Most of this is probably due to my ignorance of Linux 3d > support, but since it involves Debian specific changes to X, I thought > I'd ask here first. Well, I found it difficult to make work as well. It wasn't quite easy. I do not claim to know how it all works; I will give you my best understanding of the situation. DRI requires some help from the kernel that exists only in the 2.4 series. (And the 2.3, but who wants to run that now? :) To get my G400Max working, I had to load kernel modules agpgart and mga. At that point, using the Matrox driver seemed to make most things go. (q3a crashes after several minutes of play, UT doesn't even run, but the screensavers seemed accelerated.. :) > FYI, another partly related problem I've run into is that the mesag3 > package contains libGL and libGLU but the xlibmesa3 package only > contains libGL. What package is supposed to provide libGLU when > xlibmesa3 is used? As for libGLU, this has been hashed out many times in the past on this list. The short answer is, it isn't yet provided by the xf86 source, and until they provide it, branden has suggested a work around. It seemed like too much work to me, so I figured I would wait. :) Check the archives, they will have his suggestion. HTH
Re: Trouble with DRI on G200
* David Engel <[EMAIL PROTECTED]> [001006 08:08]: > I'm trying to get DRI working on my Matrox G200 and not having much > luck. Most of this is probably due to my ignorance of Linux 3d > support, but since it involves Debian specific changes to X, I thought > I'd ask here first. Well, I found it difficult to make work as well. It wasn't quite easy. I do not claim to know how it all works; I will give you my best understanding of the situation. DRI requires some help from the kernel that exists only in the 2.4 series. (And the 2.3, but who wants to run that now? :) To get my G400Max working, I had to load kernel modules agpgart and mga. At that point, using the Matrox driver seemed to make most things go. (q3a crashes after several minutes of play, UT doesn't even run, but the screensavers seemed accelerated.. :) > FYI, another partly related problem I've run into is that the mesag3 > package contains libGL and libGLU but the xlibmesa3 package only > contains libGL. What package is supposed to provide libGLU when > xlibmesa3 is used? As for libGLU, this has been hashed out many times in the past on this list. The short answer is, it isn't yet provided by the xf86 source, and until they provide it, branden has suggested a work around. It seemed like too much work to me, so I figured I would wait. :) Check the archives, they will have his suggestion. HTH -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: freefont and sharefont packages
I too had the same problem. The fix is simple. Edit your /etc/X11/XF86Config file. Notice there is a new Section "Files" that lists the freefont directory.. well, before there wasn't such a section, so the server used some defaults. With the section, it trusts you know what you are doing. Add the other paths to the font directories on your system, and the problem goes away. (I don't know if this is the *right* fix, maybe setting up a font server is the correct fix, but .. this worked for me! ;) Here is my Files section; you may need to modify it to suit your situation, but this is a start. :) Section "Files" FontPath "/usr/X11R6/lib/X11/fonts/freefont/" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/PEX/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/misc/" EndSection The only one you need to make it shutup about the fixed font is the misc directory. I imagine the rest add considerably to the experience, but I cna't be sure. :) * Thomas E. Vaughan <[EMAIL PROTECTED]> [001005 08:46]: > > Whenever I install either (or both) of the freefont and sharefont packages, > the X server fails to start because it cannot find font 'misc'. As soon as > I purge those packages, the X server will start again. > > Is this an incompatibility between the old X stuff and the new XF4 stuff? > If so, then is there a workaround? > > -- > Thomas E. Vaughan <[EMAIL PROTECTED]> > CIMMS/NSSL, Norman, OK, USA > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Re: freefont and sharefont packages
I too had the same problem. The fix is simple. Edit your /etc/X11/XF86Config file. Notice there is a new Section "Files" that lists the freefont directory.. well, before there wasn't such a section, so the server used some defaults. With the section, it trusts you know what you are doing. Add the other paths to the font directories on your system, and the problem goes away. (I don't know if this is the *right* fix, maybe setting up a font server is the correct fix, but .. this worked for me! ;) Here is my Files section; you may need to modify it to suit your situation, but this is a start. :) Section "Files" FontPath "/usr/X11R6/lib/X11/fonts/freefont/" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/PEX/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/misc/" EndSection The only one you need to make it shutup about the fixed font is the misc directory. I imagine the rest add considerably to the experience, but I cna't be sure. :) * Thomas E. Vaughan <[EMAIL PROTECTED]> [001005 08:46]: > > Whenever I install either (or both) of the freefont and sharefont packages, > the X server fails to start because it cannot find font 'misc'. As soon as > I purge those packages, the X server will start again. > > Is this an incompatibility between the old X stuff and the new XF4 stuff? > If so, then is there a workaround? > > -- > Thomas E. Vaughan <[EMAIL PROTECTED]> > CIMMS/NSSL, Norman, OK, USA > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sessreg not included in xbase-clients 4.0.1-0phase2v13
Joe, since this has never affected me I haven't bothered to learn; perhaps I should. But, I suggest you take a look at the archives for this group, as I know this topic has been beaten to death once or twice. * Joe Drew <[EMAIL PROTECTED]> [001004 14:23]: > For a while, I was seeing a mysterious inability for gdm to log in, and > finally tracked it down to its /etc/gdm/PreSession/Default script, > which calls /usr/X11R6/bin/sessreg. This is present in the woody version > of X, but not in the new packages. Is this a bug in gdm, the new X packages, > or has it moved to a new package from xbase-clients? > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Re: sessreg not included in xbase-clients 4.0.1-0phase2v13
Joe, since this has never affected me I haven't bothered to learn; perhaps I should. But, I suggest you take a look at the archives for this group, as I know this topic has been beaten to death once or twice. * Joe Drew <[EMAIL PROTECTED]> [001004 14:23]: > For a while, I was seeing a mysterious inability for gdm to log in, and > finally tracked it down to its /etc/gdm/PreSession/Default script, > which calls /usr/X11R6/bin/sessreg. This is present in the woody version > of X, but not in the new packages. Is this a bug in gdm, the new X packages, > or has it moved to a new package from xbase-clients? > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: A small question
Gorden, I have a suggestion; while I have 1600x1200 in my Modes line, I also run 1600x1200 all the time. So, I can't say one way or another if this will work. But, if I were a programmer at XFree86, I would start up in the first resolution listed with a desktop that size. Resolution changes downward would use a virtual desktop, resolution changes upward would increase (temporarily) the screen resolution. So, try putting 1600x1200 at the end of your Modes list. If that doesn't work, there is a Virtual entry in the display subsection. Full details are in XF86Config(5) (well, some details. Full details are in the source code. :) It might be able to help you. :) * Gordon Heydon <[EMAIL PROTECTED]> [000930 18:07]: > Hello, > > First off I would like to thank Branden for all the great work he is > doing. > > Secound I am having a little problem. I doing think it is a problem with > the packages but more of a configuration problem. > > When I put the more "1600x1200" into my list of mode lines I get as > expected 1600x1200 except that in all other resulutions I get a > 1600x1200 screen size on a what ever resolution screen, the screen then > does a pan and scan of the 1600x1200 area. > > I don't use 1600x1200 that offen but I do like to have it there without > having to edit my XF86Config nd restart my X Server everytime. > > Thanks in advance > Gordon. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Re: A small question
Gorden, I have a suggestion; while I have 1600x1200 in my Modes line, I also run 1600x1200 all the time. So, I can't say one way or another if this will work. But, if I were a programmer at XFree86, I would start up in the first resolution listed with a desktop that size. Resolution changes downward would use a virtual desktop, resolution changes upward would increase (temporarily) the screen resolution. So, try putting 1600x1200 at the end of your Modes list. If that doesn't work, there is a Virtual entry in the display subsection. Full details are in XF86Config(5) (well, some details. Full details are in the source code. :) It might be able to help you. :) * Gordon Heydon <[EMAIL PROTECTED]> [000930 18:07]: > Hello, > > First off I would like to thank Branden for all the great work he is > doing. > > Secound I am having a little problem. I doing think it is a problem with > the packages but more of a configuration problem. > > When I put the more "1600x1200" into my list of mode lines I get as > expected 1600x1200 except that in all other resulutions I get a > 1600x1200 screen size on a what ever resolution screen, the screen then > does a pan and scan of the 1600x1200 area. > > I don't use 1600x1200 that offen but I do like to have it there without > having to edit my XF86Config nd restart my X Server everytime. > > Thanks in advance > Gordon. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xterm (4.0.1-0phase2v11) depends on libc6 (>= 2.1.93)
* Kresimir Kukulj <[EMAIL PROTECTED]> [000927 14:03]: > Current unstable libc6 is 2.1.3-10. Is 2.1.93 an error or what? > xlibs 4.0.1-0phase2v11 for example depends on libc6 (>= 2.1.2) I don't know for sure what is going on, but it seems there was a legitimate 2.1.93, but that it was broke and possibly removed from the archives. It would explain why my apt is broken. :) I dunno. I figured I would wait a little while and see if someone has fixed whatever it is that is broke. :)
Re: xterm (4.0.1-0phase2v11) depends on libc6 (>= 2.1.93)
* Kresimir Kukulj <[EMAIL PROTECTED]> [000927 14:03]: > Current unstable libc6 is 2.1.3-10. Is 2.1.93 an error or what? > xlibs 4.0.1-0phase2v11 for example depends on libc6 (>= 2.1.2) I don't know for sure what is going on, but it seems there was a legitimate 2.1.93, but that it was broke and possibly removed from the archives. It would explain why my apt is broken. :) I dunno. I figured I would wait a little while and see if someone has fixed whatever it is that is broke. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: chips driver doesn't work anymore
* Sjoerd Simons <[EMAIL PROTECTED]> [000926 13:25]: > Please tell me if this isn't the right please to sent this mail. > I've been using the experimental debs from phase 1 and never had a problem, > untill phase2v9 and phase2v10. It seems that the chips driver is broken. I do think newbie@xfree86.org would be a better mailing list for these questions, since it isn't specific to Debian. (I don't think.) > X works alright when i replace chips_drv.o with an older version. > Unfortunately i can't supply any logs when using the newer version of > the driver , because when my machine enters graphical mode it hangs ;( X should also be leaving logs in /var/log/XFree86.?.log -- probably XFree86.0.log. (The ? corresponds with/to the display number, I think.) Check to see if it writes it to disk. (Be sure also to either give the machine plenty of time for the disk buffers to be flushed, or ensure that you manually flush the disk buffers while rebooting, either via telnetting/sshing into your computer and running shutdown normally, or via the system request key if you have that enabled in your 2.2 or higher kernel.. (the sysreq key does many neat things, but a sequence I hit when my X dies on me is alt-sysreq s, alt-sysreq u, alt-sysreq r, alt-sysreq b. That should sync the drives, and either umount them or remount them read only (I forget which does which, or if one or the other is better, so I hit them both :) and then reboot..))
Re: chips driver doesn't work anymore
* Sjoerd Simons <[EMAIL PROTECTED]> [000926 13:25]: > Please tell me if this isn't the right please to sent this mail. > I've been using the experimental debs from phase 1 and never had a problem, > untill phase2v9 and phase2v10. It seems that the chips driver is broken. I do think [EMAIL PROTECTED] would be a better mailing list for these questions, since it isn't specific to Debian. (I don't think.) > X works alright when i replace chips_drv.o with an older version. > Unfortunately i can't supply any logs when using the newer version of > the driver , because when my machine enters graphical mode it hangs ;( X should also be leaving logs in /var/log/XFree86.?.log -- probably XFree86.0.log. (The ? corresponds with/to the display number, I think.) Check to see if it writes it to disk. (Be sure also to either give the machine plenty of time for the disk buffers to be flushed, or ensure that you manually flush the disk buffers while rebooting, either via telnetting/sshing into your computer and running shutdown normally, or via the system request key if you have that enabled in your 2.2 or higher kernel.. (the sysreq key does many neat things, but a sequence I hit when my X dies on me is alt-sysreq s, alt-sysreq u, alt-sysreq r, alt-sysreq b. That should sync the drives, and either umount them or remount them read only (I forget which does which, or if one or the other is better, so I hit them both :) and then reboot..)) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
hehehh
Branden, thanks for putting in that great all-caps header file. I especially liked the part about the "upset X maintainer". :) Thanks for all the effort. I am enjoying using XF86 4.0.1! :)
hehehh
Branden, thanks for putting in that great all-caps header file. I especially liked the part about the "upset X maintainer". :) Thanks for all the effort. I am enjoying using XF86 4.0.1! :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Multihead-aware window managers (fvwm goofiness)
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [000925 08:51]: > > Use +xinerama. > > No can do, unless one of you guys can figure out how to do xinerama > between a colour display and a greyscale display. ;) Very simple -- make the color display the same bitdepth as the grayscale. (Not pretty, but simple! :)
Re: Multihead-aware window managers (fvwm goofiness)
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [000925 08:51]: > > Use +xinerama. > > No can do, unless one of you guys can figure out how to do xinerama > between a colour display and a greyscale display. ;) Very simple -- make the color display the same bitdepth as the grayscale. (Not pretty, but simple! :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
