ubuntu-users Digest, Vol 138, Issue 56

Seelam Koteswararao steevan2 at gmail.com
Mon Feb 15 12:22:56 UTC 2016


Dear sir,
please  don't send information...
regards
koteswararao seelam

On Mon, Feb 15, 2016 at 5:30 PM, <ubuntu-users-request at lists.ubuntu.com>
wrote:

> Send ubuntu-users mailing list submissions to
>         ubuntu-users at lists.ubuntu.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
> or, via email, send a message with subject or body 'help' to
>         ubuntu-users-request at lists.ubuntu.com
>
> You can reach the person managing the list at
>         ubuntu-users-owner at lists.ubuntu.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ubuntu-users digest..."
>
>
> Today's Topics:
>
>    1. Re: update manager refuses to upgrade kernel to newer version
>       (Oliver Grawert)
>    2. Re: update manager refuses to upgrade kernel to newer version
>       (Ralf Mardorf)
>    3. Re: update manager refuses to upgrade kernel to newer version
>       (Spyros Tsiolis)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 14 Feb 2016 21:51:14 +0100
> From: Oliver Grawert <ogra at ubuntu.com>
> To: ubuntu-users at lists.ubuntu.com
> Subject: Re: update manager refuses to upgrade kernel to newer version
> Message-ID: <1455483074.30148.52.camel at ubuntu.com>
> Content-Type: text/plain; charset="utf-8"
>
> hi,
> Am Sonntag, den 14.02.2016, 20:05 +0000 schrieb Spyros Tsiolis:
>
> > I think they are the *-46 kernel files , yes. I agree with you
> > totally.
> > What I can't stop my mind from thinking though, is why on one
> > installation
> > the kernels get updated and run the newest kernel version and on the
> > other
> > installation this no longer applies. . . . .
> >
> if you say "one installation" vs "other istallation" i assume you refer
> to the server vs the NFS root ?
>
> the way you install an ubuntu (or debian) system is pretty essential
> for the initial configuration, so while you likely used ubiquity or the
> text based installer for the server, how did you install the nfs root,
> this might explain different behavior (i.e. if you use debootstrap to
> create an initial chroot that gets you a completely unconfigured system
> which will differ from what you get using one of the installers that
> apply a debconf preseed by default ...)
>
> and on a sidenote, as i mentioned before, you should make sure that
> /proc, /sys and /dev are mounted when you are inside the chroot (and
> also make sure to unmount these before (or even after) leaving it). the
> pre/postinst scripts of packages often use info from these dirs to do
> the pre/post configuration
>
> for the PXE issue, i'd start with copying the new vmlinuz and
> initrd.img files into the PXE dir, that should get you going with the
> updated kernel ... once you have this fixed we can move on and look at
> the remaining probs.
>
> ...one thing at a time ;)
>
> ciao
>         oli
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 173 bytes
> Desc: This is a digitally signed message part
> URL: <
> https://lists.ubuntu.com/archives/ubuntu-users/attachments/20160214/4dd547a5/attachment-0001.pgp
> >
>
> ------------------------------
>
> Message: 2
> Date: Mon, 15 Feb 2016 04:34:10 +0100
> From: Ralf Mardorf <silver.bullet at zoho.com>
> To: ubuntu-users at lists.ubuntu.com
> Subject: Re: update manager refuses to upgrade kernel to newer version
> Message-ID: <20160215043410.20d6b935 at utnubu>
> Content-Type: text/plain; charset=US-ASCII
>
> On Sun, 14 Feb 2016 12:17:56 -0800, Randy Williamson wrote:
> >You have broken packages that need fixed before you can do any thing
> >else. Try dpkg - l and See off you can find what package has missing
> >dependencies
>
> A package couldn't be installed and the messages already explained what
> package and why it can't be installed.
>
> >On Feb 12, 2016 12:49 AM, "Spyros Tsiolis" <stsiol at yahoo.co.uk> wrote:
> >> W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for
> >> module r8169
>
> This is a warning that doesn't matter.
>
> >> /usr/sbin/grub-probe: error: cannot find a device for / (is /dev
> >> mounted?).
>
> This is the error. The grub auto-thingy doesn't work for the diskless
> PXE.
>
> >> dpkg: dependency problems prevent configuration of
> >> linux-image-generic-lts-trusty:
> >>  linux-image-generic-lts-trusty depends on
> >> linux-image-3.13.0-77-generic; however:
> >>   Package linux-image-3.13.0-77-generic is not configured yet.
>
> So it is a missing dependency for the meta package, but the
> dependency, the image package is available, it just can't be
> installed, as long as the automation is enabled or grub isn't removed.
> After removing grub or disabling the automation it could be installed.
>
> This already is solved for the OP, now there still seems to be a PXE
> issue.
>
> Regards,
> Ralf
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 15 Feb 2016 11:35:36 +0000 (UTC)
> From: Spyros Tsiolis <stsiol at yahoo.co.uk>
> To: not for general discussionsUbuntu user technical support
>         <ubuntu-users at lists.ubuntu.com>
> Subject: Re: update manager refuses to upgrade kernel to newer version
> Message-ID:
>         <73220608.6861642.1455536136652.JavaMail.yahoo at mail.yahoo.com>
> Content-Type: text/plain; charset=UTF-8
>
> Hi again Oliver,
>
> --------------------------------------------
> > On Sun, 14/2/16, Oliver Grawert <ogra at ubuntu.com> wrote:
> >
> >  Subject: Re: update manager refuses to upgrade kernel to newer version
> >  To: ubuntu-users at lists.ubuntu.com
> >  Date: Sunday, 14 February, 2016, 22:51
> >
> >  hi,
> >  Am
> >  Sonntag, den 14.02.2016, 20:05 +0000 schrieb Spyros
> >  Tsiolis:
> >
> >  > I think they
> >  > are the *-46 kernel files , yes. I agree with you
> >  > totally.
> >  > What I
> >  > can't stop my mind from thinking though, is why on
> >  > one
> >  > installation
> >  >
> >  > the kernels get updated and run the newest kernel version
> >  > and on the
> >  > other
> >  >
> >  > installation this no longer applies. . . . .
> >  >?
> >  if you say "one
> >  installation" vs "other istallation" i assume
> >  you refer
> >  to the server vs the NFS root ?
>
> There are two identical installations; One is running on top of the
> hardware at one clients' site the other runs on top of VMware ESXi
> on another clients' site.
>
>
> PLEASE NOTE : I WAS WRONG ! Just checked today both installations.
> Both of them run v3.13-46 if I recall the kernel versions correctly.
> My mistake again.
> But to tell you the truth, now it makes sense. Since the initial systems
> run off an NFS server and load the kernel to RAM and the Kernel
> updates the system does (while it is running) is storing the newer kernel
> versions under "/boot/" (again if recall correctly).
> So the "vmlinuz" and "initrd.img" with the newer kernel version need to
> be created by hand.
>
>
> >  the way you install an
> >  ubuntu (or debian) system is pretty essential
> >  for the initial configuration, so while you
> >  likely used ubiquity or the
>
> Sorry, could you mean "synaptic" instead of "ubiquity" ?
>
> >  text based
> >  installer for the server, how did you install the nfs
> >  root,
>
> NFS root is living on a totally different server running
> Ubuntu server v12.04 at x86 instruction set.
>
> >  this might explain different behavior
> >  (i.e. if you use debootstrap to
> >  create an
> >  initial chroot that gets you a completely unconfigured
> >  system
> >  which will differ from what you get
> >  using one of the installers that
> >  apply a
> >  debconf preseed by default ...)
>
> >  and on a sidenote, as i mentioned before, you
> >  should make sure that
> >  /proc, /sys and /dev
> >  are mounted when you are inside the chroot (and
> >  also make sure to unmount these before (or even
> >  after) leaving it). the
> >  pre/postinst scripts
> >  of packages often use info from these dirs to do
> >  the pre/post configuration
>
> The last part I pretty sure I havne't done it.
>
> Here's the output of the "mount" command from a running
> "thin-client" :
>
> ip.add.re.ss:/var/tftpboot/ubu1204x86diskless on / type nfs (rw)
> proc on /proc type proc (rw)
> sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
> udev on /dev type devtmpfs (rw,mode=0755)
> devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
> tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
> none on /sys/fs/fuse/connections type fusectl (rw)
> none on /sys/kernel/debug type debugfs (rw)
> none on /sys/kernel/security type securityfs (rw)
> none on /tmp type tmpfs (rw)
> none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
> none on /run/shm type tmpfs (rw,nosuid,nodev)
> none on /var/tmp type tmpfs (rw)
> binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc
> (rw,noexec,nosuid,nodev)
>
>
> >  for the PXE issue, i'd start with copying
> >  the new vmlinuz and
> >  initrd.img files into
> >  the PXE dir, that should get you going with the
> >  updated kernel ... once you have this fixed we
> >  can move on and look at
> >  the remaining
> >  probs.
>
> Yep, Tried it this morning. Couldn't find a machine with
> ubuntu 12.04 x86 running on it, so I will have to do a virtual
> installation on my MAC, then try to create the two files.
>
>
> >  ...one thing at a
> >  time ;)
> >
> >  ciao
> >  ???
> >  oli
>
> Best Regards,
>
> spyros
>
>
>
> ------------------------------
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>
>
> End of ubuntu-users Digest, Vol 138, Issue 56
> *********************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20160215/03c047a9/attachment.html>


More information about the ubuntu-users mailing list