Re: swap-fle on arm64, need to disable, how?
Hi Gene, please check explanations in this blog: https://www.dwarmstrong.org/zram-linuxmint/ HTH Matthias gene heskett schrieb am Sa., 30. Sept. 2023, 19:51: > On 9/30/23 13:28, Matthias Böttcher wrote: > > sudo dphys-swapfile swapoff > > sudo systemctl stop dphys-swapfile.service > > sudo systemctl disable dphys-swapfile.service > > > > . > Looks familiar but none of that is installed > cnc@rpi4:/etc$ sudo dphys-swapfile swapoff > sudo: dphys-swapfile: command not found > cnc@rpi4:/etc$ sudo systemctl stop dphys-swapfile.service > Failed to stop dphys-swapfile.service: Unit dphys-swapfile.service not > loaded. > cnc@rpi4:/etc$ sudo systemctl disable dphys-swapfile.service > Failed to disable unit: Unit file dphys-swapfile.service does not exist. > > What I'm trying to do is get rid of zram0, which is being used as swap, > and sub real swap on an SSD in its place. And zram0 is not listed in > fstab, but swapon finds it. > > Thank you, Matthias Böttcher > > Cheers, Gene Heskett. > -- > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author, 1940) > If we desire respect for the law, we must first make the law respectable. > - Louis D. Brandeis > Genes Web page <http://geneslinuxbox.net:6309/> > >
Re: swap-fle on arm64, need to disable, how?
sudo dphys-swapfile swapoff sudo systemctl stop dphys-swapfile.service sudo systemctl disable dphys-swapfile.service
Re: Debian 12 kernel NFS server doesn't listen on port 2049 UDP
On Sat, Jul 29, 2023 at 05:44:59PM +0100, piorunz wrote: > Edit /etc/nfs.conf file: > [nfsd] > udp=y > > then: > sudo systemctl restart nfs-server Yes, that fixed my NFS problem. Thank you very much -- Matthias Scheler http://zhadum.org.uk/
Debian 12 kernel NFS server doesn't listen on port 2049 UDP
Hello, after upgrading one of my systems from Debian 11 to 12 the kernel NFS server doesn't seem to accept NFS requests over UDP on port 2049 anymore: >rpcinfo -p | grep nfs 133 tcp 2049 nfs 134 tcp 2049 nfs 1002273 tcp 2049 nfs_acl This causes problems for a non-Linux NFS client whose automounter tries to perform the mount over UDP. Is there a way to re-enable the UDP port? Kind regards -- Matthias Scheler http://zhadum.org.uk/
Re: fstrim(8) Recommendation
Am Fr., 13. Jan. 2023 um 03:45 Uhr schrieb John Conover : > > I'm installing an SSD replacement for an HD in a small 24/7 mail > server. > > I would appreciate suggestions for the most reliable way to do > fstrim(8). Reliability is more important than speed, and the machine > will require a swap partition. > > Thanks, > > John Hi John, take a look at the systemd units fstrim.timer fstrim.service e2scrub_all.service e2scrub_all.timer e2scrub_reap.service Trimming swap partitions is not provided. HTH Matthias
Re: Wear levelling on micro-sd cards
> How do I tell the card that the free space in the VG really is free? blkdiscard
Re: auth log full with
Am So., 14. Aug. 2022 um 16:42 Uhr schrieb Reco : > whois, geoiplookup, even https://bgp.he.net . > Whatever works, basically. > Last one is my favorite as it shows all IP blocks assigned to AS. > Really helpful with spammer nests such as outlook.com (AS8075) or > DigitalOcean (AS14061). > > > Is there a Debian packet? > > For the first two - sure. > You'll need whois and geoip-bin. Installing iptables is assumed. Thanks for your reply, it bumps me in the right direction. Matthias
Re: auth log full with
Am So., 14. Aug. 2022 um 09:51 Uhr schrieb Reco : > Personally I don't use fail2ban for sshd. Because why bother with > userspace (written in python too, yuck) if the kernel does the same job? > I.e. block M$ AS, China Telecom AS and maybe add Eastern Europe to the > mix, and you've just reduced the number of offending logins by two > orders of magnitude. Hi Reco, how do I block these ip ranges? Which source can I use to determine the geo location of ip addresses? Is there a Debian packet? Thanks for your help. Matthias
Re: Setting up Mailman3 under Debian (using packages)
Hello, [Sorry for the delayed response. I only got around to try this out now.] On Fri, Jul 01, 2022 at 09:35:33PM +0200, Pierre-Elliott Bécue wrote: > > Using the Debian 10 packages I can get to a point where the web interface > > is up and running and I get to a login prompt. But I have no idea how > > to setup the admin account or how to change the admin password if > > an admin account has automatically been created. > > > > Any advise would be appreciated. > > > > Thanks in advance > > The web UI is a django application. During the installation of the > mailman3-web package, you should have been prompted to give the > postorius superuser password. That doesn't happen on my system. I've completely wiped any traces of Djano (including config) and installed "mailman3-full" which also installed "mailman3-web". I got prompted twice for the database that I want to use (I chose "sqlite" both times) but I was never asked for a super password. And the "python3-django-postorius" definitely got installed: Setting up python3-django-mailman3 (1.2.0-3) ... Setting up python3-django-postorius (1.2.4-1+deb10u1) ... Setting up python3-django-hyperkitty (1.2.2-1+deb10u1) ... Setting up mailman3-web (0+20180916-8) ... dbconfig-common: writing config to /etc/dbconfig-common/mailman3-web.conf > If you have deactivated debconf or provided an empty password, then no > superuser has been created. I've not deactivated "debconf" as the prompts for the database prove. But there is no prompt for the super user password. > In that case, you can use django-admin binary command to set a superuser > password. > > See /usr/share/doc/mailman3-web/README.Debian.gz for more intel. Running "dpkg-reconfigure mailman3-web" manually gave me the dialog for setting up the Postorius admin user. Kind regards -- Matthias Scheler http://zhadum.org.uk/
Setting up Mailman3 under Debian (using packages)
Hello, I'm trying to migrate the mailing lists on my server from legacy Mailan to Mailman 3 to be able to finally update the system from Buster to Bullseye. I've found guides how to migrate the configuration and lists but I haven't found a guide how to complete the basic installation on Debian. Using the Debian 10 packages I can get to a point where the web interface is up and running and I get to a login prompt. But I have no idea how to setup the admin account or how to change the admin password if an admin account has automatically been created. Any advise would be appreciated. Thanks in advance -- Matthias Scheler http://zhadum.org.uk/
Re: Slab Unreclaimable is continually growing
Just for reference: check_mk_agent caused the endlessly growing of SUnreclaim in /proc/meminfo and similary vm_area_struct in slabtop if the typical conditions are met in a Debian Buster with check-mk-agent: - Debian 10 Buster systemd241-7~deb10u1 amd64 Kernel 4.19.67-2, but with newer kernels too. - check-mk-agent my version is 1.5.0p18, but with newer versions too - check_mk.socket is active in systemd and used via 6556/tcp - one or more checks are cached for example ntp in check_mk_agent or the simple echo "0 myservice - OK: This is my custom output" tribe29 as creators of checkmk is aware of this, has observed it only in Debian Buster and recommends in Buster xinetd for the listening socket for its agent. https://lists.mathias-kettner.de/pipermail/checkmk-en/2019-September/028675.html https://lists.mathias-kettner.de/pipermail/checkmk-en/2019-September/028676.html Matthias Am Sa., 27. Juli 2019 um 11:59 Uhr schrieb Matthias Böttcher : > > On Fri, Jul 26, 2019 at 10:12:20PM +0300, Reco wrote: > > On Fri, Jul 26, 2019 at 08:55:19PM +0200, Matthias Böttcher wrote: > > [...] > > > > and additionally I stopped the socket for the Check_MK agent: > > > > > > sudo systemctl stop check_mk.socket > > > > I do not know this one. What's its purpose? Monitoring, backup, > > something else? Is there a source available. > > Checkmk, formerly Check_MK, is a monitoring software[1]. > I am using the Checkmk Raw Edition (CRE) open-source. > Per default it gets data from an agent on a host with connect to 6556/tcp > every 60 seconds. All counters are fetched in one connect, > nothing is sent to the host. The agent for Linux is one big bash script[2]. > > The deb with the agent brings systemd integration: > > > $ cat "/etc/systemd/system/check_mk@.service" > > # systemd service definition file > [Unit] > Description=Check_MK > > [Service] > ExecStart=/usr/bin/check_mk_agent > KillMode=process > > User=root > Group=root > > StandardInput=socket > > > $ cat /etc/systemd/system/check_mk.socket > > # systemd socket definition file > [Unit] > Description=Check_MK Agent Socket > > [Socket] > ListenStream=6556 > Accept=true > > [Install] > WantedBy=sockets.target > > > With check_mk.socket started, SUnreclaim and vm_area_struct are growing > endlessly. So I will investigate the checkmk agent. > > > Reco > > Reco, Thank you for your explanations and bumping me in the right direction. > > Matthias > > [1] https://checkmk.com/ > [2] https://github.com/tribe29/checkmk/blob/master/agents/check_mk_agent.linux >
Re: Slab Unreclaimable is continually growing
On Fri, Jul 26, 2019 at 10:12:20PM +0300, Reco wrote: > On Fri, Jul 26, 2019 at 08:55:19PM +0200, Matthias Böttcher wrote: [...] > > and additionally I stopped the socket for the Check_MK agent: > > > > sudo systemctl stop check_mk.socket > > I do not know this one. What's its purpose? Monitoring, backup, > something else? Is there a source available. Checkmk, formerly Check_MK, is a monitoring software[1]. I am using the Checkmk Raw Edition (CRE) open-source. Per default it gets data from an agent on a host with connect to 6556/tcp every 60 seconds. All counters are fetched in one connect, nothing is sent to the host. The agent for Linux is one big bash script[2]. The deb with the agent brings systemd integration: $ cat "/etc/systemd/system/check_mk@.service" # systemd service definition file [Unit] Description=Check_MK [Service] ExecStart=/usr/bin/check_mk_agent KillMode=process User=root Group=root StandardInput=socket $ cat /etc/systemd/system/check_mk.socket # systemd socket definition file [Unit] Description=Check_MK Agent Socket [Socket] ListenStream=6556 Accept=true [Install] WantedBy=sockets.target With check_mk.socket started, SUnreclaim and vm_area_struct are growing endlessly. So I will investigate the checkmk agent. > Reco Reco, Thank you for your explanations and bumping me in the right direction. Matthias [1] https://checkmk.com/ [2] https://github.com/tribe29/checkmk/blob/master/agents/check_mk_agent.linux
Re: Slab Unreclaimable is continually growing
Reco : > > Hi. > > On Wed, Jul 24, 2019 at 06:54:42PM +0200, Matthias Böttcher wrote: > > OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME > > 307534 304741 99%0,20K 16186 19 64744K vm_area_struct > > 14280 14274 99%3,69K 17858 57120K task_struct > > 178048 152224 85%0,25K 11128 16 44512K filp > > 8536 8536 100%4,00K 10678 34144K kmalloc-4096 > > 14640 14640 100%2,06K976 15 31232K sighand_cache > > > > How can I detect what is eating up my memory in SUnreclaim (slab > > unreclaimable)? > > You did it already. > "vm_area_struct" is a kernel structure for anonymous memory allocations. > "task_struct" is a kernel structure for maintaining process execution. > "filp" is a kernel structure for virtual memory. > > My guess is - a small number of processes that constantly allocate > memory in small numbers by executing brk(2) or its modern equivalents. > > Or a relatively large number of short-lived processes. > > > I'd start with "pidstat -rl 1 10". Now with an uptime of 2 days, 9 hours all counters of slabtop are growing no more. $ slabtop --sort c --once | head -n12 Active / Total Objects (% used): 10336938 / 10484768 (98,6%) Active / Total Slabs (% used) : 328327 / 328327 (100,0%) Active / Total Caches (% used) : 98 / 124 (79,0%) Active / Total Size (% used) : 2443615,58K / 2479644,41K (98,5%) Minimum / Average / Maximum Object : 0,01K / 0,24K / 8,00K OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME 308520 307456 99%1,05K 20568 15329088K ext4_inode_cache 1285388 1269730 98%0,20K 67652 19270608K vm_area_struct 61712 61692 99%3,69K 77148246848K task_struct 765472 649628 84%0,25K 47842 16191368K filp 36088 36083 99%4,00K 45118144352K kmalloc-4096 What I saw with "pidstat -rl 1 10" was systemd-journald and nmbd, so I did: sudo apt purge samba # Samba was not needed sudo systemctl stop systemd-journald-dev-log.socket \ systemd-journald-audit.socket systemd-journald.socket and additionally I stopped the socket for the Check_MK agent: sudo systemctl stop check_mk.socket OK, these are 3 changes at once, so I have to figure out which change does it. Matthias
Re: Slab Unreclaimable is continually growing
Shahryar Afifi : > > What happens when you run sync in terminal? sync exits immediately and slabtop gives the same output like before sync.
Slab Unreclaimable is continually growing
Hi list, my buster is using more and more memory until the oom-killer is invoked. This occurs after two days of uptime, but no process is using that memory. Slab seems suspicious to me. Kernel: 4.19.37-5+deb10u1 (2019-07-19) x86_64 from /proc/meminfo after 8 hours uptime: MemTotal:4041116 kB MemFree: 3165992 kB MemAvailable:3246560 kB Buffers: 30144 kB Cached: 240356 kB SwapCached:0 kB Active: 162056 kB Inactive: 144268 kB SwapTotal: 4194300 kB SwapFree:4194300 kB Slab: 521364 kB SReclaimable: 66776 kB SUnreclaim: 454588 kB My Top 5 in slabtop: $ sudo slabtop --sort c --once | head -n12 Active / Total Objects (% used): 2234301 / 2270100 (98,4%) Active / Total Slabs (% used) : 70832 / 70832 (100,0%) Active / Total Caches (% used) : 98 / 124 (79,0%) Active / Total Size (% used) : 501034,52K / 509459,17K (98,3%) Minimum / Average / Maximum Object : 0,01K / 0,22K / 8,00K OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME 307534 304741 99%0,20K 16186 19 64744K vm_area_struct 14280 14274 99%3,69K 17858 57120K task_struct 178048 152224 85%0,25K 11128 16 44512K filp 8536 8536 100%4,00K 10678 34144K kmalloc-4096 14640 14640 100%2,06K976 15 31232K sighand_cache Active / Total Size is growing continually about 60 MB per hour. How can I detect what is eating up my memory in SUnreclaim (slab unreclaimable)? Thanks in advance Matthias Böttcher
Einstellungen in Kontact
Hallo ich habe am Montag von Jessie auf Stretch aktualisiert. Kontact läuft soweit bis jetzt stabil. Übernahme der alten Mails hat auch sauber funktioniert. Meinen IMAP-Zugang fürs Versenden musste ich allerdings neu machen. Was da jetzt an den Einstellungen anders ist verstehe ich nicht. Aber das ist nicht das Problem, sondern: Kontact hat links (bei mir) am Rand die Ordnerübersicht. Als zusätzliche Spalten kann man die Anzahl der gelesenen, der ungelesenen und die Größe der Mails einstellen. Das habe ich gemacht, aber nach jedem Start von Kontact muss ich das Fenster mit der Ordnerübersicht breiter ziehen um die Spalten mit den Zahlen zu sehen. An welcher Stell muss ich hier schrauben, damit das dauerhaft so bleibt, wie ich es einstelle? System: Debian GNU/Linux 9.0 (stretch) Ich blick hier nicht durch, was ist das jetzt für eine KDE-Version? KDE Frameworks 5.28.0 Qt 5.7.1 (kompiliert gegen 5.7.1) KDE Runtime (lt aptitude) 4.16.08.3-2 -- Mit freundlichen Grüßen Matthias Müller (Benutzer #439779 im Linux-Counter http://counter.li.org) PS: Bitte senden Sie als Antwort auf meine E-Mails reine Text-Nachrichten! signature.asc Description: This is a digitally signed message part.
Migrationsassistent von Kwallett
Hallo ich habe am Montag von Jessie auf Stretch aktualisiert. Bei jeder Anmeldung am System startet dieser bescheuerte Migrationsassistent. Wie kann man den dauerhaft ruhig stellen. Es ist ja ganz schön, das er was migrieren will, aber was? Und warum jedes mal wieder? System: Debian GNU/Linux 9.0 (stretch) Ich blick hier nicht durch, was ist das jetzt für eine KDE-Version? KDE Frameworks 5.28.0 Qt 5.7.1 (kompiliert gegen 5.7.1) KDE Runtime (lt aptitude) 4.16.08.3-2 -- Mit freundlichen Grüßen Matthias Müller (Benutzer #439779 im Linux-Counter http://counter.li.org) PS: Bitte senden Sie als Antwort auf meine E-Mails reine Text-Nachrichten! signature.asc Description: This is a digitally signed message part.
Hintergrund beim Anmeldebildschirm
Hallo ich habe am Montag von Jessie auf Stretch aktualisiert. Dabei habe ich kdm als Anmeldemanager beibehalten. Der Hintergrund ist jetzt eine intensiv blaue (Augenschmerzen fördernde) Fläche. Wie kann ich hier ein Bild hinbekommen.? System: Debian GNU/Linux 9.0 (stretch) Ich blick hier nicht durch, was ist das jetzt für eine KDE-Version? KDE Frameworks 5.28.0 Qt 5.7.1 (kompiliert gegen 5.7.1) KDE Runtime (lt aptitude) 4.16.08.3-2 -- Mit freundlichen Grüßen Matthias Müller (Benutzer #439779 im Linux-Counter http://counter.li.org) PS: Bitte senden Sie als Antwort auf meine E-Mails reine Text-Nachrichten! signature.asc Description: This is a digitally signed message part.
Stretch: FontAwesome not properly installed / not working?
Hello I've got the following issue: When I visit the font-awesome cheat sheet [1] and copy-paste a character (like , or fa-envelope []) into gnome-shell or into another program, e.g. gedit, or thunderbird, it shows up as another character or the box with the hexvalues in them. When I use gnome-font-viewer, I do see fontawesome installed and I can view symbols. When I use charmap I also see it there. I've got fontawesome installed (I even re-installed it after the upgrade) and updated fc-cache $ apt list fonts-font-awesome Listing... Done fonts-font-awesome/stable,now 4.7.0~dfsg-1 all [installed] $ fc-list FontAwesome /usr/share/fonts/opentype/font-awesome/FontAwesome.otf: FontAwesome:style=Regular /usr/share/fonts/woff/font-awesome/fontawesome-webfont.woff: FontAwesome:style=Regular /usr/share/fonts/truetype/font-awesome/fontawesome-webfont.ttf: FontAwesome:style=Regular What could be the issue? $ xlsfonts | grep -i awesome doesn't show it, but neither does it show another installed font (RobotoMono) that works in gedit and gnome-shell. What else could I check? -Hermi [1] http://fontawesome.io/cheatsheet/ signature.asc Description: OpenPGP digital signature
Re: The same environment variables everywhere
Am 26.02.2017 um 13:26 schrieb Teemu Likonen: > I would like to hear some ideas on how to set various environment > variables (PATH, MANPATH, EDITOR etc.) in one place that would make them > effective everywhere. My "everywhere" means: > > - X session started through lightdm and ~/.xsession script > - Linux console login (bash) > - user's systemd services Put them into /etc/environment. Matthias
Re: kernel performance: 3.16 vs. 4.9
Am 06.02.2017 um 00:12 schrieb Ben Caradoc-Davies: > On 06/02/17 09:59, Matthias Bodenbinder wrote: >> Am 05.02.2017 um 09:03 schrieb Matthias Bodenbinder: >>> Hi, >>> I have upgraded my PC to newest chipset and CPU: Kaby Lake, Z270 with >>> i7-7700K. >>> Out of curiosity I did a kernel benchmark. Comparing darktable performance >>> with kernel 3.16.0-4-amd64 and 4.9.0-1-amd64. I use the following command >>> to run darktable: >>> darktable-cli test.CR2 test.jpg --core -d perf -d opencl >>> The results are surprising for me. Kernel 4.9 very much outperformance >>> kernel 3.16. Here are the results with and without opencl (using a Geforce >>> GTX750TI): >>> kernel 3.16kernel 4.9 >>> with opencl16 s9 s >>> without opencl120 s23 s >>> Without opencl, that is with pure CPU performance, the difference is a >>> factor of 5! >>> Why is that? What am I missing? I can hardly believe that kernel 4.9 is so >>> much faster. >>> Matthias >> Hi, >> the issue is solved. It is related to the CPU frequency driver acpi-cpufreq >> vs. intel_pstate and the governor powersave vs. >> performance. >> With kernel 4.9 the default CPU frequency driver for my hardware is >> intel_pstate. And I had the governor set to "powersave" in >> /etc/default/cpufrequtils. I do not see big performance differences between >> "powersave" and "performance" settings with intel_pstate. >> But with kernel 3.16 the default CPU frequency driver is acpi-cpufreq. With >> my settings in /etc/default/cpufrequtils it running in "powersave" mode >> which is giving this dramatic performance collapse. With governor "ondemand" >> or "performance" kernel 3.16 is as fast as kernel 4.9. >> Sorry for the confusion. >> Matthias > > Matthias that is very interesting. Your findings seem different to those > reported on Phoronix; no doubt the p-state driver is undergoing some changes > to improve Kaby Lake support: > http://www.phoronix.com/scan.php?page=article&item=pstate-cpufreq-kbl&num=1 > http://www.phoronix.com/scan.php?page=article&item=pstate-cpufreq-kbl&num=2 > https://www.phoronix.com/scan.php?page=news_item&px=P-State-Kabylake-Patching > > Kind regards, > The phoronix article only compares the performance governors. It does not investigate the performance decrease with acpi-cpufreq+powersave. Based on the articles I made another test with kernel 4.9 + acpi-cpufreq + performance and compared it to kernel 4.9 + intel_pstate + performance. The difference after several runs is minimal 23-24 s for intel_pstate vs. 22 s for acpi-cpufreq. Not sure if that is meaningful but it seems to support what phoronix is reporting. Matthias
Re: kernel performance: 3.16 vs. 4.9
Am 05.02.2017 um 09:03 schrieb Matthias Bodenbinder: > Hi, > > I have upgraded my PC to newest chipset and CPU: Kaby Lake, Z270 with > i7-7700K. > > Out of curiosity I did a kernel benchmark. Comparing darktable performance > with kernel 3.16.0-4-amd64 and 4.9.0-1-amd64. I use the following command to > run darktable: > darktable-cli test.CR2 test.jpg --core -d perf -d opencl > > The results are surprising for me. Kernel 4.9 very much outperformance kernel > 3.16. Here are the results with and without opencl (using a Geforce GTX750TI): > > kernel 3.16 kernel 4.9 > with opencl 16 s9 s > without opencl120 s 23 s > > Without opencl, that is with pure CPU performance, the difference is a factor > of 5! > > Why is that? What am I missing? I can hardly believe that kernel 4.9 is so > much faster. > > Matthias > > > > Hi, the issue is solved. It is related to the CPU frequency driver acpi-cpufreq vs. intel_pstate and the governor powersave vs. performance. With kernel 4.9 the default CPU frequency driver for my hardware is intel_pstate. And I had the governor set to "powersave" in /etc/default/cpufrequtils. I do not see big performance differences between "powersave" and "performance" settings with intel_pstate. But with kernel 3.16 the default CPU frequency driver is acpi-cpufreq. With my settings in /etc/default/cpufrequtils it running in "powersave" mode which is giving this dramatic performance collapse. With governor "ondemand" or "performance" kernel 3.16 is as fast as kernel 4.9. Sorry for the confusion. Matthias
Re: kernel performance: 3.16 vs. 4.9
Am 05.02.2017 um 09:49 schrieb deloptes: > have a look at the code changes. Looking at the code changes from 3.16 to 4.9 ? Good idea. I will start right now ;-) Matthias
kernel performance: 3.16 vs. 4.9
Hi, I have upgraded my PC to newest chipset and CPU: Kaby Lake, Z270 with i7-7700K. Out of curiosity I did a kernel benchmark. Comparing darktable performance with kernel 3.16.0-4-amd64 and 4.9.0-1-amd64. I use the following command to run darktable: darktable-cli test.CR2 test.jpg --core -d perf -d opencl The results are surprising for me. Kernel 4.9 very much outperformance kernel 3.16. Here are the results with and without opencl (using a Geforce GTX750TI): kernel 3.16 kernel 4.9 with opencl 16 s9 s without opencl 120 s 23 s Without opencl, that is with pure CPU performance, the difference is a factor of 5! Why is that? What am I missing? I can hardly believe that kernel 4.9 is so much faster. Matthias
Re: can not set time
Am 04.02.2017 um 17:43 schrieb Jude DaShiell: On Sat, 4 Feb 2017, Matthias Bodenbinder wrote: Date: Sat, 4 Feb 2017 09:07:00 From: Matthias Bodenbinder To: debian-user@lists.debian.org Subject: Re: can not set time Resent-Date: Sat, 4 Feb 2017 14:07:22 + (UTC) Resent-From: debian-user@lists.debian.org Am 04.02.2017 um 14:36 schrieb Jude DaShiell: please check that other box and see if it has systemd-timesyncd.service on it. You can probably start that service up and solve that problem. Then try timedatectl set-ntp true. That should make timesync happen on boot. On Sat, 4 Feb 2017, Matthias Bodenbinder wrote: timedatectl set-ntp true did not help. It is not changing the time. My reference PC has debian testing running with systemd-timesyncd. But the broken PC is MINT LMDE which is still on init.d. Matthias Okay, since you have ntp, ntpd -qg and then hwclock --systohc --utc may get this working for you. We probably don't need to do anything with your timezone setting link to /etc/localtime by now. Hello Jude, I tried it all. I googled almost every command related to time setting and tried it out. But it did not work. I am still not sure why. But now, after switching to systemd and systemd-timesyncd it works. See my other post. Thank you for help anyways. Matthias
Re: can not set time
Am 04.02.2017 um 15:49 schrieb Matthias Bodenbinder: More info: I switched to systemd and systemd-timesyncd. During boot the time is synced back and forth multiple times and in the end it stays wrong. Look at this. See the timestamps for each line. Going back and forth. Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: Using NTP server 78.46.253.198:123 (2.debian.pool.ntp.org). Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.925s/0.016s/0.000s/+0ppm Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.914s/0.017s/323.505s/+0pp Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.904s/0.015s/792.414s/+0pp Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.894s/0.015s/723.371s/+0pp Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.885s/0.015s/647.003s/+0pp Feb 04 15:59:06 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. The switch to systemd and systemd-timesyncd did the trick. But it takes very long. Its obvious from the journal messages but I did not get it at first: timesyncd changes the time in small increments of only 0.01 seconds. I just had to wait and now the time is correct. Matthias
Re: can not set time
:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.693s/0.015s/0.037s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.683s/0.015s/0.045s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.673s/0.016s/0.030s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.663s/0.015s/0.037s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.653s/0.015s/0.045s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.643s/0.016s/0.029s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.633s/0.015s/0.025s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.622s/0.017s/0.025s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.613s/0.015s/0.030s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.602s/0.016s/0.037s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.593s/0.016s/0.045s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.582s/0.015s/0.030s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.572s/0.015s/0.037s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.566s/0.016s/0.044s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Feb 04 15:44:51 broken-PC systemd-timesyncd[475]: interval/delta/delay/jitter/drift 32s/-855.556s/0.016s/0.029s/+0ppm Feb 04 15:59:07 broken-PC systemd-timesyncd[475]: System time changed. Resyncing. Any idea? Matthias
Re: can not set time
Am 04.02.2017 um 14:36 schrieb Jude DaShiell: > please check that other box and see if it has systemd-timesyncd.service on it. > You can probably start that service up and solve that problem. > Then try timedatectl set-ntp true. > That should make timesync happen on boot. > On Sat, 4 Feb 2017, Matthias Bodenbinder wrote: timedatectl set-ntp true did not help. It is not changing the time. My reference PC has debian testing running with systemd-timesyncd. But the broken PC is MINT LMDE which is still on init.d. Matthias
can not set time
Hi, I have a weird issue with one of my debian boxes (LMDE): I can not set the time. The time is off by ca. 14 min and whatever I try to fix it is failing. I tried ntp, ntpdate, date and rdate. Nothing helps. ntpdate shows the offset but is not fixing it. 91# ntpdate 0.debian.pool.ntp.org 4 Feb 14:03:55 ntpdate[8159]: step time server 85.114.132.52 offset -855.296824 sec rdate is showing some interesting behaviour. If I run a command like "date && rdate -v ptbtime1.ptb.de && date" to see the time before and after rdate, the output suggests that rdate was successful: 81# date && rdate -v ptbtime1.ptb.de && date Sat Feb 4 14:16:04 CET 2017 Sat Feb 4 14:01:49 CET 2017 rdate: adjust local clock by -855 seconds Sat Feb 4 14:01:49 CET 2017 But in fact 1 second later the time is back to old values again: 82# date Sat Feb 4 14:16:06 CET 2017 timedatectl is showing wrong time as well: 93# timedatectl Local time: Sat 2017-02-04 14:20:39 CET Universal time: Sat 2017-02-04 13:20:39 UTC RTC time: Sat 2017-02-04 13:20:39 Time zone: Europe/Berlin (CET, +0100) But is should be: Local time: Sa 2017-02-04 14:06:25 CET Universal time: Sa 2017-02-04 13:06:25 UTC RTC time: Sa 2017-02-04 13:06:25 Time zone: Europe/Berlin (CET, +0100) I am lost. Matthias
Re: apt-get is not following preferences.d
Am 25.01.2017 um 20:04 schrieb Michael Lange: Hi, On Wed, 25 Jan 2017 07:18:07 +0100 Matthias Bodenbinder wrote: (...) I do not have that file /etc/apt/apt.conf.d/02periodic. I put /etc/cron.daily/apt back where it belongs and this morning the pinning was screwed up again. This is really weird. Then you could try to create the file and add the line APT::Periodic::Update-Package-Lists "0"; and see if that helps. Maybe your system somehow has a different default. Regards Michael I created that file with this line but it does not help. Still the same odd pinning after boot. So my problem might not be related to /etc/cron.daily/apt. I guess I have to start searching again :-( Matthias
Re: apt-get is not following preferences.d
Am 23.01.2017 um 11:47 schrieb Michael Lange: Hi, On Mon, 23 Jan 2017 08:40:32 +0100 Matthias Bodenbinder wrote: (...)Yes, this is exactly what happens on my PC. But it has no solution. In the meantime I found a workaround. I moved /etc/cron.daily/apt out of the way. It looks like this script is being executed during boot before the network is ready. How can I make sure that the script /etc/cron.daily/apt is only executed when network is up? What is this script good for anyways? From what the comment at the top of the script says: # This file understands the following apt configuration variables: # Values here are the default. # Create /etc/apt/apt.conf.d/02periodic file to set your preference. (...) # # APT::Periodic::Update-Package-Lists "0"; # - Do "apt-get update" automatically every n-days (0=disable) # it looks like you have a file /etc/apt/apt.conf.d/02periodic where APT::Periodic::Update-Package-Lists is set to "1" (or so). Here (on Jessie) such a file does not exist, and as promised the updates don't happen. Regards Michael Hello Michael, I do not have that file /etc/apt/apt.conf.d/02periodic. I put /etc/cron.daily/apt back where it belongs and this morning the pinning was screwed up again. This is really weird. Matthias
Re: apt-get is not following preferences.d
Am 12.01.2017 um 20:31 schrieb Sven Hartge: Matthias Bodenbinder wrote: What is going wrong here? Any idea? Possibly https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849382 Grüße, Sven. Yes, this is exactly what happens on my PC. But it has no solution. In the meantime I found a workaround. I moved /etc/cron.daily/apt out of the way. It looks like this script is being executed during boot before the network is ready. How can I make sure that the script /etc/cron.daily/apt is only executed when network is up? What is this script good for anyways? Matthias
Re: apt-get is not following preferences.d
Am 12.01.2017 um 19:43 schrieb Michael Lange: Just a shot in the dark: maybe the apt-get update at boot time is done before a network connection has been established? I noticed that this can lead to the exact behavior you describe when pinning is in use. Apparently a bug in apt. Regards Michael Hello Michael, I gave it a try. I unplugged the network and did an apt-get update. This is throwing all the errors that the repos are not available. But in the end the next "apt-get dist-upgrade" indeed wants to update all packages to testing. So it seems that this is an issue with network not ready while apt-get update is being performed. How do I fix this? Where to look? And thank you for the hint, Michael. Matthias
apt-get is not following preferences.d
Hi,
I have a weird behaviour on one of my debian boxes. It is running Mint LMDE and
the issue is the following:
I have several additional sources defined: debian testing, debian backports,
etc. I have defined priorities for the repos so that testing has prio 300 and
does not replace the stable packages automatically. That works fine if I do an
"apt-get update" followed by an "apt-get dist-upgrade". No issue.
The issue only occurs directly after boot. Somehow there is an "apt-get update"
excecuted during boot time and this is ignoring the repo priorities. If I do a
"apt-get dist-upgrade" directly after boot it wants to upgrade all packages to
the testing version ("1547 upgraded, 358 newly installed, 97 to remove and 36
not upgraded."). This is a mistake.
After boot the priorities are all set to 500. Example:
12# apt-cache policy zip vim-common
zip:
Installed: 3.0-8
Candidate: 3.0-11
Version table:
3.0-11 0
500 http://ftp.de.debian.org/debian/ testing/main amd64 Packages
*** 3.0-8 0
500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages
100 /var/lib/dpkg/status
vim-common:
Installed: 2:7.4.488-7+deb8u1
Candidate: 2:8.0.0134-1
Version table:
2:8.0.0134-1 0
500 http://ftp.de.debian.org/debian/ testing/main amd64 Packages
*** 2:7.4.488-7+deb8u1 0
500 http://security.debian.org/ jessie/updates/main amd64 Packages
100 /var/lib/dpkg/status
2:7.4.488-7 0
500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages
If I do an "apt-get update" everything is back to normal.
15# apt-cache policy zip vim-common
zip:
Installed: 3.0-8
Candidate: 3.0-8
Version table:
3.0-11 0
300 http://ftp.de.debian.org/debian/ testing/main amd64 Packages
*** 3.0-8 0
500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages
100 /var/lib/dpkg/status
vim-common:
Installed: 2:7.4.488-7+deb8u1
Candidate: 2:7.4.488-7+deb8u1
Version table:
2:8.0.0134-1 0
300 http://ftp.de.debian.org/debian/ testing/main amd64 Packages
*** 2:7.4.488-7+deb8u1 0
500 http://security.debian.org/ jessie/updates/main amd64 Packages
100 /var/lib/dpkg/status
2:7.4.488-7 0
500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages
What is going wrong here? Any idea?
Matthias
repository uses weak digest algorithm (SHA1)
Hi, I have a weird signature issue with an LMDE Mint repository. I know that this is not pure debian but nevertheless I think my question is best posted here. The issue is: I have 4 PC and 1 laptop at home. All running LMDE2. When I do "apt-get update" the PCs have no issue. But the laptop says: # last 2 lines of "apt-get update" output W: http://linux-mint.froonix.org/dists/betsy/Release.gpg: Signature by key E1A38B8F144675D060EA666F3EE67F3D0FF405B2 uses weak digest algorithm (SHA1) W: http://extra.linuxmint.com/dists/betsy/Release.gpg: Signature by key E1A38B8F144675D060EA666F3EE67F3D0FF405B2 uses weak digest algorithm (SHA1) ## I reinstalled all keyring debs on the laptop. I am using the exact same sources on the laptop and the PCs (rsync of /etc/apt/sources.list*). During the last test I even rsync'ed all /etc/apt/trusted* to the laptop. I tried to fetch it via apt-key: ## # apt-key adv --keyserver keyserver.ubuntu.com --recv-keys E1A38B8F144675D060EA666F3EE67F3D0FF405B2 Executing: /tmp/tmp.9xZlldxhO9/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys E1A38B8F144675D060EA666F3EE67F3D0FF405B2 gpg: requesting key 0FF405B2 from hkp server keyserver.ubuntu.com gpg: key 0FF405B2: "Clement Lefebvre (Linux Mint Package Repository v1) " not changed gpg: Total number processed: 1 gpg: unchanged: 1 ## But the laptop keeps throwing these signature warnings - and only the laptop. Why is that? Thank you for your help. Matthias
Re: Icedove crashes after recent update
Hi JP, thanks for your reply. I think it is the same behavior for me (but I did not pay too close attention when it exactly crashes). Anyway, it it good the problem was already encountered :) The intention of me mail was mainly to report it. Hope there will be a fix soon -- this is super annoying and make Icedoce almost unusable for me... -Matthias On 06/25/2016 12:50 AM, Jape Person wrote: > On 06/24/2016 06:11 PM, Matthias J. Sax wrote: >> Hi, >> >> I am new to Debian mailing-list (and also not subscribed -- please >> answer directly to me if you need more input). >> >> I am using >> >> $ uname -a >> Linux XXX 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) >> x86_64 GNU/Linux >> >> After the last update, Icedove (v45.1.0) crashed regularly. >> >> Please let me know, what information I need to provide such that you can >> track the problem. >> >> Thanks! >> >> -Matthias >> > Hello, Matthias. > > I'm replying directly to you as well as sending to debian-user. Though > it's not necessary, you may want to subscribe to the list temporarily -- > just to make sure you receive all replies to your question. I can almost > guarantee that not everyone will reply to you off-list. > > Also, please do not reply directly to me, but only to the list. I will > see you reply, and so will other people who may be better able to help > than I. > > My only contribution, so far, is to say that I'm seeing the same issue > on the new version of Icedove (45.1.0). My system is running Stretch -- > > $ uname -a > Linux wiz 4.6.0-1-amd64 #1 SMP Debian 4.6.1-1 (2016-06-06) x86_64 GNU/Linux > > I am only seeing Icedove close when I am in the process of reading > messages. Furthermore, it happens only when I am using an arrow key or > the mouse to select the next message to read. It doesn't happen when I'm > using the integrated calendar (iceowl-extension), creating events, > sending mail, creating filters, etc. It only happens when I'm > progressing through a list of e-mails, reading them. > > If you can tell us whether or not you have noticed any particular action > that might precipitate the crash, that may be helpful. This is only > happening occasionally with my systems, so you may have to watch for a > while. > > I'm seeing nothing in logs, so far. > > Good luck! > > JP signature.asc Description: OpenPGP digital signature
Icedove crashes after recent update
Hi, I am new to Debian mailing-list (and also not subscribed -- please answer directly to me if you need more input). I am using $ uname -a Linux XXX 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux After the last update, Icedove (v45.1.0) crashed regularly. Please let me know, what information I need to provide such that you can track the problem. Thanks! -Matthias signature.asc Description: OpenPGP digital signature
Re: btrfs: mixing raid0 and raid1 - How?
Hello Andy, I am trying to stay with newest versions as long as it does not jeopardize stability. I am using Mint LMDE2 with debian backports. So I do have kernel 4.4+71~bpo8+1 running. btrfs tools are from debian stable, which has version 3.17. I am wondering if it would make sense to also get the tools from the backports repo which has version 4.4-1~bpo8+1. I understand from your message that I should do that. Right? Matthias 4.4+71~bpo8+1 Am 16.04.2016 um 19:57 schrieb Andy Smith: > Hello, > > On Sat, Apr 16, 2016 at 01:35:20PM +0200, Luis Felipe Tabera Alonso wrote: >> Still btrfs is quite young, I am not sure if there are serious issues in >> 3.17, >> I would make some experiments before actual use. > > If you are going to use btrfs I would consider it essential to be > subscribed to the linux-btrfs mailing list. You will also need to > use a much newer kernel than 3.17, and you will need to commit to > continuing to use newer kernels for some time yet. > > I mention this because you need to be aware that you may still hit > issues where you need the help of linux-btrfs and that there is a > need to use newer kernels than you will find packaged in Debian > stable. > > I do myself run btrfs at home and I thought I had a stable > combination of kernel version and userland tools (btrfs-tools), but > when I came to need to replace a dead device I found that subsequent > developments in btrfs meant I needed a newer btrfs-tools, and that > in turn meant I needed a newer kernel. > > If the idea of having to upgrade kernel and some userland tools in > order to recover from a simple situation of a dead device does not > appeal to you then btrfs may not yet be for you. Things like this > are why I do not yet run it in production. > > Cheers, > Andy >
Re: btrfs: mixing raid0 and raid1 - How?
You are right. I did the same test with dd. It took a while ;-) 23# dd if=/dev/zero of=file.zero dd: Schreiben in „file.zero“: Auf dem Gerät ist kein Speicherplatz mehr verfügbar 1462670786+0 Datensätze ein 1462670785+0 Datensätze aus 748887441920 Bytes (749 GB) kopiert, 14831,9 s, 50,5 MB/s 24# ll -h insgesamt 698G -rw-r--r-- 1 root root 698G Apr 16 20:03 file.zero Thank you for helping me! Matthias Am 16.04.2016 um 13:35 schrieb Luis Felipe Tabera Alonso: > On sábado, 16 de abril de 2016 12:05:05 (CEST) Matthias Bodenbinder wrote: > >> 38# df -h /mnt/test/ >> Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf >> /dev/sdg 699G 17M 466G 1% /mnt/test > > df is not reliable for btrfs raids, it is better to use btrfs fi df to check > actual used space. > > Using btrfs-tools and kernel from sid (4.4): > > root@mychabol:/mnt/temporal# dd if=/dev/zero of=disk1 bs=1 count=0 seek=750M > root@mychabol:/mnt/temporal# dd if=/dev/zero of=disk2 bs=1 count=0 seek=500M > root@mychabol:/mnt/temporal# dd if=/dev/zero of=disk3 bs=1 count=0 seek=250M > > root@mychabol:/mnt/temporal# mkfs.btrfs -f -draid1 -mraid1 disk1 disk2 disk3 > btrfs-progs v4.4 > See http://btrfs.wiki.kernel.org for more information. > > Label: (null) > UUID: 4fbfda48-3a10-4e1b-92d8-96be759c2a8c > Node size: 16384 > Sector size:4096 > Filesystem size:1.46GiB > Block group profiles: > Data: RAID183.00MiB > Metadata: RAID183.00MiB > System: RAID112.00MiB > SSD detected: no > Incompat features: extref, skinny-metadata > Number of devices: 3 > Devices: >IDSIZE PATH > 1 750.00MiB disk1 > 2 500.00MiB disk2 > 3 250.00MiB disk3 > > root@mychabol:/mnt/temporal# losetup /dev/loop0 disk1 > root@mychabol:/mnt/temporal# losetup /dev/loop1 disk2 > root@mychabol:/mnt/temporal# losetup /dev/loop2 disk3 > > root@mychabol:/mnt/temporal# mkdir test > root@mychabol:/mnt/temporal# mount /dev/loop0 test > > root@mychabol:/mnt/temporal# btrfs fi df test/ > Data, RAID1: total=75.00MiB, used=0.00B > System, RAID1: total=8.00MiB, used=16.00KiB > Metadata, RAID1: total=75.00MiB, used=112.00KiB > GlobalReserve, single: total=16.00MiB, used=0.00B > > root@mychabol:/mnt/temporal# df -h test/ > S.ficheros Tamaño Usados Disp Uso% Montado en > /dev/loop0 750M17M 491M 4% /mnt/temporal/test > > Like in your case, df thinks that there are only 491M usable. However, if I > try to fill the volume > > root@mychabol:/mnt/temporal# cd test/ > root@mychabol:/mnt/temporal/test# dd if=/dev/zero of=file.zero > dd: escribiendo en 'file.zero': No queda espacio en el dispositivo > 1345402+0 registros leídos > 1345401+0 registros escritos > 688845312 bytes (689 MB, 657 MiB) copied, 3,10508 s, 222 MB/s > > root@mychabol:/mnt/temporal/test# ls -lh > total 657M > -rw-r--r-- 1 root root 657M abr 16 13:24 file.zero > root@mychabol:/mnt/temporal/test# df -h . > S.ficheros Tamaño Usados Disp Uso% Montado en > /dev/loop0 750M 674M 64K 100% /mnt/temporal/test > > With the 75M of metadata, you can check that this fills the three devices. > Moreover > > root@mychabol:/mnt/temporal/test# rm file.zero > root@mychabol:/mnt/temporal/test# df -h . > S.ficheros Tamaño Usados Disp Uso% Montado en > /dev/loop0 750M17M 657M 3% /mnt/temporal/test > > Try to do the same to see if df gets more accurate. > > Still btrfs is quite young, I am not sure if there are serious issues in > 3.17, > I would make some experiments before actual use. > > Bests > > Luis > >
Re: btrfs: mixing raid0 and raid1 - How?
And: 39# btrfs filesystem show Label: none uuid: 35db7af4-a116-45fa-8611-97aeb5d4a8d3 Total devices 3 FS bytes used 640.00KiB devid1 size 698.64GiB used 2.02GiB path /dev/sdg devid2 size 465.76GiB used 1.01GiB path /dev/sdh devid3 size 232.88GiB used 1.01GiB path /dev/sdi Am 16.04.2016 um 12:05 schrieb Matthias Bodenbinder: > Hello Luis, > > I followed that link which confirms that a btrfs raid1 out of these three > devices should give 750 GB of data capacity. But his is not what I get. > > This is what I have: > > Disk /dev/sdg: 698,7 GiB, 750156374016 bytes, 1465149168 sectors > Disk /dev/sdh: 465,8 GiB, 500107862016 bytes, 976773168 sectors > Disk /dev/sdi: 232,9 GiB, 250058268160 bytes, 488395055 sectors > > So it is actually not 750 GB but 700. Anyways... > > This is what I did: > > ### > 35# mkfs.btrfs -f -d raid1 -m raid1 /dev/sdg /dev/sdh /dev/sdi > Btrfs v3.17 > See http://btrfs.wiki.kernel.org for more information. > > Turning ON incompat feature 'extref': increased hardlink limit per file to > 65536 > adding device /dev/sdh id 2 > adding device /dev/sdi id 3 > fs created label (null) on /dev/sdg > nodesize 16384 leafsize 16384 sectorsize 4096 size 1.36TiB > > 36# mount /dev/sdg /mnt/test/ > > 37# btrfs fi df /mnt/test/ > Data, RAID1: total=1.00GiB, used=512.00KiB > Data, single: total=8.00MiB, used=0.00B > System, RAID1: total=8.00MiB, used=16.00KiB > System, single: total=4.00MiB, used=0.00B > Metadata, RAID1: total=1.00GiB, used=112.00KiB > Metadata, single: total=8.00MiB, used=0.00B > GlobalReserve, single: total=16.00MiB, used=0.00B > > 38# df -h /mnt/test/ > Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf > /dev/sdg 699G 17M 466G 1% /mnt/test > > ### > > This leaves me with just 466 GB of free disc space. > Something is wrong. Either what I am doing is wrong or the web page is wrong. > > Matthias > > > Am 16.04.2016 um 10:20 schrieb Luis Felipe Tabera Alonso: >> On sábado, 16 de abril de 2016 9:00:00 (CEST) Matthias Bodenbinder wrote: >>> Hello, >>> >>> I have 3 hard drive with 750 GB, 500 GB and 250 GB. I want to use btrfs as >>> filesystem. This will be my first test installation of btrfs. >>> >>> My target is to get redundancy as well as a 750 GB data capacity. So I was >>> thinking to create a raid0 with the 500 and 250 GB drive. This would result >>> in a raid0 with 750 GB capacity. I want to add this raid0 as a mirror in a >>> raid1 with the other 750 GB drive. >>> >>> But how do I do that? >>> >>> Thanks >>> Matthias >> >> Disclaimer: I have necer made anything further than a btrfs raid1 with two >> equally sized devices. >> >> >> If you create a raid1 with the three devices you will get 750GB with >> redundancy. Current Btrfs raid1 means "data and metadata is copied twice in >> different devices". And btrfs is smart enough to not copy the data in the >> two >> smaller disks. I am not sure if this web page is accurate http:// >> carfax.org.uk/btrfs-usage/ but you can take a look. >> >> You can also create a single virtual device from the 250 and 500 devices >> using >> mdadm or lvm and then create a btrfs raid1 out of the 750GB device and the >> virtual device. >> >> With the "pure" btrfs setup, if you lose a single device you will be able to >> mount the device as "degraded". >> >> With the mixed setting, you can lose a single device and read the data. >> Moreover, you can lose the two small devices and still be able to mount the >> volume. >> >> luis >> >> >> > > >
Re: btrfs: mixing raid0 and raid1 - How?
Hello Luis, I followed that link which confirms that a btrfs raid1 out of these three devices should give 750 GB of data capacity. But his is not what I get. This is what I have: Disk /dev/sdg: 698,7 GiB, 750156374016 bytes, 1465149168 sectors Disk /dev/sdh: 465,8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdi: 232,9 GiB, 250058268160 bytes, 488395055 sectors So it is actually not 750 GB but 700. Anyways... This is what I did: ### 35# mkfs.btrfs -f -d raid1 -m raid1 /dev/sdg /dev/sdh /dev/sdi Btrfs v3.17 See http://btrfs.wiki.kernel.org for more information. Turning ON incompat feature 'extref': increased hardlink limit per file to 65536 adding device /dev/sdh id 2 adding device /dev/sdi id 3 fs created label (null) on /dev/sdg nodesize 16384 leafsize 16384 sectorsize 4096 size 1.36TiB 36# mount /dev/sdg /mnt/test/ 37# btrfs fi df /mnt/test/ Data, RAID1: total=1.00GiB, used=512.00KiB Data, single: total=8.00MiB, used=0.00B System, RAID1: total=8.00MiB, used=16.00KiB System, single: total=4.00MiB, used=0.00B Metadata, RAID1: total=1.00GiB, used=112.00KiB Metadata, single: total=8.00MiB, used=0.00B GlobalReserve, single: total=16.00MiB, used=0.00B 38# df -h /mnt/test/ Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf /dev/sdg 699G 17M 466G 1% /mnt/test ### This leaves me with just 466 GB of free disc space. Something is wrong. Either what I am doing is wrong or the web page is wrong. Matthias Am 16.04.2016 um 10:20 schrieb Luis Felipe Tabera Alonso: > On sábado, 16 de abril de 2016 9:00:00 (CEST) Matthias Bodenbinder wrote: >> Hello, >> >> I have 3 hard drive with 750 GB, 500 GB and 250 GB. I want to use btrfs as >> filesystem. This will be my first test installation of btrfs. >> >> My target is to get redundancy as well as a 750 GB data capacity. So I was >> thinking to create a raid0 with the 500 and 250 GB drive. This would result >> in a raid0 with 750 GB capacity. I want to add this raid0 as a mirror in a >> raid1 with the other 750 GB drive. >> >> But how do I do that? >> >> Thanks >> Matthias > > Disclaimer: I have necer made anything further than a btrfs raid1 with two > equally sized devices. > > > If you create a raid1 with the three devices you will get 750GB with > redundancy. Current Btrfs raid1 means "data and metadata is copied twice in > different devices". And btrfs is smart enough to not copy the data in the two > smaller disks. I am not sure if this web page is accurate http:// > carfax.org.uk/btrfs-usage/ but you can take a look. > > You can also create a single virtual device from the 250 and 500 devices > using > mdadm or lvm and then create a btrfs raid1 out of the 750GB device and the > virtual device. > > With the "pure" btrfs setup, if you lose a single device you will be able to > mount the device as "degraded". > > With the mixed setting, you can lose a single device and read the data. > Moreover, you can lose the two small devices and still be able to mount the > volume. > > luis > > >
btrfs: mixing raid0 and raid1 - How?
Hello, I have 3 hard drive with 750 GB, 500 GB and 250 GB. I want to use btrfs as filesystem. This will be my first test installation of btrfs. My target is to get redundancy as well as a 750 GB data capacity. So I was thinking to create a raid0 with the 500 and 250 GB drive. This would result in a raid0 with 750 GB capacity. I want to add this raid0 as a mirror in a raid1 with the other 750 GB drive. But how do I do that? Thanks Matthias
Re: apt-get error messages
Am 06.12.2015 um 22:47 schrieb Klaus Jantzen: > On 12/05/2015 08:56 PM, Myscelus wrote: >> On 12/05/2015 08:55 PM, Klaus Jantzen wrote: >>> Hi, >>> >>> due to a typing error - I wanted to say 'dpkg --add-architecture i386' >>> but wrote 'i368' - >>> I get the following error messages when running apt-get update: >>> >>> >>> ... >>> >>> W: Failed to fetch >>> http://download.virtualbox.org/virtualbox/debian/dists/vivid/Release >>> Unable to find expected entry 'contrib/binary-i368/Packages' in Release >>> file (Wrong sources.list entry or malformed file) >>> >>> W: Failed to fetch >>> http://ftp-stud.hs-esslingen.de/debian/dists/wheezy-updates/Release >>> Unable to find expected entry 'main/binary-i368/Packages' in Release >>> file (Wrong sources.list entry or malformed file) >>> >>> W: Failed to fetch >>> http://security.debian.org/dists/wheezy/updates/Release Unable to find >>> expected entry 'main/binary-i368/Packages' in Release file (Wrong >>> sources.list entry or malformed file) >>> >>> ... >>> >>> >>> Where is the information for these erroneous requests stored? >>> How can I remove it? >> >> dpkg --remove-architecture i368 >> >> > > That seems to have done something. > At least the messages shown above disappeared when I said > > dpkg --remove-architecture i368 > apt-get update > > But I cannot add the correct architecture: > > dpkg --add-architecture i386 > apt-get update > dpkg --print-architecture > > just shows me 'amd64'. > 'apt-get update' seems to have found some i386 packages > but the second architecture is not printed out. > > That output is correct. "dpkg --print-architecture" shows the default architecture for which packages are installed. Try dpkg --print-foreign-architectures That should output "i386" Matthias
Re: Upgrade Jessie to kernel 4.2
Am 06.12.2015 um 15:55 schrieb David Parfitt: > (Setup info at end) > I am considering upgrading the kernel my stable install to kernel > version 4.2 from jessie-backports. The main purpose of this is to see > whether it helps with the problem I have been having with sound. > > *My question is* : how much / what do I risk breaking in doing this? I would say you are not risking anything. As long as you do not deinstall your current kernel. You can always switch back to your old kernel during boot. And if you are not satisfied with the 4.2 kernel you can simply deinstall it. Matthias
weird BIOS / USB Problem with Technotrend S2-4600
Hi, I have a strange problem with my PC booting while my newly aqcuired Technotrend S2-4600 DVB-S2 USB box is connected. When I start for the first time (cold boot with the usb box), everything is fine. firmware is installed and I can watch TV with vdr and xine or vlc. No issue. But as soon as I power off and on again the issue occurs. The next time when I power on, the PC does ot boot. It does not even get to the boot loader. Not even the BIos messages are displayed, not even the first initial beep is played. The screen is just black. But when I unplug the Technotrend box the beep sounds immediately and the boot process starts. Attaching the box immediately again during boot works fine and I can watch TV. Why is that? I can not find any BIOS setting that could help. Motherboard is a Asus P8H67-V; Bios version 3707. What is going wrong here? Any idea? Matthias
pinning issue or what?
Hi, I wanted to have cinnamon 2.8 on debian testing. So I played around with the lmde2 repos (betsy) in testing and managed to install cinnamon 2.8. In the course of this activity I had to donwgrade a handful of packages. It is working now. All is fine, except When I do "apt-get dist-upgrade" it wants to remove cinnamon: 35# d-u Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: cinnamon cinnamon-screensaver gir1.2-webkit2-3.0 The following NEW packages will be installed: libgtop2-7 The following packages have been kept back: libjavascriptcoregtk-3.0-0 libwebkitgtk-3.0-0 The following packages will be upgraded: gir1.2-javascriptcoregtk-3.0 gir1.2-webkit-3.0 libmarco-private0 libnemo-extension1 marco marco-common 6 upgraded, 1 newly installed, 3 to remove and 2 not upgraded. Need to get 287 kB/1241 kB of archives. After this operation, 1207 kB disk space will be freed. Do you want to continue? [Y/n] ^C Why is that? The policy says: 36# apt-cache policy cinnamon cinnamon: Installed: 2.8.4+betsy Candidate: 2.8.4+betsy Version table: *** 2.8.4+betsy 0 900 http://packages.linuxmint.com/ betsy/main amd64 Packages 100 /var/lib/dpkg/status 2.6.13-1 0 500 http://ftp.de.debian.org/debian/ testing/main amd64 Packages 100 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages 2.2.16-5 0 500 http://ftp.de.debian.org/debian/ stable/main amd64 Packages >From that point of view it should keep cinnamon. Here are my pinning values: 37# cat 99_debian Package: * Pin: release a=stable,l=debian Pin-Priority: 500 Package: * Pin: release o=Debian,l=Debian-Security Pin-Priority: 500 Package: * Pin: release a=testing,l=debian Pin-Priority: 500 Package: * Pin: release a=unstable,l=debian Pin-Priority: 100 Package: * Pin: release a=experimental Pin-Priority: 100,l=debian rakete - root - /etc/apt/preferences.d 38# cat 98_mint Package: * Pin: origin packages.linuxmint.com Pin-Priority: 900 Package: * Pin: origin www.deb-multimedia.org Pin-Priority: 500 --- Any idea? Thanks Matthias
Re: Where is digikam?
Am 09.11.2015 um 18:42 schrieb Francesco Ariis: > On Mon, Nov 09, 2015 at 06:38:11PM +0100, Matthias Bodenbinder wrote: >> Hi, >> >> I see digikam in unstable for a very long time now. But it is not coming >> to testing. Why is that? Wasnt the push to testing supposed to be an >> automatic process? Or does digikam in unstable still have critical bugs? >> What is the reason for the delay? >> >> Matthias >> > > Hey Matthias, > from [1] leading to (`Check why`) [2], apparently depends on stuff > which is not into testing yet. > > [1] https://packages.qa.debian.org/d/digikam.html > [2] https://release.debian.org/migration/testing.pl?package=digikam > > Many thanks. This is helpful ... but confusing either. The page https://release.debian.org/migration/testing.pl?package=digikam says: * digikam is waiting for opencv * opencv has the same version in unstable and testing (2.4.9.1+dfsg-1.2) but a few lines done it says: * digikam depends on libopencv-core2.4 which is not available in testing This sounds contradictory to me. Matthias
Where is digikam?
Hi, I see digikam in unstable for a very long time now. But it is not coming to testing. Why is that? Wasnt the push to testing supposed to be an automatic process? Or does digikam in unstable still have critical bugs? What is the reason for the delay? Matthias
Either KLauncher is not running anymore, or it failed to start the application.
Hi, I am running a debian 8 stable system and have some trouble with KDE or KLauncher. Every once in a while, directly after loging into KDE I can not launch a program, e.g. iceweasel. The system seems to hang, not reacting to mouse clicks. After waiting for a minute or so an error message pops up that says: "Error launching /usr/share/applications/iceweasel.desktop. Either KLauncher is not running anymore, or it failed to start the application. After this message, KDE works fine. It is just this first minute after login which causes the issue. And it only happens may be 1 in 10 times. I have no clue what is going on and how to debug this thing. Any ideas what is going on here? Matthias
Re: Temporarily hold a package............
Am 09.05.2015 um 05:20 schrieb Charlie: > > From my keyboard: > > I have been looking through the man pages for: apt-get, apt-get upgrade, > but I'm certain I don't understand how I might hold a package for a > while? > > Anyone who can and is inclined to help, might assist me for the whole > testing cycle in this case with their advice. > > I get this when I attempt an upgrade of stretch: > > Retrieving bug reports... > > Done Parsing Found/Fixed information... > > Done serious bugs of openssl (1.0.1k-3 → 1.0.2a-1) > b1 - #770605 - openssl: Removes symbol without SONAME bump > > Merged with: 768476 768522 769023 770278 771169 771993 781094 781929 > > Summary: > openssl(1 bug) > > Are you sure you want to install/upgrade the above packages? > [Y/n/?/...] n > ** > ** Exiting with an error in order to stop the installation. ** > ** : Hi Charlie, you could either pin a package in /etc/apt/preferences.d/ Package: hello Pin: release n=lenny Pin-Priority: 995 .. see http://blog.opperschaap.net/2009/12/12/using-the-preferences-file-on-debian-and-debian-based-distributions/ or hold a package sudo apt-mark hold package_name .. see http://askubuntu.com/questions/18654/how-to-prevent-updating-of-a-specific-package Matthias -- 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/mikbv1$rc$1...@ger.gmane.org
Re: issue with systemd-udev-settle
Am 01.05.2015 um 08:36 schrieb Michael Biebl: It's a workaround. So it might still be worth a bug report against the linux kernel. I did that: Bug#783934: Acknowledgement (linux-image-3.16.0-4-amd64: systemd-udev-settle waiting 50 s during boot for snd-usb-audio) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783934 Matthias -- 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/mhvsu2$7oi$1...@ger.gmane.org
Re: System wide proxy in Debian Jessie
Am 01.05.2015 um 08:49 schrieb Avinash Sonawane: Which is the standard/recommended way to set system wide proxy in Debian instead of editing utility specific rc files (wgetrc, apt.conf etc)? I am aware of /etc/environment, setting http_proxy environ variable and then export it, editing bashrc. What you need is a "transparent proxy". This is setup in the background with iptables and squid. It will ensure that all IP traffic is routed through the proxy. Regardless of invidual app settings or environment variables. I had this running a few years ago and it worked perfectly. But I can not recall the detailed setup anymore. Just google "transparent proxy" and you will find your way. e.g. http://www.tldp.org/HOWTO/TransparentProxy-5.html http://www.tldp.org/HOWTO/TransparentProxy-6.html Matthias -- 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/mhvted$i3h$1...@ger.gmane.org
Re: issue with systemd-udev-settle
Am 01.05.2015 um 00:00 schrieb Michael Biebl: You could try blacklisting "snd-usb-audio" via $ echo "blacklist snd-usb-audio" > /etc/modprobe.d/no-usb-audio.conf Maybe that helps (you might need to rebuild your initramfs as well) This did the trick. The sound is disabled, the boot is fast and the usb hub in the keyboard is still working. Perfect!. Thank you all so much for your support. Matthias -- 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/mhv1r0$afe$1...@ger.gmane.org
Re: issue with systemd-udev-settle
Am 30.04.2015 um 16:57 schrieb Matthias Bodenbinder: > Am 30.04.2015 um 15:09 schrieb Michael Biebl: >> As you can see above, systemd-udevd timeouts processing the events from >> that device and is eventually killed. The internal timeout for udev is >> 90s. If you add the the remaining time to boot the system, that would >> explain the 2min boot times. >> >> This looks like either buggy hardware or a bug in the kernel. >> >> Can you try with a different keyboard and mouse directly attached to >> your computer, not via a hub? > > Yes, that is it. > > It is the keyboard! I tried a different one and the computer boots fast. > > The keyboard is not new. I had it running on the same computer for several > years. All with debian wheezy. No problems. Why is that now? I doubt that > this is a hw issue although I have never tested the sound module in that > keyboard. > > What can I do about it? I like this keyboard. I do not want to replace it. > Can I deactivate probing for usb sound? > > Matthias I tested the keyboard on a different PC with a current debian testing instalation and the issue is more or less the same. Except for the waiting time. On the debian testing machine I have to wait less than 50% of the time than on the other PC. Strange? Is that CPU performance dependent or was the timing changed between Jessie and debian testing? Anyways, I would like to deactivate the sound device in that keyboard so that udev is not waiting anymore. But how? Matthias -- 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/mhtolt$m4o$1...@ger.gmane.org
Re: issue with systemd-udev-settle
Am 30.04.2015 um 15:09 schrieb Michael Biebl: As you can see above, systemd-udevd timeouts processing the events from that device and is eventually killed. The internal timeout for udev is 90s. If you add the the remaining time to boot the system, that would explain the 2min boot times. This looks like either buggy hardware or a bug in the kernel. Can you try with a different keyboard and mouse directly attached to your computer, not via a hub? Yes, that is it. It is the keyboard! I tried a different one and the computer boots fast. The keyboard is not new. I had it running on the same computer for several years. All with debian wheezy. No problems. Why is that now? I doubt that this is a hw issue although I have never tested the sound module in that keyboard. What can I do about it? I like this keyboard. I do not want to replace it. Can I deactivate probing for usb sound? Matthias -- 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/mhtfs7$r27$1...@ger.gmane.org
Re: issue with systemd-udev-settle
tive Driver Activation Cmd: "modprobe snd_usb_audio" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #62 (Hub) 58: USB 00.3: Unclassified device [Created at usb.122] Unique ID: fwlK.e6_dCN4Dx+9 Parent ID: Uc5H.TI3vE1oZtwF SysFS ID: /devices/pci:00/:00:12.2/usb1/1-4/1-4.4/1-4.4:1.3 SysFS BusID: 1-4.4:1.3 Hardware Class: unknown Model: "Elan Microelectronics USB Audio" Hotplug: USB Vendor: usb 0x04f3 "Elan Microelectronics Corp." Device: usb 0x0a11 "USB Audio" Revision: "1.00" Driver: "usbhid" Driver Modules: "usbhid" Speed: 12 Mbps Module Alias: "usb:v04F3p0A11d0100dc00dsc00dp00ic03isc00ip00in03" Driver Info #0: Driver Status: usbhid is active Driver Activation Cmd: "modprobe usbhid" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #62 (Hub) Does that help? Matthias -- 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/mhsg4m$uo5$1...@ger.gmane.org
Re: issue with systemd-udev-settle
Am 29.04.2015 um 10:32 schrieb Christian Seiler: Just use journalctl (without -b) to see all messages (they are still in RAM in the journal - as per the log you posted, journald will use up to 80 MiB [2] which is more than enough to keep all 3000 or so messages). Just look through them (there are going to be a lot of debug messages from udev) and look at the timestamps. There you'll be able to see where the delay happens - and maybe you'll have a chance of figuring out, what the problem is. If it's nothing obvious, just post the last 20 or so udev messages before the large gap in the timestamps and every udev message afterwards. If there is no gap and udev is constantly doing something, take a look at what it's actually doing. No way. Just using journalctl makes no difference: Apr 29 18:45:08 xxx systemd-journal[170]: Forwarding to syslog missed 3819 messages. Apr 29 18:45:14 xxx systemd-journal[170]: Suppressed 2818 messages from /system.slice/systemd-udevd.service And this is exactly the time period where I would expect the issue to pop up. Any other idea? Matthias -- 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/mhr2a3$vu4$1...@ger.gmane.org
Re: issue with systemd-udev-settle
Am 29.04.2015 um 15:28 schrieb Michael Biebl:
Am 29.04.2015 um 10:32 schrieb Christian Seiler:
Am 2015-04-29 07:15, schrieb Matthias Bodenbinder:
systemd-analyze blame:
56.397s systemd-udev-settle.service
Yeah, that shouldn't happen.
Matthias, do you have any custom udev rules in /etc/udev/rules.d/?
Is this an upgraded or freshly installed system?
This is a clean install. I tried to upgrade from wheezy but could not
boot afterwards. boot eror "init not found" and I was left with and
initramd shell. I could not fix that so I made a clean install.
/etc/udev/rules.d/ has only one file:
xxx - root - /etc/udev/rules.d
17# cat 70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:24:1d:d6:df:5f", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
Matthias
--
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/mhr1i8$f41$1...@ger.gmane.org
Re: issue with systemd-udev-settle
Hello Christian, first of all many thanks for your very detailed reply. This was excellent! I activated systemd-udev-settle again and want to debug the situtation according to your instructions (with udev.log-priority etc.). Here is the time consumption: systemd-analyze blame: ## 56.397s systemd-udev-settle.service 2.735s postfix.service 482ms NetworkManager.service 470ms lvm2-activation-early.service 456ms ModemManager.service 363ms systemd-logind.service 336ms alsa-restore.service 333ms rc-local.service 333ms speech-dispatcher.service 332ms pppd-dns.service 332ms exim4.service 330ms minidlna.service 328ms openvpn.service 326ms dovecot.service 251ms avahi-daemon.service 213ms networking.service 146ms keyboard-setup.service 136ms console-setup.service 126ms kdm.service 125ms systemd-modules-load.service 117ms systemd-fsck@dev-vol\x2dgrp1-lv_1.service 111ms systemd-fsck@dev-disk-by\x2duuid-68a8248c\x2d38fd\x2d4d5c\x2d83fa\x2da2aff3ff9ce5.service 110ms kbd.service 97ms systemd-fsck@dev-disk-by\x2duuid-22c1ca3a\x2dc781\x2d46b2\x2d98d3\x2de2a5733d68d2.service 90ms lvm2-monitor.service 84ms packagekit.service 73ms nfs-common.service 71ms saned.service 68ms rpcbind.service 58ms raid5.mount 52ms udisks2.service 44ms polkitd.service 43ms rsyslog.service 40ms systemd-user-sessions.service 38ms user@1000.service 38ms colord.service 37ms systemd-udev-trigger.service 36ms systemd-fsck@dev-disk-by\x2duuid-5085c7fb\x2d926d\x2d4f44\x2db8d0\x2d78b571f805d7.service 35ms lvm2-activation.service 28ms systemd-tmpfiles-setup-dev.service 26ms systemd-update-utmp.service 26ms systemd-journal-flush.service 25ms rtkit-daemon.service 24ms upower.service 22ms lvm2-pvscan@8:17.service 22ms media-data.mount 16ms media-data2.mount 15ms systemd-remount-fs.service 15ms dev-mqueue.mount 14ms sys-kernel-debug.mount 13ms systemd-setup-dgram-qlen.service 13ms dev-hugepages.mount 12ms systemd-tmpfiles-setup.service 11ms systemd-random-seed.service 8ms kmod-static-nodes.service 8ms sys-fs-fuse-connections.mount 8ms var-tmp.mount 8ms systemd-update-utmp-runlevel.service 8ms systemd-sysctl.service 7ms dev-disk-by\x2duuid-13030826\x2d8987\x2d46c9\x2dbc1f\x2d8a9e9a4549c9.swap 7ms tmp.mount 6ms home.mount 5ms systemd-udevd.service 1ms udev-finish.service But I am not really happy with the log since I find the following statement when doing a journalctl -b: start of log Apr 29 06:51:55 xxx systemd-journal[164]: Runtime journal is using 8.0M (max allowed 79.2M, trying to leave 118.8M free of 784.2M available → current limit 79.2M). Apr 29 06:52:19 xxx systemd-journal[164]: Forwarding to syslog missed 3819 messages. Apr 29 06:52:25 xxx systemd-journal[164]: Suppressed 2818 messages from /system.slice/systemd-udevd.service Looks like I am missing plenty of udev log messages during the critical phase of the boot process. Any idea what to do about it? Thanks for your help. Matthias -- 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/554068f4.8090...@bodenbinder.de
Re: no ntp installed
Am 28.04.2015 um 16:38 schrieb Michael Biebl: An alternative is, to use systemd-timesyncd.service, which is already shipped in the systemd package, but disabled by default. It's more lightweight then ntp and doesn't do all the fancy tricks ntp does. It also doesn't provide an NTP server. For most users timesyncd should be sufficient, so you can just run $ systemctl enable systemd-timesyncd.service $ systemctl start systemd-timesyncd.service Thank you for this hint. I will try this in favor of ntp. Lets see how that works. How can I montior this service to check if it works correctly? By the way, is there a comprehensive documentation for all the systemd services which are available. Matthias -- 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/mhppn3$r42$1...@ger.gmane.org
issue with systemd-udev-settle
Hi, I installed debian 8 on one of my PCs and got into trouble with extra long boot times of > 2 min. I found out that it due to systemd-udev-settle.service. My PC is using lvm and that somehow interferes with systemd-udev-settle.service. The web tells that systemd-udev-settle.service is needed for lvm. Nevertheless I deactivated it with systemctl mask systemd-udev-settle The PC is booting fast now and the logical volumne is mounted just fine. Q1) So what is the thing about systemd-udev-settle being needed for lvm? Do I miss something? Q2) Is there a way to set a shorter timeout value for systemd-udev-settle.service? Thanks Matthias -- 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/mhn6vs$hlm$1...@ger.gmane.org
no ntp installed
Hi, I installed debian 8 on one of my PCs and found out that no ntp or ntpdate or rdate is installed. How is debian 8 synchronizing the system time? Greetings Matthias -- 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/mhn6d8$6l6$1...@ger.gmane.org
Re: temporarily disable shutdown
Am 29.03.2015 um 17:35 schrieb Michael Biebl: > Am 29.03.2015 um 11:42 schrieb Matthias Bodenbinder: >> Am 28.03.2015 um 18:51 schrieb Michael Biebl: >>> You can run something like >>> >>> systemd-inhibit --what=shutdown --mode=block /bin/sleep 3600 >>> >>> to block shutdown for 1h. >> >> This does NOT work. I tested it with debian testing. > > Are you sure you are using systemd as PID 1? PID 1 is /sbin/init with lrwxrwxrwx 1 root root 20 Feb 13 12:22 /sbin/init -> /lib/systemd/systemd All my tests where with local root: KDE+konsole, as regular user. Either executing "poweroff" via "su -" in the konsole or clicking shutdown button in KDE. Example: In konsole #1: su - systemd-inhibit --what="idle:sleep:shutdown" --mode=block sleep 3600 In konsole #2: su - poweroff The computer is just powered off. Matthias -- 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/mfenu3$qqf$1...@ger.gmane.org
Re: temporarily disable shutdown
Am 28.03.2015 um 18:51 schrieb Michael Biebl: > You can run something like > > systemd-inhibit --what=shutdown --mode=block /bin/sleep 3600 > > to block shutdown for 1h. This does NOT work. I tested it with debian testing. It does not prevent shutdown through hte KDE GUI. And even on the commandline a "poweroff" is still successfully executed. Matthias -- 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/mf8hdu$f5f$1...@ger.gmane.org
Re: temporarily disable shutdown
Hello Michael, that is a very good suggestion. Thank you. But I also have debian stable. Do you have any idea for debain stable as well? Matthias -- 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/mf8apt$j92$1...@ger.gmane.org
temporarily disable shutdown
Hi, how can I temporarily disable shutdown or reboot? My use case is the following: I create a file /tmp/NO_SHUTDOWN. If that file exists, a shutdown or reboot should not be possible. I have molly-guard installed and a script in /etc/molly-guard/run.d/ tests the existence of that file and prevents shutdown/reboot on the commandline. But a user in KDE can still do reboot/shutdown from either KDE or even KDM. How can I prevent that with a file /tmp/NO_SHUTDOWN. Thank you for your help Matthias -- 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/mf6odd$lje$1...@ger.gmane.org
Re: shutdown icon changed
Am 18.03.2015 um 07:07 schrieb Matthias Bodenbinder: > Hi, > > I am running debian testing and kde4. The icon theme is oxygen. But the > shutdown icon which is shown in the taskbar and in the menu is the shutdown > icon from the high-contrast theme. Basically this is black-and-white instead > of the red shutdowen icon from the oxygen theme. I opened the systemsettings > and switch back and forth through the different icon themes. All icons are > changed according to my selection except for the shutdown icon. It always > stays the same. > > What is happening here? > > Thanks > Matthias > > I found the root cause: KDE is taking the icons from /usr/share/icons/hicolor/ regardless which theme is actually being used. I neeed to rename the corresponding icons to get it working again: cd /usr/share/icons/hicolor/ find . | grep weg ./scalable/apps/system-shutdown.svg.weg ./48x48/apps/system-reboot.png.weg ./48x48/apps/system-log-out.png.weg ./48x48/apps/system-hibernate.png.weg ./48x48/apps/system-shutdown.png.weg ./48x48/apps/system-suspend.png.weg Those icons got installed by xfce4-session from debian experimental. From my pijnt of view this is a bug in KDE. It should stick to the icons from the selected theme and not go into hicolor. Matthias -- 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/megi78$hh4$1...@ger.gmane.org
Re: shutdown icon changed
Am 18.03.2015 um 07:07 schrieb Matthias Bodenbinder: > Hi, > > I am running debian testing and kde4. The icon theme is oxygen. But the > shutdown icon which is shown in the taskbar and in the menu is the shutdown > icon from the high-contrast theme. Basically this is black-and-white instead > of the red shutdowen icon from the oxygen theme. I opened the systemsettings > and switch back and forth through the different icon themes. All icons are > changed according to my selection except for the shutdown icon. It always > stays the same. > > What is happening here? > > Thanks > Matthias > > Actually, it is 3 icons that always stay the same: shutdown, logoff and restart. Matthias -- 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/meb5ok$pgp$1...@ger.gmane.org
shutdown icon changed
Hi, I am running debian testing and kde4. The icon theme is oxygen. But the shutdown icon which is shown in the taskbar and in the menu is the shutdown icon from the high-contrast theme. Basically this is black-and-white instead of the red shutdowen icon from the oxygen theme. I opened the systemsettings and switch back and forth through the different icon themes. All icons are changed according to my selection except for the shutdown icon. It always stays the same. What is happening here? Thanks Matthias -- 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/meb4nm$e2o$1...@ger.gmane.org
Re: how to remove libsystemd0 from a live-running debian desktop system
2015-02-16 16:26 GMT+01:00 Alastair McKinstry : > [...] > An an example, i've been a long-term linux developer, DD; i've developed > and promoted Linux not just on the desktop but both in embedded systems > and in HPC systems. In all these I've been comfortable that I've been > able to adapt Linux, reconfigure, do what was needed to get it going on > any size of device, and get my changes either accepted upstream, > maintain them locally in my organisation or both. With systemd I don't > think I could do that, and thats very disempowering. Why do you think you can't do that anymore? Systemd is used on embedded devices, reaching from the Jolla smartphone to things like the Vocore or Raspberry Pi. Getting changes accepted upstream is also not a hard thing, systemd is not different from any other upstream we have. Suure, there will be patches which are not in-scope, some will receive criticism, need to be adapted and rewritten, but that happens basically everywhere. For projects using systemd features, adapting them to do what you want also shouldn't be a problem, and the systemd unit files (from the initsystem part of it) can easily be changed and overridden to serve custom needs. So, do you have concrete bad experience? If so, working on that and fixing the associated bugs would be a useful thing to do. > [...] Cheers, Matthias P.S: Does this really have to be crossposted to -user and -devel? -- 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/caknhny9+39n7vcxqmzsfr_fek9ydom3p2hj10gsr7dabed-...@mail.gmail.com
icedove+iceowl+junk +"This message contains an invitation to an event"
Hi, since a few days I am getting the following message when applying the junk filter to my inbox: "This message contains an invitation to an event" I can not do anything about it and it does not tell me which message it means. Any idea how to solve that? 7# dpkg -l | egrep "icedove|iceowl" ii calendar-exchange-provider 3.2.0~beta47-1 all MS Exchange support for iceowl-extension ii calendar-google-provider31.2.0-1 all Google Calendar support for lightning- and iceowl-extension ii icedove 31.2.0-1 amd64mail/news client with RSS and integrated spam filter support ii icedove-l10n-de 1:31.0-1 all German language package for Icedove ii iceowl-extension31.2.0-1 amd64Calendar Extension for Thunderbird/Icedove Greetings Matthias -- 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/m53puo$k0o$1...@ger.gmane.org
Re: iceweasel and dolphin
Scott, you made my day! Your email helped me to solve the issue. Thanks a lot.
dolphin was set as my default file browser:
2# xdg-mime query default inode/directory
dolphin.desktop
I followed your next advice to disable nautilus in /usr/share/dbus-1/services
mv org.freedesktop.FileManager1.service
org.freedesktop.FileManager1.service.bak
After doing that iceweasel used nemo ;-) But not dolphin.
Therefore I edited /usr/share/applications/defaults.list. It listed a whole
bunch of apps in inode/directory incl. nemo
I removed them all except for
inode/directory=kde4-dolphin.desktop
And that was it! iceweasel now uses dolphin to open folders.
Thanks a lot
Matthias
PS
As soon as I enable "org.freedesktop.FileManager1.service" again, iceweasel
switches back to nautilus. Looks like this is leading the mime type
assignments. I would prefer default.list to lead that. Is that just an
iceweasel/firefox thing or intentional for the whole system?
Am 25.11.2014 um 09:28 schrieb Scott Ferguson:
> On 25/11/14 17:17, Matthias Bodenbinder wrote:
>> Hi,
>>
>> I am getting crazy with iceweasel not opening dolphin for "containing
>> folders".
>
> Hi, I run Debian Wheezy, with some backports, Iceweasel 33.1, KDE4[*1]
> and *no* GNOME on this workstation.
>
> [*1] kdebase-bin 4:4.8.4-2 (heavily customised KDE installation)
>
>
> To see the current file browser system association (as your usual user):-
> xdg-mime query default inode/directory
>
> *1.* to make dolphin the default file browser (as your usual user):-
> xdg-mime default dolphin.desktop inode/directory
>
> ***
> Note: that relies on you having a "dolphin.desktop" config file - your
> installation of GNOME, and my not, makes that problematic. If you have
> "locate" installed *and* 'you' are a member of "mlocate" you can check
> for it's existence with "mlocate":-
> mlocate dolphin.desktop
> /usr/share/app-install/desktop/dolphin.desktop
> /usr/share/applications/kde4/dolphin.desktop
>
> *If* you don't get those results you can create them, by downloading
> them from the attachments to this email, and saving them to the correct
> locations (you'll need to change the filenames I've used to indicate
> their future locations, to dolphin.desktop, and mv them from where you
> download them as "root").
> ***
>
> *2.* You 'may' need to disable Nautilus as the default file browser - in
> which case (check for it's existence first with "ls"), as "root":-
> mv /usr/share/dbus-1/services/org.freedesktop.FileManager1.service{,.bak}
>
> Note that's one line of code.
>
> *Further considerations for GNOME possible problems*
> Please note, again, I don't have/use GNOME so I'm forced to guess and
> try and cover all possibilities I can think of (no guarantee that's
> actually *all* - the standard Debian promise applies - "if it breaks you
> get to keep both pieces")
>
> *1.* Check that Nautilus isn't set in default apps:-
> as the usual user:-
> grep -i nautilus /usr/share/applications/defaults.list
> if you get a result, as "root":-
> cp cat /usr/share/applications/defaults.list{,.bak}
> then edit it as "root" and remove the Nautilus line:-
> nano /usr/share/applications/defaults.list
>
> *2.* Repeat step *1.* above with:-
> ~/.local/share/applications/mimeapps.list
> ~/.local/share/applications/defaults.list
>
>
>
> *Further integration of KDE4 and Iceweasel*
>
> *To add KDE's KPart capabilities*
> As root:-
> apt-get -s install kpartsplugin | less
> if you're happy with what will be installed, proceed with the installation:-
> apt-get install kpartsplugin
> Go to System Settings on the KMenu -> Network and Connectivity ->
> KPartsPlugin
> Configure to suit your needs
>
> *To add QT-style-like ability to Iceweasel* (it's a GTK app)
> As root:-
> *1.* apt-get -s install gtk2-engines-oxygen | less
> if you're happy with what will be installed, proceed with the installation:-
> apt-get install gtk2-engines-oxygen
>
> *2.* apt-get -s install kde-config-gtk-style | less
> if you're happy with what will be installed, proceed with the installation:-
> apt-get install kde-config-gtk-style
> org.freedesktop.FileManager1.service.bak
> *3.* Go to System Settings on the KMenu -> Common Appearance and
> Behaviour -> Gtk Configuration
> Configure to suit your needs
>
> *4.* Install a KDE-like theme in Iceweasel (fro
iceweasel and dolphin
Hi, I am getting crazy with iceweasel not opening dolphin for "containing folders". I searched the web for hours and tried everything I found. Working with mimeTypes.rdf in personal iceweasel folder ~/.local/share/applications/mimeapps.list /etc/gnome/defaults.list (I am running KDE but have gnome installed as well) /usr/share/applications/defaults.list /usr/share/applications/mimeinfo.cache adding dolphn.desktop to indode/directory like this inode/directory=dolphin.desktop or this inode/directory=nemo.desktop;caja.desktop;nautilus.desktop;Thunar.desktop;kde4-dolphin.desktop where kde4-dolphin.desktop is the default entry in /usr/share/applications/defaults.list but it does not exist. Changing it to dolphin.desktop does not help. So how to I tell iceweasel to open "containing folders" for downloads with dolphin and not with nautilus? This drives me crazy. Matthias -- 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/m516tp$h8i$1...@ger.gmane.org
Re: "Lennart Poettering Linux" -- some real eye openers here ... don't be blindsided!
Hi, Andrew McGlashan: > Forwarding a message "as is" from another mailing list ... very relevant > to Linux and the systemd dilemma. > No, it is not. Sorry, but requiring an up-to-date kernel (or any other infrastructure you rely on) instead of maintaining workarounds and compatibility code in perpetuity makes perfect sense. If you don't like that choice, you have a lot of legitimate options * use another init * use an older version of systemd * upgrade your kernel * back-port the features you want/need Note that bitching about upstream choices on debian-vote is not included in this list. -- -- Matthias Urlichs signature.asc Description: Digital signature
Re: piece of mind (Re: Moderated posts?)
Hi, Ian Jackson: > You put me in an awkward position. My email was an attempt to get > this discussion shut down on -devel, where it is off-topic and a total > waste of energy. > In that case, you did a poor job of getting this point across. (I misinterpreted it too.) > But your response, using phrases like `dead horse', I agree that this response was not appropriate. Burying this hatchet is not going to happen as long as both "sides" just dig it up again and again. I daresay we have better things to do than that. -- -- Matthias Urlichs signature.asc Description: Digital signature
Re: piece of mind (Re: Moderated posts?)
2014-10-13 18:23 GMT+02:00 Miles Fidelman : > Didier 'OdyX' Raboud wrote: >> >> I really don't buy the argument that "the GR proposal was too quiet to >> be noticed by 6+ people". I mean: the proposition happened to be in the >> middle of the post-TC decision wave, on the mailing lists where it >> belonged. The people who cared about the whole "default init for Debian" >> question _were_ following and contributing to these various lists. I'm >> therefore claiming that the people who missed the GR proposal were not >> sufficiently interested (otherwise they would've been subscribed to >> either -vote or -project, where these proposals belong). I'm also >> thankful that the proposer limited his proposal to these lists (I'd have >> considered a spread of the call over -devel, -user or other lists an >> abuse). >> >> > > Actually - I'd contest that, for four reasons: > > - as I've previously noted - the major impacts of systemd are being (going > to be) felt by sysadmins and upstream developers - who don't necessarily > follow debian-devel all that closely -- or have input > > - the actual GR call for vote was buried on debian-vote - immediately jumped > on regarding wording and procedural discussions You do understand that we have procedured at Debian to handle stuff like GR proposals, right? And that procedure involves posting to debian-vote, so doing that was the right thing to do. > - actual discussion of the GR on -devel was completely swamped by all the > other discussion of systemd That's why it was posted to -vote, where it belonged to. > - folks have just now pointed to the -project list --- this is the first > I've ever heard of that list - and I note that it is not even listed on > https://lists.debian.org/users.html or https://lists.debian.org/devel.html > -- only on the full list of lists, where it's buried without a description > of what it's for Debian Developers know of this (or at least should know of these lists and subscibe to the ones they are interested in). Since we are building the distribution and have to carry the additional work our decisions cause, it's good to follow well-established procedures. That was done here, and the attempt has failed. If users notice these project-internal things is not really a concern - for users we write release notes, and encourage involvement in discussions about the subject (or even explicitly request feedback). So, there is really nothing wrong or broken here, everything works as it should. And the thing we have to do now is to make Jessie as good as possible, and the systemd transition as painless and bug-free as possible. And of course, also document what people need to do if they want sysvinit instead of systemd. Cheers, Matthias -- I welcome VSRE emails. See http://vsre.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/caknhny8jefmhuhieco_bnvncmorq-28znd3fe3socdakhw3...@mail.gmail.com
Re: piece of mind (Re: Moderated posts?)
Hi, Miles Fidelman: > >Judging by the last couple of months, the rest appears to number <6 people. > > A lot more than that, by my count. > Then the question is why almost all of these "lot more" people did not second the GR proposal. > Those who are most impacted are sys admins of servers, and upstream > developers - the two communities most impacted, but that seem to have no say > in the matter. > Correct. So? Debian consists of its members, i.e. people working (in whatever capacity) on Debian itself. _Using_ a distribution does not in itself constitute working on it. Neither does work on an Upstream package. If you want to change that and include users and/or Upstream developers in our constituency more directly, you're free to go ahead and draft/discuss a GR for that. (I might even support it.) But please don't just do this in the context of yet another attempt to express dissatisfaction with the fact that our TC chose systemd: if you do, I do not think you'll achieve anything except more annoyance about the fact that we're discussing this *again*, and further regression to a discussion climate where each&every mention of systemd automatically raises hackles on both "sides". Which will do any number of things, but not improve Debian. And that's, ostensibly, what we're all here for. In any case, users _do_ have a say. They can force their systems to remain on sys5 init, or switch to a different distro if that should also turn out to be unsatisfactory. Likewise, upstream developers can refuse to include unit files or systemd-supporting tidbits (like socket activation) in their source code. Fact is that the vast majority of them don't. There has been no huge outcry among Fedora users about switching to systemd, for example. So, frankly, there doesn't seem to be a need to maufacture one here. I'm not accusing you of doing so, mind you, but sometimes that is what these repeated attempts to warm up Debian's systemd discussion look like. -- -- Matthias Urlichs -- 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/20141013140643.gn3...@smurf.noris.de
Re: bash exorcism experiment ('bug' 762923 & 763012)
Hi, Thorsten Glaser: > Never put “tainted” input into ksh arithmetics, period. The problem is that there's no option akin to perl's Taint mode which tells the shell that some operations / variable contents are OK and some are not. Sure it's a user error, ultimately, but the system doesn't help the user to fix the bug. It doesn't fail safe, indeed it cannot. That's the real failure, and it probably is not even fixable. Of course, there's the flip side: scripts which are so complex that this kind of error can creep in should not be written in Shell in the first place … -- -- Matthias Urlichs signature.asc Description: Digital signature
Re: Reality check.
Hi, Thorsten Glaser: > But Debian beings are not able to distinguish between disrespect > for actions made by some person (while at the same time holding > the person in, somewhat grudging, respect for the other things > they so) and disrespect for that person, all because they focus > on the language used nowadays. So tell me: how else you would distinguish between the two, if not by the language used? This is text email. We don't have anything else here. (Unless you resort to ASCII art.) NOTE: I don't focus on specific words here, four-letter or otherwise. The intent behind the words is what counts. I've been chastised myself, on this list, for using mostly-nice words in a decidedly-non-nice manner, and I'm trying to at least behave as if I had accepted that and was trying to do better next time. ;-) Also, even if "Debian beings" are currently unable to understand this distinction, which in the general case I doubt is true – do you really think this is an acceptable and/or $DEITY-ordained (and therefore unchangeable) state of affairs? > > > Is a proper language more useful than that "we"? > > In Debian, these days, yes. You can use language in a way which expresses that there _is_ (or at least might still be the possibility of) a "we" behind the disagreement you're addressing. … or not. -- -- Matthias Urlichs signature.asc Description: Digital signature
Re: piece of mind (Re: Moderated posts?)
Hi, lee: > I'm sure we could find quite a few supporters for having a GR amongst > the users (here). We don't do a GR among our users. We do that among Debian members/maintainers/developers/take-your-pick. Of those, most … * are perfectly happy with the TC's decision * can live with it * are unhappy, but think that to continue discussing this is way worse than biting the bullet and getting on with actual work * you do know that we plan to release Jessie sometime this decade, right? * are disillusioned about it all and decided to stand aside Judging by the last couple of months, the rest appears to number <6 people. -- -- Matthias Urlichs signature.asc Description: Digital signature
Re: exail missing plugin
I got it. exaile needs "gstreamer0.10-fluendo-mp3" Matthias -- 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/luh2o1$6r9$1...@ger.gmane.org
Re: exail missing plugin
Am 06.09.2014 um 13:48 schrieb Chris Bannister: > On Sat, Sep 06, 2014 at 12:33:37PM +0200, Matthias Bodenbinder wrote: >> Hi, >> >> I just installed exaile 3.3.2-1 for debian testing. But when I try to >> play my mp3 files it says: "no suitable plugins found". What is >> missing? > > root@tal:~# apt-cache show exail > N: Unable to locate package exail > E: No packages found > root@tal:~# > > It seems quite a lot. A lot more information for a starter. BTW, I *am* > running testing. > > > I see the error now: You should look for exaile and not exail Matthias -- 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/luf66l$o8d$3...@ger.gmane.org
Re: exail missing plugin
Am 06.09.2014 um 13:48 schrieb Chris Bannister:
> On Sat, Sep 06, 2014 at 12:33:37PM +0200, Matthias Bodenbinder wrote:
>> Hi,
>>
>> I just installed exaile 3.3.2-1 for debian testing. But when I try to
>> play my mp3 files it says: "no suitable plugins found". What is
>> missing?
>
> root@tal:~# apt-cache show exail
> N: Unable to locate package exail
> E: No packages found
> root@tal:~#
>
> It seems quite a lot. A lot more information for a starter. BTW, I *am*
> running testing.
>
Something wrong with your repos or your package list?
19# apt-cache policy exaile
exaile:
Installiert: 3.3.2-1
Installationskandidat: 3.3.2-1
Versionstabelle:
3.4.0.2-1 0
600 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages
*** 3.3.2-1 0
900 http://ftp.de.debian.org/debian/ testing/main amd64 Packages
100 /var/lib/dpkg/status
0.3.2.2-3 0
800 http://ftp.de.debian.org/debian/ wheezy/main amd64 Packages
Matthias
--
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/luf659$o8d$2...@ger.gmane.org
Re: exail missing plugin
Am 06.09.2014 um 15:29 schrieb Curt: > On 2014-09-06, Matthias Bodenbinder wrote: >> Hi, >> >> I just installed exaile 3.3.2-1 for debian testing. But when I try to >> play my mp3 files it says: "no suitable plugins found". What is >> missing? >> > > Maybe 'gstreamer ffmpeg' (shot in the dark)? > > I did that. But it did not solve the problem. Interesting though that gstreamer0.10-ffmpeg is only in stable and in unstable, but not in testing. That should not be, right? 16# apt-cache policy gstreamer0.10-ffmpeg gstreamer0.10-ffmpeg: Installiert: 0.10.13-5 Installationskandidat: 0.10.13-5 Versionstabelle: *** 0.10.13-5 0 800 http://ftp.de.debian.org/debian/ wheezy/main amd64 Packages 600 http://ftp.de.debian.org/debian/ unstable/main amd64 Packages 100 /var/lib/dpkg/status Matthias -- 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/luf61e$o8d$1...@ger.gmane.org
exail missing plugin
Hi, I just installed exaile 3.3.2-1 for debian testing. But when I try to play my mp3 files it says: "no suitable plugins found". What is missing? 10# exaile INFO: Loading Exaile 3.3.2 on Python 2.7.8... INFO: Loading settings... INFO: Using de_DE UTF-8 locale INFO: Loading plugins... INFO: Loading collection... INFO: Loading devices... INFO: Loading interface... WARNING : Failed to connect to HAL, autodetection of devices will be disabled. INFO: Using GTK+ 2.24.24 INFO: Loading main window... INFO: Connecting main window events... INFO: Loading panels... INFO: Connecting panel events... INFO: Done loading main window... INFO: Playing file:///opt/music/neu/30_seconds_to_mars/a_beautiful_lie/01_attack.mp3 ERROR : ['__class__', '__cmp__', '__delattr__', '__dict__', '__doc__', '__format__', '__getattribute__', '__grefcount__', '__gstminiobject_init__', '__gtype__', '__hash__', '__init__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', 'copy', 'flags', 'parse_async_start', 'parse_buffering', 'parse_buffering_stats', 'parse_clock_lost', 'parse_clock_provide', 'parse_duration', 'parse_error', 'parse_info', 'parse_new_clock', 'parse_qos', 'parse_qos_stats', 'parse_qos_values', 'parse_request_state', 'parse_segment_done', 'parse_segment_start', 'parse_state_changed', 'parse_step_done', 'parse_step_start', 'parse_stream_status', 'parse_structure_change', 'parse _ tag', 'parse_tag_full', 'parse_warning', 'set_buffering_stats', 'set_qos_stats', 'set_qos_values', 'set_seqnum', 'src', 'structure', 'timestamp', 'type'] gstreamer is installed: ii gstreamer-tools 0.10.36-1.4amd64Tools for use with GStreamer ii gstreamer0.10-alsa:amd64 0.10.36-1.3amd64GStreamer plugin for ALSA ii gstreamer0.10-gconf:amd640.10.31-3+nmu3 amd64GStreamer plugin for getting the sink/source information from GConf ii gstreamer0.10-nice:amd64 0.1.7-1amd64ICE library (GStreamer 0.10 plugin) ii gstreamer0.10-plugins-bad:amd64 0.10.23-7.2+b2 amd64GStreamer plugins from the "bad" set ii gstreamer0.10-plugins-base:amd64 0.10.36-1.3amd64GStreamer plugins from the "base" set ii gstreamer0.10-plugins-good:amd64 0.10.31-3+nmu3 amd64GStreamer plugins from the "good" set ii gstreamer0.10-pulseaudio:amd64 0.10.31-3+nmu3 amd64GStreamer plugin for PulseAudio ii gstreamer0.10-tools 0.10.36-1.4amd64Tools for use with GStreamer ii gstreamer0.10-x:amd640.10.36-1.3amd64GStreamer plugins for X11 and Pango ii gstreamer1.0-clutter 2.0.12-1 amd64Clutter PLugin for GStreamer 1.0 ii gstreamer1.0-libav:amd64 1.4.1-1.1 amd64libav plugin for GStreamer ii gstreamer1.0-plugins-bad:amd64 1.4.1-1amd64GStreamer plugins from the "bad" set ii gstreamer1.0-plugins-base:amd64 1.4.1-1amd64GStreamer plugins from the "base" set ii gstreamer1.0-plugins-good:amd64 1.4.1-1amd64GStreamer plugins from the "good" set ii gstreamer1.0-plugins-ugly:amd64 1.4.1-1amd64GStreamer plugins from the "ugly" set ii gstreamer1.0-pulseaudio:amd641.4.1-1amd64GStreamer plugin for PulseAudio ii gstreamer1.0-x:amd64 1.4.1-1amd64GStreamer plugins for X11 and Pango Kind Regards Matthias -- 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/luenu1$qqa$1...@ger.gmane.org
apt-get update during boot
Hi, somehow my system is running an apt-get update or something similar during boot. Whenever I login after boot I can do a "apt-get dist-upgrade" directly because the package list is already up to date. If I am too fast with the "apt-get dist-upgrade" it even complains that the database is locked by another process. waiting a few more seconds solves that. And this is true regardless which desktop I use: kde, xfce or cinnamon. I could not find any hint ffpr apt in /etc/init.d or /etc/xdg/autostart. So where is that apt-get update happening? is it webmin? Greetings Matthias PS I am using debian testing -- 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/lubh85$l5u$1...@ger.gmane.org
Re: Debian on Intel NUC?
On 07/15/2014 02:15 AM, Bob Proulx wrote: > I have been asked if there are any issues running Debian Stable on one > of the newer Intel NUC hardware. Something like this. > > Intel NUC i5 Intel HD Graphics 5000 > http://www.newegg.com/Product/Product.aspx?Item=N82E16856102054 Hi Bob, we are using an Intel NUC Kit D34010WYK at the office (http://www.newegg.com/Product/Product.aspx?Item=N82E16856102053) as monitoring station. > Does anyone have something like this running Debian? Any problems? > > * Graphics? This has the Intel HD Graphics 5000. > * UEFI? > * USB 3.0 ports? We are running Debian Jessie, because we were unable to get the ethernet card working in Wheezy (you can find a thread for a similar problem here: http://forums.debian.net/viewtopic.php?f=17&t=106169&sid=1b4381ea1cd1581910e7b8003458bdb1). > As a side question does anyone know if it is possible to use both the > display port and the hdmi for a dual monitor configuration? Or a > monitor plus projector configuration? Yes, we are a running an multi-monitor setup, it works properly! > Thanks, > Bob regards, matthias -- PGP KeyID: 0xF7BEDB94 Fingerprint: 15B1 56D8 8F67 FAAF 3FA2 76DA E072 A32C F7BE DB94 signature.asc Description: OpenPGP digital signature
Signature of wheezy's linux source package
Hi All, after downloading the most recent linux source package for wheezy on my wheezy system, I noticed that dpkg-source fails to verify its signature: $ dpkg-source -x linux_3.2.57-3+deb7u2.dsc gpgv: Signature made Thu Jun 5 10:38:20 2014 CEST using RSA key ID 1343CF44 gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on ./linux_3.2.57-3+deb7u2.dsc The debian-keyring package is installed. Apparently, the key used for signing the linux source package is included in sid's version of debian-keyring (2014.04.25), but not in wheezy's (2013.04.21). I would expect everything required to verify packages in wheezy to be included in wheezy, so I guess this is a bug. Or am I missing something? TIA, Matthias Grossmann -- 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/201406121832.16796.gross...@googlemail.com
Re: MATE 1.8: issues with sound control
On 04.06.2014 17:34, Ghislain Vaillant wrote: > Any thoughts on a possible solution ? I had the same issues! Go and try volti[1], it worked fine for me. (apt-get install volti) cheers, matthias [1] https://code.google.com/p/volti/ -- PGP KeyID: 0xF7BEDB94 Fingerprint: 15B1 56D8 8F67 FAAF 3FA2 76DA E072 A32C F7BE DB94 signature.asc Description: OpenPGP digital signature
Re: Proposal - preserve freedom of choice of init systems - Linux IS about CHOICE
*Plonk*. -- -- Matthias Urlichs signature.asc Description: Digital signature
Re: rdesktop
On 02/13/2014 04:55 PM, Reco wrote: > Hi, > > On Thu, Feb 13, 2014 at 11:03:07PM +0800, lina wrote: >> > Hi, >> > >> > When I tried to use rdesktop, it showed me >> > >> > ERROR: getaddrinfo: No address associated with hostname > That means that you've tried to connect to a non-resolvable hostname > (i.e. no hostname → IP association). No more, no less. > Quick-and-dirty solution for that is using IP address of the host > instead. > > 1) as Reco wrote, it looks like a wrong, non-resolvable hostname. check your DNS settings. 2) how does the configuration of the windows-host look like? there are 3 possible options to configure for RDP connections: a) do not accept RDP connections b) accept connections from clients running any RDP version c) only accept clients with a RDP version that supports authentication on network-level you might try option b) when using rdesktop to connect to newer version of windows (Vista, 7, 8, Server2kX). cheers, matthias -- PGP KeyID: 0xF7BEDB94 Fingerprint: 15B1 56D8 8F67 FAAF 3FA2 76DA E072 A32C F7BE DB94 signature.asc Description: OpenPGP digital signature
SOLVED: CD drive not showing up anymore
Am 03.12.2013 08:59, schrieb Matthias Bodenbinder: > Hello, > > somehow my computer does not automatically pop up with a message when I enter > a CD or DVD. Not in KDE, GNOME or XFCE. There is no automatic action at all. > I can not even see any log entries when closing the CD tray with a new CD. > But it used to work in the past. This is a new issue to me. > > I am using Debian Testing. It works fine with USB sticks. And it doesnt work > on second PC either which I just installed from scratch with debian testing. > > Any idea what is broken and how to get this working again? > > Thanks > Matthias > > Hi All, the issue is solved: I needed to enable kernel polling via echo 2000 > /sys/module/block/parameters/events_dfl_poll_msecs This is a known bug (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725978) and the issue lies probably in udev. The polling is supposed to be set in /lib/udev/rules.d/60-persistent-storage.rules but somehow it does not work. Also reported here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713877 Matthias -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/l7te4j$n0a$1...@ger.gmane.org
Re: CD drive not showing up anymore
And what I also find strange is, that I do not see ANY log entry when I close the tray with a new CD. Not in syslog, daemon.log, messages or user.log. Can this be a dbus issue? Matthias -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/l7k7tl$d9p$1...@ger.gmane.org
Re: CD drive not showing up anymore
Am 03.12.2013 09:15, schrieb Ralf Mardorf: >>> I have to add that I can mount the CD manually (mount /dev/sr0 >>> /media/cdrom) without problem. >> >> What was upgraded? Take a look at /var/log/apt/history.log, synaptics >> history or what ever you are using to upgrade. > > http://askubuntu.com/questions/21657/show-apt-get-installed-packages-history-via-commandline > > Anything in ~/.xsession-errors? ~/.xsession-errors does not show anything. /var/log/apt/history.log only contains entries from today, but the problem is already a few days old. Dont know when it occured the first time because I am not handling CDs that often. Matthias -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/l7k4j1$98t$1...@ger.gmane.org
Re: CD drive not showing up anymore
Am 03.12.2013 08:59, schrieb Matthias Bodenbinder: > Hello, > > somehow my computer does not automatically pop up with a message when I enter > a CD or DVD. Not in KDE, GNOME or XFCE. There is no automatic action at all. > I can not even see any log entries when closing the CD tray with a new CD. > But it used to work in the past. This is a new issue to me. > > I am using Debian Testing. It works fine with USB sticks. And it doesnt work > on second PC either which I just installed from scratch with debian testing. > > Any idea what is broken and how to get this working again? > > Thanks > Matthias > > I have to add that I can mount the CD manually (mount /dev/sr0 /media/cdrom) without problem. Matthias -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/l7k37e$omr$1...@ger.gmane.org
CD drive not showing up anymore
Hello, somehow my computer does not automatically pop up with a message when I enter a CD or DVD. Not in KDE, GNOME or XFCE. There is no automatic action at all. I can not even see any log entries when closing the CD tray with a new CD. But it used to work in the past. This is a new issue to me. I am using Debian Testing. It works fine with USB sticks. And it doesnt work on second PC either which I just installed from scratch with debian testing. Any idea what is broken and how to get this working again? Thanks Matthias -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/l7k311$n6k$1...@ger.gmane.org
configure gnome help page
Hi All, I had MINT LMDE installed on my PC but moved back to Debian Testing. I did not do a clean reinstall but simply changed the repositories and the pinning. If I start the Help function now in a gnome terminal or nautilus - either via F1 or "Help" menu - the system still opens the MINT URL: http://www.linuxmint.com/documentation.php How can I change that? And what would be the correct URL in Debian Testing? Thanks in advance Matthias -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/l5fcj6$8vf$1...@ger.gmane.org
Re: ZFS, longterm archive of data and Debian
Nick Lidakis wrote: > I have been Googling for the last week on file systems like ZFS and the > best way to store and preserve data that needs to be read on a regular > basis. I've read many conflicting opinions, in particular about ZFS, and > was hoping to get some opinions on this list. > > Like many music lovers I've ditched the CD player and have a Debian based > music server that fetches music from a big hard drive on my desktop box > via NFS. Most of my music is ripped from my personal collection of CDs > I've amassed over the years. But I've been purchasing quite a few high > resolution titles from online sources such as HDTracks and Channel > Classics. > > I'm trying to think of the best way to preserve the integrity of these > music files over the long term. I've read good things about FreeNAS and > its ZFS implementation but that would require assembling a separate > machine. The conflicting reports regard CPU power and the amount of RAM > one needs to run ZFS, e.g., 1GB per TB of disk space. I'm running ZFS within a virtual machine on an E450 (AMD 2x1,65GHz). You need a lot of RAM and high CPU power if you use the block-deduplication. But I would assume block-deduplication will not have any benefit for music or videos. The online-compression didn't need much RAM but CPU power. Like deduplication I would assume compression will not have any benefit for you. ZFS will calculate checksums over the files and can verify this by scrubbing the device. This will help you only if you have configured a zraid or a mirror. > > With one user reading one FLAC file at a time from a machine running ZFS > does one need a modern CPU and gobs of RAM? I understand ECC RAM and a 64 > bit OS is recommended. No. You have to export the ZFS filesystem with NFS or SMB to access it from another machine. The client will only read the data from network. All work have to be done by the server. The server must have a 64bit OS. 32bit isn't supported. ECC RAM isn't necessary. Do you know what the benefit of ECC? > > Can my desktop run ZFS on the discs with the music files and use a > separate disk with ext3 for my daily tasks? If yes, should I run 64bit > Debian or just use lots of RAM and PAE? ZFS is only a filesystem. So, as other filesystems too, you can have different partitions with differents filesystems. As mentioned above, you need a 64bit non-windows OS. > > Any other suggestions would be appreciated. A Backup inherit the risk to backup a corrupt file and destroy the correct file within your backup. So you need a very intelligent backup solution and a lot of time to find the last correct file to restore. So I would beliefe the best solution for you is either linux software raid or ZFS. Both can verify your data and restore the correct data from the parity/redundancy. -- Don't Panic -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/l21qe2$edf$1...@ger.gmane.org
Xorg/driver assignment
Hello, I have an AMD E450 and I've downloaded and install the amd-driver-installer-catalyst-13-4-x86.x86_64 Now I'm not sure whether the driver is properly installed. Probably there is a configuration problem root@vdr:~# fglrxinfo display: localhost:10.0 screen: 0 OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string: Mesa DRI Intel(R) Q35 OpenGL version string: 1.4 Mesa 8.0.5 root@vdr:~# aticonfig --query-monitor Default Adapter - AMD Radeon HD 6320 Graphics Connected monitors: none Enabled monitors: none root@vdr:~# lsmod | grep fglrx fglrx5170830 65 button 12937 1 fglrx root@vdr:~# aticonfig --px-list-active-gpu PowerXpress: Discrete GPU is active (High-Performance mode). root@vdr:~# aticonfig --list-adapters * 0. 00:01.0 AMD Radeon HD 6320 Graphics * - Default adapter root@vdr:~# lspci | grep VGA 00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6320] root@vdr:~# cat /etc/X11/xorg.conf Section "ServerLayout" Identifier "aticonfig Layout" Screen 0 "aticonfig-Screen[0]-0" 0 0 EndSection Section "Module" EndSection Section "Monitor" Identifier "aticonfig-Monitor[0]-0" Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" EndSection Section "Device" Identifier "aticonfig-Device[0]-0" Driver "fglrx" BusID "PCI:0:1:0" EndSection Section "Screen" Identifier "aticonfig-Screen[0]-0" Device "aticonfig-Device[0]-0" Monitor"aticonfig-Monitor[0]-0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection Anybody have a hint how to assign driver and monitor to my GPU? -- Don't Panic -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/l1o70u$10r$1...@ger.gmane.org
wheezy comes with synaptic, why?
Hi! I just installed Wheezy using the netinst non-free image. I used the proposed package-collections. (desktop, print-server, ssh-server, base - if i remember correctly) After first login I noticed that there is synaptic installed in addition to Debians own packaging tools. If you check the repository settings of synaptic you'll notice that they are not consistent with the content of sources.list. I suspect this may lead to problems in some cases. Another small issue: The "Updates" tab of the synaptic settings says: "Notify me of a new Ubuntu version: [always, LTS, never]" Is there any special reason why standard installation puts two tools for the same purpose on my system? kind regards, Matthias signature.asc Description: OpenPGP digital signature
