945GM graphics and mplayer

2006-10-01 Thread Ganbold
Hi, I have strange problem with my Dell Latitude D620 laptop which has 945GM chipset and onboard graphic card. I'm using September 30th RELENG_6. If I use acpi_video only, mplayer can only use "sdl" video output for full screen playing. If I use [EMAIL PROTECTED]'s i945 graphics support patch

DRM/DRI in STABLE

2006-10-01 Thread Charles P. Schaum
Hi, Just had a question about DRI/DRM using the Intel i915 module on an 845G. Using fullscreen modes that have a resolution different from the display at startup can cause the xserver to halt and restart. This actually happened more under 6.1 STABLE than 6.2-PRE. After building world I can usuall

Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2

2006-10-01 Thread Matthew Jacob
Just to add a data point: I just upgraded feral.com to the latest RELENG_6 branch. I have a dual port em for internal networks and I've never seen the problems reported. Also, for -current, things have now been stable again for the last week or so for em on multiple machines (most of which have d

Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2

2006-10-01 Thread David G Lawrence
> Just an observation. > > All the boxes I've had this problem on have _two_ em interfaces. I have > never seen it on my boxes with just one em NIC. > > The error is always em0 timeout - never em1 (I haven't seen any!) > > Yesterday my local network got completely wacky, the gateway had em0 >

Re: altq on tun0: queueing works, prioritization not?

2006-10-01 Thread Ulrich Spoerlein
Ulrich Spoerlein wrote: > This is definitely not what I would expect. Where is my error? Oh well, I should have tried 'cbq' earlier. With the following settings (renamed the queues) altq on $ext_if cbq bandwidth 800Kb queue { q_pri, q_std } queue q_pri priority 6 cbq(borrow) queue q_std priority

Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2

2006-10-01 Thread Scott Long
Martin Nilsson wrote: Just an observation. All the boxes I've had this problem on have _two_ em interfaces. I have never seen it on my boxes with just one em NIC. The error is always em0 timeout - never em1 (I haven't seen any!) Yesterday my local network got completely wacky, the gateway ha

Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2

2006-10-01 Thread Martin Nilsson
Just an observation. All the boxes I've had this problem on have _two_ em interfaces. I have never seen it on my boxes with just one em NIC. The error is always em0 timeout - never em1 (I haven't seen any!) Yesterday my local network got completely wacky, the gateway had em0 timeouts on the

altq on tun0: queueing works, prioritization not?

2006-10-01 Thread Ulrich Spoerlein
Hello all, I tried to set up TCP ACK prioritization with pf/altq as has been described on various places of the internet. It doesn't work as expected. I have a 16Mb/1Mb DSL link, the modem is connected to a dc(4) device, I'm working with the tun0 device for my firewall rules. Here they are: ext_

vmstat -i output after solving snd problems.

2006-10-01 Thread Marcin Koziej
Hello, I use FreeBSD STABLE on Acer Aspire 1525, with VIA K8M400 chipset and VIA1612A on-motherboard sound card. I've beet tracing STABLE from some time ago, and at some point of 5.X series my sound started to be distorted (clicks, lags, metallic sounds) in a random manner, with distortions

Re: Drives always come up dirty after shutdown on 6.2-PRERELEASE.

2006-10-01 Thread Wayne Sierke
On Sun, 2006-10-01 at 02:45 -0700, Jeremy Chadwick wrote: > On Sun, Oct 01, 2006 at 02:17:17PM +0930, Wayne Sierke wrote: > > If you run fsck ("fsck -n" is sufficient) without specifying a file > > system so that it reads the list of which file systems to check from > > fstab, does it check all tho

Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2

2006-10-01 Thread Erik Trulsson
On Sun, Oct 01, 2006 at 01:37:38PM +0100, Pete French wrote: > > Are you enabling an option, like IPv6, that puts Giant over the network > > stack? > > Am not enabling anything, but if INET6 is part of GENERIC (which I think it is > isn't it?) then I would have that in my kernels as they basicall

Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2

2006-10-01 Thread Kris Kennaway
On Sun, Oct 01, 2006 at 01:37:38PM +0100, Pete French wrote: > > Are you enabling an option, like IPv6, that puts Giant over the network > > stack? > > Am not enabling anything, but if INET6 is part of GENERIC (which I think it is > isn't it?) then I would have that in my kernels as they basicall

Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2

2006-10-01 Thread Pete French
> Are you enabling an option, like IPv6, that puts Giant over the network > stack? Am not enabling anything, but if INET6 is part of GENERIC (which I think it is isn't it?) then I would have that in my kernels as they basically look like this: include GENERIC options SMP

Re: Disappearing IPv6 default route

2006-10-01 Thread Matthew Seaman
Martin Blapp wrote: > > Hi, > > Will you MFC before Beta 2 ? > > Martin > >> -} else if (req == RTM_ADD && SDL(gate)->sdl_alen == 0) { >> +} else if (req == RTM_ADD && SDL(gate)->sdl_alen == 0 && >> +(rt->rt_flags & RTF_HOST) != 0) { >> ln->ln_state = ND6

Re: Drives always come up dirty after shutdown on 6.2-PRERELEASE.

2006-10-01 Thread Jeremy Chadwick
On Sun, Oct 01, 2006 at 02:17:17PM +0930, Wayne Sierke wrote: > If you run fsck ("fsck -n" is sufficient) without specifying a file > system so that it reads the list of which file systems to check from > fstab, does it check all those with a non-zero Pass#? Taken from fstab(5) manpage: The

Re: Disappearing IPv6 default route

2006-10-01 Thread Martin Blapp
Hi, Will you MFC before Beta 2 ? Martin - } else if (req == RTM_ADD && SDL(gate)->sdl_alen == 0) { + } else if (req == RTM_ADD && SDL(gate)->sdl_alen == 0 && + (rt->rt_flags & RTF_HOST) != 0) { ln->ln_state = ND6_LLINFO_INC

HEADS UP: FreeBSD 5.3, 5.4, 6.0 EoLs coming soon

2006-10-01 Thread FreeBSD Security Officer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Everyone, On October 31st, FreeBSD 5.3 and FreeBSD 5.4 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Users of either of those FreeBSD releases are strongly encouraged to upgrade to FreeBSD 5.5