Re: No HFS driver, and change install priority menu option missing -- and other bugs found while testing 2.4 boot floppies on OldWorld PowerMac
On Thursday, September 23, 2004, at 06:13 PM, Sven Luther wrote: I understand the size constraints. But isn't that the reason why we added the root-2 floppy? Would adding hfs and/or hfsplus kick us over the edge into root-3 land? We could indeed add it to root-2, but i would prefer to get the floppy loading work correctly before i do this rather cosmetic thing working. And hfs/hfsplus without ide/scsi driver is not really all that usefull, isn't it. OK. I think see the logic. I'm not clear on what comes from where as far as drivers and install components. Can you give me a general picture? (Seemingly, net-drivers and cd-drivers are obvious, but maybe not?) In particular, how are things that *aren't* on a particular floppy retrieved, and how does it know which of those to retrieve? Also, is there a general rule for what goes on root, root-2, one of the drivers floppy, or over the web? Thanks! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: No HFS driver, and change install priority menu option missing -- and other bugs found while testing 2.4 boot floppies on OldWorld PowerMac
On Thursday, September 23, 2004, at 06:45 PM, Sven Luther wrote: On Thu, Sep 23, 2004 at 06:30:48PM -0400, Rick Thomas wrote: On Thursday, September 23, 2004, at 06:13 PM, Sven Luther wrote: I understand the size constraints. But isn't that the reason why we added the root-2 floppy? Would adding hfs and/or hfsplus kick us over the edge into root-3 land? We could indeed add it to root-2, but i would prefer to get the floppy loading work correctly before i do this rather cosmetic thing working. And hfs/hfsplus without ide/scsi driver is not really all that useful, isn't it. OK. I think see the logic. I'm not clear on what comes from where as far as drivers and install components. Can you give me a general picture? (Seemingly, net-drivers and cd-drivers are obvious, but maybe not?) In particular, how are things that *aren't* on a particular floppy retrieved, and how does it know which of those to retrieve? Also, is there a general rule for what goes on root, root-2, one of the drivers floppy, or over the web? They are not, we need to find out a rule for those. Floppies are mainly worked and tested on x86, which have not the size problem we have. In root needs to be everything to load the rest of the floppies (the floppy driver and retriever) and the most of the other stuff. That is the only constraint. We put in root-2 the rest of the non-driver stuff, in the net drivers the network drivers, and in the cd drivers the ide/scsi/cdrom/disk/filesystem stuff, needed to make the cdrom work and retrieve more stuff from there. For the rest of it, it is up to us to take decisions. Let me see if I've got this right -- please correct me if I've misunderstood: BOOT) The boot floppy has the kernel and miboot loader stuff (fake System that's really a boot-loader, and empty Finder). That's all there is and it pretty much fills up the disk, even with a severely stripped-down (anorexic?) kernel. For what it's worth, there is about 169 K left. ROOT) The root floppy has enough on it to talk to the console and keyboard (at least as far as being able to tell cr, the space key, the arrow-keys, and the tab key -- none of which depend on locale) set the locale, and finally, load the root-2 floppy. That pretty much fills the floppy. There's about 160 K left on root of compressed space: equivalent to [maybe] 570 K of uncompressed space assuming a compression ratio similar to that of the current contents -- about 1:4. The largest single file is libc. After that is /var/lib/dpkg/info, /bin/busybox, and /usr/lib/locale. Together these account for about 1/3 of the uncompressed space. The remaining 2/3 is lots of small potatoes -- nothing one can point to and say That's big and useless. Let's get rid of it!. ROOT-2) The root-2 floppy is a bunch of udebs for all the components that wouldn't fit on root. [This is a good design, but it requires that root have everything needed to install a udeb, making the root floppy even more crowded.] The root-2 floppy seems to have about 600 K of free space. Since udeb's are already compressed, there's no issue of compressed vs uncompressed space on root-2. Most of the stuff on root-2 seems to be for setting up the network (The largest single file is nic-extra-modules-2.4.27-powerpc-small- di.udeb -- 409 K, over half the total.) Some of that could, theoretically, be moved to the net-drivers floppy, but what would be the point? As long as root-2 is needed at all for overflow from root, and there's free space on it, why not use it? However, it's worth keeping this observation in mind if space on root-2 becomes tight and net-drivers remains uncrowded. The only stuff that really is absolutely required to be on root-2 is that which is (1) not absolutely required to be on root, and (2) is needed for *both* a net-install *and* a CD-install. I'm not knowledgeable enough about the details of d-i architecture to tell which of the udebs on the present root-2 fits that criterion. Can you give me some clues? NET-DRIVERS) The net-drivers floppy, like root-2, is a collection of udeb's. This represents everything (modulo the stuff that goes on root-2 because it's there) that is needed to get to the point of being able to download stuff from the web. This includes drivers for *all* sorts of network interfaces (PCI NIC cards, wireless PC-card NICs for laptops, serial-IP for people who must use modems, etc, etc...). It also includes things like dhcp-client, choose-mirror, software for getting things over the web, and so on. Most of this latter stuff seems to have landed on root-2 for (guessing) historical reasons. Currently, the net-drivers floppy has about 447 K of free space. CD-DRIVERS) The cd-drivers floppy is also a collection of udeb's. It represents everything that is needed to get to the point of being able to load stuff off of a CD-ROM. The largest single file is scsi-modules-2.4.27-powerpc-small-di.udeb, followed closely
No HFS driver, and change install priority menu option missing -- and other bugs found while testing 2.4 boot floppies on OldWorld PowerMac
Package: installation-reports In addition to the already noted problems with 2.4 PowerPC boot floppies, I have two requests for modules to be included on the root or root-2: 1) The change installation priority menu item should be available *very* early in the install process. Best would be immediately after loading the root-2. Currently, it is not available up thru partitioning, at least. 2) The hfs and hfsplus (MacOS filesystem formats) filesystem modules should be available early on. This would make it much easier to save log files to a floppy or a zip disk. Also, they are *required* for support of booting with BootX, so that the kernel and initrd can be copied from /target/boot/ to the appropriate place on the MacOS partition prior to the reboot. For the sake of completeness, here's a list of the other things I've found that currently don't work about the 2.4 powermac boot floppies: 3) Country chooser is called before loading root-2, so it hangs trying to do a grep US on a file that is on root-2, but should be on root. 4) the ofonlyboot floppy never switches to text-mode screen. It reads and ejects the boot floppy. But, since the text mode screen never appears, it's impossible to proceed further. This happens on both my test machines, the beige G3 tower, and the 6500. 5) It never finds my disk. It gets all the way to partitioner without loading either the mesh driver or the driver for my PCI IDE controller card. For the record, I do not have any of these problems with installing via BootX using the latest businesscard CD. Of course, for problems 3 and 4 this is a trivial statement. Also for the record, these problems occur when using the net-drivers floppy. I have not tried to use the CD-drivers floppy. I would consider problems 3 and 5 to be show stoppers. Life would be *much* easier if 1 and 2 were fixed. Since the boot floppy works on my hardware, I consider problem 4 to be lower priority than the rest -- though others, for whom the boot floppy doesn't do the job, may reasonably disagree. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#272310: Floppy install on Oldworld PowerMac G3 tower
Package: installation-reports I tried the PowerMac install floppy set from the 18th Index of /~luther/d-i/images/2004-09-18/powerpc/floppy-2.4 NameLast modified Size Description [DIR] Parent Directory26-Aug-2004 21:35 - [ ] asian-root.img 18-Sep-2004 01:35 1.1M [ ] boot.img18-Sep-2004 01:35 1.4M [ ] cd-drivers.img 18-Sep-2004 01:35 1.4M [ ] net-drivers.img 18-Sep-2004 01:35 1.4M [ ] ofonlyboot.img 18-Sep-2004 01:35 1.4M [ ] root-2.img 18-Sep-2004 01:35 1.4M [ ] root.img18-Sep-2004 01:37 1.2M _ Apache/1.3.26 Server at people.debian.org Port 80 The boot floppy reads OK and calls for the root floppy, which also reads OK. It asks for Language (I gave it English), then the screen started blinking. Switching to the other consoles (opt-F2, -F3, -F4), which are also blinking, so it's hard to get any details, it appears that the /sbin/debian-installer process is crashing and restarting repeatedly. 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
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 return, 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]
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 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 fill a bug report against discover1
Re: No /dev/modem or similar created on PowerPC?
On Friday, September 17, 2004, at 03:12 PM, Joey Hess wrote: Russell Hires wrote: I'm just poking around on my G3/266 and I'm noticing that I don't have a /dev/modem, or any tty that links to it. Does the d-i create such a device only if you say that you want to install via ppp? This could be a problem if, for example, you want to use your modem to output a serial console (which is my situation, actually :-) In fact, I can't find (and neither can kppp) which tty connects to my modem. d-i does not know about modems. I think that pppconfig might set a /dev/modem link if you choose to use it to install via modem in base-config, but in general yes, new installs have no /dev/modem link. Probing for modems is a rather risky business that has been known to turn off UPSes and do other fun stuff, I don't think the installer wants to go there. I don't understand what a modem has to do with a serial console BTW. I think I can clear up a point or two here. OldWorld Macs have two serial RS-232 ports (actually RS-422, but who's counting?) one is marked Printer and the other is marked Modem. In at least some models, the Printer port did not have the RS-232 modem flow-control signals enabled, but the Modem port did -- hence the distinction and the naming convention. Russell is probably *not* talking about using an actual real-live modem. What he's probably talking about is the fact that the Mac Open Firmware sometimes uses the Modem port as a serial console. In order to see the stuff that appears on that line, you need to use a serial cross-over cable (also -- confusingly -- called a null-modem cable) to connect the Modem port to another machine running a terminal emulator (such as macKermit) or an actual real-live terminal from the dark ages. To answer the question Russell is probably asking: The Modem port is called /dev/ttyS0. You didn't ask, and you could probably figure it out for yourself, but just for completeness, the Printer port is called /dev/ttyS1. Note the upper-case S. I've never been able to make it work, but I'm told that when you use kernel boot-time command-line arguments to tell the booting kernel to send it's messages to the serial console port, you should leave off the /dev. Thus: console=ttyS0 Hope this helps! 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: 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#271419: mesh SCSI driver should be loaded by default on OldWorld Powermac
The following is from the installed system, so the mesh driver is installed on this system, unlike the installing system before I manually did modprobe mesh. I don't know if this changes anything. [EMAIL PROTECTED]:~$ ls -l /proc/device-tree total 9 -r--r--r-- 1 root root 4 Sep 13 07:09 #address-cells -r--r--r-- 1 root root 4 Sep 13 07:09 #size-cells dr-xr-xr-x 2 root root 0 Sep 13 07:09 AAPL,ROM -r--r--r-- 1 root root 4 Sep 13 07:09 AAPL,cpu-id -r--r--r-- 1 root root 12 Sep 13 07:09 AAPL,original-name dr-xr-xr-x 2 root root 0 Sep 13 07:09 aliases dr-xr-xr-x 2 root root 0 Sep 13 07:09 chosen -r--r--r-- 1 root root 4 Sep 13 07:09 clock-frequency -r--r--r-- 1 root root 22 Sep 13 07:09 compatible dr-xr-xr-x 3 root root 0 Sep 13 07:09 cpus dr-xr-xr-x 2 root root 0 Sep 13 07:09 memory -r--r--r-- 1 root root 16 Sep 13 07:09 model -r--r--r-- 1 root root 12 Sep 13 07:09 name dr-xr-xr-x 2 root root 0 Sep 13 07:09 offscreen-display dr-xr-xr-x 2 root root 0 Sep 13 07:09 openprom dr-xr-xr-x 2 root root 0 Sep 13 07:09 options dr-xr-xr-x 12 root root 0 Sep 13 07:09 packages dr-xr-xr-x 7 root root 0 Sep 13 07:09 pci -r--r--r-- 1 root root 256 Sep 13 07:09 pci-OF-bus-map dr-xr-xr-x 2 root root 0 Sep 13 07:09 perch [EMAIL PROTECTED]:~$ for i in $( find /proc/device-tree/ -type f | xargs grep -l mesh ); do ls -ld $i; cat -v $i; echo; done -r--r--r-- 1 root root 17 Sep 13 07:09 /proc/device-tree/aliases/scsi /pci/mac-io/mesh^@ -r--r--r-- 1 root root 17 Sep 13 07:09 /proc/device- tree/aliases/scsi-int /pci/mac-io/mesh^@ -r--r--r-- 1 root root 5 Sep 13 07:09 /proc/device-tree/pci/mac- io/mesh/name mesh^@ -r--r--r-- 1 root root 5 Sep 13 07:09 /proc/device-tree/pci/mac- io/mesh/compatible mesh^@ [EMAIL PROTECTED]:~$ Enjoy! Rick On Monday, September 13, 2004, at 06:36 AM, Colin Watson wrote: On Mon, Sep 13, 2004 at 12:45:00AM -0400, Rick Thomas wrote: Note 1: This machine has a SCSI Zip drive is on the apple mesh scsi controller. Before the discover disks phase, I had to go to the F2 console and manually modprobe mesh to get it to recognize the Zip disk. Because the mesh driver module was loaded behind d-i's back (so to speak), d-i didn't know about it, and as a result, mesh wasn't carried forward to /etc/modules after the reboot. (see note 3) Many (most?) oldworld PowerMac's have the mesh scsi controller as their *only* (and in any case *primary*) mass-storage interface. Failure to load the mesh driver module will make it impossible for inexperienced users to install Debian on their machines. It seems to me that the mesh driver should be loaded by default on *all* oldworld PowerMac machines. The problem is made more complicated because the mesh chip is on the motherboard, and so doesn't show up in the output of lspci. This only strengthens the argument for loading the mesh driver by default. Not necessarily. Does it show up in the mac-io bus? Send me a tarball of /proc/device-tree if you aren't sure. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#271419: mesh SCSI driver should be loaded by default on OldWorld Powermac
Thanks! I await the fix with baited breath... (Like the cat beside the mouse hole. -8) Enjoy! Rick On Monday, September 13, 2004, at 07:49 AM, Colin Watson wrote: reassign 271419 hw-detect tags 271419 pending thanks On Mon, Sep 13, 2004 at 07:15:17AM -0400, Rick Thomas wrote: The following is from the installed system, so the mesh driver is installed on this system, unlike the installing system before I manually did modprobe mesh. I don't know if this changes anything. /proc/device-tree is exported straight from the firmware; the set of drivers you have loaded doesn't matter. [EMAIL PROTECTED]:~$ for i in $( find /proc/device-tree/ -type f | xargs grep -l mesh ); do ls -ld $i; cat -v $i; echo; done -r--r--r-- 1 root root 17 Sep 13 07:09 /proc/device-tree/aliases/scsi /pci/mac-io/mesh^@ -r--r--r-- 1 root root 17 Sep 13 07:09 /proc/device- tree/aliases/scsi-int /pci/mac-io/mesh^@ -r--r--r-- 1 root root 5 Sep 13 07:09 /proc/device-tree/pci/mac- io/mesh/name mesh^@ -r--r--r-- 1 root root 5 Sep 13 07:09 /proc/device-tree/pci/mac- io/mesh/compatible mesh^@ [EMAIL PROTECTED]:~$ A fix to autodetect this hardware is in my local tree now waiting for the Subversion repository to come back up. Thanks, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Floppy install on Oldworld PowerMac
On Friday, September 10, 2004, at 05:04 PM, Rick Thomas wrote: The ofonlyboot has not changed. It reads and inverts the colors of the tuxmac, but never switches to text-mode screen from the inverted color tuxmac. The boot floppy reads and switches to the text screen then asks for the root floppy, which it reads. It then asks for language (English) and location (US) (but not keyboard layout) then invites me to load drivers from a floppy. I gave it the root-2 floppy and it complained about not being able to find any kernel drivers on that floppy. I chose go back and re-executed load drivers from a floppy. This time I gave it the net-drivers floppy, and it was happy. Still thinking that we wouldn't get any where without the root-2 floppy loading (and being a bit bull headed anyway) I tried load drivers from floppy for the third time, and again fed it the root-2. It complained again about not finding any kernel modules. This time I told it to continue without loading drivers and to my amazement, it started decoding the stuff from the root-2 floppy! Curioser and curioser! I think it was at this point that it asked for my keyboard layout, and suggested European as default, even though I had given it every reason to suspect that US-English was my preferred locale. I've reported this violation of the principle of least astonishment before. It proceeded then to find my ethernet interface (remember I'd loaded the net-drivers floppy earlier) and do DHCP discovery on it. This succeeded, as expected. When it asked, I chose the uchicago mirror as usual, and it loaded the installer-components list (I think -- I didn't get the exact words) after which it *again* complained about not finding any kernel modules! I told it to continue anyway, and it started downloading and unpacking installer components from the uchicago mirror (presumably). When it got done with that and moved on to the partitioner, it couldn't find any of my disks (not my IDE main disk or my SCSI Zip disk). The only IDE think it knew about was the CD-ROM drive. Exploring on the F2 console showed that it wasn't just the partitioner that was confused. There was no evidence of IDE or SCSI disks in /proc or /dev. (Same as last time -- no progress on that front...) So I wrapped it up and took a tea break to write this report. I have to consider the check for kernel modules at inappropriate times to be a serious bug... I tried again with the latest floppies: Index of /~luther/d-i/images/daily/powerpc/floppy-2.4 NameLast modified Size Description Parent Directory26-Aug-2004 21:35 - asian-root.img 13-Sep-2004 03:16 1.2M boot.img13-Sep-2004 03:17 1.4M cd-drivers.img 13-Sep-2004 03:17 1.4M net-drivers.img 13-Sep-2004 03:17 1.4M ofonlyboot.img 13-Sep-2004 03:17 1.4M root-2.img 13-Sep-2004 03:17 1.4M root.img13-Sep-2004 03:18 1.3M Apache/1.3.26 Server at people.debian.org Port 80 No change. 1) The ofonlyboot still doesn't give me a text screen. 2) Loading the root-2 floppy still gives me an error message about not finding any driver modules, which I ignore and it loads the root-2 floppy anyway. 3) No reasonable combination of choice of mirrors (ftp.us.debian.org vs debian.uchicago.edu) and distributions (testing vs unstable) give me anything but no disks found. 4) For what it's worth, at least one combination of mirror and distro (I don't remember exactly which -- I *think* it was uchicago and testing) complained about not being able to find any driver modules (presumably) on the mirror. But the other combinations didn't complain. (So maybe the uchicago unstable distro does have driver modules for the 2.4.27 kernel, but their testing doesn't... Does that make sense? Is there any way to check this?) 5) Two of the 2.6 floppy images are still too large to fit on a physical 1.44 MB disk. Any thoughts? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Floppy install on Oldworld PowerMac
On Thursday, September 9, 2004, at 01:23 PM, Sven Luther wrote: On Thu, Sep 09, 2004 at 12:45:29PM -0400, Rick Thomas wrote: Ummm... The contents of http://people.debian.org/~luther/d-i/images/daily/powerpc/floppy-2.4/ haven't changed in the last few days. Is the build process stalled somewhere? [DIR] 2004-09-08_RSYNC_IN_PROGRESS/ 07-Sep-2004 22:05 - [DIR] 2004-09-09_RSYNC_IN_PROGRESS/ 08-Sep-2004 22:05 - Hmmm.. It seems to be doing it again... 2004-09-11/ 10-Sep-2004 23:13 - 2004-09-12_RSYNC_IN_PROGRESS/ 11-Sep-2004 22:05 - daily/10-Sep-2004 23:13 - It's been this way for over an hour... Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: HELP: Failed powerpc autobuild upload again, p.d.o is rejecting my rsync.
Then it's probably not a hardware problem. On Sunday, September 12, 2004, at 06:00 AM, Sven Luther wrote: On Sun, Sep 12, 2004 at 05:10:53AM -0400, Rick_Thomas wrote: On Sun, 2004-09-12 at 03:06, Sven Luther wrote: Here is the error in my log : powerpc/netboot/2.4/vmlinuz-chrp.initrd powerpc/netboot/2.4/vmlinuz-prep.initrd Read from remote host people.debian.org: Connection reset by peer rsync: writefd_unbuffered failed to write 4 bytes: phase unknown: Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(839) Sun Sep 12 05:28:26 UTC 2004 Anyone has an idea on what is going on ? Whenever I've seen error messages similar to those, it's been because an ethernet interface has gotten confused. Usually rebooting the relevant machine clears it up (but sometimes only for a while.) If it comes back after a reboot, it's likely a sign that the interface hardware is failing and should be replaced. Err, the box in question is always online, gets my mail and host my irc client under screen. I am thus continously connected to it or something, and i don't see any failure in it. Furthermore, if i do the upload by hand, it always seems to work. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#271417: Select keyboard defaults to European when American English is expected on OldWorld PowerPC
Package: installation-reports powerpc BootX 20040911 businesscard OldWorld PowerMac See Note 2 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 12-Sep-2004 00:13 - MD5SUMS12-Sep-2004 00:13 1k sarge-powerpc-businesscard.iso 12-Sep-2004 00:07 140M sarge-powerpc-netinst.iso 12-Sep-2004 00:13 297M Apache/1.3.31 Server at cdimage.debian.org Port 80 uname -a: The result of running uname -a on a shell prompt Linux debian 2.6.8-powerpc #1 Fri Aug 27 18:02:26 CEST 2004 ppc GNU/Linux Date: Date and time of the install 3:00 AM US East Coast time Sept 12, 2004 Method: How did you install? What did you boot off? If network install, from where? Proxied? MacOS BootX using the 2.6 kernel and initrd.gz from the install/powerpc folder on the indicated businesscard CD image with an assist from the uchicago testing mirror Machine: Description of machine (eg, IBM Thinkpad R32) PowerMac G3/300 MHz Processor: processor : 0 cpu : 740/750 temperature : 36-41 C (uncalibrated) clock : 300MHz revision: 2.2 (pvr 0008 0202) bogomips: 601.29 machine : Power Macintosh motherboard : AAPL,Gossamer MacRISC detected as : 48 (PowerMac G3 (Gossamer)) pmac flags : L2 cache: 1024K unified pipelined-syncro-burst memory : 384MB pmac-generation : OldWorld Memory: 384 MB Root Device: IDE? SCSI? Name of device? root is on /dev/hdg10. Swap is on /dev/hdg8. macOS is on /dev/hdg6 /dev/hdg #type name length base ( size ) system /dev/hdg1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hdg2 Apple_Driver43 Macintosh 54 @ 64( 27.0k) Driver 4.3 /dev/hdg3 Apple_Driver43 Macintosh 74 @ 118 ( 37.0k) Driver 4.3 /dev/hdg4 Apple_Driver_IOKit Macintosh512 @ 192 (256.0k) Unknown /dev/hdg5 Apple_Patches Patch Partition 512 @ 704 (256.0k) Unknown /dev/hdg6 Apple_HFS untitled 2097152 @ 1216 ( 1.0G) HFS /dev/hdg7 Apple_UNIX_SVR2 root19531251 @ 2098368 ( 9.3G) Linux native /dev/hdg8 Apple_UNIX_SVR2 swap 1953126 @ 21629619 (953.7M) Linux swap /dev/hdg9 Apple_UNIX_SVR2 root19531251 @ 23582745 ( 9.3G) Linux native /dev/hdg10Apple_UNIX_SVR2 Root-10 5859376 @ 43113996 ( 2.8G) Linux native /dev/hdg11 Apple_Free Extra 52734377 @ 48973372 ( 25.1G) Free space /dev/hdg12 Apple_Free Extra 113607707 @ 206565349 ( 54.2G) Free space /dev/hdg13Apple_UNIX_SVR2 SuZq 104857600 @ 101707749 ( 50.0G) Linux native Block size=512, Number of Blocks=320173056 DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 23, type=0x1 2: @ 118 for 36, type=0x Root Size/partition table: Feel free to paste the full partition table, with notes on which partitions are mounted where. 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 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] =
Bug#271418: After reboot wrong ethernet interface is primary on Oldworld PowerPC Macintosh
Package: installation-reports powerpc BootX 20040911 businesscard OldWorld PowerMac See note 3 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 12-Sep-2004 00:13 - MD5SUMS12-Sep-2004 00:13 1k sarge-powerpc-businesscard.iso 12-Sep-2004 00:07 140M sarge-powerpc-netinst.iso 12-Sep-2004 00:13 297M Apache/1.3.31 Server at cdimage.debian.org Port 80 uname -a: The result of running uname -a on a shell prompt Linux debian 2.6.8-powerpc #1 Fri Aug 27 18:02:26 CEST 2004 ppc GNU/Linux Date: Date and time of the install 3:00 AM US East Coast time Sept 12, 2004 Method: How did you install? What did you boot off? If network install, from where? Proxied? MacOS BootX using the 2.6 kernel and initrd.gz from the install/powerpc folder on the indicated businesscard CD image with an assist from the uchicago testing mirror Machine: Description of machine (eg, IBM Thinkpad R32) PowerMac G3/300 MHz Processor: processor : 0 cpu : 740/750 temperature : 36-41 C (uncalibrated) clock : 300MHz revision: 2.2 (pvr 0008 0202) bogomips: 601.29 machine : Power Macintosh motherboard : AAPL,Gossamer MacRISC detected as : 48 (PowerMac G3 (Gossamer)) pmac flags : L2 cache: 1024K unified pipelined-syncro-burst memory : 384MB pmac-generation : OldWorld Memory: 384 MB Root Device: IDE? SCSI? Name of device? root is on /dev/hdg10. Swap is on /dev/hdg8. macOS is on /dev/hdg6 /dev/hdg #type name length base ( size ) system /dev/hdg1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hdg2 Apple_Driver43 Macintosh 54 @ 64( 27.0k) Driver 4.3 /dev/hdg3 Apple_Driver43 Macintosh 74 @ 118 ( 37.0k) Driver 4.3 /dev/hdg4 Apple_Driver_IOKit Macintosh512 @ 192 (256.0k) Unknown /dev/hdg5 Apple_Patches Patch Partition 512 @ 704 (256.0k) Unknown /dev/hdg6 Apple_HFS untitled 2097152 @ 1216 ( 1.0G) HFS /dev/hdg7 Apple_UNIX_SVR2 root19531251 @ 2098368 ( 9.3G) Linux native /dev/hdg8 Apple_UNIX_SVR2 swap 1953126 @ 21629619 (953.7M) Linux swap /dev/hdg9 Apple_UNIX_SVR2 root19531251 @ 23582745 ( 9.3G) Linux native /dev/hdg10Apple_UNIX_SVR2 Root-10 5859376 @ 43113996 ( 2.8G) Linux native /dev/hdg11 Apple_Free Extra 52734377 @ 48973372 ( 25.1G) Free space /dev/hdg12 Apple_Free Extra 113607707 @ 206565349 ( 54.2G) Free space /dev/hdg13Apple_UNIX_SVR2 SuZq 104857600 @ 101707749 ( 50.0G) Linux native Block size=512, Number of Blocks=320173056 DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 23, type=0x1 2: @ 118 for 36, type=0x Root Size/partition table: Feel free to paste the full partition table, with notes on which partitions are mounted where. 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 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] =
Bug#271419: mesh SCSI driver should be loaded by default on OldWorld Powermac
Package: installation-reports powerpc BootX 20040911 businesscard OldWorld PowerMac See Note 1 below... 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 12-Sep-2004 00:13 - MD5SUMS12-Sep-2004 00:13 1k sarge-powerpc-businesscard.iso 12-Sep-2004 00:07 140M sarge-powerpc-netinst.iso 12-Sep-2004 00:13 297M Apache/1.3.31 Server at cdimage.debian.org Port 80 uname -a: The result of running uname -a on a shell prompt Linux debian 2.6.8-powerpc #1 Fri Aug 27 18:02:26 CEST 2004 ppc GNU/Linux Date: Date and time of the install 3:00 AM US East Coast time Sept 12, 2004 Method: How did you install? What did you boot off? If network install, from where? Proxied? MacOS BootX using the 2.6 kernel and initrd.gz from the install/powerpc folder on the indicated businesscard CD image with an assist from the uchicago testing mirror Machine: Description of machine (eg, IBM Thinkpad R32) PowerMac G3/300 MHz Processor: processor : 0 cpu : 740/750 temperature : 36-41 C (uncalibrated) clock : 300MHz revision: 2.2 (pvr 0008 0202) bogomips: 601.29 machine : Power Macintosh motherboard : AAPL,Gossamer MacRISC detected as : 48 (PowerMac G3 (Gossamer)) pmac flags : L2 cache: 1024K unified pipelined-syncro-burst memory : 384MB pmac-generation : OldWorld Memory: 384 MB Root Device: IDE? SCSI? Name of device? root is on /dev/hdg10. Swap is on /dev/hdg8. macOS is on /dev/hdg6 /dev/hdg #type name length base ( size ) system /dev/hdg1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hdg2 Apple_Driver43 Macintosh 54 @ 64( 27.0k) Driver 4.3 /dev/hdg3 Apple_Driver43 Macintosh 74 @ 118 ( 37.0k) Driver 4.3 /dev/hdg4 Apple_Driver_IOKit Macintosh512 @ 192 (256.0k) Unknown /dev/hdg5 Apple_Patches Patch Partition 512 @ 704 (256.0k) Unknown /dev/hdg6 Apple_HFS untitled 2097152 @ 1216 ( 1.0G) HFS /dev/hdg7 Apple_UNIX_SVR2 root19531251 @ 2098368 ( 9.3G) Linux native /dev/hdg8 Apple_UNIX_SVR2 swap 1953126 @ 21629619 (953.7M) Linux swap /dev/hdg9 Apple_UNIX_SVR2 root19531251 @ 23582745 ( 9.3G) Linux native /dev/hdg10Apple_UNIX_SVR2 Root-10 5859376 @ 43113996 ( 2.8G) Linux native /dev/hdg11 Apple_Free Extra 52734377 @ 48973372 ( 25.1G) Free space /dev/hdg12 Apple_Free Extra 113607707 @ 206565349 ( 54.2G) Free space /dev/hdg13Apple_UNIX_SVR2 SuZq 104857600 @ 101707749 ( 50.0G) Linux native Block size=512, Number of Blocks=320173056 DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 23, type=0x1 2: @ 118 for 36, type=0x Root Size/partition table: Feel free to paste the full partition table, with notes on which partitions are mounted where. 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 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [
Bug#271421: Printserver task setup defaults to a4 paper when letter is expected.
Package: installation-reports powerpc BootX 20040911 businesscard OldWorld PowerMac see note 5 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 12-Sep-2004 00:13 - MD5SUMS12-Sep-2004 00:13 1k sarge-powerpc-businesscard.iso 12-Sep-2004 00:07 140M sarge-powerpc-netinst.iso 12-Sep-2004 00:13 297M Apache/1.3.31 Server at cdimage.debian.org Port 80 uname -a: The result of running uname -a on a shell prompt Linux debian 2.6.8-powerpc #1 Fri Aug 27 18:02:26 CEST 2004 ppc GNU/Linux Date: Date and time of the install 3:00 AM US East Coast time Sept 12, 2004 Method: How did you install? What did you boot off? If network install, from where? Proxied? MacOS BootX using the 2.6 kernel and initrd.gz from the install/powerpc folder on the indicated businesscard CD image with an assist from the uchicago testing mirror Machine: Description of machine (eg, IBM Thinkpad R32) PowerMac G3/300 MHz Processor: processor : 0 cpu : 740/750 temperature : 36-41 C (uncalibrated) clock : 300MHz revision: 2.2 (pvr 0008 0202) bogomips: 601.29 machine : Power Macintosh motherboard : AAPL,Gossamer MacRISC detected as : 48 (PowerMac G3 (Gossamer)) pmac flags : L2 cache: 1024K unified pipelined-syncro-burst memory : 384MB pmac-generation : OldWorld Memory: 384 MB Root Device: IDE? SCSI? Name of device? root is on /dev/hdg10. Swap is on /dev/hdg8. macOS is on /dev/hdg6 /dev/hdg #type name length base ( size ) system /dev/hdg1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hdg2 Apple_Driver43 Macintosh 54 @ 64( 27.0k) Driver 4.3 /dev/hdg3 Apple_Driver43 Macintosh 74 @ 118 ( 37.0k) Driver 4.3 /dev/hdg4 Apple_Driver_IOKit Macintosh512 @ 192 (256.0k) Unknown /dev/hdg5 Apple_Patches Patch Partition 512 @ 704 (256.0k) Unknown /dev/hdg6 Apple_HFS untitled 2097152 @ 1216 ( 1.0G) HFS /dev/hdg7 Apple_UNIX_SVR2 root19531251 @ 2098368 ( 9.3G) Linux native /dev/hdg8 Apple_UNIX_SVR2 swap 1953126 @ 21629619 (953.7M) Linux swap /dev/hdg9 Apple_UNIX_SVR2 root19531251 @ 23582745 ( 9.3G) Linux native /dev/hdg10Apple_UNIX_SVR2 Root-10 5859376 @ 43113996 ( 2.8G) Linux native /dev/hdg11 Apple_Free Extra 52734377 @ 48973372 ( 25.1G) Free space /dev/hdg12 Apple_Free Extra 113607707 @ 206565349 ( 54.2G) Free space /dev/hdg13Apple_UNIX_SVR2 SuZq 104857600 @ 101707749 ( 50.0G) Linux native Block size=512, Number of Blocks=320173056 DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 23, type=0x1 2: @ 118 for 36, type=0x Root Size/partition table: Feel free to paste the full partition table, with notes on which partitions are mounted where. 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 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] =
Bug#271420: Default kernel image is 2.6.7 -- should be 2.6.8 -- on OldWorld PowerPC Mac
Package: installation-reports powerpc BootX 20040911 businesscard OldWorld PowerMac See note 4 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 12-Sep-2004 00:13 - MD5SUMS12-Sep-2004 00:13 1k sarge-powerpc-businesscard.iso 12-Sep-2004 00:07 140M sarge-powerpc-netinst.iso 12-Sep-2004 00:13 297M Apache/1.3.31 Server at cdimage.debian.org Port 80 uname -a: The result of running uname -a on a shell prompt Linux debian 2.6.8-powerpc #1 Fri Aug 27 18:02:26 CEST 2004 ppc GNU/Linux Date: Date and time of the install 3:00 AM US East Coast time Sept 12, 2004 Method: How did you install? What did you boot off? If network install, from where? Proxied? MacOS BootX using the 2.6 kernel and initrd.gz from the install/powerpc folder on the indicated businesscard CD image with an assist from the uchicago testing mirror Machine: Description of machine (eg, IBM Thinkpad R32) PowerMac G3/300 MHz Processor: processor : 0 cpu : 740/750 temperature : 36-41 C (uncalibrated) clock : 300MHz revision: 2.2 (pvr 0008 0202) bogomips: 601.29 machine : Power Macintosh motherboard : AAPL,Gossamer MacRISC detected as : 48 (PowerMac G3 (Gossamer)) pmac flags : L2 cache: 1024K unified pipelined-syncro-burst memory : 384MB pmac-generation : OldWorld Memory: 384 MB Root Device: IDE? SCSI? Name of device? root is on /dev/hdg10. Swap is on /dev/hdg8. macOS is on /dev/hdg6 /dev/hdg #type name length base ( size ) system /dev/hdg1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hdg2 Apple_Driver43 Macintosh 54 @ 64( 27.0k) Driver 4.3 /dev/hdg3 Apple_Driver43 Macintosh 74 @ 118 ( 37.0k) Driver 4.3 /dev/hdg4 Apple_Driver_IOKit Macintosh512 @ 192 (256.0k) Unknown /dev/hdg5 Apple_Patches Patch Partition 512 @ 704 (256.0k) Unknown /dev/hdg6 Apple_HFS untitled 2097152 @ 1216 ( 1.0G) HFS /dev/hdg7 Apple_UNIX_SVR2 root19531251 @ 2098368 ( 9.3G) Linux native /dev/hdg8 Apple_UNIX_SVR2 swap 1953126 @ 21629619 (953.7M) Linux swap /dev/hdg9 Apple_UNIX_SVR2 root19531251 @ 23582745 ( 9.3G) Linux native /dev/hdg10Apple_UNIX_SVR2 Root-10 5859376 @ 43113996 ( 2.8G) Linux native /dev/hdg11 Apple_Free Extra 52734377 @ 48973372 ( 25.1G) Free space /dev/hdg12 Apple_Free Extra 113607707 @ 206565349 ( 54.2G) Free space /dev/hdg13Apple_UNIX_SVR2 SuZq 104857600 @ 101707749 ( 50.0G) Linux native Block size=512, Number of Blocks=320173056 DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 23, type=0x1 2: @ 118 for 36, type=0x Root Size/partition table: Feel free to paste the full partition table, with notes on which partitions are mounted where. 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 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] =
Bug#271423: Floppy driver not loaded during install process on OldWorld PowerPC Macs
Package: installation-reports powerpc BootX 20040911 businesscard OldWorld PowerMac see note 6 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 12-Sep-2004 00:13 - MD5SUMS12-Sep-2004 00:13 1k sarge-powerpc-businesscard.iso 12-Sep-2004 00:07 140M sarge-powerpc-netinst.iso 12-Sep-2004 00:13 297M Apache/1.3.31 Server at cdimage.debian.org Port 80 uname -a: The result of running uname -a on a shell prompt Linux debian 2.6.8-powerpc #1 Fri Aug 27 18:02:26 CEST 2004 ppc GNU/Linux Date: Date and time of the install 3:00 AM US East Coast time Sept 12, 2004 Method: How did you install? What did you boot off? If network install, from where? Proxied? MacOS BootX using the 2.6 kernel and initrd.gz from the install/powerpc folder on the indicated businesscard CD image with an assist from the uchicago testing mirror Machine: Description of machine (eg, IBM Thinkpad R32) PowerMac G3/300 MHz Processor: processor : 0 cpu : 740/750 temperature : 36-41 C (uncalibrated) clock : 300MHz revision: 2.2 (pvr 0008 0202) bogomips: 601.29 machine : Power Macintosh motherboard : AAPL,Gossamer MacRISC detected as : 48 (PowerMac G3 (Gossamer)) pmac flags : L2 cache: 1024K unified pipelined-syncro-burst memory : 384MB pmac-generation : OldWorld Memory: 384 MB Root Device: IDE? SCSI? Name of device? root is on /dev/hdg10. Swap is on /dev/hdg8. macOS is on /dev/hdg6 /dev/hdg #type name length base ( size ) system /dev/hdg1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hdg2 Apple_Driver43 Macintosh 54 @ 64( 27.0k) Driver 4.3 /dev/hdg3 Apple_Driver43 Macintosh 74 @ 118 ( 37.0k) Driver 4.3 /dev/hdg4 Apple_Driver_IOKit Macintosh512 @ 192 (256.0k) Unknown /dev/hdg5 Apple_Patches Patch Partition 512 @ 704 (256.0k) Unknown /dev/hdg6 Apple_HFS untitled 2097152 @ 1216 ( 1.0G) HFS /dev/hdg7 Apple_UNIX_SVR2 root19531251 @ 2098368 ( 9.3G) Linux native /dev/hdg8 Apple_UNIX_SVR2 swap 1953126 @ 21629619 (953.7M) Linux swap /dev/hdg9 Apple_UNIX_SVR2 root19531251 @ 23582745 ( 9.3G) Linux native /dev/hdg10Apple_UNIX_SVR2 Root-10 5859376 @ 43113996 ( 2.8G) Linux native /dev/hdg11 Apple_Free Extra 52734377 @ 48973372 ( 25.1G) Free space /dev/hdg12 Apple_Free Extra 113607707 @ 206565349 ( 54.2G) Free space /dev/hdg13Apple_UNIX_SVR2 SuZq 104857600 @ 101707749 ( 50.0G) Linux native Block size=512, Number of Blocks=320173056 DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 23, type=0x1 2: @ 118 for 36, type=0x Root Size/partition table: Feel free to paste the full partition table, with notes on which partitions are mounted where. 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 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] =
Bug#271424: Partitioner is checking active swap files!!!
Package: installation-reports powerpc BootX 20040911 businesscard OldWorld PowerMac See note 7 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 12-Sep-2004 00:13 - MD5SUMS12-Sep-2004 00:13 1k sarge-powerpc-businesscard.iso 12-Sep-2004 00:07 140M sarge-powerpc-netinst.iso 12-Sep-2004 00:13 297M Apache/1.3.31 Server at cdimage.debian.org Port 80 uname -a: The result of running uname -a on a shell prompt Linux debian 2.6.8-powerpc #1 Fri Aug 27 18:02:26 CEST 2004 ppc GNU/Linux Date: Date and time of the install 3:00 AM US East Coast time Sept 12, 2004 Method: How did you install? What did you boot off? If network install, from where? Proxied? MacOS BootX using the 2.6 kernel and initrd.gz from the install/powerpc folder on the indicated businesscard CD image with an assist from the uchicago testing mirror Machine: Description of machine (eg, IBM Thinkpad R32) PowerMac G3/300 MHz Processor: processor : 0 cpu : 740/750 temperature : 36-41 C (uncalibrated) clock : 300MHz revision: 2.2 (pvr 0008 0202) bogomips: 601.29 machine : Power Macintosh motherboard : AAPL,Gossamer MacRISC detected as : 48 (PowerMac G3 (Gossamer)) pmac flags : L2 cache: 1024K unified pipelined-syncro-burst memory : 384MB pmac-generation : OldWorld Memory: 384 MB Root Device: IDE? SCSI? Name of device? root is on /dev/hdg10. Swap is on /dev/hdg8. macOS is on /dev/hdg6 /dev/hdg #type name length base ( size ) system /dev/hdg1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hdg2 Apple_Driver43 Macintosh 54 @ 64( 27.0k) Driver 4.3 /dev/hdg3 Apple_Driver43 Macintosh 74 @ 118 ( 37.0k) Driver 4.3 /dev/hdg4 Apple_Driver_IOKit Macintosh512 @ 192 (256.0k) Unknown /dev/hdg5 Apple_Patches Patch Partition 512 @ 704 (256.0k) Unknown /dev/hdg6 Apple_HFS untitled 2097152 @ 1216 ( 1.0G) HFS /dev/hdg7 Apple_UNIX_SVR2 root19531251 @ 2098368 ( 9.3G) Linux native /dev/hdg8 Apple_UNIX_SVR2 swap 1953126 @ 21629619 (953.7M) Linux swap /dev/hdg9 Apple_UNIX_SVR2 root19531251 @ 23582745 ( 9.3G) Linux native /dev/hdg10Apple_UNIX_SVR2 Root-10 5859376 @ 43113996 ( 2.8G) Linux native /dev/hdg11 Apple_Free Extra 52734377 @ 48973372 ( 25.1G) Free space /dev/hdg12 Apple_Free Extra 113607707 @ 206565349 ( 54.2G) Free space /dev/hdg13Apple_UNIX_SVR2 SuZq 104857600 @ 101707749 ( 50.0G) Linux native Block size=512, Number of Blocks=320173056 DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 23, type=0x1 2: @ 118 for 36, type=0x Root Size/partition table: Feel free to paste the full partition table, with notes on which partitions are mounted where. 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 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] =
Bug#270599: Floppy install on Oldworld PowerMac
On Saturday, September 11, 2004, at 07:11 AM, Russell Hires wrote: P.S. jokingWhen are you finally going to start work on the manual?/joking All joking aside... That is an important task! But I kinda figured it was less important than getting the software working at all on oldworld hardware, since I seem to be the only one on the list who has oldworld pmac hardware available for testing. If there were someone else who could do the testing part, I'd have time to work on the documentation part... Any takers out there? Rick I've offered my services before in writing up some docs (or simply modifying the woody ones to fit the sarge install) in a couple of previous threads. Meanwhile, I'm running on a G3/266 that I'd be willing to test with. Also, I need help with setting my G3 to send output to a serial console, since the 2.6.x kernels don't give my voodoo3 card any console data. Russell OK Russell, you're on! Here's what you need to do: First, google a bit to find and get copies of the distribution files for BootX, miboot, and quik -- the three boot-loaders that work on OldWorld PowerMacs. Read and try to understand the documentation that comes with the package distributions. Most of it is sketchy, but if you combine it with more googling for stuff in the various mailinglist archives (debian and YellowDog Linux, in particular, but also the PowerPC Linux mailing list and any other distros that support PowerPC, such as SuSE and Fedora) and there's useful (if anecdotal) stuff in several people's personal home web pages as well. Retrieve and read the Apple Tech notes on Open Firmware. Start with TN1061 and follow pointers from there. There's also lots of useful stuff on the web. Google for Open Firmware Apple macintosh. There are also some very useful docs about using OpenFirmware with NetBSD. If you're really dedicated, the first stage should take you a couple of weeks. Second, partition your disk so that you have plenty of free space to install test releases of Debian into. Each installation takes a minimum of about 1.5 GB -- more if you want to make it actually useful. So multiply 2-3 GB by the maximum number of test installations you intend to make before you wipe the disk and start over clean. On that disk (or another one dedicated to the purpose) also set up an HFS partition (*not* HFS-plus -- Debian does not at this time support access to HFS-plus filesystems from inside the installer) of about 1 GB (more if you want it to be actually useful other than as an intermediate boot loader. If you're going to run Toast here, you should allow plenty of space [gigabytes] for CD-images). Install MacOS-9 there. Then install BootX (both the BootX extension and the BootX.app application) according to the instructions you got with the BootX distribution. MacOS-X does not support BootX. (Unfortunately, part of the MacOS_X boot loader is called bootx. It's not related to the one we are interested in here.) Third, download the latest d-i businesscard iso, and burn it (I use Toast) to a CD-RW (don't waste a CD-R on it -- you're probably only going to use it a couple of times at most). Copy the kernel of your choice from the CD (install:powerpc:vmlinux or install:powerpc:2.4:vmlinux) into the System Folder:Linux Kernels folder of your MacOS-9 partition, and the initrd.gz file from the same place to the System Folder:Linux Ramdisks folder. Invoke BootX.app, set the appropriate parameters and let her rip. Answer the questions and file an installation report. Dig out my previous d-i installation reports for OldWorld PowerPC installations from the mailing list archives. They may give you some useful hints. Fourth, try a floppy disk install. Contact Sven for instructions on where to download the latest floppy images. Let it try to install the quik bootloader, and see if you can figure out how to make that work. If you succeed in this, let me know. I haven't gotten this far yet. When you're completely familiar with all the various aspects of booting, you can start on re-writing a D-I on OldWorld installation manual. Contact me if you have questions at any point. I've left out a massive amount of detail! Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Floppy install on Oldworld PowerMac
On Thursday, September 9, 2004, at 12:45 PM, Rick Thomas wrote: On Wednesday, September 8, 2004, at 09:18 AM, Rick Thomas wrote: On Wednesday, September 8, 2004, at 05:18 AM, Sven Luther wrote: Please try again with todays floppies, and if it doesn't fix the problem, we need to investigate what driver is missing or something. I'll try the new floppies tonight. I guess whatever it was is fixed now. Because I was able to download a set of floppies from Index of /~luther/d-i/images/daily/powerpc/floppy-2.4 NameLast modified Size Description Parent Directory26-Aug-2004 21:35 - asian-root.img 10-Sep-2004 05:46 1.2M boot.img10-Sep-2004 05:47 1.4M cd-drivers.img 10-Sep-2004 05:49 1.4M net-drivers.img 10-Sep-2004 05:50 1.4M ofonlyboot.img 10-Sep-2004 05:51 1.4M root-2.img 10-Sep-2004 05:52 1.4M root.img10-Sep-2004 05:53 1.3M Apache/1.3.26 Server at people.debian.org Port 80 The ofonlyboot has not changed. It reads and inverts the colors of the tuxmac, but never switches to text-mode screen from the inverted color tuxmac. The boot floppy reads and switches to the text screen then asks for the root floppy, which it reads. It then asks for language (English) and location (US) (but not keyboard layout) then invites me to load drivers from a floppy. I gave it the root-2 floppy and it complained about not being able to find any kernel drivers on that floppy. I chose go back and re-executed load drivers from a floppy. This time I gave it the net-drivers floppy, and it was happy. Still thinking that we wouldn't get any where without the root-2 floppy loading (and being a bit bull headed anyway) I tried load drivers from floppy for the third time, and again fed it the root-2. It complained again about not finding any kernel modules. This time I told it to continue without loading drivers and to my amazement, it started decoding the stuff from the root-2 floppy! Curioser and curioser! I think it was at this point that it asked for my keyboard layout, and suggested European as default, even though I had given it every reason to suspect that US-English was my preferred locale. I've reported this violation of the principle of least astonishment before. It proceeded then to find my ethernet interface (remember I'd loaded the net-drivers floppy earlier) and do DHCP discovery on it. This succeeded, as expected. When it asked, I chose the uchicago mirror as usual, and it loaded the installer-components list (I think -- I didn't get the exact words) after which it *again* complained about not finding any kernel modules! I told it to continue anyway, and it started downloading and unpacking installer components from the uchicago mirror (presumably). When it got done with that and moved on to the partitioner, it couldn't find any of my disks (not my IDE main disk or my SCSI Zip disk). The only IDE think it knew about was the CD-ROM drive. Exploring on the F2 console showed that it wasn't just the partitioner that was confused. There was no evidence of IDE or SCSI disks in /proc or /dev. (Same as last time -- no progress on that front...) So I wrapped it up and took a tea break to write this report. I have to consider the check for kernel modules at inappropriate times to be a serious bug... Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Floppy install on Oldworld PowerMac
On Wednesday, September 8, 2004, at 09:18 AM, Rick Thomas wrote: On Wednesday, September 8, 2004, at 05:18 AM, Sven Luther wrote: Please try again with todays floppies, and if it doesn't fix the problem, we need to investigate what driver is missing or something. I'll try the new floppies tonight. Ummm... The contents of http://people.debian.org/~luther/d-i/images/daily/powerpc/floppy-2.4/ haven't changed in the last few days. Is the build process stalled somewhere? Thanks! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#270599: Floppy install on Oldworld PowerMac
On Wednesday, September 8, 2004, at 05:18 AM, Sven Luther wrote: On Wed, Sep 08, 2004 at 04:17:55AM -0400, Rick_Thomas wrote: Package: installation-reports powerpc boot-floppy 20040906 OldWorld PowerMac ... Then I tried the boot floppy. It gave me the tuxmac and made reading noises. After a while it ejected the boot floppy and switched to a text mode screen at (I think) 640x480 resolution. This is good enough for installing -- but not satisfactory for long term usage. Yes, i guess quik-installer should allow you to use further kernel options. You could create your own miboot floppy, and then you can add the options you want, more on this below. For the time being, just adding DEBCONF_PRIORITY=medium to the standard boot floppy would be a major good-thing. Frankly, I think that medium priority would be acceptable as a default mode for floppy boots. It's nice to minimize user interaction and all, but if I'm going to all the trouble of burning a bunch of floppies, I want a reasonable amount of control over the details of the installation process. I don't think inexperienced users will find the medium priority dialogue any more confusing than the existing woody installer. Just my opinion -- YMMV, of course. It called for the root floppy, so I fed it that, which it read happily. After reading the root floppy and asking me some questions about languages and locations, it asked if I wanted to read a driver floppy. I said yes and fed it the root-2 floppy. Well, i fixed the root-2 thingy earlier, so it is nice that it works, even if there is no real support for this in the installer yet. Feel free to participate in the fixing of this, be it only by suggesting what the root-2 asking question should be, and where it should be asked. Ideally we would add a load-second-root-floppy .udeb, which would present a menu and load the second floppy, and which would be part of the first root floppy. A special load-root-2.udeb (or whatever) may not be necessary: Just think of everything after the root as extra installer component floppies (or some such) rather than driver floppies specifically. Simply modify the existing dialogue to end with a question Do you want to load another installer component? If the answer is yes loop back and re-execute. If the answer is no, make a normal return. The first pass through is mandatory and loads the root-2 floppy. All subsequent passes are optional, based on what kind of installation you want to do. One thing to be careful of: It will be necessary to craft the wording of the dialogue questions very carefully so that the user understands fully what is going on, and what is required of them, at each step. The root-2 floppy contains stuff (namely netcfg and co) that was spilled out from the first root floppy. That's pretty much what I figured was going on. My choice of root-2 at this point was based on a hunch. There was no indication of which driver floppy it was expecting (Indeed, it was not clear at all that root-2 was a driver floppy. My hunch was that it would be needed immediately and that the easiest way to add files to the ram-disk root was to emulate a driver floppy.) It would be better to out-and-out say root-2 if that's what is wanted. Like Joeyh mentioned, right now there is support for loading only one drivers floppy, which may well be buggy in itself, and maybe a question for asking for an additional floppy like asking for additional apt sources later on may be welcome. Also, the root-2 is not really a drivers floppy, but should be loaded earlier on, maybe. I have no problem with answering questions about language and location before loading additional installer components. I'd go ahead and leave it right where it is in the sequence, if that's easiest. It then tried to detect my network interface and failed, so it asked Because the net drivers are not on the floppy. for the network drivers floppy, which I gave it. This time it succeeded in finding my network interface and configured it via DHCP Woaw. I was under the impression that this would fail, from joeyh's comment about only one driver floppy, but this is great. Right. This is what makes me think we can use the existing framework to load an arbitrary number of extra installer component floppies. (I would have preferred the option to do this manually, but there is no way to specify DEBCONF_PRIORITY=medium in booting an oldworld pmac Like said, if you build your own miboot floppy, you can add any kernel arguments you like. As miboot is non-free, users may be forced to do this anyway, so ... Yuch! Please don't force inexperienced users to build their own boot floppy. You'll loose a large class of potential users if you do. machine from floppy.) It asked for a mirror, and I specified the uchicago one since it seems to be fastest and most reliable from my little corner of the Internet. Overcool. Note 2: Things proceeded more or less as expected
Bug#270239: Timezone configuration should not show 'UTC' after system time
Frans Pop wrote:
On Monday 06 September 2004 19:53, Joey Hess wrote:
AfAIK hwclock output never includes the timezone.
I'm afraid it does.
On a system installed with LANG=en_US (on which I based my report):
# hwclock --show --localtime | awk '{NF-=2; print $0}'
Mon 06 Sep 2004 09:00:31 PM CEST
On a system installed with [EMAIL PROTECTED]:
# hwclock --show --localtime | awk '{NF-=2; print $0}'
ma 06 sep 2004 18:53:11 CEST
This is of course after I selected my timezone to be Europe/Amsterdam. hwclock
apparently (from the output in base-config) shows 'UTC' before timezone
selection.
I've got no clue why it does not show the timezone in your situation.
Apparently, it looks at the LANG environment variable...
LANG=C /sbin/hwclock --show --localtime
gives
Tue Sep 7 02:22:16 2004 -0.463550 seconds
but
LANG=en_US /sbin/hwclock --show --localtime
gives
Tue 07 Sep 2004 02:23:24 AM EDT -0.950496 seconds
Suggested fix: Use a LANG=C prefix.
Interesting...
I have no idea why the maintainers of hwclock care two figs about the LANG envariable.
But it seems they do.
Moral of the story: In a multicultural system like Debian, *everything* has to be
tested with a variety of LANG values. Welcome to the twenty-first century!
Rick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#270239: Timezone configuration should not show 'UTC' after system time
On Monday, September 6, 2004, at 11:00 PM, Joey Hess wrote: Rick Thomas wrote: Apparently, it looks at the LANG environment variable... LANG=C /sbin/hwclock --show --localtime gives Tue Sep 7 02:22:16 2004 -0.463550 seconds but LANG=en_US /sbin/hwclock --show --localtime gives Tue 07 Sep 2004 02:23:24 AM EDT -0.950496 seconds Ok, I see: I have LC_TIME=C while LANG=en_US. Suggested fix: Use a LANG=C prefix. That really doesn't work, the time display needs to be localised along with everything else. Unfortunatly I can't think of a good way to remove the time zone from the display that'll work for all LC_TIME settings. -- see shy jo OK: How about this /sbin/hwclock --show --localtime --debug | sed -n 's/Time read from Hardware Clock: //p' which prints this 2004/09/07 05:03:27 Which is pretty much language/locale independent. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Red X saga -- success!!! (up to a point...)
On Wednesday, September 1, 2004, at 04:45 AM, Sven Luther wrote: Ok, try out : http://people.debian.org/~luther/miboot/floppy-2.6-2004.09.01 I have checked the ofonlyboot, boot and root floppies. I tried this -- the usual 30 seconds or so of floppy noises followed by Red X for both the boot and ofonlyboot floppies. also http://people.debian.org/~luther/miboot/floppy-2.4-2004.08.31 same result - 30 seconds or so or floppy reading then Red X for both the boot and ofonlyboot floppies. I'm going to test the daily 2.4 floppies at http://people.debian.org/~luther/d- i/images/daily/powerpc/floppy-2.4/ then go to bed. ... pause while I go into the other room to try things out ... Wonder of wonders! It boots and reads the root and two drivers floppies! It got as far as finding the network interface card and the CD-rom drive and reading the d-i udebs from the CD. It even tried to run the partitioner, but there it failed to find my hard disk. Oh well -- too much success in one day is bad for your karma... (-8) We'll work on why it didn't find my hard disk another day. It's almost 4 AM and I'm going to bed! Enjoy! Rick Here's where I got the successful boot floppy from: Index of /~luther/d-i/images/daily/powerpc/floppy-2.4 NameLast modified Size Description Parent Directory26-Aug-2004 21:35 - asian-root.img 01-Sep-2004 21:26 1.1M boot.img01-Sep-2004 21:27 1.4M cd-drivers.img 01-Sep-2004 21:27 1.4M net-drivers.img 01-Sep-2004 21:27 1.4M ofonlyboot.img 01-Sep-2004 21:27 1.4M root.img01-Sep-2004 21:28 1.2M Apache/1.3.26 Server at people.debian.org Port 80 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#269529: OldWorld pmac installation -- several problems
Joey Hess wrote: Can you mail the /var/log/debian-installer/syslog and messages to this The complete set of logs and other system info from that install are available at: http://rcthomas.org:7879/~rbthomas/logfiles/install-6500/ I can mail them to the bug if you like, but why bother? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#269529: OldWorld pmac installation -- several problems
Joey Hess wrote: Rick Thomas wrote: http://rcthomas.org:7879/~rbthomas/logfiles/install-6500/ Permissions prevent me from reading the syslog. Fixed. Sorry! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Red X -- not quite gone yet...
Sven, It's 2:15 AM, and I've got a meeting tomorrow at work, so I won't be able to test these tonight. I'll try to get to them tomorrow (9/1) in the evening (US East Coast time). Please do me a favor and loop-mount the images to see if they have all the expected pieces and the pieces are of the expected sizes. That way we won't loose another round of debugging for a problem that doesn't require an actual bootstrap to discover. Thanks! Take care! Rick On Tuesday, August 31, 2004, at 11:03 AM, Sven Luther wrote: On Tue, Aug 31, 2004 at 04:15:01PM +0200, Wouter Hanegraaff wrote: On Tue, Aug 31, 2004 at 03:41:50PM +0200, Sven Luther wrote: Please try the (2.6) floppies at : http://people.debian.org/~luther/miboot/floppy-2.6-2004.08.31 boot.img only contains vmlinuz and doesn't boot, ofonlyboot.img starts loading a kernel and ends with the tux/red cross. http://people.debian.org/~luther/miboot/floppy-2.4-2004.08.31 boot.img and ofonlyboot.img start loading a kernel and end with the tux/red cross. http://people.debian.org/~luther/miboot/floppy-2.4-old-2004.08.31 boot.img only contains vmlinuz and doesn't boot, ofonlyboot.img starts loading a kernel and ends with the tux/red cross. Could you try both daily-builds tomorrow ? and todays 2.4 one too. I think miboot _never_ worked for you, right ? What is your box again ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Red X -- not quite gone yet...
On Monday, August 30, 2004, at 04:41 AM, Sven Luther wrote: On Mon, Aug 30, 2004 at 08:23:28AM +0200, Sven Luther wrote: On Mon, Aug 30, 2004 at 01:58:34AM -0400, Rick Thomas wrote: Sven Luther wrote: Rick Thomas wrote: Is it possible the objcopy is corrupting it? This is indeed a possibility. I will disable this again for the 2.4 floppies, and we will see tomorrow what happens. That said, the 2.6 floppies are too big to work with miboot without the objcopy -O binary call, so we need to investigate this more in detail. I downloaded the latest 2.4 floppy images, but it looks like you didn't get around to disabling the objcopy yet. Yeah, alioth and thus the d-i svn repo was dead yesterday. It is up again, and i will remove it for tomorrow. Fixed, please try tomorrows floppy-2.4 builds. Friendly, Sven Luther Not yet... When I boot the ofonlyboot (and the boot) floppy, I get the tuxmac icon for only a few seconds. The red X appears almost immediately. When I looked at the filesystem, it has a zero length zImage file, and no vmlinu* file. Commenting out the objcopy means that there is no vmlinux.bin file for gzip to work on. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Red X -- was: Re: new oldworld pmac miboot 2.6 floppies, root size should be ok, net_drivers still too big, please test.
On Sunday, August 29, 2004, at 04:31 AM, Rick_Thomas wrote: I tried the new 2.4 PowerMac floppys today. Now I get the Red X on the 2.4 boot floppy as well. I did an experiment... I mounted the 2.4 boot floppy and extracted the zImage file, uncompressed it, and compared it to the 2.4.25-powerpc-small kernel. They both claim to be the same kernel in that strings $file | grep 'Linux version' produces the same output for each file. Namely: Linux version 2.4.25-powerpc-small ([EMAIL PROTECTED]) (version gcc 3.3.3 (Debian 20040401)) #1 mer avr 14 17:26:11 CEST 2004 But the two files differ according to cmp. So I wonder if the process of compressing the kernel and putting it on the miboot floppy is somehow corrupting it? Rick OOOps... I missed the objcopy -O binary that was occurring in the log file. When I did that, the two files were identical. So the compression and copying to the floppy image are happening correctly. Is it possible the objcopy is corrupting it? mumble... Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Red X -- was: Re: new oldworld pmac miboot 2.6 floppies, root size should be ok, net_drivers still too big, please test.
Sven Luther wrote: Rick Thomas wrote: Is it possible the objcopy is corrupting it? This is indeed a possibility. I will disable this again for the 2.4 floppies, and we will see tomorrow what happens. That said, the 2.6 floppies are too big to work with miboot without the objcopy -O binary call, so we need to investigate this more in detail. I downloaded the latest 2.4 floppy images, but it looks like you didn't get around to disabling the objcopy yet. In any case, I still get a red X. The objcopy and the bfd library on my most recent debian sarge install are dated May 19th, 2004. Is it possible that we haven't had a successful powerpc OldWorld floppy boot since that time? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Plea for help from PowerMac Open Firmware gurus -- Testing newoldworld pmac miboot 2.6 floppies
Rick_Thomas wrote: Well... on the beige G3, I booted into Open Firmware with the ofonlyboot floppy in the drive. The G3 comes up with console input/output being keyboard/screen. From another Mac running MacOS-9, I connected with MacKermit to the G3's modem port (which is normally /dev/ttyS0 under Linux) At the G3's console, I typed boot console=ttyS0return. The floppy drive made reading noises, and the tuxMac icon appeared on the G3's screen. Nothing happened at this point on the Kermit serial port -- there was no response when I type things at it over the serial port. After a while the floppy stopped making noises and a red X appeared over the tuxMac icon. Still no messages on the serial port, but now it at least will echo what I type at it. No response other than echos, though. It seems that I'm not talking to a live kernel. Does any one have a clue what the red X means? It appears that the console=ttyS0 option is being noticed (at least that's how I interpret the fact that it switched from no-echo to echo at the point where the red X appeared...) So I could put other boot-time options there as well. Is there a verbose option I can try? 1) Reading man pages for bootparam seems to indicate that there is a debug boot parameter that turns on more verbose logging to the console. Unfortunately, when I tried it with the 2.6 boot floppy, there was no change from the above described behavior. 2) For comparison purposes, I tried the same thing with the 2.4 powerpc-small boot floppy. (the 2.4 root floppy is hosed, so I didn't expect to get very far, but...) I booted the G3 into Open Firmware while listening to the modem serial port on another machine -- as described above. On the G3's console, I typed boot debug console=ttyS0return. I was rewarded by a tuxmac icon and floppy reading noises. When the noises stopped, the kernel boot messages appeared on the G3's console screen, but nothing appered at the remote terminal watching the serial port. So I'm no longer so sure as I once was that the parameters after boot in Open Firmware are getting passed to the kernel. Is it possible to modify the boot-parameters that are compiled into the kernel? For example, the ofonlyboot kernel differs from the boot kernel only in that there is a string video=ofonly in the former, but not in the latter. How does that get there? Maybe the same mechanism could be used to give it the debug and console=ttyS0 options... Sigh! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PowerPC Install
Sven Luther wrote: the .coff booting is probably the only free alternative, but i am told requesting a debian oldworld user to get the serial console working is not acceptable. Only unacceptable in the sense that Open Firmware is dramatically different between machine types. Apple developed it only so far as necessary to get their machines to boot... This process left a new and different (and wonderfully diverse) crop of bugs for each new machine type. Thus, the problem is that instructions for using Open Firmware to boot directly would have to be different in detail for each PowerMac machine type -- not altogether a pleasant prospect. The BootX, miboot and (to some extent) quik bootloaders mask these inter-machine differences, making them vastly simpler to document and use. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PowerPC Install
Sven Luther wrote: On Thu, Aug 26, 2004 at 12:22:38AM -0400, Rick_Thomas wrote: On Wed, 2004-08-25 at 06:59, Wouter Hanegraaff wrote: Any ideas why these daily builds are broken every day? I just tried the 2.4 floppy images. What Wouter says is correct. I'm going to go over the logs with a fine-toothed comb. Maybe I can figure out what's wrong. Sorry, it is probably me that did the breakage or something when i enabled the build of the 2.6 floppies. It needs to get fixing. For what it's worth, I've been examining the log of the build at http://people.debian.org/~luther/d-i/images/2004-08-25/build_powerpc-small_floppy_root.log I noticed that near the end, the script does an e2fsck of the root.img file. This seems to indicate that the image is completely hosed, and e2fsck responds by (essentially) resetting it to an empty ext2 filesystem. This explains why the root.img is the way it is (empty except for lost+found). But it doesn't explain why the image filesystem is broken in the first place. Earlier in the script, the *-drivers images are constructed but not fsck'ed. Nevertheless, they probably suffer from the same breakage as the pre-fsck root image. When I try to run fsck on them, I get the same kind of error messages as the log shows for the root image. Anyway, it's a place to start... Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new oldworld pmac miboot 2.6 floppies, root size should be ok, net_drivers still too big, please test.
On Thursday, August 19, 2004, at 05:00 AM, Sven Luther wrote: happy floppy disk reading noises. However, the noises eventually stopped and a red X appeared over the TuxMac. Then nothing. I had to manually eject the floppy from the drive. What we need would be a way to get a log of it or something. I'll try booting from open-firmware directly on a serial console. It may take a couple of trys. I've never done that before on a Mac (On a Sun/sparc machine, it's standard operating procedure, and I've got lots of experience with Suns -- so it's not completely unexplored teritory!) Maybe there will be some console messages that will be helpful. I have a suspsicion that the pmac floppies being modular maybe one of the causes of this, not sure though, possibly another modular important piece of the kernel. Is the swim floppy driver compiled into the kernel? (not modular). If not, the kernel may be unable to read the floppy drive once it's been loaded by the firmware/bootblock code... Are there any other drivers that must be compiled in? It really is a kernel issue though, can you boot the 2.6.7 kernel with bootx or quik ? BootX works fine with 2.6.7. I haven't been able to get quik working (haven't tried very hard, since BootX works so well) Remember me what happened with the 2.4 powerpc-small based floppies ? It's been a while, (March, I think...) but I think the sequence of events went sort of like this: TuxMac gives way to Tux icon at top of screen and scrolling kernel messages. Eventually it asks me to load the root floppy (but doesn't eject -- so I have to eject manually) I load the floppy and answer a bunch of questions ... etc. I have the old March floppy images archived. Would you like me to burn some floppys from them and give them a try? Just to refresh our memories... Can you make a boot floppy with a 2.4 kernel that installs a 2.6 kernel from the net/CD/whatever? Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Old world mac
On Thursday, August 5, 2004, at 02:19 PM, Rick Thomas wrote: Rikard Borg wrote: I'm one of those out there waiting with a 7200 box at home. Rikard Borg -- Hi Rikard, Did the work-around I sent you help any? Have you got that 7200 box working yet? Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#264964: OldWorld PowerMac Debian-Install floppys
On Friday, August 13, 2004, at 09:53 AM, Sven Luther wrote: Can you please retry the miboot boot floppies tomorrow ? I fixed the daily-builds to rebuild the actual miboot floppies. Now, the only problem remaining would be the root floppy being too big, and the actual 2.6 kernel based miboot floppies. Friendly, Sven Luther Hi Sven! Sorry for the delay on getting this done. I downloaded the boot and root (and other) images from http://people.debian.org/~luther/d-i/images/daily/powerpc-small/floppy/ See appendix 1. After some fooling around with a dirty floppy drive and some poor quality floppy disks (I *hate* dealing with floppy disks! The floppy drives on Old Macs are almost invariably in poor shape. This is one reason I strongly recommend that people use BootX instead if they have the option.) I eventually succeeded in writing (and verifying) the images to physical floppies. First observation: The root image is larger than (1474560=1440*1024) bytes, so dd gets an error trying to write it to /dev/fd0. See appendix 2. Second observation: When I loop mount the root.img, all the stuff necessary for booting seems to be there (confirmed later by actually booting off of it) See appendix 3. Third observation: I booted from the boot floppy. It read the floppy, did the normal kernel initialization stuff and finally ejected the boot floppy with the message Insert root floppy...press ENTER. Which I did. It printed RAMDISK: Compressed image found at block 0 then read for a while then stopped reading (no noise from the floppy drive). And it hung. I gave it several minutes. Nothing happened. No error messages on the console -- nothing. See my next opservation for one possible explanation of this behavior. Fourth observation. When I uncompress root.img and loop mount it, there is nothing there (just a lost+found directory)! Where did the contents of the initrd go? And, if it doesn't have anything in it, what excuse is there for it being so large? See appendix 4. Hope this helps! Rick === Appendix 1 Index of /~luther/d-i/images/daily/powerpc-small/floppy NameLast modified Size Description Parent Directory07-Jul-2004 00:25 - asian-root.img 15-Aug-2004 21:06 1.2M boot.img15-Aug-2004 21:06 1.4M cd-drivers.img 15-Aug-2004 21:06 1.4M net-drivers.img 15-Aug-2004 21:06 1.4M ofonlyboot.img 15-Aug-2004 21:06 1.4M root.img15-Aug-2004 21:08 1.4M Apache/1.3.26 Server at people.debian.org Port 80 Appendix 2 $ cd /tmp/DebianFloppys/ $ ls -lA total 12860 -rw-rw-r--1 rbthomas rbthomas 1474560 Aug 16 00:10 boot.img -rw-rw-r--1 rbthomas rbthomas 1467392 Aug 16 00:12 cd-drivers.img -rw-rw-r--1 rbthomas rbthomas 1467392 Aug 16 00:12 net-drivers.img -rw-rw-r--1 rbthomas rbthomas 1474560 Aug 16 00:13 ofonlyboot.img -rw-rw-r--1 rbthomas rbthomas 1514521 Aug 16 00:10 root.img $ Appendix 3 # cd /tmp/DebianFloppys/ # mount -t hfs -o loop boot.img /mnt/floppy/ # ls -lAR /mnt/floppy/ /mnt/floppy/: total 1166 dr-xr--r--2 root root8 Aug 16 2004 .finderinfo dr-xr--r--2 root root8 Aug 16 2004 .resource -rw-r--r--1 root root 300 Aug 16 2004 .rootinfo -rwxr--r--1 root root0 Aug 16 2004 Finder -rwxr--r--1 root root0 Aug 16 2004 System -rwxr--r--1 root root 1193284 Aug 16 2004 zImage /mnt/floppy/.finderinfo: total 0 -rw-r--r--1 root root 300 Aug 16 2004 Finder -rw-r--r--1 root root 300 Aug 16 2004 System -rw-r--r--1 root root 300 Aug 16 2004 zImage /mnt/floppy/.resource: total 78 -rw-r--r--1 root root0 Aug 16 2004 Finder -rw-r--r--1 root root79593 Aug 16 2004 System -rw-r--r--1 root root0 Aug 16 2004 zImage # Appendix 4: # cp root.img root.gz # gunzip root.gz # mount -t ext2 -o loop root /mnt/floppy # ls -lAR /mnt/floppy /mnt/floppy: total 1 drwx--2 root root 1024 Aug 15 22:46 lost+found /mnt/floppy/lost+found: total 0 # -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#264964: OldWorld PowerMac Debian-Install floppys
On Monday, August 16, 2004, at 03:18 AM, Sven Luther wrote: Thanks Rick for testing it. I will build 2.6.8 miboot kernels today, could you possibly give it a try to see if it boots this evening or something such ? Sure. Expect my report at about the same time tomorrow that I posted today's. it hung. I gave it several minutes. Nothing happened. No error messages on the console -- nothing. See my next opservation for one possible explanation of this behavior. I don't think this is it. I believe that maybe it failed because it is trying to read post the end of the floppy or something. How do you account for there being nothing (except lost+found) in the ramdisk when I expanded it and mounted it? Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#264964: OldWorld PowerMac Debian-Install floppys
Package: installation-reports I retrieved the floppy images at http://people.debian.org/~luther/d-i/images/daily/powerpc-small/floppy/ so I could try out a floppy-boot install from them. I got never even got off the ground... 1) The boot.img' floppy seems to have nothing on it but the 'vmlinuz' kernel. There's no system folder or any of the other boilerplate necessary for a bootable floppy. I understand that there are technical licensing problems with miboot. Nevertheless, there at least ought to be a README file somewhere that gives the adventurous user, willing to ignore the licensing problems, the necessary magic incantations to transform this neutered thing into a live/virile/bootable floppy by mixing it with miboot (however obtained) under the light of a full moon at midnight. 2) The 'root.img' file is bigger than will fit onto a 1.44 MB floppy. Worse, for all it's size, it seems to contain nothing but a 'lost+found' directory -- no install scripts or anything else! Is there a different place I should be getting the floppy images from? Enjoy! Rick Relevant excerpt from http://d-i.alioth.debian.org/svn/debian- installer/installer/doc/checklist Release testing checklist. Successful installs should be reported for each of the following before release. We're currently testing the debian-installer build 20040801 and the 20040806 sarge_d-i CD builds. pass/fail (details) powerpc basic netinst cd basic businesscard cd ok floppy + cd [not newworld] floppy + network [not newworld] netboot using pcmcia network card 32 mb ram 48 mb ram -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#264964: OldWorld PowerMac Debian-Install floppys
On Wednesday, August 11, 2004, at 05:45 AM, Sven Luther wrote: On Wed, Aug 11, 2004 at 11:25:48AM +0200, Sven Luther wrote: # We'd like to use miboot, but it isn't in the archive yet ... #miboot -c ./tmp/powerpc-small_floppy_boot/miboot.conf # ... so instead we do some grungy HFS hacking. I wonder who did that modification, and i probably pulled it in when upgrading :/ Ah, it is fixed, Colin Watson did this :/ r15148 | cjwatson | 2004-05-11 03:48:38 +0200 (Tue, 11 May 2004) | 4 lines Arrange for there actually to be a kernel on the powerpc-small boot floppy again. This is slightly moot, though, as we don't have miboot yet so it's still not bootable ... r15116 | cjwatson | 2004-05-10 18:42:15 +0200 (Mon, 10 May 2004) | 3 lines powerpc-small root floppy was out of space; split off an asian-root floppy, the same as we already have for i386. Closes: #246958 r14082 | cjwatson | 2004-04-21 19:27:41 +0200 (Wed, 21 Apr 2004) | 2 lines Comment out miboot invocation for now; it's still not in the archive. I wonder if we should not do a miboot upload to non-free and be gone with it. This would mean a debian-installer-non-free or something such. I will see if i can find again the miboot source package and do the upload. Amen to that! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#264964: OldWorld PowerMac Debian-Install floppys
On Wednesday, August 11, 2004, at 05:25 AM, Sven Luther wrote: On Wed, Aug 11, 2004 at 01:57:22AM -0400, Rick Thomas wrote: Package: installation-reports I retrieved the floppy images at http://people.debian.org/~luther/d-i/images/daily/powerpc- small/floppy/ so I could try out a floppy-boot install from them. I got never even got off the ground... 1) The boot.img' floppy seems to have nothing on it but the 'vmlinuz' kernel. There's no system folder or any of the other boilerplate necessary for a bootable floppy. I understand that there are technical licensing problems with miboot. Nevertheless, Can you check in the logs to see what happened ? Mmm, indeed : http://people.debian.org/~luther/d- i/images/daily/build_powerpc-small_floppy_boot.log shows : # We'd like to use miboot, but it isn't in the archive yet ... #miboot -c ./tmp/powerpc-small_floppy_boot/miboot.conf # ... so instead we do some grungy HFS hacking. I wonder who did that modification, and i probably pulled it in when upgrading :/ there at least ought to be a README file somewhere that gives the adventurous user, willing to ignore the licensing problems, the necessary magic incantations to transform this neutered thing into a live/virile/bootable floppy by mixing it with miboot (however obtained) under the light of a full moon at midnight. What i would really like is to have miboot go at least to contrib if not main. The step to do this is for someone else than me though, or i would not be able to do the reimplementation. The idea is to look at the miboot boot block format, and extract the first header part (which is ok to reuse) and the little bit of code afterward, which are rumored to be trap calls to the mac rom, in m68k assembly. And describe what it is doing, so a clean-room reimplementation can be done from it. 2) The 'root.img' file is bigger than will fit onto a 1.44 MB floppy. Worse, for all it's size, it seems to contain nothing but a 'lost+found' directory -- no install scripts or anything else! Is there a different place I should be getting the floppy images from? Nope, someone broke them, and svn seems broken right now :/ BTW, can you look at the kernel found here : http://people.debian.org/~luther/d- i/images/daily/powerpc/netboot/vmlinuz-coff.initrd and try to boot it from the serial console OF and write an installation report ? Friendly, Sven Luther I'll look into making a null-modem (8-pin mini-din on both ends!) cable so I can use one machine as a serial console for the other. If I can do that, I'll give your suggestion a try. In the mean time, would it work with BootX? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#264963: Installation report for Apple Blue White G3 400 from netinstall CD (powerpc, RC1)
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]
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: Old world mac
Install MacOS-9. Then use the BootX boot-loader. (or 8.5 or 8.6, if 9 won't run on the S-900. I've never seen one of those, so I don't know what will run on it and what wont. I'm told that BootX even works with MacOS 7.5, if your machine can run it and you have a floppy drive to install it from.) You don't need much of MacOS to do the trick -- 200 MB is more than enough. But, if you can spare about 500MB to dedicate to MacOS, an easy install is a lot simpler than going thru all the options at install time trying to intuit whether you will need that feature...) One cute trick, if you have a 100MB Zip drive, is to use the IoMega tools to make an emergency boot Zip disk, which takes up less than 50 MB, even after you add the BootX and Linux kernel/initrd files and a couple of other useful tools. Once you have the emergency boot zip drive in hand, you can copy it to a small (under 100 MB) HFS partition on your hard drive, and have yourself the most feature-ful boot loader that ever was. One other thought. use the 2.4.25 kernel (or later in the 2.4 series.) The 2.6 kernels are missing some drivers for the OldWorld Mac peripherals. (The drivers are available as modules, but getting them installed is not [yet] automatic. I'm trying to get the developers to fix this, but not many of them seem to care... Rick Here's something I wrote about using the onboard SCSI and ethernet chips on my oldworld hardware under the 2.6 kernel. It may be helpful. Rikard Borg wrote: Hi I'm one of those out there waiting with a 7200 box at home. Rikard Borg -- Hi Rikard, Here's a workaround. (Thanks! and a tip of the hat to Christian Leimer [EMAIL PROTECTED] and Jens Schmalzing [EMAIL PROTECTED] for putting me onto this.) The 2.6 initrd has many more drivers than are recognized by the hardware discover and hot-plug phases of debian-installer. In particular, two that are often needed for OldWorld PowerMacs are the drivers for the mesh scsi chip, and the mace ethernet chip, frequently used on the OldWorld Apple motherboards. Along with many others, they are located in the /lib/modules/2.6.7-powerpc/kernel/drivers/ area of the initrd. So, if you are in that boat, all you have to do is: 1) Boot with the DEBCONF_PRIORITY=medium option in the BootX (or other boot-loader) kernel options line. Then, just before each of the detect network hardware and detect disks phases, switch to the Option-F2 console and do a modprobe mace or modprobe mesh respectively, then go back to the main menu on console option-F1 and proceed as normal. If your ethernet chip is not a mace, but some other one that isn't automatically recognized, substitute the appropriate driver for it in place of mace. Do the same, mutatis mutandis, if you have an odd-ball SCSI chip. 2) Since you loaded the drivers behind the back of d-i, it doesn't know to put them in the /target/etc/modlues file before the reboot, so you have to do that manually. Just before it reboots, switch one more time to the option-F2 console. Do a chroot /target and use vi (or whatever) to edit /etc/modules. Add lines for your respective behind the back drivers. Once you are safely out of the editor, you can exit the chroot by hitting ctl-D. 3) I boot using MacOS-9 and BootX, so for me there's one more step I have to do behind d-i's back. That's to mount the (hfs) MacOS partition and copy the kernel and initrd from /target/boot into the appropriate places in the System folder on the MacOS partition. [[In order to do this, I have to choose the hfs file system driver when d-i gives me a list of optional drivers to load, and I need to have formatted my MacOS-9 partition as hfs, not hfs+, when I was installing it.]] I haven't yet figured out what to do if your new boot disk needs a behind the back driver. (You're in a catch-22 situation. You need the driver to read the /etc/modules file that tells it to load the driver!) I think you have to edit the /etc/modules file on the initrd to have it load the necessary modules before it mounts the real root. That's not difficult to do if you have a functioning Linux you can boot into with access to the initrd, but if you are installing from scratch, I don't think you have that option. Let me know if you have any trouble with this procedure. I'll try to help any way I can. Enjoy! Rick On Tuesday, August 10, 2004, at 10:02 PM, Eric D. Hedekar wrote: Any one of these three bugs will render debian-installer unusable for anyone with anything but a plain vanilla hardware or networking environment who doesn't have help from a competant System Administrator, or have such skills personally. Since I'm the only one on this list who cares two figs about OldWorld PowerPC hardware, and I have UNIX SysAdmin experience going back 25 years (including some pretty unusual hardware!), I guess it's not a show stopper... Still, there *might* be some folks out there in the real world (TM), who will be disappointed that they
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]
Re: Old world mac
Rikard Borg wrote: Hi Rick Thomas Wrote: Any one of these three bugs will render debian-installer unusable for anyone with anything but a plain vanilla hardware or networking environment who doesn't have help from a competant System Administrator, or have such skills personally. Since I'm the only one on this list who cares two figs about OldWorld PowerPC hardware, and I have UNIX SysAdmin experience going back 25 years (including some pretty unusual hardware!), I guess it's not a show stopper... Still, there *might* be some folks out there in the real world (TM), who will be disappointed that they can't figure out how to install the new Debian release on their particular old Macintosh hardware. You never know! I'm one of those out there waiting with a 7200 box at home. Rikard Borg -- Hi Rikard, Here's a workaround. (Thanks! and a tip of the hat to Christian Leimer [EMAIL PROTECTED] and Jens Schmalzing [EMAIL PROTECTED] for putting me onto this.) The 2.6 initrd has many more drivers than are recognized by the hardware discover and hot-plug phases of debian-installer. In particular, two that are often needed for OldWorld PowerMacs are the drivers for the mesh scsi chip, and the mace ethernet chip, frequently used on the OldWorld Apple motherboards. Along with many others, they are located in the /lib/modules/2.6.7-powerpc/kernel/drivers/ area of the initrd. So, if you are in that boat, all you have to do is: 1) Boot with the DEBCONF_PRIORITY=medium option in the BootX (or other boot-loader) kernel options line. Then, just before each of the detect network hardware and detect disks phases, switch to the Option-F2 console and do a modprobe mace or modprobe mesh respectively, then go back to the main menu on console option-F1 and proceed as normal. If your ethernet chip is not a mace, but some other one that isn't automatically recognized, substitute the appropriate driver for it in place of mace. Do the same, mutatis mutandis, if you have an odd-ball SCSI chip. 2) Since you loaded the drivers behind the back of d-i, it doesn't know to put them in the /target/etc/modlues file before the reboot, so you have to do that manually. Just before it reboots, switch one more time to the option-F2 console. Do a chroot /target and use vi (or whatever) to edit /etc/modules. Add lines for your respective behind the back drivers. Once you are safely out of the editor, you can exit the chroot by hitting ctl-D. 3) I boot using MacOS-9 and BootX, so for me there's one more step I have to do behind d-i's back. That's to mount the (hfs) MacOS partition and copy the kernel and initrd from /target/boot into the appropriate places in the System folder on the MacOS partition. [[In order to do this, I have to choose the hfs file system driver when d-i gives me a list of optional drivers to load, and I need to have formatted my MacOS-9 partition as hfs, not hfs+, when I was installing it.]] I haven't yet figured out what to do if your new boot disk needs a behind the back driver. (You're in a catch-22 situation. You need the driver to read the /etc/modules file that tells it to load the driver!) I think you have to edit the /etc/modules file on the initrd to have it load the necessary modules before it mounts the real root. That's not difficult to do if you have a functioning Linux you can boot into with access to the initrd, but if you are installing from scratch, I don't think you have that option. Let me know if you have any trouble with this procedure. I'll try to help any way I can. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Introduction
Colin Watson wrote: On Mon, Aug 02, 2004 at 03:52:20AM +1000, James Mills wrote: On Sun, Aug 01, 2004 at 06:36:42PM +0100, Colin Watson wrote: [Please keep further questions on the mailing list, if you would.] Shit. Does this list not have an explicit Reply-To header to the mailing list address either ? THis is the 2nd list I've come across that is configured this way. My apolagies. No Debian lists have that; deliberately so. Details? If it's deliberate, there must be something that breaks with an explicit Reply-To header worse than not having such a header breaks old mailers. Thanks, Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: release status
Joey Hess wrote: At this point the only delay is waiting for the autobuilders, which are overloaded from all the other uploads surrounding the sarge release, to catch up and build the d-i images. In the past 24 hours, we've gotten builds for hppa, ia64, s390, and sparc, plus a manual build for alpha. That leaves arm, m68k (building), mips, mipsel, and powerpc. d-i is far back in the queue for most of these arches[1] and is even slipping further behind on some as more high-urgency package uploads happen. Since it's looking like it could easily take days for some of these buildds to catch up, we may need to do manual builds on some of these architectures. It would be nice if we could get all the builds done before the next dinstall run. If you do a manual build, please take careto make it in an up-to-date and clean sid chroot. Other than that, we seem to be on track for a release. I'm not aware of any showstopper issues, and the current errata list is quite small. Once the initrd builds get in and the CDs are built with them, we will have one final day for last minute testing before the release. The test checklist in installer/doc/checklist is still missing many entries and the more complete it is the better I'd feel about calling this release rc1 instead of beta5. Over the last couple of weeks, I've submitted three (what I consider to be) serious bug report for d-i on OldWorld PowerPC machines, along with several more that are more in the line of annoyances. Any one of these three bugs will render debian-installer unusable for anyone with anything but a plain vanilla hardware or networking environment who doesn't have help from a competant System Administrator, or have such skills personally. Since I'm the only one on this list who cares two figs about OldWorld PowerPC hardware, and I have UNIX SysAdmin experience going back 25 years (including some pretty unusual hardware!), I guess it's not a show stopper... Still, there *might* be some folks out there in the real world (TM), who will be disappointed that they can't figure out how to install the new Debian release on their particular old Macintosh hardware. You never know! For reference, here are the bug numbers and a short description of each: Bug#261460: Non-DHCP network config step of d-i is broken If you choose to manually configure the network (don't use DHCP) the installer keeps coming back to the configure network step, and if you force it to move forward, after the reboot, the network is not configured. This seems to be unique to OldWorld PowerPC hardware (I've tried it on two different types of OldWorld machines and it breaks identically on both of them. However, it works on a couple of NewWorld machines I tried it on.) Also, accepting the default of DNSserver==gateway makes it work OK. Verrry strange! Bug#262201: PowerMac (OldWorld) - no driver for onboard SCSI Bug#262865: With two network interfaces after reboot uses the wrong one -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: release status
OOOps... I accidentally hit send when I meant to hit save... Here's the complete message as I intended it to be! Rick Joey Hess wrote: At this point the only delay is waiting for the autobuilders, which are overloaded from all the other uploads surrounding the sarge release, to catch up and build the d-i images. In the past 24 hours, we've gotten builds for hppa, ia64, s390, and sparc, plus a manual build for alpha. That leaves arm, m68k (building), mips, mipsel, and powerpc. d-i is far back in the queue for most of these arches[1] and is even slipping further behind on some as more high-urgency package uploads happen. Since it's looking like it could easily take days for some of these builds to catch up, we may need to do manual builds on some of these architectures. It would be nice if we could get all the builds done before the next dinstall run. If you do a manual build, please take careto make it in an up-to-date and clean sid chroot. Other than that, we seem to be on track for a release. I'm not aware of any showstopper issues, and the current errata list is quite small. Once the initrd builds get in and the CDs are built with them, we will have one final day for last minute testing before the release. The test checklist in installer/doc/checklist is still missing many entries and the more complete it is the better I'd feel about calling this release rc1 instead of beta5. Over the last couple of weeks, I've submitted three (what I consider to be) serious bug report for d-i on OldWorld PowerPC machines, along with several more that are more in the line of annoyances. Any one of these three bugs will render debian-installer unusable for anyone with anything but a plain vanilla hardware or networking environment who doesn't have help from a competent System Administrator, or have such skills personally. Since I'm the only one on this list who cares two figs about OldWorld PowerPC hardware, and I have UNIX SysAdmin experience going back 25 years (including some pretty unusual hardware!), I guess it's not a show stopper... Still, there *might* be some folks out there in the real world (TM), who will be disappointed that they can't figure out how to install the new Debian release on their particular old Macintosh hardware. You never know! For reference, here are the bug numbers and a short description of each: Bug#261460: Non-DHCP network config step of d-i is broken If you choose to manually configure the network (don't use DHCP) the installer keeps coming back to the configure network step. And if you force it to move forward, then after the reboot, the network interface is not configured. This seems to be unique to OldWorld PowerPC hardware (I've tried it on two different types of OldWorld machines and it breaks identically on both of them. However, it works on a couple of NewWorld machines I tried it on. Go figure!) Also, accepting the default of DNSserver==gateway seems to make it work OK. Verrry strange! Bug#262201: PowerMac (OldWorld) - no driver for onboard SCSI The 2.6.7 kernel version of d-i for PowerPC does not recognize Apple's old mesh onboard SCSI controller. Seeing as how lots of OldWorld machines have no other way than SCSI of attaching disks or CD-ROM drives, this renders them ineligible for installation using the 2.6.7 kernel. It works OK with the 2.4.25 kernel. Bug#262865: With two network interfaces after reboot uses the wrong one On a machine with two Network interface cards, only one of which is to be used (e.g. my situation with an onboard 10BaseT and a PCI 100BaseT but I only want to use the faster interface, and ignore the slower) after the reboot, the wrong interface is configured. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: release status (checklist)
Joey Hess wrote: The test checklist in installer/doc/checklist is still missing many entries and the more complete it is the better I'd feel about calling this release rc1 instead of beta5. If you'll send me a pointer (URL?) to the test checklist, I'll try to make sure that it gets as done as possible for OldWorld PowerPC hardware. Thanks! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#261460: Is anyone else seeing this? -- Re: Bug#261460: Non-DHCP network config step of d-i is broken
On Thursday, July 29, 2004, at 05:42 AM, Rick Thomas wrote: On Wednesday, July 28, 2004, at 04:27 PM, Joshua Kwan wrote: On Wed, Jul 28, 2004 at 03:40:30PM -0400, Rick Thomas wrote: Please, somebody, give it a try and let me know I'm not going crazy. It doesn't take very long to get to the point where this bug manifests itself, and you don't ever get to the point where you need to touch your hard disk, so it's easy to check. I'm inclined to believe that this is a corner case we haven't handled, and maybe it only applies on powerpc. Because I can't reproduce it for the life of me. If you configure your network device manually, does it work? If so, boot with DEBCONF_DEBUG=5, stick a pscp binary somewhere, wget it once you've manually configured the network, and put /var/log/syslog and /var/log/messages somewhere I can see them. Thanks, and sorry for not getting to this bug earlier. -- Joshua Kwan Well... here's an interesting observation! My gateway is at a different address from my DNSserver. (For what it's worth: Gateway=192.168.1.254, DNSserver=192.168.1.118) I noticed that the non-DHCP network configuration step always offers to set the DNSserver to the same address the gateway. And I always change it to point to my DNSserver. But this time I tried (out of desperation -- just trying random stuff) leaving the DNSserver the same as the gateway. And it worked! It did *not* loop back to the network configuration step. Is this a clue? What log files (or whatever else) do you need to see to followup on this? Would somebody please try this out on an i386? (DNSserver address != Gateway address) And let me know if it breaks non-DHCP network configuration? As I say, It's easy to try... you never need to get to the point of touching the disks. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#261460: Is anyone else seeing this? -- Re: Bug#261460: Non-DHCP network config step of d-i is broken
Thanks for the prompt reply! On Sunday, August 1, 2004, at 01:55 PM, Joshua Kwan wrote: If you do not CC [EMAIL PROTECTED], nobody except me will see this. I did that. Would somebody please try this out on an i386? (DNSserver address != Gateway address) And let me know if it breaks non-DHCP network configuration? This is my configuration at home, so yes, I've tried it. DNS server = 192.168.1.1 Gateway = 192.168.2.2 Works on i386 and sparc. ... So it's not so much of a clue as I thought it would be. Did the log file with DEBUG=5 help? If not, what else can I do to help. This is bugging the #$%* out of me! Thanks! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#262201: PowerMac (OldWorld) - no driver for onboard SCSI
On Friday, July 30, 2004, at 05:34 AM, Sven Luther wrote: On Fri, Jul 30, 2004 at 12:24:54AM -0400, Rick Thomas wrote: Package: installation-reports powerpc 20040724 businesscard OldWorld PowerMac kernel-2.6 INSTALL REPORT Debian-installer-version: sid_d-i/powerpc/20040724/sarge-powerpc-businesscard.iso Comments/Problems: The powerpc 2.6 kernel on the 20040724 businesscard CD is missing drivers (modules or built-in) for the Mac onboard SCSI bus. This happens on both my beige G3 minitower and my PowerMac 6500/225. On the G3 the problem manifests as not being able to see a SCSI Zip drive. On the 6500 it can't see any SCSI devices, CD-RW, 4.3 GB hard drive, or Zip. We probably need the pci id for those scis controllers, and ideally the name of the module in charge of it. Friendly, Sven Luther Here is lspci output from the G3 running a 2.4 kernel. Hope it helps! Rick [EMAIL PROTECTED]:~$ lspci :00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40) :00:0e.0 SCSI storage controller: Artop Electronic Corp ATP865 (rev 06) :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) [EMAIL PROTECTED]:~$ lspci -n :00:00.0 0600: 1057:0002 (rev 40) :00:0e.0 0100: 1191:0009 (rev 06) :00:10.0 ff00: 106b:0010 (rev 01) :00:12.0 0300: 1002:4754 (rev 9a) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#241516: partial success on Oldworld powermac
Thanks for the reminder. You can close this bug report. The ask for floppy driver module twice (and not fined it at all bug is still present, but I've mentioned it in other bug reports that reference more current CD images, so there's no need for this one. Enjoy! Rick On Friday, July 30, 2004, at 04:31 PM, Frederik Dannemare wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, first and foremost: thank you for your bug report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=241516 I'm currently processing old installation reports, and since you reported some problems back in April, I would very much appreciate it, if you could find time to download and test the latest[1] cd image and confirm whether you still see the problems you've mentioned. If you can confirm they are no longer present, I will close this report. Much has changed with the installer since April, and it is not unlikely that these problems may have been dealt with by the Debian Developers working on the installer. Looking forward to hearing from you again. Thank you for your time. [1]http://cdimage.debian.org/pub/cdimage-testing/daily/ - -- Frederik Dannemare | mailto:[EMAIL PROTECTED] GnuPG key: search for 'dannemare' on http://pgpkeys.mit.edu Key fingerprint: BB7B 078A 0DBF 7663 180A F84A 2D25 FAD5 9C4E B5A8 http://frederik.dannemare.net | http://www.linuxworlddomination.dk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBCrAdLSX61ZxOtagRAhZJAJ9CF+bCZe4akhhI5tZTtS7m/TStXQCeJo3s uHfEd49EBvlh564oRvuvTK4= =4kHd -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#261460: Is anyone else seeing this? -- Re: Bug#261460: Non-DHCP network config step of d-i is broken
On Wednesday, July 28, 2004, at 04:27 PM, Joshua Kwan wrote: On Wed, Jul 28, 2004 at 03:40:30PM -0400, Rick Thomas wrote: Please, somebody, give it a try and let me know I'm not going crazy. It doesn't take very long to get to the point where this bug manifests itself, and you don't ever get to the point where you need to touch your hard disk, so it's easy to check. I'm inclined to believe that this is a corner case we haven't handled, and maybe it only applies on powerpc. Because I can't reproduce it for the life of me. If you configure your network device manually, does it work? If so, boot with DEBCONF_DEBUG=5, stick a pscp binary somewhere, wget it once you've manually configured the network, and put /var/log/syslog and /var/log/messages somewhere I can see them. Thanks, and sorry for not getting to this bug earlier. -- Joshua Kwan I tried it again tonite with the 20040728 businesscard CD. After configuring the network manually, it returned me to the main menu with configure network hilighted. Same as before. This time, however, I manually moved the hilight forward to the next step and hit return. As before, it returned me to the configure network step where I again requested manual configuration and answered the questions. This time, it *didn't* return me to the main menu with configure network hilighted. Instead, it took me to the next step and asked me what protocol (http or ftp) I wanted to use. Well OK! I thought. Answering the manual configuration questions twice is not *so* bad -- I can live with it. I thought. It did it's normal thing: downloaded and partitioned and rebooted. I was getting hopeful. But... After the reboot, the network was not properly configured. It's as if all the information I input (twice) about the network addresses and router addresses and DNS server addresses, all got thrown away and never made it past the reboot. What can I do to help debug this thing!?! Thanks, Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#262198: Partition hard drives fails on powerpc OldWorld PowerMac in 20040729 businesscard install.
Package: installation-reports powerpc businesscard 20040729 OldWorld PowerMac INSTALL REPORT Synopsis: Partition hard drives fails on powerpc OldWorld PowerMac on 20040729 businesscard install. Debian-installer-version: Fill in date and from where you got the image sid_d-i/powerpc/20040729 uname -a: The result of running uname -a on a shell prompt Linux debian 2.6.7-powerpc #1 Sat Jul 10 03:47:45 CEST 2004 ppc GNU/Linux Date: 2004/07/27 23:00 GMT Method: How did you install? businesscard CD-ROM What did you boot off? MacOS-9 via BootX If network install, from where? /etc/apt/sources.list #deb ftp://ftp.debian.org/debian/ sarge main deb ftp://mirrors.usc.edu/pub/linux/distributions/debian/ testing main deb-src ftp://mirrors.usc.edu/pub/linux/distributions/debian/ testing main Proxied? No Machine: Description of machine (eg, IBM Thinkpad R32) OldWorld PowerMac G3 beige minitower Processor: G3 Memory: 384 MB Root Device: IDE? SCSI? IDE Name of device? /dev/hdg Root Size/partition table: Feel free to paste the full partition table, with notes on which partitions are mounted where. /dev/hdg #type name length base ( size ) system /dev/hdg1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hdg2 Apple_Driver43 Macintosh 54 @ 64( 27.0k) Driver 4.3 /dev/hdg3 Apple_Driver43 Macintosh 74 @ 118 ( 37.0k) Driver 4.3 /dev/hdg4 Apple_Driver_IOKit Macintosh512 @ 192 (256.0k) Unknown /dev/hdg5 Apple_Patches Patch Partition 512 @ 704 (256.0k) Unknown /dev/hdg6 Apple_HFS untitled 2097152 @ 1216 ( 1.0G) HFS (MacOS-9) /dev/hdg7 Apple_UNIX_SVR2 root19531251 @ 2098368 ( 9.3G) Linux native (2.4 kernel) /dev/hdg8 Apple_UNIX_SVR2 swap 1953126 @ 21629619 (953.7M) Linux swap /dev/hdg9 Apple_UNIX_SVR2 root19531251 @ 23582745 ( 9.3G) Linux native (2.6 kernel) /dev/hdg10 Apple_Free Extra 277059060 @ 43113996 (132.1G) Free space Block size=512, Number of Blocks=320173056 DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 23, type=0x1 2: @ 118 for 36, type=0x Output of lspci and lspci -n: :00:00.0 0600: 1057:0002 (rev 40) :00:0e.0 0100: 1191:0009 (rev 06) :00:10.0 ff00: 106b:0010 (rev 01) :00:12.0 0300: 1002:4754 (rev 9a) :00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40) :00:0e.0 SCSI storage controller: Artop Electronic Corp ATP865 (rev 06) :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) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[o] Configure network HW: [?] note 1 Config network: [e] note 2 Detect CD: [o] Load installer modules: [o] Detect hard drives: [?] note 1 Partition hard drives: [e] note 3 Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] Comments/Problems: Note 0: Thanks for putting 2.4 back on the CD. Note 1: It still asks for the Linux floppy driver module (twice) at the Detect Network hardware phase and the Detect hardware (looking for hard disks) phase. (See Bug#261463) Note 2: Manual network configuration still doesn't work! (See Bug#261460: Non-DHCP network config step of d-i is broken) I continued using DHCP. Note 3: main menu step partition hard drives fails. Nothing happens and it keeps returning to partition hard drives 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]
Bug#262201: PowerMac (OldWorld) - no driver for onboard SCSI
Package: installation-reports powerpc 20040724 businesscard OldWorld PowerMac kernel-2.6 INSTALL REPORT Debian-installer-version: sid_d-i/powerpc/20040724/sarge-powerpc-businesscard.iso Comments/Problems: The powerpc 2.6 kernel on the 20040724 businesscard CD is missing drivers (modules or built-in) for the Mac onboard SCSI bus. This happens on both my beige G3 minitower and my PowerMac 6500/225. On the G3 the problem manifests as not being able to see a SCSI Zip drive. On the 6500 it can't see any SCSI devices, CD-RW, 4.3 GB hard drive, or Zip. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Is anyone else seeing this? -- Re: Bug#261460: Non-DHCP network config step of d-i is broken
Is this problem only on OldWorld PowerMac's? Or am I just the only person in the world who wants to configure his network interface without DHCP? If this is happening on i386, it would be a show stopper! Please, somebody, give it a try and let me know I'm not going crazy. It doesn't take very long to get to the point where this bug manifests itself, and you don't ever get to the point where you need to touch your hard disk, so it's easy to check. Thanks, Rick On Monday, July 26, 2004, at 01:09 AM, Rick_Thomas wrote: Package: installation-reports:[powerpc][20040724] OldWorld PowerMac INSTALL REPORT Debian-installer-version: Fill in date and from where you got the image sid_d-i/powerpc/20040724/sarge-powerpc-businesscard.iso Comments/Problems: The manual (non-dhcp) configuration option of the config network step is broken. Here is a blow-by-blow account: 1) Boot 2.6 kernel and initrd copied from CD using BootX, with DEBCONF_PRIORITY=medium 2) answer questions til we come to main menu topic Configure the network 3) Answer Auto configure network with DHCP? with no 4) Answer questions til we come to Is this information correct?. Since it is correct, answer yes. 5) This takes us back to the main menu with Configure the network hilighted again! 6) Switching to the F2 console, we see (with ifconfig and route) that the network interface has been configured as we requested. 7) two possibilities: a) If we just hit return: 1) We are asked if we want DHCP (again). Going to console F2 shows that the network has been de-configured. 2) we answer no (again) to the DHCP question, and we go thru the same set of questions again. Winding us back at step 5 (again). b) If we manually (down-arrow key) move to Choose a mirror, and hit return, we wind up at step 7a (again)! Am I doing something wrong? Very strange! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#261463: Missing drivers on powerpc 2.6 businesscard install
On Monday, July 26, 2004, at 09:25 AM, Colin Watson wrote: On Mon, Jul 26, 2004 at 02:00:46AM -0400, Rick_Thomas wrote: The powerpc 2.6 kernel version of the d-i is missing drivers (modules or built-in) for Mac floppy disks and SCSI CD-ROM drives. I've added the floppy modules. Thanks! Installing on a PowerMac/6500 with a TEAC SCSI CD-RW drive, I had to use the 2.4 kernel because the 2.6 kernel couldn't find a driver for the CD. Do you know which module you need for this CD-RW drive? No. All I know is that it works fine with the 2.4 kernel. How can I find out? For what it's worth, the MacOS-9 Apple System Profiler says that it's a CD-W512B (rev 1.0E) manufactured by TEAC. Also for what it's worth, when I boot the 2.6 kernel and let it run up thru detect and mount CD-ROM, then switch to the F2 console and look in /proc and /dev, I do not see any indication of SCSI devices at all. In particular, nothing in /dev/scsi (the directory exists, but there's nothing in it) and nothing mentioning scsi in the /proc/ide subdirectory tree. The machine has a 4GB SCSI disc and an 80 GB IDE dsic, and, while the ide disc is visible at this time, the scsi disc is nowhere to be found (/dev/discs show no trace of it.) When I do cat /proc/scsi/scsi it does not list any attached devices (neither CD-ROM nor 4GB disc, nor anything else). Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#261463: Missing drivers on powerpc 2.6 businesscard install
On Monday, July 26, 2004, at 04:53 PM, Colin Watson wrote: On Mon, Jul 26, 2004 at 02:17:46PM -0400, Rick Thomas wrote: On Monday, July 26, 2004, at 09:25 AM, Colin Watson wrote: On Mon, Jul 26, 2004 at 02:00:46AM -0400, Rick_Thomas wrote: Installing on a PowerMac/6500 with a TEAC SCSI CD-RW drive, I had to use the 2.4 kernel because the 2.6 kernel couldn't find a driver for the CD. Do you know which module you need for this CD-RW drive? No. All I know is that it works fine with the 2.4 kernel. How can I find out? /var/log/syslog on 2.4 might tell you. /var/log/syslog from a recent 2.4 boot is attached to this email. The (to my eyes) seemingly important part is: Jul 26 17:46:48 localhost kernel: SCSI subsystem driver Revision: 1.00 Jul 26 17:46:48 localhost kernel: mesh: configured for synchronous 5 MB/s Jul 26 17:46:48 localhost kernel: mesh: performing initial bus reset... Jul 26 17:46:48 localhost kernel: scsi0 : MESH Jul 26 17:46:48 localhost kernel: mesh: target 0 synchronous at 5.0 MB/s Jul 26 17:46:48 localhost kernel: Vendor: QUANTUM Model: FIREBALL SE4.3S Rev: PJ0A Jul 26 17:46:48 localhost kernel: Type: Direct-Access ANSI SCSI revision: 02 Jul 26 17:46:48 localhost kernel: mesh: target 3 synchronous at 5.0 MB/s Jul 26 17:46:48 localhost kernel: Vendor: TEAC Model: CD-W512SB Rev: 1.0E Jul 26 17:46:48 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 Jul 26 17:46:48 localhost kernel: libata version 0.75 loaded. Jul 26 17:46:48 localhost kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 Jul 26 17:46:48 localhost kernel: SCSI device sda: 8443592 512-byte hdwr sectors (4323 MB) Jul 26 17:46:48 localhost kernel: /dev/scsi/host0/bus0/target0/lun0: [mac] p1 p2 p3 p4 p5 p6 p7 p8 Jul 26 17:46:48 localhost kernel: Attached scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0 Jul 26 17:46:48 localhost kernel: sr0: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray Jul 26 17:46:48 localhost kernel: Uniform CD-ROM driver Revision: 3.12 Jul 26 17:46:48 localhost kernel: sbp2: $Rev: 1074 $ Ben Collins [EMAIL PROTECTED] For what it's worth, the MacOS-9 Apple System Profiler says that it's a CD-W512B (rev 1.0E) manufactured by TEAC. Also for what it's worth, when I boot the 2.6 kernel and let it run up thru detect and mount CD-ROM, then switch to the F2 console and look in /proc and /dev, I do not see any indication of SCSI devices at all. In particular, nothing in /dev/scsi (the directory exists, but there's nothing in it) and nothing mentioning scsi in the /proc/ide subdirectory tree. The machine has a 4GB SCSI disc and an 80 GB IDE dsic, and, while the ide disc is visible at this time, the scsi disc is nowhere to be found (/dev/discs show no trace of it.) When I do cat /proc/scsi/scsi it does not list any attached devices (neither CD-ROM nor 4GB disc, nor anything else). Do you know if it's actually a SCSI drive, or does it run by IDE-SCSI emulation? That said, we do have ide-scsi in the 2.6 initrd. It's actually a SCSI drive. Bus 0 (the on-board SCSI chip), target 3. The 4 GB disk is target 0 on the same SCSI bus. Hope this helps! Rick syslog Description: Binary data
Bug#260225: Sarge installer not recognising partition table for disk larger than 137GB
I don't know if this is relevant, but some IDE controllers only recognize the first 128 GB(binary) = 137*10^9 bytes. Is it possible that your controller has two modes? Windows uses one mode that recognizes the whole disk, and Linux uses the other (compatibility?) mode that only recognizes the first 137 GB(decimal)...? I haven't tried a big disk on an x86 box, but on my Beige G3 PowerMacs, I have to use a SIIG UltraIDE PCI controller to see the tail-ends of my larger disks. The on-board IDE controller that Apple built into those boxes refuses to see beyond 137 GB(decimal). For what it's worth, the SIIG controller works fine with Linux -- as well as with MacOS. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#260225: Sarge installer not recognising partition table for disk larger than 137GB
Controllers that don't believe in disks larger than 137 GB(decimal) report any disk larger than that as being exactly 137 GB in size. This is probably why cfdisk et al are telling you that your partitions go beyond the end of the disk -- as far as they know, the disk ends before the beginning of the partition: at 137 GB. It's a good sign that Windows can see the tail of the disk. That means that the controller is capable of seeing it, even if Linux isn't forcing the right mode to make it do so. It's also a hopeful sign that Knoppix can mount the partitions on the tail of the disk. To see if the problem really lies with parted and/or cfdisk you might try them under Knoppix... Is there a jumper or BIOS setting for the controller (or on the disk itself) to tell it to always use large disk mode? (I don't know what the official name for that mode is -- maybe somebody on the list knows?) That would be worth a try. I know it's possible to use disks larger than 137 GB with Linux -- I'm doing it! Rick On Monday, July 19, 2004, at 08:33 PM, Sara Falamaki wrote: On Mon, Jul 19, 2004 at 04:15:36PM -0400, Rick Thomas wrote: I don't know if this is relevant, but some IDE controllers only recognize the first 128 GB(binary) = 137*10^9 bytes. Is it possible that your controller has two modes? Windows uses one mode that recognizes the whole disk, and Linux uses the other (compatibility?) mode that only recognizes the first 137 GB(decimal)...? Doubt it, as the problem doesn't seem to be recognising the whole disk, 4 parts appear under /dev/discs/disc1/ as expected. I was also able to mount all the partitions in knoppix. An error arises when parted (or cfdisk) try to read the partition table, and die when they think there is a partition after the end of the disk. With parted -s /dev/discs/disc1/disc print I get the message: Error: Can't have a partition outside the disk With cfdisk, doing the same thing, I get: FATAL ERROR: Bad primary partition 3: Partition begins after end-of-disk -S -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Powerpc netinst iso.
Sven, You didn't ask for my opinion, but here it is anyway... As a user, I think splitting netinst/businesscard into separate 2.4 and 2.6 isos is a wonderful idea. The fewer unneeded Megabytes I have to download and burn before I can get started installing the better! I usually know whether I'm going to want to do 2.6 or 2.4 before I start the download process. I think it's an excellent trade-off. Would it allow the the d-i components on the 2.6 iso to use 2.6-specific features at installation time? Would this be useful? Enjoy! Rick On Saturday, July 17, 2004, at 07:58 PM, Sven Luther wrote: Hello manty, The powerpc netinst iso does not contain any 2.6 kernels .debs, and as thus, it fails to install a debian system using 2.6 kernel, since it tries to install some 2.4 kernels and fails. There are two solutions possible : 1) simply add the 2.6 kernels packages + initrd-tools + module-init-tools + mkvmlinuz. This would mean around 30MB of space used i think. Advantage: it is easy and works. Disadvantage: it grows the netinst iso another 30MB, and joeyh thinks that is too much for a netinst iso. = Additionally, in this case i want to modify the build so that the 2.6 kernels are the default ones, and the 2.4 kernels are the alternative ones, accessed via linux24. 2) split the netinst/businesscard isos into 2.4 and 2.6. This means that the isos will shirnk in size, as we gain around 10-15MB of space for removing those kernels. We duplicate the need of isos also. Here again the standard one will be the 2.6 kernel, and the 2.4 one will be marked with the additional 24 par in the name or something. What do you think of it, can you comment on this ? On what is the cost of both solutions from your point of view ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: powerpc status and missing 2.6.7 .udebs and .debs in sarge.
Sven Luther wrote: On Fri, Jul 16, 2004 at 11:45:38AM -0400, Rick_Thomas wrote: On Fri, 2004-07-16 at 11:07, Sven Luther wrote: On Fri, Jul 16, 2004 at 10:55:36AM -0400, Rick_Thomas wrote: Last night I downloaded and installed on my test-machine [beige G3 mini-tower (OldWorld)] using the 2.6.7 kernel from: http://cdimage.debian.org/pub/cdimage-testing/sid_d-i/powerpc/20040715/sarge-powerpc-businesscard.iso What kernel did it install ? 2.6.7 or 2.4.25 ? It/I installed the 2.6.7 kernel and initrd. Well, you used the 2.6 initrd, sure, but how did it install the 2.6.7 kernel packages if those where not on the netinst iso ? I didn't use the netinst iso. For the initial installation boot, I used BootX with the vmlinux and initrd from the 2.6 folder on the businesscard CD. When d-i asked which distribution I wanted to use (stable, testing, unstable) I took testing, which was the default. When d-i asked which mirror I wanted to use, I took ftp.debian.org. When d-i asked which kernel package I wanted to use, I chose 2.6.7-powerpc. That put a kernel and an initrd into /boot. I manually copied that kernel and initrd into the appropriate folders in the System folder in the MacOS-9 partition. Then I allowed d-i to reboot. This (of course) dropped me into MacOS-9 and BootX, which I then told to use the *new* vmlinux-2.6.7-powerpc and initrd.img-2.6.7-powerpc, which rebooted just fine and ran the rest of the installation. Hope that helps! Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
three different sets of daily ISOs -- what's the difference?
There are three (seemingly) different sets of daily ISOs at http://cdimage.debian.org/pub/cdimage-testing/daily/powerpc/20040710/ http://cdimage.debian.org/pub/cdimage-testing/sarge_d- i/powerpc/20040710/ http://cdimage.debian.org/pub/cdimage-testing/sid_d-i/powerpc/20040710/ Can anybody explain what the difference is? And which one should I use for testing? Thanks! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#258907: Kernel 2.6 OldWorld PowerMac businesscard daily CD 2004/07/11 fails initial reboot
Package: installation-reports INSTALL REPORT Debian-installer-version: http://cdimage.debian.org/pub/cdimage-testing/daily/powerpc/20040711/sarge-powerpc-businesscard.iso uname -a: didn't get far enough to get this... Date: early AM EDT Saturday, July 12, 2004 Method: How did you install? What did you boot off? If network install, from where? Proxied? used the BootX bootloader with the 2.6 kernel and initrd from the above CD image Machine: Beige G3 (OldWorld) PowerMac minitower with SIIG Ultra ATA 133/100 Pro IDE PCI card installed Processor: PowerPC G3 Memory: 384 MB Root Device: hdg9 Root Size/partition table: /dev/hdc #type name length base ( size ) system /dev/hdc1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hdc2 Apple_Driver43 Macintosh 54 @ 64( 27.0k) Driver 4.3 /dev/hdc3 Apple_Driver43 Macintosh 74 @ 118 ( 37.0k) Driver 4.3 /dev/hdc4 Apple_Driver_IOKit Macintosh512 @ 192 (256.0k) Unknown /dev/hdc5 Apple_Patches Patch Partition 512 @ 704 (256.0k) Unknown /dev/hdc6 Apple_HFS untitled 2097152 @ 1216 ( 1.0G) HFS (MacOS 9.2) /dev/hdc7 Apple_UNIX_SVR2 root19531251 @ 2098368 ( 9.3G) Linux native (not used) /dev/hdc8 Apple_UNIX_SVR2 swap 1953126 @ 21629619 (953.7M) Linux swap (swap) /dev/hdc9 Apple_UNIX_SVR2 root19531251 @ 23582745 ( 9.3G) Linux native (root) /dev/hdc10 Apple_Free Extra 277059060 @ 43113996 (132.1G) Free space Block size=512, Number of Blocks=320173056 DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 23, type=0x1 2: @ 118 for 36, type=0x Output of lspci and lspci -n: :00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40) :00:0e.0 SCSI storage controller: Artop Electronic Corp ATP865 (rev 06) :00:10.0 Class 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) :00:00.0 Class 0600: 1057:0002 (rev 40) :00:0e.0 Class 0100: 1191:0009 (rev 06) :00:10.0 Class ff00: 106b:0010 (rev 01) :00:12.0 Class 0300: 1002:4754 (rev 9a) 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: [o] Partition hard drives: [*] Note 1 Create file systems:[o] Mount partitions: [o] Install base system:[o] Install boot loader:[ ] Note 2 Reboot: [e] Note 3 Comments/Problems: 1) The first time, I tried with DEBCONF_PRIORITY not set. That time, the Partition Hard Drives phase hung at 22%. I tried switching to the F2 console and doing a ps to see what was going on. I got a Kernel oops for my pains. That needs to be fixed. So I went back and tried again with DEBCONF_PRIORITY=medium. This time I made sure that the HFS filesystem module was loaded when I got the chance. (First time it didn't ask about loading modules due to the default priority setting.) This time around partitioning went without a hitch -- leading me to believe that the previous time it hung trying to identify my HFS partition where I keep MacOS-9 (and BootX). 2) I skipped installing the quik bootloader, since I was using BootX instead. Just before the reboot, I switched to the F2 console and mounted my HFS MacOS partition so I could copy the kernel and initrd images from /target/boot into the appropriate folders for later use by BootX. initrd.img-2.6.6-powerpc and vmlinux-2.6.6-powerpc... 3) After the reboot (which, of course, took me into MacOS and BootX) I told BootX to use the kernel and initrd files I had saved in the last step. I used no kernel arguments other than those necessary to make the video work. The Linux boot failed. The last few lines of the console messages were: initrd-tools: 0.1.70 /sbin/init: 356: cannot open bin/root: No such file umount: bin: not mounted /sbin/init: 358: cannot create proc/sys/kernel/real-root-dev: Directory nonexistent cat: proc/cmdline: no such file or directory NET: Registered protocol family 1 umount: proc: not mounted pivot_root: No such file or directory /sbin/init: 424: cannot open dev/console: No such file Kernel panic: attempting to kill init! 0Rebooting in 180 seconds.. Help? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#258908: Kernel 2.6 OldWorld PowerMac sid_d-i businesscard daily CD 2004/07/11 fails installing unstable
Package: installation-reports INSTALL REPORT Debian-installer-version: http://cdimage.debian.org/pub/cdimage-testing/daily/powerpc/20040711/sarge-powerpc-businesscard.iso uname -a: didn't get far enough to get this... Date: early AM EDT Saturday, July 12, 2004 Method: How did you install? What did you boot off? If network install, from where? Proxied? I used the BootX bootloader with the 2.6 kernel and initrd from the above CD image Machine: Beige G3 (OldWorld) PowerMac minitower with SIIG Ultra ATA 133/100 Pro IDE PCI card installed Processor: PowerPC G3 Memory: 384 MB Root Device: hdg9 Root Size/partition table: /dev/hdc #type name length base ( size ) system /dev/hdc1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hdc2 Apple_Driver43 Macintosh 54 @ 64( 27.0k) Driver 4.3 /dev/hdc3 Apple_Driver43 Macintosh 74 @ 118 ( 37.0k) Driver 4.3 /dev/hdc4 Apple_Driver_IOKit Macintosh512 @ 192 (256.0k) Unknown /dev/hdc5 Apple_Patches Patch Partition 512 @ 704 (256.0k) Unknown /dev/hdc6 Apple_HFS untitled 2097152 @ 1216 ( 1.0G) HFS (MacOS 9.2) /dev/hdc7 Apple_UNIX_SVR2 root19531251 @ 2098368 ( 9.3G) Linux native (not used) /dev/hdc8 Apple_UNIX_SVR2 swap 1953126 @ 21629619 (953.7M) Linux swap (swap) /dev/hdc9 Apple_UNIX_SVR2 root19531251 @ 23582745 ( 9.3G) Linux native (root) /dev/hdc10 Apple_Free Extra 277059060 @ 43113996 (132.1G) Free space Block size=512, Number of Blocks=320173056 DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 23, type=0x1 2: @ 118 for 36, type=0x Output of lspci and lspci -n: :00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40) :00:0e.0 SCSI storage controller: Artop Electronic Corp ATP865 (rev 06) :00:10.0 Class 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) :00:00.0 Class 0600: 1057:0002 (rev 40) :00:0e.0 Class 0100: 1191:0009 (rev 06) :00:10.0 Class ff00: 106b:0010 (rev 01) :00:12.0 Class 0300: 1002:4754 (rev 9a) 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: [o] Partition hard drives: [e] Note 1 Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] Comments/Problems: 1) I had so much fun trying to install the 2.6.6 kernel with the testing debs, I decided to try the unstable debs. I used DEBCONF_PRIORITY=medium, and made sure the HFS modules were loaded. When it got to the Partition disks phase, the progress bar got to around 22% then it went blank and returned to the main menu screen with Partition disks hilighted. Hitting return at this point blanks the screen for a few seconds then returns to the main menu with the same thing hilighted. I'll _never_ get a chance to partition my disk at this rate... Help? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Minutes of #debian-boot meeting of 20040706 (was: Debian Installer IRCmeeting on Tuesday 07/06 20:00 UTC)
Rick Thomas wrote: Joey Hess wrote: Rick Thomas wrote: Last night I tried installing both 2.4 and 2.6 on my OldWorld Beige G3. (using the sarge netinst daily CD from 2004/07/07) Neither worked, but for different reasons. I've sent installation reports to [EMAIL PROTECTED] but they haven't yet shown up on the list with a bug number. kernel 2.6 died trying to discover disk hardware -- segfaults. kernel 2.4 died trying to install a kernel -- something about missing dependencies involving kernel modules package. I don't know about your 2.6 problem, but 0707 was a bad day to be testing, since none of the images install at all. The second problem you encountered is likely due to that, though I'm not 100% sure. OK, I'll try again with a later iso. Is 0708 likely to be any better? The 0708 netinst CD using the 2.6 kernel gave me the same symptoms -- segfaults trying to discover disk hardware. I think discover1 is not playing well with the 2.6 kernel. The 0708 netinst CD using the 2.4 kernel is feeling much better thankyou! The only strange thing it's done (so far) is to try to install quik on my OldWorld (beige G3) PowerMac. It's not supposed to do that, is it? Installation reports are being submitted with the details. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#258541: Kernel 2.6 OldWorld PowerMac netinst daily CD 2004/07/08 fails toinstall
Package: installation-reports INSTALL REPORT Debian-installer-version: http://cdimage.debian.org/pub/cdimage-testing/daily/powerpc/20040708/sarge-powerpc-netinst.iso uname -a: didn't get far enough to get this... Date: early AM EDT Saturday, July 10, 2004 Method: How did you install? What did you boot off? If network install, from where? Proxied? used the BootX botloader with the 2.6 kernel and initrd from the above CD image Machine: Beige G3 (OldWorld) PowerMac with SIIG Ultra ATA 133/100 Pro IDE PCI card installed Processor: PowerPC G3 Memory: 384 MB Root Device: hdc9 Root Size/partition table: /dev/hdc #type name length base ( size ) system /dev/hdc1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hdc2 Apple_Driver43 Macintosh 54 @ 64 ( 27.0k) Driver 4.3 /dev/hdc3 Apple_Driver43 Macintosh 74 @ 118 ( 37.0k) Driver 4.3 /dev/hdc4 Apple_Driver_IOKit Macintosh512 @ 192 (256.0k) Unknown /dev/hdc5 Apple_Patches Patch Partition 512 @ 704 (256.0k) Unknown /dev/hdc6 Apple_HFS untitled 2097152 @ 1216 ( 1.0G) HFS (MacOS 9.2) /dev/hdc7 Apple_UNIX_SVR2 root19531251 @ 2098368 ( 9.3G) Linux native (not used) /dev/hdc8 Apple_UNIX_SVR2 swap 1953126 @ 21629619 (953.7M) Linux swap (swap) /dev/hdc9 Apple_UNIX_SVR2 root19531251 @ 23582745 ( 9.3G) Linux native (root) /dev/hdc10 Apple_Free Extra 277059060 @ 43113996 (132.1G) Free space Block size=512, Number of Blocks=320173056 DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 23, type=0x1 2: @ 118 for 36, type=0x Output of lspci and lspci -n: :00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40) :00:0e.0 SCSI storage controller: Artop Electronic Corp ATP865 (rev 06) :00:10.0 Class 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) :00:00.0 Class 0600: 1057:0002 (rev 40) :00:0e.0 Class 0100: 1191:0009 (rev 06) :00:10.0 Class ff00: 106b:0010 (rev 01) :00:12.0 Class 0300: 1002:4754 (rev 9a) 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: [ ] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] Comments/Problems: detect hardware phase (the one after the network config phase) failed. The last few lines of the log file: main-menu[409]: DEBUG: menu item 'hw-detect-full' selected main-menu[409]: DEBUG: configure hw-detect-full, status 2 hw-detect: using discover version 1. hw-detect: Detecting hardware... main-menu[409]: (process 6328) Segmentation fault(occurs 14 times) main-menu[409]: WARNING**: Configuring 'hw-detect-full' failed with error code 139 main-menu[409]: WARNING**: menu item 'hw-detect-full' failed. 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]
Bug#258545: OldWorld PowerMac netinst daily CD 2004/07/08 success (mostly)
Package: installation-reports INSTALL REPORT Debian-installer-version: http://cdimage.debian.org/pub/cdimage-testing/daily/powerpc/20040708/sarge-powerpc-netinst.iso uname -a: Linux debian 2.4.25-powerpc #1 mer avr 14 15:38:38 CEST 2004 ppc GNU/Linux Date: 11 PM EDT July 9, 2004 Method: How did you install? What did you boot off? If network install, from where? Proxied? used the BootX botloader with the 2.4 kernel and initrd from the above CD image Machine: Beige G3 (OldWorld) PowerMac with SIIG Ultra ATA 133/100 Pro IDE PCI card installed Processor: PowerPC G3 Memory: 384 MB Root Device: hdc9 Root Size/partition table: /dev/hdc #type name length @ base ( size ) system /dev/hdc1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hdc2 Apple_Driver43 Macintosh 54 @ 64( 27.0k) Driver 4.3 /dev/hdc3 Apple_Driver43 Macintosh 74 @ 118 ( 37.0k) Driver 4.3 /dev/hdc4 Apple_Driver_IOKit Macintosh512 @ 192 (256.0k) Unknown /dev/hdc5 Apple_Patches Patch Partition 512 @ 704 (256.0k) Unknown /dev/hdc6 Apple_HFS untitled 2097152 @ 1216 ( 1.0G) HFS (MacOS 9.2) /dev/hdc7 Apple_UNIX_SVR2 root19531251 @ 2098368 ( 9.3G) Linux native (not used) /dev/hdc8 Apple_UNIX_SVR2 swap 1953126 @ 21629619 (953.7M) Linux swap (swap) /dev/hdc9 Apple_UNIX_SVR2 root19531251 @ 23582745 ( 9.3G) Linux native (root) /dev/hdc10 Apple_Free Extra 277059060 @ 43113996 (132.1G) Free space Block size=512, Number of Blocks=320173056 DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 23, type=0x1 2: @ 118 for 36, type=0x Output of lspci and lspci -n: :00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40) :00:0e.0 SCSI storage controller: Artop Electronic Corp ATP865 (rev 06) :00:10.0 Class 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) :00:00.0 Class 0600: 1057:0002 (rev 40) :00:0e.0 Class 0100: 1191:0009 (rev 06) :00:10.0 Class ff00: 106b:0010 (rev 01) :00:12.0 Class 0300: 1002:4754 (rev 9a) 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: [o] Partition hard drives: [o] Create file systems:[o] Mount partitions: [o] Install base system:[o] Install boot loader:[e] Reboot: [o] Comments/Problems: Everything went like clockwork except that it tried to install the quik bootloader. IT's not supposed to do that for OldWorld machines, is it? This is a beige G3 minitower. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#258545: OldWorld PowerMac netinst daily CD 2004/07/08 success (mostly)
On Saturday, July 10, 2004, at 07:33 AM, Colin Watson wrote: On Sat, Jul 10, 2004 at 03:46:29AM -0400, Rick Thomas wrote: Everything went like clockwork except that it tried to install the quik bootloader. IT's not supposed to do that for OldWorld machines, is it? This is a beige G3 minitower. quik is an OldWorld bootloader, so yes, it is supposed to do that. Did something go wrong with the bootloader installation? (For what it's worth, if the bootloader installation was successful then this will be the first success report we've had with quik-installer, which would be nice.) Unfortunately, something _did_ go wrong with installing the quik bootloader. I guess you could say that this was unfortunate for d-i, but it was definitely fortunate for me. I prefer to use macOS-9 and BootX for my bootloader chores on my OldWorld machines; it gives me an implicit dual-boot capability that I like. Also, I don't like the fact that quik mucks about with open-firmware settings; it's just too easy to get a non-bootable system that way. When the quik install phase failed, I went ahead and told d-i to continue without a bootloader, and everything was easy after that. Personally, I'd much prefer that d-i not try to install quik by default on OldWorld machines. My reasoning goes this way: Because of the licensing problems with miboot, it's not possible to distribute a bootable CD or CD/floppy combo for Debian at this time. Aside: It is _possible_ for the end-user to construct a bootable CD and/or CD/floppy-combo using piece parts that are freely available on the web but not free-as-in-speech enough for putting into a Debian distribution. While it is possible, it isn't easy, and it requires tools that are not free by any definition, e.g. MacOS and Toast. Consequently, the only practical way for the average user to install Debian on an OldWorld machine is with MacOS-9 and BootX. Given that this makes MacOS/BootX a practical requirement anyway, why muddy the waters with quik? Especially so since we can't seem to get it working in the first place, and in the second place it has distasteful side-effects in that it messes with the Open Firmware in dangerous ways? I know it's possible to bypass quik by installing with DEBCONF_PRIORITY=medium, but I wanted to try the default setup to see if there were problems that the normal user would encounter. The answer is: There is a problem. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Minutes of #debian-boot meeting of 20040706 (was: Debian Installer IRCmeeting on Tuesday 07/06 20:00 UTC)
powerpc === In unstable, 2.4 and 2.6 both work fine on newworld pmac. 2.4 oldworld pmac is unbootable, but then again it always has been. It is reasonable to move for a 2.6 powerpc kernel for sarge, for all currently supported architectures, the support for those is better, and upstream (that is the linuxppc folk) as well as our own kernel powerpc specialist are favoring 2.6 development and bug fix over 2.4. Last night I tried installing both 2.4 and 2.6 on my OldWorld Beige G3. (using the sarge netinst daily CD from 2004/07/07) Neither worked, but for different reasons. I've sent installation reports to [EMAIL PROTECTED] but they haven't yet shown up on the list with a bug number. kernel 2.6 died trying to discover disk hardware -- segfaults. kernel 2.4 died trying to install a kernel -- something about missing dependencies involving kernel modules package. oldworld has a bootloader installer so if you boot it using BootX that should theoretically be OK, but there's been zero testing. BootX depends on non-free macos 9. Booting either 2.4 or 2.6 via BootX works just fine, thanks! I don't mind giving over a few hundred Mbytes (on a 160 GByte disk!) to MacOS-9 in exchange for a stable boot-loader environment. No RC issues, apart possibly from Sven's keymap thing. Depends on whether you count the two bugs I mentioned above. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#258422: Kernel 2.6 OldWorld PowerMac netinst daily CD 2004/07/07 fails toinstall
Package: installation-reports INSTALL REPORT Debian-installer-version: http://cdimage.debian.org/pub/cdimage-testing/daily/powerpc/20040707/sarge-powerpc-netinst.iso uname -a: didn't get far enough to get this... Date: 11 PM EDT July 9, 2004 Method: How did you install? What did you boot off? If network install, from where? Proxied? used the BootX botloader with the 2.6 kernel and initrd from the above CD image Machine: Beige G3 (OldWorld) PowerMac with SIIG Ultra ATA 133/100 Pro IDE PCI card installed Processor: PowerPC G3 Memory: 384 MB Root Device: hdc9 Root Size/partition table: /dev/hdc #type name length base ( size ) system /dev/hdc1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hdc2 Apple_Driver43 Macintosh 54 @ 64 ( 27.0k) Driver 4.3 /dev/hdc3 Apple_Driver43 Macintosh 74 @ 118 ( 37.0k) Driver 4.3 /dev/hdc4 Apple_Driver_IOKit Macintosh512 @ 192 (256.0k) Unknown /dev/hdc5 Apple_Patches Patch Partition 512 @ 704 (256.0k) Unknown /dev/hdc6 Apple_HFS untitled 2097152 @ 1216 ( 1.0G) HFS (MacOS 9.2) /dev/hdc7 Apple_UNIX_SVR2 root19531251 @ 2098368 ( 9.3G) Linux native (not used) /dev/hdc8 Apple_UNIX_SVR2 swap 1953126 @ 21629619 (953.7M) Linux swap (swap) /dev/hdc9 Apple_UNIX_SVR2 root19531251 @ 23582745 ( 9.3G) Linux native (root) /dev/hdc10 Apple_Free Extra 277059060 @ 43113996 (132.1G) Free space Block size=512, Number of Blocks=320173056 DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 23, type=0x1 2: @ 118 for 36, type=0x Output of lspci and lspci -n: :00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40) :00:0e.0 SCSI storage controller: Artop Electronic Corp ATP865 (rev 06) :00:10.0 Class 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) :00:00.0 Class 0600: 1057:0002 (rev 40) :00:0e.0 Class 0100: 1191:0009 (rev 06) :00:10.0 Class ff00: 106b:0010 (rev 01) :00:12.0 Class 0300: 1002:4754 (rev 9a) 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: [ ] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] Comments/Problems: detect hardware phase (the one after the network config phase) failed. The last few lines of the log file: main-menu[409]: DEBUG: menu item 'hw-detect-full' selected main-menu[409]: DEBUG: configure hw-detect-full, status 2 hw-detect: using discover version 1. hw-detect: Detecting hardware... main-menu[409]: (process 6328) Segmentation fault(occurs 14 times) main-menu[409]: WARNING**: Configuring 'hw-detect-full' failed with error code 139 main-menu[409]: WARNING**: menu item 'hw-detect-full' failed. 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]
Re: Minutes of #debian-boot meeting of 20040706 (was: Debian Installer IRCmeeting on Tuesday 07/06 20:00 UTC)
Joey Hess wrote: Rick Thomas wrote: Last night I tried installing both 2.4 and 2.6 on my OldWorld Beige G3. (using the sarge netinst daily CD from 2004/07/07) Neither worked, but for different reasons. I've sent installation reports to [EMAIL PROTECTED] but they haven't yet shown up on the list with a bug number. kernel 2.6 died trying to discover disk hardware -- segfaults. kernel 2.4 died trying to install a kernel -- something about missing dependencies involving kernel modules package. I don't know about your 2.6 problem, but 0707 was a bad day to be testing, since none of the images install at all. The second problem you encountered is likely due to that, though I'm not 100% sure. OK, I'll try again with a later iso. Is 0708 likely to be any better? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian Sarge on oldworld Powermac?
Reset (zap) the PRAM. Turn the power off, then turn it on with the Command-Option-P-R keys (all of them) held down. Hold the keys down til it bongs a couple of times, then release and it should boot normally from floppy. Rick On Sunday, June 13, 2004, at 05:51 AM, matt-land.com wrote: On Sun, 13 Jun 2004, Rick_Thomas wrote: On Sat, 2004-06-12 at 05:43, Ralf Schlatterbeck wrote: However, you need to keep in mind that quik is very brittle -- it breaks easily -- and when it does it leaves you with a non-bootable machine. It seems I have one of those non-bootable machines you speak of. After the installer (v3.0) finished, the machine never booted. Booting from a floppy nolonger works either. Any way I can boot from a floppy? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#244099: your installation report
On Tuesday, April 20, 2004, at 01:47 AM, Joey Hess wrote: Note that if you hit the go back button at the hostname question, you'll get to the main menu, and hitting enter will let you choose how to configure it. Thanks! That solves my problem. However, we still need to get some way to set the priority (and other boot-time parameters) for OldWorld PowerMacs doing floppy based installs. What component should I direct a bug report to on this subject? Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#244394: FWD: eject-udeb
Sven Luther wrote:
snip
Still, i wonder were the right place would be for this .udeb :
1) in the cdrom iinitrd to have access to it as soon as possible ?
(it doesn't seem to appear though in the first stage of
debian-installer's main menu, don't know why though).
2) have it be downloaded with the other installer components.
Well, if it is going to be used to eject floppy disks (as well as CD
ROMs) it needs to be on the root floppy, so it can be used to eject the
root floppy when asking for the {net/cd}-drivers floppy. I know space is
tight there, but...
Rick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#244367: PowerPC install from boot floppy mostly successful - still some problems.
I'll give it a try this evening (US/Eastern time zone) Enjoy! Rick Matt Kraai wrote: On Sun, Apr 18, 2004 at 04:04:13AM -0400, Rick_Thomas wrote: 1) It automatically ejected the boot floppy when asking for the root floppy. Thanks for that, whoever put that patch in. However, when calling for the drivers floppy, it did not eject the root floppy. I had to use the paper-clip trick to eject it so I could insert the net-drivers floppy. It really should eject the root floppy automatically when it's done using it. Would you please run eject -f fd0 on the second virtual console and report back whether or not this ejects the floppy? -- Matt Kraai[EMAIL PROTECTED]http://ftbfs.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: d-i, FAI, quik-installer for oldworld, debconf4
Holger Levsen wrote: snip I would like to start hacking a quik-installer (for oldworld powerpc) now, but I am a little unsure how to test it on my own: Since my only oldworld system to develop with is a pmac4400 at the moment I have to boot if from floppies. Then I'll usually insert the net-drivers floppy and install from a debian-mirror (which includes daily built d-i packages). Should/can I use the cd-drivers floppy and build my own cd-iso-image, which will then include my unsubmitted new code ?? Holger, I would like to volunteer to help you with testing. I have a beige G3 minitower (oldworld) and a PowerMac 6500 (oldworld) that I have dedicated to Debian installer testing for the time being. I can also occasionally borrow a newworld machine for testing (as long as I don't have to partition the disk). I have facilities for downloading and burning ISO images of CDs and/or floppy disks. Will that help? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#243166: eject should provide a .udeb, so that an eject menu item can be found in debian-installer.
Sven Luther wrote: On Mon, Apr 12, 2004 at 12:28:11AM +0200, Frank Lichtenheld wrote: tags 243166 moreinfo help thanks On Sun, Apr 11, 2004 at 03:52:44PM +0200, Sven Luther wrote: A .udeb package would allow to eject the cdrom during the install. Would be particularly usefull for uncompleted pmac installs, since it is not evident to eject the cdrom by hand. I prepared a prelimary version, you can get it from deb-src http://www.lichtenheld.de/debian ./ Ok, i will test it. I'm unsure however what functionality is really needed: - Should it be possible to manually enter a device name? When booting from floppy disk -- as is pretty much required if you are using an oldworld PowerMac -- it is frequently necessary to eject the floppy disk. Currently, one has to use a paperclip for this because the Mac hardware designers did not provide a big fat eject button on their floppy drives. So, yes, there needs to be a way to eject things other than the cdrom. And (IMHO) it needs to be on the menu at priority=medium and lower. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: d-i oldworld mac: floppies fail on 4400/200 and 7200/75
On Sunday, April 11, 2004, at 01:56 AM, Sven Luther wrote: Ok. Now wee need to see why this happens. It seems that nobody was able to make it work with the boot floppies built by me, is that exact ? Only by those built by Jeremie. We need to find out why. Jeremie, did you modify the kernel config somehow ? Or maybe something is not ok with our builds or something. Friendly, Sven Luther I believe that what you say is the case. It worked for me with Jeremie's floppy images, but not with Sven's. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: d-i oldworld mac: floppies fail on 4400/200 and 7200/75
Hi! See comments interleaved below... Rick Malte Cornils wrote: Hi Rick, On Fri, Apr 09, 2004 at 01:37:21AM -0400, Rick Thomas wrote: Errors like that are usually symptomatic of a dirty/dusty floppy drive. In particular, if the boot floppy is ejected, it means that the firmware got an error trying to read it, or couldn't find the magic numbers in the magic places that it was expecting from a real-live Macintosh boot floppy. The boot floppy is ejected after the miboot run (the little icon with the penguin) had finished and few more seconds (enough time for the kernel to boot and display the usual insert root disk message) have passed. Floppy ejection at this point is normal and could also mean that the kernel boots fine, only that the local console is broken. In my experience, the floppy is *not* automatically ejected when the insert root disk message comes up. I always have to use the paper-clip trick to get the disk out so I can put the root disk in. (Again, in my experience) the only time the disk is automatically ejected is when the firmware has a problem reading it. This is with two machines -- a beige G3 mini-tower and a PowerMac 6500/225. You should clean *both* the drive you will be writing the disk on, and the one you will be reading it on. That is the second attempt was made on completely unrelated systems (both the PC generating the floppy and the Mac were different). Disk was made apparently without errors, and cmp showed no differences. (I was more careful with that after your last mail regarding that topic). That's a good sign. But (as you've seen) not conclusive -- the reading drive could be dirty (or out of calibration -- which is actually more serious because the only fix for that is to replace it. It would cost more to have it recalibrated than the drive's worth.) Also, buy a box of new floppies. Don't use floppys that have been sitting around the house for a few years. They accumulate dust over time and the oxide deteriorates. Yeah, that was when I was shocked how (relatively) expensive floppies had become now that almost no one uses them anymore. Sigh! So true... I will buy a cleaning set soon, I think you'll see a dramatic difference when you do. I couldn't get anything to work at all until I'd cleaned all the drives twice! but I would appreciate it if someone could test the current images (Holger?) on similar hardware. I'll test the latest daily-build boot floppies this weekend on both of my test machines and send you a report. Yours -Malte Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: d-i oldworld mac: floppies fail on 4400/200 and 7200/75
Sven Luther wrote: On Fri, Apr 09, 2004 at 01:37:21AM -0400, Rick Thomas wrote: Malte, Rick, does this mean that the daily build floppies work for you now ? Friendly, Sven Luther Yes. It reads all the floppies and launches d-i as expected. I still have problems with d-i once it gets launched. Specifically: Booting off of floppy, there is no way to invoke ...PRIORITY=medium mode. It just does the default. In default PRIORITY mode it always does: the dhcp thing -- which succeeds, but it give me a random IP address -- I need to be able to specify the IP address manually. I think some other folks have noted this and filed a bug report. it always tries to install yaboot (even though archdetect says it's an oldworld machine. I think something's broken in the yaboot installer) I've filed a bug report. In summary, there are still problems with d-i on oldworld machines, but the floppy boot stuff works just fine. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: d-i oldworld mac: floppies fail on 4400/200 and 7200/75
Frans Pop wrote: On Friday 09 April 2004 20:40, you wrote: Booting off of floppy, there is no way to invoke ...PRIORITY=medium mode. It just does the default. Are you sure? You have to enter 'linux DEBCONF_PRIORITY=medium' Frans This is OldWorld PowerMac. Booting off of floppy uses the miboot bootloader. It's not like lilo or grub on i386. There's no point in the process where you get to enter that kind of stuff. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: d-i oldworld mac: floppies fail on 4400/200 and 7200/75
Malte, Errors like that are usually symptomatic of a dirty/dusty floppy drive. In particular, if the boot floppy is ejected, it means that the firmware got an error trying to read it, or couldn't find the magic numbers in the magic places that it was expecting from a real-live Macintosh boot floppy. Buy and use a floppy drive cleaning kit (a bottle of isopropanol and a floppy-like thing with a non-abrasive fibrous disk in place of the usual shiny oxide coated disk). Don't be afraid to use it couple of times if you continue to have problems after the first cleaning. You shouldn't need more than two or three cleanings, though. You should clean *both* the drive you will be writing the disk on, and the one you will be reading it on. Also, buy a box of new floppies. Don't use floppys that have been sitting around the house for a few years. They accumulate dust over time and the oxide deteriorates. Finally, when you write the image to disk, always read it back to make sure you have a good copy. If you didn't get a good copy, throw away that floppy disk and use a different one. Thus: dd if=boot.img of=/dev/fd0 bs=1024 sync cmp /dev/fd0 boot.img Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Fw: Request for review of partman-newworld
Frans Pop wrote: Hello Rick, Are you still planning to work on the manual for Macs? If so, could you take a look at the text below, snip Yes I am. I got side-tracked for a while in testing d-i on old-world Macs. Thanks for the words. I'll take a look at it this weekend. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian-installer, older hardware, boot loaders, miboot amiboot ..
I just had an interesting conversation with an Apple developer (Apple employee) regarding the legal status of the boot sector for oldworld Macs. He pointed out that Darwin runs (and boots) on (at least) the beige G3, and that's oldworld. I don't know anything about Darwin except that it's from Apple, it runs on PowerMacs, and it's open source, but he (and now I) wondered if the open source boot code for Darwin would do what we're looking for. Just a thought? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#242144: installation-reports: OldWorld PowerMac install (sarge) dies trying to install bootloader
On Monday, April 5, 2004, at 07:12 AM, Colin Watson wrote: On Sun, Apr 04, 2004 at 04:29:14PM -0400, Rick Thomas wrote: Subject: installation-reports: OldWorld PowerMac install (sarge) dies trying to install bootloader The installer should automatically recognize the OldWorld subarchitecture and do the equivalent of continue without... bootloader. It's supposed to do this; the yaboot-installer udeb is not even supposed to be installable on oldworld systems. What does 'archdetect' say on your system? archdetect reports powerpc/powermac_oldworld In real life, it's a beige G3 mini-tower. Hope this helps, Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#242143: boot-floppy: no way to do expert mode boot from floppy on OldWorld PowerMac (at least)
Package: boot-floppy Severity: normal Subject: boot-floppy: no way to do expert mode boot from floppy on OldWorld PowerMac (at least) On OldWorld PowerPC Macintoshes there is no way for a user to do an expert mode boot starting from the boot floppys. I suppose theoretically that one can do things with Open Firmware to pass a DEBCONF_PRIORITY= to the kernel, but that's more complicated than it needs to be. Also, there are OldWorld models whose Open Firmware is so badly broken that this trick wouldn't work. Is this a problem for other architectures too? If so, those architectures probably don't have the luxury of Open Firmware. For those architectures, this is a serious problem. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 2.4.25-powerpc Locale: LANG=C, LC_CTYPE=C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#242144: installation-reports: OldWorld PowerMac install (sarge) dies trying to install bootloader
Package: installation-reports Severity: normal Subject: installation-reports: OldWorld PowerMac install (sarge) dies trying to install bootloader On OldWorld PowerPC Macs the yaboot bootloader doesn't work. Without resorting to expert mode (DEBCONF_PRIORITY=medium or better) there is no way to prevent the d-i from trying to install yaboot. The installer should automatically recognize the OldWorld subarchitecture and do the equivalent of continue without... bootloader. The current workaround is to do a ...PRIORITY=medium install and specify continue without... immediately after partitioning and formatting the disk, and before it attempts to install yaboot. This works, if you remember to do it, but the main menu doesn't help. As currently configured, the continue without... option is mis-placed in the main menu *after* the step that attempts to install yaboot -- i.e. too late to do any good. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 2.4.25-powerpc Locale: LANG=C, LC_CTYPE=C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#241516: install-report success (sort of) on OldWorld PowerMac
Package: installation-reports INSTALL REPORT Debian-installer-version: Date: daily for powerpc for March 30, 2004. Image from: http://gluck.debian.org/cdimage/testing/sarge_d-i/powerpc/20040330/sarge-powerpc-netinst.iso uname -a: Linux debian 2.4.25-powerpc #1 ven mar 19 19:29:26 CET 2004 ppc GNU/Linux Date: March 30, 2004 between Midnight and 4AM Eastern US time. Method: How did you install? BootX -- with DEBCONF_PRIORITY=medium -- see step-by-step description below... What did you boot off? MacOS 9.2.2 via BootX with kernel and initrd.gz from the CD with the CD in the drive If network install, from where? ftp.us.debian.org Proxied? No Machine: PowerMacintosh G3 (beige minitower) Processor: PowerPC G3 Memory: 192 MB Root Device: IDE /dev/hdc8 Root Size/partition table: # mac-fdisk -l /dev/hdc #type name length base ( size ) system /dev/hdc1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/hdc2Apple_Driver_ATA Macintosh 54 @ 64 ( 27.0k) Unknown /dev/hdc3Apple_Driver_ATA Macintosh 74 @ 118 ( 37.0k) Unknown /dev/hdc4 Apple_Driver_IOKit Macintosh512 @ 192 (256.0k) Unknown /dev/hdc5 Apple_Patches Patch Partition 512 @ 704 (256.0k) Unknown /dev/hdc6 Apple_HFS MacOS2097152 @ 1216 ( 1.0G) HFS (MacOS system BootX) /dev/hdc7 Apple_HFS boot 2097152 @ 2098368 ( 1.0G) HFS (for later use with miboot or quik) /dev/hdc8 Apple_UNIX_SVR2 root41943040 @ 4195520 ( 20.0G) Linux native (ext3) /dev/hdc9swap swap 2097152 @ 46138560 ( 1.0G) Linux swap (swap) /dev/hdc10 Apple_Free Extra 220199743 @ 48235712 (105.0G) Free space Block size=512, Number of Blocks=268435454 DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 21, type=0x701 2: @ 118 for 34, type=0xf8ff Output of lspci: # lspci 00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40) 00:10.0 Class 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) 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] manually -- my local DHCP is flakey Detect CD: [O] Load installer modules: [E] detected hardware and presented a list of candidate modules to load. This all worked OK but it seemed to want to load the same list of modules more than once at different points in the process. Detect hard drives: [O] Partition hard drives: [O] manually -- so as not to disrupt the MacOS partiton already on the disk. Create file systems:[O] Mount partitions: [O] Though I had to fill in /etc/fstab manually. It did not do that automatically (see below) Install base system:[O] Install boot loader:[E] I had to tell it not to install a bootloader. OldWorld PowerMacs can't handle yaboot. (see below) Reboot: [E] This was a bit tricky because it didn't fill in /etc/fstab before re-booting (see below) Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. When I tried it without DEBCONF_PRIORITY=medium it blew up trying to install the yaboot bootloader. Joey Hess wrote: I'm suprised this didn't already work; we have an option that is supposed to kick in if no other bootloader installer is available. It should have shown up on the menu as Continue without boot loader, or been automatically run. There is a continue without boot loader option on the main menu, but the main menu doesn't show up by default. You have to ask for it in the kernel boot options -- or wait for an error to occur. In any case, it wasn't obvious when or how I was supposed to invoke continue without..., and before I knew what was happening, the bootloader installer had blown up in my face. So I set priority to medium and tried again following these steps... 1) Install MacOS (8.x or 9.x) in an HFS (*not* HFS+) partition. 2) Install BootX in that partition. 3) Get the kernel and initrd.gz from the latest nightly build businesscard CD and put them in the appropriate places in the system folder of the MacOS partition. Leave the businesscard CD in the drive. 4) Run BootX to load that kernel and ram-disk. 5) Answer questions as appropriate. 6)
Bug#241228: Oldworld from floppy, installing the kernel fails
Sven Luther wrote: Another solution would be for base-installer to install the -powerpc kernel on your box too, since the main reason to use the -powerpc-small kernel is so that it will fit on a floppy with miboot. Would it be possible to restrict use of -powerpc-small kernel to just the floppy with miboot? The -powerpc' kernel works great for me with BootX, and I'd rather not have to deal with loading drivers if I can avoid it. Especially when the IDE disk driver (and the like) are so commonly needed that they are going to be built-in to any kernel that doesn't have to fit on a 1.4MB floppy. Thanks, Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#241228: Oldworld from floppy, installing the kernel fails
On Thursday, April 1, 2004, at 05:57 PM, Holger Levsen wrote: another mail, same topic: Is there support for setting open firmware values in debian-installer at the moment ? Not yet, but you are welcome to provide patches. We'll see, I will try to setup a d-i build this weekend or next week (should I start with i386 or is it equally easy on powerpc?), but I've also got some offline stuff todo... This would be a *very* useful thing to have. Some (most?) OldWorld Apple PowerMac models require open firmware tweaking to get them to boot Linux without the use of MacOS. And all the existing high-level(*) ways of tweaking open firmware parameters require booting either full-blown Linux or full-blown MacOS. For what it's worth, i386 doesn't use open firmware... So I'd guess that PowerPC is a good place to start. Apple has provided us with an amazing number of different open firmware implementations (typically at least a couple per each machine model) with an amazing number of different and mutually incompatible peculiarities. So I'd guess that any project that allowed setting open firmware parameters from a boot floppy would have to (at least optionally) take user input online (i.e. from the keyboard) and allow for off-line configuration as well (when -as happens- the open firmware is so badly broken that even keyboard input is impossible before patches are installed -- I'm talking here about those early PowerMac models that default to having the open-firmware console on the serial tty port.) It would be incredibly useful to have something that took all (known) model-specific peculiarities into account (and was flexible enough to deal with unknown ones) to provided a uniform, model-independent user interface, that could be used in the early phases of booting from a floppy. --- (*) Of course, you can boot and hold down command-option-O-F, then interact with the open firmware directly. But I consider that low-level. Also, there are conditions under which that doesn't work. --- Hope this helps! Rick PS: There are other architectures that use open firmware (Sun's sparc comes to mind.) Once upon a time there was a project to write an open-source Linux bios for the i386 architecture. I have no idea what relationship (if any) it had to open firmware. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: goals for next release
Sven Luther wrote: I would also vote for : ESC abort current action if possible and drop back in the main menu (at possibly a lower priority). If abortion is not possible, you simply do the drop back at the earliest possible convenience. Sorry, was not talking about the help line, but about the functionality. There is currently no interactive way to abort an action, nor is there a way to drop to a lower priority apart from failing in one of the automated steps. I would vote for this functionality as well. It would decrease the need for setting DEBCONF_PRIOTITY kernel parameters at boot time, which can be a confusing thing to a novice. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian-installer, older hardware, boot loaders, miboot amiboot ..
On Tuesday, March 30, 2004, at 10:47 AM, Colin Watson wrote: On Tue, Mar 30, 2004 at 04:01:49PM +0100, Henning Makholm wrote: Scripsit Sven Luther [EMAIL PROTECTED] On Mon, Mar 29, 2004 at 10:56:21PM +0100, Henning Makholm wrote: Google macintosh boot block turns up official Apple information that seems like it might be what you're looking for. I have a fear suspision that this may be more related to newworld, than the oldworld stuff needed for miboot, I must admit ignorance about that newworld and oldworld means in this context. Tried googling in several different ways but didn't get any wiser. http://penguinppc.org/projects/yaboot/doc/yaboot- howto.shtml/ch2.en.shtml That page has the following words: yaboot will not work on NuBus or OldWorld machines, those will require quik or (for MacOS Pre-9.0.4 only) BootX/miboot The comment about pre-9.0.4 only is wrong. I can personally vouch that BootX and miboot both work fine with MacOS 9.2.2, the latest (and last) MacOS before Apple switched to MacOS-X. It is correct that yaboot will not work on OldWorld machines. AFAIK, there is very little support for NuBus machines at all. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: corrections
Hi Simon, Can you give a blow-by-blow installation procedure for installing debian on oldworld Macs without BootX? I've done it for woody with BootX -- I haven't figured out how to do woody without BootX. Unfortunately, sarge has completely eluded me so far -- with or without BootX. Thanks! Rick [EMAIL PROTECTED] wrote: rant having a non-free os to boot the machine defeats the purpose of having a free one installed. it's a kludge. one that i would prefer avoiding. i install debian onto many oldworld pmacs, and not having mac os there is a blessing. let's not go into the bad old days of having to use bootx to boot to linux. you might as well just not install linux (i don't even have mac driver partitions on my drives, i *don't* need them). /rant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
