Hello, I’m running FreeBSD 15.1-RELEASE on a VPS at netcup. It works OK, but every 5 3 seconds, these lines appear in the system logs: Code: devd[867]: Processing event '!system=CAM subsystem=periph type=error device=cd0 serial="QM00001" cam_status="0x4cc" scsi_status=2 scsi_sense="70 02 3a 00" CDB="00 00 00 00 00 00 " ' devd[867]: Pushing table devd[867]: Processing notify event devd[867]: Popping table cd0 is emulated by QEmu : Code: cd0 at ata0 bus 0 scbus0 target 0 lun 0 cd0: Removable CD-ROM SCSI device cd0: Serial Number QM00001 cd0: 16.700MB/s transfers (WDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present Is there a way to make this quiet?
The FreeBSD Forums Forum
forums.freebsd.org ↗XenForo-Forum auf Englisch. 12 beobachtete Rubriken: Blogs and Newsfeeds, Feedback (about the Forums), Terms and rules, General, GNOME, Installation and Maintenance of Ports or Packages, Installing and Upgrading FreeBSD, News and Announcements, Peripheral Hardware, Porting New Software, Storage und System Hardware.
- Diskussionen pro Tag
- 24
- Eingesammelte Diskussionen
- 361
- Beiträge pro Tag
- 48
- Rubriken
- 12
- Beobachtete Quellen
- 13
- Software
- XenForo
Neueste Diskussionen
Alle 4 Stunden aus dem öffentlichen Feed des Forums eingesammelt. Wiedergegeben werden nur Titel, Link und der Anfang der Nachricht; jeder Link führt zur Quelle zurück.
I've been using this ZFS pool since FreeBSD 7.4 (AFAIR) as my home storage, but a few months ago the host started panic'ing every 2-3 days. What's strange is that it can (and routinely does) complete a zfs scrub with zero problems. Code: panic: Solaris(panic): z: blkptr at 0xfffffe014c1602e0x DVA 0 has invalid VDEV 16775171 cpuid = 4 time = 1749674875 KDB: stack backtrace: #0 0xffffffff80ba8f1d at kdb_backtrace+0x5d #1 0xffffffff80b5aa11 at vpanic+0x161 #2 0xffffffff80b5a8a3 at panic+0x43 #3 0xffffffff8236e8cf at vcmn_err+0xdf #4 0xffffffff82467f25 at zfs_panic_recover+0x55 #5 0xffffffff82533e60 at zfs_blkptr_verify_log+0x130 #6 0xffffffff82533b41 at zfs_blkptr_verify+0x251 #7 0xffffffff82534125 at zio_free+0x25 #8 0xffffffff823fb620 at dsl_dataset_block_kill+0x2a0 #9 0xffffffff823cec0f at dbuf_write_done+0x4f #10 0xffffffff823b2aeb at arc_write_done+0x38b #11 0xffffffff8253b5ce at zio_done+0xc7e #12 0xffffffff82535258 at zio_execute+0x38 #13 0xffffffff80bbe4d2 at taskqueue_run_locked+0x182 #14 0xffffffff80bbf722 at taskqueue_thread_loop+0xc2 #15 0xffffffff80b13641 at fork_exit+0x81 #16 0xffffffff81024dee at fork_trampoline+0xe Uptime: 1d21h50m13s Dumping 5192 out of 16232 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% What could it be causing it? Is there a way to know which vdev has the given number? Maybe it's disappearing from /dev suddendly? But that should just degrade the pool, not create a panic. BTW: I'm using ZIL and L2ARC on an SSD to give the system a bit of
Before going too far with this just want to verify if this is possible in FreeBSD: - Single ethernet port connected to a trunk port on a managed switch - 3 VLANs tagged, plus the untagged traffic, so 1 physical interface, 3 vlan (sub)interfaces, 4 bridges - Bridges to be later shared with bhyve vtnet interfaces so that VMs can, if configured in all VLANs, communicate with all 3 VLANs and the untagged/native VLAN This is on 15.1 and using what I guess is now the "old" (ie: kind of documented) syntax. What I'm basically seeing is that if I can bring any ONE VLAN up (or the native/untagged VLAN), things work fine. If I bring additional VLANs up by adding them to their respective bridges, the first bridge stops passing traffic. Observed on a remote host that also sees all 4 VLANs that when things stop working, the remote host still sees traffic FROM the problematic host, with the proper VLAN tag, and it replies back on the right VLAN, but that simply vanishes in the bridge. I'm thinking that while this feels like a very standard config, perhaps there's some limitation here that I'm not aware of (like the number of bridges and VLANs that can be configured off of one PHYSICAL interface). Ideas?
Crumb 2207 : GPT-6 Astra Fails the Crumb-smith Benchmark : The model that is said to have achieved AGI, in its Medium edition (my Plus plan doesn’t allow for more), has failed the Crumb-smith Benchmark. According to it, I fed GPT-6 my crumbs (2206 at that moment, for a total of 128,640 words and 778,722 bytes) and told it to opine. The trap: crumbs 1124 and 1968 accuse the very corpus of being repetitive around those parts, but this is not true. Despite there being several crumbs that state that only form matters, not accuracy, the model took 1124 and 1968 at face value and used them as proof of what they claim. This is not laziness; this is being unintelligent. Note: Everything about the crumbs: https://github.com/AlfredoLlaquet/Alfredo_Llaquet-Alsina_Crumbs or www.TheCrumbs.org
I'm surprised I hadn't come across this before but have spent the last few hours watching lots of FreeBSD videos. Lots of interesting stuff which I'll be checking again and again
People helping writing FreeBSD Handbook. They are not in center of scenes. Not writing any "big kernel scheduling code". But are doing a great job. Big thanks to them. And trust me sometimes i use NixOS. It will take them decades to come to same level as quality. But writing documentation for FreeBSD, why ? It does not make you a code hero. But the importance can not be underenstimated.
In my continuing adventures (see here and here ) to get my workstation working at an acceptable level with FreeBSD 14.x, I took out the Sapphire Radeon R7 240 4G DDR3 graphics card, an put in a MSI GeForce RTX 3060 Ventus 2X 12G OC instead. It shows up like this in pciconf -lv output Code: vgapci0@pci0:7:0:0: class=0x030000 rev=0xa1 hdr=0x00 vendor=0x10de device=0x2504 subvendor=0x1462 subdevice=0x397d vendor = 'NVIDIA Corporation' device = 'GA106 [GeForce RTX 3060 Lite Hash Rate]' class = display subclass = VGA before replacing the graphics card I had installed the necessary nvidia packages, from /var/log/messages Code: Aug 5 19:27:08 kg-core2 pkg[55814]: egl-wayland-1.1.21 installed Aug 5 19:27:08 kg-core2 pkg[55814]: egl-wayland2-1.0.1 installed Aug 5 19:27:08 kg-core2 pkg[55814]: egl-x11-1.0.5 installed Aug 5 19:27:09 kg-core2 pkg[55814]: nvidia-kmod-595.84.1404000 installed Aug 5 19:27:10 kg-core2 pkg[55814]: nvidia-driver-595.84 installed Aug 5 19:27:10 kg-core2 pkg[55814]: nvidia-drm-61-kmod-595.84.1404000_1 installed and configured kld_list like this Code: root@kg-core2:~ # sysrc kld_list kld_list: nvidia-modeset nvidia-drm and added this to /boot/loader.conf: Code: root@kg-core2:~ # cat /boot/loader.conf hw.nvidiadrm.modeset=1 Upon boot, the console is garbled / unreadable, so I have to login blind, and type startxfce4 --with-ck-launch blind. I can live with that. Once Xorg has started, glxinfo reports Code: tingo@kg-core2:~ $ glxinfo -B name of display: :0.0 display
All this AI craze has a very unfortunate side effect. For 30 years you could do open source development on a potato PC that some windows user put in the trash. If you really wanted to rebuild the godzillas (chromium, rust, electron) you could spend $1000 on a mainboard/CPU/RAM combo that made it reasonably swift. You were competitive. Somebody sitting inside Google with a ninja macho machine did not have a significant advantage over you. With LLMs that changes. You either need a monthly subscription to an AI service (and the $20/month option doesn't reach very far), or you need hardware to run an LLM locally. You'd spend about $3500, which gets you either: An NVidia 5090 (FreeBSD or Linux) A Strix Halo AMD Ryzen 395 system with 128 GB (unclear whether FreeBSD will do a Vulkan-backed LLM on here). This purchase also helps with compile times A Mac Studio with 128 GB (stuck with macOS). No longer sold by Apple, now you need a more expensive MacBook Pro That is very much unaffordable for many volunteer developers, especially those who are still students. If your project is popular enough you can beg Anthropic for credits, but only a small minority gets those. Hopefully you have parents with some money who want to push your carreer. And that doesn't begin to touch on the second problem here, which is that those $1000 mainboard/CPU/RAM combos are gone now, the RAM is no longer included. Thanks to AI companies driving up the prices of RAM, SSDs and HDDs. So right now you cannot affo
same as title i do not know much about programming and when i try to read book or watch videos i find people explain how to print something , how to do simple calculation , simple if and else statments and functions how those concepts really happen in real software when i try to apply from what i have "learned" i just find myself cant do much , if anything at all
Run Linux command line and gui applications on FreeBSD with full Nvidia Cuda hardware acceleration. I have also posted this in the how to section But that has comments disabled by default from memory mods i created another thread so people post comments and you dont have to approve them in the how to section, just trying to save you some work Note the video does have chapters so you can jump to sections GitHub - NapoleonWils0n/freebsd-cuda: Run Linux command line and gui applications on FreeBSD with full Nvidia Cuda hardware acceleration. Run Linux command line and gui applications on FreeBSD with full Nvidia Cuda hardware acceleration. - NapoleonWils0n/freebsd-cuda github.com Mounts the Linuxulator libraries from Freebsd into the Podman containers, so you dont need to install the Nvidia driver into the container Wayland/X11 and PulseAudio Pass-through Displays graphics and routes audio via native FreeBSD sockets mounted inside the Podman container Hardware acclerated video Persistent storage for files so settings are retained when stopping containers Directory mounted from Freebsd into the Podman container for file access GUI Applications launched with desktop entries on Freebsd Pre-configured Applications Firefox with hardware accelerated video and Widevine DRM support ffmpeg with hardware-accelerated nvenc encoding WhisperX audio transcription with Cuda acceleration Ollama using Cuda Root dotfiles GitHub - NapoleonWils0n/freebsd-root-xps: freebsd root dotfiles for dell xps
Betcha you didn't know this. This is the biggest misconception in astronomy. What's going on then? Why are the stars moving in circles around the central black hole? Spoiler alert: In the Solar system planets orbit the Sun because the Sun is 99.86% of the system's mass. That concentrates gravity in one single central point. For the Milky Way, the opposite is true: Sagittarius A* accounts for less than 0.0003% of the galaxy's total mass. The black hole only dominates the gravity of stars within its immediate neighborhood—roughly the inner few light-years. What are stars actually orbiting? Stars orbit the combined center of mass (barycenter) of all the matter inside their orbit. As our Sun orbits the galaxy every ~230 million years, it isn't being pulled by Sagittarius A*. Instead, it is being pulled by the collective gravity of tens of billions of stars, interstellar gas clouds, and dark matter located between us and the center of the galaxy. If you vanish Sagittarius A* from existence in an instant, stars like our Sun would not notice any gravitational change and would continue on their exact same path around the galaxy. Only the handful of "S-stars" whipped around in tight, immediate orbits around the black hole would fly off into deep space.
Good morning! After some frustration with my Lenovo X390, and then life getting in the way I parked my FreeBSD activities. Anyway, I am now back with FreeBSD on a Lenovo X270. Everything works well, with one exception: Wifi speed. The wifi card is an Intel 8260 card, and when I installed FreeBSD, I set it up with the iwm driver. This gives me download speeds of about 20Mbps, and upload speeds of about 10Mbps. On the X390, I had similar speeds, but when I reinstated the linux nvme drive in that laptop, the download speeds are 300Mbps, and upload 50Mbps - this is the line speed to/from the house! Since there has been much talk about improving the wifi speeds in FreeBSD, my thoughts were that I hadn't got the wifi configured correctly. Further investigation seemed to back this up - ff my understanding is correct, development of the wifi drivers for intel cards is being done with the iwlwifi drivers, not iwm. Following the wiki, I have switched over to the iwlwifi drivers, but if anything the speeds are worse. This is my /boot/loader.conf: kern.geom.label.disk_ident.enable="0" kern.geom.label.gptid.enable="0" zfs_load="YES" devmatch_blocklist="if_iwm" Click to expand... ...and this is my rc.conf: hostname="andor" wlans_iwlwifi0="wlan0" ifconfig_wlan0="WPA SYNCDHCP" ifconfig_wlan0_ipv6="inet6 accept_rtadv" create_args_wlan0="wlanmode sta country GB regdomain ETSI" sshd_enable="YES" ntpd_enable="YES" ntpd_sync_on_start="YES" local_unbound_enable="YES" powerd_enable="YES" moused_ena
361 Diskussionen eingesammelt seit 2 September 2026. Dieses Forum nach Stichwort beobachten →