Gráficos híbridos Intel/AMD

[Yasniel López Argüez]

Buenas noches colegas,

Tengo una laptop con gráficas híbridas Intel/AMD las reconoce ambas, 
pero todo me funciona a través de la Intel solamente no puedo cambiar a 
conveniencia como lo hace NVIDIA con Bumblebee. Fedora 25 tiene algo que 
se llama switheroo-control que permite hacerlo, pero en Debian no he 
visto nada parecido. Alguien tiene algun avance en dual GPU intel/amd 
con Debian?? Agradecería cualquier tipo de ayuda, gracias de antemano.



PD: Estoy  usando Debian Testing.


--
"It has been said something as small as the flutter
of a butterfly's wing can ultimately cause a typhoon
halfway around the world." - Chaos Theory -

Re: Fecha de última modificación de archivos

[Carlos Andrés Martín]

El 12/04/17 a las 21:45, TheFox escribió:
Sí, siempre y cuando ésos archivos no hayan sido borrados de forma 
segura antes del formateo.



Santiago.

El 13 abr. 2017 2:42, "Ricardo Frydman" > escribió:


Si


El 12 abr. 2017 21:40, "luis godoy" > escribió:

Una consulta, en una instalación nueva es posible encontrar
archivos con distintas fechas?  Por ejemplo de hace 6 meses
atras, y con disco duro formateado antes de la instacion.



Luis, supongo que tu pregunta apunta a archivos propios del sistema. En 
ese caso, la fecha de la imagen utilizada y la fecha de todos los 
archivos incluidos en ella son anteriores al formateo seguramente, 
porque el formateo lo has hecho recién para esta nueva instalación.

Saludos.
Carlos

Re: If Linux Is About Choice, Why Then ...

[Catherine Gramze]

> On Apr 12, 2017, at 9:05 PM, GiaThnYgeia  wrote:
> 
> The "choice" of going cheap on ancient hardware is that you all knowing
> expert "technical" but not "political" folk are really clueless of what
> those non-free eight-core gadgets you port your code on contain.  It
> would take years of testing and listening to identify where those
> machines leak from.  Geewhiz, most of you can not even swear you can
> tell what Ipv6 is all about, yet!   Do you have android anonymizing
> systems and packages?  Tell that to their engineers that have leaked
> that it is impossible to do so.  7billion people around earth have self
> imposed a gps chip and monitoring system in their pocket 24hrs a day.
> Even government and corporate servers are suspect of leaking stuff.  

The rumors of backdoors built into CPUs goes back to the early days of the 
Pentium chip, which predates the first Celeron by 5 years. Your argument is not 
valid, as it is just as possible for your Celeron chip to be compromised at the 
point of manufacture, usually in China, as it for a newer chip to be 
compromised.

Debian is not in the business of catering to the special needs of conspiracy 
theorists, but of looking to a technologically developing and progressing 
future and making it as accessible as possible to as many people as possible. 
The decisions the developers and project manager make are the best decisions 
they can make within the constraints of developer time and installer file size. 
If you truly need to use 18 year old hardware, get your hands on a copy of an 
old stable installer, say Potato, and use a version of Debian that is 
compatible with your hardware. Even auto manufacturers are only obligated to 
make parts for cars up to 10 years old.

Cathy

Re: If Linux Is About Choice, Why Then ...

[David Wright]

On Thu 13 Apr 2017 at 01:05:00 (+), GiaThnYgeia wrote:
[big snip]
> After all, to say "I am a technical guy not a political one" is a very
> politically loaded statement.  Dr Strangelove was a technical guy, not
> political at all.  It is those types you have to watch out for.

You've quoted my sentence out of context. I wrote:
"I'm not really interested in debating that here, sorry. I've seen
too many flame wars in public forums like this. And I'm a technical
guy, not a political one."

IOW I personally prefer to talk about political issues
elsewhere, face to face, and stick to technical issues here.
That has nothing to do with Dr Strangelove.

I've already written here that I find it difficult to follow your
arguments or decode sentences like
"Because what is discussed on this thread to me sounds as
 those who by majority have used the system (mostly for
 commercial large scale server applications) and are
 probably the number one source of bugs that feed development
 did not have much of a say on the direction taken."

So I have joined this conversation only to dispute certain
technical statements you made, and to ask why you make up
statistics to further your hypothetical arguments.

BTW I was surprised not to see mention of the Ken Thompson hack
in what I snipped.

Cheers,
David.

Re: If Linux Is About Choice, Why Then ...

[Joel Rees]

kAt, write a novel.

Sure, some of the people here still don't realize just how bad things
are, but there are limits to what individuals and even groups do.

My dad used to tell me, if I wanted to change things, I'd have to
change them from the inside. It's a poor expression of the principle
because you can't get "inside" far enough without X, Y, or Z, and they
all make it very difficult to change things once you are inside.

So write a novel.

That's what I'm doing. I don't know whether I'll convince very many
people, but it's helping my ability to express myself.

-- 
Joel Rees

I'm imagining I'm a novelist:
http://joel-rees-economics.blogspot.com/2017/01/soc500-00-00-toc.html
More of my delusions:
http://reiisi.blogspot.jp/p/novels-i-am-writing.html

Re: If Linux Is About Choice, Why Then ...

[GiaThnYgeia]

Maybe I started my explaining at the wrong end of the thread and I get
reactions on a personal level about what I am and whether I have the
right or reason to complaint.

So I'll start from scratch.

Let's say we have market players A B and C whose primary clients are
government agencies that have X-needs.  Then we have minute competitors
D E and F, and even more minute players who consult, write code to make
it all work, and abide by this market.  Due to their clientele ABC can
dump stuff on the market to keep DEF at the verge of destruction.  You
see if you know ahead of time that 30% of your production would be sold
at 200% profit, you can sell 70% at 0,01% profit.

Client-X has "needs" that must absolutely be met or there will be no
free lunch, as some 4x-billions spent on hardware that has a market
worth of x-billions.  To satisfy those needs A,B,C, have lots of
non-free work to do.  This work ends up everywhere on the non-free
market.  All a submissive puppet has to do is abide by the market rule.
"It is what puts bread on the table" and all submissive puppets bless
this bread.  Don't dare deny the blessings of the bread putter.

Now, let's say we need a complex hard to audit central "services"
controller to cover up (for some years at least) of all the dirty tricks
ABC have employed before some convicted felon running internationally
from the law blows some whistle and till that whistle is heard loud
enough to call this round of trickery off.  Then some virtuous
corporation comes out and says I blew that whistle, after the fact.

The "choice" of going cheap on ancient hardware is that you all knowing
expert "technical" but not "political" folk are really clueless of what
those non-free eight-core gadgets you port your code on contain.  It
would take years of testing and listening to identify where those
machines leak from.  Geewhiz, most of you can not even swear you can
tell what Ipv6 is all about, yet!   Do you have android anonymizing
systems and packages?  Tell that to their engineers that have leaked
that it is impossible to do so.  7billion people around earth have self
imposed a gps chip and monitoring system in their pocket 24hrs a day.
Even government and corporate servers are suspect of leaking stuff.  It
is a "heartbleeding" situation.

Now, is systemd a step on the right or the wrong direction in auditing
security?  What do security minded experts say and how did their project
leaders vote?  Don't listen to them, they are always paranoid, they like
morse radio code.

I arrest my case your honors, and I will take the rest of my science
fiction scenario elsewhere, but if I wanted lubuntu or gentoo or devuan
I would have been there long ago.  It just so happens that torproject,
tails, among other good projects are in bed with debian not antiX and
other systems.

After all, to say "I am a technical guy not a political one" is a very
politically loaded statement.  Dr Strangelove was a technical guy, not
political at all.  It is those types you have to watch out for.

kAt

-- 
 "The most violent element in society is ignorance" rEG

"Who died and made you the superuser?"  Brooklinux

Re: Fecha de última modificación de archivos

[TheFox]

Sí, siempre y cuando ésos archivos no hayan sido borrados de forma segura
antes del formateo.


Santiago.

El 13 abr. 2017 2:42, "Ricardo Frydman"  escribió:

Si


El 12 abr. 2017 21:40, "luis godoy"  escribió:

Una consulta, en una instalación nueva es posible encontrar archivos con
distintas fechas?  Por ejemplo de hace 6 meses atras, y con disco duro
formateado antes de la instacion.

Re: Fecha de última modificación de archivos

[Ricardo Frydman]

Si

El 12 abr. 2017 21:40, "luis godoy"  escribió:

Una consulta, en una instalación nueva es posible encontrar archivos con
distintas fechas?  Por ejemplo de hace 6 meses atras, y con disco duro
formateado antes de la instacion.

Fecha de última modificación de archivos

[luis godoy]

Una consulta, en una instalación nueva es posible encontrar archivos con
distintas fechas?  Por ejemplo de hace 6 meses atras, y con disco duro
formateado antes de la instacion.

Re: If Linux Is About Choice, Why Then ...

[Lisi Reisz]

On Wednesday 12 April 2017 23:42:00 GiaThnYgeia wrote:
>  Do I strike you
> like a person needing to hold hands with anyone?

Very much so.

Lisi

Re: If Linux Is About Choice, Why Then ...

[Nicholas Geovanis]

On Wed, Apr 12, 2017 at 6:17 PM, GiaThnYgeia 
wrote:
>
>
> Do you folk mean to tell me that at this point Debian does not have the
> power to influence industry by selecting to support only hardware with
> open/free firmware?


No, Debian does not have that power. There are no technical issues involved
in
that state of affairs, only economic issues.


> Isn't it superficial to say we are "for" free but
> we run hundreds of servers supplying "users" with non-free stuff?
>

IMO that is a valid complaint "about" Debian, but the complaint cannot
validly be laid at Debian's doorstep. It has everything to do with the point
you make later in your posting about the "tiny oligopoly" of hardware
manufacturers. You just haven't (yet) drawn all of the valid conclusions
from that valid observation.

Re: System broken after yesterday's upgrade

[Dejan Jocic]

On 13-04-17, Michael Lange wrote:
> On Wed, 12 Apr 2017 22:13:44 +0200
> solitone  wrote:
> 
> > On Wednesday, 12 April 2017 19:55:12 CEST Jochen Spieker wrote:
> > > I'd write a bug report. Your e-mail is a pretty good start.
> > 
> > To Debian BTS? Related to the kernel package? I have no clues as to
> > what component might be actually involved.
> > 
> > Thanks,
> >   Davide
> > 
> > 
> > 
> 
> I would try to install a different kernel (if possible with external
> keyboard) and boot into that one, if the problem disappears the culprit is
> most likely the kernel.
> 
He should have old kernel still installed, right? If that is the case,
he could simply boot with old kernel.

Re: If Linux Is About Choice, Why Then ...

[GiaThnYgeia]

Jonathan Dowland:
> On Wed, Apr 12, 2017 at 04:40:00PM +, GiaThnYgeia wrote:
>> As for the other post you commented on with the same attitude I would
>> have to say that getting technical in comparing sysv with competing
>> technologies does not answer the political part of the decision making.
>> It seems as this part is what irritated people not the technical aspects
>> of it.  Unless there are those that pretend the decision making process
>> was solely on technical merits.
> 
> The decision to switch the default init to systemd was made by the Tech
> Committee. You can read the history of that decision here
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727708
> 
> There's also a related General Resolution that was written, adapted and
> voted on by Debian members. The full details of that are here
> 
>   https://www.debian.org/vote/2014/vote_003
> 
> As for "who", 483 Debian Developers voted, as listed here
> 
>   https://www.debian.org/vote/2014/vote_003_voters.txt
> 
> All this stuff is in the open for anyone to read and catch up on. I
> hope you find it enlightening.

All I read is where the money goes that get donated "officially" to
debian.  Let me ask about the cost of servers/repositories for all the
non-free packages.  Whose decision goes there?
Do you folk mean to tell me that at this point Debian does not have the
power to influence industry by selecting to support only hardware with
open/free firmware?  Isn't it superficial to say we are "for" free but
we run hundreds of servers supplying "users" with non-free stuff?
What, the customer is a priority?  80% of users would have no support
running around with a portable device and some wifi that incorporates
chips from a tiny oligopoly?  Are we talking about meritocracy or
marketing?  It is a very different approach you know.

I suspect such decision making has a value!  We don't live in a free
world.  How many did you say?  483 developers, from how many contributors?

Ohh I am enlightened alright!
Show me the money honey, and save me the "constitution" preaching.


-- 
 "The most violent element in society is ignorance" rEG

"Who died and made you the superuser?"  Brooklinux

Re: If Linux Is About Choice, Why Then ...

[David Wright]

On Wed 12 Apr 2017 at 22:24:16 (+0200), Mart van de Wege wrote:
> David Wright  writes:
> 
> > On Mon 10 Apr 2017 at 21:21:00 (+), GiaThnYgeia wrote:
> >> For a second month under freeze not much
> >> development can take place in unstable, as it is really tomorrow's
> >> testing.
> >
> > What do you mean? Sid (unstable) is always sid. It doesn't suddenly
> > become buster (the next testing) when stretch is released.
> >
> To be fair, as someone running Sid and doing almost daily updates, it is
> noticeable when there is a testing freeze, as Sid comes to an almost
> complete standstill while developers concentrate on the freeze.

I think you're right. And then there may be an avalanche after release
day, something that tyros running sid should be aware of.

(But I was just pointing out in passing that packages don't get a
"free pass" from unstable to testing on release day. In fact,
of course, unstable's contents, and testing's too, do not change at all.)

Cheers,
David.

Re: If Linux Is About Choice, Why Then ...

[GiaThnYgeia]

Ric Moore:
> On 04/12/2017 12:40 PM, GiaThnYgeia wrote:
>> David Wright:
 Has Debian always been this crazy and am I so new to this madness?
>>>
>>> If you don't like it, you're free to look elsewhere for a distribution
>>> that better suits you.
>>
>> Are you mr.Debian?  Under what authority are you telling me to either
>> shut up or leave?  What makes you more Debian than me?  Why don't you
>> leave if you don't like criticism?
> 
> 
> Simple, you are admittedly new. Perhaps it would be prudent to survey
> the issues, study up some and then ask ~good~ detailed questions. Then
> act on the resolutions provided you or answer with more details when
> requested. 

I have been doing some research, I have also managed to break and
restore a few systems trying to run them without systemd.  Possibly a
harder task than I thought it might be.  Possibly unnecessarily complex,
I don't know.
But here is a good source of background on part of the issue.
http://blog.darknedgy.net/technology/2015/09/05/0/

> Linux has always been a "meritocracy". You earn your chops by
> being a productive member for a longish period of time, who consistently
> helps others with good solutions.

Save me the religious preaching, I am an atheist.  GWBjr, Trump,
Erdowan, and Putin were elected by slim majority of approved voters.
Stalin and Hitler ranked much higher in the meritocracy scale, nearly
unanimous decisions by their peers got them elected.  It must be that
Jimmy Hoffa was the only one that cheated to get elected.

> You have done none of that. You might
> be better served using Ubuntu. Debian is admittedly more tricky and not
> really suited to someone new. Ubuntu might serve your needs way better
> and their users are used to holding hands with a new fish. :) Ric

Why don't you try ubuntu and tell us what it is like.  Do I strike you
like a person needing to hold hands with anyone?


-- 
 "The most violent element in society is ignorance" rEG

"Who died and made you the superuser?"  Brooklinux

Re: System broken after yesterday's upgrade

[Michael Lange]

On Wed, 12 Apr 2017 22:13:44 +0200
solitone  wrote:

> On Wednesday, 12 April 2017 19:55:12 CEST Jochen Spieker wrote:
> > I'd write a bug report. Your e-mail is a pretty good start.
> 
> To Debian BTS? Related to the kernel package? I have no clues as to
> what component might be actually involved.
> 
> Thanks,
>   Davide
> 
> 
> 

I would try to install a different kernel (if possible with external
keyboard) and boot into that one, if the problem disappears the culprit is
most likely the kernel.

Regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

You say you are lying.  But if everything you say is a lie, then you are
telling the truth.  You cannot tell the truth because everything you say
is a lie.  You lie, you tell the truth ... but you cannot, for you lie.
-- Norman the android, "I, Mudd", stardate 4513.3

Re: If Linux Is About Choice, Why Then ...

[Lisi Reisz]

On Wednesday 12 April 2017 20:42:37 David Wright wrote:
> > If you like to contribute to my lack of understanding and possibly
> > unsubstantiated criticism, help me understand the hierarchy.  Who, and
> > how are they are selected, make the decisions and how do they relate to
> > those that do the work, and how do they all relate to those who for 2
> > decades have been employing the system and feedback with problems and
> > bugs.
>
> All this information is availble on the web, so I don't know why you
> want me to paraphrase it for you.

I had already looked these up for Kat, but accidentally sent them to her 
off-list.  (I must have pressed r not l)  Here they are again, Kat:  In fact, 
here is the whole of the post I sent off-list by mistake. 
 
On Wednesday 12 April 2017 17:40:00 GiaThnYgeia wrote:
> David Wright:
> >> Has Debian always been this crazy and am I so new to this madness?
> >
> > If you don't like it, you're free to look elsewhere for a distribution
> > that better suits you.
>
> Are you mr.Debian?  Under what authority are you telling me to either
> shut up or leave?  What makes you more Debian than me?

He is knowledgeable, helps on this list and has been using it for a long time.

> Why don't you 
> leave if you don't like criticism?
> If there is reason for madness, in which I accept I am new to, I will
> have to discover it.  Saying that simply madness is normal and whoever
> does not like it should leave doesn't justify madness.
> If you like to contribute to my lack of understanding and possibly
> unsubstantiated criticism, help me understand the hierarchy. 

https://en.wikipedia.org/wiki/List_of_Debian_project_leaders
https://www.debian.org/devel/constitution
https://en.wikipedia.org/wiki/Debian
https://en.wikipedia.org/wiki/Debian_Social_Contract
https://en.wikipedia.org/wiki/Debian_Free_Software_Guidelines

GIYF.  Do try to use the occasional accurate fact.

As David says, If you don't like Debian, use something else.  If you do like 
Debian, use it.  But do stop winging and blaming Debian for all your own 
mistakes.

> Who, and 
> how are they are selected, make the decisions and how do they relate to
> those that do the work, and how do they all relate to those who for 2
> decades have been employing the system and feedback with problems and bugs.

See above.  Why don't you EVER try to get some facts?  Just Google 
occasionally.

Lisi

Re: If Linux Is About Choice, Why Then ...

[Ric Moore]

On 04/12/2017 04:27 PM, Mart van de Wege wrote:


Here's a data point: having dealt with the vagaries and shortcomings of
SysV init professionally, I *like* systemd, even if it has a few warts.

Mart


I am going out on a limb here, but here goes, as I put on my "Amazing 
Kreskin predicts" hat.


The Amazing Kreskin PREDICTS!

1.) Pottering will adopt the word "tendrils" into his systemD schema. It 
has already been convicted of having tendrils, so now it will have them 
for real. Lennart will laugh and laugh.


2.) One he adopts tendrils, with the newer cpu's with many cores, a 
super desktop will be treated as a "cluster" with systemd administering 
processes between cpu and cuda cores in parallel in unison. Oh happy day.


3.) Then the "tendrils" snake out to the localnet of the average Jane 
and Joe Lunchbucket household, and all of the laptops, tablets and other 
desktops can share Network Attached Storage (NAS), spare cpu/cuda 
resources, and utilize every pretty new shiny piece of kit that Dad 
wants, to put the digital pedal to the digital metal. Fiber network and 
super wifi within the house, more memory for the cluster machine, 
upgrades of hardware for everyone! Kid comes home, the "tendrils" snatch 
into his wifi signal as he walks into the door, syncs it up and VAROOM!! 
He can flood the NAS, at very high speeds, with all of his junk. The 
tendrils snake into all of the Internet aware appliances and you become 
spammed by your refrigerator with shopping lists.


4.) Skynet becomes a real possibility. Tendrils everywhere.


If we're going to have a Skynet, it ought to be running Linux.

--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: If Linux Is About Choice, Why Then ...

[Jonathan Dowland]

On Wed, Apr 12, 2017 at 04:40:00PM +, GiaThnYgeia wrote:
> As for the other post you commented on with the same attitude I would
> have to say that getting technical in comparing sysv with competing
> technologies does not answer the political part of the decision making.
> It seems as this part is what irritated people not the technical aspects
> of it.  Unless there are those that pretend the decision making process
> was solely on technical merits.

The decision to switch the default init to systemd was made by the Tech
Committee. You can read the history of that decision here

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727708

There's also a related General Resolution that was written, adapted and
voted on by Debian members. The full details of that are here

https://www.debian.org/vote/2014/vote_003

As for "who", 483 Debian Developers voted, as listed here

https://www.debian.org/vote/2014/vote_003_voters.txt

All this stuff is in the open for anyone to read and catch up on. I
hope you find it enlightening.
 

-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC me, I am subscribed to the list.


signature.asc
Description: Digital signature

Re: If Linux Is About Choice, Why Then ...

[Jonathan Dowland]

On Wed, Apr 12, 2017 at 09:09:45AM -0700, Patrick Bartek wrote:
> Fedora is the development and test bed for RHEL much as Debian
> Testing is for Stable.

That's not a perfect analogy by any means: Fedora is used as a test bed for
technology that later ends up in RHEL, yes, but that's the end of it. One is a
commercial product, the other a community-driven, desktop-oriented
distribution. RHEL is not simply a rebranded, frozen Fedora release. They're
different distributions.

> But technically, you're correct: systemd was in Fedora before RHEL. Spliting
> hairs..

The best kind of correct, and not splitting hairs at all, since Fedora and
RHEL are not the same thing.

-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC me, I am subscribed to the list.


signature.asc
Description: Digital signature

Re: System broken after yesterday's upgrade

[Jochen Spieker]

solitone:
> On Wednesday, 12 April 2017 19:55:12 CEST Jochen Spieker wrote:
>> I'd write a bug report. Your e-mail is a pretty good start.
> 
> To Debian BTS? Related to the kernel package? I have no clues as to what 
> component might be actually involved.

I'd use reportbug againt the kernel package.

J.
-- 
I think of my genitals more often than my hands, but use them far less.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Re: Displaymanager resolutie

[Huub Reuver]

On Wed, Apr 12, 2017 at 10:13:35AM +0200, Paul van der Vlis wrote:
> Op 12-04-17 om 09:36 schreef Huub Reuver:
> > On Tue, Apr 11, 2017 at 03:54:24PM +0200, Paul van der Vlis wrote:
> >> Hoi allen,
> >>
> >> Ik wil de resolutie wijzigen van GDM3, of eventueel een andere
> >> displaymanager zoals LightDM. Maar dit lukt niet zo erg.
> >>
> >> Ik heb geprobeerd een regel met xrandr toe te voegen in
> >> /etc/gdm3/Init/Default, zoals in vele manuals staat.
> >> Maar het werkt niet.
> >>
> >> Ook zoiets werkt niet:
> >> cp /home/user/.config/monitors.xml /var/lib/gdm3/.config/monitors.xml
> >>
> >> Is er hier iemand die hier ervaring mee heeft?
> >>
> >> Dit gaat om Debian testing.
> > 
> > Ik gebruik zelf altijd een scriptje om direct met xrandr de resolutie
> > te wijzigen van een netbook.
> > 
> > Het script doet de volgende dingen:
> > - bekijk de huidige status (start xrandr en purge de resultaten).
> > - kijk welke aansluitingen er zijn
> > - als de externe monitor is aangesloten maar niet gebruikt zet
> >   deze dan met xrandr in een standaard resolutie
> > - zet de interne videokaart uit,
> > - schakel de externe videokaart in de resolutie van de monitor
> > 
> > De tussenregel van schakelen naar een standaard resolutie is om 
> > een vast uitgangspunt te hebben, dat verbetert de betrouwbaarheid 
> > van het script nogal.
> > 
> > Mijn script is "hardcoded" en wordt gestart met een toetsencombinatie.
> > Dit betekent dat ik geen input nodig heb. Gewoon monitor inpluggen
> > en de toetsencombinatie. En ja, xbindkeys of iets vergelijkbaars moet
> > zijn gestart bij het starten van X. En ik kan alleen enkele vaste 
> > configuraties "doortoggelen".
> > 
> > Ik gebruik dat script zelf als ik een externe monitor gebruik 
> > (laptopscherm uit, beeld extern of andersom).
> > En ja, omdat het hardcoded is werkt een vrij eenvoudig script.
> > Denk aan regels als:
> >   xrandr | grep HDMI-1 # dit gebruik ik om de gebruikte resolutie 
> ># te achterhalen voor IF-constructies.
> >   xrandr --output HDMI-1 --mode "1920x1080"
> >   xrandr --output HDMI-1 --off
> > Waarschijnlijk wil jij iets dat algemeen werkt(?).
> 
> Het liefst wel, maar dat blijkt lastig.
> 
> Wat betekend dat "--off" ?
> 
> Het gaat overigens om een HiDMI monitor, dat wordt niet juist herkend.
> Daarom is alles erg klein.
> 
> Ik heb het overigens al via een "script" geprobeerd. Dat wil zeggen, een
> script van 1 regel wat ik direct in het configfile heb gezet. Maar dit
> ging niet. Doe jij dit onder Debian, en zo ja met welke display manager?
> 
> > Wat niet werkt is een combinatie van de opensource NVidia drivers en
> > HDMI output, beperking van de drivers.
> 
> Het gaat bij mij niet om NVidia, maar om open source drivers (AMD).
> 
> > En het is mij opgevallen dat elke laptop en netbook weer andere labels
> > voor de display uitgang heeft (VGA1, VGA-1, HDMI1, HDMI-1, etc.).
> 
> Ja, iets wat voor alles geldt zou veel handiger zijn. Deze computer
> heeft 4 displayport aansluitingen, dus ik moet het 4x doen.

Ik denk dat je te moeilijk denkt voor het scriptje.

Met de output van xrandr:
~$ xrandr 
Screen 0: minimum 8 x 8, current 1680 x 1050, maximum 32767 x 32767
LVDS1 connected (normal left inverted right x axis y axis)
   1024x600  60.00 +  65.00  
   800x600   60.3256.25  
   640x480   59.94  
   512x300   60.00  
VGA1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 434mm x 
270mm
   1680x1050 59.88*+  59.95  
   1280x1024 75.0260.02  
..

Werkt het script:
#!/bin/sh
VGA=`xrandr|grep VGA1`
VGA_RES=`echo $VGA | sed -e "s/.*connected \(.*\)(normal.*/\1/"`
MAX_VGA=`xrandr | grep -A 1 VGA1 | tail -1 |colrm 1 3|colrm 10 80`

LVDS=`xrandr|grep LVDS1`
LVDS_RES=`echo $LVDS | sed -e "s/.*connected \(.*\)(normal.*/\1/"`
MAX_LVDS=`xrandr | grep -A 1 LVDS1 | tail -1 |colrm 1 3|colrm 10 80`

VGA_DIS=`echo $VGA | grep disconnected`


if [ "x$VGA_DIS" = "x"  ] ; then 

   if [ "x$LVDS_RES" = "x"  ] ; then 
  xrandr --output VGA1 --mode 800x600
  xrandr --output LVDS1 --mode 800x600
  xrandr --output LVDS1 --auto 
  xrandr --output VGA1 --off
  xrandr --output LVDS1 --mode 1024x600
   else
  xrandr --output VGA1 --mode 800x600
  xrandr --output LVDS1 --mode 800x600
  xrandr --output LVDS1 --off
  xrandr --output VGA1 --auto
  xrandr --output VGA1 --mode $MAX_VGA
   fi

else
 
   xrandr --output VGA1 --mode 800x600
   xrandr --output LVDS1 --mode 800x600
   xrandr --output LVDS1 --auto 
   xrandr --output VGA1 --off
   xrandr --output LVDS1 --mode 1024x600
   MAX_VGA="disconnected"

fi

echo -n "Max LVDS: "
echo -n $MAX_LVDS
echo -n " ("
echo -n $LVDS_RES
echo -n ") Max VGA: "
echo -n $MAX_VGA
echo -n " ("
echo -n $VGA_RES
echo")"

En dat werkt met xdm. Eerst inloggen en dan met een shortkey (bijv. 
xbindkeys) roep je het script aan en je loopt gewoon de 
mogelijkheden af.

Het script "kijkt" welke screen actief is, schakelt de andere aan

Re: If Linux Is About Choice, Why Then ...

[Ric Moore]

On 04/12/2017 12:40 PM, GiaThnYgeia wrote:

David Wright:

Has Debian always been this crazy and am I so new to this madness?


If you don't like it, you're free to look elsewhere for a distribution
that better suits you.


Are you mr.Debian?  Under what authority are you telling me to either
shut up or leave?  What makes you more Debian than me?  Why don't you
leave if you don't like criticism?



Simple, you are admittedly new. Perhaps it would be prudent to survey 
the issues, study up some and then ask ~good~ detailed questions. Then 
act on the resolutions provided you or answer with more details when 
requested. Linux has always been a "meritocracy". You earn your chops by 
being a productive member for a longish period of time, who consistently 
helps others with good solutions. You have done none of that. You might 
be better served using Ubuntu. Debian is admittedly more tricky and not 
really suited to someone new. Ubuntu might serve your needs way better 
and their users are used to holding hands with a new fish. :) Ric



--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: If Linux Is About Choice, Why Then ...

[Mart van de Wege]

GiaThnYgeia  writes:

> Am I wrong?

You have at least nothing but opinion supporting the assertion that you
are right. So the jury is out on that one.

> I don't hear newbies single machine users having much of an issue with
> systemd, but people whose work for many years was based in fine-tuning
> other init systems seem to be having issues in adopting to this new
> status-quo whether they like it or not.

Here's a data point: having dealt with the vagaries and shortcomings of
SysV init professionally, I *like* systemd, even if it has a few warts.

Mart

-- 
"We will need a longer wall when the revolution comes."
--- AJS, quoting an uncertain source.

Re: If Linux Is About Choice, Why Then ...

[Mart van de Wege]

David Wright  writes:

> On Mon 10 Apr 2017 at 21:21:00 (+), GiaThnYgeia wrote:
>> For a second month under freeze not much
>> development can take place in unstable, as it is really tomorrow's
>> testing.
>
> What do you mean? Sid (unstable) is always sid. It doesn't suddenly
> become buster (the next testing) when stretch is released.
>
To be fair, as someone running Sid and doing almost daily updates, it is
noticeable when there is a testing freeze, as Sid comes to an almost
complete standstill while developers concentrate on the freeze.

Mart

-- 
"We will need a longer wall when the revolution comes."
--- AJS, quoting an uncertain source.

Re: System broken after yesterday's upgrade

[Mart van de Wege]

solitone  writes:

> On Wednesday, 12 April 2017 19:55:12 CEST Jochen Spieker wrote:
>> I'd write a bug report. Your e-mail is a pretty good start.
>
> To Debian BTS? Related to the kernel package? I have no clues as to what 
> component might be actually involved.
>
It's USB-related, so I'd say either the kernel package or udev.

Mart

-- 
"We will need a longer wall when the revolution comes."
--- AJS, quoting an uncertain source.

Re: System broken after yesterday's upgrade

[solitone]

On Wednesday, 12 April 2017 19:55:12 CEST Jochen Spieker wrote:
> I'd write a bug report. Your e-mail is a pretty good start.

To Debian BTS? Related to the kernel package? I have no clues as to what 
component might be actually involved.

Thanks,
  Davide

Re: If Linux Is About Choice, Why Then ...

[David Wright]

On Wed 12 Apr 2017 at 16:40:00 (+), GiaThnYgeia wrote:
> David Wright:
> >> Has Debian always been this crazy and am I so new to this madness?
> > 
> > If you don't like it, you're free to look elsewhere for a distribution
> > that better suits you.
> 
> Are you mr.Debian?  Under what authority are you telling me to either
> shut up or leave?

I've disagreed with your interpretation of the well known statistical
paradox (for want of a better word) that occurs before each Debian
release (look at the historical graphs, and google for the reasons),
corrected a couple of errors, and made a common sense suggestion to
someone who says that Debian is crazy. Where's the "shut up or leave"?

> What makes you more Debian than me?  Why don't you
> leave if you don't like criticism?

I don't mind criticism at all. I found the exchanges between the likes
of Nicolas, tomás, Joel etc most interesting. But I didn't see any
criticism in your (snipped) post; just misunderstood statistics etc,
which is why I commented on that one, and the other one like it.

> If there is reason for madness, in which I accept I am new to, I will
> have to discover it.  Saying that simply madness is normal and whoever
> does not like it should leave doesn't justify madness.

I don't accept your description of Debian as crazy madness, but I
accept it as your opinion, hence my suggestion. This is the only bit
of my post you've quoted, which suggests that you just want to rant
rather than understand the processes by which the Debian project
operates.

> If you like to contribute to my lack of understanding and possibly
> unsubstantiated criticism, help me understand the hierarchy.  Who, and
> how are they are selected, make the decisions and how do they relate to
> those that do the work, and how do they all relate to those who for 2
> decades have been employing the system and feedback with problems and bugs.

All this information is availble on the web, so I don't know why you
want me to paraphrase it for you.

> Because what is discussed on this thread to me sounds as those who by
> majority have used the system (mostly for commercial large scale server
> applications) and are probably the number one source of bugs that feed
> development did not have much of a say on the direction taken.  The
> direction was dictated from above and developers went to work according
> to that direction.
> Am I wrong?  I don't hear newbies single machine users having much of an
> issue with systemd, but people whose work for many years was based in
> fine-tuning other init systems seem to be having issues in adopting to
> this new status-quo whether they like it or not.

You keep making these assertions without any references, but I'm not
going to debate them with you. You can see what I'm interested in from
my previous posts. They're all in the public archive.

You can also see that someone else posted statistics (about numbers of
developers rather than RC bugs) in this thread to accompany their
rhetoric, and I asked them what they thought the statistics showed,
but no reply was forthcoming.

> As for the other post you commented on with the same attitude I would
> have to say that getting technical in comparing sysv with competing
> technologies does not answer the political part of the decision making.

I had a similar attitude to your made-up statistics there (you
actually said you had no data to prove them) as I did to the
misunderstood statistics here. I'm not interested in debating the
politics, as you can see from the rest of my posts.

> It seems as this part is what irritated people not the technical aspects
> of it.  Unless there are those that pretend the decision making process
> was solely on technical merits.
> That's where the definition of "free" comes in, which you seem to be
> having a hard time understanding.

I don't understand what you mean by "free" getting hazier, just as I
didn't understand "free" in your other thread:

| I'll stick to the "people who want ancient hardware" and ask whether you
| perceive those people as having a choice to "want ancient" hardware or
| whether this is "all" they have.  Do you anticipate those same people to
| be able to start their computing career in developing systems?
| Which relates to that world do we want Debian to prevail.  The "free"
| world or the "non-free" world in which we live in?

This last was taken from a thread in which you expressed a desire to
prevent people being able to upgrade Debian on certain hardware
("block and prohibit someone like me", "refuses the upgrade"). That's
why I don't understand _your_ use of "free" there.

> I'd say go back and read the policy
> and principles of Debian.  The realities of industry and market is not
> part of what I understand as free, on the contrary I find them
> contradictory.

I'm not really interested in debating that here, sorry. I've seen
too many flame wars in public forums like this. And I'm a technical
guy, not a political one.

Re: Possibly erroneous "device not present" message during boot

[songbird]

Richard Owlett wrote:
...

  ran across http://forums.debian.net/viewtopic.php?f=17=128777
not sure if will help or not, but does point to what i
was thinking (bios, uefi, partition issue or module not
being loaded by grub).

...
> Any suggested reading on the "BASH like shell" I just used?
> My initial DuckDuckGo search was *NOT* encouraging ;/
> If retirement is not for learning, what use is it?

  a simple thing like a "help" or "?" command working 
would be great huh?  :)  i ended up at the grub website
trying to figure things out.

  i think hitting tab key once or twice may give full 
list of commands available.  i don't want to reboot right
now to find out...


  songbird

Re: Possibly erroneous "device not present" message during boot

[Brian]

On Wed 12 Apr 2017 at 13:33:02 -0500, Richard Owlett wrote:

> On theory "too much better than too little" I see:
> 
> ### BEGIN /etc/grub.d/20_linux_xen ###
> 
> ### END /etc/grub.d/20_linux_xen ###
> 
> ### BEGIN /etc/grub.d/30_os-prober ###
> menuentry 'Debian GNU/Linux (8.6) (on /dev/mmcblk0p1)' --class gnu-linux
> --class gnu --class os $menuentry_id_option
> 'osprober-gnulinux-simple-380e2a6d-f851-4fd1-9db2-869a0982b511' {
>   insmod part_msdos
>   insmod ext2
>   if [ x$feature_platform_search_hint = xy ]; then
> search --no-floppy --fs-uuid --set=root
> 380e2a6d-f851-4fd1-9db2-869a0982b511
>   else
> search --no-floppy --fs-uuid --set=root
> 380e2a6d-f851-4fd1-9db2-869a0982b511
>   fi
>   linux /boot/vmlinuz-3.16.0-4-686-pae root=/dev/mmcblk0p1
>   initrd /boot/initrd.img-3.16.0-4-686-pae
> }
> 

GRUB is content to boot whatever is on the SD (as you observe) so must
be happy enough with the stanza above; there is no problem with booting
there. Actually, GRUB only uses

 linux /boot/vmlinuz-3.16.0-4-686-pae root=/dev/mmcblk0p1

and

 initrd /boot/initrd.img-3.16.0-4-686-pae

to get everything up and running. Without those two lines you would not
be booting.

So try this:
When the GRUB menu displays press the "e" key and remove the

  search --no-floppy --fs-uuid --set=root 380e2a6d-f851-4fd1-9db2-869a0982b511

Then press the "F10" key. Can you still boot? Do you get the onscreen
message you are concerned about?

Re: Soporte debian

[tomas gonzalez]

Saludos! prueba con un live cd de debian reinstalar Grub
https://simplementelibre.wordpress.com/2014/10/23/recuperar-grub-con-un-livecd-de-ubuntu-14-04-tras-la-instalacion-de-windows/

El 12 de abril de 2017, 15:30, Jose Amador Salas 
escribió:

> Una pregunta,  hay alguna manera de recuperar el entorno grafico de Debian
> jessie, es que despues del Grub se me queda la pantalla en negro y no puedo
> acceder al inicio de sesión, he intentado desde la consola(CTRL Alt F2)
> hacer alguna opciones que he visto en la web pero ninguna me ha servido, me
> pueden ayudar?
> -- Mensaje reenviado --
> De: "Jose Amador Salas" 
> Fecha: 12 abr. 2017 12:25 PM
> Asunto: Soporte debian
> Para: 
> Cc:
>
> Una pregunta,  hay alguna manera de recuperar el entorno grafico de Debian
> jessie, es que despues del Grub se me queda la pantalla en negro y no puedo
> acceder al inicio de sesión, he intentado desde la consola(CTRL Alt F2)
> hacer alguna opciones que he visto en la web pero ninguna me ha servido, me
> pueden ayudar?
>

Re: Possibly erroneous "device not present" message during boot

[Pascal Hambourg]

Le 12/04/2017 à 20:33, Richard Owlett a écrit :

On 04/12/2017 12:13 PM, Pascal Hambourg wrote:


- report the menu entry code for the SD card system in
/boot/grub/grub.cfg (the one from the system on the hard drive owning
GRUB, not the one on the SD card) ;


On theory "too much better than too little" I see:

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Debian GNU/Linux (8.6) (on /dev/mmcblk0p1)' --class gnu-linux
--class gnu --class os $menuentry_id_option
'osprober-gnulinux-simple-380e2a6d-f851-4fd1-9db2-869a0982b511' {
insmod part_msdos
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root
380e2a6d-f851-4fd1-9db2-869a0982b511
else
  search --no-floppy --fs-uuid --set=root
380e2a6d-f851-4fd1-9db2-869a0982b511
fi
linux /boot/vmlinuz-3.16.0-4-686-pae root=/dev/mmcblk0p1
initrd /boot/initrd.img-3.16.0-4-686-pae
}



- while the SD card is inserted, in the GRUB menu press "c" to enter a
GRUB shell and report the result of the "ls" command.


(hd0) (hd0, msdos9) (hd0, msdos8) (hd0, msdos7) (hd0, msdos6)
(hd0, msdos5) (hd0, msdos1) (hd1) (hd1, msdos1)


Some BIOS expose a removable media only when booting from it, so my 
theory was that your BIOS did not expose the SD card and GRUB could not 
see it. The result of ls proves me wrong.


Can you also report the output of "ls (hd1,msdos1)" to check what GRUB 
sees of the partition on the card ?



Any suggested reading on the "BASH like shell" I just used?


The GRUB manual at  
describes some of the commands, but not all. The shell can display the 
command list with "help" and information about a specific command with 
"help ".

Re: Problem after dist-upgrade and dpkg install -f (Probably nvidia packages related)

[Hans]

No, no, it is never too late. If you trust me, I may login to your computer. 
To do this, I need your IP snd root password, of course. 

You can also use teamviewer, however, my bandwith is really low, so ssh would 
be better.

You can send me direct to my e-mail address, if you would like to.

Best

Hans

 

Re: Problem after dist-upgrade and dpkg install -f (Probably nvidia packages related)

[Aquarius]

Hans,
Don't be sorry (yet). I need some time to figure out some steps.
Making a backup now. After that I will re-read your answers and try to try them 
all.
If you or someone would want to do schedule a remote login let me know. As I am 
doing a Linux course now I would really like to learn from this and what others 
would do on my system when the would perform a remote login.
If anyone needs more info try and tell me how to get it out of my system.
I was wondering for instance whether some sort of roll back is possible after 
performing a (dist-)upgrade. Maybe it is too late now ...

Kind regards,
Aquarius


--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com

12. Apr 2017 20:45 by hans.ullr...@loop.de:


> Am Mittwoch, 12. April 2017, 20:32:30 CEST schrieb Aquarius:
> Hmm, your package can definetely not installed. Is it possible to remove the 
> packages one-by-one?
>
> If you are able, to remove the nvidia packages, you can download the Nvidia-
> driver from the nvidia web site. It is a file named similar NVidia-blabla.run.
>
> You have to make it executable and start it as root like 
>
> ./NVidia.blabla.run
>
> Maybe this is working for you. If this is working, you know, it is working at 
> all. This file can easily deinstalled with ./NVidia-blabla.run --uninstall.
>
> It is difficult from this side to see what is happening. It is easier, when 
> having direct access to a system, so one can see more, what is happening.
>
> Maybe someone else has also some tips ( I hope)
>
> Sorry, that my hints did not really help.
>
> Hans
>> Meanwhile I tried dpkg --configure libgl1-nvidia-glx:amd64
>> Output:
>> Setting up libgl1-nvidia-glx:amd64 (340.101-1) ...
>> Killed
>> dpkg: error processing package libgl1-nvidia-glx:amd64 (--configure):
>>  subprocess installed post-installation script returned error exit status
>> 137 Errors were encountered while processing:
>>  libgl1-nvidia-glx:amd64
>>
>> What you described below is a bit of too 'over the top' for me.
>> Don't know exactly what to do by what you describe but will try to find out.
>> Maybe I will better first do a backup of data.
>>
>> Thanks again,
>> Aquarius
>>

Re: Possibly erroneous "device not present" message during boot

[songbird]

Pascal Hambourg wrote:
> Le 12/04/2017 à 17:14, Richard Owlett a écrit :
>>
>> Whether initiated after power-on OR a restart the observed sequence is:
>> 1. Appearance of the Grub2 menu with a choice of 4 instances of Debian.
>> 2. Select instance installed on the SD card.
>> 3. Screen clears, this message appears against the Debian 8 background.
>>error:  no such device: 380e2a6d-f851-4fd1-9db2-869a0982b511.
>>Press any key to continue ...
>> 4. Otherwise the instance of Debian on the SD card boots routinely.
>
> This is a GRUB error message which cannot find the UUID specified in a 
> "search" command.
>
> In order to investigate, can you
> - report the menu entry code for the SD card system in 
> /boot/grub/grub.cfg (the one from the system on the hard drive owning 
> GRUB, not the one on the SD card) ;

  yep!


> - while the SD card is inserted, in the GRUB menu press "c" to enter a 
> GRUB shell and report the result of the "ls" command.

  also, check that the mount points exist for
the file system.

  you may think you've installed things to one
location only to later find you've actually
put them someplace else...

  another thing you can do is construct your own
menu entry and put it in /etc/grub.d/40_custom file

here is an example from when i was playing around
last week (you may need to insmod something else(s)
to get the efi, ssd, ext4, whatever partition table 
type you use, etc. going):  [and only use the lines from 
between the ='s]  adjust as needed/desired.  :)

oh and of course, check your partition tables on the
devices to make sure they're actually what you expect.

==
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.

menuentry "Count to three before launching..." {

echo "1..."
sleep 1
echo "2..."
sleep 1
echo "3..."
sleep 1

set linux_gfx_mode=
export linux_gfx_mode
load_video
insmod gzio
insmod part_msdos
insmod ext2
insmod usb
insmod fat

set root='hd0,msdos1'

echo'Loading Linux 4.9.0-1-686-pae ...'
linux   /boot/vmlinuz-4.9.0-1-686-pae ro root=LABEL=ROOT_007 
echo'Loading initial ramdisk ...'
initrd  /boot/initrd.img-4.9.0-1-686-pae
}
==

  and then run update-grub to get your new menu.


  songbird

Soporte debian

[Jose Amador Salas]

Una pregunta,  hay alguna manera de recuperar el entorno grafico de Debian
jessie, es que despues del Grub se me queda la pantalla en negro y no puedo
acceder al inicio de sesión, he intentado desde la consola(CTRL Alt F2)
hacer alguna opciones que he visto en la web pero ninguna me ha servido, me
pueden ayudar?
-- Mensaje reenviado --
De: "Jose Amador Salas" 
Fecha: 12 abr. 2017 12:25 PM
Asunto: Soporte debian
Para: 
Cc:

Una pregunta,  hay alguna manera de recuperar el entorno grafico de Debian
jessie, es que despues del Grub se me queda la pantalla en negro y no puedo
acceder al inicio de sesión, he intentado desde la consola(CTRL Alt F2)
hacer alguna opciones que he visto en la web pero ninguna me ha servido, me
pueden ayudar?

Re: Problem after dist-upgrade and dpkg install -f (Probably nvidia packages related)

[Hans]

Am Mittwoch, 12. April 2017, 20:32:30 CEST schrieb Aquarius:
Hmm, your package can definetely not installed. Is it possible to remove the 
packages one-by-one?

If you are able, to remove the nvidia packages, you can download the Nvidia-
driver from the nvidia web site. It is a file named similar NVidia-blabla.run.

You have to make it executable and start it as root like 

./NVidia.blabla.run

Maybe this is working for you. If this is working, you know, it is working at 
all. This file can easily deinstalled with ./NVidia-blabla.run --uninstall.

It is difficult from this side to see what is happening. It is easier, when 
having direct access to a system, so one can see more, what is happening.

Maybe someone else has also some tips ( I hope)

Sorry, that my hints did not really help.

Hans
> Meanwhile I tried dpkg --configure libgl1-nvidia-glx:amd64
> Output:
> Setting up libgl1-nvidia-glx:amd64 (340.101-1) ...
> Killed
> dpkg: error processing package libgl1-nvidia-glx:amd64 (--configure):
>  subprocess installed post-installation script returned error exit status
> 137 Errors were encountered while processing:
>  libgl1-nvidia-glx:amd64
> 
> What you described below is a bit of too 'over the top' for me.
> Don't know exactly what to do by what you describe but will try to find out.
> Maybe I will better first do a backup of data.
> 
> Thanks again,
> Aquarius
> 

Re: Possibly erroneous "device not present" message during boot

[Richard Owlett]

On 04/12/2017 12:13 PM, Pascal Hambourg wrote:

Le 12/04/2017 à 17:14, Richard Owlett a écrit :


Whether initiated after power-on OR a restart the observed sequence is:
1. Appearance of the Grub2 menu with a choice of 4 instances of Debian.
2. Select instance installed on the SD card.
3. Screen clears, this message appears against the Debian 8 background.
   error:  no such device: 380e2a6d-f851-4fd1-9db2-869a0982b511.
   Press any key to continue ...
4. Otherwise the instance of Debian on the SD card boots routinely.


This is a GRUB error message which cannot find the UUID specified in a
"search" command.

In order to investigate, can you
- report the menu entry code for the SD card system in
/boot/grub/grub.cfg (the one from the system on the hard drive owning
GRUB, not the one on the SD card) ;


On theory "too much better than too little" I see:

### BEGIN /etc/grub.d/20_linux_xen ###

### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Debian GNU/Linux (8.6) (on /dev/mmcblk0p1)' --class gnu-linux 
--class gnu --class os $menuentry_id_option 
'osprober-gnulinux-simple-380e2a6d-f851-4fd1-9db2-869a0982b511' {

insmod part_msdos
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root 
380e2a6d-f851-4fd1-9db2-869a0982b511

else
	  search --no-floppy --fs-uuid --set=root 
380e2a6d-f851-4fd1-9db2-869a0982b511

fi
linux /boot/vmlinuz-3.16.0-4-686-pae root=/dev/mmcblk0p1
initrd /boot/initrd.img-3.16.0-4-686-pae
}





- while the SD card is inserted, in the GRUB menu press "c" to enter a
GRUB shell and report the result of the "ls" command.


Did not see any way to capture the output. So made manual copy. The 
following appeared on a single line.


(hd0) (hd0, msdos9) (hd0, msdos8) (hd0, msdos7) (hd0, msdos6)
(hd0, msdos5) (hd0, msdos1) (hd1) (hd1, msdos1)

Any suggested reading on the "BASH like shell" I just used?
My initial DuckDuckGo search was *NOT* encouraging ;/
If retirement is not for learning, what use is it?

Thank you.

Re: Problem after dist-upgrade and dpkg install -f (Probably nvidia packages related)

[Aquarius]

Meanwhile I tried dpkg --configure libgl1-nvidia-glx:amd64
Output:
Setting up libgl1-nvidia-glx:amd64 (340.101-1) ...
Killed
dpkg: error processing package libgl1-nvidia-glx:amd64 (--configure):
 subprocess installed post-installation script returned error exit status 137
Errors were encountered while processing:
 libgl1-nvidia-glx:amd64

What you described below is a bit of too 'over the top' for me. 
Don't know exactly what to do by what you describe but will try to find out.
Maybe I will better first do a backup of data.

Thanks again,
Aquarius

--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com

12. Apr 2017 20:26 by hans.ullr...@loop.de:


> Am Mittwoch, 12. April 2017, 20:18:22 CEST schrieb Aquarius:
> Hmm, bad thing. Maybe you should remove kdm, gdm or whatever loginmanager you 
> are using out of the way, so it will not start after boot and force you into 
> a 
> bad X.
>
> Then you can try dpkg-configure -a again.
>
> You can also try to delete nvidia.ko in the kernel libs, so it inhibits to 
> start nvidia-driver.
>
> Try then dpkg-reconfigure -a again. Maybe it is working now.
>
> You might try to deinstall the downloaded package with 
> dpkg -r nvidia-blabla.deb
>
> If this all fails, trigger me again, maybe I have some other ideas.
>
> Good luck!
>
> Hans
>> Thanks Hans.
>> I must add when shutting down I get a black screen with lots of text. The
>> system will not shut down. I have to press the powerbutton and hold it to
>> power it off. After starting up again I performed  apt-get --purge remove
>> nvidia-*
>>
>> The output was:
>> root@debian:/home/piet# apt-get --purge remove nvidia-*
>> E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to
>> correct the problem.
>>
>> Well, it seems I would be running in circles then.
>> Any other idea?
>>
>> Kind regards,
>> Aquarius
>>

Re: Problem after dist-upgrade and dpkg install -f (Probably nvidia packages related)

[Hans]

Am Mittwoch, 12. April 2017, 20:18:22 CEST schrieb Aquarius:
Hmm, bad thing. Maybe you should remove kdm, gdm or whatever loginmanager you 
are using out of the way, so it will not start after boot and force you into a 
bad X.

Then you can try dpkg-configure -a again.

You can also try to delete nvidia.ko in the kernel libs, so it inhibits to 
start nvidia-driver.

Try then dpkg-reconfigure -a again. Maybe it is working now.

You might try to deinstall the downloaded package with 
dpkg -r nvidia-blabla.deb

If this all fails, trigger me again, maybe I have some other ideas.

Good luck!

Hans
> Thanks Hans.
> I must add when shutting down I get a black screen with lots of text. The
> system will not shut down. I have to press the powerbutton and hold it to
> power it off. After starting up again I performed  apt-get --purge remove
> nvidia-*
> 

> The output was:
> root@debian:/home/piet# apt-get --purge remove nvidia-*
> E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to
> correct the problem.
> 
> Well, it seems I would be running in circles then.
> Any other idea?
> 
> Kind regards,
> Aquarius
>

Re: Problem after dist-upgrade and dpkg install -f (Probably nvidia packages related)

[Aquarius]

Thanks Hans. 
I must add when shutting down I get a black screen with lots of text. The 
system will not shut down. I have to press the powerbutton and hold it to power 
it off.
After starting up again I performed  apt-get --purge remove nvidia-*

The output was:
root@debian:/home/piet# apt-get --purge remove nvidia-*
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct 
the problem. 

Well, it seems I would be running in circles then.
Any other idea?

Kind regards,
Aquarius
--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com

12. Apr 2017 19:47 by hans.ullr...@loop.de:


> Hi Aquarius,
> looks like you got into trouble with nvidia-driver.
>
> You should uninstall these, then doing a dist-upgrade and then conetrate to 
> install the nvidia-driver again.
>
> I prefer two possible ways to uninstall all nvidia-packages (but check before 
> telling "y"):
>
> apt-get --purge remove nvidia-*
>
> or
>
> aptitude purge ~nnvidia-*
>
> Both should work. But as I said, look, what is going to deinstalled, before 
> telling YES. In most cases these commands are working well.
>
> When they are all deinstalled, reinstall the required package. Note: You must 
> have a graphics card with Geforce 9 or higher! Otherwise the package will not 
> be installed. Check your hardware if it is supported by the package.
>
> Note, you must have kernel-headers installed.
>
> Good luck!
>
> Hans
>
>
>
>> In the messages I got from that were:
>>
>>  libgl1-nvidia-glx:amd64-->not configured
>>  nvidia-driver-->not configured
>>  xserver-xorg-video-nvidia-->dependency problems - leaving unconfigured
>>  nvidia-glx-->dependency problems - leaving unconfigured
>>

Re: Copying file has unexpected side effect

[David Wright]

On Mon 10 Apr 2017 at 06:41:15 (-0500), Richard Owlett wrote:
> On 04/09/2017 02:40 PM, Steve McIntyre wrote:
> >rowl...@cloud85.net wrote:
> >>On 04/09/2017 10:47 AM, Richard Owlett wrote:
> 
> Re-inserting _*CRITICAL_ critical information from 1st post
> 
> I have a laptop with multiple installs of Debian Jessie using MATE
> desktop. There are minor differences of package complements - the
> purpose being to determine an optimal configuration.
> 
> There are a relatively small number of files which I would like to
> have the latest version available no matter which install is active.
> 

The trouble is that that sounds like a repository of files that
could be readonly, whereas what later transpired is that you just
want a shared scratch area.

> >>>My solution was to place this files on a separate partition of the >>> 
> >>>hdd. It will be mounted at boot. The fstab entry is currently
> >>>UUID=E90C-65B4  /media/common vfat auto,exec,rw,flush,umask=000  0 0
> >>>
> >>>The problem occurred on the very first use:
> >>>I opened /media/common by double-clicking its desktop icon.
> >>>I then:
> >>>  right-clicked on the desktop icon of a text file
> >>>  selected "Copy" from the menu
> >>>  moved mouse over the displayed directory of /media/common
> >>>  right-clicked and chose "Paste" from menu
> >>>
> >>>The file was _apparently_ copied as expected.
> >>>*HOWEVER* the act of copying set the execution flag.
> >>>Why?

Because of the mask. But you don't say why this execute bit
is a problem, so is it, or could you just leave it?

> >>I received an almost OFFLIST reply stating:
> >>"Because your fstab entry contains the exec directive for the whole
> >>filesystem"
> >>
> >>I suspected something of the sort. The man pages and wiki references
> >>were opaque on how to chose the various mask options.

You're confusing two things. The exec mount option (redundant because
it's the default, though you might want to think of setting noexec
if you don't want these scratch files to be executed) has nothing
to do with the execute bits set by the mask. See   man mount.

> >>What I had expected to happen was for execute flag to be whatever it >> had 
> >>been set to on the source side.
> >>I wanted all users to have rw permission - that was apparently
> >>accomplished.
> >
> >The bits are rwxrwxrwx. Setting them all maps to (octal) 777. The
> >umask determines which bits you *don't* want to see set from mount, so
> >umask=111 will strip the execute bits.
> 
> That did not work as desired. The files on that partition can *NOT*
> be deleted.

That won't be the only effect you'll observe when you strip the
execute bits from the directories as well as the files; they become
almost unusable. You need to set fmask and dmask separately, rather
than using umask, so that you can keep the execute bits on directories.

> The *EXPLICIT* purpose is for *EVERYONE* to absolutely free
> unfettered access to the files on that partition.
> Think of it as a message board in the local grocery where anyone
> could post anything. Advertising flyers with tear off phone numbers
> included.

Of course, I have to add here that I don't understand why users
other than 0 and 1000 need write access when you're carrying out
your experiments on installation. I thought this isolated machine
only had you as a user.

> >Alternatively, use a real filesystem that supports permissions
> >better (i.e. at all). vfat is horrid in many, many ways.
> >
> 
> This machine doesn't have Windows on it. But I'll want to do the
> same thing on one with both Linux and Windows.
> 
> Ideas?

Developing a more secure methodology would be transferrable to other,
connected machines and so provide a richer learning experience.

Cheers,
David.

Re: System broken after yesterday's upgrade

[Jochen Spieker]

solitone:
>
> Hi, something really weird is going on today on my system--debian stretch on 
> an Apple MacBookPro 12,1.

If googling doesn't turn up something helpful (and maybe even then) I'd
write a bug report. Your e-mail is a pretty good start.

Regards,
Jochen.
-- 
If politics is the blind leading the blind, entertainment is the fucked-
up leading the hypnotised.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Re: Problem after dist-upgrade and dpkg install -f (Probably nvidia packages related)

[Hans]

Hi Aquarius,
looks like you got into trouble with nvidia-driver.

You should uninstall these, then doing a dist-upgrade and then conetrate to 
install the nvidia-driver again.

I prefer two possible ways to uninstall all nvidia-packages (but check before 
telling "y"):

apt-get --purge remove nvidia-*

or

aptitude purge ~nnvidia-*

Both should work. But as I said, look, what is going to deinstalled, before 
telling YES. In most cases these commands are working well.

When they are all deinstalled, reinstall the required package. Note: You must 
have a graphics card with Geforce 9 or higher! Otherwise the package will not 
be installed. Check your hardware if it is supported by the package.

Note, you must have kernel-headers installed.

Good luck!

Hans



> In the messages I got from that were:
> 
>  libgl1-nvidia-glx:amd64-->not configured
>  nvidia-driver-->not configured
>  xserver-xorg-video-nvidia-->dependency problems - leaving unconfigured
>  nvidia-glx-->dependency problems - leaving unconfigured
> 

Problem after dist-upgrade and dpkg install -f (Probably nvidia packages related)

[Aquarius]

I read an article on cme which would give me an GUI for viewing and editing 
systemd config files. So I thought I would install the packages involved on 
Debian 8 Jessie Dell XPS15 laptop to study systemd config files. Not to edit 
them. I use Debian for about 2 years now, so still in a learning process. I 
hope you will read through till the end of this mail in which I hopefully 
reconstruct the steps I performed:

Well, I performed:
apt-get update
 apt-get upgrade
 apt-get install gparted (this was because of another excercsie)
 apt-get install -f
all was well untill now
apt-get install cme libconfig-model-systemd-perl
I only remember a message about the packages not being found. Well, leave it be 
I thought, I will do without studying systemd for now.
But maybe I should update my system because I read until V215 of systmd it is 
vulnerable and I was running V215. I thought I could upgrade systemd but was 
not sure of that.
I performed:
apt-get dist-upgrade
I know I got a message about something with 'nvidia' but can not exactly recall 
what. But also a message to perform:
dpkg --configure -a

In the messages I got from that were:

 libgl1-nvidia-glx:amd64-->not configured
 nvidia-driver-->not configured
 xserver-xorg-video-nvidia-->dependency problems - leaving unconfigured
 nvidia-glx-->dependency problems - leaving unconfigured

Because of the dependency problems I though I'ld run:
dpkg install -f
It gives this output:
The following packages were automatically installed and are no longer required:
'long list of packages but last time I used autoremove I ultimately reinstalled 
my system, it removed to much packages'
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up libgl1-nvidia-glx:amd64 (340.101-1) ...
Cursor blinking: well here is a cursor blinking and I probably can wait forever 


The ps a gives this output:
  PID TTY  STAT   TIME COMMAND
  598 tty1 Ss+    0:00 /sbin/agetty --noclear tty1 linux
  616 tty7 Rs+    4:17 /usr/bin/X :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
 3609 pts/0    Ss 0:00 bash
 3617 pts/0    S  0:00 su
 3618 pts/0    S  0:00 bash
 3636 pts/0    S+ 1:20 apt-get install -f
 3648 pts/1    Ss+    0:00 /usr/bin/dpkg --status-fd 48 --configure 
libgl1-nvidia-glx:amd64 xserver-xorg-video-nvidia:amd64 nvidia-dri
 3649 pts/1    S+ 0:00 /usr/bin/perl -w /usr/share/debconf/frontend 
/var/lib/dpkg/info/libgl1-nvidia-glx:amd64.postinst configure 
 3655 pts/1    S+ 0:00 /bin/sh 
/var/lib/dpkg/info/libgl1-nvidia-glx:amd64.postinst configure 340.96-1
 3658 pts/1    D+ 0:00 /bin/sh 
/usr/lib/nvidia/check-for-mismatching-nvidia-module 340.101
 3818 pts/2    Ss 0:00 bash
 3827 pts/2    S  0:00 su
 3828 pts/2    S  0:00 bash
 3911 pts/2    R+ 0:00 ps a
>From that I concluded the proces apt-get install -f is in status S meaning 
>"Interruptible sleep (waiting for an event to complete)"

Yesterday I killed the process apt-get-install -f so I could shut down my 
machine. It seems to be working all right (until now).

Now I do not know what to do. I can not perform a dist-upgrade.

Do I have to enter information on where the cursor is blinking?
Any other ideas how to come out of this situation?
Any other checks to perform?
Maybe get some more information out of logs (which and where to find)?

Well I hope someone has gone reading this far. Thanks for that. I hope you can 
help!

Aquarius
--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com

Re: Possibly erroneous "device not present" message during boot

[Pascal Hambourg]

Le 12/04/2017 à 17:14, Richard Owlett a écrit :


Whether initiated after power-on OR a restart the observed sequence is:
1. Appearance of the Grub2 menu with a choice of 4 instances of Debian.
2. Select instance installed on the SD card.
3. Screen clears, this message appears against the Debian 8 background.
   error:  no such device: 380e2a6d-f851-4fd1-9db2-869a0982b511.
   Press any key to continue ...
4. Otherwise the instance of Debian on the SD card boots routinely.


This is a GRUB error message which cannot find the UUID specified in a 
"search" command.


In order to investigate, can you
- report the menu entry code for the SD card system in 
/boot/grub/grub.cfg (the one from the system on the hard drive owning 
GRUB, not the one on the SD card) ;
- while the SD card is inserted, in the GRUB menu press "c" to enter a 
GRUB shell and report the result of the "ls" command.

Re: If Linux Is About Choice, Why Then ...

[GiaThnYgeia]

David Wright:
>> Has Debian always been this crazy and am I so new to this madness?
> 
> If you don't like it, you're free to look elsewhere for a distribution
> that better suits you.

Are you mr.Debian?  Under what authority are you telling me to either
shut up or leave?  What makes you more Debian than me?  Why don't you
leave if you don't like criticism?
If there is reason for madness, in which I accept I am new to, I will
have to discover it.  Saying that simply madness is normal and whoever
does not like it should leave doesn't justify madness.
If you like to contribute to my lack of understanding and possibly
unsubstantiated criticism, help me understand the hierarchy.  Who, and
how are they are selected, make the decisions and how do they relate to
those that do the work, and how do they all relate to those who for 2
decades have been employing the system and feedback with problems and bugs.
Because what is discussed on this thread to me sounds as those who by
majority have used the system (mostly for commercial large scale server
applications) and are probably the number one source of bugs that feed
development did not have much of a say on the direction taken.  The
direction was dictated from above and developers went to work according
to that direction.
Am I wrong?  I don't hear newbies single machine users having much of an
issue with systemd, but people whose work for many years was based in
fine-tuning other init systems seem to be having issues in adopting to
this new status-quo whether they like it or not.

> Cheers,
> David.

As for the other post you commented on with the same attitude I would
have to say that getting technical in comparing sysv with competing
technologies does not answer the political part of the decision making.
It seems as this part is what irritated people not the technical aspects
of it.  Unless there are those that pretend the decision making process
was solely on technical merits.
That's where the definition of "free" comes in, which you seem to be
having a hard time understanding.  I'd say go back and read the policy
and principles of Debian.  The realities of industry and market is not
part of what I understand as free, on the contrary I find them
contradictory.

cheers

-- 
 "The most violent element in society is ignorance" rEG

"Who died and made you the superuser?"  Brooklinux

Re: If Linux Is About Choice, Why Then ...

[Patrick Bartek]

On Wed, 12 Apr 2017 10:36:33 +0100 Jonathan Dowland 
wrote:

> On Sun, Apr 09, 2017 at 11:07:13PM -0700, Patrick Bartek wrote:
> > Perhaps instead of "..more suited," it should have been "intended"
> > for servers.  After all, wasn't systemd adopted first for RHEL whose
> > market is mainly servers?
> 
> No, it wasn't. It was in Fedora before RHEL.

Fedora is the development and test bed for RHEL much as Debian
Testing is for Stable. But technically, you're correct: systemd was in
Fedora before RHEL. Spliting hairs..  In any case, systemd is truly Red
Hat's baby.

B

Re: If Linux Is About Choice, Why Then ...

[David Wright]

On Tue 11 Apr 2017 at 14:24:00 (+), GiaThnYgeia wrote:
> xxx:
> > On Tue, Apr 11, 2017 at 6:21 AM, GiaThnYgeia
> >> Has Debian always been this crazy and am I so new to this madness?
> > 
> > Moving the goalposts always generates a bit of madness. Whether this
> > time is turning out more so than previous times I'll leave for others
> > to comment on.
> 
> Moving the goalposts is a decision that weighs on those exact
> individuals that made it, not the entire community.
> 
> Let me ask this encyclopedic question.  Would newer server hardware
> benefit more from the anticipated sysv development or from the systemd?
> I suspect that a 4 year old server had a 20% capability improvement with
> systemd development while a 1 year old server had a 40% improvement,
> despite the fact that the 1 year old one was 4 times as capable as the
> older one.  With sysV i suspect the development would maybe affect 24%,
> on both.  So was the choice made on the basis of exploiting ever newer
> hardware or to continue the human support of those employing Debian for
> years?  Disregarding community and bending over to industry, that is!
> 
> I have no real data to prove this, I am only suspecting this to be true.

What's the point of making stuff up and posting it then? Just trolling?

> Sometimes sticking to principles and protecting the survivability of the
> organization becomes contradictory.  What is meant by "free" is getting
> hazier and hazier.  It is now a gray area of market logic.
> The question then becomes, as has always been, whose side are you on
> boys?  And when I say boys I mean the decision making few that usually
> are boys anyway, unlike the woman that wrote the song.

I've no idea what all this is about.

Cheers,
David.

Re: If Linux Is About Choice, Why Then ...

[David Wright]

On Mon 10 Apr 2017 at 21:21:00 (+), GiaThnYgeia wrote:
> Please excuse the intrusion, on another thread Felix Miata says:
> Re: Old 32bit PC 650kRam less VidMem 1024x768 will not run on Stretch ok
> on Jessie
> 
> > Debian-user is a user support forum, not a developer forum:
> > For bug fixes and policy modifications debian-user is the wrong place
> > for more than passing discussion. I suggest other avenues:
> 
> Ask me why I think the two threads may be related
> 
> to...@tuxteam.de:
> > On Mon, Apr 10, 2017 at 04:13:48PM +0200, Nicolas George wrote:
> >> Le primidi 21 germinal, an CCXXV, to...@tuxteam.de a écrit :
> >>> SysV init is broken because it has no process monitoring? No.
> >>> Process monitoring isn't in its scope.
> > 
> >> Your other arguments make sense, but sorry, this one does not. The
> >> process with PID one is the only immortal process on the system, and
> >> adopts all orphan processes. For that reason, any kind of process
> >> monitoring, if it needs reliability, must be rooted in PID 1. And in
> >> turn, that makes process monitoring in scope for any project that aims
> >> to implement a program for PID 1.
> > 
> > Runit works. Think about how :-)
> > 
> > (And yes, double-forking trickery fools it. Don't do that then. Most
> > daemons have a command line option for that, and those that dont...
> > after all, you have to "fix" daemons to let them participate in systemd's
> > socket activation party too, don't you?
> > 
> > regards
> > -- t
> 
> The way I see things is that there are long-time server administrators
> who refuse to leave their pre-systemd platforms no matter what.
> There are "users" on Jessie where Jessie has 4 times the open bug
> reports than testing.

This ratio should increase as the release date approaches, because
the developers are squashing bugs. That's how ratios work: reducing
the denominator increases the ratio.

> For a second month under freeze not much
> development can take place in unstable, as it is really tomorrow's
> testing.

What do you mean? Sid (unstable) is always sid. It doesn't suddenly
become buster (the next testing) when stretch is released.

> All Stretch seems to be is Jessie with linux4 solving 75% of
> its bugs, meanwhile the current old-stable will no longer be supported.

That depends on the architecture. Most of us will see support for
wheezy until at least May next year.

> Meamwhile, there are critical bugs still open on testing from last year.
> 
> Has Debian always been this crazy and am I so new to this madness?

If you don't like it, you're free to look elsewhere for a distribution
that better suits you.

Cheers,
David.

Re: Possibly erroneous "device not present" message during boot

[Richard Owlett]

On 04/12/2017 07:39 AM, songbird wrote:

Richard Owlett wrote:

...

THE SYMPTOM:

When I got home and booted to the SD card I noticed a message appeared
for ~10 seconds reporting that a device was not found giving the UUID of
the SD card.

I verified the UUID by checking the fstab file and by using gparted.

THE QUESTION:

Do I have an actual problem?
What should I be checking?


 - the bios may not be set correctly to find the device.


I do not see how the bios might be involved.
Grub2 has been installed to the MBR of /dev/sda .
The only known reference to Grub2 is in the instance of Debian residing 
on /dev/sda1 .

Whether initiated after power-on OR a restart the observed sequence is:
1. Appearance of the Grub2 menu with a choice of 4 instances of Debian.
2. Select instance installed on the SD card.
3. Screen clears, this message appears against the Debian 8 background.
   error:  no such device: 380e2a6d-f851-4fd1-9db2-869a0982b511.
   Press any key to continue ...
4. Otherwise the instance of Debian on the SD card boots routinely.



 - you may have changed it but not saved it (ditto
on the partition table).


What may may I have changed and not saved.
The *ONLY* time anything has been to/with/??? the partition &/or 
partition was when the Debian Installer created the single partition  as 
a "Primary partition" and formatted it as ext4.




 - you may have the root/boot partitions in
fstab wrong (i never use UUIDs but make partition
labels instead and use those).


"fstab" was created by the installer using its defaults.
I agree that UUIDs make no sense for a application such as mine.
I haven't got around to changing things - TODO is lengthening.



 - error in preseed file which put something in
a different location than intended.


No preseed file has been involved. The installation was completely 
manual in Expert Mode.




 - grub may not have done what you expected.


As likely as moon being "green cheese"? 
I've not had a grub problem since first using it on Squeeze, although 
I've often doubted the sanity of some design choices.

Besides a few thousand people use it daily without problems ;/

In theory, I know of the existence of log files. I've never had reason 
to investigate them. Which should I preserve, if any?





  songbird

Technology user's list/Decision makers list.

[sonya . bowers]

Hi,

We would like to ascertain your interest to acquire *technology user
contacts* or *decision maker’s contacts* list for your business campaigns.

Data fields: Name, Company's Name, Phone Number, Fax Number, Job Title,
Email address, Complete Mailing Address, Company Revenue Size, Employee
Size, Web address etc.

We own and maintain 150 Million B2B global opt-in database and have
information of 6 Million technology users within that. We can segment
Industry List & Technology Users List by C-level, VP-level, Director-Level,
Manager Level, etc as per your requirements.

Kindly review and advice or forward this email to the marketing head in
your company who are currently working on similar requirements.

Await your response.

Regards

Sonya Bowers
Data Specialist

Reply “Remove” to Opt-Out

System broken after yesterday's upgrade

[solitone]

Hi, something really weird is going on today on my system--debian stretch on 
an Apple MacBookPro 12,1.

Some time ago I noticed a strange issue with USB, which prevented the keyboard 
and the trackpad to work after bootup (they are both USB devices on 
MacBookPro's). Here's an extract of the kernel logs that I collected at the 
time:
> Mar 29 09:06:25 alan kernel: usb 2-3: device not accepting address 2, error
> -62
> Mar 29 09:06:36 alan kernel: usb 2-3: device not accepting address 3, error
> -62
> Mar 29 09:06:55 alan kernel: xhci_hcd :00:14.0: Stopped the command ring
> failed, maybe the host is dead
> Mar 29 09:06:55 alan kernel: xhci_hcd :00:14.0: Abort command ring
> failed Mar 29 09:06:55 alan kernel: xhci_hcd :00:14.0: HC died;
> cleaning up Mar 29 09:06:55 alan kernel: xhci_hcd :00:14.0: HC died;
> cleaning up Mar 29 09:06:55 alan kernel: xhci_hcd :00:14.0: HC died;
> cleaning up Mar 29 09:06:56 alan kernel: usb 2-3: device not accepting
> address 4, error -108
> Mar 29 09:06:56 alan kernel: usb usb2-port3: couldn't allocate usb_device

After some rest, everything started working again, and I didn't worried--till 
this morning, when I rebooted! Again, keyboard and trackpad no longer worked. 
Again I brutally switched of the laptop, and tried to wait some time, but 
nothing, this time it didn't help! I suspect the misbehaviour depends on the 
upgrade I carried on yesterday, since this was my first reboot since then.

The really strange thing is that even grub now is sooo slow to show up. It 
takes 30 secs or more! Obviously, the keyboard does not work there. After some 
additional time, the kernel boots up, but it stalls for 30 seconds on the step 
"loading initial ramdisk". After that, it boots up correctly, displays the 
login manager, but as I said I have no keyboard nor trackpad.

I tried many times. In the end I tried and plugged external usb mouse and 
keyboard. After bootup they didn't work either, but after some additional 30 
seconds they started working, together with the integrated keyboard and the 
trackpad. No idea what's going on.

I rebooted without the external usb devices plugged in, and waited for several 
minutes, but nothing happened, keyboard and trackpad didn't start working. I 
rebooted again, like before with the two external usb devices attached, and 
like before everything started working after some pretty long time.

As I said, the culprit might be yesteday's upgrade. Among others, the kernel 
was upgraded:
 
Start-Date: 2017-04-11  07:33:56
Commandline: packagekit role='update-packages'
Requested-By: solitone (1000)
Upgrade: [...] linux-image-4.9.0-2-amd64:amd64 (4.9.13-1, 4.9.18-1
) [...]

Everything worked fine before. Now the first steps (starting from grub) in the 
bootup process are unbelievably slow, and the laptop's keyboard and trackpad 
don't work unless I wait much time and do some weird ritual, like plugging in 
some external usb devices and again wait and wait.

Now everything works well, but I fear that at the next reboot I'll have to 
struggle, hope, and pray that I can use my sytem again!

Here are the kernel error message that I've collected during the last reboot:

solitone@alan:~$ sudo journalctl -k -b -1 -p 3
-- Logs begin at Sun 2017-02-12 21:33:16 CET, end at Wed 2017-04-12 15:42:11 
CEST. --
Apr 12 14:42:14 alan kernel: brcmfmac :03:00.0: firmware: failed to load 
brcm/brcmfmac43602-pcie.txt (-2)
Apr 12 14:42:14 alan kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware version 
= wl0: Nov 10 2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8c
Apr 12 14:42:14 alan kernel: brcmfmac: brcmf_cfg80211_reg_notifier: not a 
ISO3166 code (0x30 0x30)
Apr 12 14:42:15 alan kernel: brcmfmac: brcmf_p2p_create_p2pdev: set p2p_disc 
error
Apr 12 14:42:15 alan kernel: brcmfmac: brcmf_cfg80211_add_iface: add iface 
p2p-dev-wlp3s0 type 10 failed: err=-16
Apr 12 14:42:21 alan kernel: brcmfmac: brcmf_inetaddr_changed: fail to get arp 
ip table err:-23
Apr 12 14:42:22 alan kernel: usb 2-3: device not accepting address 2, error 
-62
Apr 12 14:42:33 alan kernel: usb 2-3: device not accepting address 3, error 
-62
Apr 12 14:42:39 alan kernel: Bluetooth: hci0 urb 8ae9df53b840 failed to 
resubmit (22)
Apr 12 14:42:39 alan kernel: Bluetooth: hci0 urb 8ae9df53b000 failed to 
resubmit (22)
Apr 12 14:42:39 alan kernel: Bluetooth: hci0 urb 8ae9df53b900 failed to 
resubmit (22)
Apr 12 14:42:39 alan kernel: Bluetooth: hci0 urb 8ae9df53bf00 failed to 
resubmit (22)
Apr 12 14:42:39 alan kernel: xhci_hcd :00:14.0: HC died; cleaning up
Apr 12 14:42:39 alan kernel: bcm5974 1-5:1.2: could not read from device
Apr 12 14:46:12 alan kernel: INFO: task kworker/1:1:46 blocked for more than 
120 seconds.
Apr 12 14:46:12 alan kernel:   Not tainted 4.9.0-2-amd64 #1
Apr 12 14:46:12 alan kernel: "echo 0 > /proc/sys/kernel/
hung_task_timeout_secs" disables this message.
Apr 12 14:48:12 alan kernel: INFO: task kworker/1:1:46 blocked for more 

Re: Possibly erroneous "device not present" message during boot

[songbird]

Richard Owlett wrote:

...
> THE SYMPTOM:
>
> When I got home and booted to the SD card I noticed a message appeared 
> for ~10 seconds reporting that a device was not found giving the UUID of 
> the SD card.
>
> I verified the UUID by checking the fstab file and by using gparted.
>
> THE QUESTION:
>
> Do I have an actual problem?
> What should I be checking?

 - the bios may not be set correctly to find
the device.

 - you may have changed it but not saved it (ditto
on the partition table).

 - you may have the root/boot partitions in
fstab wrong (i never use UUIDs but make partition
labels instead and use those).

 - error in preseed file which put something in
a different location than intended.

 - grub may not have done what you expected.


  songbird

Possibly erroneous "device not present" message during boot

[Richard Owlett]

Due to circumstances, will note rule out any of hardware, software, or 
confused operator as underlying cause.


BACKGROUND:
The hardware is a used Lenovo T510 laptop purchased a couple of months 
ago. Jessie with MATE desktop has been running fine.

Yesterday I purchased a Kingston Technology 512GB SD, primarily for backups.

As this individual unit had never had an SD card installed, the 
agreement with the store was if the card did not work in this machine I 
would not have to purchase it. My acceptance test was to install Jessie 
using a flash drive with DVD 1 of 13 of Debian 8.6.0.


It was my standard install which does NOT include either a swap 
partition being activated during install NOR installing a boot loader.


I booted into my primary OS and ran update-grub with no problems.
I rebooted, choosing the SD card from the Grub2 menu. No apparent 
problem. Also verified my other Debian installs could read/write the SD 
card.


These tests were performed before leaving the store.

THE SYMPTOM:

When I got home and booted to the SD card I noticed a message appeared 
for ~10 seconds reporting that a device was not found giving the UUID of 
the SD card.


I verified the UUID by checking the fstab file and by using gparted.

THE QUESTION:

Do I have an actual problem?
What should I be checking?
TIA

Re: system drive encryption question

[Jonathan Dowland]

On Thu, Apr 06, 2017 at 03:18:10AM -0700, Rick Thomas wrote:
> With the introduction of systemd in Jessie, the mechanism that ran a script
> to get a password to decrypt the root disk[1] got broken.  I don’t think
> there was anything about systemd in particular that made it impossible, it
> just wasn’t at the top of the developer’s priority list to implement that
> feature.

It works fine for me, now, with jessie and systemd. I use it to be able to
supply a decryption key via SSH when my headless NAS system reboots.

https://jmtd.net/hardware/phobos/#index6h3
 

-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC me, I am subscribed to the list.


signature.asc
Description: Digital signature

Re: If Linux Is About Choice, Why Then ...

[Jonathan Dowland]

On Sun, Apr 09, 2017 at 11:07:13PM -0700, Patrick Bartek wrote:
> Perhaps instead of "..more suited," it should have been "intended" for
> servers.  After all, wasn't systemd adopted first for RHEL whose
> market is mainly servers?

No, it wasn't. It was in Fedora before RHEL.

-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC me, I am subscribed to the list.


signature.asc
Description: Digital signature

Mail Confusion

[Hans]

Dear list, 

I am a little bit confused about mail behaviour. There are two things, I do 
not understand. 

First of all, the following:

When I was long time online with another computer, reading my mails, and then 
switch to another computer back, then I rsync the Mailfolder to the other 
computer (so that all mails are on the computer, I used not the long time).

But then, this computer indexes the Mailfolder again (what is ok) and then the 
weired thing starts: It downloads all mails again from the mailserver, even I 
deleted them on this mailserver! This are also mails, which are some years 
old. Where do these mails come from??? By accessing the mailserver via 
webinterface, it shows - NO MAILS! Strange thing. Can somebody technical 
explain this weired behaviour?


The second thing is: I have local system mails, which are sent to my user 
account on my computer. These are read with kmail2, and after I read, I 
deleted them. However, when I call mutt, these mails are still there. How must 
I configure kmail2, so that the mails are deleted in mutt, too, when I delte 
them in kmail2? There are four settings in the configuration: none, mutt-
dotlock, procmail-lock and mutt-lock-with-rights (hopefully correct 
translated, my kmail2 is in German).

Thanks for any enlightening!

Best regards

Hans 

Re: Displaymanager resolutie

[Paul van der Vlis]

Op 12-04-17 om 09:36 schreef Huub Reuver:
> On Tue, Apr 11, 2017 at 03:54:24PM +0200, Paul van der Vlis wrote:
>> Hoi allen,
>>
>> Ik wil de resolutie wijzigen van GDM3, of eventueel een andere
>> displaymanager zoals LightDM. Maar dit lukt niet zo erg.
>>
>> Ik heb geprobeerd een regel met xrandr toe te voegen in
>> /etc/gdm3/Init/Default, zoals in vele manuals staat.
>> Maar het werkt niet.
>>
>> Ook zoiets werkt niet:
>> cp /home/user/.config/monitors.xml /var/lib/gdm3/.config/monitors.xml
>>
>> Is er hier iemand die hier ervaring mee heeft?
>>
>> Dit gaat om Debian testing.
> 
> Ik gebruik zelf altijd een scriptje om direct met xrandr de resolutie
> te wijzigen van een netbook.
> 
> Het script doet de volgende dingen:
> - bekijk de huidige status (start xrandr en purge de resultaten).
> - kijk welke aansluitingen er zijn
> - als de externe monitor is aangesloten maar niet gebruikt zet
>   deze dan met xrandr in een standaard resolutie
> - zet de interne videokaart uit,
> - schakel de externe videokaart in de resolutie van de monitor
> 
> De tussenregel van schakelen naar een standaard resolutie is om 
> een vast uitgangspunt te hebben, dat verbetert de betrouwbaarheid 
> van het script nogal.
> 
> Mijn script is "hardcoded" en wordt gestart met een toetsencombinatie.
> Dit betekent dat ik geen input nodig heb. Gewoon monitor inpluggen
> en de toetsencombinatie. En ja, xbindkeys of iets vergelijkbaars moet
> zijn gestart bij het starten van X. En ik kan alleen enkele vaste 
> configuraties "doortoggelen".
> 
> Ik gebruik dat script zelf als ik een externe monitor gebruik 
> (laptopscherm uit, beeld extern of andersom).
> En ja, omdat het hardcoded is werkt een vrij eenvoudig script.
> Denk aan regels als:
>   xrandr | grep HDMI-1 # dit gebruik ik om de gebruikte resolutie 
># te achterhalen voor IF-constructies.
>   xrandr --output HDMI-1 --mode "1920x1080"
>   xrandr --output HDMI-1 --off
> Waarschijnlijk wil jij iets dat algemeen werkt(?).

Het liefst wel, maar dat blijkt lastig.

Wat betekend dat "--off" ?

Het gaat overigens om een HiDMI monitor, dat wordt niet juist herkend.
Daarom is alles erg klein.

Ik heb het overigens al via een "script" geprobeerd. Dat wil zeggen, een
script van 1 regel wat ik direct in het configfile heb gezet. Maar dit
ging niet. Doe jij dit onder Debian, en zo ja met welke display manager?

> Wat niet werkt is een combinatie van de opensource NVidia drivers en
> HDMI output, beperking van de drivers.

Het gaat bij mij niet om NVidia, maar om open source drivers (AMD).

> En het is mij opgevallen dat elke laptop en netbook weer andere labels
> voor de display uitgang heeft (VGA1, VGA-1, HDMI1, HDMI-1, etc.).

Ja, iets wat voor alles geldt zou veel handiger zijn. Deze computer
heeft 4 displayport aansluitingen, dus ik moet het 4x doen.

Groeten,
Paul


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

Re: Displaymanager resolutie

[Huub Reuver]

On Tue, Apr 11, 2017 at 03:54:24PM +0200, Paul van der Vlis wrote:
> Hoi allen,
> 
> Ik wil de resolutie wijzigen van GDM3, of eventueel een andere
> displaymanager zoals LightDM. Maar dit lukt niet zo erg.
> 
> Ik heb geprobeerd een regel met xrandr toe te voegen in
> /etc/gdm3/Init/Default, zoals in vele manuals staat.
> Maar het werkt niet.
> 
> Ook zoiets werkt niet:
> cp /home/user/.config/monitors.xml /var/lib/gdm3/.config/monitors.xml
> 
> Is er hier iemand die hier ervaring mee heeft?
> 
> Dit gaat om Debian testing.

Ik gebruik zelf altijd een scriptje om direct met xrandr de resolutie
te wijzigen van een netbook.

Het script doet de volgende dingen:
- bekijk de huidige status (start xrandr en purge de resultaten).
- kijk welke aansluitingen er zijn
- als de externe monitor is aangesloten maar niet gebruikt zet
  deze dan met xrandr in een standaard resolutie
- zet de interne videokaart uit,
- schakel de externe videokaart in de resolutie van de monitor

De tussenregel van schakelen naar een standaard resolutie is om 
een vast uitgangspunt te hebben, dat verbetert de betrouwbaarheid 
van het script nogal.

Mijn script is "hardcoded" en wordt gestart met een toetsencombinatie.
Dit betekent dat ik geen input nodig heb. Gewoon monitor inpluggen
en de toetsencombinatie. En ja, xbindkeys of iets vergelijkbaars moet
zijn gestart bij het starten van X. En ik kan alleen enkele vaste 
configuraties "doortoggelen".

Ik gebruik dat script zelf als ik een externe monitor gebruik 
(laptopscherm uit, beeld extern of andersom).
En ja, omdat het hardcoded is werkt een vrij eenvoudig script.
Denk aan regels als:
  xrandr | grep HDMI-1 # dit gebruik ik om de gebruikte resolutie 
   # te achterhalen voor IF-constructies.
  xrandr --output HDMI-1 --mode "1920x1080"
  xrandr --output HDMI-1 --off
Waarschijnlijk wil jij iets dat algemeen werkt(?).

Wat niet werkt is een combinatie van de opensource NVidia drivers en
HDMI output, beperking van de drivers.

En het is mij opgevallen dat elke laptop en netbook weer andere labels
voor de display uitgang heeft (VGA1, VGA-1, HDMI1, HDMI-1, etc.).

Met vriendelijke groet,
Huub Reuver