Jump to content
funtoo forums

Search the Community

Showing results for tags 'debian-sources'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Funtoo Discussion Forums
    • News and Announcements
    • General Discussion
    • Dev Central
    • Funtoo Hosting
    • Funtoo Infrastructure
  • Help Central
    • General Help
    • Installation Help
    • Portage Help
    • Desktop Help
    • Server Help
  • Funtoo Services

Blogs

There are no results to display.

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


freenode


github


web


First Name


Last Name


Location


Interests

Found 7 results

  1. Hello, what would be the best way to pass additional kernel config parameters (CONFIG_...) when emerging sys-kernel/debian-sources (or sys-kernel/debain-sources-lts)? Thank you, -- Saulius
  2. So this is strange... I just install funtoo in my Lenovo Y700 whit KDE and everything was running fine just have uno minor issue, the boot time netmount and networkmanager they just stop for a few seconds, then it resume my boot and that was it. First i just did this in the /etc/rc.conf rc_hotplug="!net.*" And it did the job then i was installing acpi, laptop for power manager, configuring the nvidia driver, trying to get working with the intel driver too. Everything was Ok but then I notice that the boot process just stop and I have to hit a key (any key) to resume the boot process, just like that. The first thing that y did was to remove services from the RC first the netmount, then the networkmanager then the acpi, laptop, ssh and nothing work, just at the end i have to hit any kit and the sddm show up. i dont know why i just try to install bootchart to try to understandit but i coudnt make it work. put the interactive mode whit RC and like i am hit a key just boot up ok. this is the rc.log rc sysinit logging started at Tue Jun 11 09:39:53 2019 OpenRC 0.40.2 is starting up Funtoo Linux (x86_64) Press I to enter interactive boot mode * /proc is already mounted * Mounting /run ... * /run/openrc: creating directory * /run/lock: creating directory * /run/lock: correcting owner * Caching service dependencies ... [ ok ] * Caching service dependencies ... [ ok ] * Clock skew detected with `(null)' * Adjusting mtime of `/run/openrc/deptree' to Tue Jun 11 16:34:11 2019 * WARNING: clock skew detected! * Mounting security filesystem ... [ ok ] * Mounting debug filesystem ... [ ok ] * Mounting config filesystem ... [ ok ] * Mounting persistent storage (pstore) filesystem ... [ ok ] * Mounting efivarfs filesystem ... [ ok ] * Mounting cgroup filesystem ... [ ok ] * Remounting devtmpfs on /dev ... [ ok ] * Mounting /dev/mqueue ... [ ok ] * Mounting /dev/shm ... [ ok ] * Creating list of required static device nodes for the current kernel ... [ ok ] * /etc/init.d/udev uses runscript, please convert to openrc-run. * Starting udev ... [ ok ] * Generating a rule to create a /dev/root symlink ... [ ok ] * Populating /dev with existing devices through uevents ... [ ok ] * Waiting for uevents to be processed ... [ ok ] rc sysinit logging stopped at Tue Jun 11 09:39:53 2019 rc boot logging started at Tue Jun 11 09:39:53 2019 * WARNING: clock skew detected! * Loading module coretemp ... * Failed to load coretemp [ !! ] * Loading kernel modules ... modprobe: ERROR: could not insert 'nvidia': Module already in kernel [ ok ] * Setting system clock using the hardware clock [Local Time] ... [ ok ] * The binfmt-misc module needs to be loaded by the modules service or built in. * Mounting misc binary format filesystem ... [ ok ] * Loading custom binary format handlers ... [ ok ] * Checking local filesystems ... /sbin/fsck.xfs: XFS file system. fsck.fat 4.1 (2017-01-24) /dev/sda1: 583 files, 20884/127746 clusters [ ok ] * Remounting root filesystem read/write ... [ ok ] * Remounting filesystems ... [ ok ] * Updating /etc/mtab ... * Creating mtab symbolic link [ ok ] * Activating swap devices ... [ ok ] * Mounting local filesystems ... [ ok ] * Configuring kernel parameters ... [ ok ] * Creating user login records ... [ ok ] * Wiping /tmp directory ... [ ok ] * Configuring /etc/hosts ... [ ok ] * Setting hostname to SykLPC ... [ ok ] * Setting terminal encoding [UTF-8] ... [ ok ] * Setting keyboard mode [UTF-8] ... [ ok ] * Loading key mappings [la-latin1] ... [ ok ] * Bringing up network interface lo ... [ ok ] * Saving key mapping ... [ ok ] * Saving terminal encoding ... [ ok ] * Initializing random number generator ... [ ok ] rc boot logging stopped at Tue Jun 11 16:39:54 2019 rc default logging started at Tue Jun 11 16:39:55 2019 * WARNING: clock skew detected! * Starting dbus ... [ ok ] * Starting metalog ... [ ok ] * Starting consolekit ... [ ok ] * Starting NetworkManager ... [ ok ] Conectando..... 1sConectando...... 1sConectando....... 1sConectando........ 1sConectando......... 1sConectando.......... 1sConectando..........$ * Marking NetworkManager as inactive. It will automatically be marked * as started after a network connection has been established. * WARNING: NetworkManager has started, but is inactive * Starting acpid ... [ ok ] * No bootchart process found! * This script does not start bootchart, but only schedules its termination. * Bootchart should be started from the kernel command line. * Please check the README on how to do that. [ ok ] * Starting cupsd ... [ ok ] * Starting laptop_mode ... [ ok ] * Initializing sensors ... [ ok ] * WARNING: netmount will start when NetworkManager has started * Starting sshd ... [ ok ] * Starting thermald ... [ ok ] * Setting up sddm ... [ ok ] * Starting local ... [ ok ] rc default logging stopped at Tue Jun 11 16:40:23 2019 Any clues?
  3. Hi! Following ebuilds now added to testing nvidia-drivers-390.77-r1 and nvidia-drivers-396.45-r1 Both including patch to resolve a blank screen issue, when kernel-4.16 or newer used.. This patch will not be applied, if older kernel version installed or/and set as default kernel. To test, assuming kernel-4.16 or newer used and video card is supported by LTS release of nvidia-drivers, proceed with following steps echo "=x11-drivers/nvidia-drivers-390.77-r1 **" >> /etc/portage/package.keywords emerge nvidia-drivers debian-sources-4.17.8 added, also with no keywords, for testing, use: echo "=sys-kernel/debian-sources-4.17.8 **" >> /etc/portage/package.keywords emerge debian-sources boot-update Testing is very much appreciated. As usual, bugs.funtoo.org is your friend for any problems encountered. Regards, Oleg.
  4. Hi, I have made the upgrade to 1.2 and stumbled on problems when building debian-source-4.15.17 I configured the kernel from scratch using config-extract for plain amd64 (exact flags lost in reboot, too some effort to get those right). When building the kernel I got this error: make[1]: *** No rule to make target 'debian/certs/benh@debian.org.cert.pem', needed by 'certs/x509_certificate_list'. Stop. make: *** [Makefile:1018: certs] Error 2 There is no debian/certs directory for the sources so it seems fair enough. According to this thread I need to remove the trusted certificate. I did so and the build progresses. I figure this is not a big deal but since feed back is asked for..... Cheers, Erik
  5. The new debian-sources-4.14.12 release now available which has the fix for severe security problem, known as meltdown. https://meltdownattack.com/
  6. Merry Christmas everyone! The new debian-sources-4.14.2 release now available and will be the default kernel in stages. We hope it will work good for you. Please, report any inconveniences found with update on bugs.funtoo.org.
  7. debian-sources-4.13.10 added some time back, currently with no keywords set. Please, give it a test nd report back the problems encountered.
×
×
  • Create New...