During the initial install from the boot floppies there was never an option to
choose a laptop installation. I did see the PCMCIA configuration dialog and
disabled the PCMCIA item on that dialog, but still ran into the same errors as
when I did not disable PCMCIA in that dialog.
Also, the CDs I
Adam C Powell IV wrote:
> > Starting internet superserver: inetd.
> > /bin/sh: /sbin/termwrap: No such file or directory
> > /bin/sh: exec: /sbin/termwrap: cannot execute: No such file or directory
>
> termwrap? Never seen it before. In fact, no file with "termwrap" anywhere
> in it appears in
Ted Swinyar wrote:
> Thank you to everyone who responded to my initial question about getting
> Debian going on the S900.
>
> I've gotten BootX going and pointing to sdb4 where I've installed the /
> partition in the initial configuration. On first boot into Debian I get the
> following error m
Yay! Booting into single-user mode on the S900 and then running the installer
using the commands as found in the inittab file. Once in the installer via
single-user mode there was a dialog box that asked me if I wanted to remove the
PCMCIA stuff. I was able to finish successfully installing the
Hello Andrew,
Yeah, I've done about 5 or 6 complete reinstalls on two different boxes with 3
different drives. The system boots into the linux kernel and the various
daemons and services begin to load. It stalls before any prompts come up so I
haven't gotten a chance to poke around at all. What
Does the system run at all? Can you log in and see what
init ID 1 is, and possibly shut it off? Read the man page
for inittab if you need to. The other option is to boot the
machine in single user mode, and try to fix it that way
(again, look in inittab and figure out what's going on).
There ma
Nope. Replacing the drive seems to have done away with the SCSI errors I was
having problems with.
--Ted
>>> Bruce McIntyre <[EMAIL PROTECTED]> - 1/30/01 2:16 AM >>>
Before the errors, did you get any warnings, or go into fsck ?
At 1:55 AM -0800 30/1/01, Ted Swinyar wrote:
>I worked on the S90
Before the errors, did you get any warnings, or go into fsck ?
At 1:55 AM -0800 30/1/01, Ted Swinyar wrote:
I worked on the S900 for a couple hours more today. Ditched the old
hard drive that was spewing SCSI errors and reinstalled OS9/BootX
from scratch on the "new" drive. On reinstalling deb
I worked on the S900 for a couple hours more today. Ditched the old hard drive
that was spewing SCSI errors and reinstalled OS9/BootX from scratch on the
"new" drive. On reinstalling debian I noticed that there was an optional item
to configure the PCMCIA interface that I hadn't noticed previous
Are you still getting the SCSI errors on startup, or was that a
one-off result of hard booting because of the init respawning? I have
been also getting the init id 1 respawning too fast on my 7300. I'm
thinking that the disk 'repair' chucks important stuff into
lost+found, although you should
It sounds like you failed to say 'Y' when the install asked
you if you wanted to get rid of the pcmcia packages. So run
dselect or dpkg and purge those packages. You surely don't
need them on a 7200.
I haven't a clue what termwrap is. I don't have it on my
x86 system, and I won't have access to
Just to verify that it's not my S900 that is the problem I pulled an old
7200/120 out of the closet and booted it up with a different hard drive. On
initial boot (using BootX) I get the exact same errors with the 7200 as I've
been getting with the S900--errors included below with my original mes
> > scsi1: MEDIUM ERROR on channel 0, id 3, lun 0, CDB: Read (10) 00 00 67 1d
> > 07 00 00 80 00
> > Info fld=0x671d24, Current sd08:14: sense key Medium Error
> > Additional sense indicates Unrecovered read error
> > scsidisk I/O error: dev 08:14, sector 6033200
> >
> > this is repeated several t
Thanks Steve, I ran e2fsck /dev/sdb4 and told it "yes" on all the errors and on
reboot everything worked as with the initial install. Unfortunately, now i'm
back where I started with the following errors on startup:
Starting PCMCIA services: modules/lib/modules/2.2.17/pcmcia/i82365.o:
init_modu
On Sun, Jan 28, 2001 at 12:38:56AM -0800, Ted Swinyar wrote:
> scsi1: MEDIUM ERROR on channel 0, id 3, lun 0, CDB: Read (10) 00 00 67 1d 07
> 00 00 80 00
> Info fld=0x671d24, Current sd08:14: sense key Medium Error
> Additional sense indicates Unrecovered read error
> scsidisk I/O error: dev 08:14
Quick follow-up to my previous message. On reboot after the initial boot
failure (see previous message below) I get the error message that "/dev/sdb4
was not cleanly unmounted, check forced."
At this point, I get a huge number of SCSI errors, as follows:
scsi1: MEDIUM ERROR on channel 0, id 3,
Thank you to everyone who responded to my initial question about getting Debian
going on the S900.
I've gotten BootX going and pointing to sdb4 where I've installed the /
partition in the initial configuration. On first boot into Debian I get the
following error message:
Starting PCMCIA servic
On Wed, Jan 17, 2001 at 02:36:57PM -0800, Ted Swinyar wrote:
> Hello,
> I am interested in getting Debian PPC going on an old Umax S900
> I've got sitting around. I got the CheapBytes CDs of Debian PPC and
> was able to successfully boot into the initial installer and was
> able to proceed throug
Hello,
I am interested in getting Debian PPC going on an old Umax S900 I've got
sitting around. I got the CheapBytes CDs of Debian PPC and was able to
successfully boot into the initial installer and was able to proceed through
the installation until the part of the install process where I was
19 matches
Mail list logo
