On Sat, 26 Feb 2011 13:12:40 -0800, Steve McCarthy wrote:
(...)
The vesa driver works fine. I've since removed it and fbdev trying to
force the intel choice. Here's the resulting X.log:
(...)
(II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so (II) Module
intel: vendor=X.Org Foundation
On Sunday 27 Feb 2011, Camaleón wrote:
I wonder what is the current status for Sandy Bridge in current Debian
releases :-?
I've read that Intel X driver 2.14.0 does fully support that chipset
(H67) but you seem to be using 2.13.0 and Xorg 1.7.7. Will that combo
work?
Greetings,
Oh, I
Hello,
I followed this topic in December when Celejar was having difficulty, but
that solution doesn't help me. I recently bought a motherboard w/ H67
chip-set and i5 processor. I managed to purchase it 8 hours before the
Intel recall was announced - lucky me.
Xorg seems determined to
On Tue, Dec 21, 2010 at 08:59:17AM EST, Celejar wrote:
[..]
If we can establish that this was the problem (that it must be
built-in, and not built as a module), is this a bug? I suppose that I
should at least update the Wiki to warn about this.
Not sure if it's relevant, but this vaguely
On Wed, 22 Dec 2010 09:03:34 -0500
Chris Jones cjns1...@gmail.com wrote:
On Tue, Dec 21, 2010 at 08:59:17AM EST, Celejar wrote:
[..]
If we can establish that this was the problem (that it must be
built-in, and not built as a module), is this a bug? I suppose that I
should at least
On Wed, Dec 22, 2010 at 03:30:38PM EST, Celejar wrote:
On Wed, 22 Dec 2010 09:03:34 -0500
Chris Jones cjns1...@gmail.com wrote:
On Tue, Dec 21, 2010 at 08:59:17AM EST, Celejar wrote:
[..]
Not sure if it's relevant, but this vaguely reminds me of having had to
add my old ATI mach64's
On Wed, 22 Dec 2010 19:29:21 -0500
Chris Jones cjns1...@gmail.com wrote:
On Wed, Dec 22, 2010 at 03:30:38PM EST, Celejar wrote:
On Wed, 22 Dec 2010 09:03:34 -0500
Chris Jones cjns1...@gmail.com wrote:
On Tue, Dec 21, 2010 at 08:59:17AM EST, Celejar wrote:
[..]
Not sure if it's
On Tue, 21 Dec 2010 16:39:16 +0100
Sven Joachim svenj...@gmx.de wrote:
On 2010-12-21 14:59 +0100, Celejar wrote:
Okay, I've just booted into my new kernel with
CONFIG_FRAMEBUFFER_CONSOLE=y, and everything seems to be working fine!
If we can establish that this was the problem (that it
On Mon, 20 Dec 2010 20:12:11 -0500
Celejar cele...@gmail.com wrote:
On Mon, 20 Dec 2010 23:11:59 +0100
Sven Joachim svenj...@gmx.de wrote:
On 2010-12-20 22:52 +0100, Celejar wrote:
On Mon, 20 Dec 2010 22:35:55 +0100
Sven Joachim svenj...@gmx.de wrote:
Is
On 2010-12-21 14:59 +0100, Celejar wrote:
Okay, I've just booted into my new kernel with
CONFIG_FRAMEBUFFER_CONSOLE=y, and everything seems to be working fine!
If we can establish that this was the problem (that it must be
built-in, and not built as a module), is this a bug?
I would think
On Sun, 19 Dec 2010 22:56:55 -0500, Celejar wrote:
On Sun, 19 Dec 2010 22:25:55 +0100 Sven Joachim wrote:
On 2010-12-19 20:56 +0100, Celejar wrote:
Running uptodate Sid. I usually run self-compiled kernels (from
kernel.org git mainline repo) with standard Debian Sid X.
You need to
On 2010-12-20 04:56 +0100, Celejar wrote:
On Sun, 19 Dec 2010 22:25:55 +0100
Sven Joachim svenj...@gmx.de wrote:
On 2010-12-19 20:56 +0100, Celejar wrote:
Running uptodate Sid. I usually run self-compiled kernels (from
kernel.org git mainline repo) with standard Debian Sid X.
You
On 2010-12-20 16:45 +0100, Camaleón wrote:
Users with an Intel VGA card should always have the vesa driver
available and ready to be used, just in case, because such cards do not
have another alternative to use (while ati or nvidia chipsets can play
with 3/4 different set of drivers, Intel
On Mon, 20 Dec 2010 17:25:02 +0100, Sven Joachim wrote:
On 2010-12-20 16:45 +0100, Camaleón wrote:
Users with an Intel VGA card should always have the vesa driver
available and ready to be used, just in case, because such cards do not
have another alternative to use (while ati or nvidia
On 2010-12-20 17:42 +0100, Camaleón wrote:
On Mon, 20 Dec 2010 17:25:02 +0100, Sven Joachim wrote:
The vesa driver won't work with Kernel Mode Setting (which is mandatory
for current Intel driver versions), the fbdev driver is a better
fallback for KMS-enabled systems. Of course it does not
On Mon, 20 Dec 2010 18:16:42 +0100, Sven Joachim wrote:
On 2010-12-20 17:42 +0100, Camaleón wrote:
How bad... but fbdev also fails:
***
(II) LoadModule: fbdev
(WW) Warning, couldn't open module fbdev (II) UnloadModule: fbdev
(EE) Failed to load module fbdev (module does not exist, 0)
On Monday 20 December 2010 18:40:02 Camaleón wrote:
On Mon, 20 Dec 2010 18:16:42 +0100, Sven Joachim wrote:
Why not? :-)
Because I'm seeing (one day and another, in this same list and in other
Debian lists) that Intel driver is failing (crashing) very often and
doesn't seem to provide an
On 2010-12-20 18:40 +0100, Camaleón wrote:
On Mon, 20 Dec 2010 18:16:42 +0100, Sven Joachim wrote:
On 2010-12-20 17:42 +0100, Camaleón wrote:
Hummm, I wouldn't like to have an Intel VGA chipset nowadays O:-)
Why not? My (four years old) laptop has always worked fine, and Intel
chipsets
On Mon, 20 Dec 2010 19:02:33 +0100, Thierry Chatelet wrote:
On Monday 20 December 2010 18:40:02 Camaleón wrote:
On Mon, 20 Dec 2010 18:16:42 +0100, Sven Joachim wrote:
Why not? :-)
Because I'm seeing (one day and another, in this same list and in other
Debian lists) that Intel driver is
On Mon, 20 Dec 2010 18:16:42 +0100
Sven Joachim svenj...@gmx.de wrote:
On 2010-12-20 17:42 +0100, Camaleón wrote:
On Mon, 20 Dec 2010 17:25:02 +0100, Sven Joachim wrote:
The vesa driver won't work with Kernel Mode Setting (which is mandatory
for current Intel driver versions), the
On Mon, 20 Dec 2010 15:45:55 + (UTC)
Camaleón noela...@gmail.com wrote:
On Sun, 19 Dec 2010 22:56:55 -0500, Celejar wrote:
On Sun, 19 Dec 2010 22:25:55 +0100 Sven Joachim wrote:
On 2010-12-19 20:56 +0100, Celejar wrote:
Running uptodate Sid. I usually run self-compiled
On Mon, 20 Dec 2010 19:02:33 +0100
Thierry Chatelet tchate...@free.fr wrote:
...
Well, I don't want to start a war, but I have machines with Intel, nvidia
and
ati graphic card. Intel one has proved to be the stable one over the past two
and a half years. And it was going to be a must for
On Mon, 20 Dec 2010 19:18:25 +0100
Sven Joachim svenj...@gmx.de wrote:
On 2010-12-20 18:40 +0100, Camaleón wrote:
On Mon, 20 Dec 2010 18:16:42 +0100, Sven Joachim wrote:
On 2010-12-20 17:42 +0100, Camaleón wrote:
Hummm, I wouldn't like to have an Intel VGA chipset nowadays O:-)
On 2010-12-20 21:55 +0100, Celejar wrote:
On Mon, 20 Dec 2010 19:18:25 +0100
Sven Joachim svenj...@gmx.de wrote:
- Black screen when the i915 kernel module loads. This happened even to
me some day¹, but the kernel developers are shaking out the KMS bugs,
so this should become less of
On Mon, 20 Dec 2010 15:50:42 -0500, Celejar wrote:
On Mon, 20 Dec 2010 15:45:55 + (UTC) Camaleón wrote:
By reading your xorg log error, I see two problems here:
Thanks for the help (as always!), but you may be confusing two different
problems. The X log is from my initial problem,
On Mon, 20 Dec 2010 17:15:43 +0100
Sven Joachim svenj...@gmx.de wrote:
On 2010-12-20 04:56 +0100, Celejar wrote:
On Sun, 19 Dec 2010 22:25:55 +0100
Sven Joachim svenj...@gmx.de wrote:
On 2010-12-19 20:56 +0100, Celejar wrote:
Running uptodate Sid. I usually run self-compiled
On Mon, 20 Dec 2010 22:14:12 +0100
Sven Joachim svenj...@gmx.de wrote:
On 2010-12-20 21:55 +0100, Celejar wrote:
On Mon, 20 Dec 2010 19:18:25 +0100
Sven Joachim svenj...@gmx.de wrote:
- Black screen when the i915 kernel module loads. This happened even to
me some day¹, but the
On Mon, 20 Dec 2010 21:14:09 + (UTC)
Camaleón noela...@gmail.com wrote:
On Mon, 20 Dec 2010 15:50:42 -0500, Celejar wrote:
On Mon, 20 Dec 2010 15:45:55 + (UTC) Camaleón wrote:
...
1/ Intel driver is failing (not normal but users are accustomed to
this)
Accustomed?!
On 2010-12-20 22:17 +0100, Celejar wrote:
On Mon, 20 Dec 2010 17:15:43 +0100
Sven Joachim svenj...@gmx.de wrote:
This may be due to the use of a framebuffer in grub2, or because
CONFIG_FRAMEBUFFER_CONSOLE is not set in the kernel configuration. For
the former, try to disable the framebuffer
On Mon, 20 Dec 2010 22:35:55 +0100
Sven Joachim svenj...@gmx.de wrote:
On 2010-12-20 22:17 +0100, Celejar wrote:
On Mon, 20 Dec 2010 17:15:43 +0100
Sven Joachim svenj...@gmx.de wrote:
This may be due to the use of a framebuffer in grub2, or because
CONFIG_FRAMEBUFFER_CONSOLE is not set
On 2010-12-20 22:52 +0100, Celejar wrote:
On Mon, 20 Dec 2010 22:35:55 +0100
Sven Joachim svenj...@gmx.de wrote:
Is CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY set?
No - should it be? The help says 'if unsure, select n', so I figured
it was best left off, since I'm certainly not sure ;)
On Mon, 20 Dec 2010 23:11:59 +0100
Sven Joachim svenj...@gmx.de wrote:
On 2010-12-20 22:52 +0100, Celejar wrote:
On Mon, 20 Dec 2010 22:35:55 +0100
Sven Joachim svenj...@gmx.de wrote:
Is CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY set?
No - should it be? The help says 'if unsure,
Hi,
Running uptodate Sid. I usually run self-compiled kernels (from
kernel.org git mainline repo) with standard Debian Sid X. This has
been working fine for years (except, of course, for the occasional,
temporary X breakage), but starting recently (presumably after some X
upgrade), X bails on
On 2010-12-19 20:56 +0100, Celejar wrote:
Running uptodate Sid. I usually run self-compiled kernels (from
kernel.org git mainline repo) with standard Debian Sid X.
You need to set CONFIG_DRM_I915_KMS=y in your kernel configuration. See
the recent bug reports on the xserver-xorg-video-intel
On Sun, 19 Dec 2010 22:25:55 +0100
Sven Joachim svenj...@gmx.de wrote:
On 2010-12-19 20:56 +0100, Celejar wrote:
Running uptodate Sid. I usually run self-compiled kernels (from
kernel.org git mainline repo) with standard Debian Sid X.
You need to set CONFIG_DRM_I915_KMS=y in your
35 matches
Mail list logo
