|Summary:||0x7183:0x1028:0x0302: RV516 Radeon X1300 Pro : Screens stay black|
|Product:||xorg||Reporter:||Nicolas Bareil <nico>|
|Component:||Driver/radeonhd||Assignee:||Luc Verhaegen <lverhaegen>|
|Status:||RESOLVED INVALID||QA Contact:||Xorg Project Team <xorg-team>|
|i915 platform:||i915 features:|
Description Nicolas Bareil 2008-04-14 06:59:29 UTC
Created attachment 15902 [details] Xorg.lorg of the bad commit I were using the 1.1.0 version of radeonhd and when I pulled and compiled the git repository today, a regression occured : my screens (I'm in dual screen) stay black after running X. If I switch back to the virtual terminal, nothing change, the screens are still black but I can reboot with Ctrl+Alt+Sys. After rebooting enough times, the bisection gave me the following commit : af0c64d897f7f2288419b6e43468850e1037bb59 is first bad commit commit af0c64d897f7f2288419b6e43468850e1037bb59 Author: Luc Verhaegen <firstname.lastname@example.org> Date: Mon Jan 28 13:09:55 2008 +0100 R5xx accel: Add XAA support. MMIO path only, no CP support yet. :040000 040000 200a88e434a3e1b1b7dfdfe9007ac063f7c7e7d2 eca764300b61c65c03417800e9dd8fe5eb7f5219 M src In the Xorg.log (attached to this report), there is this notice : (**) RADEONHD(0): Selected XAA 2D acceleration. (II) RADEONHD(0): Unknown card detected: 0x7183:0x1028:0x0302. If - and only if - your card does not work or does not work optimally please contact email@example.com to help rectify this. Use the subject: 0x7183:0x1028:0x0302: <name of board>. (--) RADEONHD(0): Detected an RV516 on an unidentified card (II) RADEONHD(0): Mapped IO at 0x2b8b3b89b000 (size 0x00010000) (II) RADEONHD(0): Getting BIOS copy from legacy VBIOS location (II) RADEONHD(0): ATOM BIOS Rom: SubsystemVendorID: 0x1028 SubsystemID: 0x0302 IOBaseAddress: 0xdc00 Filename: S3A67626.107 BIOS Bootup Message: 113-A67626-107 RV516 PRO DDR2 BIOS 600E/400M CHANNEL AB
Comment 1 Nicolas Bareil 2008-04-14 07:00:15 UTC
Created attachment 15903 [details] A Xorg.org of the last good commit
Comment 3 Luc Verhaegen 2008-04-14 07:07:31 UTC
Did you build from scratch in a new tarball, or did you update your existing build? If so, you should probable re-run autogen.sh as some files have been added.
Comment 4 Nicolas Bareil 2008-04-14 07:21:54 UTC
(In reply to comment #3) > Did you build from scratch in a new tarball, or did you update your existing > build? If so, you should probable re-run autogen.sh as some files have been > added. > Oh no! You're right, thank you! I'm so sorry to have waste you time! Thank you again!