On Sun, May 28, 2000 at 03:20:30PM +0200, Henning Loeser wrote:
What I found seems to have been related to not using yaboot. As I have a
'old 7500' with MacOS8.1 I thought BootX would be just fine. But maybe
not. Can I use yaboot on my machine? The WebPages are not very clear on
that part. BenH's site states that yaboot is onbly for 'NewWorld' macs,
but Eric's FAQ states that yaboot is for 'NewWorld' macs, but users of
earlier machines should consider switching if they encounter odd problems
...
yaboot will not work on oldworld macs, you need to use quik instead.
Well I do encounter strange Problems ...
seems typical of bootx lately...
So should I go through the hassel of installing yaboot?
no because it would be a waste of time since it won't work ;-) you
should go to the hassle of installing quik instead. (hint use debian
quik it actually works)
before anyone starts bitching about how quik is so horrible to setup,
let me say this, yaboot would be no different, they are both OF boot
loaders the only difference is yaboot is essentially a second stage
loader only, quik has a first stage loader which eliminates the need
for a bootstrap partition. The problems people have with quik is the
following:
most [oldworld] macs don't have OF video drivers, this makes
interfacing with OF someone annoying.
oldworld macs have `the BrokenFirmware from hell' not even MS has made
anything as broken as this firmware ;-)
both of these problems exist just as well with yaboot as they do with
quik. the only reason yaboot is less painful on newworld is due to
the one-quarter-way usable OF, and the OF video driver.
it might be possible to make yaboot work on an oldworld, but why? all
you would end up with is quik second stage. (which is basically all
yaboot is, quik second stage with bits of silo and other assorted
stuff to work on newworlds)
anyway my point is if you want OF booting on an oldworld you want
quik, not yaboot.
--
Ethan Benson
http://www.alaska.net/~erbenson/
yaboot will not work on oldworld macs, you need to use quik instead.
Ok
quoted
Well I do encounter strange Problems ...
seems typical of bootx lately...
quoted
So should I go through the hassel of installing yaboot?
no because it would be a waste of time since it won't work ;-) you
should go to the hassle of installing quik instead. (hint use debian
quik it actually works)
Well beeing lazy I would only do that if it does promise some progress in
getting the card to work. I'll see what I can find out about quik, but
maybe I have to give it a try to find out ... :-(
Something else seems to be fishy aswell maybe the driver (???) or
whatever. I went ahead and tried a new 2.4.0test1-ac1 kernel and all of
the sudden the driver doesn't even see the drive any more ... :
AEC6260R: IDE controller on PCI bus 00 dev 68
AEC6260R: chipset revision 1
AEC6260R: not 100% native mode: will probe irqs later
AEC6260R: ROM enabled at 0x80810000
AEC6260: reg49h=0x00 ATA-66 Cable Port0
ide0: BM-DMA at 0x0800-0x0807, BIOS settings: hda:pio, hdb:pio
AEC6260: reg49h=0x00 ATA-66 Cable Port1
ide1: BM-DMA at 0x0808-0x080f, BIOS settings: hdc:pio, hdd:pio
hda: ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ, ATA DISK drive
ide0 at 0x840-0x847,0x000 on irq 23
hda: 187353000 sectors (95925 MB) w/11565KiB Cache, CHS=23130/90/90
hda: INVALID GEOMETRY: 90 PHYSICAL HEADS?
and then doesn't even enable the drive. I emailed that to Andre Hedrick to
see whether he knows whats going on.
Henning
--------------------------------------------------------------------------
Henning Loeser Fachbereich Physik
email: henning.loeser@physik.uni-marburg.de AG Oberflaechen
Philipps-Uni Marburg
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
From: Michel Lanners <hidden> Date: 2000-05-28 15:35:11
Hi there,
On 28 May, this message from Henning Loeser echoed through cyberspace:
Something else seems to be fishy aswell maybe the driver (???) or
whatever. I went ahead and tried a new 2.4.0test1-ac1 kernel and all of
the sudden the driver doesn't even see the drive any more ... :
AEC6260R: IDE controller on PCI bus 00 dev 68
AEC6260R: chipset revision 1
AEC6260R: not 100% native mode: will probe irqs later
AEC6260R: ROM enabled at 0x80810000
AEC6260: reg49h=0x00 ATA-66 Cable Port0
ide0: BM-DMA at 0x0800-0x0807, BIOS settings: hda:pio, hdb:pio
AEC6260: reg49h=0x00 ATA-66 Cable Port1
ide1: BM-DMA at 0x0808-0x080f, BIOS settings: hdc:pio, hdd:pio
hda: ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ, ATA DISK drive
ide0 at 0x840-0x847,0x000 on irq 23
^^^^^^^^^^^
You're not using my PCI patches. I'm amazed it finds anything at all on
your card; but anyway, get my latest 2.3.99 patches (2.3.99-pre9, that
is), and apply them. From the above, it seems only part of the
communication of the card with the driver works ok, whereas the rest
reads schrott.
Michel
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art.
23, Rue Paul Henkes | Ask Questions. Make Mistakes.
L-1710 Luxembourg |
email mlan@cpu.lu |
http://www.cpu.lu/~mlan | Learn Always. "
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Hi there,
On 28 May, this message from Henning Loeser echoed through cyberspace:
quoted
Something else seems to be fishy aswell maybe the driver (???) or
whatever. I went ahead and tried a new 2.4.0test1-ac1 kernel and all of
the sudden the driver doesn't even see the drive any more ... :
AEC6260R: IDE controller on PCI bus 00 dev 68
AEC6260R: chipset revision 1
AEC6260R: not 100% native mode: will probe irqs later
AEC6260R: ROM enabled at 0x80810000
AEC6260: reg49h=0x00 ATA-66 Cable Port0
ide0: BM-DMA at 0x0800-0x0807, BIOS settings: hda:pio, hdb:pio
AEC6260: reg49h=0x00 ATA-66 Cable Port1
ide1: BM-DMA at 0x0808-0x080f, BIOS settings: hdc:pio, hdd:pio
hda: ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ, ATA DISK drive
ide0 at 0x840-0x847,0x000 on irq 23
^^^^^^^^^^^
You're not using my PCI patches. I'm amazed it finds anything at all on
your card; but anyway, get my latest 2.3.99 patches (2.3.99-pre9, that
is), and apply them. From the above, it seems only part of the
communication of the card with the driver works ok, whereas the rest
reads schrott.
Well this is with a 2.4.0test1 kernel, I wasn't shure whether your patches
would install on that. I'll try to apply your 2.3.99-pre9 patches onto
that source. But that has to wait untill tomorrow ;-)
Henning
--------------------------------------------------------------------------
Henning Loeser Fachbereich Physik
email: henning.loeser@physik.uni-marburg.de AG Oberflaechen
Philipps-Uni Marburg
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Hi,
ok I applied your 2.3.99-pre9 patches to 2.4.0.test1-ac4 sources and at
least the drive is recognized again. dmesg reads:
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
AEC6260R: IDE controller on PCI bus 00 dev 68
AEC6260R: chipset revision 1
AEC6260R: not 100% native mode: will probe irqs later
AEC6260R: ROM enabled at 0x80810000
AEC6260: reg49h=0x00 ATA-66 Cable Port0
ide0: BM-DMA at 0xf2000800-0xf2000807, BIOS settings: hda:pio, hdb:pio
AEC6260: reg49h=0x00 ATA-66 Cable Port1
ide1: BM-DMA at 0xf2000808-0xf200080f, BIOS settings: hdc:pio, hdd:pio
hda: IBM-DJNA-352030, ATA DISK drive
ide0 at 0xf2000840-0xf2000847,0x000 on irq 23
hda: 39876480 sectors (20417 MB) w/1966KiB Cache, CHS=39560/16/63,
UDMA(66)
but I'm back at the lost interrupt :-(
Partition check:
hda:hda: lost interrupt
hda: lost interrupt
ide_dmaproc: chipset supported ide_dma_lostirq func only: 13
hda: lost interrupt
ide_dmaproc: chipset supported ide_dma_lostirq func only: 13
hda: lost interrupt
hda1ide_dmaproc: chipset supported ide_dma_lostirq func only: 13
hda: lost interrupt
hda2 hda3ide_dmaproc: chipset supported ide_dma_lostirq func only: 13
hda: lost interrupt
hda4 hda5ide_dmaproc: chipset supported ide_dma_lostirq func only: 13
hda: lost interrupt
hda6 hda7ide_dmaproc: chipset supported ide_dma_lostirq func only: 13
hda: lost interrupt
hda8 hda9
I was wondering after Ben's commend if OF sets the bummaster correct for
the card. Or if I should do something like:
pci_read_config_word( pdev, PCI_COMMAND, &cmd );
cmd |= (PCI_COMMAND_MEMORY | PCI_COMMAND_IO);
pci_write_config_word( pdev, PCI_COMMAND, cmd );
How do I verify the busmaster operation is set up cerrectly ?
Henning
--------------------------------------------------------------------------
Henning Loeser Fachbereich Physik
email: henning.loeser@physik.uni-marburg.de AG Oberflaechen
Philipps-Uni Marburg
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/