Your message dated Sun, 26 Dec 2010 14:46:31 +0100
with message-id <[email protected]>
and subject line Re: Bug#592290: [linux-source-2.6.32] X.org does not work with 
Intel driver and 4GB RAM
has caused the Debian Bug report #592290,
regarding [linux-source-2.6.32] X.org does not work with Intel driver and 4GB 
RAM
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
592290: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592290
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-source-2.6.32
Version: 2.6.32-18
Severity: serious

--- Please enter the report below this line. ---

Hello everyone,

I've just realized that I still use the kernel parameter "mem=3500M"  at boot 
time. With 
this configuration everything works fine (besides the missing 500MB of RAM). 
When I remove 
this parameter X.org fails to work properly. I have only a very distorted 
log-in screen 
and cannot switch to any other console via ctrl+alt+F1. Since Bug #558237 was 
reported as 
resolved I hoped that this would resolve my issues as well, but it does not.
I'm not sure how to proceed in my case. How can I test if the changes mentioned 
in the 
upstream bug report ( http://bugs.freedesktop.org/show_bug.cgi?id=25510 ) have 
reached the 
Squeeze's current kernel version?

Best regards,

Matthias



--- System information. ---
Architecture: amd64
Kernel:       Linux 2.6.32-trunk-amd64

Debian Release: squeeze/sid
  500 testing         security.debian.org 
  500 testing         ftp2.de.debian.org 
  500 testing         dl.google.com 
  500 testing         debian.netcologne.de 
  500 stable          dl.google.com 

--- Package information. ---
Depends       (Version) | Installed
=======================-+-===========
binutils                | 2.20.1-12
bzip2                   | 1.0.5-4


Recommends      (Version) | Installed
=========================-+-===========
libc6-dev                 | 2.11.2-2
 OR libc-dev              | 
gcc                       | 4:4.4.4-2
make                      | 3.81-8


Suggests            (Version) | Installed
=============================-+-===========
libncurses-dev                | 
 OR ncurses-dev               | 
kernel-package                | 12.036
libqt3-mt-dev                 | 







--- End Message ---
--- Begin Message ---
Version: 2.6.32-29

On Sun, Dec 26, 2010 at 02:35:17PM +0100, Matthias Breier wrote:
> On Sunday 26 December 2010 12:34:47 Moritz Muehlenhoff wrote:
> > On Mon, Aug 09, 2010 at 12:04:25PM +0200, Matthias Breier wrote:
> > > > > I'm not sure how to proceed in my case. How can I test if the changes
> > > > > mentioned in the upstream bug report (
> > > > > http://bugs.freedesktop.org/show_bug.cgi?id=25510 ) have reached the
> > > > > Squeeze's current kernel version?
> > > > 
> > > > I'm pretty sure they are.  If your issue is still present in 2.6.35
> > > > (available in experimental), please file a bug against product=DRI,
> > > > component=DRM/intel at http://bugs.freedesktop.org/ and let us know the
> > > > bug number so we can track it.
> > > 
> > > I am currently running kernel version 2.6.35 and everything works fine
> > > without the memory limitation set by the kernel parameter. So the remedy
> > > for my issues are on the path to 2.6.35. How can I narrow down the
> > > patches curing this problem?
> > 
> > There have been quite a few DRM changes since then, does this still occur
> > with the current 2.6.32-29 kernel?
> > 
> > Cheers,
> >         Moritz
> 
> Oh, you are right, I forgot to check if the changes cure my problem. And 
> indeed they do! 
> :) I have just removed the mem-parameter from my grub-configuration, et 
> voila, it works! 
> Thank you very much for your efforts!

Thanks, closing the bug then.

Cheers,
        Moritz


--- End Message ---

Reply via email to