Octoprint requires Raspbian Jessie based distro to work with Raspberry Pi 3

[alex-gibson]

I have been testing ahead of the launch today, and noticed that the standard OctoPi distro gives rainbow screen of death on the Pi 3, and I could not follow the instructions (due to errors) to install for Jessie, using latest NOOBS distro as at last night.

For hassle free OctoPrint on the Pi 3 I recommend starting with the latest Jessie nightly build, which worked well enough that I demo'd it at the Pi 3 launch party today :)

Happy to contribute testing to get a stable Jessie/Pi3 build!!!

[foosel]

@picclock I'm still not 100% sure what problem exactly you are experiencing.

Did you have kernel panics like @A-Nesh (full out system crashes) or not?

There are two issues here:

1. One manifests as the Pi still being alive but the wifi going down after some idle time due to power management kicking in (and being broken). That can be fixed by disabling power management by adding wireless-power off to the wifi config in /boot/octopi-network.txt. Apparently there is also a fix available through rpi-update or possibly even apt-get upgrade by now, but personally I'd prefer a fixed raspbian base image...
2. The other is a severe bug in the driver causing a full out kernel panic in some cases, effectively locking down the system (and causing such nice things as prints stopping and heaters staying on). That manifests as the Pi not even reacting to a wired connection, keyboard, monitor etc but should hopefully be visible in /var/log/syslog. This can be solved by blacklisting the brcmfmac kernel module, but that also removes the possibility to use the integrated wifi at all (you need to use a wired connection then, or an external wifi dongle). It's a bit like solving an issue with a home appliance not by repairing it but throwing it on the trash and buying a new one - it's not a fix.

I'm asking to be very specific as to what issue specifically you are seeing (one or two or both), because the RPi people I've been talking to over some hops in between appear not be convinced yet that there are more issues than the power management related one (number 1), so any proofs for the existence of issue number 2 (in the form of hardware setup used + syslog with kernel panic etc) would help to hopefully raise awareness and get this issue addressed as well.

And just for the record, issue number 2 is nothing that can be addressed through OctoPi, it's something that needs to be fixed in the kernel driver for the wifi chipset, so something that needs to be done by the people maintaining that driver.

[picclock]

Hi Foosel. Thx for your efforts. I disabled the wifi power save as in http://www.modmypi.com/blog/disable-wifi-power-management After this the pi would not connect to the router. It could not be seen at all. I then replaced the file I had edited with the backup, and blacklisted the brcmfmac file and it worked and has been running without issues since.

It may be that the wifi power mod is incorrect, or, because I deleted the file contents and replaced them with a paste from the web page, that I may have deleted something else which was needed.

The initial problems were that wifi connected intermitantly, then would no longer connect at all.

If you wish me to run any tests to diagnose I wil be happy to do so, but please make it simple !!

Best Regards

picclock

[picclock]

@ Foosel OK, I just disabled the wifi power ( in the octopi-network, added wireless-power off) and it seems good so far without the dongle. Will keep you updated if it fails.

Best Regards

picclock

[foosel]

@picclock then blacklisting the module is possibly not necessary

---

General instructions on how to test for wifi issues with the RPi3 here

Download and flash a fresh OctoPi 0.13 nightly image (0.12 doesn't work and will give you the "rainbow image"). Configure your wifi credentials while still using the SD card as a thumb drive while still in the computer you flashed it from by editing octopi-network.txt in the root of that thumb drive. Make sure your text editor doesn't mangle the quotes around the ssid and passphrase (especially TextMate on Mac appears to love to do that, you want " or ' if either ssid or passphrase contains spaces, nothing else!). Plug the SD into the Pi, do NOT attach a wifi dongle. Boot the Pi, verify that it connects to your network. Then observe its long time behaviour while using it (e.g. printing stuff).

If an issue arises, is it

a) the Pi stopping to react to network access via wifi but still apparently running (e.g. if a print is running it continues, a keyboard and monitor still work, ...) or

b) the Pi stopping to react to network access and anything else, apparently crashing (e.g. if a print is running it stops, a keyboard and monitor don't still work, ...) or

c) nothing of the above

If a), does this solve the issue?

1. Shutdown the Pi, unplug the SD, plug it into your computer's card reader
2. Edit octopi-network.txt again

3. Turn

   ## WPA/WPA2 secured
   iface wlan0-octopi inet manual
       wpa-ssid "YOUR SSID"
       wpa-psk "YOUR PASSWORD"

   into

   ## WPA/WPA2 secured
   iface wlan0-octopi inet manual
       wpa-ssid "YOUR SSID"
       wpa-psk "YOUR PASSWORD"
       wireless-power off

   and save.

4. Put the SD back into the Pi, reboot, observe

If b), please provide your /var/log/syslog file.

If c), sounds like a so far unknown issue.

If you are only experiencing a), the solution to a) should work. If you are not seeing your Pi3 connect to your network after applying the solution to a), something else is broken in your configuration that has nothing to do with either a) or b) (probably a mistyped password, mangled quotes or something similar).

Please do not try to apply other steps outlined in other blog posts around the internet, follow the steps outlined in this thread. Give precise feedback as to what exact behaviour you are observing at all times.

[ghollingworth]

Hi,

Gordon Hollingworth here from Raspberry Pi. The WiFi power management issue has now been fixed, apt-get update / upgrade on a Raspbian distribution will fix this for you. I'd suggest pulling that kernel into the OctoPi distribution.

The driver crashing issue is specific to this case only. We're not seeing this anywhere else so it is somewhat strange (not saying it isn't a problem just that it's going to be hard to understand / diagnose!)

Could do with answers to the following:

1) If you return to Raspbian Jessie and sudo apt-get upgrade / update 2) edit /boot/config.txt and change arm_freq to 600 (i.e. force underclock just in case) 3) Does this still cause the problem 4) Other possibility is that it's something to do with the WiFi access point settings... Can you try forcing the channel to somewhere in the middle of the range and turn off encryption for a little while to see if's to do with that?

Gordon

[A-Nesh]

@ghollingworth i'll try it later today and get back to you

[foosel]

@ghollingworth thanks for reaching out. We can add the kernel update step to the OctoPi build script, but would prefer to base OctoPi on a Raspbian release that already includes that. Do you know if a new stable image release is planned soon? If not we'll have to go with adding the upgrade (in the hopes that this works with our qemu based build).

[ghollingworth]

We are planning on a new update soon, but currently no date, should be in the next week or so�

Gordon

Director of Engineering, Raspberry Pi (Trading) Limited T: +44 (0) 1223 322633 M: +44 (0) 7450 946289 E: gordon@raspberrypi.org W: www.raspberrypi.org

On 15/03/2016 13:44, "Gina H�u�ge" notifications@github.com wrote:

@ghollingworth https://github.com/ghollingworth thanks for reaching out. We can add the kernel update step to the OctoPi build script, but would prefer to base OctoPi on a Raspbian release that already includes that. Do you know if a new stable image release is planned soon? If not we'll have to go with adding the upgrade (in the hopes that this works with our qemu based build). � You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/guysoft/OctoPi/issues/207#issuecomment-196823619

[foosel]

Thank you, that's something to go on.

[seabas917]

Hey guys, Am I crazy or is the latest published nightly (2016-03-15_2016-02-26-octopi-jessie-lite-0.13.0) missing its Octoprint install?

On the other hand it looks like after ssh-ing in wifi credentials, the onboard wifi is working really well! Same ping quality as my laptop, in this build. I'll leave ping test up all night to see if this is stable. I'll do a manual Octoprint install after seeing if the system stays up.

Thanks Foosel and Gordon! Amazing work from both of you!

Side note: No surprise here, but the AdafruitLCD install script in Nightly(03-15) for the OctoPanel, will crash the Pi3 system on next reboot and not recover..

The boot/octopi-network file isn't working, so i suggest manual setup for onboard wifi: sudo nano /etc/wpa_supplicant/wpa_supplicant.conf

and adding a WPA2 network:

network={
    ssid=“*****”
    psk="*****"
}

Reboot Wifi:

sudo ifdown wlan0
sudo ifup wlan0

Then confirming Wifi IP with : ifconfig

[guysoft]

Yes! yesterday nightly is bad, don't use it

[guysoft]

@seabas917 There is a new nightly build, should work now

[picclock]

Hi I have just tried the new build and it has broken some menu items in the system menu with an API error 'Invalid API key'.

changes as listed below :-

sudo nano /etc/init.d/octoprint following at line 77, before RETVAL="$?"

gpio export 17 out gpio export 27 out gpio export 22 out

And :-

sudo nano ~/.octoprint/config.yaml

and in the system>actions section, after actions:-

• action: printer on command: gpio -g write 27 1 name: Printer on
• action: printer off command: gpio -g write 27 0 name: Printer off
• action: camera on command: gpio -g write 17 1 name: Camera on
• action: camera off command: gpio -g write 17 0 name: Camera off
• action: aux on command: gpio -g write 22 1 name: Aux on
• action: aux off command: gpio -g write 22 0 name: Aux off

Hopefully can be easily fixed:

Best Regards

oldun

On Wed, Mar 16, 2016 at 12:36 PM, Guy Sheffer notifications@github.com wrote:

@seabas917 https://github.com/seabas917 There is a new nightly build, should work now

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/guysoft/OctoPi/issues/207#issuecomment-197299535

[A-Nesh]

@ghollingworth i did what you said: did sudo apt-get upgrade / update changed arm_freq to 600 was 800 before!? and unblocked brcmfmac

I left it over night, when i got home it was dead. both LEDs (red end green) are on and it not responds on keyboard or monitor.

The syslog did not reveal anything interesting other than some error.

Mar 16 06:17:05 octopi systemd[1]: Starting Copy rules generated while the root was ro... Mar 16 06:17:05 octopi systemd[1]: Starting LSB: Set preliminary keymap... Mar 16 06:17:05 octopi systemd[1]: Started Copy rules generated while the root was ro. Mar 16 06:17:05 octopi systemd-fsck[71]: e2fsck 1.42.12 (29-Aug-2014) Mar 16 06:17:05 octopi systemd-fsck[71]: /dev/mmcblk0p2: clean, 50245/1881152 files, 477961/7775360 blocks Mar 16 06:17:05 octopi fake-hwclock[77]: Wed 16 Mar 06:17:01 UTC 2016 Mar 16 06:17:05 octopi systemd[1]: Found device /dev/ttyS0. Mar 16 06:17:05 octopi systemd[1]: Starting Sound Card. Mar 16 06:17:05 octopi systemd[1]: Reached target Sound Card. Mar 16 06:17:05 octopi systemd-udevd[120]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc00b8, key code 161): Invalid argument Mar 16 06:17:05 octopi systemd-udevd[120]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc0183, key code 226): Invalid argument Mar 16 06:17:05 octopi systemd-udevd[120]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc0184, key code 421): Invalid argument Mar 16 06:17:05 octopi systemd-udevd[120]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc0186, key code 423): Invalid argument Mar 16 06:17:05 octopi systemd-udevd[120]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc018a, key code 155): Invalid argument Mar 16 06:17:05 octopi systemd-udevd[120]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc018e, key code 397): Invalid argument Mar 16 06:17:05 octopi systemd-udevd[120]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc01b6, key code 212): Invalid argument Mar 16 06:17:05 octopi systemd-udevd[120]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc01bc, key code 430): Invalid argument Mar 16 06:17:05 octopi systemd-udevd[120]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc0221, key code 217): Invalid argument Mar 16 06:17:05 octopi systemd-udevd[120]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc0223, key code 172): Invalid argument Mar 16 06:17:05 octopi systemd-udevd[120]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc022d, key code 418): Invalid argument Mar 16 06:17:05 octopi systemd-udevd[120]: Error calling EVIOCSKEYCODE on device node '/dev/input/event0' (scan code 0xc022e, key code 419): Invalid argument Mar 16 06:17:05 octopi systemd[1]: Found device /dev/mmcblk0p1. Mar 16 06:17:05 octopi systemd[1]: Starting File System Check on /dev/mmcblk0p1... Mar 16 06:17:05 octopi keyboard-setup[108]: Setting preliminary keymap...done. ` No traces of crush or freeze... the end of syslog looks like this:

Mar 16 06:17:13 octopi systemd[1]: Starting HAProxy Load Balancer... Mar 16 06:17:13 octopi systemd[1]: Starting /etc/rc.local Compatibility... Mar 16 06:17:13 octopi systemd[1]: Starting Network is Online. Mar 16 06:17:13 octopi systemd[1]: Reached target Network is Online. Mar 16 06:17:13 octopi systemd[1]: Starting LSB: Start NTP daemon... Mar 16 06:17:13 octopi systemd[1]: Started /etc/rc.local Compatibility. Mar 16 06:17:13 octopi systemd[1]: Starting Wait for Plymouth Boot Screen to Quit... Mar 16 06:17:13 octopi systemd[1]: Starting Terminate Plymouth Boot Screen... Mar 16 06:17:13 octopi systemd[1]: Started Wait for Plymouth Boot Screen to Quit. Mar 16 06:17:13 octopi systemd[1]: Started Terminate Plymouth Boot Screen. Mar 16 06:17:13 octopi systemd[1]: Starting Getty on tty1... Mar 16 06:17:13 octopi systemd[1]: Started Getty on tty1. Mar 16 06:17:13 octopi systemd[1]: Starting Serial Getty on ttyS0... Mar 16 06:17:13 octopi systemd[1]: Started Serial Getty on ttyS0. Mar 16 06:17:13 octopi systemd[1]: Starting Login Prompts. Mar 16 06:17:13 octopi systemd[1]: Reached target Login Prompts. Mar 16 06:17:13 octopi ntpd[725]: ntpd 4.2.6p5@1.2349-o Mon Nov 2 04:29:47 UTC 2015 (1) Mar 16 06:17:13 octopi ntpd[728]: proto: precision = 0.573 usec Mar 16 06:17:13 octopi ntpd[728]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 Mar 16 06:17:13 octopi ntp[712]: Starting NTP server: ntpd. Mar 16 06:17:13 octopi systemd[1]: Started LSB: Start NTP daemon. Mar 16 06:17:13 octopi ntpd[728]: Listen and drop on 1 v6wildcard :: UDP 123 Mar 16 06:17:13 octopi ntpd[728]: Listen normally on 2 lo 127.0.0.1 UDP 123 Mar 16 06:17:13 octopi ntpd[728]: Listen normally on 3 wlan0 192.168.1.88 UDP 123 Mar 16 06:17:13 octopi ntpd[728]: Listen normally on 4 wlan0 192.168.1.232 UDP 123 Mar 16 06:17:13 octopi ntpd[728]: Listen normally on 5 lo ::1 UDP 123 Mar 16 06:17:13 octopi ntpd[728]: Listen normally on 6 wlan0 fe80::ba27:ebff:fe96:95d5 UDP 123 Mar 16 06:17:13 octopi ntpd[728]: peers refreshed Mar 16 06:17:13 octopi ntpd[728]: Listening on routing socket on fd #23 for interface updates Mar 16 06:17:13 octopi systemd[1]: Started HAProxy Load Balancer. Mar 16 06:17:13 octopi systemd[1]: Starting Multi-User System. Mar 16 06:17:13 octopi systemd[1]: Reached target Multi-User System. Mar 16 06:17:13 octopi systemd[1]: Starting Update UTMP about System Runlevel Changes... Mar 16 06:17:14 octopi systemd[1]: Started Update UTMP about System Runlevel Changes. Mar 16 06:17:14 octopi systemd[1]: Startup finished in 3.525s (kernel) + 14.625s (userspace) = 18.150s. Mar 16 06:17:18 octopi dhcpcd[708]: wlan0: no IPv6 Routers available Mar 16 13:21:28 octopi systemd[1]: Time has been changed Mar 16 13:36:04 octopi systemd[1]: Starting Cleanup of Temporary Directories... Mar 16 13:36:04 octopi systemd[1]: Started Cleanup of Temporary Directories.

i don't really understand why am i getting 2 IPs. a DHCP (232) and a static one (88)

[A-Nesh]

it crashed again, right now

[Cyphrz]

Just an update, a new base image is out

[guysoft]

There is already a new nightly build with the new image.

[yenoromp]

Hi Ive just installed the latest daily but octopi does not start automatically in it. Paul

[guysoft]

Bug in the nightly builds due to #214 , don't install it

[guysoft]

New nightly out with fix, @yenoromp you can try it now.

[yenoromp]

Thanks

I will give it a go tonight

Paul Moroney 0400720144

Sent from my iPhone

On 21 Mar 2016, at 12:28 AM, Guy Sheffer notifications@github.com wrote:

New nightly out with fix, @yenoromp you can try it now.

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub

[yenoromp]

Hi Tested it tonight and all ok. it looks very good , will do some printing tonight.

I also turned power save off on the wireless. "wireless-power off"

Paul

[lee-thompson]

As someone who was reading this thread with interest (after not being able to even get my Octopi to be recognised on my network, and being totally new to all this), I can confirm that the most recent build worked for me on a Raspberry Pi 3. Thank you!

[WZ9V]

lee-thompson, what specific build did you use?

I'm looking to setup a RPi 3 with wireless OctoPi.

[lee-thompson]

@WZ9V I used the 2016-03-20_2016-03-18-octopi-jessie-lite-0.13.0-0.13.0.zip from the nightly builds (http://docstech.net/OctoPiMirror/nightly/) - and I had to do it twice because MacOS's default text editor replaced my quote marks with the wrong kind when I updated my wifi credentials. Sublime Text was my saviour.

I literally punched the air when I could see it on my network though!

[WZ9V]

Thanks, gives me a good starting point and since I have Linux I don't expect any special quote issues.

[crazydart]

2016-03-23_2016-03-18-octopi-jessie-lite-0.13.0.zip (2016-03-23 00:36:17 UTC) is no good with the RPi3 and wifi.

2016-03-20_2016-03-18-octopi-jessie-lite-0.13.0-0.13.0.zip (2016-03-20 11:58:46 UTC) seems fine, printing with it right now.

[3driffs]

2016-03-20_2016-03-18-octopi-jessie-lite-0.13.0-0.13.0.zip (2016-03-20 11:58:46 UTC) prints, but I couldn't get the local GUI running. After mucking about installing packages, I have a local GUI and browser, but the camera isn't showing up in octoprint.

Net: I'm a LONG time removed from playing around at the UNIX/Linux level of an OS. Any guess as to when we'll see a RPi3 compatible stable build?

[gddeen]

I believe jessie 'lite' was built to NOT have a desktop session... An easier way would be to get the raspbian jessie build and then follow the steps to build octopi.

If you DO have a desktop locally, I don't think Octoprint is designed to run and display on an OctoPi. (I guess this means they didn't test it or the proxy doesn't like it? I'm clueless.)

[foosel]

The Jessie Lite base image doesn't have X included, and considering how much bloat that whole desktop cruft adds without being needed for the actual usage scenario that's a very very good thing.

If you DO have a desktop locally, I don't think Octoprint is designed to run and display on an OctoPi. (I guess this means they didn't test it or the proxy doesn't like it? I'm clueless.)

"They" did and it works just fine but "they" do NOT recommend it (and in fact strongly discourage it) since running a full desktop environment with CPU and memory hogging components including a software rendering browser next to a critical real-time job such as feeding a file to a 3d printer is a recipe for tears. OctoPrint is designed to be accessed from a different computer than the one it's running on for a reason, which means a lot of resource hungry things happen on the client to keep load off the backend. If you run both on the same device, you throw away all advantages.

And now surely people will swoop in again and tell me "oh, but I run it just fine, the four cores are plenty and I NEVER saw any bad consequences by running my full blown desktop environment on my Pi and accessing OctoPrint through that while printing a 20 hour print job with lots of curves, you are wrong!" - and I can just say, YMMV, but I wouldn't risk it.

Experience has shown that people will run way too much stuff next to OctoPrint on even a single core pi (ideally with an insufficient PSU for extra party) and then complain that it's Octo's fault their prints fail, so being able to build upon on a way less bloated base image that doesn't contain that particular risk in the first place has many advantages (download size being one of them btw, that stuff costs money...).

And if people desperately need X against all recommendations:

$ sudo ~pi/scripts/install-desktop

[nicolinux]

You should add "server" next to OctoPrint's name so people won't get the wrong idea. One does not run servers with X, except you really need it for the server's task, which for OctoPrint is not the case.

[foosel]

Wouldn't help ;)

[3driffs]

Well, the stable build has both X and a browser as part of it, so if it's not supposed to be there, someone made a mistake in that drop. I have a keyboard/monitor/mouse in the workroom with the printer, so I can operate it directly without fighting with the tiny LCD screen on the printer itself.

[foosel]

The stable build is based on Raspbian Wheezy, where no lite version without all the clutter they added (like Minecraft and whatnot, on top of X) was available. With 1.5GB base size.

The nightlies are based on Raspbian Jessie Lite.

[3driffs]

So going forward, no built-in GUI capability. Bummer - that's a big loss of functionality for me. Guess I'll have to dust off my linux skills and build my own platform, or run two different Pi's. Hmmm...that's an idea.

[foosel]

Or just install an X server? You know, via the existing package system? Or actually even something as simple as this (and yes, that is already included in the current 0.13 builds):

And if people desperately need X against all recommendations:

$ sudo ~pi/scripts/install-desktop

That means you'll have to wait a bit while it downloads a bunch of packets that are not needed for the core use case, but that's a one time thing.

And that you download these packets only if you need them instead of having them included in the image saves us time on every release trying to figure out what additional crud got added to the full Raspbian image that is not needed and only blows up the download size and saves everyone kind enough to provide a download mirror actual money for the saved traffic, not to mention saves everyone who just wants to run OctoPi as a headless server (the majority) the time needed to download the extra megabytes of image size they don't need for their use case. So win win for everyone really.

apt-get is there for a reason. Not every possible use case needs to be shipped out of the box if stuff is easy to install post-flash. Especially not if trying to do that doubles or triples the download size for everyone.

[3driffs]

Thanks, I missed that in the earlier post. No disagreement on the strategy, just wasn't aware it had changed. I may yet just run two PI's (they're cheap enough), my old 2 as the dedicated server, and the 3 with a full desktop environment. I haven't seen issues, but your point about load on during a long print is well taken.

[3driffs]

And just to close out my part in the thread, two pi's works great. Thanks for the info.

[yenoromp]

I'm sticking with the image I installed a week or so ago when the octopi install was fixed Done heaps of prints since then

Paul Moroney 0400720144

Sent from my iPhone

On 2 Apr 2016, at 12:04 PM, 3driffs notifications@github.com wrote:

And just to close out my part in the thread, two pi's works great. Thanks for the info.

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub

[glm1157]

Which nightly are you using? I tried the one of the latest builds (either 2016-04-04 or 2016-04-05, I forget) and I had problems setting up WiFi and connecting to my printer. It might be me or the build. Just want to try something that has worked for someone to eliminate one of the variables.

Thanks,

Gary

[yenoromp]

Mine is an oldish nightly

I will check later , but if you check the size of the download , mine is the second one after the size increase .... And it's working fine

Paul Moroney 0400720144

Sent from my iPhone

On 6 Apr 2016, at 8:14 AM, glm1157 notifications@github.com wrote:

Which nightly are you using? I tried the one of the latest builds (either 2016-04-04 or 2016-04-05, I forget) and I had problems setting up WiFi and connecting to my printer. It might be me or the build. Just want to try something that has worked for someone to eliminate one of the variables.

Thanks,

Gary

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub

[glm1157]

Thanks. I grabbed 2016-03-25_2016-03-18-octopi-jessie-lite-0.13.0.zip and had the same problems. I cannot get Wi-Fi to work. I am using WEP which might be part of the problem. Some folks have had problems with it on their Pi2s.

My second problem was fixed by switching to a lower baud rate. I assumed that I could use 250000 like I did on my PogoPlug version of Octoprint. I had to go down to 115200. It's working now. Printing a case for my PI now.

Thanks,

Gary

[fireman1396]

ok sooo i have literally NO idea what I'm doing... have a pi 3, running the latest nightly, got past the login screen, and have no clue what to do next.. all videos and such show only setting up with a version with GUI. i get i need to use the command line, but whats the next step? not sure if my wifi is connected or working

[yenoromp]

My wifi worked

I used the old way without the supplicant , as well as edited the networks file directly ...

Paul Moroney 0400720144

Sent from my iPhone

On 6 Apr 2016, at 2:34 PM, glm1157 notifications@github.com wrote:

Thanks. I grabbed 2016-03-25_2016-03-18-octopi-jessie-lite-0.13.0.zip and had the same problems. I cannot get Wi-Fi to work. I am using WEP which might be part of the problem. Some folks have had problems with it on their Pi2s.

My second problem was fixed by switching to a lower baud rate. I assumed that I could use 250000 like I did on my PogoPlug version of Octoprint. I had to go down to 115200. It's working now. Printing a case for my PI now.

Thanks,

Gary

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub

[notcranium]

Hi. Great job on what has been done so far. I hope this keeps progressing. I am supporting the project through Patreon!

I'm using jessie-lite-0.13.0. I don't have my printer yet so can't post if there are issues with that for another week. But the problems I see right now are:

• SD card is not initialized so I cannot upload files to it. Selecting the option to initialize it doesn't do anything.
• Timelapse is completely greyed out. The Logitech C310 appears to work like a champ though.
• I have a profile set up in the Cura Engine but can't seem to do anything with a .STL that I uploaded (maybe because there is no printer attached?)

I'm completely new to this so maybe my issues are related to not really knowing what I'm doing. :)

[nophead]

You can't upload to SD without a printer attached because the SD card it refers to is one attached to the printer. You also can't set the timelapse options without a printer attached.

Not sure about slicing as I don't use it.

[SirVer]

I have a similar issue and found out that my raspberry does not like 2.4GHz channels 12 and 13 - if your router is set to AUTO choose the channels, this might be your issue. See https://github.com/raspberrypi/linux/issues/1442#issuecomment-214993828.

[yenoromp]

Hi

Could this to be with time zones as some channels are not allowed in certain countries ?

Paul Moroney 0400720144

Sent from my iPhone

On 27 Apr 2016, at 5:33 PM, Holger Rapp notifications@github.com wrote:

I have a similar issue and found out that my raspberry does not like 2.4GHz channels 12 and 13 - if your router is set to AUTO choose the channels, this might be your issue. See raspberrypi/linux#1442 (comment).

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub

[guysoft]

Fixed in 0.13.0

[alex-gibson]

Thanks to everyone who contributed to fixing this issue!