Quote:>If there is one thing that I have learned, it is that every-
>one's problems are different. I have seen an install failure
>where, after long hours, my best guess is that the triton IDE
>controller was broken on the motherboard. A new motherboard,
>CPU and RAM was obtained and the problem went away.
Doh! In other words: a new system cleared up the problems.
Sounds terribly dramatic, to me! Were my IDE controller "broken" I
hardly think neither DOS nor Windoze would run properly, if at all.
Furthermore, what's the point of buying new CPU and RAM, on top of a
new mobo? And the most obvious question: Does this customer, friend or
associate, for whom you obliged to shell out big bucks for Linux
compatibility, still talk to you?
Quote:>On this motherboard, win3.1 installed fine, linux would not.
>We did <left alt><F2> thru <left alt><F whatever> during the
>install and did not see what I would call good descriptive
>error messages.
Well, I don't think you're supposed to get any descriptions of error
messages in any of those windows...at least, not for the installation
routine. The errors came during installation, in the same window as
the install. But I'm just a newbie: what do I know? (Then again, with
your suggestion to replace entire RAM and CPU along with motherboard,
makes me wonder what *you really know!)
However, the installation statements on screen ALT-F3 and ALT-F4
indicated that all was in order. For the CD-ROM, it stated:
sbpcd-0 [04]: Drive 0 (ID=0): CR-526 (5.00) at 0x230 (type 1)
Quote:>If the CD can be read on another machine running linux,
>it's probably ok. If you can try a different cdrom drive
>on the same machine, that may be interesting.
I don't have a situation where I can try another CD. However, since
Linux was successfully performing the installation of the majority of
packages before aborting...I'd say recognition of the CD-ROM was not a
problem. When I presented my list of error readouts, that did not mean
*all the packages could not be set up...in fact, over 50% of them went
along without a hitch.
Quote:>You didn't
>say if you have a SCSI or IDE cdrom drive. If it's IDE,
>you didn't say if it was on the primary or secondary IDE
>controller or if it is jumpered as a master or slave. Not
>that this information will solve the problem, but it may
>help some (or not).
I have neither type. My CD is a proprietary sound blaster, which is
recognized by Linux...even with "autoprobe".
Quote:>One thing I will emphasize again, even if the machine runs
>MS operating systems, it does not always mean you have good
>hardware.
I see. So Linux only wants the very best! I don't know if Linux
incompatibility is a sign of bad hardware...but perhaps a sign of just
that: incompatibility. My system is very PC-generic...and I have read
the Linux docs regarding this issue. All my components are most likely
agreeable to Linux. The only exception might be my Logitech Page
Scanner. The chipset, video card, Intel CPU, EDO RAM, sound card,
monitor, etc., all are supposed to be recognizable by Linux. I'm sure
this is some excellent hardware, with which Linux can't work.
One of my goals for switching to Linux (in addtion to boycotting M$),
is to cut back on my computer expenses. If, as you imply, Linux can be
a pricey proposition, well then: the little * will just have to
find some other system to mooch off of--not mine!
Quote:>PS: Are you sure that linux mounted the cdrom even? An
><left alt><F something (2 thru 4 or 5) > should give you
>a command prompt where you can look around some. If you
>can find a "df" command somewhere, try to use it. It may
>be mounted in one of the paths you've documented below
>under the "done unmounting filesystems" item, in which
>case you can just use "ls" and "cd" to see if it looks
>like it's mounted.
Alt-F2 put me into the bash# shell. Then I ran "df" to get the
following ("Filesystem" is abbreviated here to "Filesys"):
Filesys 1024-blocks Used Available Capacity Mounted on
/dev/root 1738 1070 578 65% /
/tmp/sbpcd 653372 653372 0 100% /tmp/rhimage
I assume this means that "rhimage" is temporarily mounted to RAM...and
this image is from the CD-ROM, as designated by the device name
"sbpcd" for my Soundblaster CD-ROM.
But I *still don't know what those error messages mean...and it sure
would be nice to find this out, as it may help me troubleshoot.
Troubleshoot? Really...here I am just trying to do this "ezstart"
(coff, coff, hak) installation, and I'm already having to
troubleshoot, instead.
I have since attempted another install...which likewise aborted, after
a pile of error statements...even though the majority of packages (the
ones before Linux aborted) went through without a problem. Here is the
error list, of my most recent installation attempt:
---begin list of errors
RMP install of libtermcap failed: read failed: Input/output
error (5)
RMP install of glibe failed execution of script failed
RMP install of bash failed execution of script failed
RMP install of aout-libs failed execution of script failed
RMP install of ash failed execution of script failed
RMP install of slang failed execution of script failed
RMP install of newt failed: unpacking of archive failed on
file /usr/bin whiptail: -1: Input/output error
RMP install of at failed execution of script failed
RMP install of zlib failed execution of script failed
RMP install of ncurses failed execution of script failed
RMP install of bc failed execution of script failed
RMP install of binutils failed execution of script failed
RMP install of dev failed execution of script failed
RMP install of diffutils failed execution of script failed
RMP install of e2fsprogs failed execution of script failed
RMP install of ed failed execution of script failed
RMP install of emacs failed execution of script failed
RMP install of expect failed execution of script failed
RMP install of faq failed execution of script failed
RMP install of findutils failed execution of script failed
RMP install of gdbm failed execution of script failed
RMP install of gimp-libgimp failed execution of script failed
RMP install of git failed execution of script failed
RMP install of gtk failed execution of script failed
RMP install of gzip failed execution of script failed
RMP install of ImageMagick failed execution of script failed
RMP install of initscripts failed execution of script failed
RMP install of kbd failed execution of script failed
RMP install of kernel failed execution of script failed
RMP install of kernel-modules failed: unpacking of archive
failed on file /lib/modules/20.32/net/3c509.o: -1:
Input/output error
RMP install of kernelcfg failed: read failed: Input/output
error (5)
error - reading header:
Input/output error install exited abonrmally
sending termination signals... done sending kill
signals...
done unmounting filesystems...Hmp/rhimage/mut/home/wnt/usr
/proc /mnt/
you may safely reboot your system.
--end list of errors
Perhaps--like the prodigal son--I should return to the all-embracing
bosom of Windoze95! What a concept! With all these zany installation
errors, just during an installation...well, this does give one pause
to reconsider. Are you sure Bill Gates hasn't put a bug into
Linux...or that Red Hat 5.0 has a M$ spy in its office?
---
My web site kicks (but never*s) butt!
http://www.veryComputer.com/