[SMAUG] Caldera Workstation 3.1

[Rick Moen]

begin Calvin Chu quotation:

> I was able to install Linux using text-only installation.  Where that gets
> me is a non X11 situation with just a text console. 

So, X11 setup is one problem you're facing.  This is complicated by the
fact that you've given us _no idea whatsoever_ what video chipset this
laptop has.  You've said only that it's "the Winbook laptop".  You
didn't even say what model of Winbook.

Your next logical step would probably be http://www.linux-laptop.net/ , 
where you can probably find general Linux installation information
specific to your model.

Given some idea about the video chipset, I can usually help people
configure X11, though it's easier in person.

> After logging in, the system will run for 10 minutes before locking up.

(This is problem #2.)

That suggests that the system is going into sleep mode, and the kernel
you have gets freaked out by power-management shutdowns.  See if turning
off power-management in the system BIOS Setup screens makes this symptom 
go away.  (I am _not_ saying you won't be able to use power-management; 
I'm saying you should try disabling it as a diagnostic step.)

> This situation never seemed to happen on windows.  I can sit there all day
> doing stuff and not have a freeze.  The odd thing is when it freezes, half
> the time the screen blanks out, and the other half it just locks up tight.
> I tried running "top" and letting it sit there updating the screen, and then
> after a while, the screen goes blank and never comes back.  Not touching the
> hardware doesn't affect it, it will freeze on its own.  

> And if I open up anything graphical (i tried starting X) it will
> freeze immediately. 

The words "it will freeze immediately", here, are vague.  That doesn't help
diagnosis.

Presumably, you have some _attempted_ configuration of X in place --
which may or may not actually image correctly.  You type "startx', and I
assume that something vaguely X-like comes up, but you don't get a
usable X session, and don't know how to reassert control.

When that happens, does pressing Ctrl-Alt-Bkspc (kill X11) do anything?
How about Ctrl-Alt-F1 (switch to text console #1)?

> I'll try text install on the compaq later this week
> when I get a moment.

Remember, in the event you need to seek help, that saying "the Compaq"
doesn't cut the mustard, here.  At the _bare_ minimum, state the model
-- but you really should be providing chipset information, which you get
from the Linux on Laptops site, your technical documentation, the
manufacturer's Web site, Google searches, or wherever you can find it.

If you want help from volunteers, make it easy for us to help you.
We're not mind-readers -- and nobody's paying us to guess.

> On the laptop I piked up an Etherlink 3 from 3Com, a 3C589D.  It turns
> out the 2.4 distribution doesn't support that card.

(This is problem #3.)

The 3C589C (prior model) is known to be fine.  See:
http://www.mobilix.org/pcmcia_ci10301.html

See, the issue is that the card's ID that it reports to Card Services
needs to be in the SUPPORTED.CARDS database that David Hinds, the PCMCIA
drivers guy, maintains.  The 3C589D is _definitely_ in his recent
versions of that list.  See:
http://pcmcia-cs.sourceforge.net/ftp/SUPPORTED.CARDS

On an installed distribution, that list is on file in a text file,
usually /etc/pcmcia/config .  Mine has this entry:  

   card "3Com 589 Ethernet"
     manfid 0x0101, 0x0589
     bind "3c589_cs"

On rare occasions, you have to kick-start the PCMCIA Card Services'
recognition of your PCMCIA card, by editing the /etc/pcmcia/config 
file to reflect the exact identity strings that Card Services will
get from the card.  (Run "cardctl ident".)  And then you say which 
driver(s) to load, for it.  For example, for my Intel combo card, I had
to insert this:

    card "Intel EtherExpress PRO/100 LAN/Modem PC Card Adapter"
    version "Intel", "EtherExpress(TM) PRO/100 LAN/Modem PC Card Adapter",
      "PRO/10 0 M16B", "1.00"
    bind "xirc2ps_cs" to 0

Also, why are you so sure that your 3C589D _isn't_ being recognised?
Did you listen to the beep codes?  Typically, there's one high-pitched
beep when Card Services activates, then a second high-pitched tone for
each card correctly recognised, or a lower-pitched tone for each card
_not_ recognised.

> I don't mean to sound negative, and I'm not going to give up unless there is
> no possible way to get Linux running.  I have an old Redhat distribution I
> picked up from Costco a couple of years ago that I will try to rule out a
> few more possibilities.

If you're still having problems by a week from this Saturday, come on
over the hill to the SVLUG InstalLFest.  We can help you install just
about anything.  (Be sure to bring printouts of any relevant pages you
find via the Linux on Laptops page.)

-- 
Cheers,                             "Ceterum censeo Linux propaganda est."
Rick Moen                                        -- Seth David Schoen
rick@linuxmafia.com