Re: adding support for a possibly unsupported M.2 harddrive?

I forgot to send a follow-up to this: despite the disk itself not having a "proper" identifier in dmesg, I was able to get it to work without major issues while doing some other maintenancen work. Thanks for the advice and input everyone.

adding support for a possibly unsupported M.2 harddrive?

about (no prior device driver writing experience) adding this to NetBSD? or 2. Who / which list would I talk to and which details are necessary (so far I know fdisk and dmesg provide good details) to help with adding this to NetBSD? Cheers, ng0

fc-cache fails to build

Hi, last night I ran into this with my NetBSD amd64 clang system while building it. Has someone looked into this already? I did not find a matching bug report with just "fc-cache". If not, I would report it. # link fc-cache/fc-cache cc -O -DFONTCONFIG_PATH='"/usr/src/../obj/destdir.amd64/et

Re: usr.sbin/sysinst compile error

Martin Husemann transcribed 384 bytes: > On Wed, Jun 26, 2019 at 09:30:41AM +, n...@n0.is wrote: > > Okay, and how would I proceed without the build.sh running clean in obj > > first then? > > I've reads bits of build.sh but I am not sure if it was obvious to find. > > It does not do a clean

Re: usr.sbin/sysinst compile error

Martin Husemann transcribed 536 bytes: > On Wed, Jun 26, 2019 at 09:11:46AM +, n...@n0.is wrote: > > This is with ./build.sh ... -U distribution > > with the host system being on 8.99.42, built with clang, > > and this being relevant parts of mk.conf: > > Is there a "-u" in the "..." part of t

Re: usr.sbin/sysinst compile error

Martin Husemann transcribed 653 bytes: > On Wed, Jun 26, 2019 at 08:28:21AM +, n...@n0.is wrote: > > Christos Zoulas transcribed 234 bytes: > > > In article <20190625191514.qbcastohka3nxfos@uptimegirl>, > > > wrote: > > > >Hi, > > > > > > > >has someone commited a fix for this in the last 8

Re: usr.sbin/sysinst compile error

Christos Zoulas transcribed 234 bytes: > In article <20190625191514.qbcastohka3nxfos@uptimegirl>, wrote: > >Hi, > > > >has someone commited a fix for this in the last 8 hours or so > >since I've been compiling src? > > Have you cleaned in the sysinst directory? Yes, this happened with a clean /

usr.sbin/sysinst compile error

Hi, has someone commited a fix for this in the last 8 hours or so since I've been compiling src? # compile amd64/msg_defs.o /usr/src/../tools/bin/x86_64--netbsd-clang -O2 -fPIE -Os -std=gnu99 -Wno-sign-compare -Wno-pointer-sign -Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer

Re: iwm driver leads to kernel crash

Martin Husemann transcribed 430 bytes: > On Sat, Apr 27, 2019 at 04:18:20PM +, n...@n0.is wrote: > > It's an T440s, so one module can be exchanged, the other is soldered > > to the board. > > > > I can give exchanging the replacable one a try. > > I have had good experience with running memte

equivalent flag or code to MSG_MORE in NetBSD?

abstract if it helps. Cheers, ng0

Re: building base with clang

Martin Husemann transcribed 372 bytes: > On Wed, Jun 05, 2019 at 07:48:25AM +, n...@n0.is wrote: > > Hi, > > > > how good or bad is the base system with clang (ie, since > > gcc is the default is enough care taken to make the cvs > > build with clang without major breakages)? > > Depends on y

building base with clang

lding GCC alongside clang is not maintained? MKGCC=no # libraries MKLLVM=yes # libc++ MKLIBCXX=yes # clang HAVE_LLVM=yes # pkgsrc with clang PKGSRC_COMPILER=clang # pkgsrc clang location CLANGBASE=/usr Cheers, ng0

Re: iwm driver leads to kernel crash

s to me like a problem related to my wireless, as most > >crashes happened when I had the wifi card activated in the BIOS, > >some crashes - like crash 16, recent CVS state (build on thursday) - > >happen with it turned off. > >So I really have no idea what's going on here

Re: iwm driver leads to kernel crash

hes happened when I had the wifi card activated in the BIOS, some crashes - like crash 16, recent CVS state (build on thursday) - happen with it turned off. So I really have no idea what's going on here, if they all are related (I doubt it), and where to start. If I'm missing something

Re: iwm driver leads to kernel crash

Hi, would further dmesg outputs from the last 10 or so kernel crashes still be useful? This still keeps happening (workaround so far is to use ethernet). Or maybe I'm looking at the wrong kind of bug and there is something to track / being worked on already? n...@n0.is transcribed 452 bytes: > m

Re: iwm driver leads to kernel crash

m...@netbsd.org transcribed 280 bytes: > It's not iwm. I have the same bug reported but with re(4) which isn't > wireless even. the backtrace looks different from ddb. > from ddb, the failing instruction is, > > stopped at pid 276.1 (dhcpcd) at netbsd:npf_ifaddrhook+0x55: movq > 18(%r12), %

iwm driver leads to kernel crash

Hi, this behavior on an Lenovo Thinkpad started today after rebuilding the system yesterday. I'm not sure what else could help, this is the dmesg from the second kernel crash. msi5 vec 0 [ 1.053482] ehci0 at pci0 dev 29 function 0: vendor 8086 product 9c26 (rev. 0x04) [ 1.053482] ehci0: