Re: quick scripting 'is /P/Q mounted'

[Richard Hector]

On 13/03/18 16:40, Mike McClain wrote:
> A while back, Pierre Gaston posted this little tidbit to quickly
> determine if my network is up:
> [ "$( 
> Now I wonder if there is a similar file in /sys that would tell if
> anything is mounted on a particular directory. I've browsed /sys but
> not found what I'm looking for.
> 
> If my other computer is South40 and I want to mount South40's /docs
> on my /south40/docs/ directory I can do that. As one script calls
> another I want to know if I need to mount South40 without
> $( mount | grep 'south40/docs').

You could look at /proc/mounts, but that's similar to the output of mount.

Or if it's for a specific directory, and you can put something in it,
you can test for the existence of a special file in the directory.

Something like

[ -f /south40/docs/.flag ]

Richard




signature.asc
Description: OpenPGP digital signature

quick scripting 'is /P/Q mounted'

[Mike McClain]

A while back, Pierre Gaston posted this little tidbit to quickly
determine if my network is up:
[ "$(

Re: PAE or not PAE?

[Joe Pfeiffer]

Gene Heskett  writes:

> On Monday 12 March 2018 15:27:23 Hans wrote:
>
>> > Note that the non PAE kernel in older Debian versions up to Jessie
>> > lacked multi-processor (including multi-core and hyper-threading)
>> > support.
>>
>> Yes, I read this, too. The N280 is a single core, but mith
>> hyperthreading, I have two cores.
>>
>> Is this still so, that the non-pae-kernel lacks still hyperthreading,
>> or does it do today, too?
>>
>> And second question: Is PAE preferred (with the look to speed) or
>> better use non-pae?
>>
>> Cheers
>>
>> Hans
>
> Both pae and hyperthreading take time, hyperthreading quite a bit more 
> than pae. With hyperthreading, to switch to the 2nd task, takes a 
> complete processor state stored on the stack, the stack pointer reloaded 
> to point at the image of the 2nd task, then pull the full register dump 
> for task 2 back into the processor. Then and only then can the first 
> cycle devoted to task 2 be initiated. Ditto to swap back. For boxes that 
> will run a realtime task, the first thing we do is turn off the 
> hyperthreading. Its a solution that works ok, but I can't think of a 
> better way to make a decently fast cpu into a provable slowpoke. All it 
> really does for us is to help heat the shop. You can keep it above the 
> dew point with electric heat to help control rust, or you can enable 
> hyperthreading and its exactly the same turns of the electric meter 
> either way.  An excellent demo of the TANSTAAFL principle.

This doesn't correlate with my understanding of the process.  My
understanding, and every block diagram I've seen of a processor capable
of hyperthreading, has a separate set of architectural registers for
every thread.  The processor does need to start refilling the pipeline
on a thread switch, but doesn't do any register dump.

I will agree that it increases the unpredictability of execution time,
and if I wanted to guarantee I could meet deadlines I'd turn it off.

Re: Simple spreadsheet program.

[Jude DaShiell]

scim probably ought to answer.
On Tue, 13 Mar 2018, terryc wrote:


Date: Mon, 12 Mar 2018 23:13:33
From: terryc 
To: debian-user@lists.debian.org
Subject: Simple spreadsheet program.
Resent-Date: Tue, 13 Mar 2018 03:14:03 + (UTC)
Resent-From: debian-user@lists.debian.org

What is a simple spreadsheet program that can be installed under
Stretch. I need to do some work quickly

hint, if your answer is LibreOffice or similar read the question again.
I'm frustrated that the last few time I wanted to do a simple
spreadsheet layout, it was easier and faster to craft a LaTex document
then try and unfathom LibreOffice methods.




--

Re: Simple spreadsheet program.

[David Wright]

On Tue 13 Mar 2018 at 14:13:33 (+1100), terryc wrote:
> What is a simple spreadsheet program that can be installed under
> Stretch. I need to do some work quickly

I use gnumeric myself. As its description says, if you know
Excel, then you'll know how to use it.

(I use a Window Manager, not a Desk Environment.)

Cheers,
David.

Simple spreadsheet program.

[terryc]

What is a simple spreadsheet program that can be installed under
Stretch. I need to do some work quickly

hint, if your answer is LibreOffice or similar read the question again.
I'm frustrated that the last few time I wanted to do a simple
spreadsheet layout, it was easier and faster to craft a LaTex document
then try and unfathom LibreOffice methods.

OT: dovecot with letsencrypt, K9 mail fails?

[Richard Hector]

Hi all,

I use dovecot with a letsencrypt certificate, which has been working fine.

In the last few days, my phone (K9 mail on Android) has started having
problems connecting. I think it's since I received the most recent
android updates (5 March patchlevel).

At first, it would just complain about the cert, but I'd click 'Next'
from the settings page and it would carry on working for a while (maybe
a day?).

Today, though - which may be unrelated - it prompted me to check the
certificate, which weirdly seemed to belong to my VPS provider; it
wasn't the one configured in dovecot.

Has anyone else seen either of these issues? My VPS provider hasn't come
up with any ideas yet.

Thanks,
Richard



signature.asc
Description: OpenPGP digital signature

Re: [Debian-Stretch on macmini-4.1] Can't get X working with nvidia

[Ennio-Sr]

* Henning Follmann  [120318, 08:09]:
> On Sat, Mar 10, 2018 at 12:21:17AM +0100, Ennio-Sr wrote:
> > Hi all!
> > [...]

> > ...solution to the 'black screen' coming out running startx, I'm curious to
> > know if there is any of you with the same hardware who found a
> > workaround and would share it.
> 
> I do have a macbookpro and for me it was exactly the issue. e.g. The
> graphics adapter by default is not bus master.
> 
Sorry, I do not understand what #'is not bus master'# means

> > 
> > Looking at the various logs I can't find any clue. 
> > Reading  I also
> > consulted the suggested link 'http://askubuntu.com/a/613573/134848' but
> > as its author worked on a MacBook7,1 whereas mine is macmini4,1 I'm
 ~~
> > afraid either I misunderstood his advices concerning the 'setpci -s' (my
> > values where different) or that patch is not applicable to macmini.
> > 
> 
> 
> what is the result of 
> nvidia-detect
> ?
I can't tell because in the meantime I went back to the 'nouveau'
driver: up to now it hasn't yet frozen (cross fingers ;-)
However, Xorg.?.log showed the module was detected and loaded and this
fact is asserted by the following lines extracted from a 'journalctl -xb
--boot=-x' (where 'x' was the number of boot when nvidia was installed)

> 
> what does 
> sudo lshw -businfo -class bridge -class display
> report back?
> 

Ok, this is the result with nouveau installed, but it was identical when
nvidia was installed (of course, being hw stuff)

Bus info  Device  Class  Description

pci@:00:00.0  bridge MCP89 HOST Bridge
pci@:00:03.0  bridge MCP89 LPC Bridge
pci@:00:0e.0  bridge NVIDIA Corporation
pci@:01:00.0  bridge XIO2213A/B/XIO2221 PCI Express to 
PCI Bridge [Cheetah Express]
pci@:00:15.0  bridge NVIDIA Corporation
pci@:00:16.0  bridge NVIDIA Corporation
pci@:00:17.0<->   bridge MCP89 PCI Express Bridge
pci@:05:00.0<->   displayMCP89 [GeForce 320M]

> and the file you created
> /etc/grub.d/01_enable_vga.conf

> can you pleas list the contents of this file?

Here it is (I saved it before removng nvidia):

# 01_enable_vga.conf
# per modificare i valori del bridge e del display della nvidia
# cfr. proprietary-nvidia-drivers-on-mac-with-efi (ask ubuntu)
  setpci -s "00:17.0"  3e.b=8
  setpci -s "05:00.0"  04.b=7

>
Note that when I checked, as suggested by the ubuntu link author, with
  $ sudo setpci -s "00:17.0" 3e.b
08
  $ sudo setpci -s "05:00.0" 04.b
07
I obtained the correct values.

Some further considrations:
While I'm writing this answer I'm recalling to my mind that I was acting
in complete ignorance of what all that mean, particularly the 3e.b=8
etc. In the meantime I have desperately searched the web for an
explanation of hex structure, which I found a few hours ago. And the
only doubt, now, is that I might have first given that setpci
instruction with the same values of ubuntu post (05.b=7) and after
getting the black screen having corrected to 04.b=7.
I am still not sure which value would have been correct and if you know
please tell me just for the case I might go back again to nvidia in case
of new frequent frozes of nouveau.

Many thanks for your help. Regards, Ennio

-- 
[Perche' usare Win$ozz (dico io) se ..."anche uno sciocco sa farlo.   \\?//
 Fa' qualche cosa di cui non sei capace!"  (diceva Henry Miller) ](°|°)
[Why use Win$ozz (I say) if ... "even a fool can do that.  )=(
 Do something you aren't good at!" (as Henry Miller used to say) ]

Re: PAE or not PAE?

[Gene Heskett]

On Monday 12 March 2018 15:27:23 Hans wrote:

> > Note that the non PAE kernel in older Debian versions up to Jessie
> > lacked multi-processor (including multi-core and hyper-threading)
> > support.
>
> Yes, I read this, too. The N280 is a single core, but mith
> hyperthreading, I have two cores.
>
> Is this still so, that the non-pae-kernel lacks still hyperthreading,
> or does it do today, too?
>
> And second question: Is PAE preferred (with the look to speed) or
> better use non-pae?
>
> Cheers
>
> Hans

Both pae and hyperthreading take time, hyperthreading quite a bit more 
than pae. With hyperthreading, to switch to the 2nd task, takes a 
complete processor state stored on the stack, the stack pointer reloaded 
to point at the image of the 2nd task, then pull the full register dump 
for task 2 back into the processor. Then and only then can the first 
cycle devoted to task 2 be initiated. Ditto to swap back. For boxes that 
will run a realtime task, the first thing we do is turn off the 
hyperthreading. Its a solution that works ok, but I can't think of a 
better way to make a decently fast cpu into a provable slowpoke. All it 
really does for us is to help heat the shop. You can keep it above the 
dew point with electric heat to help control rust, or you can enable 
hyperthreading and its exactly the same turns of the electric meter 
either way.  An excellent demo of the TANSTAAFL principle.


-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Persistent naming rules - consulta

[remgasis remgasis]

En relación a tu primera observación ya el dispositivo estaba escaneado.
A tú última observación es correcta Matias. Revisé la documentación y es la
misma. A parte, dicha operación no  cambia ni siquiera eliminando los
archivos 60-block.rules y 60-persistent-storage, o cambiando la prioridad a
01-* de mi archivo de configuración.

​Muchas gracias.

Re: how to get tethering to working

[Ben Caradoc-Davies]

On 13/03/18 10:56, Long Wind wrote:

what should i do now?


Can you add it as a new Ethernet device in NetworkManager?

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Re: how to get tethering to working

[deloptes]

Long Wind wrote:

> then i run "dhclient enp0s19f2u6"

you don't have dhcp server on your phone, do you?

> but i can't access Internet
> BTW where is ifconfig?

sudo apt-get install net-tools

> what should i do now? Thanks!

https://wiki.debian.org/Mobile
https://wiki.debian.org/UseYourCellPhoneAsModem
https://wiki.debian.org/Android_Tethering

Re: instalar debian testing en HP con W10 (solucionado)

[tomas gonzalez]

Hola amigos yo creo que es un tema independiente del Grub, tanto en lo que
es UEFI, secure boot y particiones gpt

El 12 de marzo de 2018, 17:28, Galvatorix Torixgalva <
galvatorix2...@gmail.com> escribió:

> Holas,
>
> pongo un enlace en el que creo que podras encontrar lo que buscas
>
> http://www.gnu.org/software/grub/grub-documentation.html
>
> Saludos
>
>
> ​
>
>
> 
>  Libre
> de virus. www.avast.com
> 
> <#m_3134233435204245531_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

Multiple issues after update

[mmturin]

Hello,

 

after a recent dist-upgrade on my debian 9 server I am experimenting several issues with services complaining about missing permissions.

 

There has not been any major changes on that server but since the upgrade was done apachae, postfix and apt are complaining and refusing to work as intended.

 

The apache server shows a permission denied on all webpages, the postfix server just dies after a while ("systemctl status postfix" shows the service as active after startup)

 

apt update complains about permissions too.

 

Some DBus error appears too which I have never seen before the update

 

 

Since I have an old snapshot of the server I compared the permissions on the files in question and they all match, therefore I don't know where else to look.

 

Here is some of the relevant information and log entries:

 

 


apt update
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://ftp.de.debian.org/debian stretch InRelease
Hit:3 http://ftp.de.debian.org/debian stretch-updates InRelease
Hit:4 http://ftp.de.debian.org/debian stretch Release
Hit:5 https://download.docker.com/linux/debian stretch InRelease
Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files
Reading package lists... Done
Building dependency tree   
Reading state information... Done
All packages are up to date.
W: Download is performed unsandboxed as root as file '/var/lib/apt/lists/partial/ftp.de.debian.org_debian_dists_stretch_InRelease' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)

ls -l /var/lib/apt/lists/partial/ftp.de.debian.org_debian
ls: cannot access '/var/lib/apt/lists/partial/ftp.de.debian.org_debian': No such file or directory

 

ls -l /var/lib/apt/lists/
total 108268
-rw-r--r-- 1 root root    39105 Mar 11 04:04 download.docker.com_linux_debian_dists_stretch_InRelease
-rw-r--r-- 1 root root    16254 Feb 28 02:52 download.docker.com_linux_debian_dists_stretch_stable_binary-amd64_Packages
-rw-r--r-- 1 root root 39116092 Mar 10 10:33 ftp.de.debian.org_debian_dists_stretch_main_binary-amd64_Packages
-rw-r--r-- 1 root root  7115196 Jun 16  2017 ftp.de.debian.org_debian_dists_stretch_main_i18n_Translation-de
-rw-r--r-- 1 root root 1347 Jun 16  2017 ftp.de.debian.org_debian_dists_stretch_main_i18n_Translation-de%5fDE
-rw-r--r-- 1 root root 26457271 Mar 10 10:33 ftp.de.debian.org_debian_dists_stretch_main_i18n_Translation-en
-rw-r--r-- 1 root root 33781328 Mar 10 10:33 ftp.de.debian.org_debian_dists_stretch_main_source_Sources
-rw-r--r-- 1 root root   117943 Mar 10 11:22 ftp.de.debian.org_debian_dists_stretch_Release
-rw-r--r-- 1 root root 2434 Mar 10 11:36 ftp.de.debian.org_debian_dists_stretch_Release.gpg
-rw-r--r-- 1 root root    91028 Mar 12 15:35 ftp.de.debian.org_debian_dists_stretch-updates_InRelease
-rw-r--r-- 1 root root    34570 Feb 11 21:45 ftp.de.debian.org_debian_dists_stretch-updates_main_binary-amd64_Packages
-rw-r--r-- 1 root root 2704 Feb 11 21:45 ftp.de.debian.org_debian_dists_stretch-updates_main_binary-amd64_Packages.diff_Index
-rw-r--r-- 1 root root    21713 Jan 29 21:29 ftp.de.debian.org_debian_dists_stretch-updates_main_i18n_Translation-en
-rw-r--r-- 1 root root 2212 Jan 29 21:29 ftp.de.debian.org_debian_dists_stretch-updates_main_i18n_Translation-en.diff_Index
-rw-r--r-- 1 root root    13564 Feb 11 21:45 ftp.de.debian.org_debian_dists_stretch-updates_main_source_Sources
-rw-r--r-- 1 root root 2704 Feb 11 21:45 ftp.de.debian.org_debian_dists_stretch-updates_main_source_Sources.diff_Index
-rw-r- 1 root root    0 Jul 26  2016 lock
drwx-- 2 _apt root 4096 Mar 12 21:11 partial
-rw-r--r-- 1 root root    62959 Mar 11 20:01 security.debian.org_dists_stretch_updates_InRelease
-rw-r--r-- 1 root root  1868567 Mar 10 22:43 security.debian.org_dists_stretch_updates_main_binary-amd64_Packages
-rw-r--r-- 1 root root  1048251 Mar 10 22:43 security.debian.org_dists_stretch_updates_main_i18n_Translation-en
-rw-r--r-- 1 root root  1022428 Mar 10 22:43 security.debian.org_dists_stretch_updates_main_source_Sources


the partial folder is empty

 


[Mon Mar 12 20:48:22.711299 2018] [mpm_prefork:notice] [pid 1053] AH00163: Apache/2.4.25 (Debian) OpenSSL/1.0.2l configured -- resuming normal operations
[Mon Mar 12 20:48:22.791915 2018] [core:notice] [pid 1053] AH00094: Command line: '/usr/sbin/apache2'
[Mon Mar 12 20:48:38.739798 2018] [ssl:error] [pid 1113] (13)Permission denied: [client :37336] AH01972: could not resolve address of OCSP responder ocsp.int-x3.letsencrypt.org
[Mon Mar 12 20:48:38.739889 2018] [ssl:error] [pid 1113] AH01941: stapling_renew_response: responder error
[Mon Mar 12 20:48:38.778277 2018] [core:error] [pid 1113] (13)Permission denied: [client :37336] AH00035: access to / denied (filesystem path '/var') because search permissions are missing on a component of the path
[Mon Mar 12 20:48:38.881378 2018] [core:error] [pid 1113] 

Re: instalar debian testing en HP con W10 (solucionado)

[Galvatorix Torixgalva]

Holas,

pongo un enlace en el que creo que podras encontrar lo que buscas

http://www.gnu.org/software/grub/grub-documentation.html

Saludos


​


Libre
de virus. www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Re: PAE or not PAE?

[Pascal Hambourg]

Le 12/03/2018 à 20:27, Hans a écrit :

Note that the non PAE kernel in older Debian versions up to Jessie
lacked multi-processor (including multi-core and hyper-threading) support.


Yes, I read this, too. The N280 is a single core, but mith hyperthreading, I
have two cores.

Is this still so, that the non-pae-kernel lacks still hyperthreading, or does
it do today, too?


"Today" does not tell much. It depends what Debian version you have.
Since Stretch, the non PAE kernel supports multiprocessing.


And second question: Is PAE preferred (with the look to speed) or better use
non-pae?


PAE does not make the kernel faster. On the contrary, as it adds an 
extra indirection when accessing memory.

Re: PAE or not PAE?

[Neo]

Am 12.03.2018 um 20:04 schrieb Pascal Hambourg:


No, you also need it on machines with 4 GiB of RAM and remapping 
capability, in order to use the part of the RAM which is remapped 
beyond the 4-GiB boundary due to the "PCI hole". Usually the remapped 
memory amount is about 500 MB, but I have seen machines remapping 1 
GiB or even 2 GiB, leaving only 2 or 3 GiB of usable RAM with a non 
PAE kernel.


Note that the non PAE kernel in older Debian versions up to Jessie 
lacked multi-processor (including multi-core and hyper-threading) 
support.




Thx for the clarification.

Re: PAE or not PAE?

[Pascal Hambourg]

Le 12/03/2018 à 20:04, Pascal Hambourg a écrit :

Le 12/03/2018 à 12:31, Neo a écrit :


You just need this on 32bit machines with more than 4GB of RAM.


No, you also need it on machines with 4 GiB of RAM and remapping 
capability, in order to use the part of the RAM which is remapped beyond 
the 4-GiB boundary due to the "PCI hole". Usually the remapped memory 
amount is about 500 MB, but I have seen machines remapping 1 GiB or even 
2 GiB, leaving only 2 or 3 GiB of usable RAM with a non PAE kernel.


Note that the non PAE kernel in older Debian versions up to Jessie 
lacked multi-processor (including multi-core and hyper-threading) support.


I forgot to mention that the NX/XD bit used by the "execute disable" 
protection against execution of data pages is available only with PAE.

Re: PAE or not PAE?

[Hans]

> Note that the non PAE kernel in older Debian versions up to Jessie
> lacked multi-processor (including multi-core and hyper-threading) support.

Yes, I read this, too. The N280 is a single core, but mith hyperthreading, I 
have two cores. 

Is this still so, that the non-pae-kernel lacks still hyperthreading, or does 
it do today, too?

And second question: Is PAE preferred (with the look to speed) or better use 
non-pae?

Cheers

Hans

Re: PAE or not PAE?

[Pascal Hambourg]

Le 12/03/2018 à 12:31, Neo a écrit :

No PAE.

For 2GB of RAM it makes no sense.


Indeed.


You just need this on 32bit machines with more than 4GB of RAM.


No, you also need it on machines with 4 GiB of RAM and remapping 
capability, in order to use the part of the RAM which is remapped beyond 
the 4-GiB boundary due to the "PCI hole". Usually the remapped memory 
amount is about 500 MB, but I have seen machines remapping 1 GiB or even 
2 GiB, leaving only 2 or 3 GiB of usable RAM with a non PAE kernel.


Note that the non PAE kernel in older Debian versions up to Jessie 
lacked multi-processor (including multi-core and hyper-threading) support.

Re: bug remmina

[Bernard Schoenacker]

- Mail original -
> De: "hamster" 
> À: debian-user-french@lists.debian.org
> Envoyé: Lundi 12 Mars 2018 17:48:32
> Objet: Re: bug remmina
> 
> Le 12/03/2018 à 15:40, Bernard Schoenacker a écrit :
> > 
> > 
> > - Mail original -
> >> De: "hamster" 
> >> À: debian-user-french@lists.debian.org
> >> Envoyé: Lundi 12 Mars 2018 13:01:26
> >> Objet: bug remmina
> >>
> >> Hello
> >>
> >> J'arrive pas a faire marcher remmina.
> >>
> >> Je commence par monter un tunnel ssh, ensuite je me connecte a
> >> localhost
> >> (donc au tunnel) avec le protocole VNC. La fenetre qui devrait me
> >> montrer le bureau distant s'ouvre, et se referme aussitot. Je suis
> >> sur
> >> que le souci ne viens pas de l'ordi distant parce que ca marche
> >> avec
> >> vinagre a la place de remmina, par contre c'est très lent.
> >>
> >> Je n'ai pas trouvé de fichier de log, ca ne me dit pas grand chose
> >> quand
> >> je lance remmina dans un terminal pour voir d'éventuels messages
> >> d'erreur. J'ai essayé de réinstaller remmina, et d'installer le
> >> paquet
> >> de débuggage, ca n'améliore rien. Je n'ai pas trouvé d'option
> >> genre
> >> -v
> >> dans le man pour que ca soit plus verbeux. Et j'ai pas du mettre
> >> les
> >> bons mots clef dans google parce qu'il ne me sort rien
> >> d'interessant.
> >> Tout ce que j'ai a me mettre sous la dent c'est le message suivant
> >> qui
> >> sort dans le terminal :
> >>
> >> Gtk-Message: GtkDialog mapped without a transient parent. This is
> >> discouraged.
> >>
> >> C'est peu et je sais pas quoi en faire. Quelqu'un a une idée pour
> >> trouver ce qui coince ?
> >>
> > 
> > 
> > bonjour,
> > 
> > pourrais tu passer à x2go server ?
> > 
> > et x2goclient ou pyhoca c'est très réactif ...
> > 
> > avantage: ouverture par le port ssh
> > 
> > 
> > autrement en tunnel ssh c'est :
> > 
> > ssh -C -x
> 
> Sur jessie, j'ai x2go client mais pas server.
> 
bonjour,

pour x2go :

https://wiki.x2go.org/doku.php/doc:installation:x2goserver
https://wiki.x2go.org/doku.php/wiki:repositories:debian


cat /etc/apt/sources.list.d/x2go.list
deb http://packages.x2go.org/debian jessie main

slt
bernard

Re: bug remmina

[hamster]

Le 12/03/2018 à 15:40, Bernard Schoenacker a écrit :



- Mail original -

De: "hamster" 
À: debian-user-french@lists.debian.org
Envoyé: Lundi 12 Mars 2018 13:01:26
Objet: bug remmina

Hello

J'arrive pas a faire marcher remmina.

Je commence par monter un tunnel ssh, ensuite je me connecte a
localhost
(donc au tunnel) avec le protocole VNC. La fenetre qui devrait me
montrer le bureau distant s'ouvre, et se referme aussitot. Je suis
sur
que le souci ne viens pas de l'ordi distant parce que ca marche avec
vinagre a la place de remmina, par contre c'est très lent.

Je n'ai pas trouvé de fichier de log, ca ne me dit pas grand chose
quand
je lance remmina dans un terminal pour voir d'éventuels messages
d'erreur. J'ai essayé de réinstaller remmina, et d'installer le
paquet
de débuggage, ca n'améliore rien. Je n'ai pas trouvé d'option genre
-v
dans le man pour que ca soit plus verbeux. Et j'ai pas du mettre les
bons mots clef dans google parce qu'il ne me sort rien d'interessant.
Tout ce que j'ai a me mettre sous la dent c'est le message suivant
qui
sort dans le terminal :

Gtk-Message: GtkDialog mapped without a transient parent. This is
discouraged.

C'est peu et je sais pas quoi en faire. Quelqu'un a une idée pour
trouver ce qui coince ?




bonjour,

pourrais tu passer à x2go server ?

et x2goclient ou pyhoca c'est très réactif ...

avantage: ouverture par le port ssh


autrement en tunnel ssh c'est :

ssh -C -x


Sur jessie, j'ai x2go client mais pas server.

Re: Broken kernel?

[Gene Heskett]

On Monday 12 March 2018 06:26:09 Hans wrote:

> Hi Gene,
>
> got into the same problem a long time ago. In my case I got in trouble
> with one of the kernel modules, it was the graphics driver module.
>
Somebody's quoting is making it look as if I'm the OP. I am not, and my 
stuff is running just fine.

But unless I missed the memo, the OP still has a problem.

FWIW, the nvidia driver is a profane word in my machine control world. It 
doesn't like to share its toys, locking out the irq's for hundreds of 
milliseconds at a time, when the cpu is expected to check the machines 
status at millisecond intervals to see if its tripped a limit switch 
etc.

The nouveau driver doesn't do that. And its fast enough to draw a 
backplot of the machines motion in close to realtime.

The ATI drivers are better, but they also do the irq lockouts for too 
long, so the "better" is still relative, and still not good enough for 
good, 100% safe, machine control. ATM, my x86 boxes are all running the 
intel i915 drivers, which seem to be doing things well.

> This one got in trouble with the vesa driver (somehow), and so it
> hanged at boot with a black screen.
>
> The solution was at that time, to dienstall all the Nvidia packages,
> which of course let a new initram-file created, which of course got no
> nvidia kernel module installed.
>
> If there is in your case also a kernel module the problem, you might
> be able, to blacklist the problematic module. If you have access to
> the hardddrive with the kernel modules (i.e. by using a livefile dvd),
> you can either edit the blacklist-modules file, or , if this does not
> work, by removing the modules physically out of the way from the
> modules directory (sorry for my bad English).
>
> The others got right: amd64 means, that the kernel is running on Intel
> compatible 64-bit processors. And you are also right: There was a
> time, when there were also special 64-bit Intel-cpus in the repo (when
> I remember correchtly, these were aimed for Itanium cpu's).

Which somehow seem to have vanished from the used market.
>
> Another hint: If you are able, to start a debian live cd (the actual
> one), you can take a look, which kernel modules are loaded, and also,
> which graphical driver is loaded. However, I believe, you are quite
> happy, when you are able, to ge a shell! So just try a small live
> system.
>
> If the debian live system failes, you may try Knoppix (the version
> with the same kernel version) or maybe another Debian based livesystem
> (I have kali- linux or aptosid in my mind).
>
> Long words, little sense - I hope this helps a little bit.
>
> Good luck and all the best!
>
> Hans

Gonna need it Hans, I made the mistake of looking out the front door at 
my wheelchair ramp construction area this morning, finding 1/4" snow on 
all my nice new lumber. And I still have one, maybe two long days work 
demolishing the deck where the ramp will go. Taking screws out with a 
big prybar. It would be nice if they'd just unscrew, but they've been 
there 15+ years. Takeing 20 calendars off my pile of discards would help 
too as I'm not the man I once was, even once...  Sigh.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Remote desktop

[Paul van der Vlis]

Op 12-03-18 om 14:52 schreef lists:
> On 12-3-2018 14:25, Paul van der Vlis wrote:
>> Misschien dat je x11vnc bedoeld, maar dat is -als ik me niet vergis-
>> vrij traag.
> 
> Sorry, ik type uit mn hoofd.
> 
> Ik bedoelde: xrdp met remmina.

Xrdp kun je weer op verschillende manieren implementeren, vaak gebruikt
het een VNC server als backend die het eigenlijke werk doet.
Dan draait er alleen extra proces, wat misschien handig is voor Windows
gebruikers maar weinig voordelen heeft voor Linux gebruikers.

Maar ik heb ook gehoord van een xorg-driver voor Xrdp.
https://github.com/neutrinolabs/xorgxrdp
Volgens mij zit dat niet in Debian.

Groeten,
Paul



-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Re: Remote desktop

[Paul van der Vlis]

Op 12-03-18 om 14:03 schreef lists:
> 
> On 11-3-2018 14:11, lunixbox wrote:
>> Advies gezocht om een RD op te zetten op zoon computer, debian op
>> beide en andere stad.
>>
>> Gaarne advies
> 
> Misschien xvnc als server, 

Als ik zoek op "xvnc", dan zit dit alleen in het pakket "linuxvnc". En
dat blijkt voor text te zijn volgens de beschrijving:
https://packages.debian.org/stretch/linuxvnc
Ik ken dit pakket verder niet.

Misschien dat je x11vnc bedoeld, maar dat is -als ik me niet vergis-
vrij traag.

Ik weet dat er ook een tigervnc-plugin voor Xorg is, maar daarmee heb ik
nog niet veel ervaring. Het pakket heet "tigervnc-xorg-extension".

> en remmina als client?
Remmina is inderdaad een mooie client, maar mischien dat tigervncclient
sneller is. Met de vraag welke client beter is heb ik me nog niet zo erg
bezig gehouden.

Groeten,
Paul.


-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Re: Remote desktop

[lists]

On 11-3-2018 14:11, lunixbox wrote:
Advies gezocht om een RD op te zetten op zoon computer, debian op beide 
en andere stad.


Gaarne advies


Misschien xvnc als server, en remmina als client?

MJ

Re: Persistent naming rules - consulta

[Matias Mucciolo]

On Monday, March 12, 2018 9:10:26 AM -03 Matias Mucciolo wrote:
> On Sunday, March 11, 2018 10:54:11 PM -03 remgasis remgasis wrote:
> > Saludos a todos.
> > 
> > Les escribo en esta oportunidad ya que he tratado de configurar una regla
> > udev para cambiar la denominación de un disco duro virtual scsi (sin
> > particiones) y la misma no ha funcionado. El archivo fstab está
> > configurado
> > con UUIDs; sin problemas.
> > 
> > *Pasos: denominación del dispositivo /dev/sdc a denominación /dev/sdd.*
> > 
> > 
> > *Paso 1. *Se obtuvo la información necesaria del dispositivo agregado:
> > 
> > #udevadm info -a /sys/dev/block/X:X
> > 
> > 
> > *Paso 2*. Se siguió el orden lógico para configurar la regla en
> > /etc/udev/rules.d/98-persistent-disk.rules
> > 
> > KERNEL=="sdc", ACTION=="add", KERNELS=="0:0:2:0", NAME="sdd"
> > 
> > 
> > *Paso 3*. Se guardó la regla.
> > 
> > 
> > *Paso 4. *Se recarga la configuración:
> > 
> > #udevadm control --reload-rules
> > 
> > Resultado: fdisk -l /dev/sd? como /dev/sdc
> > 
> > 
> > *Paso 5.* Se verifica el error:
> > 
> > #udevadm test /sys/dev/block/8\:32
> > 
> > Resultado: NAME="sdd" ignored, kernel device nodes cannot be renamed;
> > please fix it in /etc/udev/rules.d/98-persistent-disk-rules:1
> > 
> > 
> > *Paso 4.* Se cambia la regla:
> > 
> > KERNEL=="sdc", NAME="sdd"
> > 
> > Se guardó la misma en dos momentos longitudinales en /lib/udev/rules.d y
> > /etc/udev/rules.d.
> > 
> > *Paso 6.* Se ejecuta:
> > 
> > #udevadm test /sys/dev/block/8\:32
> > 
> > Resultado: NAME="sdd" ignored, kernel device nodes cannot be renamed;
> > please fix it in /etc/udev/rules.d/98-persistent-disk-rules:1
> > 
> > *Paso 7.* Se reformula el problema y se crea un link en el archivo de
> > configuración:
> > 
> > KERNEL=="sdc", SYMLINK+="sdd"
> > 
> > Resultado: todo bien.
> > 
> > *Paso 8.*  Se cambia la regla:
> > 
> > KERNEL=="sdc", ACTION=="add|change", NAME="sdd"
> > 
> > Resultado:  NAME="sdd" ignored, kernel device nodes cannot be renamed;
> > 
> > 
> > *?Por qué no puedo cambiar el nombre del dispositivo?*
> 
> Hola
> 
> El error te lo dice explícitamente...  "kernel device nodes cannot be
> renamed" quizas tengas que reiniciar...
> también probaría  re escanear el scsi  bus..
> 
> ejemplo:
> echo "- - -" > /sys/class/scsi_host/host0/scan
> 
> pero no se si afectara en este caso...pero no cuesta nada probar.
> 
> Saludos
> Matias.-

Mas aun...recien mirando el man de udev dice:

NAME
The name to use for a network interface. See systemd.link(5) for a 
higher-level mechanism for setting the interface name. The name of a
device node cannot be changed by udev, only additional symlinks can 
be created.

parece ser por una complicación con la b*sofia de systemd sacaron 
renombrar devices nodes..

Matias.-

Re: Persistent naming rules - consulta

[Matias Mucciolo]

On Sunday, March 11, 2018 10:54:11 PM -03 remgasis remgasis wrote:
> Saludos a todos.
> 
> Les escribo en esta oportunidad ya que he tratado de configurar una regla
> udev para cambiar la denominación de un disco duro virtual scsi (sin
> particiones) y la misma no ha funcionado. El archivo fstab está configurado
> con UUIDs; sin problemas.
> 
> *Pasos: denominación del dispositivo /dev/sdc a denominación /dev/sdd.*
> 
> 
> *Paso 1. *Se obtuvo la información necesaria del dispositivo agregado:
> 
> #udevadm info -a /sys/dev/block/X:X
> 
> 
> *Paso 2*. Se siguió el orden lógico para configurar la regla en
> /etc/udev/rules.d/98-persistent-disk.rules
> 
> KERNEL=="sdc", ACTION=="add", KERNELS=="0:0:2:0", NAME="sdd"
> 
> 
> *Paso 3*. Se guardó la regla.
> 
> 
> *Paso 4. *Se recarga la configuración:
> 
> #udevadm control --reload-rules
> 
> Resultado: fdisk -l /dev/sd? como /dev/sdc
> 
> 
> *Paso 5.* Se verifica el error:
> 
> #udevadm test /sys/dev/block/8\:32
> 
> Resultado: NAME="sdd" ignored, kernel device nodes cannot be renamed;
> please fix it in /etc/udev/rules.d/98-persistent-disk-rules:1
> 
> 
> *Paso 4.* Se cambia la regla:
> 
> KERNEL=="sdc", NAME="sdd"
> 
> Se guardó la misma en dos momentos longitudinales en /lib/udev/rules.d y
> /etc/udev/rules.d.
> 
> *Paso 6.* Se ejecuta:
> 
> #udevadm test /sys/dev/block/8\:32
> 
> Resultado: NAME="sdd" ignored, kernel device nodes cannot be renamed;
> please fix it in /etc/udev/rules.d/98-persistent-disk-rules:1
> 
> *Paso 7.* Se reformula el problema y se crea un link en el archivo de
> configuración:
> 
> KERNEL=="sdc", SYMLINK+="sdd"
> 
> Resultado: todo bien.
> 
> *Paso 8.*  Se cambia la regla:
> 
> KERNEL=="sdc", ACTION=="add|change", NAME="sdd"
> 
> Resultado:  NAME="sdd" ignored, kernel device nodes cannot be renamed;
> 
> 
> *?Por qué no puedo cambiar el nombre del dispositivo?*

Hola

El error te lo dice explícitamente...  "kernel device nodes cannot be renamed"
quizas tengas que reiniciar...
también probaría  re escanear el scsi  bus..

ejemplo:
echo "- - -" > /sys/class/scsi_host/host0/scan

pero no se si afectara en este caso...pero no cuesta nada probar.

Saludos
Matias.-

Re: [Debian-Stretch on macmini-4.1] Can't get X working with nvidia

[Henning Follmann]

On Sat, Mar 10, 2018 at 12:21:17AM +0100, Ennio-Sr wrote:
> Hi all!
> 
> since I installed new kernels (i.e. 4.9.0 and 4.14.0-0) to be
> half-protected against Meltdown/Spectre I was having freezing problems
> with X using 'nouveau' driver (never had any problem with older
> kernels). So i decided to try the original non-free nvidia driver as
> provided by the nvidia-legacy-340xx-driver and relted packages. Now,
> after struggling for a couple of days to search the web for a possible
> solution to the 'black screen' coming out running startx, I'm curious to
> know if there is any of you with the same hardware who found a
> workaround and would share it.

I do have a macbookpro and for me it was exactly the issue. e.g. The
graphics adapter by default is not bus master.

> 
> Looking at the various logs I can't find any clue. 
> Reading  I also
> consulted the suggested link 'http://askubuntu.com/a/613573/134848' but
> as its author worked on a MacBook7,1 whereas mine is macmini4,1 I'm
> afraid either I misunderstood his advices concerning the 'setpci -s' (my
> values where different) or that patch is not applicable to macmini.
> 


what is the result of 
nvidia-detect
?


what does 
sudo lshw -businfo -class bridge -class display
report back?

and the file you created
/etc/grub.d/01_enable_vga.conf

can you pleas list the contents of this file?




-- 
Henning Follmann   | hfollm...@itcfollmann.com

bug remmina

[hamster]

Hello

J'arrive pas a faire marcher remmina.

Je commence par monter un tunnel ssh, ensuite je me connecte a localhost 
(donc au tunnel) avec le protocole VNC. La fenetre qui devrait me 
montrer le bureau distant s'ouvre, et se referme aussitot. Je suis sur 
que le souci ne viens pas de l'ordi distant parce que ca marche avec 
vinagre a la place de remmina, par contre c'est très lent.


Je n'ai pas trouvé de fichier de log, ca ne me dit pas grand chose quand 
je lance remmina dans un terminal pour voir d'éventuels messages 
d'erreur. J'ai essayé de réinstaller remmina, et d'installer le paquet 
de débuggage, ca n'améliore rien. Je n'ai pas trouvé d'option genre -v 
dans le man pour que ca soit plus verbeux. Et j'ai pas du mettre les 
bons mots clef dans google parce qu'il ne me sort rien d'interessant. 
Tout ce que j'ai a me mettre sous la dent c'est le message suivant qui 
sort dans le terminal :


Gtk-Message: GtkDialog mapped without a transient parent. This is 
discouraged.


C'est peu et je sais pas quoi en faire. Quelqu'un a une idée pour 
trouver ce qui coince ?

Re: PAE or not PAE?

[Neo]

No PAE.

For 2GB of RAM it makes no sense. You just need this on 32bit machines 
with more than 4GB of RAM.


HTH

Tom


Am 12.03.2018 um 12:11 schrieb Hans:


Hi folks,

as I have still trouble with restore after suspend-to-disk, I read, 
that this issue was gone with a kernel with non pae.


This brings the following question:

MUST I use (or is it RECOMMENDED?) a kernel with PAE in my system?

My system:

CPU N280 (with PAE usable)

2 GB RAM

32-Bit operating system (debian/testing)

Do I have any advantages or disadvantages by using a PAE-Kernel or 
NON-PAE-kernel? I will never be able to use more than 2 GB RAM, as 
this EEEPC got only one RAM slot (I never saw a single DDR2 4 GB 
RAM-module, just 2 GB).


Thanks for the hint.

Best

Hans

P.S. For Gene Haskett: I tried a NON-PAE kernel on my EEEPC - did not 
boot (just an idea)

PAE or not PAE?

[Hans]

Hi folks, 

as I have still trouble with restore after suspend-to-disk, I read, that this 
issue was gone 
with a kernel with non pae.

This brings the following question: 

MUST I use (or is it RECOMMENDED?) a kernel with PAE in my system?

My system:

CPU N280 (with PAE usable)
2 GB RAM
32-Bit operating system (debian/testing)

Do I have any advantages or disadvantages by using a PAE-Kernel or 
NON-PAE-kernel? I 
will never be able to use more than 2 GB RAM, as this EEEPC got only one RAM 
slot (I 
never saw a single DDR2 4 GB RAM-module, just 2 GB).

Thanks for the hint.

Best 

Hans

P.S. For Gene Haskett: I tried a NON-PAE kernel on my EEEPC - did not boot 
(just an idea)  

Re: Broken kernel?

[floris]

Gene Heskett schreef op 2018-03-12 10:51:

On Monday 12 March 2018 05:20:07 floris wrote:


Tom Furie schreef op 2018-03-12 09:41:
> On Mon, Mar 12, 2018 at 04:34:56AM -0400, Gene Heskett wrote:
>> I just happen to have 2 machines on my home network that are Intel
>> D525MW
>> motherboards, with dual core intel atom 1.8 GHz cpu's. They run
>> flawlessly from powerbump to powerbump, on an rtai patched but now
>> elderly kernel, a kernel that says its for an i686-pae. Not an
>> AMD64.
>
> Yes, all 64-bit x86 compatible CPUs are also 32-bit compatible.
>
> Cheers,
> Tom

Intel says the Intel Atom CPU N2600 @ 1.60GHz is 64bit[1]. The am64
kernel is the right one.

[1]https://ark.intel.com/products/58916/Intel-Atom-Processor-N2600-1M-
Cache-1_6-GHz ---
Floris
Call off the dogs, you and several other are correct, and I should not 
be

posting bad info at 3 or 4 am when the only reason I'm up at all is to
take the recyclables to the curb. Its just that I've been running the 
32

bit versions so well for more than half a decade I was convinced that
was the way to fly.

But does this not leave the OP scratching his head, wondering why his
machine won't boot? So we are back to the starting square and I'm out 
of

ammo. At this point I'd run memtest86 long enough, at least overnight,
to verify its not bad memory, and if it is, reseat the lappy style 
dimm,

they are getting old enough that if the air is bad, some contact
exercise might be in order. Mine never get turned off except for power
failures, so thermal stress in the atoms mounting has not stuck up a
hand yet. For those that are shut down, thermal cycling might begin to
be a problem.

I'm going back to bed, where anyone my age ought to be this time of the
morning since he's busy building a wheelchair ramp so I can bring my 
xyl
home with a busted osteoporosis riddled leg. If I ever find the guy 
that

called these the golden years, I'd like to see where the gold is in his
house.


I just checked and the dog is still playing in the backyard, so you 
don't have to worry :-)


Back to OP's question. The Intel Atom N2600 is not very Linux/ 
opensource friendly. I have and old laptop with the same processor and 
also have mixed result with different kernels. Fortunately the Debian 
Stable/ Strech amd64 kernel works without big issues. The Testing 
version has problems with the gma500 module. (I know the OP has a 
different issue and doesn't use the build-in GPU.)


@OP
Do you have a custom initramfs? Check 
/etc/initramfs-tools/initramfs.conf and make sure MODULES is set to 
"most".


---
Floris

Re: Broken kernel?

[Hans]

Hi Gene, 

got into the same problem a long time ago. In my case I got in trouble with 
one of the kernel modules, it was the graphics driver module.

This one got in trouble with the vesa driver (somehow), and so it hanged at 
boot with a black screen.

The solution was at that time, to dienstall all the Nvidia packages, which of 
course let a new initram-file created, which of course got no nvidia kernel 
module installed.

If there is in your case also a kernel module the problem, you might be able, 
to blacklist the problematic module. If you have access to the hardddrive with 
the kernel modules (i.e. by using a livefile dvd), you can either edit the 
blacklist-modules file, or , if this does not work, by removing the modules 
physically out of the way from the modules directory (sorry for my bad 
English).

The others got right: amd64 means, that the kernel is running on Intel 
compatible 64-bit processors. And you are also right: There was a time, when 
there were also special 64-bit Intel-cpus in the repo (when I remember 
correchtly, these were aimed for Itanium cpu's).

Another hint: If you are able, to start a debian live cd (the actual one), you 
can take a look, which kernel modules are loaded, and also, which graphical 
driver is loaded. However, I believe, you are quite happy, when you are able, 
to ge a shell! So just try a small live system. 

If the debian live system failes, you may try Knoppix (the version with the 
same kernel version) or maybe another Debian based livesystem (I have kali-
linux or aptosid in my mind).

Long words, little sense - I hope this helps a little bit.

Good luck and all the best!

Hans 

   

Re: Broken kernel?

[Alexander V. Makartsev]

On 12.03.2018 04:36, John ff wrote:
>
> i have an Intel Atom CPU N2600 @ 1.60GHz that I fairly recently
> upgraded from Whezzy to Jessie, but I cannot boot the kernel(s) that
> came with Jessie.
>
> All is OK with vmlinuz-3.2.0-4-amd64, but both 3.16.0-4-amd64 and
> 3.16.0-5-amd64 fail to load. When equipped with a screen I see it
> says Loading .. but it does not complete with no disk activity.
I have an old Atom N450 CPU based NetBook right next to me, running
'jessie' with "3.16.0-5-amd64" kernel.
It was upgraded continuously from "Squeeze" without any issues.
I suggest you to boot with "single" and "debug" kernel parameters, with
"quiet" parameter removed and look into log output.
Hopefully that would help to find out where exactly it stops booting
process.

-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 

Re: Broken kernel?

[Tom Furie]

On Mon, Mar 12, 2018 at 05:51:07AM -0400, Gene Heskett wrote:

> Call off the dogs, you and several other are correct, and I should not be 
> posting bad info at 3 or 4 am when the only reason I'm up at all is to 
> take the recyclables to the curb. Its just that I've been running the 32 
> bit versions so well for more than half a decade I was convinced that 
> was the way to fly.

I wasn't aiming no set the dogs on anybody, merely looking to clarify
that amd64 packages aren't only for AMD processors or 32-bit packages
only for 32-bit processors.

Indeed, I still run 32-bit on a couple of 64-bit capable systems due to
the factors that they were originally built on 32-bit hardware and their
configuration and workload really wouldn't benefit in any real terms
from 64-bit, so the work involved in the transfer wouldn't be well
spent.

Cheers,
Tom

-- 
1: No code table for op: ++post


signature.asc
Description: Digital signature

Re: Broken kernel?

[Tom Furie]

On Mon, Mar 12, 2018 at 10:20:07AM +0100, floris wrote:

> Intel says the Intel Atom CPU N2600 @ 1.60GHz is 64bit[1]. The am64 kernel
> is the right one.

Either a 32-bit or 64-bit kernel could be equally valid, depending on
other parameters.

Cheers,
Tom

-- 
All God's children are not beautiful.  Most of God's children are, in fact,
barely presentable.
-- Fran Lebowitz, "Metropolitan Life"


signature.asc
Description: Digital signature

Re: Broken kernel?

[Gene Heskett]

On Monday 12 March 2018 05:20:07 floris wrote:

> Tom Furie schreef op 2018-03-12 09:41:
> > On Mon, Mar 12, 2018 at 04:34:56AM -0400, Gene Heskett wrote:
> >> I just happen to have 2 machines on my home network that are Intel
> >> D525MW
> >> motherboards, with dual core intel atom 1.8 GHz cpu's. They run
> >> flawlessly from powerbump to powerbump, on an rtai patched but now
> >> elderly kernel, a kernel that says its for an i686-pae. Not an
> >> AMD64.
> >
> > Yes, all 64-bit x86 compatible CPUs are also 32-bit compatible.
> >
> > Cheers,
> > Tom
>
> Intel says the Intel Atom CPU N2600 @ 1.60GHz is 64bit[1]. The am64
> kernel is the right one.
>
> [1]https://ark.intel.com/products/58916/Intel-Atom-Processor-N2600-1M-
>Cache-1_6-GHz ---
> Floris
Call off the dogs, you and several other are correct, and I should not be 
posting bad info at 3 or 4 am when the only reason I'm up at all is to 
take the recyclables to the curb. Its just that I've been running the 32 
bit versions so well for more than half a decade I was convinced that 
was the way to fly.

But does this not leave the OP scratching his head, wondering why his 
machine won't boot? So we are back to the starting square and I'm out of 
ammo. At this point I'd run memtest86 long enough, at least overnight, 
to verify its not bad memory, and if it is, reseat the lappy style dimm, 
they are getting old enough that if the air is bad, some contact 
exercise might be in order. Mine never get turned off except for power 
failures, so thermal stress in the atoms mounting has not stuck up a 
hand yet. For those that are shut down, thermal cycling might begin to 
be a problem.

I'm going back to bed, where anyone my age ought to be this time of the 
morning since he's busy building a wheelchair ramp so I can bring my xyl 
home with a busted osteoporosis riddled leg. If I ever find the guy that 
called these the golden years, I'd like to see where the gold is in his 
house.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Broken kernel?

[floris]

Tom Furie schreef op 2018-03-12 09:41:

On Mon, Mar 12, 2018 at 04:34:56AM -0400, Gene Heskett wrote:

I just happen to have 2 machines on my home network that are Intel 
D525MW

motherboards, with dual core intel atom 1.8 GHz cpu's. They run
flawlessly from powerbump to powerbump, on an rtai patched but now
elderly kernel, a kernel that says its for an i686-pae. Not an AMD64.


Yes, all 64-bit x86 compatible CPUs are also 32-bit compatible.

Cheers,
Tom


Intel says the Intel Atom CPU N2600 @ 1.60GHz is 64bit[1]. The am64 
kernel is the right one.


[1]https://ark.intel.com/products/58916/Intel-Atom-Processor-N2600-1M-Cache-1_6-GHz
---
Floris

Re: Broken kernel?

[Tom Furie]

On Mon, Mar 12, 2018 at 04:34:56AM -0400, Gene Heskett wrote:

> I just happen to have 2 machines on my home network that are Intel D525MW 
> motherboards, with dual core intel atom 1.8 GHz cpu's. They run 
> flawlessly from powerbump to powerbump, on an rtai patched but now 
> elderly kernel, a kernel that says its for an i686-pae. Not an AMD64.

Yes, all 64-bit x86 compatible CPUs are also 32-bit compatible.

Cheers,
Tom

-- 
Support bacteria -- it's the only culture some people have!


signature.asc
Description: Digital signature

Re: Broken kernel?

[Gene Heskett]

On Monday 12 March 2018 02:54:49 Tom Furie wrote:

> On Sun, Mar 11, 2018 at 11:42:44PM -0400, Gene Heskett wrote:
> > AMD64 would be like its built for an AMD phenom or newer. You want a
> > kernel built for an intel cpu.
>
> AMD64, in the context of package naming, is for any 64-bit x86
> compatible CPU.
>
> Cheers,
> Tom

I just happen to have 2 machines on my home network that are Intel D525MW 
motherboards, with dual core intel atom 1.8 GHz cpu's. They run 
flawlessly from powerbump to powerbump, on an rtai patched but now 
elderly kernel, a kernel that says its for an i686-pae. Not an AMD64.

gene@shop:~$ uname -r
3.4-9-rtai-686-pae

gene@lathe:~$ uname -r
3.4-9-rtai-686-pae

This kernel is in fact not a pae kernel, because the rtai patches disable 
that, we found that out after the fact, but those 2 machines only have 
2GB of dram, so the lack of pae is moot. Enabling pae on those wrecks 
the context switching latency anyway. And that is far more important for 
what they are doing (running linuxcnc) than anything else they may be 
asked to do. Yes, they are also 32 bit kernels, again because the 
context switch time for a 32 bit kernel is 1/2 the context switching 
time for a full 64 bit kernel. So its possible we may be compareing 
apples to oranges. What is for sure is that this mobo is the fastest 
mobo ever to come out of silicon valley for running linuxcnc, by a 
factor of at least 2/1 over the next best. I would have several more of 
them if Intel hadn't disco'd it about the time it was discovered by the 
linuxcnc people.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Broken kernel?

[deloptes]

John  ff wrote:

> All is OK with vmlinuz-3.2.0-4-amd64, but both 3.16.0-4-amd64 and
> 3.16.0-5-amd64 fail to load. When equipped with a screen I see it
> says Loading .. but it does not complete with no disk activity. The
> 3.2.0-4-amd64 kernel gives the same loading message followed shortly by
> saying the /dev/sda2 disk partition is clean and it continues to boot.
> Sorry I cannot remember the exact words after "Loading" but this m/c
> usually runs headless as my firewall and server.

I was forced to run 3.2 for quite a time, because newer did not boot. In my
case AMD cpu in headless server.
I found out that for some reason initramfs-tools did not
package /sbin/switch_root, so I unpacked initrd, copied switch_root
manually and packed again.
You can see more if you remove the "quite" option from the kernel command
line or use the recovery boot option.
If this wouldn't help I would pass init=/bin/sh and work out the boot
process manually to see where it fails.
At one point of time there was something with udev.

regards

Re: Broken kernel?

[deloptes]

Gene Heskett wrote:

> AMD64 would be like its built for an AMD phenom or newer. You want a
> kernel built for an intel cpu.

You are disappointing me, Gene. It is called amd64 because AMD first
released 64 arch cpu to the public. All intel 64 run with this kernel (and
packages).

Re: Broken kernel?

[Tom Furie]

On Sun, Mar 11, 2018 at 11:42:44PM -0400, Gene Heskett wrote:

> AMD64 would be like its built for an AMD phenom or newer. You want a 
> kernel built for an intel cpu.

AMD64, in the context of package naming, is for any 64-bit x86
compatible CPU.

Cheers,
Tom

-- 
A girl's best friend is her mutter.
-- Dorothy Parker


signature.asc
Description: Digital signature