Re: udev problem Was: kernel modules not loading at boot after upgrade

2011-04-09 Thread Ernesto Domato
On Fri, Apr 8, 2011 at 16:27, Ernesto Domato edo...@gmail.com wrote: Ok. I downgrade the udev package (and libudev0 dependency) from 167-1 to 166-1 and it solved the problem so I guess my behavior could come from it. Looking at the logs it says, when I upgraded to 167-1, converting old udev

udev problem Was: kernel modules not loading at boot after upgrade

2011-04-08 Thread Ernesto Domato
On Thu, Apr 7, 2011 at 18:34, Ernesto Domato edo...@gmail.com wrote: Hi, I'm using Debian AMD64 Sid/Experimental on a laptop and after upgrading it yesterday my touchpad, sound and battery applet stop working. I found that the kernel is not autoloading the respective modules (psmouse, snd-hda

kernel modules not loading at boot after upgrade

2011-04-07 Thread Ernesto Domato
Hi, I'm using Debian AMD64 Sid/Experimental on a laptop and after upgrading it yesterday my touchpad, sound and battery applet stop working. I found that the kernel is not autoloading the respective modules (psmouse, snd-hda-intel and battery) on boot and even placing them on /etc/modules doesn't

ia32-aptitude vs. aptitude

2009-09-25 Thread Ernesto Domato
Hi, I like the idea of the ia32-* packages managed by the ia32-apt-get package till multiarch is ready but I found that the amount of packages to be upgraded differs from aptitude to ia32-aptitude. As for today for example, I have 195 packages to upgrade using aptitude but ia32-aptitude only

Skype 2.1 with ia32-libs Was: ia32-aptitude vs. aptitude

2009-09-25 Thread Ernesto Domato
On Fri, Sep 25, 2009 at 18:30, Dave Witbrodt dawit...@sbcglobal.net wrote: For now, the officially supported solution is 'ia32-libs' again.  The officially-supported multiarch solution is on the way relatively soon, so you'll have to decide whether to keep Goswin's no-longer-official packages

Re: Skype 2.1 with ia32-libs Was: ia32-aptitude vs. aptitude

2009-09-25 Thread Ernesto Domato
On Fri, Sep 25, 2009 at 22:00, Sam Varghese s...@gnubies.com wrote: Why don't you just use the statically compiled version? Unpack it in a directory and run it from there. The statically compiled version has the same problem and solution that the .deb package version. You'll have to delete