STICKY: PINN - An enhanced version of NOOBS.

[dvaitman]

Have you tried using Raspbian on an SD card and plugging you mSata drive in to check it is recognised in there as a plain data drive?

Not exactly, but I've installed raspbian on that drive directly and it run normally, no issues, no need for an SD card.
I even managed to get TinkerOS (for the asus tinkerboard) to work with it.
My google research tells me that can't mount the usb, which is weird because if I enter the recovery mode, it definitely detects the drive and the already installed OS. I'm no expert in linux so I'm a bit out of my depth trying to address this. Any help is appreciated

[dvaitman]

ok.. new attempt tonight.

Decided to try and decouple the mSATA card (from the piDesktop) and connect them with a normal USB cable, also powering both from separate power sources...
managed to boot into raspbian once, did the Rasp configuration and reboot. Now it won't boot into raspbian. I think error 32 has something to do with mounting the usb drive.
I rebooted back into PINN and it didn't recognised the mSATA drive, with PINN running I unplugged and plugged the usb drive (mSATA) and it appeared as a destination to add OS. So decided to boot into raspbian. I guess it "reboots" again because got the same error as before. So... any ideas?
something I can do? maybe in the cmdline.txt file? or some config file?

[procount]

Have a read of this topic -> viewtopic.php?t=53832 for info.

I suggest loading a plain Raspbian image on your SD card.
Then with your mSata drive connected, log the output of dmesg and lsusb etc. as below
Open a terminal and type the following 3 commands after the '$':

$ sudo sh -c 'dmesg >/boot/dmesg.txt'
$ sudo sh -c 'lsusb >/boot/lsusb.txt'
$ sudo sh -c 'tree /sys/bus/usb >/boot/tree.txt'

You can then safely power off, remove your SD card, insert it into a PC and copy the 3 text files off the SD card and post them here to see if it identifies any other issues.

You could also try using NOOBS, installing Raspbian onto your mSATA disk and see if that suffers from the same errors.

[dvaitman]

Thanks for your advise and support. Thanks for that info too, had a quick read but I'll read in detail later.

Last night I did something else (before your post). When it was booting to raspbian, got this in dmesg:

Code: Select all

[    3.360798] usb 1-1.4: new full-speed USB device number 6 using dwc_otg
[    3.470788] usb 1-1.4: device descriptor read/64, error -32
[    3.700786] usb 1-1.4: device descriptor read/64, error -32
[    3.930795] usb 1-1.4: new full-speed USB device number 7 using dwc_otg
[    4.040791] usb 1-1.4: device descriptor read/64, error -32
[    4.270786] usb 1-1.4: device descriptor read/64, error -32
[    4.500795] usb 1-1.4: new full-speed USB device number 8 using dwc_otg
[    4.950785] usb 1-1.4: device not accepting address 8, error -32
[    5.060790] usb 1-1.4: new full-speed USB device number 9 using dwc_otg
[    5.510793] usb 1-1.4: device not accepting address 9, error -32
[    5.527358] usb 1-1-port4: unable to enumerate USB device
[   15.624261] random: crng init done

I uplugged and replugged the mSATA and then it loaded!!!

Code: Select all

[   16.410796] usb 1-1.4: new high-speed USB device number 10 using dwc_otg
[   16.552626] usb 1-1.4: New USB device found, idVendor=05e3, idProduct=0718
[   16.570230] usb 1-1.4: New USB device strings: Mfr=0, Product=1, SerialNumber=2
[   16.588265] usb 1-1.4: Product: USB Storage
[   16.602994] usb 1-1.4: SerialNumber: 000000000033
[   16.619372] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[   16.636749] scsi host0: usb-storage 1-1.4:1.0
[   17.685102] scsi 0:0:0:0: Direct-Access     LITEONIT  LMT-128M6M mSAT 0016 PQ: 0 ANSI: 4

everything went ok after that... took this dump of dmesg

This morning I was going to get the requested files as suggested but instead of running an SD card, I was going to do the same thing I did last night (unplug/replug). Lo and behold, it booted normaly into raspbian on the first go.
extracted the files as requested and attached to this post.
(note: I run raspbian from the mSATA and run the commands as recommended, then copied the files (winscp) to my windows machine and posted here. not sure if that changes anything?)

Not sure what's going on... sometimes I think maybe power to the drive? but even wih my power supply @5.1V, 2A, using a power meter it's not drawing more than 1A at all, even powering both from one source.
This last run was done with the mSATA "card" disconnected from the pi, connected via a usb cable only (the card sits on top of the GPIO pins). Powered both the pi and mSATA separately as per last 2-3 tests (which allows me to power off and abck on only the drive and not the pi).

I also noticed that when going back into PINN recovery mode, most of the time the mSATA drive is not recognised. Power cycle fixes it, I'm able to select an OS but the "power cycle" of the OS then fails because it doesn't recognise the drive again....

any more ideas?

[procount]

Sorry, I'm out of ideas I'm afraid. I don't think it is a problem with PINN, but more of a general startup issue - maybe power, maybe just timing? Certainly it doesn't look like a driver issue as you can get it to work by power cycling.

Last time I got such a sequence of USB errors not accepting a device address was when my USB-IDE caddy for my 2.5" disk drive failed. Replacing the caddy fixed it.

Maybe look at: https://paulphilippov.com/articles/how- ... ress-error

[procount]

PINN has been updated to v2.4.3

This is a major update of the user interface in preparation for future new features.
I have also overhauled the README_PINN.md documentation file on github, so please take a look at the new format with all the new features documented.

V2.4.3

• 3 Toolbars - Main Menu, Archival and Maintenance.
• OS Groups - OS lists are grouped into General, Minimal, Educational, Media and Gaming.
• Download OS - Download an OS to USB for local installation.
• Fsck - Check and fix your filesystems in case of error.
• Wipe Disk - delete all OSes and restore drive to full capacity.
• Info button - Go directly to the webpage of each OS.

A third toolbar has been added which means the command buttons have moved around a bit, but hopefully their new positions will make more sense in the future.

Due to the large number of OSes that PINN can now install, they have now been grouped onto separate tabs based on some broad categories. If you don't like this, just add `no_group` to recovery.cmdline to restore them to a single list.

Although PINN has been able to install OSes from a USB stick for a while, getting the OS installation files onto the USB stick was a bit of a manual chore. So the new Download button will now download the selected OSes onto your USB stick for local installation when you don't have (or don't want to use) network installation.

A File System Check button has been added to check and fix your installed OSes in case they become corrupted due to e.g. an improper shutdown.

A Wipe disk function has been added to restore a PINN formatted drive to a single full size disk partition. This is useful for adding additional OS distribution files to the drive for local installation.

And finally, an Info button has been added which will take you directly to the webpage of any selected OS for more information it.

[Skedone]

Having a issue with latest version from today when I go to install it fails to find files




P.s it does this with any os I select

[procount]

Apologies. Hopefully it is fixed now.
v2.4.3a has now been uploaded to sourceforge and will shortly be available for download once the mirrors have synchronised.

[Skedone]

Will give it a test after I have done school run and let you know

[Skedone]

seems to be working perfectly now, good job works nicely that

[procount]

Did I mention that you can now use Etcher to flash PINN onto your SD-card?

https://github.com/procount/pinn/blob/m ... ing-etcher

[phmio]

Thanks procount for your work on this new PINN update and for implementing my requests.
All seems ok except no_cursor that hides cursor only on the MainWindow and not on BootSelectionDialog.

In fact i realize that hiding cursor on touchscreen devices is only useful on the BootSelectionDialog. On the advanced MainWindow i gues it should be active even if no_cursor flag is present, cause there is more configuation things to do (eg editing config.txt) and it is more pratice to do it with a keyboard,a mouse and a cursor .
How do you think?

[procount]

Thanks for the feedback. I'll address it in the next release.

[dvaitman]

is there a way of getting into recovery other than holding shift? I'm trying with no success. Holding shift when the colour screen comes up, when some text comes up, when the message comes up... not sure why it isn't going into recovery...

[dvaitman]

is there a way of getting into recovery other than holding shift?

I think I found it... "forcetrigger" ??? if I leave this parameter, would it always log into recovery mode?

[procount]

Yes, forcetrigger will force the recovery menu to load each time you boot.
Usually I wait til the Raspberry logo comes up, then press the shift key. Some people find they have to press it repeatedly on some keyboards.
Or you can click the mouse, or if you have a touchscreen, touch the raspberry. Or if you have a CEC remote, press any recognised key.
Or there is also a couple of GPIO pins you can connect together. They're all listed in the documentation.

[z3phyr]

Anyone able to boot into retropie after the pinn update? I'm dual booting raspbian with retropie.

[Haris1977]

@procount are you planning on adding a programmable option for cec control? I would love to be able to change PROGRAM UP/DOWN keys to UP/DOWN arrow keys and PLAY key to ENTER on my TV remote..

Very good try though;)

2 things i would love to see as a bonus. No mouse cursor (on boot screen i mean - not in restrore mode which is essential) and background image/sound..

[procount]

1. Maybe
2. Next release
3. Dunno
3. Background sound?

[procount]

Anyone able to boot into retropie after the pinn update?

Works ok for me.

[Haris1977]

3. Background sound?

Sorry (mea culpa). I meant background image selection It would be neat to see a total black screen for example....

Also would love to see a "rename" option in images - like Berryboot already has (e.g Openelec RPi instead of openelec_rpi1 which is now). This would keep things clean.

And bigger fonts (in boot selection) would be nicer

[procount]

PINN has been updated to v2.4.4

Finally, I have eliminated one of my NOOBS bugbears.
PINN can now re-install any installed OS WITHOUT affecting the other OSes.
This means that if you trash one OS, you can reinstall a factory fresh version of it whilst still keeping your other OSes intact.

During testing, several small cosmetic bugs were found, mainly concerning the partiion labels and some USB installation features.
These have now been fixed and Pull Requests submitted to NOOBS too.

I decided the 'Wipe disk' functionality needs a bit more work, so I have removed it for the time being, with the hope of introducing it again later.

V2.4.4

• Re-install - Re-install an OS without affecting others
• no_update - disable PINN self-update (manual refesh of PINN available)
• update PINN - A manual PINN update check can now be done (for when no_update is used)
• Edit PINN - The recovery.cmdline and config.txt fiels of PINN can now be edited.
• no_cursor - The no_cursor option now only affects the bootselection dialog
• Wipe - The Wipe Disk command has been temporarily removed
• Max OSes - The number of OSes has been restricted so that boot partitions numbers are <63

[Milliways]

I had a PINN 2.1.4 installation with Arch and Raspbian Jessie (kernel 4.4.38-v7+).

I updated to PINN 2.4.4.
I expected to see an option it install Stretch, but this only offered Jessie.

I selected Re-install, this appeared to work, but on re-boot gets to random crng init done but no further.
No command prompt appears.

PS Stretch appears to be installed (as shown by /etc/os-release) but it won't boot.

EDIT The PARTUUID in cmdline.txt on the Raspbian /boot does not agree with the Disk identifier on /dev/mmcblk0

Further the contents of /etc/fstab seem to be using the /dev/mmcblk0p designation for both the boot and root partition.

[procount]

The description is showing what is currently installed and it is not updated to show what is available. I'm not sure how to handle that scenario, but I am open to suggestions.

Hmm, I think I didn't consider the differing diskIDs in my testing as it didn't arise as a problem.

Have you tried editing cmdline.txt to match fstab and use the correct /dev/mmcblk0pX device?
It looks like that is the problem so I'll look into what's causing the problem.

EDIT: NOOBS and PINN will still use the /dev/mmcblk0pX designation if you have installed your OS to the SD card.
It only uses the PARTUUID if you are installing to a USB device.

I just did another test with Raspbian and it reinstalled fine, changing both cmdline.txt and /etc/fstab appropriately to /dev/mmcblk0pX
I can only imagine that your boot partition failed to update properly
Can you confirm if you installed to SD card or USB?
I can't see anything wrong in my tests. Could you try reinstalling Raspbian a second time?
If the problem persists, please open an issue on the github and post the contents of your /tmp/debug file (see https://github.com/procount/pinn/wiki/Troubleshooting on how to get this)

[Milliways]

The description is showing what is currently installed and it is not updated to show what is available. I'm not sure how to handle that scenario, but I am open to suggestions.

Hmm, I think I didn't consider the differing diskIDs in my testing as it didn't arise as a problem.

Have you tried editing cmdline.txt to match fstab and use the correct /dev/mmcblk0pX device?
It looks like that is the problem so I'll look into what's causing the problem.

EDIT: NOOBS and PINN will still use the /dev/mmcblk0pX designation if you have installed your OS to the SD card.
It only uses the PARTUUID if you are installing to a USB device.

I just did another test with Raspbian and it reinstalled fine, changing both cmdline.txt and /etc/fstab appropriately to /dev/mmcblk0pX
I can only imagine that your boot partition failed to update properly :shrug:
Can you confirm if you installed to SD card or USB?
I can't see anything wrong in my tests. Could you try reinstalling Raspbian a second time?
If the problem persists, please open an issue on the github and post the contents of your /tmp/debug file (see https://github.com/procount/pinn/wiki/Troubleshooting on how to get this)

I am running from a SD Card.

I had already tried re-installation twice before creating my post.
I had changed cmdline.txt to /dev/mmcblk0p7 but it did not seem to work.
As it was approaching midnight I decided to call it a day. On checking this morning I realised I had made a mistake, and in the clear light of day entered the correct device, and eventually got it to boot.

(After changing the default OS from Arch, which I was using to modify the files, to Raspbian it seemed to hang on the BOOT, but power cycling got it to work. This is possibly an other issue.)

I did note that I had no network, and wpa-supplicant had no networks, so I copied across.

The OS still shows Jessie in the menu, and locks up at the Recovery screen, but power cycling works OK.