Linux on a Toshiba Satellite 1800-712 (23/7/2002) (update) (update2)

I succeded in installing Red Hat 7.3 on a Toshiba Satellite 1800-712 . My choice fell on RH just because it was the first distribution I had at hand, no deeper reason. All in all, the installation was pretty straightforward and most of the hardware I tested was recognized by the installer so, just out of the box. I'm writing this notes mainly to report that it worked and to note down the few additional post-installation steps which were necessary for me. I didn't yet try out extensively the hardware, but I'd say that the bottom line is, save the winmodem, enough of the machine works well under linux.

Hardware information:

I bought the computer in a chain store in Italy on 10/7/2002. I found no information on the net about this particular -712 submodel, however its configuration is pretty similar to that of other 1800- series Satellites. There is plenty of information about them, and this is why I had a rather easy game.

Main sources of information:

The configuration of the machine, as I got it,  is the following:

Model: Satellite 1800-712

notes

Linux support

HDD_Int:

  Ali M5529


OK

HDD

Toshiba MK2018G AP

18.62Gb

OK

Sound:

  ALI M5451 PCI AC-Link South Bridge


OK

VGA:

  Trident Cyber ALADDiN-T (Cyber Blade XP) 1024x768 @60Hz

memory is shared!

OK

Display

14.1" TFT, 1024x768


OK

CPU:

  Celeron 1100 Mhz


OK

RAM:

 256 Mb PC 100 SDRAM

16 Mb (fixed) are taken by the VGA

OK

Modem:

  Softmodem (Lucent SCORPIO)

AMR, winmodem

NO

IrDA:

  Super IO SMSC LPC47N227


untested

USB:

  OHCI root Hub, ALi M5327


untested

CDRW/DVD

Toshiba SD-R2102 (SCSI)


OK

PCMCIA:

  Toshiba ToPIC95


OK

APM:

  V1.2


OK

Mouse:

  PS2


OK

ACPI:

  V1.0b



Chipset:

  ALI M1533 ISA, M7101PMU, M5247 PCI Bridge, M1644 Host Bridge



Network:

  Intel 82557


OK

FloppyDisk_Int:

 


OK

Serial port


COM1

OK

Parallel port


LPT1/ECP

untested

Video out



untested


(untested means only that I didn't test it. Check at the above mentioned links for further information)

Linux installation notes:

The Red Hat installer recognizes most of the hardware. I had to choose manually only in a couple of occurrencies:

partition table:# /sbin/fdisk -l /dev/hda

Disco /dev/hda: 255 testine, 63 settori, 2432 cilindri
Unità = cilindri di 16065 * 512 byte

Dispositivo Avvio    Inizio    Fine   Blocchi   Id  Sistema
/dev/hda1   *         1       800   6425968+   b  Win95 FAT32
/dev/hda2           801       813    104422+  83  Linux
/dev/hda3           814      2432  13004617+   f  Win95 Ext'd (LBA)
/dev/hda5          1801      2350   4417843+   b  Win95 FAT32
/dev/hda6           814      1800   7928014+  83  Linux
/dev/hda7          2351      2432    658633+  82  Linux swap

Partition table entries are not in disk order


The rationale for making /dev/hda5 a Win95 Fat32 partition was to have a common exchange area between two OSs. I'm quite skeptical about this necessity, however, and I might change this scheme later.

Post install fine tuning:

Accelerated trident driver:

A direct replacement for the video driver is available at http://www.xfree86.org/~alanh/ . As the kernel provided with RH 7.3 is 2.4.18-3, i.e. advanced enough, it is sufficient to replace /usr/X11R6/lib/modules/drivers/trident_drv.o and to restart the X server. I didn't perform specifical speed tests, as a rule of thumb I'd say that dragging a solid window across the desktop is twice as responsive as before. However, the replacement driver has problems with the out-of-the-box libmpeg. With this driver, noatun / kaboodle / plaympeg drive the card to an unusable mode whenever I try to display mpegs, and I have to reboot to recover.

Post-install changes

Software added out of the distribution:

Software of the distribution which didn't work for me:

Remaining hardware/software issues:

Modem:

The soft modem, based on a Lucent SCORPIO chip, is marked as non-supported even by www.linmodems.org.

Mouse and sound after suspend

apm works and is able to put the computer in suspend mode, etiher calling apm -s from the shell, or choosing from a graphical menu like that of gdm or klaptop . However, after resuming the sound server of kde is either jerky or mute, and some of the mouse actions are crippled. In particular, it seems that tap-touchpad is not anymore processed as a mouse click, it is not possible to point and drag, and so on. I didn't understand to which extent the BIOS is to blame and to which the upper layers. However, adding these lines to /etc/sysconfig/apmd , the sound behaves better (in the next window manager session):

RESTORESOUND="yes"
RESTORESOUNDPROGS="yes"
SOUNDMODULES="sound sr_mod trident ac97_codec soundcore"

The mouse behaves normally after a kde logout/login, which hints at a problem solvable within kde.

Reboot

Sometimes a reboot from linux shuts correctly the system down, but then freezes the machine with a black screen and the fan at full power, while some other time the process works perfectly. I understand that it could depend from either the BIOS settings or amd, but didn't yet isolate the reason and its cure. I observed that reboot succeeds if the machine has been suspended and revived. I've seen the problem reported for another Satellite in dejanews. When the machine freezes, the only choice is to press for 1 second the power button; then the machine peeps for the next 15 seconds, and finally powers off. A further press of the power button turns the machine normally on again.

External mouse

Hot plugging an external mouse is ok, but hot unplugging leaves the trackpoint unseen until the next X server restart.

Hard disk mode

CDRW/DVD

I have been able to read and to burn CDs (used koncd). I didn't find yet a software suitable fror playing DVDs.

Extended keys

F-keys and Fn-F1-F5, Fn-F10-12 work just out of the box.
Note that Fn-F2 switches between the "Battery Save Modes" , thus affecting the performance of the hard disk .  The current mode is hinted by the brightness of the screen, which becomes a little dimmer in  "Low power".
Fn-F5 blacks out and revives the screen, I suppose it is switching between internal and external video.
I didn't experiment with the exotic "internet key" or with the "cd player keys" out of the keyboard; it is quite possible that they can be made usable for some real purpose.


Update - 8/9/2003 (perhaps will be expanded someday)

Since then I have succeeded upgrading to RedHat9, but I didn't have had the patience to sort out once more all the miscellaneous problems. I.e., sound is slightly worse, I tried but not succeeded to recompile a new kernel with UDMA5 support, there are problems of random sleep, didn't try out the network, and so on. I read on the net that things in reality improved, it's just that I didn't invest time in fine tuning. Say, the softmodem should now be operable. I have been able to play DVDs, trying out various different versions of xine and ogle, but alltogether the result was quite jumpy (up to ~12fps, which allows to see something but falls behind). I'm told however that the right combination of X driver, kernel, library does.
Useful links:



Update - september/october 2008

By now the laptop's batteries are almost gone [they are reported as 100% full, but last only 10 min at most, likely sign of one element with reduced capacity, unless the ACPI went nut], and the key 'g' triggers almost spontaneously. I wanted to give the last chance to the old beast, installed Xubuntu 8.04 off the single cd i386, and kept populating the software as soon as the ADSL network was up. That practically resurrected the laptop. I was initially particularly happy of the lightweightedness of Xfce (I could still run decently off 256Mb with half RAM free), but started to have doubts after populating a little the system software and the xfce panel applets. However, practically everything I've tried so far worked out of the box, which is remarkable.

Only one thing required a minimal post-install tweaking - the video card is not recognised automatically, and the display gets stubbornly into 800x600 vesa mode. The cure is amply described in the ubuntu forums (e.g., in this thread and this thread). For me, I simply needed to know that a) the configuration program is called displayconfig-gtk; b) you have to save the resulting xorg.conf somewhere, and then to copy it in /etc/X11.

Video output would then come shifted by 4 pixels to the right, leaving a tiny black bar at the left of the display. What fixed it was setting the initial text mode to a higher resolution, like appending vga=791 or vga=773 to the kernel options in /boot/grub/menu.lst (which takes the place of /boot/grub/grub.conf in other distros). I had no success in fixing this by playing with either Modeline or Option XvHsync in xorg.conf, which I initially tried, and anyway the higher text resolution is just nicer.

As for other kernel options suggested on jxh's page, which I was using in the past:

As for other peripherals:

Well' I heard well of Ubuntu...

Things I'm not yet happy about

Video driver related

I remember that I made several attempts at the time, swapping various trident kernel models I got with different distributions and on the net. With the new installation I'm running again in familiar problems, but I don't remember/didn't really document how I solved them at the time.

The idea is to have them working as handled by gnome-power-manager, since gnome-power-manager can be used as toolbar applet, which is convenient, the effect of events like closing the lid or pressing the power button can be configured, and all is neatly integrated in the gnome session. Out of the box, these are the problems:

# hdparm -i /dev/hda

/dev/hda:

Model=TOSHIBA MK2018GAP, FwRev=M1.42 A, SerialNo=42C75599T

Config={ Fixed }

RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=46

BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=off

CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39070080

IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}

PIO modes: pio0 pio1 pio2 pio3 pio4

DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2

UDMA modes: udma0 udma1 *udma2 udma3 udma4 udma5

AdvancedPM=yes: unknown setting WriteCache=enabled

Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5


What Tomas Pospisek reports differs in that Config is { HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }, BuffType is DualPortCache, BuffSize is 1768kB, tPIO min: is 240. The last two lines of the hdparm report are also somewhat different, bu that might be due to different formatting of hdparm across versions. Either his laptop had a better disk than mine, or there is some parameter I don't know how to set (more likely, as I noted above that I remember having seen a report about 120Mb/s once in Windows). I can set MultSect=16 with hdparm -m, but that alone doesn't help.

Serial port not working

I've just discovered this (11/1/2009). The problem is documented (this question and this bug entry), and apparently due to the kernel confusing the infrared port with the serial port. I've tried a few kernels (2.6.24-3, 2.6.24-19, 2.6.24-23) during the process of updating them, but none works.

The symptom is:

echo blahblah > /dev/ttyS0
/dev/ttyS0: No such device.

Additionally, /sys/bus/platform/devices/serial8250/tty/ shows ttyS1, ttyS2, ttyS3, but no ttyS0. The serial resource indeed appears under /sys/bus/pnp/devices/00:0a (not 02 as reported for other laptops).

One of the proposed workarounds for other laptops is to disable IR related stuff in the BIOS, but I don't find any related entry here.

Another proposed workaround is to “bounce” the port by writing 2 and then 0 to /sys/bus/pnp/devices/00:0a/power/state, but this virtual file does not exist in my installation.

Passing the boot option pnpacpi=off, I do get a dmesg line

ttyS0: LSR safety check engaged!

whenever I attempt to access the port, and some setserial help message at boot (as if setserial was called with wrong parameters, have to check what is really in the init.d script) which I haven't yet been able to read.