XPost: linux.debian.maint.boot
From: [email protected]

Package: installation-reports

Debian-installer-version: Sarge RC1 20040806 netinstall CD (powerpc)
from http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/powerpc/rc1/sarge-powerpc-netinst.iso
uname -a: N/A, didn't get that far
Date: 20040810, 11pm CST
Method: Burned the iso, booted from CDROM

Machine: Apple Blue & White G3
Processor: 400 MHz
Memory: 384MB (1x128MB + 1x256MB)
Root Device: System contains 2 SCSI drives: /dev/sda is an IBM
DDRS-39130D (9GB SCSI); /dev/sdb is a Seagate ST39140W (9GB SCSI).
Both are connected to the Apple-shipped Adaptec SCSI card. I chose
the IBM as the root device.
Root Size/partition table:
SCSI2 (0,0,0) (sda) - 9.1GB IBM DDRS-39130D
#1 32.2kB Apple
#2 28.6kB Macintosh
#3 28.6kB Macintosh
#4 28.6kB Macintosh
#5 28.6kB Macintosh
#6 262.1kB Macintosh
#7 262.1kB Macintosh
#8 262.1kB Patch Partit
#9 1.0MB boot boot
#10 3.2GB ext3 ydl
#11 2.1GB ext3 home
#12 402.6MB swap swap
#13 2.0MB hfs+ ignore
#14 3.3GB ext3 debian
Partitions #1-8 are standard Mac system partitions. #9 is a shared
boot partition for yaboot. #10 is the YellowDog root partition. #11
is the shared (between YDL and Debian) home partition. #12 is the
shared (between YDL and Debian) swap partition. #13 is some random
partition I made for some reason that I don't recall. #14 is the
Debian root partition.


Output of lspci from my YellowDog install:
00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40)
00:0d.0 PCI bridge: Digital Equipment Corporation DECchip 21154 (rev 02) 00:10.0 VGA compatible controller: ATI Technologies Inc Rage 128 RE/SG
01:00.0 FireWire (IEEE 1394): Texas Instruments PCILynx/PCILynx2 IEEE
1394 Link Layer Controller (rev 02)
01:01.0 IDE interface: CMD Technology Inc PCI0646 (rev 05)
01:02.0 PCI bridge: PicoPower Technology PT86C525 [Nile-II] PCI-to-PCI
Bridge (rev 01)
01:03.0 SCSI storage controller: Adaptec AHA-7850 (rev 03)
01:04.0 SCSI storage controller: Adaptec AHA-2940U2/U2W (rev 01)
01:05.0 Class ff00: Apple Computer Inc. Paddington Mac I/O
01:06.0 USB Controller: OPTi Inc. 82C861 (rev 10)
02:08.0 SCSI storage controller: Advanced System Products, Inc
ABP940-U / ABP960-U (rev 03)
02:09.0 Multimedia video controller: Zoran Corporation ZR36057PQC
Video cutting chipset (rev 02)

Output of lspci -n from my YellowDog install:
00:00.0 Class 0600: 1057:0002 (rev 40)
00:0d.0 Class 0604: 1011:0026 (rev 02)
00:10.0 Class 0300: 1002:5245
01:00.0 Class 0c00: 104c:8000 (rev 02)
01:01.0 Class 0101: 1095:0646 (rev 05)
01:02.0 Class 0604: 1066:0004 (rev 01)
01:03.0 Class 0100: 9004:5078 (rev 03)
01:04.0 Class 0100: 9005:0010 (rev 01)
01:05.0 Class ff00: 106b:0017
01:06.0 Class 0c03: 1045:c861 (rev 10)
02:08.0 Class 0100: 10cd:1300 (rev 03)
02:09.0 Class 0400: 11de:6057 (rev 02)


Base System Installation Checklist:

Initial boot worked: [O]
Configure network HW: [E]
Config network: [O]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Create file systems: [O]
Mount partitions: [O]
Install base system: [O]
Install boot loader: [O]
Reboot: [E]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems:

There were two problems here; the first is pretty minor but the second
is more significant. The first issue was that the onboard network
card was not detected and I had to choose the BMAC driver from the
list myself. Although I realize that not all cards will be
autodetected, it seems like this one should be since it was the
standard onboard card for the G3 series (at least the blue & whites).

The installer completed succesfully, but unfortunately wouldn't reboot
into Debian. Since this machine doesn't have a serial port I could
not capture the output of the boot process in a serial console, so I
had to take a picture and type it all out (and I could only get the
last screen). From the combination of this output and the lspci, it
seems that the problem is related to the firewire module. It's
possible that there are minor typos in this since I had to type it by
hand, so if you need something verified just ask - it's infinitely reproducable:

tsdev: loaded successfully
evbug: blacklisted
evdev: already loaded
input [success]
isapnp
isapnp [success]
net
net [success]
pci
ignoring pci display device on 00:10.0
PCI: Enabling device 0000:01:00.0 (0014 -> 0016)
pcilynx0: allocated PCL memory 4096 Bytes @ 0xd7f01000
pcilynx0: allocated interrupt 21
pcilynx0: remapped memory spaces reg 0xda1e6000, rom 0xda268000, ram 0xda246000, aux 0xda257000
Machine check in kernel mode.
Caused by (from SRR1=41030): Transfer error ack signal
Oops: machine check, sig: 7 [#1]
NIP: DA1E816C LR: DA1E9CB4 SP: D73FDAE0 REGS: d73fda30 TRAP: 0200 Not tainted
MSR: 00041030 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = d7356cf0[826] 'modprobe' THREAD: d73fc000Last syscall: 128
GPR00: 82000000 D73FDAE0 D7356CF0 FFFFFFFF 00000200 FFFFFFFF 00000002 C02B5CDC GPR08: 000591F5 DA1E6F0C 00000000 DA1E6000 82088424 1001DD78 00000000 00000000 GPR16: 00000000 00000000 00000000 00000000 10001378 10018850 00000000 00000000 GPR24: 00000020 D73FA000 C1C7CC48 C1C7CC00 D73FBD98 D73FBD9C D73FBD90 00009032 NIP [da1e816c] get_phy_reg+0x58/0xf4 [pcilynx]
LR [da1e9cb4] add_card+0x4a8/0xbd8 [pcilynx]
Call trace:
[da1e9cb4] add_card+0x4a8/0xbd8 [pcilynx]
[c00b1b80] pci_device_probe_static+0x6c/0x88
[c00b1bec] __pci_device_probe+0x50/0x70
[c00b1c3c] pci_device_probe+0x30/0x60
[c00da81c] bus_match+0x50/0x8c
[c00da99c] driver_attach+0x88/0xc8
[c00dacf4] bus_add_driver+0x98/0xec
[c00db1a8] driver_register+0x30/0x40
[c00b1f44] pci_register_driver+0x68/0xa4
[da10101c] pcilynx_init+0x1c/0xa8 [pcilynx]
[c00365ec] sys_init_module+0x198/0x31c
[c0007c40] ret_from_syscall+0x0/0x44
./pci.agent: line 156: 826 Bus error $MODPROBE $MODULE >/dev/null 2>&1
pcilynx: can't be loaded
missing kernel or user mode driver pcilynx


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.maint.boot
From: [email protected]

On Wed, Aug 11, 2004 at 12:31:04AM -0500, Evilpig wrote:

Output of lspci from my YellowDog install:
00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40)
00:0d.0 PCI bridge: Digital Equipment Corporation DECchip 21154 (rev 02) 00:10.0 VGA compatible controller: ATI Technologies Inc Rage 128 RE/SG 01:00.0 FireWire (IEEE 1394): Texas Instruments PCILynx/PCILynx2 IEEE
1394 Link Layer Controller (rev 02)
01:01.0 IDE interface: CMD Technology Inc PCI0646 (rev 05)
01:02.0 PCI bridge: PicoPower Technology PT86C525 [Nile-II] PCI-to-PCI
Bridge (rev 01)
01:03.0 SCSI storage controller: Adaptec AHA-7850 (rev 03)
01:04.0 SCSI storage controller: Adaptec AHA-2940U2/U2W (rev 01)
01:05.0 Class ff00: Apple Computer Inc. Paddington Mac I/O
01:06.0 USB Controller: OPTi Inc. 82C861 (rev 10)
02:08.0 SCSI storage controller: Advanced System Products, Inc
ABP940-U / ABP960-U (rev 03)
02:09.0 Multimedia video controller: Zoran Corporation ZR36057PQC
Video cutting chipset (rev 02)

Output of lspci -n from my YellowDog install:
00:00.0 Class 0600: 1057:0002 (rev 40)
00:0d.0 Class 0604: 1011:0026 (rev 02)
00:10.0 Class 0300: 1002:5245
01:00.0 Class 0c00: 104c:8000 (rev 02)
01:01.0 Class 0101: 1095:0646 (rev 05)
01:02.0 Class 0604: 1066:0004 (rev 01)
01:03.0 Class 0100: 9004:5078 (rev 03)
01:04.0 Class 0100: 9005:0010 (rev 01)
01:05.0 Class ff00: 106b:0017
01:06.0 Class 0c03: 1045:c861 (rev 10)
02:08.0 Class 0100: 10cd:1300 (rev 03)
02:09.0 Class 0400: 11de:6057 (rev 02)

Comments/Problems:

There were two problems here; the first is pretty minor but the second
is more significant. The first issue was that the onboard network
card was not detected and I had to choose the BMAC driver from the
list myself. Although I realize that not all cards will be
autodetected, it seems like this one should be since it was the
standard onboard card for the G3 series (at least the blue & whites).

I can't find your network card in the lspci output at all. Does anyone have any idea why this could be?

The installer completed succesfully, but unfortunately wouldn't reboot
into Debian. Since this machine doesn't have a serial port I could
not capture the output of the boot process in a serial console, so I
had to take a picture and type it all out (and I could only get the
last screen). From the combination of this output and the lspci, it
seems that the problem is related to the firewire module. It's
possible that there are minor typos in this since I had to type it by
hand, so if you need something verified just ask - it's infinitely reproducable:

tsdev: loaded successfully
evbug: blacklisted
evdev: already loaded
input [success]
isapnp
isapnp [success]
net
net [success]
pci
ignoring pci display device on 00:10.0
PCI: Enabling device 0000:01:00.0 (0014 -> 0016)
pcilynx0: allocated PCL memory 4096 Bytes @ 0xd7f01000
pcilynx0: allocated interrupt 21
pcilynx0: remapped memory spaces reg 0xda1e6000, rom 0xda268000, ram 0xda246000, aux 0xda257000
Machine check in kernel mode.
Caused by (from SRR1=41030): Transfer error ack signal
Oops: machine check, sig: 7 [#1]
NIP: DA1E816C LR: DA1E9CB4 SP: D73FDAE0 REGS: d73fda30 TRAP: 0200 Not tainted
MSR: 00041030 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK = d7356cf0[826] 'modprobe' THREAD: d73fc000Last syscall: 128
GPR00: 82000000 D73FDAE0 D7356CF0 FFFFFFFF 00000200 FFFFFFFF 00000002 C02B5CDC
GPR08: 000591F5 DA1E6F0C 00000000 DA1E6000 82088424 1001DD78 00000000 00000000
GPR16: 00000000 00000000 00000000 00000000 10001378 10018850 00000000 00000000
GPR24: 00000020 D73FA000 C1C7CC48 C1C7CC00 D73FBD98 D73FBD9C D73FBD90 00009032
NIP [da1e816c] get_phy_reg+0x58/0xf4 [pcilynx]
LR [da1e9cb4] add_card+0x4a8/0xbd8 [pcilynx]
Call trace:
[da1e9cb4] add_card+0x4a8/0xbd8 [pcilynx]
[c00b1b80] pci_device_probe_static+0x6c/0x88
[c00b1bec] __pci_device_probe+0x50/0x70
[c00b1c3c] pci_device_probe+0x30/0x60
[c00da81c] bus_match+0x50/0x8c
[c00da99c] driver_attach+0x88/0xc8
[c00dacf4] bus_add_driver+0x98/0xec
[c00db1a8] driver_register+0x30/0x40
[c00b1f44] pci_register_driver+0x68/0xa4
[da10101c] pcilynx_init+0x1c/0xa8 [pcilynx]
[c00365ec] sys_init_module+0x198/0x31c
[c0007c40] ret_from_syscall+0x0/0x44
./pci.agent: line 156: 826 Bus error $MODPROBE $MODULE >/dev/null 2>&1
pcilynx: can't be loaded
missing kernel or user mode driver pcilynx

Looks like a bug in the pcilynx module.

- David Nusinow


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.maint.boot
From: [email protected]

Evilpig wrote:

00:10.0 VGA compatible controller: ATI Technologies Inc Rage 128 RE/SG 01:00.0 FireWire (IEEE 1394): Texas Instruments PCILynx/PCILynx2 IEEE

pci
ignoring pci display device on 00:10.0
PCI: Enabling device 0000:01:00.0 (0014 -> 0016)
pcilynx0: allocated PCL memory 4096 Bytes @ 0xd7f01000

You're right about it being the firewire controller module that seems to
be crashing. Try booting in emergency mode ("linux emergency") and add
pcilynx to /etc/hotplug/blacklist.

--
see shy jo

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBGj/ud8HHehbQuO8RAm56AJ0csb3sPiyPmYbkmKPpPiVTSJe91ACgy1iB tRCnsM1jFHTox65H/iTck4s=
=/UuY
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.maint.boot
From: [email protected]

On Wed, Aug 11, 2004 at 12:49:02PM -0300, Joey Hess wrote:

Evilpig wrote:

00:10.0 VGA compatible controller: ATI Technologies Inc Rage 128 RE/SG 01:00.0 FireWire (IEEE 1394): Texas Instruments PCILynx/PCILynx2 IEEE

pci
ignoring pci display device on 00:10.0
PCI: Enabling device 0000:01:00.0 (0014 -> 0016)
pcilynx0: allocated PCL memory 4096 Bytes @ 0xd7f01000

You're right about it being the firewire controller module that seems to
be crashing. Try booting in emergency mode ("linux emergency") and add pcilynx to /etc/hotplug/blacklist.

This module is also loaded by discover1-data, so you'll have to add a "skip pcilynx" line to /etc/discover.conf too.

- David Nusinow


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.maint.boot
From: [email protected]

On Wed, 11 Aug 2004 11:16:42 -0400, David Nusinow
<[email protected]> wrote:

On Wed, Aug 11, 2004 at 12:31:04AM -0500, Evilpig wrote:

Output of lspci from my YellowDog install:
00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40)
00:0d.0 PCI bridge: Digital Equipment Corporation DECchip 21154 (rev 02) 00:10.0 VGA compatible controller: ATI Technologies Inc Rage 128 RE/SG 01:00.0 FireWire (IEEE 1394): Texas Instruments PCILynx/PCILynx2 IEEE
1394 Link Layer Controller (rev 02)
01:01.0 IDE interface: CMD Technology Inc PCI0646 (rev 05)
01:02.0 PCI bridge: PicoPower Technology PT86C525 [Nile-II] PCI-to-PCI Bridge (rev 01)
01:03.0 SCSI storage controller: Adaptec AHA-7850 (rev 03)
01:04.0 SCSI storage controller: Adaptec AHA-2940U2/U2W (rev 01)
01:05.0 Class ff00: Apple Computer Inc. Paddington Mac I/O
01:06.0 USB Controller: OPTi Inc. 82C861 (rev 10)
02:08.0 SCSI storage controller: Advanced System Products, Inc
ABP940-U / ABP960-U (rev 03)
02:09.0 Multimedia video controller: Zoran Corporation ZR36057PQC
Video cutting chipset (rev 02)

Output of lspci -n from my YellowDog install:
00:00.0 Class 0600: 1057:0002 (rev 40)
00:0d.0 Class 0604: 1011:0026 (rev 02)
00:10.0 Class 0300: 1002:5245
01:00.0 Class 0c00: 104c:8000 (rev 02)
01:01.0 Class 0101: 1095:0646 (rev 05)
01:02.0 Class 0604: 1066:0004 (rev 01)
01:03.0 Class 0100: 9004:5078 (rev 03)
01:04.0 Class 0100: 9005:0010 (rev 01)
01:05.0 Class ff00: 106b:0017
01:06.0 Class 0c03: 1045:c861 (rev 10)
02:08.0 Class 0100: 10cd:1300 (rev 03)
02:09.0 Class 0400: 11de:6057 (rev 02)

Comments/Problems:

There were two problems here; the first is pretty minor but the second
is more significant. The first issue was that the onboard network
card was not detected and I had to choose the BMAC driver from the
list myself. Although I realize that not all cards will be
autodetected, it seems like this one should be since it was the
standard onboard card for the G3 series (at least the blue & whites).

I can't find your network card in the lspci output at all. Does anyone have any
idea why this could be?

I found this previous bug report that looks like it could explain it,
but you'll have a better idea than me:

http://bugs.debian.org/260427

Thanks,
- Colleen


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.maint.boot
From: [email protected]

On Wed, Aug 11, 2004 at 11:16:42AM -0400, David Nusinow wrote:

On Wed, Aug 11, 2004 at 12:31:04AM -0500, Evilpig wrote:

There were two problems here; the first is pretty minor but the
second is more significant. The first issue was that the onboard
network card was not detected and I had to choose the BMAC driver
from the list myself. Although I realize that not all cards will be autodetected, it seems like this one should be since it was the
standard onboard card for the G3 series (at least the blue &
whites).

I can't find your network card in the lspci output at all. Does anyone
have any idea why this could be?

It's not in the lspci output because it's not a PCI card.

I thought I'd fixed this one, so I'd like the reporter to show me the
output of the following two commands, which you should be able to run on
tty2:

ls -l "/proc/device-tree$(cat /proc/device-tree/aliases/mac-io)/bmac"

find "/proc/device-tree$(cat /proc/device-tree/aliases/mac-io)" -type f -name compatible | xargs grep bmac

If the second command gives you a filename, I'd also like to see what's
in the device_type file in the same directory.

Thanks,

--
Colin Watson [[email protected]]


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.maint.boot
From: [email protected]

On Wed, 11 Aug 2004 18:35:27 +0100, Colin Watson <[email protected]> wrote:

It's not in the lspci output because it's not a PCI card.

I thought I'd fixed this one, so I'd like the reporter to show me the
output of the following two commands, which you should be able to run on tty2:

ls -l "/proc/device-tree$(cat /proc/device-tree/aliases/mac-io)/bmac"

find "/proc/device-tree$(cat /proc/device-tree/aliases/mac-io)" -type f -name compatible | xargs grep bmac

If the second command gives you a filename, I'd also like to see what's
in the device_type file in the same directory.

I will gladly do this as soon as I am able to boot into Debian. I
thought maybe I could do this from the installer after telling it to
load the bmac driver, but no such luck. The first command gave me "No
such file or directory" (also a "find /proc -name bmac" turns up
nothing).

As instructed, I added the pcilynx module to /etc/hotplug/blacklist
and "skip pcilynx" to /etc/discover.conf. Unfortunately, I was not
able to do this by booting "Linux emergency". Although it did
successfully boot up that way, my keyboard didn't work, so was unable
to do anything at all. My guess is that it doesn't load the USB
modules (which would be problematic since that is the only type of
keyboard that this machine can be used with...).

Keyboard details:
Standard USB keyboard shipped by Apple with the Blue & White G3 (not
the later Apple Pro Keyboard - this one is smaller), US layout,
connected directly to machine.

Since I couldn't edit the files that way, I just booted into my
YellowDog install and mounted the Debian root partition and edited
them that way.

Happily, the blacklisting of the pcilynx module allows the boot
process to progress beyond that point. Unfortunately it still doesn't
boot all the way without a kernel oops (appears to be USB related this
time). Again, this is hand-typed and may have mistakes so if
something doesn't look right and needs checked, just ask.

Thanks,

- Colleen

Last visible screen of the boot process:

cmd64x: loaded successfully
aic7xxx: already loaded
modprobe: FATAL: error inserting aic79xx (/lib/modules/2.6.7-powerpc/kernel/drivers/scsi/aic7xxx/aic79xx.ko):
No such device

aic79xx: can't be loaded
missing kernel or user mode driver aic79xx
aic7xxx: already loaded
usbcore: registered new driver usbfs
usbcore: registered new driver hub
Oops: kernel access of bad area, sig: 11 [#1]
NIP: C00A7A34 LR: C00A7AD8 SP: D783E50 REGS: d7313da0 TRAP: 0300 Not tainted
MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: DA3416BC, DSISR: 42000000
TASK = d75af990[990] 'modprobe' THREAD: d7982000Last syscall: 128
GPR00: 0000001A D7313E50 D75AACD0 C022A2E4 000000D0 DA1583A8 D7313E60 C01F0000 GPR08: C01F0000 C022A2DC DA3416BC DA15A518 003B0F80 1001DD78 00000000 00000000 GPR16: 00000000 00000000 00000000 00000000 10001378 10018850 00000000 00000000 GPR24: 00000000 100188B8 00000000 C01F0000 00000000 C022A2E4 FFFFFFEA DA15A4FC NIP [c00a7a34] kobject_register+0x9c/0x14c
LR [c00a7ad8 kobject_add+0x140/0x14c
Call trace:
[c00a7b10] kobject_register+0x2c/0x6c
[c00dacb4] bus_add_driver+0x58/0xec
[c00db1a8] driver_register+0x30/0x40
[c00b1f44] pci_register_driver+0x68/0xa4
[da10c05c] ohci_hcd_pci_init+0x5c/0xf8 [ohci_hcd]
[c00365ec] sys_init_odule+0x198/0x31c
[c0007c40] ret_from_syscall +0x0/0x44
./pci.agent: line 156: 990 Segmentation fault $MODPROBE $MODULE >/dev/null 2>&1
ohci-hcd: can't be loaded
missing kernel or user mode driver ohci-hcd
Linux video capture interface: v1.00
Linux video codec intermediate layer: v0.2
Zoran MJPEG board driver version 0.9.5
PCI: Enabling device 0000:02:09.0 (0000 -> 0006)
MJPEG[0]: Zoran ZR36067 (rev 2) irq: 23, memory: 0x80901000
MJPEG[0]: subsystem vendor=0x13ca id=0x4231
ZORAN: 1 card(s) found
Buz[0]: zr36057_init() - initializing card[0], zr=da2a5678
zr36067: loaded successfully
pci [success]
usb


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.maint.boot
From: [email protected]

Evilpig wrote:

On Wed, 11 Aug 2004 18:35:27 +0100, Colin Watson <[email protected]> wrote:

It's not in the lspci output because it's not a PCI card.

I thought I'd fixed this one, so I'd like the reporter to show me the output of the following two commands, which you should be able to run on tty2:

ls -l "/proc/device-tree$(cat /proc/device-tree/aliases/mac-io)/bmac"

find "/proc/device-tree$(cat /proc/device-tree/aliases/mac-io)" -type f -name compatible | xargs grep bmac

If the second command gives you a filename, I'd also like to see what's
in the device_type file in the same directory.

I will gladly do this as soon as I am able to boot into Debian. I
thought maybe I could do this from the installer after telling it to
load the bmac driver, but no such luck. The first command gave me "No
such file or directory" (also a "find /proc -name bmac" turns up
nothing).

Worry not! I have an equivalent machine that I recently successfully got Debian Sarge working on. I saw your message and got curious, so I did the above stuff on it and sent the results to Colin. Let me know if there's anything I can do to help you
get yours working...

<snip!>

Again, this is hand-typed and may have mistakes so if
something doesn't look right and needs checked, just ask.

Thanks,

- Colleen

Last visible screen of the boot process:

<BIG snip!>

Wow! Your dedication quotient just got a major bump in karma points! My eyes glaze over just thinking about typing all that!

Enjoy!

Rick


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.maint.boot
From: [email protected]

On Wed, Aug 11, 2004 at 07:15:28PM -0500, Evilpig wrote:

On Wed, 11 Aug 2004 18:35:27 +0100, Colin Watson <[email protected]> wrote:

It's not in the lspci output because it's not a PCI card.

I thought I'd fixed this one, so I'd like the reporter to show me the output of the following two commands, which you should be able to run on tty2:

ls -l "/proc/device-tree$(cat /proc/device-tree/aliases/mac-io)/bmac"

find "/proc/device-tree$(cat /proc/device-tree/aliases/mac-io)" -type f -name compatible | xargs grep bmac

If the second command gives you a filename, I'd also like to see what's
in the device_type file in the same directory.

I will gladly do this as soon as I am able to boot into Debian. I
thought maybe I could do this from the installer after telling it to
load the bmac driver, but no such luck. The first command gave me "No
such file or directory" (also a "find /proc -name bmac" turns up
nothing).

As instructed, I added the pcilynx module to /etc/hotplug/blacklist
and "skip pcilynx" to /etc/discover.conf. Unfortunately, I was not
able to do this by booting "Linux emergency". Although it did
successfully boot up that way, my keyboard didn't work, so was unable
to do anything at all. My guess is that it doesn't load the USB
modules (which would be problematic since that is the only type of
keyboard that this machine can be used with...).

Well, the same happens on my pegasos with ps/2 keyboard. I suppose that mkinitrd should add at least the keyboard modules to the initrd, which is nice to have when a manual fsck is needed. Maybe you could provide a followup to
bug report #264839 ?

Friendly,

Sven Luther


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.maint.boot
From: [email protected]

On Thu, 12 Aug 2004 09:28:20 +0200, Sven Luther <[email protected]> wrote:

On Wed, Aug 11, 2004 at 07:15:28PM -0500, Evilpig wrote:

As instructed, I added the pcilynx module to /etc/hotplug/blacklist
and "skip pcilynx" to /etc/discover.conf. Unfortunately, I was not
able to do this by booting "Linux emergency". Although it did
successfully boot up that way, my keyboard didn't work, so was unable
to do anything at all. My guess is that it doesn't load the USB
modules (which would be problematic since that is the only type of
keyboard that this machine can be used with...).

Well, the same happens on my pegasos with ps/2 keyboard. I suppose that mkinitrd should add at least the keyboard modules to the initrd, which is nice
to have when a manual fsck is needed. Maybe you could provide a followup to bug report #264839 ?

Friendly,

Sven Luther

Done; thanks for the suggestion ;-)

- Colleen


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)