cutterjohn
Posts: 62
Joined: Tue Jul 24, 2012 9:55 pm

Re: Who is in the 1GHz Club?

Sat Sep 29, 2012 1:51 pm

wallarug wrote:The idea of the Raspberry Pi was NOT to make a small, powerful and portable computer. It was to make a cheap computer that kids could mess around with and if it broke, then they could get another one. If they were at your price: $50/$60 - then it would not be ideal for a parent to buy another one as easily.
Price difference of two RPi's @ $25/$35 is much different to $50/$60. Even if the compromise is computing power.
$50/60 v. $25/35 is just not that big of a step to justify the ARM11/RAM compromise to me. This is like quibbling over the $0.95 candybar v. the $0.75 not very good one.

...and more to the point more of the cost is likely from the addons, esp. if you plan to have many USB peripherals as a decent powered hubs seem to start @ $20 and even then that seems to mostly be bog standard 500mA max/port ones... already with this you're up to about 70% of the cost of the current model b and 80% of the cost of the A, and from there we just add on depending upon what cables/etc. one already has available. Even I ended up buying a powered hub as for years now all of my notebooks and desktops have oodles of USB ports. I also had to buy some HDMI cables and adapters but I bought these just before the rpi for the allwinner sticks(ease of use although they could easily have plugged directly into the HDMI port of the TV) so add on another $10 there. Oh, and lest we forget: a case. What's the cheapest case you've seen so far? Well lets just add another $10, look I'm already at $40, so the $35 cheap computer is now a $75 computer. I give up though, cling to the $25 fairy tale like it's some sort of mystical mantra and any other number just wouldn't work... Some of you people are just WAY to focused on $25.

Ah... the 2500MHz core thing... well I wrote that post under lxde + chromium which was almost unbearably sluggish... (224/32 split 100M swap ... I've upped swap another 100M now to 200M but I've yet to try lxde again... not expecting much though...)

(Had to remove some quotings, hope that I got everything correctly.)

shuckle
Posts: 565
Joined: Sun Aug 26, 2012 11:49 am
Location: Finland

Re: Who is in the 1GHz Club?

Sat Sep 29, 2012 1:58 pm

I have now three pis. They are all used in headless mode and attached to usb devices (weather station, kamera). no extra costs. At least for me this is then 100$ compared to your 180$, which is big difference.

cutterjohn
Posts: 62
Joined: Tue Jul 24, 2012 9:55 pm

Re: Who is in the 1GHz Club?

Sat Sep 29, 2012 2:13 pm

shuckle wrote:I have now three pis. They are all used in headless mode and attached to usb devices (weather station, kamera). no extra costs. At least for me this is then 100$ compared to your 180$, which is big difference.
This is going WAY OT, so this'll be my last comment.

yes you're right, running headless and you already have everything that you needed fine. I almost brought that up in the above reply, but opted not to as that is likely to not be the general case. Also in your case computing power is not a problem. It all depends upon what you want to use it for, however IF you're staying to their cheap GP computer then an alternative to current mainstream linux apps needs to be found(simply changing window managers, etc. won't cut it if you're running GTK/Qt apps on top of it).

i.e. It's very nice for you to already have everything there that you want although I suspect for many that is not the case which is why I also didn't mention well you could build your own housing/case/etc.

Now back to the 1GHz topic please as this is a pointless and endless debate.

User avatar
wallarug
Posts: 460
Joined: Mon May 14, 2012 8:21 am
Location: Sydney, Australia

Re: Who is in the 1GHz Club?

Sun Sep 30, 2012 1:35 am

shuckle wrote:I have now three pis. They are all used in headless mode and attached to usb devices (weather station, kamera). no extra costs. At least for me this is then 100$ compared to your 180$, which is big difference.
That is what I was trying to explain to @CutterJohn before. He is looking at the cost of single units. You have to be thinking about the multiple units...which is what I was saying before.
Price difference of two RPi's @ $25/$35 is much different to $50/$60. Even if the compromise is computing power.

bwieck
Posts: 4
Joined: Mon Sep 24, 2012 2:21 am

Re: Who is in the 1GHz Club?

Sun Sep 30, 2012 10:24 pm

I clocked my RPi REV0002 since 2 days @ 950MHz and it seems to run fine. No Kernel exeptions..
While i installed some pakets i noticed that there are many entries in Syslog like this:

Code: Select all

raspberrypi kernel: [ 4097.274561] mmc0: final write to SD card still running
raspberrypi kernel: [ 4107.145704] mmc0: Timeout waiting for hardware interrupt - cmd12.
raspberrypi kernel: [ 4107.146889] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x900
This ends up that some files that DPKG or APT needs are damaged while installing packages.
Seems to be a problem with the SD-Card itself but the card is not defective.
If i set clocking to 700MHz or 800MHz then all things work fine.

My Setup:
RPi Hardware REV0002 powered by 3A-PSU @ 5,05 Volts, Voltage across testpoints TP1 and TP2 are 4,87V
SD-Card is SanDisk SDHC Card 4GB

cutterjohn
Posts: 62
Joined: Tue Jul 24, 2012 9:55 pm

Re: Who is in the 1GHz Club?

Sun Oct 07, 2012 3:27 pm

bwieck wrote:I clocked my RPi REV0002 since 2 days @ 950MHz and it seems to run fine. No Kernel exeptions..
While i installed some pakets i noticed that there are many entries in Syslog like this:

Code: Select all

raspberrypi kernel: [ 4097.274561] mmc0: final write to SD card still running
raspberrypi kernel: [ 4107.145704] mmc0: Timeout waiting for hardware interrupt - cmd12.
raspberrypi kernel: [ 4107.146889] mmcblk0: error -110 sending stop command, original cmd response 0x900, card status 0x900
This ends up that some files that DPKG or APT needs are damaged while installing packages.
Seems to be a problem with the SD-Card itself but the card is not defective.
If i set clocking to 700MHz or 800MHz then all things work fine.

My Setup:
RPi Hardware REV0002 powered by 3A-PSU @ 5,05 Volts, Voltage across testpoints TP1 and TP2 are 4,87V
SD-Card is SanDisk SDHC Card 4GB
Did you try lower sdram and core freqs? It MIGHT help...

User avatar
raspberrypiguy1
Posts: 379
Joined: Sun Sep 02, 2012 7:01 pm

Re: Who is in the 1GHz Club?

Sun Oct 07, 2012 3:50 pm

I got my Pi's CPU all the way up to 1100Mhz... Beat that! It ran stable for a couple of hours and performance on Quake 3 DRAMATICALLY improved!

The Raspberry Pi Guy ;)
Matt, The Raspberry Pi Guy YouTube channel, author of Learn Robotics with Raspberry Pi, available now: http://mybook.to/raspirobots, Computer Science & Electronics Undergraduate at The University of Edinburgh

User avatar
Mr.Dave
Posts: 148
Joined: Sat Jun 30, 2012 6:59 pm

Re: Who is in the 1GHz Club?

Sun Oct 07, 2012 4:28 pm

It's weird, I can OC my Pi higher if I use XBian, but with Raspbian/Wheezy, it crashes at the same level OC

User avatar
Jade
Posts: 17
Joined: Wed Dec 28, 2011 12:49 am
Location: Russia

Re: Who is in the 1GHz Club?

Mon Oct 08, 2012 1:50 am

Mine is perfectly stable at 1ghz, woo

rey
Posts: 38
Joined: Fri May 04, 2012 8:01 am

Re: Who is in the 1GHz Club?

Mon Oct 08, 2012 8:29 am

raspberrypiguy1 wrote:I got my Pi's CPU all the way up to 1100Mhz... Beat that! It ran stable for a couple of hours and performance on Quake 3 DRAMATICALLY improved!

The Raspberry Pi Guy ;)
I've done 1200 with overvolting before!

User avatar
wallarug
Posts: 460
Joined: Mon May 14, 2012 8:21 am
Location: Sydney, Australia

Re: Who is in the 1GHz Club?

Mon Oct 08, 2012 10:43 am

rey wrote:
raspberrypiguy1 wrote:I got my Pi's CPU all the way up to 1100Mhz... Beat that! It ran stable for a couple of hours and performance on Quake 3 DRAMATICALLY improved!

The Raspberry Pi Guy ;)
I've done 1200 with overvolting before!
What OS were you using?

rey
Posts: 38
Joined: Fri May 04, 2012 8:01 am

Re: Who is in the 1GHz Club?

Mon Oct 08, 2012 11:54 am

Raspbmc.

poing
Posts: 1132
Joined: Thu Mar 08, 2012 3:32 pm

Re: Who is in the 1GHz Club?

Mon Oct 08, 2012 12:11 pm

Mine works perfectly stable @ 950MHz but fails to boot @ 1 GHz. Didn't try a different PSU yet though.

simplesi
Posts: 2327
Joined: Fri Feb 24, 2012 6:19 pm
Location: Euxton, Lancashire, UK
Contact: Website

Re: Who is in the 1GHz Club?

Mon Oct 08, 2012 12:17 pm

I used to be in the club but after a couple of corrupt SD cards, I'm back in the land of plain 700MHz :(

Simon
Seeking help with Scratch and I/O stuff for Primary age children
http://cymplecy.wordpress.com/ @cymplecy on twitter

milhouse
Posts: 642
Joined: Mon Jan 16, 2012 12:59 pm

Re: Who is in the 1GHz Club?

Mon Oct 08, 2012 12:25 pm

I've given up boosting the core frequency due to SD card corruption, but can hit 1000 arm/500 sdram with +6 over_voltage, +4 over_voltage_sdram and current_limit_override enabled. Without current_limit_override the Pi would reboot at 950MHz (enabling it will void your warranty etc.).

bwieck
Posts: 4
Joined: Mon Sep 24, 2012 2:21 am

Re: Who is in the 1GHz Club?

Sat Oct 13, 2012 12:12 pm

It seems that i found out what the problem was.
I soldered a 100nF capacitor directly to the Power-Terminals at the SD-Slot as seen here
Image

and now my Raspi works fine and stable @ 900MHz :D
My actual config is:

arm_freq=900
core_freq=333
sdram_freq=450
over_voltage=2

Cloudcentric
Posts: 982
Joined: Fri Sep 14, 2012 9:13 am

Re: Who is in the 1GHz Club?

Sat Oct 13, 2012 1:42 pm

I have been using Raspbian for 4 weeks now and the overclock has caused no issues, using 192.ELF. The SD Card is a Transcend SD HC Class 6 8GB :shock:

arm_freq=1000
core_freq=500
sdram_freq=500
over_voltage=6
I know everything about nothing"

sdpenaloza
Posts: 4
Joined: Sat Oct 13, 2012 8:55 am

Re: Who is in the 1GHz Club?

Sat Oct 13, 2012 5:36 pm

Ironically for me on default 700Mhz was getting sd card corruption(used fsck to fix issues every startup), put it in turbo mode 1Ghz haven't had any problems since with sd card corruption :o . (128/128 mem split)

Kekule
Posts: 2
Joined: Fri Sep 28, 2012 10:33 pm

Re: Who is in the 1GHz Club?

Sat Oct 13, 2012 9:10 pm

sdpenaloza wrote:Ironically for me on default 700Mhz was getting sd card corruption(used fsck to fix issues every startup), put it in turbo mode 1Ghz haven't had any problems since with sd card corruption :o . (128/128 mem split)
hmmm, I think I have a sheet of those at work, and a Pi sitting on my desk.... curious.

simplesi
Posts: 2327
Joined: Fri Feb 24, 2012 6:19 pm
Location: Euxton, Lancashire, UK
Contact: Website

Re: Who is in the 1GHz Club?

Sat Oct 13, 2012 10:32 pm

put it in turbo mode 1Ghz haven't had any problems since with sd card corruption
its very hard to imagine that upping the clock speed improves the reliability of an RPi :)

I'd make a small wager that you've stopped doing something that was causing the problems :)

Simon
Seeking help with Scratch and I/O stuff for Primary age children
http://cymplecy.wordpress.com/ @cymplecy on twitter

Smada
Posts: 10
Joined: Sat Feb 04, 2012 9:08 pm

Re: Who is in the 1GHz Club?

Sat Oct 13, 2012 11:31 pm

milhouse wrote:
LenReinhart wrote:Mine is fine in turbo mode. ... It runs around 40 degrees C at 700MHz and it hasn't seen 50 at 1000MHz.
That's impressive, where do you live - the North Pole? ;-)

My Pi (with a small RAM heatsink on PoP and LAN) ticks over idle at 45C (700Mhz) but easily breaches 50C when running full bore in Turbo Mode (1000Mhz ARM, 500Mhz Core, 500MHz SDRam, +6 over-volt). The highest temperature I've observed is 75C. I find it a little hard to believe that a Pi doesn't breach 50C in Turbo Mode without additional forced cooling, or ridiculously low ambient temperature

Now I finally understand why some people ask for heatsinks, holes in cases and such.
I admit, my room isn't heated yet, I guess room temperature is at about 20°C, so I didn't expect highscore in the temperature rating, but 75°C is way out of my reach!
A few weeks ago when it was a bit warmer at 700MHz the RPi reached 38°C, at 1000 (yay I'm in the giggahurtz club) I reached 47°C, now I'm running at 35 and 44°C.
To be aware of the temperature and turbo modeI I have a 16x2 LCD display hooked up that shows date, time and CPU temperature, when turbo kicks in, instead of the date there is a Capslocked TURBO! and the CPU frequency displayed. :roll:
I did hope CPU frequency was adjusted in steps and not just turbo on/off, so the frequency display would be more fun to watch than just a "TURBO! 1000" appear.

User avatar
wallarug
Posts: 460
Joined: Mon May 14, 2012 8:21 am
Location: Sydney, Australia

Re: Who is in the 1GHz Club?

Sun Oct 14, 2012 12:38 am

Smada wrote:
milhouse wrote:
LenReinhart wrote:Mine is fine in turbo mode. ... It runs around 40 degrees C at 700MHz and it hasn't seen 50 at 1000MHz.
That's impressive, where do you live - the North Pole? ;-)

My Pi (with a small RAM heatsink on PoP and LAN) ticks over idle at 45C (700Mhz) but easily breaches 50C when running full bore in Turbo Mode (1000Mhz ARM, 500Mhz Core, 500MHz SDRam, +6 over-volt). The highest temperature I've observed is 75C. I find it a little hard to believe that a Pi doesn't breach 50C in Turbo Mode without additional forced cooling, or ridiculously low ambient temperature

Now I finally understand why some people ask for heatsinks, holes in cases and such.
I admit, my room isn't heated yet, I guess room temperature is at about 20°C, so I didn't expect highscore in the temperature rating, but 75°C is way out of my reach!
A few weeks ago when it was a bit warmer at 700MHz the RPi reached 38°C, at 1000 (yay I'm in the giggahurtz club) I reached 47°C, now I'm running at 35 and 44°C.
To be aware of the temperature and turbo modeI I have a 16x2 LCD display hooked up that shows date, time and CPU temperature, when turbo kicks in, instead of the date there is a Capslocked TURBO! and the CPU frequency displayed. :roll:
I did hope CPU frequency was adjusted in steps and not just turbo on/off, so the frequency display would be more fun to watch than just a "TURBO! 1000" appear.
Could you publish the python script for your Display? I have a 16 x 2 display and that sounds somewhat cool to have.

sdpenaloza
Posts: 4
Joined: Sat Oct 13, 2012 8:55 am

Re: Who is in the 1GHz Club?

Sun Oct 14, 2012 12:49 am

simplesi wrote:
put it in turbo mode 1Ghz haven't had any problems since with sd card corruption
its very hard to imagine that upping the clock speed improves the reliability of an RPi :)

I'd make a small wager that you've stopped doing something that was causing the problems :)

Simon
Probably true :lol: had quite a few issues with read-only FS lock outs, which lead to complete freezes that lead to (hard shutdowns) during the default speeds (reformatted the SD card).

Which I haven't had issues with now (same time i started overclocking to 1ghz), still I am alright with less problems =) whatever was the reason =P

Smada
Posts: 10
Joined: Sat Feb 04, 2012 9:08 pm

Re: Who is in the 1GHz Club?

Tue Oct 16, 2012 8:47 am

wallarug wrote: [...]
Could you publish the python script for your Display? I have a 16 x 2 display and that sounds somewhat cool to have.
Sure, all credits go to Matt at http://www.raspberrypi-spy.co.uk/ though, i just messed around a bit and you can be sure anything that looks efficient is his work ;)

Temperature and CPU get checked every second, time every 0.1s, so it's not a really precise clock...

Code: Select all

#!/usr/bin/python
#coding:utf-8
# HD44780 LCD Test Script for
# Raspberry Pi
#
# Author : Matt Hawkins - all credits go to him, I just messed around a bit.
# Site   : http://www.raspberrypi-spy.co.uk
# 
# Date   : 03/08/2012
#
#
# The wiring for the LCD is as follows:
# 1 : GND
# 2 : 5V
# 3 : Contrast (0-5V)*
# 4 : RS (Register Select)
# 5 : R/W (Read Write)       - GROUND THIS PIN
# 6 : Enable or Strobe
# 7 : Data Bit 0             - NOT USED
# 8 : Data Bit 1             - NOT USED
# 9 : Data Bit 2             - NOT USED
# 10: Data Bit 3             - NOT USED
# 11: Data Bit 4
# 12: Data Bit 5
# 13: Data Bit 6
# 14: Data Bit 7
# 15: LCD Backlight +5V**
# 16: LCD Backlight GND

#import
import RPi.GPIO as GPIO
import time



# Define GPIO to LCD mapping
LCD_RS = 7
LCD_E  = 8
LCD_D4 = 25 
LCD_D5 = 24
LCD_D6 = 23
LCD_D7 = 18
LED_ON = 15

# Define some device constants
LCD_WIDTH = 16    # Maximum characters per line
LCD_CHR = True
LCD_CMD = False

LCD_LINE_1 = 0x80 # LCD RAM address for the 1st line
LCD_LINE_2 = 0xC0 # LCD RAM address for the 2nd line 

# Timing constants
E_PULSE = 0.00005
E_DELAY = 0.00005

def main():
  # Main program block

  GPIO.setmode(GPIO.BCM)       # Use BCM GPIO numbers
  GPIO.setup(LCD_E, GPIO.OUT)  # E
  GPIO.setup(LCD_RS, GPIO.OUT) # RS
  GPIO.setup(LCD_D4, GPIO.OUT) # DB4
  GPIO.setup(LCD_D5, GPIO.OUT) # DB5
  GPIO.setup(LCD_D6, GPIO.OUT) # DB6
  GPIO.setup(LCD_D7, GPIO.OUT) # DB7
  GPIO.setup(LED_ON, GPIO.OUT) # Backlight enable

  # Initialise display
  lcd_init()

  # Toggle backlight on-off-on
  GPIO.output(LED_ON, True)
  time.sleep(0.1)
  GPIO.output(LED_ON, False)
  time.sleep(0.1)
  GPIO.output(LED_ON, True)
  time.sleep(0.1)
  
  print "begin"
  date=time.strftime("%a, %d.%m.%Y",time.localtime())
  oldtime=time.strftime("%H:%M:%S",time.localtime())
  i = 100
  check=1
  while i >= 1:
	try:
  		newtime=time.strftime("%H:%M:%S",time.localtime())
  		if i>10:	
			thermal = open("/sys/class/thermal/thermal_zone0/temp","r")
			temp = thermal.read()
			thermal.close()
			cpu = open("/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq","r")
			freq = cpu.read()
			cpu.close()
			freq=freq[:-1]
			temp = temp[:-1]
			temp =int(temp)/1000
			freq =int(freq)/1000
			if freq!=700:
				i=5
				freq='{:>5}'.format(freq)
				turbo= " TURBO!"+freq
			else:
				turbo=time.strftime("  %d.%m.%Y",time.localtime())
				i=1
			line = str(temp)+chr(223)+'C'+turbo 
			
		if oldtime!=newtime:
			
			lcd_byte(LCD_LINE_1, LCD_CMD)
  			lcd_string(line,1)
			#lcd_string(datum,1)
  			lcd_byte(LCD_LINE_2, LCD_CMD)
  			lcd_string(newtime,2)
  		time.sleep(0.1)
		oldtime=newtime
		i=i+1
	except KeyboardInterrupt:	
  		print "Bye!"
		time.sleep(3) # 3 second delay
		i=0
	
  # Send some left justified text
  lcd_byte(LCD_LINE_1, LCD_CMD)
  lcd_string("Shutting down",1)
  lcd_byte(LCD_LINE_2, LCD_CMD)
  lcd_string("",1)

  time.sleep(1) # 3 second delay

  # Send some right justified text
  lcd_byte(LCD_LINE_1, LCD_CMD)
  lcd_string("",3)
  lcd_byte(LCD_LINE_2, LCD_CMD)
  lcd_string("",3)

  time.sleep(1)



def lcd_init():
  # Initialise display
  lcd_byte(0x33,LCD_CMD)
  lcd_byte(0x32,LCD_CMD)
  lcd_byte(0x28,LCD_CMD)
  lcd_byte(0x0C,LCD_CMD)  
  lcd_byte(0x06,LCD_CMD)
  lcd_byte(0x01,LCD_CMD)  

def lcd_string(message,style):
  # Send string to display
  # style=1 Left justified
  # style=2 Centred
  # style=3 Right justified

  if style==1:
    message = message.ljust(LCD_WIDTH," ")  
  elif style==2:
    message = message.center(LCD_WIDTH," ")
  elif style==3:
    message = message.rjust(LCD_WIDTH," ")

  for i in range(LCD_WIDTH):
    lcd_byte(ord(message[i]),LCD_CHR)

def lcd_byte(bits, mode):
  # Send byte to data pins
  # bits = data
  # mode = True  for character
  #        False for command

  GPIO.output(LCD_RS, mode) # RS

  # High bits
  GPIO.output(LCD_D4, False)
  GPIO.output(LCD_D5, False)
  GPIO.output(LCD_D6, False)
  GPIO.output(LCD_D7, False)
  if bits&0x10==0x10:
    GPIO.output(LCD_D4, True)
  if bits&0x20==0x20:
    GPIO.output(LCD_D5, True)
  if bits&0x40==0x40:
    GPIO.output(LCD_D6, True)
  if bits&0x80==0x80:
    GPIO.output(LCD_D7, True)

  # Toggle 'Enable' pin
  time.sleep(E_DELAY)    
  GPIO.output(LCD_E, True)  
  time.sleep(E_PULSE)
  GPIO.output(LCD_E, False)  
  time.sleep(E_DELAY)      

  # Low bits
  GPIO.output(LCD_D4, False)
  GPIO.output(LCD_D5, False)
  GPIO.output(LCD_D6, False)
  GPIO.output(LCD_D7, False)
  if bits&0x01==0x01:
    GPIO.output(LCD_D4, True)
  if bits&0x02==0x02:
    GPIO.output(LCD_D5, True)
  if bits&0x04==0x04:
    GPIO.output(LCD_D6, True)
  if bits&0x08==0x08:
    GPIO.output(LCD_D7, True)

  # Toggle 'Enable' pin
  time.sleep(E_DELAY)    
  GPIO.output(LCD_E, True)  
  time.sleep(E_PULSE)
  GPIO.output(LCD_E, False)  
  time.sleep(E_DELAY)   

if __name__ == '__main__':
  main()
If you have any problems getting it to work, check out Matts original code and the great instructions at raspi-spy. http://www.raspberrypi-spy.co.uk/2012/0 ... ht-switch/

Return to “General discussion”