Well, a couple of replies but none that solved the problem, altho they
were correct as it turned out. Sun actually solved it - well, gave me a
workaround. Turns out it's a bug in sundiag. Bug ID 1182755. Seems that if
you have no floppy, have a CDROM but no CD loaded and vold is stopped (all of
which applied) the probe fails. It actually fails and core dumps but I
didn't notice that. So the fdtwo not found is actually just informative from
the probe, the next line "SunDiag: failed probing system configuration!" is
the clue to the probe actually dying.
The workaround I used was to put a CD in the CDROM drive and sundiag will
now start up fine.
Thanks to those with ideas, their messages are included below. I learned
a whole lot about system configuration in the process!
P.s. there is no patch for this bug. The Sundiag patch #101899-03 doesn't
fix the problem.
Original message:
-----------------------------------------------------
Hello all,
I'm trying to run sundiag on a SS20/514MP running Solaris 5.4 with kernel
patched to 101945-38. I get the following message after starting sundiag:
SunDiag: Starting probing routine, please wait...
07/02/96 08:55:56 wormwood probe INFO: SUNW,fdtwo device not found.
SunDiag: failed probing system configuration!
In addition, the following gets logged in syslog:
Jul 2 08:55:56 wormwood unix: Unable to install/attach driver 'fd'
(There is a file /kernel/drv/fd btw.)
After much poking/searching around I've come to the conclusion that
fdtwo is supposed to be a floppy drive. Well, this system doesn't HAVE
a floppy.
/etc/driver_aliases has this in it tho:
fd SUNW,fdtwo
After much poking/searching, I then came upon the file /etc/path_to_inst
which contained the lines:
....
"/SUNW,sx@f,80000000" 0
"/options" 0
"/obio" 0
"/obio/zs@0,100000" 0
"/obio/profile" 0
"/obio/zs@0,0" 1
"/obio/SUNW,fdtwo@0,700000" 0
"/pseudo" 0
Hmmmm..... Doing an ls -alR on /dev and /devices showed that there was
nothing linked to fdtwo so I tried deleting that line and rebooting with -r.
No joy there, it put the line back in! So... it would seem there's a
config somewhere that tells the system it's got a floppy but for the life of
me I can't figure out where.
One other possibility I've thought of would be that there IS a floppy
controller on-board (obio means on-board I/O, right) and that the problem is
that the reboot -r doesn't finish doing the necessary configurations...???
I've searched the answerbooks I've got and the Summaries which had some
info, they got me this far, but now I'm stuck.
Ideas/comments/fixes/etc. welcomed. I'll summarize.
Tnx,
Bob
-----------------------------------------------------------
Replies: (minor editing to avoid repetition of the original where possible.)
From: "Duane R. Larkin" <duane@cris.com>
Subject: Re: fdtwo device not found
To: bob@hobbes.dtcc.edu
Date: Tue, 2 Jul 1996 10:59:19 -0400 (EDT)
My thoughts, for what they are worth....
I do not believe SunDiag starts knowing how your system is confi'd. It
doesn't know you don't have a floppy, so it probes for it (along with
lots of other things). The probe INFO message is more informitive than
an error. The same is true with the syslog message. You should have
several 'Unable to install/attach driver' messages. The Solaris
kernel is dynamic, drivers are loaded at boot time. The system check
for what you need. If you don't need/have a device you get the message
'Unable to install/attach driver'.
Hope this helps.
...
-- /------------------------------------------------------------------------\ | | | Duane R. Larkin Voice: 517-895-1621 | | System Admin. Fax: 517-895-1610 | | Concentric Network Corp. E-mail: duane@concentric.net | | 400 Forty First St. | | Bay City, Mi. 48708 Thank you and have a nice day! | | | \------------------------------------------------------------------------/From: "Trevor Paquette" <TrevorPaquette@aec.ca> Date: Wed, 24 Jul 1996 10:34:29 -0600 To: bob@hobbes.dtcc.edu (Bob Rahe) Subject: Re: fdtwo device not found
You may want to try the following..
Comment out the fdtwo line from /etc/paths_to_inst.. then running under /bin/sh
_INIT_RECONFIG="YES" /etc/init.d/drvconfig /etc/init.d/devlinks
then reboot.. (maybe even another reboot -r)
Just a thought (or a shoot in the dark.. take your pick)
Trev
...
-- Name:Trevor Paquette |Network ServiCenters |Work:(403) 543-2355 Email:TrevorPaquette@nsci.net|600, 777 8th Ave SW | Fax:(403) 290-8400 postmaster@aec.ca |Calgary, Ab, Canada |ICBM:51'05"N/114'01"W root@aec.ca |T2P 3R5 |Mind:In the Rockies..
Date: Wed, 24 Jul 1996 12:18:20 -0500 From: hxktb0@svmail.supervalu.com.supervalu.com (Kris Briscoe) To: bob@hobbes.dtcc.edu Subject: Re: fdtwo device not found
It is my belief that this is merely an informative message and should not create alarm. I ran diag on my SS20 and got the same results. Not sure why the build a device table for the floppy if it does not exist, but it causes not problems.
Reason the load of the fd driver is due to the missing scsi device appropriate. If you want to test the do a modload and you should not have any problems.
Hope this helps, if not respond.
Regards, KRis _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ _/ _/ _/ Kristopher Briscoe _/ _/ Unix Systems Analyst _/ _/ _/ _/ Supervalu _/ _/ Client Server Services _/ _/ 11840 Valley View Rd _/ _/ Eden Prairie, Mn 55344 _/ _/ Phone (612) 828.4938 _/ _/ Fax (612) 828.4185 _/ _/ _/ _/ e-mail: hxktb0@svmail.supervalu.com _/ _/ unixboy@aol.com _/ _/ _/ _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
From: Kevin.Sheehan@uniq.com.au (Kevin Sheehan {Consulting Poster Child}) Date: Thu, 25 Jul 1996 09:45:05 EST To: bob@hobbes.dtcc.edu (Bob Rahe) Subject: Re: fdtwo device not found
[ Regarding "fdtwo device not found", bob@hobbes.dtcc.edu writes on Jul 24: ]
> I'm trying to run sundiag on a SS20/514MP running Solaris 5.4 with kernel > patched to 101945-38. I get the following message after starting sundiag: > > > SunDiag: Starting probing routine, please wait... > 07/02/96 08:55:56 wormwood probe INFO: SUNW,fdtwo device not found. > SunDiag: failed probing system configuration!
Okay - that's sundiag being stupid. Why it is insisting on fdtwo being there I have no idea. > > In addition, the following gets logged in syslog: > > Jul 2 08:55:56 wormwood unix: Unable to install/attach driver 'fd' > > (There is a file /kernel/drv/fd btw.)
This is normal. The system tries to auto-load things for which it has drivers. In this case, it's just letting you know that it tried to load the "fd" driver and couldn't - because you don't have one. > > After much poking/searching around I've come to the conclusion that > fdtwo is supposed to be a floppy drive. Well, this system doesn't HAVE > a floppy.
Yep - probably why the driver load failed. > > /etc/driver_aliases has this in it tho: > > fd SUNW,fdtwo > > After much poking/searching, I then came upon the file /etc/path_to_inst > which contained the lines: > > .... > > "/SUNW,sx@f,80000000" 0 > "/options" 0 > "/obio" 0 > "/obio/zs@0,100000" 0 > "/obio/profile" 0 > "/obio/zs@0,0" 1 > "/obio/SUNW,fdtwo@0,700000" 0 > "/pseudo" 0 > > Hmmmm..... Doing an ls -alR on /dev and /devices showed that there was > nothing linked to fdtwo so I tried deleting that line and rebooting with -r. > No joy there, it put the line back in! So... it would seem there's a > config somewhere that tells the system it's got a floppy but for the life of > me I can't figure out where.
Having the driver there. You might also want to try prtconf. The floppy *interface* is still there, so the system attempts to load it. You can stop that I suppose by rename the driver to fd- if you want. > > One other possibility I've thought of would be that there IS a floppy > controller on-board (obio means on-board I/O, right) and that the problem is > that the reboot -r doesn't finish doing the necessary configurations...???
It does, it just says that it couldn't load the driver, which is the message you see, since there is no device attached. > > I've searched the answerbooks I've got and the Summaries which had some > info, they got me this far, but now I'm stuck. > > Ideas/comments/fixes/etc. welcomed. I'll summarize.
Well, as far as system operation goes, it's not really broken. It sees a floppy controller and tries to auto-load the driver, which fails as there is no drive. That's the way it is supposed to work. You can move the driver out of the way if this bothers you.
As for sundiag, it looks like it assumes there is a floppy and loses the plot, which is a sundiag bug, and a different matter entirely.
l & h, kev
------ End of Replies, thanks to all -----------------
-- ---------------------------------------------------------------------------- |Bob Rahe, Delaware Tech&Comm Coll. / | |Computer Center, Dover, Delaware / | |Internet: bob@hobbes.dtcc.edu / | ----------------------------------------------------------------------------
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:06 CDT