tag:blogger.com,1999:blog-6730844193902134967.post4351659632352233284..comments2023-09-05T06:23:22.100-07:00Comments on E O N: Another way to add driver(s) to EONAndre Luehttp://www.blogger.com/profile/06886037020375947489noreply@blogger.comBlogger13125tag:blogger.com,1999:blog-6730844193902134967.post-4549358801780862362009-12-29T08:36:35.026-08:002009-12-29T08:36:35.026-08:00Hi,
I have a problem to add a driver for my NIC SU...Hi,<br />I have a problem to add a driver for my NIC SUNWurtw<br />I extracted the driver from /Solaris_11/Product/SUNWurtw/archive/none.7z and copy it to /kernel/drv using the same OpenSolaris version 129<br />I updated the /etc/name_to_major with unique id urtw 82<br />When I tried to add the driver ,I received the following error message :<br />#add_drv -v urtw<br />exit status = 0<br />devfsadm: driver failed to attach: urtw<br />exit status = 1<br />Warning: Driver (urtw) successfully added to system but failed to attach<br />Driver (urtw) installed.<br /><br />I run the following command truss -fae -vall -o /tmp/foo<br /><br />I posted the contents of /tmp/foo to http://pastebin.com/m220c985<br /><br />ThanksUnknownhttps://www.blogger.com/profile/04533900234817585147noreply@blogger.comtag:blogger.com,1999:blog-6730844193902134967.post-89588707529216104742009-08-02T17:23:02.493-07:002009-08-02T17:23:02.493-07:00Andre,
Turns out the miniroot got packaged by Sun ...Andre,<br />Turns out the miniroot got packaged by Sun with a lock file in the /tmp folder...<br /><br />Thanks!Josephhttps://www.blogger.com/profile/08403672385087802408noreply@blogger.comtag:blogger.com,1999:blog-6730844193902134967.post-62276390092786655352009-07-26T11:18:38.621-07:002009-07-26T11:18:38.621-07:00More info would be needed. You can try adding trus...More info would be needed. You can try adding truss -fae -vall -o /tmp/foo in front of your add_drv cmd and posting the contents of /tmp/foo to the opensolaris forum and asking for help. You can also post back a link and I'll take a look.Andre Luehttps://www.blogger.com/profile/06886037020375947489noreply@blogger.comtag:blogger.com,1999:blog-6730844193902134967.post-44841070441291327732009-07-06T19:57:23.538-07:002009-07-06T19:57:23.538-07:00Andre,
I was searching the net to troubleshoot the...Andre,<br />I was searching the net to troubleshoot the "add_drv/rem_drv currently busy; try later" I get when adding or removing a driver from an unpacked miniroot in Sol 10u7 and came across your site. Do you happen to have any idea whats going wrong?<br /><br />Thanks!Josephhttps://www.blogger.com/profile/08403672385087802408noreply@blogger.comtag:blogger.com,1999:blog-6730844193902134967.post-33264087351825846682009-06-20T12:49:33.694-07:002009-06-20T12:49:33.694-07:00GleNN,
I know you have this resolved but for othe...GleNN,<br /><br />I know you have this resolved but for others. The drivers on the DVD are structured as follows (SUNWrge for this example)<br />/Solaris_11/Product/SUNWrge/archive/none.7z<br /><br />This file can be unpacked with 7-zip<br />http://www.7-zip.org/<br />or on a uniz box that has 7z<br />7z e -o/tmp none.7z<br />cpio -idumBv < /tmp/none<br /><br />Move the driver into /kernel/drv/ and kernel/drv/amd64 for 64-bit, thhen edit /etc/name_to_major with the next unique number ex:<br />rge 62 (where 62 is the next unique number)Andre Luehttps://www.blogger.com/profile/06886037020375947489noreply@blogger.comtag:blogger.com,1999:blog-6730844193902134967.post-25492260989281916852009-06-09T13:54:58.051-07:002009-06-09T13:54:58.051-07:00Hello again!
I was able to add the rge driver on ...Hello again!<br /><br />I was able to add the rge driver on eon snv_114 with pkgadd on opensolaris using snv_114 sxce dvd. The problem I'm experiencing now is that the driver won't load on start up. As I've read from above posts, to check /etc/name_to_major. rge is there, with a number 61 to it. Although, the line before it was 59. I looked around the file, it seems the number is all over the place and I found 60 preceded by fssnap. So I didn't bother changing rge to 60. I can use the driver by adding the proper commands on .exec file but Apache2 is failing at start up due to no IPv4 service available at bootup. Any help?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6730844193902134967.post-8600608022202705492009-06-08T09:38:14.897-07:002009-06-08T09:38:14.897-07:00Hi, I'm new with Solaris and with EON at that....Hi, I'm new with Solaris and with EON at that. I'm using EON, of course as a basic Fileserver. EON has been working great, but I've been trying to figure out how to add the driver SUNWrge. I am no developer, just a basic end user with enough knowledge to install a system, but not exactly modify and maintain it. It's working fine now with an rtls driver, although it'd be great if I can get the GigE NIC working. First, I'm not exactly sure where to look for the binary for the driver. I downloaded snv_114 SXCE and looked around there but all I could fine was a "none" package in the products directory. I've tried google, unfortunately with no help. I'm working on making my own ISO image, but if there's any quicker way, I'd appreciate your help. Thanks.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6730844193902134967.post-76615561143002690142009-05-01T11:12:00.000-07:002009-05-01T11:12:00.000-07:00Thanks Andre,
Finally I got network working! :)
...Thanks Andre,<br /><br />Finally I got network working! :)<br /><br />There is output from the command you asked for:<br />http://pastebin.com/m113d2510<br />http://pastebin.com/m178db44d<br /><br />You said it's to solve some multi core issue, but not that my cpu is single core.scfhttps://www.blogger.com/profile/09047290969220688690noreply@blogger.comtag:blogger.com,1999:blog-6730844193902134967.post-54294303766445328852009-04-30T21:52:00.000-07:002009-04-30T21:52:00.000-07:00scf,
I think it's because sfe is not in /etc/name...scf,<br /><br />I think it's because sfe is not in /etc/name_to_major<br />try adding it to the last line and incrementing the number.<br />ie if the last line is<br />rtls 52<br />edit to<br />rtls 52<br />sfe 53<br /><br />Also, can you do me a favor. I'm trying to squash a multi-core bug<br />can you do a pastebin of output and /tmp/foo from this cmd<br />truss -fae -vall -o /tmp/foo psrinfo -v<br /><br />thanksAndre Luehttps://www.blogger.com/profile/06886037020375947489noreply@blogger.comtag:blogger.com,1999:blog-6730844193902134967.post-3050232511214592642009-04-29T11:27:00.000-07:002009-04-29T11:27:00.000-07:00There is a log file http://pastebin.com/m600400ee
...There is a log file http://pastebin.com/m600400ee<br /><br />The entries about sfe in the end of the file appear when I do:<br />add_drv -v -i "pci1039,900" sfe<br /><br />its output is there http://pastebin.com/m344b214scfhttps://www.blogger.com/profile/09047290969220688690noreply@blogger.comtag:blogger.com,1999:blog-6730844193902134967.post-32083601753526360912009-04-28T10:04:00.000-07:002009-04-28T10:04:00.000-07:00Thanks for reply Andre!
I've added a 32bit versio...Thanks for reply Andre!<br /><br />I've added a 32bit version of sfe (put it into /kernel/drv). The sfe.conf is missing even in existing osol setup, though I've tried to create an empty sfe.conf with no luck. <br /><br />The driver is not loaded on boot, this is the problem. There is even nothing from sfe in the log. I've downloaded sfe driver from its home page http://homepage2.nifty.com/mrym3/taiyodo/sfe-2.6.0a.tar.gz#../sfe-2.6.0a.tar.gz<br /><br />I've also tried the driver from snv_111 osol. And I can load both drivers manualy executing proper add_drv command. It adds a line into driver_aliases file, I change the updimage.sh script to preserve this file in the new image, but this has no effect.<br /><br />I will try to enable the debugging tomorrow when get access to this box.<br /><br />Thanks for your support!scfhttps://www.blogger.com/profile/09047290969220688690noreply@blogger.comtag:blogger.com,1999:blog-6730844193902134967.post-40316623600688884372009-04-28T06:59:00.000-07:002009-04-28T06:59:00.000-07:00scf,
Can you say which files you added (i'm guess...scf,<br /><br />Can you say which files you added (i'm guessing for 32-bit /kernel/drv/sfe, sfe.conf)?<br /><br />If you do modinfo after boot is the driver loaded? Are you using the driver binary for the matching solaris release (ie snv_110 driver with snv_110 EON)?<br /><br />Also, you may enable debugging at boot to help by adding after unix:<br />unix -m verbose or<br />unix -v<br /><br />You may also post your /var/adm/messages output at http://pastebin.com/ and link it back here so I could take a look.Andre Luehttps://www.blogger.com/profile/06886037020375947489noreply@blogger.comtag:blogger.com,1999:blog-6730844193902134967.post-50417832400459379152009-04-24T11:07:00.000-07:002009-04-24T11:07:00.000-07:00Hi! Thanks for your work on eon!
I have a problem...Hi! Thanks for your work on eon!<br /><br />I have a problem with adding a driver for my NIC. I have a SIS900 onboard adapter and I can configure it manually when booted from cd or usb drive. Though the driver doesn't get loaded when I boot with new image I have added the driver to. This image contains the driver file (sfe) in /kernel/drv (I use 32bit version) but it is just not loaded. I execute add_drv command with proper parameters, do ifconfig sfe4 plumb and it's there. What am I doing wrong?scfhttps://www.blogger.com/profile/09047290969220688690noreply@blogger.com