Rolling Notes

This page is a summary of the Release Notes and will only be updated after each release. Read the full Release Notes on aptosid.com, the Live ISO or apt-get install aptosid-releasenotes.

Release notes for aptosid 2013-01 Ἑσπερίδες - Hesperides

New features in aptosid 2013-01 Ἑσπερίδες - Hesperides, are in particular kernel 3.9 and numerous integration and stabilisation fixes. Special focus has been cast upon improving system compatibility with various UEFI systems and the Ivy-Bridge architecture; basic Haswell support should now be complete. Kernel 3.9 doesn't only improve and stabilise hardware support for newer devices, it also improves powersaving approaches for libata targets, modern sound drivers and multi-head environments with AMD/ ATi radeon graphics cards

Intel Ivy-Bridge graphics profits from improved DisplayPort support, while nouveau has gained initial fan-control for NV40 and NV50 chipsets (GeForce 6xxx/ 7xxx/ 8xxx/ 9xxx/ 1xx/ 2xx/ 3xx). The radeon driver for AMD/ ATi graphics cards has gained support for the Oland (Radeon 8500/ 8600 series) chipset generation and Richland APUs.

On the file system side CIFS now support the SMB 2.0 and SMB 2.1 protocol, while the mdadm layer can now pass through TRIM support. A new development is the dm-cache target, which allows using SSD storage to speed up hard disk access.

Atheros AR5523 support has now been merged officially, while Broadcom has added initial support for BCM43224 to brcmsmac. A new driver has become available for the Realtek RTL8723AE wlan chipset and r92su replaces the staging rtl8712u driver for the Realtek RTL8188SU/ RTL8192SU chipsets. With iwlmvm, Intel provides the first IEEE 802.11ac driver for their IWL7xxx wlan chipsets, as Atheros and Wilocity contribute a 60 GHz (WiGig WBE) drivers for the QCA WIL6210 generation.

GPT and UEFI reliability have been improved, which allows hard disks exceeding 2 TiB and their use for booting on new systems using UEFI instead of the traditional PC-BIOS. Particular emphasis has been cast upon improving UEFI support on various hardware platforms and to avoid bugs in the varying firmware implementations, both upstream and in aptosid.

As usual, a large number of individual functionality enhancements and bug fixes have been applied to the full package line up and aptosid's own packages, in order to improve the general distribution infrastructure.

Although this release happens in close temporal proximity to the Debian 7.0 "wheezy" release, it is still based on Debian sid as of this day and is not meant or suited as an alternative way to install "wheezy". Many security sensitive packages in aptosid (Debian sid) already sport a higher version number than their corresponding version in "wheezy" or are even uninstallable in a "wheezy" context.

aptosid after the 'freeze'

Now that Debian 7 Wheezy has been released, the version freeze that reached up to sid will be lifted again within the next few days. Given that there are a number of high impact changes (KDE 4.10.2/ kdepim2, xserver-xorg-core 1.14.0, udisks2, grub2 2.00, etc.) staging in experimental and are just waiting for the freeze to be lifted, the following 2-3 weeks might be slightly more vibrant and potentially less coordinated than usual in regards to package updates from Debian, therefore we recommend a little caution during dist-upgrades. This might involve checking for eventual upgrade warnings on aptosid.com or to wait a few hours if KDE 4.10 or X.org are among the upgrading packages for experiences from advanced users. Please be aware that it might not always be possible to react in time, now that Debian employs four mirror pushes a day.

We'd like to thank our sponsor Webtropia (part of myLoc managed IT AG), who provides hosting for our development– and web infrastructure. The servers from myLoc managed IT AG provide a proper technical solution for our needs, running our own server variant of aptosid.

Our special thanks go to the aptosid art- and manual teams and especially webtropia.com and all mirror hosters for their efforts regarding aptosid.

Now to the interesting topics, like what's on the menu for now:

Frequently asked questions

Installation

It is recommended to set up keymaps, locales and timezone before booting the live system to be installed, by selecting them from the boot menu [F2], [F3]. This way, locale settings propagate to all required places for the installed system and don't require cumbersome changes at several places.

The 64 bit 'amd64' editions should be preferred on modern hardware supporting it.

device mapper/ LVM2/ mdadm/ cryptsetup

A long-standing issue with Debian's initramfs integration for various device mapper based targets, like lvm2, mdadm or cryptsetup, might be triggered more likely due to minor timing changes in recent kernels. "rootdelay=1" as kernel parameter can be used as a temporary workaround for affected systems not finding the rootfs on top of a device mapper backed block device; in rare cases it might be needed to increase the rootdelay further. This setting can be added on the fly from the grub2 boot menu or be made permanent by adding it GRUB_CMDLINE_LINUX in /etc/default/grub and running update-grub afterwards.

efi_no_storage_paranoia

Starting with kernel 3.8.5, the kernel refuses to write efivars if their free space drops below 50% in order to avoid damage to broken Samsung systems. As this also affects updating existing efivars (like grub-efi boot entries, BootOrder or BootCurrent/ BootNext) on existing systems, it is suggested to remove bogus data (older kernels dumped kernel logs in pstore needlessly) from pstore. 

mount -t pstore -o kmsg_bytes=8000 pstore /sys/fs/pstore/
# rm /sys/fs/pstore/*

Due to the nature of various UEFI garbage collector implementations on existing hardware, it might be required to go through a full (non-kexec) reboot, before pstore contents become visible — and another full reboot before the garbage collector actually frees up the space for efivars. Starting with aptosid 2013-01 "Ἑσπερίδες - Hesperides ", pstore is cleared unconditionally during each boot of the live media!

On some hardware, efivars is always more than 50% full starting from the factory settings, for these cases it might be required to supply "efi_no_storage_paranoia" as kernel parameter to live- and installed (GRUB_CMDLINE_LINUX in /etc/default/grub) system; using this kernel parameter might be dangerous on broken UEFI implementations, please use with care.

isohybrid

With isolinux supporting gfxboot, it is possible to use isohybrid, which allows writing an ISO directly to USB storage or sd/ sdhc/ mmc memory sticks to make these bootable.
isohybrid adds an MBR to the ISO and sets up a partition table with one active entry, the partition containing the ISO.
This allows writing aptosid ISOs directly to USB storage devices of sdhc memory cards.
This option is particularly useful if there is no existing aptosid installation available and if an installation medium needs to be created from another distribution or operating system.
It is important to note that this method overwrites the whole USB medium and restricts the available storage to the size of the aptosid ISO.
Further partitions can be added to allow access to the unused part of the storage device. 

$cat /path/to/aptosid-*.iso > /dev/USB_raw_device_node

Further information about the aptosid install is available from the aptosid manual at Installation options.

Wireless regulatory domain settings

The regulatory domain framework for cfg80211 based wlan cards requires crda to allow access to wireless channels above ch11 (2.4 GHz or their 5 GHz equivalents), without crda only the "world domain" (channel 1-11) is available. 

apt-get update 
apt-get install crda

Network booting aptosid

Network booting aptosid over PXE (Preboot Execution Environment) and NBD (Network Block Device) is supported, the required settings can be configured from within the boot menu [F4]. Instructions about how to set up an example PXE+NBD boot server can be obtained at aptosid netboot introduction and in the manual; Booting aptosid over a network.

UEFI booting

Preliminary support for booting with UEFI has been added to the amd64 editions. While the installer GUI has not been finalised yet, the bootloader will be an EFI program installed to /efi/aptosid within your 'EFI system partition' and mounted below /boot/efi/ on your installed system, provided the following conditions are met:

At the moment aptosid only offers UEFI booting for its 64 bit edition (amd64), 32 bit UEFI (such as older Apple systems) is currently not supported.

Please also refer to "efi_no_storage_paranoia" above.

UEFI bootable removable devices

In order to create a UEFI bootable device, such as a USB stick, the contents of the aptosid ISO can be extracted to a vfat formatted partition and the partition marked as bootable. Optionally this removable medium can also be made compatible with PC-BIOS booting by installing a traditional bootsector in addition to the EFI bootloader (assuming /dev/sdz1 to be the target partition on the USB stick). 

syslinux -i -d /boot/isolinux /dev/sdz1
install-mbr /dev/sdz

Microsoft UEFI Secure Boot

There are currently no plans to support Microsoft UEFI Secure Boot. In order to allow dual-booting with other operating systems, this option needs to be disabled in the system firmware. Toggling this firmware setting does not break the installed operating system.

Localisation

A special feature of kde-full releases is the ability to select other languages than German or US English from the boot menu (F2), which automatically installs localisations for the desktop and many applications while booting. This ensures they are also present after installing aptosid, while only installing the required languages for the given system. The amount of memory required for this feature depends on the language and aptosid may refuse to install the given language packs automatically with insufficient RAM and the boot sequence will be continued in english language but with the desired locales-settings (currency, date/ time format, keyboard charsets). 1 GB memory or more is supposed to be safe for all supported languages, which are:

The language selection depends on the availability of aptosid-manual translations, get involved to add your language. Levels of up-to-date translation completeness of the following languages has dropped below the quorum for inclusion at this moment:

Additional help is urgently needed for these languages to bring the translations up to date for the language concerned.

Hints for Upgraders:

aptosid tries hard to provide seamless upgrade path for debian and aptosid' own packages, nevertheless a few things remain that could be improved with manual interaction.

Obsolete packages

As part of the continuing development of aptosid, a number of packages have been replaced by better alternatives or become redundant.

Transitional packages and obsolete libraries can often be identified by "deborphan". While this tool is very convenient for ongoing system cleanup, its results should always be checked before using it as input for removals. 

$ deborphan

The following command is able to find packages not available from any active apt repository and may hint at obsolete packages, be careful about manually installed packages though.

$ apt list 2>/dev/null | awk -F '/' '/installed,local/{print $1}'

How to get involved

Getting involved in aptosid is easy, just join us at our Forum or even better on IRC (irc.oftc.net, port 6667, channel #aptosid) and discuss your patches/ proposals or additions.

We will gladly discuss any dfsg-free patches and contributions, especially regarding alternative window managers (GNOME, LXDE), general cleanup tasks or translations/ localisations.

Roadmap:

Please understand that the following roadmap is a rough estimate regarding our release schedule and is affected by the status of upstream Debian sid, major system components like X.org, KDE, the linux kernel and our own developments and is subject to changes.

Content last revised 13/05/2013 1520 UTC