search for: atombios

...ork without tweaking. Add R500 unified shader register block. Fix R500_US_CONFIG. Add the R500 US index/data pair. Clarify R500 US setup. Alan Coopersmith (2): On non-gcc compilers, use C99's __func__ instead of gcc's __FUNCTION__ Strip ^M's from src/AtomBios/includes/ObjectID.h Alban Browaeys (1): RADEON: Revert to old behavior when resetting the memmap on VT switch Alex Deucher (167): RADEON: update man page with supported chips RADEON: fix DDC types 5 and 6 RADEON: restore clock gating and CP clock errata on VT switch...

...nel. [ 516.833580] amdgpu 0000:01:00.0: Refused to change power state, currently in D3 [ 516.912885] amdgpu 0000:01:00.0: Refused to change power state, currently in D3 [ 516.929175] amdgpu 0000:01:00.0: Refused to change power state, currently in D3 [ 521.932435] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 521.932440] [drm:amdgpu_atom_execute_table_locked] *ERROR* atombios stuck executing C392 (len 62, WS 0, PS 0) @ 0xC3AE [ 521.932442] [drm:amdgpu_atom_execute_table_locked] *ERROR* atombios stuck executing ADB8 (len 140, WS 0, PS 8) @ 0xADD3 [ 521.9...

[+cc LKML] On Tue, Sep 18, 2018 at 04:32:44PM -0500, Bjorn Helgaas wrote: > On Thu, Sep 13, 2018 at 11:37:45AM +0800, Daniel Drake wrote: > > On 38+ Intel-based Asus products, the nvidia GPU becomes unusable > > after S3 suspend/resume. The affected products include multiple > > generations of nvidia GPUs and Intel SoCs. After resume, nouveau logs > > many errors such

...--BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Subject: [ANNOUNCE] xf86-video-r128 6.8.0 To: xorg-announce at lists.freedesktop.org Dave Airlie (9): r128: fix bios size setting for pciaccess George Sapountzis (8): drop radeon, theatre (build system). drop radeon, theatre drop AtomBios and pcidb drop ati wrapper drop mach64 (build system) drop mach64 change module name and version add warning message git tag: xf86-video-r128-6.8.0 http://xorg.freedesktop.org/archive/individual/driver/xf86-video-r128-6.8.0.tar.bz2 MD5: 007bec0c6b07d9d3aeca4da18e561e...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Subject: [ANNOUNCE] xf86-video-mach64 6.8.0 To: xorg-announce at lists.freedesktop.org George Sapountzis (8): drop radeon, theatre (build system). drop radeon, theatre drop AtomBios and pcidb drop ati wrapper drop r128 (build system) drop r128 change module name and version add warning message Paulo Cesar Pereira de Andrade (1): Compile warning fixes. Yi Zhan (1): mach64: on IA64 systems the pciaccess page size mapping was getting E2...

...e the bios doesn’t show up on) to an HVM 32-bit Windows XP domU (I thought that would be the hard part, but it was easy with the Xen wiki). For the Linux domU, I cannot get the VGA passthrough to work. I started with essentially the same cfg file that worked for Windows. This lead to an “Expecting atombios for evergreen GPU” warning followed by “Fatal error during GPU init” in the Linux domU. I installed the AMD proprietary drivers and the warning and error went away. Both the virtual and physical VGA devices are listed by lspci in the Linux domU, but I cannot seem to use the physical device. I then...

http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=4d60422 also broken with this commit

...index bd6be77..ebbe8a1 100644 --- a/drivers/gpu/drm/amd/powerplay/smumgr/polaris10_smumgr.c +++ b/drivers/gpu/drm/amd/powerplay/smumgr/polaris10_smumgr.c @@ -44,7 +44,6 @@ #include "smu7_hwmgr.h" #include "hardwaremanager.h" -#include "ppatomctrl.h" #include "atombios.h" #include "pppcielanes.h" diff --git a/drivers/gpu/drm/amd/powerplay/smumgr/rv_smumgr.c b/drivers/gpu/drm/amd/powerplay/smumgr/rv_smumgr.c index b98ade6..cd9c9b9 100644 --- a/drivers/gpu/drm/amd/powerplay/smumgr/rv_smumgr.c +++ b/drivers/gpu/drm/amd/powerplay/smumgr/rv_smumgr.c...

..." [ 19.362] compiled for 1.9.0, module version = 1.1.0 [ 19.362] ABI class: X.Org Video Driver, version 8.0 [ 19.362] (II) fglrx(0): VESA BIOS detected [ 19.362] (II) fglrx(0): VESA VBE Version 3.0 [ 19.362] (II) fglrx(0): VESA VBE Total Mem: 16384 kB [ 19.362] (II) fglrx(0): VESA VBE OEM: ATI ATOMBIOS [ 19.362] (II) fglrx(0): VESA VBE OEM Software Rev: 11.22 [ 19.362] (II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc. [ 19.362] (II) fglrx(0): VESA VBE OEM Product: M96 [ 19.362] (II) fglrx(0): VESA VBE OEM Product Rev: 01.00 [ 19.390] (II) fglrx(0): ATI Video BIOS revision...

...BIOS Bootup Message: 113-MS8997-MS (II) RADEON(0): Framebuffer space used by Firmware (kb): 19 (II) RADEON(0): Start of VRAM area used by Firmware: 0x7ffb400 (II) RADEON(0): Framebuffer space used by Firmware (kb): 19 (II) RADEON(0): Start of VRAM area used by Firmware: 0x7ffb400 (II) RADEON(0): AtomBIOS requests 19kB of VRAM scratch space (II) RADEON(0): AtomBIOS VRAM scratch base: 0x7ffb400 (II) RADEON(0): Cannot get VRAM scratch space. Allocating in main memory instead (II) RADEON(0): Default Engine Clock: 390000 (II) RADEON(0): Default Memory Clock: 350000 (II) RADEON(0): Maximum Pixel ClockPLL...

...imary V_BIOS segment is: 0xc000 (II) Loading sub module "vbe" (II) LoadModule: "vbe" (II) Reloading /usr/lib/xorg/modules//libvbe.so (II) fglrx(0): VESA BIOS detected (II) fglrx(0): VESA VBE Version 3.0 (II) fglrx(0): VESA VBE Total Mem: 16384 kB (II) fglrx(0): VESA VBE OEM: ATI ATOMBIOS (II) fglrx(0): VESA VBE OEM Software Rev: 9.12 (II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc. (II) fglrx(0): VESA VBE OEM Product: M56P (II) fglrx(0): VESA VBE OEM Product Rev: 01.00 (II) fglrx(0): ATI Video BIOS revision 9 or later detected drmOpenDevice: node name is /d...

...size: 0x8c00 biosiomemstart: 0xf3060000 [ 1.777717] [drm] radeon_read_bios: succes [ 1.779057] [drm:radeon_get_bios], BIOS headerstart: 0x2077 bios length: 6|8 headerstring 0xc6 0x7c 0x0 0x0 [ 1.784874] [drm:radeon_get_bios], COMBIOS detected [ 1.786811] radeon 0000:00:05.0: Expecting atombios for evergreen GPU [ 1.788255] radeon 0000:00:05.0: Fatal error during GPU init [ 1.789919] [drm] radeon: finishing device. So the address that the radeon_read_bios function uses, also matches. So i''m pretty clueless how it ends up with the data from the cirrus rom when it''...

...0 00 00 00 00 00 00 00 01d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 51 mode(s) found VESA: v3.0, 16384k memory, flags:0x1, mode table:0xffffff8000261044 (99000044) VESA: ATI ATOMBIOS VESA: (C) 1988-2005, ATI Technologies Inc. RV610 01.00 io: <I/O> hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 cryptosoft0: <software crypto> on motherboard crypto: assign cryptosoft0 driver id 0, flags 100663296 crypto: cryptosoft0 registers alg 1 flags 0 maxoplen 0 crypto:...