A-EON: Enhancer Software 1.2 Released

[Hans_]

@duga

So A-EON rather than Hans, good to know. Serial terminal; should be possible. Which debug level should I set as a start?

The debug level is for the kernel not the RadeonHD driver. If you're convinced that there's a RadeonHD driver bug (or any Enhancer CD software), then please submit a bug report via A-EON's bug tracker.

That said, I'm not convinced that it's the graphics driver...

http://www.sapphiretech.com/productd...7B15F&lang=eng R7 240 4G D3. Lock up in Workbench at first disk activity, for example starting app from Amidock or clicking on drive icon. As long as there´s no disc activity (after loading Workbench and WBstartup programs) there´s no lockup.

If it's related to disk activity, then it could be a problem elsewhere. You're lucky your Sam440ep-Flex even boots with the Oland card because I've heard that the old Sams just don't like Southern Islands cards (a Uboot issue most likely).

Things to check:
- Which PCI-to-PCIe bridge card are you using (they're not all created equal)? Ask other Sam440ep owners what they used
- Which PCI port do you have it plugged into? The 66 MHz one? Or one of the other ones?

The difference between HDMI and VGA is that with VGA a Intution screen says "Cannot create screen mode for Radeon HD Oland" and I get a screen in probably 320x200 instead of 1920x1080.

That sounds like the DDC channel isn't working over VGA, so it can't find out what modes the monitor supports. Setting the modes manually in ScreenMode prefs will solve this, but you're better off using DVI.

Hans

[Hans_]

Thanks. Seems the card is correctly discovered as OLAND, but not fully:

RadeonHD.card (0): RadeonHD.chip 1.20 (25.10.2016)
RadeonHD (2): Graphics card name is: Radeon HD OLAND
RadeonHD (2): Identified the chipset as: OLAND

RadeonHD.chip (0): Cannot load MC microcode for this chipset
RadeonHD.chip (0): Cannot set up default voltages and clocks because the MC microcode hasn't been loaded

I have registered at Amigadeveloper.com, waiting for account verfication.

My Radeon R7 240 does the same thing and works fine (in an A1-X1000).

IIRC, MC microcode isn't needed for cards with DDR3. With GDDR5 cards, the card gets started at low speed (~150 MHz) and needs the MC microcode before they can run at their rated speed. Oland cards are already set to run at their rated speed from the get-go, so the MC microcode doesn't matter.

Hans

[Hans_]

Does your card too have 4 GB 128-bit memory? Have you seen the link to my card's specifications?

No, it has 2 GB. However, that difference shouldn't matter.

If my Radeon HD R7 card "should" work it might have something to do with DMA and disk activity.

Are you using the onboard Sata-II? If so, have you set it up correctly in UBoot? Also, what graphics card were you using on this machine before switching to the R7 240?

You write: "Oland cards are already set to run at their rated speed from the get-go, so the MC microcode doesn't matter.". But this card has 730 MHz Engine Clock and 780 MHz Boost Engine Clock. Or are you only talking about the memory speed? That is "1600 MHz, 1800 MHz effective". But maybe that's only marketing talk?

I'm talking about both clocks. My card's clocks are set to 780 MHz and 900 MHz (which gives 1800 MT/s with DDR3 RAM).

Edit: Managed to catch a crash for the first time: RadeonHD.chip (0): wait for 8 fifo entries failed (0 available).

Usually I don't get anything on the serial port when freeze occurs (debug level 3).

That sounds like your GPU is locking up. Are you able to capture a log with the debug version of the Radeon HD driver (once again, the kernel debug level is irrelevant)? If so, submit that as part of your bug report to amigadeveloper.com.

Hans

[Hans_]

Still waiting for the Mantis bugtracker account.

In the meantime:
RadeonHD.chip (2): The detected amount of video RAM is 4294967296
RadeonHD.chip (2): The detected amount of video RAM exceeds the PCI BAR aperture for video RAM.
RadeonHD.chip (2): Only 268435456 of the total 0 is accessible by the CPU.
RadeonHD.chip (5): Framebuffer space used by Firmware (kb): 0
RadeonHD.chip (5): rhdAtomGetFbBaseAndSize: AtomBIOS specified VRAM scratch space size invalid
RadeonHD.chip (5): AtomBIOS scratch space size not specified; default to: 20480
RadeonHD.chip (1): Cannot get VRAM scratch space. Allocating in main memory instead

Is that a problem?

Shouldn't be. There's clearly a bug in the debug output, but the driver should be able to handle >= 4GB VRAM.

Hans

[Hans_]

Still waiting for a functional bugreport account. Still cannot use my Oland driver.

Have you tried using the "lost your password" link?

Hans