On 2014/05/21 23:00, Philip Guenther wrote:
> On Wed, 21 May 2014, Nils R wrote:
> > since the snapshot from 18.05., the wrong MHz of my CPU is displayed in
> > both dmesg and apm. apmd is started at boot, here is my rc.conf.local:
>
> Approximately what was the date of the build you were runnin
Philip Guenther schrieb am 22.05.2014 08:00:
> On Wed, 21 May 2014, Nils R wrote:
>> since the snapshot from 18.05., the wrong MHz of my CPU is displayed in
>> both dmesg and apm. apmd is started at boot, here is my rc.conf.local:
>
> Approximately what was the date of the build you were runnin
Philip Guenther schrieb am 22.05.2014 09:36:
>
> On Wed, 21 May 2014, Nils R wrote:
>> Philip Guenther schrieb am 22.05.2014 08:00:
>> > On Wed, 21 May 2014, Nils R wrote:
>> >> since the snapshot from 18.05., the wrong MHz of my CPU is displayed in
>> >> both dmesg and apm. apmd is started at
legends:
-->
-=>
=->
==>
<--
<=-
<-=
<==
--- /usr/src/usr.bin/fstat/fstat.c Wed Oct 23 00:40:27 2013
+++ /usr/src/usr.bin/fstat/fstat.c Thu May 22 15:59:22 2014
@@ -616,6 +616,23 @@
}
}
+void print_connection_state(uint32_t s)
+{char *o,p[]=" <==> ";
+ if(SS_CONNECTOUT&s)
+ {o=p+1;
+ o[0]='
Hi,
This is not a bug.
If you want to have a chance of getting your diff accepted, send it to
the proper list (tech@) and make sure your formatting conforms to
KNF, the diff isn't mangled by your mailer and the neccesary man page
pieces are included.
-Otto
On Thu, May 22, 2014 at 04:1
Thanks!
It did not help unfortunately.
Below is copy of /var/log/Xorg.0.log, output from xrandr --verbose, $
xrandr --auto --verbose (is "crtc 0: disable" of importance?) and
finally $ xrandr --verbose again. Not much has changed though.
Looks like the driver finds booth monitors
[14.348] (--)
Hi there,
I use the latest version of -current:
OpenBSD 5.5-current (GENERIC.MP) #122: Wed May 21 08:45:26 MDT 2014
t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
I did "$ sudo sysmerge -d -s etc55.tgz -x xetc55.tgz" and got no hint
on changes related to 'kern.nosuidcored
Hi!
If fragmented IPv6 packets are redirected by pf, the code in pf_refragment6() of
pf_norm.c lacks a call to in6_proto_cksum_out() to calculate the checksum for
the packet before it is broken into fragments again.
The attached diff fixes this problem in OpenBSD 5.5.
-- Matthias
--- sys/net/pf_n
Unfortunately, it doesn't improve my situation either.
As reported in February [1], the detection of DVI/HDMI outputs is
sometimes successful, but most of time it isn't.
I haven't tested the update much yet (running since 2 hours with it),
but it seems it isn't introducing (additional) regression
Hello
If I boot the current snapshot (OpenBSD 5.5-current (GENERIC.MP) #139:
Wed May 21 09:38:42 MDT 2014) with a yubikey or usb-to-serial device
attached the port is no longer available if the device is removed.
When unplugged the yubikey message is:
wskbd2: disconnecting from wsdisplay0
On 05/21/14 20:01, Zen Floater wrote:
> I am a learning student and was going through the FAQ pages
> which lead me to reading man pages and eventually man 1 intro.
>
> http://www.openbsd.org/faq/faq2.html
>
> Lead me to this next link.
>
> http://www.openbsd.org/cgi-bin/man.cgi?query=intro&sekt
This actually should be fixed..
On 22 May 2014 19:55, "Nick Holland" wrote:
> On 05/21/14 20:01, Zen Floater wrote:
> > I am a learning student and was going through the FAQ pages
> > which lead me to reading man pages and eventually man 1 intro.
> >
> > http://www.openbsd.org/faq/faq2.html
> >
>
12 matches
Mail list logo