Bug#1071542: boost1.83: Please enable context library on ppc64
Source: boost1.83 Version: 1.83.0-2.1+b1 Severity: normal User: debian-powerpc@lists.debian.org Usertags: ppc64 X-Debbugs-Cc: debian-powerpc@lists.debian.org Hello, the context library is not being installed on ppc64 in debian/control despite being enabled in debian/rules. Please add ppc64 to the list of supported architectures for the context library and make sure it's actually being built and installed. Tests can be performed on the porterbox perotto.debian.net. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Boot failure with ppc64 port on iMacs G5
Hi, On Wed, 2024-03-06 at 12:57 +1100, Michael Ellerman wrote: > > p, the second, older image works as expected. However, the recent one does > > not > > and I have absolutely no clue why. > > I actually tested both, and both work, but then I cited the wrong one in > my email >_< > > So at least on qemu that newer kernel is OK: > > Preparing to boot Linux version 6.6.15-powerpc64 > (debian-ker...@lists.debian.org) (gcc-13 (Debian 13.2.0-13) 13.2.0, GNU ld > (GNU Binutils for Debian) 2.42) #1 SMP Debian 6.6.15-2 (2024-02-04) > ... > Booting Linux via __start() @ 0x0480 ... > Hello World ! > smp_core99_probe > smp_core99_bringup_done > Starting system log daemon: syslogd, klogd. Here is a freshly generated image using kernel 6.7.12 as the installer kernel: > https://cdimage.debian.org/cdimage/ports/tests/ppc64-test-20240511/debian-12.0.0-ppc64-NETINST-1.iso Still hangs for me with QEMU emulating a PPC970. Will retest once kernel 6.8.x enters Debian unstable. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: setting up a sbuild chroot - which key?
> On May 9, 2024, at 5:15 PM, Riccardo Mottola > wrote: > > Hi, > > perhaps I'm loosing myself in a glass of water here. > > John Paul Adrian Glaubitz wrote: >> You include the keyring when creating the chroot using the "--include" >> option: >> >> # sbuild-createchroot unstable /srv/chroot/unstable-powerpc \ >> --arch=powerpc --variant=buildd --include=debian-ports-archive-keyring \ >> http://ftp.ports.debian.org/debian-ports > I don't need buildd, so I think I can simplify the call to createchroot. Yes, you need “buildd”. > sudo sbuild-createchroot unstable debian-powerpc > --include=debian-ports-archive-keyring > http://ftp.ports.debian.org/debian-ports > > this answer me > > E: Release signed by unknown key (key id 8D69674688B6CB36) >The specified keyring /usr/share/keyrings/debian-archive-keyring.gpg may > be incorrect or out of date. >You can find the latest Debian release key at > https://ftp-master.debian.org/keys.html > > Thanks to this error and some internet search [1] > > sudo apt-get install debian-ports-archive-keyring Correct. You can also pass “—no-check-gpg”. > Reissuing the command, still gets the same error. Then I follow Jeffrey's > advice of using --keyring > > sudo sbuild-createchroot unstable debian-powerpc > --include=debian-ports-archive-keyring --keyring > /usr/share/keyrings/debian-ports-archive-keyring.gpg > http://ftp.ports.debian.org/debian-ports > > <... iBook fan goes full power and wait wait ...> > > And I seem to have an environment. > > Then I go into python-2.7 directory I got with the command: > > $ dget > -uhttp://snapshot.debian.org/archive/debian/20220801T085926Z/pool/main/p/python2.7/python2.7_2.7.18-13.2.dsc > > > I issue: > > sbuild -d sid --arch-all --arch=powerpc python2.7_2.7.18-13.2.dsc > > but I get: > Package: python2.7 > Version: 2.7.18-13.2 > Source Version: 2.7.18-13.2 > Distribution: sid > Machine Architecture: powerpc > Host Architecture: powerpc > Build Architecture: powerpc > Build Type: binary Did you run sbuild-createchroot and did it succeed? > E: Chroot for distribution sid, architecture powerpc not found > E: Error creating chroot > > > I suppose the issue is because the distribution is sid, but we want bookworm? There is no bookworm for powerpc, just sid. Adrian > Riccardo > > [1] https://github.com/go-debos/debos/issues/463
Re: setting up a sbuild chroot - which key?
Hello, On Fri, 2024-05-03 at 23:58 +0200, Riccardo Mottola wrote: > no hint for me which key to use? or if I miss one, where to get it? > > I have apt-get working, so I think I have the key. You include the keyring when creating the chroot using the "--include" option: # sbuild-createchroot unstable /srv/chroot/unstable-powerpc \ --arch=powerpc --variant=buildd --include=debian-ports-archive-keyring \ http://ftp.ports.debian.org/debian-ports Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Sid June 23-2023 Fresh install has broken “start-stop-daemon”
Hello, On Thu, 2024-05-02 at 16:38 +0100, md.ben...@gmail.com wrote: > I did a fresh install using the suggested Sid June 23-2024 iso and am glad > to report it’s working great and I was able to transfer it to the G5 Quad > and have it activate the temporary non-Apple GPU on the graphical desktop. Great. > I encountered a problem when trying to install packages, however, that > apt/dpkg > falls over with an error: > “start-stop-daemon” not found or is not exectutable I have run into this as well and seems to be an issue with this particular image. Try downloading and installing the "dpkg" package manually. # apt download dpkg # dpkg -i dpkg*deb Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Sid Install on PowerMac G5
Hi Mark, On Tue, 2024-04-30 at 09:05 +0100, md.ben...@gmail.com wrote: > smp_core99_probe > smp_core99_kick_cpu > smp_core99_kick_cpu_done > smp_core99_bringup_done This is a known, but yet unresolved regression, see [1]. Try using an older installer image, the last known to work image is the one from June, 18th 2023 [2]. The issue has been reported to the PowerPC kernel maintainers, but so far there has been no success in figuring out what's wrong. Adrian > [1] https://lists.debian.org/debian-powerpc/2024/02/msg00019.html > [2] > https://cdimage.debian.org/cdimage/ports/snapshots/2023-06-18/debian-12.0.0-ppc64-NETINST-1.iso -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Performing dist-upgrade on powerpc and ppc64
Hi, On Tue, 2024-04-16 at 13:27 -0400, Jeffrey Walton wrote: > In the old days, you could setup a chroot for PowerPC using the following. I > think it still works, but I recall something about using qemu-debootstrap > nowadays. > > qemu-debootstrap --arch=powerpc --keyring > /usr/share/keyrings/debian-ports-archive-keyring.gpg \ > --variant=buildd --exclude=debfoster unstable debian-powerpc > http://ftp.ports.debian.org/debian-ports > > The Debian host can use any flavor of Debian. I usually use Stable for the > host. > > The Debian chroot guest must use Unstable. Once you create the chroot guest, > open the guest's /etc/apt/sources.list and change it to Unstable. There is no need to use qemu-debootstrap these days, sbuild will just work transparently once you have qemu-user installed. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Performing dist-upgrade on powerpc and ppc64
Hello, On Tue, 2024-04-16 at 18:14 +0200, Riccardo Mottola wrote: > So sbuild complaints I need a chroot environment. I guess that helps > with build-dependencies only being temporary installed for the build, as > opposite to use dpkg-buildpackage directly? I suggest reading the howto or the manpage: > https://wiki.debian.org/sbuild Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Performing dist-upgrade on powerpc and ppc64
On Sun, 2024-04-14 at 22:53 -0600, Eric Ramsey wrote: > I will note that my install is currently having issues with gnutls. > ``` > The following packages have unmet dependencies: > connman : Depends: libgnutls30 (>= 3.7.5) but it is not installable > dirmngr : Depends: libgnutls30 (>= 3.7.5) but it is not installable > gkrellm : Depends: libgnutls30 (>= 3.7.0) but it is not installable > glib-networking : Depends: libgnutls30 (>= 3.7.5) but it is not installable > libapt-pkg-perl : Depends: libapt-pkg6.0 (>= 2.1.20) but it is not > installable > libarchive13 : Depends: libnettle8 but it is not installable > libavformat59 : Depends: libgnutls30 (>= 3.7.5) but it is not installable > libcups2 : Depends: libgnutls30 (>= 3.7.5) but it is not installable > libcurl3-gnutls : Depends: libgnutls30 (>= 3.7.5) but it is not installable >Depends: libnettle8 but it is not installable > libgnutls-openssl27 : Depends: libgnutls30 (= 3.7.9-2) but it is not > installable > libnm0 : Depends: libgnutls30 (>= 3.7.2) but it is not installable > libopenconnect5 : Depends: libgnutls30 (>= 3.7.5) but it is not installable >Depends: libhogweed6 but it is not installable > libvte-2.91-0 : Depends: libgnutls30 (>= 3.7.2) but it is not installable > network-manager : Depends: libgnutls30 (>= 3.7.2) but it is not installable > ntfs-3g : Depends: libgnutls30 (>= 3.7.2) but it is not installable > python3-samba : Depends: libgnutls30 (>= 3.7.0) but it is not installable > samba : Depends: libgnutls30 (>= 3.7.0) but it is not installable > samba-common-bin : Depends: libgnutls30 (>= 3.7.0) but it is not installable > samba-dsdb-modules : Depends: libgnutls30 (>= 3.7.0) but it is not > installable > samba-libs : Depends: libgnutls30 (>= 3.7.5) but it is not installable > samba-vfs-modules : Depends: libgnutls30 (>= 3.7.0) but it is not installable > wget : Depends: libgnutls30 (>= 3.7.2) but it is not installable > Depends: libnettle8 but it is not installable > xfce4-mailwatch-plugin : Depends: libgnutls30 (>= 3.7.0) but it is > not installable > ``` What commands did you perform? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Performing dist-upgrade on powerpc and ppc64
Hello, On Sun, 2024-04-14 at 22:55 +0200, Riccardo Mottola wrote: > I supposed so, just asked for confirmation. I don't care much about the > motivations - I need it as a build dependency. I understand a minimal > build only python2 retained for some time (no more?). ArcticFox is not > the only app depending python2.7 generally, butperhaps in the Debian DB? > I know Firefox eventually migrated to py3, but it took a long time and > currently I don't have the resources to folow it - simply because I > don't know python and don't know what is needed. You can fetch the source from here: $ dget -u http://snapshot.debian.org/archive/debian/20220801T085926Z/pool/main/p/python2.7/python2.7_2.7.18-13.2.dsc Then build the package with sbuild: $ sbuild -d sid --arch-all --arch=powerpc python2.7_2.7.18-13.2.dsc Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Bug#1060196: fixed in ghc 9.4.7-5
On Fri, 2024-04-12 at 22:35 +, Debian FTP Masters wrote:
>* Build unregisterised on powerpc (Closes: #1060196)
I am not 100% sure what happened, but this upload produced another
broken GHC compiler on powerpc. Lots of packages fail to build now
due to GHC segfaulting [1]:
Running dh_listpackages
libghc-splitmix-dev
libghc-splitmix-prof
libghc-splitmix-doc
-e: error: debian/hlibrary.setup build --builddir=dist-ghc died with signal 11
at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 875.
Debian::Debhelper::Dh_Lib::error("debian/hlibrary.setup build
--builddir=dist-ghc died with sig"...) called at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 614
Debian::Debhelper::Dh_Lib::error_exitcode("debian/hlibrary.setup build
--builddir=dist-ghc") called at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm
line 477
Debian::Debhelper::Dh_Lib::doit("debian/hlibrary.setup", "build",
"--builddir=dist-ghc") called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 656
Debian::Debhelper::Buildsystem::Haskell::Recipes::build_recipe() called
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned
exit status 2
Adrian
> [1]
> https://buildd.debian.org/status/fetch.php?pkg=haskell-splitmix=powerpc=0.1.0.5-1%2Bb1=1713046430=0
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: PPC64 install && Firefox
On Mon, 2024-04-08 at 19:38 +1200, Mike Hosken wrote: > I used debian-12.0.0-ppc64-NETINST.iso with the date 2023-05-16. > I downloaded this from cdimage.debian.org. When I burned it to a > cd it didn’t boot. When I tried a dvd it did boot. I’m assuming > that it’s the latest image. There were 15 images released after that one: > https://cdimage.debian.org/cdimage/ports/snapshots/ Not sure why you thought it's the latest one. > I ended up doing 6 installations overall, for testing purposes and it worked > well. > > As for Firefox thanks for the info, hopefully it will get fixed as it would > make > ppc64 still very useable in this modern era. Well, someone interested in Firefox on big-endian targets would have to take a look at it. I currently don't have the time for it. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: PPC64 install && Firefox
Hello, On Mon, 2024-04-08 at 17:19 +1200, Mike Hosken wrote: > I just wanted to give some feedback on the install of ppc64 on a Mac G5. > > I had a few issues when installing the latest version. Which image did you use? The latest snapshot image is known to not boot on PowerMac G5, so I'm doubtful you were actually using the latest version. > Grub install fails when not installing standard system utilities through > tasksel during installation. I’m not sure if packages are required for ppc64 > grub install from standard system utilities but I thought I’d mention it. Without knowing what image was used, I cannot really comment here. > During installation, upgrading via ports archive dpkg throws up an error with > the start stop daemon not being able to write to the directory. After > installation > upon reboot dpkg is broken because of this. The fix was simple and upon > reinstall > dpkg works as expected. I have run into this issue during a test installation as well, but I have not figured out yet what the problem is. > I installed xfce and noticed Firefox failed to launch with segmentation > errors also > the esr version does the same. Upon further research I discovered others also > have > this problem. The Firefox issue is a known upstream bug: > https://bugzilla.mozilla.org/show_bug.cgi?id=1845669 > I tried building both versions from Sid but they both failed to build. Is > there a fix for this issue ? Both firefox and firefox-esr built successfully on ppc64 16 days ago: > https://buildd.debian.org/status/fetch.php?pkg=firefox=ppc64=124.0.1-1=1711164847=0 > https://buildd.debian.org/status/fetch.php?pkg=firefox=ppc64=124.0.1-1=1711164847=0 > I’d like to thank the maintainers for keeping the ports going on 20 year old > hardware. You're welcome. I'm glad my work is useful to others. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Performing dist-upgrade on powerpc and ppc64
Hello, On Thu, 2024-04-04 at 22:00 +0200, Riccardo Mottola wrote: > I miss python2.7 though. python2.7-minimal appears to be intact, but I > need more modules to compile ArcticFox. I suppose what I need is in > libpython2.7-stdlib, but this needs libtirpc3:powerpc which is a t64 > transitioning package. > > Is 2.7 gone for good or is it a temporary issue on PPC? Python 2.7 was removed from Debian unstable in December 2022 [1]. The motivations for the removal are explained in [2]. If still needed, the package can be rebuilt from the older sources against the current updated shared library t64 packages [3]. Adrian > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027108 > [2] https://wiki.debian.org/Python/2Removal > [3] http://snapshot.debian.org/package/python2.7/ -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Bug#1056428: /usr/sbin/lparstat: Could not open /proc/ppc64/lparcfg when lauch lparstat
Hello Thomas, On Wed, 2024-04-03 at 12:22 +, PEPONAS Thomas wrote: > On IBM Power paltform , add cpu entitlement can not be done without > LPARCFG=Y , because /proc/ppc64/lparcfg could not open: > Logs from drmgr : > ## Apr 03 10:54:41 2024 ## > drmgr: -c cpu -r -q 10 -p ent_capacity -w 5 -d 1 > Validating CPU DLPAR capability...yes. > Could not open "/proc/ppc64/lparcfg" > No such file or directory > CPU entitlement capability is not enabled on this platform. > Could not update system parameter ent_capacity > ## Apr 03 10:54:41 2024 ## > > will the LPARCFG option be activated on future versions? The Debian kernel maintainers are informed since I have reassigned the bug to the kernel package. I assume this will be fixed in the near future. I might do it myself if I find the time during the next weeks. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Performing dist-upgrade on powerpc and ppc64
Hello, On Wed, 2024-04-03 at 07:32 +0200, Christian Marillat wrote: > Could you upgrade qt6-multimedia with your patch from #1057050 ? Sure, I can do that. I'm a bit underwhelmed that the maintainer still hasn't managed to fix the problem in unstable. *bummer* Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Bug#1057050 closed by Debian FTP Masters (reply to Patrick Franz ) (Bug#1057050: fixed in qt6-multimedia 6.6.1-1)
Control: reopen -1 Hi, looks like this didn't work: > https://buildd.debian.org/status/fetch.php?pkg=qt6-multimedia=powerpc=6.4.2-11=1705003199=0 Reopening the bug therefore. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Performing dist-upgrade on powerpc and ppc64
Hi, for anyone wondering whether it would be safe now to dist-upgrade your Debian machines running the powerpc or ppc64 ports, here's a quick update on the current status. Performing a full two-staged dist-upgrade on ppc64 should be safe while an upgrade on powerpc is currently safe. If you're running powerpc on a desktop and use lightdm as the display manager, you should wait for #1067561 [1] to be fixed unless you are using gdm3 or sddm. Either way, upgrade should be performed from a virtual console outside X11 or Wayland. First run "apt update", then "apt upgrade" and make sure every package is updated without issues. Once that has passed, you may try to run "apt dist-upgrade" but before you confirm the dist-upgrade, make sure that nothing is purged you still need. In case of unexpected breakage, please report it to the debian-powerpc mailing list. Adrian > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067561 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Boot lockups on PowerMac G5 with installer images
Hello, just as a heads-up: We still don't know what the underlying problem of the lockup on PowerMac G5 systems is when trying to boot the latest installer images. All I know so far is that the problem can be reproduced on QEMU and the last working image is image created 2023-06-18: > https://cdimage.debian.org/cdimage/ports/snapshots/2023-06-18/debian-12.0.0-ppc64-NETINST-1.iso All newer images (snapshots) just hang after the kernel has been initialized. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Boot failure with ppc64 port on iMacs G5
Hi Michael, On Wed, 2024-03-06 at 12:57 +1100, Michael Ellerman wrote: > > Yep, the second, older image works as expected. However, the recent one > > does not > > and I have absolutely no clue why. > > I actually tested both, and both work, but then I cited the wrong one in > my email >_< > > So at least on qemu that newer kernel is OK: > > Preparing to boot Linux version 6.6.15-powerpc64 > (debian-ker...@lists.debian.org) (gcc-13 (Debian 13.2.0-13) 13.2.0, GNU ld > (GNU Binutils for Debian) 2.42) #1 SMP Debian 6.6.15-2 (2024-02-04) > ... > Booting Linux via __start() @ 0x0480 ... > Hello World ! > smp_core99_probe > smp_core99_bringup_done > Starting system log daemon: syslogd, klogd. Did you get around testing the images on real hardware? And can tell me what command line you used for booting with QEMU? Maybe that gives us a clue where the problem is. Users are still reporting boot lockups with kernel 6.6.x. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Install failure debian-12.0.0ppc64-NETINST-1.iso on G5 Power Mac
Hi, please use one of the older ISO images from the snapshot folder on the server. There is currently a known regression with the latest images that I have not been able to resolve yet. I think this image should work: > http://cdimage.debian.org/cdimage/ports/snapshots/2023-06-18/debian-12.0.0-ppc64-NETINST-1.iso I‘ll verify that tomorrow as it’s already late here. Adrian > On Mar 27, 2024, at 10:12 PM, AurelianStoicist > wrote: > > > U P D A T E to previous mail from Mar 25, 2024 > > I have finally managed to get the CD to be recognized via resetting Open > Firmware as follows: > > Upon system boot into Open FIrmware (simply holding power button though long > beep and opening chime for another 10 seconds), I changed the setting for > boot-load as follows: > > 1) setenv auto-boot? false > 2) printenv auto-boot? > 3) dev / ls.—> searching for address of the system ATA optical drive > 4) dev /ht/pci@3/ata-6@d/disk > 5) devalias ud /ht/pci@3/ata-6@d ls > 6) setenv boot-device ud:,\\:tbxi > 7) printenv boot-drive > 8) mac-boot > > Upon boot, the system comes up with the menu to install debian > typed yes to auto-install during install instance 1 and > typed yes to default install during install instance 2 > the following screen image comes up (system is frozen) > > <2024-03-27 13.51.31.jpg> > > > What am I missing/ doing incorrectly? > > Still hoping to load Debian 12 on my G5 Power Mac to a) properly learn Linux > and b) increase productivity. > Any assistance would be greatly appreciated… > > Thank you very much > Thomas Mueller > Hendersonville, NC > > > > > > > > > > > > Hello JPA Glaubitz, > > first of all thank you for your dedicated work in dealing with the problems > of loading Debian 12 onto the old Mac G5 Power PC machine infrastructure. > > I recently tried to install your latest iso debian-12.0.0-ppc64-NETINST-1.iso > onto my Dual 1.8GhZ G5 Power PC. After burning the iso file to a new R/W CD > and inserting it into the optical drive, the iso file on the CD was not > recognized, regardless if I held down Option/ Alt during boot-up or the > C-key. I have no idea if my system’s boot-loader utilizes Legacy or EUFI, but > every time I utilized the CD with the burned iso file, the system started up > from the regular HD. > > No idea where to go from here, as my system does not respond like Retro > Action’s Youtube video install. I simply do not get any boot option on my > screen... > > Any ideas? > > > Vielen Dank und viele liebe Grüsse aus den USA > > Thomas Mueller > > Aurelian Stoicist > A.S. > <2024-03-27 13.51.31.jpg> >
Bug#1067735: www.debian.org: Please update links for PowerPC CHRP port
Package: www.debian.org Severity: normal User: debian-powerpc@lists.debian.org Usertags: powerpc X-Debbugs-Cc: debian-powerpc@lists.debian.org Hello, the following page for the PowerPC CHRP has some dead links: > https://www.debian.org/ports/powerpc/inst/chrp These links can be updated to point to archive.debian.org: linux.bin: http://archive.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/linux.bin rescue.bin: http://archive.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/images-1.44/rescue.bin driver-1.bin: http://archive.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/images-1.44/driver-1.bin driver-2.bin: http://archive.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/images-1.44/driver-2.bin basedebs.tar: http://archive.debian.org/debian/dists/woody/main/disks-powerpc/base-images-current/basedebs.tar CHRP System from Geert Uytterhoeven: https://web.archive.org/web/20140625035302/http://users.telenet.be/geertu/Linux/PPC/ In the long term, it might be a good idea to move the documentation for old architectures to Debian Ports. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Install problems on 43p-150 RS/6000
Hi Bill, On Mon, 2024-03-25 at 21:08 -0400, Bill deWindt wrote: > Please bear with me as this is my first post the powerpc group, but I am > pretty sure I am in the right place for this. :) You are. > After recently purchasing a NOS Sparc Ultra 5 and having great success > getting Sid running on it after much work and reading on > linux.debian.ports.sparc I decided to try and get Debian running on the > RS/6000 43p-150 machine I have in my collection. I originally purchased > the machine from a hospital back in 2008 or 09 for $20 and after a great > deal of sweat and tears I managed to get openSUSE 10.3 ppc running on > it. It has been like that since 2010 and I haven't use it since about > 2012, but if I could get Debian running on it I might have a use for it. > So, after doing the usual Googling and reading everything I could find > about this machine and why I had such trouble getting anything other > than AIX and openSUSE running on it I find myself here asking for any > assistance or guidance. So let me start with what I have tried to date > and what the results were (some are virtually identical to posts I found > from the early 2000's but I hoped some things had changed since then...) I can't go into the details right now due to lack of time, but you should first check whether your machine is still supported by the Linux kernel. I know that IBM engineers dropped support for many of their own PowerPC machines in the Linux kernel unlike Apple PowerMacs, so chances might be that your machine is no longer supported and you would have to stick to an older kernel. Your 43-P150 system is listed here: > https://www.debian.org/ports/powerpc/inst/install Apparently, there were custom installation floppy disks for this machine. Since the link above 404s, you have to download them from the archive server: > http://archive.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/ The page also links to a 404 page by Geert Uytterhoven who apparently once had such a system: > https://web.archive.org/web/20140625035302/http://users.telenet.be/geertu/Linux/PPC/ I'm CC'ing him since he might be able to give you some hints. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: git disappeared - dependencies broken
Hello, On Mon, 2024-03-25 at 16:15 +0100, Riccardo Mottola wrote: > > > https://lists.debian.org/debian-devel-announce/2024/02/msg0.html > > > https://wiki.debian.org/ReleaseGoals/64bit-time > > So since February 2 we are still broken enough that GIT is broken :( Well, no. Git itself is broken: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066794 > > As a result, you have run into this: > > > > > https://lists.debian.org/debian-sparc/2017/12/msg00060.html > > yes apparently is. I still think apt-get is being not very smart here, > even if the problem is "cruft". It shouldn't remove arbitrarily remove.. > Maybe I shall use aptitude next time. APT will only remove on "dist-upgrade", not on "upgrade". Hence, you should always run "upgrade" first and only run "dist-upgrade" after checking what would get removed. Don't just run blindly "apt-get update && apt-get -y dist-upgrade"! > Is it of any use to track libcurl3-gnutls or are you already perfectly > aware that the package is missing from the build system? src:curl is just one of the many packages that changed their API due to the time_t transition. Debian Developers are aware of all the breakage. FWIW, you actually will have to purge a lot of packages during dist-upgrade as library packages get replaced by their "t64" variants. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: git disappeared - dependencies broken
Hello, On Mon, 2024-03-25 at 13:17 +0100, Riccardo Mottola wrote: > To be honest, dist-upgrade wanted to change a lot of packages, so I did > not dig in the detail of each one being removed, but I thought that it > should preserve packages and in case hold-back packages with broken > dependencies? Debian unstable is currently undergoing a massive transition to switch 32-bit architectures to 64-bit time_t as announced last month: > https://lists.debian.org/debian-devel-announce/2024/02/msg0.html > https://wiki.debian.org/ReleaseGoals/64bit-time As a result, you have run into this: > https://lists.debian.org/debian-sparc/2017/12/msg00060.html Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: bug#65978: comp-tests-ret-type-spec-71 fails on 32-bit powerpc
Hi, On Thu, 2024-03-21 at 11:39 +0100, John Paul Adrian Glaubitz wrote: > On Thu, 2024-03-21 at 12:21 +0200, Eli Zaretskii wrote: > > > Cc: debian-powerpc@lists.debian.org, 65...@debbugs.gnu.org > > > Date: Thu, 14 Mar 2024 10:28:22 +0200 > > > From: Eli Zaretskii > > > > > > > Cc: debian-powerpc , > > > > 65...@debbugs.gnu.org > > > > From: Andrea Corallo > > > > Date: Thu, 07 Mar 2024 13:42:38 -0500 > > > > > > > > John Paul Adrian Glaubitz writes: > > > > > > > > Hi John, > > > > > > > > I *think* this should be fixed. Could you verify and let us know if you > > > > still see the issue? > > > > > > Ping! John, could you please verify the fix? > > > > Ping! Ping! > > Sorry, I will give it another try today. > > I am currently swamped in work due to Debian's time_t transition and > additional tasks at my day job. All tests pass for me on git master, so I assume the bug has been fixed. I'm not 100% sure how to run the testsuite in the same way as the Debian package though. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: bug#65978: comp-tests-ret-type-spec-71 fails on 32-bit powerpc
Hi Eli, On Thu, 2024-03-21 at 12:21 +0200, Eli Zaretskii wrote: > > Cc: debian-powerpc@lists.debian.org, 65...@debbugs.gnu.org > > Date: Thu, 14 Mar 2024 10:28:22 +0200 > > From: Eli Zaretskii > > > > > Cc: debian-powerpc , > > > 65...@debbugs.gnu.org > > > From: Andrea Corallo > > > Date: Thu, 07 Mar 2024 13:42:38 -0500 > > > > > > John Paul Adrian Glaubitz writes: > > > > > > Hi John, > > > > > > I *think* this should be fixed. Could you verify and let us know if you > > > still see the issue? > > > > Ping! John, could you please verify the fix? > > Ping! Ping! Sorry, I will give it another try today. I am currently swamped in work due to Debian's time_t transition and additional tasks at my day job. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Issues today with PowerPC
On Tue, 2024-03-19 at 02:25 -0600, Eric Ramsey wrote: > Honestly, it was people saying sid in general as mostly working. There > is not much information specifically for PowerPC which is why I > reached out here. The transition is being performed in unstable/sid, so naturally all of unstable is affected. However, there is one caveat which is whether an architecture is subject to an ABI change or not. Subject to an ABI change are all 32-bit archi- tectures in unstable except for i386 where the current ABI is kept so old binaries will be able to run in the future. All other 32-bit architectures are subject to an ABI breakage and are in the middle of a major archive rebuild which isn't done over night. See this page on the Debian wiki for more information: > https://wiki.debian.org/ReleaseGoals/64bit-time > The good news is I was able to recover the system from the odd state I > accidentally got it into using the snapshot service. > So even though I am on an older version I will wait on upgrades until > things are fine. I am not worried about it being old so there is no > real rush. Just took me by surprise, especially the inadvertent nuke > that I am still not sure how I pulled off. The start of the transition was officially announced at the beginning of February: > https://lists.debian.org/debian-devel-announce/2024/02/msg0.html > Speaking of the snapshot service, does debian-ports need hosting space > for the debian-ports snapshots? It stopped last year and I have not > investigated why yet in the mailing list. This is due to hardware issues, no idea what the current progress is: > https://lists.debian.org/debian-devel/2023/08/msg00014.html If you have the possibly to help, please reach out to the people in charge. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Issues today with PowerPC
On Mon, 2024-03-18 at 17:59 -0600, Eric Ramsey wrote: > So I found some information on the t64 transition. However, what I am > finding is that it should still work. So I am not sure if something > went sideways in the PowerPC tree or not. We're in the middle of the time64_t transition and powerpc is a pure unstable distribution target which means it's fully affected by this transition. Not sure what you read which told you everything would still work when the transition isn't over yet. There is still a lot of work to be done and since I'm currently sick, I cannot do much myself. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1066995: pulseaudio: FTBFS with _TIME_BITS=64 on 32-bit systems
Source: pulseaudio Version: 16.1+dfsg1-3 Severity: serious Tags: upstream Justification: ftbfs User: debian-powerpc@lists.debian.org Usertags: powerpc X-Debbugs-Cc: debian-powerpc@lists.debian.org Hi, pulseaudio fails to built from source with _TIME_BITS=64 [1]: [632/648] cc -Isrc/utils/libpulsedsp.so.p -Isrc/utils -I../src/utils -I. -I.. -Isrc -I../src -fdiagnostics-color=always -Wall -Winvalid-pch -std=gnu11 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -DHAVE_CONFIG_H -D_GNU_SOURCE -Wno-nonnull-compare -MD -MQ src/utils/libpulsedsp.so.p/padsp.c.o -MF src/utils/libpulsedsp.so.p/padsp.c.o.d -o src/utils/libpulsedsp.so.p/padsp.c.o -c ../src/utils/padsp.c FAILED: src/utils/libpulsedsp.so.p/padsp.c.o cc -Isrc/utils/libpulsedsp.so.p -Isrc/utils -I../src/utils -I. -I.. -Isrc -I../src -fdiagnostics-color=always -Wall -Winvalid-pch -std=gnu11 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -DHAVE_CONFIG_H -D_GNU_SOURCE -Wno-nonnull-compare -MD -MQ src/utils/libpulsedsp.so.p/padsp.c.o -MF src/utils/libpulsedsp.so.p/padsp.c.o.d -o src/utils/libpulsedsp.so.p/padsp.c.o -c ../src/utils/padsp.c In file included from /usr/include/features.h:393, from /usr/include/endian.h:21, from /usr/include/linux/soundcard.h:43, from /usr/include/powerpc-linux-gnu/sys/soundcard.h:1, from ../src/utils/padsp.c:33: /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" 26 | # error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64" | ^ This needs to be fixed for the time_t transition [2]. Thanks, Adrian > [1] > https://buildd.debian.org/status/fetch.php?pkg=pulseaudio=powerpc=16.1%2Bdfsg1-3%2Bb1=1710500596=0 > [2] https://wiki.debian.org/ReleaseGoals/64bit-time -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 # This file is part of PulseAudio. # # PulseAudio is free software; you can redistribute it and/or modify # it under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # PulseAudio is distributed in the hope that it will be useful, but # WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU # General Public License for more details. # # You should have received a copy of the GNU Lesser General Public License # along with PulseAudio; if not, see <http://www.gnu.org/licenses/>. ## Configuration file for PulseAudio clients. See pulse-client.conf(5) for ## more information. Default values are commented out. Use either ; or # for ## commenting. ; default-sink = ; default-source = ; default-server = ; default-dbus-server = ; autospawn = yes ; daemon-binary = /usr/bin/pulseaudio ; extra-arguments = --log-target=syslog ; cookie-file = ; enable-shm = yes ; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 MiB ; auto-connect-localhost = no ; auto-connect-display = no # This file is part of PulseAudio. # # PulseAudio is free software; you can redistribute it and/or modify # it under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # PulseAudio is distributed in the hope that it will be useful, but # WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU # General Public License for more details. # # You should have received a copy of the GNU Lesser General Public License # along with PulseAudio; if not, see <http://www.gnu.org/licenses/>. ## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for ## more information. Default values are commented out. Use either ; or # for ## commenting. ; daemonize = no ; fail = yes ; allow-module-loading = yes ; allow-exit = yes ; use-pid-file = yes ; system-instance = no ; local-server-type = user ; enable-shm = yes ; enable-memfd = yes ; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 MiB ; lock-memory = no ; cpu-limit = no ; high-priority = yes ; nice-level = -11 ; realtime-scheduling = yes ; realtime-priority = 5 ; exit-idle-time = 20 ; scache-idle-time = 20 ; dl-search-path = (depends on architecture) ; load-default-script-file = yes ; default-scr
Re: Boot failure with ppc64 port on iMacs G5
Hi Michael, On Fri, 2024-03-01 at 12:56 +1100, Michael Ellerman wrote: > OK. > > That second iso boots OK for me in qemu. It boots grub and then the > kernel loads and shows: > > Loading ... > OF stdout device is: /pci@f000/mac-io@c/escc@13000/ch-a@13020 > Preparing to boot Linux version 6.3.0-1-powerpc64 > (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.3.0-2) 12.3.0, GNU ld > (GNU Binutils for Debian) 2.40) #1 SMP Debian 6.3.7-1 (2023-06-12) > Detected machine type: 0400 > command line: BOOT_IMAGE=/install/vmlinux --- quiet > memory layout at init: > memory_limit : (16 MB aligned) > alloc_bottom : 05e7 > alloc_top: 3000 > alloc_top_hi : 8000 > rmo_top : 3000 > ram_top : 8000 > copying OF device tree... > Building dt strings... > Building dt structure... > Device tree strings 0x05e8 -> 0x05e80560 > Device tree struct 0x05e9 -> 0x05ea > Quiescing Open Firmware ... > Booting Linux via __start() @ 0x0200 ... > Hello World ! > smp_core99_probe > smp_core99_bringup_done > Starting system log daemon: syslogd, klogd. > > And eventually starts the installer. Yep, the second, older image works as expected. However, the recent one does not and I have absolutely no clue why. > That's using no VGA, so possibly there's something wrong with the video > setup on real hardware: > > $ qemu-system-ppc64 -nographic -vga none -M mac99,via=pmu -smp 1 -m 2G -nic > user -drive > file=$HOME/debian-12.0.0-ppc64-NETINST-1.2023-06-18.iso,format=raw,media=cdrom > -boot d > > I'll try and find time to test it on my actual G5 next week when I'm in > the office. The video issue can usually be worked around by disabling mode-setting or passing other kernel options related to the video card. That's not the main problem here though. The problem is that the newer image doesn't boot and currently I don't know why because installing the exact same kernel later from the package manager into an installed system works yields a bootable system with the latest kernel. The installer images are built from the same kernel package which makes the whole thing even more confusing. I'm using debian-cd to build the installation images: > https://salsa.debian.org/images-team/debian-cd/ Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Boot failure with ppc64 port on iMacs G5
Hi Michael, On Thu, 2024-02-29 at 17:42 +1100, Michael Ellerman wrote: > > There seems to be a regression in the kernel which affects PowerPC 970 > > machines, > > i.e. PowerMac G5 CPUs. The issue needs to be bisected and reported upstream. > > I have a quad G5 that is booting mainline happily. it's a really tricky problem because it seems to depend on how the kernel image is booted. It fails when trying to boot the kernel off the installation CD, i.e. like from here: > https://cdimage.debian.org/cdimage/ports/snapshots/2024-02-25/debian-12.0.0-ppc64-NETINST-1.iso but the kernel will boot fine when installing in an existing system which was installed with an installation CD which uses an older kernel. > https://cdimage.debian.org/cdimage/ports/snapshots/2023-06-18/debian-12.0.0-ppc64-NETINST-1.iso I have not really figured out yet what the problem is. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Boot issues with debian-installer on ppc64
Hi, On Wed, 2024-02-28 at 09:13 +0100, John Paul Adrian Glaubitz wrote: > The interesting bit is the kernel in question works fine when installing it > later instead of booting > from CD, so it might not be a kernel issue after all. However, I can no clue > yet what may have changed > in either debian-installer or debian-cd to break the installation CD. > > I will need to perform more debugging. I just had another idea for testing which is building a current installation image with an old, known to work kernel. This will help verify whether it's actually an issue with the kernel or the CD building process or the boot loader on the CD. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Boot issues with debian-installer on ppc64
Hi Richard, On Tue, 2024-02-27 at 22:51 -0600, Richard Allen wrote: > I tried these on my Dual-processor PCI-X G5. > > > https://cdimage.debian.org/cdimage/ports/tests/ppc64-test/debian-12.0.0-ppc64-NETINST-1.iso > > https://cdimage.debian.org/cdimage/ports/tests/ppc64-test-new/debian-12.0.0-ppc64-NETINST-1.iso > > Both behaved the same way. Got to the installer menu, I choose an install > mode, > showed "loading..." for approximately 1 minute bit, then showed normal > messages like > 'Quiescing OpenFirmware...' and 'Booting Linux via __start()', and within 1 > second Linux printed: > > smp_core99_probe > smp_core99_kick_cpu > smp_core99_kick_cpu_done > smp_core99_bringup_done > > but after that nothing more. After 1-2 minutes the fans spun up fully. After > 3-5 minute I gave > up and held power button to power down. > > > https://cdimage.debian.org/cdimage/ports/snapshots/2024-02-25/ > > This one got to the four smp_core99_* messages, but the fans did not spin up. > I waited 12 minutes > but the screen did not update. Thanks for the confirmation. So my tests with QEMU accurately emulate the behavior of a real G5 which means I can debug the problem much easier. The interesting bit is the kernel in question works fine when installing it later instead of booting from CD, so it might not be a kernel issue after all. However, I can no clue yet what may have changed in either debian-installer or debian-cd to break the installation CD. I will need to perform more debugging. > Is there anything I can help to diagnose from my end? Not at the moment. I need to perform more tests to figure out what went wrong. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Boot issues with debian-installer on ppc64
Hello, I have done some debugging on ppc64 to find out why the the kernel no longer boots on PowerPC G5 (PowerPC 970) systems. It turns out that the issue is much more complicated than I expected since the same kernel that doesn't boot debian-installer boots perfectly fine when installed after installation. I used QEMU for testing using the 970 CPU type (-cpu 970) and Mac99 machine type (-M mac99). I used a 32-bit system (powerpc) and installed a 64-bit kernel which works both fine with the 6.6.15 and 6.7 kernels. The same kernels don't work when used to boot debian-installer, I created test images here: > https://cdimage.debian.org/cdimage/ports/tests/ppc64-test/debian-12.0.0-ppc64-NETINST-1.iso > https://cdimage.debian.org/cdimage/ports/tests/ppc64-test-new/debian-12.0.0-ppc64-NETINST-1.iso There is also an updated debian-installer image for ppc64 with the 6.6.15 kernel: > https://cdimage.debian.org/cdimage/ports/snapshots/2024-02-25/ Would be great if anyone on this list with a PowerMac G5 ready for testing could check whether any of the images above boot on their machine. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Boot failure with ppc64 port on iMacs G5
Hello, On Tue, 2024-02-20 at 04:16 +0100, tuxayo wrote: > I tried snapshots/2024-01-31/debian-12.0.0-ppc64-NETINST-1.iso > > And was able to start booting from usb with: > boot usb0/disk@1:,\boot\grub\powerpc.elf > (typed in Open Firmware shell) > (usb0 is the top port) > > Grub worked, and then I tried default install (the 1st option) and it > started loading during like 2 minutes. > And then it got stuck with some superposition of the messages > smp_core99_probe > and > the stuff before > DO-QUIESCE finisedBooting Linux via __start() @ 0x0209 ... There seems to be a regression in the kernel which affects PowerPC 970 machines, i.e. PowerMac G5 CPUs. The issue needs to be bisected and reported upstream. If you have the time, I would really appreciate if you could test the various snapshots and let me know which kernel is the first to not work. I expect that the breakage occurred somewhere around kernel 6.3 or so. CC'ing Claudia Neumann who observed this bug before and can maybe share some additional information. > Full message of the two iMacs G5 ↓↓↓ > https://transfert.facil.services/r/Ksfq_2VM9_#tDATBcLXzB0zkAEaiqm9gfLfsaXliVJ13rQxKUHgUmA= > https://transfert.facil.services/r/Zs1h1jEtb2#jufjxv6+1DfHnO3TSfhmYD+teOvY46sGClHyz7SiXd4= Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: How to upgrade Debian 8 stable to the unofficial port (iMac G5)
Hello, On Tue, 2024-02-13 at 08:20 +0100, tuxayo wrote: > I installed the last offcial Debian 8 iso. Picking "install" and not > "install32" IIUC I have a ppc64 install. No, you still have a 32-bit PowerPC, i.e. powerpc installation. It's just that your kernel is 64 bits instead of 32 bits. > ppc64 seems the most relevant choice for a G5 to gain some performance > and to have any chance of having a full browser running on that > hardware. From the emails in the past months, I see it will likely crash > but there is hope that it might work at some point. > Still better than Firefox 52 on the powerpc port. (segfaults every 2 min > on Debian 8) > > How to upgrade from Debian 8? > Should I just change my source list to adapt the right part to point there?: > http://ftp.ports.debian.org/debian-ports/pool-ppc64 > there is also > http://ftp.debian.org/debian-ports/pool-ppc64/main/f/firefox/ > any preference? > > And then just > apt update && apt full-upgrade && apt autoremove I'm afraid that's not trivially possible although not impossible. However, crossgrading a 32-bit system to a 64-bit system requires a lot of knowledge as there are a lot of pitfalls and I would advise against it. > I'll also try to install debian-12.0.0-ppc64-NETINST-1.iso > But the past I tried debian-12.0.0-powerpc-NETINST-1.iso (because I > though ppc64 was ppc64el) > And it failed to boot: > Invalid memory access at > #SRR0: .020837dc #SRR1: 1000.00083030 Please try this image: > https://cdimage.debian.org/cdimage/ports/snapshots/2024-01-31/debian-12.0.0-ppc64-NETINST-1.iso Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Debian 12 on iMac G5
Hello Claudia, On Wed, 2024-02-07 at 20:19 +0100, Claudia Neumann wrote: > Now firmware R300_cp.bin, b43 and isight.fw is missing. Use this sources.list [1] and then install "firmware-amd-graphics". For the iSight camera, you can just download this file [2] and place it below /lib/firmware. For the b43 firmware, you need to install the b43-installer along with the b43-fwcutter. The latter is currently not built for ppc64, but I can do that manually later this week. Adrian > [1] https://people.debian.org/~glaubitz/sources.list > [2] https://github.com/ibvk/config/blob/master/bin/isight.fw -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: No video signal on iBook G4 with latest kernel
Hello, On Wed, 2024-01-24 at 16:15 +0100, Riccardo Mottola wrote: > > I have reported the issue in the Freedesktop bug tracker for the radeon > > driver [1]. > > video signal of the internal LCD or external video? When does this happen > I just updated my iBook G4 14" and it works. Boot messages, console and > X11 (but read below). As mentioned in the bug report, it's the internal connector, i.e. the LCD. > What happens is that perhaps you see the kernel booting, but then loose > the "login" and have a black screen (but you can type blindly?) > That happens here. I need to brighten the LCD several times until I see > something, it looks like the brightness is not correctly sync'd. > But this has been happening since a long time, it is not the latest kernel. Correct, there is an issue with the brightness controls. It sometimes randomly turns the screen off, even when turning it to maximum setting. Then when you change the settings again randomly, the video comes back. Still, this needs to be bisected. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Mate Desktop crashes
Hello, On Tue, 2024-01-23 at 14:24 -0700, Stan Johnson wrote: > On my PowerMac G5, I had to replace a failed Radeon card with a low-end > Nvidia card, and I was no longer able to test Debian powerpc64 kernels > because the kernel was missing the needed CONFIG options: > > *** Aug 31, 2023 kernel (doesn't work on my G5) *** > > $ fgrep -i nvidia config-6.4.0-4-powerpc64 > CONFIG_NET_VENDOR_NVIDIA=y > # CONFIG_I2C_NVIDIA_GPU is not set > # NVidia media platform drivers > > *** Dec 22, 2023 (also doesn't work) *** > > $ fgrep -i nvidia config-6.6.8-powerpc64 > CONFIG_NET_VENDOR_NVIDIA=y > # CONFIG_I2C_NVIDIA_GPU is not set > # NVidia media platform drivers > # CONFIG_HID_NVIDIA_SHIELD is not set > > Compiling a custom kernel with the following CONFIG options works: > > $ fgrep -i nvidia config-6.5.1-ppc64 > # CONFIG_NET_VENDOR_NVIDIA is not set > # CONFIG_I2C_NVIDIA_GPU is not set > CONFIG_FB_NVIDIA=y > CONFIG_FB_NVIDIA_I2C=y > # CONFIG_FB_NVIDIA_DEBUG is not set > CONFIG_FB_NVIDIA_BACKLIGHT=y > > $ dmesg | grep -i nvidia > [0.264634] nvidiafb: Device ID: 10de0321 > [0.264666] nvidiafb :f0:10.0: vgaarb: deactivate vga console > [0.285134] nvidiafb: CRTC0 analog not found > [0.309133] nvidiafb: CRTC1 analog found > [1.153130] nvidiafb: EDID found from BUS2 > [1.153154] nvidiafb: CRTC 1 appears to have a CRT attached > [1.153162] nvidiafb: Using CRT on CRTC 1 > [1.157999] nvidiafb: PCI nVidia NV32 framebuffer (64MB @ 0x9800) That's the obsolete framebuffer driver though and not the nouveau DRM driver. I'm not sure how long framebuffer drivers will be continue to be available in the kernel, as far as I know they're slated for removal. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Mate Desktop crashes
Hello Christoph, On Tue, 2024-01-23 at 21:21 +0100, Christoph wrote: > here the log files for Xorg.0.log, .xsession-errors and dmesg command. There > seem to be a lot of errors in it that indicate a bug with the nouveau driver. Looking at the output of "dmesg", this actually indicates problems with the nouveau kernel module: [ 27.578040] nouveau :0a:00.0: gr: intr 0010 [ERROR] nsource 0002 [DATA_ERROR] nstatus 0200 [BAD_ARGUMENT] ch 0 [000c1030 (udev-worker)[171]] subc 4 class 0039 mthd 0314 data 0001 [ 27.578078] nouveau :0a:00.0: gr: intr 0010 [ERROR] nsource 0002 [DATA_ERROR] nstatus 0200 [BAD_ARGUMENT] ch 0 [000c1030 (udev-worker)[171]] subc 4 class 0039 mthd 0318 data 0001 [ 27.745010] nouveau :0a:00.0: gr: intr 0010 [ERROR] nsource 0002 [DATA_ERROR] nstatus 0200 [BAD_ARGUMENT] ch 0 [000c1030 (udev-worker)[171]] subc 4 class 0039 mthd 0314 data 0001 [ 27.745077] nouveau :0a:00.0: gr: intr 0010 [ERROR] nsource 0002 [DATA_ERROR] nstatus 0200 [BAD_ARGUMENT] ch 0 [000c1030 (udev-worker)[171]] subc 4 class 0039 mthd 0318 data 0001 As far as I know, nouveau is not well supported on big-endian systems. You can try reporting the bug here: https://gitlab.freedesktop.org/drm/nouveau/-/issues If you have the possibility, I would recommend replacing the graphics card with a Radeon-based chip which is much better supported on big-endian systems. Also, this indicates that the the nouveau XOrg driver is not installed: [12.378] (II) LoadModule: "nouveau" [12.379] (WW) Warning, couldn't open module nouveau [12.379] (EE) Failed to load module "nouveau" (module does not exist, 0) You are using the modeset XOrg driver instead. So, try installing the package xserver-xorg-video-nouveau and see if that helps: # apt install xserver-xorg-video-nouveau > Unfortunately the system did not create any files and/or folders in /var/log > named syslog. You can try something like: # journalctl > all_logs.txt [1] However, that should not be necessary as we already know what's wrong. Adrian > [1] https://www.putorius.net/export-logs-to-a-file-with-journalctl.html -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Mate Desktop crashes
Hi Christoph, On Tue, 2024-01-23 at 18:19 +0100, Christoph wrote: > Hello, im actually running Debian 12 on a Powermac G5 Quad with a > Geforce 6600 with Mate Desktop. (I could only install this desktop > because the installations fails if i try another) I am using XFCE which works even fine on my iBook G4. > Suddenly it crashes randomly and most times some Text is shown as skin > colored blocks. > If i use the Desktop over RDP with XRDP everything is normal and nothing > crashes. > The system is still "usable" if you know how to use the command line by > pressing Ctrl +tab and F1 to F6 > (...) > I don't know if its a bug in Mate (seems not) or a bug in the driver or the > display manager. > I use the display manager that installs default with the Mate Desktop Please check the contents of /var/log/Xorg.0.log, /home/$(your username)/.xsession-errors and /var/log/syslog. Also, check the output of of the "dmesg" command. If you find anything that references "mate" such as "mate-session" with an error message, please post it here. The log file /var/log/Xorg.0.log is certainly most interesting, please post it here. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Debian 12 on iMac G5
Hello Claudia, On Tue, 2024-01-23 at 17:59 +0100, Claudia Neumann wrote: > I choose > debian-11.0.0-ppc64-NETINST-1.iso > from 14.5.2023. > > I can start the installation, partitioning has succeeded. > it installs busybox but hangs with: > package zstd is not available. There is a reference from another package. > The installation stopped. > > Any suggesttions? > > Should I choose another iso? I will create fresh images within the next hours. You can try these. I'll let you know once they are available. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Debian 12 on iMac G5
Hi Claudia, On Tue, 2024-01-23 at 15:39 +0100, Claudia Neumann wrote: > Hi all, hi Adrian, > > downloaded the image and burnt on DVD. Now the iMac starts from DVD but hangs > with: > smp_core99_probe > smp_core99_bringup_done > the ventilator is up high but nothing else happens. > > I have ATI Radeon X600 (Rev 380) 3E50 (PCIE) > > Any hints? If you have the time, please try any of the older images: > https://cdimage.debian.org/cdimage/ports/snapshots/ It might be a kernel bug in one of the recent kernel versions. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Debian 12 on iMac G5
Hi Claudia, On Tue, 2024-01-23 at 14:54 +0100, Claudia Neumann wrote: > I have an iMac G5, PowerMac 12,1 PPC970FX, Platform: PowerMac 12,1 MacRISC4 > Power Macinstosh, Memory 1GB+384MB. > > I had installed Ubuntu 16.04.7 LTS and it was running fine. Now I need newer > libc and so on. So I wanted to install Debian 12 or even Debian 13 on this > iMac. This is a computer running in big-endian mode, so you need to install a big-endian PowerPC distribution. > Is that possible? I tried > debian-12.4.0-ppc64el-netinst.iso > but the iMac does not start from the DVD. The ppc64el Debian port targets little-endian PowerPC, so it's not compatible with your Mac. > What can I do? Please use this installation image: > https://cdimage.debian.org/cdimage/ports/snapshots/2023-12-14/debian-12.0.0-ppc64-NETINST-1.iso Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: X-Windows on PPC in Debian SID
Hello Stan, > On Jan 22, 2024, at 4:25 PM, Stan Johnson wrote: > > Please see the last paragrraph of the message; it may provide a clue for > ppc (and probably ppc64). > > Mr. Simon McVittie seems to be saying that debian-devel isn't the right > place for these kinds of issues, since Debian 8 was the last supported > version of Debian for ppc. Perhaps the bug report he submitted will > address the problem. It’s not a powerpc-specific problem as he admits himself. The whole discussion about the powerpc port being unofficial is therefore moot. > Trying this on amd64, it appears that the problem you encountering is > probably that libelogind, elogind's partial replacement for libsystemd, > does not appear to provide all of the functions required by the current > versions of important packages like procps: procps currently requires > libsystemd0 (>= 254), and libelogind only provides a replacement for > version 252. I've reported this libelogind limitation as a bug in > elogind. Which proves my point. Adrian
No video signal on iBook G4 with latest kernel
Hello, just as a heads-up: I'm not getting a video signal with my iBook G4 with the latest kernel. dmesg shows error messages that seem to be related to the problem: [ 14.222735] radeon :00:10.0: [drm] bpp/depth value of 16/16 not supported [ 14.222774] radeon :00:10.0: [drm] bpp/depth value of 16/16 not supported [ 14.222780] radeon :00:10.0: [drm] No compatible format found I have reported the issue in the Freedesktop bug tracker for the radeon driver [1]. Adrian > [1] https://gitlab.freedesktop.org/drm/amd/-/issues/3120 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: X-Windows Issues on PPC G4 MDD
On Mon, 2024-01-22 at 09:00 +0100, John Paul Adrian Glaubitz wrote: > On Sun, 2024-01-21 at 11:27 +0100, John Paul Adrian Glaubitz wrote: > > FWIW, I will update my iBook G4 next week and check whether X.Org and co > > still work. > > I have performed a dist-upgrade and while everything works as expected, there > is a regression in the Radeon driver with kernel 6.6.13 which fails to find > a compatible video mode meaning that the screen remains blank: > > [ 14.222735] radeon :00:10.0: [drm] bpp/depth value of 16/16 not > supported > [ 14.222774] radeon :00:10.0: [drm] bpp/depth value of 16/16 not > supported > [ 14.222780] radeon :00:10.0: [drm] No compatible format found > > I'll report this upstream. See: https://gitlab.freedesktop.org/drm/amd/-/issues/3120 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: X-Windows Issues on PPC G4 MDD
Hello, On Sun, 2024-01-21 at 11:27 +0100, John Paul Adrian Glaubitz wrote: > FWIW, I will update my iBook G4 next week and check whether X.Org and co > still work. I have performed a dist-upgrade and while everything works as expected, there is a regression in the Radeon driver with kernel 6.6.13 which fails to find a compatible video mode meaning that the screen remains blank: [ 14.222735] radeon :00:10.0: [drm] bpp/depth value of 16/16 not supported [ 14.222774] radeon :00:10.0: [drm] bpp/depth value of 16/16 not supported [ 14.222780] radeon :00:10.0: [drm] No compatible format found I'll report this upstream. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: X-Windows Issues on PPC G4 MDD
Hi Stan, On Sat, 2024-01-20 at 12:43 -0700, Stan Johnson wrote: > I realize that systemd is Debian's default init system, and perhaps > X-Windows was always destined to eventually require systemd in Debian. > If that's what has happened, please let me know. I cannot answer that question, you would have to ask on debian-devel. This particular discussion is also not specific to PowerPC, every architecture would be affected by it. FWIW, I will update my iBook G4 next week and check whether X.Org and co still work. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: cmake ftbfs on ppc64el (and ppc64)
Control: tags -1 +patch
On Fri, 2024-01-12 at 01:31 +0100, John Paul Adrian Glaubitz wrote:
> This has now been tracked down to the libuv upstream change that introduced
> support
> for io_uring [1]. This regression is tracked now in a new issue for libuv [2].
The attached patch disables io_uring on ppc64 and ppc64el for the time being
until
the upstream issue has been resolved.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
From 3b6a1a14caeeeaf5510f2939a8e28ed9ba0ad968 Mon Sep 17 00:00:00 2001
From: Brad King
Date: Sat, 13 Jan 2024 06:04:01 -0500
Subject: [PATCH] linux: disable io_uring on ppc64 and ppc64le (#4285)
Since `io_uring` support was added, libuv's signal handler randomly
segfaults on ppc64 when interrupting `epoll_pwait`. Disable it
pending further investigation.
Issue: https://github.com/libuv/libuv/issues/4283
---
src/unix/linux.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/unix/linux.c b/src/unix/linux.c
index 3c1313e7..4164e90d 100644
--- a/src/unix/linux.c
+++ b/src/unix/linux.c
@@ -463,6 +463,9 @@ static int uv__use_io_uring(void) {
#elif defined(__arm__) && __SIZEOF_POINTER__ == 4
/* See https://github.com/libuv/libuv/issues/4158. */
return 0; /* All 32 bits kernels appear buggy. */
+#elif defined(__powerpc64__) || defined(__ppc64__)
+ /* See https://github.com/libuv/libuv/issues/4283. */
+ return 0; /* Random SIGSEGV in signal handler. */
#else
/* Ternary: unknown=0, yes=1, no=-1 */
static _Atomic int use_io_uring;
--
2.43.0
Re: cmake ftbfs on ppc64el (and ppc64)
Hello, On Thu, 2024-01-11 at 19:15 +0100, John Paul Adrian Glaubitz wrote: > This bug has also been reported for openSUSE [2] and Simon Lees at SUSE said > he > would be looking into it. In case he comes up with a solution, I will report > it > here. This has now been tracked down to the libuv upstream change that introduced support for io_uring [1]. This regression is tracked now in a new issue for libuv [2]. Adrian > [1] > https://github.com/libuv/libuv/commit/d2c31f429b87b476a7f1344d145dad4752a406d4 > [2] https://github.com/libuv/libuv/issues/4283 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: cmake ftbfs on ppc64el (and ppc64)
Hi Jeff, On Thu, 2024-01-11 at 13:25 -0500, Jeffrey Walton wrote: > > > It may be a good idea to give the CMake folks the first chance at the > fix. It does not look like it has been reported to them: > <https://gitlab.kitware.com/cmake/cmake/-/issues>. Searching with > 'ppc' and 'llvm' tags returned 0 hits: > <https://gitlab.kitware.com/cmake/cmake/-/issues/?sort=created_date=all=ppc=llvm>. > (Maybe I missed it in their bug tracker). It was actually reported upstream and this bug report also forwards to the corresponding issue [1]. However, cmake upstream does not consider it a bug on their side which is why they closed the bug. Adrian > [1] https://gitlab.kitware.com/cmake/cmake/-/issues/25500 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: cmake ftbfs on ppc64el (and ppc64)
Hello, the bug is definitely still present and I'm therefore not sure whether downgrading the priority to normal is justified. On ppc64, cmake still crashes regularly when configuring the LLVM build for example [1]: -- Looking for pow in m - found -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Looking for backtrace in execinfo Segmentation fault I have performed a local LLVM test build and obtained a backtrace with gdb which also indicates a crash in libuv: Program terminated with signal SIGSEGV, Segmentation fault. #0 0x in ?? () [Current thread is 1 (Thread 0x7fff811f6e60 (LWP 2635470))] (gdb) bt #0 0x in ?? () #1 #2 0x7fff82eee784 in __GI_epoll_pwait (epfd=4, events=0x7fffd3808cc8, maxevents=1024, timeout=-1, set=0x0) at ../sysdeps/unix/sysv/linux/epoll_pwait.c:40 #3 0x7fff83545238 in uv__io_poll (loop=0x10015e8edd0, timeout=-1) at ./src/unix/linux.c:1365 #4 0x7fff8352aa84 in uv_run (loop=0x10015e8edd0, mode=UV_RUN_ONCE) at ./src/unix/core.c:447 #5 0x000132669d8c in cmExecuteProcessCommand (args=..., status=...) at ./Source/cmExecuteProcessCommand.cxx:358 #6 0x000132561d38 in InvokeBuiltinCommand (status=..., args=..., command=@0x133045248: 0x1326682b0 , std::allocator >, std::allocator, std::allocator > > > const&, cmExecutionStatus&)>) at ./Source/cmState.cxx:420 #7 operator() (status=..., args=..., __closure=) at ./Source/cmState.cxx:430 #8 std::__invoke_impl&, cmExecutionStatus&)>&, const std::vector >&, cmExecutionStatus&> (__f=...) at /usr/include/c++/13/bits/invoke.h:61 #9 std::__invoke_r&, cmExecutionStatus&)>&, const std::vector >&, cmExecutionStatus&> (__fn=...) at /usr/include/c++/13/bits/invoke.h:114 #10 std::_Function_handler >&, cmExecutionStatus&), cmState::AddBuiltinCommand(const std::string&, BuiltinCommand):: >&, cmExecutionStatus&)> >::_M_invoke(const std::_Any_data &, const std::vector > &, cmExecutionStatus &) (__functor=..., __args#0=..., __args#1=...) at /usr/include/c++/13/bits/std_function.h:290 This bug has also been reported for openSUSE [2] and Simon Lees at SUSE said he would be looking into it. In case he comes up with a solution, I will report it here. Adrian > [1] > https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-17=ppc64=1%3A17.0.6-4%2Bb2=1704985815=0 > [2] https://bugzilla.suse.com/show_bug.cgi?id=1218365 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1051931: fixed in obs-studio 30.0.2+dfsg-2
Control: reopen -1 >* Add Unconditional B-D on luajit > (dropping support for ppc64el) > (Closes: #1051931) That doesn't really fix the original bug report as suggested. My suggestion was to disable lua scripting on architectures where libluajit-5.1-dev is not (yet available.) Can you implement the fix as proposed in the original report? Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1060196: ghc: Please build unregisterised compiler with --param ggc-min-expand=10 -O3 on powerpc
Source: ghc Version: 9.4.7-2 Severity: normal User: debian-powerpc@lists.debian.org Usertags: powerpc X-Debbugs-Cc: debian-powerpc@lists.debian.org Hello! Due to the current regression in the native code generator for PowerPC on 32-bit targets [1], GHC can only be built as an unregisterised compiler on the target. Thus, please configure GHC with --enable-unregisterised on powerpc. Also, since building an unregisterised GHC generates very large intermediate C sources, we additionally have to pass both "--param ggc-min-expand=10" and "-O3" to reduce the memory footprint and the size of the generated assembly code respectively [2]. Thus, please pass -optc--param -optcggc-min-expand=10 and -optc-O3 to the GHC build flags. With these changes, GHC should build successfully on powerpc. Thanks, Adrian > [1] https://gitlab.haskell.org/ghc/ghc/-/issues/23969 > [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108208 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Crowdfunding a small but important powerpc bugfix
Hello! On Tue, 2024-01-02 at 15:40 +0100, John Paul Adrian Glaubitz wrote: > If we're lucky, the original regression of the 32-bit PowerPC native codegen > backend > might already be fixed in newer versions of the GHC compiler [3], so that we > can switch > back from an unregisterised build to the faster, native build of GHC. We'll > see. The original bug in the NGC on 32-bit PowerPC still exists, I have updated the upstream bug report accordingly with the latest backtraces generated by the GHC compiler [1]. Have we agreed on some sort of funding mechanism to convince upstream to fix the bug? Adrian > [1] https://gitlab.haskell.org/ghc/ghc/-/issues/23969#note_541275 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Crowdfunding a small but important powerpc bugfix
Hello! On Wed, 2023-10-11 at 15:38 +0200, John Paul Adrian Glaubitz wrote: > There is a regression in the GHC Haskell Compiler [1] that I have been > investigating for several days. While I have been able to identify the > commit that introduced the regression, I have not been able to fix > that issue since I don't have the necessary Haskell knowledge to be able > to work on GHC. > > Since the broken GHC compiler currently blocks a lot of packages on 32-bit > PowerPC and the upstream developers don't seem to be too motivated at the > moment to fix the bug, I was wondering whether people here would be willing > to throw in some money to create a bounty on that particular bug to pay > a Haskell developer to fix it. We're starting with good news into the new year: I have been able to work around this bug and successfully built an unregisterised version of GHC 9.4.6 for powerpc. I have uploded ghc_9.4.6-1+powerpc this morning to "unreleased" and the buildds are now building all Haskell packages on powerpc that were out of date [1]. I was able to build an unregisterised compiler by setting the GCC optimization level to "O3". Building an unregisterised compiler on powerpc previously failed due to the generated C code being too large for the powerpc target [2]. The suggested CFLAGS by Segher in the comments of the GCC bug report did the trick. If we're lucky, the original regression of the 32-bit PowerPC native codegen backend might already be fixed in newer versions of the GHC compiler [3], so that we can switch back from an unregisterised build to the faster, native build of GHC. We'll see. Adrian > [1] https://buildd.debian.org/status/architecture.php?a=powerpc=sid > [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108208 > [3] https://gitlab.haskell.org/ghc/ghc/-/issues/23969 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Bug#1058740: gtk4,librsvg: big-endian support is at risk of being removed
Hello Simon! On Fri, 2023-12-15 at 11:35 +, Simon McVittie wrote: > gtk4 had a recent test failure regression on s390x and other big-endian > architectures like ppc64 (#1057782). I sent this upstream to > https://gitlab.gnome.org/GNOME/gtk/-/issues/6260 and proposed a patch in > https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/6653, but upstream is > reluctant to apply the patch because they think it is the wrong solution: > > > I would rather people fix the actual issue, which is the large table > > mapping GdkMemoryFormat to the corresponding GL format (and I bet the > > one for dmabufs is broken, too, but we don't have tests for that). Is there someone working on that? > librsvg also has long-standing unsolved endianness-related issues, most > likely in one of its dependencies (#1038447, which has affected bookworm > since September 2022). The fact that librsvg isn't fixing these issues is surprising to me. Back when the library was converted to Rust, I was raising concerns that this will reduce portability which was dismissed by the main author as unjustified. > The GNOME team does not have big-endian hardware where we can run manual > tests, so we do not know how much of an impact this has on practical > usability of GTK and librsvg on big-endian architectures: it's entirely > possible that they have always been misrendered or broken on big-endian, > but the bug was never reported because there were no users, and we > are only noticing this now as a result of wider test coverage being > introduced. There are both QEMU-based solutions available as well as big-endian machines in the GCC Compiler Farm [1]. There is also the OpenPOWER Openstack platform which has both little- and big-endian targets available [2]. So, I don't think the argument there is no way to test on big-endian targets is justified. > If porters are interested in having GTK and librsvg continue to be > available on big-endian, please work with upstream to get them to a point > where endianness-specific bugs can be taken seriously in the upstream > projects. I do not consider doing this downstream-only to be a solution. Looking at both Fedora [3] and openSUSE [4], tests aren't executed on s390x for these distributions either. > If endianness-specific issues become a blocker for the Debian release > process at some point in the future, then it is likely that I will have > to start the process of doing architecture-specific removals for these > packages and their reverse dependencies. For s390x this is likely to > have little user-visible effect, because I find it unlikely that there > are genuinely users running GUI applications on IBM mainframes, but for > -ports architectures this will probably be a larger regression. Well, removing librsvg will certainly disable quite large number of packages on s390x. Maybe someone should CC an engineer from IBM on the bug report and ask for help to fix the testsuite issues. Adrian > [1] https://portal.cfarm.net/machines/list/ > [2] https://osuosl.org/services/powerdev/request_hosting/ > [3] > https://src.fedoraproject.org/rpms/librsvg2/blob/rawhide/f/librsvg2.spec#_153 > [4] > https://build.opensuse.org/package/view_file/GNOME:Next/librsvg/librsvg.spec?expand=1 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Bug#1057050: qt6-multimedia: Please build with EIGEN_DONT_VECTORIZE on powerpc to fix FTBFS
Hi Christian! On Thu, 2023-12-07 at 08:09 +0100, Christian Marillat wrote: > > It's always safe to apply this patch. > > It is possible to see this bug fixed ? I have uploaded a patched version to unreleased for the time being. However, fixing this should be a no-brainer and wouldn't affect anything else. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Bug#1057050: qt6-multimedia: Please build with EIGEN_DONT_VECTORIZE on powerpc to fix FTBFS
Hi! On Sat, 2023-12-02 at 00:46 +0100, Patrick Franz wrote: > We're in the middle of packaging Qt 6.6 and I had not planned to do any > more 6.4.2 updates unless absolutely necessary. > > Do you know whether this patch will also work on Qt 6.6.1 ? Yes, absolutely. And since it only adds some powerpc-specific lines to debian/rules, there is nothing really that would need to be rebased when updating to a newer Qt version. It's always safe to apply this patch. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Two important open bugs on 32-bit PowerPC
Hello! Just as a heads-up, there are now two important open bugs on 32-bit PowerPC that need attention. First is the already mentioned regression in GHC: > https://gitlab.haskell.org/ghc/ghc/-/issues/23969 Second is a regression in LLVM: > https://github.com/llvm/llvm-project/issues/72279 I assume the best way to get these issues fixed would be to put a bounty on each. If anyone knows a good and working platform for that (Bountysource seems defunct at the moment), it would be great if we could create bounties to get these bugs fixed. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Grub failed
Hi Jeroen! On Wed, 2023-11-29 at 09:02 +0700, Jeroen Diederen wrote: > Apt setup for deb.debian.org/debian-ports failed because the key expired > (B523E5F3FC4E5F2C). This particular key is not expired, it expires 2024: glaubitz@z6:~> gpg --fingerprint B523E5F3FC4E5F2C pub rsa4096 2021-12-30 [SC] [expires: 2024-02-01] D0C9 87D7 BEC3 EDDF 8948 6CC2 B523 E5F3 FC4E 5F2C uid [ unknown] Debian Ports Archive Automatic Signing Key (2023) glaubitz@z6:~> Is your clock set incorrectly by any chance? > Grub installation failed for the same reason, hmount was not found, i.e. > hfsutils was not present in the chroot. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Grub failed
Hi Jeroen! On Wed, 2023-11-29 at 00:14 +0700, Jeroen Diederen wrote: > Good news! Hopefully you can now have a look at the faulty grub > installation within d-i. I can confirm that the image from [1] works for me and installed without any issues. Either you picked on of the images which are missing the hfsprogs and partman-hfs packages or there is something wrong with your environment. Did you install using default settings or did you change the partition layout by any chance? Adrian > [1] > https://cdimage.debian.org/cdimage/ports/snapshots/2022-03-24/debian-11.0.0-powerpc-NETINST-1.iso -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1057050: qt6-multimedia: Please build with EIGEN_DONT_VECTORIZE on powerpc to fix FTBFS
Source: qt6-multimedia Version: 6.4.2-11 Severity: normal User: debian-powerpc@lists.debian.org Usertags: powerpc X-Debbugs-Cc: debian-powerpc@lists.debian.org Hello! The package src:qt6-multimedia fails to build from source on powerpc since version 6.4.0-1 due to the use of some AltiVec instrisics that are not supported on 32-bit PowerPC: /usr/bin/c++ -DEIGEN_MPL2_ONLY -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS -DQT_NO_JAVA_STYLE_ITERATORS \ (...) In file included from /usr/include/eigen3/Eigen/Core:210, from /usr/include/eigen3/Eigen/Dense:1, from /<>/src/resonance-audio/../3rdparty/resonance-audio/platforms/common/utils.h:20, from /<>/src/3rdparty/resonance-audio/platforms/common/utils.cc:17: /usr/include/eigen3/Eigen/src/Core/arch/AltiVec/PacketMath.h: In function \ ‘Packet Eigen::internal::pblend(const Selector::size>&, const Packet&, const Packet&) [with Packet = __vector(2) double]’: /usr/include/eigen3/Eigen/src/Core/arch/AltiVec/PacketMath.h:2702:17: error: invalid parameter combination for AltiVec intrinsic ‘__builtin_vec_sel’ 2702 | return vec_sel(elsePacket, thenPacket, mask); | ^ This can be fixed by switching off vectorization in the »eigen« using the preprocessor macro EIGEN_DONT_VECTORIZE which can be defined on the cmake command line using the cmake variable COMPILE_DEFINITIONS: --- qt6-multimedia-6.4.2/debian/rules.orig 2023-07-26 17:52:13.0 +0200 +++ qt6-multimedia-6.4.2/debian/rules 2023-11-28 18:26:47.950137854 +0100 @@ -9,6 +9,10 @@ cmake_extra_args += -DQT_HOST_PATH=/usr endif +ifneq (,$(filter $(DEB_HOST_ARCH),powerpc)) + cmake_extra_args += -DCOMPILE_DEFINITIONS="EIGEN_DONT_VECTORIZE" +endif + %: dh $@ --with pkgkde_symbolshelper --buildsystem=cmake+ninja With the above change, cmake defines the preprocessor macro EIGEN_DONT_VECTORIZE and the build succeeds on powerpc. Could you apply this change for the next upload in order to fix the build on powerpc? Attaching a patch for a convenience. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 --- qt6-multimedia-6.4.2/debian/rules.orig 2023-07-26 17:52:13.0 +0200 +++ qt6-multimedia-6.4.2/debian/rules 2023-11-28 18:26:47.950137854 +0100 @@ -9,6 +9,10 @@ cmake_extra_args += -DQT_HOST_PATH=/usr endif +ifneq (,$(filter $(DEB_HOST_ARCH),powerpc)) + cmake_extra_args += -DCOMPILE_DEFINITIONS="EIGEN_DONT_VECTORIZE" +endif + %: dh $@ --with pkgkde_symbolshelper --buildsystem=cmake+ninja
Re: Grub failed
On Mon, 2023-11-27 at 14:17 +0100, John Paul Adrian Glaubitz wrote: > On Mon, 2023-11-27 at 20:02 +0700, Jeroen Diederen wrote: > > You have to be patient, it will take at least a minute. > > Nope, even after five minutes nothing. I assume a regression in QEMU. FWIW, older images such as [1] boot fine. Most likely an issue with the kernel in the latest image. Adrian > [1] > https://cdimage.debian.org/cdimage/ports/snapshots/2022-03-24/debian-11.0.0-powerpc-NETINST-1.iso -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Grub failed
On Mon, 2023-11-27 at 20:02 +0700, Jeroen Diederen wrote: > You have to be patient, it will take at least a minute. Nope, even after five minutes nothing. I assume a regression in QEMU. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Grub failed
Hello! On Mon, 2023-11-27 at 19:40 +0700, Jeroen Diederen wrote: > qemu-system-ppc \ >-L pc-bios \ >-boot d \ >-M mac99 \ >-m 2048 \ >-prom-env 'auto-boot?=true' \ >-prom-env 'boot-args=-v' \ >-drive file=debian-12.0.0-powerpc-NETINST-1.iso,format=raw,media=cdrom > \ >-drive file=debian12.qcow2,format=qcow2,media=disk \ >-net nic,model=sungem \ >-net user That's what I am using. However, it stops at "Booting Linux via __start()". > It will work, I did it many times before. It did work for me in the past as well. But not anymore, it seems. Might be a regression with QEMU 8.x. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Grub failed
Hello! On Mon, 2023-11-27 at 15:58 +0700, Jeroen Diederen wrote: > How are we going to solve the grub installation problem within > debian-installer then? I will have to verify the issue myself. I did a quick test with qemu-ppc but the kernel didn't boot for me. I will try on my iBook G4 later this week and commit a fix if there is a bug. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Grub failed
On Sun, 2023-11-26 at 07:57 +0700, Jeroen Diederen wrote: > Another thing that I now remember is that on one ppc64 machine > after upgrading grub-ieee1275, I had to do a fsck.hfs, as it somehow > screw up the bootstrap partition. My feeling is that the problem resides > in grub-ieee1275, which got an upgrade on November 9 (changelog grub2) > and was built by buildd in November 10. All that grub-install does is copying files into the directory /boot/grub, it makes zero modifications to the filesystem itself or the block device. It doesn't even modify the NVRAM because it's called with "--no-nvram" [1]. The HFS filesystem corruption is most likely a result of the outdated hfsprogs package which has some issues on big-endian systems as I discovered while working on the hfsprogs source code. This will be resolved once I finally update that package. Adrian > [1] > https://salsa.debian.org/installer-team/grub-installer/-/blob/master/grub-installer#L1000 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Grub failed
On Sun, 2023-11-26 at 07:19 +0700, Jeroen Diederen wrote: > I know that but can’t it be that the grub installation into /boot/grub > with geub-ieee1275 somehow makes the system lose the ability to see > /dev/sda and therefore also unable to invoke hmount? The grub-installer script was not able to invoke »hmount« because the package »hfsutils« was not installed in the /target chroot and not because the block device /dev/sda went away. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Grub failed
On Sun, 2023-11-26 at 02:57 +0700, Jeroen Diederen wrote: > With the same image I have installed Debian successfully many times, > both powerpc and ppc64. Can’t it have something to do with a change in > grub-ieee1275 lately? No, hfsutils is completely independent of grub-ieee1275 as the »hmount« utility is invoked after grub-install has been run and GRUB was installed into /boot/. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Grub failed
On Sun, 2023-11-26 at 02:47 +0700, Jeroen Diederen wrote: > Another thing I noticed in the log I sent but also when going into a > terminal from the installer menu is that /dev/sda can’t be found after > the grub-install step. You might have taken an image which is missing the hfsprogs and partman-hfs packages. As mentioned on this list before, there is no 100% robust image build for PowerMac due to the complicated licensing situation of Apple's »hfs« package. I have tried to convince Apple to switch the license to something DFSG-compatible but I never got an answer. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Grub failed
On Sat, 2023-11-25 at 16:35 +0100, John Paul Adrian Glaubitz wrote: > I will have to look up again where hfsutils needs to be added to the > package lists. I think, it was part of debian-cd. It's still there: > https://salsa.debian.org/images-team/debian-cd/-/blob/master/tools/generate_di%2Bk_list#L293 > https://salsa.debian.org/images-team/debian-cd/-/blob/master/tools/generate_di%2Bk_list#L306 So, not sure why it shouldn't get installed automatically. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Grub failed
Hi! On Fri, 2023-11-24 at 10:52 +0700, Jeroen Diederen wrote: > Good morning Adrian, > > # chroot /target > # dpkg -l hfsutils > dpkg-query: no packages found matching hfsutils That explains the problem. As a workaround, one can install hfsutils inside the chroot before choosing to install grub from the installer menu. I will have to look up again where hfsutils needs to be added to the package lists. I think, it was part of debian-cd. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: What are the current available browser options for debian-ppc64?
Hi! On Thu, 2023-11-23 at 23:45 +0100, kristoffer...@tuta.io wrote: > > Deeper debugging is beyond my skills. I don't know if this helps but the "bt" > command gave me this: > > (gdb) bt > #0 i32_load8_u (addr=2016478208, mem=) at rlbox.wasm.c:146 > #1 w2c_rlbox_streqci (var_p0=var_p0@entry=262000, var_p1=2016478208, > instance=) at rlbox.wasm.c:1499 So, it crashes again in the WASM code in rlbox.wasm.c at line 146. I'll look into it the following days. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Grub failed
On Thu, 2023-11-23 at 13:13 +0100, John Paul Adrian Glaubitz wrote: > > > On Nov 23, 2023, at 12:43 PM, Jeroen Diederen wrote: > > > > Nov 23 09:45:09 main-menu[251]: (process:8046): chroot: can't execute > > 'hmount': No such file or directory > > The chroot is missing hfsutils which is why “hmount” fails. > > Could be that someone dropped it from the packages list not knowing what they > are doing. Can you please check whether the package "hfsutils" was installed into the chroot? # chroot /target # dpkg -l hfsutils Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Grub failed
> On Nov 23, 2023, at 12:43 PM, Jeroen Diederen wrote: > > Nov 23 09:45:09 main-menu[251]: (process:8046): chroot: can't execute > 'hmount': No such file or directory The chroot is missing hfsutils which is why “hmount” fails. Could be that someone dropped it from the packages list not knowing what they are doing. Adrian
Re: What are the current available browser options for debian-ppc64?
Hi! On Tue, 2023-11-21 at 22:05 +0100, Johannes Brakensiek wrote: > Am Dienstag, dem 21.11.2023 um 21:20 +0100 schrieb John Paul Adrian > Glaubitz: > > > > Please test this build which include the image decoder big-endian fix > > from VoidPPC: > > > > > https://people.debian.org/~glaubitz/firefox-ppc64/test002/ > > > > Adrian > > > > thanks for providing the binary. It still segfaults. Could you provide > debug symbols as well, please? I'd send a backtrace. Here you go: https://box.fu-berlin.de/s/RAPxkDspfHBzG48 I am starting to fear that we're seeing a new bug here on ppc64 for which there is no patch yet. FWIW, if we manage to fix Firefox on ppc64, I do actually have some sort of commit access for Firefox to get patches landed. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: What are the current available browser options for debian-ppc64?
On Tue, 2023-11-21 at 20:38 +0100, John Paul Adrian Glaubitz wrote: > I have just been reminded by a comment in the upstream bug report [1] that > the VoidPPC > project actually has a number of patches which fix issues in Firefox on > PowerPC [2] and > I'm rebuilding Firefox with this patch [3] now which claims to address issues > with the > image decoder on big-endian targets. Please test this build which include the image decoder big-endian fix from VoidPPC: > https://people.debian.org/~glaubitz/firefox-ppc64/test002/ Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: What are the current available browser options for debian-ppc64?
Hi! On Mon, 2023-11-20 at 22:32 +0100, John Paul Adrian Glaubitz wrote: > There is currently no up-to-date version of Firefox for 32-bit PowerPC since > Firefox > currently requires NodeJS to build which is not available on 32-bit PowerPC > at the > moment. > > It is actually possible, however, to use transpile the JavaScript files from > x86_64 > for 32-bit PowerPC so that NodeJS is actually not needed. The Debian package > does > not implement such a mechanism at the moment though while Oracle does it on > Solaris > for SPARC [1]. > > Anyways, this particular crash a known upstream bug in Firefox [2]. I wonder > whether > it might be fixed by this particular patch [3]. I have just been reminded by a comment in the upstream bug report [1] that the VoidPPC project actually has a number of patches which fix issues in Firefox on PowerPC [2] and I'm rebuilding Firefox with this patch [3] now which claims to address issues with the image decoder on big-endian targets. Let's see. Adrian PS: This is why it's so important to upstream patches. The VoidPPC and Solaris people did so much work but didn't push for their patches to be merged upstream or at least, they weren't trying hard enough. > [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1845669 > > [2] > https://github.com/void-ppc/void-packages-ppc750/tree/master/srcpkgs/firefox/patches > [3] > https://github.com/void-ppc/void-packages-ppc750/blob/master/srcpkgs/firefox/patches/big-endian-image-decoders.patch -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: What are the current available browser options for debian-ppc64?
On Tue, 2023-11-21 at 08:32 -0800, Ken Cunningham wrote: > I added an 8GB swapfile, and (slowly) got this backtrace: > > # cat error.txt > Thread 1 "firefox" received signal SIGSEGV, Segmentation fault. > i32_load8_u (addr=2014643200, mem=) at rlbox.wasm.c:146 > 146 rlbox.wasm.c: No such file or directory. > (gdb) bt > #0 i32_load8_u (addr=2014643200, mem=) at rlbox.wasm.c:146 Looks like a crash in the WASM code. Could you please check whether the backtrace looks different with the older Firefox package which does not include the previously mentioned patch? > http://ftp.ports.debian.org/debian-ports/pool-ppc64/main/f/firefox/ Please install both these packages, then re-run Firefox from gdb and post the backtrace here. If my theory is correct, we will at least have the confirmation that the other patch is correct and fixes the graphics format crash. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: What are the current available browser options for debian-ppc64?
Hello! On Mon, 2023-11-20 at 15:39 -0800, Ken Cunningham wrote: > on my system I had another segfault, in libxul. A more detailed backtrace would be useful. libxul is basically all of Firefox, so referring to a crash in libxul is not saying much. Try installing the debug package from here: > https://box.fu-berlin.de/s/oLNPG2EoPtyC8tb and then run firefox from gdb. > hopefully others had more luck. sure be nice to get a current browser! It would be nice if more people could step forward and help me resolve these issues. Running gdb and testing patches isn't that difficult, for example, and would help me a lot in the process in shaping Debian Ports architectures. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: What are the current available browser options for debian-ppc64?
On Mon, 2023-11-20 at 22:32 +0100, John Paul Adrian Glaubitz wrote: > Anyways, this particular crash a known upstream bug in Firefox [2]. I wonder > whether > it might be fixed by this particular patch [3]. I have rebuild the Firefox package for ppc64 with this patch included: > https://people.debian.org/~glaubitz/firefox-ppc64/ Could anyone test this and report back, please? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: What are the current available browser options for debian-ppc64?
Hi Jeffrey! On Mon, 2023-11-20 at 15:37 -0500, Jeffrey Walton wrote: > On Mon, Nov 20, 2023 at 1:56 PM Ken Cunningham > wrote: > > > > > > The one I have installed is: > > > > firefox/unstable,now 119.0.1-1 ppc64 > > > > and it has a segmentation fault when you launch it. > > Out of curiosity... would that happen to be a G4 or a non-Altivec machine? There is currently no up-to-date version of Firefox for 32-bit PowerPC since Firefox currently requires NodeJS to build which is not available on 32-bit PowerPC at the moment. It is actually possible, however, to use transpile the JavaScript files from x86_64 for 32-bit PowerPC so that NodeJS is actually not needed. The Debian package does not implement such a mechanism at the moment though while Oracle does it on Solaris for SPARC [1]. Anyways, this particular crash a known upstream bug in Firefox [2]. I wonder whether it might be fixed by this particular patch [3]. Adrian > [1] > https://github.com/oracle/solaris-userland/tree/master/components/desktop/firefox/wrapper-node > [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1845669 > [3] > https://github.com/oracle/solaris-userland/blob/master/components/desktop/firefox/patches/firefox-53-sparc-gfx-atomicops.patch -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: What are the current available browser options for debian-ppc64?
Hello! > On Nov 20, 2023, at 10:56 AM, Jeroen Diederen wrote: > > Firefox does not work. Did you try the latest version 119? If there is a patch which fixes the crash on big-endian targets, we could include it in the Debian package or I could try to get it merged upstream. Adrian
Re: What are the current available browser options for debian-ppc64?
On Sun, 2023-11-19 at 16:46 -0800, Ken Cunningham wrote: > Does anyone have or know about a browser they use on debian > ppc64 they would feel comfortable to recommend? Firefox is available and up to date for ppc64. > https://buildd.debian.org/status/package.php?p=firefox=sid Did you try to install and run it? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: update grub-ieee1275 failed on G5 iMac ppc64
On Tue, 2023-11-14 at 20:16 +0700, Jeroen Diederen wrote: > Thank you so much. > I did it on /dev/sda2 though. Yeah, I forgot whether it was sda1 or sda2. I think it's sda1 on sparc64. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: update grub-ieee1275 failed on G5 iMac ppc64
Hello! On Tue, 2023-11-14 at 17:17 +0700, Jeroen Diederen wrote: > I tried and apt upgrade and it tried to upgrade grub-ieee1275 on a G5 > iMac (ppc64) which failed. > > Setting up grub-ieee1275 (2.12~rc1-12) ... > Installing for powerpc-ieee1275 platform. > grub-install: error: cannot backup > `/boot/grub/powerpc-ieee1275/adler32.mod': Read-only file system. You have to install hfsprogs and run fsck.hfs /dev/sda1 to fix the HFS filesystem of your /boot partition. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: PowerPC Grub doesnt work
Hi Leo! On Fri, 2023-11-03 at 14:40 -0300, Leo Historias wrote: > It doesnt give me a options and fails to install on qemu leading to > a non-bootable hard drive despite being obviously installed The problem is not QEMU but the inadequate firmware emulation when emulating a PowerPC Macintosh. You either need to boot kernel and initrd directly from the QEMU command line or use a more modern platform emulation like POWER. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: dpkg: error processing archive /var/cache/apt/archives/usr-is-merged_38_all.deb (--unpack):
Hello, On Tue, 2023-10-31 at 08:46 +0100, John Paul Adrian Glaubitz wrote: > I will trigger the chroot tarballs to be regenerated. You will have to create > your schroot session anew. This will hopefully fix the issue. Should be fixed now. At least works for me on perotto.debian.net. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: dpkg: error processing archive /var/cache/apt/archives/usr-is-merged_38_all.deb (--unpack):
Good morning On Tue, 2023-10-31 at 08:39 +0100, Mathieu Malaterre wrote: > Would anyone know what to do with perotto.d.n ? Thanks > > Here is what I get today: > > % sessionid=$(schroot -b -c sid) > % dd-schroot-cmd -c $sessionid apt-get update > % dd-schroot-cmd -c $sessionid apt-get upgrade > [..] > Preparing to unpack .../usr-is-merged_38_all.deb ... > > > ** > * > * The usr-is-merged package cannot be installed because this system does > * not have a merged /usr. > * > * Please install the usrmerge package to convert this system to merged-/usr. > * > * For more information please read https://wiki.debian.org/UsrMerge. > * > ** > > > dpkg: error processing archive > /var/cache/apt/archives/usr-is-merged_38_all.deb (--unpack): > new usr-is-merged package pre-installation script subprocess returned > error exit status 1 > Errors were encountered while processing: > /var/cache/apt/archives/usr-is-merged_38_all.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > Command apt-get --assume-yes -o Dpkg::Options::=--force-confnew > upgrade exited with exit code 1. I will trigger the chroot tarballs to be regenerated. You will have to create your schroot session anew. This will hopefully fix the issue. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: help needed with LibreOffice Java bridge on s390x/ppc64el
Hello! On Mon, 2023-10-23 at 23:20 +0200, Rene Engelhard wrote: > > > we're explicitly building with OpenJDK 8 while Debian builds > > > with OpenJDK 17 [2] which might explain the different test results. > > Which is no option here... It may not be an option, but it might give you a pointer how to fix the actual bug, even with OpenJDK 17. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: help needed with LibreOffice Java bridge on s390x/ppc64el
Hello! On Mon, 2023-10-23 at 21:59 +0200, Rene Engelhard wrote: > since LibreOffice 7.6 (which added some more tests which were manual > before to the automatic set) the testtools' bridge test fails: > > https://buildd.debian.org/status/fetch.php?pkg=libreoffice=ppc64el=4%3A7.6.2-3=1697981409=0 > > See the discussion upstream in > https://lists.freedesktop.org/archives/libreoffice/2023-September/thread.html: > "new bridgetest failures in 7.6 on ppc64le " > > and continued in October > > https://lists.freedesktop.org/archives/libreoffice/2023-October/thread.html > > especially > https://lists.freedesktop.org/archives/libreoffice/2023-October/091058.html > and > https://lists.freedesktop.org/archives/libreoffice/2023-October/091059.html > > after which unfortunately noting important happened. (And I don't see a > patch either at Fedora git nor submitted upstream to fix this.) These tests seem to be passing for 7.6.2 on openSUSE on ppc64el [1]. However, on openSUSE, we're explicitly building with OpenJDK 8 while Debian builds with OpenJDK 17 [2] which might explain the different test results. Adrian > [1] > https://build.opensuse.org/package/live_build_log/openSUSE:Factory:PowerPC/libreoffice/standard/ppc64le > [2] > https://build.opensuse.org/package/view_file/openSUSE:Factory/libreoffice/0001-Revert-java-9-changes.patch?expand=1 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1054165: ffmpeg: FTBFS when trying to bootstrap with pkg.ffmpeg.stage1
Source: ffmpeg Version: 6.0-7 Severity: normal User: debian-powerpc@lists.debian.org Usertags: ppc64 X-Debbugs-Cc: debian-powerpc@lists.debian.org Hello! I just tried to rebootstrap ffmpeg for all Debian Ports architectures and noticed that this no longer works due to the build dependency libcjson-dev missing for build profile "pkg.ffmpeg.stage1": pkg-config --exists --print-errors librist >= 0.2.7 Package libcjson was not found in the pkg-config search path. Perhaps you should add the directory containing `libcjson.pc' to the PKG_CONFIG_PATH environment variable Package 'libcjson', required by 'librist', not found ERROR: librist >= 0.2.7 not found using pkg-config This can be fixed by manually installing libcjson-dev into the chroot, so adding the build dependency "libcjson-dev [pkg.ffmpeg.stage1]" to debian/control should fix this bug. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1054035: mpich: FTBFS on ppc64 due to bogus architecture check in debian/rules
Source: mpch Version: 4.1.2-2 Severity: normal User: debian-powerpc@lists.debian.org Usertags: ppc64 X-Debbugs-Cc: debian-powerpc@lists.debian.org Hello! The configure scirpt for src:mpich is run with --with-ucx on ppc64 despite the architecture not being whitelisted in the architecture check in debian/ rules [1]: checking for rdma/fabric.h... yes checking for fi_getinfo in -lfabric... yes checking for ucp/api/ucp.h... no configure: error: --with-ucx is given but not found tail -v -n \+0 config.log This is because the architecture check in debian/rules uses findstring() which matches "ppc64" in "UCX_ARCH" which is set to "amd64 ppc64el arm64". The proper approach would be to use filter() instead of findstring() since the former matches only words separated by whitespaces [2]. I have verified that this fixes the FTBFS on ppc64. Thanks, Adrian > [1] > https://buildd.debian.org/status/fetch.php?pkg=mpich=ppc64=4.1.2-2=1694900148=0 > [2] https://www.gnu.org/software/make/manual/html_node/Text-Functions.html -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Crowdfunding a small but important powerpc bugfix
Hi! On Wed, 2023-10-11 at 08:58 -0600, Stan Johnson wrote: > Please post a link that indicates whether the GHC Haskell Compiler > license is compatible with the GPL. I haven't been able to find anything > online regarding compatibility. I would be interested in any license > issues before learning more about this compiler. > > The license appears to allow modifications and re-distribution in binary > form only, which seems incompatible with the GPL: > > https://www.haskell.org/ghc/license.html It's just the standard 3-clause BSD license [1] and those are GPL-compatible [2]. Adrian > [1] https://opensource.org/license/bsd-3-clause/ > [2] https://en.wikipedia.org/wiki/License_compatibility#GPL_compatibility -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Crowdfunding a small but important powerpc bugfix
Hi! There is a regression in the GHC Haskell Compiler [1] that I have been investigating for several days. While I have been able to identify the commit that introduced the regression, I have not been able to fix that issue since I don't have the necessary Haskell knowledge to be able to work on GHC. Since the broken GHC compiler currently blocks a lot of packages on 32-bit PowerPC and the upstream developers don't seem to be too motivated at the moment to fix the bug, I was wondering whether people here would be willing to throw in some money to create a bounty on that particular bug to pay a Haskell developer to fix it. I have run such campaigns successfully in the past for GCC such as [2] and [3] (links currently 404 for me), so I think that should work for GHC, too. I don't think we need to collect a lot of money, a few hundred dollars should probably be more than enough. We don't have to use Bountysource.com for what is worth. Any other platform or donation system would be perfectly fine, too. Comments? Suggestions? Thanks, Adrian > [1] https://gitlab.haskell.org/ghc/ghc/-/issues/23969 > [2] > https://app.bountysource.com/issues/80706251-m68k-convert-the-backend-to-mode_cc-so-it-can-be-kept-in-future-releases > [3] > https://app.bountysource.com/issues/84630749-avr-convert-the-backend-to-mode_cc-so-it-can-be-kept-in-future-releases -- .''`. 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
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: ghc: FTBFS haskell-random powerpc (ghc Segmentation fault)
Hi Christian! On Mon, 2023-10-09 at 09:25 +0200, Christian Marillat wrote: > > On Mon, 2023-10-09 at 08:57 +0200, Christian Marillat wrote: > > > > Could you provide the disassembled code for the affected code section? > > Is this enough ? > > , > > Dump of assembler code for function __GI_kill: > >0xf7644b94 <+0>: li r0,37 > >0xf7644b98 <+4>: sc > > => 0xf7644b9c <+8>: bnslr+ > >0xf7644ba0 <+12>:b 0xf762a200 <__syscall_error> > > End of assembler dump. > ` I think the interesting part would be the disassembly of base_GHCziFloat_floatToDigits_closure () where the actual crash happened. Your disassembly seems to show parts of the segfault handler. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer `. `' Physicist `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
