Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Attachments

  • IMG_0638.JPG
    IMG_0638.JPG
    689.2 KB · Views: 294
How does one get a 32 bit user land while using a 64 bit kernel?
I have MintPPC11 running on my iMac G5, this was all 32-bits.
[automerge]1569933041[/automerge]
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.
Did you try my trick of installing Jessie and then try to dist-upgrade to sid ?
 
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 ?
No, because Jessie is just as broken as Bullseye on 64 bit 😭
 
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 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:
I would go for a standard installation, is faster to know the end result.
 
Last edited:
  • Like
Reactions: sparty411
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:
I’m a stay at home dad, so I have all the time in the world (as long as the kids are behaving). 😁
I’ll burn that image, and give it a try.
 
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.
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".
 
How does one get a 32 bit user land while using a 64 bit kernel?

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.

Jessie is just as broken as Bullseye on 64 bit

Last time I checked (it's been a while, could be wrong), Jessie didn't have a full ppc64 environment. Are you talking about the mixed environment in the powerpc variant?

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".

If you are able to chroot into your system, you can manually add it to yaboot.conf. "intrid" and "vmlinux" were just appended with "-old", I think. Something like that.
 
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.
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 ?
 
  • Like
Reactions: z970
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
 
  • Like
Reactions: sparty411
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:
I had this same trouble with my G5 Quad, yaboot can't read the ext4 partition.

I had to make a /boot partition and format it ext3.
 
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
@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.
 
@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.
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 also had the same trouble with Mate 16.04 on my DC G5 2.3Ghz, swapping the hard drive positions fixed the issue.
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.
 
hello!
What could we PBG4 users look forward to coming from tiger and leopard, in regards to functions? I have never used linux at all...
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.