Re: BSD Host Counter
On Wednesday 03 January 2007 17:12, Net Warrior wrote: > Hi there guys and happy new year. > > Maybe some can remind me the name of the script to install which helps to > gather information about how many hosts (FreeBSD) are in > which counties, as far as I remember is under sysutils, but I'm not sure, I > was reading the list off line but could not find it the topic > of the discussion. > > Lotta Thanx, sorry for the noise. /usr/ports/sysutils/bsdstats ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OpenGL and Intel Graphics [WAS: Cake and Eat it Too: RTCW Port]
On Saturday 20 May 2006 01:26, Jeff Cross wrote: > Michael Nottebrock wrote: > > Jeff Cross schrieb: > >> I ran the "make" commands you specified but still do not have a i915.o > >> file on my system. Here is what I have related to i915: > > > > Oops. Turns out the complete i915 module was only added *after* FreeBSD > > 6.0 release. You'll have to upgrade to 6-STABLE/6.1-RELEASE (to be > > released very soon now) to get it. > > > >> By the way, glxinfo | grep rendering returns no. > > > > Yes, direct rendering won't work without the drm kernel module. > > > > > > Cheers, > > I have recently upgraded to RELENG_6_1 and am still not able to play > RTCW on my laptop. I do have the i915 module loaded now as well as drm. > Below is the output from kldstat: > $ kldstat > Id Refs Address Size Name > 1 36 0xc040 691928 kernel > 2 1 0xc0a92000 5f60 snd_ich.ko > 3 2 0xc0a98000 22b88 sound.ko > 4 1 0xc0abb000 2d48 wlan_wep.ko > 5 1 0xc0abe000 4040 wlan_tkip.ko > 6 1 0xc0ac3000 6da4 wlan_ccmp.ko > 7 1 0xc0aca000 1b88 wlan_xauth.ko > 8 1 0xc0acc000 2cf4 wlan_acl.ko > 9 1 0xc0acf000 fa20 if_ath.ko > 10 3 0xc0adf000 3015c ath_hal.ko > 11 2 0xc0b1 3fbc ath_rate.ko > 12 1 0xc0b14000 4ae8 atapicam.ko > 13 2 0xc0b19000 c7fc netgraph.ko > 14 1 0xc0b26000 77e4 ng_ubt.ko > 15 1 0xc0b2e000 5858 vkbd.ko > 16 1 0xc0b34000 58554 acpi.ko > 17 1 0xc47ee000 16000 linux.ko > 18 1 0xc4f3f000 5000 i915.ko > 19 1 0xc4f44000 e000 drm.ko > > glxinfo still shows no direct rendering: > > $ glxinfo | grep rendering > direct rendering: No > > > glxgears still runs at around 300fps average... It still craps on > itself when trying to launch the window. X goes crazy for a second and > then I am returned back to this: > > ]$ wolfsp > Wolf 1.41 linux-i386 Dec 4 2002 > - FS_Startup - > Current search path: > /home/cross/.wolf/main > /usr/local/share/rtcw/main/sp_pak3.pk3 (14 files) > /usr/local/share/rtcw/main/sp_pak2.pk3 (232 files) > /usr/local/share/rtcw/main/sp_pak1.pk3 (1342 files) > /usr/local/share/rtcw/main/pak0.pk3 (4775 files) > /usr/local/share/rtcw/main > > -- > 6363 files in pk3 files > execing default.cfg > couldn't exec language.cfg > couldn't exec wolfconfig.cfg > couldn't exec autoexec.cfg > Hunk_Clear: reset the hunk ok > Bypassing CD checks > - Client Initialization - > Cmd_AddCommand: map_restart already defined > - Initializing Renderer > --- > - Client Initialization Complete - > - R_Init - > loading libGL.so.1: Initializing OpenGL display > setting mode 3: 640 480 > Using XFree86-VidModeExtension Version 2.2 > XF86DGA Mouse (Version 2.0) initialized > XFree86-VidModeExtension Activated at 1024x768 > Using 4/4/4 Color bits, 16 depth, 0 stencil display. > GL_RENDERER: Mesa GLX Indirect > > > *** > You are using software Mesa (no hardware acceleration)! > Driver DLL used: libGL.so.1 > If this is intentional, add > "+set r_allowSoftwareGL 1" > to the command line when starting the game. > *** > WARNING: could not set the given mode (3) > - CL_Shutdown - > RE_Shutdown( 1 ) > --- > - CL_Shutdown - > --- > Sys_Error: GLimp_Init() - could not load OpenGL subsystem > > Is there anything else I can try or should I get over running games on > my laptop with a makeshift video card? > > agp0: port 0xeff0-0xeff7 mem > 0xd800-0xdfff,0xe038-0xe03f irq 16 at device 2.0 on pci0 did you installed graphics/dri? I am running 6.1-STABLE at i915 chipset, for me all worked fine: [EMAIL PROTECTED] [ttyp1] ~ glxinfo | grep rendering direct rendering: Yes [EMAIL PROTECTED] [ttyp1] ~ pkg_info |grep dri dri-6.4.1,2 OpenGL hardware acceleration drivers for the DRI ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Reading UFS2 from Windows
On Tuesday 16 May 2006 12:19, Kyrre Nygard wrote: > Hello! > > I have an awkward setup right here. > > I have my first harddrive split into one NTFS partition which runs Windows, > and one FAT32 partition which serves as a temporary docking station for all > my files which I later secure into my 2nd harddrive running FreeBSD. > > Can I skip this temporary docking station somehow? > > I was thinking, since UFS2 is an open specification, it shouldn't be > impossible creating a Win32 interface that will let me read and write to > one. > > Does anyone know? > http://sourceforge.net/projects/ufs2tools http://sourceforge.net/projects/ffsdrv ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mounting Canon Powershot Digital Camera
On Thursday 29 December 2005 09:32, TuxGirl wrote: > I'm trying to figure out how to mount my camera, and I seem to be > coming up empty. Here's the info that I got from attaching, and then > detaching the camera from my system: > > Dec 28 23:18:41 amon-re kernel: ugen1: Canon Inc. Canon Digital > Camera, rev 2.00/0.02, addr 2 > Dec 28 23:18:43 amon-re kernel: ugen1: at uhub4 port 4 (addr 2) > disconnected Dec 28 23:18:43 amon-re kernel: All threads purged from > ugen1.3 > Dec 28 23:18:43 amon-re kernel: All threads purged from ugen1.2 > Dec 28 23:18:43 amon-re kernel: All threads purged from ugen1.1 > Dec 28 23:18:43 amon-re kernel: All threads purged from ugen1 > Dec 28 23:18:43 amon-re kernel: ugen1: detached > > I'm running FreeBSD 6.0, and I'm fairly new to *bsd. > I tried mounting /dev/ugen1 (which only exists when the camera is > plugged in), as well as /dev/ugen.1, etc. I also tried /dev/usb. > Each of them complains that a block device is required. Someone on > #freebsd suggested that i try giving it a -t flag, so I tried -t vfat > (which apparently isn't correct on freebsd), then -t msdosfs, but > received the same error with that. > > I'm feeling a bit stumped about this, currently. for me work fine with Powershot A620. The same messages in dmesg, but digikam from ports detect camera and works fine. But don't forget give permissions you user to usb porta like described here http://www.gphoto.org/doc/manual/permissions-usb.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: possible breakin attempt?
On Tuesday 18 October 2005 21:19, Anthony Philipp wrote: > Hello, > > In my daily emails from my box I noticed this: > > Oct 17 16:13:03 lupin sshd[51861]: reverse mapping checking getaddrinfo for > 211-234-119-139.kidc.net failed - POSSIBLE BREAKIN ATTEMPT! Oct 17 16:13:05 > lupin sshd[51863]: reverse mapping checking getaddrinfo for > 211-234-119-139.kidc.net failed - POSSIBLE BREAKIN ATTEMPT! Oct 17 16:13:08 > lupin sshd[51865]: reverse mapping checking getaddrinfo for > 211-234-119-139.kidc.net failed - POSSIBLE BREAKIN ATTEMPT! Oct 17 16:13:21 > lupin sshd[51869]: reverse mapping checking getaddrinfo for > 211-234-119-139.kidc.net failed - POSSIBLE BREAKIN ATTEMPT! Oct 17 16:13:21 > lupin sshd[51867]: reverse mapping checking getaddrinfo for > 211-234-119-139.kidc.net failed - POSSIBLE BREAKIN ATTEMPT! Oct 17 16:13:30 > lupin sshd[51873]: reverse mapping checking getaddrinfo for > 211-234-119-139.kidc.net failed - POSSIBLE BREAKIN ATTEMPT! Oct 17 16:13:32 > lupin sshd[51875]: reverse mapping checking getaddrinfo for > 211-234-119-139.kidc.net failed - POSSIBLE BREAKIN ATTEMPT! Oct 17 16:13:34 > lupin sshd[51871]: reverse mapping checking getaddrinfo for > 211-234-119-139.kidc.net failed - POSSIBLE BREAKIN ATTEMPT! Oct 17 16:13:37 > lupin sshd[51877]: reverse mapping checking getaddrinfo for > 211-234-119-139.kidc.net failed - POSSIBLE BREAKIN ATTEMPT! Oct 17 16:13:37 > lupin sshd[51879]: reverse mapping checking getaddrinfo for > 211-234-119-139.kidc.net failed - POSSIBLE BREAKIN ATTEMPT! Oct 17 16:13:40 > lupin sshd[51881]: reverse mapping checking getaddrinfo for > 211-234-119-139.kidc.net failed - POSSIBLE BREAKIN ATTEMPT! Oct 17 16:13:43 > lupin sshd[51883]: reverse mapping checking getaddrinfo for > 211-234-119-139.kidc.net failed - POSSIBLE BREAKIN ATTEMPT! Oct 17 16:13:55 > lupin sshd[51885]: reverse mapping checking getaddrinfo for > 211-234-119-139.kidc.net failed - POSSIBLE BREAKIN ATTEMPT! > > I was just wondering exactly how dangerous this is, and what I can > do about it. > > Thanks for any additional help! just connections to sshd from ip which have reverse name, but not have A record in DNS provider. Usually for DSL, dialup hosts. see man ssd_config for directive UseDNS or just block tcp/22 from not trusted hosts. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
