Subject: Re: obio attachment and Macs w/ two or more I/O controllers
To: Tim Kelly <hockey@dialectronics.com>
From: Chris Tribo <ctribo@college.dtcc.edu>
List: port-macppc
Date: 11/16/2004 01:18:53
I added a dmesg to http://nycbug.org/dmesgd for the PDQ and my beige g3.

I'd also like to note that GENERIC did not find the root device on wd0a by
itself. I've had to compile kernels with it hardcoded in.

The backlight dimming and not coming up to full brightness is annoying
too.


NetBSD 2.0_RC5 (GENERIC) #0: Sat Nov 13 08:55:20 EST 2004

tinderbox@beastie:/data1/tinderbox/release-x11/netbsd-2-0/obj/sys/arch/m
acppc/compile/GENERIC
total memory = 256 MB
avail memory = 241 MB
mainbus0 (root)
cpu0 at mainbus0: 750 (Revision 3.2), ID 0 (primary)
cpu0: HID0 8290c0a4<EMCP,ECLK,DOZE,DPM,ICE,DCE,SGE,BTIC,BHT>
cpu0: 500.00 MHz, no-parity 1MB WB L2 cache (PB SRAM) at 2:1 ratio
grackle0 at mainbus0
pci0 at grackle0 bus 0
pci0: i/o space, memory space enabled
pchb0 at pci0 dev 0 function 0
pchb0: Motorola MPC106 "Grackle" Host Bridge (rev. 0x40)
obio0 at pci0 dev 13 function 0: addr 0xf3000000
mesh0 at obio0 offset 0x10000 irq 12: 50MHz, SCSI ID 7
scsibus0 at mesh0: 8 targets, 8 luns per target
zsc0 at obio0 offset 0x13000: irq 15,16
zstty0 at zsc0 channel 0
zstty1 at zsc0 channel 1
bm0 at obio0 offset 0x11000 irq 42,33: address xx:xx:xx:xx:xx:xx
davbus at obio0 offset 0x14000 not configured
mediabay0 at obio0 offset 0x34 irq 29 level-triggered
wdc0 at mediabay0 offset 0x21000 irq 14
atabus0 at wdc0 channel 0
wdc1 at obio0 offset 0x20000 irq 13: DMA transfer
atabus1 at wdc1 channel 0
adb0 at obio0 offset 0x16000 irq 18: 3 targets
aed0 at adb0 addr 0: ADB Event device
akbd0 at adb0 addr 2: PowerBook G3 keyboard
wskbd0 at akbd0: console keyboard
ams0 at adb0 addr 3: EMP trackpad <tpad> 2-button, 400 dpi
wsmouse0 at ams0 mux 0
abtn0 at adb0 addr 7: buttons
apm0 at adb0: battery flags 0x4, 71% charged
Apple Computer MAC-IO I/O Controller (Paddington) (undefined subclass
0x00) at p
ci0 dev 16 function 0 not configured
ofb0 at pci0 dev 17 function 0: ATI Technologies 3D Rage LT Pro
ofb0: 1024 x 768, 8bpp
wsdisplay0 at ofb0 kbdmux 1: console (std, vt100 emulation), using wskbd0
wsmux1: connecting to wsdisplay0
cbb0 at pci0 dev 19 function 0: Texas Instruments PCI1131 PCI-CardBus
Bridge (re
v. 0x01)
cbb1 at pci0 dev 19 function 1: Texas Instruments PCI1131 PCI-CardBus
Bridge (re
v. 0x01)
cbb0: interrupting at irq 22
cbb0: secondary bus number uninitialized; try PCIBIOS_BUS_FIXUP
cardslot0 at cbb0 slot 0 flags 0
pcmcia0 at cardslot0
cbb1: interrupting at irq 23
cbb1: secondary bus number uninitialized; try PCIBIOS_BUS_FIXUP
cardslot1 at cbb1 slot 1 flags 0
pcmcia1 at cardslot1
scsibus0: waiting 2 seconds for devices to settle...
com0 at pcmcia0 function 0: serial device
com0: ns16550a, working fifo
atapibus0 at atabus0: 2 targets
cd0 at atapibus0 drive 0: <MATSHITA CR-174, , A011> cdrom removable
cd0: drive supports PIO mode 4, DMA mode 2
cd0(wdc0:0:0): using PIO mode 4
wd0 at atabus1 drive 0: <IBM-DARA-206000>
wd0: drive supports 16-sector PIO transfers, LBA addressing
wd0: 5729 MB, 12416 cyl, 15 head, 63 sec, 512 bytes/sect x 11733120
sectors
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4 (Ultra/66)
wd0(wdc1:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
boot device: <unknown>
root device: wd0a
dump device (default wd0b): wd0b
file system (default generic): ffs
root on wd0a dumps on wd0b
init path (default /sbin/init):
init: trying /sbin/init