>> If it's an issue picking up the root filesystem, you could boot an
>> INSTALL type kernel with a built in ramdisk with dhcpcd and sshd
>> enabled, [...]
> Yes, I plan to test this also, depending on [...]
This reminds me of a case I had, once.
I wanted to test-boot a particular kernel version
Hello,
Le Fri, Aug 19, 2022 at 02:36:33PM +0100, David Brownlee a écrit :
> Tangentially...
>
> If it's an issue picking up the root filesystem, you could boot an
> INSTALL type kernel with a built in ramdisk with dhcpcd and sshd
> enabled, and see if you can ssh into the box (I think someone had
On Fri, Aug 19, 2022 at 01:52:47AM +, Taylor R Campbell wrote:
> All that said: What is the failure mode you're seeing for ihidev that
> blocks suspend?
It fails to read HID descriptor. The ihidev device remains unfunctionnal
and breaks suspend.
I thought about this workaround:
--- sys/dev/i
Tangentially...
If it's an issue picking up the root filesystem, you could boot an
INSTALL type kernel with a built in ramdisk with dhcpcd and sshd
enabled, and see if you can ssh into the box (I think someone had
pre-built arm images which did just that, so the code should be out
there :)
David
Date:Fri, 19 Aug 2022 12:40:11 +0200
From:=?UTF-8?Q?Pawe=c5=82_Cichowski?=
Message-ID: <56898e46-7714-200b-4528-afffddd6d...@3mdeb.com>
| I've built the kernel and release for evbarm aarch64 from the latest
| sources and ran it on QEMU. Unfortunately, /dev/efi wa
First of all, thank you for your detailed response to my previous message.
I have conducted some more research on how to extend EFI support and
general kernel hacking. I would like to ask you some more questions,
mainly concerning modifying the kernel, since this is my first time
trying it.
