headers
Paul Newhouse | 8 Nov 2010 22:49

NetBSD 5.0.2 and Broadcom 5761 PCI network card

Installed NetBSD 5.0.2 from ftp.netbsd.org.
I installed this on a Dell Precision T3500.
It does not recognize the Broadcom 5761 builtin
(0x14E4 0x1681).  Is there a driver for this 
card available on 5.0.2?  

I'd really prefer to run NetBSD on this thing,
but I can't change the physical hardware.

TIA,
Paul
Permalink | Reply | 8 comments |
headers
Joerg Sonnenberger | 8 Nov 2010 23:14
Picon

Re: NetBSD 5.0.2 and Broadcom 5761 PCI network card

On Mon, Nov 08, 2010 at 01:49:57PM -0800, Paul Newhouse wrote:
> Installed NetBSD 5.0.2 from ftp.netbsd.org.
> I installed this on a Dell Precision T3500.
> It does not recognize the Broadcom 5761 builtin
> (0x14E4 0x1681).  Is there a driver for this 
> card available on 5.0.2?  

No. Support was added to current in January, but I don't think it was
pulled up to netbsd-5.

Joerg
Permalink | Reply | 0 comments |
headers
Paul Newhouse | 9 Nov 2010 00:03

Re: NetBSD 5.0.2 and Broadcom 5761 PCI network card

On Mon, Nov 08, 2010 at 01:49:57PM -0800, Paul Newhouse wrote:

> > Installed NetBSD 5.0.2 from ftp.netbsd.org.
> > I installed this on a Dell Precision T3500.
> > It does not recognize the Broadcom 5761 builtin
> > (0x14E4 0x1681).  Is there a driver for this
> > card available on 5.0.2?
> 
> No. Support was added to current in January, but I don't think it was
> pulled up to netbsd-5.

AH!!! KEWL!!  Is there a fairly recent stable branch/tag in current?
Or is top of the tree it???  Should I be asking such things in another list??

Thanks,
Paul
Permalink | Reply | 6 comments |
headers
Martin S. Weber | 10 Nov 2010 01:26
Picon

M$ Wireless 400 Mouse (related to kern/41737?)

Hey...

I got a new mouse - a microsoft wireless 400. It comes with
a "nano transceiver" which reports as 

uhidev0 at uhub3 port 1 configuration 1 interface 0
uhidev0: Microsoft Microsoft® Nano Transceiver v2.0, rev 2.00/6.34, addr 2, iclass 3/1
ukbd1 at uhidev0
wskbd2 at ukbd1 mux 1
uhidev3 at uhub3 port 1 configuration 1 interface 1
uhidev3: Microsoft Microsoft® Nano Transceiver v2.0, rev 2.00/6.34, addr 2, iclass 3/1
uhidev3: 28 report ids
uhid2 at uhidev3 reportid 18: input=0, output=0, feature=1
uhid3 at uhidev3 reportid 22: input=4, output=0, feature=0
uhid4 at uhidev3 reportid 23: input=0, output=0, feature=1
ums0 at uhidev3 reportid 26: 5 buttons, W and Z dirs
wsmouse1 at ums0 mux 0
uhid5 at uhidev3 reportid 28: input=3, output=0, feature=0
uhidev4 at uhub3 port 1 configuration 1 interface 2
uhidev4: Microsoft Microsoft® Nano Transceiver v2.0, rev 2.00/6.34, addr 2, iclass 3/0
uhidev4: 8 report ids
uhid6 at uhidev4 reportid 3: input=1, output=0, feature=0
uhid7 at uhidev4 reportid 4: input=1, output=0, feature=0
uhid8 at uhidev4 reportid 7: input=7, output=0, feature=0
uhid9 at uhidev4 reportid 8: input=1, output=0, feature=0

Now when trying to use the mouse, I noticed that it's basically not working:
mouse movement is VERY slow, at the same time 100% of one CPU is stuck in
sys (as seen on xosview) and the X log file is filled with:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Manuel Bouyer | 10 Nov 2010 21:42

Re: NetBSD 5.0.2 and Broadcom 5761 PCI network card

On Mon, Nov 08, 2010 at 03:03:24PM -0800, Paul Newhouse wrote:
> > No. Support was added to current in January, but I don't think it was
> > pulled up to netbsd-5.
> 
> AH!!! KEWL!!  Is there a fairly recent stable branch/tag in current?
> Or is top of the tree it???  Should I be asking such things in another list??

AFAIK there's no recent branch or tag in current, so you should give
HEAD a try. I guess you could update only the kernel/modules, and keep
the userland at 5.0.2

--

-- 
Manuel Bouyer <bouyer <at> antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--
Permalink | Reply | 4 comments |
headers
Paul Newhouse | 11 Nov 2010 07:55

Re: NetBSD 5.0.2 and Broadcom 5761 PCI network card


>  
>  On Mon, Nov 08, 2010 at 03:03:24PM -0800, Paul Newhouse wrote:
>  > > No. Support was added to current in January, but I don't think it was
>  > > pulled up to netbsd-5.
>  > 
>  > AH!!! KEWL!!  Is there a fairly recent stable branch/tag in current?
>  > Or is top of the tree it???  Should I be asking such things in another list??

Manuel Bouyer <bouyer <at> antioche.eu.org> writes:

>  
>  AFAIK there's no recent branch or tag in current, so you should give
>  HEAD a try. I guess you could update only the kernel/modules, and keep
>  the userland at 5.0.2

I built  GENERIC from HEAD.  It gets to a point where it asks something like:

 .... (wd0a):

when I hit enter it just sits there.  I'll reinstall 5.0.2 and see if it's wd0 
or some other name??

I built an iso boot image from HEAD.  When I try to install it hangs while it 
is discovering the environment.  Usually some USB device, I'll have some time 
tomorrow to try it again and write down where it actually is.

Thanks,
Paul
(Continue reading)

Permalink | Reply | 3 comments |
headers
Matthias Scheler | 16 Nov 2010 20:15
Picon
Favicon

Re: NetBSD 5.0.2 and Broadcom 5761 PCI network card

On Wed, Nov 10, 2010 at 10:55:21PM -0800, Paul Newhouse wrote:
> >  AFAIK there's no recent branch or tag in current, so you should give
> >  HEAD a try. I guess you could update only the kernel/modules, and keep
> >  the userland at 5.0.2
> 
> I built  GENERIC from HEAD.  It gets to a point where it asks something
> like:
> 
>  .... (wd0a):

Please try building and using the "MONOLITHIC" kernel instead.

	Kind regards

--

-- 
Matthias Scheler                                  http://zhadum.org.uk/
Permalink | Reply | 2 comments |
headers
Paul Newhouse | 17 Nov 2010 06:22

Re: NetBSD 5.0.2 and Broadcom 5761 PCI network card

>  On Wed, Nov 10, 2010 at 10:55:21PM -0800, Paul Newhouse wrote:
>  > >  AFAIK there's no recent branch or tag in current, so you should give
>  > >  HEAD a try. I guess you could update only the kernel/modules, and keep
>  > >  the userland at 5.0.2
>  > 
>  > I built  GENERIC from HEAD.  It gets to a point where it asks something
>  > like:
>  > 
>  >  .... (wd0a):
>  
>  Please try building and using the "MONOLITHIC" kernel instead.
>  
>  	Kind regards
>  
>  -- 
>  Matthias Scheler                                  http://zhadum.org.uk/

I'll try that as soon as I can.  

Thanks,
Paul
Permalink | Reply | 0 comments |
headers
Paul Newhouse | 18 Nov 2010 06:46

Re: NetBSD 5.0.2 and Broadcom 5761 PCI network card

>  On Wed, Nov 10, 2010 at 10:55:21PM -0800, Paul Newhouse wrote:
>  > >  AFAIK there's no recent branch or tag in current, so you should give
>  > >  HEAD a try. I guess you could update only the kernel/modules, and keep
>  > >  the userland at 5.0.2
>  > 
>  > I built  GENERIC from HEAD.  It gets to a point where it asks something
>  > like:
>  > 
>  >  .... (wd0a):
>  
> Matthias Scheler wrote:
>
>  Please try building and using the "MONOLITHIC" kernel instead.

MONOLITHIC from HEAD with 5.0.2 userland worked.

Thanks,
Paul
Permalink | Reply | 0 comments |
headers
Jeff Rizzo | 18 Nov 2010 23:31
Favicon

kgdb expected to work?

I'm doing something a little weird, so before trying to debug it (in 
specific), I wanted to see if anyone actually _uses_ kgdb successfully 
at all these days.  Note that I haven't actually used kgdb since 
dual-serial-port boxes were the norm (probably 2002 or so), so I'm quite 
rusty.

I'm running some VMs under VMWare Fusion on MacOSX - and it just 
occurred to me that I might be able to debug using kgdb under serial 
port emulation.  A couple folks gave me some pointers, and I have things 
kind-of-sort-of working in that I can attach GDB and "continue" 
execution of the kernel.

However!

when I launch the kernel (basically GENERIC with DDB removed and KGDB 
enabled at 115200) with "boot -d", I get the following on console:

kgdb waiting...fatal breakpoint trap in supervisor mode
trap type 1 code 0 eip c057224c cs 8 eflags 296 cr2 0 ilevel 8

...I can actually attach gdb at that point, which I do.  (This is a 
cross-gdb running under MacOS, built with MKCROSSGDB=yes from the same 
src tree as the kernel)

Like so:

(gdb) set remotebreak 1
(gdb) set remotebaud 115200
(gdb) target remote 127.0.0.1:12303
(gdb)
(Continue reading)

Permalink | Reply | 2 comments |

Gmane