digifuzzy

I recall watching a talk about open source and the presenter used the phrase "bus factor equals one". I had similar situation at previous workplace. We kept asking "What happens if you get hit by bus?". After there were two deaths (1 unexplained and another a heart attack) of co-workers and a near-fatal heart attack all in the company in the span of about a year, our group switched it up to "What happens if you win the lottery?". The point? We have lots of really cool tools and piles of knowledge - is this knowledge spread around enough for others to keep going should @drobbins suddenly find he won a power ball lottery and is moving to a tropical island w/o computers? I just look at the FreeBSD ports collection or Gentoo repositories. All those indications of "unmaintained"... That should scare some people.

No, you're not. But we both learned something today... 😉

Hun...same here. I didn't notice that until I read through your post. I just double check my group file vs what is in the stage3 tarball used for install. They are both approximately the same (local has my user info added). Quick googlefu came up with this - https://www.systutorials.com/docs/linux/man/8-grpck/ I need to read more about the `groups` command for myself. You're not alone... ~Edit~ From man page (man groups): So just `groups` (at root prompt) will produce the first part of the list - or groups for current user. Using `groups root` prints that list as well as the duplicates. Try the same command as a normal user. You'll see similar duplication.

First thing that jumped to mind was the phrase "Xorg synaptics". I recall, when I had a laptop ages ago, that not having synaptic driver in xorg can cause havoc. A quick google brought this up - https://wiki.gentoo.org/wiki/Synaptics There is the later/newer libinput - https://wiki.gentoo.org/wiki/Libinput I'm not sure if these will solve your problems, but identify the need for the driver(correctly we hope) in /etc/portage/make.conf may pull in what you are missing. YMMV - https://forums.gentoo.org/viewtopic-t-1075806-start-0.html

You're not alone in this department. There's a direction...just not sure exactly to what destination.

100% loss is bad. Means card isn't talking. w/ ifconfig also ensure you don't see 169.x.x.x address. That's a "not connected" type address that NICs will assume if something isn't right. arp is good. Shows all external IP connections. Should see meaningful results.

Looks like you have a decent start. You've defined the two openrc init files net.eth0 and net.eth1. Let's make sure you have those running at startup (rc-update add net.eth{0,1}) WIth dual nic's, I ran into a host of issues with conflicts in dhcpcd service. It wants to overwrite, take charge of stuff. I agonized over this part until I found it by accident. So `rc-update del dhcpcd default` removed the service. I run my own LAN sever providing dhcp. The NIC talking to ISP box has net.eth file that just contains the line "template=dhcpcd" and that's it. I do other configuration on ISP box but generally it only uses ISP supplied dhcp. The other NIC(LAN w/ static IP for downstream for network service) is configured with base ip address w/ netmask as well as domain name. I then installed dhcpd (NOTE: different NOT DHCPCD - two different pieces of software) to manage LAN needs. In the `/etc/conf.d/dhcpd` file I have at the top `rc_need=net.ethX` where X is the LAN facing NIC. We tell openRC don't start the DHCP until you have this NIC card going. Also in the same file is the line `DHCPD_IFACE="ethX" (same as before). There's other dhcp and bind setup stuff... but you get the idea. The magic happens with `net-firewall/shorewall` - A nicer version of iptables. I used it's configuration to bridge the two NIC's. This occurs in its `/etc/shorwall/interfaces` who you marry up NIC to function one eth goes to WAN, other goes to LAN. And off to the races we go. Probably more information that you want. My suspicion is you have having issues with dhcpcd taking charge when you don't want it to. Disable the service and come back. We can go from there. BTW, IRC works too... 😉

Okay... that worked. <blink><blink> Added a 'display' section to /etc/boot.conf display { gfxmode 1024x768 } Executed `ego boot update`. Produced the desired result. @cardinal - just to clarify somethings in my head: a) /etc/boot.conf file surplants the /etc/default/grub file? Or rather, `boot-update` , or now `ego boot update` doesn't take settings from the /etc/default/grub file? (this would explain why changes to /etc/default/grub were not made to /boot/grub/grub.cfg and why grub-mkconfig made a mess of things but produced desired graphical output) b) This seems Funtoo specific...am I wrong? https://github.com/funtoo/boot-update/blob/master/doc/boot-update.8 answered this. Very much appreciate the insight you have given.

Wow! That's a really helpful tidbit! That never came up in Google searching. I must try this. News to follow.

Doing a fresh install of Funtoo into a virtualbox environment. Instructions followed carefully and subsequent install works well. Xorg has not been installed yet. From online search, grub2 has deprecated the use of 'vga=x' to change the console size. Recommended practice is to use the 'GRUB_GFXMODE=Horz X Vert' in the file /etc/default/grub. Change was mode locally to /etc/default/grub. Video mode was tested successfully from grub command line, 'videotest HorzXVert' as set in GRUB_GFXMODE. Neither 'boot update' nor the command, new that appeared in the install instructions, 'ego boot update' appears to affect whether GRUB_GFXMODE is being written. Is there some other action that needs to be taken?

You didn't see this in the original post?

Doing a fresh install into a virtualbox environment. Goal was to test cinnamon environment. All steps from Funtoo Install page were done without problem. "First Steps" done: include setting profiles and mix-ins. X-org install completed and tested (note use VMSVGA video - easiest without need of extra drivers). Attempt to install cinnamon fails with error stating "unmet requirements". Indications are that ebuild specifies python targets for python 3.4 and 3.5 but latest uses 3.6.6. A quick look at a couple of other cinnamon ebuilds show python 3.6 target in ebuild. Bug? Ebuild missed in updates? How best to resolve?

I just looked... Bug exists and was filed yesterday: https://bugs.funtoo.org/browse/FL-5932

I was getting "head detached" messages and had taken the nuclear option of removing the meta-repo folder( `rm -rf /var/git/meta-repo` ). While performing a sync, I observed the following message: # ego sync ... Syncing gnome-kit branch 3.26-prime Already on '3.26-prime' Your branch is up to date with 'origin/3.26-prime'. HEAD is now at 0bf7e35 Revert "FL-5907: move gexiv2 from gnome-kit" Already up to date. fatal: reference is not a tree: df17e1a16536abf02e5bf06fdfef14a2457e92bf ... ERROR: There was an error syncing gnome-kit. # Error message indicates to me a problem with a git tree reference. Maybe it's been already picked up by dev's but I thought it important to pass along.

...and now were going off topic. This problem is not getting resolved but devolving into something else. ....thread abandoned.