Jump to content
Read the Funtoo Newsletter: Summer 2023 ×

palica

Members
  • Posts

    294
  • Joined

  • Last visited

  • Days Won

    11

Posts posted by palica

  1. I haven't used kvm and also didn't try this myself, but it should be possible to launch a lxd container for your needs on funtoo without booting in something else. Let me know if you are interested (I could help you setting it up), or just install centos in a separate partition, it will probably detect the Funtoo install and replace funtoo's grub with centos, but you should still be able to boot both of them.

  2. The boot flag is from ancient times, where you would indicate an MBR partition record as bootable, so you could indicate where the boot loader resided.

    On modern OS'es this is widely unused, as the MBR consists of a minimal stage loader which bootstraps either into its own partition or jumps to another area on the disk where the boot loader code is kept. (An MBR can contain either executable code or the boot partition table among other things.)

    As an example, GRUB is written into the MBR and boots whatever partition you choose.

    Did you follow the instructions and issued:

    Quote

    grub-install --target=i386-pc --no-floppy /dev/sda

    Paste the exact command that you used to install grub on your disk, please.

    I don't have bootable set on any of my disks in multiple devices and all boot fine with grub.

  3. glsa-check doesn't provide an up-to-date information for Funtoo. Funtoo also backports lots of security fixes for the forked packages, so the information that you get with --list affected could be inaccurate or wrong.

    There is a open bug for glsa-check tool for funtoo

    in BFO https://bugs.funtoo.org/browse/FL-3832?jql=text ~ "glsa"

    so you can subscribe to the bug and get update once such a tool is ready for funtoo. Until then you will have to check gentoo's GLSA list and check the README.rst in the kit of the package for example here:

    https://github.com/funtoo/core-kit/blob/1.0-prime/README.rst

    Funtoo also tries to audit forked ebuilds every 30 days. You can see all stale packages on this webpage:

    http://ports.funtoo.org/stale/

    If you want to help and use any of the packages that are listed as "stale" you can check if they are affected by any know vulnerabilities and report those on https://bugs.funtoo.org where they will be squashed as fast as possible.

    Thank you in advance.

  4. @vionpic, welcome to Funtoo community!

    We would like to help you with this error/warning message that you are receiving, but need more information from you. We would also recommend reading this post as it might give you same general help and info how to write a good question.

    Info needed:

    Firefox version

    Flash version

    NVidia/AMD driver in use - version

    on what page do you get this warning?

    And anything else that could point us in the right direction.

     

  5. so there is a difference between using emerge debian-sources with USE=binary -> that will build a kernel for you using debian scripts and almost everything will work.

    compared to using genkernel where you need to supply the right config. Best way is to save current kernel config in a file and load that in genkernel. Menuconfig, ncfongi all have a way of loading a config file.

    so what went wrong is probably that the genkernel config was not complete and didn't include graphic drivers.

     

  6. ok, znavko what do you actually want to do? Do you want to use wpa_supplicant and dhcpcd? Then lets work on this solution and not jump from wpa to NM to wicd .... It makes your posts a mess.

    Restore your system to state before your modifications. And add paste /etc/wpa_supplicant/wpa_supplicant.conf without the passphrase and replace it with xxxx.

    Remove networkmanager and add wpa_supplicant and dhcpd to default.

    Report back and tell me what the problem seems to be. Wait for my reply and do not do any modifications on your own. Do not unnecessary edit posts that you posted in the past.

     

  7. sorry I am just working step by step the stuff that could be causing your problem. and so at first I was looking at drivers if you have them emerged and also VIDEO_CARD etc. now since you didn't miss that part we are diving deeper.

    but this doesn't look that healthy :)

    2 hours ago, xsilentmurmurx said:

    [drm:radeon_pci_probe [radeon]] *ERROR* radeon kernel modesetting for R600 or later requires firmware-amd-graphics.

    you probably need to emerge sys-kernel/linux-firmware

    reboot and look in dmesg if it got fixed. report back :)

×
×
  • Create New...