Who's Online |
51 user(s) are online ( 43 user(s) are browsing Forums)
Members: 0
Guests: 51
more...
|
|
Headlines |
-
imp3.lha - audio/play
Dec 5, 2025
-
vasmm68k_mot.lha - development/cross
Dec 5, 2025
-
vasmm68k_std.lha - development/cross
Dec 5, 2025
-
vasmppc_std.lha - development/cross
Dec 5, 2025
-
vlink.lha - development/cross
Dec 5, 2025
-
amissl-sdk.lha - development/misc
Dec 5, 2025
-
amiarcadia.lha - emulation/gamesystem
Dec 5, 2025
-
whdload-to-uae.lha - emulation/utility
Dec 5, 2025
-
ubek.lha - game/fps
Dec 6, 2025
-
polarpaint.lha - graphics/edit
Dec 5, 2025
|
|
|
|
|
Re: Odyssey 3.0 alpha - bug reports coming slowly...
|
Posted on: 2025/12/2 15:04
#1
|
Not too shy to talk 
|
@Rolar
Can they report it from Odyssey itself? Github needs the latest browser engine to work or it works faulty if it works at all. Bit off putting if you can't post a report on the machine with the bug but instead need to stuff around taking pictures and logs to transfer to another computer.
|
|
|
|
|
|
Re: AmigaOS 4.1FE Update 3 - Bugs and Experience Report
|
Posted on: 2025/12/1 13:19
#2
|
Not too shy to talk 
|
@yogi32
By the looks of it the boards looks well built. It's good it can last. Even if it's due for retirement. The Radeon card I bought was new but old stock. I'm somewhat loathe to replace as I don't want to replace with a used card even if newer. When RX580 cards were current and reasonably priced I should have bought one to keep for future use since we have RX drivers now. But, unlike the V3 driver, the V5 driver doesn't support the soft rebooting so a simple crash isn't as easy to recover from.
|
|
|
|
|
|
Re: AmigaOS 4.1FE Update 3 - Bugs and Experience Report
|
Posted on: 11/21 13:26
#3
|
Not too shy to talk 
|
@yogi32 Quote: Hi Everyone!
Okay, some more to report. First, my machine still hangs on boot sometimes like Hypex describes. It definitely is the USB and this needs to be fixed. I tried putting the old keyboard bootkeyboard.usbfd from Update 2, but that did not fix the problem. I still had to replace the bootmouse.usbfd back to Update 2 or my A-Eon Logitech Boing mouse does not work. Good to know I'm not the only one with a machine that goes cranky and I wasn't going crazy.  I can't leave any USB sticks in my drive as it will stall boot. Or stall Workbench on boot. Once when my mouse was plugged in to the front case port that stalled it but somehow it's been fine since. From reports I've read in places it might be related to Radeon model and drivers. I have an R7 250 and am using the RadeonHD.chip 3.7 driver. There is some unresolved interrupt issue I've had since Update 2. Some how vertical blanking interrupts are going missing. Since EHCI uses interrupts I wonder if a related issue is causing it to miss USB interrupts as well.
|
|
|
|
|
|
Re: Problem using Sil 3132 Sata2 controller with X5000
|
|
Not too shy to talk 
|
@AlfredOne Quote: I haven't had any such problems with the X1000. What version of CFE is installed on your X1000? That would be: CFE version PAS-2.0.30 for NEMO (64bit,MP,BE,PPC) Build Date: Fri Jun 8 16:04:49 CEST 2012 (hfrieden@jumpgate)
|
|
|
|
|
|
Re: Problem using Sil 3132 Sata2 controller with X5000
|
|
Not too shy to talk 
|
@m3x Quote: The Sil3132 controller is not recognized at all on the PCIe bus, so this is not the same situation you reported with the AmigaOne example. It could be an incompatibility between the PCIe bridge and the controller, or an incorrect configuration of the PCIe bridge. That's a bit more extreme than it showing up but not working with a known driver. I once plugged in a USB2 card into my X1000. It showed up on the PCI bus but Ranger reported it as something different than expected. Maybe as storage and not USB. I recall posting something about the details and seemed to get an angry response back. Which I thought was rather strange as I did recall the same card plugged into my XE came up in Ranger as being a standard USB card. The same software Ranger reported the same card as being different in my X1000. Same card. Same software. Different machine. Gave a different hardware info. No explanation as to how this would happen if the hardware should be hardwired but different firmware used in this case.
|
|
|
|
|
|
Re: Problem using Sil 3132 Sata2 controller with X5000
|
|
Not too shy to talk 
|
@joerg Quote: The AmigaOne (SE/XE/µA1) U-Boot versions don't initialize any IT, SII, LSI/NCR, etc. PCI(e) PATA, SATA and SCSI hardware either, but sg2's AmigaOS 4.x drives for it are still working on any supported hardware. At least his SII 3112 and 3114 drivers are working on the Sam440EP the same way well, using completely different versions of U-Boot. I have a Si0680 IDE controller in my XE. Uboot is able to boot off it. From any device unit IIRC. My X1000, having SATA built in, can only boot from one port and then AmigaBoot can only boot from one drive. Funny that the X1000, which has the best SATA support of all machines, providing four ports, can only boot from one drive and due to software limitations. Quote:
BTW: The X1000 doesn't use U-Boot, it's firmware is CFE (Common Firmware Environment), AFAIK OpenFirmware based and more similar to the Pegasos2 SmartFirmware, not comparable to the U-Boot firmware on the AmigaOne, Sam4x0, X5000 and A1222+
In the X1000 CFE is OpenFirmware based because it's some kind of hack. Varisys are likely responsible. CFE itself purely is not OpenFirmware based at all. It's independent. I don't know what happened to the X1000 CFE but the guts was ripped out and replaced with OpenFirmware. CFE is only the user interface on the terminal. Mind you, embedding OpenFirmware inside is no problem, but the way it was done means it's totally incompatible with Broadcoms CFE and any SDK that can compile binaries won't work. It's similar to SmartFirmware as both load OpenFirmware compatible binaries. So any binary running executes like any OpenFirmware binary using the OpenFirmware binary interface. The difference between the Pegasos and X1000 being the memory map is different. So any generic OpenFirmware binary cannot run.
|
|
|
|
|
|
Re: AmigaOS 4.1FE Update 3 - Bugs and Experience Report
|
Posted on: 11/17 12:56
#7
|
Not too shy to talk 
|
@FlynnTheAvatar
I wasn't aware GDB debugging failed because of a kernel issue. What I know about it is it hadn't been updated to work on newer CPUs. I don't recall if it worked on the Sam series but it never worked on my X1000 and I only know of it working on my G3/G4 XE.
So if Update 3 was meant to fix GDB so step debugging worked, on any other platform, that would be welcome. There may be a reason it didn't if it's kernel related, as the kernel is now handled by a different team since Trevor bought it out, so will not always contain the latest kernel release in the Hyperion produced updates.
|
|
|
|
|
|
Re: Upcoming Mirari PPC motherboard
|
|
Not too shy to talk 
|
The obvious question is where Skateman and Geennaam have been all our PowerPC life?  The OS4 market was at an all time hardware low with power dropping and prices rising when suddenly a new board is in development to offer reasonable power at a decent cost. Now, bringing a board to market at a good cost for the end user is already tough. So plans for a reasonable cost board tend to be taken as a relative term in the OS4 market. What's considered a good price today? But what I want to know is why this took so long? I mean, for years people spread on the forums that releasing a PPC board at good cost was doable, but no one did that. Even releasing a PPC board was fantasy talk and only companies like ACube could back it up after the A1 went stale. The laptop guys had an idea that was just too big to be practical. It just boggles my mind, that after all this time, a few people got together to do what teams have taken years trying to achieve and didn't deliver. Just saying. 
|
|
|
|
|
|
Re: Odyssey 3.0 Alpha vs 1.23r5
|
|
Not too shy to talk 
|
Unless I'm mistaken we need the new alpha for OS4 Update 3. With the current Odyssey it crashes on my Update 3. I haven't tested the new alpha yet.
|
|
|
|
|
|
Re: AmigaOS 4.1FE Update 3 - Bugs and Experience Report
|
Posted on: 11/17 4:36
#10
|
Not too shy to talk 
|
So thought I would have post my results about Update 3. I was hopeful for Update 3 after Update 2 introduced an interrupt issue on my X1000 hardware setup. However, it's almost made my machine worse now, which was unexpected. I disabled vertical blanking interrupts to work around the screen opening freeze issue I have. But now I have USB issues. First there is a longer delay in the USB boot drivers picking up keyboard and mouse. I had just figured out what wait ticks I need so the early startup detector picks up my mouse. Only to find after installing Update 3 the new drivers take longer to pickup my mouse and I can no longer get into the early startup menu! I thought scroll lock was assigned to Help but I cannot get it detected from keyboard either. Though using a generic Esc key would make sense for a lot of these quick key menus. I have to pull my mouse out of it's home spot and plug it into the front USB port of my X1000. For whatever reason, only the right USB port works, so with mouse plugged in and cable hanging out I cannot plug in USB sticks to my front port. Then, once OS4 is booted, all is fine until I plug a USB stick in. Or I leave one in the USB port. The USB drivers then cause the Workbench to freeze for about 20 seconds and then give up and cannot mount the stick. To be exact it is only USB2 EHCI. Sticks can work with OHCI or UHCI through a hub. Unlike on my XE years away when EHCI was introduced, there is no freeze or crash in the driver thankfully, so at least that is stable. But somehow I have an unusable system with USB devices. I'm used to plugging in a USB stick and transferring data. But now I have to avoid it or plug it through an older hub and use slower transfer speeds. This is an annoying step backward. For the most part, Update 3 brings AmigaOS4 forward, but unfortunately for me, it crippled my system. I'm avoiding the typical work around of copying over older USB drivers and other modules, since it isn't the right to pollute the system with crossed components, and the right solution is for compatible fixed modules. In the meantime I'm hoping the issues will be resolved and a hot fix will be on it's way. 
|
|
|
|
|
|
Re: AmigaOS 4.1FE Update 3 - Bugs and Experience Report
|
Posted on: 11/17 4:11
#11
|
Not too shy to talk 
|
@FlynnTheAvatar Quote: - gdb crashes with DSI after running a program, step does run the complete program Did this work before Update 3? I only recall this working on the XE with GDB 6.3 or any other G3/G4 machine. If it has been updated since sitting in bitrot for decades I missed the memo.
|
|
|
|
|
|
Re: Mount HDF on OS4?
|
Posted on: 12/12 13:02
#12
|
Not too shy to talk 
|
@broadblues
I'm surprised a def_hdd would be missing. I don't look in there a lot but I'm used to there being a full collection of def icons.
I looked at the binary of my HDD images and some have textual mount info, in the form of a mountlist, after a DOS ID, which I recall is what OS4 or MediaToolbox used to write there. I don't see any help for FixHDF from the Help command but looks like it fixes up geometry information.
|
|
|
|
|
|
Re: Sam460LE - linux Debian / Ubuntu instalation questions
|
Posted on: 12/9 10:16
#13
|
Not too shy to talk 
|
@sailor Quote: And it is interesting that ub2lb bootlader menu works on Quemu - on real hardware not. It works on the real hardware for which it was intended. It just crashed on my A1/XE when I ported it over. But I recall it wasn't consistent because sometimes it did work, depending on if it was fresh boot or reboot. I just can't recall exactly what but it annoyed me for a month before I tracked down. If only UBoot crashes were more informative.
|
|
|
|
|
|
Re: Mount HDF on OS4?
|
|
Not too shy to talk 
|
@broadblues
I do have a def_hdf. Just checked what the tooltypes are after showing all files and getting info on my hdf file. The default tool is MountDiskImage and tooltypes are "DRIVE=IDF0:"
Seems strange to mount from an "IDF0" as I associate that with a floppy but I suppose it works.
|
|
|
|
|
|
Re: Mount HDF on OS4?
|
|
Not too shy to talk 
|
@broadblues
It should be as easy as double clicking it. I have some HDF images I tested. They are partition images, so not exactly a "hard drive format" since a partition is a subset, but they opened and mounted fine. I did it the easy way. Opened up a HDF folder and showed all. Double click to mount. I am relying on DefIcons to pick up the tab since they have hdf extension. But a compatible file should open up in DiskImage tool itself. Mine are all standard DOS images.
|
|
|
|
|
|
Re: Strange crash with ARexx and RexxReqTools on Amiga OS4
|
Posted on: 12/3 13:01
#16
|
Not too shy to talk 
|
@FlynnTheAvatar That's good blacklisting would have sorted that out so you could isolate the crash point. Going over the docs, the usage of WindowPtr looks like a bad idea. It's called WindowPtr so should only contain a window pointer or NULL. This is one of those cases where it has too many possible values. While the bug in this case is in ReqTools and must surely be an old one gone unnoticed all these years, it demonstrates a flaw. Only a positive value can be an address which limits it to a 2GB boundary. Of course these pointers were designed around 40 years ago so an "MFP" (or multi function pointer) looks like a great idea.  Given there's so many values that can be there as well as a valid pointer you may need to check specially for 0, -1 and if neither interpret as pointer. The only shortcut I would trust is (!WindowPtr) to check for NULL.
|
|
|
|
|
|
Re: Strange crash with ARexx and RexxReqTools on Amiga OS4
|
Posted on: 12/2 13:15
#17
|
Not too shy to talk 
|
@joerg Quote: If I'm right the DAR (on most PPC CPUs, on 405/44x/46x CPUs it has a different name) of the crash should be 0x00000055. That looks right but you cannot trust the DAR. Anything Reaper spews out about a DAR is corrupt for ten years or more. IIRC it's correct on the serial log.
|
|
|
|
|
|
Re: Strange crash with ARexx and RexxReqTools on Amiga OS4
|
Posted on: 12/2 13:11
#18
|
Not too shy to talk 
|
@FlynnTheAvatar
It looks like you got the call stack you needed. For 68K it's recommended to disable Petunia (from Kicklayout) or blacklist the app in Compatibility Prefs. They really haven't sorted this out. You can't disable JIT emulator without modding your Kicklayout. And blacklisted apps don't have inheritance so child processes still have JIT.
Disabling JIT is recommended as in a lot of cases you don't see the actual code but the the ends of the JIT cache or something.
Edited by Hypex on 2024/12/3 12:27:41
|
|
|
|
|
|
Re: Sam460LE - linux Debian / Ubuntu instalation questions
|
Posted on: 11/30 13:08
#19
|
Not too shy to talk 
|
@joerg Quote: It can't, it only supports adding it to new images, but if you mount an ISO image with something like diskimage.device it's no problem to create a new one from an existing one. Oh I see. Indirect modification. I likely mounted images to do that if I had any. I tried to use AmiDVD to rebuild a Linux install CD since only my OS4 volumes had enough space back then. But it failed to retain the links. AmigaOS wasn't designed for Linux links so the end result was faulty. Quote: The versions illegally distributed with AmigaOS 4.1 FE (and newer) releases/CDs of AmigaOS 4.1 by Hyperion, despite explicit prohibition to continue including it, are. Not sure about the os4depot and AmiNet versions any more. IIRC it was Contrib. Convenient for the user. Easy enough to download from the depot. But looks like it has an issue with FE Update 1. https://os4depot.net/?function=comment ... e=utility/misc/amidvd.lhaQuote: It's based on El Torito, but IIRC there were some small differences required for AmigaOS 4.x or U-Boot. There were and I figured out what they were in the MakeCD days. SLB as the boot block. And some kind of "AMIGA BOOT" ID string needed. It's too late but I made a mistake when I stated "UBoot doesn't directly support booting ISO9660 off CD". That makes no sense, of course it does. What I meant is that UBoot doesn't directly support booting ISO9660 off USB.  For obvious reasons.  Quote: IIRC U-Boot itself doesn't support booting any OS at all, except for Linux with TFTP maybe, but can only load and start the SLB, which then boots AmigaOS 4.x or Linux from HD partitions (FAT, ext2fs, FFS/FFS2, SFS/SFS2, etc.) or ISO 9660 (CD/DVD or USB), or with ub2lb/Parthenope instead of SLB_v2 AROS, MorphOS and Linux, but not AmigaOS from SFS partitions. However using FFS, maybe DOS\0-DOS\5 only, not the new FFS2 DOS\6 and DOS\7 formats, for the AmigaOS Kickstart partition should work with ub2lb/Parthenope as well. That sounds about right. UBoot can scan an RDB or in the least RDB BOOT blocks which are constructed the same way. The simple secret hidden in the boota command. But I looked and ub2lb does have support for SFS. As well as ISO9660. What I cant find is any reference to FFS which is strange. Perhaps UBoot API supports it. One thing ub2lb broke was the QEMU Sam config. I knew why. Some hardware quirk or maybe MMU setup meant a NULL pointer was acceptable. The ub2lb code violated the UBoot API by passing a NULL pointer when scanning CD. I checked the docs and accordingly a pointer must be given. I don't know how or why ub2lb has a "legal" bug that works. But it caused me a month of trouble trying to figure out why it kept crashing my A1 at random when I modified it for a Linux boot menu. Quote: The format of SFS 1.84, the last version from John Hendrikx, is public, but that didn't help much. The easiest way to destroy any SFS partition is using the broken Linux implementation of SFS based on his public documentation in r/w mode  I didn't recall that. Sounds almost useful. For a boot loader only read support is needed. When I was designing my X1000 Linux boot editor I wanted a boot volume that was readable by AmigaBoot and writeable by Linux. FFS DOS3 turned out to be that happy place. Writes fast on Linux.  Quote: In my AmigaOS version of SFS I added some improvements which aren't backwards compatible, except to my own implementations of it (AmigaOS 3.x/m68k SFS, AmigaOS 4.x/PPC SFS and the SLB_v2 SFS code), but not to John's <= 1.84 versions and independent implementations of SFS like the AROS, MorphOS and Linux versions. Yes, SFS has a bit of a convoluted history on the Amiga or post Amiga, splitting up into different Amiga distros.
|
|
|
|
|
|
Re: Sam460LE - linux Debian / Ubuntu instalation questions
|
Posted on: 11/30 11:31
#20
|
Not too shy to talk 
|
@smarkusg
That's all right. It gives me some programs to check out. I last used ISO Master which may not fully live up to the name.
|
|
|
|
|
|