Re: PF: can't make queueing and priority work as expected

[Craig Skinner]

On 2016-01-15 Fri 12:53 PM |, David Gwynne wrote:
> > On 13 Jan 2016, at 19:19, Marko Cupa??  wrote:
> >
> > Have we come to conclusion that currently prio makes no sense at all?
> 
> it wont have the effect you want. that doesn't mean it doesn't make sense
> somewhere else.
> 

Such as an ADSL PPPoE bridge?
-- 
The older a man gets, the farther he had to walk to school as a boy.

Re: PF: can't make queueing and priority work as expected

[Marko Cupać]

On Fri, 15 Jan 2016 21:57:15 +1000
David Gwynne  wrote:

> the other thing to note is that loading a ruleset resets the
> assignment of existing states to queues.
>
> states are assigned to queues via rules, but if the rules go away
> (which is what happens when you load a new ruleset) the intermediary
> between rules and queues has gone.

I noticed states in systat states which have '*' as RULE, and noticed
behaviour you explained (traffic being in different queue than stated
in loaded ruleset) in systat queues.

> it kind of sucks, especially for testing.

I don't mind having to flush states or even reboot complete system.
Would be better if not, but definitely not a show stopper.

I just gave another look to earlier thread Atanas posted link to:
http://marc.info/?l=openbsd-misc=141085207225887=2

I have not yet tried i386, but I'll give it a try today and post
results back.

--
Before enlightenment - chop wood, draw water.
After  enlightenment - chop wood, draw water.

Marko Cupać
https://www.mimar.rs/

Re: Installer exits after selecting root disk

[Marko Cupać]

On Fri, 15 Jan 2016 09:20:48 +0100
Jan Stary  wrote:

> On Jan 14 18:14:18, marko.cu...@mimar.rs wrote:
> > Hi,
> >
> > I am trying to install OpenBSD 5.8 release on sdcard of PC Engines
> > apu1d, but installer exits after selecting root disk, leaving me in
> > prompt:
> >
> > ---cut-here---
> > Available disks are: sd0 sd1.
> > Which disk is the root disk? ('?' for details) [sd0] sd1
> > Disk: sd1   geometry: 1911/255/63 [30703616 Sectors]
> > Offset: 0   Signature: 0xAA55
> > Starting Ending LBA Info:
> >  #: id  C   H   S -  C   H   S [
> >
> > #
> > ---cut-here---
> >
> > I changed sdcard, tried to install both from usb thumb drive (fs)
> > and usb optical drive (iso), with the same result. I tried both
> > i386 and amd64. Needless to say, checksums of downloaded iso/fs are
> > correct.
> >
> > Strangely enough, I've recently installed a few apu1d's the same way
> > without problem. The only difference is power adapter - I am not
> > using the one from PC Engines now, but generic one with same
> > specification instead.
> >
> > Could power adapter cause such behaviour? If not, what could?
>
> My Alix1C was failing with disk operations,
> I sent it to PC engines, they said it was a bad adaptor,
> sent it back with a new one (and a chocolate)
> and the problems disappeared.
>
> I have also seen an ALIX1D rebooting for no reason with a generic
> adapter, which disappeared after I replaced it with the original one.
>
> I don't know if yours is the case too,
> but would definitely try it.
>

I will definitely replace generic with original one.

I tried with another apu1d which was already installed succesfully
before and it failed too. Just as I was starting to get really nervous
about it, I remembered that successful installation was done from
ancient laptop with integrated serial port and serial cable, while
failing installation is being done from modern ultrabook with
USB-to-Serial adapter. I switched to old laptop + serial and
installation finished fine.

Perhaps it will be interesting to someone: when I switched to baud rate
of 9600, installer exited at 'do you wish to create user' prompt. I
guess my particular model of USB-to-Serial has issues. Strangely
enough, same behaviour was seen from both Linux/xfce4-terminal and
Windows/putty.
--
Before enlightenment - chop wood, draw water.
After  enlightenment - chop wood, draw water.

Marko Cupać
https://www.mimar.rs/

Re: Asrock Rack C2750D4I -- unsupported watchdog ?

[Stuart Henderson]

On 2016-01-15, Brendan Horan  wrote:
> One thing I would like to get working if I can is the watchdog.

> acpi0: tables DSDT FACP FPDT FIDT HPET AAFT SPMI MCFG WDAT UEFI APIC BDAT SSDT


The watchdog is described in the ACPI "Watch Dog Action Table" (WDAT),
it will need code writing to support this. The specification is at
https://msdn.microsoft.com/en-us/windows/hardware/gg463320.aspx

Re: 5.8: uvideo has support for Logitech QuickCam Pro 5000 but ugen0 attaches instead

[Martin Pieuchot]

On 06/01/16(Wed) 10:17, Martin Pieuchot wrote:
> On 05/01/16(Tue) 13:19, Matt Adams wrote:
> > On 05/01/16 05:10 AM, Martin Pieuchot wrote:
> > >On 03/01/16(Sun) 23:18, Matt Adams wrote:
> > >>Hi,
> > >>
> > >>I noted that uvideo has support for the Logitech QuickCam Pro 5000 - a 
> > >>piece
> > >>of hardware that I have. However, ugen appears to attach to this device
> > >>instead of allowing the special firmware (installed via "# fw_install
> > >>uvideo") to configure /dev/video0 or /dev/video1, even though those two
> > >>device files are present in the system.
> > >>
> > >>For example:
> > >>
> > >>-bash-4.3$ luvcview
> > >>luvcview version 2.0
> > >>Video driver: x11
> > >>A window manager is available
> > >>video /dev/video0
> > >>ERROR opening V4L interface
> > >>: Device not configured
> > >>
> > >>Is there something that I am missing here or is my webcam not actually
> > >>supported?
> > >Could you paste the output of "lsusb -v" for your webcam?  lsusb(1) is
> > >part of the usbutils package.
> > 
> > lsusb -v as follows (webcam portion only):
> > 
> > Bus 001 Device 002: ID 046d:08c5 Logitech, Inc. QuickCam Pro 5000
> > Device Descriptor:
> >   bLength18
> >   bDescriptorType 1
> >   bcdUSB   2.00
> >   bDeviceClass0 (Defined at Interface level)
> >   bDeviceSubClass 0
> >   bDeviceProtocol 1
> >   bMaxPacketSize064
> >   idVendor   0x046d Logitech, Inc.
> >   idProduct  0x08c5 QuickCam Pro 5000
> 
> Thanks, does the diff below help?

Could you test the diff?  Does it work?

> Index: uvideo.c
> ===
> RCS file: /cvs/src/sys/dev/usb/uvideo.c,v
> retrieving revision 1.183
> diff -u -p -r1.183 uvideo.c
> --- uvideo.c  20 Dec 2015 10:08:05 -  1.183
> +++ uvideo.c  6 Jan 2016 09:14:05 -
> @@ -382,6 +382,12 @@ struct uvideo_devs {
>   NULL,
>   UVIDEO_FLAG_VENDOR_CLASS
>   },
> + {   /* Incorrectly reports as bInterfaceClass=UICLASS_VENDOR */
> + { USB_VENDOR_LOGITECH, USB_PRODUCT_LOGITECH_QUICKCAMPRO5K_1 },
> + NULL,
> + NULL,
> + UVIDEO_FLAG_VENDOR_CLASS
> + },
>  };
>  #define uvideo_lookup(v, p) \
>   ((struct uvideo_devs *)usb_lookup(uvideo_devs, v, p))

Re: PF: can't make queueing and priority work as expected

[David Gwynne]

> On 15 Jan 2016, at 9:07 PM, Craig Skinner  wrote:
>
> On 2016-01-15 Fri 12:53 PM |, David Gwynne wrote:
>>> On 13 Jan 2016, at 19:19, Marko Cupa??  wrote:
>>>
>>> Have we come to conclusion that currently prio makes no sense at all?
>>
>> it wont have the effect you want. that doesn't mean it doesn't make sense
>> somewhere else.
>>
>
> Such as an ADSL PPPoE bridge?

yeah.

the other thing to note is that loading a ruleset resets the assignment of
existing states to queues.

states are assigned to queues via rules, but if the rules go away (which is
what happens when you load a new ruleset) the intermediary between rules and
queues has gone.

it kind of sucks, especially for testing.

dlg

Re: unbound(8) generating too many log messages

[Philippe Meunier]

Raf Czlonka wrote:
>How about simply disabling unbound at boot: [...]
>and then have something like this in your /etc/hostname.if:

Yes, I ended up disabling ntpd and un-enabling unbound in
/etc/rc.conf.local and then using:

/etc/rc.d/unbound -f start && /etc/rc.d/ntpd -f start

at the end of the script that I use to configure network interfaces.

Thanks.

Philippe

Opaque option in ospfctl show database

[Xavier Claude]

Hi all,

With ospfctl, there is an opaque option listed in show database:

$ doas ospfctl show database none
unknown argument: none
valid commands/args:
  
  area
  asbr
  external
  network
  router
  self-originated
  summary
  opaque   # < Here


However, there no mention in the man page
http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-5.8/man8/ospfctl.8?query=ospfctl=8=OpenBSD-5.8

What does it do ?

Thank you for your answer.
-- 
Xavier Claude
cont...@xavierclaude.be

smplayer 14.9 gets muted when moving or resizing windows in xfce 4.12

[bian]

When using smplayer version: 14.9.0 (svn r6994) under xfce 4.12 as 
supplied in stock obsd 5.8 moving or resizing a window mutes the sound. 
This happens under the condition that the checkboxes 'Hide content of 
windows [when moving] or [when resizing]' are ticked. Those boxes are 
found under the Settings -> Window Manager -> Advanced tab in the main 
xfce menu.


Muting occurs when resizing or moving the smplayer window or any other 
unrelated window. The problem is repeatable. When using vlc for playing 
a file and the boxes are ticked as above then there is no muting.



dmesg:
OpenBSD 5.8 (GENERIC.MP) #1236: Sun Aug 16 02:31:04 MDT 2015
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4139388928 (3947MB)
avail mem = 4010045440 (3824MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe9f80 (88 entries)
bios0: vendor Hewlett-Packard version "786G1 v01.16" date 03/05/2009
bios0: Hewlett-Packard HP Compaq dc7900 Convertible Minitower
acpi0 at bios0: rev 0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC ASF! MCFG TCPA SLIC HPET DMAR
acpi0: wakeup devices COM1(S4) COM2(S4) PCI0(S4) PEG1(S4) PEG2(S4) 
IGBE(S4) PCX1(S4) PCX2(S4) PCX5(S4) PCX6(S4) HUB_(S4) USB1(S3) USB2(S3) 
USB3(S3) USB4(S3) USB5(S3) [...]

acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz, 3159.13 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF,SENSOR

cpu0: 6MB 64b/line 16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 7 var ranges, 88 fixed ranges
cpu0: apic clock running at 332MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz, 3158.76 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF,PERF,SENSOR

cpu1: 6MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
acpimcfg0 at acpi0 addr 0xf400, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PEG1)
acpiprt2 at acpi0: bus -1 (PEG2)
acpiprt3 at acpi0: bus 32 (PCX1)
acpiprt4 at acpi0: bus -1 (PCX2)
acpiprt5 at acpi0: bus 48 (PCX5)
acpiprt6 at acpi0: bus -1 (PCX6)
acpiprt7 at acpi0: bus 7 (HUB_)
acpicpu0 at acpi0: !C2(500@17 mwait.3@0x10), C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: !C2(500@17 mwait.3@0x10), C1(1000@1 mwait.1), PSS
acpibtn0 at acpi0: PBTN
cpu0: Enhanced SpeedStep 3159 MHz: speeds: 3166, 1998 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Q45 Host" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel Q45 PCIE" rev 0x03: msi
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 0 function 0 "ATI Radeon X1600" rev 0x00
drm0 at radeondrm0
radeondrm0: apic 1 int 16
"ATI Radeon X1600 Sec" rev 0x00 at pci1 dev 0 function 1 not configured
"Intel Q45 HECI" rev 0x03 at pci0 dev 3 function 0 not configured
pciide0 at pci0 dev 3 function 2 "Intel Q45 PT IDER" rev 0x03: DMA 
(unsupported), channel 0 wired to native-PCI, channel 1 wired to 
native-PCI

pciide0: using apic 1 int 18 for native-PCI interrupt
pciide0: channel 0 ignored (not responding; disabled or no drives?)
pciide0: channel 1 ignored (not responding; disabled or no drives?)
puc0 at pci0 dev 3 function 3 "Intel Q45 KT" rev 0x03: ports: 1 com
com4 at puc0 port 0 apic 1 int 17: ns16550a, 16 byte fifo
com4: probed fifo depth: 15 bytes
em0 at pci0 dev 25 function 0 "Intel ICH10 D BM LM" rev 0x02: msi, 
address XXX
uhci0 at pci0 dev 26 function 0 "Intel 82801JD USB" rev 0x02: apic 1 int 
20
uhci1 at pci0 dev 26 function 1 "Intel 82801JD USB" rev 0x02: apic 1 int 
21
uhci2 at pci0 dev 26 function 2 "Intel 82801JD USB" rev 0x02: apic 1 int 
22
ehci0 at pci0 dev 26 function 7 "Intel 82801JD USB" rev 0x02: apic 1 int 
22

usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 0 "Intel 82801JD HD Audio" rev 0x02: msi
azalia0: codecs: Analog Devices AD1884A
audio0 at azalia0
ppb1 at pci0 dev 28 function 0 "Intel 82801JD PCIE" rev 0x02: msi
pci2 at ppb1 bus 32
ppb2 at pci0 dev 28 function 4 "Intel 82801JD PCIE" rev 0x02: msi
pci3 at ppb2 bus 48
uhci3 at pci0 dev 29 function 0 "Intel 82801JD USB" rev 0x02: apic 1 int 
20
uhci4 at pci0 dev 29 function 1 "Intel 82801JD USB" rev 0x02: apic 1 int 
21
uhci5 at pci0 dev 29 function 2 "Intel 82801JD USB" rev 0x02: apic 1 int 
22
ehci1 at pci0 dev 29 function 7 

Re: 5.8: uvideo has support for Logitech QuickCam Pro 5000 but ugen0 attaches instead

[Matt Adams]

On 15/01/16 05:44 AM, Martin Pieuchot wrote:

Could you test the diff? Does it work?

I haven't had a chance but I will as soon as I can. Thanks!

Matt

Re: dpb question for understanding.

[Josh Grosse]

On Sat, Jan 16, 2016 at 03:09:57AM +0100, Christoph R. Murauer wrote:
> Hello !
> 
> I used today dpb and readed also the man page. But I have a question
> as none developer / coder. I followed the FAQ and put 3 ports in the
> localfile. Everything builds fine. dpb is runned as root on a local
> drive used a tmpfs to build. All 3 ports are builded but only the
> first was installed (tried it re-running make install in the other
> port directories to verify everything was builded).
> 
> I also have no lock files in /usr/ports/logs/amd64/locks/. My question
> (maybe a stupid one) is now, how find I out, why dpb builds everything
> but installes only the first port (could someone point me please to
> the right logfile and for what I should watch there) ?
> 
> Thanks for answers.
> 
> P.S. : I let the dmesg this time.
 
See the -I option in the dpb(1) man page.  That installs a path or list
of paths to install.  Otherwise, dpb() will build packages, and those 
that remain installed at the completion of the build will only be 
the most recent packages built.  Packages which are unneeded (because
the are not build dependencies of the packages in queue for building)
are removed with pkg_delete(1) from time to time.  See the junk= and
-J options.

dpb question for understanding.

[Christoph R. Murauer]

Hello !

I used today dpb and readed also the man page. But I have a question
as none developer / coder. I followed the FAQ and put 3 ports in the
localfile. Everything builds fine. dpb is runned as root on a local
drive used a tmpfs to build. All 3 ports are builded but only the
first was installed (tried it re-running make install in the other
port directories to verify everything was builded).

I also have no lock files in /usr/ports/logs/amd64/locks/. My question
(maybe a stupid one) is now, how find I out, why dpb builds everything
but installes only the first port (could someone point me please to
the right logfile and for what I should watch there) ?

Thanks for answers.

P.S. : I let the dmesg this time.

RES: VXLAN in version 5.9

[Wolfz]

If somebody can test, would be great. I really think that this version is not
ok for vxlan.











De: minha-c...@uol.com.br 
[mailto:minha-c...@uol.com.br]
Enviada em: sexta-feira, 15 de janeiro de 2016 10:08
Para: 'R0me0 ***'  >
Assunto: RES: VXLAN in version 5.9



Yes!



De: R0me0 *** [mailto:knight@gmail.com]
Enviada em: sexta-feira, 15 de janeiro de 2016 05:18
Para: minha-c...@uol.com.br 
Assunto: Re: VXLAN in version 5.9



are you enabled ip_forward ?



sysctl net.inet.ip.forwarding=1









2016-01-15 2:13 GMT-02:00  >:

Hello,



Anybody already test vxlan in version 5.9 I reproduced
the same test with version 5.8 and everything is ok.



My lab is simple:



vxlan0 192.168.1.17 Machine1 em0 200.98.41.17  <->  em1
200.98.44.18 Machine2 vxlan0 192.168.1.19





I can see the packet vxlan arriving in destination but there
is not return. Both directions is the same thing. I do the same test, same
network with version 5.8 and is ok.



machine1

# ifconfig

lo0: flags=8049 mtu 32768

priority: 0

groups: lo

inet6 ::1 prefixlen 128

inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4

inet 127.0.0.1 netmask 0xff00

em0:
flags=18b43
mtu 1500

lladdr 00:50:56:bb:59:64

priority: 0

groups: egress

media: Ethernet autoselect (1000baseT full-duplex,master)

status: active

inet 200.98.41.17 netmask 0xff00 broadcast 200.98.41.255

em1: flags=18802 mtu 1500

lladdr 00:50:56:bb:43:9d

priority: 0

media: Ethernet autoselect (1000baseT full-duplex,master)

status: active

enc0: flags=0<>

priority: 0

groups: enc

status: active

vxlan0: flags=8843 mtu 1500

lladdr fe:e1:ba:d0:f0:53

priority: 0

groups: vxlan

media: Ethernet autoselect

status: active

tunnel: inet 200.98.41.17 -> 200.98.44.18 vnetid 1

inet 192.168.1.17 netmask 0xff00 broadcast 192.168.1.255

#

# pfctl -d

pfctl: pf not enabled

#







Machine2

# ifconfig

lo0: flags=8049 mtu 32768

priority: 0

groups: lo

inet6 ::1 prefixlen 128

inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4

inet 127.0.0.1 netmask 0xff00

em0: flags=18802 mtu 1500

lladdr 00:50:56:bb:67:e5

priority: 0

media: Ethernet autoselect (1000baseT full-duplex,master)

status: active

em1:
flags=18b43
mtu 1500

lladdr 00:50:56:bb:46:a7

priority: 0

groups: egress

media: Ethernet autoselect (1000baseT full-duplex,master)

status: active

   inet 200.98.44.18 netmask 0xff80 broadcast 200.98.44.127

enc0: flags=0<>

priority: 0

groups: enc

status: active

vxlan0: flags=8843 mtu 1500

lladdr fe:e1:ba:d0:e6:c1

priority: 0

groups: vxlan

media: Ethernet autoselect

status: active

tunnel: inet 200.98.44.18 -> 200.98.41.17 vnetid 1

inet 192.168.1.19 netmask 0xff00 broadcast 192.168.1.255

# pfctl -d

pfctl: pf not enabled

#





TCPDUMP



Machine1

root@200.98.41.17  's password:

Last login: Fri Jan 15 01:45:45 2016 from 200.221.130.5

OpenBSD 5.9-beta (GENERIC.MP  ) #1540: Fri Jan  8 10:48:32
MST 2016



Welcome to OpenBSD: The proactively secure Unix-like operating system.



Please use the sendbug(1) utility to report bugs in the system.

Before reporting a bug, please try to reproduce it with the latest

version of the code.  With bug reports, please try to ensure that

enough information to reproduce the problem is enclosed, and if a

known fix for it exists, include that as well.



# tcpdump -ni em0 port 4789

tcpdump: listening on em0, link-type EN10MB

02:00:23.386424 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]

02:00:25.274328 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]

02:00:27.400703 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]

02:00:29.245143 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]

02:00:31.393324 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]

02:00:54.806495 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]

02:00:56.867895 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]

02:00:58.799075 200.98.41.17.4789 > 200.98.44.18.4789: udp 50 [tos 0x10]

Re: Installer exits after selecting root disk

[Jan Stary]

On Jan 14 18:14:18, marko.cu...@mimar.rs wrote:
> Hi,
> 
> I am trying to install OpenBSD 5.8 release on sdcard of PC Engines
> apu1d, but installer exits after selecting root disk, leaving me in
> prompt:
> 
> ---cut-here---
> Available disks are: sd0 sd1.
> Which disk is the root disk? ('?' for details) [sd0] sd1
> Disk: sd1   geometry: 1911/255/63 [30703616 Sectors]
> Offset: 0   Signature: 0xAA55
> Starting Ending LBA Info:
>  #: id  C   H   S -  C   H   S [
> 
> #
> ---cut-here---
> 
> I changed sdcard, tried to install both from usb thumb drive (fs) and
> usb optical drive (iso), with the same result. I tried both i386 and
> amd64. Needless to say, checksums of downloaded iso/fs are correct.
> 
> Strangely enough, I've recently installed a few apu1d's the same way
> without problem. The only difference is power adapter - I am not using
> the one from PC Engines now, but generic one with same specification
> instead.
> 
> Could power adapter cause such behaviour? If not, what could?

My Alix1C was failing with disk operations,
I sent it to PC engines, they said it was a bad adaptor,
sent it back with a new one (and a chocolate)
and the problems disappeared.

I have also seen an ALIX1D rebooting for no reason with a generic adapter,
which disappeared after I replaced it with the original one.

I don't know if yours is the case too,
but would definitely try it.