Re: Snapshot crash on boot, "entry point at: 0x1001000" (Intel Gemini Lake)
On Fri, Oct 09, 2020 at 03:37:37PM +0400, Michel von Behr wrote: > Hi all, > I'm trying to run snapshot on a Chuwi Lapbook laptop (Intel Gemini Lake), > but I get stuck at boot time with the message "entry point at: 0x1001000". > Based on previous discussions [1] it looks like the problem is with > BOOTX64.EFI > For now I'll be running -stable, but I would like to follow -current. Is > there a way to run -current with an old version of BOOTX64.EFI for example? > (i.e., the only alternatives I'm seeing is either 1) compiling a GENERIC > kernel with the older version of BOOTX64.EFI src, or 2) (try to) compile a > custom/smaller kernel to avoid the issue). > > [1] https://marc.info/?l=openbsd-misc=159147446008114=2 > > Any pointing to the right direction is welcome. I had the same problem with EFI on ASRock J4105M system, essentially failing to boot a kernel larger than certain size. I posted my solution here: https://marc.info/?l=openbsd-misc=159401011632149=2 I guess the patch requires more testing before asking for it to be committed. Thanks, Kastus
Snapshot crash on boot, "entry point at: 0x1001000" (Intel Gemini Lake)
Hi all, I'm trying to run snapshot on a Chuwi Lapbook laptop (Intel Gemini Lake), but I get stuck at boot time with the message "entry point at: 0x1001000". Based on previous discussions [1] it looks like the problem is with BOOTX64.EFI For now I'll be running -stable, but I would like to follow -current. Is there a way to run -current with an old version of BOOTX64.EFI for example? (i.e., the only alternatives I'm seeing is either 1) compiling a GENERIC kernel with the older version of BOOTX64.EFI src, or 2) (try to) compile a custom/smaller kernel to avoid the issue). [1] https://marc.info/?l=openbsd-misc=159147446008114=2 Any pointing to the right direction is welcome. Regards, Michel
Re: relayd doesn't load keypair with two listen statements
Anybody else seeing this?
Mischa
> On 20 Dec 2019, at 15:54, Mischa wrote:
>
> Hi All,
>
> When using the following config for relayd, the keypair is not loaded twice.
> Without 'keypair' and using the default way, .crt and
> .crt in /etc/ssl and /etc/ssl/private it's working as expected.
>
> Is this expected behavior?
>
> ###
> table { 127.0.0.1 }
> ext_v4 = "46.xx.xx.130"
> ext_v6 = "2a03::xxx::130"
> http protocol httpfilter {
>tcp { nodelay, sack }
>pass request quick path "/.well-known/acme-challenge/*" forward to
>
> }
> http protocol httpsfilter {
>tcp { nodelay, sack }
>tls { keypair test.high5.nl, ciphers
> "kEECDH:!AESGCM:!aNULL:!SHA1:!MD5:@STRENGTH", no client-renegotiation }
> }
> relay default {
>listen on $ext_v4 port 80
>listen on $ext_v6 port 80
>protocol httpfilter
>forward to port 80
>forward to port 3129
> }
> relay default_tls {
>listen on $ext_v4 port 443 tls
>listen on $ext_v6 port 443 tls
>protocol httpsfilter
>forward to port 443
> }
> ###
>
> test# relayd -d -
> startup
> socket_rlimit: max open files 1024
> socket_rlimit: max open files 1024
> socket_rlimit: max open files 1024
> relay_load_certfiles: using certificate /etc/ssl/test.high5.nl.crt
> relay_load_certfiles: using private key /etc/ssl/private/test.high5.nl.key
> /etc/relayd.conf:22: cannot load certificates for relay default_tls4:443
> socket_rlimit: max open files 1024
> pfe: filter init done
> hce exiting, pid 30862
> pfe exiting, pid 39056
> ca exiting, pid 87123
> ca exiting, pid 32013
> ca exiting, pid 78073
> relay exiting, pid 24340
> relay exiting, pid 4410
> relay exiting, pid 14486
