From: Tobias N. <tob...@t-...> - 2006-01-14 23:05:26
|
Hi all, I just uploaded a new miboot.iso to my webspace: http://home.vrweb.de/internetzel/miboot.iso That time CD-ROM access should be no problem anymore. Detection of the CD-ROM drive will take some time. That is to prevent the PMU powering off the machine in some cases; I don't know if it really works but ejecting and inserting PC-Cards a lot ot times has been no problem for me with this kernel. The image again contains the Debian Sarge installer. However it might be necessary to modify the yaboot.conf - I discribed this some time ago on the mailing list. The bootloader is preconfigured for "root=/dev/hda8" and "l2cr=0xA9000000" (512kB L2-Cache). @Florian: I think you should replace the miboot.iso on the project site as soon as possible. Tobias |
From: Tobias N. <tob...@t-...> - 2006-01-14 23:17:41
|
Hi all, I just uploaded a new miboot.iso to my webspace: http://home.vrweb.de/internetzel/miboot.iso That time CD-ROM access should be no problem anymore. Detection of the CD-ROM drive will take some time. That is to prevent the PMU powering off the machine in some cases; I don't know if it really works but ejecting and inserting PC-Cards a lot ot times has been no problem for me with this kernel. The image again contains the Debian Sarge installer. However it might be necessary to modify the yaboot.conf - I discribed this some time ago on the mailing list. The bootloader is preconfigured for "root=/dev/hda8" and "l2cr=0xA9000000" (512kB L2-Cache). @Florian: I think you should replace the miboot.iso on the project site as soon as possible. Tobias |
From: Petr <pe...@gm...> - 2006-01-15 00:19:45
|
Hi Tobias, I just tried your new image and it crashes with the same message as described before on Wed, 11 Jan 2006.. :-( Peter On Sun, 2006-01-15 at 00:17 +0100, Tobias Netzel wrote: > Hi all, > > I just uploaded a new miboot.iso to my webspace: > http://home.vrweb.de/internetzel/miboot.iso > That time CD-ROM access should be no problem anymore. > Detection of the CD-ROM drive will take some time. That is to prevent > the PMU powering off the machine in some cases; I don't know if it > really works but ejecting and inserting PC-Cards a lot ot times has > been no problem for me with this kernel. > > The image again contains the Debian Sarge installer. > However it might be necessary to modify the yaboot.conf - I discribed > this some time ago on the mailing list. > The bootloader is preconfigured for "root=/dev/hda8" and > "l2cr=0xA9000000" (512kB L2-Cache). > > @Florian: I think you should replace the miboot.iso on the project site > as soon as possible. > > Tobias > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Nubus-pmac-users mailing list > Nub...@li... > https://lists.sourceforge.net/lists/listinfo/nubus-pmac-users > |
From: Tobias N. <tob...@t-...> - 2006-01-15 10:15:03
|
Hi Peter, I'm sorry, but this miboot.iso will crash every time you boot it up with no media bay IDE driver inserted. I'll solve this issue. Tobias Am 15.01.2006 um 01:19 schrieb Petr: > Hi Tobias, > > I just tried your new image and it crashes with the same message as > described before on Wed, 11 Jan 2006.. :-( > > Peter > > On Sun, 2006-01-15 at 00:17 +0100, Tobias Netzel wrote: >> Hi all, >> >> I just uploaded a new miboot.iso to my webspace: >> http://home.vrweb.de/internetzel/miboot.iso >> That time CD-ROM access should be no problem anymore. >> Detection of the CD-ROM drive will take some time. That is to prevent >> the PMU powering off the machine in some cases; I don't know if it >> really works but ejecting and inserting PC-Cards a lot ot times has >> been no problem for me with this kernel. >> >> The image again contains the Debian Sarge installer. >> However it might be necessary to modify the yaboot.conf - I discribed >> this some time ago on the mailing list. >> The bootloader is preconfigured for "root=/dev/hda8" and >> "l2cr=0xA9000000" (512kB L2-Cache). >> >> @Florian: I think you should replace the miboot.iso on the project >> site >> as soon as possible. >> >> Tobias >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. Do you grep through >> log files >> for problems? Stop! Download the new AJAX search engine that makes >> searching your log files as easy as surfing the web. DOWNLOAD >> SPLUNK! >> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click >> _______________________________________________ >> Nubus-pmac-users mailing list >> Nub...@li... >> https://lists.sourceforge.net/lists/listinfo/nubus-pmac-users >> > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Nubus-pmac-users mailing list > Nub...@li... > https://lists.sourceforge.net/lists/listinfo/nubus-pmac-users > |
From: Petr <pe...@gm...> - 2006-01-15 13:19:09
|
Hi Tobias, I tried your latest miboot.iso with my non-working media bay CDrom inserted and indeed it booted fine from de scsi cdrom this time, so there's progress :-). Now it hangs at the partitioner, so I still can't install, neither on the CF card or a regular ide-hd. The CF card gives errormessages like hda: lost interupt, and based on some googling I tried booting the miboot image with the extra ide=nodma argument, but no luck there either. I have only been successfull with a woody install trough the original MachKernel installer on a regular ide-hd so far, but they die on me anyway after a couple of weeks/months. So I'm still hoping to succeed one day, I can probably borrow another CF card, a working cdrom media bay and another model pb1400 to experiment with. Are other people on this list successful with the miboot images and installing Sarge on a regular hd on the pb1400cs, with or without upgrade card? Peter On Sun, 2006-01-15 at 11:14 +0100, Tobias Netzel wrote: > Hi Peter, > > I'm sorry, but this miboot.iso will crash every time you boot it up > with no media bay IDE driver inserted. > I'll solve this issue. > > Tobias > > > Am 15.01.2006 um 01:19 schrieb Petr: > > > Hi Tobias, > > > > I just tried your new image and it crashes with the same message as > > described before on Wed, 11 Jan 2006.. :-( > > > > Peter > > > > On Sun, 2006-01-15 at 00:17 +0100, Tobias Netzel wrote: > >> Hi all, > >> > >> I just uploaded a new miboot.iso to my webspace: > >> http://home.vrweb.de/internetzel/miboot.iso > >> That time CD-ROM access should be no problem anymore. > >> Detection of the CD-ROM drive will take some time. That is to prevent > >> the PMU powering off the machine in some cases; I don't know if it > >> really works but ejecting and inserting PC-Cards a lot ot times has > >> been no problem for me with this kernel. > >> > >> The image again contains the Debian Sarge installer. > >> However it might be necessary to modify the yaboot.conf - I discribed > >> this some time ago on the mailing list. > >> The bootloader is preconfigured for "root=/dev/hda8" and > >> "l2cr=0xA9000000" (512kB L2-Cache). > >> > >> @Florian: I think you should replace the miboot.iso on the project > >> site > >> as soon as possible. > >> > >> Tobias > >> > >> > >> > >> ------------------------------------------------------- > >> This SF.net email is sponsored by: Splunk Inc. Do you grep through > >> log files > >> for problems? Stop! Download the new AJAX search engine that makes > >> searching your log files as easy as surfing the web. DOWNLOAD > >> SPLUNK! > >> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > >> _______________________________________________ > >> Nubus-pmac-users mailing list > >> Nub...@li... > >> https://lists.sourceforge.net/lists/listinfo/nubus-pmac-users > >> > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > > files > > for problems? Stop! Download the new AJAX search engine that makes > > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > > _______________________________________________ > > Nubus-pmac-users mailing list > > Nub...@li... > > https://lists.sourceforge.net/lists/listinfo/nubus-pmac-users > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Nubus-pmac-users mailing list > Nub...@li... > https://lists.sourceforge.net/lists/listinfo/nubus-pmac-users > |
From: Tobias N. <tob...@t-...> - 2006-01-15 14:41:47
|
Hi again, I again uploaded a new miboot.iso . Now the kernel looks what device is in the media bay and only when it finds an IDE device it tells the IDE driver to probe. It will also detect a floppy drive but there is no driver for it. I also reincluded a patch from the m68k-mac-port that tries to fix a bug in the IDE driver where it sometimes does not correctly detect the drive geometry (perhaps this solves the CF card issue???) I currently think on replacing the nubus-pmac PowerBook interrupt handling routines with the ones for the PowerBook 190 from the m68k-mac-port as they seem to be more robust. Tobias |
From: Joerg S. <jhs...@t-...> - 2006-01-16 02:47:18
|
Hi Tobias, just wanne tell that the new miBoot works just fine till now, the base system is gonne be installed... hope tomorrow it really works :-) Greetz |
From: Petr <pe...@gm...> - 2006-01-16 13:32:20
|
Hi Joerg, How did you create a bootable image from that latest miboot.iso? I'm eager to try it, but sofar I am unable to boot it, after several burn attempts, whereas I had no problems to boot the previous images. Peter On Mon, 2006-01-16 at 03:46 +0100, Joerg Stephan wrote: > Hi Tobias, > > just wanne tell that the new miBoot works just fine till now, > the base system is gonne be installed... hope tomorrow it really > works :-) > > Greetz |
From: Joerg S. <jhs...@t-...> - 2006-01-16 13:47:43
|
Petr wrote: > Hi Joerg, > > How did you create a bootable image from that latest miboot.iso? I'm > eager to try it, but sofar I am unable to boot it, after several burn > attempts, whereas I had no problems to boot the previous images. > > Peter > well, i just burned the image to an cd-rom, i hope noone will blame me, but i burned under WinXP, i insert it and telled MacOS to use it as startvolume. Nothing more Greetz |
From: Raylynn K. <aud...@sp...> - 2006-01-16 05:37:14
|
On Sun, 2006-01-15 at 15:41 +0100, Tobias Netzel wrote: > Hi again, > > I again uploaded a new miboot.iso . > > Now the kernel looks what device is in the media bay and only when it > finds an IDE device it tells the IDE driver to probe. > It will also detect a floppy drive but there is no driver for it. > The 2.2 m68k-mac kernel has a driver for the SWIM II floppy. Part of the code is in m68k assembler, though. Perhaps someone on the list has the time to port it to PPC? > I also reincluded a patch from the m68k-mac-port that tries to fix a > bug in the IDE driver where it sometimes does not correctly detect the > drive geometry (perhaps this solves the CF card issue???) > > I currently think on replacing the nubus-pmac PowerBook interrupt > handling routines with the ones for the PowerBook 190 from the > m68k-mac-port as they seem to be more robust. |
From: Daniel G. <da...@gi...> - 2006-01-26 01:15:41
|
On Mon, 16 Jan 2006 00:37:06 -0500, Raylynn Knight wrote: > The 2.2 m68k-mac kernel has a driver for the SWIM II floppy. Part of > the code is in m68k assembler, though. Perhaps someone on the list has > the time to port it to PPC? AFAIK, the floppy code in the m68k-mac kernel is for SWIM I, not SWIM II, and it did not work at all when I had 2.2.23 running on the IIfx. |
From: Raylynn K. <aud...@sp...> - 2006-01-26 04:35:44
|
On Wed, 2006-01-25 at 17:15 -0800, Daniel Gimpelevich wrote: > On Mon, 16 Jan 2006 00:37:06 -0500, Raylynn Knight wrote: > > > The 2.2 m68k-mac kernel has a driver for the SWIM II floppy. Part of > > the code is in m68k assembler, though. Perhaps someone on the list has > > the time to port it to PPC? > > AFAIK, the floppy code in the m68k-mac kernel is for SWIM I, not SWIM II, > and it did not work at all when I had 2.2.23 running on the IIfx. > > Swim I and II support was added in the last year, coded by Laurent Vivier. The driver your talking about is the swim_iop driver used by the IIfx, and the Quadra 9x0 systems. It was never completed. The comments from the new swim_driver * Copyright (C) 2004 Laurent Vivier <Lau...@wa...> * * based on Alastair Bridgewater SWIM analysis, 2001 * based on SWIM3 driver (c) Paul Mackerras, 1996 * based on netBSD IWM driver (c) 1997, 1998 Hauke Fath. * * Supported Macintoshes: * * II, IIci, IIsi, IIvx, IIx, IIcx, SE/30, * PowerBook 100, PowerBook 140, PowerBook 145, PowerBook 160, * PowerBook 165, PowerBook 165c, PowerBook 170, PowerBook 180, * PowerBook 180c, PowerBook 190, PowerBook 190cs, PowerBook 500, * Performa 460, Performa 550, LC II, LC III, LC 520, Color Classic, * Color Classic II, ClassicII, * Quadra 700, Quadra 800, Quadra 650, Quadra 605, Quadra 610, * Centris 610, Quadra 630, Performa 580, LC 475, LC 575, * And I've verified it works at least on IIci, IIsi, LC475, LC575 and Quadra 650. Ray |
From: Daniel G. <da...@gi...> - 2006-01-26 05:32:58
|
On Wed, 25 Jan 2006 23:35:34 -0500, Raylynn Knight wrote: > Swim I and II support was added in the last year, coded by Laurent > Vivier. The driver your talking about is the swim_iop driver used by > the IIfx, and the Quadra 9x0 systems. It was never completed. Not having looked at the driver source, I was under the impression that swim_iop was part of an overall swim driver. Can you point me to an HTMLized source to the new driver you mean à la http://lxr.linux.no/source so that I may take a look? I am quite fluent in m68k assembly language. |
From: Raylynn K. <aud...@sp...> - 2006-01-27 22:06:18
|
n Wed, 2006-01-25 at 21:32 -0800, Daniel Gimpelevich wrote: > On Wed, 25 Jan 2006 23:35:34 -0500, Raylynn Knight wrote: >=20 > > Swim I and II support was added in the last year, coded by Laurent > > Vivier. The driver your talking about is the swim_iop driver used by > > the IIfx, and the Quadra 9x0 systems. It was never completed. >=20 > Not having looked at the driver source, I was under the impression that > swim_iop was part of an overall swim driver. Can you point me to an > HTMLized source to the new driver you mean =E0 la > http://lxr.linux.no/source so that I may take a look? I am quite fluent i= n > m68k assembly language. >=20 http://cvs.sourceforge.net/viewcvs.py/linux-mac68k/linux-mac68k/drivers/blo= ck/Attic/swim_driver.c?rev=3D1.1.2.1&only_with_tag=3Dlinux-2_2&view=3Dauto = points to the C source file. And http://cvs.sourceforge.net/viewcvs.py/lin= ux-mac68k/linux-mac68k/drivers/block/Attic/swim_asm.S?rev=3D1.1.2.1&only_wi= th_tag=3Dlinux-2_2&view=3Dauto points to the assembly language routines used in the C source. It would be great if someone could provide PPC assembly routines and forward port this driver to 2.4 and 2.6 kernels. Ray |
From: Daniel G. <da...@gi...> - 2006-01-28 04:13:33
|
On Fri, 27 Jan 2006 17:06:04 -0500, Raylynn Knight wrote: > n Wed, 2006-01-25 at 21:32 -0800, Daniel Gimpelevich wrote: >> On Wed, 25 Jan 2006 23:35:34 -0500, Raylynn Knight wrote: >> >> > Swim I and II support was added in the last year, coded by Laurent >> > Vivier. The driver your talking about is the swim_iop driver used by >> > the IIfx, and the Quadra 9x0 systems. It was never completed. >> >> Not having looked at the driver source, I was under the impression that >> swim_iop was part of an overall swim driver. Can you point me to an >> HTMLized source to the new driver you mean à la >> http://lxr.linux.no/source so that I may take a look? I am quite fluent in >> m68k assembly language. >> > > http://cvs.sourceforge.net/viewcvs.py/linux-mac68k/linux-mac68k/drivers/block/Attic/swim_driver.c?rev=1.1.2.1&only_with_tag=linux-2_2&view=auto points to the C source file. And http://cvs.sourceforge.net/viewcvs.py/linux-mac68k/linux-mac68k/drivers/block/Attic/swim_asm.S?rev=1.1.2.1&only_with_tag=linux-2_2&view=auto > points to the assembly language routines used in the C source. It would > be great if someone could provide PPC assembly routines and forward port > this driver to 2.4 and 2.6 kernels. > > Ray This is the first time I have seen assembly language source for m68k Linux, and it appears that the GNU assembler for m68k uses different ways of specifying instruction mnemonics and addressing modes from what I am used to. Nevertheless, I was able to make perfect sense out of the code. Unfortunately, I only have passing knowledge of PPC assembly language, so I wouldn't be able to port it to that. I was hoping to port it to C instead, but having now seen the code, I can tell you that is not going to happen. The C language simply does not provide mechanisms to exactly duplicate what this code is doing. If anyone is well-versed in writing I/O code in PPC assembler (not just general PPC assembly coding) but doesn't know m68k assembly language, I will be glad to provide real-time analysis of this code to aid them in writing equivalent PPC assembly code. The only problem I foresee is concocting ways of duplicating the m68k architecture's exact instruction timing and read-modify-write cycles, etc. |
From: Daniel G. <da...@gi...> - 2006-01-28 08:15:49
|
On Fri, 27 Jan 2006 20:13:06 -0800, Daniel Gimpelevich wrote: > On Fri, 27 Jan 2006 17:06:04 -0500, Raylynn Knight wrote: > >> n Wed, 2006-01-25 at 21:32 -0800, Daniel Gimpelevich wrote: >>> On Wed, 25 Jan 2006 23:35:34 -0500, Raylynn Knight wrote: >>> >>> > Swim I and II support was added in the last year, coded by Laurent >>> > Vivier. The driver your talking about is the swim_iop driver used by >>> > the IIfx, and the Quadra 9x0 systems. It was never completed. >>> >>> Not having looked at the driver source, I was under the impression that >>> swim_iop was part of an overall swim driver. Can you point me to an >>> HTMLized source to the new driver you mean à la >>> http://lxr.linux.no/source so that I may take a look? I am quite fluent in >>> m68k assembly language. >>> >> >> http://cvs.sourceforge.net/viewcvs.py/linux-mac68k/linux-mac68k/drivers/block/Attic/swim_driver.c?rev=1.1.2.1&only_with_tag=linux-2_2&view=auto points to the C source file. And http://cvs.sourceforge.net/viewcvs.py/linux-mac68k/linux-mac68k/drivers/block/Attic/swim_asm.S?rev=1.1.2.1&only_with_tag=linux-2_2&view=auto >> points to the assembly language routines used in the C source. It would >> be great if someone could provide PPC assembly routines and forward port >> this driver to 2.4 and 2.6 kernels. >> >> Ray > > This is the first time I have seen assembly language source for m68k > Linux, and it appears that the GNU assembler for m68k uses different ways > of specifying instruction mnemonics and addressing modes from what I am > used to. Nevertheless, I was able to make perfect sense out of the code. > Unfortunately, I only have passing knowledge of PPC assembly language, so > I wouldn't be able to port it to that. I was hoping to port it to C > instead, but having now seen the code, I can tell you that is not going to > happen. The C language simply does not provide mechanisms to exactly > duplicate what this code is doing. If anyone is well-versed in writing I/O > code in PPC assembler (not just general PPC assembly coding) but doesn't > know m68k assembly language, I will be glad to provide real-time analysis > of this code to aid them in writing equivalent PPC assembly code. The only > problem I foresee is concocting ways of duplicating the m68k > architecture's exact instruction timing and read-modify-write cycles, etc. OK, I figured I ought to take a stab at it anyway. Here is a best approximation in C of the assembly code: http://homepage.mac.com/danielg4/swim_asm.c |
From: Tobias N. <tob...@t-...> - 2006-01-29 23:53:10
|
I think I will try to get it compiled into the nubus-pmac kernel. Unfortunately I don't know for sure whether the PB1400 really has the =20= SWIM II floppy controller. The developer documentation says the only difference between the PB1400 =20= and the PB5300 is the floppy controller. While it says just nothing about the controller chip in the PB5300 it =20= says that the Whitney IC for both has SWIM II functions but the floppy =20= controller in the PB1400 is mentioned by name (something like 82078, a =20= standard floppy controller with documentation available). Might this be a mistake that the Whitney IC in the PB1400 still has =20 SWIM II functions? Tobias Am 28.01.2006 um 09:15 schrieb Daniel Gimpelevich: > On Fri, 27 Jan 2006 20:13:06 -0800, Daniel Gimpelevich wrote: > >> On Fri, 27 Jan 2006 17:06:04 -0500, Raylynn Knight wrote: >> >>> n Wed, 2006-01-25 at 21:32 -0800, Daniel Gimpelevich wrote: >>>> On Wed, 25 Jan 2006 23:35:34 -0500, Raylynn Knight wrote: >>>> >>>>> Swim I and II support was added in the last year, coded by Laurent >>>>> Vivier. The driver your talking about is the swim_iop driver used = =20 >>>>> by >>>>> the IIfx, and the Quadra 9x0 systems. It was never completed. >>>> >>>> Not having looked at the driver source, I was under the impression =20= >>>> that >>>> swim_iop was part of an overall swim driver. Can you point me to an >>>> HTMLized source to the new driver you mean =E0 la >>>> http://lxr.linux.no/source so that I may take a look? I am quite =20= >>>> fluent in >>>> m68k assembly language. >>>> >>> >>> http://cvs.sourceforge.net/viewcvs.py/linux-mac68k/linux-mac68k/=20 >>> drivers/block/Attic/swim_driver.c?rev=3D1.1.2.1&only_with_tag=3Dlinux=20= >>> -2_2&view=3Dauto points to the C source file. And =20 >>> http://cvs.sourceforge.net/viewcvs.py/linux-mac68k/linux-mac68k/=20 >>> drivers/block/Attic/swim_asm.S?rev=3D1.1.2.1&only_with_tag=3Dlinux=20= >>> -2_2&view=3Dauto >>> points to the assembly language routines used in the C source. It =20= >>> would >>> be great if someone could provide PPC assembly routines and forward =20= >>> port >>> this driver to 2.4 and 2.6 kernels. >>> >>> Ray >> >> This is the first time I have seen assembly language source for m68k >> Linux, and it appears that the GNU assembler for m68k uses different =20= >> ways >> of specifying instruction mnemonics and addressing modes from what I =20= >> am >> used to. Nevertheless, I was able to make perfect sense out of the =20= >> code. >> Unfortunately, I only have passing knowledge of PPC assembly =20 >> language, so >> I wouldn't be able to port it to that. I was hoping to port it to C >> instead, but having now seen the code, I can tell you that is not =20 >> going to >> happen. The C language simply does not provide mechanisms to exactly >> duplicate what this code is doing. If anyone is well-versed in =20 >> writing I/O >> code in PPC assembler (not just general PPC assembly coding) but =20 >> doesn't >> know m68k assembly language, I will be glad to provide real-time =20 >> analysis >> of this code to aid them in writing equivalent PPC assembly code. The = =20 >> only >> problem I foresee is concocting ways of duplicating the m68k >> architecture's exact instruction timing and read-modify-write cycles, = =20 >> etc. > > OK, I figured I ought to take a stab at it anyway. Here is a best > approximation in C of the assembly code: > http://homepage.mac.com/danielg4/swim_asm.c > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log = =20 > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD = SPLUNK! > http://sel.as-us.falkag.net/sel?=20 > cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=3D121642 > _______________________________________________ > Nubus-pmac-users mailing list > Nub...@li... > https://lists.sourceforge.net/lists/listinfo/nubus-pmac-users > |
From: Florian B. <eup...@ar...> - 2006-01-26 12:00:32
|
Hi all, I just uploaded the latest miBoot ISO (15-JAN-2005) to SF. I was able to do a successful installation of Debian Sarge 3.1r1 on a clean IDE drive using that ISO and a regular Debian PPC binary-1 jigdo-made CD. There are some quick notes in the corresponding release notes which describe some extra steps I had to take. Please discuss those notes here so I will put together a installation mini-HowTo from its results. Thanks. Florian PS: Tobias, thanks a lot for another great production! ;) |
From: <tob...@t-...> - 2006-01-26 12:46:29
|
Hi Florian, in the release notes you mention the issue with keyboard selection. The following steps solve that problem: - After the error message continue with installation but leave the miboot CD in the drive - After the next error message about missing installation media launch the keyboard configuration step manually - Keyboard configuration should now work. - Eject the CD with the "eject" command and insert the Debian installation CD 1. - Continue installing This has always worked on my machine. Regards, Tobias -----Original Message----- Date: Thu, 26 Jan 2006 13:00:09 +0100 Subject: Uploaded to SF, was Re: [Nubus-pmac-users] New miboot.iso From: Florian Boelstler <eup...@ar...> To: nub...@li... Hi all, I just uploaded the latest miBoot ISO (15-JAN-2005) to SF. I was able to do a successful installation of Debian Sarge 3.1r1 on a clean IDE drive using that ISO and a regular Debian PPC binary-1 jigdo-made CD. There are some quick notes in the corresponding release notes which describe some extra steps I had to take. Please discuss those notes here so I will put together a installation mini-HowTo from its results. Thanks. Florian PS: Tobias, thanks a lot for another great production! ;) ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Nubus-pmac-users mailing list Nub...@li... https://lists.sourceforge.net/lists/listinfo/nubus-pmac-users |
From: Florian B. <eup...@ar...> - 2006-01-27 23:34:52
|
tob...@t-... <tob...@t-...> wrote: > This has always worked on my machine. I will try it and add it to the howto. Thanks, Florian |
From: Florian B. <eup...@ar...> - 2006-01-27 23:30:48
|
I just set up a separate partition on my regular hard disk to enable direct boot using miBoot. I did the following steps: Resize (i.e. shrink) existing MacOS HFS partition with "parted". Create a new partition in resulting space using "mac-fdisk". Establish a new HFS file system using "hformat" (it is part of hfsutils). Copy contents of latest miBoot ISO to new space (unfortunately I had to switch to MacOS to correctly copy the files. Is there another way to do this on Linux? hcopy didn't worked as expected. Perhaps I should have used -m) Modified yaboot.conf (partition was mounted on Linux, yaboot.conf was reformatted to regular linux ascii files. still works) to match my local root partition and added an entry for latest 2.4.30-pre1 miboot.image. Have a nice weekend! Cheers, Florian |
From: Florian B. <eup...@ar...> - 2006-01-28 15:17:26
|
Further, is there a simple way to switch the active boot partition/volume within Linux? Does MacOS care about the "boot flag" that can be set through parted? A method that currently works for me (though complicated): Boot from MacOS CD by holding down Shift+Option+Command+Backspace and change start volume appropriately. Florian |
From: Raylynn K. <aud...@sp...> - 2006-01-30 01:45:33
|
On Sat, 2006-01-28 at 15:17 +0000, Florian Boelstler wrote: > Further, is there a simple way to switch the active boot > partition/volume within Linux? > Does MacOS care about the "boot flag" that can be set through parted? > > A method that currently works for me (though complicated): > Boot from MacOS CD by holding down Shift+Option+Command+Backspace and > change start volume appropriately. > I believe the boot partition/volume is stored in PRAM. It would be nice to have a linux application to change PRAM values such as the boot partition/volume and the initial video resolution and color depth. Ray |
From: Florian B. <eup...@ar...> - 2006-01-30 10:10:14
|
Hi Ray, Raylynn Knight <aud...@sp...> wrote: > I believe the boot partition/volume is stored in PRAM. It would be nice > to have a linux application to change PRAM values such as the boot > partition/volume and the initial video resolution and color depth. Daniel guided me through a hexedit session of /dev/hda1 yesterday. After that the system booted from another partition. I don't know if there any boot volume settings in the PRAM. Daniel's approach worked. IMHO it would be best if mac-fdisk would allow to toggle the bootable flag. Daniel, how do we setup a partition map and those driver partitions from a system that got no MacOS before? Do those partitions contain copyrighted material and/or harddrive-dependent parameters? Florian |
From: Tobias N. <tob...@t-...> - 2006-01-30 10:46:53
|
Hi Florian, you seem to want to get rid of MacOS. I don't think that this would be worth the work. MacOS isn't bad despite of its memory management. Use each OS for the things it is written for. I like the simplicity of MacOS; it's pretty easy to let it do what you want it to do and there aren't hundreds of parameters you can adjust. But the classic MacOS deals pretty bad with memory demanding applications such as browsing modern web sites. In terms of stability, multitasking and flexibility linux is the only way to go. So my opinion is to use MacOS to control the bootup settings. Completing the hardware support of the linux kernel is in my opinion much more useful than getting rid of MacOS - and I don't think you will need to switch boot partitions every day. Best regards, Tobias Am 30.01.2006 um 11:09 schrieb Florian Boelstler: > Hi Ray, > > Raylynn Knight <aud...@sp...> wrote: >> I believe the boot partition/volume is stored in PRAM. It would be >> nice >> to have a linux application to change PRAM values such as the boot >> partition/volume and the initial video resolution and color depth. > > Daniel guided me through a hexedit session of /dev/hda1 > yesterday. After that the system booted from another partition. > I don't know if there any boot volume settings in the PRAM. > Daniel's approach worked. > > IMHO it would be best if mac-fdisk would allow to toggle the bootable > flag. > > Daniel, how do we setup a partition map and those driver partitions > from > a system that got no MacOS before? > Do those partitions contain copyrighted material and/or > harddrive-dependent parameters? > > Florian > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel? > cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > Nubus-pmac-users mailing list > Nub...@li... > https://lists.sourceforge.net/lists/listinfo/nubus-pmac-users > |