As you can see from the attached video, with the reference build ‘20250418-1’, this is how long it took for the icon to disappear from Wanderer. Now this does not happen with the new build, tonight so I will do some more testing!
Ok, I see. I don't recall waiting that long for USB devices (I'm using them under VirtualBox), so I would say there was something wrong with it previously and now it's probably as it should
As in the previous ISO to be tested, this build also includes tiff.datatype for managing TIFF images. Will this Tif.datatypes also be compiled for AROS 32Bit?
Among the upcoming improvements, I hope there will be a fix for MPlayer, which does not support some audio formats. On Hosted Linux, you cannot listen to streaming radio (Guru), but on native AROS Mplayer, there is no problem listening to streaming radio.
If there will be an update to 32-bit core system, tiff.datatype will be included in it. I don't plan on building selected compoments without having a complete update.
With regards to MPlayer I listen to many streams on daily basis and I haven't have a crash with them. Can you give me the URL of radio station that causes crash for you and make a screen shot of error with More.. button clicked.
The Radio links are the usual radio streams included in AROS One 64/32 Bit (scripts executed from Icona). As mentioned, there are no problems on AROS One PC Native or WMware AROS Native, while Guru only appears on AROS Hosted Linux when you exit MPlayer!
I am attaching two files: a video showing Guru + More and the radio links
I tested your radio links with two configurations:
a) 20250418-1 release (AROS-20250418-1-linux-x86_64-system.tar.bz2)
a) 20250418-1 release with U1.B applied
In both cases I opened MPlayer 1.2 via icon like on your video 10 times. I didn't get a single crash when closing for all 20 tests.
Please first try a clean release with only MPlayer 1.2 and your radio links. If it still crashes then the only thing I can think off is something to do with your host linux OS.
Edited by deadwood on 28-08-2025 12:10, 1 month ago
It looks time this is some sort of timing issues with threads. At the moment I'm not able to reproduce this, but I added to my TODO to try to patch it.
There are indeed some strange behaviours. I replaced the MPlayer folder and out of six runs i only got one Guru on the first run. I restarted Linux and the Guru reappeared on every run.
Furthermore, MPlayer crashes (Guru) if you try to run ‘AC3’ and ‘AIFF’ files. This happens on both the native and hosted Linux versions.
No problems with MPlayer on AROS 32Bit, both native and hosted Linux!
Finally had time to download the latest nightly. I've only had time to try a boot so far but I'm happy to report it boots fine on my HP EliteBook 8470p
Intsalled to USB and can boot off that. Installer refused to blank the usb drive but HDtoolbox was able to create the partition structure and intallation then proceeded fine.
Audio is working as is USB and I've had no issues so far with applications included in the nightly. The system feels very fast .
I have tried wifi; it would be particularly useful to see that working as I'm showing AROS at another local Amiga group meet at the end of September and I know people there were keen to see OWB in action, so I'd like to show OWB 64 bit but this would need me to connect to the wifi.
Setting the atheros5000.device, the wifi icon appears on Wanderer and displays all the local networks including our own, but will not connect to our router either in automatic or manual mode. Is this currently as expected?
@AMIGASYSTEM - Strange, if the WiFi icon appears, the network should be working. Make sure that the access details are correct (provider name and password).
@ntromans -
Setting the atheros5000.device, the wifi icon appears on Wanderer and displays all the local networks including our own, but will not connect to our router either in automatic or manual mode. Is this currently as expected?
I don't really know - I have no hardware at the moment where I could test it. There was a batch of commits from Neil fixing several network drivers for 64-bit some time ago and atheros was not included in them. I don't know if this means it worked for him or that he didn't yet have time to look into atheros.
I don't really know - I have no hardware at the moment where I could test it. There was a batch of commits from Neil fixing several network drivers for 64-bit some time ago and atheros was not included in them. I don't know if this means it worked for him or that he didn't yet have time to look into atheros.
Thanks. Yes, Atheros was not mentioned in Neil's list but wasn't Realtek8180 on the list though? Unfortunatly it shows the same behaviour.In any case, aside from that all seems to be working well
I have a 'new' machine thrown out from work (apparently a 16 GB, 3 GHz machine from 2015 is not good enough for Windows 11...); it boots 32 bit off hrad drive so be tryng 64 bit on that one next.
Cheers,
Nigel.
P.S. for the record realtek8180.device does not do as well as atheros5000.device in that it does not pick up any networks at all. For atherros, the scan does pick up networks but very slowly; using 'verbose' in wirelessmanager shows it tries to associate with our router but ends up with 'supplicant port unautorised'.
Edited by amigamia on 31-08-2025 09:25, 28 days ago
Disappointingly, whilst my 'new' machine (with an ASUS i7 motherboard) is working really well with 32 bit, it refuses to boot 64 bit. It gets to grub, but 5 seconds after selecting the boot option it just resets. This is the case with all options and I've tried via CD, USB stick and the hard-drive install from the core 2 duo machine this is to replace. Not just an issue with the current nightly, there's the same behaviour with the previous test release.
Hmm, have you tested how 20250418-1 release behaves?
Also if you select second option (VESA) and add debug=serial to grub command line, you should get some debug output on screen - if you record it with camera, you might catch the crash on one of the frames.
Thanks. Yes, Atheros was not mentioned in Neil's list but wasn't Realtek8180 on the list though? Unfortunatly it shows the same behaviour.In any case, aside from that all seems to be working well
...
P.S. for the record realtek8180.device does not do as well as atheros5000.device in that it does not pick up any networks at all. For atherros, the scan does pick up networks but very slowly; using 'verbose' in wirelessmanager shows it tries to associate with our router but ends up with 'supplicant port unautorised'.
Unfortunately, it's a known issue that atheros5000 doesn't work on 64-bit. As you've seen, it gives the illusion that it might work, but something unknown is wrong that causes it to drop a lot of packets. I spent a bit of time trying to fix it, but I had to set it aside for the moment as it's not the same type of problem that the other drivers had.
realtek8180 has always had strange behaviour, even on 32-bit. It works in some environments and not in others. On my last test it seemed to work quite well on 64-bit, but that could definitely be specific to my network. Does it work for you on 32-bit?
@deadwood - Hmm, have you tested how 20250418-1 release behaves?
Also if you select second option (VESA) and add debug=serial to grub command line, you should get some debug output on screen - if you record it with camera, you might catch the crash on one of the frames.
Re. 20250418, same behaviour (that's the one installed on hard-drive).
I'll try the debug as above and see what I get.
Cheers,
Nigel.
You can view all discussion threads in this forum. You cannot start a new discussion thread in this forum. You cannot reply in this discussion thread. You cannot start on a poll in this forum. You cannot upload attachments in this forum. You cannot download attachments in this forum.