From: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
To: linux-kernel@vger.kernel.org
Subject: VESA fb problem with 2.6.7-mm[567]
Date: Sun, 11 Jul 2004 22:36:59 +0200 [thread overview]
Message-ID: <20040711203659.GE2899@charite.de> (raw)
The nvidia graphics card in one of my laptops cannot be talked into
working with vesafb:
...
ACPI: PCI Interrupt Link [LNK5] enabled at IRQ 11
ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 11 (level, low) -> IRQ 11
PCI: Cannot allocate resource region 4 of device 0000:00:01.1
PCI: Cannot allocate resource region 5 of device 0000:00:01.1
vesafb: probe of vesafb0 failed with error -6
vga16fb: initializing
vga16fb: mapped to 0xc00a0000
fb0: VGA16 VGA frame buffer device
Simple Boot Flag at 0x36 set to 0x1
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
...
0000:01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 420 Go 32M] (rev a3) (prog-if 00 [VGA])
Subsystem: Hewlett-Packard Company: Unknown device 006d
Flags: bus master, 66MHz, medium devsel, latency 248, IRQ 11
Memory at ea000000 (32-bit, non-prefetchable) [size=16M]
Memory at f8000000 (32-bit, prefetchable) [size=64M]
Memory at fc000000 (32-bit, prefetchable) [size=512K]
Capabilities: [60] Power Management version 2
Capabilities: [44] AGP version 2.0
Short:
* vesafb fails
* vga16fb works
The same kernel works on another laptop with another nvidia card.
The only major difference is the unorthodox display resolution in this
laptop (WXGA, 1280x800).
--
Ralf Hildebrandt (Im Auftrag des Referat V a) Ralf.Hildebrandt@charite.de
Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155
Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-916
IT-Zentrum Standort Campus Mitte AIM. ralfpostfix
next reply other threads:[~2004-07-11 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-11 20:36 Ralf Hildebrandt [this message]
2004-07-11 20:49 ` VESA fb problem with 2.6.7-mm[567] Grzegorz Kulewski
2004-07-12 16:55 ` Giuseppe Bilotta
2004-07-11 21:45 ` Another FB Problem (trindentfb) Jim Gifford
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=20040711203659.GE2899@charite.de \
--to=ralf.hildebrandt@charite.de \
--cc=linux-kernel@vger.kernel.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 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.