Pi has arrived - 2 newbie questions

[texy]

Well it arrived and its booted ok first time with the Debian image. Its picked up the correct time and date so it has access to the net, however when I go into
Midori and I try and access a webpage a 'cannot resolve hostname' message occurs.
Also how can i prove that sound is working through the HDMI cable? I,ve tried the Music Player app and pressed play on the 'cellule' track but i cant hear anything, even after
I un-mute the sound level, as it appears to be muted by default.
Note that the HDMI cable and network cable have been removed from my Xbox 360 so I know they work for both network and sound.

Cheers,
Texy

[texy]

Maybe the sound problem is that the track isn't actually playing? I attached headphones to the jack and can't hear anything there either. There is no indication that the track is playing on the app - isn't the timeline at the top supposed to move??????
Texy

[grumpyoldgit]

It's useful to work out where the problem is.

Go into terminal and see if you can ping the google dns servers.
ping 8.8.8.8

Then ping the Raspberry Pi site.
ping www.raspberrypi.org

If you get a response from the first but not the second then dns is likely to be your issue.

On the sound issue try this.

http://elinux.org/R-Pi_Troubleshooting# ... plications

By the way, you are unlikely to hear anything plugging headphones into the jack socket as the signal is not strong enough. you need proper powered speakers.

[rasbeer]

It's useful to work out where the problem is.
By the way, you are unlikely to hear anything plugging headphones into the jack socket as the signal is not strong enough. you need proper powered speakers.

Several people have reported headphones working ok (perhaps the in-ear type need less power?)

[grumpyoldgit]

It's useful to work out where the problem is.
By the way, you are unlikely to hear anything plugging headphones into the jack socket as the signal is not strong enough. you need proper powered speakers.

Several people have reported headphones working ok (perhaps the in-ear type need less power?)

Thanks. I haven't linked my Pi up for sound yet, so that is interesting. I was just going on the reports of others.

[texy]

OK, some more info.
I rebooted the Pi and saw the ip was DHCP'ed to address 192.168.0.8, so I pinged my router and got a good response. I could also ping my windoz laptop on the same network.
So after I type startx, thats when the network is lost - when I ping from LXTerminal, I get an 'unreachable' message.
Like I said, its a linux newbie situation I,m sure - something needs to be set to enable the network in X Windows.
Thanks for the help so far

Texy

[grumpyoldgit]

Pinging your router only proves you can access your internal network, not that you can access the outside world.
You need to satisfy yourself that you can ping external addresses.

Also, when you go into startx, what ip address does your pi have? Run ifconfig.

[texy]

True. But it is getting the time from somewhere.
After a long pause,
inet addr:127.0.0.1

Texy

[grumpyoldgit]

You still haven't pinged an external address.

[texy]

Ok. Logged off lxde tried to ping the router and no go. Switch off and back on again and I can ping the router, 8.8.8.8 and the pi site.

Seems like lxde is breaking summat.
Texy

[bredman]

In answer to your questions about sound...

To test if sound is working properly, see the instructions at http://elinux.org/R-Pi_Troubleshooting#Sound

[texy]

Part of the problem is not knowing if the track is playing. When I hit the play button nothing happens - surely the timeline should be moving? I guess I could hook up a powered amp to the analogue o/p.
Texy

[texy]

Some progress with the sound at least. I changed the config.txt file to have hdmi_driver = 2. That made no apparent difference to sound or display.
However on the troubleshooting wiki page as outlined above, I tried

Code: Select all

 cd /opt/vc/src/hello_pi/hello_audio
 make
 ./hello_audio.bin

and then

Code: Select all

 ./hello_audio.bin 1

..which does produce sound from the TV!
However I also thought'd I,d give this a go

Code: Select all

 sudo modprobe snd_bcm2835
 sudo amixer cset numid=3 2

...but the amixer command is not recognised by Debian.

Texy

[grumpyoldgit]

I've just this minute been playing about with the sound advice as I wanted to get sound on Doom. I had also noticed, like you, that pressing play on that music file in LXMusic did nothing.

The first set of instructions does nothing and the make command exits with an error message.

However, sudo modprobe snd_bcm2835 before I go into startx gives me sound in Doom and also allows me to play that music file, which is a but Techno!

I don't have speakers set up yet so am using ear buds. The volume is O.K. Just a few pips and crackles now and again.

What I would like to do is set that command up so it activates on boot. It's not clear to me whether that is required.

[texy]

I have now also sorted out the network issue - well kind of. What I didn't mention was that to get from my router to the Pi
(and hard wired laptop if i want), I need to go through a pair of homeplugs. These have been working fine for the xbox, also under the tv, surprise surprise, and also when I connect to my laptop as previously stated (I think). So why the Pi doesn't like it once in lxde, who knows. Anyway
to rule things out I moved the pi and hard connected it to the router, set up tightvnc and ran it from my laptop. The Pi now browses website fine (well as fast as the little thing can manage!). So I need another plan

Texy

[Snowpuddles]

I also am having the problem of losing internet when starting lxde. Any ideas?

[dom]

@texy
sudo apt-get install alsa-utils
shoud get you amixer. (I've added this info to troubleshooting wiki).

@Snowpuddles
Sounds like a power supply issue.

[texy]

Thanks Dom. Actually I now think maybe my problem is also hardware related. I have 2 1 Amp Apple PSU's of different types and also a cheap powered hub. The problem is probably due to my usb keyboard which is rated at 110mA. I think a combination of the cheap hub and the current sapping keyboard is too blame. If I go headless, and vnc in to the pi, all is well with browsing etc.

Cheers,
Texy