Maybe this is a silly suggestion, but could someone with a card like
that boot it in a Windows environment and tell us what that hardware
manager tells us about hardware requirements the card would have if it
is configured for the '0x160' address (whatever that configuration is
on the card I don'
Andrew Gordon wrote:
> On Sun, 20 Feb 2000, Hellmuth Michaelis wrote:
> >
> > A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC
> > chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b,
> > the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73.
>
> But i
> But in the case of the teles16.3, it does _not_ use offsets 0x00-0x3b in
> the HSCX or ISAC: the ASIC on the card has 'folded' the address space so
> that the fifo appears at an address 3 bytes after the last register (0x3e
> with the current scheme - see tels0163_read_fifo()).
Ah, then the dri
On Sun, 20 Feb 2000, Hellmuth Michaelis wrote:
>
> A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC
> chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b,
> the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73.
But in the case of the teles16.3, it does
> Depends. If the drivers allocation is coherent with the vendors description
> in the PnP configuration data, it's a newbus error (it shouldn't try to
> allocate the card there in the first place). If the PnP info differs from
> the drivers view of the card, it's either the vendors fault for pro
>From the keyboard of Martin Husemann:
> > In case there is is already an IDE controller allocated at 0x170 and a
> > Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so.
>
> This is a PnP card, right?
No.
hellmuth
--
Hellmuth MichaelisTel
> In case there is is already an IDE controller allocated at 0x170 and a
> Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so.
This is a PnP card, right? So what does the PnP info say about needed
memory ranges?
> So where is the bug ?
Depends. If the drivers allocation is co
Brian Somers wrote:
> > So you are saying that what we really have here is a simple i/o conflict
> > and possibly the ISDN card can be reconfigured to use a non-conflicting
> > address? If so, then everything is working correctly and the resource
> > manager has pointed a possible hardware proble
> > > > atapci0: port 0xe000-0xe00f at device 7.1 on
> > > > pci0
> > > > ata0: at 0x1f0 irq 14 on atapci0
> > > > ata1: at 0x170 irq 15 on atapci0
> > > > ...
> > > > isic0: Error allocating io at 0x160 for Teles S0/16.3!
> > > >
> > > > While I was able to use the Teles again by changing it's
> > So you are saying that what we really have here is a simple i/o conflict
> > and possibly the ISDN card can be reconfigured to use a non-conflicting
> > address? If so, then everything is working correctly and the resource
> > manager has pointed a possible hardware problem :-).
>
> So it wo
> On Sun, 20 Feb 2000, Hellmuth Michaelis wrote:
>
> > Doug Rabson wrote:
> >
> > > > atapci0: port 0xe000-0xe00f at device 7.1 on
> > > > pci0
> > > > ata0: at 0x1f0 irq 14 on atapci0
> > > > ata1: at 0x170 irq 15 on atapci0
> > > > ...
> > > > isic0: Error allocating io at 0x160 for Teles S0/
On Sun, 20 Feb 2000, Hellmuth Michaelis wrote:
> Doug Rabson wrote:
>
> > > atapci0: port 0xe000-0xe00f at device 7.1 on
> > > pci0
> > > ata0: at 0x1f0 irq 14 on atapci0
> > > ata1: at 0x170 irq 15 on atapci0
> > > ...
> > > isic0: Error allocating io at 0x160 for Teles S0/16.3!
> > >
> > > W
Doug Rabson wrote:
> > atapci0: port 0xe000-0xe00f at device 7.1 on
> > pci0
> > ata0: at 0x1f0 irq 14 on atapci0
> > ata1: at 0x170 irq 15 on atapci0
> > ...
> > isic0: Error allocating io at 0x160 for Teles S0/16.3!
> >
> > While I was able to use the Teles again by changing it's default IO p
Jose Gabriel Marcelino wrote:
> This obviously conflicts with the secondary IDE controller which lies at
> 0x170, however this has not been a problem till this day and no driver
> complained about this. Now, with the newer kernel I get this:
>
> atapci0: port 0xe000-0xe00f at device 7.1 on
> pc
On Sat, 19 Feb 2000, Jose Gabriel Marcelino wrote:
> atapci0: port 0xe000-0xe00f at device 7.1 on
> pci0
> ata0: at 0x1f0 irq 14 on atapci0
> ata1: at 0x170 irq 15 on atapci0
> ...
> isic0: Error allocating io at 0x160 for Teles S0/16.3!
>
> While I was able to use the Teles again by changing i
Hi again,
After remaking the loader (unnecessary since it's still broken), I've
removed my KLDs from loader.conf (I was loading a splash screen) and it
now boots as Bryan noticed.
However it seems another problem showed up, and I'm not sure where the
problem is.
I have a Teles ISDN card on thi
It seems Bryan Liesner wrote:
> On Sat, 19 Feb 2000, Soren Schmidt wrote:
>
> >Have you rebuild your modules lately ??
> >
> >-Søren
> >
> Yes. My world is current as of a few hours ago. I did a make world
> right after finding out about the loader problem to rule that
> possibility out. The
On Sat, 19 Feb 2000, Soren Schmidt wrote:
>Have you rebuild your modules lately ??
>
>-Søren
>
Yes. My world is current as of a few hours ago. I did a make world
right after finding out about the loader problem to rule that
possibility out. The disk probes still fail when loading today's
mo
It seems Bryan Liesner wrote:
> >Do you use KLMs?
>
> Yes, I do! I was loading a screen saver with the boot loader. And
> now I see I am wrong about rebuilding the loader! When I had success
> loading the kernel directly, I moved loading the screensaver into
> rc.conf instead. Then I thought th
On Sat, 19 Feb 2000, Philipp Mergenthaler wrote:
>On Sat, Feb 19, 2000 at 10:39:42AM -0500, Bryan Liesner wrote:
>> Jose, the problem seems to be resolved by rebuilding the boot
>> loader. Or bypass the loader altogether.
>>
>> cd /usr/src/sys/boot
>> make obj
>> make all install
>>
>> and yo
On Sat, Feb 19, 2000 at 10:39:42AM -0500, Bryan Liesner wrote:
> Jose, the problem seems to be resolved by rebuilding the boot
> loader. Or bypass the loader altogether.
>
> cd /usr/src/sys/boot
> make obj
> make all install
>
> and you'll be able to boot the kernel with the latest ata stuff.
On Sat, 19 Feb 2000, Jose Gabriel Marcelino wrote:
>
>hi Soren,
>
>The latest ata commits left me unbootable too, the patch you provided
>below didn't help this too. I have a very different configuration from
>Bryan's (much simpler too):
>
Jose, the problem seems to be resolved by rebuilding the
It seems Jose Gabriel Marcelino wrote:
Well, rebuild the loader, that helped Bryan, apparently it has
nothing to do with the ata driver
> The latest ata commits left me unbootable too, the patch you provided
> below didn't help this too. I have a very different configuration from
> Bryan's
hi Soren,
The latest ata commits left me unbootable too, the patch you provided
below didn't help this too. I have a very different configuration from
Bryan's (much simpler too):
- DFI K6XV3+ mb with VIA MVP3 chipset
ata-pci0: port 0xe000-0xe00f at device 7.1
on pci0
ata0 at 0x01f0 irq 14 on
It seems Bryan Liesner wrote:
> On Sat, 19 Feb 2000, Soren Schmidt wrote:
>
> >It seems Bryan Liesner wrote:
> >>
> >> The latest ata commits left my system completely unbootable. No disks
> >> were probed.
> >
> >He, you always seem to be lucky when I change something :)
>
> I always hold my
On Sat, 19 Feb 2000, Soren Schmidt wrote:
>It seems Bryan Liesner wrote:
>>
>> The latest ata commits left my system completely unbootable. No disks
>> were probed.
>
>He, you always seem to be lucky when I change something :)
I always hold my breath when I cvsup and see changes to ata*:)
It seems Bryan Liesner wrote:
>
> The latest ata commits left my system completely unbootable. No disks
> were probed.
He, you always seem to be lucky when I change something :)
> I have on the motherboard's Alladin controller:
> HP 4x4x24 CD burner as master primary channel
> 40x CD as slave
The latest ata commits left my system completely unbootable. No disks
were probed.
I have on the motherboard's Alladin controller:
HP 4x4x24 CD burner as master primary channel
40x CD as slave primary channel
HP Colorado 8 Gig ATAPI tape as master secondary channel
On a Promise Ultra66:
WDC AC
28 matches
Mail list logo
