Kernal panic on boot

49 views
Skip to first unread message

Master Node

unread,
Nov 2, 2019, 2:08:00 PM11/2/19
to qubes-users
Hi I was finally able to get a working and running system, I had updated everything to whonix 15 and debian 10 leaving fedora 26 as is.

I had turned my pc off and restarted it as normal booting legacy USB threw my external m2 drive, as that is how I was able to install I get the qubes grub screen. Usually it would just boot for me normally but now I get a kernal panic and it closes. But if I go to advanced option - plane version 4.8 - xen 4.8 and linux 4.14.18-1.pvops

Is the only one that will allow my qubes to start.

I tried down grading my kernal to since I thought it might be some kind of conflication but it shouldnt be every thing was working fine while updated.

Kernal 4.19.80-1 was down graded to 4.14.18-1 with in the global settings

When I boot and try to start sys-net network connections I get an error reading

PCI device dom0:04:_00.0 does not exist

None of this happened when I could just boot normally like I had been doing before I did a full update and shut down.

Please let me know what you think I can do any help is appreciated

Thank you

awokd

unread,
Nov 3, 2019, 6:31:25 PM11/3/19
to Master Node, qubes-users
Master Node:
> Hi I was finally able to get a working and running system, I had updated everything to whonix 15 and debian 10 leaving fedora 26 as is.
>
> I had turned my pc off and restarted it as normal booting legacy USB threw my external m2 drive, as that is how I was able to install I get the qubes grub screen. Usually it would just boot for me normally but now I get a kernal panic and it closes. But if I go to advanced option - plane version 4.8 - xen 4.8 and linux 4.14.18-1.pvops
>
> Is the only one that will allow my qubes to start.
>
> I tried down grading my kernal to since I thought it might be some kind of conflication but it shouldnt be every thing was working fine while updated.
>
> Kernal 4.19.80-1 was down graded to 4.14.18-1 with in the global settings

I think you have the right idea, but the wrong approach. Check
https://www.qubes-os.org/doc/software-update-dom0/#changing-default-kernel.

> When I boot and try to start sys-net network connections I get an error reading
>
> PCI device dom0:04:_00.0 does not exist
>
> None of this happened when I could just boot normally like I had been doing before I did a full update and shut down.

I don't see why a kernel version would affect your PCI device's
existence, unless it's driver related somehow. Go into sys-net/Qube
Settings/Devices and see if it shows what it's trying to map there. You
can also check what PCI devices are out there with lspci in a dom0 terminal.

--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots
Reply all
Reply to author
Forward
0 new messages