Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso
Present Situation: I have made another USB port working so now I am using 2 USB sticks. One as debian 8.0 installation media and another to hold firmware .deb packages. But when I try to load the drivers in one of the installation steps it says: "Detected removable media that is not a known driver media. Please make sure that the correct media is inserted. You can still continue if you have an unofficial removable media you want to use. Unknown removable media. Try to load anyway? 1) No 2) Yes" When I checked virtual terminal 4 I could see my hard drive partitions (/dev/sdaX) got probed with /dev/sdb1 (the debian installation stick). It looks like the installer is not checking /dev/sdc. But I am not sure as I can only see a screenfull of messages with no apparent scrolling mechanism. Then I opted for Yes in above message. Then on next screen it said: "No kernel modules were found. This probably is due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive. If you're installing from a mirror, you can work around this problem by choosing to install a different version of debian. The install will probably *fail* to work if you continue without kernel modules Continue the install without loading the kernel modules? 1) No 2) Yes" Again no sign of probing /dev/sdc on tty4. Seeing the fail message I opted No. So what's going on? Is debian installer really probing /dev/sdc and finding firmware files there as expected or do I need to mount/unmout it manually? After saying No in "continue install without loading kernel modules" step, the firmware got loaded correctly or not? (Though this time it didn't ask for brcm/bcm43xx-0.fw) Please help. -- Avinash Sonawane (RootKea) PICT, Pune http://www.rootkea.wordpress.com -- 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/caj9bsw-3knlvu8r5x1kydzdtwcuvzk-5fegwfku8j8yaih5...@mail.gmail.com
Re: issue with systemd-udev-settle
Am 29.04.2015 um 19:23 schrieb Christian Seiler: Just for the purpose of debugging, could you increase RateLimitBurst to 1 or so (i.e. 10x the default value) in /etc/systemd/journald.conf and reboot? (Set it back again after you're done deubgging, else your logs might get flooded.) The 1 value did not help. I deactivated any limits: RateLimitInterval=0 RateLimitBurst=0 Here is what I found: Start of log is at Apr 30 07:27:55 Apr 30 07:27:55 xxx systemd-udevd[60]: starting version 215 # then it is working on all partitions. # sdc is an SSD # sdc2 is swap # sdb1 is lvm Apr 30 07:27:55 xxx systemd-udevd[175]: device 0x7f6bbb28f7b0 has devpath '/devices/pci:00/:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb1' Apr 30 07:27:55 xxx systemd-udevd[175]: restoring old watch on '/dev/sdb1' Apr 30 07:27:55 xxx systemd-udevd[175]: adding watch on '/dev/sdb1' Apr 30 07:27:55 xxx systemd-udevd[175]: device 0x7f6bbb28f7b0 has devpath '/devices/pci:00/:00:11.0/ata3/host2/target2:0:0/2:0:0:0/block/sdc/sdc3' Apr 30 07:27:55 xxx systemd-udevd[175]: restoring old watch on '/dev/sdc3' Apr 30 07:27:55 xxx systemd-udevd[175]: adding watch on '/dev/sdc3' # there are hundreds of udev message for the next 5 sec until 07:28:00 # then there are only a few udev messages for the next 50 sec until 07:28:50 # before hundreds of udev messages start again Apr 30 07:28:01 xxx systemd-udevd[175]: seq 1598 queued, 'add' 'input' Apr 30 07:28:01 xxx systemd-udevd[175]: seq 1599 queued, 'add' 'input' Apr 30 07:28:01 xxx systemd-udevd[175]: seq 1600 queued, 'add' 'input' Apr 30 07:28:01 xxx systemd-udevd[175]: seq 1601 queued, 'add' 'input' Apr 30 07:28:01 xxx systemd-udevd[175]: seq 1602 queued, 'add' 'input' Apr 30 07:28:04 xxx systemd-udevd[175]: validate module index Apr 30 07:28:04 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:07 xxx systemd-udevd[175]: validate module index Apr 30 07:28:07 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:10 xxx systemd-udevd[175]: validate module index Apr 30 07:28:10 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:13 xxx systemd-udevd[175]: validate module index Apr 30 07:28:13 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:16 xxx systemd-udevd[175]: validate module index Apr 30 07:28:16 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:19 xxx systemd-udevd[175]: validate module index Apr 30 07:28:19 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:19 xxx systemd-journal[170]: Forwarding to syslog missed 3809 messages. Apr 30 07:28:22 xxx systemd-udevd[175]: validate module index Apr 30 07:28:22 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:25 xxx systemd-udevd[175]: validate module index Apr 30 07:28:25 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:28 xxx systemd-udevd[175]: validate module index Apr 30 07:28:28 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:31 xxx systemd-udevd[175]: worker [196] /devices/pci:00/:00:12.2/usb1/1-4/1-4.4/1-4.4:1.0 timeout; kill it Apr 30 07:28:31 xxx systemd-udevd[175]: seq 1229 '/devices/pci:00/:00:12.2/usb1/1-4/1-4.4/1-4.4:1.0' killed Apr 30 07:28:31 xxx systemd-udevd[175]: validate module index Apr 30 07:28:31 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:34 xxx systemd-udevd[175]: validate module index Apr 30 07:28:34 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:37 xxx systemd-udevd[175]: validate module index Apr 30 07:28:37 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:40 xxx systemd-udevd[175]: validate module index Apr 30 07:28:40 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:43 xxx systemd-udevd[175]: validate module index Apr 30 07:28:43 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:46 xxx systemd-udevd[175]: validate module index Apr 30 07:28:46 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:49 xxx systemd-udevd[175]: validate module index Apr 30 07:28:49 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:49 xxx systemd-journal[170]: Forwarding to syslog missed 22 messages. Apr 30 07:28:50 xxx kernel: usbcore: registered new interface driver snd-usb-audio Apr 30 07:28:50 xxx systemd-udevd[175]: seq 1603 queued, 'add' 'sound' Apr 30 07:28:50 xxx systemd-udevd[175]: seq 1604 queued, 'add' 'sound' Apr 30 07:28:50 xxx systemd-udevd[175]: worker [196] exit Apr 30 07:28:50 xxx systemd-udevd[175]: worker [196] terminated by signal 9 (Killed) Apr 30 07:28:50 xxx systemd-udevd[175]: worker [196] cleaned up
Re: [way OT, but desperate] GoBook speakers (solved)
On Apr 26, 2015, at 5:50 PM, Glenn English wrote: > Is anyone here familiar with GoBook XR-1 laptops? Thank all for the suggestions. The speakers are back on. I don't remember whose idea it was, but in one of the links suggested, I found a link to a site called Troubleshooting Linux Sound: http://troubleshooters.com/linux/sound/sound_troubleshooting.htm Wonderful piece of work. I did several steps, and I don't know which of them worked, but one or more of them did the job. -- Glenn English -- 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/21dbe595-cfdb-4c93-a867-3ae8a2113...@slsware.net
Re: No HDMI-Sound anymore with onboard sound chip "Intel CougarPoint HDMI" after upgrading from Wheezy to Jessie
On 04/29/2015 06:23 PM, Lisi Reisz wrote: On Wednesday 29 April 2015 21:19:33 mailing4362 wrote: OK Ladies, problem ist solved in the spirit of List: "You can always uninstall things if they don't work." Solution: # apt-get remove pulseaudio pavucontrol $ alsamixer unmute S/PDIF which was muted by pulseaudio. Now, I am at least able to play videos _with sound_ again on my HDMI connected TV, after switching Video out also to TV (with xrandr), like it worked before with OD Wheezy. Great. :-) I'm pleased. I thought you had already exhausted the possibilities of pulseaudio. Bad pulseaudio (hm, the author of that piece of software programmed also avahi daemon and systemd...) Don't let's go there... :-/ Again, if alsa isn't set correctly pulse doesn't have a chance. This isn't news. IF you have only one sound device, then you don't need pulse. But, if you have HDMI plus USB headphones with a builtin mike, and another sound source like a webcam mike, then pulse shines for switching between them on the fly. Alsa doesn't do that well. But, you must set alsamixer to ummute the audio devices you want to use first, then add pulse / pavucontrol which switches between them. Ric -- My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. http://linuxcounter.net/user/44256.html -- 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/5541af08.5080...@gmail.com
Re: Jessie in VirtualBox: Terminal dies
On 04/29/2015 11:13 PM, dietmar.4...@web.de wrote: I searched for "*term*", and "terminal" seems to be the only installed terminal application. Does any other application open successfully? Examples? I tried other applications like file manager, iceweasel, libreoffice writer - they work fine. Do you have /usr/bin/xterm installed? Shot-in-the-dark. Ric -- My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. http://linuxcounter.net/user/44256.html -- 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/5541a6d2.6070...@gmail.com
Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso
On Thu, Apr 30, 2015 at 3:16 AM, Brian wrote: > Do we assume the firmware files on the FAT partition are .deb packages? > Do you have an existing linux installation? Yes. all firmware files are .deb packages and yes currently I am using Ubuntu. -- Avinash Sonawane (RootKea) PICT, Pune http://www.rootkea.wordpress.com -- 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/caj9bsw9ta1adwqzzaoklmyrug0yzlp6sauygh1vnh7mocte...@mail.gmail.com
Re: Re: Jessie in VirtualBox: Terminal dies
> What kind of terminal? gnome-terminal, xterm, something else ? Do all > terminal applications have a problem? I suppose it's gnome, since gdm3 and gnome-session is running. I have a screenshot here: https://www.dropbox.com/s/j9ofistsyw7pygp/terminal.png?dl=0 I searched for "*term*", and "terminal" seems to be the only installed terminal application. > Does any other application open successfully? Examples? I tried other applications like file manager, iceweasel, libreoffice writer - they work fine. Regards, Dietmar -- 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/trinity-20e1d647-ae9c-4b8c-83a4-8b3d7e4c8943-1430363609691@3capp-webde-bs46
Re: Help with TestDisk
On 4/29/2015 5:41 AM, German wrote: On Tue, 28 Apr 2015 22:24:50 -0700 Seeker wrote: On 4/28/2015 8:03 PM, German wrote: On Tue, 28 Apr 2015 19:06:29 -0700 Seeker wrote: As you can see, there are two directories, but how to view contents of them I have no clue. Enter, P, Right does nothing. In text based programs one dot represents the current directory, two dots represents one level up from the current directory. When you hit 'P' in testdisk to list the contents of the partition, it starts you in the root of the parition. So no list of files and folders indicates no files and folders are recognized in the partition it is showing you. Being at the root of the partition there are no levels above to go to when selecting the two dots and hitting 'enter'. Was this after a deep scan? After deep scan I got one FAT partition 32 MB in size, what is it and what it has to do with NTFS I also have no clue. The error message from the mount attempt was attempting to mount a partition as ntfs. It's fairly common for drives to ship with one small parition to hold the software that ships with the drive and a larger partition for backup/data storage. Often the small partition would be FAT and the large one NTFS. I think that physically ok. I just was installing Lubuntu to my computer and forgot to unplug this USB drive and installer probed it and done to it something nasty. As Murphy said "Anything that can happen, will happen". Could have been a bug in the installer, could be something else that just happened to occur during the Lubuntu install process. Thank you for the effort explaining all that to me. Have a great day. Good luck, if photorec doesn't do it for you either, I have used the Windows version of R-Studio with some success. Have not tried the Linux version and the version I have is old so looks quite a bit different that the screen shots at at the web site. There is a trial version so you can see if it will at least show you some files. http://www.r-studio.com/data_recovery_linux/Download.shtml Don't know about this next one, no Linux version, but looks like they have a trial available as a bootable disk. http://www.prosofteng.com/datarescuepc3/datarescuepcdemo/ Just downloaded it, it's provided as a zip file that extracts to a .exe file, so it may or may not do what it needs to to create a bootable disk in Wine. Later, Seeker -- 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/55419b30.6050...@comcast.net
Re: initramfs broken on Jessie upgrade
Forget the Call Trace, but I get a Kernel panic very like http://users.birkenwald.de/~berni/volatile/783620.png when I follow these instructions carefully: https://www.debian.org/releases/stable/i386/ch04s03.html.en#usb-copy-isohybrid 4.3.3. Manually copying files to the USB stick - the flexible way IOW the last line is the same. I can't speak for the rest. My syslinux.cfg is default linux append initrd=initrd.gz as these are the files copied in from boot.img.gz. I have also copied initrd.gz from the netinst.iso. (The kernels are the same apart from their name.) Same result. As reported in another thread, boot.img.gz works fine when zcat'd directly to the same stick. Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150430024959.GA21528@alum
Re: Jessie: XFCE4 Desktop background stopped working
Johann Spies wrote: > Since Jessie became stable, there is a flat gray background on the XFCE4 > desktop and I cannot change it. My normal configuration is that XFCE4 > should use a list of pictures and change the background regularly > (something that I don't think the other systems can do). This is not > working anymore. After seeing your mail, I was able to configure my background to rotate through multiple images on Jessie. When you say you are unable to change from the gray background, what are the steps you are trying? On the Desktop Settings dialog, what choice is selected under "Image" (right-hand side of the "Background" tab)? regards, mike -- 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/15617.1430361733@allegro.localdomain
Re: Jessie and screensaver on lid-close
On 04/29/2015 10:30 AM, Frederic Marchal wrote: On Wednesday 29 April 2015 09:08:41 Gary Roach wrote: On 04/28/2015 05:27 AM, Francesco Ariis wrote: Hello, I recently upgraded my laptop from wheezy to jessie, and everything is going smoothly. I run a very simple system, with X but no DE. I would like to lock the screen when the lid of my laptop is closed (by running xscreensaver, which I currently have installed, if possible, but any other method will do). How to do it? After searching a bit I suspect I have to mess with systemd configuration files, but I am not sure which one to edit. This doesn't answer you question exactly but I would like to point out that screen savers are useless with lcd / led screens. They were originally meant to protect CRT's from burn in when the electron beam stayed in the same place too long. I don't use them anymore. So unless you just like the pretty pictures, turn them off. Not quite right. I have seen LCD screens where the login screen was burned in the screen leaving a clearly visible and annoying shadow at all time. So, it isn't a good idea to leave the same display on the screen for a long period of time even if LCD screens are more robust than CRT monitors and some people claim it is possible to get rid of the shadow. Moreover, it makes sense to have a screen saver to turn the display and backlight off. It saves a lot of energy on a laptop. Frederic I bow to your experience but, for the life of me, I can't see how this could happen with the physics that is involved. I suppose that the liquid crystal material could deteriorate with time but I thought that the stuff was pretty indestructible. As follow on: Getting rid of the screen saver turns the screen power off sooner. Gary R. -- 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/554184d6.1090...@verizon.net
Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso
Quoting Avinash Sonawane (root...@gmail.com): > On Wed, Apr 29, 2015 at 8:26 PM, David Wright > wrote: > > Quoting Avinash Sonawane (root...@gmail.com): > >> I am trying to install Debian 8.0 on my system. While installing it > >> reported some firmware being missing (more specifically > >> brcm/bcm43xx-0.fw) so I downloaded the firmware files from > >> http://cdimage.debian.org/cdimage/unofficial/non-free/firmware/jessie/current/ > >> > >> I am using USB stick as an installation media which I accomplished using > >> $ dd if= of=/dev/sdb bs=4M; sync > > > > I'm not sure which iso you downloaded. If it was the netinst version > > from https://www.debian.org/releases/jessie/debian-installer/ > > take a look further down the page where there's a panel with a red > > cross. Here you can get the netinst iso with firmware included within > > it. bcm43xx-0.fw 96224 Jun 15 2014 is in there. > > I downloaded > http://cdimage.debian.org/debian-cd/8.0.0/amd64/iso-dvd/debian-8.0.0-amd64-DVD-1.iso > whose integrity I checked using sha512sum, sha256sum and md5sum. I > also verifies gpg signatures for the same. So I am pretty sure I have > the official Debian 8.0 dvd1 iso. > > I am stuck at how to create a separate partition to hold the firmware > files as mentioned in Debian Installation guide. This is what I did: http://ftp.debian.org/debian/dists/stable/main/installer-i386/current/images/hd-media/boot.img.gz I downloaded that (~40MB), and zcat boot.img.gz > /tmp/boot.img I mounted it (1GB) mount /tmp/boot.img /mnt and it looks very much like the /isolinux/ directory on the netinst CD. It has one kernel and two initrds, a text and a gtk one, corresponding to the files which accompany boot.img.gz at the website. I copied my installation iso file and the drivers that I use cp -i .../foo.iso .../driverfoo.fw .../drivebar.fw /mnt/ then unmounted it and copied it to a stick cp -i /tmp/boot.img /dev/sdX Then I booted with that stick as normal. This only works if the iso fits into the remainder of the 1GB "partition"---except it's not actually a partition: the stick will mount thus mount /dev/sdX /mnt and not mount /dev/sdX1 /mnt Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150430013515.GA20032@alum
Jessie and Chrome
Hi, All: I had a bug when I installed Jessie, and I'd like to finish confirming it. Specifically, the GPU process in Google Chrome takes up 50 percent plus of the CPU utilization - not memory, CPU utilization. Using the --disable-GPU command line parameter cures the problem somewhat. Anyone have any idea what changed from Wheezy to cause this? -- 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/55417cf8.9070...@gmail.com
Re: Jessie with ATI Radeon HD 4250 boots black screen after installing drivers...
On Wed, Apr 29, 2015 at 1:23 PM, The Wanderer wrote: > I have a laptop which also has a 4000-series Radeon GPU, and I run it > with the non-proprietary driver from the xserver-xorg-video-radeon > package instead. It's not as performant as the proprietary FGLRX > equivalent would probably be, if one were available, but it does work; > the proprietary driver went away in testing some time last year, and I > haven't had any particular problems with the free alternative. I used to have this ATI graphics chip, and it worked well then with the open Radeon driver. I'd try that. -- Steven Rosenberg http://stevenrosenberg.net/blog http://blogs.dailynews.com/click -- 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/CALDrw3M8UF0DRvR3OQj6JA6=qfsexjmkbyeie9j4+jcx+ur...@mail.gmail.com
Re: Is anyone else having trouble sending mail from Jessie?
On Thu, 30 Apr 2015, Lisi Reisz wrote: I was being ironic. Even sarcastic. Which is why you are so valuable to this group. -- These are not the droids you are looking for. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/alpine.deb.2.20.3.1504292024540.5...@arjgebyy.fvkgvrffheivibe.bet
Re: Is anyone else having trouble sending mail from Jessie?
On Wednesday 29 April 2015 21:41:32 Bob Holtzman wrote: > On Wed, Apr 29, 2015 at 08:31:06AM +0100, Lisi Reisz wrote: > > On Wednesday 29 April 2015 01:04:47 Bob Holtzman wrote: > > > On Tue, Apr 28, 2015 at 09:09:03AM +0100, Lisi Reisz wrote: > > > > On Tuesday 28 April 2015 01:23:41 John J. Boyer wrote: > > > > > I did not have this problem with Ubuntu. > > > > > > > > Ubuntu, of course, is the solution to all ills. > > > > > > > > What I don't understand, is why people who think so, don't just use > > > > Ubuntu. > > > > > > How about Marvelous Mark's dictatorial attitude? That's reason enough > > > for me. > > > > Yes, but you're not claiming that Ubuntu is marvellous, wonderful and the > > solution to all ills! Or are you? > > You can bet your last nickel it wasn't me. Unless I misread the quotes, > I thought it was you. You misread the quotes. John Boyer complained of something and then said that he didn't have this problem with Ubuntu. I meant that I did wish that people who think that Ubuntu is the solution to all ills, would just use Ubuntu, and I don't understand why they don't. I was being ironic. Even sarcastic. Lisi -- 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/201504300116.05363.lisi.re...@gmail.com
Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso
Quoting Avinash Sonawane (root...@gmail.com): > On Wed, Apr 29, 2015 at 9:50 PM, David Wright > wrote: > > > But my workaround (to reduce bandwidth as much as I could) would be to > > install with firmware-netinst as far as the first reboot and then use > > the DVD you've got from then on. > > But then won't Debian will be downloading all the packages from > internet while installing from netinst image? Can I use the existing > amd64 dvd1 iso then? (instead of downloading packages extract from the > dvd1 iso) Yes, though I have little experience of that. You could try putting the DVD (if you've got it or can burn it) in the drive and seeing if it will detect it at the appropriate point (Detect and mount CD-ROM). The really tedious way, which I think works, is to copy deb files from the DVD pool into /target/var/cache/archives using VC2 as early as possible. AFAICT if the installer finds the debs already there, it will gobble them up regardless, and not try to fetch them. The problem is there are an awful lot if you wildcard them, and you don't know which ones it wants so it pays to copy as much as you can manage. Bear in mind you only have a simple shell so it helps to know the DVD layout for wildcarding the files. > But then just to have a single 10MB firmware file is it really cool to > download the whole netinst image? Not really. I'm just tossing ideas about. Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150429232906.GA17908@alum
Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso
Quoting Avinash Sonawane (root...@gmail.com): > A new development: > > Now I have managed to create a separate FAT partition using fdisk > which is holding the > firmware files. The reason why earlier I couldn't is because I used > default block values from fdisk. > > Start partition at block more that size of iso - #debian IRC > > Now installer to begins smoothly but it says no firmware was found > though I can see the damn firmware directory in newly created FAT > partition. > > Any pointers? It's difficult for me to figure out what you've ended up with. Anyway, when you copy the iso file to /dev/sdb, I think you'll find that the stick has two partitions, sdb1 is readonly ISO9660 and sdb2 is a vfat. You could try copying the drivers (like brcm/bcm43xx-0.fw) into that vfat partition. I would copy that one, for example, both at top level and under brcm. I think the firmware loader has a pretty good look around for any files it wants. Then, when you get to the stage that it asks for firmware, two things might happen: it finds everything and carries on silently, or else it stops and asks, in which case, VC4 should show you where it has looked, which might help. (If it's scrolled off, then go to VC2 and look at /var/log/syslog) Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150429231624.GA17828@alum
Re: Jessie and screensaver on lid-close
Quoting Sven Hartge (s...@svenhartge.de): > Bob Proulx wrote: > > Gary Roach wrote: > > >> I bow to your experience but, for the life of me, I can't see how > >> this could happen with the physics that is involved. I suppose that > >> the liquid crystal material could deteriorate with time but I thought > >> that the stuff was pretty indestructible. Its mortal enemy is DC voltages being applied. Badly designed circuits can result in an AC imbalance when being overdriven. > > It doesn't make sense to me either but I will add that I have seen the > > "screen burn" effect with LCD displays too. I don't know. I can't > > explain it. I can only report that I have seen it too. > > I guess it has to do with the crystals being no longer able to bend all > the way after a time if they are forced to do so because the pixel is > constantly active. Some explanations and cures at http://en.wikipedia.org/wiki/Image_persistence http://compreviews.about.com/od/monitors/a/LCDBurnIn.htm I think this is different from the burn-in you can get with high-intensity projective displays where the damage results from UV light affecting the optically polarizing layers bonded to the LCDs. Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150429225624.GA16973@alum
Re: Question: Why do you dist-upgrade?
> So a client comes to you as a professional admin. Let's say they have > an aging Squeeze LTS based web server. They want to move to Jessie > which you may have heard is recently released. Would you re-install > their system to Jessie and ask them to reinstall their web site from > scratch? Or would you spend twenty minutes upgrading from Squeeze 6 > to Wheezy 7 and then from Wheezy 7 to Jessie 8? > > I would recommend they stop hosting their own machine and use a hosted service if they do not have a full time admin, actually. I generally haven't done work like that (freelancing or working for an integrator), but this isn't 2005 any more, either. Are there really that many companies - companies without their own IT department - with self hosted, unmanaged servers running around these days? Seriously? And really, running a server on bare metal these days is a total waste. Any hypervisor will make remote work a lot easier, and avoid the whole issue with ssh and rebooting and everything else. Sheesh, it's 2015, ya'll. Sorry for the top posting.
Re: Question: Why do you dist-upgrade?
Not to mention that unlike an install, a dist-upgrade does not require reinstalling all the special configs and tweaks you may have added to the system. Cheers, Ron. -- Sex without love is an empty experience, but, as empty experiences go, it's one of the best. -- Woody Allen -- http://www.olgiati-in-paraguay.org -- -- 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/20150429182725.024d7...@ron.cerrocora.org
Re: No HDMI-Sound anymore with onboard sound chip "Intel CougarPoint HDMI" after upgrading from Wheezy to Jessie
On Wednesday 29 April 2015 21:19:33 mailing4362 wrote: > OK Ladies, > > problem ist solved in the spirit of List: > > "You can always uninstall things if they don't work." > > Solution: > > # apt-get remove pulseaudio pavucontrol > > > > $ alsamixer > > unmute S/PDIF which was muted by pulseaudio. > > Now, I am at least able to play videos _with sound_ again on my HDMI > connected TV, after switching Video out also to TV (with xrandr), like > it worked before with OD Wheezy. Great. :-) I'm pleased. I thought you had already exhausted the possibilities of pulseaudio. > Bad pulseaudio > (hm, the author of that piece of software programmed also avahi > daemon and systemd...) Don't let's go there... :-/ Lisi -- 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/201504292323.35486.lisi.re...@gmail.com
Re: Question: Why do you dist-upgrade?
Bob Proulx wrote: > Tim Kelley wrote: >> I'm a server admin for a living, for the last 25 years, I mean data >> centers and lately, cloud. There a very few conditions that would >> make me dist-upgrade a server, that is absolutely primitive. Servers >> are created from scratch in minutes at will from an SCMS or automated >> install and if not, you are wrong! > I upgrade all of my systems each and every day. Reinstalling them > every day would be insane. Upgrades are trivial. If you already have a setup where you can create a server from a template or from a pre-seeded installer and use something like puppet, salt, ansible _and_ your applications (web or other) are integrated into that workflow, then it will be quicker to just spawn a new system and redeploy your applications. Of course, if you just have 30 servers (random number) then going that way may be more work than to just dist-upgrade the servers. If you have to control 2000 servers (random number again) then you _will_ have an automated setup which does all the grunt work for you. Or ... you go down the rabbit hole of containers like Docker, which are designed to never be upgraded but just rebuild and redeployed, if needed. Grüße, Sven. -- Sigmentation fault. Core dumped. -- 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/2biu9grur...@mids.svenhartge.de
Re: Jessie and screensaver on lid-close
Bob Proulx wrote: > Gary Roach wrote: >> I bow to your experience but, for the life of me, I can't see how >> this could happen with the physics that is involved. I suppose that >> the liquid crystal material could deteriorate with time but I thought >> that the stuff was pretty indestructible. > It doesn't make sense to me either but I will add that I have seen the > "screen burn" effect with LCD displays too. I don't know. I can't > explain it. I can only report that I have seen it too. I guess it has to do with the crystals being no longer able to bend all the way after a time if they are forced to do so because the pixel is constantly active. In contrast to a cathode ray tube where the phosphor of the pixel will detoriate over time and get dimmer and dimmer the "burned in" LCD pixel can be healed by quickly switching it from on to off and back for multiple hours. Grüße, Sven. -- Sigmentation fault. Core dumped. -- 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/1biu997ur...@mids.svenhartge.de
A few pixels are missing at the left and right of screen
I have just installed Debian 8.0 (Jessie), amd64 port. I have a Samsung E2420 monitor. The video board uses the AMD (ATI cedar) Radeon HD 5450 chip set. I had to install firmware-linux-nonfree to get the full 1920 x 1280 resolution. In Jessie, a few pixels at the left and right of the screen are off the edge of the monitor. The same thing happened in up-to-date Wheezy but all the missing pixels are on the right side of the screen. If I adjust the monitor to move the screen to the right, a black edge of the display appears at the left side of the monitor, but the pixels are still missing. My guess is that the monitor is displaying every pixel it received. Perhaps the video driver or the software is chopping off the display. How do I fix this? -- 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/55414f48.1070...@comcast.net
Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso
On Wed 29 Apr 2015 at 21:43:21 +0530, Avinash Sonawane wrote: > A new development: > > Now I have managed to create a separate FAT partition using fdisk > which is holding the > firmware files. The reason why earlier I couldn't is because I used > default block values from fdisk. > > Start partition at block more that size of iso - #debian IRC That is a good piece of advice. Thanks. > Now installer to begins smoothly but it says no firmware was found > though I can see the damn firmware directory in newly created FAT > partition. > > Any pointers? Do we assume the firmware files on the FAT partition are .deb packages? Do you have an existing linux installation? -- 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/29042015224208.f63923d18...@desktop.copernicus.demon.co.uk
Re: Setting up AP with hostapd
csanyi...@gmail.com wrote:
> What could be the problem?
I don't know but here is my working configuration. I am not running
in bridge mode. I am running in router mode.
Bob
In /etc/network/interfaces:
allow-hotplug wlan0
iface wlan0 inet static
address 192.168.93.1
netmask 255.255.255.0
hostapd /etc/hostapd/hostapd-wlan0.conf
up service isc-dhcp-server restart
down service isc-dhcp-server stop
In /etc/hostapd/hostapd-wlan0.conf:
dump_file=/tmp/hostapd.dump
ctrl_interface=/var/run/hostapd
interface=wlan0
driver=nl80211
ssid=myssidnamehere
channel=11
wpa=2
wpa_passphrase=mypassphrasehere
wpa_pairwise=CCMP
rsn_pairwise=CCMP
hw_mode=g
wmm_enabled=1
ieee80211n=1
ht_capab=[HT40-][SHORT-GI-40][HT20][SHORT-GI-20]
In /etc/dhcp/dhcpd.conf:
# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;
# option definitions common to all supported networks...
option domain-name "proulx.com";
option domain-name-servers 192.168.230.109, 192.168.230.119;
default-lease-time 600;
max-lease-time 7200;
# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
authoritative;
subnet 192.168.93.0 netmask 255.255.255.0 {
option routers 192.168.93.1;
range 192.168.93.100 192.168.93.254;
}
signature.asc
Description: Digital signature
Re: Question: Why do you dist-upgrade?
Bob Proulx wrote: Tim Kelley wrote: I'm a server admin for a living, for the last 25 years, I mean data centers and lately, cloud. There a very few conditions that would make me dist-upgrade a server, that is absolutely primitive. Servers are created from scratch in minutes at will from an SCMS or automated install and if not, you are wrong! So a client comes to you as a professional admin. Let's say they have an aging Squeeze LTS based web server. They want to move to Jessie which you may have heard is recently released. Would you re-install their system to Jessie and ask them to reinstall their web site from scratch? Or would you spend twenty minutes upgrading from Squeeze 6 to Wheezy 7 and then from Wheezy 7 to Jessie 8? I know what I would do. I would upgrade. (After ensuring a proper backup. Backups are needed regardless.) Debian is all about being able to upgrade. I know what I would do with our servers: - for our virtualization environment (Xen) - I'd reinstall from scratch - for our VMs - I'd rebuild each one from scratch In my experience, lots of glitches accumulate from upgrade to upgrade. Better to take the opportunity to build a clean system. I might add that this is particularly the case with Jessie - in that systemd changes so many things that I wouldn't trust an automated process in any way, shape, manner, or form. (Of course, I'm REALLY conservative - I'm just getting ready to upgrade some systems to Wheezy. From there, I'm seriously considering a migration to BSD.) Miles Fidelman -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra -- 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/55414d3b.2000...@meetinghouse.net
Re: Jessie and screensaver on lid-close
Gary Roach wrote: > I bow to your experience but, for the life of me, I can't see how this > could happen with the physics that is involved. I suppose that the > liquid crystal material could deteriorate with time but I thought that > the stuff was pretty indestructible. It doesn't make sense to me either but I will add that I have seen the "screen burn" effect with LCD displays too. I don't know. I can't explain it. I can only report that I have seen it too. Bob signature.asc Description: Digital signature
Re: Question: Why do you dist-upgrade?
Tim Kelley wrote: > I'm a server admin for a living, for the last 25 years, I mean data centers > and lately, cloud. There a very few conditions that would make me > dist-upgrade a server, that is absolutely primitive. Servers are created > from scratch in minutes at will from an SCMS or automated install and if > not, you are wrong! So a client comes to you as a professional admin. Let's say they have an aging Squeeze LTS based web server. They want to move to Jessie which you may have heard is recently released. Would you re-install their system to Jessie and ask them to reinstall their web site from scratch? Or would you spend twenty minutes upgrading from Squeeze 6 to Wheezy 7 and then from Wheezy 7 to Jessie 8? I know what I would do. I would upgrade. (After ensuring a proper backup. Backups are needed regardless.) Debian is all about being able to upgrade. I upgrade all of my systems each and every day. Reinstalling them every day would be insane. Upgrades are trivial. BTW... A request to all. Please trim your quoted replies. Top posting on top of hundreds of lines is poor form. Take a look at this posting for example. There were 7 lines of original content in it. Yet the entire message was 189 lines. That is a lot of noise to have to wade through to read those 7 lines of original content. https://lists.debian.org/debian-user/2015/04/msg01743.html Bob signature.asc Description: Digital signature
Re: Power completely drained in hibernate mode?
Darac Marjal wrote: > Patrick Wiseman wrote: > > Any thoughts about how to diagnose what's going on? (It's also > > painfully slow to get back up to speed coming out of hibernation, but > > that's another story.) > > First off, see if you have any lights on on the machine while it's > hibernated. If there is a sleep light, or if the power light "pulses", > for example, then the machine hasn't hibernated. > > Next, see if your system is configured for "hybrid sleep". Hybrid Sleep > is like sleep, but the system is additionally saved to disk. That way, > if the battery dies, a resume-from-hibernation can be performed. Check > /etc/systemd/login.conf in case any of the Handle* options are set to > hybrid-sleep. Another suggestion... After hibernating remove the battery from the laptop. If it still drains then you know it is a failing battery. Batteries sometimes fail with a high internal current which causes them to drain internally. Bob signature.asc Description: Digital signature
Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso
Curt wrote: > Is it just me or is the option to install an alternative desktop > environment missing from the advanced options of both amd64 netinstall > isos ( official and firmware-unofficial)? The desktop option has been added to the tasksel stage. It is a better place for it. # tasksel -t --new-install --list-tasks u desktop Debian desktop environment u gnome-desktop GNOME u xfce-desktop Xfce u kde-desktop KDE u cinnamon-desktop Cinnamon u mate-desktop MATE u lxde-desktop LXDE u web-serverweb server u print-server print server u ssh-serverSSH server u standard standard system utilities Bob signature.asc Description: Digital signature
Re: Debian 8 Display corruption and previous desktop revelation during login (nouveau)
On 29/04/15 20:04, Nick Booker wrote: > Selected details from lspci, glxinfo and dmesg in the following paste: > > http://paste.debian.net/169967/ Sorry that one was set to expire too quickly. Here's a new one set to expire never: http://paste.debian.net/170024/ -- 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/55413fef.4010...@nickbooker.uk
Re: Jessie: Problem switching from graphical to text-based login
Am 29.04.2015 um 22:29 schrieb Michael Biebl: > Am 29.04.2015 um 21:31 schrieb Reiner Bühl: >> Hi, >> >> I have installed a new system with Debian Jessie and Xfce. When I try >> to disable lightdm via systemctl, X11 is stopped as expected, but >> after the next restart, the graphical login is back. I do not want to >> uninstall lightdm, but just disable the automatic start of X11 and >> lightdm. What is the way to do this with systemd? >> >> "systemctl disable lightdm.service" seems to not do it. > > Please try "systemctl set-default multi-user.target" > > The default is graphical.target, which pulls in display-manager.service. To get the current default target use $ systemct get-default You can always switch it back to graphical mode by using $ systemctl set-default graphical.target You can also change the default target temporarily on the kernel command line. For that add "systemd.unit=multi-user.target" to the kernel command line. This requires a display manager which set's up the display-manager.service symlink correctly. Currently, lightdm and gdm3 do, patches for kdm are being worked on. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Jessie in VirtualBox: Terminal dies
On Tue, Apr 28, 2015 at 05:58:10AM +0200, dietmar.4...@web.de wrote: > Hi, > > I just installed Jessie in a Virtualbox environment (running on Win7 64Bit) > without any problems. > The installed system starts up fine. > > But when I try to open a terminal in the window manager, the icon and a > "waiting cursor" appears for some seconds, then they close. Seems that the > terminal died... > > I tried with several configurations (GNOME, KDE), but no success... > > Any ideas? What kind of terminal? gnome-terminal, xterm, something else ? Do all terminal applications have a problem? Does any other application open successfully? Examples? -- 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/20150429204209.GA15941@side
Re: Is anyone else having trouble sending mail from Jessie?
On Wed, Apr 29, 2015 at 08:31:06AM +0100, Lisi Reisz wrote: > On Wednesday 29 April 2015 01:04:47 Bob Holtzman wrote: > > On Tue, Apr 28, 2015 at 09:09:03AM +0100, Lisi Reisz wrote: > > > On Tuesday 28 April 2015 01:23:41 John J. Boyer wrote: > > > > I did not have this problem with Ubuntu. > > > > > > Ubuntu, of course, is the solution to all ills. > > > > > > What I don't understand, is why people who think so, don't just use > > > Ubuntu. > > > > How about Marvelous Mark's dictatorial attitude? That's reason enough > > for me. > > Yes, but you're not claiming that Ubuntu is marvellous, wonderful and the > solution to all ills! Or are you? You can bet your last nickel it wasn't me. Unless I misread the quotes, I thought it was you. -- Bob Holtzman A fair fight is the result of poor planning. -- 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/20150429204131.ga17...@cox.net
Re: Question: Why do you dist-upgrade?
>*Grumble* x86 desktop users. So many things are taken for granted. >No offense meant. I'm a server admin for a living, for the last 25 years, I mean data centers and lately, cloud. There a very few conditions that would make me dist-upgrade a server, that is absolutely primitive. Servers are created from scratch in minutes at will from an SCMS or automated install and if not, you are wrong! Tim Kelley On Wed, Apr 29, 2015 at 3:23 PM, Reco wrote: > Hi. > > On Wed, 29 Apr 2015 13:52:07 -0500 > Tim Kelley wrote: > > > Tim Kelley > > > > > > On Wed, Apr 29, 2015 at 12:13 PM, Reco wrote: > > > > > Hi. > > > > > > On Wed, 29 Apr 2015 11:11:52 -0500 > > > Tim K wrote: > > > > > > > For me, and I think anyone with a sensibly laid out system, it's so > much > > > > less trouble and time to reinstall. > > > > > > While the amount of trouble is subjective, the install/upgrade time is > > > objective. And it's the last one that you estimated wrong. > > > > > > An debian-installer, being a complex frontend to debootstrap, install > > > packages and configures them. It also does disks partitioning, and the > > > whole process requires two reboots (to installer and to a new system). > > > > > > An upgrade process installs the packages, configures them, but does not > > > do partitioning. Also requires a single reboot that can be postponed > > > indefinitely. > > > > > > An upgrade is simply faster. > > > > > > > Hm. Not for me, anyway. None of those reboots matter to me much. > > Get yourself a server hardware. Every reboot equals to 20-30 minutes on > hardware self-tests alone. Every reinstall requires that *magic* > firmware of very specific version (non-free, of course, so it's not > included in Debian CD). > > Don't like server hardware? Get yourself a VPS, where every reinstall > requires you to communicate with those "friendly" overseas support guys. > And you'll be lucky if they don't charge you extra for console access. > > Don't need a VPS? Get yourself an ARM board where every $DEITY-damn > *model* requires its' own street magic special trickery to run the > installer. > > *Grumble* x86 desktop users. So many things are taken for granted. > No offense meant. > > > > > I can only really think of one reason > > > > to dist-upgrade, and that's if the system is remote (and a very good > > > reason > > > > it is). I'm wondering why some of you dist-upgrade ... do you just > like > > > it > > > > that way? A habit? > > > > > > Upgrade can be done via SSH. Upgrade retains all my packages installed. > > > The most important thing is - upgrade does its best in handling all > > > those customizations in /etc. > > > > > > Oh absolutely. But it can make /etc cruftier over time. > > # du -sxh /etc > 40M > # du -sxh /etc/.git > 32M > # tune2fs -l /dev/root | grep creat > Filesystem created: Fri Jan 27 23:41:53 2008 > > I can live with that cruft :) > > > > Being able to > > upgrade a distribution remotely is a very nice feature of Debian indeed. > > Debian is not the only one in this regard. > Unless I'm mistaken, the only major distribution which does not > support major version upgrade is RHEL. > > > > > /var contents will do you little good without /etc in most server > > > environments > > > > /var's only separate because of the SSD (trying to activity on it, but > I'm > > not sure that's really even an issue any more) > > In my case, I use the same SCMS at home as I do at work (salt) and that's > > where I configure most everything, and that is backed by remote git, and > > backed up remotely in addition to that, so, I think I'm covered there. > > If you have a backup - it's not an issue. Provided, of course, that > such backup is tested on a regular basis. > > > > You're right though, the new install would be very painful without that, > > since you'd have to change a hundred little things, from /etc/papersize > to > > all the shell settings (which I have a lot of). And I admit it's very > > uncommon for a home user to back their configuration up with an SCMS. > > :) > > > > > > The cons are that firstly, it's very time consuming and much more > > > > complicated. > > > > > > See above. > > > > > > > > You have to admit, there is much more to go wrong on an upgrade than a > > reinstall. > > Yes, indeed. For example, a power outage in a middle of upgrade may > result in unbootable system. > Re-install will end the same, of course, but another re-install will > fix it. > > > > Unless you were super-careful with your backports and software > > from outside the release in general that will cause problems, and while > you > > might say "you should always be careful about that" it's also true that > > most people just aren't. > > That's exactly why they suggest disabling third-party apt sources > before the upgrade :) > > And users who install proprietary software should suffer anyway. > Especially the ones who use so-called "installers". > > > > But yes if you do it right, use /usr/local or /opt >
Re: Re: No HDMI-Sound anymore with onboard sound chip "Intel CougarPoint HDMI" after upgrading from Wheezy to Jessie
OK Ladies, problem ist solved in the spirit of List: "You can always uninstall things if they don't work." Solution: # apt-get remove pulseaudio pavucontrol $ alsamixer unmute S/PDIF which was muted by pulseaudio. Now, I am at least able to play videos _with sound_ again on my HDMI connected TV, after switching Video out also to TV (with xrandr), like it worked before with OD Wheezy. Bad pulseaudio (hm, the author of that piece of software programmed also avahi daemon and systemd...) -- 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/20150429221933.7257c...@koog.heimnetz.zone
Re: Screen resolution in Jessie
Am 29.04.2015 um 21:22 schrieb Gary Roach: > [27.621] (II) AIGLX: Screen 0 is not DRI2 capable > [27.638] (EE) AIGLX: reverting to software rendering > [29.297] (II) AIGLX: Loaded and initialized swrast > [29.297] (II) GLX: Initialized DRISWRAST GL provider for screen 0 I don't see a message about the intel driver being loaded and used successfully, only this error message. Can you provide the full Xorg.0.log somewhere? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Jessie: Problem switching from graphical to text-based login
Am 29.04.2015 um 21:31 schrieb Reiner Bühl: > Hi, > > I have installed a new system with Debian Jessie and Xfce. When I try > to disable lightdm via systemctl, X11 is stopped as expected, but > after the next restart, the graphical login is back. I do not want to > uninstall lightdm, but just disable the automatic start of X11 and > lightdm. What is the way to do this with systemd? > > "systemctl disable lightdm.service" seems to not do it. Please try "systemctl set-default multi-user.target" The default is graphical.target, which pulls in display-manager.service. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Jessie and screensaver on lid-close
Gary Roach wrote: > On 04/29/2015 10:30 AM, Frederic Marchal wrote: >> Not quite right. I have seen LCD screens where the login screen was >> burned in the screen leaving a clearly visible and annoying shadow at >> all time. >> So, it isn't a good idea to leave the same display on the screen for >> a long period of time even if LCD screens are more robust than CRT >> monitors and some people claim it is possible to get rid of the >> shadow. >> >> Moreover, it makes sense to have a screen saver to turn the display >> and backlight off. It saves a lot of energy on a laptop. > I bow to your experience but, for the life of me, I can't see how this > could happen with the physics that is involved. I suppose that the > liquid crystal material could deteriorate with time but I thought that > the stuff was pretty indestructible. The material does not detoriate per se, as the burn in effect is mostly reversible. I had two 27" TFT LCD screens at work which were used by the network guys to display the status overview of the network devices (Nagios status screen). After several months one could see the places where static elements (browser buttons, window borders, etc.) have been. But by using the lcdscrub screensaver from the xscreensaver package every night the "burn marks" were easily remediated. This screensaver displays special patters, for example horizontal black and white line with 1-pixel width, scrolling across the screen, causing the pixels to be switched on and off and on and off very often. This reduces or even eliminates the burn-in effect. Somehow the liquid crystals excercise by doing push-ups and get healthy again ;) Grüße, Sven. -- Sigmentation fault. Core dumped. -- 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/0biu315ur...@mids.svenhartge.de
Re: Question: Why do you dist-upgrade?
Hi. On Wed, 29 Apr 2015 13:52:07 -0500 Tim Kelley wrote: > Tim Kelley > > > On Wed, Apr 29, 2015 at 12:13 PM, Reco wrote: > > > Hi. > > > > On Wed, 29 Apr 2015 11:11:52 -0500 > > Tim K wrote: > > > > > For me, and I think anyone with a sensibly laid out system, it's so much > > > less trouble and time to reinstall. > > > > While the amount of trouble is subjective, the install/upgrade time is > > objective. And it's the last one that you estimated wrong. > > > > An debian-installer, being a complex frontend to debootstrap, install > > packages and configures them. It also does disks partitioning, and the > > whole process requires two reboots (to installer and to a new system). > > > > An upgrade process installs the packages, configures them, but does not > > do partitioning. Also requires a single reboot that can be postponed > > indefinitely. > > > > An upgrade is simply faster. > > > > Hm. Not for me, anyway. None of those reboots matter to me much. Get yourself a server hardware. Every reboot equals to 20-30 minutes on hardware self-tests alone. Every reinstall requires that *magic* firmware of very specific version (non-free, of course, so it's not included in Debian CD). Don't like server hardware? Get yourself a VPS, where every reinstall requires you to communicate with those "friendly" overseas support guys. And you'll be lucky if they don't charge you extra for console access. Don't need a VPS? Get yourself an ARM board where every $DEITY-damn *model* requires its' own street magic special trickery to run the installer. *Grumble* x86 desktop users. So many things are taken for granted. No offense meant. > > I can only really think of one reason > > > to dist-upgrade, and that's if the system is remote (and a very good > > reason > > > it is). I'm wondering why some of you dist-upgrade ... do you just like > > it > > > that way? A habit? > > > > Upgrade can be done via SSH. Upgrade retains all my packages installed. > > The most important thing is - upgrade does its best in handling all > > those customizations in /etc. > > > > Oh absolutely. But it can make /etc cruftier over time. # du -sxh /etc 40M # du -sxh /etc/.git 32M # tune2fs -l /dev/root | grep creat Filesystem created: Fri Jan 27 23:41:53 2008 I can live with that cruft :) > Being able to > upgrade a distribution remotely is a very nice feature of Debian indeed. Debian is not the only one in this regard. Unless I'm mistaken, the only major distribution which does not support major version upgrade is RHEL. > > /var contents will do you little good without /etc in most server > > environments > > /var's only separate because of the SSD (trying to activity on it, but I'm > not sure that's really even an issue any more) > In my case, I use the same SCMS at home as I do at work (salt) and that's > where I configure most everything, and that is backed by remote git, and > backed up remotely in addition to that, so, I think I'm covered there. If you have a backup - it's not an issue. Provided, of course, that such backup is tested on a regular basis. > You're right though, the new install would be very painful without that, > since you'd have to change a hundred little things, from /etc/papersize to > all the shell settings (which I have a lot of). And I admit it's very > uncommon for a home user to back their configuration up with an SCMS. :) > > > The cons are that firstly, it's very time consuming and much more > > > complicated. > > > > See above. > > > > > You have to admit, there is much more to go wrong on an upgrade than a > reinstall. Yes, indeed. For example, a power outage in a middle of upgrade may result in unbootable system. Re-install will end the same, of course, but another re-install will fix it. > Unless you were super-careful with your backports and software > from outside the release in general that will cause problems, and while you > might say "you should always be careful about that" it's also true that > most people just aren't. That's exactly why they suggest disabling third-party apt sources before the upgrade :) And users who install proprietary software should suffer anyway. Especially the ones who use so-called "installers". > But yes if you do it right, use /usr/local or /opt > and /etc/local and /etc/opt, /var/opt and /var/local you should be fine, > but I've never personally met anyone who does that. Or if you kept your > stable plain vanilla - never met anyone who does that either. I did. Basically, it's like this: 'apt-get install' = 'sudo make install' 'apt-get remove' = 'rm -rf' 'apt-get upgrade' = 'um. I'll think of something' IMO if one is using Debian and tries to 'make install' their way - one might as well use Slackware :) > > And that's a perfect example of good software as all those years your > > system booted successfully. > > > > > Well, yes, it is. I'm not dissing upgrading. I'd just rather re-install. There are times then re-install i
Re: Jessie with ATI Radeon HD 4250 boots black screen after installing drivers...
On 04/29/2015 at 04:11 PM, Gábor Hársfalvi wrote: > Hello, > > I have a big problem - I use the official tutorial - > https://wiki.debian.org/ATIProprietary#Debian_8_.22Jessie.22 - but > when I reboot it always give me a black screen. :( Those directions state that they are only for specific models of AMD GPUs: "For support of Radeon R9 200, Radeon R7 200, Radeon HD 8000, Radeon HD 7000, Radeon HD 6000 and Radeon HD 5000 series GPUs" The Radeon HD 4250 is part of the Radeon HD 4000-series, which is not in that supported list. In wheezy, there was a separate fglrx-legacy-driver package, which included support for older graphics cards - including the Radeon HD 4000 series. It was available from the wheezy-backports repository. Although this package is still mentioned in the description of the fglrx-driver package, it does not seem to be available anymore - at least not as far as I can tell at a glance. I have a laptop which also has a 4000-series Radeon GPU, and I run it with the non-proprietary driver from the xserver-xorg-video-radeon package instead. It's not as performant as the proprietary FGLRX equivalent would probably be, if one were available, but it does work; the proprietary driver went away in testing some time last year, and I haven't had any particular problems with the free alternative. The directions on that Wiki page should probably explicitly state that other models are not supported by the available proprietary drivers, and suggest the free driver instead. It may not work ideally well, but it should still work. Alternatively, it _should_ be possible to install the most recent FGLRX legacy driver from AMD's upstream site - but that would lose the advantages of the Debian packaging and the integration which it provides, and the directions for accomplishing it with certainty would be considerably more complicated than what's already on that Wiki page. > Why? And why gives me "aticonfig --initial" "No supported adapters > detected"? Most likely because the 4250 graphics adapter is not supported by the installed driver. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Jessie with ATI Radeon HD 4250 boots black screen after installing drivers...
Hello, I have a big problem - I use the official tutorial - https://wiki.debian.org/ATIProprietary#Debian_8_.22Jessie.22 - but when I reboot it always give me a black screen. :( Why? And why gives me "aticonfig --initial" "No supported adapters detected"? Thanks
Re: ATA resets with Intel 8/C220 and HGST drive
On Mon, Apr 27, 2015 at 03:03:58PM +0200, Nicolas George wrote:
> Summary: I had annoying resets of the SATA bus with a 8 Series/C220 Series
> Chipset controller and a HGST Travelstar 7K1000 drive. I recently managed to
> stop them and as far as I currently know I am satisfied; I write this mail
> in the hope that it may be useful for anyone having similar issues. If you
> do not have that issue and you are not a developer interested in fixing the
> issue more permanently, you can stop reading right now.
>
> Here are the details. The computer is a Zotac ZBox ID91 nettop with a
> proprietary motherboard, and, as stated above, a Travelstar 7K1000 hard
> drive (a 7200 RPM 2.5", an unusual beast). It was installed around June
> 2014, and I noticed the problems some time later, they probably started
> right away.
>
> The distribution was a Debian Jessie (testing) with the packaged kernel,
> probably linux-image-3.14-1-amd64:amd64 at the time; the issue was not fixed
> by upgrades.
>
> The possibly relevant hardware information are these:
>
> CPU: Intel(R) Core(TM) i3-4130T CPU @ 2.90GHz
>
> CPU:
> product: Intel(R) Core(TM) i3-4130T CPU @ 2.90GHz
>
> description: SATA controller
> product: 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI
> mode]
> vendor: Intel Corporation
> physical id: 1f.2
> bus info: pci@:00:1f.2
> version: 05
> width: 32 bits
> clock: 66MHz
> capabilities: storage msi pm ahci_1.0 bus_master cap_list
> configuration: driver=ahci latency=0
> resources: irq:42 ioport:f0b0(size=8) ioport:f0a0(size=4) ioport:f090(size=8)
> ioport:f080(size=4) ioport:f060(size=32) memory:f7d1a000-f7d1a7ff
>
> description: ATA Disk
> product: HGST HTS721010A9
> physical id: 0.0.0
> bus info: scsi@1:0.0.0
> logical name: /dev/sda
> version: A3J0
> serial: [REMOVED]
> size: 931GiB (1TB)
> capabilities: partitioned partitioned:dos
> configuration: ansiversion=5 logicalsectorsize=512 sectorsize=4096
> signature=d3079a6d
>
> The resets happened a few times a day (this computer was is kept on for more
> than a day and suspend is not used), mostly when the disk was in heavy use,
> sometimes as early as during the boot; there was a few good days when they
> did not happen. They were annoying because they caused a few seconds freeze
> of anything reading from disk; AFAIK they never resulted in data corruption.
>
> The corresponding kernel messages look like this:
>
> [ 337.466498] ata2: EH complete
> [ 367.251032] ata2.00: exception Emask 0x10 SAct 0x8 SErr 0x400100
> action 0x6 frozen
> [ 367.251041] ata2.00: irq_stat 0x0800, interface fatal error
> [ 367.251046] ata2: SError: { UnrecovData Handshk }
> [ 367.251053] ata2.00: failed command: WRITE FPDMA QUEUED
> [ 367.251063] ata2.00: cmd 61/08:98:68:3b:40/00:00:6b:00:00/40 tag 19 ncq
> 4096 out
> [ 367.251063] res 50/00:08:68:3b:40/00:00:6b:00:00/40 Emask 0x10
> (ATA bus error)
> [ 367.251068] ata2.00: status: { DRDY }
> [ 367.251075] ata2: hard resetting link
> [ 367.571128] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
> [ 367.577660] ata2.00: configured for UDMA/133
> [ 367.577676] ata2: EH complete
> [ 409.772730] ata2: limiting SATA link speed to 3.0 Gbps
> [ 409.772735] ata2.00: exception Emask 0x10 SAct 0x3fe00 SErr 0x400100
> action 0x6 frozen
> [ 409.772736] ata2.00: irq_stat 0x0800, interface fatal error
> [ 409.772737] ata2: SError: { UnrecovData Handshk }
> [ 409.772739] ata2.00: failed command: READ FPDMA QUEUED
> [ 409.772742] ata2.00: cmd 60/08:48:78:09:41/00:00:01:00:00/40 tag 9 ncq
> 4096 in
> [ 409.772742] res 50/00:28:e0:a3:04/00:00:02:00:00/40 Emask 0x10
> (ATA bus error)
> [ 409.772743] ata2.00: status: { DRDY }
>
> [ 409.772773] ata2.00: failed command: WRITE FPDMA QUEUED
> [ 409.772776] ata2.00: cmd 61/28:88:e0:a3:04/00:00:02:00:00/40 tag 17 ncq
> 20480 out
> [ 409.772776] res 50/00:28:e0:a3:04/00:00:02:00:00/40 Emask 0x10
> (ATA bus error)
> [ 409.772777] ata2.00: status: { DRDY }
> [ 409.772779] ata2: hard resetting link
> [ 410.092732] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
> [ 410.097670] ata2.00: configured for UDMA/133
>
> Last week, hinted by the penultimate line, I tried to lower the speed of the
> SATA link permanently, and it worked. I did this by adding
> "libata.force=2:3.0Gbps" to the kernel command line (configured using
> /etc/default/grub).
>
> Since then, no reset happened; I am confident that seven days without them
> are not a coincidence.
I had a similar experience with a Sony Vaio VGN-NS140 laptop (from 2008)
when its hard drive died a few years ago.
The replacement drives (new or used) that I tried would work for a
little while, usually long enough to install Debian, but would get
corrupted within a few hours. I would see messages like yours above,
about going to a lower SATA speed. From 3.0Gbps to 1.5 Gbps in my case.
But that wouldn't keep the drive from getting corrupted. (Mayb
Re: Jessie and screensaver on lid-close
On 04/29/2015 10:30 AM, Frederic Marchal wrote: On Wednesday 29 April 2015 09:08:41 Gary Roach wrote: On 04/28/2015 05:27 AM, Francesco Ariis wrote: Hello, I recently upgraded my laptop from wheezy to jessie, and everything is going smoothly. I run a very simple system, with X but no DE. I would like to lock the screen when the lid of my laptop is closed (by running xscreensaver, which I currently have installed, if possible, but any other method will do). How to do it? After searching a bit I suspect I have to mess with systemd configuration files, but I am not sure which one to edit. This doesn't answer you question exactly but I would like to point out that screen savers are useless with lcd / led screens. They were originally meant to protect CRT's from burn in when the electron beam stayed in the same place too long. I don't use them anymore. So unless you just like the pretty pictures, turn them off. Not quite right. I have seen LCD screens where the login screen was burned in the screen leaving a clearly visible and annoying shadow at all time. So, it isn't a good idea to leave the same display on the screen for a long period of time even if LCD screens are more robust than CRT monitors and some people claim it is possible to get rid of the shadow. Moreover, it makes sense to have a screen saver to turn the display and backlight off. It saves a lot of energy on a laptop. Frederic I bow to your experience but, for the life of me, I can't see how this could happen with the physics that is involved. I suppose that the liquid crystal material could deteriorate with time but I thought that the stuff was pretty indestructible. As follow on: Getting rid of the screen saver turns the screen power off sooner. Gary R. -- 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/55412615.7040...@verizon.net
Jessie: Problem switching from graphical to text-based login
Hi, I have installed a new system with Debian Jessie and Xfce. When I try to disable lightdm via systemctl, X11 is stopped as expected, but after the next restart, the graphical login is back. I do not want to uninstall lightdm, but just disable the automatic start of X11 and lightdm. What is the way to do this with systemd? "systemctl disable lightdm.service" seems to not do it. Best regards, Reiner -- 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/ae4bf034ab4efc27cc318cb89c2cd...@mail.buehl.net
Debian 8 Display corruption and previous desktop revelation during login (nouveau)
Hi. I'm getting display corruption during login on the latest Debian 8 (Jessie), installed from scratch on an emptied hard disk. I have the MATE desktop environment, and am using the nouveau graphics driver. This didn't happen with my previous OSes (Debian Wheezy, Linux Mint 17.1 or Parabola GNU/Linux bleeding edge). If I boot my machine from cold, having just plugged in: Boot messages progress to lightdm fine All looks normal while interacting with lightdm After entering my login details, before showing the usual MATE desktop elements and wallpaper, the screen is corrupted for a couple of seconds. During that period it is green with various coloured (mostly purple) dots in seemingly-random places. If I then reboot or shut down and start back up without unplugging and waiting for the motherboard to power down, during my next login, rather than the green with purple dots, I get a collage of bits of my previous session's windows (even some long closed before shutdown) displayed. Please can anyone help me to debug and fix this issue? I haven't filed a bug because I don't know where the issue lies at the moment (kernel/systemd/xf86-video-nouveau/...?) I don't mind poking around source code if necessary with a bit of hand-holding. Selected details from lspci, glxinfo and dmesg in the following paste: http://paste.debian.net/169967/ Thanks, Nick -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: Screen resolution in Jessie
On 04/29/2015 09:47 AM, Michael Biebl wrote: Am 29.04.2015 um 18:28 schrieb Gary Roach: I just upgraded to Jessie with no problems. I use a 24" 16x9 monitor. With wheezy, there was a 1920 x 1080? mode that gave the correct aspect ratio for the 16x9 screens. Jessie seems to only have the 4x3 1600x1200 mode. All of my circles are now elipses. Is there a solution to this problem. Is there a different driver out there. I'm using the on board video card on my Intel DP55KG mother board. I am certain that I didn't have this problem with Wheezy. Does /var/log/Xorg.0.log contain any warnings or errors? I assume you use the "intel" driver? Is xserver-xorg-video-intel correctly installed? What does xrandr -q say? OK xrandr -v -q gives: xrandr program version 1.4.2 xrandr: Failed to get size of gamma for output default Screen 0: minimum 640 x 480, current 1600 x 1200, maximum 1600 x 1200 default connected 1600x1200+0+0 0mm x 0mm 1600x1200 0.00* 1280x1024 0.00 1280x960 0.00 1024x768 0.00 800x6000.00 640x4800.00 No 1920 x ? shows up. I re-installed xserver-xorg-video-intel using Aptitude. Nothing changed. There were no warnings or errors in the Xorg.0.log but I did find the following: //(I noticed that it got the screen size right, 520, 320 mm) [27.140] (II) VESA(0): Total Memory: 256 64KB banks (16384kB) [27.140] (II) VESA(0): : Using hsync range of 30.00-83.00 kHz [27.140] (II) VESA(0): : Using vrefresh range of 50.00-61.00 Hz [27.140] (II) VESA(0): : Using maximum pixel clock of 175.00 MHz [27.140] (WW) VESA(0): Unable to estimate virtual size [27.140] (II) VESA(0): Not using built-in mode "1920x1440" (no mode of this name) [27.140] (II) VESA(0): Not using built-in mode "1856x1392" (no mode of this name) [27.140] (II) VESA(0): Not using built-in mode "1792x1344" (no mode of this name) [27.140] (II) VESA(0): Not using built-in mode "1400x1050" (no mode of this name) [27.141] (II) VESA(0): Not using built-in mode "1152x864" (no mode of this name) [27.141] (II) VESA(0): Not using built-in mode "720x400" (no mode of this name) [27.141] (II) VESA(0): Not using built-in mode "640x350" (no mode of this name) [27.141] (II) VESA(0): Not using built-in mode "512x384" (no mode of this name) [27.141] (II) VESA(0): Not using built-in mode "320x240" (no mode of this name) [27.141] (II) VESA(0): Not using built-in mode "320x200" (no mode of this name) [27.141] (--) VESA(0): Virtual size is 1600x1200 (pitch 1600) [27.141] (**) VESA(0): *Built-in mode "1600x1200" [27.141] (**) VESA(0): *Built-in mode "1280x1024" [27.141] (**) VESA(0): *Built-in mode "1280x960" [27.141] (**) VESA(0): *Built-in mode "1024x768" [27.141] (**) VESA(0): *Built-in mode "800x600" [27.141] (**) VESA(0): *Built-in mode "640x480" *[27.141] (**) VESA(0): Display dimensions: (520, 320) mm* [27.141] (**) VESA(0): DPI set to (78, 95) [27.141] (**) VESA(0): Using "Shadow Framebuffer" [27.141] (II) Loading sub module "shadow" [27.141] (II) LoadModule: "shadow" [27.141] (II) Loading /usr/lib/xorg/modules/libshadow.so [27.247] (II) Module shadow: vendor="X.Org Foundation" [27.247]compiled for 1.16.4, module version = 1.1.0 [27.247]ABI class: X.Org ANSI C Emulation, version 0.4 [27.247] (II) Loading sub module "fb" [27.247] (II) LoadModule: "fb" [27.247] (II) Loading /usr/lib/xorg/modules/libfb.so [27.324] (II) Module fb: vendor="X.Org Foundation" [27.324]compiled for 1.16.4, module version = 1.0.0 [27.324]ABI class: X.Org ANSI C Emulation, version 0.4 [27.324] (==) Depth 24 pixmap format is 32 bpp [27.324] (II) Loading sub module "int10" [27.324] (II) LoadModule: "int10" [27.324] (II) Loading /usr/lib/xorg/modules/libint10.so [27.324] (II) Module int10: vendor="X.Org Foundation" [27.324]compiled for 1.16.4, module version = 1.0.0 [27.324]ABI class: X.Org Video Driver, version 18.0 [27.324] (II) VESA(0): initializing int10 [27.324] (II) VESA(0): Primary V_BIOS segment is: 0xc000 [27.324] (II) VESA(0): VESA BIOS detected [27.324] (II) VESA(0): VESA VBE Version 3.0 [27.324] (II) VESA(0): VESA VBE Total Mem: 16384 kB [27.324] (II) VESA(0): VESA VBE OEM: ATI ATOMBIOS [27.324] (II) VESA(0): VESA VBE OEM Software Rev: 12.16 [27.324] (II) VESA(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc. [27.324] (II) VESA(0): VESA VBE OEM Product: CEDAR [27.324] (II) VESA(0): VESA VBE OEM Product Rev: 01.00 [27.324] (II) VESA(0): virtual address = 0x7f66a9821000, physical address = 0xe000, size = 16777216 [27.337] (II) VESA(0): Setting up VESA Mode 0x176 (1600x1200) [27.337] (II) VESA(0): VBESetVBEMode failed, mode set without customized refresh. [27.451] (==) VESA(0): Default visual is TrueColor [27.516] (==) VE
Re: Power completely drained in hibernate mode?
On Wed, Apr 29, 2015 at 10:17 AM, Darac Marjal wrote: > On Wed, Apr 29, 2015 at 09:50:18AM -0400, Patrick Wiseman wrote: >> Hello: >> >> To hibernate, I use 'sudo pm-hibernate' (because the hibernate button >> on my Xfce power manager tells me 'Sleep verb not supported'). I >> thought hibernate mode was not supposed to use any power, but after 4 >> days, my laptop was powerless (it wasn't when I hibernated). > > It should. Hibernate and Off should use almost the same amount of power > (there might be a trickle of usage for monitoring the lid opening). > I Googled the 'sleep verb not supported' and found that at least one person experienced the same problem when Chrome was open with a bunch of open tabs, which is _always_ the case on my laptop. I closed Chrome, and the hibernate button worked. I'll see when next I open that laptop whether hibernate really worked this time. (Could it be Chrome that was draining power even when the machine was hibernated?) >> Any thoughts about how to diagnose what's going on? (It's also >> painfully slow to get back up to speed coming out of hibernation, but >> that's another story.) > > First off, see if you have any lights on on the machine while it's > hibernated. If there is a sleep light, or if the power light "pulses", > for example, then the machine hasn't hibernated. No lights were on or blinking. It _looks_ to be shut down. > Next, see if your system is configured for "hybrid sleep". Hybrid Sleep > is like sleep, but the system is additionally saved to disk. That way, > if the battery dies, a resume-from-hibernation can be performed. Check > /etc/systemd/login.conf in case any of the Handle* options are set to > hybrid-sleep. The options in logind.conf (which I take it you meant) were all commented out, and none defaults to hybrid sleep. Thanks for your insights. Patrick -- 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/cajvvksormcezcuzjcacknahxdlfnajax5_d2jqfvb-ocjjv...@mail.gmail.com
Re: Question: Why do you dist-upgrade?
On 04/29/2015 at 12:11 PM, Tim K wrote: > For me, and I think anyone with a sensibly laid out system, it's so > much less trouble and time to reinstall. I can only really think of > one reason to dist-upgrade, and that's if the system is remote (and a > very good reason it is). I'm wondering why some of you dist-upgrade > ... do you just like it that way? A habit? Because it's the fastest and easiest way to keep the system up-to-date on a regular basis. I dist-upgrade against testing about once a week or so, and it would be just crazy to reinstall that often - especially with an install setup as complicated as the one I have, and with all the extraneous packages (as well as other, manually-compiled, software) I have installed. Even for the case of tracking stable, and thus only needing to do a major upgrade when a point release occurs or testing becomes stable, trying to keep track of everything I'd need to reinstall and reconfigure and so forth would just be far more trouble than it would be worth as a default approach. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Question: Why do you dist-upgrade?
Tim Kelley On Wed, Apr 29, 2015 at 12:13 PM, Reco wrote: > Hi. > > On Wed, 29 Apr 2015 11:11:52 -0500 > Tim K wrote: > > > For me, and I think anyone with a sensibly laid out system, it's so much > > less trouble and time to reinstall. > > While the amount of trouble is subjective, the install/upgrade time is > objective. And it's the last one that you estimated wrong. > > An debian-installer, being a complex frontend to debootstrap, install > packages and configures them. It also does disks partitioning, and the > whole process requires two reboots (to installer and to a new system). > > An upgrade process installs the packages, configures them, but does not > do partitioning. Also requires a single reboot that can be postponed > indefinitely. > > An upgrade is simply faster. > Hm. Not for me, anyway. None of those reboots matter to me much. > I can only really think of one reason > > to dist-upgrade, and that's if the system is remote (and a very good > reason > > it is). I'm wondering why some of you dist-upgrade ... do you just like > it > > that way? A habit? > > Upgrade can be done via SSH. Upgrade retains all my packages installed. > The most important thing is - upgrade does its best in handling all > those customizations in /etc. > > Oh absolutely. But it can make /etc cruftier over time. Being able to upgrade a distribution remotely is a very nice feature of Debian indeed. > > /var contents will do you little good without /etc in most server > environments /var's only separate because of the SSD (trying to activity on it, but I'm not sure that's really even an issue any more) In my case, I use the same SCMS at home as I do at work (salt) and that's where I configure most everything, and that is backed by remote git, and backed up remotely in addition to that, so, I think I'm covered there. You're right though, the new install would be very painful without that, since you'd have to change a hundred little things, from /etc/papersize to all the shell settings (which I have a lot of). And I admit it's very uncommon for a home user to back their configuration up with an SCMS. > > The cons are that firstly, it's very time consuming and much more > > complicated. > > See above. > > You have to admit, there is much more to go wrong on an upgrade than a reinstall. Unless you were super-careful with your backports and software from outside the release in general that will cause problems, and while you might say "you should always be careful about that" it's also true that most people just aren't. But yes if you do it right, use /usr/local or /opt and /etc/local and /etc/opt, /var/opt and /var/local you should be fine, but I've never personally met anyone who does that. Or if you kept your stable plain vanilla - never met anyone who does that either. | And that's a perfect example of good software as all those years your > system booted successfully. > > Well, yes, it is. I'm not dissing upgrading. I'd just rather re-install.
Re: testing or stable
On 04/29/2015 at 11:38 AM, Chris Bannister wrote: > On Mon, Apr 27, 2015 at 02:37:43PM -0400, The Wanderer wrote: > >> The "experimental" repository has no codename, at least not that I >> know of. It is used entirely for packages that developers want to >> make > > My understanding is that it is affectionally referred to as > 'rc-buggy' It had slipped my memory, but now that you mention it, yes, that's correct. (This can be verified in the list of repository symlinks posted by David Wright yesterday, under the Subject of "Debian codenames and distributions".) -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Is anyone else having trouble sending mail from Jessie? Am I?
On 20150429_2219+1200, Richard Hector wrote: > On 29/04/15 19:31, Lisi Reisz wrote: > > On Wednesday 29 April 2015 01:04:47 Bob Holtzman wrote: > >> On Tue, Apr 28, 2015 at 09:09:03AM +0100, Lisi Reisz wrote: > >>> On Tuesday 28 April 2015 01:23:41 John J. Boyer wrote: > I did not have this problem with Ubuntu. > >>> > >>> Ubuntu, of course, is the solution to all ills. > >>> > >>> What I don't understand, is why people who think so, don't just > >>> use Ubuntu. > >> > >> How about Marvelous Mark's dictatorial attitude? That's reason > >> enough for me. > > > > Yes, but you're not claiming that Ubuntu is marvellous, wonderful > > and the solution to all ills! Or are you? > > I don't think the OP did either. He just provided a point of comparison. > > Richard I have been using msmtp for several months. I think its still working for me. Best Regards, -- Paul E Condon pecon...@mesanetworks.net -- 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/20150429181613.ga12...@big.lan.gnu
Re: apt vs aptitude (was ... Re: non-stable packages infestation)
On Mon, Apr 27, 2015 at 09:21:53AM -0300, Francisco M Neto wrote: > I actually miss the good'ol days of dselect. Apart from that I've been using > a combination of apt for small tasks and synaptic for large numbers of > packages. For me, those good old days never ended. I still use dselect. :) -- 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/20150429180738.GB12462@side
Re: Re: No HDMI-Sound anymore with onboard sound chip "Intel CougarPoint HDMI" after upgrading from Wheezy to Jessie
Thanks for the hint with pavucontrol. Unfortunateley, pavucontrol shows in the profile selection menue the HDMI Output always as "unplugged": "Digital Stereo (HDMI) Output (unplugged)" And also the corresponding output device: "HDMI / DisplayPort (unplugged)" Also the sink list shows the device as "available: no". I gues that is the problem. How could I get the HDMI Output recognized as "plugged in", what it really is? (With Ubuntu 14.10 it works) pacmd list-sinks 1 sink(s) available. * index: 52 name: driver: flags: HARDWARE DECIBEL_VOLUME LATENCY FLAT_VOLUME DYNAMIC_LATENCY state: IDLE suspend cause: priority: 9950 volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 18,52 ms max request: 3 KiB max rewind: 64 KiB monitor source: 61 sample spec: s16le 2ch 44100Hz channel map: front-left,front-right Stereo used by: 0 linked by: 1 configured latency: 20,00 ms; range is 0,50 .. 371,52 ms card: 0 module: 6 properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "HDMI 0" alsa.id = "HDMI 0" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "3" alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xfe62 irq 48" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1b.0" sysfs.path = "/devices/pci:00/:00:1b.0/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "1c20" device.product.name = "6 Series/C200 Series Chipset Family High Definition Audio Controller" device.form_factor = "internal" device.string = "hdmi:0" device.buffering.buffer_size = "65536" device.buffering.fragment_size = "32768" device.access_mode = "mmap+timer" device.profile.name = "hdmi-stereo" device.profile.description = "Digital Stereo (HDMI)" device.description = "Internes Audio Digital Stereo (HDMI)" alsa.mixer_name = "Intel CougarPoint HDMI" alsa.components = "HDA:10ec0892,80862002,00100302 HDA:80862805,80862805,0010" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" active port: -- 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/20150429194412.7a6a1...@koog.heimnetz.zone
Re: Jessie and screensaver on lid-close
On Wed, 29 Apr 2015 19:30:19 +0200 Frederic Marchal wrote: > Moreover, it makes sense to have a screen saver to turn the display and > backlight off. It saves a lot of energy on a laptop. Not to mention that some, who make grunting noises in the backwoods, are still using CRT monitors... Cheers, Ron. -- So many beautiful women, and so little time. -- John Barrymore -- http://www.olgiati-in-paraguay.org -- -- 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/20150429134938.29842...@ron.cerrocora.org
Synaptic package?
I just installed new Jessie on my new laptop. I assume it is Synaptic touchpad, but can be wrong. How at all to tell by whom touchpad was made? Anyway, I think it is possible to make my touchpad more responsive. Firmware? Drivers? Clue me in. Thanks. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150429133950.57f51...@asterius.asterius.net
Re: issue with systemd-udev-settle
On 04/29/2015 06:53 PM, Matthias Bodenbinder wrote: > 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. Ah, I only noticed the first message about syslog forwarding. The second message tells us that rate limiting has kicked in, because udev just generates a TON of messages in a short time. Just for the purpose of debugging, could you increase RateLimitBurst to 1 or so (i.e. 10x the default value) in /etc/systemd/journald.conf and reboot? (Set it back again after you're done deubgging, else your logs might get flooded.) Christian -- 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/55411381.7060...@iwakd.de
Re: Jessie and screensaver on lid-close
On Wednesday 29 April 2015 09:08:41 Gary Roach wrote: > On 04/28/2015 05:27 AM, Francesco Ariis wrote: > > Hello, > > > > I recently upgraded my laptop from wheezy to jessie, and everything > > > > is going smoothly. I run a very simple system, with X but no DE. > > > > I would like to lock the screen when the lid of my laptop is closed > > (by running xscreensaver, which I currently have installed, if possible, > > but any other method will do). > > > > How to do it? After searching a bit I suspect I have to mess with systemd > > configuration files, but I am not sure which one to edit. > > This doesn't answer you question exactly but I would like to point out > that screen savers are useless with lcd / led screens. They were > originally meant to protect CRT's from burn in when the electron beam > stayed in the same place too long. I don't use them anymore. So unless > you just like the pretty pictures, turn them off. Not quite right. I have seen LCD screens where the login screen was burned in the screen leaving a clearly visible and annoying shadow at all time. So, it isn't a good idea to leave the same display on the screen for a long period of time even if LCD screens are more robust than CRT monitors and some people claim it is possible to get rid of the shadow. Moreover, it makes sense to have a screen saver to turn the display and backlight off. It saves a lot of energy on a laptop. Frederic -- 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/3380127.lei9z36...@fmarchal.edpnet.be
Re: Question: Why do you dist-upgrade?
Hi. On Wed, 29 Apr 2015 11:11:52 -0500 Tim K wrote: > For me, and I think anyone with a sensibly laid out system, it's so much > less trouble and time to reinstall. While the amount of trouble is subjective, the install/upgrade time is objective. And it's the last one that you estimated wrong. An debian-installer, being a complex frontend to debootstrap, install packages and configures them. It also does disks partitioning, and the whole process requires two reboots (to installer and to a new system). An upgrade process installs the packages, configures them, but does not do partitioning. Also requires a single reboot that can be postponed indefinitely. An upgrade is simply faster. > I can only really think of one reason > to dist-upgrade, and that's if the system is remote (and a very good reason > it is). I'm wondering why some of you dist-upgrade ... do you just like it > that way? A habit? Upgrade can be done via SSH. Upgrade retains all my packages installed. The most important thing is - upgrade does its best in handling all those customizations in /etc. Re-install *can* be done via SSH (although not by default), but that's it. > I keep my /home and my data (/share) and /var on a separate disk and only > the system goes on / (an ssd). /var contents will do you little good without /etc in most server environments. > Still have to painfully deal with outdated > configuration wrt the desktop environments, so I just make a new (fake) > user to see what the new layout is. I stopped using DEs back in 2007, so I can not comment on this. > The cons are that firstly, it's very time consuming and much more > complicated. See above. > Second, and perhaps most importantly, you're going to be left > with older versions of things when a paradigm has changed. If software works *and* is supported by Debian - it's good software, and there's nothing to worry about. If software works *but* is no longer supported by Debian - it's obsolete software, and replacing it with something is a part of post-upgrade process. If software does not work after the upgrade - it's a bug. So if upgrade leaves you with old familiar software - it's a good thing. > I dist-upgraded > for the longest time and was hence completely unaware of grub2 for several > years, since the maintainers of it wisely did not upgrade me to it! And that's a perfect example of good software as all those years your system booted successfully. I mean - grub was able to boot your system. Grub2 is able to boot your system. What's the key difference? > I can > see the same happening with init systems being switched about. You'll get systemd as a result of 'apt-get dist-upgrade' so there's nothing to worry about. > I guess if > you care and read the release notes carefully this won't happen though. And reading release notes *before* the upgrade is considered essential regardless of whenever you're re-installing or upgrading :) Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150429201310.1e1c982f125ac98cf1a9d...@gmail.com
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: Jessie and screensaver on lid-close
On 04/28/2015 05:27 AM, Francesco Ariis wrote: Hello, I recently upgraded my laptop from wheezy to jessie, and everything is going smoothly. I run a very simple system, with X but no DE. I would like to lock the screen when the lid of my laptop is closed (by running xscreensaver, which I currently have installed, if possible, but any other method will do). How to do it? After searching a bit I suspect I have to mess with systemd configuration files, but I am not sure which one to edit. This doesn't answer you question exactly but I would like to point out that screen savers are useless with lcd / led screens. They were originally meant to protect CRT's from burn in when the electron beam stayed in the same place too long. I don't use them anymore. So unless you just like the pretty pictures, turn them off. Gary R -- 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/55410209.7030...@verizon.net
Re: Screen resolution in Jessie
On Wed, 29 Apr 2015 18:30:03 +0200, Gary Roach wrote: > I just upgraded to Jessie with no problems. I use a 24" 16x9 monitor. > With wheezy, there was a 1920 x 1080? mode that gave the correct aspect > ratio for the 16x9 screens. Jessie seems to only have the 4x3 1600x1200 > mode. All of my circles are now elipses. Is there a solution to this > problem. Is there a different driver out there. I'm using the on board > video card on my Intel DP55KG mother board. I am certain that I didn't > have this problem with Wheezy. > > Gary R. My 1920 x 1200 is working fine using the on-chip Intel video system and Jessie. Never tried the x1080. Can you alter the configuration using xrandr ? HTH.. -- 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/mhr2dg$spg$1...@dont-email.me
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: [Debian 8.0 Installation] Firmware files on USB stick with debian iso
On 2015-04-29, Avinash Sonawane wrote: > On Wed, Apr 29, 2015 at 9:50 PM, David Wright > wrote: > > But then won't Debian will be downloading all the packages from > internet while installing from netinst image? Can I use the existing > amd64 dvd1 iso then? (instead of downloading packages extract from the > dvd1 iso) Won't the dvd1 iso install to your usb stick without the firmware for your wireless card? Then, let's say, if you've another usb stick with the firmware on it, you'd copy that firmware to the correct location /lib/firmware/brcm/bcm43xx-0.fw /lib/firmware/brcm/bcm43xx_hdr-0.fw /usr/share/bug/firmware-brcm80211/presubj /usr/share/doc/firmware-brcm80211/changelog.gz /usr/share/doc/firmware-brcm80211/copyright At which point you'd be able to install via a package manager the relevant package so that the package manager knows about it and updates it normally. > But then just to have a single 10MB firmware file is it really cool to > download the whole netinst image? > -- -- 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/slrnmk23a8.2bf.cu...@einstein.electron.org
Re: Screen resolution in Jessie
Am 29.04.2015 um 18:28 schrieb Gary Roach: > I just upgraded to Jessie with no problems. I use a 24" 16x9 monitor. > With wheezy, there was a 1920 x 1080? mode that gave the correct aspect > ratio for the 16x9 screens. Jessie seems to only have the 4x3 1600x1200 > mode. All of my circles are now elipses. Is there a solution to this > problem. Is there a different driver out there. I'm using the on board > video card on my Intel DP55KG mother board. I am certain that I didn't > have this problem with Wheezy. Does /var/log/Xorg.0.log contain any warnings or errors? I assume you use the "intel" driver? Is xserver-xorg-video-intel correctly installed? What does xrandr -q say? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Bluetooth mouse problems on Jessie
On Wed, 29 Apr 2015 17:23:08 +0200 Johann Spies wrote: Hello Johann, >On 29 April 2015 at 11:40, Brad Rogers wrote: >> As Lisi says, you've not eliminated the mouse as the problem (in fact, >> you've probably done the opposite). >Correct! Thanks for opening my eyes for that possibility. You're welcome. >Yes, I have tested it with other batteries also. Do you have access to another mouse you could try? BTW; No need to Cc me, as I'm subbed to the list and will see your replies. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" Keep your drink just give em the money U & Ur Hand - P!nk pgpLFyjE6i3s8.pgp Description: OpenPGP digital signature
Question: Why do you dist-upgrade?
For me, and I think anyone with a sensibly laid out system, it's so much less trouble and time to reinstall. I can only really think of one reason to dist-upgrade, and that's if the system is remote (and a very good reason it is). I'm wondering why some of you dist-upgrade ... do you just like it that way? A habit? I keep my /home and my data (/share) and /var on a separate disk and only the system goes on / (an ssd). Still have to painfully deal with outdated configuration wrt the desktop environments, so I just make a new (fake) user to see what the new layout is. The cons are that firstly, it's very time consuming and much more complicated. Second, and perhaps most importantly, you're going to be left with older versions of things when a paradigm has changed. I dist-upgraded for the longest time and was hence completely unaware of grub2 for several years, since the maintainers of it wisely did not upgrade me to it! I can see the same happening with init systems being switched about. I guess if you care and read the release notes carefully this won't happen though. But Debian was so reliable (I found) that it was pretty much a fire and forget operation with each stable release. What's your reason? Tim Kelley
Screen resolution in Jessie
I just upgraded to Jessie with no problems. I use a 24" 16x9 monitor. With wheezy, there was a 1920 x 1080? mode that gave the correct aspect ratio for the 16x9 screens. Jessie seems to only have the 4x3 1600x1200 mode. All of my circles are now elipses. Is there a solution to this problem. Is there a different driver out there. I'm using the on board video card on my Intel DP55KG mother board. I am certain that I didn't have this problem with Wheezy. Gary R. -- 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/554106b6.10...@verizon.net
Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso
On Wed, Apr 29, 2015 at 9:50 PM, David Wright wrote: > But my workaround (to reduce bandwidth as much as I could) would be to > install with firmware-netinst as far as the first reboot and then use > the DVD you've got from then on. But then won't Debian will be downloading all the packages from internet while installing from netinst image? Can I use the existing amd64 dvd1 iso then? (instead of downloading packages extract from the dvd1 iso) But then just to have a single 10MB firmware file is it really cool to download the whole netinst image? -- Avinash Sonawane (RootKea) PICT, Pune http://www.rootkea.wordpress.com -- 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/caj9bsw-1qwxbjqhnnyvwbg9lxct05zgwoyzwadx92a0hdkd...@mail.gmail.com
Re: [Debian 8.0 Installation] Synaptics touchpad not working in Graphical Install
On Wed, 29 Apr 2015 21:53:52 +0530 Avinash Sonawane wrote: > 3 Days back when I tried to install debian 7.8.0 on my laptop, at the > time of install my mouse touchpad was working just fine. But when I > tried to install Debian 8.0 in graphical way touchpad isn't working at > all. > > Does that mean Jessie lacks the Synaptics driver in default install? > Will I be able to make the touchpad work after installing Debian? > Yes, mine wasn't working either in graphical mode. I did text install and after rebooting my touchpad was working. Go ahead and install in text mode. -- 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/20150429122728.5f667...@asterius.asterius.net
[Debian 8.0 Installation] Synaptics touchpad not working in Graphical Install
3 Days back when I tried to install debian 7.8.0 on my laptop, at the time of install my mouse touchpad was working just fine. But when I tried to install Debian 8.0 in graphical way touchpad isn't working at all. Does that mean Jessie lacks the Synaptics driver in default install? Will I be able to make the touchpad work after installing Debian? -- Avinash Sonawane (RootKea) PICT, Pune http://www.rootkea.wordpress.com -- 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/caj9bsw8n4xuas6hlebarx3++7voypsjmwdgebtxwyjrsrra...@mail.gmail.com
Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso
Quoting Avinash Sonawane (root...@gmail.com): > On Wed, Apr 29, 2015 at 9:18 PM, Curt wrote: > > On 2015-04-29, Avinash Sonawane wrote: > >>> > >>> I'm not sure which iso you downloaded. If it was the netinst version > >>> from https://www.debian.org/releases/jessie/debian-installer/ > >>> take a look further down the page where there's a panel with a red > >>> cross. Here you can get the netinst iso with firmware included within > >>> it. bcm43xx-0.fw 96224 Jun 15 2014 is in there. > >> > >> I downloaded > >> http://cdimage.debian.org/debian-cd/8.0.0/amd64/iso-dvd/debian-8.0.0-amd64-DVD-1.iso > >> whose integrity I checked using sha512sum, sha256sum and md5sum. I > >> also verifies gpg signatures for the same. So I am pretty sure I have > >> the official Debian 8.0 dvd1 iso. > >> > >> I am stuck at how to create a separate partition to hold the firmware > >> files as mentioned in Debian Installation guide. > >> > > > > Yes, you have the official iso, but in order to obviate the difficulties > > you're encountering, David is saying you have the option of downloading the > > unofficial iso with the firmware included (that way you're off and > > running to the races without further ado). > > > > http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/8.0.0/amd64/iso-cd/firmware-8.0.0-amd64-netinst.iso > > I am sorry if I came as rude. Not in the slightest rude. I'm sorry I can't help you get the firmware onto the stick; it's something I will need to do in the future but just haven't had time to figure it out (so I was going to watch for replies to this thread). But my workaround (to reduce bandwidth as much as I could) would be to install with firmware-netinst as far as the first reboot and then use the DVD you've got from then on. I quite understand if even that amount of bandwidth is too much for you. Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150429162021.GA9838@alum
Re: Bluetooth mouse problems on Jessie
On Wednesday 29 April 2015 16:23:08 Johann Spies wrote: > On 29 April 2015 at 11:40, Brad Rogers wrote: > > On Wed, 29 Apr 2015 09:10:25 +0200 > > Johann Spies wrote: > > > > Hello Johann, > > > > >mouse which I have been using for years. I get the message > > >"successfully added but failed to connect". > > > > As Lisi says, you've not eliminated the mouse as the problem (in fact, > > you've probably done the opposite). > > Correct! Thanks for opening my eyes for that possibility. > > > Try the simple things first; Batteries failing, perhaps? > > Yes, I have tested it with other batteries also. Can you use the mouse with another operating system or distro? Can it be made to work anywhere? Presumably bluetooth mice die sometimes as do other rodents. Lisi -- 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/201504291718.18747.lisi.re...@gmail.com
Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso
On 2015-04-29, Curt wrote: >> > > Yes, you have the official iso, but in order to obviate the difficulties > you're encountering, David is saying you have the option of downloading the > unofficial iso with the firmware included (that way you're off and > running to the races without further ado). > > http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/8.0.0/amd64/iso-cd/firmware-8.0.0-amd64-netinst.iso > Is it just me or is the option to install an alternative desktop environment missing from the advanced options of both amd64 netinstall isos ( official and firmware-unofficial)? -- 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/slrnmk20r3.2bf.cu...@einstein.electron.org
Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso
A new development: Now I have managed to create a separate FAT partition using fdisk which is holding the firmware files. The reason why earlier I couldn't is because I used default block values from fdisk. Start partition at block more that size of iso - #debian IRC Now installer to begins smoothly but it says no firmware was found though I can see the damn firmware directory in newly created FAT partition. Any pointers? -- Avinash Sonawane (RootKea) PICT, Pune http://www.rootkea.wordpress.com -- 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/caj9bsw_fqpj41lwpkps0wvyjfcnaxo08s2xk7sdutn-o+dk...@mail.gmail.com
Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso
On Wed, Apr 29, 2015 at 9:18 PM, Curt wrote: > On 2015-04-29, Avinash Sonawane wrote: >>> >>> I'm not sure which iso you downloaded. If it was the netinst version >>> from https://www.debian.org/releases/jessie/debian-installer/ >>> take a look further down the page where there's a panel with a red >>> cross. Here you can get the netinst iso with firmware included within >>> it. bcm43xx-0.fw 96224 Jun 15 2014 is in there. >> >> I downloaded >> http://cdimage.debian.org/debian-cd/8.0.0/amd64/iso-dvd/debian-8.0.0-amd64-DVD-1.iso >> whose integrity I checked using sha512sum, sha256sum and md5sum. I >> also verifies gpg signatures for the same. So I am pretty sure I have >> the official Debian 8.0 dvd1 iso. >> >> I am stuck at how to create a separate partition to hold the firmware >> files as mentioned in Debian Installation guide. >> > > Yes, you have the official iso, but in order to obviate the difficulties > you're encountering, David is saying you have the option of downloading the > unofficial iso with the firmware included (that way you're off and > running to the races without further ado). > > http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/8.0.0/amd64/iso-cd/firmware-8.0.0-amd64-netinst.iso I am sorry if I came as rude. Yes. I am aware of the debian images with firmware included. The reason why I don't want to use that I think they are netinstall images only. And being a student in developing country I am afraid I can't manage the internet needed for the installation. So I would be thankful if you could suggest away to have a firmware work with amd64 dvd1 iso (which I got from a friend) Thank you. Avinash Sonawane (RootKea) PICT, Pune http://www.rootkea.wordpress.com -- 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/caj9bsw-g+uhqvzu8x873unas7zl4z2qe1w7xpmcdzvzvuyq...@mail.gmail.com
Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso
On 2015-04-29, Avinash Sonawane wrote: >> >> I'm not sure which iso you downloaded. If it was the netinst version >> from https://www.debian.org/releases/jessie/debian-installer/ >> take a look further down the page where there's a panel with a red >> cross. Here you can get the netinst iso with firmware included within >> it. bcm43xx-0.fw 96224 Jun 15 2014 is in there. > > I downloaded > http://cdimage.debian.org/debian-cd/8.0.0/amd64/iso-dvd/debian-8.0.0-amd64-DVD-1.iso > whose integrity I checked using sha512sum, sha256sum and md5sum. I > also verifies gpg signatures for the same. So I am pretty sure I have > the official Debian 8.0 dvd1 iso. > > I am stuck at how to create a separate partition to hold the firmware > files as mentioned in Debian Installation guide. > Yes, you have the official iso, but in order to obviate the difficulties you're encountering, David is saying you have the option of downloading the unofficial iso with the firmware included (that way you're off and running to the races without further ado). http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/8.0.0/amd64/iso-cd/firmware-8.0.0-amd64-netinst.iso -- -- 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/slrnmk1vag.2bf.cu...@einstein.electron.org
Re: testing or stable
On Mon, Apr 27, 2015 at 02:37:43PM -0400, The Wanderer wrote: > The "experimental" repository has no codename, at least not that I know > of. It is used entirely for packages that developers want to make My understanding is that it is affectionally referred to as 'rc-buggy' -- "If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing." --- Malcolm X -- 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/20150429153817.GE28736@tal
Re: testing or stable
On Mon, Apr 27, 2015 at 09:02:17AM -0700, Joris Bolsens wrote: > I've been using Debian Jessie for ~ a year now, now that it is stable > should I update to sid? or stick with jessie? > > I enjoy tinkering with everything, so I'm OK with things breaking or > needing some special configuration, hell I'll even patch a thing and > recompile from source if I have to (I know, shocking right). I might try testing for a stretch myself. :) -- "If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing." --- Malcolm X -- 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/20150429153129.GD28736@tal
Re: no ntp installed
Am 29.04.2015 um 15:34 schrieb Michael Biebl: > There is also man systemd.index, an index of all man pages. It's > massive. You should skip all (3) entries, which are API documentation > and only relevant for developers. All man pages are also available for reading online. The aforementioned systemd.index man page can be found at [1] as an entry point to the other man pages. Michael [1] http://www.freedesktop.org/software/systemd/man/ -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Bluetooth mouse problems on Jessie
On 29 April 2015 at 11:40, Brad Rogers wrote: > On Wed, 29 Apr 2015 09:10:25 +0200 > Johann Spies wrote: > > Hello Johann, > > >mouse which I have been using for years. I get the message > >"successfully added but failed to connect". > > As Lisi says, you've not eliminated the mouse as the problem (in fact, > you've probably done the opposite). > Correct! Thanks for opening my eyes for that possibility. > > Try the simple things first; Batteries failing, perhaps? > Yes, I have tested it with other batteries also. Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3)
Re: where adjusts system date/time?
Michael Biebl wrote: >schrieb songbird: >> will it stay masked when updates to systemd come through? > > The mask is created in /etc/systemd/system, which is admin territory, > i.e. not overwritten by the package. > > So your answer is yes. thanks again! i really appreciate having you and other DDs here in debian-user support/help. :) songbird -- 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/dp871c-013@id-306963.user.uni-berlin.de
Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso
On Wed, Apr 29, 2015 at 8:26 PM, David Wright wrote: > Quoting Avinash Sonawane (root...@gmail.com): >> I am trying to install Debian 8.0 on my system. While installing it >> reported some firmware being missing (more specifically >> brcm/bcm43xx-0.fw) so I downloaded the firmware files from >> http://cdimage.debian.org/cdimage/unofficial/non-free/firmware/jessie/current/ >> >> I am using USB stick as an installation media which I accomplished using >> $ dd if= of=/dev/sdb bs=4M; sync > > I'm not sure which iso you downloaded. If it was the netinst version > from https://www.debian.org/releases/jessie/debian-installer/ > take a look further down the page where there's a panel with a red > cross. Here you can get the netinst iso with firmware included within > it. bcm43xx-0.fw 96224 Jun 15 2014 is in there. I downloaded http://cdimage.debian.org/debian-cd/8.0.0/amd64/iso-dvd/debian-8.0.0-amd64-DVD-1.iso whose integrity I checked using sha512sum, sha256sum and md5sum. I also verifies gpg signatures for the same. So I am pretty sure I have the official Debian 8.0 dvd1 iso. I am stuck at how to create a separate partition to hold the firmware files as mentioned in Debian Installation guide. -- Avinash Sonawane (RootKea) PICT, Pune http://www.rootkea.wordpress.com -- 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/CAJ9BSW9RBLcvS=DcuzVCK=wbptiwhhm9g6rt2txajvdqqdl...@mail.gmail.com
Re: where adjusts system date/time?
Am 29.04.2015 um 16:54 schrieb songbird: > will it stay masked when updates to systemd come through? The mask is created in /etc/systemd/system, which is admin territory, i.e. not overwritten by the package. So your answer is yes. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: [way OT, but desperate] GoBook speakers
On Sun, Apr 26, 2015 at 06:39:31PM -0600, Glenn English wrote: > I'll try anything I haven't tried. I played with alsamixer, and it did > just what it looked like it'd do. But I'll follow your suggestions > very carefully. Thanks. I'd also suggest trying with one or more live distributions. -- "If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing." --- Malcolm X -- 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/20150429150023.GC28736@tal
Botched upgrade to jessie
I had completed apt-get upgrade alright, but then the computer was turned off during apt-get dist-upgrade. Now I tried apt-get -f upgrade: […] libaccountsservice0 libapt-pkg4.12 libatasmart4 libatk-adaptor libatk-wrapper-java-jni libatkmm-1.6-1 libavahi-gobject0 libavahi-ui-gtk3-0 libbluetooth3 libbonoboui2-0 libcanberra-gtk-module libcanberra-gtk0 libcanberra-gtk3-0 libcanberra-gtk3-module libcaribou-gtk-module libcaribou-gtk3-module libchamplain-0.12-0 libchamplain-gtk-0.12-0 libclutter-1.0-0 libclutter-gst-1.0-0 libclutter-gtk-1.0-0 libclutter-imcontext-0.1-0 libcluttergesture-0.0.2-0 libcurl3 libcurl3-gnutls libcwidget3 libdee-1.0-4 libdevmapper-event1.02.1 libdevmapper1.02.1 libdirac-encoder0 libdmapsharing-3.0-2 libenchant1c2a libepc-1.0-3 libepc-common libepc-ui-1.0-3 libept1.4.12 libevolution libexempi3 libfarstream-0.1-0 libfolks-eds25 libfolks-telepathy25 libfolks25 libgcj-common libgconf-2-4 libgconf2-4 libgdict-1.0-6 libgeoclue0 libgeocode-glib0 libgimp2.0 libgksu2-0 libglade2-0 libglademm-2.4-1c2a libglib2.0-0 libglib2.0-bin libglibmm-2.4-1c2a libglw1-mesa libgmime-2.6-0 libgnome-keyring-common libgnome-keyring0 libgnome-menu-3-0 libgnomecanvas2-0 libgnomeui-0 libgnomevfs2-0 libgoa-1.0-common libgoffice-0.8-8 libgoocanvas-common libgoocanvas3 libgpod-common libgpod4 libgraphicsmagick3 libgs9 libgs9-common libgssdp-1.0-3 libgstreamer-plugins-bad0.10-0 libgstreamer-plugins-base0.10-0 libgstreamer0.10-0 libgtk-vnc-2.0-0 libgtkglext1 libgtkhtml-4.0-0 libgtkhtml-4.0-common libgtkhtml-editor-4.0-0 libgtkhtml3.14-19 libgtkmm-2.4-1c2a libgtkmm-3.0-1 libgtksourceview2.0-0 libgtkspell0 libgucharmap-2-90-7 libgudev-1.0-0 libgupnp-1.0-4 libgupnp-av-1.0-2 libgutenprintui2-1 libgvnc-1.0-0 libgxps2 libio-socket-ssl-perl libjson-perl libjson0 liblvm2app2.2 libm17n-0 libmission-control-plugins0 libmng1 libmozjs185-1.0 libmtp9 libmx-1.0-2 libmx-common libnautilus-extension1a libneon27-gnutls libnetpbm10 libnice10 libnm-glib4 libnm-gtk-common libnm-gtk0 libnm-util2 libnotify4 libofa0 liboobs-1-5 libopenexr6 libopenraw1 libpam-modules libpam-modules-bin libpam0g libpanel-applet-4-0 libpangomm-1.4-1 libpaper1 libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-gobject-1-0 libquicktime2 libquvi7 librdf0 librest-0.7-0 librest-extras-0.7-0 librpmio3 librsvg2-bin libsemanage-common libsemanage1 libsmbclient libsnmp-base libsoup-gnome2.4-1 libsox2 libspandsp2 libssh2-1 libtag1-vanilla libtag1c2a libtiff-tools libusb-1.0-0 libv4l-0 libv4lconvert0 libvte-2.90-9 libvte-2.90-common libwbclient0 libwmf-bin libwmf0.2-7 libwnck-3-0 libwnck22 libxapian22 libxml++2.6-2 libxslt1.1 libzbar0 lightsoff lm-sensors login lsb lsb-core lsb-cxx lsb-graphics lsb-languages lsb-multimedia lsb-printing lsb-security lshw lshw-gtk menu mount mousetweaks mtink nautilus nautilus-data nautilus-wipe netpbm network-manager network-manager-gnome notification-daemon ntfs-3g packagekit packagekit-tools pan passwd pdf2svg policykit-1 poppler-utils postgresql-common ppp printer-driver-splix python-apt python-aptdaemon python-aptdaemon-gtk python-aptdaemon.gtk3widgets python-aptdaemon.gtkwidgets python-chardet python-crypto python-cups python-gconf python-gdata python-gi python-gi-cairo python-glade2 python-gnome2 python-gobject python-gobject-2 python-gtk2 python-lazr.uri python-libproxy python-mako python-notify python-numpy python-oauth python-opengl python-pexpect python-pkg-resources python-pycurl python-pyorbit python-reportbug python-simplejson python-xapian python-zope.interface quadrapassel reportbug rhythmbox rhythmbox-data rhythmbox-plugin-cdrecorder rhythmbox-plugins samba samba-common samba-common-bin simple-scan smbclient sound-juicer sudo swell-foop synaptic system-tools-backends sysv-rc sysvinit-utils tcl8.5 telepathy-gabble telepathy-haze telepathy-idle telepathy-logger telepathy-mission-control-5 telepathy-rakia telepathy-salut tracker tracker-extract tracker-gui tracker-miner-fs tracker-utils udev ufraw ufraw-batch unattended-upgrades update-notifier upower usbmuxd util-linux util-linux-locales uuid-runtime uvccapture verbiste-gnome vino x11-utils xdg-user-dirs-gtk xmms2-core xmms2-plugin-cdda xsane xsane-common xserver-xephyr xserver-xorg xsltproc zeitgeist-core zenity zenity-common 436 pacotes atualizados, 166 pacotes novos instalados, 19 a serem removidos e 275 não atualizados. 314 pacotes não totalmente instalados ou removidos. É preciso baixar 0 B/518 MB de arquivos. Depois desta operação, 185 MB adicionais de espaço em disco serão usados. Você quer continuar [S/n]? A obter relatórios de bugs... Feito A interpretar a informação de Encontrado/Corrigido... Feito bugs serious do systemd (-> 215-17) #780650 - systemd: Sources not shipped for hwdb files bugs grave do empathy (3.4.2.3-2+deb7u1 -> 3.12.7-1) #735097 - empathy: Empathy 3.8 kfreebsd-amd64 can't open window conversation bugs serious do network-manager (0.9.4.0-10 -> 0.9.10.0-7) #755202 - network-manager: keeps creating and using new con
Re: [Debian 8.0 Installation] Firmware files on USB stick with debian iso
Quoting Avinash Sonawane (root...@gmail.com): > I am trying to install Debian 8.0 on my system. While installing it > reported some firmware being missing (more specifically > brcm/bcm43xx-0.fw) so I downloaded the firmware files from > http://cdimage.debian.org/cdimage/unofficial/non-free/firmware/jessie/current/ > > I am using USB stick as an installation media which I accomplished using > $ dd if= of=/dev/sdb bs=4M; sync I'm not sure which iso you downloaded. If it was the netinst version from https://www.debian.org/releases/jessie/debian-installer/ take a look further down the page where there's a panel with a red cross. Here you can get the netinst iso with firmware included within it. bcm43xx-0.fw 96224 Jun 15 2014 is in there. Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150429145657.GA8454@alum
Re: where adjusts system date/time?
Michael Biebl wrote: > schrieb songbird: >> help? any futher things to try that come to mind? > > That's most likely hwclock-save.service, which is run on shutdown. > This was added due to [1]. Some users where quite adamant, that they > needed it. > > You can mask the unit via > $ systemctl mask hwclock-save.service thank you for your quick answer, i never searched the systemdctl output for hwclock keyword (just time and date). duh <- me... :) done, and we'll see what tomorrow brings... will it stay masked when updates to systemd come through? songbird -- 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/pu771c-iq2@id-306963.user.uni-berlin.de
Re: where adjusts system date/time?
Am 29.04.2015 um 16:28 schrieb songbird: > help? any futher things to try that come to mind? That's most likely hwclock-save.service, which is run on shutdown. This was added due to [1]. Some users where quite adamant, that they needed it. You can mask the unit via $ systemctl mask hwclock-save.service [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755722 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
[Debian 8.0 Installation] Firmware files on USB stick with debian iso
Hi! Debian n00b here! I am trying to install Debian 8.0 on my system. While installing it reported some firmware being missing (more specifically brcm/bcm43xx-0.fw) so I downloaded the firmware files from http://cdimage.debian.org/cdimage/unofficial/non-free/firmware/jessie/current/ I am using USB stick as an installation media which I accomplished using $ dd if= of=/dev/sdb bs=4M; sync After which two partitions /dev/sdb1(4 GB) and /dev/sdb2 (426 KB) got created automatically with 3.8GB of free space remaining on the stick. Now as mentioned in the Debian Installation Guide (https://www.debian.org/releases/stable/amd64/ch04s03.html.en#usb-copy-isohybrid) I want to have those firmware files on the same USB stick since I have only one USB port working. I tried using disks, gparted. But both threw warnings and errors about GPT table. "Error: The backup GPT table is not at the end of the disk, as it should be. This might mean that another operating system believes the disk is smaller. Fix, by moving the backup to the end (and removing the old backup)?" I went along the suggested "fix" options but couldn't create another partition. So then I tried fdisk to create a FAT partition to hold firmware files. It did threw a warning but allowed me to create a partition. "WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted." But then after mounting, copying firmware directory on new FAT partition when I tried to install from USB stick it reported an error saying "isolinux.bin missing or corrupt" and refused to boot from the stick. I am pretty sure it has something to do with the newly created FAT partition and the firmware files copied on it. As initially without firmware files (and the new FAT partition) installation was going smooth. Please direct me to any pointers on to how to have firmware files on USB stick alongside Debian installable image. Thank you. Avinash Sonawane (RootKea) PICT, Pune http://rootkea.wordpress.com -- 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/CAJ9BSW8QRsx8Zdg_vBWdQB_=wrjv6smszx79af6htz_qa8u...@mail.gmail.com
Re: making thumbnails
http://www.imagemagick.org/script/mogrify.php On 29/04/2015 2:28 AM, "Steve Greig" wrote: > I have about 60 large jpg files in a directory. They are almost all over > 2MB in size. I want to put them on the internet but wanted to make a > thumbnail version and a small version (about 75KB) of each one so the web > page does not take too long to load. Normally I just open them in GIMP and > modify them and save the smaller versions. Because there are 60 this is > going to take quite a lot of time. > > Is there a utility available for Debian that could do them all. I imagine > one could write a bash script invoking imagemagick but I have never written > a bash script or used imagemagick so might be quite out of my depth there. > > Any ideas would be very much appreciated, Steve >
where adjusts system date/time?
i reboot this system several times a day, it is not always connected to the network, it makes no sense to try to adjust the time or drift factors when it isn't connected... a while ago i had things working exactly as i wanted. which means, the system clock only gets adjusted when i manually enter the hwclock command. otherwise it is not altered. then i started getting the message from hwclock when i did manually do the update: "Not adjusting drift factor because it has been less than a day since the last calibration." so someplace someone is adjusting this and i am trying to find where that is so i can stop it from happening... i've already made sure /etc/networks has no bits of ntpdate in it anywhere and /etc/network/interfaces has no mention of anything time related. also, can't see any place that it is in any of the cron scripts. also, made sure systemd time-sync is disabled. help? any futher things to try that come to mind? thanks! songbird -- 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/dd671c-ij2@id-306963.user.uni-berlin.de
Re: Power completely drained in hibernate mode?
On Wed, Apr 29, 2015 at 09:50:18AM -0400, Patrick Wiseman wrote: > Hello: > > To hibernate, I use 'sudo pm-hibernate' (because the hibernate button > on my Xfce power manager tells me 'Sleep verb not supported'). I > thought hibernate mode was not supposed to use any power, but after 4 > days, my laptop was powerless (it wasn't when I hibernated). It should. Hibernate and Off should use almost the same amount of power (there might be a trickle of usage for monitoring the lid opening). > > Any thoughts about how to diagnose what's going on? (It's also > painfully slow to get back up to speed coming out of hibernation, but > that's another story.) First off, see if you have any lights on on the machine while it's hibernated. If there is a sleep light, or if the power light "pulses", for example, then the machine hasn't hibernated. Next, see if your system is configured for "hybrid sleep". Hybrid Sleep is like sleep, but the system is additionally saved to disk. That way, if the battery dies, a resume-from-hibernation can be performed. Check /etc/systemd/login.conf in case any of the Handle* options are set to hybrid-sleep. > > Patrick > > > -- > 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/cajvvksodm_-ze03r_h6hb5mmmqjhdafgt8ywgcee0kyomg3...@mail.gmail.com > signature.asc Description: Digital signature
Re: no ntp installed
Am 29.04.2015 um 15:34 schrieb Michael Biebl: > journalctl -u systemd-timesyncd.service This command needs to be run as root. Or you add your user to the systemd-journal group, to grant read privileges for the system journal. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Power completely drained in hibernate mode?
Hello: To hibernate, I use 'sudo pm-hibernate' (because the hibernate button on my Xfce power manager tells me 'Sleep verb not supported'). I thought hibernate mode was not supposed to use any power, but after 4 days, my laptop was powerless (it wasn't when I hibernated). Any thoughts about how to diagnose what's going on? (It's also painfully slow to get back up to speed coming out of hibernation, but that's another story.) Patrick -- 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/cajvvksodm_-ze03r_h6hb5mmmqjhdafgt8ywgcee0kyomg3...@mail.gmail.com
Re: Unable to set LAN Internet connection on Debian Server
On Wednesday 29 April 2015 10:57:30 Darac Marjal wrote: > On Wed, Apr 29, 2015 at 03:12:44PM +0545, Binod Yadav wrote: > >Dear all, > >We are unable to set LAN Connection in the server and so we are unable > > to get online service through Teamviewer for Koha and Dspace software. > > Please guide us to solve the problems. > > Hello, > > I think you're going to have to give us more information than "it > doesn't work". By default, Debian comes configured to perform a DHCP > request on eth0. This should work for the majority of people, but some > people have more complex requirements so the above may not work. In > fact, I seem to remember that if the installer doesn't receive a DHCP > response, it will prompt for manual configuration. Might you have got > that wrong? > > So, in order for us to help you, I think we'll want the following: > > * What model of network card(s) are installed? > * What is the topology of your network (e.g. is this a home computer >connected to an ISPs router, is it an institutional computer >connected to a network that you don't control (in which case you >should tell us how the network administrator has told you to >connect), is it an air-gapped network between a few computers which >you control, etc etc) > * What is the content of /etc/network/interfaces? > * What is the output of (as root) 'ifdown eth0 ; ifup -v eth0' >(assuming that eth0 is your network interface - on a computer with >one ethernet port, it will be)? > > The above may lead to further questions, though. Be gentle people. Notice the address. I hope that you had some sleep last night, Binov and are at least warm and dry. Is it too much to hope for that you have had something to eat and drink? Is it a wired LAN? Are all the cables still there? Are they intact or damaged (possibly internally)? Have you checked things like the power to the router? How are you communicating with us? Before anything else, tell us what physical equipment and connections you still have. Lisi -- 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/201504291449.47354.lisi.re...@gmail.com
Re: issue with systemd-udev-settle
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? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: no ntp installed
Am 29.04.2015 um 07:20 schrieb Matthias Bodenbinder: > 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? $ systemctl status systemd-timesyncd.service and $ journalctl -u systemd-timesyncd.service will give you the current state of the service and a log of what it has been doing. > By the way, is there a comprehensive documentation for all the systemd > services which are available. All binaries in the systemd package are documented extensively via man pages. So, if you have a systemd-foo binary, just read man systemd-foo There is also man systemd.index, an index of all man pages. It's massive. You should skip all (3) entries, which are API documentation and only relevant for developers. For a more highlevel documentation, you can check the upstream wiki [1] It has an extensive documentation section. Especially "The systemd for Administrators Blog Series" might be interesting for a systemd newcomer. Michael [1] http://freedesktop.org/wiki/Software/systemd/ -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
