Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #187065 > unrolled thread
| Started by | jpff <jpff@codemist.co.uk> |
|---|---|
| First post | 2017-09-20 17:50 +0200 |
| Last post | 2017-09-21 21:20 +0200 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.debian.user
Upgrade problems (wheezy->jessie) jpff <jpff@codemist.co.uk> - 2017-09-20 17:50 +0200
Re: Upgrade problems (wheezy->jessie) David Christensen <dpchrist@holgerdanske.com> - 2017-09-21 06:20 +0200
Re: Upgrade problems (wheezy->jessie) deloptes <deloptes@gmail.com> - 2017-09-21 21:20 +0200
| From | jpff <jpff@codemist.co.uk> |
|---|---|
| Date | 2017-09-20 17:50 +0200 |
| Subject | Upgrade problems (wheezy->jessie) |
| Message-ID | <urPqb-4XF-21@gated-at.bofh.it> |
I seem to need to upgrade to Debian stretch to install my printer as it needs hplip 3.16.11, ad I was running wheezy. I understand this needs to be done in two stages, wheezy->jessie->stretch, but I still need advice as I cannot find out the solution to my problem. I tried upgrading from Wheezy to Jessie using apt-get upgrade and apt-get dist-upgrade as the instructions said. All seemed OK until disaster struck when the Jessie failed to reboot. As the computer is headless I had to dismantle it all, loose the internet to the entire LAN, and find USB keyboard and dvi cable for screen. Eventually discovered that the kernel installed with Jessie did not load, but the previous kernel did. An hour or so thinking and I managed to get autobooting to work so re-installed with internet and hidden location.... , and eventually communication resumed. But... 1) Why will vmlinuz-3.16.0-4-amd64 not load (says loading and the does nothing for over 30mins) when vmlinuz-3.2.0-4-amd64 does load? 2) Is it OK to run with the older kernel? 3) More importantly will it happen on Jessie->Stretch as climbing up to dismantle the local net is hard (I have a balance issue) or is there a way of testing before rebooting? Any help very welcome ==John ff
[toc] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2017-09-21 06:20 +0200 |
| Message-ID | <us17X-4gR-1@gated-at.bofh.it> |
| In reply to | #187065 |
On 09/20/17 08:32, jpff wrote: > I seem to need to upgrade to Debian stretch to install my printer as > it needs hplip 3.16.11, ad I was running wheezy. ... While some people succeed at major version upgrades, the few times I have attempted it resulted in breakage, frustration, and lots of wasted time and energy. Now I backup my configuration settings, remove the old system drive, take an image of the old system drive, install a new/ zeroed/ secure erased system drive, do a fresh install, migrate my configuration settings, and test each subsystem as I go. If everything works, I'm done. If not, I lower my expectations, find another distribution, and/or build another computer, and restart from "do a fresh install". I have reached two conclusions: 1. Upgrading software is the act of replacing an existing, partially-known set of bugs with a another set of bugs -- some old, some new, some known, some unknown. 2. Software distributors never fix 100% of their bugs -- they make a new release, abandon the old release, and declare victory. David
[toc] | [prev] | [next] | [standalone]
| From | deloptes <deloptes@gmail.com> |
|---|---|
| Date | 2017-09-21 21:20 +0200 |
| Message-ID | <usfaV-4XA-1@gated-at.bofh.it> |
| In reply to | #187065 |
Hi jpff wrote: > 1) Why will vmlinuz-3.16.0-4-amd64 not load (says loading and the does > nothing for over 30mins) when vmlinuz-3.2.0-4-amd64 does load? > don't know - I had same issue In my case I found out that initrd was broken. I still have to unpack the initrd copy /sbin/switch_root and package initrd again, so that I can boot. Why this - I don't know ... > 2) Is it OK to run with the older kernel? > yes, I ran jessie almost 2y with 3.2.0.4-amd64 - nothing wrong happened, no problems > 3) More importantly will it happen on Jessie->Stretch as climbing up > to dismantle the local net is hard (I have a balance issue) or is > there a way of testing before rebooting? > Perhaps you make a copy to virtual machine or another computer and try it there first changes are usually not applied directly to productive systems, you do it on a test system first and take notes - best write step by step guide further more read carefully the upgrade instructions provided by debian. If you stick to them, you usually won't have problems. regards
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web