On Wednesday, June 16, 2021 6:17:50 PM CEST Lizbeth Mutterhunt, Ph.D wrote:
> hi people,
>
> first at the moment I have to short-cut my web as not at home and
> /etc/rc.conf doesn't take my wlan0 interface; I changed rooter IP to
> 192.168.8.1 and edited /etc/wpa_supplicant.conf. but still at
I was testing geli_groups with a setup similar to the example here:
https://reviews.freebsd.org/D12644
The entries in rc.conf only work if the devices are not also listed in /etc/
fstab. The rc-script processes fstab entries before trying to attach the
geli_groups.
As workaround, I've edited
On Sunday, March 22, 2020 11:38:31 AM CEST Stefan Ehmann wrote:
> On Saturday, March 21, 2020 12:07:55 PM CET Alexander Leidinger wrote:
> > Quoting Stefan Ehmann (from Sat, 21 Mar 2020
> >
> > 11:38:26 +0100):
> > > On Thursday, March 19, 2020 8:57:45 AM CET Alexand
On Saturday, March 21, 2020 12:07:55 PM CET Alexander Leidinger wrote:
> Quoting Stefan Ehmann (from Sat, 21 Mar 2020
>
> 11:38:26 +0100):
> > On Thursday, March 19, 2020 8:57:45 AM CET Alexander Leidinger via
> > freebsd-
> >
> > stable wrote:
> >> Hi,
On Thursday, March 19, 2020 8:57:45 AM CET Alexander Leidinger via freebsd-
stable wrote:
> Hi,
>
> if someone wants to donate some FreeBSD based CPU resources to the
> fight against the Corona-virus, here is a quick HOWTO in terms of
> installing the Folding@Home client on FreeBSD:
>
>
Hello,
On my Ryzen the sha256 command is much slower than openssl dgst -sha256.
For large files, openssl is more than 7 times faster in practice.
You can also test it with the builtin benchmarks:
sha256 -t
openssl speed sha256
I think the reason is that openssl supports the SHA CPU extensions
On 11/14/18 5:41 AM, Conrad Meyer wrote:
> You know what, I wonder if you're running into the CUR_TEMP_RANGE_SEL?
> I.e., sometimes the CPU chooses to report on a range from 0-225C and
> sometimes -49C-206C. I think someone else's 2990WX did the same
> thing. I guess that patch never landed?
On 11/13/18 10:14 PM, Conrad Meyer wrote:
> On Tue, Nov 13, 2018 at 1:04 PM Stefan Ehmann wrote:
>> After kldload amdtemp I see the following sysctls:
>> dev.cpu.0.temperature: 77.1C
>> dev.amdtemp.0.core0.sensor0: 77.1C
>>
>> The temperature I see in BIOS
On 11/13/18 10:40 PM, Daniel Eischen wrote:
>
>> On Nov 13, 2018, at 4:02 PM, Stefan Ehmann wrote:
>>
>>> On 11/13/18 8:59 PM, Daniel Eischen wrote:
>>>> On Tue, 13 Nov 2018, Greg V wrote:
>>>>
>>>>
>>>>
>>&
On 11/13/18 8:59 PM, Daniel Eischen wrote:
> On Tue, 13 Nov 2018, Greg V wrote:
>
>>
>>
>> On Tue, Nov 13, 2018 at 8:59 PM, Daniel Eischen
>> wrote:
>>> Greetings,
>>>
>>> I'm trying to track down a couple of things. amdtemp doesn't
>>> report any temperature sensors, and acpi seems to have
On 9/22/18 4:53 AM, Eric van Gyzen wrote:
I would like to build a Ryzen desktop. Can anyone recommend a good
motherboard?
I'm planning on a first-gen, because the second-gen has similar
stability problems as the first-gen had, and AMD hasn't released errata
for the second-gen yet (as far as
On 09.07.2017 11:52, Johannes Lundberg wrote:
Hi
Yeah I forgot to mention the LOCAL_CREDS.
It does not return the PID of the client process but i guess it could be
expanded to include that instead of adding another option for that.
I was only skimming the man page. Didn't see that cmsgcred
On 09.07.2017 10:03, Johannes Lundberg wrote:
Hi
Without altering the client code (i.e. adding sendmsg(credentials)), is
there anyway of getting the client PID (or path to binary) using the file
descriptor returned by accept() on the server side?
Similar to Linux's getsockopt with SO_PEERCRED
On 17.11.2016 10:44, O. Hartmann wrote:
> Hello,
>
> I'm looking for a suitable SmartCard read with USB connection for 12-CURRENT
> (and
> probably 11-STABLE). We have lots of Omnikey 3121 devices at hand, but I
> wasn't able to
> make this type of SC reader working. it is recognised by the
On 16.06.2014 21:21, Edward Tomasz Napierała wrote:
Hi. Patch below should fix a problem where USB stops working after
_second_ suspend/resume, which happens on various ThinkPad models.
Please test, and report both success stories and failures. If nothing
comes up, I'll commit it in a week or
Network monitoring tools show download traffic, but no upload data.
systat -ifstat output:
Interface Traffic PeakTotal
wlan0 in 1.066 KB/s 16.155 KB/s 377.757 MB
out 0.000 KB/s 0.000 KB/s0.000
On 07.06.2014 14:39, bycn82 wrote:
Hi,
Seem it was not clear in my original post: Only the wireless interface
is affected. lo0 shows upload stats.
More information is required. Please provide the output of the two commands
below
1. sysctl -a | grep octets
iwn0/wlan0 don't
On 21.05.2014 21:43, Jan Henrik Sylvester wrote:
On 05/21/2014 21:22, Hans Petter Selasky wrote:
On 05/21/14 21:16, Jan Henrik Sylvester wrote:
Unfortunately, my USB mouse does not work anymore: After the first
resume, it took a few seconds until it worked again (the build in
touchpad was
On 17.05.2014 01:39, Adrian Chadd wrote:
Hm, okay. i wonder how we can diagnose this further.
Do you have a video monitor? Can you try doing a suspend/resume with
an external VGA screen attached?
I booted with VGA as primary (and only) monitor. No real changes. The
external monitor also
On 17.05.2014 14:20, John Baldwin wrote:
On 5/16/14, 2:10 PM, Kevin Oberman wrote:
On Fri, May 16, 2014 at 10:44 AM, Adrian Chadd adr...@freebsd.org wrote:
Hi!
I wonder what changed between 9.2-RELEASE and 10.0-RELEASE.
Please poke me about this next week. I'm busy this week with work and
Suspend/Resume is broken on my T410 using CURRENT from today.
Resume was working fine on 9.2-RELEASE. 10.0-RELEASE and 10-STABLE don't
work either.
Symptoms:
acpiconf -s3 sends it into sleep mode as expected
In single user mode, it wakes up correctly, but the screen remains
black. I tried
On 16.05.2014 22:51, Adrian Chadd wrote:
Hi,
Yeah. I'd really suggest trying with stable/10 or -HEAD with vt
enabled and no VESA.
Thanks for all replies.
Using vt is definitely an improvement, but not perfect. (I've set
hw.vga.textmode=1 because graphics mode is very slow. Don't know if
I've noticed that with 9.0-RC1, usbus[0-9] are seen as network interfaces. I
figured this is need for usbdump to work.
(This isuue has been raised before [1], but no helpful replies were given).
I find this behavior rather annoying:
1)
usbus0 is the default interface (in 8.2, my primary network
On Fri, 2003-11-28 at 01:02, Don Lewis wrote:
On 27 Nov, Stefan Ehmann wrote:
On Wed, 2003-11-26 at 08:33, Don Lewis wrote:
The problem is that selrecord() wants to lock a MTX_DEF mutex, which can
cause a context switch if the mutex is already locked by another thread.
This is contrary
This happens to me several times a day (cvsup from yesterday didn't
change anything). The panic message is always the same, the backtrace is
different though (but always seems to be file system related in some
way)
Here's one from today:
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 Free Software
On Sun, 2003-11-30 at 11:13, Stefan Ehmann wrote:
This happens to me several times a day (cvsup from yesterday didn't
change anything). The panic message is always the same, the backtrace is
different though (but always seems to be file system related in some
way)
Here's one from today
On Mon, 2003-12-01 at 01:10, Don Lewis wrote:
Can you reproduce this problem without bktr?
snip
You are getting a double panic, with the second happening during the
file system sync. The code seems to be be tripping over the same mount
list entry each time. Maybe the mount list is getting
On Fri, 2003-11-28 at 01:02, Don Lewis wrote:
On 27 Nov, Stefan Ehmann wrote:
On Wed, 2003-11-26 at 08:33, Don Lewis wrote:
The problem is that selrecord() wants to lock a MTX_DEF mutex, which can
cause a context switch if the mutex is already locked by another thread.
This is contrary
On Fri, 2003-11-28 at 01:02, Don Lewis wrote:
On 27 Nov, Stefan Ehmann wrote:
On Wed, 2003-11-26 at 08:33, Don Lewis wrote:
The problem is that selrecord() wants to lock a MTX_DEF mutex, which can
cause a context switch if the mutex is already locked by another thread.
This is contrary
On Fri, 2003-11-28 at 10:31, Stefan Ehmann wrote:
On Fri, 2003-11-28 at 01:02, Don Lewis wrote:
On 27 Nov, Stefan Ehmann wrote:
On Wed, 2003-11-26 at 08:33, Don Lewis wrote:
The problem is that selrecord() wants to lock a MTX_DEF mutex, which can
cause a context switch if the mutex
On Wed, 2003-11-26 at 08:33, Don Lewis wrote:
The problem is that selrecord() wants to lock a MTX_DEF mutex, which
can
cause a context switch if the mutex is already locked by another
thread.
This is contrary to what bktr_poll() wants to accomplish by calling
critical_enter().
Strange enough
On Wed, 2003-11-26 at 19:37, Matthias Andree wrote:
Hi,
when I rebooted my 5.2-BETA (kernel about 24 hours old), it gave up on
flushing 4 dirty blocks.
I had three UFS1 softdep file systems mounted on one ATA drive, one
ext2
file system on another ATA drive and one ext2 file system on a
I got the following panic twice when starting xawtv using 5.2 BETA (CVS
from Oct 23)
panic: blockable sleep lock (sleep mutex) sellck
@/usr/src/sys/kern/sys_generic.c:1145
I don't think it is directly related to bktr since the last commit there
was ~3 months ago. Here is the dmesg output for
me)
verbose dmesg can be found here
http://stud4.tuwien.ac.at/~e0125637/dmesg.new
verbose dmesg with ata-lowlevel.c 1.11
http://stud4.tuwien.ac.at/~e0125637/dmesg.old
Stefan Ehmann
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman
: create disk ad0 dp=0xc413d470
ad0: 58644MB IC35L060AVER07-0 [119150/16/63] at ata0-master UDMA66
GEOM: create disk ad1 dp=0xc413d270
ad1: 38166MB ST340823A [77545/16/63] at ata0-slave UDMA66
acd0: CDRW CR-4804TE at ata1-master PIO3
acd1: DVDROM LITEON DVD-ROM LTD122 at ata1-slave PIO4
Stefan Ehmann
35 matches
Mail list logo
