| Author |
Message |
towo
|
|
Post subject:
 Posted: 24.06.2011, 16:35
|
|
Joined: 2010-09-13
Posts: 488
Location: Pößneck / Thüringen
Status: Offline
|
|
Btw, the experimental packages only works in 64bit.
In 32bit glx-alternative-mesa is broken. |
|
|
| |
|
|
|
 |
|
OppaErich
|
|
|
Post subject:
Posted: 24.06.2011, 16:38
|
|
Joined: 2010-09-13
Posts: 25
Location: Essen, Germany
Status: Offline
|
|
|
|
|
|
|
towo
|
|
|
Post subject:
Posted: 24.06.2011, 16:39
|
|
Joined: 2010-09-13
Posts: 488
Location: Pößneck / Thüringen
Status: Offline
|
|
| Then, there is no xserver-xorg-video-nvidia installed. |
|
|
| |
|
|
|
|
|
neosid
|
|
|
Post subject:
Posted: 24.06.2011, 16:46
|
|
Joined: 2011-06-23
Posts: 22
Status: Offline
|
|
New and additional experimental line, in sources? Then your commands? Then remove that experimental line, before my next dist-upgrade; after the fix falls to sid?
64bit here; thanks. |
|
|
| |
|
|
|
|
|
towo
|
|
|
Post subject:
Posted: 24.06.2011, 16:53
|
|
Joined: 2010-09-13
Posts: 488
Location: Pößneck / Thüringen
Status: Offline
|
|
| There is no need to remove the experimental entrie from the sources. |
|
|
| |
|
|
|
|
|
sng
|
|
|
Post subject:
Posted: 24.06.2011, 17:55
|
|
Joined: 2010-09-12
Posts: 14
Location: Greece
Status: Offline
|
|
I have successfully applied ripper's instructions and everything is ok now on 32bit
Thanks again man |
|
|
| |
|
|
|
|
|
neosid
|
|
|
Post subject:
Posted: 24.06.2011, 18:22
|
|
Joined: 2011-06-23
Posts: 22
Status: Offline
|
|
Tried fixing via experimental, and failed:
What I did
..added duplicate line, in sources, and changed sid, to experimental (left sid line), and dist-upgraded. Still broken nvidia. I broke my repaired downgrade (page 3), to test this....
Ran Towo's commands:
Quote:
apt-get purge $(dpkg -l | awk '/nvidia/{print $2}')
apt-get update && apt-get dist-upgrade
apt-get -t experimental install nvidia-kernel-source
m-a clean nvidia-kernel-source && m-a a-i nvidia-kernel-source
apt-get -t experimental install nvidia-glx
Failed installing packs. Trying to recover...
I understand, some people posted that it worked for them, but for me, and now others...
errors:
Quote:
Package glx-alternative-mesa is not configured yet.
dpkg: error processing glx-alternative-nvidia (--configure):
dependency problems - leaving unconfigured
Removed experimental source, left sid.
Trying then to fix the two stuck, and loaded (selected?) experimental packages. I set:
(This was wrong, I think)
Quote:
Package: *
Pin: release a=testing
Pin-Priority: 1001
Package: *
Pin: release a=unstable
Pin-Priority: 60
Package: *
Pin: release a=experimental
Pin-Priority: 50
Updated and ran:
# dpkg --force-depends -r glx-alternative-mesa
...DID NOT WORK, strangely.
got
Quote:
(Reading database ... 131314 files and directories currently installed.)
Removing glx-alternative-mesa ...
update-alternatives: error: /var/lib/dpkg/alternatives/glx corrupt: duplicate slave link /usr/lib/x86_64-linux-gnu/libGL.so.1
dpkg: error processing glx-alternative-mesa (--remove):
subprocess installed pre-removal script returned error exit status 2
Errors were encountered while processing:
glx-alternative-mesa
How do I get back? |
Last edited by neosid on 27.06.2011, 06:08; edited 6 times in total
|
| |
|
|
|
|
|
towo
|
|
|
Post subject:
Posted: 24.06.2011, 18:42
|
|
Joined: 2010-09-13
Posts: 488
Location: Pößneck / Thüringen
Status: Offline
|
|
I have installed the driver from experimental on 2 machines without any problem.
I don't know, what are you doing. |
|
|
| |
|
|
|
|
|
neosid
|
|
|
Post subject:
Posted: 24.06.2011, 18:56
|
|
Joined: 2011-06-23
Posts: 22
Status: Offline
|
|
I am trying to remove glx-alternative-mesa, that is left as "unconfigured"; so, I can purge the two installed, and difficult to remove, experimental packages...
glx-alternative-mesa
glx-alternative-nvidia
Quote:
apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up glx-alternative-mesa (0.1) ...
Processing triggers for glx-alternative-mesa ...
update-alternatives: error: /var/lib/dpkg/alternatives/glx corrupt: duplicate slave link /usr/lib/x86_64-linux-gnu/libGL.so.1
dpkg: error processing glx-alternative-mesa (--configure):
subprocess installed post-installation script returned error exit status 2
configured to not write apport reports
dpkg: dependency problems prevent configuration of glx-alternative-nvidia:
glx-alternative-nvidia depends on glx-alternative-mesa; however:
Package glx-alternative-mesa is not configured yet.
dpkg: error processing glx-alternative-nvidia (--configure):
dependency problems - leaving unconfigured
configured to not write apport reports
Errors were encountered while processing:
glx-alternative-mesa
glx-alternative-nvidia
E: Sub-process /usr/bin/dpkg returned an error code (1)
, per your commands, and exactly what I said, I did above.
What is "duplicate slave link", and why is that stopping the install and removal, of theses packages?
Addendum:
OK. I fixed it myself! ...Got myself in a mess, just testing for everyone, and got myself back out!
The error on the "mesa" pack (the mesa one, or some dependency, of a dependency), was the file "glx". I renamed it glx.HOLD.
I went back to my working directions, earlier in this thread and followed them, again. The point, after changing back from testing, to sid sources, I could then (and only then, after renaming glx), install dependences (the mesa one, or some dependency, of a dependency) to start, one by one, (about three) until nvidia-glx (in my line; after setting sources back) would install, along with the others. I also deleted my test, preferences file. I had none before.
Can't say as I can recommend the experimental method, even though Towo got it to work. I'd say, just use my testing downgrade post, until the fix is in sid. Then release it.
As a fall-back, you have the sgfxi script. I'm not using that currently.
Working; as testing downgrade, and held. See my instructions, on page 3, of this thread. 4+ times verified, here; on one of my systems. |
Last edited by neosid on 27.06.2011, 06:29; edited 1 time in total
|
| |
|
|
|
|
|
Spaceferret
|
|
|
Post subject:
Posted: 25.06.2011, 01:48
|
|
Joined: 2010-09-13
Posts: 96
Status: Offline
|
|
| Thank you towo, I have followed your recommendations installing from experimental and it works 100%. Thank you again ! |
|
|
| |
|
|
|
|
|
Spaceferret
|
|
|
Post subject:
Posted: 25.06.2011, 02:13
|
|
Joined: 2010-09-13
Posts: 96
Status: Offline
|
|
| Just curious- is it OK to update to the newer versions of glx in experimental ?Or is it better to comment experimental out and wait ? |
|
|
| |
|
|
|
|
|
jacmoe
|
|
|
Post subject:
Posted: 25.06.2011, 10:43
|
|
Joined: 2011-04-13
Posts: 40
Location: Denmark
Status: Offline
|
|
Why did you move this topic out of upgrade warnings?
To create drama? Or was it a mistake? |
|
|
| |
|
|
|
|
|
DonKult
|
|
|
Post subject:
Posted: 25.06.2011, 11:23
|
|
Team Member
Joined: 2010-09-02
Posts: 419
Status: Offline
|
|
|
jacmoe wrote:
Or was it a mistake?
I haven't moved it myself, but the end of the thread is FAAAAAR away from being close to be supportable. If the answer is --force-depends the question was properly: "After which commands should i reinstall my system?" The showed preference entry is also a good answer to this question…
All in all the only sane solution i have seen here is installing the package from experimental which is now in unstable, so no need for all these kind of trickery…
And i heard a few people saying it works now (irc, this thread), so if it doesn't for you, please open a new thread as it would be a different issue with the same endresult - and none of the included """solutions""" is good anymore… (if they were at any time).
P.S.: I can't help with the issue at hand as i don't have radeon or nvidia cards, but if i would read one of the posts above i wouldn't even bother to help as i would prefer to work on my skill to juggle with running chainsaws. That would be at least saner and easier… so splitting your issue to a new one is a very good idea… |
_________________
MfG. DonKult
"I never make stupid mistakes. Only very, very clever ones." ~ The Doctor
|
| |
|
|
|
|
|
jacmoe
|
|
|
Post subject:
Posted: 25.06.2011, 19:19
|
|
Joined: 2011-04-13
Posts: 40
Location: Denmark
Status: Offline
|
|
I agree that the topic was invaded by dragons. 
My problem is solved (downgraded), and I am just going to wait until updated nVidia/glx stuff hits the unstable branch. |
|
|
| |
|
|
|
|
|
mz
|
|
|
Post subject:
Posted: 25.06.2011, 23:21
|
|
Joined: 2010-09-11
Posts: 53
Status: Offline
|
|
|
neosid wrote:
The error on the "mesa" pack (the mesa one, or some dependency, of a dependency), was the file "glx". I renamed it glx.HOLD.
I upgraded two boxes; one went smoothly and the other had "the neosid effect". Thanks for this hint; both are OK now. |
|
|
| |
|
|
|
|
|
|
