Two install problems

[vayu]

I did a successful install of Firestarter KDE. I tried to install nvidia drivers. I couldn't get it to work. After purging nvidia I ended up without direct rendering. I reinstalled.  I kept the home partition as I had spent time with desktop settings.  Install went well. I try to login, KDM pauses then comes back to the login, no messages.  

Quit to console, I find startx works. Back in, wobbly windows, transparency and all.

Still can't login with KDM.  I installed lightdm.  It works.  Everything is working well.  Now what, forget about it and go on or do I have a hidden problem lurking?

I need help on that decision.  More importantly I need help getting the nvidia drivers to work.  When I run Kubuntu on this laptop with nvidia and bumblebee it runs 41 degrees, with Debian Testing 67 degrees. I installed bubblebee with nouveau and it averages 57. Nouveau runs hot on my laptop.

Twice now I have failed at getting bumblebee setup with nvidia.  I'm wondering if it's because I need to have both nvidia and intel i915 drivers working.  That's the main thing I need help with.  Any ideas on either of these problems? (Bumblebee installed fine onto Firestarter, recent version, no dependency problems)

I installed nvidia using these instructions: http://manual.siduction.org/en/gpu-en.htm. I purged nvidia using Google translate on the German Wiki page.  It's an intel i5 laptop with an NVidia 630m and onboard intel 4000.
For the reinstall I installed root on top of the old root, and I pointed /home to the same partition from the first install.

[hendrikL]

Hi,

please provide us the output of

Code Select Expand

inxi -G -M

and give us the links/url's from the output of

Code Select Expand

siduction-paste /var/log/kdm.log
and

Code Select Expand

siduction-paste /var/log/Xorg.0.log

greetings hendrikL

[vayu]

siduction-paste seems to not be working for me:

Code Select Expand

satyam@hermes:~/.siduction-paste$ siduction-paste /var/log/kdm.log
curl: Can't open '/home/satyam/.siduction-paste/20130611165315'!
curl: try 'curl --help' or 'curl --manual' for more information
Find your paste here: http://paste.siduction.org/20130611165315 - Thank you for using siduction-paste!
satyam@hermes:~/.siduction-paste$ ls

Code Select Expand

siduction-paste.log
satyam@hermes:~/.siduction-paste$ cat siduction-paste.log
20130611164740 I: directory /home/satyam/.siduction-paste created
20130611164740 I: writing messages to logfile /home/satyam/.siduction-paste/siduction-paste.log
20130611164740 I: siduction-paste started
20130611164740 I: file entered: /var/log/kdm.log
20130611164740 I: file '20130611164740' has been uploaded to the server
20130611165315 I: writing messages to logfile /home/satyam/.siduction-paste/siduction-paste.log
20130611165315 I: siduction-paste started
20130611165315 I: file entered: /var/log/kdm.log
20130611165315 I: file '20130611165315' has been uploaded to the server

When I go to the url it can't be found.

[vayu]

satyam@hermes:~$ inxi -G -M

Code Select Expand

Machine:   System: Acer product: Aspire V3-771 version: V1.06
          Mobo: Type2 - Board Vendor Name1 model: VA70_HC version: Type2 - Board Version
          Bios: Insyde version: V1.06 date: 04/19/2012
Graphics:  Card-1: Intel 2nd Generation Core Processor Family Integrated Graphics Controller
          Card-2: NVIDIA GF108 [GeForce GT 630M]
          X.Org: 1.12.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1600x900@60.3hz
          GLX Renderer: Mesa DRI Intel Sandybridge Mobile GLX Version: 3.0 Mesa 8.0.5


The /var/log/kdm.log is empty.

The xorg log has no errors. I uninstalled nvidia and the system is working with the open source driver.  Should I put it here until I figure out siduction-paste?

[vayu]

I don't need help with the KDM problem.  On a new install it was easier to start fresh again.  I'm now up on a beautiful KDE system with a proper KDM.

Can someone help me get NVidia and Bumblebee working?

I guess I should read the manual before I do too much more.  How do I know if it's a good time for upgrade/dist-upgrade?

[der_bud]

...  How do I know if it's a good time for upgrade/dist-upgrade?

In short: check forum and apt output .
Longer version: keep an eye on the forum section called upgrade warnings and read if others report some heavy breakage or warn about bigger transitions. If everybody is quiet there or only very specific problems that do not affect you are reported, it is likely a good time for dist-upgrade.
But then, watch what apt-get dist-upgrade tells you! If it says a lot of packages are to be removed, either try to guess if they are replaced by the "xy new packages to be installed", or again come back to the warnings section in forum.
Read more here: http://manual.siduction.org/en/sys-admin-apt-en.htm#apt-upgrade
And be prepared that this is sid, so perhaps one day you will be the first one bitten, then you can warn others and fix your system with the help of this community  :wink:

[vayu]

Longer version:

Thanks, just what I was looking for.

[vayu]

That page was great.  I've come to some of that on my own.  I've had my system break a couple times using package manager.  I love to use it for searching and listing, then once I've formulated my plan I often drop down to apt-get.

How strictly do people believe is prudent in not installing while in X.  What I imagine is that when packages are simple, fairly self contained and not going to modify a lot of libraries that are used universally that it should be ok?  If prudence is used, are situations like that reasonable?

I have my first upgrade situation right now, what would an experienced siduction user do in the following situation?  I have a new install.  I've been customizing my environment.  I installed a package and it wanted to upgrade about 20 packages.  None of them looked alarming so I went for it. After installing those packages my system now reports 40 packages to upgrade.  

This is where I don't know what to do.  Normally I would look at the packages and between direct recognition and gut feeling I might either skip it, don't fix what's not broken, or I would upgrade and check if it still had upgrades after that then dist-upgrade.

Based on what I've read in the manual it seems like this would be a good time to drop out of X and dist-upgrade. What would experienced users do?  Also do people use upgrade then dist-upgrade or do they just dist-upgrade?

[michaa7]

...Also do people use upgrade then dist-upgrade or do they just dist-upgrade?

To upgrade is plain wrong (upgrade does not check dependencies. This easily will break your whole system without a warning!). It is wrong even for one ore only some packages (you better install them, which will fetch new packages and check dependencies; I only ever needed this in rare occasions when sid and apt had put me in a jam). You never ever should upgrade in sid. You only and exclusivly dist-upgrade. And when you had read the manual you should have read this recomandation. You better do it outside X ( but if *you* feel you're save to do it while in X so be it. But then you're on your own.).
There is nothing you gain from doing an upgrade, nothing.

So do yourself and us a favor. Go to RL 3 (aka init 3), there execute

apt-get update && apt-get dist-upgrade

and if nothing is removed then proceed (y).
And forget about this other command.


An experienced user has forgotten this comand in question. He executes

apt-get update && apt-get dist-upgrade -d

while in X. Upps, while in X? Yes, because the -d option downloads only and does not install. So he gets a notion of what could happen during d-u and then downloads all new packages in the background. And maybe he switches to init 3 shortly before he likes to shutdown the computer ...

[vayu]

(upgrade does not check dependencies. This easily will break your whole system without a warning!)

An experienced user has forgotten this comand in question. He executes

apt-get update && apt-get dist-upgrade -d

while in X. Upps, while in X? Yes, because the -d option downloads only and does not install. So he gets a notion of what could happen during d-u and then downloads all new packages in the background. And maybe he switches to init 3 shortly before he likes to shutdown the computer ...

Thank you. These are exactly the kind of tips I'm looking for.