Raspberry Pi - Group: Raspberry Pi

glynn_bird on Trying to get an RTL8188CUS wireless USB NIC working.

Sat, 12 May 2012 21:42:56 +0000

Answering my own question:

pacman --sync --refresh --sysupgrade

Then importing your most recent driver does the trick.

Thanks for your help.

gregd72002 on Compiling and running OpenGL ES programs

Sat, 12 May 2012 20:57:13 +0000

I'm on the same boat - trying to get glmark2 to run on RPi. This might be helpful for newcomers:

glmark2 sources: https://launchpad.net/glmark2/trunk/2012.03/+download/glmark2-2012.03.tar.gz

glmark2 requires libpng12; many distros have only newer version of libpng; below is a patch to fix it;

http://pastebin.com/qUU16Dvh

With this you should be able to configure & compile glmark2. Now we need someone to fix the initiation stage (as mentioned before). There are two main things to analyse and understand:

- how does glmark2 initializes OpenGL ESv2

- how to initialize OpenGL ESv2 on RPi (hello_triangle should be good source of information)

Once we have the differences this should be trivial to fix. I also guess that the OpenGL ESv2 on RPi adheres to the specification so there should be no need for any further fixes other than the initiation stage.

http://pastebin.com/qUU16Dvh

rew on OpenWRT for Raspberry Pi

Sat, 12 May 2012 20:54:53 +0000

Openwrt is a distribution that could be useful on a 'pi.

However it is optmized to run in much less memory and flash than what we have on the 'pi. So it is unnecessary. On the other hand, why use more if that's all you need. Well for starters, you get a nicer "environment" if you take a full distro like debian.

Anyway, that said: I don't have experience with compiling openwrt. To compile openwrt, I suggest you google for "openwrt source download" and download the source. Next you google for "openwrt compile from source". Read what comes up. Good luck!

rew on OpenWRT for Raspberry Pi

Sat, 12 May 2012 20:54:35 +0000

Openwrt is a distribution that could be useful on a 'pi.

rew on Feasibility of RPi for EFI

Sat, 12 May 2012 20:47:56 +0000

Again, I"ll say that such applications are entirely possible. However you"ll have to build a device driver for "engine management". The proper thing to do would be to have userspace things do the slow things, like determining the proper value for injection moment, and then the actual triggering of an interrupt at exactly the right moment is a kernel thingy that the driver does.

You lose some of the "ease of programming" though. And you gain the complexity of interfacing with the Linux kernel. But after this driver is written, you have a neat setup with plenty "ease of programming" to add things.

Oh, and by the way: Automotive (even a scooter) environments are nasty. You'll likely sometimes drive in rain and the electrical environment with firing spark-gap components (the spark plugs!) nearby isn't friendly either....

DavidO on SSH Guide For Complete noob?

Sat, 12 May 2012 20:47:55 +0000

prodata said:

Is Putty the only such compatible ssh client to consider (I"m sure there might be others, but to rephrase: is Putty the accepted standard tool, or does it have competition?)

Is there any such tool that might also have FTP built-in (ie so that a file could easily be transferred between local and remote devices) or is the only answer to use a separate FTP tool.

You might take a look at Bitvise Tunnelier. It's not opensource, but it is free to use in a non-commercial setting. I find it much more comfortable than PuTTY, and it also provides a gui sftp interface as well.

dtud on Xmanager to Pi

Sat, 12 May 2012 20:44:41 +0000

Joe,

If I may, I think what's going on here is a little bit of a common game that Linux advocates and Windows advocates play to annoy each other.

I really aren't interested in seeing if Windows or Linux can wee up the wall the highest.

Pretty much what the OP is asking is: How do I get the Pi to automatically display a graphical login screen (I believe this is called "XDM") on my Windows PC via Xmanager?

That's exactly what I'd like.

I'm a "login and type 'startx' kinda guy

That doesn't work for me using PuTTy to SSH on the Pi....

pi@raspberrypi:~$ startx
xauth: (stdin):2: unknown command "9963f0ea9ff99fccfdb56ba762ff6a04"

X: user not authorized to run the X server, aborting.
giving up.
xinit: No such file or directory (errno 2): unable to connect to X server
xinit: No such process (errno 3): Server error.
pi@raspberrypi:~$

It falls into the legal rubric of "Know or should have known".

Fair enough, but really - who hasn't used MS Windows? 95% of the worlds PC's etc..

I'm going to walk away from this for the rest of the evening & come back at it

tomo with a with hopefully renewed vigor.

2048

SN on Cases for the Raspberry Pi

Sat, 12 May 2012 20:44:03 +0000

I do think there needs to be a "Most bizarre raspi case competition thread!"

prodata on SSH Guide For Complete noob?

Sat, 12 May 2012 20:42:31 +0000

Likewise a new Linux user, with a couple of ssh-type questions:

If I just want to access the Pi shell remotely (purely across my local LAN) from a Windows box then is there any reason to look beyond Putty? Is Putty the only such compatible ssh client to consider (I"m sure there might be others, but to rephrase: is Putty the accepted standard tool, or does it have competition?)

Is there any such tool that might also have FTP built-in (ie so that a file could easily be transferred between local and remote devices) or is the only answer to use a separate FTP tool.

Then, if I did actually want to control an X windows session remotely, what is the choice of recommended tools? I see talk of TightVNC and UltraVNC but without getting any sense of whether these are the only or necessarily the best (free) VNC tools. Can I assume that VNC is some sort of established standard so that you can use say TightVNC on the Pi and UltraVNC on the PC. Or do the server and client need to match? Does Windows (eg Vista/7) have a VNC client already built-in, which could be used. What about using say TeamViewer on the PC – just something I have and use already for remote access or does this use some different/proprietary protocol?

Sorry for all the questions – it"s just tricky trying to get a picture of how to get remote access to a Pi most easily and efficiently. (And I don"t like loading up my Windows PC with a pile of utilities that may not actually be necessary.)

toxibunny on Podcast Recommendations?

Sat, 12 May 2012 20:38:09 +0000

Answer me this

radiolab

wiretap

caustic soda

this american life

adam and joe (bit of google-fu needed to find this one...)

SN on Arch with Chrome or Firefox?

Sat, 12 May 2012 20:34:57 +0000

Chromium (v.close relative of Chrome) on Debian has been done elsewhere on here already I believe

LastSilmaril on OpenELEC meets Raspberry Pi - part 1 (XBMC)

Sat, 12 May 2012 20:33:26 +0000

Well, after the last time I tried to build, something went wrong and my entire virtual hard-disk got filled up, to the last bit. (I'm confused too.) Me being the genius that I am, there was no snapshot, but thankfully I did have a separate backup vdi that had almost all of my files/programs, so I trashed this one and made a new VM based on the backup.

Out of curiousity I ran 'date' right after I began the build - took a little more than three hours, and should be faster on subsequent builds.

Trashed the storage partition so that the new build would start fresh.

Build 10946 is the first one to be completely responsive at startup, even with the RSS feed on (shut it off anyway), and has not become unresponsive whilst accessing smb or fetching metadata - atm it's scanning my TV shows. (Haven't tempted fate though; I'm just gonna let it scan.) Using the start.elf from this build, not the one posted on the last page. I'm not sure if this stability is based on any actual code changes, or simply because the build is clean (haven't been emptying the build.OpenELEC-RPi.arm-devel folder).

rew on Exclusivity

Sat, 12 May 2012 20:22:06 +0000

RS and Farnell have to invest in a "selling-to-consumers" infrastructure JUST for this one product. If Amazon would start selling raspberry pi's NOW at $35 incl shipping their market would dry up instantly. I'm sure their legal department has put something in place to prevent that from happening.

milhouse on XBMC running on Raspberry Pi

Sat, 12 May 2012 20:20:28 +0000

igot6strings said:

What is the status of this as it is right now?
I am looking to switch from my Boxee Box to XBMC and would love to use the Pi to make the transition. I understand its not final or anything of that nature but if you folks could give me a rough idea of where its at that'd be much appreciated.

I'm using a version of OpenELEC I built yesterday (r10935).

XBMC/OpenELEC, it's a work in progress so some things are good, some are bad.

SD playback is pretty good on the whole, but HD playback (particularly 1080p) a little glitchy (certainly with LG IPS225V monitor, it seems to renegotiate the HDMI handshake every 30 seconds or so, but not always). HD audio is not playable (hardly surprising) but presumably may work on "passthru".

The biggest problem by far is the fact that the XBMC GUI consumes close to 100% CPU all of the time (but not during playback), and this makes scanning media libraries near impossible as there is so little CPU free to work on the scan. Also, start a scan and the device soon becomes unresponsive necessitating a reboot.

The GUI (certainly in OpenELEC) is currently so sluggish that it rules out any possibility of the Ras-Pi being used as a media player as it's such an unpleasant, slow and glitchy experience (it often loses the ability to display cover and fan art, showing black rectangles instead) - hopefully this is high on the list of priorities to be fixed. I've tried all the dirty region fixes, but none have yet worked.

What has been achieved so far is certainly fantastic (thanks Gimli, Dom etc.), but it's a fair way from being usable and replacing any current media player you may have.

84d

Joe Schmoe on Xmanager to Pi

Sat, 12 May 2012 20:19:22 +0000

I think the key question here is: How much do you (JamesH) know about "Xmanager"?

(which is really, "How much do you care/want to know?")

If I may, I think what's going on here is a little bit of a common game that Linux advocates and Windows advocates play to annoy each other. The essence of the game is that the Windows advocates act like they don't have to define any of their terms, because, well, everybody knows all about Windows and Windows tools and applications, right? It's in the drinking water, right? In return, Linux advocates pretend not to know things that they either clearly do know, or at least, could easily know with a small amount of Googling. It falls into the legal rubric of "Know or should have known".

So, that's what I think is going on here. FWIW, I do know what Xmanager is, having used it for quite a while, and I also know (from having tried it) that a quick Google will reveal what it is as well. Anyway, Xmanager does have an "XDM" mode, but I never saw the point in it (I'm a "login and type 'startx' kinda guy").

Pretty much what the OP is asking is: How do I get the Pi to automatically display a graphical login screen (I believe this is called "XDM") on my Windows PC via Xmanager?

With an implied: It should work OOB, just like it does under Solaris (and, probably, Linux as well, but my recollection of having messed around with it some is that it really does only completely OOB with Solaris. You had to do a little messing around to get it working with Linux)