On Tue, 24 Jun 1997, Rick Hawkins wrote:
> > Try making a 1.3 rescue disk and booting it with the fdomain parameters.
> > If you watch the screen (fast) during boot, you should see whether it got
> > the scsi controller OK or not. If that works, then it's just a matter of
> > configuring the kerne
> -- using template mhl.format --
> Date:Tue, 24 Jun 97 20:54:15 EDT
> To: Rick Hawkins <[EMAIL PROTECTED]>
> cc: debian-user@lists.debian.org
>
> From:Paul Wade <[EMAIL PROTECTED]>
> Subject: Re: more on scsi controllers
>
> X-Sender: [
Try making a 1.3 rescue disk and booting it with the fdomain parameters.
If you watch the screen (fast) during boot, you should see whether it got
the scsi controller OK or not. If that works, then it's just a matter of
configuring the kernel and LILO on your system.
On Tue, 24 Jun 1997, Rick Haw
Rick Hawkins <[EMAIL PROTECTED]> wrote:
>After the hints so far, it's clear that eata 's error messages have to
>do with using the same adresses as the second ide card (which is
>installed).
I'm new to Linux, but I've been working on computers for years, so let
me ask a question that's naive, ye
>
> At the boot: prompt type
>
> linux fdomain=0x230,11
>
> If I'm wrong about the 'linux' correct me. I can't reboot right now to
> verify that.
OK, i sort of seem to be there. I compiled the fdomain module (among
others). The autoprobe doesn't work:
modprobe fdomain=0x140,11
yields no r
Isn't there a "reserve=io_address, length" option you can feed the
kernel to protect against autoprobing? I've had experiences where
another, unrelated driver got to a card first with an autoprobe and
bolloxed everything up. Seems I used a boot line like "linux
reserve=blah,blah aic7xxx=blah,blah
>
> Use a standard kernel, like the rescue disk.
>
> At the boot: prompt type
>
> linux fdomain=0x230,11
>
> If I'm wrong about the 'linux' correct me. I can't reboot right now to
> verify that.
close. capital L. But it still didn't work :( I wonder if the eata
is somehow interfering. I h
Use a standard kernel, like the rescue disk.
At the boot: prompt type
linux fdomain=0x230,11
If I'm wrong about the 'linux' correct me. I can't reboot right now to
verify that.
On Tue, 24 Jun 1997, Rick Hawkins wrote:
> > dir /proc/scsi
>
>
> > cat /proc/scsi/aha152x (in my case) give iopor
> dir /proc/scsi
> cat /proc/scsi/aha152x (in my case) give ioport, irq, and a whole bunch of
> cool techie words.
bash-2.00# dir /proc/scsi/
scsi
bash-2.00# cat /proc/scsi/scsi
Attached devices: none
bash-2.00# dir /proc/scsi/
scsi
bash-2.00# cat /proc/scsi/scsi
Attached devices: none
bash-
The first step is to see a host adaptor.
dir /proc/scsi
cat /proc/scsi/aha152x (in my case) give ioport, irq, and a whole bunch of
cool techie words.
If nothing is there, then we need to help it along a bit.
The LILO argument is:
fdomain=,[,]
Does the card have jumpers? Somebody on this list
> Looking at the kernel source, I would say try for the future domain first.
> It should be supported by a standard Debian kernel as a built-in (not
> modular) driver. Maybe if you're lucky it will autoprobe.
no such luck :(
bash-2.00# mount /dev/scd0 /cdrom/ -t iso9660
mount: the kernel does
Looking at the kernel source, I would say try for the future domain first.
It should be supported by a standard Debian kernel as a built-in (not
modular) driver. Maybe if you're lucky it will autoprobe.
On Tue, 24 Jun 1997, Nathan E Norman wrote:
> On Tue, 24 Jun 1997, Rick Hawkins wrote:
>
> :
On Tue, 24 Jun 1997, Rick Hawkins wrote:
:
:After the hints so far, it's clear that eata 's error messages have to
:do with using the same adresses as the second ide card (which is
:installed). However, those aren't the correct adressess.
:
:I actually have three scsi cards sitting here to cho
13 matches
Mail list logo
