* Intel 810(E) driver in Kernel 2.6.10 - same problem as in 2.6.9
@ 2004-12-25 19:34 John McGowan
2004-12-25 20:17 ` Alan Cox
0 siblings, 1 reply; 5+ messages in thread
From: John McGowan @ 2004-12-25 19:34 UTC (permalink / raw)
To: linux-kernel
Intel 810(E) driver in Kernel 2.6.10 - same problem as in 2.6.9
Fedora Core2; xorg 6.8.1 (and 6.7.x); kernel 2.6.9/2.6.10
(other problem in earlier 2.6.x?)
Intel i810(E) driver
As reported for kernel 2.6.9, since rc1 the intel810(E) support seems to be
broken and the driver does not even work half way, as it did in kernel 2.6.7.
As in 2.6.9, the screen (xorg, 6.8.1; intel 810(E)) comes up with junk
(unable to access the memory?). I did not try disabling (2D) acceleration
this time (as was suggested to a user of Fedora Core3 by the Fedora team as
as reported in one of the usenet groups) since that is much too slow and, as
I recall, did not fix the (apparent) memory leak (which also occurs in 2.6.7).
[memory leak in older 2.6.x kernels]
--
In 2.6.7 it seems memory is not freed either. Gimp-Gap (Gimp 2.0.x or 2.2.x).
Use move-path and move something over an image. OK ... one animation
... do it again (moving another item over the image). And again and again
... It appears that others have no problem(?) with, in kernel 2.6.?, xorg 6.8.1
and 6.7.x, the memory used by move-path being freed. With the intel 810(E) driver
(used by so few, admittedly), it is never freed (using "free" to see it use
up system, buffer and then swap memory). It is not even freed when Gimp is closed
down. One has to close X itself to get the 810(E) driver to free the memory
(unless it is a bug in xorg 6.7.x and 6.8.1). Is this similar to the kernel
2.6.8[.1] bug where the kernel would not free certain memory under certain
conditions (most notably breaking audio CD burning)? Is there a similar bug
in the earlier 2.6.x intel810(E) drivers?
So, I am back to kernel 2.6.7 (Fedora Core2) for some things, rebooting to
RH7.2 with a 2.4.x kernel when I want to get some work done in Gimp.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Intel 810(E) driver in Kernel 2.6.10 - same problem as in 2.6.9
2004-12-25 19:34 Intel 810(E) driver in Kernel 2.6.10 - same problem as in 2.6.9 John McGowan
@ 2004-12-25 20:17 ` Alan Cox
2004-12-26 5:09 ` John McGowan
0 siblings, 1 reply; 5+ messages in thread
From: Alan Cox @ 2004-12-25 20:17 UTC (permalink / raw)
To: John McGowan; +Cc: Linux Kernel Mailing List
On Sad, 2004-12-25 at 19:34, John McGowan wrote:
> Intel 810(E) driver in Kernel 2.6.10 - same problem as in 2.6.9
>
> Fedora Core2; xorg 6.8.1 (and 6.7.x); kernel 2.6.9/2.6.10
> (other problem in earlier 2.6.x?)
> Intel i810(E) driver
In my case at least updating the X server packages fixed it.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Intel 810(E) driver in Kernel 2.6.10 - same problem as in 2.6.9
2004-12-25 20:17 ` Alan Cox
@ 2004-12-26 5:09 ` John McGowan
2004-12-26 17:44 ` Alan Cox
0 siblings, 1 reply; 5+ messages in thread
From: John McGowan @ 2004-12-26 5:09 UTC (permalink / raw)
To: Alan Cox; +Cc: Linux Kernel Mailing List
On Sat, 25 Dec 2004, Alan Cox wrote:
> On Sad, 2004-12-25 at 19:34, John McGowan wrote:
>> Intel 810(E) driver in Kernel 2.6.10 - same problem as in 2.6.9
>>
>> Fedora Core2; xorg 6.8.1 (and 6.7.x); kernel 2.6.9/2.6.10
>> (other problem in earlier 2.6.x?)
>> Intel i810(E) driver
>
> In my case at least updating the X server packages fixed it.
>
To which version? 6.8.1 (rpm build from Fedora Core xorg-6.8.1-12.src.rpm).
I see that 6.8.1 is the latest at xorg.
Fixed the memory or getting X to run at all on an 810?
Regards from:
John McGowan | jmcgowan@inch.com [Internet Channel]
| jmcgowan@coin.org [COIN]
--------------+-----------------------------------------------------
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Intel 810(E) driver in Kernel 2.6.10 - same problem as in 2.6.9
2004-12-26 5:09 ` John McGowan
@ 2004-12-26 17:44 ` Alan Cox
2004-12-26 21:02 ` John McGowan
0 siblings, 1 reply; 5+ messages in thread
From: Alan Cox @ 2004-12-26 17:44 UTC (permalink / raw)
To: John McGowan; +Cc: Linux Kernel Mailing List
On Sul, 2004-12-26 at 05:09, John McGowan wrote:
> To which version? 6.8.1 (rpm build from Fedora Core xorg-6.8.1-12.src.rpm).
> I see that 6.8.1 is the latest at xorg.
Right but there are patches in CVS beyond that and some are merged into
the FC testing/rawhide packages
> Fixed the memory or getting X to run at all on an 810?
I have 2D running nicely but not 3D
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Intel 810(E) driver in Kernel 2.6.10 - same problem as in 2.6.9
2004-12-26 17:44 ` Alan Cox
@ 2004-12-26 21:02 ` John McGowan
0 siblings, 0 replies; 5+ messages in thread
From: John McGowan @ 2004-12-26 21:02 UTC (permalink / raw)
To: Alan Cox; +Cc: Linux Kernel Mailing List
On Sun, 26 Dec 2004, Alan Cox wrote:
> On Sul, 2004-12-26 at 05:09, John McGowan wrote:
>> To which version? 6.8.1 (rpm build from Fedora Core xorg-6.8.1-12.src.rpm).
>> I see that 6.8.1 is the latest at xorg.
>
> Right but there are patches in CVS beyond that and some are merged into
> the FC testing/rawhide packages
>
>> Fixed the memory or getting X to run at all on an 810?
>
> I have 2D running nicely but not 3D
The fedora core 3 development branch has a source rpm which I built in
core 2. I am now using kernel 2.6.10 (still problems with gimp-gap
chewing up memory which isn't freed). Thanks for your time. Now I will
have to see if there is something newer at xorg.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2004-12-26 21:02 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-12-25 19:34 Intel 810(E) driver in Kernel 2.6.10 - same problem as in 2.6.9 John McGowan
2004-12-25 20:17 ` Alan Cox
2004-12-26 5:09 ` John McGowan
2004-12-26 17:44 ` Alan Cox
2004-12-26 21:02 ` John McGowan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).