dhudson
Members-
Posts
68 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Blogs
Everything posted by dhudson
-
Yes I get that, Funtoo Recommends System Rescue CD as it will boot UEFI. Also depends on Motherboard System setup.
-
looks like a warning saying it found two kernels , should be fine from boot.conf manual.... When using GRUB, boot-update will auto-enable UEFI boot configuration if it sees that your system has been booted in UEFI mode. Otherwise, MBR (legacy) boot mode will be used. I guess ubuntu booted in legacy mode.
-
wlan0: skip - SSID mismatch wlan0: No suitable network found looks like wpa_supplicant does not find the ssid you put in your config wlan0: 0: xx:xx:xx:xx:xx ssid='internet ' maybe you look close at router I see a space at end of ssid
- 20 replies
-
- wpa_supplicant
- wifi
-
(and 1 more)
Tagged with:
-
ok my last post does not work here sorry, but I did get it connected with this command as root: wpa_supplicant -Dnl80211 -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf -dd -f /var/log/wpa.log # wpa_supplicant.conf ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel update_config=1 network={ ssid="yesnotworking" scan_ssid=1 # for hidden ssid psk="supersecretpass" proto=RSN key_mgmt=WPA-PSK } notice the lack of -B which makes it run in background - better to debug in foreground docs say.
- 20 replies
-
- wpa_supplicant
- wifi
-
(and 1 more)
Tagged with:
-
maybe try this: wpa_supplicant -B -c /etc/wpa_supplicant/wpa_supplicant.conf -D nl80211 -i wlan0 replace -Dwext for -D nl80211 -dd -f /var/log/wpa.log will give you better idea of the problem
- 20 replies
-
- wpa_supplicant
- wifi
-
(and 1 more)
Tagged with:
-
yes its ok, its just a warning - because it found two genkernels same warning here too.
-
not sure what you mean here.. but running getkernel there see the "Important" where it says: Unless explicitly stated via --no-clean or --no-mrproper, Genkernel will do a make mrproper in the kernel source tree, thus cleaning a previous build and removing the previous kernel configuration file in it. meaning it will remove your configuration and clean all previous builds! as to your boot.conf the boot { } part is what you need to change default "Funtoo Linux" to default "Funtoo Linux genkernel" mount /boot and look you should see the new kernel and initramfs then your ready to run boot-update
-
that will depend on your /etc/boot.conf make sure your config looks like this boot { generate grub default "Funtoo Linux genkernel" timeout 3 } and also if you have already run emerge --depclean it will try to remove old kernels. if you want to keep your older 4.8.15 kernel around you should do emerge --ask --noreplace =sys-kernel/debian-sources-4.8.15 remember to run boot-update after any changes to boot.conf
-
emerge should of built a new kernel for you via genkernel if that is how your new kernel got there. as to config_extract i think you want amd64 which is for most multicore processors.
-
I think you already solved that but its explained well here: https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks p.s. you are correct it is not in the Funtoo install instructions. edit. well as I just did a new Funtoo install yesterday I did not remember setting the first partition bootable. and just checked my main pc its not set either,. so it must have to do with grub as jhan eluded to.
-
you can try this portageq expand_virtual / virtual/cron
-
Confusion regarding debian-sources kernel and using LVM
dhudson replied to xsilentmurmurx's question in Installation Help
hi, openrc devs seem to think it was good idea to change names of interpreter , who knows , im sure answers are out there. if you look in /etc/init.d/ open a file and look at the top line.. change runscript to openrc-run . but honestly users should not be forced into this stuff IMO. run this and you will see a list of the files needing updated.. grep '^#!/sbin/runscript' /etc/init.d/* also could be fixed with sed in one go but possible break stuff like that. ps. just thought about situations where users would have to fix this some installed packages will install run-scripts in there but its really simple enough to fix. -
[solved] how to make new kernel-4.14.2-1 default
dhudson replied to dhudson's question in General Help
yes its what I did, took reading the manual 3 times before I saw it, should look closer ah? thanks for replying, jhan, palica problem solved! -
[solved] how to make new kernel-4.14.2-1 default
dhudson replied to dhudson's question in General Help
Your very correct, found it in boot.conf manual If multiple "Funtoo Linux" boot entries are created, the one that has the most recently created kernel (by file mtime) will be booted by default. Note that double-quotes are optional both in section names and in the boot/default value. Added the genkernel to default it worked fine. thanks for pointing that out, I missed it . -
[solved] how to make new kernel-4.14.2-1 default
dhudson replied to dhudson's question in General Help
# 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... DEFAULT > Funtoo Linux genkernel - kernel-debian-sources-x86_64-4.8.15-1 Funtoo Linux genkernel - kernel-debian-sources-x86_64-4.14.2-1 memtest86+ * NOTE: Detected MBR boot. Configuring for Legacy MBR booting. * WARN: No boot/default match found - using first boot entry by default. * Completed successfully with warnings. I would of thought so too but its not the case, thanks -
after reading the docs its not clear to me what it is i need to change in /etc/boot.conf , which is unchanged I think. the old 4.8.15-1 is default at this point would like to have new one. i just want to keep the old kernel around a while just in case. $ cat /etc/boot.conf boot { generate grub default "Funtoo Linux" timeout 3 } "Funtoo Linux" { kernel bzImage[-v] } "Funtoo Linux genkernel" { kernel kernel[-v] initrd initramfs[-v] params += real_root=auto rootfstype=auto } "memtest86+" { type linux16 kernel /memtest86.bin } -rw-r--r-- 1 root root 3.2M Dec 27 17:41 System.map-debian-sources-x86_64-4.14.2-1 -rw-r--r-- 1 root root 3.3M Dec 24 2016 System.map-debian-sources-x86_64-4.8.15-1 -rw-r--r-- 1 root root 8.8M Dec 27 19:22 initramfs-debian-sources-x86_64-4.14.2-1 -rw-r--r-- 1 root root 7.8M Dec 24 2016 initramfs-debian-sources-x86_64-4.8.15-1 -rw-r--r-- 1 root root 4.8M Dec 27 17:41 kernel-debian-sources-x86_64-4.14.2-1 -rw-r--r-- 1 root root 4.2M Dec 24 2016 kernel-debian-sources-x86_64-4.8.15-1 -rw-r--r-- 1 root root 147K Sep 15 07:54 memtest86.bin any help appreciated, thanks
-
[Solved] revdep-rebuild fails with UnicodeDecodeError
dhudson replied to McQ's question in General Help
maybe not relevant but a lang=c set somewhere will cause python to break, or even LC_ALL=c but you show its unset in your locale. python, from what I have found wants utf-8 everywhere. -
just to update this matter, turns out I had put LC_ALL=C IIRC .bashrc or .Xdefaults or somewhere ? once removed it all went away. No idea why it matters, or why or what I was trying to do.
-
thanks for the reply, I thought it strange my laptop runs the query module fine and also note that the query origin works fine, but im still investigating this unicode error i noticed a warning or notice during the conky update this morning something related to U+xxx stuff but cant find it in my emerge logs. in fact I have no emerge log for today. HA!
-
that's interesting...didn't know that.. complains about 0xb4 which is the unicode character for the backtick. I guess I need to update python thanks.
-
I Know this worked a few weeks ago but now I get error when i do, ~$ ego query versions ego Traceback (most recent call last): File "/usr/bin/ego", line 102, in <module> EgoModule.run_ego_module(action, econfig, args, VERSION) File "/usr/share/ego/python/ego/module.py", line 64, in run_ego_module ego_module(*args) File "/usr/share/ego/python/ego/module.py", line 49, in __call__ self.handle(**options) File "/usr/share/ego/modules/query.ego", line 41, in handle handler(**options) File "/usr/share/ego/modules/query.ego", line 56, in handle_versions_subcommand slot = ebuild.vars.get('SLOT', '0') File "/usr/lib64/python3.4/site-packages/appi/ebuild.py", line 122, in vars self._parse_ebuild_file() File "/usr/lib64/python3.4/site-packages/appi/ebuild.py", line 180, in _parse_ebuild_file make_conf = Profile.get_system_make_conf() File "/usr/lib64/python3.4/site-packages/appi/conf/profile.py", line 136, in get_system_make_conf context = Profile._parse_make_conf_file(path, context) File "/usr/lib64/python3.4/site-packages/appi/conf/profile.py", line 117, in _parse_make_conf_file r'^\s*(?:export\s+)?([a-z][a-z0-9_]*)=', f.read(), re.M | re.I File "/usr/lib/python-exec/python3.4/../../../lib64/python3.4/encodings/ascii.py", line 26, in decode return codecs.ascii_decode(input, self.errors)[0] UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2220: ordinal not in range(128) here is ego vers. ~$ eix ego [I] app-admin/ego Available versions: 2.0.9^m **2.0.10^m 2.0.14^m **2.1.1^m 2.2.0^m 2.2.1^m 2.3.1^m **2.3.2^m **9999^m {zsh-completion PYTHON_SINGLE_TARGET="python3_4 python3_5 python3_6" PYTHON_TARGETS="python3_4 python3_5 python3_6"} Installed versions: 2.3.1^m(11:54:30 11/08/17)(-zsh-completion PYTHON_SINGLE_TARGET="python3_4 -python3_5 -python3_6" PYTHON_TARGETS="python3_4 -python3_5 -python3_6") Homepage: http://www.funtoo.org/Package:Ego Description: Funtoo's configuration tool: ego, epro, edoc. also ego kit list does work so maybe the query part I am doing wrong or was removed. no other issues with funtoo ego --sync and eix ect all work. if I need to supply other info let me know.. thanks
-
oh your right I got that wrong... sorry but you should have a dir /etc/portage/make.profile with a file called parent I belive make.profile was a file before the change. here is mine.. change your subaarch to reflect your hardware. ~$ cat /etc/portage/make.profile/parent core-kit:funtoo/1.0/linux-gnu/arch/x86-64bit core-kit:funtoo/1.0/linux-gnu/build/current core-kit:funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/amd64-piledriver core-kit:funtoo/1.0/linux-gnu/flavor/workstation core-kit:funtoo/1.0/linux-gnu/mix-ins/no-systemd core-kit:funtoo/1.0/linux-gnu/mix-ins/mediadevice-audio-pro xfce-kit:funtoo/kits/python-kit/3.4-prime net-kit:funtoo/kits/python-kit/3.4-prime python-kit:funtoo/kits/python-kit/3.4-prime core-hw-kit:funtoo/kits/python-kit/3.4-prime ruby-kit:funtoo/kits/python-kit/3.4-prime gnome-kit:funtoo/kits/python-kit/3.4-prime security-kit:funtoo/kits/python-kit/3.4-prime ml-lang-kit:funtoo/kits/python-kit/3.4-prime xorg-kit:funtoo/kits/python-kit/3.4-prime text-kit:funtoo/kits/python-kit/3.4-prime lisp-scheme-kit:funtoo/kits/python-kit/3.4-prime java-kit:funtoo/kits/python-kit/3.4-prime perl-kit:funtoo/kits/python-kit/3.4-prime games-kit:funtoo/kits/python-kit/3.4-prime desktop-kit:funtoo/kits/python-kit/3.4-prime haskell-kit:funtoo/kits/python-kit/3.4-prime php-kit:funtoo/kits/python-kit/3.4-prime lang-kit:funtoo/kits/python-kit/3.4-prime nokit:funtoo/kits/python-kit/3.4-prime science-kit:funtoo/kits/python-kit/3.4-prime editors-kit:funtoo/kits/python-kit/3.4-prime core-kit:funtoo/kits/python-kit/3.4-prime kde-kit:funtoo/kits/python-kit/3.4-prime media-kit:funtoo/kits/python-kit/3.4-prime dev-kit:funtoo/kits/python-kit/3.4-prime
-
https://github.com/funtoo/meta-repo#using-meta-repo tells to rm /usr/share/portage/config/repos.conf also says same on README.rst page. so looks like you no longer need that lnk to /usr/portage...ect
-
apologizes Sandro , was not meaning to step on your toes ...
-
https://www.funtoo.org/Funtoo_Linux_Localization talk about Azerty keymap... only thing I could find for Xorg is gentoo fourms this: To change the keymap on your console you should change the keymap var in your /etc/conf.d/keymaps: Code: keymap="fr" To change it in X, you can add the setting in your xorg.conf in the keyboard section: Section "InputClass" Identifier "keyboard-layout" MatchIsKeyboard "on" Option "XkbLayout" "fr" ... EndSection
