Page 16 of 16

Re: Jessie Q&A

Posted: Wed Apr 26, 2017 7:03 pm
by fluzz
How can I install Jessie on a pi top already running pi top OS? How do rricharz's tools come into play (do I use them to install Jessie, or do I use them after I've installed it? Or are the tools Jessie themselves?)

Thanks!

Configuring SSH And Wpa_Supplicant Together Crash SSH servic

Posted: Mon Jun 12, 2017 4:52 pm
by rod2k
Try this, I've downloaded the latest distro for raspbian (2017-04-10-raspbian-jessie-lite), copy the SSH blank file in /boot/ to auto configure SSH service, and copy your valid Wpa_Supplicant to configure your Wireless Network Headless and the SSH Service will not let you connect over Ethernet (I get "Software Abort Connection" over putty) and over Wifi, the service does not respond at all :(

if you need more info (logs, config files or something) let me know

Re: Configuring SSH And Wpa_Supplicant Together Crash SSH se

Posted: Mon Jun 12, 2017 5:28 pm
by B.Goode
rod2k wrote:Try this, I've downloaded the latest distro for raspbian (2017-04-10-raspbian-jessie-lite), copy the SSH blank file in /boot/ to auto configure SSH service, and copy your valid Wpa_Supplicant to configure your Wireless Network Headless and the SSH Service will not let you connect over Ethernet (I get "Software Abort Connection" over putty) and over Wifi, the service does not respond at all :(

if you need more info (logs, config files or something) let me know

Does that mean that you have a cabled Ethernet and a WiFi connection active simultaneously?

If so, you might have a confusing situation with regard to routing that your RPi and router cannot resolve.

Does either method of connection work correctly if you disconnect the other?

Re: Configuring SSH And Wpa_Supplicant Together Crash SSH se

Posted: Tue Jul 04, 2017 3:18 pm
by rod2k
B.Goode wrote: Does that mean that you have a cabled Ethernet and a WiFi connection active simultaneously?

If so, you might have a confusing situation with regard to routing that your RPi and router cannot resolve.

Does either method of connection work correctly if you disconnect the other?
Not really, this is the secuence:

- New SD with 2017-04-10-raspbian-jessie-lite
- in Windows, wrote in /boot/ the SSH blank file and a valid Wpa_Supplicant.conf
- Start Raspberry PI and wait for boot
- Once it started, using DHCP you will see your Raspberry in the network over wifi with a valid IP but no SSH Service over Wifi
- Connect an Ethernet Cable, wait for DHCP and try SSH, you will get "Software Abort Connection" message

I'm Using Rpi 2 with T-link wifi dongle, I don't know if this behavior is the same in Rpi3 or Zero

I will try disconnecting Wifi Dongle before connecting Ethernet Cable to test your theory

-

-

Re: Configuring SSH And Wpa_Supplicant Together Crash SSH se

Posted: Tue Jul 04, 2017 4:55 pm
by DirkS
rod2k wrote:- in Windows, wrote in /boot/ the SSH blank file and a valid Wpa_Supplicant.conf
These files should go in the root (= highest level) of the partition you see in Windows, not in the directory 'boot'
You should see other files like kernel.img

Re: STICKY: Jessie Q&A

Posted: Tue Aug 22, 2017 3:23 am
by piman1947
I am attempting to download the Jessie OS version of Rasbian but I can not
find this version or even download it  through NOOBS since it is not one of the OSs
that NOOBS supports.  I was able to get the Jessie version about 1 week
ago but it seems it is no longer available.  Was it removed or am I not looking
at the right places ?

                    Thanks

                    Jerry Hoffman

Re: STICKY: Jessie Q&A

Posted: Tue Aug 22, 2017 6:46 am
by MrEngman

Re: STICKY: Jessie (now defunct and replaced with Stretch) Q&A

Posted: Fri May 04, 2018 6:58 am
by logos
Hi All,

I looked up http://downloads.raspberrypi.org/raspbian/images/
and I see that the last Raspbian Jessie release is raspbian-2017-07-05(The kernel version of this release is 4.9.35).
So was there any update to Jessie after that?

I also looked up https://github.com/raspberrypi/firmware/ both master branch and stable branch.
I looked around July 2017 in more detail, and there, it doesn't explicitly say a commit belongs to Jessie or Stretch.

And first release of Stretch is 2017-08-17,
so if I download 4.9.37 which was committed on 2017-07-13 is it Jessie or Stretch?

In https://github.com/raspberrypi/firmware
can you pin-point from which commit is Stretch? Or up to which commit is Jessie?

And when you moved to 4.14 why is there commits keep coming up on rpi-4.9.y branch of https://github.com/raspberrypi/linux?

Thank you!
By the way I am new here.
So please excuse any ignorance that I may have.

Re: STICKY: Jessie (now defunct and replaced with Stretch) Q&A

Posted: Fri May 04, 2018 9:15 am
by DougieLawson
What are you trying to achieve. The only sensible option for a new user with a new RPi is Raspbian Stretch 2018-04-18 or NOOBS 2.8 (if you need multiboot or are totally incapable of writing SDCards with Etcher).

Jessie retired when this thread was created. It's now more than six months since Stretch became the supported version of Raspbian.

Trying to use Jessie on new hardware won't work. You are wasting your time even thinking about it.

Re: STICKY: Jessie (now defunct and replaced with Stretch) Q&A

Posted: Fri May 04, 2018 4:10 pm
by logos
I was trying to find the last version of Jessie.
And then I was confused of different repositories.

What's the correlation between http://downloads.raspberrypi.org/raspbian/images/ and https://github.com/raspberrypi/firmware/ ?

Now I am just trying to understand.

And when you say you moved to Stretch and Kernel 4.14, why are you keep maintaining 4.9?

Re: STICKY: Jessie (now defunct and replaced with Stretch) Q&A

Posted: Fri May 11, 2018 1:53 am
by skypickle
MrEngman wrote:
Tue Dec 22, 2015 7:21 pm
.....
Especially do not edit file /etc/network/interfaces. Add a network section to file /etc/wpa_supplicant/wpa_supplicant.conf like ...
I am late to this thread but am wondering why the interfaces file should not be edited in stretch and why the wpa_supplicant.conf and dhcpd.conf are the places to set network configs.

Re: STICKY: Jessie (now defunct and replaced with Stretch) Q&A

Posted: Fri May 18, 2018 7:22 am
by rin67630
skypickle wrote:
Fri May 11, 2018 1:53 am
MrEngman wrote:
Tue Dec 22, 2015 7:21 pm
.....
Especially do not edit file /etc/network/interfaces. Add a network section to file /etc/wpa_supplicant/wpa_supplicant.conf like ...
I am late to this thread but am wondering why the interfaces file should not be edited in stretch and why the wpa_supplicant.conf and dhcpd.conf are the places to set network configs.
Me too.
I would also appreciate to get an authorized recommendation on what is the current way to get a WiFi autoreconnect.

Re: STICKY: Jessie (now defunct and replaced with Stretch) Q&A

Posted: Fri May 18, 2018 8:43 am
by DougieLawson
rin67630 wrote:
Fri May 18, 2018 7:22 am
Me too.
I would also appreciate to get an authorized recommendation on what is the current way to get a WiFi autoreconnect.
Stretch has a GUI to connect to WiFi that relies on the country code being set in the preferences dialog. It's not difficult to get it working. Once connected and after the settings are saved then re-connect is built-in.

Re: STICKY: Jessie (now defunct and replaced with Stretch) Q&A

Posted: Fri May 18, 2018 1:38 pm
by hippy
skypickle wrote:
Fri May 11, 2018 1:53 am
MrEngman wrote:
Tue Dec 22, 2015 7:21 pm
.....
Especially do not edit file /etc/network/interfaces. Add a network section to file /etc/wpa_supplicant/wpa_supplicant.conf like ...
I am late to this thread but am wondering why the interfaces file should not be edited in stretch and why the wpa_supplicant.conf and dhcpd.conf are the places to set network configs.
The non-technical answer is that, because of the way things are now intended to be done with Raspbian Stretch, those two files provide the settings rather than the old /etc/network/interfaces file.

One can still edit the /etc/network/interfaces file but that is at odds with how it is recommended things are done and may create associated issues which may need resolving, so the recommendation is "don't".

Re: STICKY: Jessie (now defunct and replaced with Stretch) Q&A

Posted: Fri May 18, 2018 2:08 pm
by n67
What's the "technical" answer?

Re: STICKY: Jessie (now defunct and replaced with Stretch) Q&A

Posted: Fri May 18, 2018 5:39 pm
by rin67630
DougieLawson wrote:
Fri May 18, 2018 8:43 am
rin67630 wrote:
Fri May 18, 2018 7:22 am
Me too.
I would also appreciate to get an authorized recommendation on what is the current way to get a WiFi autoreconnect.
Stretch has a GUI to connect to WiFi that relies on the country code being set in the preferences dialog. It's not difficult to get it working. Once connected and after the settings are saved then re-connect is built-in.
I have a few RPis working headless over WiFi and VNC.
They are configured over GUI and then continue headless.

From time to time they lost connection and did not reconnect until I rebooted them.

I used to modify ifupdown according to a workaround found on the net:

Code: Select all

sudo mv /etc/ifplugd/action.d/ifupdown /etc/ifplugd/action.d/ifupdown.alt
sudo cp /etc/wpa_supplicant/ifupdown.sh /etc/ifplugd/action.d/ifupdown
sudo reboot
Would you confirm that this is not required any more?
Thank you

Re: STICKY: Jessie (now defunct and replaced with Stretch) Q&A

Posted: Fri May 18, 2018 6:41 pm
by DougieLawson
ifplugd doesn't exist on current supported OS versions.

The time to upgrade to Raspbian Stretch is NOW!

Re: STICKY: Jessie (now defunct and replaced with Stretch) Q&A

Posted: Fri May 18, 2018 8:17 pm
by rin67630
DougieLawson wrote:
Fri May 18, 2018 6:41 pm
ifplugd doesn't exist on current supported OS versions.
The time to upgrade to Raspbian Stretch is NOW!
Are you sure?
My current newest system which I installed 2 weeks ago and which never had anything else than Raspbian Stretch from NOOBS 2.8.1 has very well got a folder /etc/ifplugd.

The question is: will it reestablish a lost WiFi connection when the router returns to function? (i don't mean: when a new interface is hot-plugged)

Re: STICKY: Jessie (now defunct and replaced with Stretch) Q&A

Posted: Tue Dec 25, 2018 8:59 pm
by coding
In the thread title it says Jessie is "now defunct". Does that mean existing installations could seize to function after updating via " apt full-upgrade"? I run Dnsmasq on a Jessie Pi 1 B+ and am getting more and more strange errors after updates and reboots (which I do every few months).
Today after the latest server failure after an update & reboot I realized I cannot even reinstall Dnsmasq anymore via "apt install dnsmasq --reinstall". It says the package "cannot be downloaded". I ended up starting it by executing "sudo dnsmasq", because systemd failed to load it.

I will probably install Stretch soon, but I still wonder if Raspbian Jessie is, like the thread title says, "defunct" and trouble is expected if users try to update their running system.
I searched for an EOS (end of support) table, but didn't find any timeline.

Re: STICKY: Jessie (now defunct and replaced with Stretch) Q&A

Posted: Tue Dec 25, 2018 9:26 pm
by fruitoftheloom
coding wrote:
Tue Dec 25, 2018 8:59 pm
In the thread title it says Jessie is "now defunct". Does that mean existing installations could seize to function after updating via " apt full-upgrade"? I run Dnsmasq on a Jessie Pi 1 B+ and am getting more and more strange errors after updates and reboots (which I do every few months).
Today after the latest server failure after an update & reboot I realized I cannot even reinstall Dnsmasq anymore via "apt install dnsmasq --reinstall". It says the package "cannot be downloaded". I ended up starting it by executing "sudo dnsmasq", because systemd failed to load it.

I will probably install Stretch soon, but I still wonder if Raspbian Jessie is, like the thread title says, "defunct" and trouble is expected if users try to update their running system.
I searched for an EOS (end of support) table, but didn't find any timeline.

AFAIAA no packages have been removed from either the Raspbian or Raspberry Pi Foundation repositories.

Jessie should still function but will no longer receive any updates, regards obsolescence that happened when Stretch was released in August 2017.

Debian themselves have a timeline which is a good indicator, though be aware that LTS is not supported in Raspbian

https://wiki.debian.org/DebianReleases



Regards updating Jessie, the last release was 5th July 2017:

http://downloads.raspberrypi.org/raspbi ... 017-07-05/

Code: Select all

sudo apt-get update
sudo apt-get dist-upgrade
sudo reboot

If you want newer though possibly unstable kernel / firmware:

Code: Select all

sudo rpi-update
sudo reboot

Re: STICKY: Jessie (now defunct and replaced with Stretch) Q&A

Posted: Tue Dec 25, 2018 11:40 pm
by n67
In the thread title it says Jessie is "now defunct". Does that mean existing installations could seize to function after updating via " apt full-upgrade"?
No. Nothing of the sort.

Calling it "defunct" is just excessive verbiage - hyperbole - on the part of certain entities with axes to grind.

Pay it no heed.

Re: STICKY: Jessie (now defunct and replaced with Stretch) Q&A

Posted: Wed Dec 26, 2018 6:15 am
by gkreidl
I'm just getting another 34 package updates on one of my Jessie systems.