manual update dom0 to newest 4.5 kernel

[R]

Hi,

I got a Asus Zenbook UX305CA laptop.

Hardware is too new for older kernel support, see:
https://www.reddit.com/r/linux/comments/3svv6s/dont_buy_the_new_ux305ca_zenbooks_yet/

Biggest problems in older kernels:
- Display does not work properly without grub edit
- wifi does not work
- Touchpad does not work

Kernel 4.5 seems to solve all these issues though.
 
My question is, can I:
- install Qubes with i915.preliminary_hw_support=1 kernel parameter enabled in grub
- boot a Live Linux USB and download F24 alpha 4.5 kernel rpm
- copy kernel rpm to Qubes partition on HDD
- boot Qubes, verify and install new kernel to dom0 using yum

Cheers :)

[evado...@gmail.com]

Why developers still not add new kernel by default? :(
Please, give us any realise with newest kernel at dom0.Maybe it will solve half of problems.

[Daniel Wilcox]

Download the rpm for f24 first, extract it, find the .config or whatever the hell they ship it with, then compare it with what you get from dom0 zcat /proc/config.gz -- make sure it has all the fancy XEN options enabled like dom0 does.  (I don't know if that is the default or not, I don't normally use Fedora, but check)

That's what you really need first, beyond that there might be some libvirt stuff to look into but that'll be pretty apparent when you boot if virtual machines won't start.

Ultimately it's still just a Linux box, give it a shot.  I likewise will be patching my kernel up pretty soon.  I expect it'll be an adventure that is well worth the learning experience, cheers,

=D

ps: you shouldn't be able to copy a file to your dom0 from a live cd... you did use full disk encryption didn't you?  you'll need to do something else, there are workarounds on the documentation page, or you could try Rudd-O's ansible-qubes 'bombshell'.

On Fri, Apr 1, 2016 at 4:30 PM, <evado...@gmail.com> wrote:

Why developers still not add new kernel by default? :(
Please, give us any realise with newest kernel at dom0.Maybe it will solve half of problems.

--
You received this message because you are subscribed to the Google Groups "qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3337da62-b883-4059-bcfc-10d43b1779ed%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[R F]

On Saturday, 2 April 2016, Daniel Wilcox <d...@yubasolutions.com> wrote:

Download the rpm for f24 first, extract it, find the .config or whatever the hell they ship it with, then compare it with what you get from dom0 zcat /proc/config.gz -- make sure it has all the fancy XEN options enabled like dom0 does.  (I don't know if that is the default or not, I don't normally use Fedora, but check)

That's what you really need first, beyond that there might be some libvirt stuff to look into but that'll be pretty apparent when you boot if virtual machines won't start.

Ultimately it's still just a Linux box, give it a shot.  I likewise will be patching my kernel up pretty soon.  I expect it'll be an adventure that is well worth the learning experience, cheers,

=D

ps: you shouldn't be able to copy a file to your dom0 from a live cd... you did use full disk encryption didn't you?  you'll need to do something else, there are workarounds on the documentation page, or you could try Rudd-O's ansible-qubes 'bombshell'.

 

Thanks for your answer. 

Can anyone els comment on Daniels remark about needing to check .config (and what the file is called in Fedora) and libvirt please? Anything els needed to be checked /tweaked? Couldnt find anything in any guide on this. 

Full disk encryption is luks and can be decrypted from an other OS.

Cheers!

[evado...@gmail.com]

> Can anyone els comment on Daniels remark about needing to check .config (and what the file is called in Fedora) and libvirt please? Anything els needed to be checked /tweaked? Couldnt find anything in any guide on this. 

> Can anyone els comment on Daniels remark about needing to check .config (and what the file is called in Fedora) and libvirt please? Anything els needed to be checked /tweaked? Couldnt find anything in any guide on this.

I have the problem with the old graphic drivers in dom0. I go to the qubes devel and read the issue about updating dom0 to the new fedora. It can not be done quickly, because current Qubes software like Qubes Manager and old KDE windows decoration plugin does not support new KDE5 in the new Fedora.

If you will update dom0, then decoration plugin will not work and you will see the system without colors&tags at all VM windows. Maybe some other issues also will be there and "Qubes" will not work. You will get only Xen with virtual machines. If I'm understand correctly the situation.

You can track how it is going here: https://github.com/QubesOS/qubes-issues/issues/1807

They also want to make new Qubes system architecture and add GUI domain (X graphic system will be places at GUI domain). I hope they will concentrate all efforts on this to move X system to new GUI domain. It will give possibility to easier update dom0 and GUI.

[R F]

On Saturday, 2 April 2016, <evado...@gmail.com> wrote:

> Can anyone els comment on Daniels remark about needing to check .config (and what the file is called in Fedora) and libvirt please? Anything els needed to be checked /tweaked? Couldnt find anything in any guide on this. 

I have the problem with the old graphic drivers in dom0. I go to the qubes devel and read the issue about updating dom0 to the new fedora. It can not be done quickly, because current Qubes software like Qubes Manager and old KDE windows decoration plugin does not support new KDE5 in the new Fedora.

If you will update dom0, then decoration plugin will not work and you will see the system without colors&tags at all VM windows. Maybe some other issues also will be there and "Qubes" will not work. You will get only Xen with virtual machines. If I'm understand correctly the situation.

You can track how it is going here: https://github.com/QubesOS/qubes-issues/issues/1807

They also want to make new Qubes system architecture and add GUI domain (X graphic system will be places at GUI domain). I hope they will concentrate all efforts on this to move X system to new GUI domain. It will give possibility to easier update dom0 and GUI.

-

I see you're trying to update the entire dom0 os to a higher version of fedora. I only wanted to update the kernel to the newest one, not the os. I guess updating the kernel should be easier, right? 

[R F]

Anyway, I will try. Can anyone tell me what the latest kernel version is I can update Q3.1 dom0? Can I update to the latest kernel available for fedora: 4.5.1?

[evado...@gmail.com]

If you will not receive any answers and decide just to try.
Maybe something from this links will help.

https://groups.google.com/forum/#!topic/qubes-users/JmIc9jvmFRk
https://groups.google.com/forum/#!topic/qubes-users/J0w7nKGn6ac

Please, write shott tutorial about how to update it if you could do it.

[evado...@gmail.com]

Looks line new kernel from > 4.5 come with new AMDGPU that support my card. So, new kernel will solve my problem too...

[Axon]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

R F:

> Can anyone tell me what the latest kernel version is I can update
> Q3.1 dom0? Can I update to the latest kernel available for fedora:
> 4.5.1?

Marek might be able to answer this one.
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXF2MnAAoJEJh4Btx1RPV840kQAONVRVoUba2uxf3g9wEPf6ej
DAyqZFV/sfesq8S0WLSvI6mEnVOwWqSdB0XNG5n1k3Q0QZEnYkBW9Gio6EJMKS7h
u5VLjusCUwaGuwb/VNpGqIwYq6FUeDijAKgKgYNIAuUvzbBQOQaFy55Yvg3ybOPH
4mlAhsqjPK5tj/tHe057QTd0ZhQCeumuY35l2oFmanvr6PYtzLR073JbxOOk5Xj7
8oDky74VmNyjiBE0edF+oGrpnrDWYYciB4HFituI9YZgzDG0jSO2l0nI8JJrW/CY
ai5ptQiHN1ZgX4rumRlytuUVQkummibXwQBABPlJJookw8+t6o4wfiiwMK/oHsEw
BYx3qDuqI8uloJxGAbf2pTKrJl8pQoYkte3EakbaJ4/51eyuJw+2R96SG7sX9wV0
p7u12L9NHcO4wvsjMv+nfF7xUJd65r+wMo98fuVQ46Ip8cdCbV9OVRqrXflgumgV
NVEKRB7JGRERmeuayqC1/WGcau/exaEkv9HfSBu8fizIUdHrVjdOBWj1Dn3KFRgk
Oh3R/CrNOViLSdh7GZdjARTvfLZKJpXpEL6P8X4sLMyVOgAaJF3FzuHgJ0wR4Ub5
E+eM2cWlqWgutEWIRYczUqu0nZHWijXBEB1ztZvAq8CXJwOt4cvup9m3BWWgDt1D
bKMs71sv8FMLvUVQNCNc
=9FnG
-----END PGP SIGNATURE-----

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wed, Apr 20, 2016 at 11:08:36AM +0000, Axon wrote:
> R F:
> > Can anyone tell me what the latest kernel version is I can update
> > Q3.1 dom0? Can I update to the latest kernel available for fedora:
> > 4.5.1?
>
> Marek might be able to answer this one.

I think there was some problems with kernels >= 4.4 reported some time
ago. Eric, do you remember what was that about? AFAIR it was about VM
only, but I may be missing something.

Anyway there is no _easy_ way to upgrade dom0 kernel. But it is possible.
Version 4.5.x is available only in (not yet released) Fedora 24.
It would be something like this:
1. Add fc24 repository in dom0:
sudo cp /etc/yum.repos.d/fedora.repo /etc/yum.repos.d/fedora-24.repo
sudo cp /etc/yum.repos.d/fedora-updates.repo /etc/yum.repos.d/fedora-updates-24.repo
Adjust those settings in just copied files:
- change "20" to "24" (every occurrence)
- add "24" to names (strings in square brackets)
- add "includepkgs = kernel*" to every fc24 repository definition
2. Get Fedora 24 signing key - you have it already in your fedora-23
template: /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-24-primary. You can copy
it to dom0 with something like:
qvm-run -a fedora-23 'cat
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-24-primary' | sudo tee
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-24-primary

3. Import that key: sudo rpm --import
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-24-primary

4. Install new kernel: sudo qubes-dom0-update kernel

I haven't tested above procedure, so some minor modifications may be
needed. Also didn't tested 4.5.x kernel in dom0.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXGKXIAAoJENuP0xzK19cs4EYIAJFmXDc1/WVQnJAGH3UoMxGH
dUo61LMGGrYdusdwRjA9k6YKCrbqK4t6BTAl9L4+BGtQxvFyvTnrp+3f0LCZ3cUs
VY8tW6T4jTr/sf7kbp272FJcXVI7rg4RHzavzL1lJXF8Dj3fI0TkvZTQzn1CIMYC
SvQ5vHWQFj/PVOD2ZLvzFbsvKi54gcYYecq5TxBUDdO/d2CFmCXqivk1RsgXegRa
uH5X+rINVWTKSiiiK6fmwZrLJZKqp6pi+hKI4CA34kBO9wZtU1yy+uzV3ofqeEIg
yrjvIW09GkT1e224F5Aov3yfBiCED7W3Q5i0pRTcHe/Dwfvcxs+sIvXr+9TrJtI=
=PboE
-----END PGP SIGNATURE-----

[R F]

Really appreciate your help Marek! 

When I have sufficient time one of these weeks I will give this project a go and keep you guys updated. 

Would be nice to get Qubes working on this Zenbook UX305CA. As the old Zenbooks have good hardware virtualization support and I couldn't find any ultrabooks from the hardware compatibility list still sold today with good Qubes support.

F24 (alpha) with latest kernel (4.5.1.X) works out of the box on this machine. Thats why I hope Qubes with the latest kernel might too. 

Cheers,

R

[evado...@gmail.com]

Marek thanks for this tutorial. I will try or will wait for R F report.

[evado...@gmail.com]

> - add "24" to names (strings in square brackets)

How exactly do that? Now, I'm trying with default [updates] [updates-debuginfo] need to change it to [updates24] ?
Now, I only replaced "20" -> "24" everywhere.

As a result I got by qubes-updates "kernel* already installeted and latest version"

ps. Does not work for me. (interesting, why?)

qvm-run -a fedora-23 'cat
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-24-primary' | sudo tee
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-24-primary

Maybe it will helps to somebody. Instead of above I use:

qvm-run --pass-io fedora-23 'cat
/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-24-primary' > ~/RPM-GPG-KEY-fedora-24-primary
sudo cp ~/RPM-GPG-KEY-fedora-24-primary /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-24-primary

[evado...@gmail.com]

I also tried [updates24] -- It also say:
Loaded plugins: yum-qubes-hooks
Package 1000:kernel-4.1.13.9.props.qubes.x86_64 already installeted and latest version
Nothing to do

Of course, I added 'includepkgs = kernel*' to each section of 2 files (but seems it's can be added to only [updates24] section, because all other section have "enable=0". So, seems sources and debug-info disabled.

[Holger Levsen]

Hi Marek,

On Thu, Apr 21, 2016 at 12:04:56PM +0200, Marek Marczykowski-Górecki wrote:
> Anyway there is no _easy_ way to upgrade dom0 kernel. But it is possible.
> Version 4.5.x is available only in (not yet released) Fedora 24.
> It would be something like this:
> 1. Add fc24 repository in dom0:
> sudo cp /etc/yum.repos.d/fedora.repo /etc/yum.repos.d/fedora-24.repo
> sudo cp /etc/yum.repos.d/fedora-updates.repo /etc/yum.repos.d/fedora-updates-24.repo
> Adjust those settings in just copied files:
> - change "20" to "24" (every occurrence)
> - add "24" to names (strings in square brackets)
> - add "includepkgs = kernel*" to every fc24 repository definition
> 2. Get Fedora 24 signing key - you have it already in your fedora-23
> template: /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-24-primary. You can copy
> it to dom0 with something like:
> qvm-run -a fedora-23 'cat
> /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-24-primary' | sudo tee
> /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-24-primary

small mistake here: qvm-run --pass-io needs to be used…

> 3. Import that key: sudo rpm --import
> /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-24-primary
>
> 4. Install new kernel: sudo qubes-dom0-update kernel

this didnt work for me, so I tried:
sudo qubes-dom0-update 'kernel-4.5*'
which resulted in

[...]
Resolving Dependencies
--> Running transaction check
---> Package kernel.x86_64 0:4.5.2-301.fc24 will be installed
--> Processing Dependency: kernel-core-uname-r = 4.5.2-301.fc24.x86_64
for package: kernel-4.5.2-301.fc24.x86_64
--> Processing Dependency: kernel-modules-uname-r =
4.5.2-301.fc24.x86_64 for package: kernel-4.5.2-301.fc24.x86_64
--> Running transaction check
---> Package kernel-core.x86_64 0:4.5.2-301.fc24 will be installed
---> Package kernel-modules.x86_64 0:4.5.2-301.fc24 will be installed
--> Processing Conflict: kernel-core-4.5.2-301.fc24.x86_64 conflicts
xfsprogs < 4.3.0-1
--> Processing Conflict: kernel-core-4.5.2-301.fc24.x86_64 conflicts
xorg-x11-drv-vmmouse < 13.0.99
--> Finished Dependency Resolution
Error: kernel-core conflicts with
xorg-x11-drv-vmmouse-13.0.0-13.fc20.x86_64
Error: kernel-core conflicts with xfsprogs-3.2.1-1.fc20.x86_64
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

I tried "--skip-broken" but of course this didn't help. Now I'm a bit
lost at what my options are to get a 4.5 kernel into dom0.

Also, even if that worked, it would lack the 4.5 kernel-qubes-vm
package… so the longer term solution would be to get those into a
qubes-unstable (or such) repo?

Or should I try to be bold and add xorg packages to the includepkgs=…
from above, hoping this would allow me to update the kernel without
upgrading too much other stuff? Has anyone done that?


--
cheers,
Holger

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I think it is safe to remove xfsprogs and xorg-x11-drv-vmmouse. Look for
its dependencies (what yum remove would like to remove), but probably
nothing more. Of course unless you use XFS on some partition.

> Also, even if that worked, it would lack the 4.5 kernel-qubes-vm
> package… so the longer term solution would be to get those into a
> qubes-unstable (or such) repo?

It is easily possible to create VM kernel out of dom0 kernel.
https://www.qubes-os.org/doc/managing-vm-kernel/
In short: use qubes-prepare-vm-kernel tool.

> Or should I try to be bold and add xorg packages to the includepkgs=…
> from above, hoping this would allow me to update the kernel without
> upgrading too much other stuff? Has anyone done that?

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXH4yFAAoJENuP0xzK19csDusH/ixCNdVCTD+ZIA/9PEG0sxMl
kh5IpWRbIeA17hFh+SdS6qvVweX2p+jivm01wSq7Mfxu0913MDiYUAyd3gMsbQ6f
4c9noGGuPTJ1Yk9CjHsi1f47C2iQ90jLWXPsjy9bsnl0g7WBEiKWEwcYv7iS+Iaa
Clz/5pnG3Q27qOioeUMGZWQ00JqiksrDGmFhNjaACkNjT71B22nb0uNSLYD6Dik/
xLr85uJn1U9gk5KNh27cV29U2zAeiF898sj9e4Rc43YImkulUSEGpfunn3Rum7Vd
9B2JNg/SLbVAqAqkEukoivTx7Z438Hb4MafnQE2jyQEkCTItnWX0b+HsCQelx74=
=pdyy
-----END PGP SIGNATURE-----

[Holger Levsen]

On Tue, Apr 26, 2016 at 05:43:01PM +0200, Marek Marczykowski-Górecki wrote:
> I think it is safe to remove xfsprogs and xorg-x11-drv-vmmouse. Look for
> its dependencies (what yum remove would like to remove), but probably
> nothing more. Of course unless you use XFS on some partition.

doh, I mistook xfs for the xfontserver… anyhow, removing
xorg-x11-drv-vmmouse wants to remove xorg-x11-drivers too (which doesnt
really sound harmless…) but worse, xfsprogs is a depends of udisk2 which
is a depends of kdelibs… so this wont work.

(I tried both sudo yum remove as well as rpm -e, nothing more fancy
though.)

> > Also, even if that worked, it would lack the 4.5 kernel-qubes-vm
> > package… so the longer term solution would be to get those into a
> > qubes-unstable (or such) repo?
> It is easily possible to create VM kernel out of dom0 kernel.
> https://www.qubes-os.org/doc/managing-vm-kernel/
> In short: use qubes-prepare-vm-kernel tool.

ah, nice, thanks!


--
cheers,
Holger

[Holger Levsen]

On Tue, Apr 26, 2016 at 03:55:34PM +0000, Holger Levsen wrote:
> doh, I mistook xfs for the xfontserver… anyhow, removing
> xorg-x11-drv-vmmouse wants to remove xorg-x11-drivers too (which doesnt
> really sound harmless…) but worse, xfsprogs is a depends of udisk2 which
> is a depends of kdelibs… so this wont work.

ok:

changing to "includepkgs=kernel* xfsprogs" in the yum configs and

sudo yum remove xorg-x11-drv-vmmouse
sudo qubes-dom0-update 'kernel-4.5* xfsprogs'

helped to install the kernel 4.5 packages from fedora 24. Yay.

But, /boot/vmlinuz-4.5* does not exist, even though "rpm -ql
kernel-core-4.5*" lists it.

Also strange, "rpm -qa kernel_4.5*" lists no files at all.

Is that "just" fedora-24 being broken atm or am I missing something?


--
cheers,
Holger

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Tue, Apr 26, 2016 at 05:57:51PM +0000, Holger Levsen wrote:
> On Tue, Apr 26, 2016 at 03:55:34PM +0000, Holger Levsen wrote:
> > doh, I mistook xfs for the xfontserver… anyhow, removing
> > xorg-x11-drv-vmmouse wants to remove xorg-x11-drivers too (which doesnt
> > really sound harmless…) but worse, xfsprogs is a depends of udisk2 which
> > is a depends of kdelibs… so this wont work.
>
> ok:
>
> changing to "includepkgs=kernel* xfsprogs" in the yum configs and
>
> sudo yum remove xorg-x11-drv-vmmouse
> sudo qubes-dom0-update 'kernel-4.5* xfsprogs'
>
> helped to install the kernel 4.5 packages from fedora 24. Yay.
>
> But, /boot/vmlinuz-4.5* does not exist, even though "rpm -ql
> kernel-core-4.5*" lists it.

If rpm -ql list it, it should be there. Didn't you get any install errors?
Check also "rpm -V kernel-core" (it's verify mode).

> Also strange, "rpm -qa kernel_4.5*" lists no files at all.

There is a '-', not '_' between package and version, it isn't Debian...

> Is that "just" fedora-24 being broken atm or am I missing something?

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXH9jjAAoJENuP0xzK19csAIAIAJjqiLi8YdDqsgtwpCocDfeq
XG9Ge6o8LDwrhV7dwYU7l0ZpdjMfyHEJ05Mw/bboMVxg/N4RiP1mMNqYxSE7qpd2
CH7rS3Y6As2aqUxQ9G9yIdA02bWQ1dGefsRd8QObNlQu/TXhHVo7O2Iy1i/qaBT7
DkkAa/SfXojoVf29SJtIK42uADSOf7w71+zqF/G7Qbrb9Vjv6JtTvOgYKk8ox8lQ
eBQSG4FOoxCb1urKgnq2wNH4ds3XYrP5rPNZ+MCGiGnrA+hPZd/Loa43s5n43FYi
so4c7rh/xPEi0R26+J/AlLIul66ljVy4Z0j2yAOUobrSMBp0oCYG3BFNA7fAKXE=
=bzxG
-----END PGP SIGNATURE-----

[Holger Levsen]

On Tue, Apr 26, 2016 at 11:08:52PM +0200, Marek Marczykowski-Górecki wrote:
> > But, /boot/vmlinuz-4.5* does not exist, even though "rpm -ql
> > kernel-core-4.5*" lists it.
> If rpm -ql list it, it should be there. Didn't you get any install errors?

not that I remember (but this dark red on black is not really good to
read…)

> Check also "rpm -V kernel-core" (it's verify mode).

it only lists one entry: (see below)

> > Also strange, "rpm -qa kernel_4.5*" lists no files at all.
> There is a '-', not '_' between package and version, it isn't Debian...

right, I did that just typed it wrong in the email…:

[holger@dom0 ~]$ rpm -qa|grep kernel
kernel-modules-4.5.2-301.fc24.x86_64
kernel-4.1.13-9.pvops.qubes.x86_64
kernel-4.5.2-301.fc24.x86_64
qubes-core-dom0-linux-kernel-install-3.1.10-1.fc20.x86_64
kernel-qubes-vm-4.1.13-9.pvops.qubes.x86_64
kernel-core-4.5.2-301.fc24.x86_64
[holger@dom0 ~]$ rpm -V kernel
.......T.
/lib/modules/4.1.13-9.pvops.qubes.x86_64/modules.builtin.bin
.......T. /lib/modules/4.1.13-9.pvops.qubes.x86_64/modules.devname
.......T. /lib/modules/4.1.13-9.pvops.qubes.x86_64/modules.softdep
[holger@dom0 ~]$ rpm -V kernel-4.5.2-301.fc24.x86_64
[holger@dom0 ~]$ rpm -ql kernel-4.5.2-301.fc24.x86_64
(enthält keine Dateien)
[holger@dom0 ~]$ rpm -ql kernel-4.1.13-9.pvops.qubes.x86_64|wc
3919 3919 301717
[holger@dom0 ~]$ ls /boot/*4*
/boot/config-4.1.13-9.pvops.qubes.x86_64
/boot/initramfs-4.5.2-301.fc24.x86_64.img
/boot/System.map-4.1.13-9.pvops.qubes.x86_64 /boot/xen-4.6.0.gz
/boot/initramfs-4.1.13-9.pvops.qubes.x86_64.img
/boot/symvers-4.1.13-9.pvops.qubes.x86_64.gz
/boot/vmlinuz-4.1.13-9.pvops.qubes.x86_64
[holger@dom0 ~]$ rpm -V kernel-core
..?...... /lib/modules/4.5.2-301.fc24.x86_64/System.map
[holger@dom0 ~]$ rpm -ql kernel-core|wc
2105 2105 146127
[holger@dom0 ~]$ rpm -ql kernel-core|grep /boot
/boot/.vmlinuz-4.5.2-301.fc24.x86_64.hmac
/boot/System.map-4.5.2-301.fc24.x86_64
/boot/config-4.5.2-301.fc24.x86_64
/boot/initramfs-4.5.2-301.fc24.x86_64.img
/boot/vmlinuz-4.5.2-301.fc24.x86_64
[holger@dom0 ~]$


--
cheers,
Holger

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Tue, Apr 26, 2016 at 09:40:13PM +0000, Holger Levsen wrote:
> On Tue, Apr 26, 2016 at 11:08:52PM +0200, Marek Marczykowski-Górecki wrote:
> > > But, /boot/vmlinuz-4.5* does not exist, even though "rpm -ql
> > > kernel-core-4.5*" lists it.
> > If rpm -ql list it, it should be there. Didn't you get any install errors?
>
> not that I remember (but this dark red on black is not really good to
> read…)

Actual installation messages are white. Red is only used for VM output
(basically downloading the packages).

Interesting - while package file list contains those files, actual
archive there does not. Apparently vmlinuz is extracted to
/lib/modules/.../vmlinuz. Post transaction script:
$ rpm -q --scripts kernel-core
(...)
/bin/kernel-install add 4.5.2-301.fc24.x86_64
/lib/modules/4.5.2-301.fc24.x86_64/vmlinuz || exit $?

I think you can simply copy vmlinuz to /boot/vmlinuz-4.5.2-301.fc24.x86_64,
then execute:
dracut /boot/initramfs-4.5.2-301.fc24.x86_64.img 4.5.2-301.fc24.x86_64
grub2-mkconfig -o /boot/grub2/grub.cfg

Apparently kernel package format has changed from Fedora 20 to 24. But the
above commands should make it working in Qubes.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXH+jlAAoJENuP0xzK19cs5dAIAIoaRV2k9oJTb2kYX3e4YdFf
FjLbnWUBMmHnitWrqZ09GldOC3wzu5f/p46nbJK7WnfTXmT/n76FNn16jaCr+vZk
krgWJpHW9/ySO1ifjFqY5kkhlhE4hUJ+3mfYG/CWomKF8GNO1m+fxBCt/QaURtno
1tdrz/HOimfmxEygitPg3EXqpqQaARTZx+26DjMvdWHa26aaSzsVItC1Prd/kRo+
Ti3MiCu+b7HQP51uS4/rrR23l+p+caMxC1XmeY0XddvJMwNv411tvPDIugTJzwg+
nz806AEseuB1c11xAwpzmp3F/O+eC5t3GUqyJaLeIUegryHCajy7/WLRBTJIvKo=
=PACi
-----END PGP SIGNATURE-----

[Holger Levsen]

On Wed, Apr 27, 2016 at 12:17:09AM +0200, Marek Marczykowski-Górecki wrote:
> Interesting - while package file list contains those files, actual
> archive there does not. Apparently vmlinuz is extracted to
> /lib/modules/.../vmlinuz.

yup, I unpacked the rpm file manually and found vmlinuz and System.map
there indeed, and copied them to /boot (with the correct names) manually…

> Post transaction script:
> $ rpm -q --scripts kernel-core
> (...)
> /bin/kernel-install add 4.5.2-301.fc24.x86_64
> /lib/modules/4.5.2-301.fc24.x86_64/vmlinuz || exit $?
>
> I think you can simply copy vmlinuz to /boot/vmlinuz-4.5.2-301.fc24.x86_64,
> then execute:
> dracut /boot/initramfs-4.5.2-301.fc24.x86_64.img 4.5.2-301.fc24.x86_64
> grub2-mkconfig -o /boot/grub2/grub.cfg

My first attempt was to simple reinstall with rpm, didnt help (=created
the initramfs but nothing in /boot/grub/grub.cfg), so I did run your commands
with the exact same results :/

> Apparently kernel package format has changed from Fedora 20 to 24. But the
> above commands should make it working in Qubes.

grub2-mkconfig only finds the 4.1.13 kernel :( anything else you can
think of?


--
cheers,
Holger

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Reading through /etc/grub.d/20_linux_xen, it requires also
/boot/config-$kernelversion file.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXH+4MAAoJENuP0xzK19csIecIAJPQKsp3lD2Fnh/s/8XZ7nBd
kFpdajYzsLsTtz5StXeK9tZP6JB3tZ4w9c7SzlQWLw2yAwRhtYCjSkHu/SV3Gm62
vr3K4W5hrlWjYMIYUSqYuXQXKn06wx4GuY1zB5FRvbCUXVWjim5P0Ui0ZMVOXrVH
I1uPeSAU/QwUvoTxFD8j2LC5NLLndnmYXX+vBLheGNEjbemODSzbYRXqiaR62Hn6
9MGxm3vg1QjWETyHeyj85A9YTmtQVPRAurvhJ4ViZtg/m24iv3Z8GxLGMaBDy1fk
pAzxBg6uXLD1BbP3DOxj8NDZo1oQohv6YHS8Mg+zkF/PULC4S28h/rNvl8dE56I=
=wSx0
-----END PGP SIGNATURE-----

[Holger Levsen]

On Wed, Apr 27, 2016 at 12:39:08AM +0200, Marek Marczykowski-Górecki wrote:
> Reading through /etc/grub.d/20_linux_xen, it requires also
> /boot/config-$kernelversion file.

whoohoo, that worked, grub picked it up and when I boot it… it reboots
directly after grub loading xen and the 4.5 kernel… with no
output/failure whatsoever :/

at least the fallback to xen with 4.1 kernel works nicely…

the initramfs for 4.5 is a bit smaller (16755547 vs 17384503), there are
3778 files in /lib/modules/4.1* and 3589 in /lib/modules/4.5*

thanks a lot for your help so far!


--
cheers,
Holger

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Tue, Apr 26, 2016 at 10:54:19PM +0000, Holger Levsen wrote:
> On Wed, Apr 27, 2016 at 12:39:08AM +0200, Marek Marczykowski-Górecki wrote:
> > Reading through /etc/grub.d/20_linux_xen, it requires also
> > /boot/config-$kernelversion file.
>
> whoohoo, that worked, grub picked it up and when I boot it… it reboots
> directly after grub loading xen and the 4.5 kernel… with no
> output/failure whatsoever :/

Try removing "quiet" option from kernel cmdline.

> at least the fallback to xen with 4.1 kernel works nicely…
>
> the initramfs for 4.5 is a bit smaller (16755547 vs 17384503), there are
> 3778 files in /lib/modules/4.1* and 3589 in /lib/modules/4.5*

Interesting, but probably doesn't matter. I guess in 4.5 more things are
selected as built-in.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXH/QTAAoJENuP0xzK19cshOIH/RUGJ0WgUuV/8uOcLLn18uOF
ulC1L+VKBThMtjdAqU/GVT8Qy6YSaS91Y5GGzp5/9Iw7nNSi+6fZxQZ1pT9wHjQE
8rYiWfwjnNBEiUaVDpEEMivmCy9q1AiFRwMGGH3xgxIzfKnEU+zt5SEcoplu8bEo
lLg3VbfcFQphGOI3O7gA3KHeUdwsCNCQit1DV/4ZekPot4K/YphoQmSGNKSrtp18
AZNzfKLv2YFp4dApD6jIGLBktOcqPz+DwGDP458nDFiTFvsaSq+Fo8HOXumwVjyK
E+E+rpwwvPoX36BdEg8PhBEc0H4gYOqKGmD312/VvFdfEqBn0+z9HMj397s+7r0=
=h8p7
-----END PGP SIGNATURE-----

[R F]

Holger,

Great to hear you managed to upgrade the kernel !! This means I might not need to buy an other laptop after all. 

I looked back at what you posted but it's a bit confusing. I'm probably not the only one. 

Would it be possible for you to make a clear overview of all the steps to take (commandos in dom0 terminal) to be able to upgrade the kernel?

This would be of help to alot of people, at least to me. 

Hope you can help out. 

Much appreciated! 

Cheers,

R

[R F]

Sorry I mis-read Holgers last email after "whoohoo, that worked, grub picked it up and when I boot it…"
So there was no output, it didn't work. Bummer.

[swfo...@gmail.com]

My problem exactly. Had Qubes running well on an old Lenovo & would love to run it on this more capable Zenbook.

Did you get this working in the end? Alternative is to spare myself the headache & keep running Mint until the next release.

[R F]

On Wed, Jan 18, 2017 at 10:52 PM, <swfo...@gmail.com> wrote:

My problem exactly.  Had Qubes running well on an old Lenovo & would love to run it on this more capable Zenbook.

Did you get this working in the end?  Alternative is to spare myself the headache & keep running Mint until the next release.

--

It almost works on the current Qubes. But no mouse pad and wifi. So I'm using F25 atm and waiting for the next Qubes to roll out.
If the next Qubes uses F25 as its base, the kernel will be high enough for it to fully function.

Lets hope the Qubes team will go for F25. This will help get more hardware compatible and expand.

Until then, patience :)

[Foppe de Haan]

just checking: you two are aware of the fact that you can get the 4.8.12 kernel via --enablerepo=qubes-dom0-unstable ?

[R F]

On Thu, 19 Jan 2017 at 12:22, R F <ma...@ronilution.com> wrote:

--

For me the thing is I want the touchpad and wifi to work from the start to keep my laptop usb free. 

[motech man]

Is it reasonable to assume that the "unstable" repo doesn't mean "insecure"?

I'm not sure how new I will need to go to to get more support for the Intel 630 integrated graphics. It only provides a single resolution of 1024x768.

Also if I'm going to go thru the trouble of updating prior to the next release I'm concerned about having the essential config options required for xen / qubes. Might as well taylor the option to my hardware, but don't want to overdo that and render the new kernel unbootable.