similar to: ѵἲÀɡṜÀ

Hi there, I'm having an odd problem where this NIC (cheap-o, yes I know) doesn't seem to work on FreeBSD correctly. I have the same cards (even revision models) in two win boxen and they work fine. 10baseT works but not 100baseT. With a normal NIC config, without explicitly setting the media to 10baseT, it will autosense as 100BaseT @ full-duplex, showing active. However I can't

Hello, Today I updated my desktop PC from FreeBSD 7.0R to 7-STABLE. After that, the scroll wheel of my Intellimouse Explorer 4.0 (USB wired) stopped working. I searched relevant information and found kern/123224 "[ums] Scroll wheel breakage w/ USB MS Wireless Intellimouse Explorer 2.0". The symptom is quite similar. ums0: <Microsoft Microsoft IntelliMouse Explorer, class 0/0, rev

[votenew.jpg] _________________________________________________________________ [pixel.gif] www.darkstonemu.net [pixel.gif] [pixel.gif] [pixel.gif] [pixel.gif] [muonlinedarkstoneadv256vo4.gif]

I'm happy to announce a new CVSup mirror site "CVSup.br.FreeBSD.org", located in Brazil. It offers the entire FreeBSD CVS repository, as well as the FreeBSD web page data. Many thanks to Joao Carlos Mendes Luis and Rodolfo Heitor Gevaerd de Faria for making this service available! -- John Polstra jdp@polstra.com John D. Polstra &

Please see: http://www.freebsd.org/handbook/anoncvs.html For full information on using ``anoncvs'' to fetch FreeBSD CVS repository (or buildable source) bits. If you're also interested in setting up your own regional AnonCVS server, please see: ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-CVS/anoncvs.shar For some setup instructions on doing this (essentially the list of steps I

On Dec 17, 2014, at 6:58 AM, ??????? ??????? <freemgm at gmail.com> wrote: > OS version: FreeBSD 8.4-RELEASE-p19 > NUT version: nut-2.7.2_6 > NUT installation method: from freebsd pkg system > Device info: EATON 9SX 5000i, manufacturing date: 05.09.2014 > ups.firmware: 9SX5Ki ... > there're lot of data in output, if it needed i can attach in file... Not sure why it

Hello! I was trying to build OpenOffice using all of my 4 CPUs. To be able to do other work on the machine comfortably, I ran the build under nice, and assigned real-time priority to the two Xorg processes. The build started at about 23:10 last night, and hung at 23:46. The procstat output for the make's process group is: PID PPID PGID SID TSID THR LOGIN WCHAN EMUL

Kip, Does the problem with Xen 3.1 in HVM/Intel manifest as those BTX halted errors (e.g. http://lists.xensource.com/archives/html/xen-users/2006-10/msg00014.html) ? If so, do you happen to know whether this problem has been solved in Xen 3.2 or 3.2.1? This message of yours was written this March, so I'm assuming that 3.2.1 will contain this fix? Can anybody confirm this? I'm having

I'm quite pleased to now be able to announce FreeBSDCon '99, the first annual FreeBSD Conference and Expo. This will be a significant event for FreeBSD users and developers this year, offering a full spectrum of FreeBSD-related tutorials, demos, workshops, panels, presentations, discussions and exhibits. Many FreeBSD developers and vendors will be at this event as will most of the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On May 31st, FreeBSD 5.5, FreeBSD 6.1, and FreeBSD 6.2 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Since FreeBSD 5.5 is the last remaining supported release from the FreeBSD 5.x stable branch, support for the FreeBSD 5.x stable branch will also cease at the same point. Users of

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On January 31st, FreeBSD 4.11 and FreeBSD 6.0 will have reached their End of Life dates and will no longer be supported by the FreeBSD Security Team. Users of either of these FreeBSD releases are strongly encouraged to upgrade to FreeBSD 5.5, FreeBSD 6.1, or the upcoming FreeBSD 6.2 before that date. Discussion concerning FreeBSD

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On June 30th, FreeBSD 7.2 will reach its End of Life and will no longer be supported by the FreeBSD Security Team. Users of this release are strongly encouraged to upgrade to FreeBSD 7.3 before that date; FreeBSD 7.3 will be supported until the end of March 2012. Please note that since FreeBSD 7.1 has been designated for

Hello Everyone, The branches supported by the FreeBSD Security Officer have been updated to reflect the EoL (end-of-life) of FreeBSD 6.4 and FreeBSD 8.0. Since FreeBSD 6.4 was the last remaining supported release from the FreeBSD 6.x stable branch, support for the FreeBSD 6.x stable branch has also ended. The new list of supported branches is below and at < http://security.freebsd.org/ >.

Did nobody ever verify this for Ken? > On Mon, Oct 01, 2012 at 23:38:33 +0530, Desai, Kashyap wrote: > > > > > > > -----Original Message----- > > > From: owner-freebsd-stable at freebsd.org [mailto:owner-freebsd- > > > stable at freebsd.org] On Behalf Of Kenneth D. Merry > > > Sent: Monday, October 01, 2012 8:58 PM > > > To: John

Hello, last month i reported a problem with interrupt storms in re(4). You can find that report here: http://lists.freebsd.org/pipermail/freebsd-stable/2008-October/046075.html After that, i filled a bug report: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/128287 Remko Lodder (CC'ed) suggested me that i should disable USB code in kernel if i was not using it. As i wasn't using it,

I will be gone and out of contact from 8/1 to 8/18 on a camping trip. I will return to work Tuesday, 8/19. Please use the helpdesk system at https://sbv.techteam.com/ for assistance, and your message will be routed to an available technician. Those outside of SI wishing to contact me should use their regular SBV/SIMag/A&SMag contact person and they will take appropriate action. Others

Hello! I have the same problem, whats up? Andris > -----Original Message----- > From: owner-freebsd-stable@freebsd.org > [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Dmitry Agafonov > Sent: Friday, July 25, 2003 8:40 PM > To: freebsd-stable@freebsd.org > Subject: module_register > > > Hello! > > After today's update (4.8-stable from cvs

Hello Everyone, In light of the longer-than-expected window between 6.2-RELEASE and 6.2-RELEASE, the End-of-Life date for FreeBSD 6.2 has been adjusted from January 31st, 2008 to May 31st, 2008. As a result, FreeBSD 5.5, FreeBSD 6.1, and FreeBSD 6.2 will all cease to be supported at the end of May 2008. FreeBSD users should plan on upgrading to either FreeBSD 6.3 or FreeBSD 7.0 once those have

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On April 30th, FreeBSD 7.0 will reach its End of Life and will no longer be supported by the FreeBSD Security Team. Users of FreeBSD 7.0 are strongly encouraged to upgrade to FreeBSD 7.1 before that date. Note that the End of Life date for FreeBSD 7.0 was originally announced as being February 28, but was delayed by two months in

TB --- 2013-07-08 08:10:00 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca TB --- 2013-07-08 08:10:00 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 root at farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-07-08 08:10:00 - starting RELENG_8 tinderbox run for none/none TB --- 2013-07-08 08:10:00 -