If you're describing what I think you are, the message is inaccurate and your account is NOT blocked.

There is a stupid and broken "protection" system on LQ that causes those messages - it applies to certain snippets of text and only blocks replies containing those pieces of text, not the whole account.

When you know what is causing it, working around is fairly simple, but in cases when you don't it can be a pain to figure out. If uploading an attachment is failing then maybe try using a service such as Pastebin. (p.s. That's an example not an endorsement - there are lots of similar sites and any of them should do.)

Regarding PMs, last I heard they require both users to have over 150 posts, but you can check that by going to bodge99's profile and looking for "Send a private message to bodge99" under "Contact Info".

Hi,

CluelessLass:

It would appear that we've reached a temporary hiatus... Never mind.. stuff happens!!
Anyway, just so we can proceed with your tablet problem.. If it helps, I'll provide a fully worked set of instructions that use my earlier method of modifying the installation Iso.

For this to be guaranteed to work (well, the installation part, anyway), I'll need to know the **exact** distro & version that you want to use on the tablet.
Something like Mint 21 Xfce or Mate should be fine.. Of course you can stick with the same version that you use on your laptop, if you prefer this.

More later..

B.

Hi, Bodge!

Sorry, it took me ages to remember the password for this account! No word yet from the admins on unblocking my other account (and I can't find any link for contacting you on your profile page, so it looks like you're correct about the 150 posts thing; come to think about it, that kind-of makes sense, really - otherwise, I suppose, you could get people joining and sending random direct messages to anyone and everyone).

My laptop seems to be working fine so far (thanks to you, of course!) so maybe I don't need to do anything more to it just now; if anything, it makes sense to leave it alone - if it ain't broke... and all that (famous last words; I'll be back tomorrow begging for help because it's crashed or something!)

As for the tablet, I already have a bootable USB with Mint 20.3 Cinnamon on it; I was too lazy to make one of the latest version but I know this USB 'works' because I've used it today to install Linux on a laptop for my mum. However, I think I remember reading somewhere (or being told on another forum when I was trying to install Linux for the very first time) that XFCE might be more appropriate for a computer with a smaller and/or older 'brain', which I'm assuming is the case with my tablet? Basically, you know better than me, so I'll be guided by you, if that's OK? Whichever you think best, I'll be (more than) happy with.

Thanks (again!).

Hi,

Laptop:
You can still increase the storage space available to Linux.. You still have some space that is allocated to Windows. You can reclaim this space if you want to. There is no rush.. as long as the laptop is working O.K. you can look at this at your leisure. Just ask here or PM me directly (when you can).

Tablet:
I've rechecked the spec. on this one. It would appear to be a fairly typical tablet with either 1 or 2GB memory, 16 or 32GB eMMC storage. It appears to have a Intel Z3730 or Z3735G SoC processor. The supplied OS is 32-bit Windows 8.x . As the OS is 32-bit, this implies that the UEFI firmware/bios is also 32-bit.
The processor is 64-bit and is a derivative of the Bay Trail family of processors.

What does all of this mean?

1 or 2 GB memory:
This is the system memory. It is also referred to as the system RAM (Random Access Memory). This RAM is a temporary storage area where the computer holds data it needs to retrieve quickly. RAM keeps data easily accessible so that the processor can quickly find it without having to go into long-term storage to complete immediate processing tasks. You may be able to increase the amount of RAM that your laptop has.. you almost certainly won't be able to increase your tablet's RAM

16 or 32GB eMMC storage:
Most types of computer have a way of storing information for longer-term access. Programs and data are stored here for later use. This information is not lost when the computer is powered off. The eMMC storage here performs the same function as a hard drive in a desktop computer. The difference is that this storage comprises a particular type of integrated circuit chip that is soldered to the main circuit board within your tablet. The storage chips used here are eMMC (Embedded MultiMedia Card).. these are essentially the same technology as used in SD (Secure Digital) cards, some solid-state drives (SSD) and some USB drives.

SOC:
A System On a Chip. It can be cheaper and more power efficient to combine a processor and some of it's support electronics within a single package. This also means that computer devices can be smaller.

UEFI firmware/bios:
Most folk refer to a small chip that is present on the main computer circuit board (aka motherboard) and the software that it contains as the BIOS.
This BIOS (Basic Input Output System) software is the first thing to run when the computer is powered on. This software performs basic computer initialisation.
Most UEFI computers that have 64-bit processors have 64-bit BIOS's.. The reason that some tablets exist with 64-bit processors and a 32-bit Bios is (AFAIK) due to Microsoft being unable to produce a 64-bit UEFI tablet BIOS in time for the release date of the first Windows tablet device specifications. This forced Microsoft to use a 32-bit version of Windows as they seemed unwilling/unable to use a 32-bit bootloader for 64-bit windows. A bootloader is the software that is used to start the OS. e.g. Linux Mint uses the Grub bootloader to start Linux.

What does this mean for my tablet?
As the tablet has a 64-bit processor, you can use a 64-bit OS. This means that you can use a modern version of Linux with all of its advantages.
The relatively limited amount of RAM implies that the use of a less resource "hungry" desktop environment might be a good idea. I'd personally consider Linux Mint XFCE or Mate.
Xfce has a slightly lower resource requirements.. so it might be an idea to start with this one.
As the BIOS is 32-bit, you'll need to use a installation mechanism that is capable of booting with a 32-bit UEFI BIOS.
This is not supplied with many Linux distro's these days, but it is very easy to add to any installation flashdrive (or other device).

I'll write up a worked guide which I'll post here in the next day or two. You'll need a flashdrive (8GB is more than ample). You may find it easier to install Linux if you can use a USB keyboard & mouse and possibly a USB wifi adapter (one known to work in Linux). This implies the use of a 4 port USB hub, depending on how many USB ports your tablet has.
You may be able to just use the tablet's screen digitiser (touchscreen) and onboard wifi.. The only way to find out is to try it! More details on this when you get there..

More soon..

B.

Hi, Bodge,

You're pretty much correct; according to the 'about' thingy, my tablet has:

Intel Atom CPU Z3735G @1.33GHz
Installed RAM 1.00GB
System type 32-bit OS, x64-based processor
and Windows 8.1

I've used the tablet with a Bluetooth keyboard, which I bought separately and isn't a genuine Toshiba one. Annoyingly, the tablet has just one USB, and it's a micro one at that (I didn't really know what I was doing when I bought it - all I cared about was it being a tablet!). I've got an adapter that, in theory, allows me to connect two USBs, the power cable and an SD card, although I've never tried using all four at once; the most I've done used is a USB mouse, USB memory stick and the power cable. I do have a USB keyboard but I've never tried to use it with the tablet (it's never occurred to me to try it!).

I really appreciate your help, but, as I've said before, please don't bust a gut to get back to me - whenever is fine with you is more than fine with me.
Thanks again!

Hi,

You should be able to use any Bluetooth keyboard/mouse/trackball etc. with the tablet.. The only minor problem is that Bluetooth only works when the OS has fully started.
You'll need a USB keyboard if you need to make any changes to any Bios settings, text input from within the EFI shell or to the boot environment. (I'll explain these if you actually need them.)

FYI, A USB hub isn't supposed to "back-power", i.e. allow power supplied to a port to be passed to the host.. Actually, most of the cheaper ones do, which is very useful if a tablet is charged from a single USB port and you want to use other USB devices at the same time.

Be careful using USB "splitters".. These are often used just to allow USB power (for charging) on multiple USB ports (i.e. no data lines). Those that do have power & data connections sometimes won't work properly with more than one device plugged in at once. The tablet (or computer) USB controller electronics "talks" to the USB devices and identifies what they are. Data transfer then occurs. If the attached devices "conflict" in any way then everything stops working.

If your splitter is actually a USB hub then all is good.. assuming that you have enough USB ports for your needs. If it turns out that you do need a bigger hub with more ports (been there.. done that!) then don't spend silly money on one. All you need is a 4 port hub (5 or 6 port might be useful in the future). You can get them with various USB plugs (micro-USB, mini-USB, USB-A or USB-C). You may need one or two USB adapters.. depending on what you need to connect. Supermarkets or shops that sell computer bits or phones should have what you need.
An alternative is Ebay or Amazon. You can normally also connect one USB hub to another.. I only do this when I'm really stuck though.

More later..

B.

Hi,

I'm just about to post the worked instructions on how to create a Linux Mint installation flashdrive for your tablet.
Just have a read of it for now. There is a lot of info here which I would like to explain in greater detail later on (when I've finished writing it).

More later..

B.

Linux Mint Installation Flashdrive:- Modified for 32-bit UEFI devices.

[ Everything is now fully tested. ]

Purpose Of Writeup:
To provide a worked series of instructions on how to create a Linux Mint installation flashdrive for use with a 32-bit UEFI/64-bit CPU tablet.

The tablet installation is fully standard with only one additional requirement. This is the installation of 32-bit EFI Grub to the tablet's newly installed Mint system.
The installation then boots, runs and updates as normal. I've also added an external shell EFI program.. Hopefully you won't need it, but it's very useful to have when you do.

Note: It is certainly possible to use an external USB drive (spinning rust or SSD). Basically, any read/write device that can be fitted into a USB caddy should be fine.
Be aware, an external mechanical drive will almost certainly need external power, either from it's own dedicated PSU or via a powered USB hub. This worked example uses a flashdrive. The process is identical for other devices.

A test installation was performed onto a Linx 10 tablet. This is a (64-bit SOC) Bay Trail device with a 32-bit UEFI firmware/BIOS. For ease of installation, I used a 4 port USB hub, a USB keyboard and a USB trackball.

Overview:
The contents of the Mint live Iso are extracted and copied to a pre-prepared flashdrive. 32-bit EFI grub is added to allow the flashdrive to be booted from a 32-bit UEFI system.
It is assumed here that the actual tablet processor is a 64-bit SOC (System-On-a-Chip, e.g. Bay Trail) or other discrete 64-bit processor.

It is possible to use the extra space on the flashdrive as an easy way to access extra files from the running Live system. Note: This is **not** "persistance". If you require this type of functionality then I would recommend that you perform a full installation of the system to the flashdrive directly. You could then update the flashdrive normally. Any specific installation from here would entail either a direct partition copy or a system filestructure copy to pre-prepared target partitions. Note: **Copies** of the partitions or filesystem **contents** are used.. Don't try to copy a running system. Specific details on either method on request.

I'll assume here that you are running Linux Mint or other Ubuntu derivative. Package install commands are given using 'apt'. I'll also assume that your Iso file is in your 'Downloads' directory. There is an optional (recommended) requirement to download a further file from Github. Ensure that both are saved in or moved to this location.

Note: In the following terminal command lines, comments are shown within braces and are not to be entered. In the following, open a terminal or enter the line into the currently open terminal. Press 'enter' after each line.
e.g.
To Work:

Download the External EFI Shell. 32 bit version.

Download this to your 'Downloads' directory. Rename the file to 'shell.efi'. You will copy this to /mnt later.
https://github.com/tianocore/edk2/bl...Ia32/Shell.efi

Rename 'Shell.efi' to 'shell.efi':
In a terminal on the host system.
Create The Flashdrive:

On the host system, install 32-bit EFI grub. This can be uninstalled later, if required.
Plug in your flashdrive to the host system.

You may need to install 'gparted'. On an Ubuntu/Mint based system install this with:
Run 'gparted' with:
Select the flashdrive: 'Gparted', 'Devices' or using the drop down combo box near to the top right side.
If your laptop drive is detected as '/dev/sda' then the flashdrive will probably be '/dev/sdb'.

The size of the detected device is a good clue. e.g. an 8GB flashdrive is detected as 7.22 GiB (a slight difference in measurement methods..).
If your flashdrive has been used before or preformatted then you will probably find that it has been automounted. Unmount (disconnect from the running system) by right clicking on the partition box (or Partition/Filesystem info line, below.) and select 'Unmount'.
Note: Using a gpt partition here improves compatibility with some of the "problematic" UEFI firmwares/Bios's that exist.

Now 'Device', 'Create Partition Table'. Chooses 'gpt' and apply.

'Partition' 'New'. In the 'Filesystem' box, change to 'fat32'. Now click on 'Add' button.
Click on the 'tick' (underneath 'Help') and 'Apply'.
When the operations have completed, right click on the 'fat32' filesystem. Click on 'Manage flags' and select 'boot' and 'esp'. Click on 'Close'.
Exit Gparted using 'Gparted, 'Quit'.

Transfer the installation Iso contents to the flashdrive:
Here, I'm going to use '/mnt' for the flashdrive and '/mnt1' for the Iso file.

Open a terminal and enter
Note: The flashdrive is a relatively slow device. When the command prompt returns (after entering the 'rsync' command), enter the 'sync' command. Now wait for the command prompt to return before proceeding. This ensures that all data has been written to the device correctly.

Cleanup the directory structure slightly. Install 32 and 64-bit EFI Grub to the flashdrive:
Power down, connect to tablet. Boot from the flashdrive.
See the accompanying notes for booting methods, including the basic use of the EFI shell.
Before you install, run 'gparted'
Select '/dev/mmcblk1'. If there is a choice, choose the '/dev/mmcblk' device that matches the capacity of your storage.
Now, delete all partitions one at a time or (more easily) just create a new GPT partition table.
'Device', 'Create Partition Table'. select 'gpt' and apply. Now quit Gparted.

Now 'Install'
If you see a message asking should partitions that are in use be unmounted?
Choose 'No'.
When at the 'Disks' section,
Choose 'Erase disk and install Linux Mint'

After the installation has finished, select 'Continue Testing:'

Ensure that you perform the following **BEFORE** you attempt to restart the tablet. If this is missed, then simply reboot the tablet from the flashdrive, mount the tablet partitions and then perform the following:

Assumptions: The tablet installation is standard. i.e. the first partition is the ESP/EFI (fat32 filesystem).
The second partition contains the Linux Mint system. The swap arrangements are either a swapfile on the system ext4 filesystem (The default for Mint) or is designated as the third partition (a swap partition).

Identify and mount the system and ESP/EFI partitions:
Look for 2 partitions on the same 'mmcblk' device. They will probably be '/dev/mmcblk1p1' and '/dev/mmcblk1p2'.
Open a terminal and enter:
Shutdown, unplug the flashdrive and reboot your tablet to test everything.

B.

Hi,

The flashdrive creation part is now fully tested.. I removed a couple of typos from the writeup. The tablet test install is to follow.

B.

Hi, Bodge,


Thanks for all this!

Hi, Bodge,

First up, DO NOT FEEL COMPELLED TO RESPOND TO THIS MESSAGE - IT'S CHRISTMAS, FOR GOODNESS'S SAKE AND I WILL NOT DIE IF I DON'T HAVE A WORKING TABLET!!!!

OK, now that's clear, I've just tried, and failed, to make a USB.

I'm wondering if it's because, as far as I know I'd set it up to install Bodhi Linux (this was before I'd made contact with you and I'd read somewhere Bodhi Linux might work on the tablet but I never managed to install it; can't remember why, possibly the tablet refused to recognise the USB?). I must have created the Bodhi Linux thing correctly, as when I plug the USB into my laptop it's listed as "Bodhi Linux". Before that, though, I'd used the USB to (re-)install Windows, whether on this laptop or the one I had before, I can't remember.

I'm going to try re-formatting the USB, in the hope of clearing Bodhi Linux and anything and everything else that might be on there, and have another go at following your instructions. However, it being Christmas, I'm afraid I might not have quiet time to myself for a couple of days, but when I do, I'll report back to you how I've gone on.

I just thought I'd let you know I have been doing my 'homework' and what the 'results' have been, and that I will update you when i have more to tell you.

Oh, and I wanted to wish you, too, a very, very Merry Christmas.

Thanks again,
The Clueless One.

Hi,

Flashdrive reformat problems are quite common. I was going to mention this in the accompanying notes for the guide.
Most folk just use the normal flashdrive formatting tools.. Mint has 'USB stick Formatter' and 'USB Image Writer'. These are actually the same tool that is just started with different options.

Anyway, the basic function of this tool is to create an 'msdos' partition table and a single partition on the flashdrive. It then creates a 'fat32' filesystem within this single partition. You are now free to transfer your 2,000 cat pictures to the flashdrive..

Using a flashdrive for Linux installation purposes sometimes leaves certain flashdrives in a condition where the normal USB tools won't reformat them properly.
Sometimes the tool seems to work, but then weird things happen where old filenames appear etc.. Most folk might then consider that the flashdrive is failing and then bin it.

**Before** you bin it, try 'gparted' on it.
Create an 'msdos' partition table, a full drive capacity partition followed by a single 'fat32' filesystem. This should return the flashdrive to normal use. If Gparted fails, then the flashdrive is almost certainly failing. i.e. view it as probably "iffy".

I've asked you to use Gparted and create a 'gpt' partition table. It strictly **shouldn't** be necessary to use 'gpt' rather than an 'msdos' one, but I've seen a few tablet Bios's (certain Bios versions only) that are more stable with 'gpt' prepared flashdrives (this applies just for the Linux install.).

And before anyone asks.. It's the 'lull before the storm' here..

Have a good one!

B.

Hi,

The tablet test installation has been completed. I've added a little to the writeup and corrected a couple more typos.

On the test Linx 10, all hardware works, apart from the screen autorotation.

B.

Hi,

Just a little more basic info that should help..
I'll split this up a little.. Don't worry, all you need is a general familiarity..

Linux storage device identification:

Linux doesn't use the concept of drive letters (e.g. Windows names drives as 'c:', 'd:' etc.)
In Linux, storage devices are connected (mounted) to somewhere within the system directory structure. This is performed by a mechanism called 'mounting'. If it is required that the device is to be disconnected, the relevant mechanism is called 'unmounting'.

In Linux, just about everything is seen as a 'file' or a 'process' by the running system. We'll ignore 'processes' for now. All of the hardware including storage devices such as disk drives or USB flashdrives that are connected to the system has an abstract representation as one or more files. These files are stored within the 'device' directory (i.e. '/dev') and are known as 'device files'.

The system name for the first detected computer storage device (e.g. a hard drive) will often be 'sda'. The 'sd' part of 'sda' comes from an older hardware connection standard called SCSI (Small Computer System Interface) disk.
If a second storage device (of a similar type) is detected by the system, it would be identified as 'sdb'. The next one as 'sdc' and so on.
The device files that represent these storage devices would be '/dev/sda', '/dev/sdb' ... etc.

As you may remember, a hard drive has to be prepared with one (or more) partitions. Each of these partitions may then be formatted with a filesystem. It is the filesystem that actually contains all of the files.

The first partition on the first detected storage device will have a device file of '/dev/sda1', the second partition on the first drive as '/dev/sda2' and so on.

Storage Device identification:
Typical examples:

Type: Device Name:
HDD/SSD: sda - The first detected mass storage drive.
eMMC: mmcblk0 - The first eMMC drive. Typically used in tablet computers etc.

In the same way as detailed above, each drive type can hold one or more partitions:

To recap:
For HDD/SSD: The first partition on the first drive is 'sda1', the second is 'sda2' and so on.
eMMC: The third partition on the second eMMC drive is 'mmcblk1p3' and so on..

The device files for the above would be '/dev/sda1' and '/dev/mmcblk1p3'.

HDD - Hard Disk Drive. This normally refers to a mechanical drive but can refer to any type of disk drive.
SSD - Solid State Drive. A generic term for electronic (i.e. non-mechanical) drives.
eMMC - Embedded MultiMedia Card.

Referring to the device file names, where there is a number, drives normally count from 'zero' and partitions count from 'one'.
Be aware, there are other types of mass storage devices, each having specific designations.

The important thing to remember is that the drive designations are transient and may change between system boots/reboots.
The act of plugging in a flashdrive may change how the drive is identified by the system on the next boot.

Example: If your main hard drive is identified as 'sda', a plugged in flashdrive could be identified as 'sdb'.
If you now reboot, with the flashdrive still connected, it's now possible for the flashdrive to be identified as 'sda' and the hard drive as 'sdb'.
If the system's startup files are 'hard-coded' to use 'sda' then the system won't boot.. oops!

Because of this, most modern Linux's refer to a filesystem by its UUID. UUID stands for 'Universally Unique IDentifier' and is a unique series of hexadecimal numbers that is assigned to device partition's **filesystem**. (Yes, this is a **filesystem** UUID. There is such a thing as a partition UUID, but we're not going to be using this here.).

Examples of where these UUIDs are used. Grub, one of the bootloaders used in Linux (in its system configuration file 'grub.cfg') and the file system table 'fstab', located at '/etc/fstab'.

An example UUID for an Ext4 filesystem is 60a5679d-b728-4f5c-8b90-2e1fb0eb1efc . These UUIDs are random in nature and are assigned when a partition is formatted.

More later..

B.

Hi, Bodge,

Thanks for the advice about 'cleaning' the flash.

I've now managed to get as far as this:
------ {Copy the Iso contents to the flashdrive. At least one hidden file/directory exists..}
sync.
(I've removed the instructions/code(?) in case it gets me blocked again, but as far as I can tell these braces only appear once in the 'instructions' so I hope you understand which bit of them I mean here.)

But when I type in the next bit, I get this:

cp: cannot stat '/home/alisanna/Downloads/shell.efi': No such file or directory

I've tried umpteen times, copying and pasting your instructions and typing them in directly, but get the same result each time. I have no idea whether I hit some key or other by accident or if Terminal decided to try to give me a helping hand, but one time, after several attempts, I got this as well:

Command 'cp:' not found, did you mean:

command 'cpm' from deb cpm (0.32-1.2build2)
command 'cpu' from deb cpu (1.4.3-12)
command 'cpr' from deb node-cpr (3.0.1-1)
command 'cp' from deb coreutils (8.30-3ubuntu2)
command 'cpp' from deb cpp (4:9.3.0-1ubuntu2)
command 'cph' from deb conda-package-handling (1.6.0-2build1)

Try: sudo apt install <deb name>

I'd already downloaded the shell.efi thing, but I wondered whether there might be an issue with that, so I downloaded it again, but it's made no difference. However... when it's downloaded, it's automatically saved as Shell.efi - I didn't have to re-name it; could that make any difference?

I don't know if this is relevant, too, but it took ages for the command prompt to re-appear after I told it to rsync, but it reappeared almost straightaway after I told it to sync. (You know, I'm wondering if the 'problem' before was that I wasn't waiting long enough for the command prompt to re-appear, as it really did take forever...)

So that's where I am at the moment. Like I've said before, please don't feel obliged to bust a gut to respond asap, especially during the whole festive season thing; it's really kind of you to be helping me, so I'd rather you did it at your convenience, not mine!

Hear from you whenever...
And Happy New Year!
Clueless