Where is the basic troubleshooting information at?
Assuming that a newbie is trying to get his Pi to boot, the latest stable version of "2012-07-15-wheeze-raspbian", what is the minimum he has to have connected in order for the green "OK" LED to come on? Does a Ethernet cable with Internet access have to be connected? Do you have to a keyboard connected? Do you have to have a mouse connected? Is the bug that was causing the majority of the SD card problems fixed in the 2012-07-15 released, or is it just fixed in release candidate 4?
I have two new Pi's, and I have yet to get either of them to boot. I have tried two PSU (5v, 1A, Apple and 5v, 2A, Ktec Seagate) and three different SD cards. The green OK LED blinks as if the processor is reading and executing instructions, but I have yet to get text on the screen via HDMI to DVI cable, and I have yet to get the OK LED to stay on.
Any answers and or suggestions would be appricated.
Re: Basic Troubleshooting
It sounds like your Pi is functioning fine, it just isn't detecting an monitor (for whatever reason) on the other end of the DVI cable.rayfranco wrote:Where is the basic troubleshooting information at?
Assuming that a newbie is trying to get his Pi to boot, the latest stable version of "2012-07-15-wheeze-raspbian", what is the minimum he has to have connected in order for the green "OK" LED to come on? Does a Ethernet cable with Internet access have to be connected? Do you have to a keyboard connected? Do you have to have a mouse connected? Is the bug that was causing the majority of the SD card problems fixed in the 2012-07-15 released, or is it just fixed in release candidate 4?
I have two new Pi's, and I have yet to get either of them to boot. I have tried two PSU (5v, 1A, Apple and 5v, 2A, Ktec Seagate) and three different SD cards. The green OK LED blinks as if the processor is reading and executing instructions, but I have yet to get text on the screen via HDMI to DVI cable, and I have yet to get the OK LED to stay on.
Any answers and or suggestions would be appricated.
If I were you, I would:
- Stick the SD card in a PC
Open up the FAT32 (or only) partition
Edit/create the file "config.txt"
Add the lineSaveCode: Select all
hdmi_force_hotplug=1
{sig} Setup: Original version Raspberry Pi (B, rev1, 256MB), Dell 2001FP monitor (1600x1200), 8GB Class 4 SD Card with Raspbian and XBMC, DD-WRT wireless bridge
Re: Basic Troubleshooting
Now I see what I have got myself into!
From: http://elinux.org/RPi_Noob_Guides_for_W ... 16-18_beta
"Issues with new image
I'm posting this as a heads up I just downloaded the torrent of 201-07-15-wheezy-raspbian off of a torrent checksum ok and it appears to install to SD.
On a clean first time boot it appears not to detect the live (yes it is switched on) HDMI it's on and playing via a Blind Login using putty for an ssh connection so the image works and it appears to be good for composite but it appears the HDMI is not playing for the first time out of the SD card.
Once I have run raspi-config off of a putty blind login or composite screen it fires no problem both to command line and to startx if thats chosen from the raspi-config but oly on re-boot HDMI is still not live after a shutdown.
The earlier version was working and I do know my way round this as can be seen from the noob writeups contained in the links on this page.
Obviously I will have to do some more testing but I thought this had to be worth a heads up on the off chance it's not something I'm doing.
Ok done an additional test confirmation the composite fires up just as it did for the earlier version going directly to the raspi-config menu but it appears to be only playing on the composite output not hdmi unless you reboot or engage the startx desktop option in raspi-config.
The previous version went to composite if you did not have HDMI plugged in.
Note it works once you have chosen the Desktop option but if you can't see a command line screen you can't view the raspi-config script to activate it.
I've found something else once you have run raspi-config and done a reboot it plays ok if you reboot however if you shutdown it won't restart to HDMI.
But it re-starts and if you blind login using putty and sudo reboot it then starts with a live HDMI screen (go figure) it also still has the microscopic font. "
This definately is not something for a newbie!!!
I tried editing the config.txt file and booting in the safe mode, but that didn't work either.
As for the blind login, I have 3 PC, 3 NAS, 3 printers, 2 iPads, 2 iPhone, 3 Switches and 2 Wirelss Access Points. Does anybody want to try guessing the IP address?
The only thing I think of is go back to the 2012-06-18 beta and see if it works, or I could wait 6 months and maybe there will be a stable Raspbian OS.
From: http://elinux.org/RPi_Noob_Guides_for_W ... 16-18_beta
"Issues with new image
I'm posting this as a heads up I just downloaded the torrent of 201-07-15-wheezy-raspbian off of a torrent checksum ok and it appears to install to SD.
On a clean first time boot it appears not to detect the live (yes it is switched on) HDMI it's on and playing via a Blind Login using putty for an ssh connection so the image works and it appears to be good for composite but it appears the HDMI is not playing for the first time out of the SD card.
Once I have run raspi-config off of a putty blind login or composite screen it fires no problem both to command line and to startx if thats chosen from the raspi-config but oly on re-boot HDMI is still not live after a shutdown.
The earlier version was working and I do know my way round this as can be seen from the noob writeups contained in the links on this page.
Obviously I will have to do some more testing but I thought this had to be worth a heads up on the off chance it's not something I'm doing.
Ok done an additional test confirmation the composite fires up just as it did for the earlier version going directly to the raspi-config menu but it appears to be only playing on the composite output not hdmi unless you reboot or engage the startx desktop option in raspi-config.
The previous version went to composite if you did not have HDMI plugged in.
Note it works once you have chosen the Desktop option but if you can't see a command line screen you can't view the raspi-config script to activate it.
I've found something else once you have run raspi-config and done a reboot it plays ok if you reboot however if you shutdown it won't restart to HDMI.
But it re-starts and if you blind login using putty and sudo reboot it then starts with a live HDMI screen (go figure) it also still has the microscopic font. "
This definately is not something for a newbie!!!
I tried editing the config.txt file and booting in the safe mode, but that didn't work either.
As for the blind login, I have 3 PC, 3 NAS, 3 printers, 2 iPads, 2 iPhone, 3 Switches and 2 Wirelss Access Points. Does anybody want to try guessing the IP address?
The only thing I think of is go back to the 2012-06-18 beta and see if it works, or I could wait 6 months and maybe there will be a stable Raspbian OS.
Re: Basic Troubleshooting
Sorry, guys if I let my frustrations show. Both of my Pi's work as advertised. I didn't understand, and I am not sure I still understand the "OK" LED. I was looking for it to stay continueously "on" after a successful boot.
The problem with my Dell 1901FP moitor was that I had to manually set it up to look for a digital input rather than an analog input.
My day did not start off good. I had LED's blinking on the Pi, then nothing. I switched PSU and the LED's started blinking again. Later, nothing. I switched to a third PSU, and nothing. After two hours of pulling my hair out, I went to Walmart and purchased a new PSU cable. That solved the first problem, but it pretty much ruined my mood for the day. Well, it was it long day, but it did end good with both Pi's working as avertised.
The problem with my Dell 1901FP moitor was that I had to manually set it up to look for a digital input rather than an analog input.
My day did not start off good. I had LED's blinking on the Pi, then nothing. I switched PSU and the LED's started blinking again. Later, nothing. I switched to a third PSU, and nothing. After two hours of pulling my hair out, I went to Walmart and purchased a new PSU cable. That solved the first problem, but it pretty much ruined my mood for the day. Well, it was it long day, but it did end good with both Pi's working as avertised.
Re: Basic Troubleshooting
Nice to see that you fixed your problem.rayfranco wrote:Where is the basic troubleshooting information at?
But if anybody else needs a trouble shooting guide, please check the wiki
http://elinux.org/R-Pi_Troubleshooting