Re: HEADS UP! Always use the 'make buildkernel' target to makeyerkernels
In message <[EMAIL PROTECTED]> Christoph Sold writes: : It is neither explained in /usr/src/UPDATING, nor in the above HEADS UP : message. : : A clear explanation, including all steps, would be helpful. The step : missing from the original HEADS UP is you have to move kernel.GENERIC to : kernel BEFORE you reboot. This is not done automatically for you. If you have a suggested update to make UPDATING clearer on this, I'll be happy to integrate it. The UPDATING file generally was for -current users that are expected to have a higher level of understanding. Sometimes stable's UPDATING gets similar text and it takes a little time to get it cleaned up. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HEADS UP! Always use the 'make buildkernel' target to make yerkernels
In message <00b801bfeb66$94ab2960$9b239fc0@mobocracy> "Shawn Barnhart" writes: : I guess I don't care which tools I use, so long as they do the right : thing, and, most importantly THAT THE METHODS ARE TOTALLY DOCUMENTED : WITH ALL THE QUIRKS IN THE FSCK'N HANDBOOK AND NOT JUST IN THE MAILING : LIST ARCHIVE! Read UPDATING for late breaking news. We've been recommending this proceedure for building kernels since before 4.0 was released. It is documented. If there isn't a note in the handbook to look at UPDATING, there should be. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: problems building kernels
In message <[EMAIL PROTECTED]> "Mike O'Dell" writes: : is anyone else more than a little concerned that the people who : ostensibly understand all the details can't agree as to how to : do what and when?? The people that do understand the details do agree. Those that don't understand are still arguing. It is really that simple. At least in my opinion. The upgrade path has been documented like this in UPDATING for a while now. : and this is supposed to be STABLE??? Sometimes shit happens. : give us a break, guys. you don't go changing how a kernel : gets built in a release called STABLE. We try not to. Sometimes it is necessary. : and if you didn't do that, please explain that we can just : ignore all the mail the last few days and go back to : trying to figure out why cvsup-ing the latest STABLE : release doesn't compile/run-on-SMP/etc,etc,etc Look at UPDATING. We try to keep that up to date. Sometimes it takes a couple of days to realize an entry is needed and sometimes the UPDATING maintainer (me) has a life and can't commit it the instant that something is know. : i'll restate my minority view that the FreeBSD project : *really* needs to rethink their release names and the : whole release process, rather than explaining that : we don't understand the effort's peculiar definitions : of words like "stable" This is a once in a great while situtation. Sometimes it happens. We try to avoid it, but sometimes Doodoo happens. Given the level of heat when we do this once, I think that indicates that we've been fairly successful in doing it. This is now documented in UPDATING, which everyone should read and understand before updating. It was bad that it didn't get committed until yesterday. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: Bad sound output, AudioPCI ES1371, 4.0-STABLE
On 11-Jul-00 Joseph Scott wrote: > running 4-STABLE (from 10 Jul 2000) and putting out really crummy > sound ouput. FWIW, my June 30th 4-STABLE is driving one of these (an SB128 to be exact) very nicely indeed. I might try updating that box to see if the sound breaks, but I'm a little worried about trying to go backwards across the binutils divide :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: newpcm and RealPlayer woes
On Wed, Jul 12, 2000 at 08:25:01AM +0100, Mark Blackman wrote: > > For RealPlayer 7, I've found that the key to sync problems is > to go to the 'view-->preferences-->performance' area and set > 'enable support old ESS drivers (linux-only)'. Sync problem > solved for me anyway. Yay, that fixed it! Thanks so much for the help, everyone! -lee -- ++ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on WTnet) | | [EMAIL PROTECTED] | http://wakky.dyndns.org/~lee | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: random.h - again...
On Tue, Jul 11, 2000 at 04:00:14PM -0400, Joakim Ryden wrote: > Hi all, > I cvsupped - built and installed world and went to make a new kernel. The > kernel build fails with: > ===> syscons/fire > make: don't know how to make machine/random.h. Stop > *** Error code 2 I cannot reproduce this. Can anyone? (ONLY "YES" answers need reply) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: restarting buildworld
On Tue, Jul 11, 2000 at 12:31:47AM -0700, Jason C. Wells wrote: > > Is there a way to start buildworld without having it remove and rebuild the > > /usr/obj directory? > > There are bunches of command line options in /usr/src/Makefile*. I believe > the one you want is 'make -DNOCLEAN' but read the makefile to be sure. ^^^ 'make -DNOCLEAN buildworld' (or 'make -DNOCLEAN world') -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
loader config and the new buildkernel
Ok I've moved over to the new regime and used make buildkernel KERNEL=GNOME make installkernel KERNEL=GNOME I've created /boot/loader.conf with options kernel="/GNOME" bootfile="GNOME" What exactly does bootfile do other than put text in the square brackets in the boot up text ie Booting[GNOME] in ... if I leave bootfile option out I get Booting[kernel] in ... but it boots the right kernel. Should I be editing any other options? Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Problems with make world
On Tue, Jul 11, 2000 at 04:36:33PM -0400, Will Mitayai Keeso Rowe wrote: > the error: > cc -O6 -pipe -march=pentiumpro -I/usr/src/usr.bin/ar -Wall -I/usr/obj/usr/ ^^ Would you care to explain to me just what the hell you think you are achieving with "-O6"??? For one, no released version of GCC understands anything above "-O3" (anything above 3 gets converted to 3). RTFM. Have you done a single measure to see what the extra optimization is buying you? OR do you just want to be macho and so you can tell everyone your world is built with "-O6"? (As I stand up straight and stick out my chest like a military man) FreeBSD only officially supports building the OS with "-O". There are optimizer bugs above that (and even sometimes with just -O). -- -- David ([EMAIL PROTECTED]) Disclaimer: Not speaking for FreeBSD, just expressing my own opinion. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: kernel build fail
On Tue, Jul 11, 2000 at 07:47:19PM -0700, Marcel Moolenaar wrote: > > make build/installkernel. All's well except now Linux emulation is > > broken. Any linux app produces: > > ELF interpreter /lib/ld-linux.so.2 not found > > Abort trap > > I believe this is caused by a change in how we brand binaries. rebrand > /compat/linux/sbin/ldconfig and run it. Actually in 4-STABLE one should not need to rebrand their Linux binaries. If anyone finds they need(ed) to, I need to know ASAP!! -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HEADS UP! Always use the 'make buildkernel' target to make yerkernels
> 1. The other 1199 new FreeBSD CD-ROM customers you need to get, are they more >likely to be CVSUPping, mailing-list tracking, make-worlding-since-2.0.1 The people who buy the CDs tend to be more "expert" in nature, it's the newcomers who generally FTP install the system. >experience? Or, to put it another way, where are you planning to grow >your market? CD sales is almost something of a loss-leader in the grander scheme of thing and won't, in and of itself, actually generate enough capital to grow the market all that much. Growing the market is a function of marketing and that's generally funded by a combination of VC money and other profit centers like hardware sales, support, custom engineering, etc. BSDi does all the of the latter and has obvious designs on the former. > 2. Pending market growth, there are limited commercial funds available for >discretionary expeditures. Priorities need to be set. Is ensuring that >the product documentation documents the product one of these priorities? Yes, it's been a priority for quite some time. Finding talented individuals who can significantly advance the state of the art in our documentation (e.g. they know how to write and can produce) is somewhat more problematic. Finding such individuals who are also available for employment has been even more problematic. I'm always looking for resumes! > 3. This particular problem does not require a high-skill, high-cost >developer. If you hired a moderately intelligent and responsible >high-school student to clean up the handbook over summer vacation, You significantly underestimate the size and complexity of the challenge if you honestly think this, and I speak as someone who's burned through more than a few high school students already. :( I even have full-time resources deployed on this during those times when we're looking for another vict^H^H^H^Hhigh school student to throw into the jaws, but they have a lot of other work competing for those 60 hours a week. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: kernel build fail
> Ted Sikora wrote: > > I just installed 4.0-RELEASE and cvsup'ed to STABLE. The kernel build > > fails with an Assembler error. I always do a kernel build before a > > makeworld. I hate to break tradition. > > Then you should wait for 4.1-RELEASE to come out and install that (in > this case). You should be able to keep with tradition then. Rather you should wait for 4.1-RELEAES to come out and install that because YOU HAVE NO BUSINESS RUNNING 4-STABLE IF YOU ARE *_NOT_* GOING TO READ THIS MAILING LIST FOR "HEADS UP" AND OTHER ISSUES. -- -- David ([EMAIL PROTECTED]) Disclaimer: Not speaking for FreeBSD, just expressing my own opinion. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: More optimization issues?
On Tue, Jul 11, 2000 at 07:48:33PM -0400, Chris D. Faulhaber wrote: > While porting another program, I found the following: > Using the default CXXFLAGS (-O -pipe): > $ g++ -O -pipe ud2cd.cc -o ud2cd I don't believe this... (*sigh*). Remove the "-O" and it compiles fine on both -CURRENT and a 4-STABLE box before the Assember / Linker upgrade. Use ``g++ -Wall'' and ``g++ -O -Wall'' on the first (that works) you are given two warnings about the code. With "-O" you only get one of the warnings (and bad linking). The only difference is in the call to to ``cpp'' in which which "-O" causes "-D__OPTIMIZE__" (use ``g++ -v'' to see this). -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HEADS UP! Always use the 'make buildkernel' target to make yerkernels
"Jordan K. Hubbard" <[EMAIL PROTECTED]> writes: >Once you add up his full benefit package (medical, dental, 401K, >insurance, etc) and salary, it still takes another 1199 of you to pay >for the rest of him just through buying CDs at full price, three times >a year. [...] >To summarize, it counts, but not nearly enough to make it a meaningful >answer to the quoted paragraph. Without one hell of a lot of >volunteers working very very hard, each and every open source project >out there would sink tomorrow if it had to switch to CD revenues as >the sole method of making technical, and many other forms of, >progress. Which is exactly as I thought, but there are three points I'd like to make, the above notwithstanding: 1. The other 1199 new FreeBSD CD-ROM customers you need to get, are they more likely to be CVSUPping, mailing-list tracking, make-worlding-since-2.0.1 experts, or are they likely to be complete newcomers to the FreeBSD experience? Or, to put it another way, where are you planning to grow your market? 2. Pending market growth, there are limited commercial funds available for discretionary expeditures. Priorities need to be set. Is ensuring that the product documentation documents the product one of these priorities? If not, see point 1. 3. This particular problem does not require a high-skill, high-cost developer. If you hired a moderately intelligent and responsible high-school student to clean up the handbook over summer vacation, once a year, with follow-up on weekends, it would be a significant improvement over the current situation and would set you back all of (3*120+9*16)*$10.00=$5,040/year, plus FICA, etc. Now, you're down to a few hundred CD's to cover the cost. There is a problem. If you don't have an elegant hack handy, an ugly hack is better than no hack at all. -Michael Robinson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: newpcm and RealPlayer woes
For RealPlayer 7, I've found that the key to sync problems is to go to the 'view-->preferences-->performance' area and set 'enable support old ESS drivers (linux-only)'. Sync problem solved for me anyway. Cheers, Mark Blackman Senior Sys. Admin Direct Connection On Tue, Jul 11, 2000 at 04:40:14AM -0400, Lee Cremeans wrote: > I've been using the newpcm drivers for some time, and they seem to work with > most things, but I've noticed some problems, specifically with the > RealPlayer 7 Beta for linux. The sound seems to jump at the beginning of a > stream, leaving it at least 3-4 seconds behind the counter and any video > content. This makes video streams hard to watch, and also cuts off local > streams early. Also, on remote streams, the sound clicks and squeals loudly > about 1-2 seconds into the stream, and the stream stays out of sync with the > RealPlayer counter the whole time. I have a PR open on this, misc/18728. > > All of this seems to have started happening around the time of the May 12 > MFC, it looks like. I don't know enough about how newpcm works to be able to > offer any advice on fixing the code, but I'd be willing to take a look at it > in my spare time, and I can try any patches someone can come up with. I have > my dmesg pasted below; this is from -STABLE CVSupped Sunday night. > > -lee > > ---cut here-- > > Copyright (c) 1992-2000 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 4.0-STABLE #0: Tue Jul 11 04:10:20 EDT 2000 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LEE > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 400910252 Hz > CPU: AMD-K6(tm) 3D+ Processor (400.91-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x591 Stepping = 1 > Features=0x8021bf > AMD Features=0x8800 > real memory = 134217728 (131072K bytes) > avail memory = 127434752 (124448K bytes) > Preloaded elf kernel "LEE" at 0xc02e7000. > VESA: v2.0, 8192k memory, flags:0x1, mode table:0xc0293e82 (122) > VESA: Matrox Graphics Inc. > K6-family MTRR support enabled (2 registers) > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pcib2: at device 1.0 on pci0 > pci1: on pcib2 > pci1: at 0.0 > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port 0xd000-0xd00f at device 7.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > pci0: at 7.2 irq 11 > fxp0: port 0xd800-0xd81f mem >0xe880-0xe88f,0xe8901000-0xe8901fff irq 9 at device 8.0 on pci0 > fxp0: Ethernet address 00:a0:c9:76:92:a7, 10Mbps > sym0: <875> port 0xdc00-0xdcff mem 0xe890-0xe8900fff,0xe8904000-0xe89040ff irq >10 at device 9.0 on pci0 > sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking > sym0: open drain IRQ line driver, using on-chip SRAM > sym0: using LOAD/STORE-based firmware. > sym1: <875> port 0xe000-0xe0ff mem 0xe8903000-0xe8903fff,0xe8902000-0xe89020ff irq 9 >at device 9.1 on pci0 > sym1: Symbios NVRAM, ID 7, Fast-20, SE, parity checking > sym1: open drain IRQ line driver, using on-chip SRAM > sym1: using LOAD/STORE-based firmware. > pcib1: on motherboard > pci2: on pcib1 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > psm0: irq 12 on atkbdc0 > psm0: model MouseMan+, device ID 0 > vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/15 bytes threshold > lpt0: on ppbus0 > lpt0: Interrupt-driven port > sb0 at port 0x220 irq 5 drq 1 on isa0 > snd0: > sb0: driver is using old-style compatability shims > sbxvi0 at port 0x drq 5 on isa0 > isa_compat: didn't get ports for sbxvi > snd0: > WARNING: "snd" is usurping "snd"'s cdevsw[] > sbxvi0: driver is using old-style compatability shims > sbmidi0 at port 0x330 on isa0 > snd0: > WARNING: "snd" is usurping "snd"'s cdevsw[] > sbmidi0: driver is using old-style compatability shims > awe0 at port 0x620 on isa0 > awe0: > WARNING: "snd" is usurping "snd"'s cdevsw[] > awe0: driver is using old-style compatability shims > ad0: 8693MB [17662/16/63] at ata0-master using UDMA33 > acd0: CDROM at ata1-master using WDMA2 > afd0: 120MB [963/8/32] at ata1-slave using PIO2 > Waiting 10 seconds for SCSI devices to settle > (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. > (noperiph:sym1:0:-1:-1): SCSI BUS reset delivered. > sa0 at sym1 bus 0 target 6 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 3.300MB/s transfers > pass1 at sym1 bus 0 target 5 lun 0 > pass1: Fixed Scanner SCSI-2 device > pass1: 3.300MB/s transfers > Mounting root from ufs:/dev/ad0s1a > cd0 at s
Re: Bad sound output, AudioPCI ES1371, 4.0-STABLE
I have the exact same card you do. (9) sean@pulse: ~ $ cat /dev/sndstat FreeBSD Audio Driver (newpcm) Jun 29 2000 01:10:19 Installed devices: pcm0: at io 0x1080 irq 5 (1p/1r channels duplex) (10) sean@pulse: ~ $ dmesg | grep pcm pcm0: port 0x1080-0x10bf irq 5 at device 15.0 on pci0 (11) sean@pulse: ~ $ I also have device pcm in my kernel, and I've not have one glitch in my sound performance. I switch from X to console, I switch back, I switch desktops, I run lots of memory intensive programs (mozilla, Star Office 5.2, netscape, etc), and I've seen no performance hits. Any other comparisons you'd like to make, I'd be willing to do, compare configs, specs on machines etc... On Tue, 11 Jul 2000, Joseph Scott wrote: > > I have an AudioPCI ES1371 sound card. From dmesg & sndstat : > > --- > > dmesg|grep pcm > pcm0: port 0xb400-0xb43f irq 5 at device 13.0 on > pci0 > --- > > cat /dev/sndstat > FreeBSD Audio Driver (newpcm) Jul 10 2000 17:31:19 > Installed devices: > pcm0: at io 0xb400 irq 5 (1p/1r channels duplex) > --- > > The only thing in my kernel config for this is : > > --- > devicepcm > --- > > I've had this machine for awhile, with sound working fine under 3.4. > I believe it was also working under 4.0-RELEASE also. It's now > running 4-STABLE (from 10 Jul 2000) and putting out really crummy > sound ouput. > > You can make out the song that it's playing, but not easily because > it's generating so much static and garbage around it. > > I've seen several posts about bad sound output, but I haven't seen > any solutions yet. If there are some patches that are floating around > looking for someone to test them I'd be happy to. > > -- > Joseph Scott > [EMAIL PROTECTED] > Office Of Water Programs - CSU Sacramento > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
