LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Laptop and Netbook
User Name
Password
Linux - Laptop and Netbook Having a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).

Notices


Reply
  Search this Thread
Old 01-18-2023, 01:29 PM   #61
escertdez
LQ Newbie
 
Registered: Jan 2023
Posts: 8

Rep: Reputation: 0

Good day,

unfortunately I appear to have bricked the tablet beyond any hope (my hope, anyway). It was a good run.

Everything was going well, I performed the linux mint 21.1 installation according to the instructions, when I rebooted the tablet, I get a message saying "ubuntu boot failed" (attached)

No problems I think, I'll just try again. I created a gparted usb drive to try and boot into that, and it did, then froze at the debian terminal after failing the GUI.
I tried rebooting and it could never boot from this drive again, errors: "invalid sector size 0," then "you need to load the kernel first"
The gparted drive i created with Rufus using the GPT option, because i know that has worked before, i have cleared the drive once to install androidx86 (which was working poorly thus the linux upgrade).

I then tried booting from the original mint drive that was working and installing the system before. It goes to grub, but all the options give the attached error message, with the first and second mint option giving it twice. In the next attachment I tried "ls" in the grub console with the same effect.

"Invalid sector size 0" sounds like it's corrupting the usb drives somehow, which would make sense considering they both booted.. once. The problem persisted through a reinstall of both .isos on both drives.

I probably messed something up in the last code block in the guide (one with fdisk command), even though i double checked everything.

Was my tactic of attempting gparted with the intention to erase everything on the mmc even the correct way to try and fix this? If it wasn't obvious by now I don't really know what I'm doing :(

I am considering:

a. putting the usb drives through chkdsk or some other drive utility to try and fix the sector size then trying to get mint to boot correcly like it used to.
b. chaotic evil - using a windows 8 recovery/install .iso to see if it does anything at all, if it does, try nuking the contents of the mmc or..
c. runing over the tablet with my car in a dramatic fashion

Let me know if you have any ideas,

Dez
Attached Thumbnails
Click image for larger version

Name:	bootfail.png
Views:	9
Size:	46.0 KB
ID:	40276   Click image for larger version

Name:	mintdrive.png
Views:	9
Size:	32.9 KB
ID:	40277   Click image for larger version

Name:	grubls.png
Views:	7
Size:	28.9 KB
ID:	40278  
 
Old 01-18-2023, 03:03 PM   #62
bodge99
Member
 
Registered: Oct 2018
Location: Ashington, Northumberland
Distribution: Artix, Slackware, Devuan etc. No systemd!
Posts: 368

Rep: Reputation: 66
Hi,

Boot failures on a newly installed system:

It sounds like you've been unlucky. Now to find out exactly what has gone wrong.

I'd suggest recreating your installation flashdrives from scratch.

See post No.42 in this thread for an explanation of how I ensure that any flashdrives are properly wiped.
Now follow post No.38 to create a Linux Mint flashdrive with 32-bit efi Grub support.

You can test this flashdrive by booting any Uefi computer with it.

Now boot the tablet from this flashdrive, either using your boot override key, from your Bios boot section or from the EFI shell.

Before installing Mint to the tablet, use 'gparted' to erase the tablet's eMMC storage by creating a new 'gpt' partition table.
Now create a 200MB partition, formatted to fat32 (for the ESP/EFI filesystem). Use the rest of the space for the Linux system (Mint uses ext4 by default).

At the 'disks' section of the installation, choose 'Something else'. At the 'Installation type' screen, ensure that the 200MB partition is marked as 'efi and the larger partition as 'ext4'.
Now complete the installation as normal.. Don't forget to install 32-bit efi Grub before you finally reboot.

If you could report any errors or problems here and we'll see how to work around or fix them..

Any questions.. just ask here.

Good luck!

B.

Last edited by bodge99; 01-18-2023 at 03:55 PM.
 
Old 01-19-2023, 05:46 AM   #63
bodge99
Member
 
Registered: Oct 2018
Location: Ashington, Northumberland
Distribution: Artix, Slackware, Devuan etc. No systemd!
Posts: 368

Rep: Reputation: 66
AntiX Installation Flashdrive:- Modified for 32-bit UEFI tablet devices.

The AntiX Iso has 32-bit EFI grub installed. The standard flashdrive iso writing tools create a valid bootable flashdrive that works fine for the very vast majority of computers that I've tested it on. However, I've found one 32-bit UEFI tablet where the flashdrive boot fails. As this tablet doesn't have an internal EFI shell, the boot attempt just locks the tablet, requiring a hard reset.
I then prepared a flashdrive in the same way as the previous modified Linux Mint flashdrive. This flashdrive boots correctly on every 32-bit UEFI device tested.

I've rewritten the original writeup so that this can be used without the need to refer to the previous Linux Mint based one.

Purpose Of Writeup:
To provide a worked series of instructions on how to create a Antix Linux installation flashdrive for use with a 32-bit UEFI/64-bit CPU/SOC 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 AntiX system.
The required 32-bit Grub Efi files are already provided, they just need to be installed into the running 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 and two no-name generic 8" tablets. These are (64-bit SOC) Bay Trail devices with 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 AntiX live Iso are extracted and copied to a pre-prepared flashdrive.
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 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: The Root password for the Antix live environment is 'demo'.

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.
Code:
sudo su {Become root for all commands in this terminal until 'exit'.}
exit    {Become a normal user again.}
exit    {Close the terminal.}
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':
This is done because some early tablet Bios versions will only recognise the efi shell executable if its filename is fully lower case.
In a terminal on the host system.
Code:
mv ~/Downloads/Shell.efi ~/Downloads/shell.efi
Create The Flashdrive:

On the host system, install 32-bit EFI grub. This can be uninstalled later, if required.
Note: Here, I'm assuming that the host system is a Debian/Ubuntu/Mint system or derivative that uses 'apt' package management. Alter this to use your specific package manager as required.
Code:
sudo apt install grub-efi-ia32-bin
Plug in your flashdrive to the host system.

Most live Iso's already have 'gparted' installed, so run 'gparted' with:
Code:
sudo gparted
If 'gparted' is not installed, then install it using your local package manager.
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 slightly "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
Code:
sudo mkdir /mnt1  {Create a second working directory.}
sudo mount ~/Downloads/antiX-22_x64-full.iso /mnt1 {Using AntiX 22 here.}
sudo mount /dev/sdb1 /mnt {Mount the flashdrive to /mnt}

sudo rsync -a /mnt1/ /mnt {Copy the Iso contents to the flashdrive. At least one hidden file/directory exists..}
sync {This will take a few minutes. Wait for the command prompt to return.}

sudo cp ~/Downloads/shell.efi /mnt {Copy the external shell program to the flashdrive.}
sudo umount /mnt /mnt1  {Yes, the command is 'umount' **NOT** 'unmount'.}
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.

Power down, connect to tablet. Boot from the flashdrive.

Please see the accompanying AntiX installation notes. (coming shortly).

B.
 
Old 01-19-2023, 02:06 PM   #64
escertdez
LQ Newbie
 
Registered: Jan 2023
Posts: 8

Rep: Reputation: 0
Hello,

I have unfortunately not managed to recover the device. After clearing the eMMC first and resetting BIOS to default (making sure secure boot is still disabled), I tried to boot into a new mint .iso (tested on different PC, worked fine), but got the "invalid buffer alignment" error, in the same way as the previous "invalid sector size".

The second picture is trying to boot gparted to see if anything "linux" works. It gave a bunch of errors and failed boot, and the keyboard didn't work so I couldn't even attempt to use the provided console.

The issue being with the ISO drive is very unlikely by now so I am wondering what I did to make the "things that happen before the iso" not work.

I'd like to mention that at the last point of the installation (mounting the mmcblk's) I didn't execute any commands other than provided. (not sure if relevant)

Is it corrupt GRUB? That would explain how windows works and Linux suddenly doesn't. However GRUB, aside from the one on the boot drive, shouldn't exist (the eMMC was cleared)

I am so lost. What could have made the tablet suddenly dislike Linux boot drives?
The fact that the drive doesn't appear to be the issue complicates things a lot since the BIOS has exactly 2 buttons and no advanced settings, and it's impossible to update.

I will keep trying a couple more times and I wish everyone better installation luck than what I've had so far,

Dez
Attached Thumbnails
Click image for larger version

Name:	Screenshot_69.png
Views:	10
Size:	66.4 KB
ID:	40307   Click image for larger version

Name:	Screenshot_70.jpg
Views:	12
Size:	95.5 KB
ID:	40308  
 
Old 01-19-2023, 03:38 PM   #65
bodge99
Member
 
Registered: Oct 2018
Location: Ashington, Northumberland
Distribution: Artix, Slackware, Devuan etc. No systemd!
Posts: 368

Rep: Reputation: 66
Hi,

[[EDIT: I'm placing this here as I feel that it is important to state this.
Escertdez: I do understand how frustrating this can be.. Please, if it's at all possible, don't get disheartened and give up.
Your particular problem is quite likely to be caused by some sort of misunderstanding or misconfiguration somewhere.
I'm quite willing to offer any help that I can.
One step at a time..]]

I'm a little unsure as to exactly how and what you are attempting to boot..

Can you perform the following and post the results here please.

Connect your installation Iso to a working Linux computer.
In a terminal:
Code:
sudo fdisk -l
You should be able to identify your flashdrive.. I'll assume 'sdb' for this.
Code:
sudo mount /dev/sdb1 /mnt
tree -d /mnt
If you don't have the 'tree' tool installed, then just install it with:
Code:
sudo apt install tree
Now repeat the command, this time redirect the screen output to a text file.
Code:
tree -d /mnt > mylisting.txt
When you've finished, unmount the flashdrive with:
Code:
umount /mnt
If you could post the contents of 'mylisting.txt' here please.

This file should show a directory listing (not the files) of the installation flashdrive. I'm looking for the presence of 32-bit efi Grub.

B.

Last edited by bodge99; 01-19-2023 at 04:09 PM.
 
Old 01-19-2023, 04:16 PM   #66
escertdez
LQ Newbie
 
Registered: Jan 2023
Posts: 8

Rep: Reputation: 0
Hi again,

I am back in Mint, brand new drive, brand new install. This time i added all the 32 bit shell name variants.

I had a 200MB fat32 partition, 1GB of swap area and the rest was ext4 with the root "/".
edit: in the "Device for boot loader installation" i chose the 200MB fat32 partition.

It's currently installing. Do i stil have to mount the system before the last step of GRUB as before or was it already done with this manual installation type?

Thank You for the help,

Dez

Last edited by escertdez; 01-19-2023 at 04:19 PM.
 
Old 01-19-2023, 05:15 PM   #67
bodge99
Member
 
Registered: Oct 2018
Location: Ashington, Northumberland
Distribution: Artix, Slackware, Devuan etc. No systemd!
Posts: 368

Rep: Reputation: 66
Hi,

If you are talking about installing 32-bit efi Grub, then do this after the installation has finished. I recommend that you follow the guide exactly as the Grub install command is written to install everything to specific locations. It's easier to mount the new system partition and ESP/EFI to '/mnt' and then install Grub.

This last part, from the guide:
Quote:
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:
Code:
sudo su
fdisk -l {I'll assume /dev/mmcblk1p1 for the ESP/EFI and /dev/mmcblk1p2 for the system.}
mount /dev/mmcblk1p2 /mnt {Mount the system.}
mount /dev/mmcblk1p1 /mnt/boot/efi {Mount the ESP/EFI partition to the correct location.}

apt install grub-efi-ia32-bin {Install 32-bit efi Grub to the flashdrive host system}
{Now install 32-bit EFI grub to the tablet.}
grub-install --boot-directory=/mnt/boot --efi-directory=/mnt/boot/efi --target=i386-efi   
cp /cdrom/shell.efi /mnt/boot/efi  {Copy the external shell program to the tablet.}
Shutdown, unplug the flashdrive and reboot your tablet to test everything.
I use (and recommend) the '/mnt' directory for this sort of job. The advantage is that, however the target partitions are laid out on the target drive, I can use the same (or similar) command to perform the same job. I find this way to be much less error prone.

I'll post something that should help regarding Grub.. How to install, reinstall, tweak and fix.

More later.

B.
 
Old 01-19-2023, 05:40 PM   #68
escertdez
LQ Newbie
 
Registered: Jan 2023
Posts: 8

Rep: Reputation: 0
Hi,

The reason I was confused is the original drive was booting into desktop on my laptop so I thought the configuration was fine. It was not, indeed, fine.

I have good news: it has successfully rebooted into Mint. For now there is one issue and that is the camera light (pointlessly bright) stayed on as it is controlled by software and not by camera power, which is dumb. Tape time I guess.
The other issue is the login screen: there is no easy way to enable an on-screen keyboard to type the password with. I guess autologin is a solution, however insecure.

Apart from those everything important works: the touch is very well calibrated, the wireless connectivity is good, haven't tested the audio yet.

Thank you Bodge for doing your best to help even though the problem from the beginning was some dumb misconfiguration.

I'll come back to this thread with a whole list of working/broken stuff on the Toshiba Encore WT8-A soon™,

Dez
 
Old 01-19-2023, 06:00 PM   #69
bodge99
Member
 
Registered: Oct 2018
Location: Ashington, Northumberland
Distribution: Artix, Slackware, Devuan etc. No systemd!
Posts: 368

Rep: Reputation: 66
Hi,

Well done!! I'm very pleased to hear that you have succeeded!!
Have a look at 'onboard'.. It should be in the Mint repos.
You can configure this one to autostart and popup when a text input field is detected.

We should be able to turn your camera/LED off.. I'll look into this later.

B.
 
1 members found this post helpful.
Old 01-21-2023, 10:38 AM   #70
escertdez
LQ Newbie
 
Registered: Jan 2023
Posts: 8

Rep: Reputation: 0
Hello and welcome..

to my not very comprehensive writeup about the usability of Linux Mint 21.1 on the Toshiba WT8-A.

---SCREEN---

To start off there is a potential dealbreaker as the tablet is only functional in portrait mode. At least "out of the box".
That doesn't bother me very much since i plan to use it in portrait mode anyway as a poor man's comic/book reader.
I tried using xrandr to rotate (blank screen) as well as system options (attached).
The red outline is roughly the screen border, and it is trying to "put the landscape screen into portrait", this can be tested with lower resolutions, which don't crash. The touch also needs recalibration in those other resolutions.

I tried rotating the screen right first, then setting the landscape resolution, but that didn't work either.

Worth noting that when the tablet had androidx86, the screen rotation worked.
As this is a desktop system I wasn't expecting support for the automatic rotate, but didn't expect the landscape to not work at all.

---AUDIO & VIDEO---

The audio outputs are reversed, as in the speakers work when you plug in headphones. I'm sure this could be fixed easily if anyone wants to use audio.

The microphones don't work at all, or are too quiet to register on the the test site graph i used.

The cameras are a lost cause, they barely worked in windows, they require a weird intel driver (pretty sure that's what that intel USB hub in system info is).

---OTHER---

The system appears to go to sleep correctly (doesn't shut off the blue webcam light though).

There isn't also any excessive battery drain.
The battery is also somehow still at 82% life despite age and neglect, impressive.

There is accessibility options on the lock screen that give you an on screen keyboard.
The button is small so i didn't see them at first.

Onboard is working, not perfectly, but definitely deserves the "better than nothing" award.

I attached a file with the system information if anyone wants to take a look,

Dez
Attached Thumbnails
Click image for larger version

Name:	IMG_20230121_163335-min-min__01__01-min__01 (1).jpg
Views:	9
Size:	232.9 KB
ID:	40316  
Attached Files
File Type: pdf system info.pdf (60.9 KB, 8 views)

Last edited by escertdez; 01-21-2023 at 10:40 AM.
 
Old 01-21-2023, 12:04 PM   #71
bodge99
Member
 
Registered: Oct 2018
Location: Ashington, Northumberland
Distribution: Artix, Slackware, Devuan etc. No systemd!
Posts: 368

Rep: Reputation: 66
Hi,

Again, well done with your installation efforts.. and many thanks for the pdf.

If you want to look a bit more closely at your hardware..
It would also be a great help if you could post the results here.
I'll redirect all screen output to a text file.
Note: You might have some of these tools installed already.. I'm not near a Mint machine to check..
In a terminal:
Code:
sudo apt install hwinfo i2c-tools lshw pciutils usbutils
cat /proc/cpuinfo > mySystem.txt

sudo dmesg >> mySystem.txt
sudo hwinfo >> mySystem.txt

sudo lspci >> mySystem.txt
sudo lshw >> mySystem.txt

sudo lsusb >> mySystem.txt
find /sys/devices/platform -name name -printf "%p\t" -exec cat {} \; >> mySystem.txt
Line 1: Installation of a few tools. You can uninstall them later if you so wish.
Line 2: In depth CPU/SOC info.
Line 3: Kernel messages.
Line 4: This generates a system overview generated from probed hardware.
Line 5: This lists all PCI hardware.
Line 6: This lists hardware.
Line 7: This displays info about USB buses and devices.
Line 8: This produces a list of ACPI devices which are not handled by the current kernel.

Many thanks.

B.
 
Old 01-21-2023, 02:21 PM   #72
escertdez
LQ Newbie
 
Registered: Jan 2023
Posts: 8

Rep: Reputation: 0
Hi,

here are the requested files (hopefully the links don't get blocked):

dmesg: https://pastebin.com/xdbw6L2T

everything else: https://pastebin.com/fG1Q87yF

Let me know if you need anything else, I'm happy to perform experiments on the system.
This is also the first post from the tablet, got onboard fully configured.

Until next time,

Dez
 
Old 01-21-2023, 03:40 PM   #73
bodge99
Member
 
Registered: Oct 2018
Location: Ashington, Northumberland
Distribution: Artix, Slackware, Devuan etc. No systemd!
Posts: 368

Rep: Reputation: 66
Hi,

Thanks very much for the files.. Much appreciated!

Could I ask for one more thing.. A list of the loaded kernel modules. You can generate this with:
Code:
sudo lsmod
It might be possible to disable the "always on" LED (camera on indicator ?) by blacklisting the relevant kernel module, if the camera is actually initialised this way. I'll look closer at this one.

More later.

B.
 
Old 01-22-2023, 05:13 AM   #74
escertdez
LQ Newbie
 
Registered: Jan 2023
Posts: 8

Rep: Reputation: 0
Hi,

attached is the lsmod.txt You requested.

The camera LED seems to be on by default, disabling is left up to the operating system.
I remember when this had Windows, when booting it would turn on, then get disabled as soon as Windows started to load.

I also might've forgot about the annoying hardware issue that made me delegate this tablet to the "charge to half and turn off for years" pile of devices.

Either way it would be a shame to not use it after all this work so I am still giving it a chance, it's not used for mission critical work stuff after all.

For anyone interested, the issue at hand is the so called "ghost touch".
The screen holds a touch input in a random place. Sometimes there is more, it was easily visible on Windows with the touch bubbles. When it goes over the multitouch limit of 5, touch stops working.

It's quite funny how when the device was under warranty, it was sent for service because of this. They managed to replace every component except the screen (the suspect here).

Off to use the tablet while the screen works,

Dez
Attached Files
File Type: txt lsmod.txt (8.1 KB, 9 views)
 
Old 01-22-2023, 07:47 AM   #75
bodge99
Member
 
Registered: Oct 2018
Location: Ashington, Northumberland
Distribution: Artix, Slackware, Devuan etc. No systemd!
Posts: 368

Rep: Reputation: 66
Hi,

Escertdez:
Many thanks for the file.. This will help with the Linx 10 setup and tweaking.
I too have a big "getroundtoit" pile.. and I also want to use the Linx 10 as a pdf reader.

I remember (almost) fixing a "ghost touch" problem with a Chinwa (sp. ??) 8" tablet. Here, I was able to add a watchdog timer that reset the digitiser every 5 seconds after the last touch was registered.
The problem eventually had a manufacturer fix with a Bios upgrade. I also found out later that this particular problem occured with the specific type of digitiser that was fitted in a production run.
Essentially, a compatible digitiser from an alternative supplier wasn't actually 100% compatible.

I'm currently revamping my tablet work. I'm using an external SSD so that I can work on AntiX and Mint 21.1 . There is also space for system backups.
I'll post a writeup of how I did this next.. It's a slightly "non-standard" method.. but it fits the way I work. Hopefully, the techniques used here will be of use to others.

More soon.

B.

Last edited by bodge99; 01-22-2023 at 07:50 AM. Reason: missed a bit.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Can I make a USB hard drive bootable with same procedure to make USB stick bootable? Tem2 Linux - Hardware 1 02-16-2019 08:25 AM
Please suggest a netbook (tablet with a keyboard) AllWinner bootable without any blobs romankqsok Linux - Hardware 8 02-12-2019 12:53 AM
Use desktop with usb-usb cable as external bootable optical drive for netbook seancarver Linux - Laptop and Netbook 3 11-02-2009 09:38 PM
Making a USB stick bootable from a bootable cdrom cwwilson721 Slackware 2 10-23-2009 09:18 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Laptop and Netbook

All times are GMT -5. The time now is 02:25 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration