Jump to content

dutch-master

Members
  • Content Count

    29
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by dutch-master

  1. Linux, and Funtoo, are international. His (her?) native language (very likely) may not be English. Nor is mine 😉 It also means (s)he may not be aware of 'social rules' that govern (online) conversation in English. And even so, discussions on the web always miss a vital component in human interaction: non-verbal communication. Body-language. Smileys, and by extension emoticons, are a way to circumvent this, but generally do a poor job, TBH. To be frank, there is a valid point in his comments: not every Funtoo user is a coder. Not every Funtoo user wants to use Discord, let alone be
  2. I'm not on a Funtoo system (long story, don't bother) but IIRC you could do w/o the modemmanager package. emerge -aC modemmanager Note: this might break some packages, consider purging those as well, unless they're system-critical of course!
  3. Did you install the various firmware packages? (microcode, linux-firmware, etc) You'll probably need to reboot into a chroot environment with the external media method you've used to install Funtoo in the first place.
  4. As root, run fsck /dev/nvme0n1p1 Make sure you have the correct support package installed for the file system on that partition (probably VFAT)
  5. One more thing to consider: not everyone wants to use Discord.
  6. That's how I got my user to auto-login, but it didn't work, it went back to the greeter. Filling in my user and password didn't do anything, I just returned (again) to the greeter. Trying root instead made no difference (as it should, no GUI login for root!) Currently I have no graphics related packages installed (no Xorg nor Mate) and I can login from the cli w/o any problems. I wasn't aware of the init_opts option, thx for that 🙂
  7. Some time ago I got new hardware for my desktop, to replace what I currently run. Asus B450 Prime mainboard, AMD Ryzen 7 1700 (non-X!) and 2x 8GB RAM from Transend. For video I used an old nVidia GT710 card, as I won't be doing anything fancy like gaming on the machine anyway. I managed to get a base Funtoo system installed, eventually, using the first gen Zen stage3. But when expanding the install to a full desktop I got all kinds of issues. Following the install guides on the Funtoo Wiki I got Xorg and Mate to install. When I rebooted, I couldn't log in, despite setting Lightdm to auto-logi
  8. This could be useful for you? https://mtlynch.io/tinypilot/#how-to-build-your-own-tinypilot HTH!
  9. You may get satisfactory results when you emerge the mdadm package. JBOD is a "special" sort of RAID.
  10. As a non-coder I reckon gcc, make, libc, binutils and of course the kernel, most likely in that order. Plus any dependencies, obviously.
  11. 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.
  12. 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 👍
  13. Have a go from this site: https://build.funtoo.org/1.4-release-std/x86-64bit/amd64-k10/ HTH!
  14. 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
  15. Oh, apols, didn't catch that 😳
  16. 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?
  17. Did you sync your local repo with the online one? Do ego sync Then run the emerge command again.
  18. 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.
  19. Ah, many thanks again. I'll retrace my steps and see if I can get a working system this time 🙂 (crosses fingers!)
  20. 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
  21. 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.
  22. 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!
  23. Belated (attempted) answer: You can use 64-bit Linux on 2GB main-board systems. I happen to have a Shuttle All-in-one system with an Atom D525 as well and 64-bit Funtoo compiled fine. Takes a looooonngggg time, but it works.
  24. Welcome (a bit belated, but still 😉 ) Given that you currently have no working system, consider starting afresh with the Funtoo install-guide: https://www.funtoo.org/Install Don't try short-cuts, take it step-by-step. Keep your make.conf as clean as possible, likewise epro mix-ins. Alternatively, use emerge to remove all X-related packages from your current system. emerge -aG xorg-x11 xinit xdm emerge -a --depclean Let it finish, then reboot. Emerge uses a separate build-directory for each package, including log and build files. Any issues emerge runs into t
  25. The Wiki page on Mate (<- link!) stipulates it needs dbus as a prerequisite, so: rc-update add dbus default rc HTH!
×
×
  • Create New...