-
Posts
294 -
Joined
-
Last visited
-
Days Won
11
Content Type
Profiles
Forums
Blogs
Everything posted by palica
-
[SOLVED] Xorg and LxQT are not working for me: Please help this Newbie :)
palica replied to xsilentmurmurx's question in Desktop Help
can you paste emerge -pqv xorg-server xorg-drivers xf86-video-ati -
[SOLVED] Xorg and LxQT are not working for me: Please help this Newbie :)
palica replied to xsilentmurmurx's question in Desktop Help
Hi, please provide emerge --info, ego kit, ego profile, emerge -pqv @world lspci uname -a -
nm-dispatcher does not allow to boot after world update
palica replied to znavko's question in General Help
can you get to this state, please? So removing NM from xinit and adding it to default and rebooting. You are saying: "I authorize to lightdm ... " so Xorg does start even with NM enabled?- 34 replies
-
nm-dispatcher does not allow to boot after world update
palica replied to znavko's question in General Help
sorry my bad- 34 replies
-
nm-dispatcher does not allow to boot after world update
palica replied to znavko's question in General Help
ok. you have 2 laptops so one can be for testing stuff and the other one for communicating. is this correct? if yes, then stop xdm and remove all logs from /var/log/X.* /etc/init.d/xdm stop rm /var/log/X.* then disable networkmanager (it will not fix your situation, I just want to show you that it is NOT networkmanager that is responsible for lightdm not starting on your pc) rc-update delete NetworkManager then restart your pc and report back with what you see. and post /var/log/X.0.log (or any other number that is there) Thank you- 34 replies
-
efi [Canceled] Only 1/4 of installed memory with EFI-boot
palica replied to erikr's question in General Help
try using kernel and initrd from ubuntu to boot funtoo using efi and report back, please -
nm-dispatcher does not allow to boot after world update
palica replied to znavko's question in General Help
please post output of epro and ego kit please paste output of emerge -pvq @world- 34 replies
-
nm-dispatcher does not allow to boot after world update
palica replied to znavko's question in General Help
- 34 replies
-
nm-dispatcher does not allow to boot after world update
palica replied to znavko's question in General Help
how did you run lxde? did you have to start it by hand/manually or did you have a DisplayManager like GDM, LightDM, ...?- 34 replies
-
nm-dispatcher does not allow to boot after world update
palica replied to znavko's question in General Help
please post rc-status -a- 34 replies
-
nm-dispatcher does not allow to boot after world update
palica replied to znavko's question in General Help
@znavko, I have one plea to you, please don't fix your broken funtoo system using instructions found on archlinux wiki it will not work. Please post on this forum and then wait until someone replies if you want help from others and do not run some more commands and do stuff that you don't understand what it is doing, which makes stuff even worse for the people willing to help you. Please train your patience a bit. So post and wait, please. Are you running funtoo? If yes then systemd is not supported, we use openrc as our init. So anything copied from other sources will likely be false. Once again! Please! Please! Post and wait. Do NOT run any other commands that make stuff even worse or make your posts a mess. Thank you!- 34 replies
-
nm-dispatcher does not allow to boot after world update
palica replied to znavko's question in General Help
@znavko, your reports are getting better. No we know that the problem is with your graphics card or your graphics drivers as X reports no screens found. I would still like to know how your system was before running upgrade. Was it booting to graphical, did you startx manually ... this can be replaced by single command => eix-sync no need to use this as it will make dependency resolution slower you don't need to exclude all these things if there is no update to these packages portage will not rebuild them that is what emerge -u is there for. OK and now to your actual problem. nm-dispatcher is not your problem. nm-dispatcher happens to be the last think that runs from your init scripts and you think it is causing your error but it is not. Please paste your make.conf and eix -I "xf86-*" and your /var/lib/portage/world file- 34 replies
-
No problem. I have noticed some other things in your setup that you should fix. experimental is not supported anymore. I would recommend to switch to current. Manual edit is probably necessary. there is already 2.3.18 released and it makes sense to have portage the latest stable version as it is the core of funtoo/gentoo. you are using gcc-6.3.0 from your local overlay and I would recommend to switch to gcc-6.4.0 that can be found in core-kit and use that as anything else could be seen as unsupported. From all these mix-ins you need only no-emul-linux-x86 and gnome all the other ones come inherited from desktop or workstation ... and other packages that come from ::gentoo repo give me information that you need to run emerge -avuDN --newrepo @world to migrate all packages from the old ports-2012 to the new meta-repo/kits setup. Let me know if you need something else.
-
can you paste eix-update output, please? and eix elementary
-
eix eix to see what version of exi you have.
-
I cannot reproduce this. It works ok here, even with your .conf files. Paste these files or outputs please. emerge --info eix -I ego ego profile ego kit
-
[Resolved] Copying resolv.conf before chrooting
palica replied to aramisqc's question in Installation Help
If you are not going to use NetworkManager I would say yes, remove it. If you are going to use NetworkManager make a backup and replace it. -
[solved] how to make new kernel-4.14.2-1 default
palica replied to dhudson's question in General Help
You can select the "best answer", that will kind of close it :) Thanks -
[solved] how to make new kernel-4.14.2-1 default
palica replied to dhudson's question in General Help
and running boot-update afterwards. boot-update boot-update 1.8.2 / Copyright 2009-2017 Funtoo Technologies [use option "-l" for license info, "-h" for help] * Generating config for grub... Funtoo Linux - bzImage-4.9.71-ck Funtoo Linux - bzImage DEFAULT > Funtoo Linux genkernel - kernel-debian-sources-x86_64-4.14.2-1 Funtoo Linux genkernel - kernel-debian-sources-x86_64-4.14.1-1 memtest86+ * NOTE: Detected UEFI boot. Configuring for UEFI booting. * WARN: multiple matches found for default "Funtoo Linux genkernel" - most recent used. * NOTE: Intel microcode will be loaded at boot-time. * Completed successfully with warnings. -
[solved] how to make new kernel-4.14.2-1 default
palica replied to dhudson's question in General Help
changing /etc/boot.conf to this should work boot { generate grub default "Funtoo Linux genkernel" timeout 3 } "Funtoo Linux" { kernel bzImage[-v] } "Funtoo Linux genkernel" { kernel kernel-debian-sources-x86_64[-v] initrd initramfs-debian-sources-x86_64[-v] params += real_root=auto rootfstype=auto } "memtest86+" { type linux16 kernel /memtest86.bin } -
recently there has been work started on bringing 3.26 to funtoo. it is very early to switch to this unless you want to help with development.
-
[solved] how to make new kernel-4.14.2-1 default
palica replied to dhudson's question in General Help
Shoukd change it automatically after boot-update. Please send output of boot-update -
yes, please use 3.20-prime.
-
[SOLVED]Fetch failed for 'media-sound/spotify-1.0.64
palica replied to morphmex's question in Desktop Help
Bugs get resolved by Oleg at speed of light once they are in bugtracker :) -
efi [Canceled] Only 1/4 of installed memory with EFI-boot
palica replied to erikr's question in General Help
What RAM are you using? Are you overclocking? What are you settings in BIOS? Did you build the PC by yourself?
