Re: Server doesn't build for me (setjmp)
On Sat, 1 Mar 2003, Mark Vojkovich wrote: > setjmp is a *macro* (for __sigsetjmp) defined in /usr/include/setjmp.h. > This is libc 2.2. so it doesn't set HAS_GLIBC_SIGSETJMP. > SYMCFUNCALIAS chokes on this. This is gcc 2.95.3. >I think the HAS_GLIBC_SIGSETJMP set logic is wrong. You've got glibc 2.2.1, I'll guess. The #if's should be looking for glibc < 2.2.2, not 2.2, although a host.def override is available (see xfree86.cf). Anyway, I'm chasing a related, though a little thornier, problem on my libc5 system, so I'll fix this too. 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. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Server doesn't build for me (setjmp)
setjmp is a *macro* (for __sigsetjmp) defined in /usr/include/setjmp.h. This is libc 2.2. so it doesn't set HAS_GLIBC_SIGSETJMP. SYMCFUNCALIAS chokes on this. This is gcc 2.95.3. I think the HAS_GLIBC_SIGSETJMP set logic is wrong. Mark. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: KeyBoard BUG on sparc/sparc64 in 4.3.0 too.
From: Balint Cristian <[EMAIL PROTECTED]> Date: Sat, 1 Mar 2003 17:11:34 +0200 Unable to handle kernel paging request \|/ \|/ "@'/ .. \`@" /_| \__/ |_\ \__U_/ setserial(104): Oops The program "setserial" is causing the OOPS, not anything to do with xfree86. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: NVidia driver (open source) on Apple Powerbook G4 12"
On Sun, 2 Mar 2003, Christoph Pittracher wrote:
> On Saturday 01 March 2003 03:18, Mark Vojkovich wrote:
> >Can you VT switch back to the X-server OK, and startx again after
> > quitting?
>
> Yes, I can.
>
> > If so, it's probably just a matter of not enough stuff
> > being saved and restored in the UnLoad/LoadStateExt functions in
> > riva_hw.c.
>
> Hmm, how can I test that? Is there a list of all registers that
> exists/should be saved?
If I knew of more that should be saved, it would be saving
them already.
>
> >If you wanted to collect some data you could try reading
> > chip->PMC[0x0004/4] at the top of nv10GetConfig() just to
> > see what state that was in before the X-server touched it.
>
> What should I do with the data found at chip->PMC[0x0004/4]? I
> didn't take a closer look at the source code, is chip->PMC a struct
> including all registers or how do I know which byte is which register?
chip->PMC[0x0004/4] is a 32 word. You can just print it out.
ErrorF("chip->PMC[0x0004/4] = 0x%x\n", chip->PMC[0x0004/4]);
will send it to the /var/log/XFree86.0.log.
That's just a shot in the dark. There's probably nothing wrong there
since it starts succesfully the second time.
I'll ask some people about what's different between the
Apple and PC mobile configurations.
Mark.
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
Re: NVidia driver (open source) on Apple Powerbook G4 12"
On Saturday 01 March 2003 03:18, Mark Vojkovich wrote: >Can you VT switch back to the X-server OK, and startx again after > quitting? Yes, I can. > If so, it's probably just a matter of not enough stuff > being saved and restored in the UnLoad/LoadStateExt functions in > riva_hw.c. Hmm, how can I test that? Is there a list of all registers that exists/should be saved? >If you wanted to collect some data you could try reading > chip->PMC[0x0004/4] at the top of nv10GetConfig() just to > see what state that was in before the X-server touched it. What should I do with the data found at chip->PMC[0x0004/4]? I didn't take a closer look at the source code, is chip->PMC a struct including all registers or how do I know which byte is which register? >Have you tried it in different depths? Yes, same problem independent on the color depth. best regards, Christoph ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
radeon_vtxfmt.c assert error
Dear lists, Does any of the DRI developers remember explicitly fixing the: "radeon_vtxfmt.c:1057: radeonVtxfmtUnbindContext: Assertion vb.context == ctx' failed." error that is so often seen running the glthreads mesademo? I seem to remember Keith Whitwell (I *think*) saying that this was on his todo list. Whatever the case may be, I can reproduce this easily on XFree86 4.3.0 but NOT on DRI CVS. I also remember that this bug was still present in DRI CVS a month or two ago, so I'm trying to find out what/who fixed it. If anyone has more information on this, I would be most grateful. Thanks, Charl -- charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/ ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Multiple video consoles
On Sat, 1 Mar 2003, Sven Luther wrote: > That said, another thing that would be nice, would be the possibility to > specify one display section for every depth, instead of just copying it > for each supported depth. Do many people in these times of 64+Mo of > onboard memory specify different resolutions for different depths ? I don't know if it makes sense from a code point of view, but from the config file side, I'd suggest allowing a "Display" subsection to have multiple "Depth" qualifiers (possiby FbBpp and Visual too). -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Stepping outside the box with XAA drivers?
On 1 Mar 2003, Juliusz Chroboczek wrote: > MV> but XAA is an all or nothing thing. > > Could you please explain that? Do you mean that if you use XAA, you > can no longer wrap at the GCOps level? > You can wrap them, but if you are above XAA you MUST call down. XAA expects to see every rendering request in order to keep its SW/HW synchronization accounting straight. So you can't, for instance, build another HW-touching rendering layer on top of XAA. Mark. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Mouse Daemon for Linux/FreeBSD?
On Friday 28 February 2003 20.38, Alex Deucher wrote: > I believe Zephaniah E. Hull was doing some work for getting xfree86 to > work dynamically with the 2.5 input layer. I think it was called > evdev. I can't seem to find the link to his site at the moment though. http://people.debian.org/~warp/evdev/ > > Alex > /Mikael Andersson ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
XFree86-4.3.0 problem installing/mesa/etc
During make install: make[4]: Leaving directory `/home/war/4.3.0/source/xc/lib/GL/GL' installing in lib/GL/mesa/src/OSmesa... make[4]: Entering directory `/home/war/4.3.0/source/xc/lib/GL/mesa/src/OSmesa' gcc-c -o ../../../../../lib/GL/mesa/src/X86/common_x86_asm.o ../../../../../lib/GL/mesa/src/X86/common_x86_asm.S In file included from ../../../../../lib/GL/mesa/src/X86/common_x86_asm.S:43: ../../../../../lib/GL/mesa/src/X86/matypes.h:9:22: assyntax.h: No such file or directory ../../../../../lib/GL/mesa/src/X86/common_x86_asm.S:44:33: common_x86_features.h: No such file or directory make[4]: *** [../../../../../lib/GL/mesa/src/X86/common_x86_asm.o] Error 1 make[4]: Leaving directory `/home/war/4.3.0/source/xc/lib/GL/mesa/src/OSmesa' make[3]: *** [install] Error 2 make[3]: Leaving directory `/home/war/4.3.0/source/xc/lib/GL' make[2]: *** [install] Error 2 make[2]: Leaving directory `/home/war/4.3.0/source/xc/lib' make[1]: *** [install] Error 2 make[1]: Leaving directory `/home/war/4.3.0/source/xc' make: *** [install] Error 2 Command exited with non-zero status 2 3.86user 3.39system 0:16.03elapsed 45%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (139095major+62001minor)pagefaults 0swaps [EMAIL PROTECTED] xc]$ Also has problems throughout the install with Mesa. http://phrozen.res.cmu.edu/~war/world.log.bz2 Any ideas why it is having problems with Mesa? ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Multiple video consoles. What happened to multi-user?
The discussion thread has focused on multi-head for a single user. What about plans for multi-user? Matrox and Nvidia have four port cards. Why couldn’t a single system (maybe multi-processor) support eight simultaneous users if it had two of those cards and USB input devices? What would be the preferred method of directing developments towards this goal?
KeyBoard BUG on sparc/sparc64 in 4.3.0 too.
Regard to that one BUG with the mention that it persist in 4.3.0 too and any CVS too: By Rene: http://marc.theaimsgroup.com/?l=xfree86&m=104526841725691&w=2 By mysef: http://marc.theaimsgroup.com/?l=xfree86&m=104385693307371&w=2 I send more deBug: http://marc.theaimsgroup.com/?l=xfree86&m=104385720707941&w=2 and now my: xmodmap -pk There are 4 KeySyms per KeyCode; KeyCodes range from 8 to 132. KeyCode Keysym (Keysym) ... Value Value (Name) ... 8 0xff69 (Cancel) 0x (NoSymbol) 0xffc8 (F11) 9 0x1005ff77 (SunAudioLowerVolume)0x1005ff7b (SunVideoLowerBrightness) 10 0xff66 (Redo) 0x (NoSymbol) 0xffc9 (F12) 11 0x1005ff79 (SunAudioRaiseVolume)0x1005ff7c (SunVideoRaiseBrightness) 12 0xffbe (F1) 13 0xffbf (F2) 14 0xffc7 (F10) 15 0xffc0 (F3) 16 0xffc8 (F11)0x (NoSymbol) 0x1005ff10 (SunF36) 17 0xffc1 (F4) 18 0xffc9 (F12)0x (NoSymbol) 0x1005ff11 (SunF37) 19 0xffc2 (F5) 20 0xff7e (Mode_switch) 21 0xffc3 (F6) 22 23 0xffc4 (F7) 24 0xffc5 (F8) 25 0xffc6 (F9) 26 0xffe9 (Alt_L) 27 0xff52 (Up) 28 0xff13 (Pause) 0x (NoSymbol) 0xff6b (Break) 29 0xff61 (Print) 0x (NoSymbol) 0xff15 (Sys_Req) 0x1005ff60 (SunSys_Req) 30 0xff14 (Scroll_Lock) 31 0xff51 (Left) 32 0x1005ff70 (SunProps) 0x (NoSymbol) 0xffca (F13) 33 0xff65 (Undo) 0x (NoSymbol) 0xffcb (F14) 34 0xff54 (Down) 35 0xff53 (Right) 36 0xff1b (Escape) 37 0x0031 (1) 0x0021 (exclam) 38 0x0032 (2) 0x0040 (at) 39 0x0033 (3) 0x0023 (numbersign) 40 0x0034 (4) 0x0024 (dollar) 41 0x0035 (5) 0x0025 (percent) 42 0x0036 (6) 0x005e (asciicircum) 43 0x0037 (7) 0x0026 (ampersand) 44 0x0038 (8) 0x002a (asterisk) 45 0x0039 (9) 0x0028 (parenleft) 46 0x0030 (0) 0x0029 (parenright) 47 0x002d (minus) 0x005f (underscore) 48 0x003d (equal) 0x002b (plus) 49 0x0060 (grave) 0x007e (asciitilde) 0x00b4 (acute) 50 0xff08 (BackSpace) 0xfed5 (Terminate_Server) 51 0xff63 (Insert) 52 0x1005ff78 (SunAudioMute) 0x1005ff7a (SunVideoDegauss) 53 0xffaf (KP_Divide) 0x (NoSymbol) 0xffd6 (F25) 54 0xffaa (KP_Multiply)0x (NoSymbol) 0xffd7 (F26) 55 0x1005ff76 (SunPowerSwitch) 0x1005ff7d (SunPowerSwitchShift) 56 0x1005ff71 (SunFront) 0x (NoSymbol) 0xffcc (F15) 57 0xff9f (KP_Delete) 0xffae (KP_Decimal) 58 0x1005ff72 (SunCopy)0x (NoSymbol) 0xffcd (F16) 59 0xff50 (Home) 60 0xff09 (Tab)0xfe20 (ISO_Left_Tab) 61 0x0071 (q) 0x0051 (Q) 62 0x0077 (w) 0x0057 (W) 63 0x0065 (e) 0x0045 (E) 64 0x0072 (r) 0x0052 (R) 65 0x0074 (t) 0x0054 (T) 66 0x0079 (y) 0x0059 (Y) 67 0x0075 (u) 0x0055 (U) 68 0x0069 (i) 0x0049 (I) 69 0x006f (o) 0x004f (O) 70 0x0070 (p) 0x0050 (P) 71 0x005b (bracketleft)0x007b (braceleft) 72 0x005d (bracketright) 0x007d (braceright) 73 0x (Delete) 74 0xff20 (Multi_key) 75 0xff95 (KP_Home)0xffb7 (KP_7) 0xffd8 (F27) 76 0xff97 (KP_Up) 0xffb8 (KP_8) 0xffd9 (F28) 77 0xff9a (KP_Prior) 0xffb9 (KP_9) 0xffda (F29) 78 0xffad (KP_Subtract) 79 0x1005ff73 (SunOpen)0x (NoSymbol) 0xffce (F17) 80 0x1005ff74 (SunPaste) 0x (NoSymbol) 0xffcf (F18) 81 0xff57 (End) 82 83 0xffe3 (Control_L) 84 0x0061 (a) 0x0041 (A) 85 0x0073 (s) 0x0053 (S) 86 0x0064 (d) 0x0044 (D) 87 0x0066 (f) 0x0046 (F) 88 0x0067 (g) 0x0047 (G) 89 0x0068 (h) 0x0048 (H) 90 0x006a (j) 0x004a (J) 91 0x006b (k) 0x004b (K) 92 0x006c (l) 0x004c (L) 93 0x003b (semicolon) 0x003a (colon) 94 0x0027 (apostrophe) 0x0022 (quotedbl) 0x00b4 (acute) 95 0x005c (backslash) 0x007c (bar) 96 0xff0d (Return) 97 0xff8d (KP_Enter) 98 0xff96 (KP_Left)0xffb4 (KP_4) 0xffdb (F30) 99
Re: NVidia driver (open source) on Apple Powerbook G4 12"
On Sat, 2003-03-01 at 03:18, Mark Vojkovich wrote: >Hmmm. I've never tried it on a PowerBook. I guess I will have > to see if I can borrow one from around here to play with. Unfortunately, > that means it's unlikely to be fixed in 4.3 (I recall having a difficult > time with Linux PPC installation). Only very recent apple laptops have nVidia chips, and of course, those also need very recent kernels, typically not what is on installation CDs of distros, so indeed, installing can be tough. For older machines, there are a bunch of distros around that should pretty much work out of the box. (If you have access to a PPC machine you want to play with and want some indications about installing a distro, let me know by email). I had also a couple of reports of offb not beeing properly restored on switch from X on non-laptops. (Dan Burcaw from TerraSoft should have or will shortly send you a note about this). >Can you VT switch back to the X-server OK, and startx again after > quitting? If so, it's probably just a matter of not enough stuff > being saved and restored in the UnLoad/LoadStateExt functions in > riva_hw.c. Probably some of the CRTC registers, possibly something > specific to the PowerBook. I supposed it could also be an offb > issue. I don't think offb can do anything here. It's basically not touching the hardware at all, and since OF is long dead when linux has booted, it relies entirely on X restoring the full card state properly. offb "picks" whatever framebuffer base address configured by the firmware, and uses that assuming it is 8 bpp. It does have a couple of hacks to access the palette registers on some ATIs, but that's pretty much all it does. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Multiple video consoles
On Fri, Feb 28, 2003 at 04:19:37PM -0500, David Dawes wrote: > On Fri, Feb 28, 2003 at 09:04:06PM +0100, Sven Luther wrote: > >Are you speaking about the current 4.3.0 or the stuff you are working on ? > > What I was working on. BTW, is the stuff you were working on accessible on a CVS branch or something such ? Friendly, Sven Luther ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: xf86cfg: ERROR SIGSEGV caught!
SD> some fonts can't be displayed any more which worked with freetype1 SD> based freetype module Yes. The FreeType 1 library had been fine-tuned to include workarounds for a number of common font bugs (much against David Turner's preferences). These hacks are only now getting into FreeType 2. Now that 4.3 is out, I hope we'll be able to upgrade to 2.1.4; when that happens, I'll be very keen on bug reports describing such failures. Please do not send such bug reports now -- we do know that the version of FreeType included in 4.3 has some limitations. Juliusz ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Stepping outside the box with XAA drivers?
MV> but XAA is an all or nothing thing. Could you please explain that? Do you mean that if you use XAA, you can no longer wrap at the GCOps level? Juliusz ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Multiple video consoles
On Fri, Feb 28, 2003 at 04:19:37PM -0500, David Dawes wrote: > >Are you speaking about the current 4.3.0 or the stuff you are working on ? > > What I was working on. Ok, ... I take it, there will be a 4.4.0 before 5.0 ? > >Well, i am not sure i follow you completely here, but my interrest in > >scaling is : > > > > o having one monitor display the same framebuffer area as the other, > > but in another resolution. Like when your laptop's LCD screen can only > > display 1024x768 but you have to do a presentation on a 800x600 video > > projector. You sent the framebuffer to be 800x600 to have maximum > > quality on the video projector, and scale it to 1024x768 on the > > mirrored display of your LCD screen. > > > > o displaying lower video modes than what the LCD screen can display > > (or bigger modes also). > > The type of "scaling" that comes for free is when your LCD displays > 1024x768 and the video projector displays 800x600, but that 800x600 is > just a 800x600 pixel subset of the full 1024x768 desktop. Other forms That is not scaling, you juts open a plain second viewport on the same framebuffer. > of scaling are either handled by a hardware scaler (that may or may not > be visible to the XFree86 server and user), or by having something in > XFree86 that keeps a second copy of the image that is scaled in software. Mmm, you are speaking of a hardware scaller in the LCD monitor ? I am speaking about hardware scaller in the video chip, and altough not all video chips have those, i guess some have and more will have. Or else you could just re-use the video overlay unit for it or whatever. > A lot of chipsets that drive LCD displays do transparent scaling where > the user and XFree86 server see a "800x600" mode, and the graphic hardware > scales that to the 1024x768 physical LCD screen. Well, from my experience (i have a Sony SDM-X52, with both a DVI connector and a standard VGA connector) this doesn't seem to happen. If i request a mode lower than what the LCD can display, i get only garbage, at least on the DVI channel. I believe the VGA channel can do more advanced things, but didn't sucessfully use them. On the other hand, my graphic hardware can do arbitrary scaling of the framebuffer before passing it to the monitor, but i have to program it explicitly. I guess that this is used by the bios at startup to convert the 640x480 text mode to something my monitor supports, since the fonts appear a bit blurry. > >These would be static scalings, and could be set by specifying for the > >viewport, not only the x/y corner like it is done right now, but also > >the source height and width, the scaling would then be set to the ratio > >between the height/width of the destination over the source. > > > >Keep in mind LCD monitors can only do fixed resolution mostly and will > >become more and more predominant. > > Most of the current LCD monitors that I've seen can do built-in scaling > so that they can display non-native resolutions transparently to the user. Mmm, maybe my monitor can, but the documentation i have doesn't speak about it, and anyway, it has quite limited frequency ranges. Also, this precludes doing more advanced stuff like i say below, orupscaling instead of downscaling. BTW, do you know any doc on DVI and LCD monitors ? my monitor refuse to go to sleep when i am using the DVI channel, while it works fine with the VGA channel. > >Then there is dynamic viewports, similar to what matrox does for windows > >zooming on their windows drivers (i have not seen this personnally > >though). You could designate a window, and have it be used for the > >viewport of a second head. The second viewport would follow the window > >and scale it apropriatedly, including if the window is moved around or > >resized. > > I don't know how the Matrox driver works specifically, but if it allows > arbitrary scaling it may use hardware scaling for the second viewport > (like XVideo usually uses) to achieve this efficiently. I don't know > how it handles partially obscured or partialy off-screen windows. > > Tracking fully visible mode-line sized windows in a second viewport is > the easiest subset of this whole problem to implement. This is the part > that could easily be implemented in 4.x without a lot of work. Yes, altough if we could add a source w/h to the viewport option, we could do arbitrary hardware scalling too. static scaling only though. And if the hardware can do it, why limit ourself. That said, another thing that would be nice, would be the possibility to specify one display section for every depth, instead of just copying it for each supported depth. Do many people in these times of 64+Mo of onboard memory specify different resolutions for different depths ? > >And we would do dual head, not like now with splitting the framebuffer > >into two zones, one for each head, but by sharing the same framebuffer > >between both screens, this would give free dual head DRI also, if t
Re: Mouse Daemon for Linux/FreeBSD?
On Fri, 28 Feb 2003, Jeff Garzik wrote: > Note that CONFIG_INPUT (the "new input layer") exists in 2.4.x kernels > as well... so you can test right now. It's just that 2.5.x (and > 2.6.0 when released) has made the new input layer the default. I'm not really up to speed on the 2.4 stuff, never mind later versions, but my understanding is that some part of this new input stuff got back ported to the 2.2 kernel USB input support, so you may have some level of compatiblilty with older kernels too. I don't know whether that helps or hinders. One point that worries me about 2.2 kernels is that the USB input support doesn't do a good job of identifing particular devices with particular hardware, so if you want a dual seat setup it could be fun trying to ensure that the right keyboard, screen and mouse go together - what do I need to change if I introduce a USB hub ? Can I put the serial numbers of the mice into the X server config, and would I want to ? No doubt 2.6 has good answers to all these questions. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Monitor section in config file?
On Fri, 28 Feb 2003, Kendall Bennett wrote: > Andrew C Aitchison <[EMAIL PROTECTED]> wrote: > > X -configure comments these values out because many apps used to > > get confused by having precise dpi values and displayed silly > > fonts. I think that at one time a 85x90 dpi screen would make > > Netscape use 75x100dpi fonts. I note that Netscape 7 allows you to > > calibrate the horizontal screen pitch, but not the vertical pitch. > > So you are saying that should leave this section of the config file > commented out for better compatibility? When it went in poeple complained about the broken apps, but if we never give them the right information what would the app gain by being fixed ? > I have commented it out for now > anyway, as I haven't added the code in the installer to grab the values > from the EDID yet. I can just as easily leave it off (Red Hat 8.0 seems > ot get it directly from DDC when it is not in the config file anyway). We do all the DDC queries at run time as well as config time, with config values overriding probed values (the X server warns of conflicts), so leaving them out is OK. Ultimately whether you record DDC info in the config file depends whether you care more about what happens if a different monitor is plugged in or whether you want the same setup if you start X (and possibly the computer) before switching on the monitor ? Suppose I have a classroom full of identical machines, and at the end of the day some people switch the monitors off to save the screens. Overnight scripts detect an upgrade, kernel security patch say, install it and reboot. Now if the EDID info is not in the config, the machines whose monitors are turned off will have a different DPI from those that were left on. That might mean that web browsers come up with different sized fonts, which the user will be likely to notice. The DDC spec does allow a better solution - the video card must supply enough power for the monitor to return EDID info even when not powered, but I have yet to see a monitor which does that. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
