NewWorld "Blue & White" Mac Powerpc install -- problems with firewire and aec62xx driver.
Package: installation-reports
INSTALL REPORT
Debian-installer-version: <Fill in date and from where you got the
image>
Index of /pub/cdimage-testing/daily/powerpc/current
Name Last modified Size
Description
------------------------------------------------------------------------
Parent Directory 22-Sep-2004 00:26 -
MD5SUMS 22-Sep-2004 00:26 1k
sarge-powerpc-businesscard.iso 22-Sep-2004 00:20 153M
>>>>sarge-powerpc-netinst.iso 22-Sep-2004 00:26 310M
------------------------------------------------------------------------
Apache/1.3.31 Server at cdimage.debian.org Port 80
uname -a: <The result of running uname -a on a shell prompt>
Linux bluemac 2.6.8-powerpc #1 Fri Aug 27 18:02:26 CEST 2004
ppc GNU/Linux
Date: <Date and time of the install>
Noon September 22, 2004 US East Coast time
Method: How did you install? What did you boot off?
If network install, from where? Proxied?
Booted netinst CD directly
At Yaboot prompt, specified:
"expert-powerpc video=ofonly"
Not proxied
Machine: <Description of machine (eg, IBM Thinkpad R32)>
Apple PowerMac "Blue and White" G3 - Rev A (before IDE chip was fixed)
Processor:
G3 300 MHz
Memory:
384 Mbyte
Root Device: <IDE? SCSI? Name of device?>
/dev/hdc -- 6.4 GB IDE disk on the Mac motherboard IDE controller
Root Size/partition table: Feel free to paste the full partition
table, with notes on which partitions are mounted where.
# mac-fdisk -l /dev/hdc
/dev/hdc
# type name length
base ( size ) system
/dev/hdc1 Apple_partition_map Apple 63 @
1 ( 31.5k) Partition map
/dev/hdc2 Apple_Driver_ATA Macintosh 54 @
64 ( 27.0k) Unknown
/dev/hdc3 Apple_Driver_ATA Macintosh 74 @
118 ( 37.0k) Unknown
/dev/hdc4 Apple_Driver_IOKit Macintosh 512 @
192 (256.0k) Unknown
/dev/hdc5 Apple_Patches Patch Partition 512 @
704 (256.0k) Unknown
/dev/hdc6 Apple_Bootstrap boot 195313 @
1216 ( 95.4M) NewWorld bootblock
/dev/hdc7 Apple_UNIX_SVR2 swap 976563 @
196529 (476.8M) Linux swap
/dev/hdc8 Apple_UNIX_SVR2 root 11421868 @
1173092 ( 5.4G) Linux native
Block size=512, Number of Blocks=12594960
DeviceType=0x0, DeviceId=0x0
Drivers-
1: @ 64 for 21, type=0x701
2: @ 118 for 34, type=0xf8ff
# mount
/dev/hdc8 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
#
Output of lspci and lspci -n:
# lspci
0000:00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40)
0000:00:0d.0 PCI bridge: Digital Equipment Corporation DECchip
21154 (rev 02)
0000:01:00.0 FireWire (IEEE 1394): Texas Instruments
PCILynx/PCILynx2 IEEE 1394 Link Layer Controller (rev 02)
0000:01:01.0 IDE interface: Silicon Image, Inc. (formerly CMD
Technology Inc) PCI0646 (rev 05)
0000:01:02.0 VGA compatible controller: ATI Technologies Inc 3D
Rage Pro (rev 5c)
0000:01:03.0 SCSI storage controller: Adaptec AHA-7850 (rev 03)
0000:01:04.0 SCSI storage controller: Artop Electronic Corp
ATP865 (rev 06)
0000:01:05.0 ff00: Apple Computer Inc. Paddington Mac I/O
0000:01:06.0 USB Controller: OPTi Inc. 82C861 (rev 10)
# lspci -n
0000:00:00.0 0600: 1057:0002 (rev 40)
0000:00:0d.0 0604: 1011:0026 (rev 02)
0000:01:00.0 0c00: 104c:8000 (rev 02)
0000:01:01.0 0101: 1095:0646 (rev 05)
0000:01:02.0 0300: 1002:4749 (rev 5c)
0000:01:03.0 0100: 9004:5078 (rev 03)
0000:01:04.0 0100: 1191:0009 (rev 06)
0000:01:05.0 ff00: 106b:0017
0000:01:06.0 0c03: 1045:c861 (rev 10)
#
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked: [o]
Configure network HW: [o]
Config network: [o]
Detect CD: [o]
Load installer modules: [o]
Detect hard drives: [e]
Partition hard drives: [e]
Create file systems: [o]
Mount partitions: [o]
Install base system: [o]
Install boot loader: [o]
Reboot: [o]
Comments/Problems:
<Description of the install, in prose, and any thoughts, comments
and ideas you had during the initial install.>
Note 1:
Booting without "video=ofonly" resulted in a scrambled screen.
Note 2:
Had to manually specify "bmac" ethernet interface.
Note 3:
This machine has two IDE disk drives. One (6.4 GB) is
connected to the on-board IDE controller. The other one (180 GB)
is connected to a SIIG "Ultra ATA 133/100 PRO for Mac" IDE
interface PCI card installed. This card seems to require the
aec62xx driver, but that driver seems to be broken. At least, when
that driver is installed, I get fatal errors in the discover
hardware section and the partitioner, and I am not able to get
further. However, when I refuse to load that driver, I get long
delays in the partitioner while it's scanning all disks looking for
partitions but I *was* finally able to get the partioner to
recognize the 6.4 GB disk and allow me to partition it. Of course,
without the aec62xx driver, the 180 GB disk was not recognized, and
the partitioner did not see it.
Note 3:
After the reboot, it insisted on installing the aec62xx driver
anyway -- even though it's not listed in /etc/modules. I get
messages on the console during the boot process saying things like:
Sep 23 01:47:06 localhost kernel: hde:
dma_timer_expiry: dma status == 0x24
Sep 23 01:47:16 localhost kernel: AEC62XX time out
<4>hde: lost interrupt
Sep 23 01:47:36 localhost kernel: hde:
dma_timer_expiry: dma status == 0x24
Sep 23 01:47:46 localhost kernel: AEC62XX time out
<4>hde: lost interrupt
Sep 23 01:48:06 localhost kernel: hde:
dma_timer_expiry: dma status == 0x24
Sep 23 01:48:16 localhost kernel: AEC62XX time out
<4>hde: lost interrupt
Eventually all the time-outs expire and things start up OK.
Any references to /dev/hde hang, however. I suspect that the
aec62xx driver is attempting to use a DMA mode that is too fast for
the poor little Blue and White to keep up with. Is there some way
to set a parameter for this driver that will give it a maximum
allowable speed, or something? I'd like to be able to access my
180 GB disk from Linux!
Note 4:
There seems to be something strange going on involving the
on-board FireWire chip. See the /var/log/messages file. I've
heard it said that the RevA Blue and White motherboards used a
pre-standard firewire chip that is not properly handled by the
ohci1394 driver.
Possibly relevant excerpt from the log file:
Sep 23 01:59:02 localhost kernel: ieee1394: SelfIDs failed
monotony check with 22/0
Sep 23 01:59:02 localhost kernel: ieee1394: Error in SelfID
stage, resetting
Sep 23 01:59:02 localhost kernel: pcilynx0: resetting bus (long
bus reset) on request
Sep 23 01:59:02 localhost kernel: pcilynx0: bus reset interrupt
Sep 23 01:59:02 localhost kernel: pcilynx0: SelfID process
finished (phyid 0, root)
Sep 23 01:59:02 localhost kernel: pcilynx0: SelfID packet
0x568c7f80 rcvd
Sep 23 01:59:02 localhost kernel: ieee1394: SelfIDs failed
monotony check with 22/0
Sep 23 01:59:02 localhost kernel: ieee1394: Stopping
out-of-control reset loop
Sep 23 01:59:02 localhost kernel: ieee1394: Warning - topology
map and speed map will not be valid
Sep 23 01:59:02 localhost kernel: pcilynx0: invalid transaction code
Sep 23 01:59:02 localhost kernel: ieee1394: got invalid ack 254
from node 65535 (tcode 4)
Sep 23 01:59:02 localhost kernel: ieee1394: Current remote IRM
is not 1394a-2000 compliant, resetting...
Sep 23 01:59:02 localhost kernel: ieee1394: Stopping reset loop
for IRM sanity
Sep 23 01:59:02 localhost kernel: usbcore: registered new
driver usbfs
Sep 23 01:59:02 localhost kernel: usbcore: registered new driver hub
Sep 23 01:59:02 localhost kernel: ohci_hcd: 2004 Feb 02 USB 1.1
'Open' Host Controller (OHCI) Driver (PCI)
Sep 23 01:59:02 localhost kernel: ohci_hcd: block sizes: ed 64 td 64
Sep 23 01:59:02 localhost kernel: ohci_hcd 0000:01:06.0: OPTi
Inc. 82C861
Sep 23 01:59:02 localhost kernel: ohci_hcd 0000:01:06.0: irq
28, pci mem d5349000
Sep 23 01:59:02 localhost kernel: ohci_hcd 0000:01:06.0: new
USB bus registered, assigned bus number 1
Sep 23 01:59:02 localhost kernel: ohci_hcd 0000:01:06.0:
WARNING: OPTi workarounds unavailable
Log files (a snapshot of the full contents of /var/log) are available at
http://www.rcthomas.org/~rbthomas/logfiles/20040922/
Install logs and other status info is available in
/var/log/debian-installer/.
Once you have filled out this report, mail it to submit@bugs.debian.org.
Reply to: