Re: reading/writing CMOS beyond 256 bytes?
On Fri, 6 Jul 2001, Gregory (Grisha) Trubetskoy wrote: > I wrote a little brogram to read/write the CMOS settings to a file on an > Intel L440GX motherboard using the outb() to ports 0x70 and 0x71. The idea > is to save the BIOS settings I like and then be able to blast them from > within Linux without having to tinker with BIOS setup. > > Unfortunately, it seems that some settings are not in the 128 (or 256) > bytes accessible this way, so they must be stored elsewhere. the L440GX has a lot of stuff attached to ipmi. Perhaps some of it is stored there? Just a thought. Peter -- Peter Svensson ! Pgp key available by finger, fingerprint: <[EMAIL PROTECTED]>! 8A E9 20 98 C1 FF 43 E3 07 FD B9 0A 80 72 70 AF Remember, Luke, your source will be with you... always... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: reading/writing CMOS beyond 256 bytes?
On Fri, 6 Jul 2001, Gregory (Grisha) Trubetskoy wrote: I wrote a little brogram to read/write the CMOS settings to a file on an Intel L440GX motherboard using the outb() to ports 0x70 and 0x71. The idea is to save the BIOS settings I like and then be able to blast them from within Linux without having to tinker with BIOS setup. Unfortunately, it seems that some settings are not in the 128 (or 256) bytes accessible this way, so they must be stored elsewhere. the L440GX has a lot of stuff attached to ipmi. Perhaps some of it is stored there? Just a thought. Peter -- Peter Svensson ! Pgp key available by finger, fingerprint: [EMAIL PROTECTED]! 8A E9 20 98 C1 FF 43 E3 07 FD B9 0A 80 72 70 AF Remember, Luke, your source will be with you... always... - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: temperature standard - global config option?
On Wed, 6 Jun 2001, Chris Boot wrote: > I'm sorry, by I don't feel like adding 273 to every number I get just to > find the temperature of something. What I would do is give configuration > options to choose the default (Celsius/centigrade, Kelvin, or [shudder] > Fahrenheit) then, when you need to print or output a temperature, send it > off to a common converter function so you don't repeat core all over the > place. Kelvin (decikelvin?) is probably a good unit to use in the kernel. If you want something else you convert it in the programs you use to interact with the kernel. This is a usespace issue, I think. Peter -- Peter Svensson ! Pgp key available by finger, fingerprint: <[EMAIL PROTECTED]>! 8A E9 20 98 C1 FF 43 E3 07 FD B9 0A 80 72 70 AF Remember, Luke, your source will be with you... always... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: temperature standard - global config option?
On Wed, 6 Jun 2001, Chris Boot wrote: I'm sorry, by I don't feel like adding 273 to every number I get just to find the temperature of something. What I would do is give configuration options to choose the default (Celsius/centigrade, Kelvin, or [shudder] Fahrenheit) then, when you need to print or output a temperature, send it off to a common converter function so you don't repeat core all over the place. Kelvin (decikelvin?) is probably a good unit to use in the kernel. If you want something else you convert it in the programs you use to interact with the kernel. This is a usespace issue, I think. Peter -- Peter Svensson ! Pgp key available by finger, fingerprint: [EMAIL PROTECTED]! 8A E9 20 98 C1 FF 43 E3 07 FD B9 0A 80 72 70 AF Remember, Luke, your source will be with you... always... - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] ip autoconfig with modules, kernel 2.4
On Fri, 11 May 2001, Brian J. Murrell wrote: > If there were a way to tell the kernel, from userspace, for > change_root()/mount_root() where the nfsroot path was, yes. I have > been hunting through all of the (nfs) root mount code and I don't see > it. It looks like it can be set either on the command line, or by the > kernel implementation of bootp. Am I missing it somewhere? Doesn't the pivot_root do just that in 2.4? Not that I have used it or anything. Peter -- Peter Svensson ! Pgp key available by finger, fingerprint: <[EMAIL PROTECTED]>! 8A E9 20 98 C1 FF 43 E3 07 FD B9 0A 80 72 70 AF <[EMAIL PROTECTED]> ! Remember, Luke, your source will be with you... always... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] ip autoconfig with modules, kernel 2.4
On Fri, 11 May 2001, Brian J. Murrell wrote: If there were a way to tell the kernel, from userspace, for change_root()/mount_root() where the nfsroot path was, yes. I have been hunting through all of the (nfs) root mount code and I don't see it. It looks like it can be set either on the command line, or by the kernel implementation of bootp. Am I missing it somewhere? Doesn't the pivot_root do just that in 2.4? Not that I have used it or anything. Peter -- Peter Svensson ! Pgp key available by finger, fingerprint: [EMAIL PROTECTED]! 8A E9 20 98 C1 FF 43 E3 07 FD B9 0A 80 72 70 AF [EMAIL PROTECTED] ! Remember, Luke, your source will be with you... always... - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: magic device renumbering was -- Re: Linux 2.4.2ac20
On Wed, 14 Mar 2001, Christoph Hellwig wrote: > Put LABEL= in you fstab in place of the device name. > > Christoph > > P.S. UUID= work, too - but I prefer a human-readable label... There are a lot of different devices besides disks, e.g. tape drives etc. I seem to remember from the last round this came up that modern FC fabrics have some dynamic properties that may require more intelligence in the kernel. Peter -- Peter Svensson ! Pgp key available by finger, fingerprint: <[EMAIL PROTECTED]>! 8A E9 20 98 C1 FF 43 E3 07 FD B9 0A 80 72 70 AF <[EMAIL PROTECTED]> ! Remember, Luke, your source will be with you... always... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: magic device renumbering was -- Re: Linux 2.4.2ac20
On Wed, 14 Mar 2001, Christoph Hellwig wrote: Put LABEL=label set with e2label in you fstab in place of the device name. Christoph P.S. UUID= work, too - but I prefer a human-readable label... There are a lot of different devices besides disks, e.g. tape drives etc. I seem to remember from the last round this came up that modern FC fabrics have some dynamic properties that may require more intelligence in the kernel. Peter -- Peter Svensson ! Pgp key available by finger, fingerprint: [EMAIL PROTECTED]! 8A E9 20 98 C1 FF 43 E3 07 FD B9 0A 80 72 70 AF [EMAIL PROTECTED] ! Remember, Luke, your source will be with you... always... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux stifles innovation...
On Sun, 18 Feb 2001, Gregory S. Youngblood wrote: > I remember being at a computer show in Minneapolis where a small company > was showing off this mouse that worked on a variety of surfaces without a > ball. I'm trying to remember if the mouse was optical or used yet another > method of functioning -- I think it was optical, though I could be > mistaken. This was in 1992/1993. > > The point is, I really do not believe Microsoft made the "leap" to provide > opitcal mice without the need of the mousepad grid. Their "innovation" was > in marketing it on a wide scale though. I believe I read about an optical mouse that worked on any surface by tracking surface constrast movement in an old issue of Byte. I think it was an Xerox invention, but my memory may be off. Peter -- Peter Svensson ! Pgp key available by finger, fingerprint: <[EMAIL PROTECTED]>! 8A E9 20 98 C1 FF 43 E3 07 FD B9 0A 80 72 70 AF <[EMAIL PROTECTED]> ! Remember, Luke, your source will be with you... always... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux stifles innovation...
On Sun, 18 Feb 2001, Gregory S. Youngblood wrote: I remember being at a computer show in Minneapolis where a small company was showing off this mouse that worked on a variety of surfaces without a ball. I'm trying to remember if the mouse was optical or used yet another method of functioning -- I think it was optical, though I could be mistaken. This was in 1992/1993. The point is, I really do not believe Microsoft made the "leap" to provide opitcal mice without the need of the mousepad grid. Their "innovation" was in marketing it on a wide scale though. I believe I read about an optical mouse that worked on any surface by tracking surface constrast movement in an old issue of Byte. I think it was an Xerox invention, but my memory may be off. Peter -- Peter Svensson ! Pgp key available by finger, fingerprint: [EMAIL PROTECTED]! 8A E9 20 98 C1 FF 43 E3 07 FD B9 0A 80 72 70 AF [EMAIL PROTECTED] ! Remember, Luke, your source will be with you... always... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux and 802.IQ
On Fri, 17 Nov 2000, Robert Cohen wrote: > Anyway is Linux 802.IQ compliant? Is Linux 2.2 or just 2.4. > How long has 802.IQ been around and how widespread is it. Is Solaris > compliant. How about NT/ Win 2000. See http://vlan.sourceforge.net/ and http://scry.wanfear.com/~greear/vlan.html for two implementations for Linux. Peter -- Peter Svensson ! Pgp key available by finger, fingerprint: <[EMAIL PROTECTED]>! 8A E9 20 98 C1 FF 43 E3 07 FD B9 0A 80 72 70 AF <[EMAIL PROTECTED]> ! Remember, Luke, your source will be with you... always... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Linux and 802.IQ
On Fri, 17 Nov 2000, Robert Cohen wrote: Anyway is Linux 802.IQ compliant? Is Linux 2.2 or just 2.4. How long has 802.IQ been around and how widespread is it. Is Solaris compliant. How about NT/ Win 2000. See http://vlan.sourceforge.net/ and http://scry.wanfear.com/~greear/vlan.html for two implementations for Linux. Peter -- Peter Svensson ! Pgp key available by finger, fingerprint: [EMAIL PROTECTED]! 8A E9 20 98 C1 FF 43 E3 07 FD B9 0A 80 72 70 AF [EMAIL PROTECTED] ! Remember, Luke, your source will be with you... always... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: serial problems
On Tue, 24 Oct 2000, Theodore Y. Ts'o wrote: > First of all, Red Hat doesn't install /etc/rc.d/init.d/serial. (Checked > under both Red Hat 7.0 and Red Hat 6.2). That script comes with some > version of setserial that I ship, but in its default configuration it > certainly won't crash machines. You'll have to send me a copy of your > rc.d/init.d/serial script, plus my /etc/serial.conf for me to debug it. I missed the beginning of this thread so I'm not sure if this is relevant or not. We had som strange lockups with a serial console enabled. If anything started probing for serial port when using a serial console the whole system froze. Peter - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: serial problems
On Tue, 24 Oct 2000, Theodore Y. Ts'o wrote: First of all, Red Hat doesn't install /etc/rc.d/init.d/serial. (Checked under both Red Hat 7.0 and Red Hat 6.2). That script comes with some version of setserial that I ship, but in its default configuration it certainly won't crash machines. You'll have to send me a copy of your rc.d/init.d/serial script, plus my /etc/serial.conf for me to debug it. I missed the beginning of this thread so I'm not sure if this is relevant or not. We had som strange lockups with a serial console enabled. If anything started probing for serial port when using a serial console the whole system froze. Peter - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
