Hi,
On 23-Mar-00 vorlon-kosh wrote:
>> > The card doesn't show on pnpdump and I don't how to trie
I can't help you with that.
>> > new I/O address (and I don't know what are my free I/O addresses).
>> cat /proc/io* could help :-)
the /proc filesystem provides information on you system. ioports give all
he uesd io-addresses for example.
Which shows that there is no ncr card used right now, though the address
you gave the card would be a free (i.e. previously unused) address.
> This is what happers with cat
> /proc/io*
> 0000-001f : dma1
> 0020-003f : pic1
> 0040-005f : timer
> 0060-006f : keyboard
> 0070-007f : rtc
> 0080-008f : dma page reg
> 00a0-00bf : pic2
> 00c0-00df : dma2
> 00f0-00ff : fpu
> 0170-0177 : ide1
> 01f0-01f7 : ide0
> 0220-022f : soundblaster
> 2f80-02ff : serial (auto)
> 0376-0376 : ide1
> 03c0-03df : vga+
> 03f6-03f6 : ide0
> 03f8-03ff : serial (auto)
> 4000-4007 : ide0
> 4008-400f : ide1
>
> what I do now?
Since I don't habe anything isa in my system (besides a soundcard on
which I disabled pnp), I can't get you started with the isapnp.
But I tried to answer you second question above where to get information
on "free" adress ranges for you card.
The way to go would now be to get infos on the card, which irq/io-base
combinations are alowed (some of my networkcard hat jumpers which alwys
changed irq *and* base io simultaniously).
Then try to set the card to a valid combination. The insmod ... irq=255
probably means "don't use irq" ? Then still you would have to tell the
card a iobase it is willing to accept.
Try to get the information to which it is set under winXX (you mentioned
it's working there). Try the same values with Linux. Try a warmboot from
win into Linux, maybe the cardsettings survive. If the card shows up
then, try too figure out how to set the same without winXX (read
/proc/ioports /proc/interrupts etc. again).
The most warm "warmboot " would probably be: end windows by starting in
dos mode and use loadlin to boot linux.
Then you could try to find some more info on that card under Linux.
Try the hardware and support data base on www.suse.com or look at RedHat
or Debian. Also the /usr/src/linux/Documentation could hold some valuable
information to get the card recognised.
[Alan]
> > insmod g_NCR5380 ncr_addr=0x348 ncr_irq=255 ncr_53c400a=1
[vorlon-kosh]
> I already tried this command, but it says:
> device or resource busy (or something like this).
Could this also happen when the module is not loadable by some
kernel-mismatch? That would usually print some other error.
K.-H.
----------------------------------------------------------
E-Mail: Karl-Heinz Herrmann <[EMAIL PROTECTED]>
Date: 24-Mar-00 Time: 11:44:11
----------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
