Jump to content
funtoo forums

digifuzzy

Members
  • Content Count

    156
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by digifuzzy

  1. 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
  2. You're not alone in this department. There's a direction...just not sure exactly to what destination.
  3. 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.
  4. 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... ?
  5. 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.
  6. Wow! That's a really helpful tidbit! That never came up in Google searching. I must try this. News to follow.
  7. 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?
  8. You didn't see this in the original post?
  9. 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?
  10. I just looked... Bug exists and was filed yesterday: https://bugs.funtoo.org/browse/FL-5932
  11. 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.
  12. ...and now were going off topic. This problem is not getting resolved but devolving into something else. ....thread abandoned.
  13. Please correlate this statement to the instructions I was given from palica above. Then detail how you would peel back the non-working kernel, please.
  14. @palica - I'm trying not to confuse the descriptions here. The desktop box(w/ Artix) is a separate machine. I included it's config as I thought it would be helpful comparison because it is not exhibiting the behaviour as the Funtoo box. I built the genkernel on Funtoo via SSH. Quite certain I followed the instructions you gave me accurately. It just didn't work. Cleaning up afterwards was messy - not up on all the details of kernel handling. Ended up un-merging and re-merging debian-sources. Made me appreciate what the folks at SystemRescueCD have done even more. I'm not sure what you're asking me to do next.
  15. @palica - didn't work. Problem persisted after the reboot. Unable to upload config file to message board. Pastebin link - https://pastebin.com/ZZMAddcT
  16. @palica - so I'm building a custom kernel because of glitch in the handling of a video card? Okay. I'll deal. FTR - genkernel menu showed the ATI Radeon framebuffer as "< >" or no value. I hit 'N' anyway. I'll see what the value of config shows after the reboot but I suspect it will be unchanged.
  17. @palica - it occurred to me that it might be useful to extend your suggestion about /proc/config.gz. As I mentioned earlier, my desktop system doesn't exhibit the behaviour that the funtoo system shows. For completeness, I'm uploading the diff file of the config for the funtoo kernel 4.14.2 and the desktop kernel 4.14.12. kernel_funtoo_artix.diff.gz
  18. @palica diff of config 4.8.15 to 4.14.2 as requested... kernel_funtoo.diff.gz
  19. Focus was on getting a working kernel without the console problem. Jumping to debugging why the LTS kernel didn't build seemed off-topic/off-task at the time. I can revisit later after getting current situation under control.
  20. firmware package is already installed. Something went wrong during emerge and I didn't dig into why.
  21. @palica I tried that last night but it balked at me when it got to the drivers (IIRC - realtek was shown). The info about kernel config is useful. I was looking here for a path ahead. Your way seems easier. Appreciate the help - will report back with more.
  22. @palica I tried that. LTS is at 4.9.65 and I thought it would be a better choice. Unfortunately, I did something wrong and got a pile of errors back. Custom kernel building is new territory for me. I'm not sure about kconfig. I'll research and retrieve.
  23. Further experimenting... sys-kernel/debian-sources downgraded from 4.14.12 to next kernel below 4.14.2 (upgrade when the problems first observed). Version debian-sources-4.8.15 was the only package available. Problem did not persist after a reboot.
  24. Further experimenting... Used kernel boot parameters: nofb - no change to appearance - get 1920x1080 presentation grey text on white background nomodeset - get normal colours but old-style console display (80 cols x 2? rows) I then found an article about using setterm in the inittab. Experimenting with the setterm command I discovered there is some kind of colour masking in play. setterm -clear all -background cyan produced a screen with a purple background. Using `-background black` returned the screen to the white background.
  25. I blacklisted the radeon module and rebooted. Screen stayed white text on black background through out boot process. However, console stayed at 80 cols wide (looks ugly on a 1920x1080 monitor).
×
×
  • Create New...