Re: Kernel Panic 6.5.0-1 PPC
OK, I stand corrected! In any case, whatever the number, it seems to be fixed. And that's what's important! Rick On Wed, Oct 11, 2023, at 2:02 AM, John Paul Adrian Glaubitz wrote: > Hi Rick! > > On Wed, 2023-10-11 at 01:20 -0700, Rick Thomas wrote: >> I just did an update -> upgrade on my Power Mac G4 and noticed >> that it provides the new kernel version 6.5.0-2 . > > That's not the kernel version, but the ABI version of the kernel. > > The kernel version is 6.5.6 and the version of the kernel package is 6.5.6-1. > >> This appears to have fixed the panic-on-boot bug in version 6.5.0-1 . >> >> Big thanks for all your efforts! > > Adrian > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer > `. `' Physicist > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Kernel Panic 6.5.0-1 PPC
Wow! I just did an update -> upgrade on my Power Mac G4 and noticed that it provides the new kernel version 6.5.0-2 . This appears to have fixed the panic-on-boot bug in version 6.5.0-1 . Big thanks for all your efforts! Rick
Re: hfsprogs depends on libssl1.1 which is obsolete
On Mon, May 30, 2022, at 3:46 AM, John Paul Adrian Glaubitz wrote: > Hello Rick! > > On 5/30/22 12:24, Rick Thomas wrote: >> Sadly, it looks like this wasn't the only dependency on libssl1.1 . >> Apparently libsnmp40 also depends on it. > > Library transitions are handled by the release team, not by me. > Otherwise I would > have to manually rebuild thousands of packages. The ongoing OpenSSL > transition can > be observed here for the release architectures: > >> https://release.debian.org/transitions/html/auto-openssl.html > > and for the Debian Ports architectures: > >> https://ben.jrtc27.com/html/auto-openssl.html > > hfsprogs was a special case, because that package was built manually in > the first > place as Debian Ports does not support the contrib and non-free > sections yet. > > If libsnmp has not been rebuilt against libssl3.0 yet, it usually means there > is > a bug in the package which prevents it from building with OpenSSL 3.0 which is > indeed the case for net-snmp: > >> https://buildd.debian.org/status/package.php?p=net-snmp >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006511 > > Adrian Thanks for the excellent explanation! I understand the situation much better now. Again, I very much appreciate your efforts! Thanks, Rick
Re: hfsprogs depends on libssl1.1 which is obsolete
On Fri, May 27, 2022, at 6:07 AM, John Paul Adrian Glaubitz wrote: > Hello! > > On 5/26/22 06:56, John Paul Adrian Glaubitz wrote: >>> Am I missing something? >> >> hfsprogs needs to be rebuild against OpenSSL 3.0. I will take care of it. > > This has been done now. hfsprogs 540.1.linux3-5+ports no longer depends on > libssl1.1. > > Adrian Sadly, it looks like this wasn't the only dependency on libssl1.1 . Apparently libsnmp40 also depends on it. Thanks for all your efforts! Rick
Re: hfsprogs depends on libssl1.1 which is obsolete
On Wed, May 25, 2022, at 9:56 PM, John Paul Adrian Glaubitz wrote: > Hello! > > On 5/26/22 00:46, Rick Thomas wrote: >> The package libssl1.1 seems to have been removed from the powerpc/ppc64 >> archives. > > Yes, there is a transition going on towards OpenSSL 3.0. > >> However the package hfsprogs depends on it. >> >> hfsprogs is vital on powerpc/ppc34 . >> >> Am I missing something? > > hfsprogs needs to be rebuild against OpenSSL 3.0. I will take care of it. > > Adrian Thank you, sir!
hfsprogs depends on libssl1.1 which is obsolete
The package libssl1.1 seems to have been removed from the powerpc/ppc64 archives. However the package hfsprogs depends on it. hfsprogs is vital on powerpc/ppc34 . Am I missing something? Thanks! Rick
Re: systemd being pulled in during dist-upgrade
Try: # aptitude why systemd That may help answer the question. Rick On Sat, Feb 19, 2022, at 9:03 AM, Stan Johnson wrote: > Hello, > > On a PowerBook G3 Pismo, I just upgraded Debian SID: > # apt-get update > # apt-get upgrade > # apt-get dist-upgrade > > As part of the dist-upgrade (see below), at least one package requires > systemd as a dependency, causing the removal of sysvinit-core. > > After the dist-upgrade, I was able to remove systemd using a two-step > process: > # apt-get purge systemd > Reboot and repeat: > # apt-get purge systemd > > So there's a workaround, since I'm able to remove systemd eventually. > It's just an inconvenience for those of us who choose to run sysvinit > instead of systemd. IMO, systemd is slower and more intrusive on all > systems than sysvinit. And while it may be ok or even preferable for > larger (or corporate) systems, it is too slow for any m68k system or any > powerpc system that is slower than about a Pismo (500 MHz with 1 GiB > memory), and I don't want to use it there, either, since I use a common > Debian SID installation for all of my powerpc systems. > > I can restore from a backup and re-run the dist-upgrade if anyone knows > how to locate the specific package(s) triggering the dependency; it is > likely one or more of the 25 packagees upgraded below: > > - > # apt-get dist-upgrade > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Calculating upgrade... Done > The following packages were automatically installed and are no longer > required: > libperl5.32 libwebp6 linux-config-5.15 linux-source-5.15 > orphan-sysvinit-scripts perl-modules-5.32 > Use 'apt autoremove' to remove them. > The following packages will be REMOVED: > libwacom2 sysvinit-core > The following NEW packages will be installed: > dbus-user-session libjim0.79 libmbim-glib4 libmbim-proxy libmm-glib0 > libnss-systemd libpam-systemd libperl5.34 libpolkit-agent-1-0 > libqmi-glib5 libqmi-proxy libwacom-bin libwacom9 libwebp7 libxcvt0 > linux-source-5.16 modemmanager perl-modules-5.34 pkexec policykit-1 > polkitd systemd systemd-sysv systemd-timesyncd usb-modeswitch > usb-modeswitch-data xcvt > The following packages will be upgraded: > fwupd libgd3 libimlib2 libinput-bin libinput10 liblocale-gettext-perl > libmagickcore-6.q16-6 libtext-charwidth-perl libtext-iconv-perl > libtiff5 libwacom-common libwebpdemux2 libwebpmux3 linux-source > linux-source-5.15 perl perl-base xserver-xorg-core > xserver-xorg-input-libinput xserver-xorg-video-amdgpu > xserver-xorg-video-ati xserver-xorg-video-fbdev xserver-xorg-video-nouveau > xserver-xorg-video-radeon xserver-xorg-video-vesa > 25 upgraded, 27 newly installed, 2 to remove and 0 not upgraded. > Need to get 282 MB of archives. > After this operation, 222 MB of additional disk space will be used. > Do you want to continue? [Y/n] > - > > thanks > > -Stan Johnson
Re: Recipe for installing Debian on powerpc (G4, 32-bit) Mac? [failed installation -- looking for advice]
On Mon, Dec 27, 2021, at 2:56 AM, John Paul Adrian Glaubitz wrote: > If you really want to help me, I suggest that you perform systematic tests > with said > image and collect the results and summarize expected behavior and actual > behavior > of the software. Also, please always save the log file so that we can quickly > localize > the package in question that is responsible for the warning or error message. > > The more accurate your tests results are, the easier it is for me to localize > the bugs > and fix them. So, installation tests are indeed always welcome if they come > with usable > test results. OK, you're on! Please give me a list of the ISO images you'd like tested and what kinds of tests you want me to run. For example, I've recently tested the 2021-10-06 image with the LVM partition scheme, and given you a report on what I saw. Is that sufficient for that ISO/partition combination? Or is there some information missing that you'd like to have me add? Thanks for the opportunity to help! Enjoy! Rick
Re: Recipe for installing Debian on powerpc (G4, 32-bit) Mac? [failed installation -- looking for advice]
On Sat, Dec 18, 2021, at 12:19 AM, John Paul Adrian Glaubitz wrote: > Hello Rick! > ... > Why didn't you use any of the snapshots that you previously used and > that are known to work? ... > Use a different, known to work image. > OK, on Adrian's advice I used the NETINST iso from October 6, 2021, which I had successfully used on a mac-mini-G4 previously. In short, it worked. But the long story is more interesting: The CD booted fine. I chose the text-mode default installer. I accepted all the defaults until it came to time to partition the disk. I chose "guided - create LVM - use entire disk" for the partition scheme. All went as expected until it came time to write the partition tables to disk. At that point it complained about not having a /boot partition. I remembered hearing somewhere that a separate /boot partition was not strictly necessary as long as there was a /boot/grub partition that the firmware could access, because modern grub programs were able to find stuff from /boot even if it was buried in the root partition and the root partition was itself buried in an LVM partition. I verified that there was indeed a /boot/grub partition of type hfs in the proposed scheme. So I told it to ignore this problem and continue the installation without a /boot partition. It went ahead and created a /boot directory in the root partition, and put the kernel/initramfs and stuff there. A bit later it complained "Your boot partition is not located on the first primary partition of your hard disk ... Go back to the menu and correct the problem?" I remembered Adrian saying that we should ignore this, so I answered "no" It went ahead with configuring the package manager and installing Grub, all of which occurred without incident. I accepted all the default answers. It finished up and rebooted into the installed system without problem. Discussion: If it's true that modern grub can dig into an LVM containing root containing /boot, why is there any reason to want a separate /boot partition at all? Is this a feature that only applies to grub for powerpc? I really like the feature of having /boot be a directory in root, because it allows me to update kernels without first checking that there's enough space in the /boot partition for another kernel and initrd. I'd like to see it be at least an option, and (IMHO) preferably the default on all installs. This particular powermac-G4 is reserved for testing, so I'm happy to rest anything new from Adrian's workshop! Thanks for all the hard work, Rick
Re: Recipe for installing Debian on powerpc (G4, 32-bit) Mac? [failed installation -- looking for advice]
Installation report follows at end. On Wed, Dec 15, 2021, at 12:53 AM, Johannes Brakensiek wrote: > Am Dienstag, dem 14.12.2021 um 17:12 -0800 schrieb Rick Thomas: >> What is the URL for the latest Debian installer iso for a powerpc >> (32-bit, G4) macintosh? >> >> Is there anything I need to do (e.g. manually add a few lines to >> sources.list after/during the install) other than the the normal >> installation process (i.e. same as I would use for an amd64 machine)? >> >> Is there anything in particular you would like me to report on after >> I'm done with the installation? >> >> Thanks for all your hard work! >> >> Rick > > Hi Rick, > > you may find the last snapshot of the PowerPC ports image here: > https://cdimage.debian.org/cdimage/ports/snapshots/2021-10-20/ > > As far as I know you should be able to just run and install it. See my > note over here on how to boot from an USB stick. I don't know if a G4 > will be able to do that as well: > https://lists.debian.org/debian-powerpc/2021/01/msg00035.html > > Otherwise just burn a CD. > > If you encounter any issues just tell here. Adrian is doing all the > hard work of making the port work (thanks again!). It seems there is > not much manpower left for updating the documentation at the ports > site. I don't even know how this works in this Debian universe… (if > it's kinda straight forward I may try to update some information at > some point…) > > Good luck and happy hacking > Johannes So... I downloaded the "powerpc" netinst iso from ports/snapshots/2021-10-20/ and burned it to a CD-R (the CD-RW's I had on the shelf were so old they couldn't be recognized in the burner) It booted fine and I chose to do the default non-graphical install in non-expert mode. I accepted all the default options up to partitioning disks, where I chose "guided -- use entire disk" with "Separate /home partition" this resulted in a partition scheme with a hfs partition mounted on /boot/EFI but no /boot partition per se. I assume this means that /boot should be included in the root partition and that the new Grub would be able to find it, and the kernel/initramfs contained therein. So I accepted that scheme and allowed it to proceed. When it got to "Install the GRUB boot loader" it failed with this message: Unable to install Grub in /dev/sda3 Executing "grub-install /dev/sda3" failed This is a fatal error I called it to continue without installing grub and when it rebooted, it gave me the grub menu, but was unable to load the kernel and initramfs. Did I do something wrong? Next step is to boot from the CD into "rescue" mode so I can get the installation log files and post them here. Thanks for any help you can give! Rick
Re: Recipe for installing Debian on powerpc (G4, 32-bit) Mac?
On Wed, Dec 15, 2021, at 12:53 AM, Johannes Brakensiek wrote: > Am Dienstag, dem 14.12.2021 um 17:12 -0800 schrieb Rick Thomas: >> What is the URL for the latest Debian installer iso for a powerpc >> (32-bit, G4) macintosh? >> >> Is there anything I need to do (e.g. manually add a few lines to >> sources.list after/during the install) other than the the normal >> installation process (i.e. same as I would use for an amd64 machine)? >> >> Is there anything in particular you would like me to report on after >> I'm done with the installation? >> >> Thanks for all your hard work! >> >> Rick > > Hi Rick, > > you may find the last snapshot of the PowerPC ports image here: > https://cdimage.debian.org/cdimage/ports/snapshots/2021-10-20/ > > As far as I know you should be able to just run and install it. See my > note over here on how to boot from an USB stick. I don't know if a G4 > will be able to do that as well: > https://lists.debian.org/debian-powerpc/2021/01/msg00035.html > > Otherwise just burn a CD. The powermac G4s can't boot from USB, so I'll just burn a CD. (Or a CD-RW if I can...) > > If you encounter any issues just tell here. Adrian is doing all the > hard work of making the port work (thanks again!). It seems there is > not much manpower left for updating the documentation at the ports > site. I don't even know how this works in this Debian universe… (if > it's kinda straight forward I may try to update some information at > some point…) That would be a great service to the community! If you decide to do that and need some help, please feel free to ask me! > > Good luck and happy hacking > Johannes And for you the same! Rick
Recipe for installing Debian on powerpc (G4, 32-bit) Mac?
What is the URL for the latest Debian installer iso for a powerpc (32-bit, G4) macintosh? Is there anything I need to do (e.g. manually add a few lines to sources.list after/during the install) other than the the normal installation process (i.e. same as I would use for an amd64 machine)? Is there anything in particular you would like me to report on after I'm done with the installation? Thanks for all your hard work! Rick
But not on ppc64 [Re: Aptitude Problem PPC 32-bit]
I do not see this problem on my PowerMac G5, however. Curiouser and curiouser... Rick On Mon, Oct 11, 2021, at 3:17 PM, Rick Thomas wrote: > On Mon, Oct 11, 2021, at 3:41 AM, Dan Whitehouse wrote: >> I've got a Powermac G4 running debian ppc32. >> I've noticed a potential issue with aptitude. >> If I run "aptitude update" I notice it never seems to complete. >> It'll use 18% or so of my RAM (which is about 450mb I believe) but no >> CPU. It isn't swapping. >> >> Strace simply reveals: >> >> [pid 499] futex(0xafefc484, FUTEX_WAIT_PRIVATE, 1, NULL >> >> "apt update" and "apt upgrade" seem to be working fine. >> >> If anyone can assist I would be grateful. >> >> -- >> Dan Whitehouse (d...@dim-sum.org) > = > > I've noticed the same problem here. on a G4 Mac mini: > rbthomas@lil:~$ cat /proc/cpuinfo > processor : 0 > cpu : 7447A, altivec supported > clock : 1249.95MHz > revision : 1.2 (pvr 8003 0102) > bogomips : 83.24 > > timebase : 41620907 > platform : PowerMac > model : PowerMac10,1 > machine : PowerMac10,1 > motherboard : PowerMac10,1 MacRISC3 Power Macintosh > detected as : 287 (Mac mini) > pmac flags: 0010 > L2 cache : 512K unified > pmac-generation : NewWorld > Memory: 1024 MB > > and on a G4 PowerMac (Silver): > rbthomas@dillserver:~$ cat /proc/cpuinfo > processor : 0 > cpu : 7410, altivec supported > temperature : 36-39 C (uncalibrated) > clock : 533.32MHz > revision : 1.3 (pvr 800c 1103) > bogomips : 66.58 > > timebase : 33290001 > platform : PowerMac > model : PowerMac3,4 > machine : PowerMac3,4 > motherboard : PowerMac3,4 MacRISC2 MacRISC Power Macintosh > detected as : 69 (PowerMac G4 Silver) > pmac flags: 0010 > L2 cache : 1024K unified > pmac-generation : NewWorld > Memory: 1536 MB
Re: Aptitude Problem PPC 32-bit
On Mon, Oct 11, 2021, at 3:41 AM, Dan Whitehouse wrote: > I've got a Powermac G4 running debian ppc32. > I've noticed a potential issue with aptitude. > If I run "aptitude update" I notice it never seems to complete. > It'll use 18% or so of my RAM (which is about 450mb I believe) but no > CPU. It isn't swapping. > > Strace simply reveals: > > [pid 499] futex(0xafefc484, FUTEX_WAIT_PRIVATE, 1, NULL > > "apt update" and "apt upgrade" seem to be working fine. > > If anyone can assist I would be grateful. > > -- > Dan Whitehouse (d...@dim-sum.org) = I've noticed the same problem here. on a G4 Mac mini: rbthomas@lil:~$ cat /proc/cpuinfo processor : 0 cpu : 7447A, altivec supported clock : 1249.95MHz revision: 1.2 (pvr 8003 0102) bogomips: 83.24 timebase: 41620907 platform: PowerMac model : PowerMac10,1 machine : PowerMac10,1 motherboard : PowerMac10,1 MacRISC3 Power Macintosh detected as : 287 (Mac mini) pmac flags : 0010 L2 cache: 512K unified pmac-generation : NewWorld Memory : 1024 MB and on a G4 PowerMac (Silver): rbthomas@dillserver:~$ cat /proc/cpuinfo processor : 0 cpu : 7410, altivec supported temperature : 36-39 C (uncalibrated) clock : 533.32MHz revision: 1.3 (pvr 800c 1103) bogomips: 66.58 timebase: 33290001 platform: PowerMac model : PowerMac3,4 machine : PowerMac3,4 motherboard : PowerMac3,4 MacRISC2 MacRISC Power Macintosh detected as : 69 (PowerMac G4 Silver) pmac flags : 0010 L2 cache: 1024K unified pmac-generation : NewWorld Memory : 1536 MB
Re: Updated Debian Ports installation images 2021-09-21
On Fri, Sep 24, 2021, at 12:47 AM, Efraim Flashner wrote: > On Thu, Sep 23, 2021 at 11:30:26PM +0200, John Paul Adrian Glaubitz wrote: >> Hello! >> >> On 9/23/21 23:08, kristoffer...@tuta.io wrote: >> > I also made a fresh installation on another G4 (this time on Mini) with >> > mechanical HDD and stuck here: >> > i2c:powermac modalias failure /uni-n@800/i2c@f8001000/cereal >> >> What do you mean by "stuck here"? Does it boot up to his point and >> then nothing further happens? >> >> Please provide a little more information and context, i.e. what you >> did to get there and so on. >> >> Adrian >> > > I'm seeing something similar. using the attached screen of my iBook G4 > the last lines I see are > > [ 30.582886] fb0: switching to radeondrmfb from OFfb ATY,Snowy_ > [ 30.660875] b43 ssb0:0: firmware: direct-loading firmware b43/ucode5.fw > > and then the screen has been frozen for hours. I am able to ssh into the > machine anduse it from there but I have a minimum machine load of about 2. > I figured it was related to the firmware-amd-graphics package I installed. I'm seeing the same behavior on a Mac mini G4 (standard spinning rust hard drive, if it makes a difference). Screen freezes just at the time it switches from the open-firmware frame-buffer driver to something more native. I don't know what graphics chip it's using. I can ssh into the machine and run something to find out, if you can tell me what to run. Is there some way to tell it to not try to switch graphics drivers away from OF-FB? Thanks! Rick
Re: Bug#989645: /usr/sbin/grub-mkconfig: dpkg: error processing package linux-image-powerpc (--configure):
On Wed, Jun 9, 2021, at 9:42 PM, John Paul Adrian Glaubitz wrote: > On 6/10/21 12:14 AM, Rick Thomas wrote: > > So the only remaining question is "why was hfsprogs not automatically > > install on a G5 PowerMac?" > > See: https://lists.debian.org/debian-powerpc/2021/04/msg00129.html > > and: https://lists.debian.org/debian-powerpc/2021/05/msg00012.html Thanks. Now I understand the situation. I'll just add "install hfsprogs" to my list of things I have to do after installing on a PowerPC Mac. Enjoy! Rick
Re: Bug#989645: /usr/sbin/grub-mkconfig: dpkg: error processing package linux-image-powerpc (--configure):
On Wed, Jun 9, 2021, at 2:58 PM, Rick Thomas wrote: > > > On Wed, Jun 9, 2021, at 2:41 PM, John Paul Adrian Glaubitz wrote: > > Hello Rick! > > > > On 6/9/21 11:34 PM, Rick Thomas wrote: > > > You're right that /boot/grub somehow has gotten read-only. I didn't do > > > that > > > myself, so something else must have done that. Have you any clue you can > > > share > > > with me as to which package I should re-file this report against? > > You are too quick in assuming that there might be a bug somewhere. We don't > > know > > yet how and why the filesystem was re-mounted read-only. You should check > > your > > log files for any error messages or warnings. > > > > Normally the kernel warns you when a filesystem gets remounted read-only. > > > > Adrian > > For what it's worth, the original install was not from February. It > was the April 17th iso images instead. > > Searching "journalctl -b" I find: > > > Jun 09 01:42:55 kmac kernel: hfs: filesystem was not cleanly unmounted, > > running fsck.hfs is recommended. mounting read-only. > > I did have a brief power outage recently. Maybe that's what caused the > "not cleanly unmounted". > > I'll try unmounting it and running fsck.hfs... > Hmmm... > > root@kmac:~# fsck.hfs -f -C0 /boot/grub > > -bash: fsck.hfs: command not found > > Am I missing a package somewhere? > Rick Yep, I was missing hfsprogs. I installed that and was able to do the fsck.hfs, then remounted /boot/grub and all was well. So the only remaining question is "why was hfsprogs not automatically install on a G5 PowerMac?" Thanks to all for your help in fixing this! Rick
Re: Bug#989645: /usr/sbin/grub-mkconfig: dpkg: error processing package linux-image-powerpc (--configure):
On Wed, Jun 9, 2021, at 2:41 PM, John Paul Adrian Glaubitz wrote: > Hello Rick! > > On 6/9/21 11:34 PM, Rick Thomas wrote: > > You're right that /boot/grub somehow has gotten read-only. I didn't do that > > myself, so something else must have done that. Have you any clue you can > > share > > with me as to which package I should re-file this report against? > You are too quick in assuming that there might be a bug somewhere. We don't > know > yet how and why the filesystem was re-mounted read-only. You should check your > log files for any error messages or warnings. > > Normally the kernel warns you when a filesystem gets remounted read-only. > > Adrian For what it's worth, the original install was not from February. It was the April 17th iso images instead. Searching "journalctl -b" I find: > Jun 09 01:42:55 kmac kernel: hfs: filesystem was not cleanly unmounted, > running fsck.hfs is recommended. mounting read-only. I did have a brief power outage recently. Maybe that's what caused the "not cleanly unmounted". I'll try unmounting it and running fsck.hfs... Hmmm... > root@kmac:~# fsck.hfs -f -C0 /boot/grub > -bash: fsck.hfs: command not found Am I missing a package somewhere? Rick
Bug#989645: /usr/sbin/grub-mkconfig: dpkg: error processing package linux-image-powerpc (--configure):
Package: grub-common
Version: 2.04-18
Severity: grave
File: /usr/sbin/grub-mkconfig
Justification: renders package unusable
X-Debbugs-Cc: debian-powerpc@lists.debian.org, glaub...@physik.fu-berlin.de,
rbtho...@pobox.com
This is what happens when I attempt to do "aptitude full-upgrade" on my PowerPC
machine:
root@dillserver:/home/rbthomas# aptitude full-upgrade
The following partially installed packages will be configured:
linux-image-5.10.0-7-powerpc linux-image-powerpc
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Setting up linux-image-5.10.0-7-powerpc (5.10.40-1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.10.0-7-powerpc
/etc/kernel/postinst.d/zz-update-grub:
/usr/sbin/grub-mkconfig: 257: cannot create /boot/grub/grub.cfg.new: Read-only
file system
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 2
dpkg: error processing package linux-image-5.10.0-7-powerpc (--configure):
installed linux-image-5.10.0-7-powerpc package post-installation script
subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-powerpc:
linux-image-powerpc depends on linux-image-5.10.0-7-powerpc (= 5.10.40-1);
however:
Package linux-image-5.10.0-7-powerpc is not configured yet.
dpkg: error processing package linux-image-powerpc (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-image-5.10.0-7-powerpc
linux-image-powerpc
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up linux-image-5.10.0-7-powerpc (5.10.40-1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.10.0-7-powerpc
/etc/kernel/postinst.d/zz-update-grub:
/usr/sbin/grub-mkconfig: 257: cannot create /boot/grub/grub.cfg.new: Read-only
file system
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 2
dpkg: error processing package linux-image-5.10.0-7-powerpc (--configure):
installed linux-image-5.10.0-7-powerpc package post-installation script
subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-powerpc:
linux-image-powerpc depends on linux-image-5.10.0-7-powerpc (= 5.10.40-1);
however:
Package linux-image-5.10.0-7-powerpc is not configured yet.
dpkg: error processing package linux-image-powerpc (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-image-5.10.0-7-powerpc
linux-image-powerpc
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/mapper/dill-root / ext4 rw,relatime,errors=remount-ro 0 0
/dev/mapper/dill-home /home ext4 rw,relatime 0 0
/dev/sda3 /boot ext2 rw,relatime 0 0
/dev/sda2 /boot/grub hfs ro,relatime,uid=0,gid=0 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_apple
insmod lvm
insmod ext2
set
root='lvmid/KyeuOm-Fceg-PCoI-LcmV-eVLL-RnL7-Xh0WT4/Ut9qE2-72vC-tTDE-XyVH-6Z0i-GXy3-lyyiCh'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint='lvmid/KyeuOm-Fceg-PCoI-LcmV-eVLL-RnL7-Xh0WT4/Ut9qE2-72vC-tTDE-XyVH-6Z0i-GXy3-lyyiCh'
9151f254-2918-4435-bd1c-9a0e70edfdf7
else
search --no-floppy --fs-uuid --set=root 9151f254-2918-4435-bd1c-9a0e70edfdf7
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_sty
G4 MDD report (finally) Re: Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly
Here's the data from the G4 MDD. Sorry for the delay getting it out! rbthomas@macswell:~$ cat /proc/cpuinfo processor : 0 cpu : 7455, altivec supported clock : 1416.61MHz revision: 3.3 (pvr 8001 0303) bogomips: 83.31 processor : 1 cpu : 7455, altivec supported clock : 1416.61MHz revision: 3.3 (pvr 8001 0303) bogomips: 83.31 total bogomips : 166.63 timebase: 41659125 platform: PowerMac model : PowerMac3,6 machine : PowerMac3,6 motherboard : PowerMac3,6 MacRISC3 Power Macintosh detected as : 129 (PowerMac G4 Windtunnel) pmac flags : 0010 L2 cache: 256K unified pmac-generation : NewWorld Memory : 2048 MB rbthomas@macswell:~$ cat /proc/version Linux version 5.10.0-6-powerpc-smp (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.28-1 (2021-04-09) rbthomas@macswell:~$ lsmod | grep wind therm_windtunnel7229 0 The fans come on at low speed when I give the CPU a short workout. I haven't tried a long-term CPU intensive task yet. Hope this helps! Rick On Tue, Apr 27, 2021, at 3:55 PM, Rick Thomas wrote: > > > On Tue, Apr 27, 2021, at 12:15 AM, John Paul Adrian Glaubitz wrote:> > > On 4/27/21 8:54 AM, Rick Thomas wrote: > > > I'll look around and see if I have any MDD (mirror drive door -- the type > > > in the > > > original bugreport) machines. If so, I'll try to find some time to > > > install Adrian's > > > latest and report back. > > > > OK, thank you. Maybe someone else with a machine that previously had > > this issue can also > > comment so that we can be sure the issue has been fixed. > > > > Rick, maybe you can check whether the windfarm module(s) get(s) loaded > > on your machine? > > > > # lsmod |grep windfarm > > On the G4 (which is _not_ the MDD) I get nothing from that > > On the G5 I get: > > rbthomas@kmac:~$ lsmod | grep wind > windfarm_smu_sat8626 0 > windfarm_ad7417_sensor 7755 0 > windfarm_fcu_controls12227 0 > windfarm_cpufreq_clamp 3881 0 > windfarm_pm72 14329 0 > windfarm_pid3256 1 windfarm_pm72 > windfarm_lm75_sensor 5350 0 > windfarm_max6690_sensor 4600 0 > windfarm_core 11920 7 > windfarm_cpufreq_clamp,windfarm_fcu_controls,windfarm_max6690_sensor,windfarm_smu_sat,windfarm_ad7417_sensor,windfarm_pm72,windfarm_lm75_sensor > > Hope that helps. > Rick > > PS: I do have a MDD, but I haven't yet tried Adrian's latest on it. > Maybe later today, maybe it'll have to wait for the weekend. >
Re: Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly
Hi William! On Thu, Apr 29, 2021, at 11:05 AM, William Bonnet wrote: > > The PowerMac G5 users on this list are kindly asked to confirm the bug > > has been fixed. Until then, I'll reopen it. > > I am running the latest version (5.10.0-6-sparc64-smp #1 SMP Debian > 5.10.28-1 (2021-04-09) sparc64) from the ports repo and it runs ok on two > G5 Thanks for the report. Can you run this: "lsmod | grep wind" (without the quotes) on one or both of the G5s, and report the results back here? Thanks! Rick
Re: Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly
On Tue, Apr 27, 2021, at 12:15 AM, John Paul Adrian Glaubitz wrote:> > On 4/27/21 8:54 AM, Rick Thomas wrote: > > I'll look around and see if I have any MDD (mirror drive door -- the type > > in the > > original bugreport) machines. If so, I'll try to find some time to install > > Adrian's > > latest and report back. > > OK, thank you. Maybe someone else with a machine that previously had > this issue can also > comment so that we can be sure the issue has been fixed. > > Rick, maybe you can check whether the windfarm module(s) get(s) loaded > on your machine? > > # lsmod |grep windfarm On the G4 (which is _not_ the MDD) I get nothing from that On the G5 I get: rbthomas@kmac:~$ lsmod | grep wind windfarm_smu_sat8626 0 windfarm_ad7417_sensor 7755 0 windfarm_fcu_controls12227 0 windfarm_cpufreq_clamp 3881 0 windfarm_pm72 14329 0 windfarm_pid3256 1 windfarm_pm72 windfarm_lm75_sensor 5350 0 windfarm_max6690_sensor 4600 0 windfarm_core 11920 7 windfarm_cpufreq_clamp,windfarm_fcu_controls,windfarm_max6690_sensor,windfarm_smu_sat,windfarm_ad7417_sensor,windfarm_pm72,windfarm_lm75_sensor Hope that helps. Rick PS: I do have a MDD, but I haven't yet tried Adrian's latest on it. Maybe later today, maybe it'll have to wait for the weekend.
Re: Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly
On Mon, Apr 26, 2021, at 10:45 PM, John Paul Adrian Glaubitz wrote: > On 4/27/21 2:07 AM, Rick Thomas wrote: > > I've got the latest (Apr 17) running on my G5 right now. No problems. > > Rick, you should just confirm that this particular problem is fixed but I > assume > that this is the case? I've got a PowerMac G5 running the latest install from Adrian. It does not have any problem with fans running at high speed for prolonged time. rbthomas@kmac:~$ cat /proc/version ; cat /proc/cpuinfo Linux version 5.10.0-6-powerpc64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.28-1 (2021-04-09) processor : 0 cpu : PPC970FX, altivec supported clock : 2000.00MHz revision: 3.0 (pvr 003c 0300) processor : 1 cpu : PPC970FX, altivec supported clock : 2000.00MHz revision: 3.0 (pvr 003c 0300) timebase: platform: PowerMac model : PowerMac7,3 machine : PowerMac7,3 motherboard : PowerMac7,3 MacRISC4 Power Macintosh detected as : 336 (PowerMac G5) pmac flags : L2 cache: 512K unified pmac-generation : NewWorld Looking at the original bugreport, this in not the type of machine about which the report was filed. I also have a PowerMac G4 Silver running the 32-bit install from Feb 2, 2021 from Adrian. It also does not have any problem with fans running at high speed. rbthomas@dillserver:~$ cat /proc/version ; cat /proc/cpuinfo Linux version 5.10.0-6-powerpc (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 Debian 5.10.28-1 (2021-04-09) processor : 0 cpu : 7410, altivec supported temperature : 38-40 C (uncalibrated) clock : 533.32MHz revision: 1.3 (pvr 800c 1103) bogomips: 66.58 timebase: 33290001 platform: PowerMac model : PowerMac3,4 machine : PowerMac3,4 motherboard : PowerMac3,4 MacRISC2 MacRISC Power Macintosh detected as : 69 (PowerMac G4 Silver) pmac flags : 0010 L2 cache: 1024K unified pmac-generation : NewWorld Memory : 1536 MB Unfortunately, this is also not the type of machine from the original bugreport. I'll look around and see if I have any MDD (mirror drive door -- the type in the original bugreport) machines. If so, I'll try to find some time to install Adrian's latest and report back. Rick
Re: Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly
I've got the latest (Apr 17) running on my G5 right now. No problems. Rick rbthomas@kmac:~$ cat /proc/version Linux version 5.10.0-6-powerpc64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.28-1 (2021-04-09)
Re: Updated installer images 2021-04-16
On Thu, Apr 22, 2021, at 7:16 PM, Rick Thomas wrote: > I suspect that this difference is what's producing the "error: can't > open device" messages on the ppc64, and why they do not appear on the > amd64. If I did a manual partitioning install on the amd64 that > mimicked the layout of the ppc64, I suspect I would probably see the > same "can't open device" error messages there as well. (I do plan to > try that, and I'll report what I find) Well... "Curiouser and curiouser!" I did an expert install on my amd64 VM and accepted defaults up to the partitioning phase. In the partitioning phase, I chose to do a manual partitioning. In my manual partitioning I created an ext2 partition on /dev/sda1 with mount point /boot/grub. The rest of the installation went into an LVM partition with three volumes for root, /home, and swap. (So /boot is a directory in the root volume. If grub wants a kernel and initrd, it has to dig around in the LVM to find them) Unlike the ppc64 installation, the installer did not complain about this setup. (The ppc64 installation complained that there was no partition for /boot to mount on) and happily went ahead with installing a basic (non-gui) system with ssh. Somewhat surprisingly, when it came time for the reboot, all went smoothly. There were no "error: can't open device" messages at all, and it proceeded smoothly to a login prompt. Hope this helps! Rick
Re: Updated installer images 2021-04-16
On Wed, Apr 21, 2021, at 4:26 AM, John Paul Adrian Glaubitz wrote: > >> This issue might not even specific to PowerMacs, so it > >> would make more > >> sense first to test this on x86 systems and report a bug against > >> src:grub2 or partman-lvm > >> if the issue shows there as well. > > > > I'll try that. Would the "daily build" sid iso for amd64 have the same > > version of grub2 as your ppc64 iso? > > This should do the trick, yes: > > > https://cdimage.debian.org/cdimage/daily-builds/daily/current/amd64/iso-cd/ I just tried that on an amd64 VM. I chose the default install from the installer's menu. When it got to partitioning the disk, I chose use whole disk and set up LVM. I chose separate /home logical volume. All went well, and when it came to reboot from the newly installed disk, I did not see any of the messages that I saw on the ppc64 PowerMac G5 install. However: The amd64 install created a separate /boot partition on /dev/sda1. In addition to kernel and initrd, it contained a /boot/grub directory. > rbthomas@burnout:~$ df | grep -v tmpfs ; lsblk > Filesystem 1K-blocks Used Available Use% Mounted on > udev 1995140 0 1995140 0% /dev > /dev/mapper/burnout--vg-root 6930164 962864 5593952 15% / > /dev/sda1 480618 48562407122 11% /boot > /dev/mapper/burnout--vg-home 12028924 40 11396052 1% /home > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > sda 8:00 20G 0 disk > |-sda1 8:10 487M 0 part /boot > |-sda2 8:201K 0 part > `-sda5 8:50 19.5G 0 part >|-burnout--vg-root 254:00 6.8G 0 lvm / >|-burnout--vg-swap_1 254:10 976M 0 lvm [SWAP] >`-burnout--vg-home 254:20 11.8G 0 lvm /home > sr0 11:01 1024M 0 rom > rbthomas@burnout:~$ The ppc64 install, on the other hand, created a separate hfs type /boot/grub partition on /dev/sda2, and let the parent /boot be a directory in the ext4 root partition/logical-volume > rbthomas@kmac:~$ df | grep -v tmpfs ; lsblk > Filesystem1K-blocksUsed Available Use% Mounted on > udev1874880 0 1874880 0% /dev > /dev/mapper/kmac--vg-root 19047080 1372148 16682064 8% / > /dev/sda2249988 11228238760 5% /boot/grub > /dev/mapper/kmac--vg-home 158766164 60 150628376 1% /home > NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT > sda 8:00 232.9G 0 disk > |-sda18:10 31.5K 0 part > |-sda28:20 244.1M 0 part /boot/grub > |-sda38:30 232.6G 0 part > | |-kmac--vg-root 254:10 18.6G 0 lvm / > | |-kmac--vg-swap_1 254:2010G 0 lvm [SWAP] > | `-kmac--vg-home 254:30 154.9G 0 lvm /home > `-sda48:40 56.5K 0 part > sdb 8:16 0 931.5G 0 disk > `-backup-lvol0 254:00 500G 0 lvm > sr0 11:01 1024M 0 rom > rbthomas@kmac:~$ I suspect that this difference is what's producing the "error: can't open device" messages on the ppc64, and why they do not appear on the amd64. If I did a manual partitioning install on the amd64 that mimicked the layout of the ppc64, I suspect I would probably see the same "can't open device" error messages there as well. (I do plan to try that, and I'll report what I find) Rick
Re: Updated installer images 2021-04-16
On Tue, Apr 20, 2021, at 2:31 AM, John Paul Adrian Glaubitz wrote: > I don't understand the hurry to > make everything > perfect at once. I'm sorry if it seems that way. That is not my intent. I'm just reporting what I see. It's definitely not mission critical. The machine still boots, just with these puzzling messages. You can ignore it if you want. >This issue might not even specific to PowerMacs, so it > would make more > sense first to test this on x86 systems and report a bug against > src:grub2 or partman-lvm > if the issue shows there as well. I'll try that. Would the "daily build" sid iso for amd64 have the same version of grub2 as your ppc64 iso? Thanks for all your efforts! Rick > Adrian
Re: Updated installer images 2021-04-16
On Mon, Apr 19, 2021, at 11:33 PM, John Paul Adrian Glaubitz wrote: > On 4/20/21 3:42 AM, Rick Thomas wrote: > > (1) Can we get rid of the seemingly unnecessary error message about not > > having a /boot partition? > > As I said, it's a known issue and I'm going to fix it at some point. But > since I am doing this in my freetime and I'm not getting paid for that, > I'm not working on it every day. > > Fixing installer issues is not trivial and requires lots of testing, getting > it working last week took me four days and 10-15 installation runs, so I > cannot work on it every day. Understood. I'm grateful for the work you can afford to do, and I don't intend to pressure you. I'm just trying to do my part -- sorry, I'm not a developer, so I can't help with the code -- but I will do what I can, which is to provide my observations as I test your code. In particular, the error message mentioned above comes from the partitioner section of the installer. Presumably, this message, and the check that issues it, are relics of the past when grub was not able to dig into LVM partitions to find the kernel and initrd. Now that grub understands LVM, the check and associated message are no longer necessary. > > (2) Are the messages necessary that complain about "can't open device" and > > "press any key to continue"? > > I don't know the context of these. You need to provide more context, use a > net console if you cannot access the logs otherwise. The context of these messages is immediately after the "bong" when the machine reboots itself -- after grub has loaded and displayed its menu but before the kernel and initrd are loaded. I'm guessing that they come from grub and are byproducts of the process of grub digging around in the LVM looking for the /boot directory. If that explanation doesn't clear up the ambiguity, I'll get out my camera and take some pictures of the screen for you. Is there some way to tell grub to log its progress to some durable media like a USB stick? > Adrian Rick
Re: Updated installer images 2021-04-16
Well... I'm not very good at letting well enough alone, so I tried installing again. This time I used the "default install" and when it came to partitioning, I chose the LVM option. This time, it complained that there was no partition for /boot (though when I poked around a bit, there _was_ an hfs partition for /boot/grub .) It asked if I wanted to continue without /boot and I answered "yes". It continued and installed grub using the /boot/grub partition and the /boot directory in the root LVM partition. Then it rebooted. I was fully expecting it to get hung up unable to find /boot partition and so be unable to get the initrd and kernel, but (lo and behold!) the new grub seems to be able to dig inside of an LVM and find what it needs! ((-: It continued with an error message (twice) about "can't open device" (I don't know which device it's talking about) and paused with "Press any key to continue". While I was puzzling what to do, the pause timed out and it continued without my hitting any key. And to my great surprise and glee, it booted and gave me a "login:" prompt! So... (0) Congratulations! (1) Can we get rid of the seemingly unnecessary error message about not having a /boot partition? (2) Are the messages necessary that complain about "can't open device" and "press any key to continue"? (3) If not, can we get rid of them? Big *thanks* for this! Rick On Mon, Apr 19, 2021, at 12:35 AM, Rick Thomas wrote: > I tried it this afternoon on my PowerMac G5 - PowerMac7,3. Works > great! I used the default installation and "all in one partition" > partitioning. Let me know if you would like me to try something else. > > Thanks so much for all your work! This is fantastic... > > Enjoy! > Rick > > On Fri, Apr 16, 2021, at 2:40 AM, John Paul Adrian Glaubitz wrote: > > Hello! > > > > As promised, new images: > > > > > https://cdimage.debian.org/cdimage/ports/snapshots/2021-04-16/ > > > > ppc64 should install fine on PowerMac G5 now. > > > > Adrian > > > > -- > > .''`. John Paul Adrian Glaubitz > > : :' : Debian Developer - glaub...@debian.org > > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 > > > > > >
Re: Updated installer images 2021-04-16
I tried it this afternoon on my PowerMac G5 - PowerMac7,3. Works great! I used the default installation and "all in one partition" partitioning. Let me know if you would like me to try something else. Thanks so much for all your work! This is fantastic... Enjoy! Rick On Fri, Apr 16, 2021, at 2:40 AM, John Paul Adrian Glaubitz wrote: > Hello! > > As promised, new images: > > > https://cdimage.debian.org/cdimage/ports/snapshots/2021-04-16/ > > ppc64 should install fine on PowerMac G5 now. > > Adrian > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaub...@debian.org > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 > >
Re: Updated installer images 2021-04-16 🎉
On Fri, Apr 16, 2021, at 5:30 AM, John Paul Adrian Glaubitz wrote: > On 4/16/21 1:57 PM, Johannes Brakensiek wrote: > > > > On 16 Apr 2021, at 13:54, John Paul Adrian Glaubitz wrote: > > > >> But the image is blessed in HFS vocabulary. If you insert such a CD and > >> press the > >> key during boot, the CD will be selectable during boot. > > > > Ok, good to know. Then I suppose the Mac’s firmware just won’t detect it if > > it’s copied to a USB stick? > > It could be that the blessing gets lost when putting it onto a USB disk. > > I verified that when burnt to a CD, the image will show up in > menu with > an icon (which we can switch to a Debian swirl maybe later). But I > don't know about > OpenFirmware at the moment to know how to reproduce this behavior with > a USB stick. I vaguely remember having read somewhere that the "boot with option key" on PowerPC machines does not examine USB disks for bootable partitions. It does know about Firewire disks, and ATA/SATA disks, but just not USB disks. The workaround is to boot directly into OpenFirmware (CMD-OPT-O-F) and give it a boot command tailored for your USB disk. For other options see -- http://www.jacsoft.co.nz/Tech_Notes/Mac_Keys.shtml and the apple tech info library articles -- https://developer.apple.com/library/archive/navigation/index.html#topic=Technical+Notes§ion=Resource+Types Hope that helps!
Re: Package libnss3_3.60-1_ppc64.deb requires Power-7 hardware
Great news! Thanks very much for all your efforts, Adrian! When can we expect the next iteration on a grub-based installer DVD for the G5 Macs? I'm anxious to give it a try! Rick On Tue, Apr 6, 2021, at 2:09 AM, John Paul Adrian Glaubitz wrote: > Hello Carsten! > > On 1/17/21 12:06 AM, Carsten Jacobi wrote: > > For all who still want to run Debian 64bit on a G5, the newest > > libnss3-Package > > breaks some prominent applications like firefox or thunderbird on that > > machine. > > My fix for that just got accepted upstream [1], so it will be hopefully > be merged > after the integration tests have been successful. If all goes well, the > fix should > be part of the 3.64 release. > > Adrian > > > [1] https://phabricator.services.mozilla.com/D105354 > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaub...@debian.org > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 > >
Re: Some details on the bootloader installation for PowerMacs
On Sat, Feb 13, 2021, at 4:43 PM, Jeffrey Walton wrote: > On Sat, Feb 13, 2021 at 7:05 PM John Paul Adrian Glaubitz > wrote: > > > > On 2/6/21 7:25 PM, John Paul Adrian Glaubitz wrote: > > > On 2/5/21 9:21 PM, John Paul Adrian Glaubitz wrote: > > >> The next step will be adding a hfsprogs-udeb package which allows the > > >> hfsprogs > > >> package to be used directly by debian-installer. Every filesystem > > >> supported > > >> by debian-installer, i.e. that can be chosen to format a partition > > >> during installation, > > >> has such a udeb package. > > > > > > I have a preliminary hfsprogs-udeb package now: > > > > Just uploaded that one to unstable after cleaning everything up and > > verifying it works correctly [1]. > > > > > I will work on partman-hfs next. > > > > That needs a little more work but should be within the next days. > > Awesome, great work. > > Jeff I'll second that! Big big thanks, Adrian. I'm really looking forward to being able to use the results of all your hard work! Rick
Works (with a small tweek) on ppc64! [Re: Workaround for installing Debian onto PowerMacs (2020-02-02 image)]
On Tue, Feb 2, 2021, at 4:22 AM, John Paul Adrian Glaubitz wrote:
> Hello!
>
> For anyone wanting to install a current Debian unstable snapshot onto their
> PowerMacs, I'm going to write down a short guide how to make sure GRUB
> gets installed properly (in case the installation fails).
>
> Use either the powerpc or ppc64 image depending on your machine type:
>
> > https://cdimage.debian.org/cdimage/ports/snapshots/2021-02-02/
>
> Install normally. After GRUB has been installed and the installation has
> finished, don't reboot the machine yet.
>
> Switch to another console and enter the following commands:
>
> # mount -o bind /dev/ /target/dev/
> # mount -o bind /proc/ /target/proc/
> # mount -o bind /sys/ /target/sys/
>
> # chroot /target/
> # bash
> # grub-install --macppc-directory=/boot/grub
> # export boot_device=$()
> # nvsetenv boot-device ${boot_device%%BootX}\\grub
>
> # exit
> # exit
> # umount /target/dev
> # umount /target/proc
> # umount /target/sys
> # exit
>
> Then switch back to the installer console.
The discussion of ofpathname vs ofpath got m to thinking.
So I installed the 2021-02-02 CD on my powermac G5, and applied Adrian's
workaround with the minor tweak of, in addition to changing "Bootx" to "grub",
changing the "-1" to "1"... as below
change
/ht@0,f200/pci@5/k2-sata-root@c/@-1/@0:2
to:
/ht@0,f200/pci@5/k2-sata-root@c/@1/@0:2
then allowed the installer to reboot.
Lo and behold! It works!
Many thanks Adrian! I'm really looking forward to being able to test an
installer CD with these fixes incorporated...
Rick
Re: Workaround for installing Debian onto PowerMacs (2020-02-02 image)
On Mon, Feb 8, 2021, at 11:06 PM, Jeffrey Walton wrote: > A small problem... > After install the machine reboots automatically. We are not given an > opportunity to stop the reboot. In fact, we are not even told a reboot > is going to happen. Maybe the installer needs a step that confirms the > reboot with a Yes/No prompt? > The issue is aggravated by OpenFirmware behavior. Each command I issue > at the OF prompt results in a "corrupt disk" message. I can't even > eject the cd. OF tries to load the OS for each command I issue. Two things you need to know: 1) The grub menu, that you see when the installer CD first boots up, offers "expert" mode. If you're not familiar with it, this makes the install process more granular, so you have more control over the details and timing. In order to apply Adrian's workaround, you need to use expert mode. It's not completely obvious, but you should be able to figure it out -- usually the default answer is the best, but keep your eyes open and try to understand each step. 2) Just before the reboot (at the stage you are arguing should be more explicit about rebooting) *before* you answer "continue" you need to hit -F2 to get yourself a shell running in the installer environment. At that point, you can execute the steps of Adrian's workaround. When you are finished with that, you can switch back to the installer menu by hitting -F1 . Then answer "continue" and it will reboot -- hopefully into the system you just installed. Hope that helps! Rick
Re: Workaround for installing Debian onto PowerMacs (2020-02-02 image)
Having done the complete install (including the workaround steps) yesterday,
and not wanting to spend the time to do it all again, I booted into rescue mode
and executes a shell in the /target system.
I had to manually mount /boot/grub from /dev/sa2 because the rescue mode didn't
do it automatically.
Then to get the information Adrian wanted, I executed the following script
# df -TP
Filesystem Type 1024-blocksUsed Available Capacity Mounted on
/dev/kmac/root ext419092136 1156780 16942488 7% /
devtmpfs devtmpfs 1881600 0 1881600 0% /dev
tmpfs tmpfs 4066561664404992 1% /run
/dev/sda3 ext2 242093 64566165028 29% /boot
/dev/sda2 hfs 1249906510118480 6% /boot/grub
# ofpathname /dev/sda2
/ht@0,f200/pci@5/k2-sata-root@c/@-1/@0:2
# nvram --print-config=boot-device
/ht@0,f200/pci@5/k2-sata-root@c/@-1/@0:2,\grub
# grub-install --macppc-directory=/boot/grub
Installing for powerpc-ieee1275 platform.
Installation finished. No error reported.
# export boot_device=$(nvram --print-config=boot-device)
#nvsetenv boot-device ${boot_device%%BootX}\\grub
# nvram --print-config=boot-device
/ht@0,f200/pci@5/k2-sata-root@c/@-1/@0:2,\grub
# ls -l /boot/grub
total 88
drwxr-xr-x 1 root root 3 Feb 6 15:46 System
drwxr-xr-x 1 root root 3 Feb 6 15:46 fonts
-rw-r--r-- 1 root root 82760 Feb 7 15:30 grub
-r--r--r-- 1 root root 6018 Feb 6 15:46 grub.cfg
-rw-r--r-- 1 root root 1024 Feb 6 15:46 grubenv
-rw-r--r-- 1 root root 0 Feb 6 15:46 mach_kernel
drwxr-xr-x 1 root root 217 Feb 7 15:30 powerpc-ieee1275
Still, when I rebooted without the installer CD, I got the folder icon with
blinking question mark.
Hope it helps!
Rick
Re: Workaround for installing Debian onto PowerMacs (2020-02-02 image)
On Sun, Feb 7, 2021, at 12:43 AM, John Paul Adrian Glaubitz wrote: > On 2/7/21 1:18 AM, Rick Thomas wrote: > > But when it rebooted, all I got was a folder icon with a blinking question > > mark. > > Did you verify that: > > - /ht@0,f200/pci@5/k2-sata-root@c/@-1/@0:2 corresponds to the partition > where /boot/grub is mounted and GRUB was installed? What would be the correct way to do that? > > - Is the filesystem mounted to /boot/grub formatted as HFS? yes, I did check. And yes, it is formatted as hfs. > > - Does the folder /boot/grub contain the GRUB files, especially "grub"? I'll check. > > I think the mechanism is rather easy to understand, you need to make sure the > GRUB files are present, placed on an HFS filesystem and the firmware boot > entry is pointing to it. > > But again, this is just a hack, the proper bootloader installation is still > work-in-progress. I await the culmination of that work in progress with great anticipation! Let me know if there's anything you would like tested! > Adrian Thanks for all your efforts! Rick
Re: Workaround for installing Debian onto PowerMacs (2020-02-02 image) -- Works on 32-bit powerpc G4!
clock533.32MHz motherboard PowerMac3,4 MacRISC2 MacRISC Power Macintosh detected as 69 (PowerMac G4 Silver) VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV250 [Radeon 9000 Series] (rev 01) > On Sat, Feb 6, 2021, at 8:59 PM, Christian Calderon wrote: > Question for Rick, which G4 are you using and what graphics card? I'm > thinking about doing this on my FW800. > > ~ Christian Calderon Hope it helps! Rick
Re: Workaround for installing Debian onto PowerMacs (2020-02-02 image) -- Works on 32-bit powerpc G4!
On Tue, Feb 2, 2021, at 4:22 AM, John Paul Adrian Glaubitz wrote:
> Hello!
>
> For anyone wanting to install a current Debian unstable snapshot onto their
> PowerMacs, I'm going to write down a short guide how to make sure GRUB
> gets installed properly (in case the installation fails).
>
> Use either the powerpc or ppc64 image depending on your machine type:
>
> > https://cdimage.debian.org/cdimage/ports/snapshots/2021-02-02/
>
> Install normally. After GRUB has been installed and the installation has
> finished, don't reboot the machine yet.
>
> Switch to another console and enter the following commands:
>
> # mount -o bind /dev/ /target/dev/
> # mount -o bind /proc/ /target/proc/
> # mount -o bind /sys/ /target/sys/
>
> # chroot /target/
> # bash
> # grub-install --macppc-directory=/boot/grub
> # export boot_device=$(nvram --print-config=boot-device)
> # nvsetenv boot-device ${boot_device%%BootX}\\grub
>
> # exit
> # exit
> # umount /target/dev
> # umount /target/proc
> # umount /target/sys
> # exit
>
> Then switch back to the installer console.
>
> I am going to fix the GRUB installation for PowerMacs in the next weeks
> once and
> for all. I have read through the grub-installer code again and now have
> a rough
> idea for a proper fix for the issue. The current fix that Frank
> Scheiner authored
> and that we have been using the past months is actually a bit hacky and
> unreliable
> which is why I will take another approach which will involve a udeb for
> hfsprogs
> so that partman-auto can set up the HFS partition automatically.
>
> Adrian
So I tried this: installed my G4 powerpc mac from the "powerpc" (32-bit) image
at the location mentioned by Adrian, then executing the suggested "workaround"
steps. When it rebooted, it showed the grub menu and booted into the system I
had just before installed.
So... "curiouser and curiouser!" it works on 32-bit, but not on 64-bit.
Rick
Re: Workaround for installing Debian onto PowerMacs (2020-02-02 image)
On Tue, Feb 2, 2021, at 4:22 AM, John Paul Adrian Glaubitz wrote:
> Hello!
>
> For anyone wanting to install a current Debian unstable snapshot onto their
> PowerMacs, I'm going to write down a short guide how to make sure GRUB
> gets installed properly (in case the installation fails).
>
> Use either the powerpc or ppc64 image depending on your machine type:
>
> > https://cdimage.debian.org/cdimage/ports/snapshots/2021-02-02/
>
> Install normally. After GRUB has been installed and the installation has
> finished, don't reboot the machine yet.
>
> Switch to another console and enter the following commands:
>
> # mount -o bind /dev/ /target/dev/
> # mount -o bind /proc/ /target/proc/
> # mount -o bind /sys/ /target/sys/
>
> # chroot /target/
> # bash
> # grub-install --macppc-directory=/boot/grub
> # export boot_device=$(nvram --print-config=boot-device)
> # nvsetenv boot-device ${boot_device%%BootX}\\grub
>
> # exit
> # exit
> # umount /target/dev
> # umount /target/proc
> # umount /target/sys
> # exit
>
> Then switch back to the installer console.
Here you are...
~ # mount -o bind /dev/ /target/dev/
~ # mount -o bind /proc/ /target/proc/
~ # mount -o bind /sys/ /target/sys/
~ # chroot /target/
# /bin/bash
root@kmac:/# nvram --print-config=boot-device
/ht@0,f200/pci@5/k2-sata-root@c/@-1/@0:2,\grub
root@kmac:/# grub-install --macppc-directory=/boot/grub
Installing for powerpc-ieee1275 platform.
Installation finished. No error reported.
root@kmac:/# export boot_device=$(nvram --print-config=boot-device)
root@kmac:/# nvsetenv boot-device ${boot_device%%BootX}\\grub
root@kmac:/# nvram --print-config=boot-device
/ht@0,f200/pci@5/k2-sata-root@c/@-1/@0:2,\grub
root@kmac:/#
exit
#
~ # umount -v /target/sys
~ # umount -v /target/dev
~ # umount -v /target/proc
But when it rebooted, all I got was a folder icon with a blinking question mark.
Enjoy!
Rick
Re: Workaround for installing Debian onto PowerMacs (2020-02-02 image)
On Tue, Feb 2, 2021, at 4:57 PM, John Paul Adrian Glaubitz wrote:
> On 2/3/21 1:44 AM, Rick Thomas wrote:
> > So I tried this. I installed from the 2021-02-02 NETINST ppc64 on my G5
> > powermac.
> > When it got to the end and wanted to reboot, I switched to the F2 console
> > and ran
> > the above routine. Then I allowed it to reboot.
>
> You probably did not copy the instructions 1:1. Every character is important.
>
> You can verify the correct path with:
>
> # nvram --print-config=boot-device
>
> Can you paste the output here?
OK, here's the output.
~ # mount -o bind /dev/ /target/dev/
~ # mount -o bind /proc/ /target/proc/
~ # mount -o bind /sys/ /target/sys/
~ # chroot /target
# /bin/bash
root@kmac:/# grub-install --macppc-directory=/boot/grub
Installing for powerpc-ieee1275 platform.
Installation finished. No error reported.
root@kmac:/# nvram --print-config=boot-device
/ht@0,f200/pci@5/k2-sata-root@c/@-1/@0:2,\\BootX
root@kmac:/# export boot_device=$(nvram --print-config=boot-device)
root@kmac:/# nvsetenv boot-device ${boot_device%%BootX}\\grub
root@kmac:/# exit
exit
# exit
~ # sync
~ # sync
~ # umount -v /target/dev
~ # umount -v /target/proc
~ # umount -v /target/sys
~ # sync
Hope it helps!
Rick
Re: Workaround for installing Debian onto PowerMacs (2020-02-02 image)
On Tue, Feb 2, 2021, at 4:57 PM, John Paul Adrian Glaubitz wrote: > On 2/3/21 1:44 AM, Rick Thomas wrote: > > So I tried this. I installed from the 2021-02-02 NETINST ppc64 on my G5 > > powermac. > > When it got to the end and wanted to reboot, I switched to the F2 console > > and ran > > the above routine. Then I allowed it to reboot. > > You probably did not copy the instructions 1:1. Every character is important. > > You can verify the correct path with: > > # nvram --print-config=boot-device > > Can you paste the output here? > > Adrian What I did was to install in expert mode, when it got to installing special parts, I asked it to install the network console. Then I allowed it to proceed and (after a bit) I was invited to log in via ssh, which I did. That way I was able to run the installed in one window and see your mail in another window. Then I copy-pasted your instructions. from the mail to the installer window (one line at a time). There were no error messages while I did that, if that makes a difference. If it will help, I can mount the disk I installed to on another machine and copy the install log files. Will those show you what you want to see? I will try again soon, with your suggestion regarding "print-config", and take careful notes. I'll report again when I have the results. Thanks! Rick
Re: Workaround for installing Debian onto PowerMacs (2020-02-02 image)
On Tue, Feb 2, 2021, at 4:22 AM, John Paul Adrian Glaubitz wrote:
> Hello!
>
> For anyone wanting to install a current Debian unstable snapshot onto their
> PowerMacs, I'm going to write down a short guide how to make sure GRUB
> gets installed properly (in case the installation fails).
>
> Use either the powerpc or ppc64 image depending on your machine type:
>
> > https://cdimage.debian.org/cdimage/ports/snapshots/2021-02-02/
>
> Install normally. After GRUB has been installed and the installation has
> finished, don't reboot the machine yet.
>
> Switch to another console and enter the following commands:
>
> # mount -o bind /dev/ /target/dev/
> # mount -o bind /proc/ /target/proc/
> # mount -o bind /sys/ /target/sys/
>
> # chroot /target/
> # bash
> # grub-install --macppc-directory=/boot/grub
> # export boot_device=$(nvram --print-config=boot-device)
> # nvsetenv boot-device ${boot_device%%BootX}\\grub
>
> # exit
> # exit
> # umount /target/dev
> # umount /target/proc
> # umount /target/sys
> # exit
>
> Then switch back to the installer console.
>
> I am going to fix the GRUB installation for PowerMacs in the next weeks
> once and
> for all. I have read through the grub-installer code again and now have
> a rough
> idea for a proper fix for the issue. The current fix that Frank
> Scheiner authored
> and that we have been using the past months is actually a bit hacky and
> unreliable
> which is why I will take another approach which will involve a udeb for
> hfsprogs
> so that partman-auto can set up the HFS partition automatically.
>
> Adrian
So I tried this. I installed from the 2021-02-02 NETINST ppc64 on my G5
powermac. When it got to the end and wanted to reboot, I switched to the F2
console and ran the above routine. Then I allowed it to reboot.
It did not boot. What I got was a folder with a blinking questionmark.
I tried rebooting with the key but got nothing there.
Please let me know if there's anything else you want me to try! I'm really
looking forward to being able to install an up-to-date Debian on this machine!
Thanks very much for all your efforts!
Rick
Re: More debug infos - was: Re: iMac G5 "windfarm"
On Mon, Jan 4, 2021, at 8:46 AM, Alex Perez wrote:> > John Paul Adrian Glaubitz wrote on 1/4/2021 1:56 AM: > > My guess is that this issue can be worked around by zeroing the partition > > table of the system before installing Debian. > > > > Can someone give it a try? > I did so, zeroing out my drive first, with the latest 2020-01-03 netinst > image, and it seems to maybe get a little bit further, but still hangs. > In the TUI, it hangs at 52% instead of ~47% percent, as it did before. > It seems to stall in when executing /lib/partman/init.d/35dump (which > seems to never exit) > > All the above nine-line script does is cat the device strings (via > /var/lib/partman/devices/*) and then the debian-installer stuffs this in > a dialog box, presumably to select the drive to install to. Since > there's only one drive on my system, and I've verified I get expected > values from the one entry for sda, I'm not sure why it's hanging, but > it's progress of a sort. > > Adrian Hmmm... "then the debian-installer stuffs this in a dialog box, presumably to select the drive to install to." Is the dialog box somehow not getting to be displayed? If it's expecting an answer from the dialog box, but you can't see it to answer, that would explain the hang... Maybe? Rick
Re: iMac G5 "windfarm"
You have vmlinux -> vmlinux-5.9.0-5-powerpc64 But there is no actual file named "vmlinux-5.9.0-5-powerpc64" in the directory. Maybe that's your problem? Rick On Wed, Dec 30, 2020, at 2:55 PM, Riccardo Mottola wrote: > Hi Mathieu, > > > On 12/30/20 10:22 AM, Mathieu Malaterre wrote: > > There was a regression at some point, did you check: > > > > *https://lists.debian.org/debian-powerpc/2020/03/msg00035.html > > > > What's your kernel version ? > > > Right now, it apparently is an older version: > > Linux PPC970FX 4.16.0-1-powerpc64 #1 SMP Debian 4.16.5-1 (2018-04-29) > ppc64 GNU/Linux > > which appears to be around the critical one cited there about issues. > However, theere the issue was "windfarm not loaded". To me here it seems > to be loaded, to be almost too aggressive. > > In lsmod I see. > > windfarm_cpufreq_clamp 3213 1 > windfarm_smu_sat 7464 0 > windfarm_smu_sensors 7223 6 > windfarm_smu_controls 7878 3 > windfarm_pm121 12261 0 > windfarm_pid 2995 1 windfarm_pm121 > > > I installed also a newer kernel: > > -rw-r--r-- 1 root root 169543 Apr 29 2018 config-4.16.0-1-powerpc64 > lrwxrwxrwx 1 root root 28 Dec 29 18:21 initrd.img -> > initrd.img-5.9.0-5-powerpc64 > -rw-r--r-- 1 root root 24420098 Dec 29 18:22 initrd.img-4.16.0-1-powerpc64 > -rw-r--r-- 1 root root 27346593 Dec 29 18:22 initrd.img-5.9.0-5-powerpc64 > lrwxrwxrwx 1 root root 29 Dec 29 14:16 initrd.img.old -> > initrd.img-4.16.0-1-powerpc64 > drwx-- 2 root root 12288 Dec 29 14:09 lost+found > -rw-r--r-- 1 root root 4126454 Apr 29 2018 System.map-4.16.0-1-powerpc64 > lrwxrwxrwx 1 root root 25 Dec 29 18:21 vmlinux -> > vmlinux-5.9.0-5-powerpc64 > -rwxr-xr-x 1 root root 25371992 Apr 29 2018 vmlinux-4.16.0-1-powerpc64 > lrwxrwxrwx 1 root root 26 Dec 29 14:16 vmlinux.old -> > vmlinux-4.16.0-1-powerpc64 > > > But yaboot doesn't find it, so I have to boot "old". Maybe this is part > of the issue. > > TO me vimlinux seems as correct as vmlinux.old > > yaboot has: > > image=/vmlinux > label=Linux > read-only > initrd=/initrd.img > > image=/vmlinux.old > label=old > read-only > initrd=/initrd.img.old > > > so it looks all fine to me, why should "old" work and Linux not? > > > Riccardo > >
Re: "Not installable" error on powerpc 32-bit
On Fri, Nov 27, 2020, at 6:34 AM, John Paul Adrian Glaubitz wrote: > Hello Alessandro! > > On 11/27/20 3:02 PM, Alessandro Gaggioli wrote: > > I am a user of the debian-ports repository and would like to ask for a > > reason > > as to why, when attempting to install a package such as "firefox" to my > > powerpc > > machine, I continue receiving errors telling me that certain dependencies > > are > > unavailable. > > Are you just talking about Firefox or any other package in particular? > > Please list the packages that you are talking about. > > > Are certain programs, such as libevent or libvpx4, simply missing from the > > repositories? Am I doing something wrong here or are these simply not > > present? > > I posted a message on the Debian sparc mailing list explaining this issue [1], > let me know if this helps understanding the problem. > > Adrian > > > [1] https://lists.debian.org/debian-sparc/2017/12/msg00060.html Thanks for the heads-up Adrian! What exactly do I have to do to add snapshot.debian.org to sources.list? The documentation at that address indicates that I need specify a particular date as part of the sources.list deb line. Is there something I can do to make it generalize over all available dates? I'm particularly interested in firefox, but there are lots of other packages it would be nice to have... Thanks! Rick
Re: Looking for a PCI (not PCIe) card for (non-raid) SATA that is compatible with PowerMac G4
Or, if not with the firmware installed, where can I find instructions for installing the firmware? Thanks again, Rick On Fri, Jul 17, 2020, at 6:11 PM, Rick Thomas wrote: > Sounds great! > > Now, where can I buy one of these cards -- hopefully with the new firmware > already installed. > And where can I find instructions for including the driver module in my > Debian Jessie kernel? > > Thanks! > Rick > > On Thu, Jul 16, 2020, at 5:23 AM, luigi burdo wrote: >> Hello, >> i can say for sure this card is already compatible with linux ppc. >> The only thing necessary is have a kernel with the board included as a mod. >> The card will starting work after the kernel load in yaboot or grub... (i >> had been used it on amiga pci machine) >> I have a Marvell pcie in My G5 Quad working as the same phylosophy as i >> described before. >> The same is fo all card and device. GPU usb3 and so and so. >> >> Ciao >> Gigi Burdo >> >> >> >> *Da:* Romain Dolbeau >> *Inviato:* giovedì 16 luglio 2020 13:45 >> *A:* Rick Thomas >> *Cc:* PowerPC List Debian >> *Oggetto:* Re: Looking for a PCI (not PCIe) card for (non-raid) SATA that is >> compatible with PowerMac G4 >> >> Le mer. 15 juil. 2020 à 12:46, Romain Dolbeau a écrit : >> > You need to locate a SIL3112 (or in a pinch, SIL3114 can do) based PCI >> > SATA card and flash it with a Fcode BIOS >> >> Apparently, there is an ongoing effort to create a new firmware for >> the family of chips, which should make G4 users' life easier :-) >> >> <http://macos9lives.com/smforum/index.php/topic,5534.0.html> >> >> Cordially, >> >> -- >> Romain Dolbeau >> >
Re: Looking for a PCI (not PCIe) card for (non-raid) SATA that is compatible with PowerMac G4
Sounds great! Now, where can I buy one of these cards -- hopefully with the new firmware already installed. And where can I find instructions for including the driver module in my Debian Jessie kernel? Thanks! Rick On Thu, Jul 16, 2020, at 5:23 AM, luigi burdo wrote: > Hello, > i can say for sure this card is already compatible with linux ppc. > The only thing necessary is have a kernel with the board included as a mod. > The card will starting work after the kernel load in yaboot or grub... (i > had been used it on amiga pci machine) > I have a Marvell pcie in My G5 Quad working as the same phylosophy as i > described before. > The same is fo all card and device. GPU usb3 and so and so. > > Ciao > Gigi Burdo > > > > *Da:* Romain Dolbeau > *Inviato:* giovedì 16 luglio 2020 13:45 > *A:* Rick Thomas > *Cc:* PowerPC List Debian > *Oggetto:* Re: Looking for a PCI (not PCIe) card for (non-raid) SATA that is > compatible with PowerMac G4 > > Le mer. 15 juil. 2020 à 12:46, Romain Dolbeau a écrit : > > You need to locate a SIL3112 (or in a pinch, SIL3114 can do) based PCI > > SATA card and flash it with a Fcode BIOS > > Apparently, there is an ongoing effort to create a new firmware for > the family of chips, which should make G4 users' life easier :-) > > <http://macos9lives.com/smforum/index.php/topic,5534.0.html> > > Cordially, > > -- > Romain Dolbeau >
Looking for a PCI (not PCIe) card for (non-raid) SATA that is compatible with PowerMac G4
I have an old PowerMac G4 "Silver" (PowerMac3,4 533 MHz) running Debian Jessie, that I'd like to put a couple of SATA disks into. That means I need a SATA controller card that will fit in one of its PCI (not PCIe) slots. It also needs to be to be compatible with the PowerMac Open Firmware BIOS. I've tried two RAID SATA-ii cards but they expect to have a Windows PC BIOS motherboard and refuse to even allow the Mac to boot with them plugged in. Anybody have a recommendation? And where can I purchase it? Thanks in advance! Rick
Re: Debian live
Thanks! I'll take a look. I'm an experienced sysadmin, but I'm not a developer; so I might need some help figuring this out. Can I email you (Elimar) for occasional hints? Rick On Sun, Jul 12, 2020, at 5:38 PM, Elimar Riesebieter wrote: > * Rick Thomas [2020-07-11 16:23 -0700]: > > > The more general-purpose the "live" system can be the better. > > Ideally, it should be possible to boot from the live CD/DVD, while > > at the same time having a specially formatted USB stick inserted > > which would provide "persistent" storage for the booted system -- > > leaving the disk drive(s) of the system untouched and available > > for whatever work you want to do with them (e.g. backup and > > recovery.) The "grml" live boot for i386/amd64 is a great example > > of what I'd like. > > There is 'apt-cache show grml-live' available for Architecture: all. > If you want to contribute you can adapt ppc arch to the respective > FAI configuration and build your own grml-ppc-live system. > > https://grml.org/grml-live/ > > Just a thought > Elimar > -- > On the keyboard of life you have always > to keep a finger at the escape key;-) > >
Re: Debian live
The more general-purpose the "live" system can be the better. Ideally, it should be possible to boot from the live CD/DVD, while at the same time having a specially formatted USB stick inserted which would provide "persistent" storage for the booted system -- leaving the disk drive(s) of the system untouched and available for whatever work you want to do with them (e.g. backup and recovery.) The "grml" live boot for i386/amd64 is a great example of what I'd like. Rick On Tue, Jul 7, 2020, at 3:39 AM, Steffen Möller wrote: > That - and for ARM as well. Would be a good chance to attract more > users, indeed. > > On 07.07.20 12:38, Jeroen Diederen wrote: > > Hi! > > > > Do you guys know if it is possible to create live installer images > > from a working Debian PowerpPC system? I know debian-live is only for > > i386 and amd64. Maybe there are other unofficial ways to achieve this? > > Documentation somewhere? > > > > What I want to achieve is create a live iso from a customised Debian > > system which is able to install that customised system from USB. On > > the desktop in that system I want to have a launcher that installs > > this system in a desired place. > > > > Regards, > > Jeroen > > > >
Re: Installing Jessie on PowerMac G4 (32 bit) -- expired key
On Tue, Jun 23, 2020, at 12:29 AM, John Paul Adrian Glaubitz wrote: > On 6/23/20 9:07 AM, Rick Thomas wrote: > >> W: GPG error: http://archive.debian.org jessie Release: The following > >> signatures were invalid: KEYEXPIRED 1587841717 > > > > And it still isn't working... /-: > > It is. The error has been downgraded from an Error to a Warning which is > exactly what you want. > > Adrian Ahh... yes. So it has! Thanks!
Re: Installing Jessie on PowerMac G4 (32 bit) -- expired key
On Mon, Jun 22, 2020, at 11:36 PM, John Paul Adrian Glaubitz wrote: > If setting it in apt.conf doesn't work, try setting > "APT::Get::AllowUnauthenticated "true";": > > > https://askubuntu.com/questions/74345/how-do-i-bypass-ignore-the-gpg-signature-checks-of-apt Well... that seems to work. It does suppress the warning. It also seems to suppress the checksum authentication, which is too bad. But for my purposes here, it's good enough. Thanks very much for all the help! Rick PS: Any idea why the Check-Valid-Until option doesn't work? Thanks!
Re: Installing Jessie on PowerMac G4 (32 bit) -- expired key
On Mon, Jun 22, 2020, at 11:36 PM, John Paul Adrian Glaubitz wrote: > On 6/23/20 8:27 AM, Rick Thomas wrote: > > Unfortunately, as you can see, I still get the warning. > > > > I have a vague recollection of seeing something somewhere (I know -- I'm > > sorry I can't be > > more specific) that the version of apt in Jessie doesn't respond to > > "Check-Valid-Until". > > Can anyone confirm or deny this? > > Did you set the setting in /etc/apt/apt.conf or in your sources.list? > The latter doesn't > work. > > If setting it in apt.conf doesn't work, try setting > "APT::Get::AllowUnauthenticated "true";": > > > https://askubuntu.com/questions/74345/how-do-i-bypass-ignore-the-gpg-signature-checks-of-apt > > > I wonder if it is possible to get the Release file re-signed with an > > up-to-date key? > > As those files have been archived, it isn't possible. But you could run your > own > mirror, copy all packages and add a new Release file plus signature. I tried setting it in sources.list. As you noted, it didn't work. So I created a file in /etc/apt/apt.conf.d/ as follows: > root@grey:~# cat /etc/apt/apt.conf.d/25ignoreexpired > APT::Get::AllowUnauthenticated "true"; > root@grey:~# Then tried > root@grey:~# apt update > Ign http://archive.debian.org jessie InRelease > Get:1 http://archive.debian.org jessie Release.gpg [2420 B] > Hit http://archive.debian.org jessie Release > Ign http://archive.debian.org jessie Release > > W: GPG error: http://archive.debian.org jessie Release: The following > signatures were invalid: KEYEXPIRED 1587841717 And it still isn't working... /-: Rick PS: Thanks very much for the quick replies!
Re: Installing Jessie on PowerMac G4 (32 bit) -- expired key
On Mon, Jun 22, 2020, at 11:29 PM, Jeroen Diederen wrote: > You might also want to try this: > https://linux-audit.com/how-to-solve-an-expired-key-keyexpired-with-apt/ > https://futurestud.io/tutorials/fix-ubuntu-debian-apt-get-keyexpired-the-following-signatures-were-invalid > https://www.reddit.com/r/debian/comments/g9is3p/debian_8_jessie_keyexpired_drive_my_crazy/ > > Regards, > Jeroen So I did: > root@grey:~# apt-key list | grep -A 1 expired > pub 4096R/46925553 2012-04-27 [expired: 2020-04-25] > uid Debian Archive Automatic Signing Key (7.0/wheezy) > -- > pub 4096R/65FFB764 2012-05-08 [expired: 2019-05-07] > uid Wheezy Stable Release Key > -- > pub 4096R/623DB0B8 2014-01-16 [expired: 2015-01-31] > uid Debian Ports Archive Automatic Signing Key (2014) > > -- > pub 4096R/C448326E 2015-01-27 [expired: 2016-02-01] > uid Debian Ports Archive Automatic Signing Key (2015) > and: > apt-key adv --keyserver hkp://keyserver.ubuntu.com --recv-keys 46925553 But I still get the warning. /-: Thanks! Rick
Re: Installing Jessie on PowerMac G4 (32 bit) -- expired key
On Mon, Jun 22, 2020, at 2:35 AM, John Paul Adrian Glaubitz wrote: > Hello Rick! > > On 6/19/20 10:59 AM, Rick Thomas wrote: > > So my second question is: How do I get it to proceed automatically in spite > > of the expired key? > > You can set this option in your APT configuration: > > Acquire::Check-Valid-Until=false > > which will disable the check for expired signatures. > > Adrian Thanks Adrian! I tried this to see if I could get a one-time over-ride: > root@grey:~# apt-get -o 'Acquire::Check-Valid-Until=false' update > Ign http://archive.debian.org jessie InRelease > Get:1 http://archive.debian.org jessie Release.gpg [2420 B] > Hit http://archive.debian.org jessie Release > Ign http://archive.debian.org jessie Release > Ign http://archive.debian.org jessie/main powerpc Packages/DiffIndex > Ign http://archive.debian.org jessie/non-free powerpc Packages/DiffIndex > Ign http://archive.debian.org jessie/contrib powerpc Packages/DiffIndex > Hit http://archive.debian.org jessie/contrib Translation-en > Hit http://archive.debian.org jessie/main Translation-en > Hit http://archive.debian.org jessie/non-free Translation-en > Hit http://archive.debian.org jessie/main powerpc Packages > Hit http://archive.debian.org jessie/non-free powerpc Packages > Hit http://archive.debian.org jessie/contrib powerpc Packages > Fetched 2420 B in 12s (197 B/s) > Reading package lists... Done > W: GPG error: http://archive.debian.org jessie Release: The following > signatures were invalid: KEYEXPIRED 1587841717 > root@grey:~# Unfortunately, as you can see, I still get the warning. I have a vague recollection of seeing something somewhere (I know -- I'm sorry I can't be more specific) that the version of apt in Jessie doesn't respond to "Check-Valid-Until". Can anyone confirm or deny this? I wonder if it is possible to get the Release file re-signed with an up-to-date key? Thanks! Rick
Re: Installing Jessie on PowerMac G4 (32 bit) -- expired key
On Mon, Jun 22, 2020, at 12:18 AM, Jeroen Diederen wrote: > Make it > deb http://archive.debian.org/debian/ jessie main contrib non-free > > Beste regards, > Jeroen Diederen Thanks. it looks like this now deb http://archive.debian.org/debian/ jessie main non-free contrib I have no idea how the [1] got in there. but I still get the Warning. Rick
Installing Jessie on PowerMac G4 (32 bit) -- expired key
I need to install Jessie powerpc (32-bit) on a G4 powermac. (And before you ask, yes it needs to be Jessie – just for a couple of months. Then I will be able to install Adrian’s Sid from Ports.) But I’m running up against some roadblocks. Any help will be greatly appreciated! When the installer gets to the part where I choose a package repository, I choose to enter the name manually as “archive.debian.org”. But that fails because it wants the dist to be “oldoldstable”, which doesn’t exist on the archive repo. If I could make it use “jessie” instead, things would work fine, but I don’t know how to tell the installer to do that. So my first question is: Does anybody know how to force the dist name to be something other than “oldoldstable”? OK… I gave up and chose not to specify a package repository. The install runs to completion with a very minimal configuration. It does that and reboots fine. Then I log in on the console and edit the sources.list file to look like this: > *deb **http://archive.debian.org/debian/** jessie main non-free contrib* Then, when I do “apt update” I get this: > *root@grey:~# apt update * > *Ign **http://archive.debian.org** jessie InRelease * > *Get:1 **http://archive.debian.org** jessie Release.gpg [2420 B] * > *Hit **http://archive.debian.org** jessie Release * > *Ign **http://archive.debian.org** jessie Release * > *Ign **http://archive.debian.org** jessie/main powerpc Packages/DiffIndex * > *Ign **http://archive.debian.org** jessie/non-free powerpc Packages/DiffIndex * > *Ign **http://archive.debian.org** jessie/contrib powerpc Packages/DiffIndex * > *Hit **http://archive.debian.org** jessie/contrib Translation-en * > *Hit **http://archive.debian.org** jessie/main Translation-en * > *Hit **http://archive.debian.org** jessie/non-free Translation-en * > *Hit **http://archive.debian.org** jessie/main powerpc Packages * > *Hit **http://archive.debian.org** jessie/non-free powerpc Packages * > *Hit **http://archive.debian.org** jessie/contrib powerpc Packages * > *Fetched 2420 B in 14s (165 B/s) * > *Reading package lists... Done * > *Building dependency tree * > *Reading state information... Done * > *All packages are up to date. * > *W: GPG error: **http://archive.debian.org** jessie Release: The following > signatures were invalid: KEYEXPIRED 1587841717 * If I ignore the warning and do “apt install exim4.doc-html” I get this: > *root@grey:~# apt install exim4.doc-html * > *Reading package lists... * > *Building dependency tree... * > *Reading state information... * > *The following NEW packages will be installed: * > * exim4-doc-html * > *0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. * > *Need to get 0 B/464 kB of archives. * > *After this operation, 3354 kB of additional disk space will be used. * > *WARNING: The following packages cannot be authenticated! * > * exim4-doc-html * > *Install these packages without verification? [y/N] * If I take the default (“N”) the install fails. So I choose “Y”, and get: > *Install these packages without verification? [y/N] y * > *Selecting previously unselected package exim4-doc-html. * > *(Reading database ... 22481 files and directories currently installed.) * > *Preparing to unpack .../exim4-doc-html_4.84-1_all.deb ... * > *Unpacking exim4-doc-html (4.84-1) ... * > *Setting up exim4-doc-html (4.84-1) ... * > *root@grey:~# * So my second question is: How do I get it to proceed automatically in spite of the expired key? Thanks! Any suggestions will be greatly appreceated. Rick
Re: Make Debian Sid cdimage download more obvious in official powerpc port page?
Thanks for this! A useful history. But I think some links for the references
would be very helpful.
Rick
On Fri, May 15, 2020, at 12:18 PM, jjhdiederen wrote:
> I made a little progress. I edited the index.wml file in
> webwml/english/ports/powerpc and made the corresponding html file. It
> looks good, it reads like this:
>
> ...
> Debian on 32-bit PowerPC (powerpc)
>
> It first became an official "release architecture" with Debian GNU/Linux
> 2.2 ("potato") and had retained that status until the publication of
> Debian 9 ("stretch"). The last supported release for 32-bit PowerPC is
> Debian 8 ("jessie"). See the release note and installation manual for
> further information. Since the powerpc architecture is no longer
> officially supported, the repository of powerpc can be found at the
> Debian ports website. The latest installer images can be found at
> cdimage ports.
> Debian on 64-bit PowerPC (ppc64)
>
> In 2012 the ppc64 architecture was added to the Debian ports site. More
> information about this port can be found at the ppc64 wiki. The latest
> installer images can be found at cdimage ports.
> Debian on 64-bit Little Endian PowerPC (ppc64el).
>
> Where can I transfer the edited index.wml file for you guys to read and
> comment?
>
> Jeroen
>
>
Re: Updated installation images for Debian Ports 2020-04-19
On Thu, Apr 23, 2020, at 6:21 PM, Rick Thomas wrote: > I will be submitting soon a separate bug report for the disk-drive > weirdness on the G4. (Any ideas on what's going on there?) Done. Bug#958649. Hope it helps! Rick
Re: Updated installation images for Debian Ports 2020-04-19
On Thu, Apr 23, 2020, at 1:35 AM, John Paul Adrian Glaubitz wrote: > Note: The official way to report about a successful installation is using > "installation-reports", see [1]. This way, your report doesn't get lost. Done. Bug#958527 . This is only the report for the successful install on the G5. I will be submitting soon a separate bug report for the disk-drive weirdness on the G4. (Any ideas on what's going on there?) Best regards, Rick
Re: Updated installation images for Debian Ports 2020-04-19
On Sun, Apr 19, 2020, at 11:30 AM, John Paul Adrian Glaubitz wrote: > > [1] https://cdimage.debian.org/cdimage/ports/2020-04-19/ Works great fresh out of the box on my PowerMac G5 "PowerMac7,3" -- Congratulations! Let me know if you want log files or other data from that installation. I then tried it on my PowerMac G4 Silver "PowerMac 3,5" -- and ran into a problem: The CD booted fine. I used the default install option. All went well until it came time to partition the disk. The machine has three IDE (Parallel ATA) drives. Two are configured as a RAID1 array and the third is the boot disk. But none of those disks were found by the installer's partitioning step! So I couldn't continue with the installation. Interestingly enough, when I switched to -F2 console and did "ls -l /dev/sd*", all three of the disks seemed to be present. Very strange! So I thought maybe I could save the log files to a USB thumb-drive (I had forgotten about the "save to the web" option). I plugged in a USB drive and tried again. This time it *found* all the disks (including the USB drive) and kindly offered to partition them for me! Wow! "Curiouser and curiouser!" So I disconnected the USB drive and tried again. As expected, it did not find the disks this time. So I saved the log files (having noticed the web option in a previous attempt). Then I re-plugged the USB drive and tried the install with it in. As expected, it found the disk drives and successfully partitioned the boot drive for me. The rest of the install went fine, including installing Grub and rebooting into the newly installed system. I saved the log files for comparison with the failed attempt. I'm attaching to this email the two sets of log files as a single compressed tar.gz file. Hope it helps! Thanks for all your work! Rick LogsForAdrian.tar.gz Description: application/gzip
Re: Lombard booting Debian Ports 2020-04-19 (was Re: Updated installation images for Debian Ports 2020-04-19)
On Mon, Apr 20, 2020, at 9:18 AM, John Paul Adrian Glaubitz wrote: > On 4/20/20 6:02 PM, user...@yahoo.com wrote: > > Yes, I forgot to checkout the mac-support branch. Here are the new results: > > > > root@lombard:/data/software/powerpc-utils# ./scripts/ofpathname --version > > ofpathname: Version 0.5 > > Written by: Nathan Fontenot > > > > root@lombard:/data/software/powerpc-utils# ./scripts/ofpathname /dev/sda > > /pci@8000/mac-io@10/ata-3@2/@0 > > > > root@lombard:/data/software/powerpc-utils# ./scripts/ofpathname /dev/sda1 > > /pci@8000/mac-io@10/ata-3@2/@0:1 > > So the ofpathname script is working correctly on your machine as the output > matches the one from the ofpath script from Yaboot. > > I would suggest finding a better recordable CD and rewrite the ISO image > for Debian sid and test again. I assume an external drive doesn't work, > maybe one with SCSI? Make sure it's a CD-R, not CD+R or CD-RW or any kind of DVD. I've got a couple of older machines that have trouble with anything but pure and simple CD-R (and won't even recognize DVDs!) Rick
Re: Repository address for netinst
That works! I tried it with jessie-backports as well, and I got: root@kmac:~# apt update Ign http://archive.debian.org jessie InRelease Get:1 http://archive.debian.org jessie-backports InRelease [166 kB] W: There is no public key available for the following key IDs: 8B48AD6246925553 E: Release file for http://archive.debian.org/debian/dists/jessie-backports/InRelease is expired (invalid since 424d 14h 54min 36s). Updates for this repository will not be applied. Any clues as to how to deal with that? Thanks! Rick On Sun, Apr 19, 2020, at 2:42 AM, Gianluca Bonetti wrote: > Hi Rick > > What about this? > deb http://archive.debian.org/debian/ jessie contrib main non-free > > Does it work for you? > > Cheers > > Il giorno dom 19 apr 2020 alle ore 11:35 Rick Thomas > ha scritto: >> __ >> Hi Gianluca, >> >> Colton (and I) want to use Jessie (Debian 8) because it is the last working >> Debian version that supports powerpc and ppc64. Unfortunately, the repo at >> http://ftp.ports.debian.org/debian-ports/ only has unreleased, unstable, and >> experimental. Nothing there that looks like it is usable for jessie. >> >> Adrian's work on getting a "ports" version for Debian 10 is still a >> work-in-progress and not yet suitable for a "production" machine. There's a >> bunch of us helping with the effort, and we are hopeful we can get it going >> soon. Big kudos to Adrian for spearheading the effort! >> >> Rick >> >> On Sat, Apr 18, 2020, at 1:22 PM, Gianluca Bonetti wrote: >>> Hi Colton >>> >>> Have you tried a newer installer image from here? >>> https://cdimage.debian.org/cdimage/ports/ >>> >>> Then I think you can use this line in sources.list >>> deb http://ftp.ports.debian.org/debian-ports/ unstable main >>> >>> At least I was using that if I remember correctly >>> Cheers >>> Gianluca >>> >>> Il giorno sab 18 apr 2020 alle ore 21:14 Colton Booth >>> ha scritto: >>>> Good day everyone, >>>> >>>> I was wondering if someone could please point me in the direction of a >>>> repository to use with Debian 8 PowerPC netinst? Due to brittle plastics >>>> my iBook G4 is going to be staying with its original CD drive and will not >>>> be able to use DVDs. >>>> >>>> I would also like to set up my own repository server in the near future >>>> and make it available to the public. I am currently gathering the hardware >>>> and should be set up sometime next week. >>>> >>>> Thank you, >>>> >>>> Colton >>
Re: Repository address for netinst
Hi Gianluca, Colton (and I) want to use Jessie (Debian 8) because it is the last working Debian version that supports powerpc and ppc64. Unfortunately, the repo at http://ftp.ports.debian.org/debian-ports/ only has unreleased, unstable, and experimental. Nothing there that looks like it is usable for jessie. Adrian's work on getting a "ports" version for Debian 10 is still a work-in-progress and not yet suitable for a "production" machine. There's a bunch of us helping with the effort, and we are hopeful we can get it going soon. Big kudos to Adrian for spearheading the effort! Rick On Sat, Apr 18, 2020, at 1:22 PM, Gianluca Bonetti wrote: > Hi Colton > > Have you tried a newer installer image from here? > https://cdimage.debian.org/cdimage/ports/ > > Then I think you can use this line in sources.list > deb http://ftp.ports.debian.org/debian-ports/ unstable main > > At least I was using that if I remember correctly > Cheers > Gianluca > > Il giorno sab 18 apr 2020 alle ore 21:14 Colton Booth > ha scritto: >> Good day everyone, >> >> I was wondering if someone could please point me in the direction of a >> repository to use with Debian 8 PowerPC netinst? Due to brittle plastics my >> iBook G4 is going to be staying with its original CD drive and will not be >> able to use DVDs. >> >> I would also like to set up my own repository server in the near future and >> make it available to the public. I am currently gathering the hardware and >> should be set up sometime next week. >> >> Thank you, >> >> Colton
Re: ofpath vs ofpathname vs grub-ofpathname
No problem! It was a fun adventure tracking it down! (-; On Sun, Apr 19, 2020, at 1:41 AM, Frank Scheiner wrote: > On 19.04.20 10:36, Rick Thomas wrote: > > OK > > > > On Sat, Apr 18, 2020, at 11:47 PM, Frank Scheiner wrote: > >> You need to use the `ofpathname` from the `mac-support` branch mentioned > >> on [2]. You can either download it directly from [3] or `git clone > >> https://github.com/glaubitz/powerpc-utils.git` and do a `git checkout > >> mac-support` in the created dir and then use the `ofpathname` in the > >> checked-out branch. > >> > >> [3]: > >> https://raw.githubusercontent.com/glaubitz/powerpc-utils/mac-support/scripts/ofpathname > > > > So I went the "git" route (downloading from [3] failed because it was > > missing the "series_platform" script) > > Ok, sorry, didn't knew of that runtime dependency of `ofpathname`. > > Cheers, > Frank >
Re: ofpath vs ofpathname vs grub-ofpathname
OK On Sat, Apr 18, 2020, at 11:47 PM, Frank Scheiner wrote: > Hi Rick, > > nice to hear from you! > > On 19.04.20 00:10, Rick Thomas wrote: > > On Sat, Apr 18, 2020, at 1:58 AM, John Paul Adrian Glaubitz wrote: > >> You should test with ofpathname as well. > > > > OK, I will. Is there an updated version of ofpathname I should be using? > > If so how do I get it? > > Check [1] and [2] for details. > > [1]: https://lists.debian.org/debian-powerpc/2020/04/msg00075.html > > [2]: https://lists.debian.org/debian-powerpc/2020/04/msg00076.html > > You need to use the `ofpathname` from the `mac-support` branch mentioned > on [2]. You can either download it directly from [3] or `git clone > https://github.com/glaubitz/powerpc-utils.git` and do a `git checkout > mac-support` in the created dir and then use the `ofpathname` in the > checked-out branch. > > [3]: > https://raw.githubusercontent.com/glaubitz/powerpc-utils/mac-support/scripts/ofpathname > > Cheers, > FranK So I went the "git" route (downloading from [3] failed because it was missing the "series_platform" script) This is what I got... (/dev/sdc is a usb flash drive plugged into the front USB2 port. sda and sdb are hard disks in the inside the case SATA caddies.) root@kmac:~# cd /home/rbthomas/ofpathname/powerpc-utils/scripts root@kmac:/home/rbthomas/ofpathname/powerpc-utils/scripts# ./ofpathname /dev/sda /ht@0,f200/pci@5/k2-sata-root@c/@0/@0 root@kmac:/home/rbthomas/ofpathname/powerpc-utils/scripts# ./ofpathname /dev/sda1 /ht@0,f200/pci@5/k2-sata-root@c/@0/@0:1 root@kmac:/home/rbthomas/ofpathname/powerpc-utils/scripts# ./ofpathname /dev/sdb /ht@0,f200/pci@5/k2-sata-root@c/@1/@0 root@kmac:/home/rbthomas/ofpathname/powerpc-utils/scripts# ./ofpathname /dev/sdb1 /ht@0,f200/pci@5/k2-sata-root@c/@1/@0:1 root@kmac:/home/rbthomas/ofpathname/powerpc-utils/scripts# ./ofpathname /dev/sdc /ht@0,f200/pci@2/usb@b,2/storage@3/disk@103 root@kmac:/home/rbthomas/ofpathname/powerpc-utils/scripts# ./ofpathname /dev/sdc1 /ht@0,f200/pci@2/usb@b,2/storage@3/disk@103:1 Hope it helps! Rick
Re: ofpath vs ofpathname vs grub-ofpathname
On Sat, Apr 18, 2020, at 1:58 AM, John Paul Adrian Glaubitz wrote: > You should test with ofpathname as well. OK, I will. Is there an updated version of ofpathname I should be using? If so how do I get it? Thanks! Rick
Re: ofpath vs ofpathname vs grub-ofpathname
OK here it is with the fixed ofpath... rbthomas@kmac:~/tmp/usr/sbin$ ./ofpath /dev/sda /ht@0,f200/pci@5/k2-sata-root@c/@0/@0 rbthomas@kmac:~/tmp/usr/sbin$ ./ofpath /dev/sdb /ht@0,f200/pci@5/k2-sata-root@c/@1/@0 rbthomas@kmac:~/tmp/usr/sbin$ ./ofpath /dev/sda1 /ht@0,f200/pci@5/k2-sata-root@c/@0/@0:1 rbthomas@kmac:~/tmp/usr/sbin$ ./ofpath /dev/sdb1 /ht@0,f200/pci@5/k2-sata-root@c/@1/@0:1 All seems well on this machine... Rick
Re: ofpath vs ofpathname vs grub-ofpathname
> > Now, the only test I would like to see is whether ofpath sees a difference > > between "sda" and "sdb" because apparently, Romain got identical paths > > with ofpathname for both his disks. Here's what I ge on my PowerMacc7,3 PCI-X machine It appears that ofpath gives the same answer for both sda and sdb H Rick root@kmac:~# ofpath /dev/sda /ht@0,f200/pci@5/k2-sata-root@c/@/@0 root@kmac:~# ofpath /dev/sdb /ht@0,f200/pci@5/k2-sata-root@c/@/@0 root@kmac:~# lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 931.5G 0 disk |-sda18:10 31.5K 0 part |-sda28:20 977K 0 part |-sda38:30 244.1M 0 part /boot |-sda48:40 931.3G 0 part | |-kmac--vg-root 254:00 6.5G 0 lvm / | |-kmac--vg-swap_1 254:10 11.4G 0 lvm [SWAP] | `-kmac--vg-home 254:20 913.4G 0 lvm /home `-sda58:50 24.5K 0 part sdb 8:16 0 232.9G 0 disk |-sdb18:17 0 31.5K 0 part |-sdb28:18 0 977K 0 part |-sdb38:19 0 244.1M 0 part |-sdb48:20 0 232.7G 0 part `-sdb58:21 0 56.5K 0 part sr0 11:01 3.7G 0 rom
Re: Failed install attempt - GRUB issue - hfsprogs missing?
Here’s the URL for the yaboot-only installer: https://cdimage.debian.org/cdimage/ports/10.0/powerpc/iso-cd/debian-10.0-powerpc-NETINST-1.iso It has worked for me, but I had to do a little work to get it to accept the ports repo without having the certificate for it on the CD. I’ll try to reproduce what I did and post a report here. Rick > On Jun 21, 2019, at 4:05 AM, John Paul Adrian Glaubitz > wrote: > > If you want something that is stable and working, use the Yaboot-only > image in the "10.0" folder unless you have an IBM power machine where > GRUB works without problems.
Re: Debian 9 / 10 mirror server address
> On Jun 6, 2019, at 4:22 PM, John Paul Adrian Glaubitz > wrote: > > On 6/6/19 10:18 PM, Rick Thomas wrote: >>>> Any suggestions? Thanks! >>> Try one of the newer snapshot images or skip the mirror step. You can add >>> the mirror later once the system is installed and running. >> >> Which particular image would you recommend? > > Just use the last 10.0 image which was not a snapshot and skip the mirror > step. You can add a mirror via the sources.list later. No need to use > a mirror during installation. > I’m sorry for being so dumb, but… What’s the difference between a snapshot and a non-snapshot? Can you give me a specific URL to try? Thanks! Rick PS: If I can get a working OS on my PowerMac G5 I’ll be happy to give a shot at grub-ofpathname. As long as you don’t mind answering a bunch of dumb questions like: Where’s the source? And Is there any documentation for how it’s supposed to work?
Re: Debian 9 / 10 mirror server address
> On Jun 6, 2019, at 3:56 AM, John Paul Adrian Glaubitz > wrote: > > On 6/6/19 12:27 PM, Rick Thomas wrote: >> I tried that image. Here’s the MD5 just to be certain. >> >>> $ md5sum debian-10.0-powerpc-NETINST-1.iso >>> 7d1383cea7c831e4e1420e261ee2ea40 debian-10.0-powerpc-NETINST-1.iso >> >> All went well til it tried to connect to the mirror. I tried several mirror >> locations and all resulted in errors because the public key >> “DA1B2CEA81DCBC61” could not be verified. >> >> Any suggestions? Thanks! > Try one of the newer snapshot images or skip the mirror step. You can add > the mirror later once the system is installed and running. Which particular image would you recommend? Thanks! Rick
Re: Debian 9 / 10 mirror server address
> On Jun 2, 2019, at 10:57 PM, John Paul Adrian Glaubitz > wrote: > > You should use this image: > >> https://cdimage.debian.org/cdimage/ports/10.0/powerpc/iso-cd/ > I tried that image. Here’s the MD5 just to be certain. > $ md5sum debian-10.0-powerpc-NETINST-1.iso > 7d1383cea7c831e4e1420e261ee2ea40 debian-10.0-powerpc-NETINST-1.iso All went well til it tried to connect to the mirror. I tried several mirror locations and all resulted in errors because the public key “DA1B2CEA81DCBC61” could not be verified. Any suggestions? Thanks! Rick PS: If it helps, here’s the tail end of the syslog file: Jun 4 09:42:52 apt-setup: Using CD-ROM mount point /media/cdrom/ Jun 4 09:42:52 kernel: [ 1670.884790] ISO 9660 Extensions: RRIP_1991A Jun 4 09:42:52 apt-setup: Identifying... Jun 4 09:42:52 apt-setup: [ab1cb98aed33d5f3d3db2423488d636a-2] Jun 4 09:42:52 apt-setup: Scanning disc for index files... Jun 4 09:42:55 apt-setup: Found 1 package indexes, 0 source indexes, 1 translation indexes and 0 signatures Jun 4 09:42:55 apt-setup: This disc is called: Jun 4 09:42:55 apt-setup: 'Debian GNU/Linux 10.0 _Sid_ - Unofficial powerpc NETINST 20180516-18:14' Jun 4 09:42:55 apt-setup: Copying package lists... Jun 4 09:42:55 apt-setup: ^MReading Package Indexes... 0%^M Jun 4 09:42:55 apt-setup: ^MReading Package Indexes... 1%^M Jun 4 09:42:56 apt-setup: ^MReading Package Indexes... Done^M Jun 4 09:42:56 apt-setup: ^MReading Translation Indexes... 0%^M Jun 4 09:42:56 apt-setup: ^MReading Translation Indexes... Done^M Jun 4 09:42:56 apt-setup: Writing new source list Jun 4 09:42:56 apt-setup: Source list entries for this disc are: Jun 4 09:42:56 apt-setup: deb cdrom:[Debian GNU/Linux 10.0 _Sid_ - Unofficial powerpc NETINST 20180516-18:14]/ sid main Jun 4 09:42:56 apt-setup: Repeat this process for the rest of the CDs in your set. Jun 4 09:42:57 kernel: [ 1676.247999] ISO 9660 Extensions: RRIP_1991A Jun 4 09:42:57 kernel: [ 1676.482358] ISO 9660 Extensions: RRIP_1991A Jun 4 09:43:02 kernel: [ 1681.573460] ISO 9660 Extensions: RRIP_1991A Jun 4 09:43:03 kernel: [ 1681.807852] ISO 9660 Extensions: RRIP_1991A Jun 4 09:43:57 choose-mirror[1213]: DEBUG: command: wget --no-verbose http://deb.debian.org/debian-ports/dists/sid/Release -O - | grep -E '^(Suite|Codename|Architectures):' Jun 4 09:43:58 choose-mirror[1213]: DEBUG: command: wget --no-verbose http://deb.debian.org/debian-ports/dists/unstable/Release -O - | grep -E '^(Suite|Codename|Architectures):' Jun 4 09:43:58 choose-mirror[1213]: INFO: suite/codename set to: unstable/sid Jun 4 09:43:58 choose-mirror[1213]: DEBUG: command: wget --no-verbose http://deb.debian.org/debian-ports//dists/sid/main/binary-powerpc/Release -O - | grep ^Architecture: Jun 4 09:44:15 in-target: Get:1 http://deb.debian.org/debian-ports sid InRelease [55.3 kB] Jun 4 09:44:16 in-target: Err:1 http://deb.debian.org/debian-ports sid InRelease Jun 4 09:44:16 in-target: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DA1B2CEA81DCBC61 Jun 4 09:44:16 in-target: Reading package lists... Jun 4 09:44:16 in-target: Jun 4 09:44:16 in-target: W: GPG error: http://deb.debian.org/debian-ports sid InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DA1B2CEA81DCBC61 Jun 4 09:44:16 in-target: E: The repository 'http://deb.debian.org/debian-ports sid InRelease' is not signed. Jun 4 09:45:24 choose-mirror[1394]: DEBUG: command: wget --no-verbose http://ftp.ports.debian.org/debian-ports/dists/unstable/Release -O - | grep -E '^(Suite|Codename|Architectures):' Jun 4 09:45:24 choose-mirror[1394]: DEBUG: command: wget --no-verbose http://ftp.ports.debian.org/debian-ports/dists/sid/Release -O - | grep -E '^(Suite|Codename|Architectures):' Jun 4 09:45:25 choose-mirror[1394]: DEBUG: command: wget --no-verbose http://ftp.ports.debian.org/debian-ports//dists/sid/main/binary-powerpc/Release -O - | grep ^Architecture: Jun 4 09:45:26 in-target: Get:1 http://ftp.ports.debian.org/debian-ports sid InRelease [55.3 kB] Jun 4 09:45:27 in-target: Err:1 http://ftp.ports.debian.org/debian-ports sid InRelease Jun 4 09:45:27 in-target: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DA1B2CEA81DCBC61 Jun 4 09:45:27 in-target: Reading package lists... Jun 4 09:45:27 in-target: Jun 4 09:45:27 in-target: W: GPG error: http://ftp.ports.debian.org/debian-ports sid InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DA1B2CEA81DCBC61 Jun 4 09:45:27 in-target: E: The repository 'http://ftp.ports.debian.org/debian-ports sid InRelease' is not signed. Jun 4 09:46:13 choose-mirror[1575]: DEBUG: command: wget --no-verbose https://ftp.ports.debian.org/debian-ports/dists/unstable/Release -O - | grep -E '^(Suite|Codename|Architectures):' Jun 4 09:46:13 choose-mir
Re: Problem installing Debian PowerPC Jessie on PowerMac G5 7,3 PCI-X
Scroll the list of mirrors all the way to the top. (you can use the up-arrow key repeatedly, or the home key once) You’ll see an “enter manually” option there. Rick > On May 19, 2019, at 10:24 AM, Noah Wolfe wrote: > > Hey Rick, > > Quick question, how do you manually enter repositories at > installation? For me, it always defaults to selecting a preexisting, > non-functional mirror off a list, and I never see any option to enter > anything manually, like it does by default in the ppc64 installations. > > Thanks, > Noah > > On May 18, 2019, at 9:43 PM, Rick Thomas wrote: > >> I’m trying to install Debian Jessie ppc64 8.11 on my PowerMac G5 >> 7,3 machine for comparison purposes with Adrian’s 10.0 “ports”. >> >> I downloaded the PowerPC 8.11 DVD and used it to install a default >> system. The only thing out of the ordinary was that I had to >> manually enter the packages mirror name as “archive.debian.org” >> since Jessie is no longer available on the normal mirror network. >> >> The installation ran to completion, finishing up with installing >> yaboot on the hard disk. >> >> But when it tried to reboot into the installed system, it got to >> “second level boot loader” and stopped with the blinking question- >> mark folder icon. >> >> Does anybody have any ideas as to what’s going wrong? >> >> I can provide log files for the installation if you think they >> would help. >> >> Thanks! >> Rick >
Problem installing Debian PowerPC Jessie on PowerMac G5 7,3 PCI-X
I’m trying to install Debian Jessie ppc64 8.11 on my PowerMac G5 7,3 machine for comparison purposes with Adrian’s 10.0 “ports”. I downloaded the PowerPC 8.11 DVD and used it to install a default system. The only thing out of the ordinary was that I had to manually enter the packages mirror name as “archive.debian.org” since Jessie is no longer available on the normal mirror network. The installation ran to completion, finishing up with installing yaboot on the hard disk. But when it tried to reboot into the installed system, it got to “second level boot loader” and stopped with the blinking question-mark folder icon. Does anybody have any ideas as to what’s going wrong? I can provide log files for the installation if you think they would help. Thanks! Rick
Re: Undelivered Mail Returned to Sender
> On May 5, 2019, at 2:34 AM, John Paul Adrian Glaubitz > wrote: > > > >> On May 5, 2019, at 11:33 AM, Rick Thomas wrote: >> >> The file was “.zip” compressed on a Mac — not “.gz’ on a Linux. Do you >> think that makes a difference? > > You should simply not send compressed attachments, especially for text. > > Adrian What do you recommend instead? The original file was 365KB. The compressed file was 48KB. Rick
Re: Undelivered Mail Returned to Sender
> On May 5, 2019, at 1:04 AM, Frank Scheiner wrote: > > Hi Rick, > > On 5/5/19 09:06, Rick Thomas wrote: >> >> >>> On May 4, 2019, at 9:28 PM, Mail Delivery System >>> wrote: >>> >>> : host bendel.debian.org[82.195.75.100] >>> said: >>>550 5.7.1 No attachments allowed (in reply to end of DATA command) >>> Reporting-MTA: dns; pb-sasl20.pobox.com >> >> Hmmm… I was trying to attach the syslog file from a failing install. >> >> What’s the approved method for doing that now, since it’s not allowing >> attachments? > > Did you compress the attachments? > > Strange indeed, maybe that was changed. But no longer allowing > attachments is not that useful. Maybe just an intermediate issue because > of spamming other lists? > > Cheers, > Frank The file was “.zip” compressed on a Mac — not “.gz’ on a Linux. Do you think that makes a difference? Rick
Re: Undelivered Mail Returned to Sender
> On May 4, 2019, at 9:28 PM, Mail Delivery System > wrote: > > : host bendel.debian.org[82.195.75.100] said: >550 5.7.1 No attachments allowed (in reply to end of DATA command) > Reporting-MTA: dns; pb-sasl20.pobox.com Hmmm… I was trying to attach the syslog file from a failing install. What’s the approved method for doing that now, since it’s not allowing attachments? Rick
Re: Updated installation images for Debian Ports 2019-04-20
> On May 2, 2019, at 9:56 PM, John Paul Adrian Glaubitz > wrote: > > Btw, are there any news regarding tests with grub-ofpathname? Otherwise > I would start working on these in the weekend after hopefully finishing > switching d-i/debian-cd over to GRUB for powerpc/ppc64. I’ll be happy to test grub-ofpathname (and any other open-firmware path-deduction programs) on my collection of G4 and G5 hardware, but I’ll need some guidance as to what kinds of tests you want done and where to get the programs to test. I mentioned this in a reply to Adrian’s original request, but I never got any response, so I assume it must have gotten lost. Enjoy! Rick
Re: G5 Suddenly Can't Boot Into GRUB
> On Apr 28, 2019, at 12:30 PM, Frank Scheiner wrote: > > On 4/28/19 18:08, John Paul Adrian Glaubitz wrote: >> Hi! >> >> On 4/25/19 9:20 AM, Mathieu Malaterre wrote: Best would be, of course, to fix the ofpathname from the IBM utils package. >>> >>> Could you give more details as to why you believe this would be 'best' >>> ? While I never had feedback from neither IBM group nor GRUB group >>> about my (WIP) patches, I believe grub path is the way to go. >> >> I don't have a particularly strong opinion on this. We can use either of the >> alternatives if they work fine or can be fixed with reasonable efforts. >> >> I don't know what the current state of grub-path is though. Can anyone with >> a PowerMac test it and report back? > > I'm actually on it, but still have some other things in the queue, so if > someone is quicker, no issue. What is “grub path" and how do I install it? If I can get it on my G5 and G4, I’ll be happy to test it. Though I’ll need somebody to coach me on what features nee to be tested. Enjoy! Rick
Re: Trying 2019-04-11 on PowerMac G4 Silver - [Solved]
> On Apr 26, 2019, at 12:26 PM, Frank Scheiner wrote: > > > This firmware limitation is now documented in the Debian Wiki at [1]. > > Up until not I can confirm that this limitation is **not** present on a > later PowerMac3,6 (see [1] for details about the testing). I'll > subsequently test for this issue on other Power Macs and document my > findings in the Debian Wiki. > > [1]: https://wiki.debian.org/PowerPC/ppc32#PowerMac3.2C4 > > Cheers, > Frank Thanks, Frank!
Re: Trying the 2019-04-15 image on PowerMac7,3 G5 dual processor -- GUI screen colors are strange.
> On Apr 15, 2019, at 3:34 PM, Rick Thomas wrote: > > I tried the 2019-04-12 debian-10.0-powerpc-NETINST-1.iso on a PowerMac G5 > dual processor (PowerMac7,3). > > https://everymac.com/systems/apple/powermac_g5/specs/powermac_g5_2.0_dp_2.html > > The image was burned to a CD-RW and booted by Open Firmware. > > A normal install was performed by keeping everything not otherwise mentioned > as default. > > Proprietary firmwares were not manually added. > > Module to slow spinning fans was loaded manually. > > Partitioning of the hard drive was guided and not manual. > I chose LVM, which forces a separate /boot partition. > All files were stored in one root partition only (/). > > The usual debian-ports mirror was manually entered. > > Base system and SSH server only were installed (default tasksel selection). > > Installation of GRUB was automatic and I was not asked anything. > No problems reported in this process. > > When it booted, there was the GRUB screen, as expected. I let it boot after > the usual few seconds timeout. All was well and the next thing I saw was a > login prompt. > > I added a “windfarm-core” line to /etc/modules to keep the fans from spinning > out-of-control — a reboot is required to make this take effect. > > Let me know if you need any further details. > > Thanks to everyone involved for all the hard work! > Rick I did it again with the April 15th iso. This time I installed the “mate” desktop — otherwise everything the same as above. All went well. One odd thing is that the mate GUI screen has strange colors. Possibly missing firmware for the video adapter? any suggestions as to how to fix that will be appreciated! Enjoy! Rick
Trying the 2019-04-12 image on PowerMac7,3 G5 dual processor
I tried the 2019-04-12 debian-10.0-powerpc-NETINST-1.iso on a PowerMac G5 dual processor (PowerMac7,3). https://everymac.com/systems/apple/powermac_g5/specs/powermac_g5_2.0_dp_2.html The image was burned to a CD-RW and booted by Open Firmware. A normal install was performed by keeping everything not otherwise mentioned as default. Proprietary firmwares were not manually added. Module to slow spinning fans was loaded manually. Partitioning of the hard drive was guided and not manual. I chose LVM, which forces a separate /boot partition. All files were stored in one root partition only (/). The usual debian-ports mirror was manually entered. Base system and SSH server only were installed (default tasksel selection). Installation of GRUB was automatic and I was not asked anything. No problems reported in this process. When it booted, there was the GRUB screen, as expected. I let it boot after the usual few seconds timeout. All was well and the next thing I saw was a login prompt. I added a “windfarm-core” line to /etc/modules to keep the fans from spinning out-of-control — a reboot is required to make this take effect. Let me know if you need any further details. Thanks to everyone involved for all the hard work! Rick
Re: GRUB Error on 04-12 Images
Hi Noah, What model machine are you trying to install on? Can you provide the full syslog file? Thanks, Rick > On Apr 14, 2019, at 4:37 PM, Noah Wolfe wrote: > > Okay, so I tried again with everything on default mount points, and the same > error and message appear. > > This appears to be some kind of problem with manual vs. automatic > partitioning... > > Just wanted to put this out there. > > Noah > > On Apr 14, 2019 7:08 PM, Noah Wolfe wrote: > Hi all, > > I tried the 04-12 images today, and manually partitioned the disk to this: > > Sda2, 1mb NewWorld partition > > Sda3, 1gb Ext2 partition mounted at /boot. Noatime. > > Sda4, 20gb Ext4 partition mounted at /. Noatime. > > Sda5, 5gb swap > > Sda6, 94gb Ext4 partition mounted at /home. Noatime. > > Installation goes well, then GRUB fails to install, giving the same message > we've always seen. > > Here's what syslog says: > > Mk-hfs-bootstrap: the HFS bootstrap partition couldn't be found. Cannot > continue! Exiting. > Main-menu: cat: can't open /var/lib/partman/devices/=dev=SDB/string of > numbers/mountpoint: no such file or directory > WARNING**: Configuring grub-installer failed with error code 1 > > I suspect it has to do with the noatime mount points, although this has never > happened before. Unless, of course, this is GRUB specific. > > I'll try again without them... > > Thanks all, > Noah
Re: Trying 2019-04-11 on PowerMac G4 Silver - [Solved]
> On Apr 13, 2019, at 5:39 AM, Frank Scheiner wrote: > > Do you happen to have a smaller disk (e.g. below 128 GB) available for > use? Or maybe you try with a separate small (512 MiB or so) `/boot` > partition directly after the HFS bootstrap partition, so the kernel is > located in the first GiB of this disk. Thanks, Frank! That was the clue it needed. I used the 2019-04-12 iso for my most recent test, just incase there was a change that might affect the problem. I did everything the same as I did for the original test, except that when it got to partitioning the disk, I chose guided partitioning and “Use whole disk, with LVM”. The LVM part forces it to create a separate /boot partition directly after the HFS one. That installed GRUB, which booted without a hitch. So it appears that this model of PowerMac has boot firmware that doesn’t like the high-address parts of large disk drives. Interestingly enough, this problem does not seem to affect the Linux kernel. Once past the bootstrap firmware, it works fine with the 300GB disk. Thanks to all! Rick root@dillserver:~# df -HTP | grep -v tmpfs > Filesystem Type Size Used Avail Use% Mounted on > /dev/mapper/dillserver--vg-root ext4 58G 1.1G 54G 2% / > /dev/sda3 ext2 248M 44M 192M 19% /boot > /dev/sda2 hfs20M 9.1M 11M 46% /boot/grub > root@dillserver:~# mac-fdisk -l /dev/sda > /dev/sda > #type name length base ( > size ) system > /dev/sda1 Apple_partition_map Apple 63 @ 1 ( > 31.5k) Partition map > /dev/sda2 Apple_Bootstrap untitled 39063 @ 64( > 19.1M) NewWorld bootblock > /dev/sda3 Apple_UNIX_SVR2 untitled 51 @ 39127 > (244.1M) Linux native > /dev/sda4 Linux_LVM untitled 624603271 @ 539128 > (297.8G) Unknown > /dev/sda5 Apple_Free Extra 49 @ 625142399 ( > 24.5k) Free space > > Block size=512, Number of Blocks=625142448 > DeviceType=0x0, DeviceId=0x0 > root@dillserver:~# lvs > LV VGAttr LSize Pool Origin Data% Meta% Move Log > Cpy%Sync Convert > root dillserver-vg -wi-ao 54.44g > > swap_1 dillserver-vg -wi-ao—— 1.43g > > root@dillserver:~# vgs > VG#PV #LV #SN Attr VSize VFree > dillserver-vg 1 2 0 wz—n- 297.83g <241.96g > root@dillserver:~# lsblk > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > sda 8:00 298.1G 0 disk > |-sda1 8:10 31.5K 0 part > |-sda2 8:20 19.1M 0 part /boot/grub > |-sda3 8:30 244.1M 0 part /boot > |-sda4 8:40 297.9G 0 part > | |-dillserver--vg-root 254:00 54.5G 0 lvm / > | `-dillserver--vg-swap_1 254:10 1.4G 0 lvm [SWAP] > `-sda5 8:50 24.5K 0 part
Re: Trying 2019-04-11 on PowerMac G4 Silver
> On Apr 13, 2019, at 2:13 PM, John Paul Adrian Glaubitz > wrote: > > > > On Apr 13, 2019, at 11:11 PM, Rick Thomas wrote: > >> I’m not sure what you mean by “model number”? > > > https://everymac.com/systems/by_capability/mac-specs-by-model-number-family-number.html It seems to be this one… > https://everymac.com/systems/apple/powermac_g4/specs/powermac_g4_533.html which would make it > > Model M5183 (EMC 1862) I’ll check the plaque on the back to make sure. Rick
Re: Trying 2019-04-11 on PowerMac G4 Silver
> On Apr 13, 2019, at 2:01 PM, John Paul Adrian Glaubitz > wrote: > > > >> On Apr 13, 2019, at 10:42 PM, Rick Thomas wrote: >> >> >> >>> On Apr 13, 2019, at 6:26 AM, John Paul Adrian Glaubitz >>> wrote: >>> >>> On 4/13/19 10:36 AM, Rick Thomas wrote: >>>>> Loading Linux 4.19.0-4-powerpc … >>>>> error: failure reading sector 0x208099d7 from >>>>> `ieee1275//pci@200/mac-io@17/ata-4@1f00/disk@0’ >>>>> >>>>> Loading initial ramdisk … >>>>> error: you need to load the kernel first >>>>> >>>>> Press any key to continue … >>>> >>>> I was able to boot into rescue mode from the CD-R and retrieved the >>>> attached information. >>>> Let me know if there’s anything more you need. >>> >>> Hmm, this sounds as if there are problems with your disk or disk controller. >>> >>> Can you tell me the exact model number of your Mac? I might have the same >>> sitting in the storage room of the university and give it a try myself >>> soonish. >> >> The install went fine, with no hint of hardware problems. For what that’s >> worth. >> >> Here’s the output of ‘cat /proc/cpuinfo’ > > Can you just give me the Apple model number? That’s easier. > > Adrian I’m not sure what you mean by “model number”? As given in /proc/cpuinfo, it says > model : PowerMac3,4 If that’s not what you want, I’ll go look at the plaque on the back of the chassis, maybe that will have something? Rick
Re: Trying 2019-04-11 on PowerMac G4 Silver
> On Apr 13, 2019, at 6:26 AM, John Paul Adrian Glaubitz > wrote: > > On 4/13/19 10:36 AM, Rick Thomas wrote: >>> Loading Linux 4.19.0-4-powerpc … >>> error: failure reading sector 0x208099d7 from >>> `ieee1275//pci@200/mac-io@17/ata-4@1f00/disk@0’ >>> >>> Loading initial ramdisk … >>> error: you need to load the kernel first >>> >>> Press any key to continue … >> >> I was able to boot into rescue mode from the CD-R and retrieved the attached >> information. >> Let me know if there’s anything more you need. > > Hmm, this sounds as if there are problems with your disk or disk controller. Was there anything in the syslog? (I attached it to the original email) Is there anything else you’d like me to extract from it before I try the 2019-04-12 iso, which will wipe away the remaining evidence from this attempt. Enjoy! Rick
Re: Trying 2019-04-11 on PowerMac G4 Silver
> On Apr 13, 2019, at 6:26 AM, John Paul Adrian Glaubitz > wrote: > > On 4/13/19 10:36 AM, Rick Thomas wrote: >>> Loading Linux 4.19.0-4-powerpc … >>> error: failure reading sector 0x208099d7 from >>> `ieee1275//pci@200/mac-io@17/ata-4@1f00/disk@0’ >>> >>> Loading initial ramdisk … >>> error: you need to load the kernel first >>> >>> Press any key to continue … >> >> I was able to boot into rescue mode from the CD-R and retrieved the attached >> information. >> Let me know if there’s anything more you need. > > Hmm, this sounds as if there are problems with your disk or disk controller. > > Can you tell me the exact model number of your Mac? I might have the same > sitting in the storage room of the university and give it a try myself > soonish. The install went fine, with no hint of hardware problems. For what that’s worth. Here’s the output of ‘cat /proc/cpuinfo’ > processor : 0 > cpu : 7410, altivec supported > temperature : 35-37 C (uncalibrated) > clock : 533.32MHz > revision : 1.3 (pvr 800c 1103) > bogomips : 66.58 > > timebase : 33290001 > platform : PowerMac > model : PowerMac3,4 > machine : PowerMac3,4 > motherboard : PowerMac3,4 MacRISC2 MacRISC Power Macintosh > detected as : 69 (PowerMac G4 Silver) > pmac flags: 0010 > L2 cache : 1024K unified > pmac-generation : NewWorld > Memory: 1536 MB and ‘df -HTP’ > Filesystem Type Size Used Avail Use% Mounted on > /dev/sda3 ext4 313G 1.2G 296G 1% / > devtmpfs devtmpfs 781M 0 781M 0% /dev > none tmpfs 159M 91k 158M 1% /run and ‘mac-fdisk -l’ > /dev/sda > #type name length base ( > size ) system > /dev/sda1 Apple_partition_map Apple 63 @ 1 ( > 31.5k) Partition map > /dev/sda2 Apple_Bootstrap untitled 39063 @ 64( > 19.1M) NewWorld bootblock > /dev/sda3 Apple_UNIX_SVR2 untitled 622087891 @ 39127 > (296.6G) Linux native > /dev/sda4 Apple_UNIX_SVR2 swap 3015381 @ 622127018 ( > 1.4G) Linux swap > /dev/sda5 Apple_Free Extra 49 @ 625142399 ( > 24.5k) Free space > > Block size=512, Number of Blocks=625142448 > DeviceType=0x0, DeviceId=0x0 Does any of that help? Rick
Trying 2019-04-11 on PowerMac G4 Silver
I tried the 2019-04-11 debian-10.0-powerpc-NETINST-1.iso on a PowerMac G4 Silver (PowerMac3,4). The image was burned to a CD-R and booted by Open Firmware. A normal install was performed by keeping everything not otherwise mentioned as default. Proprietary firmwares were not manually added. Module to slow spinning fans was not loaded, as it is not needed on this machine model. Partitioning of the hard drive was guided and not manual. All files were stored in one partition only (/). The usual debian-ports mirror was manually entered. Base system and SSH server only were installed (default tasksel selection plus SSH and minus print-server). Installation of GRUB was automatic and I was not asked anything. No problems reported in this process. When it booted, there was the GRUB screen, as expected. I let it boot after the usual few seconds timeout. Unfortunately, the boot failed: > Loading Linux 4.19.0-4-powerpc … > error: failure reading sector 0x208099d7 from > `ieee1275//pci@200/mac-io@17/ata-4@1f00/disk@0’ > > Loading initial ramdisk … > error: you need to load the kernel first > > Press any key to continue … I was able to boot into rescue mode from the CD-R and retrieved the attached information. Let me know if there’s anything more you need. I’ll try 2019-04-12 on Saturday. Thanks to all for the good work so far! Rick var-log-installer.tar.xz Description: Binary data mac-fdisk.out Description: Binary data df-HTP Description: Binary data cpuinfo Description: Binary data
Re: baffled .. the 2019-01-27 debian-10.0-ppc64-NETINST-1.iso not bootable
It’s *possible* that the DVD drive in the dual-socket machine is not able to boot from DVD-RW. (I have seen this before occasionally) Try burning to a DVD-R Just a thought… Rick PS: Also note that Adrian is in the process of making an updated boot CD for PowerPC64. See the recent mail in the Debian PowerPC list. > On Apr 5, 2019, at 8:16 PM, Dennis Clarke wrote: > > On 4/5/19 11:00 PM, Dennis Clarke wrote: >> >> So here is further odd behavior. At this point I am just going to dig in >> and keep plugging away here. >> >> I fetched from : >> >> >> https://cdimage.debian.org/cdimage/ports/2019-01-27/debian-10.0-ppc64-NETINST-1.iso >> > > > Carefulyl tested. It boots fine on a PowerMac G5 "quad" unit but not on > a PowerMac G5 which is a dual socket PPC970FX unit. No idea why. > > I was able to get a very very basic install from the 2018 netinst but > then I am stonewalled by the usual gpg signature issues : > > root@callisto:~# vi /etc/apt/sources.list > root@callisto:~# apt-get update > Get:1 http://ftp.debian.org/debian unstable InRelease [242 kB] > > Get:2 http://incoming.debian.org/debian-buildd buildd-unstable InRelease > [54.5 kB] > Get:3 http://ftp.ports.debian.org/debian-ports unstable InRelease [47.1 > kB] > Get:4 http://incoming.ports.debian.org/buildd unstable InRelease [49.1 > kB] > Get:5 http://ftp.ports.debian.org/debian-ports unreleased InRelease > [52.4 kB] > Get:6 http://incoming.debian.org/debian-buildd buildd-unstable/main > Sources [37.5 kB] > Err:3 http://ftp.ports.debian.org/debian-ports unstable InRelease > The following signatures couldn't be verified because the public key > is not available: NO_PUBKEY DA1B2CEA81DCBC61 > Get:7 http://ftp.debian.org/debian unstable/main Sources [8735 kB] > Err:5 http://ftp.ports.debian.org/debian-ports unreleased InRelease > The following signatures couldn't be verified because the public key > is not available: NO_PUBKEY DA1B2CEA81DCBC61 > Err:4 http://incoming.ports.debian.org/buildd unstable InRelease > The following signatures couldn't be verified because the public key > is not available: NO_PUBKEY DA1B2CEA81DCBC61 > Reading package lists... Done > > W: GPG error: http://ftp.ports.debian.org/debian-ports unstable > InRelease: The following signatures couldn't be verified because the > public key is not available: NO_PUBKEY DA1B2CEA81DCBC61 > E: The repository 'http://ftp.ports.debian.org/debian-ports unstable > InRelease' is not signed. > N: Updating from such a repository can't be done securely, and is > therefore disabled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration details. > W: GPG error: http://ftp.ports.debian.org/debian-ports unreleased > InRelease: The following signatures couldn't be verified because the > public key is not available: NO_PUBKEY DA1B2CEA81DCBC61 > E: The repository 'http://ftp.ports.debian.org/debian-ports unreleased > InRelease' is not signed. > N: Updating from such a repository can't be done securely, and is > therefore disabled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration details. > W: GPG error: http://incoming.ports.debian.org/buildd unstable > InRelease: The following signatures couldn't be verified because the > public key is not available: NO_PUBKEY DA1B2CEA81DCBC61 > E: The repository 'http://incoming.ports.debian.org/buildd unstable > InRelease' is not signed. > N: Updating from such a repository can't be done securely, and is > therefore disabled by default. > N: See apt-secure(8) manpage for repository creation and user > configuration details. > root@callisto:~# > root@callisto:~# > root@callisto:~# uname -a > Linux callisto 4.16.0-1-powerpc64 #1 SMP Debian 4.16.5-1 (2018-04-29) > ppc64 GNU/Linux > root@callisto:~# > root@callisto:~# cat /etc/debian_version > buster/sid > root@callisto:~# > > So .. that's nice. Not sure how to get around the need for that key. > > Dennis >
Best way too install Debian Jessie on powerpc/powerpc64 ?
Is there a new install CD/DVD for PowerPC Jessie now that it’s repo has been moved to archives? And in a similar vein, what changes do I need to make to sources.list for a Mac powerpc and/or powerpc64 that already has Jessie installed (*not* Sid) Thanks! Rick
Re: Installation of Debian on an iMac PowerPC
Hi David, Try installing with the “oldstable”/“Jessie” CD. http://cdimage.debian.org/mirror/cdimage/archive/8.11.0/powerpc/iso-cd/ Grub for Powerpc is still a work in progress. It may not work on your old G3 machine. Jessie uses the older “yaboot” bootloader, which may be more stable for your situation. Everybody seems to agree that Grub is the wave of the future, but that wave hasn’t fully crested yet. Hope this helps! Rick > On Feb 11, 2019, at 10:58 AM, David VANTYGHEM wrote: > > Hello, > > I'm a beginner on Macintosh. > > I'm trying to install Debian (+ LXDE) on my iMac G3. > > I'm using a CD-ROM with > https://cdimage.debian.org/cdimage/ports/2019-01-27/debian-10.0-powerpc-NETINST-1.iso > on it. > > I've got 2 errors : > > 1) An error during the softwares installation : > https://framapic.org/U8WJdTtyBnT6/4y7B4AB68uBz.jpg > > 2) A more important error with GRUB that doesn't install : > > https://framapic.org/akOHeksS12oS/Da09AivOaCdX.png > > https://framapic.org/mJ8AHgLUdQXb/7xPInXj4wSDY.png > > And I can't boot after the end of the installation : > > https://framapic.org/52MPBtyV0Qrw/Z9Zi8opwh3F1.png > > > I tested the installation in a virtual computer with QUEMU (AQEMU). I've > got only the 2) error and the same problem to boot. > > Is it a bug or did I make something wrong ? > > -- > David VANTYGHEM > Mél. : david.vantyg...@free.fr > Installer facilement GNU/Linux : http://numopen.fr > >.--. > |o_o | > ||_/ | > //\\Envoyé avec mon GNU/Linux > (| |) > / \_ _/ \ > \___)=(___/ >
Debian 10.0 ppc64 NETINST-1 2019/01/27 -- windfarm on PowerMac G5 7,3
I just tried installing the 2019/01/27 ppc64 NETINST-1 on my Powermac G5 7,3. It booted OK and went thru the preliminaries, but about the time it got to loading the partitioner, the windfarm fans started going crazy and I had to shut it down. I seem to remember that there was a module I could go to the console and modprobe that would control that, but I forget the details. Anybody got a clue they feel like sharing with me? Anybody else see this happening? Enjoy! Rick
Re: PPC64 Image Installation Error
> On Feb 2, 2019, at 8:11 AM, John Paul Adrian Glaubitz > wrote: > > > > On Feb 2, 2019, at 1:25 PM, Noah Wolfe wrote: >> The matter is all the more compacted, of course, due to the fact it doesn't >> even have ifconfig OOTB, giving you few usable methods to fix network errors. >> > > ifconfig has been replaced by the “ip” command these days on most Linux > distributions. > > It’s a change unrelated to ppc64, every architecture works like this now. > > Adrian The ifconfig program hasn’t gone away completely. It’s no longer installed by default, but it is available in the “net-tools” package. To install it do: apt-get net-tools Of course, it would be a good idea to read the man page for ip(8) sometime soon. Lot’s more useful features, and it seems to be the wave of the future in network admin these days. Enjoy! Rick
Re: PPC64 Image Installation Error
Hi again Noah, You can install a bare-bones system without any GUI by de-selecting the “Debian Desktop” task (and leaving de-selected all the individual desktops sub-tasks) when it gets to the “Running Tasksel” stage. Use the arrow keys to move the highlight to a line you want to select or de-select. Use the space bar to select (asterisk in the box) or de-select (space in the box) that row. I usually choose to select the “SSH server” and the “basic system”(last line) and leave everything else de-selected. HTH, Rick > On Feb 1, 2019, at 4:32 PM, Noah Wolfe wrote: > > Perhaps I spoke too soon... > > After reinstalling the system due to an unresolvable networking error (A > perfectly stable connection would drop without reason, something that did not > happen in Ubuntu 16.04, at least after network-manager was installed. The > only fix was to deactivate and reactivate the wired connection in nmtui, > which itself as a part of network-manager had to be manually downloaded from > another OS in individual package format as it did not come out of the box.), > it seems I am not able to fully boot into it via the yaboot from Ubuntu > 16.04, which works well and recognizes both systems without any problems, > boots into either without issue, but then Debian throws a BusyBox initramfs > terminal halfway through booting, citing: "Gave up waiting for root device.", > "Missing modules (cat /proc/modules; ls /dev)", "ALERT! > /dev/disk/by-uuid/ does not exist. Dropping to a > shell!". Absolutely everything is partitioned and configured exactly the same > as before, when I had it working. The only thing different, however, is > perhaps having chosen the option to install LXQt in favor of GNOME, which was > the environment installed when it was able to boot without issue. The same > blockage occurs when LXDE is chosen, as well. I wish it would allow you to > install your system without needing to choose a desktop environment, which > just lengthens installation time by a great amount. > > From my experiences alone in the last few days, the ppc64 versions really put > the "unstable" in "Sid". > > In any case, please advise. Thank you. > > From: Noah Wolfe > Sent: Friday, February 1, 2019 2:08 PM > To: Rick Thomas > Cc: PowerPC List Debian; John Paul Adrian Glaubitz > Subject: Re: PPC64 Image Installation Error > > Thanks, Rick. > I got around this issue by simply making the /boot partition (sda2) 1 GB > instead of 1 MB, and the / partition (sda3) doubled to 80 GB. Using this same > method with a reinstall of Ubuntu Server 16.04 (which was giving me the same > error when it was installed in partitions 6, 7, 8, and 9, below Sid) I am > now, as a result, able to dual boot between it and Debian. > So it really goes to show that sometimes the best solutions in life are > usually the easiest ones. > But I still found the 01-27 build to be unable to install the kernel due to > an apparent "lack of space" in whatever configuration I put it in (save for > the aforementioned method), so that still needs to be fixed. > And, a lot of ppc64 packages are experiencing issues unseen in the powerpc > equivalents. Xfwm4 puts out graphical glitches and artifacts when any windows > are moved, or when the cursor moves over any windows, and GNOME 3 hasn't > displayed any color besides pinkish hues since Jessie, if I'm remembering > correctly. > Anyway, thank you for your time. > N > On Jan 31, 2019 5:16 AM, Rick Thomas wrote: > > > > Hi Noah, > > > > Is it possible for you to temporarily replace the hard drive in your > > machine with one you don’t mind experimenting on? > > > > If so, after a clean installation onto the fresh hard disk, what you want > > to finish up your installation with is something that looks kind of like > > this: > > > > > root@msmini:~# mac-fdisk -l /dev/sda > > > /dev/sda > > > #type name length base > > > ( size ) system > > > /dev/sda1 Apple_partition_map Apple 63 @ 1 > > > ( 31.5k) Partition map > > > /dev/sda2 Apple_Bootstrap untitled1954 @ 64 > > > (977.0k) NewWorld bootblock > > > /dev/sda3 Apple_UNIX_SVR2 untitled 51 @ 2018 > > > (244.1M) Linux native > > > /dev/sda4 Linux_LVM untitled 468360060 @ 502019 > > > (223.3G) Unknown > > > /dev/sda5 Apple_Free Extra 49 @ > > > 468862079 ( 24.5k) Free space > > > > > >
Re: PPC64 Image Installation Error
16.04, which used up 313 KB, leaving 7.32 MB unused. > #3 40 GB Ext4 System Partition (mounted at /) - Designated to Ubuntu > Server 16.04 > #4 4.8 GB Swap Partition (4.5 GB installed) - Designated to Ubuntu > Server 16.04 > #5 455 GB Ext4 Home Partition (mounted at /home) - Designated to Ubuntu > Server 16.04 > > #6 8 MB Ext2 Boot Partition (to be mounted at /boot) - Designated to > Debian 10, which the installer left with 298 KB used, leaving 7.34 MB > unused. (Which is why I didn't jump to it being a space issue.) > #7 40 GB Ext4 System Partition (to be mounted at /) - Designated to > Debian 10 > #8 4.8 GB Swap Partition (ditto) - Designated to Debian 10 > #9 455 GB Ext4 Home Partition (to be mounted at /home) - Designated to > Debian 10 > > This was actually also the first time I tried to dual-boot Linux > systems on PPC, so I now feel like I'm very obviously at fault for > this. > > But we're always learning. I've been on this train for just under a > year and not only do I thank myself every day, I also learn something > new every day. Or at least, every other day, perhaps. Just as well.Thanks, > all. > > N > > On Tue, 2019-01-29 at 03:41 -0800, Rick Thomas wrote: >> >>> >>> On Jan 28, 2019, at 11:19 PM, Noah Wolfe >>> wrote: >>> >>> Hello. >>> >>> I'm running a Late 2005 Power Mac G5 (11,2), and although the >>> regular >>> powerpc installer images may be fixed from most problems at this >>> point >>> (going off of other people's posted experiences), the newest >>> netinstall >>> ppc64 images from 2019-01-27 >>> (http://cdimage.debian.org/cdimage/ports/2 >>> 019-01-27/) are still unable to install the linux-image-powerpc64 >>> package during normal (non-expert) installation, and when the >>> installer >>> gives you the notification of this, it quits the rest of the >>> installation, leaving an incomplete base system. >>> >>> The notification window itself displays "Unable to install the >>> selected >>> kernel" in red text at the top, with the description "An error was >>> returned while trying to install the selected kernel into the >>> target >>> system." in regular black text. It specifies with "Kernel package: >>> 'linux-image-powerpc64'." below, and adds "Check /var/log/syslog or >>> see >>> virtual console 4 for the details." at the end. It is accompanied >>> by a >>> blue backdrop instead of the usual red. >>> >>> Upon further inspection into virtual console 4 (Ctrl+Alt+F4), the >>> last >>> remaining written installer activity is displayed, a particular >>> point >>> of interest after the usual "Unpacking linux-image-4.19.0-2- >>> powerpc64 >>> (4.19.16-1) ...", being: "dpkg: error processing archive >>> /media/cdrom//pool-ppc64/main/l/linux/linux-image-4.19.0-2- >>> powerpc64_4.19.16-1_ppc64.deb (--unpack)", "Cannot copy extracted >>> data >>> for './boot/vmlinux-4.19.0-2-powerpc64' to '/boot/vmlinux-4.19.0-2- >>> powerpc64.dpkg-new': failed to write (No space left on device)", >>> "dpkg- >>> deb: error: paste subprocess was killed by signal (Broken pipe)", >>> "W: >>> Last kernel image has been removed, so removing the default >>> symlinks". >>> >>> It then goes on to normally select, prepare to unpack, and unpack >>> linux-image-powerpc64, only to stop with "Errors were encountered >>> while >>> processing: /media/cdrom//pool-ppc64/main/l/linux/linux-image- >>> 4.19.0-2- >>> powerpc64_4.19.16-1_ppc64.deb", "error: exiting on error base- >>> installer/kernel/failed-install", "WARNING **: Configuring >>> 'bootstrap- >>> base' failed with error code 30", "WARNING **: Menu item >>> 'bootstrap- >>> base' failed.", ending there. >>> >>> Debian 7.11, 8.11, and the May 2018 Sid netinstall cd, all install >>> onto >>> this machine (given the same partition tables) without a hitch, >>> along >>> with Ubuntu Server 16.04.5. Though admittedly they were all of >>> regular >>> powerpc decent and not ppc64 as seen here. I had also tried the >>> Debian >>> 9 installer port for ppc64 >>> (http://cdimage.debian.org/cdimage/ports/9.0 >>> /ppc64/iso-cd/) and got the same result displayed here, so it >>> appears >>> this may be a longstanding issue among the ppc64 builds, at least >>> from >>> my point of view. >>> >>> Putting that aside, maybe something was overlooked in the ppc64 >>> images >>> specifically when building the new batches? To my knowledge, much >>> of it >>> should be synonymous with the regular powerpc builds, save for a >>> 64-bit >>> userspace over a 32-bit one, but of course, I'm not a developer. >>> >>> In any case, all is much appreciated. >>> >>> N >> Hi Noah, >> >> It sounds like you’re running out of free space in the partition that >> contains the /boot directory. >> >> Can you describe the steps you used to partition the disk? In >> particular, if you are re-using the /boot partition so as not to >> interfere with your existing installation, how much free space is >> there in it. E.g. on your existing (working) setup do >> df -HTP /boot >> >> hope it helps! >> Rick >>
Re: PPC64 Image Installation Error
> On Jan 28, 2019, at 11:19 PM, Noah Wolfe wrote: > > Hello. > > I'm running a Late 2005 Power Mac G5 (11,2), and although the regular > powerpc installer images may be fixed from most problems at this point > (going off of other people's posted experiences), the newest netinstall > ppc64 images from 2019-01-27 (http://cdimage.debian.org/cdimage/ports/2 > 019-01-27/) are still unable to install the linux-image-powerpc64 > package during normal (non-expert) installation, and when the installer > gives you the notification of this, it quits the rest of the > installation, leaving an incomplete base system. > > The notification window itself displays "Unable to install the selected > kernel" in red text at the top, with the description "An error was > returned while trying to install the selected kernel into the target > system." in regular black text. It specifies with "Kernel package: > 'linux-image-powerpc64'." below, and adds "Check /var/log/syslog or see > virtual console 4 for the details." at the end. It is accompanied by a > blue backdrop instead of the usual red. > > Upon further inspection into virtual console 4 (Ctrl+Alt+F4), the last > remaining written installer activity is displayed, a particular point > of interest after the usual "Unpacking linux-image-4.19.0-2-powerpc64 > (4.19.16-1) ...", being: "dpkg: error processing archive > /media/cdrom//pool-ppc64/main/l/linux/linux-image-4.19.0-2- > powerpc64_4.19.16-1_ppc64.deb (--unpack)", "Cannot copy extracted data > for './boot/vmlinux-4.19.0-2-powerpc64' to '/boot/vmlinux-4.19.0-2- > powerpc64.dpkg-new': failed to write (No space left on device)", "dpkg- > deb: error: paste subprocess was killed by signal (Broken pipe)", "W: > Last kernel image has been removed, so removing the default symlinks". > > It then goes on to normally select, prepare to unpack, and unpack > linux-image-powerpc64, only to stop with "Errors were encountered while > processing: /media/cdrom//pool-ppc64/main/l/linux/linux-image-4.19.0-2- > powerpc64_4.19.16-1_ppc64.deb", "error: exiting on error base- > installer/kernel/failed-install", "WARNING **: Configuring 'bootstrap- > base' failed with error code 30", "WARNING **: Menu item 'bootstrap- > base' failed.", ending there. > > Debian 7.11, 8.11, and the May 2018 Sid netinstall cd, all install onto > this machine (given the same partition tables) without a hitch, along > with Ubuntu Server 16.04.5. Though admittedly they were all of regular > powerpc decent and not ppc64 as seen here. I had also tried the Debian > 9 installer port for ppc64 (http://cdimage.debian.org/cdimage/ports/9.0 > /ppc64/iso-cd/) and got the same result displayed here, so it appears > this may be a longstanding issue among the ppc64 builds, at least from > my point of view. > > Putting that aside, maybe something was overlooked in the ppc64 images > specifically when building the new batches? To my knowledge, much of it > should be synonymous with the regular powerpc builds, save for a 64-bit > userspace over a 32-bit one, but of course, I'm not a developer. > > In any case, all is much appreciated. > > N Hi Noah, It sounds like you’re running out of free space in the partition that contains the /boot directory. Can you describe the steps you used to partition the disk? In particular, if you are re-using the /boot partition so as not to interfere with your existing installation, how much free space is there in it. E.g. on your existing (working) setup do df -HTP /boot hope it helps! Rick
Re: installing NETINST 20190127 on Mac mini G4
> On Jan 29, 2019, at 12:00 AM, Michael Cree wrote: > > On Mon, Jan 28, 2019 at 12:45:10PM +0100, John Paul Adrian Glaubitz wrote: >> On 1/28/19 12:34 PM, Rick Thomas wrote: >>> I realize that this may require some programming, but would it be possible >>> to have it ask a question early on (maybe at or before the beginning of >>> partitioning) requesting the user to choose between yaboot and grub? Then >>> the partitioner would automatically create the necessary partition(s) and >>> “install boot loader” would automatically install the chosen boot loader >>> conditioned on the answer to the question… >> >> Yaboot is unmaintained upstream and does not support modern ext4 features. In >> order for Yaboot to work properly, you have to turn certain features in ext4 >> off, otherwise it won't work and the boot fails. > > Can you not have an ext3 boot partition and the rest of the OS on > an ext4 partition? > > Cheers > Michael. Hi Michael, I don’t know if it works with ext3, but I can personally vouch for it with ext2. Rick
