https://bugzilla.novell.com/show_bug.cgi?id=350212 User olh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350212#c1 Olaf Hering changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME --- Comment #1 from Olaf Hering 2008-01-04 08:25:27 MST --- boot yaboot.ibm instead of inst64 as tftp file. inst64 is now larger than 12mb and does not fit into the free memory area at 0x0000 something like this should work: cp /DVD1/suseboot/{yaboot.ibm,yaboot.cnf,inst64,yaboot.txt} /tftpboot/ mv /tftpboot/yaboot.cnf /tftpboot/yaboot.conf -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=350212 User keith@au1.ibm.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350212#c3 Keith Matthews changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | --- Comment #3 from Keith Matthews 2008-01-10 17:43:07 MST --- Hi Olaf, I followed your suggestions As you can see from the output below, we still got a read error when eventually the system attempted to load inst64. Any ideas? BOOTP: chosen-network-type = ethernet,auto,sc,auto BOOTP: server IP = 0.0.0.0 BOOTP: requested filename = BOOTP: client IP = 0.0.0.0 BOOTP: client HW addr = 0 9 6b f6 2b 36 BOOTP: gateway IP = 0.0.0.0 BOOTP: device /pci@3fffde09000/pci@b,6/ethernet@1 BOOTP: loc-code U1.9-P1-I4/E1 BOOTP: Cancel = ctl-C BOOTP R = 1 BOOTP S = 1 FILE: zImage.rego11 Load Addr=0x4000 Max Size=0x10000000 FINAL Packet Count = 819 FINAL File Size = 419122 bytes. Elapsed time since release of system processors: 4197 mins 50 secs yaboot starting: loaded at 00040000 00062848 (0/0/00c3c578; sp: 0291ffd0) brokenfirmware did not claim executable memory, fixed it myself BOOTP: chosen-network-type = ethernet,auto,sc,auto BOOTP: server IP = 0.0.0.0 BOOTP: requested filename = yaboot.conf BOOTP: client IP = 0.0.0.0 BOOTP: client HW addr = 0 9 6b f6 2b 36 BOOTP: gateway IP = 0.0.0.0 BOOTP: device /pci@3fffde09000/pci@b,6/ethernet@1 BOOTP: loc-code U1.9-P1-I4/E1 BOOTP: Cancel = ctl-C BOOTP R = 1 BOOTP S = 1 FILE: yaboot.conf Load Addr=0x3a00000 Max Size=0x10000000 FINAL Packet Count = 2 FINAL File Size = 531 bytes. Config file 'yaboot.conf' read, 531 bytes BOOTP: chosen-network-type = ethernet,auto,sc,auto BOOTP: server IP = 0.0.0.0 BOOTP: requested filename = yaboot.txt BOOTP: client IP = 0.0.0.0 BOOTP: client HW addr = 0 9 6b f6 2b 36 BOOTP: gateway IP = 0.0.0.0 BOOTP: device /pci@3fffde09000/pci@b,6/ethernet@1 BOOTP: loc-code U1.9-P1-I4/E1 BOOTP: Cancel = ctl-C BOOTP R = 1 BOOTP S = 1 FILE: yaboot.txtFINAL Packet Count = 1 Load Addr=0x3a00000 Max Size=0x10000000 FINAL File Size = 218 bytes. Welcome to openSuSE 10.3 (PPC)! Type "install" to start the YaST installer on this CD/DVD Type "slp" to start the YaST install via network Type "rescue" to start the rescue system on this CD/DVD Welcome to yaboot version 10.1.22-r1024.SuSE booted from '/pci@3fffde09000/pci@b,6/ethernet@1:000.000.000.000,,000.000.000.000,000.000.000.000,00,00' Enter "help" to get some basic usage information boot: install Please wait, loading kernel... BOOTP: chosen-network-type = ethernet,auto,sc,auto BOOTP: server IP = 0.0.0.0 BOOTP: requested filename = inst64 BOOTP: client IP = 0.0.0.0 BOOTP: client HW addr = 0 9 6b f6 2b 36 BOOTP: gateway IP = 0.0.0.0 BOOTP: device /pci@3fffde09000/pci@b,6/ethernet@1 BOOTP: loc-code U1.9-P1-I4/E1 BOOTP: Cancel = ctl-C BOOTP R = 1 BOOTP S = 1 FILE: inst64 Load Addr=0x3a00000 Max Size=0x10000000 FINAL File Size = 12566528 bytes. Allocated 00e00000 bytes for executable @ 04a00000 Read failed boot: Please wait, loading kernel... BOOTP: chosen-network-type = ethernet,auto,sc,auto BOOTP: server IP = 0.0.0.0 BOOTP: requested filename = inst64 BOOTP: client IP = 0.0.0.0 BOOTP: client HW addr = 0 9 6b f6 2b 36 BOOTP: gateway IP = 0.0.0.0 BOOTP: device /pci@3fffde09000/pci@b,6/ethernet@1 BOOTP: loc-code U1.9-P1-I4/E1 BOOTP: Cancel = ctl-C BOOTP R = 1 BOOTP S = 1 FILE: inst64 Load Addr=0x3a00000 Max Size=0x10000000 FINAL File Size = 12566528 bytes. Allocated 00e00000 bytes for executable @ 04a00000 Read failed boot: -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=350212 User olh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350212#c5 --- Comment #5 from Olaf Hering 2008-01-15 02:12:56 MST --- Created an attachment (id=190529) --> (https://bugzilla.novell.com/attachment.cgi?id=190529) x.patch debug patch -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=350212 User kmatthew@au1.ibm.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350212#c7 Keith Matthews changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kmatthew@au1.ibm.com --- Comment #7 from Keith Matthews 2008-01-15 17:23:14 MST --- Hi Olaf, I'll try to get it booted today. I spoke to Paul M & Ben H, they tell me Yaboot cannot tftp files larger than about 5M, so prehaps its this? Ben H mentioned there are ways of changing the load base from F/W when booting files too large (zImage + Initrd) for the normal one. I'll try to get more info out of him. Meanwhile I'll bring the p690 back up and try your debug yaboot. 8-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=350212 User olh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350212#c9 --- Comment #9 from Olaf Hering 2008-01-17 02:13:01 MST --- my 10.3 inst64 has a different size, 12957543: BOOTP R = 1 BOOTP S = 2 FILE: pmac/inst64-10.3 FINAL Packet Count = 25308 FINAL File Size = 12957543 bytes. load-base=0x4000 real-base=0xc00000 yaboot downloaded 00c5b767 bytes via network Allocated 00e00000 bytes for executable @ 01c00000 Elf32 kernel loaded... SuSE Linux zImage starting: loaded at 01c00000-02856cbc (40000/0/00c39c48; sp: 01a1fdd0) its still not cler why the read function failed. In case of tftp, read operates on an internal buffer. what firmware level is on the p650 and p690? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=350212 User olh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350212#c11 --- Comment #11 from Olaf Hering 2008-01-17 03:59:40 MST --- the p650 firmware prints this, which indicates that some internal tftp buffer is limited to 12mb: .. Load Addr=0x3a00000 Max Size=0x10000000 .. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=350212 User kmatthew@au1.ibm.com added comment https://bugzilla.novell.com/show_bug.cgi?id=350212#c13 --- Comment #13 from Keith Matthews 2008-01-17 17:37:15 MST --- Hi Olaf, The main p690 I have been testing on has F/W ROM Level.(alterable).......3H070425 ROM Level.(alterable).......RG070425_d79e20_regatta ROM Level.(alterable).......0000RHE11193 I have yet to test check the other p690 and my p650. But I think I had them all the same. The p650 is in my Garage at home, so I have to wait till a cool night to power it on. lol. Yep, I tested a net & DVD install on our POWER6 Model 570 MMA and it worked fine. I havn't tried Opensuse on any of the Power5's (They are all running SLES) So it looks like this may be POWER4 Regatta bug only. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.