Today I patched the brand new zen-sources-2.6.31-r2 with tuxonice. Again it required the modified tuxonice patch of my last ebuild.
Suspend to RAM works at least on my Dell Precison M65 as well as suspend to disk does.
Download the zen-sources 2.6.31-zen2 patch here: zen-sources.org. Then apply the patch to vanilla kernel sources. Afterwards download my modified tuxonice patch from here: . Then apply it.
For Gentoo users there is a more easy way: Download my modified overlay (including the patches) from
and extract it in /usr/local/portage. Be sure to include the following line in your /etc/make.conf:
PORTDIR_OVERLAY=”/usr/local/portage”
Then emerge zen-sources-toi and buld the kernel as you wish.
Tuxonice is not officially supported in zen-sources. So If you’re using the files above, don’t report any bugs to zen-sources.org. You are on your own.
For my Precision M65 I used the following kernel config:
All Information regarding the iwl3945 driver, the aha152x pcmcia scsi card and cpu undervolting in my last post on zen-sources-toi still apply to this version.
Today I patched the new zen-sources-2.6.31-r1 with tuxonice. This time it was a bit more complicated since the two patches are conflicting. So I modified the tuxonice patch to apply cleanly over the zen-kernel.
Suspend to RAM works at least on my Dell Precison M65 as well as suspend to disk does.
Download the zen-sources 2.6.31-zen1 patch here: zen-sources.org. Then apply the patch to vanilla kernel sources. Afterwards download my modified tuxonice patch from here:
For Gentoo users there is a more easy way: Download my modified overlay (including the patches) from and extract it in /usr/local/portage. Be sure to include the following line in your /etc/make.conf:
PORTDIR_OVERLAY=”/usr/local/portage”
Then emerge zen-sources-toi and buld the kernel as you wish.
To work around the black screen problem with some nvidia-drivers versions occuring with 2.6.30 kernels, discussed at gentoo forums, I had to upgrade to nvidia-drivers-190.18. Most probably this problem persists with 2.6.31. Strangely the issue did only occur on my Precision M65 with a Quadro FX350M. It did not occur with the Quadro FX3400 in my Desktop PC, Nvidia-drivers-185.18.31 are running there without any problems.
Tuxonice is not officially supported in zen-sources. So If you’re using the files above, don’t report any bugs to zen-sources.org. You are on your own.
For my Precision M65 I used the following kernel config:
If you want to use all channels with the iwl3945 driver change the line static char *ieee80211_regdom = “US”; to static char *ieee80211_regdom = “JP”; in the file net/wireless/reg.c.
If you also own of those old 16 Bit Adaptec pcmcia scsi cards using the aha152x_cs module you might want to enable it also for 64 Bit kernels. It was masked for 64 Bit kernels somewhere before 2.6.13. I was unable to find out the reason for this so I tried to compile the module. When I insert the card, the module loads properly. Since the drive I could test it with, is currently attached to another box and in use, I can´t try it out for the moment. Once I tried I´ll keep you updated.
To enable the driver remove the line
depends on !64BIT
in the config PCMCIA_AHA152X section in /usr/src/linux/drivers/scsi/pcmcia/Kconfig and select the module in menuconfig.
Addon: I tried a SCSI cdrom with this and it works perfectly. I just filed a bug on this on bugzilla.kernel.org and hope for the driver being unmasked for future 64 Bit kernels.
If you are using this kernel on a notebook with i.e. a Core2 CPU you might be interesting to undervolt your CPU to save power and to produce less heat (keeps the fan off longer). This works like a charm on my M65. Information on this topic can be found here: aldeby.org. The linux-pch patch mentioned there is already included in zen-sources, thus you only have to perform the userspace part begnning at (3).
For image compression in tuxonice include Compressor lzo in your suspend2.conf file.
Sadly the iptables mirror target I published here does not work anymore with the 2.6.31 kernel. A newer version will be available soon on mygnu.de.
After updating my gentoo-linux boxes I recognized enigmail asking for the password multiple times when decrypting a single mail. Some days later, when I rebooted the system gnome did not start anymore.
A quick look into my/var/log/messages showed:
Oct 2 10:50:43 hostname seahorse-agent[419]: segfault at 0 ip 0000000000432fb8 sp 00007fff01ceb150 error 4 in seahorse-agent[400000+50000] Oct 2 10:50:43 hostname seahorse-agent[419]: init_gpgme: assertion `GPG_IS_OK (err)’ failed Oct 2 10:50:43 hostname seahorse-agent[419]: seahorse_pgp_source_init: assertion `GPG_IS_OK (err)’ failed Oct 2 10:50:43 hostname seahorse-agent[419]: unsupported key server uri scheme: ldap
So I suspected seahorse to be responsible for this missbehaviour. When searching the net for the problem I found the corresponding bug entry on bugs.gentoo.org. The problem was caused by some changes in gpgme-1.2.0. The patch from there solved the problem for me. After reemerging seahorse and rebooting the system gnome did start again and enigmail worked properly.
Today I patched the brand new zen-sources-2.6.30-r4 with tuxonice. This was necessary since I need tuxonice on my notebook for suspend modes and tuxonice has been removed permanently from zen-sources. Suspend to RAM works at least on my Dell Precison M65 as well as suspend to disk does.
I recommend using this version over using the r3-version, because it fixes the root exploit vulnerability mentioned on www.linux-magazine.com.
and extract it in /usr/local/portage. Be sure to include the following line in your /etc/make.conf:
PORTDIR_OVERLAY="/usr/local/portage"
Then emerge zen-sources-toi and buld the kernel as you wish.
To work around the black screen problem with some nvidia-drivers versions, discussed at gentoo forums, I had to upgrade to nvidia-drivers-190.18. Strangely the issue does only occur on my Precision M65 with a Quadro FX350M. It does not occur with the Quadro FX3400 in my Desktop PC, Nvidia-drivers-185.18.31 are running there without any problems.
Tuxonice is not officially supported in zen-sources. So If you’re using the files above, don’t report any bugs to zen-sources.org. You are on your own.
For my Precision M65 I used the following kernel config:
If you want to use all channels with the iwl3945 driver change the line
static char *ieee80211_regdom = “US”;
to
static char *ieee80211_regdom = “JP”;
in the file net/wireless/reg.c.
If you are using this kernel on a notebook with i.e. a Core2 CPU you might be interesting to undervolt your CPU to save power and to produce less heat (keeps the fan off longer). This works like a charm on my M65. Information on this topic can be found here: aldeby.org. The linux-pch patch mentioned there is already included in zen-sources, thus you only have to perform the userspace part begnning at (3).
Today I managed to patch the brand new zen-sources-2.6.30-r3 with tuxonice. This was necessary since I need tuxonice on my notebook for suspend modes and tuxonice has been removed permanently from zen-sources. Suspend to RAM works at least on my Dell Precison M65 as well as suspend to disk does.
and extract it in /usr/local/portage. Be sure to include the following line in your /etc/make.conf:
PORTDIR_OVERLAY="/usr/local/portage"
Then emerge zen-sources-toi and continue with building the kernel as you wish.
To work around the black screen problem with some nvidia-drivers versions, discussed at gentoo forums, I had to upgrade to nvidia-drivers-190.18. Strangely the issue does only occur on my Precision M65 with a Quadro FX350M. It does not occur with the Quadro FX3400 in my Desktop PC, Nvidia-drivers-185.18.31 are running there without any problems.
Tuxonice is not officially supported in zen-sources. So If you’re using the files above, don’t report any bugs to zen-sources.org. You are on your own.
For my Precision M65 I used the following kernel config:
Today, when I tried to sync the portage overlays on my gentoo linux boxes, I got the error:
ImportError: No module named layman.config
The recent update from python-2.5 to python-2.6 has broken several applications. This issue was solved by running python-updater, which re-emerges all broken python packages. Besides from layman not working, the python upgrade may cause several other problems in portage and in the whole system. Thus just be sure to run python-updater after the python-upgrade.
A while ago during regular upgrades my gentoo box serving as test environment for vservers updated to util-vserver-0.30.216_pre2841. Some weeks later, when I restarted the box I recognized that it could not start any vserver:
An error occured while executing the vserver startup sequence; when there are no other messages, it is very likely that the init-script (/etc/init.d/rc 3) failed.
Common causes are: * /etc/rc.d/rc on Fedora Core 1 and RH9 fails always; the ‘apt-rpm’ build method knows how to deal with this, but on existing installations, appending ‘true’ to this file will help.
The box is running vserver-sources kernel 2.6.28-vs2.3.0.36.4-gentoo #2 SMP.
Since I did not find any useful information regarding his error in the web I tried downgrading to util-vserver-0.30.215-r3. For gentoo users this is accomplished by including
>sys-cluster/util-vserver-0.30.215-r3
in /etc/portage/package.mask. Afterwards everything reverted to normality.
If you also experience the “pivot_root(): Invalid argument” error, try downgrading util-vserver and hope for the best 😉
MyGNU.de
![[Valid RSS]](https://validator.w3.org/feed/images/valid-rss.png "Validate my RSS feed")
