Re: update on beige G3 bootx issues
On Mon, 1 Oct 2001, Paul Rodriguez wrote: > Hmm... there is no root device field, but under options, I can specify > the ramdisk, I choose the all.gz from the cd. > Sorry about that. I just pulled up BootX again, as I haven't run it in a while. When using a Ramdisk, that field is replaced with the "Ramdisk Size" field. > In the meantime I'm going to keep trying. I'm going to try now with a > different graphics card. Would it help if I sent some sort of device > configuration file from the mac? I'm not very familiar with the > macintosh, and maybe knowing exactly what hardware is in this machine > would help. > A different graphics card is only going to complicate matters. Your issue is the drives, not graphics. >From what you've told me so far, you are able to get past stage1 into stage2 correct? (select language). Is is true that the only portions of the CD you've copied to MacOS are the all.gz and vmlinux files? If this is so, and you are getting to stage2 and/or the rescue mode, then the CD is being found. What I would like to see is the information from Apple System Profiler, concerning Devices and Volumes, in particular the SCSI bus, as that seems to be where you are having problems. Also, if it's possible, do a pdisk (MacOS version - see html doc in "docs" on CD for URL) listing of the drives. Either mail or post screenshots of these screens from MacOS. If you really want to swap out some hardware, and this machine has IDE - an IDE drive would make your life a lot easier at this point. Initialize it with MacOS and make sure to leave free space for Linux. Stew Benedict -- MandrakeSoftOH/TN, USA http://perso.mandrakesoft.com/~sbenedict/ PPC Faq: http://marc.theaimsgroup.com/?l=mandrake-cooker-ppc&m=99441208917647&w=
Re: update on beige G3 bootx issues
Hmm... there is no root device field, but under options, I can specify the ramdisk, I choose the all.gz from the cd. Do you know if 8.1 for the PPC is due out any time soon, maybe I won't have any install issues with a new verion. In the meantime I'm going to keep trying. I'm going to try now with a different graphics card. Would it help if I sent some sort of device configuration file from the mac? I'm not very familiar with the macintosh, and maybe knowing exactly what hardware is in this machine would help. -Paul Rodriguez > Most versions of BootX I'm familar with require you to specify the "root" > device. For the installer or rescue image, that should be a ramdisk, > rather than any hard drive. > > Stew Benedict > > _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: update on beige G3 bootx issues
On Mon, 1 Oct 2001, Paul Rodriguez wrote: > It already has detected Symbios|53c875, mesh and mac53c94. There > doesn't seem to be any place to manually type in modprobe. > Well that should be more than enough SCSI modules (you really have three controllers?). I'm not sure what to tell you beyond this. All that is normally needed is the appropriate controller module and sd_mod for hard drive detection. For instance, with an exernal SCSI MO on my Powerbook: [stew@powerbook-cooker stew]$ sudo /sbin/modprobe sd_mod Password: [stew@powerbook-cooker stew]$ /sbin/lsmod Module Size Used by mesh 17152 0 (autoclean) (unused) sd_mod 13360 0 (unused) dmasound_awacs 24464 0 dmasound_core 11280 0 [dmasound_awacs] soundcore 4880 3 [dmasound_core] macserial 38256 0 (autoclean) af_packet 15136 1 (autoclean) ds 8400 1 i82365 23872 1 pcmcia_core46064 0 [ds i82365] bmac 12080 1 (autoclean) supermount 39072 2 (autoclean) [stew@powerbook-cooker stew]$ dmesg | tail -8 scsi0 : MESH mesh: target 6 synchronous at 5.0 MB/s Vendor: FUJITSU Model: M2513EL Rev: 0030 Type: Optical Device ANSI SCSI revision: 02 Attached scsi removable disk sda at scsi0, channel 0, id 6, lun 0 SCSI device sda: 310352 2048-byte hdwr sectors (636 MB) sda: Write Protect is off sda: sda1 sda2 sda3 For a SCSI CD, you would want sr_mod, but you shouldn't need to manually load these. > I'm not sure what you mean about root=/dev/ram3 . There is no space to > type this in on my Bootx screen except the kernel parameters. > Most versions of BootX I'm familar with require you to specify the "root" device. For the installer or rescue image, that should be a ramdisk, rather than any hard drive. Stew Benedict -- MandrakeSoftOH/TN, USA http://perso.mandrakesoft.com/~sbenedict/ PPC Faq: http://marc.theaimsgroup.com/?l=mandrake-cooker-ppc&m=99441208917647&w=
Re: update on beige G3 bootx issues
Stew Benedict wrote:
> On Sat, 29 Sep 2001, Paul Rodriguez wrote:
>
>
>>Stew Benedict wrote:
>>
>>
>>>On Thu, 27 Sep 2001, Paul Rodriguez wrote:
>>>
>>>
>>>
Also, I currently have two sets of Linux partitions in addition to my
mac os 9 partition. Can I repartion my Linux partitions without
effecting my Mac one? No need for a mac os reinstall?
>>>You should be able too, if we can get you that far. =(
>>>I forget - have you tried both 2.2 and 2.4 kernels and stage1 images?
>>>
>>>I would be curious if you could boot the rescue image, and then manually
>>>modprobe the appropriate scsi driver, and still get the kernel panic.
>>>
>>>Stew Benedict
>>>
>>>
>>>
>>With the 2.2 kernel (instead of vmlinux or 2.4) I get farther. Up to
>>the point when it looks for the disks to partition ("doPartitionDisks").
>> Then it tells me that I have no valid devices on which to create new
>>filesystems.
>>
>>
>
> This is good - actually. It should have offered you an opportunity to
> install some SCSI modules. As an alternative, you can open VT2 and
> modprobe them manually. It is probably "mesh" or "mac53c94":
>
> modprobe mesh
>
> or
>
> modprobe mac53c94
>
>
> Do this before you get to disk partitioning. Is the CD scsi too? Odd that
> ot is seen but not the hard, drives, unless they use different
> controllers.
>
> Expert mode will definitely let you add the SCSI modules. I've been
> working with the IBM user trying to resolve that issue, and have been
> running in expert mode.
>
>
>>With the 2.4 kernel it doesn't recognize my cdrom drive. (A CD-MATSHITA
>>ZS20 CDROM CR-585, stock with my G3.)
>>
>>
>
> Kernel should not make any difference here. Both have the appropriate
> modules?
>
>
>>Using either rescue image with any kernel panics me out and recommends I
>>try init= or id= in the kernel arguments. I've tried different init's
>>but to no avail.
>>
>>
>
> You are doing something wrong here in booting the rescue. Are you using
> root=/dev/ram3, setting the ramdisk to 32000 and still using all.gz, but
> with "rescue" as kernel parameters?
>
>
>>PS I also notice blue error messages in the background when I'm doing
>>a text install. For example as I'm choosing reccommended or expert
>>install I see the perl locale messages in blue in the background.
>>
>>
>
> Normal - ugly but normal.
>
> Stew Benedict
>
>
It already has detected Symbios|53c875, mesh and mac53c94. There
doesn't seem to be any place to manually type in modprobe.
I'm not sure what you mean about root=/dev/ram3 . There is no space to
type this in on my Bootx screen except the kernel parameters.
-Paul Rodriguez
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Re: update on beige G3 bootx issues
On Sat, 29 Sep 2001, Paul Rodriguez wrote:
> Stew Benedict wrote:
>
> > On Thu, 27 Sep 2001, Paul Rodriguez wrote:
> >
> >
> >>Also, I currently have two sets of Linux partitions in addition to my
> >>mac os 9 partition. Can I repartion my Linux partitions without
> >>effecting my Mac one? No need for a mac os reinstall?
> >>
> >>
> >
> > You should be able too, if we can get you that far. =(
> > I forget - have you tried both 2.2 and 2.4 kernels and stage1 images?
> >
> > I would be curious if you could boot the rescue image, and then manually
> > modprobe the appropriate scsi driver, and still get the kernel panic.
> >
> > Stew Benedict
> >
> >
>
> With the 2.2 kernel (instead of vmlinux or 2.4) I get farther. Up to
> the point when it looks for the disks to partition ("doPartitionDisks").
> Then it tells me that I have no valid devices on which to create new
> filesystems.
>
This is good - actually. It should have offered you an opportunity to
install some SCSI modules. As an alternative, you can open VT2 and
modprobe them manually. It is probably "mesh" or "mac53c94":
modprobe mesh
or
modprobe mac53c94
Do this before you get to disk partitioning. Is the CD scsi too? Odd that
ot is seen but not the hard, drives, unless they use different
controllers.
Expert mode will definitely let you add the SCSI modules. I've been
working with the IBM user trying to resolve that issue, and have been
running in expert mode.
> With the 2.4 kernel it doesn't recognize my cdrom drive. (A CD-MATSHITA
> ZS20 CDROM CR-585, stock with my G3.)
>
Kernel should not make any difference here. Both have the appropriate
modules?
> Using either rescue image with any kernel panics me out and recommends I
> try init= or id= in the kernel arguments. I've tried different init's
> but to no avail.
>
You are doing something wrong here in booting the rescue. Are you using
root=/dev/ram3, setting the ramdisk to 32000 and still using all.gz, but
with "rescue" as kernel parameters?
> PS I also notice blue error messages in the background when I'm doing
> a text install. For example as I'm choosing reccommended or expert
> install I see the perl locale messages in blue in the background.
>
Normal - ugly but normal.
Stew Benedict
--
MandrakeSoftOH/TN, USA http://perso.mandrakesoft.com/~sbenedict/
PPC Faq: http://marc.theaimsgroup.com/?l=mandrake-cooker-ppc&m=99441208917647&w=
Re: update on beige G3 bootx issues
Stew Benedict wrote:
> On Thu, 27 Sep 2001, Paul Rodriguez wrote:
>
>
>>Also, I currently have two sets of Linux partitions in addition to my
>>mac os 9 partition. Can I repartion my Linux partitions without
>>effecting my Mac one? No need for a mac os reinstall?
>>
>>
>
> You should be able too, if we can get you that far. =(
> I forget - have you tried both 2.2 and 2.4 kernels and stage1 images?
>
> I would be curious if you could boot the rescue image, and then manually
> modprobe the appropriate scsi driver, and still get the kernel panic.
>
> Stew Benedict
>
>
With the 2.2 kernel (instead of vmlinux or 2.4) I get farther. Up to
the point when it looks for the disks to partition ("doPartitionDisks").
Then it tells me that I have no valid devices on which to create new
filesystems.
With the 2.4 kernel it doesn't recognize my cdrom drive. (A CD-MATSHITA
ZS20 CDROM CR-585, stock with my G3.)
Using either rescue image with any kernel panics me out and recommends I
try init= or id= in the kernel arguments. I've tried different init's
but to no avail.
-Paul Rodriguez
PS I also notice blue error messages in the background when I'm doing a
text install. For example as I'm choosing reccommended or expert
install I see the perl locale messages in blue in the background.
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Re: update on beige G3 bootx issues
On Thu, 27 Sep 2001, Xavier wrote: > errorOpeningFile Mandrake/mdkinst/usr/bin/perl-install/po/en_US.po > errorOpeningFile Mandrake/mdkinst/usr/bin/perl-install/po/en.po > normal > Later I also see: > > kmod:failed to exec /sbin/modprobe -s -k nls_cp437, errno=2 > kmod:failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno=2 > this is OK - it's trying various modules > Hope this helps a little. Of course, when it panics it still gives me: > > sda9Kernel panic: Kernel access of bad area pc c015ea40 lr c01f1564 > address 6960 tsk insmod_138 > here it succeeds loading some module - and then bye-bye =( > Do you think repartitioning my drives would work? > Shouldn't matter, but who knows - do you have an sda9? Can you run the MacOS version of pdisk? See doc/mandrake-ppc.html on the CD for the URL Stew Benedict -- MandrakeSoftOH/TN, USA http://perso.mandrakesoft.com/~sbenedict/ PPC Faq: http://marc.theaimsgroup.com/?l=mandrake-cooker-ppc&m=99441208917647&w=
Re: update on beige G3 bootx issues
On Thu, 27 Sep 2001, Paul Rodriguez wrote: > Also, I currently have two sets of Linux partitions in addition to my > mac os 9 partition. Can I repartion my Linux partitions without > effecting my Mac one? No need for a mac os reinstall? > You should be able too, if we can get you that far. =( I forget - have you tried both 2.2 and 2.4 kernels and stage1 images? I would be curious if you could boot the rescue image, and then manually modprobe the appropriate scsi driver, and still get the kernel panic. Stew Benedict -- MandrakeSoftOH/TN, USA http://perso.mandrakesoft.com/~sbenedict/ PPC Faq: http://marc.theaimsgroup.com/?l=mandrake-cooker-ppc&m=99441208917647&w=
Re: update on beige G3 bootx issues
Also, I currently have two sets of Linux partitions in addition to my mac os 9 partition. Can I repartion my Linux partitions without effecting my Mac one? No need for a mac os reinstall? -Paul Rodriguez Xavier wrote: > Hi, Stew, thank a lot for your help. I tried the alternate version of > bootx or was it an alternate kernel you sent me, but I can't get past > the "loading second stage install with that one". Using the version on > the cd I get just to the next stage (choosing language, agree to > licence, and choose install rather than upgrade) before the kernel > panics, and I thought it would be helpful to include the kernel logs > before it asks me to choose language. > > It says: > > > errorOpeningFile Mandrake/mdkinst/usr/bin/perl-install/po/en_US.po > errorOpeningFile Mandrake/mdkinst/usr/bin/perl-install/po/en.po > > Later I also see: > > kmod:failed to exec /sbin/modprobe -s -k nls_cp437, errno=2 > kmod:failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno=2 > > Hope this helps a little. Of course, when it panics it still gives me: > > sda9Kernel panic: Kernel access of bad area pc c015ea40 lr c01f1564 > address 6960 tsk insmod_138 > > Do you think repartitioning my drives would work? > > -Paul Rodriguez > > > Stew Benedict wrote: > >> On Mon, 24 Sep 2001, Xavier wrote: >> >> >>> One step at a time. I found that if I choose "no video driver" and >>> "text" as a kernel argument (not "install-text") I get a little >>> further.Now, I manage to enter the install program. I get as far >>> as choosing the install method and then the install language. Later >>> I get a kernel panic: >>> >>> sda9Kernel panic: Kernel access of bad area pc c015ea40 lr c01f1564 >>> address 6960 tsk insmod_138 >>> >>> >> >> I'm pretty sure "text" is what I recommended. Someone else mentioned >> "install-text". As I said all you need to do is look at yaboot.conf on >> the CD to see the append arguments and other arguments needed for BootX. >> >> It looks like you have a SCSI drive, with at least 9 partitions (sda9), >> and the kernel panics when the module is loaded (insmod). >> >> I believe some other folks had a similar issue with this and are using >> Phil's workaround: >> >> http://www.linux-mandrake.com/en/demos/temp/BootXtest.sit >> >> Which uses another kernel. >> >> HTH, >> Stew Benedict >> >> > > > > _ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: update on beige G3 bootx issues
Hi, Stew, thank a lot for your help. I tried the alternate version of bootx or was it an alternate kernel you sent me, but I can't get past the "loading second stage install with that one". Using the version on the cd I get just to the next stage (choosing language, agree to licence, and choose install rather than upgrade) before the kernel panics, and I thought it would be helpful to include the kernel logs before it asks me to choose language. It says: errorOpeningFile Mandrake/mdkinst/usr/bin/perl-install/po/en_US.po errorOpeningFile Mandrake/mdkinst/usr/bin/perl-install/po/en.po Later I also see: kmod:failed to exec /sbin/modprobe -s -k nls_cp437, errno=2 kmod:failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno=2 Hope this helps a little. Of course, when it panics it still gives me: sda9Kernel panic: Kernel access of bad area pc c015ea40 lr c01f1564 address 6960 tsk insmod_138 Do you think repartitioning my drives would work? -Paul Rodriguez Stew Benedict wrote: > On Mon, 24 Sep 2001, Xavier wrote: > > >>One step at a time. I found that if I choose "no video driver" and >>"text" as a kernel argument (not "install-text") I get a little further. >>Now, I manage to enter the install program. I get as far as >>choosing the install method and then the install language. Later I get >>a kernel panic: >> >>sda9Kernel panic: Kernel access of bad area pc c015ea40 lr c01f1564 >>address 6960 tsk insmod_138 >> >> > > I'm pretty sure "text" is what I recommended. Someone else mentioned > "install-text". As I said all you need to do is look at yaboot.conf on > the CD to see the append arguments and other arguments needed for BootX. > > It looks like you have a SCSI drive, with at least 9 partitions (sda9), > and the kernel panics when the module is loaded (insmod). > > I believe some other folks had a similar issue with this and are using > Phil's workaround: > > http://www.linux-mandrake.com/en/demos/temp/BootXtest.sit > > Which uses another kernel. > > HTH, > Stew Benedict > > _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: update on beige G3 bootx issues
On Mon, 24 Sep 2001, Xavier wrote: > One step at a time. I found that if I choose "no video driver" and > "text" as a kernel argument (not "install-text") I get a little further. > Now, I manage to enter the install program. I get as far as > choosing the install method and then the install language. Later I get > a kernel panic: > > sda9Kernel panic: Kernel access of bad area pc c015ea40 lr c01f1564 > address 6960 tsk insmod_138 > I'm pretty sure "text" is what I recommended. Someone else mentioned "install-text". As I said all you need to do is look at yaboot.conf on the CD to see the append arguments and other arguments needed for BootX. It looks like you have a SCSI drive, with at least 9 partitions (sda9), and the kernel panics when the module is loaded (insmod). I believe some other folks had a similar issue with this and are using Phil's workaround: http://www.linux-mandrake.com/en/demos/temp/BootXtest.sit Which uses another kernel. HTH, Stew Benedict -- MandrakeSoftOH/TN, USA http://perso.mandrakesoft.com/~sbenedict/ PPC Faq: http://marc.theaimsgroup.com/?l=mandrake-cooker-ppc&m=99441208917647&w=
Re: update on beige G3 bootx issues
One step at a time. I found that if I choose "no video driver" and "text" as a kernel argument (not "install-text") I get a little further. Now, I manage to enter the install program. I get as far as choosing the install method and then the install language. Later I get a kernel panic: sda9Kernel panic: Kernel access of bad area pc c015ea40 lr c01f1564 address 6960 tsk insmod_138 I'm not sure what this means or how to resolve it. -Paul Rodriguez Xavier wrote: > No, the beige G3 is an "old world" macintosh. That's why I'm trying to > get the installer to work with Bootx. Still no luck. > > I've tried every combination. > > -Paul R > > Wijnand Rietman wrote: > >> Hi, >> >> though I'm still having difficulties installing Mandrake-PPC myself >> (due to >> partitioning problems) I maybe can help you out a bit. The machine you >> want >> to install is a "new world" machine, right? I suggest you should use >> yaboot >> to boot your system. I think that the option root device: /dev/ram3 is the >> driver you need to create the ramdisk. >> >> Greetings, Wijnand. >> >> -- >> >>> From: Xavier <[EMAIL PROTECTED]> >>> To: [EMAIL PROTECTED] >>> Subject: update on beige G3 bottx issues >>> Date: zon, 23 sep 2001 17:54 >>> >>> >> >>> Ok, this is where I stand. >>> >>> After starting bootx, I choose the file all.gz. I set the ramdisk size >>> as 32000. I choose vmlinux as my kernel. >>> >>> Whatever I put into my command arguments is ignored, including >>> "install-text" or "text". (Unless of course, they're not being ignored, >>> but just makes no difference to the problem.) >>> >>> Immediatly after clicking linux the system starts up, shows me the name >>> of the kernel, says it is beginning boot and freezes there, in a black >>> screen with some system information. >>> >>> Choosing "no video driver" gets me a little farther, to finishing second >>> stage install, but not to the Mandrake install program. >>> >>> Stew mentioned that he had a setting: >>> >>> root device: /dev/ram3 >>> >>> I have no idea what this is. There are no parameters for me to set to >>> the above, and I'm not sure what that means anyway. >>> >>> These troubles may or may not be related to my video card. If that was >>> the case, it would seem that text install should work, but it's not. >>> >>> -Paul Rodriguez >>> >>> PS I did have some trouble booting my machine after adding the kernels >>> from the Mandrake cd to the bootx folder, but that went away. >>> >>> >>> _ >>> Do You Yahoo!? >>> Get your free @yahoo.com address at http://mail.yahoo.com >>> >>> >>> >> >> > > > > _ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
