Jump to content
Read the Funtoo Newsletter: Summer 2023 ×

xsilentmurmurx

Members
  • Posts

    41
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by xsilentmurmurx

  1. On 3/6/2018 at 10:05 PM, xsilentmurmurx said:

    Hello all

    I recently installed Funtoo on my desktop computer and I would like to install and configure KVM so I can host VMs.  I installed Qemu and libvirt. What else do I have to do in terms of networking, and package installations, configurations etc, to be able to create, and host VMs on my Funtoo? 

     

    Thanks!

    I guess no body knows the answer?

  2. Hello all

    On the Funtoo FAQs, the following is stated:

     

    Quote

    We are planning to develop a new OpenRC-style init system, incorporating "next-gen" features, which will be comparable in functionality to systemd.

    What will these next-gen features consist of and is there any timeline for when this will be released? I am eager to see what new features will be in the new OpenRC.

     

    Thanks!

  3. 9 minutes ago, Oleg Vinichenko said:

    this particular problem should be fixed with update.

    most of management such as masks, unmasks, keywords should be just about the same as in Gentoo.

    thank you for your reply. I actually got this error after I did a full update of my system.   Also, where and what files should I edit for unmasking and masking files and adding/removing keywords?

     

     

  4. Hello all

     

    I used to play around with Gentoo like 8 years ago so my knowledge of all of this is rusty, but how does one  unmask a package or add/remove keywords from it? For example, I am trying to emerge xfce4-meta but I ran into this error:

    # emerge -av xfce4-meta
    
    These are the packages that would be merged, in order:
    
    Calculating dependencies... done!
    
    emerge: there are no ebuilds to satisfy ">=sys-devel/automake-1.16:1.16".
    (dependency required by "sys-apps/vbetool-1.1::nokit" [ebuild])
    (dependency required by "sys-power/pm-utils-1.4.1-r7::core-kit[amd64,-video_cards_intel]" [ebuild])
    (dependency required by "sys-power/upower-0.99.3-r1::gnome-kit[deprecated]" [ebuild])
    (dependency required by "xfce-base/xfce4-settings-4.13.1::xfce-kit[upower]" [ebuild])
    (dependency required by "xfce-base/xfce4-meta-4.12::xfce-kit" [ebuild])
    (dependency required by "xfce4-meta" [argument])

    In my old Gentoo days, I used to unmask automake so I could pull in the latest versions of it (I believe this is what I used to do ) but with Funtoo I am at totally lost when it comes to how to resolve these emerge errors.  Also, I was previously told in another post that if I was to emerge the latest version of LVM2, with out keywords, I will not run into the Openrc Init scripts to runlevels problem.  How do I go about emerging LVM2 with out keywords?  Are there any articles on this site that explain how to do these things?  Also, how relevant are Gentoo's articles to Funtoo?

     

    Thank you for all of your help!

  5. 17 hours ago, nrc said:

    Your log says "Greeter requests session Xsession".  It should say "Greeter requests session xfce".   If you have the session type indicator on your greeter screen then be sure that you have xfce selected.  If not then you probably need to adjust your lightdm settings to enable the session indicator or set the default session to xfce.

     

    I tried that, and the XFCE desktop still does not start up...   Here is my /etc/lightdm/lightdm.conf:

    https://paste.pound-python.org/show/PRPtuM1TZEGXtzin0i33/

    I added user-session=xfce4-session.  I do not know if its even correct lol   but the only thing that happens is a very very minimal xwm session starts but not the XFCE4 session

  6. 3 hours ago, cardinal said:
    
    epro show

    Do you have mix-ins: xfce

    If not

    
    # epro mix-in +xfce
    Verify its set:
    # epro show
    # emerge -avuDN @world

    Emerge  xsm:

    
    emerge -av xsm

    Check /var/log/lightdm/lightdm.log for more hints if login still fails.

    Yes I have the mix-ins for xfce and I ran emerge -avuDN @world and afterwards I reemerged xsm and I rebooted and logged in again, and still I do not see the XFCE desktop.   

     

    Here is a link to my /var/log/lightdm/lightdm.log : 

    https://paste.pound-python.org/show/aluHLGolO1K9e9worl91/

  7. 13 hours ago, cardinal said:

    Look for significant errors in ~/.xsession of the account your trying to log into.

     

    Thank you for your reply.  I saw the following error in the ~/.xsession-errors  file:

    /etc/X11/Sessions/Xsession: line 106: exec: xsm: not found

    I emerged xsm and now when I try to login using LightDM, I get a blank black screen. I dont get the XFCE desktop at all. 

  8. Hello all

     I emerged xorg-x11 and xfce4-meta and they installed just fine, I also emerged lightdm and configured my /etc/conf.d/xdm to use DISPLAYMANAGER="lightdm"

    but whenever I reboot my system, and LightDM comes up, I put in my username and password and instead of the XFCE desktop starting, LightDM starts up again and I have to relogin and this continues on and on and on.. How do I get xfce4 to start up ? 

  9. I fixed it!  I had misspelled my Volume Group name in /etc/boot.conf and when I fixed that and changed both my /etc/fstab and my /etc/boot.conf to the following:

    /etc/fstab:

    (chroot) livecd / # cat /etc/fstab
    # /etc/fstab: static file system information.
    #
    # The root filesystem should have a pass number of either 0 or 1.
    # All other filesystems should have a pass number of 0 or greater than 1.
    #
    # NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
    #
    # See the manpage fstab(5) for more information.
    #
    # <fs>                  <mountpoint>    <type>          <opts>          <dump/pass>
    
    /dev/sda1               /boot           ext2            noauto,noatime  1 2
    /dev/sda2               none            swap            sw              0 0
    /dev/mapper/VolGroup00-LogVol00 /       ext4            noatime         0 1
    #/dev/cdrom             /mnt/cdrom      auto            noauto,ro       0 0

    and my /etc/boot.conf to:

    (chroot) livecd / # cat /etc/boot.conf
    boot {
            generate grub
            default "Funtoo Linux genkernel" 
            timeout 3 
    }
    
    "Funtoo Linux" {
            kernel bzImage[-v]
    }
    
    "Funtoo Linux genkernel" {
            kernel kernel[-v]
            initrd initramfs[-v]
            params += dolvm real_root=/dev/mapper/VolGroup00-LogVol00 rootfstype=ext4 resume=swap:/dev/sda2 quiet
    } 
    

     

    It finally worked after I ran boot-update!  

     

    I recommend adding the following to the LVM install guide for funtoo:

    The real_root path for the root partition, in /etc/boot.conf, has to match the entry in /etc/fstab exactly in the same format. Also giving examples in the guide, will also help! Just a friendly suggestion :)

     

    Thank you for your help! Now onto rebooting the VM and seeing if it even boots!

  10. 1 hour ago, xsilentmurmurx said:

    Thank you for your reply. I just built the VM last night and it is a brand new installation. I can try to reemerge debian-sources again and see if that works.

    I emerged debian-sources and did boot-update again and I still get the same error..  I am lost as to how to fix this

     

    This is my /etc/fstab:

    (chroot) livecd / # cat /etc/fstab
    # /etc/fstab: static file system information.
    #
    # The root filesystem should have a pass number of either 0 or 1.
    # All other filesystems should have a pass number of 0 or greater than 1.
    #
    # NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
    #
    # See the manpage fstab(5) for more information.
    #
    # <fs>                  <mountpoint>    <type>          <opts>          <dump/pass>

    /dev/sda1               /boot           ext2            noauto,noatime  1 2
    /dev/sda2               none            swap            sw              0 0
    /dev/VolGroup00/LogVol00        /       ext4            noatime         0 1
    #/dev/cdrom             /mnt/cdrom      auto            noauto,ro       0 0

     

     

  11. 6 minutes ago, palica said:

    benefit is that you don't have to configure your own kernel. and you are getting a generic distribution kernel where most of the stuff should just work. If you have compiled your kernel in gentoo and know what you are doing then you can surely stick to the old habit.

    hdd space is cheap these days :)

    20GB is still huge for a kernel though.  Even Red Hat's kernel isnt that huge.  I am able to install a minimal installation of Red Hat on a 7 GB VM VHD

  12. 5 hours ago, jhan said:

    Have you looked at https://www.funtoo.org/LVM_Install_Guide ?

    There the / entry in fstab looks as follows:

    
    /dev/funtoo/ROOT                /                   ext4        noatime     0           1

    Notice the naming of the root entry? It seems that you should not use labels for LVM devices in fstab:

    "LVM snapshots can result in duplicate UUIDs and labels, so LVM logical volumes should always be identified by logical volume name (/dev/mapper/name)." (source https://wiki.debian.org/fstab#Defining_filesystems)

    Thank you for your reply.. I changed my /etc/fstab so it uses the logical volume name instead of the label and I still get the same error

  13. 5 hours ago, Oleg Vinichenko said:

    LABEL is actually not that boot-update directly using, it is kernel command line argument that is passed to kernel. 

    If you using prebuilt kernel from older installation, it's initramfs is not using --disklabel. It was fixed, but to get the fix, you need to do emerge debian-sources.

     

    Thank you for your reply. I just built the VM last night and it is a brand new installation. I can try to reemerge debian-sources again and see if that works.

  14. Well I saw this post:

    https://forums.funtoo.org/topic/927-boot-update-error-with-lvm/

    It mentions that the path for the LVM, in /etc/fstab and /etc/boot.conf have to be the same (i.e. if you have /dev/VolGroup00/LogVol00 in /etc/fstab, it should be the same in the /etc/boot.conf file)   I changed the entry in /etc/boot.conf to /dev/VolGroup00/LogVol00 but left the entire in /etc/fstab as LABEL="ROOT" and I got the same error.  How come boot-update will not accept the LABEL="ROOT" entry?

     

  15. Hello all

     

    I am installing a VM of Funtoo, using LVM, and I keep getting the following error after running boot-update after grub-install:

    (chroot) livecd / # boot-update
    
    boot-update 1.8.2 /
    Copyright 2009-2017 Funtoo Technologies
    
     [use option "-l" for license info, "-h" for help]
    
      * Generating config for grub...
    
    
      * NOTE: Detected MBR boot. Configuring for Legacy MBR booting.
      * ERR : (rootfstype=auto) - cannot find a valid / entry in /etc/fstab.
      * ERR : No matching kernels or boot entries found in /etc/boot.conf.
    
      * ERR : Did not complete successfully.

     

    My /etc/boot.conf was configured to look like this:

     

    (chroot) livecd / # cat /etc/boot.conf
    boot {
            generate grub
            default "Funtoo Linux genkernel" 
            timeout 3 
    }
    
    "Funtoo Linux" {
            kernel bzImage[-v]
    }
    
    "Funtoo Linux genkernel" {
            kernel kernel[-v]
            initrd initramfs[-v]
            params += dolvm real_root=/dev/mapper/VolGroup-LogVol00 rootfstype=ext4 resume=swap:/dev/sda2 quiet
    } 

     

    My /etc/fstab looks like this:

    (chroot) livecd / # cat /etc/fstab
    # /etc/fstab: static file system information.                                                                                                  
    #                                                                                                                                              
    # The root filesystem should have a pass number of either 0 or 1.                                                                              
    # All other filesystems should have a pass number of 0 or greater than 1.                                                                      
    #                                                                                                                                              
    # NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.                                                                     
    #                                                                                                                                              
    # See the manpage fstab(5) for more information.                                                                                               
    #                                                                                                                                              
    # <fs>                  <mountpoint>    <type>          <opts>          <dump/pass>                                                            
                                                                                                                                                   
    /dev/sda1               /boot           ext2            noauto,noatime  1 2                                                                    
    /dev/sda2               none            swap            sw              0 0                                                                    
    LABEL="ROOT"            /               ext4            noatime         0 1                                                                    
    #/dev/cdrom             /mnt/cdrom      auto            noauto,ro       0 0 

    LABEL="ROOT' is /dev/VolGroup00/LogVol00

    I have no idea what is going on and why I get the error I mentioned.  Also, someone should update the LVM Wiki page for Funtoo with up to date information

     

    All help is greatly appreciated! Thanks!

×
×
  • Create New...