I have had old computers run the CD just fine and then the default install set the screen resolution to high. No mode is supposed to solve that problem but doesn't always.

This is actually an intell M processor.


On 12-11-10 02:23 AM, Jack Chastain wrote:
It isn't THAT old (386!!) - IIRC, it's an P5, and it runs the LiveCD just fine - so I believe Ubuntu should run on it once I get the disks worked out properly.

Unfortunately though, it appears either work is blocking the appropriate Dell site, or it is down - so I can't confirm the hardware yet. Sigh. Once this long Solaris SAN migration completes, I can head home and do some REAL work - instead of this stuff I get paid for. (Which, I might add, is supposed to include RHEL, at which I pretty much suck, so it is kind of embarrassing that I need to ask all this in the first place. Sigh.)

JC


On Fri, Nov 9, 2012 at 11:11 PM, Mark Wallace <[email protected] <mailto:[email protected]>> wrote:

    If your system is that old, you might find your best desktop to be
    LXDE.  Lubuntu is a good distro of it. It's a little rough cut but
    it runs like the wind.  The system that I am using originally had
    XP service pack one in it.  If you get kernel panic when you try
    to boot up, it's because your old system is a 386 processor.  If
    you want another desktop, put Lubuntu in it if  you have trouble
    and then use the synaptic package manager to get KDE or Xubuntu
    into it.  If you pick KDE, disable the desktop effects because
    chances are your system can't handle them.  If it keeps coming off
    like you have a bad install, with your task bar disappearing, etc,
    or it hangs, then your system can't handle distros designed for a
    686.  The only Ubuntu distro that will  work with an old system is
    Lubuntu.

    Mark




    On 12-11-09 10:10 PM, Jack Chastain wrote:
    Thanks all - I think Chris may have the correct analysis. This
    third-shift work makes it miserable for me to try anything in a
    reasonable frame, but I will give this a shot soon.

    I believe based on the way things were installed that Chris is
    reading it right - I don't understand why the external USB-based
    disk was the only one I was offered (I tried a few times to
    insure I didn't have a list of three drives - I did not, however,
    with the system up, fdisk clearly sees the other drives) but
    there you go.

    My impression is that - for some reason - Ubuntu installed itself
    to the drive that is not available until the drives for that
    drive  are made available - after boot. Live and learn. Or not.

    The system si a quite old Dell - I think it is maybe going on 10
    years now - and last night, I just got tired of the gradual and
    continual slowdown of the system. I figured the only thing it
    really has is Visio, so I would replace the (even older?) laptop
    and see if I couldn't squeak out a little more performance. Silly me.

    Unfortunately, now I am at work in White Plains and won't be home
    until about 0600 - I guess I will get to play then. For now, off
    to do some reading.

    JC


    On Fri, Nov 9, 2012 at 7:16 PM, Chris Knadle
    <[email protected] <mailto:[email protected]>> wrote:

        On Friday, November 09, 2012 05:30:24 PM Matthias Johnson wrote:
        > Chris,
        >
        > You may be correct but if the internal drive wasnt
        mountable how would it
        > install anything to it?
        >
        > Matthias

        When Grub2 installs the boot sector portion of the boot
        loader into the MBR,
        it does that on the raw device (such as /dev/sda), not a
        filesystem.  When it
        installs the /rest/ of Grub2 -- the configuration, modules,
        etc -- that's done
        on a mounted filesystem.

        --

          -- Chris

        Chris Knadle
        [email protected] <mailto:[email protected]>
        _______________________________________________
        Mid-Hudson Valley Linux Users Group http://mhvlug.org
        http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug

        Upcoming Meetings (6pm - 8pm)             Vassar College
          Dec 5 - Sysadmin Panel
          Jan 9 - High Performance Computing
          Feb 6 - February Meeting




-- Eschew obfuscation and pompous prolixity.

    Light a man a fire, he is warm for the night.
    Light a man afire, he is warm for the rest of his life.


    _______________________________________________
    Mid-Hudson Valley Linux Users Grouphttp://mhvlug.org
    http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug

    Upcoming Meetings (6pm - 8pm)                         Vassar College
       Dec 5 - Sysadmin Panel
       Jan 9 - High Performance Computing
       Feb 6 - February Meeting


-- Robert Mark Wallace
    PO Box 11144
    Newburgh, NY 12552-1114
    Telephone:(845)-541-7396  <tel:%28845%29-541-7396>


    _______________________________________________
    Mid-Hudson Valley Linux Users Group http://mhvlug.org
    http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug

    Upcoming Meetings (6pm - 8pm)                         Vassar College
      Dec 5 - Sysadmin Panel
      Jan 9 - High Performance Computing
      Feb 6 - February Meeting




--
Eschew obfuscation and pompous prolixity.

Light a man a fire, he is warm for the night.
Light a man afire, he is warm for the rest of his life.


_______________________________________________
Mid-Hudson Valley Linux Users Group                  http://mhvlug.org
http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug

Upcoming Meetings (6pm - 8pm)                         Vassar College
   Dec 5 - Sysadmin Panel
   Jan 9 - High Performance Computing
   Feb 6 - February Meeting


--
Robert Mark Wallace
PO Box 11144
Newburgh, NY 12552-1114
Telephone:(845)-541-7396

_______________________________________________
Mid-Hudson Valley Linux Users Group                  http://mhvlug.org
http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug

Upcoming Meetings (6pm - 8pm)                         Vassar College
  Dec 5 - Sysadmin Panel
  Jan 9 - High Performance Computing
  Feb 6 - February Meeting

Reply via email to