No init 5 with kernel 3.7.0

Started by mylo, 2012/12/16, 09:41:37

Previous topic - Next topic

mylo

Hi,

the kernel does not let me into graphical mode. Just init 3 is possible.
What can I do? What Information do you need?

qwerthi

Hi mylo,

you have to change to nvidia-glx from experimental too:

apt-get install -t experimental nvidia-kernel-dkms nvidia-glx

greetings,qwerthi.

towo

No!
The driver from experimental does not work with his card.
But the driver from our fixes Repo should do.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

mylo

Hi towo,

thanks for your message. I was just on the way searching wiki and manual (i never found out for what info i have to search where) how to activate experimental in the sources. I could not find the answer and asked myself "experimental" yes, but debian exp or siduction exp?

So I decided to come back here and saw your message.

How to activate the fixes repo?

The good message: up to now I never used it, as siduction runs so troublefree over years, also above forking events...wow a really performing linux.

Let me take this opportunity to say thank you to the team and their great work on this famous piece of software.

I wish the siduction team, their helpers and supportes and fans all over the world some peaceful calm christmas days and a happy new year!

Sorry mayas, I have to extend your calendar:
The world continues on Dec22, 2012.

towo

Show your siduction sources, the fixes repo should be in there (theoretical).
If not, you need

deb http//ftp.uni-stuttgart.de/siduction/fixes unstable main contrib non-free

to get the fixed driver.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

mylo

wie sage ich, dass ich aus dem fixes-repo installieren will?

apt-get install -t fixes packagename ?

Oder deaktiviere ich für die Installation die siduction unstable-Quelle?

dibl

Hi mylo no, no need to do "-t fixes". You should have a repo /etc/apt/sources.list.d/siduction-fixes.list and it looks like this:

root@siductionbox:/etc/apt/sources.list.d# cat siduction-fixes.list
deb http://packages.siduction.org/fixes unstable main contrib non-free
#deb-src http://packages.siduction.org/fixes unstable main contrib non-free


You might need to add contrib and non-free.

Then apt-get update and afterwards you should be able to see the available nvidia drivers like this:

root@siductionbox:/etc/apt/sources.list.d# apt-cache policy nvidia-glx
nvidia-glx:
 Installed: (none)
 Candidate: 304.64-3.1
 Version table:
    304.64-3.1 0
       500 http://packages.siduction.org/fixes/ unstable/non-free i386 Packages
    304.64-3 0
       500 http://http.debian.net/debian/ unstable/non-free i386 Packages


On this 32-bit system (with Intel GPU), I ran "apt-get -s install nvidia-glx" and it would install the fixed driver from the siduction-fixes repo.  However, you could also run:

apt-get install nvidia-glx=304.64-3.1 and that will install the fixed one.
System76 Oryx Pro, Intel Core i7-11800H, ASRock B860 Pro-A, Intel Core Ultra 7 265KF, Nvidia GTX-1060, SSD 990 EVO Plus.

mylo

Hi dibl,

regards to Ohio!

Yes, I made it towards init 5 again. I tried to install
nvidia-glx
nvidia-kernel-dkms


However, apt was "zickig", means "did anything else I expected (so the opposite of troublefree)".

So I deinstalled anything, apt had a prob with ("Abhängigkeiten") and I installed


...-glx and ...-dkms

again.
It works. Thanks guys for your help.

From my understanding, now I have a nvidia driver from source "fixes".

Do I have to obey something in terms of d-u?
How to handle *fixes in the sources list? Comment out?

dibl

Quote from: "mylo"Hi dibl,

regards to Ohio!

und Frohe Weihnachten zu Wiesbaden!

Quote

Do I have to obey something in terms of d-u?
How to handle *fixes in the sources list? Comment out?

No, just leave the siduction-fixes.list active.  There will be no problems with d-u (except maybe your kranken/zickig apt ...).  :)
System76 Oryx Pro, Intel Core i7-11800H, ASRock B860 Pro-A, Intel Core Ultra 7 265KF, Nvidia GTX-1060, SSD 990 EVO Plus.

mylo

Ok, I understand. If fixes has a better pack with higher version number it is taken, otherwise the standard repo is the package source.