This is only intended at present for anyone who has had problems producing a bootable stick.
The target device remains as an 8GB or greater USB2 or USB3 stick. I have however tested it with both cards and sticks.
I will edit this post with a detailed write-up of those changes should it give a better booting success rate. Blue Pup itself only has minor non-critical changes. If you are happy with V1 or V2 there is no vital need to change but you could test on another stick.
blue_pup_v3_4gb.img.xz [323 Meg]together with the MD5 can be found here:
MD5 2eceada3a5220d89bb5f84365db26f37
https://drive.google.com/folderview?id= ... sp=sharing
&
https://archive.org/details/Puppy_Linux_blue_pup
NOTES:
1. Unplug any other cards or sticks before attempting to boot V3.
2. Use a port rather than a USB hub if possible as there is an underlying problem with QT.
3. Linux install terminal commands for V3:
(The target stick should not be mounted. In the directory that you downloaded the .img.xz file to, right click then /window/terminal here/ to access the terminal)
Only issue the sync command when the first command has completed which may take up to 20 minutes. If you wish you can monitor it running in HTOP.
Code: Select all
# xz --decompress --stdout blue_pup_v3_4gb.img.xz > /dev/sdx
# sync
(replace the x at the end with your target device letter)
Code: Select all
# Boot Blue Pup ETP 25th March 2014
default /vmlinuz root=/dev/sdb2 rootwait rw
In summary try the default sdb2 then move up to sdc2 then sdd2 until you boot successfully without seeing a kernel panic message.
If you first attempt to boot the stick on the same pc or laptop that you used to create it, make sure that before doing so, you shut down the device and remove all mains power from it for a couple of minutes.
This will ensure that your BIOS refreshes its view of the stick and sees it as bootable.
Edit: 31/03/14 A copy of my own rough build notes as below.
- V3 Changes: (DPI left at 102)
************************
1. Default apps - change HTML editor to geany (HTML viewer Chromium)
2. Chromium:
A - Clear P/Ws.
B - Set allow local data to be set as the default. (Cookies)
C - Update Metro to v 1.02 (supposed to update automatically but does not always do so)
3. Line up GTK panel with extra space after QUIT but before :
4. Change Metro & Panel to V3
5. Program E-Mail button to launch T'bird (key 236) (For multimedia K/Bs)
6. Eliminate typo from some scripts (usr instead of user!!!!)
7. Zeroise build card with dd before starting build. (Compressed image then half the size of V2)
8. Abandon QT stick layout to deal with difficult BIOSs.
9. Use syslinux 4.04 instead of 4.05 and create 16 Meg Fat32 image instead of Fat16. Prepare with HP Utility before
applying boot-loader.
10. Start build by applying the above 16 Meg image to 4GB card then format rest as f2fs.