Re: Creating /dev/dk* nodes so as to be persistent

I now notice a page on www.netbsd.org, NetBSD Documentation: Other FAQs and HOWTOs with a section on rebuilding /dev The /dev directory contains the necessary device files for accessing hardware and pseudo devices. If it becomes damaged, much strangeness can ensue. To rebuild the /dev

Re: Creating /dev/dk* nodes so as to be persistent

mueller6...@bellsouth.net (Thomas Mueller) writes: I wonder if rebuilding/updating the NetBSD system from source would fix the /dev. A rebuild would do nothing and I doubt that an update helps (but it would be a good feature). A reinstall (using sysinst) does help. After building

Re: Creating /dev/dk* nodes so as to be persistent

from Michael van Elst mlel...@serpens.de: mueller6...@bellsouth.net (Thomas Mueller) writes: After building the system from source and installing/copying the kernels, generic and custom, my installworld command was, or something like because +directory names were not always the same

Re: etcupdate and DESTDIR

On Wed, 20 Nov 2013, Thomas Mueller wrote: I look in man etcupdate and see nothing that supports updating /etc on a different partition. I recently encountered the same issue myself. In about two weeks, I'll be able to look at adding a -d DESTDIR option to etcupdate, unless

USB quirks: how to apply?

I believe some USB sticks and other USB devices have quirks that must be enabled to make the device work or work properly, but how is such a quirk applied? Or is it simply in the source code with no way to apply when running NetBSD(-current)? FreeBSD has /usr/sbin/usbconfig which has more

Re: READ ME: updating mpc, mpfr, and eventually gmp

Base gcc hasn't been updated. Updating mpc, mpfr, and gmp are part of the preparation for update base gcc. Segfault due to internal compiler error is often due to bad memory. You might want to run pkgsrc/sysutils/memtestplus. I tried again, this time noticed that the choking point was

Re: READ ME: updating mpc, mpfr, and eventually gmp

from Paul Goyette: I've had intermittent similar problems with NetBSD for at least three years now. I have no idea what the problem is, though. I've suspected some sort of memory corruption, but was never able to make any progress in tracking it down. It could be a corruption or bug in

Re: READ ME: updating mpc, mpfr, and eventually gmp

This is in particular a sudden inability to build NetBSD-current from source. could you be more explicit about what is failing? there shouldn't be any issues remaining, but some types of failure modes require cleaning out your build/obj trees, and won't go away with any amount of cvs

Re: READ ME: updating mpc, mpfr, and eventually gmp

Last failure was on gmp, which later built successfully as a dependency from pkgsrc. ah, i see the confusion here. my post was *only* about the in-tree gmp/mpfr/mpc that we use for the in-tree gcc and for building netbsd, and has nothing to do with the versions in

Re: NetBSD-HEAD amd64 refuses to build

On Mon, Dec 09, 2013 at 08:19:53AM +, mueller6...@bellsouth.net wrote: This time, using build.sh as always, I added -V MKLLVM=yes and HAVE_LLVM=yes to command line: For amd64, clang defaults to libc++, so you want -V MKLIBCXX=yes as well. Joerg Wiki didn't say that,

Re: NetBSD-HEAD amd64 refuses to build

Since -current had some hard times in the last few weeks, and maybe not everyone is aware of this site: http://releng.netbsd.org/cgi-bin/builds.cgi shows the status of the last autobuilds. We already had one working -current (HEAD) build this week, yay! As you

Building NetBSD system: what is PIGSGZIP?

I look at the build.sh command line in the build logs on http://releng.netbsd.org/cgi-bin/builds.cgi and at least for HEAD and netbsd-6, one parameter is USE_PIGZGZIP=yes What is this, and would it make a build succeed that would otherwise fail? I just used the search on netbsd.org and found

Re: READ ME: updating mpc, mpfr, and eventually gmp

This is in particular a sudden inability to build NetBSD-current from source. Those happen, and are usually fixed by reading UPDATING and doing what it recommends (or in the case of obvious breaks, waiting a day, updating and running the build again). -current is built by umpteen

Re: READ ME: updating mpc, mpfr, and eventually gmp

Matt Sporleder asks: What is your build.sh command? Did the build ever work? Latest build.sh command was === build.sh command:./build.sh -m amd64 -M ../obj.amd64.llvm -B nb20131214-llvm -T ../tooldir.amd64.llvm -V MKLLVM=yes -V HAVE_LLVM=yes -V MKLIBCXX=yes -U -j 9 distribution

Re: NetBSD-HEAD amd64 refuses to build

A clean build with no special options means at least this: * clean source tree, with no extra or modified files (it might be easiest to delete everything and check out a clean source tree); * no left over output files or temporary files from previous build attempts, such as TOOLDIR,

Re: NetBSD-HEAD amd64 refuses to build

On Dec 17, 1:16pm, Thomas Mueller wrote: } } A clean build with no special options means at least this: } } * clean source tree, with no extra or modified files (it might be } easiest to delete everything and check out a clean source tree); } * no left over output files or temporary

Re: NetBSD-HEAD amd64 refuses to build

| A different compiler I might use would be a newer version of gcc That can cause problems - or would if you really were using it the way that you believe... When building NetBSD, the compiler that needs to be on the host system (the one you're talking about) is used to build the

Re: NetBSD-HEAD amd64 refuses to build

On Sat, Dec 28, 2013 at 01:07:45PM +, Thomas Mueller wrote: After clearing src tree, but saving and putting back CVS subdirectory, I was able to redownload the src tree. I was then successful (?) building and installing NetBSD-current for i386 and amd64, building from amd64

Re: NetBSD-HEAD amd64 refuses to build

Just to ask the obvious: did you try without the -c, and if so, what happened? Sure I tried without -c, went into the debugger prompt. At point in the boot process did you end up in the debugger? (What was on the screen?) Did a backtrace bt give any clues? Cheers,

Re: NetBSD-HEAD amd64 refuses to build

Basically, I'm lost with the debugger, and the best I can do is type reboot. As Patrick suggested, please try typing bt in the debugger, to get a back-trace. Is there any documentation? Yes - see man 4 ddb But I don't think the debugger could really

Re: NetBSD-HEAD amd64 refuses to build

Thomas Mueller wrote: Where do I get a serial console, and how do I connect it to a computer when there are no serial ports? My suggestion would be not to bother with the serial console, but instead take a picture of the screen using a digital camera, type bt at the ddb prompt, take

Re: Mystery subject

/usr/src/lib/librumphijack/hijack.c:2462:1: error: redefinition of 'readlink' /usr/src/obj/destdir.amd64/usr/include/ssp/unistd.h:42:1: note: previous definition of 'readlink' was here *** [hijack.pico] Error code 1 nbmake[6]: stopped in /usr/src/lib/librumphijack 1 error nbmake[6]: stopped

Re: README - xorg xsrc updates happening.

just FYI, in case you didn't see already - i'm updating many of the xsrc components at the moment, so the tree may see breakage. please send-pr and/or send email to me/this list if you see breakage that a clean objdir doesn't fix. i'm pretty much done for now. there may be some

Xorg server version in base xsrc?

How do I find the xorg-server version in xsrc (base) as opposed to pkgsrc? I am mainly interested in NetBSD-current here. Since I use modular (pkgsrc) Xorg, I never see the xsrc version. I tried browsing the cvs source tree, it seems like the version might be 1.10.5, but it was not clear.

Re: Xorg server version in base xsrc?

On Tue, 22 Apr 2014, Thomas Mueller wrote: How do I find the xorg-server version in xsrc (base) as opposed to pkgsrc? See AC_INIT() macro, in xsrc/external/mit/xorg-server/dist/configure.ac regards, iain That led me to the right place: looks like 1.10.6 in HEAD

Atheros onboard AR9271 can't load firmware most of the time

I have MSI Z77 MPOWER motherboard, which includes Atheros AR9271 wi-fi chip, USB interface but part of the motherboard and not removable. I have USB-stick installations of NetBSD-current amd64 and i386, now at 6.99.40. A problem now and in the past is that the firmware fails to load most of

Re: updating pkg osabi/x11-links

Chavdar Ivanov wrote: Prior to updating osabi, I always force the removal of the packages which depend on it, then update osabi, then manually install the dependencies (in my case, x11-links, lsof and libgtop). I ended up doing so. Actually, while trying to remove x11-links I found the

Re: Atheros onboard AR9271 can't load firmware most of the time

On Mon, May 05, 2014 at 09:31:24PM -0700, Thomas Mueller wrote: I see through various device man pages that some firmwares are supposed to be in /etc/firmware, and some are supposed to be in /libdata/firmware. Why can't they all be in one or the other? Firmware was installed to /libdata

Re: Loading firmware for USB device after boot

On Fri, Jun 06, 2014 at 04:27:00AM +, Thomas Mueller wrote: Is it possible to load firmware for a USB device subsequent to boot? This is the drivers responsability (via the firmload(9) API). In this case, the USB device is a wireless network adapter, Atheros AR9271

USB 3.0 status in NetBSD-current?

Is there, or is there supposed to be, USB 3.0 support in the current kernel? I see xhci in kernel config, but have not yet been able to access anything on a USB 3.0 port. This would be for amd64 and i386 in my case. Tom

Re: DESTDIR support for etcupdate?

On Mon, 09 Jun 2014, Thomas Mueller wrote: Is there any way to run etcupdate for NetBSD on other than the current root? No, there is not. Adding DESTDIR support to etcupdate is on my to-do list. --apb (Alan Barrett) Good luck! Thanks for letting me know. I still wonder

Re: Loading firmware for USB device after boot

On Fri, Jun 06, 2014 at 04:27:00AM +, Thomas Mueller wrote: Is it possible to load firmware for a USB device subsequent to boot? This is the drivers responsability (via the firmload(9) API). In this case, the USB device is a wireless network adapter, Atheros AR9271

Scroll Lock on NetBSD-current amd64 and i386: different behavior

I've tried, at a text console, Scroll Lock, which then permits scrolling back some way with PageUp key on NetBSD-current i386, just like in FreeBSD, except that in FreeBSD, up- and down-arrow keys also work. But this does not work at all in NetBSD-current amd64. Is that a bug? I wouldn't

Finding version from src tree in HEAD

How do you find the NetBSD version to be built, like 6.99.43 or whatever it happens to be at the time, from the source tree? I know it must be somewhere, since the build log quickly finds it. Tom

Re: DESTDIR support for etcupdate?

On Mon, 09 Jun 2014, Thomas Mueller wrote: Is there any way to run etcupdate for NetBSD on other than the current root? Please try revision 1.56 of etcupdate, which now takes a -d destdir option. --apb (Alan Barrett) I browsed cvsweb.netbsd.org, found the new etcupdate 6 hours old

Re: USB 3.0 status in NetBSD-current?

That may not help. A USB2 cable should still leave you using the xhci driver - just at the lower speed. There is some 'magic' needed to hand over the port from ohci? to xhci (which probably require correct parsing of ACPI data to work out which usb2 port the xhci port is linked to). If

etcupdate destructive tricks

I've updated NetBSD-current system and notice that etcupdate wants to destroy some useful files. For instance, it wants to destroy /etc.rc.conf, throwing the user back to square zero (square one?). Also, /etc/master.passwd and /etc/ttys I'm watchful to what's happening, and know to hit d to

cvs update stopped by missing file or directory

I tried to update source tree but was stopped by cvs [update aborted]: cannot open directory /cvsroot/src/external/mit/lua/src: No such file or directory Is something temporarily missing at the server end, or did something get screwed at my end? Update command, from head of source tree, in

Re: cvs update stopped by missing file or directory

from my original post: I tried to update source tree but was stopped by cvs [update aborted]: cannot open directory /cvsroot/src/external/mit/lua/src: No such file or directory Is something temporarily missing at the server end, or did something get screwed at my end? Matthias Scheler

Re: Which X driver to use for genfb?

Paul Goyette wrote: For me, debugging the X code is just to much detail. I was hoping someone might have tried it before... Robert Swindells responded: I guess you will need to wait until riastradh@ finishes his drmkms work, if you want to try it out now you will need to add the microcode

Re: Wedges enabled on -current

Now that we have branched 7, I am planning to enable full wedge support for kernels that used wedges before. What this means is that disks with mbr and bsd labels will now create dkN devices for each partition in found. This should be generally transparent, because fstab offers backwards

Permission problems and questions on 7.99.1 and 7.0_BETA

I notice strange problems not being able to run things like mpop, msmtp, or even man as nonroot because of Permission denied on trying to create temporary file. Has anybody else noticed it? Problem was not present on NetBSD 6.99.44 amd64 and i386. Src and xsrc trees are on a FreeBSD

Criterion for version bump in HEAD?

I notice the numbering scheme for NetBSD-current versions, x.99.x but am curious about what determines when the rightmost component is bumped up, like 6.99.44 to 6.99.45 or 7.99.1 to 7.99.2 . Answer to this question won't make my NetBSD installations run any better or worse, but I'm still

Re: Build fails on extra files in DESTDIR, what does that mean?

from Ian D. Leroux: Passing the -r option to ./build.sh will force a clean of DESTDIR. That's good to know! I just went through ./build.sh again, see -r option clears both DESTDIR and TOOLDIR. I think the DESTDIR must have still had stuff from 6.99.40. Tom

Build fails on extra files in DESTDIR, what does that mean?

Trying to build NetBSD 7.99.10 amd64, i386, from 7.99.7 installation was stopped by === checkflist === distrib/sets cd /BETA1/netbsd-HEAD/usr/src/distrib/sets DESTDIR=/BETA1/netbsd-HEAD/usr/src/../obj/BETA1/netbsd-HEAD/usr/src/destdir.amd64 MACHINE=amd64

Change in xsrc and src tree structure?

When running cvs up -dP -A in /BETA1/netbsd-HEAD/usr/xsrc and /BETA1/netbsd-HEAD/usr/src I noticed many files no longer in repository, and it looked like there was some change in the xsrc and src tree structure regarding X11 and xsrc. What is now the version of native xorg-server? I am now

Re: Migrating from MBR to GPT?

from Thomas Klausner: > I've recently noticed that I have a 4TB disk in use of which I'm only > using 2TB. > # disklabel wd0 | tail -5 > 5 partitions: > #sizeoffset fstype [fsize bsize cpg/sgs] a: 4294965247 2048 RAID # (Cyl. 2*- 4294967295*)

Re: pkgsrc-2015Q3 released

Now that pkgsrc-wip has been moved to a git repository, how does a user who already has pkgsrc-wip by cvs update? I checked the URL, http://pkgsrc.org/wip/ , and this was not discussed. Or does the user just delete or move the cvs repository and git clone, fresh start? Tom

Status of xsrc/native X?

What is now the status of native vs. modular (pkgsrc) X in NetBSD-current? I seemed to read something about native X being deprecated in favor of pkgsrc X, but keep seeing xsrc in nightly build logs, and recently noticed a big upgrade in native X in xsrc tree as well as supporting files in src

Re: Can I use NetBSD as a desktop system?

On Mon, Jul 17, 2017 at 03:03:47PM -0300, SOUL_OF_ROOT 55 wrote: > Can I use NetBSD as a desktop system? > I used it for a few years, starting with NetBSD 4, and was pretty happy > about it. > Now I don't use because: > - My wifi is not supported, after my hardware changed. (NetBSD

How to get started with pkgsrc, or is it sh bug?

I can't seem to get started building anything with pkgsrc because nothing will build, can't get started. System is NetBSD-current amd64 (8.99.1), June 20, 2017, which may have a bearing because of a bug in /bin/sh and recent changes in SRCDIR/bin/sh. On a pristine system, there is no

Re: How to get started with pkgsrc, or is it sh bug?

from Patrick Welche: On Fri, Jul 21, 2017 at 07:14:44AM +, Thomas Mueller wrote: > System is NetBSD-current amd64 (8.99.1), June 20, 2017, > sh: /usr/pkg/sbin/pkg_info: not found > sh: /usr/pkg/sbin/pkg_admin: not found For me: $ which pkg_info

Re: How to get started with pkgsrc, or is it sh bug?

from Patrick Welche: On Fri, Jul 21, 2017 at 07:14:44AM +, Thomas Mueller wrote: > System is NetBSD-current amd64 (8.99.1), June 20, 2017, > sh: /usr/pkg/sbin/pkg_info: not found > sh: /usr/pkg/sbin/pkg_admin: not found For me: $ which pkg_info

Re: UEFI status?

Excerpt from SAITOH Masanobu: > I've not used grub2. If someone(TM) succeeded booting with grub2, it would be > good to summarize the howto. I haven't tried to boot NetBSD with UEFI, only legacy. But it works (legacy boot at least) with grub2; I use Super Grub2 Disk image on older versions of

DRM error in cpt_serr_int_handler, failure to boot NetBSD 7.99.71

Trying to boot a newly-updated NetBSD-7.99.71 installation fell short on a computer with Intel Ivy Bridge CPU, for both amd64 and i386. Generic kernel went into immediate reboot with no messages showing, while my custom kernel failed at or near the end. No /var/run/dmesg.boot, but I was able

Re: re0 watchdog timeouts

FreeBSD also has some problems with Ethernet re driver, at least on some versions of the Realtek 8111/8168/8169 chip. > On Mon, May 15, 2017 at 11:19:55PM -0700, Soren Jacobsen wrote: > > On 05/16 12:27, sc dying wrote: > > > Is the condition at line 1919 of ic/rtl8169.c inverted? > > > It

Re: re0 watchdog timeouts

> Hauke Fath wrote: > > messages, and network access ground to a halt with a 02 May 7.99.71 > > kernel. No re0 related messages after reverting if_re_pci.c to v1.46. > I instead found that sys/dev/ic/rtl8169.c has the issue > I have identified the breakage date of the file >

NetBSD-current amd64 with dhcpcd connects only partially

On my latest NetBSD-current amd64 installation, from the small hours June 11, I get mixed results with re(4) driver and wonder if there is any dhcpcd tweak that will help. On motherboard MSI Z68MA-ED55(B3), Realtek 8111E/8168 Ethernet chip, "dhcpcd re0" connects OK, local network and outside.

NetBSD-current amd64 with dhcpcd connects only partially

> > On my latest NetBSD-current amd64 installation, from the small hours June > > 11, I get mixed results with re(4) driver and wonder if there is any dhcpcd > > tweak that will help. > > On motherboard MSI Z68MA-ED55(B3), Realtek 8111E/8168 Ethernet chip, > > "dhcpcd re0" connects OK, local

Re: HEADS-UP: /bin/sh memory management bug fixes committed

from Robert Elz: > Date:Tue, 20 Jun 2017 04:59:57 + > From: "Thomas Mueller" <mueller6...@twc.com> > Message-ID: <D5.B9.01815.9CBA8495@dnvrco-omsmta03> > | One barrier was package security/sudo, > Works

Re: dhcpcd.conf, ntp_servers, and RCS ID?

from Roy Marples: > On 02/06/17 17:31, John D. Baker wrote: > > The recent import of newer versions of the dhcpcd software has changed > > some behaviors. > > > In the past, the default "dhcpcd.conf" included "option ntp_servers". > > The current default has this commented out. > Some people

Re: heads-up: sh changes (perhaps fragility)

from Robert Elz: Date:Mon, 05 Jun 2017 07:24:38 + From:"Thomas Mueller" <mueller6...@twc.com> Message-ID: <E2.00.03935.95705395@dnvrco-omsmta01> | Now I don't know which branch to stay with, lean toward staying with | current

Re: heads-up: sh changes (perhaps fragility)

from Robert Elz: > You might want to actually try with a newer dhcpcd - while the intent is > to keep full binary compatibility with older userland, sometimes things > just slip through the cracks, especially when some kernel function is, in > practice, only ever used by one program. > You might

Re: NetBSD-current amd64 with dhcpcd connects only partially

from Roy Marples: > On 14/06/2017 03:03, Thomas Mueller wrote: > > FreeBSD uses dhclient, which works when the driver is OK (re or rsu). > Does this imply that on FreeBSD the driver sometimes fails? > dhcpcd (an older version) is in the FreeBSD ports tree as well as >

Re: NetBSD-current amd64 with dhcpcd connects only partially

from Roy Marples and my previous post: > > Using dhcpcd or dhclient makes me rusty on directly setting internet > > interface; any suggestions for improvement on what I did are welcome. > > But directly configuring internet interface uncripples an otherwise > > crippled NetBSD installation.

Re: HEADS-UP: /bin/sh memory management bug fixes committed

from Robert Elz: > I have just committed the (long awaited) bug fix set for /bin/sh -- > to fix some bugs I introduced recently - but also, several old, > devious, bugs that had remained hidden for years, but which became > more exposed with some of the recent changes - not so much the changes >

Re: HEADS-UP: /bin/sh memory management bug fixes committed

from Robert Elz: Date:Sun, 18 Jun 2017 07:16:55 + From:"Thomas Mueller" <mueller6...@twc.com> Message-ID: <D4.70.03935.CE826495@dnvrco-omsmta01> | I guess bugs in sh could affect a run with pkg_rolling-replace | and othe

Re: HEADS-UP: /bin/sh memory management bug fixes committed

from Robert Elz: > Date:Sun, 18 Jun 2017 19:28:19 + > From: "Thomas Mueller" <mueller6...@twc.com> > Message-ID: <79.F6.01815.A54D6495@dnvrco-omsmta03> > | What do you use instead of pkg_rolling-replace, while waiting fo

Re: heads-up: sh changes (perhaps fragility)

from co...@sdf.org and my previous post: > UPDATE: Not so fast! I tried the update on amd64 and found the > resulting kernel broke dhcpcd and dhclient in combination with re(4) > driver, making it impossible to access the Internet. > That was the opencrypto stuff. I made kern/52277 for it.

Re: NetBSD-current amd64 with dhcpcd connects only partially

from Robert Elz: > | Do you really mean netstat -nrf inet4 , or should that be inet? > Roy meant the latter. (That weird inconsistency is annoying, we should > support "inet4" as an alias to "inet" everywhere. But we don't...) > | Now if I knew what options/parameters to tweak, I could

Re: X Server struggle

from co...@sdf.org: > On Sun, Apr 30, 2017 at 02:44:27PM -0500, Robert Nestor wrote: > > Tried “Xorg” and then looked at the Xorg.0.log file and find “No > > screens”. > I seem to recall the various X commands aren't all the same. I use 'startx', > I'm not sure what additional things it

Any way to capture messages on a failed boot?

Is there any way to capture messages from a failed boot? I see /var/run/dmesg.boot was not created. In this case, I was trying to boot a kernel from 7.99.71, saw a message about nine hardware detection errors, see syslog, but no such file is found, at least not a new version. Maybe something

Re: heads-up: sh changes (perhaps fragility)

from Robert Elz: Date:Mon, 05 Jun 2017 07:24:38 + From:"Thomas Mueller" <mueller6...@twc.com> Message-ID: <E2.00.03935.95705395@dnvrco-omsmta01> | Now I don't know which branch to stay with, lean toward staying with | current

Re: UEFI boot NetBSD?

> On Tue, Oct 10, 2017 at 03:03:22AM +0000, Thomas Mueller wrote: > > Is it currently possible to boot newer versions of NetBSD in UEFI mode? > -8 and -current should work, but the installer has not yet been updated > to reflect it. > > How would the boot/load code know w

Re: nbpax: not found

from Paul Goyette: > You need to build the tools target furst > % ./build/sh -U -O ../obj tools > On Thu, 24 Aug 2017, Miwa Susumu wrote: > > Hi. > > I dowonload current source yesterday. > > I build "install", then got error, "nbpax: not found". > > Did I mistake the procedure? >

Re: Heads up: users of the netbsd-8 branch

from Martin Husemann: > If you are using NetBSD 8 BETA already, and are not updating from the > official "daily" builds, please note: > - The gcc internal specs have changed (rules for libgcc when building >shared binaries). This change requires a full build of ALL binaries >ever

UEFI boot NetBSD?

Is it currently possible to boot newer versions of NetBSD in UEFI mode? I looked online in NetBSD wiki, also man pages, but couldn't find anything informative. I notice /usr/mdec/bootx64.efi, also bootia32.efi, but where would the process go after that step? How would the boot/load code know

Re: Remove fortune quotes attributed to or providing admiration of Adolf Hitler [pr bin/52735]

Too difficult to decide what to quote here, but there has been a comparable controversy in the USA about whether to remove Confederate statues, statues of Confederate leaders and generals who played a big role in the Confederacy during the Civil War era. Governor Matt Bevin of Kentucky didn't

Re: NetBSD 8.0 Release Candidate 2 available

Excerpts from Martin Husemann on netbsd-announce: > On behalf of the NetBSD project, it is my pleasure to announce the second > (and hopefully last) release candidate of NetBSD 8.0. ... > Many changes have been made since 7.0. Here are a few highlights: ... - On i386/amd64 cpus:

Re: DHCP client: dhclient vs dhcpcd ?

On Wed, Jan 31, 2018 at 1:18 PM, KIRIHARA Masaharu wrote: > NetBSD has two DHCP clients; dhclient(8) and dhcpcd(8). > What's the difference? > Which is better to use? On Wed, 31 Jan 2018 13:47:42 +0100, Benny Siegert responded: > I agree that this is confusing.

Re: earmv7hf test status, specifically utimensat

> We really should have a proper (and non-optional) devfs and then the problem > is moot. >- thorpej Strongly agree! Preconfigured device nodes and MAKEDEV are a downside to NetBSD and OpenBSD, and decidedly awkward with GTP-partitioned hard drives with many partitions. Tom

Graphics open-source-friendliness, AMD Ryzen vs. Intel

I may need to buy parts for a new computer because of malfunctions on current motherboard and CPU (Intel Sandy Bridge dating to May 2011). Question is whether I am better off, regarding open-source-friendliness of graphics chips for running Xorg, with AMD Ryzen or the newer Intel chipsets. I

Re: Graphics open-source-friendliness, AMD Ryzen vs. Intel

from Robert Swindells and my previous post: > >I tried replacing the thermal paste and installing a new case fan to > >replace one that had quit, but CPU temperature still shows and stays at >97 C. > >Now I have a replacement Arctic Cooler heatsink and fan on order to > >replace the

Re: Cross-compiling Haiku from NetBSD?

> On Mon 03 Dec 2018 at 07:59:55 +0000, Thomas Mueller wrote: > > You mention Haiku. Did you ever attempt to cross-compile Haiku from > > NetBSD? > > > I tried but never succeeded, apparently because Haiku build system > > makes assumptions about where cer

Re: How to boot in UEFI mode: practically no documentation

Thanks for the suggestions. I could try to see what happens with /usr/mdec/bootx64.efi and FreeBSD's /loader.efi, possibly copied to $EFI_PARTITION/EFI/boot Also, I have an EFI and non-EFI version of grub2 compiled for FreeBSD, also want to take a look at FreeBSD's efibootmgr (in base

How to boot in UEFI mode: practically no documentation

Where do I find documentation on how to boot NetBSD amd64 or possibly i386 in UEFI mode? I couldn't find any man page and couldn't find anything useful in the online NetBSD wiki. I don't want to be limited to NetBSD, would also want to be able to boot FreeBSD and Linux in UEFI mode. I

Re: Cross-compiling Haiku from NetBSD?

> Hi Thomas, > Thomas Mueller wrote: > > You mention Haiku. Did you ever attempt to cross-compile Haiku from NetBSD? > no, I never did cross.compile, I only installed it. Also, it never worked > reliably and stopped booting. > I see now a new CD is out, I will try it

Cross-compiling Haiku from NetBSD?

Excerpt from Riccardo Mottola, Subject: Re: issues with touchpad after update: > Given the above test, it indeed appears to be multi-touch! But not usable... > the Scroll bar at right was probably something specific to the windows driver > (I don't have windows anymore... I used the other

Re: Does IPv6 on athn(4) work?

from: Masanobu SAITOH: > While modifying Ethernet multicast's code, I noticed that > athn.c doesn't modify the multicast filter. Does IPv6 on > athn(4) work? --- > Index: sys/dev/ic/athn.c I have a motherboard from 2013 by MSI (MPOWER) that has an onboard athn (Atheros 9271) wi-fi

Booting UEFI from GPT partition, how to denote the wedge?

I am having difficulty finding how to indicate the wedge to boot in UEFI mode. According to "man boot", a wedge can be indicated by "wedge:" followed by the wedge name, but that was not recognized. I was using the boot prompt, calling "help" many times. Desired wedge to boot was WD2G18 : The

Re: issues while doing pkgs update on py37-scons

from Benny Siegert: > It's a bug in pkg_rr. It gets confused by py27-foo vs. py37-foo etc. > Just go to the scons directory and "make package-install > PYTHON_VERSION_DEFAULT=37", then restart pkg_rr. > On Wed, Jun 26, 2019 at 12:20 PM Riccardo Mottola > wrote: > > Hi, > >

USB tethering setup

I couldn't find any documentation for USB tethering; I looked in the NetBSD Guide online. USB tethering would enable a smartphone to share its internet connection with a laptop or desktop computer via USB connection. There is documentation online in the FreeBSD Guide, but that is for FreeBSD:

USB tethering setup

I couldn't find any documentation for USB tethering; I looked in the NetBSD Guide online. USB tethering would enable a smartphone to share its internet connection with a laptop or desktop computer via USB connection. There is documentation online in the FreeBSD Guide, but that is for FreeBSD:

Re: NetBSD 9.99.1 Quick Question

> Perfect! > On 7/31/19, 1:31 PM, "J. Lewis Muir" wrote: > On 07/31, Ron Georgia wrote: > > I noticed that images and sets for NetBSD 9.99.1 is out. I have a > > totally noob question. According to the docs this would be current fo r > > version 10. Does this mean version 9 will

Re: NetBSD 9.99.1 Quick Question

from Greg Troxel: > Paul Goyette writes: > > On Wed, 31 Jul 2019, Thomas Mueller wrote: > >> How do users of 8.99.51 and earlier 8.99.x decide whether to go with > >> 9.99.1 or 9.0_BETA? > >> I am on > >> NetBSD amelia2 8.99.51 NetBSD 8.99.51 (Ne

Re: NetBSD 9.99.1 Quick Question

> > On Mon, 5 Aug 2019, Rhialto wrote: > > On Thu 01 Aug 2019 at 22:52:56 +0000, Thomas Mueller wrote: > > > Is there any preference on which Xorg I should use on a new > > > installation: modular or native? > > > I personally prefer native, since I con

Re: Booting UEFI from GPT partition, how to denote the wedge?

from nottobay: > I'm new to BSD in general and coming from Linux. I tried pulling the > binaries using the installer and it isn't working for me. Can I use pkg src > to upgrade in place from release to current or do I have to build > everything? What do you have now? Did you install the release

Re: firefox dumping core after NetBSD upgrade

from Sad Clouds: > What's the alternative, I've not used NetBSD for desktop tasks for a > while now, but I wish recent Opera browser was available for NetBSD. I > suppose you could run it with Linux emulation, but not sure how well it > works on NetBSD. Last time I tried, which was years ago,

Clearing ghosts of wedges (you forgot the subject line)

MLH wrote: > Right now I temporarily gave up on getting NetBSD to recognise both > wd2 and wd3. Either one or both go missing when I reboot now. > > I thought I would go back to just trying to boot from a gpt wedge > and give up on raid but I can't even get wedges set up. I can > completely

Re: github.com/NetBSD/src 5 days old?

> > Then what will be the primary way to track NetBSD src and pkgsrc trees? > > Now it's CVS, mirrored to git. What will replace CVS, will it be git, hg, > > or something else, and will it be in the base system, or will it have to be > > built or pkg_add'ed from pkgsrc? > > Is it a matter

  1   2   >