Article View: aus.computers.sun
Article #455Re: Magma Sbus driver v5.4 installs but no device nodes created - ideas?
From: Craig Dewick
Date: Thu, 25 May 2006 04:20
Date: Thu, 25 May 2006 04:20
45 lines
3364 bytes
3364 bytes
Craig Dewick <cdewick@lios.apana.org.au> writes: >Casper H.S. Dik <Casper.Dik@Sun.COM> writes: >>Is this a 64 bit driver? By default an Ultra 2 likely runs in 64 bit >>mode and won't load 32 bit drivers as a result. >That's a good point Casper. I will try the 64-bit driver instead. Magma >supply a 64-bit version called 'mh64' so I'll give that a go and see what >happens. Ok that produced the same result. This is what happened with the 32 bit 'mh' driver (recorded in /var/adm/messages): May 24 20:58:36 jedi swapgeneric: [ID 370176 kern.warning] WARNING: forceload of drv/mh failed May 24 20:58:40 jedi genunix: [ID 197085 kern.warning] WARNING: mod_installdrv: no major number for mh May 24 20:58:40 jedi mh: [ID 809075 kern.warning] WARNING: MAGMA: _init mod_install error=6. The same thing happened when I tried the 64 bit 'mh64' driver this morning: May 25 08:18:31 jedi swapgeneric: [ID 370176 kern.warning] WARNING: forceload of drv/mh64 failed May 25 08:18:35 jedi genunix: [ID 197085 kern.warning] WARNING: mod_installdrv: no major number for mh64 May 25 08:18:35 jedi mh64: [ID 809075 kern.warning] WARNING: MAGMA: _init mod_install error=6. I don't know if this is connected, but the /etc/name_to_major file doesn't show a major number for the mh driver, but that might be due to the 'forceload' action failing? I might try modifying /etc/system again to use "forceload: drv/sparcv9/mh" just in case that's the problem. That file btw is the same as the /kernel/drv/mh64 file, but I presume to the kernel it's handled a bit differently when loaded from /kernel/drv as opposed to from /kernel/drv/sparcv9? The 'postinstall' script supplied with the driver package doesn't do anything with /etc/name_to_major but it does edit some other files and all those modifications (to /etc/devlink.tab, /etc/system, /etc/iu.ap, /etc/minor_perm, and /etc/path_to_inst) are all ok as far as I can tell. Craig. -- Post by Craig Dewick (tm). Web @ "http://lios.apana.org.au/~cdewick". Email 2 "cdewick@lios.apana.org.au". SunShack @ "http://www.sunshack.org" Forums @ "http://www.sunshack.org/phpBB2". Also Galleries, tech archive, etc. Sun Microsystems webring at "http://n.webring.com/hub?ring=sunmicrosystemsu".
Technical Details
Message-ID:
<e53bat$qd$1@yoda.apana.org.au>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news4.google.com!news.glorb.com!news.tele.dk!feed118.news.tele.dk!news.melb.apana.org.au!news.yoda.apana.org.au!cdewickReferences:
<e51fls$9tp$1@yoda.apana.org.au> <44744879$0$31649$e4fe514c@news.xs4all.nl> <e52jfq$lko$1@yoda.apana.org.au>Show Full Headers
Complete Article Headers
X-Google-Thread: 10d053,2637e20caf8ce855 X-Google-Thread: 11035d,2637e20caf8ce855 X-Google-Thread: 1070f0,2637e20caf8ce855 X-Google-Attributes: gid10d053,gid11035d,gid1070f0,public X-Google-Language: ENGLISH,ASCII-7-bit From: Craig Dewick <cdewick@lios.apana.org.au> Newsgroups: aus.computers.sun,comp.unix.solaris,comp.sys.sun.admin Subject: Re: Magma Sbus driver v5.4 installs but no device nodes created - ideas? Date: Thu, 25 May 2006 04:20:45 +0000 (UTC) Organization: Core Matrix Foundation inc. ORBnet Lines: 45 Message-ID: <e53bat$qd$1@yoda.apana.org.au> References: <e51fls$9tp$1@yoda.apana.org.au> <44744879$0$31649$e4fe514c@news.xs4all.nl> <e52jfq$lko$1@yoda.apana.org.au> NNTP-Posting-Host: lios.apana.org.au X-Trace: yoda.apana.org.au 1148530845 845 203.14.152.52 (25 May 2006 04:20:45 GMT) X-Complaints-To: postmaster@yoda.apana.org.au NNTP-Posting-Date: Thu, 25 May 2006 04:20:45 +0000 (UTC) User-Agent: nn/6.6.5 Path: arc1-ca.pugleaf.net!g2news2.google.com!news4.google.com!news.glorb.com!news.tele.dk!feed118.news.tele.dk!news.melb.apana.org.au!news.yoda.apana.org.au!cdewick