Jump to content
funtoo forums

digifuzzy

Members
  • Content Count

    132
  • 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

328 profile views
  1. digifuzzy

    Error with sync of gnome-kit branch

    I just looked... Bug exists and was filed yesterday: https://bugs.funtoo.org/browse/FL-5932
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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
  7. 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.
  8. 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
  9. 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
  10. 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.
  11. digifuzzy

    TTY (console) colour changed after OpenRC start

    firmware package is already installed. Something went wrong during emerge and I didn't dig into why.
  12. digifuzzy

    TTY (console) colour changed after OpenRC start

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

    TTY (console) colour changed after OpenRC start

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

    TTY (console) colour changed after OpenRC start

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

    TTY (console) colour changed after OpenRC start

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