The answer is “i dont know why you need this, this is probably not possible in linux and have another way, but it is important what scenario makes you want to do that to give the right answer”.
People dont just restart their Graphics driver for fun.
A conversation is not harassment. You are choosing to continue having it.
I know OP was trying to kludge some weird problem - that is why I said as much, yesterday. People don’t ask how to restart their graphics driver for fun.
They need help. “But why do you want that?” almost never helps. It is help prevention. It is where tech support threads end bitterly. Try ‘here’s the answer, please don’t,’ then doing the thing you did.
But you tell them how to disable and reenable their graphics driver, then xorg crashes, their problem isn’t solved and they give up. This question is “what is the problem you are trying to fix?”
That answer will help someone more than giving them an answer that won’t fix anything
Third time: by all means, ask the question AFTER a direct answer. A direct answer absolves any too-clever “X/Y problem” philosophizing. And obviously people would love to just not have the problems they’re trying to kludge.
by all means, ask the question AFTER a direct answer
As original commenter pointed out, by the time they commented there were 12 direct answers to the question, none of which were likely to solve any problems. I think you’re qualifying your statement after the fact to regain ground
The answer is “i dont know why you need this, this is probably not possible in linux and have another way, but it is important what scenario makes you want to do that to give the right answer”.
People dont just restart their Graphics driver for fun.
And please stop harassing me.
A conversation is not harassment. You are choosing to continue having it.
I know OP was trying to kludge some weird problem - that is why I said as much, yesterday. People don’t ask how to restart their graphics driver for fun.
They need help. “But why do you want that?” almost never helps. It is help prevention. It is where tech support threads end bitterly. Try ‘here’s the answer, please don’t,’ then doing the thing you did.
But you tell them how to disable and reenable their graphics driver, then xorg crashes, their problem isn’t solved and they give up. This question is “what is the problem you are trying to fix?”
That answer will help someone more than giving them an answer that won’t fix anything
But asking it often results in neither answer.
Third time: by all means, ask the question AFTER a direct answer. A direct answer absolves any too-clever “X/Y problem” philosophizing. And obviously people would love to just not have the problems they’re trying to kludge.
But that’s not what they came here to ask for.
As original commenter pointed out, by the time they commented there were 12 direct answers to the question, none of which were likely to solve any problems. I think you’re qualifying your statement after the fact to regain ground
What a dishonest reading of the chronology of this conversation.
And a hypocritical effort to make about us, instead of about the subject.