Bernd Schemmer wrote:
Hi,

Solaris snv_110 does not like my 3Com Etherlink PCMCIA card anymore:

$ uname -a
SunOS sol10 5.11 snv_110 i86pc i386 i86pc
[r...@sol10 Sat Apr 11 19:11:25 ~ ]

in /var/adm/messages I can see this messages:

Apr 9 15:59:04 sol10 pcelx: [ID 157528 kern.info] pcelx0 (@0x0): 3COM EtherLink 10/100 (PCMCIA): ether (10baseT) 0:a0:24:ac:a5:c5 Apr 9 15:59:04 sol10 pcmcia: [ID 580848 kern.info] pcelx0 at p...@9 in socket 0 Apr 9 15:59:04 sol10 genunix: [ID 936769 kern.info] pcelx0 is /p...@0,0/pci1002,4...@14,4/pci1025,7...@9/netw...@0 Apr 9 15:59:04 sol10 softmac: [ID 226523 kern.warning] WARNING: pcelx0 has more than 2 minor nodes; unsupported Apr 9 15:59:04 sol10 net_dacf: [ID 730773 kern.warning] WARNING: net_postattach: cannot create softmac for device pcelx0 (48) Apr 9 15:59:04 sol10 softmac: [ID 226523 kern.warning] WARNING: pcelx0 has more than 2 minor nodes; unsupported Apr 9 15:59:04 sol10 net_dacf: [ID 730773 kern.warning] WARNING: net_postattach: cannot create softmac for device pcelx0 (48) Apr 9 15:59:04 sol10 softmac: [ID 226523 kern.warning] WARNING: pcelx0 has more than 2 minor nodes; unsupported Apr 9 15:59:04 sol10 net_dacf: [ID 730773 kern.warning] WARNING: net_postattach: cannot create softmac for device pcelx0 (48) Apr 9 15:59:04 sol10 genunix: [ID 667643 kern.warning] WARNING: Postattach failed for pcelx0

What I found out until now is that there are multiple entries for the pcelx in /etc/minor_perm:

[r...@sol10 Sat Apr 11 19:11:07 ~ ]
$ grep  pcelx /etc/minor_perm
clone:pcelx 0666 root sys
pcelx:* 0666 root sys
pcelx:* 0666 root sys

But I don't know if that is a problem.

How can I get this card to work in Solaris snv110 ? It did work with an earlier release of Solaris.

prtconf -vp would be more helpful.

We really should have an open source GLDv3 version of the pcelx driver... I haven't had time to look at it, and I no longer have the necessary 3com hardware....

   -- Garrett



regards

Bernd


_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to