similar to: HEADSUP: XFree86 4.3.0 update

Displaying 20 results from an estimated 600 matches similar to: "HEADSUP: XFree86 4.3.0 update"

2003 Apr 03
4
Signal 11 on X server startup (Was: HEADSUP: XFree86 4.3.0 update
On Sun, 2003-03-16 at 19:24, Ted Faber wrote: > On Fri, Mar 14, 2003 at 02:48:26AM -0500, Andrew J Caines wrote: > > Starting the server as normal with xinit gives normal startup messages, then fails > > with a signal 11: > > I have this problem, too. Same nv server. I'm happy to provide > details. One that might help is that this is an Athelon XP 1800. > >
2004 Sep 10
2
Non-audio applications
On Wed, 2002-11-20 at 16:56, Josh Coalson wrote: > I mean). FLAC only supports 8 channels, but I would bet that > the compression would be a lot better if you separated the 300 > channels stream into several streams (<=8 channels each) and > compressed them with FLAC. That may not be practical for your > application. Hmm, I just acquired some data that has 2 gates and 4
2003 Apr 16
2
USB2.0/Firewire Enclosure
I (work :) bought a USB2.0/Firewire enclosure and I had a little trouble with it until I came across this page http://people.freebsd.org/~maho/USB/comment/ku350a.txt after trying the sysctl things work well. I haven't tried the USB2.0 side of it, as I don't have any USB2.0 controllers. The Firewire bit works great too (quite a bit faster than USB1 :) The enclosure in question is made
2003 Nov 26
1
Can't use offline files in Windows 2000 properly
Hi, I have Samba 2.2.3a running on a FreeBSD 4.8-STABLE system and a Windows 2000 Pro laptop. I am trying to use the offline files feature in windows to keep offline copies of some documents but it doesn't appear to play nicely with Samba :( I setup some documents to sync and it appears to copy them over, and says it was successful, but after I go offline they are 0 bytes long and in the
2003 Apr 26
1
Maxtor 5000XT Firewire/USB2 Drive
Hi, I am trying to get FreeBSD 4.7 to connect to a Maxtor 5000XT drive, but I get the following when connecting it -> Apr 26 09:19:43 chowder /kernel: fwohci0: node_id = 0xc000ffc1, CYCLEMASTER mode Apr 26 09:19:43 chowder /kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) Apr 26 09:19:50 chowder /kernel: fwohci0: BUS reset Apr 26 09:19:50 chowder /kernel: fwohci0: node_id =
2004 Sep 10
3
Non-audio applications
Hi, I work for a company which makes meteor and wind radar (http://www.gsoft.com.au). On occasion (ie during meteor showers such as the Leonids) we configure the system to save raw data as it comes out of the acquisition system, the data rate for this varies (depends on acquisition parameters and number of coherent integrations etc), but usually it is around 600kb/sec. The data consists of 16
2003 Apr 27
1
XFree86-4 is broken ?
Hi guys, I just cvsuped my box to latest stable, as well as did upgrade of almost all the ports. I cant get XFree86-4-Clients running. The build fails here: /usr/ports/x11/XFree86-4-clients/work/xc/programs/xcursorgen rm -f xcursorgen cc -o xcursorgen -O -pipe -ansi -Dasm=__asm -Wall -Wpointer-arith -Wundef -L/usr/ports/x11/XFree86-4-clients/work/xc/exports/lib xcursorgen.o -lXcursor -lXrender
2003 May 08
2
Problex with Matrox G450 and XFree86 4.3.0 on 4.8-STABLE
Hi All I have just finished a re-install of a box that was previously working fine under 4.7. The problem is that the matrox drm kernel module is failinf to initialise correctly. :from the dmesg: FreeBSD 4.8-STABLE #0: Thu May 8 11:41:26 SAST 2003 root@shagrat.prv.moria.org:/usr/src/sys/compile/SHAGRAT48 Timecounter "i8254" frequency 1193182 Hz CPU: Intel Pentium III
2003 Aug 11
1
swap_pager: out of swap space
Aug 11 03:56:34 danux /kernel: swap_pager: out of swap space Aug 11 04:02:34 danux /kernel: swap_pager_getswapspace: failed Aug 11 04:02:34 danux /kernel: pid 278 (XFree86), uid 0, was killed: out of swap space i was actually looking at the screen and then everything stopped (mouse etc). i could not switch to console, but a ctrl+alt+del rebooted fine. one thing that could be taking a lot of
2003 Apr 23
2
Problems with dri/drm using Radeon 7000 VE in -stable
Hi, I tried applying http://people.freebsd.org/~anholt/dri/files/drm-stable-20030411.diff to stable from today (using device radeondrm and options DRM_LINUX). Kernel reports drm seems to be there: drm0: <ATI Radeon QY RV100 VE> port 0x9000-0x90ff mem 0xed000000-0xed00ffff,0xe$ info: [drm] Initialized radeon 1.8.0 20020828 on minor 0 Now, when I try to start XFree86 everything looks fine
2003 Apr 06
0
XFree86 4.3.0 Matrox/MultiHead (Long!)
On Mon, 2003-03-17 at 16:37, Eric Anholt wrote: > On Thu, 2003-03-13 at 09:10, Paul Boehmer wrote: > > I have a test box that had been running X 4.2 in a multihead config for a > > while now (1 Nvidia TNT2 AGP, and 2 Matrox Millennium/Mystique PCI Cards). > > I upgraded yesterday to 4.3.0 only to find out that any attempts to run X > > result in a complete console lockup
2005 Feb 20
0
HeadsUp: will be moving list and RoR next week
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Everyone, Want to let you know that I''ll be syncing over all the aspects of RoR''s mailing lists and it''s site onto a new dedicated server that''ll just be for RubyOnRails.org/.com. It''ll all be seemless and kept in sync until David flips the DNS switch, but there will be a couple of times where the
2020 Mar 18
0
[Dovecot-news] Headsup on feature removal
On 17/03/20 7:50 pm, Aki Tuomi wrote: > Dovecot is now a nearly 20 year old product, and during that time it has accumulated many different features and plugins in its core repository. > > We are starting to gradually remove some of these parts, which are unused, untested or deprecated. > We will provide advance notification before removing anything. > > To start, the following
2020 Mar 18
0
Headsup on feature removal - password
<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 18/03/2020 00:06 Rupert Gallagher <ruga@protonmail.com> wrote: </div> <div> <br> </div> <div> <br>
2020 Mar 18
2
Headsup on feature removal - password
Was there any reason for this message to be HTML-only? On Wed, Mar 18, 2020 at 07:13:12AM +0200, Aki Tuomi wrote: > <!doctype html> > <html> > <head> > <meta charset="UTF-8"> > </head> > <body> > <div> > <br> > </div> > <blockquote type="cite"> > <div> >
2020 Mar 18
0
Headsup on feature removal - password
On Wed, 18 Mar 2020 09:51:51 -0400, Hendrik Boom stated: >Was there any reason for this message to be HTML-only? Was there any reason to 'top post' and include the HTML text? -- Jerry -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL:
2020 Mar 18
2
Headsup on feature removal - password
On Wed, Mar 18, 2020 at 10:38:37AM -0400, Jerry wrote: > On Wed, 18 Mar 2020 09:51:51 -0400, Hendrik Boom stated: > >Was there any reason for this message to be HTML-only? > > Was there any reason to 'top post' and include the HTML text? Yes. (1) To indicate that my question was about the whole message and not its contents. I normally don't top-post. (2) To make it
2020 Mar 18
0
Headsup on feature removal - password
> On 18/03/2020 17:31 Hendrik Boom <hendrik at topoi.pooq.com> wrote: > > > On Wed, Mar 18, 2020 at 10:38:37AM -0400, Jerry wrote: > > On Wed, 18 Mar 2020 09:51:51 -0400, Hendrik Boom stated: > > >Was there any reason for this message to be HTML-only? > > > > Was there any reason to 'top post' and include the HTML text? > > Yes. >
2020 Mar 18
2
[Dovecot-news] Headsup on feature removal
18.03.20, 04:32 CET, Peter: > Please consider holding off on removing features for the next major > release, 2.4.0 instead. It makes sense to retain, in as much as is > possible, feature backwards compatibility across a major release. Seconded! That you are going to drop features from the code base that are old and rarely used is understandable. Doing so in a minor release is not.
2020 Mar 18
0
[Dovecot-news] Headsup on feature removal
I fully agree with this: > Please consider holding off on removing features for the next major > release, 2.4.0 instead. It makes sense to retain, in as much as is > possible, feature backwards compatibility across a major release.