ballsystemlord
-
Content Count
29 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Posts posted by ballsystemlord
-
-
All the rest of the time I can figure things out for myself, but this time portage has me fooled. I was having trouble rebuilding mesa and this new update pulls in a new version of llvm and clang.
See the output of portage at:
-
Tried xopengl 11, my screen goes blank and does not come back, even after killing the X server.
I also decided to try to use the radeon opensource drivers, since they should support my 7780 card, according to http://kmuto.jp/debian/hcl/. The screen, while booting, looked like it was very stretched and I looked in the kernel config to see if I missed something and I tried passing nomodesetting and then it works for a terminal now. Alas, xorg unloads the drivers when it starts. I thought I should pass some mode settings for my monitor through xorg.conf but it does not recognize them. The driver it selected, fbdev, when running using sdl or opengl and any app that utilizes them turns the screen of every 3 secs for 2 secs.
Here is my xorg.conf (I tried learning from aticonfig to no avail):
https://bpaste.net/show/576420c5a340
And the logs:
drivers ati, opengl ati,
https://bpaste.net/show/d88809627419
drivers ati, opengl x11,
https://bpaste.net/show/f22ff809da89
drivers OS radeon, oepngl x11,
https://bpaste.net/show/2e6bfec879c0
Thanks, David
-
Got it working! Kinda...
I figured out why the /sbin/v86d file was missing, I ran make clean before I used genkernel! The reason that the radeon drivers were not loading was because of a kernel option I configured CONFIG_X86_SYSFB to on, which does not affect the drivers, on my laptop (intel), but does interfere with fglrx.
However, I still have a problem, I can't use anything with opengl. My Xorg log is located here https://bpaste.net/show/a4f28b122134. Any help would be appreciated. My kernel config is located here: https://bpaste.net/show/6649db1c7ee0 . The kernel's log can be found here: https://bpaste.net/show/3a3494f49a6c . Thanks!
-
I think I found the problem with the fglrx drivers, now how do I fix it?
As a heads up to the funtoo devs, the uvesafb drivers fail to start because it claims that /sbin/v86d does not exist or is not executable. It both exists and is executable, though the kernel may be trying to load it from the initrd and I've not checked yet if it exisits there; so your wiki page may need to be changed.
-
So, which python 3.4 version does funtoo support/recommend unmasking?
I have a choise of:
dev-lang/python-3.4.0-r1000
dev-lang/python-3.4.1-r1000
dev-lang/python-3.4.2-r1000
dev-lang/python-3.4.3-r1000
dev-lang/python-3.4.4_pre20150621
dev-lang/python-3.4.4_pre20150628
dev-lang/python-3.4.4_pre20150705
dev-lang/python-3.4.4_pre20150712
-
I've figured part of this out, I turned off the module versioning support in the kernel and now the module loads, but it is still not working right. I still get a black screen. Uvesafb still does not work. I won't post modinfo, it's too big.
-
I followed the instructions but uvesafb does not work either. I know that the card works, it was great on Opensuse with the ati drives.
I did the smart thing and setup a boot script to try to load the aiti drivers and got the following error message.
modprobe: ERROR: could not insert 'fglrx': Required key not available
I turned off the SIG check but that did not help (CONFIG_MODULE_SIG=n).
I don't know what the uvesafb modules is so I could not load it.
I asked about this at irc #kernelnewbies but they only said that I should use the regular old ati driver from the kernel. If this is so then funtoo should not support the ati proprietary dirvers.
-
Acctually, nothing, because I'm booting into a terminal, not X; but thatnks for asking you got me thinking and I opened my systems logs and so now I have more to post.
Here are the three logs from my system.
-
Hello, I'm encountering a most annying problem, my system boots up with my custom kernel and initramfs (both created by genkernel, though I did the configuring), but I can't see anything. The system changes that state of the numlock key, reponds to ctrl-alt-del, cleans tmp, but I can't see a thing. I have merged that ati-drives.
The default debian kernel does output messages.
My card is an amd 7770. My kernel version is pf-sources 3.19_r1, grub 2.02_beta2-r3, boot-update 1.7.3, and genkernel 3.4.40.7-r6.
I did read the ati install guide and follow the directions.
Thanks.
-
Sorry about the missing code tags, I tried to add them manually. There is currently no options for smilies or anything in firefox.
-
This message is mainly INFORMATIVE.
I got this weird error during my installation and tracked it down to an env array called "path" (lower case).
It was not eliminated when I ran: evn -i bla and so I had to kill it manually.
You will get an error like this:
/bin/sh ../libtool --silent --tag=CC --mode=link x86_64-pc-linux-gnu-gcc -pipe -O2 -march=native -mfpmath=sse -m3dnow -mmmx -msse -msse3 -msse4a -mpopcnt -mabm -mfxsr -msahf -mrecip=all -minline-stringops-dynamically -frecord-gcc-switches -ggdb -ggdb -ggdb -ggdb -ggdb -ggdb -ggdb -ggdb -fno-strict-aliasing -D_USE_MMAP -fomit-frame-pointer -Wall -Wpointer-arith -Wsign-compare -Wmissing-declarations -Wdeclaration-after-statement -Werror-implicit-function-declaration -Wstrict-aliasing -Warray-bounds -Wstrict-prototypes -export-dynamic -release 0 -version-info 13:60 -thread-safe -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -o libzzipwrap.la -rpath /usr/lib64 wrap.lo ../zzip/libzzip.la
/usr/bin: file not recognized: Is a directory
collect2: error: ld returned 1 exit status
Makefile:374: recipe for target 'libzzipwrap.la' failed
make[3]: *** [libzzipwrap.la] Error 1
make[3]: Leaving directory
To fix it run: export path=""
That killed it for me, but only after I preformed the chroot; in other words, it would not work outside of the chroot.
If you have any further troubles, feel free to ask.
-
Hello, now that I want to swith my desktop from Opensuse to Funtoo I remmember that some of the AMD cards requier a seperate binary only proprietary driver. The Linux kernel has been upgraded several times since 3.0 and so they might have a driver out or I might need to do some magic to get my card working properly, I'm not certain.
Mine is the R7770. Here's the output of lspci:
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Cape Verde [Radeon HD 7700 Series] (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. Device 2710
Flags: bus master, fast devsel, latency 0, IRQ 74
Memory at c0000000 (64-bit, prefetchable)
Memory at fea00000 (64-bit, non-prefetchable)
I/O ports at e000
Expansion ROM at fea40000 [disabled]
Capabilities: [48] Vendor Specific Information: Len=08 <?>
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
Capabilities: [150] Advanced Error Reporting
Capabilities: [270] #19
Kernel driver in use: radeon
I would research this myself, however, I'm not sure where to start since if I did a web search I'll undoubtably get a bunch of outdated info.
-
Figured it out at last, I was using the bulldozer stage3 tarball when I needed that stage3 k10 tarball, so, strange though it may seem, instead of signalling because of an illegal instruction in the executing of any of the afore mentioned binaries, I got a: no such file or dir error.
-
Hello, I wanted to set up a firewall and on my previous distro, opensuse I used yast to do it and it was an on off type deal. With funtoo it requires that I start the service and test that ot's working the way I want it to and I wanted to know how I could make changes and apply them, now, instead of saving them permenently.
If I run /etc/init.d/iptables start (which I think you do to start the firewall), then it needs me to save some rules and I only wanted to see how those rules affected the firewall, to make certain that I know that what I'm doing is the right thing.
This may not be the bast way to do this and you can recommend another one, as I said, I've never actually used iptables before.
-
Here is the cotents of /boot
EFI
System.map-3.18.11-gentoo1
config-3.18.11-gentoo1
grub
vmlinuz-3.18.11-gentoo1And this is /etc/boot.conf
boot { generate grub default "Funtoo Linux" timeout 3 } "Funtoo Linux" { kernel vmlinux[-v] }I'm really not seeing my error.
-
I fail to understand, what is this topic needed for? I mean, I don't have systemd and I'm guessing that you don't, so why bring it up? Is Pottering infesting another direly needed program or something that we should all be shocked and horrified and create a fork of this program or some such thing?
-
I'm encountering a strange problem while trying to install funtoo
on my desktop. The files which I extract from the stage 3 tarball
refuse to be executed.
I tried the following (not in this order):
Mounted filesystem --rw -o exec.
fsck -f /dev/sda3
cp bin/bash /root && /root/bash
cp /bin/bash . && chroot . bash -l
The above command failed because bash could not find the shared
object (.so) files.
tar -xpf stage3*
cat bin/bash
find bin -exec file --mime-type '{}' \; | grep -v application/x-executable
I then executed bin/gunzip as it was a shell script and it ran fine.
I tried changing my PATH.
I always get the same error for all operations.
Here's the name of the stage 3 tarball:
-rwxr-xr-x 1 root root 300494916 May 26 06:54 /mnt/gentoo/stage3-amd64-bulldozer-funtoo-stable-2015-05-25.tar.xz
Here's the error I get when executing a binary file:
zsh: no such file or directory: /mnt/gentoo/bin/bash
The files show up with ls.
The version of the cd I'm using is 4.5.0.
The kernel is 3.14.31 std450 amd64.
A simmilar problem occurs when using knoppix from a dvd (knoppix is 32bit,
version 7.2 kernel 3.9.6, this rescue cd is 64bit, booted UEFI with the
black screen, default option).
The error is:
bash: /media/sda3/bin/bash: cannot execute binary file
If I boot it in 64bit mode it returns the same error as above (except
that knoppix is using bash, of course). I suppose that it might be a bad
archive, but then xz uses 64bit crc checksums so xz should have said
something to tar indicative of an error. I just decompressed it with
plain xz and used echo $?, there is no error. Of course you can turn off
the checksum but I doubt you would have, I typically change it to sha256.
Here's my hardware list from lspci -vk :
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx0 port B) (rev 02) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx0 port B) Flags: fast devsel Capabilities: [f0] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [c4] HyperTransport: Slave or Primary Interface Capabilities: [40] HyperTransport: Retry Mode Capabilities: [54] HyperTransport: UnitID Clumping Capabilities: [9c] HyperTransport: #1a Capabilities: [70] MSI: Enable- Count=1/4 Maskable- 64bit- 00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port B) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 0000e000-0000efff Memory behind bridge: fea00000-feafffff Prefetchable memory behind bridge: 00000000c0000000-00000000cfffffff Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot+), MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [b0] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 5a14 Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [190] Access Control Services Kernel driver in use: pcieport Kernel modules: shpchp 00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port D) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 Memory behind bridge: fe900000-fe9fffff Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot+), MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [b0] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 5a14 Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [190] Access Control Services Kernel driver in use: pcieport Kernel modules: shpchp 00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port H) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: 0000d000-0000dfff Memory behind bridge: fe800000-fe8fffff Prefetchable memory behind bridge: 00000000d0000000-00000000d00fffff Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Port (Slot+), MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [b0] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device 5a14 Capabilities: [b8] HyperTransport: MSI Mapping Enable+ Fixed+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [190] Access Control Services Kernel driver in use: pcieport Kernel modules: shpchp 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40) (prog-if 01 [AHCI 1.0]) Subsystem: Gigabyte Technology Co., Ltd Device b002 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 19 I/O ports at f040 [size=8] I/O ports at f030 [size=4] I/O ports at f020 [size=8] I/O ports at f010 [size=4] I/O ports at f000 [size=16] Memory at feb0b000 (32-bit, non-prefetchable) [size=1K] Capabilities: [70] SATA HBA v1.0 Capabilities: [a4] PCI Advanced Features Kernel driver in use: ahci 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller (prog-if 10 [OHCI]) Subsystem: Gigabyte Technology Co., Ltd Device 5004 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18 Memory at feb0a000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci-pci 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller (prog-if 20 [EHCI]) Subsystem: Gigabyte Technology Co., Ltd Device 5004 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17 Memory at feb09000 (32-bit, non-prefetchable) [size=256] Capabilities: [c0] Power Management version 2 Capabilities: [e4] Debug port: BAR=1 offset=00e0 Kernel driver in use: ehci-pci 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller (prog-if 10 [OHCI]) Subsystem: Gigabyte Technology Co., Ltd Device 5004 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18 Memory at feb08000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci-pci 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller (prog-if 20 [EHCI]) Subsystem: Gigabyte Technology Co., Ltd Device 5004 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17 Memory at feb07000 (32-bit, non-prefetchable) [size=256] Capabilities: [c0] Power Management version 2 Capabilities: [e4] Debug port: BAR=1 offset=00e0 Kernel driver in use: ehci-pci 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 42) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller Flags: 66MHz, medium devsel Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4, sp5100_tco 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) (rev 40) Subsystem: Gigabyte Technology Co., Ltd Device a014 Flags: slow devsel, IRQ 10 Memory at feb00000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller (rev 40) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller Flags: bus master, 66MHz, medium devsel, latency 0 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge (rev 40) (prog-if 01 [Subtractive decode]) Flags: bus master, VGA palette snoop, 66MHz, medium devsel, latency 64 Bus: primary=00, secondary=04, subordinate=04, sec-latency=64 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller (prog-if 10 [OHCI]) Subsystem: Gigabyte Technology Co., Ltd Device 5004 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18 Memory at feb06000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci-pci 00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller (prog-if 10 [OHCI]) Subsystem: Gigabyte Technology Co., Ltd Device 5004 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18 Memory at feb05000 (32-bit, non-prefetchable) [size=4K] Kernel driver in use: ohci-pci 00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller (prog-if 20 [EHCI]) Subsystem: Gigabyte Technology Co., Ltd Device 5004 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17 Memory at feb04000 (32-bit, non-prefetchable) [size=256] Capabilities: [c0] Power Management version 2 Capabilities: [e4] Debug port: BAR=1 offset=00e0 Kernel driver in use: ehci-pci 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration Flags: fast devsel Capabilities: [80] HyperTransport: Host or Secondary Interface 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map Flags: fast devsel 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller Flags: fast devsel Kernel modules: amd64_edac_mod 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control Flags: fast devsel Capabilities: [f0] Secure device <?> Kernel driver in use: k10temp Kernel modules: k10temp 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control Flags: fast devsel 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 Flags: bus master, fast devsel, latency 0, IRQ 74 Memory at c0000000 (64-bit, prefetchable) [size=256M] Memory at fea00000 (64-bit, non-prefetchable) [size=256K] I/O ports at e000 [size=256] Expansion ROM at fea40000 [disabled] [size=128K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [270] #19 Kernel driver in use: radeon Kernel modules: radeon 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] Subsystem: Micro-Star International Co., Ltd. [MSI] Device aab0 Flags: fast devsel, IRQ 7 Memory at fea60000 (64-bit, non-prefetchable) [disabled] [size=16K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting 02:00.0 USB controller: VIA Technologies, Inc. Device 3483 (rev 01) (prog-if 30 [XHCI]) Subsystem: Gigabyte Technology Co., Ltd Device 5007 Flags: bus master, fast devsel, latency 0, IRQ 72 Memory at fe900000 (64-bit, non-prefetchable) [size=4K] Capabilities: [80] Power Management version 3 Capabilities: [90] MSI: Enable+ Count=1/4 Maskable- 64bit+ Capabilities: [c4] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Kernel driver in use: xhci_hcd 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) Subsystem: Gigabyte Technology Co., Ltd Motherboard Flags: bus master, fast devsel, latency 0, IRQ 73 I/O ports at d000 [size=256] Memory at fe800000 (64-bit, non-prefetchable) [size=4K] Memory at d0000000 (64-bit, prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00 Kernel driver in use: r8169 Kernel modules: r8169
-
/etc/issue is just printed to stdout prior to login. When I first installed gentoo I did not have one until I created one with a tux logo using the program linux-logo. You're welcome to create it, overwriting it is not a problem, if it were then your system would not boot correctly.
If you feel that this is a bug you can create a bug report or feature request at https://bugs.funtoo.org .
-
Test two
Should add text after newline to see if it gets eaten.
-
Hello, I installed funtoo according to the guide but I decided to custom compile the kernel and I used the gentoo-sources and boot-update is complaining about a missing bzImage. I have vmlinux and no initrd, I'm using UEFI booting and I do get the b/w screen. What should I do?
-
Test
-
I've submitted most of them.
And now I must apologize since I should have submitted one and then waited to see if it was in a good form (Duh!) Sorry!
I also should say that most of the use flags I diabled to install the software are in order (sometimes I would get tired of retyping a name and disable different use flags from different problems on the same line), and commented out (hash) in my package.use file and so if I missed anything or there is some other simmilar problem I'm going to post ALL the disabled use flags here:
# tmp #media-libs/giflib -rle #media-libs/urt -gif dev-lang/python -doc #media-gfx/autotrace -imagemagick #media-gfx/pstoedit -imagemagick #media-gfx/imagemagick -autotrace #dev-python/cython -numpy #dev-ruby/racc -doc #dev-libs/cyrus-sasl -openldap #net-nds/openldap -sasl -cxx #dev-python/pygments -doc #dev-lang/php -vpx #media-lbs/libvpx -doc #app-crypt/mit-krb5 -pkinit #dev-libs/openssl -kerberos #sys-libs/ncurses -gpm #dev-python/jinja -doc #dev-python/six -doc #dev-python/Babel -doc #x11-proto/xextproto -doc #app-doc/doxygen -qt4 #dev-lang/php -postgres #dev-libs/ossp-uuid -php #dev-db/postgresql -uuid #www-client/lynx -idn #net-dns/libidn -mono #app-crypt/mit-krb5 -openldap #net-nds/openldap -kerberos #media-libs/mesa -vaapi #xll-libs/libva -opengl #gnome-base/librsvg -tools #app-text/ghostscript -X #x11-libs/libXext -doc #x11-libs/libXdmcp -doc #media-libs/freetype -utils -doc #dev-python/packaging -doc #dev-ruby/rake -doc #media-libs/lasi -doc #media-gfx/graphviz -lasi #media-libs/opencv -ffmpeg #media-video/ffmpeg -frei0r #media-plugins/frei0r-plugins -facedetect #app-text/asciidoc -graphviz #x11-libs/libXaw -doc #media-gfx/graphviz -gtk -cairo #media-libs/libjpeg-turbo -java #x11-libs/libXmu -doc #app-doc/doxygen -latex -dot #app-text/texlive -X #media-gfx/graphviz -cairo #x11-libs/cairo -opengl #media-libs/mesa -vdpau #x11-libs/libvdpau -doc #dev-java/icedtea-bin -cups -X -nsplugin #media-gfx/graphviz -cairo #x11-libs/libxcb -doc #x11-libs/cairo -xlib-xcb #dev-lang/nasm -doc #app-text/ghostscript-gpl -X -gtk #x11-libs/libICE -doc #x11-libs/libXcomposite -doc #app-text/texlive-core -xetex #media-libs/gd -xpm #x11-libs/libX11 -doc #media-fonts/urw-fonts -X #x11-proto/xproto -doc #app-text/texlive-core -X #x11-libs/libSM -doc #app-text/xmlto -latex #dev-java/icedtea-bin -alsa #media-libs/alsa-lib -doc #app-text/ghostscript-gpl -idn #dev-libs/zziplib -sdl #media-libs/libsdl -caca #media-libs/libcaca -doc #app-arch/unzip -natspec #dev-libs/libnatspec -doc #media-libs/fontconfig -doc #media-libs/harfbuzz -graphite #dev-util/cmake -qt4 #dev-qt/qtgui -gtkstyle #x11-libs/xtrans -doc #net-print/cups -X #app-text/docbook-xsl-stylesheets -ruby #dev-lang/ruby -socks5 #dev-libs/libverto -glib #app-text/poppler -qt4 #dev-qt/qtgui -cups #net-print/cups -kerberos -ssl #app-crypt/mit-krb5 -doc #x11-libs/gdk-pixbuf -jpeg2k #media-libs/jasper -opengl #x11-libs/libXi -doc #app-text/ghostscript-gpl -djvu #net-libs/gnutls -crywrap #net-dns/libidn -java -doc #dev-java/antlr -mono #media-libs/libexif -doc #net-libs/libproxy -webkit #net-libs/glib-networking -libproxy #dev-ruby/json -doc dev-haskell/xhtml -doc #dev-ruby/mustache -doc #dev-ruby/rdiscount -doc #net-zope/zope.interface -doc # dev-python/repoze.sphinx.autointerface dev-python/oct2py -ipython #dev-python/ipython -octave #dev-python/matplotlib -doc #dev-python/ipython -matplotlib
-
x11-libs/libva
virtual/opengl
media-libs/mesa,
x11-themes/adwaita-icon-theme
gnome-base/librsvg
x11-libs/gtk+3-.14,
x11-libs/libXext
app-doc/doxygen
app-text/ghostscript,
app-doc/doxygen
media-libs/freetype
x11-libs/libXdmcp,
dev-python/setuptools
dev-python/packaging
dev-python/sphinx,
dev-ruby/rake
dev-ruby/rdoc
dev-ruby/json,
app-doc/doxygen
media-gfx/graphviz
media-libs/lasi,
media-video/ffmpeg
media-plugins/frei0r-plugins
media-libs/opencv,
media-gfx/graphviz
x11-libs/libXaw
app-text/asciidoc,
virtual/jdk
dev-java/icedtea-bin
virtual/jpeg
media-libs/libjpeg-turbo,,
x11-libs/cario
media-libs/mesa
x11-libs/vdpau
media-gfx/graphviz,
virtual/jdk
dev-java/icedtea-bin
net-print/cups
virtual/jre,
app-doc/doxygen
media-gfx/graphviz
x11-libs/cario
x11-libs/libxcb
-
dev-python/sphinx
dev-python/Babel,
app-doc/doxygen
dev-qt/qtgui
x11-proto/xextproto,
dev-lang/php-5.4
dev-db/postgres
dev-libs/ossp-uuid,
www-client/lynx
net-dns/libidn
dev-lang/mono,
net-nds/openldap
virtual/krb5
app-crypt/mit-krb5
spamassassin will not bind ipv4 localhost
in Server Help
Posted
Hello, I'm running spamassassin, I've never used it before FYI, and I can't get it to bind ipv4 to my localhost, only ipv6, I tried passing -4 in /etc/init.d/spamd but it will not go with the init scripts, though it does work by hand. I searched the initscripts, to see if it defaults to ipv6 but I don't see anything.