Jump to content
funtoo forums

ballsystemlord

Members
  • Content Count

    29
  • Joined

  • Last visited

  1. 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.
  2. 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: http://dpaste.com/0GKCMPN
  3. 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
  4. 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!
  5. 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. kernel-errors.txt
  6. 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
  7. 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. f-kmods.txt
  8. 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.
  9. 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. current.txt log-2015-06-25.txt log-2015-06-24.txt
  10. 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.
  11. Sorry about the missing code tags, I tried to add them manually. There is currently no options for smilies or anything in firefox.
  12. 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.
  13. 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.
  14. 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.
  15. 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.
×
×
  • Create New...