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
https://bugs.launchpa
** Tags added: patch
--
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://lists.ubuntu.com
** 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 Ubunt
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 g
I now have a beagleboard xm for testing and the same issue is back
again. Mounting rw fails with the card not being mounted although it's
being listed as being present. Mounting ro causes the entire card to be
mounted ro.
The identical kernel boots on the b7 board just fine.
--
2.6.35-devel is u
I can acknowledge that it's also working for my setup now. Thanks a lot!
--
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
u
Upstream change isn't correctly reading the gpio_wp line on the beagle..
(the kernel pin mux for the omap is still very young and we do alot in
the bootloader...)
** Changed in: linux-ti-omap (Ubuntu)
Status: New => Fix Released
** Changed in: linux-ti-omap (Ubuntu)
Assignee: (unassig
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
/dev/mm
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 script
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 boot
That's really strange. You can see below that it claims to mount the
rootfs read only. But as you can also see, i can just create a file and
that file is still there after reboot (so it's not just some strange ram
cache i am seeing). And you can also see swap not being mounted.
I am pretty sure yo
Hi,
it's a meego rootfs i am intending to run (if that's your question), but how
should the
rootfs have to do with this? It's not being loaded at all due to this issue.
But: Changing rw to ro allowed root to be mounted and to boot up. This has a
strange
drawback: All other partitions (BOOT on
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:
http://rcn-ee.homeip.net:81
Full log from start to panic attached
** Attachment added: "Full log from start to panic"
http://launchpadlibrarian.net/52245464/log.txt
--
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
On Tue, Jul 20, 2010 at 2:24 PM, Till Harbaum wrote:
> Hi Robert,
>
> i don't have access to the machine in question at this moment, but
> will add the missing information tomorrow.
>
> Regards,
> Till
>
> BTW: I really enjoy your scripts and am i using them to run meego
> on the beagle.
Hi Till
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
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 to
** Branch linked: lp:~beagleboard-kernel/+junk/2.6-stable
** Branch unlinked: lp:~beagleboard-kernel/+junk/2.6-stable
** Branch linked: lp:~beagleboard-kernel/+junk/2.6.35-devel
--
2.6.35-devel is unable to mount root on mmc
https://bugs.launchpad.net/bugs/607906
You received this bug notificat
A similar problem is reported in this thread:
http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/28895.aspx?PageIndex=2
But no explanation/resolution has been found there.
--
2.6.35-devel is unable to mount root on mmc
https://bugs.launchpad.net/bugs/607906
You received this bug
19 matches
Mail list logo
