Build USB install with kernel 5+
m...@militant.dk
Ilpo Järvinen
> Hi everyone,
>
> Any help appreciated.
>
> I managed to install a Qubes 4.0.3 on an Intel NUC10FNK. No VM's can start
> due to an error like: Internal error: Unable to reset PCI device
> 0000:00:1f:6:no FLR, PM rset or bus reset available.
--
i.
Max Andersen
> Den 28. mar. 2020 kl. 19.38 skrev Ilpo Järvinen <ilpo.j...@cs.helsinki.fi>:
I tried your recommendation, and now it starts the vm, but it still has no network, since the driver propably only resides in newer kernels which dom0 does not have. (it says sys-net has no network cards)
I can actually put in an older wireless usb in the machine, and it sees it with lsusb in dom0, but I Dont know how To enable it in vm
I tried readlink /sys/bus/usb/devices/usb1
It gave 0000:00:14.0/usb1
Tried qvm-pci
It showed usb controller on that?
When runming qvm-pci a sys-net-clone-1 dom0:00_14.0 it failed with got empty response from qubesd and hung
Any ideas, maybe on getting kernel 5 on qubes?
Sincerely
Max
FredGarr
Hi everyone,
I have an audio issue in DOM0 since last Wednesday (04/08/2020), and I'm unable to fix it...
Any help or advise is welcomed!!
(as a non English native, please excuse my English)
Issue Explanation:
Intel PCH Audio card 0 is no more present in pulseaudio GUI, only
the NVIDIA HDMI audio card 1 is present.
Although hardware is OK (verified with my previous debian hard
drive today).
Commands, configuration and things that may help:
Kernel version: 4.14 (latest versions cause issue on laptop
screen power off/on with Nvidia card...)
Qubes release 4.0-8
lspici : OK
00:1b.0 Audio device: Intel Corporation 8
Series/C220 Series Chipset High Definition Audio Controller (rev
04)
Subsystem: Hewlett-Packard Company ZBook 15
Flags: bus master, fast devsel, latency 0, IRQ
22
Memory at d0330000 (64-bit, non-prefetchable)
[size=16K]
Capabilities: <access denied>
Kernel driver in use: pciback
--
01:00.1 Audio device: NVIDIA Corporation GK106
HDMI Audio Controller (rev a1)
Subsystem: Hewlett-Packard Company Device 197b
Flags: bus master, fast devsel, latency 0, IRQ
17
Memory at d0000000 (32-bit, non-prefetchable)
[size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
/var/lib/alsa/asound.state:OK
This file has the two cards definitions well configured (PCH
& NVidia).
journalctl parsing since January: Only one error on
alsa, alsactl kernel crash on Apr08 upon shutdown command (another
but beg March so, ignored)
Apr 08 17:54:53 dom0 systemd[1]: Stopping Manage Sound
Card State (restore and store)...
Apr 08 17:54:53 dom0 kernel: audit: type=1131
audit(1586361293.216:308): pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=xen-init-dom0 comm="systemd"
exe="/usr/lib/systemd/systemd" host
Apr 08 17:54:53 dom0 kernel: audit: type=1113
audit(1586361293.216:309): pid=4353 uid=0 auid=1000 ses=2
msg='op=logout id=1000 exe="/usr/sbin/lightdm" hostname=dom0
addr=? terminal=/dev/tty1
Apr 08 17:54:53 dom0 kernel: alsactl[1989]: segfault at 28
ip 00005f6263fbc806 sp 00007ffcff227110 error 4 in
alsactl[5f6263fab000+17000]
Apr 08 17:54:53 dom0 kernel: audit: type=1701
audit(1586361293.222:310): auid=4294967295 uid=0 gid=0
ses=4294967295 pid=1989 comm="alsactl" exe="/usr/sbin/alsactl"
sig=11 res=1
Apr 08 17:54:53 dom0 audit[1]: SERVICE_STOP pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=xen-init-dom0
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=
Apr 08 17:54:53 dom0 audit[4353]: USER_LOGOUT pid=4353
uid=0 auid=1000 ses=2 msg='op=logout id=1000
exe="/usr/sbin/lightdm" hostname=dom0 addr=? terminal=/dev/tty1
res=success'
Apr 08 17:54:53 dom0 audit[1989]: ANOM_ABEND
auid=4294967295 uid=0 gid=0 ses=4294967295 pid=1989 comm="alsactl"
exe="/usr/sbin/alsactl" sig=11 res=1
From alsa-info.sh:
Loaded ALSA modules : snd_hda_intel
Soundcards recognised by ALSA : 1 [NVidia ]:
HDA-Intel - HDA NVidia (HDA-Intel HDA Intel PCH not present)
Amixer output only sees Card hw:1 'Nvidia'
Alsactl output only presents NVidia card 1 controls, not
the PCH card 0 ones
!!ALSA/HDA dmesg
!!--------------
[ 33.223400] Already setup the GSI :17
[ 33.223410] snd_hda_intel 0000:01:00.1: Disabling MSI
[ 33.223414] snd_hda_intel 0000:01:00.1: Handle
vga_switcheroo audio client
[ 33.241080] snd_hda_codec_idt hdaudioC0D0: autoconfig
for 92HD91BXX: line_outs=1 (0xa/0x0/0x0/0x0/0x0) type:line
[ 33.241082] snd_hda_codec_idt hdaudioC0D0:
speaker_outs=1 (0xd/0x0/0x0/0x0/0x0)
[ 33.241084] snd_hda_codec_idt hdaudioC0D0: hp_outs=1
(0xb/0x0/0x0/0x0/0x0)
[ 33.241085] snd_hda_codec_idt hdaudioC0D0: mono:
mono_out=0x0
[ 33.241086] snd_hda_codec_idt hdaudioC0D0: inputs:
[ 33.241088] snd_hda_codec_idt hdaudioC0D0: Mic=0xc
[ 33.241089] snd_hda_codec_idt hdaudioC0D0:
Internal Mic=0x11
[ 33.241091] snd_hda_codec_idt hdaudioC0D0:
Line=0xf
[ 33.480372] input: HDA NVidia HDMI/DP,pcm=3 as
/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input20
[ 33.480458] input: HDA NVidia HDMI/DP,pcm=7 as
/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input21
[ 33.480526] input: HDA NVidia HDMI/DP,pcm=8 as
/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input22
[ 33.588662] Adding 11931644k swap on
/dev/mapper/qubes_dom0-swap. Priority:-2 extents:1
across:11931644k SSFS
[ 34.289114] input: HDA Intel PCH Mic as
/devices/pci0000:00/0000:00:1b.0/sound/card0/input16
[ 34.289373] input: HDA Intel PCH Line as
/devices/pci0000:00/0000:00:1b.0/sound/card0/input17
[ 34.289582] input: HDA Intel PCH Dock Line Out
as /devices/pci0000:00/0000:00:1b.0/sound/card0/input18
[ 34.289785] input: HDA Intel PCH Headphone as
/devices/pci0000:00/0000:00:1b.0/sound/card0/input19
[ 34.479079] input: ST LIS3LV02DL Accelerometer as
/devices/platform/lis3lv02d/input/input23
=> dmesg, soundcard 0 PCH is detected...
Thank's fore any support!
awokd
> I can actually put in an older wireless usb in the machine, and it sees it with lsusb in dom0, but I Dont know how To enable it in vm
devices don't passthrough very well, though.
> Tried qvm-pci
>
> It showed usb controller on that?
>
> When runming qvm-pci a sys-net-clone-1 dom0:00_14.0 it failed with got empty response from qubesd and hung
sys-net-clone-1. This can work, if you're sure nothing else is on it
(like your keyboard & mouse). Many systems only have one controller
though, so try USB passthrough first.
--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots
Max Andersen
issues might be lack of support.
On 4/14/20 1:28 AM, 'awokd' via qubes-users wrote:
> 'Max Andersen' via qubes-users:
>
>> I can actually put in an older wireless usb in the machine, and it sees it with lsusb in dom0, but I Dont know how To enable it in vm
> In dom0, use qvm-usb to try to attach that device to sys-net. Some USB
> devices don't passthrough very well, though.
[max@dom0 ~]$ qvm-usb
BACKEND:DEVID DESCRIPTION USED BY
[max@dom0 ~]$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS
802.11n Wireless Network Adapter
Bus 001 Device 005: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 046d:c318 Logitech, Inc. Illuminated Keyboard
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 8087:0026 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[max@dom0 ~]$
>> Tried qvm-pci
>>
>> It showed usb controller on that?
>>
>> When runming qvm-pci a sys-net-clone-1 dom0:00_14.0 it failed with got empty response from qubesd and hung
> You might be trying to attach the USB controller itself to
> sys-net-clone-1. This can work, if you're sure nothing else is on it
> (like your keyboard & mouse). Many systems only have one controller
> though, so try USB passthrough first.
Sincerely
Max
Frédéric Pierret
I used to build newer ISO in the past for such troubles with kernel-latest embedded. If you are interested, I can build you an 4.0.3 with kernel-latest-5.6 for try?
Best,
Max Andersen
> Den 14. apr. 2020 kl. 08.02 skrev Frédéric Pierret <frederic...@qubes-os.org>:
>
> Hi,
I would love to build it on my own, so I can do it in the future, since my hardware is so new
Thank you very much
Max
Frédéric Pierret
On 2020-04-15 08:09, Max Andersen wrote:
>
>
>> Den 14. apr. 2020 kl. 08.02 skrev Frédéric Pierret <frederic...@qubes-os.org>:
>>
>> Hi,
>> I used to build newer ISO in the past for such troubles with kernel-latest embedded. If you are interested, I can build you an 4.0.3 with kernel-latest-5.6 for try?
>
> When I try, the builder script fails horribly. Can you write a stepguide? Maybe just commands and selections on how you build it(if it is not too much of a hassle)?
1) In a working directory, e.g. `/home/user/`, clone `qubes-builder`:
git clone https://github.com/QubesOS/qubes-builder
2) Download specific builder conf file for such process:
wget https://raw.githubusercontent.com/QubesOS/qubes-release-configs/master/R4.0/qubes-os-iso-full-online.conf -O /home/user/qubes-builder/builder.conf
3) Enable QubesOS testing packages for the build and specify release branch for the installer:
echo 'USE_QUBES_REPO_TESTING=1' >> /home/user/qubes-builder/builder.conf
echo 'BRANCH_installer_qubes_os=release4.0' >> /home/user/qubes-builder/builder.conf
4) Get sources:
cd /home/user/qubes-builder/
make get-sources
5) Enable `kernel-latest` in the ISO build process:
sed -i 's#\(<packagereq type="\)optional\(">kernel-latest.*$\)#\1mandatory\2#' qubes-src/installer-qubes-os/conf/comps-qubes.xml
6) Build ISO:
make iso
7) Get your freshly built ISO in `/home/user/qubes-builder/iso`
The current kernel-5.6 is still at PR stage. If you want to try it you need to build it:
3.1) Add `linux-kernel` in `COMPONENTS`:
echo 'COMPONENTS+=linux-kernel'
3.2) Change URL and BRANCH of the git repository:
echo 'URL_linux_kernel=https://github.com/fepitre/qubes-linux-kernel' >> /home/user/qubes-builder/builder.conf
echo 'BRANCH_linux_kernel=kernel-5.6' >> /home/user/qubes-builder/builder.conf
4.1) Get sources of it:
make get-sources
4.2) Build it:
make linux-kernel
Those extra steps X.Y) can be added into the whole ISO build process. Else, it can be done after you have installed the ISO previously built (or downloaded ISO from official website) with official Qubes packages and install the built kernel manually by copying the RPMs create into `/home/user/qubes-builder/qubes-src/linux-kernel/pkgs/dom0-fc25/x86_64/`.
I've probably written typo. Don't hesitate to ask in any case.
Best,
Frédéric
Max Andersen
On 2020-04-15 08:09, Max Andersen wrote:Den 14. apr. 2020 kl. 08.02 skrev Frédéric Pierret <frederic...@qubes-os.org>: Hi, I used to build newer ISO in the past for such troubles with kernel-latest embedded. If you are interested, I can build you an 4.0.3 with kernel-latest-5.6 for try?When I try, the builder script fails horribly. Can you write a stepguide? Maybe just commands and selections on how you build it(if it is not too much of a hassle)?Sure, here are the procedure for building latest Qubes 4.0.3 ISO with already built packages (templates included) using Qubes OS official repositories: 1) In a working directory, e.g. `/home/user/`, clone `qubes-builder`: git clone https://github.com/QubesOS/qubes-builder 2) Download specific builder conf file for such process: wget https://raw.githubusercontent.com/QubesOS/qubes-release-configs/master/R4.0/qubes-os-iso-full-online.conf -O /home/user/qubes-builder/builder.conf 3) Enable QubesOS testing packages for the build and specify release branch for the installer: echo 'USE_QUBES_REPO_TESTING=1' >> /home/user/qubes-builder/builder.conf echo 'BRANCH_installer_qubes_os=release4.0' >> /home/user/qubes-builder/builder.conf 4) Get sources: cd /home/user/qubes-builder/ make get-sources 5) Enable `kernel-latest` in the ISO build process: sed -i 's#\(<packagereq type="\)optional\(">kernel-latest.*$\)#\1mandatory\2#' qubes-src/installer-qubes-os/conf/comps-qubes.xml 6) Build ISO: make iso
[user@qubes-builder qubes-builder]$ make iso
-> Preparing for ISO build...
--> Removing old rpms from the installer repos...
which: no createrepo_c in
(/home/user/.local/bin:/home/user/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/home/user/qubes-builder/qubes-src/builder-rpm/tools)
which: no createrepo in
(/home/user/.local/bin:/home/user/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/home/user/qubes-builder/qubes-src/builder-rpm/tools)
---> Cleaning up repo: dom0-updates...
./clean_repos.sh: line 6: -q: command not found
---> Cleaning up repo: installer...
./clean_repos.sh: line 6: -q: command not found
---> Cleaning up repo: qubes-dom0...
./clean_repos.sh: line 6: -q: command not found
make[1]: *** [Makefile:80: clean-repos] Error 127
make: *** [Makefile:485: iso.clean-repos] Error 2
[user@qubes-builder qubes-builder]$
Do I need some libraries or something?
Sincerely
Max
Frédéric Pierret
> When running make iso I get:
>
> [user@qubes-builder qubes-builder]$ make iso
> -> Preparing for ISO build...
> --> Removing old rpms from the installer repos...
> which: no createrepo_c in (/home/user/.local/bin:/home/user/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/home/user/qubes-builder/qubes-src/builder-rpm/tools)
> which: no createrepo in (/home/user/.local/bin:/home/user/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/home/user/qubes-builder/qubes-src/builder-rpm/tools)
> ---> Cleaning up repo: dom0-updates...
> ./clean_repos.sh: line 6: -q: command not found
> ---> Cleaning up repo: installer...
> ./clean_repos.sh: line 6: -q: command not found
> ---> Cleaning up repo: qubes-dom0...
> ./clean_repos.sh: line 6: -q: command not found
> make[1]: *** [Makefile:80: clean-repos] Error 127
> make: *** [Makefile:485: iso.clean-repos] Error 2
> [user@qubes-builder qubes-builder]$
>
> Do I need some libraries or something?
make install-deps
Here it seems that 'createrepo' or 'createrepo_c' is not installed.
Hum a little fix in the script 'clean_repos.sh' is needed for proper exit and message. I'll fix that.
Best,
Frédéric
> Sincerely
>
> Max
>
Max Andersen
I cloned a new machine from the newest fedora-template-31, so I know what is needed in the newest build.
Running make install-deps. installing :
Installed:
annobin-8.78-3.fc31.x86_64
createrepo_c-0.15.5-1.fc31.x86_64
createrepo_c-libs-0.15.5-1.fc31.x86_64
drpm-0.4.1-1.fc31.x86_64
dwz-0.12-11.fc31.x86_64
efi-srpm-macros-4-3.fc31.noarch
elfutils-0.179-1.fc31.x86_64
fonts-srpm-macros-2.0.3-1.fc31.noarch
fpc-srpm-macros-1.2-2.fc31.noarch
gdb-minimal-8.3.50.20190824-30.fc31.x86_64
ghc-srpm-macros-1.5.0-1.fc31.noarch
gnat-srpm-macros-4-10.fc31.noarch
go-srpm-macros-3.0.8-4.fc31.noarch
libmodulemd-2.9.1-1.fc31.x86_64
nim-srpm-macros-3-1.fc31.noarch
ocaml-srpm-macros-5-6.fc31.noarch
openblas-srpm-macros-2-6.fc31.noarch
patch-2.7.6-11.fc31.x86_64
perl-Digest-SHA-1:6.02-440.fc31.x86_64
perl-srpm-macros-1-33.fc31.noarch
python-srpm-macros-3-54.fc31.noarch
python3-sh-1.12.14-13.fc31.noarch
qt5-srpm-macros-5.13.2-1.fc31.noarch
redhat-rpm-config-143-1.fc31.noarch
rpm-build-4.15.1-1.fc31.x86_64
rpm-sign-4.15.1-1.fc31.x86_64
rpmdevtools-8.10-9.fc31.noarch
rust-srpm-macros-13-1.fc31.noarch
xemacs-filesystem-21.5.34-34.20190323hgc0ed7ef9a5a1.fc31.noarch
zstd-1.4.4-1.fc31.x86_64
New error emerges:
[user@qubes-builder qubes-builder]$ make iso
-> Preparing for ISO build...
--> Removing old rpms from the installer repos...
---> Cleaning up repo: dom0-updates...
---> Cleaning up repo: installer...
---> Cleaning up repo: qubes-dom0...
--> Copying installer-qubes-os RPMs...
ln: failed to access
'pkgs/dom0-fc25/noarch/pykickstart-2.32-4.fc25.noarch.rpm': No
such file or directory
ln: failed to access
'pkgs/dom0-fc25/noarch/python-kickstart-2.32-4.fc25.noarch.rpm':
No such file or directory
ln: failed to access
'pkgs/dom0-fc25/noarch/python3-kickstart-2.32-4.fc25.noarch.rpm':
No such file or directory
ln: failed to access
'pkgs/dom0-fc25/noarch/python-blivet-2.1.11-6.fc25.noarch.rpm':
No such file or directory
ln: failed to access
'pkgs/dom0-fc25/noarch/python3-blivet-2.1.11-6.fc25.noarch.rpm':
No such file or directory
ln: failed to access
'pkgs/dom0-fc25/x86_64/lorax-25.19-1.fc25.x86_64.rpm': No such
file or directory
ln: failed to access
'pkgs/dom0-fc25/x86_64/lorax-lmc-virt-25.19-1.fc25.x86_64.rpm':
No such file or directory
ln: failed to access
'pkgs/dom0-fc25/x86_64/lorax-lmc-novirt-25.19-1.fc25.x86_64.rpm':
No such file or directory
ln: failed to access
'pkgs/dom0-fc25/x86_64/lorax-templates-generic-25.19-1.fc25.x86_64.rpm':
No such file or directory
ln: failed to access
'pkgs/dom0-fc25/noarch/lorax-templates-qubes-4.0.6-1.fc25.noarch.rpm':
No such file or directory
ln: failed to access
'pkgs/dom0-fc25/noarch/pungi-4.1.14-2.fc25.noarch.rpm': No such
file or directory
ln: failed to access
'pkgs/dom0-fc25/noarch/pungi-utils-4.1.14-2.fc25.noarch.rpm': No
such file or directory
ln: failed to access
'pkgs/dom0-fc25/x86_64/anaconda-25.20.9-17.fc25.x86_64.rpm': No
such file or directory
ln: failed to access
'pkgs/dom0-fc25/x86_64/anaconda-core-25.20.9-17.fc25.x86_64.rpm':
No such file or directory
ln: failed to access
'pkgs/dom0-fc25/x86_64/anaconda-gui-25.20.9-17.fc25.x86_64.rpm':
No such file or directory
ln: failed to access
'pkgs/dom0-fc25/x86_64/anaconda-tui-25.20.9-17.fc25.x86_64.rpm':
No such file or directory
ln: failed to access
'pkgs/dom0-fc25/x86_64/anaconda-widgets-25.20.9-17.fc25.x86_64.rpm':
No such file or directory
ln: failed to access
'pkgs/dom0-fc25/x86_64/anaconda-widgets-devel-25.20.9-17.fc25.x86_64.rpm':
No such file or directory
ln: failed to access
'pkgs/dom0-fc25/x86_64/anaconda-dracut-25.20.9-17.fc25.x86_64.rpm':
No such file or directory
ln: failed to access
'pkgs/dom0-fc25/x86_64/anaconda-debuginfo-25.20.9-17.fc25.x86_64.rpm':
No such file or directory
ln: failed to access
'pkgs/dom0-fc25/x86_64/anaconda-debugsource-25.20.9-17.fc25.x86_64.rpm':
No such file or directory
ln: failed to access
'pkgs/dom0-fc25/noarch/qubes-anaconda-addon-4.0.11-1.fc25.noarch.rpm':
No such file or directory
ln: failed to access
'pkgs/dom0-fc25/noarch/qubes-release-4.0-8.noarch.rpm': No such
file or directory
ln: failed to access
'pkgs/dom0-fc25/noarch/qubes-release-notes-4.0-8.noarch.rpm': No
such file or directory
ln: failed to access
'pkgs/dom0-fc25/noarch/qubes-dom0-dist-upgrade-2.0-2.noarch.rpm':
No such file or directory
make[1]: ***
[/home/user/qubes-builder/qubes-src/builder-rpm/Makefile.rpmbuilder:158:
update-repo-do] Error 1
make: *** [Makefile:493: iso.copy-rpms.installer-qubes-os] Error
2
[user@qubes-builder qubes-builder]$
Sincerely
Max
Frédéric Pierret
make iso COMPONENTS=linux-kernel
else
make iso COMPONENTS=
As 'installer-qubes-os' is in COMPONENTS of builder.conf it thinks that the packages have been built where as it downloaded it.
Max Andersen
It went quite well with 5.5.13, but not with 5.6. I get the error:
-> Updating sources for linux-kernel...
--> Fetching from
https://github.com/QubesOS/qubes-linux-kernel.git kernel-5.6...
fatal: Remote branch kernel-5.6 not found in upstream origin
The builder.conf contains:
vim: ft=make
VERBOSE ?= 2
BACKEND_VMM ?= xen
GIT_BASEURL ?= https://github.com
GIT_PREFIX ?= QubesOS/qubes-
RELEASE ?= 4.0
DIST_DOM0 ?= fc25
DISTS_VM ?=
COMPONENTS = \
installer-qubes-os \
linux-yum \
linux-kernel \
builder-rpm
BUILDER_PLUGINS ?= builder-rpm
USE_QUBES_REPO_VERSION = $(RELEASE)
INSTALLER_KICKSTART=/home/user/qubes-src/installer-qubes-os/conf/iso-full-online.ks
USE_QUBES_REPO_TESTING=1
BRANCH_installer_qubes_os=release4.0
URL_linux_kernel=https://github.com/fepitre/qubes-linux-kernel
BRANCH_linux_kernel=kernel-5.6
Thank you very much for your help. I really
appreciate it.
Sincerely
Max
Frédéric Pierret
>> -> Updating sources for linux-kernel...
>> --> Fetching from https://github.com/QubesOS/qubes-linux-kernel.git kernel-5.6...
>> fatal: Remote branch kernel-5.6 not found in upstream origin
>>
> There is a typo in 3.2. It should be :
>
> GIT_URL_linux_kernel=...
>
> instead of just
>
> URL_...
>
Frédéric Pierret
On 2020-04-16 22:55, Max Andersen wrote:
> On 4/16/20 10:46 PM, Frédéric Pierret wrote:
>> Also, if you wait a little bit, it will be in official repository soon. The PR has been merged few minutes ago and the build is in progress :)
>
> -> Updating sources for linux-kernel...
> --> Verifying tags...
> No valid signed tag found!
> make: *** [Makefile:204: linux-kernel.get-sources] Error 1
> [user@qubes-builder qubes-builder]$
>
It's because I don't sign commit tag. Please add NO_CHECK = 1 into builder.conf. BTW, don't hesitate to check documentation too.
Max Andersen
>>
> It's because I don't sign commit tag. Please add NO_CHECK = 1 into builder.conf. BTW, don't hesitate to check documentation too.
Sincerely
Max