On 4 май 2015 г. 4:26:30 mark hellewell mark.hellew...@gmail.com wrote:
Hi,
Hi,
Today I reported a similar observation to misc. Did you find out any
more information? Some more info below.
I red your email. The only information I found was when I made a BIOS reset
- then I got 3-4
On Mon, 4 May 2015, Maximilian Pichler wrote:
From: Maximilian Pichler maxim.pich...@gmail.com
To: misc@openbsd.org
Date: Mon, 4 May 2015 06:19:13
Subject: iwm0: fatal firmware error / could not initiate scan
I'm getting these console errors on startup and each time I run
ifconfig iwm0
On 2015-05-03, Markus Rosjat ros...@ghweb.de wrote:
Am 03.05.2015 um 10:32 schrieb Stuart Henderson:
On 2015-05-02, Markus Rosjat ros...@ghweb.de wrote:
okay it seems dovecot runs root and not as the _dovecot user so applying
a login class for the dovecote group only helps if you add root to
On 4 May 2015 at 17:19, vl...@bsdbg.net wrote:
I red your email. The only information I found was when I made a BIOS reset
- then I got 3-4 silo overflows in dmesg per day which where much better.
Also every overflow was from 1 to 3 which didn't break NMEA sentence like
before.
Then I start
On Mon, May 04, 2015 at 01:10:25AM -0400, Sandrine Duvalier wrote:
On Sun, May 3, 2015 at 12:46 PM, Alexandre Ratchov a...@caoua.org wrote:
The volume keys always control the mixer of the first audio device,
this can't be changed without modifying the kernel.
If X is running, volume
2015-05-04 11:29 GMT+02:00 Alexandre Ratchov a...@caoua.org:
The bug is that the key is processed twice in two contradictory
ways (once by the kernel to control the mixer and once by X apps to
possibly control the mixer differently). When X is running either
the kernel or X apps should use
On Mon, May 04, 2015 at 08:56:08AM +0100, Dennis Davis wrote:
iwm0: hw rev: 0x140, fw ver 25.228 (API ver 9), address f8:16:54:dd:a7:0c
iwm0: fatal firmware error
iwm0: could not initiate scan
Don't have an iwm interface. But is the firmware installed?
Yes, the firmware is installed at
Hi,
just installed the current snapshot and I am running cwm.
M-. should spawn the 'ssh to' dialog.
It works fine if the known_hosts file exists (with entries or blank does
not matter),
but the dialog is not spawned if the file is missing.
IMO the dialog should be spawned also if the
On Mon, May 4, 2015 at 6:10 AM, Stefan Sperling s...@stsp.name wrote:
Is the following thread of any use:
http://openbsd-archive.7691.n7.nabble.com/iwm0-fatal-firmware-error-on-current-td267434.html
That might be it. Maximilian, can you please try this patch which was
committed by jsg@ in
On Mon, May 04, 2015 at 11:53:49AM +0200, ludovic coues wrote:
2015-05-04 11:29 GMT+02:00 Alexandre Ratchov a...@caoua.org:
The bug is that the key is processed twice in two contradictory
ways (once by the kernel to control the mixer and once by X apps to
possibly control the mixer
I actually think that feature should be removed; cwm shouldn't need to
re-implement kwown_hosts parsing just for auto-completion. For simple
entries, it has worked, but when once there are multiples or even v6
addresses, it's too much for a window manager to do all this just for
auto-completion.
Hello Kawamata-san,
KAWAMATA Yoshihiro wrote on Sat, May 02, 2015 at 10:51:19PM +0900:
I found this problem when I was building my OpenBSD LiveCD FuguIta.
For LiveCD, it is very important to get more disk space, so I've
compressed manpages by gzip.
Oh, i see. For that purpose, you can
On Mon, May 04, 2015 at 08:22:28PM -0400, Steve Shockley wrote:
Does anyone know if the Dell PERC S300 controller will work under
OpenBSD as a non-RAID SAS HBA? It has an LSI SAS 1068e, but I didn't
know if they did something to make it not work as an HBA. Thanks.
I don't believe the
I have a configuration on my box running OpenBSD 5.6 with errata that is
supposed to tunnel IPv4 over IPv6. However, due to bugged RFC 2473
implementations shared across ALL BSD systems, pf's af-to comes into play
when I decide to navigate through the abhorrent path MTU discovery issue
found in
Does anyone know if the Dell PERC S300 controller will work under
OpenBSD as a non-RAID SAS HBA? It has an LSI SAS 1068e, but I didn't
know if they did something to make it not work as an HBA. Thanks.
Hi
I dont want to purchase 5.7 CDs and pay international shipping (also done
have a CD drive). I would like to donate that amount instead.
From the OpenBSD Project donations page (
http://www.openbsd.org/donations.html) I gather that donations to OpenBSD
Project are different from donations to
We follow -current on amd64, upgrading about once a month.
Occasional WinSCP (5.7.1, 5.7.2) clients, which previously worked fine, appear
to be unable to connect following recent upgrades to -current. We don't know
exactly which snapshot this stopped working. FileZilla on Linux clients still
On Mon, May 04, 2015 at 09:23:53PM -0700, lawgi...@nym.hush.com wrote:
We follow -current on amd64, upgrading about once a month.
Thanks!
[...]
debug1: Client protocol version 2.0; client software version
WinSCP_release_5.7.2
[...]
Hm, kex protocol error: type 30 seq 1 [preauth]
message
On Tue, May 5, 2015, at 12:19 AM, Hrishikesh Muruk wrote:
Hi
I dont want to purchase 5.7 CDs and pay international shipping (also done
have a CD drive). I would like to donate that amount instead.
From the OpenBSD Project donations page (
http://www.openbsd.org/donations.html) I gather
On 5/4/2015 at 9:39 PM, Darren Tucker dtuc...@zip.com.au wrote:
[...]
debug1: Client protocol version 2.0; client software version
WinSCP_release_5.7.2
[...]
Hm, kex protocol error: type 30 seq 1 [preauth]
message type 30 is the pre-RFC4419 group exchange message. Since
RFC4419 was published
On Tue, May 05, 2015 at 05:19:13AM BST, Hrishikesh Muruk wrote:
Hi
Hi Hrishikesh,
I dont want to purchase 5.7 CDs and pay international shipping (also
done have a CD drive). I would like to donate that amount instead.
You don't need a CD drive in order to support the project :^)
From the
Perhaps it would be helpful if the man page inteldrm(4)
mentioned this, so people can avoid buying unsupported hardware.
Come on, are you serious about this? The man page of inteldrm(4) has a
section intel(4) where you can see the supported hardware very nice
listed. It is super-giga-quite
On Sun, May 03, 2015 at 11:26:26AM +, Jona Joachim wrote:
On 2015-04-29, Cristián Edwards cri...@gmail.com wrote:
Problem is that only the ugen driver is present... so I think there is no
chance of speaking with the modem.
Will read the link thoruoughly
You have a cdce device. As
On 05/02/15 01:46, Edgar Pettijohn III wrote:
On May 1, 2015, at 6:09 PM, Daniel Melameth wrote:
On Fri, May 1, 2015 at 3:09 PM, Kevin spy...@gmail.com wrote:
How does one go about specifying a custom 404 page w/the new httpd?
This seems like the correct directive:
error_page 404
I use the auto-complete feature quite a bit, myself.
M-. typetabdown-arrow is a relatively common use for me.
On 2015 May 04 (Mon) at 11:09:08 -0400 (-0400), Okan Demirmen wrote:
:I actually think that feature should be removed; cwm shouldn't need to
:re-implement kwown_hosts parsing just for
On Monday, May 4, 2015, Mihai Popescu mih...@gmail.com
javascript:_e(%7B%7D,'cvml','mih...@gmail.com'); wrote:
Perhaps it would be helpful if the man page inteldrm(4)
mentioned this, so people can avoid buying unsupported hardware.
Come on, are you serious about this? The man page of
Perhaps I have missed something, but intel(4) is the xorg driver
(which is the slow one identified by the helpful people on the list).
It is indeed a bit confusing to me at least that inteldrm(4) points to
the intel(4) list of hardware, which contains hardware that is not yet
suppported by the
27 matches
Mail list logo
