Re: System freeze when useing bfe (Broadcom BCM440x) driver
Hello again, Well on the up side i'm sending this from my inspiron 1100. It only took me how long? I ended up useing 5.3BETA2 since that came out in the middle of my hacking attempts on this system. Thanks for your advice. Oh and btw the freezes during sysinstall were while configuring the X.org server( i have now learned to do this post install) and those bug's are allready known so i didn't bother reporting them. Thanks again. On Sat, 28 Aug 2004 11:04:57 +0930, Daniel O'Connor <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Sat, 28 Aug 2004 07:26, Genius Freak wrote: > > The kernel is rebuilding now :) > > I was so desperate I even tried the 5.3 beta1 to see if that would > > work and it did but it was too much of a beta for me to use, it > > crashed in sysinstall twice. > > Personally I'd trust 5.3-BETA over 5.2.1... > > If it crashes in sysinstall you should report it (eg the panic message) so > it's less of a beta when it's released :) > > - -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.2.4 (FreeBSD) > > iD8DBQFBL+FB5ZPcIHs/zowRAglPAKCH0Ch2W3h4/rYvMIJVnFLffwmZVgCfX5dF > jX8bNG5v5NWXfBoWnPskkw8= > =2gbX > -END PGP SIGNATURE- > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: slow login, app launching, etc
"Bagus" wrote: > > Hi, is anyone able to help me problem solve on this? Is this the right > forum for this kind of question? If not, could someone please send me a > pointer to an organization that might be able to help. I have a small budget > to get this fixed if anyone wants it. > > I'm running FreeBSD 2.2CAM-19980716-SNAP on bagus.org. > > I've been running it for a few years. Recently, after normal performance, > I've been experiencing extremely slow login prompt appearance, extremely > slow application launching and what bugs me the most is the extremely slow > response time of my java-web server. OTher functionality is ok. It serves > html files just fine and also basic command line response is fine. > > Anyone out there have any clues as to what it could be? I'm kind > of guessing it has something to do with some name resolution somewhere, > but I'm not sure. Any help would be greatly appreciated. Consider upgrading to 4.10-RELEASE, while you'r doing that, you may resolve some old issues (caution, we abandoned a few thing between 2 & 4, such as one old scsi controller I used to have, Future domain something 85 as I recall). I sympathise with "never touch a running system" but 2.2 is Seriously ancient ! -SNAP was for testing, not for production. Use releases for long term bases if you want to install freeze & forget. Could be no one else even runs your ancient particular version :-) If you'r running such seriously ancient software, maybe you'r also running ancient hardware ? eg I have a loose co-axial 10M ethernet connection somewhere, periodically makes my internal net go `sticky' (Well yes, Ive got a 100 Switch, but it's got a loud fan :-) There's tools in /usr/ports/sysutils/ for net performance & packet sniffing etc. Also in 4.9-RELEASE & 5.2-RELEASE there's man netstat The netstat command symbolically displays the contents of various net- work-related data structures. man sysstat - Julian Stacey. Unix,C,Net & Sys. Eng. Consultant, Munich. http://berklix.com Mail in Ascii, Html dumped as Spam. Ihr Rauch = mein allergischer Kopfschmerz. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[CFR] OpenSSL ENGINE fix
Hi,
The stunnel port had been badly broken on -CURRENT for some time, and
today I seem to have tracked it down. There is a problem in
OpenSSL's ENGINE code, which seems to depend on realloc()'s initializing
unused memory with zeroes. Since this is certainly not true with
malloc's 'J' option, the ENGINE code never actually runs out of RAND
routines to look for, and dumps core on attempting to dereference a
structure at 0xd0d0d0d0.
The following simple patch seems to fix this particular problem, but I
think there are others lurking close beneath the surface. When I built
stunnel with this patch, it did not immediately segfault on
initialization, but it did later, when it attempted to get a couple of
random bytes in order to actually establish an SSL connection. A quick
examination shows that the ENGINE code had "successfully" loaded and
initialized all built-in engines and then tried to use the last one
loaded - in this case, the 4758cca one - which promptly invoked a
function pointed to by the static randomNumberGenerate variable, which,
as you may have guessed by this point, held a NULL value. Apparently,
something else is rotten in ENGINE initialization land, and (at least)
the 4758cca driver cannot properly detect that it has not properly
detected its hardware :(
Still, I think the attached patch should be committed and MT5'd before
5.3-RELEASE, to fix at least one of the flaws. Also here is a simple C
program that illustrates the problem - just compile it and run it on a
stock 5.x or 6.x system, and I'd be, well, somewhat surprised if it gets
to the printf's at all.
So.. the patch itself:
Index: src/crypto/openssl/crypto/engine/eng_table.c
===
RCS file: /home/ncvs/src/crypto/openssl/crypto/engine/eng_table.c,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 eng_table.c
--- src/crypto/openssl/crypto/engine/eng_table.c28 Jan 2003 21:22:30 -
1.1.1.1
+++ src/crypto/openssl/crypto/engine/eng_table.c2 Sep 2004 14:40:52 -
@@ -287,7 +287,7 @@
}
trynext:
ret = sk_ENGINE_value(fnd->sk, loop++);
- if(!ret)
+ if(!ret || loop == sk_ENGINE_num(fnd->sk))
{
#ifdef ENGINE_TABLE_DEBUG
fprintf(stderr, "engine_table_dbg: %s:%d, nid=%d, no "
And the test program:
#include
#include
#include
#include /* for CRYPTO_* and SSLeay_version */
#include
#if SSLEAY_VERSION_NUMBER >= 0x00907000L
#include
#else
#error weird openssl version
#endif
int main(void)
{
ENGINE_load_builtin_engines();
ENGINE_register_all_complete();
if (RAND_status()) {
printf("RAND_status said ok\n");
} else {
printf("RAND_status kinda sorta failed\n");
}
return (0);
}
G'luck,
Peter
--
Peter Pentchev [EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED]
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553
If there were no counterfactuals, this sentence would not have been paradoxical.
pgpRwpYouoP8f.pgp
Description: PGP signature
Re: [CFR] OpenSSL ENGINE fix
On Thu, Sep 02, 2004 at 07:03:00PM +0300, Peter Pentchev wrote:
> Hi,
>
> The stunnel port had been badly broken on -CURRENT for some time, and
> today I seem to have tracked it down. There is a problem in
> OpenSSL's ENGINE code, which seems to depend on realloc()'s initializing
> unused memory with zeroes. Since this is certainly not true with
> malloc's 'J' option, the ENGINE code never actually runs out of RAND
> routines to look for, and dumps core on attempting to dereference a
> structure at 0xd0d0d0d0.
>
> The following simple patch seems to fix this particular problem, but I
> think there are others lurking close beneath the surface. When I built
> stunnel with this patch, it did not immediately segfault on
> initialization, but it did later, when it attempted to get a couple of
> random bytes in order to actually establish an SSL connection. A quick
> examination shows that the ENGINE code had "successfully" loaded and
> initialized all built-in engines and then tried to use the last one
> loaded - in this case, the 4758cca one - which promptly invoked a
> function pointed to by the static randomNumberGenerate variable, which,
> as you may have guessed by this point, held a NULL value. Apparently,
> something else is rotten in ENGINE initialization land, and (at least)
> the 4758cca driver cannot properly detect that it has not properly
> detected its hardware :(
Oh, and of course, here's a program that demonstrates the null pointer
problem after the eng_table.c patch is applied:
#include
#include
#include
#include /* for CRYPTO_* and SSLeay_version */
#include
#if SSLEAY_VERSION_NUMBER >= 0x00907000L
#include
#else
#error weird openssl version
#endif
int main(void)
{
unsigned char buf[256];
int ret;
ENGINE_load_builtin_engines();
ENGINE_register_all_complete();
if (RAND_status()) {
printf("RAND_status said ok\n");
} else {
printf("RAND_status kinda sorta failed\n");
}
ret = RAND_pseudo_bytes(buf, sizeof(buf) / 2);
printf("RAND_pseudo_bytes() returned %d\n", ret);
return (0);
}
G'luck,
Peter
--
Peter Pentchev [EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED]
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553
If I had finished this sentence,
pgpW2tc4dntHa.pgp
Description: PGP signature
5.2.1 netcard performance em slow vs fxp
Just been testing a em ( gE ) netcard vs a old fxp in the same machine ( Dual PIII 800 ) and the em can't even match the fxp for throughput. Looking at sysstat the interrupt rate on em is virtually double that of the fxp 11K vs 5k. When testing with straight ftp from a 2.5Ghz P4 windows client using an em connected with a crossover cable I get: em = 8->9MB/s fxp = 10->11MB/s Tweaking the em to use jumbo packets I can push that to 14MB/s before the cpu on the P3 saturates. This is mainly interrupt and system time not user ( proftpd ) time. Unfortunately this doesn't really help because I'm after increased through put to multiple 100Mb clients not to one gE client hence jumbo frames is not an option. Is their anyway to tweak the em driver to give better performance. I would at least expect as good as the fxp if not substantially better. Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.2.1 netcard performance em slow vs fxp
Just been testing a em ( gE ) netcard vs a old fxp in the same machine ( Dual PIII 800 ) and the em can't even match the fxp for throughput. Looking at sysstat the interrupt rate on em is virtually double that of the fxp 11K vs 5k. When testing with straight ftp from a 2.5Ghz P4 windows client using an em connected with a crossover cable I get: em = 8->9MB/s fxp = 10->11MB/s Tweaking the em to use jumbo packets I can push that to 14MB/s before the cpu on the P3 saturates. This is mainly interrupt and system time not user ( proftpd ) time. Unfortunately this doesn't really help because I'm after increased through put to multiple 100Mb clients not to one gE client hence jumbo frames is not an option. Is their anyway to tweak the em driver to give better performance. I would at least expect as good as the fxp if not substantially better. Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.2.1 netcard performance em slow vs fxp
Grr sorry for the double post mail server issues - Original Message - From: "Steven Hartland" <[EMAIL PROTECTED]> Just been testing a em ( gE ) netcard vs a old fxp in the same machine ( Dual PIII 800 ) and the em can't even match the fxp for throughput. This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to customize a release?
I'm looking for information on how to properly customize a FreeBSD distribution when using the "make release" framework. Specifically I need to modify some config files to default to serial console and fast baud rate, and use a custom kernel configuration (not just hack the GENERIC conf file). The documentation on the FreeBSD site covers how to build a release, but other than a few hints I'm not finding and references on the correct way to _customize_ the release. I did find a site that discusses building a release, mirroring the usr/src tree from that release directory, modifying the source, then creating a diff patch that's used on a subsequent "make release". If it works as advertised, this is somewhat helpful other than waiting an entire day for multiple release builds to finish. Is there a way to populate the build area with the source, then apply my own patches prior to running a full "make release"? I tried "make release.1" but this totally ignored my CHROOTDIR and tried to create "/R" in my root partition :-(. Also I noted that "make rerelease" updates the source from CVS which is undesirable in my case since I already have fresh source that was used to create patches, and if any of those original files changed my patches could fail. Can CVS updates be turned off for subsequent builds? Lastly, KERNCONF seems to have no relevance in "make release". How can I force a non generic kernel to be used when building the release? Chris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to customize a release?
On Thursday 02 September 2004 03:21 pm, [EMAIL PROTECTED] wrote: > I'm looking for information on how to properly customize a FreeBSD > distribution when using the "make release" framework. Specifically I need > to modify some config files to default to serial console and fast baud > rate, and use a custom kernel configuration (not just hack the GENERIC > conf file). > > The documentation on the FreeBSD site covers how to build a release, but > other than a few hints I'm not finding and references on the correct way > to _customize_ the release. I did find a site that discusses building a > release, mirroring the usr/src tree from that release directory, modifying > the source, then creating a diff patch that's used on a subsequent "make > release". If it works as advertised, this is somewhat helpful other than > waiting an entire day for multiple release builds to finish. > > Is there a way to populate the build area with the source, then apply my > own patches prior to running a full "make release"? I tried "make > release.1" but this totally ignored my CHROOTDIR and tried to create "/R" > in my root partition :-(. > > Also I noted that "make rerelease" updates the source from CVS which is > undesirable in my case since I already have fresh source that was used > to create patches, and if any of those original files changed my patches > could fail. Can CVS updates be turned off for subsequent builds? > > Lastly, KERNCONF seems to have no relevance in "make release". How can I > force a non generic kernel to be used when building the release? There is a 'KERNELS' variable that is helpful. Also, look at LOCAL_PATCHES and LOCAL_SCRIPTS as far as how to patch a release build. Note that you can include patches to src/release/Makefile in LOCAL_PATCHES if need be. :) -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to customize a release?
On Thu, Sep 02, 2004 at 03:38:26PM -0400, John Baldwin wrote: > On Thursday 02 September 2004 03:21 pm, [EMAIL PROTECTED] wrote: > > I'm looking for information on how to properly customize a FreeBSD > > distribution when using the "make release" framework. Specifically I need > > to modify some config files to default to serial console and fast baud > > rate, and use a custom kernel configuration (not just hack the GENERIC > > conf file). > > > > The documentation on the FreeBSD site covers how to build a release, but > > other than a few hints I'm not finding and references on the correct way > > to _customize_ the release. I did find a site that discusses building a > > release, mirroring the usr/src tree from that release directory, modifying > > the source, then creating a diff patch that's used on a subsequent "make > > release". If it works as advertised, this is somewhat helpful other than > > waiting an entire day for multiple release builds to finish. > > > > Is there a way to populate the build area with the source, then apply my > > own patches prior to running a full "make release"? I tried "make > > release.1" but this totally ignored my CHROOTDIR and tried to create "/R" > > in my root partition :-(. > > > > Also I noted that "make rerelease" updates the source from CVS which is > > undesirable in my case since I already have fresh source that was used > > to create patches, and if any of those original files changed my patches > > could fail. Can CVS updates be turned off for subsequent builds? > > > > Lastly, KERNCONF seems to have no relevance in "make release". How can I > > force a non generic kernel to be used when building the release? > > There is a 'KERNELS' variable that is helpful. Also, look at LOCAL_PATCHES > and LOCAL_SCRIPTS as far as how to patch a release build. Note that you can > include patches to src/release/Makefile in LOCAL_PATCHES if need be. :) > I'd say, please read the release(7) manpage. Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer pgpoiYMD5MKux.pgp Description: PGP signature
Re: How to customize a release?
John, Thanks for the quick reply. > There is a 'KERNELS' variable that is helpful. I see this in the Makefile, but if I were to use KERNELS=MYKERNEL will that prevent the other standard kernels from being built? > Also, look at LOCAL_PATCHES and LOCAL_SCRIPTS as far as how to patch a > release build. Note that you can include patches to > src/release/Makefile in LOCAL_PATCHES if need be. :) LOCAL_PATCHES is what I'm using now (waiting for build to finish to see how it worked). I was hoping for a way to populate the src tree without doing a full release so I could create the patches, then run make release only once (it took 5 hours on my devel system last time). At this point I've already done that, but for the next time I'd like to work more efficiently. BTW, I see I overlooked the RELEASENOUPDATE variable in the man page, so that answers my question about preventing CVS updates on "make rerelease". Unfortunately make rerelease didn't rebuild anything in /R/stage (I got "ftp.1 is up to date"). Am I supposed to delete the stage directories to force a rebuild, or do I need to do a full release to incorporate any minor changes? Chris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: System freeze when useing bfe (Broadcom BCM440x) driver
On Thu, Sep 02, 2004 at 03:25:07AM -0700, Genius Freak wrote: > Hello again, > > Well on the up side i'm sending this from my inspiron 1100. > It only took me how long? > I ended up useing 5.3BETA2 since that came out in the middle of my > hacking attempts on this system. > > Thanks for your advice. > > Oh and btw the freezes during sysinstall were while configuring the > X.org server( i have now learned to do this post install) and those > bug's are allready known so i didn't bother reporting them. > The X config stuff was thrown out of CURRENT and RELENG_5 during the last days, so this won't be a problem anymore... ;-) - Christian -- Christian Brueffer [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D pgpD2xg4GaLrI.pgp Description: PGP signature
Re: How to customize a release?
> I'd say, please read the release(7) manpage. Ruslan, I appreciate the tip, but I've read all available information I could find including the man pages. The underlying problem here is there is a lack of information on the inner workings of the release framework. The subject matter is "here's how we make a release for FreeBSD", but there's no "how-to" incorporate your own src changes and "roll your own". I was 14 pages into google.com/bsd before I found this : http://alumni.cse.ucsc.edu/~brucem/fbsd_sysgen.htm#make_dist see "How do I add custom modifications to the release I build?" While it sounds like it should work, I question whether this is the most efficient way to accomplish this, and that is why I've turned to the freebsd-hackers list. Using the above I have to run "make release" twice (at 5 hours each currently) to accomplish my changes when it seems reasonable that I should be able to : CVS the source Apply Patches make release make rerelease appears as if it should be able to suck in minor changes, but I've not had such luck so far. I understand that these lists get a lot of newbie questions, but I've spent many hours using all resources that were available (Handbook, RTFM, list archives, Google, Usenet) before posting my questions. I'm just hoping to get some further clarity from those that have already been through this. Thanks again. Chris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to customize a release?
On Thursday 02 September 2004 04:07 pm, [EMAIL PROTECTED] wrote:
> John,
> Thanks for the quick reply.
>
> > There is a 'KERNELS' variable that is helpful.
>
> I see this in the Makefile, but if I were to use KERNELS=MYKERNEL will
> that prevent the other standard kernels from being built?
>
> > Also, look at LOCAL_PATCHES and LOCAL_SCRIPTS as far as how to patch a
> > release build. Note that you can include patches to
> > src/release/Makefile in LOCAL_PATCHES if need be. :)
>
> LOCAL_PATCHES is what I'm using now (waiting for build to finish to see
> how it worked). I was hoping for a way to populate the src tree without
> doing a full release so I could create the patches, then run make release
> only once (it took 5 hours on my devel system last time). At this point
> I've already done that, but for the next time I'd like to work more
> efficiently.
>
> BTW, I see I overlooked the RELEASENOUPDATE variable in the man page, so
> that answers my question about preventing CVS updates on "make rerelease".
> Unfortunately make rerelease didn't rebuild anything in /R/stage (I got
> "ftp.1 is up to date"). Am I supposed to delete the stage directories to
> force a rebuild, or do I need to do a full release to incorporate any
> minor changes?
I just delete the files in ${CHROOTDIR}/usr/obj/usr/src/release to get it to
rebuild the targets I want.
--
John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve" = http://www.FreeBSD.org
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Right way to test SMBus? Trying to add nForce2...
Hello,
I got a new motherboard; it is MSI K7N2 Delta2 Platinum (MS-6570E-010).
http://www.msicomputer.com/product/p_spec.asp?model=K7N2_Delta2_Platinum&class=mb
Right now, I am playing with the sys/pci/amdpm.c by add IDs. It's my first
time to poke in the drivers code with no C knowledge, so please try to
speak in English. :-)
Before pciconf:
=
[EMAIL PROTECTED]:1:1: class=0x0c0500 card=0x57001462 chip=0x008410de rev=0xa1
hdr=0x00
vendor = 'NVIDIA Corporation'
device = 'nForce PCI System Management'
class= serial bus
subclass = SMBus
=
After pciconf:
=
[EMAIL PROTECTED]:1:1: class=0x0c0500 card=0x57001462 chip=0x008410de rev=0xa1
hdr=0x00
vendor = 'NVIDIA Corporation'
device = 'nForce PCI System Management'
class= serial bus
subclass = SMBus
=
But in dmesg shows:
=
amdpm0: port 0-0x1f,0xec00-0xec1f irq 23 at
device 1.1 on pci0
amdpm0: could not map i/o space
device_attach: amdpm0 attach returned 6
=
I think, I might have to change the PCI registers from 0x14 to 0x50 and/or
(not sure) 0x54, which I haven't done on this part yet. I hope, I have the
right PCI registers number (found in google). I am going to try add two
PCI registers (not sure how to do it yet) and I want to know how should I
test with SMBus to make sure it works? Thanks!
So far the patch looks like this:
=
--- sys/pci/amdpm.c.origThu Sep 2 11:24:09 2004
+++ sys/pci/amdpm.c Thu Sep 2 12:20:01 2004
@@ -73,6 +73,7 @@
/* nVidia nForce chipset */
#define AMDPM_VENDORID_NVIDIA 0x10de
#define AMDPM_DEVICEID_NF_SMB 0x01b4
+#define AMDPM_DEVICEID_NF2_SMB 0x0084
/* PCI Configuration space registers */
#define AMDPCI_PMBASE 0x58
@@ -167,7 +168,8 @@
}
if ((vid == AMDPM_VENDORID_NVIDIA) &&
- (did == AMDPM_DEVICEID_NF_SMB)) {
+ ((did == AMDPM_DEVICEID_NF_SMB) ||
+(did == AMDPM_DEVICEID_NF2_SMB))) {
device_set_desc(dev, "nForce SMBus Controller");
/*
=
Cheers,
Mezz
--
mezz7 at cox.net - mezz at FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gnome at FreeBSD.org
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to customize a release?
Hi Chris,
On Thu, Sep 02, 2004 at 04:19:18PM -0400, John Baldwin wrote:
> On Thursday 02 September 2004 04:07 pm, [EMAIL PROTECTED] wrote:
> > John,
> > Thanks for the quick reply.
> >
> > > There is a 'KERNELS' variable that is helpful.
> >
> > I see this in the Makefile, but if I were to use KERNELS=MYKERNEL will
> > that prevent the other standard kernels from being built?
> >
Let me know if you believe this is unclear and should be improved (from the
release(7) manpage):
: release.3Makes and installs the GENERIC kernel as well as any
^^^^^
: other kernels listed in KERNELS.
^^^
:
: KERNELS Specifies a list of additional kernel configura-
^
: tions to compile and install into the ``base'' dis-
: tribution. Each kernel is installed into
: /boot/ so that it can be booted from the
: loader via ``boot ''.
> > > Also, look at LOCAL_PATCHES and LOCAL_SCRIPTS as far as how to patch a
> > > release build. Note that you can include patches to
> > > src/release/Makefile in LOCAL_PATCHES if need be. :)
> >
> > LOCAL_PATCHES is what I'm using now (waiting for build to finish to see
> > how it worked). I was hoping for a way to populate the src tree without
> > doing a full release so I could create the patches, then run make release
> > only once (it took 5 hours on my devel system last time). At this point
> > I've already done that, but for the next time I'd like to work more
> > efficiently.
> >
What do you mean, I don't get it?
> > BTW, I see I overlooked the RELEASENOUPDATE variable in the man page, so
> > that answers my question about preventing CVS updates on "make rerelease".
> > Unfortunately make rerelease didn't rebuild anything in /R/stage (I got
> > "ftp.1 is up to date"). Am I supposed to delete the stage directories to
> > force a rebuild, or do I need to do a full release to incorporate any
> > minor changes?
>
> I just delete the files in ${CHROOTDIR}/usr/obj/usr/src/release to get it to
> rebuild the targets I want.
>
So do I.
One more hint: suppose you want to rebuild world inside the chroot. Then
you have two options with "make rerelease": one is to *not* use RELEASENOUPDATE
-- it will then use CVS to update your source tree (beware this doesn't work
if you ran "make release" with EXTSRCDIR). Another is to run "make rerelease"
with RELEASENOUPDATE and remove ${CHROOTDIR}/tmp/.world_done before doing it.
In any case, buildworld will be rebuilt with -DNOCLEAN, which should be fast.
To force rebuild of other stages, you need to remove particular files under
${CHROOTDIR}/usr/obj/usr/src/release/ (as has been already mentioned).
Cheers,
--
Ruslan Ermilov
[EMAIL PROTECTED]
FreeBSD committer
pgpKqVKAv3V9I.pgp
Description: PGP signature
