Forums - All Posts - The Amigans website

Forum Index

Board index » All Posts (balaton)

Bottom

(1) 2 3 4 ... 43 »

balaton

Re: Catching memory corruption "in the act"

Posted on: 7/5 11:43 #1

Quite a regular

@BSzili
I think PPC is unsupported in Debian for a while so you should try something contemporary to these machines or what's known to work on real machine. The most recent Debian I've found that supported AmigaNG machines was about Debian 8.11 and if you just want to run valgrind on it don't update it. Other Linux distros that are newer and still have PPC versions that might work are https://github.com/finnix/finnix-docs/blob/main/platforms.md (only old version) or https://www.adelielinux.org/download/ but maybe these only support -machine mac99,via=pmu which is closest to PowerMac3,1 (that is also listed for MorphOS on my page in the signature below). Maybe you could get AmigaOS running on one of the boards in QEMU and 2GB could be enough to debug it with the page protection trick. Or you can try a PPC64 distro with qemu-system-ppc64 that should still be able to run 32 bit PPC code. Those may be better supported for spapr for example but I don't have much experience with that.

https://qmiga.codeberg.page/

Topic | Forum

balaton

Re: Catching memory corruption "in the act"

Posted on: 7/4 12:41 #2

Quite a regular

@BSzili
I don't know if valgrind works with user mode emulation (I've only found old tickets that said it did not work but could be fixed since). Otherwise there are docs at https://www.qemu.org/docs/master/system/ppc/amigang.html about running Linux on my boards in QEMU. Or for Linux any other PPC board may be used which can probably run more recent distros but PPC emulation is quite neglected. But you can use up to 2GB memory with AmigaOS on QEMU.
Another idea, if you can replace the allocation in the code you're debugging (e.g. with some preprocessor #defines) to call your own wrapper you could allocate more memory for some guard bytes before and after the address returned to the application then you can check it on free or when a crash occurs.

https://qmiga.codeberg.page/

Topic | Forum

balaton

Re: Bootarguments for Qemu AmigaOne install on Mac M1

Posted on: 6/26 13:17 #3

Quite a regular

@johnfante
For inserting CD after boot see change command in QEMU Monitor https://www.qemu.org/docs/master/system/monitor.html or you could use the early startup menu as on real machine by holding both mouse buttons at the right moment during boot (around when the logo fades in but it may be hard to find when to do that, too early or too late may not work).
About USB shared folder see http://qmiga.codeberg.page/#faq you need the corresponding -drive option to define ufat but this is limited to small files and writing it does not really work so using network for file transfer is better.

https://qmiga.codeberg.page/

Topic | Forum

balaton

Re: Bootarguments for Qemu AmigaOne install on Mac M1

Posted on: 6/26 11:38 #4

Quite a regular

@johnfante
What error do you get? What network settings you use in AmigaOS? With -netdev user you should leave it using DHCP and ping may not work but should still be able to connect to services (like from behind a router doing NAT).

https://qmiga.codeberg.page/

Topic | Forum

balaton

Re: NULL, 0xFFFFFFFF and Exec: Real vs QEMU

Posted on: 6/23 19:02 #5

Quite a regular

There was a patch recently to fix address wrap around (https://patchew.org/QEMU/2025050420571 ... ard.henderson@linaro.org/) so probably before that QEMU did not check this. Are you using latest QEMU from git where this patch should already be merged?

https://qmiga.codeberg.page/

Topic | Forum

balaton

Re: How to use clib4 (natively)?

Posted on: 6/20 19:46 #6

Quite a regular

@joerg
Quote:

Work required for re-implementing all of my AmigaOS 4.x parts, depending on the skills of the developer, about 25-100 man hours, which is much less than the time already spend on clib4...

Why does it need to be reimplemented? Couldn't you just release it under a similar licence as the rest of newlib then others could update it without having to start from scratch. Otherwise why anybody would want to redo stuff that was already done when there is an alternative that is open source and can be updated instead of having to figure out what's missing.

https://qmiga.codeberg.page/

Topic | Forum

balaton

Re: Updating system

Posted on: 6/20 19:39 #7

Quite a regular

Do you have serial cable and another system to connect to? U-Boot should print some messages on serial which might give some hint on what could be wrong. Checking that might be easier than guessing what could be wrong.

https://qmiga.codeberg.page/

Topic | Forum

balaton

Re: wget 1.25.0 for os4

Posted on: 6/20 19:36 #8

Quite a regular

@LiveForIt
Quote:

Can easily hack into amigaOS4 library api. AmiSSL has a big back door. Statically linking makes it harder to be man in the middle.

How is that an issue on an OS without memory protection or user separation? Since AmigaOS has no security at all anything can mess with anyting anyway. Even on Unix like systems you can probably preload dynamic objects and override library functions and it's not considered a problem for using openssl.

https://qmiga.codeberg.page/

Topic | Forum

balaton

Re: QEMU GPU-PCIe AmigaONE

Posted on: 5/27 12:19 #9

Quite a regular

@white
You already got help several times you're just not following advice. Have you completely missed post #178 earlier in this thread? And post #175 that shows the advice I gave is enough to find the solution.

https://qmiga.codeberg.page/

Topic | Forum

balaton

Re: unix like "netstat" tool for os4, v1.1

Posted on: 5/25 14:40 #10

Quite a regular

@kas1e
Thank you. Sharing more source helps people who want to develop for AmigaOS.

https://qmiga.codeberg.page/

Topic | Forum

balaton

Re: qemu emualtion of AmigaONE XE

Posted on: 5/25 14:34 #11

Quite a regular

@AlexC
Quote:

The Amiga RDB can be located anywhere within the first few KB of a drive, can't remember if it's 4k, 32k or more, but when you configure the RDB in MediaToolbox you can choose where the RDB should be written (start block and size), and is automatically found, wherever it is, by kickstart or cfe/uboot.

So if your RDB start at block 2, and has an SFS partition listed in it, it wouldn't matter what you do in Parted, the RDB would still be there until you overwrite the RDB, presumably with data written to the first partition starting at block 2.
I doubt linux would scan the entire disk and find the SFS partition, but rather finds and parses the RDB.

I use this feature extensively on external drives as it allows to share the same drive between x86 and Amiga by having an MBR on the first block, followed by the RDB, keeping the partitions hidden from each other.

That approach requires remembering not to create/start the first MBR partition before the end of the RDB blocks, and keeping track of which block is the border between the x86 and Amiga partitions to prevent overlapping partitions.

Technically you could even specify the otherwise invisible partitions of the other OS in both the MBR and RDB, but it's too easy to make a destructive mistake, not worth the risk on a backup drive.

This does not seem to work. While it is possible to put RDB on second block and RDB partitions show up in MediaToolBox, AmigaOS4 only mounts them as long as there is no MBR partition table on the disk. If there's an MBR in the first block then the RDB partitions don't appear. How do you use it then?

https://qmiga.codeberg.page/

Topic | Forum

balaton

Re: Project - hardware to run AOS4 for 35 euro on QEMU 10 + GPU passthrough

Posted on: 5/24 13:55 #12

Quite a regular

@smarkusg
Quote:

I have noticed one more thing regarding QEMU 8x and QEMU 10.
QEMU 8 is able to show me an image on the output of the ‘ati’ device with rom image and pegasos2.rom
Screen - > https://ibb.co/vCdzsmL2
QEMU 10 does not display anything.
Screen - > https://ibb.co/B5pzTMCL
This may have nothing to do with "vfio", but I thought this information might be useful for something.

I have bisected this to this commit which enables configuring location of the VIA south bridge devices. The pegasos2.rom seems to put parallel port to 0x3BC which was ignored before this commit and parallel port was at default 0x378 location that this VBIOS seems to depend on so maybe this is also broken on real Pegasos II. But what does a VBIOS has to do with a parallel port and why is it broken by not finding one? Maybe the port number of parallel port is configurable on real Pegasos II but that may need NVRAM which we don't have. As the pegasos2.rom writes this config I can't fix it in QEMU as the default is overwritten by the firmware.

EDIT: It seems that default address matches real machine according to this message but a problem with QEMU was also reported on qemu-devel list that I forgot about. I'm not sure if this VBIOS ROM only works with parallel port at 0x378 or there's a problem with accessing it at the PegasosII default address. If you want to debug further you could check if it works when you send something to parallel port (from either Linux or AmigaOS guest) then it should appear in one of the virtual consoles or wherever you redirect it (I think there is a -parallel option similar to -serial for that).

EDIT2: Also the Bochs VGA BIOS as described here does not have this problem so that's a possible work around.

Edited by balaton on 2025/5/24 23:01:58
Edited by balaton on 2025/5/25 21:05:42

https://qmiga.codeberg.page/

Topic | Forum

balaton

Re: Project - hardware to run AOS4 for 35 euro on QEMU 10 + GPU passthrough

Posted on: 5/23 23:16 #13

Quite a regular

@smarkusg
This was discussed in some other thread here when we were trying to find why the RX card was slower. I think the Read/WritePixelArray variants use processor specific optimisations so e.g. AltiVec with a G4. Did the default CPU change between those QEMU versions? What if you use -cpu g3 with latest QEMU? Also look up the message I've sent to the qemu-ppc list about it a few months ago which has the benchmark with code from Hans that models these tests which can be run under Linux that might be easier to test with than running the whole Gfx benchmark on AmigaOS. If it's not related to some change like CPU then you may need to git bisect it to find the change that caused the slowdown but it could be it's an actual bug fix so it may have been fast before but also wrong but I can't tell without knowing what changed that made it slower.

https://qmiga.codeberg.page/

Topic | Forum

balaton

Re: QEMU GPU-PCIe AmigaONE

Posted on: 5/20 10:59 #14

Quite a regular

@white
Here's an easy solution. Go to your favourite web search engine. Type: pipewire sound as root. Follow first link (if that does not help then look at further links). I hope that will put an end on your suffering with this. This solution works for most problems

https://qmiga.codeberg.page/

Topic | Forum

balaton

Re: Project - hardware to run AOS4 for 35 euro on QEMU 10 + GPU passthrough

Posted on: 5/17 23:38 #15

Quite a regular

@smarkusg
It would be more interesting to find out what's the problem with interrupts and fix it as that should work better and faster. Disabling it is just a work around. Do the IDE interrupt logs show up without the network card or only with it? You have the same IRQ setting as in sailor's article but different card with different BARs. This may not matter but if we want to debug something it helps to look at relevant information not something similar only. I think to get further we would at least need BBoot output with and without firmware on pegasos2 and amigaone and see if there are some difference that could be fixed when running without firmware. For the IRQ more understanding is needed. I'm not sure how vfio works (and currently it's being changed so it may look different after a few commits so I wait until those are merged before trying to dig deeper) but maybe this has something to do with how interrupts are acknowledged with vfio-pci so it may ack an IRQ too soon or somehow mess up the IRQs in a way that AmigaOS can't handle. This works with Linux and Windows guests at least so it should be usable but maybe AmigaOS relies on something not emulated correctly or we have some problem specific to these PPC machines where I've missed some emulation of the IRQ handling (which is also possible as I don't understand all of the details of this). Does the passed through network card work with linux on amigaone and peagsos2? That would at least confirm the emulation is correct or might give some error that helps debugging it.

https://qmiga.codeberg.page/

Topic | Forum

balaton

Re: Project - hardware to run AOS4 for 35 euro on QEMU 10 + GPU passthrough

Posted on: 5/17 18:59 #16

Quite a regular

@smarkusg
If it only works with ROM then the card needs some init that BBoot does not do. Usually e.g. Linux can init the cards it has a driver for but AmigaOS relies on the firmware to init cards. The AmigaOne U-Boot should init cards too but maybe it's too old and does not recognise this card or only inits the card that's onboard which has a specific address as the article you linked shows. You could specify that address with -device vfio-pci,addr= to put the card where the onboard device should be and see if that changes anything with amigaone u-boot but only bboot won't work on amigaone either until we find out what's needed. You could compare the card infos in Ranger and logs from the driver when you booted with firmware or with only bboot and see what's missing. You still did not show what's your card settings and what interrupt it uses so I have no idea. The logs you posted refer to IDE interrupts so likely not related. If these only show up on boot when detecting IDE devices and never again after that then it's probably due to a QEMU issue that there seems to be an empty device on every port even when there isn't an ide-hd or ide-cd attached but when the guest tries to query it it won't respond so you get spurious warnings but then it's ignored aferwards so should not be a problem later. We have found this a few years ago, it is described in some message on the QEMU mailing list but since it does not cause other problems nobody fixed it.

https://qmiga.codeberg.page/

Topic | Forum

balaton

Re: unix like "netstat" tool for os4, v1.1

Posted on: 5/17 18:46 #17

Quite a regular

@samo79
No netstat is the name of this kind of tool on every platform. You can just think of this version as surpassing the existing one so that's now obsoleted by this.

https://qmiga.codeberg.page/

Topic | Forum

balaton

Re: QEMU GPU-PCIe AmigaONE

Posted on: 5/17 14:59 #18

Quite a regular

@white
Quote:

Someone who is emulating the AmigaONE and uses the
ALCS1200A audio chipset
mounted on their motherboard ?

The audio codec chip is not relevant to your problem in any way. You could ask instead if anybody uses QEMU with pipewire.

https://qmiga.codeberg.page/

Topic | Forum

balaton

How to configure screen modes without EDID (solved)

Posted on: 5/17 13:27 #19

Quite a regular

When EDID info is not available AmigaOS 4.1FE seems to default to 640x480x8 and no other screen modes are available. I've tried to add a monitor file with tool types with DDC disabled and frequency limits and some modes defined which then show up on the monitor tab of ScreenMode prefs but not on the main tab so they can't be selected. I've also tried defining modes with Picasso96Mode but it defaults to something like 72Hz and I cannot edit it without attching to a card and when attached to the card it says for even the 640x480x8 mode that size is too big for the card for any action. What is the correct way to define screen modes when the monitor does not send and EDID and so no modes can be selected? I never used RTG or AGA so this screen mode stuff is completely new to me.

EDIT: Nevermind, I've figured it out. Despite that documentation says the boardtype tooltype overrides the file name in Devs/Monitors it doesn't and it seems the file name has to match the graphics driver name for it to be recognised. After renaming the monitor file I can select modes defined in it.

Edited by balaton on 2025/5/17 14:55:51
Edited by balaton on 2025/5/17 23:24:38

https://qmiga.codeberg.page/

Topic | Forum

balaton

Re: unix like "netstat" tool for os4, v1.1

Posted on: 5/17 13:19 #20

Quite a regular

@kas1e
Nice. Can we also get the source as a network programming example?

https://qmiga.codeberg.page/

Topic | Forum

Top

(1) 2 3 4 ... 43 »