(Pictured, Hinoki; name source: the Betterman anime series)
Dell Inspiron 600m
Work in progress. Post any suggestions here.
This machine has many other pages written about it on their owners' trek to get Linux installed upon it. So this page is basically going to mention differences and the machine itself. I'm currently using Gentoo Linux on the machine. Some sparse Gentoo specific information is located at the bottom of this page.
Note: it seems that if you get the built-in Dell Wireless 1350 or 1450, you'll probably also get the Broadcom v.92 winmodem. If you get the Intel Pro Wireless/2100 or 2200, you'll likely get the Conexant v.92 winmodem.
This machine is a lot less friendly to Linux than my Gateway in some respects, better in others. ACPI works without patching on my 600m!
The machine uses i810 AC97 compliant hardware, which OSS uses the i810_audio
driver. ALSA uses snd_inte8x0.
In newer Linux releases you'll be using libata drivers. The ICH4 is supported
directly and both the hard drive and the optical drive will be using the SCSI
API, and thus device=1,0,0 will point to the cdrom.
The optical drive is a Sony CDRW/DVDROM combo drive. It works as an IDE
secondary master, and no issues with ide-scsi when using legacy ATA drivers.
Use device=0,0,0 in cdrecord.
In newer Linux releases you'll be using libata drivers. The ICH4 is supported directly and both the hard drive and the optical drive will be using the SCSI API, and thus device=1,0,0 will point to the cdrom.
Unlike the Gateway's internal modem, which is usable only in 2.4 (2.6 too if
you buy the Linuxant driver, which will taint your install as it's also binary
only), this appears to be yet another incarnation of a Conexant modem that
isn't detected in hsflinmodem. If you have the Broadcom Winmodem, as of now
it's totally useless in Linux.
Ethernet is a Broadcom Tigon3 derivative using the tg3 driver.
I found that Redhat's 2.4.20 seems
to barf on it after operating for a short while. The stock 2.6.9 works fine.
My machine has the Intel's Pro Wireless/2200 802.11b/g internal wireless card.
The CPU and this wireless card combo makes the machine 'Centrino' compliant.
The 0.12 version of the
ipw2200 drivers work fine.
Since people seem to be searching for data about it:
The Dell Wireless 1350 and 1450: They are Broadcom chipset wireless. There are NO native drivers as far as I know, but they can be used in Linux with the NdisWrapper, which uses the NDIS (Network Driver Interface Specification?) Windows driver in Linux. Linuxant and NdisWrapper Sourceforge has more data about it. Since I don't have one, and don't need it since I do have the Intel-backed (even if binary only due to FCC rules) Centrino... sorry folks. If you haven't bought one yet, I'd suggest get the Intel Centrino set with the Pro Wireless/2100(802.11b) or 2200(802.11b/g) so you get to use the Intel-written native driver, which I think is just as good as the Atheros compromise. There aren't many 802.11a networks around anyway.
The Alps touchpad pointer appears as a regular PS/2 device. It has two buttons
and not very
interesting. You'll need to Emulate3Buttons and imho the quality of the
trackpad and its buttons are horrible compared to my Gateway Solo 5350.
My Inspiron 600m has a 32MB ATI Radeon Mobility 9000 hooked up to a 14.1"
1400x1050 SXGA+ display, which is supported by
the opensource drivers in X.Org's X11 drivers. It worked pretty flawlessly
once the correct kernel was installed. Seems the older 2.4 kernels have
problems with the AGPGART on this machine, but I'm running 2.6-series (so that
the IPW2200 will work.) It's about 1/2 the speed of my Radeon AIW 8500DV,
a little faster than my GF4MX420, but clearly blows the i830m in my Gateway
Solo 5350 away.
The Inspiron 600m has ACPI hardware and this should be enabled in the kernel
config. It does support speedstep and will change CPU frequency on the fly.
Its lowest frequency is 600MHz.
Linux S4 sleep (Kernel Swsusp suspend-to-disk/hibernation) works fine. However, S3 sleep on this laptop has caveats - firmware has a bug that apparently does not correctly reinitializes video when resuming from S3 sleep. Running the A16 or A17 firmware, there is a workaround - if BIOS needs to ask for a password, it is compeled to initialize video, and then it can properly complete the resume cycle. Setting a BIOS password is sufficient to allow resume to complete.
Here's what I use in my /etc/portage/package.keywords