Re: [gentoo-user] Re: [~amd64] Keyboard stops working several times/day
Le 17/08/15 à 21:13, Michel Catudal a tapoté : drivers/char/sunxi_mem/sunxi_physmem.c:22:27: erreur fatale: mach/includes.h : Aucun fichier ou dossier de ce type I guess you should disable CONFIG_SUNXI_PHYS_MEM_ALLOCATOR since anyway, this option is not available into official linux-sunxi-3.4.103, it has been added by one armbian patch, and this driver seems broken for your platform.
Re: [gentoo-user] martian source with unknown IP and MAC
On Aug 17, 2015, at 20:46, Grant emailgr...@gmail.com wrote: I received a suspicious prompt while browsing a financial account of mine on my laptop so I restarted my modem but did not DHCP to it. I immediately received a series of type 08 00 martian sources logged to dmesg on my laptop from a 10.x.x.x source while my local network runs on 192.168.x.x only, and the logged MAC address does not match that of any systems on my LAN including the modem and I don't run wifi. Is that martian source suspicious? Use tcpdump to study your traffic. My ISP runs their DHCP server in 10.x.x.x space so my firewalls dmesg is full on martian source warnings because the DHCP traffic in the network. My firewall has a public ip and in that public network the DHCP server runs in 10.x.x.x. -- -Matti
Re: [gentoo-user] Re: [~amd64] Keyboard stops working several times/day
Am 18.08.2015 um 04:04 schrieb walt: I see the keyboard problem in mate and xfce4 (the only ones I use now). I've wondered about the same things but I don't know how to debug those possible scenarios. And which terminal emulator are you using? At the moment I'm waiting for my new keyboard to arrive from amazon, hoping to pin the blame on flakey hardware instead of flakey software. Somehow I doubt that it's the keyboard. I rather guess it's either a wrong configuration of or a bug in the desktop environment, the terminal emulator and/or systemd/udev.
Re: [gentoo-user] how to get a couple of -9999 packages to behave
/usr/lib64/pkgconfig/atk-bridge.2.0.pc is part of at-spi2-atk which comes as a dependency of gtk+[X]. So you need at-spi2-atk[abi_x86_32] which should be pulled in by gtk+[abi_x86_32]. emerge @preserved-rebuild, make sure all flag changes are applied (emerge --changed-use --deep @world) and then try again. It could be that this is a recent change to packages you want (at-spi2-core/at-spi2-atk), they are live ebuilds after all, so you may need to report to the gnome overlay maintainers.
Re: [gentoo-user] how to get a couple of -9999 packages to behave
Jeremi Piotrowski jeremi.piotrow...@gmail.com wrote: /usr/lib64/pkgconfig/atk-bridge.2.0.pc is part of at-spi2-atk which comes as a dependency of gtk+[X]. So you need at-spi2-atk[abi_x86_32] which should be pulled in by gtk+[abi_x86_32]. emerge @preserved-rebuild, make sure all flag changes are applied (emerge --changed-use --deep @world) and then try again. It could be that this is a recent change to packages you want (at-spi2-core/at-spi2-atk), they are live ebuilds after all, so you may need to report to the gnome overlay maintainers. OK, I have the following in /etc/portage/package.use app-accessibility/at-spi2-atk abi_x86_32 app-accessibility/at-spi2-core abi_x86_32 But the 999 versions are not giving the /usr/lib32 items including /usr/lib32/pkgconfig/atspi-2.pc and this seems to be the problem -- how can I fix, or how can I do the same thing outside of tree i.e. get both the /usr/lib64 and /usr/lib32 items like the one mentioned above. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] how to get a couple of -9999 packages to behave
On Tue, 18 Aug 2015, cov...@ccs.covici.com wrote: OK, I have the following in /etc/portage/package.use app-accessibility/at-spi2-atk abi_x86_32 app-accessibility/at-spi2-core abi_x86_32 Can you verify that these are being picked up properly by running emerge -av at-spi2-atk at-spi2-core Should show you the active use flags and hopefully abi_x86_32 will be among them. Additionally I'm going to go out on a limb here and ask: are you using a multilib profile? But the 999 versions are not giving the /usr/lib32 items including /usr/lib32/pkgconfig/atspi-2.pc and this seems to be the problem The gnome-overlay ebuilds do not differ too much from the main tree ebuilds and those are multlib friendly so the live ones should be too. -- how can I fix, or how can I do the same thing outside of tree i.e. get both the /usr/lib64 and /usr/lib32 items like the one mentioned above. Multilib ebuilds basically copy the sources into two folders and run different configure commands in them. Something like CFLAGS=-m32 CXXFLAGS=-m32 LDFLAGS=-m32 ./configure --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --prefix=/usr/local --libdir=/usr/local/lib32 should build the 32 bit variant properly. You will also be able to use everything straight away since /usr/local/include is on the default preprocessor search path and /usr/local/lib32 (should) be in /etc/ld.so.conf by default. But I don't think it is likely an ebuild problem here, this kind of thing would be quickly caught.
[gentoo-user] !!!!
Like a stupid dumbfuck, I tried to update my machine today tortoise ~ # revdep-rebuild /bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory tortoise ~ # ufed sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory Couldn't determine EPREFIX and PORTDIR from Portage INIT failed--call queue aborted. tortoise ~ # GOOD JOB, PENGUINS!!! I won't even be able to reboot my machine!!! A+ configuration management -- IQ is a measure of how stupid you feel. Powers are not rights.
Re: [gentoo-user] !!!!
What did you update? Nothing I remember recently came out to break like this. On Tue, Aug 18, 2015 at 2:52 PM, Alan Grimes alonz...@verizon.net wrote: Like a stupid dumbfuck, I tried to update my machine today tortoise ~ # revdep-rebuild /bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory tortoise ~ # ufed sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory Couldn't determine EPREFIX and PORTDIR from Portage INIT failed--call queue aborted. tortoise ~ # GOOD JOB, PENGUINS!!! I won't even be able to reboot my machine!!! A+ configuration management -- IQ is a measure of how stupid you feel. Powers are not rights.
Re: [gentoo-user] Re: Install PreQualifying Matrix
James wrote: Dale rdalek1967 at gmail.com writes: James wrote: What I really would appreciate is some feedback on the Planning Questions listed below, as to help folks organized their thoughts and hardware details BEFORE actually performing an install or test-drive. Many/most of these options exist Install PreQualifying Matrx::QUESTIONS Live Testdrive options before installation(usb/cd/dvd):: Intended Usage (workstation/server/device/) Hardware or Vitual installation:: PC mobo or tablet/embedded/device:: Processor/Ram characteristics:: MBR vs (u)EFI (type of mobo):: Single or Multi or RAID disk configuration:: OpenRC or Systemd:: Grub1 vs Grub2 or other boot-semantics:: File System type(s):: Hope other will also share and help give you ideas. Dale Hello Dale, Acutally answering the question, with comments is a good idea. But what I had in mind, that is much more pressing is a list of additional questions, or re-ordering the questions or re-stating the quesions or matrix logic on the causal relationships between these quesions and other questions as to conclusion of valid install options is more of what I had in mind. Once that is reasoably vetted then I would look for some statisical inferences on the actual answers to these quetions as well as valid install links like sabayon for gentoo(ish) systemd like calculate-linus for gentoo(ish)openrc like pentoo for gentoo-penetration systems like zentoo for gentoo CI systems Like funtoo as an option install like gentooliveUSB for a gentoo + persistence experience. I think this sort of approach will take some stress off of the gentoo-user list and handbook whilst Blueness brings maturity to his efforts; he alreayd has lilblue, tinhat and tor-ramdisk gentoo installs, so he is one of those guys that can single-handedly solve this crisis: should he put his fingers to the task. MaffBlaster has been very quite of late. Blueness is a wonderful and collegial type of dev and is currently seeking input on his 'alpha' ideas:: https://wiki.gentoo.org/wiki/Project:RelEng_GRS THANKS! James So this is to create a installer then? Someone built a installer a long time ago and it didn't work well. Heck, I never could get the thing to even complete the install and that was IF it would boot at all to even start the process. It would hang somewhere and then sit there doing nothing. After that, I found a installer to be useless and a waste of time. I wasn't alone on that point either. Not long after that, the installer project died. The current handbook, it works. This is the issue as I see it. A few people want a installer to make Gentoo easier to install. Well, why? After you install Gentoo, you have to update, maintain and maybe repair that install. A installer isn't going to do that unless you wait for a new version of the installer and re-install/update sort of like windoze does. Basically, you are going to need what is learned during the install to maintain/repair your system and that is just the start of it. It's that simple. Another issue with having a installer. People install Gentoo with the installer, if it works, and are basically completely clueless about Gentoo and the effort it takes to run it. I'd be surprised if even a small percentage that used the last installer are still using Gentoo. People use the installer, find out that Gentoo isn't a point n click distro, get pissed because they actually have to work at it and then they switch to something else. Does that benefit Gentoo? Not likely. Gentoo can be a pain and most people don't want that because they don't want to put any real effort into their OS. When I install Linux for someone else, I put some sort of Ubuntu or something that they can handle. Putting Gentoo on a system and expecting them to handle updates would be . . . well . . . silly. It would be a setup for failure. If someone wanted to run Gentoo on their puter, I'd sit with them while they went through the install, with them doing the work and learning. Before I first installed Gentoo way back in 2003, I did my research. I researched my hardware, all sorts of options and read the handbook several times. It took me a few tries to get it right but I did. I don't recall asking anyone for help during that install process. I just followed the handbook and learned from the few mistakes I made. Later on, I learned how to customize things to suite my needs. When I built my new rig a few years ago, I sat down, figured out what I wanted to use and adjusted the install process to suite that. That effort was on me not someone else. If I want to use LVM, RAID, BTRFS or something else that isn't included in the default install handbook, it's on me to figure out where to insert that part of my install. When a person has used Linux for a while, they tend to learn
Re: [gentoo-user] Re: !!!!
Grant Edwards wrote: On 2015-08-18, Dale rdalek1...@gmail.com wrote: Alan Grimes wrote: tortoise ~ # revdep-rebuild /bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory [...] Did you update ncurses by any chance? According to a look up, that file belongs to that package. I might also add, I don't have that file here at all. Sort of odd that I don't have it but portage works fine here. I don't have any libtinfo.whatever on any of my systems either. By default, I don't think a separate libtinfo is built. One suggestion I saw for this problem (on a different distro) is to symlink libtinfo to libncurses. I did a google search, I got three or four hits. That sort of makes me think that there is a bad setting somewhere. Since no one else has posted about this, I doubt a dev did it because if they did, I'd think others would be hitting this problem too. Maybe we will get some replies from the OP soon. Dale :-) :-)
Re: [gentoo-user] !!!!
Alan Grimes wrote: Like a stupid dumbfuck, I tried to update my machine today tortoise ~ # revdep-rebuild /bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory tortoise ~ # ufed sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory Couldn't determine EPREFIX and PORTDIR from Portage INIT failed--call queue aborted. tortoise ~ # GOOD JOB, PENGUINS!!! I won't even be able to reboot my machine!!! A+ configuration management Did you update ncurses by any chance? According to a look up, that file belongs to that package. I might also add, I don't have that file here at all. Sort of odd that I don't have it but portage works fine here. Dale :-) :-)
Re: [gentoo-user] !!!!
Meik Frischke wrote: 2015-08-18 22:40 GMT+02:00 Dale rdalek1...@gmail.com mailto:rdalek1...@gmail.com: Alan Grimes wrote: Like a stupid dumbfuck, I tried to update my machine today tortoise ~ # revdep-rebuild /bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory tortoise ~ # ufed sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory Couldn't determine EPREFIX and PORTDIR from Portage INIT failed--call queue aborted. tortoise ~ # GOOD JOB, PENGUINS!!! I won't even be able to reboot my machine!!! A+ configuration management Did you update ncurses by any chance? According to a look up, that file belongs to that package. I might also add, I don't have that file here at all. Sort of odd that I don't have it but portage works fine here. Dale :-) :-) Seems like ncurses was recompiled without the tinfo use flag. You could try booting up a rescue system and unpack a precompiled bash package from another (trusted) system to get your machine working again and continue from there. That would make sense. Just a FYI tho, I don't have that USE flag enabled here either. [ebuild R] sys-libs/ncurses-5.9-r3:5::gentoo USE=gpm unicode -ada -cxx -debug -doc -minimal -profile -static-libs -tinfo -trace ABI_X86=32 (64) (-x32) 0 KiB This may be one of those times where having the binaries for older packages would come in handy. Just find it, untar it and then fix it so that it works right. Dale :-) :-)
[gentoo-user] Re: !!!!
On 2015-08-18, Dale rdalek1...@gmail.com wrote: Alan Grimes wrote: tortoise ~ # revdep-rebuild /bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory [...] Did you update ncurses by any chance? According to a look up, that file belongs to that package. I might also add, I don't have that file here at all. Sort of odd that I don't have it but portage works fine here. I don't have any libtinfo.whatever on any of my systems either. By default, I don't think a separate libtinfo is built. One suggestion I saw for this problem (on a different distro) is to symlink libtinfo to libncurses. -- Grant Edwards grant.b.edwardsYow! Edwin Meese made me at wear CORDOVANS!! gmail.com
Re: [gentoo-user] Re: !!!!
On Tue, 18 Aug 2015, Dale wrote: Grant Edwards wrote: On 2015-08-18, Dale rdalek1...@gmail.com wrote: I don't have any libtinfo.whatever on any of my systems either. By default, I don't think a separate libtinfo is built. One suggestion I saw for this problem (on a different distro) is to symlink libtinfo to libncurses. Ncurses can be compiled as a single library or as two (ncurses + tinfo), in either case all the symbols are present on the system it's just a question of where they are located. Many packages are not prepared to handle the seperate tinfo library, we have many bugs in the bugzilla that deal with tracking down such build failures and correcting them. But this is the first I hear of anyone having a problem with the reverse. Symlinking libtinfo to libncurses *should* work, or atleast seems like a valid rescue attempt. Maybe we will get some replies from the OP soon. Would help, I too don't recall any serious updates lately.
Re: [gentoo-user] Re: installation failure
On 18/08/15 02:58, »Q« wrote: On Mon, 17 Aug 2015 20:46:44 +0200 Alan McKinnon alan.mckin...@gmail.com wrote: Er, no. You don't. You really, really REALLY don't want to go Stage 1 :-) My second install was a stage 1, way back in the day when the stage 3s weren't fully usable out of the box yet. My first was a stage 2 (fully documented back then) and for the second one I decided to be brave. I did learn something, but it really wasn't worth the effort. For my second or third install I also used a stage 2, and I completely agree with you. sort of ... conditions were different in the beginning a stage 1 was all there was. We used to sneer at those too soft to do it hard core :) When viable stage 3's became available, the handbook gradually moved to recommending a stage 3 then mandating it. In about 2000/2001 when I first started with gentoo (on a 486, moved from Redhat 4.0 from memory, took a whole week to download the sources via dialup, and 2 days to build the basic stage 3). The problem was that the build process was full of holes - there is a reason modern portage/emerge is as complicated as it is. A full stage one was consistent. After a few months of use inconsistencies would creep in and an emerge world -e became necessary to restore smooth functioning. Have not had to do that for a couple of years now ... don't miss it :) BillK
Re: [gentoo-user] Re: [WAS: keyboard stops working] Recent kernels block the loading of non-GPL kernel modules
On 08/18/2015 09:54 PM, Rich Freeman wrote: I think the kernel devs would be hard-pressed to mount some kind of GPL infringement lawsuit. In general US courts have tended to block attempts to use copyright/trademark/patents/etc simply to prevent interoperability, and that is basically what this is. The entire point of the GPL is to prevent interoperability with people who want to steal your work and take away its users' freedoms. And would we really want it any other way? How is this not like Brother sticking chips in their ink cartridges containing copyrighted code, or the chip in lightning cables? They are similar. The original GPL was a legal hack: to take copyright and use it in a novel way, granting freedoms rather than restricting them. Which coincidentally is how your example differs from EXPORT_SYMBOL_GPL =)
Re: [gentoo-user] Re: !!!!
On 08/18/2015 06:38 PM, walt wrote: On Tue, 18 Aug 2015 18:03:31 -0700 John Campbell jdc@cox.net wrote: I haven't really been following this closely but I haven't seen any suggestion to use emerge -1 --quiet=y smart-live-rebuild to remove the offending curses output. Hopefully emerge doesn't check/use curses unless it's producing actual output. A very obscure hint, and I like it :) I have no trouble emerging packages (at the moment) so I emerged app-portage/smart-live-rebuild, which dragged in eselect-package-manager as a dependency. 'eselect package-manager list' shows only portage as installed, even though I now also have porthole and smart-live-rebuild installed too. Do you see something different? I only have portage as a manager. You probably have to re-emerge porthole to get it to show up. Your problem seems to be a portage/ncurses mismatch. Once you fix that you should be able to at least see the output from your initial smart-live-rebuild Whenever I have a problem with python throwing out library mismatch errors I look to emerge everything from the program to the library. Something along the way has probably lost it's library... And as python's an interpreted language revdep-rebuild won't find it. Do you get different output from emerge @smart-live-rebuild than from smart-live-rebuild? I personally don't use the smart-live-rebuild script but instead rely on the emerge @smart-live-rebuild set. But that's just my preference and really shouldn't make any difference. How about emerge --color=n --nospinner -p @smart-live-rebuild Color and spinners are the only things in portage that should be using curses. Maybe emerge --quiet=y -a @smart-live-rebuild
Re: [gentoo-user] Re: [WAS: keyboard stops working] Recent kernels block the loading of non-GPL kernel modules
On 08/18/2015 08:39 PM, Dale wrote: Here's a clue. Why doesn't the kernel devs let users decide what drivers they are comfy with using? If they don't like the drivers, then make it so that users have to install their own just like we have for ages but don't disable them or make them not load and work. A lot of people build and distribute kernels. The EXPORT_SYMBOL_GPL thing is there to prevent those people from linking closed-source modules against certain parts of the kernel, because the result would not be distributable under the GPL. The legal issue is there regardless: you can't link closed-source stuff to GPL code and then distribute the result.
Re: [gentoo-user] Re: [WAS: keyboard stops working] Recent kernels block the loading of non-GPL kernel modules
walt wrote: entire post severely snipped for brevity On Mon, 17 Aug 2015 00:53:37 -0500 Dale rdalek1...@gmail.com wrote: walt wrote: Linus and friends have been marking lots of existing kernel symbols with the SYMBOL_EXPORT_GPL macro, which was designed to block the loading of any kernel module not explicitly licensed as GPL software. The only module I have is Nvidia but that is one thing that doesn't work at times. Sometimes, it doesn't want to boot all the way. It doesn't even get through the kernel loading everything up at times. The Nvidia module is causing your problem then, because Nvidia supplies their binary blob under their own proprietary license. I'm using an elderly version of x11-drivers/nvidia-drivers on an elderly machine, but when I run 'modinfo -l nvidia' I see 'NVIDIA' as the response. If the response isn't 'GPL' then the affected kernels will refuse to load the module at boot time. The kernel devs have provided a workaround for the problem, however: You (or a gentoo dev) need to edit the source code for the problem kernel by changing the SYMBOL_EXPORT_GPL to SYMBOL_EXPORT. That macro appears maybe hundreds of places in the kernel sources, and has been there for years now, but only one or two of those source files needs to be patched, depending on which of those exported symbols is needed by your particular binary driver (e.g. nvidia-drivers or ati-drivers). This whole GPL/module thing is far from new. What's new is that the kernel devs are slowly adding more kernel symbols to their black list. I think the idea is to turn up the pressure very slowly on companies like Nividia and ATI to discourage them from providing proprietary drivers while not driving them out of the linux market completely. Every year linux is getting stronger and the devs can afford to be pushier with wealthy corporations who need more linux customers. I think there is two issues but you are addressing one of them it seems. The other issue happens when the kernel panics and it reboots itself. It doesn't complete the boot process. The one you describe could be it tho. On that one, I don't have a GUI. Since I use my puter a lot, I usually just reboot to a known working kernel and deal with it later. While I think I get the idea of what the kernel devs are doing. I also think they should let the users send the message. The users can start buying ATI or other video hardware and at some point, they will either get their ducks in a row or lose sales. In the meantime, the users decide what software they want to use. I did some searching based on the config option you gave and I'm unable to find a way to override this myself. It doesn't seem to be a setting I can put in make.conf or package.use etc either. If this is the case, I may wish Nvidia would switch to open source but it sort of rubs me the wrong way that someone else is making the decision and me having no way to exercise my decision to use it anyway. I don't care if Nvidia doesn't show its code as long as it works and it isn't spying on me or blowing up my house here. If you have any info on how to override this, I'd be glad to see it. Just a link or something would help. Thanks. Dale :-) :-)
Re: [gentoo-user] Re: [WAS: keyboard stops working] Recent kernels block the loading of non-GPL kernel modules
walt wrote: On Tue, 18 Aug 2015 15:49:16 -0500 Dale rdalek1...@gmail.com wrote: I think there is two issues but you are addressing one of them it seems. The other issue happens when the kernel panics and it reboots itself. It doesn't complete the boot process. The one you describe could be it tho. On that one, I don't have a GUI. Since I use my puter a lot, I usually just reboot to a known working kernel and deal with it later. While I think I get the idea of what the kernel devs are doing. I also think they should let the users send the message. The users can start buying ATI or other video hardware and at some point, they will either get their ducks in a row or lose sales. In the meantime, the users decide what software they want to use. I did some searching based on the config option you gave and I'm unable to find a way to override this myself. It doesn't seem to be a setting I can put in make.conf or package.use etc either. If this is the case, I may wish Nvidia would switch to open source but it sort of rubs me the wrong way that someone else is making the decision and me having no way to exercise my decision to use it anyway. I don't care if Nvidia doesn't show its code as long as it works and it isn't spying on me or blowing up my house here. If you have any info on how to override this, I'd be glad to see it. Just a link or something would help. This is a bug for ati-drivers, but nvidia-drivers has exactly the same problem to solve. Comments 7, 8, 9 sum it up pretty well: https://bugs.gentoo.org/show_bug.cgi?id=548118 I read through that long thing. It seems the kernel folks are stirring up a storm that makes the users have to jump through hoops. Let me see if I get this right. The kernel devs don't want to allow a user to install a driver that they don't approve of. Those would include Nvidia and ATI it would seem, at least. So, since they don't like the drivers, they make it so that users can't use them. Which leaves users with two options, three if you like to jump a lot. Option one, don't upgrade your kernel and use the older versions, lacking security fixes and all that goes with it. Option 2, do without a GUI since you don't have video driver for your video card. Option 3, force the drivers to build and maybe even violate the law while doing it. It seems based on one post that you can't just change that code so that it will load like it has before. Well, at least not easily. Here's a clue. Why doesn't the kernel devs let users decide what drivers they are comfy with using? If they don't like the drivers, then make it so that users have to install their own just like we have for ages but don't disable them or make them not load and work. The kernel devs can stop using the drivers they don't like and sit there in a console with no GUI while the rest of us go on with life and using our video drivers that we are happy with. Sounds to simple don't it? LOL Dale :-) :-)
Re: [gentoo-user] Re: !!!!
On 08/18/2015 05:29 PM, walt wrote: On Tue, 18 Aug 2015 15:52:53 -0400 Alan Grimes alonz...@verizon.net wrote: Like a stupid dumbfuck, I tried to update my machine today tortoise ~ # revdep-rebuild /bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory tortoise ~ # ufed sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory Couldn't determine EPREFIX and PORTDIR from Portage INIT failed--call queue aborted. tortoise ~ # GOOD JOB, PENGUINS!!! I won't even be able to reboot my machine!!! In addition to the suggestions already made by other posters, it's good to keep busybox in mind. Depending on how you boot your machine, there is usually a way you can pass 'init=/bin/bb' to the kernel at boot time. You can do wonderful stuff with busybox when you're in a bind. I haven't really been following this closely but I haven't seen any suggestion to use emerge -1 --quiet=y smart-live-rebuild to remove the offending curses output. Hopefully emerge doesn't check/use curses unless it's producing actual output.
[gentoo-user] Re: [~amd64] Keyboard stops working several times/day
On Tue, 18 Aug 2015 20:38:10 +0200 Heiko Baums li...@baums-on-web.de wrote: Am 18.08.2015 um 04:04 schrieb walt: I see the keyboard problem in mate and xfce4 (the only ones I use now). I've wondered about the same things but I don't know how to debug those possible scenarios. And which terminal emulator are you using? I've seen the keyboard halting problem using xterm and gnome-terminal (running under mate, not gnome, but it seems to work normally). At the moment I'm waiting for my new keyboard to arrive from amazon, hoping to pin the blame on flakey hardware instead of flakey software. Somehow I doubt that it's the keyboard. I rather guess it's either a wrong configuration of or a bug in the desktop environment, the terminal emulator and/or systemd/udev. I plugged in my new keyboard two hours ago. So far no problems but that doesn't mean much yet. I used the old keyboard for about ten hours this morning and it stopped only once, about eight hours ago. If the new keyboard works correctly for the rest of this week I'll be convinced it was hardware :)
[gentoo-user] Re: !!!!
On Tue, 18 Aug 2015 18:03:31 -0700 John Campbell jdc@cox.net wrote: I haven't really been following this closely but I haven't seen any suggestion to use emerge -1 --quiet=y smart-live-rebuild to remove the offending curses output. Hopefully emerge doesn't check/use curses unless it's producing actual output. A very obscure hint, and I like it :) I have no trouble emerging packages (at the moment) so I emerged app-portage/smart-live-rebuild, which dragged in eselect-package-manager as a dependency. 'eselect package-manager list' shows only portage as installed, even though I now also have porthole and smart-live-rebuild installed too. Do you see something different?
[gentoo-user] Re: [WAS: keyboard stops working] Recent kernels block the loading of non-GPL kernel modules
On Tue, 18 Aug 2015 15:49:16 -0500 Dale rdalek1...@gmail.com wrote: walt wrote: entire post severely snipped for brevity On Mon, 17 Aug 2015 00:53:37 -0500 Dale rdalek1...@gmail.com wrote: walt wrote: Linus and friends have been marking lots of existing kernel symbols with the SYMBOL_EXPORT_GPL macro, which was designed to block the loading of any kernel module not explicitly licensed as GPL software. The only module I have is Nvidia but that is one thing that doesn't work at times. Sometimes, it doesn't want to boot all the way. It doesn't even get through the kernel loading everything up at times. The Nvidia module is causing your problem then, because Nvidia supplies their binary blob under their own proprietary license. I'm using an elderly version of x11-drivers/nvidia-drivers on an elderly machine, but when I run 'modinfo -l nvidia' I see 'NVIDIA' as the response. If the response isn't 'GPL' then the affected kernels will refuse to load the module at boot time. The kernel devs have provided a workaround for the problem, however: You (or a gentoo dev) need to edit the source code for the problem kernel by changing the SYMBOL_EXPORT_GPL to SYMBOL_EXPORT. That macro appears maybe hundreds of places in the kernel sources, and has been there for years now, but only one or two of those source files needs to be patched, depending on which of those exported symbols is needed by your particular binary driver (e.g. nvidia-drivers or ati-drivers). This whole GPL/module thing is far from new. What's new is that the kernel devs are slowly adding more kernel symbols to their black list. I think the idea is to turn up the pressure very slowly on companies like Nividia and ATI to discourage them from providing proprietary drivers while not driving them out of the linux market completely. Every year linux is getting stronger and the devs can afford to be pushier with wealthy corporations who need more linux customers. I think there is two issues but you are addressing one of them it seems. The other issue happens when the kernel panics and it reboots itself. It doesn't complete the boot process. The one you describe could be it tho. On that one, I don't have a GUI. Since I use my puter a lot, I usually just reboot to a known working kernel and deal with it later. While I think I get the idea of what the kernel devs are doing. I also think they should let the users send the message. The users can start buying ATI or other video hardware and at some point, they will either get their ducks in a row or lose sales. In the meantime, the users decide what software they want to use. I did some searching based on the config option you gave and I'm unable to find a way to override this myself. It doesn't seem to be a setting I can put in make.conf or package.use etc either. If this is the case, I may wish Nvidia would switch to open source but it sort of rubs me the wrong way that someone else is making the decision and me having no way to exercise my decision to use it anyway. I don't care if Nvidia doesn't show its code as long as it works and it isn't spying on me or blowing up my house here. If you have any info on how to override this, I'd be glad to see it. Just a link or something would help. This is a bug for ati-drivers, but nvidia-drivers has exactly the same problem to solve. Comments 7, 8, 9 sum it up pretty well: https://bugs.gentoo.org/show_bug.cgi?id=548118
[gentoo-user] Re: !!!!
On Tue, 18 Aug 2015 15:52:53 -0400 Alan Grimes alonz...@verizon.net wrote: Like a stupid dumbfuck, I tried to update my machine today tortoise ~ # revdep-rebuild /bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory tortoise ~ # ufed sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory Couldn't determine EPREFIX and PORTDIR from Portage INIT failed--call queue aborted. tortoise ~ # GOOD JOB, PENGUINS!!! I won't even be able to reboot my machine!!! In addition to the suggestions already made by other posters, it's good to keep busybox in mind. Depending on how you boot your machine, there is usually a way you can pass 'init=/bin/bb' to the kernel at boot time. You can do wonderful stuff with busybox when you're in a bind.
Re: [gentoo-user] Re: !!!!
walt wrote: On Tue, 18 Aug 2015 15:52:53 -0400 Alan Grimes alonz...@verizon.net wrote: Like a stupid dumbfuck, I tried to update my machine today tortoise ~ # revdep-rebuild /bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory tortoise ~ # ufed sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory Couldn't determine EPREFIX and PORTDIR from Portage INIT failed--call queue aborted. tortoise ~ # GOOD JOB, PENGUINS!!! I won't even be able to reboot my machine!!! In addition to the suggestions already made by other posters, it's good to keep busybox in mind. Depending on how you boot your machine, there is usually a way you can pass 'init=/bin/bb' to the kernel at boot time. You can do wonderful stuff with busybox when you're in a bind. And for the future, this could be very handy. FEATURES=buildpkg That goes in or added to the current line in make.conf. That little thing has saved my bacon more than once. Dale :-) :-)
Re: [gentoo-user] Re: !!!!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 19/08/15 10:41, Dale wrote: And for the future, this could be very handy. FEATURES=buildpkg That goes in or added to the current line in make.conf. That little thing has saved my bacon more than once. For system-critical packages when all other hope is lost, there's also http://packages.gentooexperimental.org/packages/ I haven't seen anything that says exactly what packages this provides, but I would assume @system. - -- wraeth wra...@wraeth.id.au GnuPG Key: B2D9F759 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iF4EAREIAAYFAlXT01gACgkQXcRKerLZ91nkgQD5AXDsupX07+3AitX013BJiQct tB7+6vD+lly0X8qmICQA/jj0PJJzPqWeBX+zW8orxZ0ngZ2Pqf6UhdAS1djQGA/o =/glH -END PGP SIGNATURE-
Re: [gentoo-user] Re: [WAS: keyboard stops working] Recent kernels block the loading of non-GPL kernel modules
On Tue, Aug 18, 2015 at 4:49 PM, Dale rdalek1...@gmail.com wrote: If you have any info on how to override this, I'd be glad to see it. Just a link or something would help. I haven't tested it, but I'd think the simplest solution would be something like this (which just turns EXPORT_SYMBOL_GPL into EXPORT_SYMBOL, and should be a lot easier than fixing every export that the drivers use): diff --git a/include/linux/export.h b/include/linux/export.h index 96e45ea..b1bc4c3 100644 --- a/include/linux/export.h +++ b/include/linux/export.h @@ -69,7 +69,7 @@ extern struct module __this_module; __EXPORT_SYMBOL(sym, ) #define EXPORT_SYMBOL_GPL(sym) \ - __EXPORT_SYMBOL(sym, _gpl) + __EXPORT_SYMBOL(sym, ) #define EXPORT_SYMBOL_GPL_FUTURE(sym) \ __EXPORT_SYMBOL(sym, _gpl_future) I really think that this kind of approach by the kernel devs isn't really going to go anywhere. It might cause companies like nvidia/ati to just dump linux support, but it seems more likely that they'd just play workaround games. Maybe they create a GPL module that just exposes all the APIs as non-GPL. Maybe they make it clear that their module is non-GPL, but have it report itself as GPL to the kernel. I think the kernel devs would be hard-pressed to mount some kind of GPL infringement lawsuit. In general US courts have tended to block attempts to use copyright/trademark/patents/etc simply to prevent interoperability, and that is basically what this is. And would we really want it any other way? How is this not like Brother sticking chips in their ink cartridges containing copyrighted code, or the chip in lightning cables? I do get the frustration of the kernel developers. The GPU makers should be competing on their GPUs, not on their drivers. However, Linux isn't their main market and forcing the issue is probably just going to drive them to ignore it. -- Rich
Re: [gentoo-user] Re: !!!!
Fernando Rodriguez wrote: PS: There's a post by wraeth on this thread, is anybody having problems opening it? kmail crashes everytime I try. It opens fine here. It's short and has a GnuPG v2 signature attached at the bottom. Could that be the cause of the problem? I don't see anything else in the message. Dale :-) :-)
Re: [gentoo-user] UEFI booting
2015-08-17 20:59 GMT+08:00 Rod r...@rods.id.au: Hi list, I'm trying to figure out how to make my boot partition to boot from UEFI, I have grub2 installed, but I keep getting a error when I ask it to install the boot information. mount /dev/sdc1 201633156 201478 1% /boot/efi I have the /boot/efi part mounted ok.. # efibootmgr efibootmgr: EFI variables are not supported on this system. # grub2-install --target=x86_64-efi /dev/sdc Installing for x86_64-efi platform. efibootmgr: EFI variables are not supported on this system. efibootmgr: EFI variables are not supported on this system. Installation finished. No error reported. I have this disk as my 1st boot drive in BIOS, the 2nd is the normal drive. Boot order is EFI then Legacy (EFI only tells me Insert boot disk and hit Enter) if you see Insert boot disk and hit Enter then you are not using EFI mode. it is printed by MS DOS bootloader, aka , the MBR. I'm assuming the variables not supported is blocking the install. BIOS reports the 1st disk to boot is EFI: ST2000DM001-1ER1 Mobo is a Gigabyte Z68X-UD3H-B3 (with the latest UEFI firmware) How can I get this UEFI be become bootable without media to make it boot in to that mode to begin with ? -- --- Regards, Rod Smart 0417 513 286
Re: [gentoo-user] Re: !!!!
On Wednesday, August 19, 2015 12:14:46 AM Jeremi Piotrowski wrote: On Tue, 18 Aug 2015, Dale wrote: Grant Edwards wrote: On 2015-08-18, Dale rdalek1...@gmail.com wrote: I don't have any libtinfo.whatever on any of my systems either. By default, I don't think a separate libtinfo is built. One suggestion I saw for this problem (on a different distro) is to symlink libtinfo to libncurses. Ncurses can be compiled as a single library or as two (ncurses + tinfo), in either case all the symbols are present on the system it's just a question of where they are located. Many packages are not prepared to handle the seperate tinfo library, we have many bugs in the bugzilla that deal with tracking down such build failures and correcting them. But this is the first I hear of anyone having a problem with the reverse. It could happen if the tinfo flag is removed (perhaps as an attempt to build one of the many broken packages). If the tinfo library is not preserved everything that linked against it stops working. That's one of the many problems with the current approach to this use flag (patching the multitude of broken packages). I patched my ncurses ebuild to build and install both a full ncurses along with a tinfo library, that causes the most packages to link against curses only so no rebuild is necessary after removing the use flag, everything builds ok and only binary packages use libtinfo. I posted the patch on the tinfo tracker but no one seems interested. Symlinking libtinfo to libncurses *should* work, or atleast seems like a valid rescue attempt. It's worth a shot, but it doesn't work for all packages. I think it depends on the linking order. PS: There's a post by wraeth on this thread, is anybody having problems opening it? kmail crashes everytime I try. -- Fernando Rodriguez
[gentoo-user] how to get a couple of -9999 packages to behave
Hi. I am trying to use at-spi2-core- and at-spi2-atk- from the gnome overlay, but I am having some very peculiar things happening when I emerge them.Both of them need to be abi_x86_32, gtk3 is also, but when I emerge them it gives me existing preserved libs and wants me to compilex11-libs/gtk-3.16.5 and it dies because it cannot find /usr/lib32/pkgconfig/atk-bridge-2.0.pc . So, how do I get the - versions of the ebuilds to give me all the correct files like the 2.16.x versions do? I know the - are from git, but it should do what gentoo wants. If I have to compile out of tree, how could I accomplish getting both the 64 and 32 bit items? I hope I explained my situation properly. Thanks in advance for any ideas. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] !!!!
2015-08-18 22:40 GMT+02:00 Dale rdalek1...@gmail.com: Alan Grimes wrote: Like a stupid dumbfuck, I tried to update my machine today tortoise ~ # revdep-rebuild /bin/bash: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory tortoise ~ # ufed sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory sh: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory Couldn't determine EPREFIX and PORTDIR from Portage INIT failed--call queue aborted. tortoise ~ # GOOD JOB, PENGUINS!!! I won't even be able to reboot my machine!!! A+ configuration management Did you update ncurses by any chance? According to a look up, that file belongs to that package. I might also add, I don't have that file here at all. Sort of odd that I don't have it but portage works fine here. Dale :-) :-) Seems like ncurses was recompiled without the tinfo use flag. You could try booting up a rescue system and unpack a precompiled bash package from another (trusted) system to get your machine working again and continue from there.
