WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: 1 ... 7 8 [9] 10
81
Raspberry Pi / Re: Eth0:1 fallback static IP on first boot?
« Last post by ovacikar on March 07, 2024, 06:53:21 AM »
@Paul_123 sorry for off topic, but did you receive my PM for openvpn? Need to recompile it with current openssl. currently it is downloading old openssl-1.1.1.tcz
82
after reviewing:
https://forum.tinycorelinux.net/index.php/topic,26897.0.html

and visiting the referenced register dot com links, naturally went poking and found this:

https://www.theregister.com/2024/02/07/failed_usb_sticks
83
Raspberry Pi / Re: Eth0:1 fallback static IP on first boot?
« Last post by ovacikar on March 07, 2024, 06:40:04 AM »
Got it, however I only need this after downloading a new image. So it needs to be implemented on the original picore image, not the one i have modified.

Maybe I submit it as an enhancement request then.
84
Raspberry Pi / Re: Eth0:1 fallback static IP on first boot?
« Last post by patrikg on March 06, 2024, 11:47:27 PM »
Yes and you need to change the initrd. Write/change if I am wrong here.
If you pass some the kernel command line options that not correspond to the kernels parameters, the kernel will pass these to environmental variables.
So if you pass ip=213.123.123.123 you can get this via $ip.

You can use that in the bootlocal.sh
Code: [Select]
echo $ip
85
TCE Corepure64 / Re: ThinkPad issue in 15.0
« Last post by curaga on March 06, 2024, 11:00:02 PM »
Fix the half resolution first. xrandr can change those at runtime, for permanent changes you'd edit xorg.conf.
86
TCE Corepure64 / Re: ThinkPad issue in 15.0
« Last post by thane on March 06, 2024, 03:40:50 PM »
Thanks for the replies!

I compared xorg.0.log in version 14.0 to the one for 15.0. In both it looks like Xorg is switching to a default resolution and screen physical size. This is 1280 x 800 and 338 x 211 in version 14.0, 640 x 400 and 169 x 105 in version 15.0.

xdpyinfo confirms screen #0 in version 14.0 is 1280 x 800 pixels (338 x 211 mm), screen #0 in version 15 is 640 x 400 pixels (338 x 211 mm).

So maybe in both versions something is missing but the default in 14.0 is at least workable whereas 15.0 isn't?
87
Raspberry Pi / Re: Eth0:1 fallback static IP on first boot?
« Last post by Paul_123 on March 06, 2024, 02:32:55 PM »
command line can be processed by any program.  it live at /proc/cmdline after boot.

Write a script to do what you want.
88
Raspberry Pi / Re: Kexec Support?
« Last post by patrikg on March 06, 2024, 11:40:21 AM »
Why do you need this tool ??

Are you compiling lots of kernels so you don't want to reboot.
Or I missing something with your thoughts.
 
Why not try to compile it your self, and also first thinking of this is that you maybe also
need to compile your own kernel enable/support this feature.

https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git
89
Raspberry Pi / Re: Eth0:1 fallback static IP on first boot?
« Last post by ovacikar on March 06, 2024, 11:09:44 AM »
I was looking for something similar to raspbian cmdline.txt, to pass the static Ip on boot by mounting the vfat filesystem only.

https://raspberrypi.stackexchange.com/questions/13464/how-can-i-edit-a-raspbian-sd-card-image-to-use-a-static-ip-address-within-window

Open your SD card installed with Raspbian with Windows Explorer through card reader. You'd find cmdline.txt. Open cmdline.txtand add ip = x.x.x.x after rootwait (x.x.x.x being the intended IP address).

dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet init=/usr/lib/raspi-config/init_resize.sh ip=192.168.1.145

90
Raspberry Pi / Re: Eth0:1 fallback static IP on first boot?
« Last post by CentralWare on March 06, 2024, 10:47:38 AM »
I cannot speak for anyone else's methods, as my way of thinking may not be suited for everyone, but here's how we do things at the shop:

For a potentially headless device (RasPi pico-w included) we first check to see if there's been a successful wired or wireless connection previously; if so we attempt to reconnect using those specs.

IF NOT or if the above attempt fails, we shut down dhcp-client if it's running, clean out all IP related settings and temporarily turn the device INTO an access point.  A remote computer can then connect to the RasPi, configure it as desired and upon disconnecting from it, have it reboot to make the new settings go into effect.

We started doing things in this fashion when we had to come up with a close-to-fool-proof method to build devices which were Alexa/Google compatible where we could configure a device remotely without the fear of duplicate IP addressing, we were able to see what device we were connecting to based on its SSID, etc.  Each device could have the exact same network specs (such as 192.168.0.1/24) and not interfere with any others as they cannot "see" one another.

To accomplish this with a normal RasPi, you'll need dnsmasq to serve as the device's DHCP server (it's tiny and is only needed in "AP MODE.")  Setting it up is very simple since you really only need to tell it what IP ADDRESS RANGE to use, such as the above noted 192.168.0.1/24.  Secondly, you'll need hostapd.  This allows you to create the hot-spot ("Access Point") itself.  Finally, you'd launch dropbear (or OpenSSH if that's your preference) and from there it simply waits for an SSH connection from your remote computer.

I just did a GxxGLE search for the concept; here's a page which might help if you're interested: https://raspberrypi-guide.github.io/networking/create-wireless-access-point
Pages: 1 ... 7 8 [9] 10