mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* 2.0.37 crashes immediately
@ 2001-01-16 23:35 Stefan Ring
  2001-01-17  0:08 ` Dr. Kelsey Hudson
  2001-01-17  4:08 ` Mike A. Harris
  0 siblings, 2 replies; 8+ messages in thread
From: Stefan Ring @ 2001-01-16 23:35 UTC (permalink / raw)
  To: linux-kernel

2.0.37+ kernels crash even before I can see the "Uncompressing linux..."
message. I use the same configuration for 2.0.36 and 2.0.37 (basically
it's the default configuration without anything interesting changed), and
the latter just won't work. It also doesn't matter if I use zImage or
bzImage. Kernel compiled with a stock redhat 4.2 (gcc 2.7.2.1). My machine
configuration is as follows:

ASUS CUBX-E MB
PIII Coppermine
512MB SDRAM
3c905-tx
guillemot tnt2 m64
ibm dtla-307030 & 305020, quantum fireball ex 6.4

-
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/

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: 2.0.37 crashes immediately
  2001-01-16 23:35 2.0.37 crashes immediately Stefan Ring
@ 2001-01-17  0:08 ` Dr. Kelsey Hudson
  2001-01-17  9:00   ` Stefan Ring
  2001-01-17  4:08 ` Mike A. Harris
  1 sibling, 1 reply; 8+ messages in thread
From: Dr. Kelsey Hudson @ 2001-01-17  0:08 UTC (permalink / raw)
  To: Stefan Ring; +Cc: linux-kernel

On Wed, 17 Jan 2001, Stefan Ring wrote:

> 2.0.37+ kernels crash even before I can see the "Uncompressing linux..."
> message. I use the same configuration for 2.0.36 and 2.0.37 (basically
> it's the default configuration without anything interesting changed), and
> the latter just won't work. It also doesn't matter if I use zImage or
> bzImage. Kernel compiled with a stock redhat 4.2 (gcc 2.7.2.1). My machine
> configuration is as follows:
> 
> ASUS CUBX-E MB
> PIII Coppermine
> 512MB SDRAM
> 3c905-tx
> guillemot tnt2 m64
> ibm dtla-307030 & 305020, quantum fireball ex 6.4

Is there a reason you are using a relatively new machine like that with
such an outdated and arcane kernel (and distribution, for that
matter)? I'd suggest you upgrade to a more recent kernel and/or
distribution...it'll be a lot more stable (and not to mention secure!)

Good luck to you!

 Kelsey Hudson                                           khudson@ctica.com 
 Software Engineer
 Compendium Technologies, Inc                               (619) 725-0771
---------------------------------------------------------------------------     

-
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/

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: 2.0.37 crashes immediately
  2001-01-16 23:35 2.0.37 crashes immediately Stefan Ring
  2001-01-17  0:08 ` Dr. Kelsey Hudson
@ 2001-01-17  4:08 ` Mike A. Harris
  2001-01-17  9:43   ` Stefan Ring
  1 sibling, 1 reply; 8+ messages in thread
From: Mike A. Harris @ 2001-01-17  4:08 UTC (permalink / raw)
  To: Stefan Ring; +Cc: linux-kernel

On Wed, 17 Jan 2001, Stefan Ring wrote:

>Date: Wed, 17 Jan 2001 00:35:39 +0100 (MET)
>From: Stefan Ring <e9725446@student.tuwien.ac.at>
>To: linux-kernel@vger.kernel.org
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>Subject: 2.0.37 crashes immediately
>
>2.0.37+ kernels crash even before I can see the "Uncompressing linux..."
>message. I use the same configuration for 2.0.36 and 2.0.37 (basically
>it's the default configuration without anything interesting changed), and
>the latter just won't work. It also doesn't matter if I use zImage or
>bzImage. Kernel compiled with a stock redhat 4.2 (gcc 2.7.2.1). My machine
>configuration is as follows:

Holy ancient and unsupported kernel + distribution batman.  ;o)

Have you tried 2.0.39 (said with a slight grin)  ;o)

Seriously, why not upgrade to Red Hat 7.0?  You'll get a lot more
help with any troubles you may have.  Subscribe to the Red Hat
guinness-list and I'd be glad to help with such a transition.

Good luck!


----------------------------------------------------------------------
    Mike A. Harris  -  Linux advocate  -  Free Software advocate
          This message is copyright 2001, all rights reserved.
  Views expressed are my own, not necessarily shared by my employer.
----------------------------------------------------------------------
If it weren't for C, we'd all be programming in BASI and OBOL.

-
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/

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: 2.0.37 crashes immediately
  2001-01-17  0:08 ` Dr. Kelsey Hudson
@ 2001-01-17  9:00   ` Stefan Ring
  2001-01-17  9:15     ` David Weinehall
  2001-01-17  9:24     ` Andreas Dilger
  0 siblings, 2 replies; 8+ messages in thread
From: Stefan Ring @ 2001-01-17  9:00 UTC (permalink / raw)
  To: Dr. Kelsey Hudson; +Cc: linux-kernel

On Tue, 16 Jan 2001, Dr. Kelsey Hudson wrote:

> Is there a reason you are using a relatively new machine like that with
> such an outdated and arcane kernel (and distribution, for that
> matter)? I'd suggest you upgrade to a more recent kernel and/or
> distribution...it'll be a lot more stable (and not to mention secure!)

Every version above 2.0.36 behaves the same (from the 2.0.x series). Gee,
I should have said a few words about my intent. Of course, I'm not
actually using these old versions of everything. I just wanted to run a
2.0.x kernel to do some hardware testing, and since 2.0.x can't access the
new ext2fs with the spare superblock option, I thought, I might be up and
running fastest by installing a RH distribution still using the 2.0.x
kernel. It just happened that RH4.2 was the only one I had handy at that
moment.

-
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/

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: 2.0.37 crashes immediately
  2001-01-17  9:00   ` Stefan Ring
@ 2001-01-17  9:15     ` David Weinehall
  2001-01-17  9:24     ` Andreas Dilger
  1 sibling, 0 replies; 8+ messages in thread
From: David Weinehall @ 2001-01-17  9:15 UTC (permalink / raw)
  To: Stefan Ring; +Cc: Dr. Kelsey Hudson, linux-kernel

On Wed, Jan 17, 2001 at 10:00:31AM +0100, Stefan Ring wrote:
> On Tue, 16 Jan 2001, Dr. Kelsey Hudson wrote:
> 
> > Is there a reason you are using a relatively new machine like that with
> > such an outdated and arcane kernel (and distribution, for that
> > matter)? I'd suggest you upgrade to a more recent kernel and/or
> > distribution...it'll be a lot more stable (and not to mention secure!)
> 
> Every version above 2.0.36 behaves the same (from the 2.0.x series).
> Gee, I should have said a few words about my intent. Of course, I'm
> not actually using these old versions of everything. I just wanted to
> run a 2.0.x kernel to do some hardware testing, and since 2.0.x can't
> access the new ext2fs with the spare superblock option, I thought, I
> might be up and running fastest by installing a RH distribution still
> using the 2.0.x kernel. It just happened that RH4.2 was the only one I
> had handy at that moment.

Actually, v2.0.39 _does_ cope with sparse superblocks.


/David
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Project MCA Linux hacker        //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </
-
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/

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: 2.0.37 crashes immediately
  2001-01-17  9:00   ` Stefan Ring
  2001-01-17  9:15     ` David Weinehall
@ 2001-01-17  9:24     ` Andreas Dilger
  1 sibling, 0 replies; 8+ messages in thread
From: Andreas Dilger @ 2001-01-17  9:24 UTC (permalink / raw)
  To: Stefan Ring; +Cc: Dr. Kelsey Hudson, linux-kernel

Stefan Ring writes:
> Every version above 2.0.36 behaves the same (from the 2.0.x series). Gee,
> I should have said a few words about my intent. Of course, I'm not
> actually using these old versions of everything. I just wanted to run a
> 2.0.x kernel to do some hardware testing, and since 2.0.x can't access the
> new ext2fs with the spare superblock option, I thought, I might be up and
> running fastest by installing a RH distribution still using the 2.0.x
> kernel.

Actually, if you have the 2.0.39 kernel (or a pre-patch), it can use the
sparse ext2 superblock feature.  Even so, it is only a matter of turning the
sparse_super flag on or off and running e2fsck on the filesystem to convert.

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert
-
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/

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: 2.0.37 crashes immediately
  2001-01-17  4:08 ` Mike A. Harris
@ 2001-01-17  9:43   ` Stefan Ring
  2001-01-17 12:33     ` David Weinehall
  0 siblings, 1 reply; 8+ messages in thread
From: Stefan Ring @ 2001-01-17  9:43 UTC (permalink / raw)
  To: Mike A. Harris; +Cc: linux-kernel

> Holy ancient and unsupported kernel + distribution batman.  ;o)
> 
> Have you tried 2.0.39 (said with a slight grin)  ;o)

Ahh, it was my fault. I forgot about binutils. Strange enough, 2.0.36
worked and 2.0.37 not. There is no change to the Changes file between
these two versions, however.

-
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/

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: 2.0.37 crashes immediately
  2001-01-17  9:43   ` Stefan Ring
@ 2001-01-17 12:33     ` David Weinehall
  0 siblings, 0 replies; 8+ messages in thread
From: David Weinehall @ 2001-01-17 12:33 UTC (permalink / raw)
  To: Stefan Ring; +Cc: Mike A. Harris, linux-kernel

On Wed, Jan 17, 2001 at 10:43:13AM +0100, Stefan Ring wrote:
> > Holy ancient and unsupported kernel + distribution batman.  ;o)
> > 
> > Have you tried 2.0.39 (said with a slight grin)  ;o)
> 
> Ahh, it was my fault. I forgot about binutils. Strange enough, 2.0.36
> worked and 2.0.37 not. There is no change to the Changes file between
> these two versions, however.

Nope, I think Alan missed this out. I updated the Changes file for
v2.0.39, hopefully it should be a little more accurate now.


/David
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Project MCA Linux hacker        //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </
-
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/

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2001-01-17 12:34 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-01-16 23:35 2.0.37 crashes immediately Stefan Ring
2001-01-17  0:08 ` Dr. Kelsey Hudson
2001-01-17  9:00   ` Stefan Ring
2001-01-17  9:15     ` David Weinehall
2001-01-17  9:24     ` Andreas Dilger
2001-01-17  4:08 ` Mike A. Harris
2001-01-17  9:43   ` Stefan Ring
2001-01-17 12:33     ` David Weinehall

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®