Two people now reporting that this bug may be back in the current daily
images. Will continue to investigate, but I wanted to go ahead and
reopen this since it seems likely to be the case.
** Changed in: linux-fsl-imx51 (Ubuntu Karmic)
Status: Fix Released = Triaged
--
hardware clock
Actually things work like a charm with Babbage 2.5 for me; they never
worked with Babbage 2.0.
It seems Paul's 2.5 fails, my works, and all 2.0 fail. We need more
input.
--
hardware clock not saved if board power is removed on babbage 2.5
https://bugs.launchpad.net/bugs/427289
You received
Ok, I misunderstood a conversation on irc. Loic confirmed that on his
2.5 the time is still preserved after being unplugged. Looks like my
battery is just going dead :(
** Changed in: linux-fsl-imx51 (Ubuntu Karmic)
Status: Triaged = Fix Released
--
hardware clock not saved if board
Is the voltage supposed to match between b3.0 and 2.5/2.0?
--
hardware clock not saved if board power is removed on babbage 2.5
https://bugs.launchpad.net/bugs/427289
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This appears to get fixed using the test kernel from comment #5 in bug
446140
--
hardware clock not saved if board power is removed on babbage 2.5
https://bugs.launchpad.net/bugs/427289
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This bug was fixed in the package linux-fsl-imx51 - 2.6.31-105.14
---
linux-fsl-imx51 (2.6.31-105.14) karmic; urgency=low
[ Andy Whitcroft ]
* rebase to Ubuntu-2.6.31-14.46
* [Config] update configs since rebase to Ubuntu-2.6.31-14.46
* lirc update dropped module
I have checked on my BBG3.0, that the time is correctly kept after a shutdown.
My KCONFIG has this:
#
# on-CPU RTC drivers
#
# CONFIG_RTC_MXC is not set
# CONFIG_RTC_DRV_MXC_V2 is not set
# CONFIG_RTC_DRV_IMXDI is not set
CONFIG_RTC_MC13892=y
# CONFIG_DMADEVICES is not set
CONFIG_REGULATOR=y
#
Please note BBG2.0 coin-cell battery can not be chargable. If the
voltage of coin-cell battery is lower than 1.8V, it can not maintain RTC
any more. You can replace another coin-cell battery or use BBG2.5/BBG3.0
whose coin-cell battery can be chargable for tests.
--
hardware clock not saved if
I'm testing with a BBG2.5. Thanks for the heads up though.
--
hardware clock not saved if board power is removed on babbage 2.5
https://bugs.launchpad.net/bugs/427289
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
same here, i belive the only person that commented here on the bug who
actually has a 2.0 available is lioc, the rest of us should be testing
on 2.5 anyway.
--
hardware clock not saved if board power is removed on babbage 2.5
https://bugs.launchpad.net/bugs/427289
You received this bug
hmm, i see two different options in my current config (-101 though)
o...@babbage2:~/devel/kernel/linux-fsl-imx51-2.6.31$ grep 13892
/boot/config-2.6.31-101-imx51 |grep RTC
CONFIG_MXC_MC13892_RTC=y
# CONFIG_RTC_MC13892 is not set
--
hardware clock not saved if board power is removed on babbage
I applied the following patch, built and tested. This didn't help. In
fact, the date/time is reset across simple reboots.
diff --git a/debian.fsl-imx51/config/config.common.ubuntu
b/debian.fsl-imx51/config/config.common.ubuntu
index c7c95b0..7730975 100644
---
I applied the following patch as well and still no joy.
diff --git a/debian.fsl-imx51/config/config.common.ubuntu
b/debian.fsl-imx51/config/config.common.ubuntu
index 7730975..6660034 100644
--- a/debian.fsl-imx51/config/config.common.ubuntu
+++ b/debian.fsl-imx51/config/config.common.ubuntu
@@
** Changed in: linux-fsl-imx51 (Ubuntu Karmic)
Status: Triaged = In Progress
** Changed in: linux-fsl-imx51 (Ubuntu Karmic)
Assignee: Amit Kucheria (amitk) = Brad Figg (brad-figg)
--
hardware clock not saved if board power is removed on babbage 2.5
In the current fsl-imx51 branch. The configuration already has
CONFIG_RTC_MC13892=y. I disabled CONFIG_RTC_DRV_MXC_V2 and tested that
change. The date is reset across simple reboots. I didn't bother testing
pulling the power.
--
hardware clock not saved if board power is removed on babbage 2.5
I might've made a mistake in the RTC configuration. Brad, could you try
enabling CONFIG_RTC_MC13892=y ( from Jaunty) and disabling
CONFIG_RTC_DRV_MXC_V2=y.
** Changed in: linux-fsl-imx51 (Ubuntu Karmic)
Status: Incomplete = Triaged
--
hardware clock not saved if board power is removed on
I installed a Babbage 2.0 with latest karmic image (beta image
candidate) and left it running for the night; then I unplugged
everything (including ethernet and DVI) for ~30 mn and the time was back
to 1970 when I powered it again. (ntpdate didn't kick in due to NM not
picking up the interface.)
** Changed in: linux-fsl-imx51 (Ubuntu Karmic)
Milestone: ubuntu-9.10-beta = ubuntu-9.10
--
hardware clock not saved if board power is removed on babbage 2.5
https://bugs.launchpad.net/bugs/427289
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
For those who see this bug, could you please try to measure the the
batter voltage. I suspect several of you have dead batteries that won't
charge anymore.
My board managed to keep its date and time after being unplugged for
over 3 days. (I was working on in on Friday and then put it on the place
Marking invalid so that it annoys people with this bug into action :-p
** Changed in: linux-fsl-imx51 (Ubuntu Karmic)
Status: Triaged = Invalid
--
hardware clock not saved if board power is removed on babbage 2.5
https://bugs.launchpad.net/bugs/427289
You received this bug notification
Please use the incomplete state for that, as that's what it is for.
Also, invalid causes it to fall off the radar unless you are actively
looking for it or subscribed. I'll try to dig out a voltmeter today and
take a look at this on my board also.
** Changed in: linux-fsl-imx51 (Ubuntu Karmic)
@amitk also, since yours is working, could you please verify the
voltages that you see when it's on/charging, and also the voltage with
the power completely disconnected?
--
hardware clock not saved if board power is removed on babbage 2.5
https://bugs.launchpad.net/bugs/427289
You received this
I'm seeing about 2-2.01V when powered on. I left it running for several
hours this morning while I did an install, and about another hour or two
after that. Time was correct and current when I powered down. I left
it off for about 30 min and tested the battery again. I got pretty
close to the
ok, finally fond my voltmeter:
if the board is powered off completely i see 1.104V measuring directly on the
battery.
powering up the board this does not change at all. given that the regulator
should initialize a charge, i would expect the voltage to change the moment the
charger gets
** Changed in: linux-fsl-imx51 (Ubuntu Karmic)
Status: Fix Committed = Triaged
--
hardware clock not saved if board power is removed on babbage 2.5
https://bugs.launchpad.net/bugs/427289
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
testing with 2.6.31-101-imx51 i now left the battery charge for two days but
there doesnt seem to be a difference ...
reboot works and keeps the time just fine, shutting down, removing power and
booting up again gets me the clock to 01.01.1970
--
hardware clock not saved if board power is
oh, and i dont have a voltmeter handy but given the board and battery
are pretty new i would expect the battery to not be broken ... i will
try to find a voltmeter to actually measure the voltage
--
hardware clock not saved if board power is removed on babbage 2.5
** Changed in: linux-fsl-imx51 (Ubuntu Karmic)
Milestone: karmic-alpha-6 = ubuntu-9.10-beta
--
hardware clock not saved if board power is removed on babbage 2.5
https://bugs.launchpad.net/bugs/427289
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Fix committed and about to be uploaded.
** Changed in: linux-fsl-imx51 (Ubuntu Karmic)
Status: Triaged = Fix Committed
--
hardware clock not saved if board power is removed on babbage 2.5
https://bugs.launchpad.net/bugs/427289
You received this bug notification because you are a member
Still easily reproducible in current daily builds
** Changed in: linux-fsl-imx51 (Ubuntu Karmic)
Status: New = Triaged
--
hardware clock not saved if board power is removed on babbage 2.5
https://bugs.launchpad.net/bugs/427289
You received this bug notification because you are a member
Hi,
Freescale told the patch I'm attaching is probably needed to help things
work.
They mentioned there are two RTCs on Babbage, the one they are using and
recommend we use is the power management one.
They said they might be other issues with the RTC but this should solve
the top issue.
The
Oh and I verified that it applied to our imx51 branch.
--
hardware clock not saved if board power is removed on babbage 2.5
https://bugs.launchpad.net/bugs/427289
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
The patch will not show instant results, as it simply enables the button
battery to be charged. The button battery holds the RTC running when
power is removed so you need to allow the battery to charge for some
time (likely 8-10 hours) before it will hold the clock alive.
There is also some
33 matches
Mail list logo
