Re: [gentoo-user] Radeon driver - blank console [SOLVED]

[Helmut Jarausch]

On 01/07/2015 08:07:26 AM, Mick wrote:
> On Tuesday 06 Jan 2015 10:09:25 Helmut Jarausch wrote:
> > On 01/05/2015 02:49:04 PM, Florian Gamböck wrote:
> > > Am 05.01.2015 um 14:42 schrieb Helmut Jarausch:
> > > > Which (framebuffer?) kernel parameters have to set?
> > >
> > > Try compiling CONFIG_DRM_RADEON as module and do not enable any
> frame
> > >
> > > buffers, especially not CONFIG_FB_RADEON, as absurd as it sounds.
> > >
> > > This should take care of your invisible virtual terminal.
> >
> > Unfortunately, this didn't suffice.
> > Looking at the kernel configuration of Systemrescuecd I've added
> the
> > following kernel configuration parameters (to my previous kernel
> > configuration for fglrx)
> >
> >
> > # CONFIG_FIRMWARE_IN_KERNEL is not set
> > CONFIG_DRM=m
> > CONFIG_DRM_KMS_HELPER=m
> > CONFIG_DRM_KMS_FB_HELPER=y
> > CONFIG_DRM_LOAD_EDID_FIRMWARE=y
> > CONFIG_DRM_TTM=m
> > CONFIG_DRM_RADEON=m
> > CONFIG_FIRMWARE_EDID=y
> > CONFIG_FB_BOOT_VESA_SUPPORT=y
> > CONFIG_FB_VESA=y
> > CONFIG_FB_SIMPLE=y
> > CONFIG_FRAMEBUFFER_CONSOLE=y
> > CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
> > CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
> >
> >
> > I hope this might help others experiencing the same problems
> > Helmut
>
> With CONFIG_FIRMWARE_IN_KERNEL not set your set up would run the VESA
>
> framebuffer, rather than  KMS.
>
> These are my corresponding choices on my system:
>
> CONFIG_FRAMEBUFFER_CONSOLE=y
> CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
> # CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
>
> CONFIG_X86_SYSFB=y
> # CONFIG_NET_SCH_SFB is not set
> # CONFIG_IFB is not set
> CONFIG_DRM_KMS_FB_HELPER=y
> CONFIG_FB=y
> # CONFIG_FB_DDC is not set
> # 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 is not set
> CONFIG_FB_MODE_HELPERS=y
> # CONFIG_FB_TILEBLITTING is not set
> # CONFIG_FB_CIRRUS is not set
> # CONFIG_FB_PM2 is not set
> # CONFIG_FB_CYBER2000 is not set
> # CONFIG_FB_ARC is not set
> # CONFIG_FB_ASILIANT is not set
> # CONFIG_FB_IMSTT is not set
> # CONFIG_FB_VGA16 is not set
> # CONFIG_FB_UVESA is not set
> # CONFIG_FB_VESA is not set
> # CONFIG_FB_N411 is not set
> # CONFIG_FB_HGA is not set
> # CONFIG_FB_OPENCORES is not set
> # CONFIG_FB_S1D13XXX is not set
> # CONFIG_FB_NVIDIA is not set
> # CONFIG_FB_RIVA is not set
> # CONFIG_FB_I740 is not set
> # CONFIG_FB_LE80578 is not set
> # CONFIG_FB_MATROX is not set
> # CONFIG_FB_RADEON is not set
> # CONFIG_FB_ATY128 is not set
> # CONFIG_FB_ATY is not set
> # CONFIG_FB_S3 is not set
> # CONFIG_FB_SAVAGE is not set
> # CONFIG_FB_SIS is not set
> # CONFIG_FB_VIA is not set
> # CONFIG_FB_NEOMAGIC is not set
> # CONFIG_FB_KYRO is not set
> # CONFIG_FB_3DFX is not set
> # CONFIG_FB_VOODOO1 is not set
> # CONFIG_FB_VT8623 is not set
> # CONFIG_FB_TRIDENT is not set
> # CONFIG_FB_ARK is not set
> # CONFIG_FB_PM3 is not set
> # CONFIG_FB_CARMINE is not set
> # CONFIG_FB_SMSCUFX is not set
> # CONFIG_FB_UDL is not set
> # CONFIG_FB_VIRTUAL is not set
> # CONFIG_FB_METRONOME is not set
> # CONFIG_FB_MB862XX is not set
> # CONFIG_FB_BROADSHEET is not set
> # CONFIG_FB_AUO_K190X is not set
> # CONFIG_FB_SIMPLE is not set
> # CONFIG_FB_CON_DECOR is not set
> # CONFIG_FB_XGI is not set
>
> --
Thanks Mick,

I'll try that when I generate my next kernel.

Helmut