@acmn
Bug reports are best made on AmigaOS's official support forum, where OS4 devs & beta-testers are more likely to see it.

_________________
Author of the PortablE programming language.
I love using Amiga OS4.1 on my A1-X1000 & Sam440
Don't forget the official support forum for OS4!

@ChrisH

Done already...MK

@all

One thing I noted: on a µ with its tiny amount of videomemory, I used to have 0% to 2% memory free on average. It is now easily 30%!
And as I already mentioned elsewhere, it feels snappier.
Good work! Love it.

OldFart

_________________
As long as I don't express my age in terms of 'years'
and my wealth not in terms of 'money',
I can still pass for rich young man...

@NutsAboutAmiga & Karlos

Sorry for the stupid question but where can i found this ENV:Warp3D/RadeonR200 ??
I search my entire ENV directory but i didn't found anythings !

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

@samo79

The default settings are compiled into the driver, so the directory won't exist until you want to change something. For example:

SetEnv save Warp3D/RadeonR200/wipeout/UseChromaTestABGR on

The above will create the necessary directory path and set the variable that instructs the driver to use the "wrong" colour order for chroma testing when the driver is being used by an executable called "wipeout".

_________________
IBrowse/AWeb user? amiga.org - classic browser edition

I'm pleased that rebooting from keyboard is once again fully working. Even for a (long) discontinued product like AmigaOneXE.

_________________
: AmigaOneXE (unmod.) 750FX/512 MB +stuff & AmigaOS 4.(0|1)
: A1200/68060&96MB/SCSI/EM1200-Voodoo3 & OS 3.5
: A500/1MB
: Pegasos (ff) 512 MB & MorphOS 1.4.5
Praise seitan.

@Thematic

On my 460 reboot from keyboard doesn't work anymore, when I press Ctrl + A sx + A dx the system reset but AmigaOS doesn't load.
This happened also with Update 4 for me

@kyle

Admittedly I use only PS/2 keyboard, no guesses from me if that makes any difference.

_________________
: AmigaOneXE (unmod.) 750FX/512 MB +stuff & AmigaOS 4.(0|1)
: A1200/68060&96MB/SCSI/EM1200-Voodoo3 & OS 3.5
: A500/1MB
: Pegasos (ff) 512 MB & MorphOS 1.4.5
Praise seitan.

Did anyone try it on a AmigaOne SE? It did not say it was supported but I hope it will work.

Coder

_________________
Can't get enough of me?
The Bucket Diary Blog
The Bucket Diary Twitter Account

@Coder

I wouldn't be surprised if the number of betatesters having A1SE as their only "OS4 system" would be less than 2.

_________________
: AmigaOneXE (unmod.) 750FX/512 MB +stuff & AmigaOS 4.(0|1)
: A1200/68060&96MB/SCSI/EM1200-Voodoo3 & OS 3.5
: A500/1MB
: Pegasos (ff) 512 MB & MorphOS 1.4.5
Praise seitan.

@Thematic

Its advisable on all ng amiga systems if you have a ps2 port you should use that as opposed to usb due to problems with os4 stack..

my amigaone keyboard resets nicely with the 3 finger salute!

Thank you Hyperion! I've got it installed and seems like things have improved and i'm loving the addiotional refining of RuninUAE and its integration into workbench.

@realize
Quote:

Its advisable on all ng amiga systems if you have a ps2 port you should use that as opposed to usb due to problems with os4 stack..

I can vouch for that on my µA1. PS2 input no problems; USB input gives periodic freezes.

_________________
SAM Flex 800MZ with 1GB memory & OS4.1u4

@Xenic

The problem with USB is that it is run as a task and not by an interrupt like a real Amiga input dervice or like PS/2.. If you get a yellow alert forget it. Might as well hard reset on the case if you have reset on case.

On a Sam 440 you can click mouse every ten seconds and the yellow alert will disappear. Or come back for another ten seconds.

On my X1000 being limited to USB makes my system utterly useless! If that gets a yellow alert I lose everything. It never detects mouse input, not even after ten seconds. So I have to hard reset. Which is more annoying because the X1000 is a bigger and more powerful machine that takes so much longer to boot again.

What I think they should do is run the USB input task as a soft interrupt. All it does is pass messages around the system anyway once it reads from the hardware. And a soft interrupt runs higher than a task so the message would get processed immediately.

Perhaps the USB task is simply not running high enough? In any case if the USB driver uses interrupts at all when data is tranferred then we really have no excuse for USB mice freezing on OS4 systems. There should be a direct line of code there straight to the input.device.

I mean. OS4 already gets flamed enough having buggy USB drivers, that still need to be fixed, and some people think should be completely replaced. This just makes it worse! If Apple could do it with OSX why can't it be done with AmigaOS4?

@Hypex

Usually, on my SAM440 it is enough to remove keyboard USB plug and reconnect it. Does that work on x1000 to avoid reboot?

(on SAM the reboot is not too slow, when compared to going for the USB plug. but it's annoying to manually open all apps and documents again, untill we have SW shutdown and applications restore also it would be nice to be able to enable SW reboot also when keyboard+mouse is not working.)


btw. Anyone thought of building PS2 interface to SAM/X1000 ?
( I Imagine it could be done from GPIO lines, I2C or from UART port. )


Any info about who are working with AOS4 USB stack? Is there lack of resources for that? This bug hunt should be high priority.
(I imagine if I had time to contribute I could e-mail SSolie to apply for "USB stack/driver bug hunter" -position.)

Last edited by KimmoK on 18-Aug-2012 at 08:50 AM.
Last edited by KimmoK on 18-Aug-2012 at 08:50 AM.

_________________
- KimmoK
// For freedom, for honor, for AMIGA
// "priest" is just the RED goaul in me
// The multicolor AmigaFUTURE IS NOW !!

@Karlos

Quote:

The default settings are compiled into the driver, so the directory won't exist until you want to change something. For example: SetEnv save Warp3D/RadeonR200/wipeout/UseChromaTestABGR on

Good thank you for explain

Quote:

The above will create the necessary directory path and set the variable that instructs the driver to use the "wrong" colour order for chroma testing when the driver is being used by an executable called "wipeout".

Now graphics works perfectly and maybe i discover also why the game freeze (i'm currently in deep testing) so i can't say for sure yet

It seems a problem related to the Sam440 clock usage, altrough the results are not always reliable nor always reproducible with the same effects or with all WOS games

My Sam440 Flex is the 800 Mhz model:

CPU: 800 Mhz - FSB: 133 Mhz - PCI: 133

So I use HyperClock to turn down the values, i set my at 667 Mhz and then a 733, then i reset the Amiga and i start again WipeOut 2097

Now WipeOut (i'm trying the demo version from Aminet) don't freeze but always crash instead (ISI) at some point ..

Quote:

rash log for task "wipeout_demo" Generated by GrimReaper 53.5 Crash occured in module wipeout_demo at address 0x55D2DF0C Type of crash: ISI (Instruction Storage Interrupt) exception Register dump: GPR (General Purpose Registers): 0: 55D20448 54EFE210 55336008 54EFE274 00000000 00000000 00000280 000001E0 8: 00000000 6F9A9E2C 0000000A 00000020 00000008 00000009 5462CD48 54EFEC2E 16: 000000FF 00000000 00000000 00000000 00000001 00000000 00000001 00000001 24: 00000000 0000D2F0 00000000 00000000 00000000 00000000 00000000 00000000 FPR (Floating Point Registers, NaN = Not a Number): 0: nan 0 1 0.00274036 4: 7.50959e-06 0.5 66581.5 2.46571e-05 8: 2.08757e-09 1 -0.5 2.46565e-05 12: nan 640 0 0 16: 0 0 0 0 20: 0 0 0 8.88967e+20 24: 0 0 2.65249e-315 -1.17478e+229 28: 0 1.35808e-312 8.8275e-311 1.78006e-307 FPSCR (Floating Point Status and Control Register): 0xA2000100 SPRs (Special Purpose Registers): Machine State (msr) : 0x0002F030 Condition (cr) : 0x28444822 Instruction Pointer (ip) : 0x55D2DF0C Xtended Exception (xer) : 0x20000002 Count (ctr) : 0x6F9A9E2C Link (lr) : 0x55D205B8 DSI Status (dsisr) : 0x00000000 Data Address (dar) : 0x7FDC03E0 680x0 emulated registers: DATA: 00000001 FFFFFFFF 00000001 5852B760 00000001 FFD50001 FFD60001 568FBBA4 ADDR: 54EFEF5C 5852B760 5852B760 568FBBA4 54EFEFFC 54EFEFF0 568FA4D0 54EFEF3C FPU0: 0 0 0 0 FPU4: 0 0 0 0 Symbol info: Instruction pointer 0x55D2DF0C belongs to module "wipeout_demo" (HUNK/Kickstart) Stack trace: module wipeout_demo at 0x55D2DF0C (section 1 @ 0x8AF08) module wipeout_demo at 0x58B5E970 (section 17 @ 0x6BC) module wipeout_demo at 0x55D49C98 (section 1 @ 0xA6C94) module wipeout_demo at 0x55D2E684 (section 1 @ 0x8B680) native kernel module kernel+0x00023008 native kernel module kernel+0x000231b8 module LIBS:powerpc.library at 0x6FAC4CF0 (section 5 @ 0x4CD4) module LIBS:powerpc.library at 0x6FAC3F3C (section 5 @ 0x3F20) native kernel module kernel+0x0005514c native kernel module kernel+0x009bdbf6 PPC disassembly: 55d2df04: 7c0803a6 mtlr r0 55d2df08: 4e800020 blr *55d2df0c: 90830000 stw r4,0(r3) 55d2df10: 90a30004 stw r5,4(r3) 55d2df14: 90c30008 stw r6,8(r3) System information: CPU Model: AMCC PPC440EP V1.3 CPU speed: 666 MHz FSB speed: 133 MHz Extensions: Machine Machine name: Sam440EP Memory: 1048576 KB Extensions: bus.pci

Heretic 2 instead does not work with the lower settings, it just freeze during the loading of the first level while it start (but freeze during game) with the original CPU settings (800 Mhz)

So just to continue my test i reset the CPU value at the original settings (800 Mhz) and with some surprise WipeOut don't freeze anymore but as with the first experiment at 667/733 clock just crash ...

As you can see these experiments do not seem to give a unique result but at this point I think that the problem may be related to CPU clock

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

@Hypex

quote: “If you get a yellow alert forget it”

I have patch for that, but it not complete yet, depending on how many that interested I complete it.

_________________
Software developer and forum troll.
Please check out my software:
Excalibur, Basilisk 2, AmigaInputAnywhere.

@NutsAboutAmiga
A patch to solve the cannot-dismiss-yellow-alert problem would be great.

_________________
Author of the PortablE programming language.
I love using Amiga OS4.1 on my A1-X1000 & Sam440
Don't forget the official support forum for OS4!

@NutsAboutAmiga

As "yellow alert" you mean that ?

http://forum.hyperion-entertainment.biz/viewtopic.php?f=26&t=95&p=4758&hilit=alert#p4758

If so it is already reported internally as bug 6243 but i don't know (i don't test it yet) if it was fixed for the Update 5 .. it was reported long ago by the way

Last edited by samo79 on 18-Aug-2012 at 12:30 PM.

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

An official and integrated to the system "patch" would be welcome, not skippable alerts are very very annoying :-/

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

@Coder

Hi, Quote:

by Coder on 17-Aug-2012 23:21:02 Did anyone try it on a AmigaOne SE? It did not say it was supported but I hope it will work. Coder

Yes it works, it installed without any problems.

Draby