I was running into this problem to. I ended up solving it by adding support for all the permutations of [OUEX]HCI and "high speed usb2/3 bus support" into my kernel. (Not sure why they were disabled, I must never have noticed them while installing.

For reference:
CONFIG_USB_OHCI_HCD=m
CONFIG_USB ...

dunno. i just see symlinks in / as a bad thing. also if portage can swap /lib and /lib64 at will, that is rather troublesome...

well, it appears to have worked flawlessly. the only hitch i had was with postfix (looked like some form of a symlink) but that went away when i recompiled it after removing the /lib64 and /usr/lib64 symlinks. thanks for the guide.

well, im 2/3s of the way through the first system, and i must say this is going pretty well. is there any reason the no-multilib profile doesnt do this by default? especially on hardened, this only seems like a security hole...

yay thanks. gonna try it this afternoon/tommorow

this is on a server, so i would rather avoid having 3rd party binaries being ran, i hate java, and refuse to waste my time installing openoffice (im an abiword fan too). and i also watch my portage updates carefully, so perl/gcc or anything else ...

well, currently its a non-booting new install, and i was just about to recompile everything anyway (already chrooted+screened), so ill give it a go.

apparently it needs /lib64 to be present for chroot to work though, so that might present some problems? right not its just a symlink to /lib, but ...

sorry if this is borderline OCD, but i have a pure 64 bit server (no multilib), but there seems to be a strange dependence on the existence of /lib64. what the hell? anyone know how to fix this? portage seems to be forcing the programs to be linked against /lib64, and constantly re-arranging root so ...

ok, thank you, after enabling lo to do its stuff (input AND output) it works now. thanks.

yes, everything works when the firewalls down. yes, i want x11-forwarding. heres the script, see if you can find any errors.

#!/bin/bash
IPTABLES="/sbin/iptables"

$IPTABLES -P INPUT DROP
$IPTABLES -P OUTPUT DROP
$IPTABLES -P FORWARD DROP
$IPTABLES -F

$IPTABLES -A INPUT -i eth0 -p all -m state ...

as i said in the first post, X forwarding works fine without the firewall on.

when i turn it on, everything goes to hell.

xauth is installed already.

No, just trying to get ssh and X to work. I have port 22 open, but its still stopping X. scp and normal ssh work fine though.

Hello, ive been all over google, the forums, the iptables site, and #iptables on freenode, but no one seems to know how to do this.

Is there any way at all to forward x11 connections over ssh (ssh -X) with iptables set to drop by default? I also cant figure out what ports X is using with the ...

their search is very hit and miss. you just have to look at the obvious ones, then apoligize when the connect your bug to someone elses

you might want to supply the modded ebuild with a bug report on the tracker so it can get into portage.

xorg is dependant on xinit because thats the tool used to start X. i assume you can just install X and leave it unstartable for the hell of it?

virtual/x11 should just collect all the X packages needed for a build, but that shouldnt need xdm, xorg should require xdm. if it really annoys you, file a ...

it looks like its hardcoded into the ebuild. youll either have to path the ebuild, or submit a bug report.

a revdep-rebuild might fix things. or else i would try remerging X and mesa, then see what happens.

yes, the app is already trying to set a transparency, and X7 doesnt play well with pngs (i dont know about other formats) setting their own transparency. filing a bug with X.org might work...

i dont know, i wonder if you have the driver "nv" installed instead of "nvidia". isnt nvidia the foss one, and nv the binaries from Nvidia? or try Altezza2k2's solution and see if that works.

bah lazy nvidia people need to make a tool to do this. atis fglrxconfig thing is pretty nice, and gives you a generally working xorg.conf...

ok, use X -configure or something to try to make a xorg.conf, then post any errors you get. we can start debugging from that. errors are either dumped on the ...

do other dri apps like games work? best way to test it would be bzflag, unless you have another dri game that you can easily benchmark with

well, i would say dri works, but glxgears is broken. recompiling mesa might fix it...

an "emerge -auD world" should help clear things up. it should bing in whatever package you acidently deleted.

yes, where are you confused at? the partitioning? making the filesystem is as easy as just formating the partition with whatever format you want (probably ext3 or reiserfs)

do you need help making partitions or picking a fs type, or something else?

are you looking in the right place? /etc/X11/xorg.conf? could you paste a "ls /etc/X11" ?