-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Graphical Corruption with Rage 128 on B&W G3 #3
Comments
I'll reverse the OS9 driver for that card when I get time, to see if I'm missing anything in particular, but given that I don't have the hardware, there's only so much I'll be able to do. What does open firmware fcode set up the card to be? I just blindly try to set 32bpp, so if some card comes up in 1024x768 and doesn't have enough vram to handle 32bpp in that resolution I'm sure there will be issues there. |
(some reversing later) ...turns out the various MMIO registers are in totally different positions on these cards! no wonder the modeswitch isn't working correctly lol |
Can you try the latest release? Hopefully it will at least try to modeswitch, but without having the hardware there's not much else I can suggest other than experimenting with the timing registers... |
Can you try this? This adds a write to the hsync start/width register, which I only didn't implement because I observed no difference on lombard, but probably is important on desktops lol. |
Unfortunately no luck with that either, exact same thing. |
Yeah, I just found out that the MMIO base address for the rage4 cards are at a different assigned-address. Try this one. |
yeah, that's probably DSP timing issues... can you try this one? |
Got the same result with it. |
ok, so the hsync register doesn't matter it seems? can you try this? |
ok, can you try this one? just want to see what it does when the DSP timing registers aren't touched: |
With that one back to the normal blue/triplicate stuff. |
looking at the register documentation again, one of the DSP registers are slightly different on rage4, two of the fields changed positions. try this one: |
ok, so it is DSP timing stuff... just saw an issue with the DAC gamma table, so hopefully this at least fixes the colours: |
ok, can you try this one? |
this is now just trial and error of dsp timing register changes and observing the output: |
This one lost the color lines, but we're back to the same missing text as the 2nd previous test. |
tried reimplementing how the linux driver sets the DSP timings, along with reimplementing how the OS9 driver gets the vclk |
With this latest test zip, NT bootloader freezes here during initial isntall: Not sure if this was supposed to be a fully working ISO or if it has bits missing, apologies if it is the latter. Also I see that the instructions say to install "PowerMac General HID & Storage" but it appears to be named "ADB and USB" in this build. |
Just curious, did you get through the text-mode setup and all that jazz yet? I'm not able to actually make it through the setup at all, documented here: #5 |
No, I only got as far as loading the drivers - I hadn't yet been asked to select a keyboard layout. Happy to turn this into a new issue or add to #5 to get it out of this now resolved topic. |
OK, this crash on boot looks like HAL dying early. Possibly PCI related, which I tried to work around as I read somewhere that blindly enumerating the PCI bus on these systens can freeze, but I probably didn't do it right due to lack of real hardware to test with. Different issue anyway. (And yes, the driver name is different, due to being my own test ISO rather than a properly cleaned up release build.) Regarding this specific issue, I'll clean things up for commit and release later. |
Another fun not-Powerbook bug. The factory Rage 128 does not seem to be functioning as intended with the ATI driver support. The display has vertical lines through and text is both massive and wrapping. Image is attached.
The text was updated successfully, but these errors were encountered: