yes I use your script since I own the dongle
but I have always got this disconnect issue.
I did not updated this PI3 since one or 2 month, and only update today, so maybe some changes is older than latest kernel/driver, I dont know.
The thing is that I am now contemplating my router wifi interface's clients logs for hours without Alpha dongle disconnection
Just a question that has nothing to do (linux noob here) : I dont understand when and how I should issue the "install-wifi" when I check for update :
sudo apt-get update
I did try to launch the script just after this two commands, but it then detect the actual kernel since I havent yet rebooted and not the new one.
So after rebooting the wifi of course doesn't have the good driver and I need to hard plug the pi to the network to install the matching driver.
If you have any instructions...
I've had this problem as well. Determining if the kernel is updated when running apt-get upgrade is an issue I've had.
Unfortunately I've no solution for using my script as it is but I have been investigating and have found a sort of solution but it requires some manual work. The issue is primarily determining if apt-get upgrade is going to update the kernel and then if it is what is the version going to be. However, I think I've found a way round the problem.
So to find if apt-get upgrade is going to update the kernel run the command apt-get upgrade and before installing the new packages check the package list for raspberry pi kernel updates, such as "libraspberrypi-bin libraspberrypi-dev libraspberrypi-doc libraspberrypi0
" and "raspberrypi-bootloader raspberrypi-kernel
If you see packages like these let the upgrade run but do not
reboot when the command finishes installing the new files.
Now to find the new kernel version and build that has been installed. Execute the following commands
Code: Select all
sudo gunzip -k changelog.Debian.gz
This should open the new changelog file which has, or should have, info on the new kernel version like
Code: Select all
raspberrypi-firmware (1.20170303-1) jessie; urgency=medium
* firmware as of b51046a2b2bb69771579a549d157205d9982f858
-- Serge Schneider <[email protected]> Fri, 03 Mar 2017 14:30:23 +0000
raspberrypi-firmware (1.20170215-1) jessie; urgency=medium
* firmware as of 3fb63c413cabfddb7fb9ed286bfc62abe73cc310
* Added bcm2708-rpi-0-w.dtb
-- Serge Schneider <[email protected]> Wed, 15 Feb 2017 17:47:53 +0000
The first line with "firmware as of
" gives a pointer to the firmware version at https://github.com/raspberrypi/firmware/commits
. There is a button which probably shows "Branch: master
". Click that button and select "stable
" and then look through the list of commits for one that matches the value shown in the Changelog.Debian file you opened with nano. When you find it make a note of the description and date then open the Hexxeh/rpi-firmware repo https://github.com/Hexxeh/rpi-firmware/commits/stable
and check for a commit with a similar description to the raspberrypi/firmware repo. Take a note of the commit ID and then you can run the install-wifi script using command format like
Code: Select all
sudo install-wifi -u 185fcf81f599aa9db7ec114de9bf7d0345065f67
. This is the commit ID value from the Hexxeh/rpi-firmware repo with the same description as the raspberrypi/firmware repo with the commit ID from changelog.Debian file example above. After the wifi driver is installed you can reboot and your Pi should be up and running with the new kernel and wifi driver.
All a bit of a pain and for me I think it would be easier to connect to a wired network but it appears to work as I tried it on my Pi 3 today and it worked fine.
Would be nice to be able to get the script to do this but I have no idea how it could be done.
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra
Please post ALL technical questions on the forum. Please Do Not send private messages.