You are not logged in.
Hello
I installed a vfio kernel and after that my system didn't want to boot anymore.
I installed the kernel with yaourt -S linux-vfio-lts. I also tried the linux-vfio. And I also tried to install both with pacaur, pacaur takes forever though I wonder why.
I can't do anything when It drops you into the recovery shell, the keyboard just doesn't work.
I copied this from a screengrab on my phone there might be tyops I tried my best.
::running early hook [udev]
Warning: /lib/modules/4.4.32-1-vfio-lts/modules.devname not found - ignoring
::running hook [udev]
::Triggering uevents...
Waiting 10 seconds for device /dev/disk/by-uuid/ffc3c085-ed9d-456a-ad12-daa3fb27b8e4 ...
ERROR: device 'UUID=ffc3c085-ed9d-456a-ad12-daa3fb27b8e4' not found. skipping fsck.
ERROR: Unable to find root device 'UUID=ffc3c085-ed9d-456a-ad12-daa3fb27b8e4' .
You are beeing dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty; job control turned off
[rootfs ]#
I managed to get me old kernel working again by booting from a arch-stick and deleting everything related to the linux-vfio kernel in /boot/ by hand and doing a $mkinitcpio -p linux.
First I though maybe modules.devname is missing, but its there.
$ cat /lib/modules/4.4.32-1-vfio-lts/modules.devname
# Device nodes to trigger on-demand module loading.
fuse fuse c10:229
cuse cuse c10:203
btrfs btrfs-control c10:234
loop loop-control c10:237
tun net/tun c10:200
ppp_generic ppp c108:0
uinput uinput c10:223
dm_mod mapper/control c10:236
vfio vfio/vfio c10:196
hci_vhci vhci c10:137
uhid uhid c10:239
vhost_net vhost-net c10:238
snd_timer snd/timer c116:33
snd_seq snd/seq c116:1
I thought it might be fstab, but it looks fine to me.
cat /etc/fstab
# UUID=ffc3c085-ed9d-456a-ad12-daa3fb27b8e4
/dev/sda3 / ext4 rw,relatime,data=ordered0 1
# UUID=0864636d-ce23-446a-a7cc-be2d716a8ae1
/dev/sda2 /boot ext4 rw,relatime,data=ordered0 2
# UUID=AA70-9A55
/dev/sda1 /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
# UUID=9b0e1ae6-035a-4800-81d4-382da1cba9b6
/dev/sda4 /home ext4 rw,relatime,data=ordered0 2
# UUID=38AEE45FAEE41762 LABEL=Data
/dev/sdc2 /home/haroon/media/toshiba ntfs rw,auto,user,exec 0 0
Then I though maybe it was the rEFInd config file, it looked fine to me too.
$ cat /boot/refind_linux.conf
"Boot with standard options" "ro rw root=UUID=ffc3c085-ed9d-456a-ad12-daa3fb27b8e4 intel_iommu=on"
"Boot to single-user mode" "ro rw root=UUID=ffc3c085-ed9d-456a-ad12-daa3fb27b8e4 intel_iommu=on"
"Boot with minimal options" "ro rw root=UUID=ffc3c085-ed9d-456a-ad12-daa3fb27b8e4 intel_iommu=on"
I also checked the mkinitcpio.conf, but I didn't find a error.
$ cat /etc/mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="vfio vfio_iommu_type1 vfio_pci vfio_virqfd"
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
#
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect block filesystems"
#
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev block filesystems"
#
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev block mdadm encrypt filesystems"
#
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev block lvm2 filesystems"
#
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
# COMPRESSION_OPTIONS
# Additional options for
I'm absolutely clueless on how to get this kernel working or what I'm doing wrong to it is not working.
Regards
Last edited by Haroon (2017-02-20 21:48:07)
Offline
Did you generate an initrd for the vfio kernel? And configure your bootloader to find it?
Offline
By initrd do you mean '$mkinitcpio -p linux-vfio' because I tried that multiple times and it didn't help. Also yaourt executes mkinitcpio -p linux-vfio at the end of the installation process afaik.
However I had a initramfs-linux-vfio.img and initramfs-linux-vfio-fallback.img on my boot partition, but I deleted them, since the system wouldn't boot with them there. The names are paraphrased, because I don't know them by heart, I only saw them for a few moments before I deleted them.
About the bootloader how do I configure it? I only know about the refind.conf file, I looked for another conf file in the boot partition, but I didn't find it.
Offline
Offline