pII. Max RAM, CPU(s), VPU according to board limits. Ex. Radeon 9200 (R280) for PCI / AGP 1x bus, Radeon 9700 Pro (R300) for AGP 2x bus, Radeon X1950 XTX (R580+) (?) for AGP 4x bus.
You can do better than a 9700 on AGP 2x
pII. Max RAM, CPU(s), VPU according to board limits. Ex. Radeon 9200 (R280) for PCI / AGP 1x bus, Radeon 9700 Pro (R300) for AGP 2x bus, Radeon X1950 XTX (R580+) (?) for AGP 4x bus.
Doing this method is not as effective on a Mac as it is on other platforms because, as the Mac has no user-accessible BIOS, the integrated feature chips can't be disabled. So on a Mac, you've got this network card running at the same time as the integrated network chip. Likewise for internal storage, and other I/O. The CPU is still doing the extra work.
Doing this method is not as effective on a Mac as it is on other platforms because, as the Mac has no user-accessible BIOS, the integrated feature chips can't be disabled. So on a Mac, you've got this network card running at the same time as the integrated network chip. Likewise for internal storage, and other I/O. The CPU is still doing the extra work.
Couldn't one accomplish something similar on a Mac by selectively disabling kexts?
You can do better than a 9700 on AGP 2x![]()
How much better? I was under the impression that the R300 was the best a 3.3v slot could pull.
I have a Radeon 9800 Pro in a Sawtooth. This is a fully 2x AGP compatible card.
And very loud.
Is the Sawtooth still running the stock PSU or did you put in a new PSU?
First thing I'd do is quieten it down as much as possible - another project to pursue.
Haha, indeed. It makes me really sad that so many distro's seem to be in a race to see who can drop i686 the quickest. However, I am confident that SOMEONE will continue supporting i686 well into the future, considering how ubiquitous the hardware is.@sparty411
And if things don't work out, we can just switch to one of the thousands of other distros available to i686.![]()
However, I am confident that SOMEONE will continue supporting i686 well into the future, considering how ubiquitous the hardware is.
However, I am confident that SOMEONE will continue supporting i686 well into the future, considering how ubiquitous the hardware is.
Now that I was able to boot into OpenBSD/XFCE I dare to ask, how to launch Window Maker from the command line.The BSD’s are even more lightweight, OpenBSD has only slightly higher used RAM then Mac OS 9 with nothing open but a GUI (I use the excellent Window Maker based off of NextStep).
Now that I was able to boot into OpenBSD/XFCE I dare to ask, how to launch Window Maker from the command line.
Also don't know, if "pkg_add windowmaker" did install the right thing ...
Put the command to launch windowmaker in your ~/.xsession file, then run "doas rcctl -f start xenodm"
rcctl controls daemons, such as xenodm. Starting xenodm will start X11, and will execute the lines contained in ~/.xsession upon X11 startup.
Oh sorry causing you so much trouble ... I thought it was just a single command like "startxfce4" for the XFCE-desktop ...
This is something I have to dive in more deeply and I have to postpone further efforts to another weekend unfortunately.
BTW, is there an option for VPN(CiscoIPSec) and an RDP-client for OpenBSD, that might give me the option to run them on a PPC in any PPC-version of BSD?
Well, that looks promising!It has an IPSec implementation built-in; look into ipsecctl and ikectl.
You can pkg_add rdesktop for an rdp client.
Well, that looks promising!
But based on my skills I'm gonna need ages to understand - it looks like a learning curve too steep for me.
I don't believe I'm gonne get the knack before retirement - and then I won't have any need for VPN/RDP anymore ...
The BSD’s are even more lightweight, OpenBSD has only slightly higher used RAM then Mac OS 9 with nothing open but a GUI (I use the excellent Window Maker based off of NextStep).