From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Ferrell Subject: Re: Package for reading hardware information such as BIOS Version etc .. Date: Thu, 20 Mar 2003 19:11:39 -0800 Sender: linux-admin-owner@vger.kernel.org Message-ID: <3E7A82EB.2010907@baywinds.org> References: <2DE78F33FFE0D3118C0200508B94F9CA19420E5E@uswaumsx08medge.med.ge.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: "Sadanapalli, Pradeep Kumar (MED, TCS)" Cc: linux-admin@vger.kernel.org I see messages like that from a system that has a S.M.A.R.T. technology drive installed and the bios doesn't have support for it. Sadanapalli, Pradeep Kumar (MED, TCS) wrote: > I downloaded lshw-T.00.07.tar.gz and compiled. When I execute lshw in > X-Terminal, it works fine. > But when I executed it in the Virtual Terminal(Text Mode) , it generates > the output,but > before that it displays two error messages. > > "hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error } > hdc: drive_cmd: error=0x04 " > > I don't understand what these error messages mean? Can someone explain > me these error messages and why > I am getting these? > > Thanks > Pradeep > > > > > -----Original Message----- > From: Bruce Ferrell [mailto:bferrell@baywinds.org] > Sent: Wednesday, March 19, 2003 10:40 PM > To: Sadanapalli, Pradeep Kumar (MED, TCS) > Cc: linux-admin@vger.kernel.org > Subject: Re: Package for reading hardware information such as BIOS > Version etc .. > > > I just ran across something called lshw. I think I found it on > freshmeat. > > Sadanapalli, Pradeep Kumar (MED, TCS) wrote: > >>Hi Friends... >>Thank you all for all your responses for my previous mails..!! >> >>I am running RedHat Linux 8.0 on my Dell Latitude C610 Laptop. I am >>using the i8k package >>which reports the information such as BIOS Version, Serial Number, fan >>status, CPU temperature...etc. >> >>I believe it is SMM BIOS for Dell Latitude Laptops. I don't even what >>this SMM BIOS means? >> >>But when I am running the same i8k module on my Dell GX260 which runs >>same RedHat Linux 8.0, >>it reports an error message that >>"unsupported model Dell Optiplex GX260 >>unable to get SMM Dell Signature >>unable to get SMM BIOS Version" >> >>What is the BIOS that comes with Dell Optiplex GX260? Is there any > > other > >>package to read the serial number >>from BIOS, as we do with i8k module on Dell Laptops? Please tell me if > > I > >>am not clear >>with what I am saying. >> >>If anybody has got an idea on this, please share with me. >>Thank you all in advance... >> >>Thanks and Regards, >>Pradeep >> >> >>-----Original Message----- >>From: Paul Furness [mailto:paul.furness@vil.ite.mee.com] >>Sent: Wednesday, March 19, 2003 8:10 AM >>To: Yu Chen >>Cc: linux-admin@vger.kernel.org >>Subject: Re: Rather odd NIS problem >> >> >>Thanks, that fixed it. I know it sounds stupid, but it didn't occur to >>me that yppasswdd had a configuration file. Man, I must be asleep. :) >> >>Paul. >> >> >>On Wed, 2003-03-19 at 13:54, Yu Chen wrote: >> >> >>>Looks like the same problem I had once. On NIS server do a ps -ef|grep >> >>yp, >> >> >>>see how yppasswdd is run, in your case, it should be something like >>>rpc.yppasswdd -D /var/yp >>>if not, you should tell yppasswdd where is your files, edit >>>/etc/sysconfig/yppasswdd >>> >>>Hope this will help! >>> >>>=========================================== >>>Yu Chen >>>Howard Hughes Medical Institute >>>University of Maryland at Baltimore County >>>1000 Hilltop Circle >>>Baltimore, MD 21250 >>> >>>phone: (410)455-6347 >>> (410)455-2718 >>>fax: (410)455-1174 >>>email: chen@hhmi.umbc.edu >>>=========================================== >>> >>>On 19 Mar 2003, Paul Furness wrote: >>> >>> >>> >>>>Hello. >>>> >>>>I have a reccuring problem with NIS. My main production NIS server >>> >>won't >> >> >>>>let me change any passwords. The system is a completely new system >>> >>which >> >> >>>>I have built from the ground up to replace the old, failing one. It >>> >>is >> >> >>>>based around RedHat 7.3 with updates; the kernel version is >>>>2.4.18-24.7.x, ypserv is version 2.5-2.7x, ypbind is 1.10-7, and >>>>yp-tools is 2.6-4. >>>> >>>>Although the setup (in terms of the files which are shared) is the >>> >>same >> >> >>>>as the original system (which did work ok), the config files are the >>> >>new >> >> >>>>default ones, edited by me. Also, I have needed to edit the Makefile >>> >>in >> >> >>>>/var/yp so as to share the correct things as the correct names. The >>>>changes I made were based on comparing the old files with the new >>> >>ones, >> >> >>>>so I didn't simply copy all the old stuff into the new places. >>>> >>>>Anyhow, ypserv, ypbind and yppasswdd all start fine, and the domain >>> >>is >> >> >>>>shared correctly and works. I have moved everything over to using >>> >>this >> >> >>>>domain, and removed the old NIS server. Everything else works fine, >>> >>but >> >> >>>>when I try and change a user's password, this happens: >>>> >>>># yppasswd furnesp >>>>Changing NIS account information for furnesp on >>> >>antonia.vil.ite.mee.com. >> >> >>>>Please enter root password: >>>>Changing NIS password for furnesp on antonia.vil.ite.mee.com. >>>>Please enter new password: >>>>Please retype new password: >>>>Error while changing the NIS password. >>>>The NIS password has not been changed on antonia.vil.ite.mee.com. >>>># >>>> >>>>(obviosly, I enter the appropriate passwords when prompted!) >>>> >>>>If I try to "su - user" first, I still get the same output (asking >>> >>for >> >> >>>>user's old password instead of root password). >>>> >>>>Incidentally, I did wonder if the password I was using was too >>> >>simple, >> >> >>>>but the problem happens with very strong passwords as well. >>>> >>>>It may or may not affect it, but I am not using passwd or group file >>> >>in >> >> >>>>/etc; all the files are in /var/yp/ypfiles. I have edited the >>>>configuration in the Makefile to take account of this, and it works >>>>fine. If I manually enter a new user into /var/yp/ypfiles/passwd, >>> >>and >> >> >>>>copy/paste a password from an existing account into the password >>> >>field, >> >> >>>>then do a make, the new user account appears correctly in the NIS, >>> >>and >> >> >>>>the password works. Oh, and I am not using a shadow file at all. >>>> >>>> >>>>For brevity, I haven't copied the Makefile to this email, but below >>> >>is >> >> >>>>/etc/ypserv.conf and yp.conf. If anyone wants to look at the >>> >>Makefile, >> >> >>>>I'll send it to you off list. >>>> >>>>Has anyone seen this problem before? >>>> >>>>Tks. >>>> >>>>Paul. >>>> >>>>----------- >>>> >>>>yp.conf: >>>> >>>> >>>>domain vilnis broadcast >>>> >>>> >>>> >>>>ypserv.conf: >>>> >>>> >>>>dns: no >>>> >>>>files: 30 >>>> >>>>xfr_check_port: yes >>>> >>>># Host : Domain : Map : Security >>>> >>>>* : * : * : none >>>> >>>> >>>> >>>> >>>>--------------- >>>> >>>>-- >>>>Paul Furness >>>> >>>>Systems Manager >>>>Visual Information Lab >>>>Mitsubsihi Electric ITE BV >>>>Guildford, UK >>>>__________________________________________________________ >>>>| Fight Spam! Join EuroCAUCE: http://www.euro.cauce.org/ | >>>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>>> >>>> >>>>- >>>>To unsubscribe from this list: send the line "unsubscribe >>> >>linux-admin" in >> >> >>>>the body of a message to majordomo@vger.kernel.org >>>>More majordomo info at http://vger.kernel.org/majordomo-info.html >>>> >>> >>>- >>>To unsubscribe from this list: send the line "unsubscribe linux-admin" >> >>in >> >> >>>the body of a message to majordomo@vger.kernel.org >>>More majordomo info at http://vger.kernel.org/majordomo-info.html >> >