my requirements were "simple", though perhaps "simple" in the way that the plans in mission impossible episodes were "simple": under 5 pounds, perfect linux support, look good, decent screen (esp when viewing from an angle), be suitable for development and not cost more than CA$1000. and just like in mission impossible, it all turned out well in the end. i ended up springing for a toshiba m50-mx5 which comes with a pentium m 750, 512mb ram, 100gb sata drive, built in wireless, 14" widescreen, dvd burner, etc...

i was fairly confident things would go decently smooth since the graphics, wifi and .. well .. every other chipset that mattered to me was an intel product. when it comes to laptops, intel and linux tend to go well together in my experience. but i wasn't prepared for how well it did go.
i picked up the machine tuesday afternoon, shoved a kubuntu 5.10 cd in and a half an or so later ... had a working system. i did zero configuration and everything worked: the screen had the right (widescreen) resolution, networking worked, speedstep, hibernation/suspend (the power button does a cool orange pulsing thing when hibernating), the all-important coming out of hibernation (which is usually the part that doesn't work so well under linux ime), sound ...
well, almost everything. the sd card reader doesn't seem to work (some error about "generic_make_request: trying to access nonexistent block-device mmcblk0"). and i seem to be having some intermittent problem with the Marvel 88E8036 ethernet chipset and the sky2 driver; a rmmod followed by a modprobe "fixse" it, but it's certainly a bug in the sky2 driver with 2.6.15.
ironically, the wifi support has so far been more stable than the traditional, wired ethernet. though at first i didn't think the wifi worked at all as iwconfig could see the wifi card and i could configure it but it wouldn't pick up any access points. then i discovered a little switch on the front of the machine that when turned to 'on' actually turns on the wifi card. i noticed this while looking at the pretty blue lights and noticing a little panel beneath that with a wifi icon. turning the switch to "on" allowed me scan for and join wireless networks. it's a nice little feature to have when running on battery and not on a wireless network.
well, since everything went too easy, i upgraded immediately to the dapper beta2. still nothing broke (though the sd card and ethernet problems remained) and now i have a nice kde 3.5.2 system humming away. all i can say is "wow".
it also starts up, reboots and shuts down faster than the devil himself. so kudos to the kubuntu/ubuntu team for putting together such a great operating system, and to toshiba for a decent laptop at a reasonable price. though i suppose the real test will be 6 months from now and seeing how it stands up to the aseigo treatment =)
hopefully by tomorrow i'll have my kde4 dev env up and running .. *fingers crossed*
i also got the laundry situation sorted out. the neighbour came looking for his
laundry asking if i'd seen it. instead of answering his question immediately i informed him that we have a problem. he proceeded to freak out as i stood there calmly waiting for him to finish (took him a couple minutes to get it all out) and then explained to him the problems i had with how he was behaving. he calmed down pretty much instantly, apologized and then we talked for another 10 minutes or so finally arriving at a schedule that works for both of us (he gets night time, i get day time). i then told him where his laundry was and went to fetch it for him. i begin to understand why rich people end up building huge walls around their houses.

9 comments:
Remember Aaron: 50% of world's population are below average.
For extra bonus points, try setting up VGA-out (clone mode) using the Kubuntu control center replacement thingy (system-settings).
/me crosses fingers.
--
Simon Edwards
> try setting up VGA-out (clone
> mode) using the Kubuntu control
> center replacement thingy
didn't have to. Fn+F5 to switch between lcd, lcd+vga-out and vga-out only as well krandrtray for switching resolutions on the fly both worked flawlessly out of the box. =)
Does Toshiba in general use very Linux friendly HW or did you look up each Chipset?
Btw. I can't find a M50-MX model. Can you Point to a URL? I'm in search for a laptop, too!
> Does Toshiba in general use very
> Linux friendly HW or did you look
> up each Chipset?
i looked at the chipsets. toshiba tends to use linux-friendly hardware in their laptops (i've had a couple of them now) but you do have to be careful. some of their laptops comes with ATi chipsets and they aren't exactly fun to deal with. ditto for various wifi chipsets you may end up getting.
I'm surprised that you got so far that the card reader gave you an mmcblk0p1 device but that it still doesn't work.
What's the chipset for the SD card reader? Does it support SDHCI? In other words, does "lspci -n |grep 0805" print anything?
@johan:
aseigo@freedom:~$ lspci -n |grep 0805
0000:06:04.4 0805: 104c:8034
so, there it is =) and it doesn't quite get to mmcblk0p1. it gets as far as mmcblk0, complains, and then never create the partition device. i'm chalking it up to being a beta of the OS (hopefully). i didn't think to check it under breezy because i actually assumed it wouldn't work at all.
heh. too many years using linux has led me to discount such things from being easy ... what a brave new world we live in.
Alright. If you just do a plain lspci, do you have a line that says something like
0000:02:04.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller
If so, you need to enable the SDHCI interface. The TI controllers are a bit quirky. I use "setpci -s 02:04.3 4c=22" where the first numerical argument is taken from lspci above.
If you don't have a TI controller, I have no idea what's wrong.
btw, aaron, my girlfriend and me especially like your 'laundry stories' - we can relate :D
Post a Comment