<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>

<channel>
	<title>Graceful Exits &#187; hardware</title>
	<atom:link href="http://www.jpstacey.info/blog/category/hardware/www.jpstacey.info/blog/category/hardware/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jpstacey.info/blog</link>
	<description>Garbage collection, in a very real sense</description>
	<pubDate>Tue, 30 Sep 2008 20:10:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
	<language>en</language>
			<item>
		<title>Hardy Heron and the Dell Precision M4300</title>
		<link>http://www.jpstacey.info/blog/2008/07/16/hardy-heron-and-the-dell-precision-m4300/</link>
		<comments>http://www.jpstacey.info/blog/2008/07/16/hardy-heron-and-the-dell-precision-m4300/#comments</comments>
		<pubDate>Wed, 16 Jul 2008 19:16:10 +0000</pubDate>
		<dc:creator>jps</dc:creator>
		
		<category><![CDATA[hardware]]></category>

		<category><![CDATA[projects]]></category>

		<category><![CDATA[quickies]]></category>

		<category><![CDATA[software]]></category>

		<category><![CDATA[alsa]]></category>

		<category><![CDATA[dell]]></category>

		<category><![CDATA[display]]></category>

		<category><![CDATA[hardy]]></category>

		<category><![CDATA[heron]]></category>

		<category><![CDATA[install]]></category>

		<category><![CDATA[laptop]]></category>

		<category><![CDATA[linux]]></category>

		<category><![CDATA[m4300]]></category>

		<category><![CDATA[nvidia]]></category>

		<category><![CDATA[precision]]></category>

		<category><![CDATA[sound]]></category>

		<category><![CDATA[ubuntu]]></category>

		<category><![CDATA[upgrade]]></category>

		<guid isPermaLink="false">http://www.jpstacey.info/blog/?p=184</guid>
		<description><![CDATA[Summary: it just works.]]></description>
			<content:encoded><![CDATA[<p>In brief: the problems discussed <a href="http://www.jpstacey.info/blog/2008/01/07/the-full-sensory-experience-of-linux-on-a-dell-m4300-sound-vision-and-tinfoil-hat-microwaves/" >here</a> and <a href="http://www.jpstacey.info/blog/2007/08/28/laptop-and-linux-the-fixes-for-a-dell-precision-m4300/" >here</a> go away under the most recent <a href="http://www.ubuntu.com/" >Ubuntu</a> release, Hardy Heron, which I can generally recommend.</p>
<p>Alsa seems stable and graphics support is present from installation onwards. Enabling fancier 3D compiz effects requires the nvidia-glx-new package; compiz spots this, however and prompts for installation. All very smooth. Wireless works; my VoIP headset works; but I haven&#8217;t yet tested Bluetooth.</p>
<p>The only problem was in upgrading from Gutsy: my previous peregrinations had rendered my hybrid distribution shafted and incapable of upgrade. This isn&#8217;t a problem, though, if one has installed the /home directory (and in my case the /music one too) on a separate partition: the Ubuntu Live CD will blat the root partition with Heron, but leave the other partitions alone if you so require. Don&#8217;t resize any of your partitions during installation, though, or you&#8217;ll lose everything. Everything!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jpstacey.info/blog/2008/07/16/hardy-heron-and-the-dell-precision-m4300/feed/</wfw:commentRss>
		</item>
		<item>
		<title>The full sensory experience of Linux on a Dell M4300: sound, vision and tinfoil-hat microwaves</title>
		<link>http://www.jpstacey.info/blog/2008/01/07/the-full-sensory-experience-of-linux-on-a-dell-m4300-sound-vision-and-tinfoil-hat-microwaves/</link>
		<comments>http://www.jpstacey.info/blog/2008/01/07/the-full-sensory-experience-of-linux-on-a-dell-m4300-sound-vision-and-tinfoil-hat-microwaves/#comments</comments>
		<pubDate>Mon, 07 Jan 2008 21:14:44 +0000</pubDate>
		<dc:creator>jps</dc:creator>
		
		<category><![CDATA[hardware]]></category>

		<category><![CDATA[projects]]></category>

		<category><![CDATA[software]]></category>

		<category><![CDATA[dell]]></category>

		<category><![CDATA[display]]></category>

		<category><![CDATA[feisty]]></category>

		<category><![CDATA[gutsy]]></category>

		<category><![CDATA[install]]></category>

		<category><![CDATA[laptop]]></category>

		<category><![CDATA[linux]]></category>

		<category><![CDATA[m4300]]></category>

		<category><![CDATA[nvidia]]></category>

		<category><![CDATA[precision]]></category>

		<category><![CDATA[ubuntu]]></category>

		<category><![CDATA[wireless]]></category>

		<guid isPermaLink="false">http://www.jpstacey.info/blog/2008/01/07/the-full-sensory-experience-of-linux-on-a-dell-m4300-sound-vision-and-tinfoil-hat-microwaves/</guid>
		<description><![CDATA[Gutsy Gibbon on a Dell: almost everything has been fixed (edit: <a href="/blog/2008/07/16/hardy-heron-and-the-dell-precision-m4300/" >see Hardy Heron</a> for absolutely everything being fixed).]]></description>
			<content:encoded><![CDATA[<p>Now that Gutsy Gibbon is fairly mature, I&#8217;ve managed to upgrade my machine to it and am now running the 2.6.22-14-386 kernel. More importantly, with a minimum of fuss I now have <em>video</em>, <em>wireless</em> and <em>sound</em>!</p>
<p>Long-term readers of <cite>Graceful Exits</cite> might remember that the too-new hardware in my Dell Precision M4300 <a href="/blog/2007/08/28/laptop-and-linux-the-fixes-for-a-dell-precision-m4300/">needed some rather nasty hacks</a> just to get both display and wireless card working. One of those left me with a weird hybrid Gutsy/Feisty installation of Ubuntu, which worked for a while. I could get both video and wifi (by compiling both myself) as far as the 2.6.22-9 kernel, but no further. I needed to upgrade fully to Gutsy.</p>
<h3>From hybrid to Gutsy Ubuntu</h3>
<p>Upgrading from the hybrid version required me first to comment out the two Gutsy repositories I&#8217;d sneaked into my <code>/etc/apt/sources.list</code>. Then <code>gksudo update-manager -c</code> presented me with the necessary upgrade button. An hour or so later all the packages had been downloaded, but it took <em>a whole</em> day to have to keep going back and clicking on &#8220;OK to replace this configuration file&#8221; popups in between sleeping, showering and going to work. There must be a better way for Ubuntu to do that during mass package installations such as an upgrade.</p>
<h3>What worked and what didn&#8217;t</h3>
<p>When it comes to display drivers, Gutsy is very forgiving. My nVidia drivers didn&#8217;t work straight away, but the machine realised this and presented me with a low-res VESA mode, which in turn led to a low-graphics mode that was still more than adequate for the mean time. When Gnome finally finished starting, I noticed with joy that <b>wireless works in Gutsy out of the box</b>. I didn&#8217;t need to download the <code>iwlwifi</code> package and compile it. Lovely.</p>
<h3>If I were going to nVidia, I wouldn&#8217;t start from here</h3>
<p><a href="http://albertomilone.com/nvidia_scripts1.html">Envy</a> is an easy way to install the right nVidia drivers for your machine. <em>However</em>, if you&#8217;ve already tried to install the drivers using nVidia&#8217;s own packages (as I had, back when I had a hybrid system), you need to find and delete these files. <code>modprobe -l nvidia</code> will tell you where they are: run <code>envy -t</code> and uninstall everything, then delete whatever&#8217;s remaining in, oh, something like <code>/lib/modules/2.6.22-14-386/kernel/drivers/video/nvidia.ko</code>. Then reinstall the drivers with Envy. That should be enough.</p>
<h3>Alsa is a known problem, to put it mildly</h3>
<p>A comment on <a href="https://bugs.launchpad.net/ubuntu/+bug/131133/comments/42">Ubuntu bug 131133</a> describes the Alsa codebase as &#8220;mercurial&#8221;. Apparently the snd_hda_intel support is fixed and broken on alternate releases, and Ubuntu High Command are doing all they can. In the interim there&#8217;s a <a href="https://wiki.ubuntu.com/Gutsy_Intel_HD_Audio_Controller">workaround</a>: method A worked just fine for me.</p>
<p>I&#8217;m terribly, terribly happy. K&#8217;s even happier, as now she&#8217;ll be able to prise me away from frequent driver recompilation messes.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jpstacey.info/blog/2008/01/07/the-full-sensory-experience-of-linux-on-a-dell-m4300-sound-vision-and-tinfoil-hat-microwaves/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Distributed FM radio from a single digital signal</title>
		<link>http://www.jpstacey.info/blog/2007/11/25/distributed-fm-radio-from-a-single-digital-signal/</link>
		<comments>http://www.jpstacey.info/blog/2007/11/25/distributed-fm-radio-from-a-single-digital-signal/#comments</comments>
		<pubDate>Sun, 25 Nov 2007 14:57:48 +0000</pubDate>
		<dc:creator>jps</dc:creator>
		
		<category><![CDATA[configuration]]></category>

		<category><![CDATA[formats]]></category>

		<category><![CDATA[futurology]]></category>

		<category><![CDATA[hardware]]></category>

		<category><![CDATA[am]]></category>

		<category><![CDATA[analogue]]></category>

		<category><![CDATA[convert]]></category>

		<category><![CDATA[converter]]></category>

		<category><![CDATA[digital]]></category>

		<category><![CDATA[fm]]></category>

		<category><![CDATA[fon]]></category>

		<category><![CDATA[radio]]></category>

		<category><![CDATA[relay]]></category>

		<category><![CDATA[transmitter]]></category>

		<guid isPermaLink="false">http://www.jpstacey.info/blog/2007/11/25/distributed-fm-radio-from-a-single-digital-signal/</guid>
		<description><![CDATA[There&#8217;s currently no plan to switch off FM stations. In fact, many radio bosses have said oh, for heaven&#8217;s sake to the very idea. There is, astonishingly, less of a plan for radio switchover than there is desire among the general public for TV switchover. So that must be some sort of record for nothingness.
Seriously: [...]]]></description>
			<content:encoded><![CDATA[<p>There&#8217;s currently <a href="http://www.frequencycast.co.uk/godigital.html">no plan to switch off FM stations</a>. In fact, many radio bosses have said <a href="http://www.guardian.co.uk/media/2004/jul/08/radio">oh, for heaven&#8217;s sake</a> to the very idea. There is, astonishingly, less of a plan for radio switchover than there is desire among the general public for TV switchover. So that must be some sort of record for nothingness.</p>
<p>Seriously: who among us is just itchy and fidgety, waiting for analogue TV signals to be switched off? Who wakes up of a morning thinking, ooh, Whitehaven have to buy Freeview boxes now! with a frisson of glee? Radio switchover would be even more disastrous, of course: whereas TVs normally have a gap between themselves and an aerial into which to insert a Freeview box and convert digital to analogue, most radios are monolithic: receiver, &#8220;decoder&#8221; and audio equipment all together. That means that the average of five radios per household would be simply landfill material, useless fizzing boxes capable of picking up nothing but static. Future generations will already find a sliver in the geological strata that they can classify as &#8220;analogue to digital&#8221;; FM switchoff would add a shiny, plasticky laminate to that layer.</p>
<p>Here&#8217;s a thought, though: how about a little digital-to-analogue converter for radio? It could be the size and construction of, say, a <a href="http://www.fon.com/">Fon</a>, and configurable over USB. It would transmit FM in the style of an <a href="http://en.wikipedia.org/wiki/ITrip">iTrip</a> to fill perhaps the room it&#8217;s kept in, plus neighbouring rooms. It could transmit multiple FM stations at the same time, and even mimic the frequencies of the analogue stations (if they were ever, say, switched off without anyone wanting them to be: God forbid!)</p>
<p>But what if your converter&#8217;s chosen frequencies conflict with next door? FM transmission depends on phase coherence, so even if your two boxes were within an electronic ace of each other frequency-wise, they&#8217;d still interfere with each other and cause all sorts of beating, flangeing and other dirtily-named auditory confusion. At least when someone passes you on the motorway and their phat BMW iPod transmitter briefly swamps yours then they&#8217;re gone quickly, hopefully to come to some sort of messy grief on the next bend. But if you&#8217;re stuck near someone who permanently foxes your radio listening&#8212;and it would only take maybe three or four such converters for a conflict to be inevitable in the narrow FM band&#8212;then what do you do?</p>
<p>Answer: <em>let the converter boxes know how to talk to each other</em>. Let them negotiate their frequency spreads. Let them, moreover, report back to you over what sort of understandings you and your neighbour&#8217;s radios can come to. Let them synchronize, if possible, on stations you both want to listen to, strengthening the signal and meaning both of your houses are entirely covered by the FM cloud. Exploit, don&#8217;t squash, the wisdom of the group.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jpstacey.info/blog/2007/11/25/distributed-fm-radio-from-a-single-digital-signal/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Barcamp left me with a sticky keyboard</title>
		<link>http://www.jpstacey.info/blog/2007/09/15/barcamp-left-me-with-a-sticky-keyboard/</link>
		<comments>http://www.jpstacey.info/blog/2007/09/15/barcamp-left-me-with-a-sticky-keyboard/#comments</comments>
		<pubDate>Sat, 15 Sep 2007 12:45:04 +0000</pubDate>
		<dc:creator>jps</dc:creator>
		
		<category><![CDATA[hacking]]></category>

		<category><![CDATA[hardware]]></category>

		<category><![CDATA[bud]]></category>

		<category><![CDATA[clean]]></category>

		<category><![CDATA[coke]]></category>

		<category><![CDATA[cotton]]></category>

		<category><![CDATA[drink]]></category>

		<category><![CDATA[internals]]></category>

		<category><![CDATA[key]]></category>

		<category><![CDATA[keyboard]]></category>

		<category><![CDATA[nipple]]></category>

		<category><![CDATA[sticky]]></category>

		<category><![CDATA[wd40]]></category>

		<guid isPermaLink="false">http://www.jpstacey.info/blog/2007/09/15/barcamp-left-me-with-a-sticky-keyboard/</guid>
		<description><![CDATA[The inevitable keyboard accident happened at Barcamp, although not as badly as I think Tristan Roddis suffered. A few teaspoons of a particularly sugary branded drink ended up under my arrow keys, which meant that pressing up became an unpleasant feedback experience. I should&#8217;ve asked people for advice at the time, to be honest: I [...]]]></description>
			<content:encoded><![CDATA[<p>The inevitable keyboard accident happened at Barcamp, although not as badly as I think <a href="http://blog.cogapp.com/">Tristan Roddis</a> suffered. A few teaspoons of a particularly sugary branded drink ended up under my arrow keys, which meant that pressing up became an unpleasant feedback experience. I should&#8217;ve asked people for advice at the time, to be honest: I had to hand a gathering of like-minded, caffeine-addicted typing machines, some or most of whom had probably done the same thing in the past. But it only became an obvious issue after a few days, and so I had to work out myself how to clean the keys.</p>
<p>There&#8217;s lots of help out there, but most advice begins with unscrewing the laptop case, something I was unwilling to do owing to its youth. With hindsight I&#8217;ve been able to Google <a href="http://www.acmeiowa.com/Tips/Action.lasso?-Database=TipsTech&#38;-Layout=Web&#38;-Response=TipArtical.lasso&#38;nID=6&#38;-Search">a similar suggestion</a> to the method I followed, but at the time I wass just making small, non-destructive steps towards getting rid of the stickiness.</p>
<p>I started by, of course, switching off the laptop and removing the battery. The latter bit may or may not be important, but I was taking no chances. On this keyboard (<em>yours may vary!</em>) I found I could prise the keys off if I pull them either on their top or bottom edge: they have four plastic connections to the base, and removing them this way unclicks two connections at once. Pulling them up from the left or right would put stress on the connections opposite instead, and I&#8217;ve had key mountings break before doing that, so be warned. With the plastic head of the key removed, the board reveals the rubbery underlay nipples (say that out loud, I dare you) that each key squashes when it&#8217;s pressed down. </p>
<p>With my up-key nipple thus revealed (!) I found some cotton buds and a can of WD40. I sprayed the WD40 at the bud&#8212;<em>not at the keyboard</em>, as it can go everywhere&#8212;and then rubbed the sticky fizzy drink off the exposed internals with the bud. Two buds to clean and one to dry up the WD40, although WD40 shouldn&#8217;t do too much harm in small amounts: I think keyboards ship with a gentle frosting of some specially mixed lubricant anyway, so the WD40 was only replacing that. But still I dried off the nipple, replaced the key gently&#8212;again watching out for the four delicate plastic connections under the key&#8212;and superstitiously left it all to dry for a minute or two before reconnecting the battery and starting it up.</p>
<p>Now the key works just great. And in one fell swoop I&#8217;ve written a post that&#8217;s almost guaranteed to get hordes of entirely the wrong sort of visitors to my blog.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jpstacey.info/blog/2007/09/15/barcamp-left-me-with-a-sticky-keyboard/feed/</wfw:commentRss>
		</item>
		<item>
		<title>DO NOT BEEP!</title>
		<link>http://www.jpstacey.info/blog/2007/08/29/do-not-beep/</link>
		<comments>http://www.jpstacey.info/blog/2007/08/29/do-not-beep/#comments</comments>
		<pubDate>Wed, 29 Aug 2007 16:42:50 +0000</pubDate>
		<dc:creator>jps</dc:creator>
		
		<category><![CDATA[hardware]]></category>

		<category><![CDATA[useability]]></category>

		<category><![CDATA[beep]]></category>

		<category><![CDATA[dell]]></category>

		<category><![CDATA[loud]]></category>

		<category><![CDATA[sound]]></category>

		<category><![CDATA[volume]]></category>

		<category><![CDATA[xp]]></category>

		<guid isPermaLink="false">http://www.jpstacey.info/blog/2007/08/29/do-not-beep/</guid>
		<description><![CDATA[On both my work and home Dell laptops, the computer beeps at full volume when you change the sound settings. This has come close to shattering my eardrums on several occasions these past few days.
Bizarrely, if you open &#8220;Control Panel &#62; System &#62; Hardware &#62; Device Manager&#8221;, and click on &#8220;View &#62; Show hidden devices,&#8221; [...]]]></description>
			<content:encoded><![CDATA[<p>On both my work and home Dell laptops, the computer beeps at full volume when you change the sound settings. This has come close to shattering my eardrums on several occasions these past few days.</p>
<p>Bizarrely, if you open &#8220;Control Panel &gt; System &gt; Hardware &gt; Device Manager&#8221;, and click on &#8220;View &gt; Show hidden devices,&#8221; then there&#8217;s a Non-Plug and Play Driver for a service called &#8220;Beep&#8221;. And, unlike most XP services, this one does exactly what it says. It beeps. And beeps. Whenever a system beep is needed, Beep is there, with its full-volume flava and rich, screeching aroma! Disable it and reboot, or <a href="http://blog.netnerds.net/2007/05/5-ways-to-stop-windows-vista-xp-2003-from-beeping/" title="5 ways to stop Windows Vista/XP/2003 from beeping">do something more clever</a> if you need to.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jpstacey.info/blog/2007/08/29/do-not-beep/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Laptop and Linux: the fixes for a Dell Precision M4300</title>
		<link>http://www.jpstacey.info/blog/2007/08/28/laptop-and-linux-the-fixes-for-a-dell-precision-m4300/</link>
		<comments>http://www.jpstacey.info/blog/2007/08/28/laptop-and-linux-the-fixes-for-a-dell-precision-m4300/#comments</comments>
		<pubDate>Tue, 28 Aug 2007 18:04:52 +0000</pubDate>
		<dc:creator>jps</dc:creator>
		
		<category><![CDATA[hardware]]></category>

		<category><![CDATA[projects]]></category>

		<category><![CDATA[software]]></category>

		<category><![CDATA[1394]]></category>

		<category><![CDATA[4695]]></category>

		<category><![CDATA[bluetooth]]></category>

		<category><![CDATA[dell]]></category>

		<category><![CDATA[display]]></category>

		<category><![CDATA[firewire]]></category>

		<category><![CDATA[install]]></category>

		<category><![CDATA[laptop]]></category>

		<category><![CDATA[linux]]></category>

		<category><![CDATA[m4300]]></category>

		<category><![CDATA[nvidia]]></category>

		<category><![CDATA[precision]]></category>

		<category><![CDATA[ubuntu]]></category>

		<category><![CDATA[wireless]]></category>

		<guid isPermaLink="false">http://www.jpstacey.info/blog/2007/08/28/laptop-and-linux-the-fixes-for-a-dell-precision-m4300/</guid>
		<description><![CDATA[Getting a Dell Precision M4300 to work with a weird Feisty/Gutsy hybrid Ubuntu (<a href="/blog/2008/07/16/hardy-heron-and-the-dell-precision-m4300/" >edit: upgrading to Hardy Heron</a> eventually fixed everything).]]></description>
			<content:encoded><![CDATA[<p>The Ubuntu Live CD worked straight away for the laptop: I was able to boot into a temporary copy of Linux using the VESA display drivers, and test sound, CD and other peripherals (obviously) and wired networking. However, optimising the system wasn&#8217;t so easy, and <a href="/blog/2007/08/26/precision-decision/">as I say Nick practically installed Ubuntu for me</a>, fixing all that he could.</p>
<p>Below is a list of the main fixes and workarounds that Nick employed, for my reference as much as anything else.</p>
<h3>Kernel</h3>
<p>Gusty Gibbon kernel, headers etc. on a Feisty Fawn installation, mixed with <code>apt-pinning</code>; necessary to get the wireless to work.</p>
<h3>Wireless</h3>
<p>Bleeding-edge Intel wireless drivers were needed for the IPW 4965 chipset (they in turn need most recent kernel). Download the following:</p>
<ul>
<li>mac80211 8.x driver</li>
<li>ipw4965 latest driver source</li>
<li>ipw4965 latest firmware</li>
</ul>
<p>The 4695 is a firmware-less card, so you need a copy of the firmware in <code>/lib/firmware/</code>: it gets automagically flashed to the card on boot.</p>
<p>Then, the nastier bit, </p>
<ul>
<li>install Gutsy kernel headers</li>
<li>patch kernel headers for mac80211</li>
<li>build ipw4965 module</li>
</ul>
<p>Three lines, detailing so much pain. At least the kernel itself didn&#8217;t need recompiling.</p>
<h3>Sound</h3>
<p>Although ALSA is configured correctly, there&#8217;s <a href="https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/122560">some bug in the handling of this version of the 82801H chipset</a>. I&#8217;m looking into it: there&#8217;s nothing more embarrassing than <a href="http://blogs.zdnet.com/hardware/?p=7242">making your users choose between good networking and audio playback&#8230;!</a></p>
<h3>Display</h3>
<p>The most recent version of the <a href="https://launchpad.net/ubuntu/gutsy/+source/linux-restricted-modules-2.6.22/+changelog">linux-restricted-modules</a> for Gutsy now makes this fix redundant, but initially we needed a bleeding-edge  <a href="http://tuxenclave.wordpress.com/2007/07/14/nvidia-1001409-driver-stable/">100.14.09 version of the NVidia drivers</a> to get the display working properly.</p>
<p>The hack to install that was originally accomplished by <a href="http://www.nvidia.com/object/linux_display_ia32_100.14.09.html">downloading a non-standard installer</a> and crossing one&#8217;s fingers; it worked pretty well but the restricted modules kept trying to do their bit and had to be removed. If you&#8217;re sure you have a compatible, hacked-in NVidia module on your system but the restricted version keeps butting in, then <code>sudo modprobe -r nvidia</code> and then restarting X works: Xorg looks in the right place, whereas the kernel gets it wrong.</p>
<blockquote><p><strong>Edit (2.6.22-10):</strong> doesn&#8217;t seem to support 100.14.09, so back to the NVidia downloads again.</p>
</blockquote>
<h3>CDROM</h3>
<p>There seems to be a recurring bug with the Linux kernel and SATA CDROM drives, frequently whacked but never fully squashed, that the Gutsy kernel has fallen prey to: my CD drive was not at <code>/dev/scd0</code> by default. Running <code>sudo lshw</code> produced no details under &#8220;*-cdrom&#8221; There are a lot of solutions out there, but <a href="http://ubuntuforums.org/archive/index.php/t-42726.html" title="">the one that seemed to work for me</a> was to load the <code>ide_cd</code> module using modprobe. </p>
<p>This does seem to have put my CDROM at <code>/dev/hda</code>, which took a bit of finding, but at least as soon as I ran modprobe Sound Juicer spotted the audio CD in the drive. I&#8217;ve not yet tested CD writing, nor DVD writing, so I don&#8217;t know yet whether or not I actually need <code>ide_scsi</code> instead; Nick assures me that as most devices support ATAPI these days then the SCSI support shouldn&#8217;t be necessary.</p>
<h3>Bluetooth</h3>
<p>The Precision seems to have an internal USB bluetooth dongle! <code>hcitool</code> finds it with no trouble. I&#8217;ve not used it yet and might need to add <code>hci_usb</code> to <code>/etc/modules</code>.</p>
<h3>Firewire/1394</h3>
<p>As I don&#8217;t have any Firewire devices, I still have to have a poke around for this; might need the firewire host controller driver, or sbp2 (SCSI over firewire). Watch this space.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jpstacey.info/blog/2007/08/28/laptop-and-linux-the-fixes-for-a-dell-precision-m4300/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Precision decision</title>
		<link>http://www.jpstacey.info/blog/2007/08/26/precision-decision/</link>
		<comments>http://www.jpstacey.info/blog/2007/08/26/precision-decision/#comments</comments>
		<pubDate>Sun, 26 Aug 2007 19:35:00 +0000</pubDate>
		<dc:creator>jps</dc:creator>
		
		<category><![CDATA[culture]]></category>

		<category><![CDATA[hardware]]></category>

		<guid isPermaLink="false">http://www.jpstacey.info/blog/2007/08/26/precision-decision/</guid>
		<description><![CDATA[I have a new laptop: a Dell Precision M4300. Thanks to everyone who gave feedback to my request for recommendations about laptops. I really did take your suggestions to heart: but when I realised that (a) I&#8217;d run any laptop I bought into the ground, and so didn&#8217;t need to go refurbished to obtain maximum [...]]]></description>
			<content:encoded><![CDATA[<p>I have a new laptop: a Dell Precision M4300. Thanks to <a href="/blog/2007/07/24/laptop-nearly-dead-stop-please-send-help-stop-or-soldering-iron-will-do-stop/" >everyone who gave feedback to my request</a> for recommendations about laptops. I really did take your suggestions to heart: but when I realised that (a) I&#8217;d run any laptop I bought into the ground, and so didn&#8217;t need to go refurbished to obtain maximum greenness and (b) I was going to get a one-off deal if I bought a Dell, then&#8212;I bought a Dell.</p>
<p>Because it&#8217;s a fairly new model (newer than I actually realised), Ubuntu is stretched rather thin on it, but it works really remarkably well without seriously irreversible hacks. Thanks to my co-worker and systems genius <a href="http://gagravarr.livejournal.com/" >Nick</a> I now have a kind of bleeding-edge combination of Feisty Fawn and Gutsy Gibbon running. This was necessary in order to use the similarly paint-still-wet <a href="http://tuxenclave.wordpress.com/tag/nvidia/">v100.14.09 NVidia drivers</a> to get the full 1680-pixel, widescreen resolution and TrueLife sweetness from the screen. </p>
<p>The experimental Ubuntu display tweaks also work pretty well, which makes the whole thing feel very Vista/OSX. When the switch between two of my four workspaces looked like the rotating of a cube across the screen for the first time, I almost wept. Linux oughtn&#8217;t to look this good. It was the same realisation that I had when I first opened a terminal in OSX, but in reverse: you <em>can</em> build good-looking, responsive interfaces on top of solid, well-built cores; patience can, in the end, produce far better results than compromise.</p>
<p>You can mix and match your own Ubuntu distributions far more easily than you&#8217;d imagine. <code>apt</code> is really a clever piece of software, and you can configure it via &#8220;pinning&#8221; to obey certain preference &#8220;policies&#8221;&#8212;these are configured in the file <code>/etc/apt/preferences</code>. Here&#8217;s my copy of that file:</p>
<blockquote class="code"><p>
# If no priority given for a package, it&#8217;s set to 500.<br />
# So setting a lower priority than 500 deprecates a repository type<br />
# Setting a higher priority preferences that repository type</p>
<p># All packages - gutsy has low priority<br />
Package: *<br />
Pin: release a=gutsy<br />
Pin-Priority: 200</p>
<p># libc6 and libc6-dev - gutsy has higher priority than any other repository type<br />
Package: libc6<br />
Pin: release a=gutsy<br />
Pin-Priority: 600<br />
Package: libc6-dev<br />
Pin: release a=gutsy<br />
Pin-Priority: 600</p>
<p># Kernel images begin linux-, so gutsy gets higher priority for those<br />
Package: linux-*<br />
Pin: release a=gutsy<br />
Pin-Priority: 600
</p></blockquote>
<p>If you run <code>apt-cache policy X</code> then <code>apt</code> will tell you exactly what policy it will follow when prioritizing all possible candidates for package X.</p>
<p>Beautiful, really. Not perfect&#8212;I&#8217;ll put up a list of Nick&#8217;s necessary fixes shortly&#8212;but as far as coping with really quite new hardware goes, this was a triumph for open source. I just wish I&#8217;d waited till after Dell&#8217;s announcement to run Ubuntu-enabled laptops in Europe&#8230;.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jpstacey.info/blog/2007/08/26/precision-decision/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Laptop nearly dead stop please send help stop or soldering iron will do stop</title>
		<link>http://www.jpstacey.info/blog/2007/07/24/laptop-nearly-dead-stop-please-send-help-stop-or-soldering-iron-will-do-stop/</link>
		<comments>http://www.jpstacey.info/blog/2007/07/24/laptop-nearly-dead-stop-please-send-help-stop-or-soldering-iron-will-do-stop/#comments</comments>
		<pubDate>Tue, 24 Jul 2007 09:57:12 +0000</pubDate>
		<dc:creator>jps</dc:creator>
		
		<category><![CDATA[hardware]]></category>

		<category><![CDATA[software]]></category>

		<guid isPermaLink="false">http://www.jpstacey.info/blog/2007/07/24/laptop-nearly-dead-stop-please-send-help-stop-or-soldering-iron-will-do-stop/</guid>
		<description><![CDATA[I&#8217;d like your thoughts on a replacement for my laptop. 
It&#8217;s been dying for a long time now. I originally bought it to write my thesis on back in 2002, spending most of an inheritance from my grandmother on the last of the 1.2GHz machines in the now defunct Dixons. A few months ago the [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;d like your thoughts on a replacement for my laptop. </p>
<p>It&#8217;s been dying for a long time now. I originally bought it to write my thesis on back in 2002, spending most of an inheritance from my grandmother on the last of the 1.2GHz machines in the now defunct Dixons. A few months ago the keyboard developed the <a href="http://motls.blogspot.com/2007/02/fixing-keyboard-of-hewlett-packard.html" >canonical HP Pavilion G-H-F4 problem</a>, which I was able to correct by occasionally unscrewing the case and fiddling with cables. But now, every time I open it, the display shows a mess of unsync&#8217;ed blue lines and rubbish, hinting at the screen it ought to show, unless I have the laptop almost closed. Fiddling with cables doesn&#8217;t help, although as all the connectors warm up then I&#8217;m permitted to open the shell further and further.</p>
<p>Anyway, I&#8217;ve been watching <a href="http://www.dell.com/open" >Dell&#8217;s abortive open-source offerings</a> (<a href="http://lxer.com/module/newswire/view/87499/index.html" >why <em>would</em> you scupper your own product ranges?</a>) eagerly for a while now, waiting for a time when searching dell.co.<em>uk</em> doesn&#8217;t redirect me back to the .com site with American prices. I&#8217;ve also been sniffing round the now apparently defunct <a href="http://www.ubuntuboxes.co.uk/" >Ubuntu Boxes</a>, which <a href="http://seanmcgrath.blogspot.com/" >Sean McGrath</a> spotted in his capacity as another avid OS-ready fan. But as nothing seems to be materialising any time soon to enable me to use the software and hardware combination I desire, it looks like I might have to roll my own.</p>
<p>What do people recommend in a laptop that will eventually have Linux on it? Is most hardware plug-and-go these days? What about X and a second monitor, which always seems to be problematic? Anything I should look out for? If all laptops are created evil, pardon, equal, then I may just <a href="http://www.greenpeace.org/international/campaigns/toxics/electronics/how-the-companies-line-up" >go for Lenovo or Dell on green issues alone</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jpstacey.info/blog/2007/07/24/laptop-nearly-dead-stop-please-send-help-stop-or-soldering-iron-will-do-stop/feed/</wfw:commentRss>
		</item>
		<item>
		<title>No, Mister Bond: I expect you to I!</title>
		<link>http://www.jpstacey.info/blog/2007/05/06/no-mister-bond-i-expect-you-to-i/</link>
		<comments>http://www.jpstacey.info/blog/2007/05/06/no-mister-bond-i-expect-you-to-i/#comments</comments>
		<pubDate>Sun, 06 May 2007 11:37:06 +0000</pubDate>
		<dc:creator>jps</dc:creator>
		
		<category><![CDATA[hardware]]></category>

		<guid isPermaLink="false">http://www.jpstacey.info/blog/2007/05/06/no-mister-bond-i-expect-you-to-i/</guid>
		<description><![CDATA[I&#8217;ve found myself learning a number of interesting facts about iPods this past day or two that perhaps I&#8217;d rather not have ever known:

An iPod can be connected safely, via the Y-shaped cable that comes with a dock, to two generic power supplies at once. For instance, the Firewire cable can be plugged into a [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve found myself learning a number of interesting facts about iPods this past day or two that perhaps I&#8217;d rather not have ever known:</p>
<ol>
<li>An iPod can be connected safely, via the Y-shaped cable that comes with a dock, to two generic power supplies at once. For instance, the Firewire cable can be plugged into a mains adapter, while the USB cable used to transfer files onto the iPod (and incidentally charge it).</li>
<li>However, this is no longer safe if one of the power supplies is reactive to what you connect to it e.g. a solar/mains-charged, third-party battery pack. In this case, if the pack spots an alternative power supply on the far side of the iPod, it will try to use it to recharge. This will be accomplished through the iPod, which will drain its battery so fast that the case becomes hot enough to fry an egg on.</li>
<li>When the computer at the other end of a USB connection is switched off, it no longer provides power to the iPod, so you only have to worry about currents running down the other connection.</li>
<li>However, this does not seem to be the case with the Firewire standard which, if the computer is connected to the mains, still seems to  provide a large thump of power to the device. Or this might actually be a fault, owing to the age of the computer the iPod was connected to.</li>
</ol>
<p>So, there you have it: if you use an iPod as a bridge between your solar charger of choice and the mains voltage, chances are it will nigh-on catch fire. It&#8217;s a rather long and drawn-out way of destroying the device, but it has a certain Goldfinger charm to its convolutions. Bring in an experimental death ray or a room that fills with poison gas in twenty seconds and you&#8217;re all set to be the next Bond villain.</p>
<p>In a sense I was lucky that my iPod was already showing the <a href="/blog/2006/10/08/percussive-maintenance-with-a-twist/" >archetypal signs of pod wear</a>, as it&#8217;s now turned into an unresponsive metal brick: this finally gives me the impetus to free myself from the tyranny of making-do. Anyway, I&#8217;m now looking for a new portable music player (money willing) if I can find a suitable device. It really has to be:</p>
<ol>
<li>Longer-lasting than my iPod (hence Flash- rather than hard-driven?)&#8212;the greenness of the product is important for me, and I&#8217;d rather just not buy anything than buy a product with a two-year lifespan.</li>
<li>Compatible with Linux on some reasonable level. I hear that anything other than the iPod lets you drop files onto it as if it were a USB hard drive, but that might not be the case.</li>
<li>Probably not made by Apple. Between their <a href="http://www.greenpeace.org/apple/" >environmental policy</a>, their <a href="http://www.msnbc.msn.com/id/13357555/" >use of sweatshops</a>, and their <a href="http://thetyee.ca/Books/2006/08/01/MadeToBreak/" >disdain for their customers</a>, I&#8217;m heartily sick of Apple&#8217;s use of beautiful design to paper over their moral cracks. I hope to find a company that, while it might be just as badly behaved, doesn&#8217;t present its products as a choice of lifestyle or aesthetics.</li>
</ol>
<p>If anyone has any suggestions then do let me know.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jpstacey.info/blog/2007/05/06/no-mister-bond-i-expect-you-to-i/feed/</wfw:commentRss>
		</item>
		<item>
		<title>How to get Dell to provide more Linux-installed machines: people power!</title>
		<link>http://www.jpstacey.info/blog/2007/03/15/how-to-get-dell-to-provide-more-linux-installed-machines-people-power/</link>
		<comments>http://www.jpstacey.info/blog/2007/03/15/how-to-get-dell-to-provide-more-linux-installed-machines-people-power/#comments</comments>
		<pubDate>Thu, 15 Mar 2007 11:41:09 +0000</pubDate>
		<dc:creator>jps</dc:creator>
		
		<category><![CDATA[business]]></category>

		<category><![CDATA[hardware]]></category>

		<category><![CDATA[news]]></category>

		<category><![CDATA[software]]></category>

		<guid isPermaLink="false">http://www.jpstacey.info/blog/2007/03/15/how-to-get-dell-to-provide-more-linux-installed-machines-people-power/</guid>
		<description><![CDATA[I&#8217;m not one for passing on memes and crazy petitions, but Sean McGrath has pointed out that Dell are requesting advice on expanding their pre-installed Linux range.
I think they currently provide, oh, some old version of Ubuntu on two of their billion computer models only in the US, and then only in states whose names [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m not one for passing on memes and crazy petitions, but <a href="http://seanmcgrath.blogspot.com/2007_03_11_seanmcgrath_archive.html#7257906049584760712#7257906049584760712" >Sean McGrath</a> has pointed out that <a href="http://www.dell.com/content/topics/global.aspx/corp/linux" >Dell are requesting advice on expanding their pre-installed Linux range</a>.</p>
<p>I think they currently provide, oh, some old version of Ubuntu on two of their billion computer models only in the US, and then only in states whose names begin with &#8220;K&#8221;. This might be a way to lever open the barriers placed around this potentially very popular market. You&#8217;ll have to move fast, though, as the petition closes on Friday March 23.</p>
<p>Do this for your potential customers, Dell. You could be part of a new revolution: after all, <a href="http://radar.oreilly.com/archives/2007/03/web_20_goes_mai_1.html" >Tim O&#8217;Reilly says that Web 2.0 is all about putting the customer first</a>. I bet that came as a bit of a shock to all those people in other industries, like the old Web 1.9, or cheese-making, or DIY superstores, who think <em>their</em> sector is about putting the customer first and it&#8217;s nothing to actually crow about. But banal marketing statements from industry sacred cows aside, this is a great chance for Dell and for their customers.</p>
<p>If Dell can give me a computer which categorically does <em>not</em> contribute to the statistics of how many users there are of Vista or XP, and which has a reasonable Linux version on it from day one, then I for one pledge to go out and buy one off them. They&#8217;ll have to be quick, though. Without choice, I&#8217;ll eventually lose patience and go for a cheaper option: any one of their competitors will do. I&#8217;ll have to swallow my pride and just buy and then discard an XP licence for zero pounds, but I&#8217;ll be buying it from them, dearest Dell: not you. Time&#8217;s a tickin&#8217;.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jpstacey.info/blog/2007/03/15/how-to-get-dell-to-provide-more-linux-installed-machines-people-power/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
