Re: G3 Beige Tower install help
On Tue, Sep 09, 2008 at 05:16:35PM -0400, Rick Thomas wrote: > That's good news. I have tried to get xorg and gnome running on my test > machine, but it seems that the video chip it has isn't very well > supported. I need to open a bug report on the subject. I have 2 video cards in it. Back in the day when it was a workstation with dual heads. I left the stock video card in, (RageII 3d) with a whopping 8 mb/ram. It's this card that the Lenny installer picked up, not the dual head card. But that's OK. Is your card different from stock ? -- Regards, S.D.Allen - Toronto -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: G3 Beige Tower install help
On Mon, Sep 08, 2008 at 07:34:43PM +0300, [EMAIL PROTECTED] wrote: > 2008/9/8, Stephen Allen <[EMAIL PROTECTED]>: [ ...] > The other IDE socket has probably the CD drive (hdc)? Maybe the spare > drive has been as a slave in its earlier life? In Linux, hda/b are > master/slave on primary ide bus, and hdc/d on secondary. > Risto Hi again Risto: Nope, none of the jumpers were changed, as it turns out. The box has 2 CD drives, both scsi. The other IDE socket isn't used at the moment. I just saw an Ad on CraigsList today, for several bigger scsi drives at a great price, so I may be putting in some extra storage. :D Risto, as you've probably read by now; I've got the G3 Beige up and running with Lenny and even a window manager, (XFce4). This was due in large part to your help, the only missing link was furnished by Nicolas, in terms of applying the Apple disk driver again as the installer corrupted it. Once I did that, I was able to boot into Linux using BootX. Thanks for all your help ! -- Regards, S.D.Allen - Toronto -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: G3 Beige Tower install help
On Sep 9, 2008, at 7:30 AM, Stephen Allen wrote: On Tue, Sep 09, 2008 at 09:17:55AM +0100, Nicholas Helps wrote: Hello Stephen (and everyone else), Howdy Nicholas, Being polite this time ;-) Glad the step by step worked. Please make sure you acknowledge Rick as well, without this help, I would never have gotten my install working either The list works! Absolutely. I believe he has some additions for the SxS as well. Having read the other posts about the expert installer setting, I would add that in my experience setting the installer to expert did not allow me to avoid the installer trying to install quik. On older versions (eg Woody) even without putting the installer in expert mode one could stop this (and the install manual explained how). With Etch, the installer just pushed ahead regardless of what I tried to do to stop it. Fortunately, since quik does not work with ext3 file systems, it aborted. I consider this a bug. Perhaps I should file one then ? What's the best way to do this; reportbug ? Rick perhaps you can chime in here ... I consider it a bug too! The "expert mode" hack allowed me to skip the "install quik" step, as I described in my previous email, but it didn't do any good; the object of skipping it was to allow OS9 to boot cleanly, but as reported, it's still necessary to do the "refresh the disk drivers" trick with the OS9 install disk. I was using Lenny beta2, and your tests were with Etch, if I remember. Maybe the "barge forward and install the boot loader, even in expert mode" mis-feature got dropped somewhere in-between? I'm planning to do some experiments to see just where the boot info gets clobbered -- when I get some time... (Sigh!) Hope you enjoy your new system. I have found Debian to run extremely well on these systems. Yes it is quite a bit snappier then MacOS X, and my SCSI Agfa scanner, "just works". Xsane autoconfigured it ! That's good news. I have tried to get xorg and gnome running on my test machine, but it seems that the video chip it has isn't very well supported. I need to open a bug report on the subject. -- Regards, S.D.Allen - Toronto Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Call Trace and scary messages on kernel 2.6.27-rc5
On Mon, 8 Sep 2008 21:47:29 -0300 Rogério Brito <[EMAIL PROTECTED]> wrote: > Hi there. > > I just compiled a new 2.6.27-rc5 kernel for my standard Kurobox (an > embedded NAS that has an MPC8241 CPU, if I'm not mistaken) and upon > booting, I get these scary messages and Call Traces: [snip] This is a known problem. Check patch bb23b431db7405f6d79f989ad0236bf6428ba1cb in Linus' tree, it should correct the traces you see. Regards, M. -- And if you don't know where you're going, any road will take you there. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: G3 Beige Tower install help
On Tue, Sep 09, 2008 at 09:17:55AM +0100, Nicholas Helps wrote: > Hello Stephen (and everyone else), Howdy Nicholas, > Being polite this time ;-) > > Glad the step by step worked. Please make sure you acknowledge Rick as well, > without this help, I would never have gotten my install working either > The list works! Absolutely. I believe he has some additions for the SxS as well. > Having read the other posts about the expert installer setting, I would add > that in my experience setting the installer to expert did not allow me to > avoid the installer trying to install quik. On older versions (eg Woody) even > without putting the installer in expert mode one could stop this (and the > install manual explained how). With Etch, the installer just pushed ahead > regardless of what I tried to do to stop it. Fortunately, since quik does not > work with ext3 file systems, it aborted. I consider this a bug. Perhaps I should file one then ? What's the best way to do this; reportbug ? Rick perhaps you can chime in here ... > Hope you enjoy your new system. I have found Debian to run extremely well on > these systems. Yes it is quite a bit snappier then MacOS X, and my SCSI Agfa scanner, "just works". Xsane autoconfigured it ! -- Regards, S.D.Allen - Toronto -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: snd-aos not working on a PowerBook6,2 (PowerBook G4 12")
> BTW, please *post* your installation reports so that we can link them > to the release certification page. I want to help with this arch as much > as I can. > Just a very, very brief installation report. I was installing lenny on Sunday 7th September using snapshot of businesscard installation CD on Powerbook 5,6 and all went without a glitch. Sound works fine, too. Piotr -- http://okle.pl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: G3 Beige Tower install with BootX - help
>>> Rick Thomas <[EMAIL PROTECTED]> 09/09/08 8:49 AM >>> > > Hello all, > > I have been working with Debian for quite a few years now and using > powermac G3 machines with extra network cards in them as routers > and firewalls, etc. These machines were set up back in the days of > Woody and have been kept uptodate with security updates, but > otherwise pretty much left untouched. Due to the issues around the > firmware in these machines and because it was useful, I always set > them up to boot initially into mac OS9 then use BootX to hand over > the Debian. This worked a treat. > > However, I thought it would be good come up to date by installing > Etch instead. I'll bring this up to Lenny. [Rick] > I used a free machine that was not actually in use and ran the > install using the current network install ISO. I used the Lenny Beta2 "businesscard" install disk. > Things have changed since the days of woody and it now seems that > floppy images (boot image and root image) are no longer used. > Hence, I copied the initrd.gz file over to the mac HD and set that > as the ram disk for the install. I also copied across the linux > kernel and put that into the kernels folder in the system folder. In a little more detail: I drag- n- dropped the "vmlinux" and "initrd.gz" files from the Debian install CD (they are in the "install/powerpc" directory) into the MacOS9 "System Folder:Linux Kernels" folder. Then I chose those two as the "Kernel" and "use specified RAM disk" options in BootX. I set the "More kernel arguments" box to "DEBCONF_PRIORITY=low" (without the quotes) to specify that I wanted to run the installer in "expert" mode, so I could do a couple of non- default tricks needed by OldWorld Macs using BootX. You may or may not want to check the "No video driver" checkbox, depending on your video hardware. This is the equivalent of the "video=ofonly" in yaboot. You'll have to experiment to find out which option works for you. You may (probably will) want to change the "Ramdisk size" option to a larger number. I use 32768. The default is 8192. > Using that allows me to boot into the installer where I answered the questions in the usual way, until I got to the step "Load Installer Components from CD". There I chose the option to install "hfs- modules": HFS filesystem support. We'll need them later on when we copy the new customized kernel and initrd to the MacOS9 partition. This is the first "non- default trick" for BootX installation, for which we need to be in "expert mode". There will be another occasion later. > and using the installer partitioner in the installer > I deleted the previous linux partition (hda7) and swap (hda8) and > made new ones. I used the "manual partitioning" option and created "root" and "swap" partitions. Note that these two partitions should have single digit numbers. Otherwise, during the reboot following the installation, the Linux boot process will hang "waiting for the root partition". I suspect this is a bug somewhere in the code that decodes the kernel arguments. Putting this restriction another way, the root and swap partitions should each be chosen from hda7, hda8, or hda9 (assuming your MacOS9 partition is hda6, as it usually will be.) If either of them are hda10 or greater, you'll have problems later. You can use two- digit partition numbers for things like "/home" and "/usr", it's just the root that is restricted. The "guided partitioning" will try to create an ext2 "boot" partition. This is necessary for the quik bootloader, but completely *un*necessary for BootX. In fact, it's actually undesirable because I've recently discovered that the default size (8 MB) for the "boot" partition is too small -- kernel and initrd have grown since quik was written. So including /boot as just a directory in the root partition allows it to have arbitrarily large contents. While you're there in the partitioner, make a note of the partition numbers of your MacOS9 and root partitions. You'll want them later. > Then installed the base system, etc,etc all the way through to > where it runs tasksel. I just leave that at the basic system for now. > Following on some more, finally we get to the point of having finished "Select and install software" where the next thing it would want to do is "Install quik on a hard disk". You do *not* want to install quik. You've got MacOS9 and BootX to do that job. So skip over that line and continue with "Continue without boot loader". It will tell you that you need to use the vmlinux from the "boot" partition and set the kernel parameter "root=" to the root partition that you just installed into. Write down the root partition number (if you didn't do so during the partitioning step) you'll need it later. At this point you should switch to a different console (hit the "alt" and "F2" keys) and do t
Kernel problems - PMU related
Hi list! I have trouble running the latest sid kernel on my macmini G4 1Ghz. When loading the kernel modules, it loads eeprom and afterwards a delay of 10 seconds occurs and a message with something like PMU (!ack) is displayed and the machine stops booting. What's wrong here? I already reset nvram and PMU but this does not help. Kind regards, Marko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: G3 Beige Tower install help
* Dr. N.R. Helps Medical Research Council Protein Phosphorylation Unit College of Life Sciences MSI/WTB/JBC Complex University of Dundee Dundee DD1 5EH Scotland t: 44 (0)1382 384745 (office) t: 44 (0)1382 388019 (lab) f: 44 (0)1382 388729 e: [EMAIL PROTECTED] w: http://www.dnaseq.co.uk/ w: http://www.ppu.mrc.ac.uk >>> Stephen Allen <[EMAIL PROTECTED]> 09/08/08 11:38 PM >>> On Mon, Sep 08, 2008 at 10:41:09AM +0100, Nicholas Helps wrote: > Hello Stephen / all, Hi Nicholas: > So, here is the way I got it to work [ ...] Excellent instructions, thanks very much Nicholas ! I'm writing this from my G3 Beige booted into Lenny- Debian using mutt. :) I'm a happy camper. I think you have just written the best SxS I've ever seen. You should write technical manuals. The thing about updating the MacOS disk driver is all it took, and I was able to boot into the install I had done from yesterday. Yay !! Thanks to *Everyone* who helped here. Amazing that there are people around that remember the incantations one has to do to get these Old World boxen to work with a current Linux. Nicolas, do you mind if I add these instructions to the Debian Wiki ? I'll be sure to give full attribution. Cheers. -- Regards, S.D.Allen - Toronto -- To UNSUBSCRIBE, email to debian- powerpc- [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] Hello Stephen (and everyone else), Being polite this time ;-) Glad the step by step worked. Please make sure you acknowledge Rick as well, without this help, I would never have gotten my install working either The list works! Having read the other posts about the expert installer setting, I would add that in my experience setting the installer to expert did not allow me to avoid the installer trying to install quik. On older versions (eg Woody) even without putting the installer in expert mode one could stop this (and the install manual explained how). With Etch, the installer just pushed ahead regardless of what I tried to do to stop it. Fortunately, since quik does not work with ext3 file systems, it aborted. Hope you enjoy your new system. I have found Debian to run extremely well on these systems. Best wishes, Nick. The University of Dundee is a registered Scottish charity, No: SC015096 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: The status of Preemptible kernels on PowerPC?
On Mon, 2008-09-08 at 19:14 -0300, Rogério Brito wrote: > Hi there. > > In the past, there were some problems with the PREEMPT option of the > kernel and PowerPC and I remember that BenH just recommended that we > disabled it when compiling kernels from his tree (gee, that was quite > some time ago). > > Does anybody know what the current status is? I've been running kernels with CONFIG_PREEMPT_VOLUNTARY=y for a long time without any problems. It also does seem to help a lot for interactivity vs. disk I/O. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: G3 Beige Tower install with BootX - help
Hello all, I have been working with Debian for quite a few years now and using powermac G3 machines with extra network cards in them as routers and firewalls, etc. These machines were set up back in the days of Woody and have been kept uptodate with security updates, but otherwise pretty much left untouched. Due to the issues around the firmware in these machines and because it was useful, I always set them up to boot initially into mac OS9 then use BootX to hand over the Debian. This worked a treat. However, I thought it would be good come up to date by installing Etch instead. I'll bring this up to Lenny. [Rick] I used a free machine that was not actually in use and ran the install using the current network install ISO. I used the Lenny Beta2 "businesscard" install disk. Things have changed since the days of woody and it now seems that floppy images (boot image and root image) are no longer used. Hence, I copied the initrd.gz file over to the mac HD and set that as the ram disk for the install. I also copied across the linux kernel and put that into the kernels folder in the system folder. In a little more detail: I drag-n-dropped the "vmlinux" and "initrd.gz" files from the Debian install CD (they are in the "install/powerpc" directory) into the MacOS9 "System Folder:Linux Kernels" folder. Then I chose those two as the "Kernel" and "use specified RAM disk" options in BootX. I set the "More kernel arguments" box to "DEBCONF_PRIORITY=low" (without the quotes) to specify that I wanted to run the installer in "expert" mode, so I could do a couple of non- default tricks needed by OldWorld Macs using BootX. You may or may not want to check the "No video driver" checkbox, depending on your video hardware. This is the equivalent of the "video=ofonly" in yaboot. You'll have to experiment to find out which option works for you. You may (probably will) want to change the "Ramdisk size" option to a larger number. I use 32768. The default is 8192. Using that allows me to boot into the installer where I answered the questions in the usual way, until I got to the step "Load Installer Components from CD". There I chose the option to install "hfs-modules": HFS filesystem support. We'll need them later on when we copy the new customized kernel and initrd to the MacOS9 partition. This is the first "non-default trick" for BootX installation, for which we need to be in "expert mode". There will be another occasion later. and using the installer partitioner in the installer I deleted the previous linux partition (hda7) and swap (hda8) and made new ones. I used the "manual partitioning" option and created "root" and "swap" partitions. Note that these two partitions should have single digit numbers. Otherwise, during the reboot following the installation, the Linux boot process will hang "waiting for the root partition". I suspect this is a bug somewhere in the code that decodes the kernel arguments. Putting this restriction another way, the root and swap partitions should each be chosen from hda7, hda8, or hda9 (assuming your MacOS9 partition is hda6, as it usually will be.) If either of them are hda10 or greater, you'll have problems later. You can use two-digit partition numbers for things like "/home" and "/usr", it's just the root that is restricted. The "guided partitioning" will try to create an ext2 "boot" partition. This is necessary for the quik bootloader, but completely *un*necessary for BootX. In fact, it's actually undesirable because I've recently discovered that the default size (8 MB) for the "boot" partition is too small -- kernel and initrd have grown since quik was written. So including /boot as just a directory in the root partition allows it to have arbitrarily large contents. While you're there in the partitioner, make a note of the partition numbers of your MacOS9 and root partitions. You'll want them later. Then installed the base system, etc,etc all the way through to where it runs tasksel. I just leave that at the basic system for now. Following on some more, finally we get to the point of having finished "Select and install software" where the next thing it would want to do is "Install quik on a hard disk". You do *not* want to install quik. You've got MacOS9 and BootX to do that job. So skip over that line and continue with "Continue without boot loader". It will tell you that you need to use the vmlinux from the "boot" partition and set the kernel parameter "root=" to the root partition that you just installed into. Write down the root partition number (if you didn't do so during the partitioning step) you'll need it later. At this point you should switch to a different console (hit the "alt" and "F2" keys) and do the following magical stuff: mount -v -t hfsplus /dev/hda6 /mnt # Instead of hda6 you should use th
IBM RS/6000 44P 170 Install
It seems that all info that I can find on the web for installing Debian on this machine is outdated. Every guide describes the installation of 3.0 yet every guide is older than the latest firmware for this machine. All I did was install the new firmware on the server and installed Debian using the debian-40r4a-powerpc-netinst. It went like any other install on x86 except yaboot instead of grub. It has been up for two weeks running a MYSQL database without issue. My thanks to all who contributed to this port and Ill be glad to help anyone installing Debian on this 44P. Ben
