headers
George Harvey | 2 Mar 2007 00:05

Re: 4.0 Pullup Testing

On Wed, 28 Feb 2007 10:13:18 -0500
"Stephen M. Rumble" <stephen.rumble <at> utoronto.ca> wrote:

> Hello everyone,
> 
> I'd like to pull up many of my changes from -current to the netbsd-4  
> branch for inclusion in the next release. Among them are several  
> feature additions and some bug fixes, which I'd very much like to get 
>  out there. However, I have no hardware at hand to test with at the  
> moment.
> 
> I've compiled kernels for all machines and placed them at  
> ftp.netbsd.org/pub/NetBSD/misc/rumble/4.0/ .
> 
> If anyone has the time to pull down one that they could test (if it  
> boots and appears immediately unbroken, it should be sufficient. The  
> changes from 4.0 aren't that significant and have been tested in  
> -current.), I'd very much appreciate it.

I've got a R5000 Challenge S with a Phobos G130 card. Your IP2x test
kernel boots OK and detects all three Ethernet interfaces. I've run
quick FTP transfer tests on the 2nd 10Mb port (sq1) and on the Phobos
100Mb (tlp0) and they both look good. I've also got a Set 100Mb card
that I'll put in and test at the weekend.

I'll try and dig out my R5000 O2 to test the IP3x kernel as well.

Let me know if you want the dmesg output or any specific tests run.

George
(Continue reading)

Permalink | Reply | 1 comment |
headers
Stephen M. Rumble | 2 Mar 2007 00:45
Picon
Picon
Favicon

Re: 4.0 Pullup Testing

Quoting George Harvey <fr30 <at> dial.pipex.com>:

> I've got a R5000 Challenge S with a Phobos G130 card. Your IP2x test
> kernel boots OK and detects all three Ethernet interfaces. I've run
> quick FTP transfer tests on the 2nd 10Mb port (sq1) and on the Phobos
> 100Mb (tlp0) and they both look good. I've also got a Set 100Mb card
> that I'll put in and test at the weekend.
>
> I'll try and dig out my R5000 O2 to test the IP3x kernel as well.

My changes shouldn't touch IP3x at all (with the exception of a tiny  
patch to mec(4)). I'm not too concerned about this case, so don't  
worry about it if your machine is not immediately accessible.

> Let me know if you want the dmesg output or any specific tests run.

Nope, I've nothing specific in mind. As I said, the changes aren't big  
and were tested in -current. I'm just making sure that there isn't any  
obvious breakage due to back-porting.

Let me know if the Set Engineering board doesn't work properly. I  
imagine it will be fine.

Much appreciated,
Steve
Permalink | Reply | 0 comments |
headers
Thierry Lacoste | 2 Mar 2007 23:11
Picon

is sgimipscd-3.0.2.iso bootable

I'm confused. According to the FAQ 
http://www.netbsd.org/Ports/sgimips/faq.html#bootstrapping
"Since NetBSD 3.0 the sgimipscd.iso image is bootable"

I recall having to build my own installation cd but it was before 3.0.

I downloaded and burned sgimipscd-3.0.2.iso
but cannot boot from it.

>> hinv
                   System: IP22
                Processor: 150 Mhz R4400, with FPU
     Primary I-cache size: 16 Kbytes
     Primary D-cache size: 16 Kbytes
     Secondary cache size: 1024 Kbytes
              Memory size: 128 Mbytes
                 Graphics: Indy 24-bit
                SCSI Disk: scsi(0)disk(1)
                SCSI Disk: scsi(0)disk(3)
               SCSI CDROM: scsi(0)cdrom(4)
                    Audio: Iris Audio Processor: version A2 revision 4.1.0

>> boot -f scsi(0)cdrom(4)rdisk(0)partition(8)ip2xboot
dks0d4s8: volume header not valid
Unable to load scsi(0)cdrom(4)rdisk(0)partition(8)ip2xboot: no recognizable 
file system on device.

Any help appreciated.

Regards,
(Continue reading)

Permalink | Reply | 501 comments |
headers
Izumi Tsutsui | 3 Mar 2007 03:22
Picon
Gravatar

Re: is sgimipscd-3.0.2.iso bootable

lacoste <at> univ-paris12.fr wrote:

> I downloaded and burned sgimipscd-3.0.2.iso
> but cannot boot from it.

Hmm, actually sgimipscd-3.0.2.is looks plain ISO image
and doesn't have sgivol header.

I don't know how the image was created exactly, but
src/distrib/cdrom/Makefile looks to have a problem
on ivoking the sgivol(8) program as a host tool.

How about this image?
ftp://ftp.NetBSD.org/pub/NetBSD/misc/tsutsui/sgimipscd-3.0.2.iso.gz
---
Izumi Tsutsui
Permalink | Reply | 502 comments |
headers
Thierry Lacoste | 3 Mar 2007 15:13
Picon

Re: is sgimipscd-3.0.2.iso bootable

On Saturday 03 March 2007 03:22, Izumi Tsutsui wrote:
> lacoste <at> univ-paris12.fr wrote:
> > I downloaded and burned sgimipscd-3.0.2.iso
> > but cannot boot from it.
>
> Hmm, actually sgimipscd-3.0.2.is looks plain ISO image
> and doesn't have sgivol header.
>
> I don't know how the image was created exactly, but
> src/distrib/cdrom/Makefile looks to have a problem
> on ivoking the sgivol(8) program as a host tool.
>
> How about this image?
> ftp://ftp.NetBSD.org/pub/NetBSD/misc/tsutsui/sgimipscd-3.0.2.iso.gz
> ---
> Izumi Tsutsui
Thanks. It works.
I have two remarks.

1) I had to issue the boot command twice !?!

>> boot -f scsi(0)cdrom(4)rdisk(0)partition(8)ip2xboot

Cannot load scsi(0)cdrom(4)rdisk(0)partition(8)ip2xboot.
Illegal f_magic number 0xbe5, expected MIPSELMAGIC or MIPSEBMAGIC.
Unable to load scsi(0)cdrom(4)rdisk(0)partition(8)ip2xboot: execute format 
error
>> boot -f scsi(0)cdrom(4)rdisk(0)partition(8)ip2xboot

NetBSD/sgimips 3.0.2 Bootstrap, Revision 1.2
(Continue reading)

Permalink | Reply | 2 comments |
headers
Izumi Tsutsui | 3 Mar 2007 17:41
Picon
Gravatar

Re: is sgimipscd-3.0.2.iso bootable

lacoste <at> univ-paris12.fr wrote:

> 1) I had to issue the boot command twice !?!
> 
> >> boot -f scsi(0)cdrom(4)rdisk(0)partition(8)ip2xboot
> 
> Cannot load scsi(0)cdrom(4)rdisk(0)partition(8)ip2xboot.
> Illegal f_magic number 0xbe5, expected MIPSELMAGIC or MIPSEBMAGIC.
> Unable to load scsi(0)cdrom(4)rdisk(0)partition(8)ip2xboot: execute format 
> error
> >> boot -f scsi(0)cdrom(4)rdisk(0)partition(8)ip2xboot
> 
> NetBSD/sgimips 3.0.2 Bootstrap, Revision 1.2
> (builds <at> b0.netbsd.org, Wed Nov  1 05:28:20 UTC 2006)

Looks ARCS' bug, but if it could be a workaround it's okay :-)

> 2) The instalation fails when mounting the cd to install sets.
> Is this expected?
> 
>      Status: Command failed
>     Command: /sbin/mount -rt cd9660 /dev/cd0a /mnt2
>      Hit enter to continue
> --------------------------------------------------------------------------------
> mount_cd9660: /dev/cd0a on /mnt2: Invalid argument

I can reproduce it on my IP32 and there is another problem
in src/distrib/cdrom/Makefile on creating sgivolhdr.

Could you try this one?
(Continue reading)

Permalink | Reply | 1 comment |
headers
Thierry Lacoste | 3 Mar 2007 20:44
Picon

Re: is sgimipscd-3.0.2.iso bootable


> Could you try this one?
> ftp://ftp.netbsd.org/pub/NetBSD/misc/tsutsui/sgimipscd-3.0.2-bootable.iso.g
>z
>
> It works fine on IP32, and if it works on your IP22
> I'll commit it and ask releng to check how it goes.
> ---
> Izumi Tsutsui
>
It works great.
Thanks.

Thierry.
Permalink | Reply | 0 comments |
headers
Manuel Bouyer | 5 Mar 2007 19:56

Re: UPDATE: various changes on INSTALL and iso generation

On Mon, Mar 05, 2007 at 05:49:00PM +0100, Manuel Bouyer wrote:
> Hi,
> here's an updated patch for my changes on iso generation. Changes since
> [...]
> 
> ftp://asim.lip6.fr/outgoing/bouyer/install_cdrom.diff

I've a problem with the sgimips iso: it can't be mounted as iso9660 fs.
I don't understand what's the difference with the code in distrib/cdrom
or etc/etc.sgimips. From what I understood, this builds a SGI volume
header, and adds the iso image as is after the volume header.
The 3.1 sgimips iso image can be mounted on i386, yet the one I generate
can't. On the other hand, sgivol can grook the iso I generated but can't grook
the one from 3.1. Is the 3.1 iso (from pub/NetBSD/iso/3.1) bootable on
sgimips ?
Can someone explain me what I've done wrong ?

--

-- 
Manuel Bouyer <bouyer <at> antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--
Permalink | Reply | 7 comments |
headers
Izumi Tsutsui | 6 Mar 2007 00:12
Picon
Gravatar

Re: UPDATE: various changes on INSTALL and iso generation

bouyer <at> antioche.eu.org wrote:

> I've a problem with the sgimips iso: it can't be mounted as iso9660 fs.
> I don't understand what's the difference with the code in distrib/cdrom
> or etc/etc.sgimips. From what I understood, this builds a SGI volume
> header, and adds the iso image as is after the volume header.
> The 3.1 sgimips iso image can be mounted on i386, yet the one I generate
> can't. On the other hand, sgivol can grook the iso I generated but can't grook
> the one from 3.1.

FYI, I've just fixed distrib/cdrom/Makefile:
http://mail-index.netbsd.org/source-changes/2007/03/04/0016.html
http://mail-index.netbsd.org/source-changes/2007/03/04/0017.html

> Is the 3.1 iso (from pub/NetBSD/iso/3.1) bootable on
> sgimips ?

Probably not, they seem raw iso images without sgivolhdr.
See recent port-sgimips archives.
---
Izumi Tsutsui
Permalink | Reply | 6 comments |
headers
Stephen M. Rumble | 6 Mar 2007 00:28
Picon
Picon
Favicon

Re: UPDATE: various changes on INSTALL and iso generation

Quoting Izumi Tsutsui <tsutsui <at> ceres.dti.ne.jp>:

> FYI, I've just fixed distrib/cdrom/Makefile:
> http://mail-index.netbsd.org/source-changes/2007/03/04/0016.html
> http://mail-index.netbsd.org/source-changes/2007/03/04/0017.html

Will these be pulled-up for 4.0?

Steve
Permalink | Reply | 2 comments |

Gmane