Re: discuss debian 's attitude to ppa
On 05/23/2015 08:58 AM, mudongliang wrote: > Yesterday I installed the LMDE(Linux Mint based Debian Jessie),which is > a rolling release issued by Linux Mint! > The installation is of no question! But when I want to install > openyoudao from ppa , it returns me "not support ppa"! > > So I search it ! Although I don't find some real proof , but I can see > one thing ! Maybe debian will not support ppa , > because in the talk of Neil McGovern, he says some weakness of ppa! And > from the development of Debian , > ppa's development seems to be not able to ensure its stablity! > > What's your opinion? > mudongliang > > I don't know what openyoudao is but when running Debian it is highly recommended not to mix repositories with Ubuntu or other linux distributions. In your case you are not even running Debian but only Debian based Mint (as far as I know though LMDE is Debian compatible in the repository level). That said you can try to install the .deb package with other ways (for example using gdebi) but the main drawback (apart from any inconsistencies already mentioned) is that the package won't be updated with the rest of the system because apt/synaptic will not be able to do this. Regards Dalios -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55602015.3030...@eumx.net
Laptops, UEFI, Secure Boot and Debian
Patrick Bartek writes: > 2. How UEFI compatible is Debian Wheezy? What I'm running on the > Desktop. Or is Jessie the better choice. Or something else entirely? > Except Ubuntu variants (Hate it!). I don't want to run in Legacy mode > for future compatibility. I won't be installing a desktop, just a > window manager. Probably Openbox. Then get Acer C720 Chromebook (with 4 GB of RAM) and install a bigger SSD to it. Everything works in Debian Jessie once you upgrade kernel to a newer version. Boots in a few seconds and no need to pay tax to MS or have UEFI hassles. -- Juha -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/21856.10009.878066.943...@tutpro.com
Re: discuss debian 's attitude to ppa
On 05/23/2015 02:37 PM, Dalios wrote: On 05/23/2015 08:58 AM, mudongliang wrote: Yesterday I installed the LMDE(Linux Mint based Debian Jessie),which is a rolling release issued by Linux Mint! The installation is of no question! But when I want to install openyoudao from ppa , it returns me "not support ppa"! So I search it ! Although I don't find some real proof , but I can see one thing ! Maybe debian will not support ppa , because in the talk of Neil McGovern, he says some weakness of ppa! And from the development of Debian , ppa's development seems to be not able to ensure its stablity! What's your opinion? mudongliang I don't know what openyoudao is but when running Debian it is highly First , openyoudao is an open source project on the github! The designer says we can use ppa to install it! recommended not to mix repositories with Ubuntu or other linux distributions. In your case you are not even running Debian but only Debian based Mint (as far as I know though LMDE is Debian compatible in the repository level). Second , I run Debian Jessie on my desktop! It can install software from ppa! I forget to note it! I'm sorry! That said you can try to install the .deb package with other ways (for example using gdebi) but the main drawback (apart from any inconsistencies already mentioned) is that the package won't be updated with the rest of the system because apt/synaptic will not be able to do this. At last , I want to talk about the future of ppa in Debian! Even the leader has said the weakness of ppa! Maybe Debian will not use ppa! Maybe LMDE is just a hint! Isn't it!? mudongliang Regards Dalios -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/blu436-smtp1673c3dc5c236cf3f042690bc...@phx.gbl
Re: Laptops, UEFI, Secure Boot and Debian
On Fri, 22 May 2015 23:53:14 -0700 Patrick Bartek wrote: > > Researching a laptop purchase (within the next 6 months or so) to > replace my aging Desktop (1 to 8.5 years depending on which parts). > Going to abandoned the Big Box forever. Need to be very portable in > the next year or two. Two questions to begin: > > 1. Many laptops seem to only be able to turn off Secure Boot through > the OS, Windows 8.x, or so I've researched. However, I've read some > makes (Asus, Lenovo, Dell and HP) can do it directly through "BIOS" > without needing to boot Windows? True? Any others? I don't have a laptop myself (don't like them), but every one I've seen so far has had a switch to disable Secure Boot in the BIOS. AFAIK, that switch is mandatory to adhere to the "Built For Windows 8" MS program, although it is only optional for the coming Windows 10 program. That might be something to watch out for. If this is going to become a real problem or not, we will just have to wait and see. > 2. How UEFI compatible is Debian Wheezy? What I'm running on the > Desktop. Or is Jessie the better choice. Or something else > entirely? Except Ubuntu variants (Hate it!). I don't want to run in > Legacy mode for future compatibility. I won't be installing a > desktop, just a window manager. Probably Openbox. You can find details here: https://www.debian.org/releases/stable/amd64/ch03s06.html.en#UEFI I believe the Canonical people have put some effort into becoming fully Secure Boot-compliant, but if you do not like them, then that is not an option. There are also others (RedHat?) but I can't remember who. Petter -- "I'm ionized" "Are you sure?" "I'm positive." pgpuU4SQ3PZja.pgp Description: OpenPGP digital signature
Re: discuss debian 's attitude to ppa
On Sat, 23 May 2015 15:13:33 +0800 mudongliang wrote: > On 05/23/2015 02:37 PM, Dalios wrote: > > That said you can try to install the .deb package with other ways > > (for example using gdebi) but the main drawback (apart from any > > inconsistencies already mentioned) is that the package won't be > > updated with the rest of the system because apt/synaptic will not > > be able to do this. > At last , I want to talk about the future of ppa in Debian! Even the > leader has said the weakness of ppa! Maybe Debian will not use ppa! > Maybe LMDE is just a hint! Isn't it!? > mudongliang The major problem with using a ppa is that the software has not been vetted by the Debian project. It could contain malware or other security problems, and the maintainer of the ppa can suddenly decide to drop support of it, leaving you with a package that does not receive updates. You need to consider whether you trust the person running the ppa to not introduce weaknesses to your system. With the Debian repositories, there is a system in place to handle all of this. Adding a foreign repository _can_ make you vulnerable. You just don't know. There is also the matter of dependencies, if the repository you are using is not intended for your exact distribution. It's not a matter of not supporting ppas, it's a matter of not recommending them. You can always add the repository to sources.list and add the key manually. Petter -- "I'm ionized" "Are you sure?" "I'm positive." pgp_YwpMnryWH.pgp Description: OpenPGP digital signature
Re: discuss debian 's attitude to ppa
On 05/23/2015 03:28 PM, Petter Adsen wrote: On Sat, 23 May 2015 15:13:33 +0800 mudongliang wrote: On 05/23/2015 02:37 PM, Dalios wrote: That said you can try to install the .deb package with other ways (for example using gdebi) but the main drawback (apart from any inconsistencies already mentioned) is that the package won't be updated with the rest of the system because apt/synaptic will not be able to do this. At last , I want to talk about the future of ppa in Debian! Even the leader has said the weakness of ppa! Maybe Debian will not use ppa! Maybe LMDE is just a hint! Isn't it!? mudongliang The major problem with using a ppa is that the software has not been vetted by the Debian project. It could contain malware or other security problems, and the maintainer of the ppa can suddenly decide to drop support of it, leaving you with a package that does not receive updates. You need to consider whether you trust the person running the ppa to not introduce weaknesses to your system. With the Debian repositories, there is a system in place to handle all of this. Adding a foreign repository _can_ make you vulnerable. You just don't know. I think Debian is a distribution which focuses security and stablity. So maybe it should help these interesting ,useful,meaning project import into Debian project! Things out of control may be a bomb I think! Sometimes, you should not rely on the users to classify the problem of application in ppa! The users may only know its function ,but not its details ,or dependency! Maybe it has many vulnerablities for attacker to hack! Maybe it is a virus! There is also the matter of dependencies, if the repository you are using is not intended for your exact distribution. It's not a matter of not supporting ppas, it's a matter of not recommending them. You can always add the repository to sources.list and add the key manually. I have to confess what you said! The user who write list file for his/her system may know much about this software or be an experienced user of Debian! mudongliang -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/blu436-smtp226ffc9680d09ccf2eb18f4bc...@phx.gbl
Re: discuss debian 's attitude to ppa
On Sat, 23 May 2015 16:28:19 +0800 mudongliang wrote: > On 05/23/2015 03:28 PM, Petter Adsen wrote: > > The major problem with using a ppa is that the software has not been > > vetted by the Debian project. It could contain malware or other > > security problems, and the maintainer of the ppa can suddenly > > decide to drop support of it, leaving you with a package that does > > not receive updates. > > > > You need to consider whether you trust the person running the ppa to > > not introduce weaknesses to your system. With the Debian > > repositories, there is a system in place to handle all of this. > > Adding a foreign repository _can_ make you vulnerable. You just > > don't know. > I think Debian is a distribution which focuses security and stablity. > So maybe it should help these interesting ,useful,meaning project > import into Debian project! If you want to get the package adopted by Debian, there is nothing to stop you from offering to maintain it yourself. Somebody needs to take on the responsibility of building the package for Debian, and provide updates and fixes. In the Debian community, this happens within a framework. Everyone is free to contribute and suggest packages for adoption, but it is still dependent on someone actually taking responsibility for the package in question. I have no idea what the package you are talking about is, but if there is a significant need for it, I suggest you go through the appropriate channels to have it adopted. There is probably information on how to do this on the wiki, I'm just too lazy to check. (OK, I checked ;) Read this: https://www.debian.org/doc/manuals/maint-guide/index.en.html That is a guide on building/maintaining Debian packages. You should also take a look at: https://www.debian.org/doc/debian-policy/ch-binary.html And read this if you want the package to actually be adopted: https://wiki.debian.org/SponsorChecklist If there are other things you need to know about, I hope someone else will speak up, as I know little about this. Petter -- "I'm ionized" "Are you sure?" "I'm positive." pgpNthwaDET34.pgp Description: OpenPGP digital signature
Re: Problems getting started with QtQuick and QtCreator
On Sat, 2015-05-23 at 08:24 +0300, Jarle Aase wrote: > Hi all, > > Sorry for the noise. > > I started trying more of the suggestions in different forum threads > regarding this problem, and > >aptitude install qtdeclarative5-dev > > solved it. That sounds like a dependency problem, be sure to file a bug so others won't have the same problem! -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 6FAB5CD5 signature.asc Description: This is a digitally signed message part
Re: discuss debian 's attitude to ppa
Hi. On Sat, 23 May 2015 09:28:55 +0200 Petter Adsen wrote: > On Sat, 23 May 2015 15:13:33 +0800 > mudongliang wrote: > > > On 05/23/2015 02:37 PM, Dalios wrote: > > > That said you can try to install the .deb package with other ways > > > (for example using gdebi) but the main drawback (apart from any > > > inconsistencies already mentioned) is that the package won't be > > > updated with the rest of the system because apt/synaptic will not > > > be able to do this. > > At last , I want to talk about the future of ppa in Debian! Even the > > leader has said the weakness of ppa! Maybe Debian will not use ppa! > > Maybe LMDE is just a hint! Isn't it!? > > mudongliang > > The major problem with using a ppa is that the software has not been > vetted by the Debian project. It could contain malware or other > security problems, and the maintainer of the ppa can suddenly decide to > drop support of it, leaving you with a package that does not receive > updates. > > You need to consider whether you trust the person running the ppa to > not introduce weaknesses to your system. With the Debian repositories, > there is a system in place to handle all of this. Adding a foreign > repository _can_ make you vulnerable. You just don't know. > > There is also the matter of dependencies, if the repository you are > using is not intended for your exact distribution. > > It's not a matter of not supporting ppas, it's a matter of not > recommending them. You can always add the repository to sources.list > and add the key manually. I'd like to add something to your excellent points. $ wget http://ppa.launchpad.net/justzx2011/openyoudao-v0.4/ubuntu/pool/main/o/openyoudao/openyoudao_0.4-1_amd64.deb ... $ lintian openyoudao_0.4-1_amd64.deb | wc -l 48 Whoever packaged this software did abysmally bad job. I doubt that this package would be accepted in Debian archive in the current shape. Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150523150447.b354e66df21b4c91d1d4e...@gmail.com
Re: discuss debian 's attitude to ppa
Hi, On Sat, May 23, 2015 at 01:58:16PM +0800, mudongliang wrote: > Yesterday I installed the LMDE(Linux Mint based Debian Jessie),which is a > rolling release issued by Linux Mint! LMDE is based on Debian but not exactly a Debian. It's Linux Mint. > The installation is of no question! But when I want to install openyoudao > from ppa , it returns me "not support ppa"! > > So I search it ! Although I don't find some real proof , but I can see one > thing ! Maybe debian will not support ppa , PPA created by Debian and based on Debian will be supported but that still has not been created. Random PPA style archive is not supported although some binaries may work. > because in the talk of Neil McGovern, he says some weakness of ppa! And from > the development of Debian , > ppa's development seems to be not able to ensure its stablity! I do not know what you are talking about, but I thought Neil is pushing to create PPA asa paert of service. Osamu -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150523124316.GA19222@goofy.local
Problem Running Application with Alias
VI am running Wheezy (v-7.8.0) in a VM and have encountered rather a strange problem .with an application, MOPAC (a well established quantum chemistry program). The application is installed in /opt/mopac (required by the executable) and, in order to execute the program the following is an entry in the user .bashrc: LD_LIBRARY_PATH="/opt/mopac/MOPAC2012.exe:$LD_LIBRARY_PATH" export LD_LIBRARY_PATH alias mopac='/opt/mopac/MOPAC2012.exe' The permissions for /opt/mopac are: drwxrwxrwx (I should note at this point that this works flawlessly in my production machine.) Now, for the problem, the alias or MOPAC2012.exe work only if evoked in /opt/mopac! If, I attempt running the alias in /home/comp (the user), for instance, I get: comp@inga:~$ mopac /opt/mopac/MOPAC2012.exe: error while loading shared libraries: libiomp5.so: can not open shared object file: No such file or directory Alternately, if I try to run with the ful path to the executabe I get: comp@inga:~$ /opt/mopac/MOPAC2012.exe /opt/mopac/MOPAC2012.exe: error while loading shared libraries: libiomp5.so: can not open shared object file: No such file or directory The workaround is to copy the argument to /opt/mopac, run the executable for the calculation, and then transfer the results to the working directory. This is most inconvenient and I would really appreciate a solution to the problem. Thanks iin advance. -- Stephen P. Molnar, Ph.D. Life is a fuzzy set Foundation for Chemistry Stochastic and Multivariate www.FoundationForChemistry.com (614)312-7528(c) Skype: smolnar1 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5560825f.1030...@sbcglobal.net
Re: Problem Running Application with Alias
On Sat, 23 May 2015 09:36:31 -0400 "Sephen P. Molnar" wrote: > VI am running Wheezy (v-7.8.0) in a VM and have encountered rather a > strange problem .with an application, MOPAC (a well established > quantum chemistry program). > > The application is installed in /opt/mopac (required by the > executable) and, in order to execute the program the following is an > entry in the user .bashrc: > > LD_LIBRARY_PATH="/opt/mopac/MOPAC2012.exe:$LD_LIBRARY_PATH" This is an obvious thing that jumps out at me, this line should be: LD_LIBRARY_PATH="/opt/mopac:$LD_LIBRARY_PATH" as LD_LIBRARY_PATH is meant to contain directories where shared libraries can be found, not an executable binary. In this case, I expect that the shared libraries will not be found, since the loader will look for them in a _directory named_ "MOPAC2012.exe", not "/opt/mopac". > export LD_LIBRARY_PATH > alias mopac='/opt/mopac/MOPAC2012.exe' > > The permissions for /opt/mopac are: drwxrwxrwx > > > (I should note at this point that this works flawlessly in my > production machine.) Maybe there are copies of the libraries in another directory that the loader searches, or "/opt/mopac" is listed in "/etc/ld.so.conf". > comp@inga:~$ /opt/mopac/MOPAC2012.exe > /opt/mopac/MOPAC2012.exe: error while loading shared libraries: > libiomp5.so: can > not open shared object file: No such file or directory > > The workaround is to copy the argument to /opt/mopac, run the > executable for the calculation, and then transfer the results to the > working directory. > > This is most inconvenient and I would really appreciate a solution to > the problem. Try fixing the line that sets LD_LIBRARY_PATH, or adding "/opt/mopac" to "/etc/ld.so.conf" and run ldconfig to update the cache. Petter -- "I'm ionized" "Are you sure?" "I'm positive." pgpW4CMFvGwOJ.pgp Description: OpenPGP digital signature
Testing - login screen and console very dark
At some point during the recent slew of updates in testing I noticed that one of my four systems began exhibiting a strange behavior. When I log out from a desktop session to the greeter or switch to a console screen, the display is so dark I can hardly see its content. I would point out that the first time the login screen is seen after boot it shines at normal brightness. The affected system is a Lenovo Thinkpad T520i, the only system among my 4 machines running the AMD64 kernel. Fortunately it has screen brightness control built into the hardware, so remedying the dim screens is easy enough. I recall having to fiddle with screen brightness on in the DE (Xfce) more than once in the past as versions of the power manager changed. But, in those cases, the login screen and console screen brightness were not affected. The other odd effect I see is that using the screen brightness keys when at the login screen or on the console doesn't step the brightness. The first touch of the brightness control takes brightness all the way to 100%. Once logged in, the brightness control is properly granular. One more oddity about brightness control on the system is that the new power manager plugin for the Xfce panel behaves as I would expect -- except that, if it is sitting in the notification area instead of out on the panel, use of the mouse scrollwheel with the cursor positioned over the power icon does not control screen brightness. This latter issue might well be attributed to the plugin itself, but is the issue of login screen and console screen brightness not a function of non-DE components? There are many, many reports online of people having problems with display brightness recently, but none that I have read seems at all a close match to my situation. Could someone here steer me toward documentation or testing methods that could help me resolve the issue of login screen and console brightness? Thanks! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/556089bb.7030...@comcast.net
RE: Problem Running Application with Alias
-Original Message- From: Petter Adsen [mailto:pet...@synth.no] Sent: Saturday, May 23, 2015 9:47 AM To: debian-user@lists.debian.org Subject: Re: Problem Running Application with Alias On Sat, 23 May 2015 09:36:31 -0400 "Sephen P. Molnar" wrote: > VI am running Wheezy (v-7.8.0) in a VM and have encountered rather a > strange problem .with an application, MOPAC (a well established > quantum chemistry program). > > The application is installed in /opt/mopac (required by the > executable) and, in order to execute the program the following is an > entry in the user .bashrc: > > LD_LIBRARY_PATH="/opt/mopac/MOPAC2012.exe:$LD_LIBRARY_PATH" This is an obvious thing that jumps out at me, this line should be: LD_LIBRARY_PATH="/opt/mopac:$LD_LIBRARY_PATH" as LD_LIBRARY_PATH is meant to contain directories where shared libraries can be found, not an executable binary. In this case, I expect that the shared libraries will not be found, since the loader will look for them in a _directory named_ "MOPAC2012.exe", not "/opt/mopac". > export LD_LIBRARY_PATH > alias mopac='/opt/mopac/MOPAC2012.exe' > > The permissions for /opt/mopac are: drwxrwxrwx > > > (I should note at this point that this works flawlessly in my > production machine.) Maybe there are copies of the libraries in another directory that the loader searches, or "/opt/mopac" is listed in "/etc/ld.so.conf". > comp@inga:~$ /opt/mopac/MOPAC2012.exe > /opt/mopac/MOPAC2012.exe: error while loading shared libraries: > libiomp5.so: can > not open shared object file: No such file or directory > > The workaround is to copy the argument to /opt/mopac, run the > executable for the calculation, and then transfer the results to the > working directory. > > This is most inconvenient and I would really appreciate a solution to > the problem. Try fixing the line that sets LD_LIBRARY_PATH, or adding "/opt/mopac" to "/etc/ld.so.conf" and run ldconfig to update the cache. Petter -- "I'm ionized" "Are you sure?" "I'm positive." Well, that was a red-faced forehead slapper. The solution, or rather the problem, was staring me in the face and I faled to comprehend. Thanks very much for your reply! Stephen P. Molnar, Ph.D.Life is a fuzzy set Foundation for Chemistry Stochastic and multivariate www.FoundationForChemistry.com (614)312-7528 (c) Skype: smolnar1 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/00dc01d09562$af8113b0$0e833b10$@mol...@sbcglobal.net
KVM switch: DVI-D, DVI-I or vga?
Hi list, I am shopping locally here for a good KVM switch. For now, I am not even sure what type should I get. What are advantages to have DVI instead of VGA interface? Are there any justifications in price? VGA KVM is about $20, where is DVI is $100. If money is no object, DVI KVM is better than VGA? Thanks for all info you can share. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150523103033.473c5...@asterius.asterius.net
Running Debian with only 213MB Ram?
Hi all. On my old laptop I chose Openobex as window manager because Gnome is too heavy for it. I get though: $ free -m total used free sharedbuffers cached Mem: 213207 5 4 23111 -/+ buffers/cache: 73140 Swap: 952 0952 with just Openobex and Emacs and a couple of terminal emulators running, not else. Do you think that is too little? Then maybe I should gave up hoping to use Debian on that machine, and look for - if any exists - other systems? Another thing: reading an old post of mine on Linux Debian Users mailing list, some years ago, the above command would show 216 as total Memory. Is it possibile that it's decreased since then?? Thanks for any help, Rodolfo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87oalbnyf4@gmail.com
Re: KVM switch: DVI-D, DVI-I or vga?
On Sat, 23 May 2015 10:30:33 -0400 German wrote: > Hi list, > > I am shopping locally here for a good KVM switch. For now, I am not > even sure what type should I get. What are advantages to have DVI > instead of VGA interface? Are there any justifications in price? VGA > KVM is about $20, where is DVI is $100. If money is no object, DVI KVM > is better than VGA? Thanks for all info you can share. DVI-D = digital, DVI-I = digital + analog, VGA = analog. One thing to be aware of is that you *might* get issues with HDCP (DRM) when using DVI. Read: https://en.wikipedia.org/wiki/Dvi Petter -- "I'm ionized" "Are you sure?" "I'm positive." pgppN8viIhVsL.pgp Description: OpenPGP digital signature
udev hwdb question
In followup to the question I asked about a Logitech mouse a couple of days ago; I can add a file in /etc/udev/hwdb.d and remap a binding as such: KEYBOARD_KEY_70007=back But where can I find a list of what I can map them _to_ (ie, the "back" in this example)? Petter -- "I'm ionized" "Are you sure?" "I'm positive." pgp9aZHEZ5x03.pgp Description: OpenPGP digital signature
Re: Running Debian with only 213MB Ram?
Hi. On Sat, 23 May 2015 14:47:27 + Rodolfo Medina wrote: > Hi all. > > On my old laptop I chose Openobex as window manager because Gnome is too heavy > for it. I get though: > > $ free -m > total used free sharedbuffers cached > Mem: 213207 5 4 23111 > -/+ buffers/cache: 73140 > Swap: 952 0952 > > with just Openobex and Emacs and a couple of terminal emulators running, not > else. Do you think that is too little? Your 'free -m' result cleary show that you have 140M free memory. I.e. 65% of your memory is free. Moreover, you managed to avoid using the swap. An excellent result, if you ask me. Also, see [1]. And BTW, it's openbox, not Openobex :) > Then maybe I should gave up hoping to > use Debian on that machine, and look for - if any exists - other systems? Why would you choose to do so? As long as overall performance satisfies you - there's no need to change anything. > Another thing: reading an old post of mine on Linux Debian Users mailing list, > some years ago, the above command would show 216 as total Memory. Is it > possibile that it's decreased since then?? I have no idea of e-mail you're talking about, so no help from me here, sorry. [1] http://www.linuxatemyram.com/ Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150523180744.b3d03601dee04322a2acc...@gmail.com
Re: KVM switch: DVI-D, DVI-I or vga?
On Sat, 23 May 2015 16:53:37 +0200 Petter Adsen wrote: > On Sat, 23 May 2015 10:30:33 -0400 > German wrote: > > > Hi list, > > > > I am shopping locally here for a good KVM switch. For now, I am not > > even sure what type should I get. What are advantages to have DVI > > instead of VGA interface? Are there any justifications in price? VGA > > KVM is about $20, where is DVI is $100. If money is no object, DVI > > KVM is better than VGA? Thanks for all info you can share. > > DVI-D = digital, DVI-I = digital + analog, VGA = analog. Most of the monitors are DVI-D, right? Now, my attention was caught by DVI-I KVM because of affordable price. Do I need some sort of adapter for DVI-D monitor? How much it is usually running at? Or DVI-I will fit DVI-D output? Thanks > > One thing to be aware of is that you *might* get issues with HDCP > (DRM) when using DVI. > > Read: https://en.wikipedia.org/wiki/Dvi > > Petter > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150523111718.186e4...@asterius.asterius.net
Re: udev hwdb question
On Sat, 2015-05-23 at 16:38 +0200, Petter Adsen wrote: > In followup to the question I asked about a Logitech mouse a couple of > days ago; I can add a file in /etc/udev/hwdb.d and remap a binding as > such: > > KEYBOARD_KEY_70007=back > > But where can I find a list of what I can map them _to_ (ie, the "back" > in this example)? > > Petter > I think that is /usr/include/linux/input.h but in lowercase and without the KEY_ prefix. I haven't tried it myself though. -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 6FAB5CD5 signature.asc Description: This is a digitally signed message part
Re: Testing - login screen and console very dark
On 05/23/2015 10:07 AM, Jape Person wrote: At some point during the recent slew of updates in testing I noticed that one of my four systems began exhibiting a strange behavior. When I log out from a desktop session to the greeter or switch to a console screen, the display is so dark I can hardly see its content. I would point out that the first time the login screen is seen after boot it shines at normal brightness. The affected system is a Lenovo Thinkpad T520i, the only system among my 4 machines running the AMD64 kernel. Fortunately it has screen brightness control built into the hardware, so remedying the dim screens is easy enough. I recall having to fiddle with screen brightness on in the DE (Xfce) more than once in the past as versions of the power manager changed. But, in those cases, the login screen and console screen brightness were not affected. The other odd effect I see is that using the screen brightness keys when at the login screen or on the console doesn't step the brightness. The first touch of the brightness control takes brightness all the way to 100%. Once logged in, the brightness control is properly granular. One more oddity about brightness control on the system is that the new power manager plugin for the Xfce panel behaves as I would expect -- except that, if it is sitting in the notification area instead of out on the panel, use of the mouse scrollwheel with the cursor positioned over the power icon does not control screen brightness. This latter issue might well be attributed to the plugin itself, but is the issue of login screen and console screen brightness not a function of non-DE components? There are many, many reports online of people having problems with display brightness recently, but none that I have read seems at all a close match to my situation. Could someone here steer me toward documentation or testing methods that could help me resolve the issue of login screen and console brightness? Thanks! Additional Information: Once the first use of the brightness key has brightened the login screen or the console screen, the control becomes granular when decreasing or increasing screen brightness. Each time a brightness control keypress is made with a console screen visible, a "^@" appears on the command line or prompt line in addition to the change in screen brightness. The initial adjustment to screen brightness has to be performed separately on the login screen and one of the console screens. (Obviously, I think, making the adjustment on one console screen affects all console screens.) If I adjust the brightness on a console screen, then switch to the login screen, then switch back to the console screen, the console screen has become dimmed again. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55609d08.9000...@comcast.net
Re: KVM switch: DVI-D, DVI-I or vga?
On Sat, 23 May 2015 11:17:18 -0400 German wrote: > On Sat, 23 May 2015 16:53:37 +0200 > Petter Adsen wrote: > > > On Sat, 23 May 2015 10:30:33 -0400 > > German wrote: > > > > > Hi list, > > > > > > I am shopping locally here for a good KVM switch. For now, I am > > > not even sure what type should I get. What are advantages to have > > > DVI instead of VGA interface? Are there any justifications in > > > price? VGA KVM is about $20, where is DVI is $100. If money is no > > > object, DVI KVM is better than VGA? Thanks for all info you can > > > share. > > > > DVI-D = digital, DVI-I = digital + analog, VGA = analog. > > Most of the monitors are DVI-D, right? Now, my attention was caught by > DVI-I KVM because of affordable price. Do I need some sort of adapter > for DVI-D monitor? How much it is usually running at? Or DVI-I will > fit DVI-D output? Thanks Well, all you really need to know is in the link I gave you :) For the connectors, see this: https://en.wikipedia.org/wiki/Digital_Visual_Interface#Connector AFAIK, a DVI-D connector/cable can be plugged into both DVI-D and DVI-I ports, but a DVI-I cable carries extra (analog) signals, so it has extra pins that won't fit in a DVI-D port. A DVI-I KVM will carry both the digital and the analog signal, so you can use a DVI-D cable to connect it to a DVI-D screen - it just won't carry the analog signal, which you wouldn't need or be able to use anyway. You can see illustrations of the connectors in the above link - I really advice you to read it, since it thoroughly explains everything you may need to know. I also remember seeing a "quick and dirty" rundown of the differences on the nVidia site, you will find it if you search for it. The above link is far more exhaustive, though. Petter -- "I'm ionized" "Are you sure?" "I'm positive." pgp1gyePahadw.pgp Description: OpenPGP digital signature
Re: Laptops, UEFI, Secure Boot and Debian
On Sat, 23 May 2015, Petter Adsen wrote: > On Fri, 22 May 2015 23:53:14 -0700 > Patrick Bartek wrote: > > > > > Researching a laptop purchase (within the next 6 months or so) to > > replace my aging Desktop (1 to 8.5 years depending on which parts). > > Going to abandoned the Big Box forever. Need to be very portable in > > the next year or two. Two questions to begin: > > > > 1. Many laptops seem to only be able to turn off Secure Boot through > > the OS, Windows 8.x, or so I've researched. However, I've read some > > makes (Asus, Lenovo, Dell and HP) can do it directly through "BIOS" > > without needing to boot Windows? True? Any others? > > I don't have a laptop myself (don't like them), but every one I've > seen so far has had a switch to disable Secure Boot in the BIOS. > AFAIK, that switch is mandatory to adhere to the "Built For Windows > 8" MS program, although it is only optional for the coming Windows 10 > program. That might be something to watch out for. I've read about that, but right now until W10 in its final form is release, nobody really knows for sure. > If this is going to become a real problem or not, we will just have to > wait and see. > > > 2. How UEFI compatible is Debian Wheezy? What I'm running on the > > Desktop. Or is Jessie the better choice. Or something else > > entirely? Except Ubuntu variants (Hate it!). I don't want to run > > in Legacy mode for future compatibility. I won't be installing a > > desktop, just a window manager. Probably Openbox. > > You can find details here: > > https://www.debian.org/releases/stable/amd64/ch03s06.html.en#UEFI Yes, I read that during my initial research. > I believe the Canonical people have put some effort into becoming > fully Secure Boot-compliant, but if you do not like them, then that > is not an option. There are also others (RedHat?) but I can't > remember who. That compatibility comes from the Linux manufacturer buying a Microsoft Secure Boot key which Canonical and RH have. SUSE, too, I think. Don't know how much that costs them. I prefer not to have Linux under Microsoft's thumb that way. I have no problems with turning Secure Boot off and leaving it off. It's just that I fear that in the future one won't be able to turn it off. And that will really throw a wrench in the Linux community. We'll see. Thanks for your input. B -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150523090455.73d0c...@debian7.boseck208.net
Re: Laptops, UEFI, Secure Boot and Debian
On Sat, 23 May 2015 09:04:55 -0700 Patrick Bartek wrote: > On Sat, 23 May 2015, Petter Adsen wrote: > > > On Fri, 22 May 2015 23:53:14 -0700 > > Patrick Bartek wrote: > > > > > > > > Researching a laptop purchase (within the next 6 months or so) to > > > replace my aging Desktop (1 to 8.5 years depending on which > > > parts). Going to abandoned the Big Box forever. Need to be very > > > portable in the next year or two. Two questions to begin: > > > > > > 1. Many laptops seem to only be able to turn off Secure Boot > > > through the OS, Windows 8.x, or so I've researched. However, > > > I've read some makes (Asus, Lenovo, Dell and HP) can do it > > > directly through "BIOS" without needing to boot Windows? True? > > > Any others? > > > > I don't have a laptop myself (don't like them), but every one I've > > seen so far has had a switch to disable Secure Boot in the BIOS. > > AFAIK, that switch is mandatory to adhere to the "Built For Windows > > 8" MS program, although it is only optional for the coming Windows > > 10 program. That might be something to watch out for. > > I've read about that, but right now until W10 in its final form is > release, nobody really knows for sure. Well, yes and no. We *do* know that the status has changed from "mandatory" to "optional", but whether hardware manufacturers will actually remove the ability to turn Secure Boot off remains to be seen. > > If this is going to become a real problem or not, we will just have > > to wait and see. > > > > > 2. How UEFI compatible is Debian Wheezy? What I'm running on the > > > Desktop. Or is Jessie the better choice. Or something else > > > entirely? Except Ubuntu variants (Hate it!). I don't want to run > > > in Legacy mode for future compatibility. I won't be installing a > > > desktop, just a window manager. Probably Openbox. > > > > You can find details here: > > > > https://www.debian.org/releases/stable/amd64/ch03s06.html.en#UEFI > > Yes, I read that during my initial research. > > > I believe the Canonical people have put some effort into becoming > > fully Secure Boot-compliant, but if you do not like them, then that > > is not an option. There are also others (RedHat?) but I can't > > remember who. > > That compatibility comes from the Linux manufacturer buying a > Microsoft Secure Boot key which Canonical and RH have. SUSE, too, I > think. Don't know how much that costs them. I prefer not to have > Linux under Microsoft's thumb that way. I absolutely agree. > I have no problems with turning Secure Boot off and leaving it off. > It's just that I fear that in the future one won't be able to turn > it off. And that will really throw a wrench in the Linux community. > We'll see. The Linux Foundation is also examining the possibility of obtaining a key that can be used to sign images for distributions (free of charge), and there is also work being done on signing a shim that will launch a "real" bootloader. As the Perl people lovingly remind us, there's more than one way to do it :) Petter -- "I'm ionized" "Are you sure?" "I'm positive." pgpWNbZuGkvwx.pgp Description: OpenPGP digital signature
CLI download interface/tool for Google Images?
I like to use Google Images as a way to get images but I don't like the interface which involves looking at hundreds of tiny thumbs and clicking on numerous links to download a single image. I wonder, did anyone do a tool so you can just type, e.g. $ google-img-dl -s 1024x768 -n 100 jungle to download the 100 first "jungle" hits that are of size 1024x768? Then you can use whatever software to examine the material and decide what to use and what to discard. -- underground experts united http://user.it.uu.se/~embe8573 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87vbfjyzvy@debian.uxu
Re: Query about possible impact of leap second on Debian Linux
Bret Busby wrote: > And, with Debian 6 LTS, in /etc/apt/sources.list, I have, apart from > the commented out lines, > > deb http://http.debian.net/debian/ squeeze main contrib non-free > deb-src http://http.debian.net/debian/ squeeze main contrib non-free > deb http://http.debian.net/debian squeeze-lts main contrib non-free > deb-src http://http.debian.net/debian squeeze-lts main contrib non-free I am only commenting for the archive to confirm that those should be good. Here are references for those reading later and wish to check for updated information. https://wiki.debian.org/LTS https://wiki.debian.org/LTS/Using Bob signature.asc Description: Digital signature
Re: [OT] 2 dhcp server on same lan
Eike Lantzsch wrote: > DHCP failover on a small network does not seem to be worth the > effort, except for training purposes. Exactly that is why this > thread was very informative for me. Just for kicks (training) I was > trying for a while to set up two dhcp servers on my network. One > OpenBSD on a router and the other on Debian arm isc-dhcp-server on a > cubietruck. Training is almost always worth the effort as long as something is learned in the process. > One sends sync messages and the other connects to ip-ports - duh! > The philosophy of OpenBSD dhcp seems to be really wide area networks not > being > on the same premises and isc-dhcp seems to be better fitted for LAN. > Now I know that my endeavours are futile. They were not futile. You learned something from them. Therefore the effort had good value. > The synchronization between two OpenBSD dhcp servers and the > failover isc-dhcp-server are essentially different and do not work > together. Either 2 * isc-dhcp-server (which is available for OpenBSD > as a package) or 2 * OpenBSD dhcp servers (which does not exist for > the armv7l cubietruck) => need another machine or "maquinita". Even better you shared your experience with the mailing list and allowed me to learn something too. I am completely unfamiliar with the OpenBSD dhcp daemon but now I know a little more about it. (I use the ISC dhcp software.) Bob signature.asc Description: Digital signature
Re: CLI download interface/tool for Google Images?
On Sat, 2015-05-23 at 19:20 +0200, Emanuel Berg wrote: > I like to use Google Images as a way to get images but > I don't like the interface which involves looking at > hundreds of tiny thumbs and clicking on numerous links > to download a single image. > > I wonder, did anyone do a tool so you can just type, > e.g. > > $ google-img-dl -s 1024x768 -n 100 jungle > > to download the 100 first "jungle" hits that are of > size 1024x768? > > Then you can use whatever software to examine the > material and decide what to use and what to discard. I have seen a couple of different scripts that scrape the image search, for example: https://github.com/tytek2012/givemepics I haven't tried it myself though, and do be careful when trying random scripts found on the web :) If that doesn't work, I don't think it can be too hard to write something form scratch, either scraping the results or using Googles APIs? HTH, -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 6FAB5CD5 signature.asc Description: This is a digitally signed message part
Re: Boot menu entries
Lisi Reisz wrote: > Bob Proulx wrote: > > The newest latest kernel installed is on the bottom. > > Not here. I have the oldest on the bottom. > > lisi@Tux-II:~$ dpkg -S /boot/vmlinuz-* > linux-image-3.16.0-0.bpo.4-amd64: /boot/vmlinuz-3.16.0-0.bpo.4-amd64 > linux-image-3.16-0.bpo.2-amd64: /boot/vmlinuz-3.16-0.bpo.2-amd64 > linux-image-3.16-0.bpo.3-amd64: /boot/vmlinuz-3.16-0.bpo.3-amd64 > linux-image-3.2.0-4-amd64: /boot/vmlinuz-3.2.0-4-amd64 > lisi@Tux-II:~$ I got caught by version sorting lexicographical! Good catch! I had the same two with 3.2 and 3.16 too but didn't see it because for me those were buried in the middle. I guess I could have used the ls --sort=version sort to sort the order first. Just because I am pedantic try this: $ dpkg -S $(ls -v /boot/vmlinuz-*) linux-image-2.6.39-2-amd64: /boot/vmlinuz-2.6.39-2-amd64 linux-image-3.0.0-2-amd64: /boot/vmlinuz-3.0.0-2-amd64 linux-image-3.1.0-1-amd64: /boot/vmlinuz-3.1.0-1-amd64 linux-image-3.2.0-1-amd64: /boot/vmlinuz-3.2.0-1-amd64 linux-image-3.2.0-2-amd64: /boot/vmlinuz-3.2.0-2-amd64 linux-image-3.2.0-3-amd64: /boot/vmlinuz-3.2.0-3-amd64 linux-image-3.2.0-4-amd64: /boot/vmlinuz-3.2.0-4-amd64 linux-image-3.8-2-amd64: /boot/vmlinuz-3.8-2-amd64 linux-image-3.9-1-amd64: /boot/vmlinuz-3.9-1-amd64 linux-image-3.10-1-amd64: /boot/vmlinuz-3.10-1-amd64 linux-image-3.10-2-amd64: /boot/vmlinuz-3.10-2-amd64 linux-image-3.10-3-amd64: /boot/vmlinuz-3.10-3-amd64 linux-image-3.16.0-4-amd64: /boot/vmlinuz-3.16.0-4-amd64 linux-image-4.0.0-1-amd64: /boot/vmlinuz-4.0.0-1-amd64 The docs on ls -v are: ‘-v’ ‘--sort=version’ Sort by version name and number, lowest first. It behaves like a default sort, except that each sequence of decimal digits is treated numerically as an index/version number. :-) Bob signature.asc Description: Digital signature
Re: KVM switch: DVI-D, DVI-I or vga?
On 05/23/2015 07:30 AM, German wrote: I am shopping locally here for a good KVM switch. For now, I am not even sure what type should I get. What are advantages to have DVI instead of VGA interface? Are there any justifications in price? VGA KVM is about $20, where is DVI is $100. If money is no object, DVI KVM is better than VGA? Thanks for all info you can share. I run and work on many different makes and models of PC-compatible computers. VGA and PS/2 are the lowest-common-denominator interfaces -- especially for servers, retail point of sale, and business desktops. So, I have an 8-port KVM with VGA and PS/2 connectors, and a monitor, keyboard, and mouse to match. I use various PS/2-to-USB, DVI-I-to-VGA, DisplayPort-to-VGA, etc., adapters at the computer end of the KVM cables. I don't use USB or microphones through the KVM. I use a passive line-level mixer for speakers. Determining compatibility before making a purchase is tough. Hardware tends to be identified by product manufacturer name and model number, while software (device drivers) tends to be identified by chip manufacturer name and part number. After searching and reading whatever you can, you will need to buy a KVM, plug it in, and find out for yourself. Make sure you buy the KVM through a vendor that will allow you to use it for a week or two, and return it if you don't like it. I went through several KVM's before finding one (IOGEAR GCS78) that worked reliably with Windows and Linux, and put the hotkeys where they didn't interfere with other applications (notably games). David -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5560c468.1010...@holgerdanske.com
Re: KVM switch: DVI-D, DVI-I or vga?
On Sat, 23 May 2015 11:18:16 -0700 David Christensen wrote: > On 05/23/2015 07:30 AM, German wrote: > > I am shopping locally here for a good KVM switch. For now, I am not > > even sure what type should I get. What are advantages to have DVI > > instead of VGA interface? Are there any justifications in price? VGA > > KVM is about $20, where is DVI is $100. If money is no object, DVI > > KVM is better than VGA? Thanks for all info you can share. > > I run and work on many different makes and models of PC-compatible > computers. VGA and PS/2 are the lowest-common-denominator interfaces > -- especially for servers, retail point of sale, and business > desktops. So, I have an 8-port KVM with VGA and PS/2 connectors, and > a monitor, keyboard, and mouse to match. I use various PS/2-to-USB, > DVI-I-to-VGA, DisplayPort-to-VGA, etc., adapters at the computer end > of the KVM cables. I don't use USB or microphones through the KVM. > I use a passive line-level mixer for speakers. > > > Determining compatibility before making a purchase is tough. > Hardware tends to be identified by product manufacturer name and > model number, while software (device drivers) tends to be identified > by chip manufacturer name and part number. After searching and > reading whatever you can, you will need to buy a KVM, plug it in, and > find out for yourself. Make sure you buy the KVM through a vendor > that will allow you to use it for a week or two, and return it if you > don't like it. I went through several KVM's before finding one > (IOGEAR GCS78) that worked reliably with Windows and Linux, and put > the hotkeys where they didn't interfere with other applications > (notably games). > > > David > > Thanks for your thoughts, David. You have mentioned adapters. So it makes sense to use for instance vga-to-dvi adapter? How about the quality of this connection? Is this worth it? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150523143852.167fa...@asterius.asterius.net
Re: CLI download interface/tool for Google Images?
Sven Arvidsson writes: > I have seen a couple of different scripts that > scrape the image search, for example: > https://github.com/tytek2012/givemepics That didn't work, and the style of the program including the documentation tells me it isn't "mature" in more than one sense of the word... > If that doesn't work, I don't think it can be too > hard to write something form scratch, either > scraping the results or using Googles APIs? If you do it, please tell me :) -- underground experts united http://user.it.uu.se/~embe8573 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87fv6nyvh8@debian.uxu
Re: Fwd: rc.local and systemd
Hi Michael, thanks for your prompt reply. Am Montag, 18. Mai 2015, 22:21:42 schrieb Michael Biebl: > Am 18.05.2015 um 22:01 schrieb Rainer Dorsch: > > root@nanette:~# systemctl status rc-local.service > > ● rc-local.service - /etc/rc.local Compatibility > > > >Loaded: loaded (/lib/systemd/system/rc-local.service; static) > >Active: failed (Result: exit-code) since Mon 2015-05-18 14:29:04 CEST; > >7h > > > > ago > > > > May 18 14:29:02 nanette rc.local[741]: Loaded 750 prior measurements > > May 18 14:29:04 nanette rc.local[741]: Error opening terminal: unknown. > > May 18 14:29:04 nanette rc.local[741]: RAPL device for cpu 0 > > May 18 14:29:04 nanette rc.local[741]: RAPL device for cpu 0 > > May 18 14:29:04 nanette rc.local[741]: RAPL device for cpu 0 > > May 18 14:29:04 nanette systemd[1]: rc-local.service: control process > > exited, code=exited status=1 > > May 18 14:29:04 nanette systemd[1]: Failed to start /etc/rc.local > > Compatibility. > > May 18 14:29:04 nanette systemd[1]: Unit rc-local.service entered failed > > state. > > root@nanette:~# > > So, as you can see, /etc/rc.local *is* run. > As you can also see, powertop exits with a non-zero return code. Since > /etc/rc.local uses "set -e", your script exits at this point and the > service is marked as failed. > > Everything working as expected from the systemd side. Hmmseems that systemd does not define the TERM variable. Defining that at least makes powertop performing the expected settings. Nevertheless I am still wondering why it has the failed status, rc.local has an hard "exit 0" return code (?) : rd@nanette:/etc$ diff -u rc.local~ rc.local --- rc.local~ 2015-01-31 15:34:33.044782111 +0100 +++ rc.local2015-05-23 14:27:42.043875921 +0200 @@ -11,6 +11,6 @@ # # By default this script does nothing. -powertop --auto-tune +TERM=vt100 powertop --auto-tune exit 0 rd@nanette:/etc$ systemctl status rc-local.service ● rc-local.service - /etc/rc.local Compatibility Loaded: loaded (/lib/systemd/system/rc-local.service; static) Active: failed (Result: exit-code) since Sat 2015-05-23 12:26:46 CEST; 8h ago Process: 795 ExecStart=/etc/rc.local start (code=exited, status=1/FAILURE) rd@nanette:/etc$ cat rc.local #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing. TERM=vt100 powertop --auto-tune exit 0 rd@nanette:/etc$ Thanks, Rainer -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2566366.HTGLlFCDbi@nanette
Re: KVM switch: DVI-D, DVI-I or vga?
On 05/23/2015 11:38 AM, German wrote: So it makes sense to use for instance vga-to-dvi adapter? How about the quality of this connection? Is this worth it? My DVI-I-to-VGA adapter came with my Intel motherboard and seems to work without problems or visual artifacts (signal degradation). I suspect that it is a passive device that simply wires through the right pins and/or sockets for the analog signal path. I assume there are VGA-to-DVI-I adapters, but I haven't had the need and don't own one. A key specification for devices that pass analog video is the bandwidth -- the higher the better. That shouldn't be a problem today, but... As for quality and worth, that's up to you to measure and decide. As with the KVM, researching adapters can be tough and the only way to find out for sure is to buy one and try it. David -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5560d208.7070...@holgerdanske.com
Re: Fwd: rc.local and systemd
Am 23.05.2015 um 20:56 schrieb Rainer Dorsch: > Am Montag, 18. Mai 2015, 22:21:42 schrieb Michael Biebl: >> As you can also see, powertop exits with a non-zero return code. Since >> /etc/rc.local uses "set -e", your script exits at this point and the >> service is marked as failed. .. > Hmmseems that systemd does not define the TERM variable. Defining that at > least makes powertop performing the expected settings. Nevertheless I am > still > wondering why it has the failed status, rc.local has an hard "exit 0" return > code (?) : The "exit 0" is useless since, as already explained, the script use "set -e". If a command returns a non-zero exit status, the script will stop at this point and return that exit status. Which means you'll never reach exit 0 in such a case. From "help set" -e Exit immediately if a command exits with a non-zero status. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: KVM switch: DVI-D, DVI-I or vga?
German wrote: > I am shopping locally here for a good KVM switch. For now, I am not > even sure what type should I get. What are advantages to have DVI > instead of VGA interface? Are there any justifications in price? VGA > KVM is about $20, where is DVI is $100. If money is no object, DVI KVM > is better than VGA? Thanks for all info you can share. There is, in my opinion, a significant difference in visual quality between the digital and analog display feeds. For me I might not pay $100 for a digital KVM but I also would not give up my digital display feed for an analog KVM one either. Analog was okay for lower resolution CRT analog monitors. Higher resolution LCD monitors really look a lot better with a digital feel than with an analog feed. Feeding a large high resolution LCD monitor with an analog VGA feed in my opinion really looks terrible. There are dynamic artifacts. It's awful. My advice is to try it yourself. Try two tests side by side. One being an analog feed of your display and the other being a digital feed of your display. It's a brain thing and maybe for your brain you will look at it and go, I don't see anything significant there. If so that is great. Don't spend any money on it. On the other hand you may be like me and find the analog feed to the LCD monitor to be really pretty annoying. You should try it and see how it works for you. Another possibility is that a lot of monitors have both an analog VGA and a digital DVI input and can switch between them using the monitor's on screen display. You could plug the KVM into the analog VGA for some light use but still use the digital DVI for your main work and enjoy the full quality resolution there. Just an idea. Bob signature.asc Description: Digital signature
Re: Laptops, UEFI, Secure Boot and Debian
On Sat, 23 May 2015, Petter Adsen wrote: > On Sat, 23 May 2015 09:04:55 -0700 > Patrick Bartek wrote: > > > On Sat, 23 May 2015, Petter Adsen wrote: > > > > > On Fri, 22 May 2015 23:53:14 -0700 > > > Patrick Bartek wrote: > > > > > > > > > > > Researching a laptop purchase (within the next 6 months or so) > > > > to replace my aging Desktop (1 to 8.5 years depending on which > > > > parts). Going to abandoned the Big Box forever. Need to be very > > > > portable in the next year or two. Two questions to begin: > > > > > > > > 1. Many laptops seem to only be able to turn off Secure Boot > > > > through the OS, Windows 8.x, or so I've researched. However, > > > > I've read some makes (Asus, Lenovo, Dell and HP) can do it > > > > directly through "BIOS" without needing to boot Windows? True? > > > > Any others? > > > > > > I don't have a laptop myself (don't like them), but every one I've > > > seen so far has had a switch to disable Secure Boot in the BIOS. > > > AFAIK, that switch is mandatory to adhere to the "Built For > > > Windows 8" MS program, although it is only optional for the > > > coming Windows 10 program. That might be something to watch out > > > for. > > > > I've read about that, but right now until W10 in its final form is > > release, nobody really knows for sure. > > Well, yes and no. We *do* know that the status has changed from > "mandatory" to "optional", but whether hardware manufacturers will > actually remove the ability to turn Secure Boot off remains to be > seen. Yes. I read that. Wonder what Microsoft has up its sleeve? Maybe, this is indicative of W10 being even more insecure than previous Windows' OSes. > > > If this is going to become a real problem or not, we will just > > > have to wait and see. > > > > > > > 2. How UEFI compatible is Debian Wheezy? What I'm running on > > > > the Desktop. Or is Jessie the better choice. Or something else > > > > entirely? Except Ubuntu variants (Hate it!). I don't want to > > > > run in Legacy mode for future compatibility. I won't be > > > > installing a desktop, just a window manager. Probably Openbox. > > > > > > You can find details here: > > > > > > https://www.debian.org/releases/stable/amd64/ch03s06.html.en#UEFI > > > > Yes, I read that during my initial research. > > > > > I believe the Canonical people have put some effort into becoming > > > fully Secure Boot-compliant, but if you do not like them, then > > > that is not an option. There are also others (RedHat?) but I can't > > > remember who. > > > > That compatibility comes from the Linux manufacturer buying a > > Microsoft Secure Boot key which Canonical and RH have. SUSE, too, I > > think. Don't know how much that costs them. I prefer not to have > > Linux under Microsoft's thumb that way. > > I absolutely agree. > > > I have no problems with turning Secure Boot off and leaving it off. > > It's just that I fear that in the future one won't be able to turn > > it off. And that will really throw a wrench in the Linux community. > > We'll see. > > The Linux Foundation is also examining the possibility of obtaining a > key that can be used to sign images for distributions (free of > charge), and there is also work being done on signing a shim that > will launch a "real" bootloader. As the Perl people lovingly remind > us, there's more than one way to do it :) Where there's a will, there's a way I suppose. Although, instead of a patch or shim, the threat of a class action lawsuit by Linux developers might be more effective. B -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150523124610.3b20e...@debian7.boseck208.net
test if fan is working
hello, How can I test if my fan is working in Debian?, thanks, -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1432411314.3937272.276553953.0ae38...@webmail.messagingengine.com
Re: test if fan is working
On Sat, May 23, 2015 at 01:01:54PM -0700, Anil Duggirala wrote: > hello, > How can I test if my fan is working in Debian?, thanks, I've installed the xsensors package. It continually reports the RPM of three fans. Would this do? Haines Brown -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150523201614.gd30...@engels.historicalmaterialism.info
Re: Problem Running Application with Alias
Petter Adsen wrote:
> On Sat, 23 May 2015 09:36:31 -0400
> > LD_LIBRARY_PATH="/opt/mopac/MOPAC2012.exe:$LD_LIBRARY_PATH"
>
> This is an obvious thing that jumps out at me, this line should be:
>
> LD_LIBRARY_PATH="/opt/mopac:$LD_LIBRARY_PATH"
>
> as LD_LIBRARY_PATH is meant to contain directories where shared
> libraries can be found, not an executable binary.
I have a small comment concerning the syntax. I am sure you are
correct about the problem. But both of those assume that
$LD_LIBRARY_PATH already exists in the environment. If it does then
fine. Let me use "foo" as a stand-in for the explanation.
$ foo=/bar
$ foo=/opt/somepath:$foo
$ echo "$foo"
/opt/somepath:/bar
But if it does not exist then it leaves the environment variable with
a hanging colon at the end.
$ unset foo
$ foo=/opt/somepath:$foo
$ echo "$foo"
/opt/somepath:
That is bad and actually has been argued is a security consideration
in other paths such as PATH.
To avoid that the following shell syntax is typically used.
$ foo="/bar"
$ foo=/opt/somepath${foo+:$foo}
$ echo "$foo"
/opt/somepath:/bar
$ unset foo
$ foo=/opt/somepath${foo+:$foo}
$ echo "$foo"
/opt/somepath
Or to append to the end of the path put the colon on the other side.
$ foo="/bar"
$ foo=${foo+$foo:}/opt/somepath
$ echo "$foo"
/bar:/opt/somepath
$ unset foo
$ foo=${foo+$foo:}/opt/somepath
$ echo "$foo"
/opt/somepath
The dash documentation on this standard shell feature is:
${parameter:+word}Use Alternative Value. If parameter is unset or
null, null is substituted; otherwise, the expansion
of word is substituted.
In the parameter expansions shown previously, use of the colon in the
format results in a test for a parameter that is unset or null; omission
of the colon results in a test for a parameter that is only unset.
The form without the colon is correct for path handling so that it
maintains the state in the case that the variable was already set to
an empty value indicating the current working directory.
$ foo=""
$ foo=${foo+$foo:}/opt/somepath
$ echo "$foo"
:/opt/somepath
Note however that an empty path indicating using the current working
directory is almost never desirable. In the case of LD_LIBRARY_PATH
one would never want to have it set to an empty value.
Bob
signature.asc
Description: Digital signature
Re: Fwd: rc.local and systemd
Rainer Dorsch wrote: > Nevertheless I am still wondering why it has the failed status, > rc.local has an hard "exit 0" return code (?) : Look at the first line of /etc/rc.local script. > rd@nanette:/etc$ cat rc.local > #!/bin/sh -e The set -e ^^ here is what sets the -e flag for the shell. Bob signature.asc Description: Digital signature
Re: Mousepad Not Saving Prefs
On Mon, 18 May 2015 17:52:47 +0200 Sven Arvidsson wrote: > On Mon, 2015-05-18 at 11:31 -0400, Stephen R Guglielmo wrote: > > Hi list, > > > > I'm running Debian Stretch/testing (updated daily). I use Xfce4 and > > Mousepad as my GUI text editor. It seems that Mousepad is no longer > > saving my preferences. > [...] > > Any ideas on how to investigate this? > > Looks like mousepad uses dconf for settings, so it could be a problem > with that. > I've been unable to figure out why this is happening. I've tried to investigate myself, but I don't know anything about the dconf system. I've filed a bug report. pgptbjUcOqpm2.pgp Description: OpenPGP digital signature
Re: CLI download interface/tool for Google Images?
On 05/23/2015 09:55 PM, Emanuel Berg wrote: Sven Arvidsson writes: I have seen a couple of different scripts that scrape the image search, for example: https://github.com/tytek2012/givemepics That didn't work, and the style of the program including the documentation tells me it isn't "mature" in more than one sense of the word... Feel free to mature it and show us what you call a mature piece of code. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5560fd59.1000...@rktmb.org
Re: CLI download interface/tool for Google Images?
Mihamina Rakotomandimby writes: > Feel free to mature it and show us what you call > a mature piece of code. I don't have to show a lamer like you anything. The reason I call it immature as a program is that it outputs it logo using Unicode chars for no reason (especially not recommended for a CLI program); it output strings one char at a time which is irritating and absolutely not called for in this type of application the reason for which is speed and convenience; it creates a directory with the name "tmp" instead of using the input data to make a name; it doesn't work; and, it has the following line in the documentation: "gmp hot chicks drinking beer". *plonk* -- underground experts united http://user.it.uu.se/~embe8573 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87617izwxu@debian.uxu
Re: KVM switch: DVI-D, DVI-I or vga?
On 05/23/2015 12:26 PM, Bob Proulx wrote: There is, in my opinion, a significant difference in visual quality between the digital and analog display feeds. I have one machine that can do dual-head. The primary display feed starts as analog DVI-I, is adapted to VGA, goes into the VGA KVM, and then goes into the VGA port of a consumer 22" LED LCD monitor. The secondary display feed starts as DisplayPort (digital), is converted to VGA, and then goes into the VGA port of an older 22" LCD monitor: 1. The primary image looks pretty good for desktop/ server stuff, but shows its shortcomings with LCD monitor test images: http://www.lagom.nl/lcd-test/ 2. The secondary image is not as good as the primary, and the flourescent backlight causes nasty flickering on some of the test images. 3. The motherboard and secondary monitor both have DVI-D ports. If I change the secondary display feed to DVI-D (digital), I don't see *any* difference in the image quality (including flickering). 4. Changing the secondary display feed back to analog, I don't see *any* difference. I can only conclude that there is no difference in image quality between analog and digital display feeds. But, there is a big difference in analog (VGA) vs. digital (DVI) KVM product offerings and prices: 1. My IOGEAR 8-port VGA PS/2 KVM with cables (analog) is $159 on Amazon. 2. For comparison with the digital product, the 8-port VGA KVMP (adds PS/2 or USB connectivity and two shared USB ports) is $364 with cables. 3. The DVI KVMP is $679. While USB or PS/2 connectivity is nice, USB to PS/2 adapters are only $14 each. I don't want or need shared USB peripherals. David -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5561110a.8060...@holgerdanske.com
Re: test if fan is working
Ive installed the xsensors package as well, it only shows me 2 temperature readings, temp1 and core 0, cant see any rpm (Im running lxde). Is there a way for me to manually turn the fan on? thanks, On Sat, May 23, 2015, at 01:16 PM, Haines Brown wrote: > On Sat, May 23, 2015 at 01:01:54PM -0700, Anil Duggirala wrote: > > hello, > > How can I test if my fan is working in Debian?, thanks, > > I've installed the xsensors package. It continually reports the RPM of > three fans. Would this do? > > Haines Brown > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: > https://lists.debian.org/20150523201614.gd30...@engels.historicalmaterialism.info > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1432425565.3982839.276634817.57c2e...@webmail.messagingengine.com
Re: Boot menu entries
On 05/22/2015 04:56 PM, Brian wrote: On Fri 22 May 2015 at 16:24:29 -0500, Emil Payne wrote: On 05/22/2015 03:24 PM, Bob Proulx wrote: $ uname -r 3.9-1-amd64 Don't remove the running kernel nor the latest kernel. Remove all of the others. Bob BTW What is the linux-header? Is that just to compile my own? Do I need to keep these? You are full of questions but very short on saying whether the advice you have been given answers your needs, Delete headers packages too. You put them there and should know whether you need them. As far as I know, I never put them there. I've had to reinstall Debian a few times lately and it kept adding new entries to the boot menu. This is my latest: $> update-grub2 Generating grub.cfg ... Found background image: /usr/share/images/desktop-base/desktop-grub.png Found linux image: /boot/vmlinuz-3.2.0-4-amd64 Found initrd image: /boot/initrd.img-3.2.0-4-amd64 Found linux image: /boot/vmlinuz-3.2.0-4-amd64 Found initrd image: /boot/initrd.img-3.2.0-4-amd64 No volume groups found done I'm a home user and know enough to be able to do some technical things, but sometimes I don't know everything that they do. I try to study the stuff on the web but there is too much conflicting info. Right now the boot menu is more manageable so I'll leave it at that. Thanks everyone. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5561290b.2060...@yahoo.com
No sound at boot
I have a decent setup with an ASUS ROG motherboard (overkill for Linux, I know). I was tooling along nicely, when, after an update (back when Jessie was Testing), sound quit working at boot. Of course, the first thing I tried was root@persephone:~# modprobe snd-hda-intel and that got me sound again. However, I have to run it manually after every boot. What steps do I need to take to get it to load at boot again? Re-Installing ALSA does nothing, of course, and I guess I have no Google skills, because all I can find with Google is advice to reinstall ALSA. MArk -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/556153a7.8080...@allums.top
Re: Problem Running Application with Alias
On Sat, 23 May 2015 14:28:54 -0600 Bob Proulx wrote: > Petter Adsen wrote: > > On Sat, 23 May 2015 09:36:31 -0400 > > > LD_LIBRARY_PATH="/opt/mopac/MOPAC2012.exe:$LD_LIBRARY_PATH" > > > > This is an obvious thing that jumps out at me, this line should be: > > > > LD_LIBRARY_PATH="/opt/mopac:$LD_LIBRARY_PATH" > > > > as LD_LIBRARY_PATH is meant to contain directories where shared > > libraries can be found, not an executable binary. > > I have a small comment concerning the syntax. I am sure you are > correct about the problem. But both of those assume that > $LD_LIBRARY_PATH already exists in the environment. If it does then > fine. Let me use "foo" as a stand-in for the explanation. > > $ foo=/bar > $ foo=/opt/somepath:$foo > $ echo "$foo" > /opt/somepath:/bar > > But if it does not exist then it leaves the environment variable with > a hanging colon at the end. Oooops, sorry. Another thing I should have mentioned last night, but I was getting really tired: On Sat, 23 May 2015 09:36:31 -0400 "Sephen P. Molnar" wrote: > The permissions for /opt/mopac are: drwxrwxrwx ^ In this case, adding /opt/mopac to /etc/ld.so.conf without first fixing up the permissions is probably not a good idea either. The shell expansion I must admit I didn't even think about. Thanks, Bob. Petter PS: What _are_ the security implications of having a PATH set to "/foo/bar:"? -- "I'm ionized" "Are you sure?" "I'm positive." pgpgrT8pCQ5QT.pgp Description: OpenPGP digital signature
Re: Laptops, UEFI, Secure Boot and Debian
On Sat, 23 May 2015 12:46:10 -0700 Patrick Bartek wrote: > On Sat, 23 May 2015, Petter Adsen wrote: > > > On Sat, 23 May 2015 09:04:55 -0700 > > Patrick Bartek wrote: > > > I've read about that, but right now until W10 in its final form is > > > release, nobody really knows for sure. > > > > Well, yes and no. We *do* know that the status has changed from > > "mandatory" to "optional", but whether hardware manufacturers will > > actually remove the ability to turn Secure Boot off remains to be > > seen. > > Yes. I read that. Wonder what Microsoft has up its sleeve? If I were to guess, this is in preparation for at some point in the future requiring Secure Boot to be used, without the ability to turn it off. You know, "think of the children!". > Maybe, this is indicative of W10 being even more insecure than > previous Windows' OSes. Secure Boot itself is not actually such a bad idea, in some circumstances it might be nice to have a fully signed chain. IMHO. In itself, it should help to make Windows *more* secure, but this is hardly the right place for that particular discussion. Nor do I care :) > > > I have no problems with turning Secure Boot off and leaving it > > > off. It's just that I fear that in the future one won't be able > > > to turn it off. And that will really throw a wrench in the Linux > > > community. We'll see. > > > > The Linux Foundation is also examining the possibility of obtaining > > a key that can be used to sign images for distributions (free of > > charge), and there is also work being done on signing a shim that > > will launch a "real" bootloader. As the Perl people lovingly remind > > us, there's more than one way to do it :) > > Where there's a will, there's a way I suppose. Although, instead of a > patch or shim, the threat of a class action lawsuit by Linux > developers might be more effective. Hardware manufacturers will have to take into account the fact that there are a large number of people and organizations that run their machines without Windows, so I don't think there will be a lack of machines that can turn Secure Boot off in the near future. But will it become something to watch out for when buying new hardware? Most certainly, at least for a period of time. I have a sneaking suspicion that it might become a bigger problem for laptop users than for desktop users, although I'm unable to back that up. For those of us who prefer to build their own machines, I think it will be much less of a problem. The cleanest option would probably be to allow the owner of the machine to install his/her own keys in the firmware, and sign the boot image with those. And we still have legacy mode. For now. In my view, a solution for Linux that doesn't work for our BSD brethren and other people would not be good enough - we shouldn't settle for it. I remember all too well how hard it was to get Linux (or BSD, for that matter) up and running with new hardware back in the day, and I don't want a return to that state of things. There may very well be another Linus quietly tinkering away at something that might become the Next Big Thing out there, and it would be a shame if we were to limit hardware to not make that possible. I am also not sure MS really _wants_ to lock Linux/others out of the playing field. If they do, I assume the murmurs of class-action and anti-competition would rise in pitch, and someone might do something that could *really* hurt them. They really should work with the community to come up with a solution that works for everyone before someone forces them to. Petter -- "I'm ionized" "Are you sure?" "I'm positive." pgppYMaPIKOqg.pgp Description: OpenPGP digital signature
Re: No sound at boot
On Sat, 23 May 2015 23:29:27 -0500 Mark Allums wrote: > I have a decent setup with an ASUS ROG motherboard (overkill for > Linux, I know). I was tooling along nicely, when, after an update > (back when Jessie was Testing), sound quit working at boot. Of > course, the first thing I tried was > > > root@persephone:~# modprobe snd-hda-intel > > > and that got me sound again. However, I have to run it manually > after every boot. What steps do I need to take to get it to load at > boot again? Re-Installing ALSA does nothing, of course, and I guess > I have no Google skills, because all I can find with Google is advice > to reinstall ALSA. Take a look in /etc/modules-load.d - you can add a file called, say, "sound.conf" there with the contents: snd-hda-intel That should load that module on boot. I haven't tested it, as I've never had the need to force a module to load in recent years, but it should work. Petter -- "I'm ionized" "Are you sure?" "I'm positive." pgpUtt6KP1gke.pgp Description: OpenPGP digital signature
Re: SOLVED: Re: Logitech M545 button mappings
Ooops! A small correction for people looking through the archives and reading this: On Tue, 19 May 2015 11:50:12 +0200 Petter Adsen wrote: > Create "/etc/udev/hwdb.d/90-logitech-m-545.hwdb" with following: > > # Logitech M545 > keyboard:usb:v046DpC52B* > KEYBOARD_KEY_70007=back > KEYBOARD_KEY_700E7=forward This last line should be: KEYBOARD_KEY_700E3=forward > Then: > > udevadm hwdb --update > > Unplug the receiver and plug it in again, and it works the way $DEITY > intended. Hopefully someone else can use this information. Feel free to contact me if you need help, I've been messing quite thoroughly with this now :) Petter -- "I'm ionized" "Are you sure?" "I'm positive." pgpgIflYr6CnZ.pgp Description: OpenPGP digital signature
Re: No sound at boot
On Sat, 23 May 2015, Mark Allums wrote: . . . Re-Installing ALSA does nothing, of course, and I guess I have no Google skills, because all I can find with Google is advice to reinstall ALSA. . . . hi Mark, I had almost the same problem, although the sound didn't work after modprobe. What do you mean by re-installing? If it is "aptitude reinstall", that didn't work for me. Did you try purge and then install for alsa packages? As I said, that worked for me. cheers, -- Pierre Frenkiel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/alpine.deb.2.11.1505240806210.8...@pfr2.frenkiel-hure.net
Re: Boot menu entries
On Sat, 23 May 2015 20:27:39 -0500 Emil Payne wrote: > On 05/22/2015 04:56 PM, Brian wrote: > > On Fri 22 May 2015 at 16:24:29 -0500, Emil Payne wrote: > > > >> On 05/22/2015 03:24 PM, Bob Proulx wrote: > >>> > >>> $ uname -r > >>> 3.9-1-amd64 > >>> > >>> Don't remove the running kernel nor the latest kernel. Remove > >>> all of the others. > >>> > >>> Bob > >>> > >> > >> BTW What is the linux-header? Is that just to compile my own? Do I > >> need to keep these? > > > > You are full of questions but very short on saying whether the > > advice you have been given answers your needs, > > > > Delete headers packages too. You put them there and should know > > whether you need them. > > > > > As far as I know, I never put them there. I've had to reinstall > Debian a few times lately and it kept adding new entries to the boot > menu. This is my latest: > > $> update-grub2 > Generating grub.cfg ... > Found background > image: /usr/share/images/desktop-base/desktop-grub.png Found linux > image: /boot/vmlinuz-3.2.0-4-amd64 Found initrd > image: /boot/initrd.img-3.2.0-4-amd64 Found linux > image: /boot/vmlinuz-3.2.0-4-amd64 Found initrd > image: /boot/initrd.img-3.2.0-4-amd64 No volume groups found > done > > I'm a home user and know enough to be able to do some technical > things, but sometimes I don't know everything that they do. I try to > study the stuff on the web but there is too much conflicting info. > > Right now the boot menu is more manageable so I'll leave it at that. I should have mentioned this earlier, but there is a package floating around out there called "GRUB Customizer", that you can use to edit the menu. It wouldn't have uninstalled the extraneous kernels, I think, but it can be nice if you are not familiar with GRUBs syntax (which I admit I don't fully understand, either). As a side note, if you are trying to learn something about Linux, two of the best resources I have found are the Arch wiki[1] and the Debian wiki[2]. Another really nice link is the Debian Administrator's Handbook[3]. Following random advice and running scripts found on a forum can be quite dangerous, and often don't tell you *why* you need to do what you need to do. Look for official documentation. Petter [1] https://wiki.archlinux.org/ [2] https://wiki.debian.org/ [3] http://debian-handbook.info/ -- "I'm ionized" "Are you sure?" "I'm positive." pgp6adQT_tpdc.pgp Description: OpenPGP digital signature
Re: No sound at boot
On 05/24/2015 01:15 AM, Pierre Frenkiel wrote: On Sat, 23 May 2015, Mark Allums wrote: . . . Re-Installing ALSA does nothing, of course, and I guess I have no Google skills, because all I can find with Google is advice to reinstall ALSA. . . . hi Mark, I had almost the same problem, although the sound didn't work after modprobe. What do you mean by re-installing? If it is "aptitude reinstall", that didn't work for me. Did you try purge and then install for alsa packages? As I said, that worked for me. cheers, That's what I did, purge and install. Thanks, Mark -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5561704b.6070...@allums.top
Re: No sound at boot
On 05/24/2015 12:58 AM, Petter Adsen wrote: On Sat, 23 May 2015 23:29:27 -0500 Mark Allums wrote: I have a decent setup with an ASUS ROG motherboard (overkill for Linux, I know). I was tooling along nicely, when, after an update (back when Jessie was Testing), sound quit working at boot. Of course, the first thing I tried was root@persephone:~# modprobe snd-hda-intel and that got me sound again. However, I have to run it manually after every boot. What steps do I need to take to get it to load at boot again? Re-Installing ALSA does nothing, of course, and I guess I have no Google skills, because all I can find with Google is advice to reinstall ALSA. Take a look in /etc/modules-load.d - you can add a file called, say, "sound.conf" there with the contents: snd-hda-intel That should load that module on boot. I haven't tested it, as I've never had the need to force a module to load in recent years, but it should work. Petter Didn't work. Nor did adding snd-hda-intel line to /etc/modules. Any more suggestions? I'm running Jessie. Have been since Jessie was testing, about three months after the release of Wheezy. So it's seen a lot of changes, the biggest of which was the transition from sysvinit to systemd. I should have fixed it a lot sooner, but as long as I could fix it by running modprobe, I wasn't in a big hurry. Anyway, if this had worked, it feels like a workaround, and isn't really getting to the actual cause of the problem. So, any more suggestions are welcome. Thanks, Mark -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5561721d.80...@allums.top
Re: No sound at boot
On 05/24/2015 09:39 AM, Mark Allums wrote: > > > On 05/24/2015 12:58 AM, Petter Adsen wrote: >> On Sat, 23 May 2015 23:29:27 -0500 >> Mark Allums wrote: >> >>> I have a decent setup with an ASUS ROG motherboard (overkill for >>> Linux, I know). I was tooling along nicely, when, after an update >>> (back when Jessie was Testing), sound quit working at boot. Of >>> course, the first thing I tried was >>> >>> >>> root@persephone:~# modprobe snd-hda-intel >>> >>> >>> and that got me sound again. However, I have to run it manually >>> after every boot. What steps do I need to take to get it to load at >>> boot again? Re-Installing ALSA does nothing, of course, and I guess >>> I have no Google skills, because all I can find with Google is advice >>> to reinstall ALSA. >> Take a look in /etc/modules-load.d - you can add a file called, say, >> "sound.conf" there with the contents: >> >> snd-hda-intel >> >> That should load that module on boot. I haven't tested it, as I've >> never had the need to force a module to load in recent years, but it >> should work. >> >> Petter >> > > Didn't work. Nor did adding snd-hda-intel line to /etc/modules. > > Any more suggestions? I'm running Jessie. Have been since Jessie was > testing, about three months after the release of Wheezy. So it's seen a > lot of changes, the biggest of which was the transition from sysvinit to > systemd. I should have fixed it a lot sooner, but as long as I could fix > it by running modprobe, I wasn't in a big hurry. Anyway, if this had > worked, it feels like a workaround, and isn't really getting to the > actual cause of the problem. So, any more suggestions are welcome. > You can try to run alsactl init as root: # alsactl init HTH Kind regards Georgi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/556174c5.5000...@oles.biz
