[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Potato boot floppies problems on MVME (was Re: MVME162, The saga continues.....)



On Thu, Apr 06, 2000 at 03:14:53PM +0200, Christian T. Steigies wrote:
> On Thu, Apr 06, 2000 at 09:06:55AM -0400, Jim Ziegler wrote:
> > On Wed, Apr 05, 2000 at 11:38:32PM +0000, John K. Stevenson wrote:
> > > Debian installer. Not altogether well yet, fdisk states 
> > >  Your system is not supported yet!
> > 
> > For some reason the script calls the wrong fdisk.  You have to
> > shell out at that point and use (I believe it is) pmac-fdisk.
> Which script? Are you trying to install slink(stable) or potato(frozen)?
> If its potato, we can still fix it, please send a patch ;-)

With potato the /sbin/fdisk script in root.bin is broken for Motorola VME
boards.  This is a root.bin I grabbed from

http://www.debian.org/~cts/debian-m68k/boot-floppies/

a couple of days ago:

-rw-rw-r--    1 richard  richard    873286 Apr  4 19:13 root.bin

/proc/hardware gives, for example, "Model: Motorola MVME166", and the
script doesn't cope with the space between Motorola and MVME166:

    Arch=`cat /proc/hardware | ( read line; set -- $line;
          if [ "$1" = "Model:" ]; then echo $2 ; fi)`

and then tries to match Arch with

        BVME*|Motorola\ MVME*)

Doesn't work because $2 is "Motorola", $3 is "MVME*".  I changed the
setting of Arch to

    Arch=`cat /proc/hardware | ( read line; set -- $line;
          if [ "$1" = "Model:" ]; then shift; echo $* ; fi)`

and that works for "Motorola MVME177", but I've no idea whether it will
break Amiga etc.

Alternatively we could just change the match in the case statement to
be

	BVME*|Motorola)




Another problem with that root.bin is that /dev/console is major 4 minor 0,
which is wrong for 2.2 kernels.  Should be major 5 minor 1.  If I don't
fix that then the install on MVME hangs with "Cannot open initial console".


I was also surprised that the tftplilo.conf didn't append "console=ttyS0"
(note ttyS0, not /dev/ttyS0 as per 2.0 kernels), but that hasn't mattered
so far.


I've only got as far as partition harddisk so far, but I have base2_2.tgz
so I'll continue and see what happens.

Richard


Reply to: