Debian Sid Installation Guide (PowerPC)

[galgot]

Try to edit

/etc/default/grub

and change to

GRUB_DISABLE_OS_PROBER=false

To have Debian visible in the boot picker, you can make a CHRP file (template here: https://wiki.gentoo.org/wiki/GRUB_on_Open_Firmware_(PowerPC)#CHRP_boot_script) and change the boot line to yours (
boot hd:9,\grub). You then need to copy it to your boot partition (presumably sda9 or hda9) which already looks to have your grub and grub.cfg file.

Make sure you set the attributes correctly after copying, using e.g.

hattrib -t tbxi :ofboot.b

Cheers,

Thanks !
GRUB_DISABLE_OS_PROBER=false
doesn't seem to work tho... Grub still shows only Debian.
Anyway I've
setenv boot-device hd:9,\grub
in OF, so to boot into grub by default. If I want to boot the other two systems I just press alt and they show.

Also, this running on a SSD, there seems to be a problem with sleep. After some time of inactivity, the system freezes , so I think sleep/suspend/hybernate is activated by default, but it doesn't like waking up a SSD or a PCC...
So I disactivated all :
sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target
So far, so good. no big deal anyway, as sleep is broken on PowerPC Debian since Jessie.

 

[pc297]

GRUB_DISABLE_OS_PROBER=false
doesn't seem to work tho... Grub still shows only Debian.

It could be that you have to run grub-mkconfig / grub2-mkconfig after having set it

 

[galgot]

It could be that you have to run grub-mkconfig / grub2-mkconfig after having set it

Ok, some small progress...
After trying your suggestion and getting no result, checked some infos on GRUB_DISABLE_OS_PROBER…
Tried different things , like
sudo os-prober
Which did tell me that it was seeing OS X at least.
Then:
sudo grub-mkconfig -o /boot/grub/grub.cfg
Which does the same as you have suggested…
Still no joy.. until I reopened /etc/default/grub
And found out I had typed :
GRUB_DISABLE_OS_prober=false , « prober » in lowercase All my fault, sorry for that...
Correcting that, then doing :
sudo grub-update
Did the trick, it recognized the OSX part…
But then, now booting grub gives me this :



Hu ? I have a 64-bit Tiger there ?
And selecting the « Mac OS X (32-bit) (on /dev/sda10) »
I get this :



Funny stuff… grub should have installed a kext but didn’t or something ?… trying the « Mac OS X (64-bit) (on /dev/sda10) »
gives me the same error but with « 64 » added to these « xnu-kernel » and « xnu_mkext »….
And no trace of my OS 9, which is on sda9…
I think I’ll stop here with these booting stuff, holding the alt key is enough of an option for me for now…
Here are the 3 systems on this Pismo :







Cheers !

 

[pc297]

Hu ? I have a 64-bit Tiger there ?
And selecting the « Mac OS X (32-bit) (on /dev/sda10) »
I get this :

Awww I forgot about that one... I think the xnu loader was never implemented for grub under ppc :/ Which is why you see 32- and 64-bit options, made for intel. If you really want the OSes to be displayed at boot (rather than at the boot picker) then you're probably better off with Yaboot, with which I confirm booting foreign OSes works properly, e.g. with macosx=/dev/sda10 in /etc/yaboot.conf and I think macos=/dev/sda11 there too if you have OS9 there. You will need an ext2-formatted boot partition though, e.g. 1Gb to accomodate various initrd and kernel variations and updates, but your root partition can be ext4. Make sure that your ext2-formatted boot partition is mounted at /boot. Worked for me with debian, but grub is easier, allows 1 large partition. Strangely enough with Ubuntu 16.04 yaboot could still use ext4 partitions formatted under 16.04, but this stopped there. You could also format your partition with Ubuntu 16.04 (but nothing later than that) and then install debian and then yaboot, I think this also worked for me.

 

[fluidhd]

hello,

I'm hoping someone can help me, I'm currently on my 4th/5th install of
Debian SID and I have yet to get the radeon graphics card working

I'm on a G5 quad
geforce 6600 (openfirmware vbios)
radeon 5850 (pc vbios)

I've looked online for the same issue, but I've only come across solutions on x86

as I understand it "radeon" is the free driver and "amdgpu" is the commercial driver? and these
can sometimes conflict

also I get the feeling that "amdgpu" is best suited to cards newer than my 5850

on the previous install I managed eventually to get boot text to ouput from the radeon, but at
this point the nvidia card stopped working

when I tries "startx" I ran into one of two issues

I would either get an error about DRM conflict between version 2.5.0 and 3.0.0
I thought I had cured this, on the next boot I had a error (EE) no screens found

so is there a foolproof way to get a radeon driver working in Debian SID ppc64?

this is what I am seeing presently

vee@g5mac:~$ su
Password:
root@g5mac:/home/vee# lspci -k|egrep 'VGA|in use'
0000:0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cypress PRO [Radeon HD 5850]
Kernel driver in use: snd_hda_intel
Kernel driver in use: macio
Kernel driver in use: ohci-pci
Kernel driver in use: ohci-pci
Kernel driver in use: ehci-pci
Kernel driver in use: sata_svw
Kernel driver in use: pata-pci-macio
Kernel driver in use: firewire_ohci
Kernel driver in use: tg3
Kernel driver in use: tg3
0001:06:00.0 VGA compatible controller: NVIDIA Corporation NV43 [GeForce 6600 LE] (rev a2)
Kernel driver in use: nouveau
root@g5mac:/home/vee# radeon_device_intialize
bash: radeon_device_intialize: command not found
root@g5mac:/home/vee#

 

[pc297]

hello,

I'm hoping someone can help me, I'm currently on my 4th/5th install of
Debian SID and I have yet to get the radeon graphics card working

I'm on a G5 quad
geforce 6600 (openfirmware vbios)
radeon 5850 (pc vbios)

I've looked online for the same issue, but I've only come across solutions on x86

as I understand it "radeon" is the free driver and "amdgpu" is the commercial driver? and these
can sometimes conflict

also I get the feeling that "amdgpu" is best suited to cards newer than my 5850

on the previous install I managed eventually to get boot text to ouput from the radeon, but at
this point the nvidia card stopped working

when I tries "startx" I ran into one of two issues

I would either get an error about DRM conflict between version 2.5.0 and 3.0.0
I thought I had cured this, on the next boot I had a error (EE) no screens found

so is there a foolproof way to get a radeon driver working in Debian SID ppc64?

this is what I am seeing presently

Did you try:

video=offb:off video=nouveaufb:off video=radeonfb:off radeon.modeset=1 nouveau.modeset=0 pci=realloc radeon.agpmode=-1 radeon.dpm=1

as your append on top of installing firmware-linux-nonfree?

I have a radeon HD 5770 in my Quad so very very close to your setup and in my hands Sid works fine, although a few packages have been broken as of late to fully install gnome (you can find whatever library versions it's not finding on debian-snapshot), but one solved gnome runs very well

 

[fluidhd]

Did you try:

video=offb:off video=nouveaufb:off video=radeonfb:off radeon.modeset=1 nouveau.modeset=0 pci=realloc radeon.agpmode=-1 radeon.dpm=1

as your append on top of installing firmware-linux-nonfree?

I have a radeon HD 5770 in my Quad so very very close to your setup and in my hands Sid works fine, although a few packages have been broken as of late to fully install gnome (you can find whatever library versions it's not finding on debian-snapshot), but one solved gnome runs very well

Thanks for replying, do I add the video=off........ To the grub file? Or do I need to type it in a yaboot at every bootup? Sorry I'm a bit of a newbie to this

 

[fluidhd]

I

Thanks for replying, do I add the video=off........ To the grub file? Or do I need to type it in a yaboot at every bootup? Sorry I'm a bit of a newbie to this

I forgot to mention I installed firmware-amd-graphics from the powerprogress repo

 

[pc297]

I

I forgot to mention I installed firmware-amd-graphics from the powerprogress repo

So depending on whether you use grub or yaboot, you add it to your /boot/grub/grub.cfg on the same line as

linux /boot/vmlinuz root=/dev/sdXX quiet splash

(just add in front of quiet splash)

or to your /etc/yaboot.conf in the line that says append=xxxx

If using yaboot be sure to type

sudo mkofboot -v -C /etc/yaboot.conf
sudo ybin -v -C /etc/yaboot.conf

Not sure if firmware-amd-graphics is enough, maybe try apt install firmware-linux-nonfree on top for which it is a dependency

 

[fluidhd]

I'm using grub

Trouble is even with sudo nano grub.cfg is write protected, so I can't add anything to it

 

[pc297]

I'm using grub

Trouble is even with sudo nano grub.cfg is write protected, so I can't add anything to it

Ah I see, I guess that you followed powerprogress's instructions then your /boot is hfs and write-protected.

You can go around it using a couple of hcopies (from hfsutils), e.g.

sudo hmount /dev/sdX

where sdX is your boot partition

sudo hcopy :grub.cfg ~/
sudo nano ~/grub.cfg

then add your appends and save

sudo hcopy ~/grub.cfg :grub.cfg
sudo humount

However if you just want to try it instead of modifying /boot/grub.cfg just type c in grub and then:

root=(ieee1275/ultraX,appleY)

where X is 0 if your top bay, 1 your bottom bay, Y your boot partition number

linux /boot/vmlinuz root=/dev/sdZW video=offb:off video=nouveaufb:off video=radeonfb:off radeon.modeset=1 nouveau.modeset=0 pci=realloc radeon.agpmode=-1 radeon.dpm=1

where Z is a if your top bay, b your bottom bay, W your root partition number

initrd /boot/initrd
boot

Could be that you have to try it multiple times if it doesn't work the first time around, somehow occasionally sda and sdb get swapped in grub

 

[fluidhd]

Thanks for the help

I've just borked debian again, if I can't find a live build I'll have to do a reinstall again

I don't suppose you feel like uploading a working Radeon hd image ?

Are there any ppc64 Linux builds where PC radeons will autoconfigure on install?

Btw I think this issue might be related to some of the issues I've been having, but your card is similar to mine so maybe not

[drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) (#773) · Issues · drm / amd · GitLab

Submitted by intermediadc@hotmail.com Assigned to Default DRI bug account

gitlab.freedesktop.org

 

[pc297]

Thanks for the help

I've just borked debian again, if I can't find a live build I'll have to do a reinstall again

I don't suppose you feel like uploading a working Radeon hd image ?

Are there any ppc64 Linux builds where PC radeons will autoconfigure on install?

Btw I think this issue might be related to some of the issues I've been having, but your card is similar to mine so maybe not

[drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) (#773) · Issues · drm / amd · GitLab

Submitted by intermediadc@hotmail.com Assigned to Default DRI bug account

gitlab.freedesktop.org

I can try to make a dd image in the next few days and upload it to dropbox. It's on a gpt-formatted hard drive though, but you should be fine with it.

Re big-endian ppc64 linux distros with radeons autoconfigured, try Tumbleweed following these instructions (it needs to be installed on a gpt-formatted hard drive, which will only work on G5 Quads/DC possibly the very last iMac G5 iSight - I tested it and it won't boot from any earlier G5):

Booting a GUID disk on PowerPC Macs

Booting from gpt allows OpenSuse Tumbleweed to be installed on PM G5s. The way to go about it using an empty drive in the top bay: 1) Format your empty drive using the GUID partition scheme 2) Install OpenSuse Tumbleweed ppc64, let the installer use the entire drive, it should result in...

forums.macrumors.com

That said, I can also make a dd image out of this one, you would simply need to partition your hard drive using gpt

Don't update to the latest kernel with a 5770/5870, you will lose acpi powerdown, which oddly still works with HD 4650/4870 cards with 5.16.X

Otherwise there's always Gentoo but my electricity bill jumped up after compiling for a straight 2+ days so I won't recommend it these days, and it's a pain in the neck to get radeons to work with it but it's doable.

 

[MacMaverick855]

@wicknix, @z970, @swamprock I have successfully loaded Debian11 on my Mac Tower G5!!! Problem is, I had to plug in a DVI monitor to see the desktop. Haven't taken it for a spin yet but, I had to know if plugging in my 17" Apple Display to it proprietary GPU connection (on the same Radeon ATY128 card) would have any results. It did!, well at least the Display preference saw the display, it even knew what it was but there was nothing on the screen. Pure black. There has got to be a way for Debian 11, from terminal if I have to, to drive the Apple display. How can theDisplay preference "see" that the Apple display is connected and yet not drive the monitor?

Again, I got as far as starting up in Debian 11, no boot parameters needed, to get the desktop to appear on the DVI monitor. Then I hooked up the Apple Display (yes hot , did not turn off the computer) and Display preferences immediately detected the monitor.

I'm guessing it's time to modify etc/X11/xorg.conf, or at least look at it to see what it's showing. Next trick will be to get the Airport card to work. I'm currently hard wired to the interwebz.

Any suggestions would be appreciated.

 

[Amethyst1]

How can theDisplay preference "see" that the Apple display is connected and yet not drive the monitor?

It’s possible that it’s sending an incompatible resolution to the Apple monitor, which can cause it to remain black.

 

[MacMaverick855]

It’s possible that it’s sending an incompatible resolution to the Apple monitor, which can cause it to remain black.

I did notice that I could NOT change the resolution for the Apple display in the Display preference app. I did not try to mess with the resolution for the DVI monitor.

So, how do I force a “more compatible” resolution to the Apple display?

Thanks for the quick reply!!
Mav

 

[Amethyst1]

So, how do I force a “more compatible” resolution to the Apple display?

What display is this? The 17" CRT Studio Display or the 17" LCD Studio Display? What resolution is it currently reporting in the Display preference app?

 

[MacMaverick855]

What display is this? The 17" CRT Studio Display or the 17" LCD Studio Display? What resolution is it currently reporting in the Display preference app?

I’ll have to wait until I get back from “TOP GUN MAVERICK” to get the resolution but it is the smaller 17” LCD.

 

[Amethyst1]

I’ll have to wait until I get back from “TOP GUN MAVERICK” to get the resolution but it is the smaller 17” LCD.

The 17" LCD's native resolution is 1280×1024. I don't think it has a built-in scaler (the larger Cinema Displays don't have one either), i.e. if you're sending it any other resolution it will remain black.

 

[MacMaverick855]

The 17" LCD's native resolution is 1280×1024. I don't think it has a built-in scaler (the larger Cinema Displays don't have one either), i.e. if you're sending it any other resolution it will remain black.

I believe the first resolution number was 1280 but I don’t recall the second one. However if the 1280x1024 IS the resolution showing in the Display preference, I may have other issues to deal with. Thanks for the advice!!!
MacMaverick855

 

[MacMaverick855]

I’ll have to wait until I get back from “TOP GUN MAVERICK” to get the resolution but it is the smaller 17” LCD.

@Amethyst1 So, the resolution in the Display preference for both the DVI and the Apple Display is 1280x1024.
I started the G5 with both monitors attached and the Apple display remained black AND the DVI monitor was pixelated and the panel at the top and taskbar at the bottom were not visible.

I disconnected the Apple display and restarted the G5 and the DVI monitor worked perfectly as it had before. I then reconnected the Apple display and the Display preferences showed both monitors attached but the resolution could not be changed on either of the monitors:1280x1024 was the only choice available. I’m guessing I will need to get into /etc/X11/xorg.conf to see what resolutions are available and probably add more resolutions. The thing that bothers me is that if the native resolution for the Apple Cinema Display is 1280x1024, why is it black (blank)? Also, why is the screen on the DVI monitor pixelated when the computer starts up with both monitors are connected during start up?

More research required,
MacMav

 

[MacMaverick855]

Ok, I looked for /etc/X11/xorg.conf.d and there isn’t one. I did find /user/share/X11/xorg.conf.d and it contained radeon.conf among others. I tried to create an xorg.conf using the command Xorg -configure but it through an error.
I need a method, command , file something to get the Apple Cinema Display to show something. Displays preference sees it, running xrandr shows it as VGA-0 with only one resolution, 1280x1024 which is what it is set at when I run Sorbet Leopard on the same machine. The monitor has numerous options for other resolutions in Mac OSX but in Debian, only the one.
What file do I need to add and where to get Debian to drive the Apple Cinema Display?
Should I add Device, Monitor, Screen Sections to the radeon.conf file with the appropriate information to “force” Debian to see the ACD? Would it even work?

 

[Amethyst1]

Displays preference sees it, running xrandr shows it as VGA-0 […]

I’m not sure if that means anything (it could just be a meaningless label) but ADC LCDs require digital (DVI/TMDS) input. If it’s fed an analog VGA signal that’s not going to work…

What state is the display’s power light in? Off, solid white or flashing repeatedly (the latter indicates “incompatible input”)?

 

[MacMaverick855]

I’m not sure if that means anything (it could just be a meaningless label) but ADC LCDs require digital (DVI/TMDS) input. If it’s fed an analog VGA signal that’s not going to work…

What state is the display’s power light in? Off, solid white or flashing repeatedly (the latter indicates “incompatible resolution”)?

Interesting, I thought it was strange that the display was labeled VGA, when it’s anything but… The power light on the ACD is on solid, the brightness button shows no response when pushed. The desktop behaves as if the desktop extends to the ACD. I can run the cursor to the left (where it is “arranged”) and windows open on that screen, I just can’t get to them.

What would be telling the Debian OS to drive the ACD with a VGA signal? I wouldn’t know where to begin to develop instructions to send a digital signal to the ACD. If I wrote an xorg.conf file telling the software that monitor 2 or the monitor to the left was a DVI, I wonder if it would send a digital signal to the monitor. My problem right now is I’m having trouble locating the file I should modify. The radeon.conf doesn’t have Monitor, Device, or Screen sections only, Output.


I’ll look into what it might take to get a digital signal to the ACD.

Thanks for the reply,
Mac Mav

 

[repairedCheese]

Interesting, I thought it was strange that the display was labeled VGA, when it’s anything but… The power light on the ACD is on solid, the brightness button shows no response when pushed. The desktop behaves as if the desktop extends to the ACD. I can run the cursor to the left (where it is “arranged”) and windows open on that screen, I just can’t get to them.

What would be telling the Debian OS to drive the ACD with a VGA signal? I wouldn’t know where to begin to develop instructions to send a digital signal to the ACD. If I wrote an xorg.conf file telling the software that monitor 2 or the monitor to the left was a DVI, I wonder if it would send a digital signal to the monitor. My problem right now is I’m having trouble locating the file I should modify. The radeon.conf doesn’t have Monitor, Device, or Screen sections only, Output.


I’ll look into what it might take to get a digital signal to the ACD.

Thanks for the reply,
Mac Mav

I'm going to go out on a limb and guess because there's a VGA passthrough, it's making the easy guess. If it got a DVI-A port wrong like that, it wouldn't be a problem, as monitors that support DVI-A also support VGA.

The good news is, DVI-D exists, without the passthrough, so if you could convince Debian that it's a DVI-D port, it might actually work. I realize it's kind of a long shot, and the only other way to test the port under Linux would be get an old 17" Studio Display CRT that seems to have used the VGA passthrough, and there's very little documentation about this aspect of the port in general.