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
On Sat, 19 Feb 2000, Jose Gabriel Marcelino wrote:
atapci0: VIA 82C586 ATA33 controller 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
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: VIA 82C586 ATA33 controller port
Doug Rabson wrote:
atapci0: VIA 82C586 ATA33 controller 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
On Sun, 20 Feb 2000, Hellmuth Michaelis wrote:
Doug Rabson wrote:
atapci0: VIA 82C586 ATA33 controller 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!
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 +49
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.
Do
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 disk probes
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
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 you'll be able to
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 that
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
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*:)
Hmm,
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 breath when I
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: VIA 82C586 ATA-33 controller port 0xe000-0xe00f at device 7.1
on
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
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 boot
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
18 matches
Mail list logo