install:upgrade-up7 [LMDE journeys]

A PCRE internal error occured. This might be caused by a faulty plugin

====== Differences ====== This shows you the differences between two versions of the page.

--- install:upgrade-up7 [2013/12/06 04:59]
admin [Time for a Backup?]
+++ install:upgrade-up7 [2013/12/16 09:34] (current)
admin [Need Some Fixes?]
@@ Line 39: / Line 39: @@
 At that stage, the restart process didn't went smoothly, it got stuck. The screen turned to command line indicating: "The system is going down for reboot NOW", and the machine got stuck there. I waited a few minutes to make sure it wasn't silently in the process of shutting down, but nothing happened.
-So I decided to power cycle my machine. It restarted and rEFInd happily showed me "Tux", the penguin, as a startup option. Clicking on it brought me to the GRUB bootloader selection. All seemed well, until the screen turned black with the Linux Mint logo, only the first three dots blinked before they stopped... Once again I waited a few minutes, but nothing happened: power cycle again !
+If you encounter this kind of trouble, reading the [[tricks:forced-restart|Forced Restart]] article of this wiki might be of interest...
-This time I selected the "recovery mode" in the GRUB menu, so I could see the command line output, and it got stuck again after about 12 seconds, I went through this 3 times to make sure it wasn't a temporary problem :-/
-From previous experience, I discovered that, sometimes, after a system crash and a power cycle restart was forced, turning off the computer - unplugging it - removing the battery - keeping the power button down for a few seconds (on a MacBook laptop) - replugging everything and starting it again did the trick!\\
-I still don't know exactly what is going on at that level, but I guess that involves some sort of PRAM information or the like, that prevents the computer from starting up correctly. Maybe I'll get some time to dig that matter someday.
-Well, after all that "hardware reset" stuff, everything was back on track and startup went on as expected...
 ===== Need Some Fixes? =====
 During the upgrade process you might have received some warnings like the one here below:
-<WRAP hi>This system is currently running Linux 3.2.0-4-amd64 and you are installing Linux 3.10-2-amd64.  In the new version some of the drivers used on this system may require additional firmware files:
+<WRAP center box 85%>This system is currently running Linux 3.2.0-4-amd64 and you are installing Linux 3.10-2-amd64.  In the new version some of the drivers used on this system may require additional firmware files:
 b43: b43/ucode9.fw, b43/ucode5.fw, b43/ucode16_mimo.fw, b43/ucode15.fw, b43/ucode14.fw, b43/ucode13.fw, b43/ucode11.fw
-Most firmware files are not included in the system because they do not conform to the Debian Free Software Guidelines. You may need to reconfigure the package manager to include the contrib and non-free sections of the package archive before you can install these firmware files.</WRAP>\\
+Most firmware files are not included in the system because they do not conform to the Debian Free Software Guidelines. You may need to reconfigure the package manager to include the contrib and non-free sections of the package archive before you can install these firmware files.</WRAP>
 Also, if you followed the command line output during the upgrade process you might have noticed some warnings or errors like these ones:
-<WRAP hi>Not starting fancontrol; run pwmconfig first. ...</WRAP>\\
+<WRAP center box 85%>Not starting fancontrol; run pwmconfig first. ...</WRAP>
 Or even something like:
-<WRAP hi>Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103: Having multiple values in <test> isn't supported and may not work as expected</WRAP>\\
+<WRAP center box 85%>Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103: Having multiple values in <test> isn't supported and may not work as expected</WRAP>
-If that is the case, you might be interested in consulting the [[install:fixes:start|Base Fixes]] section of the site.
+If that is the case, you might be interested in consulting the [[install:fixes:start|Base Fixes]] section of this wiki.
-===== Time for a Backup? =====
+===== Time for a Backup! =====
 Well, you now have a shiny new install of your LMDE system. Polished, clean and shiny!
 You're up to the next step on the path: installing applications and creating documents... But, thinking of all the distance you've already traveled, what if you were to make a mistake, or lightning strikes... well that doesn't happen, OK...  But coffee spills, right?\\
 Would you spend all this time resuming to the point you've already reached?\\
+**NO!**\\
+It is time to think about a backup.
-**NO!**
+Of course this is totally optional, and won't hinder your experience in case you don't do it. But trust me, one day or the other, you'll be happy you did choose to regularly backup your system.
-It is time to think about a backup.
+If you're interested in knowing how to preserve your data integrity, check out the [[applications:backup|Backups]] section of this wiki.
-Of course this is totally optional, and won't hinder your experience in case you don't do it. But trust me, one day or the other, you'll be happy you did choose to regularly backup your system.
+===== Additions =====
+Even when your installation and upgrade went without a glitch, and although Linux Mint comes packed with most applications to satisfy your basic requirements, it is quite obvious that you'll need to add some packages and/or applications.
-If you're interested in knowing how to preserve your data, check out the [[applications:backup|Backup]] section of this wiki.
+To consult a list of the additions I installed shortly after having completed the installation process consult the [[install:additions|Base Additions]] section of this wiki.