@rbalint cool, almost 5 years for that answer. (a completely bogus
answer)
I can tell you've never actually tried FLASH_KERNEL_SKIP, as it doesn't
work in an early debian-install (di) environment.
See: March 15, 2013:
Public bug reported:
Please bump xf86-video-omap to head to support the upcoming
BeagleBoard-x15:
http://www.elinux.org/Beagleboard:BeagleBoard-X15
http://cgit.freedesktop.org/xorg/driver/xf86-video-
omap/commit/?id=5d3d49ba6a9744291bf345a4bf931762a8b8703e
Regards,
** Affects:
I checked in /var/log/dist-upgrades/apt.log and it was getting confused
by gnuplot, gnuplot-x11 and gnuplot-nox. I don't remember why I ever
installed gnuplot, so I uninstalled them and the upgrade can now be
calculated
--
You received this bug notification because you are a member of Ubuntu
Closing... Found a better fix for me.. I'm just installing flash-kernel
earlier and patching the all.db.
** Changed in: flash-kernel (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Wrong block device info in flash-kernel... u-boot.imx is dd'ed directly
to the drive not the partition..
** Affects: flash-kernel (Ubuntu)
Importance: Undecided
Status: New
** Tags: trusty
** Patch added: patch to fix it
** Attachment added: screenshot
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1304022/+attachment/4072968/+files/IMG_20140407_154245.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well last I checked, even mainline v3.9.x one needs to explicitly
cpufreq on the omap4460 to even boot to console prompt. Haven't
personally tried v3.10/v3.11/v3.12 as i've been busy with other projects
and that panda es just keeps running on v3.9.x. Long term, remember
that division was canned
Public bug reported:
I've just started looking at adding Ubuntu Raring to my 'netinstall'
script: https://github.com/RobertCNelson/netinstall and just run into
a fun issue with this commit:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/raring/flash-
kernel/raring/revision/447
Since
apport-cli/apport-collect doesn't work with externally supported kernels
as it doesn't find the kernel in ubuntu's repo...
*** Error: Invalid problem report
Package linux-image-3.2.16-x11 does not exist
Press any key to continue...
Regards,
--
You received this bug notification because you
Hi Yang,
Please retest with: http://rcn-
ee.homeip.net:81/testing/beagleboard/sprz319-erratum-2.1/
As this is the same patch referenced in:
http://osdir.com/ml/beagleboard/2012-02/msg01309.html
Regards,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is actually a mainline bug that affects a very small number of
Beagle xm boards (dm3730 hardware)...
[ 244.997741] usb 1-2.5: USB disconnect, device number 5
[ 1133.655883] hub 1-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
[ 1133.663085] usb 1-2: USB disconnect, device number 2
[
Looks good on my xM B:
First with Oneiric:
ubuntu@omap:~$ dmesg | grep Beagle
[0.00] Machine: OMAP3 Beagle Board
[0.083557] OMAP3 Beagle Rev: xM Ax/Bx
[4.303009] OMAP3 Beagle/Devkit8000 SoC init
ubuntu@omap:~$ uname -a
Linux omap 3.0.0-15-omap #25~xmdetectfix Thu Jan 5 12:10:40
Likewise with Precise, on my xM B:
ubuntu@omap:~$ dmesg | grep Beagle
[0.00] Machine: OMAP3 Beagle Board
[0.048156] OMAP3 Beagle Rev: xM Ax/Bx
[4.425476] OMAP3 Beagle/Devkit8000 SoC init
ubuntu@omap:~$ uname -a
Linux omap 3.2.0-7-omap #13~xmdetectfix Thu Jan 5 11:12:24 UTC 2012
I have this same laptop, this was fixed in v3.2-rc1 via:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=cf2aff6eff251b6fbdaf8c253e65ff7c693de8cd
Freedesktop bug reference:
https://bugs.freedesktop.org/show_bug.cgi?id=41569
Regards,
** Bug watch added: freedesktop.org
Guys,
I won't be able to verify this in time, as another developer has the C
board at another location.. By now, more users on irc should have the
C board..
Regards,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Ricardo,
The kernel looks good on the xM C..
ubuntu@omap:~$ lsusb
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ubuntu@omap:~$ dmesg | grep Beagle
[
u-boot notes: (with natty headless image):
Texas Instruments X-Loader 1.5.0 (Apr 11 2011 - 09:47:05)
Beagle xM
Reading boot sector
Loading u-boot.bin from mmc
U-Boot 2011.03 (Apr 20 2011 - 07:19:53)
OMAP3630/3730-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
OMAP3 Beagle board + LPDDR/NAND
Matt,
Your ID of (011) doesn't make a lot of sense, since that would be the
next logical xM C++ aka xM D revision would be.. ;)
Maybe Koen knows something we don't, when he implemented the omap3:
beagle: if rev unknown, assume xM revision C part of the xM C
changeset...
Regards,
--
You
Hi Ricardo,
Sure i'll give it a test. I have an xM B at my desk now (it actually
comes up as xM A, last i talked to Gerald, none of the xM B's are
actually xM B's as far as the gpio identification..) But the xM C
left yesterday with another developer, should have it back tomorrow..
Regards,
Hi Ricardo,
Nope, i'm not seeing any sudden freeze's or lockup's..
Panda's dmesg running gcc/testsuite before:
http://rcn-ee.homeip.net:81/dl/gcc/sys/dmesg-170061-2.6.38-rc4-d3-panda-a1-1gb.log
(lot's of kevent, stall, oom's, etc..)
After:
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, after 13 hours, my panda hasn't had a single kevent while
building gcc and running the
Hi Laurent,
I think the macaddr parameter is a ubuntu sauce only fix that isn't in
mainline.. On my panda, I take care of it thru
/etc/network/interfaces with:
# The primary network interface
allow-hotplug usb0
iface usb0 inet dhcp
hwaddress ether 62:55:bf:8d:05:28
Odd.. I don't lose that much
Hi Laurent,
For a maverick userspace, on the panda board download and run this
script:
wget http://rcn-ee.net/deb/maverick/v2.6.37-x1/install-me.sh
/bin/bash install-me.sh
The script will then download that version, install it and backup the
older ubuntu uImage and uInitrd's on the mmc card:
Hi Laurent,
It survived the -j2 pass,
http://rcn-ee.homeip.net:81/dl/gcc/SVN-168690-trunk-c-c++-panda-a1-1gb/
It's running the testsuite now, and i have it setup to try -j 3 on the
next run..
Based on my log date stamps:
-j 2 = 7 hours 27 minutes
no -j setting and nice = 13 hours 44 minutes
Hey Laurent,
Finally setup my panda to do the same thing, so far i haven't been seeing this
issue.. (I'm not using the mem=768M boot arg)
(MMC contains uImage/uInitrd rootfs on external usb sata drive)
My own kernel: (http://rcn-ee.net/deb/squeeze/v2.6.37-x0/)
voo...@panda-a1-1gb:~$ cat
Hi Laurent,
Yeah, i didn't have any '-j' parameters in those builds (also had 'nice'
enabled)...
I just updated my script to use -j2 and disabled nice so we shall
see what it does..
No, I'm not using NFS, (i really should), I'm using a locally mounted
usb sata drive (160G/7200rpm), also
Hi Ricardo,
Yeap, this patch fixes the issue i was seeing with building both 2.6.35
and 2.6.37-rc's in natty.. and no regressions on the old userspaces,
(lenny/karmic)..
I haven't seen a need for the 2nd one, AFLAGS_sleep44xx.o
:=-Wa,-march=armv7-a$(plus_sec) as i don't have the omap4 power
Hi Anand,
No luck, using 2.6.37-rc3, and manually reverting that commit (changed
smc #0 to smc)..
CC arch/arm/mach-omap2/prm44xx.o
CC arch/arm/mach-omap2/mcbsp.o
CC arch/arm/mach-omap2/omap-smp.o
AS arch/arm/mach-omap2/omap-headsmp.o
It might be the wrong rabbit hole, but there were some tweaks to 'smc'
in binutils's changelog:
http://bazaar.launchpad.net/~vcs-imports/binutils/master/revision/22100
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gas/config/tc-
arm.c.diff?r1=1.464r2=1.465cvsroot=srcf=h
--
natty gcc-4.5 kernel
Interesting Michael,
AS arch/arm/mach-omap2/omap-headsmp.o
CC arch/arm/mach-omap2/omap-hotplug.o
AS arch/arm/mach-omap2/omap44xx-smc.o
CC arch/arm/mach-omap2/omap4-common.o
AS arch/arm/mach-omap2/sram34xx.o
diff --git a/arch/arm/mach-omap2/Makefile
it'll take 4-5 hours for build and test of the image..
One big limitation with this patch, it breaks older binutils..
Assembler messages:
Error: unknown architecture `armv7-a+sec'
Error: unrecognized option -march=armv7-a+sec
make[1]: *** [arch/arm/mach-omap2/omap-headsmp.o] Error 1
make: ***
Hi Matthias,
Thank you for taking some time to look at this..
Versions:
gcc-4.5: gcc version 4.5.1 (Ubuntu/Linaro 4.5.1-9ubuntu1)
gcc-4.4: gcc version 4.4.5 (Ubuntu/Linaro 4.4.5-7ubuntu1)
as: GNU assembler version 2.20.90
So grepping the (arch/arm/Makfile) there's one occurance of 'mimplicit-
Clarity Note: the playing around with gcc-4.4 is back with the original
config mentioned in this bug.. (thumb2 kernel disabled)
--
natty gcc-4.5 kernel (2.6.37-rc1) build failure
https://bugs.launchpad.net/bugs/669912
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Binary package hint: gcc-4.5
On Natty, I'm seeing build failure of the Linux Kernel, where i wasn't
seeing them on Maverick, I can't replicate the issue with the maverick
x86 gcc-4.5 armel cross compiler in the maverick repo..
Full logs of my builds:
Hi Mario,
With the last patch:
Traceback (most recent call last):
File /usr/sbin/oem-config, line 530, in module
main(oem_config)
File /usr/sbin/oem-config, line 517, in main
install(query=options.query)
File /usr/sbin/oem-config, line 242, in install
ret = wizard.run()
File
Thanks for looking into this Mario..
Unfortunally no dice with the last patch..
Traceback (most recent call last):
File /usr/sbin/oem-config, line 530, in module
main(oem_config)
File /usr/sbin/oem-config, line 517, in main
install(query=options.query)
File /usr/sbin/oem-config,
Sure, I had stopped reporting as it would have been mostly the same
spam.. ;)
With Ubiquity 2.4.4 (oem-config) (this is the console not X11/GTK
version, which works ish..) Same issue.. Attaching recent oem-config
log...
Regards,
** Attachment added: oem-config-2.4.8.log
I did spend some time merging in alwaysinnovating's patches into
2.6.36..
http://bazaar.launchpad.net/~beagleboard-
kernel/%2Bjunk/2.6.36-devel/files/head:/patches/touchbook/
it's really not worth it till the cpufreq and voltage scaling patches
hit mainline as my touchbook does get pretty hot
Hi Matt,
Yeah, on the omap's we are pretty much stuck with booting off FAT...
I'm not sure how Canonical does their images. But with the images I
push out, I bypass the symlink problem by leaving /boot/* on the ext*
partition, and mounting the fat as /boot/uboot/*... Then let some other
Just a note...
I haven't really had a chance to test a working* oem-config/ubiquity
with an xfce based image from rootstock (just bare terminal setups)..
So I can't confirm or deny gdm may or may not be fighting with it..
*(just started testing the gtk gui version last week with 2.3.17/18/19
all
Well with ubiquity 2.4.0 it seems to work.. (Beagle xM A 512Mb running
at 800Mhz)
Other then crashing after it should be done.. but new user/settings all
exist on next reboot with gdm showing my new user name...
Rootstock command:
Ubiquity 2.3.17 (oem-config) still fails the same way...
--
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.
--
ubuntu-bugs mailing list
looks like a dup of: 588243
--
Beagle Rev A2 XM panics on shutdown -r
https://bugs.launchpad.net/bugs/632463
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
Slowly been bisecting between the releases.. (rebuilding in a native
chroot, and with testing it takes about 3-4 hours per build..)
Original Alpha-3's 2.3.3 is still first good, and 2.3.5 is current first
bad..
Rebuilding 2.3.3 and 2.3.4 should know more tomorrow..
Regards,
--
Ubiquity 2.3.13
Bisect complete, it looks like the changes from 2.3.3 (last good) to
2.3.4 (first bad) caused this regression..
somewhere in:
https://launchpad.net/ubuntu/+archive/primary/+files/ubiquity_2.3.3_2.3.4.diff.gz
Regards,
** Attachment added: oem-config.log
Ubiquity 2.3.15 (oem-config) just hit the armel repo, same problem...
** Attachment added: oem-config.log
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/628587/+attachment/1537435/+files/oem-config.log
--
Ubiquity 2.3.13 (oem-config) fails to create initial user
Hi Ricardo,
Looks good, boot tested on my new Numonyx powered Beagle xM A2
Regards,
--
x-loader misses Beagleboard xM support for boards based on Numonyx memory chips
https://bugs.launchpad.net/bugs/628243
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: ubiquity
Using rootstock (debootstrap script) i build custom images for omap3
users using a custom kernel with enhancements not yet ready for ubuntu's
omap3 kernel..
At some point between maverick alpha-3 (ubiquity (2.3.3)) and 2.3.13 the
username and
** Attachment added: oem-config.log
https://bugs.launchpad.net/bugs/628587/+attachment/1536547/+files/oem-config.log
--
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
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/628587/+attachment/1536548/+files/syslog
--
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
missing:
ubuntu user with encrypted passwd...
** Attachment added: passwd
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/628587/+attachment/1536549/+files/passwd
--
Ubiquity 2.3.13 (oem-config) fails to create initial user
https://bugs.launchpad.net/bugs/628587
You received this
Alpha-3's Ubiquity 2.3.3 (oem-config)
** Attachment added: oem-config.log
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/628587/+attachment/1536559/+files/oem-config.log
--
Ubiquity 2.3.13 (oem-config) fails to create initial user
https://bugs.launchpad.net/bugs/628587
You received
Alpha-3's syslog for comparison
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/628587/+attachment/1536560/+files/syslog
--
Ubiquity 2.3.13 (oem-config) fails to create initial user
https://bugs.launchpad.net/bugs/628587
You received this bug notification
Alpha-3's passwd, with correct user/password combo..
** Attachment added: passwd
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/628587/+attachment/1536561/+files/passwd
--
Ubiquity 2.3.13 (oem-config) fails to create initial user
https://bugs.launchpad.net/bugs/628587
You received
Just finished testing on my 2.6.35 kernel, and it fixes the bug for me..
It's also much cleaner then my own solution..
Regards,
--
kernel BUG at
/build/buildd/linux-ti-omap-2.6.33/drivers/video/omap2/dss/core.c:323!
https://bugs.launchpad.net/bugs/588243
You received this bug notification
Sure,
Mainline 2.6.35 + Mathieu's config, - revert of 6da20c89
http://rcn-ee.homeip.net:81/testing/lp-591941/2.6.35-u2.uImage
Regards,
--
SDHC card not recognized
https://bugs.launchpad.net/bugs/591941
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Guys,
xm: http://bazaar.launchpad.net/~beagleboard-
kernel/%2Bjunk/2.6.35-devel/annotate/head:/patches/xm/0001-OMAP-omap3630
-based-xm-has-no-mmc-wp-line.patch
Bx/Cx: git revert of ed8303fc111e58530e22bd29b0d7e08dced75999
From my own testing, in 2.6.35 (and 2.6.34) the pin write-protect
Success... My Bx and XM work great with
6da20c89af64b75302399369a90b9d50c1a87665 Reverted..
At first we looked at the configs, the kernel was bootable again with
disabling these
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
# CONFIG_SND_SOC is not set
So it looked like the SND_SOC was messing with the
Thanks Mathieu for the updated config.
I've been config hunting since yesterday, my baseline ubuntu.config was
just a little off: http://pastebin.com/dg4wiEZM
So far nothing obvious is causing it...
--
SDHC card not recognized
https://bugs.launchpad.net/bugs/591941
You received this bug
Loosing my mind, so let's reset some things.. ;)
Mathieu, did you happen to boot the uImage posted in Message #9 on a XM?
I get this on my XM:
mmc1 is available
reading uImage
3606988 bytes read
## Booting kernel from Legacy Image at 8030 ...
Image Name: Linux-2.6.35-rc6
Image
Okay, finally replicated the -110 error on 2.6.35 with my XM
Minimal 2.6.35 tree, using Mathieu's config, on my XM:
https://code.launchpad.net/~beagleboard-kernel/+junk/2.6.35-XM
uImage: http://rcn-ee.homeip.net:81/testing/lp-591941/
PS. i was under the impression this -110 error was only a XM
Hi Lee,
No dice..
I modified my config with:
-# CONFIG_CPU_IDLE is not set
+CONFIG_CPU_IDLE=y
+CONFIG_CPU_IDLE_GOV_LADDER=y
+CONFIG_CPU_IDLE_GOV_MENU=y
It finds the mmc card just fine, mounts card, login, etc...
Boot Log: http://pastebin.com/4vXH1yx4
Regards,
--
SDHC card not recognized
Hi Lee,
Sorry i didn't get back on irc like i thought, some fun meetings..
Just confirmed with the image I downloaded this morning on my XM p7
256Mb beagle...
2.2G 2010-08-01 21:16 maverick-preinstalled-netbook-armel+omap.img
Same issue with my 4GB Sandisk..
dmesg log: (enabled serial port on
Hi Mathieu,
It might be CONFIG_CPU_IDLE, as all the rest i have enabled in my
config..
I have always disabled that in the past due to the serial port becoming
corrupt... (well only tested 2.6.26 thru 2.6.34 on the beagle with it
enabled..)
cat patches/lucid-defconfig | grep CONFIG_CPU_FREQ=
Yeah, my XM Rev A (256Mb) has the same issue. Although i haven't looked
at it closely in awhile, is there any kind of Write Protect level on
the mini-sd card holder? I don't think there is, well the kernel still
thinks there is, we will have to add another check here for the XM, to
ignore the
** Patch added: xm-ignore-gpio_wp.diff
http://launchpadlibrarian.net/52536213/xm-ignore-gpio_wp.diff
--
2.6.35-devel is unable to mount root on mmc
https://bugs.launchpad.net/bugs/607906
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Actually are you sure? on my xm with 2.6.35-rc6-dl11
It's coming up as:
ubu...@beagleboard:~$ mount | grep -v none | grep -v proc
/dev/mmcblk0p2 on / type ext4 (rw,errors=remount-ro)
/dev/mmcblk0p1 on /boot/uboot type vfat (rw)
--
2.6.35-devel is unable to mount root on mmc
Hi Till,
Found the change that broke this:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=ed8303fc111e58530e22bd29b0d7e08dced75999
Reverted the change and it now correctly mounts the partitions..
ubu...@beagleboard:~$ mount | grep -v none | grep -v proc
: (unassigned) = Robert Nelson (robertcnelson)
--
2.6.35-devel is unable to mount root on mmc
https://bugs.launchpad.net/bugs/607906
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
https
Hi Till,
Thanks for the serial log, that's a strange one. What userspace lucid,
maverick, other are you using? (i'm going to build a similar image)
In my own gcc testing, my beagle auto tests every newer rc kernel,
here's that one in squeeze userspace for comparison:
Hi Till,
I'm going to start a full bisect from 2.6.34... While testing this
tonight i got:
ubu...@beagleboard:~$ mount | grep -v none | grep -v proc
/dev/mmcblk0p2 on / type ext4 (rw,errors=remount-ro)
/dev/mmcblk0p1 on /boot/uboot type vfat (ro)
the root file system comes up right, but my
Okay, one step closer..
The regression occurs between snapshots in the merge 2.6.34-git6 (good)
and 2.6.34-git7 (first bad).. (limitations of my current script..)
There's a big mmc merge in their for omap, so there's a lot that can be
removed from the 11Mb difference between git6/7..
This
Hi Tim,
Do you know what revision of the 2.6.35-devel you used?
It'll print it out at bootup, something like;
[0.00] Linux version 2.6.35-rc5-d6 (r...@debian-sheevaplug) (gcc
version 4.4.4 (Debian 4.4.4-6) ) #1 PREEMPT Thu Jul 15 21:41:21 UTC 2010
Regards,
--
2.6.35-devel is unable
Hi Tim,
Just adding some more questions...
Can you provide a full boot log from the serial console. (from X-loader
load to crash)
Thanks,
--
2.6.35-devel is unable to mount root on mmc
https://bugs.launchpad.net/bugs/607906
You received this bug notification because you are a member of Ubuntu
#STABLE_PATCH=.1
#PRE_RC=2.6.34-git16
RC_KERNEL=2.6.35
RC_PATCH=-rc5
ABI=8
Note, take a look at the ABI value i try to make sure the tree is
always buildable, but if it late and i'm heading home the ABI will be
a non constant value, if it's not tested..
Regards,
--
Robert Nelson
http://www.rcn-ee.com
Bryan,
Talked to upstream about this a month ago:
http://www.spinics.net/lists/linux-omap/msg30138.html
Till there's a significant rewrite i'm using this quick workaround that
hides the problem, buy un-suspending the display before reboot..
http://bazaar.launchpad.net/~beagleboard-
Off hand, i don't remember if this is a limitation of the Omap3, but the
blue terminal background has always existed with dss2 since the
2.6.28ish days for me. (Most people run 16bit mode for faster drawing,
it takes more bandwidth for 32bit mode)
Give 24 bit mode a try:
The attached quick patch seems to work me on my beagles, using on my
2.6.34 + dss2-for next builds...
I just sent it to the linux-omap mailing list for review...
** Patch added: reboot-fix.diff
http://launchpadlibrarian.net/49031560/reboot-fix.diff
--
DSS2 oops when shutting down while
latest can be found here (for the 2.6.32-psp kernel):
http://git.alwaysinnovating.com/cgit.cgi/ai.openembedded.dev/tree/recipes/linux
/linux-omap-psp-2.6.32
--
omap3 dss2 touchbook patch missing in lucid kernel
https://bugs.launchpad.net/bugs/581771
You received this bug notification because you
I want it packaged too... desperately.
--
[needs-packaging] Emusic Download Manager
https://bugs.launchpad.net/bugs/370676
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
For comparison sake, I gave qemu access to a 2nd hardrive in my system
-hda /dev/sda1 same result as with using disk images..
Selecting previously deselected package libgnomekbd-common.
Unpacking libgnomekbd-common (from
.../libgnomekbd-common_2.30.0-0ubuntu2_all.deb) ...
Selecting previously
For comparison sake, I gave qemu access to a 2nd hardrive in my system
-hda /dev/sda1 same result as with using disk images..
Selecting previously deselected package libgnomekbd-common.
Unpacking libgnomekbd-common (from
.../libgnomekbd-common_2.30.0-0ubuntu2_all.deb) ...
Selecting previously
Just adding some OMAP Board Details.
Development Boards:
Original Bx/C2 Beagles have no prevision for installing a backup battery.
C3 C4(current shipping) Beagles have an area reserved for end users to
solder a 3V coin battery. I believe the XM will have the same
provision, i just don't have
Hi Guys,
My Bx board been kinda of a pain lately so i haven't nailed down this
config issue yet. I have some time so i'm going to give it another
round tonight..
For the moment, this config change gives a working ehci port on Cx
boards on startup. (compare builds with lsusb making sure both
Attaching dmesg and lsusb dumps..
dmesg-500.4.log
500.4 as is in ubuntu's repo (couple igepv2 patches pulled from 2.6.34-rc3 and
nand options)
No usb devices on boot, must force:
sudo insmod /lib/modules/2.6.33-500-omap/kernel/drivers/usb/gadget/g_ether.ko
dmesg-500.4-configpatch-541030.log
dmesg-500.4-configpatch-541030.log
** Attachment added: dmesg-500.4-configpatch-541030.log
http://launchpadlibrarian.net/43206710/dmesg-500.4-configpatch-541030.log
--
omap kernel musb/ehci ports not enabled on beagleboard
https://bugs.launchpad.net/bugs/541030
You received this bug
dmesg-500.4-configpatch-541030-revert-b586f759.log
** Attachment added: dmesg-500.4-configpatch-541030-revert-b586f759.log
http://launchpadlibrarian.net/43206746/dmesg-500.4-configpatch-541030-revert-b586f759.log
--
omap kernel musb/ehci ports not enabled on beagleboard
More testing with b586f759f4dda7622a90f68c9c05424e777b8b2b reverted then
reintroduced in small chunks...
Reference: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
lucid.git;a=commit;h=b586f759f4dda7622a90f68c9c05424e777b8b2b
This is safe: 01-CONFIG-safe-musb.diff musb works fine..
These config
** Patch added: 02-CONFIG-Breaks-musb.diff
http://launchpadlibrarian.net/43212418/02-CONFIG-Breaks-musb.diff
--
omap kernel musb/ehci ports not enabled on beagleboard
https://bugs.launchpad.net/bugs/541030
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Note: i also add to revert b586f759f4dda7622a90f68c9c05424e777b8b2b to
get this working again for 500.4 I'm currently testing these individual
config differences in that patch to find the breakage.
For comparison in my 2.6-dev 2.6.33.1 tree:
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set (different)
** Description changed:
- The currently kernel configuration does not setup the ehci/musb port on
- the beagleboard due to some misconfiguration.
+ The currently kernel configuration does not correctly setup the
+ ehci/musb ports on the beagleboards..
+
+ These specific kernel config options
Public bug reported:
The currently kernel configuration does not setup the ehci/musb port on
the beagleboard due to some misconfiguration.
** Affects: linux-ti-omap (Ubuntu)
Importance: Undecided
Status: New
--
omap kernel musb/ehci ports not enabled on beagleboard
** Patch added: 0001-UBUNTU-Config-Enable-musb-ehci-on-beagleboard.patch
http://launchpadlibrarian.net/41232261/0001-UBUNTU-Config-Enable-musb-ehci-on-beagleboard.patch
--
omap kernel musb/ehci ports not enabled on beagleboard
https://bugs.launchpad.net/bugs/541030
You received this bug
Public bug reported:
Binary package hint: ubiquity
To ease new users to setup their own rootfs on armel hardware. A new
option in project-rootstock for lucid is to run oem-config in the rootfs
on first boot.
A typical user would:
1: Run rootstock on a x86 machine to setup an ubuntu armel
** Attachment added: oem-config debug
http://launchpadlibrarian.net/39827974/oem-config.log
** Tags added: armv7
--
ubiquity fails after /bin/hw-detect, on armel hardware, on first boot
https://bugs.launchpad.net/bugs/528605
You received this bug notification because you are a member of
This bug is safe to close...
After a day of testing on multiple boards i haven't been able to get
lucid to fail... Sounds like a good time for me to generate a demo
alpha-2 rootfs and dump it on the beagleboard community.. ;)
--
fakeroot Illegal instruction in lucid armv7 on the beagleboard
Thanks Dave for all your help!
So far enabling the errata workarounds seems to be the secret, I built 4
combinations with those defconfig changes...
I'm going to run a few more tests on the other beagles in my farm, but
those 3 errata workarounds seem to have fixed it...
Sorry for the noise, once the ARM_ERRATA_430973 errata option is enabled
in the .config (lp bug 495536) this problem also goes away. Safe to
Close...
--
Segmentation fault with running apt-get ../ports/sysdeps/arm/memcpy.S:137
https://bugs.launchpad.net/bugs/511032
You received this bug
Thanks Dave... Still a mystery.. cachepolicy=uncache really makes the it
slow on the omap3530...
[27564.130035] Alignment trap: not handling instruction 2b2f at [a630]
[27564.142974] Unhandled fault: alignment exception (0x801) at 0xbeb7237d
(gdb) x/12x 0xa618
0xa618: 0xb1336823
Humm, a possible result, but I'm not sure if it's valid, so I'm
attaching the patch i used to output the PID in do_DataAbort()... It's
similar to something that was posted but never merged into the sh
fault.c After running it a couple of times i really should have
printed the task name...
1 - 100 of 159 matches
Mail list logo
