Jump to content

Welcome, Guest!


  • Content Count

  • Joined

  • Last visited

  • Days Won


Tripitaka last won the day on October 6 2013

Tripitaka had the most liked content!

Community Reputation

1 Neutral

About Tripitaka

  • Rank

Profile Information

  • Gender
  • Location
    British Columbia, Canada
  1. Hey all. I dropped off this for a while but rediscovered it while patching my stuff for Heartbleed. Apologies for my lack of diligence. In the end, I managed to get a viable solution based off Raspbian that boots through to the IAR login page. I've not found a solution to auto-populate the login pop-up but I haven't looked either. I get around that by using an X-11 server and logging in remotely using TightVNC to IPaddress::5900 (note the double colon), fill out the details in the pop-up and then close the VNC session. Here are my build notes from last year: Obtain base build Install base build using Win32DiskImager Card into Pi and attach keyboard & mouse Config base build Resize root partition Set Keyboard Set locale Set timezone Enable SSH Boot to GUI Config WiFi Wifinet / password Exit GUI Update: sudo apt-get update sudo apt-get upgrade Install packages: sudo apt-get install chromium x11-xserver-utils unclutter x11vnc Boot to GUI Config Chromium Set default start page Close Exit GUI Setup auto-login: sudo nano /etc/inittab #1:2345:respawn:/sbin/getty 115200 tty1 1:2345:respawn:/bin/login -f pi tty1 </dev/tty1 >/dev/tty1 2>&1 Config no screensaver sudo nano /etc/lightdm/lightdm.conf # don't sleep the screen xserver-command=X -s 0 dpms Set up x11vnc sudo nano ~/.xsessionrc x11vnc -bg -nevershared -forever -tightfilexfer -display :0 x11vnc -storepasswd Config chromium start sudo nano /etc/xdg/lxsession/LXDE/autostart # comment everything and add the following lines @xset s off @xset -dpms @xset s noblank @chromium --kiosk --incognito http://www.iamresponding.com/V3/pages/default.aspx Config GUI autostart: sudo raspi-config enable GUI start at boot Reboot
  2. Yes, I have it working as well as it is going to given the limitations of the IAR code. I'm just about to fly out of the door but I can probably grab the image and mail it to you if you PM me your email address. better yet, I can probably up it to a Dropbox or something but it might be early Mon/Tue. In the end, I had to boot into the GUI and autostart Chromium to get past the useragent issue. I then use TightVNC to get remote access for login.
  3. I did get the dhclient files but I've been maxed out with work also. Stability seems to have settled down a bit with only one of the units - the furthest away from the router - giving problems. I'm going to move the router first and see if that helps. The devs are IAR are just just painful to deal with. I can write detailed test reports, present ideas and ask questions and I get maybe 3 or 4 word replies. They don't even have a support ticket system. From what I can gather, in March they will release an update that will eliminate all the issues regarding login so all I can do is wait and see what that brings; it seems pointless to expend energy finding workarounds at this stage if that is on the horizon. I'll update as I find more but I've had the fire lit under me to do a bit more stuff with the Pi. I have a 6 yr old daughter that I'd like to get into it so expect more from me here. :-)
  4. Yeah, I discovered that Midori uses the useragent defined in the config file while expanding on your use of startx to run Chromium, I've no idea why it wouldn't use the same when called from the command line but thats why I'm no programmer.. :-) Back to the choice screen, I did copy the link from the 'Access From A Desktop' and it was something like - default.aspx,true,false)) so I suspect that hitting one or the other link simply sends back a true/false value through the post form which then triggers something on the back end.
  5. Hmm. It would seem that the mobile/desktop selection is determined via a javascript post form from that landing page so no success in discovering the URL. They sure do like to make life difficult and I wouldn't mind if it was an all singing, all dancing HTML5 implementation but the site looks like something we used to build in about 1998! Running out of options that don't rely on the devs, I fear.
  6. OK, this morning I managed to get some time to play with the test rig. startx /usr/bin/chromium -kiosk [url="http://some.url.here/"]http://www.iamresponding.com[/url] did start Chromium but still dumped me at the mobile/desktop choice screen Anything in a script or at command that uses the --app switch crashes Chromium Running Chromium under matchbox WM with no switches does allow it to start but after about 10 seconds, if you type anything into the URL address bar, it crashes. WIthout typing, it will quite happily sit and run. I pulled the user agent string from an IE instance I have; it was: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.3; .NET4.0C; .NET4.0E) It seems that nothing running from a script uses the user agent string; if I run Midori under the GUI, it does pick up the user string in the config file perfectly and bypasses the choice screen at IAR. However, if I use: startx /usr/bin/midori -e Fullscreen -a http://www.iamresponding.com/ I get the same problem with the choice screen appearing. I've no problem using startx as a WM as long as I can script the startup. I'm going to see if I can capture the destination of the link for 'Access from a Desktop' and hit that directly.
  7. OK, it will be tomorrow before I grab that. There are 3 Pi's, all hooked up via WiFi in 2 different stations.
  8. The WiFi is a standard DSL connection that we manage. A couple of times, I've come to the screen to see the Midori screen saying that the site cannot be reached and with the 'Try Again' button, which never does anything; I have to reboot. I'm wondering if I'm getting a DHCP lease timeout that isn't getting refreshed for some reason and I thought that rather than spending time troubleshooting, I could just circumvent the area that might be contributing. I've no need for this to be DHCP but the WiFi does need to be issuing DHCP leases for other devices, like FF smartphones etc.
  9. Anyone ever tell you that your awesome? :-D Thanks man. I'm going to try and play with it too.
  10. Chrome on any platform other than the Pi doesn't get that screen so I'm wondering if there is something else they are grabbing at the back end of the site to define the platform other than the UserAgent string. The devs aren't very forthcoming. My alternative approach is to see if they will give me a string for the URL that will bypass this page and define the device as desktop via the URL. I'll try and do something on it over the weekend and let you know. On another issue - what would I need to do to assign an IP during boot on Wheezy rather than using DHCP? I think I'm having an issue with DHCP leases timing out and I want to head that one off at the pass. I've got the networks configured using the WiFi Config utility in the GIU which in turn has written to the wpa_configuration file rather than /etc/network/interfaces I'll admit I haven't researched yet through lack of time.
  11. I tried both methods, neither worked and both resulted in the GTK+ error.
  12. I followed some of the other links you gave earlier and run a script from the prompt which starts matchbox window manager and just Midori in fullscreen on top of that. Once I get the autologin working, I'll add a loop in there to restart the browser if it crashes and autorun the script so if anything goes south, all that will be required is to unplug the Pi and plug it back in again. I'll dig out a user agent string from IE on a Windows box I use for work. It's the only one in the house! ;-)
  13. Thanks for the tip! I tried the lines you gave me but I still get the same screen. I think that the key will lie with the back-end guys but they aren't the most communicative bunch. If I'm honest, the whole site setup is like something from the late '90's on Netscape Navigator, I don't think the concepts of HTML5 have reached them yet. I've got the screens up and running at the stations so it is doing it's job but there are a lot of improvements to be made in the interface. I do really appreciate the help so far though.
  14. I'm at my wits end trying to get Chromium to run from a command line. I've installed via sudo apt-get install chromium-browser and the install went OK. What I now want to do is run the browser from the command line without starting the default desktop manager. I can do it with Midori by using the lightweight 'matchbox' manager but typing 'chromium -kiosk' just gives me a GTK+ error. The problem that I'm trying to solve is that the back-end site I'm accessing cannot tell whether Midori is a desktop or mobile client from the User Agent report; I'm hoping that Chrome might address that issue. In a nutshell, can anyone suggest how I would go from the command prompt to a web browser with a defined URL using Chrome via script?

About Us

Bringing you the latest Raspberry Pi news, tutorials and user forum.

The Fruity Computer

  • Create New...