Well, pushing the buttons to turn up and down the brightness have no
effect while I'm in open firmware or booted into netbsd off of the
floppy. However, it occured to me to use the VGA out port on the back to
hookup a monitor and this gave some interesting results. Instead of the
screen being black, it's actually grey (open firmware grey, not "trying
to boot macos" grey). So, right now I'm just checking out -CURRENT and
then I'll compile that kernel and see what happens. At least now we have
some output to work with. 
So, are the buttons not supposed to work in open firmware? I don't know
why, but I was under the impression they were caught and handled by
software. 

Thanks again,
 -- Anthony


On Mon, 2005-02-21 at 09:36 -0500, Chris Tribo wrote:
> If the kernel loaded, you probably need to use the brightness button to 
> bring the backlight back on. The pmu code in 2.0 doesn't handle the 
> brightness control correctly.
> 
> On Feb 21, 2005, at 7:28 AM, Anthony de Almeida Lopes wrote:
> 
> > Okay, I've made some progress. I got it to start booting, but then it
> > flickers for a second and goes black. At first the HD clicks and then
> > nothing.
> >
> > To get this far what i did was, do the firmware patch with SystemDisk,
> > then do "installboot -v -m macppc /dev/rwd0a /bootxx /ofwboot" (these
> > files exist) then I set the load-base and real-base and then used :
> >
> > setenv auto-boot? true
> > setenv boot-device ide0/disk@0:8
> > setenv boot-file netbsd
> > reset-all
> >
> > That got me to the black screen. I considered that maybe the kernel
> > doesn't have the video driver compiled in, but even so, the hd would
> > click a lot more.
> >
> > --Anthony
> >
> >
> > On Sun, 2005-02-20 at 02:40 -0500, Chris Tribo wrote:
> >> Assuming you have the system disk or startup disk nvram patches 
> >> loaded,
> >> adjusted your real base and load base, it should be
> >>
> >> boot ide0/@0:0 for the internal HD or
> >> boot ide1/@0:0,OFWBOOT.XCF;1 for the CDROM
> >>
> >> If you don't see ide0 and ide1 in your devaliases, and a big long 
> >> nvramrc,
> >> the patches are not loaded.
> >>
> >> On Sat, 19 Feb 2005, Anthony de Almeida Lopes wrote:
> >>
> >>> Hi, I'm trying to boot a PowerBook G3 (233mhz, Open Firmware 2.0.1)
> >>> which already has NetBSD installed on it. I just can't figure out the
> >>> right Open Firmware command to do the job. I've tried dozens, but, 
> >>> one
> >>> of the problems is I just don't know what device it's on.
> >>>
> >>> devalias gives:
> >>> ...
> >>> scsi /pci/mac-io/mesh
> >>> sci-int /pci/mac-io/mesh
> >>> ata0 /pci/mac-io/ata0
> >>> ata-int /pci/mac-io/ata0
> >>> ata2 /pci/pccard@13
> >>> ata3 /pci/pccard@13,1
> >>> ata1   /pci/mac-io/media-bay/ata1
> >>> bay-ata1 /pci/mac-io/media-bay/ata1/ata-disk
> >>> atapi1 /pci/mac-io/media-bay/ata1/atapi-disk
> >>> fd /pci/mac-io/media-bay/floppy
> >>> ata4 /pci/mac-io@D/media-bay/ata4
> >>> bay-ata4 /pci/mac-io@D/media-bay/ata4/ata-disk
> >>> atapi4 /pci/mac-io@D/atapi-disk
> >>> fd2 /pci/mac-io@D/media-bay/floppy
> >>> ...
> >>>
> >>> So, i can boot to fd2 (floppy drive in the left bay), by using boot
> >>> fd2:,\OFWBOOT.XCF. And that worked just fine to install everything;
> >>> however, I can't boot to what I installed. I double checked and made
> >>> sure that file system wd0a is mountable and everything seems to be
> >>> there. I copied everything from /usr/mdec/ to it's /.
> >>>
> >>> I thought I did 'installboot' correctly, but maybe that's the 
> >>> problem. I
> >>> did: "installboot -m macppc /dev/rwd0a /tmp/bootxx /tmp/boot." Is 
> >>> this
> >>> even correct? I used absolute pathnames, but should I be doing this
> >>> chrooted into the new install?
> >>>
> >>> I've read the macppc install guide repeatedly and the 'ofwboot' man
> >>> page, but I'm still confused.
> >>>
> >>> Any suggestions? Thank you in advance,
> >>> * Anthony
> >>>
> >>>
> >>
>