Subject: RE: Problems with a Pismo
From: Ferwerda Darren (app3dxf) (app3dxf@ups.com)
Date: Thu Jan 10 2002 - 12:09:19 MST
It seems to work in console mode OK. But why would Gnome have a problem
with the Ram count. I have YDL 2.1 running on an iBook 2 as well with 192M
and no problems.
-----Original Message-----
From: Iain Stevenson [mailto:iain@iainstevenson.com]
Sent: Thursday, January 10, 2002 9:17 AM
To: yellowdog-general@lists.yellowdoglinux.com
Subject: RE: Problems with a Pismo
Does it work OK with more than 128K RAM in console mode? Is it possible
that this is to do with X/Gnome and not a RAM issue at all?
Iain
--On Thursday, January 10, 2002 9:04 am -0500 "Ferwerda Darren (app3dxf)"
<app3dxf@ups.com> wrote:
> G++,
>
> Yes, I was wearing a static strap when I changed the RAM. And I
> changed it on a wood table. I checked all of the connections, but to no
> avail. I am almost of the opinion that I have a bad Processor module. I
> will double check all of the connections tonight though. Question, can
> you run the machine with only the ram on the top bank, or does it HAVE to
> have one in the botom bank? Thanks.
>
> Darren
>
> -----Original Message-----
> From: Gavin Hemphill [mailto:hemphill@drea.dnd.ca]
> Sent: Wednesday, January 09, 2002 2:09 PM
> To: yellowdog-general@lists.yellowdoglinux.com
> Subject: Re: Problems with a Pismo
>
>
> Well my Pismo (same specs as yours) has 192meg in it running YDL 2.1
> (and a whole variety of kernels have been used over the last two months,
> from the original 2.4.10-12a through a custom 2.4.12 devel kernel I've
> been using to port to another board). I've never seen the problems you
> describe. The only things I can think of is to question if you were
> using a static strap when you had your machine open to swap memory
> around, or whether or no you moved the HD in the process and made the
> connection flaky.
> G++
>
> Ferwerda Darren (app3dxf) wrote:
>
>> Hello,
>>
>> I have been pulling my hair out with my Pismo. To give some
>> history. This machine was picked up specifically to be a Linux box. It
>> started out as LinuxPPC, but since someone at my local lug (NYLUG) let me
>> install YDL 2.0, I was HOOKED. I have had problems with the ram on the
>> machine since the beginning. To explain. When I have more than 128 megs
> of
>> ram in the machine, E comes to a grinding halt. I mean when you left
> click
>> on the desktop and bring up the menu, as you are moving down the entries
> in
>> the menu, the box cursor that usually follows the arrow trails behind
> really
>> far. This seemed odd, but I brought it back down to 128 megs, and it was
>> fine. This happened in both LinuxPPC and YDL. I tried updating the OF
>> to 4.1.8, but to no avail. The Tech Notes state that the machine can
>> handle
> up
>> to a Gig of ram, but, I have not had good results with over 128. I
>> originally picked up 1 256M module with the hope of getting half a Gig of
>> ram on the machine, but after returning the ram to crucial a couple of
>> times, I went back to 128. That is problem A. Let's move on to problem
> B.
>> I was using the machine about a week ago, after I had gotten
>> everything installed from source that I needed, (isn't this how it always
>> goes) when the power cut out on me. I figured that the worst thing I
> would
>> have to deal with was a fsck, and go on with life. When it came back up,
> it
>> said that the disk was too messed up to check, so it dropped me into
> system
>> maintenance mode. Ok, I ran fsck manually, and it said it fixed a whole
>> bunch of problems. Fine. Gnome panel would not load. I figured the
> binary
>> was corrupted, so I reinstalled 2.1. I wiped the partition, and
>> recreated it (actually, it was installed with 4 partitions, bootstrap,
>> swap, / , /home. I wiped them all). Now, the same problem is
>> happening, panel is
> not
>> loading up, and on vt1 I get a weird message about a Gnome error. I
> booted
>> onto the install disc, and it dropped me into rescue mode. As I said
>> before, I wiped the partitions, and since, have run fsck.ext2 -vc and
>> just about everything else on the drive that I could think of. I
>> figured it
> was
>> a head crash, and that something would show up in fsck.ext2 -c. I am in
>> a quandary about both problems. I have plowed through both the LinuxPPC
>> and YDL lists. I have not found anything like this. If I have missed
> something
>> in the lists, please let me know with a link, so I can go read up. If
>> you need more information, here it is. I did run the Apple diagnostic
>> cd that came with the PowerBook, and it recognized everything, and said
>> everything was working properly. The diagnostic cd does nothing about
>> the HDD
> though.
>>
>
>
This archive was generated by hypermail 2a24 : Thu Jan 10 2002 - 12:24:52 MST