Re: /bsd: uvideo0: could not SET probe request: STALLED
On Tue, Dec 27, 2022 at 09:25:00PM +0100, Bodie wrote: > This one may help a little too > > https://community.silabs.com/s/article/the-role-of-stall-handshake-packet-in-usb-transfer?language=en_US I would like to express again my grateful thanks for the help provided. I had the opportunity to test another webcam and Iridium could use it without any problems. So this issue could presumably be hardware-related in the end. What can be said is the webcam that Iridium couldn't access to is able to go to a resolution up to 3840x2880 which I never could use with video(1) without getting an mmap error message. However, it can be accessed in raw mode with e.g. fswebcam, so I can use my device as an overhead scanner for books, which is fine. For information, my limits are as follows: $ ulimit -a time(cpu-seconds)unlimited file(blocks) unlimited coredump(blocks) 0 data(kbytes) 1572864 stack(kbytes)4096 lockedmem(kbytes)87381 memory(kbytes) 16182924 nofiles(descriptors) 512 processes256 Could it be that Iridium unsuccessfully tried to probe the device via mmap up to this resolution? Anyway, the good news is that using another device now gives excellent results. Thank you! -- Robert
Re: Change (spoof) MAC address
On 2023-01-06, Tomaž Kokolj wrote: > Hi everyone, > > Work week is over and I have time to play with real hardware. > Just wanted to let you know that this configuration did work: > > # cat /etc/hostname.re0 > inet autoconf lladdr 00:11:22:33:44:55 > > # ifconfig re0 > re0: flags=808843 mtu 1500 > lladdr 00:11:22:33:44:55 > index 1 priority 0 llprio 3 > groups: egress > media: Ethernet autoselect (100baseTX full-duplex) > status: active > inet 192.168.0.208 netmask 0x broadcast 192.168.255.255 > > But it did not work within VirtualBox. > Possibly a bug? I don't know VirtualBox but it is fairly common for virtualisation software to prevent MAC address changes, there's often a setting to permit it, look for something like "allow MAC address changes" or "allow MAC spoofing" in either VM or virtual switch config, you might also find some settings relating to promiscuous mode which may also be needed in some cases. -- Please keep replies on the mailing list.
Softraid crypto metadata backup
The way I see it, this depends on one's use case. There certainly are cases where it is important to be able to irrevocably destroy all data in an instant. But there are also use cases where one is only interested in making sure that the average person couldn’t access one’s data if one lost one’s laptop/external drive. I still think that anyone with the second use case could benefit from more documentation as I suggested, but I get the feeling this opinion is in the distinct minority here. So — thanks to everyone for the answers, I’m signing off this question now. Take care and stay secure, Nathan >Nathan Carruth writes: >> permanently and irrevocably destroy all data on your entire disk”. > >This is a feature. More so, it's the very point in an encrypted >filesystem. If you haven't planned for this failure scenario then >what are you doing using a device which *by design* can irrevocably >trash its contents in an instant? > >Matthew
Re: 回复: 回复: 回复: 回复: Softraid crypto metadata backup
Nathan Carruth writes: > permanently and irrevocably destroy all data on your entire disk”. This is a feature. More so, it's the very point in an encrypted filesystem. If you haven't planned for this failure scenario then what are you doing using a device which *by design* can irrevocably trash its contents in an instant? Matthew
