Search results

I can confirm this on stable/9 amd64. A 100mpx image freezes the entire X server for several minutes. Only the mouse cursor still reacts. Key/mouse events during this time accumulate and are acted out when the freeze ends.

I haven't been here for a long, long time. The answer you were looking for can be found in buildflags.mk.

Just out of curiosity, what's wrong with amd? On access mounting seems like a good idea to me.

About the video issue. Just set mplayer to use a decent amount of cache. The default is ridiculously low.

Flash memory has always more memory than available to the user. This is used to replace broken sectors. Normally if a sector breaks, it's detected in time before a data loss and the data is transparently transferred to a hidden sector that henceforth replaces the old one. Also the flash memory...

With sed you cannot have newlines in the expression. You can only add them in the replacement string. There is a workaround if you are certain of a certain character not being used: # Replace newlines with ~ Replace 3 lines Replace ~ with newlines ... | rs -TeC~...

If you set AllowEmptyInput to off, you can turn HAL off, unless you require it for something else.

An SSD already has a much longer life expectancy than a regular hard disk. No optimizations required.

You can always use binary packages. If you use sysutils/bsdadminscripts, you can even use pkg_upgrade for installing, which will download all required packages in advance (if available even parallel from several mirrors) and take care of conflicts (unlike pkg_add). It just downloads an INDEX...

Well, can you provide us your /var/log/Xorg.0.log?

So, now it's time to find out whether this is a KDE or an Xorg problem. I assume you didn't build Xorg without HAL support, so you definitely have to turn that on and restart X. Give us your /var/log/Xorg.0.log contents if that doesn't fix your problem.

Does | grep ums yield any output? If not the mouse driver does not detect your mouse. The command | grep ums tells you whether the appropriate module is loaded.

USB mice should definitely work out of the box. A lot of people find HAL on FreeBSD very painful and turn it off or compile Xorg right without HAL support. You do not need to compile a custom kernel to use USB mice. Does the mouse work on the console? If so, HAL should detect it, if you're...

I have it after converting a DVD with mencoder, so it's got nothing to do with mounting, but it seems to me that the driver misses somehow that the device is no longer accessed by anything.

I don't know how to do it with HAL, but it's possible with sysutils/automounter. In that case mounted partitions will have the access rights of the device nodes that can be set using devfs.rules. Note that the access permissions should be set for the geom labels (e.g. msdosfs/*) instead of...

This is most likely the solution. BTW, you can turn HAL support off in the xorg.conf (of course, you also should deactivate HAL in your rc.conf).

There's a group of people in the German community who regularly tries to get wine running under amd64. We've been getting closer, a lot of bugs preventing this have been fixed. I've solved a lot of the mysteries of getting i386 jails running. Yamagi's been keeping in touch with the right people...

-o res might help you find processes that have a memory leak, because that will sooner or later be the process that reserved most memory. And end up at the top.

Did you actually test that? I'd like to know whether it works, because we might just be having the same symptoms and not really the same problem. If the solution works for you, too, it might mean that HAL is not the cause. An alternative suspect would be (to me) gamin. I've got nothing to back...

I actually don't set any env variables. The defaults seem to be fine to me. I only ran -M 4G to get a decently large cache. But 4G is really a lot more than most people need. Ccache really just works fine. The benefits only show after having used it for a longer time. My current cache hit rate...