@kas1e My system, which uses QEMU PCI passthrough, works fine with (official/original) pegasos2.rom. It has the U3 update and the latest kernel. This morning I tested (as described here) the exact same “boot.img” disk image with ATI graphics cards in QEMU. It’s the exact same version of kickstart.zip that I use for QEMU PCI passthrough PEG2. I used bboot.fth there as well. I found another issue. If I use non-ATI cards on QEMU PEG2 (without QEMU PCI passthrough - sm501,voodoo3), the system won’t boot either. Here it looks a little different. You can see that the card is initialized (the contents of the QEMU window change), but the system freezes. There’s nothing in the kernel debug logs. If you have the opportunity to test a non-ATI/Radeon card on a real Peg2, maybe you could check that as well. Hmm. Are you using the official Radeon driver or some developer version? Maybe that’s where the problem lies. Does the new pegaso2.rom change anything drastically for Radeon cards? Have you also tested with a Radeon HD card? I have a Radeon RX; I can connect it via QEMU PCI passthrough if you need to check anything else.
EDIT: Just to clarify everything: a Radeon RX card with QEMU PCI passthrough is capable of booting. It runs extremely slowly. I didn’t have access to newer kernel releases for PEG2 or Radeon drivers. If I recall correctly, I also didn’t test the Radeon RX card with the UP3 update for QEMU.
Edited by smarkusg on 2026/5/14 20:29:06 Edited by smarkusg on 2026/5/14 20:34:49 Edited by smarkusg on 2026/5/14 20:37:12
I found another issue. If I use non-ATI cards on QEMU PEG2 (without QEMU PCI passthrough - sm501,voodoo3), the system won’t boot either. Here it looks a little different. You can see that the card is initialized (the contents of the QEMU window change), but the system freezes. There’s nothing in the kernel debug logs. If you have the opportunity to test a non-ATI/Radeon card on a real Peg2, maybe you could check that as well.
But that probably expected, because sm501/voodoo3 is not real cards on your setup, so how can you passthrough with them ? That the same with original and with new firmware, right ? But yes, i will check with putting any non ATI/AMD card to, just to see if there correct fallback, or if firmware can handle anything else too.
I may try to find some PCI/e and AGP versions of some Nvidia/Voodoo cards, those probably will be good to test.
Quote:
Hmm. Are you using the official Radeon driver or some developer version? Maybe that’s where the problem lies.
I use RadeonRX driver 2.23 on real peg2 which should fit someday in enhancer (if it will ever happens), and i also use beta kernel with peg2 fixes for test, so can use it without BBOOT, but that shouldn't matter, because if the same setup works for you with original firmware on qemu, and simple changing on new firmware cause it to not work, then it mean something changes, and that not related to your components.
Quote:
Does the new pegaso2.rom change anything drastically for Radeon cards?
Nope, it didn't change anything for cards, just simple initialization behind bridge and POST running.
Quote:
Have you also tested with a Radeon HD card?
Not for now, but will do. What version of RadeonHD you use ?
Quote:
Just to clarify everything: a Radeon RX card with QEMU PCI passthrough is capable of booting. It runs extremely slowly. I didn’t have access to newer kernel releases for PEG2 or Radeon drivers.
So, RadeonRX cars is booting with both original firmware and new one ? Or only with new one ? Can you try plz to boot RadeonRX without BBOOT on this Update3 (and be sure, that Kickstart.zip contain kernel 54.57 in)
Quote:
If I recall correctly, I also didn’t test the Radeon RX card with the UP3 update for QEMU.
But you tested it now with UP3 update, right ? It works both with original and our firmware ?
Anyway, what i want to say mainly now is that if you have update3 installed, and you surely have kernel 54.57 and BBOOT "only" fix 64/32 address issues, you can try to not use BBOOT and it should works without. Try it plz if you can.
Thanks for tests !
@Mlehto
Quote:
WB naturally launches to screen what is set on screenmode prefs.
So agp port primary allways, pcie primary if only pcie available sounds good.
What i found is : The card which i run POST init on the firmware, will be the one taken as the primary by AmigaOS4.
So, i implemented it like this (at least for now): added "primary-vga" environment, which default value is "vga0", meaning the first video card found during PCI scan. The first one usually a PCI one (not AGP one) in the pci probing. So if you have 2 video cards in peg2 , then "vga0" mean pci one, and "vga1" an agp one. If card running alone, then "vga0" will handle any card it find be it agp or pci/pcie.
The good thing is that we don't need removing cards or disconnecting cables, I tested right now with both video cards connected to monitor at the same time : RadeonRX connected via HDMI cable, and Radeon9250 connected via VGA cable to same monitor at the same time, and simple set to "vga0", make firmware outputs to RadeonRX and amigaos4 boots to RadeonRX as the main one, and simple set to "vga1" make Radeon9250 in AGP output on firmware, and amigaos4 take this one as the primary to boot from.
@kas1e I have the latest kernel and UP3 on my current system. I’ll do a fresh PEG2 installation today, just to be on the safe side, on a disk image. I’ll update to UP3 and connect it to QEMU instead of NVMe. Currently, on QEMU PEG2 passthrough, I’m using a real NVMe drive – the NVMe controller is passed through to QEMU. With a new system image, it will be easiest for me and we’ll be 100% certain about my system. I can then also simply boot the system with or without bboot. I would have modified the installation disc for PEG2, but from what you wrote, kernel version 54.57 is required, so that’s out of the question. I also don’t know if the RadeonHD drivers themselves have any requirements regarding the system version
The strange thing is that the ATI card in QEMU, ‘-device ati-vga,model=rv100’, works. Even the ‘VGABIOS’ patch doesn’t work on it, and it’s emulated in the same way as the sm501 and Voodoo3. I haven’t checked the RadeonRX card yet. I’ll let you know what else I’ve noticed and what works and what doesn’t.
The strange thing is that the ATI card in QEMU, ‘-device ati-vga,model=rv100’, works. Even the ‘VGABIOS’ patch doesn’t work on it, and it’s emulated in the same way as the sm501 and Voodoo3
The switch to Balaton's video driver happens only if you use rv100, yes, but that probably out of firmware question and it all the same with original firmware too (at least as far as i can tell).
@smarkusg OK, new system – full update to UP3 and kernel 54.57 Booting from amigaboot.of gives the same result as with bboot.fth
RTAS instantiate base=01EE8BE0 size=00002A90 blob=00002A90 src_hash=E220CAD1 dst_hash=E220CAD1 words=7CA802A6 48000225 4800011D 480000ED
RadeonRX (2): Could not identify the chipset
graphics.library AltiVec/VMX enabled
graphics.library PPC74xx optimizations enabled
RadeonHD.card (0): RadeonHD.chip 3.7 (19.11.2019)
RadeonHD.chip (0): ERROR: Could not get the video RAM resource range
RadeonHD.chip (0): RadeonHD card closed
graphics.library cannot configure your graphics board!
Either your board is not supported or there's a configuration problem.
Did you install PCIGraphics.kmod?
I'll add this too – I'm not sure if it'll be of any use
pcidev: cls=0x60000 v=0x11AB d=0x6460 rom...
rom: 0:0.0 size ret=0 size=0x0
rom: no ROM BAR/size 0
pcidev: rom err=-3440
pcidev: builtin cls=0x60000...
pcidev: builtin err=-3439
pcidev: cls=0x30000 v=0x1002 d=0x683F rom...
rom: 0:1.0 size ret=0 size=0x20000
rom: addr=0xC0100000 hbridge=1
rom: write BAR ret=0 reg=0xC0100001
rom: cmd=0x100002
rom: first=55 AA 80 E9 all_ff=0 all_00=0
rom: property saved len=0x20000
rom: magic 55AA at 0x0
rom: PCIR at 0x228
rom: image type=0x0 vendor=0x1002 device=0x683F
rom: x86 BIOS image size=65536
rom: prepost BAR0x18 space=3 addr=0x0,0xC0140000 size=0x0,0x40000
rom: prepost BAR0x20 space=1 addr=0x0,0x1000 size=0x0,0x100
rom: id banner "AMD Radeon HD 7700 Series"
x86emu: enter 0:1.0 romsize=65536 io_base=0xF8000000
x86emu: BE_init ok
x86emu: call POST C000:0003 AX=0008
x86emu: POST returned font=8192 text=8192
x86emu: IVT10=C000:039A IVT42=F000:F065
x86emu: call INT10 mode3
x86emu: INT10 returned font=8192 text=8192 eax=0x3
x86emu: call VBE 4F00
x86emu: VBE 0x300
x86emu: VBE memory 16384K
x86emu: VBE product "VERDE"
x86emu: font validation ok
x86emu: success
rom: x86emu post_ok=1 err=0
pcidev: rom err=0
pcidev: cls=0x40300 v=0x1002 d=0xAAB0 rom...
rom: 0:2.0 size ret=0 size=0x0
rom: no ROM BAR/size 0
pcidev: rom err=-3440
pcidev: builtin cls=0x40300...
pcidev: builtin err=-3439
My RadeonHD also works without any issues on QEMU PCI passthrough, on an A1 emulation booted from a ‘ROM’ (without bboot), and I can see the U-Boot information on the Radeon display – if that information is helpful.
I’ll check what’s happening on RadeonRx as well.....
@smarkusg So to make it short, bboot is not need it with original (no our new) firmware and all works without with update3's kernel, right ? You can boots from RadeonHD with no probs ?
(i just need that to understand if we can get rid of bboot now and it's fixes for tests).
@sailor Quote:
Unfortunatelly my Pegasos is now in the box - I have to rebuild my computer place
You have time for : i ordered Promise TX4 pci2sata card, as well as 3112 and 31114, as well as few Geforce modesl (one agp and one PCIe), so want to make it all works too and to have more real live test cases.
(i just need that to understand if we can get rid of bboot now and it's fixes for tests).
Thank you so much ;P ... it took me a bit of effort to get it running It's a bit tricky to run Peg2 QEMU PCI passthrough on a computer where you only have remote access, especially when the original pegasos2.rom freezes during RadenHD initialization. I have scripts, but I had to improvise a bit here.
YES. It is possible to run QEMU PEG2 RADEONHD with QEMU PCI passthrough without bboot on kernel 54.57 on the original pegasos2.rom.
YES. It is possible to run QEMU PEG2 with QEMU PCI passthrough without bboot on kernel 54.57 on the original pegasos2.rom.
Ok, good ! One issue less ! Not using bboot there make it easy to test things correctly. And in case with new firmware UDMA is added, so booting will be same fast as with bboot.
Now i need to understand our current mambo-jambo, so far it looks like this:
1). original firmware: you can boot via passthrough with RadeonHd and can boot with RadeonRX (just RadeonRX slow like hell), that right ?
2). with our firmware, you still can boot with RadeonRX (while still slow), but can't RadeonHD anymore, and have " ERROR: Could not get the video RAM resource range". That right too ?
It's quite interesting why things changes...
For now, while i trying to fix RTAS issue in the firmware (and there indeed was issue because of which the RTAS scan code of kernel wasn't working for anything in bus more than 0), i found that even RadeonRx start to give me " ERROR: Could not get the video RAM resource range", but then, with beta kernel it works for RadeonRx, so .. i snork something somewhere close enough ..
ps. can you tell me plz what version of RadeonHD and RadeonRX you use for tests ?
@kas1e We need to do a quick recap of what I’ve been testing on QEMU. I haven’t tested anything yet on a Radeon RX with QEMU, the new pegasos2kas1e.rom, or the original pegasos2.rom with the UP3 update on my machine. Maybe I wrote something wrong or you misunderstood. Someone might read what we wrote in a few days and won’t be able to understand a thing
1. On QEMU without PCI passthrough booted via pegasos2kas1e.rom (not bboot), only the emulated ATI RV100 graphics card works: “-device ati-vga,model=rv100,guest_hwcursor=on” sample video - > https://youtu.be/-eS3WjsMX4E
2. Tests on QEMU PCI passthrough have so far been performed on the “AMD Radeon HD 7700 Series” Asus Radeon HD 7750 card. Emulation and successful system boot QEMU PCI passthrough with a Radeon HD card using an older kernel < 54.57 (without UPDATE 3 installed) works only with bboot (bboot.fth) and the original pegasos2.rom Emulation and successful system boot via QEMU PCI passthrough with a RadeonHD card using kernel 54.57 (with UPDATE 3 installed) works via bboot (bboot.fth) with the original pegasos2.rom and the standard boot mode (amigaboot.of) Currently, the system is unable to boot correctly on my system in QEMU emulation with pegasos2kas1e.rom on a system with kernel 54.57 via bboot (boot.fth) and in standard boot mode (amigaboot.of)
I was going to install RadeonRX yesterday and test it, but you wrote to check the system boot with amigaboot.of. I haven't tested anything yet with the pegasos2kas1e.rom and the RadeonRX card. From now on, I'll mention which card I used in every post to make things clearer.
On QEMU without PCI passthrough booted via pegasos2kas1e.rom (not bboot), only the emulated ATI RV100 graphics card works: “-device ati-vga,model=rv100,guest_hwcursor=on
By "works" you mean can't boot to firmware with correct output, or, can't boot to amigaos4 with Balaton's driver ? If the later, that probably exactly the same with original firmware too ?
I mean is there any difference with original firmware in that terms ? Because as for me, the new one can boot to firmware and with vga, and with cirrus-vga, and with ati-vga, etc, while original firmware can't with some. But then, booting to amigaos4 from CD installation with Balaton's driver can happens only with rv1000 (same on original firmware and on new one).
@kas1e “works” = QEMU and the system will boot from pegasos2_kas1e.rom on an emulated ATI card “-device ati-vga,model=rv100,guest_hwcursor=on”. You don't even need to specify the “rom” file Other emulated cards in QEMU that work with AOS4 (sm501, voodoo3) cause the system to freeze during startup (the system won’t boot). That’s what I meant
I’ve added a sample video to the previous description.
edit: I've finished testing the Radeon RX. My card is an ASUS RX 560 Dual Fan OC 2 GB. It only works with bboot (bboot.fth) on kernel 54.57 and the original pegasos2.rom. It doesn't work with pegasos2_kas1e.rom, amigaboot.of, or boot.fth. I'll add more details here later.
@smarkusg I also can't follow what you tested and what works and not. You should be more specific about the tests and results. Such as: describe exactly what you tested with QEMU command line then say how it did not work. Just saying does not work is not enough to understand the issue. The ati-vga is only meant to work with model=rv100 because PCIGraphics.card only recognises Radeon cards no Rage cards so even if you get picture in firmware AmigaOS won't load the driver. You said sm501 does not work with @kas1e's rom. Does it work with that rom + bboot? Maybe there's either some problem with PCI init or RTAS.
For now, while i trying to fix RTAS issue in the firmware (and there indeed was issue because of which the RTAS scan code of kernel wasn't working for anything in bus more than 0), i found that even RadeonRx start to give me " ERROR: Could not get the video RAM resource range", but then, with beta kernel it works for RadeonRx, so .. i snork something somewhere close enough ..
I think Hans had to fix some more PCI issues in Pegasos2 kernel than 64bit BARs and IRQ setting that BBoot patches so unless those are also released in Update 3 it probably won't work. You might be able to patch some of that in the firmware by presinting a different device tree to AmigaOS but that would probably break new kernels so maybe just get the fixed kernel released or leave it for later when that kernel will be available otherwise you cause yourself unnecessary issues.
Once it will works, i can simple release just a smartfirmware part with a python script which build a new rom from original (extracting bootstrap, combine with our smartfirmware, and create new rom). This way ppls already can use it, while i will worry about bootstrap replacement, which, IMHO, will be harder part.
Uploading the sources to a repo and let people test it review it and help fixing it could be done even when it's not finished yet. That way you don't have to do everything alone.
“works” = QEMU and the system will boot from pegasos2_kas1e.rom on an emulated ATI card “-device ati-vga,model=rv100,guest_hwcursor=on”. You don't even need to specify the “rom” file Other emulated cards in QEMU that work with AOS4 (sm501, voodoo3) cause the system to freeze during startup (the system won’t boot). That’s what I meant
But that the same with original firmware, isn't it ?
@kas1e All graphics cards emulated in QEMU and supported by AOS4 work correctly with the original pegasos2.rom. You don't even need to use bboot. They also work correctly with QEMU AmigaOneXE using the original uboot. If you’re asking about “-device ati-vga,model=rv100,guest_hwcursor=on”—yes, it works on pegasos2.rom with bboot and amigaboot.of.
As far as I know, bboot was created to avoid using SmartFirmware and uboot in QEMU for PEG2 and A1. It is closed-source software, and there is no way to fix it or access the source code. You can freely use either bboot or the original SmartFirmware/uboot for PEG2 and A1 emulation. Bboot also fixes a few issues—for example, in PEG2 emulation, the memory limit of 1GB (real hardware also had issues with certain RAM modules) when using pegasos.rom has been fixed, etc.
@balaton Quote:
I also can't follow what you tested and what works and not. You should be more specific about the tests and results.
I'll give it a try. I'm assuming (probably wrongly) that everyone knows exactly what I mean. I'll try to explain it in more detail.
@smarkusg wait wait, forget about bboot. It have no needs since in latest kernel issues which fix bboot fixed. Now let's not refer to it, anymore (for our tests at least), because all tests since that on kernel 54.57. So it's all amigaboot.of now, and no mess.
Next, i still didn't get about "graphics cards supported by AOS4"..
Original firmware rom, works only with:
-device VGA with VGABIOS-lgpl-latest.bin. -device ati-vga with rage128progl16mb.VBI
maybe with latest releast with rv100, dunno.
Then, new firmware rom, works with:
- "currus-vga" - "VGA" with VGABIOS-lgpl-latest.bin - "VGA" with default seabios's vgabios-stdvga.bin - "ati-vga" with rage128progl16mb.VBI - "ati-vga" with default vgabios-ati.bin - "ati-vga,model=rv100" with default vgabios-ati.bin
By "works" i mean it show itself on the firmware output screen. And there i mean only firmware, not amigaos4 itself.
Now, when you say that "All graphics cards emulated in QEMU and supported by AOS4 work correctly with the original pegasos2.rom. ", it make it sounds , like with new firmware they stop working ? Or what ?
I just trying to understand what bug you found are. For me, with new firmware much more cards are visibly in firmware. Or there is issue with exactly boot to amigaos4 , and only with new firmware ? If so, plz, give me the full lines of your qemu run , which works with original firmware and didn't with new firmware, so i simple can test it myself on my QEMU too.
Doh, quotes doent work with ipad/vivaldi. Newer mind.
That part I didnt understood.What you mean you run POST? By setting vga0/vga1?
Protocol sounds fair and good. I personally want better card for higher resolution. As bonus there is all 3D&CO. So i probably drop agp card. But needs may vary and vga0/vga1 resolves that all. Well done :)
News feed
OS4 Feedback forum
OS4Depot Feedback forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
