Linux-Setup Digest #755, Volume #20 Mon, 5 Mar 01 05:13:07 EST
Contents:
Modules problems when upgrading from 2.2.16-32 to 2.4.0 (Richard Ng)
Re: LILO at start prints "LI" ("Eric")
Re: 1024 cylinder limit ("Eric")
Re: I know I'm boring. . . but ("Eric")
Re: Test if mount was a sucess from shell script? (Lew Pitcher)
Re: multiboot help (=?iso-8859-1?Q?Zilla=A9?=)
vfat-Filesystem and UC/LC-conversion (Rainer Menzner)
Re: crc errors at boot ("Eric")
Re: Something to chew on.. (Soeren Ziehe)
Re: Gurus: How to configure Monitor? -- Newbie (Joris Roefs)
Re: Odd harddrive problems ("Eric")
----------------------------------------------------------------------------
From: Richard Ng <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.questions,linux.redhat.ppp,comp.os.linux.redhat
Subject: Modules problems when upgrading from 2.2.16-32 to 2.4.0
Date: Mon, 05 Mar 2001 07:12:12 GMT
Hi, I have the same problem. I also upgraded my RH7 with kernel 2.2.16 to
2.4.2. I have installed all the ppp modules in my kernel. I had tried
different versions(2.4.0, 2.4.0b2, 2.4.0b4) of ppp but none of them works.
All of the complain my kernel does not support ppp. It seems that there is a
miscommunication between ppp and kernel 2.4.2. I don't know whether
modutils-2.4.3 could help or not but I am using modutils-2.4.2. I will try
anyway. Thanks, in advance, for anyone who help.--Richard
Christos Dimitrakakis wrote:
> OK, I've installed ppp.2.4.0, kernel 2.4.2 (for amd) with
> ppp_generic, ppp_async, ppp_deflate and ppp_synctty as modules
>
> However, I get an error from pppd that kernel does not have support for
> PPP(!). It actually says to do modprobe -v ppp (of course ppp.o does not
> exist!).. hm..
>
> It looks like none of my modules get loaded under 2.4.2, (while my
> 2.2.16-32 installation works OK). lsmod only shows the dummy.o module
> loaded!!!!!!!!!
>
> Maybe I am missing some step .. maybe I should change some init files(?)
>
> Anyway, modprobe and insmode produce this output:
>
> <------------------modprobe/insmode outputs----------------------->
> [olethros@localhost olethros]$ /sbin/modprobe -v ppp
> modprobe: Can't locate module ppp
> [olethros@localhost olethros]$ /sbin/modprobe
> modprobe: Nothing to load ???
> Specify at least a module or a wildcard like \*
> [olethros@localhost olethros]$ /sbin/modprobe \*
> /lib/modules/2.4.2/kernel/drivers/parport/parport.o: unresolved symbol
> _mmx_memc
> py
> /lib/modules/2.4.2/kernel/drivers/parport/parport.o: insmod
> /lib/modules/2.4.2/k
> ernel/drivers/parport/parport.o failed
> /lib/modules/2.4.2/kernel/drivers/net/dummy.o: create_module: Operation
> not perm
> itted
> /lib/modules/2.4.2/kernel/drivers/net/dummy.o: insmod
> /lib/modules/2.4.2/kernel/
> drivers/net/dummy.o failed
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: unresolved symbol
> _mmx_memcpy
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: insmod
> /lib/modules/2.4.2/kernel/d
> rivers/net/slhc.o failed
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: unresolved symbol
> _mmx_memcpy
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: insmod
> /lib/modules/2.4.2/kernel/d
> rivers/net/slhc.o failed
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: unresolved symbol
> _mmx_memcpy
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: insmod
> /lib/modules/2.4.2/kernel/d
> rivers/net/slhc.o failed
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: unresolved symbol
> _mmx_memcpy
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: insmod
> /lib/modules/2.4.2/kernel/d
> rivers/net/slhc.o failed
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: unresolved symbol
> _mmx_memcpy
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: insmod
> /lib/modules/2.4.2/kernel/d
> rivers/net/slhc.o failed
> /lib/modules/2.4.2/kernel/drivers/parport/parport.o: unresolved symbol
> _mmx_memc
> py
> /lib/modules/2.4.2/kernel/drivers/parport/parport.o: insmod
> /lib/modules/2.4.2/k
> ernel/drivers/parport/parport.o failed
> /lib/modules/2.4.2/kernel/drivers/parport/parport.o: unresolved symbol
> _mmx_memc
> py
> /lib/modules/2.4.2/kernel/drivers/parport/parport.o: insmod
> /lib/modules/2.4.2/k
> ernel/drivers/parport/parport.o failed
> /lib/modules/2.4.2/kernel/drivers/parport/parport.o: unresolved symbol
> _mmx_memc
> py
> /lib/modules/2.4.2/kernel/drivers/parport/parport.o: insmod
> /lib/modules/2.4.2/k
> ernel/drivers/parport/parport.o failed
> /lib/modules/2.4.2/kernel/drivers/scsi/sg.o: unresolved symbol
> _mmx_memcpy
> /lib/modules/2.4.2/kernel/drivers/scsi/sg.o: insmod
> /lib/modules/2.4.2/kernel/dr
> ivers/scsi/sg.o failed
> /lib/modules/2.4.2/kernel/drivers/scsi/sr_mod.o: unresolved symbol
> _mmx_memcpy
> /lib/modules/2.4.2/kernel/drivers/scsi/sr_mod.o: insmod
> /lib/modules/2.4.2/kerne
> l/drivers/scsi/sr_mod.o failed
> /lib/modules/2.4.2/kernel/drivers/sound/ac97_codec.o: create_module:
> Operation n
> ot permitted
> /lib/modules/2.4.2/kernel/drivers/sound/ac97_codec.o: insmod
> /lib/modules/2.4.2/
> kernel/drivers/sound/ac97_codec.o failed
> /lib/modules/2.4.2/kernel/drivers/sound/ac97_codec.o: create_module:
> Operation n
> ot permitted
> /lib/modules/2.4.2/kernel/drivers/sound/ac97_codec.o: insmod
> /lib/modules/2.4.2/
> kernel/drivers/sound/ac97_codec.o failed
> /lib/modules/2.4.2/kernel/drivers/sound/soundcore.o: create_module:
> Operation no
> t permitted
> /lib/modules/2.4.2/kernel/drivers/sound/soundcore.o: insmod
> /lib/modules/2.4.2/k
> ernel/drivers/sound/soundcore.o failed
> /lib/modules/2.4.2/kernel/drivers/usb/usb-uhci.o: unresolved symbol
> _mmx_memcpy /lib/modules/2.4.2/kernel/drivers/usb/usb-uhci.o: insmod
> /lib/modules/2.4.2/kern
> el/drivers/usb/usb-uhci.o failed
> /lib/modules/2.4.2/kernel/drivers/usb/storage/usb-storage.o: unresolved
> symbol _
> mmx_memcpy
> /lib/modules/2.4.2/kernel/drivers/usb/storage/usb-storage.o: insmod
> /lib/modules
> /2.4.2/kernel/drivers/usb/storage/usb-storage.o failed
> /lib/modules/2.4.2/kernel/fs/fat/fat.o: unresolved symbol _mmx_memcpy
> /lib/modules/2.4.2/kernel/fs/fat/fat.o: insmod
> /lib/modules/2.4.2/kernel/fs/fat/
> fat.o failed
> /lib/modules/2.4.2/kernel/net/sunrpc/sunrpc.o: unresolved symbol
> _mmx_memcpy
> /lib/modules/2.4.2/kernel/net/sunrpc/sunrpc.o: insmod
> /lib/modules/2.4.2/kernel/
> net/sunrpc/sunrpc.o failed
> /lib/modules/2.4.2/kernel/fs/fat/fat.o: unresolved symbol _mmx_memcpy
> /lib/modules/2.4.2/kernel/fs/fat/fat.o: insmod
> /lib/modules/2.4.2/kernel/fs/fat/
> fat.o failed
> /lib/modules/2.4.2/kernel/net/sunrpc/sunrpc.o: unresolved symbol
> _mmx_memcpy
> /lib/modules/2.4.2/kernel/net/sunrpc/sunrpc.o: insmod
> /lib/modules/2.4.2/kernel/
> net/sunrpc/sunrpc.o failed
> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-15.o: create_module:
> Operation notpermitted
> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-15.o: insmod
> /lib/modules/2.4.2/ker
> nel/fs/nls/nls_iso8859-15.o failed
> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-7.o: create_module:
> Operation not p
> ermitted
> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-7.o: insmod
> /lib/modules/2.4.2/kern
> el/fs/nls/nls_iso8859-7.o failed
> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-4.o: create_module:
> Operation not p
> ermitted
> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-4.o: insmod
> /lib/modules/2.4.2/kern
> el/fs/nls/nls_iso8859-4.o failed
> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-3.o: create_module:
> Operation not p
> ermitted
> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-3.o: insmod
> /lib/modules/2.4.2/kern
> el/fs/nls/nls_iso8859-3.o failed
> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-2.o: create_module:
> Operation not p
> ermitted
> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-2.o: insmod
> /lib/modules/2.4.2/kern
> el/fs/nls/nls_iso8859-2.o failed
> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-1.o: create_module:
> Operation not p
> Using /lib/modules/2.4.2/kernel/drivers/net/slhc.o
> Symbol version prefix ''
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: unresolved symbol
> _mmx_memcpy
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: insmod
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o failed
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: insmod ppp_async failed
> [root@localhost olethros]# /sbin/modprobe -v slhc
> /sbin/insmod /lib/modules/2.4.2/kernel/drivers/net/slhc.o
> Using /lib/modules/2.4.2/kernel/drivers/net/slhc.o
> Symbol version prefix ''
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: unresolved symbol
> _mmx_memcpy
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: insmod
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o failed
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: insmod slhc failed
> [root@localhost olethros]# insmod
> bash: insmod: command not found
> [root@localhost olethros]# /sbin/insmod ppp
> insmod: ppp: no module by that name found
> [root@localhost olethros]# /sbin/insmod ppp_generic
> Using /lib/modules/2.4.2/kernel/drivers/net/ppp_generic.o
> /lib/modules/2.4.2/kernel/drivers/net/ppp_generic.o: unresolved symbol
> _mmx_memcpy
> /lib/modules/2.4.2/kernel/drivers/net/ppp_generic.o: unresolved symbol
> slhc_free_R2894cfb0
> /lib/modules/2.4.2/kernel/drivers/net/ppp_generic.o: unresolved symbol
> slhc_remember_R0bc55868
> /lib/modules/2.4.2/kernel/drivers/net/ppp_generic.o: unresolved symbol
> slhc_toss_Rf89e3455
> /lib/modules/2.4.2/kernel/drivers/net/ppp_generic.o: unresolved symbol
> slhc_uncompress_R3bc1319e
> /lib/modules/2.4.2/kernel/drivers/net/ppp_generic.o: unresolved symbol
> slhc_compress_R76135e6c
> /lib/modules/2.4.2/kernel/drivers/net/ppp_generic.o: unresolved symbol
> slhc_init_R2e0e927f
> [root@localhost olethros]# /sbin/insmod slhc
> Using /lib/modules/2.4.2/kernel/drivers/net/slhc.o
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o: unresolved symbol
> _mmx_memcpy
> [root@localhost olethros]#
>
> <----------------------------------------------------------------------->
>
> This is my modules.dep file:
>
> [root@localhost olethros]# more /lib/modules/2.4.2/modules.dep
> /lib/modules/2.4.2/kernel/drivers/char/lp.o:
> /lib/modules/2.4.2/kernel/driver
> s/parport/parport.o
> /lib/modules/2.4.2/kernel/drivers/net/dummy.o:
> /lib/modules/2.4.2/kernel/drivers/net/plip.o:
> /lib/modules/2.4.2/kernel/driver
> s/parport/parport.o
> /lib/modules/2.4.2/kernel/drivers/net/ppp_async.o:
> /lib/modules/2.4.2/kerne
> l/drivers/net/ppp_generic.o
> /lib/modules/2.4.2/kernel/drivers/net/ppp_deflate.o:
> /lib/modules/2.4.2/kerne
> l/drivers/net/ppp_generic.o
> /lib/modules/2.4.2/kernel/drivers/net/ppp_generic.o:
> /lib/modules/2.4.2/kerne
> l/drivers/net/slhc.o
> /lib/modules/2.4.2/kernel/drivers/net/ppp_synctty.o:
> /lib/modules/2.4.2/kerne
> l/drivers/net/ppp_generic.o
> /lib/modules/2.4.2/kernel/drivers/net/slhc.o:
> /lib/modules/2.4.2/kernel/drivers/parport/parport.o:
> /lib/modules/2.4.2/kernel/drivers/parport/parport_pc.o:
> /lib/modules/2.4.2/kerne
> l/drivers/parport/parport.o
> /lib/modules/2.4.2/kernel/drivers/scsi/sg.o:
> /lib/modules/2.4.2/kernel/drivers/scsi/sr_mod.o:
> /lib/modules/2.4.2/kernel/drivers/sound/ac97_codec.o:
> /lib/modules/2.4.2/kernel/drivers/sound/soundcore.o:
> /lib/modules/2.4.2/kernel/drivers/sound/via82cxxx_audio.o:
> /lib/modules/2.4
> .2/kernel/drivers/sound/soundcore.o \
> /lib/modules/2.4.2/kernel/drivers/sound/ac97_codec.o
> /lib/modules/2.4.2/kernel/drivers/usb/storage/usb-storage.o:
> /lib/modules/2.4.2/kernel/drivers/usb/usb-uhci.o:
> /lib/modules/2.4.2/kernel/fs/fat/fat.o:
> /lib/modules/2.4.2/kernel/fs/lockd/lockd.o:
> /lib/modules/2.4.2/kernel/net/su
> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-1.o:
> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-15.o:
> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-2.o:
> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-3.o:
> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-4.o:
> /lib/modules/2.4.2/kernel/fs/nls/nls_iso8859-7.o:
> /lib/modules/2.4.2/kernel/fs/smbfs/smbfs.o:
> /lib/modules/2.4.2/kernel/fs/vfat/vfat.o:
> /lib/modules/2.4.2/kernel/fs/fat/fat.o
> /lib/modules/2.4.2/kernel/net/ipx/ipx.o:
> /lib/modules/2.4.2/kernel/net/sunrpc/sunrpc.o:
>
> A<------------------------------------------------------->
>
> And this is my modules tree..
>
> [root@localhost 2.4.2]# ls -Rt
> .:
> modules.dep modules.pcimap pcmcia kernel build
>
> ./pcmcia:
>
> ./kernel:
> net fs drivers
>
> ./kernel/net:
> sunrpc ipx
>
> ./kernel/net/sunrpc:
> sunrpc.o
>
> ./kernel/net/ipx:
> ipx.o
>
> ./kernel/fs:
> fat lockd msdos nfs nls smbfs vfat
>
> ./kernel/fs/fat:
> fat.o
>
> ./kernel/fs/lockd:
> lockd.o
>
> ./kernel/fs/msdos:
> msdos.o
>
> ./kernel/fs/nfs:
> nfs.o
>
> ./kernel/fs/nls:
> nls_iso8859-1.o nls_iso8859-2.o nls_iso8859-4.o
> nls_iso8859-15.o nls_iso8859-3.o nls_iso8859-7.o
>
> ./kernel/fs/smbfs:
> smbfs.o
>
> ./kernel/fs/vfat:
> vfat.o
>
> ./kernel/drivers:
> net parport scsi sound usb char
>
> ./kernel/drivers/net:
> [root@localhost 2.4.2]# ls -Rt
> .:
> modules.dep modules.pcimap pcmcia kernel build
>
> ./pcmcia:
>
> ./kernel:
> net fs drivers
>
> ./kernel/net:
> sunrpc ipx
>
> ./kernel/net/sunrpc:
> sunrpc.o
>
> ./kernel/net/ipx:
> ipx.o
>
> ./kernel/fs:
> fat lockd msdos nfs nls smbfs vfat
>
> ./kernel/fs/fat:
> fat.o
>
> ./kernel/fs/lockd:
> lockd.o
>
> ./kernel/fs/msdos:
> msdos.o
>
> ./kernel/fs/nfs:
> nfs.o
>
> ./kernel/fs/nls:
> nls_iso8859-1.o nls_iso8859-2.o nls_iso8859-4.o
> nls_iso8859-15.o nls_iso8859-3.o nls_iso8859-7.o
>
> ./kernel/fs/smbfs:
> smbfs.o
>
> ./kernel/fs/vfat:
> vfat.o
>
> ./kernel/drivers:
> net parport scsi sound usb char
>
> ./kernel/drivers/net:
> dummy.o ppp_async.o ppp_generic.o slhc.o
> plip.o ppp_deflate.o ppp_synctty.o
>
> ./kernel/drivers/parport:
> parport.o parport_pc.o
>
> ./kernel/drivers/scsi:
> sg.o sr_mod.o
>
> ./kernel/drivers/sound:
> ac97_codec.o soundcore.o via82cxxx_audio.o
>
> ./kernel/drivers/usb:
> storage usb-uhci.o
>
> ./kernel/drivers/usb/storage:
> usb-storage.o
>
> ./kernel/drivers/char:
> lp.o
>
> -------------------------------------------------------------
>
> Hope someone can help me!!!!!!
>
> Christos Dimitrakakis
------------------------------
From: "Eric" <[EMAIL PROTECTED]>
Subject: Re: LILO at start prints "LI"
Date: Mon, 5 Mar 2001 08:30:24 +0100
> What changed on the disk from hanging on "LI" to booting ok?
>
The (physical) location of the bootfiles on the disk?
Eric
------------------------------
From: "Eric" <[EMAIL PROTECTED]>
Subject: Re: 1024 cylinder limit
Date: Mon, 5 Mar 2001 08:39:13 +0100
"> THIS bullshite is exactly why I don't fuck with LILO altogether. LILO was
> hosed back in 1994 becuse of the limit on beer cans, and now it's way
> ridiculous. This with LILO is about the last of my complaints with Linux,
an
> otherwise beautiful OS. I always use Loadlin, and will do so forever
unless
> the LILO developers get their heads out of their arses. Out of the two
> computers I successfully lit off Linux on, both used Loadlin, and neither
> could use LILO even with an old 128M hard drive.
>
> As I do any install, I observe that same LILO limit but NEVER attempt to
use
> LILO. And LILO never has worked for me except for a pathetic 128M hard
drive.
> Otherwise, I use Loadlin except for _rawcopied_ floppies. LILO sucks,
plain
> and simple, and is about the only complaint about Linux I have.
Show me.
Why does it fail?
Where does it fail?
How does it fail?
The newer LILO's (v21.4.3 and higher) do NOT have the 1024 cyl. limit.
It was not a limit of LILO, but a BIOS limit. Try to boot DOS from beyond
that limit, with no extra bootloader. It will fail miserably.
I'm no LILO developer, but I really love LILO's power.
I've yet to run into a linux I cannot boot with the help of LILO.
To the OP, if you want to convert CHS values to bytes:
Cylinders*Heads*Sectors_per_track*512=bytes
(The maximum is approx. 8GB)
Eric
------------------------------
From: "Eric" <[EMAIL PROTECTED]>
Subject: Re: I know I'm boring. . . but
Date: Mon, 5 Mar 2001 08:46:35 +0100
> root (hd1,0)
> Filesystem type is fat, partition type 0xb
type 0x0b is win95 FAT32
Are you sure this is your win2k partition?
> map (0x81) (0x80)
> map (0x80) (0x81)
Are these needed?
if hd1=hdb, then probably yes, hd1=hda then probably not
(I don't know grub very well)
Eric
------------------------------
From: Lew Pitcher <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: Test if mount was a sucess from shell script?
Date: Sun, 04 Mar 2001 19:36:21 -0500
Ken Williams wrote:
>
> I'm trying to mount a drive before I do something, does anyone know how I can
> test to see if the mount was sucessfull from a bash shell script?
mount will return an exitcode based on whether or not the command
worked.
In bash, this exitcode is stored in the $? variable, and is also
implicitly testable. A value of 0 means success, while a non-zero value
is failure.
You could use code like this...
if mount /dev/somedevice /some/mount/pt ; then
echo The mount worked
else
echo The mount failed
fi
--
Lew Pitcher
Master Codewright and JOAT-in-training
Registered Linux User #112576
------------------------------
From: =?iso-8859-1?Q?Zilla=A9?= <[EMAIL PROTECTED]>
Crossposted-To: aus.computers.linux
Subject: Re: multiboot help
Date: Mon, 05 Mar 2001 03:14:04 -0500
Alex Zaslavsky wrote:
>
> For college I have been given a simple assignment to set up a multi boot
> system running. MS-dos 6.22, windows 98, windows NT server 4.0 and any
> version of linux (i have redhat 5.2 , 7.0 and mandrake 7.2).
Maybe not as simple as you thought, eh? :o) I'm struggling with it my
self, but I believe my problems are more hardware related... so far...
------------------------------
From: Rainer Menzner <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: vfat-Filesystem and UC/LC-conversion
Date: 05 Mar 2001 09:14:40 +0100
Hi,
if I copy files from a ext2-partition to a mounted vfat-partition the
filenames are perfectly preserved under Linux. The problem is that
filenames which (by chance) adhere to the 8.3 naming convention appear
in uppercase only under Windows. The leads to problems because after
burning a CD from such data under Windows these filename remain
uppercase even if the CD is mounted under Linux.
I'm not sure about the actual problem. Is it Windows that converts the
filenames, or does this happen on Linux while copying to the
vfat-partition? I tend to believe to the first alternative because the
filenames appear OK after copying under Linux.
Does anyone know a solution?
Thanks for your opinions,
-Rainer
--
*** ____ ****** . * . ******* Dr.-Ing. Rainer Menzner ********************
( / \ /| /| Ruhr-Universit�t Bochum
/ | / | / | Institut fuer Neuroinformatik
/____/ / |/ | __ D-44780 Bochum, Germany
/ \ / ' | ( / ---------------------------------------------
(/ \_ o (/ | -/- o
********************* /--) ** Tel. +49-234/32-27978 ************************
eMail: [EMAIL PROTECTED]
WWW: http://www.neuroinformatik.ruhr-uni-bochum.de/ini/PEOPLE/rmz/top.html
------------------------------
From: "Eric" <[EMAIL PROTECTED]>
Subject: Re: crc errors at boot
Date: Mon, 5 Mar 2001 09:39:15 +0100
Check your RAM by running the memtest86 program.
Eric
------------------------------
From: [EMAIL PROTECTED] (Soeren Ziehe)
Crossposted-To:
comp.os.linux.security,alt.os.linux,alt.os.linux.mandrake,alt.os.linux.slackware,comp.unix.bsd.freebsd.misc,comp.unix.bsd.openbsd.misc,linux.debian.publicity,linux.redhat.misc
Subject: Re: Something to chew on..
Date: 05 Mar 2001 09:35:00 +0100
Reply-To: [EMAIL PROTECTED]
In article <[EMAIL PROTECTED]> [02 Mar 01]
Luke Vogel <[EMAIL PROTECTED]> wrote:
>> Uptime for Win2k Pro -- three hours.
> Uptime for linux:
> 4:34pm up 82 days, 6:04, 1 user, load average: 0.00, 0.00,
> 0.00
9:01am up 248 days, 16:05, 1 user, load average: 0.17, 0.11, 0.04
And this "lousy" uptime is just the result of a power loss.
Robinton
F'up set to:
comp.os.linux.security where I saw the original posting
this is as good a group as the others where it showed up
--
Wer kriecht kann nicht stolpern.
------------------------------
From: Joris Roefs <[EMAIL PROTECTED]>
Subject: Re: Gurus: How to configure Monitor? -- Newbie
Date: Mon, 5 Mar 2001 10:32:19 +0100
Jawahir Koul wrote:
> How to configure monitor?
>
>
Can you be more specific?
Do you want your monitor configured in X-Windows, or just the console
(change you resolution)...?
What type of monitor/videocard do you have? Which Linux-distro?
- Joris
------------------------------
From: "Eric" <[EMAIL PROTECTED]>
Subject: Re: Odd harddrive problems
Date: Mon, 5 Mar 2001 11:01:21 +0100
> I install BestLinux on a hard drive with one partition of about 4 and a
> half GB.
Then how did you get two?
Or do you mean the size of the HDD is 4.5 GB?
>However, when I ran KDE (that was install with BestLinux) it
> ran very slowly and was similar to what Windows did when out of space or
> memory.
X tends to be slower than the windows GUI.
(It's not intertwined with the OS like in windows)
> So I checked system information. I'm not sure if this is normal
> or not, but system info showed that there were two partition (I guess
> they were) were mounted to / and /home.
It's only normal if you set it up like this.
(There's nothing wrong with this though)
I do mis a swap partition. Do you have a swapfile? Or no swap at all?
> The sizes were 2393 mb and 2293
> mb respectively. The thing that confused me is that it showed that the
> first was 87% full and the second was 94%.
If there is a swap file in these partitions, it would make more sense
> I did do full install on
> BestLinux, but the install was 1.4 GB (estimated) and, as I said before,
> my harddrive was over 4 and a half GB. Also, it said each filesystem was
> of type ext2 (not sure if that matters or not).
what does `mount` provide for info?
and `df`? and `du`
Eric
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to comp.os.linux.setup.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Setup Digest
******************************
