A long time ago (last December) I reported a problem with Dreamplug at
least 3.6.10 through to 3.7.5 suffering from the kernel reporting a soft
lockup when I doing a git pull when it was anything but a small update
over the network - see
https://bugzilla.redhat.com/show_bug.cgi?id=910593 . The
I have tried booting a Dreamplug with the 3.10.10 kernel, but it fails
to boot successfully, and I would appreciate some guidance as to how to
work around the problem.
The symptoms are that it drops into dracut, reporting that it cannot
find the root filesystem on /dev/sdb3 (another Dreamplug
available to install?
Any help with identifying the problem (and better still resolving it!)
would be much appreciated.
Quentin Armitage
___
arm mailing list
arm@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm
My boot partition is VFAT. For some reason the factory u-boot on the
Dreamplug does not support EXT; I've always assumed that this was
because the Sheevaplug u-boot had problems with EXT (it couldn't load a
file if any part of it was more the 2Gb from the start of the
partition).
Quentin
On Wed,
to see support for them being dropped from Fedora.
For me, I still see quite a lifetime in them for what they are doing.
Quentin Armitage
___
arm mailing list
arm@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm
[c0008c60]
(ret_fast_syscall+0x0/0x2c)
And the above keeps repeating until I power off the plug.
Is this of interest on this list, or should I report it elsewhere?
Quentin Armitage
___
arm mailing list
arm@lists.fedoraproject.org
https
behaviour does not seem intuitive to me; is it correct
behaviour? If this is what is expected, how do I stop a tmpfs filesystem
being mounted on tmp before I mount another filesystem on /tmp?
Quentin Armitage
___
arm mailing list
arm@lists.fedoraproject.org
https
Hi,
I realise this is short notice, but I'd be happy to test on my
Dreamplug. It is already running F18, but I'd happy install an RC1 image
if one is available.
Quentin Armitage
On Fri, 2012-10-26 at 00:06 -0400, Paul Whalen wrote:
Good day all,
Please join us tomorrow (October 26th, 2012
is a patch that sets MOZ_ARM_ARCH to armv5te if $target_cpu is
armv5tel.
I have build the modified js package and Authorisation Manager now
successfully starts.
Should I report this anywhere else, or is this email sufficient for this
problem to be resolved.
Quentin Armitage
--- a/js/src/configure.in
as the start sector, and that works fine.
Does the rootfs-resize script need to be modified to read the start
sector of the partition before it deletes it, and force the new
partition to have the same start sector? I have attached a patch to the
rootfs-resize script that does that.
Quentin
___
The URL http://arm.koji.fedoraproject.org/~jchiappetta/fxxstats.html
gives me a 404 Not Found error.
Quentin Armitage
___
arm mailing list
arm@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm
F13 Beta 3, at least at
http://arm.koji.fedoraproject.org/mash/beta/f13-arm-2011-05-10/f13-arm/arm/os/Packages/
has fedora-release-13-1.2.beta2.noarch.rpm but presumably this should be beta3.
Looking at the /etc/yum.repos.d/*repo files in that package, they not
surprisingly point to
On Wed, 2011-05-18 at 22:42 +0100, Quentin Armitage wrote:
The only packages that I have installed on Beta2 that are upgraded in
Beta3 are thte gcc suite and perl-version. I intend to edit
the /etc/yum.repos.d/* files to point to the new location and install
them; presumably that's an easy way
Hi,
I've done a scratch build of perl-Crypt-OpenSSL-RSA which has been
successful, although there is no installable package available (it is
listed in http://arm.koji.fedoraproject.org/possible_dep_failures.html ,
but this seems to be for the F-11 build): see
14 matches
Mail list logo
