Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED] RPI 4 and LXDE
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on ARM
View previous topic :: View next topic  
Author Message
ROGA
Tux's lil' helper
Tux's lil' helper


Joined: 17 Feb 2018
Posts: 108
Location: Zurich, Switzerland

PostPosted: Sat Feb 15, 2020 8:06 am    Post subject: [SOLVED] RPI 4 and LXDE Reply with quote

I installed LXDE on my RPI 4 but unfortunately LXDE won't start. I don't known how I can find the reason why my LXDE won't start.

This is my Xorg.0.log

Code:
[   196.611].
X.Org X Server 1.20.6
X Protocol Version 11, Revision 0
[   196.612] Build Operating System: Linux 5.4.3-v8+ aarch64 Gentoo
[   196.612] Current Operating System: Linux raspi4 5.4.3-v8+ #2 SMP PREEMPT Fri Dec 27 22:49:14 CET 2019 aarch64
[   196.612] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 cma=64M cma=256M video=HDMI-A-1:1680x1050M@60,margin_left=0,margin_right=0
[   196.612] Build Date: 15 February 2020  08:32:15AM
[   196.612]..
[   196.612] Current version of pixman: 0.38.4
[   196.612] <->Before reporting problems, check http://wiki.x.org
<------>to make sure that you have the latest version.
[   196.612] Markers: (--) probed, (**) from config file, (==) default setting,
<------>(++) from command line, (!!) notice, (II) informational,
<------>(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   196.612] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Feb 15 09:03:41 2020
[   196.613] (==) Using config directory: "/etc/X11/xorg.conf.d"
[   196.613] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   196.613] (==) No Layout section.  Using the first Screen section.
[   196.613] (==) No screen section available. Using defaults.
[   196.613] (**) |-->Screen "Default Screen Section" (0)
[   196.613] (**) |   |-->Monitor "<default monitor>"
[   196.613] (==) No monitor specified for screen "Default Screen Section".
<------>Using a default monitor configuration.
[   196.613] (==) Automatically adding devices
[   196.613] (==) Automatically enabling devices
[   196.613] (==) Automatically adding GPU devices
[   196.613] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   196.614] (WW) The directory "/usr/share/fonts/misc/" does not exist.
[   196.614] <->Entry deleted from font path.
[   196.614] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[   196.614] <->Entry deleted from font path.
[   196.614] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[   196.614] <->Entry deleted from font path.
[   196.614] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[   196.614] <->Entry deleted from font path.
[   196.614] (WW) The directory "/usr/share/fonts/100dpi/" does not exist.
[   196.614] <->Entry deleted from font path.
[   196.614] (WW) The directory "/usr/share/fonts/75dpi/" does not exist.
[   196.614] <->Entry deleted from font path.
[   196.614] (==) FontPath set to:
<------>
[   196.614] (==) ModulePath set to "/usr/lib64/xorg/modules"
[   196.614] (II) The server relies on udev to provide the list of input devices.
<------>If no devices become available, reconfigure udev or disable AutoAddDevices.
[   196.614] (II) Loader magic: 0x556285fce0
[   196.614] (II) Module ABI versions:
[   196.614] <->X.Org ANSI C Emulation: 0.4
[   196.614] <->X.Org Video Driver: 24.0
[   196.614] <->X.Org XInput driver : 24.1
[   196.614] <->X.Org Server Extension : 10.0
[   196.615] (--) using VT number 1

[   196.615] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[   196.616] (II) no primary bus or device found
[   196.616] (II) LoadModule: "glx"
[   196.617] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[   196.619] (II) Module glx: vendor="X.Org Foundation"
[   196.619] <->compiled for 1.20.6, module version = 1.0.0
[   196.619] <->ABI class: X.Org Server Extension, version 10.0
[   196.619] (==) Matched modesetting as autoconfigured driver 0
[   196.619] (==) Matched fbdev as autoconfigured driver 1
[   196.619] (==) Assigned the driver to the xf86ConfigLayout
[   196.619] (II) LoadModule: "modesetting"
[   196.619] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[   196.620] (II) Module modesetting: vendor="X.Org Foundation"
[   196.620] <->compiled for 1.20.6, module version = 1.20.6
[   196.620] <->Module class: X.Org Video Driver
[   196.620] <->ABI class: X.Org Video Driver, version 24.0
[   196.620] (II) LoadModule: "fbdev"
[   196.620] (WW) Warning, couldn't open module fbdev
[   196.620] (EE) Failed to load module "fbdev" (module does not exist, 0)
[   196.620] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   196.625] (WW) Falling back to old probe method for modesetting
[   196.625] (EE) open /dev/dri/card0: No such file or directory
[   196.625] (WW) Falling back to old probe method for modesetting
[   196.625] (EE) open /dev/dri/card0: No such file or directory
[   196.625] (EE) No devices detected.
[   196.625] (EE).
Fatal server error:
[   196.625] (EE) no screens found(EE).
[   196.625] (EE).
Please consult the The X.Org Foundation support.
<------> at http://wiki.x.org
 for help..
[   196.625] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   196.625] (EE).
[   196.634] (EE) Server terminated with error (1). Closing log file.


anybody got an idea?
_________________
regards,

Roland


Last edited by ROGA on Thu Feb 20, 2020 1:52 pm; edited 1 time in total
Back to top
View user's profile Send private message
xaviermiller
Administrator
Administrator


Joined: 23 Jul 2004
Posts: 8503
Location: ~Brussels - Belgique

PostPosted: Sat Feb 15, 2020 2:01 pm    Post subject: Reply with quote

Moved from Desktop Environments to Gentoo on ARM.
_________________
Kind regards,
Xavier Miller
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 15995

PostPosted: Sat Feb 15, 2020 4:17 pm    Post subject: Reply with quote

That looks to me like a more general problem with X not working. Was X working correctly before you tried to install LXDE?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Sat Feb 15, 2020 4:34 pm    Post subject: Reply with quote

ROGA,

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

That says that you have a bit missing from your kernel.

Code:
raspi4 5.4.3-v8+
looks almost but not quite like the Pi Foundation kernel.
That suggests that you started with bcm2711_defconfig and took a bit out that you need.
_________________
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
ROGA
Tux's lil' helper
Tux's lil' helper


Joined: 17 Feb 2018
Posts: 108
Location: Zurich, Switzerland

PostPosted: Sun Feb 16, 2020 10:01 am    Post subject: Reply with quote

@HU

I don't known if X was working correctly. How could I test this?

@NeddySeagoon

Yes, I have installed the Pi Foundation kernel from the Git-hub repository and had started with bcm2711_defconfig. But I didn't took a bit out of this config.


I cross compiled the kernel on my pc with:

Code:
ARCH=arm64 CROSS_COMPILE=aarch64-unknown-linux-gnu- make bcm2711_defconfig


then modyfied only the Power-Settings:

Code:
ARCH=arm64 CROSS_COMPILE=aarch64-unknown-linux-gnu- make menuconfig


and changed the value

Code:
CPU Power Management –> CPU Frequency scaling –> Default CPUFreq governor (powersave) –>


to

Code:
CPU Power Management –> CPU Frequency scaling –> Default CPUFreq governor (Ondemand) –>


after that I compiled the kernel

Code:
ARCH=arm64 CROSS_COMPILE=aarch64-unknown-linux-gnu- make -j8


What do you think now, would be false in my config?
_________________
regards,

Roland
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Sun Feb 16, 2020 10:21 am    Post subject: Reply with quote

ROGA,

That's completely correct.

Can you put the dmesg onto a pastebin site please?
wgetpaste can help.

What do you have in your /boot/config.txt?
_________________
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
ROGA
Tux's lil' helper
Tux's lil' helper


Joined: 17 Feb 2018
Posts: 108
Location: Zurich, Switzerland

PostPosted: Sun Feb 16, 2020 3:18 pm    Post subject: Reply with quote

Hi NeddySeagoon,

here is my dmesg

and my config.txt

Code:
# Pi 4 64 Bit Kernel waehlen

#kernel=kernel-4.19.88-v8+
kernel=kernel-5.4.2-v8+


# Wir sollten wirklich unseren eigenen Geaetebaum verwenden
# da es Verwechslungen zwischen 32- und 64-Bit Varianten gibt

#device_tree=bcm2711-rpi-4-b_64_kernel-4.19.88-v8+.dtb
device_tree=bcm2711-rpi-4-b_64_kernel-5.4.2-v8+.dtb


# Einstellung des 64-Bit Modus
arm_64bit=1
enable_gic=1
armstub=armstub8-gic.bin

# have a properly sized image
disable_overscan=1

# lets have the VC4 hardware accelerated video
dtoverlay=vc4-kms-v3d
dtparam=i2c_arm=on
dtparam=spi=on
dtparam=audio=on

# fuer Ton ueber HDMI
hdmi_drive=2
hdmi_force_hotplug=1

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

# gpu_mem is for closed-source driver only; since we are only using the
# open-source driver here, set low
gpu_mem=128


hope, it helps :wink:
_________________
regards,

Roland
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Sun Feb 16, 2020 4:31 pm    Post subject: Reply with quote

ROGA,

Your dmesg is missing lines related to the vc4drmfb frame buffer device
Code:
[   13.363977] vc4-drm soc:gpu: fb0: vc4drmfb frame buffer device

That's required to use the modesetting driver in Xorg.

Please put your kernel .config file onto a pastebin.
As your dmesg is missing all traces of vc4drmfb, I suspect its been accidentality turned off in your kernel.

The option to check is
Code:
CONFIG_DRM_VC4=m

_________________
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
ROGA
Tux's lil' helper
Tux's lil' helper


Joined: 17 Feb 2018
Posts: 108
Location: Zurich, Switzerland

PostPosted: Mon Feb 17, 2020 5:06 am    Post subject: Reply with quote

Hello NeddySeagoon,

so here is my .config file

I looked in the .config file for this option and it was already turned on. Why does my kernel not recognize the vc4 device?
_________________
regards,

Roland
Back to top
View user's profile Send private message
ROGA
Tux's lil' helper
Tux's lil' helper


Joined: 17 Feb 2018
Posts: 108
Location: Zurich, Switzerland

PostPosted: Mon Feb 17, 2020 12:52 pm    Post subject: Reply with quote

Hi NeddySeagoon,

I did make a new config file directly on my raspi 4 and compiled it there. The difference between the two .config files are this:


Code:
raspi4 ~ # diff /usr/src/linux/.config /usr/src/linux/.config.old -y --suppress-common-lines
CONFIG_CHECKPOINT_RESTORE=y                                   | # CONFIG_CHECKPOINT_RESTORE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set            | CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y                        | # CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set
CONFIG_FB_UVESA=m                                             | # CONFIG_FB_UVESA is not set
CONFIG_PROC_CHILDREN=y                                        | # CONFIG_PROC_CHILDREN is not set
CONFIG_CRYPTO_USER_API_HASH=m                                 | # CONFIG_CRYPTO_USER_API_HASH is not set


looks a little bit strange to me :roll: because this settings are opposites and I don't remember, that I changed this on my own.

After compiling, dmesg shows me this:

Code:
raspi4 ~ # dmesg | grep vc4
[    3.686428] debugfs: Directory 'fe902000.hdmi' with parent 'vc4-hdmi' already present!
[    3.687306] vc4_hdmi fe902000.hdmi: vc4-hdmi-hifi <-> fe902000.hdmi mapping ok
[    3.687318] vc4_hdmi fe902000.hdmi: ASoC: no DMI vendor name!
[    3.690077] vc4-drm soc:gpu: bound fe902000.hdmi (ops vc4_hdmi_ops [vc4])
[    3.690198] vc4-drm soc:gpu: bound fe806000.vec (ops vc4_vec_ops [vc4])
[    3.690310] vc4-drm soc:gpu: bound fe004000.txp (ops vc4_txp_ops [vc4])
[    3.690393] vc4-drm soc:gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])
[    3.690801] vc4-drm soc:gpu: bound fe206000.pixelvalve (ops vc4_crtc_ops [vc4])
[    3.691012] vc4-drm soc:gpu: bound fe207000.pixelvalve (ops vc4_crtc_ops [vc4])
[    3.691216] vc4-drm soc:gpu: bound fe807000.pixelvalve (ops vc4_crtc_ops [vc4])
[    3.691229] fb0: switching to vc4drmfb from simple
[    3.692090] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 1
[    8.801101] vc4-drm soc:gpu: fb0: vc4drmfb frame buffer device



It seems to be that now the kernel can see the vc4 device but unfortunately my journal-log looks very ugly


Code:
Feb 17 13:32:55 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:32:55 raspi4 systemd[1]: Started Load/Save Random Seed.
Feb 17 13:32:55 raspi4 systemd[1]: Started OpenSSH server daemon.
Feb 17 13:32:55 raspi4 systemd[1]: Started Permit User Sessions.
Feb 17 13:32:55 raspi4 systemd[1]: Started LXDE Display Manager.
Feb 17 13:32:55 raspi4 systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
Feb 17 13:32:55 raspi4 sshd[219]: Server listening on 0.0.0.0 port 22.
Feb 17 13:32:55 raspi4 sshd[219]: Server listening on :: port 22.
Feb 17 13:32:55 raspi4 systemd-logind[220]: New seat seat0.
Feb 17 13:32:55 raspi4 systemd-logind[220]: Watching system buttons on /dev/input/event1 (Logitech K520)
Feb 17 13:32:55 raspi4 systemd[1]: Started Login Service.
Feb 17 13:32:55 raspi4 systemd[1]: Reached target Multi-User System.
Feb 17 13:32:55 raspi4 systemd[1]: Reached target Graphical Interface.
Feb 17 13:32:55 raspi4 systemd[1]: Startup finished in 1.712s (kernel) + 3.317s (userspace) = 5.029s.
Feb 17 13:32:56 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:32:56 raspi4 kernel: broken atomic modeset userspace detected, disabling atomic
Feb 17 13:32:57 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:32:58 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:32:59 raspi4 systemd-networkd[128]: eth0: Gained carrier
Feb 17 13:32:59 raspi4 kernel: bcmgenet fd580000.genet eth0: Link is Up - 1Gbps/Full - flow control off
Feb 17 13:32:59 raspi4 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Feb 17 13:32:59 raspi4 systemd-networkd[128]: eth0: DHCPv4 address 192.168.241.105/24 via 192.168.241.1
Feb 17 13:32:59 raspi4 systemd-timesyncd[208]: Network configuration changed, trying to establish connection.
Feb 17 13:33:58 raspi4 systemd-timesyncd[208]: Synchronized to time server for the first time 192.168.241.1:123 (192.168.241.1).
Feb 17 13:33:58 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:33:58 raspi4 kernel: Console: switching to colour frame buffer device 90x30
Feb 17 13:33:58 raspi4 kernel: vc4-drm soc:gpu: fb0: vc4drmfb frame buffer device
Feb 17 13:33:59 raspi4 systemd[1]: systemd-rfkill.service: Succeeded.
Feb 17 13:33:59 raspi4 systemd-networkd[128]: eth0: Gained IPv6LL
Feb 17 13:34:00 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:34:01 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:34:02 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:34:03 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:34:04 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:34:05 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:34:06 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:34:07 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:34:08 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:34:09 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:34:11 raspi4 systemd-networkd[128]: eth0: Configured
Feb 17 13:34:19 raspi4 kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:182:crtc-2] flip_done timed out
Feb 17 13:34:29 raspi4 kernel: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:182:crtc-2] flip_done timed out
Feb 17 13:34:40 raspi4 kernel: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CONNECTOR:47:Composite-1] flip_done timed o>
Feb 17 13:34:50 raspi4 kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:182:crtc-2] flip_done timed out
Feb 17 13:34:50 raspi4 dbus-daemon[252]: [session uid=0 pid=250] Activating service name='org.a11y.Bus' requested by ':1.0' (uid=0 pid=241 comm="/>
Feb 17 13:34:50 raspi4 dbus-daemon[252]: [session uid=0 pid=250] Activating service name='org.gtk.vfs.Daemon' requested by ':1.1' (uid=0 pid=254 c>
Feb 17 13:34:51 raspi4 dbus-daemon[252]: [session uid=0 pid=250] Successfully activated service 'org.gtk.vfs.Daemon'
Feb 17 13:34:51 raspi4 dbus-daemon[252]: [session uid=0 pid=250] Successfully activated service 'org.a11y.Bus'
Feb 17 13:34:51 raspi4 org.a11y.Bus[252]: dbus-daemon[263]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=0 pid=241 c>
Feb 17 13:34:51 raspi4 org.a11y.Bus[252]: dbus-daemon[263]: Successfully activated service 'org.a11y.atspi.Registry'
Feb 17 13:34:51 raspi4 org.a11y.Bus[252]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Feb 17 13:34:51 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:34:52 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:34:53 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:34:54 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:34:55 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out
Feb 17 13:35:01 raspi4 kernel: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:182:crtc-2] flip_done timed out
Feb 17 13:35:06 raspi4 kernel: i2c-bcm2835 fe805000.i2c: i2c transfer timed out


I don't find any information with google, that can explain me this behavior.

Any idea?
_________________
regards,

Roland
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Mon Feb 17, 2020 1:40 pm    Post subject: Reply with quote

ROGA,

Here's the kernel and related files that I use.

You must not rename the directory inside 5.4.3-v8+.tbz2 as thats the kernels modules.
Everything else goes into boot.

Your
Code:
[    3.691229] fb0: switching to vc4drmfb from simple
[    3.692090] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 1
[    8.801101] vc4-drm soc:gpu: fb0: vc4drmfb frame buffer device
says that your DRM is fixed now.

Wild thought ... do you run ntpd to set the Pi clock as soon as its gets a network connection?
If not, and your time steps backwards, make will get confused. Builds may succeed but will often be incomplete or broken.
Time must be monotonic. It need not be correct but it must never go backwards.
_________________
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
ROGA
Tux's lil' helper
Tux's lil' helper


Joined: 17 Feb 2018
Posts: 108
Location: Zurich, Switzerland

PostPosted: Mon Feb 17, 2020 2:33 pm    Post subject: Reply with quote

Hi NeddySeagoon,

Thank you very much! With your newer kernel version everythings works greate now!

Quote:
do you run ntpd to set the Pi clock as soon as its gets a network connection?


Yes, I did. I had configure ntpd with timedatectl from systemd.

It would be great to know, why my kernel configuration not proper was running. Where was the error?
_________________
regards,

Roland
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Mon Feb 17, 2020 3:47 pm    Post subject: Reply with quote

ROGA,

My kernel config is in /proc/config.gz. You will need to modprobe the module to get it.
Compare my kernel config with yours.
_________________
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
ROGA
Tux's lil' helper
Tux's lil' helper


Joined: 17 Feb 2018
Posts: 108
Location: Zurich, Switzerland

PostPosted: Tue Feb 18, 2020 5:44 am    Post subject: Reply with quote

Hi NeddySeagoon,

Has to find your kernel config in /proc ? I don't have found a config.gz there.
_________________
regards,

Roland
Back to top
View user's profile Send private message
ROGA
Tux's lil' helper
Tux's lil' helper


Joined: 17 Feb 2018
Posts: 108
Location: Zurich, Switzerland

PostPosted: Tue Feb 18, 2020 5:56 am    Post subject: Reply with quote

Ok, NeddySeagoon,

I was asking google for "linux get config.gz modprobe" and found the solution.

with

Code:
modprobe configs


I get now the /proc/config.gz :lol:

You never stop learning
_________________
regards,

Roland
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on ARM 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