Tiny Core Base > CorePlus
Help for Newbie: offline installation of tcz packages in texmode
Tambry:
I just set up my Fileserver and its backup with Lubuntu 24.04 LTS and configured rsnapshot and samba by the terminal only - but I am still a Linux-Newbie...so sorry for my stupid questions (not sure if I have my post even in the right category).
I want to learn more and as goal, I want to install a Linux on my NAS (QNAP TS-451), and have ssh, samba and mdadm installed to use it ...well, as a NAS (but without any clutter and me in full control). Local storage holding the OS is a USB drive with 400 MB (MB, not GB). This lead me to Tiny Core and I can install it with the Core Plus CD, use the GUI, enable my USB-WiFi and download and install all needed packages. This showed me that TC can run on the NAS.
To learn, I would like to repeat the installation but with no GUI and no Internet (ie not using the Appbrowser). How/Where can I download the required tcz files from the repository? Can I then just put them on a USB disk, mount it and install with tce-load from it?
Rich:
Hi Tambry
Welcome to the forum.
--- Quote from: Tambry on September 09, 2024, 02:59:58 PM --- ... How/Where can I download the required tcz files from the repository? ...
--- End quote ---
The latest 32 bit versions are here:
http://tinycorelinux.net/15.x/x86/tcz/
The latest 64 bit versions are here:
http://tinycorelinux.net/15.x/x86_64/tcz/
You might want to consider taking an hour to read the fine book found here:
http://tinycorelinux.net/book.html
CentralWare:
--- Quote from: Tambry on September 09, 2024, 02:59:58 PM ---I want to learn more and as goal, I want to install a Linux on my NAS (QNAP TS-451)
--- End quote ---
@Tambry: Welcome to TinyCore!
QNAP already has a custom linux image running on it, and yes, it's full of bloat and restrictions galore where third party repositories are required just to get it to operate a little more Linux'y.
WARNING: Modifying the firmware is a one-shot deal! Be sure you have ALL of the necessary VIDEO, USB, STORAGE and NETWORK drivers before you begin; once you've overwritten the internal 512MB'ish flash there's no turning back!
I have the x31 series units here (ARM based) and not the x51 (Celeron based) so I cannot walk you through the process directly, but can give you a few pointers to make the transition easier. Bare in mind, the QNAP systems are usually not your standard run of the mill motherboard with BIOS that's accessible and programmable by the end user which will boot by CD/DVD or USB (or not that I was aware of...) That would make your task too easy! :) Based on your details, here is your system from inside.
IF the above matches your system (Dual Core Celeron) we'll need to dig a little deeper and determine the NETWORK hardware as Power-Up didn't mention it and I cannot zoom in close enough to tell what chipset it runs off of. I'm assuming it uses the same chips as it's big brother, the 451+ (Intel WGI210AT 1GBe chips)
If your standard Linux kernel and/or third party drivers are readily available, start collecting them before making any attempt at installing Linux of ANY flavor permanently. You'll also want to create a DD image of the flash as it stands right now "just in case."
Before considering replacing your existing Linux kernel, I'm going to recommend USING the existing setup to get rid of the bloat; this way you can always "Factory Reset" if you get yourself into trouble. The first thing you need to do, however, is to offload any and all files on the device that you want to keep -- they may not survive the trip!
Once your system is good to experiment with, search G00gle for QNAP third party repositories such as MyQNAP if they still exist. You'll find instructions on how to use the APPS console to install the repository. Once installed, search that repo for a package called ENTware. This is vital at this stage as it'll give you access to software extensions that QNAP otherwise doesn't make available to you - which is "most everything else" found in a Linux environment.
Once you've located and installed ENTware, go into your Control Panel > Telnet/SSH and ENABLE SSH if you haven't already. SSH is going to become your new best friend since you'll be getting rid of QTS in the end, which is their web-based control system. If you prefer to connect a keyboard and HDMI monitor, you can also (likely) do all of this from the QNAP itself instead of SSH, but I don't know the limitations of the x51 series of what you see on the screen; whether it's the shell or their version of a desktop. The shell is preferred.
Once ENTware is installed, go into the shell and install pciutils and usbutils which is going to help us determine your exact hardware setup
--- Code: ---ipkg update
ipkg install pciutils
ipkg install usbutils
--- End code ---
NOTE: I have ENTware installed on two different ARM platforms (ARM6 and ARM7) and the app is "ipkg" on one and "opkg" on the other... if the above complains about not being able to find ipkg... switch to opkg instead.
Afterward, create a number of text files to attach here on the forum
--- Code: ---dmesg > /mnt/Public/dmesg.txt
uname -a > /mnt/Public/uname.txt
pciutils > /mnt/Public/pciutils.txt
usbutils > /mnt/Public/usbutils.txt
--- End code ---
NOTE: This assumes you still have the default Public share set up. Change "Public" to one of your share folder names if you do not.
Get this far and return here with your experiences and attach your files. You may have to attach dmesg.txt separately depending on its size.
@Rich: I have to go "under the knife" (so to speak) in a few hours and may not be back online for a bit. Head over to the links I posted above if you would, please, and check to see if the chipsets Power-Up did list are in fact kernel supported. I believe the major differences between the 451 and 451+ were the enclosures themselves, the CPU (Dual vs. Quad) and I THINK the PSU, but I cannot be certain as that was a decade'ish ago and like when you're out fishing... something that small usually gets thrown back, and with such a high price tag (at the time)... I was happy to do just that; we purchased a half dozen or so Atom boards and built our own devices for roughly the same price as one of theirs and ended up using Webmin as a really easy control panel that fit the bill perfectly for what the devices were intended - almost completely ready to run out of the box :)
Good luck!
Rich:
Hi CentralWare
--- Quote from: CentralWare on September 10, 2024, 03:12:06 AM --- ... determine the NETWORK hardware as Power-Up didn't mention it and I cannot zoom in close enough to tell what chipset it runs off of. ...
--- End quote ---
Near the bottom of the page they show an image of the board labeled:
"On the mainboard's solder side are also a pair of Intel WGI210AT Ethernet controllers."
That's the igb driver.
I see no driver for this:
"The hardware monitor IC, a Fintek F71869AD."
I see no driver for this:
"An Asmedia ASM1442 controls the HDMI port the HD Station exploits."
This one should be OK:
"The CPU is passively cooled by a small heatsink. It is an Intel Celeron J1800 (Bay Trail) with two cores running at 2.41 GHz."
I had to deal with a Bay Trail in a netbook (Asus T100CHI). Needed to build a kernel
with extra options, most of which were added to later kernel configs, including these:
--- Code: ---CONFIG_I2C_DESIGNWARE_BAYTRAIL=y
CONFIG_PINCTRL_BAYTRAIL=y
--- End code ---
I don't know if it matters, this is not set:
--- Code: ---# CONFIG_INTEL_SOC_PMIC is not set
--- End code ---
CentralWare:
@Rich:
--- Quote from: Rich on September 10, 2024, 10:45:39 AM ---Near the bottom of the page they show an image of the board labeled:
...update.pdf]WGI210AT[/url] Ethernet controllers.
That's the igb driver.
I see no driver for this: "The hardware monitor IC, a Fintek F71869AD."
I see no driver for this: "An Asmedia ASM1442 controls the HDMI port the HD Station exploits."
This one should be OK: "The CPU is passively cooled by a small heatsink. It is an Intel Celeron J1800 (Bay Trail) with two cores running at 2.41 GHz."
I had to deal with a Bay Trail in a netbook (Asus T100CHI). Needed to build a kernel...
--- Code: ---CONFIG_I2C_DESIGNWARE_BAYTRAIL=y
CONFIG_PINCTRL_BAYTRAIL=y
--- End code ---
I don't know if it matters, this is not set:
--- Code: ---# CONFIG_INTEL_SOC_PMIC is not set
--- End code ---
--- End quote ---
NOTES:
Fintek: https://github.com/torvalds/linux/blob/master/drivers/gpio/gpio-f7188x.c
ASMedia: (Possible Reference - need hardware ID) https://linux-hardware.org/?id=pci:1b21-1242-1043-8675
KERNEL:CONFIG_INTEL_SOC_PMIC: I don't see a reference to Crystal Cove, but noted "just in case."
--- Quote ---That's the igb driver.
--- End quote ---
Please elaborate? (In the Garbage Bin? :) )
This guy: ? https://www.intel.com/content/www/us/en/support/articles/000005480/ethernet-products.html
Didn't we already have an e1000 driver built at one point? Or is that in the kernel these days?
Then again, not exactly seeing "straight" @ the moment, pain meds haven't worn off yet :P so all references to grey matter memory... currently on hiatus...
Ya' know... I'm not investing right now as I don't really have justification, but I'm rather intrigued.
I was pondering doing a complete open-heart bypass on different Buffalo and QNAP (ARM based) NAS devices not all that long ago, mainly because their "recovery" options are almost nil if the unit goes kaput... but I just added Intel/AMD based NAS units to the "Maybe To Do" list along with the ARM units still humming away in my personal repository storage (which were already hacked to double as dns/dhcp/tftp/ntpd and a few other things Buffalo intentionally left out of their desktop models and QNAP... well, they started off great, BUT THEN...)
Thank you for your efforts, my good Sir!
Navigation
[0] Message Index
[#] Next page
Go to full version