Following up on suggestions by people in this forum, I:
(1) updated my Radeon 9200 ATI ROM to the newest available (ATI
4.5.1, ROM ATY, Bugsy_A, FCode Version 1.94, NDRV version 1.0.1f59)
(2) started using Rawhide and updating from the development tree.
The result of starting over from a local rsync of Rawhide was that I
was finally able to get LVM2 working the way I had always wanted.
(Yeah!). Unfortunately, X is still not working. The ATI ROM
update actually seems to have made the situation a little worse.
1. Locally rsynced Rawhide and burned the rawhide boot CD from June
2. Installed system, was not able to get X to work. Ran it this way
a few days. (reboots did not hang, see below)
3. Updated to the newest Radeon ROM via a Mac OS X partition on the
4. Rebooted to Rawhide, but now it hangs during boot with the message:
"PCI: Cannot allocate resource region 1 of device
0001:11:02.0" (this is in fact the address of the ATI Radeon.)
I get the same thing using the Rawhide boot CD from June 18. I
didn't when I installed with it, however.
The message comes directly after the penguin images appears on the
screen and is the only thing else appearing on the screen. The
only sure fire way of getting the boot sequence not to hang at this
message every time is to use the kernel option "debug". It appears
"video=ofonly" sometimes, but not always works, but I have yet to see
"debug" fail. Specifically, the kernels I have had to use this
workaround against are: Kernel 2.6.11-1.1381_FC5, Fedora Core release
4 (Stentz) and Kernel 2.6.12-1.1411_F. In the case of the latter
kernel, if I use both "video=ofonly" and "debug" it hangs at "IN
bad port 3f9 at c01e2758". Using only "debug" gets me beyond this.
I went back and retested the special X11 CD-ROM (Jeremy Katz). If I
add the options "video=radeonfb" or if I instead use "video=ofonly" I
get the same result.
ATI Radeon 9200
Studio Dsply 1
Generic 3 Button Mouse (PS/2)
X server started successfully
mini-wm: Fatal IO error 104.
However, looking the the logs I see the X server appears to have
EE Failed to load module "glx"
(module does not exist, 0)
EE Failed to load module "record"
(module does not exist, 0)
The Rawhide boot CD from June 18 gives the above PCI resource region
error if I use video=radeonfb. It sometimes moves forward with
video=ofonly and always makes it with debug.
For what it is worth, the Gentoo 2005.0 CD hangs with the same PCI
resource region error. The Ubuntu LiveCD of 2005-07-04 (5.04 "Hoary
Hedgehog") not only gives no PCI error, but also gives me a nice X
screen that fills the entire display. I also got LVM to work on the
first try with it.
In any event, my goal is to get Fedora running, so since the Ubuntu
folks can do it, I'm sure you guys can too.
Where does one report their finding with PPC Rawhide? <https://
If I want X, is it more advisable to go to the regular Core
release? I don't mind living with some instability, as long as I
might eventually get X.
On Jun 8, 2005, at 4:13 PM, Paul Nasrat wrote:
On Wed, 2005-06-08 at 15:48 +0200, Mike Hammill wrote:
> Dear Paul,
> On Sun, 2005-06-05 at 23:06, Paul Nasrat wrote:
>> Could you try a later boot cd of rawhide, or verify against FC4
> It might have been a bit lost in my previous pst, but I did test it
> against FC4 test 3 (iso files dated May 26, 2005). The system itself
> reports "Fedora Core release 3.9.2 (Pre-FC4)"/"kernel
> 2.6.11-1.1286_FC4". I have steered clear of rawhide because I was
> the impression that the only safe way to install it was rsyncing
> it to a
> NFS server then netbooting, which is unfortunately beyond my
> resources to try. Is the boot image you're suggesting "boot.iso"
> If so, it appears to be from 8 June 2005.
If you have large enough b/w you can do a http install off a local-ish
mirror to you. It is probably best at this stage to test with FC4
>> Hmm what happens if you boot with offb to use OF fb rather than
> To try this is it correct that I change yaboot.conf to contain:
> append="video=offb"? I read that using the OF framebuffer
> disables the
> radeonfb and also gives one a slower driver. Is that the idea behind
> the test?
video=ofonly and you can just type it on the yaboot line rather than
edit yaboot.conf - try with eg:
linux video=ofonly debug
>> Please file a bug so things get tracked.
> OK, I'll try to get to it. Might take a few days. Thanks for the