Re: Why debian put ~/bin beginning of $PATH
On 09/08/17 05:11, spp mg wrote: > In the ~/.profile has below default setting: > > -- > # set PATH so it includes user's private bin if it exists > if [ -d "$HOME/bin" ] ; then > PATH="$HOME/bin:$PATH" > fi > -- > > Why put ~/bin beginning ? So that your own stuff has precedence... > Is that dangerous ? Not really. Only you or a system administrator would have write access to ~/bin. What makes you think it might be dangerous? -- E: j...@jj5.net P: +61 4 3505 7839 W: https://www.jj5.net/ <>
Disabled audio devices
Hi there. Suddenly my audio device isn't working. I didn't change anything (well, not on purpose). I'm running Debian stretch. If I click System Settings -> Multimedia -> Audio and Video then I see something like this: https://www.jj5.net/file/2017-08-05-220654/disabled-audio-devices.png Can anyone suggest how I re-enable audio..? Regards, John Elliot V -- E: j...@jj5.net P: +61 4 3505 7839 W: https://www.jj5.net/ <>
Re: System locks up while moving file
On 25/06/17 20:13, to...@tuxteam.de wrote: > You might try to play around with ionice. Something along the lines of > > ionice -c 3 mv /this/path /that/path Thanks. I gave that a try. Didn't seem to help much. But... On 25/06/17 20:19, Reco wrote: > A known problem aka Linux 12309 bug. > > Try this: > > sysctl -w vm.dirty_ratio=5 > sysctl -w vm.dirty_background_ratio=5 > > If it helps, put these kernel tunables into /etc/sysctl.d somewhere. I did that a few weeks after trying the previous suggestion for a while, and it seems to have solved the issue. Thanks! -- E: j...@jj5.net P: +61 4 3505 7839 W: https://www.jj5.net/ <>
Re: How did you update to stretch?
On 27/06/17 05:39, Brian wrote: > It was. I am a creature of habit. I still reboot between upgrade and > dist-upgrade when I eventually upgrade a machine from one distribution > to another. Do you ever use configuration management tools like Salt Stack? https://saltstack.com/ I'm just starting out with Salt, and I haven't figured out what you do if you want to put a reboot between various configuration steps... -- E: j...@jj5.net P: +61 4 3505 7839 W: https://www.jj5.net/ <>
Sound issue WAS: Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading
On 27/06/17 03:16, John Elliot V wrote: > Hmm. I re-enabled hyper-threading (to test) and sound didn't come back. After a number of false starts I was able to restore audio by: KDE -> System Settings -> Multimedia (Hardware) -> Audio and Video -> Audio Hardware Setup Then in the Hardware section changing Profile from: Digital Stereo (IEC958) Output + Analog Stereo Input To: Digital Stereo (HDMI2) Output + Analog Stereo Input I'm not sure what changed that required me to make this change. Anyway, happy that sound is working again for me. Regards, John Elliot V -- E: j...@jj5.net P: +61 4 3505 7839 W: https://www.jj5.net/ <>
Re: How did you update to stretch?
On 27/06/17 03:06, Greg Wooledge wrote: > On Tue, Jun 27, 2017 at 03:04:30AM +1000, John Elliot V wrote: >> Can I ask why you did the apt-get upgrade before the apt-get >> dist-upgrade? Why not just go straight for apt-get dist-upgrade..? > > Probably because (s)he read the release notes Oh. Right. Thanks. :) -- E: j...@jj5.net P: +61 4 3505 7839 W: https://www.jj5.net/ <>
Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading
On 27/06/17 02:47, John Elliot V wrote: > I disabled hyper-threading in my BIOS in response to this advisory (I > have an i7-7700K). Now I get weird graphical artifacts in drop-down > lists in KDE (they flash between black and white background) and sound > has stopped working on my system. Can anyone guess why that might be > happening? I might try re-enabling hyper-threading to see if things go > back to normal... Hmm. I re-enabled hyper-threading (to test) and sound didn't come back. So I disabled hyper-threading again. Before I disabled hyper-threading the first time I tried updating my BIOS, and in order to do that my BIOS reconfigured itself to enable some networking features so it could update the BIOS over the Internet. Turned out my BIOS was already at the latest version (details are here [1]). I'm not sure how to diagnose a "no sound" issue. I've checked all the volume controls I know about, and nothing is mute and/or low volume. Sound was working this morning, and now, after I changed my hyper-threading settings, it's not. Dunno what happened or why. Totally stumped. Regards, John Elliot V [1] https://www.progclub.org/pipermail/programming/2017-June/002892.html -- E: j...@jj5.net P: +61 4 3505 7839 W: https://www.jj5.net/ <>
Re: How did you update to stretch?
On 26/06/17 23:12, Jonathan Dowland wrote: >> So, how are your experiences? Did you end in the same issues as I ended? > > Nope, I read the release notes and simply did > > (correct sources.list) > apt-get update > apt-get upgrade > apt-get dist-upgrade > (pending reboot) Can I ask why you did the apt-get upgrade before the apt-get dist-upgrade? Why not just go straight for apt-get dist-upgrade..? -- E: j...@jj5.net P: +61 4 3505 7839 W: https://www.jj5.net/ <>
Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading
I disabled hyper-threading in my BIOS in response to this advisory (I have an i7-7700K). Now I get weird graphical artifacts in drop-down lists in KDE (they flash between black and white background) and sound has stopped working on my system. Can anyone guess why that might be happening? I might try re-enabling hyper-threading to see if things go back to normal... Regards, John Elliot V -- E: j...@jj5.net P: +61 4 3505 7839 W: https://www.jj5.net/ <>
System locks up while moving file
Hey there. Maybe someone can help me with this. I'm running Debian 9.0 (stretch). I have a few scripts which periodically create and then move a file from my 1TB M.2 drive to a MD RAID1 device comprised of 2x 6TB Seagate IronWolf drives. Full details are here [1]. My disks look something like this: jj5@tact:~$ df -h Filesystem Size Used Avail Use% Mounted on /dev/md0469G 86G 378G 19% / /dev/md15.5T 4.0T 1.6T 73% /data /dev/nvme0n1p1 931G 78G 853G 9% /data/fast An example of the move command which locks everything up is: mv /data/fast/temp/blob-tact.tgz \ /data/temp/blob-tact.tgz.8157-12003.tmp So while this mv command is being processed my mouse doesn't respond, my KDE Plasma session locks up, everything grinds to a halt. There seems to be plenty of RAM available, and plenty of CPU. So must be some I/O thing..? Anyway, I'm a bit stumped. I haven't tried running the mv command with nice, because it doesn't seem to be a CPU thing... but maybe I should..? Anyone got any ideas about how to keep my system responsive while the mv command is processed? Regards, John Elliot V [1] https://www.jj5.net/sixsigma/Workstation#Disk -- E: j...@jj5.net P: +61 4 3505 7839 W: https://www.jj5.net/ <>
Re: Debian hardware compatibility
On 20/04/17 01:14, Joshua Schaeffer wrote: > I would recommend the 850 Evo vs the 850 Pro Thanks for the tip. I had considered the Evo but this: https://www.kosagi.com/forums/viewtopic.php?id=421 had me a little spooked. I've already parted with my money for the Pro. I've made bigger mistakes in life... :) -- E: j...@jj5.net P: +61 4 3505 7839 W: https://www.jj5.net/ <>
Re: Debian hardware compatibility
On 20/04/17 10:33, Ben Caradoc-Davies wrote: > why not just install stretch from RC3? stretch is close to release. Sounds like a good idea! Thanks Ben. Will stretch RC3 smoothly transition to stable (with an apt-get dist-upgrade) when stretch is released? > HD 630 iGPU is working fine for me with XFCE on an i7 7700 with one HDMI > output on 4.9.18-1 amd64. I am on sid, but stretch has the same kernel. > I purged xserver-xorg-video-intel because the modesetting driver is > preferred for modern hardware. Will that apply to me? I.e. I should purge xserver-xorg-video-intel? > Asus UEFI BIOS (H110I-PLUS BIOS 3202) defaults to incorrect turbo boost > multipliers but I was able to manually set the correct "Per CPU" values > in the BIOS. For a 7700K, these should be 45/44/44/44 if you are not > overclocking (base clock 100MHz): > https://en.wikipedia.org/wiki/Kaby_Lake OK, cool, thanks. ...and what if I am overclocking? I've never overclocked a system before, but I heard I could safely overclock my new CPU to 5GHz, which sounded pretty exciting..! :P -- E: j...@jj5.net P: +61 4 3505 7839 W: https://www.jj5.net/ <>
Debian hardware compatibility
I'm getting a new workstation. Proposed specs are here: https://au.pcpartpicker.com/list/7MCfjc I tried to find out if my new hardware would run Debian stable, but couldn't confirm. CPU is Intel Core i7-7700K on an Asus STRIX Z270F mobo. I'm planning to drive two monitors from the onboard graphics controller, one via DVI the other via HDMI. Will Debian (w/ KDE Plasma) run on my new kit, does anybody know? Cheers, John. -- E: j...@jj5.net P: +61 4 3505 7839 W: https://www.jj5.net/ <>
Re: Which package for reportbug?
On 15/12/16 21:30, John Elliot V wrote: > I'm having an issue logging into my KDE Plasma desktop, > which package should I file the bug under? My apologies. After a little more reading I discovered this: https://www.debian.org/Bugs/Reporting#findpkgver then this: jj5@orac:~$ dpkg --search /etc/init.d/kdm kdm: /etc/init.d/kdm So I will file the bug under 'kdm' (although I'm not sure that is strictly correct). Regards, John Elliot V <>
Which package for reportbug?
Hi there. I'm running Debian jessie with a KDE Plasma desktop, and after I did an apt-get dist-upgrade today when I logged into KDE Plasma after rebooting I got a blank screen (with the Debian logo in the bottom right). Eventually I figured out that if I run: sudo /etc/init.d/kdm restart that I can log into KDE. Which is good, because now I can send you this email. I've been using Debian (and similar) for a long time, but I haven't submitted a Debian bug report before. I figured out that I'm supposed to use the 'reportbug' command. I ran reportbug and it asked me which package the problem relates to: Please enter the name of the package in which you have found a problem, or type 'other' to report a more general problem. If you don't know what package the bug is in, please contact debian-user@lists.debian.org for assistance. So, since I don't know what package to nominate I'm emailing debian-user as instructed! I'm having an issue logging into my KDE Plasma desktop, which package should I file the bug under? Thanks for your help. Regards, John Elliot V <>
