Boot fails after CSLIP (slackware v2.1.0) help?!

Boot fails after CSLIP (slackware v2.1.0) help?!

Post by Rodn » Sat, 26 Nov 1994 09:43:17



Gidday,

I have installed Linux (slackware 2.1.0) v1.1.59, only the `a'
series of disks.  The install runs fine (and I have had a previous
wersion of Linux ~March'94 running with NO probs until now!).

When booting up it then stops after the CSLIP has been loaded!

Can anyone offer some suggestions - this should be a vanilla install
'486 with tseng ET4000 8meg Ram 250meg IDE  - no scsi or sound or cdrom

(I do have a NE2000 compatible ethernet card installed tho!)

Kym A. Burgemeister
Department of Mechanical Engineering
University of Adelaide
South Australia                                            Ph.   +61 8 30 33156
5005                                                       Facs. +61 8 30 34367

===============================================================================

 
 
 

Boot fails after CSLIP (slackware v2.1.0) help?!

Post by Rodn » Sat, 26 Nov 1994 13:18:49



Quote:>Gidday,
>I have installed Linux (slackware 2.1.0) v1.1.59, only the `a'
>series of disks.  The install runs fine (and I have had a previous
>wersion of Linux ~March'94 running with NO probs until now!).
>When booting up it then stops after the CSLIP has been loaded!
>Can anyone offer some suggestions - this should be a vanilla install
>'486 with tseng ET4000 8meg Ram 250meg IDE  - no scsi or sound or cdrom
>(I do have a NE2000 compatible ethernet card installed tho!)

^^
I wrote this stuff and have discovered some more stuff since . . .

and from what I have been reading the NE2000 is a bit dodgey!

sure enough, I have removed it and it boots fine - it seems that it is
* because it doesn't detect the NE2000 properly -
it says eth0:3c509 not found - or words to that effect.

Does this mean I have to recompile the kernel?  ouch.  This does NOT sound
like fun.

any ideas?
_______________________________________________________________________________
Kym A. Burgemeister
Department of Mechanical Engineering
University of Adelaide
South Australia                                            Ph.   +61 8 30 33156
5005                                                       Facs. +61 8 30 34367

===============================================================================

 
 
 

Boot fails after CSLIP (slackware v2.1.0) help?!

Post by Paul Bud » Tue, 29 Nov 1994 12:45:52



Quote:>I have installed Linux (slackware 2.1.0) v1.1.59, only the `a'
>series of disks.  The install runs fine (and I have had a previous
>wersion of Linux ~March'94 running with NO probs until now!).
>When booting up it then stops after the CSLIP has been loaded!
>(I do have a NE2000 compatible ethernet card installed tho!)

I ran into this too.  I was not using the factory default settings on
the ne2000 and the probing at boot was crashing linux.  This must not
be an ancient bug since the old version of linux I had had no problem.
Anyway, at least for irq 5 address 0x320 I needed to give lilo the
option at boot time of ether=5,0x320,0,0,eth0.  This got me to a point
where I could log in anyhow but I still had problems until I changed my
network card address to 0x300 both in lilo.conf and with the jumpers on
the card.
--

 
 
 

1. help pls - fsck fail on boot; fixed, fsck still fails on boot

With the file system check during boot, get a report:
   *** An error occurred during the file system check
   ***   (blah, blah...)

From the shell, ran e2fsck -f on all Linux partitions.
The root partition had a couple of problems which fsck
supposedly fixed. (No critical files were affected, it
seems.  Interestingly, the affected files were ones I
had copied over from a DOS partition using automatic
CRLF-LF conversion.)  Rebooted, but got the same error
as before.  Reran e2fsck -f on all Linux partitions
again, all were reported as OK.  I only checked the
ext2 partitions, although there are a few non-Linux
partitions (FAT, HPFS, etc.); I assume fsck ignores
those, so even if they had a problem (I don't think
they do) that wouldn't seem to be an issue.

What is going on here?  I assume it is e2fsck that is
detecting the problem and returning an error code during
boot, so why doesn't it identify a problem when I run it
from the shell?  More urgently, how can I repair the
problem so I can boot Linux again?

(Yes, in case anyone is wondering, I ALWAYS do a normal
shutdown.  I am well aware how disastrous it can be to
power off the machine without shutting down first.)

Any help on this will be GREATLY appreciated, since a
reformat/reinstall does not especially appeal to me...

Regards,
Marty

2. NQS help

3. oops. Slackware hangs durring boot after CSLIP:

4. Broadcast PRoblems

5. slackware hangs durring boot after CSLIP:

6. system clock delay

7. Booting failed on CSLIP...

8. Apache for Linux

9. boot fails at CSLIP line

10. IO Overflow via putc() in GCC v2.6.3, Slackware v2.x Linux v1.2.11

11. Slackware Update - v2.0 to v2.1

12. Help: Slackware 96 initial boot fails

13. Problem with XFree v3.3 and FreeBSD v2.1.0 (HELP ME, PLEASE!!!)