lubuntu-qa team mailing list archive

[JM <meets@xxxxxx>]

Hi all,

Has anyone noticed that zram is a normal kernel module, which is not only enabled but
also configured thanks to the zram-config scripts? I am asking because of the post you
point to at the forum.

There would be a simple solution to satisfy all people : an additional script to enable
and disable it at will, from within the system menus.

I would not insist enough about the way it is configured actually, in the Ubuntu
zram-config scripts. The system need a control over swappiness, and for zram smaller block
devices. Really!

In my T30 Lubuntu as of yesterday lags badly, whereas the Ubuntu Openbox Remix installed
in it, with the setups I pointed to, is snappy! (Lubuntu does  not use much more RAM
btw). I suspect the setup, although I have not had time today to reconfigure it and retry.

Regards,
Mélodie

PS: Lars, about your test with Thunderbird and Firefox, I'm not too much astonished: both
are heavy... what about trying Sylpheed along with Midori in that 1 GB Macmini machine of
your's? :)


On Mon, 23 Sep 2013 23:17:43 +0100
Phill Whiteside <PhillW@xxxxxxxxxx> wrote:

> Hi Joe,
> 
> I have got the final beta installed fine with 512Mb of RAM in my VM system.
> It is running 3.11.0-8.15 I pinged you on #ubuntu-kernel to check if the
> fix had dribbled down into that .8-15 kernel.
> 
> The issue as reported at
> http://ubuntuforums.org/showthread.php?t=2162655&p=12735571#post12735571 is
> still there.
> 
> Regards,
> 
> Phill.
> 
> 
> On 23 September 2013 17:14, Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx
> > wrote:
> 
> > On 09/21/2013 01:20 PM, Phill Whiteside wrote:
> > > Lars,
> > >
> > > thanks for that.. can you update the bug.. there is the impossible
> > > part of pulling in something from the 3.12 kernel. Any reports we can
> > > give to the bug will hopefully assist the kernel team, as zram seems
> > > to fairly broken in the 3.11 kernel.
> > >
> > > Regards,
> > >
> > > Phill.
> > >
> > >
> > > On 21 September 2013 18:11, Lars Noodén <lars.nooden@xxxxxxxxx
> > > <mailto:lars.nooden@xxxxxxxxx>> wrote:
> > >
> > >     On 09/21/2013 08:00 PM, Phill Whiteside wrote:
> > >     > At this point it seems that we are trapped between a rock and a
> > >     hard place.
> > >     >
> > >     > Kernel team <> ISO team. ::SIGH:: Such frustrations led to my
> > >     resigning
> > >     > from various teams, I've asked a couple of people who can make
> > >     an ISO with
> > >     > the test kernel if they would. Other than that, my hands are tied.
> > >     >
> > >     > We need an ISO with the patch that has been already applied
> > >     upstream into
> > >     > it.... Grrrrr.
> > >     >
> > >     > Regards,
> > >     >
> > >     > Phill.
> > >
> > >     I did try this kernel the other day and it did lock up just like
> > >     the one
> > >     in the repository:
> > >
> > >     linux-image-3.11.0-7-generic_3.11.0-7.14~lp1227202v1_amd64.deb
> > >
> > >     I thought I wrote it in a message, but can't find it in my archive,
> > so
> > >     maybe I didn't.
> > >
> > >     So far turning off zram seems to be the only thing that works.  Or at
> > >     least seems to work, so far so good.
> > >
> > >     Regards,
> > >     /Lars
> > >
> > >     --
> > >     Mailing list: https://launchpad.net/~lubuntu-qa
> > >     <https://launchpad.net/%7Elubuntu-qa>
> > >     Post to     : lubuntu-qa@xxxxxxxxxxxxxxxxxxx
> > >     <mailto:lubuntu-qa@xxxxxxxxxxxxxxxxxxx>
> > >     Unsubscribe : https://launchpad.net/~lubuntu-qa
> > >     <https://launchpad.net/%7Elubuntu-qa>
> > >     More help   : https://help.launchpad.net/ListHelp
> > >
> > >
> > >
> > >
> > > --
> > > https://wiki.ubuntu.com/phillw
> >
> > First of all, Thanks for all the hard work, everyone.
> >
> > Do we know for sure if this issue is actually fixed in upstream
> > v3.12-rc1?  Lars, were you able to test and ISO with the test kernel
> > built in, or can you reproduce the bug just by booting into the test
> > kernel?
> >
> > Thanks,
> >
> > Joe
> >
> >
> 
> 
> -- 
> https://wiki.ubuntu.com/phillw


-- 
JM <meets@xxxxxx>