Opened 17 years ago
Closed 15 years ago
#2275 closed bug (fixed)
Radeon driver GCC4 issues.
| Reported by: | euan | Owned by: | euan |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Drivers/Graphics/radeon | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | x86 |
Description
Radeon driver fails to run when built with GCC4. Bad stuff happens, and darkness is final outcome.
Log to follow.
Attachments (5)
Change History (9)
by , 17 years ago
| Attachment: | radeon.serial.log added |
|---|
comment:1 by , 17 years ago
FYI, the system itself appears to be running OK...keyboard is responding to numlock, I can ping, etc., it's just the display that's in an invalid mode.
Let me know what else I can do to help debug.
by , 17 years ago
| Attachment: | serial.gcc4.0529.log added |
|---|
Updated log with higher Radeon debugging on.
by , 16 years ago
| Attachment: | radeon.gcc4.i2c-spin.debug.log added |
|---|
Next log with debug tracing added to i2c.c's spin() implementation to ensure gcc4 wasn't optimizing it out somehow,
comment:2 by , 16 years ago
Based on banging on things all weekend, I think it's possible we might be looking at the wrong problem...one of the recent changes in the tree caused whatever mode EDID detected during boot to be written to the app_server_settings file immediately to prevent a mode switch, which in turn short circuits the radeon's monitor detection routines...however, I still end up with the same invalid signal to the monitor. At this point I'm starting to think something's going wrong with the kernel driver's setup of things, since I also tried forcing the routines that query the BIOS for the connector types to force DVI, and that also made no difference.
comment:3 by , 16 years ago
| Status: | new → assigned |
|---|
It must be an i2c issue IMHO. it works in GCC2 and fails in gcc4.
Serial log from radeon error