Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Problem with udev upgrading from wheezy to jessie

1,007 views
Skip to first unread message

Martin Hanson

unread,
Jan 24, 2016, 6:30:05 AM1/24/16
to
I am trying to upgrade a cubox (arm) from Wheezy to Jessie, but I keep running into problems with udev. When I try to install latest kernel from backports:

<SNIP>
# dpkg -i linux-image-4.3.0-0.bpo.1-armmp_4.3.3-7~bpo8+1_armhf.deb
dpkg: regarding .../linux-image-4.3.0-0.bpo.1-armmp_4.3.3-7~bpo8+1_armhf.deb containing linux-image-4.3.0-0.bpo.1-armmp:
linux-image-4.3.0-0.bpo.1-armmp breaks udev (<< 208-8~)
udev (version 175-7.2) is present and installed.

dpkg: error processing archive linux-image-4.3.0-0.bpo.1-armmp_4.3.3-7~bpo8+1_armhf.deb (--install):
installing linux-image-4.3.0-0.bpo.1-armmp would break udev, and
deconfiguration is not permitted (--auto-deconfigure might help)
Errors were encountered while processing:
linux-image-4.3.0-0.bpo.1-armmp_4.3.3-7~bpo8+1_armhf.deb
</SNIP>

Then trying to solve that installing udev:

<SNIP>
# dpkg -i udev_215-17+deb8u3_armhf.deb
(Reading database ... 50189 files and directories currently installed.)
Preparing to unpack udev_215-17+deb8u3_armhf.deb ...
Since release 198, udev requires support for the following features in
the running kernel:

- inotify(2) (CONFIG_INOTIFY_USER)
- signalfd(2) (CONFIG_SIGNALFD)
- accept4(2)
- open_by_handle_at(2) (CONFIG_FHANDLE)
- timerfd_create(2) (CONFIG_TIMERFD)
- epoll_create(2) (CONFIG_EPOLL)

Please upgrade your kernel before or while upgrading udev.

AT YOUR OWN RISK, you can force the installation of this version of udev
WHICH DOES NOT WORK WITH YOUR RUNNING KERNEL AND WILL BREAK YOUR SYSTEM
AT THE NEXT REBOOT by creating the /etc/udev/kernel-upgrade file.
There is always a safer way to upgrade, do not try this unless you
understand what you are doing!


dpkg: error processing archive udev_215-17+deb8u3_armhf.deb (--install):
subprocess new pre-installation script returned error exit status 1
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
insserv: warning: script 'K01nzbgetd' missing LSB tags and overrides
insserv: warning: script 'nzbgetd' missing LSB tags and overrides
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
insserv: warning: script 'K01nzbgetd' missing LSB tags and overrides
insserv: warning: script 'nzbgetd' missing LSB tags and overrides
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
insserv: warning: script 'K01nzbgetd' missing LSB tags and overrides
insserv: warning: script 'nzbgetd' missing LSB tags and overrides
Errors were encountered while processing:
udev_215-17+deb8u3_armhf.deb
</SNIP>

How do I solve that, one is depending upon the other, but the other won't install as long as the first is running.

deloptes

unread,
Jan 24, 2016, 9:40:05 AM1/24/16
to
Martin Hanson wrote:

> Please upgrade your kernel before or while upgrading udev.

install both at the same time?

Michael Biebl

unread,
Jan 24, 2016, 1:20:07 PM1/24/16
to
> How do I solve that, one is depending upon the other, but the other won't install as long as the first is running.

- Use a Debian kernel, which has all necessary features enabled.
- Read the error messsage (again) It tells you what you can do.


--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

signature.asc

Martin Hanson

unread,
Jan 24, 2016, 5:20:05 PM1/24/16
to
> install both at the same time?

Are you kidding me?!

Martin Hanson

unread,
Jan 24, 2016, 5:20:06 PM1/24/16
to
Wauw, amazing, just freaking amazing!

24.01.2016, 18:56, "Michael Biebl" <bi...@debian.org>:

Lisi Reisz

unread,
Jan 24, 2016, 6:20:03 PM1/24/16
to
On Sunday 24 January 2016 21:50:35 Martin Hanson wrote:
> > install both at the same time?
>
> Are you kidding me?!

No.

# aptitude install linux-image-whatever udev

Lisi

Chris Bannister

unread,
Jan 26, 2016, 5:30:05 AM1/26/16
to
On Sun, Jan 24, 2016 at 11:58:16AM +0100, Martin Hanson wrote:
>
> Please upgrade your kernel before or while upgrading udev.
>
> AT YOUR OWN RISK, you can force the installation of this version of udev
> WHICH DOES NOT WORK WITH YOUR RUNNING KERNEL AND WILL BREAK YOUR SYSTEM
> AT THE NEXT REBOOT by creating the /etc/udev/kernel-upgrade file.

I read this as force the installation of udev (man dpkg search for
force) so, trying to decipher 'dpkg --force-help' I get

dpkg --force-breaks -i udev*deb then IMMEDIATEDLY try installing the
kernel again. Do not reboot until everything is installed without error.

If you get error messages about the syntax, then google or ask here,
I've had trouble myself when doing this. But, I've only needed to do
this maybe once or twice from memory.

Note the message, 'AT YOUR OWN RISK'

I don't know what it means by 'creating the /etc/udev/kernel-upgrade
file.' I'd check to see it it exists prior then after. I'd remove it if
the latter, e.g. I haven't got one in my system.

All this makes me wonder, how did you get into this "situation" in the
first place?

> There is always a safer way to upgrade, do not try this unless you
> understand what you are doing!

I guess this is meaning via normal use of a package manager.

--
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the
oppressing." --- Malcolm X

Lisi Reisz

unread,
Jan 26, 2016, 7:00:07 AM1/26/16
to
On Tuesday 26 January 2016 10:08:35 Chris Bannister wrote:
> On Sun, Jan 24, 2016 at 11:58:16AM +0100, Martin Hanson wrote:
> > Please upgrade your kernel before or while upgrading udev.
> >
> > AT YOUR OWN RISK, you can force the installation of this version of udev
> > WHICH DOES NOT WORK WITH YOUR RUNNING KERNEL AND WILL BREAK YOUR SYSTEM
> > AT THE NEXT REBOOT by creating the /etc/udev/kernel-upgrade file.
>
> I read this as force the installation of udev (man dpkg search for
> force) so, trying to decipher 'dpkg --force-help' I get

No, Chris, surely not. I read it as meaning what it says:

"Please upgrade your kernel before or while upgrading udev"

I.e. upgrade the kernel first or at least install both so that at no time does
the system have to cope with that udev without the newer kernel.

That does of course beg the question of why it needs to ask you to do it, but
perhaps the old kernel is held or something.

Lisi

Michael Biebl

unread,
Jan 26, 2016, 8:10:05 AM1/26/16
to
Am 26.01.2016 um 11:08 schrieb Chris Bannister:
> On Sun, Jan 24, 2016 at 11:58:16AM +0100, Martin Hanson wrote:
>>
>> Please upgrade your kernel before or while upgrading udev.
>>
>> AT YOUR OWN RISK, you can force the installation of this version of udev
>> WHICH DOES NOT WORK WITH YOUR RUNNING KERNEL AND WILL BREAK YOUR SYSTEM
>> AT THE NEXT REBOOT by creating the /etc/udev/kernel-upgrade file.
>
> I read this as force the installation of udev (man dpkg search for
> force) so, trying to decipher 'dpkg --force-help' I get

The maintainer script of udev checks in the preinst phase, if the
installed and running kernel has all necessary features to run udev
successfully. If it doesn't it bails out.

If you are using a Debian provided kernel, it has all necessary features
enabled, so this problem should only happen if you have a self-compiled
kernel.

You can force the upgrade of the udev by creating the flag file
/etc/udev/kernel-upgrade simply by running something like
touch /etc/udev/kernel-upgrade
The run the udev installation again. No special --force flags are necessary.

If you do *not upgrade the kernel afterwards *before* rebooting, it can
lead to an unbootable system.

I thought the error message from udev was pretty clear, but apparently
it isn't?


Michael
signature.asc

deloptes

unread,
Jan 26, 2016, 2:40:04 PM1/26/16
to
Chris Bannister wrote:

> I don't know what it means by 'creating the /etc/udev/kernel-upgrade
> file.' I'd check to see it it exists prior then after. I'd remove it if
> the latter, e.g. I haven't got one in my system.

if we read the OPs original post we would note that he's upgrading from
wheezy to jessie, which is not recommended. he must first upgrade to
squeeze and then jessie. RTFM :)

regards

Charlie Kravetz

unread,
Jan 26, 2016, 3:40:05 PM1/26/16
to
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
If I am reading this list correctly, release sequence was Squeeze,
Wheezy, Jessie. That would make the upgrade wheezy to jessie correct.


- --
Charlie Kravetz
Linux Registered User Number 425914
[http://linuxcounter.net/user/425914.html]
Never let anyone steal your DREAM. [http://keepingdreams.com]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJWp9ToAAoJEIqui46mydCAyaoH/2E9q1jDEUPfZO+VDvQmyqzv
E0NJYBZ6v8h8DCaAlr8gYg/T3IwKqH6U2dSSqdOIRbj7a08nJI/H5tSUkOkC5oVN
owJIesbwB48cvxTu5s42Tsk3VqbaKM4pIqRrI2ir88DVqG3idhm1mM/s8NV4h+ZY
veIENwz+OZcDM2IKTFwbQ103N+AM23+U54v2/a3ND7P4qi7r5+tUfIfaRYXpfrs+
sWjrTuIhUIyuAula3uj/r/mb+AAt+6QqpBEArTb+3sjTFUCa42mynjGrVwpWe1v5
wx9OQFD8lo0wmI9jgtsxmL/+wNNh4359ktZy5M196pmqgzDHhQhmiYNVG5eSJNA=
=uXjg
-----END PGP SIGNATURE-----

Selim T. Erdoğan

unread,
Jan 26, 2016, 4:00:07 PM1/26/16
to
On Tue, Jan 26, 2016 at 01:41:24PM +0100, Michael Biebl wrote:
> Am 26.01.2016 um 11:08 schrieb Chris Bannister:
> > On Sun, Jan 24, 2016 at 11:58:16AM +0100, Martin Hanson wrote:
> >>
> >> Please upgrade your kernel before or while upgrading udev.
> >>
> >> AT YOUR OWN RISK, you can force the installation of this version of udev
> >> WHICH DOES NOT WORK WITH YOUR RUNNING KERNEL AND WILL BREAK YOUR SYSTEM
> >> AT THE NEXT REBOOT by creating the /etc/udev/kernel-upgrade file.
> >

...

> You can force the upgrade of the udev by creating the flag file
> /etc/udev/kernel-upgrade simply by running something like
> touch /etc/udev/kernel-upgrade
> The run the udev installation again. No special --force flags are necessary.
>
> If you do *not upgrade the kernel afterwards *before* rebooting, it can
> lead to an unbootable system.
>
> I thought the error message from udev was pretty clear, but apparently
> it isn't?

The way I read it, the part in capitals grabs all the attention and
breaks the flow of the main sentence. When I first read it (admittedly
not carefully enough) I thought it meant "Installing this version of
udev will break the system at next reboot. It will do this by creating
the /etc/udev/kernel-upgrade file." :)

I think it would have been much clearer if it had been:

AT YOUR OWN RISK, you can force the installation of this version of
udev, by creating the /etc/udev/kernel-upgrade file. However, this
version of udev does not work with your running kernel, so, after
upgrading udev, you MUST also upgrade the kernel before rebooting.
OTHERWISE YOU WILL BREAK YOUR SYSTEM AT THE NEXT REBOOT.

deloptes

unread,
Jan 26, 2016, 4:10:05 PM1/26/16
to
it was my mistake - jessie follows wheezy - I apologize

regards

deloptes

unread,
Jan 26, 2016, 5:00:07 PM1/26/16
to
Charlie Kravetz wrote:

>
> If I am reading this list correctly, release sequence was Squeeze,
> Wheezy, Jessie. That would make the upgrade wheezy to jessie correct.
>

Yes apologies - this should be something with the arm related kernel and
udev versions.

regards

Charlie Kravetz

unread,
Jan 26, 2016, 5:40:04 PM1/26/16
to
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

No problem, just don't want to confuse new people. It would be nice if
names were, at least, alphabetical. Anything to help lesson the
confusion of trying to remember them.


- --
Charlie Kravetz
Linux Registered User Number 425914
[http://linuxcounter.net/user/425914.html]
Never let anyone steal your DREAM. [http://keepingdreams.com]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJWp/B5AAoJEIqui46mydCAJBsH/iNnadpkfrltjJqdg0Gm5NxX
eZ73AUjUdSwcndwyo9t/ZvjYAMEBxNMii/2Sh34CkGLafhPkGiPrBujW0B+zP/8/
caEPlhzZ1fd6nYvp2e0MuD9nhpmkskSA66upKoBuzEkBkf+2wUCW4lsss9OvMexn
pVMV53xNYDfSg3blcEtUdiw+zcqUMq+HfLcfCEoAN/O/FmVtGFcgQJA4dDfIaSGh
DSrDu56eUa291B1JlzDnHXyGohZvffpJTHl3O3dkwDDOMOnvl8fe6vbz9KNOd9Se
Eb+IVQvlzgnQUJfJTcWjtiEoBoCymcIuAulhvpPLE1SrTTKXMsEhCZGvr5B07PY=
=TfNQ
-----END PGP SIGNATURE-----

Brian

unread,
Jan 26, 2016, 6:40:05 PM1/26/16
to
On Tue 26 Jan 2016 at 22:38:36 +0200, Selim T. Erdoğan wrote:

> On Tue, Jan 26, 2016 at 01:41:24PM +0100, Michael Biebl wrote:
>
> > You can force the upgrade of the udev by creating the flag file
> > /etc/udev/kernel-upgrade simply by running something like
> > touch /etc/udev/kernel-upgrade
> > The run the udev installation again. No special --force flags are necessary.
> >
> > If you do *not upgrade the kernel afterwards *before* rebooting, it can
> > lead to an unbootable system.
> >
> > I thought the error message from udev was pretty clear, but apparently
> > it isn't?
>
> The way I read it, the part in capitals grabs all the attention and
> breaks the flow of the main sentence. When I first read it (admittedly
> not carefully enough) I thought it meant "Installing this version of
> udev will break the system at next reboot. It will do this by creating
> the /etc/udev/kernel-upgrade file." :)

It's primarily a "comma" problem, but the capitals do not help and the
"AT YOUR OWN RISK" and "WILL BREAK YOUR SYSTEM" are superfluous.
Any action carried out on a computer is done at the user's risk and if
it does not work with the running kernel it will obviously break the
system.

This might be an improvement:

You can force the installation of this version of udev, WHICH WILL NOT
WORK WITH YOUR PRESENT, RUNNING KERNEL AT THE NEXT REBOOT, by creating
the /etc/udev/kernel-upgrade file.

"force" and "creating" are still somewhat dissociated from each other.
The two ideas would be better expressed in two sentences.

Alternatively:

Please upgrade your kernel before or after upgrading udev. This
version of udev will not work with the kernel you are using at
present. If you do not upgrade the kernel before rebooting it can
lead to an unbootable system.

You can force the installation of this version of udev by creating the
file /etc/udev/kernel-upgrade.

> I think it would have been much clearer if it had been:
>
> AT YOUR OWN RISK, you can force the installation of this version of
> udev, by creating the /etc/udev/kernel-upgrade file. However, this
> version of udev does not work with your running kernel, so, after
> upgrading udev, you MUST also upgrade the kernel before rebooting.
> OTHERWISE YOU WILL BREAK YOUR SYSTEM AT THE NEXT REBOOT.

The first two commas are not necessary.

Lisi Reisz

unread,
Jan 26, 2016, 6:40:05 PM1/26/16
to
7 -> 6 -> 8 ????

I think it is you who have had a slight aberration, deloptes. ;-)

Lisi

Sorry for erroneous off-list post.

deloptes

unread,
Jan 26, 2016, 7:10:11 PM1/26/16
to
Lisi Reisz wrote:

>
> I think it is you who have had a slight aberration, deloptes. ;-)
>
> Lisi
>
> Sorry for erroneous off-list post.

at least gmail seem to work better than yahoo

Chris Bannister

unread,
Jan 28, 2016, 5:50:07 AM1/28/16
to
On Tue, Jan 26, 2016 at 10:38:36PM +0200, Selim T. Erdoğan wrote:
> On Tue, Jan 26, 2016 at 01:41:24PM +0100, Michael Biebl wrote:
> > Am 26.01.2016 um 11:08 schrieb Chris Bannister:
> > > On Sun, Jan 24, 2016 at 11:58:16AM +0100, Martin Hanson wrote:
> > >>
> > >> Please upgrade your kernel before or while upgrading udev.
> > >>
> > >> AT YOUR OWN RISK, you can force the installation of this version of udev
> > >> WHICH DOES NOT WORK WITH YOUR RUNNING KERNEL AND WILL BREAK YOUR SYSTEM
> > >> AT THE NEXT REBOOT by creating the /etc/udev/kernel-upgrade file.
> > >
>
> ...
>
> > You can force the upgrade of the udev by creating the flag file
> > /etc/udev/kernel-upgrade simply by running something like
> > touch /etc/udev/kernel-upgrade
> > The run the udev installation again. No special --force flags are necessary.
> >
> > If you do *not upgrade the kernel afterwards *before* rebooting, it can
> > lead to an unbootable system.
> >
> > I thought the error message from udev was pretty clear, but apparently
> > it isn't?
>
> The way I read it, the part in capitals grabs all the attention and
> breaks the flow of the main sentence. When I first read it (admittedly
> not carefully enough) I thought it meant "Installing this version of
> udev will break the system at next reboot. It will do this by creating
> the /etc/udev/kernel-upgrade file." :)

Me too! :)

> I think it would have been much clearer if it had been:
>
> AT YOUR OWN RISK, you can force the installation of this version of
> udev, by creating the /etc/udev/kernel-upgrade file. However, this
> version of udev does not work with your running kernel, so, after
> upgrading udev, you MUST also upgrade the kernel before rebooting.
> OTHERWISE YOU WILL BREAK YOUR SYSTEM AT THE NEXT REBOOT.

Perfect! (ok, you don't need the comma after the first 'udev')

Lisi Reisz

unread,
Jan 28, 2016, 6:10:06 AM1/28/16
to
Not quite. It still does need the sentence:
"Please upgrade your kernel before or while upgrading udev."
Perhaps even better:
"Please upgrade your kernel before upgrading udev."
to precede it, since that would obviously be the best way to proceed. Get the
kernel on first - after all, there are such things as power cuts. You might
install udev, then have e.g. a power cut.

Lisi

Chris Bannister

unread,
Jan 28, 2016, 6:10:06 AM1/28/16
to
On Tue, Jan 26, 2016 at 11:19:26PM +0000, Brian wrote:
> This might be an improvement:
>
> You can force the installation of this version of udev, WHICH WILL NOT
> WORK WITH YOUR PRESENT, RUNNING KERNEL AT THE NEXT REBOOT, by creating
> the /etc/udev/kernel-upgrade file.

That sounds confusing. I could, on a bad day, read that as needing to
reboot to update udev after creating the /etc/udev/kernel-upgrade file.

> "force" and "creating" are still somewhat dissociated from each other.
> The two ideas would be better expressed in two sentences.
>
> Alternatively:
>
> Please upgrade your kernel before or after upgrading udev. This
> version of udev will not work with the kernel you are using at
> present. If you do not upgrade the kernel before rebooting it can
> lead to an unbootable system.
>
> You can force the installation of this version of udev by creating the
> file /etc/udev/kernel-upgrade.

Or ...

You can force the installation of this version of udev by first creating
a /etc/udev/kernel-upgrade file, "touch /etc/udev/kernel-upgrade file"
is sufficient, before proceeding with the udev installation.

Chris Bannister

unread,
Jan 31, 2016, 1:00:07 PM1/31/16
to
On Thu, Jan 28, 2016 at 10:53:55AM +0000, Lisi Reisz wrote:
>
> Not quite. It still does need the sentence:
> "Please upgrade your kernel before or while upgrading udev."
> Perhaps even better:
> "Please upgrade your kernel before upgrading udev."
> to precede it, since that would obviously be the best way to proceed. Get the
> kernel on first - after all, there are such things as power cuts. You might
> install udev, then have e.g. a power cut.

My understanding was that the kernel won't install *because* of the installed version
of udev

Lisi Reisz

unread,
Jan 31, 2016, 1:30:06 PM1/31/16
to
On Sunday 31 January 2016 17:35:46 Chris Bannister wrote:
> On Thu, Jan 28, 2016 at 10:53:55AM +0000, Lisi Reisz wrote:
> > Not quite. It still does need the sentence:
> > "Please upgrade your kernel before or while upgrading udev."
> > Perhaps even better:
> > "Please upgrade your kernel before upgrading udev."
> > to precede it, since that would obviously be the best way to proceed.
> > Get the kernel on first - after all, there are such things as power cuts.
> > You might install udev, then have e.g. a power cut.
>
> My understanding was that the kernel won't install *because* of the
> installed version of udev

No. Other way round. Install the new kernel and udev will be fine. That
sentence
"Please upgrade your kernel before or while upgrading udev."
was taken from the original error message as reported by the OP - I just
copied and pasted it.

The upgraded udev won't boot with the old kernel, so if you install the
upgraded udev, and you shut down or are forcibly shut down by force majeure,
you are in trouble. The kernel must go on first or simultaneously. First is
obviously safer.

Lisi
0 new messages