Jump to content

dutch-master

Members
  • Content Count

    24
  • Joined

  • Last visited

About dutch-master

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. This could be useful for you? https://mtlynch.io/tinypilot/#how-to-build-your-own-tinypilot HTH!
  2. You may get satisfactory results when you emerge the mdadm package. JBOD is a "special" sort of RAID.
  3. As a non-coder I reckon gcc, make, libc, binutils and of course the kernel, most likely in that order. Plus any dependencies, obviously.
  4. You may want to start afresh with emerge --jobs=4 --load-average=2 --emptytree --with-bdeps=y -auDN @world Worked for me last time I got stuck. 🙂 Note: takes a long, long time on old(er) hardware! You may want to remove some large packages like the DE (Mate, Gnome, KDE) as well as mesa, xorg and similar to speed up the process.
  5. Apols, I hadn't checked, but I got the same results as you got: 404 😞 Alternatively, use the generic-64 stage3 file (it's there, I checked 😉 ) then change the cflags and chost entries in make.conf after rebooting into the actual system: CHOST="x86_64-pc-linux-gnu" CFLAGS="-march=amdfam10 -O2 -pipe" CPU_FLAGS="3dnow 3dnowext mmx mmxext popcnt sse sse2 sse3 sse4a" Then do a world update: emerge --jobs=4 --load-average=2 -auDN @world It may not be the "official" way, but at least it's a start 👍
  6. Have a go from this site: https://build.funtoo.org/1.4-release-std/x86-64bit/amd64-k10/ HTH!
  7. Managed to install lxd and everything that comes with it on my AMD k10 system (Phenom II X4 965 proc, 16GB RAM, 120GB SSD). Then I proceeded by getting the lxd image for k10 arch and set up lxd following the Wiki by DRobbins. but launching the testcontainer as per the instructions failed with an error. After some trial and continues errors I managed to get both the lxd-generic_64 and intel westmere images installed and associated with a testcontainer: # lxc list +---------------+---------+------+------+-----------+-----------+ | NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS
  8. Oh, apols, didn't catch that 😳
  9. Sorry to see you stop JFS support, as I use it pretty much exclusively. (not just Funtoo, but on my Devuan installs as well) At the time I choose JFS over XFS as the former had slightly better performance for small file storage, while being on par for large files. What does this mean though for JFS support in Funtoo? Will JFS remain an option to install on? Or is this just for a personal project you run?
  10. Did you sync your local repo with the online one? Do ego sync Then run the emerge command again.
  11. Could a dedicated fork for -bin packages be an option? A bit like a "Debianized Funtoo", just -bin packages to install. Great way to get going on older hardware! Case in point: my CPU dates from 2012-ish and I'm not in a position to upgrade to a Ryzen system any time soon. Building libreoffice-bin takes up a lot less time then libreoffice, which is often newer then the -bin package, but libreoffice-bin doesn't always build successfully whereas libreoffice usually succeeds. Other big packages like mesa, ffmpeg etc also eat enormous amounts if install time to get a fairly basic working desktop.
  12. Ah, many thanks again. I'll retrace my steps and see if I can get a working system this time 🙂 (crosses fingers!)
  13. Well, that didn't work. Blocked the 1.8 release globally in make.conf but the 1.4 version it wanted instead is no longer available. For some reason, the libvpx line was missing in funtoo-cautionary (at least on my system) so it wasn't blocked to start with from that layer. No idea where the blockage comes from then. As I was quite fed up by now, I tried reverting the 1.4 release back to 1.3 by first removing everything outside the core flavour, setting ego.conf back to 1.3, then deleting the existing package cache (and rebuilding it with ego sync) before running emerge -auDN @world
  14. Ah thanks, I wasn't aware there was a bug filed already (didn't think checking the bugs list). I'll have another go later.
  15. Reviving my attempts to install Funtoo 1.4, I've run into an issue with libvpx-1.9.0. This package is masked by package.mask but it is required for installing Mate. Several packages depend on libvpx, including ffmpeg, gst-plugins-[libav,meta], brasero and mate (meta-package) itself. Is there an alternative/workaround/fix for this? TIA!
×
×
  • Create New...