Ticket #1176 (closed defect: fixed)

Opened 9 years ago

Last modified 8 years ago

Truncated u-boot printout of kernel version string

Reported by: cwixon@… Owned by: willie_chen
Priority: high Milestone:
Component: u-boot Version: 2007.2
Severity: normal Keywords:
Cc: buglog@… Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: no PatchReviewResult:
Reproducible:

Description

I'm pretty sure this is a u-boot function and not a kernel function, but in any
event . . .

It's not a trivial matter to figure out what kernel is installed and operative.

The obvious choices would be uname -r or look at what ipkgs are installed.

Unfortunately, uname omits the svn revision -- I get only "2.6.22.5-moko11".
And ipkg list_installed gives me:

kernel - 2.6.22.5-moko11+svnr3743-r10 - Linux 2.6.x kernel for FIC SmartPhones?
shipping w/ OpenMoko?
kernel-2.6.21.6-moko11 - 2.6.21.6-moko11-r2 - 2.6 Linux Development Kernel for
FIC Neo1973 (GTA01)
kernel-2.6.22.5-moko11 - 2.6.22.5-moko11+svnr3777-r10 - Linux 2.6.x kernel for
FIC SmartPhones? shipping w/ OpenMoko?
kernel-image-2.6.21.6-moko11 - 2.6.21.6-moko11-r2 - 2.6 Linux Development Kernel
for FIC Neo1973 (GTA01)
kernel-image-2.6.22.5-moko11 - 2.6.22.5-moko11+svnr3801-r10 - Linux 2.6.x kernel
for FIC SmartPhones? shipping w/ OpenMoko?

. . . which doesn't narrow things down much.

But by going into the u-boot menu and booting from there, there is a display for
a fraction of a second of the full kernel file information, including the svn
revision, build date, etc.

HOWEVER the svn revision is truncated by one digit. In my case, the info ended
in "r377" which, when checked against the ipkg list, suggests that I have r3777.

But it would not distinguish between multiple kernel options having svn

revisions that differ only in the last digit.

Change History

comment:1 Changed 9 years ago by roh

  • Owner changed from willie_chen@… to willie_chen

comment:2 Changed 8 years ago by john_lee

  • Status changed from new to closed
  • HasPatchForReview unset
  • Resolution set to fixed

with our current git scm this should be easy now.

Note: See TracTickets for help on using tickets.