Search results

exFAT bugs are still there. Claimed to be read[36818192286464] 65536 bytes from 1497104384 flags: 0x0 ERROR: failed to read cluster 0xe64f3. unique: 144, error: -5 (Input/output error), outsize: 16 unique: 145, opcode: READ (15), nodeid: 2, insize: 80, pid: 83779 read[36818192286464] 131072...

Is there a way to give Internet from a FreeBSD machine to other devices via USB cable? I have Android devices in my mind mostly (and not sure at the moment, but at least I think I've seen something about USB Ethernet adapters supported on Android via OTG cables) but may be another FreeBSD...

I have samewhat similar problem. After upgrading to 14 I've given a try to net/realtek-re-kmod. But after awhile my system almost freezed with errors about ps_bpf_recvbuf and ps_root_recvbuf "No buffer space available" from dhcp daemon and named in /var/log/messages. Although I have plenty of...

em0: <Intel(R) Legacy PRO/1000 MT 82540EM> port 0xe400-0xe43f mem 0xfebe0000-0xfebfffff irq 21 at device 6.0 on pci4 em0: The EEPROM Checksum Is Not Valid em0: IFDI_ATTACH_PRE failed 5 device_attach: em0 attach returned 5 em0: <Intel(R) Legacy PRO/1000 MT 82540EM> port 0xe400-0xe43f mem...

Luckily, the one that is working is served by re driver. By the way, somehow faulty intel em card still works in Windows, despite EEPROM error. As I've seen it probably could be restored by rewriting this EEPROM, but it is cumbersome for me now. So, I am planning to replace it with a Broadcom...

Oh, thanks. I think it is what I need.

I have faulty ethernet card which is served by em driver (EEPROM problem). I have eliminated the driver from my custom kernel and it is absent in loader.conf, but still it is somehow automatically loaded in the boot process only making it a bit longer, diagnosing faulty EEPROM. So the question...

As far as I can see, somehow the trim was approved, but it is bluntly formal to the date of release end of life. I've put 276495 in bugs, although.

Thanks, that was not obvious for me.

Do you know, how to get previous version, and not .diff file from the history?

As I can see all those tremendous trims began on May 2023. The last one on January, 3rd. (Why? The file is not huge at all, and by the trim links in this file became "not found".)

I am updating from 12 to 14 (as it occurred, inevitably via 13), and I see /usr/ports/UPDATING is cut now. For example, there's mentioning of 20190420, but it starts now only from 2021. Where can I get longer version of this file with older information?

-s Do not echo any commands as they are executed How's that can help?

Is it possible to get rid of noticable debug portion when building world from source? Not to build it at all, I mean. (/usr/lib/debug etc.)

Hoorah! The problem was that provided DNS servers of the local network do not make trusted responses. "broken trust chain" appered in logs when I managed to configure them (not too friendly with bind). And only "dnssec-validation no;" on named's options solved the problem (somehow, although...

If it was a bad RAM it would be obvious in other activities like compilation of kernel, world and a bunch of ports, wouldn't it? And as far as I remember memcheck was O.K. The system has only a UFS disc. And how to check if there's no any filtering? Any debugging options for bind itself?

Well, as far as I can see local interface do not make checksums and it's O.K. The same is with my good working home computer. It also gives "bad cksum" on localhost, although no ServFail and good answers from bind-named. No lagg nor bridge for now (only planning to bridge ethernet to wireless...

15:33:57.126723 IP (tos 0x0, ttl 64, id 56596, offset 0, flags [none], proto UDP (17), length 79, bad cksum 0 (->9f87)!) localhost.41482 > localhost.domain: 44668+ [1au] A? google.com. (51) 15:33:57.134712 IP (tos 0x0, ttl 64, id 37103, offset 0, flags [none], proto UDP (17), length 95, bad...

I understand that. But for my DIMMs written parameters are 11-11-11-30 for 1600MHz and 9-9-9-24 for 1333MHz. Usually they are linked and I haven't modified them in BIOS settings. By the way, I do not see "Configured Memory Speed" in a dmidecode output at all, only "Speed" field. So, I believe...

It looks like the opposite: CPU-Z shows real-time data, since it is 803-804MHz (dual-channel mode) and a bit changing. The BIOS on this motherboard shows actual "auto" timings 11-11-xx which correspond to 1600MHz frequency, although do not show the frequency itself.