[SOLVED] Vulkaninfo amdgpu on -current

ernie young · 10-06-2020, 09:51 PM

I did run cp command and my folder shows that everything is there:

Code:

# ls /boot/efi/EFI/Slackware/
elilo.conf*  elilo.conf~*  elilo.efi*  initrd.gz*  initrd_5.4.60.gz*  vmlinuz*  vmlinuz-generic-5.4.60*

I should remove the /boot, then. Let me try that.

bassmadrigal · 10-07-2020, 10:07 AM

Quote:

Originally Posted by ernie young

I did run cp command and my folder shows that everything is there:

Code:

# ls /boot/efi/EFI/Slackware/
elilo.conf*  elilo.conf~*  elilo.efi*  initrd.gz*  initrd_5.4.60.gz*  vmlinuz*  vmlinuz-generic-5.4.60*

I should remove the /boot, then. Let me try that.

Yup, if everything is there, you should just need to remove the /boot/ portion from the image and then reboot.

walecha · 10-07-2020, 10:42 AM

Quote:

Originally Posted by ernie young

how did you come across this "other-module:another-module:amdgpu"? I looked for something to reference for the future but could not find this specific line on the net.

Just type

Code:

man mkinitrd

on your terminal

ernie young · 10-07-2020, 07:19 PM

I took out the /boot as agreed but also had to take out the resume=/dev/sdb2 from append because when loading up the OS it truncated the rest of the loading, but now I get another error when loading the OS:

Code:

mount: mounting /dev/sda2 on /mnt failed: No such device
ERROR: No /sbin/init found on rootdev (or not mounted). Trouble
       You can try to fix it. Type 'exit' when things are done.

/bin/sh: can't access tty: job control turned off

0XBF · 10-08-2020, 08:48 AM

Perhaps you have the wrong initrd specified for booting the generic kernel? You posted this snippet of your mkinitrd command for kernel 5.4.60 with the initrd generated as "/boot/initrd.gz":

Quote:

Originally Posted by ernie young

Code:

# initrd created with 'mkinitrd -c -k 5.4.60 -f ext4 -r /dev/sda2 -m xhci-pci:ohci-pci:ehci-pci:xhci-hcd:uh 
ci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-asus:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitec 
h-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:crc32c_intel:crc32c_generic:ext4 -u -o /boot/initrd.gz'

If that was the case then make sure that you copied that file from /boot/initrd.gz to /boot/efi/EFI/slackware/initrd.gz, or in your case you would have had to rename the initrd to "initrd_5.4.60.gz", since thats what you're using in your elilo.conf stanzas.

Also note that the huge kernel shouldn't need an initrd, just the generic kernels should need them. You could try remaking the initrd and making sure that the newest initrd is the one sitting on the efi partition and pointed to by elilo.conf generic kernel stanza with the same name. Just a thought, perhaps you're past this alredy.

ernie young · 10-10-2020, 07:21 PM

I cleared the previous mkinitrd files I had created, initrd.gz & initrd_5.4.60.gz. As you can probably see on my first post initrd.gz was being used by the huge kernel. I know it's not needed by Huge, however, now that I deleted it, my kernel went down with it. I am somewhat confused what has caused it.

Has this happened to someone before and what solution did you have, if any?

The error is: kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2)

ernie young · 10-11-2020, 02:09 PM

I ran eliloconfig, and I don't know if this is indicative of an issue but it adds this line to the Huge stanza: initrd=initrd.gz
If it's not needed why does the eliloconfig script add it? Is there a way for me to run mkinitrd to restore the OS.

I have tried:

Code:

mount /dev/sdaX /mnt #X - your root partition
mount /dev/sdaZ /mnt/boot #Z - your boot partition
mount -t proc /proc /mnt/proc
mount --rbind /sys /mnt/sys
mount --rbind /dev /mnt/dev

Thank you for your help and time.

bassmadrigal · 10-11-2020, 03:46 PM

eliloconfig will copy over the /boot/initrd.gz and /boot/vmlinuz files (or the file(s) they point to if a symlink). It is not a "smart" program.

Here's what I'd do to maximize the chances of this work. First, forget about eliloconfig. It's done its job of registering the elilo efi file with the motherboard's firmware.

Now, since you're running -current, I'm going to use the kernel version that's included today with a fully updated system (5.4.70). If you don't have 5.4.70, either install it or adjust the version numbers below.

First, generate an initrd for that kernel. I'm using the line previously provided and including the amdgpu module:

Code:

mkinitrd -c -k 5.4.70 -f ext4 -r /dev/sda2 -m xhci-pci:ohci-pci:ehci-pci:xhci-hcd:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-asus:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:crc32c_intel:crc32c_generic:ext4:amdgpu -u -o /boot/initrd-5.4.70.gz

Now, copy the initrd and generic kernel to the UEFI partition:

Code:

cp /boot/*5.4.70* /boot/efi/EFI/Slackware/

Now, make sure your elilo.conf properly points to the right files:

Code:

chooser=simple
delay=100
timeout=100
#
image=vmlinuz-generic-5.4.70
  initrd=initrd-5.4.70.gz
  label=5.4.70
  append="radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 amdgpu.dc=1 vga=normal"
  read-only

ernie young · 10-11-2020, 05:16 PM

@bassmadrigal, I greatly appreciate your help. Would you be able to help me overcome what I hope is our last hump, how can I load the modules for my 5.4.60 kernel to make mkinitrd work when mounting like in post #22? Or is there another way?

Before, I was able to make changes because my Huge kernel was working but since I got rid of initrd.gz through ignorance, I haven't been able to access my OS at all. Once I recover my current OS I will update to 5.4.70.

bassmadrigal · 10-11-2020, 06:20 PM

One easy way to get into a working install is to boot off your install media, mount your OS drive, and then bind mount a few directories, and then chroot into the mounted filesystem. Since you're running UEFI, you'll also want to mount your UEFI partition.

Code:

mount /dev/sda2 /mnt
mount /dev/sda1 /mnt/boot/efi   # This is a guess on your UEFI partition... adjust as needed
mount -o bind /dev/ /mnt/dev/
mount -o bind /proc/ /mnt/proc/
mount -o bind /sys/ /mnt/sys/
chroot /mnt

From here, you should be able to make adjustments to your installed system.

ernie young · 10-12-2020, 10:57 PM

Hello @bassmadrigal, your instructions worked like a charm. My chroot was not working before, maybe I didn't use the bind command correctly. Thank you very much for the help and the patience.