pkg_version and no origin found == SEGFAULT
It seems when pkg_version hits an installed port that has no origin found it segfaults. I have found other people to verify that it segfaults for them too. DWhite seems to think that it may be pointer corruption in libc, specifically snprintf, fopen, strlcpy or strncpy Here is the backtrace Program received signal SIGSEGV, Segmentation fault. 0x28204e57 in strlcpy () from /usr/lib/libc.so.5 (gdb) bt #0 0x28204e57 in strlcpy () from /usr/lib/libc.so.5 #1 0x0804a003 in pkg_do (pkg=0x0) at /usr/src/usr.sbin/pkg_install/version/perform.c:169 #2 0x08049bfc in pkg_perform (indexarg=0x0) at /usr/src/usr.sbin/pkg_install/version/perform.c:71 #3 0x08049a45 in main (argc=1, argv=0xbfbffc0c) at /usr/src/usr.sbin/pkg_install/version/main.c:79 #4 0x08049879 in _start () Any help or guidance would be appreciated. It does seem that portupgrade -f the ports that cause this problem fixes it because the origin is created. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: pkg_version and no origin found == SEGFAULT
Have you checked your /var/db/pkg/port_name/+CONTENTS files? For some reason some ports on my relatively stale -CURRENT box had these files truncated to zero length, and this caused some package tools (namely pkg_version) to crash. The procedure to read plist simply returns with all plist struct members set to zero without indicating any errors when CONTENTS file is empty, and the pkg_version crashes trying to defererence null 'origin' pointer. This is exactly the problem I'm seeing and would explain why portupgrade -f fixes the problem for the port that causes the segfault. Shouldn't pkg_version handle this a little more gracefully? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: pkg_version and no origin found == SEGFAULT
Can someone with a src commit bit please do the honours... Cool, thanks for the quick fix! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
cbb module build failure
mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/dev -I@/. ./include -I/usr/obj/usr/src/i386/usr/include /usr/src/sys/modules/pccard/../.. /dev/pccard/pccard.c /usr/src/sys/modules/pccard/../../dev/pccard/pccard_cis.c / usr/src/sys/modules/pccard/../../dev/pccard/pccard_cis_quirks.c === cbb @ - /usr/src/sys machine - /usr/src/sys/i386/include make: don't know how to make pccbb.c. Stop *** Error code 2 -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: BTX Loader issue with today current
GTX Loader 1.0 BTX Version 0.00 Error: Client format not supported Anyone have any ideas to be able to boot. I'm seeing this as well. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: /boot/loader problem
On Fri, Aug 30, 2002 at 11:48:52AM -0700, walt wrote: After make world/kernel yesterday I get this error from the bootloader: BTX version =0.00 (instead of 1.01) Client format not supported. and then it hangs. I have to do a hard reset to reboot at that point. I can still boot with /boot/loader.old which works fine. I see that today's /boot/loader is 10kb smaller(166960) than loader.old(176128). I can't seem to get far enough to pick my /boot/loader -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2.1-pre imported
On Sun, Sep 01, 2002 at 05:58:46PM -0400, Alexander Kabaev wrote: GCC 3.2.1-pre is now in the tree. Please let me know if you see any problems recompiling your world/kernel. I have completed a world and kernel, just upgrading all my ports with portupgrade -a -f now, we'll see how that goes. Remember to recompile your C++ ports. GCC 3.2 is not binary compatible with 3.1. If this works out would it be a good idea to get this new gcc version on the port build clusters for -current so we can get to work on making sure all the ports work with the new compiler? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2.1-pre imported
On Sun, Sep 01, 2002 at 04:46:18PM -0700, Kris Kennaway wrote: On Sun, Sep 01, 2002 at 06:33:05PM -0500, David W. Chapman Jr. wrote: Remember to recompile your C++ ports. GCC 3.2 is not binary compatible with 3.1. If this works out would it be a good idea to get this new gcc version on the port build clusters for -current so we can get to work on making sure all the ports work with the new compiler? I'll be doing a new bento run ASAP. I will look at the logs when its done and see where I can help out. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
Of course. And being accused of 'trolling' is also a learning experience. I would have to agree with your sarcasm, seems like there is a big troll hunt and everyone is being accused. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: internal compiler error with gcc 3.2
On Mon, Sep 02, 2002 at 09:01:31AM -0700, Steve Kargl wrote: On Mon, Sep 02, 2002 at 08:52:56AM -0700, Steve Kargl wrote: To test gcc 3.2, I've been updating all of my installed ports. It appears gcc 3.2 is having problems with libiconv-1.8_1. cc -I. -I. -I../include -I./../include -I/usr/local/include -O -pipe\ -march=athlon -c ./iconv.c -fPIC -DPIC -o .libs/iconv.lo ^ This appears to be the cause of the problem. If I comment out CPUTYPE?=athlon in /etc/make.conf, then libiconv compiles without a problem. Yes, seems to be any CPUTYPE as far as I can tell -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: installworld broken
Strange, I just did a make buildworld ... mergermaster sequence and I did not need the three utilities you mention. Why is that strange? You're talking about everything up to but not including installworld. Warner's talking about installworld. :-) Sigh. I said 'make buildworld ... mergemaster sequence'. I assume people running -current would understand the use of ... and the word sequence to mean Some build just do buildworld to make sure it compiles not needing to install it. Just for clarification in the future, saying make world sequence will get your exact point across as well as saying make kernel instead of make buildkernel -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: A different light, perhaps.
On Mon, Sep 23, 2002 at 10:11:56PM -0400, Carl Schmidt wrote: cheerleading There seems to be many complaints of things being broken. Maybe I'm just lucky and never cvsup when things are broken. I have encountered -no- errors over the past month when building world and kernel. So anyway to add to that I'd just like to report on today's build so as to balance things out. After running cvsup at about 5PM EDT (September 23, 2002 -- using cvsup3) and running a full build I am happy to report that everything worked fine. No war stories to speak of. I've not had any problems either and I usually build once or twice a week. Now if only my laptop would stop overheating whenever I run FreeBSD on it. Does the fan not turn on? Are you using acpi? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Old port recompiles needed (Re: Unknown symbol __sF)
On Sun, Oct 13, 2002 at 11:29:32PM -0400, Carl Schmidt wrote: On Mon, Oct 14, 2002 at 11:43:20AM +0900, Makoto Matsushita wrote: tlambert2 That's 3.4 hours saved on a 28.8K modem download time, tlambert2 overall... a 14% reduction in size. The percentage doesn't matter. If ISO image is compressed, user who downloads the image may de-compress that image to burn (I don't know any about the burner softwares which support compressed ISO image). What's happen if there is no space to make de-compressed image on a HDD? I do not follow this. If the user can not fit a non-compressed image on their drive then they certainly will not be downloading a non- compressed image nor a compressed image hence rendering this whole discussion moot for that user...it seems so to me at least. Maybe I am not seeing something? The temporary space required to do the decompression is what I am assuming is being reference, although I'm not sure how accurate that argument is. Whether we think the size is too large for dial-up or not people will still download it. And 200MB is absolutely nothing compared to what people put up with for full-size distribution ISOs. You could argue that not everyone has gzip (I would assume primarily a Windows user). As far as I know there is a DOS version of gzip. This would be where you might need both types of images (compressed and not compressed), and that is something up to the snapshots people. Winzip supports tar and gz, winrar supports bzip2 One might argue that Mr. Lambert is simply speculating that anyone has a 28.8k connection anymore. What are the odds that everyone fits this: a: they live close enough to a provider to get broadband (see 'b'), I did not think distance was a requirement for cable modem, but I do agree with your logic that not everyone has broadband. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Request: remove ssh1 fallback
Check the mailing list archives around 4.3-RELEASE, when it was discovered that /etc/pam.conf didn't get ssh lines added to it on upgrades, and people were getting locked out of boxes left and right (predates other entries). Changing behaviour on an upgrade, without the user's consent, is a bad thing (note: *consent*, not *knowledge*: it's not up to the user to know about everything some programmer has diddled into non-operability in the two years since FreeBSD 5.x was branched). Isn't that what UPDATING is for and wouldn't between 4.x and 5.x be better than 5.x and 5.x+n? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
DRI
Anyone know if -current supports Direct Rendering Infrastructure? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ICH2-M IDE controller
I think there are a few chips like that, that cannot do ATA100, but only vaguely remember hearing about it. - Original Message - From: "Benjamin Close" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, March 24, 2001 6:49 PM Subject: ICH2-M IDE controller Hi All, Is anyone looking at supporting the Intel ICH2-M IDE controller? This controller is basically the same as the ICH2 controller except it has extra powermanagment features as it's the for portable computers (hence the M=mobile). I'm currently using the attached patch which runs flawlessly on my laptop. However, I'm just an amature code hacker and hence can't guarentee I haven't missed something between the chipsets. The other question I have is why in ata-dma.c is there the fall through to the ICH chipset? It seems to prevent any drive actually using ATA100/UDMA5 features. Cheers, -- * Benjamin Close To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /etc/exports: 192.168.5 = 192.168.0.5
From a pure logic point of view here's something that might help you understand it the 4 octets are broken down into binary and then combined without the decimal point. when whatever libraries are doing this, the first octec(192) is converted to binary. Then there is probably some sort of if statement that says if there is only one more octet to process make it the last octet. The reason for this is so you can enter in ip addresses like 3232236800 which is another way of looking at 192.168.5.0, if it wasn't processed like this, it might try to ping 3232236800.0.0.0 If I've caused any more confusion than help, let me know and I can email you in private and help better explain. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /etc/exports: 192.168.5 = 192.168.0.5
Its always been working in the correct way for stable and currently is right now. - Original Message - From: "Daniel C. Sobral" [EMAIL PROTECTED] To: "Leif Neland" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, March 25, 2001 6:52 AM Subject: Re: /etc/exports: 192.168.5 = 192.168.0.5 Leif Neland wrote: showmount -e showed 192.168.5 was being interpreted as 192.168.0.5 This is the correct interpretation. Changing -network to 192.168.5.0 fixed it, naturally, but the 192.168.5 used to work. It was broken, then. :-) So an unlisted bug was fixed :-) Quick! Open a PR about -stable! :-) -- Daniel C. Sobral (8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] all your kernels arpanic: blockable sleep lock (sleep mutex) Giant @ ../../kern/kern_sig.c:153 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /etc/exports: 192.168.5 = 192.168.0.5
192.168.5 should be interpreted as 192.168.0.5 in host address context, but as 192.168.5.0 in network address context. (Such network address context is well seen in sentences such as "10/8", "192.168/16".) The only problem I see with 10/8 is that when broken down into binary they do not match 10.0.0.0/8 1010 and just 10 1010 the significance of one "octet" is that the above(10.0.0.0) can be written in this form as 167772160 which doesn't equal 10 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ISO image available?
the only difference I know of between the 905b and c is wake on lan. I thought I heard something about a 905c II that had problems with freebsd, but I don't remember much more. - Original Message - From: "Lars Eggert" [EMAIL PROTECTED] To: "Norbert Koch" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, April 12, 2001 2:14 PM Subject: Re: ISO image available? Norbert Koch wrote: The 5.0-20010410-CURRENT installer doesn't recognize my "3Com 3c905C-TX Fast Etherlink XL", which in 4.2 is handled by the xl driver. I guess the netinstall will have to wait... Uh, is there so much difference between 3c905(B|C)-TX? I ask, because I have xl0: 3Com 3c905B-TX Fast Etherlink XL port 0xd000-0xd07f mem 0xdd00-0xdd7f irq 11 at device 12.0 on pci0 I don't know. :-) All I can say is that it is recognized fine under 4.2. -- Lars Eggert [EMAIL PROTECTED] Information Sciences Institute http://www.isi.edu/larse/University of Southern California To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kernel core
I'm gettind kernel core dumps in the weirdest places with a -current from early today. One place it coredumps is when I run "chsh", another is during a certain part of make install on XFree86-4, the same place every time. I can get some more details if this is an unknown bug. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel core
Here's an exact error message because I'm sure I wrongly diagnosed it. Fatal trap 12: pagefault while in kernel mode fault code = supervisor read, page not present kernel: type 12 trap, code = 0 stopped atffs_valloc+0x8eicmpb$0,0(%edi,%eax,1) I can still try to play around with cvs dates if needed, just give me a clue on how far back I should start. Its been over a month since I've cvsuped -current besides this morning. - Original Message - From: "John Baldwin" [EMAIL PROTECTED] To: "David W. Chapman Jr." [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, April 20, 2001 9:08 PM Subject: RE: kernel core On 21-Apr-01 David W. Chapman Jr. wrote: I'm gettind kernel core dumps in the weirdest places with a -current from early today. One place it coredumps is when I run "chsh", another is during a certain part of make install on XFree86-4, the same place every time. I can get some more details if this is an unknown bug. Is it always a sig 11? Can you cvsup or cvs update to specific dates to track down which commit started causing these as well? -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel core
I just tried to do an installkernel on a new kernel I built and I got the same error except the last line changed to stopped atffs_dirpref+0x210movzbl0(%ECX,%EAX,1),%EAX Do I have any hope at recovering from this or should I start again with 4 and upgrade to -current. I'm assuming is a problem with the kernel and without being able to update the kernel and install a new one, I don't think I can fix it. - Original Message - From: "David W. Chapman Jr." [EMAIL PROTECTED] To: "John Baldwin" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, April 20, 2001 9:45 PM Subject: Re: kernel core Here's an exact error message because I'm sure I wrongly diagnosed it. Fatal trap 12: pagefault while in kernel mode fault code = supervisor read, page not present kernel: type 12 trap, code = 0 stopped atffs_valloc+0x8eicmpb$0,0(%edi,%eax,1) I can still try to play around with cvs dates if needed, just give me a clue on how far back I should start. Its been over a month since I've cvsuped -current besides this morning. - Original Message - From: "John Baldwin" [EMAIL PROTECTED] To: "David W. Chapman Jr." [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, April 20, 2001 9:08 PM Subject: RE: kernel core On 21-Apr-01 David W. Chapman Jr. wrote: I'm gettind kernel core dumps in the weirdest places with a -current from early today. One place it coredumps is when I run "chsh", another is during a certain part of make install on XFree86-4, the same place every time. I can get some more details if this is an unknown bug. Is it always a sig 11? Can you cvsup or cvs update to specific dates to track down which commit started causing these as well? -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! bad bug in -current.
It was almost like that dirpref problem I ran into a few weeks ago, I upgraded from -stable to -current and I had to reinstall because of it, but this usually doesn't happen. - Original Message - From: Jordan Hubbard [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, May 01, 2001 6:56 PM Subject: Re: HEADS UP! bad bug in -current. Say, FreeBSD is usually pretty safe, even in CURRENT. Has something near this magnitude of Really Bad Stuffage snuck into the codebase before? No, it's not common, and it generally takes a Dane swinging something sharp to inflict quite this much damage on our user base. ;-) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Linux_Base port work around for Current?
I am installing current on a new box and I need jkd. That basically means linux emulation. I haven't been able to build it for some time on current. I have used the submitted PR to upgrade it to 7.? and it has worked except I have problems with all other ports that need linux_base. Right now the only solution is the upgrade that I see. Three questions: Does anyone have a better way? Has the PR/patch for ports been changed in the last few weeks? Is there a chance that it will be committed shortly? If I remember, it has been there for a long time. It will stay there until I can upgrade the rest of the Linux ports to work with it, and its too big of a job for me alone. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: usr.sbin/pim6[sd]d will be removed soon.
I wouldn't mind, but what exactly does pim do and do you need both pim6dd
and pim6sd?
- Original Message -
From: Hajimu UMEMOTO [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Saturday, June 02, 2001 11:38 AM
Subject: usr.sbin/pim6[sd]d will be removed soon.
Hi,
I heared from itojun that usr.sbin/pim6[sd]d has non-BSD license and
does not allow fee-based redistribution. So, I will remove them from
the tree soon. NetBSD was already done.
Could someone please make them ports? ftp.kame.net:~ftp/pub/kame/misc
has pim6[sd]-*.tar.gz.
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
[EMAIL PROTECTED] [EMAIL PROTECTED] ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
devfs
If I'm using devfs on -current, can I erase the contents of my /dev before devfs is mounted to save space? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
kde22 current
I don't know if this helps, I tried gdb'ing through the lt-meinproc.core that is produced when trying to compile kde22 and got this. I'm not a programmer so hopefully someone can point me in the right direction on this. It appears to only be an issue on -current and new version of -current. warning: Can't set a watchpoint on a core file. warning: Can't set a watchpoint on a core file. Program received signal SIGSEGV, Segmentation fault. 0x28857740 in QCString::resize () from /usr/X11R6/lib/libqt2.so.4 -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kde22 current
On Sat, Aug 18, 2001 at 11:05:09PM -0700, Alex Zepeda wrote: warning: Can't set a watchpoint on a core file. warning: Can't set a watchpoint on a core file. Program received signal SIGSEGV, Segmentation fault. 0x28857740 in QCString::resize () from /usr/X11R6/lib/libqt2.so.4 What application is this from? I believe it is from meinproc -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: devfs
On Sun, Aug 19, 2001 at 07:50:31PM -0400, Brandon D. Valentine wrote: On Sat, 18 Aug 2001, David W. Chapman Jr. wrote: If I'm using devfs on -current, can I erase the contents of my /dev before devfs is mounted to save space? What space are you planning to save? You might free up some inodes but according to my 4.4-PRERELEASE box: [bandix@leto /dev]% du -sh . 58K. Hrm, mine said 5.5M. I did say this machine had been around since 2.2.8, right? I still had raw devices in there I believe. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: devfs
On Mon, Aug 20, 2001 at 02:05:06AM -0400, Brandon D. Valentine wrote: On Sun, 19 Aug 2001, Kris Kennaway wrote: Devices are just inodes..you shouldn't have anything in /dev other than MAKEDEV, the fd/ subdirectory and a whole bunch of device nodes. You probably have some other file in there which was accidentally created by something like # verbosecommand /dev/nlul The following command should reveal the culprit: du -h /dev/* | grep -v 0B The only problem is devfs is mounted and I can't seem to get around that. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: devfs
On Mon, Aug 20, 2001 at 11:17:42AM -0400, Brandon D. Valentine wrote: On Mon, 20 Aug 2001, David W. Chapman Jr. wrote: The only problem is devfs is mounted and I can't seem to get around that. I haven't had much time lately to fool with my -CURRENT box but it seems that booting singleuser oughta help? Already tried that, still mounts devfs immediately. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Disk I/O problems with -current.
On Tue, Aug 21, 2001 at 12:54:35PM -0700, Kris Kennaway wrote: On Mon, Aug 20, 2001 at 11:52:07AM +0100, Josef Karthauser wrote: I'm having strange problems with -current on a laptop with 64mb of memory. Periodically things go strange [tm]. Because of the lack of memory I'm using a fair amount of swap. Everything runs smoothly up until a point, which seems to depend upon not running too many large processes for too long. Then the file system grinds to a halt for seconds at a time. Some processes run, and others just hang. Yes, I see almost exactly the same thing (except that I haven't noticed any processes which stay running during the freeze -- things like keyboard and mouse activity in X or the console always freeze). Mine could well be swap related too, though I have 128MB of memory. I really think developers should be made to run -current on an old, slow, crippled machines so they notice this kind of thing which would be lost in the noise on their fast machines :-) Hrm, I'm even seeing this on my thunderbird 1100 with 256mb ram. Sometimes I even get a Bus I/O error when I try to do too much when this happens. I have all kernel debugging options turned off, but I can turn them on if this is something you can debug with gdb. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Disk I/O problems with -current.
On Tue, Aug 21, 2001 at 05:42:55PM -0500, Jim Bryant wrote: Kris Kennaway wrote: On Mon, Aug 20, 2001 at 11:52:07AM +0100, Josef Karthauser wrote: I'm having strange problems with -current on a laptop with 64mb of memory. Periodically things go strange [tm]. Because of the lack of memory I'm using a fair amount of swap. Everything runs smoothly up until a point, which seems to depend upon not running too many large processes for too long. Then the file system grinds to a halt for seconds at a time. Some processes run, and others just hang. Yes, I see almost exactly the same thing (except that I haven't noticed any processes which stay running during the freeze -- things like keyboard and mouse activity in X or the console always freeze). Mine could well be swap related too, though I have 128MB of memory. I really think developers should be made to run -current on an old, slow, crippled machines so they notice this kind of thing which would be lost in the noise on their fast machines :-) I've also noticed this... Sunday and yesterday, I deleted ALL installed -ports and -packages thinking that the meinproc issue with kde-2.2 was being caused by conflicts in libraries and/or include files [it's not either] on this system which has had about three years since a good clean scrubbing... While I was busy recompiling the basics, I noted that the disk activity would stop, and the console become non-responsive, yet there was no panic or other kernel message. This was happening consistantly for about 12 hours or so, and I had to back down from 5 or 6 parallel -ports compiles to one and two in parallel. I also have noted that when switching VTY [by hand, or when exiting X] the system would panic on mwrite and give message about the possibility of buffers being wierded out POSSIBLY [the message was a question]. I also noted on several instances that the freezes would occur when there is heavy disk and CPU activity combined with network access [this may or may not be a contributing factor, I don't know] such as fetching a distribution file. I have also noticed extreme slowness when disk activity occurs. top will show almost no CPU being used, but when there is something being copied or moved, everything becomes REALLY sluggish. This has only been noticed in kernels of the last month or so. 3/4th's of these problems describe ones I am having. I have a Gigabyte 7ZX w/ thunderbird 1100 256mb ram. 3c905b. I'm running -current as of 1.5 weeks ago. nvidia geforce DDR and sb 128(onboard). My drives are IDE w/ 1 cdrom and 1 scsi burner. Tyan S1696-DLUA MoBo, 2 ATAPI busses in use 20G-pri-master, 12G-pri-slave, HP burner sec-master, 2 SCSI-UW busses in use ST15150W dedicated bus, NEC CD-ROM and HP DDS2 on second bus, LinkSys [dc0] 10/100 ethernet, DEC DEFPA SAS UTP-PMD, SB-Live!/Value, Hauppauge WinTV/Theatre. dual P-II/333's, 512Megs SDRAM. Matrox MGA-G200 AGP. USB CompactFlash/SmartMedia reader. -CURRENT as of 3am CDT today. I noticed a lot of changes last night, especially in the vm code, and I'll wait and see if this fixes anything I've noted... Man them cvsup servers were slow this morning! Please let me know, I'd definitely make world if this fixes those problems. I'd be more than willing to test any patches anyone can think to send me. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: diskcheckd is poo
On Thu, Aug 23, 2001 at 10:07:15PM +0200, Søren Schmidt wrote: It seems David O'Brien wrote: diskcheckd is very annoying. Many doubt its usefulness in detecting errors before it is too late. It thinks 40% of my disks are bad (which I don't). I've turned it off, I know many that have. I would like to remove it from the base system and put it in ports. I really don't see what justifies keeping it in /usr/src. YES! If someone could roll a tarball for me, I could atleast make the skeleton for the port if not finish it off. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
unknown PNP hardware
I'm running -current as of an hour ago. I've gotten this since I've been running 4.2-stable, any ideas on how I can find out what it belongs to? unknown: PNP0303 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0401 can't assign resources unknown: PNP0700 can't assign resources unknown: PNP0f13 can't assign resources dwcjr# pnpinfo Checking for Plug-n-Play devices... No Plug-n-Play devices were found dwcjr# pciconf -l hostb0@pci0:0:0:class=0x06 card=0x chip=0x03051106 rev=0x03 hdr=0x00 pcib1@pci0:1:0: class=0x060400 card=0x0080 chip=0x83051106 rev=0x00 hdr=0x01 isab0@pci0:7:0: class=0x060100 card=0x06861106 chip=0x06861106 rev=0x22 hdr=0x00 atapci0@pci0:7:1: class=0x01018a card=0x chip=0x05711106 rev=0x10 hdr=0x00 uhci0@pci0:7:2: class=0x0c0300 card=0x12340925 chip=0x30381106 rev=0x10 hdr=0x00 uhci1@pci0:7:3: class=0x0c0300 card=0x12340925 chip=0x30381106 rev=0x10 hdr=0x00 none0@pci0:7:4: class=0x0c0500 card=0x chip=0x30571106 rev=0x30 hdr=0x00 ahc0@pci0:12:0: class=0x01 card=0x78879004 chip=0x87789004 rev=0x01 hdr=0x00 bktr0@pci0:13:0:class=0x04 card=0x00011002 chip=0x036e109e rev=0x02 hdr=0x00 none1@pci0:13:1:class=0x048000 card=0x00011002 chip=0x0878109e rev=0x02 hdr=0x00 pcm0@pci0:14:0: class=0x040100 card=0x20601458 chip=0x13711274 rev=0x07 hdr=0x00 xl0@pci0:15:0: class=0x02 card=0x905510b7 chip=0x905510b7 rev=0x30 hdr=0x00 none2@pci1:0:0: class=0x03 card=0x400a1043 chip=0x010110de rev=0x10 hdr=0x00 Let me know if I need to provide anything else. Also I get this bktr0: Warning - card vendor 0x1002 (model 0x0001) unknown. this is an ATI TV Wonder. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: diskcheckd is poo
On Thu, Aug 23, 2001 at 01:57:15PM -0700, David O'Brien wrote: On Thu, Aug 23, 2001 at 03:11:00PM -0500, David W. Chapman Jr. wrote: If someone could roll a tarball for me, I could atleast make the skeleton for the port if not finish it off. We should just repo copy it to ports. See how I do the setcdboot port. Here is a shar of what I am working on. Comments patches and complaints are appreciated. I just have to make the rc script for it to startup on boot. http://people.freebsd.org/~dwcjr/diskcheckd.shar -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: diskcheckd is poo
On Thu, Aug 23, 2001 at 05:51:41PM -0500, David W. Chapman Jr. wrote: Here is a shar of what I am working on. Comments patches and complaints are appreciated. I just have to make the rc script for it to startup on boot. http://people.freebsd.org/~dwcjr/diskcheckd.shar -- Update: I have the rc script, although it isn't too grand and I haven't tested it, everything should be there and I'm going to test it now. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: unknown PNP hardware
On Fri, Aug 24, 2001 at 01:13:36AM +0200, Salvo Bartolotta wrote: I'm running -current as of an hour ago. I've gotten this since I've been running 4.2-stable, any ideas on how I can find out what it belongs to? unknown: PNP0303 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0401 can't assign resources unknown: PNP0700 can't assign resources unknown: PNP0f13 can't assign resources This harmless message has been known for a good number of months. There is nothing to worry about. Now before someone flames both of us -- me for responding and you for not first searching the archives, where discussions about this topic took place countless times -- could you please go there and retrieve this information? :-)) By the way, you can also find freebsd posts on http://www.google.com and http://www.geocrawler.com. I have no problem with that, last time I asked this wasn't in the archives and I didn't get a response. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: diskcheckd is poo
On Fri, Aug 24, 2001 at 04:14:24PM -0700, Mike Smith wrote: If we want a surface scrubber, we ought to have a real one; it's also very, very bad in the laptop context (since it keeps waking your disks up). I have the shar of the port up at http://people.freebsd.org:~/dwcjr/diskcheckd.shar I believe. its already in the ports, I'm just awaiting a repo copy of the files from /usr/src/usr.sbin/diskcheckd into ports/sysutils/diskcheckd/files -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
diskcheckd port
I'm almost finished with the port for diskcheckd. I'm just waiting on a repo copy of the config file I forgot to include in my repo request. When it is time to change it over from src to ports in modules, I'd appreciate some help since I haven't made any src commits before. Thanks. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ports diskcheckd patch
After the repo copy of the diskcheckd.conf gets done this patch
should be the last one I need to make ports/sysutils/diskcheckd to
work properly. Any comments/problems would be appreciated. I would
especially appreciate some patches to pkg-descr for a more detailed
description if possible.
Thanks.
--
David W. Chapman Jr.
[EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net
[EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org
Index: Makefile
===
RCS file: /home/ncvs/ports/sysutils/diskcheckd/Makefile,v
retrieving revision 1.1
diff -u -r1.1 Makefile
--- Makefile2001/08/24 14:33:09 1.1
+++ Makefile2001/08/25 20:13:23
@@ -20,12 +20,21 @@
NO_WRKSUBDIR= yes
+CFLAGS+= -D_PATH_CONF='\${PREFIX}/etc\'
+
+
+.include bsd.port.pre.mk
+
+.if ${OSVERSION} 50
+BROKEN=Only runs on 5.0 or higher (-current)
+.endif
+
do-extract:
@${MKDIR} ${WRKSRC}
@(cd ${FILESDIR} pax -r -w * ${WRKSRC})
-do-build:
- cd ${WRKSRC} ${CC} ${CFLAGS} -DCONFPATH=\${PREFIX}/etc\ -o diskcheckd
diskcheckd.c
+do-patch:
+ @${PERL} -pi.fbsd -e 's|/usr/sbin|${PREFIX}/sbin|g' ${WRKSRC}/Makefile
do-install:
${INSTALL_PROGRAM} ${WRKSRC}/diskcheckd ${PREFIX}/sbin
@@ -33,4 +42,4 @@
${INSTALL_SCRIPT} ${WRKSRC}/diskcheckd.sh ${PREFIX}/etc/rc.d
${INSTALL_MAN} ${WRKSRC}/diskcheckd.8 ${PREFIX}/man/man8
-.include bsd.port.mk
+.include bsd.port.post.mk
Index: files/diskcheckd.c
===
RCS file: /home/ncvs/ports/sysutils/diskcheckd/files/diskcheckd.c,v
retrieving revision 1.4
diff -u -r1.4 diskcheckd.c
--- files/diskcheckd.c 2001/08/20 15:09:33 1.4
+++ files/diskcheckd.c 2001/08/25 20:13:23
@@ -47,7 +47,10 @@
#define DKTYPENAMES
#include sys/disklabel.h
-#define_PATH_CONF /etc/diskcheckd.conf
+#ifndef _PATH_CONF
+#define_PATH_CONF /usr/local/etc/diskcheckd.conf
+#endif
+
#define_PATH_SAVE _PATH_VARDBdiskcheckd.offsets
#defineREAD_SIZE (64 10)
Re: 3.4 - current upgrade/bootstrap problem
The procedure for going form 3.4 to -current is make your -current kernel reboot do make world make -current kernel again - Original Message - From: "Robert Schien" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, January 16, 2000 9:42 AM Subject: 3.4 - current upgrade/bootstrap problem I wanted to upgrade my 3.4 system to current. I cvsuped the current sources and did a 'make buildworld'. This went fine. Now I tried 'make installworld' . This crashed with a signal 12 error in /bin/sh. I already have used current for years. For some reason I had to install 3.4 on the machine and now I wanted to go back to current. The procedure I always used was: make buildworld make installworld reboot compiling new kernel reboot Now I have a bootstrapping problem with /bin/sh (bad system call). How can I solve this problem? TIA Robert To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
As discussed at BSDCon, the release engineers are committed to releasing a relatively stable snapshot of FreeBSD -CURRENT on or around April 1, 2002. Obviously, a lot of major components are still in progress, but a great deal of work has already been accomplished, and could benefit from the additional exposure that a polished snapshot with full package set and documentation will provide. I don't know if this is something worth making it the snapshot, but currently kde doesn't work due to binuntils update. It may work now after the most recent binutils update, but we have to recompile kde to see that I believe, andkdelibs cannot be compiled which builds kde-config which the rest of the kde meta-ports try to run. I think that last sentence is a huge run on and I by no means am trying to complain, just wondering if anyone thinks its important to make it on this snapshot. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
currently kde doesn't work due to binuntils update. It may work now after the most recent binutils update, but we have to recompile kde to see that I believe, andkdelibs cannot be compiled which builds kde-config which the rest of the kde meta-ports try to run. I think that last sentence is a huge run on and I by no means am trying to complain, just wondering if anyone thinks its important to make it on this snapshot. Hmm. My impression was that the libpng stuff had been fixed, could you confirm that KDE still doesn't build on 5.0-CURRENT? Its not related to libpng, I believe that has been fixed, but I cannot tell for sure because kde cannot be compiled under -current. I'm not the only one that is experiencing it either, here is what I was told by Alan Eldridge [EMAIL PROTECTED] On Tue, Mar 05, 2002 at 05:26:27PM -0600, David W. Chapman Jr. wrote: When I try to build kdelibs2 I get the following under recent -current builds ,.deps/kextsock.pp -c kextsock.cpp -fPIC -DPIC -o .libs/kextsock.o kextsock.cpp: In method `struct kde_addrinfo * KExtendedSocketLookup::results()' : kextsock.cpp:294: implicit declaration of function `int __htons(...)' kextsock.cpp:353: implicit declaration of function `int __htonl(...)' Yes. Recent changes to netinet/in.h have made it require the inclusion of arpa/inet.h. As well, arpa/inet.h must include netinet/in.h. IOW, each of these files must #include the other in order to work correctly. As you might guess, this is a less than desirable situation. A #includes B and B #includes A is a very bad arrangement. However, unless both files are overhauled, that is what will have to happen. To say that this sucks is an understatement. I already have an open PR on the arpa/inet.h problem. Now that the reverse dependency has been made to occur, I have written portmgr@ requesting a referral to a mainline developer who can handle this mess in an expedient manner. In the meantime, you need to find every occurence of either of those files being included, and make sure the other is included as well. netinet/in.h needs to come first. Since the problem is a large one, and any change will not happen without a reasonable amount of deliberation, I suggest you submit a PR with a patch for kdelibs source tree. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
currently kde doesn't work due to binuntils update. It may work now after the most recent binutils update, but we have to recompile kde to see that I believe, andkdelibs cannot be compiled which builds kde-config which the rest of the kde meta-ports try to run. I think that last sentence is a huge run on and I by no means am trying to complain, just wondering if anyone thinks its important to make it on this snapshot. If you're referring to the problems loading libpng.so (and probably other shared libraries), I can confirm that it's been fixed now. I was curious about that, but it wasn't my main concern. Have you been able to run anything that uses OBJPRELINK? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
On Fri, Mar 08, 2002 at 11:20:35AM -0500, Will Andrews wrote: On Fri, Mar 08, 2002 at 10:17:16AM -0600, David W. Chapman Jr. wrote: currently kde doesn't work due to binuntils update. It may work now after the most recent binutils update, but we have to recompile kde to see that I believe, andkdelibs cannot be compiled which builds kde-config which the rest of the kde meta-ports try to run. I think that last sentence is a huge run on and I by no means am trying to complain, just wondering if anyone thinks its important to make it on this snapshot. Hmm. My impression was that the libpng stuff had been fixed, could you confirm that KDE still doesn't build on 5.0-CURRENT? Its not related to libpng, I believe that has been fixed, but I cannot tell for sure because kde cannot be compiled under -current. I'm not the only one that is experiencing it either, here is what I was told by Alan Eldridge [EMAIL PROTECTED] You said binutils upgrade broke KDE -- the quoted mail has nothing to do with binutils. I'm sorry for the lack of clarity in my email, if I didn't explain it the way I wanted to here is a better attempt. I cannot recompile kde due to the reasons stated in the quoted email so I'm not sure if the binutils problem has been fixed, but apparently a few people can vouch that it has. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
I'm surprised that everyone hasn't complained about world breakage from this. It has been broken for almost 2 weeks now. Everything that goes near ntohl and has WARNS = 2 fails to compile. Without WARNS, the bug is reported as above, but a bogus version of __hton* is found in the library and only optimization of hton* is broken. Very strange, I have been making world over the past few weeks (just did one yesterday) with no problems, maybe I have some stuff that it stale? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
Hmm. This should be non-fatal in any event, but which header does it include to get it's htons() and htonl() prototypes? netinet/in.h, arpa/inet.h, or sys/param.h? Yes. Recent changes to netinet/in.h have made it require the inclusion of arpa/inet.h. As well, arpa/inet.h must include netinet/in.h. IOW, each of these files must #include the other in order to work correctly. From reading all the posts, I believe the solution has been to manually modify the kde port to do this. This is almost completely bogus. I recently saw a PR of similar bogusness. This was most likely quoted from the same person who submitted the pr you read. I'm not sure how I can help you because I'm not a programmer, but I'd be happy to boot into -current and give you any information you need if there is actually a problem(I don't totally understand what it is at the moment). To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
Maybe not. I think missing prototypes might be fatal in C++. If this is the case, my new endian patch will fix this. Try compiling KDE after installing a world with the following patch applied: http://people.FreeBSD.org/~mike/patches/endian-ng3.diff I plan on committing this on Sunday. I don't know if its related to this patch, but I get this when I buildworld now cc -O -pipe -march=k6 -DDES -Wall -Wformat -Werror -Wall -Wno-uninitialized -W non-const-format -Wno-format-extra-args -Werror -c /usr/src/bin/ed/sub.c cc -O -pipe -march=k6 -DDES -Wall -Wformat -Werror -Wall -Wno-uninitialized -W non-const-format -Wno-format-extra-args -Werror -c /usr/src/bin/ed/undo.c gzip -cn /usr/src/bin/ed/ed.1 ed.1.gz cc -O -pipe -march=k6 -DDES -Wall -Wformat -Werror -Wall -Wno-uninitialized -W non-const-format -Wno-format-extra-args -Werror -static -o ed buf.o cbc.o glbl .o io.o main.o re.o sub.o undo.o -lcipher cbc.o: In function `get_keyword': cbc.o(.text+0x17d): undefined reference to `getpass' *** Error code 1 1 error *** Error code 2 -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
I don't know if its related to this patch, but I get this when I buildworld now I just did a complete buildworld + installworld with no trouble, and I then added the above patch and did another complete buildworld + installworld. I had no problems with either build. Applying the above patch got rid of about 81 warning messages in the buildworld process, and another 9 from buildkernel. Applying the patch causes no new warning messages (for me, with my kernel options, make options, on i386, etc etc). I wonder what's broken, I did a buildworld twice with the same result, I'll try to cvsup tomorrow and see if its fixed, maybe I caught it between commits. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: Be nice to -CURRENT ( 1 week Feature Slush )
I'm able to compile kdelibs now, no problem as well as QT, but when I run configure on kdebase it locks my system up. I can switch terminals but that's it. It locks up on configure when detecting QT(I believe line 5612). The first time it did this I decided that was because I need to rebuild QT, so I did that, but it still locks up. Is anyone else seeing this with a very recent -current? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: New i386 5.0 packages uploaded (and toolchain problems)
On Sat, Mar 09, 2002 at 04:35:20AM -0800, Kris Kennaway wrote: I've uploaded a new set of packages to ftp-master for -current on i386; they should be picked up by the mirrors shortly. As I mentioned in a previous mail, there were compilation problems which caused a number of ports to fail, including qt2 and gnomelibs, meaning there were no KDE or GNOME packages built (hey, at least it's a symmetric failure!). QT built fine for me with a -current as of yesterday night, and so does kdelibs, but as I posted earlier kdebase locks up the system on configure, but I believe this is known as the (Subject: Keyboard (quasi-)lockup running script) or sounds similar. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ntfs causing kernel panic
Has anyone seen mounting an NTFS drive casing a kernel panic? I'd love to give the output, but I'm not sure how to redirect the output into a file so I can post it here. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ntfs causing kernel panic
On Tue, Mar 26, 2002 at 10:08:20AM +1030, Greg 'groggy' Lehey wrote: On Monday, 25 March 2002 at 9:41:09 -0600, David W. Chapman Jr. wrote: Has anyone seen mounting an NTFS drive casing a kernel panic? I'd love to give the output, but I'm not sure how to redirect the output into a file so I can post it here. You need to take a dump and analyse it. There's some stuff in the handbook about how to do it. Unfortunately it has been fixed, but I am still planning on looking at the handbook, thanks! -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ntfs causing kernel panic
It could be this problem is a result of the loadable VFS module bug hacked/fixed in the tree this morning. Was the NTFS driver being loaded as a module, or compiled into the kernel? If a loadable module, could you try compiling it into the kernel, or updating past the fix? If already compiled in, follow the directions grog pointed at to generate useful debugging output. Ideally, a copy of the full panic message, stack trace, and information on what kernel options you linked with so that the symbol offsets are useful. The recent vfs fix has fixed it, but thanks for the tips on what information to provide. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
PAM error messages
I'm seeing this a lot on a recent 4.5-STABLE to -current upgrade, is this a problem or something I did wrong? dwcjr login: in openpam_dispatch(): pam_unix.so: no pam_sm_close_session() dwcjr login: in openpam_dispatch(): pam_unix.so: no pam_sm_open_session() -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
-current breakage
I'm getting this on a recent machine that has been upgraded from 4.5 to a -current today o over.o text.o script.o mark.o other.o delim.o sqrt.o pile.o special.o /usr/obj /usr/src/i386/usr/src/gnu/usr.bin/groff/src/preproc/eqn/../../../src/libs/libgro ff/libgroff.a make: don't know how to make neqn. Stop *** Error code 2 I'm not getting this on a machine that's been running -current for a while. I was able to do one buildworld from 4.5-STABLE to -current, but after that I keep getting this? Let me know if anyone else has seen this. About 2 hours after I started seeing this, I removed /usr/src and cvsup'd and I still get it. Any ideas? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ATA errors on recent -current
I updated to -current today and am now getting these errors ad0: READ command timeout tag=1 serv=1 - resetting ata0: resetting devices .. ad0: invalidating queued requests done -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make world stops...
On Sun, Apr 14, 2002 at 07:22:33PM +0200, Jeroen Ruigrok/asmodai wrote: -On [20020414 19:14], Matthias Schuendehuette ([EMAIL PROTECTED]) wrote: make: don't know how to make neqn. Stop *** Error code 2 I think David O`Brien fixed this by backing out a commit to make. In general, wait a couple of hours or a day before reporting a failure, since chances are good it has already been fixed. I got hit by this on a machine that had just been updated from 4.5 to -current and then I went to buildworld again and got the above. At the same time a machine that had been -current for a while didn't get this. I'm going to try to remake make as suggested. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5-current buildworld breakage?
On Thu, Apr 18, 2002 at 10:29:23AM +0900, Makoto Matsushita wrote: Using 5-current code as of Apr/17/2002 15:00:00 GMT: # pwd /usr/src/gnu/usr.bin/groff/src/preproc/eqn # ident Makefile Makefile: $FreeBSD: src/gnu/usr.bin/groff/src/preproc/eqn/Makefile,v 1.3 2002/04/11 11:06:03 ru Exp $ # make -n neqn make: don't know how to make neqn. Stop # Anybody have seen this? or it's my local problem? Yeah, your make is broken, try rebuilding make by itself and install it then try the buildworld again -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: upgrade from 4.5 to current fails
I have cvsuped my source and already made buildworld and buildkernel. But installworld failed with Signal 12 while installing chpass. You're attempting to upgrade incorrectly. Follow the directions _precisely_ and this won't happen. I just got bit by this one myself from not following instructions, for the past 2 weeks you didn't have to, you could just upgrade to 5.0 like tracking -stable. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: upgrade from 4.5 to current fails
No, for the past several months you haven't been able to installworld a -current system under a -stable kernel. That you were ever able to do that before that time is pure chance. Very strange that I did it last week then, possibly a fluke? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD security hole?
On Thu, Apr 25, 2002 at 02:56:26PM +0600, Vladimir G. Drobyshevsky wrote: Hello all! stdio kernel bug in All releases of FreeBSD up to and including 4.5-RELEASE decided to make a trivial exploit to easily get root :) CW Indeed, see security advisory FreeBSD-SA-02:23.stdio at: CW ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-02:23.stdio.asc CW Please upgrade to 4.5-p4 or 4-STABLE (April 21 or after). That's really strange - I subscribed to freebsd-security-notifications, but didn't receved that message. Or just readed it by Delete key. ;-) Anyway, thank you for your help. It was on anounce as well for future reference. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make.conf and -CURRENT
On Fri, May 10, 2002 at 06:37:11PM -0400, Jeff Ito wrote: Hello, Is the lack of /etc/defaults/make.conf intentional? an oversite? or perhaps something that I have messed up on my end? I have run cvsup/mergemaster (18:30PM EST May 10. 2002), and that changes nothing. /usr/src/etc/*/* does not contain said file, the only place it does exist is in /usr/share/examples/etc. sysctl.conf is also missing. If its not there, it doesn't get parsed. You only need make.conf if you wish to put stuff in there. same with rc.conf, except everyone puts something in rc.conf -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make.conf and -CURRENT
On Fri, May 10, 2002 at 05:40:11PM -0500, David W. Chapman Jr. wrote: On Fri, May 10, 2002 at 06:37:11PM -0400, Jeff Ito wrote: Hello, Is the lack of /etc/defaults/make.conf intentional? an oversite? or perhaps something that I have messed up on my end? I have run cvsup/mergemaster (18:30PM EST May 10. 2002), and that changes nothing. /usr/src/etc/*/* does not contain said file, the only place it does exist is in /usr/share/examples/etc. sysctl.conf is also missing. If its not there, it doesn't get parsed. You only need make.conf if you wish to put stuff in there. same with rc.conf, except everyone puts something in rc.conf N/m on the sysctl.conf I think that one exists now. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: patch to add athlon to bsd.cpu.mk
On Sat, May 11, 2002 at 01:35:05PM -0700, David O'Brien wrote:
On Sat, May 11, 2002 at 01:08:35PM -0700, Kris Kennaway wrote:
On Sat, May 11, 2002 at 12:12:16PM -0700, Steven G. Kargl wrote:
-. if ${CPUTYPE} == k7
-_CPUCFLAGS = -march=k6 # gcc doesn't support athlon yet, but it will
+. if ${CPUTYPE} == athlon
+_CPUCFLAGS = -march=athlon
AFAIK the k7 is a valid name for the athlon (marchitecture name).
Don't break backwards compatibility here.
Nope. Athlon(tm) is the correct name, just like there really isn't a
i586. I just posted a patch for review. Being the originator of
bsd.cpu.mk, I hope you review it.
So if I have an athlon-xp do I set CPUTYPE to athlon and it handles
everything for me and selects the correct one or athlon-xp?
--
David W. Chapman Jr.
[EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net
[EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
installworld problem with /usr/src/usr.bin/tip/tip
I get the following everytime I make installworld on -current ln: /usr/bin/cu: Operation not permitted *** Error code 1 To fix it I have to modify /usr/src/usr.bin/tip/tip/Makefile and remove the LINKS to cu and then all works well. Is anyone else having this problem? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: The future of perl on FreeBSD
On Mon, May 13, 2002 at 02:45:09PM -0600, Lyndon Nerenberg wrote: Jonathan == Jonathan Perkin [EMAIL PROTECTED] writes: Jonathan An auto-configuration script which merely checks for the Jonathan existance of a file rather than actually testing it's the Jonathan file it needs is a bit silly and probably deserves the Jonathan breakage. And just what else besides Perl would you expect to find in /usr/bin/perl you silly pedant?!? ;-) A perl wrapper? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: /usr/ports/emulators/bochs on -CURRENT
On Thu, May 16, 2002 at 01:14:01PM -0400, Mike Barcroft wrote: Riccardo Torrini [EMAIL PROTECTED] writes: # cd /usr/ports/emulators/bochs make [...] gmake[1]: Entering directory `/usr/ports/emulators/bochs/work/bochs-1.4/iodev' [...] c++ -c -O2 -pipe -march=pentiumpro -fno-rtti -fno-exceptions -fomit-frame-pointer -I/usr/X11R6/include -I.. -I./.. -I../instrument/stubs -I./../instrument/stubs cdrom.cc -o cdrom.o In file included from cdrom.cc:40: /usr/include/arpa/inet.h:102: conflicting types for `typedef __uint32_t socklen_t' ../osdep.h:105: previous declaration as `typedef int socklen_t' gmake[1]: *** [cdrom.o] Error 1 gmake[1]: Leaving directory `/usr/ports/emulators/bochs/work/bochs-1.4/iodev' gmake: *** [iodev/libiodev.a] Error 2 *** Error code 2 The problem appears to be that osdep.h is defining types it should not be defining. Software should include system headers to get new types, not try and out-smart the OS by defining its own (possibly incorrect) types. There is a patch in gnats to fix this error, but it still has errors, pat@ is currently looking at this and I'm building patches for him since I have a -current machine Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: MAKEDEV in current
On Tue, May 21, 2002 at 10:41:05AM -0700, Rob wrote: I've tried to copy MAKEDEV to /dev in current. But get the error- operation not supported. I must be missing some very basic concept. Rob. You are if you run mount it will tell you /dev is devfs you don't need to run MAKEDEV on -currrent as devices are created as you need them. If you're having a problem with a certain device not existing, then you should post that with all details. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: buildworld broken
On Wed, May 22, 2002 at 05:21:59PM +0200, Martin Kacerovsky wrote: Hi, I've got this error during buildworld: Have you read UPDATING and put what it told you to in make.conf? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: gdb breaks world
On Mon, May 27, 2002 at 11:12:47AM +0900, Jun Kuriyama wrote: At Wed, 22 May 2002 18:54:02 + (UTC), David O'Brien wrote: -ggdb means to use the most expressive debugging format the compiler knows about. You want -gstabs+ or -gstabs I cannot debug a kernel with -gstabs+ option. Any hints about this? % cd sys/i386/compile/WATERBLUE % grep gdb ../../conf/WATERBLUE makeoptions DEBUG=-gstabs+ #Build kernel with gdb(1) debug symbols % sudo gdb52 (gdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (gdb) exec-file kernel (gdb) core-file /var/crash/vmcore.4 /var/crash/vmcore.4 is not a core dump: File format not recognized Last time I checked, gdb was broken in -current and people were encouraged to use gdb in the ports system, but this may be oudated. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
FW: Re: Error with post 1.1 release Postfix and Cyrus -Possible Bug in VM system
Do we have anyone working on the VM system that could look at this? - Forwarded message from Wietse Venema [EMAIL PROTECTED] - Date: Thu, 30 May 2002 12:49:10 -0400 (EDT) Reply-To: Postfix users [EMAIL PROTECTED] From: [EMAIL PROTECTED] (Wietse Venema) To: Postfix users [EMAIL PROTECTED] Subject: Re: Error with post 1.1 release Postfix and Cyrus X-Mailer: ELM [version 2.4ME+ PL82 (25)] Sender: [EMAIL PROTECTED] You're somehow still running qmgr code that speaks the protocol from before 20020514. To find the file, # find / \( -name qmgr -o -name nqmgr \) -ls But you may not find this file. After upgrading Postfix I very, very, occasionally find that FreeBSD will execute a new process from an old file that was just replaced. Postfix always installs executables by using mv newfile oldfile. At this time, the old file may still be executing, and the parent process is always executing (the Postfix master daemon). I suspect an obscure VM system bug. postfix reload does not seem to cure this condition. The problem goes away after postfix stop then postfix start, which terminates the parent process. This has happened to me only twice over the past year. My server and workstations run FreeBSD versions 4.1 - 4.4. I haven't found the time and energy to debug this. Wietse - To unsubscribe, send mail to [EMAIL PROTECTED] with content (not subject): unsubscribe postfix-users - End forwarded message - -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: -current as guest of VMWare2
I'm running windows XP and vmware 3.1.1 with a guest os of FreeBSD 4.5 which I'm going to upgrade to -current. I couldn't find too much info on this thread. Does anyone know if vmware3 is affected by this problem when using a windows host os? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
PCMCIA 32-bit Cardbus Network Card
I hvae an Aprotech AE330T 32-bit cardbus card, that doesn't want to work on -stable or 5.0DP1 The error I get is kernel: pcic1: Card type 32-bit cardbus is unsupported. Luckily I have a linksys laying around somewhere, but has anyone tried to get this card to work under FreeBSD? --- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: PCMCIA 32-bit Cardbus Network Card
On Wed, Jun 12, 2002 at 07:24:49PM -0600, M. Warner Losh wrote: In message: [EMAIL PROTECTED] David W. Chapman Jr. [EMAIL PROTECTED] writes: : I hvae an Aprotech AE330T 32-bit cardbus card, that doesn't want to : work on -stable or 5.0DP1 : : The error I get is kernel: pcic1: Card type 32-bit cardbus is : unsupported. Luckily I have a linksys laying around somewhere, but : has anyone tried to get this card to work under FreeBSD? You need to run a NEWCARD kernel. I got it working pretty good with NEWCARD. The network card seems to hang sometimes and I lose connection. What's the best way to debug this when it happens, I think it may be a conflict with acpi, so I currently have it disabled. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ACPI errors on laptop running latest -current
When I boot up my gateway solo 2550, I get the following errors ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1305: *** Error: Method execution failed, AE_ERROR ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1305: *** Error: Method execution failed, AE_ERROR ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1305: *** Error: Method execution failed, AE_ERROR ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1305: *** Error: Method execution failed, AE_ERROR ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1305: *** Error: Method execution failed, AE_ERROR ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1305: *** Error: Method execution failed, AE_ERROR I've attached my dmesg. I also think there is a problem with acpi detecting the battery properly. IF anyone has any ideas I'd appreciate it. hw.acpi.acline: 0 hw.acpi.battery.life: 0 hw.acpi.battery.time: -1 hw.acpi.battery.state: 0 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Wed Jun 12 22:44:45 CDT 2002 root@:/usr/obj/usr/src/sys/DWCJR Preloaded elf kernel /boot/kernel/kernel at 0xc03e9000. Preloaded elf module /boot/kernel/usb.ko at 0xc03e90a8. Preloaded elf module /boot/kernel/random.ko at 0xc03e9150. Preloaded elf module /boot/kernel/sysvmsg.ko at 0xc03e91fc. Preloaded elf module /boot/kernel/sysvsem.ko at 0xc03e92a8. Preloaded elf module /boot/kernel/snp.ko at 0xc03e9354. Preloaded elf module /boot/kernel/acpi.ko at 0xc03e93fc. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 647189041 Hz CPU: Pentium III/Pentium III Xeon/Celeron (647.19-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 167706624 (163776K bytes) avail memory = 158613504 (154896K bytes) Pentium Pro MTRR support enabled Using $PIR table, 15 entries at 0xc00fded0 npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTDRSDT on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-safe frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0x8008-0x800b on acpi0 acpi_cpu0: CPU on acpi0 acpi_tz0: thermal zone on acpi0 acpi_pcib0: Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: PCI bus on acpi_pcib0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0x1000-0x100f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller irq 5 at device 7.2 on pci0 uhci0: Could not map ports device_probe_and_attach: uhci0 attach returned 6 pci0: bridge, PCI-unknown at device 7.3 (no driver attached) pccbb0: TI1225 PCI-CardBus Bridge irq 10 at device 10.0 on pci0 cardbus0: CardBus bus on pccbb0 pccard0: 16-bit PCCard bus on pccbb0 pccbb1: TI1225 PCI-CardBus Bridge irq 10 at device 10.1 on pci0 cardbus1: CardBus bus on pccbb1 pccard1: 16-bit PCCard bus on pccbb1 pci0: multimedia, audio at device 14.0 (no driver attached) pci0: simple comms at device 16.0 (no driver attached) acpi_acad0: AC adapter on acpi0 acpi_cmbat0: Control method Battery on acpi0 acpi_button0: Sleep Button on acpi0 acpi_ec0: embedded controller port 0x66,0x62 on acpi0 ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A fdc0: enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 orm0: Option ROM at iomem 0xc-0xcbfff on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 pmtimer0 on isa0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled Timecounters tick every 10.000 msec acpi_cpu: CPU throttling enabled
