Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
startx, no displays found...
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
bigbanana69
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jul 2017
Posts: 141
Location: Skopje

PostPosted: Wed Mar 13, 2019 8:57 pm    Post subject: startx, no displays found... Reply with quote

I just installed gentoo x86-17.0/desktop (stable) with xfce4 by the gentoo handbook on my Acer AspireES laptop.

I did echo exec startxfce4" > ~/.xinitrc

when I try startx or startxfce4, or exec startxfce4 it returns with error:

No monitors found. (Or maybe it was No displays found), so xfce4 doesn't starts.

Previously I had installed gentoo x86-17.0/desktop (stable) just as i686 and startxfce4 was working fine.
This time I had put -march=native (instead i686), CPU_FLAGS_X86= (for my laptop's cpu) & also VIDEO_CARDS="amdgpu radeonsi" in make.conf. Only that is the difference\ between the installations

Hardware:

AMD E1-2500 1.4 dualcore APU with radeon hd 8240 (listed as Kabini or also /R3)
2gb ddr low profile ram
atheros bluetooth and wifi.
realtek alc, ethernet and cardreader.
Chicony UVC webcam
Elan touchpad
_________________
You are not using computers if you are not using Gentoo.


Last edited by bigbanana69 on Wed Mar 13, 2019 9:19 pm; edited 1 time in total
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43758
Location: 56N 3W

PostPosted: Wed Mar 13, 2019 9:02 pm    Post subject: Reply with quote

bigbanana69,

Please put /var/log/Xorg.0.log onto a pastebin site and post the link.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
bigbanana69
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jul 2017
Posts: 141
Location: Skopje

PostPosted: Wed Mar 13, 2019 10:33 pm    Post subject: Reply with quote

/var/log/Xorg.0.log

https://pastebin.com/7sPdXMU2
_________________
You are not using computers if you are not using Gentoo.
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7259
Location: Saint Amant, Acadiana

PostPosted: Wed Mar 13, 2019 10:50 pm    Post subject: Reply with quote

Code:
[ 43430.144] (EE) open /dev/dri/card0: No such file or directory

Your kernel is misconfigured, CONFIG_DRM_RADEON needs to be enabled.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43758
Location: 56N 3W

PostPosted: Wed Mar 13, 2019 11:08 pm    Post subject: Reply with quote

bigbanana69,

Code:
[ 43430.135] (==) Matched ati as autoconfigured driver 0
[ 43430.135] (==) Matched modesetting as autoconfigured driver 1
[ 43430.135] (==) Matched fbdev as autoconfigured driver 2
[ 43430.135] (==) Matched vesa as autoconfigured driver 3
[ 43430.135] (==) Assigned the driver to the xf86ConfigLayout


That's your autodetected driver list. As Jaglover says, you need CONFIG_DRM_RADEON in your kernel.

For another thread we know that you have VIDEO_CARDS="amdgpu radeonsi"
You will also need to fix your VIDEO_CARDS as you won't want amdgpu. its radeon.
I'm not sure about radeonsi for your card, for mesa.

Code:
[ 43430.138] (II) RADEON: Driver for ATI/AMD Radeon chipsets:

So Radeon is there.

Code:
[ 43430.144] (II) [KMS] drm report modesetting isn't supported.
[ 43430.144] (EE) open /dev/dri/card0: No such file or directory


It looks like it just your kernel to fix before you move on to your next Gentoo educational experience. :)
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
bigbanana69
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jul 2017
Posts: 141
Location: Skopje

PostPosted: Thu Mar 14, 2019 8:52 pm    Post subject: Reply with quote

Ok, in the kernel I have selected the 2, radeon & amgpu... I tried it without radeon and even terminal didn't bou, I figured that I need radeon in kernel. Then the terminal works.

After reading this article on gentoo wiki:

https://wiki.gentoo.org/wiki/AMDGPU

I figured that my gpu which is shown as Kabini is on the list, so that's why I had put "amdgpu radeonsi" instead "radeon" even if the the gentoo installation wasn't working with only amdgpu selected in the kernel configuration (so I had to recompile with radeon selected).

I'll change it to "radeon" and apply
Code:
emerge --ask --changed-use --deep @world
as suggested on https://wiki.gentoo.org/wiki/Template:VIDEO_CARDS, but another question before I'll apply this is I also want to put av1 in USE in make.conf. AV1 is videocodec which isn't on the list in use.desc. Should I put av1 in USE in make.conf or it's support is automatically installed in programs such as ffmpeg, vlc and mplayer?
_________________
You are not using computers if you are not using Gentoo.
Back to top
View user's profile Send private message
bigbanana69
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jul 2017
Posts: 141
Location: Skopje

PostPosted: Sun Mar 17, 2019 8:39 pm    Post subject: Reply with quote

I reinstalled gentoo x86. I selected only radeon in kernel (no amdgpu). I had put VIDEO_CARDS="radeon" in make.conf, then installed gentoox86/17.0/desktop, then xfce4. Then I did echo "exec startsfce4" > ~/.xinitrc, but startx and startxfce4 terminate again.

Here's the new Xorg.0.log

Code:
[ 23187.872]
X.Org X Server 1.20.3
X Protocol Version 11, Revision 0
[ 23187.873] Build Operating System: Linux 4.19.27-gentoo-r1 i686 Gentoo
[ 23187.873] Current Operating System: Linux AspireES 4.19.27-gentoo-r1 #1 SMP Fri Mar 15 09:22:14 CET 2019 i686
[ 23187.873] Kernel command line: BOOT_IMAGE=/vmlinuz-4.19.27-gentoo-r1 root=/dev/sda4 ro
[ 23187.873] Build Date: 17 March 2019  04:29:14PM
[ 23187.873] 
[ 23187.874] Current version of pixman: 0.36.0
[ 23187.874]    Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
[ 23187.874] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 23187.875] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 17 20:30:20 2019
[ 23187.875] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 23187.876] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 23187.876] (==) No Layout section.  Using the first Screen section.
[ 23187.876] (==) No screen section available. Using defaults.
[ 23187.876] (**) |-->Screen "Default Screen Section" (0)
[ 23187.876] (**) |   |-->Monitor "<default monitor>"
[ 23187.877] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
[ 23187.877] (==) Automatically adding devices
[ 23187.877] (==) Automatically enabling devices
[ 23187.877] (==) Automatically adding GPU devices
[ 23187.877] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 23187.877] (WW) The directory "/usr/share/fonts/misc/" does not exist.
[ 23187.877]    Entry deleted from font path.
[ 23187.877] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[ 23187.877]    Entry deleted from font path.
[ 23187.877] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 23187.877]    Entry deleted from font path.
[ 23187.877] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 23187.877]    Entry deleted from font path.
[ 23187.877] (WW) The directory "/usr/share/fonts/100dpi/" does not exist.
[ 23187.877]    Entry deleted from font path.
[ 23187.877] (WW) The directory "/usr/share/fonts/75dpi/" does not exist.
[ 23187.877]    Entry deleted from font path.
[ 23187.877] (==) FontPath set to:
   
[ 23187.877] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 23187.877] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 23187.877] (II) Loader magic: 0x74f640
[ 23187.877] (II) Module ABI versions:
[ 23187.877]    X.Org ANSI C Emulation: 0.4
[ 23187.877]    X.Org Video Driver: 24.0
[ 23187.877]    X.Org XInput driver : 24.1
[ 23187.877]    X.Org Server Extension : 10.0
[ 23187.885] (--) PCI:*(0@0:1:0) 1002:9838:1025:104b rev 0, Mem @ 0x80000000/268435456, 0x90000000/8388608, 0x90a00000/262144, I/O @ 0x00003000/256, BIOS @ 0x????????/131072
[ 23187.885] (II) LoadModule: "glx"
[ 23187.885] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 23187.887] (II) Module glx: vendor="X.Org Foundation"
[ 23187.887]    compiled for 1.20.3, module version = 1.0.0
[ 23187.887]    ABI class: X.Org Server Extension, version 10.0
[ 23187.887] (==) Matched ati as autoconfigured driver 0
[ 23187.887] (==) Matched modesetting as autoconfigured driver 1
[ 23187.887] (==) Matched fbdev as autoconfigured driver 2
[ 23187.887] (==) Matched vesa as autoconfigured driver 3
[ 23187.887] (==) Assigned the driver to the xf86ConfigLayout
[ 23187.887] (II) LoadModule: "ati"
[ 23187.888] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[ 23187.888] (II) Module ati: vendor="X.Org Foundation"
[ 23187.888]    compiled for 1.20.3, module version = 18.1.0
[ 23187.888]    Module class: X.Org Video Driver
[ 23187.888]    ABI class: X.Org Video Driver, version 24.0
[ 23187.889] (II) LoadModule: "radeon"
[ 23187.889] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[ 23187.890] (II) Module radeon: vendor="X.Org Foundation"
[ 23187.890]    compiled for 1.20.3, module version = 18.1.0
[ 23187.890]    Module class: X.Org Video Driver
[ 23187.890]    ABI class: X.Org Video Driver, version 24.0
[ 23187.890] (II) LoadModule: "modesetting"
[ 23187.890] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 23187.890] (II) Module modesetting: vendor="X.Org Foundation"
[ 23187.890]    compiled for 1.20.3, module version = 1.20.3
[ 23187.890]    Module class: X.Org Video Driver
[ 23187.890]    ABI class: X.Org Video Driver, version 24.0
[ 23187.890] (II) LoadModule: "fbdev"
[ 23187.890] (WW) Warning, couldn't open module fbdev
[ 23187.890] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 23187.890] (II) LoadModule: "vesa"
[ 23187.891] (WW) Warning, couldn't open module vesa
[ 23187.891] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 23187.891] (II) RADEON: Driver for ATI/AMD Radeon chipsets:
   ATI Radeon Mobility X600 (M24), ATI FireMV 2400,
   ATI Radeon Mobility X300 (M24), ATI FireGL M24 GL,
   ATI Radeon X600 (RV380), ATI FireGL V3200 (RV380),
   ATI Radeon IGP320 (A3), ATI Radeon IGP330/340/350 (A4),
   ATI Radeon 9500, ATI Radeon 9600TX, ATI FireGL Z1, ATI Radeon 9800SE,
   ATI Radeon 9800, ATI FireGL X2, ATI Radeon 9600, ATI Radeon 9600SE,
   ATI Radeon 9600XT, ATI FireGL T2, ATI Radeon 9650, ATI FireGL RV360,
   ATI Radeon 7000 IGP (A4+), ATI Radeon 8500 AIW,
   ATI Radeon IGP320M (U1), ATI Radeon IGP330M/340M/350M (U2),
   ATI Radeon Mobility 7000 IGP, ATI Radeon 9000/PRO, ATI Radeon 9000,
   ATI Radeon X800 (R420), ATI Radeon X800PRO (R420),
   ATI Radeon X800SE (R420), ATI FireGL X3 (R420),
   ATI Radeon Mobility 9800 (M18), ATI Radeon X800 SE (R420),
   ATI Radeon X800XT (R420), ATI Radeon X800 VE (R420),
   ATI Radeon X850 (R480), ATI Radeon X850 XT (R480),
   ATI Radeon X850 SE (R480), ATI Radeon X850 PRO (R480),
   ATI Radeon X850 XT PE (R480), ATI Radeon Mobility M7,
   ATI Mobility FireGL 7800 M7, ATI Radeon Mobility M6,
   ATI FireGL Mobility 9000 (M9), ATI Radeon Mobility 9000 (M9),
   ATI Radeon 9700 Pro, ATI Radeon 9700/9500Pro, ATI FireGL X1,
   ATI Radeon 9800PRO, ATI Radeon 9800XT,
   ATI Radeon Mobility 9600/9700 (M10/M11),
   ATI Radeon Mobility 9600 (M10), ATI Radeon Mobility 9600 (M11),
   ATI FireGL Mobility T2 (M10), ATI FireGL Mobility T2e (M11),
   ATI Radeon, ATI FireGL 8700/8800, ATI Radeon 8500, ATI Radeon 9100,
   ATI Radeon 7500, ATI Radeon VE/7000, ATI ES1000,
   ATI Radeon Mobility X300 (M22), ATI Radeon Mobility X600 SE (M24C),
   ATI FireGL M22 GL, ATI Radeon X800 (R423), ATI Radeon X800PRO (R423),
   ATI Radeon X800LE (R423), ATI Radeon X800SE (R423),
   ATI Radeon X800 XTP (R430), ATI Radeon X800 XL (R430),
   ATI Radeon X800 SE (R430), ATI Radeon X800 (R430),
   ATI FireGL V7100 (R423), ATI FireGL V5100 (R423),
   ATI FireGL unknown (R423), ATI Mobility FireGL V5000 (M26),
   ATI Mobility Radeon X700 XL (M26), ATI Mobility Radeon X700 (M26),
   ATI Radeon X550XTX, ATI Radeon 9100 IGP (A5),
   ATI Radeon Mobility 9100 IGP (U3), ATI Radeon XPRESS 200,
   ATI Radeon XPRESS 200M, ATI Radeon 9250, ATI Radeon 9200,
   ATI Radeon 9200SE, ATI FireMV 2200, ATI Radeon X300 (RV370),
   ATI Radeon X600 (RV370), ATI Radeon X550 (RV370),
   ATI FireGL V3100 (RV370), ATI FireMV 2200 PCIE (RV370),
   ATI Radeon Mobility 9200 (M9+), ATI Mobility Radeon X800 XT (M28),
   ATI Mobility FireGL V5100 (M28), ATI Mobility Radeon X800 (M28),
   ATI Radeon X850, ATI unknown Radeon / FireGL (R480),
   ATI Radeon X800XT (R423), ATI FireGL V5000 (RV410),
   ATI Radeon X700 XT (RV410), ATI Radeon X700 PRO (RV410),
   ATI Radeon X700 SE (RV410), ATI Radeon X700 (RV410),
   ATI Radeon X1800, ATI Mobility Radeon X1800 XT,
   ATI Mobility Radeon X1800, ATI Mobility FireGL V7200,
   ATI FireGL V7200, ATI FireGL V5300, ATI Mobility FireGL V7100,
   ATI FireGL V7300, ATI FireGL V7350, ATI Radeon X1600, ATI RV505,
   ATI Radeon X1300/X1550, ATI Radeon X1550, ATI M54-GL,
   ATI Mobility Radeon X1400, ATI Radeon X1550 64-bit,
   ATI Mobility Radeon X1300, ATI Radeon X1300, ATI FireGL V3300,
   ATI FireGL V3350, ATI Mobility Radeon X1450,
   ATI Mobility Radeon X2300, ATI Mobility Radeon X1350,
   ATI FireMV 2250, ATI Radeon X1650, ATI Mobility FireGL V5200,
   ATI Mobility Radeon X1600, ATI Radeon X1300 XT/X1600 Pro,
   ATI FireGL V3400, ATI Mobility FireGL V5250,
   ATI Mobility Radeon X1700, ATI Mobility Radeon X1700 XT,
   ATI FireGL V5200, ATI Radeon X2300HD, ATI Mobility Radeon HD 2300,
   ATI Radeon X1950, ATI Radeon X1900, ATI AMD Stream Processor,
   ATI RV560, ATI Mobility Radeon X1900, ATI Radeon X1950 GT, ATI RV570,
   ATI FireGL V7400, ATI Radeon 9100 PRO IGP,
   ATI Radeon Mobility 9200 IGP, ATI Radeon X1200, ATI RS740,
   ATI RS740M, ATI Radeon HD 2900 XT, ATI Radeon HD 2900 Pro,
   ATI Radeon HD 2900 GT, ATI FireGL V8650, ATI FireGL V8600,
   ATI FireGL V7600, ATI Radeon 4800 Series, ATI Radeon HD 4870 x2,
   ATI Radeon HD 4850 x2, ATI FirePro V8750 (FireGL),
   ATI FirePro V7760 (FireGL), ATI Mobility RADEON HD 4850,
   ATI Mobility RADEON HD 4850 X2, ATI FirePro RV770,
   AMD FireStream 9270, AMD FireStream 9250, ATI FirePro V8700 (FireGL),
   ATI Mobility RADEON HD 4870, ATI Mobility RADEON M98,
   ATI FirePro M7750, ATI M98, ATI Mobility Radeon HD 4650,
   ATI Radeon RV730 (AGP), ATI Mobility Radeon HD 4670,
   ATI FirePro M5750, ATI RV730XT [Radeon HD 4670], ATI RADEON E4600,
   ATI Radeon HD 4600 Series, ATI RV730 PRO [Radeon HD 4650],
   ATI FirePro V7750 (FireGL), ATI FirePro V5700 (FireGL),
   ATI FirePro V3750 (FireGL), ATI Mobility Radeon HD 4830,
   ATI Mobility Radeon HD 4850, ATI FirePro M7740, ATI RV740,
   ATI Radeon HD 4770, ATI Radeon HD 4700 Series, ATI RV610,
   ATI Radeon HD 2400 XT, ATI Radeon HD 2400 Pro,
   ATI Radeon HD 2400 PRO AGP, ATI FireGL V4000, ATI Radeon HD 2350,
   ATI Mobility Radeon HD 2400 XT, ATI Mobility Radeon HD 2400,
   ATI RADEON E2400, ATI FireMV 2260, ATI RV670, ATI Radeon HD3870,
   ATI Mobility Radeon HD 3850, ATI Radeon HD3850,
   ATI Mobility Radeon HD 3850 X2, ATI Mobility Radeon HD 3870,
   ATI Mobility Radeon HD 3870 X2, ATI Radeon HD3870 X2,
   ATI FireGL V7700, ATI Radeon HD3690, AMD Firestream 9170,
   ATI Radeon HD 4550, ATI Radeon RV710, ATI Radeon HD 4350,
   ATI Mobility Radeon 4300 Series, ATI Mobility Radeon 4500 Series,
   ATI FirePro RG220, ATI Mobility Radeon 4330, ATI RV630,
   ATI Mobility Radeon HD 2600, ATI Mobility Radeon HD 2600 XT,
   ATI Radeon HD 2600 XT AGP, ATI Radeon HD 2600 Pro AGP,
   ATI Radeon HD 2600 XT, ATI Radeon HD 2600 Pro, ATI Gemini RV630,
   ATI Gemini Mobility Radeon HD 2600 XT, ATI FireGL V5600,
   ATI FireGL V3600, ATI Radeon HD 2600 LE,
   ATI Mobility FireGL Graphics Processor, ATI Radeon HD 3470,
   ATI Mobility Radeon HD 3430, ATI Mobility Radeon HD 3400 Series,
   ATI Radeon HD 3450, ATI Radeon HD 3430, ATI FirePro V3700,
   ATI FireMV 2450, ATI Radeon HD 3600 Series, ATI Radeon HD 3650 AGP,
   ATI Radeon HD 3600 PRO, ATI Radeon HD 3600 XT,
   ATI Mobility Radeon HD 3650, ATI Mobility Radeon HD 3670,
   ATI Mobility FireGL V5700, ATI Mobility FireGL V5725,
   ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
   ATI Radeon HD 3300 Graphics, ATI Radeon 3000 Graphics, SUMO, SUMO2,
   ATI Radeon HD 4200, ATI Radeon 4100, ATI Mobility Radeon HD 4200,
   ATI Mobility Radeon 4100, ATI Radeon HD 4290, ATI Radeon HD 4250,
   AMD Radeon HD 6310 Graphics, AMD Radeon HD 6250 Graphics,
   AMD Radeon HD 6300 Series Graphics,
   AMD Radeon HD 6200 Series Graphics, PALM, CYPRESS,
   ATI FirePro (FireGL) Graphics Adapter, AMD Firestream 9370,
   AMD Firestream 9350, ATI Radeon HD 5800 Series,
   ATI Radeon HD 5900 Series, ATI Mobility Radeon HD 5800 Series,
   ATI Radeon HD 5700 Series, ATI Radeon HD 6700 Series,
   ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon HD 5570,
   ATI Radeon HD 5670, ATI Radeon HD 5570, ATI Radeon HD 5500 Series,
   REDWOOD, ATI Mobility Radeon Graphics, CEDAR, ATI FirePro 2270,
   ATI Radeon HD 5450, CAYMAN, AMD Radeon HD 6900 Series,
   AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series, BARTS,
   AMD Radeon HD 6800 Series, AMD Radeon HD 6700 Series, TURKS, CAICOS,
   ARUBA, TAHITI, PITCAIRN, VERDE, OLAND, HAINAN, BONAIRE, KABINI,
   MULLINS, KAVERI, HAWAII
[ 23187.894] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 23187.894] (--) using VT number 7

[ 23187.897] (II) [KMS] drm report modesetting isn't supported.
[ 23187.897] (EE) open /dev/dri/card0: No such file or directory
[ 23187.898] (WW) Falling back to old probe method for modesetting
[ 23187.898] (EE) open /dev/dri/card0: No such file or directory
[ 23187.898] (EE) Screen 0 deleted because of no matching config section.
[ 23187.898] (II) UnloadModule: "radeon"
[ 23187.898] (EE) Screen 0 deleted because of no matching config section.
[ 23187.898] (II) UnloadModule: "modesetting"
[ 23187.898] (EE) Device(s) detected, but none match those in the config file.
[ 23187.898] (EE)
Fatal server error:
[ 23187.898] (EE) no screens found(EE)
[ 23187.898] (EE)
Please consult the The X.Org Foundation support
    at http://wiki.x.org
 for help.
[ 23187.898] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 23187.898] (EE)
[ 23187.900] (EE) Server terminated with error (1). Closing log file.


Acctually I'm using AMD E1-2500 1.4GHz dualcore APU with Radeon HD 8240 - listed as Kabini in terminal (also sometimes marked with /R3).

I had installed gentoo previously without VIDEO_CARDS, and startx and startxfce4 work.
_________________
You are not using computers if you are not using Gentoo.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43758
Location: 56N 3W

PostPosted: Sun Mar 17, 2019 9:39 pm    Post subject: Reply with quote

bigbanana69,

Code:
[ 23187.897] (II) [KMS] drm report modesetting isn't supported.
[ 23187.897] (EE) open /dev/dri/card0: No such file or directory


You are missing DRM support in your kernel.

Code:
[ 23187.873] Current Operating System: Linux AspireES 4.19.27-gentoo-r1 #1 SMP Fri Mar 15 09:22:14 CET 2019 i686

You built the running kernel at Fri Mar 15 09:22:14 CET 2019. Is that what you expected?
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
bigbanana69
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jul 2017
Posts: 141
Location: Skopje

PostPosted: Sun Mar 17, 2019 9:45 pm    Post subject: Reply with quote

Ok, I'll reinstall.
_________________
You are not using computers if you are not using Gentoo.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43758
Location: 56N 3W

PostPosted: Sun Mar 17, 2019 10:15 pm    Post subject: Reply with quote

bigbanana69,

Just rebuild your kernel.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
bigbanana69
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jul 2017
Posts: 141
Location: Skopje

PostPosted: Mon Mar 18, 2019 5:42 am    Post subject: Reply with quote

I'll do a new install anyway.
I want to practice a little bit the things (configuring and installing) in Gentoo. Compiling the packages is a bit of time consuming, but it's fine. Later I'll be learning more advanced things in linux, in bash & ksh and the various linux applications usage, even in terminal.
_________________
You are not using computers if you are not using Gentoo.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43758
Location: 56N 3W

PostPosted: Mon Mar 18, 2019 10:27 am    Post subject: Reply with quote

bigbanana69,

If its not too late, there is a shortcut.

Keep /etc/portage (the dir) and put it in your new install.
Keep /var/lib/portage/world and put it in your new install.

In make.conf set FEATURES=buildpkg

Now
Code:
emerge -e world
will reinstall everything, saving binary packages as it goes.
Next reinstall you can use the binaries instead of waiting for everything to build.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
bigbanana69
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jul 2017
Posts: 141
Location: Skopje

PostPosted: Mon Mar 18, 2019 11:10 am    Post subject: Reply with quote

Oh, I had already formatted the notebook and installed a new kernel with firmware, sysklogd, cronie and grub2.

According to this article: https://wiki.gentoo.org/wiki/Radeon, in the part for the kernel where it says Dynamic Rendering Manager (and the sub-options), they where checked by default, but below that, there were few DRM options with sub-options, so I checked them too. Also from that article, there's a part for the linux firmware, which also was checked by default.

After rebooting, the terminal stopped at some point where it was written something like DRM... up to 128s. I wasn't sure what it was but I had waited for few minutes and it booted. Maybe it was some DRM check or test.

Actually it stops at:
Code:
clocksource: Switched to clocksource tsc


where after 1-2mins it keeps loading.

Later I'll emerge the packages for 17.0/desktop which would take for a while.
_________________
You are not using computers if you are not using Gentoo.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43758
Location: 56N 3W

PostPosted: Mon Mar 18, 2019 2:31 pm    Post subject: Reply with quote

bigbanana69,

Pauses in the boot are often waiting for firmware that is not being provided.
Put dmesg onto a pastebin,

The individual kernel messages are generally not useful as booting is a multi-tasking process, so the last message on the screen is just that.
It does not usually indicate the task that has stalled.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
bigbanana69
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jul 2017
Posts: 141
Location: Skopje

PostPosted: Mon Mar 18, 2019 3:10 pm    Post subject: Reply with quote

dmesg

http://dpaste.com/39Z6X7Z
_________________
You are not using computers if you are not using Gentoo.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43758
Location: 56N 3W

PostPosted: Mon Mar 18, 2019 5:23 pm    Post subject: Reply with quote

bigbanana69,

There is 96 seconds.
Code:
[    1.992351] clocksource: Switched to clocksource tsc
[   98.958758] [drm] radeon kernel modesetting enabled.
[...
[   98.964544] [drm] Loading kabini Microcode
[   98.964667] radeon 0000:00:01.0: Direct firmware load for radeon/kabini_pfp.bin failed with error -2
[   98.964845] radeon 0000:00:01.0: Direct firmware load for radeon/KABINI_pfp.bin failed with error -2
[   98.965003] cik_cp: Failed to load firmware "radeon/KABINI_pfp.bin"
[   98.965109] [drm:cik_init] *ERROR* Failed to load firmware!

Much of the functionality of Radeon card is lost without the firnware.
As root isn't mounted until
Code:
 [  101.266221] VFS: Mounted root (jfs filesystem) readonly on device 8:4.
/lib/firmware cannot be read when the firmware is required.
You need to
Code:
emerge linux-firmware
to populate /lib/firmware/ then include the missing firmware in your kernel build.
Populate the kernel options
CONFIG_EXTRA_FIRMWARE and CONFIG_EXTRA_FIRMWARE_DIR
You might as well include your CPU microcode at the same time.

Code:
[   99.179134] BTRFS: selftest
takes a few seconds ...
Is that really required?

Code:
[  113.637382] evbug: Event. Dev: input4, Type: 4, Code: 4, Value: 19

That looks like another debug kernel option.
If thats CONFIG_INPUT_EVBUG, its a very bad thing an all your keystrokes are recorded in the log. Your username and password may be there but I'm not going to decode it.

Code:
[  115.305157] IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0: link becomes ready

This is close to the last message at the end of booting. You can get about 100 sec out of than by adding in your firmware and turning off debug logspam.

-- edit --

I missed
Code:
[  100.405531] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
thats required for you WiFi
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
bigbanana69
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jul 2017
Posts: 141
Location: Skopje

PostPosted: Mon Mar 18, 2019 5:33 pm    Post subject: Reply with quote

NeddySeagoon, but after compiling the kernel I did
Code:
emerge --ask sys-kernel/linux-firmware
and it installed correctly. JFS might be read-only as I had non-properly shut down the notebook (with holding the power button) as it took a while for the loading.


Quote:
Populate the kernel options
CONFIG_EXTRA_FIRMWARE and CONFIG_EXTRA_FIRMWARE_DIR
You might as well include your CPU microcode at the same time.


How do I do this?
_________________
You are not using computers if you are not using Gentoo.
Back to top
View user's profile Send private message
bigbanana69
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jul 2017
Posts: 141
Location: Skopje

PostPosted: Mon Mar 18, 2019 6:23 pm    Post subject: Reply with quote

As I figured out, I needed to emerge linux-firmware before compiling the kernel, right?

Then to configure the kernel with firmware loading options, amd microcode and compile, right?

So actually now I need to recompile the kernel and install it, then reconfigure grub2, right?

This option in the kernel doesn't checks when I select it and click 'Y':

Code:
() Build named firmware blobs into the kernel binary

_________________
You are not using computers if you are not using Gentoo.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43758
Location: 56N 3W

PostPosted: Mon Mar 18, 2019 6:53 pm    Post subject: Reply with quote

bigbanana69,

Quote:
... but after compiling the kernel ...

That's too late. It cannot be included in the kernel.

Any module requiring firmware must have the firmware available when the module initalises.
There are two cases that work and two that don't.

a) The module and its firmware are both included in the kernel.
b) The module and its firmware are loaded after root is mounted so both can be read from the root filesystem.

Your radeon driver is built into the kernel, so its initalised and tries to load firmware before root is mounted.
The firmware is in /lib/firmware which cannot yet be read because root is not mounted.
Its case c)
d) is hard to do. That's firmware only in the kernel and the kernel module as a loadable module.

Now that linux-firmware is installed, you need to include the bits you need in the kernel.

Go into menuconfig.
Press / and enter EXTRA_FIRMWARE
Press the digit next to the option to go there.
Edit the option, its a text box. Enter radeon/kabini_pfp.bin

All of a sudden, it gets worse. Looking in /lib/firmware/radeon there are 31 files there. I think you only need the ones in lower case as the driver tried to load those first.
Grepping the kernel returns
Code:
/usr/src/linux $ grep -R kabini
drivers/gpu/drm/amd/amdgpu/gfx_v7_0.c:MODULE_FIRMWARE("amdgpu/kabini_pfp.bin");
drivers/gpu/drm/amd/amdgpu/gfx_v7_0.c:MODULE_FIRMWARE("amdgpu/kabini_me.bin");
drivers/gpu/drm/amd/amdgpu/gfx_v7_0.c:MODULE_FIRMWARE("amdgpu/kabini_ce.bin");
drivers/gpu/drm/amd/amdgpu/gfx_v7_0.c:MODULE_FIRMWARE("amdgpu/kabini_rlc.bin");
drivers/gpu/drm/amd/amdgpu/gfx_v7_0.c:MODULE_FIRMWARE("amdgpu/kabini_mec.bin");
drivers/gpu/drm/amd/amdgpu/gfx_v7_0.c:      chip_name = "kabini";
drivers/gpu/drm/amd/amdgpu/amdgpu_uvd.c:#define FIRMWARE_KABINI   "amdgpu/kabini_uvd.bin"
drivers/gpu/drm/amd/amdgpu/cik_sdma.c:MODULE_FIRMWARE("amdgpu/kabini_sdma.bin");
drivers/gpu/drm/amd/amdgpu/cik_sdma.c:MODULE_FIRMWARE("amdgpu/kabini_sdma1.bin");
drivers/gpu/drm/amd/amdgpu/cik_sdma.c:      chip_name = "kabini";
drivers/gpu/drm/amd/amdgpu/amdgpu_vce.c:#define FIRMWARE_KABINI   "amdgpu/kabini_vce.bin"
drivers/gpu/drm/radeon/cik.c:MODULE_FIRMWARE("radeon/kabini_pfp.bin");
drivers/gpu/drm/radeon/cik.c:MODULE_FIRMWARE("radeon/kabini_me.bin");
drivers/gpu/drm/radeon/cik.c:MODULE_FIRMWARE("radeon/kabini_ce.bin");
drivers/gpu/drm/radeon/cik.c:MODULE_FIRMWARE("radeon/kabini_mec.bin");
drivers/gpu/drm/radeon/cik.c:MODULE_FIRMWARE("radeon/kabini_rlc.bin");
drivers/gpu/drm/radeon/cik.c:MODULE_FIRMWARE("radeon/kabini_sdma.bin");
drivers/gpu/drm/radeon/cik.c:      new_chip_name = "kabini";
So you certainly need the six files listed in drivers/gpu/drm/radeon/cik.c
Any more will be harmless. Missing one will get you another firmware loading error.

Notice that kabini is listed against drivers/gpu/drm/amd/amdgpu/gfx_v7_0.c too. That's interesting but not immediately relevant.

List those six files (at least) in the EXTRA_FIRMWARE text box. Its a space separated list. radeon/kabini_pfp.bin radeon/kabini_me.bin radeon/kabini_ce.bin and so on.
Once that box in populated, you will get a new option CONFIG_EXTRA_FIRMWARE_DIR, that will already contain /lib/firmware.

Rebuild and reinstall your kernel. The build process will copy the named files into the kernel binary.
When you reboot, the built in Radeon will find its firmware.

Its the same process for CPU microcode or any other firmware.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
bigbanana69
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jul 2017
Posts: 141
Location: Skopje

PostPosted: Mon Mar 18, 2019 7:03 pm    Post subject: Reply with quote

Ok, I didn't knew that.

Quote:
Press the digit next to the option to go there.
Edit the option, its a text box. Enter radeon/kabini_pfp.bin


Please explain me how to do this more exactly?

And also for the amd microcode?
_________________
You are not using computers if you are not using Gentoo.
Back to top
View user's profile Send private message
bigbanana69
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jul 2017
Posts: 141
Location: Skopje

PostPosted: Tue Mar 19, 2019 11:23 am    Post subject: Reply with quote

I reinstalled Gentoo with firmwares. Now, at boot I get error messages error loading formware radeon/boniare... & radeon /BONIARE ...

It also stops at the "clocksource: Switched to clocksource tsc " for a while and then it boots in terminal with better graphics acceleration and resolution.

Here's the new dmesg output:

http://dpaste.com/0EBRYXK
_________________
You are not using computers if you are not using Gentoo.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43758
Location: 56N 3W

PostPosted: Tue Mar 19, 2019 1:55 pm    Post subject: Reply with quote

bigbanana69,

Now it wants radeon/bonaire_uvd.bin and maybe other bonaire too.
I wasn't expecting that as you have a kabini GPU, not bonaire.

It pauses waiting for microcode still
Code:
[    1.738686] clocksource: Switched to clocksource tsc
[   62.538502] radeon 0000:00:01.0: radeon_uvd: Can't load firmware "radeon/bonaire_uvd.bin"


You may as well add in all the bonaire firmware files too. I don't know which ones it needs.

Your CPU microcode is in /lib/firmware/amd-ucode/.
Your CPU is
Code:
[    0.115218] smpboot: CPU0: AMD E1-2500 APU with Radeon(TM) HD Graphics (family: 0x16, model: 0x0, stepping: 0x1)

That's family: 0x16.

Add in amd-ucode/microcode_amd.bin amd-ucode/microcode_amd_fam15h.bin amd-ucode/ microcode_amd_fam16h.bin to your list of firmware files.
The corresponding .asc files are the detached GPG signatures, so that the validity of the files can be confirmed.
I don't think this is done at load time.

Look for this in dmesg.
Code:
[  187.873367] microcode: CPU1: patch_level=0x07000106
[  187.875756] microcode: Microcode Update Driver: v2.2.
changing. If there is a newer microcode, the patch_level will change.

I have
Code:
[    1.957941] microcode: microcode updated early to new patch_level=0x010000dc
but thats for my 10 year old Phenom II.
The important bit is the microcode updated early to new patch_level=
.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
bigbanana69
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jul 2017
Posts: 141
Location: Skopje

PostPosted: Tue Mar 19, 2019 6:28 pm    Post subject: Reply with quote

Yes, I read an article on wikipedia about radeon hd 8000 series where it says they are based on bonaire but they are improved.

I reinstalled the gentoo including the boniare firmware and now it doesn't shows firmware errors, but again it pauses at

clocksource: Switched to clocksource tsc

At least on the first boot. Nvm, works fine. Later I'll install the packages for desktop 17.0 x86 and xfce4.
_________________
You are not using computers if you are not using Gentoo.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum