Since Fedora 9 my Radeon HD 2400 Pro (RV610) doesn't work anymore. I cant start initlevel 5. If the xorg-xserver gets started i only see a defect image of the rhgb. a few seconds later my fedora 9 machine reboots. i already tried the radeon and the radeonhd xorg driver. i have attached some log files.
Created attachment 308647 [details] xorg log file
Created attachment 308648 [details] dmesg log file
Created attachment 308649 [details] messages log file
I figured out, that this problem is only available with 4gb of ram if i remove 1 ram brick it works (with 2gb ram) without problem. this problem wasnt available on fedora 8
this bug looks very similar should we close one? https://bugzilla.redhat.com/show_bug.cgi?id=450247
Although they both seem related to 4GB memory, on my machine with the intel driver it crashes xorg, yours with the radeon driver reboots the machine (kernel panic?) I'd rather see some comment from ajax and/or airlied before closing either of them.
I found out something more about this problem. could this be an mtrr problem? i have attached a dmesg file and my gdm log in both there are mtrr problems like: error setting MTRR (base = 0xf0000000, size = 0x08000000, type = 1) Invalid argument (22)
Created attachment 309033 [details] gdm log file
Created attachment 309035 [details] dmesg log file
i found a solution for my problem. i dont know if this is a nice idea... i disabled the memory remap feature in my motherboard bios. ofter that my ati radeon 2400 pro works
can you check with your motherboard vendor if they have an updated BIOS for your motherboard. I've heard of a few problems with the memory remap and some people mentioned BIOs upgrades fixed them.
i have a asus p5k motherboard with the latest bios 1006. the strange thing is, that it worked perfect with my fedora 8 system. is disabling memory remap function a bad idea? or should i use the x64 version on fedora 9 with my system? i have 4gb ram and 256mb ram on my ati card
Just a "me too". I have 4gb RMAN, F9 x86_64 with the Radeon HD 2400 Pro, and I can only use the vesa driver. Let me know if I can provide other information.
ugh, that should be "4gb RAM", not "4gb RMAN". Too much time around Oracle.
i have this problems only with 32bit fedora, but if i disable memory remapping it also works. now i switched to x86_64 and the radeon card also works with enabled memory remapping.
Also an FYI that I actually was chatting with airlied in #radeon last night and he suggested a file a bug at bugs.freedesktop.org, which I did. https://bugs.freedesktop.org/show_bug.cgi?id=16768
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.