Re: 5.0-RUSH: -current install testers wanted!
On Tue Oct 22, 2002 at 08:33:53AM +0200, Poul-Henning Kamp wrote: [...] > > And I want them to do it RSN: 5.0-R is only 9 days away. [...] 9 days??? There won't be another DP? A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-stable build on -current
Hello! Can 5.x properly cross-buildworld a 4.x source tree? Background info.. I have 3 machines at home: 1- graphic workstation 1Ghz, 1Gbyte of RAM dual Win2k/FreeBSD-stable 2- personal web/mail server P166 FreeBSD-stable 3- router 486 FreeBSD-stable My concern is that I won't be able to buildworld in 50 minutes as I can do now on the 1Ghz. Basically, I would turn my experiments machine (the workstation) in a real development machine, running -current and still a -stable world for the 2 other boxes. Anyone cares to share such experiences? Please CC me, I'm not on the list (yet). Thanks, A. -- From the age of uniformity, from the age of solitude, from the age of Big Brother, from the age of doublethink - greetings! msg46689/pgp0.pgp Description: PGP signature
Re: -stable build on -current
On Fri Nov 15, 2002 at 10:10:13PM +0200, Ruslan Ermilov wrote: > On Thu, Nov 14, 2002 at 09:03:58PM -0500, The Anarcat wrote: > > Hello! > > > > Can 5.x properly cross-buildworld a 4.x source tree? > > > > Background info.. I have 3 machines at home: > > > > 1- graphic workstation 1Ghz, 1Gbyte of RAM dual Win2k/FreeBSD-stable > > 2- personal web/mail server P166 FreeBSD-stable > > 3- router 486 FreeBSD-stable > > > > My concern is that I won't be able to buildworld in 50 minutes as I > > can do now on the 1Ghz. > > > > Basically, I would turn my experiments machine (the workstation) in a > > real development machine, running -current and still a -stable world > > for the 2 other boxes. > > > > Anyone cares to share such experiences? > > > > Please CC me, I'm not on the list (yet). > > > It was possible some time ago -- I've spent a few hours today making > this possible again. You need to perform the following steps to do > this: > > 1. Install ports/lang/perl5 (I haven't tested with perl5.8). > 2. Make a symlink from /usr/local/bin/pod2man to /usr/bin. > 3. Make sure all the attached commits are in your /usr/src. > > With these fixes, I have successfully built RELENG_4 world on today's > morning 5.0-CURRENT: > > : ===> etc/sendmail > : rm -f freebsd.cf > : (cd /STABLE/usr/src/etc/sendmail && m4 >-D_CF_DIR_=/STABLE/usr/src/etc/sendmail/../../contrib/sendmail/cf/ >/STABLE/usr/src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 freebsd.mc) > >freebsd.cf > : chmod 444 freebsd.cf > > But I didn't test the buildkernel yet -- you're welcome to, or I will, > on Monday. This is great news! So in other words, a -stable build on a -current machine is not necessarly some dare-devil crazy thing to do, and should be perfecly workable, right? If that is so, I'm switching. I've been waiting way too long on -stable.. If I can help debugging the crossbuild in the way, it'll make things only better, I guess. :) Thanks, A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! Major commits in the tree coming soon
On the tune of some cute Ramones song... "Beat on the Troll Beat on the Troll Beat on the Troll With a baseball bat Oh yeah! Oh yeah! Oh yeah!" A. On Thu May 29, 2003 at 06:18:42PM +0100, Thorsten Futrega wrote: > Dear users, > > The HEAD code freeze was extended by three days to > allow for some final pending work to be committed and > prepare 5.1 to be a good release. The code freeze will > > likely end sometime tomorrow, May 30. > > We ask that large scale changes still be deferred > until after 5.1 is actually released so that any > problems can be dealt with. The release > engineering team will send out emails explicitely > stating when HEAD has thawed and when large changes > like new compilers and dynamic-linked worlds can go > it. > > The most important changes I'm going to commit today: > > - Remove gcc and replace it with a new TenDRA > snapshot. > - Remove GNU tar. > - Fix httpd.ko to make it work on buggy AMD > processors. > - Drop support for 386 and 486 cpus. > - Remove ext2 support (GPL encumbered). > - Add perl 5.8 *and* python 2.2 to base. > - Remove Sendmail and replace it with Postfix. > > If anyone has any reason why these should not be > committed, I'll give a 5 hours grace time. Send > replies > to the list. > > Thank you. > > Thorsten and the rest or the release engineering team. > > __ > Yahoo! Plus - For a better Internet experience > http://uk.promotions.yahoo.com/yplus/yoffer.html > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Seul a un caractère scientifique ce qui peut être réfuté. Ce qui n'est pas réfutable relève de la magie ou de la mystique. - Popper, Karl pgp0.pgp Description: PGP signature
Re: s4bios
I put my test results in: http://anarcat.ath.cx/acpi-test/ I have done other tests using a build made after the recent ACPI import and bugfixes, and I will update the info there when completely done. A. On Tue Jun 03, 2003 at 05:32:05PM +0200, Mark Santcroos wrote: > Is there anyone that has succesfully used "acpiconf -s 4"? > > I'm very interested in your reports. If you haven't tried yet, but are > willing to help me, please report me your findings. > > Thanks > > Mark > > -- > Mark SantcroosRIPE Network Coordination Centre > http://www.ripe.net/home/mark/New Projects Group/TTM > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: s4bios
On Tue Jun 03, 2003 at 06:17:10PM -0700, Kevin Oberman wrote: > > Date: Tue, 3 Jun 2003 16:03:19 -0400 > > From: The Anarcat <[EMAIL PROTECTED]> > > Sender: [EMAIL PROTECTED] > > > > I put my test results in: > > > > http://anarcat.ath.cx/acpi-test/ > > > > I have done other tests using a build made after the recent ACPI > > import and bugfixes, and I will update the info there when completely > > done. > > Could you add the result of "sysctl hw.acpi"? As is, it's not clear that > your platform supports S1. The output will also let you know about a > number of other things. Done! More tests results underway, I'll just have to find some time to write them down... A. -- Advertisers, not governments, are the primary censors of media content in the United States today. - C. Edwin Baker http://www.ad-mad.co.uk/quotes/freespeech.htm pgp0.pgp Description: PGP signature
SMBFS automounting broken?
Hi!
Recently, I noticed that my samba shares were not automounted on
boot.
What I understand of it is that netfs_types is defined in
rc.d/mountcritlocal, but not in rc.d/mountcritremote, which makes the
code:
# Mount other network filesystems if present in /etc/fstab.
for i in ${networkfs_types}; do
fstype=${i%:*}
fsdecr=${i#*:}
[ "${fstype}" = "nfs" ] && continue
case "`mount -d -a -t ${fstype}`" in
*mount_${fstype}*)
echo -n "Mounting ${fsdecr} file systems:"
mount -a -t ${fstype}
echo '.'
;;
esac
done
does strictly nothin, since networkfs_types is empty.
A workaround would be the following patch, but I'm sure there's a
better way to do this, maybe by putting the networkfs_types in
defaults/rc.conf?
--- mountcritremote.origWed Jun 4 18:48:31 2003
+++ mountcritremote Wed Jun 4 18:55:55 2003
@@ -55,6 +55,9 @@
mount -a -t nfs
echo '.'
+# Set up the list of network filesystem types for which mounting
+# should be delayed until after network initialization.
+networkfs_types='nfs:NFS smbfs:SMB portalfs:PORTAL'
# Mount other network filesystems if present in /etc/fstab.
for i in ${networkfs_types}; do
fstype=${i%:*}
The patch to rc.conf would be very similar, of course.
I think this should be rushed in 5.1 so I CC: the REs.
A.
--
Seul a un caractère scientifique ce qui peut être réfuté. Ce qui n'est
pas réfutable relève de la magie ou de la mystique.
- Popper, Karl
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SMBFS automounting broken?
I forgot to mention this vital information: FreeBSD lenny.anarcat.ath.cx 5.1-RELEASE FreeBSD 5.1-RELEASE #4: Wed Jun 4 10:34:08 EDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LENNII i386 -rw-r--r-- 1 root wheel 0 Jun 4 07:32 /usr/src/cvsup-done.timestamp -- Conformity-the natural instinct to passively yield to that vague something recognized as authority. - Mark Twain pgp0.pgp Description: PGP signature
Re: SMBFS automounting broken?
I have opened a PR with a cleaner patch: http://www.freebsd.org/cgi/query-pr.cgi?pr=52959 A. -- Seul a un caractère scientifique ce qui peut être réfuté. Ce qui n'est pas réfutable relève de la magie ou de la mystique. - Popper, Karl pgp0.pgp Description: PGP signature
Re: ipfw feature request
You're looking for the "me" keyword. See the manpage for details. A. On Fri Aug 08, 2003 at 08:52:07AM -0400, David Hill wrote: > Hello - > I apologize in advance if this feature is already implemented. > > Is there anyway for ipfw to automatically get the IP from the interface? In > OpenBSD's PF, putting ()'s around the interface name will cause that rule to be > refreshed on an IP change, such as DHCP, making reloading the rules manually > unnecessary. > > Thanks > David > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Lorsque l'on range des objets dans des tiroirs, et que l'on a plus d'objets que de tiroirs, alors un tiroir au moins contient deux objets. - Lejeune-Dirichlet, Peter Gustav pgp0.pgp Description: PGP signature
xmms looping forever
Hi! I recently upgraded my machine from 4.7-stable to 5.0-release. The upgrade went almost smoothly. I say almost because so many things changed between 4.x and -current that I missed a few. :) But overall, I'm quite happy with the results. I had problems with almost all my apps, at first. Third part applications that weren't recompiled during the buildworld (ports) had linking problems. Take wget, for example: anarcat@lenny[~]% wget /usr/libexec/ld-elf.so.1: /usr/local/lib/libintl.so.4: Undefined symbol "stpcpy" anarcat@lenny[~]% Recopmiling wget solves the problem. Some folks pointed out to me this might be due to the fact I forgot to include COMPAT4X=yes in my make.conf. At first I had considered upgrading from -release to -current (because I'm a careless freak), so I already had my /usr/src cvsup'd to yesterday's current. So I builded world over that and installed it. Of course, that didn't solve the linking problem. But it made another problem appear. My dear user-friendly xmms now fails to start. This machine is used by the whole family here and I got really embarrassed over this. :) xmms seemed to pop an empty window, and sucked all the CPU time available on my AMD Druon 1GHz: CPU states: 14.4% user, 0.0% nice, 84.4% system, 1.2% interrupt, 0.0% idle Mem: 116M Active, 56M Inact, 92M Wired, 600K Cache, 92M Buf, 862M Free Swap: 498M Total, 1452K Used, 496M Free ... 891 anarcat1150 15820K 7060K RUN 0:05 82.69% 18.31% xmms ... So I told my self, "eh, that's -current for you!" ;) And I thought that -release wasn't so bad after all and that the upgrade didn't give me anything good anyways. So I downgraded to -release. Without success. xmms hangs as before. But it used to work on -release!!! How is that possible? Using SIGINFO, I've witnessed the following: load: 1.12 cmd: xmms 9744 [*Giant] 0.33u 0.85s 1% 7144k load: 1.19 cmd: xmms 9744 [*Giant] 0.41u 1.06s 1% 7144k load: 1.19 cmd: xmms 9744 [running] 0.41u 1.09s 1% 7144k load: 1.19 cmd: xmms 9744 [*Giant] 0.41u 1.12s 1% 7144k load: 1.19 cmd: xmms 9744 [running] 0.41u 1.14s 1% 7144k But I'm able to see this only when it system is loaded (with the compilation of a port, for example). So I suspect xmms is somehow looping over the giant lock, for some reason. truss gives me the following: sigprocmask(0x3,0x28144710,0x0) = 0 (0x0) SIGNAL 27 SIGNAL 27 gettimeofday(0x281678b8,0x0) = 0 (0x0) sigprocmask(0x3,0x28167924,0x0) = 0 (0x0) sigreturn(0xbfbff4a0)= 0 (0x0) sigreturn(0xbfbff330)= 135891072 (0x8198880) sigreturn(0xbfbff330)= 135891072 (0x8198880) sigreturn(0xbfbff330)= 135891072 (0x8198880) And ktrace: 26035 xmms CALL mmap(0,0x4788,0x3,0x1000,0x,0,0,0) 26035 xmms RET mmap 686489600/0x28eb 26035 xmms CALL munmap(0x28eb,0x4788) 26035 xmms RET munmap 0 26035 xmms CALL mprotect(0x28e3c000,0x62000,0x5) 26035 xmms RET mprotect 0 26035 xmms CALL sigprocmask(0x3,0x28144710,0) 26035 xmms RET sigprocmask 0 26035 xmms PSIG SIGPROF caught handler=0x28159510 mask=0x0 code=0x0 26035 xmms CALL gettimeofday(0x281678b8,0) 26035 xmms RET gettimeofday 0 26035 xmms CALL sigprocmask(0x3,0x28167924,0) 26035 xmms RET sigprocmask 0 26035 xmms CALL sigreturn(0xbfbff4a0) 26035 xmms RET sigreturn JUSTRETURN 26035 xmms PSIG SIGSEGV caught handler=0x28159510 mask=0x0 code=0xc 26035 xmms CALL sigreturn(0xbfbff330) 26035 xmms RET sigreturn JUSTRETURN 26035 xmms PSIG SIGSEGV caught handler=0x28159510 mask=0x0 code=0xc I include my dmesg at the end of this mail, in the meantime, here are the pcm sysctls that might be relevant: root@lenny[/usr/home/anarcat]# sysctl hw.snd hw.snd.targetirqrate: 32 hw.snd.report_soft_formats: 1 hw.snd.verbose: 1 hw.snd.unit: 0 hw.snd.maxautovchans: 2 hw.snd.pcm0.buffersize: 4096 hw.snd.pcm0.vchans: 1 I also tried: root@lenny[/usr/home/anarcat]# sysctl hw.snd hw.snd.targetirqrate: 32 hw.snd.report_soft_formats: 1 hw.snd.verbose: 1 hw.snd.unit: 0 hw.snd.maxautovchans: 0 hw.snd.pcm0.buffersize: 4096 hw.snd.pcm0.vchans: 0 I had odd crashes with xmms before, but *crashes*, no hangs. :) I am available for testing and debugging, and I am eager to solve this problem, since xmms is a must here, right now. I'd be forced to downgrade to 4.7-stable (!) but I feel I'll have the same results. :) A. Copyright (c) 1992-2003 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-RELEASE #2: Wed Feb 5 22:17:29 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LENNY Preloaded elf kernel "/boot/kernel/kernel" at 0xc05e9000. Preloaded elf module "/boot/kernel
Re: xmms looping forever
On Thu Feb 06, 2003 at 10:30:52AM -0500, Don wrote: > > I had problems with almost all my apps, at first. Third part > > applications that weren't recompiled during the buildworld (ports) had > > linking problems. Take wget, for example: > > > > anarcat@lenny[~]% wget > > /usr/libexec/ld-elf.so.1: /usr/local/lib/libintl.so.4: Undefined symbol "stpcpy" > > anarcat@lenny[~]% > > > > Recopmiling wget solves the problem. > Have you tried simply recompiling xmms? I have been using xmms on -CURRENT > and -RELEASE for about a month with 0 problems. Yep. Trice. I've been using it on -RELEASE without any problems too! Then the upgrade, then problems, even on -release. There's got to be something I'm missing here. A. -- From the age of uniformity, from the age of solitude, from the age of Big Brother, from the age of doublethink - greetings! msg51882/pgp0.pgp Description: PGP signature
Re: pcm channel duplicate lock
Can it be possible that this would be related to the problem I'm having
with xmms on -release right now? Except that -release don't have WITNESS
stuff enabled?
I guess I should try enabling debugging.
Just a shot in the dark...
A.
Lars Eggert wrote:
Got thsi when opening gnomemeeting2 while having xmms playing:
acquiring duplicate lock of same type: "pcm channel"
1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/sound.c:191
2nd pcm0:play:0 @ /usr/src/sys/dev/sound/pcm/sound.c:191
Debugger("witness_lock")
Stopped at Debugger+0x5a: xchgl %ebx,in_Debugger.0
db> trace
Debugger(c0328da1,c6283a54,c0532609,bf,eb3828ac) at Debugger+0x5a
witness_lock(c635ce40,8,c0532609,bf,eb3828d4) at witness_lock+0x142
_mtx_lock_flags(c635ce40,0,c0532609,bf,c5e5) at _mtx_lock_flags+0x63
pcm_chnalloc(c21a9e00,1,c5e5,,8) at pcm_chnalloc+0x66
dsp_open(c03a6a50,7,2000,c6612780,c0534380) at dsp_open+0x12f
spec_open(eb3829c8,eb382ae4,c0217796,eb3829c8,c03b3ae0) at
spec_open+0x37d
spec_vnoperate(eb3829c8,c03b3ae0,0,180,c6612780) at spec_vnoperate+0x18
vn_open_cred(eb382bd4,eb382cd4,0,c7575600,eb382cc0) at vn_open_cred+0x306
vn_open(eb382bd4,eb382cd4,0,295,eb382b20) at vn_open+0x29
kern_open(c6612780,888ceb0,0,7,0) at kern_open+0x197
open(c6612780,eb382d10,c0363f83,407,c6610c50) at open+0x30
syscall(875002f,2f,bfbf002f,6,0) at syscall+0x3d6
Xint0x80_syscall() at Xint0x80_syscall+0x1d
--- syscall (5, FreeBSD ELF32, open), eip = 0x2932e273, esp =
0xbfa65abc, ebp = 0xbfa65ad8 ---
Lars
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
atapicam not in NOTES?
I can't seem to find atapicam in NOTES. Is this voluntary? On the atapicam website, it says that it's been integrated into current. I can build a 5.0-release kernel with it, so has it just been forgotten from NOTES? :) Thanks A. anarcat@lenny[~/dump/c/src/sys/i386/conf]% cvs -R status NOTES === File: NOTES Status: Up-to-date Working revision:1.1070 Wed Jan 15 20:15:33 2003 Repository revision: 1.1070 /home/ncvs/src/sys/i386/conf/NOTES,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) anarcat@lenny[~/dump/c/src/sys/i386/conf]% grep -i ata NOTES anarcat@lenny[~/dump/c/src/sys/i386/conf]% msg52520/pgp0.pgp Description: PGP signature
Re: atapicam not in NOTES?
My apologies to the list for not looking in /sys/conf/NOTES before posting. I wasn't aware of the "split". :) A. msg52522/pgp0.pgp Description: PGP signature
reproducable ACPI hang on 5.0-RELEASE + Asus A7V mobo
Hello! I've been experimenting quite a bit with the new ACPI stuff from 5.0-release. I can reliably hang my box using acpiconf -s 3, both from X and the console. In X, upon wakeup, the screen is trashed with color strips. In the console, I can actually get some interaction back, but the whole thing hangs after a few seconds anyways. This is with an almost GENERIC kernel (attached), on a Asus A7V KT133 motherboard. Any concrete way to debug this? Cause a panic? Should I report this somewhere else since 5.0 != 5.x-current? :) A. Copyright (c) 1992-2003 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-RELEASE #1: Sun Feb 16 23:11:48 EST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/LENNII Preloaded elf kernel "/boot/kernel/kernel" at 0xc06a9000. Preloaded elf module "/boot/kernel/snd_emu10k1.ko" at 0xc06a90a8. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc06a9158. Preloaded elf module "/boot/kernel/radeon.ko" at 0xc06a9204. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc06a92b0. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1008992864 Hz CPU: AMD Duron(tm) Processor (1008.99-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x670 Stepping = 0 Features=0x383f9ff AMD Features=0xc044 real memory = 1207877632 (1151 MB) avail memory = 1167048704 (1112 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 Using $PIR table, 9 entries at 0xc00f1750 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 acpi_cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe600-0xe7ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 drm0: port 0xd800-0xd8ff mem 0xd700-0xd700,0xd800-0xdfff irq 11 at device 0.0 on pci1 info: [drm] AGP at 0xe600 32MB info: [drm] Initialized radeon 1.1.1 20010405 on minor 0 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xb800-0xb80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xb400-0xb41f irq 9 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xb000-0xb01f irq 9 at device 4.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at device 4.4 (no driver attached) vr0: port 0x9400-0x94ff mem 0xd680-0xd68000ff irq 9 at device 9.0 on pci0 vr0: Ethernet address: 00:50:ba:64:e3:6a miibus0: on vr0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcm0: port 0x9000-0x901f irq 5 at device 10.0 on pci0 atapci1: port 0x7000-0x703f,0x7400-0x7403,0x7800-0x7807,0x8000-0x8003,0x8400-0x8407 mem 0xd600-0xd601 irq 10 at device 17.0 on pci0 ata2: at 0x8400 on atapci1 ata3: at 0x7800 on atapci1 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 orm0: at iomem 0xcc000-0xce7ff,0xc-0xcafff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec acpi_cpu: CPU throttling enabled, 16 steps from 100% to 6.2% ad4: 38182MB [77578/16/63] at ata2-master UDMA100 MBREXT Slice 5 on ad4s2: 00 01 01 c1 0b fe bf 42 3f 00 00 00 c3 a6 54 02 |...B?.T.| [0] f:00 typ:11 s(CHS):193/1/1 e(CHS):66/254/191 s:63 l:39102147 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 cd0 at ata0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed cd1 at ata1 bus 0 target 0 lun 0 cd1: Removable CD-ROM SCSI-0 device cd1: 16.000MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present Mounting root from
Re: reproducable ACPI hang on 5.0-RELEASE + Asus A7V mobo
On Tue Feb 18, 2003 at 12:19:35AM +, Bruce Cran wrote: > > ACPI power management on Asus motherboards with the VIA chipset seems to > be quite broken. On my A7V333 I can use mode 1 (CPU off), 2 and 3 > report AE_NOT_FOUND and 4 dumps the cpu registers, while power-off on > shutdown reports an ACPI timeout error. I can power-off on shutdown (halt -p & acpiconf -s 5, if I understand this correctly). mode 1 doesn't seem to do anything, but that might just be because I can't notice the CPU stopped. 3 actually halts the drives and the fans, but powering evrything back up gives me a nice freeze. 4 just hangs. > However, these motherboards _do_ seem to have the configuration part > of ACPI working very well, whereas lots of computers don't even boot > with ACPI enabled. I don't know, but I'd guess that the priority > will be to get computers booting and configuring properly with ACPI, > before moving onto fixing problems with the power management, and > working around features which make the AML (low-level ACPI code) > work with Windows. Of course. I didn't think of that. :) A. -- Imagination is more important than knowledge - Albert Einstein msg52624/pgp0.pgp Description: PGP signature
Re: Any ideas why we can't even boot a i386 ?
On Fri Feb 28, 2003 at 04:42:14PM +0100, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, John Baldwin writes: > > >I personally think that we should not support the 80386 in 5.x. > >However when that has been brought up before there were a lot of > >theoretical objections. > > Well, unless somebody actually manages to put a -current on an i386 > and run the tests I suggested in a couple of weeks, then I think > those theoretical objections stand very weakly in the light of > proven reality :-) Anyways, nothing keeps a old hardware freak (like me) to take over the maintainership of 386-related stuff, if he wants to. Thing is, no one stepped forward at this time, so I guess this settles the future of the 386. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Plea for base system trim
On Wed Mar 05, 2003 at 02:29:00PM -0800, Doug Barton wrote: > On Wed, 5 Mar 2003, Adrian Steinmann wrote: > > > > > I use this command in my build script to force apache13+modssl to use > > the openssl in base. > > > > # Use base openssl (OpenSSL 0.9.7a as of Feb 19 2003) > > cd /usr/ports/www/apache13-modssl > > cp Makefile Makefile- > > sed -ie 's/^\.include.*Makefile\.ssl.*$/OPENSSLBASE=\/usr/' Makefile- >Makefile > > You could instead do: > > sed Makefile > makefile > > The lowercase makefile will be used by make in preference to Makefile. Juste jumping in... Couldn't you just: sed -i.orig -e Makefile For example: [EMAIL PROTECTED] cat > foo this is a test [EMAIL PROTECTED] sed -i.orig -e 's/test/gizmo/' foo [EMAIL PROTECTED] diff -u foo.orig foo --- foo.origWed Mar 5 17:54:09 2003 +++ foo Wed Mar 5 17:54:13 2003 @@ -1 +1 @@ -this is a test +this is a gizmo Much simpler, unless I missed something. A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Plea for base system trim
On Wed Mar 05, 2003 at 03:52:22PM -0800, Doug Barton wrote: > On Wed, 5 Mar 2003, The Anarcat wrote: > > > Juste jumping in... Couldn't you just: > > > > sed -i.orig -e Makefile > > No, because sed -i is evil, and will cause you to have hairy palms. What? A. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
playing mp3s and burning a cd
I'm running 5.0-release, so I'm not sure this is the proper forum, but I'm trying my luck anyways. I used to listen to MP3s (using xmms) while burning CDs (using cdrecord) and it used to work fine on -stable. Now on 5.0-release, the music gets *slw* as soon as the massive IO gets on. I presume it's related to the interrupt problems the current branch is generally having. Anyone else seeing this? Should I upgrade to -current? A. -- Seul a un caractère scientifique ce qui peut être réfuté. Ce qui n'est pas réfutable relève de la magie ou de la mystique. - Popper, Karl pgp0.pgp Description: PGP signature
Re: playing mp3s and burning a cd
Should a PR be filed or some QA team contacted to make sure this problem doesn't stay alive in 5.2? :) A. On Mon Mar 24, 2003 at 01:45:26PM -0500, Craig Reyenga wrote: > I see this too: when I listen to tunes and untar a file, the music plays at > about .7x the speed, and sounds kind of "robotic", even with xmms niced > to -20, and tar/gzip at +20. I am running 5.0-CURRENT-20030320-JPSNAP, so I > doubt an 'upgrade' is really going to do anything for you at this time. > > -Craig > > From: "The Anarcat" <[EMAIL PROTECTED]> > >Subject: playing mp3s and burning a cd > >I'm running 5.0-release, so I'm not sure this is the proper forum, but > >I'm trying my luck anyways. > > >I used to listen to MP3s (using xmms) while burning CDs (using > >cdrecord) and it used to work fine on -stable. > > >Now on 5.0-release, the music gets *slw* as soon as the massive IO > >gets on. I presume it's related to the interrupt problems the current > >branch is generally having. > > >Anyone else seeing this? Should I upgrade to -current? > > >A. > > >-- > >Seul a un caractère scientifique ce qui peut être réfuté. Ce qui n'est > >pas réfutable relève de la magie ou de la mystique. > >- Popper, Karl > > > > -- Si les triangles avaient un Dieu, ils lui donneraient trois côtés. - Montesquieu, Lettres persanes pgp0.pgp Description: PGP signature
Re: playing mp3s and burning a cd
On Mon Mar 24, 2003 at 02:14:48PM -0500, Don wrote: > > Should a PR be filed or some QA team contacted to make sure this > > problem doesn't stay alive in 5.2? :) > This isn't, by chance, a problem with your setting for the > sysctl "hw.ata.atapi_dma" is it? No idea. [EMAIL PROTECTED] sysctl hw.ata.atapi_dma hw.ata.atapi_dma: 0 [EMAIL PROTECTED] should I enable it? I guess I'm out to burn another CD and just test that.. A. -- The idea that Bill Gates has appeared like a knight in shining armour to lead all customers out of a mire of technological chaos neatly ignores the fact that it was he who, by peddling second-rate technology, led them into it in the first place. - Douglas Adams (1952-2001) pgp0.pgp Description: PGP signature
Solved??? Re: playing mp3s and burning a cd
On Mon Mar 24, 2003 at 02:14:48PM -0500, Don wrote: > > Should a PR be filed or some QA team contacted to make sure this > > problem doesn't stay alive in 5.2? :) > This isn't, by chance, a problem with your setting for the > sysctl "hw.ata.atapi_dma" is it? How extraordinarly cute! This solves it! I'm currently listening to Me, Mom and Morgentaler and burning a 4x CD without any slowdown, this is great. So I guess a "workaround" is to toggle DMA for my ATAPI bus. Indeed, the burner is IDE and should be working on DMA mode to get optimal performance. The thing is that atapicam hides the DMA/PIO magic from the usual boot messagesand there's therefore no way to see wether the device is in DMA mode unless you compile in both cd0 and acd0 which I heard isn't recommended... A. PS: what's the proper way to enable ATAPI DMA in the loader.conf file? I don't see any flag WRT that there.. I'm tempted to add: set hw.ata.atapi_cam=1 anywhere there... Copyright (c) 1992-2003 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-RELEASE #2: Fri Mar 7 15:05:32 EST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/LENNII Preloaded elf kernel "/boot/kernel/kernel" at 0xc06ea000. Preloaded elf module "/boot/kernel/snd_emu10k1.ko" at 0xc06ea0a8. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc06ea158. Preloaded elf module "/boot/kernel/radeon.ko" at 0xc06ea204. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc06ea2b0. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1008992834 Hz CPU: AMD Duron(tm) Processor (1008.99-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x670 Stepping = 0 Features=0x383f9ff AMD Features=0xc044 real memory = 1207877632 (1151 MB) avail memory = 1166782464 (1112 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 Using $PIR table, 9 entries at 0xc00f1750 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 acpi_cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe600-0xe7ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 drm0: port 0xd800-0xd8ff mem 0xd700-0xd700,0xd800-0xdfff irq 11 at device 0.0 on pci1 info: [drm] AGP at 0xe600 32MB info: [drm] Initialized radeon 1.1.1 20010405 on minor 0 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xb800-0xb80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xb400-0xb41f irq 9 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ugen0: Color FlatbedScanner 22, rev 1.00/1.00, addr 2 uhci1: port 0xb000-0xb01f irq 9 at device 4.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at device 4.4 (no driver attached) vr0: port 0x9400-0x94ff mem 0xd680-0xd68000ff irq 9 at device 9.0 on pci0 vr0: Ethernet address: 00:50:ba:64:e3:6a miibus0: on vr0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcm0: port 0x9000-0x901f irq 5 at device 10.0 on pci0 atapci1: port 0x7000-0x703f,0x7400-0x7403,0x7800-0x7807,0x8000-0x8003,0x8400-0x8407 mem 0xd600-0xd601 irq 10 at device 17.0 on pci0 ata2: at 0x8400 on atapci1 ata3: at 0x7800 on atapci1 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 orm0: at iomem 0xcc000-0xce7ff,0xc-0xcafff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec IPsec: Initialized Security Association Processing. acpi_cpu: CPU throttling enabled, 16 steps from 100% to 6.2% ad4: 38182MB [77578/16/63] at ata2-master UDMA100 MBREXT Slice 5 on ad4s2: 00 01 c1 ff 0b fe ff ff 3f 00 00 00 4d 59 18 02 |?...MY..| [0] f:00 typ:11 s(CHS):255/1/193
Broken DMA devices
On Mon Mar 24, 2003 at 11:52:07AM -0800, Kevin Oberman wrote: > > PS: what's the proper way to enable ATAPI DMA in the loader.conf file? > > I don't see any flag WRT that there.. I'm tempted to add: > > > > set hw.ata.atapi_cam=3D1 > > > > anywhere there... > > Close. Add: > hw.ata.atapi_dma="1"# Run the CD-ROM/DVD in DMA mode > to /boot/loader.conf. > > This should be in almost EVERY /boot/loader.conf. The default is 0 (PIO) > because DMA is broken on at least a few early CD readers, but it is > very rare to have it fail. (I've never seen it.) Can't the ata drivers detect that condition or recognize the set of drives that are broken instead of penalizing everyone else? A. -- Advertisers, not governments, are the primary censors of media content in the United States today. - C. Edwin Baker http://www.ad-mad.co.uk/quotes/freespeech.htm pgp0.pgp Description: PGP signature
Re: Solved??? Re: playing mp3s and burning a cd
On Mon Mar 24, 2003 at 03:33:51PM -0500, Don wrote: > > On Mon Mar 24, 2003 at 02:14:48PM -0500, Don wrote: > > > > Should a PR be filed or some QA team contacted to make sure this > > > > problem doesn't stay alive in 5.2? :) > > > This isn't, by chance, a problem with your setting for the > > > sysctl "hw.ata.atapi_dma" is it? > > How extraordinarly cute! This solves it! I'm currently listening to > > Me, Mom and Morgentaler and burning a 4x CD without any slowdown, this > > is great. > Glad to be of help. Anytime you have odd system problems like that give > "sysctl -a" a perusal. Sometimes you will be surprised at what you find. > > There was definitely a reason for turning off DMA access for atapi devices > by default, I just can not remember why. I'm sure this issue and the > reason were mentioned on the list already. Right... Another dig through the archives I guess. :( > > PS: what's the proper way to enable ATAPI DMA in the loader.conf file? > > I don't see any flag WRT that there.. I'm tempted to add: > > > > set hw.ata.atapi_cam=1 > hw.ata.atapi_dma not _cam :) Now *that* was an odd typo. A. -- Conformity-the natural instinct to passively yield to that vague something recognized as authority. - Mark Twain pgp0.pgp Description: PGP signature
Re: Broken DMA devices
On Tue Mar 25, 2003 at 08:16:28AM +0100, Soeren Schmidt wrote: > It seems The Anarcat wrote: > > > hw.ata.atapi_dma="1"# Run the CD-ROM/DVD in DMA mode > > > to /boot/loader.conf. > > > > > > This should be in almost EVERY /boot/loader.conf. The default is 0 (PIO) > > > because DMA is broken on at least a few early CD readers, but it is > > > very rare to have it fail. (I've never seen it.) > > > > Can't the ata drivers detect that condition or recognize the set of > > drives that are broken instead of penalizing everyone else? > > ATAPI DMA is more likely to be broken than to be working, it is a > function of both controller chip and device, in some situations even > a function of what master/slave device combo we have.. > > There is a reason that almost all OS's out there has it disabled as default :) Thanks for those precisions... This could be a FAQ, pertaining also to how to enable it. So it's enabled system-wide? Can't it be done at the bus or device level? A. -- Advertisers, not governments, are the primary censors of media content in the United States today. - C. Edwin Baker http://www.ad-mad.co.uk/quotes/freespeech.htm pgp0.pgp Description: PGP signature
Re: several background fsck panics
On Tue Mar 25, 2003 at 03:54:58AM -0800, Terry Lambert wrote: > Alexander Langer wrote: > > Thus spake Terry Lambert ([EMAIL PROTECTED]): > > > Disable write caching on your ATA drive. You should be able to > > > "safely" reset after that. > > > > Good idea, thanks. Nevertheless: I don't think the system should > > panic on background fsck's, while a manual fsck works. > > A manual fsck can deal with corrupt data. > > A background fsck can only deal with invalid cylinder group > bitmaps, and operates on a snapshot. > > For a background fsck to be feasible, the FS has to be in a > self-consistent state already, which it wasn't. > > When you killed the power on your system and reset it, you > lost the cached data sitting in the ATA disk. This is due > to the fact that the ATA disk lied, and claimed that it had > committed some writes to stable storage, when in fact it had > only copied them to the disk cache. As a result, when the > device reset happened, you lost some writes which were in > progress. Therefore you disk image was corrupt, and so your > FS was *not* in a self-consistent state. Shouldn't fsck run in the foreground for disks setup with WC? That would be a quick hack solving this issue altogether. A. -- Conformity-the natural instinct to passively yield to that vague something recognized as authority. - Mark Twain pgp0.pgp Description: PGP signature
Re: Broken DMA devices
On Tue Mar 25, 2003 at 06:28:38PM +0100, Soeren Schmidt wrote: > It seems The Anarcat wrote: > > > > Thanks for those precisions... This could be a FAQ, pertaining also to > > how to enable it. > > > > So it's enabled system-wide? Can't it be done at the bus or device > > level? > > You can set the transfer mode of any ATA/ATAPI device with atacontrol... This is great. I should have looked at that earlier. So it looks like the sysctl, boot loader-time setting isn't really useful since I can set the modes when the kernel is booted, contrarly to the sysctl setting. And it still solves the skipping MP3 problem I had. Thanks for those precisions and that atacontrol pearl, Soeren. :) A. -- Advertisers, not governments, are the primary censors of media content in the United States today. - C. Edwin Baker http://www.ad-mad.co.uk/quotes/freespeech.htm pgp0.pgp Description: PGP signature
LOR at boot
Hello! I'm running 5.0-RELEASE and this might have already been reported and/or fixed, but here it goes anyways. Copyright (c) 1992-2003 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-RELEASE #3: Mon Mar 24 15:39:05 EST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/LENNII Preloaded elf kernel "/boot/kernel/kernel" at 0xc0735000. Preloaded elf module "/boot/kernel/snd_emu10k1.ko" at 0xc07350b4. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc0735164. Preloaded elf module "/boot/kernel/radeon.ko" at 0xc0735210. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc07352bc. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1008992999 Hz CPU: AMD Duron(tm) Processor (1008.99-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x670 Stepping = 0 Features=0x383f9ff AMD Features=0xc044 real memory = 1207877632 (1151 MB) avail memory = 1166475264 (1112 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 Using $PIR table, 9 entries at 0xc00f1750 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 acpi_cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe600-0xe7ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 drm0: port 0xd800-0xd8ff mem 0xd700-0xd700,0xd800-0xdfff irq 11 at device 0.0 on pci1 info: [drm] AGP at 0xe600 32MB info: [drm] Initialized radeon 1.1.1 20010405 on minor 0 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xb800-0xb80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xb400-0xb41f irq 9 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port error, restarting port 1 uhub0: port error, giving up port 1 ugen0: Color FlatbedScanner 22, rev 1.00/1.00, addr 2 uhub0: port error, restarting port 2 uhub0: port error, giving up port 2 uhci1: port 0xb000-0xb01f irq 9 at device 4.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub1: port error, restarting port 1 uhub1: port error, giving up port 1 uhub1: port error, restarting port 2 uhub1: port error, giving up port 2 pci0: at device 4.4 (no driver attached) vr0: port 0x9400-0x94ff mem 0xd680-0xd68000ff irq 9 at device 9.0 on pci0 ../../../vm/uma_core.c:1330: could sleep with "vr0" locked from ../../../pci/if_vr.c:666 vr0: Ethernet address: 00:50:ba:64:e3:6a miibus0: on vr0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ../../../vm/uma_core.c:1330: could sleep with "vr0" locked from ../../../pci/if_vr.c:292 pcm0: port 0x9000-0x901f irq 5 at device 10.0 on pci0 atapci1: port 0x7000-0x703f,0x7400-0x7403,0x7800-0x7807,0x8000-0x8003,0x8400-0x8407 mem 0xd600-0xd601 irq 10 at device 17.0 on pci0 ata2: at 0x8400 on atapci1 ata3: at 0x7800 on atapci1 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 orm0: at iomem 0xcc000-0xce7ff,0xc-0xcafff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec IPsec: Initialized Security Association Processing. acpi_cpu: CPU throttling enabled, 16 steps from 100% to 6.2% ad4: 38182MB [77578/16/63] at ata2-master UDMA100 MBREXT Slice 5 on ad4s2: 00 01 c1 ff 0b fe ff ff 3f 00 00 00 4d 59 18 02 |?...MY..| [0] f:00 typ:11 s(CHS):255/1/193 e(CHS):255/254/255 s:63 l:35150157 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 cd0 at ata0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed cd1 at ata1 bus 0 target 0 lun
Re: Bluetooth on IBM T30 (USB device problem)
On mer mar 26, 2003 at 09:38:57 -0800, Maksim Yevmenkin wrote: > Hello Lee, > > >I'm playing with Bluetooth on my T30 as well. I've activated legacy > >USB support in BIOS, but still get > > > > Mar 26 08:41:03 tylendel kernel: uhub2: device problem, disabling port 1 Just a "me too".. somehow: I've seen this happen with my Acer Flatbed scanner. It would just jam while scanning, xscanimage would hang and I'd see that exact same message on my console. Nothing short of rebooting would solve this. A. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Removing Sendmail
On Wed Apr 02, 2003 at 02:29:30PM -0500, John Baldwin wrote: > > > I really think splitting the base in some sub-parts would it make much > > easier to do NO_SENDMAIL on my own. So I had to remove each not required > > file separately. That's no good solution. > > [stepping back a bit ] > > I find an odd situation here whenever this topic comes up. One the > one hand, people are always wanting to split the entire base system > up into small packages for each little piece of the base. On the > other hand, one of FreeBSD's selling points in real-world environments > is that it doesn't have a bunch of little packages for the base system > like Linux distros. Do people really prefer something like having > rpm's for /bin/ps to having one lump base dist for all of /bin, /sbin, > etc.? Those two aren't necessarly in contradiction. We could provide a myriad of small packages and a "wrapper package" containing them all. Debian has "tasks" to deal with this, it's a meta package that solely depend on other packages. We could do something similar, or even better: make a meta package that actually embeds the other package files. No I don't have any patches. A. -- Advertisers, not governments, are the primary censors of media content in the United States today. - C. Edwin Baker http://www.ad-mad.co.uk/quotes/freespeech.htm pgp0.pgp Description: PGP signature
Re: SMBFS automounting broken?
On Fri Jun 06, 2003 at 11:23:37AM -0700, Gordon Tetlow wrote: > On Wed, Jun 04, 2003 at 06:57:09PM -0400, The Anarcat wrote: > > Hi! > > > > Recently, I noticed that my samba shares were not automounted on > > boot. > > > > What I understand of it is that netfs_types is defined in > > rc.d/mountcritlocal, but not in rc.d/mountcritremote, which makes the > > code: > > You are a little late. I committed a solution to this problem on > the 1st. I asked re@ for permission to MFC but that request was > denied (understandably from my point of view). Oh, sorry for the noise.. :) A. -- C'est avec les pierres de la loi qu'on a bâti les prisons, et avec les briques de la religion, les bordels. - Blake, William pgp0.pgp Description: PGP signature
(fwd) Re: cvs commit: ports/sysutils Makefile ports/sysutils/rclean Makefile distinfo pkg-comment pkg-descr pkg-plist
[putting anti-flame on] -- N'aimer qu'un seul est barbarie, car c'est au détriment de tous les autres. Fût-ce l'amour de Dieu. - Nietzsche, "Par delà le bien et le mal" --- Begin Message --- On Wed, 15 May 2002 13:16:52 -0400 The Anarcat <[EMAIL PROTECTED]> wrote: > Why isn't this part of base? It needs agreement of -current. Why don't you ask there ? -- Computer science is no more about computers than astronomy is about telescopes - E. Dijkstra --- End Message --- msg38383/pgp0.pgp Description: PGP signature
Re: cvs commit: ports/sysutils Makefile ports/sysutils/rclean Makefile distinfo pkg-comment pkg-descr pkg-plist
On Wed May 15, 2002 at 09:55:42PM +0300, Maxim Sobolev wrote: > The Anarcat wrote: > > > > [putting anti-flame on] s/on/suit on/ > To invite a normal discussion you should at least provide the > following information: Well, I expected people to look at the port, but I'll provide more information here. > - What `rclean' is for? " rclean provides a command-line tool to order and clean content of rc.conf, using option order from /etc/defaults/rc.conf and printing only choices that were different by the default value in /etc/rc.conf. Output is customizable from "only used values" to "full listing". WWW: http://www.lapo.it/rclean/ " > - Why do you think it could be useful in base system? Well, that part is more personal, but I think it could remove the tendency people have of complaining about the current /etc/defaults scheme. There has been a few threads about problems arising when /etc/defaults/rc.conf was getting updated. I think rclean might help solve those problems, in the same spirit mergemaster helps managing configuration file changes. > Your assumption that the list readers know answers to those two > questions (or would care enough to dig for the answers by themselves) > is incorrect and entitles you not to flamewar but to "ugh, what this > is all about?" reaction from their part and likely to the complete > lack of any discussion at all as a result. I wonder what's best after all. ;) I must admit I was being a bit blunt by just challenging people to put this in base, somehow assuming everything should go in. In other words, the question is: "Why should this go in base?" rather than: "Why isn't this in base?" My apologies. A. -- Un éducateur dans l'âme ne prend rien au sérieux que par rapport à ses disciples -- soi-même non excepté. - Nietzsche, "Par delà le bien et le mal" msg38387/pgp0.pgp Description: PGP signature
Re: bash in /usr/local/bin?
[This email contains coarse language due to the absurdity of the thread level we're in. My apologies to those offended. Also, my apologies to the author of the original mail. You have triggered very sensitive areas of my mind. :)] [This probably belongs to -chat, -flame (we should create that one) or IRC, anyways] On Sun, 12 Aug 2001, Jim Bryant wrote: > Also, dinosaurs or not, DOD is now an INVESTOR in the FreeBSD system. Name > any other group besides maybe BSDI that has provided $1.4 million [USD] to > the project. > > We should look towards making FreeBSD the open-source OS of choice in the > DOD environment, in which Linux has already made major inroads where FreeBSD > isn't even allowed to tread yet. I do not agree with that statement. We should not distort FreeBSD's vision to fit what a few people believe to be DOD wishes. Even if it would be the DODs wishes, I say: fuck the DOD. Fuck the army. FreeBSD is a Free project. We don't have to comply to some freakin military. > Actually, it is up to us to resolve this. I don't think you understand how > DOD operates. The vendor makes the changes, not DOD. Not the admin. And FreeBSD is the *vendor*? I don't think so. At least I don't hope so. If I'm mistaken, slap me, but the project should not bend over for any big guy who pulls out enough money. I know this will sound ridiculous, but what if Mucrosoft put 1M$ in FBSD? Would we fucking bend over? I hope not. > Moving the non-GPL shells to /bin is a trivial request that can solve > problems that you obviously don't understand. Then we could also answer a trivial request such as making apache part of the base system! If the DOD need a webserver, they're screwed? They panic? What the heck is that? And why should we care about such d**kheads? > DOD will is a vast new market for FreeBSD, and if we don't think ahead now > and consider what will make admins recommend FreeBSD over Linux, Solaris, or > HP-UX, then we'll never reach the kind of market penetration that Linux, > Solaris, and HP-UX have in the DOD market. Saying: "the military uses our sw, you should use it too" should make admins use the sw? What a sick world we're in. Wasn't the DOD using NT? > Key to this is an admin-friendly > environment designed to get around the pre-cambrian attitudes that prevent > DOD admins from using standard tools just because it's in the wrong place on > the disk array or because it's considered a third-party option, or even > worse: freeware [h! step away from the keyboard, son. you going to > prison, boy!]. Bash standard? Funny. I had very good comments on the easiness (sp?) ppl have installing third party apps in the install process. And the ports collection, and the packages, etc... FreeBSD is very admin friendly, IMHO. > DOD is only an example of an organization that can benefit from such a > trivial change. They can already get this with Sun, and probably HP as well > [I haven't seen the latest minor release to 11.x, but I bet they are > following Sun's lead]. I don't give a flying fluck about the DOD, they can go blow themselves up on freakin Mars. Seriously. > Try thinking outside the box sometime. If you want a "traditional" unix, I > think there is still a PDP-11 emulator and DL01 image of V7 at > gatekeeper.dec.com. Yeah. Let's go with the New Technology: NT. All these buzzwords and semantics are messing things up here. It's not a matter of tradition, it's a matter of license (bash is GPL, FBSD is BSD-licensed), and functionality (bash != sh). See also the comment about resistance to have perl in the base system. Linux have bash in the base system simply because there's no other free close relative to sh around. > I'm more for an evolutionary unix where the idea of what's standard changes > to reflect the needs of it's admins and users in diverse environments. As much as I appreciate "evolution", I think this mentality is exactly the thing that makes us pull away from support from old hardware. That's a shame. > going nowhere due to outdated beliefs "oh, but that belongs in > /usr/local/bin". Again, it's not a belief. It's a philosophy that is behind FreeBSD. I would actually like to get *more* stuff out of the base system. Small is beautiful. We could probably include about 10 other shells in /bin just on the grounds that it's "standard" or "useful". > If something after years of use becomes a standard tool, > it needs to be moved into the base distribution. I give perl as a prime > example of one time that this actually happened, despite the arguments for > or against perl, it *IS* a standard tool, and it *IS* expected to be > available. Perl might be a standard tool (again, a funny thought) but being "available" does not necessarly mean to have it in the base system. Anyways, this has probably been burnt to death long time ago, I should not get into this. > My argument for the trivial move of the non-GPL shells to /bin, so long as > they
Re: My Recommended Development/Testing environment for -current
On Tue, 28 Aug 2001, Brandon D. Valentine wrote: > On Tue, 28 Aug 2001, Matt Dillon wrote: > [snip of diskless comments] You wouldn't happen to have sample configs around, wouldn't you? :) > I will say though, on the subject of NFS, that one of the things that > I'm almost annoyed enough with to start hacking on is the BSDs lack of > autofs support. Linux now has a kickass autofs automounter. The BSDs > are, to the best of my knowledge, the only OS left without one. Wrong. > Am-utils (the contrib source for our amd) has been kicking around autofs > support for a while now but still does not appear to have anything > release quality. Am-utils, while being a quite complex piece of software, does fullfil the task of "autofs". It does need extra configuration compared to Linux's autofs though. For the record, I automount my cdr, cdrom, zip and floppy drives (both in ufs and msdos mode) using this configuration files: ---8<--- Cut here [amd.mnt] -8< cdr type:=cdfs;fs:=/cdr;dev:=/dev/cd0c;opts:=ro,nodev,nosuid cdrom type:=cdfs;fs:=/cdrom;dev:=/dev/acd0c;opts:=ro,nodev,nosuid fat type:=pcfs;fs:=/fat;dev:=/dev/fd0;opts:=nosuid,nodev flp type:=ufs;fs:=/flp;dev:=/dev/fd0;opts:=nosuid,nodev zip type:=ufs;fs:=/zip;dev:=/dev/afd0;opts:=nosuid,nodev zap type:=pcfs;fs:=/zap;dev:=/dev/afd0s4;opts:=nosuid,nodev ---8<--- Cut here [amd.mnt] -8< ---8<--- Cut here [amd.conf] -8< [ global ] normalize_hostnames =no print_pid = no restart_mounts = yes #auto_dir = /n log_file = /var/log/amd log_options =all #debug_options = all plock = no cache_duration =6 dismount_interval = 20 selectors_on_default = yes # config.guess picks up "sunos5" and I don't want to edit my maps yet os = sos5 # if you print_version after setting up "os", it will show it. print_version = no map_type = file search_path = /etc/amdmaps:/usr/lib/amd:/usr/local/AMD/lib:/etc browsable_dirs = yes [ /mnt ] map_name = amd.mnt ---8<--- Cut here [amd.conf] -8< I think I will dare opening a pr making this default config files. :) > It's a nuisance to have to run special scripts to > parse your auto.* maps into stuff amd can understand in an NIS > environment. I am not sure I completely understand that, but you must expect having to reconfigure stuff to accomodate new software... I guess you want to port autofs to fbsd, eh? :) A. PGP signature
