[opensuse-ppc] Booting openSUSE-NET-ppc-Build0003-Media.iso
Hi there, just a few words how to boot current factory on PowerMac. I tried it on a 1,6GHz PowerMac G5. 1. Power on your PowerMac ;) 2. Get to Open Firmware with "Alt-Option-O-F" keys pressed 3. Insert openSUSE-NET-ppc CD by ejecting CD-ROM drive with command "eject cd" 4. Boot into yaboot by entering "boot cd:,\suseboot\yaboot" 5. Choose your Installation-Type
From there I was able to go through installation pre-configuration setup (network, http-server) and YaST2 started. But it crashed when I tried to do partitioning stuff.
Maybe someday I'll have the knowledge to be able to fix things for PPC... Have fun! Wolfgang -- View this message in context: http://opensuse.14.n6.nabble.com/Booting-openSUSE-NET-ppc-Build0003-Media-is... Sent from the opensuse-ppc mailing list archive at Nabble.com. -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On Sat, Feb 18, 2012 at 10:47 PM, Wolfgang Engel <wengel@suse.de> wrote:
Hi there, Hey,
just a few words how to boot current factory on PowerMac. I tried it on a 1,6GHz PowerMac G5.
1. Power on your PowerMac ;) 2. Get to Open Firmware with "Alt-Option-O-F" keys pressed 3. Insert openSUSE-NET-ppc CD by ejecting CD-ROM drive with command "eject cd" 4. Boot into yaboot by entering "boot cd:,\suseboot\yaboot" 5. Choose your Installation-Type
From there I was able to go through installation pre-configuration setup (network, http-server) and YaST2 started. But it crashed when I tried to do partitioning stuff. I'll try to install it on pSeries machine. And will see if I can reproduce this issue. Maybe even the bug is not architecture specific.
Maybe someday I'll have the knowledge to be able to fix things for PPC...
Thanks for the testing.
Have fun!
Wolfgang
-- View this message in context: http://opensuse.14.n6.nabble.com/Booting-openSUSE-NET-ppc-Build0003-Media-is... Sent from the opensuse-ppc mailing list archive at Nabble.com. -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
Installation without using partitioner dialog in YaST2 works. I used minimal package selection. I'm trying to do more testing. Regards, Wolfgang -- View this message in context: http://opensuse.14.n6.nabble.com/Booting-openSUSE-NET-ppc-Build0003-Media-is... Sent from the opensuse-ppc mailing list archive at Nabble.com. -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On Sat, Feb 18, 2012 at 5:19 PM, Wolfgang Engel <wengel@suse.de> wrote:
Installation without using partitioner dialog in YaST2 works. I used minimal package selection. I'm trying to do more testing.
Back when 10.0 was in beta, there were issues with partitioning mac drives with YaST. You should be able to start a rescue system and use "pdisk" to partition a MacOS drive if you need to(didn't know if you knew that). Then you will have to reboot and restart the install. If you aren't familiar with MacOS partitioning, be careful. You need a 32MB ProDOS type partition for yaboot. Anyway, I have a PowerMac G4/Digital Audio(466Mhz) & an iBook G3/366Mhz. Will try them out. Overall, how do you find the current factory to run on the G5? -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On 19/02/12 02:02, Larry Stotler wrote:
On Sat, Feb 18, 2012 at 5:19 PM, Wolfgang Engel<wengel@suse.de> wrote:
Installation without using partitioner dialog in YaST2 works. I used minimal package selection. I'm trying to do more testing.
Back when 10.0 was in beta, there were issues with partitioning mac drives with YaST. You should be able to start a rescue system and use "pdisk" to partition a MacOS drive if you need to(didn't know if you knew that).
Then you will have to reboot and restart the install.
If you aren't familiar with MacOS partitioning, be careful. You need a 32MB ProDOS type partition for yaboot.
Anyway, I have a PowerMac G4/Digital Audio(466Mhz)& an iBook G3/366Mhz. Will try them out.
Overall, how do you find the current factory to run on the G5?
Larry, Thanks for the reminder about partitioning. I'm keen to try this out on my old G5, but I can't work out where the files are. Nothing obvious at http://software.opensuse.org nor http://download.opensuse.org/ So, please can someone tell me where the latest NET iso is available from? Also, where do we need to point the installation to for it to find PPC factory (or does it default to the appropriate place)? (Is this what Larry's final line is asking?) Finally if I may a third question: I'm think it might be worth grabbing the entire repo with rsync? (not sure how big it is) - if so what is the URL? -- Cheers Richard (MQ) Linux user # 439271 -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On 2/20/12, Richard (MQ) <osl2008@googlemail.com> wrote:
Thanks for the reminder about partitioning. I'm keen to try this out on my old G5, but I can't work out where the files are. Nothing obvious at http://software.opensuse.org nor http://download.opensuse.org/
it was moved to: powerpc.opensuse.org you can also partition under MacOS as well.
So, please can someone tell me where the latest NET iso is available from? Also, where do we need to point the installation to for it to find PPC factory (or does it default to the appropriate place)? (Is this what Larry's final line is asking?)
powerpc.opensuse.org/factory/iso/
Finally if I may a third question: I'm think it might be worth grabbing the entire repo with rsync? (not sure how big it is) - if so what is the URL?
powerpc.opensuse.org/factory/repo/oss/ -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On Mon, Feb 20, 2012 at 4:05 PM, Larry Stotler <larrystotler@gmail.com> wrote:
powerpc.opensuse.org/factory/repo/oss/
does anyone know why this isn't also available from ftp? I can't figure out how to pull the repo with wget on http. keep getting a failure. -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On 21/02/12 06:52, Larry Stotler wrote:
On Mon, Feb 20, 2012 at 4:05 PM, Larry Stotler<larrystotler@gmail.com> wrote:
powerpc.opensuse.org/factory/repo/oss/
does anyone know why this isn't also available from ftp? I can't figure out how to pull the repo with wget on http. keep getting a failure.
I can't connect using ftp either (resolves OK but then times out), but rsync seems to be working (once I worked out the syntax): $ rsync powerpc.opensuse.org::opensuse/ppc/factory/repo/oss/ drwxr-xr-x 912 2012/02/21 19:04:10 . -rw-r--r-- 24494754 2012/02/19 00:08:45 ARCHIVES.gz -rw-r--r-- 10966767 2012/02/18 23:52:37 ChangeLog -rw-r--r-- 17996 2012/02/06 19:27:09 GPLv2.txt -rw-r--r-- 35147 2012/02/06 19:27:09 GPLv3.txt ... -- Cheers Richard (MQ) Linux user # 439271 -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
Hi, I used parted to do the partitioning before installation, which I was not aware of that it is able to do so now. Thanks for pointing me to pdisk, this would have helped me too. After installation the system does not boot properly because it got stuck in the startup process. I need to do more investigation at which point excactly it runs into problems. The rescue system runs fine. There you can do all the pre-work like partitioning or even get into your installed system to modify files. Regards, Wolfgang On 02/20/2012 10:05 PM, Larry Stotler wrote:
On 2/20/12, Richard (MQ)<osl2008@googlemail.com> wrote:
Thanks for the reminder about partitioning. I'm keen to try this out on my old G5, but I can't work out where the files are. Nothing obvious at http://software.opensuse.org nor http://download.opensuse.org/ it was moved to:
powerpc.opensuse.org
you can also partition under MacOS as well.
So, please can someone tell me where the latest NET iso is available from? Also, where do we need to point the installation to for it to find PPC factory (or does it default to the appropriate place)? (Is this what Larry's final line is asking?) powerpc.opensuse.org/factory/iso/
Finally if I may a third question: I'm think it might be worth grabbing the entire repo with rsync? (not sure how big it is) - if so what is the URL? powerpc.opensuse.org/factory/repo/oss/
-- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On 20/02/12 21:05, Larry Stotler wrote:
On 2/20/12, Richard (MQ)<osl2008@googlemail.com> wrote:
Thanks for the reminder about partitioning. I'm keen to try this out on my old G5, but I can't work out where the files are. Nothing obvious at http://software.opensuse.org nor http://download.opensuse.org/
it was moved to:
powerpc.opensuse.org ... OK, thanks - I'm testing behind a firewall, so I have cloned the repo using
rsync -avz --delete powerpc.opensuse.org::opensuse/ppc/factory/repo/oss/ . and made it available on a local ftp server. Booting NET ISO (build 0003) still (*) fails with "Insert CD number 1" but backing up to the configuration and specifying network install parameters (to local the server) loads the images and starts YaST. Yay! (*) This also occurred with OSL 11.0, previously run on this box. Same work-around. However: 2 problems immediately bite me. (NB the text that follows was transcribed manually and in a hurry, so may not be accurate, but the gist is there) Problem (1): SHA1 sum error: ftp://.../oss/boot/ppc/config Continue (Y/N). I said Y... Is this just me (maybe a corrupted image, but rsync is good at not doing that and was used for both transfers) or is it a bug? Problem (2): YaST then reports no hard disc, and getting a console with Alt-F2 and running "fdisk -l" confirms this. I assume the necessary module is not being loaded, but how do I find which one? I may be able to run OSL 11.0 again to see what it loads, if I can find the Hard Disc - or at least a gzipped image to create one. Sounds like a bug unless caused by (1) - I wonder if it's worth creating one in bugzilla? Hardware is a G3 "New world" iMac from 1999 (the iconic translucent blue model) ("G5" in my earlier message was a typo). 512M RAM, 333 MHz PPC CPU. I also have somewhere a MacBook from the same era, will try that too when I have time. -- Cheers Richard (MQ) Linux user # 439271 -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On Thu, Feb 23, 2012 at 2:29 PM, Richard (MQ) <osl2008@googlemail.com> wrote:
Booting NET ISO (build 0003) still (*) fails with "Insert CD number 1" but backing up to the configuration and specifying network install parameters (to local the server) loads the images and starts YaST. Yay! (*) This also occurred with OSL 11.0, previously run on this box. Same work-around.
Yeah, evidently since there's no media it fails. There's probably a way to set it up from the boot, but I don't remember how, and like you said the work around does get you started.
Problem (1): SHA1 sum error: ftp://.../oss/boot/ppc/config Continue (Y/N). I said Y... Is this just me (maybe a corrupted image, but rsync is good at not doing that and was used for both transfers) or is it a bug?
More than likely it is the test of the package that is failing. I had an issue with that with the older 10.x systems with a lot of MD5 errors on the packages from the CDs. It could be that there is a problem with the RAM, which is what I think was wrong with mine. However, I could usually skip enough to get a bootable system and fix it then. Try doing a minimal install just to get a working system and then add in what you need/want. That will also help narrow down where we have broken packages.
Problem (2): YaST then reports no hard disc, and getting a console with Alt-F2 and running "fdisk -l" confirms this. I assume the necessary module is not being loaded, but how do I find which one? I may be able to run OSL 11.0 again to see what it loads, if I can find the Hard Disc - or at least a gzipped image to create one. Sounds like a bug unless caused by (1) - I wonder if it's worth creating one in bugzilla?
Are you sure there's a disk in it? You should use pdisk to partition, not fdisk. fdisk should still see the drive but it will be empty. Try: pdisk -l /dev/sda or pdisk -l /dev/hda IIRC some machines still show the drives as IDE with the /dev/hdx When the installer fails, you should have access to system information or something to see whether linux is recognizing your drive.
Hardware is a G3 "New world" iMac from 1999 (the iconic translucent blue model) ("G5" in my earlier message was a typo). 512M RAM, 333 MHz PPC CPU. I also have somewhere a MacBook from the same era, will try that too when I have time.
It would be a PowerBook from that era. MacBooks are Intel based. Just make sure it's not an Old World Mac. Those won't boot from CD like the newer Colored Macs. I don't have a fast enough internet connection to do an install so I haven't had time to test it yet. I DID grab the Fedora 16 PPC install DVD and hop to try it out next week when I have time. -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On 23/02/12 20:21, Larry Stotler wrote:
On Thu, Feb 23, 2012 at 2:29 PM, Richard (MQ)<osl2008@googlemail.com> wrote:
Booting NET ISO (build 0003) still (*) fails with "Insert CD number 1" but backing up to the configuration and specifying network install parameters (to local the server) loads the images and starts YaST. Yay! (*) This also occurred with OSL 11.0, previously run on this box. Same work-around.
Yeah, evidently since there's no media it fails. There's probably a way to set it up from the boot, but I don't remember how, and like you said the work around does get you started.
:-)
Problem (1): SHA1 sum error: ftp://.../oss/boot/ppc/config Continue (Y/N). I said Y... Is this just me (maybe a corrupted image, but rsync is good at not doing that and was used for both transfers) or is it a bug?
More than likely it is the test of the package that is failing. I had an issue with that with the older 10.x systems with a lot of MD5 errors on the packages from the CDs. It could be that there is a problem with the RAM, which is what I think was wrong with mine. However, I could usually skip enough to get a bootable system and fix it then. Try doing a minimal install just to get a working system and then add in what you need/want. That will also help narrow down where we have broken packages.
I think the RAM & other hardware is OK - OS-X boots as expected. I just realised that I can check the file SHA1 sum on the server - I'll do that in the morning. Not sure how many people are on this list, I assume no-one else sees the error but is that because no-one is testing? Or is the sum wrong on the repo?
Problem (2): YaST then reports no hard disc, and getting a console with Alt-F2 and running "fdisk -l" confirms this. I assume the necessary module is not being loaded, but how do I find which one? I may be able to run OSL 11.0 again to see what it loads, if I can find the Hard Disc - or at least a gzipped image to create one. Sounds like a bug unless caused by (1) - I wonder if it's worth creating one in bugzilla?
Are you sure there's a disk in it? You should use pdisk to partition, not fdisk. fdisk should still see the drive but it will be empty.
My bad. But there is an HD - it boots OS-X just fine. So "fdisk -l" should at least report it, as should pdisk. Will try the latter tomorrow. Looks to me like a missing module - I need that OSL 11.0 HD
IIRC some machines still show the drives as IDE with the /dev/hdx
I'll check this, but "pdisk -l" alone (no device specifier) should list all devices (subject to driver modules), no?
Hardware is a G3 "New world" iMac from 1999 (the iconic translucent blue model) ("G5" in my earlier message was a typo). 512M RAM, 333 MHz PPC CPU. I also have somewhere a MacBook from the same era, will try that too when I have time.
It would be a PowerBook from that era. MacBooks are Intel based. Just make sure it's not an Old World Mac. Those won't boot from CD like the newer Colored Macs.
Again, my bad. I think it's a Powerbook ("Lombard" G3, with a dodgy keyboard IIRC).
I don't have a fast enough internet connection to do an install so I haven't had time to test it yet.
rsync is your friend! repo is around 10G at the moment.
I DID grab the Fedora 16 PPC install DVD and hop to try it out next week when I have time.
Is that easy to find on their site? I'd appreciate a link if not. -- Cheers Richard (MQ) Linux user # 439271 -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On Thu, Feb 23, 2012 at 3:48 PM, Richard (MQ) <osl2008@googlemail.com> wrote:
I think the RAM & other hardware is OK - OS-X boots as expected. I just realised that I can check the file SHA1 sum on the server - I'll do that in the morning. Not sure how many people are on this list, I assume no-one else sees the error but is that because no-one is testing? Or is the sum wrong on the repo?
Hard to tell. Unfortunately, interest in PPC died when the devs decided to drop support with 11.2, and didn't tell anyone untill 11.2 was released. I didn't have the ability to beta test for that release so I didn't find out until it was too late to try to make a difference. should still see the drive but it will be empty.
My bad. But there is an HD - it boots OS-X just fine. So "fdisk -l" should at least report it, as should pdisk. Will try the latter tomorrow. Looks to me like a missing module - I need that OSL 11.0 HD
ftp://ftp5.gwdg.de/pub/opensuse/discontinued/distribution/11.0/iso/cd/openSUSE-11.0-NET-ppc.iso ftp://ftp5.gwdg.de/pub/opensuse/discontinued/distribution/11.0/iso/dvd/openSUSE-11.0-DVD-ppc.iso
I'll check this, but "pdisk -l" alone (no device specifier) should list all devices (subject to driver modules), no?
Far as I know. However, I was under the impression that the newer versions defaulted to /dev/sda and that if you had a cd, it would try to open it instead(ran into that a few times). Hard to tell.
Again, my bad. I think it's a Powerbook ("Lombard" G3, with a dodgy keyboard IIRC).
If you are in need of one, the LowEndMac swap list is a good resource.
Is that easy to find on their site? I'd appreciate a link if not.
ftp://mirror.aarnet.edu.au/pub/fedora-secondary/releases/16/Fedora/ppc/iso/Fedora-16-ppc-DVD.iso ftp://mirror.aarnet.edu.au/pub/fedora-secondary/releases/16/Fedora/ppc/iso/Fedora-16-ppc-netinst.iso Unfortunately, it's probably in a similar state as our factory. They are focusing on 64bit, & the 32bit version is pretty much untested, so YMMV. -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
Am 23.02.2012 20:29, schrieb Richard (MQ):
Booting NET ISO (build 0003) still (*) fails with "Insert CD number 1" but backing up to the configuration and specifying network install parameters (to local the server) loads the images and starts YaST. Yay! [...] Problem (1): SHA1 sum error: ftp://.../oss/boot/ppc/config Continue (Y/N). I said Y... Is this just me (maybe a corrupted image, but rsync is good at not doing that and was used for both transfers) or is it a bug?
I'm seeing that too using HTTP powerpc.opensuse.org /factory/repo/oss/. Same if I try to enter rescue mode. Hardware is an IBM IntelliStation 9111-285 (POWER5). I've tried letting it partition the disks with btrfs and then get stuck in an endless loop that keeps asking me if I want to ignore a missing checksum: <<< Installation - Vorbereitung Keine Prüfsumme gefunden Es wurde keine Prüfsumme für Datei /var/tmp/TmpDir.HiC8oc/suse/setup/slide/txt in dem Repository gefunden. Dies bedeutet, dass die Datei Teil des signierten jedoch nicht in der Liste der Prüfsummen in diesem Repository erwähnt wird. Du kann die Integrität des Systems gefährdet werden. Trotzdem verwenden? [ ] Diese Meldung nicht erneut zeigen [Ja] [Nein]
Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
Am 23.02.2012 21:54, schrieb Andreas Färber:
Am 23.02.2012 20:29, schrieb Richard (MQ):
Booting NET ISO (build 0003) still (*) fails with "Insert CD number 1" but backing up to the configuration and specifying network install parameters (to local the server) loads the images and starts YaST. Yay! [...] Problem (1): SHA1 sum error: ftp://.../oss/boot/ppc/config Continue (Y/N). I said Y... Is this just me (maybe a corrupted image, but rsync is good at not doing that and was used for both transfers) or is it a bug?
I'm seeing that too using HTTP powerpc.opensuse.org /factory/repo/oss/.
Same if I try to enter rescue mode.
Is the following WARNING expected in rescue mode? It appeared to hang after the last line but maybe I was just too impatient... Rescue:~ # reboot WARNING: could not determine runlevel - doing soft reboot (it's better to use shutdown instead of reboot from the command line) Broadcast message from root@Rescue (console) (Thu Feb 23 18:51:21 2012): The system is going down for reboot NOW! INIT: Switching to runlevel: 6 INIT: Sending processes the TERM signal INIT: Sending processes the KILL signal Boot logging started on /dev/hvc0(/dev/console) at Thu Feb 23 18:51:27 2012 Master Resource Control: previous runlevel: 3, switching to runlevel:6 Master Resource Control: Running /etc/init.d/before.local done Saving random seed done Shutting down syslog services done Shutting down D-Bus daemon done Shutting down (remotefs) network interfaces: Shutting down service (remotefs) network . . . . . . . . . done Shutting down (localfs) network interfaces: eth0 device: Intel Corporation 82546GB Gigabit Ethernet Co No configuration found for eth0 Nevertheless the interface will be shut down. done eth1 device: Intel Corporation 82546GB Gigabit Ethernet Co No configuration found for eth1 Nevertheless the interface will be shut down. done Shutting down service (localfs) network . . . . . . . . . done Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On 23/02/12 20:54, Andreas Färber wrote:
Am 23.02.2012 20:29, schrieb Richard (MQ):
Problem (1): SHA1 sum error: ftp://.../oss/boot/ppc/config Continue (Y/N). I said Y... Is this just me (maybe a corrupted image, but rsync is good at not doing that and was used for both transfers) or is it a bug?
I'm seeing that too using HTTP powerpc.opensuse.org /factory/repo/oss/.
I think we must assume this is a bug - see https://bugzilla.novell.com/show_bug.cgi?id=748706 I thought the SHA1 sums were kept in ARCHIVES.gz but no find relevant matches there to "config". Or is that why it says the sum fails? -- Cheers Richard (MQ) Linux user # 439271 -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On Thu, Feb 23, 2012 at 09:57:57PM +0000, Richard (MQ) wrote:
On 23/02/12 20:54, Andreas Färber wrote:
Am 23.02.2012 20:29, schrieb Richard (MQ):
Problem (1): SHA1 sum error: ftp://.../oss/boot/ppc/config Continue (Y/N). I said Y... Is this just me (maybe a corrupted image, but rsync is good at not doing that and was used for both transfers) or is it a bug?
I'm seeing that too using HTTP powerpc.opensuse.org /factory/repo/oss/.
I think we must assume this is a bug - see https://bugzilla.novell.com/show_bug.cgi?id=748706
I thought the SHA1 sums were kept in ARCHIVES.gz but no find relevant matches there to "config". Or is that why it says the sum fails?
It comes from /content /content has now SHA256 sums, but I think the part that evaluates this is not yet updated from SHA1 to SHA256 support. (I think its linuxrc, need to check). Ciao, Marcus -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
Hi, I managed to install Factory on pSeries power5 machine. using PReP partition (type 41) and ext3 for root. It seems booting is broken somewhere around FAT16 partition creation. As SMS doesn't sees it, but should. On Fri, Feb 24, 2012 at 5:20 PM, Marcus Meissner <meissner@suse.de> wrote:
On Thu, Feb 23, 2012 at 09:57:57PM +0000, Richard (MQ) wrote:
On 23/02/12 20:54, Andreas Färber wrote:
Am 23.02.2012 20:29, schrieb Richard (MQ):
Problem (1): SHA1 sum error: ftp://.../oss/boot/ppc/config Continue (Y/N). I said Y... Is this just me (maybe a corrupted image, but rsync is good at not doing that and was used for both transfers) or is it a bug?
I'm seeing that too using HTTP powerpc.opensuse.org /factory/repo/oss/.
I think we must assume this is a bug - see https://bugzilla.novell.com/show_bug.cgi?id=748706
I thought the SHA1 sums were kept in ARCHIVES.gz but no find relevant matches there to "config". Or is that why it says the sum fails?
It comes from /content
/content has now SHA256 sums, but I think the part that evaluates this is not yet updated from SHA1 to SHA256 support.
(I think its linuxrc, need to check).
Ciao, Marcus -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
Am 23.02.2012 21:54, schrieb Andreas Färber:
Hardware is an IBM IntelliStation 9111-285 (POWER5). I've tried letting it partition the disks with btrfs and then get stuck in an endless loop that keeps asking me if I want to ignore a missing checksum:
<<< Installation - Vorbereitung
Keine Prüfsumme gefunden
Es wurde keine Prüfsumme für Datei /var/tmp/TmpDir.HiC8oc/suse/setup/slide/txt in dem Repository gefunden. Dies bedeutet, dass die Datei Teil des signierten jedoch nicht in der Liste der Prüfsummen in diesem Repository erwähnt wird. Du kann die Integrität des Systems gefährdet werden.
Trotzdem verwenden?
[ ] Diese Meldung nicht erneut zeigen
[Ja] [Nein]
After lots of Alt-E (don't show again), Alt-J (use this file) and Alt-N (don't use this file) I finally got the installation running through until it wants to reboot. After reboot the system is not bootable and drops back to System Management menu and the boot options there too do not recognize any bootable devices apart from CD-ROM and NICs. Parted says this: (parted) print list Model: IBM H0 HUS103073FL3800 (scsi) Disk /dev/sda: 73.4GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 214MB 213MB primary fat16 boot, type=06 2 214MB 73.4GB 73.2GB extended lba, type=0f 5 215MB 2369MB 2154MB logical linux-swap(v1) type=82 6 2370MB 31.0GB 28.7GB logical type=83 7 31.0GB 73.4GB 42.4GB logical type=83 Previously there was AIX5 on the disk and it seemed it was completely repartitioned by the installer. Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On Thu, Feb 23, 2012 at 5:18 PM, Andreas Färber <afaerber@suse.de> wrote:
After lots of Alt-E (don't show again), Alt-J (use this file) and Alt-N (don't use this file) I finally got the installation running through until it wants to reboot. After reboot the system is not bootable and drops back to System Management menu and the boot options there too do not recognize any bootable devices apart from CD-ROM and NICs. Previously there was AIX5 on the disk and it seemed it was completely repartitioned by the installer.
On your system, YaST probably just used the whole disk. I've never used any of the POWER systems so I can't really help. SLED 11(SUSE Linux Enterprise Desktop) would likely have better support for your hardware. It is $50 a year for updates & stuff, but it would at least have all the security patches that openSUSE 11.1 doesn't get anymore. There is also the Evergreen project: http://en.opensuse.org/openSUSE:Evergreen which should theoretically have the possibility for a fairly updated 11.1 system. However, I'm not sure how well 11.1/ppc is supported or if there are any ppc users helping out with the project. Evergreen is using the SLE 11 kernel. -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On Thu, Feb 23, 2012 at 09:42:53PM -0500, Larry Stotler wrote:
On Thu, Feb 23, 2012 at 5:18 PM, Andreas Färber <afaerber@suse.de> wrote:
After lots of Alt-E (don't show again), Alt-J (use this file) and Alt-N (don't use this file) I finally got the installation running through until it wants to reboot. After reboot the system is not bootable and drops back to System Management menu and the boot options there too do not recognize any bootable devices apart from CD-ROM and NICs. Previously there was AIX5 on the disk and it seemed it was completely repartitioned by the installer.
On your system, YaST probably just used the whole disk. I've never used any of the POWER systems so I can't really help.
SLED 11(SUSE Linux Enterprise Desktop) would likely have better support for your hardware. It is $50 a year for updates & stuff, but it would at least have all the security patches that openSUSE 11.1 doesn't get anymore.
The enterprise desktop is not available for PowerPC, only SLES is.
There is also the Evergreen project:
http://en.opensuse.org/openSUSE:Evergreen
which should theoretically have the possibility for a fairly updated 11.1 system. However, I'm not sure how well 11.1/ppc is supported or if there are any ppc users helping out with the project. Evergreen is using the SLE 11 kernel.
11.1 powerpc is not covered by Evergreen at this time. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
Am 24.02.2012 03:42, schrieb Larry Stotler:
On Thu, Feb 23, 2012 at 5:18 PM, Andreas Färber <afaerber@suse.de> wrote:
After lots of Alt-E (don't show again), Alt-J (use this file) and Alt-N (don't use this file) I finally got the installation running through until it wants to reboot. After reboot the system is not bootable and drops back to System Management menu and the boot options there too do not recognize any bootable devices apart from CD-ROM and NICs. Previously there was AIX5 on the disk and it seemed it was completely repartitioned by the installer.
On your system, YaST probably just used the whole disk. I've never used any of the POWER systems so I can't really help.
SLED 11(SUSE Linux Enterprise Desktop) would likely have better support for your hardware. [...]
Our quest here is testing and fixing Factory, not running some old-but-working version. :) Kudos to Dinar for getting it this far already! So I am mainly in need of pointers how to get some of these fixed. I verified that using ext4 and always choosing Alt+J for the checksums did not help. I notice that the CD that boots fine uses \suse\yaboot.ibm, whereas the FAT16 boot partition uses just a yaboot file. Are there differences between yaboot and yaboot.ibm maybe? I tried appending all kinds of things in OF such as :1,yaboot without success, and the SMS menu is able to boot fine from CD but not from disk. 0 > printenv boot-device -------------- Partition: common -------- Signature: 0x70 --------------- boot-device /pci@800000020000003/pci@2,4/pci1069,b166@1/scsi@0/sd@8,0:1,yaboot /pci@800000020000003/pci@2,4/pci1069,b166@1/scsi@0/sd@8:2 ok 0 > boot ok 0 > boot /pci@800000020000003/pci@2,4/pci1069,b166@1/scsi@0/sd@8,0 ok 0 > boot /pci@800000020000003/pci@2,4/pci1069,b166@1/scsi@0/sd@8,0:1,yaboot ok 0 > boot /pci@800000020000003/pci@2,3/ide@1/disk@0 - Elapsed time since release of system processors: 60 mins 35 secs [...] Welcome to yaboot version r22.8-r1190.SuSE booted from '/pci@800000020000003/pci@2,3/ide@1/disk@0:1,\suseboot\yaboot.ibm' The installer said the following: Choose the root partition. 1) sda1 (203 MB, vfat, 'CE93D1C3-1) 2) sda6 (27 GB, btrfs) 3) sda7 (39 GB, btrfs)
1
*** Invalid root device. Choose the root partition. 1) sda1 (203 MB, vfat, 'CE93D1C3-1) 2) sda6 (27 GB, btrfs) 3) sda7 (39 GB, btrfs)
2
Starting syslog services..done Probing connected terminal... Initializing virtual console... Found a mlterm terminal on /dev/console (80 columns x 24 lines). Setting up (localfs) network interfaces: lo lo IP address: 127.0.0.1/8 done eth0 device: Intel Corporation 82546GB Gigabit Ethernet Co eth0 Starting DHCP4 client. Then it hangs there and I have to do an instant poweroff via Advanced System Management interface. The first system NIC was used successfully for network installation before. Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On Fri, Feb 24, 2012 at 10:11 AM, Andreas Färber <afaerber@suse.de> wrote:
Am 24.02.2012 03:42, schrieb Larry Stotler:
On Thu, Feb 23, 2012 at 5:18 PM, Andreas Färber <afaerber@suse.de> wrote:
After lots of Alt-E (don't show again), Alt-J (use this file) and Alt-N (don't use this file) I finally got the installation running through until it wants to reboot. After reboot the system is not bootable and drops back to System Management menu and the boot options there too do not recognize any bootable devices apart from CD-ROM and NICs. Previously there was AIX5 on the disk and it seemed it was completely repartitioned by the installer.
On your system, YaST probably just used the whole disk. I've never used any of the POWER systems so I can't really help.
SLED 11(SUSE Linux Enterprise Desktop) would likely have better support for your hardware. [...]
Our quest here is testing and fixing Factory, not running some old-but-working version. :) Kudos to Dinar for getting it this far already!
So I am mainly in need of pointers how to get some of these fixed.
I verified that using ext4 and always choosing Alt+J for the checksums did not help.
I notice that the CD that boots fine uses \suse\yaboot.ibm, whereas the FAT16 boot partition uses just a yaboot file. Are there differences between yaboot and yaboot.ibm maybe? I tried appending all kinds of things in OF such as :1,yaboot without success, and the SMS menu is able to boot fine from CD but not from disk. If SMS doesn't sees a disk to boot from, then you don't have bootloader installed to the disk.
The right debug would be after isntallation run lilo in verbose mode. So we can see if yaboot wrapped correctly. I finally have G5 on my desk (ppc970 based). So soon I'll start to do tests on G5 as well besides pSeries tests. And yes. Back to december I remember that bootloader installation was failed even on pSeries. So something is wrong with lilo or perl-Bootloader.
0 > printenv boot-device -------------- Partition: common -------- Signature: 0x70 --------------- boot-device /pci@800000020000003/pci@2,4/pci1069,b166@1/scsi@0/sd@8,0:1,yaboot /pci@800000020000003/pci@2,4/pci1069,b166@1/scsi@0/sd@8:2 ok 0 > boot ok 0 > boot /pci@800000020000003/pci@2,4/pci1069,b166@1/scsi@0/sd@8,0 ok 0 > boot /pci@800000020000003/pci@2,4/pci1069,b166@1/scsi@0/sd@8,0:1,yaboot ok 0 > boot /pci@800000020000003/pci@2,3/ide@1/disk@0 - Elapsed time since release of system processors: 60 mins 35 secs [...] Welcome to yaboot version r22.8-r1190.SuSE booted from '/pci@800000020000003/pci@2,3/ide@1/disk@0:1,\suseboot\yaboot.ibm'
The installer said the following:
Choose the root partition.
1) sda1 (203 MB, vfat, 'CE93D1C3-1) 2) sda6 (27 GB, btrfs) 3) sda7 (39 GB, btrfs)
1
*** Invalid root device.
Choose the root partition.
1) sda1 (203 MB, vfat, 'CE93D1C3-1) 2) sda6 (27 GB, btrfs) 3) sda7 (39 GB, btrfs)
2
Starting syslog services..done Probing connected terminal...
Initializing virtual console...
Found a mlterm terminal on /dev/console (80 columns x 24 lines). Setting up (localfs) network interfaces: lo lo IP address: 127.0.0.1/8 done eth0 device: Intel Corporation 82546GB Gigabit Ethernet Co eth0 Starting DHCP4 client.
Then it hangs there and I have to do an instant poweroff via Advanced System Management interface. The first system NIC was used successfully for network installation before.
Andreas
-- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On 24.02.2012, at 11:59, Dinar Valeev <k0da@opensuse.org> wrote:
On Fri, Feb 24, 2012 at 10:11 AM, Andreas Färber <afaerber@suse.de> wrote:
Am 24.02.2012 03:42, schrieb Larry Stotler:
On Thu, Feb 23, 2012 at 5:18 PM, Andreas Färber <afaerber@suse.de> wrote:
After lots of Alt-E (don't show again), Alt-J (use this file) and Alt-N (don't use this file) I finally got the installation running through until it wants to reboot. After reboot the system is not bootable and drops back to System Management menu and the boot options there too do not recognize any bootable devices apart from CD-ROM and NICs. Previously there was AIX5 on the disk and it seemed it was completely repartitioned by the installer.
On your system, YaST probably just used the whole disk. I've never used any of the POWER systems so I can't really help.
SLED 11(SUSE Linux Enterprise Desktop) would likely have better support for your hardware. [...]
Our quest here is testing and fixing Factory, not running some old-but-working version. :) Kudos to Dinar for getting it this far already!
So I am mainly in need of pointers how to get some of these fixed.
I verified that using ext4 and always choosing Alt+J for the checksums did not help.
I notice that the CD that boots fine uses \suse\yaboot.ibm, whereas the FAT16 boot partition uses just a yaboot file. Are there differences between yaboot and yaboot.ibm maybe? I tried appending all kinds of things in OF such as :1,yaboot without success, and the SMS menu is able to boot fine from CD but not from disk. If SMS doesn't sees a disk to boot from, then you don't have bootloader installed to the disk.
The right debug would be after isntallation run lilo in verbose mode. So we can see if yaboot wrapped correctly.
I finally have G5 on my desk (ppc970 based). So soon I'll start to do tests on G5 as well besides pSeries tests.
And yes. Back to december I remember that bootloader installation was failed even on pSeries. So something is wrong with lilo or perl-Bootloader.
At least the Apple OF has support for ELF straight in the firmware, so one thing to try would be to completely circumvent yaboot and boot the kernel straight from there. I don't think you can use an initrd with this though, so you might want to compile your own kernel with everything set to =y that you need to boot. It's just an alternative to get the system booting at all and debug yaboot from there. You can also try to run it in qemu-system-ppc64 with -M pseries, which should behave very similar to the pseries OF. Just that you can there modify the image from the outside to debug. Alex -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On Fri, Feb 24, 2012 at 4:11 AM, Andreas Färber <afaerber@suse.de> wrote:
Our quest here is testing and fixing Factory, not running some old-but-working version. :) Kudos to Dinar for getting it this far already! So I am mainly in need of pointers how to get some of these fixed.
I realize that. Was just offering an alternative.
I notice that the CD that boots fine uses \suse\yaboot.ibm, whereas the FAT16 boot partition uses just a yaboot file. Are there differences between yaboot and yaboot.ibm maybe? I tried appending all kinds of things in OF such as :1,yaboot without success, and the SMS menu is able to boot fine from CD but not from disk.
Way back when, you had to use CD2 to boot the IBM style systems. That's probably been one of the biggest problems with POWER is the different type of boot loaders required. -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
Am 23.02.2012 23:18, schrieb Andreas Färber:
Am 23.02.2012 21:54, schrieb Andreas Färber:
Hardware is an IBM IntelliStation 9111-285 (POWER5). I've tried letting it partition the disks with btrfs and then get stuck in an endless loop that keeps asking me if I want to ignore a missing checksum:
<<< Installation - Vorbereitung
Keine Prüfsumme gefunden
Es wurde keine Prüfsumme für Datei /var/tmp/TmpDir.HiC8oc/suse/setup/slide/txt in dem Repository gefunden. Dies bedeutet, dass die Datei Teil des signierten jedoch nicht in der Liste der Prüfsummen in diesem Repository erwähnt wird. Du kann die Integrität des Systems gefährdet werden.
Trotzdem verwenden?
[ ] Diese Meldung nicht erneut zeigen
[Ja] [Nein]
After lots of Alt-E (don't show again), Alt-J (use this file) and Alt-N (don't use this file) I finally got the installation running through
(About 31x Alt-J)
until it wants to reboot. After reboot the system is not bootable and drops back to System Management menu and the boot options there too do not recognize any bootable devices apart from CD-ROM and NICs.
Parted says this:
(parted) print list Model: IBM H0 HUS103073FL3800 (scsi) Disk /dev/sda: 73.4GB Sector size (logical/physical): 512B/512B Partition Table: msdos
Number Start End Size Type File system Flags 1 1049kB 214MB 213MB primary fat16 boot, type=06 2 214MB 73.4GB 73.2GB extended lba, type=0f 5 215MB 2369MB 2154MB logical linux-swap(v1) type=82 6 2370MB 31.0GB 28.7GB logical type=83 7 31.0GB 73.4GB 42.4GB logical type=83
With Alex, Dinar's and Ben's help I figured out that the type=06 partition is the culprit here. The YaST partitioner sets it up correctly as type=41, but when ext4 or btrfs is used, it gets converted from PReP to FAT16. Selecting ext3 in the partitioner leads to an error during bootloader installation when it tries to shrink the PReP boot partition using: /usr/sbin/parted -s /dev/sda resize 1 2048s 2191s parted does not recognize the filesystem in /dev/sda1 (there is none in such a PReP boot partition) and therefore refuses to resize it. I used fdisk to manually delete and recreate it using these start and end sectors and ran dd if=/media/cdrom/suseboot/yaboot.ibm of=/dev/sda1 That made the disk bootable for SMS and OF but yaboot does not find its config. Creating an ext3 primary partition 3 in the space between resized PReP boot partition and extended partition and placing files /etc/yaboot.conf and /etc/yaboot,cnf did not help. (I still have to try /yaboot.cnf.) The following worked to boot into the installation: yaboot: disk:6,/boot/vmlinux initrd=disk:6,/boot/initrd There are still some errors though, like DHCP4 hanging (although it does in the installer) and something localfs-dependent network hangs, too. Using static IP, default route and static nameserver worked. Shutting down the system has the same problems as starting up and this is reproducible on every boot. All feels a bit unstable but that might be just the current state of Factory. Unfortunately osc is not available yet, to work on improving things from the ppc machine. Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
On Mon, Feb 27, 2012 at 2:27 PM, Andreas Färber <afaerber@suse.de> wrote:
Am 23.02.2012 23:18, schrieb Andreas Färber:
Am 23.02.2012 21:54, schrieb Andreas Färber:
Hardware is an IBM IntelliStation 9111-285 (POWER5). I've tried letting it partition the disks with btrfs and then get stuck in an endless loop that keeps asking me if I want to ignore a missing checksum:
<<< Installation - Vorbereitung
Keine Prüfsumme gefunden
Es wurde keine Prüfsumme für Datei /var/tmp/TmpDir.HiC8oc/suse/setup/slide/txt in dem Repository gefunden. Dies bedeutet, dass die Datei Teil des signierten jedoch nicht in der Liste der Prüfsummen in diesem Repository erwähnt wird. Du kann die Integrität des Systems gefährdet werden.
Trotzdem verwenden?
[ ] Diese Meldung nicht erneut zeigen
[Ja] [Nein]
After lots of Alt-E (don't show again), Alt-J (use this file) and Alt-N (don't use this file) I finally got the installation running through
(About 31x Alt-J)
until it wants to reboot. After reboot the system is not bootable and drops back to System Management menu and the boot options there too do not recognize any bootable devices apart from CD-ROM and NICs.
Parted says this:
(parted) print list Model: IBM H0 HUS103073FL3800 (scsi) Disk /dev/sda: 73.4GB Sector size (logical/physical): 512B/512B Partition Table: msdos
Number Start End Size Type File system Flags 1 1049kB 214MB 213MB primary fat16 boot, type=06 2 214MB 73.4GB 73.2GB extended lba, type=0f 5 215MB 2369MB 2154MB logical linux-swap(v1) type=82 6 2370MB 31.0GB 28.7GB logical type=83 7 31.0GB 73.4GB 42.4GB logical type=83
With Alex, Dinar's and Ben's help I figured out that the type=06 partition is the culprit here. The YaST partitioner sets it up correctly as type=41, but when ext4 or btrfs is used, it gets converted from PReP to FAT16. Yeah.. FAT16 setup is broken, but as I can see from the logs kernel, initrd, yaboot and its config are copied over to the partition. So metadata or FS itself is not compatible.
Selecting ext3 in the partitioner leads to an error during bootloader installation when it tries to shrink the PReP boot partition using:
/usr/sbin/parted -s /dev/sda resize 1 2048s 2191s
parted does not recognize the filesystem in /dev/sda1 (there is none in such a PReP boot partition) and therefore refuses to resize it. I used fdisk to manually delete and recreate it using these start and end sectors and ran dd if=/media/cdrom/suseboot/yaboot.ibm of=/dev/sda1
That made the disk bootable for SMS and OF but yaboot does not find its config. Creating an ext3 primary partition 3 in the space between resized PReP boot partition and extended partition and placing files /etc/yaboot.conf and /etc/yaboot,cnf did not help. (I still have to try /yaboot.cnf.) The following worked to boot into the installation:
yaboot: disk:6,/boot/vmlinux initrd=disk:6,/boot/initrd
Weird, I don't have such problem
There are still some errors though, like DHCP4 hanging (although it does in the installer) and something localfs-dependent network hangs, too. Using static IP, default route and static nameserver worked. Shutting down the system has the same problems as starting up and this is reproducible on every boot. All feels a bit unstable but that might be just the current state of Factory.
I think this is related to sed is missing in initrd
Unfortunately osc is not available yet, to work on improving things from the ppc machine.
You can grab osc from openSUSE:Tools project (It builds against factory). Or use SDK packages.
Andreas
-- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
Hi here my experience in getting Factory 0003 build installed on pmac_new G5. On Sat, Feb 18, 2012 at 10:47 PM, Wolfgang Engel <wengel@suse.de> wrote:
Hi there,
just a few words how to boot current factory on PowerMac. I tried it on a 1,6GHz PowerMac G5.
1. Power on your PowerMac ;) 2. Get to Open Firmware with "Alt-Option-O-F" keys pressed 3. Insert openSUSE-NET-ppc CD by ejecting CD-ROM drive with command "eject cd" 4. Boot into yaboot by entering "boot cd:,\suseboot\yaboot" 5. Choose your Installation-Type
From there I was able to go through installation pre-configuration setup (network, http-server) and YaST2 started. But it crashed when I tried to do partitioning stuff. It didn't crashed for me. Maybe I'm using newer yast build.
The lilo.conf generated by perl-Bootloader is wrong. It writes to the option section: append initrd root You need to configure installation in a way it start a shell before and after installation. (So after installation you can debug booloader) So I've deleted those bad strings and rerun lilo. It wrote yaboot configuration to the disk. But still have an error like: MAC-PARTS: specified partiition is not valid /ht@0,f2000000/pci@5/k2-sata-root@c/k2-sata@0/disk@0:4,/boot/vmlinux-3.2.0-5-ppc64: Unable to open file, Invalid device Also I've found that perl-Bootloader reports missing submodule powerlilo that might cause issue. Have fun,
Maybe someday I'll have the knowledge to be able to fix things for PPC...
Have fun!
Wolfgang
-- View this message in context: http://opensuse.14.n6.nabble.com/Booting-openSUSE-NET-ppc-Build0003-Media-is... Sent from the opensuse-ppc mailing list archive at Nabble.com. -- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ppc+owner@opensuse.org
participants (7)
-
Alexander Graf -
Andreas Färber -
Dinar Valeev -
Larry Stotler -
Marcus Meissner -
Richard (MQ) -
Wolfgang Engel