miniroot66.fs failed to boot

2019-10-22 Thread Zen Floater2
I have a new laptop with an I7 processor and UEFI miniroot66.fs failed to boot up so I could install OpenBSD 6.6. I have Trisquel 8 installed and running on this laptop and have attached two files describing the cpu architecture and this machines hardware. I have also made a video of the

Re: Kernel panic upon resume of Linux/KVM VM (OpenBSD 6.6)

2019-10-22 Thread Mike Larkin
On Tue, Oct 22, 2019 at 04:25:19PM -0700, guent...@openbsd.org wrote: > On Tue, 22 Oct 2019, Andreas Rottmann wrote: > > >Synopsis: panic: pvclock0: unstable result on stable clock > > >Category: virtualization > > >Environment: > > System : OpenBSD 6.6 > > Details : OpenBSD 6.6

Re: Kernel panic upon resume of Linux/KVM VM (OpenBSD 6.6)

2019-10-22 Thread guenther
On Tue, 22 Oct 2019, Andreas Rottmann wrote: > >Synopsis:panic: pvclock0: unstable result on stable clock > >Category:virtualization > >Environment: > System : OpenBSD 6.6 > Details : OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT > 2019 >

Re: 6.6 on Hetzner: arpresolve: 172.31.1.1: route contains no arp information

2019-10-22 Thread jajiss
Hello, I have the same issue. I never cared about IPv6 so the rest is only IPv4 relevant. I used hetzner from 6.2 to 6.5 without issues. Starting with 6.6 IPv4 does not work out of the box and needs the suggested workaround. This includes system upgraded with sysupgrade, system upgraded with

xterm dumped core on pasting huge X selection

2019-10-22 Thread Klemens Nanni
Running regular snaps on my X230: OpenBSD 6.6 (GENERIC.MP) #369: Fri Oct 11 11:04:11 MDT 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP tl;dr: As a last resort, I tried to paste 2.3M of data from my local X selection (xterm1) onto a remote machine (xterm2) through

Kernel panic upon resume of Linux/KVM VM (OpenBSD 6.6)

2019-10-22 Thread Andreas Rottmann
Hi! >Synopsis: panic: pvclock0: unstable result on stable clock >Category: virtualization >Environment: System : OpenBSD 6.6 Details : OpenBSD 6.6 (GENERIC.MP) #372: Sat Oct 12 10:56:27 MDT 2019

Re: Connection issues when connected via Wifi

2019-10-22 Thread mailinglists
> I don't know. Repeaters are not properly standardized in IEEE802.11. > I don't think interop is guaranteed between products from different vendors. > Perhaps you were supposed to buy all your devices from Fritz and use their > proprietary drivers for this to work? After doing some test with the

Re: problem with athn driver

2019-10-22 Thread victor
Hello, The wifi works ok with an upgrade to 6.6 release. Victor. On 10/15/19 12:19 PM, victor wrote: Sorry. First time I send a bug. I'm not a programmer. I've compiled with 1.100 and 1.101 revisions 1.100: following messages appears at startup: athn0: could not wakeup chip athn0: unable

Re: Connection issues when connected via Wifi

2019-10-22 Thread Stefan Sperling
On Tue, Oct 22, 2019 at 05:05:24PM +, mailinglists wrote: > Hello, > > thank you very much for your support. > With your explanation I found the causer. > It is my WiFi Repeater (Fritz!Wlan Repeater 1160). > If I connecting directly to my AP, the connection works fine and > "netstat -W iwn"

Re: 6.6 on Hetzner: arpresolve: 172.31.1.1: route contains no arp information

2019-10-22 Thread Lauri Tirkkonen
On Fri, Oct 18 2019 12:45:54 +0300, Lauri Tirkkonen wrote: > Hi, I updated one of my OpenBSD VM's hosted on Hetzner to 6.6 using > sysupgrade. After upgrade the network stopped working. > > The following message repeats in dmesg (106 times, before I worked > around it): > > arpresolve: