Re: Debian Installer beta2 working on an OldWorld PowerMac-6500/225
Thanks! Sven, I've subscribed to the debian-boot list so I can listen in to the discussion. (Who know? Maybe even participate a bit!) BootX compatibility is fairly important to me because I've got some really old hardware with fairly broken Open Firmware. (PowerMac 6500, and Beige G3). Quik *can* be made to work on this hardware, but if anything goes wrong it's a long and arduous process getting the OF settings back to a working condition. Also, I need to be able to dual-boot Debian and MacOS9. As I understand your reply: Soon (Monday is the first time I'll be able to play again... Is that too soon?) I should be able to download a new iso from the daily build area that will allow me to tell it to skip the boot-loader installation part and get on with things. (I'll have to simulate [manually using BootX] the normal functions of a boot loader...) this will get me un-stuck and allow me to move on to the next phase of the installation. Will it be obvious how to tell it to skip the boot-loader install? Or do I need some special magic? Please let me know if there is anything I can do to help! Thanks, Rick Sven Luther wrote: On Thu, Jan 22, 2004 at 02:15:20AM -0500, Rick Thomas wrote: Hardware: PowerMac 6500/225 with 128MB of RAM and a 6GB SCSI disk partitioned as 2.5GB for MacOS, 3.0 GB for Linux root (an all-in-one filesystem) and 500 MB for Linux swap. It also has a SCSI CD-RW drive and a floppy drive. Software: MacOS 9.1 with Roxio Toast for the CD-RW drive. Following the call for testers in Debian Weekly News - January 20th, 2004, I decided to give it a try. The Beta2 d-i for PowerPC doesn't support OldWorld PowerMacs, but armed with my trusty copy of BootX, I figured I could do anything yaboot could do. Amazingly, I succeeded in getting it to boot and run the installer! (Some problems remain, but I'm sure they can be solved...) Cool. ... snip . I'm currently stuck almost at the end of the install, because it insists on trying to install yaboot. This is impossible on an OldWorld Mac. I may have to do a loopback mount of the ISO so I can do a little surgery on the install scripts to allow me to gracefully bail out of the yaboot install when I burn the next CD. This will be solved in the next d-i uploads. I have uploaded yesterday a nobootloader package, which enable you to work without any bootloader, but ultimately, a quik-installer would be needed. Maybe Jeremie is already working on that ? Also, this means that it is possible to boot with bootx on oldworld, and that the default -powerpc-small that was selected in kernel-installer is probably not the right solution. A kernel to use kind of question might be welcome, and maybe there could also be some kind of auto-probing for which kernel was booted. BTW, these kind of things have more their place on the debian-boot mailing list, so i forward this there. 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: using beta 2 install on oldworld powermac
Hi Rolando, I'm also trying to get debian installer working on an OldWorld PowerMac. See my comments below... Enjoy! Rick Rolando Abarca wrote: Hello, this is my second try to install sarge on my PowerMac 7200/120, this time ... snip ... Everything went smooth from here, until it tried to install yaboot, wich won't work on oldworld powermacs, I tried to skip that step, but I wasn't allowed. Finally I decided to reboot the machine from the other terminal. After setting BootX to boot from the hard disk ... snip ... Now, I'm presented with the login prompt, but I can't login because I haven't set the password for root and I haven't created another account... The installer didn't finish it process... :( I got past this one... Boot in single user mode. (Add single to the boot parameters in BootX. It will come up in single user mode and --for some reason-- not demand a password.) You can set the password for root by typing passwd root and then reboot. It will come up in multi-user mode and you can log in as root using your new password. is there a way to finish it? I mean, what does the installer do after the first boot? I think that if I boot in single mode I'll be able to finish the install... Once you login as root, you may have to manually enter the commands that the installer would have done automatically after installing yaboot. I don't know, I haven't gotten that far yet. See the recent posting by Sven (and my reply). This issue may be fixed soon. Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: goals for next release
I like it! Ideally, the selector would look at the sub-arch and only offer those bootloader options that work on that sub-arch? Rick On Thursday, January 29, 2004, at 03:39 AM, Sven Luther wrote: Ideally, but i don't know if this is beta2 stuff, a bootloader selector would be done, which on powerpc selects yaboot, quik, nothing, and on x86 would select grub, lilo, nothing. This could only be shown on lower priority, and fallen back to if the primary boot-loader somehow fails. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bits about countrychooser and languagechooser
Yeah! Please do this! On Sunday, January 25, 2004, at 09:26 PM, Jeremie Koenig wrote: Also, what about adding the C and POSIX locales somehow ? -- 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: 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 -- 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 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]
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]
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#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 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 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]
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#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]
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#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]
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]
NewWorld Blue White Mac Powerpc install -- problems with firewire and aec62xx driver.
Package: installation-reports INSTALL REPORT Debian-installer-version: Fill in date and from where you got the image Index of /pub/cdimage-testing/daily/powerpc/current Name Last modified Size Description Parent Directory 22-Sep-2004 00:26 - MD5SUMS22-Sep-2004 00:26 1k sarge-powerpc-businesscard.iso 22-Sep-2004 00:20 153M sarge-powerpc-netinst.iso 22-Sep-2004 00:26 310M Apache/1.3.31 Server at cdimage.debian.org Port 80 uname -a: The result of running uname -a on a shell prompt Linux bluemac 2.6.8-powerpc #1 Fri Aug 27 18:02:26 CEST 2004 ppc GNU/Linux Date: Date and time of the install Noon September 22, 2004 US East Coast time Method: How did you install? What did you boot off? If network install, from where? Proxied? Booted netinst CD directly At Yaboot prompt, specified: expert-powerpc video=ofonly Not proxied Machine: Description of machine (eg, IBM Thinkpad R32) Apple PowerMac Blue and White G3 - Rev A (before IDE chip was fixed) Processor: G3 300 MHz Memory: 384 Mbyte Root Device: IDE? SCSI? Name of device? /dev/hdc -- 6.4 GB IDE disk on the Mac motherboard IDE controller Root Size/partition table: Feel free to paste the full partition table, with notes on which partitions are mounted where. # mac-fdisk -l /dev/hdc /dev/hdc #type name length base ( size ) system /dev/hdc1 Apple_partition_map Apple63 @ 1( 31.5k) Partition map /dev/hdc2Apple_Driver_ATA Macintosh54 @ 64 ( 27.0k) Unknown /dev/hdc3Apple_Driver_ATA Macintosh74 @ 118 ( 37.0k) Unknown /dev/hdc4 Apple_Driver_IOKit Macintosh 512 @ 192 (256.0k) Unknown /dev/hdc5 Apple_Patches Patch Partition 512 @ 704 (256.0k) Unknown /dev/hdc6 Apple_Bootstrap boot 195313 @ 1216 ( 95.4M) NewWorld bootblock /dev/hdc7 Apple_UNIX_SVR2 swap 976563 @ 196529 (476.8M) Linux swap /dev/hdc8 Apple_UNIX_SVR2 root 11421868 @ 1173092 ( 5.4G) Linux native Block size=512, Number of Blocks=12594960 DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 21, type=0x701 2: @ 118 for 34, type=0xf8ff # mount /dev/hdc8 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) usbfs on /proc/bus/usb type usbfs (rw) # Output of lspci and lspci -n: # lspci :00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40) :00:0d.0 PCI bridge: Digital Equipment Corporation DECchip 21154 (rev 02) :01:00.0 FireWire (IEEE 1394): Texas Instruments PCILynx/PCILynx2 IEEE 1394 Link Layer Controller (rev 02) :01:01.0 IDE interface: Silicon Image, Inc. (formerly CMD Technology Inc) PCI0646 (rev 05) :01:02.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro (rev 5c) :01:03.0 SCSI storage controller: Adaptec AHA-7850 (rev 03) :01:04.0 SCSI storage controller: Artop Electronic Corp ATP865 (rev 06) :01:05.0 ff00: Apple Computer Inc. Paddington Mac I/O :01:06.0 USB Controller: OPTi Inc. 82C861 (rev 10) # lspci -n :00:00.0 0600: 1057:0002 (rev 40) :00:0d.0 0604: 1011:0026 (rev 02) :01:00.0 0c00: 104c:8000 (rev 02) :01:01.0 0101: 1095:0646 (rev 05) :01:02.0 0300: 1002:4749 (rev 5c) :01:03.0 0100: 9004:5078 (rev 03) :01:04.0 0100: 1191:0009 (rev 06) :01:05.0 ff00: 106b:0017 :01:06.0 0c03: 1045:c861 (rev 10) # Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[o] Configure network HW: [o] Config network: [o] Detect CD: [o] Load installer modules: [o] Detect hard drives: [e] Partition hard drives: [e] Create file systems:[o] Mount partitions: [o] Install base system:[o] Install boot loader:[o] Reboot: [o] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. Note 1: Booting without video=ofonly resulted in a scrambled screen. Note 2: Had to manually specify bmac ethernet interface. Note 3: This machine has two IDE disk drives. One (6.4 GB) is connected to the on-board IDE controller. The other one (180 GB) is connected to a SIIG Ultra ATA 133/100 PRO for Mac IDE
Bug#272967: Acknowledgement (NewWorld Blue White Mac Powerpc install -- problems with firewire and aec62xx driver.)
I forgot to add: Note 5: Several times during the installation, I got an error message telling me that some modules were not loaded because they could not be found: ide-mod, ide-probe-mod, ide-detect, ide-generic Note 6: I installed the same netinst CD on my beige G3 tower, using BootX as boot loader. This machine also has the SIIG Ultra ATA controller. Curiously enough, I did *not* get timeout /lost interrupt messages on this install. Is it possible that the Beige G3 somehow declares itself to have a slower bus than the Blue White claims, and this causes the driver to use a slower DMA mode -- hence no timeouts? In other words, the Blue White is claiming to have a faster PCI bus than it really can deliver, but the Beige makes no such claims. The Blue and White pays the price for boasting, the Beige reaps the benefits of modesty? Also, curiously, the Beige G3 had no complaints about missing modules... Go figure! 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 11:02 AM, Sven Luther wrote: On Mon, Sep 20, 2004 at 05:05:58PM -0400, Rick Thomas wrote: 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: Ok, actually following up on this from Oldenbourg with an oldworld box on hand. Glad you finally got an oldworld powermac box to test things on! (-8) I hope Oldenbourg is fun. It's a bit far for me to travel. 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. Hehe. Well, this is a general thingy. The idea is to change this in the kernel command line with DEBCONF_PRIORITY=medium or low. Maybe i should create an 'expert' boot/boot-ofonly floppy set ? Hmmm... In general, I'd much prefer to solve this problem without a multiplication of floppies -- one for each possible boot-time option! It takes several minutes to download and burn a floppy. Multiply that by all the options I need to test, and you're talking about a serious investment of time. Can't we come up with some more general method of setting boot-time options? In this particular case, could someone please explain to me the logic behind putting the first availability of change installation priority so late in the game? 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. Yeah, but you have to balance the usefullness of that together with the size limit of the floppies. 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? Enjoy! 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: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
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 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. Actually, it's quite useful -- for writing to mac-formatted (HFS) floppy disks... as in for saving the log files for later debugging when all else has failed. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Oldworld Serial Console
On Friday, September 24, 2004, at 09:17 AM, Gregory Seidman wrote: In fact, I can attest to using an ordinary Mac printer cable between my Oldworld Mac running Linux and my dual G4 with a Keyspan adapter and running MacOS X. I use minicom on the Mac and have set up quik, not BootX, to allow me to have a console over the serial line. Thanks for the explanation! Could I prevail upon you to post a detailed step-by-step description of how you got quik to let you have a console over the serial line? There are at least a few of us who have been beating our heads against this particular wall for some time... 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 Saturday, September 25, 2004, at 04:13 AM, Colin Watson wrote: On Fri, Sep 24, 2004 at 01:50:34AM -0400, Rick Thomas wrote: 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.] We're killing root-2; it wasn't a good idea to introduce it without good support for loading it, and everything fits on root and net-drivers if you juggle things around a bit. Commits will come after the archive cron.daily run today. I respectfully disagree. Hey, I'm just a tester. You developer guys can do what you want. But I predict you'll live to regret this decision. I think the effort would be better spent in fixing the support for loading additional floppies to make it completely open-ended and seamless. It almost works right now -- There are simple work-arounds for all existing problems with root-2 as it is today. Oh well... 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 Saturday, September 25, 2004, at 04:49 PM, Colin Watson wrote: Bringing things back into sync with other architectures is worth it on its own, and reducing the number of floppies required for an installation was one of the original goals of d-i. After my changes, there's *loads* of room left for things. We were just being inefficient, that's all. Glad to hear that you can free up space and still maintain functionality. I look forward to seeing the result! Enjoy! Rick PS - I've often wondered if things would be simpler (maybe *much* simpler) if the floppy-boot process just assumed that there will always be a CD-rom drive available. Has anybody else explored that possibility? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge on OldWorld Mac - No root device
Hi Duane, Did you install a 2.6 or 2.4 kernel? The 2.6 kernel requires an initial ramdisk. The 2.4 kernel (usually) does not. The kernel installer leaves a kernel and a tailored initrd in the /boot partition. You need to copy them into the appropriate places inside the MacOS System folder on your HFS partition. The way I do this is to go to the alt-F2 console after the new kernel has been installed and just before it reboots. Then I do the following: modprobe hfs # (see note 1) mkdir /MacOS mount -t hfs /dev/discs/disc0/part6 /MacOS # (see note 2) ls -l /MacOS # (to make sure you've got the right partition mounted!) cp /target/boot/vmlinux /MacOS/System\ Folder/Linux\ Kernels/ # (see note 3) cp /target/boot/initrd.img /MacOS/System\ Folder/Linux\ Ramdisks/ # (see note 3) sync umount /MacOS Then switch back to the alt-F1 console and allow the reboot to proceed. This will land you in MacOS with BootX running. You will need to modify the various options to make it pick your new kernel and initrd. Don't worry about the fact that choosing an initrd will take away the option to tell it where your root partition is: The initrd that was prepared for you by the kernel install stuff has the right code to switch to your real root partition once it has loaded the necessary modules, etc. You just have to point BootX at it and it does the rest. note 1: You can use hfsplus in place of hfs, if your MacOS partition is HFSplus. I use HFS, personally, because I feel like the Linux HFSplus module is still fairly new and untested. But I'm old and paranoid. You may be braver. note 2: The installer uses devfs (I think that's the right word) device names. You need to figure out which partition has your MacOS system on it, and use that in place of /dev//part6. Shell auto-completion is your friend here! note 3: BootX gives you a variety of places to put your kernels and initial ramdisk images. I've used the folder-names that I chose when I was getting started. You should use your own choice, of course. Enjoy! Rick On Sunday, September 26, 2004, at 12:28 AM, Duane Cottle wrote: I successfully installed Sarge using this week's iso CD. I used BootX to access it, as the box won't boot from the CD. After the installation, I deselected the ramdisk according to README and set root to /dev/hda7 likewise. I get kernel panic and no root error. When I use the ramdisk, the installer begins again. Has anyone seen this? I prefer BootX over miboot, and yaboot is not an option on OldWorlds AFAICT. Thanks for any advice. Cheers, Duane -- 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: Sarge on OldWorld Mac - No root device
On Sunday, September 26, 2004, at 08:34 AM, Duane Cottle wrote: I'm going to start another thread concerning the fact that my scsi hard drive wasn't detected during the entire installation. You probably have a mesh SCSI controller. Almost all OldWorld Apple machines had them. Early on in the installation process -- before the disk/hardware discovery phase, switch to the F2 console and type modprobe mesh Then, just before the reboot, switch to the F2 console again, and add the line mesh to the /target/etc/modules file. I've submitted several bug reports on this topic. The developers know about it, and may fix it sometime. It's not as easy to fix as it sounds, because the mesh controller is not on the regular PCI bus, so the normal hardware discovery programs never get a chance to see it. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: floppy root.img sizes
On Oct 15, 2004, at 11:16 AM, Duane Cottle wrote: Hi all, Sorry if this is the wrong list for this... I have been testing daily sarge floppy install images from http://people.debian.org/~luther/d-i/images/daily/powerpc/floppy/ for a few weeks on OldWorld Macs. That is, until October 8. Since then, root.img seems to have swollen to a size bigger than I can dd onto a floppy. What's puzzling to me is that the sizes reported by any tool I use to download the images is less than the ls -l report by around 4.2KB. Example: in gFTP today's root.img shows 1468006 on the server and 1509557 on my hd. Hi Duane, I'm forwarding this to Sven Luther, who generates the floppy images in question. I'm also forwarding this to the debian-boot list, where there are other folks besides Sven who may be able to help. Enjoy! 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]
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: 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]
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: 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]
Re: testing beyond Intel [PATCH]
If not, ask smart questions[1] [1] http://www.catb.org/~esr/faqs/smart-questions.html I sincerely hope that what I've been asking so far are not viewed as dumb questions! Here's my first feedback on the manual (since I have to read the manual before I can start using the installer!) It would be really nice if the html version of the manual had a prominent link to a PDF or plain-ascii-text version, for the sake of those like me who have trouble reading large html documents from CRT screens. I'll have to read up on how to submit a bug-report on this. (Yes, I've located the section of the installation manual that points to the other manual that points to... and tells how to submit a bug report.) In the mean time, I'll also be reading up on CVS and trying to figure out how to generate my own PDF or text from the hints I've got so far. Are there any other developer tools I should be reading up on in order to get to the point of having a readable installation manual in hand? Hopefully, all this will eventually lead to my being able to make a useful contribution to testing the OldWorld PowerMac version of debian installer -- which was the original aim, after all! Thanks! Rick You are right, we should update the What can I do to help? section. So it is attached... +An other way to help is test the Debian-Installer +on your hardware, especailly if you have access to none Intel computers. +/p + +p +Follow the instructions from + a href=http://d-i.alioth.debian.org/manual/;the install manual/a. + ( feedback on the manual is also welcome ) +/p -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: testing beyond Intel [PATCH]
Frans, That's wonderful! However, nothing's easy. I get not found errors from both of those links. Am I missing something? Thanks! Rick Frans Pop wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 18 March 2004 03:35, Rick_Thomas wrote: Is the Preliminary Sarge Installation Manual available as a PDF or in some other form that can be printed directly to paper? By chance I build a pdf (English) only yesterday from current CVS. It is available at: http://[EMAIL PROTECTED]/d-i/install.en.pdf (460 kb) or : http://[EMAIL PROTECTED]/d-i/install.en.pdf.gz (254 kb) Have fun, FJP -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAWe3rgm/Kwh6ICoQRAhARAKCwKZh5Yz/kSN3vCDP0AwqfKjotTwCfejdn UDchmqRKH7SEnkXsTPYUCfQ= =C/nf -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: testing beyond Intel [PATCH]
Ahhh... That worked! As I said, Nothing's easy!. I need the PowerPC version. This one's for the i386. Could I impose on you to generate a PowerPC version for me? (Sorry to be a pain!) Thanks in advance! Rick Frans Pop wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sorry, messed up with the links (copied FTP to HTML) :-( Below are the correct ones (unless I messed up again). No, tested. These are OK. On Thursday 18 March 2004 03:35, Rick_Thomas wrote: Is the Preliminary Sarge Installation Manual available as a PDF or in some other form that can be printed directly to paper? By chance I build a pdf (English) only yesterday from current CVS. It is available at: http://home.tiscali.nl/isildur/d-i/install.en.pdf (460 kb) or : http://home.tiscali.nl/isildur/d-i/install.en.pdf.gz (254 kb) Have fun, FJP -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFAWfXYgm/Kwh6ICoQRAk6eAKC/gywLe4a83L7fXsT5nUIUa1ZmdQCg1yW1 VF3c1VP/UVYRliiMn7l1N1E= =tcRH -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge/beta-3 on a RS6000/7025-F50 (PPC 604e, CHRP)
On Saturday, March 20, 2004, at 01:22 AM, Sven Luther wrote: Ok, copying to debian-boot, since this is most relevant there, and to rick thomas, which volunteered to help with installation manual. Rick, this is a boot method on a chrp-rs6k ibm box. I don't know if you are familiar with these boxes, but just keep this mail until we are ready to write documentation for it. Anton, copying you since i was not sure you would read this, and i want your feedback on the possibility of creating a PReP boot partition. I know of the existence of the PREP and CHRP flavors of OpenFirmware. I've even had occasion to install a few SGI mips and IBM rs/6k boxes that use them. I don't remember any details (it was a long time ago) so I'll have to rely on other's experiences for anything I put in the PPC manual about them. So: Please provide detailed and clear descriptions of anything you want to get into the user manual. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: testing beyond Intel [PATCH]
Thanks! This will be very helpful. Please see my notes below... On Saturday, March 20, 2004, at 04:17 AM, Miroslav Kure wrote: On Sat, Mar 20, 2004 at 12:42:51AM -0500, Rick_Thomas wrote: I would be very grateful If you (or someone else on this list) could point me at the chapters and sections of the PowerPC debian-installer docs that are most seriously out of date, and give me a few hints as to where to look for the raw information that I can turn into the needed updates. Great. See the other posts about ppc. I'll point you to the doc/manual/en/. Please remember that I am a *complete* beginner at things Debian. I assume that doc/manual/en is a directory in some repository of document source. Where is this repository located and how (using what protocols/programs) do I access it??? welcome/ is very generic and ok now hardware/ lists supported hardware, so look at supported/powerps.xml preparing/ is quite generic, just some bios and partitioning (should be same as woody) install-methods/ this is heavily arch dependent boot-installer/ dtto the rest of chapters should be common to all archs partitioning/ there are some arch specific bits, but should be same as before. Thanks! This will help me direct my efforts to where they can do the most good. Maybe this will all become clear once I get a look at the document source, but: Is it the plan that there be a separate manual for each architecture, or just a few architecture specific chapters in a generic Installing Debian manual? Does there exist a design document for the installation manual? (I know that's too much to ask of an all-volunteer workforce, but Hey! Sometimes you get lucky!) If (as seems likely) there was no intention per-se (The existing manual just grew as part of an organic process.) what is the current state of affairs on the placement of architecture specific information. I am a competent technical writer and a native speaker of English with a long background in UNIX, but I am just beginning with Debian Linux Since you are native speaker, it would be very helpful if you could also proofread the generic parts of the manual. Will do. I can start on this part right away. To whom do I send my errata? Cheers -- Miroslav Kure Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: testing beyond Intel [PATCH]
Thanks! You're very kind. I'm still (figuratively) learning where the bathrooms are, but with help from friends like you I'll be up and running in no time. I'll have to learn how to do svs, docbook, xml and so on myself eventually, and that's one of my top priorities. In the mean time, until I do, I'll take you up on your offer. A first crop of updates will follow in a day or so. Thanks! Rick On Sunday, March 21, 2004, at 04:51 PM, Miroslav Kure wrote: If you don't like to mess with docbook and xml, you can send me plain text and I'll docbookize it and commit into the right place. Will do. I can start on this part right away. To whom do I send my errata? See above (send it to me, and I'll take care about the rest). -- Miroslav Kure -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: suggestion: something to add!
Let me second Jeremy's suggestion. I keep DHCP turned on on my router because my printer needs it, but I much prefer to have everything (except the printer -- sigh!) have statically assigned IP addresses. I know I could do that with DHCP, but why bother if I don't have to? Enjoy! Rick On Sunday, March 21, 2004, at 09:28 PM, Jeremy D. May wrote: what about adding something to the installer where it activly asks the user if they wouold perfer manual config or dhcp. in some cases the user may have dhcp but want to use manual config. just a suggestion! --jeremy -- 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: suggestion: something to add!
Here's a larger question: Why do I have to subject myself to the full-monty expert mode when I just want one tiny feature that isn't completely covered by normal mode? Shouldn't it be possible to dip down into expert territory for just the parts you need fine control over, and return to normal mode for the rest? This is not something that needs to be done right away. And it likely involves changes in lots of places. Maybe we could put it on the wish-list for 'rev 2'? Rick On Sunday, March 21, 2004, at 10:25 PM, Joey Hess wrote: Jeremy D. May wrote: ok, but what about the not so expert user that wants to do that? I've added a FAQ entry explaining our reasoning. http://wiki.debian.net/index.cgi?DebianInstallerFAQ -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: OldWorld floppy images
Hi Jeremie! I downloaded the images. The first thing I noticed was that the root.img was more than 1.440 MB long. The second thing that I noticed was that fdformat and superformat don't work on powerpc hardware, so I can't create a 1.920 MB formatted floppy to put root.img onto. For example, when I try to do fdformat /dev/fd0 I get an error message: ioctl(FDFMTBEG): Inappropriate ioctl for device. So the largest image I can write to media is 1.440 MB. I decided to try the boot.img anyway since it was the right size. I could at least see if my systems would boot with it. The third thing I noticed was that the floppy drives hadn't been used for years (literally) and they were *dirty*. The blank floppy disks I had around the house were about the same age, so I couldn't trust them either. So I went out and got a drive cleaning kit and a box of brand-new floppy disks. (I had to go to three stores before I found one that carried floppy drive cleaning kits. Floppy disks are seriously going out of style!) After a thorough cleaning... I was able to write the boot.img and read it back without error. The original boot.img and the read-back file compared bit-for-bit, so I figured I had a good one. First, I tried it on the machine that wrote it (a beige G3 at 300 MHz). It succeeded in booting (got a happy-mac icon that changed after a while to an icon of Tux Penguin snuggling up to a happy-mac.) Of course, when it ejected the boot floppy (presumably because it wanted the root floppy inserted -- though there was no indication on the screen that this was the case. I assume that is normal?) I had no root floppy to insert. But I felt good that I'd gotten that far! Next I tried it on a different machine (a powermac 6500 at 225MHz). It got to the point of the Tux-and-Mac icon, but the drive made grinding noises and it never ejected the disk. It just hung. I believe that the floppy drive on that machine is terminally old/tired/flakey, even after a couple of thorough cleanings. It's not altogether surprising, since in a previous life, this machine was used (and abused!) by students in a public computer lab. I'll try swapping the floppy drive with a known good one and try again. Though that may take a couple of days. So, can we make a root.img file that will fit on a 1.440 MB disk? Hope this helps! Rick Rick Thomas wrote: Thanks, I'll give that a try. Rick On Sunday, March 21, 2004, at 06:47 PM, Jeremie Koenig wrote: On Sat, Mar 20, 2004 at 01:06:55PM -0500, Rick Thomas wrote: OK, I'm willing to give it a try. Where do I start? You can find some floppy images at http://sprite.fr.eu.org/d-i-oldworld/ I haven't tested them at all, so please tell me how it goes ! You won't be able to install any bootloader, but IIRC chrooting into /target and running quikconfig works. Maybe you'll also need to do some OpenFirmware configuration to boot into the new system. Good luck ! -- Jeremie Koenig [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: OldWorld floppy images
Jeremie Koenig wrote: On Thu, Mar 25, 2004 at 11:35:04AM -0500, Rick Thomas wrote: so I may not have picked the right module(s). Which ones should I have used? You mean, in anna when loading the floppy ? Pickup everything, and hopefully your scsi host will be detected. -- Jeremie Koenig [EMAIL PROTECTED] Ummm... No SCSI devices on this machine. There's an on-board SCSI chip on the motherboard (just like all oldworld PowerMacs) but it's not connected to any devices. I've got a PCI IDE controller card with two disks attached to it that MacOS *thinks* is a SCSI conroller, but Linux (Yellowdog 3.0 anyway) recognizes as an IDE controller. Does that change anything? Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: OldWorld floppy images
Malte, Errors like that are usually symptomatic of a dirty/dusty floppy drive. 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. 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. 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 Malte Cornils wrote: Jeremie Koenig wrote: There's a new version of the images which should fix your problems: http://sprite.fr.eu.org/d-i-oldworld/floppy/ One of ofonlyboot.img and boot.img should work for you (the other will probably give no video output). Just testing here too... On a 4400/200 system, the boot.img works. However, inserting a root.img floppy shows RAMDISK: Compressed image found at block 0 swim3: expected cyl 2, got 4 [three times] end_request: I/O error, dev 02:00 (floppy), sector 72 (and then, nothing) This *might* be a bad image, although I tried two different floppies. If you think it is, I will test with more floppies (although floppies never work right for me. Never.) I will be perfectly happy testing all matter of d-i stuff on the system, too, once oldworld images become available. -Malte Cornils -- 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: Debian-installer, older hardware, boot loaders, miboot amiboot ..
Maybe we could get the boot-sector code declared OK to use by Apple? It would be a hack the system kind of thing, but I suppose technically they wouldn't have to release the copyright on the source code for the boot sector, just the derived sequence of binary bits. Indeed, Apple may have already done so. I believe they allow free download of the MacOS 7.x floppy images. It's just a thought... Rick On Sunday, March 28, 2004, at 02:16 AM, Sven Luther wrote: Hello, 2) a small file, the boot1 macos ressource, a 1K boot-sector to be copied to the floppy boot sector, is taken from the mac os system file. This is non-free, binary only, altough, well, the file in question only contains some ROM calls to initialize HFS, and load the boot2, open the mac os system file, and load boot2, which is provided by the GPL-free part of miboot mentioned above. [ Please CC me or keep the debian-boot CCed, as i am not subscribed to debian-legal, but am to debian-boot ] 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]
Bug#240602: boot-floppies: sarge - there may be multiple driver floppies - need to ask for more
Yes. It's the new debian-installer on an OldWorld PowerMac. Jeremie has pointed out that one floppy worth of drivers should be enough to give you access to either a CD-ROM or a network, and that's all you really need. So this is actually a wishlist request. I have no problem with that. So think of this as a birthday wish for the new debian-installer: That it always have an open ended design when it's easy and sensible to do so. Thanks, Rick On Sunday, March 28, 2004, at 05:04 AM, Sven Luther wrote: On Sun, Mar 28, 2004 at 02:42:30AM -0500, Rick_Thomas wrote: Package: boot-floppies Notice, that since this is probably a debian-installer you are using, a bug report against debian-installer should have been more likely. I think it goes to the same please though, just wanted to confirm that it is indeed debian-installer you are using here, or maybe not ? Version: N/A; reported 2004-03-28 Severity: normal When starting an installation by booting from floppy, it first asks for the root disk then it asks for the drivers disk. If you answer yes to the drivers question, it loads one floppy worth of drivers and continues the installation without asking if there might be more driver floppies to be loaded. It should loop asking for more driver floppies until the user says no more. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian-installer, older hardware, boot loaders, miboot amiboot ..
Here's a thought. First some background: Last night, just to prove it could be done, I succeeded (first try) in using BootX under MacOS9 on an OldWorld PowerMac G3 (beige mini-tower) to load and run the debian-installer kernel and initrd downloaded from: http://ftp.debian.org/dists/sarge/main/installer- powerpc/beta3/images/powerpc/netboot/ I got as far as the point where the d-i tries to install a bootloader. It died there because there is no boot loader for the oldworld subarchitecture. I could have done the same thing using miboot, but it would have been *much* harder. BootX has a nice Mac-like user friendly interface. Miboot most definitely does not. The amount of MacOS actually needed for this is quite small. With a little work, I've gotten the corresponding thing for yellowdog Linux down to under 50 MB and put it on a zip disk. So here's my suggestion: Declare that all OldWorld machines must have a minimal MacOS partition with BootX as their boot loader. That is, If you want to use debian-sarge on an OldWorld Mac, it presupposes that you first have MacOS and BootX installed on that machine. Do not provide BootX on the CD, just a note in the README document that says you need it and how to download it from, say, non-free or contrib. Now the part of debian-installer that died on me last night has an easy fix: Simply do not install any boot loader at all for that subarchitecture. This makes installing a new kernel on an oldworld machine a bit tedious because you have to manually copy the new kernel binary and any associated initrd to the right places on your MacOS partition, and make manual changes to the parameters on BootX. Also, since HFS+ filesystem support is still iffy enough that it's recommended to use it read-only, this means that your MacOS partition should be HFS rather than HFS+. Some folks may find that irksome, but it's definitely not a show-stopper. It's still possible to use quik or miboot to get a completely macOS free machine, but we can leave that as an exercise for the serious hackers. Would that fit all the legal requirements? It has the advantage that it's doable in the time-frame needed to get sarge out the door. 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 ..
Sven Luther wrote: Rick wrote: Now the part of debian-installer that died on me last night has an easy fix: Simply do not install any boot loader at all for that subarchitecture. Rick, Quik can easily be used to boot from CD, no problem, sadly it cannot be used to boot from floppies, and thus cannot be used to install debian on a blank disk. I'm glad to hear that quik can be used to boot CDs. Sometime if you have the time, I'd like to hear how that's done. In either case, under my proposal, once the user has gone to the trouble of setting up MacOS and BootX for the install process, they might as well continue to use that setup for booting their production system. Unless you (or someone) can come up with a foolproof way of packaging quik in a bootloader installer. I'll do whatever I can to help with testing. But if it drags out, there *is* always the no boot loader option as a last resort. 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 ..
Joey Hess wrote: Rick Thomas wrote: I got as far as the point where the d-i tries to install a bootloader. It died there because there is no boot loader for the oldworld subarchitecture. It's good to know that it got that far. Declare that all OldWorld machines must have a minimal MacOS partition with BootX as their boot loader. That is, If you want to use debian-sarge on an OldWorld Mac, it presupposes that you first have MacOS and BootX installed on that machine. Do not provide BootX on the CD, just a note in the README document that says you need it and how to download it from, say, non-free or contrib. This seems eminently reasonable. I'll note that there exists x86 hardware with some of the same issues: you can currently only install Debian on it if some other non-free OS is installed first. Thanks! Now the part of debian-installer that died on me last night has an easy fix: Simply do not install any boot loader at all for that subarchitecture. 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. What should I have done differently? 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'm sorry. I don't have the skills in assembler language to help with this phase. However, I'll happily test things on my farm of old Macs of various flavors. For what it's worth, since MacOS7.6 and (I think) 8.6 boot on M68k Macs, the boot sector is very likely to be in M68k machine language, not PowerPC. Hope that helps! Rick On Monday, March 29, 2004, at 02:32 AM, Sven Luther wrote: On Sun, Mar 28, 2004 at 07:00:06PM -0500, Rick Thomas wrote I'll do whatever I can to help with testing. No problem. If you feel like disassembling the miboot stage 1 boot-sector, and providing me info on what it does, i would appreciate. It seems i am legally barred from doing it myself if i want to write the reimplementation. -- 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]
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]
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]
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#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]
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]
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: 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
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: 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, 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]
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]
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]
D-I Etch+1/2 CD images for non x86/x86-64 arch?
On Feb 7, 2008, at 8:24 PM, dann frazier wrote: Let me try and reiterate some points of your proposal to make sure I understand. The only install media for etchnhalf will be netinst cds. These cds will be limited to i386, amd64, and other archs for which a need is demonstrated. It sounds good to me - an additional benefit is that it reduces the number of images we need to test. -- dann frazier I realize it's very late in the game, but doesn't the security requirement to update openssh used in the installer make it necessary to provide 4.0r4 for all architectures? Just a thought... Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Setting FSCKFIX=yes on certain machines
On Aug 14, 2008, at 4:50 AM, Martin Michlmayr wrote: We have to set FSCKFIX=yes in /etc/default/rcS on machines that don't have any I/O devices to follow the boot process, otherwise fsck might prompt the user to press a key and this is not possible. This is mostly needed on NAS devices. They all have ttyS0 which means that we cannot modify /etc/default/rcS automatically if there's no ttySx. Instead we have to hard code the specific devices we're aware of that might have ttyS0 (or another output devices) but where users typically don't have a serial console hooked up. Since this mostly applies to NAS devices, I thought of simply putting sed -i s/^FSCKFIX=no$/FSCKFIX=yes/ /target/etc/default/rcS in the postinst of flash-kernel. This is not the most generic way of solving this but sounds like the best option to me right now. I think the can look for a more generic solutions once we're aware of other devices that need this. Any objections to this approach? (Note that /etc/default/rcS is not a conffile so we may modify it.) It would probably be a good idea to put a comment into /etc/default/ rcS to the effect that this is being done, so we can find it later when we have a more generic fix... Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
