On 11 Mar 2003, Bob Sloots wrote:
> On Tue, 2003-03-11 at 13:59, Bob Sloots wrote:
> > On Tue, 2003-03-11 at 12:26, Stew Benedict wrote:
> > > On 11 Mar 2003, Bob Sloots wrote:
> > >
> > > > Stew,
> > > >
> > > > I tried an install on my 7600:
> > > > - afaik I can only do text install, right? (text works ofcourse, but
> > > > graphical would be nice)
> > >
> > > My bad - broke the Xpmac setup migrating to 9.1 installer. Although on my
> > > 7600, the XFree install works at 640x480, from BootX. I checked both video
> > > related boxes in BootX.
> >
> > I'll give it a shot.
>
> I tried following:
> - check "no video driver" AND "force video": screen split vertically in
> halves, only left half used, colors bad, text barely readable (not good)
> - check "no video driver" , leave "force video" unchecked: same as
> previous
> - leave "no video driver" unchecked and check "force video": screen
> split horizontally in halves, only top half used, image doubled, colors
> bad etc. (not good)
>
> Do I need an extra kernel argument?
> (I use "devfs=mount ramdisk_size=40000 root=/dev/ram3")
>
I don't specify devfs at all for install. I'm using a non-mac monitor
(MAG), so MacOS insists it can only do 640x480 (no driver for the monitor,
what crap!). Maybe that's why it works for me. Colors are set at
"thousands of colors" in MacOS.
I use:
BootX Options:
Force video settings: checked
Use specified RAM Disk: all.gz
Kernel: vmlinux
Arguments: root=/dev/ram3 ramdisk_size=40000
No video driver: checked
> >
> > >
> > > > - using the 9.1beta1/2 I could use the via-rhine network module, using
> > > > rc1 insmod complains about unresolved symbols (mii_... amongst others)
> > > > (mace works fine but is 10Mb i.o. 100Mb)
> > >
> > > Must be some dependencies needed for that NIC driver. I can add them in
> > > if you can figure out what they are. I had similar issues with pcnet32 on
> > > the RS6000.
> > >
> >
> > I'll jot down the complaints I see next install tryout.
>
> Here's what I see:
> ...
> have to insmod via-rhine
> needs mii
> file-not-found-in-archive mii.o
> needs via-rhine
> unresolved symbol mii_nway_restart_R018b8111
> unresolved symbol mii_link_ok_...
> unresolved symbol mii_ethtool_gset_...
> unresolved symbol generic_mii_ioctl_...
> unresolved symbol mii_ethtool_sset_...
> failed
> warning, insmod failed (via-rhine)
>
OK, just mii then. that's what pcnet32 wanted too. (seperate RS6000
stage1 to fit on a floppy). I'll try to get that into the stage1 modules.
> >
> > > > - install halts when nearly finished (after step in which yaboot is
> > > > configured(??)), I had to break off
> > >
> > > Don't know what's going on there, probably some invasive probe I didn't
> > > disable.
> > >
> > > > - boot fails because ramdisk can not be found (I copied the
> > > > vmlinuz-2.4.21pre4-10mdk and initrd.2.4.21pre4-10mdk.ext3 from
> > > > disk/BootX to my "System folder/Linux kernels" and selected them in the
> > > > BootX panel)
> > >
> > > That should be all that's needed. I don't use the system folder, but
> > > other than that, that's what I do. Where are you seeing "ramdisk can't be
> > > found, from the kernel?"
> >
> > I'll be more elaborate.
>
> Booting OK until:
> ...
> Loading ext3 module
> Mounting /proc filesystem
> Creating root device
> Mounting root filesystem with flags noatime
> mount: error 6 mounting ext3 flags noatime
> Well, retrying without the option flags
> mount: error 6 mounting ext3
> Well, retrying read-only without any flag
> mount: error 6 mounting ext3
> pivotroot: pivot_root (/sysroot, /sysroot/initrd) : 2
> ... (text about rebooting in 180 seconds)
>
> > I also tried to boot the 2.4.21pre4-10mdk kernel+initrd on my
> > Cooker-install with the same results (also not working after creating my
> > own initrd)
> >
OK - I used the provided kernel and initrd from the same RC1 ISO you have:
Are you specifying root?
BootX Options:
Force video settings: unchecked
Use specified RAM disk: initrd-2.4.21pre4-1mdk.ext3
Kernel: vmlinuz-2.4.21pre4-10mdk
Arguments: root=/dev/sda7 devfs=mount
No video driver: unchecked
> > > > - default keymap is not right, so I can't react to disk-check findings,
> > > > but after second reboot disk is clean, so on we go (I renamed the
> > > > /etc/sysconfig/console/default.kmap)
> > > >
> > >
Seems that loading the keymap is what is breaking things:
[EMAIL PROTECTED] rc.d]# gendiff . .ppc91
--- ./rc.sysinit.ppc91 2003-03-11 03:34:50.000000000 -0500
+++ ./rc.sysinit 2003-03-11 04:21:54.000000000 -0500
@@ -242,6 +242,7 @@
progress 3
+if [ "$ARCH" != "ppc" ];then
if [ "`/sbin/consoletype`" = "vt" -a -x /bin/loadkeys ]; then
KEYTABLE=
KEYMAP=
@@ -267,6 +268,7 @@
echo
fi
fi
+fi
# Set the hostname.
action "Setting hostname %s: " ${HOSTNAME} hostname ${HOSTNAME}
You can test this by applying the patch,
rm -fr /lost+found
touch /etc/forcefsck
And reboot.
Seemed to be able to enter "y" here now, instead of "4".
> > Done that, only problem during install is creation of initrd (but I
> > allready have that one from the Cooker-install) because of need for
> > loop-device.
> >
You lost me here. I know this was a kernel problem at one time, but I
haven't seen any loop issues lately.
Stew Benedict
--
MandrakeSoft
PPC FAQ: http://www.linux-mandrake.com/en/ppcFAQ.php3
IRC: irc.freenode.net #cooker-ppc
Archives: http://marc.theaimsgroup.com/?l=mandrake-cooker-ppc&r=1&w=2
