I am trying to change the static IP address of USB0 port of BeagleBone Black.
I know this thread was open previously (Changing the static IP of Beagle Bone Black USB0). But no answer was found. So I am reopening now, to see if people have got any solution now.
I also found there is solution by Eric Wong. (http://ewong.me/changing-usb0-ip-address-on-the-beaglebone-black/)
----- But this solution is good for may be old debian images. The latest ones have different file contents of what's mentioned in the solution. And therefore above solution does not work.
Steps I did:
step 1: I tried to change /etc/network/interfaces such that default address is 192.168.8.2 instead of 192.168.7.2 as this:
iface usb0 inet static
address 192.168.8.2
netmask 255.255.255.0
network 192.168.8.0
gateway 192.168.8.1
step2: Then I changed contents of file /etc/udhcpd.conf
-- change "192.168.7.1" to "192.168.8.1" in two places.
step3: reboot
Bingo, I lost my connectivity and now I have to rewrite the Debian image onto Beaglebone black again, as I no longer can access it. So basically neither I am unable to access through 192.168.7.2 or 192.168.8.2
So If anyone knows how to do it, It would be really helpful if you can share your thoughts ?
Coming into this late; my network uses 192.168.6/24 and 192.168.7/24 internally, so the latest BB images didn't work for me at all.
First: there's no real substitute for a real serial connection via the J1 connector; a 3.3v USB serial doodad is cheap, and being able to watch the whole boot (and image flashing!) process from the very start is super helpful. Adafruit sells one that works great with BeagleBone: https://www.adafruit.com/product/954
Anyway, on Debian GNU/Linux 10 (Apr 2020 image), /etc/default/bb-boot contains:
...
USB_CONFIGURATION=enable
#It's assumed usb0 is always enabled, usb1 can be disabled...
USB0_SUBNET=192.168.7
USB0_ADDRESS=192.168.7.2
USB0_NETMASK=255.255.255.0
USB1_ENABLE=enable
USB1_SUBNET=192.168.6
USB1_ADDRESS=192.168.6.2
USB1_NETMASK=255.255.255.0
DNS_NAMESERVER=8.8.8.8
Adjust this to taste and reboot. In my case, I changed USB0 to 192.168.70, and #commented out all the USB1 lines altogether.
Because I have to re-flash a bunch of boards periodically, I burned this into the SD card image itself, which saved me a lot of time later.
Related
I installed mosquitto on my Raspberry Pi.
I installed the MQTT Binding, MQTT Binding (1.x) using PaperUI.
I created an item:
Number mqtt_kitchen_gas "Gas Level [%.1f]" {mqtt="<[mosquitto:Home/Floor1/Kitchen/Gas_Sensor:state:default]"}
I opened a terminal window and sent:
mosquitto_pub -u openhabian --pw xxxx -t "Home/Floor1/Kitchen/Gas_Sensor" -m 10
The value "10" appeared in the Gas Level field.
I could change "10" to any number and that would appear in the field.
All was good with the world.
Then I rebooted and looked for the binding MQTT. It is not listed under Configuration, Bindings. (GPIO, another binding I installed is listed.) Also, if I search the Add-ons for MQTT it shows MQTT Binding (1.x) is installed (can be uninstalled) and I can still change the Gas Level field using the above mosquitto_pub.
Maybe I shouldn't worry about it since it works but maybe I have something wrong with my installation and it will come back to bite me.
Any opinions?
I am not completely sure (about 75% :D), but i think that the MQTT 1.x Binding simply doesn't provide any configuration that could be done in paper ui.
That could be the reason why it isn't displayed in the config section.
Since it appears in the addons section and works, everything should be fine.
I am using this binding too and it works properly for ages.
Of course i checked my configuration area in paper ui and it isn't shown there for me too.
Anyways its always fine to check the logs regularly for problems.
If there are none, installation is fine.
I had made uclinux(uboot+kernel+romfs) for my disco board for (stm32f429).
Now I have a custom board which uses different bank (bank1 instead of bank2 in disco board) I tried to configure u-boot according to new board but I have an odd problem:
when I use the old u-boot without any changes, the boot loader can see kernel image but it has a HARD FAULT ERROR when it extracts the kernel image to SDRAM,and this is natural!
BUT when I configure uboot according to new board structure even uboot doesnt load and I see nothing in serial console!
could you please help me about it, it is more than two months Im trying to solve it!!!
Some background:
I'm trying to set up Azure Pack in a test environment, and are currently woriking on setting up the servers who's going to host it all.
To do this i have two virtual Windows Server 2016 TP4 servers hostet on a ESXI host, and so i need to set up Storage Spaces Direct.
(iSCSI target and Storage Spaces (WS 2012), have been ruled out since the first is a nightmare to set up and the internet told me the second one comes with a low R/W speed).
I've been following this guide: https://technet.microsoft.com/en-us/library/mt126109.aspx
Problem:
When i run this cmdlet: Enable-ClusterStorageSpacesDirect
, I get this warning: No elegible DAS disk found.
Both servers have 3 disk each. They are initialized and 100% unallocated, and I have tried with them beeing both offline and online.
If I try running this cmdlet: (Get-Cluster).DasModeEnabled=1
I get the following error: The property 'DasModeEnabled' cannot be found on this object. Verify that the property exists and can be set.
Any and all help is greatly appriciated!
Storage Spaces Direct doesn't support FC & RAID-controlled LUNs.
The key is to force S2D to accept RAID BusType:
(Get-Cluster).S2DBusTypes=256
Here's a good article about it https://www.starwindsoftware.com/blog/resolving-enable-clusters2d-bus-type-support-issue-on-some-storage-controllers.
Another option is to reflash the controller's firmware to IT mode.
There's also other solutions, like that Starwind, which I suggest you to test.
i'm running a Red Hat EL 5.7 workstation with some NFS users mounted on a server. I have to set NVidia parameters to dual screen with xinerama and save the X configuration file, that's ok, but when i login the first time in every user included root, the second monitor doesn't turn on and when i login the second time it works, any ideas?
Read Xorg's log to discover. It's usually /var/log/Xorg.0.log.
Hope this doesn't sound crazy or something
I am trying to create a mini O.S. (who didn't?, it is like visiting Mecca for a muslim - any programmer must do it at least once in his life)
So, I created a simple boot-loader, that works fine when executed from a virtual boot-able ISO, in a virtual machine (Oracle VM Virtual Box). It just displays a message for now.
At this point, I am supposed to give the control to another code, that would start being my O.S. All this will be executed from the virtual optical disk. I could burn it on a CD and run it on a i386.
No, to make this really something, I want to run the "O.S". from a hard disk, so I wonder if there's a way to "burn" the boot-able information (boot-loader and other files to be loaded) directly on a virtual disk (like .vmi, .vhd, .hdd)
When I install a conventional O.S., like Windows or Linux, from an ISO image, on the virtual machine, the boot-loader starts a new code section, that installs the O.S. on the virtual disk. That is how I should do it, too: create a installer for the O.S., that would write my booting section on the virtual disk. That means that everytime I make a change to my O.S. I must re-install it. I don't like that. I would like to be able to write the booting code directly inside the virtual disk file, start the machine in Virtual Box, and see it running. I opened the .vmi file with an HEX editor but I cannot figure out where should I place the code to be considered boot-able.
Now, tell me whether I don't know what am I talking about or is there a solution for this.
Thanks to everybody!
I found out how to do it. Create a vmdk disk, open in in a HEX editor and paste the bootable information starting from 0