Re: apt-build
On Fri, Jan 13, 2017 at 08:59:12AM +0100, Antonio Trujillo Carmona wrote: > Tengo que recompilar el paquete freerdp2-x11 que esta en sid. > Como me he encontrado problemas de compatibilidades de librerías he > creado una maquina virtual con strecht/sid solo para este proceso, No te hace falta una máquina virtual entera para eso. Con un chroot es más que suficiente. Puedes usar debootstrap para crear un chroot y luego usar schroot para meterte dentro y compilar cosas. O mejor, usa sbuild + schroot para compilar cosas. > al intentar instalar apt-build me da : > Configurando apt-build (0.12.45) ... > sed: character class syntax is [[:space:]], not [:space:] > dpkg: error al procesar el paquete apt-build (--configure): > el subproceso instalado el script post-installation devolvió el código Es un fallo en el script "postinst", muy fácil de arreglar en origen, así que he puesto un bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851814 y ya está corregido: https://lists.debian.org/debian-devel-changes/2017/01/msg02259.html No se puede arreglar con dpkg ni con apt-get, es el paquete lo que está mal. Si tienes mucha prisa también puedes desactualizar "sed" a la versión de jessie y luego intentarlo de nuevo.
Re: Missing dependencies in steam package?
Rémi DUCCESCHI writes: > I hope this is the right list to post. I think it is better to report it to the package maintainer: > reportbug steam:i386 Thanks for your report! -- Alberto
Re: Recreating a second boot kernel in LILO
On Wed, Jan 18, 2017, at 20:49, Stephen Powell wrote: > > ... > The first two "image" entries define the standard "most recent" and > "next-most recent" kernels and don't need to be messed with, provided > that the standard symbolic link names are being maintained by > "do_symlinks = yes" in /etc/kernel-img.conf or by installation of the > xy-symlinks kernel hook scripts. > ... :1,$s/xy-symlinks/zy-symlinks/ -- .''`. Stephen Powell: :' : `. `'` `-
Re: Pas de posts depuis plusieurs jours
Le 19/01/2017 à 15:15, bernard schoenacker a écrit : On Thu, 19 Jan 2017 14:41:14 +0100 Dominik de Gratzwrote: Bonjour la liste, Je n'ai plus de posts depuis plusieurs jours ??? Cordialement bonjour, j'ai cru que les serveurs étaient mis en sommeil pour cause de grand froid "nucléaire" ... slt bernard Je suis rassuré, je retourne à ma propre hibernation Cordialement Dom
Re: Modificar velocidad placa de red (LAN)
El 19/01/17 a las 16:32, Rivera Valdez escribió: > 2017-01-19 10:18 GMT-03:00 Felix Perez: >> El día 19 de enero de 2017, 5:37, Rivera Valdez >> escribió: >>> 2017-01-05 15:16 GMT-03:00 Matias Mucciolo : On Thursday 05 January 2017 14:59:01 Rivera Valdez wrote: > 2017-01-05 10:06 GMT-03:00 Jorge A. Secreto : >> Hola >> >> El 4 de enero de 2017, 22:16, Rivera Valdez >> escribió: - Original Message - From: "Rivera Valdez" To: "debian-user-spanish" Sent: Wednesday, January 4, 2017 3:30:27 PM Subject: Modificar velocidad placa de red (LAN) Qué tal, tengo una notebook conectada por cable de red a un router que a su vez está conectado también por cable de red a una máquina de escritorio (es decir, una LAN hogareña, bah, que consiste sólo en esto que mencioné). Ambas máquinas tienen distros basadas en Debian. Las máquinas se ven y comunican entre sí sin problemas, salvo que -por algún motivo que no consigo elucidar- la velocidad de transmisión de archivos entre ellas (sea mediante gestores gráficos o mediante sftp por terminal) ha bajado y está clavada en 1.1MB/s. Antes, durante un par de años y normalmente, la velocidad era mucho mayor. ¿Desde dónde puedo controlar y modificar esto?, la velocidad a la cual se comunican/transmiten datos entre sí. ¡Muchas gracias! >>> 2017-01-04 21:13 GMT-03:00 Matias Mucciolo : Buenas proba con mii-tool o ethtool >> --- -- Matias Mucciolo Area de Infraestructura. Piedras 737 C.A.B.A SUTEBA >>> Muchas gracias, Matias, ! >>> >>> Por lo que estoy viendo ethtool tiene una manpage bastante poblada, >>> ahora me voy a poner a leerla en detalle. >>> >>> Mientras, por si alguno detecta rápidamente cuál puede ser el >>> problema, pego la salida que me da: >>> >>> $ ethtool eth0 >>> Settings for eth0: >>> Supported ports: [ TP MII ] >>> Supported link modes: 10baseT/Half 10baseT/Full >>>100baseT/Half 100baseT/Full >>>1000baseT/Half 1000baseT/Full >>> Supported pause frame use: No >>> Supports auto-negotiation: Yes >>> Advertised link modes: 10baseT/Half 10baseT/Full >>>100baseT/Half 100baseT/Full >>>1000baseT/Half 1000baseT/Full >>> Advertised pause frame use: Symmetric Receive-only >>> Advertised auto-negotiation: Yes >>> Link partner advertised link modes: 10baseT/Half 10baseT/Full >>> 100baseT/Half 100baseT/Full >>> Link partner advertised pause frame use: Symmetric >>> Link partner advertised auto-negotiation: Yes >>> Speed: 100Mb/s >>> Duplex: Full >>> Port: MII >>> PHYAD: 0 >>> Transceiver: internal >>> Auto-negotiation: on >>> Cannot get wake-on-lan settings: Operation not permitted >>> Current message level: 0x0033 (51) >>> drv probe ifdown ifup >>> Link detected: yes >>> >>> Reitero que, de momento, con ese resultado, la velocidad de >>> transmisión real en la práctica es de 1.1MB/s, ¿alguna pista? >>> >>> Gracias de nuevo, ! >>> > Qué tal, Jorge, muchas gracias por la ayuda: > >> Lo primero que pensé fué en probar los cables. >> Aunque si fueran un desastre, la negociación debería haber elegido 10 y >> no >> 100 >> Por las dudas los chequearía igual. > En principio los cables no sufrieron ningún "acto de violencia", pero > en cuanto pueda voy a buscar otro cable y hacer la prueba. > >> Otra cosa a tener en cuenta es que no estén pasando cerca de una fuente >> de >> ruido. >> O paralelos a un cable de alimentación. Salvo que estés usando cables >> blindados. > No son blindados, pero están en el lugar de siempre, sin > modificaciones en ese sentido, ni nuevos equipos que se hayan > instalado cerca. > >> Como decís que originalmente funcionaban bien, buscaría algún cambio de >> ese >> estilo. > En ese sentido no hubo cambios. > >> O que hayan pisado el cable con una silla. ese tipo de cosas. > Cabe la posibilidad. Cuando testée con otro par de cables (si puedo > esta noche) te confirmo. > >> ¿Probaste de desconectar todo lo demás del router? Que funcione solamente >> como switch. > Ídem. Esta noche hago la prueba. > >> ¿Puede ser que alguien haya habilitado alguna regla
Re: Cómo activar placa de red (notebook)
2016-12-03 15:02 GMT-03:00 José María: > El 03/12/16 a las 15:05, Rivera Valdez escribió: > >> 1) Muchas gracias a todos por la ayuda y orientación. >> >> 2) Efectivamente, la placa wireless ahora está funcionando y el >> problema era que estaba bloqueada por hardware (en esta notebook es >> especialmente incómodo porque las teclas F1, F2, etc., tienen >> incorporadas acciones "multimedia", pero hay que elegir al bootear si >> serán usadas como "multimedia" o como "función", de modo que hay que >> bootear como "multimedia", activar la placa wireless, rebootear y >> volver las teclas al modo normal... Creo que se pueden mapear >> correctamente para que hagan una o la otra cosa añadiendo el uso de >> una tecla "Fn" que tiene el teclado, pero ya es un laburo extra). >> >> 3) Sigue sin funcionar la placa de red. Y tengo la sospecha de que el >> problema pase porque el nombre está duplicado. Fíjense: >> >> root@debian:/home/user# lshw >> >>*-network >> description: Wireless interface >> product: Centrino Wireless-N 1030 [Rainbow Peak] >> vendor: Intel Corporation >> physical id: 0 >> bus info: pci@:03:00.0 >> logical name: wlan0 >> version: 34 >> serial: ac:72:89:0b:a1:2b >> width: 64 bits >> clock: 33MHz >> capabilities: pm msi pciexpress bus_master cap_list >> ethernet physical wireless >> configuration: broadcast=yes driver=iwlwifi >> driverversion=3.16.0-4-amd64 firmware=18.168.6.1 ip=10.0.0.8 latency=0 >> link=yes multicast=yes wireless=IEEE 802.11bgn >> resources: irq:55 memory:f1b0-f1b01fff >> >>*-network >> description: Ethernet interface >> product: RTL8111/8168/8411 PCI Express Gigabit >> Ethernet Controller >> vendor: Realtek Semiconductor Co., Ltd. >> physical id: 0 >> bus info: pci@:06:00.0 >> logical name: eth0 >> version: 06 >> serial: 14:fe:b5:b8:11:13 >> size: 10Mbit/s >> capacity: 1Gbit/s >> width: 64 bits >> clock: 33MHz >> capabilities: pm msi pciexpress msix vpd bus_master >> cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt >> 1000bt-fd autonegotiation >> configuration: autonegotiation=on broadcast=yes >> driver=r8169 driverversion=2.3LK-NAPI duplex=half >> firmware=rtl_nic/rtl8168e-2.fw latency=0 link=no multicast=yes >> port=MII speed=10Mbit/s >> resources: irq:41 ioport:2000(size=256) >> memory:f1804000-f1804fff memory:f180-f1803fff >> >> root@debian:/home/user# ifconfig -a >> >> eth0 Link encap:Ethernet HWaddr 14:fe:b5:b8:11:13 >> UP BROADCAST MULTICAST MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) >> >> loLink encap:Local Loopback >> inet addr:127.0.0.1 Mask:255.0.0.0 >> inet6 addr: ::1/128 Scope:Host >> UP LOOPBACK RUNNING MTU:65536 Metric:1 >> RX packets:857 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:857 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:145861 (142.4 KiB) TX bytes:145861 (142.4 KiB) >> >> wlan0 Link encap:Ethernet HWaddr ac:72:89:0b:a1:2b >> inet addr:10.0.0.8 Bcast:10.0.0.255 Mask:255.255.255.0 >> inet6 addr: fe80::ae72:89ff:fe0b:a12b/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:18545 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:16154 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:20507322 (19.5 MiB) TX bytes:2233434 (2.1 MiB) >> >> root@debian:/home/user# iwconfig >> >> lono wireless extensions. >> >> wlan0 IEEE 802.11bgn ESSID:"Los Tanukis" >> Mode:Managed Frequency:2.412 GHz Access Point: >> 38:22:9D:0C:56:51 >> Bit Rate=54 Mb/s Tx-Power=15 dBm >> Retry short limit:7 RTS thr:off Fragment thr:off >> Encryption key:4C61-5265-696E-6154-616E-756B-69 >> Power Management:off >> Link Quality=54/70 Signal level=-56 dBm >> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 >> Tx excessive retries:6 Invalid misc:488 Missed beacon:0 >> >> eth0 no wireless extensions. >> >> >> Aparece otra eth0 entre las interfaces wireless, ¿puede ser que al >> estar el nombre duplicado el sistema no sepa qué hacer y la ignore? >> ¿Cómo puedo anular/eliminar la
Re: Modificar velocidad placa de red (LAN)
2017-01-19 10:18 GMT-03:00 Felix Perez: > El día 19 de enero de 2017, 5:37, Rivera Valdez > escribió: >> 2017-01-05 15:16 GMT-03:00 Matias Mucciolo : >>> >>> >>> On Thursday 05 January 2017 14:59:01 Rivera Valdez wrote: 2017-01-05 10:06 GMT-03:00 Jorge A. Secreto : > Hola > > El 4 de enero de 2017, 22:16, Rivera Valdez > escribió: >> >> > - Original Message - >> > From: "Rivera Valdez" >> > To: "debian-user-spanish" >> > Sent: Wednesday, January 4, 2017 3:30:27 PM >> > Subject: Modificar velocidad placa de red (LAN) >> > >> > Qué tal, >> > >> > tengo una notebook conectada por cable de red a un router que a su vez >> > está conectado también por cable de red a una máquina de escritorio >> > (es decir, una LAN hogareña, bah, que consiste sólo en esto que >> > mencioné). Ambas máquinas tienen distros basadas en Debian. >> > >> > Las máquinas se ven y comunican entre sí sin problemas, salvo que -por >> > algún motivo que no consigo elucidar- la velocidad de transmisión de >> > archivos entre ellas (sea mediante gestores gráficos o mediante sftp >> > por terminal) ha bajado y está clavada en 1.1MB/s. Antes, durante un >> > par de años y normalmente, la velocidad era mucho mayor. >> > >> > ¿Desde dónde puedo controlar y modificar esto?, la velocidad a la cual >> > se comunican/transmiten datos entre sí. >> > >> > ¡Muchas gracias! >> 2017-01-04 21:13 GMT-03:00 Matias Mucciolo : >> > >> > Buenas >> > proba con mii-tool >> > o ethtool >> > >> > --- >> >> > >> > -- >> > Matias Mucciolo >> > >> > Area de Infraestructura. >> > Piedras 737 C.A.B.A >> > SUTEBA >> > >> >> Muchas gracias, Matias, ! >> >> Por lo que estoy viendo ethtool tiene una manpage bastante poblada, >> ahora me voy a poner a leerla en detalle. >> >> Mientras, por si alguno detecta rápidamente cuál puede ser el >> problema, pego la salida que me da: >> >> $ ethtool eth0 >> Settings for eth0: >> Supported ports: [ TP MII ] >> Supported link modes: 10baseT/Half 10baseT/Full >>100baseT/Half 100baseT/Full >>1000baseT/Half 1000baseT/Full >> Supported pause frame use: No >> Supports auto-negotiation: Yes >> Advertised link modes: 10baseT/Half 10baseT/Full >>100baseT/Half 100baseT/Full >>1000baseT/Half 1000baseT/Full >> Advertised pause frame use: Symmetric Receive-only >> Advertised auto-negotiation: Yes >> Link partner advertised link modes: 10baseT/Half 10baseT/Full >> 100baseT/Half 100baseT/Full >> Link partner advertised pause frame use: Symmetric >> Link partner advertised auto-negotiation: Yes >> Speed: 100Mb/s >> Duplex: Full >> Port: MII >> PHYAD: 0 >> Transceiver: internal >> Auto-negotiation: on >> Cannot get wake-on-lan settings: Operation not permitted >> Current message level: 0x0033 (51) >> drv probe ifdown ifup >> Link detected: yes >> >> Reitero que, de momento, con ese resultado, la velocidad de >> transmisión real en la práctica es de 1.1MB/s, ¿alguna pista? >> >> Gracias de nuevo, ! >> Qué tal, Jorge, muchas gracias por la ayuda: > Lo primero que pensé fué en probar los cables. > Aunque si fueran un desastre, la negociación debería haber elegido 10 y > no > 100 > Por las dudas los chequearía igual. En principio los cables no sufrieron ningún "acto de violencia", pero en cuanto pueda voy a buscar otro cable y hacer la prueba. > Otra cosa a tener en cuenta es que no estén pasando cerca de una fuente > de > ruido. > O paralelos a un cable de alimentación. Salvo que estés usando cables > blindados. No son blindados, pero están en el lugar de siempre, sin modificaciones en ese sentido, ni nuevos equipos que se hayan instalado cerca. > Como decís que originalmente funcionaban bien, buscaría algún cambio de > ese > estilo. En ese sentido no hubo cambios. > O que hayan pisado el cable con una silla. ese tipo de cosas. Cabe la posibilidad. Cuando testée con otro par de cables (si puedo esta noche) te confirmo. > ¿Probaste de desconectar todo lo demás del router? Que funcione solamente > como switch. Ídem. Esta noche hago la prueba. >
Re: Memory Upgrade for Ancient Enspiron 2600
Dougwrites: > As you watch the youtube, please note that he DID NOT USE ANY ARCTIC > SILVER > when he installed the CPU! > > I doubt that he'll have much life with that laptop! > > --doug Jimmy Johnson writes: > Here's a 2650 replacement, maybe it will help. https://www.youtube.com/ > watch?v=t5kzYN8FuHU It is similar but Dell has made it a little easier in the 2650. I am going to ask a dumb question, here but explain why. As someone who has no usable vision, I have done this sort of technical work complete with small parts and the need to be gentle with them, for almost 50 years. The idea is to make it better, not destroy it. In the video, Mr. Lord mentions being able to lift up the thin panel containing the keyboard to reach the under side of the keyboard. Does the 2650 also have the touch pad and two large mouse buttons between it and the edge that normally would be closest to you? The 2600 has as much room devoted to those items as is taken up by the keyboard whose top row is maybe two finger-widths from the lower edge of the screen. If you tried to lift it up high enough to reach the bottom of the keyboard and remove the screws, I think you would hear the sounds of over-stressed plastic cracking. Those two remaining screws blocked by the bottom of the screen, if out, probably would let you tilt it up, being mindful that there are several fragile cables that shouldn't be stressed. At least he did tell folks to remove the battery. There are probably some who wouldn't even give that lithium hydroxide bomb a second thought until it gave them 3rd-degree burns. This stuff is never really off unless all batteries are out. I take it that Arctic Silver is thermal grease. Ya' gotta' have it. Martin
Missing dependencies in steam package?
Hello, I just did a fresh install of Debian Sid on my computer, and I tried to install Steam (along with bumblebee-nvidia). Steam was not able to load steamui.so because of missing libraries. I had to manually install these packages in order to make it work: - libxtst6:i386 - libxrandr2:i386 - libglib2.0-0:i386 - libpulse0:i386 Should it be part of the steam package dependencies? I think it would help a lot people in the future... Also, to finish the installation, I needed to run "sudo ln -s /usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 /usr/lib/libGL.so.1" (I tried the update-alternatives solution as described here: http://askubuntu.com/a/517739, but I had an error saying that such alternatives doesn't exist). I hope this is the right list to post. Best wishes in 2017! Rémi
Aw: Re: Re: Bash different behaviour of read / strings in jessie versus stretch (regression?) [SOLVED]
Thanks, for that info as well, I adopted it for my script. Yours lopiuh Gesendet: Dienstag, 10. Januar 2017 um 14:32 Uhr Von: "Greg Wooledge"An: debian-user@lists.debian.org Betreff: Re: Re: Bash different behaviour of read / strings in jessie versus stretch (regression?) On Tue, Jan 10, 2017 at 01:10:53AM +0100, foo fighter wrote: > mapfile -t _array <<<"${_inputstring// /$'\n'}" For larger inputs, this will probably be more efficient: mapfile -t _array < <(your command | tr ' ' '\n') Bash's substitution can be rather slow on large strings.
Re: Memory Upgrade for Ancient Enspiron 2600
On 01/19/2017 11:54 AM, Jimmy Johnson wrote: On 01/18/2017 09:01 PM, Martin McCormick wrote: Jimmy Johnsonwrites: Hi Martin, How much memory does the Dell Inspiron 2600 Series Laptop take? I gave Dell the service tag number and found that this model can only hold 512 MB maximum and I was able to contact a company that is shipping two 256 MB modules. One is the easy one, the little door in the bottom near the battery. The other is the fun one, called the factory configurable slot under the keyboard. Getting to this second slot is not terribly hard as it appears that the keyboard and touch pad panel will come off or at least raise up but there is one last hurdle which I am trying to jump without breaking something. The bottom edge of the screen exactly hides the last two screws. You can't move it to any position which will expose them. The hinges and screen work fine and I want to keep it that way but it looks like if one could temporarily take the hinges loose from the screen, it would probably move enough to take out the last two screws. I have been googling to find out if there is a way to temporarily take the screen out of the grasp of the hinges and am running in to the usual mechanized help syndrome of people who want to sell you services and tons of articles about the wrong models of Dell. I also know that one or both hinges probably also pass the screen's electrical cables so whatever one does to the hinges must be done with care to keep from cutting or damaging those flex cables. Otherwise, I'm mostly there. When I do get it upgraded, it should run Debian as I have gotten systems to run it on 384 MB without gnome. Thanks for any suggestions. In a previous life, I repaired AV equipment in the eighties and the hinge problem is very similar to a few others I have dealt with in that there is probably a trick that makes all the difference between making things worse and fixing it. Those screws do have to come out. Martin McCormick Here's a 2650 replacement, maybe it will help. https://www.youtube.com/watch?v=t5kzYN8FuHU As you watch the youtube, please note that he DID NOT USE ANY ARCTIC SILVER when he installed the CPU! I doubt that he'll have much life with that laptop! --doug
Re: NFS msg: Unable to find suitable address
On Thu, Jan 19, 2017 at 11:29:37AM -0600, Dennis Wicks wrote: > > PING robin.netgear.com (192.168.254.62) 56(84) bytes of data. > > 64 bytes from robin.netgear.com (192.168.254.62): > icmp_seq=1 ttl=64 time=0.472 ms > > sudo mount //192.168.254.62/znfs/edrv -o user=,password= > /mnt > > Unable to find suitable address. You're still using Windows syntax. Use NFS syntax instead. mount -o user=,password= robin.netgear.com:/znfs/edrv /mnt //robin/ = Windows robin: = NFS
Nvidia fan speed control
Hi to everyone. Just bought new gpu card, Asus GTX 1070, everything is working, but gpu fan is producing a lot of noise. Tried to search methods how to make it more quiet, and all solutions are based on the following: nvidia-settings -a [gpu:0]/GPUFanControlState=1 -a [fan:0]/GPUTargetFanSpeed=$new_speed (also with adding Coolbits to xorg.conf) But this doesn't work for me. If I stop X server, gpu disables fan and works without any noise. Once I start lightdm - fan is on, speed and noise are constant, whichever value of $new_speed I set. I tried using nvidia-driver from repository, tried several versions of proprietary nvidia driver from official site - no changes. Has anyone met such issue before and has solution for it? Thanks in advance.
Re: NFS msg: Unable to find suitable address
Kent West wrote on 01/19/2017 10:07 AM: On Jan 19, 2017 10:03 AM, "Dennis Wicks"> wrote: This is what happens: sudo mount //robin/znfs/edrv -o user=,password= /mnt Unable to find suitable address. What happens if you use the IP address instead of the name "robin"? Can you ping "robin"? -- Kent No difference! > PING robin.netgear.com (192.168.254.62) 56(84) bytes of data. > 64 bytes from robin.netgear.com (192.168.254.62): icmp_seq=1 ttl=64 time=0.472 ms > sudo mount //192.168.254.62/znfs/edrv -o user=,password= /mnt > Unable to find suitable address.
Re: Memory Upgrade for Ancient Enspiron 2600
On 01/18/2017 09:01 PM, Martin McCormick wrote: Jimmy Johnsonwrites: Hi Martin, How much memory does the Dell Inspiron 2600 Series Laptop take? I gave Dell the service tag number and found that this model can only hold 512 MB maximum and I was able to contact a company that is shipping two 256 MB modules. One is the easy one, the little door in the bottom near the battery. The other is the fun one, called the factory configurable slot under the keyboard. Getting to this second slot is not terribly hard as it appears that the keyboard and touch pad panel will come off or at least raise up but there is one last hurdle which I am trying to jump without breaking something. The bottom edge of the screen exactly hides the last two screws. You can't move it to any position which will expose them. The hinges and screen work fine and I want to keep it that way but it looks like if one could temporarily take the hinges loose from the screen, it would probably move enough to take out the last two screws. I have been googling to find out if there is a way to temporarily take the screen out of the grasp of the hinges and am running in to the usual mechanized help syndrome of people who want to sell you services and tons of articles about the wrong models of Dell. I also know that one or both hinges probably also pass the screen's electrical cables so whatever one does to the hinges must be done with care to keep from cutting or damaging those flex cables. Otherwise, I'm mostly there. When I do get it upgraded, it should run Debian as I have gotten systems to run it on 384 MB without gnome. Thanks for any suggestions. In a previous life, I repaired AV equipment in the eighties and the hinge problem is very similar to a few others I have dealt with in that there is probably a trick that makes all the difference between making things worse and fixing it. Those screws do have to come out. Martin McCormick Here's a 2650 replacement, maybe it will help. https://www.youtube.com/watch?v=t5kzYN8FuHU -- Jimmy Johnson Debian Sid/Testing - Plasma 5.8.4 - Kernel 4.8.0-2 - EXT4 at sda24 Registered Linux User #380263
compmgr problem
Hi, I'm running awesome wm on Stretch. After moving from Jessie to Stretch I had to install xcompmgr in order to get my Conky transparent again. However xcompmgr seems to damage my VirtualBox windows as you can see on the screenshot the link is here: http://i.imgur.com/W7f7Oz8.jpg I apreciate any help, Jurek
Re: NFS msg: Unable to find suitable address
Hi. On Thu, 19 Jan 2017 10:01:43 -0600 Dennis Wickswrote: > This is what happens: > > sudo mount //robin/znfs/edrv -o user=,password= /mnt > Unable to find suitable address. > > The server is Jessie 8.7 and NFS-V4 (I think!) Why guess? It listens tcp:2049 - it's nfsv4. It does not - it's nfsv3. Jessie comes with NFS2/3/4 support, NFS4 being the default. > The directory is exported as: > /znfs/edrv/ *(rw,sync,no_subtree_check,root_squash) > If this is a result of 'showmount -e' then it does not proof anything (showmount always uses nfsv3). If this is a result of 'exportfs' on server - then it's a different story. > And the mount is: > /dev/sdf1 on /znfs/edrv type ext3 > (rw,relatime,data=ordered) You mean - the mountpoint on a server? Good to know, hardly relevant to the issue. > I can't find any info that looks like a solution to the problem. > > Anybody have a clue? A hint? Seen it before? Sure. First, nobody mounts nfs like you do. It's done differently. Second, they give you automounter which simplifies things. Third, assuming 'robin' is a hostname, and you're using ipv4: sudo mount -t nfs -o soft,tcp robin:/znfs/edrv /mnt Last, but not least - https://wiki.debian.org/NFS Reco
Re: NFS msg: Unable to find suitable address
On Thu, Jan 19, 2017 at 10:01:43AM -0600, Dennis Wicks wrote: This is what happens: sudo mount //robin/znfs/edrv -o user=,password= /mnt Unable to find suitable address. I think you're using a CIFS/SMB-style address. Try $ sudo mount robin:/znfs/edrv -o . Take at look at the 'nfs' man page for the specification. The server is Jessie 8.7 and NFS-V4 (I think!) The directory is exported as: /znfs/edrv/ *(rw,sync,no_subtree_check,root_squash) And the mount is: > /dev/sdf1 on /znfs/edrv type ext3 (rw,relatime,data=ordered) I can't find any info that looks like a solution to the problem. Anybody have a clue? A hint? Seen it before? As usual, Many TIA!! Dennis -- For more information, please reread.
Re: NFS msg: Unable to find suitable address
On Jan 19, 2017 10:03 AM, "Dennis Wicks"wrote: This is what happens: sudo mount //robin/znfs/edrv -o user=,password= /mnt Unable to find suitable address. What happens if you use the IP address instead of the name "robin"? Can you ping "robin"? -- Kent
NFS msg: Unable to find suitable address
This is what happens: sudo mount //robin/znfs/edrv -o user=,password= /mnt Unable to find suitable address. The server is Jessie 8.7 and NFS-V4 (I think!) The directory is exported as: /znfs/edrv/ *(rw,sync,no_subtree_check,root_squash) And the mount is: > /dev/sdf1 on /znfs/edrv type ext3 (rw,relatime,data=ordered) I can't find any info that looks like a solution to the problem. Anybody have a clue? A hint? Seen it before? As usual, Many TIA!! Dennis
Re: Memory Upgrade for Ancient Enspiron 2600
David Christensenwrites: > On 01/18/17 22:02, Doug wrote: > The Service Manual can be downloaded from the support page I posted > previously: > > http://www.dell.com/support/home/us/en/19/product-support/product/ > inspiron-2600/manuals Thank you! I will certainly do that. Also, remembering the eighties when I worked as a technician in our audio visual repair shop, the advice about labelling removed parts for later re-assembly is a great idea. It's amazing how fuzzy one's memory can get when working on some device that is new to you, especially if there is a delay between tear-down and re-assembly. We were officially classified as electronic technicians but back then most of what broke was mechanical and involved that inner circle of Hell which is the interface between electronics and things that move. It's kind of fun but agrevating when one is trying to really fix it so that it stays fixed. Martin McCormick
Re: stretch/KDE: bluetooth: unable to connect
After better examining my logs, I managed to solve it. I found the following error in /var/log/syslog: Jan 19 14:27:06 alan bluetoothd[475]: a2dp-source profile connect failed for 78:F8:82:48:55:C3: Protocol not available A2DP is the "Advanced Audio Distribution Profile", and I found a related debian wiki page: https://wiki.debian.org/BluetoothUser/a2dp I installed the required packages listed in that page, and now I can connect to my smartphone via bluetooth.
Re: Pas de posts depuis plusieurs jours
On Thu, 19 Jan 2017 14:41:14 +0100 Dominik de Gratzwrote: > Bonjour la liste, > > Je n'ai plus de posts depuis plusieurs jours ??? > > Cordialement bonjour, j'ai cru que les serveurs étaient mis en sommeil pour cause de grand froid "nucléaire" ... slt bernard -- bernard schoenacker
Re: Pas de posts depuis plusieurs jours
On 01/19/2017 02:41 PM, Dominik de Gratz wrote: Bonjour la liste, Je n'ai plus de posts depuis plusieurs jours ??? Cordialement Salut Rien d'anormal, par temps froid, on hiberne :) https://lists.debian.org/debian-user-french/2017/01/maillist.html -- Maderios
Pas de posts depuis plusieurs jours
Bonjour la liste, Je n'ai plus de posts depuis plusieurs jours ??? Cordialement
Re: Modificar velocidad placa de red (LAN)
El día 19 de enero de 2017, 5:37, Rivera Valdezescribió: > 2017-01-05 15:16 GMT-03:00 Matias Mucciolo : >> >> >> On Thursday 05 January 2017 14:59:01 Rivera Valdez wrote: >>> 2017-01-05 10:06 GMT-03:00 Jorge A. Secreto : >>> > Hola >>> > >>> > El 4 de enero de 2017, 22:16, Rivera Valdez >>> > escribió: >>> >> >>> >> > - Original Message - >>> >> > From: "Rivera Valdez" >>> >> > To: "debian-user-spanish" >>> >> > Sent: Wednesday, January 4, 2017 3:30:27 PM >>> >> > Subject: Modificar velocidad placa de red (LAN) >>> >> > >>> >> > Qué tal, >>> >> > >>> >> > tengo una notebook conectada por cable de red a un router que a su vez >>> >> > está conectado también por cable de red a una máquina de escritorio >>> >> > (es decir, una LAN hogareña, bah, que consiste sólo en esto que >>> >> > mencioné). Ambas máquinas tienen distros basadas en Debian. >>> >> > >>> >> > Las máquinas se ven y comunican entre sí sin problemas, salvo que -por >>> >> > algún motivo que no consigo elucidar- la velocidad de transmisión de >>> >> > archivos entre ellas (sea mediante gestores gráficos o mediante sftp >>> >> > por terminal) ha bajado y está clavada en 1.1MB/s. Antes, durante un >>> >> > par de años y normalmente, la velocidad era mucho mayor. >>> >> > >>> >> > ¿Desde dónde puedo controlar y modificar esto?, la velocidad a la cual >>> >> > se comunican/transmiten datos entre sí. >>> >> > >>> >> > ¡Muchas gracias! >>> >> 2017-01-04 21:13 GMT-03:00 Matias Mucciolo : >>> >> > >>> >> > Buenas >>> >> > proba con mii-tool >>> >> > o ethtool >>> >> > >>> >> >>> > --- >>> >> >>> >> > >>> >> > -- >>> >> > Matias Mucciolo >>> >> > >>> >> > Area de Infraestructura. >>> >> > Piedras 737 C.A.B.A >>> >> > SUTEBA >>> >> > >>> >> >>> >> Muchas gracias, Matias, ! >>> >> >>> >> Por lo que estoy viendo ethtool tiene una manpage bastante poblada, >>> >> ahora me voy a poner a leerla en detalle. >>> >> >>> >> Mientras, por si alguno detecta rápidamente cuál puede ser el >>> >> problema, pego la salida que me da: >>> >> >>> >> $ ethtool eth0 >>> >> Settings for eth0: >>> >> Supported ports: [ TP MII ] >>> >> Supported link modes: 10baseT/Half 10baseT/Full >>> >>100baseT/Half 100baseT/Full >>> >>1000baseT/Half 1000baseT/Full >>> >> Supported pause frame use: No >>> >> Supports auto-negotiation: Yes >>> >> Advertised link modes: 10baseT/Half 10baseT/Full >>> >>100baseT/Half 100baseT/Full >>> >>1000baseT/Half 1000baseT/Full >>> >> Advertised pause frame use: Symmetric Receive-only >>> >> Advertised auto-negotiation: Yes >>> >> Link partner advertised link modes: 10baseT/Half 10baseT/Full >>> >> 100baseT/Half 100baseT/Full >>> >> Link partner advertised pause frame use: Symmetric >>> >> Link partner advertised auto-negotiation: Yes >>> >> Speed: 100Mb/s >>> >> Duplex: Full >>> >> Port: MII >>> >> PHYAD: 0 >>> >> Transceiver: internal >>> >> Auto-negotiation: on >>> >> Cannot get wake-on-lan settings: Operation not permitted >>> >> Current message level: 0x0033 (51) >>> >> drv probe ifdown ifup >>> >> Link detected: yes >>> >> >>> >> Reitero que, de momento, con ese resultado, la velocidad de >>> >> transmisión real en la práctica es de 1.1MB/s, ¿alguna pista? >>> >> >>> >> Gracias de nuevo, ! >>> >> >>> >>> Qué tal, Jorge, muchas gracias por la ayuda: >>> >>> > Lo primero que pensé fué en probar los cables. >>> > Aunque si fueran un desastre, la negociación debería haber elegido 10 y no >>> > 100 >>> > Por las dudas los chequearía igual. >>> >>> En principio los cables no sufrieron ningún "acto de violencia", pero >>> en cuanto pueda voy a buscar otro cable y hacer la prueba. >>> >>> > Otra cosa a tener en cuenta es que no estén pasando cerca de una fuente de >>> > ruido. >>> > O paralelos a un cable de alimentación. Salvo que estés usando cables >>> > blindados. >>> >>> No son blindados, pero están en el lugar de siempre, sin >>> modificaciones en ese sentido, ni nuevos equipos que se hayan >>> instalado cerca. >>> >>> > Como decís que originalmente funcionaban bien, buscaría algún cambio de >>> > ese >>> > estilo. >>> >>> En ese sentido no hubo cambios. >>> >>> > O que hayan pisado el cable con una silla. ese tipo de cosas. >>> >>> Cabe la posibilidad. Cuando testée con otro par de cables (si puedo >>> esta noche) te confirmo. >>> >>> > ¿Probaste de desconectar todo lo demás del router? Que funcione solamente >>> > como switch. >>> >>> Ídem. Esta noche hago la prueba. >>> >>> > ¿Puede ser que alguien haya habilitado alguna regla de calidad de servicio >>> > en el router? >>> >>> En principio, no. Ese router lo administro sólo yo, y no modifiqué >>> nada en él (salvo haber pasado el protocolo de
Re: Modificar velocidad placa de red (LAN)
El 19/01/17 a las 05:37, Rivera Valdez escribió: > ... > Gracias a todos y perdón por la demora, recién hoy dispuse del espacio > y tiempo para hacer más pruebas. > > Aparentemente es cosa del cable (cuestión que me descolocó porque > coincidió *justo* con unos problemas de drivers y cambios de kernel, > con lo que me parecía *demasiada* casualidad que *justo* el cable se > jodiera en ese preciso momento, pero...), acabo de hacer la prueba con > un cable corto que tenía a mano y parece estar funcionando ok. > > $ dd if=/dev/zero bs=1024 count=1048576 | ssh USER@PC 'cat > /dev/null' > USER@PC's password: > 1048576+0 registros leídos > 1048576+0 registros escritos > 1073741824 bytes (1,1 GB) copiados, 94,4255 s, 11,4 MB/s > > Copiando [put/get] con sftp también, tengo una velocidad que ronda los > 11.0MB/s. > > $ sudo mii-tool eth0 > [sudo] password for user: > eth0: negotiated 100baseTx-FD flow-control, link ok > > La salida de ethtool sigue siendo la misma que posteé antes. > > Habrá que joderse y reemplazar el largo cable... > Si tienen alguna sugerencia más, les agradezco cualquier idea/propuesta. > > ¡Muchas gracias de nuevo a todos! > > Saludos, ! Si el cable pasa por la pared, fijate que no haya interferencia eléctrica (cables eléctricos que pasen por el mismo caño). Si los hay, convendría reemplazar el cable de red con cable utp mallado (stp). Saludos, Javier. -- Eco red Natural. Veta de productos orgánicos y BPA. Totalmente naturales.
Fattura TIM linea Fissa - Gennaio 2017 - scadenza 12/01/2017
<<< text/html: Unrecognized >>>
Re: ffmpeg / avconv
Le decadi 30 nivôse, an CCXXV, Pol Hallen a écrit : > My goal is not to waste the file size (disk space) That makes one. > > ie: if I've a 10Mb of a file with video bitrate 1000K and 128K audio > bitrate, I'd like don't exceed 10Mb using a larger bitrate :) > > unfortunately I've some flv file and my home player doesn't play it :-/ And I guess you want to play those files on your home player. That makes two. You can achieve these goals by using a very low bitrate, but that results in a horrible quality. My guess is you do not want that either, you want reasonable quality or something. That would make three. You need to prioritize these goals. Once this is done, you need to find out exactly what codecs and formats your home player supports. Note, these are two independent pieces of information, and both are needed. Regards, -- Nicolas George signature.asc Description: Digital signature
Re: ffmpeg / avconv
What is your actual purpose? Hello, thanks for your reply My goal is not to waste the file size (disk space) ie: if I've a 10Mb of a file with video bitrate 1000K and 128K audio bitrate, I'd like don't exceed 10Mb using a larger bitrate :) unfortunately I've some flv file and my home player doesn't play it :-/ thanks! Pol
Re: Memory Upgrade for Ancient Enspiron 2600
On Thursday 19 January 2017 06:02:08 Doug wrote: > On 01/19/2017 12:01 AM, Martin McCormick wrote: > > Jimmy Johnsonwrites: > >> Hi Martin, > >> > >> How much memory does the Dell Inspiron 2600 Series Laptop take? > > > > I gave Dell the service tag number and found that this model can > > only hold 512 MB maximum and I was able to contact a company that > > is shipping two 256 MB modules. One is the easy one, the little > > door in the bottom near the battery. The other is the fun one, > > called the factory configurable slot under the keyboard. > > > > Getting to this second slot is not terribly hard as it > > appears that the keyboard and touch pad panel will come off or > > at least raise up but there is one last hurdle which I am trying > > to jump without breaking something. > > > > The bottom edge of the screen exactly hides the last two > > screws. You can't move it to any position which will expose them. > > > > The hinges and screen work fine and I want to keep it > > that way but it looks like if one could temporarily take the > > hinges loose from the screen, it would probably move enough to > > take out the last two screws. > > > > I have been googling to find out if there is a way to > > temporarily take the screen out of the grasp of the hinges and am > > running in to the usual mechanized help syndrome of people who > > want to sell you services and tons of articles about the wrong > > models of Dell. > > > > I also know that one or both hinges probably also pass > > the screen's electrical cables so whatever one does to the hinges > > must be done with care to keep from cutting or damaging those > > flex cables. > > > > Otherwise, I'm mostly there. > > > > When I do get it upgraded, it should run Debian as I have > > gotten systems to run it on 384 MB without gnome. > > > > Thanks for any suggestions. In a previous life, I repaired AV > > equipment in the eighties and the hinge problem is very similar > > to a few others I have dealt with in that there is probably a > > trick that makes all the difference between making things worse > > and fixing it. Those screws do have to come out. > > > > Martin McCormick > > For most Dell laptops, there is a service manual. See if there is one for > this model, and download it. The manual I used for my machine was > very useful--it specifies the exact series of procedures you need to run > to get at any particular module in the machine. Then you don't have to > guess and maybe break something. The time I had to do something to a Dell laptop, I downloaded the service manual and it gave detailed and easy-to-follow instructions a) on how to dismantle it and b) equally good instructions for putting it together again. It was quite complicated, with all sorts of things layered. I would not have been able to guess, but it was really easy (if some of it fiddly) with the instructions. Lisi
Fattura TIM linea Fissa - Gennaio 2017 - scadenza 12/01/2017
<<< text/html: Unrecognized >>>
Fattura TIM linea Fissa - Gennaio 2017 - scadenza 12/01/2017
<<< text/html: Unrecognized >>>
Fattura TIM linea Fissa - Gennaio 2017 - scadenza 12/01/2017
<<< text/html: Unrecognized >>>
Fattura TIM linea Fissa - Gennaio 2017 - scadenza 12/01/2017
<<< text/html: Unrecognized >>>
Re: Modificar velocidad placa de red (LAN)
2017-01-05 15:16 GMT-03:00 Matias Mucciolo: > > > On Thursday 05 January 2017 14:59:01 Rivera Valdez wrote: >> 2017-01-05 10:06 GMT-03:00 Jorge A. Secreto : >> > Hola >> > >> > El 4 de enero de 2017, 22:16, Rivera Valdez >> > escribió: >> >> >> >> > - Original Message - >> >> > From: "Rivera Valdez" >> >> > To: "debian-user-spanish" >> >> > Sent: Wednesday, January 4, 2017 3:30:27 PM >> >> > Subject: Modificar velocidad placa de red (LAN) >> >> > >> >> > Qué tal, >> >> > >> >> > tengo una notebook conectada por cable de red a un router que a su vez >> >> > está conectado también por cable de red a una máquina de escritorio >> >> > (es decir, una LAN hogareña, bah, que consiste sólo en esto que >> >> > mencioné). Ambas máquinas tienen distros basadas en Debian. >> >> > >> >> > Las máquinas se ven y comunican entre sí sin problemas, salvo que -por >> >> > algún motivo que no consigo elucidar- la velocidad de transmisión de >> >> > archivos entre ellas (sea mediante gestores gráficos o mediante sftp >> >> > por terminal) ha bajado y está clavada en 1.1MB/s. Antes, durante un >> >> > par de años y normalmente, la velocidad era mucho mayor. >> >> > >> >> > ¿Desde dónde puedo controlar y modificar esto?, la velocidad a la cual >> >> > se comunican/transmiten datos entre sí. >> >> > >> >> > ¡Muchas gracias! >> >> 2017-01-04 21:13 GMT-03:00 Matias Mucciolo : >> >> > >> >> > Buenas >> >> > proba con mii-tool >> >> > o ethtool >> >> > >> >> >> > --- >> >> >> >> > >> >> > -- >> >> > Matias Mucciolo >> >> > >> >> > Area de Infraestructura. >> >> > Piedras 737 C.A.B.A >> >> > SUTEBA >> >> > >> >> >> >> Muchas gracias, Matias, ! >> >> >> >> Por lo que estoy viendo ethtool tiene una manpage bastante poblada, >> >> ahora me voy a poner a leerla en detalle. >> >> >> >> Mientras, por si alguno detecta rápidamente cuál puede ser el >> >> problema, pego la salida que me da: >> >> >> >> $ ethtool eth0 >> >> Settings for eth0: >> >> Supported ports: [ TP MII ] >> >> Supported link modes: 10baseT/Half 10baseT/Full >> >>100baseT/Half 100baseT/Full >> >>1000baseT/Half 1000baseT/Full >> >> Supported pause frame use: No >> >> Supports auto-negotiation: Yes >> >> Advertised link modes: 10baseT/Half 10baseT/Full >> >>100baseT/Half 100baseT/Full >> >>1000baseT/Half 1000baseT/Full >> >> Advertised pause frame use: Symmetric Receive-only >> >> Advertised auto-negotiation: Yes >> >> Link partner advertised link modes: 10baseT/Half 10baseT/Full >> >> 100baseT/Half 100baseT/Full >> >> Link partner advertised pause frame use: Symmetric >> >> Link partner advertised auto-negotiation: Yes >> >> Speed: 100Mb/s >> >> Duplex: Full >> >> Port: MII >> >> PHYAD: 0 >> >> Transceiver: internal >> >> Auto-negotiation: on >> >> Cannot get wake-on-lan settings: Operation not permitted >> >> Current message level: 0x0033 (51) >> >> drv probe ifdown ifup >> >> Link detected: yes >> >> >> >> Reitero que, de momento, con ese resultado, la velocidad de >> >> transmisión real en la práctica es de 1.1MB/s, ¿alguna pista? >> >> >> >> Gracias de nuevo, ! >> >> >> >> Qué tal, Jorge, muchas gracias por la ayuda: >> >> > Lo primero que pensé fué en probar los cables. >> > Aunque si fueran un desastre, la negociación debería haber elegido 10 y no >> > 100 >> > Por las dudas los chequearía igual. >> >> En principio los cables no sufrieron ningún "acto de violencia", pero >> en cuanto pueda voy a buscar otro cable y hacer la prueba. >> >> > Otra cosa a tener en cuenta es que no estén pasando cerca de una fuente de >> > ruido. >> > O paralelos a un cable de alimentación. Salvo que estés usando cables >> > blindados. >> >> No son blindados, pero están en el lugar de siempre, sin >> modificaciones en ese sentido, ni nuevos equipos que se hayan >> instalado cerca. >> >> > Como decís que originalmente funcionaban bien, buscaría algún cambio de ese >> > estilo. >> >> En ese sentido no hubo cambios. >> >> > O que hayan pisado el cable con una silla. ese tipo de cosas. >> >> Cabe la posibilidad. Cuando testée con otro par de cables (si puedo >> esta noche) te confirmo. >> >> > ¿Probaste de desconectar todo lo demás del router? Que funcione solamente >> > como switch. >> >> Ídem. Esta noche hago la prueba. >> >> > ¿Puede ser que alguien haya habilitado alguna regla de calidad de servicio >> > en el router? >> >> En principio, no. Ese router lo administro sólo yo, y no modifiqué >> nada en él (salvo haber pasado el protocolo de seguridad WiFi de WEP >> -que venía por defecto- a WPA2; pero entiendo que no tiene nada que >> ver con esto, y además fue posterior a esta caída en velocidad de la >> conexión por red cableada). >> >> > Ah, y la negociación de
Re: Resume From Hibernation Failing With Automatic Reboot - Debian Testing
On Wed, Oct 12, 2016 at 09:43:48PM +0200, Sicelo wrote: > > I am running Debian Testing, and for the last two weeks or so, it is > impossible to successfully resume the system from hibernation. I am now using Debian Unstable/Sid, and have exactly the same issues > The hardware is a ThinkPad X40 (yes, old), running Debian testing with > the 4.7.0-1-686 #1 SMP Debian 4.7.5-1 kernel. It has 1GB RAM, and a 60GB > SSD. > > At this time I am out of clues on what to check and how. I understand > that the hardware is old, but if it would be possible to narrow down the > problem to a specific package, etc. I will appreciate any clues or > suggestions you can give. > I have since narrowed the problem down to the kernel in use. Any 4.x kernel available on Debian exhibits this issue, while using the old 3.16 kernel works fine consistently. If you have suggestions on how to narrow down the problem with the 4.x kernels I would appreciate it. Regards Sicelo A. Mhlongo
Fattura TIM linea Fissa - Gennaio 2017 - scadenza 12/01/2017
<<< text/html: Unrecognized >>>