Jump to content
funtoo forums

All Activity

This stream auto-updates     

  1. Yesterday
  2. Hi again, I tried to get a little further here and maybe I have some more useful information. When I delete udev and udev-trigger from sysinit via rc-update sddm starts and login screen comes up. Unfortunately without any devices like network, keyboard or mouse loaded. As soon as I switch on udev again there is 100% load caused by udev and if I start sddm same behaviour as before, the computer freezes and I can only reset it. Did a complete comilation of the system via @world without any problems, but still the same problem. Maybe someone got a hint where the issue comes from? Thanks in advance.
  3. Last week
  4. I figured it out. One is a slightly older build than the other. The debian-kernal lts had to have been compiled against different configs. The one with ipv6 is running 4.9.168_p1 and the one without 4.19.37_p6. I guess this is a bug. ipv6 was left out of the newer kernel.
  5. How can a machine be missing ipv6? Also, they're identical.
  6. Thanks. I did that. FL-6604 https://bugs.funtoo.org/projects/FL/issues/FL-6604
  7. OK, thanks for testing and reporting this. I should be able to fix it. If you have some time, can you report an official bug on bugs.funtoo.org and then I will reference it in the commit that fixes this issue. Thanks.
  8. I'm testing the new 1.4. My test system is an older laptop, MSI GX720, core2duo P8400 with a nvidia GT9600M video card. I started with a blank disk, installed the minimal 1.3 system from the latest stage3 (core2 subarch) and from there proceeded to upgrade to 1.4 as per instructions. I tried the nvidia driver first (gfxcard_nvidia) but it seems that there's no driver compatible with my video card. So then I switched to gfxcard_nouveau and I get an error emerging mesa-19.1.3. Everything else emerges fine but the last step, mesa, fails. I'm attaching an archive of logs. I think the issue is related to the following in build.log: . >>> Configuring source in /var/tmp/portage/media-libs/mesa-19.1.3-r1/work/mesa-19.1.3 ... meson /var/tmp/portage/media-libs/mesa-19.1.3-r1/work/mesa-19.1.3 /var/tmp/portage/media-libs/mesa-19.1.3-r1/work/mesa-19.1.3-build --buildtype release -Db_ndebug=if-release --libdir lib64 --localstatedir /var/lib --sharedstatedir /usr/share/mesa-19.1.3 --prefix /usr --wrap-mode nodownload --prefix=/usr --libdir=lib64 -Dplatforms=x11,drm,surfaceless -Ddri3=false -Ddri-drivers=swrast,nouveau -Dgallium-drivers=gallium-nouveau -Dgallium-extra-hud=false -Dgallium-vdpau=auto -Dgallium-xvmc=auto -Dgallium-omx=disabled -Dgallium-va=auto -Dgallium-xa=auto -Dgallium-nine=false -Dgallium-opencl=disabled -Dvulkan-drivers= -Dshader-cache=auto -Dshared-glapi=true -Dgles1=auto -Dgles2=auto -Dopengl=true -Dgbm=auto -Dglx=auto -Degl=auto -Dglvnd=true -Dasm=true -Dglx-read-only-text=false -Dllvm=true -Dvalgrind=false -Dlibunwind=false -Dlmsensors=false -Dbuild-tests=false -Dselinux=false -Dosmesa=classic -Dosmesa-bits=8 -Dswr-arches= -Dtools=glsl,nir,nouveau -Dxlib-lease=auto . . meson.build:21:0: [1;31mERROR:[0m Options "gallium-nouveau" are not in allowed choices: ", auto, kmsro, radeonsi, r300, r600, nouveau, freedreno, swrast, v3d, vc4, etnaviv, tegra, i915, svga, virgl, swr, panfrost, iris, lima" mesaerror.tar.bz2
  9. probably missing ipv6 connectivity on the second one
  10. Hi, no changes were made to boot.conf Can I check why udev is causing high load or can udev be stopped in any way?
  11. Please check if /etc/boot.conf got updated and nomodeset added. If so, this needs removed and ego boot updated re-ran, then a system reboot. Seems to be the Bug du jour.
  12. Hi there, I just did the update to 1.4 following the instructions. Finally after solving some dependency issues the system now compile without any problems. Unfortunately I can't start xdm anymore using sddm and KDE as DE. As soon as I start xdm the computer freezes and I can't do anything. I found out that the computer is still available by ssh and stuff like htop works, a reboot does not. I'm not sure if that is connected but udevd is generating 100% cpu load right after boot and dmesg gives me following message worker [5203] /devices/pci0000:40/0000:40:03.1/0000:41:00.0 is taking a long time [ 76.636036] elogind-daemon[6746]: New seat seat0. [ 76.637282] elogind-daemon[6746]: Watching system buttons on /dev/input/event1 (Power Button) [ 76.637337] elogind-daemon[6746]: Watching system buttons on /dev/input/event0 (Power Button) [ 76.754160] elogind-daemon[6746]: Watching system buttons on /dev/input/event17 (LOGITECH G110 G-keys Keypad) [ 76.766173] elogind-daemon[6746]: Watching system buttons on /dev/input/event19 (Gaming Keyboard G110) [ 76.776171] elogind-daemon[6746]: Watching system buttons on /dev/input/event14 (ROCCAT ROCCAT Kova Consumer Control) [ 76.787788] elogind-daemon[6746]: New session c1 of user xxxxx. [ 163.540917] elogind-daemon[6746]: New session c2 of user root. [ 188.079028] udevd[5156]: worker [5203] /devices/pci0000:40/0000:40:03.1/0000:41:00.0 timeout; kill it [ 188.079049] udevd[5156]: seq 2350 '/devices/pci0000:40/0000:40:03.1/0000:41:00.0' killed The kernel I use is a self generated 4.19.27-gentoo-r1 that worked before the update and should not be the problem I guess. I have added the gfx-card-nvidia mix-in since I'm using the NVIDIA drivers. Thanks in advance for any help.
  13. Seems complicated to me but I'll try, because I want to install liquorix kernel on my computer.
  14. You may need to modify your kernel build options to make sure that a module for your wifi chipset is being built. You may also need to check whether the module is being loaded or if there is other firmware or drivers for the chipset that need to be installed. https://wiki.gentoo.org/wiki/Kernel/Gentoo_Kernel_Configuration_Guide https://www.funtoo.org/Install#Wi-Fi
  15. Hi, I installed gentoo in vmware. /usr/src/linux/.config CONFIG_VMWARE_VSOCKETS=m CONFIG_VMWARE_BALLOON=m CONFIG_VMWARE_VMCI=m CONFIG_VMWARE_PVSCSI=y I changed them all to =y. CONFIG_VMWARE_VSOCKETS=y CONFIG_VMWARE_BALLOON=y CONFIG_VMWARE_VMCI=y CONFIG_VMWARE_PVSCSI=y This is because I don't know how to autoload kernel modules when it's started. I don't know if that is in /etc/conf.d/modules, because it's definitely not in /etc/modules.autoload.d/kernel-. File systems ---> <*> FUSE (Filesystem in Userspace) support [*] Network device support ---> [*] Ethernet driver support ---> (disable every driver but this) [*] AMD Devices <*> AMD PCNet32 PCI support Device Drivers ---> [*] Network device support ---> <*> VMware VMXNET3 ethernet driver # lsmod Module Size Used by vmw_vsock_vmci_transport 32768 2 vsock 36864 3 vmw_vsock_vmci_transport I don't understand why it shows up as .ko if I didn't specify it like '<M>'. # find /lib/modules/`uname -r` -name '*.ko' /lib/modules/5.1.3-gentoo/kernel/drivers/thermal/intel/x86_pkg_temp_thermal.ko /lib/modules/5.1.3-gentoo/kernel/fs/efivarfs/efivarfs.ko /lib/modules/5.1.3-gentoo/kernel/net/vmw_vsock/vmw_vsock_vmci_transport.ko /lib/modules/5.1.3-gentoo/kernel/net/vmw_vsock/vsock.ko /lib/modules/5.1.3-gentoo/kernel/net/vmw_vsock/vsock_diag.ko /lib/modules/5.1.3-gentoo/kernel/net/ipv4/netfilter/iptable_nat.ko /lib/modules/5.1.3-gentoo/kernel/net/ipv4/netfilter/nf_log_arp.ko /lib/modules/5.1.3-gentoo/kernel/net/ipv4/netfilter/ipt_MASQUERADE.ko /lib/modules/5.1.3-gentoo/kernel/net/ipv4/netfilter/nf_log_ipv4.ko /lib/modules/5.1.3-gentoo/kernel/net/netfilter/xt_addrtype.ko /lib/modules/5.1.3-gentoo/kernel/net/netfilter/xt_nat.ko /lib/modules/5.1.3-gentoo/kernel/net/netfilter/xt_mark.ko /lib/modules/5.1.3-gentoo/kernel/net/netfilter/xt_LOG.ko /lib/modules/5.1.3-gentoo/kernel/net/netfilter/nf_log_common.ko /lib/modules/5.1.3-gentoo/kernel/net/ipv6/netfilter/nf_log_ipv6.ko # rc-update binfmt | boot bootmisc | boot cgroups | sysinit consolekit | default dbus | default devfs | sysinit dmesg | sysinit elogind | boot fsck | boot hdparm | default hostname | boot hwclock | boot keymaps | boot killprocs | shutdown kmod-static-nodes | sysinit local | default nonetwork localmount | boot loopback | boot modules | boot mount-ro | shutdown mtab | boot netmount | default opentmpfiles-dev | sysinit opentmpfiles-setup | boot procfs | boot root | boot save-keymaps | boot save-termencoding | boot savecache | shutdown sshd | default swap | boot sysctl | boot sysfs | sysinit syslog-ng | default termencoding | boot udev | sysinit udev-trigger | sysinit urandom | boot vmware-tools | default Even though it works until drag'n' drop, copy/paste is quite unstable, sometimes it works and sometimes it doesn't. I guess if I specify '<*>' then I don't need to add anything to the /etc/conf.d/modules file, because I did not build the driver as a module, I built it directly into the kernel.
  16. Earlier
  17. Maybe you should add not only pt but the correct name of the keymap as well. Looking at the available pt keymaps: sicota@farout /data/incoming $ find /usr/share/keymaps/ -name "*pt*" /usr/share/keymaps/i386/olpc/pt-olpc.map.gz /usr/share/keymaps/i386/qwerty/pt-latin9.map.gz /usr/share/keymaps/i386/qwerty/pt-latin1.map.gz /usr/share/keymaps/mac/all/mac-pt-latin1.map.gz sicota@farout /data/incoming $ I would suggest to use something like pt-latin1 instead of pt.
  18. Two machines identically configured. On one, netstat returns tcp 0 0* LISTEN tcp 0 0* LISTEN tcp 0 0* LISTEN tcp 0 0* LISTEN tcp 0 0* LISTEN tcp6 0 0 :::33060 :::* LISTEN tcp6 0 0 :::80 :::* LISTEN tcp6 0 0 :::22 :::* LISTEN tcp6 0 0 :::443 :::* LISTEN On the other, tcp 0 0 localhost:mysql* LISTEN tcp 0 0* LISTEN tcp 0 0 localhost:9000* LISTEN Why is Apache showing up in one and not the other? More generally, why does one list IPv6 connectivity and the other not?
  19. I remember running into this a few years ago. There is an environment variable that can be set that sometimes works: https://wiki.archlinux.org/index.php/Dwm#Fixing_misbehaving_Java_applications _JAVA_AWT_WM_NONREPARENTING=1 This is supposed to tell AWT to behave under a non-reparenting WM, such as dwm. Drop that into a file under /etc/env.d, and then run env-update.
  20. But I got other issue, I have no wi-fi access anymore. It seems like some time ago when I tried to install liquorix kernel by an overlay. But this time I'm using the default debian sources kernel that got updated when I updated @world. After the update I did run genkernel all because I thought that the X server problem was because kernel configuration. Although if I choose the older kernel on GRUB's init I can get access to wi-fi.
  21. Yuup!! It solved my issue. Thank you so much! :><333
  22. Hi, I just installed Funtoo on Virtualbox VM, but I'm having trouble changing the keymap. What I've done: 1 - nano /etc/conf.d/keymaps changed the keymap from "us" to "pt". 2 - rc-update add keymaps boot rc-update: keymaps already installed in runlevel `boot' ; skipping 3 - rc-service keymaps restart "* WARNING! you are stopping a boot service * Setting keyboard mode [UTF-8] .. * Loading key mappings [pt] ... cannot open file pt" Any help would be greatly appreciated.
  23. most likely /etc/boot.conf got updated and nomodeset got added please remove the nomodeset and run ego boot update then reboot your box. hopefully all will be well then 🙂
  24. I did emerge -auDN @world and I got a list of new packages to be installed and others to be reinstalled. I saw that xorg-server should be updated, bringing some other dependecies with it. After the world update I did reboot my notebook. On the initiation of OpenRC I realized that the letters on the screen did not become small (as it usually does) and when I tried startx I got: I suspect about flags of xorg-server and flags of its dependencies, but I'm not sure about that. Can anybody help me with this issue?
  25. Basicly this problem is because I use dwm, which is a tiled widow manager, which means that it doesn't work well with Java. I tried "man dwm" and at the end of the manual I saw a note about this issue with Java.
  26. I am just curious - what is the manual effort that Daniel and team perform? It seems there is some testing around that, can that by automated is what I'm getting at? Why can't there be rolling releases? I'm not complaining about the release process, but am trying to understand when the infra team prepares 1.3 or 1.4, what are they doing? Why must they do it by hand? I understand that Funtoo packages is a collection of software all developed at a different pace and that ebuilds have to be maintained to keep up with those packages. I'm looking for, how can we improve infrastructure to make this process better, more robust, etc.
  1. Load more activity
  • Create New...