kernel compile.again.
Greetings. Still trying to understand why I can't seem to run any kernels I compile. Been trying since 2.6.17 on my new amd64-X2 and since then the only kernel that'll boot is a 2.6.16-2-amd64-k8-smp. I've tried using the debian amd64 kernel conifig on most kernels as well, with no joy. Kind of at the end of the rope here with ideas. NOW I'm beginning to think it's the compiler, 4.1? I've noticed that 2.6.16-2 is compiled with 4.0. How do I specify gcc 4.0 instead of 4.1 to compile a kernel? Thanks for any support. Chris W. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile.again.
HiI had the same problem, but if I remember well it's a known issue with gcc-4.x and kernel-2.6.xSwithching to gcc-2.95 should remove the problem. Try with a symbolic link to the gcc you want to use.I am running amd64 on a dual opteron proliant server and got several depedencies problems with libncurses5 when trying to recompile, even if I switch. 2006/10/25, C_Wakefield [EMAIL PROTECTED]: Greetings.Still trying to understand why I can't seem to run any kernels I compile.Been trying since 2.6.17 on my new amd64-X2 and since then the only kernelthat'll boot is a 2.6.16-2-amd64-k8-smp.I've tried using the debian amd64 kernel conifig on most kernels as well, with no joy.Kind of at the end of the rope here with ideas.NOW I'm beginning to thinkit's the compiler, 4.1?I've noticed that 2.6.16-2 is compiled with 4.0.How do I specify gcc 4.0 instead of 4.1 to compile a kernel? Thanks for any support.Chris W.--To UNSUBSCRIBE, email to [EMAIL PROTECTED]with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile.again.
On Wednesday 25 October 2006 09:08, C_Wakefield wrote: Greetings. Still trying to understand why I can't seem to run any kernels I compile. Been trying since 2.6.17 on my new amd64-X2 and since then the only kernel that'll boot is a 2.6.16-2-amd64-k8-smp. I've tried using the debian amd64 kernel conifig on most kernels as well, with no joy. Kind of at the end of the rope here with ideas. NOW I'm beginning to think it's the compiler, 4.1? I've noticed that 2.6.16-2 is compiled with 4.0. How do I specify gcc 4.0 instead of 4.1 to compile a kernel? I would expect it to be part of the alternatives mechanism, but it seems its not. there is a /etc/alternatives/cc file, but its a link to /usr/bin/gcc. /usr/bin/gcc is again a link, this time to /usr/bin/gcc-4.1 in my case. I have successfully compiled sources that needed gcc-4.0 by changing the links of /usr/bin/gcc and /usr/bin/g++ to point to the 4.0 version. I guess you can try the same brute trick. Dimitris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: oowriter not recognising graphics in 64 bit
Hi I can confirm that behaviour. Try to open the document with a chrooted oowriter. Then the picture should appear and you can then save it in odt format and then open it with the amd64 version. That worked for me at least. I was so happy for the bugs that had disappeared so I did not consider this as a bug:) /Gudjon On 2006-10-24 15:03, Clive Menzies wrote: Hi I've been running OOo 2.0 in a 32bit chroot for some time now and it works fine. Our letterhead has a graphic logo which shows and prints OK. I installed the 64bit OOo packages from sid recently and they too seemed work fine. However, in trying to print an invoice today, I realise the logo is missing; it is neither shown on screen nor does it print. I have another sid system with the 32bit packages in a chroot where the logo shows up fine on the invoices. If I save a document under a different name within the 64bit system and then look at it in 32bit chroot there is no logo but the original doc still has it. The logo was originally created in a word template. Before file a bug report, I wonder if anyone else has seen this? Alternatively, does anyone have a view on what could be causing this? Thanks Clive -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile.again.
On Wednesday 25 October 2006 09:57, Raffaele Morelli wrote: Hi I had the same problem, but if I remember well it's a known issue with gcc-4.x and kernel-2.6.x Swithching to gcc-2.95 should remove the problem. Try with a symbolic link to the gcc you want to use. I am running amd64 on a dual opteron proliant server and got several depedencies problems with libncurses5 when trying to recompile, even if I switch. well, i've been compiling my 2.6 kernels with gcc-4.1, no problem at all, using a dual core athlon. As far as the libncurses thing is concerned, you should pull the development package of libncurses (libncurses5-dev) before trying a make menuconfig. Dimitris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile.again.
On Wed, 2006-10-25 at 02:45 -0700, C_Wakefield wrote: On Wednesday 25 October 2006 01:05, you wrote: On Wednesday 25 October 2006 09:08, C_Wakefield wrote: Greetings. Still trying to understand why I can't seem to run any kernels I compile. Been trying since 2.6.17 on my new amd64-X2 and since then the only kernel that'll boot is a 2.6.16-2-amd64-k8-smp. I've tried using the debian amd64 kernel conifig on most kernels as well, with no joy. Kind of at the end of the rope here with ideas. NOW I'm beginning to think it's the compiler, 4.1? I've noticed that 2.6.16-2 is compiled with 4.0. How do I specify gcc 4.0 instead of 4.1 to compile a kernel? I would expect it to be part of the alternatives mechanism, but it seems its not. there is a /etc/alternatives/cc file, but its a link to /usr/bin/gcc. /usr/bin/gcc is again a link, this time to /usr/bin/gcc-4.1 in my case. I have successfully compiled sources that needed gcc-4.0 by changing the links of /usr/bin/gcc and /usr/bin/g++ to point to the 4.0 version. I guess you can try the same brute trick. Dimitris Thanks for the idea. I just compiled 2.6.18.1 with .config from my only running debian kernel: 2.6.16-2-amd64-k8-smp with gcc-4.0 using the symlink in /etc/alternatives/gcc. Again, no joy. My next, is to use gcc-2.95, but not sure if it that's a good idea, given it's age? What is odd, also, is that debian linux-images: 2.6.18-1-amd64 and 2.6.17-2-amd64 won't boot my machine either!Thanks for the replies, 2.95 has no 64-bit support. If you want a 32-bit kernel, then this probably isn't the right list. What precisely is happening when you try boot your system? Do you have some some specific error or diagnostic information that could be used to find what the issue is? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bind mounts and shutdown sequence
jmt [EMAIL PROTECTED] writes: On Thursday 19 October 2006 15:33, Stephen Olander Waters wrote: I am running sid with amd64 architecture. I also have a chroot called /x86 to run openoffice, acroread, boinc, etc. In my /etc/fstab, I have several bind mounts into /x86. When I run shutdown -h now or shutdown -r now, the shutdown sequence stops with an error after stopping all the processes. I have to use Alt +SysRq to reboot. However, the shutdown sequence works OK if I manually unmount the bind mounts before executing shutdown. Is anyone else experiencing this problem? I can file a bug once I figure out what script is dying (it's hard for me to tell because the machine is unusable except Alt+SysRq!) Thanks so much, -s Are you sure you don't run the shutdown in the chroot ? I never tried that, because I think I could expect precisely this kind of troubles ... jmt Shouldn't make a difference. Afaik shutdown just tells the init to change runlevels through the unix domain socket. If that is bind mounted inside the chroot that still tells the init outside to do its work. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bind mounts and shutdown sequence
On Thursday 19 October 2006 15:33, Stephen Olander Waters wrote: I am running sid with amd64 architecture. I also have a chroot called /x86 to run openoffice, acroread, boinc, etc. In my /etc/fstab, I have several bind mounts into /x86. When I run shutdown -h now or shutdown -r now, the shutdown sequence stops with an error after stopping all the processes. I have to use Alt +SysRq to reboot. However, the shutdown sequence works OK if I manually unmount the bind mounts before executing shutdown. Is anyone else experiencing this problem? I can file a bug once I figure out what script is dying (it's hard for me to tell because the machine is unusable except Alt+SysRq!) I've seen this sometimes. I have set up a chroot on my laptop a few times and on one of the installations, I had this problem. Unfortunately I've now wiped that system and the two I have now don't exhibit that behaviour. I wrote a short script to unmount the shares. This was using cifs which is where I thought the problem lay. Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile.again.
On Wed, Oct 25, 2006 at 10:57:47AM +0100, Jo Shields wrote: What is odd, also, is that debian linux-images: 2.6.18-1-amd64 and 2.6.17-2-amd64 won't boot my machine either!Thanks for the replies, What precisely is happening when you try boot your system? Do you have some some specific error or diagnostic information that could be used to find what the issue is? It's good to see other people have the same problem with anything later than 2.6.16 :) In my case the kernel just stops after: Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered in 2.6.16.24 the next lines would be the RTC driver, agpgart and serial with my monolitic kernel config. -- When you do things right, people won't be sure you've done anything at all. Daniel Tryba -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile.again.
On Wed, Oct 25, 2006 at 02:45:46AM -0700, C_Wakefield wrote: Thanks for the idea. I just compiled 2.6.18.1 with .config from my only running debian kernel: 2.6.16-2-amd64-k8-smp with gcc-4.0 using the symlink in /etc/alternatives/gcc. Again, no joy. My next, is to use gcc-2.95, but not sure if it that's a good idea, given it's age? What is odd, also, is that debian linux-images: 2.6.18-1-amd64 and 2.6.17-2-amd64 won't boot my machine either! If you compile 2.6.16 yourself, does that boot? Maybe a change in 2.6.17 broke support for your mainboard. Which board do you have? Which bios version? What chipset does it use? -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bind mounts and shutdown sequence
On Mon, 2006-10-23 at 10:30 -0500, Stephen Olander Waters wrote: On 10/19/06, Stephen Olander Waters [EMAIL PROTECTED] wrote: I am running sid with amd64 architecture. I also have a chroot called /x86 to run openoffice, acroread, boinc, etc. In my /etc/fstab, I have several bind mounts into /x86. When I run shutdown -h now or shutdown -r now, the shutdown sequence stops with an error after stopping all the processes. I have to use Alt +SysRq to reboot. However, the shutdown sequence works OK if I manually unmount the bind mounts before executing shutdown. Is anyone else experiencing this problem? I can file a bug once I figure out what script is dying (it's hard for me to tell because the machine is unusable except Alt+SysRq!) Here is the error message I'm getting --- Asking non-system processes to terminate..done Killing non-system processes ...error: '/etc/init.d/rc' exited outside the expected codeflow. INIT: no more processes in this runlevel --- Here is my /etc/fstab --- # x86 mounts /home /x86/home none bind0 0 /tmp/x86/tmp none bind0 0 /dev/x86/dev none bind0 0 sysfs /x86/sys sysfs none0 0 proc/x86/proc proc defaults0 0 I found a workaround. I don't know if it counts as a fix but it does work. Change /x86/sys to a bind mount and shutting down works. /sys /x86/sys bind none0 0 HTH, -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[CORRECTION] Re: bind mounts and shutdown sequence
CORRECTION Here is my /etc/fstab --- # x86 mounts /home /x86/home none bind0 0 /tmp/x86/tmp none bind0 0 /dev/x86/dev none bind0 0 sysfs /x86/sys sysfs none0 0 proc/x86/proc proc defaults0 0 I found a workaround. I don't know if it counts as a fix but it does work. Change /x86/sys to a bind mount and shutting down works. /sys /x86/sys bind none0 0 Of course, that should be: /sys /x86/sys none bind0 0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: when will nvidai-glx and nvidia-kernel-source hit etch? {Scanned} {Scanned} {Scanned}
On Tue, Oct 24, 2006 at 12:19:40PM -0500, Henry Hollenberg wrote: So gdm is looking for /usr/X11R6/bin/X but my xserver now is: /usr/X11R6/bin/Xorg when I try and run this binary by hand I see these errors: (==) Using config file: /etc/X11/xorg.conf Error: API mismatch: the NVIDIA kernel module has the version 1.0-8774, but this X module has the version 1.0-8776. Please make sure that the kernel module and all NVIDIA driver components have the same version. (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! Please ensure (EE) NVIDIA(0): that there is a supported NVIDIA GPU in this system, and (EE) NVIDIA(0): that the NVIDIA device files have been created properly. (EE) NVIDIA(0): Please consult the NVIDIA README for details. (EE) NVIDIA(0): *** Aborting *** (EE) Screen(s) found, but none have a usable configuration. Ok, I have a Leadtek PX6800GT video card installed in this system so I don't think the supported NVIDIA GPU line is the issue must be the API mismatchnot sure how that would have happened. Think I'll cc Randall Donald the nvidia maintainer andy:/usr/X11R6/bin# lspci :01:00.0 VGA compatible controller: nVidia Corporation NV40 [GeForce 6800 Ultra/GeForce 6800 GT] (rev a2) I'll give kdm a whirl and see if it does better than gdm... Try 'modprobe nvidia' to see if you can load the kernel module. Might be worth appending 'nvidia' to /etc/modules to make sure it is always loaded at boot. If you can't load the module then it probably isn't compiled for the current kernel yet. To fix that do: m-a -t prepare m-a -t a-i nvidia modprobe nvidia -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Kernel 2.6.18: agpgart-modules ???
Hi folks, I am missing some agpgart-modules in the kernel-sources. In earlier days, I could build them as modules, now I only find intel-agp, sis-agp and ali-agp. It is wiered, as on another computer, I can see the others and activate them. I supposed, it has something to do with the .config in the /usr/src/linux-directory, so I made a fresh installation of the related packages (sources and header-files) How can I see them again ? Is this related on the hardware the running kernel does see ? Are there some temoporeral files I should delete ? I am running the headers and image *-2.6.18-1-amd64. Is there a difference between 32-bit and 64-bit ? (I have no second 64-bit system available) Thanks for help ! Regards Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.6.18: agpgart-modules ???
On Wed, 2006-10-25 at 16:14 +0200, Hans-J. Ullrich wrote: I am missing some agpgart-modules in the kernel-sources. In earlier days, I could build them as modules, now I only find intel-agp, sis-agp and ali-agp. There is only one AGP module for the AMD64 architecture cleverly named amd64-agp -- however it is built-in on Debian kernels. I assume this is because it's built into all AMD64 CPUs or is required for AMD64 northbridges. -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: when will nvidai-glx and nvidia-kernel-source hit etch? {Scanned} {Scanned} {Scanned}
On Tue, Oct 24, 2006 at 11:24:13AM -0500, Henry Hollenberg wrote: OK, I added some unstable lines to my sources.list and ran apt-get update: deb http://cudlug.cudenver.edu/debian/ testing main contrib non-free deb-src http://cudlug.cudenver.edu/debian/ testing main contrib non-free deb http://cudlug.cudenver.edu/debian/ unstable main contrib non-free deb-src http://cudlug.cudenver.edu/debian/ unstable main contrib non-free then: apt-get -f install which installed: ii linux-image-2.6.18-1-amd642.6.18-2Linux 2.6.18 image on AMD64 apt-get -t unstable install nvidia-kernel-common apt-get -t unstable install nvidia-kernel-source apt-get -t unstable install module-assistant m-a a-i nvidia apt-get -t unstable install nvidia-glx And somehow the 2.6.18 kernel headers got installed not sure when or how: ii linux-kernel-headers 2.6.18-3Linux Kernel Headers for development linux-kernel-headers provides /usr/include/linux for compiling user space programs. It has nothing to do with your running kernel and the version doesn't really matter. The headers for compiling kernel modules involves linux-headers-2.6.18 or similar. I checked /etc/X11/XF86Config-4 and it looked ok according to Andrew Schulman's instructions. I also added my user to group video in case that was needed also according to Schulman. I am still gettting a gdm startup error: Failed to start the X server GDM: Xserver not found: /usr/X11R6/bin/X :0 Error: Command could not be executed! Please install the Xserver or correct the GDM configuration and restart GDM Maybe your gdm is misconfigured since I think it should be /usr/bin/X Assuming the X symlink is actually installed and pointing at Xorg. Is xserver-xorg installed? -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel compile.again.
This is exactly my error as well. Working on some diag... Thanks, Chris W. On Wednesday 25 October 2006 04:22, Daniel Tryba wrote: On Wed, Oct 25, 2006 at 10:57:47AM +0100, Jo Shields wrote: What is odd, also, is that debian linux-images: 2.6.18-1-amd64 and 2.6.17-2-amd64 won't boot my machine either!Thanks for the replies, What precisely is happening when you try boot your system? Do you have some some specific error or diagnostic information that could be used to find what the issue is? It's good to see other people have the same problem with anything later than 2.6.16 :) In my case the kernel just stops after: Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered in 2.6.16.24 the next lines would be the RTC driver, agpgart and serial with my monolitic kernel config. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
