| === Wyly0 is now known as Wyly | ||
| === Wyly9 is now known as Wyly | ||
| === Wyly8 is now known as Wyly | ||
| === Wyly7 is now known as Wyly | ||
| === patrick is now known as Guest9196 | ||
| === patrick_ is now known as patrick | ||
| === Perflosopher05 is now known as Perflosopher0 | ||
| === jgee0 is now known as jgee | ||
| === jgee6 is now known as jgee | ||
| === EddyD is now known as SergeiD | ||
| Guest51 | Good day, I have a question/issue with autoinstall and the cloud-init docs suggested asking here. However, it is for a desktop installation and related to the oem kernel flags. Is this the right place to get some help or is there somewhere else that would be better? | 20:30 |
|---|---|---|
| sarnold | this is likely to be the best spot on irc, but that might not be the best overall place, i'm not sure.. | 20:35 |
| oerheks | ask, wait and see? | 20:39 |
| Guest51 | Okay, I'll post some details and see if someone can suggest where to go. I'm trying to build an image to install on a number of different Dell Laptops. I have it all built out with autoinstall and it has generally been working well. Within the autoinstall.yaml file, I have set `oem` to '`auto` which appears to be the default anyway. I've recently | 20:41 |
| Guest51 | received some newer models and the OS installation is failing. In the logs, it says "A specific kernel was requested but it cannot be satisfied when installing on certified hardware." Just before that, it appears that it was looking up info on the `oem-somerville-muk-meta` package and specifically that package says `wants_oem_kernel=false`. | 20:41 |
| Guest51 | So, I guess the question is this: is there a way for me to setup autoinstall to prefer oem kernels if available but fall back to the regular one otherwise? | 20:42 |
| Guest51 | From the docs here: https://canonical-subiquity.readthedocs-hosted.com/en/latest/reference/autoinstall-reference.html#id4, it appears my only options are `true`, `false`, or `auto` which is true on desktop and false on server. | 20:44 |
| Guest51 | Oh, also as part of the logs it is saying that I should set the oem install flag to `false` and if I do that I can get the installation to succeed. With it set to `auto`, the installation fails whien it can't find the oem kernel. | 20:44 |
| oerheks | i think no, build 2 images | 20:47 |
| oerheks | maybe someone else has a trick | 20:50 |
| Guest51 | Okay, thanks for the info. I'm not sure if there's a way to make a suggestion but it would be helpful for my use case and managing a range of machines if I could set it up to be more tolerant somehow. | 21:14 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!