ext2 trouble in 1.3.3x kernels

ext2 trouble in 1.3.3x kernels

Post by Laszlo Vecs » Mon, 13 Nov 1995 04:00:00



I've been running 1.2.13 for some time now, all of my partitions
formatted as ext2. After upgrading to the 1.3 series, on bootup the
kernel has trouble finding one of my partitions, reporting the error:
"Can't find valid filesystem superblock"...

I'm running 1.2.9 ELF now and things are back to normal, the partition is
found just fine. Also, the Adaptec 1740 support in the 1.3 kernel is
broken (it works, but lots of errors now and then, lockups), but the 2940
support on my other system is rock stable in 1.3.35.

Also, is there an 8bit console character patch that I can apply to my 1.2
series kernel?

--
/----------------------------------------------------------\
| The Internet Nexus - http://www.internexus.net/~master/  |

\----------------------------------------------------------/

 
 
 

ext2 trouble in 1.3.3x kernels

Post by Andries Brouw » Tue, 14 Nov 1995 04:00:00


: I've been running 1.2.13 for some time now, all of my partitions
: formatted as ext2. After upgrading to the 1.3 series, on bootup the
: kernel has trouble finding one of my partitions, reporting the error:
: "Can't find valid filesystem superblock"...

Please be explicit - there is no kernel called "1.3 series",
and the behaviour of 1.3.40 is very different from that of 1.3.0.

: Also, is there an 8bit console character patch that I can apply to my 1.2
: series kernel?

I have no idea of what you could mean.
Most patches take more than 8 bits.
The kernel has always been 8-bit clean.

 
 
 

ext2 trouble in 1.3.3x kernels

Post by J Austin Dav » Tue, 14 Nov 1995 04:00:00


:I've been running 1.2.13 for some time now, all of my partitions
:formatted as ext2. After upgrading to the 1.3 series, on bootup the
:kernel has trouble finding one of my partitions, reporting the error:
:"Can't find valid filesystem superblock"...
:Also, the Adaptec 1740 support in the 1.3 kernel is
:broken (it works, but lots of errors now and then, lockups), but the 2940
:support on my other system is rock stable in 1.3.35.

  I am running a very stable 1.3.30 on IDE, but 1.3.37 said I had bad
blocks on ext2 (which, of course, I didn't really).  I've not tried 1.3.38 or
9, but I'm happy enough w/ 30 that I'll wait a bit.
====================================
Spark's Sixth Rule for Managers:
 If a subordinate asks you a pertinent question, look at him as
 if he had lost his senses.  When he looks down, paraphrase the
 question back at him.  
--

                  http://havoc.gtf.gatech.edu/austin/

 
 
 

1. SIOCADDRT errors when running route under 1.3.3x kernels

I have recently compiled version 1.3.35 on my Linux box.  When running
under 1.2.12 all network function work fine.  Under 1.3.35 I can not
even ping 127.0.0.1 (localhost).  The route command always returns
'SIOCADDRT: Invalid argument'.  I double checked and re-compiled
insuring that I enable Networking support and TCP/IP support although
I did not enable gatewaying, multicasting, firewalling, accounting,
or tunneling (don't ever remember enable such in 1.2.xx kernels). Do
I need to any of these in order to get my networking/route working
again.
Thanks in advance.

2. Linux port to Be box info

3. docs for SVR4 form(3x), menu(3x), and panel(3x)

4. Please HELP running XFree86!

5. kerneld and 1.3.3x?

6. dial-up access set-up prob. with red hat linux 7

7. 1.3.3X and ELF modules

8. Subroutine

9. 1.3.3x weirdness - /proc/cpuinfo

10. Volume problem with xmcd 1.3 / PAS16 SCSI / NEC CDR-500 (3x) cdrom

11. Solved: SIOCADDRT errors when running route under 1.3.3x

12. 1.3.xx kernel trouble

13. termcap trouble with 1.3.x kernels