Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

922 profile views

kindofblue's Achievements


Newbie (1/14)



  1. Thanks. I was thinking of doing that but I'm not in a hurry, I'll wait for the issue to be fixed. I raised a bug report, so hopefully someone will see it.
  2. That's where I went. Thanks anyway.
  3. I started installing Funtoo on an old PC with an AMD K10 processor but the link to the stage 3 file is broken (HTTP 404 error). Can someone fix this? Thanks in advance.
  4. The lvm flag didn't work for me. I still see the same messages at boot time as those I posted in my original message. At least I have a working kernel with the manual build of the kernel I described. Thanks again.
  5. Sorry I just saw your answer. I rebuilt the kernel with Device Mapper Support built in (instead of a module) and it's now working. I was not aware of the lvm use flag. I added it and I'm now emerging debian-sources-lts again. I'll let you know how it goes. Thanks a lot.
  6. Correction: the kernel parameter real_root in /etc/boot.conf is /dev/mapper/funtoo-ROOT.
  7. Hello everybody, I just installed Funtoo release 1.4 on an AMD K10 cpu; the kernel is debian-sources-lts version 4.19.67_p2-r1. I used LVM for all the file systems, including the root file system (I used the instructions in the following guide). I used the following kernel parameters in /etc/boot.conf (again from the guide mentioned above): dolvm real_root=/dev/funtoo/ROOT rootfstype=ext4 resume=swap:/dev/mapper/funtoo-SWAP. When booting I see the following messages: I have another box running Funtoo release 1.3 with version 4.19.37_p6 of the Debian kernel. I have the same setup on this one as the new one (using LVM for the root file system) and it works fine. There's differences in relation to LVM in the initramfs files of the two kernels. Here's what I see for version 4.19.37_p6: And only this for version 4.19.67_p2-r1 Could that explain the issue? Thanks in advance.
  8. Thanks to all for the replies. I'll upgrade to Funtoo 1.4 as soon as I can.
  9. I tried to build kde-plasma/plasma-meta on two different PCs but they both fail on the same package, sys-apps/accountsservice. The error message is that systemd is required. I added the nosystemd mix-in to my profile but that didn't help. I tried to blacklist the package in package.mask but emerge returns an error saying that it must be unmasked. Would someone know if there's a way to build this package without systemd? Thanks in advance.
  10. Thanks, but that shows the version of the kernel, which I think is not related to the Funtoo release version.
  11. Ok thanks. I see mostly 1.2-release when I run this command so I guess it means I'm running version 1.2. Would that explain why I don't get new updates?
  12. Here it is: denis@euclide(~)$ cat /etc/ego.conf # This is the ego.conf file [kits] # You can set your default kits here. Unset kits will use the Funtoo default prime/master # branch by default. # python-kit = 3.6-prime
  13. I haven't updated my Funtoo systems in a while and now when I run ego sync there's no new packages. I see that there are new releases of Funtoo (1.2, 1.3). Can someone please tell me how to see which release I'm running. Thanks.
  14. I am really sorry, I wasted your time all along. I sudoed to root on the MacBook and looked at the command history. I was root when I changed the profile. I wonder how I can work in that business and be sometimes so confused.
  15. If you read the documentation on profiles, for example here, it doesn't say root privilege is required. I'm only trying to change my own profile, not system wide. I use sudo to emerge. For the rest I set up the two PCs exactly the same way, except for the stage download. Thanks again.
  • Create New...