On 2012-11-05 11:10 +0100, John Hughes wrote:
> On 04/11/12 12:11, Sven Joachim wrote:
>>
>> Assuming that you still have the hardware:
>
> Aha, there's the rub - I fobbed it off on some other poor loser.
>> How much memory does your system have? If it's more than 2 Gigabyte,
>> try booting with
On 04/11/12 12:11, Sven Joachim wrote:
Assuming that you still have the hardware:
Aha, there's the rub - I fobbed it off on some other poor loser.
How much memory does your system have? If it's more than 2 Gigabyte,
try booting with the "mem=2G" kernel parameter.
As far as I remember it ha
Hi John,
coming back to an old problem of yours. Please read
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608133 to refresh your
memory.
On 2011-03-09 10:48 +0100, John Hughes wrote:
> A further piece of info.
>
> This bug only happens on 64 bit systems. If I install the 32 bit
> (x86) ver
More info - the system is not dead, I can SSH into it.
What syslog & dmesg show:
Mar 9 12:34:44 slender kernel: [ 269.492354] [drm] nouveau :00:05.0:
Allocating FIFO number 1
Mar 9 12:34:44 slender kernel: [ 269.492898] [drm] nouveau :00:05.0:
nouveau_channel_alloc: initialised FIF
A further piece of info.
This bug only happens on 64 bit systems. If I install the 32 bit (x86)
version of Debian I get no problem.
Will try changing kernel now.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists
5 matches
Mail list logo
