Re: Previous packages?
Goswin von Brederlow wrote: David Liontooth <[EMAIL PROTECTED]> writes: Is it possible to revert to a previous package in our current repository system? The latest etherape (0.9.0-8) has a bug (277703) that makes it unusable on my i686 and amd64 machines. On the i686 I can get the previous package from http://snapshot.debian.net Of course these things typically happen when you need the app the most -- our network was mysteriously down and I couldn't use the tool I was familiar with to see what was happening! Cheers, Dave If it was a (very) recent upload the old deb will be in pure64/old/... with the same subdirs as the new one in pure64/pool. But since alioths disk is nearly full I clean that often. MfG Goswin Thanks, that's very helpful. Does anyone else do this? Goswin seems to keep them for just a day or two. Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debconf and other outdated packages
Great! Is it possible that some packages are still missing? For instance the X server is -8, whereas pure64 has -10. When I upgraded pure64 to gcc-3.4 I had to leave the -10 packages installed because they have some important fixes. Today I was trying to find out why wxwidgets2.5's compilation is failing (see below), but I couldn't readily install the -dev packages I need to compile it because I don't have the X's -dev packages corresponding to the binaries I've installed. Maybe I should also install X's -dev packages from pure64 for now. On a second look to wxwidgets2.5 compilation's log in gcc-3.4/buildd-logs it looks like it's downloading the build dependencies from pure64, as it's actually fetching the -10-dev X packages. Anyway, in case somebody knows before hand about this problem, the error message is: checking for strcasecmp() in string.h... no checking for strcasecmp() in strings.h... no configure: error: No case-insensitive string comparison function found. make: *** [configure-gtk-shared-stamp] Error 1 The log is from Feb, 2nd. As usual, thanks a lot. Andreas Jochens wrote: On 05-Feb-09 21:23, Javier Kohen wrote: Hi, I was wondering why some packages which are successfully compiled by buildd for gcc-3.4 don't make it to the pool. One particular case is debconf 1.4.45, which fixes some awful looking error messages when running dpkg. Another is the Is there always manual intervention involved in moving the packages to the pool? I'm afraid I don't know how Debian works on that level. Thanks for the report. Usually there is almost no manual intervention necessary. However, something went wrong with the archive's source update and also with the upload of some packages. I just rebuilt and uploaded quite a few missing package versions. The debconf version 1.4.45 is now available in the archive. Regards Andreas Jochens -- Javier Kohen <[EMAIL PROTECTED]> ICQ: blashyrkh #2361802 Jabber: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Previous packages?
David Liontooth <[EMAIL PROTECTED]> writes: > Is it possible to revert to a previous package in our current > repository system? > > The latest etherape (0.9.0-8) has a bug (277703) that makes it > unusable on my i686 and amd64 machines. > On the i686 I can get the previous package from http://snapshot.debian.net > > Of course these things typically happen when you need the app the most > -- our network was mysteriously down and I couldn't use the tool I was > familiar with to see what was happening! > > Cheers, > Dave If it was a (very) recent upload the old deb will be in pure64/old/... with the same subdirs as the new one in pure64/pool. But since alioths disk is nearly full I clean that often. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Previous packages?
Is it possible to revert to a previous package in our current repository system? The latest etherape (0.9.0-8) has a bug (277703) that makes it unusable on my i686 and amd64 machines. On the i686 I can get the previous package from http://snapshot.debian.net Of course these things typically happen when you need the app the most -- our network was mysteriously down and I couldn't use the tool I was familiar with to see what was happening! Cheers, Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Oracle won't cooperate
On Thu, 2005-02-10 at 16:48 -0800, Joseph Pelle wrote: > Did anyone get this (Oracle) working? Which Oracle download did you use? I > tried the linux x86-64, but I can't even get the runInstaller to work. You have to edit the runInstaller and associated programs before they will run. I was unable to get the Java installer to run. Note to Oracle: Java is not portable if you link in a bunch of 32-bit JNI garbage. The only way I was able to get this to work was to install Oracle on a RedHat system and transplant the installation onto a proper Debian system. -jwb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Oracle won't cooperate
Did anyone get this (Oracle) working? Which Oracle download did you use? I tried the linux x86-64, but I can't even get the runInstaller to work. -Original Message- From: Jeffrey W. Baker [mailto:[EMAIL PROTECTED] Sent: January 7, 2005 9:26 AM To: debian-amd64@lists.debian.org Subject: Re: Oracle won't cooperate On Thu, 2005-01-06 at 22:46 -0500, Javier Kohen wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > I fear I'm suggesting the obvious, but do you have the locales package > installed in the chroot? Yeah, I have the chroot configured for the same locales as the main system (and the system with the X server, too). I'm fairly certain the locale message is completely spurious and misleading. -jwb -- 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: Anyone tried the ASUS A8V-E Deluxe?
On Thursday, 10 February 2005 01:01, Giacomo Mulas wrote: > On Wed, 9 Feb 2005, Wesley J Landaker wrote: > > I have this board, I'm still working on migrating everything over > > to this system (it's going to be my new primary system on my desk). > > May I ask you, and the list, a question (well, a couple) then: how > much RAM do you have installed? I have 4Gb on it, but I was unable to > use it all, because apparently some addressing space (about 400Mb) is > reserved for the southbridge. I found an option in the bios (the > documentation is terse on it, to say the least) which claims to > "remap" memory to make it all available. I tried enabling that, but > then some drivers do not work well (e.g. nvidia, but I can live with > it) or do not work at all (e.g. sk98lin, and this crashes the > computer). Currently, for the sake of stability, I left remapping > disabled in the bios and everything works like a charm, apart from > the missing 400Mb, but this is not copletely satisfactory. Anybody > else went through this? Suggestions? I have 1GB, and I have all of my RAM available minus the size of the kernel (1023816 kB total reported by /proc/meminfo). I'm using the binary nvidia drivers for x86_64, the sysconnect sk98lin driver for network. I'm actually curious what BIOS option you're talking about, as I don't see anything like what you were describing listed either in the BIOS or in the A8V-E Dexlue motherboard manual. Anyway, 400MB seems like an incredible (and strange) amount of address space to reserve for ISA compatibility--it seems like it must be for something else. -- Wesley J. Landaker <[EMAIL PROTECTED]> OpenPGP FP: 4135 2A3B 4726 ACC5 9094 0097 F0A9 8A4C 4CD6 E3D2 pgp48T4wMtBZf.pgp Description: PGP signature
Re: Re: Another go at the Abit AV8 Pro 1.1
HI, I understand you are having problems with the Abit AV8 motherboard paired with the AMD 64 3400+ cpu, well, for one obvious problem I see is the motherboard and cpu mismatch. The Abit AV8 motherboard is a 939 socket, the AMD 3400+ is a 754 socket, while the cpu may fit on the mobo you won't be able to use the dual channel memory feature and I suspect the mismatch would cause other problems as well. TigerDirect is also selling the motherboard combo and fail to mention the socket for the cpu. One would assume the cpu is also a 939 pin but it isn't. the dual channel memory PC3200 latency and voltage must also match your mobo.. I am searching the internet for a good 939 mobo, and Abit AV8 and the Asus A8V get high marks. hope this helps some Gary No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.6 - Release Date: 2/7/2005
Re: quake3
just a side note. I've had this problem in the 32bit debian unstable the echo > /proc line fixed it there as well. I also had the problem where the sound would re-disappear every now and then as well. On Thu, 2005-02-10 at 14:35 -0800, tony mancill wrote: > Hi - I had this same problem with Enemy Territory, and had to google for > quite a bit before I found something that worked for me. > > Some articles referenced loading my sound modules with the option > "mmap_valid=1". This didn't change anything for me, but allegedly has > worked for others. Here's an example of what to add to > /etc/modutils/alsa-base: > >alias snd-card-0 snd-via82xx >options snd-via82xx mmap_valid=1 > > Another article recommended this, which did do the trick: > > echo "et.x86 0 0 direct" > /proc/asound/card0/pcm0p/oss > > Or if you use systune, add this line to /etc/systune.conf: > > /proc/asound/card0/pcm0p/oss:et.x86 0 0 direct > > In both cases, you'll need to change the "et.x86" to the name of the > executable that runs quake3. > > If I can locate them, I'll follow up for the post and provide references > for the original sources for this info. > > FWIW, ET sound worked for me without these changes for a while, and then > went away. I believe it was due to updating ALSA packages. (It's tough > to say when you track unstable on a daily basis.) Also FWIW, I have to > disable the GL extensions when I run ET in 64-bit or else the textures > flicker between solid black and the normal texture. The amazing thing is > that the AMD64 is just about fast enough that the game remains playable, > even doing all of the rendering in software... > > HTH, > tony > > On Thu, February 10, 2005 14:22, Philippe said: > > hello > > > > i'm just installing quake3 on sid pure64. > > i think quake3 was not able to find libGL in /emul/ so i copy it in > > quake3 dir > > it's work but now I have no sound > > > > is there a solution pour this problem ? > > > > --- sound initialization --- > > Could not mmap dma buffer PROT_WRITE|PROT_READ > > trying mmap PROT_WRITE (with associated better compatibility / less > > performance code) > > /dev/dsp: Input/output error > > Could not mmap /dev/dsp > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: chroot and X
On Thu, Feb 10, 2005 at 02:11:52PM -0800, Theodore Kisner wrote: > On Thursday 10 February 2005 13:44, [EMAIL PROTECTED] wrote: > > xterm from my 64bit XFce: "could not open Display :0.0. > > Do you have /tmp bind mounted in the chroot? > > For example, in my (64bit) fstab I have: > > /tmp/data/ia32-root/tmp nonebind0 0 I think there is nothing pointing to the chroot in fstab ... The Knoppix ( chroot ) has their own /tmp and their own fstab ... I think that is the reason. I'll try it. Salute, -- Gruß Ralf Springwald Und die See wird allen neue Hoffnung bringen, sowie der Schlaf die Träume bringt, daheim (Christoph Kolumbus) -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: quake3
Hi - I had this same problem with Enemy Territory, and had to google for quite a bit before I found something that worked for me. Some articles referenced loading my sound modules with the option "mmap_valid=1". This didn't change anything for me, but allegedly has worked for others. Here's an example of what to add to /etc/modutils/alsa-base: alias snd-card-0 snd-via82xx options snd-via82xx mmap_valid=1 Another article recommended this, which did do the trick: echo "et.x86 0 0 direct" > /proc/asound/card0/pcm0p/oss Or if you use systune, add this line to /etc/systune.conf: /proc/asound/card0/pcm0p/oss:et.x86 0 0 direct In both cases, you'll need to change the "et.x86" to the name of the executable that runs quake3. If I can locate them, I'll follow up for the post and provide references for the original sources for this info. FWIW, ET sound worked for me without these changes for a while, and then went away. I believe it was due to updating ALSA packages. (It's tough to say when you track unstable on a daily basis.) Also FWIW, I have to disable the GL extensions when I run ET in 64-bit or else the textures flicker between solid black and the normal texture. The amazing thing is that the AMD64 is just about fast enough that the game remains playable, even doing all of the rendering in software... HTH, tony On Thu, February 10, 2005 14:22, Philippe said: > hello > > i'm just installing quake3 on sid pure64. > i think quake3 was not able to find libGL in /emul/ so i copy it in > quake3 dir > it's work but now I have no sound > > is there a solution pour this problem ? > > --- sound initialization --- > Could not mmap dma buffer PROT_WRITE|PROT_READ > trying mmap PROT_WRITE (with associated better compatibility / less > performance code) > /dev/dsp: Input/output error > Could not mmap /dev/dsp -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: quake3
Hi, On Thu, Feb 10, 2005 at 11:22:54PM +0100, Philippe wrote: > is there a solution pour this problem ? > > --- sound initialization --- > Could not mmap dma buffer PROT_WRITE|PROT_READ > trying mmap PROT_WRITE (with associated better compatibility / less > performance code) > /dev/dsp: Input/output error > Could not mmap /dev/dsp you need both oss support and 32bit ioctl. Presuming you setup your system to use alsa, add the following to your /etc/modules.conf: snd_pcm_oss snd_mixer_oss snd_seq_oss snd_ioctl32 dont forget to modprobe the modules, too. HTH Frederik Schueler -- ENOSIG signature.asc Description: Digital signature
quake3
hello i'm just installing quake3 on sid pure64. i think quake3 was not able to find libGL in /emul/ so i copy it in quake3 dir it's work but now I have no sound is there a solution pour this problem ? --- sound initialization --- Could not mmap dma buffer PROT_WRITE|PROT_READ trying mmap PROT_WRITE (with associated better compatibility / less performance code) /dev/dsp: Input/output error Could not mmap /dev/dsp thank -- Philippe <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: chroot and X
On Thursday 10 February 2005 13:44, [EMAIL PROTECTED] wrote: > xterm from my 64bit XFce: "could not open Display :0.0. Do you have /tmp bind mounted in the chroot? For example, in my (64bit) fstab I have: /tmp/data/ia32-root/tmp nonebind0 0 -Ted -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
chroot and X
Hi folks, I'm running amd64-debian from alioth and a Knoppix 3.7 on 2 differend Partitions. The Motherboard from ASUS is Ok. The d-i found the hardware. X runs on a Matrox G550. I don't need 3D for games. Ok, anything runs at once, excepting burning dvd, 32bit plugins for mozilla, openoffice ... Nothing new. After I have read the amd64-howto, I build a chroot to the installation of Knoppix on the 2. partition. Any commandline tool work fine. But I can't start any xterm from my 64bit XFce: "could not open Display :0.0. From another xterm I've set a "xhost +" to the windowmanager, to allow the access. If I start X with "startx" from the chroot, the complete KDE from Knoppix starts corectly. What is my mistake? Any idea? Please send a CC: to me, I don't have subscribe your mailing-list. Thanks for answer, -- Gruß Ralf Springwald Und die See wird allen neue Hoffnung bringen, sowie der Schlaf die Träume bringt, daheim (Christoph Kolumbus) -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel 2.6.10-9-amd64-k8
Am Sonntag, 6. Februar 2005 15:43 schrieb Andree Zeulner: > Hi, > > since kernel 2.6.10-9 I get an error while booting: > > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > Evaluate _OSC Set fails. Status = 0x0005 > pciehp: add_host_bridge: status 5 > pciehp: acpi_pciehprm:\_SB_.PCI0 _HPP fail=0x5 > pciehp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5 > pciehp: acpi_pciehprm: Slot sun(1) at s:b:d:f=0x00:00:08: > pciehp: acpi_pciehprm:\_SB_.PCI0 _HPP fail=0x5 > pciehp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5 > pciehp: acpi_pciehprm: Slot sun(2) at s:b:d:f=0x00:00:09: > pciehp: acpi_pciehprm:\_SB_.PCI0 _HPP fail=0x5 > pciehp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5 > pciehp: acpi_pciehprm: Slot sun(3) at s:b:d:f=0x00:00:0a: > pciehp: acpi_pciehprm:\_SB_.PCI0 _HPP fail=0x5 > pciehp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5 > pciehp: acpi_pciehprm: Slot sun(4) at s:b:d:f=0x00:00:0c: > pciehp: acpi_pciehprm:\_SB_.PCI0 _HPP fail=0x5 > pciehp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5 > pciehp: acpi_pciehprm: Slot sun(5) at s:b:d:f=0x00:00:12: > pciehp: acpi_pciehprm:\_SB_.PCI0 _HPP fail=0x5 > pciehp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5 > pciehp: acpi_pciehprm: Slot sun(6) at s:b:d:f=0x00:00:13: > pciehp: Fails to gain control of native hot-plug > shpchp: acpi_shpchprm:\_SB_.PCI0 _HPP fail=0x5 > shpchp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5 > shpchp: acpi_shpchprm: Slot sun(1) at s:b:d:f=0x00:00:08: > shpchp: acpi_shpchprm:\_SB_.PCI0 _HPP fail=0x5 > shpchp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5 > shpchp: acpi_shpchprm: Slot sun(2) at s:b:d:f=0x00:00:09: > shpchp: acpi_shpchprm:\_SB_.PCI0 _HPP fail=0x5 > shpchp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5 > shpchp: acpi_shpchprm: Slot sun(3) at s:b:d:f=0x00:00:0a: > shpchp: acpi_shpchprm:\_SB_.PCI0 _HPP fail=0x5 > shpchp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5 > shpchp: acpi_shpchprm: Slot sun(4) at s:b:d:f=0x00:00:0c: > shpchp: acpi_shpchprm:\_SB_.PCI0 _HPP fail=0x5 > shpchp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5 > shpchp: acpi_shpchprm: Slot sun(5) at s:b:d:f=0x00:00:12: > shpchp: acpi_shpchprm:\_SB_.PCI0 _HPP fail=0x5 > shpchp: acpi_pciehprm:\_SB_.PCI0 OSHP fails=0x5 > shpchp: acpi_shpchprm: Slot sun(6) at s:b:d:f=0x00:00:13: > shpchp: shpc_init : shpc_cap_offset == 0 > shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 > > FATAL: Error inserting pciehp > (/lib/modules/2.6.10-9-amd64-k8/kernel/drivers/pci/hotplug/pciehp.ko): No > such device > > modinfo pciehp > filename: > /lib/modules/2.6.10-9-amd64-k8/kernel/drivers/pci/hotplug/pciehp.ko > license:GPL > description:PCI Express Hot Plug Controller Driver > author: Dan Zink <[EMAIL PROTECTED]>, Greg Kroah-Hartman > <[EMAIL PROTECTED]>, Dely Sy <[EMAIL PROTECTED]> > srcversion: 5EC532C0153B2015B7CB083 > alias: pci:v*d*sv*sd*bc06sc04i00* > depends:pci_hotplug > vermagic: 2.6.10-9-amd64-k8 gcc-3.4 > parm: pciehp_debug:Debugging mode enabled or not > parm: pciehp_poll_mode:Using polling mechanism for hot-plug > events or not > parm: pciehp_poll_time:Polling mechanism frequency, in seconds > > what further info is needed to solve this problem? > > regards > > Andree I found a way to turn this message off by adding pciehp shpchp to /etc/hotplug/blacklist -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic with latest iso's
Ok, Thanks a lot!! I'll try right now! Goswin von Brederlow escribió: "Marcos Hdez." <[EMAIL PROTECTED]> writes: Hi! I'm new in here. I'm trying to install from the netinstall iso and still the same problem. Does anybody know where to report the bug? Here's about right. Are you sure you have the sid netinstall iso? By the way, can I do a network installation with the netboot or monolithic isos? - mini and netboot just boot from CD and do everything over the net. - monolithic is like netboot but has all modules preinstalled. - netinstall installs a full Debian base system from CD There isn't a good reason for those names. The netinstall iso is old (kernel 2.6.8) and known to work. The netboot isos are known to panic, hopefully fixed tonight. Thanks a lot!! Marcos Hdez. SpikeyGG escribió: Yeah, I installed my system about a week ago using the mini.iso off the netinst directory and it worked like a charm. MSI K8N Neo2 Platinum installing on 2 SATA drives in a mirrored array. Don't use softraid bios if you use only Linux. Use Linuxs own software raid support. I just wanted to set it up and decide if the AMD64 port works well enough to use as a HTPC. I've decided that it's more stable that I expected and that there are more 64bit packages than I know what to do with. So I wanted to wipe it clean and redistribute my array to account for some swap space and make it more redundant. I tried to use the CD that I used before and when it got to the "downloading stuff" portion of the install it complained that there weren't and Netinst never downloads prior to the reboot into the real system. So you must have a netboot iso. MfG Goswin No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.6 - Release Date: 07/02/2005
Re: AMD64 Compat List
Le 10.02.2005 19:19:28, Lennart Sorensen a écrit : On Thu, Feb 10, 2005 at 06:14:14PM +, Jean-Luc Coulon (f5ibh) wrote: On the heatsink is not really problem (with an amd64, nt a Prescott), in the bladesof the fan might e a problem ;-) But it is not always clear *where* are located the sensors. Most if not all motherboards since the Athlon XP came about, have had a temp sensor under the cpu socket I believe. My old A7V board (first Asus socket A board) had an external sensor to put on the heat sink, while later A7V series (with newer chipsets and support for newer athlons) had the sensor under the socket somehow. The Athlon64 has thermal sensing diode on the chip. But unfortunately it is not used to monitor the temperature. The A8V use a thermistor under the socket to do that, you are right. But it seems that the thermal diode is used for safety purposes: it shut down the system is case of overheat. (I've found this information on AMD site, in the supported motherboard section but surprisingly I've not found this information at ASUS's). Len Sorensen Jean-Luc pgpspSoRGNQ7V.pgp Description: PGP signature
Re: AMD64 Compat List
Later boards used the onboard temperature sensor on the CPU. Most modern processors do this. Lennart Sorensen wrote: On Thu, Feb 10, 2005 at 06:14:14PM +, Jean-Luc Coulon (f5ibh) wrote: On the heatsink is not really problem (with an amd64, nt a Prescott), in the bladesof the fan might e a problem ;-) But it is not always clear *where* are located the sensors. Most if not all motherboards since the Athlon XP came about, have had a temp sensor under the cpu socket I believe. My old A7V board (first Asus socket A board) had an external sensor to put on the heat sink, while later A7V series (with newer chipsets and support for newer athlons) had the sensor under the socket somehow. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 Compat List
On Thu, Feb 10, 2005 at 06:14:14PM +, Jean-Luc Coulon (f5ibh) wrote: > On the heatsink is not really problem (with an amd64, nt a Prescott), > in the bladesof the fan might e a problem ;-) > > But it is not always clear *where* are located the sensors. Most if not all motherboards since the Athlon XP came about, have had a temp sensor under the cpu socket I believe. My old A7V board (first Asus socket A board) had an external sensor to put on the heat sink, while later A7V series (with newer chipsets and support for newer athlons) had the sensor under the socket somehow. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 Compat List
Le 10.02.2005 18:58:29, Daniel James a écrit : Hi Alessandro, At school I studied a strange law kwnon also as second thermodynamic principle, which state that heat flows from a higher temberature body to a lower temperature body. For this reason, NEVER should happen that the heatsink has a temperature higher than the CPU (heat source) whichever fan you apply ;-) You could be right, but as CPU use is bursty and the heatsink is surrounded by insulating air, the heatsink might still be hot after the CPU has cooled. And isn't the radiator in a house hotter at the top than at the bottom? All I know for sure is: 1. hot CPU and cold heatsink is a bad sign 2. not to put my finger on a heatsink while computer is in use : ) On the heatsink is not really problem (with an amd64, nt a Prescott), in the bladesof the fan might e a problem ;-) But it is not always clear *where* are located the sensors. Cheers Daniel Jean-Luc pgpGNppsazJNL.pgp Description: PGP signature
Re: AMD64 Compat List
Hi Alessandro, > At school I studied a strange law kwnon also as second > thermodynamic principle, which state that heat flows from a higher > temberature body to a lower temperature body. For this reason, > NEVER should happen that the heatsink has a temperature higher than > the CPU (heat source) whichever fan you apply ;-) You could be right, but as CPU use is bursty and the heatsink is surrounded by insulating air, the heatsink might still be hot after the CPU has cooled. And isn't the radiator in a house hotter at the top than at the bottom? All I know for sure is: 1. hot CPU and cold heatsink is a bad sign 2. not to put my finger on a heatsink while computer is in use : ) Cheers Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: python and automake error
I've got all python2.x-dev packages and it does not help. Could it be something in automake settings? Gasper Kurt Roeckx wrote: On Thu, Feb 10, 2005 at 12:42:31AM +0100, Gasper Zejn wrote: If i use "autoconf ; automake ; autoreconf" on source (I'd supposedly have to do this on cvs source) the autoreconf pops the following error: aclocal.m4: 374: `jm_MAINTAINER_MODE' is obsolete; use `AM_MAINTAINER_MODE' aclocal: configure.ac: 12: macro `AM_PATH_PYTHON' not found in library autoreconf: aclocal failed with exit status: 1 You probably need to install python-dev or python2.3-dev or something. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 Compat List
At school I studied a strange law kwnon also as second thermodynamic principle, which state that heat flows from a higher temberature body to a lower temperature body. For this reason, NEVER should happen that the heatsink has a temperature higher than the CPU (heat source) whichever fan you apply ;-) On Thu, Feb 10, 2005 at 10:09:03 +, Daniel James <[EMAIL PROTECTED]> wrote: > Hi Per, > > > the M/B temp is higher than the CPU temp > > This might be right if your CPU cooling is particularly efficient, or > your box otherwise has inadequate ventilation. I have a heatpipe > cooler on my Opteron, and if I turn up the CPU fan I can make it > cooler than the rest of the system at idle. Right now it's 32C system > and 33C CPU with the fan running quiet. > > 45C does sound way too hot for a motherboard with a CPU at 36C, so in > your case it does sound as though the values have been swapped. > > > and the > > CPU temp is lower than the temp I'm getting from a probe attached > > to the heatsink. > > That's just as it should be, because you want the heat to be rising > into the heatsink and not staying in the CPU core. If it was the > other way round then it would probably mean there was poor contact > between CPU and heatsink, with an air gap where the thermal compound > should be. > > Cheers! > > Daniel > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- <[EMAIL PROTECTED]> Everithing I tell is always IMHO, if it's not enought please take a visit at http://aquelpaese.da.ru -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: xorg, transparency and ati drivers
f.carone wrote: I was originally interested in the improved open source Radeon code with DRI and have not tried the composite and transparency in your question. Try it if you can, as I'd like to know if this is an issue of my installation or not. Googling a bit, it seems this 'slowlyness' affects ATI cards but not nVidia ones. Cheers, fc +++ I found the xcompmgr and transset at ubuntu. The first time I had the transparency enabled caused the Xserver to almost freeze. That was much worse than just being slow. I have been trying a few more settings without any solution. I need to read more about the new special effects before I know if my configuration is correct. They probably won't be widely implemented for quite a while anyway. My first experience was bad although I could see the transparency in action. I am still very happy with the new Xorg X11 compared to the old Xfree86. :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 Compat List
Hi Per, > the M/B temp is higher than the CPU temp This might be right if your CPU cooling is particularly efficient, or your box otherwise has inadequate ventilation. I have a heatpipe cooler on my Opteron, and if I turn up the CPU fan I can make it cooler than the rest of the system at idle. Right now it's 32C system and 33C CPU with the fan running quiet. 45C does sound way too hot for a motherboard with a CPU at 36C, so in your case it does sound as though the values have been swapped. > and the > CPU temp is lower than the temp I'm getting from a probe attached > to the heatsink. That's just as it should be, because you want the heat to be rising into the heatsink and not staying in the CPU core. If it was the other way round then it would probably mean there was poor contact between CPU and heatsink, with an air gap where the thermal compound should be. Cheers! Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debconf and other outdated packages
On 05-Feb-09 21:23, Javier Kohen wrote: > > Hi, > > I was wondering why some packages which are successfully compiled by > buildd for gcc-3.4 don't make it to the pool. One particular case is > debconf 1.4.45, which fixes some awful looking error messages when > running dpkg. Another is the Is there always manual intervention > involved in moving the packages to the pool? I'm afraid I don't know how > Debian works on that level. Thanks for the report. Usually there is almost no manual intervention necessary. However, something went wrong with the archive's source update and also with the upload of some packages. I just rebuilt and uploaded quite a few missing package versions. The debconf version 1.4.45 is now available in the archive. Regards Andreas Jochens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: Anyone tried the ASUS A8V-E Deluxe?
On Thu, 10 Feb 2005, Alois Z. wrote: I got it running last night with the drvier from the manufacturer. But only after I installed the kernel sources only kernel headers broke the compilation of the driver. I spoted the same for the nvidia drivers. running gcc3.4 and kernel 2.6.9-9 You should be careful with the gcc3.4 tree: it is the slightly more experimental one, there have been some glitches in the past and probably there will be some more in the future, since it uses the gcc4.0 compiler family to compile its packages and this is known to be still somewhat buggy. On the other hand, this is useful for its added error checking capabilities and helped catch quite a few bugs already, which were fixed in pure64 as well. And although "experimental" is to be read in the usual Debian way, i.e. still very stable, pure64 is supposed to be the more conservative, and more stable tree. In short, if you want to help chasing and fixing bugs, and are prepared to accept a little bit of instability, go with gcc3.4; if on the other hand you want something (almost) rock solid and dependable, go with pure64. Bye Giacomo -- _ Giacomo Mulas <[EMAIL PROTECTED]> _ OSSERVATORIO ASTRONOMICO DI CAGLIARI Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA) Tel. (OAC): +39 070 71180 248 Fax : +39 070 71180 222 Tel. (UNICA): +39 070 675 4916 _ "When the storms are raging around you, stay right where you are" (Freddy Mercury) _ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: Anyone tried the ASUS A8V-E Deluxe?
> On Thu, 10 Feb 2005, Alois Zoitl wrote: > > > i got this htin g yesterday and I'm not to glad about it because I can > not > > get the network running. > > As far as I found out it uses also the sk98lin driver. > > But the standard driver that comes along with the debian amd 64 cd fails > the > > installation. > > It's a bug in the installation image, it's known to fail to load the > module even though it detects it fine. During installation, you have to > choose the option to execute a shell, run "modprobe -f sk98lin", which > initialises the NIC, possibly bring up and configure the interface with > the appropriate ifconfig command and friends, and from then on you should > be fine. I have such a beast working under my desk right now, with pure64 > installed, and had no other problem with it. I am currently running a > kernel compiled from the stock debian sources, 2.6.10. > I got it running last night with the drvier from the manufacturer. But only after I installed the kernel sources only kernel headers broke the compilation of the driver. I spoted the same for the nvidia drivers. running gcc3.4 and kernel 2.6.9-9 Alois -- DSL Komplett von GMX +++ Supergünstig und stressfrei einsteigen! AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Anyone tried the ASUS A8V-E Deluxe?
On Wed, 9 Feb 2005, Wesley J Landaker wrote: I have this board, I'm still working on migrating everything over to this system (it's going to be my new primary system on my desk). May I ask you, and the list, a question (well, a couple) then: how much RAM do you have installed? I have 4Gb on it, but I was unable to use it all, because apparently some addressing space (about 400Mb) is reserved for the southbridge. I found an option in the bios (the documentation is terse on it, to say the least) which claims to "remap" memory to make it all available. I tried enabling that, but then some drivers do not work well (e.g. nvidia, but I can live with it) or do not work at all (e.g. sk98lin, and this crashes the computer). Currently, for the sake of stability, I left remapping disabled in the bios and everything works like a charm, apart from the missing 400Mb, but this is not copletely satisfactory. Anybody else went through this? Suggestions? Thanks, bye Giacomo -- _ Giacomo Mulas <[EMAIL PROTECTED]> _ OSSERVATORIO ASTRONOMICO DI CAGLIARI Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA) Tel. (OAC): +39 070 71180 248 Fax : +39 070 71180 222 Tel. (UNICA): +39 070 675 4916 _ "When the storms are raging around you, stay right where you are" (Freddy Mercury) _ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: Anyone tried the ASUS A8V-E Deluxe?
On Thu, 10 Feb 2005, Alois Zoitl wrote: i got this htin g yesterday and I'm not to glad about it because I can not get the network running. As far as I found out it uses also the sk98lin driver. But the standard driver that comes along with the debian amd 64 cd fails the installation. It's a bug in the installation image, it's known to fail to load the module even though it detects it fine. During installation, you have to choose the option to execute a shell, run "modprobe -f sk98lin", which initialises the NIC, possibly bring up and configure the interface with the appropriate ifconfig command and friends, and from then on you should be fine. I have such a beast working under my desk right now, with pure64 installed, and had no other problem with it. I am currently running a kernel compiled from the stock debian sources, 2.6.10. Bye Giacomo -- _ Giacomo Mulas <[EMAIL PROTECTED]> _ OSSERVATORIO ASTRONOMICO DI CAGLIARI Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA) Tel. (OAC): +39 070 71180 248 Fax : +39 070 71180 222 Tel. (UNICA): +39 070 675 4916 _ "When the storms are raging around you, stay right where you are" (Freddy Mercury) _ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
