Linux Compatability
hi i have 2 distinct questions, and first is, i installed a linux app (binaries) and it failed when run complaining that it needs a "CPU with SSE instuctions enabled". does anyone know what this is and related too? i am running 7.2-prerelease i386 with linux_base-fc4. the only setting i have is fallback_elf_brand=3 (no osrelease) has anyone ever come across this? 2nd question, is the freebsd base (usr/src) documented anywhere, as to the programs it entirely contains? i thought developers handbook, but all i found is description of the directories in usr/src/ (unless i missed it elsewhere). besides that, is there any kind of database app in the base system no matter how compact/basic? if not, what would be the *closest* in ports? thanks in advance for any info ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Linux Compatability
Paul B. Mahol wrote: On 3/18/09, rasz wrote: hi i have 2 distinct questions, and first is, i installed a linux app (binaries) and it failed when run complaining that it needs a "CPU with SSE instuctions enabled". does anyone know what this is and related too? For example, mplayer check for SSSE3 but it will fail even if your CPU supports it because gcc that ships with freebsd (4.2.1) doesnt know about SSSE3. I dont know what's happening in your SSE case. vaguely my first thoughts were that the app makes some checks for SSE but in the wrong place freebsd-wise. i thought i'd try mailing the developers now, see if they have some insight. thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Blundered with gnome-desktop
manish jain wrote: Hi all, I blundered - I downloaded the latest ports tarball and did a 'make install' in deskutils/conduit. The conduit port asked for a deinstall followed by a reinstall in gnome-desktop, which I promptly complied with. As was bound to happen, everything in gnome is now broken/paralysed. Being a gnomer, I do not want to abandon my gnome environment. Just to make sure before attempting recovery, will the following 2 steps generally be able to fix things for me : #1) pkgdb -aF #2) portupgrade -L /var/gnome2-upgrade-logs/portupgrade-%s::%s.log -l \ /root/gnome2-portupgrade-results.txt -vrR -x gnome-desktop gnome-desktop just in case, do you know if your gnome before this was updated to lastest version (2.24.x) ? cuz the above could get messy if you had previous version and only updated gnome-desktop. (there is something in ports/UPDATING) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: nvidia-drivers crash computer on X start
RW wrote: On Sat, 28 Mar 2009 13:53:43 +0100 Anders Holmström wrote: The current xorg.conf I'm using is listed below. It was generated with X -configure. I've used many different xorg.confs, but they've all more or less been using the same settings as below, I don't know if it will help, but the nvidia driver has its own utility for generating xorg.conf: x11/nvidia-xconfig ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" did you try Option "AllowEmptyInput" "off" in Serverlayout section under screen, keyboard, mouse? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: nvidia-drivers crash computer on X start
Anders Holmström wrote: did you try Option "AllowEmptyInput" "off" in Serverlayout section under screen, keyboard, mouse? I was told by a guy on the nvnews.net forums that I should put machdep.disable_mtrrs=1 in my /boot/loader.conf. Apparently he had had the same problem and he said it was because he had more than 2 gigs of ram. He had solved it by that setting, and later by simply removing the ram. I have 4 gigs, and the setting did work for me. HOWEVER, now that I startx it's impossible to move the mouse/use the keyboard. It also complaints about not being able to locate driver "kbd" and driver "mouse", plus mentions AllowEmptyInput as the culprit. I tried disabling it but it in xorg.conf, but didn't help on the input device issue. X still started though. I didn't think the two were related, but based on your post I guess they are. You could (or somebody else) possibly enlighten me a bit more about the relationship, or point me in the right direction? man xorg.conf didn't give much info. i am not sure about the machdep setting there so i cc'd the mailing list maybe someone else can help you there. about the AllowEmptyInput however, there is some info in ports/UPDATING round about when xorg was updated because I am not sure if you said you disabled the mouse from xorg config instead of moused in etc/rc.conf ( if that is what you said). i have moused_enable="NO" in etc/rc.conf and add Option "AllowEmptyInput" "off" in xorg.conf.new right after a Xorg -configure. also, i think you have to test cuz ppl get different setting to work depending their hardware, but i have had similar problem as you with moused enabled and AllowEm...added. ( i have only 1gb memory fyi) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: too many video drivers
John Nielsen wrote: On Tuesday 31 March 2009 03:08:14 pm Tsu-Fan Cheng wrote: I am rebuilding ports and realize that i have too many input/video drivers for x-win installed. i know i need nv driver since my graphic card is from nvidia, and i want to deinstall all others. but i am not sure if its safe to do so, e.g. i am confused by "xf86-video-chips" since i don't know what kind of "chip" that stands for. can someone tell me which are basics and which are safe to remove? thanks!! Obviously you should keep mouse, keyboard and whatever driver(s) you actually plan to use (nv in this case). It's also a good idea to keep vesa as a fallback option. I habitually also keep the dummy driver though I'm not sure what it's used for. Everything else is fair game and should be safe to remove. "Chips" is (or was) a video card vendor so if you don't have such a card it's safe to remove as well. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" also, once you removed/kept what you want, don't forget to reinstall xorg-drivers port (meta-port). i think you get complains about missing dependencies otherwise. (rebuild xorg-drivers with just the drivers you want) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Ports options not coming up
Da Rock wrote: I'd to debug this, but I'm not even sure where to start. On just one system since some recent updates I have no options screens coming up for ports. I get a blue screen and then nothing; stdout says options unchanged. It is a vm if that means anything? Cheers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" if i understand you correctly, and this is the same thing, i have had this happen when building ports in a terminal emulator of sorts, particularly the xfce4 one (and maybe kde4 konsole) when the actual window is too small (e.g. in number of lines). i would see the blue screen for a bit and then options unchanged. it doesn't happen if at all if i keep the window a good size, but i don't know about VM. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
write dma udma icrc error
hi, can anyone tell me what this message is related to? WRITE_DMA UDMA ICRC error (retrying request) LBA=62939519 drive/hardware failing? i am seeing a lot of it lately on a particular disk where i have tried a few different installs and do not always get this problem. i have seen it disappear after some painstaking before an install to it, like wiping the whole disk clean before install, checking geometry is right, but maybe coincidence? it is a sata300, 7.2 beta1 amd64 and i am thinking there is problem with the disk, but the error varied a bit with different installs (i.e. whether i see the error or not) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
