Bug#264492: NewWorld (G4) PowerPC d-i hardware detect does not see firewire disk
On Mon, Aug 09, 2004 at 08:02:05PM -0300, Joey Hess wrote: Sven Luther wrote: - i suspect that the pci id is already used to load the actual firewire driver, and since discover 1 cannot load more than one module for a given pci id, i suspect you will encounter problem this way. I suppose ohci1394 will be loaded for the pci id. That said, there is some other place where other modules are loaded, since d-i clearly loads the firewire network modules. Once it finds ohci1394 loaded, hw-detect will unconditionally try to load sbp2 and eth1394 modules, as there's no other way. I think that ohci1394 is the right thing to have in the discover db for firewire controllers, after all you can't tell what's on the controller and as you say discover can only load one module. As far as I can see, discover1-data has no pci ids mapped to sbp2 or eth1394, they all map to ohci1394. Ok, so we do it by hand. I wonder though what newworld pmac box he has that doesn't work, apple usually reused the same componnent in various boxes, and thus it should usually work. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#264492: NewWorld (G4) PowerPC d-i hardware detect does not see firewire disk
On Monday, August 9, 2004, at 03:55 PM, Rick_Thomas wrote: OK, as I said, output of lspci and lspci -n will be sent tonight, when I can get my hands on the machine in question. Here is the output of lspci ; lspci -n Hope it helps! BTW, I manually did modprobe ohci1394 ; modprobe sbp2 just before the discover disk hardware phase to get this. Out of curiosity, I let the installation proceed (even though I knew it was doomed, because at reboot time the initrd wouldn't know that it would be necessary to load those two modules.) When the time came to install yaboot, it failed. Contents of /var/log are available on request if you think it will help to take a look. Also, I can repeat the process with a higher debug level, if that would help. Rick :00:0b.0 Host bridge: Apple Computer Inc. UniNorth 1.5 AGP :00:10.0 VGA compatible controller: ATI Technologies Inc Radeon RV200 QW [Radeon 7500] :01:0b.0 Host bridge: Apple Computer Inc. UniNorth 1.5 PCI :01:17.0 ff00: Apple Computer Inc. KeyLargo Mac I/O (rev 03) :01:18.0 USB Controller: Apple Computer Inc. KeyLargo USB :01:19.0 USB Controller: Apple Computer Inc. KeyLargo USB :02:0b.0 Host bridge: Apple Computer Inc. UniNorth 1.5 Internal PCI :02:0e.0 FireWire (IEEE 1394): Lucent Microelectronics FW323 :02:0f.0 Ethernet controller: Apple Computer Inc. UniNorth GMAC (Sun GEM) (rev 01) :00:0b.0 0600: 106b:002d :00:10.0 0300: 1002:5157 :01:0b.0 0600: 106b:002e :01:17.0 ff00: 106b:0022 (rev 03) :01:18.0 0c03: 106b:0019 :01:19.0 0c03: 106b:0019 :02:0b.0 0600: 106b:002f :02:0e.0 0c00: 11c1:5811 :02:0f.0 0200: 106b:0021 (rev 01) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#264492: NewWorld (G4) PowerPC d-i hardware detect does not see firewire disk
On Tuesday, August 10, 2004, at 04:04 AM, Sven Luther wrote: Ok, so we do it by hand. I wonder though what newworld pmac box he has that doesn't work, apple usually reused the same componnent in various boxes, and thus it should usually work. Well, it's a PowerMac G4 733 MHz. The case is grey. No mirror-effect doors, no mesh-like front. And, if it helps, here's what Apple System Profiler has to say about the Firewire: OXFORD IDE Device LUN 0 Vendor ID: 1d2 Speed: 400 Mb/sec GUID: 119296d Vendor name:Oxford Semiconductor Ltd. Unit version: 66691 And Here's what it says about the rest of it. Production information ROM revision: Boot ROM version: 4.33f2 Serial number: XB2250EL-M1X-ff11-3-5 Software bundle: Not applicable Sales order number: 0100612491 Software overview Serial number: XB2250ELM1X Mac OS overview System: Mac OS X 10.1.5 (5S66) Startup device Name: GreyBoxHD Memory overview Built-in memory:768 MB Number of empty RAM slots: 1 (DIMM2/J23) PC133 CL3 LocationSizeMemory type DIMM0/J21 256 MB SDRAM DIMM1/J22 512 MB SDRAM L2 cache: 256K L3 cache: Hardware overview Machine ID: 406 Model name: Power Mac G4 Keyboard type: Apple Pro Keyboard Processor info: PowerPC G4 (2.1) Machine speed: 733 MHz Network overview Where: built-in Flags: Multicast, Simplex, Running, b6, Broadcast, Up Address:00.03.93.6f.ab.a0 IP Address: 192.168.1.162 Broadcast address: 192.168.255.255 net mask: 255.255.0.0
Re: Bug#264492: NewWorld (G4) PowerPC d-i hardware detect does not see firewire disk
On Tue, Aug 10, 2004 at 04:26:04AM -0400, Rick Thomas wrote: On Monday, August 9, 2004, at 03:55 PM, Rick_Thomas wrote: OK, as I said, output of lspci and lspci -n will be sent tonight, when I can get my hands on the machine in question. Here is the output of lspci ; lspci -n Hope it helps! Ok, I cloned this assigned the clone to discover1-data (I'll fix it in CVS today). Joey or someone else, if you want to load this module by default go for it, otherwise I think it's safe to just close the original install report. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#264492: NewWorld (G4) PowerPC d-i hardware detect does not see firewire disk
On Tue, 2004-08-10 at 11:52, David Nusinow wrote: On Tue, Aug 10, 2004 at 04:26:04AM -0400, Rick Thomas wrote: On Monday, August 9, 2004, at 03:55 PM, Rick_Thomas wrote: OK, as I said, output of lspci and lspci -n will be sent tonight, when I can get my hands on the machine in question. Here is the output of lspci ; lspci -n Hope it helps! Ok, I cloned this assigned the clone to discover1-data (I'll fix it in CVS today). Joey or someone else, if you want to load this module by default go for it, otherwise I think it's safe to just close the original install report. If you close the original install report, how will I know when there is a daily with the proposed fix in it that I should test? Thanks! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#264492: NewWorld (G4) PowerPC d-i hardware detect does not see firewire disk
Rick Thomas wrote: The detect disks phase failed to detect my firewire disk, which I was intending to use for installation test. I'm afraid that your report left out the lspci and lspci -n output that we need to get ohci1394 loaded on your system and enable firewire support. -- see shy jo signature.asc Description: Digital signature
Bug#264492: NewWorld (G4) PowerPC d-i hardware detect does not see firewire disk
On Mon, 2004-08-09 at 11:54, Joey Hess wrote: Rick Thomas wrote: The detect disks phase failed to detect my firewire disk, which I was intending to use for installation test. I'm afraid that your report left out the lspci and lspci -n output that we need to get ohci1394 loaded on your system and enable firewire support. OK, I'm at work right now, and the machine is at home, but I'll try to get you that data tonight. However, that said, let me argue that it should not be needed: All NewWorld Macs have onboard FireWire, and so potentially need ohci1394 and sbp2 to access external disks. Now, it's true that not all NewWorld Macs will have actual firewire disks, and loading those modules should probably be optional, not default. So... why not just always make the ohci1394 and sbp2 modules available as an option in one of the hardware discovery menus whenever we're installing on a NewWorld Mac? Or is there something about the hardware discovery process that I don't know (very likely) that makes that difficult or unpalatable? Like, it's totally driven by [the equivalent of] the output of lspci? Is there a design/implementation document somewhere that describes this process? I'd be interested in reading it, if it's available. Thanks for all the hard work! Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#264492: NewWorld (G4) PowerPC d-i hardware detect does not see firewire disk
Rick_Thomas wrote: However, that said, let me argue that it should not be needed: All NewWorld Macs have onboard FireWire, and so potentially need ohci1394 and sbp2 to access external disks. Now, it's true that not all NewWorld Macs will have actual firewire disks, and loading those modules should probably be optional, not default. So... why not just always make the ohci1394 and sbp2 modules available as an option in one of the hardware discovery menus whenever we're installing on a NewWorld Mac? Or is there something about the hardware discovery process that I don't know (very likely) that makes that difficult or unpalatable? Like, it's totally driven by [the equivalent of] the output of lspci? Is there a design/implementation document somewhere that describes this process? I'd be interested in reading it, if it's available. Of course we could always load this module on newworld macs if we decided that was the best way. As I'm not a mac person, I really can't say. Personally, I perfer being cautious about loading hardware drivers unconditionally, since there are often edge cases where they hang a machine. And while perhaps all newworld macs have firewire today, it's hard to say if that will be the case tomorrow. The nice thing about the pci bus is it lets us eliminate the guesswork. Anyway, adding the pci id is the quickest fix at this point. -- see shy jo signature.asc Description: Digital signature
Bug#264492: NewWorld (G4) PowerPC d-i hardware detect does not see firewire disk
On Mon, 2004-08-09 at 15:07, Joey Hess wrote: Rick_Thomas wrote: However, that said, let me argue that it should not be needed: All NewWorld Macs have onboard FireWire, and so potentially need ohci1394 and sbp2 to access external disks. Now, it's true that not all NewWorld Macs will have actual firewire disks, and loading those modules should probably be optional, not default. So... why not just always make the ohci1394 and sbp2 modules available as an option in one of the hardware discovery menus whenever we're installing on a NewWorld Mac? Or is there something about the hardware discovery process that I don't know (very likely) that makes that difficult or unpalatable? Like, it's totally driven by [the equivalent of] the output of lspci? Is there a design/implementation document somewhere that describes this process? I'd be interested in reading it, if it's available. Of course we could always load this module on newworld macs if we decided that was the best way. As I'm not a mac person, I really can't say. Personally, I perfer being cautious about loading hardware drivers unconditionally, since there are often edge cases where they hang a machine. And while perhaps all newworld macs have firewire today, it's hard to say if that will be the case tomorrow. The nice thing about the pci bus is it lets us eliminate the guesswork. Anyway, adding the pci id is the quickest fix at this point. OK, as I said, output of lspci and lspci -n will be sent tonight, when I can get my hands on the machine in question. Still, perhaps I wasn't clear. I was suggesting only that the modules be made available as a user-choice option in one of the discovering hardware menus -- not that they be loaded always. I agree that future Macs cannot be guaranteed to have built-in onboard firewire, or they may have firewire controllers that don't conform to the ohci1394 specs and freeze up when presented with ohci1394 commands. So make it optional, but make it a standard option. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#264492: NewWorld (G4) PowerPC d-i hardware detect does not see firewire disk
On Mon, Aug 09, 2004 at 04:07:12PM -0300, Joey Hess wrote: Rick_Thomas wrote: However, that said, let me argue that it should not be needed: All NewWorld Macs have onboard FireWire, and so potentially need ohci1394 and sbp2 to access external disks. Now, it's true that not all NewWorld Macs will have actual firewire disks, and loading those modules should probably be optional, not default. So... why not just always make the ohci1394 and sbp2 modules available as an option in one of the hardware discovery menus whenever we're installing on a NewWorld Mac? Or is there something about the hardware discovery process that I don't know (very likely) that makes that difficult or unpalatable? Like, it's totally driven by [the equivalent of] the output of lspci? Is there a design/implementation document somewhere that describes this process? I'd be interested in reading it, if it's available. Of course we could always load this module on newworld macs if we decided that was the best way. As I'm not a mac person, I really can't say. Personally, I perfer being cautious about loading hardware drivers unconditionally, since there are often edge cases where they hang a machine. And while perhaps all newworld macs have firewire today, it's hard to say if that will be the case tomorrow. The nice thing about the pci bus is it lets us eliminate the guesswork. Anyway, adding the pci id is the quickest fix at this point. Joeyh, two comments on this : - firewire will probably be on newworld pmacs for the whole of sarge (and probably even sarge+1) lifetime, if not longer. - i suspect that the pci id is already used to load the actual firewire driver, and since discover 1 cannot load more than one module for a given pci id, i suspect you will encounter problem this way. I suppose ohci1394 will be loaded for the pci id. That said, there is some other place where other modules are loaded, since d-i clearly loads the firewire network modules. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#264492: NewWorld (G4) PowerPC d-i hardware detect does not see firewire disk
Sven Luther wrote: - i suspect that the pci id is already used to load the actual firewire driver, and since discover 1 cannot load more than one module for a given pci id, i suspect you will encounter problem this way. I suppose ohci1394 will be loaded for the pci id. That said, there is some other place where other modules are loaded, since d-i clearly loads the firewire network modules. Once it finds ohci1394 loaded, hw-detect will unconditionally try to load sbp2 and eth1394 modules, as there's no other way. I think that ohci1394 is the right thing to have in the discover db for firewire controllers, after all you can't tell what's on the controller and as you say discover can only load one module. As far as I can see, discover1-data has no pci ids mapped to sbp2 or eth1394, they all map to ohci1394. -- see shy jo signature.asc Description: Digital signature
Bug#264492: NewWorld (G4) PowerPC d-i hardware detect does not see firewire disk
Package: installation-reports powerpc businesscard RC1 NewWorld PowerMac INSTALL REPORT Synopsis: Partition hard drives fails to see FireWire disk on powerpc NewWorld (G4) PowerMac on RC1 businesscard install. You folks are probably tired of seeing OldWorld PowerPC bug reports from me, so I thought I'd shake things up a bit with a NewWorld bug report. Debian-installer-version: Fill in date and from where you got the image http://cdimage.debian.org/pub/cdimage-testing/sarge_d- i/powerpc/rc1/sarge-powerpc-businesscard.iso uname -a: The result of running uname -a on a shell prompt Not available Date: 2004/08/08 23:00 GMT Method: How did you install? booted businesscard CD in expert mode If network install, from where? /etc/apt/sources.list #deb ftp://ftp.us.debian.org/debian/ sarge main deb ftp://ftp.us.debian.org/debian/ testing main deb-src ftp://ftp.us.debian.org/debian/ testing main Proxied? No Machine: Description of machine (eg, IBM Thinkpad R32) NewWorld PowerMac G4 733MHz grey tower with handles Processor: G4 733MHz Memory: 768 MB Root Device: Didn't get that far because it didn't see my FireWire drive, which I intended to use for installation testing. Drive is a 200 GB connected to the onboard firewire port. 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] See below Partition hard drives: [e] See below Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] Comments/Problems: The detect disks phase failed to detect my firewire disk, which I was intending to use for installation test. I started over and, just before detect disks phase, I switched to the F2 console and typed modprobe ohci1394 modprobe sbp2 Then switched back to the F1 console and proceeded. This time it saw the firewire disk. Log files and other debugging information available on request. Install logs and other status info is available in /var/log/debian-installer/. Once you have filled out this report, mail it to [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
