Re: 'whereis portname' behaviour changed from 4.X to 5.X ?
On Sat, Dec 04, 2004 at 02:23:13PM +0900, Rob wrote: > > Hi, > > When I search a port with 'whereis', I get different results > on my 4.10 and 5.3 systems. For example > > 4.10 $ whereis lyx > /usr/ports/print/lyx /usr/ports/japanese/lyx > > 5.3 $ whereis lyx > /usr/ports/japanese/lyx > > > Why this difference? > On both systems /usr/ports/print/lyx exists. > > Similar cases are there with other ports. > The result on 5.3 is rather confusing. Hmm. Weird. > uname -rs FreeBSD 5.3-RELEASE-p2 > ls /usr/ports/japanese/lyx Makefiledistinfofiles pkg-descr pkg-plist > ls /usr/ports/print/lyx Makefiledistinfopkg-descr pkg-plist > whereis lyx lyx: /usr/ports/print/lyx > In case if it's important, I used to have a refuse file for cvsup which refused any languages I don't speak, but not any more. Andrew pgpyZEFz7Tb4B.pgp Description: PGP signature
'whereis portname' behaviour changed from 4.X to 5.X ?
Hi, When I search a port with 'whereis', I get different results on my 4.10 and 5.3 systems. For example 4.10 $ whereis lyx /usr/ports/print/lyx /usr/ports/japanese/lyx 5.3 $ whereis lyx /usr/ports/japanese/lyx Why this difference? On both systems /usr/ports/print/lyx exists. Similar cases are there with other ports. The result on 5.3 is rather confusing. Rob. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: the best graphicscard for FreeBSD
I've been experimenting with various cards, most cheap. The monitors are HP P1110 21" surplus, very bright (too bright) and very sharp. These are the PC version with VGA connectors, not the ones with BNC connectors. I currently have a Matrox G450 in dual-head mode under 5.3-STABLE with Xorg, updated a couple of days ago from ports. Xinerama is very nice; the only problem I have is that MS Windows XP appears to leave the card in a wierd state, and I have to power cycle the system sometimes before the second monitor works correctly. This system is an old SM P6DGH dual PII/300 with an early AGP slot. I am moving to a newer machine, SM P4DCE+ dual Xeon 1.8GHZ. It came with a Radeon 7000 VE board which works fine with 5.3-STABLE/Xorg using the config written by Xorg. With versions before 5.3 I had to add radeondrm support, not now. Both agp/drm show on dmesg. This card works very well at 1280x1024, using very small characters - combination is as good as the 19" NEC plasma I have at work, except bigger (and hotter). (The Dell at work has a dual-head nVidia 5200 board). I bought a new nVida based FX5500 board to experiment. Trouble. The main problem is that the video amps don't have the bandwidth to show sharp characters on the screen at 1280x1024 at any refresh I've tried. nVidia does have drivers for FreeBSD 5.21 and later, but I haven't tried them. (I tried both FreeBSD with the "nv" driver and MS Windows XP using the MS certified nVidia FX5500 driver). I suspect that name-brand nVida-based cards would be better (I can't even find a name on this one, other than "nVidia"), but my mind is already made up. For the moment I'm sticking with ATI-made Radeon cards; my next one will probably be either an 8400 dual head or a 9200 dual head. I just have to find a game player who wants an nVidia FX5500/256MB dual head card cheap. Mike Squires ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.x can't read 5.x dump?
On Fri, Dec 03, 2004 at 02:36:09PM +, Ceri Davies wrote: > > > Should I expect a dump taken from 4.X to be restorable on 5.X though? > > Yes. > Phew. I didn't even think about the possibility of dump not being forwards compatible (8-( In passing, you may find the buffer port useful. I spent a while a couple of years ago experimenting with settings, and find this sort of thing sufficiently fast: /sbin/dump -L -0 -u -C 32 -b 32 -f - /home | /usr/local/bin/buffer -s 32k -m 16m -t | gzip | /usr/local/bin/buffer -s 32k -m 16m -t > new/home.dump.gz That is, big buffers and block sizes for dump, with a 16 MB buffer of either side of gzip to absorb some of the delays in compression or writing the dump file. Sorry, no timings available at the moment. Note: * Remove the -L under Release 4 * When the above line is executed, the script has changed its CWD to the dump directory, usually on an NFS mount. * When dumping to the same machine, I include -h 0 and make the dump directory (and a slew of other recoverable by other ways ones) nodump with chflags nodump. -- Adrian Wontroba ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: the best graphicscard for FreeBSD
Godwin Stewart wrote: I'd add that Matrox cards are excellent in the 2D arena. I still have an old G200 here and It beats the socks off the ATI Rage128 I also have as far as clarity and general piquà are concerned. Obviously, the Rage128 does better than the G200 in the 3D department, although not in FreeBSD for some reason I have yet to fathom out. In Linux it works fine. If one can get them for free (they seem to become available in larger numbers these days, when machines from around 1999/2000 get scrapped), then Matrox cards (up to g500) are still quite decent for "office" work. However, I have seen that new ones are still sold for up to 100 EUR, which is just outrageous, imho. Considering that you can get a R9200 for half the price, which not only sports facilities like DVI and TV-Out but also supports 8x AGP, has 4-8x the memory and runs circles around the MGA, and image quality is roughly comparable, imho. -- Matthias Buelow; [EMAIL PROTECTED],informatik.uni-wuerzburg}.de ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: the best graphicscard for FreeBSD
On Sat, Dec 04, 2004 at 12:35:49AM +0100, Godwin Stewart wrote: > On Sat, 4 Dec 2004 00:01:29 +0100, Roland Smith <[EMAIL PROTECTED]> wrote: > > > > I tried kldloading radeon anyway and running glxgears. It can't do any > > > better than about 10 fps at 1024x768/24bits. > > > > My radeon gives 560 - 580 fps with direct rendering. An R128 would > > probably be somewhat slower. > > Running Slackware with XFree86-4.3.0 I'd get about 60-70 fps out of it. > > > I think this is just telling you that it is loading the modules you told > > it to. Later in the logfile you see if those modules are actually used. > > Try to grep for [drm] and [agp] to see if they are really used. Or IIRC > > grep for UnloadModule to see if Xorg discards some of those modules. Also > > check for warning (WW) or error (EE) messages. > > Hmm > > $ grep -i '\(dr\(i\|m\)\|glx\)' /var/log/Xorg.0.log > X.Org Video Driver: 0.7 > X.Org XInput driver : 0.4 > ABI class: X.Org Video Driver, version 0.7 > (--) Using syscons driver with X support (version 2.0) > (II) LoadModule: "glx" > (II) Loading /usr/X11R6/lib/modules/extensions/libglx.a > (II) Module glx: vendor="X.Org Foundation" > (II) Loading extension GLX > (II) LoadModule: "dri" > (II) Loading /usr/X11R6/lib/modules/extensions/libdri.a > (II) Module dri: vendor="X.Org Foundation" > (II) Loading sub module "drm" > (II) LoadModule: "drm" > (II) Loading /usr/X11R6/lib/modules/freebsd/libdrm.a > (II) Module drm: vendor="X.Org Foundation" > (II) Loading extension XFree86-DRI > (II) Loading /usr/X11R6/lib/modules/drivers/r128_drv.o > Module class: X.Org Video Driver > ABI class: X.Org Video Driver, version 0.7 > (II) Loading /usr/X11R6/lib/modules/drivers/ati_drv.o > Module class: X.Org Video Driver > ABI class: X.Org Video Driver, version 0.7 > Module class: X.Org XInput Driver > ABI class: X.Org XInput driver, version 0.4 > (II) ATI: ATI driver (version 6.5.6) for chipsets: ati, ativga > (II) R128: Driver for ATI Rage 128 chipsets: > (II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP), > (II) Reloading /usr/X11R6/lib/modules/drivers/r128_drv.o > ABI class: X.Org Video Driver, version 0.7 > ABI class: X.Org Video Driver, version 0.7 > ABI class: X.Org Video Driver, version 0.7 > ABI class: X.Org Video Driver, version 0.7 > ABI class: X.Org Video Driver, version 0.7 > ABI class: X.Org Video Driver, version 0.7 > ABI class: X.Org Video Driver, version 0.7 > drmOpenDevice: minor is 0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 8, (OK) > drmOpenDevice: minor is 0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 8, (OK) > drmOpenDevice: minor is 0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is 8, (OK) > drmGetBusid returned '' > (II) R128(0): [drm] created "r128" driver at busid "PCI:1:0:0" > (II) R128(0): [drm] added 8192 byte SAREA at 0xc1c0b000 > (II) R128(0): [drm] mapped SAREA 0xc1c0b000 to 0x2834b000 > (II) R128(0): [drm] framebuffer handle = 0xf800 > (II) R128(0): [drm] added 1 reserved context for kernel > (II) R128(0): [drm] register handle = 0xf020 > (II) R128(0): [dri] Visual configs initialized > (II) R128(0): [drm] installed DRM signal handler > (II) R128(0): [DRI] installation complete > (II) R128(0): [drm] Added 128 16384 byte vertex/indirect buffers > (II) R128(0): [drm] Mapped 128 vertex/indirect buffers > (II) R128(0): [drm] dma control initialized, using IRQ 11 Right after this line I get (for my radeon): (II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808 Followed by: (II) RADEON(0): Direct rendering enabled Maybe AGP GART isn't working? -- R.F. Smith /"\ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ /No HTML/RTF in email http://www.xs4all.nl/~rsmith/ X No Word docs in email / \Respect for open standards pgpBuTxA8XLZ7.pgp Description: PGP signature
Re: fsck_ffs patch testers wanted
I'd just like to post a follow up to this, and thanks ... one of our servers crashed tonight, after being up and running for ~67days ... normally, I'd be cursing, because after *that* long, the fsck would take about 12 hours or so ... The server rebooted, fsck'd and dump'd a core file in <60 minutes ... Thanks Don ... On Thu, 30 Sep 2004, Don Lewis wrote: On 30 Sep, Marc G. Fournier wrote: Would you be willing to post a 4.x version of this, or send me one, that I can test, since I'm the one that seems lucky to get the "glacially slow" fsck's :( I was planning on posting a 4.x version sometime after I did the commit to -CURRENT and it had time to get well exercised by the masses. My plan is to allow about a month of testing between the commit to -CURRENT and the MFC. Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: the best graphicscard for FreeBSD
On Sat, 4 Dec 2004 00:01:29 +0100, Roland Smith <[EMAIL PROTECTED]> wrote: > > I tried kldloading radeon anyway and running glxgears. It can't do any > > better than about 10 fps at 1024x768/24bits. > > My radeon gives 560 - 580 fps with direct rendering. An R128 would > probably be somewhat slower. Running Slackware with XFree86-4.3.0 I'd get about 60-70 fps out of it. > I think this is just telling you that it is loading the modules you told > it to. Later in the logfile you see if those modules are actually used. > Try to grep for [drm] and [agp] to see if they are really used. Or IIRC > grep for UnloadModule to see if Xorg discards some of those modules. Also > check for warning (WW) or error (EE) messages. Hmm $ grep -i '\(dr\(i\|m\)\|glx\)' /var/log/Xorg.0.log X.Org Video Driver: 0.7 X.Org XInput driver : 0.4 ABI class: X.Org Video Driver, version 0.7 (--) Using syscons driver with X support (version 2.0) (II) LoadModule: "glx" (II) Loading /usr/X11R6/lib/modules/extensions/libglx.a (II) Module glx: vendor="X.Org Foundation" (II) Loading extension GLX (II) LoadModule: "dri" (II) Loading /usr/X11R6/lib/modules/extensions/libdri.a (II) Module dri: vendor="X.Org Foundation" (II) Loading sub module "drm" (II) LoadModule: "drm" (II) Loading /usr/X11R6/lib/modules/freebsd/libdrm.a (II) Module drm: vendor="X.Org Foundation" (II) Loading extension XFree86-DRI (II) Loading /usr/X11R6/lib/modules/drivers/r128_drv.o Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 0.7 (II) Loading /usr/X11R6/lib/modules/drivers/ati_drv.o Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 0.7 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.4 (II) ATI: ATI driver (version 6.5.6) for chipsets: ati, ativga (II) R128: Driver for ATI Rage 128 chipsets: (II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP), (II) Reloading /usr/X11R6/lib/modules/drivers/r128_drv.o ABI class: X.Org Video Driver, version 0.7 ABI class: X.Org Video Driver, version 0.7 ABI class: X.Org Video Driver, version 0.7 ABI class: X.Org Video Driver, version 0.7 ABI class: X.Org Video Driver, version 0.7 ABI class: X.Org Video Driver, version 0.7 ABI class: X.Org Video Driver, version 0.7 drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmGetBusid returned '' (II) R128(0): [drm] created "r128" driver at busid "PCI:1:0:0" (II) R128(0): [drm] added 8192 byte SAREA at 0xc1c0b000 (II) R128(0): [drm] mapped SAREA 0xc1c0b000 to 0x2834b000 (II) R128(0): [drm] framebuffer handle = 0xf800 (II) R128(0): [drm] added 1 reserved context for kernel (II) R128(0): [drm] register handle = 0xf020 (II) R128(0): [dri] Visual configs initialized (II) R128(0): [drm] installed DRM signal handler (II) R128(0): [DRI] installation complete (II) R128(0): [drm] Added 128 16384 byte vertex/indirect buffers (II) R128(0): [drm] Mapped 128 vertex/indirect buffers (II) R128(0): [drm] dma control initialized, using IRQ 11 (II) Keyboard "Keyboard1" handled by legacy driver $ grep "^(WW)" < /var/log/Xorg.0.log (WW) `fonts.dir' not found (or not valid) in "/usr/X11R6/lib/X11/fonts/Speedo/". (WW) R128(0): Can't determine panel dimensions, and none specified. Disabling programming of FP registers. (WW) fcntl(9, O_ASYNC): Inappropriate ioctl for device This last line is apparently something to do with the mouse, which does work nonetheless: (II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE) (II) Mouse1: SetupAuto: hw.iftype is 3, hw.model is 4 (II) Mouse1: SetupAuto: protocol is SysMouse (WW) fcntl(9, O_ASYNC): Inappropriate ioctl for device $ grep "^(EE)" < /var/log/Xorg.0.log (EE) R128(0): No DFP detected Googling on this error message threw up loads of results of people seeing it but nothing as to what it actually means. I also got it using Linux but it didn't prevent hardware acceleration from working. -- G. Stewart - [EMAIL PROTECTED] The bigger they are, the harder they hit. pgpXynuJyEM9z.pgp Description: PGP signature
Re: UPDATING file on FreeBSD Stable
On 2004.12.03 19:08:14 +0100, ptitoliv wrote: > I have a little question about the UPDATING file on RELENG_5 branch. I > have received a security advisory about procfs for my FreeBSD-STABLE. > While looking the text of this mail, I saw that the UPDATING file was > updating on all RELENG_X.X branches but not in the stable branch. Why not ? On the development branches (-CURRENT and -STABLE) UPDATING is used for changes which users should be aware since they could cause problems. Security fixes rarely fits this "requirement". On the security / errata branches (RELENG_X_Y) UPDATING is used to document all changes, so people know exactly what to expect, since only very important changes go into those branches. So, in short the reason is that UPDATING has different goals on the different branches. At least I think that is the reason, I'm actually not 100% sure... :-). -- Simon L. Nielsen pgp9mCdkHchcE.pgp Description: PGP signature
Re: the best graphicscard for FreeBSD
On Fri, Dec 03, 2004 at 11:09:06PM +0100, Godwin Stewart wrote: > On Fri, 3 Dec 2004 22:45:32 +0100, Roland Smith <[EMAIL PROTECTED]> wrote: > > > For 3D you have to load the agp and radeon modules. > > This is a Rage128, not a Radeon. I was indeed referring to a Radeon. > agp is built into the kernel and r128 is already kldloaded. > > I tried kldloading radeon anyway and running glxgears. It can't do any > better than about 10 fps at 1024x768/24bits. My radeon gives 560 - 580 fps with direct rendering. An R128 would probably be somewhat slower. > Mind you, this might have something to do with it: > > $ glxinfo | grep direct > direct rendering: No > OpenGL renderer string: Mesa GLX Indirect Yes, I agree that's the culprit. > And yet, quoting snippets from /var/log/Xorg.0.log: > > (II) LoadModule: "glx" > (II) Loading /usr/X11R6/lib/modules/extensions/libglx.a > (II) Module glx: vendor="X.Org Foundation" > compiled for 6.7.0, module version = 1.0.0 > ABI class: X.Org Server Extension, version 0.2 I think this is just telling you that it is loading the modules you told it to. Later in the logfile you see if those modules are actually used. Try to grep for [drm] and [agp] to see if they are really used. Or IIRC grep for UnloadModule to see if Xorg discards some of those modules. Also check for warning (WW) or error (EE) messages. Roland -- R.F. Smith /"\ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ /No HTML/RTF in email http://www.xs4all.nl/~rsmith/ X No Word docs in email / \Respect for open standards pgpsXNMrWcy5e.pgp Description: PGP signature
Re: the best graphicscard for FreeBSD
On Fri, 3 Dec 2004 22:45:32 +0100, Roland Smith <[EMAIL PROTECTED]> wrote: > For 3D you have to load the agp and radeon modules. This is a Rage128, not a Radeon. agp is built into the kernel and r128 is already kldloaded. I tried kldloading radeon anyway and running glxgears. It can't do any better than about 10 fps at 1024x768/24bits. Mind you, this might have something to do with it: $ glxinfo | grep direct direct rendering: No OpenGL renderer string: Mesa GLX Indirect And yet, quoting snippets from /var/log/Xorg.0.log: (II) LoadModule: "glx" (II) Loading /usr/X11R6/lib/modules/extensions/libglx.a (II) Module glx: vendor="X.Org Foundation" compiled for 6.7.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading sub module "GLcore" (II) LoadModule: "GLcore" (II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a (II) Module GLcore: vendor="X.Org Foundation" compiled for 6.7.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading extension GLX (II) LoadModule: "dri" (II) Loading /usr/X11R6/lib/modules/extensions/libdri.a (II) Module dri: vendor="X.Org Foundation" compiled for 6.7.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading sub module "drm" (II) LoadModule: "drm" (II) Loading /usr/X11R6/lib/modules/freebsd/libdrm.a (II) Module drm: vendor="X.Org Foundation" compiled for 6.7.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading extension XFree86-DRI /etc/X11/xorg.conf also has this: Section "DRI" Mode 0666 EndSection -- G. Stewart - [EMAIL PROTECTED] There is nothing more frightening than ignorance in action. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: the best graphicscard for FreeBSD
On Fri, Dec 03, 2004 at 07:34:50PM +0100, Godwin Stewart wrote: > On Fri, 03 Dec 2004 13:26:20 -0500, Jason Andresen <[EMAIL PROTECTED]> > wrote: > > > IMHO, if you just want 2D, pretty much any bottom of the barrel card > > will work. > > I'd add that Matrox cards are excellent in the 2D arena. I still have an old > G200 here and It beats the socks off the ATI Rage128 I also have as far as > clarity and general piqué are concerned. > > Obviously, the Rage128 does better than the G200 in the 3D department, > although not in FreeBSD for some reason I have yet to fathom out. In Linux > it works fine. If you want hardware accellerated 3D (direct rendering) you can use any radeon upto and including the 9250 (which I have). It works fine in both 2D and 3D. Direct rendering now also works on AMD64. For 3D you have to load the agp and radeon modules. Roland -- R.F. Smith /"\ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ /No HTML/RTF in email http://www.xs4all.nl/~rsmith/ X No Word docs in email / \Respect for open standards pgps27uY7AnTZ.pgp Description: PGP signature
ATA Problem going from FreeBSd 5.3 Beta7 to 5.3 Release.
Hopefully this is the correct mailing list, if not, please let me know a more suitable one. I'm setting up a Supermicro 1U server, (6014HX8B: dual Xeon, 2GB ram, hot swappable scsi backplane, dual GB nics, etc...) I tried installing FBSD 5.3 release on it, but I received the following error while booting: ata1-master: FAILURE - ATAPI_IDENTIFY timed out ata1-master: FAILURE - ATAPI_IDENTIFY timed out ata1-master: FAILURE - SETFEATURES SET TRANSFER MODE timed out Fatal trap 12: page fault while in kernel mode fault virtual address= 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc04b345c stack pointer= 0x10:0xc0c21cc0 frame pointer= 0x10:0xc0c21ccc code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) trap number = 12 panic: page fault uptime: 16s cannot dump. No dump device defined. Shutting down ACPI stray irq9 Automatic reboot in 15 seconds - press a key on the console to abort This results in an endless reboot loop. I had no problem installing FBSD 5.3 Beta7 (developer set), so I sync'd the sources and rebuilt the kernel and world to see if I could update it this way to 5.3 RELEASE. On the first reboot after installing the new kernel (compiled with the GENERIC settings) I received the exact same error. Swapping out the new kernel with the old, returned me to a working system. The the only ATA device on this machine is the CDROM (on ATA1-master). If I try to disable the ATA device entries in the kernel and recompile, I then start having SCSI issues... For the record, there are no local HD on this machine, as it is booting from a raid array connected via a Fiber Channel adaptor (using the MPT driver) However, I tried removing the FC card and plugging in a SCSI drive, and the problem is exactly the same. If no one has any better ideas, where can I find a detailed description of the changes between 5.3 Beta7 and 5.3 Release? Thanks for any suggestions, Lapo Nustrini ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: the best graphicscard for FreeBSD
On Fri, 03 Dec 2004 13:26:20 -0500, Jason Andresen <[EMAIL PROTECTED]> wrote: > IMHO, if you just want 2D, pretty much any bottom of the barrel card > will work. I'd add that Matrox cards are excellent in the 2D arena. I still have an old G200 here and It beats the socks off the ATI Rage128 I also have as far as clarity and general piquà are concerned. Obviously, the Rage128 does better than the G200 in the 3D department, although not in FreeBSD for some reason I have yet to fathom out. In Linux it works fine. -- G. Stewart - [EMAIL PROTECTED] BOFH excuse #452: Somebody ran the operating system through a spelling checker ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: the best graphicscard for FreeBSD
Matthias Buelow wrote: Pertti Kosunen wrote: The newer cards work very well. I have a X800se PCI-Express card and it works like a charm with X.org 6.8.1 on 5.3. The only thing that's Isn't that pretty expencive for 2d use? Yes.. that's why I also have Windows installed for a game every now and then. I just wanted to point out that the current generation Radeons do, in contrast to what has been claimed before, actually work with the current Xorg release (which unfortunately hasn't arrived in ports yet, as it seems, but is available via patchsets from the ports maintainer). With "work", I mean, solid 2d performance (supported by the radeon driver, not Vesa). I see 3d support as a nice add-on but not as the core functionality. IMHO, if you just want 2D, pretty much any bottom of the barrel card will work. Even low end Nvidia or ATI cards (Geforce4 MX, Geforce 2, etc...) will work and they're not very expensive (~$30 new for a Geforce 2 MX). Drivers don't become an issue unless you buy an exotic (or extremely off-brand) card or want 3D graphics. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
UPDATING file on FreeBSD Stable
Hi Everybody, I have a little question about the UPDATING file on RELENG_5 branch. I have received a security advisory about procfs for my FreeBSD-STABLE. While looking the text of this mail, I saw that the UPDATING file was updating on all RELENG_X.X branches but not in the stable branch. Why not ? Thank you for your answers Best Regards, Ptitoliv ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.x can't read 5.x dump?
On Fri, Dec 03, 2004 at 09:27:07AM -0500, Ken Smith wrote: > On Fri, Dec 03, 2004 at 02:24:15PM +, Ceri Davies wrote: > > > Should I expect a dump taken from 4.X to be restorable on 5.X though? > > (I do). > > Yes. Phew. Ceri -- Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.-- Einstein (attrib.) pgpAZ96A0iaJk.pgp Description: PGP signature
Re: 4.x can't read 5.x dump?
On Fri, Dec 03, 2004 at 02:24:15PM +, Ceri Davies wrote: > Should I expect a dump taken from 4.X to be restorable on 5.X though? > (I do). Yes. -- Ken Smith - From there to here, from here to | [EMAIL PROTECTED] there, funny things are everywhere. | - Theodore Geisel | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.x can't read 5.x dump?
On Wed, Dec 01, 2004 at 09:40:53PM -0500, Ken Smith wrote: > On Thu, Dec 02, 2004 at 10:48:43AM +1000, Joel Hatton wrote: > > > I'm backing up a 5.x machine at the moment with this command: > > > > dump -0Lau -b128 -f - /var | gzip -2 | ssh FreeBSD4 dd of=aacd0s1f.gz > > > > After the dump finishes, I try to read the file on the 4.x destination: > > > > # gzip -dc aacd0s1a.gz | restore -ivf - > > Verify tape and initialize maps > > Tape is not a dump tape > > > > I can scp the file back to the 5.x machine and it loads just fine, so what > > gives? This type of failure is somewhat scary for me right now, given that > > I may have to restore files to another destination that may not be 5.x > > based. > > This is, unfortunately, something that you should not expect to work > for any *nix variant. The dump mechanism of creating backups creates > output that has "intimate knowledge" of the filesystem so that it can > recreate that filesystem exactly as it exists on the disk. As the > filesystem itself evolves (has features added to it) the dump programs > need to have their data structures change to accomodate the extra > information that is now needed. For example if in 4.X there were no > ACLs but 5.X added ACLs then the dump program's data structures would > need to be changed so it had the ability to store the ACL information > in the output, and the restore program would need to be modified to > look for that and do the right thing if it finds ACL information. > > If there had been no filesystem changes between 4.X and 5.X then > there would not be any need to change dump, and what you are trying > to do would work. But there were filesystem changes between 4.X and > 5.X, so dump was changed, and now there is extra stuff in the dump > images that the 4.X version of restore doesn't understand. This same > general principle holds for all OS's, not just FreeBSD. Should I expect a dump taken from 4.X to be restorable on 5.X though? (I do). Ceri -- Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.-- Einstein (attrib.) pgpktWmj3aUyv.pgp Description: PGP signature
Re: Was: Re: Making a data DVD with 4.10 and dvd+rw-format
On Dec 3, 2004, at 1:38 PM, Godwin Stewart wrote: On Fri, 3 Dec 2004 13:31:09 +0100, Godwin Stewart <[EMAIL PROTECTED]> wrote: but sometimes it gets thrown into limbo and the only way to resume operation is to perform a hard reset Sorry for the self-fup but a thought occurred to me. Stein, have you tried "camcontrol reset n,n,n" to reset the DVD drive? Yes, I tried that (if my memory doesn't fail me). It seemed to fail on something related to the ATAPI device /dev/acd0. Well, I'll test this again tonight, just to be sure Thanx for info anyways. -- G. Stewart - [EMAIL PROTECTED] Cheers Stein M. Sandbech --sms ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Was: Re: Making a data DVD with 4.10 and dvd+rw-format
On Fri, 3 Dec 2004 13:31:09 +0100, Godwin Stewart <[EMAIL PROTECTED]> wrote: > but sometimes it gets thrown into limbo and the only way to resume > operation is to perform a hard reset Sorry for the self-fup but a thought occurred to me. Stein, have you tried "camcontrol reset n,n,n" to reset the DVD drive? -- G. Stewart - [EMAIL PROTECTED] A budget is trying to figure out how the family next door is doing it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Was: Re: Making a data DVD with 4.10 and dvd+rw-format
On Fri, 3 Dec 2004 13:17:49 +0100, Stein Morten Sandbech <[EMAIL PROTECTED]> wrote: > My only problem are when an operation on the unit fails, the > /dev/cd0 device disappears, and a mknod to recreate the device > doesn't work either. > > The most recent causes have been using cdda2wav. > > As of now, it gets reestablished only after a reboot. This kind of thing will often happen on a device that's having difficulty reading the media - either because the media's physical characteristics are close to or outside the tolerance required, or because the drive has a problem such as a dirty or tired optical block. More often than not, the drive will perform an internel reset and attempt to resume reading where it lost track, but sometimes it gets thrown into limbo and the only way to resume operation is to perform a hard reset, hence devfs seeing that the drive is offline and the need to reboot the box. I don't know of any silver bullet to prevent this. I've generally resorted to ripping the audio data on another box and scp/ftp'ing the data over. BTW, cdparanoia is less problematic than cdda2wav IME. -- G. Stewart - [EMAIL PROTECTED] BOFH excuse #210: We didn't pay the Internet bill and it's been cut off. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Was: Re: Making a data DVD with 4.10 and dvd+rw-format
On Dec 3, 2004, at 11:46 AM, nicky wrote: Joan Picanyol wrote: : --> snip Do you have the devices /dev/cd0x etc? Sorry 'bout intruding on this thread, but I have just one question. I use ATAPICAM on a FreeBSD5.3R system, with a Pioneer DVR-108 dual layer with great success. Well, almost then :-) My only problem are when an operation on the unit fails, the /dev/cd0 device disappears, and a mknod to recreate the device doesn't work either. The most recent causes have been using cdda2wav. As of now, it gets reestablished only after a reboot. Any ideas? Cheers Stein M. Sandbech --sms ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making a data DVD with 4.10 and dvd+rw-format
Joan Picanyol wrote: * Michael Nottebrock <[EMAIL PROTECTED]> [20041203 10:52]: Joan Picanyol wrote: # grep atapi /usr/src/sys/i386/conf/LILO device atapicd # ATAPI CDROM drives You don't need this, but device scbus device da device cd Does atapicam really work without atapicd in the kernel? Just a question, I never actually tried. It works for me (on RELENG_5): 503,p3,0$ strings /boot/kernel/kernel | grep ___ | grep atapi ___#device atapicd # ATAPI CDROM drives ___device atapicam 504,p3,0$ camcontrol devlist at scbus1 target 1 lun 0 (pass0,cd0) qvb Do you have the devices /dev/cd0x etc? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making a data DVD with 4.10 and dvd+rw-format
* Michael Nottebrock <[EMAIL PROTECTED]> [20041203 10:52]: > Joan Picanyol wrote: > > >># grep atapi /usr/src/sys/i386/conf/LILO > >>device atapicd # ATAPI CDROM drives > > > > > >You don't need this, but > > > >device scbus > >device da > >device cd > > Does atapicam really work without atapicd in the kernel? Just a question, I > never actually tried. It works for me (on RELENG_5): 503,p3,0$ strings /boot/kernel/kernel | grep ___ | grep atapi ___#device atapicd # ATAPI CDROM drives ___device atapicam 504,p3,0$ camcontrol devlist at scbus1 target 1 lun 0 (pass0,cd0) qvb -- pica ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Dead vnode locking against itself
I'm trying to get ARLA work stable on FreeBSD (5.3-RELEASE) but have found that it sometimes hangs: A process gets stuck in 'ckvnlk' state. I have found someting strange (probably a bug) but I need a second opinion. I patched fs/deadfs/dead_vnops so it does a panic when it tries to go into ckvnlk state and found that it seems to lock against itself. Part of the backtrace: #10 0xc04c6f8f in panic (fmt=0x296 ) at /usr/src/sys/kern/kern_shutdown.c:537 #11 0xc0483de3 in chkvnlock (vp=0xc239d420) at /usr/src/sys/fs/deadfs/dead_vnops.c:248 #12 0xc0483d0a in dead_lock (ap=0xdb344914) at /usr/src/sys/fs/deadfs/dead_vnops.c:210 #13 0xc0515f8f in vclean (vp=0xc239d420, flags=8, td=0xc1c3d640) at vnode_if.h:1013 #14 0xc0516525 in vgonel (vp=0xc239d420, td=0xc1c3d640) at /usr/src/sys/kern/vfs_subr.c:2701 #15 0xc0513051 in vtryrecycle (vp=0xc239d420) at /usr/src/sys/kern/vfs_subr.c:720 #16 0xc051327a in getnewvnode (tag=0xc0645372 "ufs", mp=0xc1918000, vops=0x0, vpp=0x0) at /usr/src/sys/kern/vfs_subr.c:783 ---Type to continue, or q to quit--- #17 0xc05bac67 in ffs_vget (mp=0xc1918000, ino=427054, flags=2, vpp=0xdb344a84) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:1230 #18 0xc05c1c64 in ufs_lookup (ap=0xdb344b40) at /usr/src/sys/ufs/ufs/ufs_lookup.c:599 #19 0xc05c7eaf in ufs_vnoperate (ap=0x0) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2816 #20 0xc050b5d6 in vfs_cache_lookup (ap=0x0) at vnode_if.h:82 #21 0xc05c7eaf in ufs_vnoperate (ap=0x0) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2816 #22 0xc050fcf3 in lookup (ndp=0xdb344c30) at vnode_if.h:52 #23 0xc050f778 in namei (ndp=0xdb344c30) at /usr/src/sys/kern/vfs_lookup.c:181 #24 0xc051a9f6 in lstat (td=0xc1c3d640, uap=0xdb344d14) at /usr/src/sys/kern/vfs_syscalls.c:2069 #25 0xc060e093 in syscall (frame= {tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 134609408, tf_esi = 134609480, tf_ebp = -1077941208, tf_isp = -617329292, tf_ebx = 672396780, tf_edx = 134561792, tf_ecx = 0, tf _eax = 190, tf_trapno = 12, tf_err = 2, tf_eip = 671905847, tf_cs = 31, tf_eflags = 658, t f_esp = -1077941364, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1001 #26 0xc06015ff in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:201 If I look at the source I can see that in sys/kern/vfs_subr.c:2696 (in vgonel) the vnode is locked by VI_XLOCK. Later on (via vclean) dead_lock is called and founds that the vnode is locked. It then waits for it to be unlocked and the results is a hanged process. What have I missed or have I found a bug? /thn -- --- Svensk Aktuell Elektronik AB Thomas Nyström Box 10Phone: +46 8 35 92 85 S-191 21 SollentunaFax: +46 8 35 92 86 Sweden Email: [EMAIL PROTECTED] --- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making a data DVD with 4.10 and dvd+rw-format
Joan Picanyol wrote: # grep atapi /usr/src/sys/i386/conf/LILO device atapicd # ATAPI CDROM drives You don't need this, but device scbus device da device cd Does atapicam really work without atapicd in the kernel? Just a question, I never actually tried. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making a data DVD with 4.10 and dvd+rw-format
* Scott Sewall <[EMAIL PROTECTED]> [20041203 10:11]: > > Scott Sewall wrote: > > > lilo# growisofs -dvd-compat -Z /dev/cd0 -J -R blitz10 > > > :-( unable to open("/dev/cd0",O_RDONLY): No such file or directory ls -l /dev/cd0 ? > # grep atapi /usr/src/sys/i386/conf/LILO > device atapicd # ATAPI CDROM drives You don't need this, but device scbus device da device cd qvb -- pica ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making a data DVD with 4.10 and dvd+rw-format
On Wed, 1 Dec 2004, flip vernooy wrote: > Scott Sewall wrote: > > > > > I'm running FreeBSD 4.10 and trying to make a data DVD. I've > > following the procedure outlined in the handbook without any success. > > > > Any hints or advise would be grealty appreciated. > > > > -- Scott > > > > > > lilo# growisofs -dvd-compat -Z /dev/cd0 -J -R blitz10 > > :-( unable to open("/dev/cd0",O_RDONLY): No such file or directory > > lilo# growisofs -dvd-compat -Z /dev/cd0a -J -R blitz10 > > :-( unable to open("/dev/cd0a",O_RDONLY): Device not configured > > lilo# growisofs -dvd-compat -Z /dev/cd0c -J -R blitz10 > > :-( unable to open("/dev/cd0c",O_RDONLY): Device not configured > > lilo# growisofs -dvd-compat -Z /dev/rcd0a -J -R blitz10 > > :-( unable to open("/dev/rcd0a",O_RDONLY): Device not configured > > lilo# > > > > lilo# uname -a > > FreeBSD lilo.redlinenetworks.com 4.10-RELEASE-p3 FreeBSD > > 4.10-RELEASE-p3 #1: Thu Nov 11 20:54:12 PST 2004 > > [EMAIL PROTECTED]:/usr/src/sys/compile/LILO i386 > > lilo# > > > > lilo# dmesg -a | grep ^cd > > cd0 at ata1 bus 0 target 0 lun 0 > > cd0: Removable CD-ROM SCSI-0 device > > cd0: 33.000MB/s transfers > > cd0: Attempt to query device size failed: NOT READY, Medium not present > > lilo# > > > > lilo# sysctl hw.ata.atapi_dma > > hw.ata.atapi_dma: 1 > > lilo# > > > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > Did you recompilled your kernel? > > check the atapicam device on [url] > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html > [/url] > yes, I've included "device atapicam' in my kernel config file. # grep atapi /usr/src/sys/i386/conf/LILO device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives device atapicam# emulate ATAPI devices as SCSI ditto via CAM -- Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Making a data DVD with 4.10 and dvd+rw-format
I think I'm ok with the pass through devices: # camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) at scbus2 target 0 lun 0 (pass1,cd0) # ls -l /dev | grep pass crw--- 1 root operator 31, 0 Oct 12 13:17 pass0 crw--- 1 root operator 31, 1 Oct 12 13:17 pass1 crw--- 1 root operator 31, 2 Oct 12 13:17 pass2 crw--- 1 root operator 31, 3 Oct 12 13:17 pass3 I have 'device atapicam' entry in my kernel config file. I'll go search the web. -- Scott On Thu, 2 Dec 2004, Donald Goodwin wrote: > I had the same exact problem a few weeks ago. Did you make sure the pass > through devices are configured? > > Check to see what pass device is needed by issuing the folowing command (as > root of course): > > camcontrol devlist > > For example, mine was on pass4. I had to run: > > /dev/ sh MAKEDEV pass5 (I had pass1, pass2, and pass3 already. Note the > indexing. sh MAKEDEV passN will create the device passN-1. Learned that the > hard way). > > Also, do a search on the web. There are several people who have had had > similar experiences and share their success stories. > > Lastly, did you modify your kernel to accomodate ATAPICAM (and the other > required changes)? > > My Sony (710A) is working great now. > > Best of luck, > > Donald > > > - Original Message - > From: "Scott Sewall" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, December 01, 2004 9:50 PM > Subject: Making a data DVD with 4.10 and dvd+rw-format > > > > > > I'm running FreeBSD 4.10 and trying to make a data DVD. I've following > > the procedure outlined in the handbook without any success. > > > > Any hints or advise would be grealty appreciated. > > > > -- Scott > > > > > > lilo# growisofs -dvd-compat -Z /dev/cd0 -J -R blitz10 > > :-( unable to open("/dev/cd0",O_RDONLY): No such file or directory > > lilo# growisofs -dvd-compat -Z /dev/cd0a -J -R blitz10 > > :-( unable to open("/dev/cd0a",O_RDONLY): Device not configured > > lilo# growisofs -dvd-compat -Z /dev/cd0c -J -R blitz10 > > :-( unable to open("/dev/cd0c",O_RDONLY): Device not configured > > lilo# growisofs -dvd-compat -Z /dev/rcd0a -J -R blitz10 > > :-( unable to open("/dev/rcd0a",O_RDONLY): Device not configured > > lilo# > > > > lilo# uname -a > > FreeBSD lilo.redlinenetworks.com 4.10-RELEASE-p3 FreeBSD 4.10-RELEASE-p3 > > #1: Thu Nov 11 20:54:12 PST 2004 > > [EMAIL PROTECTED]:/usr/src/sys/compile/LILO i386 > > lilo# > > > > lilo# dmesg -a | grep ^cd > > cd0 at ata1 bus 0 target 0 lun 0 > > cd0: Removable CD-ROM SCSI-0 device > > cd0: 33.000MB/s transfers > > cd0: Attempt to query device size failed: NOT READY, Medium not present > > lilo# > > > > lilo# sysctl hw.ata.atapi_dma > > hw.ata.atapi_dma: 1 > > lilo# > > > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"