With Linux 5.1 (which isn't quite released yet) we have good support for the network ports on the GnuBee.Both ports on the Gnubee-PC1, and all three on the Gnubee-PC2 are independently usable.
I have tried this and can't get the recovery to work. I press the black button on boot and can't get to 192.168.10.1.
With Linux 5.1 (which isn't quite released yet) we have good support for the network ports on the GnuBee.Both ports on the Gnubee-PC1, and all three on the Gnubee-PC2 are independently usable.
...
--
You received this message because you are subscribed to a topic in the Google Groups "GnuBee" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gnubee/YVM08lfWUUc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gnubee+un...@googlegroups.com.
To post to this group, send email to gnu...@googlegroups.com.
Visit this group at https://groups.google.com/group/gnubee.
To view this discussion on the web visit https://groups.google.com/d/msgid/gnubee/5352d1dc-f594-4e70-a5ea-26d3f82e39dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "GnuBee" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gnubee/YVM08lfWUUc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gnubee+un...@googlegroups.com.
To post to this group, send email to gnu...@googlegroups.com.
Visit this group at https://groups.google.com/group/gnubee.
To view this discussion on the web visit https://groups.google.com/d/msgid/gnubee/6f94d6bc-f323-4c09-9254-091a38cd6474%40googlegroups.com.
If I understand correctly, it is the build process that is hanging - yes?
The last line it prints is:FUSE (Filesystem in Userspace) support (FUSE_FS) [M/n/y/?] m??I tried the same experiment and the next line should be:Character device in Userspace support (CUSE) [N/m/?] (NEW) mat which point it waits for you to give an answer.Are you running this build in a normal terminal window, or have you redirected output to a file or something else?Are you running this on the gnubee, or are you cross-compiling?I've added CONFIG_FUSE_FS=m and CONFIG_CUSE=m to my configs to the next firmware I build will have this support included.
at which point it waits for you to give an answer.
Are you running this build in a normal terminal window, or have you redirected output to a file or something else?
Are you running this on the gnubee, or are you cross-compiling?
01-lo 02-eth0-1 02-ethblack
--
You received this message because you are subscribed to the Google Groups "GnuBee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gnubee+un...@googlegroups.com.
To post to this group, send email to gnu...@googlegroups.com.
Visit this group at https://groups.google.com/group/gnubee.
To view this discussion on the web visit https://groups.google.com/d/msgid/gnubee/7c0bf033-d06f-4bd9-8788-fa83354ab016%40googlegroups.com.
Hi Neil,Is there a list of patches you've applied to 5.1 ? Or better yet could be rebase your patches on top of 5.1 instead of merging in 5.1? That way it would be very easy to cherry pick your patches. I'm trying to build a 5.2-rc3 based firmware, but not sure if I need your patches or not.
/etc/network/interfaces.d/01-lo:auto lo
/etc/network/interfaces.d/01-lo:iface lo inet loopback
/etc/network/interfaces.d/02-eth0-1:auto eth0.1
/etc/network/interfaces.d/02-eth0-1:iface eth0.1 inet dhcp
/etc/network/interfaces.d/02-eth0-1: pre-up /etc/network/scripts.d/set_switch
/etc/network/interfaces.d/02-ethblack:auto ethblack
/etc/network/interfaces.d/02-ethblack:iface ethblack inet dhcp
/etc/network/interfaces.d/02-ethblack: pre-up /etc/network/scripts.d/no_switch
Is it possible to upgrade to this version using apt? Or do I have
to reinstall?
I've now build a 5.2.8 kernel. Kernel source, config files and prebuild images are available in the places described in the original post.
--
You received this message because you are subscribed to the Google Groups "GnuBee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gnubee+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gnubee/7b5fdf19-c8b9-44fb-9ecf-49de07033f62%40googlegroups.com.
I just installed the latest version on a fresh SD card but it
prints
cat: can't open '/mnt/gnubee-config.txt': No such file or
directory
[ 20.163309] Searching for partition GNUBEE-ROOT...
[ 20.181277] Assembling md arrays
[ 20.222487] random: crng init done
mdadm: No arrays found in config file or automatically
findfs: unable to resolve 'PARTLABEL=GNUBEE-CRYPT-ROOT'
findfs: unable to resolve 'LABEL=GNUBEE-ROOT'
While booting
I've now build a 5.2.8 kernel. Kernel source, config files and prebuild images are available in the places described in the original post.
Nvm I just forgot you have to run the config script after
flashing the firmware.
To view this discussion on the web visit https://groups.google.com/d/msgid/gnubee/5dc431eb-cd5d-c0cf-e9ee-57f8a0517d6c%40itscode.red.
Is it possible to upgrade to this version using apt? Or do I have to reinstall?
On 10/8/19 8:49 am, Neil Brown wrote:
--
I've now build a 5.2.8 kernel. Kernel source, config files and prebuild images are available in the places described in the original post.
You received this message because you are subscribed to the Google Groups "GnuBee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gnu...@googlegroups.com.
It looks like the firmware images are down right now?
On Sunday, 31 March 2019 01:32:19 UTC+1, Neil Brown wrote:With Linux 5.1 (which isn't quite released yet) we have good support for the network ports on the GnuBee.Both ports on the Gnubee-PC1, and all three on the Gnubee-PC2 are independently usable.Consequently I've decided that it is time to move on from the 4.4 kernels and start providing support for, and encouraging the use of, mainline.Mainline isn't 100% working (just very close) so I have a few patches on top of the latest 5.1 Release Candidate. The code that I'm building can be found in the "gnubee/v5.1" branch of https://github.com/neilbrown/linux. I build a complete firmware image using my gnubee-tools package, found at https://github.com/neilbrown/gnubee-tools.gitThe README.md file for that package has useful information about how to work with this firmware. It includes support for creating a brand new Debian installation without the need for a serial cable.Prebuilt firmware images can be found that http://neil.brown.name/gnubee/
Is there a mirror of neil.brown.name/gnubee some where? I have successfully installed debian jessie using Neil's firmware and I'm missing the modules.I will try to build them myself from Neil's sources in the meantime.
Note that if you are upgrading from a 4.4 installation, the network device names have changed and this can cause some confusion. They were previously eth0.1 and eth0.2. They are now ethblack and ethblue.The initramfs code creates a new copy of the Debian "/etc/network" directory and edits the interface files so that the correct names are used. This new copy is in a tmpfs filesystem which is mounted over /etc/network. Once you decide to stay with 5.1, you should probably make the changes permanent. If you aren't sure how, please ask.I'll be updating code and images as new release-candidates come out, and will probably follow 5.1-stable for a while before switching to 5.2Please report any problems, and also feel free to just let me know if you find this useful.
Using the USB-to-UART adaptor allowed me to set up the network and install debian jessie. No major issues.Thanks again Neil, great job!
--
You received this message because you are subscribed to the Google Groups "GnuBee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gnubee+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gnubee/79582f22-9fe5-46df-a89c-8880c2b9384e%40googlegroups.com.
Also I'm getting "database error" when I try to access your site, so not quite back up yet :p
I've had a hard time building from sources, as the current guide assumes you're bootstrapping from a Debian system of the right architecture. I'd love to get a working buildroot image.
> an email to gnu...@googlegroups.com
> <mailto:gnu...@googlegroups.com>.
Success/failure reports alway welcome.