Date: Mon, 6 Sep 1999 10:56:19 +0200 From: Martin Kahlert <martin.kahlert@mchp.siemens.de> Message-ID: <19990906105618.A827@keksy.mchp.siemens.de> Subject: Re: [suse-axp] 2 Problems with the kernel
Quoting Stefan Reinauer (stepan@suse.de):
> On Mon, 6 Sep 1999, Martin Kahlert wrote:
>
> > Hi,
> > yesterday i installed SuSE-6.1-AXP on my Ruffian board.
> > Nearly everything went fine, but i have 2 problems:
> >
> > I wanted to upgrade from the 2.2.9-Suse kernel to the recent
> > 2.2.12 (which is a bit friendlier to Solaris 2.7....)
> > But it couldn't boot. I compiled with the NCR53C7/8xx driver
> > 2.2.9 recognizes my NCR53C875 onboard controller any problems)
> > but with 2.2.12 i get a SCSI: 0 hosts message at boot time,
> > which produces a slight problem when mounting my root partition later on.
>
> Try thy SYM53C8xx driver. This is the new driver for "newer"
> NCR/Symbios SCSI chipsets (>=825 I think) They have been split to be able
> to specialize on the newer chips' features.
Thanks, i'll try that as soon as i am at home again.
> > i have a iomega zip drive (the older 100MB version plugged into the
> > parallel port). I used to do modprobe ppa
> > and mount /dev/sdb1 /zip with my 2.0.38 kernel. The modprobe
> > command seems to work (in the logfile it tells me, it found the drive)
> > but the mount command says /dev/sdb1 is not a valid block device
> > or something like that. fdisk -l /dev/sdb doesn't work either.
>
> What does it tell? Are you sure there is a partition table on the zip
> medium? Does a dd if=/dev/sdb of=/dev/null "work" ?
As i said: not a valid block device.
> > Has anything changed since my 2.0.* days in the naming of the
> > parport devices? (i tried fdisk -l /dev/sd[b-z], too).
>
> Ah.. you might have to explicitly load the "parport" and "parport_pc"
> modules before (Or tell modprobe/kmod to load it automatically when
> loading the ppa driver)
Of course i did a modprobe ppa, which should do the trick.
In the logfile are lines telling me that the zipdrive was found.
Thanks for your fast reply,
Martin.
-- Your mouse has moved. Windows must be restarted for the change to take effect. Reboot now?
This archive was generated by hypermail 2.1.0 : Mon Jun 04 2001 - 04:17:20 PDT