Installing on a 3.0 USB Stick

Non release banter
Lucas
Black ninja
Black ninja
Posts: 42
Joined: 25 Apr 2015, 01:58
Distribution: Porteus 3.1
Location: São Paulo, Brazil

Re: Installing on a 3.0 USB Stick

Post#31 by Lucas » 16 Mar 2017, 21:29

Hello everyone,

I tried the delay=30 and the kernel posted by Brokenman and it didn't work out on the Sandisk, the MicroSD is working perfectly fine with the kernel suggested by him. I'm really considering buying a pen drive from another brand or exchanging it. If anyone has any ideas....

Best regards,

Lucas.

User avatar
Ed_P
Contributor
Contributor
Posts: 3403
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Installing on a 3.0 USB Stick

Post#32 by Ed_P » 16 Mar 2017, 22:51

Lucas wrote: and the kernel posted by Brokenman
Lucas did you update the kernel as noted here?
brokenman wrote:When updating a kernel you MUST replace both the vmlinuz (kernel) and the 000-kernel.xzm (kernel firmwre and modules) files.
Ed

Lucas
Black ninja
Black ninja
Posts: 42
Joined: 25 Apr 2015, 01:58
Distribution: Porteus 3.1
Location: São Paulo, Brazil

Re: Installing on a 3.0 USB Stick

Post#33 by Lucas » 20 Mar 2017, 17:35

Hi Ed,

I just went into the folder http://dl.porteus.org/x86_64/kernel/porteus-4.9.12/ downloaded everything in it and put them in the /base folder. When asked to replace I choose "yes to all". To say the truth, I don't know why with this files my wifi isn't recognized and my screens boots blurred (in the MicroSD, I installed in my microSD and Sandisk USB). In the Sandisk USB, it continued giving the same error message (the SCSI one). Any ideas?

Best regards and have a nice week,

Lucas.

User avatar
Ed_P
Contributor
Contributor
Posts: 3403
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Installing on a 3.0 USB Stick

Post#34 by Ed_P » 20 Mar 2017, 19:25

Lucas wrote:downloaded everything in it and put them in the /base folder.
:(

Try these locations instead.

vmlinux -> /boot/syslinux
000-kernel.xzm -> /porteus/base
other xzm files -> /porteus/modules

:)

How big are each of the USB sticks and what are they formatted as?
Ed

Lucas
Black ninja
Black ninja
Posts: 42
Joined: 25 Apr 2015, 01:58
Distribution: Porteus 3.1
Location: São Paulo, Brazil

Re: Installing on a 3.0 USB Stick

Post#35 by Lucas » 22 Mar 2017, 18:30

Hi Ed,

It worked as a charm in the MicroSD, on the Sandisk it gave the same message (SCSI one). The MicroSD is formatted in ext4 with 64gb and the Sandisk USB is formatted in ext4 with 32gb.

Regards,

User avatar
Ed_P
Contributor
Contributor
Posts: 3403
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Installing on a 3.0 USB Stick

Post#36 by Ed_P » 22 Mar 2017, 20:23

Excellent. :Yahoo!:

With the SanDisk one try adding acpi=off as a boot option.
Ed

Lucas
Black ninja
Black ninja
Posts: 42
Joined: 25 Apr 2015, 01:58
Distribution: Porteus 3.1
Location: São Paulo, Brazil

Re: Installing on a 3.0 USB Stick

Post#37 by Lucas » 27 Mar 2017, 13:45

Hi Ed,

As you can imagine, I'm advancing with the MicroSD and stuck with the USB. I followed the acpi suggestion. Porteus got stuck at the second line after booting, the one that says that it is loading initrd.xz. It stopped before the point that was stopping.

Thanks and regards,

rchase
Samurai
Samurai
Posts: 158
Joined: 10 Jan 2016, 17:26
Distribution: Porteus 3.2.2 xfce x64
Location: Denver, Colorado

Re: Installing on a 3.0 USB Stick

Post#38 by rchase » 15 May 2017, 04:38

I am having a problem similar to Lucas'. With many old computers having only USB 2.0 ports able to run Porteus quite well, being able to take advantage of the superior speed and backwards compatibility of USB 3.0 drives is extremely desirable. I also want to take advantage of Porteus' ability to use multiple partitions on a flash drive to format such drives with a large Windows-accessible partition for data while booting Porteus off a smaller one.

I installed 64-bit xfce to a microSD, creating a 2GB FAT32 partition, a 4.4 GB ext4 partition (to which I installed Porteus), and a 1GB linux swap partition. I copied the /boot directory to the fat32 partition, modified porteus.cfg to use "from=/dev/sda2" and ran the installer script from there. This works beautifully on an eleven-year-old machine (USB 2.0 only) with an Intel Core Duo processor with the HD unplugged. The machine only has 1GB of RAM; it can run Windows 10, but the old Hitachi HD is slow and Windows just makes it thrash -- takes about a minute to boot, too. Porteus boots in about half that off of a Class 6 card in a USB 2.0 adapter and in about twenty-four seconds (to my modified desktop) off a Sandisk Ultra UHS1 microSD in a USB 3.0 adapter (and in an equal amount of time when I boot Porteus installed to an ext4-formatted USB 3.0 flash drive). I can boot the same drives on the desktop I built two years ago and Porteus works similarly well. I see the advantage of "UUID:" in "from=" and "changes=" to make flash drives boot from their own Porteus data irrespective of their letter assignments and modified my porteus.cfg files accordingly.

On a USB 2.0 drive, I can create either a FAT32 or NTFS partition, copy the /boot directory there, run the installer from there, and have a USB drive Windows can use which will also boot Porteus in either a USB 2.0 or USB 3.0 slot. I can also just install Porteus to the second partition on a USB 2.0 drive, run the installer, and the drive will boot Porteus (with the first partition visible to Windows). I want to be able to do the same with USB 3.0 drives, but the first procedure (copying /boot and installing the bootloader to the first partition) makes a drive which will only boot in a USB 3.0 slot; in a USB 2.0 slot, the loader can't find the rest of the OS and fails with "Porteus data not found". Trying to boot Porteus installed to the second partition of a USB 3.0 drive results in "Porteus data not found" in both USB 2.0 and USB 3.0 slots. Porteus installed to the first partition of an ext4-formatted USB 3.0 drive (with a swap partition) boots fine from USB 2.0 and USB 3.0 slots, but most of the drive is useable only by Porteus or other Linux distributions.

Feel free to move this, but it would be useful to be able to use most of USB 3.0 flash drives for Windows-accessible storage and just a few gigabytes to boot Porteus. This is easy to do on USB 2.0 drives, but I haven't succeeded on USB 3.0. Is there a fix?

User avatar
brokenman
Site Admin
Site Admin
Posts: 5652
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Installing on a 3.0 USB Stick

Post#39 by brokenman » 21 May 2017, 15:52

I will need to purchase a USB3 device to test this. It seems strange since USB3 devices have backwards compatibility with USB2 ports. It should simply act as a USB2 device. I see you manage to boot until the boot menu which confirms that the USB device is indeed being located and used correctly. The problem appears when the system tries to detect the second partition.
How do i become super user?
Wear your underpants on the outside and put on a cape.

rchase
Samurai
Samurai
Posts: 158
Joined: 10 Jan 2016, 17:26
Distribution: Porteus 3.2.2 xfce x64
Location: Denver, Colorado

Re: Installing on a 3.0 USB Stick

Post#40 by rchase » 25 May 2017, 15:06

brokenman wrote:I will need to purchase a USB3 device to test this. It seems strange since USB3 devices have backwards compatibility with USB2 ports. It should simply act as a USB2 device. I see you manage to boot until the boot menu which confirms that the USB device is indeed being located and used correctly. The problem appears when the system tries to detect the second partition.
My problem was bad flash -- Sandisk tells me they never warranted my Ultra Fit to boot an OS! In trying to boot Phoenix OS off my Kangaroo, I discovered that although the loader could never detect the installation when left to its own devices, if I unplugged the drive during the process and plugged it back in, Phoenix' loader could then see the stick and continue booting. It would be interesting to know precisely what is going on; the drive appears to function properly -- except when trying to boot from it.

Post Reply