This page was started the day the first machine arrived, and is developing.
As they are working sufficiently, they are given to their users, so I no longer have access to the machines (unless they happen to be on the internet, which is rare).
This report is listed at TuxMobil - Linux on laptops, notebooks, PDAs and mobile phones under Toshiba
A user reports
I've borrowed a USB CDROM drive that the BIOS is able to boot off just fine. However, if I try and use the Toshiba recovery CD, it boots the kernel fine (into Windows98) and then fails to see the CD as it only contains drivers for a very specific 16bit PCMCIA (i.e. not 32 bit PC Card) CDROM drive. I've tried a horrid hack using the USB drive to boot and then the VAIO PCMCIA card to try and get at the Win98 filesystem, but the drivers still don't work with the VAIO drive. Reading the Toshiba support site, it turns out that even if you have a Toshabia drive you may need to purchase a special "16 bit cable" to get it to work with the recovery CD.
The CD sounds like a complete and utter crock - It's obviously just a ghost image with a crappy Win98 wrapper to auto install it.
Anyway, I have made some progress. It turns out that RH9 boot CD works fine in text mode (there's no XF86 driver). Booting it up to a shell, I can then bring the LAN up, which seems to work fine.and Rodrigo Castro reports
I bought a Toshiba PCMCIA DVD unit (external Slimline DVD-ROM), I have checked that PCIC="yenta_socket", but I can't make it run in Linux.
Note that the screen appears to show only a section of console window (reed.net says to use `video=vga16:off' but this doesn't work for me). This made running `fdisk /dev/hda' tricky, but my fingers can configure a disk without help from my brain :-)
Set up hda3 as 917-1041 (1GB), hda4 as extended partition, hda5 as 1GB swap,
and hda6 as an LVM partition to hold separate partitions for /tmp, /usr/share
and a `cache' partition we use.
It all `just worked'.
`lspci' knows about most of the devices.
--force')
kernel-module-hostap
ipw2100-firmware
kernel-module-ipw2100
hostap-driver
ipw2100
and modprobe the ipw2100 kernel module,
and without an ifcfg-eth1, it was immediately associated with our AP,
having found the broadcast ESSID which uses no WEP.
dmesg shows:
ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, 0.45See the ipw2100 INSTALL for more details.
ipw2100: Copyright(c) 2003-2004 Intel Corporation
ipw2100: Compiled with LEGACY FW load.
divert: allocating divert_blk for eth1
Detected ipw2100 PCI device at 0000:02:0a.0, dev: eth1, mem: 0xDFDFE000-0xDFDFEFFF -> 53950000, irq: 11
eth1: Using legacy firmware load.
ipw2100: Associated with 'wgb-public' at 11Mbps, channel 1
There seems to be no way to `resume' mode in the BIOS, so the on/off switch cannot be set to suspend.
\Documents and Settings\$user\unix_home),
cygwin
(`mount c:\Documents and Settings\$user\unix_home /home/$user')
and VMWare
(`mount -bind /mnt/hgfs/$user /home/$user')
worlds share the same filespace.
This way Linux has access to devices and full control of the machine. Neat.
I installed Microsoft TweakUI from the Microsoft PowerToys and enabled 'X-Mouse' to get focus follows mouse (rather than click to focus). Rather than using the virtual window manager included with PowerToys, I use 'vern' which seems better once properly configured (there are loads of options).
I've also installed cygwin/XFree86, and found it much improved over the version I tried a year ago. I used 'setup' to install all packages.
I use the 'mount' command in the cygwin profile to mount c:/Documents and Settings/iap10/unix_home on /home/iap10 This keeps all 'user' files under the same subtree.
I start the xserver using 'xwin -multiwindow -emulate3buttons'. This allows Windows and X windows to nicely coexist on the same screen. I have a .bat file in my windows 'startup' directory that starts the xserver, 'xrdb -load .Xresources', starts 'ssh-agent', and pops up a terminal window.
Rather than using windows terminal windows, I find that 'rxvt' works rather better. I use 'rxvt -ls -sl 5000 -e bash' to get a login shell running bash with some decent scrollback.
I found that copying across all my normal .profile, .bashrc and .ssh directories worked just fine. It's also possible to run sshd, but I haven't used this much.
The other thing I've experimented with is VMWare Workstation for windows 4.0. I've installed a RH9 VM (guest) under this, into a 4GB file rather than a real partition. I then installed the vmware tools into the guest, which is well worth doing. I have VMWare configured to export c:/Documents and Settings/iap10 to the guest. It's available in the guest as /mnt/hgfs/iap10 which I then 'mount -bind' to /home/iap10 I end up with a unified directory tree, which is very nice.
I currently have guest networking configured to use NAT, but may switch to using a seperate IP. From the guest, the host always appears as 192.168.57.1 Adding an entry for this in the guest's /etc/hosts is really useful, as it enables you to set the DISPLAY variable such that all windows you create in the guest appear on the hosts' display. I never have to use the vmware console window at all (I start it auto-minimised, and ssh in from the host).
This setup seems to work pretty well for me as I wean myself off Linux and onto Windows...