As Peter suggested I post here a PPC question.I have a cube Apple g4, where I can t start installation.It starts till probing hardware, but when tries modprobing sbp2 gives to me a Uncoverable machine check, kernel panic. It s not a hardware issues ,Tiger is fine on the machine, recently I booted from 10.0 suseboot and it s fine too.This issues appeared since beta version of 10.1. Somebody has a suggestion how to working out?
On Mon, Mar 20, andrea wrote:
As Peter suggested I post here a PPC question.I have a cube Apple g4, where I can t start installation.It starts till probing hardware, but when tries modprobing sbp2 gives to me a Uncoverable machine check, kernel panic. It s not a hardware issues ,Tiger is fine on the machine, recently I booted from 10.0 suseboot and it s fine too.This issues appeared since beta version of 10.1. Somebody has a suggestion how to working out?
Try to blacklist the module, boot with either install brokenmodules=ieee1394 or install brokenmodules=sbp2
Try to blacklist the module, boot with either
install brokenmodules=ieee1394
or
install brokenmodules=sbp2
Thanks Olaf, I tried but same result. I tried brokenmodules=ieee1394, borkenmodules=sbp2 but they didn t work , same kernel panic not syncing unrecoverable machine check. I ll wait for a different kernel version more suitable for my machine. Andrea
Alle 01:20, martedì 21 marzo 2006, andrea ha scritto:
Try to blacklist the module, boot with either
install brokenmodules=ieee1394
or
install brokenmodules=sbp2
Thanks Olaf, I tried but same result. I tried brokenmodules=ieee1394, borkenmodules=sbp2 but they didn t work , same kernel panic not syncing unrecoverable machine check. I ll wait for a different kernel version more suitable for my machine.
the problem is that it loads the modules anyway , yaboot seems doesn t care of brokenmodules Andrea
On Tue, Mar 21, andrea wrote:
I tried brokenmodules=ieee1394, borkenmodules=sbp2 but they didn t work , same kernel panic not syncing unrecoverable machine check. I ll wait for a different kernel version more suitable for my machine.
Ok, then it is not firewire but something else. can you boot with 'install linuxrcstderr=/dev/console' to see how far linuxrc gets?
Ok, then it is not firewire but something else. can you boot with 'install linuxrcstderr=/dev/console' to see how far linuxrc gets?
Are you sure? I checked before too linuxrc with alt ctrl f3 to see the console output. insmod module usb .storage done insmod module ieee1394 insmod module ochi1394 ................. kernel panic mon no output that s all ( I tried to write out the last messages) Andrea
Alle 01:20, martedì 21 marzo 2006, andrea ha scritto:
Try to blacklist the module, boot with either
install brokenmodules=ieee1394
or
install brokenmodules=sbp2
Now is magically working, I download suseboot folder from factory, and booted from there, install brokenmoules=ieee1394 works now good. Ican load intallation system but I have now a media error no proposal but may be this is a factory issues. Thanks again Olaf fro your attention Andrea
On Tue, Mar 21, andrea wrote:
Alle 01:20, martedì 21 marzo 2006, andrea ha scritto:
Try to blacklist the module, boot with either
install brokenmodules=ieee1394
or
install brokenmodules=sbp2
Now is magically working, I download suseboot folder from factory, and booted from there, install brokenmoules=ieee1394 works now good. Ican load intallation system but I have now a media error no proposal but may be this is a factory issues.
I think its ok if you just pick the kernel. (aka initrd32+linux32.gz or inst32) Unfortunately, there was a incompatible change after beta7. A beta8+ install initrd can not be used with beta7 CDs. Did beta8 work ok for you, or was it also broken? Are you saying that brokenmodules=ieee1394 is still required?
I think its ok if you just pick the kernel. (aka initrd32+linux32.gz or inst32) Unfortunately, there was a incompatible change after beta7. A beta8+ install initrd can not be used with beta7 CDs. Did beta8 work ok for you, or was it also broken? Are you saying that brokenmodules=ieee1394 is still required?
I forgot to mention that I m trying a network installation through ftp server. I suppose the factory tree is now 8+, and booting from that inst32 related still require brokenmodules=ieee1394. The incredible is that random , but not so often from beta6, it boots fine and panics after 2 or 3 times you turn on the computer with the installed system. Im upgrading from alpha1 , but it s from alpha4 that I encountered the first kernel panic on ieee1394, in the same time the kernel version changed from 2.6.14 to 2.6.15, and 2.6.16 now. May be I need to download beta 8 cd's and give them a try or I ll wait till RC1 . Andrea
participants (2)
-
andrea -
Olaf Hering