@kas1e
Quote:
When you have found hardware conflict, it need reporting and fixing of course ! But someting make me think that you just on very old RadoenHD lite version, which need to be replaced on latest Radoen HD Lite, or on normal full RadeonHD driver, and there will be no conflict.
No way man, if I was still using the Lite driver I'd be stuck on 1024x768 with no hardware acceleration. I couldn't hack that! But with no compositing it would actually work better!
In fact, it wouldn't even boot. The OS4 OEM driver on CD doesn't even support an R7 250. I don't know what it supports up to as I can find no clear list nor see any models listed in the binary.
I've got the full RadeonHD from Enhancer 1.5 Plus.
Quote:
As you have it now, you can't expect that most software will works ok for you and devs should know that when you report any bugs about anything that your system is combain of all sort of different components from different updates .
Though it needs a crash I find a crash log is the best way to list all versions. Since it logs all module versions in system which is convenient. Be good if a tool existed that could give the same list without needing to crash and save a log.
Quote:
Was it reported anywhere ?
Yes. On the amiga.org MantisBT September last year. Report #803.
Quote:
Did you create already boot iso with latest RadeonHD lite , or with just latest RadeonHD driver ?
With full RadeonHD driver yes but it was before Update 2. So it actually works! I haven't yet patched an Update 2 boot CD together yet and it's pain we can't boot from USB.
I created test volumes on my HDD with fresh install and updates with the latest RadeonHD at the time. All froze on WB. My beta volume is worse as disabling interrupts and compositing doesn't fully fix it. So when AmiUpdate runs it stalls the system. For some reason AmiUpdate is good at killing the system this way.
It's related to interrupts and compositing. Disabling them lets the system boot but it's still not fully stable. There is no crash on serial. So it's hard to tell what is going on. The last thing on serial at boot is changing the pointer sprite and then the system freezes. But, according to a serial logger active tick tool, the system is still alive with the user interface frozen.