Thinkpad 600E and 5.2

[Kevin Oberman]

> Date: Thu, 29 Jul 2004 13:24:38 -0700
> From: Gary Kline <kline at tao.thought.org>
> 
> On Thu, Jul 29, 2004 at 12:57:39PM -0700, Kevin Oberman wrote:
> > > Date: Thu, 29 Jul 2004 12:32:15 -0700
> > > From: Gary Kline <kline at tao.thought.org>
> > > 
> > > On Thu, Jul 29, 2004 at 11:29:22AM -0700, Kevin Oberman wrote:
> > > > > From: "Peter Sandilands" <peter at sandilands.vu>
> > > > > Date: Thu, 29 Jul 2004 10:34:30 +1000
> > > > > 
> > > 	[ ... ]
> > > 
> > > > 
> > > > I just fired up my 600E. It's running 5.2-BETA from Dec. of last year.
> > > > Something my have broken since then, but I get NEWCARD to work with the
> > > > following in /boot/loader.conf: hw.cbb.start_memory="0x20000000"
> > > > hw.pci.allow_unsupported_io_range="1"
> > > > 
> > > > My kernel config is:
> > > > device	  cbb
> > > > device	  pccard
> > > > device	  cardbus
> > > > 
> > > > It was not happy with ACPI, so I am running APM.
> > > > 
> > > > My Xircom card seems quite happy there.
> > > 
> > > 
> > > 	A couple of questons.  First, we are prob'ly running a similar
> > > 	5.2; none of the files in my KERNEL conf directory is older
> > > 	that early Dec., '03.  Where is the NEWCARD file?  Should my
> > > 	Xircom be recognized once I rebuild the GENERIC kernel?  
> > > 	I see that what you have as ^define targets and nodefines in
> > > 	OLDCARD.
> > 
> > There is no "NEWCARD" file. GENERIC is NEWCARD. The config lines I
> > included result in a NEWCARD kernel. OLDCARD uses pcic and card while
> > GENERIC uses cbb, cardbus, and pccard. The dmesg should contain entries
> > for 2 each cbb, cardbus, and pccard devices. The actual Ethernet device
> > will be way down the dmesg from the other stuff.
> 
> 	Thanks for clarifying.  I'm about 45 minutes into a rebuild
> 	with KERCONF=GENERIC.  I should know fairly soon; will post
> 	further comments|queries in a few hours.
> 
> 	<PERSONAL>
> 	when did lbl become es.net?  i worked at llnl for a few years
> 	and thought all the labs were .gov.  
> 	</PERSONAL>

LBL won the contract to operate ESnet about 8 years ago. Prior to that
ESnet was operated as a part of the NERSC supercomputing facility at
LLNL. ESnet is the wide area network that provides connectivity to DOE
laboratories and contract facilities around the country. We act as an
NSP for LLNL, LBNL, LANL, Sandia, Brookhaven, Fermilab, Argonne, and
about 40 other sites and maintain a 10 Gbps trans-continental backbone
to carry the traffic between DOE sites and US and international research
sites such as CERN. We also provide commercial connectivity for our
sites and peer with over 100 commercial Internet providers such as
UUnet, Sprint, Savvis and AT&T.

While we are currently located at LBNL (and I hope to stay there),
except for administrative support, we LBNL is just another site on the
network. So my work address is es.net, but I can also be reached at
KOberman at lbl.gov. The legal name of LBNL is the rather verbose one in my
.sig file, but lab management prefers "Berkeley Lab", so I stick it in
there, too.

I was at LLNL for 23 years before moving to LBNL, mostly in the
Engineering Department where my last job was managing their internal
networks. Might I ask when and where you worked at LLNL?
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net			Phone: +1 510 486-8634