On Mon, Mar 7, 2011 at 11:27 AM, warmcat 708...@bugs.launchpad.net wrote:
Since Sebasien Jan took my patch into his tree, and the Ubuntu Panda
kernel is coming via his tree, it should mean that kernel has the patch
in it. You can confirm it with
$ dmesg | grep 6030: Interrupt status
if it
** Changed in: ubuntu
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/607752
Title:
[needs-packaging] devmem2 needs packaging
--
ubuntu-bugs mailing list
/GtkLauncher and also by
installing with the pre-installed image (after also installing the
slideshow).
** Changed in: webkit (Ubuntu)
Status: New = In Progress
** Changed in: webkit (Ubuntu)
Assignee: (unassigned) = Ricardo Salveti (rsalveti)
--
You received this bug notification
Built packages, in case someone wants to test it:
http://people.canonical.com/~rsalveti/728211/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/728211
Title:
webkit crashes with SIGSEGV on ARM
--
Please try reproducing this issue with latest kernel update, based on
rc4 (2.6.38-3.30).
Also these traces happen probably because the smsc95xx driver is eating
a lot of kernel memory, probably more than it should.
Do you have any other device or usb disk connected at your usb ports?
--
You
On Mon, Feb 14, 2011 at 9:36 AM, Robert Nelson robertcnel...@gmail.com wrote:
Hi Laurent,
On the beagleboard list, we found a hack/workaround for the smsc95xx
kevent spam in dmesg, that seems to lock up the ethernet interface:
Add to /etc/sysctl.conf:
vm.min_free_kbytes = 8192
So far,
Tobin, can you try reproducing this issue with our latest image
available? Thanks in advance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/702999
Title:
oprofile failure on armel
--
ubuntu-bugs
= Confirmed
** Changed in: qt4-x11 (Ubuntu)
Assignee: Ricardo Salveti (rsalveti) = (unassigned)
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in ubuntu.
https://bugs.launchpad.net/bugs/707794
Title:
libqt4-opengl on armel
Public bug reported:
root@panda-alpha2:~# apt-cache show linux-image-linaro-omap
Package: linux-image-linaro-omap
Priority: optional
Section: universe/metapackages
Installed-Size: 32
Maintainer: Ubuntu Kernel Team kernel-t...@lists.ubuntu.com
Architecture: armel
Source: linux-meta-linaro
Version:
This kernel works fine for me when installing it at the Ubuntu Natty
Alpha-2 release. Was able to boot and use the board without any hang.
Seems I'm using a newer u-boot, so it would be good to test to make sure
it's not related with it.
Texas Instruments X-Loader 1.4.4ss (Jan 26 2011 -
** Attachment added: Full dmesg.
https://bugs.launchpad.net/ubuntu/+source/linux-linaro/+bug/708883/+attachment/1835889/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/708883
This needs to be addressed with the new development targeting kernel
2.6.38, as TI will rewrite the whole driver again. Don't think it's
worthy to fix the current driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What I still don't understand is why Paul Larson was able to reproduce
this issue without ever touching the USB OTG and using just the external
power supply?
The x-loader that Paul is using is already based on this upstream one,
and it's the same one we're using at the Ubuntu images.
Paul, are
** Tags added: armel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/724615
Title:
unity FTBFS on armel
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/725567
Title:
chromium-browser dies when trying to run a webgl application with GLES
on ARM
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: chromium-browser
With a Pandaboard, running with the PVR SGX drivers installed from ti-
omap/omap-trunk PPA, chromium browser dies when trying to run a webgl
application.
To use the GLES support you need to start up chromium giving the --use-
gl=egl,
The only messages you get from chromium is about the lack of PCI
support:
+ exec /usr/lib/chromium-browser/chromium-browser --use-gl=egl
pcilib: Cannot open /proc/bus/pci
pcilib: Cannot find any working access method.
pcilib: Cannot open /proc/bus/pci
pcilib: Cannot find any working access
You can go ahead and remove the Versatile support, Qemu from qemu-linaro
is emulating both Beagle and Beagle XM quite well, and enough for users
trying to emulate an ARM machine with Ubuntu.
Linaro is already using the Omap emulation at their tools, and for the
moment even if we still want to
** Changed in: powervr-omap3 (Ubuntu)
Status: New = In Progress
** Changed in: powervr-omap3 (Ubuntu)
Assignee: (unassigned) = Ricardo Salveti (rsalveti)
** Tags added: armel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
After talking with Peter Maydell, it seems that we'll probably need to
support vexpress for next cycle (versatile but better), as he's afraid
Beagle support will now basically be maintained, but not improved with
new features.
So we may end up needing a new versatile support for next cycle, even
On Mon, Feb 28, 2011 at 11:01 AM, Jani Monoses j...@ubuntu.com wrote:
If beagle will still work for 11.10 it can be the 'versatile' of that
cycle, i.e. a valid qemu target to test our images on even if not our
most used target.
Yeah, but I believe vexpress would probably be the best one for
-sgx (Most GL-ES2 GPUs with shader compiler)
--enable-gles-variety-s3c6410 (s3c6410 with offline shader compiler)
You will also need to enable the OpenGL engine for X11 with:
--enable-gl-x11]
** Affects: evas (Ubuntu)
Importance: Undecided
Assignee: Ricardo
** Changed in: evas (Ubuntu)
Status: New = In Progress
** Changed in: evas (Ubuntu)
Assignee: (unassigned) = Ricardo Salveti (rsalveti)
** Patch added: Debdiff activating --enable-gles-variety-sgx.
https://bugs.launchpad.net/ubuntu/+source/evas/+bug/727591/+attachment/1880120
From Main, we have the following problems:
1 - avogadro: uses OpenGL and libqt4-opengl, and as a result it'll have symbols
collision and the build will fail (no easy solution);
2 - kdeedu: need to remove Kalzium, as it uses avogadro and libqt4-opengl;
3 - kdegames: need to remove OpenGL support,
it for this
cycle.
What do you think?
** Changed in: qt4-x11 (Ubuntu)
Status: New = In Progress
** Changed in: qt4-x11 (Ubuntu)
Assignee: (unassigned) = Ricardo Salveti (rsalveti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
On Wed, Feb 2, 2011 at 2:08 PM, Jonathan Thomas echidna...@kubuntu.org wrote:
I don't think removing Kalzium and Kubrick would be an option.
Kalzium can still be enabled, but without the molecular editor.
Kubrick is disabled automatically once you remove OpenGL support.
If you plan to have just
I already published the backported patch, but the problem is that the
patch is huge, and as the release will be out in a few days, besides
being an LTS one, I don't think the patch will be incorporated.
The good thing is that at the time they decide to update the kernel to
2.6.33 this fix will be
@Claudius: I was able to build it following the same steps you can find
at comment #48.
After installing the module, just load it with sudo modprobe
rt2870sta.
After loading the driver you'll probably be able to access your wireless
interface.
--
[lucid] rt2860 frequently fails to connect to
@Claudius: after installing the module, you can check if it was loaded
successfully by checking the lsmod output.
Also, dmesg should say something when loading the driver.
After loading it, try giving ifconfig -a, see if you can see your
wireless interface there.
--
[lucid] rt2860 frequently
@Laurent: can you also post your device id?
You can easily get the device ID by running lspci -nn -vv. Please
attach the output at the bug so we can match which device you're
currently using.
--
[lucid] rt2860 frequently fails to connect to mixed mode WPA/WPA2 secured
wireless networks
Attached you can find the backported patch regarding the update of this
driver.
At mainline we have many other patches, but most are cosmetic changes,
to follow the kernel coding style.
This patch got into 2.6.33, and the original hash is
ca97b8388838ee9ea4b4bad04948f8f7f8a607a3 .
The only
They should first work to get the driver upstream, and this has nothing
to do with Ubuntu itself.
What I saw is that there is a community effort to improve the quality of
the driver, to then be able to push it at Linus' tree. At the moment
this driver is located at the staging, and it's older
@HaroldAling: can you paste the result of $ lspci -vnn | grep RaLink?
In my EeePC 1000HE I get:
01:00.0 Network controller [0280]: RaLink RT2860 [1814:0781]
--
[lucid] rt2860 frequently fails to connect to mixed mode WPA/WPA2 secured
wireless networks
https://bugs.launchpad.net/bugs/496093
You
This doesn't seems to be fixed at the current kernel repository, so this
should probably work just for some time.
Let us know if this is stable for you, and also your device id.
--
[lucid] rt2860 frequently fails to connect to mixed mode WPA/WPA2 secured
wireless networks
@jh: the problem is that this driver is still alpha/beta software, even
upstream.
The upstream is basing the driver from the vendor's 2.1 version, but the
vendor already released the 2.3 one.
Neither one is stable or in a state that can be merged upstream, so
issues like these ones are, somehow,
@nicleuskore: if doesn't work, please post the output of $ lspci -vnn |
grep RaLink here.
--
[lucid] rt2860 frequently fails to connect to mixed mode WPA/WPA2 secured
wireless networks
https://bugs.launchpad.net/bugs/496093
You received this bug notification because you are a member of Ubuntu
@John D.: the patch was submitted already, but the kernel team is
responsible for reviewing and applying it, if they decide that this is
the way to go.
Probably the review will happen in the next weeks.
--
[lucid] rt2860 frequently fails to connect to mixed mode WPA/WPA2 secured
wireless
Public bug reported:
Binary package hint: compiz
If you use the window menu to send a not fullscreen window to a
different workspace, the window will be located in a different position
(x and y).
Reproduce:
1. Using default compiz Normal settings.
2. Using Gnome 2.30 with Ubuntu Lucid Beta 2
3.
This problem doesn't happen when I remove the visual effects (using
metacity).
--
Move to another workspace doesn't keep the window original position.
https://bugs.launchpad.net/bugs/561177
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's the link of the upstream bug:
https://bugzilla.kernel.org/show_bug.cgi?id=15749
At comment #7 you can check the proposed fix, but it's still outside
Linus' tree.
** Bug watch added: Linux Kernel Bug Tracker #15749
http://bugzilla.kernel.org/show_bug.cgi?id=15749
--
2.6.32.30
Bryan, as this bug also affects the Maverick's kernel, can you create
another kernel package based on the Maverick one?
--
Usb host mode on OTG doesn't work on Maverick with BeagleBoard
https://bugs.launchpad.net/bugs/608312
You received this bug notification because you are a member of Ubuntu
Tobin, can you please test this issue when Bryan releases a new kernel
for Maverick?
Thanks in advance.
--
Usb host mode on OTG doesn't work on Maverick with BeagleBoard
https://bugs.launchpad.net/bugs/608312
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Tobin, can you please test this kernel and see if this bug is actually
gone? Also make sure that the OTG works as expected.
Thanks in advance.
--
OTG configuration is broken on omap kernel
https://bugs.launchpad.net/bugs/566645
You received this bug notification because you are a member of
Tested with Maverick's vmlinuz-2.6.35-10-versatile and I'm still able to
reproduce the problem (qemu cdcf9153e5e17dde340135fee5dcc7c299f2d4f5
this time).
--
qemu-system-arm segfaults emulating versatile machine after running debootstrap
--second-stage inside vm
Public bug reported:
Binary package hint: mono
While trying to install mono packages inside a qemu-arm-static chroot on
a x86_64, with proc filesystem mounted inside the chroot, mono hangs and
block the installation.
You can also reproduce it easily by calling mono directly, like:
# mount -t
While looking into the strace, it seems that mono requests a lot of
information from /proc and then tries to use this information to run
mmap/mprotect. Also note that it's getting lots of SIGSEGV.
** Attachment added: qemu-strace.txt
http://launchpadlibrarian.net/52619914/qemu-strace.txt
--
Public bug reported:
Binary package hint: qemu-kvm
At lucid the pselect patch was added to qemu, in a way to remove the
annoying qemu: Unsupported syscall: 335 messages that you get when
running apt-get with qemu arm user emulation, but now this message is
back in Maverick.
Original bug for
The thread explaining why the pselect patch was dropped:
http://www.mail-archive.com/qemu-de...@nongnu.org/msg28238.html
--
qemu shows qemu: Unsupported syscall: 335 for pselect in Maverick
https://bugs.launchpad.net/bugs/610742
You received this bug notification because you are a member of
Here you can find the qemu image I'm using to reproduce this bug:
http://people.canonical.com/~rsalveti/610719/
--
Mono hangs while running with qemu ARM user emulation (chroot)
https://bugs.launchpad.net/bugs/610719
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm now implementing the support for creating a rootstock rootfs without
requiring root, and I also got stuck at a segmentation fault, just after
executing the debootstrap' second stage.
I'm running the qemu-system-arm from qemu-kvm-extras 0.12.4+noroms-
0ubuntu4, at maverick.
My qemu command
Public bug reported:
Binary package hint: qemu-kvm
As I'm now implementing the support for creating a rootstock rootfs
without requiring root, I need to run the deboostrap' second stage
inside a VM, to correctly install the packages into the rootfs.
qemu-system-arm fails right after debootstrap
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/51803593/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/51803594/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/51803595/Dependencies.txt
**
Maverick:
I: Base system installed successfully.
I: Starting basic services in VM
Program received signal SIGSEGV, Segmentation fault.
0xceeef54c in ?? ()
(gdb) bt full
#0 0xceeef54c in ?? ()
No symbol table info available.
#1 0x7fffdfa0 in ?? ()
No symbol table info
I'm also able to reproduce with upstream Qemu, hash
aa5fb7b3bf388d643bd9c6e6fee9ace5db2e590f
I: Base system installed successfully.
I: Starting basic services in VM
Program received signal SIGSEGV, Segmentation fault.
0x8be2208b in ?? ()
(gdb) bt full
#0 0x8be2208b in ?? ()
No
If you're at Lucid or Maverick, you can also create the rootfs img by
running the attached rootstock script.
Please install all rootstock dependencies by installing the official version
provided by the distro:
sudo apt-get install rootstock
Using the attached script:
sudo bash ./rootstock
For the seg fault bug I've created the bug 604872.
Meanwhile I'll try to reproduce the hang problem with Maverick and
upstream Qemu.
--
apt/dpkg in qemu-system-arm hangs if a big task is installed
https://bugs.launchpad.net/bugs/532733
You received this bug notification because you are a member
** Changed in: project-rootstock
Status: New = Confirmed
** Changed in: project-rootstock
Assignee: (unassigned) = Ricardo Salveti (rsalveti)
--
rootstock: bashism introduced in bzr revision 94
https://bugs.launchpad.net/bugs/575854
You received this bug notification because you
** Changed in: project-rootstock
Status: Confirmed = In Progress
--
rootstock: bashism introduced in bzr revision 94
https://bugs.launchpad.net/bugs/575854
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Fixed on revision 104.
** Changed in: project-rootstock
Status: In Progress = Fix Committed
** Changed in: project-rootstock
Importance: Undecided = High
--
rootstock: bashism introduced in bzr revision 94
https://bugs.launchpad.net/bugs/575854
You received this bug notification
This is actually expected on the current genext2fs implementation.
Currently it's declaring and filling only the required fields for
revision 0.
For revision 1 filesystems we also have volume name, UUID and some other
extra fields. This is listed to be implemented in the TODO file from
genext2fs
Marking this as Invalid as this is the default behavior of the software.
Please reopen it if you don't agree with the solution.
** Changed in: genext2fs (Ubuntu)
Status: Confirmed = Invalid
** Changed in: genext2fs (Ubuntu)
Assignee: (unassigned) = Ricardo Salveti (rsalveti
I'm also getting a similar error when configuring qemu upstream (hash
08218b3527301760393b0b4ec732fcdfb7ff6cda).
Seems to run fine, but apport gets the segfault at ld.bfd:
[70428.554802] ld[28939]: segfault at 0 ip 7fea8d784692 sp
7fff2a067be8 error 4 in libc-2.12.so[7fea8d6fe000+17a000]
After some tests I was able to reproduce the issue on Maverick and with
upstream Qemu (08218b3527301760393b0b4ec732fcdfb7ff6cda).
Also tried stressing the disk with fsstress and dd for many hours, but
couldn't reproduce the issue. The easier way to reproduce it is with
dpkg, but hard to find the
Here is where it's getting stuck now:
Selecting previously deselected package libimobiledevice0.
Unpacking libimobiledevice0 (from
.../libimobiledevice0_0.9.7-1ubuntu1_armel.deb) ...
Selecting previously deselected package libtalloc2.
Unpacking libtalloc2 (from
I also got this issue with Lucid 2.6.33-502-omap, but this is not
something that you can reproduce on every boot, as some times it does
works correctly.
Still going to try with latest Maverick and upstream kernel to see if
it's already fixed.
--
OTG configuration is broken on omap kernel
For Maverick's kernel the OTG doesn't even work as Lucid's kernel.
Before plugging in the cable:
r...@ubuntu-desktop:~# cat /sys/devices/platform/musb_hdrc/mode
b_idle
After plugging the cable:
r...@ubuntu-desktop:~# cat /sys/devices/platform/musb_hdrc/mode
a_idle
echo host
With Maverick it does work if I compile the kernel with the following config
file:
*
http://bazaar.launchpad.net/~beagleboard-kernel/+junk/2.6.35-devel/annotate/head:/patches/defconfig
It's quite different from Maverick's one, so still need to compare most
of the changes related with usb and
Public bug reported:
When booting Maverick on a C4 BeagleBoard the host mode on USB OTG
doesn't work as it should.
In theory it should just work when I add a micro usb cable (otg
compatible) connected to a powered hub.
Checking the device status:
Before plugging the cable:
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/52269085/AlsaDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/52269086/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/52269088/CurrentDmesg.txt
**
It's probably a config issue, cause when compiling and using the same
kernel with config file from http://bazaar.launchpad.net/~beagleboard-
kernel/+junk/2.6.35-devel/annotate/head:/patches/defconfig it does work
as expected.
--
Usb host mode on OTG doesn't work on Maverick with BeagleBoard
For Maverick I opened bug 608312, because the basic functionality is not
working yet.
--
OTG configuration is broken on omap kernel
https://bugs.launchpad.net/bugs/566645
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This patch is just a simple fix the issue by verifying the return string
of the command lspci.
The proper fix would probably involve checking correctly the output from
command_output, but then depends on how do you want to display the error
when it happens.
** Patch added:
Argh, for some reason the OTG just get initialized when you load the
g_ether driver.
Just activated the debug and here's what I got:
Initializing MUSB:
[ 16.670837] musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
[ 16.767852] musb_hdrc: ConfigData=0xde (UTMI-8,
Tested at my EeePC 1000 HE and it seems to be working fine.
My card:
$ lspci -vnn | grep RaLink
01:00.0 Network controller [0280]: RaLink RT2860 [1814:0781]
Subsystem: RaLink Device [1814:2790]
--
[lucid] rt2860 frequently fails to connect to mixed mode WPA/WPA2 secured
wireless
** Tags added: maverick
--
bluetooth-applet crashed with SIGSEGV
https://bugs.launchpad.net/bugs/551831
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This issue happens more than 10 times a day at my Maverick installation.
--
telepathy-butterfly crashed with NotImplementedError in __init__()
https://bugs.launchpad.net/bugs/609894
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: project-rootstock
Milestone: None = 0.1.99.4
** Changed in: project-rootstock
Status: Fix Committed = Fix Released
--
rootstock: bashism introduced in bzr revision 94
https://bugs.launchpad.net/bugs/575854
You received this bug notification because you are a member of
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/52749896/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/52749897/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/52749898/Disassembly.txt
** Attachment
A better stacktrace:
#0 cairo_rectangle (cr=0x0, x=58, y=0, width=50, height=43) at
/build/buildd/cairo-1.9.12/src/cairo.c:2088
#1 0x7fe3c3be7313 in play_button_toggle_play_pause (button=0x870900,
update=value optimized out) at play-button.c:470
#2 0x7fe3d6b6f69e in g_closure_invoke
A better stacktrace:
#0 cairo_rectangle (cr=0x0, x=58, y=0, width=50, height=43) at
/build/buildd/cairo-1.9.12/src/cairo.c:2088
#1 0x7fe3c3be7313 in play_button_toggle_play_pause (button=0x870900,
update=value optimized out) at play-button.c:470
#2 0x7fe3d6b6f69e in g_closure_invoke
This bug only happens with the indicator-sound-0.3.9 release, with
indicator-sound-0.3.8 it works fine.
The crash is happening in this piece of code, added at the newer
version:
play_button_toggle_play_pause(GtkWidget* button, PlayButtonState update)
{
PlayButtonPrivate* priv =
** Also affects: indicator-sound
Importance: Undecided
Status: New
--
[maverick] indicator-applet crashed when rhythmbox changes track
https://bugs.launchpad.net/bugs/611755
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Just installs StartCraft 2 and try to run it on a ATI device with the
open source Radeon driver.
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-13-generic 2.6.35-13.18
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu
** Attachment added: AcpiTables.txt
http://launchpadlibrarian.net/52951746/AcpiTables.txt
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/52951747/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/52951748/AplayDevices.txt
**
I'm still getting lots of OOM errors while booting latest Maverick
image.
I just created a basic image with rootstock, using linux-
image-2.6.35-14-omap, and I'm still getting the OOM errors.
Please check the attached file for the dmesg.
Packages:
* linux-image-2.6.35-14-omap 2.6.35-14.19
*
Just running ureadahead at the console is enough to get the OOM:
r...@beagle-maverick:~# free
total used free sharedbuffers cached
Mem:108912 17392 91520 0 56 2464
-/+ buffers/cache: 14872 94040
Swap:
Sorry, beagle B5 (will test on a C4 beagle tomorrow).
--
ureadahead generating oom messages during boot.
https://bugs.launchpad.net/bugs/600359
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
For reference, I believe we're using u-boot from
http://gitorious.org/pandaboard/u-boot.
There are quite many others u-boot trees around (omapzoom, sakoman) so
we should probably try to use one of these trees for the future.
--
u-boot fails to load new kernel fromm boot partition after kernel
@Chase Douglas: tested your package, with the backported driver from
2.6.34 and it seems to be working fine. This fix is included in upstream
since 2.6.33, that's the version with the updated driver.
My hardware is an EeePC 1000HE, with following description and code:
01:00.0 Network controller
I also noticed this bug when I installed the latest Lucid in my eeepc
1000he.
Checking linux mainline, I saw that they updated the driver with almost
40 patches, but the main important one was the update from vendor's
V2.1.0.0 driver, that could possible fix this issue.
Tested with 2.6.34-rc3
@Claudius: does it work when you use the latest driver provided by the
vendor?
Currently the latest version available to download is v2.3.0.0
(RT2870USB(RT2870/RT2770)). The release notes doesn't say anything
specific to this bug, but it'd be nice to know if it's fixed so we can
work on updating
@lispy: can you post your device id?
You can easily get the device ID by running lspci -nn -vv. Please
attach the output at the bug so we can match which device you're
currently using.
--
[lucid] rt2860 frequently fails to connect to mixed mode WPA/WPA2 secured
wireless networks
Yes, this bug is fixed with latest version of the driver. The driver's
code that you can find at 2.6.33 is enough to get it working, and that's
why I'm using the backported patch.
As I think this is not going to be merged into Lucid (huge patch), the
easier solution is to install the latest
@Joseph: what's your hardware id?
--
[lucid] rt2860 frequently fails to connect to mixed mode WPA/WPA2 secured
wireless networks
https://bugs.launchpad.net/bugs/496093
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
@Chase Douglas: I also believe that bringing the newer version from
2.6.34 into linux-backports-modules-wireless is the best option. We saw
from this bug that none of the solutions actually fixed most of the bugs
reported, so it's hard to select the best option.
Even the upstream code is in a
I'm also maintaining the kernel with the backported patch at
http://rsalveti.net/pub/ubuntu/kernel/lucid for those who want to test
it, but it's easier to just install the vendor's driver.
--
[lucid] rt2860 frequently fails to connect to mixed mode WPA/WPA2 secured
wireless networks
The proper patch to apply on top of the stable one that caused this bug
just got mainline, and the hash is
2060c44576c79086ff24718878d7edaa7384a985.
--
2.6.32.30 reproducible oops at startup in acpi_ex_read_data_from_field
https://bugs.launchpad.net/bugs/561151
You received this bug notification
Can you test with the released maverick repo and report back if this is
still an issue?
--
Ubiquity 2.3.13 (oem-config) fails to create initial user
https://bugs.launchpad.net/bugs/628587
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu Maverick)
Status: New = Fix Committed
** Changed in: linux (Ubuntu Maverick)
Assignee: (unassigned) = Ricardo Salveti (rsalveti)
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Committed
--
omapdss: VDDA_DAC regulator on IGEPv2
https
This patch got applied at Linux 2.6.36-rc6.
At Maverick we currently don't need it as we're using it as built in
(CONFIG_SMSC911X=y).
--
smsc911x has no module alias, does not get auto-loaded on OMAP3 EVM
https://bugs.launchpad.net/bugs/646368
You received this bug notification because you are
801 - 900 of 2173 matches
Mail list logo
