[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: DRM/DRI accelerated (3D) graphics?



Dear Émeric et al,

Unfortunately, I still hadn't had time yet to reinstall Debian yet.
In the meantime, could you perhaps publish screenshots?

Also, besides the FireGL X1, what are the chances for the HD5450?



Kind regards,

Marco


On 19-9-2011 20:22, Émeric Maschino wrote:
That's great news!

If it can help further, here's how framebuffer is configured in Debian
-mckinley kernels:
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
CONFIG_FB_DDC=m
# CONFIG_FB_BOOT_VESA_SUPPORT is not set
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
CONFIG_FB_SYS_FILLRECT=m
CONFIG_FB_SYS_COPYAREA=m
CONFIG_FB_SYS_IMAGEBLIT=m
# CONFIG_FB_FOREIGN_ENDIAN is not set
CONFIG_FB_SYS_FOPS=m
# CONFIG_FB_WMT_GE_ROPS is not set
CONFIG_FB_DEFERRED_IO=y
CONFIG_FB_SVGALIB=m
# CONFIG_FB_MACMODES is not set
CONFIG_FB_BACKLIGHT=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y

#
# Frame buffer hardware drivers
#
CONFIG_FB_CIRRUS=m
CONFIG_FB_PM2=m
# CONFIG_FB_PM2_FIFO_DISCONNECT is not set
CONFIG_FB_CYBER2000=m
CONFIG_FB_ASILIANT=y
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_UVESA is not set
CONFIG_FB_S1D13XXX=m
CONFIG_FB_NVIDIA=m
CONFIG_FB_NVIDIA_I2C=y
# CONFIG_FB_NVIDIA_DEBUG is not set
CONFIG_FB_NVIDIA_BACKLIGHT=y
# CONFIG_FB_RIVA is not set
CONFIG_FB_MATROX=m
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_FB_MATROX_MYSTIQUE=y
CONFIG_FB_MATROX_G=y
CONFIG_FB_MATROX_I2C=m
CONFIG_FB_MATROX_MAVEN=m
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y
# CONFIG_FB_RADEON_DEBUG is not set
CONFIG_FB_ATY128=m
CONFIG_FB_ATY128_BACKLIGHT=y
CONFIG_FB_ATY=m
CONFIG_FB_ATY_CT=y
CONFIG_FB_ATY_GENERIC_LCD=y
CONFIG_FB_ATY_GX=y
CONFIG_FB_ATY_BACKLIGHT=y
CONFIG_FB_S3=m
CONFIG_FB_SAVAGE=m
CONFIG_FB_SAVAGE_I2C=y
# CONFIG_FB_SAVAGE_ACCEL is not set
CONFIG_FB_SIS=m
CONFIG_FB_SIS_300=y
CONFIG_FB_SIS_315=y
CONFIG_FB_NEOMAGIC=m
CONFIG_FB_KYRO=m
CONFIG_FB_3DFX=m
# CONFIG_FB_3DFX_ACCEL is not set
CONFIG_FB_3DFX_I2C=y
CONFIG_FB_VOODOO1=m
CONFIG_FB_VT8623=m
CONFIG_FB_TRIDENT=m
CONFIG_FB_ARK=m
CONFIG_FB_PM3=m
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_TMIO is not set
CONFIG_FB_SM501=m
# CONFIG_FB_UDL is not set
# CONFIG_FB_VIRTUAL is not set
CONFIG_FB_METRONOME=m
CONFIG_FB_MB862XX=m
CONFIG_FB_MB862XX_PCI_GDC=y
# CONFIG_FB_BROADSHEET is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_GENERIC is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
# CONFIG_BACKLIGHT_PCF50633 is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y

With a default 1600x1200 X display, I'm getting a 200x75 colour console:

emeric@longspeak:~$ dmesg | grep Console
[    0.000000] Console: colour VGA+ 80x25
[   30.332167] Console: switching to colour frame buffer device 200x75

      Émeric



2011/9/18 A. Devine<devine@dna.ie>:
Apologies for the Spam, but I made a lot of progress on the below:

Built hp-agp into the kernel, not a module
Enabled the fbcon module in the Kernel config
Forceload fbcon module at boot
Set AGP mode to 2 and allowed KMS on


This got me a black screen in the terminal (some sort of unsupported
text mode?) but starting X I can see with KMS enabled I get no AGP bind
errors and no DRM panics. GLXGears/Info confirm DRI and HW acceleration
with R300 working and no corruption! GLXgears is putting out 1925fps.

Now just need to fix the terminal mode!


Alan


On 09/18/11 00:38, A. Devine wrote:
Just to update on the below, after Sending I double-checked if HP AGP
was actually selected in the Kernal config.. which it wasnt, doh! With
that on and hp-agp forced to load as a module that bit is ok, but with
KMS enabled I get no screen and instant beeping error.

With no KMS I get:

[   275.231] drmOpenByBusid: drmGetBusid reports pci:0000:80:00.0
[   275.231] (II) [drm] DRM interface version 1.4
[   275.231] (II) [drm] Mapping SAREA for DRM lock failed.
[   275.231] (EE) RADEON(0): [dri] DRIScreenInit failed.  Disabling DRI.


This is with Emeric's patch on hp-agp , same no matter I think. I think
Ill try the other AGP card again (above still with R300).



On 09/17/11 22:42, A. Devine wrote:
Hi Emeric,

To finally get back onto this, it appears hp-agp is not being loaded as
a module (not in lsmod and I have tried manually specifing it in the
modules file).
I have also tried compiling the kernel with it built in, no difference
to results. With the R300 card when KMS is enabled I get a black screen
when Gentoo is loaded, with no KMS (radeon modeset=0) I get the terminal
but no working AGP (no DRI) due to:

Xorg.0.log
[  5480.077] (II) [drm] DRM interface version 1.4
[  5480.077] (II) [drm] Mapping SAREA for DRM lock failed.
[  5480.077] (EE) RADEON(0): [dri] DRIScreenInit failed.  Disabling DRI.


AGPGart however is loaded (dmesg |grep agp):
IOC: reserving 512Mb of IOVA space at 0x60000000 for agpgart
Linux agpgart interface v0.103


I get a DRM error in dmesg however:
[drm] Initialized radeon 1.33.0 20080528 for 0000:80:00.0 on minor 0
[drm:drm_mmap_locked] *ERROR* Could not find map


Very odd I get all these problems only with an R300 card though.. as per
the earlier note in the thread the RV620 (Radeon HD2500) works much
better, though in "PCI mode"?


Alan


On 09/02/11 13:16, Émeric Maschino wrote:
Hi Alan,

[drm:radeon_agp_init] *ERROR* Unable to acquire AGP: -19

This error is always there no matter the patch or not.
Good news at tleast that the patch isn't introducing a new regression.

About this error, did you check that the hp zx1 AGP GART is either
compiled into the kernel or as a module AND loaded into memory (lsmod
| grep hp-agp)?

More annoyingly I get a corrupted display even in GLXGears with the R300
(although 700fps) where I was getting perfect image but 400fps on the RV610.
I cannot understand why the R300 is still getting the corrupted display,
it got it without any recompiling (which I have done now many times to
test the above) even when just swapping the cards over (same driver so
should work).
Is it with current Mesa? I also had screen corruption with my FireGL
X1, but the problem has been fixed by now
(https://bugs.freedesktop.org/show_bug.cgi?id=36608).

      Emeric



--
To UNSUBSCRIBE, email to debian-ia64-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/4E75D25C.5090502@dna.ie





Reply to: