Netboot install trouble on a blue and white G3.
After trying to figure out how to netboot the sarge installer on my blue and white G3, I had to give up and use the woody installer instead. The problems I ran into: 1) The install document says to use yaboot to boot the kernel. There's no "yaboot" or yaboot.conf files in the installer directory[1] for sarge. I ended up next trying to use yaboot from woody's installer dir to boot. 2) There's a bunch of kernel+initrd images which don't boot (vmlinuz-*.initrd), none of which are bootable on my blue&white. Openfirmware pukes on the images. 3) There's a generic "vmlinux", which actually loads via yaboot, but yaboot can't load the initrd.gz. 4) The 2.4 netboot images, and 2.4 netboot-minimal images have the same problems. I wouldn't be suprised to see these problems on a testing release, but I'm quite suprised that the *stable* release doesn't come with a working netbootable installer, when the previous version did (and it worked just fine!). [1] http://ftp.debian.org/debian/dists/sarge/main/installer-powerpc/current/images/powerpc/netboot/ Pat -- Purdue University ITAP/RCAC --- http://www.rcac.purdue.edu/ The Computer Refuge --- http://computer-refuge.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
kernel 2.6.8 and 2.6.12 fail to boot on blue&white G3
I just installed debian on a blue and white G3 (another story in itself, see my next email), and tried to install a 2.6 kernel, both kernel-image-2.6.8-powerpc from stable, and 2.6.12 from testing. Both kernels panic when trying modprobing the cmd64x ide driver in their initrd. I had to capture the messages by hand, and this is what I got, booting the 2.6.8 kernel in stable: DAR: BD9D377E, DSIR: 4000 TASK = cfe12000[156] 'modprobe' THREAD: cff3a000Last syscall:128 ... NIP: [c00fbd14] ide_inb+0xc/0x24 LR: [c01026a8 ide_get_or_set_dma_base+0xa8/0x1a4 Call trace: [c0102c90] ide_hwif_setup_dma+0x84/0x154 [c0103020] ide_pci_setup_ports+0x190/0x1f0 [c010314c] do_ide_setup_pci_device+0xcc/0x1a0 [c0103244] ide_setup_pci_device+0x24/0x88 [d18386a8] cmd64x_init_one+0x60/0x74 [cmd64x] ... The "..."s signify more lines which I didn't copy. I couldn't get anything above the DAR: line, as the boot logo was in the way. I tried to get everything I thought was the most relevant. Is there a workaround? Has anyone seen this before? I've got a Rev 1 motherboard, if that could be a part of the problem (that's not going to change, though). I'd really rather be runnign a 2.6 kernel if possible. 2.4.27 from stable boots just fine. Pat -- Purdue University ITAP/RCAC --- http://www.rcac.purdue.edu/ The Computer Refuge --- http://computer-refuge.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: reinstalling tiger
kohzak wrote: > I would like to know if it will be a problem to install Tiger. > Will it erase my dual boot ? You might need to hold the Option key at boot, select Linux, and once the system's booted, rerun 'ybin'. Other than that, it should "just work". > Will i have to reinstall my Debian ? No. -- Derrik Pates [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Request for help to identify some bugs (part two)
On Sun, 2005-10-23 at 11:10 +0200, Yannick Roehlly wrote: > > Hrm... This is a slot loading CD ? I don't know what KDE is trying to do > > there. Do you actually have a media in hte drive when that happen ? > > The problem occurs at the moment I insert a CD in the slot drive. In some > rare cases, there's no problem and when it's a blank cd-rw it's ok. Maybe > kded tries to access to the cdrom to fast? Possibly. It looks like a mixed problem with kded and the kernel (the kernel because the CD driver shouldn't spam your log with what looks like a normal thing). Do you have a bug report open somewhere on a bugzilla ? If not, please open one on bugzilla.kernel.org with all the infos about the issue (don't bother with UDMA stuff, that's a different issue, the real problem is this error in your log triggered by kded) and add me to the CC list of the bug. I'll try to followup. Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Feedback on patch to PowerPC ports pmac page requested
On Sun, Oct 23, 2005 at 10:33:32AM -0700, Shyamal Prasad wrote: > So perhaps the statement needs to be something like > > "For users of the powerpc flavour a 2.4 kernel is also provided to > support Amiga Power-UP (apus) systems, and as a fall back for users > with external kernel modules that are not available for the 2.6 > kernel, but strongly discouraged even in that case :)" Yep. > Or should we also document the miboot issue? (I don't know much about > it, never used an old world Mac for Linux). well, i need to build miboot floppies for sarge, and then we can link to them. They are not in the archive because of the non-free boot sector, and thus they don't work anyway. I will build them in a fixed way so that 2.6 work for them also. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Feedback on patch to PowerPC ports pmac page requested
> "Sven" == Sven Luther <[EMAIL PROTECTED]> writes: Sven> On Sat, Oct 22, 2005 at 07:24:23PM -0700, Shyamal Prasad Sven> wrote: >> the G4) you also have the option of choosing a 2.4 kernel in >> case your hardware is really old. However most hardware built >> after 2001 should be well supported by the default 2.6 kernel. Sven> No way, there is no chance of a 2.4 kernel supporting more Sven> hardware than the 2.6 kernels, the only reason to keep it at Sven> all was for those people needing external modules which Sven> where not rewritten for 2.6, and because of a Sven> at-that-time-unsolved in the miboot floppies generator. Cool. I did not know why the 2.4 kernels were out there which is why I wanted the patch reviewed. Thanks. Sven> The other reason to use 2.4 kernels was if you ran apus or Sven> if nubus powermacs, but the first one, i know 4 users left Sven> and the first of those tested it yesterday since sarge, Sven> while the second was not officially supported in sarge, Sven> altough this may change for etch. So perhaps the statement needs to be something like "For users of the powerpc flavour a 2.4 kernel is also provided to support Amiga Power-UP (apus) systems, and as a fall back for users with external kernel modules that are not available for the 2.6 kernel." Or should we also document the miboot issue? (I don't know much about it, never used an old world Mac for Linux). Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Feedback on patch to PowerPC ports pmac page requested
> "Rogério" == Rogério Brito <[EMAIL PROTECTED]> writes: Rogério> On Oct 22 2005, Shyamal Prasad wrote: >> as +little as 600 to 700M for a really basic system, but you'll Rogério> I question the 600 to 700M figures for a "really basic Rogério> system". I think that these numbers are too high for Rogério> "just the basics", especially if the user is space Rogério> conscious. Hi Rogério, My opinion was originally the same as yours. But since I suspected that linux installations have got larger since I last did a space concious install I tried looking for some documented experience. The i386 install manual says one needs at least 450M. http://www.debian.org/releases/stable/i386/ch03s04.html.en The i386 and powerpc install manuals say that a i386 2.4 install with all standard packages is 573M. http://www.debian.org/releases/stable/powerpc/apcs03.html.en Including swap space I'd say 600M is pushing the lower limit for a normal (i.e. documented in the manual) sarge install. If any one has done it in less do let me know - it has been many years since I've worked on a system with less than 1G of disk space. Cheers! Shyamal
Re: reinstalling tiger
Le Dimanche 23 Octobre 2005 14:15, marco a écrit : > Il giorno dom, 23/10/2005 alle 13.59 +0200, Yannick Roehlly ha scritto: > > Here a simple reset of the openfirmware (Command-Option-P-R a the > > starting of the ibook) does the trick to start again yaboot after a MacOS > > X reinstallation. > > I think this would set OF to boot from the first bootable partition > (which could be tiger's one) You're right Marco! In fact, my disk was carefully partitioned to have the yaboot partition at the begining. ;-) Yannick
Re: reinstalling tiger
Douglas Russell wrote: > It will destroy your yaboot stuff, so I've always booted a CD and rerun > yaboot to reinstall the bootloader stuff. I think it might be possible to > switch back to yaboot by booting to openfirmware and making a choice > there, but I've always done the above and it worked fine. Here a simple reset of the openfirmware (Command-Option-P-R a the starting of the ibook) does the trick to start again yaboot after a MacOS X reinstallation. Yannick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: reinstalling tiger
Dnia 23-10-2005, nie o godzinie 12:51 +0200, Jorge Salamero Sanz napisał(a): > On Sunday 23 October 2005 12:21, kohzak wrote: > > hum, sorry but how i do that ? Just being root and go to /mnt/mypartition > > ? > > mount -t xxx /dev/hdaX /mnt/foo > chroot /mnt/foo > ybin -v > > instead the last two instructions you can also do > > ybin -v -c /mnt/foo/etc/yaboot.conf > > ybin will most probably need /proc to be mounted, so the first way should include mount -t proc bar /mnt/foo/proc before chroot-ing -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: reinstalling tiger
On Sunday 23 October 2005 12:21, kohzak wrote: > hum, sorry but how i do that ? Just being root and go to /mnt/mypartition > ? mount -t xxx /dev/hdaX /mnt/foo chroot /mnt/foo ybin -v instead the last two instructions you can also do ybin -v -c /mnt/foo/etc/yaboot.conf
Re: reinstalling tiger
Hi all Thanks for your quick answer. Jorge Salamero Sanz a écrit : >On Sunday 23 October 2005 12:00, kohzak wrote: > > >>i'm running osx Panther and Debian etch on my ibook 12 G4. >> >>I would like to know if it will be a problem to install Tiger. >>Will it erase my dual boot ? >> >> > >yes > > > >>Will i have to reinstall my Debian ? >> >> > >no > > > >>thanks for any information about that. >> >> > >just reinstall yaboot: > >boot with a livecd, > Ok, i may have a live ubuntu somewhere >mount your linux partition, > mount on /mnt ok >chroot to it, > hum, sorry but how i do that ? Just being root and go to /mnt/mypartition ? >and run ybin -v > > > > ok I will do it this afternoon and comeback here if any problems. koh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: reinstalling tiger
On Sunday 23 October 2005 11:00, kohzak wrote: > Hi all > > i'm running osx Panther and Debian etch on my ibook 12 G4. > > I would like to know if it will be a problem to install Tiger. > Will it erase my dual boot ? When you install Tiger you'll have to make sure that you install it into the partition that Panther was installed in, don't just let it run riot over your whole hard disk. > > Will i have to reinstall my Debian ? It will destroy your yaboot stuff, so I've always booted a CD and rerun yaboot to reinstall the bootloader stuff. I think it might be possible to switch back to yaboot by booting to openfirmware and making a choice there, but I've always done the above and it worked fine. Douglas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: reinstalling tiger
On Sunday 23 October 2005 12:00, kohzak wrote: > i'm running osx Panther and Debian etch on my ibook 12 G4. > > I would like to know if it will be a problem to install Tiger. > Will it erase my dual boot ? yes > Will i have to reinstall my Debian ? no > thanks for any information about that. just reinstall yaboot: boot with a livecd, mount your linux partition, chroot to it, and run ybin -v -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
reinstalling tiger
Hi all i'm running osx Panther and Debian etch on my ibook 12 G4. I would like to know if it will be a problem to install Tiger. Will it erase my dual boot ? Will i have to reinstall my Debian ? thanks for any information about that. koh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem with clock on Beige G3
> Does this patch fixes it ? Sorry for the late reply, it does fix the problem. Thanks a lot ! -- Sylvain Joyeux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Request for help to identify some bugs (part two)
Hi Ben,
Benjamin Herrenschmidt wrote:
> How do you set it to u/dma2 and remind me the exact machine model
It tryed to set the combo drive to udma2 both with "hdparm -q -d1 -X
udma2 /dev/hdc" and with "command_line {hdparm -q -d1 -X udma2 /dev/hdc}"
in /etc/hdparm.conf (if I use transfert_mode, hdparm complains that it
doesn't know this option).
My ibook is a "Late 2004" (october) one.
>> I'm not sure that this problem is related to hardware configuration since
>> it only happen with KDE "media discovery" (when turning off the
>> "gestionnaire de media kded", the cd insertion does not produce the kded
>> madness but the cdrom is not accessible via media:/) and not with de
>> Gnome one.
>
> Hrm... This is a slot loading CD ? I don't know what KDE is trying to do
> there. Do you actually have a media in hte drive when that happen ?
The problem occurs at the moment I insert a CD in the slot drive. In some
rare cases, there's no problem and when it's a blank cd-rw it's ok. Maybe
kded tries to access to the cdrom to fast?
Yannick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
