Jump to content
funtoo forums

jhan

Members
  • Content Count

    268
  • Joined

  • Last visited

  • Days Won

    15

Everything posted by jhan

  1. Please report a bug at https://bugs.funtoo.org for that
  2. The log file looks ok but is this the log file from the failing startx? And what happens when you use startx? What are the error symptoms? What is not working?
  3. jhan

    r8168 ebuild outdated?

    Why don't you follow the link in the message? Going to the page mentioned, scrolling down to Unix, clicking on the download button before the mentioned link, enter email address and click on "Download File". Answer captcha and you get the file.
  4. The log file does not look too bad. What is the result of startx? I see that you have nomodeset in your kernel command line. Can you remove that from /etc/boot.conf and re-run ego boot update, then reboot. Maybe that will help. You also might need to give the desired screen size if the system can't detect the right one.
  5. As far as I know, the fbcon error can be ignored. The above message is the problem. What graphics card do you have? What setup do you want to achieve? I get the same error when I run 'X -configure' (which I haven't in ages) on my computer with an intel/nvidia combo. And my guess would be that the command can't handle this, like it says in the man file: -configure When this option is specified, the Xorg server loads all video driver modules, probes for available hardware, and writes out an initial xorg.conf(5) file based on what was detected. This option currently has some problems on some platforms, but in most cases it is a good way to bootstrap the configuration process. This option is only available when the server is run as root (i.e, with real-uid 0). Does just using 'startx' give you a working server? You could probably also use an old xorg.conf if you want and modify it to your needs. It is always better to have at least a working configuration (automatically with startx or manually) to fall back on and work on from there.
  6. That seems to be a warning about the different python versions for those two packages. Currently numpy-1.17.0_rc1 accepts python 3.5, 2.6 and 3.7 while inkscape-0.92.4 just python 2.7 Looks like bug report FL-6568 to me.
  7. It seems to be a similar case as bug FL-6628 That would mean that you need to emerge dev-libs/gobject-introspection and then the problem should be solved. If you could verify that it would be good if you could also open a bug report at bugs.funtoo.org so that the problem can be fixed.
  8. What are the permissions of the directories above? Do you have enough free space available (in all partitions)? Any error messages, e.g. in dmesg? Can you read the contents of the file? An OSError can be a lot of things. Unless you can find more information, there isn't much to say.
  9. For running kde with wayland without xorg there still seem to be a few showstoppers but I think kwin does help with getting started. Gnome should be also on the way, at least according to their roadmap but you can also find more information there, including information for using android drivers. Generally my information is that the usability of wayland without xorg still depends on the applications you want to use and their support for wayland. Looking at the packages on gentoo that support wayland, the list is not that big yet. There are also some cases where wayland still causes problems, see Link1 and link2 I was looking at trying out wayland as well but it seems to be now quite where I would be willing to do that. At least not for my main computer.
  10. Look at the output of 'epro' arch should be set there. See https://www.funtoo.org/Install/Profiles and https://www.funtoo.org/Funtoo_Profiles for more details.
  11. That is the important part. Making the suggested changes could solve the problem. You can either do this manually, by adding the USE flags to /etc/portage/package.use or by choosing the appropiate mix-in for your graphics card. Available mix-ins can be shown with 'epro list'.
  12. I would either remove the old version or rename it, so that it fits into the new versioning scheme. If I see that correctly, it seems to me that the new scheme is something like <main version>.<year>.<yearly release number> With 8046 the 12th release for 2016 that would be 1.2016.12 or 0.2016.12 in the new scheme, depending on the real meaning of the first digit. Packages that may depend on plantuml may need to be looked at but that has to be done anyhow, to make sure that the new scheme doesn't lead to problems.
  13. Well, you know how it is with software that has dependencies, sometimes some of the dependencies can be forgotten. It is called making an error. And that is also the reason why there is the pull request for some time, to deliver the missing dependency. The reason why the pull request is not accepted yet, is that all newer versions of lua >dev-lang/lua-5.1.5-r4 are slotted on gentoo, as can be seen at https://packages.gentoo.org/packages/dev-lang/lua That might not be a problem for you or me but @drobbins doesn't like it and would prefer it "unslotted". That is his right, as it is his project. If you don't like this situation you can either convince him otherwise, so that the PR will be accepted. Or, better, "unslot" the new lua version and submit your on pull request. The open bug report for the update of conky can be found at https://bugs.funtoo.org/browse/FL-6457
  14. https://bugs.funtoo.org/browse/FL-6463
  15. Because you probably had a reason to choose one profile over another. And looking at the difference between those two mix-ins, I would say that the amdgpu mix-in seems to be more fitting to your make.conf settings (VIDEO_CARDS="gallium-r600 swrast r600 radeon"): farout ~ # more /var/git/meta-repo/kits/core-kit/profiles/funtoo/1.0/linux-gnu/mix-ins/gfxcard-older-ati/* /var/git/meta-repo/kits/core-kit/profiles/funtoo/1.0/linux-gnu/mix-ins/gfxcard-amdgpu/* :::::::::::::: /var/git/meta-repo/kits/core-kit/profiles/funtoo/1.0/linux-gnu/mix-ins/gfxcard-older-ati/make.defaults :::::::::::::: VIDEO_CARDS="radeon r100 r200" USE="vdpau" (Next file: /var/git/meta-repo/kits/core-kit/profiles/funtoo/1.0/linux-gnu/mix-ins/gfxcard-amdgpu :::::::::::::: /var/git/meta-repo/kits/core-kit/profiles/funtoo/1.0/linux-gnu/mix-ins/gfxcard-amdgpu/make.defaults :::::::::::::: VIDEO_CARDS="amdgpu radeon gallium-r300 gallium-r600 gallium-radeonsi" USE="xa xvmc vaapi vdpau" farout ~ #
  16. Are you sure that the mix-in gfxcard-older-ati applies for your card and not gfxcard-amdgpu? I'm not familar with the AMD/ATI cards but I think that the HD6450 is a bit younger than a R100 or R200 mentioned at https://www.funtoo.org/Make.conf/VIDEO_CARDS/Mix-ins
  17. That probably depends on the terminal you are using. For xterm the colors and other visual settings used are stored in ~/.Xdefaults
  18. Maybe you should add not only pt but the correct name of the keymap as well. Looking at the available pt keymaps: sicota@farout /data/incoming $ find /usr/share/keymaps/ -name "*pt*" /usr/share/keymaps/i386/olpc/pt-olpc.map.gz /usr/share/keymaps/i386/qwerty/pt-latin9.map.gz /usr/share/keymaps/i386/qwerty/pt-latin1.map.gz /usr/share/keymaps/mac/all/mac-pt-latin1.map.gz sicota@farout /data/incoming $ I would suggest to use something like pt-latin1 instead of pt.
  19. Do you mean the testing or the upgrade process? As far as I know some parts are tested automatically but you can't test everything as one would need all possible hard- and software configurations to do that.
  20. You can follow the instructions at https://www.funtoo.org/Upgrade_Instructions/1.4-release and report any problems in IRC or bugs.funtoo.org (if they are not already there).
  21. It works but you might have misunderstood me. The problem is that you don't have virtual/mysql and dev-db/mysql yet. Your tree should look like: /opt my-overlay dev-db mysql Manifest metadata.xml mysql-8.0.16.ebuild metadata layout.conf profiles repo_name virtual mysql Manifest metadata.xml mysql-... As @cardinal also said, you need the category level as well, otherwise it won't work. The structure in general is always: overlay_root category1 package1 package2 package3 category2 package1 package2 package3 . . .
  22. You need to add the category as well: virtual/mysql => /opt/my-overlay/virtual/mysql dev-db/mysql => /opt/my-overlay/dev-db/mysql
  23. jhan

    Kicad emerge failed

    It seems that this is a problem between kicad and glm which seems to be fixed in later versions of both packages. The nearly released funtoo 1.4 provides upgrades of media-libs/glm to 0.9.9.5 and kicad to 5.1.2
  24. You can always try a complete new installation with 1.4, even if it is still in beta. But there are already stage3 images available: https://build.funtoo.org/1.4-release-std/x86-64bit/ But make sure to make backups before doing any major update. And if you are talking about this steam solution: you should probably be able to test that out with funtoo 1.2 as well, as it uses lxd to do that.
  25. The problem is that the newer conky versions require lua version 5.3 There is an open pull request (https://bugs.funtoo.org/browse/FL-6463) to add lua 5.3 to funtoo. To solve the problem you can either mask the newest conky version or install lua 5.3 in a local overlay until lua 5.3 makes it into funtoo.
×
×
  • Create New...