public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Oliver Seitz <info@vtnd.de>
To: intel-gfx@lists.freedesktop.org
Subject: crash when loading intelfb on D945GSEJT board
Date: Sun, 13 Feb 2011 08:50:07 +0100	[thread overview]
Message-ID: <4D578D2F.3000501@vtnd.de> (raw)

Hi.

I can not make intelfb run on intel board D945GSEJT. I've tried a very 
clean setup, here's what I've done:

 > Install a minimal debian squeeze (stable)

$ wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.37.tar.bz2
$ tar -xf linux-2.6.37.tar.bz2
$ cd linux-2-6-37
$ make defconfig

 > using "make menuconfig", I enabled "Configure standard features", 
disabled "i915", enabled as module "intelfb" with "intelfb_debug"

$ make
$ make modules_install
$ update-initramfs -c -k 2.6.37
$ make install
$ update-grub

When rebooting, the machine crashes in the init sequence by performing a 
reboot, over and over again. Starting the old kernel, I did:

$ echo "blacklist intelfb" >>/etc/modprobe.d/fbdev-blacklist.conf

Now, the machine boots to a working text mode.

$ modprobe intelfb idonly
FATAL: Error inserting intelfb (/path/to/module/intelfb.ko): No such device

The commands

$ modprobe intelfb probeonly
and
$ modprobe intelfb noregister

execute without error, the module is loaded

The commands

$ modprobe intelfb noinit
and
$ modprobe intelfb

lead to a crash by instant reboot.

Have I done something wrong, or is the 2.6.37 intelfb module broken?

Greets,
Kiste

             reply	other threads:[~2011-02-13  7:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-13  7:50 Oliver Seitz [this message]
2011-02-13 10:31 ` crash when loading intelfb on D945GSEJT board Oliver Seitz
2011-02-13 10:34 ` Julien Cristau
2011-02-13 11:19   ` Oliver Seitz
2011-02-13 17:40     ` Tino Keitel
2011-02-13 17:58       ` Oliver Seitz
2011-02-15 23:35         ` Tino Keitel
2011-02-16  6:21           ` Oliver Seitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D578D2F.3000501@vtnd.de \
    --to=info@vtnd.de \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox