Re: FreeBSD problem: $50 reward.
On Mon, Jul 01, 2002 at 06:25:04PM -0700, Lucky Green wrote: Fifty bucks to the person that is first to help me solve this problem. I have a brand new Asus A7V333 motherboard with the latest BIOS version 1007. I am trying to install FreeBSD 4.6 via floppies onto a brand new Western Digital WD1200AB 120GB IDE drive. I have installed FreeBSD many times before going back to FreeBSD 2.x. The partition editor and disklabel only see 8056MB of my 120GB drive. In other words, I am being stopped by the 8.4GB barrier. Obviously, Asus' new motherboard supports IDE drives larger than 8.4GB. Following some suggestions, I wrote a slice and disklabels to the drive at 8.4GB. This did not help. The drive is still only being recognized at 8.4GB. Any suggestions how to overcome the problem are appreciated. I need to very badly copy some data from a FireWire drive with FAT32 partitions onto the new FreeBSD installation before 6 AM PDT. Set it up to the dangerously dedicated mode covering the entire disk, using the `F' key and answering `No' to the forthcoming question, while in the slice editor. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg35447/pgp0.pgp Description: PGP signature
RE: S/390 port status
On 02-Jul-2002 Serguei Tzukanov wrote: Reaches mount root prompt in emulator. More info is on http://tzukanov.narod.ru/freebsd390/ Wow. Very cool. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
FreeBSD Auto-update (Was: Re: resolv and dynamic linking to compatlibc)
On Mon, 1 Jul 2002, Brett Glass wrote: At 12:22 PM 7/1/2002, Jacques A. Vidrine wrote: Gee, I guess we better get cracking to take offline every previous version of libc, too --- which would mean every version of FreeBSD and who knows what else. Alas, ethics demand that they be either taken offline or accompanied with a clear, visible, and strong warning. Who is going to expend the time and effort to do this, and what task should they let drop on the floor to get it done? [...snip...] A snapshot of 4.6-STABLE should also be made and released as 4.6.1. I repeat my above question. Yes, Windows-update-like machinery in sysinstall would be nice, but I don't see you falling all over yourself to either contribute it or fund it. All I see you doing is complaining that your priorities aren't adopted by the committers. What you want is more likely to occur if/when sysinstall is cleaned up. By all accounts, it's a maze of twisted little code paths, all alike. You could contribute to that, for a start, to make sure that the modularity needed to plug in an update facility is designed in. I'd suggest piggybacking the update facility on top of portupgrade to minimize duplication of effort. That, of course, depends upon the availability of known good binary packages with valid MD5 checksums and/or PGP signatures, and that's a whole 'nother resource problem. Followups to -hackers. -- Chris BeHanna http://www.pennasoft.com Principal Consultant PennaSoft Corporation [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FreeBSD Auto-update (Was: Re: resolv and dynamic linking to compatlibc)
[Apologies if this gets delivered twice; some broken DNS is causing mail sent via shaw.ca to bounce.] At 10:32 02/07/2002 -0400, Chris BeHanna wrote: On Mon, 1 Jul 2002, Brett Glass wrote: Alas, ethics demand that [older code which is now known to have security flaws] be either taken offline or accompanied with a clear, visible, and strong warning. Who is going to expend the time and effort to do this, and what task should they let drop on the floor to get it done? A snapshot of 4.6-STABLE should also be made and released as 4.6.1. You could contribute to that, for a start, to make sure that the modularity needed to plug in an update facility is designed in. I'd suggest piggybacking the update facility on top of portupgrade to minimize duplication of effort. That, of course, depends upon the availability of known good binary packages with valid MD5 checksums and/or PGP signatures, and that's a whole 'nother resource problem. I'm new here (well, I've only been around for a bit over a year) so I'm probably hopelessly lost, but... what is wrong with making world and (GENERIC) kernel each time the 4.6 security branch is updated, and publishing (signed) lists of the form if you have file X with md5 hash X_hash, replace it with file Y with md5 hash Y_hash (where X is a local path, and Y is a URL)? I'd do this myself, except that I don't have any secure system to do this, and I'd be horrified if anyone would trust binary updates coming from me anyway. Colin it can't really be that easy, can it? Percival To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
AMI MegaRAID + Reboot issues
Hi, I've posted on this before, and I've received no reply. I'm cross-posting just in case it was missed before (I am desperate for help) and to ask for further advice. Basically we have a number of FreeBSD servers, running 4.5-RELEASE and 4.6-RELEASE, that use AMI MegaRaid 500 controllers. These boxes refuse to reboot when sent a reboot or shutdown -r. They simply close all processes and show : amr0: flushing cache...done Rebooting... At this point the numlock key is locked, and Ctrl + Alt + Deleting does nothing. The exact dmesg shows: amr0: AMI MegaRAID mem 0x-0x irq 11 at device 11.0 on pci0 amr0: Series 475 40 Logical Drive Firmware Firmware E161, BIOS 3.13, 32MB RAM This is the same controller in both boxes that is giving us this particular problem. Has anybody experienced and managed to solve this problem. Not being able to remotely reboot our servers is not a good thing. Are there any other recommended AMI controllers? What I find odd is this controller is specifically mentioned in both the Hardware Notes and amr(4). -byron To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FreeBSD Auto-update (Was: Re: resolv and dynamic linking tocompatlibc)
On Tue, 2 Jul 2002, Colin Andrew Percival wrote: [Apologies if this gets delivered twice; some broken DNS is causing mail sent via shaw.ca to bounce.] At 10:32 02/07/2002 -0400, Chris BeHanna wrote: On Mon, 1 Jul 2002, Brett Glass wrote: Alas, ethics demand that [older code which is now known to have security flaws] be either taken offline or accompanied with a clear, visible, and strong warning. Who is going to expend the time and effort to do this, and what task should they let drop on the floor to get it done? A snapshot of 4.6-STABLE should also be made and released as 4.6.1. You could contribute to that, for a start, to make sure that the modularity needed to plug in an update facility is designed in. I'd suggest piggybacking the update facility on top of portupgrade to minimize duplication of effort. That, of course, depends upon the availability of known good binary packages with valid MD5 checksums and/or PGP signatures, and that's a whole 'nother resource problem. I'm new here (well, I've only been around for a bit over a year) so I'm probably hopelessly lost, but... what is wrong with making world and (GENERIC) kernel each time the 4.6 security branch is updated, and publishing (signed) lists of the form if you have file X with md5 hash X_hash, replace it with file Y with md5 hash Y_hash (where X is a local path, and Y is a URL)? That's the basic idea, in part. If cons, for example, had the ability to use a URL to point to a cache, this could work just ducky (cons uses MD5 hashes rather than timestamps to determine if a file is out-of-date. That's a big win over make; however, cons can't yet do parallel builds). If the base system were itself divided into packages, then a solution based upon portupgrade could be employed. It requires someone to invest the time to set it up, and it requires some dedicated, trusted hardware, as you point out below: I'd do this myself, except that I don't have any secure system to do this, and I'd be horrified if anyone would trust binary updates coming from me anyway. Another part of the puzzle is generating and supplying trusted precompiled packages from the ports tree. Finally, the last link in the chain is teaching sysinstall to automatically search for newer packages than were burned onto the CD, so that it can prompt the user to install the newer (presumably more secure) versions. Brett has been moaning for a very long time that this mechanism isn't in place, but he hasn't lifted a finger to help put it in place. -- Chris BeHanna http://www.pennasoft.com Principal Consultant PennaSoft Corporation [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: AMI MegaRAID + Reboot issues
At 4:49 PM +0100 7/2/02, Byron Schlemmer wrote: Hi, I've posted on this before, and I've received no reply. I'm cross-posting just in case it was missed before (I am desperate for help) and to ask for further advice. Basically we have a number of FreeBSD servers, running 4.5-RELEASE and 4.6-RELEASE, that use AMI MegaRaid 500 controllers. These boxes refuse to reboot when sent a reboot or shutdown -r. They simply close all processes and show : amr0: flushing cache...done Rebooting... At this point the numlock key is locked, and Ctrl + Alt + Deleting does nothing. This will not help much, but I can at least say that I have noticed your messages go by. Unfortunately I have no experience with any raid controllers under freebsd. If you made it successfully to the Rebooting... line, then I think it's at the point that freebsd has done everything it expected to do, and freebsd has told the hardware to reboot. I do not know why the hardware wouldn't reboot at that point. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
'make release' tries to build a port?
I'm mucking with 'make release' under 4.5-RELEASE, and keep running into a stumbling block: When the documentation toolset is being built in the chrooted environment, at one point docbook-dsssl-doc is built, among other things, via ports. Regrettably, this is hosted on Sourceforge, who've interposed a 'pick-a-mirror' webpage when you attempt to do a regular http download. So, the port build fails, and 'make release' fails, and rerunning 'make release' scrubs all of your work. I seem to have two options: - convince Sourceforge to unbreak themselves, or - install these documentation tools on my system, and make them somehow available in the chrooted environment. I'm trying the latter: I was able to circumvent Sourceforge enough to get the port installed. I _think_ I need to affect src/etc/mtree/BSD.usr.dist to reflect the /usr/local/share/sgml/docbook tree, but I may be wrong. My only effort to edit this file resulted in an even worse 'make release' effort; I must be misunderstanding the syntax of that file. Does anyone have any advice on how to get the 'make release' chroot environment to take advantage of the ports I've already got installed? Or have I missed the point entirely? Thanks for your time... -- Brian 'you Bastard' Reichert[EMAIL PROTECTED] 37 Crystal Ave. #303Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: AMI MegaRAID + Reboot issues
On Tue, 2 Jul 2002, Byron Schlemmer wrote: Hi, I've posted on this before, and I've received no reply. I'm cross-posting just in case it was missed before (I am desperate for help) and to ask for further advice. My apologies to the list for this double post. Is seems the list manager is too smart for me. I'll post separately to -questions. -byron ( ... sneaks away in shame ... ) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: 'make release' tries to build a port?
On 2 Jul, Brian Reichert wrote: I'm mucking with 'make release' under 4.5-RELEASE, and keep running into a stumbling block: When the documentation toolset is being built in the chrooted environment, at one point docbook-dsssl-doc is built, among other things, via ports. Regrettably, this is hosted on Sourceforge, who've interposed a 'pick-a-mirror' webpage when you attempt to do a regular http download. So, the port build fails, and 'make release' fails, and rerunning 'make release' scrubs all of your work. I seem to have two options: - convince Sourceforge to unbreak themselves, or - install these documentation tools on my system, and make them somehow available in the chrooted environment. Try manually downloading a copy of the distfile into your non-chrooted /usr/ports/distfiles directory. make release copies all your distfiles into the chrooted environment. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: AMI MegaRAID + Reboot issues
--- Garance A Drosihn [EMAIL PROTECTED] wrote: At 4:49 PM +0100 7/2/02, Byron Schlemmer wrote: Hi, I've posted on this before, and I've received no reply. I'm cross-posting just in case it was missed before (I am desperate for help) and to ask for further advice. Basically we have a number of FreeBSD servers, running 4.5-RELEASE and 4.6-RELEASE, that use AMI MegaRaid 500 controllers. These boxes refuse to reboot when sent a reboot or shutdown -r. They simply close all processes and show : amr0: flushing cache...done Rebooting... At this point the numlock key is locked, and Ctrl + Alt + Deleting does nothing. This will not help much, but I can at least say that I have noticed your messages go by. Unfortunately I have no experience with any raid controllers under freebsd. If you made it successfully to the Rebooting... line, then I think it's at the point that freebsd has done everything it expected to do, and freebsd has told the hardware to reboot. I do not know why the hardware wouldn't reboot at that point. Did you check the BIOS settings on that machines, and if the Raid controller has its own BIOS, did you check that as well? Just an FYI. -- Hiten __ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
RTU.ru
÷ÁÛÅ ÐÒÅÄÐÒÉÑÔÉÅ ÅÝÅ ÎÅ ×ÎÅÓÅÎÏ × ËÁÔÁÌÏÇ RTU.ru? üÔÏ ÎÅ ÐÏÚÄÎÏ ÓÄÅÌÁÔØ ÓÅÊÞÁÓ http://www.rtu.ru/registration/ äÏÐÕÓËÁÅÔÓÑ ÒÅÇÉÓÔÒÁÃÉÑ ÐÒÅÄÐÒÉÑÔÉÊ, ÎÅ ÉÍÅÀÝÉÈ Ó×ÏÅÇÏ ÓÁÊÔÁ. ðÏÄÒÏÂÎÏÓÔÉ ÎÁ www.rtu.ru/about/ áÄÍÉÎÉÓÔÒÁÔÏÒ ËÁÔÁÌÏÇÁ www.rtu.ru To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: 'make release' tries to build a port?
On Tue, Jul 02, 2002 at 03:46:18PM -0700, Don Lewis wrote: On 2 Jul, Brian Reichert wrote: I'm mucking with 'make release' under 4.5-RELEASE, and keep running into a stumbling block: When the documentation toolset is being built in the chrooted environment, at one point docbook-dsssl-doc is built, among other things, via ports. Regrettably, this is hosted on Sourceforge, who've interposed a 'pick-a-mirror' webpage when you attempt to do a regular http download. So, the port build fails, and 'make release' fails, and rerunning 'make release' scrubs all of your work. I seem to have two options: - convince Sourceforge to unbreak themselves, or - install these documentation tools on my system, and make them somehow available in the chrooted environment. Try manually downloading a copy of the distfile into your non-chrooted /usr/ports/distfiles directory. make release copies all your distfiles into the chrooted environment. I did copy those file to my /usr/ports/distfiles manually, in preperation for installing them in the base system; % ls -ld /usr/ports/distfiles/docb* -rw-r--r-- 1 root ports 61031 Jan 10 1997 /usr/ports/distfiles/docbk30.tar.Z -rw--- 1 root ports 336295 Jun 30 02:44 /usr/ports/distfiles/docbook-dsssl-1.73.tar.gz -rw-r--r-- 1 root ports 217706 Jun 30 20:32 /usr/ports/distfiles/docbook-dsssl-doc-1.73.tar.gz But, not all of /usr/ports/distfiles is copied into the chrooted directory. I have well over a hundred files there, and oly a dozen or so got subsequently fetched. I've saved a typescript of my efforts, if you think perusing that would be helpful. I ran 'make release' thusly: /usr/bin/time make release \ CHROOTDIR=/home/release \ BUILDNAME=4.5-RELEASE \ CVSROOT=/home/ncvs \ RELEASETAG=RELENG_4_5_0_RELEASE in a script session. The resulting typescript has this line in it (I've wrapped it): if [ -d /home/src/release/../../ports/distfiles/ ]; then cp -rp /home/src/release/../../ports/distfiles /home/release/usr/ports/distfiles; fi And sure enough. /home/src/release/../../ports/distfiles/ is not congruent to /usr/src/distfiles. In fact, I don't see where in that typescript file the distfiles tree is copied at all. Did I mis-invoke make? If anyone cares, here's a typescript of my efforts: http://www.numachi.com/~reichert/misc/typescript.make_release.1025660080 Again, thanks for your time... -- Brian 'you Bastard' Reichert[EMAIL PROTECTED] 37 Crystal Ave. #303Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: 'make release' tries to build a port?
src/release/Makefile assumes that src/release directory is actually /usr/src/release. It seems that your source code location is /home/src. reichert /usr/bin/time make release \ reichert CHROOTDIR=/home/release \ reichert BUILDNAME=4.5-RELEASE \ reichert CVSROOT=/home/ncvs \ reichert RELEASETAG=RELENG_4_5_0_RELEASE DOCDISTFILES=/your/ports/distfile/directory will help you. Note that this variable name is changed to 'RELEASEDISTFILES' in recent 4-stable. If you want to learn more about make release, read release(7) manual available in recent 4-stable. Also src/release/Makefile will help you:) -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: 'make release' tries to build a port?
On Wed, Jul 03, 2002 at 11:33:04AM +0900, Makoto Matsushita wrote: src/release/Makefile assumes that src/release directory is actually /usr/src/release. It seems that your source code location is /home/src. I hoped hoped that symlinks would solve that problem. :/ reichert /usr/bin/time make release \ reichert CHROOTDIR=/home/release \ reichert BUILDNAME=4.5-RELEASE \ reichert CVSROOT=/home/ncvs \ reichert RELEASETAG=RELENG_4_5_0_RELEASE DOCDISTFILES=/your/ports/distfile/directory will help you. Note that this variable name is changed to 'RELEASEDISTFILES' in recent 4-stable. If you want to learn more about make release, read release(7) manual available in recent 4-stable. Also src/release/Makefile will help you:) Ah, thank you for the pointer! My only other one was: http://people.freebsd.org/~murray/#publications The Release Engineering of FreeBSD 4.4, Conference Proceedings, BSDCon Europe 2001 A very helpful PDF file... Off I go, for more poking... -- - Makoto `MAR' Matsushita -- Brian 'you Bastard' Reichert[EMAIL PROTECTED] 37 Crystal Ave. #303Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
test please ignore
To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: AS99127F Hardware Monitor
On Mon, Jul 01, 2002 at 07:07:54AM -0700, Thomas D. Dean wrote:
The ASUS A7N266-E motherboard has the nVidia 420D chipset. Of course,
ASUS and nVidia will not provide datasheets...
This is not a production machine...
So, have you -current installed?
Here is the nForce diff from Linux lm_sensors. Do you feel like trying the change by
yourself? Otherwise, I'll have to do it...
Nicholas
--
Nicholas Souchu - [EMAIL PROTECTED] - [EMAIL PROTECTED]
Index: i2c-amd756.c
===
RCS file: /home/cvs/lm_sensors2/kernel/busses/i2c-amd756.c,v
retrieving revision 1.16
retrieving revision 1.19
diff -u -r1.16 -r1.19
--- i2c-amd756.c2002/05/01 23:17:25 1.16
+++ i2c-amd756.c2002/05/02 14:44:31 1.19
@@ -2,7 +2,7 @@
amd756.c - Part of lm_sensors, Linux kernel modules for hardware
monitoring
-Copyright (c) 1999 Merlin Hughes [EMAIL PROTECTED]
+Copyright (c) 1999-2002 Merlin Hughes [EMAIL PROTECTED]
Shamelessly ripped from i2c-piix4.c:
@@ -25,7 +25,11 @@
*/
/*
- Supports AMD756, AMD766, and AMD768.
+2002-04-08: Added nForce support. (Csaba Halasz)
+*/
+
+/*
+ Supports AMD756, AMD766, AMD768 and nVidia nForce
Note: we assume there can only be one device, with one SMBus interface.
*/
@@ -41,21 +45,31 @@
#include version.h
#include linux/init.h
-#ifdef MODULE_LICENSE
-MODULE_LICENSE(GPL);
-#endif
-
#ifndef PCI_DEVICE_ID_AMD_756
#define PCI_DEVICE_ID_AMD_756 0x740B
#endif
#ifndef PCI_DEVICE_ID_AMD_766
#define PCI_DEVICE_ID_AMD_766 0x7413
#endif
+#ifndef PCI_DEVICE_ID_NVIDIA_NFORCE_SMBUS
+#define PCI_DEVICE_ID_NVIDIA_NFORCE_SMBUS 0x01B4
+#endif
+
+struct sd {
+const unsigned short vendor;
+const unsigned short device;
+const unsigned short function;
+const char* name;
+int amdsetup:1;
+};
-static int supported[] = {PCI_DEVICE_ID_AMD_756,
- PCI_DEVICE_ID_AMD_766,
- 0x7443, /* AMD768 */
- 0 };
+static struct sd supported[] = {
+{PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_756, 3, AMD756, 1},
+{PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_766, 3, AMD766, 1},
+{PCI_VENDOR_ID_AMD, 0x7443, 3, AMD768, 1},
+{PCI_VENDOR_ID_NVIDIA, 0x01B4, 1, nVidia nForce, 0},
+{0, 0, 0}
+};
/* AMD756 SMBus address offsets */
#define SMB_ADDR_OFFSET0xE0
@@ -141,6 +155,7 @@
};
static int __initdata amd756_initialized;
+static struct sd *amd756_sd = NULL;
static unsigned short amd756_smba = 0;
/* Detect whether a AMD756 can be found, and initialize it, where necessary.
@@ -150,7 +165,7 @@
int amd756_setup(void)
{
unsigned char temp;
- int *num = supported;
+ struct sd *currdev;
struct pci_dev *AMD756_dev = NULL;
if (pci_present() == 0) {
@@ -158,38 +173,41 @@
return(-ENODEV);
}
- /* Look for the AMD756, function 3 */
- /* Note: we keep on searching until we have found 'function 3' */
- do {
- if((AMD756_dev = pci_find_device(PCI_VENDOR_ID_AMD,
- *num, AMD756_dev))) {
- if(PCI_FUNC(AMD756_dev-devfn) != 3)
- continue;
- break;
+ /* Look for a supported chip */
+ for(currdev = supported; currdev-vendor; ) {
+ AMD756_dev = pci_find_device(currdev-vendor,
+ currdev-device, AMD756_dev);
+ if (AMD756_dev != NULL) {
+ if (PCI_FUNC(AMD756_dev-devfn) == currdev-function)
+ break;
+ } else {
+ currdev++;
}
- num++;
- } while (*num != 0);
+ }
if (AMD756_dev == NULL) {
printk
- (i2c-amd756.o: Error: Can't detect AMD756, function 3!\n);
+ (i2c-amd756.o: Error: No AMD756 or compatible device
+detected!\n);
return(-ENODEV);
}
+ printk(KERN_INFO i2c-amd756.o: Found %s SMBus controller.\n, currdev-name);
+ if (currdev-amdsetup)
+ {
+ pci_read_config_byte(AMD756_dev, SMBGCFG, temp);
+ if ((temp 128) == 0) {
+ printk(i2c-amd756.o: Error: SMBus controller I/O not
+enabled!\n);
+ return(-ENODEV);
+ }
- pci_read_config_byte(AMD756_dev, SMBGCFG, temp);
- if ((temp 128) == 0) {
- printk
- (i2c-amd756.o: Error: SMBus controller I/O not enabled!\n);
- return(-ENODEV);
+ /* Determine the address of the SMBus areas */
+ /* Technically it is a dword but... */
+ pci_read_config_word(AMD756_dev, SMBBA, amd756_smba);
+ amd756_smba = 0xff00;
+ amd756_smba += SMB_ADDR_OFFSET;
WANTED: Business People...
DISTRIBUTORS WANTED: We're looking for motivated, entrepreneurial people who would like to be their own boss and earn an executive 6-figure income by this time next year. Sales or travel industry background a plus, but not necessary. Would you enjoy earning $1,000 commissions starting this month? (And market a product with a value of over $15,000). This is a legitimate business that you can run from your home: - You make $1,000 profit for every sale - Market a high demand travel-related product - Total support given at all times - Excellent income is possible starting immediately We have a simple turn-key system for you to plug into. We have our own leads for you to work, and a great personalized website which we provide for you. Our support team is unparalleled and you can start earning $1,000 per sale right away. If you're success-minded and enjoy a challenge that this could be just the opportunity you've been looking for. For FREE and immediate info, please send your name to the email address below: mailto:[EMAIL PROTECTED] Unsubscribe Instructions: To remove yourself from further mailings, please send a blank email to the address below: mailto:[EMAIL PROTECTED] 1817qjvl7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
