Search results

Please don't do that. At best, it will only hide the real problem until it becomes too severe to fix.

Thread closed.

Did you follow the instructions in the Handbook? https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html

Have you run memtest on that system?

ugen means no specific driver has attached to the device. See https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-bluetooth.html.

It should be possible to cut and paste from the Handbook printing chapter.

dd if=/dev/da1 | hd | less Although this is more likely to be useful: file -s /dev/da1

Don't know, but I wouldn't be surprised. In the ones I tried, it's really a separate device, although it appeared to share the same antennas.

Please stop using dd to copy drives. It is brute-force and does not understand the data being copied, leading to partitioning and other problems. If you must use it, realize it has numerous ways to go wrong, and at least use a 64K blocksize to avoid overhead.

About transferring UFS: Backup Options For FreeBSD. It should also be possible to use restore to ZFS.

I've tried a couple of wireless cards with Bluetooth, and the BT part appears as a USB device. I wish I could say I was successful in using BT peripherals reliably, but that's another matter.

The 802.11ac thing is misleading. The card itself might work, although only in b/g/n modes. Have you tried it?

I don't see how any of this applies to the question. Dell notebooks in particular work well with replacement wireless cards, I have several and have changed the cards on quite a few. Lenovo and HP purposely build firmware that prevents the user from choosing a non-vendor wireless card. In...

On standard Arduinos, the USB serial port is /dev/cuaU0.

No idea about that particular card, but I routinely replace the wireless cards in notebooks with supported ones. It is generally not difficult unless you have a Lenovo or HP, where the firmware has a short list of cards that are allowed to work. For that and other reasons, I avoid Lenovo and...

Usually the "multiple devices" problem is due to multiple X drivers loaded when multiple video cards or devices are detected.

It's due to labels. See glabel. It's worth trying to use the memory stick image instead. Ordinary multiboot installers like that often don't understand the partitioning or labels used by FreeBSD.

Pretty sure that when Windows is installed in UEFI mode, it will only boot in UEFI mode. The only Windows 10 setups that are booting in BIOS mode are computers that were upgraded from earlier versions booting in BIOS mode. Dual-booting is suboptimal in many ways. But if you must dual-boot...

The "Windows method" should not be necessary. Log in to the FreeBSD system from the keyboard, then edit /etc/rc.conf.

Please be specific about the error messages and the HBA. These do not sound like drive failures, more like a problem with the HBA. Possibly it's a hardware RAID card between ZFS and the drives. It might even be something as simple as SMART tests scheduled at the same time as scrubs, making...