Re: Sarge NR_CPUS limit of 1 reached. Processor ignored.
On 12/14/05, Lubos Vrbka <[EMAIL PROTECTED]> wrote: > > > Linux 2.6.8-11-amd64-k8 # x86_64 GNU/Linux > > > > Both the processors are detected but one is ignored as said in the boot > > dmesg. > i think you need smp kernel to support both processors, i.e. something > like 2.6.8-11-amd64-k8-smp > Thankyo so much lubos :-) for the quick reply. Is there a way to install the kernel using apt-get?? Also will I have to re-install the packages to support SMP? Thankyou so much kind regards Siju
Re: Sarge NR_CPUS limit of 1 reached. Processor ignored.
Linux 2.6.8-11-amd64-k8 # x86_64 GNU/Linux Both the processors are detected but one is ignored as said in the boot dmesg. i think you need smp kernel to support both processors, i.e. something like 2.6.8-11-amd64-k8-smp regards, -- Lubos [EMAIL PROTECTED]" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Sarge NR_CPUS limit of 1 reached. Processor ignored.
Hi, I have a dual processor amd64 server with 2 AMD Opterons. Installed on it is Sarge Linux 2.6.8-11-amd64-k8 # x86_64 GNU/Linux Both the processors are detected but one is ignored as said in the boot dmesg. -- Processor #0 15:5 APIC version 16 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Processor #1 15:5 APIC version 16 WARNING: NR_CPUS limit of 1 reached. Processor ignored. --- How do I change the NR_CPUS limit to 2? ( if that helps) or how do I get to use both my CPUs? The system was installed from CDROMS Debian GNU/Linux 3.1 r0a _Sarge_ - Official amd64 Binary-1 Debian GNU/Linux 3.1 r0a _Sarge_ - Official amd64 Binary-2 Full Boot dmesg is below :-) Thankyou so much Kind Regards Siju -/var/log/dmesg- Bootdata ok (command line is root=/dev/sda2 ro console=tty0 ) Linux version 2.6.8-11-amd64-k8 ([EMAIL PROTECTED]) (gcc version 3.4.4 20050314 (prerelease) (Debian 3.4.3-13)) #1 Wed Jun 1 01:03:08 CEST 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009f400 (usable) BIOS-e820: 0009f400 - 000a (reserved) BIOS-e820: 000e - 0010 (reserved) BIOS-e820: 0010 - f9ff (usable) BIOS-e820: f9ff - f9fff000 (ACPI data) BIOS-e820: f9fff000 - fa00 (ACPI NVS) BIOS-e820: ff78 - 0001 (reserved) No mptable found. On node 0 totalpages: 1023984 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 1019888 pages, LIFO batch:16 HighMem zone: 0 pages, LIFO batch:1 ACPI: RSDP (v000 ACPIAM) @ 0x000f6d70 ACPI: RSDT (v001 A M I OEMRSDT 0x1611 MSFT 0x0097) @ 0xf9ff ACPI: FADT (v001 A M I OEMFACP 0x1611 MSFT 0x0097) @ 0xf9ff0200 ACPI: MADT (v001 A M I OEMAPIC 0x1611 MSFT 0x0097) @ 0xf9ff0380 ACPI: OEMB (v001 A M I OEMBIOS 0x1611 MSFT 0x0097) @ 0xf9fff040 ACPI: SRAT (v001 A M I OEMSRAT 0x1611 MSFT 0x0097) @ 0xf9ff3b10 ACPI: ASF! (v001 AMIASF AMDSTRET 0x0001 INTL 0x02002026) @ 0xf9ff3c20 ACPI: DSDT (v001 0 0000 0x INTL 0x02002026) @ 0x ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 15:5 APIC version 16 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Processor #1 15:5 APIC version 16 WARNING: NR_CPUS limit of 1 reached. Processor ignored. ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled) ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: Assigned apic_id 2 IOAPIC[0]: apic_id 2, version 17, address 0xfec0, GSI 0-23 ACPI: IOAPIC (id[0x03] address[0xfebff000] gsi_base[24]) IOAPIC[1]: Assigned apic_id 3 IOAPIC[1]: apic_id 3, version 17, address 0xfebff000, GSI 24-27 ACPI: IOAPIC (id[0x04] address[0xfebfe000] gsi_base[28]) IOAPIC[2]: Assigned apic_id 4 IOAPIC[2]: apic_id 4, version 17, address 0xfebfe000, GSI 28-31 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Using ACPI (MADT) for SMP configuration information Checking aperture... CPU 0: aperture @ adfe00 size 32 MB Aperture from northbridge cpu 0 too small (32 MB) No AGP bridge found Built 1 zonelists Kernel command line: root=/dev/sda2 ro console=tty0 Initializing CPU#0 PID hash table entries: 16 (order 4: 256 bytes) time.c: Using 1.193182 MHz PIT timer. time.c: Detected 1991.872 MHz processor. Console: colour VGA+ 80x25 Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) Memory: 4025644k/4095936k available (1586k kernel code, 69528k reserved, 901k data, 124k init) Calibrating delay loop... 3915.77 BogoMIPS Security Scaffold v1.0.0 initialized Capability LSM initialized Mount-cache hash table entries: 256 (order: 0, 4096 bytes) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) CPU: AMD Opteron(tm) Processor 246 stepping 0a Using local APIC NMI watchdog using perfctr0 ENABLING IO-APIC IRQs init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-16, 2-17, 2-18, 2-19, 2-20, 2-21, 2-22, 2-23, 3-0, 3-1, 3-2, 3-3, 4-0, 4-1, 4-2, 4-3 not connected. ..TIMER: vector=0x31 pin1=2 pin2=-1 Using local APIC timer interrupts. Detected 12.449 MHz APIC timer. checking if image is initramfs...it isn't (ungzip failed); looks like an initrd NET: Registered protocol family 16 PCI: Using configuration type 1 mtrr: v2.0 (20020519) ACPI: Subsystem revision 20040326 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (00:00) PCI: Probing PCI hardware (bus 00) ACPI: PCI Interru
Re: How to package SuperCollider (or, whats the deal with multiarch)
Mario Lang wrote:
> In this specific case, that is a very hypothetical thesis... I cant really
> imagine an arch which does say 80bit or 128bit floating point math
> faster than 64bit...
M68K comes to mind, I think that might do 80bit FP faster than it does
64-bit (because the FPU does 80-bit). I'd have to pull out my M68K books...
> I've looked at it, and it is doable. However, I think it would require
> some preprocessor magic, since currently, copying slots is done by
> assignment, which is definitely faster than a memcpy of a struct...
The assignment operator ought to be fairly well optimized. Actually,
memcpy might be, too. Remember, memcpy is a part of the C standard
library; the compiler is perfectly free to implement it any way it
choses --- it need not be a function call. I think GCC might actually do
this.
Let's find out:
[EMAIL PROTECTED]:tmp$ cat test-memcpy.c
#include
int test(int *a, int *b, int *c, int *d) {
memcpy(b, a, sizeof(int));
*c = *d;
return 0;
}
[EMAIL PROTECTED]:tmp$ gcc -O3 test-memcpy.c -c
[EMAIL PROTECTED]:tmp$ objdump -d test-memcpy.o
test-memcpy.o: file format elf64-x86-64
Disassembly of section .text:
:
0: 8b 07 mov(%rdi),%eax
2: 89 06 mov%eax,(%rsi)
4: 8b 01 mov(%rcx),%eax
6: 89 02 mov%eax,(%rdx)
8: 31 c0 xor%eax,%eax
a: c3 retq
And, yep, gcc performs that optimization.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: DualCore Dual-Opteron Board - suggestion?
Lubos Vrbka wrote: > we planned to have dual core dual opteron machine with tyan mobo. > however tyans are not available at the moment (and this situation will > last at least till the end of the year). we were offered supermicro > h8da8 mobo. does anyone have any experience with it, or should we wait > for tyan? I believe thats what's in Yoko.AnimeMusicVideos.Org. Hasn't been put under any real load yet, though the install went fine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: installing a debian source ISO
On Tuesday 13 December 2005 8:02 am, Jo Shields wrote: > Debian isn't a "source based" distro like gentoo - if you really want to > do that, look at "Debian from Scratch" - though I'd not recommend > source-based distributions If you are referring to DFS - Debian from Scratch from John Goerzen, http://people.debian.org/~jgoerzen/dfs/html/ it is not source based either - it simply allows you to boot into a Debian system from CD and provides a collection of packages for installing your system manually from the command line. You still use the same deb's from the same mirrors or the CD. It works very well though and gives you absolute control over the install, and makes a great rescue disk - its not for anyone shy of the command line though. JCM -- John C. Martin - http://www.cs.utk.edu/~jomartin * Please be aware that non-encrypted e-mail is NOT a secured communication * vehicle, and that others may in certain circumstances be able to view its * contents. You should encrypt your e-mail. Disclaimers in your e-mail * signature about confidentiality and designated recipients are silly and * useless. That is what public key encryption is for. * Use my gpg key to ensure privacy - http://www.cs.utk.edu/~jomartin/John.gpg pgpJjW7ns2myl.pgp Description: PGP signature
Re: New install - no sound
Kernels 2.6.12 enable something called dmix by default if your soundcard does not support multiple channels. This would allow rhythmbox and xmms to play sounds at the same time without esd/alsa/your sound server. This is a very cool feature that I sorely missed for a long time. Russ Cook wrote: Oops. I reran alsaconf. That killed a process that was running (I don't know what it was). Afterwards, both XMMS and Rythmbox are functional now. Thank you both for your helpful suggestions. Now that sound is working, I can turn to other problems - like whether to install a 32-bit chroot for programs like Mplayer, Mozilla with Java support, etc. Thanks again. I really appreciate your help. Regards, Russ Russ Cook wrote: Len, In /proc/asound I have a symlink CK804 which links to a directory card0. In card0 I have a file named intel8x0 and a directory named codec97#0. There also other files and directories. Connecting to other audio jacks does not appear to help. Lennart Sorensen wrote: On Mon, Dec 12, 2005 at 07:01:35PM -0600, Russ Cook wrote: I believe I have. As a user, I am a member of the audio group. I can run alsamixer as normal user. Still no sound. I visited this web site for hints - http://xtronics.com/reference/Debian-sound.html and looked at the list of packages it recommended installing. I noticed that I can't install alsa-modules because it isn't available. I am running testing - does that have any bearing on my problem? You only need alsa-modules for 2.4 kernels. 2.6 kernels have alsa drivers already included. Do you have your card listed in /proc/asound/cards? What sound chip is it? If it is an i8x0 ac97 chip, then try plugging the speakers into the mic jack or other jacks and see if it helps, or turn up the headphone volume. If any of that works, you need to go find out which ac97_quirk option you have to pass to the driver for your hardware. Len Sorensen -- Matthew A. Nicholson Digium -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Xvnc crashing
Em Ter, 2005-12-13 às 22:36 -0200, loos escreveu: > I disponibilize debs which I built from > Harald Dunkel modified source (available at the same place) > > http://qt1.iq.usp.br/downloads > > Michel. > > Oops: http://qt1.iq.usp.br/download/ Michel
Re: New install - no sound
Oops. I reran alsaconf. That killed a process that was running (I don't know what it was). Afterwards, both XMMS and Rythmbox are functional now. Thank you both for your helpful suggestions. Now that sound is working, I can turn to other problems - like whether to install a 32-bit chroot for programs like Mplayer, Mozilla with Java support, etc. Thanks again. I really appreciate your help. Regards, Russ Russ Cook wrote: Len, In /proc/asound I have a symlink CK804 which links to a directory card0. In card0 I have a file named intel8x0 and a directory named codec97#0. There also other files and directories. Connecting to other audio jacks does not appear to help. Lennart Sorensen wrote: On Mon, Dec 12, 2005 at 07:01:35PM -0600, Russ Cook wrote: I believe I have. As a user, I am a member of the audio group. I can run alsamixer as normal user. Still no sound. I visited this web site for hints - http://xtronics.com/reference/Debian-sound.html and looked at the list of packages it recommended installing. I noticed that I can't install alsa-modules because it isn't available. I am running testing - does that have any bearing on my problem? You only need alsa-modules for 2.4 kernels. 2.6 kernels have alsa drivers already included. Do you have your card listed in /proc/asound/cards? What sound chip is it? If it is an i8x0 ac97 chip, then try plugging the speakers into the mic jack or other jacks and see if it helps, or turn up the headphone volume. If any of that works, you need to go find out which ac97_quirk option you have to pass to the driver for your hardware. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: New install - no sound
Len, In /proc/asound I have a symlink CK804 which links to a directory card0. In card0 I have a file named intel8x0 and a directory named codec97#0. There also other files and directories. Connecting to other audio jacks does not appear to help. Lennart Sorensen wrote: On Mon, Dec 12, 2005 at 07:01:35PM -0600, Russ Cook wrote: I believe I have. As a user, I am a member of the audio group. I can run alsamixer as normal user. Still no sound. I visited this web site for hints - http://xtronics.com/reference/Debian-sound.html and looked at the list of packages it recommended installing. I noticed that I can't install alsa-modules because it isn't available. I am running testing - does that have any bearing on my problem? You only need alsa-modules for 2.4 kernels. 2.6 kernels have alsa drivers already included. Do you have your card listed in /proc/asound/cards? What sound chip is it? If it is an i8x0 ac97 chip, then try plugging the speakers into the mic jack or other jacks and see if it helps, or turn up the headphone volume. If any of that works, you need to go find out which ac97_quirk option you have to pass to the driver for your hardware. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: New install - no sound
Following your suggestion, I ran gstreamer-properties and set the options to use alsa (I have no idea yet what gstreamer is, my learning curve looks like Mt Everest). Rythmbox now gives the error 'ALSA device "default" is already in use by another program' and also 'Could not pause playback'. Additionally, XMMS no longer works now. I get the error message 'Couldn't open audio'. Thank you for your patience and assistance. Matthew A. Nicholson wrote: Use gstreamer-properties to make gstreamer use alsa. Russ Cook wrote: Partial success. After installing the programs I could find from the referenced list, XMMS now works. Rythmbox 0.8.8 still fails with the error message 'Could not create audio output element; check your setting'. Russ Cook wrote: I believe I have. As a user, I am a member of the audio group. I can run alsamixer as normal user. Still no sound. I visited this web site for hints - http://xtronics.com/reference/Debian-sound.html and looked at the list of packages it recommended installing. I noticed that I can't install alsa-modules because it isn't available. I am running testing - does that have any bearing on my problem? Matthew A. Nicholson wrote: You didn't follow my directions... First make sure you are part of the audio group, you generally should just "be root". adduser mynamehere audio Then run alsamixer as that user and make sure the sound is at a resonable level. If it works as root then it should work as user if you have the right permissions. You should not need to manually run esd. Russ Cook wrote: Udev was already installed - I confirmed with Aptitude. Executing the command 'modprobe snd_intel8x0' made no difference. When I click on volume control under the sound and Video menu item of Gnome, I get the error message "No volume control elements and/or devices found." When I try to play a file using Rythmbox 0.8.8, I get the message "Could not create audio output element; check your settings".When I clicked on the "volume monitor" under the Sound and Video menu item of Gnome, I get the error message "Cannot connect to sound daemon. Please run 'esd' at a command prompt." From a terminal as root, I execute esd, and get a momentary tone sequence. I then tried again to play a file under Rythmbox, and get the same error message "Could not create audio output element; check your settings". This certainly appears to be a configuration issue, but I don't know what the problem is or how to fix it. As always, any help or pointers to references would be greatly appreciated. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Xvnc crashing
I disponibilize debs which I built from Harald Dunkel modified source (available at the same place) http://qt1.iq.usp.br/downloads Michel. Em Seg, 2005-12-12 às 18:21 +0100, Heinrich Rebehn escreveu: > Lennart Sorensen wrote: > > On Mon, Dec 12, 2005 at 04:55:13PM +0100, Heinrich Rebehn wrote: > > > >>are there known Problems with the VNC server? > >> > >>Trying to start > >> > >>$ Xvnc :9 > >> > >>yields "Segmentation fault" in the xterm and > >> > >>Dec 12 16:41:55 bremerhaven kernel: [ 2702.397481] Xvnc[7770]: segfault > >>at ab3827e8 rip 2b1cf54b rsp 7fbc99c0 error 4 > >> > >>on syslog. > >> > >>My machine runs pure "deb http://amd64.debian.net/debian-amd64/ stable > >>main" and vanilla kernel 2.6.14.3 SMP > >>ii vncserver 3.3.7-7 Virtual network computing server > >>software > >> > >>Any thoughts? > > > > > > Well last time I remember reading anything about vnc on amd64, the vnc > > server was known to be broken, while the client worked fine. I have no > > idea if this is still the case or not. By the looks of it, perhaps the > > vnc server is still broken on amd64. > > > > A search of the mailing list archive may shed some light on things. > > > Of course i did search before asking :-) But the posts i found where > over a year old, so i doubted they were still relevant. > http://lists.debian.org/debian-amd64/2004/11/msg00064.html > Seems they still are. > As proposed, i installed the fedora rpm via alien. Works fine.
Re: Flash (Re: OpenOffice-2.0.)
Kalle Kivimaa ha scritto: >How have you managed that? All my attempts to install Flash on my >amd64 laptop have failed miserably... > > I have repacked some 32bit debs. You can now try it from my repository, but please read notes on my website first! -- Alessandro Dal Grande Student In The University Of Padua - Computer Science Linux Registered User #359258 System: GNU/Linux Debian Sid Pure64 on [EMAIL PROTECTED] Chat: Psi ICQ) 150487234 Jabber) [EMAIL PROTECTED] Home: http://v0n0.altervista.org signature.asc Description: OpenPGP digital signature
Re: New install - no sound
Use gstreamer-properties to make gstreamer use alsa. Russ Cook wrote: Partial success. After installing the programs I could find from the referenced list, XMMS now works. Rythmbox 0.8.8 still fails with the error message 'Could not create audio output element; check your setting'. Russ Cook wrote: I believe I have. As a user, I am a member of the audio group. I can run alsamixer as normal user. Still no sound. I visited this web site for hints - http://xtronics.com/reference/Debian-sound.html and looked at the list of packages it recommended installing. I noticed that I can't install alsa-modules because it isn't available. I am running testing - does that have any bearing on my problem? Matthew A. Nicholson wrote: You didn't follow my directions... First make sure you are part of the audio group, you generally should just "be root". adduser mynamehere audio Then run alsamixer as that user and make sure the sound is at a resonable level. If it works as root then it should work as user if you have the right permissions. You should not need to manually run esd. Russ Cook wrote: Udev was already installed - I confirmed with Aptitude. Executing the command 'modprobe snd_intel8x0' made no difference. When I click on volume control under the sound and Video menu item of Gnome, I get the error message "No volume control elements and/or devices found." When I try to play a file using Rythmbox 0.8.8, I get the message "Could not create audio output element; check your settings".When I clicked on the "volume monitor" under the Sound and Video menu item of Gnome, I get the error message "Cannot connect to sound daemon. Please run 'esd' at a command prompt." From a terminal as root, I execute esd, and get a momentary tone sequence. I then tried again to play a file under Rythmbox, and get the same error message "Could not create audio output element; check your settings". This certainly appears to be a configuration issue, but I don't know what the problem is or how to fix it. As always, any help or pointers to references would be greatly appreciated. -- Matthew A. Nicholson Digium -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: yesterdays and todays netinstall cd images
Hello, On Tue, Dec 13, 2005 at 04:40:35PM +1100, Dean Hamstead wrote: > just trying to use yesterdays and todays netboot install > disk images (the 100mb ones), they cant find the modules.dep > file. Yes, the kernel udebs had a bug which was fixed in the upload from yesterday. The unstable daily build from today[1] works, the testing isos from cdimage.debian.org should follow tomorrow. Best regards Frederik Schueler [1] http://amd64.debian.net/debian-installer/daily/ -- ENOSIG signature.asc Description: Digital signature
Re: DualCore Dual-Opteron Board - suggestion?
Great, thanks very much, I'll look through these. On Thu, 2005-12-08 at 10:58 -0800, Elaine Tsiang YueLien wrote: > Here's AMD's bulletin on erratum 122: > > www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/33340.pdf > I have not stressed my system enough to encounter it. > > Here's AMD's latest online revision doc: > http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/25759.pdf > > Errata 118-136 affect dual-core opterons. I came across only 122 in > regards to Linux. > > Elaine > > On Thu, 2005-12-08 at 13:12 -0500, Adam C Powell IV wrote: > > On Wed, 2005-12-07 at 16:02 -0500, Austin Denyer wrote: > > > I believe there is an issue with kernels < 2.6.14-2 with Opteron SMP. > > > That is why I'm running 2.6.14-2 myself. > > > > > > The issue was an AMD errata rather than a bug with the kernel - > > > 2.6.14-2 contained a workaround. > > > > I have a dual/dual machine (265/S940, Tyan S2891) which has trouble > > net-booting, while other dual/single core machines do fine: on the > > dual/dual, dhclient sends a request, the server replies, dhclient > > doesn't seem to get the reply. > > > > Could this kernel issue be causing my problem? > > > > -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Welcome to the best software in the world today cafe! http://www.take6.com/albums/greatesthits.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: install ifort 9.0 with alien...
On Tue, Dec 13, 2005 at 08:39:10PM +0100, fred wrote:
> Hi all,
>
> I attempt to install intel fortran compiler 9.0 amd64/EM64T
> (intel-iforte9-9.0-021.em64t.rpm) with alien.
>
> But alien fails :
> alien intel-iforte9-9.0-021.em64t.rpm
> Package build failed. Here's the log:
> dh_testdir
> dh_testdir
> dh_testroot
> dh_clean -k -d
> dh_installdirs
> dh_installdocs
> dh_installchangelogs
> find . -maxdepth 1 -mindepth 1 -not -name debian -print0 | \
> xargs -0 -r -i cp -a {} debian/intel-iforte9
> dh_compress
> dh_makeshlibs
> objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libcprts.so: File
> format not recognized
> objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libcxa.so: File
> format not recognized
> objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libcxaguard.so: File
> format not recognized
> objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libifcore.so: File
> format not recognized
> objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libifcoremt.so: File
> format not recognized
> objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libifport.so: File
> format not recognized
> objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libunwind.so: File
> format not recognized
> dh_installdeb
> dh_shlibdeps
> /usr/bin/ldd: line 1: /lib/ld-linux.so.2: No such file or directory
> ldd: /lib/ld-linux.so.2 exited with unknown exit code (127)
> dpkg-shlibdeps: failure: ldd on
> `debian/intel-iforte9/opt/intel/fce/9.0/bin/codecov' gave error exit
> status 1
> dh_shlibdeps: command returned error code 256
> make: [binary-arch] Error 1 (ignored)
> dh_gencontrol
> dpkg-gencontrol: error: current build architecture amd64 does not appear
> in package's list (em64t)
> dh_gencontrol: command returned error code 65280
> make: *** [binary-arch] Error 1
> find: intel-iforte9-9.0: No such file or directory
>
> In fact, several *.so file are ascii text :
> cat libunwind.so
> INPUT ( libunwind.so.5 )
>
> I could link these files alien would erase them.
>
> What's wrong ?
Not sure, but redhat does organize their 64bit support rather
differently. Of course alien may just not know about amd64 yet. Of
course on redhat you have 32bit libs too, not just 64bit and some
companies think that doing mixed 32 and 64bit code on amd64 is perfectly
reasonable, which it isn't on a pure 64bit system like amd64 debian.
/lib/ld-linux.so.2 is for 32bit systems, amd64 doesn't use that which
makes it really look like that package requires a mixed architecture
system (perhaps ia32-libs would help since it does contain
/lib/ld-linux.so.2).
Len Sorensen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
install ifort 9.0 with alien...
Hi all,
I attempt to install intel fortran compiler 9.0 amd64/EM64T
(intel-iforte9-9.0-021.em64t.rpm) with alien.
But alien fails :
alien intel-iforte9-9.0-021.em64t.rpm
Package build failed. Here's the log:
dh_testdir
dh_testdir
dh_testroot
dh_clean -k -d
dh_installdirs
dh_installdocs
dh_installchangelogs
find . -maxdepth 1 -mindepth 1 -not -name debian -print0 | \
xargs -0 -r -i cp -a {} debian/intel-iforte9
dh_compress
dh_makeshlibs
objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libcprts.so: File
format not recognized
objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libcxa.so: File
format not recognized
objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libcxaguard.so: File
format not recognized
objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libifcore.so: File
format not recognized
objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libifcoremt.so: File
format not recognized
objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libifport.so: File
format not recognized
objdump: debian/intel-iforte9/opt/intel/fce/9.0/lib/libunwind.so: File
format not recognized
dh_installdeb
dh_shlibdeps
/usr/bin/ldd: line 1: /lib/ld-linux.so.2: No such file or directory
ldd: /lib/ld-linux.so.2 exited with unknown exit code (127)
dpkg-shlibdeps: failure: ldd on
`debian/intel-iforte9/opt/intel/fce/9.0/bin/codecov' gave error exit
status 1
dh_shlibdeps: command returned error code 256
make: [binary-arch] Error 1 (ignored)
dh_gencontrol
dpkg-gencontrol: error: current build architecture amd64 does not appear
in package's list (em64t)
dh_gencontrol: command returned error code 65280
make: *** [binary-arch] Error 1
find: intel-iforte9-9.0: No such file or directory
In fact, several *.so file are ascii text :
cat libunwind.so
INPUT ( libunwind.so.5 )
I could link these files alien would erase them.
What's wrong ?
Thanks in advance.
--
Fred.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to package SuperCollider (or, whats the deal with multiarch)
[EMAIL PROTECTED] (Lennart Sorensen) writes: > On Tue, Dec 13, 2005 at 01:53:04PM +0100, Mario Lang wrote: >> SuperCollider is for some reason I am going to explain below a bit >> strange when it comes to porting it to AMD64: >> >> SC consists of two separate programs, the synthesis server (connects to >> JACK), >> and the language client which executes SCLang code. Both processes >> communicate with each other via UDP (OSC). >> >> For reasons of design and speed vs. space tradeoffs, the language >> *has* to be compiled as a 32bit binary. The 64bit build fails >> at runtime due to pointer size overflows. (if anyone wants to know >> more about it, the main reason for this is that SCLang uses a kind >> of slot-mechanism to hold direct and indirect values all in a 64bit >> double, therefore a 64bit pointer + tag does not fit). > > Briliant. I just love when programers write non portable code for the > sake of performance. :) Well, I've been there, felt like that, but I sort of understand the original decision. realtime audio synthesis is really very demanding on the CPU, so it is very understandable why the author wanted to get the best possible performance for his interpreter language. > What if some future architecture has the ability to run your code > way faster but can't run it because of the clunky code you decided > to write. In this specific case, that is a very hypothetical thesis... I cant really imagine an arch which does say 80bit or 128bit floating point math faster than 64bit... OTOH, I dont really know what I am talking about here, I am not a hardware person. > This has been done many times before and every single time it > eventually became a big problem. > > I wonder how hard it would be to change it to using a struct of a 32 and > a 64bit value instead. I've looked at it, and it is doable. However, I think it would require some preprocessor magic, since currently, copying slots is done by assignment, which is definitely faster than a memcpy of a struct... But I agree, a proper patch which is acceptable by upstream would be favourable. Only to a purist I am afraid, the userbase seems quite happy with the current situation. And upstream is not going to accept a solution which reduces performance for a 32bit address space version. >> OTOH, the synthesis server builds in 64bit mode, and works nicely. It >> actually has to be built 64bit, since it links to JACK, which >> is most probably a 64bit version on an debian amd64 box... >> >> Now, I can build and install this stuff by hand, simply build the >> server on the system as usual, and build the language client in a sid-ia32 >> chroot, do the ld.so.conf magic and symlink sclang. That works >> nicely. >> However, I am kind of wondering how to solve this properly >> when it comes to packaging supercollider? >> I am not up-to-date with how multiarch is exactly ment to work >> these days, would it fit this kind of application? >> If so, whats the proper way to do it, and can this already be done >> with the infrastructure currently in amd64 sid? > > Well best case, the code gets cleaned up to be 64bit clean. > > Worst case you don't package it for 64bit machines. > > Or you can perhaps make the package so that it only builds the "client" > on 32bit systems, and builds the server packages on all systems. These three cases I already worked out, I was looking for case 4 :-), or some ambitioned porter willing to take a look at it and help... -- CYa, Mario -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to package SuperCollider (or, whats the deal with multiarch)
On Tue, Dec 13, 2005 at 01:53:04PM +0100, Mario Lang wrote: > SuperCollider is for some reason I am going to explain below a bit > strange when it comes to porting it to AMD64: > > SC consists of two separate programs, the synthesis server (connects to JACK), > and the language client which executes SCLang code. Both processes > communicate with each other via UDP (OSC). > > For reasons of design and speed vs. space tradeoffs, the language > *has* to be compiled as a 32bit binary. The 64bit build fails > at runtime due to pointer size overflows. (if anyone wants to know > more about it, the main reason for this is that SCLang uses a kind > of slot-mechanism to hold direct and indirect values all in a 64bit > double, therefore a 64bit pointer + tag does not fit). Briliant. I just love when programers write non portable code for the sake of performance. :) What if some future architecture has the ability to run your code way faster but can't run it because of the clunky code you decided to write. This has been done many times before and every single time it eventually became a big problem. I wonder how hard it would be to change it to using a struct of a 32 and a 64bit value instead. > OTOH, the synthesis server builds in 64bit mode, and works nicely. It > actually has to be built 64bit, since it links to JACK, which > is most probably a 64bit version on an debian amd64 box... > > Now, I can build and install this stuff by hand, simply build the > server on the system as usual, and build the language client in a sid-ia32 > chroot, do the ld.so.conf magic and symlink sclang. That works > nicely. > However, I am kind of wondering how to solve this properly > when it comes to packaging supercollider? > I am not up-to-date with how multiarch is exactly ment to work > these days, would it fit this kind of application? > If so, whats the proper way to do it, and can this already be done > with the infrastructure currently in amd64 sid? Well best case, the code gets cleaned up to be 64bit clean. Worst case you don't package it for 64bit machines. Or you can perhaps make the package so that it only builds the "client" on 32bit systems, and builds the server packages on all systems. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: installing a debian source ISO
On Tue, Dec 13, 2005 at 01:19:03PM +, Adam Stiles wrote: > Good on you for installing from source; but I will warn you in advance, it is > not as easy as installing "click and go" spyware-infested applications under > Windows! OTOH, there is something undefinable yet deeply satisfying about > knowing you built it all yourself from source code . just like the way > vegetables from a supermarket never taste as good as the ones you grew on > your own allotment, or other people's babies are never as pretty as yours. Personally I don't consider it good, I consider it silly. :) [snip] > I don't doubt that somebody will have created a boot CD with a working build > environment that can be used for bootstrapping Debian from sources. But you will get the same result building the source packages yourself. If you don't it is a serious bug. So really what would be the point (given I don't believe there is a point to any source based distribution). If you want a source distribution, try looking at the original debian releases (1.x releases). We don't want to go back to that kind of install again. :) Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: installing a debian source ISO
On Tue, Dec 13, 2005 at 09:23:28AM -0300, fernando tear wrote: > I get source debian sarge ISO and i am trying to > install it. > I search it by internet and i found how install a > binary distribution, not a source one. > > where can i find the steps to install a source > distro?? You don't install from source CDs, those you use if you want to rebuild a package with some changes to it. This is fortunately not gentoo. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: New install - no sound
On Mon, Dec 12, 2005 at 07:01:35PM -0600, Russ Cook wrote: > I believe I have. As a user, I am a member of the audio group. I can > run alsamixer as normal user. Still no sound. I visited this web site > for hints - > http://xtronics.com/reference/Debian-sound.html and looked at the list of > packages it recommended installing. I noticed that I can't install > alsa-modules because it isn't available. I am running testing - does > that have > any bearing on my problem? You only need alsa-modules for 2.4 kernels. 2.6 kernels have alsa drivers already included. Do you have your card listed in /proc/asound/cards? What sound chip is it? If it is an i8x0 ac97 chip, then try plugging the speakers into the mic jack or other jacks and see if it helps, or turn up the headphone volume. If any of that works, you need to go find out which ac97_quirk option you have to pass to the driver for your hardware. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: acpi on turion 64
Bruno Ducrot spiffera, alle 18:46, lunedì 12 dicembre 2005 circa: > Try > echo 0 > /proc/acpi/fan/xx/state > to turn it on, and > echo 3 > /proc/acpi/fan/xx/state > to turn it off. simply, it doesn't work... where can I get some logs? ( i'll try enabling a little debug while compiling the kernel...) thanks, anyway... :P -- -gaspa- --- Powered by Debian GNU/Linux and Debian GNU/Hurd -- HomePage: iogaspa.altervista.org ---
Re: installing a debian source ISO
On Tuesday 13 Dec 2005 12:23, fernando tear wrote:
> I get source debian sarge ISO and i am trying to
> install it.
> I search it by internet and i found how install a
> binary distribution, not a source one.
>
> where can i find the steps to install a source
> distro??
Good on you for installing from source; but I will warn you in advance, it is
not as easy as installing "click and go" spyware-infested applications under
Windows! OTOH, there is something undefinable yet deeply satisfying about
knowing you built it all yourself from source code . just like the way
vegetables from a supermarket never taste as good as the ones you grew on
your own allotment, or other people's babies are never as pretty as yours.
First of all, you have to set up a minimal build environment on the target
machine. {You can't do this with just the debian sources disc; get something
like an LFS or gentoo boot CD to use instead. You might even be able to use
Slax if you can find a version which includes GCC}. Partition your HDD, and
mount it somewhere like /target {don't forget to mount other filesystems
under it}. Unless you have stupid amounts of RAM, enable swap space with
swapon. Build a text editor, GCC, a kernel, all the Debian packaging tools,
the base system and lilo -- all with a PREFIX that will place them under the
target system. NB: If the GCC version on your bootdisc is older than the
source you have, build the new GCC first and use it to build everything else.
Chroot into the target and set up /etc/fstab and /etc/lilo.conf.
Run /sbin/lilo. *EXIT FROM THE CHROOT*, remove the boot CD and reboot into
the target system.
If that sounds too complicated, start installing a very minimal base system
from a Debian binary install CD and complete it with sources compiled locally
from your sources CD.
If that still sounds too complicated, cut your losses and download the binary
ISO. Is there a good reason you can't use netinstall? Even with only a
512Kb internet connection, it's still reasonably quick.
I don't doubt that somebody will have created a boot CD with a working build
environment that can be used for bootstrapping Debian from sources.
--
AJS
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Xvnc crashing
Lennart Sorensen wrote: > Well last time I remember reading anything about vnc on amd64, the vnc > server was known to be broken, while the client worked fine. I have no > idea if this is still the case or not. By the looks of it, perhaps the > vnc server is still broken on amd64. > > A search of the mailing list archive may shed some light on things. http://lists.debian.org/debian-amd64/2005/10/msg00657.html With the unofficial packages from that, it worked for me. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: installing a debian source ISO
fernando tear wrote: I get source debian sarge ISO and i am trying to install it. I search it by internet and i found how install a binary distribution, not a source one. where can i find the steps to install a source distro?? greetings fernando Debian isn't a "source based" distro like gentoo - if you really want to do that, look at "Debian from Scratch" - though I'd not recommend source-based distributions --Jo Shields -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
How to package SuperCollider (or, whats the deal with multiarch)
Hi. SuperCollider is for some reason I am going to explain below a bit strange when it comes to porting it to AMD64: SC consists of two separate programs, the synthesis server (connects to JACK), and the language client which executes SCLang code. Both processes communicate with each other via UDP (OSC). For reasons of design and speed vs. space tradeoffs, the language *has* to be compiled as a 32bit binary. The 64bit build fails at runtime due to pointer size overflows. (if anyone wants to know more about it, the main reason for this is that SCLang uses a kind of slot-mechanism to hold direct and indirect values all in a 64bit double, therefore a 64bit pointer + tag does not fit). OTOH, the synthesis server builds in 64bit mode, and works nicely. It actually has to be built 64bit, since it links to JACK, which is most probably a 64bit version on an debian amd64 box... Now, I can build and install this stuff by hand, simply build the server on the system as usual, and build the language client in a sid-ia32 chroot, do the ld.so.conf magic and symlink sclang. That works nicely. However, I am kind of wondering how to solve this properly when it comes to packaging supercollider? I am not up-to-date with how multiarch is exactly ment to work these days, would it fit this kind of application? If so, whats the proper way to do it, and can this already be done with the infrastructure currently in amd64 sid? -- CYa, Mario -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
installing a debian source ISO
I get source debian sarge ISO and i am trying to install it. I search it by internet and i found how install a binary distribution, not a source one. where can i find the steps to install a source distro?? greetings fernando ___ 1GB gratis, Antivirus y Antispam Correo Yahoo!, el mejor correo web del mundo http://correo.yahoo.com.ar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Flash (Re: OpenOffice-2.0.)
v0n0 <[EMAIL PROTECTED]> writes: > This fd openoffice...I'm running even Firefox with Flash without > chroot!!! How have you managed that? All my attempts to install Flash on my amd64 laptop have failed miserably... -- * Sufficiently advanced magic is indistinguishable from technology (T.P) * * PGP public key available @ http://www.iki.fi/killer * -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Synaptic segfaulting
Interesting. I don't manage to update apt to 0.6.43; it tries toremove synaptic, because it wants to replace libsigc++- 2.0-0c2 withlibsigc++-2.0-0c2a...I guess this will "sort itself" in a few days...?, I'm waiting since 3/4 weeks for libapt-pkg-libc6 updating:)Giulio
