Re: Problems with gcc
I think my gcc problem is partly solved. It seems related to time_t which doesn't behave on amd64 as on i386 (where it was a double). I don't know yet how to cope with this but there must be a solution, there is a lot of concern about time_t and amd64 on the web. If you have a quick answer to this question too, don't hesitate to talk to me! For the installation and removal of gcc-4.3 base I still can't figure out what to do, but if compilation is possible, I feel less annoyed yet. Thank you again, Emmanuel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems with gcc
On Wed, Jul 16, 2008 at 11:56:46PM +0200, E. Rens wrote: When I realized that I couldn't run compiled programs I decided to remove all the versions of gcc I had (3.4, 4.1, 4.3) to reinstall them from the mirror (ftp://ftp.fr.debian.org/debian/ lenny main contrib -- changing it later to the main didn't improve the situation) running apt-get clean, then: # sudo apt-get remove gcc-4.3 gcc-4.3-base Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libgcc1: Depends: gcc-4.3-base (= 4.3.1-2) but it is not going to be installed E: Broken packages After that,trying to remove libgcc1 (just to see) I got : The following packages have unmet dependencies: libc6: Depends: libgcc1 but it is not going to be installed E: Broken packages I can only reinstall these 2 packages but not remove them. Trying to remove libc6 (also for testing) brings up an awful list of software, among them essential ones that wouldn't leave my system usable, but at least it is removable. libc6, libgcc1 and hence gcc-4.3-base are required packages. You can replace them, but not remove them. Still there may not actually be a problem. You could install the apt-show-versions tool and run it, and see if it lists anything as not uptodate or such, including 'newer than version in archive' which would tend to indicate something from sid or elsewhere. If everything is simply up to date then there is nothing currently incorrect installed, and anything that doesn't work is either a bug or a user error. I can't actually remember what the problem started out as anymore. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems with gcc
On Thu, Jul 17, 2008 at 11:35:52AM +0200, E. Rens wrote: I think my gcc problem is partly solved. It seems related to time_t which doesn't behave on amd64 as on i386 (where it was a double). I don't know yet how to cope with this but there must be a solution, there is a lot of concern about time_t and amd64 on the web. If you have a quick answer to this question too, don't hesitate to talk to me! For the installation and removal of gcc-4.3 base I still can't figure out what to do, but if compilation is possible, I feel less annoyed yet. Well making code 64bit clean takes work in some cases where people made (incorrect) assumptions about types which just happened to work. time_t is __TIME_T_TYPE which is __SLONGWORD_TYPE which is 'long int' which is 32bit on some systems and 64bit on others I believe. As long as the code ALWAYS uses time_t when working on time values, that is no problem. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia and latest unstable kernel image
On Wed, Jul 16, 2008 at 07:36:35PM -0500, Mark Allums wrote: Thanks for that, I am forewarned. However, my point was really about the newest driver working well with the newest kernels. I am not a particular fan of nvidia, per se. (I would like to see them release some of their software as free and/or open sourece.) 3rd party installers are not as a category the problem; the problem is individual software developers not taking the time to do things right. This is a definite issue that Linux is going to have as long as there are different distributions. It is hard for someone to package up something for Redhat, SuSE, Slackware, Debian, and so on. Debian is a particular challenge for them, apparently. Which is odd given it has by far the nicest tools for making packages. Making rpm's is hard and has to be made for each distribution. A debian package will often work on many different debian based distributions. I do not run my particular setup as a production system. It won't cost me much time or any productivity to have to fix it when things finally break. So, I don't have to wait for a Debian maintainer to get around to packaging up the solution to my current problem. Your advice should definitely be heeded by someone who is more dependent on their machine being up most of the time. I will keep this in mind when giving out info or advice from here on. A better solution is to make a new debian package based on the new upstream driver and install that. That way you are working with the package system rather than against it, and it is very easy to do. Isn't the current 173 driver version new enough for you? Did nvidia go and release 177 as stable already? -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia and latest unstable kernel image
On Wed, Jul 16, 2008 at 08:53:10PM -0400, C. Ahlstrom wrote: I update nvidia direct from nvidia.com, and have had no issues. So far. You will at some point. Everyone does eventually. Same for the kernel -- I always build it from source myself (that way I can change the configuration). The kernel has its own location for files so it isn't usually a big deal, although using make-kpkg (from kernel-package) makes it trivial to have your own kernel installed using the package system. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia and latest unstable kernel image
On Wed, 16 Jul 2008 20:53:10 -0400, C. Ahlstrom [EMAIL PROTECTED] wrote: [...] I update nvidia direct from nvidia.com, and have had no issues. Same for the kernel -- I always build it from source myself (that way I can change the configuration). Here's a thread where I learnt the hard way what Lennart is referring to: http://permalink.gmane.org/gmane.linux.debian.ports.amd64/20620 so you may not notice the mess until the changes interfere with Debian proper packages. -- Seb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia and latest unstable kernel image
Seb 11:33 Thu 17 Jul On Wed, 16 Jul 2008 20:53:10 -0400, C. Ahlstrom [EMAIL PROTECTED] wrote: [...] I update nvidia direct from nvidia.com, and have had no issues. Same for the kernel -- I always build it from source myself (that way I can change the configuration). Here's a thread where I learnt the hard way what Lennart is referring to: http://permalink.gmane.org/gmane.linux.debian.ports.amd64/20620 so you may not notice the mess until the changes interfere with Debian proper packages. I update both my main systems (32-bit DELL laptop and 64-bit no-name desktop) nearly every day, and have had no issues. (I don't permit the Nvidia installer to touch xorg.conf). Therefore, I view this note at that link: The nvidia-installer indiscriminately overwrites key files in /usr, leading to major system death in the event of upgraded X-related packages. as innocent F.U.D. until proven otherwise. Is there a list of the files the nvidia-installer overwrites? A spot check shows only /usr/lib/libGL.so and friends. -- I am ready to meet my Maker. Whether my Maker is prepared for the great ordeal of meeting me is another matter. -- Winston Churchill -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia and latest unstable kernel image
Lennart Sorensen 12:46 Thu 17 Jul On Wed, Jul 16, 2008 at 08:53:10PM -0400, C. Ahlstrom wrote: I update nvidia direct from nvidia.com, and have had no issues. So far. You will at some point. Everyone does eventually. Well, it's been about two years so far. I'll be sure to post an account of this disaster when it happens grin. Same for the kernel -- I always build it from source myself (that way I can change the configuration). The kernel has its own location for files so it isn't usually a big deal, although using make-kpkg (from kernel-package) makes it trivial to have your own kernel installed using the package system. make menuconfig make make modules_install mkinitramfs copy files to /boot modify grub/menu.lst THe only part that bugs me is the menuconfig. I'd really like to make a kernel that builds /only/ the parts my laptop needs, but I have no idea what comprises that set! -- Deek Yes, America is a country based on how pissed-off a group of taxed people can get. Deek We exist as a country because we're cheap. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia and latest unstable kernel image
Lennart Sorensen wrote: On Wed, Jul 16, 2008 at 07:36:35PM -0500, Mark Allums wrote: It is hard for someone to package up something for Redhat, SuSE, Slackware, Debian, and so on. Debian is a particular challenge for them, apparently. Which is odd given it has by far the nicest tools for making packages. Making rpm's is hard and has to be made for each distribution. A debian package will often work on many different debian based distributions. True enough. Although that is not universally true. Ubuntu people should not use Debian packages, and vice versa. Isn't the current 173 driver version new enough for you? Did nvidia go and release 177 as stable already? I am using a(n nvidia) patched 173. Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia and latest unstable kernel image
On Thu, Jul 17, 2008 at 02:58:15PM -0500, Mark Allums wrote: True enough. Although that is not universally true. Ubuntu people should not use Debian packages, and vice versa. Almost always works fine, and the dependancies will let you know when it won't pretty much. I am using a(n nvidia) patched 173. Well the 173 package in debian is patched and works wtih the kernels in debian just fine. It only needed a bit of work to put up with XEN. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia and latest unstable kernel image
C. Ahlstrom wrote: The kernel has its own location for files so it isn't usually a big deal, although using make-kpkg (from kernel-package) makes it trivial to have your own kernel installed using the package system. 0. make mrproper 0.5 cp /boot/config .config 1.make menuconfig 2.make 2.5 modules 3 make modules_install 4.depmod -a 5.mkinitramfs 6.make install copy files to /boot modify grub/menu.lst THe only part that bugs me is the menuconfig. I'd really like to make a kernel that builds /only/ the parts my laptop needs, but I have no idea what comprises that set! You are missing a few steps. I have modified your list, a bit. There is another way, the Debian way, that makes it almost trivial. It requires the Debian kernel package and the Debian kernel tools. If you run gnome you can substitute make gconfig for make menuconfig. much better. You can copy the old Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia and latest unstable kernel image
Mark Allums wrote: 0. make mrproper 0.5 cp /boot/config .config 1.make menuconfig 2.make 2.5 modules 3 make modules_install 4.depmod -a 5.mkinitramfs 6.make install copy files to /boot modify grub/menu.lst 2. should read make bzImage 2.5 should read make modules. Although, if you use just make, the bzImage and module are made in one step. I like to make them separately. Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia and latest unstable kernel image
Mark Allums 15:18 Thu 17 Jul Mark Allums wrote: 0. make mrproper 0.5 cp /boot/config .config 1.make menuconfig 2.make 2.5 modules 3 make modules_install 4.depmod -a 5.mkinitramfs 6.make install copy files to /boot modify grub/menu.lst 2. should read make bzImage 2.5 should read make modules. Although, if you use just make, the bzImage and module are made in one step. I like to make them separately. Thanks! I'm pretty sure the modules_install target does depmod for you, though. Anyway, the procedure is pretty straightforward and I no longer have to consult notes to do it. I missed an opportunity to try it the Debian way recently, when I did a full reinstall dang. Linux fluxster 2.6.25.10-ca #1 SMP Wed Jul 9 18:17:49 EDT 2008 i686 -- Q: Why do the police always travel in threes? A: One to do the reading, one to do the writing, and the other keeps an eye on the two intellectuals. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia and latest unstable kernel image
C. Ahlstrom wrote: Thanks! I'm pretty sure the modules_install target does depmod for you, though. It may do that now. Just like make does the equivalent of 'make dep' for you now, so you can skip that step. Anyway, the procedure is pretty straightforward and I no longer have to consult notes to do it. I missed an opportunity to try it the Debian way recently, when I did a full reinstall dang. A brief description of the Debian way is in the Debian documentation, if you have that installed. It requires quite a few packages, and it depends on the Debian patched kernel. If you use the vanilla kernel, you may need to use the standard way. Linux fluxster 2.6.25.10-ca #1 SMP Wed Jul 9 18:17:49 EDT 2008 i686 Yes, I see you are using a vanilla kernel. I usually can wait for the Debian package. Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
