When I play mp3's or mpg files on my computer, it plays fine during first
three minutes or so and then I start hearing a lot of statics. If I pause
the player and play again right after that, it comes to normal.
Does anybody experience this?
I am using snd0 with crystal semiconductor 4232
I spent about 2 to 3 hours last night futzing with sysinstall and
getting the amr.ko file onto the 4.0 install disk (using the
4.0-19991114 SNAP) I tried adding the amr disks to devices.c in
sysinstall but had no luck.
After booting the install disks and loading the amr kld (the probe
messages
David O'Brien wrote:
I'll be pulling the switch to use GCC 2.95.2 as the base compiler in
-CURRENT on Sunday evening (Freefall time).
Those not-quite-so daring might want to hold off on your next make world.
*** NOTE *** that I have NOT changed the shared lib version for
libstc++.so (the
On Sat, Nov 13, 1999 at 06:24:09PM +0100, Hellmuth Michaelis wrote:
I'm not at all satisfied with the way password arguments to spppcontrol
work currently.
How about some /etc/sppp/{pap,chap}-secrets with restrictive permissions?
So you could specify everything except the secrets with
The design phase for FreeBSD 4.0 is coming to a close. There are a couple
of things I'm planning on (belatedly) for the SCSI tape driver. I'd like
feedback and suggestions about these and other things, so pass 'em my way.
One change I'm thinking about is probably controversial, so I'd like to
have you tried using the pcm0 sound drivers instead? I used them for the
crystal -based on-board sound that comes with Dell Optiplexsp?
machines... Have a look at LINT for the setup instructions.
DJM:
On Mon, 15 Nov 1999, Byung Yang wrote:
When I play mp3's or mpg files on my computer, it
' statement:
../../i386/isa/pcaudio.c:196: fixed or forbidden register 0 (ax) was spilled for class
AREG.
*** Error code 1
Stop in /usr/src/sys/compile/MRYMACH.
mrynet# gcc -v
Using builtin specs.
gcc version 2.95.2 19991024 (release)
Last cvsup was completed at 05:51 +0800 on 19991115
Out of da blue Jim King aka ([EMAIL PROTECTED]) said:
I just picked up an AWE64 to use until the Vortex2 driver is working.
Is someone actively working on the Vortex2 driver for FreeBSD or are you
referring to the work that's being done by the opensound group?
The card is detected in Win98,
Nicolai Petri Secure [EMAIL PROTECTED] writes:
I'm currently programming a screensaver the shows statistics (cpu load and
stuff) but the interface for doing it in kernel mode sucks.. What is the
right way to do it ?
Check out the sysctl(8) source to see how it special-cases vm.loadavg;
find
Jim King [EMAIL PROTECTED] writes:
At 11:20 PM 11/13/1999 -0600, Jim King wrote:
That does it. When running the loop forward only the ISA PnP modem is
found; after hacking it to run the loop backwards the AWE64 *and* the
modem are both found. Thanks!
fwiw, the same thing applies to
I just got a new machine, an HP Kayak/XA with a PIII/500, 256 MB of RAM and
2x 9 GB of disk. It has a builtin sound card on the motherboard,
apparently a soundblaster clone of some sort on the ISA bus.
FreeBSD Audio Driver (newpcm) Nov 15 1999 14:52:14
Installed devices:
pcm0: SoundBlaster Pro
Ollivier Robert wrote:
I just got a new machine, an HP Kayak/XA with a PIII/500, 256 MB of RAM and
2x 9 GB of disk. It has a builtin sound card on the motherboard,
apparently a soundblaster clone of some sort on the ISA bus.
FreeBSD Audio Driver (newpcm) Nov 15 1999 14:52:14
Installed
"Peter Edwards" [EMAIL PROTECTED] writes:
I've attached a patch that appears reliable. Can someone review it
(and possibly commit??)
Send in a PR with the patch.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current"
According to Peter Wemm:
Have you tried plain "device pcm0"?
Yes, nothing was found.
(and if it's not detected (ie: it's a
motherboard resources rather than a pnp isa device), try adding "options
PNPBIOS" to your kernel.)
Here are the results of dmesg
According to Peter Wemm:
Have you tried plain "device pcm0"? (and if it's not detected (ie: it's a
motherboard resources rather than a pnp isa device), try adding "options
PNPBIOS" to your kernel.)
With the following options, the machine doesn't crash but mpg123 doesn't
seem to be able to
Ollivier Robert wrote:
Oh, also, there's a bug:
peter@overcee[11:42pm]~src/sys/dev/pcm/isa-185 grep ADS *
ad1816.c: case 0x80719304: /* ADS7180 */
mss.c: case 0x80719304: /* ADS7180 */
And yet:
date: 1999/09/28 20:00:05; author: cg; state: Exp; lines: +15 -347
seperate the
Ollivier Robert wrote:
According to Peter Wemm:
Have you tried plain "device pcm0"? (and if it's not detected (ie: it's a
motherboard resources rather than a pnp isa device), try adding "options
PNPBIOS" to your kernel.)
With the following options, the machine doesn't crash but mpg123
According to Peter Wemm:
Err.. *both* PNPBIOS and 'device pcm0' - the dmesg you showed below is
with a static ISA sb card configured. I'm particularly interested in
ADS7180, but it's conflicting with something, possibly the ISA pcm0.
Hmm, sorry.
With PNPBIOS and "device pcm0" it seems to be
On Sat, 13 Nov 1999, Vladimir Kushnir wrote:
I've been working on a driver which would support the 'legacy' (i.e.
soundblaster compatible) section of the chip. This would support playback
but not record but its better than nothing. At this stage, I have it
mostly working but no sound
Ollivier Robert wrote:
[..]
But it doesn't seem to output anything.
I get this on the console as soon as I press ^C.
start dma, failed to set bit 0xfe 0xff
[..]
This will be the mss vs ad1816 problem. I've just been told that the mss.c
driver should not be attaching to this card, ad1816
According to Peter Wemm:
Please try:
options PNPBIOS
controller pnp0
device pcm0
No pcm device attached when I remove the code from mss.c:
cat: /dev/sndstat: Device not configured
unknown0: PNP0c02 at port
On Mon, Nov 15, 1999 at 05:51:58AM +, FreeBSD mailing list wrote:
The following is AFTER cvsup, world build, config, make clean, and make depend:
...
../../i386/isa/pcaudio.c:196: Invalid `asm' statement:
../../i386/isa/pcaudio.c:196: fixed or forbidden register 0 (ax) was spilled for
I've discovered the following problem, either due to egcs or the
source code for in_cksum in ping, I'm not sure.
The symptom is that in_cksum() returns an invalid result on an
odd-size buffer, when compile optimization is on.
You can check this by trying "ping -s 65 localhost" and seeing that
On Mon, 15 Nov 1999 17:48:31 +0100, Pierre Beyssac wrote:
I've discovered the following problem, either due to egcs or the
source code for in_cksum in ping, I'm not sure.
Alas, you're not in virgin territory, Columbus. :-)
See PR 13292.
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL
On Saturday, 13 November 1999 at 15:28:38 -0800, David O'Brien wrote:
Hi folks,
Once again, `boot2' is the only thing holding us back from upgrading our
base compiler. The commit below plus -fdata-sections gets us to needing
to reduce another 100 bytes from `boot2'.
This is an appeal to
On Mon, Nov 15, 1999 at 06:52:23PM +0200, Sheldon Hearn wrote:
On Mon, 15 Nov 1999 17:48:31 +0100, Pierre Beyssac wrote:
I've discovered the following problem, either due to egcs or the
source code for in_cksum in ping, I'm not sure.
See PR 13292.
Wow, Thanks! August 21th, it's not really
On Mon, 15 Nov 1999 18:01:45 +0100, Pierre Beyssac wrote:
Maybe I can at least commit the addition of "volatile" to the source
code. That will work around that particular bug until egcs is
fixed...
FWIW, the newly committed gcc-2.95.2 doesn't "fix" the problem.
Ciao,
Sheldon.
To
The design phase for FreeBSD 4.0 is coming to a close. There are a couple
of things I'm planning on (belatedly) for the SCSI tape driver. I'd like
feedback and suggestions about these and other things, so pass 'em my way.
One change I'm thinking about is probably controversial, so I'd like
Maybe I can at least commit the addition of "volatile" to the source
code. That will work around that particular bug until egcs is
fixed...
FWIW, the newly committed gcc-2.95.2 doesn't "fix" the problem.
Are you sure? GCC-2.95.2 seems OK here.
Dima
To Unsubscribe: send mail to
There seems to be a great amount of confusion about the 2 EOF marks on
tapes. It has nothing to do with physical EOT, even the 556BPI 1/2"
tape drives on an IBM 1401 can detect physical EOT. The problem is
with LOGICAL EOT, most tape drives do not have a logical EOT write
command, even
On Mon, 15 Nov 1999 18:01:45 +0100, Pierre Beyssac [EMAIL PROTECTED] said:
Maybe I can at least commit the addition of "volatile" to the source
code. That will work around that particular bug until egcs is
fixed...
It's not a compiler bug, it's a source code bug.
The C Language specifies
On Mon, Nov 15, 1999 at 01:35:15PM -0500, Garrett Wollman wrote:
If, rather than casting pointers, the code used a union (containing
one u_int16_t and one array[2] of u_int8_t), the compiler would have
enough information to know about the aliases.
You're right, this seems to work even with
Reread/reresponse, sorry- ENOCOFFEE:
1 filemark can not be used for EOT, it is EOF, you can't tell if what you
read next is another file or not that may have been left by a previosly
longer usage on the tape.
Well, read until *BLANK CHECK* seems to be what the driver
I noticed that ipfilter is still gone... Was there any resolution here,
or is ipfilter gone for good?
All other concerns/features aside, I find the stateful inspection stuff
much easier to setup than the ipfw filtering... I only touch my firewall
once in a blue moon, and just about everything
On Mon, 15 Nov 1999, Rodney W. Grimes wrote:
Reread/reresponse, sorry- ENOCOFFEE:
1 filemark can not be used for EOT, it is EOF, you can't tell if what you
read next is another file or not that may have been left by a previosly
longer usage on the tape.
:It's not a compiler bug, it's a source code bug.
:
:The C Language specifies that pointers to distinct types can be
:assumed, under certain conditions, never to alias one another. (This
:...
:Recent values of GCC make use of this obscure language feature to
:improve optimization. Essentially,
On Sun, 14 Nov 1999, Lester Igo wrote:
Speaking of which, is their an archive (web based?) of the FreeBSD-current
mailing list (how about others?)? I didn't see one linked in my searches
around the web pages.
http://www.freebsd.org/mail/
kind of obviously pointed to by
[in_cksum bugs]
Fix committed for ping.
There's another bug in sbin/routed/rdisc.c:in_cksum() on odd packet
sizes, albeit I'm not sure it's ever triggered (does routed ever
generate odd-size packets?). It's a portability bug (works only on
little-endian machines). I'll commit the same fix if
On Mon, 15 Nov 1999, Alfred Perlstein wrote:
I spent about 2 to 3 hours last night futzing with sysinstall and
getting the amr.ko file onto the 4.0 install disk (using the
4.0-19991114 SNAP) I tried adding the amr disks to devices.c in
sysinstall but had no luck.
...
replying to my own
I just successfully compiled the world and the kernel (defaut
optimizations on everything) with gcc 2.95.2, and so far all is well :-)
=
| Kenneth Culver | FreeBSD: The best OS around.|
| Unix Systems
Same here, no problems.
_F
At 03:36 PM 11/15/99 -0500, Kenneth Wayne Culver wrote:
I just successfully compiled the world and the kernel (defaut
optimizations on everything) with gcc 2.95.2, and so far all is well :-)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
At 04:10 PM 11/15/99 -0500, Forrest Aldrich wrote:
Same here, no problems.
_F
At 03:36 PM 11/15/99 -0500, Kenneth Wayne Culver wrote:
I just successfully compiled the world and the kernel (defaut
optimizations on everything) with gcc 2.95.2, and so far all is well :-)
I did the same and
Yes, I've tried the "newpcm" sound driver. Before ppl started modifying
pcm drivers, pcm0 was the best driver for my sound card, but then after
this newpcm came out, it started crashing all over the place. That means
when I play mp3 or sound files, the player program freezes(not freebsd
itself)
According to Peter Wemm:
PNPBIOS should pick this up automatically, that's why you need to remove the
'at isa' stuff and stop overriding the pnp code from using what it discovers
from the bios.
See Peter's commits in ad1816.c to see the fix. Thanks Peter.
--
Ollivier ROBERT -=- FreeBSD: The
can erase a password
or similar sensitive arguments.
Test, test, test...
Poul-Henning
/19991115
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long tim
In article [EMAIL PROTECTED] you write:
The p_args.patch patch implements a cache of the commandline arguments
in the process structure and makes ps(1) pick it up from there with
sysctl rather than by groping around in the target process memory.
I don't think this should go in at all.
It
:http://phk.freebsd.dk/misc/p_args.patch
:
:The p_args.patch patch implements a cache of the commandline arguments
:in the process structure and makes ps(1) pick it up from there with
:sysctl rather than by groping around in the target process memory.
:
:This patch:
:Speeds up ps(1).
:I don't think this should go in at all.
:
:It increases the size of the proc structure (thereby affecting _all_
:processes) gratuitously. While I'm generally in favour of having the process
:arguments kept around, the "BSD way" has been to only examine them in user
:memory, despite that being
"Matthew" == Matthew Dillon [EMAIL PROTECTED] writes:
Matthew Why don't we get rid of the 'e' option to ps while we
Matthew are at it considering how much of a security hole it is.
I wouldn't nuke it completely. Make -e a noop unless the real uid ps
is running with matches the
On Mon, Nov 15, 1999 at 02:27:10PM -0800, Matthew Dillon wrote:
And, also, we need to get rid of the 'e' option to ps entirely. It's a
major security hole.
Not more so than option 'u', or even 'a', if you ask me.
It's common knowledge under Unix that you shouldn't put anything
[in_cksum bugs]
There's another bug in sbin/routed/rdisc.c:in_cksum() on odd packet
sizes, albeit I'm not sure it's ever triggered (does routed ever
generate odd-size packets?).
I've checked, the answer is no: apparently, in_cksum() in routed/rdisc.c
is only called in two places, both with
Hi,
At 11:01 am -0800 15/11/99, Matthew Jacob wrote:
I repeat what I said in other mail- can you actually show me a tape drive
where what I propose really doesn't work?
I have access to a few assorted drives and I'll do the experiments but
don't hold your breath.
BUT I have to say that on
Pierre Beyssac wrote in list.freebsd-current:
On Mon, Nov 15, 1999 at 02:27:10PM -0800, Matthew Dillon wrote:
And, also, we need to get rid of the 'e' option to ps entirely. It's a
major security hole.
Not more so than option 'u', or even 'a', if you ask me.
It's common
At 3:48 PM -0700 11/15/99, Lyndon Nerenberg wrote:
"Matthew" == Matthew Dillon [EMAIL PROTECTED] writes:
Matthew Why don't we get rid of the 'e' option to ps while we
Matthew are at it considering how much of a security hole it is.
I wouldn't nuke it completely. Make -e a noop
Okay- I hear you both.
What do you do with QIC drives which cannnot write 2FM then?
On Mon, 15 Nov 1999, Bob Bishop wrote:
Hi,
At 11:01 am -0800 15/11/99, Matthew Jacob wrote:
I repeat what I said in other mail- can you actually show me a tape drive
where what I propose really doesn't
Okay- I hear you both.
What do you do with QIC drives which cannnot write 2FM then?
Can you give me a model of a QIC drive that has the ``can't write 2 FM's''
and I'll see if I can find one so that I can see this problem first hand
and propose a solution to it. I find it extreamly hard to
In article [EMAIL PROTECTED] you write:
The latest port of wine references PR 14652
for patches to make -current work.
some of these ptches are however in areas I don't understand.
In particular signals, register contexts, etc.
This refers to validity of segment registers fs/gs in
On Mon, 15 Nov 1999, Rodney W. Grimes wrote:
Okay- I hear you both.
What do you do with QIC drives which cannnot write 2FM then?
Can you give me a model of a QIC drive that has the ``can't write 2 FM's''
Just about all. For that matter, it isn't just QIC drives- see all the
quirk
:Matthew Why don't we get rid of the 'e' option to ps while we
:Matthew are at it considering how much of a security hole it is.
:
:I wouldn't nuke it completely. Make -e a noop unless the real uid ps
:is running with matches the effective uid of the process being reported.
:And if ps
:I don't think this should go in at all.
:
:It increases the size of the proc structure (thereby affecting _all_
:processes) gratuitously. While I'm generally in favour of having the process
:arguments kept around, the "BSD way" has been to only examine them in user
:memory, despite that being
On Tue, 16 Nov 1999, Pierre Beyssac wrote:
[in_cksum bugs]
There's another bug in sbin/routed/rdisc.c:in_cksum() on odd packet
sizes, albeit I'm not sure it's ever triggered (does routed ever
generate odd-size packets?).
I've checked, the answer is no: apparently, in_cksum() in
Alright, it seems I have my first problem with gcc 2.95.2, (well, I'm not
really sure that it's a gcc problem). The problem is that now, after
having upgraded the compiler, fxtv will only display every other scanline
instead of all of them.
:In my opinion, doing so majorly bloats the proc struct for no good reason and
:also introduces gratuitous incompatibilities for utilities that want to modify
:their argv[*] and expect the modifications to show up in ps(1).
:
:-DG
:
:David Greenman
Well, I think there is an issue in the proc
Bob Bishop wrote:
At 11:01 am -0800 15/11/99, Matthew Jacob wrote:
I repeat what I said in other mail- can you actually show me a tape drive
where what I propose really doesn't work?
BUT I have to say that on principle I'm with Rod on this one: EOF != EOT
and mixing them up is a recipe for
Will we be updating 4.0-current to the latest BIND-8.22-P5?
_F
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Mon, 15 Nov 1999, Forrest Aldrich wrote:
Will we be updating 4.0-current to the latest BIND-8.22-P5?
Or -stable for that matter? I believe these changes are eminently
qualified, being bugfixes.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To
On Mon, 15 Nov 1999, Pierre Beyssac wrote:
On Mon, Nov 15, 1999 at 01:35:15PM -0500, Garrett Wollman wrote:
If, rather than casting pointers, the code used a union (containing
one u_int16_t and one array[2] of u_int8_t), the compiler would have
enough information to know about the
At 6:22 PM -0800 11/15/99, Matthew Dillon wrote:
Well, I think there is an issue in the proc struct bloat but I disagree
strongly about modifying argv - any worthwhile code uses setproctitle()
now simply because the argv space is highly dependant on the number of
arguments passed
In message [EMAIL PROTECTED], Sean Eric Fagan writes:
In article [EMAIL PROTECTED] you write:
The p_args.patch patch implements a cache of the commandline arguments
in the process structure and makes ps(1) pick it up from there with
sysctl rather than by groping around in the target process
In message [EMAIL PROTECTED], Matthew Dillon writes:
:http://phk.freebsd.dk/misc/p_args.patch
:
:The p_args.patch patch implements a cache of the commandline arguments
:in the process structure and makes ps(1) pick it up from there with
:sysctl rather than by groping around in the target process
In message [EMAIL PROTECTED], David Greenman writes:
I agree that we need to get rid of 'e' and any other options that allow
reading another process's environment. I don't agree with putting the command
args in the proc struct, however, for the reason that Sean mentioned above.
In my opinion,
Ben Rosengart wrote:
On Mon, 15 Nov 1999, Forrest Aldrich wrote:
Will we be updating 4.0-current to the latest BIND-8.22-P5?
Or -stable for that matter? I believe these changes are eminently
qualified, being bugfixes.
The changes are most definately not "just" bugfixes. The impact is
72 matches
Mail list logo
