[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Installation Problems..please help..it's URGENT!



Kevin,

It is also possible that HP provides drivers that allow the IRQ to be
shared. This has been theoretically possible for a long time (ie. the
defaults for Com1/3 and COM 2/4) but requires driver writers to co-operate.
If they come from the same source, it could be done. This also would
explain it working in Win95/NT and not in Linux.

----------
> From: Kevin D. Colby <kevin marcal com>
> To: redhat-install-list redhat com
> Subject: Re: Installation Problems..please help..it's URGENT!
> Date: Sunday, November 30, 1997 5:20 PM
> 
> Sorry, but I've been away for Thansgiving...
> 
> >>>>What do you have on IRQ 15?  Can you move the second SCSI there?
> >>>Nope, both SCSI "cards" (they are onboard) automatically assigns IRQ's
> >>HP says there is _no_way_ to change the IRQs of the SCSI
controllers?!?!?
> >>You have _got_ to be joking...
> >nope
> 
> My opinion of HP just dropped to a new record low.
> 
> >>I can tell you what the problem is...
> >>You can't have two controllers on the same IRQ, that's what.
> >>Right now you have the second SCSI controller and the Net card both
> >>on IRQ 11.  Won't fly.  Not now, not ever.  Someone's got to move.
> >>
> >>This would be a problem even under NT.  What does HP say again?
> >>Tell them you have a network card on IRQ 11 and the secondary SCSI
> >>controller is conflicting with it.  Ask them how you can change the
SCSI
> >>controller's IRQ.  I'm sure it can be done.  No system designer would
> >>be _that_ stupid as to not let you change it at all.
> >
> >well..this is the crux of the problem.. in windows 95 & NT it works
Okay..
> >It's ONLY under Linux that I have this problem..arrrrgh!
> 
> Yes, that is understandable.  I presume HP provided drivers for NT
> and 95.  These drivers could sense that there is a conflict and change
> the IRQ on the fly to resolve it.  Under Linux (or any *nix that HP
> doesn't specifically provide a driver for) what they are set to is
> what you get.
> 
> If you really can't move the SCSI controllers' IRQs, then you
> _must_ change the network card's IRQ.  I'm 99% sure that
> this can be done, since any company making cards that wouldn't
> would go out of business FAST.
> 
> Have you contacted the network card's manufacturer?
> The card is likely PnP and this needs to be disabled.
> You want to set the IRQ manually from any OS you
> can using some utility provided by the card's manufacturer,
> or _maybe_ by setting jumpers on the card, though few
> cards are made this way anymore.
> 
> Pay no attention to what Windows thinks the IRQ is,
> and do not attempt to change the cards IRQ through
> Windows utilities.  These would only affect Windows,
> and wouldn't do squat for Linux.
> 
> The manufacturer's utility should let you "flash"
> the card's BIOS with new information on it's IRQ.
> Ask around there for something like this.  It probably
> shipped on a floppy with the card.
> 
>         - Kevin Colby
>           kevin marcal com
> 
> 
> -- 
>   PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST
ARCHIVES!
> http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips
/mailing-lists
>          To unsubscribe: mail redhat-install-list-request redhat com
>                      with "unsubscribe" as the Subject.
> 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]