328569 – ATI driver not working on FireGL V5200 (T60p)

Bug 328569 - ATI driver not working on FireGL V5200 (T60p)

Summary: ATI driver not working on FireGL V5200 (T60p)

Status:	RESOLVED DUPLICATE of bug 326473

Alias:	None

Product:	openSUSE 10.3
Classification:	openSUSE
Component:	X11 3rd Party Driver (show other bugs)
Version:	RC 2
Hardware:	i386 Other

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	E-mail List
QA Contact:	Stefan Dirsch

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2007-09-26 15:41 UTC by Andreas Bauer
Modified:	2007-09-26 15:45 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
SaX.log (30.03 KB, text/x-log) 2007-09-26 15:43 UTC, Andreas Bauer	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Andreas Bauer 2007-09-26 15:41:42 UTC

fglrx rpms installed from /mounts/dist/full/full-i386

bauersmobil:~ # rpm -qa | grep fglrx
ati-fglrxG01-kmp-default-8.41.7_2.6.22.5_31-2
x11-video-fglrxG01-8.41.7-5

bauersmobil:~ # rpm -qa | grep kernel-default
kernel-default-2.6.22.5-31

bauersmobil:~ # sax2 -rm 0=fglrx
SaX: initializing please wait...
SaX: your current configuration will not be read in

SaX: no X-Server is running
SaX: will start own server if needed
SPP: prepare device [0] profile: FireGL
SPP: prepare device [1] profile: synaptics
SPP: calling device [1] profile script: synaptics
SPP: prepare device [3] profile: ibm-trackpoint
SPP: profile will add new section(s) -> moving: 3
SPP: including prepared profile(s)...

SaX: startup

xc: sorry could not start configuration server
xc: for details refer to the log file:

    /var/log/SaX.log

xc: abort...

SaX.log will be attached

Comment 1 Andreas Bauer 2007-09-26 15:43:02 UTC

Created attachment 174894 [details]
SaX.log

Comment 2 Stefan Dirsch 2007-09-26 15:45:13 UTC


*** This bug has been marked as a duplicate of bug 326473 ***