Solaris / OpenSolarisThis forum is for the discussion of Solaris, OpenSolaris, OpenIndiana, and illumos.
General Sun, SunOS and Sparc related questions also go here. Any Solaris fork or distribution is welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
13. I tried to ping other machine, it works perfectly...
14. I applied this command:
#touch /reconfigure
15. up to this point, I am able to continue installing applications, accessing network, etc.
But after I rebooted my PC, the system unable to recognize the NIC. And when I do
#prtconf
it displays :
pci1186,1300 (driver not attached)
And I have to redo all the steps above again....
Could someone help me on this matter? I am quite frustrated on this (I've done it 3x...).
FYI, this is my first Solaris installation. Previously I already installed other UNIX-like system (Linux, FreeBSD, Mac OSX) without encountering this problem.
Originally posted by keefaz Try :
touch /reconfigure
sys-unconfig
Thanks for the suggestion... but it seems that it is still the same...
When I did sys-unconfig, the system tried to detect my NIC as "rtls0", which is incorrect. Everytime I reconfigure the DLink NIC manually, the system always referred it as "rf1". Why the system can't recognize "rf1" but tried to use "rtls0" instead?
I've been thinking.... at the step where the Configuration Assistant read my floppy where the driver for the DLink NIC resides, does the system copied the driver to the harddrive or only read it from the floppy?
Is there any way to copy the driver to the harddrive manually and let Solaris read it when booting?
Distribution: Solaris 11.4, Oracle Linux, Mint, Debian/WSL
Posts: 9,789
Rep:
Quote:
I downloaded the driver for this NIC
Where did you get the driver ?
Any installation notes there ?
Is it tested with Solaris 10 ?
Which release of Solaris 10 are you using ?
Quote:
# ifconfig rf1 plumb
10. then I configure the IP address:
#ifconfig rf1 10.8.9.98 netmask 255.255.255.0 broadcast 10.8.9.255
11. The next step is to bring up the rf1:
#ifconfig rf1 up
This can be shorten to:
Code:
ifconfig rf1 plumb 10.8.9.98 netmask 255.255.255.0 broadcast 10.8.9.255 up
Why is you driver rf1, is there a rf0 ?
Have you more than one ethernet interface ?
Quote:
When I did sys-unconfig, the system tried to detect my NIC as "rtls0", which is incorrect.
What makes you think this is incorrect ?
Solaris 10 already includes a realtek driver named rtls, perhaps the driver you installed is conflicting with the builtin one.
Why is you driver rf1, is there a rf0 ? Have you more than one ethernet interface ?
No, I only have 1 NIC installed
What makes you think this is incorrect ? Solaris 10 already includes a realtek driver named rtls, perhaps the driver you installed is conflicting with the builtin one.
Before I use the driver which I downloaded, the system didn't recognize the NIC... actually I tried rtls0, but nothing... Btw, even the NIC light was off.
Distribution: Solaris 11.4, Oracle Linux, Mint, Debian/WSL
Posts: 9,789
Rep:
There's definitely two drivers competing to handle your NIC, rf which is an open source driver from Masayuki Murayama and rtls which is the official driver from RealTek.
Some suggestions:
- Check if your card is known (and known once) to the driver's alias file /etc/driver_aliases:
Code:
grep "pci1186,1300" /etc/driver_aliases
- if more than one line shows up, remove all but the one you want to try with an text editor. (make a backup copy of /etc/driver_aliases as any mistake may make your system hang on reboot).
- You can tell the O/S to load a specific driver without rebooting, e.g.:
Code:
update_drv -a -i '"pci1186,1300"' rtls
- Check if the driver specific configuration file is there:
/usr/kernel/drv/<drivername>.conf (e.g. rf.conf or rtls.conf)
- If you have a modem card, try removing it (it may be the one picking rf0).
I experienced a similiar issue with an .itu .. TBH I never did find out how to make .itu permanent. But here is an alternate solution
Fire up you're editor; open /boot/solaris/devicedb/master; go down to the following entry:
pci10ec,8139 pci10ec,8139 net pci none "Realtek 8139 Fast Ethernet"
Copy that line directly below itself, changing the pci10ec,8139
portion to this :
pci1186,1300
Don't put that editor away yet ...Next edit /etc/driver_aliases
rtls "pci1186,1300"
Then proceed with your reconfigure.
Note: You will see a note that the driver does not support ...etc. @ boot. It does, I haven't figured out why that message occurs, but rest assured, the card will work.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.