Jump to content
funtoo forums

cafaia

Members
  • Content count

    70
  • Joined

  • Last visited

  • Days Won

    7

cafaia last won the day on October 28 2017

cafaia had the most liked content!

1 Follower

About cafaia

  • Rank
    Advanced Member

Recent Profile Visitors

203 profile views
  1. Several problems on KDE-Plasma

    Hi, dear Silvio! Well, now who does not know, it's me. Unfortunately I give up... I suggest you do a new installation of Funtoo, in the face of all this seems to be the most correct thing to do. Big hug, Eduardo
  2. Several problems on KDE-Plasma

    Hi, Silvio! Yes, the "emerge grub" command should be with chroot and if you get error while running the "boot-update" command you should do this "emerge boot-update" and follow these steps: https://www.funtoo.org/Package:Boot-Update Big hug, Eduardo
  3. Several problems on KDE-Plasma

    Hi, Silvio! The first command is the correct command, the error is because you have not installed in Funtoo the Grub program. Then you will have to do these steps: # mkdir /mnt/funtoo # mount /dev/sdb3 /mnt/funtoo # mount /dev/sda2 /mnt/funtoo/boot/efi # cd /mnt/funtoo # mount -t proc none proc # mount --rbind /sys sys # mount --rbind /dev dev # cp /etc/resolv.conf /mnt/funtoo/etc/ # env -i HOME=/root TERM=$TERM /bin/chroot . bash -l # export PS1="(chroot) $PS1" (chroot) # ego sync (chroot) # emerge debian-sources (chroot) # emerge grub (chroot) # emerge @module-rebuild (chroot) # grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sdc (chroot) # boot-update (chroot) # exit # cd /mnt # umount -lR funtoo # reboot I put it more: "emerge grub". I believe that if you follow this you will have a bootable system. Big hug, Eduardo
  4. Several problems on KDE-Plasma

    Hi, Silvio! Yes, we'll have to make Funtoo bootable again and for that we will use a pendrive. After you boot with SystemRescueCD you should connect the pendrive (/dev/sdc) and follow these steps, assuming you only have two disks (/dev/sda and /dev/sdb) on your PC: # mkdir /mnt/funtoo # mount /dev/sdb3 /mnt/funtoo # mount /dev/sda2 /mnt/funtoo/boot/efi # cd /mnt/funtoo # mount -t proc none proc # mount --rbind /sys sys # mount --rbind /dev dev # cp /etc/resolv.conf /mnt/funtoo/etc/ # env -i HOME=/root TERM=$TERM /bin/chroot . bash -l # export PS1="(chroot) $PS1" (chroot) # ego sync (chroot) # emerge debian-sources (chroot) # emerge @module-rebuild (chroot) # grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sdc (chroot) # boot-update (chroot) # exit # cd /mnt # umount -lR funtoo # reboot After these steps you should start the PC by the pendrive that should not be disconnected. Try this and tell me the result, please. I'm happy to help and I would love to make everything work again! Big hug, Eduardo
  5. Several problems on KDE-Plasma

    Hi, Silvio! I believe you did not see my message because she is on page two of the forum. Did you find her now? In my opinion it would be very important to reinstall grub, for this I'll explain the output lsblk. This is the output of the lsblk command here without the attached pendrive: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465,8G 0 disk ├─sda1 8:1 0 2M 0 part ├─sda2 8:2 0 2G 0 part │ └─md1 9:1 0 2G 0 raid1 /boot └─sda3 8:3 0 463G 0 part └─md2 9:2 0 925,8G 0 raid0 ├─swsyho-swap 253:0 0 32G 0 lvm [SWAP] ├─swsyho-system 253:1 0 250G 0 lvm / └─swsyho-home 253:2 0 643,8G 0 lvm /home sdb 8:16 0 465,8G 0 disk ├─sdb1 8:17 0 2M 0 part ├─sdb2 8:18 0 2G 0 part │ └─md1 9:1 0 2G 0 raid1 /boot └─sdb3 8:19 0 463G 0 part └─md2 9:2 0 925,8G 0 raid0 ├─swsyho-swap 253:0 0 32G 0 lvm [SWAP] ├─swsyho-system 253:1 0 250G 0 lvm / └─swsyho-home 253:2 0 643,8G 0 lvm /home sdc 8:32 0 2,7T 0 disk └─sdc1 8:33 0 2,7T 0 part /hd sr0 11:0 1 1024M 0 rom sr1 11:1 1 1024M 0 rom And this is the output with the pendrive connected: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465,8G 0 disk ├─sda1 8:1 0 2M 0 part ├─sda2 8:2 0 2G 0 part │ └─md1 9:1 0 2G 0 raid1 /boot └─sda3 8:3 0 463G 0 part └─md2 9:2 0 925,8G 0 raid0 ├─swsyho-swap 253:0 0 32G 0 lvm [SWAP] ├─swsyho-system 253:1 0 250G 0 lvm / └─swsyho-home 253:2 0 643,8G 0 lvm /home sdb 8:16 0 465,8G 0 disk ├─sdb1 8:17 0 2M 0 part ├─sdb2 8:18 0 2G 0 part │ └─md1 9:1 0 2G 0 raid1 /boot └─sdb3 8:19 0 463G 0 part └─md2 9:2 0 925,8G 0 raid0 ├─swsyho-swap 253:0 0 32G 0 lvm [SWAP] ├─swsyho-system 253:1 0 250G 0 lvm / └─swsyho-home 253:2 0 643,8G 0 lvm /home sdc 8:32 0 2,7T 0 disk └─sdc1 8:33 0 2,7T 0 part /hd sdh 8:112 1 14,9G 0 disk └─sdh1 8:113 1 14,9G 0 part sr0 11:0 1 1024M 0 rom sr1 11:1 1 1024M 0 rom So the pendrive is what is different between one and another, in this case the device /dev/sdh. So in my case I would have to do "grub-install (parameters for the UEFI system) /dev/sdh", can you do this? Then you should choose the boot by the pendrive in bios... I'm rooting for you and I hope we can get it working again! Big hug, Eduardo
  6. Several problems on KDE-Plasma

    Hi, Silvio! I thought that SystemRescueCD had the driver nvidia, then we'll have to do something else, let's make Funtoo bootable again. For this you should do a chroot and reinstall the kernel and the necessary drivers with the commands: # emerge debian-sources # emerge @module-rebuild I do not use the UEFI system, but you should follow the steps in the Grub Funtoo installation manual, but this time we will install Grub on a USB drive, so you should connect one and see what device it is with the 'lsblk' command, and at the time of installing Grub you should replace the value of /dev/sda with the pendrive. You should then leave the pendrive connected to the PC and reboot, and choose this device (pen drive) as bootable. So you do not lose the installation of grub that accesses your other operating systems. Let's see if that works, because chroot is more for working only in text mode. Big hug, Eduardo
  7. Several problems on KDE-Plasma

    Hi, Silvio! Funtoo manuals are very well written and are slightly different from Gentoo, you did right to follow the Funtoo manual. We'll try to solve this mouse problem first. I believe it would be good for you to create an xorg.conf file with these commands: # Xorg -configure :5 # mv /root/xorg.conf.new /etc/X11/xorg.conf # nvidia-xconfig To test this setting file: # X -config /etc/X11/xorg.conf Try this and tell me how it went. Big hug, Eduardo
  8. Several problems on KDE-Plasma

    Hi, Silvio! Wow, the photo is very beautiful, it's a city I want to meet! This, if you encounter any problems when following the manual, here insert the error that I will be happy to help. One more question: do you have the services "dbus" and "consolekit" running? Maybe it is that... Anything is just calling, because the Funtoo community is here to help and welcome to the Funtoo community! Big hug, Eduardo
  9. Several problems on KDE-Plasma

    Hi, Bourbon! Now who does not know what to do is me, because the settings seem to be correct... I hope you find help in the manuals I sent you because I no longer have any idea what can be. You should try to follow the manual and if something goes wrong contact. I'm sorry but at the moment I do not know what to do. Big hug, Eduardo
  10. Several problems on KDE-Plasma

    Hi, Bourbon! I'm sorry you're in trouble. Your problems seem to be for lack of this command: # emerge -av --update --deep --newuse --changed-use --with-bdeps=y @world Because in funtoo the programs most of the time are dependencies of correct FLAGS/USES in master programs. For example: you should not install xf86-input-evdev with the command emerge, because this program must be installed with the parameter INPUT_DEVICES="evdev" in master program xorg-drivers. Could you send me the output of the command "emerge --info"? I advise you to read this, for me it helped: https://wiki.gentoo.org/wiki/Xorg https://wiki.gentoo.org/wiki/KDE I hope this helps you. Big hug, Eduardo
  11. Several problems on KDE-Plasma

    Hi, Bourbon! Well, to install again the kernel does not have much difficulty, is a process similar to the first steps of the installation. I advise you to use the Live CD SystemRescueCD and do this: # mkdir /mnt/funtoo # mount /dev/sda3 /mnt/funtoo # mkdir /mnt/funtoo/boot # mount /dev/sda1 /mnt/funtoo/boot # cd /mnt/funtoo # mount -t proc none proc # mount --rbind /sys sys # mount --rbind /dev dev # cp /etc/resolv.conf /mnt/funtoo/etc/ # env -i HOME=/root TERM=$TERM /bin/chroot . bash -l # export PS1="(chroot) $PS1" (chroot) # ego sync (chroot) # emerge debian-sources (chroot) # exit # cd /mnt # umount -lR funtoo # reboot I do not have UEFI so I do not know for sure how you should proceed, but the above commands I believe arrive. I read that the new debian kernel will have what is missing for you (CONFIG_SND_HDA_PREALLOC_SIZE=2048). I also love Brazil and my Italian blood. I'm glad you've visited my country. I have not yet visited Rio de Janeiro and neither Salvador, but I have great interest to visit these two cities. The Italian corals of Rio Grande do Sul are famous, because Rio Grande do Sul is the Brazilian state with the largest number of Italian immigrants. Big hug, Eduardo Coutinho Scalabrin P. S.: Excuses, but I do not have Facebook, but if I create one I'll look for you, okay?
  12. Several problems on KDE-Plasma

    Hi, bourbon! I'm glad I'm helping you and it's a pleasure to help you! But after you have put on /etc/portage/make.conf this: L10N="en-US it" LINGUAS="en_US it" did you run the command below as root? emerge -av --update --deep --newuse --changed-use --with-bdeps=y @world About your network, you should follow these commands: # cd /etc/init.d # ln -s netif.tmpl net.eth0 # rc-update add net.eth0 default # echo template=dhcpcd > /etc/conf.d/net.eth0 # echo 'rc_need="net.eth0"' >> /etc/conf.d/ntp-client # rc-update add ntpd default And you should disable the dhcpcd boot service, thus: # rc-update del dhcpcd default You edited the wrong files, the correct one is edit '/etc/conf.d/ntp-client' and not '/etc/init.d/ntp-client'. To cancel the old user, you must give this command: # userdel -f -r LOGIN It is not correct to edit the file '/etc/init.d/udev' because the error saying to user run script is harmless. I am from Brazil of the state of Rio Grande do Sul of the city of Frederico Westphalen. My great grandfather was Italian, he was from the Vicenza state of the city of Schio, my last name is Scalabrin. Big hug!
  13. Several problems on KDE-Plasma

    Hi, bourbon! I think I found your mistake. You must have this in your make.conf: L10N="en-US it" LINGUAS="en_US it" With best regards!
  14. Several problems on KDE-Plasma

    Hi, bourbon! I'm glad that I have helped! Let's go to the points with errors: - KDE is still 99% in English = NOT SOLVED. In your System Settings do you have something similar to this: I see that your configuration files are correct, I advise you to put this too in your .bash_profile: export LANG="it_IT.utf8" After that, I noticed two warnings at boot: - mdam = I don't remember what is wrong (red asterisk) - npd = (red asterisk) does'nt start at boot (I have been installing it because am in multiboot with Windows 10. It solved the time issue on Funtoo but still needing to fix manually on Windows when using it). The mdadm service is for raid, but it is not necessary if you have an image with the settings. I have raid and I do not have this service running. The ntpd service requires special network configurations, you should not use dhcpcd as a service. The correct service should be net.eth0 and you should have this in /etc/conf.d/ntp-client: rc_need="net.eth0" The time in your bios is in UTC? The time in my bios is three hours early. I advise you to copy the files from the external hd again, permission errors may occur. I hope I've helped! Big hug!
  15. Several problems on KDE-Plasma

    Hi, bourbon! I advise you to do this: # useradd -m -G lp,wheel,uucp,audio,cdrom,video,games,usb,users,plugdev,lpadmin,pulse-access,scanner -s /bin/bash master-test # passwd master-test Login with this new user and see if the error will occur. I hope I've helped!
×