Author Topic: MD won't start properly if no monitor is connected to it  (Read 2420 times)

bulek

  • Administrator
  • wants to work for LinuxMCE
  • *****
  • Posts: 909
  • Living with LMCE
    • View Profile
MD won't start properly if no monitor is connected to it
« on: March 29, 2008, 10:27:15 pm »
Hi,

I have older Epia mobo (ME6000) that is used only as audio source for whole-house audio and therefore is used as headless MD, only for remote controlled audio play... But I spot weird behaviour. If I disconect LCD monitor, then it won't boot properly (it says "cannot connect to X...").

I've read few entries about monitor detection to be disabled, but I'm not sure if this is proper cure and how to do this most efficient and easy under lmce ?

Thanks in advance,

regards,

Bulek.
« Last Edit: March 29, 2008, 10:37:54 pm by bulek »
Thanks in advance,

regards,

Bulek.

Zaerc

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 2256
  • Department of Redundancy Department.
    • View Profile
Re: MD won't start properly if no monitor is connected to it
« Reply #1 on: March 30, 2008, 01:11:31 pm »
Are there any related errors in /var/log/Xorg.0.log?
"Change is inevitable. Progress is optional."
-- Anonymous


bulek

  • Administrator
  • wants to work for LinuxMCE
  • *****
  • Posts: 909
  • Living with LMCE
    • View Profile
Re: MD won't start properly if no monitor is connected to it
« Reply #2 on: April 20, 2008, 12:13:49 am »
Are there any related errors in /var/log/Xorg.0.log?
Hi,

sorry for response delay... I've tried again and it works in quite determined way:
- if nothing is connected on RGB, then error is displayed - something like "X11 server cannot be started" or something similar
- if I connect LCD to VGA port during work, error message imediately dissappears and then X is started along with LMCE Orbiter...

Any idea ?

Thanks in advance,

regards,

Bulek.

Quote
...

(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
        compiled for 1.3.0, module version = 1.0.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 0.3
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
        compiled for 1.3.0, module version = 1.0.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 0.3
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
        compiled for 1.3.0, module version = 1.13.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 0.3
(II) Loading extension RECORD
(II) LoadModule: "xtrap"
(II) Loading /usr/lib/xorg/modules/extensions//libxtrap.so
(II) Module xtrap: vendor="X.Org Foundation"
        compiled for 1.3.0, module version = 1.0.0
        Module class: X.Org Server Extension
        ABI class: X.Org Server Extension, version 0.3
(II) Loading extension DEC-XTRAP
(II) LoadModule: "type1"
(WW) Warning, couldn't open module type1
(II) UnloadModule: "type1"
(EE) Failed to load module "type1" (module does not exist, 0)
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
        compiled for 1.3.0, module version = 1.0.0
        ABI class: X.Org Server Extension, version 0.3
(**) AIGLX disabled
(II) Loading extension GLX
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules//libint10.so
(II) Module int10: vendor="X.Org Foundation"
        compiled for 1.3.0, module version = 1.0.0
        ABI class: X.Org Video Driver, version 1.2
(II) LoadModule: "v4l"
(II) Loading /usr/lib/xorg/modules/drivers//v4l_drv.so
(II) Module v4l: vendor="X.Org Foundation"
        compiled for 7.2.0, module version = 0.1.1
        ABI class: X.Org Video Driver, version 1.1
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
        compiled for 1.3.0, module version = 1.0.0
        ABI class: X.Org Server Extension, version 0.3
(II) Loading extension XFree86-DRI
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules//fonts/libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
        compiled for 1.3.0, module version = 2.1.0
        Module class: X.Org Font Renderer
        ABI class: X.Org Font Renderer, version 0.5
(II) Loading font FreeType
(II) LoadModule: "via"
(II) Loading /usr/lib/xorg/modules/drivers//via_drv.so
(II) Module via: vendor="X.Org Foundation"
        compiled for 1.3.0, module version = 0.2.1
        Module class: X.Org Video Driver
        ABI class: X.Org Video Driver, version 1.2
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
        compiled for 1.3.0, module version = 1.2.1
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 0.7
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
        compiled for 1.3.0, module version = 1.2.1
        Module class: X.Org XInput Driver
        ABI class: X.Org XInput driver, version 0.7
(II) v4l driver for Video4Linux
(II) VIA: driver for VIA chipsets: CLE266, KM400/KN400, K8M800,
        PM800/PM880/CN400
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(--) Chipset CLE266 found
(!!) VIA Technologies does not support or endorse this driver in any way.
(!!) For support please contact the driver maintainer or your X vendor.
(II) resource ranges after xf86ClaimFixedResources() call:
       
  • -1  0       0x00100000 - 0x3fffffff (0x3ff00000) MXE(B)
  • [1] -1  0       0x000f0000 - 0x000fffff (0x10000) MX

        [2] -1  0       0x000c0000 - 0x000effff (0x30000) MX
        [3] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX
        [4] -1  0       0xea002000 - 0xea0020ff (0x100) MX
        [5] -1  0       0xea001000 - 0xea0010ff (0x100) MX
        [6] -1  0       0xea000000 - 0xea0007ff (0x800) MX
        [7] -1  0       0xe0000000 - 0xdfffffff (0x0) MXO
        [8] -1  0       0xe8000000 - 0xe8ffffff (0x1000000) MX(B)
        [9] -1  0       0xe4000000 - 0xe7ffffff (0x4000000) MX(B)
        [10] -1 0       0x0000ffff - 0x0000ffff (0x1) IX
        [11] -1 0       0x00000000 - 0x000000ff (0x100) IX
        [12] -1 0       0x0000e400 - 0x0000e4ff (0x100) IX
        [13] -1 0       0x0000e000 - 0x0000e0ff (0x100) IX
        [14] -1 0       0x0000dc00 - 0x0000dc1f (0x20) IX
        [15] -1 0       0x0000d800 - 0x0000d81f (0x20) IX
        [16] -1 0       0x0000d400 - 0x0000d41f (0x20) IX
        [17] -1 0       0x0000d000 - 0x0000d07f (0x80) IX
(II) resource ranges after probing:
       
  • -1  0       0x00100000 - 0x3fffffff (0x3ff00000) MXE(B)
  • [1] -1  0       0x000f0000 - 0x000fffff (0x10000) MX

        [2] -1  0       0x000c0000 - 0x000effff (0x30000) MX
        [3] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX
        [4] -1  0       0xea002000 - 0xea0020ff (0x100) MX
        [5] -1  0       0xea001000 - 0xea0010ff (0x100) MX
        [6] -1  0       0xea000000 - 0xea0007ff (0x800) MX
        [7] -1  0       0xe0000000 - 0xdfffffff (0x0) MXO
        [8] -1  0       0xe8000000 - 0xe8ffffff (0x1000000) MX(B)
        [9] -1  0       0xe4000000 - 0xe7ffffff (0x4000000) MX(B)
        [10] 0  0       0x000a0000 - 0x000affff (0x10000) MS
        [11] 0  0       0x000b0000 - 0x000b7fff (0x8000) MS
        [12] 0  0       0x000b8000 - 0x000bffff (0x8000) MS
        [13] -1 0       0x0000ffff - 0x0000ffff (0x1) IX
        [14] -1 0       0x00000000 - 0x000000ff (0x100) IX
        [15] -1 0       0x0000e400 - 0x0000e4ff (0x100) IX
        [16] -1 0       0x0000e000 - 0x0000e0ff (0x100) IX
        [17] -1 0       0x0000dc00 - 0x0000dc1f (0x20) IX
        [18] -1 0       0x0000d800 - 0x0000d81f (0x20) IX
        [19] -1 0       0x0000d400 - 0x0000d41f (0x20) IX
        [20] -1 0       0x0000d000 - 0x0000d07f (0x80) IX
        [21] 0  0       0x000003b0 - 0x000003bb (0xc) IS
        [22] 0  0       0x000003c0 - 0x000003df (0x20) IS
(II) Setting vga for screen 0.
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
        compiled for 1.3.0, module version = 0.1.0
        ABI class: X.Org Video Driver, version 1.2
(**) VIA(0): Depth 24, (--) framebuffer bpp 32
(==) VIA(0): RGB weight 888
(==) VIA(0): Default visual is TrueColor
(==) VIA(0): Using XAA acceleration architecture
(==) VIA(0): Using HW cursor
(--) VIA(0): Chipset: "CLE266"
(--) VIA(0): mapping MMIO @ 0xe8000000 with size 0x9000
(--) VIA(0): mapping BitBlt MMIO @ 0xe8200000 with size 0x10000
(II) VIA(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(--) VIA(0): Chipset Rev.: 3
(WW) VIA(0): Manufacturer plainly copied main PCI ids to Subsystem/Card ids.
(--) VIA(0): Detected VIA VT3122 (CLE266)-EPIA M/MII/....
(==) VIA(0): Using gamma correction (1.0, 1.0, 1.0)
(--) VIA(0): videoram =  65536k
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"(II) Module already built-in
(II) VIA(0): I2C bus "I2C bus 1" initialized.
(II) VIA(0): I2C bus "I2C bus 2" initialized.
(II) VIA(0): I2C bus "I2C bus 3" initialized.
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"(II) Module already built-in
(II) VIA(0): I2C device "I2C bus 1:ddc2" registered at address 0xA0.
(II) VIA(0): I2C device "I2C bus 1:ddc2" removed.
(II) VIA(0): I2C device "I2C bus 2:VT162x" registered at address 0x40.
(--) VIA(0): Detected VIA Technologies VT1622 TV Encoder
(--) VIA(0): VT162x: Nothing connected.
(II) VIA(0): Monitor0: Using hsync range of 20.00-500.00 kHz
(II) VIA(0): Monitor0: Using vrefresh range of 59.00-61.00 Hz
(II) VIA(0): Clock range:  20.00 to 230.00 MHz
(II) VIA(0): Not using default mode "640x350" (vrefresh out of range)
(II) VIA(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "640x400" (vrefresh out of range)
(II) VIA(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "720x400" (width too large for virtual size)
(II) VIA(0): Not using default mode "360x200" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "640x480" (no clock available for mode)
(II) VIA(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "640x480" (vrefresh out of range)
(II) VIA(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "640x480" (vrefresh out of range)
(II) VIA(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "640x480" (vrefresh out of range)
(II) VIA(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "800x600" (width too large for virtual size)
(II) VIA(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "800x600" (width too large for virtual size)
(II) VIA(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "800x600" (width too large for virtual size)
(II) VIA(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "800x600" (width too large for virtual size)
(II) VIA(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "800x600" (width too large for virtual size)
(II) VIA(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "1024x768" (width too large for virtual size)
(II) VIA(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "1024x768" (width too large for virtual size)
(II) VIA(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "1024x768" (width too large for virtual size)
(II) VIA(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "1024x768" (width too large for virtual size)
(II) VIA(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "1024x768" (width too large for virtual size)
(II) VIA(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "1152x864" (width too large for virtual size)
(II) VIA(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "1280x960" (width too large for virtual size)
(II) VIA(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "1280x960" (width too large for virtual size)
(II) VIA(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "1280x1024" (width too large for virtual size)
(II) VIA(0): Not using default mode "640x512" (height too large for virtual size)
(II) VIA(0): Not using default mode "1280x1024" (width too large for virtual size)
(II) VIA(0): Not using default mode "640x512" (height too large for virtual size)
(II) VIA(0): Not using default mode "1280x1024" (width too large for virtual size)
(II) VIA(0): Not using default mode "640x512" (height too large for virtual size)
(II) VIA(0): Not using default mode "1600x1200" (width too large for virtual size)
(II) VIA(0): Not using default mode "800x600" (width too large for virtual size)
(II) VIA(0): Not using default mode "1600x1200" (width too large for virtual size)
(II) VIA(0): Not using default mode "800x600" (width too large for virtual size)
(II) VIA(0): Not using default mode "1600x1200" (width too large for virtual size)
(II) VIA(0): Not using default mode "800x600" (width too large for virtual size)
(II) VIA(0): Not using default mode "1600x1200" (width too large for virtual size)
(II) VIA(0): Not using default mode "800x600" (width too large for virtual size)
(II) VIA(0): Not using default mode "1600x1200" (width too large for virtual size)
(II) VIA(0): Not using default mode "800x600" (width too large for virtual size)
(II) VIA(0): Not using default mode "1792x1344" (width too large for virtual size)
(II) VIA(0): Not using default mode "896x672" (width too large for virtual size)
(II) VIA(0): Not using default mode "1792x1344" (width too large for virtual size)
(II) VIA(0): Not using default mode "896x672" (width too large for virtual size)
(II) VIA(0): Not using default mode "1856x1392" (width too large for virtual size)
(II) VIA(0): Not using default mode "928x696" (width too large for virtual size)
(II) VIA(0): Not using default mode "1856x1392" (width too large for virtual size)
(II) VIA(0): Not using default mode "928x696" (width too large for virtual size)
(II) VIA(0): Not using default mode "1920x1440" (width too large for virtual size)
(II) VIA(0): Not using default mode "960x720" (width too large for virtual size)
(II) VIA(0): Not using default mode "1920x1440" (width too large for virtual size)
(II) VIA(0): Not using default mode "960x720" (width too large for virtual size)
(II) VIA(0): Not using default mode "832x624" (width too large for virtual size)
(II) VIA(0): Not using default mode "416x312" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "1280x768" (width too large for virtual size)
(II) VIA(0): Not using default mode "640x384" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "1280x800" (width too large for virtual size)
(II) VIA(0): Not using default mode "640x400" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "1152x768" (width too large for virtual size)
(II) VIA(0): Not using default mode "576x384" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "1152x864" (width too large for virtual size)
(II) VIA(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
(II) VIA(0): Not using default mode "1400x1050" (width too large for virtual size)
(II) VIA(0): Not using default mode "700x525" (width too large for virtual size)
(II) VIA(0): Not using default mode "1400x1050" (width too large for virtual size)
(II) VIA(0): Not using default mode "700x525" (width too large for virtual size)
(II) VIA(0): Not using default mode "1400x1050" (width too large for virtual size)
(II) VIA(0): Not using default mode "700x525" (width too large for virtual size)
(II) VIA(0): Not using default mode "1400x1050" (width too large for virtual size)
(II) VIA(0): Not using default mode "700x525" (width too large for virtual size)
(II) VIA(0): Not using default mode "1440x900" (width too large for virtual size)
(II) VIA(0): Not using default mode "720x450" (width too large for virtual size)
(II) VIA(0): Not using default mode "1600x1024" (width too large for virtual size)
(II) VIA(0): Not using default mode "800x512" (width too large for virtual size)
(II) VIA(0): Not using default mode "1680x1050" (width too large for virtual size)
(II) VIA(0): Not using default mode "840x525" (width too large for virtual size)
(II) VIA(0): Not using default mode "1920x1200" (width too large for virtual size)
(II) VIA(0): Not using default mode "960x600" (width too large for virtual size)
(II) VIA(0): Not using default mode "1920x1200" (width too large for virtual size)
(II) VIA(0): Not using default mode "960x600" (width too large for virtual size)
(II) VIA(0): Not using default mode "1920x1440" (width too large for virtual size)
(II) VIA(0): Not using default mode "960x720" (width too large for virtual size)
(II) VIA(0): Not using default mode "2048x1536" (width too large for virtual size)
(II) VIA(0): Not using default mode "1024x768" (width too large for virtual size)
(II) VIA(0): Not using default mode "2048x1536" (width too large for virtual size)
(II) VIA(0): Not using default mode "1024x768" (width too large for virtual size)
(II) VIA(0): Not using default mode "2048x1536" (width too large for virtual size)
(II) VIA(0): Not using default mode "1024x768" (width too large for virtual size)
(WW) VIA(0): Mode pool is empty
(EE) VIA(0): No valid modes found
(II) VIA(0): I2C device "I2C bus 2:VT1622" removed.
(II) UnloadModule: "via"
(II) UnloadModule: "vgahw"
(II) Unloading /usr/lib/xorg/modules//libvgahw.so
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found
root@moon32:~#
Thanks in advance,

regards,

Bulek.

colinjones

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 3003
    • View Profile
Re: MD won't start properly if no monitor is connected to it
« Reply #3 on: April 20, 2008, 09:08:46 am »
looks like it is unable to generate/probe/determine any valid modes (mode pool is empty), and so unloads the drivers - thus X can't find any screens and fails to initialise....

don't really know why, but I'm assuming that there is an option you can use in xorg.conf to tell it not to detect the monitor.

also, check that UseEDID is set to false - that's the default, and the messages don't mention the EDID process is starting, but its worth a try

finally, maybe turning off some of the ModeValidation options (or use the "No..." version of the option to disable it", or even set UseExactModeTimingsDVI to false - you are trying to prevent the mode validation process from running so that all the default modes are not eliminated from the mode pool.... if you can get that to happen then it will leave the drivers initialised, select a mode and start up X.... however there is no guarantee that the mode selected will work with any monitor you subsequently plug into it :)
« Last Edit: April 20, 2008, 09:10:31 am by colinjones »

Zaerc

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 2256
  • Department of Redundancy Department.
    • View Profile
Re: MD won't start properly if no monitor is connected to it
« Reply #4 on: April 20, 2008, 01:54:01 pm »
Maybe you just have to specify an appropriate modeline for the monitor/resolution you are using.
"Change is inevitable. Progress is optional."
-- Anonymous