Search results

Hi all! I see all over the Internet instructions of how to chainload the loader from GRUB, which is NOT what I'm trying to do. It seems Debian GNU/KFreeBSD uses GRUB to boot the kernel directly, how can this be done from a normal freebsd FreeBSD install?

Undefined references I get undefined references to environ and __progname from libc.a when linking certain programs statically. What I'm wanting to know, is if there is anyway to force libc to build with those symbols defined, or is there any way I can use objdump to define it?

I would not link GNOME 3 statically, for shared linking freebsd FreeBSD's libc is fine, but for tiny programs, a tiny libc would be nice.

Hello, I've been working on a small project for myself lately, a distro, using the freebsd FreeBSD kernel, and libc, with GNU's userland and toolchain, and to build the entire OS statically linked. I got all of this done, and even have several self-contained packages, such as X, and GNOME 3...

Hi all. I'm trying to build a completely static userland, and most things work fine simply having LDFLAGS=-static in /etc/src.conf. However some builds fail with undefined references to environ and __getprogname. Usually this is fixed by adding some library to your linker flags, but I'm not...

I would suggest not trying to write to the partition, Linux kernel doesn't have very good write support for ufs, I doubt the debian kernel is even compiled to support ufs write though either way.

for some reason, freebsd-8 netbsd-current and even on linux i believe. the cp command loops when doing this cp -Rvp /home/user/path/.* /home/user/path/ I do this to copy all my dotfiles. example of what i mean by loop cp /media/hdd/.zshrc > /home/user/.zshrc cp /media/hdd/../hdd/.zshrc >...

I have had the same problem. I can confirm that (in my case) it's not hardware failure. it happened with old mobo. new mobo, it happens in amd64 freebsd. not yet in i386 similar problem happens in netbsd-current, netbsd-stable, and opensolaris. I have absolutely no idea why this happens, but it...

Your kernel source tree was probably newer than your running kernel. I had this problem running stable and current, always make sure to build and install the kernel from your tree.

May I ask how you have that menu and dropdown info? and maybe the config for it? :e

@oliverh, would i happen to need 8-STABLE to compile mesa? I got past those intel dri compile errors only to get intel_drm errors, figured it had something to do with me running -RELEASE.

Sorry I should have mentioned, I am using 8.0-RELEASE, i'll try the options in fronclynnes xorg.conf and post back. Edit: still no good, even with radeonhd-devel can't post log because its too long, tried code tags.

Could you post your xorg.conf? I had the same problem with my friends m200(mobile radeon 200, cant remember if thats the actually name).

Sorry to bump, but shouldn't xf86-video-ati have 2d xv accel for all cards. I'm not trying to get 3d, although I am interested in pulling in the git driver, I would however like 2d support and the ability to play fullscreen videos in mplayer without -zoom.

not sure if this is any problem but here are some hardware specs amd athlon 64 x2 3gb ram nvidia geforce 6150 se integrated graphics if anything else is needed just ask

late reply, but the problem is still there, completely reinstalled 7.2 and have tried 8.0-current, it doesnt really reboot on current, it also has this problem on the console, so i suppose that rules out the nvidia driver

no everytime i start finch i get a segfault 11 when my buddy list comes up, it was just coincidence that it had a panic right after. /edit i might just reinstall freebsd, i stole alot of configs from pc-bsd and built a custom kernel, both were unnecessary. if i get the same problems with 7.2...

i think i might have to delete /var/crash/core.txt.2 i had used crashinfo a few times before i enabled core dumping and it wrote to that file, but now that i have a vmcore.2 its writing to the same file but nothing has changed at all, its the old crash. the exact same in every way to the one a...

@dutchdaemon, that gave me the exact same thing i posted a while ago, that large segment from crashinfo

well it happended again, and now i have a core dump in /var/crash called /var/crash/vmcore.X (x being a number, i have 0-2) but this file is about 345mb, so how do i know what to post? thanks in advance, and hopefully ill get this problem solved before i have to change back over to that...