[gentoo-user] DRM kernel issues

[gentoo-user] DRM kernel issues

[James]

> OK,

So I built this kernel twice, one with DRM * and once DRM [m]

In the /boot dir ; diff config-3.13.6-gentoo config-3.13.6B-gentoo

yeilds:


2256,2257c2256,2257
< CONFIG_AGP=y
< CONFIG_AGP_AMD64=y
---
> CONFIG_AGP=m
> CONFIG_AGP_AMD64=m
2264,2265c2264,2265
< CONFIG_DRM=y
< CONFIG_DRM_KMS_HELPER=y
---
> CONFIG_DRM=m
> CONFIG_DRM_KMS_HELPER=m
2268c2268
< CONFIG_DRM_TTM=y
---
> CONFIG_DRM_TTM=m
2278c2278
< CONFIG_DRM_RADEON=y
---
> CONFIG_DRM_RADEON=m


So when I boot the one with DRM_Radeon=m, I still get this error
message building the latest radeon driver:

* Checking for suitable kernel configuration options...
(red) * CONFIG_DRM must be disabled or compiled as a module and not 
(red) * loaded for direct rendering to work.
 * Please check to make sure these options are set correctly.

Sure it can easily be related to my limited knowledge of grub2,
but I did boot the 3.13.6B version of the kernel....
where all is set as modules....

ideas or suggestions as to what I missed?



James

Re: [gentoo-user] DRM kernel issues

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 749 bytes --]

On Tue, 25 Mar 2014 20:48:29 +0000 (UTC), James wrote:

> So I built this kernel twice, one with DRM * and once DRM [m]
> 
> So when I boot the one with DRM_Radeon=m, I still get this error
> message building the latest radeon driver:
> 
> * Checking for suitable kernel configuration options...
> (red) * CONFIG_DRM must be disabled or compiled as a module and not 
> (red) * loaded for direct rendering to work.
>  * Please check to make sure these options are set correctly.

Doesn't the ebuild check the config in /usr/src/linux, not 
/proc/config.gz? So it is checking your latest config, not the running
kernel.


-- 
Neil Bothwick

Hospitality:  making your guests feel like they're at home, even if you
wish they were.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] DRM kernel issues

[wraeth]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 26/03/14 07:48, James wrote:
> So I built this kernel twice, one with DRM * and once DRM [m]

> Sure it can easily be related to my limited knowledge of grub2, but I did
> boot the 3.13.6B version of the kernel.... where all is set as modules....

The build process builds against whatever was last built in /usr/src/linux.

That means that, even though you've booted a kernel that has DRM built as a
module, when ati-drivers builds, it is looking at the config and objects that
reside within /usr/src/linux.

That being said, I'm pretty sure the warning you're being presented with is
just a warning and is safe to ignore, given that you know you need to be
running a kernel that does not have DRM built-in.

Cheers;
wraeth
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlMx/6sACgkQGYlqHeQRhkyEzwD/R+WuCQZvxD4pqS/3gxtfNcdn
J1+91UsQKlcKf9+ZXl8A/1XAjptt2Bd9lfWh3TrVsE7M3kWguFnT4lSoUztm0bOS
=nESM
-----END PGP SIGNATURE-----

[gentoo-user] Re: DRM kernel issues

[James]

Neil Bothwick <neil <at> digimed.co.uk> writes:


> > * Checking for suitable kernel configuration options...
> > (red) * CONFIG_DRM must be disabled or compiled as a module and not 
> > (red) * loaded for direct rendering to work.
> >  * Please check to make sure these options are set correctly.

> Doesn't the ebuild check the config in /usr/src/linux, not 
> /proc/config.gz? So it is checking your latest config, not the running
> kernel.


Ahhhhhhhhhhhhh.

I did not know that.

makes sense...

thx


James

[gentoo-user] Re: DRM kernel issues

[James]

wraeth <wraeth <at> privatdemail.net> writes:


> That being said, I'm pretty sure the warning you're being presented with is
> just a warning and is safe to ignore, given that you know you need to be
> running a kernel that does not have DRM built-in.

Well this is good news too.... I suspected something like
this, but did not know....

thx
James

[gentoo-user] Re: DRM kernel issues

[James]

wraeth <wraeth <at> privatdemail.net> writes:


> That being said, I'm pretty sure the warning you're being presented with is
> just a warning and is safe to ignore, given that you know you need to be
> running a kernel that does not have DRM built-in.

Ah, look what I verified:

glxinfo
name of display: :0
display: :0  screen: 0
direct rendering: Yes


But compiling the driver still fails, despite making DRM[m]
as suggested:

make[1]: Leaving directory `/usr/src/linux-3.13.6B-gentoo'
make: *** [kmod_build] Error 2
 * ERROR: x11-drivers/ati-drivers-13.9::gentoo failed (compile phase):
 *   emake failed

menuconfig -->DD-->graphics--> 

 <M> /dev/agpgart (AGP Support)  --->                           
 <M> Direct Rendering Manager (XFree86 4.1.0 and higher DRI 
 <M> ATI Radeon       

Can you spot what I'm doing wrong?

James  

Re: [gentoo-user] Re: DRM kernel issues

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 3406 bytes --]

On Wednesday 26 Mar 2014 15:01:07 James wrote:
> wraeth <wraeth <at> privatdemail.net> writes:
> > That being said, I'm pretty sure the warning you're being presented with
> > is just a warning and is safe to ignore, given that you know you need to
> > be running a kernel that does not have DRM built-in.
> 
> Ah, look what I verified:
> 
> glxinfo
> name of display: :0
> display: :0  screen: 0
> direct rendering: Yes
> 
> 
> But compiling the driver still fails, despite making DRM[m]
> as suggested:
> 
> make[1]: Leaving directory `/usr/src/linux-3.13.6B-gentoo'
> make: *** [kmod_build] Error 2
>  * ERROR: x11-drivers/ati-drivers-13.9::gentoo failed (compile phase):
>  *   emake failed
> 
> menuconfig -->DD-->graphics-->
> 
>  <M> /dev/agpgart (AGP Support)  --->
>  <M> Direct Rendering Manager (XFree86 4.1.0 and higher DRI
>  <M> ATI Radeon
> 
> Can you spot what I'm doing wrong?
> 
> James

This much works fine here:

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH=""
CONFIG_DEVTMPFS=y
# CONFIG_DEVTMPFS_MOUNT is not set
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE="radeon/R700_rlc.bin radeon/RV730_smc.bin 
radeon/RV710_uvd.bin"
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware/"
# CONFIG_FW_LOADER_USER_HELPER is not set
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
# CONFIG_GENERIC_CPU_DEVICES is not set
CONFIG_DMA_SHARED_BUFFER=y
[snip ...]

#
# Graphics support
#
CONFIG_AGP=y
CONFIG_AGP_INTEL=y
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_VIA is not set
CONFIG_VGA_ARB=y
CONFIG_VGA_ARB_MAX_GPUS=16
# CONFIG_VGA_SWITCHEROO is not set
CONFIG_DRM=y
CONFIG_DRM_USB=m
CONFIG_DRM_KMS_HELPER=y
# CONFIG_DRM_LOAD_EDID_FIRMWARE is not set
CONFIG_DRM_TTM=y

#
# I2C encoder or helper chips
#
# CONFIG_DRM_I2C_CH7006 is not set
# CONFIG_DRM_I2C_SIL164 is not set
# CONFIG_DRM_I2C_NXP_TDA998X is not set
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=y
# CONFIG_DRM_RADEON_UMS is not set
# CONFIG_DRM_NOUVEAU is not set
# CONFIG_DRM_I915 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
# CONFIG_DRM_VMWGFX is not set
# CONFIG_DRM_GMA500 is not set
CONFIG_DRM_UDL=m
# CONFIG_DRM_AST is not set
# CONFIG_DRM_MGAG200 is not set
# CONFIG_DRM_CIRRUS_QEMU is not set
# CONFIG_DRM_QXL is not set
# CONFIG_VGASTATE is not set
CONFIG_VIDEO_OUTPUT_CONTROL=m
CONFIG_HDMI=y
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
CONFIG_FB_DDC=y
# CONFIG_FB_BOOT_VESA_SUPPORT is not set
CONFIG_FB_CFB_FILLRECT=y
# CONFIG_DRM_QXL is not set
# CONFIG_VGASTATE is not set
CONFIG_VIDEO_OUTPUT_CONTROL=m
CONFIG_HDMI=y
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
CONFIG_FB_DDC=y
# 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 is not set
CONFIG_FB_DEFERRED_IO=y
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
CONFIG_FB_BACKLIGHT=y
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

[gentoo-user] Re: DRM kernel issues

[James]

Mick <michaelkintzios <at> gmail.com> writes:


> > But compiling the driver still fails, despite making DRM[m]
> > as suggested:

> This much works fine here:

> # Generic Driver Options

SNIP

> Regards,
> Mick

Hey, thx Mick. This problem is related to my quandry of how to manage grub2
efficiently. It's likely to take me days/weeks to experiment and 
figure out what to do, exactly. I find interesting snippets about Grub 2
around the net, few well written documents. If rebooting is an 
unpredictable exercise, it makes kernel refinements and debugging
an event for lots of cursing; not that I curse machines (too much).....


I'll post back when I've made some progress (either forward or backward).

thx,
James

[gentoo-user] Re: DRM kernel issues

[James]

wraeth <wraeth <at> privatdemail.net> writes:


> > So I built this kernel twice, one with DRM * and once DRM [m]

> > Sure it can easily be related to my limited knowledge of grub2, but I did
> > boot the 3.13.6B version of the kernel.... where all is set as modules....

> The build process builds against whatever was last built in /usr/src/linux.

> That means that, even though you've booted a kernel that has DRM built as a
> module, when ati-drivers builds, it is looking at the config and objects 
> that  reside within /usr/src/linux.

> That being said, I'm pretty sure the warning you're being presented with is
> just a warning and is safe to ignore, given that you know you need to be
> running a kernel that does not have DRM built-in.


Well, I think I found the problem (?)

lspci shows:

[Radeon HD 4350/4550]    an old fanless  card in this FX8350 machine

This web pages shows only x11-org support for this card (?):
https://wiki.gentoo.org/wiki/ATI_FAQ

RV770 (R700) 	RadeonHD 4000 series 	[xorg]   
Note no "AMD" or "DRI"

equery depends ati-drivers
 * These packages depend on ati-drivers:
x11-base/xorg-drivers-1.14 (video_cards_fglrx ? x11-drivers/ati-drivers)


So I must make modification so the ati-drivers is not called by
xorg-drivers. The desktop is simple X with LXDE and openbox; so why is
ati-drivers being called by xorg-drivers? Because I have this set up in
make.conf (?):

VIDEO_CARDS="radeon fbdev fglrx vesa"

Which should be 
VIDEO_CARDS="fbdev fglrx vesa"

???
comments?

James

Re: [gentoo-user] Re: DRM kernel issues

[wraeth]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 28/03/14 12:04, James wrote:
> So I must make modification so the ati-drivers is not called by 
> xorg-drivers. The desktop is simple X with LXDE and openbox; so why is 
> ati-drivers being called by xorg-drivers? Because I have this set up in 
> make.conf (?):
> 
> VIDEO_CARDS="radeon fbdev fglrx vesa"
> 
> Which should be VIDEO_CARDS="fbdev fglrx vesa"

Yes, VIDEO_CARDS is a USE-Expand variable - each item in VIDEO_CARDS is
expanded to an equivalent use flag of "video_cards_<flag>", meaning
VIDEO_CARDS="radeon fbdev fglrx vesa" expands into:

video_cards_radeon
video_cards_fbdev
video_cards_fglrx
video_cards_vesa

These use flags then tell xorg-drivers to pull in the relevant packages.

Remove fglrx from your VIDEO_CARDS, do a world-update and depclean (and make
sure you check ``eselect opengl`` is set to "xorg-x11") and see how that goes.

Cheers.
- --
wraeth
GnuPG Fingerprint:
D1FF 129E 77EF FD1F CEA4
F384 1989 6A1D E411 864C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlM0zgAACgkQGYlqHeQRhkwqewD8Dm1OEy0CmazxYRRjwqYrWava
kYbDYFreOr7JiuFLgkMA/3l10U8aqswhJF5sJJ7QpwRs/Y7M01FadKsORja1pafK
=qSs4
-----END PGP SIGNATURE-----