Ubuntu 16.04 should work. Void doesn’t work either?
I can't even get to the installer with Void.
Ubuntu 16.04 should work. Void doesn’t work either?
I have MintPPC11 running on my iMac G5, this was all 32-bits.How does one get a 32 bit user land while using a 64 bit kernel?
Did you try my trick of installing Jessie and then try to dist-upgrade to sid ?I’m under the impression that Debian Sid 64 bit is still utterly broken. I did 2 clean installs last night, and after installing the latest kernel, and a DE, it kernel panics while booting.
No, because Jessie is just as broken as Bullseye on 64 bit 😭I have MintPPC11 running on my iMac G5, this was all 32-bits.
[automerge]1569933041[/automerge]
Did you try my trick of installing Jessie and then try to dist-upgrade to sid ?
In theory, shouldn't one be able to simply yank a 32 bit kernel image from an existing ISO, and replace the 64 bit kernel image?In the past we had 64-bits kernel and 32-bits user land. Apparently there are still folks building such environemnts:
I will try to do that, or install images with 64-bits kernel and 32-bits userland as per Jenkins. This whole ppc64 project is still in its infancy I think.In theory, shouldn't one be able to simply yank a 32 bit kernel image from an existing ISO, and replace the 64 bit kernel image?
I’m a stay at home dad, so I have all the time in the world (as long as the kids are behaving). 😁I will try to do that, or install images with 64-bits kernel and 32-bits userland as per Jenkins. This whole ppc64 project is still in its infancy I think.
[automerge]1569939106[/automerge]
If you have the time now, you can try to boot and install Debian sid on G5 with this image here:
debian-cd_sid_powerpc workspace : /build [Jenkins]
jenkins.kfreebsd.eu
Last nights installation was done with the 10 installer. No problems arose, until I did a full upgrade, and installed LXDE. After upgrading, and installing LXDE, it would kernel panic when booting.According to the specialist, Adrian Glaubitz, the 10.0 installer should also work on G5:
You might want to try that too....
The image you linked to from 2017 complains about not having any modules to load after reaching the installer.I see...
Cannot you boot with the kernel you had before dist-upgrading ?I remember in the past you had that option in yaboot of choosing an old kernel "old".Last nights installation was done with the 10 installer. No problems arose, until I did a full upgrade, and installed LXDE. After upgrading, and installing LXDE, it would kernel panic when booting.
How does one get a 32 bit user land while using a 64 bit kernel?
Jessie is just as broken as Bullseye on 64 bit
Cannot you boot with the kernel you had before dist-upgrading ?I remember in the past you had that option in yaboot of choosing an old kernel "old".
Yes, I was able to boot with the old kernel, but Userspace was broken.Cannot you boot with the kernel you had before dist-upgrading ?I remember in the past you had that option in yaboot of choosing an old kernel "old".
This option of install64 is no longer there in the recent images. These images are either full 32-bits or 64-bits. So, maybe, when installing this mixed 64-bit kernel and 32-bit userland from the past and upgrading to latest sid, will break the system as it then also installs a kernel that cannot handle this mixed environment any longer. Is this a reasonable conclusion ?Linux distributions (and I believe OS X) have done this for a long time. The userland in the powerpc environments are 32-bit by default, and when you select 'install64' or 'install-powerpc64' in the installer, you are selecting a 64-bit kernel while retaining the 32-bit userland.
Possibly, I dunno. I’m gonna try installing Bullseye again.Are you talking about the mixed environment in the powerpc variant?
Can you check if your system after dist-upgrading also has 64-bits packages ?Yes, I was able to boot with the old kernel, but Userspace was broken.
I had this same trouble with my G5 Quad, yaboot can't read the ext4 partition.Ok, I did that. Then also did the apt get for hfsutils.
Followed the previous steps and rebooted. This time I didn't get the no OS icon ( Progress!). However when it started to boot, I got the following:
@wicknix what does your G5 configuration look like? Ubuntu appears to install okay on my 2.3 GHz DP, but I just get the no disk found icon when trying to boot after installation. Interestingly enough, it installs, and works perfectly on my Powerbook A1138.This is just a suggestion.... If debian proves to be too problematic, why not just respin an updated Ubuntu 16.04.6? It offers a live CD w/install option, it automatically determines if you need 32 or 64 bit kernel and installs the appropriate one, yaboot works out of the box, it's still getting security updates for another 18 months or so, the 4.4 kernel works and still has radeon 9200 support and still gets updates, and your mintppc overlay packages install and work fine in my testing. Then just rebuild a few things that you may want newer versions of and host them in your repo.
Again, just a suggestion, but I think it'd solve many issues until debian 10 ppc is more stable.
Cheers
I also had the same trouble with Mate 16.04 on my DC G5 2.3Ghz, swapping the hard drive positions fixed the issue.@wicknix what does your G5 configuration look like? Ubuntu appears to install okay on my 2.3 GHz DP, but I just get the no disk found icon when trying to boot after installation. Interestingly enough, it installs, and works perfectly on my Powerbook A1138.
Really? I used the SATA connector located on the bottom of the drive bay. I'll try a reinstall using the top one later on.I also had the same trouble with Mate 16.04 on my DC G5 2.3Ghz, swapping the hard drive positions fixed the issue.
I didn't have to reinstall, just swapped the drives around and that got it booting.Really? I used the SATA connector located on the bottom of the drive bay. I'll try a reinstall using the top one later on.