But note that the command speaker-test seems only to like mono wav files, and seems not to play stereo wav files. The command aplay plays 2 channel stereo wav files in stereo sound without problem provided they last longer than the time it takes the TV to unmute and remute. Enter the command 'alsamixer' and use the control to check that the volume is up arrow keys and that the output is not muted M key.
To install support for sound, type the following from a command line from the command prompt before "startx" or in a terminal window. Next try:. By default output will be automatic hdmi if hdmi supports audio, otherwise analogue. You can force it with:. Also note that you may have to add your user to the 'audio' group to get permission to access the sound card.
Between December and February the standard raspbian wheezy distribution, and apt-get upgrade, included pulseaudio. Forum posts suggest that pulseaudio can break alsa. Whilst some members identify various workarounds, others find only removal of pulseaudio restores sound output. By default there are only a few hundred MB free in the 2 GB main partition, which can quickly fill up if you download files.
Also, installing some software may incorrectly create or modify a. Xauthority file in your home directory, causing startx to fail, according to this thread. Temporarily renaming, moving, or deleting that file may fix the problem. Notwithstanding the previous paragraph, omxplayer may be included in some versions of raspbian. It is a command line tool, and happily plays. Known issue with distro package as of 17th April - there's some missing boot config information.
Creating a suitable cmdline.
Out of the box, R-Pi graphics don't necessarily fill the whole screen. This is due to something called "Underscan", and it can be fixed easily. Making the R-Pi graphics fill the screen is a matter of experimenting with the numbers you put in the config. Change the numbers — try jumps of 5 or 10 at a time. Bigger negative numbers reduce the black borders so means less black border than The numbers do not all have to be the same; you can use this feature to centre the display on the screen.
This only affects the framebuffer e. You can make it apply to hardware layers with:. Follow the instructions in the section "Big black borders around small image on HD monitors", but use positive numbers for the overscan settings, for example.
This may be caused by loss of signal on long video cables. The signal level may be increased by changing a configuration parameter. Value 1 is used for very short cables, value 7 is used for very long cables. At your own risk, you can go up to 11, but risk frying a sensitive monitor. See Troubleshooting Power Problems. If you have the Rasbian Wheezy image recommended then try. For a quicker way to force wheezy into booting in safe mode, which doesn't need editing config.
Be very careful not to connect any other pins, especially not pins 1 and 2 3V3 and 5V as doing so, with power on, will damage your PI! Otherwise, try adding the following line to the configuration file similar to interference case above. A similar problem has occured following the installation of Rasbian Wheezy image "wheezy-raspbian" - the hotplug signal appeared to be no longer detected when a HDMI 3 Port Switcher was in use for the Pi running from that image. An older, but updated and upgraded image still worked, as did a similar image on the other Pi connected to the switch, but, unless the above override was implemented, the Pi with the new image would only provide a HDMI display when directly connected to the monitor.
The same problem has re-occurred when using that wheezy image with a new in March "Model A" Pi.
Also try the following video options:. Some cheap HDMI cables do not implement the individual grounds and just have a common foil shield that's connected to the HDMI plug shells at both ends. You can tell if an HDMI cable implements the individual grounds by checking for continuity using an Ohmmeter or multimeter. Most TVs will show an image with that, but older PAL European televisions may display only back and white or no image.
To fix this:.
The input polyfuse may have tripped. It is self-resetting after it cools down and the polymer re-crystallizes, which can take several hours. Set the Pi aside and try again later. The GPIO pins connect directly into the core of the ARM processer, and are static-sensitive, so you should avoid touching the pins wherever possible. If you are carrying a static charge, for example by taking off an acrylic pullover, or walking across a nylon carpet, touching the GPIO pins could destroy your R-Pi, so always earth yourself before touching the pins or anything connected to them.
Si vous voulez, vous pouvez le ressouder, ou plus simplement ne pas en tenir compte. Quand vous essayez d'installer un paquet avec la commande sudo apt-get install xxxx vous pouvez rencontrer l'erreur. If you think you have a problem with your power supply, it is a good idea to check the actual voltage on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board to facilitate voltage measurements. You should see a voltage between 4.
Anything outside this range indicates that you have a problem with your power supply or your power cable. If you have not used a multimeter before, see these [ basic instructions ]. Note: Even if the multimeter shows the correct voltage, you may have some power supply problems. A multimeter only displays the average voltage. If there are very short-lived dips or spikes in the voltage, these will not be shown by the multimeter.
It is best to measure voltage when Pi is busy. Try to use a basic one. Wifi dongles are also unlikely to work when directly connected. See also: Power Supply Problems. How to test the F3 polyfuse .
Les cookies sont désactivés
If the voltage is different by more than about 0. When polyfuses "blow" their resistance increases dramatically, there by limiting the voltage that can pass through them. If your power problem suddenly appeared after your board was known to be working fine, it is probable the fuse is just "blown" and will return to normal. Polyfuses recover from the tripped state to near their normal value in a few minutes, but do take some hours to fully recover so leave it unpowered and check it again in a little while. Also, on a related issue, do note that if you do not power the PI in the "official manner", that is through it's micro-USB port, but use any alternative way such as through the GPIO header, the test points TP1 and TP2 , but also by back-powering it, you are actually bypassing the PI's input polyfuse protection device!
Comment récupérer des données sur une carte SD endommagée
This can have extreme consequences if ever you manage to put more than 6V on the PI, even for a very short period. As this causes the overvoltage device D17 on the the PI to trigger and short the 5V supply!
Without the polyfuse limiting the current through D17, it will burn out, probably melting the PI's enclosure with it, if you have any and possibly causing a fire-hazard. It will probably also create a permanent short of the 5V supply! So be warned, and if you use back power make sure your hub or its PSU has a fuse to prevent this from happening.
If not, add your own fuse. Pour Ver carte. From eLinux. Jump to: navigation , search. Retour vers le Hub. Multi-meter lead placement for testing the Raspberry Pi F3 Polyfuse. Raspberry Pi.