Re: install/43954: 5.1 RC4 Installation CD doesn't work on IBM R31 - exec /sbin/init: error 2

[Matto Fransen <matto%matto.nl@localhost>]

The following reply was made to PR port-i386/43954; it has been noted by GNATS.

From: Matto Fransen <matto%matto.nl@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: install/43954: 5.1 RC4 Installation CD doesn't work on IBM R31
 - exec /sbin/init: error 2
Date: Mon, 11 Oct 2010 10:27:15 +0200

 --YD3LsXFS42OYHhNZ
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 Hi David,
 
 On Mon, Oct 11, 2010 at 02:40:03AM +0000, David Holland wrote:
 > The following reply was made to PR port-i386/43954; it has been noted by =
 GNATS.
 >=20
 > From: David Holland <dholland-bugs%netbsd.org@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc:=20
 > Subject: Re: install/43954: 5.1 RC4 Installation CD doesn't work on IBM R=
 31
 >  - exec /sbin/init: error 2
 > Date: Mon, 11 Oct 2010 02:35:40 +0000
 >=20
 >  On Sun, Oct 10, 2010 at 08:05:03AM +0000, matto fransen wrote:
 >   >  Option 1 will be chosen in 0 seconds
 >   >  booting cd0a:netbsd
 >   >  10089048+518916+618576 [521152+508996]=3D3D0xbb283c
 >   >  WARNING: couldn't open /stand/i386/5.1/modules/something
 >   >  Loading something WARNING: couldn't open /stand/i386/5.1/modules/som=
 ething
 >   > =20
 >   >  where "something" is a bunch of garbled characters
 > =20
 >  Ah, it's from the bootloader.
 > =20
 >  Hrm. Does the same CD work in other machines? One possibility is that
 >  it's corrupted somehow, although that admittedly seems unlikely if you
 >  see the same behavior from 5.1RC4 and 5.0.2.
 
 Indeed. =20
 I just tried the CD on a Toshiba Satelitte A200-237, there it works fine.
 
 >  The message should certainly not be garble.
 
 >  Does the file /boot.cfg on the CD contain garble? I think you can
 >  print (text) files from the bootloader but I don't remember how...
  =20
 I mounted it on the IBM R31 (running NetBSD 4) with mount /dev/cd0d=20
 and /boot.cfg is flawless. So that seems not to be the problem.
 
 Cheers,
 
 Matto
 
 --YD3LsXFS42OYHhNZ
 Content-Type: application/pgp-signature; name="signature.asc"
 Content-Description: Digital signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.4.10 (GNU/Linux)
 
 iEYEARECAAYFAkyyymIACgkQOJ62+7VpM0Ib/QCghUWEJWNm+nHWXgbjKIkkK/mP
 S7cAoIh2t6peddb3Yu9KAy9YzKdi/KHw
 =cvoc
 -----END PGP SIGNATURE-----
 
 --YD3LsXFS42OYHhNZ--