Re: Plugins
On 5/4/07, Pepo [EMAIL PROTECTED] wrote: Hi friends. Please, How do I can use plugins in Iceweasel if I am using Lenny-AMD64? (java, flash player) Thanks. hi, afaik adobe flash player comes in 32bit version only You might want to consider Installing a Debian IA32bit chroot system: take a look at https://alioth.debian.org/docman/view.php/30192/21/debian-amd64-howto.html#id292010 bye // SS
Re: Howto create 64bit Kernel?
* Alex Samad [EMAIL PROTECTED] [May 01. 2007 23:08]: snip I´m working with many new hardware because of that, i need an kernel with updated driver and debian doesn´t update the kernel after an freeze. you might want to track unstable or even testing ... or try out a kernel from backports.org: deb http://ftp.de.debian.org/backports.org/ etch-backports main There's a backported 2.6.20 kernel available there. I'm using the i386 version on a 32-bit system myself and haven't experienced any problems so far. Thanks, to all for your help. Regards Stefan D. Cheers, Jonas -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: swap
Francesco Pietra [EMAIL PROTECTED] writes: Is it conceivable to add a low-quality 300GB HD (for swap file) to a raid1 system? What do you mean with low-quality? You certainly want a reliable driver there since a failin swap drive can take down the whole system. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Fwd: swap
On Mon, May 07, 2007 at 03:10:11AM -0700, Francesco Pietra wrote: Below I mean adding a single HD not to the raid, just as additional space where to point the swap file thanks Running a raid1 system with non raid swap just doesn't make sense. If the swap drive fails, your system dies horribly possible in ways that could mess up the filesystem. Why make a system with redundancy suddenly have none? Better to buy a pair of those drives and run swap on another raid1. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New box crashes
On Sun, May 06, 2007 at 04:53:19PM -0700, M. Edward (Ed) Borasky wrote: I just got a new box (Athlon 54 X2 4200+ on a Gigabyte Technology NVIDIA GeForce 6100 Socket AM2 AMD ATX Motherboard). I'm getting miscellaneous crashes on Etch. They usually occur during I/O intensive operations, and at this point I have no reason to suspect the hardware. I've gotten a few traces in /var/log/messages, which I'll post to the appropriate place as soon as I find out what the appropriate place is. Nothing wrong with trying them here. At worst someone will suggest posting them to lkml instead if it looks like an actual kernel problem. So, where does one take this sort of thing? I don't have enough information yet to rule out hardware or enough decent debug traces to file a defect anywhere. If I can find a non-SMP kernel for Etch on an AMD64, I'll probably install it just to see if this stuff goes away. Most athlon 64 system stability problems come down to the use of bad ram or more specifically ram that just doesn't have the timing accuracy that the amd memory controller requires. Even running memtest for days may not find it, but taking out half the ram might find a bad stick, although in some cases the only solution is to buy a different brand of ram (preferably one the motherboard maker has certified). Another source of weird crashes is using crappy generic power supplies. Just don't ever do that. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New box crashes
Jack Malmostoso wrote: I've gotten a few traces in /var/log/messages, which I'll post to the appropriate place as soon as I find out what the appropriate place is. If it's kernel related, the LKML is the right place. Yeah ... once I try a 32-bit kernel, that's where I'm going. Etch, Feisty Fawn, Gentoo 2006.1 and CentOS all have similar problems, so it's pretty much got to be either hardware or the upstream 64-bit kernel. In order: 1) Check the memory with memtest for 12+ hours So far it has about five hours with no errors. I'm hoping there are other diagnostics I can use. 2) Check that HD cables are correctly placed in their sockets This seems unlikely -- the messages I'm getting look more like memory management than I/O. I have one GB -- I'm thinking that might not be enough for a 64-bit kernel. 3) Check that the computer isn't running too hot What's the package in Etch that does that? I couldn't find it in the Gnome desktop. 4) Check with another distro. Check the md5sum of the iso BEFORE burning it Pretty much all the distros and kernels ranging from 2.6.17 through 2.6.18 do this. If I can get the 2.6.20 kernel to build without a crash during the compile, I'll check it out. 5) If nothing yields results, disassemble the computer and remount it with more care and love Good luck! By the way, so far, Etch has been the most stable and it's the only one that's configured the video right. Feisty Fawn crashed during the install, CentOS can't give me a reasonable looking screen and Gentoo hasn't been able to do a kernel build without crashing. If I can figure out make-kpkg and start building my own kernels, lenny may be the best choice for this system. It's a scientific workstation. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Random Crashes
Hello all, Ever since I bought my AMD64 system (AMD 64 3000+, Asus K8U-X motherboard) I've been experiencing random freezes, in which the system completely stops to respond, or sometimes automatic reboots. Sometimes the system halts during boot with a message such as HARDWARE ERROR CPU 0: Machine Check Exception:4 Bank 4: b2070f0f TSC a38a02f0b This is not a software problem! The crashes do not necessarily happen when the system is doing something ram or processor intensive. I can do heavy tasks such as video encoding with no problems, but sometimes the system crashes when it's idle, only background tasks running. Also, the crashes are not so frequent. When I bought the system, it had one stick with 512Mb of RAM. Crashes already happened then. Later I added anoter stick with 1Gb of RAM. I suspected the memory, and ran memtest only. But it was for a short time, so in fact I cannot conclude anything from the lack of errors. So I took of the old 512Mb ram module, because it should be the one with problems, since the crashes happened already when I had only that one. The system still crashed. Just to be sure, I put it on again, and only this one, and the system also crashes. The motherboard has two slots for RAM. I tried both modules in both slots, and I did notice that when a module (either one) is in one of the slots, the system crashes just after boot --- at most I can type the password and let KDE start, but it crashes before KDE is fully loaded. With a module in the other slot, then the system is usable most of the times. So, am I really unlucky to have two memory modules with problems, or what else should I suspect? Motherboard? Processor? What would be the possible ways to diagnose the problem? -- They told me I was gullible ... and I believed them! Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Fwd: swap
On Mon, May 07, 2007 at 09:11:36AM -0700, Francesco Pietra wrote: Len, Patrick: Thanks. Actually, I didn't see the original by Len. Well, security comes first. Also, the idea of setting in a cheap HD was a faulty idea anyway because I am at WD Raptor just because cheap HDs didn't work on long runs. The mentioned Tyan mother board has 4 SATA ports, two, I suppose, already occupied by raid1. Following the suggestion by Len, is that possible to install another raid1 (just for additional disk space, say swap) while preserving the current Debian amd64 etch on present raid1 (Linux driven)? This machine is ssh with Debian i386 as graphical interface on another machine so that reinstalling everything on new HDs would not be attractive. Also, I am pressed to fish some computations. It is possible, swap is dynamic under linux. swapon/swapoff are the tools you are looking for. man swapon Patrick. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Fwd: swap
Lennart Sorensen wrote: Running a raid1 system with non raid swap just doesn't make sense. If the swap drive fails, your system dies horribly possible in ways that could mess up the filesystem. On the other hand you (mostly) don't have redundant RAM modules in your system and if one fail it is the same effect. Bye -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New box crashes
On Mon, May 07, 2007 at 07:15:25AM -0700, M. Edward (Ed) Borasky wrote: So far it has about five hours with no errors. I'm hoping there are other diagnostics I can use. Well a lot of people who have reported stability problems with new athlon 64 machines ran memtest and got nothing, and still their problems were caused by the ram. memtest can tell you if you have a problem in many cases. It can never tell you that you do not have a problem. This seems unlikely -- the messages I'm getting look more like memory management than I/O. I have one GB -- I'm thinking that might not be enough for a 64-bit kernel. Should be plenty for most uses. Certainly has been for me. What chipset does you system use? That may give a much better clue as to whether there may be kernel problems for that board. What's the package in Etch that does that? I couldn't find it in the Gnome desktop. lm-sensors, etc, but it is board/chipset specific, not something that just works genericly. Pretty much all the distros and kernels ranging from 2.6.17 through 2.6.18 do this. If I can get the 2.6.20 kernel to build without a crash during the compile, I'll check it out. Certainly 2.6.20 might fix some of the many many issues with the ATI SB600 chipset. By the way, so far, Etch has been the most stable and it's the only one that's configured the video right. Feisty Fawn crashed during the install, CentOS can't give me a reasonable looking screen and Gentoo hasn't been able to do a kernel build without crashing. If I can figure out make-kpkg and start building my own kernels, lenny may be the best choice for this system. It's a scientific workstation. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Random Crashes
On Mon, May 07, 2007 at 11:42:08AM -0300, Eduardo M KALINOWSKI wrote: Hello all, Ever since I bought my AMD64 system (AMD 64 3000+, Asus K8U-X motherboard) I've been experiencing random freezes, in which the system completely stops to respond, or sometimes automatic reboots. Sometimes the system halts during boot with a message such as HARDWARE ERROR CPU 0: Machine Check Exception:4 Bank 4: b2070f0f TSC a38a02f0b This is not a software problem! The crashes do not necessarily happen when the system is doing something ram or processor intensive. I can do heavy tasks such as video encoding with no problems, but sometimes the system crashes when it's idle, only background tasks running. Also, the crashes are not so frequent. When I bought the system, it had one stick with 512Mb of RAM. Crashes already happened then. Later I added anoter stick with 1Gb of RAM. I suspected the memory, and ran memtest only. But it was for a short time, so in fact I cannot conclude anything from the lack of errors. So I took of the old 512Mb ram module, because it should be the one with problems, since the crashes happened already when I had only that one. The system still crashed. Just to be sure, I put it on again, and only this one, and the system also crashes. The motherboard has two slots for RAM. I tried both modules in both slots, and I did notice that when a module (either one) is in one of the slots, the system crashes just after boot --- at most I can type the password and let KDE start, but it crashes before KDE is fully loaded. With a module in the other slot, then the system is usable most of the times. So, am I really unlucky to have two memory modules with problems, or what else should I suspect? Motherboard? Processor? What would be the possible ways to diagnose the problem? A google search on that error message seems to indicate that it has been seen on some systems where the power supply wasn't sufficient to provide stable power to the system. Other posibilities is that the ram simply isn't stable (although bad power can make ram not stable of course). What size power supply, what brand/model, and how much hardware is in that system? -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Fwd: swap
On Mon, May 07, 2007 at 09:11:36AM -0700, Francesco Pietra wrote: Len, Patrick: Thanks. Actually, I didn't see the original by Len. Well, security comes first. Also, the idea of setting in a cheap HD was a faulty idea anyway because I am at WD Raptor just because cheap HDs didn't work on long runs. The mentioned Tyan mother board has 4 SATA ports, two, I suppose, already occupied by raid1. Following the suggestion by Len, is that possible to install another raid1 (just for additional disk space, say swap) while preserving the current Debian amd64 etch on present raid1 (Linux driven)? This machine is ssh with Debian i386 as graphical interface on another machine so that reinstalling everything on new HDs would not be attractive. Also, I am pressed to fish some computations. Sure. Just add the two new drives, and use mdadm to create another raid1 on the new drives. Should be very simple and should have no effect on your current raid at all. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Random Crashes
On Mon, May 07, 2007 at 11:42:08AM -0300 Eduardo M KALINOWSKI said: So, am I really unlucky to have two memory modules with problems, or what else should I suspect? Motherboard? Processor? What would be the possible ways to diagnose the problem? Have you tried running the box with two similar memory modules? Sam -- (Sam Varghese) http://www.gnubies.com Program testing can best show the presence of errors but never their absence. - Edsger Wybe Dijkstra My PGP key: http://www.gnubies.com/encryption/sign.txt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New box crashes
On Mon, 07 May 2007 16:20:09 +0200, M. Edward (Ed) Borasky wrote: So far it has about five hours with no errors. I'm hoping there are other diagnostics I can use. That's the most accurate I know about. As suggested by Lennart, check that the timings in the BIOS are set to auto. This seems unlikely -- the messages I'm getting look more like memory management than I/O. I have one GB -- I'm thinking that might not be enough for a 64-bit kernel. I have 1GB of good RAM on my box and I have never had a problem. I suggested the HD cables because I had such a problem a few weeks ago :) What's the package in Etch that does that? I couldn't find it in the Gnome desktop. lm_sensors is what you're looking for. Pretty much all the distros and kernels ranging from 2.6.17 through 2.6.18 do this. If I can get the 2.6.20 kernel to build without a crash during the compile, I'll check it out. There's a 2.6.20 in Sid. Maybe it's been backported to Etch, or you can just install the .deb package. -- Best Regards, Jack Linux User #264449 Powered by Debian GNU/Linux on AMD64 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Random Crashes
Eduardo M KALINOWSKI wrote: Hello all, Ever since I bought my AMD64 system (AMD 64 3000+, Asus K8U-X motherboard) I've been experiencing random freezes.. Hi Eduardo, I get the same problem with my Asus K8V Deluxe - AMD Athlon 64 +3200, but only with debian (etch) AMD64. With other kind of arch (i.e. i486, i686 k7) no problems at all. I guess the problem is with AMD64 flavour. Just my 2 cents. Bye, Giorgio. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Random Crashes
Eduardo M KALINOWSKI wrote: Hello all, Ever since I bought my AMD64 system (AMD 64 3000+, Asus K8U-X motherboard) I've been experiencing random freezes.. Hi Eduardo, I get the same problem with my Asus K8V Deluxe - AMD Athlon 64 +3200, but only with debian (etch) AMD64. With other kind of arch (i.e. i486, i686 k7) no problems at all. I guess the problem is with AMD64 flavour. I don't think it's a software problem... I forgot to mention in the original mail, but there is nothing in the system logs. It just freezes or reboots. -- Eduardo M Kalinowski [EMAIL PROTECTED] http://move.to/hpkb
Re: Random Crashes
On Mon, 2007-05-07 at 17:35 +, Jack Malmostoso wrote: On Mon, 07 May 2007 16:50:13 +0200, Eduardo M KALINOWSKI wrote: HARDWARE ERROR CPU 0: Machine Check Exception:4 Bank 4: b2070f0f TSC a38a02f0b This is not a software problem! Turn off Chipkill in the BIOS unless you know for a fact that your RAM is single rank (x4bit). -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Swap area shorter than signature indicates
Hi all. The subject of this mail is the message I can find for every boot in my /var/log/messages file. I've set up a RAID1 environment with etch amd64; it's composed of 2 identical HDDs. The partitioning scheme is the same for both the devices. I've put the swap area (a /dev/md1 made by /dev/sda5 and /dev/sdb5) in the RAID, setting the ID label as fd (that is the 'Linux raid autodetect' mode). The /proc/mdstat file says about that partition: md1 : active raid1 sda5[0] sdb5[1] 1951744 blocks [2/2] [UU] Is that correct? Is the swap area working right despite the message above? If so, why do I get that strange message in the logs? Thanks a lot for your hints. Greetings, Matteo -- Matteo F. Vescovi mfv (at) fsugpadova (dot) org Free Software Users Group Padova GPG Fingerprint: 8EF0 F019 80D1 96BF C9C6 387E D6DE 031F 991F 9D2D -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Random Crashes
On Mon, May 07, 2007 at 03:10:34PM -0300, Eduardo M Kalinowski wrote: The power supply could indeed be the problem. It's no great power supply, and I have two (PATA) HDs. No fancy graphics card, though --- only a SIS 315. I have also a DVD burner. However, I've been able to successfully burn DVDs (when more power would be needed, I guess). Still, changing the power supply would be the easiest thing for me to do. At the worst, I'll have a good one to use when I decide to build a new system. (Unlike the DDR1 modules that the motherboard uses.) A friend of mine had a system some years ago that crashed very often and corrupted disk contents. Replacing the power supply with a nice high quality name brand one eliminated all the crashes and disk corruption. He noticed the voltage monitoring in the bios one day and found that some of the rails were bouncing up and down a lot and were not really that close to what they should be. With a new power supply the voltages became completely steady as did the system. Remember a quality 300W will easily handle more load than a generic who knows what 500W. And the more they weight the better they are is fairly accurate for power supplies, although I am sure there are exceptions to that. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Swap area shorter than signature indicates
On Mon, May 07, 2007 at 09:24:18PM +0200, Matteo Vescovi wrote: The subject of this mail is the message I can find for every boot in my /var/log/messages file. I've set up a RAID1 environment with etch amd64; it's composed of 2 identical HDDs. The partitioning scheme is the same for both the devices. I've put the swap area (a /dev/md1 made by /dev/sda5 and /dev/sdb5) in the RAID, setting the ID label as fd (that is the 'Linux raid autodetect' mode). The /proc/mdstat file says about that partition: md1 : active raid1 sda5[0] sdb5[1] 1951744 blocks [2/2] [UU] Is that correct? That message is what to expect for a raid1 with both devices up and running (U = Up) Is the swap area working right despite the message above? If so, why do I get that strange message in the logs? Did you mkswap /dev/md1 or /dev/sda5? Try doing swapoff, then make sure free shows no swap space, then use mkswap to recreate the swap on /dev/md1 and then swapon again and see if it gives a message then. Making the swap on the low level filesystem rather than the raid one would cause such problems, as would taking an existing swap partition and adding a new drive and making raid on it and not reinitializing the swap space to match the new slightly smaller size (since raid does require a small superblock to store it's information). -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Shouldn't this work?
On Mon, May 07, 2007 at 04:35:02PM -0400, Wayne Topa wrote: Did I misunderstand somthing? I 'thought' I read that the Athlon was a 64 bit processor. Am I wrong, again? The Athlon64 is a 64-bit processor, as is the Opteron. The regular Athlon is definitely a 32-bit processor. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Re: Swap area shorter than signature indicates
Everything seems setup correctly. What's in /proc/swaps? Probably you initialized the swap partitions before creating the raid array (on /dev/sda5 and/or /dev/sdb5). Software raid steals a bit of space from the device so your resulting mirror is smaller than each device. Make sure first that you aren't using it (swapoff /dev/md1), then do a mkswap /dev/md1 to reinitialize the array as swap. Matteo Vescovi wrote: Hi all. The subject of this mail is the message I can find for every boot in my /var/log/messages file. I've set up a RAID1 environment with etch amd64; it's composed of 2 identical HDDs. The partitioning scheme is the same for both the devices. I've put the swap area (a /dev/md1 made by /dev/sda5 and /dev/sdb5) in the RAID, setting the ID label as fd (that is the 'Linux raid autodetect' mode). The /proc/mdstat file says about that partition: md1 : active raid1 sda5[0] sdb5[1] 1951744 blocks [2/2] [UU] Is that correct? Is the swap area working right despite the message above? If so, why do I get that strange message in the logs? Thanks a lot for your hints. Greetings, Matteo -- -Cedar What's an Intel chip doing in a Mac? A whole lot more than it's ever done in a PC. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Shouldn't this work?
On Mon, May 07, 2007 at 04:35:02PM -0400, Wayne Topa wrote: I just purchased a set of DVD's to install Debian Etch (4.0) on my system. I also got a Ubuntu Ver 6.06 AMD 64 DVD to see how a amd64 compared to the K7 I'm currently running. On bootup the Ubuntu DVD say that I am not running on a amd64 box. Here is what /proc/cpuingo says: processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 4 model name : AMD Athlon(tm) processor stepping: 2 cpu MHz : 1000.123 cache size : 256 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnow up bogomips: 2002.13 Did I misunderstand somthing? I 'thought' I read that the Athlon was a 64 bit processor. Am I wrong, again? Athlon 64 chips are 64bit. Athlon's were not (That is Athlon, Athlon XP, and such). Some Semprons are 64bit, some are not, depending on the model. Opterons are all 64bit. Certainly an old 1GHz chip isn't 64bit. An Athlon IS a K7. An Athlon 64 is a K8. Here is an Athlon 64 3500+ (64bit): # cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 15 model name : AMD Athlon(tm) 64 Processor 3500+ stepping: 0 cpu MHz : 2202.920 cache size : 512 KB fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow up bogomips: 4410.82 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp This particular model is 2.2GHz. It is running amd64. For comparison here is an Athlon XP 2800+ (32bit only). # cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 10 model name : AMD Athlon(tm) XP 2800+ stepping: 0 cpu MHz : 2088.163 cache size : 512 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow up ts bogomips: 4179.29 This one is about 2.085Ghz, but is a whole lot slower than the Athlon 64. It is running i386. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Swap area shorter than signature indicates
On 05/07/2007 10:24 PM, Lennart Sorensen wrote: That message is what to expect for a raid1 with both devices up and running (U = Up) I kind of knew that, but needed some confirm ;-) Is the swap area working right despite the message above? If so, why do I get that strange message in the logs? Did you mkswap /dev/md1 or /dev/sda5? I did it before via sudo but for some reasons it didn't work. Try doing swapoff, then make sure free shows no swap space, then use mkswap to recreate the swap on /dev/md1 and then swapon again and see if it gives a message then. So, now I tried as superuser and it worked :-) The log says: server kernel: Adding 1951736k swap on /dev/md1. Priority:-1 extents:1 across:1951736k ... and in free I've got the right size for the swap area. Great! Thanks a lot, Len! :-) Greetings, Matteo -- Matteo F. Vescovi mfv (at) fsugpadova (dot) org Free Software Users Group Padova GPG Fingerprint: 8EF0 F019 80D1 96BF C9C6 387E D6DE 031F 991F 9D2D -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Plugins
Am Donnerstag, den 03.05.2007, 23:05 -0500 schrieb Pepo: Hi friends. Please, How do I can use plugins in Iceweasel if I am using Lenny-AMD64? (java, flash player) Thanks. On sid-amd64 there is nspluginwrapper. With that little piece of software you can run the Adobe Flash-Player on amd64. If you don´t want to mix up your system with unstable you can get nspluginwrapper from http://gwenole.beauchesne.info/projects/nspluginwrapper/ You don´t have to compile it. Just take the two *.rpm files (both Plugin _and_ Viewer), convert them with alien into deb and install. Normally this should work. More instructions you can find on the Web-Site mentioned above. Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
64bit hassles (exim + domainkeys truecrypt)
Hi Just wondering if its me, but I have been running into some 64bit hurdles recently. I tried installing truecrypt - because of licensing its not part of the main repository, and you have to build it from the source tree. Of course somebody has been kind enough to make a build package - works great but assumes i386, I have left some comments to the author, just some simple changes and it works. Now I am looking at trialing domainkeys with exim, and again I have to do a build from source route and it looks like I am going to run into the same problem, although this time it might be a bit harder, cause the library I have to link to is i386. The true crypt i386 specific stuff was just scripts. Any one else tried the exim + domain keys. Is there a amd64 debian wiki somewhere I can write this up. Does somebody have a repo with these pre built Alex signature.asc Description: Digital signature
Re: Shouldn't this work?
Lennart Sorensen([EMAIL PROTECTED]) is reported to have said: On Mon, May 07, 2007 at 04:35:02PM -0400, Wayne Topa wrote: I just purchased a set of DVD's to install Debian Etch (4.0) on my system. I also got a Ubuntu Ver 6.06 AMD 64 DVD to see how a amd64 compared to the K7 I'm currently running. --snip-- Did I misunderstand somthing? I 'thought' I read that the Athlon was a 64 bit processor. Am I wrong, again? Athlon 64 chips are 64bit. Athlon's were not (That is Athlon, Athlon XP, and such). Some Semprons are 64bit, some are not, depending on the model. Opterons are all 64bit. Certainly an old 1GHz chip isn't 64bit. An Athlon IS a K7. An Athlon 64 is a K8. 'If' I had read the anywhere I would not have goofed! I was sure that I read somewhere that 'All Athlon's were 64 bit. I should have asked here first. Thanks guys! Now I have an excuse to get a new system! This box is getting a bit weary anyway. Regards Wayne -- Documentation is the castor oil of programming. Managers know it must be good because the programmers hate it so much. ___ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
