[00:29] <waltman> jedijf: I'm a lost cause
[00:38] <ChinnoDog> InHisName: TheLordOfTime is right. Your specs dont match your technology.
[02:14] <InHisName> I checked back on mem stick.  Yep this is what is printed on the 184 pin mem stick.  ----  1GB PC3200 DDR CL3 400MHz  184 pin memory for desktop ?    is 184 pin memory not really DDR ?
[02:20] <ChinnoDog> oh, I got it. The 400Mhz was throwing me off. (Clock is actually 200Mhz)
[02:20] <ChinnoDog> I think I have 2gb of that around here somewhere
[02:21] <ChinnoDog> Unless I gave it away. Trying to remember
[02:54] <InHisName> even a single stick of 1GB will work.    One of my sticks got a sticky bit somewhere in it.   Just replacing that one will put me back to 2GB again.
[02:55] <InHisName> It's really old memory.   Best Buy didn't have ANY DDR   just 2's & 3's.
[02:58] <TheLordOfTime> InHisName, im' not surprised.
[02:58] <TheLordOfTime> DDR is ancient-grade technology
[02:58] <TheLordOfTime> EBay'd be your source.
[02:58] <TheLordOfTime> try to find redistributed RAM sticks of that type
[02:58] <TheLordOfTime> i'm not even sure they still *MAKE* DDR
[02:59] <InHisName> I checked, they mostly have ECC and registered and 'High Density'   <---- not for Intel, Sony, Dell, HP, etc.
[03:00] <InHisName> That's why I asked for a 'spare' memory from your old memories bin.
[03:03] <ChinnoDog> InHisName: Run memtest86 and identify the bad memory range and then exclude it
[03:04] <InHisName> How to exclude It?     I asked Sat at PACSLinux and jedijf said to buy another, cant mark bits bad.
[06:20] <InHisName> Got a web site link to tell me how to 'exclude' the bad bits range of a RAM ?
[11:01] <rmg51> Morning
[12:27] <jedijf> InHisName: you didn't ask me
[12:28] <jedijf> InHisName: http://www.pricewatch.com/system_memory/
[12:37] <waltman> Morning
[12:45] <waltman> So my iPad is shipping from Lewisberry, PA (near Harrisburg) and might actually arrive today. But my Smart Cover(tm) is shipping all the way from Shenzhen and won't be here until Thursday.
[12:50] <jedijf> that's good for china
[12:50] <jedijf> my average time from seeed studio in Shenzhen is like 10 days; and I'm happy with that
[12:51] <waltman> I just figured that it would be the opposite -- plenty of local covers but they'd have to ship the device from China.
[12:52] <JonathanD> Morning.
[12:52] <waltman> I ordered stuff from Deal Extreme once. Insane low prices, but the stuff took like a month to arrive.
[12:53] <waltman> Their offices in Hong Kong had to wait to receive things from Shenzhen, then had to ship it to me on a slow boat from China. :)
[13:31] <jedijf> yeah i ebayed something from china took 3 weeks - seeed studio at 10 days gets my china work - now i do north america only for ebay
[13:31] <jedijf> Shenzhen is definitely a place to visit at least once though, it seems
[14:30] <InHisName> jedijf: I originally asked all of you and only ChinnoDog replied, so we had a conversation for a while.   He seemed to think I can mark off bad sections of a RAM and keep using it a bit smaller.   That would save me from spending more $$ on really old stuff if I can really do that.
[14:32] <InHisName> I still eBay to china places provided a month or more wait is fine with me.   Like I use my last spare xyz, so order one from China to come by slow boat is just the right price.  If I did want it soon, then no China orders.
[14:33] <InHisName> Thanks for link to remind me of an old favorite haunt (pricewatch)
[15:04] <ChinnoDog> InHisName: pretty sure that you can pass a parameter to the kernel that will exclude a memory range. I ran a Windows system that way for a very long time. (Window's kernel memory exclusion is not as flexible but I lucked out because the bad chip was at the top of the memory range)
[15:06] <InHisName> Got a link how to exclude for ubuntu, ChinnoDog ?  Being easier than Windows you describe would be real nice.
[15:12] <ChinnoDog> http://ubuntuforums.org/showthread.php?t=860631
[15:13] <ChinnoDog> Ignore those posts about buying more RAM. idk why people can't just answer the question asked instead of suggesting the solution the poster is obviously avoiding
[15:34] <InHisName> Thanks, for the link.   I checked into prices for obsolete memory and frequently an 8GB stick is cheaper than an OLD 512MB one.   Sometimes I have a HIT at the giveaway table at PACS that is nice. Not the last 3 months, though.
[15:41] <ChinnoDog> Just use the memmap parameter
[15:44] <InHisName> Nice the instructions say add memmap param to the menu.lst in grub.....
[15:44] <InHisName> except I am using grub2.0
[15:44] <InHisName> Still reading to see if someone updates comment.
[16:06] <InHisName> Here's a good link for that too, ChinnoDog.   https://help.ubuntu.com/community/BadRAM
[16:06] <InHisName> I says how to do it in grub2
[16:21] <ChinnoDog> That involves building a kernel patch. Is that really necessary?
[17:03] <jedijf> memmap the area - add to grub2 with single quotes
[17:23] <InHisName> That's what the last link says in the grub2 section.  Not kernel messing, just adjust the GRUB_BADRAM= setting in the /etc/default/grub  file     lastly do grub update
[17:24] <InHisName> I'm partway there now.
[17:27] <ChinnoDog> Tell us when you are done so you can amaze us.
[17:31] <InHisName> I did the update-grub and now rebooting.    I noticed that memtest86 is installed according to software center.  How to run from   either gui or terminal mode ?      Issuing memtest or memtest86 did not work in terminal mode.  Nor is it in man pages.
[17:36] <InHisName> booted up, now.    System monitor reports 1.9GB memory.   Is there a way to see how many BYTES I have without the rounding ?   probably a terminal command
[17:37] <InHisName> I had to disable the motherboard RAM testing to boot.   Seems OK so far.
[17:38] <InHisName> I set the sticks so the bad one was in the upper slot.  So the OS is in the more stable stick.   I want to test the upper stick more to be sure I excluded all the bad bytes.
[17:45] <ChinnoDog> I don't think you can do it like that. You can only test all memory and get a complete memory report
[17:46] <ChinnoDog> I would think 'cat /proc/meminfo' would tell you everything you need
[17:46] <InHisName> How many bytes is 2GB memory ?    2x2^9 or 2 billion bytes ?
[17:46] <ChinnoDog> 2*2^30
[17:46] <InHisName> free reports 2030835
[17:47] <InHisName> which comes to 1.936Gigs
[17:47] <InHisName> I only blocked 32Meg (I think)
[17:48] <InHisName> I'll check that meminfo
[18:23] <InHisName> Installed something called 'memtester'.     Now that I've figured out how to do syntax,  It is finding more errors, just not as many as before.
[18:37] <ChinnoDog> Even if you bought more memory there is no guarantee that it would help. In a system as old as yours it could also be bad address lines. Probably best to just make this work.
[18:42] <InHisName> That's another good reason.    Seems the bad memory travels with moving it to the other slot.  So it seems to be more memory dependent than socket addressing dependent.   I think I need to run memtest86 some more to isolate more bad areas.   As long as I don't toss away too much memory in exclusions.
[18:45] <ChinnoDog> Yea, bad address lines.
[23:03] <waltman> *SIGH*
[23:03] <waltman> ENOIPAD :(
[23:09] <pleia2> there there
[23:10] <waltman> I made a typo in my shipping address, so they tried to deliver it somewhere else.
[23:10] <waltman> Now I have to wait until Tuesday or Wednesday. :(
[23:11] <waltman> Fedex doesn't deliver on Monday!
[23:11] <pleia2> doh
[23:11] <waltman> It took me calls to Fedex and Apple just to change the address.
[23:12] <waltman> One scenario is that Fedex tries again on Tuesday, fails, brings it back to their warehouse, and THEN discovers the address change request.
[23:13] <waltman> I don't understand how, in 2012, an address change request submitted 2 1/2 days in advance might not make it in time.
[23:15] <waltman> Obviously it's my own fault for mistyping my own address, but it wouldn't even have been necessary if Apple's order system had an option to ship to the billing address on my iTunes account.
[23:18] <waltman> So I'm a little grumpy. I was all psyched when I saw it was going to be delivered today, but now I have to wait another 2-3 days.
[23:18] <waltman> er, 3-4 days.
[23:23] <waltman> So, like, I kinda feel like smashing something.