<link>http://people.skolelinux.org/pere/blog/</link>
<atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
+ <item>
+ <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
+ <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
+ <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
+ <description><p>Earlier, I reported about
+<a href="http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html">my
+problems using an Intel SSD 520 Series 180 GB disk</a>. Friday I was
+told by IBM that the original disk should be thrown away. And as
+there no longer was a problem if I bricked the firmware, I decided
+today to try to install Intel firmware to replace the Lenovo firmware
+currently on the disk.</p>
+
+<p>I searched the Intel site for firmware, and found
+<a href="https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=3472&DwnldID=18363&ProductFamily=Solid-State+Drives+and+Caching&ProductLine=Intel%c2%ae+High+Performance+Solid-State+Drive&ProductProduct=Intel%c2%ae+SSD+520+Series+(180GB%2c+2.5in+SATA+6Gb%2fs%2c+25nm%2c+MLC)&lang=eng">issdfut_2.0.4.iso</a>
+(aka Intel SATA Solid-State Drive Firmware Update Tool) which
+according to the site should contain the latest firmware for SSD
+disks. I inserted the broken disk in one of my spare laptops and
+booted the ISO from a USB stick. The disk was recognized, but the
+program claimed the newest firmware already were installed and refused
+to insert any Intel firmware. So no change, and the disk is still
+unable to handle write load. :( I guess the only way to get them
+working would be if Lenovo releases new firmware. No idea how likely
+that is. Anyway, just blogging about this test for completeness. I
+got a working Samsung disk, and see no point in spending more time on
+the broken disks.</p>
+</description>
+ </item>
+
<item>
<title>90 percent done with the Norwegian draft translation of Free Culture</title>
<link>http://people.skolelinux.org/pere/blog/90_percent_done_with_the_Norwegian_draft_translation_of_Free_Culture.html</link>
</description>
</item>
- <item>
- <title>The value of a good distro wide test suite...</title>
- <link>http://people.skolelinux.org/pere/blog/The_value_of_a_good_distro_wide_test_suite___.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_value_of_a_good_distro_wide_test_suite___.html</guid>
- <pubDate>Sat, 22 Jun 2013 07:00:00 +0200</pubDate>
- <description><p>In the <a href="http://www.skolelinux.org/">Debian Edu /
-Skolelinux</a> project, we include a post-installation test suite,
-which check that services are running, working, and return the
-expected results. It runs automatically just after the first boot on
-test installations (using test ISOs), but not on production
-installations (using non-test ISOs). It test that the LDAP service is
-operating, Kerberos is responding, DNS is replying, file systems are
-online resizable, etc, etc. And it check that the PXE service is
-configured, which is the topic of this post.</p>
-
-<p>The last week I've fixed the DVD and USB stick ISOs for our Debian
-Edu Wheezy release. These ISOs are supposed to be able to install a
-complete system without any Internet connection, but for that to
-happen all the needed packages need to be on them. Thanks to our test
-suite, I discovered that we had forgotten to adjust our PXE setup to
-cope with the new names and paths used by the netboot d-i packages.
-When Internet connectivity was available, the installer fall back to
-using wget to fetch d-i boot images, but when offline it require
-working packages to get it working. And the packages changed name
-from debian-installer-6.0-netboot-$arch to
-debian-installer-7.0-netboot-$arch, we no longer pulled in the
-packages during installation. Without our test suite, I suspect we
-would never have discovered this before release. Now it is fixed
-right after we got the ISOs operational.</p>
-
-<p>Another by-product of the test suite is that we can ask system
-administrators with problems getting Debian Edu to work, to run the
-test suite using <tt>/usr/sbin/debian-edu-test-install</tt> and see if
-any errors are detected. This usually pinpoint the subsystem causing
-the problem.</p>
-
-<p>If you want to help us help kids learn how to share and create,
-please join us on
-<a href="irc://irc.debian.org/%23debian-edu">#debian-edu on
-irc.debian.org</a> and the
-<a href="http://lists.debian.org/debian-edu/">debian-edu@</a> mailing
-list.</p>
-</description>
- </item>
-
</channel>
</rss>
projects / homepage.git / blobdiff