bogus microuptime() warnings?
I regularly get "microuptime() went backwards" warnings on my desktop box. The funny thing about them is that the reported timevals have the same seconds part, but the microseconds part of the second timeval is so large that it's wrapped around to a negative number (causing the signed comparison to report that it went backwards). This suggests that the current process has been running uninterrupted for several seconds, which seems unlikely - or that the timecounter was adjusted upwards while the process was running (could ntp cause that?) DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bogus microuptime() warnings?
In message [EMAIL PROTECTED], Dag-Erling Smorgrav writes: I regularly get "microuptime() went backwards" warnings on my desktop box. The funny thing about them is that the reported timevals have the same seconds part, but the microseconds part of the second timeval is so large that it's wrapped around to a negative number (causing the signed comparison to report that it went backwards). This suggests that the current process has been running uninterrupted for several seconds, which seems unlikely - or that the timecounter was adjusted upwards while the process was running (could ntp cause that?) No, this is either a problem reading the i8254 timecounter reliably or an interrupt latency problem. If you sysctl's indicate that you are running on the TSC timecounter and you can reproduce this there is some chance we can create a workaround. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bogus microuptime() warnings?
Poul-Henning Kamp [EMAIL PROTECTED] writes: No, this is either a problem reading the i8254 timecounter reliably or an interrupt latency problem. Given that this is -CURRENT, interrupt latency is a likely explanation... Going off on a tangent, I'm getting a lot fewer "hwptr went backwards" with the latest -CURRENT than I used to... If you sysctl's indicate that you are running on the TSC timecounter and you can reproduce this there is some chance we can create a workaround. I'll check. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bogus microuptime() warnings?
In message [EMAIL PROTECTED], Dag-Erling Smorgrav writes: Poul-Henning Kamp [EMAIL PROTECTED] writes: No, this is either a problem reading the i8254 timecounter reliably or an interrupt latency problem. Given that this is -CURRENT, interrupt latency is a likely explanation... Going off on a tangent, I'm getting a lot fewer "hwptr went backwards" with the latest -CURRENT than I used to... That's also the irq-latency if I understand it right. The latency went from "abysmal" to "bad" recently. We used to do "ok". -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
newpcm audio recording
Hi, I have been trying to do some audio-recording lately without much success. After searching the archieves etc I found some reports of this problem and there are also some PR's about it (8bit at low rates ok, 16bit and higher rates is not). I was wondering if someone is working on this and if we could expect some progress soon? -- Patrik Sundberg - email: [EMAIL PROTECTED] || [EMAIL PROTECTED] --- telefon: 013-178 567 - mobiltelefon: 070-760 22 40 --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm audio recording
Hi, I have been trying to do some audio-recording lately without much success. After searching the archieves etc I found some reports of this problem and there are also some PR's about it (8bit at low rates ok, 16bit and higher rates is not). I was wondering if someone is working on this and if we could expect some progress soon? I believe this may be related to the soundcard driver, which soundcard are you using? I am using an SB Live 1024 in my computer, and I am reading from the audio input, 16 bits at 44.1KHz, although only in mono, doing fourier transform on the data, and displaying the results graphically, without any problems. --- Erik H. Bakke Don't ask "Who invented time?", the real question is "When was time invented?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm audio recording
On Tue, Jan 09, 2001 at 02:29:59PM +0100, Erik H. Bakke wrote: Hi, I have been trying to do some audio-recording lately without much success. After searching the archieves etc I found some reports of this problem and there are also some PR's about it (8bit at low rates ok, 16bit and higher rates is not). I was wondering if someone is working on this and if we could expect some progress soon? I believe this may be related to the soundcard driver, which soundcard are you using? I am using an SB Live 1024 in my computer, and I am reading from the audio input, 16 bits at 44.1KHz, although only in mono, doing fourier transform on the data, and displaying the results graphically, without any problems. I have a SB32 isa-card. -- Patrik Sundberg - email: [EMAIL PROTECTED] || [EMAIL PROTECTED] --- telefon: 013-178 567 - mobiltelefon: 070-760 22 40 --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fan speed control sony vaio lx800 slimtop
Hi, Now I'd like to figure out how to turn the damn fan up and down. This machine is quiet under windows but sets the fan to high under FreeBSD and never turns it down. The fan has three settings - 0V, 6V and 12V. Under windows it stays between 0 and 6V. Thermal management implementation is in our queue. We'll create policy manager for ACPI subsystems including thermal (Active, Passive cooling etc.). Of course any help would be welcome :-) I've tried "apm -h 1; apm -e 1;" hoping something would happen but it still doesn't slow down the fan. Currently we don't have any means to control fan device (except for the machine specific tools). If someone can sketch out a road map of what I should do I'll do the dirty work. I don't know about ACPI etc and so would appreciate a kick start. I've picked up the spec but haven't printed it out yet. You could find `3.10 Thermal Management' for overview and `12 THERMAL MANAGEMENT' for detail in ACPI 2.0 spec. Also `7.1 Declaring a Power Resource Object' and `10.6 Fan Device' may help you. [EMAIL PROTECTED] is a mailing list for ACPI development. # English and Japanese are mixed :-) If you are interested in it, please send a mail to [EMAIL PROTECTED] with subscribe acpi-jp on body. Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm audio recording
I have a SB32 isa-card. what revision of sys/dev/sound/isa/sb16.c ? -cg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release still broken...
On Tue, Jan 09, 2001 at 09:11:20AM +0100, Poul-Henning Kamp wrote: === rpcsvc rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h rpcgen: cannot find any C preprocessor (cpp) *** Error code 1 Let me start a release. This means rpcgen has been using /usr/libexec/cpp which is *only* for the compiler's use. rpcgen should have been using /usr/bin/cpp all this time. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FYI: got back second channel of aic7896
Hi Didn't get around rebuilding world and kernel until today. Got back my cdrom and old Fireball_TM disk, thank you. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
proposed small change to .cshrc
I think the patch below (in some form) was agreed upon a while ago but nobody actually committed it.. in any case, are there any objections? This makes it so if root's shell is /bin/tcsh then CTRL-W erases only the previous word instead of the entire line. Thanks, -Archie __ Archie Cobbs * Packet Design * http://www.packetdesign.com Index: src/etc/root/dot.cshrc === RCS file: /home/ncvs/src/etc/root/dot.cshrc,v retrieving revision 1.27 diff -u -r1.27 dot.cshrc --- dot.cshrc 2000/05/28 15:09:31 1.27 +++ dot.cshrc 2001/01/09 17:44:00 @@ -27,4 +27,7 @@ set history = 100 set savehist = 100 set mail = (/var/mail/$USER) + if ( `basename $SHELL` == "tcsh" ) then + bindkey ^W backward-delete-word + endif endif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: proposed small change to .cshrc
On Tue, Jan 09, 2001 at 09:45:14AM -0800, Archie Cobbs wrote: + if ( `basename $SHELL` == "tcsh" ) then + bindkey ^W backward-delete-word + endif I generally test for tcsh like this: if ( $?tcsh ) then bindkey ^W backward-delete-word endif -- Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: proposed small change to .cshrc
:On Tue, Jan 09, 2001 at 09:45:14AM -0800, Archie Cobbs wrote: : : +if ( `basename $SHELL` == "tcsh" ) then : +bindkey ^W backward-delete-word : +endif : :I generally test for tcsh like this: : : if ( $?tcsh ) then : bindkey ^W backward-delete-word : endif : :-- :Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology How about this: if ( $?tcsh ) then bindkey "^W" backward-delete-word bindkey -k up history-search-backward bindkey -k down history-search-forward endif For personal use I also do (for tcsh): set prompt = "%m:%/%# " But the Amiga-style integrated history search is the feature I use the most. Having a multi-thousand line history actually becomes useful. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADSUP: kernel config required
isp_pci.c just moved from sys/pci to sys/dev/isp (for maintenance ease). You will need to reconfig kernels if you included this. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make release still broken...
=== rpcsvc rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h rpcgen: cannot find any C preprocessor (cpp) *** Error code 1 Let me start a release. This means rpcgen has been using /usr/libexec/cpp which is *only* for the compiler's use. rpcgen should have been using /usr/bin/cpp all this time. From rpc_main.c #ifdef __FreeBSD__ #define SUNOS_CPP "/usr/libexec/cpp" Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fan speed control sony vaio lx800 slimtop
Note also that Scott Long ([EMAIL PROTECTED]) is also working on this, you will want to check with him to work out where he's up to... Now I'd like to figure out how to turn the damn fan up and down. This machine is quiet under windows but sets the fan to high under FreeBSD and never turns it down. The fan has three settings - 0V, 6V and 12V. Under windows it stays between 0 and 6V. Thermal management implementation is in our queue. We'll create policy manager for ACPI subsystems including thermal (Active, Passive cooling etc.). Of course any help would be welcome :-) I've tried "apm -h 1; apm -e 1;" hoping something would happen but it still doesn't slow down the fan. Currently we don't have any means to control fan device (except for the machine specific tools). If someone can sketch out a road map of what I should do I'll do the dirty work. I don't know about ACPI etc and so would appreciate a kick start. I've picked up the spec but haven't printed it out yet. You could find `3.10 Thermal Management' for overview and `12 THERMAL MANAGEMENT' for detail in ACPI 2.0 spec. Also `7.1 Declaring a Power Resource Object' and `10.6 Fan Device' may help you. [EMAIL PROTECTED] is a mailing list for ACPI development. # English and Japanese are mixed :-) If you are interested in it, please send a mail to [EMAIL PROTECTED] with subscribe acpi-jp on body. Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Current-ISO
I have been unsucessfully trying to build an ISO image of the 5.0-CURRENT branch for the past several weeks. Is anyone aware of a tool to pull the latest tree and turn it into an ISO image? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problems related to disappearnce of libgcc_r
Hi, I wonder if anyone noticed that disappearance of libgcc_r will cause lot of ports to break. Therefore it would be nice if some form of compatibility shim is provided, for example symlink from /usr/lib/libgcc.a to /usr/lib/libgcc_r.a automatically created by installworld would do the trick nicely. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems related to disappearnce of libgcc_r
On Tue, 9 Jan 2001, Maxim Sobolev wrote: Hi, I wonder if anyone noticed that disappearance of libgcc_r will cause lot of ports to break. Therefore it would be nice if some form of compatibility shim is provided, for example symlink from /usr/lib/libgcc.a to /usr/lib/libgcc_r.a automatically created by installworld would do the trick nicely. Fix the ports to not use libgcc_r any longer. Wasn't linking to -lgcc_r just a hack to work around the problems we introduced just before 4.2R (also into -current)? -- Dan Eischen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: proposed small change to .cshrc
Matt Dillon wrote: :On Tue, Jan 09, 2001 at 09:45:14AM -0800, Archie Cobbs wrote: : : + if ( `basename $SHELL` == "tcsh" ) then : + bindkey ^W backward-delete-word : + endif : :I generally test for tcsh like this: : : if ( $?tcsh ) then : bindkey ^W backward-delete-word : endif : :-- :Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology How about this: if ( $?tcsh ) then bindkey "^W" backward-delete-word bindkey -k up history-search-backward bindkey -k down history-search-forward endif I was about to write a 'over my dead body' here, but I tried it out and discovered that the POLA (for tcsh users) is not too bad after all. In fact, I think I will add this to my .tcshrc :-) Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems related to disappearnce of libgcc_r
"David O'Brien" wrote: On Tue, Jan 09, 2001 at 07:53:29PM +0200, Maxim Sobolev wrote: I wonder if anyone noticed that disappearance of libgcc_r will cause lot of ports to break. Therefore it would be nice if some form of compatibility sh im is provided, for example symlink from /usr/lib/libgcc.a to /usr/lib/libgcc_ r.a automatically created by installworld would do the trick nicely. I really don't want to propogate libgcc_r. Lets just fix the ports that break. They can be seen at http://bento.freebsd.org/ We need to be a little careful for ports that are supposed to work on RELENG_4 and -CURRENT. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: proposed small change to .cshrc
On Tue, 9 Jan 2001, Peter Wemm wrote: Matt Dillon wrote: :On Tue, Jan 09, 2001 at 09:45:14AM -0800, Archie Cobbs wrote: : : +if ( `basename $SHELL` == "tcsh" ) then : +bindkey ^W backward-delete-word : +endif : :I generally test for tcsh like this: : : if ( $?tcsh ) then : bindkey ^W backward-delete-word : endif : :-- :Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology How about this: if ( $?tcsh ) then bindkey "^W" backward-delete-word bindkey -k up history-search-backward bindkey -k down history-search-forward endif I was about to write a 'over my dead body' here, but I tried it out and discovered that the POLA (for tcsh users) is not too bad after all. In fact, I think I will add this to my .tcshrc :-) Just use bash ;-) -- Dan Eischen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems related to disappearnce of libgcc_r
On Tue, 9 Jan 2001, Peter Wemm wrote: "David O'Brien" wrote: On Tue, Jan 09, 2001 at 07:53:29PM +0200, Maxim Sobolev wrote: I wonder if anyone noticed that disappearance of libgcc_r will cause lot of ports to break. Therefore it would be nice if some form of compatibility sh im is provided, for example symlink from /usr/lib/libgcc.a to /usr/lib/libgcc_ r.a automatically created by installworld would do the trick nicely. I really don't want to propogate libgcc_r. Lets just fix the ports that break. They can be seen at http://bento.freebsd.org/ We need to be a little careful for ports that are supposed to work on RELENG_4 and -CURRENT. OSVERSION checks? -- Dan Eischen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bogus microuptime() warnings?
On 09-Jan-01 Dag-Erling Smorgrav wrote: Poul-Henning Kamp [EMAIL PROTECTED] writes: No, this is either a problem reading the i8254 timecounter reliably or an interrupt latency problem. Given that this is -CURRENT, interrupt latency is a likely explanation... Going off on a tangent, I'm getting a lot fewer "hwptr went backwards" with the latest -CURRENT than I used to... Which soundcard? -- 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
Re: Problems related to disappearnce of libgcc_r
"David O'Brien" wrote: On Tue, Jan 09, 2001 at 07:53:29PM +0200, Maxim Sobolev wrote: I wonder if anyone noticed that disappearance of libgcc_r will cause lot of ports to break. Therefore it would be nice if some form of compatibility sh im is provided, for example symlink from /usr/lib/libgcc.a to /usr/lib/libgcc_ r.a automatically created by installworld would do the trick nicely. I really don't want to propogate libgcc_r. Lets just fix the ports that break. They can be seen at http://bento.freebsd.org/ We need to be a little careful for ports that are supposed to work on RELENG_4 and -CURRENT. Yes, it's why I think we need this compatability hack. Bloating all 20+ ports that have to use gcc_r on 4-STABLE and downwards with OSVERSION check is PITA. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems related to disappearnce of libgcc_r
On Tue, 9 Jan 2001, Peter Wemm wrote: "David O'Brien" wrote: On Tue, Jan 09, 2001 at 07:53:29PM +0200, Maxim Sobolev wrote: I wonder if anyone noticed that disappearance of libgcc_r will cause lot of ports to break. Therefore it would be nice if some form of compatibility sh im is provided, for example symlink from /usr/lib/libgcc.a to /usr/lib/libgcc_ r.a automatically created by installworld would do the trick nicely. I really don't want to propogate libgcc_r. Lets just fix the ports that break. They can be seen at http://bento.freebsd.org/ We need to be a little careful for ports that are supposed to work on RELENG_4 and -CURRENT. OSVERSION checks? Yes, I know it's possible, but to provide a hack in one place istead of 20+ places (find /usr/ports -type f | xargs grep -l gcc_r | wc -l) is much easier both in the terms of efforts and testing required. After all, it would only cost us one inode for symlink and probably two-three lines in appropriate Makefile. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems related to disappearnce of libgcc_r
On Tue, Jan 09, 2001 at 02:04:05PM -0800, Peter Wemm wrote: We need to be a little careful for ports that are supposed to work on RELENG_4 and -CURRENT. RELENG_4 and -current are the same in this reguard. I should bump __FreeBSD_version in both and then people can use that as the cut over date. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems related to disappearnce of libgcc_r
On Wed, Jan 10, 2001 at 02:20:01AM +0200, Maxim Sobolev wrote: Yes, I know it's possible, but to provide a hack in one place istead of 20+ places (find /usr/ports -type f | xargs grep -l gcc_r | wc -l) is much easier both in the terms of efforts and testing required. After all, it would only cost us one inode for symlink and probably two-three lines in appropriate Makefile. The answer is "NO". To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
securelevel and sysctl
I'am working on module, which catches __sysctl system call, and on securelevel grater than 3, refuse any changes of sysctl oids. Are there any problems, which might happen after blocking sysctl oids change ? AFAIR there is no such application running in user Space,which requires ability to change sysctl oids,is there ? Secondly I'was thinking about oids,which are needed for user space aplications to work. I figured out,that vi use some (I didn't check which one) oid on startup, so is there a list of oids used by user space applications ? -- _ __ __ / \ | | / / / \ / \ -- Tomasz Paszkowski --- NS88-6BONE | |\ \| | \ \ |/ \||/ \| === BSD is for people who love Unix /_/ \__/ /_/ \_/ \_/ --- Linux is for people who hate Microsoft - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: proposed small change to .cshrc
Matt Dillon writes: if ( $?tcsh ) then bindkey "^W" backward-delete-word bindkey -k up history-search-backward bindkey -k down history-search-forward endif Why do you need the 'up' and 'down' ones.. doesn't it already do that without explicit configuration? -Archie __ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: proposed small change to .cshrc
:Matt Dillon writes: : if ( $?tcsh ) then : bindkey "^W" backward-delete-word : bindkey -k up history-search-backward : bindkey -k down history-search-forward : endif : :Why do you need the 'up' and 'down' ones.. doesn't it already do that :without explicit configuration? : :-Archie This is the history *search* function. Lets say you did a complex 'find' command 5 minutes ago and a hundred intervening commands since, and you want to run the 'find' again. You type: % finup-arrow If you did a bunch of find's, hit up arrow as many times as necessary. You can type as few or as many characters as you like prior to hitting the up arrow, depends on what you are looking for. If you just hit the up or down arrow without having partial text on the line, it works just like normal history. Once you start using it, you will never be able to go back. This is how the Amiga used to do it. It's the only right way. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sio serial console in -current?
On Mon, 8 Jan 2001, Matthew Jacob wrote: Something wierd has been happening lately- the serial console on my i386 machine works fine up until init is forked.. THen the output is mangled, and one gets replicated and/or mangled stuff. On a reboot I'm getthing things like: Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped This may be caused by inconsistent settings in /etc/rc.serial. /etc/rc.serial should rarely be changed from its default of doing nothing. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sio serial console in -current?
Good guess, I shouldn't wonder, but: quarm.feral.com diff /etc/rc.serial /usr/src/etc/ quarm.feral.com On Wed, 10 Jan 2001, Bruce Evans wrote: On Mon, 8 Jan 2001, Matthew Jacob wrote: Something wierd has been happening lately- the serial console on my i386 machine works fine up until init is forked.. THen the output is mangled, and one gets replicated and/or mangled stuff. On a reboot I'm getthing things like: Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped This may be caused by inconsistent settings in /etc/rc.serial. /etc/rc.serial should rarely be changed from its default of doing nothing. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
YES! laptop installing
This is to let everyone know that right now as I type I am setting up FreeBSD to start downloading over my cardbus ethernet card. It seems to work great except it doesn't beep when the card enables, but that's fine with me. :-) = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: YES! laptop installing
This is to let everyone know that right now as I type I am setting up FreeBSD to start downloading over my cardbus ethernet card. It seems to work great except it doesn't beep when the card enables, but that's fine with me. :-) What card? My Netgear FA510 (dc0) probes (sorta) but comes up with a crazy MAC address, and then doesn't work. It doesn't even go UP. MAC=00:00:80:00:00:80, FWIW. M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: YES! laptop installing
I'm using a 3ccfe575ct-d, it works great, I just installed using it by making my own GENERIC kernel with the cardbus stuff on it, and putting it on an install boot floppy instead of the one that normally comes on it. I'm not sure the pmtimer is working though, and I keep getting dmesg: malloc failed = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Wed, 10 Jan 2001, Mark Murray wrote: This is to let everyone know that right now as I type I am setting up FreeBSD to start downloading over my cardbus ethernet card. It seems to work great except it doesn't beep when the card enables, but that's fine with me. :-) What card? My Netgear FA510 (dc0) probes (sorta) but comes up with a crazy MAC address, and then doesn't work. It doesn't even go UP. MAC=00:00:80:00:00:80, FWIW. M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pmtimer
I'm not sure what pmtimer is supposed to do. Isn't it supposed to give support for the broken statclock on laptops? I saw my friend running 4.1 with some patches that allowed him to use the statclock (and the rtc device showed up in systat -vm 2) On my laptop, pmtimer doesn't appear to do anything; and I couldn't find a manpage on it = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bogus microuptime() warnings?
On Tue, Jan 09, 2001 at 04:11:16PM -0800, John Baldwin wrote: Going off on a tangent, I'm getting a lot fewer "hwptr went backwards" with the latest -CURRENT than I used to... Which soundcard? SB 64 AWE ISA PNP... almost no hwptr... messages any more and sound is no longer popping under normal circumstances. (even if eg disk io is in progress) I was already rejoicing about this to the list in the last millenium... ( 30th December to be precise:-) -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
