The FreeBSD Forums forum

Having an issue, reinstalled from STABLE to RELEASE ( Today ) but problem still persists. I had 2 nvidia gpus ( p620 and Titan V ) , Titan V - top slot, p620 - 2nd. Main monitor was p620. During boot sequence , system always crashes on same part: Code:  dmesg --- >--- Copyright (c) 1992-2025 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 15.1-RELEASE releng/15.1-n283562-96841ea08dcf GENERIC amd64 FreeBSD clang version 19.1.7 (https://github.com/llvm/llvm-project.git llvmorg-19.1.7-0-gcd708029e0b2) VT(efifb): resolution 1024x768 CPU: Intel(R) Xeon(R) CPU E5-2690 v4 @ 2.60GHz (2598.63-MHz K8-class CPU) Origin="GenuineIntel" Id=0x406f1 Family=0x6 Model=0x4f Stepping=1 Features=0xbfebfbff Features2=0x7ffefbff AMD Features=0x2c100800 AMD Features2=0x121 Structured Extended Features=0x21cbfbb Structured Extended Features3=0x9c000400 XSAVE Features=0x1 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr TSC: P-state invariant, performance statistics real memory = 137434759168 (131068 MB) avail memory = 134235217920 (128016 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: Reinstalled OS - problem persists. Removed nvidia p620 - problem persists. During selection method, usually have to change option 5 from Video to Serial first and still sometimes hangs up ... sometimes have to circle trough Serial, Ser

The BSD family of licenses are unusually compatible with consumer rights. The licenses cope well with the right to be informed. If a consumer owns a product which includes software under a BSD license, they're legally eligible to obtain (or, better saying, use) the sources. When a company states that the product includes software under a BSD license, it is making a representation. The core feature of these licenses is the freedom to use, modify, and redistribute the source code. By failing to provide a way to use the source code, the company is making a material omission. It is omitting the crucial fact that the advertised open nature of the software is practically inaccessible. A reasonable consumer, seeing that a product uses open-source software, would be led to believe they can benefit from the openness of the software (e.g., for security audits, community repairs, modifications). Denying use misleads the consumer about this essential characteristic. 1) redistribution is illusory if the sources weren't disclosed in first place; 2) use implies access. Use is illusory if access is illusory. Both cases are material omissions. The FTC Act prohibits deceptive or unfair practices or acts in or affecting commerce. All it takes is a company engage in deceitful behavior, such as claiming sources may not be disclosed. This is a false claim, and flies in the face of the right to be informed. Note I'm not saying the BSD licenses replace GNU GPL. GNU GPL better kicks in to make modifi

On my DELL it updates firmware for BIOS, wifi, NIC, video like very other week via Windows 11. How would I get the new firmware via FreeBSD?

I bought a thunderbolt 3 eGPU dock and an Intel Arc A770 for my laptop, but I noticed that Code: # Disabled for now since thunderbolt(4) breaks suspend/resume in some instances # and the overall implementation isn't fully fleshed out yet. #device thunderbolt # Thunderbolt PCI->USB interface (USB 4.0) so I want to build the kernel with device thunderbolt , is this issue of breaking suspend/resume seriously?

I can't get cron jobs to run, when adding them with user www (nologin account): Code: crontab -u www -e * * * * * /usr/local/bin/php /www_master/sites/support/artisan schedule:run >> /dev/null 2>&1 But if I edit /etc/crontab and add this line with the user www before the command, everything is working: Code: * * * * * www /usr/local/bin/php /www_master/sites/support/artisan schedule:run >> /dev/null 2>&1 Am I missing something?

This home server running FreeBSD 15.1 has system on 2 SATA SSD disks using gmirror , MBR and UFS . Mainboard has X370 chipset and CSM enabled. At a whim I added third disk to gmirror - it is NVMe . I expected system not to boot from it, but at least it would be a bit faster (changed gmirror disk read priorities). Recently I was upgrading CPU and memory and removed all other disks except NVMe. I expected system to be not bootable, but I still ended up in FreeBSD boot menu. How come? How does this work?

The motherboard ( Intel B75A ) is a noname. The voice recorder is connected via USB for 9 seconds and then disconnected. This process is not random, but rather regular and repetitive. $ uname -aKU Code: FreeBSD none 15.0-RELEASE-p1 FreeBSD 15.0-RELEASE-p1 releng/15.0-n280999-7bceec30b351 GENERIC amd64 1500068 1500068 $ tail /var/log/messages Code: Dec 31 08:41:03 none kernel: (da0:umass-sim0:0:0:0): CACHE PAGE TOO SHORT data len 3 desc len 0 Dec 31 08:41:03 none kernel: (da0:umass-sim0:0:0:0): Mode page 8 missing, disabling SYNCHRONIZE CACHE Dec 31 08:41:03 none kernel: da1 at umass-sim0 bus 0 scbus3 target 0 lun 1 Dec 31 08:41:03 none kernel: da1: Removable Direct Access SCSI-2 device Dec 31 08:41:03 none kernel: da1: Serial Number 2001347530000000 Dec 31 08:41:03 none kernel: da1: 40.000MB/s transfers Dec 31 08:41:03 none kernel: da1: 14910MB (30535680 512 byte sectors) Dec 31 08:41:03 none kernel: da1: quirks=0x2 Dec 31 08:41:03 none kernel: (da1:umass-sim0:0:0:1): CACHE PAGE TOO SHORT data len 3 desc len 0 Dec 31 08:41:03 none kernel: (da1:umass-sim0:0:0:1): Mode page 8 missing, disabling SYNCHRONIZE CACHE $ tail /var/log/messages Code: Dec 31 08:41:03 none kernel: (da1:umass-sim0:0:0:1): Mode page 8 missing, disabling SYNCHRONIZE CACHE Dec 31 08:41:09 none kernel: ugen1.5: at usbus1 (disconnected) Dec 31 08:41:09 none kernel: umass0: at uhub4, port 3, addr 5 (disconnected) Dec 31 08:41:09 none kernel: da0 at umass-sim0 bus 0 scbus3 target 0 lun 0 Dec 31 08:41:09 none ker

Hi! Problem in short: In my usage scenario of X and mouse I got mouse stops working. If restart X session, functionality restores, if without restarting X plug in USB mouse, it moves the cursor, but after some time, or after plug-out system crushes. I'm running Code: FreeBSD bsd15 15.0-RELEASE-p4 FreeBSD 15.0-RELEASE-p4 releng/15.0-n281010-8ef0ed690df2 GENERIC amd64 on Dell Latitude E6420. Here is ALPS Touchpad, that sadly still not recognized by psm(4) . So I've managed to configured it -- PS/2 mouse -- as close to expectations, as possible. Related configs: /etc/rc.conf Code: moused_enable="YES" moused_flags="-3 -V" This emulates third (middle button), and virtual scrolling, that I do not understand where and how to be used. Resolution and acceleration, make it close to touchpad feeling, psm(4) : /boot/device.hints Code: hint.psm.0.flags="0x24" Here I may say, that in conosole I have no problems. Problems arise in Xorg. Xorg-related config: /usr/local/etc/X11/xorg.conf.d/30-alps.conf Code: Section "InputClass" Identifier "alps-as-mouse" Driver "libinput" MatchProduct "Generic PS/2 mouse" MatchIsPointer "true" Option "ScrollMethod" "button" Option "NaturalScrolling" "true" EndSection Until there all feels ok, except that it's not touchpad, thus now edge scrolling and other things, but it can be used. One thing is very annoing: tapping (mouse clicking) with palm, whet I typing text, Very annoying. For touchpad, especially, synaptics, there is syndaemon, that listening for key

1. Boot from the USB flash drive (version 15.1). 2. Reach the Beastie menu with the system boot options. 3. Press the Space bar to pause the menu and prevent the automatic boot sequence from starting. 4. Press the NumLock key on the keyboard (a 2007–2010 model HP KB-0316 PS/2) to enable the numeric keypad. Press it again to disable it. If you do this 20–30 times, everything works fine. 1. Boot from the "booting USB flash drive" (version 15.1). 2. Reach the Beastie menu with the system boot options. 3. Enter the installer—the first screen is the "Welcome to FreeBSD!" greeting. 4. Press the NumLock key on the same keyboard to enable the numeric keypad. Press it again to disable it. If you do this 10–15 times, everything "freezes." The keyboard becomes unresponsive, and the PC can only be turned off using the hardware power button. If you perform the same actions on an already installed system, the only difference is that you log in as root and enter the password. If you are lucky and the keyboard doesn't hang immediately, you can trigger the "freeze" by repeatedly toggling NumLock. Sometimes the keyboard freezes right at the login prompt! That’s how it happens! This doesn't happen consistently; you might work in X for half an hour with no issues. This doesn't happen on Windows or Linux . Verified through testing. I thought my A4 wireless mouse might be the culprit. It wasn't. I disconnected the wireless receiver, but the problem persisted. I connected a standard USB mouse, but

This home server running FreeBSD 15.1 has system on 2 SATA SSD disks using gmirror , MBR and UFS . Mainboard has X370 chipset and CSM enabled. At a whim I added third disk to gmirror - it is NVMe . I expected system not to boot from it, but at least it would be a bit faster (changed gmirror disk read priorities). Recently I was upgrading CPU and memory and removed all other disks except NVMe. I expected system to be not bootable, but I still ended up in FreeBSD boot menu. How come? How does this work?

I can't get cron jobs to run, when adding them with user www (nologin account): Code: crontab -u www -e * * * * * /usr/local/bin/php /www_master/sites/support/artisan schedule:run >> /dev/null 2>&1 But if I edit /etc/crontab and add this line with the user www before the command, everything is working: Code: * * * * * www /usr/local/bin/php /www_master/sites/support/artisan schedule:run >> /dev/null 2>&1 Am I missing something?

Major hang happens if I set kern.elf64.nxstack=0. I normally have it =1, so if I try to manually disable it by setting it to 0, everything breaks and I get an error trying to do anything: Code: [user@freebsd ~]$ sudo sysctl kern.elf64.nxstack=0 kern.elf64.nxstack: 1 -> 0 [user@freebsd ~]$ sudo sysctl kern.elf32.nxstack=0 exec_new_vmspace: mapping stack size 0x20000000 prot 0x7 failed, mach error 2 errno 13 Abort trap sudo sysctl kern.elf32.nxstack=0 [user@freebsd ~]$ sudo sysctl kern.elf32.nxstack exec_new_vmspace: mapping stack size 0x20000000 prot 0x7 failed, mach error 2 errno 13 Abort trap sudo sysctl kern.elf32.nxstack If I set it to 0 in /etc/sysctl.conf, I can't even boot into the system, similar error message, unknown error 134, says "init crashes", and I'm stuck in a login loop for single-user mode.