My Linux crashes! - HELP

My Linux crashes! - HELP

Post by Miguel Arr » Mon, 23 Nov 1998 04:00:00



Hi!

  I have a 6400/180 with a SCSI and an IDE disks, and 48 MBytes of RAM.

  I installed LinuxPPC DR 4 that came on a french magazine (UniversMac)
on the IDE drive. But I'm having a lot of problems.

  I use BootX to boot linux. It boots OK, but it says that modules.conf
or something is empty.

  Then KDE starts. First time, so login as superuser. Start working with
KDE... and the thing sometimes doesn't do anything (when I click on the
app menus, the apps won't open) and dometimes (specially when I'm
working with Netscape) KDE hangs and I have to reboot the machine.

  On the reboot, Linux checks the partitions and says ALLWAYS that
"Deleted inode 34885 has zero dtime. FIXED". But the crash happens again
and again, and the program that checks partitions keeps saying "Deleted
inode 34885 has zero dtime. FIXED".

  I thought that maybe it was because of the kernel version (BootX
starts with 1.2.127 and my installation has 1.2.85 I guess). I installed
vmlinux 1.2.127 and the modules too. But when I boot it keeps sayng the
modules.conf is empty and is starts kerneld 1.2.85...

  I'a linux newbie, and I'm not understanding what a heck is going on
here. So, please HELP ME! :-)

  Send me a cc of your answer, please.

 Yours

Miguel Arroz

--

****** Guia Macintosh em Portugal - http://www.ip.pt/mac ******
   How to put your Mac on the Net / Softpage for Macintosh:
         http://www.geocities.com/SiliconValley/3232

 
 
 

My Linux crashes! - HELP

Post by jeramy aka yourmomslove » Mon, 23 Nov 1998 04:00:00


Modules.conf empty thing is no big deal.

KDE is a piece of sh*t and 48 megs of ram may not be good enough to run
it. Please don't flame me for saying that about KDE, its just my
opinion. Point is, make sure your swap partition is about 128 megs.
When i ran Mklinux with KDE for a brief 3 days, 48 megs of ram was how
much running KDE would take up. Even with Linux's generous memory
allocation scheme (unused memory is watsed memory) I thought this was
too much.

Right now, the best developer kernel is probably 2.1.125. But it even
crashes on boot-up sometimes for me.

Solutions:
1) Use a lighter window manager (fvwm, windowmaker).
:if you need help, theres a link at linuxppc.org on how to change window
managers
2) Make sure you have at LEAST 128 megs of swap space.
3) Get up to 64 megs of ram if possible anyway. Software isn't getting
any smaller and ram prices are cheap nowadays.
4) When the G4 chips come out and the G3 prives drop, get a newer mac.
The G3 desktop at work that I turned into an 2.1.125/Enlightenment
workstation has evryone awed.

 
 
 

My Linux crashes! - HELP

Post by Miguel Arr » Tue, 24 Nov 1998 04:00:00



Hi!

 Just a question: is it OK to be kernekd 1.2.85 with vmlinux 1.2.125?

Quote:> KDE is a piece of sh*t and 48 megs of ram may not be good enough to run
> it. Please don't flame me for saying that about KDE, its just my
> opinion. Point is, make sure your swap partition is about 128 megs.
> When i ran Mklinux with KDE for a brief 3 days, 48 megs of ram was how
> much running KDE would take up. Even with Linux's generous memory
> allocation scheme (unused memory is watsed memory) I thought this was
> too much.

 Well, I have 100 Mbytes of swap space, but OK

Quote:> Solutions:
> 1) Use a lighter window manager (fvwm, windowmaker).

 When I choose it on the Window managers menu at login, it appears just
like normal KDE. Is it normal? What is fvwm?

 Also, what is AfterStep? I heard it was a great window manager... ca I
use it? How?

Quote:> 3) Get up to 64 megs of ram if possible anyway. Software isn't getting
> any smaller and ram prices are cheap nowadays.
> 4) When the G4 chips come out and the G3 prives drop, get a newer mac.
> The G3 desktop at work that I turned into an 2.1.125/Enlightenment
> workstation has evryone awed.

 USA forever! :-) Here in Portugual stuff costs more and peolpe receive
less... maybe next year! :-(

 Yours

Miguel Arroz

--

****** Guia Macintosh em Portugal - http://www.ip.pt/mac ******
   How to put your Mac on the Net / Softpage for Macintosh:
         http://www.geocities.com/SiliconValley/3232

 
 
 

My Linux crashes! - HELP

Post by Niels Roes » Tue, 24 Nov 1998 04:00:00




> Hi!

>  Just a question: is it OK to be kernekd 1.2.85 with vmlinux 1.2.125?

Hey! New versions! But if you mean kerneld 2.1.85 & vmlinux 2.1.125,
that's ok. I use those too.

Quote:>  When I choose it on the Window managers menu at login, it appears just
> like normal KDE. Is it normal? What is fvwm?

Yeah, choosing fvwm does nothing. It's just an 'unimplemented feature'
(bug?)
fvwm is just another windowmanager, like AfterStep, twm, mwm, etc..

Quote:>  Also, what is AfterStep? I heard it was a great window manager... ca I
> use it? How?

Sure. Expect however to be juggling textfiles. The most userfriendly of
'm all
is still kde. For instance, check /etc/X11/xinit/Xclients.
In there kde gets started (exec startkde).
If you remove that, you'll end up with fvwm if that's installed.
Be careful, you could end up with a unbootable system!
Have fun,
Niels
 
 
 

1. Linux crashing. Help needed.

        Here is the scoop.  I have finally upgraded to
Linux 0.96a and have not had too many problems.  The MOST
annoying one is this:
        When downloading with Pcomm (I think 0.95a version) and
rz (zmodem receive, got from a netter), if rz aborts because of
too many errors or what I get this:
        Pcomm doesn't respond but I can type junk in that session.

        In ALL other "windows", I can't type anything.  

        If I press the scoll lock and get the debug info, it whole
thing stops.  I can't even go to any virtual consoles after that.

Any ideas?

Dan

--
-------------------------------------------------------------------------
 Dan Miner                         email:


2. mrouted ?

3. SMB makes files 0 size when linux crashes!! HELP!

4. Why ascii file formats??

5. Help with OpenBSD 3.1 crashes (/var/crash/ files included)

6. Intel 740 AGP card?

7. Need help with server crashes (/var/crash files included)

8. DNS

9. (for gurus) ISSUES: crashes, crash on boot, crash on shutdown

10. 2.0.34 keeps crashing and crashing and crashing and ...

11. Crashing Crashing Crashing

12. 2.0.34 keeps crashing and crashing and crashing and ...

13. ypbind crash crash crash