On Mon, Apr 15, 2024 at 10:22:48AM -0600, Brook Milligan wrote:
> I’m trying to upgrade an amd64 system that has been running a version of 9.3
> (same as release on ftp.netbsd.org). I untarred the 10.0 GENERIC kernel set
> (kern-GENERIC.tar.xz), untarred the 10.0 modules set (modules.tar.xz), an
I ported the changes in FreeBSD SVN r257305 that add support for
RTL8168G. This works except for the RX path. When I netboot; an
unpatched NetBSD re(4) works for TX and RX. Any ideas?
Jonathan Kollasch
On Sun, Dec 15, 2013 at 09:57:59AM -0600, Jonathan A. Kollasch wrote:
>
> I ported the changes in FreeBSD SVN r257305 that add support for
> RTL8168G. This works except for the RX path. When I netboot; an
> unpatched NetBSD re(4) works for TX and RX. Any ideas?
>
>
On Sun, Dec 15, 2013 at 09:57:59AM -0600, Jonathan A. Kollasch wrote:
>
> I ported the changes in FreeBSD SVN r257305 that add support for
> RTL8168G. This works except for the RX path. When I netboot; an
> unpatched NetBSD re(4) works for TX and RX. Any ideas?
>
>
Hi,
Attached is a patch that should enable PCI MSI for pci(4)-attached re(4)
NICs. I would like both review of the code, and additional testing.
I've tested it successfully on amd64 -current with a
8100E/8101E/8102E/8102EL chip.
Jonathan Kollasch
Index: src/sys/dev/pci/if_re_pci.c
=
Additionally, this was committed as src/sys/dev/usb/motg.c 1.17.
On Mon, Jun 06, 2016 at 12:38:33PM +0200, Thomas Klausner wrote:
> netbsd-bugs is just for the GNATS traffic, please use current-users@
> instead (cc'ed).
>
> Thanks,
> Thomas
>
> On Sun, Jun 05, 2016 at 01:56:46PM +0300, Artturi
On Wed, Dec 28, 2016 at 11:26:10AM -0800, Brian Buhrow wrote:
> Hello. I'm sure this problem is pilot error on my part, but I'm
> having trouble figuring out where the build process is picking up the user
> postgres in the destination build environent.
> I'm hosting the build on a NetBSD-5
On Sun, Jan 01, 2017 at 01:09:57AM +0100, Tom Ivar Helbekkmo wrote:
> Happy new year! :)
>
> Being awake, I decided to observe the leap second. Not much luck.
> Turns out that date(1) shows :59 for two seconds, instead of going to
> the correct :60 during the extra second. Is that correct behavi
On Mon, Jan 30, 2017 at 05:14:33PM +0200, Andreas Gustafsson wrote:
> Yesterday, I reported a build failure on a Debian 8 host:
> >
> > /bracket/build/2017.01.29.05.13.55-i386/src/crypto/external/bsd/heimdal/dist/lib/vers/print_version.c:38:29:
> > fatal error: krb5/krb5-types.h: No such file o
On Sun, Mar 29, 2020 at 09:58:14AM +0200, Thomas Klausner wrote:
> Hi!
>
> After creating a gpt entry with type fbsd-zfs I noticed that it's not
> recognized by dk(4).
>
> dk5 at wd2: "ZFS_202003", 3907029101 blocks at 34, type:
>
> The attached diff fixes it:
>
> dk5 at wd2: "ZFS_202003", 390
On Sat, May 02, 2020 at 12:02:45PM +1000, Paul Ripke wrote:
> Since I have my qemu disk images on slow spinning rust host disks, when the
> host disk is busy (esp. daily+security runs), I find my qemu vm's see disk
> timeouts, and end up crashing. This isn't great behaviour.
Timeout issue aside, c
On Mon, Apr 21, 2014 at 06:04:13PM +0200, J. Hannken-Illjes wrote:
> - With -fno-omit-frame-pointer all is well.
>
> Does it ring any bell?
>
No, but I've seen this too.
Jonathan Kollasch
On Sat, May 10, 2014 at 04:17:10PM -0700, Paul Goyette wrote:
> 15:43:14). With no other changes than the updated kernel (and
> modules), it crashes with
>
> kernel: pagefault trap, code=0
> uvm_fault(0xfe813aec5e60, 0x0, 2) -> e
> fatal page fault in supervisor mode
> trap type 6 code 2 rip f
On Wed, Jun 11, 2014 at 05:47:28AM +, Thomas Mueller wrote:
> 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.
Use a USB 2.0 cable in between to force USB 2.0 speed
On Mon, Sep 15, 2014 at 11:46:24PM +0900, Ryo ONODERA wrote:
> Hi,
>
> Our xHCI USB 3.0 driver with Intel Lynx Point/Lynx Point-LP, Renesas uPD70202
> and Fresco Logic 0x1b73/0x1100 xHCI chips does not support non-root hub
> as following.
> I believe our xHCI driver have no non-root hub support.
On Thu, Dec 04, 2014 at 02:21:55PM -0800, bch wrote:
> I see that there is mention[1] of a porting effort for NetBSD to this
> device -- I quickly trawled the commit msgs in the repo and didn't see
> any obvious mention of it. Does anybody know the status of NetBSD on
> the ci20, or know where to g
On Tue, Dec 30, 2014 at 07:13:15PM +, David Laight wrote:
> On Wed, Dec 24, 2014 at 09:30:31PM -0500, Greg Troxel wrote:
> >
> > and a further question:
> >
> > I know /boot (with MBR) can skip the raidframe header. So given a
> > disk with a single MBR partition of type RAID, and an ins
On Mon, Aug 02, 2021 at 05:03:29PM -0600, Brook Milligan wrote:
> Is there any work to support the RTL8723 in NetBSD?
>
> I’m not sure this is relevant, but I see that the OpenBSD rtwn driver has
> support mentioned in the man page (https://man.openbsd.org/rtwn.4).
Which RTL8723 are you interest
On Wed, Dec 28, 2022 at 05:38:00PM +, Riccardo Mottola wrote:
> Hi,
>
> to debug nouveau I need to build a current kernel, as advised on
> netbsd-users.
>
> I got sources snapshot, updated with "cvs -q update -dPA". Did it twice to
> be sure not to have gotten a bad release.
> To do this, I n
On Wed, Jun 21, 2023 at 02:17:37PM +0200, Sagar Acharya wrote:
> I have no clue on the wedges thing.
>
> dmesg shows these errors while mounting.
>
> ufs: ufs_fill_super(): fragment size 0 is not a power of 2
> ufs: ufs_fill_super(): fragment size 8192 is too large
Linux's ufs driver is incapabl
On Wed, Jul 12, 2023 at 02:28:15PM +0200, Thomas Klausner wrote:
> Hi!
>
> For the last years, my nearly-GENERIC[1] kernel had size around 30MB.
> Yesterday's kernel is 32MB.
>
> Any ideas what changed, or how to find out?
>
> -rwxr-xr-x 2 root wheel 29652280 Jun 27 12:40 /netbsd.10.99.4
> -
Due to some recent changes to some file system syscalls, it is necessary
to follow correct upgrade procedures to avoid trouble.
Be sure to install new kernel and matching modules and boot the new
kernel before upgrading userland. Remember that once userland is
upgraded you will not be able to run
On Sat, Oct 05, 2019 at 12:02:38AM +0300, Andrius V wrote:
> Hello,
>
> Recently (around a week ago) I faced an issue with my mechanical
> keyboard (Fnatic Gear Rush) that it doesn't react to any keypress
> anymore (in general I can't use it as a keyboard). Weirdly enough this
> issue is present i
: fence driver on ring 3 use gpu addr 0x8c0c
> > and cpu addr 0x0xdec290e6cc0c
> > radeon0: info: fence driver on ring 4 use gpu addr 0x8c10
> > and cpu addr 0x0xdec290e6cc10
> > radeon0: info: fence driver on ring 5 use gpu addr 0x0007
back to NKRO in NetBSD though (keyboard reacts to
> > an attempt by turning off/on but apparently stays in 6KRO mode. I need
> > to boot into Linux, make a switch and reboot to make it work again).
> > Switching to 6KRO immediately renders the keyboard unusable
> > immed
On Sun, Apr 30, 2017 at 03:31:35PM -0500, Robert Nestor wrote:
> The hardware is a Lenovo 80S6 (Lenovo N22) which has an LCD screen.
>
> Startx, xinit and Xorg all produce the same results in the Xorg log file.
>
> MintLinux configures the output on eDP1, matches a two Intel drivers, Vesa
> and
On Wed, Jun 07, 2017 at 09:45:48PM +0200, Jaromír Doleček wrote:
> Hello,
>
> I plan to merge the branch to HEAD very soon, likely over the weekend.
> Eventual further fixes will be done on HEAD already, including mvsata(4)
> restabilization, and potential switch of siisata(4) to support NCQ.
>
>
On Tue, Jul 25, 2017 at 10:59:16PM -0700, Brian Buhrow wrote:
> Hello. I'm working on transitioning services at our shop from
> NetBSD-5 to NetBSD-8. As part of that effort, I'm working on figuring out
> how to write configurations for npf(7) which are direct replacements for
> our pf(4) co
On Wed, Aug 09, 2017 at 09:17:19AM -0700, Brian Buhrow wrote:
> Hello. It looks like the ukbd driver only allows 8 modifier keys on
> the keyboard, although the comment says it's 32 keys.
> sys/dev/usb/ukbd.c:87 says: #define MAXMOD 8 /* max 32 */
> Assuming the comment is correct, i
On Thu, Aug 10, 2017 at 03:41:37PM +0200, Christian Baer wrote:
> On Wed, 2017-08-09 at 11:43 -0500, Jonathan A. Kollasch wrote:
>
> > I doubt that alone will work. I've been sitting on a ukbd(4) rototill
> > that addresses this issue that I need to work on getting commit
There's a (probably remote) chance my changes to uhidev(4) and ukbd(4)
might have broken things.
Particularly, I was not able to test that ukbd(4)'s "FLAG_APPLE_FIX_ISO",
"FLAG_APPLE_FN", "FLAG_GDIUM_FN" still function correctly.
Additionally, I'd like to know if you've got a USB NKRO keyboard t
On Mon, Apr 30, 2018 at 12:43:50PM -0400, D'Arcy Cain wrote:
> On 2018-04-30 11:14 AM, Michael van Elst wrote:
> >> "Write snapshot driver -only skeleton was written yet."
> >
> > That's the problem. While a few bugs have been fixed, edges have
> > been smoothed and userland tools have been update
On Tue, Jun 12, 2018 at 12:13:27PM +0100, Patrick Welche wrote:
> I haven't seen "autoconfiguration error" before - something to worry about?
> (native X works fine)
On Tue, Jun 12, 2018 at 07:40:30PM +0700, Robert Elz wrote:
> Date:Tue, 12 Jun 2018 12:13:27 +0100
> From:Pat
On Wed, Jun 20, 2018 at 05:47:01PM +0800, Paul Goyette wrote:
> I'm unfortunately well aware that modern nVidia graphics cardds aren't
> working with the noveaudrmkms stuff. (I've got this nice spiffy new
> GTX-1050 running in vesa mode.)
>
> I've located a source for a reasonably current, reason
On Sun, Dec 15, 2024 at 08:34:35PM +, Patrick Welche wrote:
> Chasing a problem in print/pmw, I came across the following difference
> in behaviour:
>
> #include
> #include
>
> int main()
> {
> printf("%d", isspace(0xu));
>
> return 0;
> }
>
> causes a segmentation
On Sat, Nov 23, 2024 at 12:36:39PM +, Chavdar Ivanov wrote:
> Hi,
>
> I have been consistently getting
>
> #create libbluetooth/libbluetooth.so.4.2.diffsym
> + echo 'if diff -u
> /home/sysbuild/src/lib/libbluetooth/bluetooth.expsym
> libbluetooth.so.4.2.actsym >libbluetooth.so.4.2.di
On Sat, Mar 15, 2025 at 10:09:30PM +0100, Adam wrote:
> It seems like ZFS is not working on NetBSD-aarch64. The kernel module fails
> to load.
>
> # zfs
> internal error: failed to initialize ZFS library
> # modload zfs
> modload: zfs: Operation not permitted
> # uname -a
> NetBSD virtual 10.99.1
On Mon, Mar 17, 2025 at 06:37:42PM -0400, Tom Lane wrote:
> I have a macppc machine running NetBSD 10.1 that has been failing to
> run some larger programs. dmesg showed things like
>
> [ 1750816.967766] trap: pid 18392.18392 (perl): user write DSI trap @
> 0xbc949000 by 0xfdc9ea88 (DSISR 0x4200
On Tue, Feb 25, 2025 at 06:00:35PM +0100, Havard Eidnes wrote:
> Hi,
>
> I'm currently in the process of cross-building rust 1.85 for the
> various targets we try to maintain. This is mostly proceeding
> well, but our "mipsel" target is failing to build, with:
>
>
> clippy_utils.c33fa
39 matches
Mail list logo
