All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Fenzi <kevin@scrye.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: X and 2.4.0 problem (video bios probing?)
Date: Fri, 5 Jan 2001 14:08:31 -0700 (MST)	[thread overview]
Message-ID: <20010105210831.2001.qmail@scrye.com> (raw)
In-Reply-To: <E14Ee3z-0008R6-00@the-village.bc.nu>
In-Reply-To: <20010105210016.1778.qmail@scrye.com> <E14Ee3z-0008R6-00@the-village.bc.nu>

>>>>> "Alan" == Alan Cox <alan@lxorguk.ukuu.org.uk> writes:

>> (II) Loading /usr/X11R6/lib/modules/linux/libint10.a (II) Module
>> int10: vendor="The XFree86 Project" compiled for 4.0.1a, module
>> version = 1.0.0 ABI class: XFree86 Video Driver, version 0.2 (EE)
>> ATI(0): Unable to initialise int10 interface.

Alan> Thats the critical bit but it isnt directly a kernel thing. Im
Alan> not sure why it should have failed. Do you have different
Alan> .config options (eg ATI fb options ?)

nope. I did do a 'make oldconfig' after patching to 2.4.0 (final), but
all the other options are the same. 

I was not using the ATI fb in either case. I had it built as a module,
"ATI Rage 128 display support (EXPERIMENTAL)" (that I didn't load)
and I did have "VESA VGA graphics console" enabled. 

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

  reply	other threads:[~2001-01-05 21:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-05 21:00 X and 2.4.0 problem (video bios probing?) Kevin Fenzi
2001-01-05 21:06 ` Alan Cox
2001-01-05 21:08   ` Kevin Fenzi [this message]
2001-01-06  1:41   ` X and 2.4.0 problem (video bios probing?) (more info) Kevin Fenzi
2001-01-06  5:30   ` X and 2.4.0 problem (video bios probing?) (SOLUTION!) Kevin Fenzi

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=20010105210831.2001.qmail@scrye.com \
    --to=kevin@scrye.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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.