Thank you for the nice little tutorial on the REQUIRED_USE syntax. It did the trick with installing asciidoc!

I installed grub on another hard drive and it worked. Then I tried installing back on the original drive (sda) and it worked again. So I'm back in business. I suspect it has something to do with btrfs and its stickiness and the fact that you cannot change the UUID on a drive or partition. At least ...

Hi. I had a fine working Gentoo system. I had my system files on /dev/sda5 (ext4 formatted) and my home directory on a btrfs array of four partitions. Last week I ran btrfs-check on /dev/sda5 and it returned errors, and the btrfs-repair function did not fix it. Although the computer still worked ...

Zeroed out /dev/sde and then copied the partition from another drive as I had before, and grub2 installed without a problem. Would have liked a more elegant (and less laborious) solution, but at least it worked!

Yesterday I was installing btrfs when I gave the fatal command to format a partition but forgot to include the partition number! So the drive was wiped and the functioning RAID devices (a RAID1 and a RAID5) were decommissioned. I used sgdisk to duplicate the partition structure from a mated disk and ...

Installed the latest version of Slackware with the 3.14.4 kernel, and everything worked perfectly. However, this was not on a software RAID foundation, so no proof yet that the fault lies in gentoo-sources. Now I have to make RAID partitions and see what happens.

Sorry for Hijacking your thread, but I have a similar problem.

Root is on btrfs
Nvidia-drivers-337.19
Gentoo-Sources-3.14.4


Gentoo Sources 3.13. runs fine even with Nvidia-drivers-337.19.
Hijack away musv. I'm glad to know someone else has essentially the same problem. A few differences: my ...

Oops. Not time for huzzahs yet. Yes, it booted into X, and yes, I was even able to emerge files. But when I ran revdep-rebuild, it got hung up at 2%. I tried it again, and it got stuck at 2% again. I rebooted into 3.13.5 and it ran revdep-rebuild without a hitch. I rebooted into 3.14.3, ran revdep ...

Eureka! The new gentoo-sources-3.14.3 did the trick. Without changing any settings, I ran on the .config I used for 3.14.2 and voila! It works perfectly. At least so far. I'll get back in case it freezes, but it doesn't look like that's going to happen from its behavior so far.

I use 3.14, X and BTRFS and have no such issues.
I do not think you should keep focusing on "it must be btrfs".
Also I let btrfs do the raid. btrfs on top of hardware raid is... odd?

I changed to btrfs a year after setting up my computer so I didn't want the agita of converting mdraid (which is ...

I found that using a /tmp directory, /var directory, and /var/tmp directory formatted in ext4 rather than btrfs enabled me to boot into X, but things would lock up after some usage. Seems that there is a problem with btrfs and raid 5 in 3.14. Those three directories I just listed were all lvm2 ...

What do you mean "nothing happens"? Does the xterm not appear? Does the xterm appear but fail to start a shell? Is some error message printed?

In either case, whether I can boot into X in a 3.13 kernel or whether I can't with a 3.14 kernel (I've also tried 3.14.2 this week), after I vt-switch and ...

According to man xterm , xterm understands the command line option -display display . It states This option specifies the X server to contact; see X().

No luck. When I'm in X (using kernel 3.13.5), I get DISPLAY is :0. I get this value from a set command and see how DISPLAY is defined. When I ...

Hu wrote:According to man xterm, xterm understands the command line option -display display. It states This option specifies the X server to contact; see X().

Thanks, Hu. Will try this late tonight when I'm back home.

What happens if you vt-switch to an unused console, log in, and start an xterm pointing at the local X server? Does the xterm render? Can it be used normally?

Hu, I understand your request up to "start an xterm pointing at the local X server". I don't know what you mean here. How do you start an ...

To Hu, if I vt-switch to an unused console, kill X, and then startx, still no bananas. Also no bananas if I use xdm instead of kdm.

To ng-cat, my rootfs (/) is formatted as ext4. Only the partitions listed in my first posting are btrfs. I'm thinking of formatting /var and /var/tmp in another ...

Hi Hu,

Here's the Xorg.0.log obtained by starting in X, it hangs, and I got to a console as root and copied the file. It looks OK to me. What do you think? Here it is:

[ 14.416]
X.Org X Server 1.15.1
Release Date: 2014-04-13
[ 14.416] X Protocol Version 11, Revision 0
[ 14.416] Build Operating ...

Here is the dmesg output starting at stage [5]. Please let me know if you want me to give you the output from the beginning or if you want to see output from a successful boot with 3.13.5.

[ 5.205519] systemd-udevd[3280]: starting version 212
[ 5.693920] [drm] radeon kernel modesetting enabled ...

Hi Hu. Thanks for responding. I made a new user and home directory but the same thing happened. The problem has to do with btrfs. The computer gets hung up on kdm and the stopwatch symbol before it even gets to the opening screen, so it doesn't even access the home folder before it freezes. And if I ...

Hi. I upgraded to 3.14.1 from 3.13.5, which worked (and still works) perfectly. However, when I try to start up 3.14.1 it freezes at kdm, where the stopwatch (at kdm) just stays on. /boot is formatted with ext2, /usr is formatted with ext4, and /var, /var/tmp, /home, /opt, /tmp, /usr/portage, and ...

Spinmc, many thanks. I've been hung up on this jpeg issue, and the static-libs use flag did the trick. Excuse me now while I install a batch of ebuilds!

I was able to get Wine apps going again by doing the following:
emerge =media-libs/libpng-1.4.8
emerge wine
emerge libpng
Do not delete libpng-1.14 as suggested. That library needs to survive. You will now have libpng-1.5.5 installed (as of today) but the lingering library file from libpng-1.4.8 ...

No, I removed libpng-1.4. But I'll try your suggestion anyway when I'm back home. Thanks.

The odd thing is that it says it was compiled with 1.5 but is running 1.4. Hmmm.

I suddenly got the following message over the weekend while starting Quicken through Wine:

Your Quicken program files (not your data files) may have been damaged.
You will need to reinstall Quicken.

When I started it from the command line, I got the following block of text, repeated about 15 ...

Just an idea. I had problems after I installed a new kernel with the nvidia module not loading and thus I had no X. I ran (as root) to create a new xorg.conf and voila!