Search results

Little improvement. Kernel panicked with the ataraid device removed and again after wiping the drive completely and reinstalling. However, the /dev/ar0 warnings are now gone.

No, I destroyed the array using the RAID BIOS management utilities. It is currently a stand alone drive. I also wiped the drive prior to installation, although the RAID watermark made it past. I removed all of my make.conf options except for the -march tuning and rebuilt a new kernel without...

Problem report amd64/154629 submitted and awaiting moderator approval.

Where is the preferred location to upload the core files, or should I just host them on a 3rd party site and include the URL in the problem report?

Correct, it is the GENERIC binary straight off the ISO image. Understood, which is why I keep my CFLAGS fairly conservative, and my COPTFLAGS even more so. And if something I build does puke, one of the first things I do is grab the pre-compiled package/binary to see if something in my...

Two notes: 1) The default GENERIC kernel that came with the installation ISO also panics 2) I've used this make.conf file since FreeBSD 3.x with no other issues Are you suggesting that I am hitting a bug that manifests itself with the default packaged kernel and custom CFLAG kernels, but...

Here are all of the combinations I've used where I've had a kernel panic: 8.1-RELEASE/i386 - GENERIC kernel (panics) 8.1-RELEASE/i386 - custom kernel (panics) 8.2-RC2/i386 - custom kernel (panics) 8.2-RC2/amd64 - GENERIC kernel (panics) 8.2-RC2/amd64 custom kernel (panics) When building a...

Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0xffffffff80649f27 stack pointer = 0x28:0xffffff808a3f69d0 frame pointer = 0x28:0xffffff808a3f6a00 code segment = base 0x0, limit 0xfffff, type 0x1b...

My FreeBSD 8.2-RC2 system is repeatedly generating kernel panics. I'm about ready to submit a report via the send-pr system, but I'd like to know what I should do with the core file. The various how-to guides over on the main FreeBSD site mainly discuss attaching patches, not multi-gigabyte...

You'll need to add VESA framebuffer support to your kernel. This will allow you to set your console to a higher resolution. First, add these lines to your kernel conf file: options VESA options SC_PIXEL_MODE Rebuild your kernel and then reboot. Next, you'll want to see what screen modes...

Interestingly, the same issues plagued the products I mentioned earlier. One was a more minimalistic product that acted as a natural extension of existing GUI functionality, the other was a revolutionary feature-rich suite. They came with radically different programming interfaces, resource...

I agree. The widget toolkit war in X between GTK, QT, Wx and Motif is a major issue that the FreeDesktop folks need to iron out. This isn't just an issue for FreeBSD, but rather, for all open source operating systems that mainly rely on X. Looking back in history, AmigaOS went through a...

I'd say, "not quite". The Xorg video drivers for FreeBSD are a bit rough, especially in the area of XVideo and OpenGL. Even our flagship Nvidia proprietary drivers are best used for Geforce 7-series cards. Internet use is a bit rough, too. The Java JRE libraries are a PITA to download...

One note of caution: Make sure that you install the fusefs-kmod 0.3.9.p1.20080208_5 port. There is a known issue where the fusefs write buffer does not perform a writeback in a timely fashion. According to PR/122907, uncommitted data can remain in the buffer for as long as 15 minutes...

There is a commercial utility called "UFS Explorer" for Win32 and Win64 that includes support for recovering files from many BSD and Linux file systems, including Ext3, HPFS+, NTFS, ReiserFS, UFS2 and XFS. I gave it a spin today on a UFS2 partition and found that, compared to my experiences...