[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] X under dom0



(to list admin: please ignore the same message 
which was sent from a different address, sorry).


folks,

X (Xorg-x11) fails under dom0 (unstable-tree) on my environment.
If it works for me, it's very appreciated.

<Symptom>
 - X fails with the message 
  ...(snip)
  (II) VESA(0): initializing int10
  (EE) VESA(0): Cannot map SYS BIOS
  (II) UnloadModule: "vesa"
  (II) UnloadModule: "int10"
  (snip)...

 - strace -F gdm log says
  ...(snip)
  6293  write(0, "(II) VESA(0): initializing int10"..., 33) = 33
  6293  open("/dev/mem", O_RDWR)          = 5
  6293  mmap2(0xf0000, 65536, PROT_READ|PROT_EXEC, MAP_SHARED|MAP_FIXED, 5, 
0xf0) = -1 EINVAL (Invalid argument)
  6293  write(2, "(EE) VESA(0): Cannot map SYS BIO"..., 34) = 34
  6293  write(0, "(EE) VESA(0): Cannot map SYS BIO"..., 34) = 34
  6293  close(5)                          = 0
  (snip)...

 - ignorebiostables was not a help


<target hardware>
 - i915G (ICH6) m/b


Though I was not sure what kind of logs can provde clues,
on this mail, I attached the files below:-
 - Xorg.0.log.success : X success log under gentoo
 - Xorg.0.log.failed  : full failed-X-log under dom0
 - gdm.log.bz2        : full "strace -F gdm" under dom0
 - lspci_on_dom0      : lspci -vv under dom0



Thanks very much for your help.

Best regards,
Daisaku

Attachment: Xorg.0.log.failed
Description: Binary data

Attachment: Xorg.0.log.success
Description: Binary data

Attachment: gdm.log.bz2
Description: application/bzip

Attachment: lspci_on_dom0
Description: Binary data


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.