AMIGASYSTEMDistro MaintainerPosted
21 days agoOn VMware, ZunePaint gets a Guru even with PNG, ILBM is saved without errors.
I've been trying to get my HP Elitebook on the internet again, this time trying tethering. Unfortunately, whilst tethering works on 32 bit it refuses to connect on 64 bit ('no route to host' on ping). One difference seems to be in the binding of mdis class to the Android device; this happens autmatically on 32 bit when the tethering is enabled, but for 64 bit it only happens if the port is powercycled.
Cheers,
Nigel.
AMIGASYSTEMDistro Maintainer Posted
17 days agoWith my old ‘ACER ASpire 5920’ laptop running AROS One 64Bit, USB tethering works well. I can browse with OWB, AmiTube and use shared Windows (Network Drive) on the network.
For USB tethering to work properly, it must be enabled before starting Wanderer!
I have only one problem: the Google search engine does not work, error 28, but perhaps this problem is due to the fact that I only have 2 GB of RAM on the ‘ACER ASpire 5920 laptop’.
The Google search engine works fine with AmiFox, so it is not a connection problem but a problem with OWB 64 with 4 MB of RAM?
ntromans wrote:
@ntromans - ncafferkey wrote:
@ncafferkey
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?
Hi Neil, good to hear from you. Yes, I agree realtek8180 can be fussy; it does work on this machine under 32 bit though. However, it does require me to (a) set all ip addresses manually (tried for 64 bit as well as DHCP) and (b) run sequentially startnet, stopnet, startnet and then wirelessmanager. Oddly doing the start/stop/start makes connection to our router via realtek8180 much more reliable. I tried that with 64 bit but got a crash on running stopnet; when I get back home I'll try again and post up the crash log.
Cheers,
Nigel.
Edit: Stopnet error log attached.
ntromans wrote:
Hi Neil, good to hear from you. Yes, I agree realtek8180 can be fussy; it does work on this machine under 32 bit though. However, it does require me to (a) set all ip addresses manually (tried for 64 bit as well as DHCP) and (b) run sequentially startnet, stopnet, startnet and then wirelessmanager. Oddly doing the start/stop/start makes connection to our router via realtek8180 much more reliable. I tried that with 64 bit but got a crash on running stopnet; when I get back home I'll try again and post up the crash log.
Cheers,
Nigel.
Edit: Stopnet error log attached.
I'm attaching an updated AROSTCP binary that fixes the stopnet crash for me. The fix is also committed to Deadwood's repo.
You do not have access to view attachments
Hit a crash with the realtek8180.device and with wirelssmanager when trying to cancel it via ctrl-C - please see attached if these will be of any help.
Cheers,
Nigel..
You do not have access to view attachments
deadwood wrote:
@deadwood - For people reporting "file is not executable" when starting Odyssey, please try this kernel:
https://axrt.org/.../kernel.gz
Also please note that there is a suspicion of regression in network in nightlies which causes Odyssey to fail to load heavier sites like YT. EDIT: It's most likely a false alarm and related to issues with a specific ISP. Same hardware using another ISP works correctly.
deadwood wrote:
@deadwood - For people reporting "file is not executable" when starting Odyssey, please try this kernel:
https://axrt.org/.../kernel.gz
Also please note that there is a suspicion of regression in network in nightlies which causes Odyssey to fail to load heavier sites like YT. EDIT: It's most likely a false alarm and related to issues with a specific ISP. Same hardware using another ISP works correctly.
I've tried the new kernel with 'intersting' results.
Firstly I booted on thw working i5 machine. Kernel booted, OWB started, albeit it felt a bit slowly.
Then I bootted the AMD machine. It booted and OWB started up. No improvement for google (still not loading, this through realtek8189.device0. I tried to post to here from that machine and that's then things got strange. In this reply box, if I hit '1' the box closed and I bounced back to the forum page. This happend a coupdl of times, On the third attemp the reply box refused to open at all. I went back to the home page and found I couldn't oprn a forum at all. I tried deleting cookies, restarting OWB and rebooting, no improvement.
I then went back to the i5 machine to see if it did the same and OWB crashed on opening - please see attached.
Cheers,
Nigel.
P.S. reinstalled kernel from most recent nightly linked to here, OWB is now behaving as it previously was on the i5 machine.
Edited by ntromans on 16-09-2025 07:36,
12 days ago You do not have access to view attachments
Thanks for adding more details.
For AMD: I don't see realtek8189.device on the ISO :/ Are you sure this is the wired ethernet you are using?
For i5: please start Odyssey 10x using 26th kernel. Then swap kernel to 149.25 and again start Odyssey 10x. Is there any pattern to the crashes?
