On Thu, 2005-04-21 at 13:04 -0400, Joe.Hoot@itec.suny.edu wrote:
I just downloaded the fedora core test2 for ppc. I rebooted my PPC Dual G5. I was prompted by yaboot and hit enter to except the default kernel "linux." The kernel starts to load and then dies. I shutdown the machine and started it back up and at yaboot, typed linux nofb. It started to load again and then died again. Here is the output when it stops booting:
Wrong list, fedora-test-list is where this should go
opening display /pci@0,fd000000/NVDA,Parent@10/NVDA,Display-B@1... ok copying 0F device tree...done starting cpu /cpus/PowerPC,G5...failed: 0000000
Don't have a g5, but that surely looks wrong
Initializing fake screen: NVDA,Display-A Calling quiesce ... returning 0x01400000 from prom_init
Invalid memory access at SRR0: 00000000.01403b7c SRR1: 10000000.000083030
Any suggestions? Is this a problem with dual proc g5's? Is there any way to disable SMP with a kernel parameter that can be passwed?
max_cpus=1 might work. In fact, whats in there might actually be a uniprocessor kernel, because there was a bug (or still is a bug) in relation to the installation
So hit tab, and don't boot into linux (there should be another kernel there, its just not the default)
On Fri, 2005-04-22 at 09:47 +1000, Colin Charles wrote:
max_cpus=1 might work. In fact, whats in there might actually be a uniprocessor kernel, because there was a bug (or still is a bug) in relation to the installation
No, it's the ppc32 smp kernel. max_cpus=1 won't help. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=149618
* David Woodhouse dwmw2@infradead.org [2005-04-21 20:31]:
On Fri, 2005-04-22 at 09:47 +1000, Colin Charles wrote:
max_cpus=1 might work. In fact, whats in there might actually be a uniprocessor kernel, because there was a bug (or still is a bug) in relation to the installation
No, it's the ppc32 smp kernel. max_cpus=1 won't help. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=149618
I'm seeing similar behaviour to comment 9 in this bug. I installed from test2 but have been updating regularly since. I can't boot any kernels other than 'linux-up'.
/etc/yaboot.conf:
# yaboot.conf generated by anaconda
boot=/dev/sda3 init-message=Welcome to Fedora Core! Hit <TAB> for boot options
partition=5 timeout=20 install=/usr/lib/yaboot/yaboot delay=5 default=latest-smp image=/vmlinuz-2.6.11-1.1268_FC4smp label=latest-smp read-only initrd=/initrd-2.6.11-1.1268_FC4smp.img append="rhgb quiet root=LABEL=/1"
[...]
image=/vmlinuz-2.6.11-1.1226_FC4 label=linux-up read-only initrd=/initrd-2.6.11-1.1226_FC4.img append="rhgb quiet root=LABEL=/1"
macosx=/dev/sda4 magicboot=/usr/lib/yaboot/ofboot
/proc/cpuinfo: [...] motherboard: PowerMac7,3 MacRISC4 Power Macintosh detected as: 336 (PowerMac G5)
Anyone have any ideas?
Andrew
On Wed, 2005-04-27 at 16:49 -0400, Andrew Overholt wrote:
I'm seeing similar behaviour to comment 9 in this bug. I installed from test2 but have been updating regularly since. I can't boot any kernels other than 'linux-up'.
This persists even after you 'rpm -e --allmatches kernel-smp' ?
* David Woodhouse dwmw2@infradead.org [2005-04-28 02:00]:
On Wed, 2005-04-27 at 16:49 -0400, Andrew Overholt wrote:
I'm seeing similar behaviour to comment 9 in this bug. I installed from test2 but have been updating regularly since. I can't boot any kernels other than 'linux-up'.
This persists even after you 'rpm -e --allmatches kernel-smp' ?
That fixed it. Thanks!
Did I miss an FAQ somewhere?
Andrew
On Thu, 2005-04-28 at 11:16 -0400, Andrew Overholt wrote:
- David Woodhouse dwmw2@infradead.org [2005-04-28 02:00]:
On Wed, 2005-04-27 at 16:49 -0400, Andrew Overholt wrote:
I'm seeing similar behaviour to comment 9 in this bug. I installed from test2 but have been updating regularly since. I can't boot any kernels other than 'linux-up'.
This persists even after you 'rpm -e --allmatches kernel-smp' ?
That fixed it. Thanks!
Did I miss an FAQ somewhere?
Not really. It's discussed in https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=149618 though.