Search results

I don't recall the exact number but very similar. I think ugen1.3. I'll give it a try later. UPDATE: "usbconfig -d 'device number' power_off" works. I'm guessing this number will stay the same until I start adding or removing usb devices.

When I use xinput --list-props I can see that the touchscreen was successfully disabled, Enabled=0, but shortly afterwards becomes Enabled=1. Similarly, I can kdlunload the module but until I moved the .ko file it would auto reload. I do see a message for usbgen referring to the touchscreen...

I've noticed something strange with a damaged touchscreen. When I disable with "xinput --disable" it's only temporary. Quickly changes to enabled within 20 seconds. Is there a way to disable an input device for a session? Update: Couldn't find a trivial way so moved the kernel module. That...

Powerline kits only work on the same circuit. I did need to reset some Netgear kit using the OS X/Windows utility. These were used and the hardware reset switch didn't work for me for some reason. After the reset I was able to use them with any operating system.

Check which soundcard is the default and modify with 'sysctl snd.hw.default_unit=N' with N=0..2 on your system. Then 'cat .profile > /dev/dsp'. With my system I have the onboard and addon soundcards. I've also managed to have loose connections or plugged into the wrong plugs entirely.

Have you checked to see if the program builds on FreeBSD without using the linux layer? You would also need to install a linux base system before anything else. I think the current favored base system is fedora 10.

I haven't used mplayer from a console in years but last time the output was to an SVGA framebuffer in an earlier version of slackware. Not sure what FreeBSD has for that now.

I believe the maximum supported resolution of the graphics card is 1600x1200 at 24 bits. You could try a lower display depth or lower resolution like 1600x900.

Did you try my suggestion for clearing the start of the memory stick in post #6 prior to setting up the image? I had the same thing happen with my tests before I did that. You need to make sure that the old settings for the memory stick aren't still being used by your system after clearing...

I'm pretty sure you're right. Everyone likes to complain about something. Just look at all the occupy something groups. There's probably some driver issue with the radeon mobility 7500 that I haven't seen before. Incidentally, the firefox7 binary segfaults while other browsers work.

I did not install from ports. The install was done using the FreeBSD 9.0 memstick image and Xorg was added using pkg_add. Perhaps there is a problem with some binary package. I'll do another test install after RELEASE.

AEI enabled is fine and I don't care about that one way or another. The keyboard and mouse being disabled regardless of hald and dbus is another matter. There should not be a requirement to create an xorg.conf file just to get a keyboard and mouse. I make the assumption that nobody has a...

That is very interesting but not the situation. On a new install Xorg enabled AEI without having any configuration file and does not vary regardless of HAL or DBUS running. After creating a bare xorg.conf that disables AEI there are no issues with the mouse and keyboard. Let me repeat...

The default is to enable AEI and disable the keyboard and mouse. That isn't acceptable.

I'm not messing with AEI. I installed FreeBSD and xorg. Xorg disabled both the keyboard and mouse. The new install of xorg enabled AEI as the default.

That can't be correct. In a new install I see the following line in Xorg.0.log (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. Xorg is disabling kbd and mouse plus there seems to be a hard lock (sometimes) when exiting Xorg. That is without any...

I've used zfs on a p3 with 1GB of ram and some tweaks for low memory systems. There may be some power saving issues that I didn't look for. I didn't notice any difference in performance from ufs other than the larger memory requirements.

You could try the PC-BSD 9 live or install dvd/usb image. That uses FreeBSD 9 and will have the same version of zfs. There is also the openindiana and oracle's solaris express cds.

EXT3 is forward compatible with EXT4. An EXT4 system can be mounted as EXT3 if extents aren't enabled. Is the ext2fs feature complete for EXT3?

What were the gpart commands you used to partition the drive? Also, have you looked at the http://wiki.freebsd.org/ZFSOnRootWithZFSboot page?