Raspberry Pi Forums

Hi Guys,
Can I ask one or more of you more knowledgeable guys to take a look at this thread please?: -

http://www.raspberrypi.org/phpBB3/viewt ... 75#p464375

I have tried everything I and another member can think of to persuade the USB ports on my brand new Pi to cooperate with various USB wired and wireless KBs and mice, all without success. Before I request a RTM from the seller, RS-Online, can I ask if any of you have any idea if it is me that might have done something wrong, to avoid having the same problem with any replacement.
Thanks for any responses,
Dave.

try reflashing sd card and make sure mouse / keyboard are plugged in b4 loading operating system wont work as plug and play

Sometimes this is caused by a not working LAN9512 chip, its easy enough to check if its working though, just plug in a ethernet cable connected to any kind of Ethernet device into the PI's Ethernet port. Several LED's should go on to signal a connection, if not the LAN9512 chip isn't working.
The cause is often that the 25MHz crystal X1 on the bottom side isn't oscillating, sometimes it helps to re-solder it. Just trying to lightly tap on it might also be enough to get it going, if this works it will generally keep working.

Hi mahjongg,
I think you may well have put you metaphorical finger on it. I always connect it to a 10/100 LAN switch (with all the other connections) and the only LEDs that light are the PWR and the ACT, the former permanently red and the ACT mainly red but briefly in the power up cycle flashes green before settling on red.
If I can identify the LA N9512 chip I'll try tapping it gently with a lump hammer to see if I can wake it from it's slumbers.
Thanks very much for your input.
Dave.
Quick update: -
A lump hammer proved ineffective but a few hearty swings of a sledge hammer seems to have had some effect . Seriously, I could not identify the relevant chip so with the PCB out of it's case but powered up and with HDMI, LAN and power connected I gently tapped everything I could see with my finger nail and, surprise, surprise, tapping the USB connection suddenly brought all the LEDs on, albeit the ACT on only flashing very briefly, green. PWR was solid red, the FDX and LNK were solid green and the 100 solid amber. I will power and connect everything properly a little later, including UBS, and see if I can persuade the cursor to get active.
Thanks again,
Dave.

DaveK wrote:If I can identify the LA N9512 chip I'll try tapping it gently with a lump hammer to see if I can wake it from it's slumbers

No, mahjongg said to try tapping the crystal called X1 (biggish metal thing) on the underside of the board. Tapping the LAN9512 chip may help if it has a loose connection, but that is less likely.

The LAN chip is the black square behind the USB socket. The crystal is on the other side of the board between that chip and the network socket.

Thanks rpdom for your clarification but please see my edit above.
FWIW I can only see 2 (comparatively) biggish metal things underneath, neither of which I could identify as the component in question.
Dave.

The XTAL timing cystals are clearly marked as X1 and X2 on the board, the X1 chip should have 25.000 written on the biggish metal thingy (25MHz).

Richard S.

Hi Guys,
Update: -
I've got it working fine on OpenElec XMBC and been listening to a surprisingly good SQ Classic fm. However the main reason I wanted to faff around with the Pi was to give RaspyFi a listen. Unfortunately I cannot get past the opening DOS-like screen with the large 'icon' of a pair of headphones with RaspyFi in the middle and the very last line that states "switching to governor ondemand" followed by a flashing cursor. It has not got to the point of recognising the USB mouse or KB, or shown a GUI.
Any ideas as to what I might be doing wrong, given that OpenElec XMBC works fine when I swap that card into the slot?
TIA,
Dave.

keyboard mouse (any USB device) problems are mostly an indication on an insufficiently powered PI.
or as I said before a non running 25MHZ xtal.

Hi y'all ,
I am making slow progress and as the problem seems now to be limited to RaspyFi I have started a thread here: -

http://www.raspyfi.com/forum/raspyfi-in ... ase/#p2041

which is making some progress, so thanks for your past input and any future ones you might make.
Cheers,
Dave.