--OXfL5xGRrasGEqWY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

I'm forwarding this message that I originally sent to netbsd-users.
I'm not certain if that was the right list (or if this one is).  If I'm
posting this to the wrong list, pointers to the appropriate list would
be appreciated.

Anyway, I just wanted to share my BETA2 findings and see if anyone else
is seeing anything similar, if theses are known issues or if I need to
start filing PRs.

        --Jerry

name:  Jerry Alexandratos         ||  Open-Source software isn't a
phone: 703.599.6023               ||  matter of life or death...
email: jerry@thehutt.org          ||  ...It's much more important
                                  ||  than that!

--OXfL5xGRrasGEqWY
Content-Type: message/rfc822
Content-Disposition: inline

	by localhost with POP3 (fetchmail-5.8.5)
	for jerry@localhost (single-drop); Mon, 11 Jun 2001 01:23:06 -0400 (EDT)
  by earth.udlug.org with SMTP; 11 Jun 2001 05:18:22 -0000
  by mail.netbsd.org with SMTP; 11 Jun 2001 05:15:57 -0000
Date: Mon, 11 Jun 2001 01:20:18 -0400
From: Jerry A! <jerry@thehutt.org>
To: netbsd-users@netbsd.org
Subject: 1.5.1_BETA2
Message-ID: <20010611012018.A77606@gemini.thehutt.org>
Reply-To: jerry@thehutt.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Organization: Broken Toys Unlimited
Sender: netbsd-users-owner@netbsd.org

I just ran into 1.5.1_BETA2.  Overall things went well, however I did
run into a few problems.  I wanted to point them out and see if they're
known issues.

On my desktop system everything worked fine (the VIA686b changes even
supported ATA100!), with the following exceptions:

1. Sound; auvia0 is found, but not audio0.

2. Network; sip0 (Netgear FA311 Rev-A1/DB83815) is totally messed up.
It's very strange.  No matter what I do, the card just doesn't seem to
work.  The strange part is that if I try to configure the NIC via DHCP
instead of by hand, it successfully grabs an addresses, configures the
NIC and then just does nothing (just like when I configured the NIC by
hand).  Either way, the end result is the same, I can ping the NIC, but
nothing beyond it.  8(

I also tried installing on my VAIO F270.  Everything installed fine
with one notable exception:

1. Network; ex0 doesn't work.  It comes up with an ether address of
69:00:69:00:69:00.

Has anyone else seen any issues like this?  Do these issues exist under
-current?

Thanks in advance...

        --Jerry

name:  Jerry Alexandratos         ||  Open-Source software isn't a
phone: 703.599.6023               ||  matter of life or death...
email: jerry@thehutt.org          ||  ...It's much more important
                                  ||  than that!

--OXfL5xGRrasGEqWY--