#9648 NORM 1.5-F11: applying a kernel upgrade via rpm is ineffective

[Zarro Boogs per Child]

#9648: applying a kernel upgrade via rpm is ineffective
------------------------------------+---------------------------------------
           Reporter:  Quozl         |       Owner:                                   
               Type:  defect        |      Status:  new                              
           Priority:  normal        |   Milestone:  1.5-F11                          
          Component:  not assigned  |     Version:  Development build as of this date
         Resolution:                |    Keywords:                                   
        Next_action:  diagnose      |    Verified:  0                                
Deployment_affected:                |   Blockedby:                                   
           Blocking:                |  
------------------------------------+---------------------------------------

Comment(by mikus):

 I'm not sure of how to read your problem description. In my mind, there
 are several stages to "upgrading" a kernel. The most important of these
 stages is to 'store' the new kernel file(s), and to 'point' the boot
 loader to this new stored kernel. The above description says the old
 kernel file(s) were moved, without saying to which kernel (new or old) the
 boot loader is now pointed.

 [ For what it's worth, on an XO-1 with soas04xo (i.e., F12) I installed a
 later kernel with 'rpm', and what the boot loader tried to bring up was
 the new kernel. When that attempt crashed, I had to manually 're-point'
 the boot loader to the old kernel, in order to be able to use that machine
 again. Luckily, 'rpm' had "installed" the new kernel version without
 "removing" the old kernel version. ]

-- 
Ticket URL: <http://dev.laptop.org/ticket/9648#comment:2>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system