Re: [Xpert]How to stop a laptop going into standby when i close the lid?

2002-05-17 Thread Derek J Witt

Hi, J. Grant.

 I think most laptops have options in their bios about that, particularly
the power management menus.

If you're running acpid, I think the laptop lid acts like another button.

Just some starters.

-- Derek.

- Original Message -
From: "J. Grant" <[EMAIL PROTECTED]>
To: "xpert" <[EMAIL PROTECTED]>
Sent: Wednesday, May 15, 2002 1:19 AM
Subject: [Xpert]How to stop a laptop going into standby when i close the
lid?


> Hello, not sure if this got though, i could not find it on the mailing
> list log.
>
> Has anyone any thoughts on how to get this working please?
>
> JG
>
>  Original Message 
> Subject: How to stop a laptop going into standby when i close the  lid?
> Date: Mon, 13 May 2002 17:11:59 +0900
> From: "J. Grant" <[EMAIL PROTECTED]>
> To: xpert <[EMAIL PROTECTED]>
>
> Hi,
> Could someone tell me how can I stop a laptop going into standby when i
> close the lid?
>
> I checked apm but could not find this option that triggers the whole
> process, could someone point me to the file that contains this
> ON_LID_CLOSE=/usr/bin/apm suspend now
> or similar command please? I can not find it in the bios. Another OS can
> disable it...
>
> JG
>
> I have tired the following
>
> server flags section
>
>  Option "NoPM"  "boolean"
>
> Monitor section
>
>  Option  "DPMS"  "off"
>
> and
>
> Section "Device"
>
>  Option  "power_saver"
>
>
>
> All with no luck, it still 'Saves to RAM'
> In the bios i had it on custom with each one disabled, now i have it
> just on all disabled instead of custom.
>
> occasionall it does not go off, which is odd, but every time while i
> have been testing today it has.
>
> I dont want to cut off the switch and then leave the screen light on, i
> would like to just close the lid for carrying around the office, but it
> goes into suspend each time tho..
>
>
> ---
> Laptop Adagio (38W2) Same as DELL Inspiron 7500
>
>
> Chipset: "ATI Rage 128 Mobility LF (AGP)" (ChipID = 0x4c46)
> ATI Mobility 128 AGP 2X (English)
> ASIC Mobility 128
> ASIC ID 4c46
> Bios 004.039.064.023
> Date 31/8/2000
> Tuner Type: Philips FI1236 MK1 NTSC M/C
> Tuner Type: BT819
>
> Linear framebuffer at 0xf800
> MMIO registers at 0xf410
> VideoRAM: 16384 kByte (128-bit SDR SGRAM 1:1) SDRAM
>
> Using flat panel for display
> Panel size: 1400x1050
> Panel ID: IBM ITSX93
> Panel Type: Color, Single, TFT
> Panel Interface: LVDS
> PLL parameters: rf=2700 rd=60 min=12500 max=25000; xclk=10500
> Resolutions supported
> 1600 x 1200 but not all visible.
> 1400 x 1050 full
> 1280 x 1024
> 1024 x 768
> all 32 or 16 bpp or 256
> no 24bit mode
>
>






>
> XFree86 Version 4.1.0 / X Window System
> (protocol Version 11, revision 0, vendor release 6510)
> Release Date: 2 June 2001
> If the server is older than 6-12 months, or if your card is
> newer than the above date, look for a newer version before
> reporting problems.  (See http://www.XFree86.Org/FAQ)
> Build Operating System: Linux 2.4.8-5mdkenterprise i686 [ELF]
> Module Loader present
> (==) Log file: "/var/log/XFree86.0.log", Time: Mon May 13 16:47:52 2002
> (==) Using config file: "/etc/X11/XF86Config-4"
> Markers: (--) probed, (**) from config file, (==) default setting,
>  (++) from command line, (!!) notice, (II) informational,
>  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) ServerLayout "2"
> (**) |-->Screen "screen1" (0)
> (**) |   |-->Monitor "Generic|Generic Monitor, 1600x1200 @ 70 Hz"
> (**) |   |-->Device "ATI Rage 128 Mobility"
> (**) |-->Input Device "mouse2"
> (**) |-->Input Device "Keyboard1"
> (**) Option "AutoRepeat" "250 30"
> (**) Option "XkbRules" "xfree86"
> (**) XKB: rules: "xfree86"
> (**) Option "XkbModel" "pc105"
> (**) XKB: model: "pc105"
> (**) Option "XkbLayout" "gb"
> (**) XKB: layout: "gb"
> (==) Keyboard: CustomKeycode disabled
> (**) FontPath set to "unix/:-1"
> (**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
> (==) ModulePath set to "/usr/X11R6/lib/modules"
> (**) Option "NoPM" "1"
> (--) using VT number 7
>
> (II) Module ABI versions:
> XFree86 ANSI C Emulation: 0.1
> XFree86 Video Driver: 0.4
> XFree86 XInput driver : 0.2
> XFree86 Server Extension : 0.1
> XFree86 Font Renderer : 0.2
> (II) Loader running on linux
> (II) LoadModule: "bitmap"
> (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
> (II) Module bitmap: vendor="The XFree86 Project"
> compiled for 4.1.0, module version = 1.0.0
> Module class: XFree86 Font Renderer
> ABI class: XFree86 Font Renderer, version 0.2
> (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.1.0, module version = 0.1.0
> ABI class: XFree86 Video Driver, version 0.4
> (II) PCI: Probing config type using method 1
> (II) PCI: Config type is 1
> (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1

[Xpert]unsubscribe tngdsn12

2002-06-20 Thread Derek J Witt



___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]S3 ViRGE problems with Xfree86 v4.02

2001-09-21 Thread Derek J Witt

Mohan, I have an S3 Virge GX2 here. Does it lock up with certain
colour-depths? Try running X at 8-bit and see if it locks up. In my case,
if I try running it at 32-bit, all sorts of strange effects happen (like
invisible windows and floating widgets). AFAIK, 16-bit is the highest your
card can support.  I would try running 4.0.3 at least. The fixes related
to the gx2 partially fix the problems with the MX. The fixes were
incorporated in 4.0.3. I'm now running 4.1.0 and have not had problems
since 4.0.3. Before, the forsaken SVGA server would cause me to lock up
within seconds of any line-stipling or fast-scrolling text.

On Fri, 21 Sep 2001, Kevin Brosius wrote:

|Mohan Rajagopalan wrote:
|>
|>
|>
|> I tried compiling and installing X on my Toshiba Satellite 490CDT laptop
|> .. it compiles and installs. I have a S3 ViRGE /MX card with 2MB on the
|> laptop which is identified by xf86config.
|
|4.0.2 is rather old, would you be able to install 4.1.0?
|
|>
|> When I to start with any screen resolution > 320 X 200 the machine
|> hangs. After spending hours trying to trace the cause, I discovered the S3
|> device driver would hang trying to update the MTRRs for Write Combining.
|> Tha machine hangs even with all forms of acceleration disabled.
|> The only fix I could use is to change the driver to VESA.
|>
|> Has anyone else had similar problems ? Any fixes ??
|>
|> -mohan
|>
|
|We've had some trouble with MX.  What makes you think MTRRs are hanging
|the machine?  There are a couple updated drivers on my page at
|http://www.user1.netcarrier.com/~kbrosius/pages/virge.html, although I
|suspect even the 4.0.3 version will not run with 4.0.2.  If you give it
|a try let me know if it loads.
|
|

-- 
**  Derek J Witt**
*   Email: mailto:[EMAIL PROTECTED] *
*   Home Page: http://www.flinthills.com/~djw/   *
*** "Houston, the Eagle has landed and laid an egg!" -- Unknown **

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]S3 ViRGE problems with Xfree86 v4.02

2001-09-21 Thread Derek J Witt

Mohan, I have an S3 Virge GX2 here. Does it lock up with certain
colour-depths? Try running X at 8-bit and see if it locks up. In my case,
if I try running it at 32-bit, all sorts of strange effects happen (like
invisible windows and floating widgets). AFAIK, 16-bit is the highest your
card can support.  I would try running 4.0.3 at least. The fixes related
to the gx2 partially fix the problems with the MX. The fixes were
incorporated in 4.0.3. I'm now running 4.1.0 and have not had problems
since 4.0.3. Before, the forsaken SVGA server would cause me to lock up
within seconds of any line-stipling or fast-scrolling text.

On Fri, 21 Sep 2001, Kevin Brosius wrote:

|Mohan Rajagopalan wrote:
|>
|>
|>
|> I tried compiling and installing X on my Toshiba Satellite 490CDT laptop
|> .. it compiles and installs. I have a S3 ViRGE /MX card with 2MB on the
|> laptop which is identified by xf86config.
|
|4.0.2 is rather old, would you be able to install 4.1.0?
|
|>
|> When I to start with any screen resolution > 320 X 200 the machine
|> hangs. After spending hours trying to trace the cause, I discovered the S3
|> device driver would hang trying to update the MTRRs for Write Combining.
|> Tha machine hangs even with all forms of acceleration disabled.
|> The only fix I could use is to change the driver to VESA.
|>
|> Has anyone else had similar problems ? Any fixes ??
|>
|> -mohan
|>
|
|We've had some trouble with MX.  What makes you think MTRRs are hanging
|the machine?  There are a couple updated drivers on my page at
|http://www.user1.netcarrier.com/~kbrosius/pages/virge.html, although I
|suspect even the 4.0.3 version will not run with 4.0.2.  If you give it
|a try let me know if it loads.
|
|

-- 
**  Derek J Witt**
*   Email: mailto:[EMAIL PROTECTED] *
*   Home Page: http://www.flinthills.com/~djw/   *
*** "Houston, the Eagle has landed and laid an egg!" -- Unknown **


___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



[Xpert]Radeon 7000 QD (32Mb DDR)

2002-01-05 Thread Derek J Witt

Good day, everyone.  I have found a way to get this card to work with
XFree86 4.1.0.  I had to recompile the kernel with the AGP support module
(agpgart), the Radeon framebuffer modules (radeonfb), and the DRM updates
from dri.sourceforge.net.  I am using the 2.4.17 kernel.  The framebuffer
module has to be compiled as a module. If it's compiled into the kernel,
the scrolling mechanism is messed up; I get just a one-line buffer at the
top of the screen (overlapping the tux logo) until the screen is cleared
(via "clear").

Then in my XF86Config-4 file, I put this into my Device section:

Section "Device"
Driver  "radeon"
VideoRam 32768
Option  "UseDepthMoves"
Option  "UseFBDev"
EndSection

Now, "UseFBDev" must be in there, or XFree86 will either say no screens
found or the monitor will go on standby and freeze the computer.

I have found that the ATI2 drivers from the Gatos project will not work
with this card. The monitor ends up going into standby and the computer
hard locks.

But now, I get full GLX support. glxgears reports  900 fps.

Just my experience with this.

**  Derek J Witt  **
*   Email: mailto:[EMAIL PROTECTED]   *
*   Home Page: http://www.flinthills.com/~djw/ *
*** "...and on the eighth day, God met Bill Gates." - Unknown **

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



[Xpert]Re: Radeon 7000 QD (32Mb DDR)

2002-01-05 Thread Derek J Witt

Yeah, I was using the latest XFree86 4.1.0 drivers from GATOS's web site
and DRM drivers from there, too.  Hmm... Using "CrtScreen" should fix that
standby problem?  Is the framebuffer still needed for the radeaon X
driver? On my roommate's Gateway 2k box here, I have it running the
framebuffer and specifying the amount of vram in XF86Config-4.

**  Derek J Witt  **
*   Email: mailto:[EMAIL PROTECTED]   *
*   Home Page: http://www.flinthills.com/~djw/ *
*** "...and on the eighth day, God met Bill Gates." - Unknown **

___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert] Advice please?

2002-02-26 Thread Derek J Witt

Stephen, you just need to download the Linux kernel drivers and the GLX
nvidia drivers from nvidia.com. You can find the Linux drivers there. I
also have a MX card. Once you follow the instructions for those drivers,
you should have X running just fine. May have issues with your AGP
chipset, but the instructions for the GLX driver will help you with
that, too.
-- 
**  Derek J Witt  **
*   Email: mailto:[EMAIL PROTECTED]   *
*   Home Page: http://www.flinthills.com/~djw/ *
*** "...and on the eighth day, God met Bill Gates." - Unknown **



signature.asc
Description: This is a digitally signed message part