nvidia and latest unstable kernel image

[Sebastian P. Luque]

Hi,

I just upgraded to the latest linux kernelimage (2.6.25-2) in my sid system,
followed up by the usual 'm-a prepare && m-a a-i nvidia".  I also rebooted
into single-user mode and upgraded nvidia-glx, and got no errors or warnings.  
However, upon rebooting, I can see that kdm (my login manager) starts fine,
but I only get a black screen (with a super thin color line, matching the
colors of my login background) at this point.  It seems as if the login
manager is there, and I can even login "blindly" by just typing my user name
and password.  The usual kde sounds, etc. work, but the screen just remains
black, so something seems out of whack with X server.  I have never had this
problem before after upgrades of kernel images and/or nvidia packages.  Any
help please?  Thanks!

Seb


--
To UNSUBSCRIBE, email to debian-amd64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Lennart Sorensen]

On Fri, Jun 27, 2008 at 08:51:24PM +0000, Sebastian Luque wrote:

> I just upgraded to the latest linux kernelimage (2.6.25-2) in my sid system,
> followed up by the usual 'm-a prepare && m-a a-i nvidia".  I also rebooted
> into single-user mode and upgraded nvidia-glx, and got no errors or warnings.  
> However, upon rebooting, I can see that kdm (my login manager) starts fine,
> but I only get a black screen (with a super thin color line, matching the
> colors of my login background) at this point.  It seems as if the login
> manager is there, and I can even login "blindly" by just typing my user name
> and password.  The usual kde sounds, etc. work, but the screen just remains
> black, so something seems out of whack with X server.  I have never had this
> problem before after upgrades of kernel images and/or nvidia packages.  Any
> help please?  Thanks!

Which nvidia version?  Did you clean up /usr/src/modules/nvidia* before
running m0a again (I really wish m-a would celan up rather than just
extract on top of old code).

Which nvidia card type?

--
Len Sorensen


--
To UNSUBSCRIBE, email to debian-amd64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Sebastian P. Luque]

Lennart Sorensen <lsorense <at> csclub.uwaterloo.ca> writes:

> Which nvidia version?  Did you clean up /usr/src/modules/nvidia* before
> running m0a again (I really wish m-a would celan up rather than just
> extract on top of old code).
>
> Which nvidia card type?

Thanks Len, this is in sid (so nvidia-kernel-source 173.14.09-2), and yes I
did 'rm /usr/src/nvidia*' before doing the module-assistant calls.  WRT the
nvidia card type, I'm not sure where to access that info in my system.  If
you're referring to the video card, it's a GeForce 6100.

--
Seb



--
To UNSUBSCRIBE, email to debian-amd64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Lennart Sorensen]

On Fri, Jun 27, 2008 at 09:44:37PM +0000, Sebastian Luque wrote:
> Thanks Len, this is in sid (so nvidia-kernel-source 173.14.09-2), and yes I
> did 'rm /usr/src/nvidia*' before doing the module-assistant calls.  WRT the
> nvidia card type, I'm not sure where to access that info in my system.  If
> you're referring to the video card, it's a GeForce 6100.

Hmm.  Someone else was seeing system crashes with a GeForce 6200
recently.  I am starting to wonder if there is a problem with some
models and the new driver.  I think I have a 6200 around somewhere I
could try on, but I certainly don't have a 6100.

What does your /var/log/Xorg.0.log say.  Perhaps it has a clue as to
why the screen would be blank.

--
Len Sorensen


--
To UNSUBSCRIBE, email to debian-amd64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Sebastian P. Luque]

Lennart Sorensen <lsorense <at> csclub.uwaterloo.ca> writes:

> Hmm.  Someone else was seeing system crashes with a GeForce 6200
> recently.  I am starting to wonder if there is a problem with some
> models and the new driver.  I think I have a 6200 around somewhere I
> could try on, but I certainly don't have a 6100.
>
> What does your /var/log/Xorg.0.log say.  Perhaps it has a clue as to
> why the screen would be blank.

Thanks again.  Nothing looks odd in the log, except for a:

"Could not init font path element /usr/share/fonts/X11/cyrillic, removing from
list!"

which doesn't seem too serious.  I'll see if removing that font path from
my /etc/X11/xorg.conf resolves the issue, but I doubt it.  Should I try
installing from experimental with m-a?  If so, how?

Cheers,
--
Seb




--
To UNSUBSCRIBE, email to debian-amd64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Sebastian P. Luque]

I recall seeing a message that went something
like: "somefile_has_stack_protector: no such file or directory", during the
building done by module-assistant.  The building procedure hung there for a
while and then continued without problems, but I haven't seen that before and
may be the problem.  Does this ring a bell?  Where may I see a log of the
build procedure to have a closer look?  Thanks!

--
Seb





--
To UNSUBSCRIBE, email to debian-amd64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Sebastian P. Luque]

I tried building a few times more and got the full error message:

/usr/src/linux-headers-2.6.25-2-amd64/scripts/gcc-x86_64-has-stack-protector.sh:
No such file or directory

and although the build process finishes fine, this looks like a bug somewhere
which may be rendering the package unuseable.  At this point, I'd like to just
downgrade to the testing packages.  Can someone provide some tips to do this
with module-assistant?  I have my /etc/apt/apt.conf with the following:

APT::Default-Release "unstable";

so I'm not sure how to get module-assistant to do it.  Thanks.


--
Seb


--
To UNSUBSCRIBE, email to debian-amd64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Sebastian P. Luque]

On Sat, 28 Jun 2008 17:28:26 +0000 (UTC),
Sebastian Luque <spluque@...> wrote:

> I tried building a few times more and got the full error message:
> /usr/src/linux-headers-2.6.25-2-amd64/scripts/gcc-x86_64-has-stack-protector.sh:
> No such file or directory

> and although the build process finishes fine, this looks like a bug
> somewhere which may be rendering the package unuseable.  At this
> point, I'd like to just downgrade to the testing packages.  Can
> someone provide some tips to do this with module-assistant?  I have my
> /etc/apt/apt.conf with the following:

> APT::Default-Release "unstable";

> so I'm not sure how to get module-assistant to do it.  Thanks.

I'm quite stuck and without knowing how to do the above, I've tried to
use module-assistant again (removing /usr/src/nvidia* and
/usr/src/modules/nvidia prior to that) and with the -t switch to have a
better log of the procedure (please see attached).  In the meantime,
I've set my /etc/X11/xorg.conf to use the "nv" driver (which makes my
display look quite funny...).  I'm also not sure whether this is a
problem in the latest linux kernel image (2.6.25-2) or in the nvidia
driver, or their combination, since this only came up after upgrading
both.  Any further help would be much appreciated.  Thanks.


--
Seb

["Jaime Ochoa Malagón"]

Hi, just add to your /etc/apt/sources.list

deb http://snapshot.debian.net/archive pool nvidia-graphics-drivers
deb-src http://snapshot.debian.net/archive pool nvidia-graphics-drivers

install the right version and use

m-a -t -f clean,buidl,install nvidia

That usually work for me...

On Sat, Jun 28, 2008 at 7:39 PM, Seb <spluque@...> wrote:

>> I tried building a few times more and got the full error message:
>> /usr/src/linux-headers-2.6.25-2-amd64/scripts/gcc-x86_64-has-stack-protector.sh:
>> No such file or directory
>
>> and although the build process finishes fine, this looks like a bug
>> somewhere which may be rendering the package unuseable.  At this
>> point, I'd like to just downgrade to the testing packages.  Can
>> someone provide some tips to do this with module-assistant?  I have my
>> /etc/apt/apt.conf with the following:
>
>> APT::Default-Release "unstable";
>
>> so I'm not sure how to get module-assistant to do it.  Thanks.
>
> I'm quite stuck and without knowing how to do the above, I've tried to
> use module-assistant again (removing /usr/src/nvidia* and
> /usr/src/modules/nvidia prior to that) and with the -t switch to have a
> better log of the procedure (please see attached).  In the meantime,
> I've set my /etc/X11/xorg.conf to use the "nv" driver (which makes my
> display look quite funny...).  I'm also not sure whether this is a
> problem in the latest linux kernel image (2.6.25-2) or in the nvidia
> driver, or their combination, since this only came up after upgrading
> both.  Any further help would be much appreciated.  Thanks.
>
>
> --
> Seb
>

--
Perhaps the depth of love can be calibrated by the number of different
selves that are actively involved in a given relationship.

        Carl Sagan (Contact)

        Jaime Ochoa Malagón
        Arquitecto de Soluciones
        Cel: [phone]


--
To UNSUBSCRIBE, email to debian-amd64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Sebastian P. Luque]

On Sat, 28 Jun 2008 21:15:32 -0500,
"Jaime Ochoa Malagón" <chptma@...> wrote:

> Hi, just add to your /etc/apt/sources.list deb
> http://snapshot.debian.net/archive pool nvidia-graphics-drivers
> deb-src http://snapshot.debian.net/archive pool
> nvidia-graphics-drivers

> install the right version

Thanks Jaime, are you referring to nvidia-kernel-source here?


--
Seb


--
To UNSUBSCRIBE, email to debian-amd64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

["Jaime Ochoa Malagón"]

kernel-source and libraries should match version...

ii  nvidia-glx                                  173.14.09-2
              NVIDIA binary Xorg driver
ii  nvidia-glx-dev                              173.14.09-2
              NVIDIA binary Xorg driver development files
ii  nvidia-glx-ia32                             173.14.09-2
              NVIDIA binary XFree86 4.x driver
ii  nvidia-kernel-2.6.24-1-amd64                173.14.09-2+2.6.24-7
              NVIDIA binary kernel module for Linux 2.6.24
ii  nvidia-kernel-source                        173.14.09-2
              NVIDIA binary kernel module source


On Sun, Jun 29, 2008 at 6:42 AM, Seb <spluque@...> wrote:

> On Sat, 28 Jun 2008 21:15:32 -0500,
> "Jaime Ochoa Malagón" <chptma@...> wrote:
>
>> Hi, just add to your /etc/apt/sources.list deb
>> http://snapshot.debian.net/archive pool nvidia-graphics-drivers
>> deb-src http://snapshot.debian.net/archive pool
>> nvidia-graphics-drivers
>
>> install the right version
>
> Thanks Jaime, are you referring to nvidia-kernel-source here?
>
>
> --
> Seb
>
>
> --
> To UNSUBSCRIBE, email to debian-amd64-REQUEST@...
> with a subject of "unsubscribe". Trouble? Contact listmaster@...
>
>

--
Perhaps the depth of love can be calibrated by the number of different
selves that are actively involved in a given relationship.

        Carl Sagan (Contact)

        Jaime Ochoa Malagón
        Arquitecto de Soluciones
        Cel: [phone]


--
To UNSUBSCRIBE, email to debian-amd64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Koen Tavernier]

Hi,

Sebastian Luque wrote:
> I tried building a few times more and got the full error message:
>
> /usr/src/linux-headers-2.6.25-2-amd64/scripts/gcc-x86_64-has-stack-protector.sh:
> No such file or directory
>
>  
Just to chip in, I got the same error message when compiling the new
module, however the resulting kernel module works fine for me. I'm
running this on a Geforce 8600 GT though.

modinfo gives:

filename:       /lib/modules/2.6.25-2-amd64/nvidia/nvidia.ko
license:        NVIDIA
alias:          char-major-195-*
alias:          pci:v000010DEd*sv*sd*bc03sc02i00*
alias:          pci:v000010DEd*sv*sd*bc03sc00i00*
depends:        i2c-core
vermagic:       2.6.25-2-amd64 SMP mod_unload
[...]

Regards,

Koen.





--
To UNSUBSCRIBE, email to debian-amd64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Sebastian P. Luque]

Thanks everyone for the feedback.  I found another report with the same
card I have, which shows the problem of the 1 thin (1 pixel presumably)
line at the top:

http://www.nvnews.net/vbulletin/showthread.php?t=115209

Unfortunately, no solution was offered, so it seems I'll have to just
revert back to a previous version of the driver, following Jaime's
pointers for building it.  Thanks.




On Mon, 30 Jun 2008 09:31:56 +0100,
Koen Tavernier <koen@...> wrote:

> Hi,
> Sebastian Luque wrote:
>> I tried building a few times more and got the full error message:

>> /usr/src/linux-headers-2.6.25-2-amd64/scripts/gcc-x86_64-has-stack-protector.sh:
>> No such file or directory


> Just to chip in, I got the same error message when compiling the new
> module, however the resulting kernel module works fine for me. I'm
> running this on a Geforce 8600 GT though.

> modinfo gives:

> filename: /lib/modules/2.6.25-2-amd64/nvidia/nvidia.ko license: NVIDIA
> alias: char-major-195-* alias: pci:v000010DEd*sv*sd*bc03sc02i00*
> alias: pci:v000010DEd*sv*sd*bc03sc00i00* depends: i2c-core vermagic:
> 2.6.25-2-amd64 SMP mod_unload [...]

> Regards,

> Koen.



Cheers,

--
Seb


--
To UNSUBSCRIBE, email to debian-amd64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Sebastian P. Luque]

On Mon, 30 Jun 2008 08:41:49 -0500,
Seb <spluque@...> wrote:

> Thanks everyone for the feedback.  I found another report with the
> same card I have, which shows the problem of the 1 thin (1 pixel
> presumably) line at the top:

> http://www.nvnews.net/vbulletin/showthread.php?t=115209

> Unfortunately, no solution was offered, so it seems I'll have to just
> revert back to a previous version of the driver, following Jaime's
> pointers for building it.  Thanks.

Just a quick followup report to indicate that I ultimately succeeded
with these steps (for posterity!):

1) rm -rf /usr/src/modules/nvidia /usr/src/nvidia*

2) added /etc/apt/sources.list lines (thanks to Jaime):

---<---------------cut here---------------start-------------->---
deb http://snapshot.debian.net/archive pool nvidia-graphics-drivers
deb-src http://snapshot.debian.net/archive pool nvidia-graphics-drivers
---<---------------cut here---------------end---------------->---

3) apt-get update
4) apt-get install nvidia-kernel-common nvidia-kernel-source=169.12-1
5) can't use the latest sid kernel, so go back to 2.6.24-1:

apt-get install linux-image-2.6.24-1-amd64 linux-headers-2.6.24-1-amd64

6) boot into 2.6.24-1 and:

m-a -t -f clean,build,install nvidia

7) apt-get install nvidia-glx=169.12-1


However, it's frustrating to remain ignorant about what the problem is
with my combination of the latest driver, kernel, and have to use an
older kernel.


Thanks to everyone for your input,

--
Seb


--
To UNSUBSCRIBE, email to debian-amd64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Sebastian P. Luque]

Hi,

I still cannot use the new 2.6.25 kernel due to this problem with nvidia
module, even with the recently available linux-headers-2.6.25-2-amd64
and image packages.  I'm starting to think that these don't work with my
card anymore.  If anybody has any further tips, I'd be grateful for
them.  Thanks.


Cheers,

--
Seb


--
To UNSUBSCRIBE, email to debian-amd64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Cassiel]

I am on debian lenny amd64 shipped with an nvidia GeForce 6150, with 2.6.24 release I had no problem running nv driver, now I am 2.6.25 using nvidia proprietary driver with no problem at all. Dual head works fine too.

I just followed this brief but operative how-to
http://tinyplanet.ca/~lsorense/debian/debian-nvidia-dri-howto.html

hope this helps

2008/7/15 Seb <spluque@...>:

Hi,

I still cannot use the new 2.6.25 kernel due to this problem with nvidia
module, even with the recently available linux-headers-2.6.25-2-amd64
and image packages.  I'm starting to think that these don't work with my
card anymore.  If anybody has any further tips, I'd be grateful for
them.  Thanks.


Cheers,

--
Seb


--
To UNSUBSCRIBE, email to debian-amd64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[er-5]

Hi,

I'm migrating from an i686 to an EM64T machine (Intel core 2 quad) and
I'd like to know whether there are specific options that I can pass to
gcc for an optimization of my code or if everything is blindly set up.
How would I manage the 4 cpu cores if I was to write in assembly?

Thank you in advance for any link or information on this subject.

Emmanuel


--
To UNSUBSCRIBE, email to debian-amd64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Cyril Jaquier-2]

Hi,

> I'm migrating from an i686 to an EM64T machine (Intel core 2 quad) and
> I'd like to know whether there are specific options that I can pass to
> gcc for an optimization of my code or if everything is blindly set up.
> How would I manage the 4 cpu cores if I was to write in assembly?
>

GCC has a lot of optimization/architecture flags. Just have a look here
[1]. However, this won't make your software use the 4 cores.

You should use threads or multiple processes with IPC. I don't know what
you want to do but I think you should forget about writing in assembly
and use an higher level language. You probably don't need assembly at
all. Moreover, higher level language have sometimes concurrency and
synchronization facilities which will help you getting the most of your
4 cores.

Regards,

Cyril Jaquier

[1] http://gcc.gnu.org/onlinedocs/gcc/i386-and-x86_002d64-Options.html


--
To UNSUBSCRIBE, email to debian-amd64-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...