You know, despite all 7.0 has been a HUGE improvement performance-wise
on my main laptop (it's the same one since 2010) compared to the 6.x
series and whatever was before.
I've just upgraded to 7.0.1, let's see how it works.
2016-09-14 18:17 GMT+03:00 :
> I feel that for home
I feel that for home users, -current may be a good choice.
netbsd 7.0 is entirely unusable on much of my hardware. desktop was
extra bad. no USB3 means USB keyboard interrupts are lost or something,
need to boot with ACPI disabled (disables hyperthreading), cannot install
from USB, lack of
2016-09-13 2:48 GMT+03:00 :
> No USB3 support on NetBSD-7.0. I had the same. Requires twiddling with
> BIOS options to even boot the installer.
> Hopefully 7.1 will have merged by release (planned), -current already
> does, and it works well.
>
In my case USB installation (7.0)
2016-09-12 1:13 GMT+03:00 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
No USB3 support on NetBSD-7.0. I had the same. Requires twiddling with
BIOS options to even boot the installer.
Hopefully 7.1 will have merged by release (planned), -current already
does, and it works well.
On 11 September 2016 at 23:13, Michael van Elst wrote:
> 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
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
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
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
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
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
2016-09-10 18:05 GMT+03:00 Andrei M. :
> No, this happened when the installation CD was loading. I've had
> exactly the same problem in the installation process last year, see
> attachment.
>
>
> 2016-09-10 2:49 GMT+03:00 Michael van Elst :
>>
On Fri, 9 Sep 2016 23:49:30 + (UTC)
mlel...@serpens.de (Michael van Elst) wrote:
> But neither should happen during installation. My guess is that
> sysinst didn't clean the disk and the screenshot comes from booting
> the installed system.
Or at least the original boot blocks which may not
swiftgri...@gmail.com (Swift Griggs) writes:
>I wonder what happened in his case. I can tell he's re-using the same box
>and drive from his FreeBSD install, but I've done that many times and
>never had a problem (other than being annoyed at 'dk' devices showing up).
>I just wipe the disk and
On Fri, 9 Sep 2016, D'Arcy J.M. Cain wrote:
> I always dd nulls to a disk that was used for another OS before starting
> a new install.
Same here.
> Specifically I have had issues installing NetBSD to a drive that had
> Linux (Red Hat) on it. It's been a while but I think that the behaviour
Mike Larabel of Phoronix had the same problem with installation of
NetBSD 7.0 a year ago:
http://www.phoronix.com/scan.php?page=news_item=BSD-Linux-Late-2015
In fact I experienced it last year myself, but some good guy told me
to change the BIOS settings for HD from SATA to legacy/IDE and after
http://www.phoronix.com/scan.php?page=article=trying-8-bsds=2
I wonder what happened in his case. I can tell he's re-using the same box
and drive from his FreeBSD install, but I've done that many times and
never had a problem (other than being annoyed at 'dk' devices showing up).
I just wipe
17 matches
Mail list logo