WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Dom0 Xorg won't work

On Sat, 05 Sep 2009 14:53:48 -0400
ken <gebser@xxxxxxxxxxxx> wrote:

> Here's one thing to try: Run (as root) "lspci -v" and find what the
> system thinks your video controller is.

There is no lspci in NetBSD. The approximate command is pcictl, and
with "pcictl pci2 list" I get this:
    002:00:0: ATI Technologies product 0x95c5 (VGA display)
    002:00:1: ATI Technologies product 0xaa28 (multimedia subclass 0x03)
 which ist the ATI (Asus) EAH3450 video and audio.

> Years ago I had a problem with
> the system wrongly detecting the video chipset for my Radeon card.

The base system doesn't have to know the video card, except for the VGA
compatible part to do console text. The Xorg radeonhd driver supports
the card, at least well enough for me to work with.

> I was able to fix it just by changing one line in some file I can't remember 
> right
> now and then doing radical surgery on my xorg.conf file.

Well, I don't know where to tweak a setting. Here's an excerpt of
Xorg.0.log when it fails to initialise the radeonhd:

...[snip]...
(II) RADEONHD(0): Detected VGA mode.
(II) RADEONHD(0): Minimum Pixel ClockPLL Frequency Output: 0
(II) RADEONHD(0): Maximum Pixel ClockPLL Frequency Output: 1200000
(II) RADEONHD(0): Maximum Pixel Clock: 400000
(II) RADEONHD(0): Reference Clock: 27000
(II) RADEONHD(0): FB: Allocated Cursor Image at offset 0x00000000 (size
= 0x00004000)
(II) RADEONHD(0): FB: Allocated Cursor Image at offset 0x00004000 (size
= 0x00004000)
(II) RADEONHD(0): Connector[0] {RHD_CONNECTOR_VGA, "VGA CRT2",
RHD_DDC_1, RHD_HPD_NONE, { RHD_OUTPUT_DACB, RHD_OUTPUT_NONE } }
(II) RADEONHD(0): Connector[1] {RHD_CONNECTOR_DVI_SINGLE, "HDMI_TYPE_A
DFP1", RHD_DDC_2, RHD_HPD_1, { RHD_OUTPUT_UNIPHYB, RHD_OUTPUT_NONE } }
(II) RADEONHD(0): Connector [2] {RHD_CONNECTOR_DVI, "DUAL_LINK_DVI_I
CRT1 DFP2", RHD_DDC_0, RHD_HPD_0, { RHD_OUTPUT_KLDSKP_LVTMA,
RHD_OUTPUT_DACA } }
(--) RADEONHD (0): Attaching Output DAC B to Connector VGA 1
(EE) RADEONHD(0): RHDHdmiInit: unknown HDMI output type
(--) RADEONHD(0): Attaching Output UNIPHY_B to Connector DVI-D 1
(--) RADEONHD(0): Attaching Output UNIPHY_KLDSKP_LVTMA to Connector
DVI-I 2
(--) RADEONHD (0): Attaching Output DAC A to Connector DVI-I 2
(II) RADEONHD(0): RandR 1.2 support disabled due to configuration
(EE) RADEONHD(0): Failed to detect a connected monitor
(II) RADEONHD(0): Destroying DAC B
(II) RADEONHD(0): Destroying UNIPHY_B
(II) RADEONHD(0): Destroying UNIPHY_KLDSKP_LVTMA
(II) RADEONHD(0): Destroying DAC A
(II) RADEONHD(0): I2C bus "RHD I2C line 0" removed.
(II) RADEONHD(0): I2C bus "RHD I2C line 1" removed.
(II) RADEONHD(0): I2C bus "RHD I2C line 2" removed.
(II) RADEONHD(0): I2C bus "RHD I2C line 3" removed.
(II) UnloadModule: "radeonhd"
(EE) Screen(s) found, but none have a usable configuration.
...[snap]...

My VGA monitor is connected to Connector[0] in above output, i.e. to
"VGA CRT2". The monitor isn't recognized through E-EDID. When running
in native mode, it is detected and used:

...[snip]...
(--) RADEONHD(0): Attaching Output DAC B to Connector VGA 1
(EE) RADEONHD(0): RHDHdmiInit: unknown HDMI output type
(--) RADEONHD(0): Attaching Output UNIPHY_B to Connector DVI-D 1
(--) RADEONHD(0): Attaching Output UNIPHY_KLDSKP_LVTMA to Connector
DVI-I 2
(--) RADEONHD(0): Attaching Output DAC A to Connector DVI-I 2
(II) RADEONHD(0): RandR 1.2 support disabled due to configuration
(II) RADEONHD(0): DAC A: Sensed Output: VGA
(II) RADEONHD(0): I2C device "RHD I2C line 0:E-EDID segment register"
registered at address 0x60.
(II) RADEONHD(0): I2C device "RHD I2C line 0:ddc2" registered at
address 0xA0.
(II) RADEONHD(0): EDID data for Acer X223W
(II) RADEONHD(0): Manufacturer: ACR  Model: 9  Serial#: 2171690010
(II) RADEONHD(0): Year: 2008  Week: 17
...[snap]...

It looks like the I²C device isn't working under xen33 and so the
monitor can't be detected.

Juergen

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>