Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#18924 - [ati-dri] ATI HD4650: impossible to start X with 7.7.1-0.1

Attached to Project: Arch Linux
Opened by Lionel Poiblanc (Laserpithiumm) - Friday, 02 April 2010, 11:56 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 19 December 2010, 13:53 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Andreas Radke (AndyRTR)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
I am using an ATI HD4650, with radeon driver on an Archlinux 64bits.
Impossible to start X server (black screen) with the newer ati-dri 7.7.1-0.1, updated in extra the 31/03.
Kernel log says: "Your graphic environnement is broken. Try updating xf86-video-ati or mesa"
Everything was OK with previous version (7.7.1).

System is running Archlinux 64bits and all repository up-to-date the 02nd/04. Using nothing from testing (especially, the kernel is still 2.6.32).

Reinstalling the previous version of ati-dri and libgl (7.7.1 instead of 7.7.1-0.1) solves the issue.

This task depends upon

Closed by  Andreas Radke (AndyRTR)
Sunday, 19 December 2010, 13:53 GMT
Reason for closing:  None
Comment by Gerardo Exequiel Pozzi (djgera) - Saturday, 03 July 2010, 17:30 GMT
  • Field changed: Summary (ATI HD4650: impossible to start X with ati-dri 7.7.1-0.1 → [ati-dri] ATI HD4650: impossible to start X with 7.7.1-0.1)
  • Field changed: Status (Unconfirmed → Assigned)
  • Task assigned to Jan de Groot (JGC)
status with 7.8.2?
Comment by Lionel Poiblanc (Laserpithiumm) - Sunday, 04 July 2010, 02:32 GMT
OK, I did a fresh install with up-to-date core and extra repo (thus using 7.8.2).
Now this is working.

As I have been the only one to report this problem which is not appearing again on a fresh install with newer version, I propose to close this bug report.

Loading...