Jump to content

Search the Community

Showing results for tags 'boot'.

  • 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

  • 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
  • Linux Container Club - LXD/LXC's Blog
  • Funtoo Perl Hackers's Perl on Funtoo

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 8 results

  1. 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 p
  2. 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 ordinar
  3. 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
  4. 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 happ
  5. 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.
  6. 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 ve
  7. 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.)
  8. 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
×
×
  • Create New...