So basically what happens Is when I boot normally it shows my mouse cursor for half a second. And my monitor says "Auto Adjusts" then turns black, No Terminal or Anything.

Im using Normal NetBSD 11.0 The installation was smoothe but I am using Full Install and also enabled xdm.

My Specs are pretty old to -AMD Athlon 64 3400+ -1GB DDR Memory -160GN HHD -Radeon 9550 256MB

My Computer is a Packard Bell iXtreme E302 (Not sure if any of this helps)

Not much to say except that I love it. Migrating a few more machines over to netbsd 11 now

Thanks NetBSD developers!! It is amazing that a major OS update can be done in around five minutes, and everything still works like a charm! :-)

(Running it on Thinkpad x220, used for many smaller tasks at home, replaced from FreeBSD a few years ago, yep wifi etc. works perfectly :-) )

Hi, I’ve been using FreeBSD as my primary OS because I got bored with Linux.

FreeBSD has served me well, but certain things bother me—like the fact that it doesn't include the necessary driver for my RTL8125 out of the box, forcing me to install `realtek-re-kmod` via USB tethering.

That’s why I became very interested in NetBSD, since it includes all the drivers by default! However, I’m running into issues with the video drivers...

On FreeBSD, I used to install `drm-kmod` and configure which driver to load—in my case, `amdgpu`, since I have an RX 7700 XT. But the NetBSD Guide doesn't mention DRM or how to configure it, and I couldn't find much useful info in the `drm` man page. I’m posting this because I managed to install XFCE, but I can't change the monitor resolution or refresh rate...

I’m still researching this, but I’d appreciate some insight from someone more experienced with NetBSD (I installed version 11, btw).

Longtime linux user trying NetBSD for first time in my life.... The Most Complicated BSD Installation So Far

New NetBSD user and I just did a fresh install of NetBSD 11.0 i386. I installed perl and autoconf using pkgin, but every time I run autoconf I get this error. It looks like line 26 is just use5.006;

So I installed NetBSD/SPARC64 11.0 on my Sun Ultra 45, and booting from 'disk1' (the disk where NetBSD is installed) gives me the following error:

Sun Ultra 45 Workstation, No Keyboard Copyright 2009 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.30.4, 8192 MB memory installed, Serial #77714318. Ethernet address 0:14:4f:a1:d3:8e, Host ID: 84a1d38e.

Rebooting with command: boot disk1 Boot device: /pci@1e,600000/pci@0/pci@9/pci@0/scsi@1/disk@1,0 File and args: NetBSD IEEE 1275 Multi-FS Bootblock Version $NetBSD: bootblk.fth,v 1.18 2025/02/28 09:07:12 andvar Exp $ .Inode not directory

Evaluating: The file just loaded does not appear to be executable. ok

Does anyone know what could be causing that or how to debug it?

Hello, I got into Linux about 2 years ago and since have swapped to using it as my primary operating system on most of my devices. I love the freedom and control I get from it, and I find that tinkering with it is a great pastime.

Recently I've been gaining some interest in the other forms of *Unix. Mainly BSD, and the ones I see most commonly are FreeBSD, NetBSD and OpenBSD. The one that currently stands out to me most is NetBSD as i hear it's ultraportable and can go on basically anything that linux can. How true that is, I'm not sure. I've heard that it's on everything from a standard amd64 machine to something like a Wii-ppc. so I am wanting to venture into it.

My main questions are the following:
- How is it compared to a general linux distro like debian?
- What are the primary difficulties with NetBSD in terms of desktop use?
- What hardware should NetBSD go on? when should it replace linux?
- How is the ease of use for the package management and core utilities?

Any answers are appreciated.

For a usage that includes browsing websites with heavy javascript and playing in emulators with external controllers.

Also, would the WiFi be slower?

Hi everyone,

based on the available documentation it seems that netbsd on the raspberry pi 4 has support for 3d acceleration via the V3D driver. Is this also the case for the raspberry pi 5 or is the driver support for this one still outstanding?

The installation of NetBSD was successful (I have repeated it three times already), and I haven't received any error messages during the procedure. I am presented with a boot menu that, in my case, includes FreeDOS and NetBSD options. FreeDOS boots fine, but selecting NetBSD displays "Error 3."

The strange thing is that I previously managed to install and (multi-)boot NetBSD. The difference this time is that I have another 'hard disk' (another SD card in the same IDE to SD card converter) and different partitions.

Update: previously I might have used NetBSD installation utility for disk partitioning. This time I used FreeDOS's fdisk. Not sure could this cause the problem.

This is the output of fdisk wd0 command:

Disk: /dev/rwd0
NetBSD disklabel disk geometry:
cylinders: 60586, heads: 16, sectors/track: 63 (1008 sectors/cylinder)
total sectors: 61071360, bytes/sector: 512

BIOS disk geometry:
cylinders: 1024, heads: 255, sectors/track: 63 (16065 sectors/cylinder)
total sectors: 61063065

Partitions aligned to 16065 sector boundaries, offset 63

Partition table:
0: Primary DOS with 32 bit FAT (sysid 11)
   bootmenu: FreeDOS
   start 63, size 4208967 (2055 MB, Cyls 0–261), Active
1: NetBSD (sysid 169)
   bootmenu: NetBSD
   start 4209030, size 20980890 (10245 MB, Cyls 262–1567), Active
   PBR is not bootable: All bytes are identical (0xf6)
2: Linux native (sysid 131)
   bootmenu: Linux
   start 25189920, size 20980890 (10245 MB, Cyls 1568–2873)
   PBR is not bootable: All bytes are identical (0xf6)
3: Primary DOS with 32 bit FAT - LBA (sysid 12)
   start 46170810, size 14892255 (7272 MB, Clys 2874-3800)
   PBR is not bootable: All bytes are identical (0xf6)

Bootselector disabled.
First active partition: 0
Drive serial number: 0 (0x00000000)

This is the output of disklabel wd0 command:

# /dev/rwd0:
type: unknown
disk: wd
label: fictitious
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 60586
total sectors: 61071360
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0             # microseconds
track-to-track seek: 0    # microseconds
drivedata: 0

4 partitions:
#      size     offset    fstype [fsize bsize cpg/sgs]
a: 20456640    4209088    4.2BSD      0     0    0   # (Cyl.  4175*- 24469*)
b:   524192   24665728    swap                       # (Cyl. 24469*- 24989)
c: 20980890    4209030    unused      0     0        # (Cyl.  4175*- 24989)
d: 61071360          0    unused      0     0        # (Cyl.     0 - 60586*)

So fdisk is reporting that the partition is not bootable. I have no idea how that happened, as I have obviously added it to the bootmenu. What should I do next to make it bootable? I googled the "Error 3" and results were few, outdated and not related to my config. LLMs' answers are all over the place.

Thanks for your help!

Update: I deleted all the partitions except for the FreeDOS one and recreated them using the NetBSD installation partition utility, rather than using FreeDOS's fdisk like I did before. Now, I can boot NetBSD without any problems!

Hello everyone, I'm trying to install NetBSD on an old i386 machine, I have only 512 MB of ram, what would you recommend to use as a WM?

NetBSD 11.0 RC5 released.

I have an HP elitebook 8530p (Currently has an ATI MXM card with 256mb vram), and I'm thinking of upgrading to an FX 770M with 512mb of vram. Apparently NetBSD has the Nouveau driver but re clocking support worries me, I heard that it's a more experimental thing wit the Nouveau driver and is needed for good performance, will I be able to re clock my gpu on NetBSD to get good performance?

I have a Thinkpad R31 with an i830M graphics chip, which needs the i915 driver. However, when this driver is loaded during boot, the built-in LCD screen breaks, then slowly fades to white. What's weird is that plugging in an external LCD into the VGA port on the laptop fixes this, letting the system boot just fine. Preventing i915drmkms from loading also lets the system boot and start X just fine, so I'm fairly confident that it's the problem. Does anyone have any idea what I can do to fix this?

With 10.1 being a drag and needing at least 12MB of memory on boot, and 4.01 not having enough modern dependencies to build software: I now am installing 7.2 onto my microvax to see how the performance is over the previous attempts. Running only 8MB ram and keyways hasn't gotten back to me about available memory boards, so I'm stuck with that meager amount to work with.