Bug#270599: Testing newoldworld pmac miboot 2.6 floppies
On Fri, Sep 17, 2004 at 09:55:17AM +0200, Sven Luther wrote: Definitively a bug in discover, could you fill a bug report against discover1 with your lspci and lspci -n output ? You won't get much help out of lspci. These are not PCI devices. The macio chip shows up as one huge PCI device, and the macio layer knows how to /proc/device-tree/aliases then. And this probably means that there is no chance ever of discover discovering them. Oh well. Attached is a tar-ball of /proc/device-tree from this machine. I hope it helps! Rick device-tree.tar.gz Description: GNU Zip compressed data
Bug#270599: Testing newoldworld pmac miboot 2.6 floppies
On Friday, September 17, 2004, at 03:55 AM, Sven Luther wrote: On Fri, Sep 17, 2004 at 02:31:09AM -0400, Rick Thomas wrote: Meanwhile, back at the 2.4 ranch... The 2.4 boot floppy read, switched to text mode, asked for root, which read, asked for language (English), then gave me a blue screen which lasted for more than a minute. I switched to the F2 console, killed 4 processes: "udpkg --configure --force-configure countrychooser", two more "countrychooser", and "grep US" [this may be a clue]. Back on the main menu on F1 console, I told it to "load drivers" and fed it the "root-2". It read that and decoded it, then put me in the country chooser screen (not blue, this time) I chose "US". [possible clue: There is probably a file (the one the "grep US" was looking for) that is on the "root-2" floppy, but is needed by the country chooser, so should be on the "root" floppy...] Indeed. Do you know the name of the floppy in question ? I'm not sure what you're asking, but here's the table of contents of the directory I got the floppies from... Index of /~luther/d-i/images/2004-09-16/powerpc/floppy-2.4 NameLast modified Size Description Parent Directory26-Aug-2004 21:35 - asian-root.img 16-Sep-2004 01:55 1.1M boot.img16-Sep-2004 01:55 1.4M cd-drivers.img 16-Sep-2004 01:56 1.4M net-drivers.img 16-Sep-2004 01:56 1.4M ofonlyboot.img 16-Sep-2004 01:56 1.4M root-2.img 16-Sep-2004 01:56 1.4M root.img16-Sep-2004 01:58 1.2M Apache/1.3.26 Server at people.debian.org Port 80 It asked for an ethernet driver. The 8139too wasn't listed so I said "none of the above" to get it to read the net-drivers floppy. It did, and things continued normally til we got to choose a mirror. I chose "ftp.us.debian.org" but it didn't ask for protocol type or debian version, and when it tried to read stuff, I got the "no driver modules" message. I hit "go back" and re-did the mirror choice (presumably at lower priority). This time it did ask for Debian version. I said "unstable", and it proceeded without problems until it got to the partitioner. Yes, this is the infamous 2.6.8 modules not in sarge. I may have a solution for this, but it will need some convincing and work. Remember, this is the *2.4* floppy set I'm using here. Does that make any difference? As with previous attempts, the partitioner said "no disks found". Also as with previous attempts, poking around on the F2 console shows that it really hasn't found any disks. Ok. We need to know what is your ide controller, and in which udeb it is found, and if discover lists it or not. It's an "UltraATA 133/100 Pro for Mac" PCI-card, from SIIG, Inc of Freemont CA. It works with kernel 2.4.25 and 2.6.8 installed from a businesscard CD. Output of lspci and lspci -n: :00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40) :00:0d.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10) :00:0e.0 SCSI storage controller: Artop Electronic Corp ATP865 (rev 06) :00:0f.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) (rev 13) :00:10.0 ff00: Apple Computer Inc. Heathrow Mac I/O (rev 01) :00:12.0 VGA compatible controller: ATI Technologies Inc 3D Rage I/II 215GT [Mach64 GT] (rev 9a) :01:08.0 USB Controller: NEC Corporation USB (rev 41) :01:08.1 USB Controller: NEC Corporation USB (rev 41) :01:08.2 USB Controller: NEC Corporation USB 2.0 (rev 02) :01:0b.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394 Controller (Link) :00:00.0 0600: 1057:0002 (rev 40) :00:0d.0 0200: 1186:1300 (rev 10) :00:0e.0 0100: 1191:0009 (rev 06) :00:0f.0 0604: 3388:0021 (rev 13) :00:10.0 ff00: 106b:0010 (rev 01) :00:12.0 0300: 1002:4754 (rev 9a) :01:08.0 0c03: 1033:0035 (rev 41) :01:08.1 0c03: 1033:0035 (rev 41) :01:08.2 0c03: 1033:00e0 (rev 02) :01:0b.0 0c00: 104c:8020 I *think* the driver it needs is aec62xx, but doing "lspci | grep aec62xx" on the F2 console during the install show that driver as having been loaded. So I don't kow what to think. Unless one of the "ide-*" drivers it claimed to have not found is the culprit? Back at the main menu, I changed installer priority to "low", and re-ran detect hardware. It said "unable to load some modules" listing: ide-scsi, ide-mod, ide-probe-mod, ide-detect, ide-generic, ide-floppy. Presumably one of those is needed to get it to see my IDE disk. Strange. Just for fun, I did a "modprobe mesh", and re-ran detect hardware. This time it found my SCSI ZIP disk, and offered to partition it for me. I declined and rebooted to write up this report. Definitively a bug in discover, could you fil
Bug#270599: Testing newoldworld pmac miboot 2.6 floppies
On Friday, September 17, 2004, at 01:00 PM, Sven Luther wrote: On Fri, Sep 17, 2004 at 09:42:09AM -0700, Brad Boyer wrote: [Lots of stuff about what's where in a beige G3 ...] Bottom line, Sven, what pieces of information about the G3 do you need from me? Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Testing newoldworld pmac miboot 2.6 floppies
On Fri, Sep 17, 2004 at 09:55:17AM +0200, Sven Luther wrote: > Damnit. But Jens reported it as working on his oldworld box. Could you maybe > fill a bug report against kernel-image-2.6.8-powerpc about this ? I suspect that the one that worked was SCSI only. All the first generation PCI powermacs (7x00,8x00,9x00) had one or two SCSI controllers, but no onboard IDE. However, most of the G3 models had IDE and SCSI onboard, and used mostly IDE devices. > Ok. We need to know what is your ide controller, and in which udeb it is > found, and if discover lists it or not. If it is the onboard stuff, it can't be built as a separate module from the way the source looks. It appears that ide/ppc/pmac.c is always compiled into ide-core if it is enabled. > Definitively a bug in discover, could you fill a bug report against discover1 > with your lspci and lspci -n output ? You won't get much help out of lspci. These are not PCI devices. The macio chip shows up as one huge PCI device, and the macio layer knows how to read data from OF to find the sub-devices. I don't think either version of discover has any knowledge of macio, which prevents detection of drivers like mac53c94, mesh, mace, pmac_zilog, and lots of other older mac stuff. The pmac IDE support can handle both PCI and macio devices, but I'm pretty sure that only newworld macs came with onboard IDE that showed up as separate PCI devices. Brad Boyer [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Testing newoldworld pmac miboot 2.6 floppies
On Fri, Sep 17, 2004 at 09:42:09AM -0700, Brad Boyer wrote: > On Fri, Sep 17, 2004 at 09:55:17AM +0200, Sven Luther wrote: > > Damnit. But Jens reported it as working on his oldworld box. Could you maybe > > fill a bug report against kernel-image-2.6.8-powerpc about this ? > > I suspect that the one that worked was SCSI only. All the first generation > PCI powermacs (7x00,8x00,9x00) had one or two SCSI controllers, but no > onboard IDE. However, most of the G3 models had IDE and SCSI onboard, and > used mostly IDE devices. Ah, maybe ... > > Ok. We need to know what is your ide controller, and in which udeb it is > > found, and if discover lists it or not. > > If it is the onboard stuff, it can't be built as a separate module from > the way the source looks. It appears that ide/ppc/pmac.c is always > compiled into ide-core if it is enabled. Yes, indeed it is. > > Definitively a bug in discover, could you fill a bug report against discover1 > > with your lspci and lspci -n output ? > > You won't get much help out of lspci. These are not PCI devices. The macio > chip shows up as one huge PCI device, and the macio layer knows how to /proc/device-tree/aliases then. And this probably means that there is no chance ever of discover discovering them. Oh well. > read data from OF to find the sub-devices. I don't think either version > of discover has any knowledge of macio, which prevents detection of drivers > like mac53c94, mesh, mace, pmac_zilog, and lots of other older mac stuff. > The pmac IDE support can handle both PCI and macio devices, but I'm pretty > sure that only newworld macs came with onboard IDE that showed up as > separate PCI devices. Probably yes. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Testing newoldworld pmac miboot 2.6 floppies
On Fri, Sep 17, 2004 at 02:31:09AM -0400, Rick Thomas wrote: > > > Sven Luther wrote: > > > > > Oh, and btw, I'm just installing my oldworld 4400/200 mac with d-i and the > > > daily built 2.4-floppy images (with root.img and root-2.img) and it seems to > > > work fine - right now. I'll keep you informed in another mail. > > > > BTW, as of tomorrows build, the 2.6 images should be fine also. > > The 2.6 images now fit on a physical floppy, so that's good. Unfortunately, the > resulting floppy doesn't boot on my G3. It reads and gives me a tux-mac icon, but > when it gets to the end the screen colors invert, and it just sits there. No text > screen. The boot floppy doesn't eject. When I eject it manually, feed it the > "root" floppy, and hit , nothing happens -- specifically, it doesn't start > reading the root floppy. This same behavior happens for both the "boot" and > "ofonlyboot" floppies. Damnit. But Jens reported it as working on his oldworld box. Could you maybe fill a bug report against kernel-image-2.6.8-powerpc about this ? Anyway, we will work on that at the Oldenbourg meeting next week, so there may be progress done there. > Meanwhile, back at the 2.4 ranch... > > The 2.4 boot floppy read, switched to text mode, asked for root, which read, asked > for language (English), then gave me a blue screen which lasted for more than a > minute. I switched to the F2 console, killed 4 processes: "udpkg --configure > --force-configure countrychooser", two more "countrychooser", and "grep US" [this > may be a clue]. Back on the main menu on F1 console, I told it to "load drivers" > and fed it the "root-2". It read that and decoded it, then put me in the country > chooser screen (not blue, this time) I chose "US". [possible clue: There is > probably a file (the one the "grep US" was looking for) that is on the "root-2" > floppy, but is needed by the country chooser, so should be on the "root" floppy...] Indeed. Do you know the name of the floppy in question ? > It asked for an ethernet driver. The 8139too wasn't listed so I said "none of the > above" to get it to read the net-drivers floppy. It did, and things continued > normally til we got to choose a mirror. I chose "ftp.us.debian.org" but it didn't > ask for protocol type or debian version, and when it tried to read stuff, I got the > "no driver modules" message. I hit "go back" and re-did the mirror choice > (presumably at lower priority). This time it did ask for Debian version. I said > "unstable", and it proceeded without problems until it got to the partitioner. Yes, this is the infamous 2.6.8 modules not in sarge. I may have a solution for this, but it will need some convincing and work. > As with previous attempts, the partitioner said "no disks found". Also as with > previous attempts, poking around on the F2 console shows that it really hasn't found > any disks. Ok. We need to know what is your ide controller, and in which udeb it is found, and if discover lists it or not. > Back at the main menu, I changed installer priority to "low", and re-ran detect > hardware. It said "unable to load some modules" listing: ide-scsi, ide-mod, > ide-probe-mod, ide-detect, ide-generic, ide-floppy. Presumably one of those is > needed to get it to see my IDE disk. Strange. > Just for fun, I did a "modprobe mesh", and re-ran detect hardware. This time it > found my SCSI ZIP disk, and offered to partition it for me. I declined and rebooted > to write up this report. Definitively a bug in discover, could you fill a bug report against discover1 with your lspci and lspci -n output ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Testing newoldworld pmac miboot 2.6 floppies
Sven Luther wrote: > > > Oh, and btw, I'm just installing my oldworld 4400/200 mac with d-i and the > > daily built 2.4-floppy images (with root.img and root-2.img) and it seems to > > work fine - right now. I'll keep you informed in another mail. > > BTW, as of tomorrows build, the 2.6 images should be fine also. The 2.6 images now fit on a physical floppy, so that's good. Unfortunately, the resulting floppy doesn't boot on my G3. It reads and gives me a tux-mac icon, but when it gets to the end the screen colors invert, and it just sits there. No text screen. The boot floppy doesn't eject. When I eject it manually, feed it the "root" floppy, and hit , nothing happens -- specifically, it doesn't start reading the root floppy. This same behavior happens for both the "boot" and "ofonlyboot" floppies. Meanwhile, back at the 2.4 ranch... The 2.4 boot floppy read, switched to text mode, asked for root, which read, asked for language (English), then gave me a blue screen which lasted for more than a minute. I switched to the F2 console, killed 4 processes: "udpkg --configure --force-configure countrychooser", two more "countrychooser", and "grep US" [this may be a clue]. Back on the main menu on F1 console, I told it to "load drivers" and fed it the "root-2". It read that and decoded it, then put me in the country chooser screen (not blue, this time) I chose "US". [possible clue: There is probably a file (the one the "grep US" was looking for) that is on the "root-2" floppy, but is needed by the country chooser, so should be on the "root" floppy...] It asked for an ethernet driver. The 8139too wasn't listed so I said "none of the above" to get it to read the net-drivers floppy. It did, and things continued normally til we got to choose a mirror. I chose "ftp.us.debian.org" but it didn't ask for protocol type or debian version, and when it tried to read stuff, I got the "no driver modules" message. I hit "go back" and re-did the mirror choice (presumably at lower priority). This time it did ask for Debian version. I said "unstable", and it proceeded without problems until it got to the partitioner. As with previous attempts, the partitioner said "no disks found". Also as with previous attempts, poking around on the F2 console shows that it really hasn't found any disks. Back at the main menu, I changed installer priority to "low", and re-ran detect hardware. It said "unable to load some modules" listing: ide-scsi, ide-mod, ide-probe-mod, ide-detect, ide-generic, ide-floppy. Presumably one of those is needed to get it to see my IDE disk. Just for fun, I did a "modprobe mesh", and re-ran detect hardware. This time it found my SCSI ZIP disk, and offered to partition it for me. I declined and rebooted to write up this report. Hope this helps! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
