Worked on both an iBook clamshell and Mac mini with 0 configuration for me as well. Sndio rocks.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
- Status
Worked on both an iBook clamshell and Mac mini with 0 configuration for me as well. Sndio rocks.
A week ago I installed 6.7 on my Titanium Powerbook 3,5 1GHz DVI. Multi partition, Tiger, Leopard, and borked scraps of void and adélie. Made USB stick as per instructions and booted in OF as usb0/disk@1.
Installation smooth except I was bemused by how to point the installer to the files on the stick and wasted time with unnecessary stalling downloads before I engaged cerebrum and restarted the install and let it find the files.
Not glaringly obvious, but I'm not complaining.
To boot from the installed partition required me to locate an obscure [SOLVED] forum query, what's new...it was the only place which said I'd have to specify the partition number, well, ok, yeah, sort of obvious.
My boot prescription turned out to be boot hd:13,ofwboot, determined by sequentially advancing through the wastelands of my hd.
The desktop is refreshingly archaic, (archaic=good, I love Plan9), with xterm's spidery font, but last night I stuck xfce on there and I'm in the process of seeing how useable my lovely old, excellent build quality TiBook can be.
Installation smooth except I was bemused by how to point the installer to the files on the stick and wasted time with unnecessary stalling downloads before I engaged cerebrum and restarted the install and let it find the files.
Not glaringly obvious, but I'm not complaining.
To boot from the installed partition required me to locate an obscure [SOLVED] forum query, what's new...it was the only place which said I'd have to specify the partition number, well, ok, yeah, sort of obvious.
My boot prescription turned out to be boot hd:13,ofwboot, determined by sequentially advancing through the wastelands of my hd.
The desktop is refreshingly archaic, (archaic=good, I love Plan9), with xterm's spidery font, but last night I stuck xfce on there and I'm in the process of seeing how useable my lovely old, excellent build quality TiBook can be.
I don't know if CDE even compiles on OpenBSD/macppc but it sure is archaic. Ran it on my Debianised iBook for the LOLs.
These past 2 weeks I picked up my iBook G4 12" 1.07 Ghz with OpenBSD 6.6 again.
Got a recent GNS3 2.2.7 installed via pip3.7 (packages only have the older 0.85 release).
Source-compiled ubridge, with the package installed Qemu 4.1.0 and almost able to boot a Cisco vIOS QEMU image.
One strange thing GNS3 2.2.7 doesn't recognize the local GSN3 server, I have to run it as a Remote server on 127.0.01 LOL.
How easy or difficult would it be to clone my 6.6 install onto another iBook G4 (14" with more RAM and higher CPU speed) ?
Use DD as explained here ?
Got a recent GNS3 2.2.7 installed via pip3.7 (packages only have the older 0.85 release).
Source-compiled ubridge, with the package installed Qemu 4.1.0 and almost able to boot a Cisco vIOS QEMU image.
One strange thing GNS3 2.2.7 doesn't recognize the local GSN3 server, I have to run it as a Remote server on 127.0.01 LOL.
How easy or difficult would it be to clone my 6.6 install onto another iBook G4 (14" with more RAM and higher CPU speed) ?
Use DD as explained here ?
i wasn't able to install xfce due to an issue with packages, and otter browser segfaults when i try to to search something in it. can anyone help me out? the computer is a PowerBook G4 from 2004 running openbsd 6.7
Replaced GNU Nano with Pico (smaller size with less dependencies), sudo with doas, added the Surf Web Browser, and changed installing the sets to pull from server instead of CD (this will make USB installation easier).
@superlions16 If it's the 503 error, just try installing it again. As for the browser, a Segmentation fault is (to my understanding) due to a compilation issue. Right now, you can either try recompiling it from source, or try a different browser, like Surf, NetSurf, or Links.
There is also Firefox, but that segfaults on PowerPC too, last I checked.
@superlions16 If it's the 503 error, just try installing it again. As for the browser, a Segmentation fault is (to my understanding) due to a compilation issue. Right now, you can either try recompiling it from source, or try a different browser, like Surf, NetSurf, or Links.
There is also Firefox, but that segfaults on PowerPC too, last I checked.
6.7 broke all of the above, 6.6 works fine. I never looked deeper into why this happened, I was quite disappointed since so much stuff broke.
That’s due to the base default compiler on macppc being switched from the elderly gcc to clang. Lots of ports seem to have been broken when that happened.
It would be nice if it worked. Might be worth grabbing a core dump and filing a bug report. Though I always found webkit based browsers very buggy, on both OpenBSD and Linux. I'm not surprised it broke.
I have now upgraded to 6.8-release. Actually the upgrade process has become really simple, all you need to run is sysupgrade -r, then pkg_add -u upon the reboot.
In 6.8-release both midori and otter-browser work with JavaScript OFF. Both crash otherwise. Surf still displays a blank screen.
Also the Broadcom WiFi adapter in my Powerbook G4 12" started to disconnect randomly with no way to bring it up. It was rock solid in 6.6 and 6.7.
In 6.8-release both midori and otter-browser work with JavaScript OFF. Both crash otherwise. Surf still displays a blank screen.
Also the Broadcom WiFi adapter in my Powerbook G4 12" started to disconnect randomly with no way to bring it up. It was rock solid in 6.6 and 6.7.
I upgraded to 6.8 last night on my 1GHz TiBook. The sysupgrade -r process was straightforward but after rebooting twice, in open firmware as usual, and logging in as usual, my xfce desktop froze upon opening terminal: the terminal window outline was drawn and then froze, so I wasn't able to do the pkg_add -u. I rebooted and tried again, same deal. I haven't done a lot with openBSD macppc yet, especially as its GUI performance has been so sluggish to Tiger or Leopard, which I have on partitions on there, so I haven't got round to faultfinding, especially as the TiBook's in an unheated room and it's getting cold in my mountain shack. It's a low priority, I'm posting to inform as much as to request help, but if there's any out there, cheers.
Hi thanks for the documentation here, trying to install OpenBSD on an eMac 1GHz here but the Radeon 7500 in it is giving problems with both 6.8 and 6.7, about to try 6.6 for good measure. The screen goes blank when attempting to load the radeon driver. Can get a console working by booting with 'boot -c' and 'disable radeondrm' but X would be nice.
dmesg logs "Unable to locate a BIOS ROM" but I've run "fw_update -a" to install the firmware, checked the supposed firmware image was in /etc/firmware/radeon/R100_cp.bin but same problem and out of ideas :-/ any help appreciated!
from dmesg:
dmesg logs "Unable to locate a BIOS ROM" but I've run "fw_update -a" to install the firmware, checked the supposed firmware image was in /etc/firmware/radeon/R100_cp.bin but same problem and out of ideas :-/ any help appreciated!
from dmesg:
Code:
bootpath: /pci@f2000000/mac-io@17/ata-4@1f000/disk@0:/bsd
root on wd0a (832a9c14c449f519.a) swap on wd0b dump on wd0b
initializing kernel modesetting (RV200 0x1002:0x5157 0x1002:0x5157 0x00).
[drm] *ERROR* Unable to locate a BIOS ROM
radeondrm0: 1024x768, 16bpp
wsdisplay0 at radeondrm0 mux 1: console (std, vt100 emulation), using wskbd0
wsdisplay0: screen 1-5 added (std, vt100 emulation)
I've got a 2010 MacBook Air that has several OS bootable via rEFInd. I've always struggled to get WiFi working with BSD variants but have no problem with Linux, so I'm assuming I'm just missing some drivers?
Yeah it's probably a Broadcom chip and that company is notoriously unhelpful to open source projects. What's the output of 'dmesg' and 'ifconfig'?
I noticed this happened on a Mac Mini Core 2 Duo when I installed 6.8, and I ended up replacing the thermal paste. Fans have returned to normal now. OpenBSD evidently has no means to throttle or control fans.
Hey all, appreciate any help... I can't seem to get xfce to work/run.
I followed the instructions in the first post... when I run
I am told it needs to run with the "-f" option. Okay.
When I do that, I don't get Xfce, I get a logon to FVMM, not Xfce
When I run
I get this...
I made my the .xinitrc file... I don't know what I am doing wrong.
The computer in question is a Mac mini G4 w/ 1GB RAM running OpenBSD 6.8
I followed the instructions in the first post... when I run
sudo rcctl start xenodmI am told it needs to run with the "-f" option. Okay.
When I do that, I don't get Xfce, I get a logon to FVMM, not Xfce
When I run
sudo startxI get this...
Mac-mini-G4$ sudo startx
xauth: (stdin):1: bad display name "Mac-mini-G4.eureka:0" in "add" command
X.Org X Server 1.20.8
X Protocol Version 11, Revision 0
Build Operating System: OpenBSD 6.8 macppc
Current Operating System: OpenBSD Mac-mini-G4.eureka 6.8 GENERIC#790 macppc
Build Date: 06 October 2020 02:06:55AM
Current version of pixman: 0.38.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Aug 11 22:28:31 2021
(==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d"
(II) [KMS] Kernel modesetting enabled.
(EE) Failed to open authorization file "/root/.serverauth.nUq8sDQLTa": Permission denied
/root/.xinitrc[1]: xfce: not found
xinit: connection to X server lost
waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.
xauth: (argv):1: bad display name "Mac-mini-G4.eureka:0" in "remove" command
I made my the .xinitrc file... I don't know what I am doing wrong.
The computer in question is a Mac mini G4 w/ 1GB RAM running OpenBSD 6.8
@danielktdoranie I haven't used OpenBSD/macppc nearly as much as I have Debian in the past, and I certainly haven't tried the newer releases of the former, either. From what I recall though, I believe I may have had success with sudo startxfce4.
That said, how have you configured your .xinitrc file? Given the above message /root/.xinitrc[1]: xfce: not found, you might want to try changing your "xfce" entry to "xfce4" instead, and see what happens.
I hope that was helpful.
That said, how have you configured your .xinitrc file? Given the above message /root/.xinitrc[1]: xfce: not found, you might want to try changing your "xfce" entry to "xfce4" instead, and see what happens.
I hope that was helpful.
From :
wiki.xfce.org
I think the command would be :
to put in the .xinitrc too.
faq [Xfce Wiki]
startxfce4to put in the .xinitrc too.