Popularity |
|
Linux and the Toshiba Satellite 4030 CDTAuthor: Matt J. GumbleyCreated: Fri Oct 1 15:52 1999 Last Updated: Mon Dec 30 22:03:36 2002
Abstract This page lists things you will have to be aware of when installing Linux on Toshiba 40xx laptops. It notes changes you'll have to make to the basic installation, and extra drivers you'll need to take advantage of the laptop's hardware. Note: Thanks to all those people who have got in touch with me about this page - it's great to know that it has helped! Table of Contents
1 Changes
2 AcknowledgementsI'd like to thank my employer for allowing me relative freedom of choice when buying a laptop (and for actually buying it!), the maintainers of the "Linux for Laptops" pages for their invaluable advice when choosing a laptop, and to Linus Torvalds, Richard Stallman, The XFree86 Organisation, Red Hat software etc. for developing a system that's actually worth installing on a laptop.Thanks to Trident, whose press release told me that the (unsupported) video chipset was pin-compatible with one that was, enabling me to add support for it in the XF86_SVGA server. Thanks to them for providing chipset info so the server can be extended. This information has been incorporated into XFree86 3.3.5. Particularly, I'd like to thank Scott Hovey and Iming Pau at Trident, Pavel Machek, Dirk Hohndel and Alan Hourihane (SuSE/XFree86) for their support. Thanks to Alan Cox and Zach Brown (Building #3, RedHat) for developing the Maestro sound driver used by the laptop. I also need to thank Bernd Reichert for the NT OS + Linux mini-HOWTO, David Hinds for the Linux PCMCIA HOWTO, Kenneth Harker for the Linux on Laptops pages, and everyone who has contacted me since I released this page - I'd thank everyone in turn, but then we'd never get to the real content! You know who you are - thanks! Thanks should also go to Toshiba who have given in, and supplied information about their IrDA hardware to the Linux IrDA team. IMHO, it's about time that hardware manufacturers acknowledge the importance of Linux. This page is now mirrored at: 3 IntroductionYou can find the full specifications for the 4030 CDT on Toshiba U.K.'s Website.The 4030 CDT works well under Linux. The video chipset is supported as standard under XFree86 3.3.5, available as an update to RedHat 6.0. The sound hardware is available as an add-on, and is available from Zach Brown's pages (@ RedHat).
The laptop has a built-in modem - it's a WinModem, but I'm told drivers are
available.
I chose a Xircom RealPort REM56G-100 PCMCIA network/modem card - this is
supported by RedHat 6.0
4 Windows 95/98 Dual-InstallWhen we bought our Tosh, it came with Windows 95/98 pre-installed, with the option of choosing one and deleting the other.I chose a Win95/FAT16 installation, since my disk repair tools (and the Linux systems I'd been using to that point) didn't understand FAT32. Win NT still doesn't, and since we'd need that too, I had to use FAT16. Red Hat Linux 6.0 supports FAT32. Note that if you choose Win98, the Toshiba setup program will use all 4GB for a single partition, and you'll have to use FIPS to resize it.
Note: If you apply the "rescue" CD, then it'll wipe out everything - including Linux. After install, I found the disk laid out thusly: /dev/hda: 255 heads 63 sectors 526 cylinders /dev/hda1 * 1 1 261 2096451 6 DOS 16-bit >= 32M /dev/hda2 262 262 525 2120580 5 Extended /dev/hda5 262 262 522 2096451 6 DOS 16-bit >= 32M /dev/hda6 523 523 525 24066 4 DOS 16-bit < 32MWin95 was in /dev/hda1, the other two partitions were blank.
5 Preparing the disk for Linux and NTI'd need to install NT 4.0 Workstation on here too, in its own NTFS partition, so decided to remove hda2, 5, and 6, and create three new primary partitions:/dev/hda2 a 1.5GB NTFS partition for NT /dev/hda3 a ~500MB Ext2 partition for Linux /dev/hda4 a 32MB swap partition for LinuxI'll be using the NT boot loader as the first-stage loader. It'll take over the MBR, and I'll have an option in there for Windows 95 and one for Red Hat. This is to be done using the techniques described in the NT OS Loader + Linux mini=HOWTO To prepare the disk, I used DOS' fdisk to delete both logical DOS drives under the extended partition (drives D: and E:), then to delete the extended partition itself. DOS is so challenged that I could not create a second primary partition using DOS' fdisk, so I rebooted with a Linux boot disk, and did it using Linux fdisk. In Linux' fdisk, I created the partitions shown above, then started the Red Hat install. (I did it this way, since I *know* old fdisk, not the new Red Hat disk druid thing!) /dev/hda: 255 heads 63 sectors 526 cylinders /dev/hda1 * 1 1 261 2096451 6 DOS 16-bit >= 32M /dev/hda2 262 262 453 1542240 6 DOS 16-bit >= 32M (gets NTFS'd) /dev/hda3 454 454 522 554242+ 83 Linux native /dev/hda4 523 523 525 24097+ 82 Linux swapNote: I recreated /dev/hda4 - it's the same number of cylinders as the old /dev/hda6, but has more blocks. I could have taken it to cyl 526, but there may be some valid reason for not using the last cylinder on the drive, so kept it at 525.
Rebooted... DOS 95 came up, drive D: couldn't be accessed, but that's OK. (NT
reformatted that later anyway).
Windows booted, which was the main thing.
6 Installing Red Hat 6.0Note: I originally installed Red Hat 5.1 from the Powertools 5.1 set, then gradually upgraded bits of it to 5.2, and now 6.0, so I'm not really qualified to say whether a fresh 6.0 install works fine. You may want to check the old Red Hat 5 page (see address at top) for details.Some points to note:
The following modelines have been reported to me for particular machines:WARNING WARNING WARNING WARNING USE OF THIS SOFTWARE CAN DO PERMANENT DAMAGE TO YOUR MONITOR AND/OR VIDEO CARD. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL MATT GUMBLEY (OR HIS EMPLOYER) OR THE XFree86 PROJECT INC. BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
7 The Internal ModemTo get my Xircom modem working, I had to disable the internal modem in the BIOS. The internal one is a PCI-based Lucent Technologies winmodem (possibly based on LT Luna PCI chip). 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.I'm told by Brian Almeida that Lucent have releaced a binary-only driver for the Winmodem in 40xx laptops that works great with minicom, ppp, etc. It's available here. Jon Wikne posted the following to the mailing list: I am using it with RedHat 6.1. Be sure to get the most recent version of the Lucent program (ltmodem.o), though. > Also, if anyone has any tips on getting it started, I'd appreciate > hearing them. I hacked a small script to insert / remove the ltmodem.o during startup / shutdown. It is installed in /etc/rc.d/init.d/lucent, and linked as follows: /etc/rc.d/init.d/lucent /etc/rc.d/rc0.d/K18lucent -> ../init.d/lucent /etc/rc.d/rc1.d/K18lucent -> ../init.d/lucent /etc/rc.d/rc2.d/K18lucent -> ../init.d/lucent /etc/rc.d/rc3.d/S83lucent -> ../init.d/lucent /etc/rc.d/rc4.d/S83lucent -> ../init.d/lucent /etc/rc.d/rc5.d/S83lucent -> ../init.d/lucent Here is the script itself: #!/bin/bash # # /etc/rc.d/init.d/lucent # # Loads / unloads driver module for Lucent modem chip # 20-01-2000 -- Jon Wikne # Source function library. . /etc/rc.d/init.d/functions test -f /lib/modules/current/misc/ltmodem.o || exit 0 # # See how we were called. # case "$1" in start) # Check if modem is already running if [ -z "`/sbin/lsmod | grep ltmodem`" ] ; then echo -n 'Inserting Lucent modem module: ' /sbin/insmod -f /lib/modules/current/misc/ltmodem.o success echo fi ;; stop) if [ -n "`/sbin/lsmod | grep ltmodem`" ] ; then echo -n 'Removing Lucent modem module: ' /sbin/rmmod ltmodem success echo fi ;; reload|restart) $0 stop $0 start ;; *) echo "Usage: /etc/rc.d/init.d/lucent {start|stop|reload}" exit 1 esac exit 0 One prereuisite of the script is that you have a link in the /lib/modules directory pointing "current" to whereever that is (i.e. which kernel you use). Exactly how you use the modem depends somewhat on what is at the other end (i.e. your ISP, employer or fixed-line computer), but I use the following script (<*> to be replaced by own info): #!/bin/sh pppd /dev/ttyS14 115200 debug connect \ 'chat -v ABORT BUSY ABORT "NO CARRIER" "" ATDT<phone number> CONNECT ""' \ noipdefault ipcp-accept-local ipcp-accept-remote \ user 8 MultimediaI'm using stock RH 6.0, plus most of the latest updates from updates.redhat.com - no later kernel than 2.2.5-15 required, it seems.Downloaded the maestro driver from http://people.redhat.com/~zab/maestro/ (or http://www.zabbo.net/maestro/), did make, and copied the resulting maestro.o into /lib/modules/2.2.5-15/misc I ran sndconfig, but this didn't seem to work 100%, so I hand edited /etc/conf.modules to read: alias parport_lowlevel parport_pc pre-install pcmcia_core /etc/rc.d/init.d/pcmcia start alias sound maestro pre-install sound insmod sound (/etc/sysconfig/soundcard still says CARDTYPE=WSS - this doesn't seem to get used anywhere, or does it? Haven't got midi working yet; not really too bothered) MP3's play; CD's play. Some people still report problems. Check Zach Brown's page above for updates.
Note: You may notice that the maestro driver leaves the mixer settings quite low - so if you insmod it and the sound doesn't make any, then turn the mixer up. 9 PCMCIA (PC Card) CompatibilityThe following devices are known to work with these laptops:
Jon Wikne says: I have done some systematic tests with kernels 2.2.10 and 2.2.12 together with different pcmcia versions and the Xircom REM56G-100BTX Ethernet / modem card. Whether there are problems or not is definitely pcmcia version dependant (not that this excludes other possible dependancies). Here are the results: pcmcia-3.0.9 -> OK pcmcia-3.0.10 -> OK pcmcia-3.0.11 -> OK pcmcia-3.0.12 -> OK, but does not compile on kernel 2.2.12 pcmcia-3.0.13 -> *NOT* OK pcmcia-3.0.14 -> *NOT* OK pcmcia-3.1.0 -> OK I made the pcmcia driver developer Dave Hinds aware of the problems with the Xircom card on 3.0.13 and 3.0.14. Whether it was this report that lead to the 3.1.0 being OK again, or that was a coincidence, I don't know.... Also, the possible impact of pcmcia revisions on cards _other_ than the Xircom REM56G-100BTX I know nothing about. For all I know, those that I label "OK" above might be buggy, and vice versa, in the context of other cards. PCMCIA SCSI is broken out of the box. Using an Adaptec 1460 PCMCIA card, You need a later kernel - 2.2.12-7 has been confirmed to work. Note that when installed, you'll have to more some startup files around, so that PCMCIA is started before the network.
Note: If you install the maestro sound module on RH 6.1, you may find that first time after installing the maestro.o module (insmod etc), you reboot and the PC hangs at the pcmcia module loading (In the case of a 3com ethernet card). If you force quit and reboot, wait for the hda to be fixed and then load inetractively, saying no to the pcmcia module it loads fine only ethernet-less - if you then reboot normally and let it boot all by itself it works fine, sound and pcmcia. 10 Miscellaneous Tips10.1 Getting into the BIOSWhen you power up, hold down the Escape key, you're asked to press F1. Don't change the screen size to 'expand' (wide' inthe BIOS, as Linux will not accept this.10.2 Booting from CD-ROMThe system boots from CD-ROM if you power the laptop off, hold down 'c', and reboot.10.3 Missing pixels, black lines, shifted screen?Upgrade to XFree86 3.3.5 and run Xconfigurator.11 ConclusionsThe 4030 CDT is a nice laptop, great with Win95 (if that isn't an oxymoron), and works very well with Red Hat 6.0, once tweaked.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:
12 References and Resources
|