[XFree86] can't disable DPMS
In 4.3.99.15 and 4.3.99.16 disabling DPMS via: xset -dpms doesn't work. Applications like mplayer can't cope with it either. I've found this: http://www.mail-archive.com/[EMAIL PROTECTED]/msg10150.html but this is the time the bug has _appeared_ (not vanished), so please check the patch out once again. -- Tom Pala [EMAIL PROTECTED] http://vfmg.sourceforge.net/ http://www.pld-linux.org/Members/gotar/ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Two modifiers on one key
Hi! I want caps lock key do act as ISO_Level3_Shift and as Caps_Lock when pressed with Control key. I've tried this: partial modifier_keys xkb_symbols caps_switch { key CAPS { type[Group1]=PC_BREAK, symbols[Group1] = [ ISO_Level3_Shift, Caps_Lock ] }; }; And it's OK with Caps Lock disabled. When enabled by ctrl-caps lock: 1. it's being disabled by pressing (and releasing) caps lock alone, 2. pressed with other letter does only level3 shifting (and remains enabled). How should I fix it? -- Tom Pala [EMAIL PROTECTED] http://vfmg.sourceforge.net/ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] [4.3.0] nv driver: videoram option
On Mon, Mar 17, 2003 at 15:05:42 -0500, Mark Vojkovich wrote: Ramdisk located in video ram would be overwritten if something else (in ths case - X) use this video ram. You can't do that. Not only would you not want to do that because of the horrible performance reading from video ram, Is the performance worst than hard disk? NVIDIA hardware has critical state stored in videoram. The chip will hang if it gets corrupted. It's my risk. Anyway, it doesn't matter - the option shall not end with sig11. -- GoTaR priv0.onet.pl-gotar PLD stuff at http://mops.uci.agh.edu.pl/~gotar/ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] [4.3.0] nv driver: videoram option
On Sun, Mar 16, 2003 at 16:51:33 -0500, Mark Vojkovich wrote: I want to reduce memory being used in order to use the rest as a ramdisk. I don't understand that. What does reducing the amount of videoram have to do with a ramdisk? Ramdisk located in video ram would be overwritten if something else (in ths case - X) use this video ram. I thought the idea up and Michal Schulz gave the solution and detailed description, which you can find at: http://hedera.linuxnews.pl/_news/2002/09/03/_long/1445.html Caution in 5th point misses the true in the last sentence. Is there another way to say to X not to touch specified region of video memory? I see no reason to force VideoRam to lower than what there actually is, As you can see it's good solution for limited memory systems with modern graphics adapters (up to 128MB of VRAM). but if you do it's possible that something in core XFree86 code requires it to be a power of two. Write combine ranges can only be setup on power of two apertures. I've tried 16384, 8192 and 4096 - these are powers of 2. Nothing in the nv driver has changed in this respect. So where's the bug? Reducing works with tseng driver on my second video board - ET6100. -- GoTaR priv0.onet.pl-gotar PLD stuff at http://mops.uci.agh.edu.pl/~gotar/ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86