Who's Online |
28 user(s) are online ( 22 user(s) are browsing Forums)
Members: 2
Guests: 26
kishigo, daveyw,
more...
|
|
Headlines |
-
arabic_console_devicepro2.lha - driver/input
Apr 28, 2025
-
openmedalofhonor.lha - game/fps
Apr 27, 2025
-
reportplus.lha - utility/misc
Apr 27, 2025
-
astone.lha - graphics/viewer
Apr 26, 2025
-
amigagpt.lha - network/chat
Apr 25, 2025
-
privoxy.lha - network/misc
Apr 25, 2025
-
wormhole.lha - network/misc
Apr 25, 2025
-
vasmm68k_mot.lha - development/cross
Apr 24, 2025
-
vasmm68k_std.lha - development/cross
Apr 24, 2025
-
vasmppc_std.lha - development/cross
Apr 24, 2025
|
|
|
|
|
Re: QEMU GPU vfio-pci pass through
|
Posted on: 4/13 22:17
#101
|
Quite a regular 
|
@joerg Quote: Only relevant difference should be the '/', on Italian keyboards it's the '-' key left to the right shift key, Not really as the " is also different. On a US English keyboard it's two keys right from L: https://en.wikipedia.org/wiki/File:KB_United_States-NoAltGr.svg[/
|
|
|
|
|
|
Re: QEMU GPU vfio-pci pass through
|
Posted on: 4/13 21:57
#102
|
Quite a regular
|
@smarkusg
If you have a RadeonHD card the pegasos2 and sam460ex versions come with a RadeonHD light driver that can't do 3D but should be enough to get picture for testing. It seems to be missing from amigaone version though but maybe it's in an update? For RX card I think you need Enhancer (and for fully using an HD card but at least for testing the light driver might be enough until you get a full driver). The RadeonHD lite driver may also need new enough PCIGraphics.card, I don't know if the amigaone version is new enough but the one from sam460ex that works with the sm501 possibly also works with the RadeonHD that comes with the sam460ex install CD.
|
|
|
|
|
|
Re: QEMU GPU vfio-pci pass through
|
Posted on: 4/13 21:54
#103
|
Quite a regular
|
@white
OK, so you have bochs-display selected there and then you type the " /failsafe" io command blindly in that window. Try with English layout. If successful you should get an ok prompt in the other window where you started QEMU from and got the errors.
|
|
|
|
|
|
Re: QEMU GPU vfio-pci pass through
|
Posted on: 4/13 21:42
#104
|
Quite a regular
|
@white
What do you have in the menu "Visualizza"?
|
|
|
|
|
|
Re: QEMU GPU vfio-pci pass through
|
Posted on: 4/13 21:40
#105
|
Quite a regular
|
@white Quote: tried in qemu compat-monitor terminal the keyboard is Italian and the symbols are correct That one is handled by QEMU so it may use your host's layout but the guest window is handled by pegasos2.rom which has no way to know you're using what layout so it likely defaults to English keyboard.
|
|
|
|
|
|
Re: QEMU GPU vfio-pci pass through
|
Posted on: 4/13 21:38
#106
|
Quite a regular
|
@white
It's quite possible that the pegasos2.rom defaults to English keyboard as there's no way to configure keyboard that early so this can also be a problem. This would be the same as on real machine where the firmware probably also uses English layout and only when the OS boots will it change to other layout. Also I don't know what you call "parallel" terminal but it's what says Guest has not initialized display (yet) and should be labelled bochs-display in the view menu. There may also be a parallel0 window but that's not what you need, that shows data from the parallel port.
|
|
|
|
|
|
Re: QEMU GPU vfio-pci pass through
|
Posted on: 4/13 21:28
#107
|
Quite a regular
|
@white
The bochs-display also has a rom by default that also crashes. So disable it and use -device bochs-display,romfile="" instead. You don't get separate windows because using gtk display where these are tabs or available from the view menu. Type the " /failsafe" io command in the bochs-display window/tab whatever it is. To see the output from the passed through card you need a monitor connected to it, you won't see anything from that on the host.
|
|
|
|
|
|
Re: QEMU GPU vfio-pci pass through
|
Posted on: 4/13 20:57
#108
|
Quite a regular
|
By the way, anybody else managed to get it work following this thread?
|
|
|
|
|
|
Re: QEMU GPU vfio-pci pass through
|
Posted on: 4/13 20:54
#109
|
Quite a regular
|
@white
I wrote above quite a few times now that you MUST PUT A SPACE BETWEEN " AND / IN THE " /failsafe" io command. If you did not do that and typed what you posted above then that's why you don't get the ok prompt. Or you're typing it in the wrong window. After adding -device bochs-display to QEMU command you should see a black window with text in the middle saying the guest did not init display. That's where you should type and while typing you would see more errors on the serial window. If you typed the command correctly it should give you an ok prompt where the errors were. Then you can leave the black window. You won't see anything in the black window, it's just to capture keyboard and mouse events for the guest.
|
|
|
|
|
|
Re: QEMU GPU vfio-pci pass through
|
Posted on: 4/13 20:34
#110
|
Quite a regular
|
@smarkusg Quote: Use your old command line with ‘-device VGA,romfile=’ and older qemu. Don't do that. Adding that VGA card prevents the passed through card BIOS to access VGA ports. Even if the BIOS does not run correctly it may be needed to init the card correctly so don't add any other VGA device just the passed through card. The bochs-display does not have VGA part so you can use that. It's true you can also type the boot command instead of the " /failsafe" io blindly, it's just easier to see what you do so getting a prompt may help.
|
|
|
|
|
|
Re: QEMU GPU vfio-pci pass through
|
Posted on: 4/13 20:32
#111
|
Quite a regular
|
@white Quote: It keeps crashing giving me a series of errors What do you mean by crashing? Seeing the errors from BIOS emulator in firmware is normal, don't care about those. Just try typing
" /failsafe" io
after clicking in the window that says guest has not initialized display yet. To get that window you need to add -device bochs-display to QEMU command line. While typing there you might see more errors but don't care about them. If you typed the command correctly with space after first quote and no typos then you should see an ok prompt where you got the emulation errors before. Then you can leave the guest window with Ctrl+Alt+g and can use the ok prompt to enter the boot hd bboot.fth command (after you've copied bboot, bboot.fth and Kickstart.zip to the boot volume as we said before).
|
|
|
|
|
|
Re: QEMU GPU vfio-pci pass through
|
Posted on: 4/13 20:26
#112
|
Quite a regular
|
@joerg Quote: As an alternative you could try changing the firmware stdin and stdout from keyboard/display to serial. On U-Boot systems that's done using
setenv stdin serial
setenv stdout serial
saveenv
, but I don't know how it works in the Pegasos2 SmartFirmware. Won't work, pegasos2 does not emulate nvram and it's easier to type one line than three so just do " /failsafe" io with space after first " !
|
|
|
|
|
|
Re: QEMU GPU vfio-pci pass through
|
Posted on: 4/13 18:38
#113
|
Quite a regular
|
@white Do you see anything on the monitor attached to the passed through card? It started but the bios emulator cannot run the BIOS of the card. This may or may not be a problem. If you see nothing on any of the outputs of the passed through card you can try to get a prompt on serial. I forgot that you also need a way for input so you need to add -device bochs-display which will open an empty window that you can type into even if you see nothing. Enter there:
" /failsafe" io
then you should get an ok prompt on serial. You need a space after the first quote char exactly as above. You'll only see more errors while typing but if typed correctly this should get a prompt on serial and then you can use the serial window to enter the boot command.
|
|
|
|
|
|
Re: QEMU GPU vfio-pci pass through
|
Posted on: 4/13 17:44
#114
|
Quite a regular
|
@white Quote: qesudo qemu-system-ppc -M pegasos2 -bios /home/white/Scaricati/pegasos2.rom -m 1024 -serial stdio -device VGA,romfile="" -drive if=none,id=hd,file=/home/white/Scaricati/32gb.raw,format=raw -device ide-hd,drive=hd,bus=ide.1 -netdev user,id=tap0 -device rtl8139,netdev=tap0 -vga none -drive if=none,id=hd1,file=/home/white/Scaricati/coffin.raw,format=raw -device ide-hd,drive=hd1,bus=ide.1 -device vfio-pci,host=06:00.0,bus=pci.0 -device vfio-pci.host=06:00.1,bus=pci.0 -accel tcg This command is unnecessarily complicated and also wrong. You're adding here a VGA card next to the passed through card so when the BIOS tries to access the VGA resources of the passed through card it gets to the emulated VGA not the ATI card. Therefore it can't init the ATI card and you get no picture. Try this simpler command instead that should do the same:
sudo qemu-system-ppc -M pegasos2 -m 1024 -bios pegasos2.rom -serial stdio -drive media=disk,format=raw,file=32gb.raw -drive media=disk,format=raw,file=coffin.raw -netdev user,id=net -device rtl8139,netdev=net -vga none -device vfio-pci,host=06:00.0,bus=pci.0,x-vga=on,multifunction=on -device vfio-pci,host=06:00.1,bus=pci.0
|
|
|
|
|
|
Re: QEMU GPU vfio-pci pass through
|
Posted on: 4/12 11:41
#115
|
Quite a regular
|
@white
Your libfuse installation seems to be broken, I don't know how could configure detect it but then it does not work. Either install the appropriate devel package for fuse or add --disable-fuse to configure as fuse is not needed anyway.
|
|
|
|
|
|
Re: QEMU GPU vfio-pci pass through
|
Posted on: 4/12 10:51
#116
|
Quite a regular
|
@white
How do we know without you telling what error you get? But if QEMU compiled you don't have to install it, you can run it from build dir: cd build; ./qemu-system-ppc...
|
|
|
|
|
|
Re: WebKit based browser initiative
|
Posted on: 4/5 14:04
#117
|
Quite a regular
|
@TheMagicSN Quote: Bsd licemce is less restrictive not more restrictive (typo?) bsd does not Require copyleft. I meant BSD is more restrictive than public domain or a license that says do whatever you want. With BSD you can use the code even in closed source products but you can't claim you wrote it and you have to say where the code comes from in binaries and source. For example if you have an Apple product check the legal notices in About, they have a lot of such copyright messages to show where parts come from. BSD license does not require the source to be published but you also can't claim copyright for it and have to keep the original copyright message. The GPL is even more restrictive and says you can only use the source such that it won't become a closed source software. You can still make changes to GPL software for yourself as long as you don't distribute it but if you give your modified version to somebody then they are also entitled to get the sources for it so they can also make changes or adapt it to their needs. The LGPL requires this only to the software itself, usually a library which then can be used by closed source project without making the project that uses it have to be open source and only requires changes to the library itself to be given back to community but GPL also requires anything that links to it to be GPL so you can't even use it as a library in non-open source projects.
|
|
|
|
|
|
Re: QEMU GPU vfio-pci pass through
|
Posted on: 4/5 13:47
#118
|
Quite a regular
|
@white I think slowing a bit and thinking and knowing which command you do why helps. It's hard to guess what your problem is but I think you should verify if the card is still assigned to vfio-pci. I've posted the modprobe.d config file that would avoid needing unbind or driverctl but you did not try that. Here it is again:
options vfio-pci ids=1002:6798,1002:aaa0
softdep drm pre: vfio-pci
softdep snd_hda_intel pre: vfio-pci
put that in /etc/modprobe.d/vfio.conf then reboot and verify with lspci -v that the AMD GPU is using vfio-pci driver. If that works that's all, no need to manually unbind, rebind or use driverctl when you make sure that the correct driver is bound to the card and not try to fix up later.
|
|
|
|
|
|
Re: WebKit based browser initiative
|
Posted on: 4/3 19:40
#119
|
Quite a regular
|
@joerg Quote: For example YAM is GPL and you can ask Amigakit to send you the YAM sources they are using for their AROS/m68k YAM executables, and as you wrote only customers who bought the binaries have that right, nobody else. Where did you get that idea from? The GPL says: Quote:
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable.
|
|
|
|
|
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
