TLDR: >>>> https://github.com/deadwood2/AROS/labels/IBOTM <<<<

Here were are with another IBOTM! We continue with bug-fixing fun!


General rules are simple:

1) Bugs are selected from bugs reported > bug tracker
2) There is a poll made and community selects one bug from suggested bugs
3) I fix the bug.
4) Wait until next month; Go To 1;

The initial list of bugs will be related to ABIv0 i386 or ABIv11 x86_64. In effect bugs specific to m68k AROS or any other AROS flavor won't be added to poll options. Bugs can be in either AROS core system or in Contrib package. Bugs need to be reproducible on clean system releases, so bugs visible only on distributions won't be included.

ok voted

Thank you

Quick reminder - only one day left. Please vote!

Done!

Thank you.

And voting is now closed.

It has been a close race but at the end #135 is selected to be fixed in March. Thanks to all who voted.

many thanks

Okay, I had voted for #116, it will be for next time !

Hi All,

Here is ahci.device for tests:

https://axrt.org/...6-aros.zip

When you open HDToolbox you should now see full disk capacity. Existing partitions won't be "extended", but if you "wipe" and InstallAROS, the partition should be created to cover whole disk or 127GB if the disk is bigger than 127GB. Let me know if it works for you.

Many Thanks

Thank you for your efforts to improve AROS.

So if I understand correctly, with new ahci.device (version 0.9) you were able to partition the disk to have more than 8GB partition, but then when installing after reboot, you got the error?

Does it happen every time you try to install?
Is this happening on one of the recommended hardware?

Does you added comment mean that on this hardware also installing using old ahci.device gives errors?

Thanks for explanation. Additional question: What do you mean by "for first bits"? Does it mean that when you partition with new driver, reboot to old driver, start InstallAROS then it starts writing some files but process still crashes at some point and does not finish?

Please test the new driver with AHCI=slowstart grub kernel parameter. Does it solve the "-6" problem?

It's quite weird that old driver fails on newly partitioned drive :/

Can you do two tests:

1) repartition (Wipe option) the disk using ata.device and check if old ahci.device allows installing correctly
2) repartition the disk using ahci.device and check if installing 3-4 times work every time

If in both cases installing using old ahci.device works, I will prepare for you a few versions of new ahci.device to try to pin point where is the problem. Can you also share vendor id and product id of your AHCI chipset?

Ok, so let me understand correctly:

When you use 20220318-1 release, the old ahci driver partitions and installs AROS, but partition is limited to 8GB (as expected).

When you use 20220318-1 release, the new ahci driver partitions and installs AROS, and partition is not limited to 8GB.

Is this correct understanding?

Ok, good. That's a relief

I should be able to provide one more version of the driver with possibly shortened start up time.

Here is another version for tests:

https://axrt.org/development/ahci.device-0.9b.i386-aros.zip

*) recognizes hard disks bigger than 8GB
*) improved boot times by more than 50%
*) uses 60 MB of RAM less

Unless problems are found, this will be the "final" version for this IBOTM

all this is needed for some systems because from the bios I changed the entry from ata to sata ahci but the dvd does not boot

@Amiwell79

What do you mean?