2013/11/13 Bruno Delbono
> Stop ranting away on the demerits of disabling apm (and now pci - right!
> wtf?!).
>
He's not. He's rambling about you twisting knobs without having any kind of
clue as to why or how it would have helped, probably based on an outdated
guide which now also don't know w
I'm the tech Bruno has been working with regarding this. QEMU version is 1.5
and the relevant section of the KVM Config file is "
4". We've
tried it with 2 sockets, with 4 sockets, with 2 threads, 4 threads, and so on.
ACPI and APIC are enabled for the KVM Container.
Jeff Fuhrman
Level 2 Tech
Sigh, Theo. Seriously I am asking for your help to find out the issue as its
unique to OpenBSD. Stop ranting away on the demerits of disabling apm (and now
pci - right! wtf?!). Like dude, have you never tried variations of anything
except default bsd kernel? Why is tinkering (and not even perma
Theo, fine. Truce. I just got advice from jirib@ to ask my provider about:
Show qemu/kvm args!
Ask provider what does he use, which qemu/KVM, which distro...
Try to define 2 sockets, each one core, I bet it will work.
.
I will report back as soon as they do this. And include full dmesg
> Sigh, Theo. Seriously I am asking for your help to find out the
> issue as its unique to OpenBSD.
> Stop ranting away on the demerits of disabling apm (and now pci - right!
> wtf?!).
Then stop justifying your blind following of what you read on the web.
It looks too much like incompetence.
> As for why completely random disabling apm and acpi...rant by you and Theo...
Bullshit.
Perhaps the solution you are looking for is:
boot -c
> disable pci*
You never know, it just might work.
We are not ranting. We're telling you that you don't know what the
hell you are doing, an
Mike,
I've asked the provider to look into it.
As for why completely random disabling apm and acpi...rant by you and
Theo...please see that they are all output that have been tried including
booting generic.mp. Its not that it was randomly disabled, it was tested to see
if there is a differen
On Wed, Nov 13, 2013 at 10:29:34PM +0100, Peter J. Philipp wrote:
> He took the advice from me on IRC. I had googled and found a similar
> mail from someone who could not see 2 cpu's but only 1, people told that
> person to disable apm, but granted the mails were a little dated.
>
> So I was givi
Am Mon, 11 Nov 2013 22:08:20 +
schrieb Laurence Rochfort :
> Hello,
>
> I'm trying to configure my laptop so that a normal user may mount a
> CD/DVD or playback a DVD in Xine.
>
> So far I've just put an entry in /etc/fbtab. /cdrom permissions look
> OK, but the devices themselves less so.
>
On 11/13/13 22:13, Mike Larkin wrote:
> On Wed, Nov 13, 2013 at 09:44:11PM +0100, Otto Moerbeek wrote:
>> On Wed, Nov 13, 2013 at 08:26:57PM +, Bruno Delbono wrote:
>>
>>> Hi Otto,
>>>
>>> http://pastebin.com/zfkEUxX8
>>>
>>> This is generic.mp with flags of apm and acpi disable
>>>
>
> Why w
> On Wed, Nov 13, 2013 at 09:44:11PM +0100, Otto Moerbeek wrote:
> > On Wed, Nov 13, 2013 at 08:26:57PM +, Bruno Delbono wrote:
> >
> > > Hi Otto,
> > >
> > > http://pastebin.com/zfkEUxX8
> > >
> > > This is generic.mp with flags of apm and acpi disable
> > >
>
> Why would you start tryin
On Wed, Nov 13, 2013 at 09:44:11PM +0100, Otto Moerbeek wrote:
> On Wed, Nov 13, 2013 at 08:26:57PM +, Bruno Delbono wrote:
>
> > Hi Otto,
> >
> > http://pastebin.com/zfkEUxX8
> >
> > This is generic.mp with flags of apm and acpi disable
> >
Why would you start trying to disable random de
* Paolo Aglialoro [131113 14:37]:
> Hi Jim,
>
> just today I had compiled the kernel (after fiddling with GENERIC and
> sli_pci.c) with this result:
>
> pci0 at vpci0
> sli0 at pci0 dev 0 function 0 "Emulex LPe11000" rev 0x02: ivec 0x794
> sli1 at pci0 dev 0 function 1 "Emulex LPe11000" rev 0x02
On Wed, Nov 13, 2013 at 08:26:57PM +, Bruno Delbono wrote:
> Hi Otto,
>
> http://pastebin.com/zfkEUxX8
>
> This is generic.mp with flags of apm and acpi disable
>
> http://pastebin.com/PEjCr2vY
>
> Generic.MP boot.
>
> I am not sure what is wrong and why this works with all the other OS'
Hi Jim,
just today I had compiled the kernel (after fiddling with GENERIC and
sli_pci.c) with this result:
pci0 at vpci0
sli0 at pci0 dev 0 function 0 "Emulex LPe11000" rev 0x02: ivec 0x794
sli1 at pci0 dev 0 function 1 "Emulex LPe11000" rev 0x02: ivec 0x795
also I have:
# pcidump
Domain /dev/p
Hi Otto,
http://pastebin.com/zfkEUxX8
This is generic.mp with flags of apm and acpi disable
http://pastebin.com/PEjCr2vY
Generic.MP boot.
I am not sure what is wrong and why this works with all the other OS's...
--
Bruno Delbono
| Cognitive Researcher - Human Behavioural Project
| Real Soc
On Wed, Nov 13, 2013 at 07:36:58PM +, Bruno Delbono wrote:
> Hello,
>
>
> I have a QEMU instance that works perfectly fine at detecting cpu cores on
> NetBSD/FreeBSD/Linux. All except OpenBSD 5.4
>
>
> - I have tried the GENERIC amd64 and i386 bsd.mp kernel and the bsd.mp
> snapshot kernel
* Chris Cappuccio [13 11:41]:
> Paolo Aglialoro [paol...@gmail.com] wrote:
> > Hello,
> >
> > just tried today on a sparc64 T1000 running 5.4 release the card, but,
> > unfortunately, sli(4) cannot configure it as dmesg says:
> >
> > pci0 at vpci0
> > "Emulex LPe11000" rev 0x02 at pci0 dev 0
On Wed, Nov 13, 2013 at 08:28:14PM +0100, Stefan Sperling wrote:
> On Wed, Nov 13, 2013 at 09:07:48PM +0200, Ville Valkonen wrote:
> > ahem.. you are not revealing all the needed information "Tried to
> > compile, but got an error". Please specify all the commands you used
> > in compiling, thanks.
Hello,
I have a QEMU instance that works perfectly fine at detecting cpu cores on
NetBSD/FreeBSD/Linux. All except OpenBSD 5.4
- I have tried the GENERIC amd64 and i386 bsd.mp kernel and the bsd.mp
snapshot kernel.
- I have tried disabling apm and acpi* during boot config
I am completely los
On Wed, Nov 13, 2013 at 09:07:48PM +0200, Ville Valkonen wrote:
> ahem.. you are not revealing all the needed information "Tried to
> compile, but got an error". Please specify all the commands you used
> in compiling, thanks. Wild guess, you forgot to make depend?
No he didn't. 'make depend' is t
On 13 November 2013 20:31, wrote:
On 13.11.2013 20:24, Theo de Raadt wrote:
I have updated the BIOS already to A26. The story is that everything
was
great after KMS was introduced, but then at some point a "diff was
reduced to Linux" or something else, which caused aforementioned
problems.
On 13-11-11 11:48 PM, Chris Cappuccio wrote:
Adam Thompson [athom...@athompso.net] wrote:
Well, you could - perhaps - flip this on its head. Instead of changing BGP,
what about forcing one router to be the master (via advbase/advskew),
advertising a lower BGP preference (probably by using both
On 13 November 2013 20:31, wrote:
> On 13.11.2013 20:24, Theo de Raadt wrote:
>>>
>>> I have updated the BIOS already to A26. The story is that everything was
>>> great after KMS was introduced, but then at some point a "diff was
>>> reduced to Linux" or something else, which caused aforementione
cieti.lv> writes:
> > bios0: vendor Dell Inc. version "A24" date 12/06/2011
> > bios0: Dell Inc. Latitude E4300
>
> > This model has "Latitude E4300 System BIOS A26" available.
>
> I have updated the BIOS already to A26. The story is that everything was
> great after KMS was introduced, but th
On 13.11.2013 20:24, Theo de Raadt wrote:
I have updated the BIOS already to A26. The story is that everything
was
great after KMS was introduced, but then at some point a "diff was
reduced to Linux" or something else, which caused aforementioned
problems.
Awesome! So since you know it was a
> I have updated the BIOS already to A26. The story is that everything was
> great after KMS was introduced, but then at some point a "diff was
> reduced to Linux" or something else, which caused aforementioned
> problems.
Awesome! So since you know it was a diff, can you isolate it specifical
bios0: vendor Dell Inc. version "A24" date 12/06/2011
bios0: Dell Inc. Latitude E4300
This model has "Latitude E4300 System BIOS A26" available.
I have updated the BIOS already to A26. The story is that everything was
great after KMS was introduced, but then at some point a "diff was
reduce
On 11/13/13 14:54, Tomas Bodzar wrote:
my Dell E6320 (tried like 3 weeks ago or so), Chromium was simply just
crashing all the time.
A fix for chromium went in to ports around the 4 November:
http://marc.info/?l=openbsd-ports&m=138353073228230
port:fred ~> chrome --version
Chromium 30.0.1599
On Wed, Nov 13, 2013 at 10:03:58AM -0500, Brian Callahan wrote:
> On 11/13/2013 9:56 AM, Christian Weisgerber wrote:
> >ropers wrote:
> >
> >>Having long wanted to run http://www.openbsd.org/loongson.html, I've
> >>just seen that the main EU vendor of Loongson/Lemote/Yeeloong has
> >>finally -temp
On Wed, Nov 13, 2013 at 4:54 PM, Tomas Bodzar wrote:
> Yeah, however Firefox is running pretty badly after introduction of KMS on
> my Dell E6320 (tried like 3 weeks ago or so), Chromium was simply just
> crashing all the time.
could you provide dmesg with most recent -current?
cieti.lv> writes:
>
> Hello dear OpenBSD people,
>
> does anyone of the developers have time to look at this issue? It is the
> same problem I reported here:
> http://marc.info/?l=openbsd-bugs&m=137388801502300&w=2 but unfortunately
bios0: vendor Dell Inc. version "A24" date 12/06/2011
bio
> On Wed, Nov 13, 2013 at 11:47 AM, wrote:
>
> > :I am talking about recent snapshot. I use -current from 7/30/13 and I
> >>
> >> Recent as in "the last 4 days". The recent fixes are *very* *very*
> >> recent.
> >>
> > OK, thanks for now. I'll test it and report the results as soon as I get
> >
On 11/13/2013 9:56 AM, Christian Weisgerber wrote:
ropers wrote:
Having long wanted to run http://www.openbsd.org/loongson.html, I've
just seen that the main EU vendor of Loongson/Lemote/Yeeloong has
finally -temporarily, they say- significantly cut the hitherto
relatively high cost of these m
On Wed, Nov 13, 2013 at 1:35 PM, ropers wrote:
> Having long wanted to run http://www.openbsd.org/loongson.html, I've
> just seen that the main EU vendor of Loongson/Lemote/Yeeloong has
> finally âtemporarily, they sayâ significantly cut the hitherto
> relatively high cost of these machines.
ropers wrote:
> Having long wanted to run http://www.openbsd.org/loongson.html, I've
> just seen that the main EU vendor of Loongson/Lemote/Yeeloong has
> finally -temporarily, they say- significantly cut the hitherto
> relatively high cost of these machines.
> I'm not going to spam the URL, but
On Wed, Nov 13, 2013 at 4:18 PM, Claudio wrote:
> After updating the bios and setting setperf I can no longer reproduce the
> issue :), I'll try enabling apmd again later and check how it runs.
>
> (On an unrelated note Firefox uses incredibly high amounts of cpu compared to
> chromium and is ve
On Wed, Nov 13, 2013 at 03:20:58PM +0200, Alexey Suslikov wrote:
> On Wed, Nov 13, 2013 at 3:18 PM, Claudio wrote:
> > On Wed, Nov 13, 2013 at 03:06:08PM +0200, Alexey Suslikov wrote:
> >> On Wed, Nov 13, 2013 at 2:30 PM, Claudio wrote:
> >> > On Wed, Nov 13, 2013 at 12:12:47PM +, Alexey E. S
On Wed, Nov 13, 2013 at 3:18 PM, Claudio wrote:
> On Wed, Nov 13, 2013 at 03:06:08PM +0200, Alexey Suslikov wrote:
>> On Wed, Nov 13, 2013 at 2:30 PM, Claudio wrote:
>> > On Wed, Nov 13, 2013 at 12:12:47PM +, Alexey E. Suslikov wrote:
>> >> Tomas Bodzar gmail.com> writes:
>> >>
>> >> > Right
Laurence Rochfort wrote:
> What are the consequences of putting myself in the operator group?
Members of group operator may
* run shutdown(8),
* read disk devices--intended for backups with dump(8), but of course
it means that members can bypass any filesystem-permission-based
read restricti
On Wed, Nov 13, 2013 at 03:06:08PM +0200, Alexey Suslikov wrote:
> On Wed, Nov 13, 2013 at 2:30 PM, Claudio wrote:
> > On Wed, Nov 13, 2013 at 12:12:47PM +, Alexey E. Suslikov wrote:
> >> Tomas Bodzar gmail.com> writes:
> >>
> >> > Right, my fault. Missed complete path in output. Those are fo
On Wed, Nov 13, 2013 at 2:30 PM, Claudio wrote:
> On Wed, Nov 13, 2013 at 12:12:47PM +, Alexey E. Suslikov wrote:
>> Tomas Bodzar gmail.com> writes:
>>
>> > Right, my fault. Missed complete path in output. Those are for Haswell
>>
>> Looking at mentioned commits, at least cursor update diffs
Having long wanted to run http://www.openbsd.org/loongson.html, I've
just seen that the main EU vendor of Loongson/Lemote/Yeeloong has
finally —temporarily, they say— significantly cut the hitherto
relatively high cost of these machines.
I'm not going to spam the URL, but if this interests you and
On Wed, Nov 13, 2013 at 12:12:47PM +, Alexey E. Suslikov wrote:
> Tomas Bodzar gmail.com> writes:
>
> > Right, my fault. Missed complete path in output. Those are for Haswell
>
> Looking at mentioned commits, at least cursor update diffs aren't
> strictly Haswell related. So Mesa update.
>
I
Tomas Bodzar gmail.com> writes:
> Right, my fault. Missed complete path in output. Those are for Haswell
Looking at mentioned commits, at least cursor update diffs aren't
strictly Haswell related. So Mesa update.
On Wed, Nov 13, 2013 at 12:07 PM, wrote:
> On Wed, Nov 13, 2013 at 11:47 AM, wrote:
>>
>> :I am talking about recent snapshot. I use -current from 7/30/13
and I
Recent as in "the last 4 days". The recent fixes are *very*
*very*
recent.
>>> OK, thanks for now. I'll
On Wed, Nov 13, 2013 at 11:47 AM, wrote:
:I am talking about recent snapshot. I use -current from 7/30/13
and I
Recent as in "the last 4 days". The recent fixes are *very*
*very*
recent.
OK, thanks for now. I'll test it and report the results as soon as
I get to my notebook.
Because eg. Cl
On Wed, Nov 13, 2013 at 11:47 AM, wrote:
> :I am talking about recent snapshot. I use -current from 7/30/13 and I
>>
>> Recent as in "the last 4 days". The recent fixes are *very* *very*
>> recent.
>>
> OK, thanks for now. I'll test it and report the results as soon as I get
> to my notebook.
>
:I am talking about recent snapshot. I use -current from 7/30/13 and I
Recent as in "the last 4 days". The recent fixes are *very* *very*
recent.
OK, thanks for now. I'll test it and report the results as soon as I get
to my notebook.
On 2013 Nov 13 (Wed) at 12:33:00 +0200 (+0200), ja...@cieti.lv wrote:
:I am talking about recent snapshot. I use -current from 7/30/13 and I
Recent as in "the last 4 days". The recent fixes are *very* *very*
recent.
--
I often quote myself; it adds spice to my conversation.
--
Please try a most recent snapshot. There have been massive fixes added
since 5.4, and some especially important fixes added very recently.
On 2013 Nov 13 (Wed) at 10:51:45 +0200 (+0200), ja...@cieti.lv wrote:
:Hello dear OpenBSD people,
:
:does anyone of the developers have time to look at this
Please try a most recent snapshot. There have been massive fixes added
since 5.4, and some especially important fixes added very recently.
On 2013 Nov 13 (Wed) at 10:51:45 +0200 (+0200), ja...@cieti.lv wrote:
:Hello dear OpenBSD people,
:
:does anyone of the developers have time to look at this
Hello dear OpenBSD people,
does anyone of the developers have time to look at this issue? It is the
same problem I reported here:
http://marc.info/?l=openbsd-bugs&m=137388801502300&w=2 but unfortunately
it was not fixed.
After Mesa 9.x it got worse, now additionaly there are visual artifacts
Related to that is problem with new smartphones operating on MTP protocol
https://en.wikipedia.org/wiki/Media_Transfer_Protocol and not over regular
USB host.
Because of recently added fuse support in OpenBSD it may be possible to
access at least files, music, video on those phones eg. via
http://
This might help too
http://undeadly.org/cgi?action=article&sid=20131113030229&mode=expanded
On Wed, Nov 13, 2013 at 2:04 PM, Tomas Bodzar wrote:
> On Tue, Nov 12, 2013 at 9:48 PM, Laurence Rochfort <
> laurence.rochf...@gmail.com> wrote:
>
> > Thanks Fred,
> >
> > /cdrom is the mount point, so n
On Tue, Nov 12, 2013 at 9:48 PM, Laurence Rochfort <
laurence.rochf...@gmail.com> wrote:
> Thanks Fred,
>
> /cdrom is the mount point, so no I don't think it should be a symlink.
>
> The command is:
>
> $ mount /dev/cd0a /cdrom
> mount_cd9660: /dev/cd0a on /cdrom: Operation not permitted
>
You'r
56 matches
Mail list logo
