Who's Online |
75 user(s) are online ( 35 user(s) are browsing Forums)
Members: 0
Guests: 75
more...
|
|
|
|
|
Re: Trying to update my A1XEG4 to OS4.1 FE
|
Posted on: 2021/5/14 16:31
#21
|
Just popping in 
|
@RinceWynd
Booting off the onboard VIA IDE controller is a safe bet in case the 0680 fails.
I remember having trouble with booting off a DVD drive on the 0680 controller, not sure why.
Make sure the VIA controller uses PIO instead of DMA transfers which I think is the default setting on the 4.1FE CD\DVD.
|
|
|
|
|
|
Re: ACube/AEon - more info about PCIe cards in SAM440, please
|
Posted on: 2021/4/15 16:03
#22
|
Just popping in
|
@geennaam Quote: This adapter is based on the Pericom PI7C9X111SL. It offers a ... transparent bridge Can this Transparent mode be set by the user? Transparent mode as in that the bridge chip is undetectable by the system? so that it would not show up if you use the "pci 0" or "pci 1" commands to scan for it in uboot? That would be rather excellent, as the AmigaOne XE has difficulties working with nested PCI devices. e.g. invalid interupts in 33mhz slots and nothing showing up in the 66mhz slot.
|
|
|
|
|
|
Re: New Sam460cr boards will hit the road soon!
|
Posted on: 2021/4/10 17:04
#23
|
Just popping in
|
|
|
|
|
|
|
Re: New Sam460cr boards will hit the road soon!
|
Posted on: 2021/4/9 16:20
#24
|
Just popping in
|
@Spectre660 Ditto The Yeston card is great, runs fairly cool, quiet too and comes with both a full height and low profile brackets. That Amazon listing seems quite pricey though, I've purchased my 4GB variant on ebay for 115 Euro some weeks ago from this seller.Prices seem to have risen but you can still find them there for about 130 Euro, make sure you don't accidentally get a 2GB variant as they tend to be only 5 bucks cheaper than the 4GB ones.
|
|
|
|
|
|
Re: Trying to get a Radeon RX 460 working in an AmigaOne XE
|
Posted on: 2020/4/7 13:23
#25
|
Just popping in
|
@nbache @Hans Uboot gives the option to change the IRQ number (7/9/10/11/13/Auto) and IRQ detection of PCI slots to "level" or "edge" I can change the IRQ detection from slot A to slot D, not sure which is which as they aren't marked on the PCB or in the PDF manuel. Here's a shot from the 7750 thread, where AmigaOS calls them interrupt A through D instead.  I tried to change detection from level to edge of one slot at a time and made sure to reboot after changing detection methode. Setting any to Edge won't avoid the system getting stuck during the OS4 splash screen with "RadeonRX (5): RadeonRX (5): Cannot print bridge configuration for PCI:0.7,0, because it is not a bridge device." continuously being printed to the terminal. Trying to boot straight from the RX460 will still fail after loading the kickstart files with normal and debug drivers. changing IRQ number doesn't seem to change anything. Quote: Better leave interrupts disabled for now... Good to hear, I somehow made myself under the impression that IRQ was required for it to work, could you tell me what the disadvantage is of having interrupts disabled if you would mind? Also does it matter for the driver that uboot has it's PCI/AGP bootcard option backwards? booting from AGP option will boot with the PCI card and vice versa. Sorry to suddenly leave you both hanging, have been ill. (no corona)
|
|
|
|
|
|
Re: Trying to get a Radeon RX 460 working in an AmigaOne XE
|
Posted on: 2020/3/31 9:17
#26
|
Just popping in
|
@Hans Quote: That's a UBoot bug. It should set the Polaris11's line, pin & number to match whatever the values for that slot are.
When I first started working on the RadeonHD.chip driver, I hard-coded the IRQ line into the driver for the slot I put it in. I cannot do that in a production driver, because those values vary by motherboard, & the driver doesn't know which slot you put the card in.
oh wow I understand that hardcoding IRQ's should not be done for a production driver, but maybe there could be a way for the end user to set IRQ? Perhaps via an user created .txt file in the kickstart folder as an unsupported "as is - backdoor" kind of method?
|
|
|
|
|
|
Re: Trying to get a Radeon RX 460 working in an AmigaOne XE
|
Posted on: 2020/3/30 23:53
#27
|
Just popping in
|
@Hans *crosses fingers* Tried swapping around the sil0680 ide controller and got the following interrupt lines from the 33mhz slots Upperslot: Line: 0x09 Pin: A Number: 25 (Previously PEX) Middleslot: Line: 0x0B Pin: A Number: 27 Bottomslot: Line: 0x0A Pin: A Number: 26 The PEX8111 bridge chip got the same interrupt in every slot, PEX8111: Line: 0x00 Pin: A Number: 16 Polaris11: Line: 0xFF Pin: A Number: 271 Also got serial output working from OS4, and you're right about "RadeonRX (5): RadeonRX (5): Cannot print bridge configuration for PCI:0.7,0, because it is not a bridge" being an infinite loop, as it gets continuously printed when it gets stuck on the OS4 splash screen when booting with the 9250 and the Polaris driver included in the kicklayout file. Some most likely inane findings Trying to enable the PCIGraphics monitor when skipping the startup-sequence does start the RadeonRX driver and but doesn't go further than the following Quote: RadeonRX (5): RadeonRX graphics.library AltiVec/VMX enabled
graphics.library PPC74xx optimizations enabled
RadeonRX (5): findRXCard called
RadeonRX (5): Card 0 (0): 0x1002, 0x5960, unknown, other driver, active
RadeonRX (5): Calling original FindCard()
RadeonRX (5): Found a graphics card
RadeonRX (5): initRXCard called
RadeonRX (5): Calling original InitCard() System also is about to collapse as drawers and programs don't respond anymore. The driver also prints this when trying to boot straight from the Polaris card in uboot and then halts after loading the kickstart files, it's also the only thing OS4 prints to the serial terminal. Also discovered that the PEX card and the RX460 only get IO and MEM if the 460 is used as the uboot display card and the driver excluded from the kicklayout. booting with the 9250 as the uboot display card removes them, even though the driver is also excluded. @LiveForIt Does seem like some of the files are depended on others loading first. booting with the following order makes it fail much sooner when loading RadeonRX.chip MODULE Kickstart/kernel.debug MODULE Kickstart/newlib.library.kmod MODULE Kickstart/intuition.library.kmod MODULE Kickstart/RadeonRX.chip.debug MODULE Kickstart/ATIRadeon.chip MODULE Kickstart/PCIGraphics.card Still, strange though that the normal versions of the kernel and RadeonRX driver just work together as is but not the debug versions. I have multiple configurations inside my kicklayout file and have it backed up on a usb stick, so I can mess around with it as much as I want. should anyone have a idea on how it should be ordered let me know.
Edited by Helloworld on 2020/3/31 0:14:40
Edited by Helloworld on 2020/3/31 0:21:46
|
|
|
|
|
|
Re: Trying to get a Radeon RX 460 working in an AmigaOne XE
|
Posted on: 2020/3/29 23:23
#28
|
Just popping in
|
@LiveForIt I gave that a go by putting newlib on the top of the layout, before RadeonRX.chip.debug. Now it fails loading the intuition library, trying to put intuition.library.kmod before newlib or right after it will make it fail loading the graphics.library.kmod instead. I don't think shuffling kickstart files around would help anymore, as it seems it always fails loading halfway the layout. I really ought to make that serial thread at Hyperion now. Thanks for the suggestion Quote:LABEL Yikes
; Exec name
EXEC Kickstart/loader
;
; PPC native modules
;
MODULE Kickstart/intuition.library.kmod
MODULE Kickstart/newlib.library.kmod
MODULE Kickstart/RadeonRX.chip.debug
MODULE Kickstart/ATIRadeon.chip
MODULE Kickstart/PCIGraphics.card
;MODULE Kickstart/petunia.library.kmod
MODULE Kickstart/kernel.debug
;MODULE Kickstart/FastFileSystem
MODULE Kickstart/SmartFilesystem
;MODULE Kickstart/JXFileSystem
;MODULE Kickstart/a1floppy.device.kmod
MODULE Kickstart/a1ide.device.kmod
MODULE Kickstart/battclock.resource.kmod
MODULE Kickstart/biosversion.resource.kmod
MODULE Kickstart/bootmenu.kmod
MODULE Kickstart/bootimage
MODULE Kickstart/CDFileSystem
MODULE Kickstart/con-handler.kmod
MODULE Kickstart/console.device.kmod
MODULE Kickstart/diskboot.kmod
MODULE Kickstart/diskboot.config
MODULE Kickstart/diskcache.library.kmod
MODULE Kickstart/dos.library.kmod
MODULE Kickstart/elf.library.kmod
MODULE Kickstart/env-handler.kmod
MODULE Kickstart/FileSystem.resource.kmod
MODULE Kickstart/gadtools.library.kmod
;MODULE Kickstart/gameport.device.kmod
MODULE Kickstart/graphics.library.kmod
MODULE Kickstart/hunk.library.kmod
MODULE Kickstart/input.device.kmod
;MODULE Kickstart/it8212ide.device.kmod
MODULE Kickstart/keyboard.device.kmod
MODULE Kickstart/keymap.library.kmod
;MODULE Kickstart/lsi53c8xx.device.kmod
MODULE Kickstart/mounter.library
MODULE Kickstart/nonvolatile.library.kmod
MODULE Kickstart/nvram.resource.kmod
MODULE Kickstart/ps2.resource.kmod
MODULE Kickstart/ram-handler.kmod
MODULE Kickstart/ramdrive.device.kmod
MODULE Kickstart/ramlib.kmod
MODULE Kickstart/shell.kmod
MODULE Kickstart/sii0680ide.device.kmod
;MODULE Kickstart/sii3112ide.device.kmod
;MODULE Kickstart/sii3114ide.device.kmod
;MODULE Kickstart/sii3512ide.device.kmod
MODULE Kickstart/strap.kmod
MODULE Kickstart/timer.device.kmod
;MODULE Kickstart/3dfxVoodoo.chip
;MODULE Kickstart/3DLabsPermedia2.chip
;MODULE Kickstart/usbresource.library
;MODULE Kickstart/usbsys.device
;MODULE Kickstart/uhci.usbhcd
;MODULE Kickstart/ehci.usbhcd
;MODULE Kickstart/hub.usbfd
MODULE Kickstart/bootmouse.usbfd
MODULE Kickstart/bootkeyboard.usbfd
;MODULE Kickstart/massstorage.usbfd
;MODULE Kickstart/ohci.usbhcd
;MODULE Kickstart/RadeonHD.chip
|
|
|
|
|
|
Re: Trying to get a Radeon RX 460 working in an AmigaOne XE
|
Posted on: 2020/3/28 21:35
#29
|
Just popping in
|
@Hans The serial cable arrived, still need to figure out how to log debugging info from AmigaOS. Been following this wiki page and so far I've been only able to log system configuration information and nothing while loading the kickstart files.  I guess it's because uboot has its serial baudrate at 115200, but AmigaOS' serial settings don't allow baudrate to go higher than 31250 Also using both "Serial" and "Munge" together in the commandline causes the system to crash.. off to the Hyperion forums... I tried to use the RadeonRX.chip.debug driver with the debug kernel, but when I put both in the kickstart layout it causes uboot to fail loading the newlib library, which I cannot comment out, so it's either Radeon.chip.debug or kernel.debug. I gave a shot capturing the debug buffer with RadeonRX.chip.debug alone with the startup-sequence skipped. The RadeonRX.chip.debug will also remove MEM and IO from the Pex chip and disconnects the Polaris card. The debugbuffer isn't much different when booting the first time Quote: RadeonRX (2): Could not identify the chipset
RadeonRX (2): Identified the chipset as: POLARIS11
RadeonRX (2): Graphics card name is: Radeon RX Polaris11
RadeonRX (2): If - and only if - your card does not work or does not work optimally
please submit a bug report at:
http://www.spam.com/bugreports
Remember to include the driver version, and the following card details:
0x67EF:0x174B:0xE348: <name of board>
and *please* describe the problems you are seeing in detail.
graphics.library AltiVec/VMX enabled
graphics.library PPC74xx optimizations enabled
RadeonRX (5): findRXCard called
RadeonRX (5): Card 0 (0): 0x1002, 0x5960, unknown, other driver, active
RadeonRX (5): Calling original FindCard()
RadeonRX (5): Found a graphics card
RadeonRX (5): initRXCard called
RadeonRX (5): Calling original InitCard()
0000: 00 FF FF FF FF FF FF 00 22 F0 22 30 01 01 01 01 ........"."0....
0010: 23 17 01 03 80 26 1E 78 2E FD 25 A2 58 4F 9F 26 #....&.x..%.XO.&
0020: 0D 50 54 A1 08 10 81 80 01 01 01 01 01 01 01 01 .PT.............
0030: 01 01 01 01 01 01 30 2A 00 98 51 00 2A 40 30 70 ......0*..Q.*@0p
0040: 13 00 78 2D 11 00 00 1E 00 00 00 FD 00 32 4C 18 ..x-.........2L.
0050: 53 11 00 0A 20 20 20 20 20 20 00 00 00 FC 00 48 S..............H
0060: 50 20 4C 41 31 39 35 36 78 0A 20 20 00 00 00 FF P.LA1956x.......
0070: 00 33 43 51 33 33 35 31 4A 43 48 0A 20 20 00 CF .3CQ3351JCH.....
0080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ The RX driver seems to find the 9250? It finds card 0, 0x5960 is the Radeon 9250, it also prints a hex table, with "HP.LA1956x" which is the monitor the 9250 is connected to. The 460 is connected to a BenQ 17-TZ1 1280x1024 lcd monitor via DVI. Doing a softreset gives alot more information Quote: [RAM] Handler has started successfully. [DebugLevel=7]
RadeonRX (5): findRXCard called
RadeonRX (5): Card 1 (2): 0x1002, 0x67EF, Radeon RX Polaris11, supported, inactive
RadeonRX (5): Found supported card
RadeonRX (5): initRXCard called
RadeonRX (5): Initializing card
RadeonRX (2): Obtaining ITimer interface
RadeonRX (2): Got ITimer interface
RadeonRX (2): Returning from LibOpen().
RadeonRX (0): RadeonRX.chip 1.11 (14.8.2018)
RadeonRX (6): <rxOpen>
RadeonRX (4): Have altivec.
RadeonRX (4): PCI device is a graphics card.
RadeonRX (2): Identified the chipset as: POLARIS11
RadeonRX (2): Graphics card name is: Radeon RX Polaris11
RadeonRX (2): If - and only if - your card does not work or does not work optimally
please submit a bug report at:
http://www.spam.com/bugreports
Remember to include the driver version, and the following card details:
0x67EF:0x174B:0xE348: <name of board>
and *please* describe the problems you are seeing in detail.
RadeonRX (5): RadeonRX (5): PCI_DEVICE_ID: 0x8111
RadeonRX (5): RadeonRX (5): PCI_VENDOR_ID: 0x10B5
RadeonRX (5): RadeonRX (5): PCI_STATUS: RadeonRX (5): ECP enable, RadeonRX (5): 66 MHz capable, RadeonRX
(5): RadeonRX (5): RadeonRX (5): DEVSEL# timing 1, RadeonRX (5): RadeonRX (5): RadeonRX (5): RadeonRX (5):
RadeonRX (5): RadeonRX (5):
RadeonRX (5): RadeonRX (5): PCI_COMMAND: RadeonRX (5): RadeonRX (5): RadeonRX (5): Bus master enabled,
RadeonRX (5): RadeonRX (5): RadeonRX (5): RadeonRX (5): RadeonRX (5): RadeonRX (5): RadeonRX (5): RadeonRX
(5):
RadeonRX (5): RadeonRX (5): PCI_CLASS: 0x60400
RadeonRX (5): RadeonRX (5): PCI_REVISION_ID: 0x21
RadeonRX (5): RadeonRX (5): PCI_HEADER_TYPE: 0x1
RadeonRX (5): RadeonRX (5): PCI_LATENCY_TIMER: 32
RadeonRX (5): RadeonRX (5): PCI_CACHE_LINE_SIZE: 8
RadeonRX (5): RadeonRX (5): PCI_SEC_LATENCY_TIMER: 0
RadeonRX (5): RadeonRX (5): PCI_PRIMARY_BUS: 0
RadeonRX (5): RadeonRX (5): PCI_SECONDARY_BUS: 2
RadeonRX (5): RadeonRX (5): PCI_SUBORDINATE_BUS: 2
RadeonRX (5): RadeonRX (5): PCI_SEC_STATUS: RadeonRX (5): RadeonRX (5): RadeonRX (5): RadeonRX (5): RadeonRX
(5): DEVSEL# timing 0, RadeonRX (5): RadeonRX (5): RadeonRX (5): Received master abort, RadeonRX (5):
RadeonRX (5): RadeonRX (5):
RadeonRX (5): RadeonRX (5): PCI_IO_BASE (full): 0x3000
RadeonRX (5): RadeonRX (5): PCI_IO_LIMIT (full): 0x3FFF
RadeonRX (5): RadeonRX (5): PCI_MEMORY_BASE (full): 0xB0200000
RadeonRX (5): RadeonRX (5): PCI_MEMORY_LIMIT (full): 0xB02FFFFF
RadeonRX (5): RadeonRX (5): PCI_PREF(ETCH)_MEMORY_BASE (full): 0xA0000000
RadeonRX (5): RadeonRX (5): PCI_PREF(ETCH)_MEMORY_LIMIT (full): 0xB01FFFFF
RadeonRX (5): RadeonRX (5): PCI_BRIDGE_CONTROL: RadeonRX (5): RadeonRX (5): RadeonRX (5): RadeonRX (5): VGA
enable, RadeonRX (5): RadeonRX (5): RadeonRX (5): RadeonRX (5): RadeonRX (5): RadeonRX (5): RadeonRX (5):
RadeonRX (5):
RadeonRX (5): RadeonRX (5): PCI_INTERRUPT_PIN: 0x1
RadeonRX (4): Enabling blind prefetch on the PEX 8111 bridge
RadeonRX (5): RadeonRX (5): Cannot print bridge configuration for PCI:0.7,0, because it is not a bridge
device.
RadeonRX (5): RadeonRX (5): Cannot print bridge configuration for PCI:0.7,0, because it is not a bridge
device.
RadeonRX (5): RadeonRX (5): Cannot print bridge configuration for PCI:0.7,0, because it is not a bridge
device.
RadeonRX (5): RadeonRX (5): Cannot print bridge configuration for PCI:0.7,0, because it is not a bridge
device. PCI_INTERRUPT_PIN: 0X1 instead of 0xFF? The PEX8111's interrupt pin is 0x00 and the 9250's interrupt pin is 0x0A It then proceeds to print "RadeonRX (5): RadeonRX (5): Cannot print bridge configuration for PCI:0.7,0, because it is not a bridge" a couple hundred times it seems and suddenly ends. Enabling the Radeon and PCIGraphics monitors won't affect the debug buffer Here is the entire log if you need it https://pastebin.com/XNw52e9u
|
|
|
|
|
|
Re: Trying to get a Radeon RX 460 working in an AmigaOne XE
|
Posted on: 2020/3/26 20:16
#30
|
Just popping in
|
@Hans Quote: Looks like you have the driver starting up. So, can you see the RX 460's screen modes in ScreenMode prefs? Have you tried using them? Sorry, should have been more clear about it. There are no screenmodes for the Polaris card as it does not get initialized and stays idle with a blinking cursor. The Ranger shot is with the driver commented out of the kickstart layout, in which case I can boot with the 460 as the main card in uboot and it will switch to the 9250 after the kickstart files are loaded. with the RadeonRX.chip included in the kickstart layout then the RX460 will get disconnected and the pex chip will lose "IO" and "MEM" in Ranger. Trying to boot with the RX460 as the main display in uboot with the RadeonRX.chip seems to result in a instant crash after the kickstart files are loaded, all drive activity immediately stops and the caps, num and scroll lock keys don't respond on the the ps/2 keyboard. The Dumpdebugbuffer shot is captured with the 9250 and RadeonRX.chip but with the startup-sequence skipped as the 460 does not get initialized. the OS gets stuck in a inifinite loop at the OS4 splash screen after the kickstart files are loaded. (no crash, can still soft and hard reboot and go into the early start menu with the 9250) The system has two monitors, "Radeon" and PCIGraphics both with interrupts unchecked. Seems like it has the same dead ends as with the 7750 card last time, which is why I thought it would be a good idea to log what uboot is doing although I probably should have asked how to do that first on the Hyperion forums.  Ordered a serial cable which should arrive in a few days.
Edited by Helloworld on 2020/3/27 5:06:00
Edited by Helloworld on 2020/3/27 5:10:36
Edited by Helloworld on 2020/3/27 5:17:41
|
|
|
|
|
|
Trying to get a Radeon RX 460 working in an AmigaOne XE
|
Posted on: 2020/3/25 21:06
#31
|
Just popping in
|
BACK WITH A VENGEANCE    SO CLOSE I CAN ALMOST TASTE IT Without the driver inside the kicklayout , the PEX8111 chip and RX460 has all of the required (i think) 'commands' in order to be used, but the Pex chip loses IO and MEM and the Radeon gets disconnected when I put the RadeonRX.chip in the kickstart layout. Also the RX.chip needs to put at the top of the layout otherwise uboot gives an error when loading the file, it also can't seem to co-exist with Petunia and USB so they have to be commented out. Not that I expect anything out of it, but is there a way to get debugging info from uboot with a serial cable? Fully aware that I'm digging myself a deeper hole here.
Edited by Helloworld on 2020/3/25 21:22:37
Edited by Helloworld on 2020/3/25 21:35:22
|
|
|
|
|
|
Re: Odyssey's MediaPlayer thread
|
Posted on: 2020/3/25 18:52
#32
|
Just popping in
|
@kas1e Quote: Yeah, for me that c-media card works evetywhere else fine, that why i think at first it's mediaplayer bug. But maybe mediaplayer just first app which use ahi in some way in which other ahi-based apps not. Hope to check today with sblive Are you using a 'legacy parallel' PCI sound card? I recall an thread about ethernet cards for the X5000 where someone said that the bottom two PCI slots don't support DMA transfers (can someone confirm this?) and that it was actually faster and less CPU intensive to use a PCI Express card even though it uses the exact same PCI chip connected to a PCI to PCI Express bridge. There are PCI-E soundcards based on the CMI8738 if the Soundblaster Live! doesn't work out for you. btw thanks for the updates :)
|
|
|
|
|
|
Re: OpenClaw
|
Posted on: 2019/7/3 22:13
#33
|
Just popping in
|
We're off to a good start Captain Claw already has an official AmigaOS appearance in Shogo M.A.D 
|
|
|
|
|
|
Re: Maximum memory X1000
|
Posted on: 2019/6/17 14:08
#34
|
Just popping in
|
@Raziel Quote: There shouldn't be the need to recompile every program to make use of bank switching.
It should be handled by ExecSG, or any other program, in the background, on the fly. Do you mean that all of the existing OS4 software should dynamically be mapped above the 2GB barrier by the OS? I'm not very technical, but doesn't this mean that those OS4 programs out of the currently used banks would suddenly freeze or not able to multitask alongside other programs without warning? If so then I personally would not like to be implemented this way, seems inconvenient to me. Unless Exec would also constantly switch banks to allow for multitasking but I think that would have quite a performance penalty. I rather have the normal programs reside in the 2GB barrier and have ExtMem support hardwired in certain programs e.g. web browsers having tabs in different banks or video editors. Of course I wouldn't mind if this dynamic way of storing programs in different banks is optional for the user.
|
|
|
|
|
|
Re: 2019 AmigaOS 4.x Graphics Card Survey
|
Posted on: 2019/6/9 0:57
#35
|
Just popping in
|
@Daytona675x 
|
|
|
|
|
|
Re: 2019 AmigaOS 4.x Graphics Card Survey
|
Posted on: 2019/6/9 0:34
#36
|
Just popping in
|
@Hans A1222 plays a huge part in that, but I think that the problem also lies with Hyperion's silence which may helped to avoid flamewars early on but now it's alienating users due to stagnation. The OS4 scene isn't active enough to entice newcomers, even with what A-eon is doing.
To keep the ball rolling, Hyperion needs to give progress reports, update their blog again.
That is, if Hyperion is even making enough progress to allow for that.
Sounds like they really have issues with writing drivers for onboard i/o
Should A-EON ever make a new motherboard for some reason (upgrade to e6500 perhaps)
then they should consider to include a Pci Express to Pci bridge on the motherboard, connect a Pci hub chip to it
and add a Sil3114 Sata controller, a RTL8169S Ethernet controller and a NEC/Renesans D720101F1 USB 2.0 controller to that.
Something like this, but integrated on the motherboard with ethernet instead of firewire.
https://www.ebay.nl/itm/Gamme-Pro-Cart ... 8b75fd:g:2E0AAOSwa~BYSXzM
Drastic measure since the PPC SOC's already have those intergrated, but we have working and mature drivers for those controllers
and this could shave off years time to port OS4 to a new platform to a state that it is acceptable for end users.
Of course this isn't a possibility for the A1222, but should the X5000 had this then maybe the OS4 team could have gone quicker to the A1222.
Sorry for my off-rails, unproductive Amigaworld.net style ramble. Won't do that again.  (anyway to hide text behind a spoiler button here?)
|
|
|
|
|
|
Re: 2019 AmigaOS 4.x Graphics Card Survey
|
Posted on: 2019/5/17 20:41
#37
|
Just popping in
|
@trixie
I'm so funny I should win an oscar.
@Hans
Wow, from over 400 to under 300.
Did the UAE guys lost interests?
|
|
|
|
|
|
Re: 2019 AmigaOS 4.x Graphics Card Survey
|
Posted on: 2019/5/16 19:11
#38
|
Just popping in
|
I bet Hans and Daniel are still using AGA
|
|
|
|
|
|
Re: AmigaOne G3-SE safe overclock @667MHz
|
Posted on: 2019/3/16 19:45
#39
|
Just popping in
|
@monomango I didn't know you could overclock the SE, pretty cool! Quake 3 suddenly crashing unfortunately seems to normal, I've tried numerous source ports and all would randomly crash on my stock 800mhz 7451 and it still crashes on my 1066mhz 7457, with a lovely continuous buzz sound coming out of the speakers :) Btw, the smoke trail of the rocket launcher really kills performance on my 9250, I recommand to go to the console and type cg_noProjectileTrail 0 to disable it, makes it so much faster and clearer too! r_ext_compressed_textures 1 Also gains some FPS, but the textures will look very low res. Here's a list of all Q3 console commands
|
|
|
|
|
|
Re: Trying to get a Radeon HD 7750 working in an AmigaOne XE
|
Posted on: 2019/3/16 18:52
#40
|
Just popping in
|
@monomango Hans was kind enough to send me a special driver which initialized the card when kickstart was loaded but it gave an out of range signal Quote: RadeonHD (0): ERROR: AtomBIOS is stuck in a loop for more than 5 seconds. Aborting
RadeonHD (0): ERROR: AtomBIOS stuck executing C7E5 (len 321, WS 0, PS 4) @ 0x0072. Aborting.
RadeonHD.chip (0): ParseTable said: CD_INFINITE_LOOP_ENCOUNTERED
RadeonHD.chip (0): rhdOpen: AsicInit failed. Won't be able to obtain VRAM FB scratch space We've hit a roadblock so as a last ditch effort I (on my own initiative) tried to reflash the bios and killed my 7750. As others have posted, cards before the 7000 series probably work but without Nova support I'm not motivated to try. The 7750 wouldn't display anything in the 66mhz slot. uboot cannot see anything behind a PCI bridge chip in the 66mhz slot, so the pex chip actually gets detected in uboot. (with the AGP card installed, I can't remember why you couldn't use both slots) My 128bit 256MB 9250 has the same problem with only 128MB being used, but as a 32bit 1600x1200 user I personally never came close to running out of VRAM. (Oddessy with 10 tabs takes 80MB, 47MB left) Althrough I think that my card now only has a 64bit memorybus because of it?
|
|
|
|
|
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
