Very Computer

Hello All,

I have just managed to get LinuxPPc onto my StarMax 3000 onto
my internal drive.

After much trouble I can now boot linux every time.
My only problem is that I can not switch back.  The macos command
fails.  It complains about the /dev/nvram device not being there or
something like that.

I have tried to do a MAKEDEV but it does not regenerate the devices.

Does anyone out there know how to do this?  Or Fix this?

Mark Daku

I'm using kernal 2.1.79 from ftp.linuxppc.org

Mark Daku

Quote:> >> >I have just managed to get LinuxPPc onto my StarMax 3000 onto
> >> >my internal drive.

> >> >After much trouble I can now boot linux every time.
> >> >My only problem is that I can not switch back.  The macos command
> >> >fails.  It complains about the /dev/nvram device not being there
> or
> >> >something like that.

> >> >I have tried to do a MAKEDEV but it does not regenerate the
> devices.

> >> >Does anyone out there know how to do this?  Or Fix this?

> >> Should be 'mknod /dev/nvram c 1 10' (IIRC) for 2.1.24

> >I tried this but no luck.  It still screams about not being able to
> open
> >ornot being able to find /dev/nvram.  Would this be a Kernal problem?

> >I'm using kernal 2.1.79 from ftp.linuxppc.org

> The device numbers may have changed in the newer kernels.  You might
> try 10 144 - I've seen this mentioned as /dev/nvram numbers.
> Otherwise,
> I can't help you.

I'll let the group know my success in this thread.

Mark Daku

Quote:> > >> >I have tried to do a MAKEDEV but it does not regenerate the
> > devices.

> > >> >Does anyone out there know how to do this?  Or Fix this?

> > >> Should be 'mknod /dev/nvram c 1 10' (IIRC) for 2.1.24

> > >I tried this but no luck.  It still screams about not being able to

> > open
> > >ornot being able to find /dev/nvram.  Would this be a Kernal
> problem?

> > >I'm using kernal 2.1.79 from ftp.linuxppc.org

> > The device numbers may have changed in the newer kernels.  You might

> > try 10 144 - I've seen this mentioned as /dev/nvram numbers.
> > Otherwise,
> > I can't help you.

> Thanks I'll give that a shot as well.

> I'll let the group know my success in this thread.

In summary:
The device /dev/nvram should have the numbers 10 144 for the vmlinux
kernal 2.1.79.
Thus during the install phase after it sets the boot-device drop down to
the prompt
with <command>-<F2> and rm the /mnt/dev/nvram device and replace it.  To
replace
it type the following command.
mknod /mnt/dev/nvram c 10 144

Also make sure that you have the modules.tgz file that corisponds to the
2.1.79 kernal.
I simple extracted it into /lib/modules.  I then got a new director
called /mnt/lib/modules/2.1.79
this directory now contains the proper modules for the kernal.

After instalation and reboot the following items are now modified.
/dev/nvram
vmlinux
/lib/modules/2.1.79/

Once all of these are updated you can run linux properly on a StarMax
3000 series computer.

Good Luck Kids
Mark Daku