Re: Bordeaux fails install
by Erick Calder
I tried your suggestion but get:
"Unable to read package metadata. This may be due to a missing repodata
directory. Please ensure that your install tree has been correctly
generated. Failure: repodata/primary.xml.gz from anaconda: [Errno: 256].
No more mirrors to try."
grr... what next?
> From: "Brian D. Carlstrom" <bdc(a)carlstrom.com>
> Reply-To: "Brian D. Carlstrom" <bdc(a)carlstrom.com>
> Date: Wed, 19 Apr 2006 23:44:31 -0700
> To: Erick Calder <e(a)arix.com>
> Cc: <fedora-ppc(a)lists.infradead.org>
> Subject: Bordeaux fails install
>
> Erick Calder writes:
>> I then tried a network install, in case the drive had problems. I attempted
>> an FTP-based install but with similar results.
>
> I've done a half dozen G5 DVD installs of FC5 ppc without significant
> issues (the only real one is that yaboot doesn't work on a G5 2.0GHz we
> have.
>
> I also have done two network installs, one a fresh install on ppc and
> the other an ugprade install on i386. For ppc try HTTP to
> mirrors.kernel.org:fedora/core/4/ppc/os/. In the network installs I just
> used the rescue CD.
>
> -bri
18 years
2.6.16-1.2096_FC5, kernel exception when waking up
by Charles-Edouard Ruault
Hi all,
i've just installed pmud on my powerbook and tried a sleep/resume.
I'm getting the following exception ( running the latest Fedora kernel
2.6.16-1.2096_FC5 ).
Has anyone had this problem ?
eth0: suspending, WakeOnLan disabled
radeonfb (0000:00:10.0): suspending to state: 2...
radeonfb (0000:00:10.0): resuming from state: 2...
PCI: Enabling device 0000:00:10.0 (0000 -> 0003)
PM: Writing back config space on device 0001:10:12.0 at offset 1. (Was
100000, writing 100004)
PM: Writing back config space on device 0001:10:12.0 at offset 3. (Was
0, writing 1000)
PM: Writing back config space on device 0001:10:12.0 at offset 4. (Was
0, writing a0006000)
PM: Writing back config space on device 0001:10:12.0 at offset f. (Was
100, writing 134)
PM: Writing back config space on device 0001:10:13.0 at offset 1. (Was
2100000, writing 2100007)
PM: Writing back config space on device 0001:10:13.0 at offset 3. (Was
20000, writing 2a808)
PM: Writing back config space on device 0001:10:13.0 at offset 4. (Was
0, writing a0004000)
PM: Writing back config space on device 0001:10:13.0 at offset 6. (Was
0, writing b0141110)
PM: Writing back config space on device 0001:10:13.0 at offset 7. (Was
0, writing 90000000)
PM: Writing back config space on device 0001:10:13.0 at offset 8. (Was
0, writing 9ffff000)
PM: Writing back config space on device 0001:10:13.0 at offset 9. (Was
0, writing f3000000)
PM: Writing back config space on device 0001:10:13.0 at offset a. (Was
0, writing f33ff000)
PM: Writing back config space on device 0001:10:13.0 at offset b. (Was
0, writing 1000)
PM: Writing back config space on device 0001:10:13.0 at offset c. (Was
0, writing 11fc)
PM: Writing back config space on device 0001:10:13.0 at offset d. (Was
0, writing 1400)
PM: Writing back config space on device 0001:10:13.0 at offset e. (Was
0, writing 15fc)
PM: Writing back config space on device 0001:10:13.0 at offset f. (Was
34001ff, writing 5c00135)
PCI: Enabling device 0001:10:1b.0 (0000 -> 0002)
PCI: Enabling device 0001:10:1b.1 (0000 -> 0002)
PCI: Enabling device 0001:10:1b.2 (0000 -> 0002)
PM: Writing back config space on device 0001:10:1b.2 at offset 1. (Was
2100006, writing 2100016)
usb usb4: root hub lost power or was reset
ehci_hcd 0001:10:1b.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
eth0: resuming
PHY ID: 1410cc1, addr: 0
hda: Enabling Ultra DMA 5
Badness in wait_for_ready at drivers/ide/ide-iops.c:516
Call Trace:
[C0393C40] [C0007A50] show_stack+0x54/0x184 (unreliable)
[C0393C60] [C000E574] program_check_exception+0x19c/0x520
[C0393CB0] [C000FC34] ret_from_except_full+0x0/0x4c
--- Exception: 700 at wait_for_ready+0x94/0xec
LR = wait_for_ready+0x3c/0xec
[C0393D70] [C005A01C] disable_irq_nosync+0x7c/0x90 (unreliable)
[C0393D90] [C01DF36C] pmac_ide_do_setfeature+0x108/0x320
[C0393DB0] [C01DF88C] pmac_ide_dma_check+0x308/0x490
[C0393DE0] [C01D36AC] ide_do_request+0x618/0x8cc
[C0393E50] [C01D3CF0] ide_intr+0x204/0x240
[C0393E80] [C0059CB8] handle_IRQ_event+0x54/0xa8
[C0393EA0] [C0059E10] __do_IRQ+0x104/0x188
[C0393EC0] [C00057E8] do_IRQ+0x4c/0x7c
[C0393EE0] [C000FC80] ret_from_except+0x0/0x14
--- Exception: 501 at default_idle+0x3c/0x44
LR = default_idle+0x34/0x44
[C0393FA0] [C00247E0] cpu_idle+0x3c/0x5c (unreliable)
[C0393FB0] [C0003E70] rest_init+0x28/0x38
[C0393FC0] [C0394720] start_kernel+0x19c/0x1b0
[C0393FF0] [000037A0] 0x37a0
hdc: Enabling MultiWord DMA 2
hci_usb 1-1:1.0: no resume for driver hci_usb?
hci_usb 1-1:1.1: no resume for driver hci_usb?
eth0: Link is up at 100 Mbps, full-duplex.
eth0: Pause is disabled
adb: starting probe task...
adb devices: [2]: 2 c4 [3]: 3 1 [7]: 7 1f
ADB keyboard at 2, handler 1
ADB mouse at 3, handler set to 4 (trackpad)
adb: finished probe task...
Here's my /proc/cpuinfo
processor : 0
cpu : 7447/7457, altivec supported
clock : 612.000000MHz
revision : 0.1 (pvr 8002 0101)
bogomips : 36.73
timebase : 18432000
machine : PowerBook5,2
motherboard : PowerBook5,2 MacRISC3 Power Macintosh
detected as : 287 (PowerBook G4 15")
pmac flags : 0000001b
L2 cache : 512K unified
pmac-generation : NewWorld
--
Charles-Edouard Ruault
+33 1 55 34 76 65
ce(a)idtect.com
Idtect SA
37 Bd des Capucines
75002 Paris, France
www.idtect.com
18 years
Bordeaux fails install
by Erick Calder
greetings everyone,
I've just downloaded a copy of Bordeaux, burnt the 5 disks and attempted to
upgrade my FC4 MacMini to it, reaching the disappointing message:
> The package gnome-mime-data-2.4.2-1.2.1.ppc.rpm cannot be opened. This is due
> to a missing file or perhaps a corrupt package. If you are installing from
> CD media this usually means the CD media is corrupt, or the CD drive is unable
> to read the medai.
> Press Retry to try again.
I've checked the sha1sums and did the media check before install. I tried
the install a couple of times, getting these errors on different files e.g.
bluetooth-libs-0.7.0-2.ppc.rpm, crypt* and others.
I then tried a network install, in case the drive had problems. I attempted
an FTP-based install but with similar results.
what could be wrong? what can I do?
1,000 TIA - e
18 years, 1 month
FC5 PPC, support, bugzilla and package selection.
by Brian Durant
I just wanted to say that despite there being a few outstanding issues,
like with sound for G5 machines, I have been very impressed both with
the support provided, the quick and friendly responses (even to more or
less newbies like myself) for the PPC platform from the package
maintainers through bugzilla, as well package selection for the PPC
platform, that has made me a big fan of Fedora Core 5 and makes Fedora
Core 5 my favorite distro, despite my having earlier only been
interested in .deb based distros.
Kudos to the FC PPC team!
Brian
18 years, 1 month
Switching my stock Apple keyboard in FC5.
by Brian Durant
I have purchased a stock (white) Apple USB keyboard with Danish language
layout that I would like to replace the stock (white) Apple USB keyboard
(US) keyboard that I m using now, to make it easier for me to access the
extra Danish letters in FC 5.
How do I switch the layout so that I get the Danish layout correctly
from the moment I boot in the command line, as well as in GNOME? I tried
this about 2 years ago with FC 3 on a PC and I could never get the
keyboard layout correctly from the moment I booted in the command line.
This is important if (for example) you have a problem with the GUI
freezing and have to run FC 5 from runlevel 3 to solve the problem.
What is a stock (white) Apple USB keyboard that comes with a G5 listed
as (dk, dk-latin1, etc.)?
Cheers,
Brian
18 years, 1 month
FC5 Dual Head Support
by Brian D. Carlstrom
I have have two recent G5s, one Quad 2.5GHz G5 PowerPCs and one Dual
2.7GHz G5 PowerPCs. I installed FC5 on them recently and I'm trying to
get at least one of them running dual head.
The Quad has an NVIDIA GeForce 6600. Although there was an issue with
some unreadable text during the graphical install, things are fine post
installation with an increased color depth. From what I read, one head
is as good as it will get. That is, the nv driver will not support dual
head and there is no way to use something like fbdev to run two heads on
one nv card. If someone could confirm this, I would appreciate it.
The Dual has an ATI Radeon 9600T. Under FC4, I'm pretty sure we had the
"radeon" driver working, but regrettably I didn't save the xorg.conf
file. Graphic install would not work and after fighting with all day, we
have it running with the fbdev drivier. Basically we ended up running
the YDL 4.1 install disk and looking at the xorg configuration file they
used to get the graphical installer running.
However, I am assuming that I can't run dual head with fbdev, so now I'm
stuck. If I try to run with the "radeon" driver, the machine hangs. not
just no video, which I've had before with inproper monitor settings, but
complete death as it stops responding to ping and I can't ssh login or
ctrl-alt-del the machine. This seems to be a problem with the "radeon"
driver in xorg 7.0.0, as discussed here:
https://launchpad.net/distros/ubuntu/+source/xserver-xorg-driver-ati/+bug...
Anyone out there have dual head working with a PowerMac G5 Desktop and
FC5? I have some older machines I could try if anyone has it working on
a slightly different box.
-bri
18 years, 1 month
