Jump to content
funtoo forums

digifuzzy

Members
  • Content Count

    137
  • Joined

  • Last visited

  • Days Won

    4

digifuzzy last won the day on January 9 2015

digifuzzy had the most liked content!

2 Followers

About digifuzzy

  • Rank
    Advanced Member

Personal

  • Location
    Canada

Recent Profile Visitors

389 profile views
  1. digifuzzy

    Grub install and GRUB_GFXMODE

    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.
  2. digifuzzy

    Grub install and GRUB_GFXMODE

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

    Grub install and GRUB_GFXMODE

    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?
  4. digifuzzy

    Cinnamon install unmet requirements

    You didn't see this in the original post?
  5. 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?
  6. digifuzzy

    Error with sync of gnome-kit branch

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

    Error with sync of gnome-kit branch

    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.
  8. digifuzzy

    TTY (console) colour changed after OpenRC start

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

    TTY (console) colour changed after OpenRC start

    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.
  10. digifuzzy

    TTY (console) colour changed after OpenRC start

    @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.
  11. digifuzzy

    TTY (console) colour changed after OpenRC start

    @palica - didn't work. Problem persisted after the reboot. Unable to upload config file to message board. Pastebin link - https://pastebin.com/ZZMAddcT
  12. digifuzzy

    TTY (console) colour changed after OpenRC start

    @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.
  13. digifuzzy

    TTY (console) colour changed after OpenRC start

    @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
  14. digifuzzy

    TTY (console) colour changed after OpenRC start

    @palica diff of config 4.8.15 to 4.14.2 as requested... kernel_funtoo.diff.gz
  15. digifuzzy

    TTY (console) colour changed after OpenRC start

    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.
×