RE: Ethernet card problem

2002-12-09 Thread Thomas Connolly
Thanks very much for the quick reply.
I would agree with that.  The model is a Kingston KNE100TX and it says that
the driver is a dc(4).  Which Ethernet selection and I supposed to pick for
that on Sysinstall?  Is there a way to reconfigure it after installation.  I
apologize for the ignorance but I am very new to all this.  I basically just
went step-by-step through the FreeBSD manual on installation.  There was no
option that said dc(4).  

Thanks again,

Thomas P. Connolly
Senior Development Engineer
Colorado Engineering Experiment Station Inc.
Phone: (970) 897-2711
Fax: (970) 897-2710
Email: [EMAIL PROTECTED]
 

-Original Message-
From: D J Hawkey Jr [mailto:[EMAIL PROTECTED]] 
Sent: Monday, December 09, 2002 9:45 AM
To: Thomas Connolly
Subject: Re: Ethernet card problem

On Dec 09, at 09:32 AM, Thomas Connolly wrote:
 
 Hi all,
 I just installed FreeBSD on an HP Vectra machine with a Kingston KNE 100
 network card.  The FreeBSD Handbook says it is supported.  From
sysinstall,
 I chose the 
 NE1000, NE2000, 3C503, WD/SMC80xx Ethernet Adapters ed0
 Option.  When I went to configure the network device, ed0 did not show up
in
 the list.  Can anyone offer me some guidance here?

Double-check the NIC's model. Variou Kingston NICs are listed as ed(4),
dc(4), and aue(4) compatable. I'd say you picked the wrong one.

 Thank you,
 Thomas Connolly

Dave

-- 
  __ __
  \__   \D. J. HAWKEY JR.   /   __/
 \/\ [EMAIL PROTECTED]/\/
  http://www.visi.com/~hawkeyd/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



RE: Ethernet card problem

2002-12-09 Thread Thomas Connolly
Thanks again for the help.  Can you tell me how to set my interface up
manually so that it will use DHCP for the ip and netmask, gateway, etc.?

Thanks,

Tom Connolly

-Original Message-
From: D J Hawkey Jr [mailto:[EMAIL PROTECTED]] 
Sent: Monday, December 09, 2002 10:25 AM
To: Thomas Connolly
Subject: Re: Ethernet card problem

On Dec 09, at 10:07 AM, Thomas Connolly wrote:
 
 Thanks very much for the quick reply.
 I would agree with that.  The model is a Kingston KNE100TX and it says
that
 the driver is a dc(4).  Which Ethernet selection and I supposed to pick
for
 that on Sysinstall?

dc0, I would imagine.

 Is there a way to reconfigure it after installation.

Oh, yes. Go on through the installation. Afterward, edit /etc/rc.conf to
reflect reality. You'll have lines like these to change:
hostname=sheol.localdomain
ifconfig_ed0=inet 192.168.16.2 netmask 255.255.255.0
What you'll change is the hostname (if need be), and ifconfig_ed0 to
ifconfig_dc0. IIRC, that's all it takes.

 I
 apologize for the ignorance but I am very new to all this.  I basically
just
 went step-by-step through the FreeBSD manual on installation.  There was
no
 option that said dc(4).  

I don't remember how to specify the interface within sysinstall(8), but I'm
sure you can (make sure you've resolved conflicting interrupts first).
I usually set up the network manually, after sysinstall(8), just to stay in
practice!

 Thanks again,
 Thomas P. Connolly
 Senior Development Engineer
 Colorado Engineering Experiment Station Inc.
 Phone: (970) 897-2711
 Fax: (970) 897-2710
 Email: [EMAIL PROTECTED]

Need a telecommuting UNIX SysAdmin in Minnesota?
Dave

-- 
  __ __
  \__   \D. J. HAWKEY JR.   /   __/
 \/\ [EMAIL PROTECTED]/\/
  http://www.visi.com/~hawkeyd/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: Ethernet card problem

2002-12-09 Thread Brian
isnt is /stand/sysinstall, post install config, network, pick yer interface,
answer yes to the dhcp popup, thats it?

BTW, if it asks you if you want to activate now, that typically will not get
you the new parameters on the interface, youll need to either ifconfig it
down and then up, or reboot as a quik dirty way.

Bri

- Original Message -
From: Thomas Connolly [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, December 09, 2002 9:36 AM
Subject: RE: Ethernet card problem


 Thanks again for the help.  Can you tell me how to set my interface up
 manually so that it will use DHCP for the ip and netmask, gateway, etc.?

 Thanks,

 Tom Connolly

 -Original Message-
 From: D J Hawkey Jr [mailto:[EMAIL PROTECTED]]
 Sent: Monday, December 09, 2002 10:25 AM
 To: Thomas Connolly
 Subject: Re: Ethernet card problem

 On Dec 09, at 10:07 AM, Thomas Connolly wrote:
 
  Thanks very much for the quick reply.
  I would agree with that.  The model is a Kingston KNE100TX and it says
 that
  the driver is a dc(4).  Which Ethernet selection and I supposed to pick
 for
  that on Sysinstall?

 dc0, I would imagine.

  Is there a way to reconfigure it after installation.

 Oh, yes. Go on through the installation. Afterward, edit /etc/rc.conf to
 reflect reality. You'll have lines like these to change:
 hostname=sheol.localdomain
 ifconfig_ed0=inet 192.168.16.2 netmask 255.255.255.0
 What you'll change is the hostname (if need be), and ifconfig_ed0 to
 ifconfig_dc0. IIRC, that's all it takes.

  I
  apologize for the ignorance but I am very new to all this.  I basically
 just
  went step-by-step through the FreeBSD manual on installation.  There was
 no
  option that said dc(4).

 I don't remember how to specify the interface within sysinstall(8), but
I'm
 sure you can (make sure you've resolved conflicting interrupts first).
 I usually set up the network manually, after sysinstall(8), just to stay
in
 practice!

  Thanks again,
  Thomas P. Connolly
  Senior Development Engineer
  Colorado Engineering Experiment Station Inc.
  Phone: (970) 897-2711
  Fax: (970) 897-2710
  Email: [EMAIL PROTECTED]

 Need a telecommuting UNIX SysAdmin in Minnesota?
 Dave

 --
   __ __
   \__   \D. J. HAWKEY JR.   /   __/
  \/\ [EMAIL PROTECTED]/\/
   http://www.visi.com/~hawkeyd/


 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



RE: Ethernet card problem

2002-12-09 Thread Thomas Connolly
Yes, that is what I tried to do but my interface doesn't come up in the
list, only plip, and com 1 come up, not dc0.

Thanks,
Thomas Connolly

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Brian
Sent: Monday, December 09, 2002 10:45 AM
To: Thomas Connolly; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Ethernet card problem

isnt is /stand/sysinstall, post install config, network, pick yer interface,
answer yes to the dhcp popup, thats it?

BTW, if it asks you if you want to activate now, that typically will not get
you the new parameters on the interface, youll need to either ifconfig it
down and then up, or reboot as a quik dirty way.

Bri

- Original Message -
From: Thomas Connolly [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, December 09, 2002 9:36 AM
Subject: RE: Ethernet card problem


 Thanks again for the help.  Can you tell me how to set my interface up
 manually so that it will use DHCP for the ip and netmask, gateway, etc.?

 Thanks,

 Tom Connolly

 -Original Message-
 From: D J Hawkey Jr [mailto:[EMAIL PROTECTED]]
 Sent: Monday, December 09, 2002 10:25 AM
 To: Thomas Connolly
 Subject: Re: Ethernet card problem

 On Dec 09, at 10:07 AM, Thomas Connolly wrote:
 
  Thanks very much for the quick reply.
  I would agree with that.  The model is a Kingston KNE100TX and it says
 that
  the driver is a dc(4).  Which Ethernet selection and I supposed to pick
 for
  that on Sysinstall?

 dc0, I would imagine.

  Is there a way to reconfigure it after installation.

 Oh, yes. Go on through the installation. Afterward, edit /etc/rc.conf to
 reflect reality. You'll have lines like these to change:
 hostname=sheol.localdomain
 ifconfig_ed0=inet 192.168.16.2 netmask 255.255.255.0
 What you'll change is the hostname (if need be), and ifconfig_ed0 to
 ifconfig_dc0. IIRC, that's all it takes.

  I
  apologize for the ignorance but I am very new to all this.  I basically
 just
  went step-by-step through the FreeBSD manual on installation.  There was
 no
  option that said dc(4).

 I don't remember how to specify the interface within sysinstall(8), but
I'm
 sure you can (make sure you've resolved conflicting interrupts first).
 I usually set up the network manually, after sysinstall(8), just to stay
in
 practice!

  Thanks again,
  Thomas P. Connolly
  Senior Development Engineer
  Colorado Engineering Experiment Station Inc.
  Phone: (970) 897-2711
  Fax: (970) 897-2710
  Email: [EMAIL PROTECTED]

 Need a telecommuting UNIX SysAdmin in Minnesota?
 Dave

 --
   __ __
   \__   \D. J. HAWKEY JR.   /   __/
  \/\ [EMAIL PROTECTED]/\/
   http://www.visi.com/~hawkeyd/


 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: Ethernet card problem

2002-12-09 Thread Kevin D. Kinsey, DaleCo, S.P.
dc driver uses the miibus code, make sure you have that enabled
on your kernel.

There is nothing needed in sysinstall, a device probe ought to
catch it IF the miibus is enabled in your kernel config.

Sorry, I'm late on this discussion, if I've missed important
points, please forgiveI just hadn't seen this point
mentioned.

Kevin Kinsey
DaleCo, S.P.
- Original Message -
From: Thomas Connolly [EMAIL PROTECTED]
To: 'Brian' [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, December 09, 2002 11:50 AM
Subject: RE: Ethernet card problem


Yes, that is what I tried to do but my interface doesn't come up in
the
list, only plip, and com 1 come up, not dc0.

Thanks,
Thomas Connolly

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Brian
Sent: Monday, December 09, 2002 10:45 AM
To: Thomas Connolly; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Ethernet card problem

isnt is /stand/sysinstall, post install config, network, pick yer
interface,
answer yes to the dhcp popup, thats it?

BTW, if it asks you if you want to activate now, that typically will
not get
you the new parameters on the interface, youll need to either
ifconfig it
down and then up, or reboot as a quik dirty way.

Bri

- Original Message -
From: Thomas Connolly [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, December 09, 2002 9:36 AM
Subject: RE: Ethernet card problem


 Thanks again for the help.  Can you tell me how to set my interface
up
 manually so that it will use DHCP for the ip and netmask, gateway,
etc.?

 Thanks,

 Tom Connolly

 -Original Message-
 From: D J Hawkey Jr [mailto:[EMAIL PROTECTED]]
 Sent: Monday, December 09, 2002 10:25 AM
 To: Thomas Connolly
 Subject: Re: Ethernet card problem

 On Dec 09, at 10:07 AM, Thomas Connolly wrote:
 
  Thanks very much for the quick reply.
  I would agree with that.  The model is a Kingston KNE100TX and it
says
 that
  the driver is a dc(4).  Which Ethernet selection and I supposed
to pick
 for
  that on Sysinstall?

 dc0, I would imagine.

  Is there a way to reconfigure it after installation.

 Oh, yes. Go on through the installation. Afterward, edit
/etc/rc.conf to
 reflect reality. You'll have lines like these to change:
 hostname=sheol.localdomain
 ifconfig_ed0=inet 192.168.16.2 netmask 255.255.255.0
 What you'll change is the hostname (if need be), and ifconfig_ed0
to
 ifconfig_dc0. IIRC, that's all it takes.

  I
  apologize for the ignorance but I am very new to all this.  I
basically
 just
  went step-by-step through the FreeBSD manual on installation.
There was
 no
  option that said dc(4).

 I don't remember how to specify the interface within sysinstall(8),
but
I'm
 sure you can (make sure you've resolved conflicting interrupts
first).
 I usually set up the network manually, after sysinstall(8), just to
stay
in
 practice!

  Thanks again,
  Thomas P. Connolly
  Senior Development Engineer
  Colorado Engineering Experiment Station Inc.
  Phone: (970) 897-2711
  Fax: (970) 897-2710
  Email: [EMAIL PROTECTED]

 Need a telecommuting UNIX SysAdmin in Minnesota?
 Dave

 --
   __
__
   \__   \D. J. HAWKEY JR.   /
__/
  \/\ [EMAIL PROTECTED]
/\/
   http://www.visi.com/~hawkeyd/


 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



RE: Ethernet card problem

2002-12-09 Thread Thomas Connolly
Thanks for the advice but again, I am very new to all this.  Can you tell me
how to check if miibus is enabled and how to enable it if it is not?

Thanks in advance,

Tom Connolly

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Kevin D. Kinsey,
DaleCo, S.P.
Sent: Monday, December 09, 2002 2:07 PM
To: Thomas Connolly; 'Brian'; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Ethernet card problem

dc driver uses the miibus code, make sure you have that enabled
on your kernel.

There is nothing needed in sysinstall, a device probe ought to
catch it IF the miibus is enabled in your kernel config.

Sorry, I'm late on this discussion, if I've missed important
points, please forgiveI just hadn't seen this point
mentioned.

Kevin Kinsey
DaleCo, S.P.
- Original Message -
From: Thomas Connolly [EMAIL PROTECTED]
To: 'Brian' [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, December 09, 2002 11:50 AM
Subject: RE: Ethernet card problem


Yes, that is what I tried to do but my interface doesn't come up in
the
list, only plip, and com 1 come up, not dc0.

Thanks,
Thomas Connolly

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Brian
Sent: Monday, December 09, 2002 10:45 AM
To: Thomas Connolly; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Ethernet card problem

isnt is /stand/sysinstall, post install config, network, pick yer
interface,
answer yes to the dhcp popup, thats it?

BTW, if it asks you if you want to activate now, that typically will
not get
you the new parameters on the interface, youll need to either
ifconfig it
down and then up, or reboot as a quik dirty way.

Bri

- Original Message -
From: Thomas Connolly [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, December 09, 2002 9:36 AM
Subject: RE: Ethernet card problem


 Thanks again for the help.  Can you tell me how to set my interface
up
 manually so that it will use DHCP for the ip and netmask, gateway,
etc.?

 Thanks,

 Tom Connolly

 -Original Message-
 From: D J Hawkey Jr [mailto:[EMAIL PROTECTED]]
 Sent: Monday, December 09, 2002 10:25 AM
 To: Thomas Connolly
 Subject: Re: Ethernet card problem

 On Dec 09, at 10:07 AM, Thomas Connolly wrote:
 
  Thanks very much for the quick reply.
  I would agree with that.  The model is a Kingston KNE100TX and it
says
 that
  the driver is a dc(4).  Which Ethernet selection and I supposed
to pick
 for
  that on Sysinstall?

 dc0, I would imagine.

  Is there a way to reconfigure it after installation.

 Oh, yes. Go on through the installation. Afterward, edit
/etc/rc.conf to
 reflect reality. You'll have lines like these to change:
 hostname=sheol.localdomain
 ifconfig_ed0=inet 192.168.16.2 netmask 255.255.255.0
 What you'll change is the hostname (if need be), and ifconfig_ed0
to
 ifconfig_dc0. IIRC, that's all it takes.

  I
  apologize for the ignorance but I am very new to all this.  I
basically
 just
  went step-by-step through the FreeBSD manual on installation.
There was
 no
  option that said dc(4).

 I don't remember how to specify the interface within sysinstall(8),
but
I'm
 sure you can (make sure you've resolved conflicting interrupts
first).
 I usually set up the network manually, after sysinstall(8), just to
stay
in
 practice!

  Thanks again,
  Thomas P. Connolly
  Senior Development Engineer
  Colorado Engineering Experiment Station Inc.
  Phone: (970) 897-2711
  Fax: (970) 897-2710
  Email: [EMAIL PROTECTED]

 Need a telecommuting UNIX SysAdmin in Minnesota?
 Dave

 --
   __
__
   \__   \D. J. HAWKEY JR.   /
__/
  \/\ [EMAIL PROTECTED]
/\/
   http://www.visi.com/~hawkeyd/


 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



RE: Ethernet card problem

2002-12-09 Thread Thomas Connolly
Oh yes, and one other thing, can you tell me how to do a device probe?

Thanks again,

Tom Connolly
 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Kevin D. Kinsey,
DaleCo, S.P.
Sent: Monday, December 09, 2002 2:07 PM
To: Thomas Connolly; 'Brian'; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Ethernet card problem

dc driver uses the miibus code, make sure you have that enabled
on your kernel.

There is nothing needed in sysinstall, a device probe ought to
catch it IF the miibus is enabled in your kernel config.

Sorry, I'm late on this discussion, if I've missed important
points, please forgiveI just hadn't seen this point
mentioned.

Kevin Kinsey
DaleCo, S.P.
- Original Message -
From: Thomas Connolly [EMAIL PROTECTED]
To: 'Brian' [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, December 09, 2002 11:50 AM
Subject: RE: Ethernet card problem


Yes, that is what I tried to do but my interface doesn't come up in
the
list, only plip, and com 1 come up, not dc0.

Thanks,
Thomas Connolly

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Brian
Sent: Monday, December 09, 2002 10:45 AM
To: Thomas Connolly; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Ethernet card problem

isnt is /stand/sysinstall, post install config, network, pick yer
interface,
answer yes to the dhcp popup, thats it?

BTW, if it asks you if you want to activate now, that typically will
not get
you the new parameters on the interface, youll need to either
ifconfig it
down and then up, or reboot as a quik dirty way.

Bri

- Original Message -
From: Thomas Connolly [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, December 09, 2002 9:36 AM
Subject: RE: Ethernet card problem


 Thanks again for the help.  Can you tell me how to set my interface
up
 manually so that it will use DHCP for the ip and netmask, gateway,
etc.?

 Thanks,

 Tom Connolly

 -Original Message-
 From: D J Hawkey Jr [mailto:[EMAIL PROTECTED]]
 Sent: Monday, December 09, 2002 10:25 AM
 To: Thomas Connolly
 Subject: Re: Ethernet card problem

 On Dec 09, at 10:07 AM, Thomas Connolly wrote:
 
  Thanks very much for the quick reply.
  I would agree with that.  The model is a Kingston KNE100TX and it
says
 that
  the driver is a dc(4).  Which Ethernet selection and I supposed
to pick
 for
  that on Sysinstall?

 dc0, I would imagine.

  Is there a way to reconfigure it after installation.

 Oh, yes. Go on through the installation. Afterward, edit
/etc/rc.conf to
 reflect reality. You'll have lines like these to change:
 hostname=sheol.localdomain
 ifconfig_ed0=inet 192.168.16.2 netmask 255.255.255.0
 What you'll change is the hostname (if need be), and ifconfig_ed0
to
 ifconfig_dc0. IIRC, that's all it takes.

  I
  apologize for the ignorance but I am very new to all this.  I
basically
 just
  went step-by-step through the FreeBSD manual on installation.
There was
 no
  option that said dc(4).

 I don't remember how to specify the interface within sysinstall(8),
but
I'm
 sure you can (make sure you've resolved conflicting interrupts
first).
 I usually set up the network manually, after sysinstall(8), just to
stay
in
 practice!

  Thanks again,
  Thomas P. Connolly
  Senior Development Engineer
  Colorado Engineering Experiment Station Inc.
  Phone: (970) 897-2711
  Fax: (970) 897-2710
  Email: [EMAIL PROTECTED]

 Need a telecommuting UNIX SysAdmin in Minnesota?
 Dave

 --
   __
__
   \__   \D. J. HAWKEY JR.   /
__/
  \/\ [EMAIL PROTECTED]
/\/
   http://www.visi.com/~hawkeyd/


 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: Ethernet card problem

2002-12-09 Thread D J Hawkey Jr
On Dec 09, at 03:07 PM, Kevin D. Kinsey, DaleCo, S.P. wrote:
 
 dc driver uses the miibus code, make sure you have that enabled
 on your kernel.
 
 There is nothing needed in sysinstall, a device probe ought to
 catch it IF the miibus is enabled in your kernel config.

Um, he can't enable miibus in the kernel from sysinstall(8), can he?
I don't know that miibus is in the distribution kernel or not, if
/modules/miibus.ko is likewise available, nor if you can activate
modules from sysinstall(8).

I don't recall any difficulties with sysinstall(8) when I brought
up this box with Linksys NICs (Realtek chipsets, which also use dc(1)).

Otherwise, you point out that which I'd forgotten. Thanks.

 Sorry, I'm late on this discussion, if I've missed important
 points, please forgiveI just hadn't seen this point
 mentioned.

Forgive? Nonsense. You made the effort, that's what counts.

 Kevin Kinsey
 DaleCo, S.P.

Dave

-- 
  __ __
  \__   \D. J. HAWKEY JR.   /   __/
 \/\ [EMAIL PROTECTED]/\/
  http://www.visi.com/~hawkeyd/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



RE: Ethernet card problem

2002-12-09 Thread Jack L. Stone
At 02:19 PM 12.9.2002 -0700, Thomas Connolly wrote:
Thanks for the advice but again, I am very new to all this.  Can you tell me
how to check if miibus is enabled and how to enable it if it is not?

Thanks in advance,

Tom Connolly


Just edit your kernel config file with this line and recompile:
device  miibus  # MII bus support

Best regards,
Jack L. Stone,
Administrator

SageOne Net
http://www.sage-one.net
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: Ethernet card problem

2002-12-09 Thread D J Hawkey Jr
On Dec 09, at 03:51 PM, Jack L. Stone wrote:
 
 At 02:19 PM 12.9.2002 -0700, Thomas Connolly wrote:
 Thanks for the advice but again, I am very new to all this.  Can you tell me
 how to check if miibus is enabled and how to enable it if it is not?
 
 Thanks in advance,
 Tom Connolly
 
 Just edit your kernel config file with this line and recompile:
 device  miibus  # MII bus support

Again, this can only occur _after_ the initial sysinstall(8), right?

 Best regards,
 Jack L. Stone,

Dave

-- 
  __ __
  \__   \D. J. HAWKEY JR.   /   __/
 \/\ [EMAIL PROTECTED]/\/
  http://www.visi.com/~hawkeyd/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: Ethernet card problem

2002-12-09 Thread Kevin D. Kinsey, DaleCo, S.P.

- Original Message -
From: D J Hawkey Jr [EMAIL PROTECTED]
To: Jack L. Stone [EMAIL PROTECTED]
Cc: Thomas Connolly [EMAIL PROTECTED]; Kevin D. Kinsey,
DaleCo, S.P. [EMAIL PROTECTED]; 'Brian' [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Monday, December 09, 2002 3:57 PM
Subject: Re: Ethernet card problem


 On Dec 09, at 03:51 PM, Jack L. Stone wrote:
 
  At 02:19 PM 12.9.2002 -0700, Thomas Connolly wrote:
  Thanks for the advice but again, I am very new to all this.  Can
you tell me
  how to check if miibus is enabled and how to enable it if it is
not?
  
  Thanks in advance,
  Tom Connolly
 
  Just edit your kernel config file with this line and recompile:
  device  miibus  # MII bus support

 Again, this can only occur _after_ the initial sysinstall(8),
right?

  Best regards,
  Jack L. Stone,

 Dave

Guess so.  So, he's trying to do an FTP install, and it
won't recognize his NIC?

KDK


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: Ethernet card problem

2002-12-09 Thread Kevin D. Kinsey, DaleCo, S.P.
OK, he's got a Kingston (generally dc driver) and is trying
to do sysinstall and d-load over NIC.

IME it doesn't matter what you pick in the configuration
section of sysinstall --- whatever's first should work, because
those are just old nonPNP ISA NIC drivers.

After doing kernel configuration in full-screen visual/CLI/skip
then sysinstall does an initial device probe, and when you get
to configure interface, it should be there.

For the record, device miibus is enabled in -GENERIC kernel.

If his NIC is *not* there when it's time to configure and start
the d-load, it's a hardware/BIOS issue, or somebody's broke
sysinstall(8).or is there another option I'm missing?

Kevin Kinsey


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



RE: Ethernet card problem

2002-12-09 Thread Thomas Connolly
I actually installed from CD and won't recognize my NIC.  I selected the ed0
NIC from sysinstall because I wasn't sure what I was supposed to use for my
card (Kingston KNE100TX - dc(4)).  When I got to the configuration screen,
there was no Ethernet card listed.  I am confused on what to do next.  What
I'm haring is that I have to install miibus, then I have to edit
/etc/rc.conf.  Do I have that right?

Thanks again,

Thomas Connolly

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Kevin D. Kinsey,
DaleCo, S.P.
Sent: Monday, December 09, 2002 2:58 PM
To: [EMAIL PROTECTED]; Jack L. Stone
Cc: Thomas Connolly; 'Brian'; [EMAIL PROTECTED]
Subject: Re: Ethernet card problem


- Original Message -
From: D J Hawkey Jr [EMAIL PROTECTED]
To: Jack L. Stone [EMAIL PROTECTED]
Cc: Thomas Connolly [EMAIL PROTECTED]; Kevin D. Kinsey,
DaleCo, S.P. [EMAIL PROTECTED]; 'Brian' [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Monday, December 09, 2002 3:57 PM
Subject: Re: Ethernet card problem


 On Dec 09, at 03:51 PM, Jack L. Stone wrote:
 
  At 02:19 PM 12.9.2002 -0700, Thomas Connolly wrote:
  Thanks for the advice but again, I am very new to all this.  Can
you tell me
  how to check if miibus is enabled and how to enable it if it is
not?
  
  Thanks in advance,
  Tom Connolly
 
  Just edit your kernel config file with this line and recompile:
  device  miibus  # MII bus support

 Again, this can only occur _after_ the initial sysinstall(8),
right?

  Best regards,
  Jack L. Stone,

 Dave

Guess so.  So, he's trying to do an FTP install, and it
won't recognize his NIC?

KDK


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



RE: Ethernet card problem

2002-12-09 Thread Thomas Connolly

This is exactly my situation, any ideas??
If his NIC is *not* there when it's time to configure and start
the d-load, it's a hardware/BIOS issue, or somebody's broke
sysinstall(8).or is there another option I'm missing?

Tom

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Kevin D. Kinsey,
DaleCo, S.P.
Sent: Monday, December 09, 2002 3:05 PM
To: [EMAIL PROTECTED]; Jack L. Stone
Cc: [EMAIL PROTECTED]
Subject: Re: Ethernet card problem

OK, he's got a Kingston (generally dc driver) and is trying
to do sysinstall and d-load over NIC.

IME it doesn't matter what you pick in the configuration
section of sysinstall --- whatever's first should work, because
those are just old nonPNP ISA NIC drivers.

After doing kernel configuration in full-screen visual/CLI/skip
then sysinstall does an initial device probe, and when you get
to configure interface, it should be there.

For the record, device miibus is enabled in -GENERIC kernel.

If his NIC is *not* there when it's time to configure and start
the d-load, it's a hardware/BIOS issue, or somebody's broke
sysinstall(8).or is there another option I'm missing?

Kevin Kinsey


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: Ethernet card problem

2002-12-09 Thread Kevin D. Kinsey, DaleCo, S.P.
From: Thomas Connolly [EMAIL PROTECTED]
Sent: Monday, December 09, 2002 4:15 PM
Subject: RE: Ethernet card problem


 I actually installed from CD and won't recognize my NIC.  I
selected the ed0
 NIC from sysinstall because I wasn't sure what I was supposed to
use for my
 card (Kingston KNE100TX - dc(4)).  When I got to the configuration
screen,
 there was no Ethernet card listed.  I am confused on what to do
next.  What
 I'm haring is that I have to install miibus, then I have to edit
 /etc/rc.conf.  Do I have that right?

 Thanks again,

 Thomas Connolly

If you're using the GENERIC kernel, miibus should
already be enabled.  As to rc.conf, see below.

If you installed from CD, and therefore have a
working system, please post the output of:

$dmesg

If you're able, pipe it to a .txt file and attach
it, otherwise copy/paste to your email program.

$dmesg  attach.txt

That might show us if there is a problem at device
probe time.

It would be worth your time to look at /etc/rc.conf,
because it might be easy to spot if sysinstall actually
wrote the file using ed0 instead of dc0.  If so,
changing it would be a hurdle on our way to fixing
the issue.

You could also send us output from ifconfig -a,
but it sounds as if that's already been decided,
and dc0 isn't in there.

KDK


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



RE: Ethernet card problem

2002-12-09 Thread Brian
ah so then its not being detected, pci or isa card?  Id isa, perhaps
setting bios irq to isa legacy is necessary..

Bri


On Mon, 9 Dec 2002, Thomas Connolly wrote:

 Yes, that is what I tried to do but my interface doesn't come up in the
 list, only plip, and com 1 come up, not dc0.

 Thanks,
 Thomas Connolly

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]] On Behalf Of Brian
 Sent: Monday, December 09, 2002 10:45 AM
 To: Thomas Connolly; [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Subject: Re: Ethernet card problem

 isnt is /stand/sysinstall, post install config, network, pick yer interface,
 answer yes to the dhcp popup, thats it?

 BTW, if it asks you if you want to activate now, that typically will not get
 you the new parameters on the interface, youll need to either ifconfig it
 down and then up, or reboot as a quik dirty way.

 Bri

 - Original Message -
 From: Thomas Connolly [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Sent: Monday, December 09, 2002 9:36 AM
 Subject: RE: Ethernet card problem


  Thanks again for the help.  Can you tell me how to set my interface up
  manually so that it will use DHCP for the ip and netmask, gateway, etc.?
 
  Thanks,
 
  Tom Connolly
 
  -Original Message-
  From: D J Hawkey Jr [mailto:[EMAIL PROTECTED]]
  Sent: Monday, December 09, 2002 10:25 AM
  To: Thomas Connolly
  Subject: Re: Ethernet card problem
 
  On Dec 09, at 10:07 AM, Thomas Connolly wrote:
  
   Thanks very much for the quick reply.
   I would agree with that.  The model is a Kingston KNE100TX and it says
  that
   the driver is a dc(4).  Which Ethernet selection and I supposed to pick
  for
   that on Sysinstall?
 
  dc0, I would imagine.
 
   Is there a way to reconfigure it after installation.
 
  Oh, yes. Go on through the installation. Afterward, edit /etc/rc.conf to
  reflect reality. You'll have lines like these to change:
  hostname=sheol.localdomain
  ifconfig_ed0=inet 192.168.16.2 netmask 255.255.255.0
  What you'll change is the hostname (if need be), and ifconfig_ed0 to
  ifconfig_dc0. IIRC, that's all it takes.
 
   I
   apologize for the ignorance but I am very new to all this.  I basically
  just
   went step-by-step through the FreeBSD manual on installation.  There was
  no
   option that said dc(4).
 
  I don't remember how to specify the interface within sysinstall(8), but
 I'm
  sure you can (make sure you've resolved conflicting interrupts first).
  I usually set up the network manually, after sysinstall(8), just to stay
 in
  practice!
 
   Thanks again,
   Thomas P. Connolly
   Senior Development Engineer
   Colorado Engineering Experiment Station Inc.
   Phone: (970) 897-2711
   Fax: (970) 897-2710
   Email: [EMAIL PROTECTED]
 
  Need a telecommuting UNIX SysAdmin in Minnesota?
  Dave
 
  --
__ __
\__   \D. J. HAWKEY JR.   /   __/
   \/\ [EMAIL PROTECTED]/\/
http://www.visi.com/~hawkeyd/
 
 
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with unsubscribe freebsd-questions in the body of the message
 


 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



RE: Ethernet card problem

2002-12-09 Thread Thomas Connolly
It's a pci card.

Thomas P. Connolly
Senior Development Engineer
Colorado Engineering Experiment Station Inc.
Phone: (970) 897-2711
Fax: (970) 897-2710
Email: [EMAIL PROTECTED]
 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Brian
Sent: Monday, December 09, 2002 4:27 PM
To: Thomas Connolly
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Ethernet card problem

ah so then its not being detected, pci or isa card?  Id isa, perhaps
setting bios irq to isa legacy is necessary..

Bri


On Mon, 9 Dec 2002, Thomas Connolly wrote:

 Yes, that is what I tried to do but my interface doesn't come up in the
 list, only plip, and com 1 come up, not dc0.

 Thanks,
 Thomas Connolly

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]] On Behalf Of Brian
 Sent: Monday, December 09, 2002 10:45 AM
 To: Thomas Connolly; [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Subject: Re: Ethernet card problem

 isnt is /stand/sysinstall, post install config, network, pick yer
interface,
 answer yes to the dhcp popup, thats it?

 BTW, if it asks you if you want to activate now, that typically will not
get
 you the new parameters on the interface, youll need to either ifconfig it
 down and then up, or reboot as a quik dirty way.

 Bri

 - Original Message -
 From: Thomas Connolly [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Sent: Monday, December 09, 2002 9:36 AM
 Subject: RE: Ethernet card problem


  Thanks again for the help.  Can you tell me how to set my interface up
  manually so that it will use DHCP for the ip and netmask, gateway, etc.?
 
  Thanks,
 
  Tom Connolly
 
  -Original Message-
  From: D J Hawkey Jr [mailto:[EMAIL PROTECTED]]
  Sent: Monday, December 09, 2002 10:25 AM
  To: Thomas Connolly
  Subject: Re: Ethernet card problem
 
  On Dec 09, at 10:07 AM, Thomas Connolly wrote:
  
   Thanks very much for the quick reply.
   I would agree with that.  The model is a Kingston KNE100TX and it says
  that
   the driver is a dc(4).  Which Ethernet selection and I supposed to
pick
  for
   that on Sysinstall?
 
  dc0, I would imagine.
 
   Is there a way to reconfigure it after installation.
 
  Oh, yes. Go on through the installation. Afterward, edit /etc/rc.conf to
  reflect reality. You'll have lines like these to change:
  hostname=sheol.localdomain
  ifconfig_ed0=inet 192.168.16.2 netmask 255.255.255.0
  What you'll change is the hostname (if need be), and ifconfig_ed0 to
  ifconfig_dc0. IIRC, that's all it takes.
 
   I
   apologize for the ignorance but I am very new to all this.  I
basically
  just
   went step-by-step through the FreeBSD manual on installation.  There
was
  no
   option that said dc(4).
 
  I don't remember how to specify the interface within sysinstall(8), but
 I'm
  sure you can (make sure you've resolved conflicting interrupts first).
  I usually set up the network manually, after sysinstall(8), just to stay
 in
  practice!
 
   Thanks again,
   Thomas P. Connolly
   Senior Development Engineer
   Colorado Engineering Experiment Station Inc.
   Phone: (970) 897-2711
   Fax: (970) 897-2710
   Email: [EMAIL PROTECTED]
 
  Need a telecommuting UNIX SysAdmin in Minnesota?
  Dave
 
  --
__ __
\__   \D. J. HAWKEY JR.   /   __/
   \/\ [EMAIL PROTECTED]/\/
http://www.visi.com/~hawkeyd/
 
 
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with unsubscribe freebsd-questions in the body of the message
 


 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: Ethernet card problem

2002-12-09 Thread Cliff Sarginson
On Mon, Dec 09, 2002 at 04:30:28PM -0700, Thomas Connolly wrote:
 It's a pci card.
 
mega-snip

- miibus is in the generic, there are a dozen or so PCI cards that need
it, some very common ones at that.
- the dc driver works on one of my systems that needs it, both under
4.7-Stable and Current.
- If you have a PCI card you can delete/ignore all the cards mentioned
in sysinstall, they are all ISA cards.

Nobody has suggested a few simple things yet. Such as is the card
properly seated in it's slot, have you tried another PCI slot in the 
computer. Check the PCI settings in your BIOS for any reserved slots,
turn off plug and play. Or maybe the card is kapot ?

Good luck.

-- 
Regards
   Cliff Sarginson 
   The Netherlands

[ This mail has been checked as virus-free ]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



RE: Ethernet card problem

2002-12-09 Thread Mat Branyon
Make sure pnp operating system is disabled in your bios and pnp disabled
on your card, or maybe recompiling your kernel for pnp support...

--mat

On Mon, 2002-12-09 at 16:28, Thomas Connolly wrote:
 
 This is exactly my situation, any ideas??
 If his NIC is *not* there when it's time to configure and start
 the d-load, it's a hardware/BIOS issue, or somebody's broke
 sysinstall(8).or is there another option I'm missing?
 
 Tom
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]] On Behalf Of Kevin D. Kinsey,
 DaleCo, S.P.
 Sent: Monday, December 09, 2002 3:05 PM
 To: [EMAIL PROTECTED]; Jack L. Stone
 Cc: [EMAIL PROTECTED]
 Subject: Re: Ethernet card problem
 
 OK, he's got a Kingston (generally dc driver) and is trying
 to do sysinstall and d-load over NIC.
 
 IME it doesn't matter what you pick in the configuration
 section of sysinstall --- whatever's first should work, because
 those are just old nonPNP ISA NIC drivers.
 
 After doing kernel configuration in full-screen visual/CLI/skip
 then sysinstall does an initial device probe, and when you get
 to configure interface, it should be there.
 
 For the record, device miibus is enabled in -GENERIC kernel.
 
 If his NIC is *not* there when it's time to configure and start
 the d-load, it's a hardware/BIOS issue, or somebody's broke
 sysinstall(8).or is there another option I'm missing?
 
 Kevin Kinsey
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-questions in the body of the message
 




To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: Ethernet card problem

2002-12-09 Thread Kevin D. Kinsey, DaleCo, S.P.
Try setting the BIOS to OS TYPE:  non-PNP

Relevant lines from your dmesg:

dc0: Intel 21143 10/100BaseTX at device 13.0 on pci0
dc0: couldn't map ports/memory device_probe_and_attach: dc0 attach
returned 6

If you look down a ways, you'll also see that you're going to have
USB trouble
if we don't address this issue.

I'm still looking about a bit.  If we can get the NIC recognized,
then
fixing rc.conf should be easy...

HTH,

KDK

- Original Message -
From: Thomas Connolly [EMAIL PROTECTED]
To: Kevin D. Kinsey, DaleCo, S.P. [EMAIL PROTECTED]; Thomas
Connolly [EMAIL PROTECTED]; [EMAIL PROTECTED]; 'Jack L.
Stone' [EMAIL PROTECTED]
Cc: 'Brian' [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Monday, December 09, 2002 9:47 PM
Subject: RE: Ethernet card problem


 Kevin,
 Here is the files you asked me to post.  Again thanks everyone for
your
 continued support.  I will be looking forward to your reply.


 -Original Message-
 From: Kevin D. Kinsey, DaleCo, S.P. [mailto:[EMAIL PROTECTED]]
 Sent: Monday, December 09, 2002 3:23 PM
 To: Thomas Connolly; [EMAIL PROTECTED]; 'Jack L. Stone'
 Cc: 'Brian'; [EMAIL PROTECTED]
 Subject: Re: Ethernet card problem


 From: Thomas Connolly [EMAIL PROTECTED]
 Sent: Monday, December 09, 2002 4:15 PM
 Subject: RE: Ethernet card problem


  I actually installed from CD and won't recognize my NIC.  I
 selected the ed0
  NIC from sysinstall because I wasn't sure what I was supposed to
 use for my
  card (Kingston KNE100TX - dc(4)).  When I got to the
configuration
 screen,
  there was no Ethernet card listed.  I am confused on what to do
 next.  What
  I'm haring is that I have to install miibus, then I have to edit
  /etc/rc.conf.  Do I have that right?
 
  Thanks again,
 
  Thomas Connolly
 
 If you're using the GENERIC kernel, miibus should
 already be enabled.  As to rc.conf, see below.

 If you installed from CD, and therefore have a
 working system, please post the output of:

 $dmesg

 If you're able, pipe it to a .txt file and attach
 it, otherwise copy/paste to your email program.

 $dmesg  attach.txt

 That might show us if there is a problem at device
 probe time.

 It would be worth your time to look at /etc/rc.conf,
 because it might be easy to spot if sysinstall actually
 wrote the file using ed0 instead of dc0.  If so,
 changing it would be a hurdle on our way to fixing
 the issue.

 You could also send us output from ifconfig -a,
 but it sounds as if that's already been decided,
 and dc0 isn't in there.

 KDK





To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: Ethernet card problem

2002-12-09 Thread D J Hawkey Jr
On Dec 09, at 08:47 PM, Thomas Connolly wrote:
 
 In another thread, Thomas wrote:
   My NIC is a pci card.  Do I still have to mess with my BIOS?

My bad. I thought you wrote it was an ISA card, but that was Kevin,
making an observation: OK, he's got a Kingston (generally dc driver)
and is trying to do sysinstall and d-load over NIC. IME it doesn't
matter what you pick in the configuration section of sysinstall
whatever's first should work, because those are just old nonPNP ISA
NIC drivers.

I inferred that the NIC was ISA, where Kevin wrote that the driver
is ISA.

You might have to, yes. See below.

 Copyright (c) 1992-2002 The FreeBSD Project.
 Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
   The Regents of the University of California. All rights reserved.
 FreeBSD 4.7-RELEASE #0: Wed Oct  9 15:08:34 GMT 2002
 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
 Timecounter i8254  frequency 1193182 Hz
 CPU: Pentium II/Pentium II Xeon/Celeron (347.67-MHz 686-class CPU)
   Origin = GenuineIntel  Id = 0x651  Stepping = 1
   
Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR
 real memory  = 134217728 (131072K bytes)
 config di sn0
 config di lnc0
 config di ie0
 config di fe0
 config di cs0
 config di bt0
 config di aic0
 config di aha0
 config di adv0
 config q

OK, you disabled things with conflicting IRQs and other not-needed-here
stuff. Good.

 avail memory = 125435904 (122496K bytes)
 Preloaded elf kernel kernel at 0xc050f000.
 Preloaded userconfig_script /boot/kernel.conf at 0xc050f09c.
 Pentium Pro MTRR support enabled
 md0: Malloc disk
 Using $PIR table, 8 entries at 0xc00fdf40
 npx0: math processor on motherboard
 npx0: INT 16 interface
 pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard
 pci0: PCI bus on pcib0
 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0
 pci1: PCI bus on pcib1
 pci1: Matrox MGA G100 AGP graphics accelerator at 0.0 irq 9
 isab0: Intel 82371AB PCI to ISA bridge at device 4.0 on pci0
 isa0: ISA bus on isab0
 atapci0: Intel PIIX4 ATA33 controller port 0xfcf0-0xfcff at device 4.1 on pci0
 ata0: at 0x1f0 irq 14 on atapci0
 ata1: at 0x170 irq 15 on atapci0
 uhci0: Intel 82371AB/EB (PIIX4) USB controller at device 4.2 on pci0
 uhci0: Could not map ports
 device_probe_and_attach: uhci0 attach returned 6
 chip1: Intel 82371AB Power management controller port 0x2180-0x218f at device 4.3 
on pci0

I'm not sure what this should be, but I've seem chip1 entries occur
when there's hardware that the kernel isn't prepped for. ICH chipsets come
to mind, for instance.

This shouldn't be fatal, and probably isn't related to your NIC.

 dc0: Intel 21143 10/100BaseTX at device 13.0 on pci0
 dc0: couldn't map ports/memory
 device_probe_and_attach: dc0 attach returned 6

There's your dc(4) driver trying to initialize. I don't know what the
6 return value specifically is, but it can't set up its I/O. This
leads me to believe that yes, you may have to twiddle ISA/PnP settings
in your BIOS.

In BIOS, you should be able to zero in on the PCI bus stuff easily enough.
Within that, several slot options. I can't tell you specifically what to
look for or change though; different BIOSes use different words and phrases
to describe the same things. A shot in the dark: Disable Plug-n-Play.

Best I can offer. G'Luck, and don't give up yet.
Dave

-- 
  __ __
  \__   \D. J. HAWKEY JR.   /   __/
 \/\ [EMAIL PROTECTED]/\/
  http://www.visi.com/~hawkeyd/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: Ethernet card problem

2002-12-09 Thread Igor B. Bykhalo
 From: D J Hawkey Jr [EMAIL PROTECTED]
 To: Thomas Connolly [EMAIL PROTECTED]
 Cc: Kevin D. Kinsey, DaleCo, S.P. [EMAIL PROTECTED]; Jack L. Stone 
[EMAIL PROTECTED]; 'Brian' [EMAIL PROTECTED];
[EMAIL PROTECTED]
 Sent: Tuesday, December 10, 2002 8:35 AM
 Subject: Re: Ethernet card problem


 On Dec 09, at 08:47 PM, Thomas Connolly wrote:
 
  In another thread, Thomas wrote:
My NIC is a pci card.  Do I still have to mess with my BIOS?
[...]
  pci1: Matrox MGA G100 AGP graphics accelerator at 0.0 irq 9
 I'd say this is not very good ^

[...]
  uhci0: Intel 82371AB/EB (PIIX4) USB controller at device 4.2 on pci0
  uhci0: Could not map ports
  device_probe_and_attach: uhci0 attach returned 6
  chip1: Intel 82371AB Power management controller port 0x2180-0x218f at device 
4.3 on pci0
[...]

  dc0: Intel 21143 10/100BaseTX at device 13.0 on pci0
  dc0: couldn't map ports/memory
  device_probe_and_attach: dc0 attach returned 6
[...]
Looks like there's still some conflict (irq?)

 In BIOS, you should be able to zero in on the PCI bus stuff easily enough.
 Within that, several slot options. I can't tell you specifically what to
 look for or change though; different BIOSes use different words and phrases
 to describe the same things. A shot in the dark: Disable Plug-n-Play.

One more shot-in-the-dark: In the BIOS near PnP OS: Yes/No
(Choose No, as others said)
you'll see the line something like Reset configuration (data)
Make it Yes, and exit from BIOS with Save, then BIOS will be forced
to reassign PnP/PCI resources for your hardware.

This helped me a number of times.

Oh, and when you boot off CD first time, you can select Visual
config. Delete here _everyting_ you are sure you don't need
(or have). This will simplify device probing a little.

HTH,
Igor


 Best I can offer. G'Luck, and don't give up yet.
 Dave


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message