On 2010-02-23, Sjoerd Hardeman wrote:
> This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
> --enig8A6162A10A29BD9D157868EB
> Content-Type: text/plain; charset=UTF-8; format=flowed
> Content-Transfer-Encoding: quoted-printable
>
> Charlie schreef:
>> On Tue, 23 Feb 2010 08:48:3
On Tue, 23 Feb 2010 21:39:00 -0500 Frank McCormick
shared this with us all:
>> I've already noted my problem on the KMS page of the Debian wiki;
>> you might want to, too:
>>
>> http://wiki.debian.org/KernelModesetting
>
> Now that's strange. I had to turn on KMS on my Intel 865 graphics
>boa
On Tue, 23 Feb 2010 19:00:53 -0500 Celejar shared
this with us all:
>On Tue, 23 Feb 2010 22:56:56 +0100
>wzab wrote:
>
>> I have just found the real source of problem - it is the Kernel Mode
>> Switch (KMS).
>> As soon as I have edited /etc/modprobe.d/i915-kms.conf
>> replacing "options i915 mod
Jeffrey Cao wrote:
On 2010-02-23, wzab wrote:
--TB36FDmn/VVEgNH/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Hi,
I have two different debian/testing systems. The common feature is the
Intel graphics chipset.
Both of them stopped to boot after upgrade which I perfor
On 2010-02-23, wzab wrote:
>
> --TB36FDmn/VVEgNH/
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> Hi,
>
> I have two different debian/testing systems. The common feature is the
> Intel graphics chipset.
> Both of them stopped to boot after upgrade which I performed b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 23 Feb 2010 19:00:53 -0500
Celejar wrote:
> On Tue, 23 Feb 2010 22:56:56 +0100
> wzab wrote:
>
> > I have just found the real source of problem - it is the Kernel
> > Mode Switch (KMS).
> > As soon as I have edited /etc/modprobe.d/i915-kms.
On Tue, 23 Feb 2010 22:56:56 +0100
wzab wrote:
> I have just found the real source of problem - it is the Kernel Mode Switch
> (KMS).
> As soon as I have edited /etc/modprobe.d/i915-kms.conf
> replacing "options i915 modeset=1" with "options i915 modeset=0"
> the problem disappeared on both machi
On Tue, 23 Feb 2010 22:56:56 +0100 wzab shared
this with us all:
>I have just found the real source of problem - it is the Kernel Mode
>Switch (KMS).
>As soon as I have edited /etc/modprobe.d/i915-kms.conf
>replacing "options i915 modeset=1" with "options i915 modeset=0"
>the problem disappeared
I have just found the real source of problem - it is the Kernel Mode Switch
(KMS).
As soon as I have edited /etc/modprobe.d/i915-kms.conf
replacing "options i915 modeset=1" with "options i915 modeset=0"
the problem disappeared on both machines.
So it seems, that this feature may be dangerous (espe
Charlie wrote:
| That did the trick removing Your help is much appreciated.
In case of both my systems problem was obviously not screen mode related.
I have removed using of framebuffer by grub. I have deinstalled "fonty".
I have switched off everything in /etc/init.d what was suspected to change
On Tue, 23 Feb 2010 10:23:51 +0100 Sjoerd Hardeman
shared this with us all:
>Charlie schreef:
>> On Tue, 23 Feb 2010 08:48:31 +0100 wzab shared
>> this with us all:
>>
>>> Hi,
>>>
>>> I have two different debian/testing systems. The common feature is
>>> the Intel graphics chipset.
>>> Both of
Charlie schreef:
On Tue, 23 Feb 2010 08:48:31 +0100 wzab shared
this with us all:
Hi,
I have two different debian/testing systems. The common feature is the
Intel graphics chipset.
Both of them stopped to boot after upgrade which I performed between
20.02 and 22.02 (the last successful boot l
On Tue, 23 Feb 2010 08:48:31 +0100 wzab shared
this with us all:
>Hi,
>
>I have two different debian/testing systems. The common feature is the
>Intel graphics chipset.
>Both of them stopped to boot after upgrade which I performed between
>20.02 and 22.02 (the last successful boot log is from the
13 matches
Mail list logo
