GM45 works fine playing html5 videos in firefox for me
OpenBSD 5.4-current (GENERIC.MP) #150: Thu Nov 14 00:30:57 MST 2013
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4161064960 (3968MB)
avail mem = 4042162176 (3854MB)
mainbus0 at root
bios0 at mainbus0: SM
On Sat, Nov 16, 2013 at 5:03 PM, Claudio wrote:
> Unfortunately today I was able to reproduce the issue by simply going to
> youtube with chromium and browsing around (not even reproducing any video)
To find exact problematic code path, have you considered using
google octane or other browser te
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.
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 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 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 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
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
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
Hello,
I'm running the latest snapshot on a thinkpad T400 witha an intel GM45 intel
video card.
After some use I get errors in dmesg and sometimes it glxinfo reports switching
to sw rendering, it can always be triggered simply by trying to use youtube in
chromium.
Even when glxinfo reports st
30 matches
Mail list logo
