Re: 5.x, 6.x and CPUTYPE
On 11/8/05, Chuck Swiger [EMAIL PROTECTED] wrote: Craig Boston wrote: On Tue, Nov 08, 2005 at 12:05:13PM +1000, Joel Hatton wrote: Thanks, Craig. I'm glad to hear that I'm not alone in pursuing this method. Do you know of any particular disadvantages of continuing with this less-than-optimised model - I guess I mean, is this something that is likely to break or become uneconomical at some point? It won't break; after all the release binaries are targeted for 386 (or maybe 486 now) in order to be able to run on anything. You might need to update make.conf with the pentiumpro name just in case they ever drop the i686 alias, but that's about it. Remeber that MacOSX/i386 requires the latest SSE feature set? Well, some day, although in a much more justified way, that might happen to FreeBSD. I don't think it'll happen earlier than 5-10 years from now, but it will. It doesn't mean you'll have to put something in your configs - just that the default target will include optimizations for some instructions. I still don't understand many of this gcc scheduling stuff, but -mfpmath=sse should give a noticable boost to all code, not matter when it was written. Also, things like OpenSSH and mplayer were manually optimized to benefit from MMX, MMX2, 3DNow, 3DNowEx, SSE, SSE2... (that's what mplayer says about my athlon64 cpu, it was compiled without runtime cpu detection). So that's a matter of taste. It's not in vain to have a dozen scheduling configurations for a medium site, but it could live without that. Personally, I think, if there's a way to automate everything nicely, then one should do it. Package building is another issue, but I think FreeBSD will gain a good world-wide distributed compilation network, where you can get a binary with some specific options and optimizations, - in the months to come. Let's hope for that. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_6 tinderbox] failure on i386/i386
TB --- 2005-11-08 06:48:07 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-11-08 06:48:07 - starting RELENG_6 tinderbox run for i386/i386 TB --- 2005-11-08 06:48:07 - cleaning the object tree TB --- 2005-11-08 06:49:22 - checking out the source tree TB --- 2005-11-08 06:49:22 - cd /tinderbox/RELENG_6/i386/i386 TB --- 2005-11-08 06:49:22 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2005-11-08 07:17:16 - building world (CFLAGS=-O -pipe) TB --- 2005-11-08 07:17:16 - cd /src TB --- 2005-11-08 07:17:16 - /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything TB --- 2005-11-08 08:22:07 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2005-11-08 08:22:07 - cd /src TB --- 2005-11-08 08:22:07 - /usr/bin/make buildkernel KERNCONF=GENERIC Kernel build for GENERIC started on Tue Nov 8 08:22:08 UTC 2005 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for GENERIC completed on Tue Nov 8 08:40:43 UTC 2005 TB --- 2005-11-08 08:40:43 - generating LINT kernel config TB --- 2005-11-08 08:40:43 - cd /src/sys/i386/conf TB --- 2005-11-08 08:40:43 - /usr/bin/make -B LINT TB --- 2005-11-08 08:40:43 - building LINT kernel (COPTFLAGS=-O -pipe) TB --- 2005-11-08 08:40:43 - cd /src TB --- 2005-11-08 08:40:43 - /usr/bin/make buildkernel KERNCONF=LINT Kernel build for LINT started on Tue Nov 8 08:40:44 UTC 2005 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies [...] rm -f .newdep /usr/bin/make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP=cc -E CC=cc xargs mkdep -a -f .newdep -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/contrib/dev/ath -I/src/sys/contrib/dev/ath/freebsd -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding /src/sys/dev/acpi_support/acpi_asus.c:50:18: acpi.h: No such file or directory /src/sys/dev/acpi_support/acpi_fujitsu.c:40:18: acpi.h: No such file or directory /src/sys/dev/acpi_support/acpi_panasonic.c:40:18: acpi.h: No such file or directory /src/sys/dev/acpi_support/acpi_sony.c:34:18: acpi.h: No such file or directory /src/sys/dev/acpi_support/acpi_toshiba.c:37:18: acpi.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-08 08:42:32 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-08 08:42:32 - ERROR: failed to build lint kernel TB --- 2005-11-08 08:42:32 - tinderbox aborted ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: New user confused by need to do huge upgrade
On Tuesday 08 Nov 2005 00:30, Stephen Hurd wrote: I installed from two CDs, and got a working KDE system. Now, I want to [snip] Heh, essentially the problem is this... before a release, the ports tree is stabalized... everything builds and works together, broken dependencies are fixed, all is good with the world. This is the ports tree which is included in the release. After the release, More Stuff (tm) is added/updated/etc. By doing a cvsup, you asked for the newest version of all the ports, one which is not necessarily stable... dependencies may be broken, things may not work etc. Doing a cvsup in ports is like tracking -STABLE for ports. If you had not done the cvsup, FF would have built and installed nicely. IMHO, CVSupping ports is subject to the same caveats as tracking -STABLE (See section 20.2.2 in the handbook) Hi, Stephen You have hit the nail on the head! I fundamentally misunderstood the purpose of CVSupping ports. It is not like syncing in Gentoo at all! I probably did not read the manual carefully enough; I got the idea that it was something to do routinely before making a kernel. To all others who responded. Thanks! It is true what they say about the great level of user support for FreeBSD. I will take the Gentoo machine down again at the end of the week when it is not needed and start afresh with 6.0, and try to do it properly next time! All the best Alistair ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Is 6.0 the new stable or is it 5.4??
newbie wants to know. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Is 6.0 the new stable or is it 5.4??
newbie wants to know :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is 6.0 the new stable or is it 5.4??
As the front page of the website says, the 5.x series of releases are now Legacy. 6.0 is now considered the stable release platform, but 5.x will be supported for a while longer, I think. Eriq Lamar wrote: newbie wants to know :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD6 /bin/tcsh ls-F : Floating exception (core dumped)
On Tue, Nov 08, 2005 at 02:46:28PM +0900, TOMITA Yoshinori wrote: [...] Here is a tiny patch. Please send-pr this, so that it doesn't get lost. This would probably fix http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/88538 as well. Thanks. -- Jonathan Chen [EMAIL PROTECTED]Once is dumb luck. Twice is coincidence. Three times and Somebody Is Trying To Tell You Something. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: timecounter and Hz quality in kern RELENG_6
Hello, thanks to Oliver and Michael for explain me the mechanics behind timecounter and Hz quality. I have send the question, why i have to wonder about different IRQ-Counts but same HZ. It is really thaat HZ on both machines is the same. I have only knowed the old behavior. I set the HZ over Options HZ in my Kernelconfig, and then i could see that the IRQCount's on clk are alwas the same value as HZ +- a few tics. So that i have thinked ( and feeled on busy machines) that the IRQ-work is more smooth and they are less holes in responsitivity if the HZ is going to an Value 1000. So i have alwas set HZ to 2000 on every machine. If i have the answers and the mechanics behind timecounter and Hz quality right understand, so i have no more modify the HZ Value to become an smooth polling of the interupts. if i be right the smooth behavior comes with the calculation from Hz quality. Please correct me if i am wrong. thanks to all and best regards michael 2005/11/7, Michael Schuh [EMAIL PROTECTED]: Hello, i be very surprised about the performance of RELENG_6. Congratulations to the entire Team for this very good work. Now i have 2 Machines installed with 6.0-RC1, and i have seen that on both machines the Hz is differntly with GENERIC-Kernel. Machine A is an Sempron 2400+ that runs as 2500+ (i have tuned the clock to best RAM-Performace) Machine B is an Duron 700MHz On Machine A i got an Hz from 2000 effectively systat -vmstat 1 show me 2000 IRQ/s on clk sysctl say's 1000i think, but not sure On Machine B i got an Hz from 1000 effectively systat-vmstat 1 show me 1000 IRQ/s on clk After digging in the source i have found that timec.c have an routine for computing the so called Hz quality. Can anyone explain me the mystics behind Hz quality, and why or how this quality is computed and what are the efforts? My knowledge is not deep enough to know these details. thanks best regards michael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
xl1: watchdog timeout on 6-STABLE with 3c575B cardbus NIC
Since upgrading to 6-STABLE I get errors on my cardbus NIC. If I have the patience to wait for echo on an ssh terminal one could say that it works, but in a real world it's unusable. Hopefully helpful details: * Worked fine on 5.4 * Whilst downloading a freebsd iso over ftp, no watchdog timeouts occured and speed was 100%, but immediately after the download finished they started popping up again (connecting seems to be slow though) * Inbound connections on xl1 are extremely laggy, switching screens via ssh take a long while to start but then suddenly the whole screen is redrawn. * My xl0 is fine (3Com 3c905C-TX Fast Etherlink XL) ssh, smb, all works as expected. * booting no-acpi results in the same error snippet from dmesg: cardbus0: Resource not specified in CIS: id=14, size=80 cardbus0: Resource not specified in CIS: id=18, size=80 xl1: 3Com 3c575B Fast Etherlink XL port 0x1000-0x107f mem 0x8800-0x887f,0x8880-0x8800 00ff irq 10 at device 0.0 on cardbus0 miibus1: MII bus on xl1 tdkphy0: TDK 78Q2120 media interface on miibus1 tdkphy0: 10baseT, 100baseTX, auto xl1: Ethernet address: 00:00:86:57:76:22 cutcut xl1: watchdog timeout xl1: watchdog timeout xl1: watchdog timeout Anyone got a clue what happens here and how I can fix this? Spil. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Missing wep_wlan at 5.4 (was: Atheros (ath0) no RX traffic)
Sam Leffler [EMAIL PROTECTED] wrote: Stephen Montgomery-Smith wrote: Richard Arends wrote: Today I upgraded my laptop from 5-STABLE to 6-STABLE. After the upgrade, my wireless is not working anymore. You are doing better than me. I try this: ifconfig ath0 wepkey 12345 and get ifconfig: SIOCS80211: Invalid argument (Actually maybe that is happening to you as well, but since you are setting ifconfig_ath0 from within rc.conf, you might be missing this error message as it flies by in your start up.) I get this error on other wireless cards as well. kldload wlan_wep Since a few days I get ifconfig: SIOCS80211: Invalid argument while trying to set up wep with up to date ndis stuff on 5.4. ATM I use an older ndis build which still works. wlan_wep seems to exist at 6.0 only: http://fxr.watson.org/fxr/source/modules/wlan_wep/?v=RELENG54 http://fxr.watson.org/fxr/source/modules/wlan_wep/?v=RELENG6 Is there some secret I don't know about? Fabian -- http://www.fabiankeil.de/ pgp6YHwsfXpfs.pgp Description: PGP signature
Sobre FreeBSD stable
Hola listeros Soy nuevo en el tema del FreeBSD y me gustaria saber cual es la distribucion stables en estos momentos. Podria ser la 4.11 o la 5.x? Saludos y gracias taurus __ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: timecounter and Hz quality in kern RELENG_6
martinko [EMAIL PROTECTED] wrote: Oliver Fromme wrote: Michael Schuh [EMAIL PROTECTED] wrote: After digging in the source i have found that timec.c have an routine for computing the so called Hz quality. During boot, the kernel probes several time counters and assigns quality values. Typically you have three of them (i8254, ACPI, TPC). The time counter with the highest quality value will be used for timing by default, but you can change it via sysctl if you know what you are doing. Type sysctl kern.timecounter and see the result. are those quality values preset (i.e. TSC = 800) or are they computed (during boot) somehow? and if the latter, how pls?? They have hardcoded defaults, but some of them are adjusted under certain circumstances. For example, the TSC's default value of 800 is reduced on an SMP-enabled or APM-enabled system. You should be able to look it up in the source code easily yourself. Look for struct timecounter. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. Perl will consistently give you what you want, unless what you want is consistency. -- Larry Wall ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sobre FreeBSD stable
On Tue, Nov 08, 2005 at 04:27:21PM +0100, dani mot wrote: Hola listeros Soy nuevo en el tema del FreeBSD y me gustaria saber cual es la distribucion stables en estos momentos. Podria ser la 4.11 o la 5.x? Saludos y gracias taurus Hola, La distribucion stable en este momento es la 6.0 como lo puedes ver en la web (www.freebsd.org). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
What should be in GENERIC? (was Re: Facilitating binary kernel upgrades)
Tom Grove wrote: Richard Bejtlich wrote: After speaking with Colin, he mentioned that IPSec, NAT, and disk quotas (enabled via options QUOTA) are the three most popular kernel changes that prevent people from running GENERIC and hence using freebsd-update for binary kernel updates. Can anyone shed light on why those three features are not available in GENERIC? My guess is that just because those are the three most popular kernel changes that prevent people from running GENERIC doesn't mean that the majority of users implement these changes. I find this argument hard to accept. The vast majority of FreeBSD users will never need the NFS_ROOT option, and many systems do not even have the hardware for serial or parallel ports, yet those are supported in the GENERIC kernel. In deciding what options should go into the GENERIC kernel, I think the question we should be asking is not how many people use this?, but instead would adding this option inconvenience more people than it would help?. Colin Percival ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
swapinfo error on 6.x
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 5-stable: [EMAIL PROTECTED]:/home/imb# swapinfo Device 1K-blocks UsedAvail Capacity /dev/da0s1b 104419222736 1021456 2% /dev/da1s1b 104419222996 1021196 2% Total 208838445732 2042652 2% On 6-stable: [EMAIL PROTECTED]:/home/imb swapinfo Device 1K-blocks UsedAvail Capacity /dev/ar0s1b 1048576 307504 104857629% ~ .. avail shouldn't be the same as 1k-blocks :-( Thanks to Jarrod Sayers for pointing out my oversight, Michael -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFDcNGDiJykeV6HPMURAiYbAKDr1GKPnBJ4coBeygBq02viQDfwWACg7CPx bwKvqZgUq7iXowzCTbmJXSs= =f6/o -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
5-stable kernel hang during boot
Hi, I've got an IBM Intellistation M Pro with dual 600 Mhz PIIIs, an IBM DNES-309170W (da0 on ahc0) as the root drive and HighPoint RocketRaid 1520 with two WD1600JD drives mirrored as data drives. There is nothing on ata0 and the CD-ROM drive is the master on ata1. I have been running a custom kernel (GENERIC with SMP) since installation. The verbose output from dmesg from the a 5.4 Release kernel (booted from CD-ROM) is attached. I installed 5.3 Release on this machine a while back and just decided to try to upgrade to 5.4 Stable. (This is my first attempt at doing a buildworld upgrade.) I cvsup'ed /usr/src using the stable-supfile in /usr/share/examples/cvsup. I then followed the instructions in /usr/src/Makefile to build world, build a new custom kernel and install the new kernel. Then I attempted to reboot into single user mode. The boot hangs while processing ata1, right after the following: ata0: [MPSAFE] ata1: channel #1 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 The really interesting part is that after installing the new kernel, I can't boot from kernel.old or another backup of my custom kernel. They both hang in the same way as the new kernel. If I boot off the 5.4 Release CD-ROM, remove the new kernel and rename kernel.old to kernel, the system comes up just fine. At this point I guess I'm looking for any help I can get. Could the fact that there is nothing on ata0 be causing a problem? I know I can boot the 5.4 Release kernel, would I be better off upgrading from the install? I have had no problems with this machine so I can just scratch the upgrade, but it would be nice to be able to get it up to 5-stable and eventually 6-stable. -- Paul Keusemann [EMAIL PROTECTED] 4266 Joppa Court (952) 894-7805 Savage, MN 55378 SMP: Added CPU 1 (BSP) SMP: Added CPU 0 (AP) MPTable: IBM-PCCO CrossFire MP APIC ID: physical 0, logical 0:0 APIC ID: physical 1, logical 0:1 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 1 cpu1 (AP): APIC ID: 0 bios32: Found BIOS32 Service Directory header at 0xc00fd800 bios32: Entry = 0xfd811 (c00fd811) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xd84c pnpbios: Found PnP BIOS data at 0xc00fde60 pnpbios: Entry = f:5bea Rev = 1.0 Other BIOS signatures found: ioapic0: Assuming intbase of 0 ioapic0: Routing external 8259A's - intpin 0 ioapic0: intpin 0 - ExtINT (edge, high) ioapic0: intpin 1 - ISA IRQ 1 (edge, high) ioapic0: intpin 2 - ISA IRQ 2 (edge, high) ioapic0: intpin 3 - ISA IRQ 3 (edge, high) ioapic0: intpin 4 - ISA IRQ 4 (edge, high) ioapic0: intpin 5 - ISA IRQ 5 (edge, high) ioapic0: intpin 6 - ISA IRQ 6 (edge, high) ioapic0: intpin 7 - ISA IRQ 7 (edge, high) ioapic0: intpin 8 - ISA IRQ 8 (edge, high) ioapic0: intpin 9 - ISA IRQ 9 (edge, high) ioapic0: intpin 10 - ISA IRQ 10 (edge, high) ioapic0: intpin 11 - ISA IRQ 11 (edge, high) ioapic0: intpin 12 - ISA IRQ 12 (edge, high) ioapic0: intpin 13 - ISA IRQ 13 (edge, high) ioapic0: intpin 14 - ISA IRQ 14 (edge, high) ioapic0: intpin 15 - ISA IRQ 15 (edge, high) ioapic0: intpin 16 - PCI IRQ 16 (level, low) ioapic0: intpin 17 - PCI IRQ 17 (level, low) ioapic0: intpin 18 - PCI IRQ 18 (level, low) ioapic0: intpin 19 - PCI IRQ 19 (level, low) ioapic0: intpin 20 - PCI IRQ 20 (level, low) ioapic0: intpin 21 - PCI IRQ 21 (level, low) ioapic0: intpin 22 - PCI IRQ 22 (level, low) ioapic0: intpin 23 - PCI IRQ 23 (level, low) ioapic0: intpin 1 bus ISA ioapic0: intpin 1 trigger: edge ioapic0: intpin 1 polarity: high ioapic0: intpin 2 bus ISA ioapic0: Routing IRQ 0 - intpin 2 ioapic0: intpin 2 trigger: edge ioapic0: intpin 2 polarity: high ioapic0: intpin 3 bus ISA ioapic0: intpin 3 trigger: edge ioapic0: intpin 3 polarity: high ioapic0: intpin 4 bus ISA ioapic0: intpin 4 trigger: edge ioapic0: intpin 4 polarity: high ioapic0: intpin 5 bus ISA ioapic0: intpin 5 trigger: edge ioapic0: intpin 5 polarity: high ioapic0: intpin 6 bus ISA ioapic0: intpin 6 trigger: edge ioapic0: intpin 6 polarity: high ioapic0: intpin 7 bus ISA ioapic0: intpin 7 trigger: edge ioapic0: intpin 7 polarity: high ioapic0: intpin 8 bus ISA ioapic0: intpin 8 trigger: edge ioapic0: intpin 8 polarity: high ioapic0: intpin 12 bus ISA ioapic0: intpin 12 trigger: edge ioapic0: intpin 12 polarity: high ioapic0: intpin 13 bus ISA ioapic0: intpin 13 trigger: edge ioapic0: intpin 13 polarity: high ioapic0: intpin 15 bus ISA ioapic0: intpin 15 trigger: edge ioapic0: intpin 15 polarity: high ioapic0: Routing SMI - intpin 23 ioapic0: intpin 18 bus PCI ioapic0: intpin 18 trigger: level ioapic0: intpin 18 polarity: low ioapic0: intpin 19 bus PCI ioapic0: intpin 19 trigger: level ioapic0: intpin 19 polarity: low ioapic0: intpin 19 bus PCI ioapic0: intpin 19 trigger: level ioapic0: intpin 19 polarity: low ioapic0:
Re: Fwd: carp + ipfw problem
Hello all, I'm trying to configure a firewall with carp + ipfw, but I encountered the strange problem. Packets are bypassing carp interface, instead ipfw log shows packet flow to/from physical interface, e.g.: http://www.countersiege.com/doc/pfsync-carp/ it is important to keep in mind that from pf's perspective, all traffic comes from the physical interface, even if it is routed through the carp address. However, the address is of course associated with the carp interface. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What should be in GENERIC? (was Re: Facilitating binary kernel upgrades)
Colin Percival wrote: Tom Grove wrote: Richard Bejtlich wrote: After speaking with Colin, he mentioned that IPSec, NAT, and disk quotas (enabled via options QUOTA) are the three most popular kernel changes that prevent people from running GENERIC and hence using freebsd-update for binary kernel updates. Can anyone shed light on why those three features are not available in GENERIC? My guess is that just because those are the three most popular kernel changes that prevent people from running GENERIC doesn't mean that the majority of users implement these changes. I find this argument hard to accept. The vast majority of FreeBSD users will never need the NFS_ROOT option, and many systems do not even have the hardware for serial or parallel ports, yet those are supported in the GENERIC kernel. And they should stay supported in GENERIC, since these are features you want to use if you have quite a big serverfarm and want to do PXE (speaking of NFS_ROOT). :) In deciding what options should go into the GENERIC kernel, I think the question we should be asking is not how many people use this?, but instead would adding this option inconvenience more people than it would help?. I agree. Today I upgraded my private rootserver to 6.0-RELEASE (good job folks!) and it's running the GENERIC. Since I want to use quota's and need 'em, I have to compile my own kernel. But... well, what the hack, I'll do it anyway to strip down the GENERIC :) Just my 0,02 cents. 6.0-RELEASE looks really good (as it already looked good in RC1). Keep up the good work. Best Regards, Marian PS.: For whom it may concern and for those who are from Germany: it's a root-server at Strato (german company). Whoever runs FreeBSD on those webservers: and upgrade from 5.4-RELEASE to 6.0-RELEASE went easy and works like a charm (except of some struggles with dhclient) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Does ath driver support Atheros 5005G?
I installed 6.0-RELEASE on a Toshiba M55-139 laptop. It has the Atheros AR5005G 802.11 device, which 'dmesg' reports as ath0 Atheros 5212 mem 0xd0200-0xd020 irq 21 at device 2.0 on pci 4 ath0: Ethernet address: 00:11:f5:8d:f4:fc ath0: mac 7.8 phy 4.5 radio 5.6 On PCI Bus 4, 'scanpci' sees pci bus 0x0004 cardum 0x02 function 0x00: vendor 0x168c device 0x001a Device unknown pci bus 0x0004 cardnum 0x04 function 0x01: vendor 0x168c device 0xff96 Device unknown and 'pciconf -vl' sees [EMAIL PROTECTED]:2:0: class 0x02 card=0x7094144f chip=0x001a168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' class = network subclass = ethernet After reading Sam Leffler's August 2005 freebsdmall article, ( http://www.freebsdmall.com/~loader/...ss/article.html http://www.freebsdmall.com/%7Eloader/en_US.ISO8859-1/articles/wireless/article.html) I compiled a new kernel with device ath device ath_hal device ath_rate_sample device wlan device wlan_wep device wlan_ccmp device wlan_tkip kldstat: 1 19 0xc040 37de9c kernel 2 1 0xc077e000 1b88 wlan_xauth.ko 3 1 0xc078 2cf4 wlan_acl.ko 4 2 0xc0783000 ca00 if_ndis.ko 5 3 0xc079 173c4 ndis.ko 6 1 0xc07a8000 a36e4 ar5211_sys.ko 7 16 0xc084c000 568dc acpi.ko 8 1 0xc1c98000 15000 linux.ko So far, I have not used any security at all, and the 5005G 'ifconfigs' as ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 ether 00:11:f5:8d:f4:fc media: IEEE 802.11 Wireless Ethernet autoselect (DS/1Mbps) status: no carrier ssid Binky DHCP channel 3 authmode OPEN privacy OFF txpowmx 34 protmode CTS I am very sure that there actually is a network available, because when I dual-boot the laptop in Windows XP I both see the network and successfully connect (I am 1 meter from a D-Link DI-624 rev.C). When I run ifconfig ath0 up scan I get nothing at all. I'm worried that the 5005 is not supported at all, and wonder if anyone knows if 1) that is true, 2) if it will be soon. The 6.0-RELEASE 'man ath' claims support only for the 5210 5211 5212 chips. If the AR5005G is properly supported as a 5212, does anyone have any other suggestions? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-stable Digest, Vol 135, Issue 3
Hi All I just installed FreeBSD I have to say, it looks good. Certainly I have better experiences with it than I have with Linux. Jamie. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AGP ceased to work on eMachines M5310 laptop
On Monday 07 November 2005 09:23 pm, Mike Jakubik wrote: Jung-uk Kim wrote: On Monday 07 November 2005 05:18 pm, Mike Jakubik wrote: On Mon, November 7, 2005 11:49 am, Jung-uk Kim wrote: Please send me 'pciconf -lv' output. Here it is, thanks. -- [EMAIL PROTECTED]:0:0:class=0x06 card=0x chip=0xcab01002 rev=0x13 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'A3/U1 S2K CPU to PCI Bridge' class= bridge subclass = HOST-PCI The driver exists on -CURRENT but it was not MFC'd before release. http://docs.freebsd.org/cgi/mid.cgi?200509170336.j8H3alVZ083992 Any ideas why? I don't know. ENOTIME, maybe? CC'ing anholt. Jung-uk Kim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Tun and ALTQ
On Tue, Nov 08, 2005 at 02:39:02PM +0100, Marko Cuk wrote: It seems that it work. Thanks. Damn, for vlan's ( 802.1Q) you should specify em, for tun, vice versa... what a mess, hehe. No prob; I don't see why using the em(4) backing the tun(4) wouldn't work for ALTQ _IF_ you actually tagged the (PPPoE?) traffic on em(4). I think that might be really hard, though, so for ALTQ you should probably just specify the logical interface that you intend to limit (that would be the IP tun(4) rather than the PPPoE em(4)). Do you have suggestion on what would be good text to go into pf.conf(5) so that this particular case is documented? -- Brian Fundakowski Feldman \'[ FreeBSD ]''\ [EMAIL PROTECTED] \ The Power to Serve! \ Opinions expressed are my own. \,,\ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
psm0 broken with acpi_ibm on 6.0-RELEASE
Hi all, I've found the following problem on my IBM T41p when running 6.0-RELEASE: when both psm and acpi_ibm are compiled in the kernel, the psm0 device (touchpad) doesn't initialize properly - with verbose logging it says psm0: unable to allocate IRQ When acpi_ibm is removed from the kernel, psm0 works OK. However, combination of both psm and acpi_ibm used to work at least till 6.0-BETA4, which is what I had previously on this laptop. Best, Petr Petr Holub CESNET z.s.p.o. Supercomputing Center Brno Zikova 4 Institute of Compt. Science 162 00 Praha 6, CZMasaryk University Czech Republic Botanicka 68a, 60200 Brno, CZ e-mail: [EMAIL PROTECTED] phone: +420-549493944 fax: +420-541212747 e-mail: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_5 tinderbox] failure on sparc64/sparc64
TB --- 2005-11-08 17:30:11 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2005-11-08 17:30:11 - starting RELENG_5 tinderbox run for sparc64/sparc64 TB --- 2005-11-08 17:30:11 - cleaning the object tree TB --- 2005-11-08 17:31:07 - checking out the source tree TB --- 2005-11-08 17:31:07 - cd /tinderbox/RELENG_5/sparc64/sparc64 TB --- 2005-11-08 17:31:07 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2005-11-08 17:39:56 - building world (CFLAGS=-O -pipe) TB --- 2005-11-08 17:39:56 - cd /src TB --- 2005-11-08 17:39:56 - /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything TB --- 2005-11-08 18:23:10 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2005-11-08 18:23:10 - cd /src TB --- 2005-11-08 18:23:10 - /usr/bin/make buildkernel KERNCONF=GENERIC Kernel build for GENERIC started on Tue Nov 8 18:23:10 UTC 2005 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for GENERIC completed on Tue Nov 8 18:30:01 UTC 2005 TB --- 2005-11-08 18:30:01 - generating LINT kernel config TB --- 2005-11-08 18:30:01 - cd /src/sys/sparc64/conf TB --- 2005-11-08 18:30:01 - /usr/bin/make -B LINT TB --- 2005-11-08 18:30:01 - building LINT kernel (COPTFLAGS=-O -pipe) TB --- 2005-11-08 18:30:01 - cd /src TB --- 2005-11-08 18:30:01 - /usr/bin/make buildkernel KERNCONF=LINT Kernel build for LINT started on Tue Nov 8 18:30:01 UTC 2005 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] /src/sys/pci/viapm.c:968: error: (near initialization for `isa_viapm_driver_mod.dmd_driver') /src/sys/pci/viapm.c:968: error: `isa_devclass' undeclared here (not in a function) /src/sys/pci/viapm.c:968: error: initializer element is not constant /src/sys/pci/viapm.c:968: error: (near initialization for `isa_viapm_driver_mod.dmd_devclass') /src/sys/pci/viapm.c:969: error: initializer element is not constant /src/sys/pci/viapm.c:969: error: (near initialization for `isa_viapropm_driver_mod.dmd_driver') /src/sys/pci/viapm.c:969: error: initializer element is not constant /src/sys/pci/viapm.c:969: error: (near initialization for `isa_viapropm_driver_mod.dmd_devclass') *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-08 18:36:33 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-08 18:36:33 - ERROR: failed to build lint kernel TB --- 2005-11-08 18:36:33 - tinderbox aborted ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panic with cdrecord
On Mon, 07 Nov 2005 14:53:21 +0200 Andriy Gapon [EMAIL PROTECTED] wrote: on 05/11/2005 20:36 Manfred Lotz said the following: I agree. Happened to me as well under FreeBSD 6.0. burncd was hanging when trying to fixate and never came back. I personally don't see this problem, but I am still curious - has any of you guys tried to debug this problem ? E.g. attaching with gdb and checking where exaclty burncd hangs/loops etc. I am sure that there should exist a PR for this problem, so maybe collecting all available (useful) information under would help to make resolution closer. Haven't tried to debug yet. Hopefully I'll find some time next week to debug it. Then I'll come back to you with the results. -- Manfred ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Does ath driver support Atheros 5005G? - CORRECTED kldstat
Two hours ago I made a post with the Subject line you see on this note. I copied the post I made to bsdforum's laptop forum Sunday night, and added the kldstat to the copy. Unfortunately, I included the kldstat from my more recent NDISulator efforts to get the 5005 going (which has not worked yet either, though Bill has some suggestions...) Here's the output from kldstat for the native 'ath' driver: Id Refs Address Size Name 1 19 0xc040 37de9c kernel 2 1 0xc077e000 1b88 wlan_xauth.ko 3 1 0xc078 2cf4 wlan_acl.ko 7 16 0xc0783000 568dc acpi.ko 8 1 0xc17cb000 15000 linux.ko Sorry for the confusion, - Randy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sendmail not compiling with make world in 6.0
As Brain had stated you are using the libsasl from your 5.x system. You need to rebuild the sasl port for 6.x, and then do either a buildworld or build sendmail manually from the base sources. If your system is not at 6.x right now, just comment out those entries in /etc/make.conf. Do the build/installworld. Then build the Cyrus SASL port (I would suggest that you take this time to update to the Cyrus SASL 2 port). Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What should be in GENERIC? (was Re: Facilitating binary kernel upgrades)
Colin Percival wrote this message on Tue, Nov 08, 2005 at 08:22 -0800: In deciding what options should go into the GENERIC kernel, I think the question we should be asking is not how many people use this?, but instead would adding this option inconvenience more people than it would help?. GENERIC is already so large, that if you want/need a smaller kernel, you're going to rebuild anyways, so the only people it truely inconviences are the people who just want their system to work w/o extra work... From 5.4-R: -r-xr-xr-x 1 root wheel 5896397 May 8 2005 /boot/kernel.GENERIC/kernel* -r-xr-xr-x 1 root wheel 3508960 Sep 4 15:29 /boot/kernel/kernel* Since I care about that extra 2megs, I recompiled my own kernel, but most systems these days a couple megs isn't that big of a deal, and if you're trying to fit it on a small system, you'll care, and you'll need to recompile anyways... If it doesn't conflict, add it. :) -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
multicast join flood messes up sk0
My sk0 is rendered useless when flooded with multicast join requests. Here is my setup: FreeBSD server.mcneil.com 6.0-STABLE FreeBSD 6.0-STABLE #94: Mon Nov 7 23:51:05 PST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AMD64 amd64 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ (2009.79-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x20f32 Stepping = 2 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x1SSE3 AMD Features=0xe2500800SYSCALL,NX,MMX+,b25,LM,3DNow+,3DNow real memory = 2147418112 (2047 MB) avail memory = 2064441344 (1968 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 skc0: Marvell Gigabit Ethernet port 0xa800-0xa8ff mem 0xf500-0xf5003fff irq 19 at device 11.0 on pci2 skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) sk0: Marvell Semiconductor, Inc. Yukon on skc0 sk0: Ethernet address: 00:14:85:85:27:b3 miibus1: MII bus on sk0 e1000phy0: Marvell 88E1000 Gigabit PHY on miibus1 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto I'm streaming MPEG with vls to a target device that is running Linux. Something goes wrong (not related) and I stop the streaming, but the Linux target appears to start flooding multicast join requests. When this happens, my sk0 nic suddenly becomes useless. I get messages like: sk0: watchdog timeout sk0: link state changed to DOWN sk0: watchdog timeout dhcpd: send_packet: No buffer space available If I kill my Linux target, the interface recovers just fine. The sk0 is attached to a gigE linksys switch which is attached to a 100BT switch which is attached to the Linux target. There should be no way that it could use up all the resources on my machine. Sean ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What should be in GENERIC? (was Re: Facilitating binary kernel upgrades)
John-Mark Gurney wrote: GENERIC is already so large, that if you want/need a smaller kernel, you're going to rebuild anyways, Since I care about that extra 2megs, I recompiled my own kernel, And the real problem of a big kernel is I dont understand exactly why do you have to recompile, unless a new future is needed, like SMP, isnt it?, what harm is doing those extra megs? May be you could clarify on this (for the newbies... :-) ), i always add things to generic instead of cut them down, especially that im not an expert on every future commented there, and i am scared to break working things, openbsd recomends dont recompile, shoul we? thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sobre FreeBSD stable
Sounds like a misunderstanding. . Dani asks the question about freebsd releases. I just answer his question in spanish. - Rodrigo Hector Lecuanda wrote: Hay dos ramas de -stable 6.0-stable y 5.x ambas son de calidad de produccion aunque la de nueva tecnologia es la 6.0 y la de legado es la 5.x Podras tener mejor resultado en las listas si te comunicas en ingles. For the benefit or our non-spanish speaking readership, Rodrigo was asking which is the sable release. I referred him to 6.0 as the new technology stable release, and 5.x as the legacy stable release. On 11/8/05, Rodrigo OSORIO [EMAIL PROTECTED] wrote: On Tue, Nov 08, 2005 at 04:27:21PM +0100, dani mot wrote: Hola listeros Soy nuevo en el tema del FreeBSD y me gustaria saber cual es la distribucion stables en estos momentos. Podria ser la 4.11 o la 5.x? Saludos y gracias taurus Hola, La distribucion stable en este momento es la 6.0 como lo puedes ver en la web (www.freebsd.org). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- -Hector Lecuanda PGP Public Key / Llave Publica PGP: http://lecuanda.com/pgp_pubkey.asc http://lecuanda.com/pgp_pubkey.txt ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
USB Card Reader Permissions
Hi, I was wondering if someone could tell me how to set the permissions for a USB card reader when it's plugged in? I've been Googling for hours and found nothing concrete so far although I'll keep looking. So far I have this situation: I plug in the card reader and device nodes are created (e.g. /dev/da0s1, /dev/da1s1 etc). I can mount this as root and if I manually set the permissions I can mount it as my user too. What I can't work out is how to change the permissions when I plug it in so I can just use the reader as my user. I've read the man pages for devfs, devfs.conf and devfs.rules. devfs.rules looks like what I need but I can't work out what I actually need to do or how to test a rule without rebooting. I'm using FreeBSD 6.0-STABLE. Thanks in advance to anyone who can help. -- Andy. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB Card Reader Permissions
On Wed, 9 Nov 2005 07:24, Andy Fraser wrote: I was wondering if someone could tell me how to set the permissions for a USB card reader when it's plugged in? I've been Googling for hours and found nothing concrete so far although I'll keep looking. devfs.conf can do it. So far I have this situation: I plug in the card reader and device nodes are created (e.g. /dev/da0s1, /dev/da1s1 etc). I can mount this as root and if I manually set the permissions I can mount it as my user too. What I can't work out is how to change the permissions when I plug it in so I can just use the reader as my user. [inchoate 8:36] ~ cat /etc/devfs.rules [root=100] add path 'da*' group operator mode 660 And in rc.conf.. devfs_system_ruleset=root I've read the man pages for devfs, devfs.conf and devfs.rules. devfs.rules looks like what I need but I can't work out what I actually need to do or how to test a rule without rebooting. It isn't very obvious :( You can test your changes by doing.. /etc/rc.d/devfs restart -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpDqH757Gbj2.pgp Description: PGP signature
Re: USB Card Reader Permissions
On Tuesday 08 Nov 2005 10:11 pm, Daniel O'Connor wrote: I was wondering if someone could tell me how to set the permissions for a USB card reader when it's plugged in? I've been Googling for hours and found nothing concrete so far although I'll keep looking. devfs.conf can do it. I thought that was only for devices that exist at boot? I have my DVD burner set up in devfs.conf so I can use it as my user (reading and burning with some other tweaks[1]). So far I have this situation: I plug in the card reader and device nodes are created (e.g. /dev/da0s1, /dev/da1s1 etc). I can mount this as root and if I manually set the permissions I can mount it as my user too. What I can't work out is how to change the permissions when I plug it in so I can just use the reader as my user. [inchoate 8:36] ~ cat /etc/devfs.rules [root=100] add path 'da*' group operator mode 660 I already had something like this... And in rc.conf.. devfs_system_ruleset=root ...and this turned out to be the missing piece in the jigsaw. I've read the man pages for devfs, devfs.conf and devfs.rules. devfs.rules looks like what I need but I can't work out what I actually need to do or how to test a rule without rebooting. It isn't very obvious :( You can test your changes by doing.. /etc/rc.d/devfs restart I'd been trying that. It turns out I had completely missed the rc.conf line above so obviously restarting devfs had no effect. Many thanks Daniel. It's working just how I want it now. :-) [1] One of the reasons I first tried FreeBSD as a desktop OS was because it has better support for CD/DVD burning as a user than Linux does (I still can't get burning working reliably with Gentoo but FreeBSD works flawlessly). And the sound system is much better but that's another story. :-) -- Andy. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB Card Reader Permissions
On Wed, 9 Nov 2005 09:20, Andy Fraser wrote: On Tuesday 08 Nov 2005 10:11 pm, Daniel O'Connor wrote: I was wondering if someone could tell me how to set the permissions for a USB card reader when it's plugged in? I've been Googling for hours and found nothing concrete so far although I'll keep looking. devfs.conf can do it. I thought that was only for devices that exist at boot? I have my DVD burner set up in devfs.conf so I can use it as my user (reading and burning with some other tweaks[1]). Nope, it's applied to all devices as they are created as well as pre-existing ones. ...and this turned out to be the missing piece in the jigsaw. Yeah it took me a while to find out you needed that too :) [1] One of the reasons I first tried FreeBSD as a desktop OS was because it has better support for CD/DVD burning as a user than Linux does (I still can't get burning working reliably with Gentoo but FreeBSD works flawlessly). And the sound system is much better but that's another story. :-) Weird, I would expect it to be largely the same. PS another way to do this would be to create a devd file which does the chmod's for this particular device (instead of blindly changing all da devices). -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpLxdfhq0wip.pgp Description: PGP signature
Re: What should be in GENERIC? (was Re: Facilitating binary kernel upgrades)
On Tue, 8 Nov 2005, Colin Percival wrote: Tom Grove wrote: Richard Bejtlich wrote: After speaking with Colin, he mentioned that IPSec, NAT, and disk quotas (enabled via options QUOTA) are the three most popular kernel changes that prevent people from running GENERIC and hence using freebsd-update for binary kernel updates. Can anyone shed light on why those three features are not available in GENERIC? My guess is that just because those are the three most popular kernel changes that prevent people from running GENERIC doesn't mean that the majority of users implement these changes. I find this argument hard to accept. The vast majority of FreeBSD users will never need the NFS_ROOT option, and many systems do not even have the hardware for serial or parallel ports, yet those are supported in the GENERIC kernel. While I agree with you in principle, I think many people would disagree with your assertion about serial ports :-). In deciding what options should go into the GENERIC kernel, I think the question we should be asking is not how many people use this?, but instead would adding this option inconvenience more people than it would help?. With regard to the specific three kernel options mentioned above: KAME IPSEC adds significant additional overhead to the processing of every packet, and also requires that Giant be held over the entire network stack. Also, as there's a competing IPSEC implementation, FAST_IPSEC, it's not clear that all users of IPSEC will want to use KAME IPSEC rather than FAST_IPSEC, and right now they are mutually exclusive. You can argue that these are technical problems that need to be fixed, but I think they need to be fixed before we change GENERIC, not after. In 6.x, IPDIVERT no longer needs to be compiled into the kernel. You can load ipdivert.ko, I believe, although I've not personally tested that. The natd rc.d start script looks like it will even auto-load it for you when nat is started, but again, not personally tested. In 6.x, UFS disk quotas require that Giant be placed over the entire UFS implementation, resulting in significant overhead for users who don't need the feature. Again, an implementation problem, but a good reason to not have it in GENERIC until it is fixed. I expect to see Giant fall off quotas in the next minor release or so of 6.x, but it hasn't happened yet. On the topic of a few of the options you've mentioned: - A wide range of people do use serial ports frequently with FreeBSD -- it's the recommended configuration for headless servers (which I promise there are a lot of), and it's the recommended configuration for debugging. - NFS_ROOT minimally expands the kernel, but is required for PXE booting diskless systems, which is actually quite widely used. It might more usefully be argued that we should have NFS_ROOT there, but not the NFSCLIENT or NFSSERVER, as NFS_ROOT really just does minor tweaks and inclusions for the nfsclient, which is already loadable as a module. Robert N M Watson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-stable Digest, Vol 135, Issue 5
hello, i have new box FreeBSD6.0RC1, i'm tested for running IRC but can not connect, what should i do for this problem? should i install some irc software inside the box? regards --- [EMAIL PROTECTED] wrote: Send freebsd-stable mailing list submissions to freebsd-stable@freebsd.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.freebsd.org/mailman/listinfo/freebsd-stable or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than Re: Contents of freebsd-stable digest... Today's Topics: 1. Missing wep_wlan at 5.4 (was: Atheros (ath0) no RX traffic) (Fabian Keil) 2. Sobre FreeBSD stable (dani mot) 3. Re: timecounter and Hz quality in kern RELENG_6 (Oliver Fromme) 4. Re: Sobre FreeBSD stable (Rodrigo OSORIO) 5. What should be in GENERIC? (was Re: Facilitating binary kernel upgrades) (Colin Percival) 6. swapinfo error on 6.x (Michael Butler) 7. 5-stable kernel hang during boot (Paul Keusemann) 8. Re: Fwd: carp + ipfw problem (rihad) 9. Re: What should be in GENERIC? (was Re: Facilitating binary kernel upgrades) (Marian Hettwer) 10. Does ath driver support Atheros 5005G? (Randy Parker) 11. Re: Tun and ALTQ (Brian Fundakowski Feldman) 12. Re: freebsd-stable Digest, Vol 135, Issue 3 (Jamie White) 13. Re: AGP ceased to work on eMachines M5310 laptop (Jung-uk Kim) 14. psm0 broken with acpi_ibm on 6.0-RELEASE (Petr Holub) 15. [releng_5 tinderbox] failure on sparc64/sparc64 (FreeBSD Tinderbox) 16. Re: kernel panic with cdrecord (Manfred Lotz) 17. Does ath driver support Atheros 5005G? - CORRECTED kldstat (Randy Parker) 18. Re: Sendmail not compiling with make world in 6.0 (Scot Hetzel) 19. Re: What should be in GENERIC? (was Re: Facilitating binary kernel upgrades) (John-Mark Gurney) 20. multicast join flood messes up sk0 (Sean McNeil) 21. Re: What should be in GENERIC? (was Re: Facilitating binary kernel upgrades) (Miguel) 22. Re: Sobre FreeBSD stable (rodrigo) 23. USB Card Reader Permissions (Andy Fraser) 24. Re: USB Card Reader Permissions (Daniel O'Connor) 25. Re: USB Card Reader Permissions (Andy Fraser) 26. Re: USB Card Reader Permissions (Daniel O'Connor) -- Message: 1 Date: Tue, 8 Nov 2005 13:47:40 +0100 From: Fabian Keil [EMAIL PROTECTED] Subject: Missing wep_wlan at 5.4 (was: Atheros (ath0) no RX traffic) To: Sam Leffler [EMAIL PROTECTED] Cc: freebsd-stable@freebsd.org Message-ID: 20051108134740.12b68596@ Content-Type: text/plain; charset=us-ascii Sam Leffler [EMAIL PROTECTED] wrote: Stephen Montgomery-Smith wrote: Richard Arends wrote: Today I upgraded my laptop from 5-STABLE to 6-STABLE. After the upgrade, my wireless is not working anymore. You are doing better than me. I try this: ifconfig ath0 wepkey 12345 and get ifconfig: SIOCS80211: Invalid argument (Actually maybe that is happening to you as well, but since you are setting ifconfig_ath0 from within rc.conf, you might be missing this error message as it flies by in your start up.) I get this error on other wireless cards as well. kldload wlan_wep Since a few days I get ifconfig: SIOCS80211: Invalid argument while trying to set up wep with up to date ndis stuff on 5.4. ATM I use an older ndis build which still works. wlan_wep seems to exist at 6.0 only: http://fxr.watson.org/fxr/source/modules/wlan_wep/?v=RELENG54 http://fxr.watson.org/fxr/source/modules/wlan_wep/?v=RELENG6 Is there some secret I don't know about? Fabian -- http://www.fabiankeil.de/ -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20051108/6998ec73/attachment-0001.bin -- Message: 2 Date: Tue, 8 Nov 2005 16:27:21 +0100 (CET) From: dani mot [EMAIL PROTECTED] Subject: Sobre FreeBSD stable To: freebsd-stable@freebsd.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=iso-8859-1 Hola listeros Soy nuevo en el tema del FreeBSD y me gustaria saber cual es la distribucion stables en estos momentos. Podria ser la 4.11 o la 5.x? Saludos y gracias taurus __ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es -- Message: 3 Date: Tue, 8 Nov 2005 16:29:03 +0100 (CET) From: Oliver Fromme [EMAIL PROTECTED] Subject: Re: timecounter and Hz quality
Re: Does ath driver support Atheros 5005G? - CORRECTED kldstat
Randy Parker wrote: Two hours ago I made a post with the Subject line you see on this note. I copied the post I made to bsdforum's laptop forum Sunday night, and added the kldstat to the copy. Unfortunately, I included the kldstat from my more recent NDISulator efforts to get the 5005 going (which has not worked yet either, though Bill has some suggestions...) The card should work but I see nothing that shows what fails for you. Also pleaes do not cc me. Sam ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB Card Reader Permissions
On Wednesday 09 Nov 2005 12:22 am, Daniel O'Connor wrote: I thought that was only for devices that exist at boot? I have my DVD burner set up in devfs.conf so I can use it as my user (reading and burning with some other tweaks[1]). Nope, it's applied to all devices as they are created as well as pre-existing ones. Ah, cool. :-) ...and this turned out to be the missing piece in the jigsaw. Yeah it took me a while to find out you needed that too :) :-) [1] One of the reasons I first tried FreeBSD as a desktop OS was because it has better support for CD/DVD burning as a user than Linux does (I still can't get burning working reliably with Gentoo but FreeBSD works flawlessly). And the sound system is much better but that's another story. :-) Weird, I would expect it to be largely the same. I don't want to say too much, it being OT and all, but a change in Linux 2.6.8 has meant that I have to run my burning software as root to get a reliable burn. I've yet to find a solution to that problem. PS another way to do this would be to create a devd file which does the chmod's for this particular device (instead of blindly changing all da devices). I have things working, I'm happy. :-) I'll look at other options and better set ups when I have either the need or the time. :-) -- Andy. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_5 tinderbox] failure on alpha/alpha
TB --- 2005-11-09 01:16:50 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2005-11-09 01:16:50 - starting RELENG_5 tinderbox run for alpha/alpha TB --- 2005-11-09 01:16:50 - cleaning the object tree TB --- 2005-11-09 01:17:51 - checking out the source tree TB --- 2005-11-09 01:17:51 - cd /tinderbox/RELENG_5/alpha/alpha TB --- 2005-11-09 01:17:51 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2005-11-09 01:26:23 - building world (CFLAGS=-O -pipe) TB --- 2005-11-09 01:26:23 - cd /src TB --- 2005-11-09 01:26:23 - /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything TB --- 2005-11-09 02:10:04 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2005-11-09 02:10:04 - cd /src TB --- 2005-11-09 02:10:04 - /usr/bin/make buildkernel KERNCONF=GENERIC Kernel build for GENERIC started on Wed Nov 9 02:10:04 UTC 2005 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for GENERIC completed on Wed Nov 9 02:17:59 UTC 2005 TB --- 2005-11-09 02:17:59 - generating LINT kernel config TB --- 2005-11-09 02:17:59 - cd /src/sys/alpha/conf TB --- 2005-11-09 02:17:59 - /usr/bin/make -B LINT TB --- 2005-11-09 02:18:00 - building LINT kernel (COPTFLAGS=-O -pipe) TB --- 2005-11-09 02:18:00 - cd /src TB --- 2005-11-09 02:18:00 - /usr/bin/make buildkernel KERNCONF=LINT Kernel build for LINT started on Wed Nov 9 02:18:00 UTC 2005 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] /src/sys/pci/viapm.c:968: error: (near initialization for `isa_viapm_driver_mod.dmd_driver') /src/sys/pci/viapm.c:968: error: `isa_devclass' undeclared here (not in a function) /src/sys/pci/viapm.c:968: error: initializer element is not constant /src/sys/pci/viapm.c:968: error: (near initialization for `isa_viapm_driver_mod.dmd_devclass') /src/sys/pci/viapm.c:969: error: initializer element is not constant /src/sys/pci/viapm.c:969: error: (near initialization for `isa_viapropm_driver_mod.dmd_driver') /src/sys/pci/viapm.c:969: error: initializer element is not constant /src/sys/pci/viapm.c:969: error: (near initialization for `isa_viapropm_driver_mod.dmd_devclass') *** Error code 1 Stop in /obj/alpha/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-09 02:24:47 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-09 02:24:47 - ERROR: failed to build lint kernel TB --- 2005-11-09 02:24:47 - tinderbox aborted ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: psm0 broken with acpi_ibm on 6.0-RELEASE
On Tue, 8 Nov 2005, Petr Holub wrote: I've found the following problem on my IBM T41p when running 6.0-RELEASE: when both psm and acpi_ibm are compiled in the kernel, the psm0 device (touchpad) doesn't initialize properly - with verbose logging it says psm0: unable to allocate IRQ When acpi_ibm is removed from the kernel, psm0 works OK. However, combination of both psm and acpi_ibm used to work at least till 6.0-BETA4, which is what I had previously on this laptop. I have the same problem with my IBM T40p. If I load acpi_ibm after boot, the module loads fine and the mouse continues to work. It looks like acpi_ibm, if loaded by /boot/loader, takes over irq 12 and prevents psm from attaching. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_5 tinderbox] failure on amd64/amd64
TB --- 2005-11-09 02:24:47 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2005-11-09 02:24:47 - starting RELENG_5 tinderbox run for amd64/amd64 TB --- 2005-11-09 02:24:47 - cleaning the object tree TB --- 2005-11-09 02:26:08 - checking out the source tree TB --- 2005-11-09 02:26:08 - cd /tinderbox/RELENG_5/amd64/amd64 TB --- 2005-11-09 02:26:08 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2005-11-09 02:34:55 - building world (CFLAGS=-O -pipe) TB --- 2005-11-09 02:34:55 - cd /src TB --- 2005-11-09 02:34:55 - /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything stage 5.1: building 32 bit shim libraries TB --- 2005-11-09 03:40:05 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2005-11-09 03:40:05 - cd /src TB --- 2005-11-09 03:40:05 - /usr/bin/make buildkernel KERNCONF=GENERIC Kernel build for GENERIC started on Wed Nov 9 03:40:06 UTC 2005 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for GENERIC completed on Wed Nov 9 03:48:52 UTC 2005 TB --- 2005-11-09 03:48:52 - generating LINT kernel config TB --- 2005-11-09 03:48:52 - cd /src/sys/amd64/conf TB --- 2005-11-09 03:48:52 - /usr/bin/make -B LINT TB --- 2005-11-09 03:48:52 - building LINT kernel (COPTFLAGS=-O -pipe) TB --- 2005-11-09 03:48:52 - cd /src TB --- 2005-11-09 03:48:52 - /usr/bin/make buildkernel KERNCONF=LINT Kernel build for LINT started on Wed Nov 9 03:48:52 UTC 2005 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] /src/sys/pci/viapm.c:968: error: (near initialization for `isa_viapm_driver_mod.dmd_driver') /src/sys/pci/viapm.c:968: error: `isa_devclass' undeclared here (not in a function) /src/sys/pci/viapm.c:968: error: initializer element is not constant /src/sys/pci/viapm.c:968: error: (near initialization for `isa_viapm_driver_mod.dmd_devclass') /src/sys/pci/viapm.c:969: error: initializer element is not constant /src/sys/pci/viapm.c:969: error: (near initialization for `isa_viapropm_driver_mod.dmd_driver') /src/sys/pci/viapm.c:969: error: initializer element is not constant /src/sys/pci/viapm.c:969: error: (near initialization for `isa_viapropm_driver_mod.dmd_devclass') *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-09 03:56:24 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-09 03:56:24 - ERROR: failed to build lint kernel TB --- 2005-11-09 03:56:24 - tinderbox aborted ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5-stable kernel hang during boot
See my posts and others on these topics: critical BOOT failure updating to latest 5-Stable (5.4) 5.3 - 5.4 breaks ATA (Intel ICH2) [PATCH] option to re-enable aggressive ATA probing Those are from September 2005, when I and others started having problems with the latest (poor) edits to the 5-Stable code. There was obviously a regression for many of us with certain hard drives or systems. As an important side note, notice that I am using a similar computer to yours, an IBM PC365 with dual Pentium Pros. Although I have not tried the patch due to lack of time, I hope that will fix your issue. Also, I wonder if we share a similar bad BIOS issue in which our systems seem to choke on this new code for IDE detection during boot time. See my dmesg output in the archives. BTW, this has effectively kept me from upgrading to the latest 5-Stable since September, as it is not a quick and easy task on my old system. Also, there might be another mailing list - ACPI or something where there may be more answers. I don't know if there is a PR for this, yet. I had thought of filing one, but I sort of forgot. Check the archives to see if someone else did. Billy Paul Keusemann wrote: Hi, I've got an IBM Intellistation M Pro with dual 600 Mhz PIIIs, an IBM DNES-309170W (da0 on ahc0) as the root drive and HighPoint RocketRaid 1520 with two WD1600JD drives mirrored as data drives. There is nothing on ata0 and the CD-ROM drive is the master on ata1. I have been running a custom kernel (GENERIC with SMP) since installation. The verbose output from dmesg from the a 5.4 Release kernel (booted from CD-ROM) is attached. I installed 5.3 Release on this machine a while back and just decided to try to upgrade to 5.4 Stable. (This is my first attempt at doing a buildworld upgrade.) I cvsup'ed /usr/src using the stable-supfile in /usr/share/examples/cvsup. I then followed the instructions in /usr/src/Makefile to build world, build a new custom kernel and install the new kernel. Then I attempted to reboot into single user mode. The boot hangs while processing ata1, right after the following: ata0: [MPSAFE] ata1: channel #1 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 The really interesting part is that after installing the new kernel, I can't boot from kernel.old or another backup of my custom kernel. They both hang in the same way as the new kernel. If I boot off the 5.4 Release CD-ROM, remove the new kernel and rename kernel.old to kernel, the system comes up just fine. At this point I guess I'm looking for any help I can get. Could the fact that there is nothing on ata0 be causing a problem? I know I can boot the 5.4 Release kernel, would I be better off upgrading from the install? I have had no problems with this machine so I can just scratch the upgrade, but it would be nice to be able to get it up to 5-stable and eventually 6-stable. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AGP ceased to work on eMachines M5310 laptop
Jung-uk Kim wrote: On Monday 07 November 2005 09:23 pm, Mike Jakubik wrote: Jung-uk Kim wrote: On Monday 07 November 2005 05:18 pm, Mike Jakubik wrote: On Mon, November 7, 2005 11:49 am, Jung-uk Kim wrote: Please send me 'pciconf -lv' output. Here it is, thanks. -- [EMAIL PROTECTED]:0:0:class=0x06 card=0x chip=0xcab01002 rev=0x13 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'A3/U1 S2K CPU to PCI Bridge' class= bridge subclass = HOST-PCI The driver exists on -CURRENT but it was not MFC'd before release. http://docs.freebsd.org/cgi/mid.cgi?200509170336.j8H3alVZ083992 Any ideas why? I don't know. ENOTIME, maybe? CC'ing anholt. I emailed him in private, he is simply too busy. I have tried it with 6-STABLE, and it seems to work just fine. OpenGL apps are very slow, but this is because the radeon driver does not support 3d acceleration on the IGP chipsets for some reason. Thanks. -- agp0: ATI RS100 AGP bridge port 0x8090-0x8093 mem 0xd400-0xd7ff,0xd040-0xd0400fff at device 0.0 on pci0 drm0: ATI Radeon RS100 Mobility U1 port 0x9000-0x90ff mem 0xe000-0xefff,0xd010-0xd010 irq 10 at device 5.0 on pci1 info: [drm] AGP at 0xd400 64MB info: [drm] Initialized radeon 1.16.0 20050311 on minor 0 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_5 tinderbox] failure on i386/i386
TB --- 2005-11-09 03:56:25 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2005-11-09 03:56:25 - starting RELENG_5 tinderbox run for i386/i386 TB --- 2005-11-09 03:56:25 - cleaning the object tree TB --- 2005-11-09 03:57:28 - checking out the source tree TB --- 2005-11-09 03:57:28 - cd /tinderbox/RELENG_5/i386/i386 TB --- 2005-11-09 03:57:28 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2005-11-09 04:06:06 - building world (CFLAGS=-O -pipe) TB --- 2005-11-09 04:06:06 - cd /src TB --- 2005-11-09 04:06:06 - /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything TB --- 2005-11-09 04:51:02 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2005-11-09 04:51:02 - cd /src TB --- 2005-11-09 04:51:02 - /usr/bin/make buildkernel KERNCONF=GENERIC Kernel build for GENERIC started on Wed Nov 9 04:51:02 UTC 2005 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] /src/sys/modules/i2c/controllers/viapm/../../../../pci/viapm.c:968: error: (near initialization for `isa_viapm_driver_mod.dmd_driver') /src/sys/modules/i2c/controllers/viapm/../../../../pci/viapm.c:968: error: `isa_devclass' undeclared here (not in a function) /src/sys/modules/i2c/controllers/viapm/../../../../pci/viapm.c:968: error: initializer element is not constant /src/sys/modules/i2c/controllers/viapm/../../../../pci/viapm.c:968: error: (near initialization for `isa_viapm_driver_mod.dmd_devclass') /src/sys/modules/i2c/controllers/viapm/../../../../pci/viapm.c:969: error: initializer element is not constant /src/sys/modules/i2c/controllers/viapm/../../../../pci/viapm.c:969: error: (near initialization for `isa_viapropm_driver_mod.dmd_driver') /src/sys/modules/i2c/controllers/viapm/../../../../pci/viapm.c:969: error: initializer element is not constant /src/sys/modules/i2c/controllers/viapm/../../../../pci/viapm.c:969: error: (near initialization for `isa_viapropm_driver_mod.dmd_devclass') *** Error code 1 Stop in /src/sys/modules/i2c/controllers/viapm. *** Error code 1 Stop in /src/sys/modules/i2c/controllers. *** Error code 1 Stop in /src/sys/modules/i2c. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-09 04:58:15 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-09 04:58:15 - ERROR: failed to build generic kernel TB --- 2005-11-09 04:58:15 - tinderbox aborted ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Tun and ALTQ
On Tuesday 08 November 2005 18:15, Brian Fundakowski Feldman wrote: On Tue, Nov 08, 2005 at 02:39:02PM +0100, Marko Cuk wrote: It seems that it work. Thanks. Damn, for vlan's ( 802.1Q) you should specify em, for tun, vice versa... what a mess, hehe. No prob; I don't see why using the em(4) backing the tun(4) wouldn't work for ALTQ _IF_ you actually tagged the (PPPoE?) traffic on em(4). I think that might be really hard, though, so for ALTQ you should probably just specify the logical interface that you intend to limit (that would be the IP tun(4) rather than the PPPoE em(4)). The problem with tun(4) in contrast to vlan(4) is that in some cases the packet has to go through userland (i.e. userland PPPoE). During this detour the packet loses the ALTQ mbuf_tag and thus can no longer be stuck into the right queue. That is why there is ALTQ support on tun(4) eventhough it doesn't make that much sense to introduce unnatural queueing in the pseudo interface. For vlan(4) there is no such problem (VLANs are handled in the kernel all the way) so it's easy to stick the ALTQ tags on the packet and queue on the hardware interface underneath. Do you have suggestion on what would be good text to go into pf.conf(5) so that this particular case is documented? [- doc@, maybe somebody is interested/creative? ] -- /\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News pgpAhJ56luaSZ.pgp Description: PGP signature
Re: USB Card Reader Permissions
On Tue, 2005-Nov-08 20:54:41 +, Andy Fraser wrote: I've read the man pages for devfs, devfs.conf and devfs.rules. devfs.rules looks like what I need but I can't work out what I actually need to do or how to test a rule without rebooting. I also found the man pages very opaque but some googling turned up a site with a tutorial (unfortunately, I didn't keep a record). -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What should be in GENERIC?
Hi folks! And the real problem of a big kernel is Sometimes people want just what they need. Do you want your cousin's cycle in a living room? Stuff one even don't know what is it for? Drivers for scsii you don't have? I would like freebsd as neat as possible. It _is_ simple and neat. What I do not get is why system _must_ have newbies and what newbies in this situation are. Is there any dead-line for something? Million newbies till the end of year? As for everything, one _must_ exercise and learn. It is, btw, the pleasure of living. Why does freebsd need graphic install if it matters once-twice in a year? Openbsd discourages from recompiling for onother reason. Security. If someone likes it, ok, if not, ok. If the system is broken, is it over for the rest of life? Of course not. Openvms doesn't use customised kernel too. ;-) Best regards Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_5 tinderbox] failure on sparc64/sparc64
TB --- 2005-11-09 06:13:51 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2005-11-09 06:13:51 - starting RELENG_5 tinderbox run for sparc64/sparc64 TB --- 2005-11-09 06:13:51 - cleaning the object tree TB --- 2005-11-09 06:14:45 - checking out the source tree TB --- 2005-11-09 06:14:45 - cd /tinderbox/RELENG_5/sparc64/sparc64 TB --- 2005-11-09 06:14:45 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_5 src TB --- 2005-11-09 06:23:37 - building world (CFLAGS=-O -pipe) TB --- 2005-11-09 06:23:37 - cd /src TB --- 2005-11-09 06:23:37 - /usr/bin/make -B buildworld Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything TB --- 2005-11-09 07:06:27 - building generic kernel (COPTFLAGS=-O -pipe) TB --- 2005-11-09 07:06:27 - cd /src TB --- 2005-11-09 07:06:27 - /usr/bin/make buildkernel KERNCONF=GENERIC Kernel build for GENERIC started on Wed Nov 9 07:06:27 UTC 2005 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything Kernel build for GENERIC completed on Wed Nov 9 07:13:31 UTC 2005 TB --- 2005-11-09 07:13:31 - generating LINT kernel config TB --- 2005-11-09 07:13:31 - cd /src/sys/sparc64/conf TB --- 2005-11-09 07:13:31 - /usr/bin/make -B LINT TB --- 2005-11-09 07:13:31 - building LINT kernel (COPTFLAGS=-O -pipe) TB --- 2005-11-09 07:13:31 - cd /src TB --- 2005-11-09 07:13:31 - /usr/bin/make buildkernel KERNCONF=LINT Kernel build for LINT started on Wed Nov 9 07:13:31 UTC 2005 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] /src/sys/pci/viapm.c:968: error: (near initialization for `isa_viapm_driver_mod.dmd_driver') /src/sys/pci/viapm.c:968: error: `isa_devclass' undeclared here (not in a function) /src/sys/pci/viapm.c:968: error: initializer element is not constant /src/sys/pci/viapm.c:968: error: (near initialization for `isa_viapm_driver_mod.dmd_devclass') /src/sys/pci/viapm.c:969: error: initializer element is not constant /src/sys/pci/viapm.c:969: error: (near initialization for `isa_viapropm_driver_mod.dmd_driver') /src/sys/pci/viapm.c:969: error: initializer element is not constant /src/sys/pci/viapm.c:969: error: (near initialization for `isa_viapropm_driver_mod.dmd_devclass') *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-09 07:20:18 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-09 07:20:18 - ERROR: failed to build lint kernel TB --- 2005-11-09 07:20:18 - tinderbox aborted ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.0 on VMWare 5.0: `calcru: negative runtime of -12728437 usec for pid 28 (irq17: lnc0)'
Hello freebsd-stable, FreeBSD 6.0 on VMWare 5.0 prints such messages every 3-4 minute. Also, messages like calcru: runtime went backwards from 40644816 to 40005944 usec for pid 3 (g_up) is shown routinely. timecounter is ACPI-safe, kernel is GENERIC one. 5.4-STABLE on some virtual machine runs without such messages. And, hey, numbers are TOO big to be true, aren't they? -- Best regards, Lev mailto:[EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
