Dunno why there 2 displays, but that what each of them show:
Could it be a TV out? If not then a duplicate device for extra VGA or DVI perhaps. My 9200SE used to show extra devices, which had a TV out, and could display UBoot on my TV. Been a while since I checked the PCI config.
The main difference in the RTL 8029 and 8139 drivers is that AFAIK the 8139 one uses DMA, while the 8029 is PIO-only, which should be much easier to emulate.
Also I've found the OS4 8139 driver to be crippled somewhat. I can never get full speed out of it. Whatever that is about. If I use Linux it can download at full speed.
Also, strangely, Linux can use the X1000 Ethernet. But OS4 cannot. Except for a buggy driver which by comparison doesn't count. I thought the X1000 was made for AmigaOS but it only works fully in Linux.
However, it is not possible to set up an internet connection via DHCP using Roadshow. There is no other solution like with the rtl8139 driver at the moment.
That log doesn't make sense. First it can't open the network device and after it can. Then it's able to query it.
Also that Dialer is really old by now. Looks like it needs an update. It does need an update, since 15 years, because by default Ethernet devices have been given an icon that tries to make a dial up connection, that always complains when you open it and the Workbench thinks is a mountlist!
Can you boot Linux on real pegasos2 and get lspci -v and /proc/interrupts from it?
Don't have linux installed on peg2, but do have spare SSD, so if there needs may install it if it will of any help.
edit: maybe you aware of the best currently support linux distro for pegasos2 ?
@All What is also interst me in terms of real pegasos2 hardware : all the PCI slots in here is 33MHZ, but AGP slot (which is the same PCI) is 66MHZ. So using PCI to PCIE adapters, we will be able to only have 33MHZ PCI for video , which on real hardware will be surely worse, if, in comprasion, use some AGP to PCIE adapter. I am not sure if any is present and sold, but i am sure there should be somewhere AGP to PCI line adapters, as it mostly just an the same PCI, with different slot..
Edited by kas1e on 2023/7/8 9:22:39 Edited by kas1e on 2023/7/8 9:31:42
Don't have linux installed on peg2, but do have spare SSD, so if there needs may install it if it will of any help.
Linux wont display additional information compared to AmigaOS tools like Ranger or shell PCI tools anyway with which you can check BARs, IRQs, etc. as well. And even if Linux does display some more information: It's irrelevant what Linux does for emulating AmigaOS.
@kas1e You don't need to install Linux just boot a live CD or rescue system and get the info needed which should not need a full install. I don't know what's the best distro but I think this should at least boot with 'boot install/pegasos': https://cdimage.debian.org/cdimage/archive/8.11.0/powerpc/iso-cd/ I used the netinstall CD for testing, select rescue in boot menu then you either go through the questins it asks just accepting defaults or Tab to the Back button then select run a shell from the menu (or somthing similat, I write from memory).
Linux wont display additional information compared to AmigaOS tools like Ranger or shell PCI tools anyway with which you can check BARs, IRQs, etc. as well. And even if Linux does display some more information: It's irrelevant what Linux does for emulating AmigaOS.
At least Linux displays info in text which is easier to handle than Ranger or can you get a text report that you can easily post with ranger? Also Linux may give error messages in log, we have its source to check what is happening if a problem can be reproduced with Linux. And finally it's not irrelevant because we don't emulate AmigaOS but emulate pegasos2 so if we can find a difference between real machine and emulation under any OS that helps to improve emulation (even for AmigaOS).
Also I don't know what shell PCI tools are available for AmigaOS so if you have more info on those that might help.
Also I don't know what shell PCI tools are available for AmigaOS so if you have more info on those that might help.
I don't know either which tools are available. OS4 developers, and probably OS4 beta testers as well, had access to such shell PCI (and Zorro bus) tools long before any GUI tools like Ranger were implemented, but I don't know if any of them was ever available to end users. The old Zorro II/III ShowConfig command displays some PCI info on NG Amigas as well, but I don't know if "ShowConfig DEBUG" includes enough information.
Just to update, I think I’ve reached the limit of what I can do without being more of a burden than a help. I’ve managed to determine that the hangs in os4 are not specific to networking. If I add emulated sound hardware, it hangs too. I will try disabling the startup sound and see if I can use the os just without actually triggering any sound in which case I may be able to get some device info and stuff but of course I’ll be limited in what I can do.
I am running Qemu built from master incidentally. It was the easiest way since Ubuntu’s repo is still on qemu 6. I fetched / updated yesterday I believe.
I’ve managed to determine that the hangs in os4 are not specific to networking. If I add emulated sound hardware, it hangs too. I will try disabling the startup sound and see if I can use the os just without actually triggering any sound in which case I may be able to get some device info and stuff but of course I’ll be limited in what I can do.
I have tried the script you gave me, and I am getting the same result - The GFX card is recognised so OS4 boots to workbench, but the whole OS hangs after a short amount of time.
I will get the Linux iso on usb and boot from that to get some pci output, both with and without the script. That was the autopilot kicking in there... dont need to do that for QEMU :)
@balaton I were able to boot to linux as you advice, so want to clarify little bits : "cat /proc/interrupts" will be enough for second part ?
And, do you aware if serial output should work if i will just do "echo aaa >/dev/ttyS0" ? Why i ask, it's because i did the commands you need, have output, but to save it in text i need to throw it on serial (which is working of course, as it display pegasos2 init stages, etc and i have "Linux/PPC 3.16.0" out. But then, when i tried from the shell do "echo aaa >/dev/ttyS0" it didn't works, same as if i use /dev/serial.. I may forget somethings about linux, but should't it just works like that ?
I know an OS without sound isn't much fun, or network but it would be useful to me, at least if you could remove the sound device from your qemu command and see if your OS is then stable until you use the network.
To do that will mean that your addresses are going to change, but if you paste the output from properties again then I can update your script. It sounds like if you add
,addr=4
to the gpu device line(s) then hopefully only the easy part of the addresses will change and I can tell you where they go very easily. I didn't try that myself yet.
I don't think it will get us any further forward but it will at least ensure it's not anything specific to my setup.
(ignore the BAR numbers being odd-numbers, as I believe thats a simple bug in the code for displaying the data for 64-bit BARs - increments the number by 1 before displaying it!)
ok show-pci-full
Br Bus Dv F Vend Dev Vendor Chip Description
===============================================================================
0 0 0 0 11AB 6460 Marvell MV6436x System Controller for PowerPC Processors
0 0 1 0 1234 1111 Technical
8000.0008- 80FF.FFFF BAR 0 MEM
8100.0000- 8100.0FFF BAR 2 MEM
0 0 12 0 1106 8231 VIA VT8231 PCI to ISA Bridge
0 0 12 1 1106 0571 VIA VT82C586/596/686 PCI IDE Controller
0000.1001- 0000.1007 BAR 0 I/O
0000.100D- 0000.100F BAR 1 I/O
0000.1011- 0000.1017 BAR 2 I/O
0000.101D- 0000.101F BAR 3 I/O
0000.1021- 0000.102F BAR 4 I/O
0 0 12 2 1106 3038 VIA VT83C572 PCI USB Controller
0000.1041- 0000.105F BAR 4 I/O
0 0 12 3 1106 3038 VIA VT83C572 PCI USB Controller
0000.1061- 0000.107F BAR 4 I/O
0 0 12 4 1106 8235 VIA VT8235 Power Management Controller
0 0 12 5 1106 3058 VIA VT82C686A/B AC97 Audio Codec
0000.1101- 0000.11FF BAR 0 I/O
0000.1031- 0000.1033 BAR 1 I/O
0000.1035- 0000.1037 BAR 2 I/O
0 0 12 6 1106 3068 VIA VT82C686/686A/686B AC97 Modem Codec
1 0 0 0 11AB 6460 Marvell MV6436x System Controller for PowerPC Processors
1 0 1 0 1002 6811 ATI
0000.0000.C000.000C-0000.0001.CFFF.FFFF BAR 1 MEM
0000.0000.D000.0004-0000.0001.D003.FFFF BAR 3 MEM
0000.1001- 0000.10FF BAR 4 I/O
D004.0000- D005.FFFF BIOS MEM
1 0 2 0 1002 AAB0 ATI
0000.0000.D006.0004-0000.0001.D006.3FFF BAR 1 MEM
ok
smartfirmware .properties (/pci@C0000000/display@1) - before script
ok show-pci-full
Br Bus Dv F Vend Dev Vendor Chip Description
===============================================================================
0 0 0 0 11AB 6460 Marvell MV6436x System Controller for PowerPC Processors
0 0 1 0 1234 1111 Technical
8000.0008- 80FF.FFFF BAR 0 MEM
8100.0000- 8100.0FFF BAR 2 MEM
0 0 12 0 1106 8231 VIA VT8231 PCI to ISA Bridge
0 0 12 1 1106 0571 VIA VT82C586/596/686 PCI IDE Controller
0000.1001- 0000.1007 BAR 0 I/O
0000.100D- 0000.100F BAR 1 I/O
0000.1011- 0000.1017 BAR 2 I/O
0000.101D- 0000.101F BAR 3 I/O
0000.1021- 0000.102F BAR 4 I/O
0 0 12 2 1106 3038 VIA VT83C572 PCI USB Controller
0000.1041- 0000.105F BAR 4 I/O
0 0 12 3 1106 3038 VIA VT83C572 PCI USB Controller
0000.1061- 0000.107F BAR 4 I/O
0 0 12 4 1106 8235 VIA VT8235 Power Management Controller
0 0 12 5 1106 3058 VIA VT82C686A/B AC97 Audio Codec
0000.1101- 0000.11FF BAR 0 I/O
0000.1031- 0000.1033 BAR 1 I/O
0000.1035- 0000.1037 BAR 2 I/O
0 0 12 6 1106 3068 VIA VT82C686/686A/686B AC97 Modem Codec
1 0 0 0 11AB 6460 Marvell MV6436x System Controller for PowerPC Processors
1 0 1 0 1002 6811 ATI
0000.0000.C000.000C-0000.0001.CFFF.FFFF BAR 1 MEM
0000.0000.D000.0004-0000.0001.D003.FFFF BAR 3 MEM
0000.1001- 0000.10FF BAR 4 I/O
D004.0000- D005.FFFF BIOS MEM
1 0 2 0 1002 AAB0 ATI
0000.0000.D006.0004-0000.0001.D006.3FFF BAR 1 MEM
ok