Re: X stopped working with 5.14 on iBook
On Thu, Oct 7, 2021 at 10:21 AM John Paul Adrian Glaubitz wrote: > > On 10/7/21 06:16, Stan Johnson wrote: > > Compiling the downloaded kernel-source using Debian's .config file > > "config.powerpc_none_powerpc.xz" resulted in a 200 MB kernel (perhaps > > because it included all possible options), and I couldn't get it to boot > > (but I also didn't compile or install any modules). But compiling using > > the same .config file (see attached) that I've been using for testing > > 5.13 kernels, and that I also used for the above kernels that worked, > > results in a working 12 MB kernel, and X is also working: > > > > # uname -a > > Linux ppc-cube 5.14.9-pmac #2 SMP Wed Oct 6 21:38:58 MDT 2021 ppc GNU/Linux > > # ls -l vmlinux > > -rwxr-xr-x 1 root root 12382136 Oct 6 15:39 vmlinux > > > > So I think the problem with the default kernel in Debian SID (5.14.0-2) > > has already been fixed, or perhaps there was an issue with the options > > that were selected for the .config file. Either way, it doesn't appear > > that a bisect is needed. > > Well, we still have the Debian stock kernel not working. So we might be > missing a kernel option that is required for X to work on the PowerMacs. This one ? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790690 > Did you try building a custom kernel with the config file located in the > /boot directory? > > Adrian > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaub...@debian.org > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 >
Poll: Is anyone using nouveau driver on ppc64 system?
Hi all, One of the kernel maintainers is wondering if the nouveau driver is completely broken with 64K pages ? So my question is simply: is anyone out there using a ppc64 system with nouveau on a default linux-image-powerpc64 debian system (64K page). I am only interested in ppc64be system only. Thanks for your time,
Re: Poll: Is anyone using nouveau driver on ppc64 system?
Hi Stephen ! On Fri, Oct 8, 2021 at 8:34 AM Stephen Harker wrote: > > Hi Mathieu, > > > One of the kernel maintainers is wondering if the nouveau driver is > > completely broken with 64K pages ? > > > > So my question is simply: is anyone out there using a ppc64 system > > with nouveau on a default linux-image-powerpc64 debian system (64K > > page). I am only interested in ppc64be system only. > > I have debian running as below. I am emailing from my old Fedora 28 > partition as I had not got around to enabling email from Debian. I > have had no problems with X11 using a GeForce 6600 LE (until recently > I was using a 7600GTX 512 and, despite not fixing some boot settings, > it is working with the 6600). The glxinfo below may be partly > incorrect due to those settings. > > uname -a output: > > Linux 5.10.0-8-powerpc64 #1 SMP Debian 5.10.46-4 (2021-08-03) ppc64 > GNU/Linux > > cat /proc/cpuinf:o > > processor : 0 > cpu : PPC970MP, altivec supported > clock : 2000.00MHz > revision: 1.1 (pvr 0044 0101) > > processor : 1 > cpu : PPC970MP, altivec supported > clock : 2000.00MHz > revision: 1.1 (pvr 0044 0101) > > timebase: > platform: PowerMac > model : PowerMac11,2 > machine : PowerMac11,2 > motherboard : PowerMac11,2 MacRISC4 Power Macintosh > detected as : 337 (PowerMac G5 Dual Core) > pmac flags : > L2 cache: 1024K unified > pmac-generation : NewWorld > > glxinfo (partly cut for space): > > name of display: :0 > display: :0 screen: 0 > direct rendering: Yes > server glx vendor string: SGI > server glx version string: 1.4 > server glx extensions: > GLX_ARB_create_context, GLX_ARB_create_context_no_error, > GLX_ARB_create_context_profile, GLX_ARB_fbconfig_float, > GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, > GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, > GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, > GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_no_config_context, > GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, > GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, > GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, > GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, > GLX_SGI_swap_control > client glx vendor string: Mesa Project and SGI > client glx version string: 1.4 > client glx extensions: > GLX_ARB_context_flush_control, GLX_ARB_create_context, > GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, > GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, > GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, > GLX_ATI_pixel_format_float, GLX_EXT_buffer_age, > GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, > GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, > GLX_EXT_import_context, GLX_EXT_no_config_context, GLX_EXT_swap_control, > GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, > GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, > GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, > GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_NV_float_buffer, > GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, > GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, > GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync > GLX version: 1.4 > GLX extensions: > GLX_ARB_create_context, GLX_ARB_create_context_no_error, > GLX_ARB_create_context_profile, GLX_ARB_fbconfig_float, > GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, > GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, > GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, > GLX_EXT_import_context, GLX_EXT_no_config_context, GLX_EXT_swap_control, > GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, > GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_query_renderer, > GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, > GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, > GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, > GLX_SGI_swap_control, GLX_SGI_video_sync > Extended renderer info (GLX_MESA_query_renderer): > Vendor: nouveau (0x10de) > Device: NV43 (0x142) > Version: 21.2.3 > Accelerated: yes > Video memory: 108MB > Unified memory: no > Preferred profile: compat (0x2) > Max core profile version: 0.0 > Max compat profile version: 2.1 > Max GLES1 profile version: 1.1 > Max GLES[23] profile version: 2.0 > OpenGL vendor string: nouveau > OpenGL renderer string: NV43 > OpenGL version string: 2.1 Mesa 21.2.3 > OpenGL shading language version string: 1.20
Re: Poll: Is anyone using nouveau driver on ppc64 system?
John, On Mon, Oct 11, 2021 at 10:34 PM John Ogness wrote: > > Hi Mathieu, > > On 2021-10-07, Mathieu Malaterre wrote: > > One of the kernel maintainers is wondering if the nouveau driver is > > completely broken with 64K pages ? > > > > So my question is simply: is anyone out there using a ppc64 system > > with nouveau on a default linux-image-powerpc64 debian system (64K > > page). I am only interested in ppc64be system only. > > My main desktop machine at home is a PowerMac G5 (Dual PPC970, > PowerMac7,2), so it gets lots of daily use for audio, video, and web > browsing. The graphic card is: > > :f0:10.0 VGA compatible controller: NVIDIA Corporation NV34 [GeForce FX > 5200 Ultra] (rev a1) Thanks for your report ! In case you have not seen it before, this is known as: * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790690 It is unlikely that the root issue will ever be solved, so we need to provide a 4K page kernel for the affected users. As you've seen from another user report, it appears that nouveau may work under certain work load: * https://lists.debian.org/debian-powerpc/2021/10/msg00068.html -M
Re: red background always during install
On Mon, Mar 28, 2022 at 9:52 AM Dennis Clarke wrote: > > > Red background always during install : > > https://i.imgur.com/ja5SI2x.png > > Strange but true :\ > > Same thing I saw last year and the year before that etc ... Can you check that radeonfb module was loaded ? I believe Alt+F2 gives you a shell during the install. https://bugs.debian.org/826629 Thanks
Re: red background always during install
On Mon, Mar 28, 2022 at 10:00 AM Dennis Clarke wrote: > > On 3/28/22 03:56, Mathieu Malaterre wrote: > > On Mon, Mar 28, 2022 at 9:52 AM Dennis Clarke wrote: > >> > >> > >> Red background always during install : > >> > >> https://i.imgur.com/ja5SI2x.png > >> > >> Strange but true :\ > >> > >> Same thing I saw last year and the year before that etc ... > > > > Can you check that radeonfb module was loaded ? I believe Alt+F2 gives > > you a shell during the install. > > > > https://bugs.debian.org/826629 > > > > Thanks > > Computer says no. :) sorry. > > I checked /proc/modules and there is no radeon to be seen at all. How about: $ dmesg | grep radeon
Re: Need for manual link to libatomic on powerpc?
On Tue, Aug 23, 2022 at 3:34 PM Jeffrey Walton wrote: > > Hi Everyone, > > I'm trying to track down a Crypto++ 8/GCC 12 bug at [1,2]. Our Debian > maintainer, who is helping with testing, mentioned we were missing > libatomic during link when using santiziers on powerpc and hppa.[3,4] > That kind of caught me off-guard. > > On Fedora (but not Debian in the past), we needed to install gcc, g++, > libasan, libubsan and friends. Libraries for Asan and Ubsan are > separate installs on Fedora (but not Debian). However, once installed, > the compiler driver added the necessary libs (like libubsan and > libatomic) when it encountered an option like -fsanitize=undefined. > > My question is, are libasan, libubsan and friends a separate install > for Debian on powerpc and hppa? > > If not, does anyone know why libatomic might not be added by the > compiler driver when needed on Debian powerpc? Last time I asked, I was reminded the status: * https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104248#c4 Long story short, gcc will not automatically add -latomic for you .. end of story :(
Tracking a bug on POWER10
Hi there, I vaguely remember someone mentioning a service where one could ssh onto ppc64el machines. I need access to a POWER10 machine to track a bug. platti.d.o is POWER8 AFAIK. Thanks !
dpkg: error processing archive /var/cache/apt/archives/usr-is-merged_38_all.deb (--unpack):
Hi folks, 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.
"Power Mac Gigabit Ethernet" (codename "Mystic")
Dear all, Does anyone of you has access to an SMP PPC32 machine ? I need to check if an issue I am seeing on an SMP PPC64 kernel (PPC32 userland) can be reproduced on a pure SMP PPC32 machine. Thanks much for help. -M
Re: "Power Mac Gigabit Ethernet" (codename "Mystic")
On Fri, Apr 8, 2016 at 7:15 PM, Kristen R wrote: > >> On Apr 8, 2016, at 3:02 AM, Mathieu Malaterre wrote: >> >> Dear all, >> >> Does anyone of you has access to an SMP PPC32 machine ? I need to >> check if an issue I am seeing on an SMP PPC64 kernel (PPC32 userland) >> can be reproduced on a pure SMP PPC32 machine. >> >> Thanks much for help. >> >> -M >> > > I have the PowerPC is question. With the original 450MHz dual processor or a > Sonnet 1.6GHz which is currently in the machine. And I have a weekend too! > > How can I help? Neat ! So: 1. Make sure you are running linux-image-powerpc-smp (uname -a to check). 2. Step: $ sudo apt-get build-dep mono-devel $ cd $HOME $ git clone https://github.com/mono/mono.git && cd mono $ ./autogen.sh --prefix=$HOME/blah $ make get-monolite-latest $ make V=1 PROFILE=basic Technically it should fails at this point. If not, I'd interested in the following log file: $ cd mcs/class/System $ export MONO_PATH="./../../class/lib/monolite:$MONO_PATH" $ $HOME/mono/mono/mini/mono --verify-all ./../../class/lib/monolite/basic.exe -d:NET_4_0 -d:NET_4_5 -d:MONO -d:BOOTSTRAP_BASIC -nowarn:1699 -d:DISABLE_CAS_USE -lib:./../../class/lib/basic -optimize /noconfig -nowarn:618 -d:CONFIGURATION_2_0 -d:FEATURE_PAL,SYSTEM_NAMESPACE,MONO,PLATFORM_UNIX -d:MONO_FEATURE_PROCESS_START -d:MONO_FEATURE_THREAD_ABORT -d:MONO_FEATURE_THREAD_SUSPEND_RESUME -unsafe -target:library -out:../../class/lib/basic/secxml/System.dll @./../../build/deps/basic_System.dll.sources >& runtime.log as well as: $ valgrind --tool=helgrind $HOME/mono/mono/mini/mono --verify-all ./../../class/lib/monolite/basic.exe -d:NET_4_0 -d:NET_4_5 -d:MONO -d:BOOTSTRAP_BASIC -nowarn:1699 -d:DISABLE_CAS_USE -lib:./../../class/lib/basic -optimize /noconfig -nowarn:618 -d:CONFIGURATION_2_0 -d:FEATURE_PAL,SYSTEM_NAMESPACE,MONO,PLATFORM_UNIX -d:MONO_FEATURE_PROCESS_START -d:MONO_FEATURE_THREAD_ABORT -d:MONO_FEATURE_THREAD_SUSPEND_RESUME -unsafe -target:library -out:../../class/lib/basic/secxml/System.dll @./../../build/deps/basic_System.dll.sources >& helgrind.log Thanks much !
Re: "Power Mac Gigabit Ethernet" (codename "Mystic")
On Sun, Apr 10, 2016 at 1:55 AM, kristen R wrote: > On 4/8/16 10:57 AM, Mathieu Malaterre wrote: >> On Fri, Apr 8, 2016 at 7:15 PM, Kristen R >> wrote: >>> >>>> On Apr 8, 2016, at 3:02 AM, Mathieu Malaterre >>>> wrote: >>>> >>>> Dear all, >>>> >>>> Does anyone of you has access to an SMP PPC32 machine ? I need >>>> to check if an issue I am seeing on an SMP PPC64 kernel (PPC32 >>>> userland) can be reproduced on a pure SMP PPC32 machine. >>>> >>>> Thanks much for help. >>>> >>>> -M >>>> >>> >>> I have the PowerPC is question. With the original 450MHz dual >>> processor or a Sonnet 1.6GHz which is currently in the machine. >>> And I have a weekend too! >>> >>> How can I help? >> >> >> Neat ! >> >> So: 1. Make sure you are running linux-image-powerpc-smp (uname -a >> to check). 2. Step: >> >> $ sudo apt-get build-dep mono-devel $ cd $HOME $ git clone >> https://github.com/mono/mono.git && cd mono $ ./autogen.sh >> --prefix=$HOME/blah $ make get-monolite-latest $ make V=1 >> PROFILE=basic >> >> Technically it should fails at this point. If not, I'd interested >> in the following log file: >> >> $ cd mcs/class/System $ export >> MONO_PATH="./../../class/lib/monolite:$MONO_PATH" $ >> $HOME/mono/mono/mini/mono --verify-all >> ./../../class/lib/monolite/basic.exe -d:NET_4_0 -d:NET_4_5 >> -d:MONO -d:BOOTSTRAP_BASIC -nowarn:1699 -d:DISABLE_CAS_USE >> -lib:./../../class/lib/basic -optimize /noconfig -nowarn:618 >> -d:CONFIGURATION_2_0 >> -d:FEATURE_PAL,SYSTEM_NAMESPACE,MONO,PLATFORM_UNIX >> -d:MONO_FEATURE_PROCESS_START -d:MONO_FEATURE_THREAD_ABORT >> -d:MONO_FEATURE_THREAD_SUSPEND_RESUME -unsafe -target:library >> -out:../../class/lib/basic/secxml/System.dll >> @./../../build/deps/basic_System.dll.sources >& runtime.log >> >> as well as: >> >> $ valgrind --tool=helgrind $HOME/mono/mono/mini/mono --verify-all >> ./../../class/lib/monolite/basic.exe -d:NET_4_0 -d:NET_4_5 >> -d:MONO -d:BOOTSTRAP_BASIC -nowarn:1699 -d:DISABLE_CAS_USE >> -lib:./../../class/lib/basic -optimize /noconfig -nowarn:618 >> -d:CONFIGURATION_2_0 >> -d:FEATURE_PAL,SYSTEM_NAMESPACE,MONO,PLATFORM_UNIX >> -d:MONO_FEATURE_PROCESS_START -d:MONO_FEATURE_THREAD_ABORT >> -d:MONO_FEATURE_THREAD_SUSPEND_RESUME -unsafe -target:library >> -out:../../class/lib/basic/secxml/System.dll >> @./../../build/deps/basic_System.dll.sources >& helgrind.log >> >> Thanks much ! >> > > Mathieu, > > I have finished with the build process and attempted to gather logs. I > have attached a text file showing commands and results as requested. > > Let me know what more you would like Kristen, You need to remove the line wrapping in the shell commands. See it attached again. Thanks for your time. run.sh Description: Bourne shell script
(Closed) Re: "Power Mac Gigabit Ethernet" (codename "Mystic")
On Fri, Apr 8, 2016 at 1:02 PM, Mathieu Malaterre wrote: > Dear all, > > Does anyone of you has access to an SMP PPC32 machine ? I need to > check if an issue I am seeing on an SMP PPC64 kernel (PPC32 userland) > can be reproduced on a pure SMP PPC32 machine. Thanks everyone out there for your kind help. I've managed to track down the issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819711#36 I do not need access to SMP / PPC32 system anymore. Again thanks much for your (cpu) time ! -M
Re: Bug#692324: Oops and hang at boot
On Tue, May 26, 2015 at 5:21 PM, Daniel Kahn Gillmor
wrote:
> On Tue 2015-05-26 04:54:47 -0400 about https://bugs.debian.org/692324,
> Mathieu Malaterre wrote:
>> Any update with more recent kernel ?
>
> Sorry, i don't have easy access to this machine ("colddeadhands") right
> now. I know it was running the recent kernel with no problems as of
> about a year ago (early 2014), but i don't recall whether it crashed
> when loading snd-powermac, or whether i had functional audio device
> access or not.
snd-powermac is now blacklisted upon installation. I believe this is
safe to close this bug report.
Thanks.
linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly
Dear all, I am looking for testers for the following patch: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741663#20 Wolfram (CC here) is looking for feedback from users for this patch. Thanks much.
Suspend on iBook G3 (A1007) no longer works
Hi, Since the OP of #697606 does not have the hardware anymore, I am thinking of closing the bug report. Does anyone have access to an iBook G3 and wants to update the bug ? thx
Re: Airport wireless and current Debian
On Thu, Apr 14, 2016 at 1:02 AM, Riccardo Mottola wrote: > Hi, > > I just upgraded everything. > > I noticed that I cannot connect to my home wifi anymore, which is a pretty > simple WEP encrypted network, which always used to work. > > I noticed that the Airport card is detected as a device and that I can > configure it with iwconfig to the correct ESSID and KEY: What do you get running: $ apt-cache policy firmware-linux-nonfree
Re: systemd warning
Hi, On Thu, Apr 14, 2016 at 1:04 AM, Riccardo Mottola wrote: > Hi, > > in my dmesg I see this: > > [ 268.896698] systemd-logind[1976]: New seat seat0. > [ 268.941156] systemd-logind[1976]: Failed to start user service, ignoring: > Unknown unit: user@1000.service > > > should I worry? where does it come from? https://bugs.debian.org/756247
Re: Airport wireless and current Debian
On Thu, Apr 14, 2016 at 8:04 PM, Riccardo Mottola wrote: > Hi, > > Mathieu Malaterre wrote: >>> >>> that I can >>> >configure it with iwconfig to the correct ESSID and KEY: >> >> What do you get running: >> >> $ apt-cache policy firmware-linux-nonfree > > > > firmware-linux-nonfree: > Installed: (none) > Candidate: 20160110-1 > Version table: > 20160110-1 500 > 500 http://ftp.de.debian.org/debian unstable/non-free powerpc > Packages > > I just installed it yesterday, because otherwise during startup I saw in the > messages a problem with missing firmware. That precisely states you did not install it...
d-i: 4.3. Preparing Files for USB Memory Stick Booting
Does anyone knows what happen to section: 4.3. Preparing Files for USB Memory Stick Booting in the powerpc install guide ? I see it alright from here: https://www.debian.org/releases/stable/amd64/ch04.html.en but not from here: https://www.debian.org/releases/stable/powerpc/ch04.html.en AFAIK USB booting works from powerpc system (at least some that I tried). Also I see reference to powerpc in the raw XML file: http://anonscm.debian.org/viewvc/d-i/trunk/manual/en/install-methods/boot-usb-files.xml?view=markup Comments ?
Re: d-i: 4.3. Preparing Files for USB Memory Stick Booting
Hi, On Tue, Apr 19, 2016 at 6:53 PM, Lennart Sorensen wrote: > On Tue, Apr 19, 2016 at 12:16:27PM +0200, Mathieu Malaterre wrote: >> Does anyone knows what happen to section: >> >> 4.3. Preparing Files for USB Memory Stick Booting >> >> in the powerpc install guide ? >> >> I see it alright from here: >> >> https://www.debian.org/releases/stable/amd64/ch04.html.en > > Well that's x86_64 so totally different thing. > >> but not from here: >> >> https://www.debian.org/releases/stable/powerpc/ch04.html.en >> >> AFAIK USB booting works from powerpc system (at least some that I tried). >> >> Also I see reference to powerpc in the raw XML file: >> >> http://anonscm.debian.org/viewvc/d-i/trunk/manual/en/install-methods/boot-usb-files.xml?view=markup >> >> Comments ? > > You could try to follow the older instructions and it might work: > > https://www.debian.org/releases/etch/powerpc/ch05s01.html.en > > Section 5.1.3 says newworld mac booting from USB. It has to be done > manually from openfirmware though, so it is probably the most complicated > boot method there is. > > It also had a warning that it might not work. Maybe it was removed from > newer release's documentation for a reason. That was precisely my point: why did it got removed ? And if so why is the upstream (raw) XML still referencing the USB boot mechanism for powerpc ? > The instructions from Ubuntu might work too: > https://wiki.ubuntu.com/PowerPCFAQ#How_do_I_boot_from_a_USB_drive.3F Neat it contains some more extra information I was not aware, thanks ! I did follow: https://lists.debian.org/debian-powerpc/2012/08/msg00042.html and it works for me, on a Mac Mini G4 (PPC). Full steps: # wget http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/8.4.0/powerpc/iso-cd/firmware-8.4.0-powerpc-netinst.iso # wget http://ftp.nl.debian.org/debian/dists/jessie/main/installer-powerpc/current/images/powerpc/hd-media/boot.img.gz # zcat boot.img.gz > /dev/sdb # sync [manually eject + plug USB drive again] # cp firmware-8.4.0-powerpc-netinst.iso /media/mathieu/bootable drive/shortname.iso [reboot + press and hold cmd/option/o/f] > boot usb1/disk@1:2,\\yaboot [some silly warning that partition cannot be read] boot: install done ! The only tricky part was that the name 'firmware-8.4.0-powerpc-netinst.iso' is a bit too long for HFS (AFAIK) and the file extension was *.si instead of *.iso which is an issue for the debian installer (hence the need for a shorter name on the USB disk). I'll make an installation-reports bug report for stretch and ask for the documentation clarification from there. Thanks -M
Re: d-i: 4.3. Preparing Files for USB Memory Stick Booting
On Wed, Apr 20, 2016 at 2:29 PM, Lennart Sorensen wrote: > On Wed, Apr 20, 2016 at 08:36:22AM +0200, Mathieu Malaterre wrote: >> Hi, >> >> On Tue, Apr 19, 2016 at 6:53 PM, Lennart Sorensen >> wrote: >> > On Tue, Apr 19, 2016 at 12:16:27PM +0200, Mathieu Malaterre wrote: >> >> Does anyone knows what happen to section: >> >> >> >> 4.3. Preparing Files for USB Memory Stick Booting >> >> >> >> in the powerpc install guide ? >> >> >> >> I see it alright from here: >> >> >> >> https://www.debian.org/releases/stable/amd64/ch04.html.en >> > >> > Well that's x86_64 so totally different thing. >> > >> >> but not from here: >> >> >> >> https://www.debian.org/releases/stable/powerpc/ch04.html.en >> >> >> >> AFAIK USB booting works from powerpc system (at least some that I tried). >> >> >> >> Also I see reference to powerpc in the raw XML file: >> >> >> >> http://anonscm.debian.org/viewvc/d-i/trunk/manual/en/install-methods/boot-usb-files.xml?view=markup >> >> >> >> Comments ? >> > >> > You could try to follow the older instructions and it might work: >> > >> > https://www.debian.org/releases/etch/powerpc/ch05s01.html.en >> > >> > Section 5.1.3 says newworld mac booting from USB. It has to be done >> > manually from openfirmware though, so it is probably the most complicated >> > boot method there is. >> > >> > It also had a warning that it might not work. Maybe it was removed from >> > newer release's documentation for a reason. >> >> That was precisely my point: why did it got removed ? And if so why is >> the upstream (raw) XML still referencing the USB boot mechanism for >> powerpc ? >> >> > The instructions from Ubuntu might work too: >> > https://wiki.ubuntu.com/PowerPCFAQ#How_do_I_boot_from_a_USB_drive.3F >> >> Neat it contains some more extra information I was not aware, thanks ! >> >> I did follow: >> >> https://lists.debian.org/debian-powerpc/2012/08/msg00042.html >> >> and it works for me, on a Mac Mini G4 (PPC). >> >> Full steps: >> >> # wget >> http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/8.4.0/powerpc/iso-cd/firmware-8.4.0-powerpc-netinst.iso >> # wget >> http://ftp.nl.debian.org/debian/dists/jessie/main/installer-powerpc/current/images/powerpc/hd-media/boot.img.gz >> # zcat boot.img.gz > /dev/sdb >> # sync >> [manually eject + plug USB drive again] >> # cp firmware-8.4.0-powerpc-netinst.iso /media/mathieu/bootable >> drive/shortname.iso >> >> [reboot + press and hold cmd/option/o/f] >> >> > boot usb1/disk@1:2,\\yaboot >> [some silly warning that partition cannot be read] >> boot: install > > I think maybe the 2 should be a 1 for the partition. Not certain. > >> done ! >> >> The only tricky part was that the name >> 'firmware-8.4.0-powerpc-netinst.iso' is a bit too long for HFS (AFAIK) >> and the file extension was *.si instead of *.iso which is an issue for >> the debian installer (hence the need for a shorter name on the USB >> disk). >> >> I'll make an installation-reports bug report for stretch and ask for >> the documentation clarification from there. > > Well checking the iso powerpc image, it has a partition table and yaboot > is there, so I think the hd-media step is not needed. I think you can > just write the iso to the usb key and it would work just as well. Hum. I tried burning the iso directly on key, but the filesystem was ISO 9660 which Open Firmware refused to read... If you want I can try harder tonight, but I assumed the key needed to be in HFS.
Re: d-i: 4.3. Preparing Files for USB Memory Stick Booting
On Wed, Apr 20, 2016 at 7:51 PM, Milan Kupcevic wrote: > On 04/19/2016 06:16 AM, Mathieu Malaterre wrote: >> Does anyone knows what happen to section: >> >> 4.3. Preparing Files for USB Memory Stick Booting >> >> in the powerpc install guide ? >> > > > The Mac producer officially does not support USB booting on PowerPC > machines. While it is often possible to do it, the firmware behavior is > inconsistent from version to version. Thus there is no official Debian > guideline on how to do it. The situation with IBM Power machines could > be different. > > There were discussions about this issue over the years on debian-powerpc > mailing list. Search the list for more hints. I could not find any solid arguments searching: "site:https://lists.debian.org/debian-powerpc usb boot open firmware" Everywhere else it seems to be working: - http://mac.linux.be/content/booting-open-firmware - http://apple.stackexchange.com/questions/11128/how-do-i-make-my-1-5-ghz-powerbook-g4-boot-from-a-usb-stick * http://apple.stackexchange.com/a/19958/85526 * http://apple.stackexchange.com/a/160252/85526 ← this one looks a bit crazy though I do not see why the d-i manual should not mention a method that works for some systems, we just need to put a warning.
Re: G4 MacMini network boot of install media failing at system clock set
Hi, On Tue, Apr 26, 2016 at 11:53 AM, wrote: > Hi folks, > > I have been trying to resurrect my MacMini. This is not clear to me, but my Mac Mini G4 does boot nicely from a properly prepared USB key: https://lists.debian.org/debian-powerpc/2016/04/msg00081.html Pay attention that on your HFS USB key, the iso file extension should still be *.iso (pay attention to long filename). Some people have reported that some NewWorld PowerMac may not boot from USB (again I have no clue which version/system). HTH -M
Re: d-i: 4.3. Preparing Files for USB Memory Stick Booting
On Wed, Apr 20, 2016 at 2:33 PM, Mathieu Malaterre wrote: > On Wed, Apr 20, 2016 at 2:29 PM, Lennart Sorensen > wrote: >> On Wed, Apr 20, 2016 at 08:36:22AM +0200, Mathieu Malaterre wrote: >>> Hi, >>> >>> On Tue, Apr 19, 2016 at 6:53 PM, Lennart Sorensen >>> wrote: >>> > On Tue, Apr 19, 2016 at 12:16:27PM +0200, Mathieu Malaterre wrote: >>> >> Does anyone knows what happen to section: >>> >> >>> >> 4.3. Preparing Files for USB Memory Stick Booting >>> >> >>> >> in the powerpc install guide ? >>> >> >>> >> I see it alright from here: >>> >> >>> >> https://www.debian.org/releases/stable/amd64/ch04.html.en >>> > >>> > Well that's x86_64 so totally different thing. >>> > >>> >> but not from here: >>> >> >>> >> https://www.debian.org/releases/stable/powerpc/ch04.html.en >>> >> >>> >> AFAIK USB booting works from powerpc system (at least some that I tried). >>> >> >>> >> Also I see reference to powerpc in the raw XML file: >>> >> >>> >> http://anonscm.debian.org/viewvc/d-i/trunk/manual/en/install-methods/boot-usb-files.xml?view=markup >>> >> >>> >> Comments ? >>> > >>> > You could try to follow the older instructions and it might work: >>> > >>> > https://www.debian.org/releases/etch/powerpc/ch05s01.html.en >>> > >>> > Section 5.1.3 says newworld mac booting from USB. It has to be done >>> > manually from openfirmware though, so it is probably the most complicated >>> > boot method there is. >>> > >>> > It also had a warning that it might not work. Maybe it was removed from >>> > newer release's documentation for a reason. >>> >>> That was precisely my point: why did it got removed ? And if so why is >>> the upstream (raw) XML still referencing the USB boot mechanism for >>> powerpc ? >>> >>> > The instructions from Ubuntu might work too: >>> > https://wiki.ubuntu.com/PowerPCFAQ#How_do_I_boot_from_a_USB_drive.3F >>> >>> Neat it contains some more extra information I was not aware, thanks ! >>> >>> I did follow: >>> >>> https://lists.debian.org/debian-powerpc/2012/08/msg00042.html >>> >>> and it works for me, on a Mac Mini G4 (PPC). >>> >>> Full steps: >>> >>> # wget >>> http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/8.4.0/powerpc/iso-cd/firmware-8.4.0-powerpc-netinst.iso >>> # wget >>> http://ftp.nl.debian.org/debian/dists/jessie/main/installer-powerpc/current/images/powerpc/hd-media/boot.img.gz >>> # zcat boot.img.gz > /dev/sdb >>> # sync >>> [manually eject + plug USB drive again] >>> # cp firmware-8.4.0-powerpc-netinst.iso /media/mathieu/bootable >>> drive/shortname.iso >>> >>> [reboot + press and hold cmd/option/o/f] >>> >>> > boot usb1/disk@1:2,\\yaboot >>> [some silly warning that partition cannot be read] >>> boot: install >> >> I think maybe the 2 should be a 1 for the partition. Not certain. >> >>> done ! >>> >>> The only tricky part was that the name >>> 'firmware-8.4.0-powerpc-netinst.iso' is a bit too long for HFS (AFAIK) >>> and the file extension was *.si instead of *.iso which is an issue for >>> the debian installer (hence the need for a shorter name on the USB >>> disk). >>> >>> I'll make an installation-reports bug report for stretch and ask for >>> the documentation clarification from there. >> >> Well checking the iso powerpc image, it has a partition table and yaboot >> is there, so I think the hd-media step is not needed. I think you can >> just write the iso to the usb key and it would work just as well. > > Hum. I tried burning the iso directly on key, but the filesystem was > ISO 9660 which Open Firmware refused to read... > > If you want I can try harder tonight, but I assumed the key needed to be in > HFS. My Mac Mini G4 does support ISO 9660. Steps: $ sudo dd if=debian.iso of=/dev/sdb bs=1M $ sudo sync [eject + put the USB key on mac mini, power up + cmd+option/o/f] > dir usb0/disk@1:2,\ -> should list the 'install' directory (and some other stuff) > boot usb0/disk@1:2,\install\yaboot done !
Re: Power Mac G5: Attempting to get 2D acceleration with nouveau and 6800 Ultra
Hi Rick,
On Tue, May 3, 2016 at 12:49 AM, Rick Thomas wrote:
[...]
> Is there a hardware solution? Is there a non-Nvidia graphics card I
> could purchase and install in my PowerMac-G5 11,2 that wouldn’t have the
> problem? I don’t need anything fancy. Just enough to run a simple 2D
> mate or xfce desktop.
My Mac Mini G4 has a RV280 GPU ("Radeon 9200"), so I know this -somewhat- works.
Re: Power Mac G5: Attempting to get 2D acceleration with nouveau and 6800 Ultra
On Mon, May 9, 2016 at 8:44 AM, Rick Thomas wrote: > > On May 8, 2016, at 11:06 PM, Mathieu Malaterre wrote: > >> Hi Rick, >> >> On Tue, May 3, 2016 at 12:49 AM, Rick Thomas wrote: >> [...] >>> Is there a hardware solution? Is there a non-Nvidia graphics card I >>> could purchase and install in my PowerMac-G5 11,2 that wouldn’t have the >>> problem? I don’t need anything fancy. Just enough to run a simple 2D >>> mate or xfce desktop. >> >> My Mac Mini G4 has a RV280 GPU (“Radeon 9200"), so I know this -somewhat- >> works. > > Thanks… That’s good to know. > > But does it work in a G5 64-bit machine? > > If I understand correctly, that’s the problem with the Nvidia boards — the > nouveau driver doesn’t work in a 64-bit environment with the huge page option > that is native to that environment. So Peter’s software change configures it > to use the smaller page size which is native to the 32-bit environment, but > available for backwards compatibility in the 64-bit environment as well… > > Please correct me if I’ve got it wrong. The above is correct. If you want to stick with your actual nvidia graphics cards (until the bug is fixed upstream in nouveau), you are required to rebuild your kernel and change the setting for PPC_64K_PAGES. refs: https://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage https://www.debian.org/releases/stable/powerpc/ch08s06.html.en https://debian-handbook.info/browse/stable/sect.kernel-compilation.html
Debian Installer Stretch Alpha 6 release
Hi there, Has anyone tried the newly release d-i on ppc32 ? Here is what I am seeing over here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825110#15
GRUB in place of YABOOT
Hi there, Could someone please share the steps needed during an `expert32` d-i to have grub be the default loader in place of yaboot ? Thanks,
Re: GRUB in place of YABOOT
On Tue, May 24, 2016 at 9:28 AM, Mathieu Malaterre wrote: > Hi there, > > Could someone please share the steps needed during an `expert32` d-i > to have grub be the default loader in place of yaboot ? So far I've been able to find that: - I need to create a /boot/grub partition (yes: '/boot/grub' you have to enter it manually) during disk setup. - Go back to main menu - A GRUB entry is now available, I did select it - It return promply without any message, nothing is available in `dmesg` Upon reboot, yaboot is still the default loader. What's missing here ? Thanks,
Re: GRUB in place of YABOOT
On Wed, May 25, 2016 at 7:34 AM, Mathieu Malaterre wrote: > On Tue, May 24, 2016 at 9:28 AM, Mathieu Malaterre wrote: >> Hi there, >> >> Could someone please share the steps needed during an `expert32` d-i >> to have grub be the default loader in place of yaboot ? > > So far I've been able to find that: > > - I need to create a /boot/grub partition (yes: '/boot/grub' you have > to enter it manually) during disk setup. > - Go back to main menu > - A GRUB entry is now available, I did select it > - It return promply without any message, nothing is available in `dmesg` > > Upon reboot, yaboot is still the default loader. What's missing here ? If I understand correctly, this trick only works on CHRP IBM machines. The missing parts for PowerMac are: https://bugs.debian.org/691207 & https://bugs.debian.org/691209
Re: No GUI after install of Debian 8.4.0 PowerPC
Hi, On Mon, May 30, 2016 at 2:33 AM, Programmingkid wrote: > > I installed Debian 8.4.0 PowerPC onto an iMac G5. When I tried using Debian, I only saw a command-line interface. startx didn't start the GUI. I did see an error message when I tried using startx, but it went away too quickly for me to read. This is the name of the install cd I used: debian-8.4.0-powerpc-kde-CD-1.iso. > > What I expected was KDE to appear on startup. > > This is my Mac: http://www.everymac.com/systems/apple/imac/specs/imac_g5_2.0_17.html Sorry to hear about your troubles. The simplest way to report this kind of issue is to follow one of the last section of the install guide: https://www.debian.org/releases/stable/powerpc/ch05s04.html.fr#submit-bug Please do carefully review those steps. Since you have a gmail account, you should be able to follow this simple guide [*] to have 'reportbug' up and running in no time. Once you've reported your bug against 'installation-report', please send us the bug number. Thanks [*] https://wiki.debian.org/reportbug#Using_GMail.27s_SMTP_Server
Re: No GUI after install of Debian 8.4.0 PowerPC
On Mon, May 30, 2016 at 8:25 AM, Mathieu Malaterre wrote: > > Hi, > > > On Mon, May 30, 2016 at 2:33 AM, Programmingkid wrote: > > > > I installed Debian 8.4.0 PowerPC onto an iMac G5. When I tried using Debian, I only saw a command-line interface. startx didn't start the GUI. I did see an error message when I tried using startx, but it went away too quickly for me to read. This is the name of the install cd I used: debian-8.4.0-powerpc-kde-CD-1.iso. > > > > What I expected was KDE to appear on startup. > > > > This is my Mac: http://www.everymac.com/systems/apple/imac/specs/imac_g5_2.0_17.html > > > Sorry to hear about your troubles. The simplest way to report this kind of issue is to follow one of the last section of the install guide: > > https://www.debian.org/releases/stable/powerpc/ch05s04.html.fr#submit-bug Hum, meant to copy/paste: https://www.debian.org/releases/stable/powerpc/ch05s04.html.en#submit-bug > > > > Please do carefully review those steps. Since you have a gmail account, you should be able to follow this simple guide [*] to have 'reportbug' up and running in no time. Once you've reported your bug against 'installation-report', please send us the bug number. > > Thanks > > [*] https://wiki.debian.org/reportbug#Using_GMail.27s_SMTP_Server
Re: No GUI after install of Debian 8.4.0 PowerPC
On Mon, May 30, 2016 at 4:34 PM, Programmingkid wrote: > > > On May 30, 2016, at 2:27 AM, Mathieu Malaterre wrote: > > > > > > > On Mon, May 30, 2016 at 8:25 AM, Mathieu Malaterre wrote: > > > > > > Hi, > > > > > > > > > On Mon, May 30, 2016 at 2:33 AM, Programmingkid < programmingk...@gmail.com> wrote: > > > > > > > > I installed Debian 8.4.0 PowerPC onto an iMac G5. When I tried using Debian, I only saw a command-line interface. startx didn't start the GUI. I did see an error message when I tried using startx, but it went away too quickly for me to read. This is the name of the install cd I used: debian-8.4.0-powerpc-kde-CD-1.iso. > > > > > > > > What I expected was KDE to appear on startup. > > > > > > > > This is my Mac: http://www.everymac.com/systems/apple/imac/specs/imac_g5_2.0_17.html > > > > > > > > > Sorry to hear about your troubles. The simplest way to report this kind of issue is to follow one of the last section of the install guide: > > > > > > https://www.debian.org/releases/stable/powerpc/ch05s04.html.fr#submit-bug > > > > Hum, meant to copy/paste: > > https://www.debian.org/releases/stable/powerpc/ch05s04.html.en#submit-bug > > > > > > > > > > > > Please do carefully review those steps. Since you have a gmail account, you should be able to follow this simple guide [*] to have 'reportbug' up and running in no time. Once you've reported your bug against 'installation-report', please send us the bug number. > > > > > > Thanks > > > > > > [*] https://wiki.debian.org/reportbug#Using_GMail.27s_SMTP_Server > > > Here is the bug number: 825835 Hum, sorry :( Looks like this did not do what I expected. Please run "/usr/share/bug/xorg/script 3>/tmp/script.log" and attached it to this bug report.
Re: Re: Power Mac G5: Attempting to get 2D acceleration with nouveau and 6800 Ultra
On Fri, May 27, 2016 at 10:25 PM, Richard Kuenz wrote: > Hello , > > i am on a fresh install of Debian Wheezy kernel 3.2 on Powermac G5 Dual > (model 7,3) with Radeon 9600XT - very nice. > > atm i am compiling Mpv player > > Can someone please give me a hint how to enable sound on this machine? Did you check this page: https://wiki.debian.org/PowerPC/SoundCards
Re: Power Mac G5: Attempting to get 2D acceleration with nouveau and 6800 Ultra
Hi, Glad to hear sound is working for you now. Did you check you had actually hardware accelerated setup ? You need to check the output of glxinfo (cant remember if there is any other easy way). I was also considering installing kodi on my Mac Mini G4, but it seems the Debian package only allow the GUI installation not a headless one using the framebuffer. -M On Tue, May 31, 2016 at 11:49 AM, Richard Kuenz wrote: > thanks, > > i was able to run sound on the powerpc. > > what helped me was this here > > https://wiki.ubuntu.com/PowerPCFAQ > > section "why do i have no sound" > > > i run > sudo rm /etc/modprobe.d/blacklist.local.conf > > than sudo nano /etc/modules > > > and activate >> >> snd-aoa-i2sbus > > > uncommenting snd_powermac > > and other snd- > > > but, > > graphic is so slow with 9600 xt 128 mb that i am not able to run kodi > decently which is strange. > > i am wondering if it would be better with ultra 6800 dual. > > cheers > > > On 31.05.2016 09:03, Mathieu Malaterre wrote: >> >> On Fri, May 27, 2016 at 10:25 PM, Richard Kuenz >> wrote: >>> >>> Hello , >>> >>> i am on a fresh install of Debian Wheezy kernel 3.2 on Powermac G5 Dual >>> (model 7,3) with Radeon 9600XT - very nice. >>> >>> atm i am compiling Mpv player >>> >>> Can someone please give me a hint how to enable sound on this machine? >> >> >> Did you check this page: >> >> https://wiki.debian.org/PowerPC/SoundCards
Re: Bug#825110: ppc64 patch for yaboot FTBFS and e2fslibs1.41-dev
unarchive 322540 reopen 322540 1.3.17-3 tags 322540 patch thanks On Mon, Jun 6, 2016 at 6:57 PM, Lennart Sorensen wrote: > On Tue, May 31, 2016 at 09:17:20AM -0400, wrote: >> On Tue, May 31, 2016 at 02:07:31PM +0200, Mathieu Malaterre wrote: >> > I understand your point for ppc64el, but since `yaboot` gets build on >> > ppc64, some users may break their systems... >> >> According to buildd, it fails to build on ppc64 (not surprising since >> it requires 32bit static libraries to link). yaboot does not currently >> exist in the archive for anything other than 32bit powerpc. So there >> is no reason for it to even attempt to build on 64bit. > > Well in case anyone wants to try and fix it, these patches seem to fix > yaboot build on ppc64: > > diff -urN yaboot-1.3.17.orig/debian/control yaboot-1.3.17/debian/control > --- yaboot-1.3.17.orig/debian/control 2015-11-02 02:54:41.0 + > +++ yaboot-1.3.17/debian/control2016-06-06 15:36:46.0 + > @@ -3,7 +3,7 @@ > Priority: important > Maintainer: Debootloaders Yaboot Maintainers Team > > Uploaders: Aurélien GÉRÔME , Milan Kupcevic > > -Build-Depends: debhelper (>= 9), e2fslibs1.41-dev > +Build-Depends: debhelper (>= 9), e2fslibs1.41-dev, libc6-dev-powerpc [ppc64] > Standards-Version: 3.9.6 > Homepage: http://yaboot.ozlabs.org > > > diff -urN e2fsprogs1.41-1.41.14.orig/debian/rules > e2fsprogs1.41-1.41.14/debian/rules > --- e2fsprogs1.41-1.41.14.orig/debian/rules 2015-11-02 02:20:29.0 > + > +++ e2fsprogs1.41-1.41.14/debian/rules 2016-06-06 15:56:42.0 + > @@ -4,6 +4,7 @@ > > export DEB_BUILD_MAINT_OPTIONS=hardening=-stackprotector > export DEB_CFLAGS_MAINT_APPEND=-fgnu89-inline -fno-builtin-malloc > +export CC:=$(CC) -m32 > > %: > dh $@ --with autotools-dev > @@ -11,10 +12,18 @@ > override_dh_auto_install: > dh_auto_install --destdir=debian/tmp -- install-libs > > +override_dh_auto_build: > + dh_auto_build -- libs > + > override_dh_auto_clean: > dh_auto_clean > rm -f asm_types.h public_config.h > > +override_dh_auto_test: > + > +override_dh_auto_configure: > + dh_auto_configure -- --host=powerpc-linux-gnu > --target=powerpc-linux-gnu > + > get-orig-source: > wget > http://downloads.sourceforge.net/project/e2fsprogs/e2fsprogs/1.41.14/e2fsprogs-1.41.14.tar.gz > \ > -O e2fsprogs1.41_1.41.14.orig.tar.gz > > The fix is that since yaboot is always built 32bit, then on ppc64 we > better build-dep on the 32bit libc headers and stuff, and when building > the e2fslibs it has to be built 32bit, not 64bit, since yaboot is the > only user and it is building 32bit. While at it I made it stop building > all the other crap that wasn't actually being packaged since it was > taking too long to build. > > I am not entirely pleased with the CC variable as a way to pass the > -m32 needed, but it seems to work. Maybe someone can see a cleaner way > (maybe the configure command somehow) to do that. > > I would have sent this to bug 322540 since that is the ppc64 yaboot > bug, but for some reason it is closed and archived even though it never > actually worked and was never actually built on ppc64. That seems like > a mistake. Fixed ! I do not believe using #825110 make sense. Thanks for the patch !
Misc PowerPC News
I've been playing a bit with BTS lately and I have setup powerpc & ppc64 tags on a few outstanding bugs related to PowerPC arch: http://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=powerpc&user=debian-powerpc%40lists.debian.org http://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=ppc64&user=debian-powerpc%40lists.debian.org Here is a summary of some outstanding issues that have either been solved or are being worked on: 1. mono (http://bugs.debian.org/819711) The issue with mono on PowerPC (and ppc64!) has been found and reported upstream. I'll keep an eye on the package to check that mono on PowerPC comes back in Debian. 2. yaboot 1.3.17 (http://bugs.debian.org/819549) Thanks to Milan Kupcevic we finally have yaboot 1.3.17 in Debian ! There is still an issue with PPC64 build but a patch has been provided by Lennart Sorensen (http://bugs.debian.org/322540). 3. partman-ext3 (http://bugs.debian.org/825110) Debian Installer Stretch Alpha 6 release is currently broken as described in the bug report. But Milan Kupcevic managed to provide a work around. I've not tested but the daily installer should work, use it instead. 4. OFfb red / blue color inversion (http://bugs.debian.org/825840) Currently when using d-i the text based installation display inverted colors. I am currently tracking down why this is happening and if it possible to directly fix OFfb. There are alternatives describe in this bug tracker to fix the symptoms, namely to use radeon(fb) in place of OFfb. So d-i on PowerPC may not only be suited for color blind people after all :-) 5. partman-auto (http://bugs.debian.org/610206) By default yaboot is the bootloader on PowerPC. But there is a secret option in d-i to install grub-ieee1275 on CHRP IBM machines. I am trying to make that also an option for NewWorld Mac machines, one patch at a time. 6. r300: Visuals not found in (default) depth = 24 (http://bugs.debian.org/746272) Users of the r300 driver needed to use an old patch (http://wiki.debian.org/PowerPC/FAQ#How_do_I_get_graphics_working.3F) to get the default depth working. This has now been fixed upstream and will be part of the next mesa release. 7. No sound on PowerPC with Jessie upgrade (http://bugs.debian.org/714345) There were actually two different issues that prevented some users to have sound working. They have both been solved by Wolfram Sang (http://bugs.debian.org/714345#120 & http://bugs.debian.org/714345#161). The first one is already in linux 4.5.5, and the last patch has been tagged for stable release in linux. -M
Re: old G5 iMac with NVIDIA card
Hi Steven, On Wed, Jun 8, 2016 at 9:24 PM, Lennart Sorensen wrote: > On Wed, Jun 08, 2016 at 12:13:35PM -0400, Steven Grunza wrote: >> Does anyone know if the nouveau driver will work with an old G5 PowerPC and >> the GeForce FX G05200 it originally used? >> >> The last time I tried it had numerous problems (no graphics, kernel panics, >> etc). >> >> lsusb reports the video card as: >> >> NVIDIA Corporation NV34M [GeForce FX Go5200] (rev a1) >> >> >> Various versions of jessie failed in various ways. Does Stretch have a >> different version of the nouveau driver? Since the machine is PowerPC I >> can't use the NVIDIA driver. > > my understanding is that it does NOT work with a 64bit kernel with a > page size other than 4K, which means the kernel currently in Debian does > not work. Someone has posted a link on the list to a kernel built with > 4K pages that is supposed to work. > > I think that is the current state of things. That's correct. You'll need to recompile your kernel and change the option PPC_64K_PAGES: https://lists.debian.org/debian-powerpc/2016/05/msg8.html ATI card should work out of the box. Please note that GNOME/KDE may have other restrictions, so I would suggest you use MATE and/or XFCE instead. -M
Re: old G5 iMac with NVIDIA card
On Thu, Jun 9, 2016 at 4:16 PM, Elimar Riesebieter wrote: > * Steven Grunza [2016-06-09 09:45 -0400]: > > [...] >> so it's not using the vesa driver >> >> Must be using the intel driver (which makes sense since this is an i7 >> laptop). > > $ cat /proc/fb > > shows you the framebuffer driver in use which corresponds to the X > driver. Nice trick ! I would have used something more like: $ lspci -vvx -s $(lspci | grep VGA | cut -f1 -d' ') | grep module
Re: iMac G3 Snow 600MHz
On Thu, Jun 9, 2016 at 10:42 PM, Alex Santos wrote: > Hello > > I have an iMac G3 Snow 600MHz with a CDR. I would like to install some kind > of Unix variant with a GUI. Can someone recommend a starting point. You could try to install Debian with XFCE. -M
Re: old G5 iMac with NVIDIA card
Michel, On Fri, Jun 10, 2016 at 4:03 AM, Michel Dänzer wrote: > On 10.06.2016 05:44, Programmingkid wrote: >> I have a ATI Radeon 9600 and it has problems. Debian disappointedly >> booted to a command prompt after installing it. Startx also failed to >> load the GUI. This news about making a kernel that supports 4k pages >> might be a solution. > > The radeon driver doesn't have trouble with non-4K page size, only the > nouveau driver does. Could you have a quick look at OP report, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825835#15 All I could find was a : [...] [48.943] (II) SELinux: Disabled on system [48.947] (II) AIGLX: Screen 0 is not DRI2 capable [48.947] (EE) AIGLX: reverting to software rendering [49.219] (II) AIGLX: Loaded and initialized swrast [...] Thanks for suggestion (or should I fill a bug report upstream). Thx
Re: old G5 iMac with NVIDIA card
Dear Programmingkind, On Fri, Jun 10, 2016 at 9:39 AM, Michel Dänzer wrote: > On 10.06.2016 15:45, Mathieu Malaterre wrote: >> Michel, >> >> On Fri, Jun 10, 2016 at 4:03 AM, Michel Dänzer wrote: >>> On 10.06.2016 05:44, Programmingkid wrote: >>>> I have a ATI Radeon 9600 and it has problems. Debian disappointedly >>>> booted to a command prompt after installing it. Startx also failed to >>>> load the GUI. This news about making a kernel that supports 4k pages >>>> might be a solution. >>> >>> The radeon driver doesn't have trouble with non-4K page size, only the >>> nouveau driver does. >> >> Could you have a quick look at OP report, see: >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825835#15 > > [48.519] (II) RADEON(0): GPU accel disabled or not working, using > shadowfb for KMS > > => check dmesg: > > [ 14.772580] [drm:r100_cp_init] *ERROR* Failed to load firmware! > > Hardware acceleration requires the firmware-amd-graphics / > firmware-linux-nonfree package to be installed. Could you please re-run "/usr/share/bug/xorg/script 3>/tmp/script.log" and attached it again to this bug report, now that you installed the firmware: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825835#25 -M
Re: old G5 iMac with NVIDIA card
On Fri, Jun 10, 2016 at 10:36 AM, Programmingkid wrote: > > On Jun 10, 2016, at 3:42 AM, Mathieu Malaterre wrote: > >> Dear Programmingkind, >> >> On Fri, Jun 10, 2016 at 9:39 AM, Michel Dänzer wrote: >>> On 10.06.2016 15:45, Mathieu Malaterre wrote: >>>> Michel, >>>> >>>> On Fri, Jun 10, 2016 at 4:03 AM, Michel Dänzer wrote: >>>>> On 10.06.2016 05:44, Programmingkid wrote: >>>>>> I have a ATI Radeon 9600 and it has problems. Debian disappointedly >>>>>> booted to a command prompt after installing it. Startx also failed to >>>>>> load the GUI. This news about making a kernel that supports 4k pages >>>>>> might be a solution. >>>>> >>>>> The radeon driver doesn't have trouble with non-4K page size, only the >>>>> nouveau driver does. >>>> >>>> Could you have a quick look at OP report, see: >>>> >>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825835#15 >>> >>> [48.519] (II) RADEON(0): GPU accel disabled or not working, using >>> shadowfb for KMS >>> >>> => check dmesg: >>> >>> [ 14.772580] [drm:r100_cp_init] *ERROR* Failed to load firmware! >>> >>> Hardware acceleration requires the firmware-amd-graphics / >>> firmware-linux-nonfree package to be installed. >> >> Could you please re-run "/usr/share/bug/xorg/script 3>/tmp/script.log" >> and attached >> it again to this bug report, now that you installed the firmware: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825835#25 > > I will have to reinstall Debian. I used the kde version of the iso file. Did > you want me to try this iso again, or did you have another iso in mind? If > you do please send me the iso's URL. Thanks. You need to re-run this script from the environment you used the last time you did it. Maybe it was KDE, if so just redo it. The logs have been generated before you installed the firmware, I need them now that you installed the firmware. Thx! -M
Re: Airport gone
On Fri, Jun 10, 2016 at 12:51 AM, Riccardo Mottola wrote: > Hi, > > as I wrote a little while ago, I had issues with Airport on my iBook G3. > Now I installed several updates, including kernel and others... I reboot and > notice that I have no airport at all! Did you keep your older kernel around ? If so could you please reboot using an older kernel, and report back if Airport can be seen or not. Thanks
Re: Airport gone
On Fri, Jun 10, 2016 at 7:53 PM, Riccardo Mottola wrote: > Hi, > > Karoly Balogh (Charlie/SGR) wrote: >> >> Unlikely, however i had an iBook G3, and its Airport was a bit >> intermittent, so it's possible there is a (fixable) HW problem. Just a >> guess. > > luckily booting an older kernel proves that it works. I never had issues, > although this thing is getting a bit old, but I am fond of it! > What issues? connector soldering issues' Overheating? So what does lspci shows now ?
Re: Airport gone
On Fri, Jun 10, 2016 at 8:07 PM, Riccardo Mottola wrote: > Hi, > > Mathieu Malaterre wrote: >>> >>> luckily booting an older kernel proves that it works. I never had issues, >>> >although this thing is getting a bit old, but I am fond of it! >>> >What issues? connector soldering issues' Overheating? >> >> So what does lspci shows now ? >> > as I wrote in the other message, the interface comes up, is reported by > iwconfig/ifconfig and dmesg with the older kernel. > But, as Karoly supposed, lspci doesn't show it: Could you try then: # lshw -class network Thanks
Re: Airport gone
On Fri, Jun 10, 2016 at 8:19 PM, Riccardo Mottola
wrote:
> Hi,
>
> sure! I had to install lshw.
>
> Mathieu Malaterre wrote:
>>
>> Could you try then:
>>
>> # lshw -class network
>
>
> On the kernel that works I see this:
[...]
> *-network
>description: Wireless interface
>physical id: 1
>logical name: eth0
>serial: 00:30:65:0c:ba:d1
>capabilities: ethernet physical wireless
>configuration: broadcast=yes driver=airport ip=192.168.1.156
> multicast=yes wireless=IEEE 802.11b
Ok, then copy/paste:
$ find /lib/modules/ -name airport.ko -exec /sbin/modinfo {} \;
and sent it back. thx
Re: Airport gone
On Fri, Jun 10, 2016 at 8:21 PM, Lennart Sorensen wrote: > On Fri, Jun 10, 2016 at 07:57:17PM +0200, Mathieu Malaterre wrote: >> So what does lspci shows now ? > > It is NOT a PCI device. It is a localbus device. Sorry. How does one list those ? Thx
Re: Airport gone
Wolfram,
Could you please double check the following output from modinfo and
confirm this is the same issue as Debian #714345
On Fri, Jun 10, 2016 at 8:25 PM, Riccardo Mottola
wrote:
> Hi Mathieu,
>
> Mathieu Malaterre wrote:
>>
>> Ok, then copy/paste:
>>
>> $ find/lib/modules/ -name airport.ko -exec /sbin/modinfo {} \;
>>
>> and sent it back. thx
>
> filename:
> /lib/modules/4.0.0-2-powerpc/kernel/drivers/net/wireless/orinoco/airport.ko
> license:Dual MPL/GPL
> description:Driver for the Apple Airport wireless card.
> author: Benjamin Herrenschmidt
> alias: of:NradioT*C*
> depends:orinoco
> intree: Y
> vermagic: 4.0.0-2-powerpc mod_unload modversions
> filename:
> /lib/modules/4.1.0-2-powerpc/kernel/drivers/net/wireless/orinoco/airport.ko
> license:Dual MPL/GPL
> description:Driver for the Apple Airport wireless card.
> author: Benjamin Herrenschmidt
> alias: of:NradioT*C*
> depends:orinoco
> intree: Y
> vermagic: 4.1.0-2-powerpc mod_unload modversions
> filename:
> /lib/modules/4.3.0-1-powerpc/kernel/drivers/net/wireless/orinoco/airport.ko
> license:Dual MPL/GPL
> description:Driver for the Apple Airport wireless card.
> author: Benjamin Herrenschmidt
> alias: of:NradioT*C*
> depends:orinoco
> intree: Y
> vermagic: 4.3.0-1-powerpc mod_unload modversions
> filename:
> /lib/modules/4.4.0-1-powerpc/kernel/drivers/net/wireless/orinoco/airport.ko
> license:Dual MPL/GPL
> description:Driver for the Apple Airport wireless card.
> author: Benjamin Herrenschmidt
> alias: of:NradioT*C*
> depends:orinoco
> intree: Y
> vermagic: 4.4.0-1-powerpc mod_unload modversions
> filename:
> /lib/modules/4.5.0-2-powerpc/kernel/drivers/net/wireless/intersil/orinoco/airport.ko
> license:Dual MPL/GPL
> description:Driver for the Apple Airport wireless card.
> author: Benjamin Herrenschmidt
> alias: of:NradioT*CC*
> alias: of:NradioT*C
> depends:orinoco
> intree: Y
> vermagic: 4.5.0-2-powerpc mod_unload modversions
Regards.
Re: Bug#714345: Airport gone
On Fri, Jun 10, 2016 at 8:43 PM, Lennart Sorensen wrote: > On Fri, Jun 10, 2016 at 08:28:12PM +0200, Mathieu Malaterre wrote: >> Wolfram, >> >> Could you please double check the following output from modinfo and >> confirm this is the same issue as Debian #714345 > > Well if it is, then manually doing: > modprobe airport Correct > should detect the wifi on the new kernel. > > It also means the 4.6 kernel in unstable ought to work automatically > again. Actually there are two issues in #714345, the last one which I suspect (trailing 'C' in alias) has still not been merged ([GIT PULL] Please pull powerpc/linux.git powerpc-4.7-3 tag)
Re: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly
On Fri, Jun 3, 2016 at 5:29 PM, Wolfram Sang wrote: > On Tue, Apr 12, 2016 at 12:08:03PM +0200, Mathieu Malaterre wrote: >> Dear all, >> >> I am looking for testers for the following patch: >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741663#20 >> >> Wolfram (CC here) is looking for feedback from users for this patch. > > For completeness, it should be one of those machines: > > https://en.wikipedia.org/wiki/Power_Mac_G4#Wind_Tunnel > As Gilles discovered the concerned MDD models are the following: http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_867_dp_mdd.html http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_1.0_dp_mdd.html http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_1.25_dp_mdd.html some people have older PowerPC + SMP machine such as: http://www.everymac.com/systems/apple/powermac_g4/specs/powermac_g4_450_dp.html but they are not concerned with this patch. Sorry for the confusion everybody, thanks to Gilles for the update. -M
Re: [Stretch] Status for architecture qualification
Hi Hector, On Thu, Jun 16, 2016 at 2:12 AM, Hector Oron wrote: [...] > While working out ArchitectureQualification/Stretch wiki page I > believe everything is mostly fine for release, however I got a > personal concern on powerpc architecture. Is it well maintained? Does > it have porters? Does it have users? Does it still make sense to carry > along? [...] The debian-powerpc@l.d.o mailing list is active so I would say it still has some users. I have been using partch.d.o for doing some work on PowerPC. I posted a summary of work people have been doing on this port lately: https://lists.debian.org/debian-powerpc/2016/06/msg00046.html However I do agree that true PowerPC hardware is actually disappearing, and it is alive mostly thanks to being an ABI using 32bits integer for PPC64 CPU(s). -M
Re: Debian "Jessie" on Apple eMac 1.25 GHz PowerPC G4 (7447A) with ATI Radeon 9200 gives "Black Screen of Death"
Hi Francesco, On Fri, Jun 17, 2016 at 9:30 AM, aggaz wrote: > Dear list, > > I have an Apple eMac 1.25 GHz PowerPC G4 (7447A) with ATI Radeon 9200. > > For several years I used Debian "Wheezy" on it without issues. > > Some day ago I upgraded to "Jessie" and graphics stopped working. > > I also tried to make a fresh install of Jessie that later I upgraded to > "testing", but I always have the same problem. > > The problem is that after boot I have the so called "Black Screen of > Death", which means that the monitor goes black and this is not related > to Xorg, in fact I can not even see a shell prompt. > > I read everithing I could to fix it. > > I my understanding the problem is that new radeon drivers require KMS > but KMS is for some reason not compatible with my machine. > > The only way to have an almost working screen is to disable radeon-kms > either by adding to yaboot.conf the line: > > append="nomodeset" > > or in /etc/modprobe.d/radeon-kms.conf the line: > > options radeon modeset=0 > > In both cases, I get a working console, but a messed up X. > > I see weird colors and X is ot usable. > > Now I read that I could fix it as described here by disabling > open-firmware frame-buffer and using the driver fbdev, which is slow. > > So, my solution is to go back to wheezy. > > My questions: > > 1. Am I missing something? Is there a way to use Jessie with radeon drivers? Sorry to hear your trouble. Just to put things in order, when you say "I get a working console", could you please dump the output of: $ cat /proc/fb to your email. Also for real complete bug report you could run "/usr/share/bug/xorg/script 3>/tmp/script.log" and attach it here. Finally what is the status of the firmware, just send: $ apt-cache policy firmware-linux-nonfree > 2. Where can I find a downloadable iso for Debian Wheezy PPC? It seems I > can download only "Jessie" and testing. https://www.debian.org/releases/wheezy/debian-installer/ -M
Re: Radeon driver not works on PPC with X800
On Thu, Jun 16, 2016 at 1:15 AM, TCH wrote: > Hi! > > I have an old G4 MDD, with an X800 card. I've just installed Debian Jessie > and tried to breathe life into the 2d acceleration, but without success. If > i install "firmware-linux-nonfree", then it loads the "r420_cp.bin", but > then i only got a black screen after boot and the machine freezes > completely. Sorry to hear your troubles. Really in a case of complete installation, I would like to invite you to report a proper bug report: https://www.debian.org/releases/jessie/powerpc/ch05s04.html.en#submit-bug If you have never configured an MTA before, you can simply configure reportbug using the simple gmail example: https://wiki.debian.org/reportbug#Using_GMail.27s_SMTP_Server Let us know the bug number. -M
Re: Radeon driver not works on PPC with X800
[top post sorry] Actually installation report on successful installation are important too. Anyway, if you only want to report the issue with radeon, then do: $ reportbug xserver-xorg-video-radeon HTH On Mon, Jun 20, 2016 at 8:31 PM, TCH wrote: > I would like to send a bugreport, but the linked article is about filing bug > reports about installation problems, which i don't have. Debian 8 installs > perfectly, everything works perfectly, the only exception is the radeon > driver, which is only works, if i don't install the firmware for my card and > thus, forcing the driver to disable the 2D acceleration. > Do you have a template for graphics driver bugreports? > > 2016-06-20 8:54 GMT+02:00 Mathieu Malaterre : >> >> On Thu, Jun 16, 2016 at 1:15 AM, TCH wrote: >> > Hi! >> > >> > I have an old G4 MDD, with an X800 card. I've just installed Debian >> > Jessie >> > and tried to breathe life into the 2d acceleration, but without success. >> > If >> > i install "firmware-linux-nonfree", then it loads the "r420_cp.bin", but >> > then i only got a black screen after boot and the machine freezes >> > completely. >> >> Sorry to hear your troubles. Really in a case of complete >> installation, I would like to invite you to report a proper bug >> report: >> >> https://www.debian.org/releases/jessie/powerpc/ch05s04.html.en#submit-bug >> >> If you have never configured an MTA before, you can simply configure >> reportbug using the simple gmail example: >> >> https://wiki.debian.org/reportbug#Using_GMail.27s_SMTP_Server >> >> Let us know the bug number. >> >> -M > >
maclhw ?
Does anyone knows if any of the flavor: powerpc / ppc64 / ppc64el supports 'maclhw' ? Thanks
give back for ffmpeg on ppc64
It looks like ffmpeg fails to build on ppc64 due to a timeout: https://buildd.debian.org/status/fetch.php?pkg=ffmpeg&arch=ppc64&ver=7%3A3.0.2-4&stamp=1465651053 gb ffmpeg_7:3.0.2-4 . ppc64 comments ?
Re: give back for ffmpeg on ppc64
It does build on pizzetti.d.o as of this morning... On Tue, Jun 21, 2016 at 12:15 PM, luigi burdo wrote: > I was building it without problems > > on fedora 24 PPC 64. > > > Luigi > > > > > Da: mathieu.malate...@gmail.com per conto di > Mathieu Malaterre > Inviato: martedì 21 giugno 2016 12.03 > A: PowerPC List Debian > Oggetto: give back for ffmpeg on ppc64 > > It looks like ffmpeg fails to build on ppc64 due to a timeout: > > https://buildd.debian.org/status/fetch.php?pkg=ffmpeg&arch=ppc64&ver=7%3A3.0.2-4&stamp=1465651053 > > gb ffmpeg_7:3.0.2-4 . ppc64 > > comments ? >
Re: give back for ffmpeg on ppc64
Hi, On Tue, Jun 21, 2016 at 1:57 PM, Hiroyuki Yamamoto wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi, Mathieu, > > Mathieu Malaterre wrote: >> It looks like ffmpeg fails to build on ppc64 due to a timeout: >> >> https://buildd.debian.org/status/fetch.php?pkg=ffmpeg&arch=ppc64&ver=7%3A3.0.2-4&stamp=1465651053 >> >> gb ffmpeg_7:3.0.2-4 . ppc64 >> >> comments ? >> >> > > To be certain, I will give back ffmpeg_7:3.0.2-4 after gcc-6_6.1.1-7 has been > built, > but ffmpeg has failed to build on ppc64 from changing to ver. 3.0 by same > point: > > TESTffprobe_xml > /?PKGBUILDDIR?/tests/fate-run.sh fate-ffprobe_xml "" "" > "/?PKGBUILDDIR?/debian/standard" 'run ffprobe -show_streams -show_packets > -show_format -show_frames -bitexact tests/data/ffprobe-test.nut -of xml' '' > '' '' '1' '' '' '' '' '' '' '' '' > /?PKGBUILDDIR?/debian/standard/ffprobe -show_streams -show_packets > -show_format -show_frames -bitexact tests/data/ffprobe-test.nut -of xml > make[2]: Target 'check' not remade because of errors. > make[2]: Leaving directory '/?PKGBUILDDIR?/debian/standard' > dh_auto_test: make -j1 check -k returned exit code 2 > debian/rules:225: recipe for target 'override_dh_auto_test-arch' failed > make[1]: *** [override_dh_auto_test-arch] Error 2 > make[1]: Leaving directory '/?PKGBUILDDIR?' > debian/rules:185: recipe for target 'build-arch' failed > make: *** [build-arch] Error 2 > dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 Indeed. What are the machine amaterasu and tsukuyomi, do they have altivec ? I cannot reproduce FTBFS on the sole ppc64 porterbox we have: pizzetti.d.o: malat@pizzetti ~ % cat /proc/cpuinfo processor : 0 cpu : POWER8E (raw), altivec supported clock : 3425.00MHz revision : 2.1 (pvr 004b 0201) processor : 1 cpu : POWER8E (raw), altivec supported clock : 3425.00MHz revision : 2.1 (pvr 004b 0201) processor : 2 cpu : POWER8E (raw), altivec supported clock : 3425.00MHz revision : 2.1 (pvr 004b 0201) processor : 3 cpu : POWER8E (raw), altivec supported clock : 3425.00MHz revision : 2.1 (pvr 004b 0201) timebase : 51200 platform : pSeries model : IBM pSeries (emulated by qemu) -M
Re: jpeg-turbo 6.2 and ppc G3
On Mon, Jul 4, 2016 at 6:45 PM, Lennart Sorensen wrote: > On Sat, Jul 02, 2016 at 08:57:56AM +0200, Riccardo Mottola wrote: >> Hi, >> >> any of you still running G3 or anyway a non-altivec computer? >> >> I noticed that using GS applications (compiled from source, not debian >> packages) I am unable to open JPEG files, I get an Illegal instruction. >> >> (gdb) bt >> #0 0x0d243b68 in ?? () from /usr/lib/powerpc-linux-gnu/libjpeg.so.62 >> #1 0x0d243b40 in ?? () from /usr/lib/powerpc-linux-gnu/libjpeg.so.62 >> #2 0x0d23a3c4 in ?? () from /usr/lib/powerpc-linux-gnu/libjpeg.so.62 >> #3 0x0d21c550 in ?? () from /usr/lib/powerpc-linux-gnu/libjpeg.so.62 >> #4 0x0d2220a0 in ?? () from /usr/lib/powerpc-linux-gnu/libjpeg.so.62 >> #5 0x0d21a6bc in jpeg_read_scanlines () from >> /usr/lib/powerpc-linux-gnu/libjpeg.so.62 >> #6 0x0fbbae30 in -[NSBitmapImageRep(JPEGReading) >> _initBitmapFromJPEG:errorMessage:] (self=0x1040fe78, _cmd=, >> imageData=0x1028e678, errorMsg=0x0) at NSBitmapImageRep+JPEG.m:462 >> #7 0x0fbb3cfc in +[NSBitmapImageRep imageRepsWithData:] (self=> out>, _cmd=, imageData=0x1028e678) >> at NSBitmapImageRep.m:223 >> >> The GS code is quite well tested on many platforms and hasn't chaged >> recently, so I want to be reassured that jpegturbo works also on PPC without >> altivec or anyway works. > > I would think libjpeg-turbo-progs would have something small in it you > could test with. > >> I what test program could I use? I noticed that e.g. Firefox (which works) >> is not linked against it. > > You could try forcing altivec off in libjpegturbo by setting the environment: > > export JSIMD_FORCENONE=1 Neat ! > If that helps, then something is wrong with the runtime detection code. > It appears it is supposed to detect if the CPU supports altivec at > runtime and only use it if it is there. Could be using: __builtin_cpu_supports (see https://bugs.debian.org/826987) -M
Re: jpeg-turbo 6.2 and ppc G3
On Tue, Jul 5, 2016 at 9:01 PM, Lennart Sorensen
wrote:
> On Tue, Jul 05, 2016 at 07:46:10PM +0200, Riccardo Mottola wrote:
>> Hi Lennart,
>>
>> Lennart Sorensen wrote:
>> >On Sat, Jul 02, 2016 at 08:57:56AM +0200, Riccardo Mottola wrote:
>> >>I what test program could I use? I noticed that e.g. Firefox (which works)
>> >>is not linked against it.
>> >You could try forcing altivec off in libjpegturbo by setting the
>> >environment:
>> >
>> >export JSIMD_FORCENONE=1
>>
>> that works! Once set, the application loads several JPG files without
>> issues.
>
> So it turns out libjpeg-turbo has NO runtime detection on powerpc and
> just assumes altivec is valid.
>
> This untested patch might work:
>
> --- simd/jsimd_powerpc.c.orig 2016-07-05 14:57:48.305763762 -0400
> +++ simd/jsimd_powerpc.c2016-07-05 14:58:04.453763762 -0400
> @@ -32,7 +32,10 @@
>if (simd_support != ~0U)
> return;
>
> - simd_support = JSIMD_ALTIVEC;
> + if (__builtin_cpu_supports("altivec"))
> +simd_support = JSIMD_ALTIVEC;
> + else
> +simd_support = 0;
>
>/* Force different settings through environment variables */
>env = getenv("JSIMD_FORCENONE");
Well it does not work -yet- at least on ppc32 with gcc 6.1.1:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71777
But I would report the bug anyway to libjpegturbo. Riccardo, could you do that?
thx
Re: yaboot 1.3.17 broken
Hi, On Mon, Aug 15, 2016 at 10:23 AM, Herminio Hernandez, Jr. wrote: > I found a solution if anyone else runs into this. During the install process > create a separate /boot partition and format it as ext2. Hum, this really looks like #825110. Could you please be a little bit more specific and tell us the iso image you used. In particular could you please check the partman-ext3 package version. Thanks.
powerpcspe: Not enough room for program headers,
Sebastiaan, On Fri, Aug 26, 2016 at 3:31 PM, Christian Seiler wrote: > Hi, > > I recently uploaded a new version of open-iscsi to sid. It failed to build > on powerpcspe: > https://buildd.debian.org/status/fetch.php?pkg=open-iscsi&arch=powerpcspe&ver=2.0.873%2Bgit1.4c1f2d90-2&stamp=1472216616 > > Funny thing though: the binary that dh_strip tries to process shouldn't have > changed between -1 and -2, and the former built without problems. (And the > binary builds, it's dh_strip that fails. Also, build on powerpc works, plus > open-iscsi doesn't use the FPU heavily.) > > The error message >> Not enough room for program headers, try linking with -N > seems especially weird, as dh_strip calls objcopy, not ld. (And I could only > find information about that message in the context of ld from over a decade > ago.) Could you please share any information you have on this error ? I see you had it at some point: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835170#17 Thanks in advance
Re: PowerPC agpmode issues
Hi, On Mon, Sep 19, 2016 at 11:13 AM, Herminio Hernandez, Jr. wrote: > Apologies for the previous email. > > What I was trying to say was I just recently installed Debain on my PowerMac > G5. I upgraded to sid and install the nonfree firmware. After reboot I > noticed that GPU acclleration was broken and I recieved the following error > > [ 10.428542] [drm] Loading R300 Microcode > [ 10.486631] radeon :f0:10.0: firmware: direct-loading firmware > radeon/R300_cp.bin > [ 10.486865] [drm] radeon: ring at 0x0001 > [ 10.634417] [drm:.r100_ring_test [radeon]] *ERROR* radeon: ring test > failed (scratch(0x15E4)=0xCAFEDEAD) > [ 10.634526] [drm:.r100_cp_init [radeon]] *ERROR* radeon: cp isn't working [...] > [ 11.935061] [drm] Forcing AGP to PCI mode Well that is really odd. I am trying hard to push my pci patch upstream: https://patchwork.kernel.org/patch/9088181/ I do believe PCI mode always work, so I would be interested if you could report the bug upstream to have PCI mode work on all Powermac (AGP is know to be broken). Pay attention to your /etc/modules file check whether or not it contains a option for the loaded modules, eg: radeon.agpmode=-1 Finally your dmesg looks odd since the line `[drm] Forcing AGP to PCI mode` comes only after the first error. -M
Re: Porter roll call for Debian Stretch
Hi all, On Fri, Sep 23, 2016 at 3:54 PM, Matthias Klose wrote: > On 20.09.2016 23:46, John Paul Adrian Glaubitz wrote: >> On 09/20/2016 11:16 PM, Niels Thykier wrote: >>>- powerpc: No porter (RM blocker) >> >> I'd be happy to pick up powerpc to keep it for Stretch. I'm already >> maintaining powerpcspe which is very similar to powerpc. > > No, you are not maintaining powerpcspe as a release architecture, and that's > something different than building packages for some of the ports > architectures. > If you can get powerpcspe accepted as a release architecture, then maybe you > gain some credibility to maintain another release architecture ;) [Let's assume that we can't find a powerpc porter in time for Stretch.] 1. Will `powperpc` automatically be downgraded to simple port ? Or is this also not automated and the port may simply be removed (eg. sparc) ? 2. Apart from loosing the automatic debian-installer stuff, what else are we going to loose in that scenario ? Thanks much for pointers ! -M
Re: Porter roll call for Debian Stretch
Adrian, On Fri, Sep 30, 2016 at 10:34 PM, John Paul Adrian Glaubitz wrote: [...] > On the other hand, some packages dropped support for PowerPC32 like Mono > but this isn't a concern for most users, I would say. [...] Thanks very much for stepping up as porter, you have my vote ! However I need to mention that the specific ppc/mono issue is in fact pretty interesting. The long thread is on debian-powerpc@l.d.o but the short version is that this issue only happen because we build the ppc32 mono version on a ppc64 kernel, I know that since I did debug this issue. I have not heard from the ppc64el porters, but I suspect ppc64 will not be a release arch. So you need to take into consideration that for powerpc to remain a release arch, one need minimal working ppc64 port. Could we solve the situation of ppc64 for Stretch, could it be moved to official release arch ? -M
Re: Porter roll call for Debian Stretch
On Sat, Oct 1, 2016 at 2:28 AM, Adam Borowski wrote: > On Fri, Sep 30, 2016 at 11:01:55PM +0200, Mathieu Malaterre wrote: >> On Fri, Sep 30, 2016 at 10:34 PM, John Paul Adrian Glaubitz >> wrote: >> [...] >> > On the other hand, some packages dropped support for PowerPC32 like Mono >> > but this isn't a concern for most users, I would say. >> [...] >> >> However I need to mention that the specific ppc/mono issue is in fact >> pretty interesting. The long thread is on debian-powerpc@l.d.o but the >> short version is that this issue only happen because we build the >> ppc32 mono version on a ppc64 kernel, I know that since I did debug >> this issue. > > Which, if I read the bug correctly, is a yet another case of a bogus > build system looking at characteristics of the machine it's compiled on > rather than baseline of the arch. Well the bug is really upstream: one cannot assume page size at compilation time. But that is a different story. > And, per your own work, it's +patch +fixed-upstream. Wow ! In fact I just realize my patch was against git/master at the time, and was never backported. Need to get this fixed ASAP. >> I have not heard from the ppc64el porters, but I suspect ppc64 will >> not be a release arch. So you need to take into consideration that for >> powerpc to remain a release arch, one need minimal working ppc64 port. >> Could we solve the situation of ppc64 for Stretch, could it be moved >> to official release arch ? > > What would you need ppc64 for? Unlike i386, powerpc includes 64-bit > kernels so users don't need multiarch: > > powerpc has: > linux-image-4.7.0-1-powerpc - Linux 4.7 for uniprocessor 32-bit PowerPC > (signed) > linux-image-4.7.0-1-powerpc-smp - Linux 4.7 for multiprocessor 32-bit PowerPC > (signed) > linux-image-4.7.0-1-powerpc64 - Linux 4.7 for 64-bit PowerPC (signed) > i386 has: > linux-image-4.7.0-1-686-pae-unsigned - Linux 4.7 for modern PCs > linux-image-4.7.0-1-686-unsigned - Linux 4.7 for older PCs > linux-image-4.7.0-1-grsec-686-pae - Linux 4.7 for modern PCs, Grsecurity > protection > linux-image-4.7.0-1-686 - Linux 4.7 for older PCs (signed) > linux-image-4.7.0-1-686-pae - Linux 4.7 for modern PCs (signed) > > Note the joke: "for modern PCs". Unless you do embedded it takes some > serious dumpster diving to find a machine not better served by an -amd64 > kernel (and thus multiarch). The i386 architecture is not self-contained, > powerpc is. > > Thus, there is no need for ppc64 (userland), as long as powerpc has the > toolchain to build 64-bit kernels. And that's a primary target for gcc > upstream. Great ! That's all I wanted to check. I was worried we would need buildd(s) running on ppc64el.
PowerPC roadmap for Stretch
Hi all, Since there has been some fuss about powerpc recently, let's see if I can get some help on issue(s) I'd like to fix for Stretch. If anyone is able to provide help with any of the following, please do contact me ! 1. Secret GRUB option in d-i. This is no suprise that we have a situation with yaboot in powerpc (in particular partman-ext3 #825110). So I would like to finish the initial work to have GRUB be an alternative on PowerMac (famous secret option in d-i). Who can help me finish: - https://bugs.debian.org/610206 (I sent a patch but would appreciate feedback) ? - https://bugs.debian.org/691207 ? - https://bugs.debian.org/691209 ? 2. offb/ATY,RockHopper: inverts red and blue in bterm I have not been able to make progress on https://bugs.debian.org/825840. So if anyone is familar with ioctl/FBIOPUTCMAP, I'd appreciate a little help here. 3. radeonfb should be able to kick out offb In case (2) above cannot be solved in time. We can also fix the color inversion another way. Technically some PowerMac uses a radeon based graphic card, so we could fix the radeonfb module issue so that it is properly loaded during d-i. So who can help me with: https://bugs.debian.org/826629 ? Thanks !
Fails to build mono when PPC_64K_PAGES is set
Control: tags -1 patch Attaching debdiff. Sorry this bug totally fell of my radar. Thanks for resurecting powerpc binaries ! debdiff did not include the updated powerpc symbol file for some reason attaching as file directly. The patch has been tested on partch.d.o where building previously failed (ppc64 with 64K page). I am building also on PowerMac G4 ATM to double check any possible regression. PPC_64K_PAGES.debdiff Description: Binary data libmonoboehm-2.0-1.symbols.powerpc Description: Binary data
Re: PowerPC roadmap for Stretch
Adrian, On Mon, Oct 3, 2016 at 6:36 PM, John Paul Adrian Glaubitz wrote: > On 10/01/2016 02:16 PM, Mathieu Malaterre wrote: >> 3. radeonfb should be able to kick out offb >> >> In case (2) above cannot be solved in time. We can also fix the color >> inversion another way. Technically some PowerMac uses a radeon based >> graphic card, so we could fix the radeonfb module issue so that it is >> properly loaded during d-i. >> >> So who can help me with: >> >> https://bugs.debian.org/826629 ? > > I will do a fresh install of Debian Stretch using the current d-i images > tomorrow on my > Mac Mini G4 to see what I can do. I have previously fixed some issues > regarding "radeonfb". > The primary problem back then was that "radeonfb" left the GPU in a weird > state from where > the "radeon" KMS module could not initialize it. > > Problem was that that CONFIG_FB_RADEON was configured with =y instead of =m > meaning that > I had to disable "radeonfb" on the kernel command line using > "video:radeonfb=off". This > is also mentioned on the Ubuntu Wiki [1]. I am glad you mention this ! In fact if you read carefully the red/blue color inversion, you'll discover this particular message: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825840#59 I'd appreciate if you could also run the installer with offb:off. What is happening is that CONFIG_FB_RADEON=y make sure to use radeonfb (I was not able to find exactly why it skips offb), while CONFIG_FB_RADEON=m is doing something like this: 1. Try hardware framebuffer: offb 2. Try framebuffer: radeonfb However step (2) above fails as explained in #826629. Thus I fear CONFIG_FB_RADEON=m only fixes the *symptoms*. I would really appreciate if you could confirm that `radeonfb` properly works on your Mac Mini G4. -M
Re: PowerPC roadmap for Stretch
Hi, On Mon, Oct 3, 2016 at 8:52 PM, John Paul Adrian Glaubitz wrote: > On 10/03/2016 08:39 PM, Mathieu Malaterre wrote: >> However step (2) above fails as explained in #826629. Thus I fear >> CONFIG_FB_RADEON=m only fixes the *symptoms*. I would really >> appreciate if you could confirm that `radeonfb` properly works on your >> Mac Mini G4. > > I wasn't using radeonfb on my Mac Mini G4 at all but just the radeon module. > > I also tested that on an iBook G3 with Radeon chipset as well as on a > Powerbook > G4 aluminum. In fact, once radeonfb has been loaded once, the radeon KMS > module can no longer be loaded correctly and X.Org doesn't work. > > Reciting my results from back then [1]: I know that very well, read it multiple times :) You need to consider that d-i only ships radeonfb (there is another bug report from milan@d.o requesting it) about that. So the question is really during d-i should we leave it as-is with a very low level offb, or try to tidy up radeonfb (radeon.ko will never be part of d-i, there is also a long thread about this). -M
Re: PowerPC roadmap for Stretch
Ben, On Mon, Oct 3, 2016 at 9:16 PM, John Paul Adrian Glaubitz wrote: > On 10/03/2016 09:14 PM, Mathieu Malaterre wrote: >> You need to consider that d-i only ships radeonfb (there is another >> bug report from milan@d.o requesting it) about that. So the question >> is really during d-i should we leave it as-is with a very low level >> offb, or try to tidy up radeonfb (radeon.ko will never be part of d-i, >> there is also a long thread about this). > > Can you point me to the discussion regarding radeon in d-i? I would be > curios to know what the problem is. >From the top of my head I remember a mail (from you) where you gave some details as to why radeon.ko is not present in during d-i (only radeonfb.ko is). However today I can only find: https://bugs.debian.org/782058#51 I thought you mentioned some kind of regression, hence the reason to not ship radeon.ko during debian installation. Do you remember saying that, or am I dreaming ? Thanks much !
Re: PowerPC roadmap for Stretch
On Mon, Oct 3, 2016 at 1:35 PM, Christoph Biedl wrote: > Mathieu Malaterre wrote... > >> Since there has been some fuss about powerpc recently, let's see if I >> can get some help on issue(s) I'd like to fix for Stretch. > > Let's see what I can do (and I'm subscribed to debian-powerpc now, so > no need for Cc: in the future :) > >> 1. Secret GRUB option in d-i. >> >> This is no suprise that we have a situation with yaboot in powerpc (in >> particular partman-ext3 #825110). So I would like to finish the >> initial work to have GRUB be an alternative on PowerMac (famous secret >> option in d-i). >> >> Who can help me finish: >> - https://bugs.debian.org/610206 (I sent a patch but would appreciate >> feedback) ? >> - https://bugs.debian.org/691207 ? >> - https://bugs.debian.org/691209 ? > > I'll give it a try. > >> 2. offb/ATY,RockHopper: inverts red and blue in bterm >> >> I have not been able to make progress on >> https://bugs.debian.org/825840. So if anyone is familar with >> ioctl/FBIOPUTCMAP, I'd appreciate a little help here. > > I can confirm it's still there. Saw it when testing d-i for my recent > report and was a bit confused. But isn't this rather some > nice-to-have? True. But keep in mind that this will be the very first screen users will see. >> 3. radeonfb should be able to kick out offb >> >> In case (2) above cannot be solved in time. We can also fix the color >> inversion another way. Technically some PowerMac uses a radeon based >> graphic card, so we could fix the radeonfb module issue so that it is >> properly loaded during d-i. >> >> So who can help me with: >> >> https://bugs.debian.org/826629 ? > > Sorry, both my boxes are nvidia. Which causes a lot of trouble, too. > > Christoph
Re: CPU requirements for powerpc
On Sat, Oct 8, 2016 at 8:02 PM, Christoph Biedl wrote: > Hello, > > just to make sure I got things right: The 74xx/G4 processors are > to be supported by Debian's powerpc architecture? I use a PowerMac (Mac Mini) with a G4 and everything is fine. Technically even Altivec is not required: https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=powerpc&user=debian-powerpc%40lists.debian.org Don't forget to set the usertags so that we can track those. -M
Re: Problem with gem network card
On Fri, Oct 14, 2016 at 12:14 AM, Christian Groessler wrote: > On 10/11/16 20:56, Thadeu Lima de Souza Cascardo wrote: > >> On Tue, Oct 11, 2016 at 07:51:30PM +0200, Christian Groessler wrote: >>> >>> Hi, >>> >>> on my Mac G5 I see loss of network connectivity when doing big downloads >>> or >>> uploads. >>> >>> The machine cannot be pinged anymore then and also cannot ping out. >>> >>> When it's happening I see the following messages: >>> >>> Oct 11 10:45:13 g5 kernel: [ 430.477967] gem 0001:04:0f.0 eth0: RX MAC >>> fifo >>> overflow smac[03810400] >>> Oct 11 10:45:17 g5 kernel: [ 434.141957] gem 0001:04:0f.0 eth0: RX MAC >>> fifo >>> overflow smac[03810400] >>> >> Does setting the interface down, then up works? Like ifdown eth0; ifup >> eth0. Or ip link set eth0 down; ip link set eth0 up, and verifying the >> address and route are restablished (in case you are using >> NetworkManager, for example). > > > After > > $ ip link set eth0 down > $ ip link set eth0 up > > it's working again. > > But I have to be physically at the machine for this, so it's not a real > solution. You can put that in a script, or use screen: http://serverfault.com/questions/278838/restarting-network-through-ssh
Re: Debian 8.6 fails startup for Apple PPCs
On Sat, Oct 15, 2016 at 10:12 PM, Kristen wrote: > List, > > I am wondering if the Apple PowerPC line of computers are still > supported in Debian? I have tried to use a netinstall of Debian 8.6.0 on > a G3 iBook, a G4 MP, and a G5 iMac and all have failed in the same manner. > > The install appears to progress wonderfully. However after the initial > reboot the system fails with a message reading "Oh no! Something has > gone wrong.". If I click the button to "Log out" I am given only a blank > black screen. The virtual terminals also fail to respond. I suppose I > can SSH in if I hunt for the IP address assigned via DHCP. > > Any thoughts about this? I cannot find the thread anymore but basically GNOME 3.x has extra requirement, which older graphics cards do not have. As suggested, you should pick another desktop environment. I would also avoid KDE. I am a happy xfce user, but MATE may work if you want to stay closer to GNOME 2.x (not tested) -M
Re: Problem with gem network card
Hi, On Fri, Oct 14, 2016 at 4:45 PM, Thadeu Lima de Souza Cascardo wrote: > There is certainly a way to automate this, but my question on whether > that sequence would fix the problem was intended to more easily fix a > real bug in the driver. > > I can try to help fix the driver on my free time as a volunteer. > Christian, would you be willing to test patches to the driver? That > would require some back and forth between us and some patience of yours, > as I would be doing it on my spare time, considering I have family and > other projects I would like to attend to as well. > > I don't have a PPC Macbook of my own, but I used to fix Linux drivers on > PPC64 for a living not too long ago. That's a good news ! Feel free to use the bug report #841044 to send your patch (and/or updates). Regards.
Re: system frozen and mouse problem
On Sun, Oct 30, 2016 at 8:14 PM, Klaus Becker wrote: > Hi, > > I have new passwords and new problems: > > - I updated Debian 8 without any problem, but: > > - the mouse and the mousepad of the iBook G4 will not work. Sometimes after > system start they work some seconds, than the computer is completely frozen, I > can only restart it. > > - how to write a pipe "|", for ex. "dmesg | grep firewire"? (I saw boot hang > some time with a message about firewire) > > - I suppose there is a hardware problem, but I am not sure. I tried another > (usb) mouse and I had the same problem. I also tried the 2 usb connections. I am guessing you have an ATI card, try: $ cat /etc/modprobe.d/radeon-agpmode.conf options radeon agpmode=-1 You may want to do that from one of the virtual tty (Ctrl+Alt+1), then simply reboot. Some people prefer setting this param using yaboot: https://wiki.debian.org/PowerPC/FAQ#How_do_I_get_graphics_working.3F HTH
Fwd: Release Architectures for Debian 9 'Stretch'
Anyone has a summary of the powerpc specific discussion ? -- Forwarded message -- [...] The only change from Jessie is the removal of powerpc as a release architecture. We discussed this at length, and eventually took the view that the least disservice to users of that port is to provide reasonable notice of its discontinuation. We recognise and acknowledge that discontinuing any port is unavoidably disruptive. The question of whether powerpc remains an architecture in the main archive or moves to ports is one for FTP masters, not the release team. [...]
Re: [Debian-ports-devel] Moving powerpc to Debian Ports
Hi Eric, On Fri, Nov 4, 2016 at 1:12 AM, Franc-Parler ancien wrote: > Le 03/11/16 02:32, Rick Thomas a écrit : > >> On Nov 2, 2016, at 8:03 AM, Herminio Hernandez >> Jr. wrote: >> >>> I would like to know after Stretch will we be able to submit bugs to BTS >>> or are we basically on our own. >>> On Nov 2, 2016, at 4:43 AM, Gatis Visnevskis wrote: I would like to have knowledge shared, how to still run Debian on powerpc without main archives. >> >> >> We need answers to both of these questions ASAP. >> >> I have old PowerPC Macs that run Jessie, and I’m very reluctant to replace >> them. I need to know exactly what I’ll have to do to keep them running and >> secure. >> >> Thanks! >> Rick >> > Hello, > > I'm a prospective user of Debian owning a mac ppc G3 . I couldn't install > Jessie (graphic card issue for the moment) but still willing to succeed to > go further with next computers. Did you check the FAQ: https://wiki.debian.org/PowerPC/FAQ I am reading ATM I thought there was a section for G3, I remember vaguely that resolution needs to be passed at startup. But I cant find the reference at this time. -M
Re: Re: Re: Debian 8 on Late 2005 G5, Graphics Issues
On Mon, Nov 7, 2016 at 11:40 AM, Daniel Cavalli wrote: > Hi Peter, > > firstly thanks very much for providing the kernel images. > > yesterday I installed Jessie on my newly acquired G5 powerpc (GeForce FX > 5200 Ultra) and experienced problems with nouveau, which I used the > parameter nouveau.noaccel=1 as a workaround to get a functioning system. > > So I have installed both the 3.18 and the 4.5.0-rc2 versions of the kernels > you provided. Both seemed to boot up ok to the splash screen, but I could go > no further, as my wireless usb keyboard and mouse no longer worked. they > worked fine on the 3.16 kernel. any ideas? I have a wired mouse which worked > fine for 3.18 and 4.5.0 but unfortunately I don't have a wired keyboard to > test with. This is the first time I've installed a kernel myself so any > advice you can provide is appreciated. I have not tried this kernel but are you sure it is using the same .config file as Debian or is this a `localmodconfig` build one ?
Re: Using 4KiB page size by default on buildds
Hi, On Sat, Nov 12, 2016 at 12:02 PM, Thadeu Lima de Souza Cascardo wrote: > Hi, > > While recently investigating the mariadb bug, I found out the culprit is > in fact jemalloc. This library assumes the system page size is the one > that it found when building it. The version in Jessie was built on a > 4KiB-page size system. So, when using it on a 64KiB-page size system, we > might see crashes. That's why building mariadb for Jessie on partch > fails. mariadb uses jemalloc and during make check, a crash induces a > deadlock. Nice ! added usertags 'powerpc': https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=powerpc&user=debian-powerpc%40lists.debian.org > To give some context, I used to work fixing drivers for IBM Power > Systems, which used 64KiB-page size kernels on most situations. And we > found many issues due to people assuming 4KiB page sizes. > > Even though we could debate about the value of using any page size > different from 4KiB, the fact is that there are systems out there using > different page sizes, and even Debian ships with some kernels and uses > it on its buildds. > > I, for one, believe we should support such different page sizes on the > entire archive. This means fixing jemalloc, device drivers, other memory > allocators and any other software that might break or work suboptimally > on such systems. > > However, the current state of things has meant that powerpc has been > dropped from squeeze and while I would agree that jemalloc might have > been an exception, who knows what else might break because of such > differences? We might look for things like page.*size/i in the archive, > but upstream fixes might not always be an easy and quick path. Consider > the jemalloc case, where upstream has diverged a lot from the current > version in Debian, and I am not sure how they might take a fix for the > version in Jessie. > > So, my proposal here is that we decide on a default page size for > buildds and kernels shipped with Debian, give the option for the > different page size for other users, but state there might be breakages > when using it. That doesn't mean it's not supported, and shipping it is > a way of giving the chance for it to be tested. It's not broken either, > most things should work, but some things here and there are broken, and > we could even have a list of known issues (that we want to fix > eventually, though in future releases). > > Given that most users I see on this list are using 10+ year old > hardware, which likely have low memory capacity and some support only > 32-bit kernels, I'd say we default to 4KiB page size, and that's where > most software will work, while 64KiB page size will impact much more > broken software. > > Next steps here are getting a 64-bit kernel built with 4KiB page size > available in the archives, and using those kernels on those buildds that > currently run a 64-bit kernel. The old ppc64 was this way, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826796 > What are the thoughts of the Debian powerpc community? As you know 'powerpc' has been removed from the release archs. So instead I would suggest that you get in touch with reproducible people instead. Ideally the autopkg test should (could?) be run on a kernel with different page size. But I fail to see how you can address something like: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819711 The page size is hardcoded (at built time) to 64K, so that it passes on both partch.d.o (64K page) as well as my old G4 (4K page)... Thanks anyway for your interest in powerpc. -M
Re: Kworker
On Wed, Feb 1, 2017 at 12:01 PM, Luke wrote: > How to do the same on PPC based machine? > > http://askubuntu.com/questions/176565/why-does-kworker-cpu-usage-get-so-high#answer-233947 > > I'm running Debian 8.7 - 3.16.0-4-powerpc on PowerBook3,1 G3 PISMO. There is a single core on a G3, what are you trying to do *exactly* ?
Re: A few questions about stretch ( testing ) on a PowerMac G5
Dear OP, On Sun, Feb 5, 2017 at 8:59 AM, John Paul Adrian Glaubitz wrote: > On 02/05/2017 12:12 AM, dev_user wrote: >> The first of many little problems that I hit is that the nouveau driver >> is just terrible and all I see on the screen is a very very messed up pile >> of what >> looks like static. So there is no GUI no graphical login at all that works. >> I created a file in /etc/modprobe.d/ thus : > > nouveau is problematic on PowerPC. If upgrading to the latest kernel > doesn't help, I recommend using a different graphics adapter. Just for reference: no updating to the latest kernel will not help. This is one outstanding issue: https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=ppc64&user=debian-powerpc%40lists.debian.org -> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790690 I believe someone posted instructions to rebuild your ppc64 kernel to cope with this issue. If not please ping me. -M
Re: Performance difference 32bit/64bit userland
On Wed, Feb 8, 2017 at 2:21 PM, Breno Leitao wrote: > On 02/07/2017 07:22 PM, Lennart Sorensen wrote: >> ppc64el is different since it is targeting systems where the applications >> are expected to need a lot of ram, and switching the little endian >> improves performance when working with GPUs (which are all designed >> for the x86 little endian world). At the same time being able to >> assume power8 as a minimum cpu means you can gain some instruction set >> improvements that normal powerpc can't assume. > > Correct. And we can't do 32-bits userspace also, since we do not have a > 32-bits little endian ABI. For ppc64el, bi-arch does not seem to be a valid > feature. I always assumed it was possible to run ppc32 (be) or ppc64 (be) userlands on a ppc64el system. Is this a restriction at Linux level or hardware level ? -M
Re: Unable to wake up PowerBook G4's display after closing and reopening its lid.
On Tue, Mar 7, 2017 at 3:04 AM, PhiLLip Pi wrote: > Hello. > > Now, I have Debian PowerPC installed, updated, and running on the very > old 2002 15" PowerBook G4. I noticed after closing (Apple's glowing logo > light goes off, but the old fans still spin) and opening its lid, it > won't wake up. I retried this in both LXDE, XFCE, and the GUI login > screens. Mac OS X/Jaguar v10.2.8 and Yaboot (Apple's lid's logo light > doesn't turn off though) had no problems. > > Is there something I need to install and configure to make it this work > correctly in Linux? I would install at minimum: pbbuttonsd https://packages.qa.debian.org/p/pbbuttonsd.html -M
Re: What are you guys running on your PowerBook G4's Debian PPC?
On Wed, Mar 8, 2017 at 10:53 PM, PhiLLip Pi wrote: > Server? Workstation? Old school text stuff? Just curious. I am trying to > see what I can use my slow PowerBook G4 with 512 MB of RAM to do. I use my MacMiniG4 for: - ssh server to outside (ppc32 is uncommon so it gives me impression of improved security). - git server - build+test robot for big endian compilation+testing. I used it in the past for running minidlna but I had to give up mainly because of bug #774149 (using kodi with a dedicated RPi3B+ now) Obviously this may not fit a laptop goal. -M
Re: Shutting down my PowerBook G4 doesn't really shut down?
Hi, On Fri, Mar 17, 2017 at 4:57 AM, PhiLLip Pi wrote: > I noticed every time I do a shut down from Debian PPC stable/Jessie, it > doesn't fully shut down. I see its screen go black and stuff. I can't > even wake it up with keys (can't even ctrl+alt+F1 keys), trackpad and > its button, and power button. Holding its power button for five seconds > fully shuts down (can hear its fan and other shut down), and then I can > power up again. It seems to get stuck in its shut down. It even happens > in its X login screen. :( What do you see in the system log as you shutdown ? Does it get stuck on something (you may want to ssh onto your laptop and tail -f the log file). -M
Re: Radeon Graphics Acceleration for Debian wheezy / Hwoto?
Richard, On Mon, Apr 3, 2017 at 6:09 PM, John Paul Adrian Glaubitz wrote: > Hello Richard! > > On 04/03/2017 05:07 PM, Richard Kuenz wrote: >> Got a very nice Powermac 7,3 Dual CPU with a Radeon 9650 Graphics Card. The >> System runs smooth and silent; >> >> Would like to use Debian Wheezy on this Computer. >> >> I installed it and it runs very fine, but i get no graphics acell. > > Could you please provide your /var/log/Xorg.0.log file as well as the > output from the commands "glxinfo" and "dpkg -l libgl\*". Plus, the > output of "dmesg" right after the machine has booted. > > It should be possible to install a newer kernel from wheezy-backports > as well as updated MESA and X.Org drivers from there (if available). Technically for a full bug report we would want: /usr/share/bug/xorg/script 3>/tmp/script.log Thanks for your time
Re: Radeon Graphics Acceleration for Debian wheezy / Hwoto?
On Mon, Apr 3, 2017 at 7:07 PM, Richard Kuenz wrote: > "script.log" > > see attachment please uh ? You really need to see this in your terminal: $ /usr/share/bug/xorg/script 3>/tmp/script.log
Re: Radeon Graphics Acceleration for Debian wheezy / Hwoto?
On Mon, Apr 3, 2017 at 7:29 PM, Richard Kuenz wrote: > sorry > > there you go Ok: [24.327] (EE) AIGLX error: r300 does not export required DRI extension [24.328] (EE) AIGLX: reverting to software rendering I can't remember from the top of my head, but I would try the famous radeon.agpmode=-1 trick in yaboot.
Re: Bug#859748: general: fails to address full 8GiB of DDR RAM on PowerMac G5 (only 5.8GiB)
FYI On Thu, Apr 6, 2017 at 11:44 PM, Ben Hutchings wrote: > Control: reassign -1 src:linux 3.16.39-1+deb8u2 > Control: tag -1 moreinfo > > On Thu, 2017-04-06 at 12:23 -0700, Mark G.B. wrote: >> Package: general >> Severity: normal >> >> Dear Maintainer, >> >> I recently installed 4x1GiB sticks of DDR RAM into my PowerMac G5 DP 2.0 GHz. >> Apple indicates the maximum amount of RAM supported is indeed 8GiB. > > I'm inferring from this that you have the DP+ with 8 RAM slots, and you > have upgraded from 4 * 1 GiB to 8 * 1 GiB installed. Is that right? > >> The system is fully usable, it runs without problems in any area, pretty >> much, >> but I would like to know if it is using the full 8GiB since in system monitor >> it states only 5.8 GiB total are registered. >> >> Please, if you are able to direct me, or fix, thanks. There would certainly >> be >> a performance boost in say things like Kdenlive for me if the missing ~2GiB >> were restored. >> >> >> P.S. I've attached output of 'cat /proc/meminfo' for reference. > > This is quite surprising. It is normal for the system firmware to > reserve some amount of memory that is then unavailable to Linux, but > this is a very large amount. > > Please also send the kernel boot messages, which might help explain > what's going on. (We probably still won't be able to solve this, > though, as there are few developers still interested in PowerMac > systems.) > > Ben. > > -- > Ben Hutchings > When in doubt, use brute force. - Ken Thompson
Re: debian-installer now available in Ports
On Fri, Apr 14, 2017 at 10:04 AM, Linux User #330250 wrote: > One suggestion for further improvement: on an older installation I had used > before powerpc was dropped (Debian 7.x, then testing) I was able to get > grub2 running. It would be an idea to have grub2 as an alternative to yaboot > during installation. Hum, is this a regression from: https://bugs.debian.org/664128 Did you really create manually '/boot/grub' partition ? I believe there will still be some manual steps since this is not a PRep machine but should get you almost there. -M
Re: debian-installer now available in Ports
On Fri, Apr 14, 2017 at 10:25 AM, John Paul Adrian Glaubitz wrote: > > Does anyone know how well supported GRUB on powerpc is? Does it support all > PPC Macs or only newer > ones, e OldWorld will not work: https://lists.gnu.org/archive/html/help-grub/2015-03/msg00072.html NewWorld are supposed to work. So the question is: does anyone still has an OldWorld ?
Re: debian-installer now available in Ports
On Fri, Apr 14, 2017 at 11:14 AM, John Paul Adrian Glaubitz wrote: > On 04/14/2017 11:05 AM, Mathieu Malaterre wrote: >>> Does anyone know how well supported GRUB on powerpc is? Does it support all >>> PPC Macs or only newer >>> ones, e >> >> OldWorld will not work: >> >> https://lists.gnu.org/archive/html/help-grub/2015-03/msg00072.html > > Yeah, I was actually about to ask whether the criteria would be a NewWorld > machine, but for some reason I didn't finish my sentence :O. > >> NewWorld are supposed to work. So the question is: does anyone still >> has an OldWorld ? > > I tried installing on a PB3400 a while ago - didn't work, there are issues > [1]. > > However, I'm not ruling out that other OldWorld machines work, so we could > just try detecting the machine type in debian-installer and enable GRUB > for the NewWorld machines only. Leaving it to the user is by far the best option ! I think I am getting confused now, because on one page, we have Performa 4400, 54xx, 5500 listed as powermac-OldWorld https://www.debian.org/ports/powerpc/inst/install while (Performa)54xx,6400 is reported to have OF 2.0: http://www.netbsd.org/ports/macppc/models.html So I am not clear exactly if OldWorld really imply no OpenFirmware. I'll pass on to another expert. -M
__ppc__ and __ppc64__ gone ?
Hi there, Could someone shed some lights on: https://lists.freedesktop.org/archives/gstreamer-commits/2016-September/096001.html Really is __ppc__ & __ppc64__ gone from gcc ? One would need to update https://wiki.debian.org/ArchitectureSpecificsMemo do a codesearch.d.n at some point if that is real. Thanks
Re: dmesg kernel trace and base system without less/man (WAS: Re: debian-installer now available in Ports)
Hi, This is not clear to me. Is this the stable kernel ? Did you send this information to: ? On Fri, Apr 14, 2017 at 3:49 PM, Linux User #330250 wrote: > BTW, I get this in dmesg output, on both the installer boot and when booting > the installed -smp kernel. > > [4.767389] [ cut here ] > [4.774668] WARNING: CPU: 0 PID: 1 at > /build/linux-dp17Ba/linux-4.9.18/arch/powerpc/lib/feature-fixups.c:208 > check_features+0x38/0x7c > [4.782256] Modules linked in: > [4.789766] CPU: 0 PID: 1 Comm: swapper Not tainted 4.9.0-2-powerpc #1 > Debian 4.9.18-1 > [4.797441] task: df4db1a0 task.stack: df4dc000 > [4.805089] NIP: c0776484 LR: c0776484 CTR: > [4.812736] REGS: df40 TRAP: 0700 Not tainted (4.9.0-2-powerpc > Debian 4.9.18-1) > [4.820485] MSR: 00029032 > [4.820622] CR: 242ff422 XER: > [ 4.828326] > [4.828326] GPR00: c0776484 df4dde80 df4db1a0 002c 0004 00ff > 00ff > [4.828326] GPR08: 00ff c085271c c085271c 222ff444 > c00047ec > [4.828326] GPR16: > c086 > [4.828326] GPR24: c076ecdc c07d2e80 c0766720 c07b2310 c085f5b0 > c086 c07b > NIP [c0776484] check_features+0x38/0x7c > [4.875135] LR [c0776484] check_features+0x38/0x7c > [4.882958] Call Trace: > [4.890751] [df4dde80] [c0776484] check_features+0x38/0x7c (unreliable) > [4.898650] [df4dde90] [c0004154] do_one_initcall+0x4c/0x188 > [4.906477] [df4ddf00] [c076f578] kernel_init_freeable+0x164/0x200 > [4.914269] [df4ddf30] [c0004810] kernel_init+0x24/0x134 > [4.921942] [df4ddf40] [c0016500] ret_from_kernel_thread+0x5c/0x64 > [4.929536] Instruction dump: > [4.937046] bfc10008 90010014 3fc0c086 811ef028 3fe0c07b 80ff349c > 8108000c 7f883800 > 41be0014 3c60c06b 38632f34 4be5f601 <0fe0> 815ef028 3bff349c 813f0004 > [4.952413] ---[ end trace de3271b83777a44e ]--- > > > On the installer (non-smp), it starts with this: > [0.00] Total memory = 512MB; using 1024kB for hash table (at > cff0) > [0.00] Linux version 4.9.0-2-powerpc > (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170321 (Debian > 6.3.0-11) ) #1 Debian 4.9.18-1 (2017-03-30) > [0.00] Found initrd at 0xc0c4:0xc19744bc > [0.00] Found UniNorth memory controller & host bridge @ 0xf800 > revision: 0x11 > [0.00] Mapped at 0xff7c > [0.00] Found a Keylargo mac-io controller, rev: 3, mapped at > 0xff74 > [0.00] PowerMac motherboard: PowerMac G4 Silver > [0.00] Using PowerMac machine description > > This might be fixed in a 4.10 kernel, but I just thought it would be worth > mentioning it here. > *Despite* the message the kernel *seems to work* in an orderly fashion. > > And one more thing I noticed: less is missing on both the installer (shell) > and on the base installation thereafter. man is also not installed. I would > have thought that man and less were part of a base system... >
Re: Problems installing Jessie to Powerbook from USB Stick
On Wed, May 17, 2017 at 8:29 PM, Carlos wrote: > Hello to all, > > first of, great community. This is my first post but I have read a lot of > threads on this mailing list. And I’m a totally noob on Linux. > > I would like to install Debian from a USB-Stick, but sadly it fails. Here is what I use: https://lists.debian.org/debian-powerpc/2016/04/msg00081.html
Re: Problems installing Jessie to Powerbook from USB Stick
On Wed, May 17, 2017 at 9:39 PM, Mathieu Malaterre wrote: > On Wed, May 17, 2017 at 8:29 PM, Carlos wrote: >> Hello to all, >> >> first of, great community. This is my first post but I have read a lot of >> threads on this mailing list. And I’m a totally noob on Linux. >> >> I would like to install Debian from a USB-Stick, but sadly it fails. > > Here is what I use: > > https://lists.debian.org/debian-powerpc/2016/04/msg00081.html Sorry about that, I meant: https://lists.debian.org/debian-powerpc/2016/04/msg00103.html The previous link was my first attempt. Burning the ISO directly seems to work in a lot of cases.
