Jump to content

Search the Community

Showing results for tags 'Boot'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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


  • drobbins' Blog
  • It's a Bear's life
  • haxmeister's Blog
  • psychopatch's Blog
  • 666threesixes666's Blog
  • decision theory
  • Chris Kurlinski's Blog
  • Sandro's Blog
  • danielv's Blog
  • Not So Stupid Admin Tricks
  • maldoror's Blog
  • andreawilson's Blog
  • Simple Step-by-Step Server Setup
  • saraedward's Blog
  • eusanpe
  • Funtoo Perl Hackers's Perl on Funtoo

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






First Name

Last Name



Found 9 results

  1. Hello, I have a crypted /home (/dev/mapper/lvm-home) inside lvm, and a keyfile on /boot (/dev/sda1): /boot/keyfile Why: On normal days, it boot automatically, but on vacations/trips I delet the /boot/keyfile and people can't access. On ArchLinux it worked with: [ /etc/default/grub ] GRUB_CMDLINE_LINUX="cryptdevice=/dev/mapper/lvm-home:home cryptkey=/dev/sda1:ext4:/.boot root=/dev/mapper/lvm-funtoo dolvm rootfstype=ext4" and before: grub-mkconfig -o /boot/grub/grub.cfg On Funtoo I tried the same and: [ /etc/crypttab ] home UUID=44ae1749-28d7-4f35-9948-e02b747213cf /dev/disk/by-uuid/013e1dc7-cb3f-4a90-8b4e-251179adcbe5:/keyfile luks,initramfs [ /etc/conf.d/dmcrypt ] target=home source=UUID=44ae1749-28d7-4f35-9948-e02b747213cf key=/dev/disk/by-uuid/013e1dc7-cb3f-4a90-8b4e-251179adcbe5:/keyfile With "genkernel --lvm --luks initramfs" after all. [ /boot/grub/grub.cfg ] linux /kernel-debian-sources-x86_64-5.10.40_p1 root=/dev/mapper/lvm-funtoo ro cryptdevice=/dev/mapper/lvm-home:home cryptkey=/dev/sda1:ext4:/keyfile root=/dev/mapper/lvm-funtoo dolvm rootfstype=ext4 loglevel=7 echo 'Loading initial ramdisk ...' initrd /early_ucode.cpio /initramfs-genkernel-x86_64-5.10.40_p1-debian-sources [ /etc/fstab ] /dev/mapper/lvm-funtoo / ext4 defaults 0 1 /dev/sda1 /boot ext4 defaults 0 0 /dev/mapper/home /home ext4 defaults 0 0 /home/.swap none swap sw 0 0
  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. Over time I have experienced problem that my keyboard does not work during early boot, the time where I am supposed to make key-map selection on system-rescue-cd, but - more important - at the time I am expected to enter encryption key to unlock my encrypted partitions. If I end up in rescue mode I can't do anything, not even ctrl-alt-delete to reboot. I have had the problem on my current and previous hardware if I am using debian-sources (4.8 and 4.14). I have this problem with all kernels I have tested with my present hardware (ASUS Prime Z370). Naturally it failes with my ordinary logitech k750 keyboard but it also fails with a ordinary plain USB cable connected USB-keyboard. I have played around with different settings in kernel (gentoo-sources) to build in or not support for USB, logitech modules, the fundamental USB HIDBP, etc and cannot observe any difference during boot (but I managed to disable mouse in KDE). I can see that the logitech modules are loaded when booting debian-kernel but it still wont work. This is the latest dmesg where HID is loaded [ 1.239301] hidraw: raw HID events driver (C) Jiri Kosina [ 1.239542] usbcore: registered new interface driver usbhid [ 1.239780] usbhid: USB HID core driver . . . [ 20.619928] logitech-djreceiver 0003:046D:C52B.0003: hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-5.1/input2 [ 20.732809] input: Logitech K750 as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.1/1-5.1:1.2/0003:046D:C52B.0003/0003:046D:4002.0005/input/input9 [ 20.732897] logitech-hidpp-device 0003:046D:4002.0005: input,hidraw2: USB HID v1.11 Keyboard [Logitech K750] on usb-0000:00:14.0-5.1:1 [ 21.154637] usbcore: registered new interface driver snd-usb-audio [ 25.298802] logitech-hidpp-device 0003:046D:4002.0005: HID++ 2.0 device connected. I am quite sure that luks is opened long before the 20 seconds and the HID is hidraw. The very same rows with the very same keyboard on a working setup where I can enter the password: One difference I found is that in a working boot (where keyboard is working) the same rows as above seems to happen earlier: Dec 30 09:20:37 nuffsan kernel: [ 2.440038] usb 8-2.1: new full-speed USB device number 4 using xhci_hcd Dec 30 09:20:37 nuffsan kernel: [ 2.624861] usb 8-2.1: New USB device found, idVendor=046d, idProduct=c52b Dec 30 09:20:37 nuffsan kernel: [ 2.624866] usb 8-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Dec 30 09:20:37 nuffsan kernel: [ 2.624869] usb 8-2.1: Product: USB Receiver Dec 30 09:20:37 nuffsan kernel: [ 2.624872] usb 8-2.1: Manufacturer: Logitech Dec 30 09:20:37 nuffsan kernel: [ 2.628778] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:09.0/0000:04:00.0/usb8/8-2/8-2.1/8-2.1:1.0/0003:046D:C52B.0001/input/input5 Dec 30 09:20:37 nuffsan kernel: [ 2.680543] hid-generic 0003:046D:C52B.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:04:00.0-2.1/input0 Dec 30 09:20:37 nuffsan kernel: [ 2.683897] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:09.0/0000:04:00.0/usb8/8-2/8-2.1/8-2.1:1.1/0003:046D:C52B.0002/input/input6 Dec 30 09:20:37 nuffsan kernel: [ 2.735411] hid-generic 0003:046D:C52B.0002: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:04:00.0-2.1/input1 Dec 30 09:20:37 nuffsan kernel: [ 2.738136] hid-generic 0003:046D:C52B.0003: hiddev1,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:04:00.0-2.1/input2 . . . Dec 30 09:20:38 nuffsan kernel: [ 12.393989] cryptsetup (4105) used greatest stack depth: 13648 bytes left Dec 30 09:20:38 nuffsan kernel: [ 20.241508] cryptsetup (4179) used greatest stack depth: 13520 bytes left Password was entered before 12 and 20 seconds. I use the very same and slightly modified linuxrc and initrd.scripts. Modification is an own luks open function that is similar but independent from the cryptroot-stuff. Instead I open encrypted partitions specified at kernel line in specified order right before BTRFS scan is performed. Eventually I might send a patch. I have tried the solution mentioned in https://forums.gentoo.org/viewtopic-t-1063372.html but it didn't work.
  4. After many many considerations I went for EFI-boot in faovour of good old BIOS-boot using syslinux. The fall back solution is still BIOS-boot using extlinux. Problem is that with the very same (carefully verified) initramfs and kernel all my 16GB ram shows up in BIOS boot while only 4GB (well, 3.5) shows up booting from EFI. Any hint on the reason to this? My world does not depend on EFI-boot, the BOIS boot works very well and will be my primary until this is sorted out, but it would be good to understand. Some facts; Motherboard is ASUSTeK SABERTOOTH 990FX R2.0 Rev 1.xx BIOS is dated Date: 05/04/2016 and version 2901 that seems to be the latest version. # uname -a Linux kalle 4.13.12-gentoo #6 SMP PREEMPT Thu Dec 14 07:42:52 CET 2017 x86_64 AMD FX(tm)-9590 Eight-Core Processor AuthenticAMD GNU/Linux I have tried several combinations of legacy modes including no legacy support (CSM disabled).
  5. I am trying to bring up a system with ZFS following https://www.funtoo.org/ZFS_Install_Guide I'm having trouble booting. at the completion of the steps in the Guide. # grub-mkconfig -o /boot/grub/grub.cfg None of the 'initramfs-genkernel-XXXX' are being found that were build with the --zfs flag. The Guide indicates these initramfs-genkernel's should be the ones found in its example output. grub-mkconfig is finding the normal initramfs-debian-sources-XXXX and kernel files and these were not build with the --zfs flag to my knowledge. Anyone have any idea why this is happening and how to fix it? If I force a menu entry in /etc/grub.d/40_custom that uses initramfs-genkernel-XXXX the system will boot until it reaches the point where it tries to import the pools. Gives error cannot import 'rpool' no such pool or dataset destroy and re-create the pool... Yet if I go to the grub shell and do a zpool import rpool is found. What is going on here? I think something is broken as when emerging zfs, zfs-0.7.3 and and a new grub were pulled in. Has anyone gotten zfs install to work with the *current* portage? I know it worked in the past, doesn't seem to be working now.
  6. I'm looking to install Lilo to by MBR, but I'm not sure how to proceed with telling Lilo which kernel/initrd to use. I'm using the latest debian-sources kernel, so I would expect to write "image=/boot/debian-sources-x86_64-4.7.8" and the initrd bit to lilo.conf for it to boot. However my kernel isn't in /boot, and I'm not sure what to symlink to /boot/bzImage. I'd rather not creating symlinks, if it can be avoided.
  7. Yesterday night I performed a global upgrade of all my packages, noticed that it had genkernel updates included. The system upgraded nice and clean. I was doing my work while it worked. Turned off my PC after a depclean. But it seems that I had to eselect and boot-update the new kernel before doing that for now I can't boot to my OS anymore. Ok... Burned a System rescuecd 4.7.1 (the most recent on the install page). To try mounting my Funtoo installation directories and doing what I forgot last night. My problem is, everytime I boot this System rescuecd from my pen or any of the latest versions of it. I get at certain boot part of this cd what follows: 'Error: Cannot mount sysrcd.dat (none ....kernel details....)' and it gives me the basic terminal. (By the way, I'm currently having to use my Windows instalation, that's the only one that still works and burning the systemrescuecd with lili, (this kind of thing) is one of those situations that never gave any problem such as I reported... I'm stuck, for it never happened to me before. My computer hardware is very recent too. Can any of you guys possibly have an idea for me? Thanks in advance.
  8. After following the instructions on the /Install page I get this "boot: not a valid runlevel" message on boot, and / is read-only. I can login and remount / rw. (I feel like I should give more information, but don't know what would be relevant.)
  9. Hello, I followed this guide for setting up UEFI: http://www.funtoo.org/UEFI_Install_Guide After I select an option from GRUB the screen just goes black. I have SSH server on for testing and the system never goes up. I have tried with both the debian binary kernel and a custom kernel. I also haven't ran an emerge -auDN world (maybe this is my problem), as I'd imagine it shouldn't matter if Xorg radeon drivers are installed to get to a shell. Here is the config for the custom kernel I tried. Here is my make.conf And my grub.cfg Any ideas? My video card is an R9 270x if that helps :). Thanks.
  • Create New...