LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Laptop and Netbook (https://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/)
-   -   Turn off display on Toshiba Tecra 9000 - Debian 7.0 (https://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/turn-off-display-on-toshiba-tecra-9000-debian-7-0-a-4175468493/)

h4rri 07-04-2013 11:39 AM

Turn off display on Toshiba Tecra 9000 - Debian 7.0
 
Hi,

I have an old Toshiba Tecra 9000 which I have 'converted' into a photo frame re-using all the original boards and screen.

I have an issue where the display goes dark but will not power off and the back light is lighting up the room. I am trying to console in and power down the screen using:

Code:

xset dpms force off
xset:  unable to open display ""

sudo vbetool dpms off
This command hangs the console window

When I run xrandr to attempt to disable the display with:

Code:

xrandr --output LVDS1 --off
I get:

Code:

xrandr
Can't open display


The laptop is picking up on the correct VGA driver:

Snippet of cat /var/log/Xorg.0.log
Code:

[    43.056] (II) Loading /usr/lib/xorg/modules/drivers/savage_drv.so
[    43.082] (II) Module savage: vendor="X.Org Foundation"
[    43.082]    compiled for 1.12.1, module version = 2.3.4
[    43.082]    Module class: X.Org Video Driver
[    43.082]    ABI class: X.Org Video Driver, version 12.0
[    43.083] (II) LoadModule: "vesa"
[    43.083] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[    43.218] (II) Module vesa: vendor="X.Org Foundation"
[    43.218]    compiled for 1.12.1, module version = 2.3.1
[    43.218]    Module class: X.Org Video Driver
[    43.218]    ABI class: X.Org Video Driver, version 12.0
[    43.218] (II) LoadModule: "fbdev"
[    43.219] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    43.234] (II) Module fbdev: vendor="X.Org Foundation"
[    43.234]    compiled for 1.12.1, module version = 0.4.2
[    43.234]    ABI class: X.Org Video Driver, version 12.0
[    43.234] (II) SAVAGE: driver (version 2.3.4) for S3 Savage chipsets: Savage4,
        Savage3D, Savage3D-MV, Savage2000, Savage/MX-MV, Savage/MX,
        Savage/IX-MV, Savage/IX, ProSavage PM133, ProSavage KM133,
        Twister PN133, Twister KN133, SuperSavage/MX 128, SuperSavage/MX 64,
        SuperSavage/MX 64C, SuperSavage/IX 128, SuperSavage/IX 128,
        SuperSavage/IX 64, SuperSavage/IX 64, SuperSavage/IXC 64,
        SuperSavage/IXC 64, ProSavage DDR, ProSavage DDR-K
[    43.236] (II) VESA: driver for VESA chipsets: vesa
[    43.236] (II) FBDEV: driver for framebuffer: fbdev
[    43.236] (++) using VT number 7

[    43.281] (WW) Falling back to old probe method for vesa
[    43.281] (WW) Falling back to old probe method for fbdev
[    43.281] (II) Loading sub module "fbdevhw"
[    43.281] (II) LoadModule: "fbdevhw"

The EDID of the screen is:

Code:

sudo get-edid | sudo parse-edid
parse-edid: parse-edid version 2.0.0
get-edid: get-edid version 2.0.0

        Performing real mode VBE call
        Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
        Function supported
        Call successful

        VBE version 200
        VBE string at 0xc2d2a "S3 Graphics Incorporated. Paramount video BIOS"

VBE/DDC service about to be called
        Report DDC capabilities

        Performing real mode VBE call
        Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
bff7e214:b7795798: B779F000 ILLEGAL EXTENDED X86 OPCODE!
halt_sys: file îVy·<, line -1216784488
        Function unsupported
        Call successful

Reading next EDID block

VBE/DDC service about to be called
        Read EDID

        Performing real mode VBE call
        Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
        Function supported
        Call failed

The EDID data should not be trusted as the VBE call failed
Error: output block unchanged
parse-edid: IO error reading EDID



Running Xorg -configure to refresh the config yields the following log:
Code:

[ 76736.317] (**) ModulePath set to "/usr/lib/xorg/modules"
[ 76736.317] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 76736.317] (WW) Disabling Mouse0
[ 76736.317] (WW) Disabling Keyboard0
[ 76736.318] (WW) Falling back to old probe method for fbdev
[ 76736.318] (II) Loading sub module "fbdevhw"
[ 76736.318] (II) LoadModule: "fbdevhw"
[ 76736.319] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 76736.333] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 76736.333]    compiled for 1.12.4, module version = 0.0.2
[ 76736.333]    ABI class: X.Org Video Driver, version 12.1
[ 76736.333] (WW) Falling back to old probe method for vesa
[ 76736.334] Number of created screens does not match number of detected devices.
  Configuration failed.



Can anyone point me in the right direction please? I am out of idea's and googling has only got me this far.

ukiuki 07-16-2013 08:02 PM

Are you running the default install of Debian 7? Could you post the output for xset q please.

To have the xset to turn off the screen it must be enabled with
Code:

xset +dpms
By default it turns off the screen in 600 secs or 10 minutes.

Regards

h4rri 07-18-2013 10:48 AM

Thanks you for replying, I am indeed running the default Debian 7.

The output is from an SSH session is:

Code:

xset q
xset:  unable to open display ""

I am assuming I will need to run this from an X session on the box

I am currently getting an issue with the backlight where it 'bleeds' until the screen is entirely white.


All times are GMT -5. The time now is 12:25 PM.