To take better advantage of the card, I upgraded to Linux 2.0.36, as found on the Red Hat Updates page. Installation of this was rather tedious, and I won't go into it here. You have to install all the new kernel stuff, usually using the --force option, and remove all the old stuff (I kept the old kernel itself lying around, in case).

You might have to keep a copy of /etc/sysconfig/pcmcia around, since new installs of the kernel-pcmcia-cs package (or something kernelly) seems to install a version of this file that disables PCMCIA. Read the PCMCIA HOWTO for all the details.

8.1 On the LAN

DEVICE=eth0
IPADDR=a.b.c.d
NETMASK=255.255.255.e
NETWORK=a.b.d.e
BROADCAST=a.b.c.255
ONBOOT=yes

Created /etc/resolv.conf:

search ourdomain.co.uk
nameserver a.b.c.f

/etc/sysconfig/network is like this:

NETWORKING=yes
FORWARD_IPV4=false
HOSTNAME=penguin.ourdomain.co.uk
DOMAINNAME=ourdomain.co.uk
GATEWAY=a.b.c.g
GATEWAYDEV=eth0

Under 2.0.34, I needed to do a ifup eth0 manually to bring the network up nicely.

Under 2.0.36, this isn't needed. (Get the kernel-pcmcia-cs package as well!)

8.2 Using the modem

Life's too short to work out why, so I upgraded to 2.0.36, and it works fine on /dev/ttyS3 (although I had to disable the internal modem in the BIOS to avoid an interrupt conflict; see the PCMCIA HOWTO).

"Internal modem is a PCI-based Lucent Technologies winmodem (possibly based on LT Luna PCI chip) and certainly not workable under Linux. Under Win98 with Toshiba drivers it works in Win programs and in DOS window, but it doesn't work in "DOS mode". For some reason it uses IRQ 3 and I/O port 0x2f8 (you can actually set this in BIOS setup), so DOS/Linux think there is a COM2/ttyS1 - but there is no standard UART interface to communicate to, thus no communication. Get a good PCMCIA modem card (I've got 3com "super-combo" 3CXEM556C - 56k modem + 10baseT + 10base2 - and it works great with pcmciacs-3.0.9) and you won't be sorry. The quality of internal winmodem is questionable even under Win98 with Toshiba drivers, at least according to my experience with 56k calls to two local ISPs in NYC."

So there you have it. Forget about the internal modem.

I figured it out: I'm using loadlin to boot, and when I booted after running Windows 98 (using "restart in MS-DOS"), the serial port doesn't show up. However if I boot without running Windows 98 (by booting while holding down the control key and selecting the MS-DOS prompt from the menu) it seems to work fine."

I've noted the following:
My /dev/ttyS0 (major 4, minor 64) is the port on the back of the machine. Kernel 2.0.35 detects 'tty00 at 0x3f8 (irq=4) is a 16550A', which is odd, since I don't have a /dev/tty00 - perhaps it's getting confused. The port works fine with minicom, connected to a terminal.
I also get tty03 detected, which is the Xircom's modem. (/dev/cua3)
Stangely, I can't use minicom to access my modem any more, but PPP works fine?
In Win95, the infrared box in control panel says "Enable infrared communication on COM5, providing application support on COM4 and LPT3)"... ?

I haven't played with suspend/resume on this machine yet, but on my previous Toshiba notebook (Tecra 730) the settings above was all that was needed in the kernel. It also needed apmd with automatic suspend script to perform "cardctl eject" on PCMCIA cards. More on this later ... "

Andrew Mehlos also notes keyboard lockups with > 2.1.100 kernels - this is covered in the RedHat 6.0 section.

Ivo sent in the following for those wanting to try suspend: " If you close the laptop while running X, the laptop will suspend. If you open the laptop again, you will find X hopelessly garbled and you will have to reboot. I had this same problem with my previous laptop, the 490 xcdt, and I found a solution to this problem on the net somewhere, and in case you haven't: here it is...

The basic solution is to swith to a text console before suspending. You can do this by hand but it's nicer to make apmd do it as follows: Create two scripts in (for example) /etc/sysconfig/apmd-scripts, apmd-suspend and apmd-resume.

apmd-suspend contains the following lines (don't forget to make it executable):

#!/bin/sh
# switch to a safe vt. Suspending while in X will crash X
/usr/bin/chvt 1
exit 0

#!/bin/sh
#
# Switch back to vc 7 (hoping that's where we left. If not, tough luck).
# also, unload/reload any sounddriver necessary.
/usr/bin/chvt 7

-s /etc/sysconfig/apmd-scripts/apmd-suspend -r
/etc/sysconfig/apmd-scripts/apmd-resume

[ivo@laptopje sysconfig]$ cat apmd
APMD_OPTIONS="-p 10 -w 5 -W -s /etc/sysconfig/apmd-scripts/apmd-suspend -r
/etc/sysconfig/apmd-scripts/apmd-resume"

ESS Device Manager uses IRQ 11, I/O FC00-FCFF
Gameport Joystick uses I/O 0200-0207
Maestro DOS Games/FM Devices uses I/O 0220-022F, 0388-038B, IRQ 05, DMA 01
Maestro MPU401 Devices uses I/O 0330-0331

Andrew Mehlos tells me: " Flipping through the manual [gasp], it says it's compatible with the Windows Sound System and an SB-Pro; most of the documentation that comes with the kernel source would seem to indicate that it's an OPL3/SA[1x] chipset. (by virtue of being WSS _and_ SBPro compatible, anyways). Hmm. So I check /proc/pci (running 2.2.3 kernel), which knows it's an audio controller, and knows it's revision 16, but doesn't know the Vendor(id 125d) or the Device (1978), and says the IO is at 0xfc00 [0xfc01], and running IRQ 11, like the internal modem, the video card, and the USB port. Huh. However, the 'lspci' utility says it's an ESS controller, with "unknown device 1978" and revision 10 (as opposed to 16). (lspci also calls it a 440BX board; I'm pretty sure it's a 440DX, however). "

He later replied: " Well, I got email back from the OSS people; apparently the ESS 1978 is the same as a Maestro-2 card, which no one seems to support yet, but they said they're working on something for it.

You can however get the SB PRO drivers working by first initializing the card in DOS and then booting linux using loadlin and then configureing either the OSS/Free kernel drivers using the SB PRO definition or you can configure the commercial OSS drivers using the SB PRO definition. The drawback is that you only get 8 bit audio.

We expect to add native (16bit audio) and other support for the ESS Maestro2 card shortly.

... So that's kind of a bummer, since I don't have any DOS disks sitting around, and the isapnptools package doesn't know a thing about it. Argh. I wonder if I can fit the drivers on a minimal floppy disk and still have 500-600k left for the kernel... Hmm. At least we know what it _is_ now, though. :) "

Andrew later replied: OSS has drivers for the Maestro 2E in the latest version from www.4front-tech.com -- I've got sound working on my laptop now... CD's sound great, but the driver is definately still beta... mp3's sound fairly ugly, in all honesty. Hopefully Alan Cox will get the 2E stuff in a -ac? kernel soon. But at least sound is there now.

• The keyboard locks up on reboot:
  1. during installation, select "no mouse"
  2. Andrew Mehlos reports: " One thing I've noticed with the last couple Toshiba laptops I've put Linux on, especially with > 2.1.100-ish kernels is that it seems to disable the keyboard upon powering up. Not sure if it does it with other makes, but on the 4030CDT and the 4000CDS I've used, the trick is changing the BIOS to do Resume on power-up instead of boot, let it boot to the login screen, hit the power button to suspend it, and then bring it back up. "
  3. Alexandro Russo reports: " I am having the same problem; it seems specifically related to 6.0. I haven't had time to find a real solution to this problem; here are a couple of "dirty fixes".
     Select your mouse as PS/2. then, either
     - keep pressing and releasing a key (e.g. Caps Lock) during the boot until the gpm has started.
     or
     - when frozen, put the computer in standby and then turn it on. "
  4. Scott Hunter reports: " [disabling the mouse during install] ... is overkill. All you need to do is when the install asks which services to start at boot you want to disable the GPM service. This is the service that provides mouse support for text based applications. It seems to not like the Toshiba's but I haven't looked into why. Disable it and 6.0 will boot and work just fine. Least on mine it does. :-)"
  5. Honza Jirousek reports: " My case definitely indicates it's PCMCIA. Happened to me with RH6.0 and RH5.2 + PCMCIA 3.0.9 as well. In case of 5.2, i installed it OK without PCMCI card, and after setup of PCMCIA support I got lockups. The /etc/pcmcia/config.opt fixed it - but don't ask me for details, most of the exclude sections are black magic for me. I have 3com Megahertz 3CXEM556 10Mb ethernet/56k modem combo and I thought the problem was with the card - so I searched tip on dejanews and foud this config.
     I never did anything to gpm. But hearing other people, it sure sounds like a resource conflict between PCMCIA card and PS/2 mouse. "
  6. Bobby Cossum reports: " I finally got as far as getting my system up and running with pcmcia support and gpm both going and got minicom to dial my isp. i'm running a 4010cdt, with a 3com noteworthy 56k modem in pcmcia socket 0, suse 6.1, kernel version 2.2.7, pcmcia version 3.0.9, and gpm version 1.17.5.
     What did the trick was getting into /etc/rc.config and setting
     PCMCIA_PCIC_OPTS = "do_scan=0 irq_mask=0xefff"
     Near as I can tell this keeps the pcmcia driver from scanning irq 12 and causing a conflict with the ps/2 mouse.
     What I'd like to know, now, is whether this is eqivalent to setting
     exclude irq 12
     in /etc/pcmcia/config.opts, or, maybe, if I knew the name of the module for my modem
     module "xxxxxx" opts "irq_list=3" "
• Setting the correct mouse device. Bruce Maxwell reports: "After installing your Xserver patch, I had to link /dev/mouse to /dev/psaux for X to find the mouse from your config file."

Date: Sun, 25 Jul 1999 10:59:53 -0300 (ADT)
From: Douglas Johnston 
To: linux-tosh-40xx@geekstuff.co.uk
Subject: [linux-tosh-40xx] RH6 X Accelerated for Newbies

I have been following all the little bits on this mailing list about
installing X on the Toshiba laptop, and gave it a go last night. It worked
beautifully, so I just wanted to help put it all together for all the
newbies that are surveying this list.

Caveat: I have a plain-vanilla Red Hat 6.0 distribution and am running it
on a Satellite 4060XCDT. While these instructions should work for most
recent distros, I cannot verify this, and so you're on your own.
Hopefully, there should be enough information here to get you well on your
way, though. These instructions also reflect what I did: I do not claim
that there may not be better or more efficient ways of doing this. Read
EVERYTHING here before you start.


Quickstart
==========

1) Grab Matt's patched X Server/XF86Config file and install the set.
2) Make sure they're working: tweak the XF86Config as necessary.
3) Grab and install the new XFree86 3.3.4 set.
4) Link the /etc/X11/X to the new SVGA server.
5) Go to the XF86Config and comment out the chipset and noaccel option.
   Add the option "accel".
6) Try it. Optionally, tweak your MTRR.



Full Newbie Version
===================

Install the Gumbley X Server:

1) Go to Matt Gumbley's site and follow the directions for the patched X
server installation. You should know the page anyway, but it's at:
     http://www.gumbley.demon.co.uk/linux-tosh-4030-cdt.html

2) Go into your XF86Config. You may have to change certain of the settings
for your hardware, fonts, etc. In particular, pay careful attention to the
X Keyboard Layout setting, the mouse settings, and the font paths. If any
of these don't jive, you may have to make the necessary changes.

3) Start up your X. You should know then if your XF86Config is correct. If
you notice the screen go black, and then bleed white in from the edges,
hit Ctrl-Alt-Backspace REAL QUICK: you've done something wrong. Go back
and verify that you've followed the instructions to the letter.

4) Once everything is working, you should have an unaccelerated X server
which can be rather slow. The important thing is that it does work, and
work well. If you do not need it to run faster, then you can stop right
here. If you want to continue, back up your working XF86Config and
SVGA_Server files (simply copying them, as in
   cp XF86Config XF86Config.patched
should suffice), just in case something screws up later. Also, note the
time stamp on the SVGA_Server.


Grab the New XFree86 3.3.4 Distribution:

5) If you have a recent Red Hat, you can find the necessary files at:
     http://www.rpmfind.net
   (This is an excellent site for finding almost any RPM you might be
looking for. I am surprised by how many Red Hat users don't even know of
this site yet.) Go into the RPM database, list the packages by name, go to
the X series, and scroll on down until you find the XFree stuff. Many of
the files you need are currently being marked by a little yellow "New"
tag, so they will be easy to find. The files you need are:
   XFree86-3.3.4-2.i386.rpm            XFree86-devel-3.3.4-2.i386.rpm
   XFree86-SVGA-3.3.4-2.i386.rpm       XFree86-libs-3.3.4-2.i386.rpm
   XFree86-XF86Setup-3.3.4-2.i386.rpm  XFree86-xfs-3.3.4-2.i386.rpm
(Keep in mind that these may be superseded by newer versions.)

Install the set with "rpm -Uvh XFree86-*.rpm". If it tells you you need
other RPMs to satisfy the dependencies, and you don't have the appropriate
packages already installed, then you should listen to it and grab/install
those packages as well.

6) If you don't have Red Hat, go to ftp.xfree86.org or mirror, and grab
the 3.3.4 series. Installing these is beyond the scope of this document,
as almost every system differs enough to make an explanation very
complicated.


The Last Steps:

7) Verify that your XF86Config has not been overwritten. If it has, then
replace it with the .patched version you copied earlier.

8) Make sure the link from X (check your /etc/X11 directory) is pointing
at the new SVGA_Server. Check the time stamp on the linked file, and
verify that it is new. You may have to change to link from X to the new
server using a "ln -sf /path/to/new/SVGA_Server /etc/X11/X" if it isn't.
If you don't know what I'm talking about here, please ask the mailing list
for help.

9) Start up X. It should still run, in unaccelerated form. If it isn't,
and you see the white creeping death, hit Ctrl-Alt-Backspace NOW and
double-check that you've followed the instructions.

10) If all is well, then exit X and go into the XF86Config. Comment out
(put a '#' in front) the lines 'Chipset "cyber9525"' and 
'Option "cyber_shadow"'. Change the line 'Option "noaccel"' to read
'Option "accel"'. Save and exit.

11) Start X again. Things should now be accelerated. Grab a large window
and drag it around the screen. You should not be seeing hardly any
repainted of the window and it should be fairly smooth. If so,
congratulations: you have a working accelerated X.


A Last Option?

12) It has been mentioned that the MTRR should be changed for the purposes
of running X, but I have tried it with and without, and have seen no
discernible difference. If, however, you wish to try it, read the
/usr/src/linux/Documentation/mtrr.txt file and set it up as it describes.
For my machine and X (caution: yours may be different!), I use:
  echo "base=0xff800000 size=0x200000 type=write-combining" > /proc/mtrr
As I said, it may make a difference. However, I do not claim any real
knowledge about what this actually does, or how it does it.


I hope this helps someone out there. My own expertise lies in web
development, and while I love using Linux and X, I cannot spend all the
time I would like to get to know these better. Therefore, I caution anyone
following these instructions that they may be inaccurate. Hopefully, list
members will find errors in this before the errors find the newbies. All
the usual disclaimers apply: do this at your own risk.

cheers,
Doug Johnston

• Xircom RealPort REM56G-100. What Matt uses - seems to work fine with no real problems, although I haven't managed to get it to work @ 100Mbps yet.

• Intel Etherexpress Pro 10/100 Mobile. Bruce Maxwell says it's supposedly supported under the latest PCMCIA package.
• Trust 10meg (generic NE2000). Steve Hardy says it works in '98, but isn't recognised in a 4030CDT with RH5.2.
• Paulo Meriggi has problems with a PCMCIA Wavelan.

As a general rule when purchasing equipment that will be used with Linux, don't go for state-of-the-art, as the drivers are probably not ready.

Pros:

• Screen clarity
• Excellent keyboard
• Eraserhead mouse (not a trackpoint!)
• CD-ROM, and bootable too!
• Windows 95/98 dual-install leaves a D: partition free, making installation quite straightforward.

• Internal modem is a WinModem. See http://www.winmodems.org/ for information on why these are Bad, bad, BAD. It mimics COM2, but I couldn't get it working under Linux, and there's probably no chance of it ever working. I disabled it in the BIOS, and use the RealPort modem.
• Cyber9525DVD video chipset not yet officially supported by XFree86, although I have a fix.
• Sound chipset is a little new, and unsupported.

• Get Red Hat 5.2, life's too short to hack 5.1 into usability! 6.0 is good, but there are things to be borne in mind with gpm.
• At least, upgrade to Kernel 2.0.36 and associated PCMCIA package.
• Get my experimental XF86_SVGA.
• Get a real network/modem card. The RealPort is nice.
• Get Jonathan Buzzard's fan control program.

• Kenneth Harker's Linux on Laptops page - Far More Than You Ever Wanted To Know About Linux On Laptops.
• Jonathan Buzzard's Toshiba Utilities, essential for fan control.
• Linux Winmodem Support, keep checking back here to see if we'll ever get support for that internal modem.