Page 83 of 100
Re: LMDE BREAKAGES - tracking TESTING - updated 10 Fev
Posted: Tue Feb 21, 2012 3:42 pm
by kruijf
GregE wrote: You cannot just change to 64bit by changing the kernel.
I know you cannot just change the kernel for 64bit, i didth a 64bit install. The result whas the same problem as whit 32bit. installing the 686-PAE in 32bit results in the same problem. Every time i got a log out of my system.
I solved the problem whit a install of Debian Testing, and the problem is gone.
Re: LMDE BREAKAGES - tracking TESTING - updated 10 Fev
Posted: Tue Feb 21, 2012 3:59 pm
by zerozero
kruijf
if debian testing is working for you, wonderful!
that leads me to think that your previous issue was the flash v. you had installed (probably still 10.x) and having 5 flash v. in the repo doesn't help either
Screenshot-11.png
Re: LMDE BREAKAGES - tracking TESTING - updated 10 Fev
Posted: Tue Feb 21, 2012 4:09 pm
by kruijf
I think i had the mint-flashpluging 11 but i dont know for sure.
Whit Debian Testing everything is working normal and good, in the past i had all ready Debian stable.
But went to Mint for the eye candy, no i'am back whit Debian does not means that i let Mint go.
I still are a Team member of Linux Mint NL, and whil test every new Mint in Vbox becaus Mint is a very good distro.
Also i install Mint whit new Linux users, and my second laptop is getting Mint also.
Re: LMDE BREAKAGES - tracking TESTING - updated 10 Fev
Posted: Thu Feb 23, 2012 10:05 pm
by mockturtl
nvidia-glx
Debian Wheezy amd64 + nvidia-glx-290.10-1 and xserver-xorg-video-nvidia + linux-image-3.2.0-1-amd64 = FAIL
No joy with
nvidia-glx v295 from sid, either.
See if your card is a "supported product:"
http://www.nvidia.com/object/linux-disp ... river.html
I'm able to get rid of the nvidia-glx packages in synaptic by booting into an older kernel.
(Psst. If this problem affects you, and you're using Cinnamon, please let me know whether it
crashes when you restart twice.)
Re: LMDE BREAKAGES - tracking TESTING - updated 10 Fev
Posted: Thu Feb 23, 2012 11:12 pm
by mockturtl
The new
google-chrome-unstable 19.0.1049.3 dev closes a few seconds after launching.
Re: LMDE BREAKAGES - tracking TESTING - updated 10 Fev
Posted: Fri Feb 24, 2012 12:32 am
by GregE
My Google Chrome is working fine (64bit) Version 19.0.1049.3 dev, although my system is Sid based.
If it is just you rather than everyone on testing then try a fix that often works. Rename ~/.config/google-chrome to google-chrome.sav and restart with a clean config.
Re: LMDE BREAKAGES - tracking TESTING - updated 10 Fev
Posted: Fri Feb 24, 2012 12:46 am
by mockturtl
GregE wrote:My Google Chrome is working fine (64bit) Version 19.0.1049.3 dev, although my system is Sid based.
If it is just you rather than everyone on testing then try a fix that often works. Rename ~/.config/google-chrome to google-chrome.sav and restart with a clean config.
It does feel like a sync problem.
Re: LMDE BREAKAGES - tracking TESTING - updated 10 Fev
Posted: Fri Feb 24, 2012 7:17 pm
by zerozero
Re: LMDE BREAKAGES - tracking TESTING - updated 10 Fev
Posted: Fri Feb 24, 2012 8:57 pm
by mockturtl
No, that box is new -- it was supposed to be a freeBSD server, but
that didn't work out.
Just trying to upgrade from nouveau for the first time. That will definitely come in handy, thanks for the link.
Re: LMDE BREAKAGES - tracking TESTING - updated 10 Fev
Posted: Tue Feb 28, 2012 4:50 am
by mockturtl
Still no luck with the
latest kernel update. Back to nouveau for now.
Re: LMDE BREAKAGES - tracking TESTING - updated 10 Fev
Posted: Tue Feb 28, 2012 9:28 pm
by zerozero
Re: LMDE BREAKAGES - tracking TESTING - updated 10 Fev
Posted: Tue Feb 28, 2012 10:33 pm
by mockturtl
Here we go...
amd64, I have dkms, I think I have the headers installed correctly:
Code: Select all
$ apt-cache policy linux-image-3.2.0-1-amd64
linux-image-3.2.0-1-amd64:
Installed: 3.2.6-1
Candidate: 3.2.6-1
(wheezy box, I also have 3.2.4-1 on my UP4 box with GeForce 8800 GT; no nvidia-glx there either)
Didn't know about
kbuild, I'll look into that.
Re: LMDE BREAKAGES - tracking TESTING - updated 10 Fev
Posted: Sun Mar 04, 2012 3:31 pm
by zerozero
we have to search for these small things to keep this topic alive
today's update of
Code: Select all
Start-Date: 2012-03-04 15:04:50
Commandline: apt-get dist-upgrade
[...]
Upgrade:[...]gnome-tweak-tool:amd64 (3.2.2-2, 3.2.2-3), [...]
End-Date: 2012-03-04 15:07:11
breaks the user-theme extension;
the fix is
Code: Select all
Start-Date: 2012-03-04 19:19:31
Commandline: /usr/sbin/synaptic
Reinstall: gnome-shell-extensions:amd64 (3.2.3-1), gnome-tweak-tool:amd64 (3.2.2-3)
End-Date: 2012-03-04 19:19:38
HTH
Re: LMDE BREAKAGES - tracking TESTING - updated 10 Fev
Posted: Mon Mar 12, 2012 6:47 am
by viking777
we have to search for these small things to keep this topic alive
Not today.
Upgrade to kernel 3.2.0-2 resulted in graphics failure. Easily cured by an upgrade of nvidia-kernel-dkms followed by a reboot ( the reboot wasn't necessary to get the graphics back but necessary to cure the dreadful overheating/slow performance/lack of acceleration/gnome-fallback/gdm3 runaway, that resulted from the upgrade).
All OK now though (or so it seems, it has only been running for 5 minutes).
Re: LMDE BREAKAGES - tracking TESTING - updated 10 Fev
Posted: Mon Mar 12, 2012 7:32 am
by zerozero
that's what gives hit the "y" key before checking the news
same here
nvidia doesn't rebuild against the new kernel (not automatically, we have to force it as viking pointed out in the post above)
VB also fails;
i'm a total n00b in that matter, so this is more a question than a solution: i reinstalled vb-dkms and it's working now. it's all it takes or shall i take any extra steps?
Re: LMDE BREAKAGES - tracking TESTING - updated 10 Fev
Posted: Mon Mar 12, 2012 7:43 am
by viking777
VB also fails;
Thanks for the reminder, I will have to do that as well. Reinstalling vb-dkms is all that is usually necessary for me.
Its ironical this, a few months ago I switched over to using sgfxi for nvidia installs, but I switched back to dkms because I had to run sgfxi after every kernel update, but now I have to update nvidia-kernel-dkms every time instead. I might as well have stayed where I was.
Re: LMDE BREAKAGES - tracking TESTING - updated 10 Fev
Posted: Mon Mar 12, 2012 7:49 am
by GeneC
viking777 wrote:.............Its ironical this, a few months ago I switched over to using sgfxi for nvidia installs, but I switched back to dkms because I had to run sgfxi after every kernel update, but now I have to update nvidia-kernel-dkms every time instead. I might as well have stayed where I was.
It is confusing, isn't it.
I am staying with sgfxi. Its simple, it always works, but necessary every kernel upgrade.
Re: LMDE BREAKAGES - tracking TESTING - updated 12 Mar
Posted: Wed Mar 21, 2012 1:18 am
by ptruchon
On one partition, I'm using LMDE-Xfce tracking
latest and I'm very pleased. I used the repo posted here:
http://forums.linuxmint.com/viewtopic.php?f=141&t=76556 without problem.
Now, I'd like to install LMDE tracking
testing on my other partition to play with GNOME 3. Which repo should I use? Would it make sense to mention these at the beginning of the thread?
Cheers!
Re: LMDE BREAKAGES - tracking TESTING - updated 12 Mar
Posted: Wed Mar 21, 2012 12:33 pm
by cecar
ptruchon wrote:
Now, I'd like to install LMDE tracking testing on my other partition to play with GNOME 3. Which repo should I use? Would it make sense to mention these at the beginning of the thread?
Cheers!
This i believe.
Code: Select all
deb http://packages.linuxmint-fr.net/ debian upstream import romeo main
deb http://ftp.se.debian.org/debian/ testing main contrib non-free
deb http://security.debian.org/ testing/updates main contrib non-free
deb http://www.debian-multimedia.org testing main non-free
Re: LMDE BREAKAGES - tracking TESTING - updated 12 Mar
Posted: Wed Mar 21, 2012 6:49 pm
by GregE
cecar wrote:
This i believe.
Code: Select all
deb http://packages.linuxmint-fr.net/ debian upstream import romeo main
deb http://ftp.se.debian.org/debian/ testing main contrib non-free
deb http://security.debian.org/ testing/updates main contrib non-free
deb http://www.debian-multimedia.org testing main non-free
That looks correct, except you would alter the second line to the mirror for your own country or use the main Debian server.
Then do
sudo apt-get update
sudo apt-get dist-upgrade
And always be careful that there is not some odd dependency that wants to remove half your system. My rule is simple - if it says "0 to remove" then you are good to go. And read this forum for possible problems. Running testing is pretty safe, it is rare to have problems. But, it can happen.
is that a 32 or 64bit system? if 32 are you still using the 486 kernel or already installed the 686-pae? and the headers? and dkms? and kbuild? a lot of questions