Re: mktemp and diff orphaned?
On 11/9/2010 1:33 PM, Hans-J. Ullrich wrote: Hi all, I am running debian-amd64/testing. When I start orphaner there are two packages, which are marked as essentials. These packages are diff and mktemp, but they are below oldlibs. Can they safely to be removed, as they are meanwhile old? Or better leave them? Regards Hans mktemp is required; don't remove it. diff has alternatives, but there is really no need to remove it. It is still has lots of scripts that expect it. -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cda96f2.4060...@allums.com
Re: mktemp and diff orphaned?
On 11/10/2010 6:58 AM, Mark Allums wrote: On 11/9/2010 1:33 PM, Hans-J. Ullrich wrote: Hi all, I am running debian-amd64/testing. When I start orphaner there are two packages, which are marked as essentials. These packages are diff and mktemp, but they are below oldlibs. Can they safely to be removed, as they are meanwhile old? Or better leave them? Regards Hans mktemp is required; don't remove it. diff has alternatives, but there is really no need to remove it. It is still has lots of scripts that expect it. I may have misunderstood. Your system needs and expects the functions of mktemp and diff, but *those particular _versions_ of the packages* may be obsolete. Check out the equivalents and replacements using the apt tools or aptitude, e.g.: # aptitude why diff In my case, the answer is Unable to find a reason to install diff. or, # apt-get remove -s mktemp NOTE: This is only a simulation! ... Package mktemp is not installed, so not removed So, you may not need mktemp or diff packages. mktemp the command is also in package coreutils. diff is also in diffutils. These are the up-to-date packages. -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cdaa9ec.6030...@allums.com
Re: intel i3 processor
On 7/20/2010 2:15 AM, Dean Hamstead wrote: There is 64bit flash bit adobe dropped it. It was always a alpha/beta status, never a release. They have said that 64-bit will return, but gave no indication about when or in what form. My personal guess is that there was only ever one guy working on it, and he's too busy. But that is just speculation. -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c4554ae.8080...@allums.com
Re: libc6 and X11 seem not to work together
Norval Watson wrote: From what Hans reported, it was my impression this is related to the Xorg Radeon (ati) drivers, not to NVidia or something else ? Yes, my system (working) runs Nvidia drivers, self-compiled 2.6.29 realtime kernel Norv I have Nvidia GeForce 7000M and it is not working. I just installed Stable and everything works nicely. If I (just/only) upgrade my system to Testing then the X does not work. kernel 2.6.29.1-rt8-rt-200904211039 #1 SMP PREEMPT RT x86_64 GNU/Linux +++-==-==- ii libc6 2.9-26 GNU C Library: Shared libraries ii nvidia-glx 180.44-2 NVIDIA binary Xorg driver ii xserver-xorg-c 2:1.6.4-1 Xorg X server - core server I think the card is Nvidia 7600, system is current debian sid, but nvidia-glx might be one down from current HTH Norv The non-3D (default) nvidia drivers do not function properly with some 7600s, in particular, the 7600 GT. I must use another driver with mine. I use the nvidia proprietary blob[0], it works fine. Mark Allums 0. binary large object, packaged as a shell and perl script -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: How to install wine on debian/amd64/sid?
hend...@topoi.pooq.com wrote: On Tue, Jul 21, 2009 at 08:07:20PM -0300, Cavan Mejias wrote: 2009/7/20 Dean Hamstead d...@fragfest.com.au: If you arent able to fix breaks, you should use 'testing' which is currently 'squeeze' testing is generally solid enough but also bleeding edge enough for desktops. Ya, I agree. Exactly why I use testing. It must be possible to downgrade from sid to lenny, w/out a reinstall. Downgrading has always been a problem in Debian. The slow way is simply to change your sources.list to point to lenny instead of sid. As sid packages drift into lenny by the normal development process, your system will gradually become more lenny than sid. Along the way aptitude will probably have a few conniptions. The answer to that is simply to back out of any upgrade that causes trouble (using control-U in interactive more). The problems will usually sort themselves out in a few weeks. I think you mean Squeeze, don't you? Lenny will not be updated, other than some backported security fixes. You may want to downgrade in stages, first to Squeeze, then to Lenny. As Hendrick pointed out, it can be very trying of your patience to downgrade. Generally, you can do it by downgrading groups of packages, ending with the kernel and the basic system packages. It will be easiest by hand, but also the most dangerous. Creating and installing some dummy packages to resolve dependencies may help, if you stick to apt, aptitude, and Synaptic. (Remove them as soon as possible.) You can create equivalents, packages that supposedly provide some prerequisite. This may be more work than you want to do. You need to do this all at once. That means, once you start, you should not rest until you are finished. Otherwise, the system may self-destruct. This is true for essential packages that modify system files. You might be able to put off downgrading something like the GIMP. It may be desirable to locate backports of newer versions of programs before you start. If it were me, I would just do a fresh install. Good luck! Mark Allums -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: I want all my 4GB!!!
Bob Proulx wrote: James Brown wrote: Bob Proulx wrote: Hmm... I recommend installing memtest86+ and then seeing how much memory it detects at boot time. apt-get install memtest86+ This should automatically install a grub boot entry and be very easy to boot into afterward. I am thinking it might only detect 3G too. In any case this would be a good independent test. I have installed this packege but I can find neither a man-page of it nor the help information. How can I use it (I think that it works when system booting) and when (and how) can I see the results of this test? It is a boot time image. Reboot and observe the grub boot menu. Use the cursor keys to move down to the memtest image. Boot that image. Memtest86 will run forever until you stop it from running. It is an infinitely running test program. It is very useful for testing memory. But here I was interested in how much memory it reported and so you could stop it almost immediately after noting that information. Upstream package documentation mostly documenting building it is available in /usr/share/doc/memtest86+/README*. Bob I'm posting the obvious, but: Are you sure you have installed the amd64 distro? If so, then it may take some kernel boot parameters to see all of the memory, or you may need to check your BIOS settings. Mark Allums -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Where is the kernel?
Hans-J. Ullrich wrote: Dear maintainers, just some questions What happened to the kernel higher than 2.6.26 ? Is the kernel on hold, due toe the upcoming release of Lenny? Meanwhile the latest stable kernel-version is 2.6.28 (and 2.6.29 is at work). Where is 2.6.27 and 2.6.28 in debian? I only found 2.6.26 as the latest release. Did I miss something? Cheers Hans It's not there, and won't be until after Lenny's release. Unless the maintainers relent and put 2.6.27 into Experimental. Mark Allums -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Where is the kernel?
Lennart Sorensen wrote: On Mon, Jan 05, 2009 at 09:16:14AM -0600, Mark Allums wrote: It's not there, and won't be until after Lenny's release. Unless the maintainers relent and put 2.6.27 into Experimental. Well 2.6.27 was in the kernel experimental area for a while, and 2.6.28 is there now. Yes. Most users either aren't aware, forget about the existence of it, or don't want to mess with kernel experimental. And most of the time, they'd be right. The Lenny freeze is causing an exception to the usual rule. I personally think both kernels should be is the main experimental section, or even in Sid. But I am not a Debian Maintainer. Mark Allums -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Where is the kernel?
Lennart Sorensen wrote: On Mon, Jan 05, 2009 at 09:41:26AM -0600, Mark Allums wrote: Yes. Most users either aren't aware, forget about the existence of it, or don't want to mess with kernel experimental. And most of the time, they'd be right. The Lenny freeze is causing an exception to the usual rule. I personally think both kernels should be is the main experimental section, or even in Sid. But I am not a Debian Maintainer. Given the number of bug reports the kernel packaging team deals with, I can understand why they might not want to make it too easy to get a hold of experimental kernel builds. Besides the more testing there is of the lenny kernel before release, the better. Exactly. That's why 2.6.27 should be more mainstream. To reiterate the thoughts of millions of right-thinking people, 2.6.27 should be the official Lenny kernel. Or at least be packaged alongside 2.6.26 in the final distribution as an alternative. Mark Allums -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Where is the kernel?
Robert Isaac wrote: On Mon, Jan 5, 2009 at 6:25 PM, Lennart Sorensen lsore...@csclub.uwaterloo.ca wrote: On Mon, Jan 05, 2009 at 03:06:18PM -0600, Mark Allums wrote: Exactly. That's why 2.6.27 should be more mainstream. To reiterate the thoughts of millions of right-thinking people, 2.6.27 should be the official Lenny kernel. Or at least be packaged alongside 2.6.26 in the final distribution as an alternative. Well I certainly wouldn't object to 2.6.27 being the Lenny kernel, but I have no say in that matter. That would break all three nvidia drivers currently within non-free, so it is not necessarily a good idea for the people that rely on those for a desktop. The you say! Is this why I can't get X going under vanilla 2.6.28? Any word on the ETA of the fixing of the breakage? What's the deal, anyway? The nVidia blob installer tries to make like it can't find the kernel headers, nor the compiled output. Mark Allums -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Machine died
. Is there a recommended card (from the point-of-view of the debian-packaged driver support)? Thanks for the advice, Gilles Uh, 8000, 9000, 260, 280 is supported with the nVidia blob. For Debian-approved drivers, 7000-series. ATI drivers are open source, now, but have not matured yet. nVidia has the edge. Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Machine died
Gilles wrote:
Hello.
Three years and a half ago, I bought a machine composed of what I thought
were good quality components:
MB: Dual Opteron MB Tyan Tiger K8W (S2875)
Graphics: Asus V9520 TD (FX 5200) - AGP
Power Supply: FSP Blue STorm (500W)
RAM: Kingston KVR333 (4x256MB)
Ten days ago, I halted the machine after 106 days uninterrupted use.
Strangely, it didn't shut down completely by itself: I had to switch the
main power supply. [IIRC the last line on the screen contained
acpi_power_off.]
Then the machine simply wouldn't start.
After clearing the CMOS, switching on the main PS would (directly, i.e.
without pressing the power button on the tower) start all the fans, and
all LEDs are on (power, HDD, CD). But nothing more happens (no boot).
A LED display on the MB indicates FF. Removing all the extension cards
doesn't change this behaviour.
I also tried another PS but that one doesn't even start the fans, which
seems the correct behaviour (?) but I cannot be completely sure.
Then, we discovered that the fan of the graphics card had burnt!
Could this be cause of the MB not working anymore? Visually there isn't
any sign of other burnt components on the MB.
I sent an email to Tyan last Friday; they haven't even acknowledged
receiving it... And their web site warns that you shouldn't send a message
twice lest you want that they answer even more slowly. Really nice.
One last thing I wanted to try is to have the BIOS chip reprogrammed (in
case it was somehow corrupted during the problem, whatever that was). But
no one offers this service here (Brussels) and the reseller is not really
helpful either...
So, it seems that after less than 4 years I am obliged to buy a new MB and,
consequently a new CPU (while we are otherwise still using an 8 years old
Athlon machine!). And a graphics card.
So I come here for:
1. Suggestions about the possible cause of the problem. Is there anything
else I can do to know what went wrong (if not repair)?
2. Advice on what to buy (CPU, MB, graphics and RAM) since it is doubtful
that I will get any help from Tyan.
With the usual provision: Everything must work with Debian GNU/Linux,
especially:
- Audio: both play _and_ recording (on the ThinkPad laptop I recently
bought, recording doesn't work: The chipset is not supported by the
kernel).
- 3D graphics acceleration
- Network
And, are there makes that offer longer warranty?
Thanks for reading my lament. :-{
Best regards,
Gilles
I am thinking, no BIOS reprogram necessary. Power Supply is always a
good guess. I think it is time for a new system, but don't completely
give up on the old one. Build a new machine, and when it is up and
running, go back and see if the old one can be salvaged and put to good use.
Build the new machine using an Intel CPU this time 'round, whether it
was AMD or Intel before. Core 2 is your best bet, A Xeon for servers or
multisocket workstations. It is too soon to buy Nehalem, if you need to
buy it today. If you can wait three months, consider a Core i7.
Almost any wired network NIC will do. The onboard ones are probably
supported by Linux.
Get a 80+ PS, meaning a PS that is at least 80% efficient. If you use
it in an office building, or business, get one with power factor correction.
For a personal desktop machine, if 3d is necessary, nVidia or AMD/ATI
both will do. AMD recently had its fiasco with the midrange chips. You
may with to go with the red team (ATI) this time, until nVidia gets its
act together.
An Intel motherboard (I mean the motherboard itself is Intel) is
generally supported well by Linux.
This is general advice. For specific advice, often the enthusiast
magazines are a good place to start.
Mark Allums
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: task hald-addon-stor:2815 blocked for more than 120 seconds.
Lennart Sorensen wrote: On Sun, Oct 26, 2008 at 09:05:42PM +0530, Vikram Vincent wrote: The following messages keep repeating at regular intervals and I am not sure how to deal with them or to ignore them. Any suggestions will be useful. Thanks. Vikram Vincent I have seen similar multi minute hangs on my Q6600 running amd64 with 2.6.26 kernel. I have no idea what caused it to start happening in 2.6.26. I am now running with nohz=off highres=off which seems to have made the problem go away. 2.6.25 and earlier never do it. It also seems to always be related to disk IO. I am seeing hangs due to excessive disk activity when Epiphany browser has been running for too long. I close it or kill it, and switch to Iceweasel, and the problem resolves. Of course, Iceweasel has its own issues. This may not be related, but it is a recent phenomenon. Since I switched from 2.6.25 to 2.6.26. Dual-core Athlon 64 X2 4800, 4 GB. Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia and latest unstable kernel image, now [OT]
Lennart Sorensen wrote: On Thu, Jul 17, 2008 at 06:26:19PM -0500, Mark Allums wrote: A brief description of the Debian way is in the Debian documentation, if you have that installed. It requires quite a few packages, and it depends on the Debian patched kernel. If you use the vanilla kernel, you may need to use the standard way. I have used it on plain kernels many times. I have never seen any indication it requries any debian patches. make-kpkg doesn't seem to care. That's good to know. Although, I think that there is an issue. I get a series of 'modules.dep' file not found-type error messages early on boot. I have been wondering if it is something I have done wrong, or there is something wrong with the build process. The system still seems to run perfectly well after the init process completes. I only get that message when I build a custom kernel. A kernel image from sid installed through apt boots fine. This may not be an AMD64 only issue, thus OT. Am I missing something? Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia and latest unstable kernel image
Lennart Sorensen wrote: On Wed, Jul 16, 2008 at 07:36:35PM -0500, Mark Allums wrote: It is hard for someone to package up something for Redhat, SuSE, Slackware, Debian, and so on. Debian is a particular challenge for them, apparently. Which is odd given it has by far the nicest tools for making packages. Making rpm's is hard and has to be made for each distribution. A debian package will often work on many different debian based distributions. True enough. Although that is not universally true. Ubuntu people should not use Debian packages, and vice versa. Isn't the current 173 driver version new enough for you? Did nvidia go and release 177 as stable already? I am using a(n nvidia) patched 173. Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia and latest unstable kernel image
C. Ahlstrom wrote: The kernel has its own location for files so it isn't usually a big deal, although using make-kpkg (from kernel-package) makes it trivial to have your own kernel installed using the package system. 0. make mrproper 0.5 cp /boot/config .config 1.make menuconfig 2.make 2.5 modules 3 make modules_install 4.depmod -a 5.mkinitramfs 6.make install copy files to /boot modify grub/menu.lst THe only part that bugs me is the menuconfig. I'd really like to make a kernel that builds /only/ the parts my laptop needs, but I have no idea what comprises that set! You are missing a few steps. I have modified your list, a bit. There is another way, the Debian way, that makes it almost trivial. It requires the Debian kernel package and the Debian kernel tools. If you run gnome you can substitute make gconfig for make menuconfig. much better. You can copy the old Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia and latest unstable kernel image
Mark Allums wrote: 0. make mrproper 0.5 cp /boot/config .config 1.make menuconfig 2.make 2.5 modules 3 make modules_install 4.depmod -a 5.mkinitramfs 6.make install copy files to /boot modify grub/menu.lst 2. should read make bzImage 2.5 should read make modules. Although, if you use just make, the bzImage and module are made in one step. I like to make them separately. Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia and latest unstable kernel image
C. Ahlstrom wrote: Thanks! I'm pretty sure the modules_install target does depmod for you, though. It may do that now. Just like make does the equivalent of 'make dep' for you now, so you can skip that step. Anyway, the procedure is pretty straightforward and I no longer have to consult notes to do it. I missed an opportunity to try it the Debian way recently, when I did a full reinstall dang. A brief description of the Debian way is in the Debian documentation, if you have that installed. It requires quite a few packages, and it depends on the Debian patched kernel. If you use the vanilla kernel, you may need to use the standard way. Linux fluxster 2.6.25.10-ca #1 SMP Wed Jul 9 18:17:49 EDT 2008 i686 Yes, I see you are using a vanilla kernel. I usually can wait for the Debian package. Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia and latest unstable kernel image
Lennart Sorensen wrote: Using the nvidia installer is a terrible idea in the long term. It overwrites files that the package system owns, and the package system will take them back someday, breaking the nvidia driver in the process. Just remember how broken windows tends to be. Then remeber windows allows all sorts of people to make 3rd party installers that overwrite system files in the install. Those two issues are related. Just say no to 3rd party installers. Thanks for that, I am forewarned. However, my point was really about the newest driver working well with the newest kernels. I am not a particular fan of nvidia, per se. (I would like to see them release some of their software as free and/or open sourece.) 3rd party installers are not as a category the problem; the problem is individual software developers not taking the time to do things right. This is a definite issue that Linux is going to have as long as there are different distributions. It is hard for someone to package up something for Redhat, SuSE, Slackware, Debian, and so on. Debian is a particular challenge for them, apparently. I do not run my particular setup as a production system. It won't cost me much time or any productivity to have to fix it when things finally break. So, I don't have to wait for a Debian maintainer to get around to packaging up the solution to my current problem. Your advice should definitely be heeded by someone who is more dependent on their machine being up most of the time. I will keep this in mind when giving out info or advice from here on. Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia and latest unstable kernel image
Hi, I still cannot use the new 2.6.25 kernel due to this problem with nvidia module, even with the recently available linux-headers-2.6.25-2-amd64 and image packages. I'm starting to think that these don't work with my card anymore. If anybody has any further tips, I'd be grateful for them. Thanks. The kernel and the nvidia driver didn't get along at first, but the latest kernel patchlevel and the latest nvidia driver version now get along swimmingly. So make sure everything is up to date. Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia and latest unstable kernel image
Seb wrote: On Tue, 15 Jul 2008 15:14:26 -0500, Mark Allums [EMAIL PROTECTED] wrote: [...] The kernel and the nvidia driver didn't get along at first, but the latest kernel patchlevel and the latest nvidia driver version now get along swimmingly. So make sure everything is up to date. Thanks for the feedback. Are you referring to sid or experimental packages? Lenny/testing with a sid kernel, at my desk. Any 2.6.25 kernel that has problems with nvidia drivers was sid/unstable at the time. I had the problem here on a 7800GT when I moved from 2.6.24 to 2.6.25. I was patient, and they went away when nvidia released their latest driver. I'm using 173.14.09 right now, it's on the main download page for non windows and betas on the nvidia website. Works great. Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: laser printer that is very reliable that runs well under debian.....
Michael Fothergill wrote: Dear folks, I bought a Samsung ML-2510 laser printer a while ago and drove it under Debian Etch and now Lenny. It seems to have developed a fault of some sort. The manufacturer says that I can run diagnostic software under either Linux (so it says) or MSWindows that might give me a hint as to why it is freezing up. I don't think it is a paper jam. I could mess around with this but I am very busy. So very busy that it is cheaper in time and money to simply buy a new printer to solve the problem. The printer cost me $100 or so. If I spent e.g. $1000 on a printer solely with the intent of finding one that is very reliable that Lenny will drive well and smell malfunctions and diagnose what they are really well (better still the printer itself has a display on it that gives copious details of any error on it indepedently of the operating system that is driving it that anyone could understand quickly), what printer would you recommend? I am beginning to understand why people buy printers from Xerox etc. Regards Michael Fothergill My experience with Xerox is that they are overpriced and finicky. HP is not my favorite brand, but they do have good linux support now. They get credit for having some of the very best laser printers in the early days, although I can't say anything about today. Still I would give them consideration, since the linux drivers are mostly open source and mostly free. Or at least widely available, including Debian support. Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: C.P.U. suggestions.
Chris Wakefield wrote: Greetings all. I'm planning to build my next power machine, this time I may go with a Core Duo, but I looking for some suggestions and CPU stories from Y'all To my dissappointment my 'AMD 64 X2 Dual Core 3800' has been a ho-hum experience; don't know if it's the scheduler with the default debian compile that seems to effect the performance, but it's certainly nothing to write home about. .I actually found my original AMD 64 Processor 3200+ (the one with 1 MiB L2 cache) to be probably the best CPU I ever had and I think just as capable as my X2. So, I'm wondering about the Core Duo family and which is best for the desktop? (I've built about 3 machines for clients with these CPU's and they seem very snappy. I'm even talking about the 1.8 MHz variety). I'm also wondering about alternate CPU's as well and what suggestions anyone has about those as well? Any Suggestions? Thanks, Chris W. Make sure your BIOS is up to date, you need BIOS support to run a dual core CPU on the old AMD boards from around the time of the transition to dual core. Then look for an Opteron 185 on eBay. Almost the fastest non-FX socket 939 X2 CPU. Again, make sure the BIOS support is there. Or, you can buy a new motherboard and go Intel Core 2. They are seriously fast. Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Apology - Re: ignore
Mark Allums wrote: test ignore Apparently some people object to tests of this nature. I am sorry for committing this offense. I will not repeat it. In my defense, I cannot in good conscience recommend GoDaddy or secureserver.net as an email provider, due to the way they handle spam. If you use them, you can expect to get many legitimate email messages blocked or bounced. I believe they are doing this to many of the debian lists' messages, including the debian-amd64 list. Service has improved some since I whitelisted the list server and the list email address, and added it to the GoDaddy webmail address book. Some messages may still be blocked. (It's hard to tell.) Be warned. Thank you for your patience. -- Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ignore
test ignore -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel: APIC error on CPU0: 40(40)
Karl Schmidt wrote: Apr 10 10:54:02 poland kernel: APIC error on CPU0: 40(40) I see this every once in a while - no problems with the server and others on the web see it only on amd64. Any kernel gurus know exactly what this means? Not a kernel guru by any stretch of the imagination, but I used to see it on my 64-bit, dual core systems (nForce 4 mb) (running 32-bit Linux kernels). Also saw it on a dual-socket system socket for 370 Celeron.* With 64-bit kernels, the whole system locks up during the boot init stuff. I think it means your motherboard has a broken BIOS, usually. (APIC implemented badly.) On mine, I run with the kernel parameter noapic, which seems to do no harm. Mark Allums * Yes, I had one of the legendary Abit motherboards that did dual socket 370 Celerons before the Pentium III came out (and it wouldn't do the Pentium III, it had voltage issues.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Hey everyone, GUI isn't working; I can't figure out how to configure my xserver correctly.
Lance Ferrer wrote: Im getting XIO: Fatal IO error 104 (connection reset by peer) on X server :0.0 when I try to boot debian. I'm new to linux and computers in general, so any help would be great. I have a BFG NVidea 8800 GT if that helps. If you need any more specs or anything just let me know. The newer NVIDIA cards still aren't supported particularly well by most Linux distros. I have a 7800 GT that won't work right with X anytime I install even a recent Linux distro in a box with that card installed.[1] (Haven't had the guts to try an 8000-series card.) I usually use a 6600 GT for installs, install the non-free[2] NVIDIA proprietary driver available on NVIDIA's web site, and then switch out cards. Works for me, although that is not really solving the problem, just working around it. And, it is more work to do that, extra steps and all. Mark Allums [1] Worked great with Fedora 8, though. But I prefer Debian. Doesn't work in vanilla Debian (or Ubuntu). [2] For newbies, the term non-free in Linux usually refers to the software being closed-source or otherwise encumbered by copyright or patent. The binary may be available at no cost to you, like the NVIDIA drivers, but they are closed source, hence non-free. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Graphics cards with Free drivers
Jo Shields wrote: On Tue, 2008-04-08 at 15:49 +, A J Stiles wrote: On Tuesday 08 Apr 2008, Dean Hamstead wrote: Please define most. (That's the driver I'm using on my machine at work, which is fitted with an older nVidia card.) I want to be certain that whatever I buy will work correctly with 100% Free software. SUPPORTED HARDWARE The nv driver supports PCI, PCI-Express and AGP video cards based on the following NVIDIA chips: RIVA 128 NV3 RIVA TNT NV4 RIVA TNT2 NV5 GeForce 256, QUADRO NV10 GeForce2, QUADRO2 NV11 NV15 GeForce3, QUADRO DCC NV20 nForce, nForce2 NV1A, NV1F GeForce4, QUADRO4 NV17, NV18, NV25, NV28 GeForce FX, QUADRO FX NV30, NV31, NV34, NV35, NV36, NV37, NV38 GeForce 6XXX NV40, NV41, NV43, NV44, NV45, C51 GeForce 7XXX G70, G71, G72, G73 The nv driver is alleged to work with 7000-series cards, but it has issues on my systems with a 7800 GT and typically, an nforce 4 chipset Asus motherboard. I have never successfully gotten it to work in that combination. The vesa driver works, but...meh. I choose to use the Nvidia closed driver because it works well and has few hassles. I have no reason to believe than Nvidia will cripple that driver in the future. I will worry about that problem when it happens. Until then, I'm happy. GeForce 8XXX G80, G84, G86, G92 -- Mark Allums -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
