Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 438
  • Last Modified:

problems with HME NIC on solars 8 and 9

i have an ultra 10 with open boot 3.25. i was running SUSE 7.3 for sparc. i recently purchashed a sunpci  card and chose to wipe the sytem clean in favor of solaris.

the problem :
when runnig solaris 8 or 9 the hme nic does not function nor do any indicator lights on the hub indicate a connection.

same system but when running linux, the nic works fine. hub lights indicate a connection.

i have used the ndd command here is what info it gives :

link_status = 1 (up)
link_mode = 0 (half duplex)
link_speed = 0 (10 mbp/s)
transceiver_inuse = 0 (external \onboard nic)

the nick responds to loopback pings but i cannot ping out to any thing. this was set up for a test  network. the machines ip info
ip = 192.168.1.3
mask = 255.255.255.0
gate = 192.168.1.1

the cable has been tested with a cable tester and on other pc's with no issues. other machine are able to reach the router/gateway.

how do i get this nic to work under solaris ?
0
buddajah
Asked:
buddajah
  • 6
  • 6
  • 2
  • +3
1 Solution
 
shivsaCommented:
If the NIC was working right for linux and not working for solaris.it may be because of bad network setup.

1. add default router.
create a file called /etc/defaultrouter if it is not there and add the router ip address to it. if it is there check for the router value.

2.  ireconfig network.
ifconfig hme0 unplumb
ifconfig hme0 plumb
ifconfig hme0 inet 192.168.1.3 netmask 255.255.255.0 broadcast x.x.x.x  ( fill in the correct braodcast address).
ifconfig hme0 up

at the same time check #dmesg if any unusual message show up.

3. try to run sys-unconfig and reset all the settings for this NIC card.

0
 
shivsaCommented:
if those does not work please check the setting  on obp for local-mac-address true.
ok printenv and check for local-mac-address.
0
 
jlevieCommented:
Is this system connected to a 10MBps only hub or switch or a 10/100MBps hub or switch?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
buddajahAuthor Commented:
during the setup i asked for the system ip info and i gave it :
ip = 192.168.1.3 - pc w/issue
mask = 255.255.255.0
gate = 192.168.1.1 - linksys router w/4 port hub - connected to cable modem.

i will try your suggestion after class and keep u posted. thank you
0
 
durindilCommented:
Just fyi, you can also use:

     ifconfig hme0 192.168.1.3  netmask + broadcast + up

     and the "+" assigns the defaults based on the class of the first octet.  You must also put these configurations in your network script files to make them persistent across reboots

For your network setup, as shivsa said, you do need to assign your default gateway by using:

     route add default 192.168.1.1

and add that in your /etc/defaultrouter to make it persistent.  

     192.168.1.1

Change your /etc/nsswitch.conf by copying the /etc/nsswitch.dns file over /etc/nsswitch.conf file

the hosts line should read:

     hosts    dns  files

Add your DNS servers (from your cable company, ISP, etc.) into the /etc/resolv.conf file:

     nameserver x.x.x.x
     nameserver x.x.x.x
0
 
buddajahAuthor Commented:

1. add default router. this setting is correct

2.  ifconfig network. - this did not help

3.try to run sys-unconfig and reset all the settings for this NIC card.
 - this ran the ip set up for the system again - it is now the same as it was before

4. check the setting  on obp for local-mac-address true. - the led's on the router come on in tne embeded system mode and during the diag mode or watch-net - sometimes it appears as if the system lock up though ?

5. /etc/nsswitch.dns and /etc/nsswitch.conf file are the same. now and after sys-unconfig.

6. Add your DNS servers (from your cable company, ISP, etc.) into the /etc/resolv.conf file:
 they were already there and are correct

now what ?
0
 
jlevieCommented:
My guess would be that something is non-standard w/respect to link negotiation on the hub that this system connects to. It might be possible to work around that by forcing the link mode in /etc/system. To do that you have to know whether this is a swithc or a hub and whether it is a 10Mbps or 10/100MBps device.
0
 
buddajahAuthor Commented:
here is the link on the link on the router/switch:
http://www.linksys.com/products/product.asp?grid=34&scid=29&prid=561
ftp://ftp.linksys.com/datasheet/befsr41v3_ds.pdf

it supports tcp/ip, netbeui, and ipx/spx protocols and only supports windows OS's but i have been running linix on s machines forover 2 years with no issues.

it is a small home router with a built in swicht. i have had it for 2-3 years now.  i was even using it on tne ultra 10 when it had linux on and had no issues.i believe it to be 10/100 auto-sensing

what do i have to do to force this to work?
0
 
buddajahAuthor Commented:
well at this pint it looks no one has any answers. i am putting linux back on. the only thing i think it could be at this point is an EPROM issue. thanks for the help any ways.
0
 
shivsaCommented:
could u check your sbus-probe-list to e0123.
and diag-switch to true.

and see how it goes.
i am not sure at this what is the problem, but i'm just shooting in dark.
0
 
shivsaCommented:
also do u see NIC in show-net output.
u can also test the NIC with
test-net <device-name for NIC>

0
 
shivsaCommented:
test net or "watch-net-all from ok prompt.

also set these into /etc/system
set hme:hme_adv_100fdx_cap=1
set hme:hme_adv_100hdx_cap=0
set hme:hme_adv_autoneg_cap=0

and reboot the system.
0
 
shivsaCommented:
also set these too.

set hme:hme_adv_100T4_cap=0
set hme:hme_adv_10fdx_cap=0
set hme:hme_adv_10hdx_cap=0

and check the output of netstat -in.

thanks,
Shiv
0
 
Hanno P.S.IT Consultant and Infrastructure ArchitectCommented:
To reset you EEPROM settings do

ok set-defaults

NOw, the Solaris install should go smoothly :-)
0
 
buddajahAuthor Commented:


" could u check your sbus-probe-list to e0123.
and diag-switch to true."
     this system is pci based. (unless i am misundertanding you)

" also do u see NIC in show-net output.
u can also test the NIC with
test-net <device-name for NIC>"
      when i did this the embedded sytem locks up. i need to actually reload the eprom chip to fix it. for now linux is working like a charm.

0
 
buddajahAuthor Commented:
well reloading the eprom fixed. apparently the version of suse linux i had on it over/rewrote part of the eprom for what it needed. i want to thank everyone for their adive and help when i posted this.
0
 
moduloCommented:
PAQed, with points refunded (125)

modulo
Community Support Moderator
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 6
  • 6
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now