public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Joshua M. Schmidlkofer" <menion@srci.iwpsd.org>
To: Linux kernel Development Mailing List  <linux-kernel@vger.kernel.org>
Subject: 2.4.6-preX, 2.4.6...
Date: Tue, 10 Jul 2001 09:10:51 -0600	[thread overview]
Message-ID: <3B4B1AFB.1090506@srci.iwpsd.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]

I have a strange problem, and I browsed the archives, but I don't see it 
being reported.  [God, what's the point.?  It's probably far too 
ambiguous to be useful.]

My System
HP Vectra VL8, 128 Ram, pIII 500, Matrox G200 [embedded], 2 Twelve-gig 
IDE drives.
Redhat 7.1 [Although, I don't think it matters]

I am using 'kgcc' [a.k.a. egcs-2.91.66] for compiling the kernel.

I have not located exactly [in which patch] the problem began, but if 
try to boot w/2.4.6-preX - 2.4.6,  the video goes away. And then it 
seems to lock up the computer.   At first I had APGART + DRI + MatroxFB. 
  So I removed the FB drivers, and tried again.   Same problems.   So I 
modularized Agpart, and DRI, [I need them for my X config].  No Change. 
  Almost immediatly after 'Uncompressing Linux.....'   I see a rush of 
the text across the screen, and then the screen flashes, and blinks, and 
then nothing.   I do not even have a  chance to see anything at all.  

I can't tell what's locking up, I tried a SysRQ, but got nothing.   No 
screen. *sigh*   I am not equiped to do this over a serial or parallel 
port.   I was hoping that someone would have a clue.  

In the mean time, I am expirimenting with different things. [kernel 
config's]   I will try to narrow it to a pre-release from 6.


thanks,
   Joshua

[-- Attachment #2: 2.4.6.config.bz2 --]
[-- Type: application/octet-stream, Size: 3535 bytes --]

             reply	other threads:[~2001-07-10 15:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-10 15:10 Joshua M. Schmidlkofer [this message]
2001-07-10 17:56 ` 2.4.6-preX, 2.4.6 Andreas Dilger
2001-07-11 18:59 ` Joshua M. Schmidlkofer

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=3B4B1AFB.1090506@srci.iwpsd.org \
    --to=menion@srci.iwpsd.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox