unsubscribe freebsd-stable
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Signal 4 while compiling 4.1.1
Small note, as I wasn't thinking this far back when I wrote this.. I tracked stable since 3.3-RELEASE on a K6-2 333 ([EMAIL PROTECTED]), and never had such problems. Same good cooling - big fan/heatsink and conducting grease. On Mon, 2 Oct 2000, Jeff Wyman wrote: > Just a little side note, although enough info might have been given out > already... > > I have a K6-2/500 system (actually a 550@6x83) running at 2.2v core. It > runs very fast and has tracked stable for a few months now, building about > every week or so. I decided as of 4.1.1-R to stop this wasting of time, > and built that. 4.1.1-R is built and has been running very stable for a > week now. > > I can also agree with others that a good heatsink/fan combo and either > conducting grease or pads are a MUST with this chip. With a good amount of > grease on mine, it runs fine even without the fan, but I didn't like the > idea of this just to save a little bit more of my ear drums. > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Signal 4 while compiling 4.1.1
Just a little side note, although enough info might have been given out already... I have a K6-2/500 system (actually a 550@6x83) running at 2.2v core. It runs very fast and has tracked stable for a few months now, building about every week or so. I decided as of 4.1.1-R to stop this wasting of time, and built that. 4.1.1-R is built and has been running very stable for a week now. I can also agree with others that a good heatsink/fan combo and either conducting grease or pads are a MUST with this chip. With a good amount of grease on mine, it runs fine even without the fan, but I didn't like the idea of this just to save a little bit more of my ear drums. On Mon, 2 Oct 2000, Jeff Duffy wrote: > On Mon, 2 Oct 2000, Jordan Hubbard wrote: > > >If this was a software error, however, one would think more than just > >a couple of people would be running into it. -stable builds just fine > >on multiple test boxes I have here, and that encompasses everything > >from Celerons to Athlons. > > I agree. I was just waiting for someone who had a successful buildworld > of 4.1.1-STABLE on a K6-II or K6-III to speak up (since these were the > two CPUs in question). I assume (and correct me if I'm wrong) that Jordan > is saying that he has done just that. Given, I'm sure he knows the issues > better than I. > > While I look for cooling issues on the K6-III, I'm still going to try a > 4.1-STABLE and a 4.1.1-STABLE buildworld on another K6-II 500 machine I > have, to generate some empirical data on the issue. If both compile > cleanly, I'll post the info so at least I can kill the thread I > helped start :) > > If the 4.1.1-STABLE build fails in the same place however, can I assume > that that would be interesting data? > > Jeff > > > > 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
Re: mouse broken in X-4.0.1 (cvsup yesterday)
I've had problems using /dev/sysmouse in conjunction with moused. It jerks around uncontrollably unless I set the X device to /dev/cuaa0 and kill moused. Then, the mouse freezes on startup. Clicking a few mouse buttons seems to wake it up. This sure is fun! On Thu, 28 Sep 2000, Andre Goeree wrote: > Hello, > > After cvsupping the ports collection yesterday and reinstalling > XFree86-4 my mouse freezes (just hangs in the middle of the screen). > > Any of you the same problem? > > -- Ago > > > 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
Re: I broke my /dev tree, can't fsck /dev/ad0s2a, help?
> >From the shell, I can cd into /dev and see that all the ads0's are > there except ad0s2a. My /etc/fstab has that as /, so it's kinda > odd that I can boot it at all? When I try and MAKEDEV /dev/ad0s2a > it complains that it's a read-only filesystem. > > Can anyone make a suggestion for how I can get it back up? mount -f / To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Small handbook error
Thanks for helping a kid out :) On Wed, 19 Jul 2000, Ben Smithurst wrote: > Jeff Wyman wrote: > > > I'm a complete idiot who doesn't even know how to make diffs, so I > > thought I'd just let everybody know right away instead of figuring out > > how to write a diff and holding out on you all for the time that may > > take - I'm a slow learner. > > $ cp foo foo.orig > $ your-favourite-editor foo > > $ diff -u foo.orig foo > foo.diff > > and that's about it. :-) > > Note that if you're sending a diff for documentation, diffs to the > SGML source are best because that's the format the documentation is > maintained in. (Well, the stuff under doc/ anyway, manpages are > different of course.) But if you don't have the SGML source installed, > a diff to the HTML would probably almost be sufficient to get the > problem fixed. > > -- > Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D > FreeBSD Documentation Project / > 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
On Mon, 10 Jul 2000, Doug Barton wrote: > There is also the option of naming your kernel config file "kernel". > Yes, but some people don't like to name their children "kernel" for whatever reason. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: SMP Busted?
On Sat, 8 Jul 2000, Jeff Wyman wrote: > > > On Sat, 8 Jul 2000, Nimrod Mesika wrote: > > > I've had these random lockups myself on this BP6 board. Seems like bad > > hardware but very difficult to explain to the Windows-oriented > > salesmen... They'll tell you try Windows and when it crashes go complain > > to MS :) > > As for bad hardware, we've had reports of this behavior from users of > Pentium Pro and Pentium classic SMP systems. Not that it couldn't be a > problem though. Whoops, in the process of checking 159 new messages from -stable, I sent this message too soon before seeing the MFC reply. I need to start replying _afterwards_ It's ok to admit my mistakes... Right? :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: SMP Busted?
On Sat, 8 Jul 2000, Nimrod Mesika wrote: > I've had these random lockups myself on this BP6 board. Seems like bad > hardware but very difficult to explain to the Windows-oriented > salesmen... They'll tell you try Windows and when it crashes go complain > to MS :) As for bad hardware, we've had reports of this behavior from users of Pentium Pro and Pentium classic SMP systems. Not that it couldn't be a problem though. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
