[Xpert]Dual-head on trident cyberbladeai1d
Dear Xperts. Since I got my dual-boot RH7.2/Win98 laptop, it's been bugging me that windows does a nice xinerama-like two-screen virtual desktop, while linux and XFree86 4.1 doesn't... Since linux is really my preferred OS, I'd be really happy if somebody would tell me if xinerama for the trident driver with cyberbladeai1d chipset is available. Currently, my XF86Config-4 contains two devices, monitors and screens. Both devices contain a BusID "PCI:1:0:0" since it's an AGP device. However, XFree86 doesn't like this and crashes with the message "Entity already in use". Any pointers? Help is greatly appreciated! :-) Kind regards, -- ___ / \ / '_/\ //Paul M. Diderichsen \\/ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: ATI Radeon VE dual head support? [PATCH for Dell OEM boards]
> We have bought a number of Dells with the OEM RadeonVE card. I can > certainly confirm that they are strange compared to the out-of-box > Radeon VE QY, although the PCI vendor id is identical. Have a look at: > > http://wetlogic.net/stewart/xfree-radeon-ve/radeon-ve-dell.jpg > > to see the card and the single connector on the board. Unlike the > retail version of the board I have, this board does not duplicate > output on both connectors, but instead displays only on cable 1 (the > blue connector on the Y-adaptor in the picture), and nothing at all > on cable 2. Nice picture. Just to add, Dell also has a different Y-adaptor with two DVI-D outputs (working for the same card) as disscussed below. > When I tried a dual-head configuration that works successfully on a > retail version of the Radeon VE versions, I found two problems which > I patched: > > - The first problem is that the primary interface does not report > the BIOS value that radeon_driver.c expects in the function > RADEONGetBIOSParameters(). Instead, it reports only a CRT on > the secondary connector. In the single-headed case this works > correctly. > > In the dual-head case things would also work correctly except > that when RADEONPreInit() is called on the second screen instance, > it checks for BypassSecondary and quite silently returns FALSE. > This stumped me for a long time since there were no error > messages in the X log file that indicated why Screen 1 was > completely ignored in my XF86Config-4. > > I'm not sure I understand why it is an error ifthe BIOS > doesn't claim to detect a second monitor. Does this mean > the user must reboot in order to attach a second monitor, or > in many cases just because it happened to be off at boot time? > In my patch, I commented the return out, but I think it's > worth opening a discussion (I'm not on Xpert, so please Cc > me). The behavior as a result of this change is that if > there's a second screen definition and the card is multi-head, > and there's at least one monitor attached, the second monitor > is pre-initted. Current driver uses BIOS settings to detect connected monitors, this requires you to have correct monitors connected during the boot (some versions of BIOS can handle hot-plug, which will set correct settings even after boot). Ideally the driver should do monitor probe itself (scan through all DDC types and try to talk to the possible connected monitors). Even more, it should handle hot-plug interrupt, so that you can swap or plug a monitor even after X started. But all this takes time and man power to get implemented. BypassSecondary is used when only one monitor connected to the second CRT port while you have dual-head setup in the config file. I remember there was some problem before this flag was added. So be careful to comment it out. In you case, it seems you didn't have all monitors connected during the boot, the BIOS didn't detect one of your monitor which causes it's bypassed. > - The second problem is that the secondary monitor on the OEM > Dell Radeon VE uses DAC2 for output. There was actually a > bit of commented out code in RADEONInitCrtc2Registers() already, > so I simply added an option named "Crt2Dac2" and tested for > it there. The true maintainers of this code may want to add > another boolean field to RADEONEntRec and hunt for the option > elsewhere, if they think that's cleaner. > Thesecond screen definition in my XF86Config-4 now looks like: > > Section "Device" > Identifier "ATI Radeon 1" > Driver "radeon" > BoardName "Radeon" > BusID "PCI:1:0:0" > Option "AGPMode" "4" > Option "Crt2Dac2" > Screen 1 > EndSection DELL card can be auto detected from Sub-System Card ID of PCI configuration space. So you don't really need an option for it's special configuration. Yes, for DELL's two CRTs adaptor, you need to turn on TV DAC to drive secondary CRT (RADEON_DAC2_DAC2_CLK_SEL). For dual DVI-D cable, things are more complicated, mode validation routines have to be added and FP2 registers need to be programmed for the second flat panel. > The third problem, which I didn't deal with, is that the DDC info > for the two monitors attached was swapped. In other words, the DDC > info listed for screen 0 (the monitor displaying the settings listed > in the "Screen 0" Section, also the monitor connected to the first > cable) appeared in the section of the log file dedicated to screen 1, > and vice versa. This wasn't a big enough problem for me to solve, > and since it's hard to solve it without yet another option, I decided > to forego it. The DDCType from DELL card's BIOS does not follow the old rule, it need to be hard coded. I have working code on my system for both 2-CRT and 2-DVI adaptors. The code has lots of other changes since XF4.2
[Xpert]two graphic cards again and again and ...
Hi, Michel, We tried xfree86 4.2.0. In 4.2, doFramebufferMode has been set to TRUE. But no image displays on AGP card. Is there any other place where X disables the AGP card(primary card) that X doesn't use? It would appear that somewhere in the Xserver code the PCI bus (and AGP) is being scanned for graphics cards (by device class?). Can we modify that code so that the AGP card will not be detected or so that the server behaves as though there is no AGP card present in the machine? If so, do you know where we should look in the code to do such a modification? Thanks in advance, jing --- Michel Dänzer <[EMAIL PROTECTED]> wrote: >The X server disables graphics chips it doesn't use >because they can cause problems otherwise. > Look at > xc/programs/Xserver/hw/xfree86/common/xf86Bus.c, it > might be enough to hardcode doFramebufferMode to > TRUE. >The initial question is as follows: >I have two graphic cards in my box, one is ATI Rage >XL(PCI) and one is ATI Radeon VE QY(AGP). I would like >to control the AGP card from a kernel module we have >written (which displays on a projector) and I would >like to let X control the PCI card (which displays on >a flat panel monitor). While in console mode the >kernel module correctly displays images using the >AGP card and the message "ATI Rage SDRAM BIOS P/N >113-72307-100 4.330" is displayed using the PCI card. >We used the vesafb driver to configure the AGP >card (primary card according to BIOS) to the desired >mode of 1024x768. >The problem begins when we use startx. The PCI >controlled monitor starts X correctly but our >kernel module no longer has control of our AGP card >(no image displays on projector). >Does any know why X seems to be taking our control >of the AGP card away? >jing __ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]a problem about Xfree86 4.2.0
On Tue, 23 Apr 2002, Jing Xu wrote: > Yeah!!! It works. Of course, it does. Sheesh. > I have another question about Xfree86. This is also the reason why I try > Xfree86 4.2. > I have two graphic cards in my box, one is ATI Rage XL(PCI) and one is > ATI Radeon VE QY(AGP). I would like to control the AGP card from a > kernel module we have written (which displays on a projector) and I > would like to let X control the PCI card (which displays on a flat panel > monitor). While in console mode the kernel module correctly displays > images using the AGP card. > We used the vesafb driver to configure the AGP card (primary card > according to BIOS) to the desired mode of 1024x768. > The problem begins when we use startx. The PCI controlled monitor starts > X correctly but our kernel module no longer has control of our AGP card > (no image displays on projector). > We received the reply from Michael Danzer who suggested us that "Look at > xc/programs/Xserver/hw/xfree86/common/xf86Bus.c, it might be enough to > hardcode doFramebufferMode to TRUE." > In 4.2.0 "doFramebufferMode" has been set to TRUE. However, when I run > my program in X, still no image displays on projector(AGP card). But an > interesting thing is that the color is changed in X Window. In our > program we change the color palette, but this is supposed to work on > AGP(primary card) not PCI. It seems that PCI card has been set to the > primary card by X. > How can I prevent X from disabling the AGP card? Right now, you can't. That might be something to address in a future version, but I can't say for sure. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 Core Team member. ATI driver and X server internals. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Why no RGBA visual in XFree 4.1 software Mesa?
Sorry, in my desire to shorten the email, I appear to have skipped something important. Here are the snippets of my X log that led me to believe I'm in 32bpp: (II) Setting vga for screen 0. (==) ATI(0): Chipset: "ati". (**) ATI(0): Depth 24, (--) framebuffer bpp 32 . . . (==) ATI(0): RGB weight 888 (==) ATI(0): Default visual is TrueColor . . . (--) Depth 24 pixmap format is 32 bpp Of course, as someone else has pointed out, why does Mesa necessarily have to use the same pixel format (internally) as X does? Is it designed to avoid having to do format conversion per frame? Or did that requirement come up as part of the merge with the X code base? -'f On Tue, Apr 23, 2002 at 11:15:02AM -0700, Mark Vojkovich wrote: > On Mon, 22 Apr 2002, Geoffrey Broadwell wrote: > > [snip] > > Anyone have any clue what's going on? As far as I can interpret the tea > > leaves, it looks like I'm really running with 32-bit pixels, so I don't > > see a problem there . . . . > >I see only xdpyinfo and glxinfo attached. There's nothing in those > to specify whether or not you are in 24bpp or 32bpp. Why do you think > you are in 32bpp? > > > Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SAVESET extension proposal
Getting extensions going also ends up typically causing round trips, so lots of little ones would become a performance headache (though with batching, it could be avoided). - Jim -- Jim Gettys Cambridge Research Laboratory Compaq Computer Corporation [EMAIL PROTECTED] ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]SAVESET extension proposal
Owen Taylor <[EMAIL PROTECTED]> writes: > Here's a proposal for a tiny protocol extension (one request other than > QueryVersion) that would help a lot in making inter-client embedding > robust. > > I'm willing to do the work in implementing this for XFree86, though > I might need help in checking the protocol for sanity and figuring > out how to implement it. (A separate library for one request seems > like overkill, but I'm not sure that adding it to XLib would be > legitimate.) > > Does this proposal make sense? I went ahead and tried implementing my proposed extension; went quite easily as I expected. (This is with 'reparent to root' instead of 'reparent to WINDOW'.) In the functional part of the diff, where I have: - if(!pWin->realized && pWin->mapped) + if(!pWin->realized && pWin->mapped && pTmp->mapAction != SaveSetUnmap) pWin->mapped = FALSE; } - MapWindow(pWin, client); + if (pTmp->mapAction == SaveSetMap) + MapWindow(pWin, client); + else/* SaveSetUnmap */ + UnmapWindow(pWin, FALSE); I'm not sure I quite understand the original pWin->mapped = FALSE, so I'm not so confident in the change, though it seems to work in the limited testing I've done. The comparison of the size of the diff (~1000 lines) with the amount of it (~350 lines) which is not just adding a new extension and a new library certainly supports Keith's opposition to lots of little extensions. Regards, Owen saveset-extension-20020403.diff.gz Description: Initial implementation attempt
[Xpert]ATI Radeon 8500+Xinerama (second head blinks)
Hi, i'm experiencing a problem with my ati radeon 8500. I'm using 2 CRT Sony CPD G420 attached to both vga and dvi exits. The head attached to the DVI exit has got horizontal blinking linews, something like when your cellphone is near the monitor and it starts ringing. I got this problem in X (both xfree4.2 and CVS) ,in framebuffer and vga, where they are in clone mode (they are in clone mode in BIOS too, where i got this problem too). Silly thing i don't have this problem under WindowsXP except when playing games, where _sometimes_ the second head gives this problem. My System is a Debian Linux 2.4.18 box. That's my XF86Config-4: Section "Files" FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/lib/X11/fonts/Type1" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/lib/X11/fonts/75dpi" EndSection Section "Module" Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"pex5" Load"record" Load"speedo" Load"type1" Load"vbe" Load"xie" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc104" Option "XkbLayout" "it" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/psaux" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" Option "ZAxisMapping" "4 5" Option "Resolution""500" EndSection Section "Device" Identifier "Ati1" Driver "ati" Option "crt_screen" BusID "PCI:1:5:0" Screen 1 EndSection Section "Device" Identifier "Ati2" Driver "ati" Option "crt_screen" BusID "PCI:1:5:0" EndSection Section "Monitor" Identifier "Sony1" HorizSync 30-110 VertRefresh 48-170 Option "DPMS" EndSection Section "Monitor" Identifier "Sony2" HorizSync 30-110 VertRefresh 48-170 Option "DPMS" EndSection Section "Screen" Identifier "Screen1" Device "Ati1" Monitor "Sony1" DefaultDepth24 DefaultFbBPP32 SubSection "Display" Depth 24 Modes "1600x1200" EndSubSection EndSection Section "Screen" Identifier "Screen2" Device "Ati2" Monitor "Sony2" DefaultDepth24 DefaultFbBPP32 SubSection "Display" Depth 24 Modes "1600x1200" EndSubSection EndSection Section "ServerLayout" Identifier "Desktop" Screen "Screen1" RightOf "Screen2" Screen "Screen2" 0 0 InputDevice "Generic Keyboard" InputDevice "Configured Mouse" Option "Xinerama" EndSection Section "DRI" Mode0666 EndSection -- Claudio Martella Centro Informatico di Ateneo - CCR Politecnico di Milano ... Powered By Debian/GNU Linux ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Nvidia 2GO Suspend problem
On Tue, 23 Apr 2002, Aron Vrtala, Vienna Univ. Computer Center wrote: > > Actually, in the case of GeForce2 Go there is more to it than this. > > The video bios does not have APM support. It's ACPI only and this > > is not something well supported in Linux kernel. > > In principle you are right. In standard RedHat 7.2 Kernel there is no ACPI > support and the DELL C810 Notebook won't suspend (with or without > graphics). > > This is why I checked out for a more new kernel (2.4.16) and had ACPI > activated in it. Now it can't be a problem of the Linux Kernel ! The > notebook will suspend when closed or when apm -s is entered, but _only_ if > X isn't started. When X has been activated once - the notebook won't shut > down (stating resource unavailable). But there is more to it: After > stopping X (NVdriver stays in memory) the notebook will continue to refuse > suspend! > NVdriver does not support power management. Support was never written because of lack of ACPI. I am doubtful that any 2.4 kernel has usable ACPI support. It was my impression that that it would only possibly be fixed in the 2.6 timeframe. Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]give option interactively to the shadowfb ( rotation )
On Tue, 23 Apr 2002, Robert Wörle wrote: > Hi > > how can i give the shadowfb interactively an option , so that it would > rotate the screen live without the need to restart the X-server > i know how to rotate , but i dont know how to do that in realtime ( on a > press of a butten --- doing a command ) > You can't. Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Why no RGBA visual in XFree 4.1 software Mesa?
On Mon, 22 Apr 2002, Geoffrey Broadwell wrote: > I'm trying to get Perl's OpenGL support working on my systems, which do > not currently have hardware acceleration support under Mesa. However, > Perl's OpenGL support requires an RGBA visual, but for some reason the > visuals available under software Mesa (the one builtin to XFree 4.1) are > all RGB-only for me. > > I've hit the same problem on both a laptop and a desktop, both installed > recently with Debian Woody, and both running the 4.1.0-14 xfree packages. > The XF86Config-4 files were both built using the debconf magic in the > xfree packages. Both are running at 1024x768, 24-bit color, with 4MB RAM. > The systems both have lots of system memory available, 128MB on one, and > 256MB on the other. Attached are the output of xdpyinfo and glxinfo, and > the contents of the XF86Config-4 and XFree86.0.log files. > > Anyone have any clue what's going on? As far as I can interpret the tea > leaves, it looks like I'm really running with 32-bit pixels, so I don't > see a problem there . . . . > I see only xdpyinfo and glxinfo attached. There's nothing in those to specify whether or not you are in 24bpp or 32bpp. Why do you think you are in 32bpp? Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]XF 4.2 (cvs april 7) Nvidia GeForce2 Go (bug) - FlatpanelDell Inspiron
On Tue, 23 Apr 2002, rob wrote: > First of all I'd like to report a possible bug I'm not sure where the > appropriate place to do that is. > > I'm using xfree built from april 7 cvs under NetBSD 1.5. The video > chipset is the Nvidia GeForce2 Go - distributed with Dell mobile > Inspiron 8000's. > > > bug #1 (bug?) > When x is required to draw a lot of high contrast edges there are > noticable horizontal white lines that flicker on the left side of > the root window. > > It's reproducable with an all black root window and a lot of > white backgrounded xterm's. (opening and running xmms in addition > to or something that has a timer continually updating helps to reproduce > the undesired effect. I can't reproduce this. What modeline are you using? Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]push the freak'n button for X
Has anyone ever heard of such a thing? Matt Paulson Zeborg Inc. 781-759-0162 781-704-7017 (mobile) 500 W Cummings Park, Suite 4900, Woburn MA 01801-6503 www.zeborg.com This message is a personal and confidential communication. If you are not the intended recipient, please do not read, copy, or use it, and do not disclose it to others. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. Thank you. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]a problem about Xfree86 4.2.0
Yeah!!! It works. Thank you very much. I have another question about Xfree86. This is also the reason why I try Xfree86 4.2. I have two graphic cards in my box, one is ATI Rage XL(PCI) and one is ATI Radeon VE QY(AGP). I would like to control the AGP card from a kernel module we have written (which displays on a projector) and I would like to let X control the PCI card (which displays on a flat panel monitor). While in console mode the kernel module correctly displays images using the AGP card. We used the vesafb driver to configure the AGP card (primary card according to BIOS) to the desired mode of 1024x768. The problem begins when we use startx. The PCI controlled monitor starts X correctly but our kernel module no longer has control of our AGP card (no image displays on projector). We received the reply from Michael Danzer who suggested us that "Look at xc/programs/Xserver/hw/xfree86/common/xf86Bus.c, it might be enough to hardcode doFramebufferMode to TRUE." In 4.2.0 "doFramebufferMode" has been set to TRUE. However, when I run my program in X, still no image displays on projector(AGP card). But an interesting thing is that the color is changed in X Window. In our program we change the color palette, but this is supposed to work on AGP(primary card) not PCI. It seems that PCI card has been set to the primary card by X. How can I prevent X from disabling the AGP card? Thanks a bunch! jing __ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]ATI Rage 128 PR
Hi, I have upgraded to the latest XFree86 server. I ran XFree86 -configure, which ran fine and produced a reasonable looking XF86Config. When I try to start the X server, it aborts with an error. Here are the relevant messages: (WW) R128(0): Mode 0x0 is out of range. Valid mode should be between 640x480-0x0 (EE) R128(0): No valid mode found for this DFP/LCD (EE) Screen(s) found, but none have a usable configuration. I have attached the complete log as well as my XF86Config and hope that a kind soul out there can give me a hint on what is going wrong. I suspect my XF86Config needs some tweaking. Thanks, Arno Section "ServerLayout" Identifier "XFree86 Configured" Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" EndSection Section "Files" RgbPath "/usr/local/X11R6/lib/X11/rgb" ModulePath "/usr/local/X11R6/lib/modules" FontPath "/usr/local/X11R6/lib/X11/fonts/misc/" FontPath "/usr/local/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/local/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/local/X11R6/lib/X11/fonts/CID/" FontPath "/usr/local/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/local/X11R6/lib/X11/fonts/100dpi/" EndSection Section "Module" Load "extmod" Load "glx" Load "dri" Load "dbe" Load "record" Load "xtrap" Load "speedo" Load "type1" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "PS/2" Option "Device" "/dev/mouse" EndSection Section "Monitor" #DisplaySize 300 230 # mm Identifier "Monitor0" VendorName "SNY" ModelName"PCVA-15XTAP2" Option "DPMS" EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz" ### [arg]: arg optional #Option "NoAccel" # [] #Option "SWcursor" # [] #Option "Dac6Bit" # [] #Option "Dac8Bit" # [] #Option "ForcePCIMode" # [] #Option "CCEPIOMode"# [] #Option "CCENoSecurity" # [] #Option "CCEusecTimeout"# #Option "AGPMode" # #Option "AGPSize" # #Option "RingSize" # #Option "BufferSize"# #Option "Display" # #Option "PanelWidth"# #Option "PanelHeight" # #Option "ProgramFPRegs" # [] #Option "UseFBDev" # [] #Option "VideoKey" # #Option "ShowCache" # [] Identifier "Card0" Driver "ati" VendorName "ATI" BoardName "Rage 128 Pro PR" BusID "PCI:1:0:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor"Monitor0" SubSection "Display" Depth 1 EndSubSection SubSection "Display" Depth 4 EndSubSection SubSection "Display" Depth 8 EndSubSection SubSection "Display" Depth 15 EndSubSection SubSection "Display" Depth 16 EndSubSection SubSection "Display" Depth 24 EndSubSection EndSection XFree86 Version 4.2.0 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 18 January 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.2.20 i686 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Tue Apr 23 10:17:50 2002 (++) Using config file: "/root/XF86Config.new" (==) ServerLayout "XFree86 Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (==) Keyboard: CustomKeycode disabled (**) FontPath set to "/usr/local/X11R6/lib/X11/fonts/misc/,/usr/local/X11R6/lib/X11/fonts/Speedo/,/usr/local/X1
[Xpert]kernel module version incorrect
Mark LaPierre wrote: >I downloaded and compiled the DRM drivers from xfee86.org as suggested by two > very helpful people. I copied the r128.o file to > /lib/modules/2.4.9-31/kernel/drivers/char/drm/r128.o and restarted X. I > checked the permissions so don't tell me to fix that. ... > It would appear that the version on xfree86.org is not any newer than what I > already had. Perhaps I copied it to the wrong location? This should be the right location for your new r128.o file. Did you do depmod -a after copying? Any messages coming out of that? Another suggestion: Perhaps the Redhat kernel 2.4.9-31 is too "old" or badly configured. I'm not running a Redhat kernel any longer on RH 7.1, so I don't know the default settings for 2.4.9-31. I'm using a pristine kernel 2.4.18 and have compiled it with the following settings for drm (you'd surely have to enable other or all kinds of chipsets, mine is a VIA): [snip] CONFIG_AGP=m # CONFIG_AGP_INTEL is not set # CONFIG_AGP_I810 is not set CONFIG_AGP_VIA=y # CONFIG_AGP_AMD is not set # CONFIG_AGP_SIS is not set # CONFIG_AGP_ALI is not set # CONFIG_AGP_SWORKS is not set CONFIG_DRM=y # CONFIG_DRM_OLD is not set # # DRM 4.1 drivers # CONFIG_DRM_NEW=y CONFIG_DRM=y # CONFIG_DRM_TDFX is not set # CONFIG_DRM_GAMMA is not set CONFIG_DRM_R128=m # CONFIG_DRM_RADEON is not set # CONFIG_DRM_I810 is not set # CONFIG_DRM_I830 is not set # CONFIG_DRM_MGA is not set # CONFIG_MWAVE is not set [snip] The crucial point is to disable support for the "old" DRM drivers. Now XFree86 4.2.0 is nicely running with direct rendering enabled. Klaus ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]a problem about Xfree86 4.2.0
On Tue, 23 Apr 2002, Jing Xu wrote: > I updated my X Server from 4.1 to 4.2.0 (built from > source code). The same XF86Config-4 file works in 4.1 > but not in 4.2. The problem is when I execute > 'startx', the screen says, > OUT OF RANGE > H: 99.2 KHZ > V: 123.6 HZ > My graphic card is ATI Rage XL(PCI) and the following > is XF86config-4 file. [...] > Section "Device" > Identifier "ATI Rage XL" > Driver "ati" > BoardName "Unknown" > Option "nodri" > EndSection Add 'Option "NoCompositeSync"' to this section. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 Core Team member. ATI driver and X server internals. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]a problem about Xfree86 4.2.0
Hi, I updated my X Server from 4.1 to 4.2.0 (built from source code). The same XF86Config-4 file works in 4.1 but not in 4.2. The problem is when I execute 'startx', the screen says, OUT OF RANGE H: 99.2 KHZ V: 123.6 HZ My graphic card is ATI Rage XL(PCI) and the following is XF86config-4 file. -- # XFree86 4.0 configuration generated by Xconfigurator Section "ServerLayout" Identifier "XFree86 Configured" Screen "Screen0" InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" EndSection # By default, Red Hat Linux 6.0 and later use xfs Section "Files" FontPath "unix/:7100" EndSection # Module loading section Section "Module" Load "dbe" # Double-buffering Load "GLcore" # OpenGL support Load "dri" # Direct rendering infrastructure Load "glx" # OpenGL X protocol interface Load "extmod" # Misc. required extensions Load "v4l" # Video4Linux # Load "pex5" # PHIGS for X 3D environment (obsolete) # Load "record"# X event recorder # Load "xie" # X Image Extension (obsolete) # You only need the following two modules if you do not use xfs. # Load "freetype" # TrueType font handler # Load "type1" # Adobe Type 1 font handler EndSection Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Device" "/dev/mouse" Option "Protocol" "IMPS/2" Option "Emulate3Buttons" "off" Option "ZASection "Monitor" Identifier "NEC LCD1530V" VendorName "Unknown" ModelName "Unknown" HorizSync 31 - 60 VertRefresh 56 - 75 Option "dpms" EndSection Section "Device" Identifier "ATI Rage XL" Driver "ati" BoardName "Unknown" Option "nodri" EndSection Section "Screen" Identifier "Screen0" Device "ATI Rage XL" Monitor "NEC LCD1530V" DefaultDepth 8 Subsection "Display" Depth 8 Modes "1024x768" EndSubSection EndSection Section "DRI" Mode 0666 EndSection - If I use driver "vesa" instead of "ati", and set BusID, then everything is fine. But I want to use "ati", can anyone help me? Thanks in advance, jing __ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]xf 4.2 (cvs april 7) Nvidia GeForce2 Go (bug) - Flatpanel Dell Inspiron
irst of all I'd like to report a possible bug I'm not sure where the appropriate place to do that is. I'm using xfree built from april 7 cvs under NetBSD 1.5. The video chipset is the Nvidia GeForce2 Go - distributed with Dell mobile Inspiron 8000's. bug #1 (bug?) When x is required to draw a lot of high contrast edges there are noticable horizontal white lines that flicker on the left side of the root window. It's reproducable with an all black root window and a lot of white backgrounded xterm's. (opening and running xmms in addition to or something that has a timer continually updating helps to reproduce the undesired effect. bug #2 (possibly the fault of x) If a ps/2 mouse is plugged into the notebook while x is running all mouse devices become unusable. It's only remedied by exiting x and restarting it. It's reproducable by starting x and plugging in a ps/2 mouse. I'm not entirely sure if this is the fault of the operating system or x. update #1 I reported a problem where if the screen was blanked by x while the notebook was running on dc power the screen was being improperly re-drawn when it was un-blanked. Someone had replied to this and said they were getting ahold of a similar unit to try and reproduce can anyone comment on whether or not it's been fixed? Anyway thats the end, Thanks Rob ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]KDrive XChips server ignoring /dev/ts
Hi all; Im trying to get TinyX running on a fujitsu pt510 touchpanel ( running Linux ) I've written a kernel module to provide /dev/ts ( in the format documented on handhelds.org which I believe TinyX reads ). This appears to work fine. I built an XChips kdrive server with the following host.def ; #define ThreadedX NO #define BuildDocs NO #define BuildServersOnlyYES #define KDriveXServer YES #define TouchScreen YES #define TinyXServer YES #define XchipsServerYES #define KdriveServerExtraDefines -DMAXSCREENS=1 #undef BuildRandR #define BuildRandR YES #define BuildLBXNO #define BuildXInputLib YES #define ProjectRoot /usr/X11R6 #define BuildScreenSaverExt YES #define BuildScreenSaverLibrary YES #define SharedLibXssYES The built Xchips server appears to runs ok. However, both strace and fuser seem to point to it making no effort to open /dev/ts , though both the source code and experiences with TinyX on the ipaq say that it should. Am I missing a 'hidden' switch or something ? I using the 4.2 source BTW. Many thanks; -- Matthew Allum ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Nvidia 2GO Suspend problem
ACPI support in Linux is still early days: it could easily be that as well; just because there are bits in your kernel for it does not mean they work properly. Keith will be posting a patch: please install it and test to see if it changes the behavior. - Jim > In principle you are right. In standard RedHat 7.2 Kernel there is no ACPI > support and the DELL C810 Notebook won't suspend (with or without > graphics). > > This is why I checked out for a more new kernel (2.4.16) and had ACPI > activated in it. Now it can't be a problem of the Linux Kernel ! The > notebook will suspend when closed or when apm -s is entered, but _only_ if > X isn't started. When X has been activated once - the notebook won't shut > down (stating resource unavailable). But there is more to it: After > stopping X (NVdriver stays in memory) the notebook will continue to refuse > suspend! > > -- Jim Gettys Cambridge Research Laboratory Compaq Computer Corporation [EMAIL PROTECTED] ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Strange kernel messages from DRM
Hi! I'm getting two annoying messages when running X on my on FreeBSD 4.5-STABLE (built on 16 March 2002). XFree86 version 4.2.0 from ports. I have Rage 128 card with 32M on-board, using DRI: (WW) fcntl(7, F_SETOWN): Inappropriate ioctl for device I'm also getting the following messages from kernel (must be drm-kmod built from the ports, version 0.9.5): error: [drm:r128_freelist_get] *ERROR* returning NULL! I'm also experiencing slight lock-ups during performing of various GL-things (like glxgears, for instance), which is rather strange. Can anyone give my some advice for these? Thanks! ./danfe PS. I've attached my XF86Config and /var/log/XFree86.0.log. XFree86 Version 4.2.0 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 18 January 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: FreeBSD 4.5 i386 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Mon Apr 22 10:39:53 2002 (==) Using config file: "/usr/X11R6/lib/X11/XF86Config" (==) ServerLayout "XFree86 Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc104" (**) XKB: model: "pc104" (**) Option "XkbLayout" "ru" (**) XKB: layout: "ru" (**) Option "XkbOptions" "grp:caps_toggle,grp_led:caps" (**) XKB: options: "grp:caps_toggle,grp_led:caps" (==) Keyboard: CustomKeycode disabled (**) FontPath set to "/usr/X11R6/lib/X11/fonts/local/cyr-rfx/koi8-1/misc/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/local/cyr-rfx/koi8-1/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/local/ms/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/local/cyr-rfx/koi8-1/75dpi/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (**) ModulePath set to "/usr/X11R6/lib/modules" (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.5 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (II) Loader running on freebsd (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.2.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The XFree86 Project" compiled for 4.2.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,1130 card 8086,1130 rev 04 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,1131 card , rev 04 class 06,04,00 hdr 01 (II) PCI: 00:1e:0: chip 8086,244e card , rev 11 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,2440 card , rev 11 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,244b card , rev 11 class 01,01,80 hdr 00 (II) PCI: 00:1f:5: chip 8086,2445 card 8384,7600 rev 11 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 1002,5446 card 1002,0018 rev 00 class 03,00,00 hdr 00 (II) PCI: 02:02:0: chip 8086,1229 card 8086,0009 rev 05 class 02,00,00 hdr 00 (II) PCI: 02:04:0: chip 1274,1371 card 1274,1371 rev 08 class 04,01,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: "scanpci" (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor="The XFree86 Project" compiled for 4.2.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) UnloadModule: "scanpci" (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) PCI-to-PCI bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0c (VGA
Re: [Xpert]Window ID
On Mon, 22 Apr 2002, Vladimir Dergachev wrote: > On Mon, 22 Apr 2002, Bharathi S wrote: > > On Mon, 22 Apr 2002, Vladimir Dergachev wrote: > > > > How find the window id by using the following structures > > > > Display, Drawable, Graphics Context ? > > > > > > AFAIK, Window id is the same thing as the drawable, provided the drawable > > > points to the window. I.e. where the man page says Xblahblah function > > > takes a drawable as an argument it means that you can either pass a window > > > id or a pixmap (but not XImage) handle to it. > > > > Most of the functions taking Pixmap(DRAWABLE) as argument. > > I need the window id for maintaining a virtual buffer > > and window id as the key. > > You lost me at this point. Could you provide more detail about what is it > you are trying to do ? Is it in the user application or in Xserver code ? Thanks to all for the reply. All our modification is only in XLIB. If it is not possible at Xlib level, we may move to XServer. If we did this modification in the XLib, the application running on top xlib will automatically inherit this facility. KeyBoard | \|/ keycode | \|/ keysym(ASCII) | \|/ ISCII -> File | | \|/ Display XDrawString() / XDrawImageString() Inside this functions I am doing the Encoding to Glyph code conversion The Resulting Glyph is sent for display. ( No of resulting glyph code may not equal to the No of Encoding code ) :( | | \|/ XDrawLine() to move the Cursor Application calculating the cursor position or width based on the Encoding code. It should calculate the new position based on the resulting glyph. So when ever application try to move the cursor position we have to calculate the new position by converting the encoding to glyph. But for XDrawLine, App won't send the strings So I planned to store the encoding codes coming to the XDrawString / XDrawImageString in a List of VirtualWindowBuffer ( Window ID as Key ) VirtualWindowBuffer --> 2 Dimension Array and one KeyID Inside the XDrawLine i will find the VirtualWindowBuffer and I will take the Whole line VirtualWindowBuffer(x, y) and i am calculating the new position. i tried Pixmap value as ID. But pixmap is keep on changing. :( Sorry for my bad english. :( Thank you, Bharathi S -- --==| Bharathi S | BSB-364 DONLab | IIT-Madras |==-- Even a single evil word Will turn all good results to bad. *In Tirukkural of Holy Tamil poet Tiruvalluvar. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]XFree 4.2.0 Problem with Cut And Paste / German Umlauts
On Tue, Apr 23, 2002 at 12:36:03PM +0200, Marc-Christian Petersen wrote: > Hi there, hi > i've upgraded to xfree 4.2.0 yesterdays evening and have some problems, or, > no, only one problem. I cannot Cut and Paste between any application :-((( > Attached is my XF86Config-4. Dunno, could it be the 3rd button isn't configured properly? > In some apps i don't have german umlauts, but not in all. With XFree 4.1 it > works great. Try "nodeadkeys" variant, I also have lots of troubles without it :-) Bye, Peter Surda (Shurdeek) <[EMAIL PROTECTED]>, ICQ 10236103, +436505122023 -- three saints: looser & lamer & hacker msg05703/pgp0.pgp Description: PGP signature
[Xpert]XFree 4.2.0 Problem with Cut And Paste / German Umlauts
Hi there, i've upgraded to xfree 4.2.0 yesterdays evening and have some problems, or, no, only one problem. I cannot Cut and Paste between any application :-((( Attached is my XF86Config-4. In some apps i don't have german umlauts, but not in all. With XFree 4.1 it works great. Kernel: 2.4.18-wolk3.4 System: Debian SID GFX:ATI All-In-Wonder (Rage 128) -- Kind regards Marc-Christian Petersen http://sourceforge.net/projects/wolk PGP/GnuPG Key: 1024D/569DE2E3DB441A16 Fingerprint: 3469 0CF8 CA7E 0042 7824 080A 569D E2E3 DB44 1A16 Key available at wwwkeys.pgp.net. Encrypted e-mail preferred. # XF86Config-4 (XFree86 server configuration file) generated by Dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config manual page. # (Type "man XF86Config" at the shell prompt.) Section "Files #FontPath "unix/:7100" FontPath "/usr/X11R6/lib/X11/fonts/local/" FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" EndSection Section "ServerFlags" Option "AllowMouseOpenFail""true" Option "standby time" "20" Option "suspend time" "30" Option "off time" "60" EndSection Section "Module" Load"ddc" Load"GLcore" Load"dbe" Load"dri" Load"extmod" Load"glx" Load"pex5" Load"record" Load"xie" Load"bitmap" Load"freetype" Load"speedo" Load"type1" Load"vbe" Load"int10" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc105" Option "XkbLayout" "de" Option "AutoRepeat""250 30" EndSection #Section "InputDevice" Identifier "Configured Mouse" # Driver "mouse" # Option "CorePointer" # Option "Device""/dev/psaux" # Option "Protocol" "ImPS/2" ## Option "Emulate3Buttons" "true" # Option "ZAxisMapping" "4 5" # Option "Buttons" "3" #EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Protocol" "MouseSystems" Option "Device""/dev/gpmdata" Option "ZAxisMapping" "4 5" Option "Buttons" "5" Option "Resolution""100" EndSection Section "InputDevice" Identifier "Generic Mouse" Driver "mouse" Option "SendCoreEvents""true" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" Option "ZAxisMapping" "4 5" EndSection #Section "Device" #Identifier "ATI All In Wonder 128" #Driver "fbdev" #Option "UseFBDev" "true" #VideoRam32768 #EndSection Section "Device" Identifier "ATI All In Wonder 128" Driver "ati" VideoRam32768 Option "AGPMode" "4" Option "UseCCEFor2D" "false" EndSection Section "Monitor" Identifier "NEC MultiSync FP1370" HorizSync 31-130 VertRefresh 55-160 Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "ATI All In Wonder 128" Monitor "NEC MultiSync FP1370" DefaultDepth16 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
[Xpert]xpr/xpr2
I noticed on the cvs list that the xwd manpage was changed to reflect the non-existance of xpr. Is there any reason/general consensus as to why this tool was dropped ? There may be better tools for its purpose today, but that is probably true for xwd as well... Martin -- Dr. Martin Kroeker, daveg GmbH Darmstadt CAD/CAM/CAQ [EMAIL PROTECTED] Precision Powered by Penguins ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Rage 128 Mobility and DRI
On 22 Apr 2002, Doug Alcorn wrote: > Vladimir Dergachev <[EMAIL PROTECTED]> writes: > > > Most likely you do not have enough video ram for this. One suggestion is > > to switch to 16bpp. > > I've gotten several comments of this nature. I have 8MB of video > ram. According to the DRI calculator, I should be able to do > 1400x1050 in 16bpp. That is not the case. I can only do 1280x1024 in > 16bpp. I can't do DRI in 24bpp and 1280x1024. Of course, my LCD does > 1400x1050. Running 1280x1024 on it looks cruddy. Hmm.. What does /var/log/XFree86.0.log say ? Vladimir Dergachev > > > On 21 Apr 2002, Doug Alcorn wrote: > > > > > I thought I would post this mainly to populate google. I can't > > > remember where I saw the user comment with the solution. Probably on > > > the dri.sourceforge.net site. Anyway, my Rage 128 Mobility LF won't > > > do DRI at resolutions higher than 1280x1024. I don't know if this is > > > a limited by the chipset or the dri drives. Wouldn't hurt if this was > > > documented in a manpage or something. > > -- > (__) Doug Alcorn - Unix/Linux/Web Developing > oo / PGP 02B3 1E26 BCF2 9AAF 93F1 61D7 450C B264 3E63 D543 > |_/ mailto:[EMAIL PROTECTED] http://www.lathi.net > ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Nvidia 2GO Suspend problem
On Mon, 22 Apr 2002, Jim Gettys and Mark Vojkovich wrote: > There are bugs in suspend in general with Linux (having nothing to do with > X per' se'). Keith Packard has sent Linus a patch; not a great one, > (loop after a pause for a long time), but one that works. > > Basically, if the system is busy at the instant that the > suspend request is made, it fails. This can happen if the disk or > other device is busy at that instant, which can happen as the X server > writes its log that it is suspending (or other logging activity). I know this kind of nasty behavior. It occurs in rare occasions on a DELL Latitude CP233XT Notebook, which in general will suspend without any problems. However, it would be really nice to have a patch for these rare occations too! (According to Murphy, they will always occur, when they are absolutely not needed :-) ). > This will depend on exactly the hardware/software combination, and may > or may not be repeatable (until you change something!). This behavior is completely different. It will _allways_ occur. It is not possible to suspend the notebook at all (except when running it under Windows2k alternatively - (pain) - I do mention this, 'cause it can't be a hardware problem on the notebook). Now turning to Marc's statement: > Actually, in the case of GeForce2 Go there is more to it than this. > The video bios does not have APM support. It's ACPI only and this > is not something well supported in Linux kernel. In principle you are right. In standard RedHat 7.2 Kernel there is no ACPI support and the DELL C810 Notebook won't suspend (with or without graphics). This is why I checked out for a more new kernel (2.4.16) and had ACPI activated in it. Now it can't be a problem of the Linux Kernel ! The notebook will suspend when closed or when apm -s is entered, but _only_ if X isn't started. When X has been activated once - the notebook won't shut down (stating resource unavailable). But there is more to it: After stopping X (NVdriver stays in memory) the notebook will continue to refuse suspend! Thanx for any help, Aron -- === Aron Vrtala| Internet eMail: Zentraler Informatikdienst der | [EMAIL PROTECTED] Universitaet Wien | [EMAIL PROTECTED] | -- Abteilung Dezentrale Systeme| eMail Hotline-Service: Aussenstelle Physik | [EMAIL PROTECTED] | -- Boltzmanngasse 5, A-1090 Vienna| Tel: +43-1-4277 /14102,Hotline: /14100 Austria, Europe| Fax: +43-1-4277 /9141 === - -->--> This message was sent using only 100 % recycled electrons & photons. <--<-- -BEGIN PGP PUBLIC KEY BLOCK- Version: 2.6.3i mQCNAzXF2vcAAAEEALtcyrg4NOfLdcQTKMP3rUa67lb3Sp25gn9fNMQ68Iyc7roX Y0dhcQXbWxGDvId1CQJGzB1JdYFPXGcmSh2Qj2B3DL6Mm6dLwNJLI2pHJzsSAdxj wEDhr869Jb3bdntETNFXs4Wh+G/QrZZi4R1MJxrtQP6DNaC6PhIZWDFPoJ1xAAUR tAtBcm9uLlZydGFsYYkAlQMFEDXF2vcSGVgxT6CdcQEBeq4EAKD5h5d3VZYAqCE9 VyNsqv9ZlUeIt1srehyrRSi2uojT53F5TDXrsNNgTrakoE+XLsF1QRoqgTnbZOE8 hmRKUwGq2HPEHzUQpFm8K0vzAQcrKXKf9IqfXqmD8I5aGJMeYMZtEFWYdZJ4VGA8 SB/IqlUqZFaMK23fGzF2r9SkP8Wb =foVl -END PGP PUBLIC KEY BLOCK- ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
