Search results

@@wblock: almost, but not quite.

Also, I found some useful posts: this one suggests a broken network card, the other two, which are solved, were solved by changing some BIOS configurations, but they were about hard drives, I think.

I'm not sure if I can help you, but others will be able to do a better job if you would also post which version of FreeBSD you're using.

Aha, okay, cool! I'm glad you worked it out ;). Have fun!

It's because you use the new X.Org (maybe you have WITH_NEW_XORG enabled somewhere -- make sure this variable is not even mentioned your in make.conf -- the switch works if the variable is defined, regardless of its value), because acceleration for X with the new X.Org has so far only been...

Since the clang has been recently upgraded to clang-3.3 in the 9-STABLE branch of the base system, I think it would be interesting for y'all to see these tests. Besides compiler efficiency on resources and speed, binary performance tests are also performed. Results on which performs better are...

Some laptops may experience problems with a USB install. Try installing from a CD/DVD.

@igorino, what the hell? You should include this in the report to the police, not only to the monthly web usage report. I'd like to hear more of that story.

No offense to the OP, but really I don't understand why isn't this in the Off-Topic section. This is a philosophical question, which has nothing to do with either Linux or FreeBSD, but the immaturity of "diehard" fan(atic)s and narrow-mindedness of fundamentalists, which you can find anywhere...

The problem you have is because you didn't follow ruby notice in UPDATING, and now you're with two different origins of ruby. Like your output suggests, run pkgdb -F, to fix the origin. And, please, read portupgrade(1), portmaster(8) and again go through the Handbook. The documentation is there...

Maybe something like FreeNAS?

Aha, ok :e. In this case, what kind of problems did you face with installing 9.1?

Well, first of all, both FreeBSD 9.0 and FreeBSD 8.2 are unsupported and reached EOL. You should try FreeBSD 9.1, or any other supported release. Also, it would be nice if you gave some more information on this hardware card. See this thread (and threads referenced on it).

I mean, did you update perl recently? Or ruby? Before updating any packages, check what /usr/ports/UPDATING says about it. It's easy to see which entries are new, because they're timestamped: Excerpt from UPDATING on perl update: 20130612: AFFECTS: users of lang/perl* and any port that...

So ...

What do you mean PRERELEASE? Although could be unrelated, upgrade to a more recent version. There is a FreeBSD 9.1-RELEASE since December 2012, and there's the fourth installment of security patches already (FreeBSD 9.1-RELEASE p4). Like I said before, it could be due to a ruby or perl upgrade...

Which version of FreeBSD are you using? Also, did you follow the /usr/ports/UPDATING regarding the recent perl and ruby updates?

Well first of all make sure your ports tree is up to date (portsnap fetch update or svn up /usr/ports) and then try portupgrade -Rf openjdk6 or portmaster -Rf openjdk6. I had a very weird problem with java/openjdk6 myself a month or two ago.The solution was to completely deinstall it, and then...

There are no releases of -CURRENT, because it's not ready yet. 10-CURRENT may not even compile from time to time, how are you going to make a release from it? The -RELEASE means stable and frozen base system (frozen in time -- it's not being updated), from which you can save your base system...

Section "Device" # This is for radeondriver # Radeon 2600 XT (RV 630) Identifier "ATI Graphics Adapter" Driver "ati" Option "DRI" "on" #Option "AGPSize" "16" #Option "AGPMode" "4" #Option "DDCMode" "true" #Option "GARTSize" "256" EndSection I think you should...