| Introduction
Disclaimer Partitioning Installation DVD/CD-ROM Modem |
Networking
IrDA Sound APM USB Links |
The XG9 uses the same NeoMagic Magic Media 256AV 128 bit 2.5 meg video used on earlier PCG-F series, and the same Yamaha DS-XG sound used in the F430 and F450. The newer XG models appear to use the NeoMagic 256XL, and have a larger (14.1") LCD panel in addition to a faster processor.
See David Efflant's excellent write-up on the Sony VAIO F-series. I owe my easy success and the format of this document to his notes.
This model came standard with 128 meg RAM, 13.3" TFT 1024x768 display, DVD/CD, and removable floppy drive which can be replaced with a weight saver, optional second battery, 10GB removable hard drive, or CD-RW. It can be expanded up to 256 meg of RAM by replacing the 2 64MB modules with standard 128MB PC100 SDRAM modules. Unfortunately, since it comes with both slots full, at least one must be removed to expand it, so buy as much memory as you think you'll need up front.
A mini docking station is also available which you need to bring out some of the ports (serial/control-A1, S-Video, optical digital) that aren't on the main unit. The removable floppy drive can be attached to the notebook or the docking station via a provided cable that also brings out the parallel port. With this cable, it is possible to have both the DVD/CD (internal) and floppy (external) attached simultaneously. This is generally unnecessary, since the BIOS will boot from the DVD/CD. There are USB and FireWire (i.Link, IEEE 1394) ports on both the main unit and the docking station, though the documentation implies that both FireWire ports can't be used at the same time. There is an IrDA port on the back of the notebook. Win98 Device Manager shows 2 IrDA devices, but I'll be darned if I can find a second one.
When running Windows98, the unit seems to get a good honest 5+ hours out of 2 batteries, when doing word processing, web surfing and the like. I don't have any data yet when running Linux.
The standard hard drive on the XG9 is 18.1 GB split into 2 partitions of approximately 10 GB (C:) and 8 GB (D:) with the 2nd empty partition intended for multimedia storage. (Why they thought Win98 would need 10G is unknown).
If installing RedHat Linux, pay particular attention to RedHat documentation about Server or Workgroup installation and disk partitioning. This may apply to other Linux distributions as well. Making the wrong selection may completely overwrite your current operating system or render it unbootable.
I shrank C: (hda1) to about 3 GB, and put in a ~16MB /boot adjacent to it in hda3. I stretched the Windows extended partition (hda2) down to fill the rest of the new empty space, then expanded the D: partition (hda6) to about 10 GB for shared data space between Linux and Windows. I inserted a 2.5GB Linux ext2 partition for the Linux root. Partition Magic refused to create a Linux Swap partition bigger than 128MB, so I just left that for Disk Druid.
Put the RedHat 6.2 CD in the drive, power it on, and go. I selected the graphical install (in hindsight, I think I like text mode better).
It is usually best to select Custom setup and "I want to select all packages". Just be careful about backing up during the install. If you back up too far, almost all of the default and selected packages will be unselected, including major and essential packages. After you select all the packages you want, it will take under 15 minutes to install them from the CD.
The install went with only 1 minor glitch -- even though the graphical install worked fine on the LCD display, the X configuration step could not initialize the display correctly, even though it correctly identified it as the NeoMagic chipset. Even Generic VGA wouldn't work. I left it configured for the NeoMagic, and continued. I forgot to mark the Linux /boot as Active in Disk Druid, so I had to boot Win98 once in order to run fdisk.
Once booted in Linux, X wouldn't start. I booted single-user, and ran the text-mode Xconfigurator. It correctly identified the NeoMagic chipset and it worked from then on.
We all know the sorry story behind DVD. This and the FireWire/DV apps under Windows 98 are why I'll probably keep it as dual boot for a while.
I am currently using a Netwave Wireless Ethernet card, which coupled with the 6-hour battery life, means I can sit in the dining room, in front of the TV, or on the back porch, and work without wires.
For when I'm sitting at the desk, and need to transfer lots of data, I have now purchased a NetGear FA510C Cardbus Fast Ethernet card. UPS delivered, I plugged it in the docking station, powered up the XG9, and it worked. No fuss, no muss. The system correctly configures whichever card (wired or wireless) is plugged in, and sets it up.
The Linux Wireless Tools are useful for any wireless networking setup. The version (20) appropriate for RedHat 6.2 is available there or on sourceforge. I have taken the liberty of fixing the xwireless program contained in the wireless tools package. A patch is available here. This is an (apparently) Netwave-specific program that displays a signal quality bar on the X desktop.
The Linux drivers for this card are much better than Netwave's drivers for Win98 and Windows For Workgroups (I've also used this card on an older Winbook that went to computer heaven a week after I installed RedHat 6.0 on it last fall). The Windows drivers have a horrific memory leak, such that if I leave the machine idle for a day, it won't do anything, including shutdown. Also, the silly thing frequently doesn't initialize correctly on startup or un-suspend, and I have to eject the card and stick it back in 5 or 10 times before it starts. (Windows 98 provides no "restart card", only "stop card".) The Linux drivers work first time, every time.
Acquire the drivers, library, and utilities from the
ALSA project.
The drivers needs to be 0.5.10b or better (2001-01-23) for the
Yamaha DS-XG support (the YMFPCI driver).
Deconfigure all sound support in your kernel
You then have to go through a 3-step install for ALSA, in the following order:
./configure make (as root) make installThen, you have to provide the system with module configuration file. The sound portion of my /etc/modules.conf is here. This file includes compatibility with all the OSS device interfaces. Tack this on the end of your file, and make sure it contains no other "snd" or "sound" configs. Then, assuming you don't use DEVFS, you need to populate /dev. Run the snddevices script:
(as root) ./snddevicesThe only tricky part is that you need to un-mute the sound channels before they'll make any noise. There is a script provided that you can out into /etc/rc.d to automatically handle startup.
As far as hot keys, Fn-Esc (suspend) and Fn-F12 (hiberinate) both put it into deep suspend. Fn-D (display off) and Fn-S (idle standby) do not do anything.
Initially I had trouble with the system locking up when coming out of suspend, but found that the USB workaround suggested for earlier kernels was not necessary. I did have to set the PCMCIARESTART="yes" in the /etc/sysconfig/apmd configuration file.
I was playing with a suspend-to-swap space patch from Gabor Kuti available on his web site. It appears to work, though I can't seem to get the Magic Sysrq key sequences to work. Configuring it to override APM suspend makes the Fn-Esc key sequence suspend-to-disk rather than to RAM. I'd like to be able to do either, with different hot keys. This code appears to be sporadically maintained, and has not been updated for 2.4 kernels.
I tried out the ACPI4Linux code, but other than disabling APM, it doesn't actually do anything. It appears to correctly identify the ACPI capabilities, though, so there is hope.
In addition, I have now acquired a D-Link DSB-C300 USB video camera. This is an ov511-based camera, which is well-supported by Mark McClelland's ov511 driver as a Video4Linux grabber in the 2.4.0 kernel. So far, I have successfully used xawtv to look at myself, and ohphone to connect to a PolyCom video conferencing system and Microsoft NetMeeting 3.01. UCL VIC and qVIX are giving me a little more trouble, as I try to track down the lengthy lists of prerequisites.
I've been unable to perform live dock/undock operations. The system hangs when it comes out of suspend mode after undocking, and doesn't seem to notice the dock on insertion. This is an annoyance, since it means I have to halt the machine first. It may be possible to use the apmd features to do pre/post suspend scripts that disable and re-enable the hardware in the docking station (floppy, PC Card, USB ?) similarly to the PCMCIA restart.
Linux
Laptop Home Page
HOWTO Sony VAIO PCG-F450/F430 Linux
Linux Laptop Hardware
Linmodems
Sony Notebook
Computers
Linux Wireless Tools
Open H.323 Project
Linux-USB