Re: Compiling a kernel module. gcc-3.3 vs. gcc-3.4
Why should he not change the link? Changing the link is what I did. Why should the link point to one version of gcc or another? If anything, I would assume that you would want to point it to the version that corrseponds to the version that the kernel was compiled against, if for no other reason that to avoid this very issue. jamie. On Mon, Oct 17, 2005 at 04:10:00PM +0200, Goswin von Brederlow wrote: > James Hansen <[EMAIL PROTECTED]> writes: > > > Thanks for everyone's replies on this. Much appreciated. I've built > > the module using gcc-3.4 and it's inserted into the kernel happily > > enough. (by changing the gcc symlink) > > Don't change the link. Set CC or similar. > > MfG > Goswin > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Compiling a kernel module. gcc-3.3 vs. gcc-3.4
I was having this same problem, even though I had both gcc-3.3 and gcc-3.4 installed. The problem was only in the link of /usr/bin/gcc. You should have gcc-3.4 installed (avvailable in etch), and make sure that the link at /usr/bin/gcc points to /usr/bin/gcc-3.4. Once that is done, modules will build against gcc 3.4 and you will be able to insert them without problem. jamie. On Fri, Oct 14, 2005 at 05:28:02PM +0100, James Hansen wrote: > I'm having problems building and installing a kernel module for the > amd64 port of debian. > > It seems that debian is shipped with gcc-3.3 as it's compiler, but it > looks like the amd64 kernel is built with gcc-3.4 > > (from a syslog message I'm getting when I modprobe a driver) > > Oct 14 16:54:39 localhost kernel: mydriver: version magic > '2.6.8-11-amd64-generic gcc-3.3' should be '2.6.8-11-amd64-generic gcc-3.4' > > Is this actually the case, and if so is this going to continue when this > becomes an official debian distribution? > > Oh, and also what can I do about this? Do I have to fetch gcc-3.4 to > build kernel modules? (Or rebuild my kernel with gcc-3.3) > > Thanks people. > > James > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ssh login delay
is it a pam auth issue? I don't see a pam module that controls that in my /etc/pam.d/ssh, but I'm not sure. jamie. On Mon, Oct 03, 2005 at 11:53:28AM +1000, Hamish Moffatt wrote: > On Mon, Oct 03, 2005 at 12:51:56AM +0200, Gudjon I. Gudjonsson wrote: > > Hi > >This is most probably not an amd64 related problem but could someone > > tell > > me where the delay time for the failed login in ssh is set in Debian. All > > the > > computers I have access to have delay but not my amd64 one. I have looked > > through the internet for 2 hours without success. > > Possibly /etc/login.defs. I'm not sure if that applies to ssh or not. > > Hamish > -- > Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Matlab in sarge amd64 chroot
Matlab comes with a native x86-64 version that I've installed and runs fine on Sarge, for what it's worth. Not sure why you would want to run it 32bit in a chroot, honestly, but I'm sure there's a good reason. If you'd like some hints getting it installed natively, I'd be happy to help. jamie. On Sat, Oct 01, 2005 at 01:33:39AM +0200, Gudjon I. Gudjonsson wrote: > Hi >I wrote a somewhat detailed description on how to set up Matlab in sarge > chroot on Debian testing/unstable amd64. Hope it helps someone. > > Start with: > $sux > #debootstrap --resolve-deps --arch amd64 sarge /var/chroot/sarge-amd64 > http://bach.hpc2n.umu.se/debian-amd64/debian/ > > Add the file /var/chroot/sarge-amd64/etc/apt/sources.list and put the > following line into it > deb http://bach.hpc2n.umu.se/debian-amd64/debian/ stable main contrib non-free > > Change to the new environment > #chroot /var/chroot/sarge-amd64 > > Upgrade the package list > #apt-get upgrade > > Install some packages > #apt-get install libxtst6 libxp6 libxt6 libx11-6 > > Add the following lines to /etc/fstab (in base system) > # amd64 chroot > /home /var/chroot/sarge-amd64/home none bind0 0 > /tmp/var/chroot/sarge-amd64/tmp none bind0 0 > /dev/var/chroot/sarge-amd64/dev none rbind 0 0 > proc/var/chroot/sarge-amd64/proc proc defaults0 0 > > Remount everything and open for X connection from chroot (in base system) > #mount -a > #xhost + > > Hardlink the password and shadow files between the systems > /var/chroot/sarge-amd64/etc# mv passwd passwd.old > /var/chroot/sarge-amd64/etc# mv passwd- passwd-.old > /var/chroot/sarge-amd64/etc# mv group group.old > /var/chroot/sarge-amd64/etc# ln /etc/group group > /var/chroot/sarge-amd64/etc# ln /etc/passwd passwd > /var/chroot/sarge-amd64/etc# ln /etc/passwd- passwd- > > Switch to the chroot system and do > #export DISPLAY=:0 > > Then set up matlab > > Add the following lines to /etc/dchroot.conf > # sarge amd64 chroot > amd64/var/chroot/sarge-amd64 > > Then matlab can be run by typing (in the base system > $dchroot -d amd64 -c matlab > > or by adding the file /usr/local/bin/do_amd64_chroot (in the base system) and > put the following lines into it > #!/bin/sh > ARGS="" > for i in "$@" ; do > ARGS="$ARGS '$i'" > done > exec dchroot -c amd64 -d -q "`basename $0`" "$ARGS" > > Make symbolic link from matlab to do_amd64_chroot > /usr/local/bin# ln -s do_amd64_chroot matlab > > /Gudjon > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installer segfaults.
You don't have to use pen and paper if you use the serial line and minicom. You can configure PXE to output to the serial line with: "serial 0 115200 0x303" as the first line of your configuration file in pxelinux.cfg. The Debian installer initrd I believe is already configured to use the serial line as well. You may get more information from the serial line as well. jamie. On Mon, Sep 26, 2005 at 01:39:40PM +0200, Thomas Alexander Frederiksen wrote: > Hi. > > I've been having a bit of a fight with the AMD64-installer: > > The current sarge installer image segfaults with "swapper not tainted" > as soon as the kernel has been fetched over TFTP. > > The images for etch work without problems. > > I'm guessing that whatever the problem is, it has been resolved after > 2.6.8 was released. > > My main issue is that I actually need sarge, and not etch, as I'm > working on automated installs for production use. > > If it's useful to anyone, I'll try to get the entire message posted as > well, but as I'll have to do it with pen and paper first, it's not > something I'm particularly looking forward to. > > Any good ideas? > > -- > Yours sincerely > Thomas Alexander Frederiksen EasySpeedy ApS > Hard- & Software Technician 33, Hoesterkoebvej > Phone: +45 4594 1401 DK-2970 Hoersholm > Denmark > http://EasySpeedy.com > ___ > Reliable Dedicated Server Hosting > 24/7 Customer Self-Services available > Multiple Linux and BSD distributions > ___ > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
wake-on-lan with Abit KV-80
Hello, all. I've been having trouble getting wake-on-lan (WOL) working with some Abit KV-80 cluster nodes and was wondering if someone on one of these lists had any thoughts. (Maybe useful: sarge 2.6.8-11-amd64-k8). So far, I have only been able to get WOL working (with standard 'magic packets') from a fully powered off state, ie. the power to the board had been killed by turning off the power supply. I have NOT been able to get it to work after powering down the board from a "poweroff" or "shutdown" signal. I've also tried various combinations of the -H/-P/-h options with "shutdown". Does anyone have any idea why this might be the case? I have tried every possible permutation of BIOS and hardware settings to no avail. If WOL works from a completely powered off state, I can only assume that there is something peculiar about how "poweroff" is "powering down" the machine, ie. it's not fully powering down the machine in a way that mimics what happens when the power supply is cut. I guess this isn't a complete surprise. Can someone fill me in on what exactly is the state that the machine ends up in after a "poweroff", and why WOL might not work in that state? Is there a way to coax the machine into a powered off state where it WOULD be receptive to a WOL? Does this have something to do with ACPI? I'm not running acpid. The last thing the console spits out after a poweroff command is "acpi_power_off called", but I'm not certain how to interpret that. As you can imagine, Abit has not been of any help yet. Any help at all would be much appreciated. jamie. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: matlab crashes on amd64
I was having this exact same problem and I can verify that it indeed has to do with the libc6 upgrade from 2.3.2 to 2.3.5. I downgraded libc6 back to 2.3.2 and matlab works again. In fact I downgraded the entire system to stable. jamie. On Tue, Sep 06, 2005 at 01:16:08PM +0200, Gudjon I. Gudjonsson wrote: > Hi >I have the following error using matlab. It doesn't even start, only > giving > the following message: > *** glibc detected *** malloc(): memory corruption: 0x0059dde0 *** > Aborted > I think it has to do with the upgrade from libc6 from 2.3.2 to 2.3.5. > I am using Matlab version 7.0.4. > > Sincerely > Gudjon > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
libc6 issues and libpam-ldap
I was wondering if someone can maybe provide the list with some sort of concise summary of what exactly all of these issues are that keep popping up with libc6 on amd64. I have personally seen lots of issues, and I keep seeing people posting dependencies questions that have to do with libc6. The one that I am currently running into is that while trying to install libpam-ldap on some amd64 etch machines today, I got the following unmet dependency error for libc6: - $ apt-get install libpam-ldap Reading Package Lists... Done Building Dependency Tree... 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. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: libpam-ldap: Depends: libc6 (>= 2.3.5-1) but 2.3.2.ds1-22 is to be installed E: Broken packages - I originally thought this was an issue with libpam-ldap, but the libpam-ldap maintainer says that this is an issue for the amd64 maintainers. Is libpam-ldap supposed to be a newer version than it is? What exactly is going on here? jamie. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sarge amd64 chroot inside sid amd64 problem.
The "--resolve-deps" option seems to have fixed the problem for me. jamie. On Tue, Jul 19, 2005 at 02:00:40PM -0400, Jamie Rollins wrote: > I am getting a very similar message when trying to setup/install lessdisks on > my > amd64 system: > > beginning debootstrap install... > Tue Jul 19 13:50:27 EDT 2005 > I: Retrieving Release > I: Retrieving Packages > I: Validating Packages > I: Checking component main on > http://debian.csail.mit.edu/debian-amd64/debian... > E: Couldn't find these debs: 30628912 > > I have no idea what it means. Please let me know if you figure it out. > > jamie. > > > On Tue, Jul 19, 2005 at 12:41:35PM +0200, Patryk Cisek wrote: > > Hello all, > > > > I'm trying to install Sarge/AMD64 choot system inside my Sid/AMD64 system: > > > > # debootstrap sarge /var/chroot/sarge/ http://amd64.debian.net/debian-amd64 > > I: Retrieving Release > > I: Retrieving Packages > > I: Validating Packages > > I: Checking component main on http://amd64.debian.net/debian-amd64... > > E: Couldn't find these debs: 33024830 > > > > > > What seems to be the problem? > > > > -- > > Regards, > > Patryk Cisek > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sarge amd64 chroot inside sid amd64 problem.
I am getting a very similar message when trying to setup/install lessdisks on my amd64 system: beginning debootstrap install... Tue Jul 19 13:50:27 EDT 2005 I: Retrieving Release I: Retrieving Packages I: Validating Packages I: Checking component main on http://debian.csail.mit.edu/debian-amd64/debian... E: Couldn't find these debs: 30628912 I have no idea what it means. Please let me know if you figure it out. jamie. On Tue, Jul 19, 2005 at 12:41:35PM +0200, Patryk Cisek wrote: > Hello all, > > I'm trying to install Sarge/AMD64 choot system inside my Sid/AMD64 system: > > # debootstrap sarge /var/chroot/sarge/ http://amd64.debian.net/debian-amd64 > I: Retrieving Release > I: Retrieving Packages > I: Validating Packages > I: Checking component main on http://amd64.debian.net/debian-amd64... > E: Couldn't find these debs: 33024830 > > > What seems to be the problem? > > -- > Regards, > Patryk Cisek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
