Re: Phoronix 8-way-BSD-install - NetBSD bombed

2016-09-11 Thread Michael van Elst
lingvofact...@gmail.com ("Andrei M.") writes: >> That's why it might be interesting to find out why ahcisata fails for you. >Are there any kernel debug facilities on the installation distro? Not much. You can boot the kernel with the -x parameter, but capturing the dmesg output without a serial

Re: NPF NAT port range behaviour

2016-09-11 Thread Eric Garver
Hi brkt, I've also been using NPF and hit pretty much the same thing. On Sat, Sep 10, 2016 at 07:39:56PM -0700, brkt wrote: > I've been using NPF as a gateway router for my homelab for a number of weeks > now, after a positive experience using it+fail2ban on my homeserver. > > What I've run

Re: Phoronix 8-way-BSD-install - NetBSD bombed

2016-09-11 Thread Andrei M.
2016-09-11 23:40 GMT+03:00 Michael van Elst : > lingvofact...@gmail.com ("Andrei M.") writes: > >>As I previousy wrote, I switched from SATA to IDE mode in BIOS (after >>which everything started working), so the system no longer recognizes >>ahcisata. Here's the output for my

Re: Phoronix 8-way-BSD-install - NetBSD bombed

2016-09-11 Thread Michael van Elst
lingvofact...@gmail.com ("Andrei M.") writes: >As I previousy wrote, I switched from SATA to IDE mode in BIOS (after >which everything started working), so the system no longer recognizes >ahcisata. Here's the output for my HD and CD: That's why it might be interesting to find out why ahcisata

Re: Phoronix 8-way-BSD-install - NetBSD bombed

2016-09-11 Thread Andrei M.
As I previousy wrote, I switched from SATA to IDE mode in BIOS (after which everything started working), so the system no longer recognizes ahcisata. Here's the output for my HD and CD: wd0 at atabus0 drive 0 wd0: wd0: drive supports 16-sector PIO transfers, LBA48 addressing wd0: 465 GB, 969021

Re: Phoronix 8-way-BSD-install - NetBSD bombed

2016-09-11 Thread Michael van Elst
lingvofact...@gmail.com ("Andrei M.") writes: >No, this happened when the installation CD was loading. I've had >exactly the same problem in the installation process last year, see >attachment. The screenshot shows two SATA devices that couldn't be recognized. one USB umass device. The