I think this isn't for 32 bit ppc.Void is really great at least because of more or less modern browser (Firefox). My Gentoo is sitting jealous, because Firefox can't compile there (even required dependency packages fails).
I think this isn't for 32 bit ppc.Void is really great at least because of more or less modern browser (Firefox). My Gentoo is sitting jealous, because Firefox can't compile there (even required dependency packages fails).
The only 32-bit PPC Linux I can think of which has any version of Firefox originally released upstream at any point in 2020 is Adiéle, which has Firefox ESR 68.10.0. Haven't spent any time attempting to test it, though.I think this isn't for 32 bit ppc.
slub_debug=P page_poison=1
/etc/default/grub
Thanks for all the help.yeah, I followed the advice to make the bootstrap 10MB as on this link
![]()
Installation · Issue #2 · void-ppc/void-ppc-docs
We need to simplify the installation. That means doing the following: add support for live image generation to mklive fix GRUB working instructions for OpenPOWER hardware working instructions for P...github.com
yeah, good luck, I found it not too difficult, and I've got the attention span of a goldfish.Thanks for all the help.
sqeeezy, I will go and read through the link you posted.
Thank you. That page says in relation to Rage Pro: "It will not work out of box - you need to correctly set up your modelines in xorg.conf.d to make it work." but I've been unable to find any examples of this.Look at this page:
Graphics - Void Linux for PPC (unofficial) documentation
docs.voidlinux-ppc.org
Maybe it helps
rfkill bluetooth on didn't work either. Do I need a proprietary driver or something? Bluetooth just worked in Ubuntu 16 so it must be in the Linux kernel somewhere...I am now a convert to Void, sound working beautifully after I removed Pulseaudio. My next challenge is bluetooth.
I have installed bluez and blueman and got the bluetoothd service running but I get the message "No default controller available" when I try to use it.
lsusb detects the bluetooth device: Bus 002 Device 002: ID 05ac:1000 Apple, Inc. Bluetooth HCI MacBookPro (HID mode)
But no joy trying to get it to work.
rfkill shows it is not blocked:
$ rfkill
ID TYPE DEVICE SOFT HARD
0 wlan phy0 unblocked unblocked
Although the bluetooth is not detected by rfkill either.
Any advice? Thank you....
Thank you. That page says in relation to Rage Pro: "It will not work out of box - you need to correctly set up your modelines in xorg.conf.d to make it work." but I've been unable to find any examples of this.
Does anyone know how I should set up xorg.conf.d so that voidlinux-ppc supports my Rage128 Pro?
I have installed the xf86-video-r128 driver with... xbps-install -S xf86-video-r128
The original /usr/share/X11/xorg.conf.d/10-amdgpu.conf is as follows:
Section "OutputClass"
Identifier "AMDgpu"
MatchDriver "amdgpu"
Driver "amd"
EndSection
I assume I need to change Driver line above from "amd" to "xf86-video-r128"?
I've tried creating a new file /usr/share/X11/xorg.conf.d/10-monitor.conf as follows:
Section "Monitor"
Identifier "VGA1"
Modeline "1280x1024_60.00" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync
Option "PreferredMode" "1280x1024_60.00"
EndSection
Section "Screen"
Identifier "Screen0"
Monitor "VGA1"
DefaultDepth 24
SubSection "Display"
Modes "1280x1024_60.00"
EndSubSection
EndSection
Though I must say I've no idea if that is even close!
The current output of /var/log/Xorg.0.log: here
I'm struggling with this and would appreciate guidance. If it is too hard then perhaps I should just wait for the mac Radeon 9600 to arrive, which I hope would be more straight-foward to get working than this mac Rage128 Pro.
From what I learned recently, musl must use the free open source graphics drivers, which means hardware acceleration is a no go... at least with the nouveau (NVIDIA) driver. The ATI driver may be better.I was blown away to discover a modern non BSD based distro for 32bit ppc. I have an (infamous?) ibook duel USB that i know worked 10ish years ago when I installed gentoo on it, but for the life of me I can't get 2D acceleration to work in X11. I understand the kernel has changed how it does graphics drivers and I know 3D is a lost cause most likely, but I would love to get 2D working in r128 vs using fbdev. Server starts in r128 but is just a blank screen.
I must note that running a 5.9 kernel is pretty amazing on this hardware. In console it feels pretty snappy, and the original battery even gets an hour of use. Obviously its not a serious computer at this point but getting a usable desktop would be great.
edit: I'm using musl if that changes anything
It was in a chat with Adelie Linux devs as I was talking/working through some glitches in their MATE Live CD. I need to look a little more into it, so if you know more, let me know. It may only relate to their particular distribution, perhaps?@NathanJHill Where did you read that musl requires FOSS drivers?
BTW, you can insert more or less recent card in G5 PCI-Ex, using additional power connector. The expediency is questionable.because of the age of our video cards
As far as I remember when I had gentoo installed it was the open source xf86 r128 driver. I just don't know why the screen turns blank with the r128 driver. At least with an xorg crash it could tell me something useful, but I don't seem to have any indication that something is wrong as far as the software thinks.From what I learned recently, musl must use the free open source graphics drivers, which means hardware acceleration is a no go... at least with the nouveau (NVIDIA) driver. The ATI driver may be better.
I've started tinkering with Adelie Linux on my G5 and have had mixed results. I need to try void soon.
ah bummer! That's actually the card I had in it before i got a 9600 for the dual dvi ports. I sold the 5200 sadly to recoup the cash. I'll give 4.4 a go and see if that helps out, thanks!I had the same issue with the same gfx card on my dual 2ghz g5. I ended up swapping in the nvidia GeForce fx5200 from my 1.6ghz g5 and now its buttery smooth. I did however roll back to the 4.4 kernel as all the 5.x kernels either wouldn't boot, or had graphics display issues (unreadable text and tearing) after a few minutes of being booted. For what it's worth the same issues happened with Debians 5.x kernels as well on the same machines. 4.x kernels worked fine.