Another workaround might be to use Ubuntu's own compressed image with a
preinstalled Ubuntu Server (although not officially released) according
to the following link
https://ubuntuforums.org/showthread.php?t=2474692
Scroll down to read also the following posts, that describe how to
install Lubunt
If you have problems to boot live systems (from USB), I think it can be
solved with mkusb
https://help.ubuntu.com/community/mkusb
because it makes the live system use GFXMODE set to 800x600 except when
cloning. So select 'live-only' and in the next menu 'dus-iso2usb' ...
Please report the result
Do you think this bug is somehow related to the following bug?
https://bugs.launchpad.net/bugs/1886148
For example, are there problems to boot into a live system from a USB
drive in a real system, or booted from a virtual hard disk drive with
the image in a virtual machine? (I know that it boots
Maybe this bug is located in casper (like 1848404)
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1848404
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1848333
Title:
wifi pro
** Description changed:
This problem is rather new. It did not affect Lubuntu Eoan zsynced 9
days ago (Oct 6).
Now there is a delay of 1 min 30 sec during booting, and I think there
is something wrong with the recognition of the wifi hardware or maybe
matching of driver and hardware.
attached photo showing the waiting
** Attachment added: "lubuntu-waiting-90s.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848333/+attachment/5297779/+files/lubuntu-waiting-90s.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
I had also an Ubuntu Eoan iso file from Sept 25 and got a new one now.
Both boot fast, but do not behave in the same way. The current Ubuntu
sends a notify message to the desktop:
"Network service discovery disabled
Your current network has a .local domain, which is not recommen..."
This notice i
attached what I think are relevant lines from 'syslog'
** Attachment added: "relevant lines from 'syslog'"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848333/+attachment/5297468/+files/temp.txt
--
You received this bug notification because you are a member of Kernel
Packages, which
Public bug reported:
This problem is rather new. It did not affect Lubuntu Eoan zsynced 9
days ago (Oct 6).
Now there is a delay of 1 min 30 sec during booting, and I think there
is something wrong with the recognition of the wifi hardware or maybe
matching of driver and hardware. It happens in '
More testing, this time also with Xubuntu 18.10, 32 bit.
Testing in my Dell laptop
https://www.cnet.com/products/dell-precision-mobile-
workstation-m4800-15-6-core-i7-4810mq-8-gb-ram-256-gb-ssd-english/specs/
Lubuntu 18.10, 32 bit:
The persistent live USB drive (by mkusb) boots and runs without
More testing, this time also with Xubuntu 18.10, 32 bit.
1. Testing in my Dell laptop
https://www.cnet.com/products/dell-precision-mobile-
workstation-m4800-15-6-core-i7-4810mq-8-gb-ram-256-gb-ssd-english/specs/
Lubuntu 18.10, 32 bit:
The persistent live USB drive (by mkusb) boots and runs with
More testing, this time also with Xubuntu 18.10, 32 bit.
1. Testing in my Toshiba laptop (link in my previous comment)
I needed the boot option nomodeset to get 'more than an underscore' on
the screen. Then the boot process of a *cloned* USB drive as well as a
persistent live USB drive (by mkusb)
I *think* that this bug affects me too:
I am able to boot Lubuntu 18.10 in my Toshiba laptop with 64-bit
architecture both in UEFI and BIOS mode.
http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w/
I used mkusb to create a persistent live drive (using default settings).
Mayb
Both.
I discovered it testing Xenial, but it appears also today, when I'm
testing Yakkety.
You may edit the tags accordingly. (I usually avoid editing tags and
leave it to people more involved in the administration.)
--
You received this bug notification because you are a member of Kernel
Packa
@ Joseph Salisbury (jsalisbury),
I have been trying to think.
- I don't think it helps with a new kernel, because Lubuntu desktop of
the corresponding daily-live iso file works (can identify the drive via
that USB 3 adapter). See post #4.
- It would be very hard for me to create an alternate iso
@ Joseph Salisbury (jsalisbury),
I have been trying to think.
- I don't think it helps with a new kernel, because Lubuntu desktop of
the corresponding daily-live iso file works (can identify the drive via
that USB 3 adapter). See post #4.
- It would be very hard for me to create an alternate iso
I'll try, but I am a total newbie concerning new or non-standard
kernels, so I'm not sure it will work for me :-P
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1596281
Title:
the target
I continued testing the problem with
- the released version lubuntu-16.04-alternate-amd64.iso
- another adapter/box to connect the SSD via USB 3.
And this is the result:
This (new) adapter, Deltaco USB 3.0 to SATA II cable fails also with the
released version, so it is an old bug.
An (older) A
** Summary changed:
- the target drive is not found when connected via USB 3
+ the target drive is not found when connected via USB 3 while installing
Lubuntu alternate
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
Commands illustrating how the target drive is recognized by the desktop
system.
** Attachment added: "commands.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1596281/+attachment/4690472/+files/commands.txt
--
You received this bug notification because you are a member of Kernel
Pa
Public bug reported:
While trying to install from the Lubuntu 16.04 LTS alternate amd64 daily
iso file, the target drive is not found when connected via USB 3.
This happens with an SSD connected via USB 3. The corresponding desktop
iso file works, and the released Lubuntu 16.04 LTS alternate amd6
+1 for Lubuntu 16.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1552985
Title:
[Dell Inspiron 14 3000 Series] System hangs on poweroff
Status in linux package in Ubuntu:
Expired
This bug is still alive in Lubuntu Xenial final.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1359689
Title:
cryptsetup password prompt not shown
Status in linux package in Ubuntu:
It seems to me that this bug affects systems booted via syslinux, but
not systems booted via grub.
See this comment to a related bug report,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552985/comments/17
--
You received this bug notification because you are a member of Kernel
Packages
Booted via grub-n-iso shutdown works for me, but not when the pendrive
was created by cloning the current Lubuntu Xenial i386 daily iso file,
xenial-desktop-i386.iso
Today I tested with USB-creator-gtk 0.3.2 and mkusb, but can get the
same result with other cloning tools, e.g. gnome-disks, dd.
I
I have seen indications that it makes a difference which tool or method
was used to create the USB boot drive. So please tell us which tool was
used when this bug appeared, as if you get different results when trying
to shut down, when the USB drive was created with different tools or
methods.
--
I have seen indications that it makes a difference which tool or method
was used to create the USB boot drive. So please tell us which tool was
used when this bug appeared, as if you get different results when trying
to shut down, when the USB drive was created with different tools or
methods.
--
This problem is still there in Lubuntu desktop, which means the desktop
iso file with the graphical user interface.
The problem appears on desktop computers as well as on laptop computers,
and I think it is caused by problems with plymouth (which displays
nothing, no logo, no dots, (and no passphr
I see.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1305480
Title:
BUG: pcmC0D0p:0, pos = 16390, buffer size = 16384, period size = 1024
Status in linux package in Ubuntu:
Fix Relea
I have tried,
$ uname -a
Linux xenial32 4.5.0-040500rc7-generic #201603061830 SMP Sun Mar 6 23:43:15 UTC
2016 i686 i686 i686 GNU/Linux
but it is the same (this kernel does not solve the problem). Instead, I
suspect another bug. Please look at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug
OK, I think I managed to add the tag 'kernel-bug-exists-upstream'
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1555487
Title:
snd_au8820 :01:04.0: BUG: , pos = 16388, buffer size =
Bug #1551041 affects my hp xw8400 workstation when running 32-bit
*Xenial*. Raymond (superquad-vortex2) has helped me identify the
problem, and he found, that it is probably caused by what you describe
in the following link,
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound
This bug does *not* affect precise and *not* trusty. Sorry if that was
not clear in the original comment.
It only affects *xenial*
** Description changed:
- Directly at login after reboot I had many prompts to send a bug report
- about kernel oops. I tried to count them. think this report is
- r
Public bug reported:
Directly at login after reboot I had many prompts to send a bug report
about kernel oops. I tried to count them. think this report is
responding to the 26th prompt to send a bug report, and a few seconds
later there was one more prompt to send a bug report.
I think it is a du
Public bug reported:
Probably a duplicate of Bug #1551041.
I upgraded to a new kernel today and it works well. No kernel oops
during normal operation.
I started a virtual machine in VirtualBox - still no kernel oops. I
closed the virtual machine, and then there was a kernel oops, and this
report
I upgraded to a new kernel today and it works well. No kernel oops
during normal operation.
I started a virtual machine in VirtualBox - still no kernel oops. I
closed the virtual machine, and then there was a kernel oops, bug report
#1554980
But I notice no other problem (than prompting the bug r
Thank you for working with this bug :-)
But I must admit, that I don't understand what is the problem. Except
from the automatic prompting for bug reports, I do not notice any
problem. The computer run happily like it has been running with older
versions of Lubuntu and Xubuntu.
And since I see no
Public bug reported:
This time the bug appeared directly after login
ProblemType: KernelOops
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-9-generic 4.4.0-9.24
ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
Uname: Linux 4.4.0-9-generic i686
NonfreeKernelModules: nvidia
Annotation:
Public bug reported:
This occurred after upgrading to the following kernel
$ uname -a
Linux xenial32 4.4.0-9-generic #24-Ubuntu SMP Mon Feb 29 19:30:41 UTC 2016 i686
i686 i686 GNU/Linux
and it was triggered by starting a virtual machine with VirtualBox.
ProblemType: KernelOops
DistroRelease: U
Public bug reported:
Occurred right after login, several very similar bug alerts happened,
this report is about one of them.
pos = 16384
pos = 16386
pos = 16388
...
ProblemType: KernelOops
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-8-generic 4.4.0-8.23
ProcVersionSignature: Ubuntu 4.
Public bug reported:
This is similar to a bug report a few minutes ago. This time I could
start a virtual machine in VirtualBox - there is the prompt to a bug
report, but thing work anyway.
ProblemType: KernelOops
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-8-generic 4.4.0-8.23
ProcVer
Public bug reported:
This happened when I tried to run VirtualBox
ProblemType: KernelOops
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-8-generic 4.4.0-8.23
ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
Uname: Linux 4.4.0-8-generic i686
NonfreeKernelModules: nvidia
Annotation: Yo
Public bug reported:
Kernel oops in a new installed system, that I configuring ...
ProblemType: KernelOops
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-8-generic 4.4.0-8.23
ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
Uname: Linux 4.4.0-8-generic i686
NonfreeKernelModules: nvid
** Description changed:
+ Edit:
+
+ This new syntax for boot options (alias this bug) affects also the
+ Ubuntu Server 14.04.2 LTS iso files. I tested the 32-bit version,
+
+ ubuntu-14.04.2-server-i386.iso
+
+ and it needed
+
+ ... forcepae -- forcepae
+
+ to work in my Thinkpad T42 with Pent
This new syntax for boot options (alias this bug) affects the Ubuntu
Server 14.04.2 LTS iso files. I tested the 32-bit version,
ubuntu-14.04.2-server-i386.iso
and it needed
... forcepae -- forcepae
to work in my Thinkpad T42 with Pentium M.
Expect that there are other cases, where the boot opt
I tested Lubuntu trusty-alternate-i386.iso (14.04.2 LTS) in my IBM
Thinkpad T42 with Pentium M, and this bug is squashed here too with this
double boot option.
I clicked F6 and ESC to get to the boot line and changed the end of it
from
... quiet --
to
... quiet forcepae -- forcepae
But the oth
I tested the Ubuntu Vivid daily 32-bit mini.iso (dated feb 9) in my IBM
Thinkpad T42 with Pentium M, and it works for me too with this double
boot option.
I clicked tab to get to the boot line.
I edited the boot line from
> linux vga=788 initrd=initrd.gz -- quiet
to
> linux vga=788 initrd=init
I try to make it clear what works and what does not work with Pentium M and
Celeron M processors that have PAE capability but lack the PAE flag.
_
These iso files work:
Ubuntu Trusty mini.iso (dated jan 30)
http://archive.ubuntu.com/ubuntu/dists/trusty-upd
I tried: Neither apport-collect nor apt-get are available in the
alternate installer, so I can't run it and I don't know how to install
it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/14
Someone managed to make you add the boot option forcepae, and it has
been used successfully until now.
Please fix what is probably a minor bug, to keep 14.04.x available for
computers with Pentium M and Celeron M processors !
--
You received this bug notification because you are a member of Kern
This same problem occurs during iso-testing for the point version
14.04.2 LTS
lubuntu-trusty-alternate-i386.iso
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1422675
Title:
No installa
Sorry,
apport-collect 1422675
does not work in the mini.iso system :-(
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs
Public bug reported:
I tried to install from the Ubuntu Vivid 32-bit mini.iso into a computer
with Pentium M
http://www.cnet.com/laptops/lenovo-
thinkpad-t42-2373/4507-3121_7-31155666.html
and booted the installer with the forcepae boot option. This made the
installer start and work until it sho
Sorry for the confusion,
*I asked*
> I have a couple of questions about your Sony Vaio with Pentium M:
>
> What happens when you try to boot a PAE kernel with forcepae? Do you get
> an error message? Black screen?
>
> Are you sure it is not 'only' a problem with some other hardwar
Hi Chris,
1. It is not my computer. I have one with a very similar Pentium M CPU
which works with forcepae. I have asked the same questions but not yet
received a full answer from the owner. I will ask again ...
2. Thanks for finding the difference between the cpuid flags "a7e9fbbf"
and "afe9fbbf
The vast majority of Pentium M and Celeron M CPUs are suitable for
fakepae or forcepae and can work with PAE kernels. But some of these
processors need a non-pae kernel.
We found a Pentium M 1.70 GHz which does not work with forcepae. It
gives the following output from
cpuid|grep ^0001
0
Yes, it would be nice for the user to not have to bother with forcepae
to run computers with Pentium M and Celeron M CPUs.
But I think this is a great improvement. Forcepae (used according to
Colin Watson's advice in post #8) makes it much easier to use Ubuntu
flavours in version 14.04 LTS compare
I can confirm that Colin Watson's advice in post #8 works.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1307105
Title:
Kernel install fails due PAE checks
Status in “linux” package in
This is new and positive information :-)
I did not know the function of -- and I think many people need to be
informed about it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1307105
Tit
*** This bug is a duplicate of bug 1307105 ***
https://bugs.launchpad.net/bugs/1307105
** This bug has been marked a duplicate of bug 1307105
Kernel install fails due PAE checks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
I was testing the Lubuntu Trusty desktop i386 final iso file and had the
message 'This kernel does not support a non-PAE CPU' when I tried to
install the low latency kernel.
Please make the installer (or some other program part) add forcepae
into /etc/default/grub and from there into /boot/grub/g
My bug report seems to be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307105
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1307862
Title:
package linux-image-3
** Summary changed:
- package linux-image-3.13.0-24-lowlatency (not installed) failed to
install/upgrade: underprocessen nytt pre-installation-skript gav felkod 1
+ package linux-image-3.13.0-24-lowlatency (not installed) failed to
install/upgrade: underprocessen nytt pre-installation-skript gav
Just to confirm my suggested solution, I added forcepae to
/etc/default/grub
and ran
sudo update-grub
After reboot it was possible to install the new kernel (in this somewhat
synthetic case the low-latency kernel), and the computer can run with it
(both kernels work).
--
You received this bug
Public bug reported:
I installed Lubuntu with the boot option forcepae into a computer with
Pentium M with PAE capability but without PAE flag. It worked. But the
forcepae boot option was not automatically added in
/etc/default/grub and from there into /boot/grub/grub.cfg
so when I try to instal
Maybe the automatically collected data in Bug #1300645 helps you solving
the problem. (I was prompted into a new bug report.)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1299473
Title:
I have this bug too: I get the spinning wheel forever instead of the
windows of the installer.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1299473
Title:
ubiquity hangs when trying to
:-)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/930447
Title:
Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M
x86 Laptop due to bug in PAE kernel, initramfs o
a gpg key separately.
Best regards
sudodus alias Nio
- Comment #279 -
Chris Bainbridge (chris-bainbridge) wrote on 2014-03-03:#279
lkml: "grub is jumping to the 32-bit entry point and skipping the entire
real mode setup code. Bad grub."
You don't need to build a sysli
@Frogman - fakePAE trick
Until the new patches in the main-stream code trickle down (maybe it
stays in 14.04 LTS), I suggest that you try
Lubuntu-fake-pae according to this link
https://help.ubuntu.com/community/Lubuntu-fake-PAE
or if you want some other flavour of Ubuntu, you have a wide choic
What about the boot option 'forcepae'?
Is it still available, and possible to use in order to make Pentium M
and Celeron M run a PAE kernel?
In that case, I think that it should be described in the wiki page that
the error text is referring to
https://help.ubuntu.com/community/EnablingPAE
inste
... and the text in https://help.ubuntu.com/community/EnablingPAE will
need updating too, and there are volunteers that can do that (for
example I can do it, unless someone has 'adopted' that wiki page and
wants to do it).
--
You received this bug notification because you are a member of Kernel
P
Thanks Chris :-)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/930447
Title:
Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M
x86 Laptop due to bug in PAE kernel
ERROR: PAE is disabled on this Pentium M
(PAE can potentially be enabled with kernel parameter
"forcepae" - this is unsupported, may cause unknown
problems, and will taint the kernel)
This kernel requires the following features not present on the CPU:
pae
Unable to boot - please use a kernel appro
Works in my IBM Thinkpad T42 with Pentium M without a PAE flag but with
PAE capability.
But I have only booted via grub, because I cannot remaster an iso file.
Did you boot from syslinux, Roland?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
There were *very* strong signals that the board, deciding about the
main-stream ubuntu edition, had decided to stop supporting non-pae CPUs
including Pentium M amd Celeron M, and that the decision was not going
to be changed.
You think that fake-PAE has been counter-productive, that it has done
mo
All the main Ubuntu flavours of version 13.10 are available as tarballs
to be installed with the One Button Installer,
ubuntuforums.org/showthread.php?t=2172971
and this works with Pentium M and Celeron M CPUs. Experimental Trusty
tarballs are already uploaded,
http://ubuntuforums.org/showthread
'...Why?? PAE Kernel!! I had to install 12.04, install fake-pae and the
make 3 (THREE) dist upgrades! (after days of research). Why force users
that have a PAE capable cpu (unlikely not advertised) to make tricks and
3-4-5 etc distribution upgrades just to be able to install the latest
distribution
+1
(good news, thanks)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/930447
Title:
Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M
x86 Laptop due to bug in PAE
Roland,
1. Thanks for keeping this issue alive :-)
2. We have evidence that these two CPUs also have PAE capability but no
PAE flag:
Celeron M 1200 Mhz 0001 0695 0812 a7e9f9bf
Celeron M 1300 MHz 0001 0695 0812 a7e9f9bf
Best regards
Nio
--
You received
I think so too [that the faster ones with 133 MHz FSB (533 MHz transfer
rate) actually do report PAE].
Thank you for that cpuid line! I'll upload it into the list at
https://help.ubuntu.com/community/Lubuntu-fake-PAE#Test
--
You received this bug notification because you are a member of Kernel
Hi Oliver,
That is the fastest Pentium M without a PAE flag reported yet in this
project :-) Please post also the short output of the following command
line,
cpuid|grep ^0001
Best regards
Nio
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
Hi Roland,
Nice list :-) How did you compile it? Are all those CPUs tested, or are
you adding some of the CPUs versions via logical conclusions?
Best regards
Nio
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
There is a start for such a whitelist in comment #203 :-)
If *you* have a Celeron M or Pentium M different from those in that
list, please supply your result of the PAE test described in
https://help.ubuntu.com/community/Lubuntu-fake-PAE
--
You received this bug notification because you are a m
I tested Mélodie's system in a Toshiba with an Intel i5 processor according to
the attached file "submission.xml".
zram was active (without any tweaks by me).
--
>> Yes What do you expect Xnoise to do? I'm familiar with Audacity.
>
> It seems not to be able to read ogg files I don't know why and
On 2013-10-01 18:02, Phill Whiteside wrote:
> Hi Nio,
>
> I just popped desktop amd64 onto my VM, no hang and..
>
> swapon -s reports zram as being in use.
>
> Happy days!
>
> Phill.
>
Great news :-)
Nio
--
You received this bug notification because you are a member of Kernel
Packages, whic
I can try it.
I understand the sudo commands, but how to apply 'CONFIG_ZRAM=m'? Is it
a boot option? Or should it be entered in a config file somewhere?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
Hi Joseph,
Testing the ISO file of post #22:
When zram is running in Lubuntu I can see zram block devices with
swapon -s
but I can see no such devices running from this ISO file.
- Is zram running although I see no zram block devices?
- How can I activate zRAM or check that it is really running?
On 2013-09-26 00:45, Phill Whiteside wrote:
> Hi Joe,
>
> install went okay, (slow, but to be accepted with 512MB RAM and Ubuntu).
> Reboot did not freeze and the system rebooted fine. Uses a heck of a lot
> of swap (again to be expected). So, the major bug is now resolved. We
> can now look at ot
The 'install Ubuntu' menu item works, and I can start text screens with
ctrl+alt+F2 ... , but still, I cannot activate zram.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1227202
Title:
Will it work for us at all to test installing with zram using this
Ubuntu ISO file, or must we to get a Lubuntu ISO file?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1227202
Title:
Un
I have Ubuntu running in KVM. The live desktop is OK with a VGA screen.
But ...
1. Ubiquity starts but only in the background. There is no window. How
can I test installing?
2. There is no zram. When I try to install zram-config, apt-get
complains: Failed to fetch http://archive.ubuntu.com/ubuntu
Joseph,
I downloaded the ISO file of post #22. Please confirm or correct the
following size and md5sum!
wc -c ubuntu-13.10-desktop-amd64-lp1227202.iso
1049980928 ubuntu-13.10-desktop-amd64-lp1227202.iso
md5sum ubuntu-13.10-desktop-amd64-lp1227202.iso
e939fec65cd6d9a01689b22468f2300a ubuntu-13.1
I have tested the Lubuntu Saucy beta2 ISO files now, live, installing
and installed. It is easy to provoke a crash using the kernels (i386 and
amd64), that come with the ISO files.
I installed the kernel in post #6 into this beta2 amd64 version, and it
has *not* crashed for me. But I have had no c
The kernel in #6 has not crashed for me (and I have tested it for
several days), but if I understand correctly, it has crashed for another
tester, Lars Noodén. Please ask him directly to determine if that is
correct.
I cannot determine, which bug is causing which crash, unless guided by
you or som
Help for Lubuntu testers:
1. Test with the daily build as it is but with zRAM turned off
If you want to test how the installation and installed system works,
turn off zRAM with the following commands (as shown briefly above in
post #8). Do it *before* you start the installation, or at the beginn
Going back to the bug description:
...
WORKAROUND: Setting the Intel driver's acceleration method to UXA rather than
its default SNA *always* fixes the Flash problem, but causes a garbled login
screen under LightDM that so far has no workaround.
...
This 'UXA' workaround makes the graphics rend
I'm rather convinced it is the zRAM bug, that Leszek Lesner described
earlier today. I reported success with 768 MB RAM, and now I have
succeeded also with 512 MB RAM to install from saucy-desktop-i386.iso
without any freeze, when zRAM was switched off. This is half of the RAM
necessary to succeed
Two tests were added to
https://help.ubuntu.com/community/Lubuntu-fake-PAE
See this link for details
http://ubuntuforums.org/showthread.php?t=2113826&page=3&p=12729858#post12729858
For the first time a Pentium M CPU was found not suitable for fakePAE.
Our test results so far for Pentium M and
99 matches
Mail list logo
