qemu-ppc
[Top][All Lists]
Advanced

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

Re: Missing dimm-info properties in openbios ?


From: Andrew Randrianasulu
Subject: Re: Missing dimm-info properties in openbios ?
Date: Fri, 21 Mar 2025 18:24:57 +0300

On Fri, Mar 21, 2025 at 6:16 PM Josh Juran <jjuran@gmail.com> wrote:
>
> On Mar 21, 2025, at 10:59 AM, BALATON Zoltan <balaton@eik.bme.hu> wrote:
>
> On Fri, 21 Mar 2025, Andrew Randrianasulu wrote:
>
>
> So far  I found that other ROMs works with patched qemu, too,  and
> curiously OF 2.0.1f allow me to dev into ide0/ide/ide1/ata-int but I
> still can't boot anything or list ISO9660 content on attached cdrom
> image ... But OF 2.4 does not allow me to dev into ide devices!
>
>
> Is there anybody with a real beige G3 Mac
>
>
> I have an OldWorld G3 tower, although it’s not really beige, but light grey. 
> ;-)
>
> who could test how this works on real machine? Just to know what should we 
> see.
>
>
> Can you be specific as to what “this” is?  I once wrote a program that 
> queries the Name Registry; would that be useful here?


Just boot into openFirmware with attached IDE device(s) like disk or
ATAPI cdrom and report that it says  if you try:

dev /
ls
dev ide0 (and ata-int, ide1, ide)

for me on OFW 2.01f it can "dev" there and report OK

on OFW 2.4 it can't
but may be  it  was from too different machine ...

another interesting bit is to see if this instruction piece from
https://cdn.netbsd.org/pub/NetBSD/NetBSD-10.1/macppc/INSTALL.html#can't%20OPEN

----

Note that some of these items are the device itself, and some are a
bus. When you only have the devalias to a bus, you need to specify
which device on that bus you want to use. You can use the Open
Firmware dev and ls commands. For example, here are the devices on the
internal SCSI bus of a PowerMacintosh 7300:


0 > dev scsi-int
0 > ls
FF83C850: /sd@0,0
FF83D480: /st@0,0
 ok

In this case, Open Firmware seems to be saying there are two devices,
both at address zero (one is a SCSI disk `sd@0,0' and the other is a
SCSI tape `st@0,0 ).' Unfortunately, older systems will only list the
naming convention and not the actual devices currently connected, but
that's OK -- we've got more tricks up our sleeve.

If you've got ATA/IDE drives, you have all the device information you
need (since Apple only ever ships drives as ``master'' which is
typically something like ata-disk@0, ATA-Disk@0, atapi-disk, or disk@0
).

You can find out the devices on your SCSI bus with the show-children command:


0 > dev scsi-int
0 > show-children
Target 0
  Unit 0  Disk     IBM     DCAS-32160      S65A
Target 3
  Unit 0  Removable Read Only device    SONY    CD-ROM CDU-8005 1.0j
 ok

Open Firmware calls SCSI IDs ``Target''. The ``Unit'' number is the
Logical Unit Number (LUN). This is almost always zero. Thus, this
PowerMacintosh system has an IBM hard drive (DCAS-32160) at SCSI ID 0,
and a Sony CD-ROM drive (CDU-8005) at SCSI ID 3.

Now, we've got enough information to construct the device name for
Open Firmware. Just stick everything together to describe to Open
Firmware what you want. For example, Open Firmware calls the CD-ROM
drive in this system scsi-int/sd@3.

To determine if a device is bootable, type:


0 > dev scsi-int/sd@3
0 > words
load          write        read          seek        close     open
write-blocks  read-blocks  max-transfer  block-size  dma-sync  dma-map-out
dma-map-in    dma-free     dma-alloc
 ok

If the word ``open'' is present in the list, then the device is almost
certainly bootable.

== quote end ===

this does not work for me, but may be I type it wrong?

SCSI seems to be NOT working on DPPC as of yet, and not in qemu.

So my only hope to see NetBSD boot is ATAPI cdrom image boot, but  I can't ...

dir path also does not work for me.

works



>
> Cheers,
> Josh
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]