| Native | |
| Reference | https://axrt.org/download/aros/v0/AROS-20161228-1-pc-i386-boot-iso.zip |
| Testing | https://axrt.org/download/aros/v0/AROS-20170402-4-pc-i386-boot-iso.zip |
| Linux-Hosted | |
| Reference | N/A |
| Testing | https://axrt.org/download/aros/v0/AROS-20170402-3-linux-i386-system.tar.bz2 |
| Windows-Hosted | |
| Reference | N/A |
| Testing | https://axrt.org/download/aros/v0/AROS-20170402-3-mingw32-i386-system.tar.bz2 |
| Contrib Archive | |
| Reference | N/A |
| Testing | https://axrt.org/download/aros/v0/AROS-20170402-3-any-i386-contrib.tar.bz2 |
AROS ABIv0 20170402 changes:
Functionalities:
Align naming of graphic drivers and make them visible in SysExplorer (Kalamatee)
Query graphics driver for 3D subdriver (Kalamatee)
C library improvements (Mazze, Kalamatee)
Kernel ACPI support (Kalamatee)
SysMon listing tasks better (Kalamatee)
Kernel IO-APIC support (Kalamatee, Schulz)
Kernel interrupt support (Kalamatee, Schulz)
Kernel SMP support (Kalamatee, Schulz)
Kernel shutdown/reboot support (Kalamatee)
Kernel spinlock support (Kalamatee, Schulz)
Public locking mechanism support (Kalamatee, Schulz)
Kernel CPU cores control (Kalamatee, Schulz)
processor.resource improvements (Kalamatee, Schulz)
SMP-enabled Message Port handling (Kalamatee, Schulz)
Protect access to Exec resources (Kalamatee)
Better measurement of CPU usage (Schulz)
SysMon listing CPU usage better (Kalamatee)
Graph.mcc (Kalamatee)
picture.datatype DTM_Write support (Mazze)
vusbhci.device (DizzyOfCRN)
Kernel MSI interrupt support (Kalamatee)
List.mui improvements (Kalamatee)
ACPI button driver (Kalamatee)
PCI driver IRQ routing table (Kalamatee, Schulz, Neil)
pcx.datatype (Mazze)
targa.datatype (Mazze)
64-bit support:
misc fixes (Kalamatee, Schulz)
ahi.device, ac97.audio, hdudio.audio 64-bit support (Kalamatee)
pciusb.device 64-bit support (Kalamatee)
ata.device 64-bit support (Schulz)
Updates:
Flexcat 2.18 (Mazze)
libz 1.2.11 (Mazze)
libjpeg 9b (Mazze)
libpng 1.6.28 (Mazze)
AROS build system (Kalamatee)
Icons (Paolone)
GCC-6.3.0 (patch file) (Kalamatee)
libmikmod 3.3.10 (Mazze)
libspeex 1.2.0 (Mazze)
libflac 1.3.2 (Mazze)
Text2PDF (Mazze)
Dt2Thumb 1.1 (Mazze)
CDXLPlay 1.4 (Mazze)
PlayCCDA 1.6 (Mazze)
Fixes:
Corrected datatype descriptors (Neil, Mazze)
VGA driver (Kalamatee, Neil)
Documentation (Neil, Kalamatee)
X11 driver (deadwood)
MUI (o1i, Kalamatee)
Shell commands (Neil, Kalamatee, Mazze, Schulz)
dos.library (Kalamatee)
C:Decoration (Kalamatee)
Kernel (Kalamatee)
Catalogs (polluks, mmartinka, Kalamatee)
Mesa (Kalamatee, Neil)
emul-handler (Neil)
console.device (Schulz)
Intuition (Schulz, Neil)
Preferences (Neil, balaton)
kms.library (Kalamatee)
pciusb.device (Schulz)
C library (deadwood)
Kernel ACPI support (Neil)
Kernel interrupt support (Neil)
PCI driver (Neil)
Kernel IO-APIC support (Neil)
atheros5000.device (Neil)
Kernel shutdown/reboot support (Neil)
Windows-hosted booting (deadwood)
SDL-mixer (Neil)
hdaudio.audio (deadwood)
Boot in the Virtual Box 5.0.40
Reference CD boot OK
Test CD no boot (attach picture)
Reference https://axrt.org/download/aros/v0/AROS-20161228-1-pc-i386-boot-iso.zip Testing https://axrt.org/download/aros/v0/AROS-20170402-1-pc-i386-boot-iso.zip
Ok, so far I could test it on VMware Player 15 and
- booted fine both with VESA and Native driver
- sound is garbled (sb128.audio) at 44.1 KHz HIFi stereo and ++.
- I could power off the machine via the ACPI function
- VMware SVGA driver seems to work pretty well
In order to save time and efforts, are you planning to release another ISO in the next few days? If not, I will proceed with integrating files into current build of Icaros Desktop and let icaros beta testers to test it, along with newer features I added in the latest weeks.
While integrating AROS system files I noticed two differences:
- tool "delete" and its icon in system/wanderer/tools are not present
- smartcan is not present in wbstartup
Ok, I tried integrating ISO files into Icaros Desktop, but it doesn't boot no matter if I add noacpi option or I choose a VESA mode, or VGA.
VMware Player 15. Your ISO alone, as I said, boots correctly.
Ok, I tried integrating ISO files into Icaros Desktop, but it doesn't boot no matter if I add noacpi option or I choose a VESA mode, or VGA.
VMware Player 15. Your ISO alone, as I said, boots correctly.
What if you delete SYS:Devs/Monitors/Compositor?
Ok, I tried integrating ISO files into Icaros Desktop, but it doesn't boot no matter if I add noacpi option or I choose a VESA mode, or VGA.
VMware Player 15. Your ISO alone, as I said, boots correctly.
What if you delete SYS:Devs/Monitors/Compositor?
I removed all .hids in Devs/Drivers that are not present anymore (graphics.hidd, sm502.hidd and another one I don't remember), and the distro boots. But for now I kept compositor in monitors.
In a few words, what does composition do in monitors? is it safe to remove it considering that I have to keep also linux/windows hosted modes alive?
Yes, the native issue has been solved. However, the internal changes broken Windows hosted mode.
Not a great issue, if only I hadn't been working on windows hosted mode for the last three months, to improve is useability.
So, either I give up with Windows Hosted, and it would be very sad to me, or also Win32 and Linux hosted AROS should be recompiled as well, and maybe the issue disappears.
But let's face issues step by step...
Isn't it the same case of "stalled" hidds?
I have linux-hosted compiled as well, I will see if I can compile windows-hosted.
Environment:
----------------------------------
VirtualBox 6.1.4 r136177 (Qt5.6.2)
RAM: 1024MB, 1 CPU, Nested Paging on
VideoRAM: 7MB
Audio driver: Windows DirectSound
Audio controller: ICH AC97
Audio output on, Audio input on
Network adapter: On, NAT
USB: On, UBS 2.0 (OHCI + EHCI)
Mode ID : 0x0039004
Recording: Nope
Driver: Devs:/AHI/ac97.audio
Version: ac97.audio 6.6 (22.03.2017)Intuition is attempting to reset the screen,
please close all windows except Wanderer's ones | poseidon.library | Root hub has been enumerated
Failure | poseidon.library | Opening pciusb.device unit 2 failed device/eunit failed to open (-1)
Error | poseidon.library | Failed to load config from 'ENVARC:Sys/poseidon.prefs'!
| poseidon.library | PoPo kick ass.
Error | poseidon.library | Failed to load config from 'ENV:Sys/poseidon.prefs'!
Error | poseidon.library | Failed to load config from 'ENVARC:Sys/poseidon.prefs'!Error | poseidon.library | Couldn't save config.TEST USB 1.0TEST USB 2.0TEST USB 3.0
AROS-20170402-1-pc-i386-boot-iso
Thanks. I also confirmed that behavious under VBox. The question is how wide-spread this behaviour is under real hardware.I'm afraid it's a matter of philosophy) For example, the sound doesn't work for me in the same VMWare Player and VBox.
Are the problems you are describing specific to the Test ISO or are they also present in Reference ISO?I'm don't tested Reference ISO.
@caveman
Is this a problem for some software? DejaVu fonts were moved to contrib repository, so they are still available in full build, but no longer available in core ISO build.
Integrated my AROS One x86 with "AROS-20170402-1-pc-i386-boot-iso", the system started without problems from VMware, the DVD in Live works well, updated also some icons created by me, in the next days I will try to install and test the various applications, thanks Deadwood for the great work done ;)It's fine. We'll use it, if you are ever shared. I think that more specifics are needed: attach a script for Install, for example. Create a bug here (https://github.com/deadw00d/AROS/issues?q=is%3Aopen+is%3Aissue+project%3Adeadw00d%2FAROS%2F3).
It's fine. We'll use it, if you are ever shared. I think that more specifics are needed: attach a script for Install, for example. CreateMy AROS x86 and 68k distribution has always been available for everyone even if it's ignored in this forum, unfortunately I'm not a developer and I don't have my own site to post it, maybe that's why it's not considered.
My AROS x86 and 68k distribution has always been available for everyone even if it's ignored in this forum, unfortunately I'm not a developer and I don't have my own site to post it, maybe that's why it's not considered.No that's not true.
I will make some det, but on my old WMWare Player the audio works perfectly and also the USB3 port works on WMWare, see screenshot:On your old WMWare Player - which version is it? If you state something, write information. No information - nothing to discuss.
however how should I use the ping command
@ntromans
Thanks for the test, two questions:
1) Does the Netgear dongle work with Reference ISO?
2) With regards to you second hardware, can you edit the grub command line and remove the pciusb.device module line and then see if AROS boots (this disables USB support)
Environment:
------------
VMware 15 Player : 15.5.2 build-15785246
RAM: 1024MB, 1 CPU, no checkmarks in Virtualization engine
Display: Specify to 1024x768, no Accelerate 3D graphics
Sound: Specify host sound card: Roland Rubix 24, Connect at power on
Network: NAT, Connect at power on
USB: USB 1.1 Checkmark on Show all USB input devices
After start:Environment:
------------
VMware 15 Player : 15.5.2 build-15785246
RAM: 1024MB, 1 CPU, no checkmarks in Virtualization engine
Display: Specify to 1024x768, no Accelerate 3D graphics
Sound: Specify host sound card: Roland Rubix 24, Connect at power on
Network: NAT, Connect at power on
USB: USB 2.0 Checkmark on Show all USB input devices
After start:Environment:
------------
VMware 15 Player : 15.5.2 build-15785246
RAM: 1024MB, 1 CPU, no checkmarks in Virtualization engine
Display: Specify to 1024x768, no Accelerate 3D graphics
Sound: Specify host sound card: Roland Rubix 24, Connect at power on
Network: NAT, Connect at power on
USB: USB 3.0 Checkmark on Show all USB input devices
After start:My old links don't work because I had to distribute the new version, not having a site many users downloaded the old one instead of the new one, then came health problems (operated on one eye) as well as small old age sicknesses.Links to google drive do not belong to you?
I don't know of any distributions with m68k-aros architecture except yours AROS One.user AMIGASYSTEM already addressed that part, as there are a couple of them some created waaay before AROS-One (such as ORCA/vision) and others (such as ApollOS) that are pretty new when comparing. Perhaps you should have a closer look at my turds ( https://ae.amigalife.org/index.php?topic=76.0 ) (even though ORCA does not get mentioned there simply because the website went belly up ages ago, and neither is the distribution being updated anymore afaik) ;)
What we compile needs to be tested. Applications for m68k-aros will not appear on their own.Sure, and in light of the above that has already be done or when speaking of apollos _is_ being done.
ApolloOS not related to m68k-aros.It started out as m68k-aros and much of the original codebase is still there.
These guys have no prejudices and it's just a soup from different m68 software.Your words... not mine ;)
Officially: Instead of just porting AROS from Intel to 68k, ApolloOS will be accesses Amiga chipset and 68k directly instead of using AROS HAL.That is correct. As far as i have been able to tell/see is that the abstraction layer posed some speed related issues (and from the thread-responses they didn't actually quite seem to understand why this layer even exist) so basically they ripped (are ripping) that layer out of the equation.
I have a sample of this creativity, it's beautiful and unstable AmigaOS build.No idea how that could have happened :D
I will look towards AROS Vision, it seems to make sense, thanks.A heads up... if you are biased against mix- and matching... aros vision is one big mixed pile (or at least it used to be one big messed up pile of software that required quite some work to get it a bit more organized)
However, we cannot download anything from the links you provide (https://ae.amigalife.org/index.php?topic=530): 404 Not found or No access.AROS One x86 1.3 was available here: https://ae.amigalife.org/index.php?topic=510.0
AROS One x86 1.3 was available here:Sorry AMIGASYSTEM, that might have been my wrongdoing because i linked to your first thread about AROS one (i will try to fix that tomorrow).
ORCA does not get mentioned there simply because the website went belly up ages ago, and neither is the distribution being updated anymore afaik) ;)
I have compiled the data about USB in VM into two table.
bottom table - what was expected, top table - what happened:
Riguardo la mia richiesta fatta nel post precedente, la riposto qui:
Da quanto ho notato InstallAROS ignora la Directory che ho aggiunto (Ufficio, Musica ecc.) nella ISO da me creata, c'è un modo per forzare l'installazione di queste Directory?
Just place them into Extras like I did on Icaros. Yes, there's a reason for Icaros' strange file organization.Paolo as mentioned in another post also on my AROS One I used "Extras" but I don't like that they are "hidden", also because on AROS One 68k the new folders are externally in the Root and this could be confusing.
the iso test when it boots and I enter the system if I restart with the classic keyboard commands "ctrl + alt + del" everything crashes with a "software failure"
@nikos
Hello Nikos, good to see you back. What network device did you use on your laptop?
Trying to play any sound via Terratec Aurion soundcard crashed the machine hard, needing a power cycle. This card is fine with normal Icaros aside from not being properly initialised on power up (gives distorted sound until a reset and then is fine).
@all
There is new testing ISO in the first post 20170402-2
@all
There is new testing ISO in the first post 20170402-2
Please test:
- warm reboot (Wanderer->Restart AROS)
- cltr+alt+delete
- realtek8180.device crash
- garbled sound with HDAudio
- garbled sound with sb128
- atheros.device crash
@all
There is new testing ISO in the first post 20170402-2
VirtualBox 5.0.40
Please test:
- warm reboot (Wanderer->Restart AROS) work OK
- cltr+alt+delete work OK
- garbled sound with HDAudio System slow - the sound is full of noise
- garbled sound with sb128 system no detected sound card
@all
There is new testing ISO in the first post 20170402-2
Please test:
- warm reboot (Wanderer->Restart AROS)
- cltr+alt+delete
- realtek8180.device crash
- garbled sound with HDAudio
- garbled sound with sb128
- atheros.device crash
On my DELL Latitude 520 wi-fi with atheros is now working :)
Warm reboot does not work as the whole computer shuts down.
Shot down computer from menu freeze the computer as before.
Restart Computer and Restart AROS from menu also shuts down the computer.
System Explorer worked in 2016.
Now I get this:
https://imgshare.io/image/img-20201216-002851574.NQHLYw
It should reset the OS, just like on real Amiga hardware. Not a complete reboot.@all
There is new testing ISO in the first post 20170402-2
Please test:
- warm reboot (Wanderer->Restart AROS)
- cltr+alt+delete
- realtek8180.device crash
- garbled sound with HDAudio
- garbled sound with sb128
- atheros.device crash
On my DELL Latitude 520 wi-fi with atheros is now working :)
Warm reboot does not work as the whole computer shuts down.
Shot down computer from menu freeze the computer as before.
Restart Computer and Restart AROS from menu also shuts down the computer.
System Explorer worked in 2016.
Now I get this:
https://imgshare.io/image/img-20201216-002851574.NQHLYw
About System Explorer - you screen shot suggests you installed the ISO to harddrive. Is that correct? If so, you are having old drivers (hidd files) which conflict with new kernel. You need to remove those.
What should CTRL+ALT+DELETE do? W warm reboot of AROS or a complete reboot of a machine?
@all
There is new testing ISO in the first post 20170402-2
VirtualBox 5.0.40
Please test:
- warm reboot (Wanderer->Restart AROS) work OK
- cltr+alt+delete work OK
- garbled sound with HDAudio System slow - the sound is full of noise
- garbled sound with sb128 system no detected sound card
Does it mean this ISO actually started on your VBox 5.0.40? I think you were reporting that previous test ISO did not work for you.
I must disable IO-APIC then the boot.Hehe. That's for sure.
It should reset the OS, just like on real Amiga hardware. Not a complete reboot.
It is correct, I installed the ISO to HDD. I did a clean install with format and looking at the time of the files it is all the same so must be from same install.
I must disable IO-APIC then the boot.
It should reset the OS, just like on real Amiga hardware. Not a complete reboot.
Do you have a version of AROS that does that? I tried Icaros 2.1 in VBox and it reboots the machine instead of reseting AROS.It is correct, I installed the ISO to HDD. I did a clean install with format and looking at the time of the files it is all the same so must be from same install.
Can you try booting from livecd and running SysExplorer from livecd to see if it crashes as well? I does not crash for me in VBox.
In the VM setting. AROS boot parameter me not work (ACPI=disable - is it correct?)I must disable IO-APIC then the boot.
Did you disable it in VM setting or via AROS boot parameters?
In the VM setting. AROS boot parameter me not work (ACPI=disable - is it correct?)I must disable IO-APIC then the boot.
Did you disable it in VM setting or via AROS boot parameters?
Almost on all ABI v.0 versions of AROS warm-reset is working including your 2016 version :)
When it did not work I'm most certain it was driver related, some hidd, but then it froze the machine and not turn off computer like like your 2017 version.
I tried the Live-CD of the new 2017 build and it is the same problem. SysExplorer crash and key combo. turn off hardware.
Edit:
I found out it is the native driver. On my hardware, IntelGMA.
Booting from VESA mode SystemExplorer does not crash. Key combo is still shutting down the computer.
What should CTRL+ALT+DELETE do? W warm reboot of AROS or a complete reboot of a machine?It should reset the OS, just like on real Amiga hardware. Not a complete reboot.
It is correct, I installed the ISO to HDD. I did a clean install with format and looking at the time of the files it is all the same so must be from same install.
I think in this case, ctrl-alt-del should be disabled and ctrl-amiga-amiga should be a hard reset. it boots that quickly it doesn't really need a command just to restart the os(ctrl-amiga-amiga crashes my aros box anyway)
I think in this case, ctrl-alt-del should be disabled and ctrl-amiga-amiga should be a hard reset. it boots that quickly it doesn't really need a command just to restart the os(ctrl-amiga-amiga crashes my aros box anyway)
I think in this case, ctrl-alt-del should be disabled and ctrl-amiga-amiga should be a hard reset. it boots that quickly it doesn't really need a command just to restart the os(ctrl-amiga-amiga crashes my aros box anyway)Don't be fooled. When AROS learns to do everything that other OS do during boot, it will slow down in the same way. It's only a matter of time.
What should CTRL+ALT+DELETE do? W warm reboot of AROS or a complete reboot of a machine?It should reset the OS, just like on real Amiga hardware. Not a complete reboot.
It is correct, I installed the ISO to HDD. I did a clean install with format and looking at the time of the files it is all the same so must be from same install.
Sorry but...
didn't warb reset (OS Only) trigger with Ctrl+lAmiga+rAmiga
and
cold (whole pc) reset trigger with Ctrl+Alt+Del?
I am quite sure Ctrl+Alt+Del should reset the whole PC, while Ctrl+lAmiga+rAmiga OS only.
I always though that was the same. I did not know AROS supports a shut down key combo, but you are right.
On my DELL laptop I use CTRL+LWIN+MENU key
Anyway, warm-reset is not working with 2017 build on my DELL laptop, but works with 2016 build.
I always though that was the same. I did not know AROS supports a shut down key combo, but you are right.
On my DELL laptop I use CTRL+LWIN+MENU key
Anyway, warm-reset is not working with 2017 build on my DELL laptop, but works with 2016 build.
What if you use VESA for video and don't start network?
Thanks - if you have wired networking can you try if you get the freezes there as well?
First post update, version 20170402-3 available:
- no changes to ISO
- linux and windows hosted builds available
AROS ABIv0 20170402 changes:
Functionalities:
Align naming of graphic drivers and make them visible in SysExplorer (Kalamatee)
Query graphics driver for 3D subdriver (Kalamatee)
C library improvements (Mazze, Kalamatee)
Kernel ACPI support (Kalamatee)
SysMon listing tasks better (Kalamatee)
Kernel IO-APIC support (Kalamatee, Schulz)
Kernel interrupt support (Kalamatee, Schulz)
Kernel SMP support (Kalamatee, Schulz)
Kernel shutdown/reboot support (Kalamatee)
Kernel spinlock support (Kalamatee, Schulz)
Public locking mechanism support (Kalamatee, Schulz)
Kernel CPU cores control (Kalamatee, Schulz)
processor.resource improvements (Kalamatee, Schulz)
SMP-enabled Message Port handling (Kalamatee, Schulz)
Protect access to Exec resources (Kalamatee)
Better measurement of CPU usage (Schulz)
SysMon listing CPU usage better (Kalamatee)
Graph.mcc (Kalamatee)
picture.datatype DTM_Write support (Mazze)
vusbhci.device (DizzyOfCRN)
Kernel MSI interrupt support (Kalamatee)
List.mui improvements (Kalamatee)
ACPI button driver (Kalamatee)
PCI driver IRQ routing table (Kalamatee, Schulz, Neil)
64-bit support:
misc fixes (Kalamatee, Schulz)
ahi.device, ac97.audio, hdudio.audio 64-bit support (Kalamatee)
pciusb.device 64-bit support (Kalamatee)
ata.device 64-bit support (Schulz)
Updates:
Flexcat 2.18 (Mazze)
libz 1.2.11 (Mazze)
libjpeg 9b (Mazze)
libpng 1.6.28 (Mazze)
AROS build system (Kalamatee)
Icons (Paolone)
GCC-6.3.0 (patch file) (Kalamatee)
Fixes:
Corrected datatype descriptors (Neil, Mazze)
VGA driver (Kalamatee, Neil)
Documentation (Neil, Kalamatee)
X11 driver (deadwood)
MUI (o1i, Kalamatee)
Shell commands (Neil, Kalamatee, Mazze, Schulz)
dos.library (Kalamatee)
C:Decoration (Kalamatee)
Kernel (Kalamatee)
Catalogs (polluks, mmartinka, Kalamatee)
Mesa (Kalamatee, Neil)
emul-handler (Neil)
console.device (Schulz)
Intuition (Schulz, Neil)
Preferences (Neil, balaton)
kms.library (Kalamatee)
pciusb.device (Schulz)
C library (deadwood)
Kernel ACPI support (Neil)
Kernel interrupt support (Neil)
PCI driver (Neil)
Kernel IO-APIC support (Neil)
atheros5000.device (Neil)
Kernel shutdown/reboot support (Neil)
Windows-hosted booting (deadwood)
While integrating AROS system files I noticed two differences:
- tool "delete" and its icon in system/wanderer/tools are not present
- smartcan is not present in wbstartup
This is a developer build with some debug enabled - I'd suggest just testing the ISO, not including it into a release. If all goes well there will be a new clean build available
Glad to hear it.
@all, please also test DEV-4 on your real hardware.
@AMIGASYSTEM
Thanks for tests. For VirtualBox tests, select "Intel HD Audio".
@AMIGASYSTEM
I think associations are added via def Icons in ENV:SYS.
Tested 5-DEV-1 and the audio worked fine on my VMWare, VirtualBox and PC Real Netbooks DELL Inspiron Mini 910
Are the ABIv0 images using Grub Bootloader or Grub2 ?I can answer that for you as well and if you don't mind me doing so: that would be grub2 (has been so for years)
i can't debug deadwood, an infinite series of strings comes out in the sashimi output window
@aGGreSSorMy motherboard (Gigabyte H370M DS3H) has USB 2.0 (black) and USB 3.0 ports (blue).
Thanks for tests. What is the difference between first and second test - both seems to be using same USB drive and same VMWare 15 Player?
@aGGreSSor
Can you capture sashimi output from DEV-4 and 2.0 port when pluggin in USB drive?
Please start sashimi from shell like this:Sashimi, little information is recorded.
sashimi > ram:out.txt
And them upload somewhere the resulting text file for me to examine.
INT=C008
INT=C008
INT=C008
INT=C008
INT=C008
Sashimi installed ([Ctrl]+C or "Break 1" to remove)
Sashimi removed.
VMware 15 in USB 2.0 mode, DEV-4INT=C004
ehciIntCode/1240: PCI Int Port 1 Change 00001003
ehciIntCode/1240: PCI Int Port 2 Change 00001000
ehciIntCode/1240: PCI Int Port 3 Change 00001000
ehciIntCode/1240: PCI Int Port 4 Change 00001000
ehciIntCode/1240: PCI Int Port 5 Change 00001000
ehciIntCode/1240: PCI Int Port 6 Change 00001000
hub_nHubTask/535: Port changed at 00000002, Numports=6!
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 0109e688, 4)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
hub_nConfigurePort/1148: Configuring port 1 of hub 0x0102f204
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 0109e5ec, 4)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
hub_nConfigurePort/1160: Status 0x0101, change 0x0000
hub_nConfigurePort/1182: There's something at port 1!
hub_nConfigurePort/1186: A
hub_nConfigurePort/1195: B
hub_nConfigurePort/1202: C
hub_nConfigurePort/1204: C1
hub_nConfigurePort/1207: C2
hub_nConfigurePort/1210: C3
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=3
hub_nConfigurePort/1212: C4
hub_nConfigurePort/1218: PORT_RESET failed 3.
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
hub_nConfigurePort/1375: Y
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
hub_nConfigurePort/1388: Z
psd_28_psdSendPipe/4179: psdSendPipe(0102f344, 0102f26c, 1)
INT=C008
INT=C008
INT=C008
INT=C004
ehciIntCode/1240: PCI Int Port 1 Change 0000110A
ehciIntCode/1240: PCI Int Port 2 Change 00001000
ehciIntCode/1240: PCI Int Port 3 Change 00001000
ehciIntCode/1240: PCI Int Port 4 Change 00001000
ehciIntCode/1240: PCI Int Port 5 Change 00001000
ehciIntCode/1240: PCI Int Port 6 Change 00001000
hub_nHubTask/535: Port changed at 00000002, Numports=6!
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 0109e688, 4)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_28_psdSendPipe/4179: psdSendPipe(0102f344, 0102f26c, 1)
INT=C004
ehciIntCode/1240: PCI Int Port 1 Change 00001103
ehciIntCode/1240: PCI Int Port 2 Change 00001000
ehciIntCode/1240: PCI Int Port 3 Change 00001000
ehciIntCode/1240: PCI Int Port 4 Change 00001000
ehciIntCode/1240: PCI Int Port 5 Change 00001000
ehciIntCode/1240: PCI Int Port 6 Change 00001000
hub_nHubTask/535: Port changed at 00000002, Numports=6!
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 0109e688, 4)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
INT=C004
ehciIntCode/1240: PCI Int Port 1 Change 0000110A
ehciIntCode/1240: PCI Int Port 2 Change 00001000
ehciIntCode/1240: PCI Int Port 3 Change 00001000
ehciIntCode/1240: PCI Int Port 4 Change 00001000
ehciIntCode/1240: PCI Int Port 5 Change 00001000
ehciIntCode/1240: PCI Int Port 6 Change 00001000
hub_nConfigurePort/1148: Configuring port 1 of hub 0x0102f204
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 0109e5ec, 4)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
hub_nConfigurePort/1160: Status 0x0110, change 0x0003
hub_nConfigurePort/1388: Z
psd_28_psdSendPipe/4179: psdSendPipe(0102f344, 0102f26c, 1)
hub_nHubTask/535: Port changed at 00000002, Numports=6!
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 0109e688, 4)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_28_psdSendPipe/4179: psdSendPipe(0102f344, 0102f26c, 1)
INT=C008
INT=C008
INT=C008
INT=C008
INT=C008
INT=C004
ehciIntCode/1240: PCI Int Port 1 Change 00001103
ehciIntCode/1240: PCI Int Port 2 Change 00001000
ehciIntCode/1240: PCI Int Port 3 Change 00001000
ehciIntCode/1240: PCI Int Port 4 Change 00001000
ehciIntCode/1240: PCI Int Port 5 Change 00001000
ehciIntCode/1240: PCI Int Port 6 Change 00001000
hub_nHubTask/535: Port changed at 00000002, Numports=6!
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 0109e688, 4)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
INT=C008
hub_nConfigurePort/1148: Configuring port 1 of hub 0x0102f204
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 0109e5ec, 4)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
hub_nConfigurePort/1160: Status 0x0111, change 0x0000
hub_nConfigurePort/1182: There's something at port 1!
hub_nConfigurePort/1186: A
hub_nConfigurePort/1195: B
hub_nConfigurePort/1202: C
hub_nConfigurePort/1204: C1
hub_nConfigurePort/1207: C2
hub_nConfigurePort/1210: C3
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=3
hub_nConfigurePort/1212: C4
hub_nConfigurePort/1218: PORT_RESET failed 3.
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
hub_nConfigurePort/1375: Y
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
psd_27_psdDoPipe/4140: psdDoPipe(0102f294, 00000000, 0)
psd_30_psdWaitPipe/4295: psdWaitPipe(0102f294)=0
hub_nConfigurePort/1388: Z
psd_28_psdSendPipe/4179: psdSendPipe(0102f344, 0102f26c, 1)
INT=C008
Sashimi installed ([Ctrl]+C or "Break 8" to remove)
Sashimi removed.
@aGGreSSorDEV-6 found pen only with USB 1.1 and none in USB 2.0 and USB 3.0.
Can you try DEV-6:
https://axrt.org/development/AROS-20170402-5-DEV-6-pc-i386-boot-iso.zip
If your disk in 2.0 port still does not work, can you capture debug?
INT=C008
INT=C008
INT=C008
INT=C008
INT=C008
Sashimi installed ([Ctrl]+C or "Break 1" to remove)
Sashimi removed.
INT=C004
ehciIntCode/1240: PCI Int Port 1 Change 00001003
ehciIntCode/1240: PCI Int Port 2 Change 00001000
ehciIntCode/1240: PCI Int Port 3 Change 00001000
ehciIntCode/1240: PCI Int Port 4 Change 00001000
ehciIntCode/1240: PCI Int Port 5 Change 00001000
ehciIntCode/1240: PCI Int Port 6 Change 00001000
hub_nHubTask/535: Port changed at 00000002, Numports=6!
hub_nConfigurePort/1148: Configuring port 1 of hub 0x0102f204
hub_nConfigurePort/1160: Status 0x0101, change 0x0000
hub_nConfigurePort/1182: There's something at port 1!
hub_nConfigurePort/1186: A
hub_nConfigurePort/1195: B
hub_nConfigurePort/1202: C
hub_nConfigurePort/1204: C1
hub_nConfigurePort/1207: C2
hub_nConfigurePort/1210: C3
cmdControlXFerRootHub/796: EHCI: Resetting Port (ok)
cmdControlXFerRootHub/799: EHCI: Port status=00001001
cmdControlXFerRootHub/805: EHCI: Reset=BAD!
cmdControlXFerRootHub/810: EHCI: Reset=BAD!
cmdControlXFerRootHub/811: EHCI: Highspeed=NO
cmdControlXFerRootHub/812: EHCI: Port status=00001101
cmdControlXFerRootHub/816: EHCI: Transferring ownership to UHCI/OHCI port 0
cmdControlXFerRootHub/821: EHCI has no companion controller, can't transfer ownership!
hub_nConfigurePort/1212: C4
hub_nConfigurePort/1218: PORT_RESET failed 3.
hub_nConfigurePort/1375: Y
hub_nConfigurePort/1388: Z
INT=C008
INT=C008
INT=C008
INT=C008
INT=C008
Sashimi installed ([Ctrl]+C or "Break 1" to remove)
Sashimi removed.
DEV-7USB 2.0 mode work (attachment)!
https://axrt.org/development/AROS-20170402-5-DEV-7-pc-i386-boot-iso.zip
Same test please.
INT=C008
INT=C008
INT=C008
INT=C008
INT=C008
Sashimi installed ([Ctrl]+C or "Break 1" to remove)
Sashimi removed.
Did you try DEV-7?
Please post sashimi debug output.
@mmartinka
Thanks. AC97 is broken for VBox 6.x and will not work
For Intel HD, can you follow this procedure with 6.1.16 using DEV-4 ISO:
"Please boot the ISO with the default option in grub selected. Then start Development/Debug/Sachimi and make the window full screen. Then start AHI Prefs and press play test sound once. Post the screen shot showing content of sashimi please"
Ok thanks deadwood, i meanwhile with your DEV-7 update my AROS One, integrated support US3 and works perfectly :)
On PC DELL Mini and ACER One Real with DEV-7 AROS One does not start the screen remains in the eyes of the cat ...
If I restore DEV-4 USB Drivers, DELL Mini and ACER One boot up quietly.
This ISO should have USB 2.0 working under VMWare, VirtualBox and real hardware ..If i select USB 2.0 controller in virtualbox then i am unable to wipe the disk.
New ISO for testing. This ISO should have USB 2.0 working under VMWare, VirtualBox and real hardware where it was already working (solving regression introduced in DEV-2)(https://i.postimg.cc/J4rZwsy6/DEV-8-test.png)
Hello,
New ISO for testing. This ISO should have USB 2.0 working under VMWare, VirtualBox and real hardware where it was already working (solving regression introduced in DEV-2)
https://axrt.org/development/AROS-20170402-5-DEV-8-pc-i386-boot-iso.zip
Also fixes icon for Development directory and makes development files being installed with InstallAROS.
Thank you deadw00d
If i select USB 2.0 controller in virtualbox then i am unable to wipe the disk.
I can produce an exact error message in case that i more convenient for you, but the gist of it is that aros report that is unable to access usbscsii device number 0, named du0 (while it is actually there as reported by hd-toolbox/info command).
I reviewed past post and it looks like USB 2.0 under VirtualBox was working for you in DEV-3, DEV-5 and DEV-7. Do I read correctly that DEV-8 is a regression for you?No, they didn't work under VirtualBox, but it seems USB devices were at least bound to classes and with DEV-8, this definitely doesn't happen. Apparently for me the best was DEV-7 under VMware 15 Player. As far as I can tell, Poseidon is sorting through the drivers to play its own sound about connecting the USB device by default, that's all that can be seen.
@nikos
Hello Nikos, good to see you back. What network device did you use on your laptop?
Yes, correct as Salvo said, Atheros.
With Power Off my laptop freeze. Restart Computer, Restart AROS works perfect.
Are some things faster now? Everything seams stable and fast :)
I write this from Odyssey on your nice build :)
Edit: Great news :) It is definatly faster!! I had a video where I recorded GPmark tests around 3 years ago. All tests with Deadwoods latest builds show a boost at around 10%. That is massive :)
I had some time to test a little now. I forgot that I changed the CPU on the laptop so it is not faster than before. I do not want to spread false info. The speed with latest backports from abi v.1 is exactly the same as from some years back regarding 3D, fps. This is IntelGMA.
ok deadwood i have no more problems with usb ports :)
I reviewed past post and it looks like USB 2.0 under VirtualBox was working for you in DEV-3, DEV-5 and DEV-7. Do I read correctly that DEV-8 is a regression for you?No, they didn't work under VirtualBox, but it seems USB devices were at least bound to classes and with DEV-8, this definitely doesn't happen. Apparently for me the best was DEV-7 under VMware 15 Player. As far as I can tell, Poseidon is sorting through the drivers to play its own sound about connecting the USB device by default, that's all that can be seen.
Windows 10 Home Single Language (Russian)What is your host operating system?I reviewed past post and it looks like USB 2.0 under VirtualBox was working for you in DEV-3, DEV-5 and DEV-7. Do I read correctly that DEV-8 is a regression for you?No, they didn't work under VirtualBox, but it seems USB devices were at least bound to classes and with DEV-8, this definitely doesn't happen. Apparently for me the best was DEV-7 under VMware 15 Player. As far as I can tell, Poseidon is sorting through the drivers to play its own sound about connecting the USB device by default, that's all that can be seen.
DEV-9 on my VirtualBox doesn't work with USB 2.0 and USB 3.0, it only works with USB 1.1
With VMWare, USB 2.0 and USB 3.0, as always work perfectly.
@magoriumIt is a very weird phenomenon. I am able to reproduce the wipe error with dev-8 and virtualbox USB 2.x controller. Switching to usb 1.x controller just wipes the disk as expected. With dev-7 i was able to wipe the disk (both USB 1.x and 2.x virtualbox controller) without issues (but it might be i was lucky on my tries) but AROS "lost" the pendrive device during boot (insert bootable medium / cat-eyes)..
I can confirm the I/O error during copying, though wiping USB pendrive works for me.
On my VirtualBX v5.2.44 r139111, con anyone DEV has it ever worked USB2.0 e USB3.0, only USB 1.1 worked
@magorium, aGGreSSor
Please try DEV-9 under VirtualBox
On my setup (Linux Mint 20.1 host/VBox 6.1.18) I'm now able to format and do a full installation to USB pen drive under VirtualBox. Next I'm able to boot from PEN drive (load kickstart from CDROM, go to bootmenu and select pen drive for system booting)
https://axrt.org/development/AROS-20170402-5-DEV-9-pc-i386-boot-iso.zip
@aGGreSSor
Yes, there is definatelly something wrong with installation. You now have issues even with 1.1 which everyone else reports as working. Also DEV-9 has no changes to OHCI that could cause problems with 1.1. Maybe you can try re-installing VirtualBox and/or re-install Extensions Package?
With regards to hardware USB 3.0 ports, it might be Windows-related. I do all the testing with pendrive plugged into USB 3.0 port and VBox still works for me.I did my tests also on a USB 3.0 port. The pendrive that i tested is USB 2.x though. I don't have any free true 3.x devices around to be able to test atm.
test: dev10-deadw00d
host: linux64 debian deriviate
vm: virtualbox 6.1.18
usb 3.x: not detected
usb 2.x: detected. installed to USB pendrive ok.
usb 1.x: detected. installed to USB pendrive ok.
e.g. advise from bugtracker is to install win 10 pro and the issue is goneImpossible. It would take a week to migrate all the specific Windows software and my data I need to work on a new operating system. If the Windows were not fed now I would be under Linux and the problems of Windows wouldn't be interesting to me. :)
it seems to be a longstanding issues that gets closed over and over, and users do not seem to agree and put it back on their bugtrackerMost likely it is. OEM Windows and Windows Home Language is the most common Windows.
Impossible. It would take a week to migrate all the specific Windows software and my data I need to work on a new operating system. If the Windows were not fed now I would be under Linux and the problems of Windows wouldn't be interesting to me.Yeah, i know :-(
fwiw: showconfig does work when invoked from a shell window, but indeed i am also unable to start it from the icon. Increasing the stacksize by factor 10 did not solve that.
No no it's a Stack problem, ShowConfig works fine, the problem are the AROS icons where some functions present on OS3 are missing, to work ShowConfig needs the parameter "CLI" in the Toltypes, that you have to add manually, same thing of the Workbench Programs where in some cases you need the parameter "WB".No. ShowConfig just supports the definition of running from WB or not. If ShowConfig finds that was launched from WB, will open its own window.
To me ShowConfig but also other applications will never start without the CLI in the toolypes, even on OS3.9 ShowConfig needs that Option has Shell in the Tooltypes, on OS 3.9 also works without CLI parameter, so on AROS there is some problem?Look at the title bar of window in my screenshot. It's not written there "Output window".
char __stdiowin[]="CON://800/400/ShowConfig/AUTO/CLOSE/WAIT"
Thanks, yes I noticed the title on the bar, on AROS One on many Icons I had to use CLI in the Tooltype, so "in general" with this kind of applications how should I proceed without using CLI in the Tooltype?Developer is a big word for most people I know, myself included. ;)
I'm not a developer or just found some workarounds to make them work.