Re: Installation report and plans for oldworld power macintoshes
On Sun, Jan 18, 2004 at 12:31:08PM +0100, Sven Luther wrote: > On Sat, Jan 17, 2004 at 02:15:39PM -0500, Joey Hess wrote: > > Sven Luther wrote: > > > And there i faced the last problem, well most probably a bug or > > > something, i was simply presented with a login prompt, and i had not the > > > root password to enter it. Normally at this time, it should have booted > > > in the post-d-i install process, and proceeded smoothly with the > > > install. Why this happened has me trully baffled, but i couldn't do > > > much, for lack of root password. > > > > Boot with init=/bin/sh or such, and check /etc/inittab; it should have > > an entry in it to run base-config. > > Well, i have loged in another install on the disk, and mounted the root > partition. i attach the inittab here, there is no such thing as > base-config entry in it. Also strange, altough other files have January > 17 dates, the inittab has date : Dec 23 23:18. > > I have a supsision that maybe there was an older system install on this > partition previously, altough parted did not detect any filesystem and > supposedly did the install. > > This is not supposed to happen, since d-i should have made a new ext3 > filesystem on this partition, at least i asked him to do so, so i am a > bit confused. > > But maybe this is due to one of the previous steps (yaboot in > particular) failing, and d-i all the time wanting to come back to it. Oops, forgot the inittab, here it is. Friendly, Sven Luther # /etc/inittab: init(8) configuration. # $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $ # The default runlevel. id:2:initdefault: # Boot-time system configuration/initialization script. # This is run first except when booting in emergency (-b) mode. si::sysinit:/etc/init.d/rcS # What to do in single-user mode. ~~:S:wait:/sbin/sulogin # /etc/init.d executes the S and K scripts upon change # of runlevel. # # Runlevel 0 is halt. # Runlevel 1 is single-user. # Runlevels 2-5 are multi-user. # Runlevel 6 is reboot. l0:0:wait:/etc/init.d/rc 0 l1:1:wait:/etc/init.d/rc 1 l2:2:wait:/etc/init.d/rc 2 l3:3:wait:/etc/init.d/rc 3 l4:4:wait:/etc/init.d/rc 4 l5:5:wait:/etc/init.d/rc 5 l6:6:wait:/etc/init.d/rc 6 # Normally not reached, but fallthrough in case of emergency. z6:6:respawn:/sbin/sulogin # What to do when CTRL-ALT-DEL is pressed. ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now # Action on special keypress (ALT-UpArrow). #kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work." # What to do when the power fails/returns. pf::powerwait:/etc/init.d/powerfail start pn::powerfailnow:/etc/init.d/powerfail now po::powerokwait:/etc/init.d/powerfail stop # /sbin/getty invocations for the runlevels. # # The "id" field MUST be the same as the last # characters of the device (after "tty"). # # Format: # ::: # # Note that on most Debian systems tty7 is used by the X Window System, # so if you want to add more getty's go ahead but skip tty7 if you run X. # 1:2345:respawn:/sbin/getty 38400 tty1 2:23:respawn:/sbin/getty 38400 tty2 3:23:respawn:/sbin/getty 38400 tty3 4:23:respawn:/sbin/getty 38400 tty4 5:23:respawn:/sbin/getty 38400 tty5 6:23:respawn:/sbin/getty 38400 tty6 # Example how to put a getty on a serial line (for a terminal) # #T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100 #T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100 # Example how to put a getty on a modem line. # #T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3
Re: Installation report and plans for oldworld power macintoshes
On Sat, Jan 17, 2004 at 02:15:39PM -0500, Joey Hess wrote: > Sven Luther wrote: > > And there i faced the last problem, well most probably a bug or > > something, i was simply presented with a login prompt, and i had not the > > root password to enter it. Normally at this time, it should have booted > > in the post-d-i install process, and proceeded smoothly with the > > install. Why this happened has me trully baffled, but i couldn't do > > much, for lack of root password. > > Boot with init=/bin/sh or such, and check /etc/inittab; it should have > an entry in it to run base-config. Well, i have loged in another install on the disk, and mounted the root partition. i attach the inittab here, there is no such thing as base-config entry in it. Also strange, altough other files have January 17 dates, the inittab has date : Dec 23 23:18. I have a supsision that maybe there was an older system install on this partition previously, altough parted did not detect any filesystem and supposedly did the install. This is not supposed to happen, since d-i should have made a new ext3 filesystem on this partition, at least i asked him to do so, so i am a bit confused. But maybe this is due to one of the previous steps (yaboot in particular) failing, and d-i all the time wanting to come back to it. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installation report and plans for oldworld power macintoshes
Sven Luther wrote: > And there i faced the last problem, well most probably a bug or > something, i was simply presented with a login prompt, and i had not the > root password to enter it. Normally at this time, it should have booted > in the post-d-i install process, and proceeded smoothly with the > install. Why this happened has me trully baffled, but i couldn't do > much, for lack of root password. Boot with init=/bin/sh or such, and check /etc/inittab; it should have an entry in it to run base-config. -- see shy jo signature.asc Description: Digital signature
Re: Installation report and plans for oldworld power macintoshes
On Sat, Jan 17, 2004 at 03:56:01PM +0100, Bastian Blank wrote: > On Fri, Jan 16, 2004 at 07:13:41PM +0100, Gaudenz Steinlin wrote: > > Another possible solution which would be less intrusive to core > > components like anna would be to handle this via the isinstallable > > scripts in the quik-installer package. yaboot-installer currently does > > this to make sure it's only used on newworld powermac. Gaudenz, i have to shatter your illusions here, yaboot-installer does nothing such. Now that the new -5 powerpc kernels have been used in linux-kernel-di, i decided to give the installation a try on my pegasos box, and here is what happened : I easily built the initrd enabled kernel using the netboot initrd (the cdrom one is too big). I booted it with the devfs=mount option, and it worked well. First problem appeared as i got to choose the keyboard. Only USB-pmac keyboard were available, while i need ps2 keyboards. This resulted in me choosing the USB-pmac french keyboard, which worked some, but either Alt or the function keys were not mapped, so i couldn't switch to the second console. Which gives : Problem 1 : keyboard selection = => Easy solution. Propose both ps2 and USB-pmac (and maybe amiga for apus) keyboard as choice for powerpc. I think the oldworld adb keyboards get emulated as USB-pmac ones, so this should be no problem. Someone with oldworld hardware would have to confirm though. Then everything went well, there was some issue with my sym53c8xx scsi card not being detected, so i could not test the partitioning scheme on my scsi removable disk, but i guess that this should be ok, since i can use parted. Problem 2 : partitioning = => I don't know if parted is used on all powerpc subarches, but i guess it could at least be possible. I called parted by hand from a shell (and thus discovered that Alt+F2 did not work) and it worked well. That said, maybe there is some message or something which should tell the user what kind of partition table should be chosen, depending on subarches. So, i chose a partition of my main disk, taking the risk of again losing everything, and proceeded with the install. This went well, upto the point where yaboot-installer was to be run, and naturally complained about no apple bootstrap partition or something. Problem 3 : bootloader = => Here the bootloaders, quik for oldpmac, yaboot for newpmac, nothing for the other subarches, need to check for the subarch. This can be done by either the isinstallable script, or the libd-i arch detection code. I guess that the best would be the creation of smallish udebs for the other subarches without bootloader, which could simply tell the user that there is no bootloader for its subarch and the steps needed to boot the final kernel. This could include information on where the kernel has been installed and such. Ok, this is mostly what needs to be done to enable support for chrp, prep, chrp-rs6k and chrp-pegasos powerpc subarches. Not really all that much. I rebooted the box by chosing "finish and reboot", altough the french translation let me a bit dubious about if it was the right thing to do, but i will tell that the french translation team once it is done, and then proceeded to reboot into the partition by hand. And there i faced the last problem, well most probably a bug or something, i was simply presented with a login prompt, and i had not the root password to enter it. Normally at this time, it should have booted in the post-d-i install process, and proceeded smoothly with the install. Why this happened has me trully baffled, but i couldn't do much, for lack of root password. > > As these little udebs are really small it does not really matter much if > > the get installed by anna or not. No, as long as they don't get used when they should not. > Sven Luther and myself decided to enable the subarchitecture matching in > anna and libdi. The yaboot-installer changes should propagate into > unstable tomorrow, the other changes may need some days. Cool. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installation report and plans for oldworld power macintoshes
On Fri, Jan 16, 2004 at 07:13:41PM +0100, Gaudenz Steinlin wrote: > Another possible solution which would be less intrusive to core > components like anna would be to handle this via the isinstallable > scripts in the quik-installer package. yaboot-installer currently does > this to make sure it's only used on newworld powermac. > > As these little udebs are really small it does not really matter much if > the get installed by anna or not. Sven Luther and myself decided to enable the subarchitecture matching in anna and libdi. The yaboot-installer changes should propagate into unstable tomorrow, the other changes may need some days. Bastian -- Respect is a rational process -- McCoy, "The Galileo Seven", stardate 2822.3 signature.asc Description: Digital signature
Re: Installation report and plans for oldworld power macintoshes
On Fri, Jan 16, 2004 at 07:18:16PM +0100, Gaudenz Steinlin wrote: > If yaboot-installer is presented to you as an option this is clearly a > bug. Please tell us which architecture "archdetect" reports on your > machine. What's the return code of yaboot-installers "isinstallable" > script? I'll test. However, archdetect wasn't on the initrd. I think it has been pulled in by anna, but I don't know if it has been run. -- Jeremie Koenig <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installation report and plans for oldworld power macintoshes
Sorry, I did not read your installation report before replying to this mail. If yaboot-installer is presented to you as an option this is clearly a bug. Please tell us which architecture "archdetect" reports on your machine. What's the return code of yaboot-installers "isinstallable" script? Gaudenz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installation report and plans for oldworld power macintoshes
Am Mit, den 14.01.2004 schrieb Jeremie Koenig um 23:25: > - try to make the commented subarch code in anna come to life, in > order to get a suitable bootloader for one's subarch. > > If anyone has ideas about the above things, please speak now. Another possible solution which would be less intrusive to core components like anna would be to handle this via the isinstallable scripts in the quik-installer package. yaboot-installer currently does this to make sure it's only used on newworld powermac. As these little udebs are really small it does not really matter much if the get installed by anna or not. Gaudenz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installation report and plans for oldworld power macintoshes
On Thu, Jan 15, 2004 at 12:57:33PM -0600, Stephen R Marenka wrote: > On Thu, Jan 15, 2004 at 01:23:14PM +0100, Jeremie Koenig wrote: > > > Ok, I won't care. I do care about something, however : is there a > > distribution of miBoot in a readable archive format (there seem to be no > > stuffit free implementation) ? Is there a license for it ? Is the source > > code available ? I can't find this on http://penguinppc.org/~benh/, > > which seems to be the home. > > It seems to be in boot-floppies cvs. > > debian-boot/boot-floppies/powerpc-specials/miBoot/ Yes, I found that. But there's still no license/source code. A friend should unsit the distribution for me soon, let's hope it'll be there. -- Jeremie Koenig <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installation report and plans for oldworld power macintoshes
On Thu, Jan 15, 2004 at 01:23:14PM +0100, Jeremie Koenig wrote: > Ok, I won't care. I do care about something, however : is there a > distribution of miBoot in a readable archive format (there seem to be no > stuffit free implementation) ? Is there a license for it ? Is the source > code available ? I can't find this on http://penguinppc.org/~benh/, > which seems to be the home. It seems to be in boot-floppies cvs. debian-boot/boot-floppies/powerpc-specials/miBoot/ -- Stephen R. Marenka If life's not fun, you're not doing it right! <[EMAIL PROTECTED]> signature.asc Description: Digital signature
Re: Installation report and plans for oldworld power macintoshes
On Wed, Jan 14, 2004 at 11:30:53PM +0100, Sven Luther wrote: > > - add the floppy image type for powerpc to the build directory, > > using the "-small" powerpc kernel (the big one won't fit on a > > floppy.) I guess separate boot floppies will be needed for > > different subarches ; > > You probably don't care about floppy target on other subarches. I doubt > they will be usefull on newworld pmac, and other subarches can use > different install media anyway. Ok, I won't care. I do care about something, however : is there a distribution of miBoot in a readable archive format (there seem to be no stuffit free implementation) ? Is there a license for it ? Is the source code available ? I can't find this on http://penguinppc.org/~benh/, which seems to be the home. Debian woody doesn't seem to contain anything of this, either. > > - produce a quik-installer udeb ; > > - try to make the commented subarch code in anna come to life, in > > order to get a suitable bootloader for one's subarch. > > Oh. That is why the pegasos keyboard detection got broken. Who did > comment that out and why ? I don't think so. The piece of code I'm speaking about is just keeping udebs for wrong subarches from being installed. It'd only help with the boot loader. -- Jeremie Koenig <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installation report and plans for oldworld power macintoshes
On Wed, Jan 14, 2004 at 11:25:33PM +0100, Jeremie Koenig wrote: > Hello, > > I just finished a sarge installation on OldWorld pmac, using the woody > miboot boot-floppy-hfs.bin and a home-built kernel. I'm now going to try > to use this system to get floppy images building for oldworld powermac > ASAP, the ultimate goal being to get beta2/ppc support oldworld. > > My TODO-list for the next days : > - add the floppy image type for powerpc to the build directory, > using the "-small" powerpc kernel (the big one won't fit on a > floppy.) I guess separate boot floppies will be needed for > different subarches ; You probably don't care about floppy target on other subarches. I doubt they will be usefull on newworld pmac, and other subarches can use different install media anyway. > - produce a quik-installer udeb ; > - try to make the commented subarch code in anna come to life, in > order to get a suitable bootloader for one's subarch. Oh. That is why the pegasos keyboard detection got broken. Who did comment that out and why ? Thanks Jeremie for helping out with oldworld pmacs debian-installer. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
