From: Florent Ouchet <ouchet.florent@laposte.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Gentoo AMD64 + Xen + Ati drivers
Date: Wed, 05 Dec 2007 11:33:35 +0100 [thread overview]
Message-ID: <47567E7F.7080806@laposte.net> (raw)
Hi all,
I experienced some problems with the following combination of software:
- xen-sources 2.6.20-r6
- xen-tools 3.1.2
- ati-drivers 8.40.4
- linux 2.6.20
- xorg-server 1.3.0.0-r2 (build with support for fbdev, vesa and fglrx)
The system is a Dom0 of a paravirtualized system:
- Core 2 Duo 2.4GHz (vT enabled)
- 2GB RAM
- ATI Radeon x1300 video card
Is anyone running such a configuration with success? I have to stay with
the vesa driver without hardware acceleration.
First of all, the "fglrx" kernel module of ati-drivers refuse to be
loaded because of an inexistent symbol (flush_tlb_page) in the kernel,
this error is easily solved by patching
/usr/src/linux/arch/x86_64/kernel/smp.c (note that this patch is applied
to the i386 arch, why is it missing here? - worth a report to
xensource). After recompiling the kernel and its modules, rebooting and
emerging ati-drivers again the fglrx module can be loaded.
an export is missing on line 301:
-----------------------
void flush_tlb_page(struct vm_area_struct * vma, unsigned long va)
{ xen_invlpg_mask(&vma->vm_mm->cpu_vm_mask, va); }
+EXPORT_SYMBOL(flush_tlb_page);
void flush_tlb_all(void)
-----------------------
After doing this, the ati-drivers don't work as expected, running "Xorg
-configure" raise an exception in the driver:
-----------------------
xenoutch / # Xorg -configure :1
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: UNKNOWN
Current Operating System: Linux xenoutch 2.6.20-xen-r6 #10 SMP Tue Dec 4
14:55:28 CET 2007 x86_64
Build Date: 04 December 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Wed Dec 5 11:22:43 2007
List of video drivers:
fglrx
fbdev
vesa
vga
Backtrace:
0: Xorg(xf86SigHandler+0x6d) [0x48f90e]
1: /lib/libc.so.6 [0x2b4d877c4680]
2: /lib/libc.so.6(memcpy+0x46) [0x2b4d8780a636]
3: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(atiddxProbeMain+0xf1)
[0x2b4d87e3a731]
4: Xorg(DoConfigure+0x1f6) [0x49d2e0]
5: Xorg(InitOutput+0x6a2) [0x465605]
6: Xorg(main+0x275) [0x439aca]
7: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b4d877b1b74]
8: Xorg(FontFileCompleteXLFD+0x211) [0x439039]
Fatal server error:
Caught signal 11. Server aborting
Aborted
xenoutch / #
--------------------------
Selecting "fglrx" in an existing /etc/X11/xorg.conf makes X server to
freeze (and local display unusable), all tty cannot be reached, screen
is black; the system can be rebooted via ssh.
Regards,
Florent
--
gentoo-amd64@gentoo.org mailing list
next reply other threads:[~2007-12-05 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-05 10:33 Florent Ouchet [this message]
2007-12-08 18:27 ` [gentoo-amd64] Gentoo AMD64 + Xen + Ati drivers Florent Ouchet
2007-12-08 19:07 ` Beso
2007-12-09 13:56 ` Florent Ouchet
2007-12-09 14:33 ` Beso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47567E7F.7080806@laposte.net \
--to=ouchet.florent@laposte.net \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox