I've just installed debian wheezy and things are pretty much working in the multimedia area. In particular, CDs and DVDs are playing. But I've run into troubles with mp4 files. VLC plays them, but the audio is terrible and the video is a bit worse than I remember in squeeze. Totem does nothing at all with these files. I presume there's some library out there that I need to load, but I don't know which one. I've added
deb http://www.deb-multimedia.org wheezy main non-free
to /etc/apt/sources.list![Mplayer Mplayer](/uploads/1/2/5/8/125849369/681705177.jpg)
and the following packages are present:
gstreamer0.10-ffmpeg/wheezy uptodate 1:0.10.13-0.2
gstreamer0.10-fluendo-mp3/wheezy uptodate 0.10.15.debian-1
gstreamer0.10-gconf/wheezy uptodate 0.10.31-3
gstreamer0.10-nice/wheezy uptodate 0.1.2-1
gstreamer0.10-plugins-bad/wheezy uptodate 0.10.23-6
gstreamer0.10-plugins-base/wheezy uptodate 0.10.36-1
gstreamer0.10-plugins-good/wheezy uptodate 0.10.31-3
gstreamer0.10-plugins-really-bad/wheezy uptodate 0.10.23-0.0
gstreamer0.10-plugins-ugly/wheezy uptodate 0.10.19-2+b2
gstreamer0.10-pulseaudio/wheezy uptodate 0.10.31-3
gstreamer0.10-x/wheezy uptodate 0.10.36-1
libgstreamer0.10-0/wheezy uptodate 0.10.36-1
Something seems to have changed between squeeze and wheezy. Any clues what?
-- al
![Debian install kernel source Debian install kernel source](/uploads/1/2/5/8/125849369/280680694.jpg)
Upgrade the kernel. Deb wheezy-updates main contrib non-free deb-src. Install newer kernel after upgrade to Jessie. Mplayer fails to play files - mplayer error while loading shared libraries: libdvdnavmini.so.4:. How to Install Mplayer and Multimedia Codecs (libdvdcss2,w32codecs,w64codecs) on Ubuntu 13.04 Raring Ringtail. In this article I will show you how to install MPlayer and the multimedia codecs needed for watching movies on Ubuntu 13.04 Raring Ringtail. Install Linux Kernel 3.8.6 on Ubuntu, Debian and Linux Mint Operating Systems.
deb http://www.deb-multimedia.org wheezy main non-free
to /etc/apt/sources.list
![Mplayer Mplayer](/uploads/1/2/5/8/125849369/681705177.jpg)
and the following packages are present:
gstreamer0.10-ffmpeg/wheezy uptodate 1:0.10.13-0.2
gstreamer0.10-fluendo-mp3/wheezy uptodate 0.10.15.debian-1
gstreamer0.10-gconf/wheezy uptodate 0.10.31-3
gstreamer0.10-nice/wheezy uptodate 0.1.2-1
gstreamer0.10-plugins-bad/wheezy uptodate 0.10.23-6
gstreamer0.10-plugins-base/wheezy uptodate 0.10.36-1
gstreamer0.10-plugins-good/wheezy uptodate 0.10.31-3
gstreamer0.10-plugins-really-bad/wheezy uptodate 0.10.23-0.0
gstreamer0.10-plugins-ugly/wheezy uptodate 0.10.19-2+b2
gstreamer0.10-pulseaudio/wheezy uptodate 0.10.31-3
gstreamer0.10-x/wheezy uptodate 0.10.36-1
libgstreamer0.10-0/wheezy uptodate 0.10.36-1
Something seems to have changed between squeeze and wheezy. Any clues what?
-- al
We suggest that before upgrading you also read the information in Chapter 5, Issues to be aware of for jessie. That chapter covers potential issues which are not directlyrelated to the upgrade process but could still be important to know aboutbefore you begin.
4.1.1. Back up any data or configuration information
Before upgrading your system, it is strongly recommended that you make a fullbackup, or at least back up any data or configuration information you can'tafford to lose. The upgrade tools and process are quite reliable, but ahardware failure in the middle of an upgrade could result in a severely damagedsystem.
The main things you'll want to back up are the contents of
/etc
, /var/lib/dpkg
,/var/lib/apt/extended_states
and the output ofdpkg --get-selections '*'
(the quotes are important). Ifyou use aptitude to manage packages on your system, youwill also want to back up /var/lib/aptitude/pkgstates
.The upgrade process itself does not modify anything in the
/home
directory. However, some applications (e.g. partsof the Mozilla suite, and the GNOME and KDE desktop environments) are known tooverwrite existing user settings with new defaults when a new version of theapplication is first started by a user. As a precaution, you may want to makea backup of the hidden files and directories (“dotfiles”) in users' homedirectories. This backup may help to restore or recreate the old settings.You may also want to inform users about this.Any package installation operation must be run with superuser privileges, soeither log in as
root
or use su or sudo togain the necessary access rights.The upgrade has a few preconditions; you should check them before actuallyexecuting the upgrade.
It's wise to inform all users in advance of any upgrades you're planning,although users accessing your system via an ssh connectionshould notice little during the upgrade, and should be able to continueworking.
If you wish to take extra precautions, back up or unmount the
/home
partition before upgrading.You will have to do a kernel upgrade when upgrading to jessie, so areboot will be necessary. Typically, this will be done after the upgrade is finished.
There might be services that are offered by the system which are associated with packagesthat will be included in the upgrade. If this is the case, please note that,during the upgrade, these services will be stopped while their associated packages are being replaced and configured. During this time, these services will not beavailable.
The precise downtime for these services will vary depending on the number ofpackages being upgraded in the system, and it also includes the time the systemadministrator spends answering any configuration questions from packageupgrades. Notice that if the upgrade process is left unattended andthe system requests input during the upgrade there is a highpossibility of services being unavailable[1] for a significant period of time.
If the system being upgraded provides critical services for your users or thenetwork[2], you can reduce the downtime ifyou do a minimal system upgrade, as described in Section 4.4.4, “Minimal system upgrade”, followed by a kernel upgrade and reboot,and then upgrade the packages associated with yourcritical services. Upgrade these packages prior to doing the full upgradedescribed in Section 4.4.5, “Upgrading the system”. This way you can ensure thatthese critical services are running and available through the full upgradeprocess, and their downtime is reduced.
Although Debian tries to ensure that your system stays bootable at all times,there is always a chance that you may experience problemsrebooting your system after the upgrade. Known potential issues aredocumented in this and the next chapters of these Release Notes.
For this reason it makes sense to ensure that you will be able to recover ifyour system should fail to reboot or, for remotely managed systems, fail tobring up networking.
If you are upgrading remotely via an ssh link it isrecommended that you take the necessary precautions to be able to access theserver through a remote serial terminal. There is a chance that, afterupgrading the kernel and rebooting, you will have to fix the systemconfiguration through a local console. Also, if the system is rebootedaccidentally in the middle of an upgrade there is a chance you will need torecover using a local console.
Generally we recommend using the rescuemode of the jessie Debian Installer. The advantage of using theinstaller is that you can choose between its many methods to find onethat best suits your situation. For more information, please consult thesection “Recovering a Broken System” in chapter 8 of the InstallationGuide and the Debian Installer FAQ.
If that fails, you will need an alternative way to boot your system so you canaccess and repair it. One option is to use a special rescue image or a Linuxlive CD. After booting from that, you should be able to mount your root filesystem and
chroot
into it to investigate and fix theproblem.The
initramfs-tools
package includes a debugshell[3] in theinitrds it generates. If for example the initrd is unable to mount your rootfile system, you will be dropped into this debug shell which has basic commandsavailable to help trace the problem and possibly fix it.Basic things to check are: presence of correct device files in
/dev
; what modules are loaded (cat/proc/modules
); output of dmesg for errors loadingdrivers. The output of dmesg will also show what devicefiles have been assigned to which disks; you should check that against theoutput of echo $ROOT
to make sure that the root file systemis on the expected device.If you do manage to fix the problem, typing
exit
will quitthe debug shell and continue the boot process at the point it failed. Ofcourse you will also need to fix the underlying problem and regenerate theinitrd so the next boot won't fail again. If the boot fails under systemd, it is possible to obtain a debug root shell by changing the kernel command line. If the basic boot succeeds, but some services fail to start, it may be useful to add
systemd.unit=rescue.target
to the kernel parameters. Otherwise, the kernel parameter
systemd.unit=emergency.target
will provide you with a root shell at the earliest possible point. However, this is done before mounting the root file system with read-write permissions. You will have to do that manually with: More information on debugging a broken boot under systemd can be found in the Diagnosing Boot Problems article.
If everything else fails, you might be able to boot via the old sysvinit system. This requires that
sysvinit
is still installed and the binary /lib/sysvinit/init
is included in your initramfs. If these requirements are met, add init=/lib/sysvinit/init
on the kernel command-line and it will boot with the sysvinit binary. The distribution upgrade should be done either locally from a textmode virtualconsole (or a directly connected serial terminal), or remotely via anssh link.
Important |
---|
If you are using some VPN services (such as tinc ) they might not be available throughout the upgrade process. Please see Section 4.1.3, “Prepare for downtime on services”. |
In order to gain extra safety margin when upgrading remotely, we suggest thatyou run upgrade processes in the virtual console provided by thescreen program, which enables safe reconnection and ensuresthe upgrade process is not interrupted even if the remote connection processfails.
Important |
---|
You should not upgrade using telnet, rlogin, rsh, or from an X session managed by xdm, gdm or kdm etc. on the machine you are upgrading. That is because each of those services may well be terminated during the upgrade, which can result in an inaccessible system that is only half-upgraded. Use of the GNOME application update-manager is strongly discouraged for upgrades to new releases, as this tool relies on the desktop session remaining active. |
![Debian install kernel source Debian install kernel source](/uploads/1/2/5/8/125849369/280680694.jpg)
Users of the watchdog daemon provided by the
micro-evtd
package should stop the daemon and disable the watchdog timer before the upgrade, to avoid a spurious reboot in the middle of the upgrade process: