All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Fw: device mapper & cryptsetup error and   intelfb
Date: Tue, 4 Jan 2005 17:51:59 -0800	[thread overview]
Message-ID: <20050104175159.244105a7.akpm@osdl.org> (raw)


intelfb glitch...


Begin forwarded message:

Date: Wed, 29 Dec 2004 17:52:34 +0100
From: Mateusz Berezecki <mateuszb@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: device mapper & cryptsetup error and   intelfb


1)
Dec 29 17:42:41 localhost kernel: device-mapper: crypt: Error allocating 
crypto tfm
Dec 29 17:42:42 localhost kernel: device-mapper: error adding target to 
table
Dec 29 17:42:47 localhost udev[18896]: removing device node '/dev/dm-0'

invoked with command:

losetup /dev/loop0 /home/mb/fs1&&cryptsetup create crloop /dev/loop0 && 
mount /dev/mapper/crloop /media/crypted

2)

i also get a plenty of  such messages

intelfb: intelfb_check_var: accel_flags is 1
intelfb: the cursor was killed - restore it !!
intelfb: size 8, 16   pos 488, 0
intelfb: intelfb_check_var: accel_flags is 1
intelfb: the cursor was killed - restore it !!
intelfb: size 8, 16   pos 792, 80
intelfb: intelfb_check_var: accel_flags is 1
intelfb: the cursor was killed - restore it !!
intelfb: size 8, 16   pos 184, 752

Is it normal behaviour ?


hardware info:

0000:00:02.0 VGA compatible controller: Intel Corp. 
82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03)
thats from lspci
and lspci -v

0000:00:02.0 VGA compatible controller: Intel Corp. 
82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03) 
(prog-if 00 [VGA])
        Subsystem: Dell: Unknown device 0149
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at e0000000 (32-bit, prefetchable) [size=128M]
        Memory at f6f80000 (32-bit, non-prefetchable) [size=512K]
        Capabilities: [d0] Power Management version 1

Maybe this helps.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

             reply	other threads:[~2005-01-05  1:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05  1:51 Andrew Morton [this message]
2005-01-05 16:50 ` Fw: device mapper & cryptsetup error and intelfb Sylvain Meyer

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=20050104175159.244105a7.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.