Blue Pup V6 Released 11th Oct 2014 32-bit

For talk and support relating specifically to Puppy derivatives
Post Reply
Message
Author
gcmartin

#121 Post by gcmartin »

Hi @ETP

Say your reference to the "might" in the GParted message. This leads to this question: Is GParted, which is capable of creating an f2fs not able to resize an f2fs?

On your other reference in that post, to clarify: I booted one pristine BLUE stick. Next, running BLUE, I created a new, 2nd, BLUE stick. After creating, I removed and re-inserted the 2nd stick into the system so that the system properly referenced its partitions and opened GParted. As you can see, GParted, shows this problem and does not allow resizing. Question arising from this discovery: Is this a bug, in GParted or in the tools?

Trying to, both, get an understanding and provide good information to the thread.

Here to help

User avatar
ETP
Posts: 1193
Joined: Tue 19 Oct 2010, 19:55
Location: UK

Blue Pup V1 & V2 (Released 13th March 2014),

#122 Post by ETP »

Hi Billtoo,

There is nothing wrong with the sticks or their production if they are each happy to boot in at least one PC. What you are seeing is a BIOS issue which typically afflicts bioses manufactured between 2005?- 2008?

I have such a BIOS in my Pentium D box and it is a proper swine with something of the night about it.
Many moons ago I was trying to persuade it to see a stick as bootable but it stubbornly refused to do so. I tried several re-configurations and numerous reboots before giving up, cursing one last time and retiring to bed. I left the stick plugged in and as is my habit killed the power to all systems.
The next day I powered up expecting to be met by the vesa menu on my usual boot stick which is always plugged in. The box however proceeded to boot from the new stick!
The only thing that had changed was the overnight interruption of external power to the BIOS.

In short some bioses have a volatile memory for devices that they have already seen during a session retaining I guess the hardware I/D, SN and whether it last saw it as a bootable removable device or not. The idea was, I think, intended to cut down on the number of checks made and reduce boot time. A quick reboot does not clear that memory but a 30 seconds complete power off does. The Bios battery does not support the volatile memory which must use the 5v or 12v supplies.

My box fortunately has an on/off switch on the power supply at the rear. It may be that more than 30 seconds is needed if a large capacitor continues to supply current to the volatile memory. Once it is cleared the BIOS will be forced to see things afresh and will offer the stick as a bootable device.
Last edited by ETP on Mon 31 Mar 2014, 15:12, edited 1 time in total.
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]

User avatar
ETP
Posts: 1193
Joined: Tue 19 Oct 2010, 19:55
Location: UK

Blue Pup V1 & V2 (Released 13th March 2014),

#123 Post by ETP »

Hi gcmartin,

Currently Gparted can create and delete but not resize f2fs partitions. In order to resize see the method I described.
It is not a bug but the fact that the ability to do so has not yet been incorporated into Gparted.
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

Re: Blue Pup V1 & V2 (Released 13th March 2014),

#124 Post by Billtoo »

ETP wrote: Currently Gparted can create and delete but not resize f2fs partitions. In order to resize see the method I described.
It is not a bug but the fact that the ability to do so has not yet been incorporated into Gparted.
On one of the new flashdrives I made a second f2fs partition, on the other the second partition is ext4 (just to see how it goes)

EDIT:
Gparted and partview see the same thing differently.
Attachments
image-4.jpg
(92.65 KiB) Downloaded 1724 times
gparted.jpg
(51.17 KiB) Downloaded 1784 times
Last edited by Billtoo on Tue 01 Apr 2014, 03:09, edited 1 time in total.

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

Re: Blue Pup V1 & V2 (Released 13th March 2014),

#125 Post by Billtoo »

Double post

Les Kerf
Posts: 317
Joined: Sun 24 Jun 2012, 13:30

#126 Post by Les Kerf »

8-bit wrote:...
I also read that Plop can be run from a CD crated with an ISO file of Plop.
No mention was given though of being able to make a boot Plop floppy disk for an older PC that had a floppy drive that in turn would boot the USB stick.
...
I have used all three methods (Install PloP to MBR, PloP Live CD and PloP Floppy) to boot older machines from USB that lacked the native USB boot support.

PloP does not work with SATA drives, but anything that new will usually boot with a USB natively.
Les

gcmartin

#127 Post by gcmartin »

Hello @Les Kerf
Les Kerf wrote:... I have used all three methods (Install PloP to MBR, PloP Live CD and PloP Floppy) to boot older machines from USB that lacked the native USB boot support. ...
Did PloP work to boot your 8GB full-install BLUE USB stick?

If so, are the steps clear?
Curious

User avatar
8-bit
Posts: 3406
Joined: Wed 04 Apr 2007, 03:37
Location: Oregon

#128 Post by 8-bit »

I am now downloading Gparted 0.18 to see if resizing of an f2fs partition is now included.
Puppy Precise 5,7,1 has Gparted version 0.16 which says in the release notes for it that it supports f2fs partitions.
But resize in that version does not work. So that is my reasoning to check out the latest stable version.
If I had to go to the extent of copying the contents of the f2fs partition to another area and then format the partition to e3fs to resize it and then after the resize, formatting it again as a f2fs partition and copying back the contents, I feel like I would be jumping through hoops. If I left the resized partition as an e3fs one, would it still boot even though I would loose the benefits that the f2fs file system is supposed to provide?
Also, have you tried the steps you provided to see if the resulting flash drive is still bootable?

I just not, after examining the contents if the gparted 0.18 zipped file that it contains UEFI boot code for both 32 and 64 bit PCs!
That in itself may make the file worth a look!

User avatar
ETP
Posts: 1193
Joined: Tue 19 Oct 2010, 19:55
Location: UK

#129 Post by ETP »

8-bit wrote:I am now downloading Gparted 0.18 to see if resizing of an f2fs partition is now included.
Puppy Precise 5,7,1 has Gparted version 0.16 which says in the release notes for it that it supports f2fs partitions.
But resize in that version does not work. So that is my reasoning to check out the latest stable version.
If I had to go to the extent of copying the contents of the f2fs partition to another area and then format the partition to e3fs to resize it and then after the resize, formatting it again as a f2fs partition and copying back the contents, I feel like I would be jumping through hoops. If I left the resized partition as an e3fs one, would it still boot even though I would loose the benefits that the f2fs file system is supposed to provide?
Also, have you tried the steps you provided to see if the resulting flash drive is still bootable?

I just not, after examining the contents if the gparted 0.18 zipped file that it contains UEFI boot code for both 32 and 64 bit PCs!
That in itself may make the file worth a look!
Also, will increasing the f2fs partition size effect booting ability.
No. To do so you would first (using 5.7.1) need to move all the files off it to a linux partition somewhere. Then using Gparted change the format of it to ext2. Expand it then revert it back to f2fs before finally moving your files back onto it.
This is necessary as Gparted does not yet allow for the resizing of f2fs partitions.
Hi 8-bit.
The kernel (vmlinuz) is quite happy to boot the OS from any file system it recognises. If you do not mind loosing the benefits of f2fs, on flash an ext4 partition set up as non-journaled, would be a good choice. You would still have to move the files to a temporary store however so the number of steps is still the same.
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]

User avatar
ETP
Posts: 1193
Joined: Tue 19 Oct 2010, 19:55
Location: UK

Blue Pup V1, V2 & V3 (Released 2nd April 2014)

#130 Post by ETP »

Version 3 of Blue Pup has today been released and I wish to express my gratitude to all members who have contributed to this thread and undertaken testing. A raft of problems associated with the true capacities of sticks and the quirkiness of some BIOSs emerged which hopefully V3 addresses.

I have edited all the major posts to incorporate the lessons learnt and will also place a link in the second post to the brief summary below.
Thanks once again.

Version Summary: (All versions include the Metro interface)
Please ensure that you have read the first 2 posts in this thread.
Blue Pup – (V1 Released 3rd March 2014 - 575 MB)
Has a very traditional desktop complete with all icons.

Blue Pup – (V2 Released 13th March 2014 - 602 MB)
Starts here: http://www.murga-linux.com/puppy/viewto ... 653#764653
Provides an alternate panel desktop, new cosmetics, improved speed and easier navigation.

Blue Pup – (V3 Released 02nd April 2014 - 323MB)
Starts here: http://www.murga-linux.com/puppy/viewto ... 134#767134
This contains a boot partition specially crafted to deal with difficult BIOSs but will still boot on any kit. The download is smaller and the original partition layout totally changed.
The expanded image has been reduced to 4GB but the target stick size of 8GB or greater still applies. This deals with 8GB sticks that are actually short of capacity which would not image correctly.
Minor editing of syslinux.cfg for this to boot may be needed depending on your hardware.
Choose this version if your BIOS cannot normally boot from a USB stick or if you prefer it.

Blue Pup – (V4-FINAL - Released 09th May 2014 – 424MB)
Starts here: http://www.murga-linux.com/puppy/viewto ... 329#776329
This is the final release of Blue. Its main new feature is that it is suitable for any type of BIOS so eliminating the need for a separate version (V3) to deal with awkward ones. It incorporates all previous service packs and dotpets including optional pets. “Hot screen sides
Last edited by ETP on Sat 11 Oct 2014, 09:04, edited 3 times in total.
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

kernel bug

#131 Post by step »

I extracted the image to an 8GB SD card from QT 6.0.5

Code: Select all

# date; xz --decompress --stdout blue_pup_v3_4gb.img.xz > /dev/mm0p; sync; date
Extraction took about 90 seconds. It sounds too short. Anyway, after rebooting the system into QT I could see two desktop icons for /dev/mm0p1, vfat 15 MB, and /dev/mm0p2, f2fs 3.7GB. Clicking mm0p1 mounts the partition and display ROX. Clicking mm0p2 attempts to mount the partitition but nothing visible happens. Eventually the system logs this trace:

Code: Select all

[   54.692445] ------------[ cut here ]------------
[   54.692532] kernel BUG at fs/f2fs/node.c:972!
[   54.692604] invalid opcode: 0000 [#1] SMP 
[   54.692661] Modules linked in: cpufreq_ondemand iptable_mangle xt_conntrack ipt_REJECT nf_conntrack_ftp nf_conntrack_irc iptable_filter xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ip_tables fan fuse btusb bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev tifm_sd sdhci_pci sdhci mmc_block mmc_core tifm_7xx1 pcspkr tifm_core arc4 yenta_socket firewire_ohci firewire_core iwl4965 iwlegacy mac80211 cfg80211 radeon fbcon bitblit softcursor font tileblit tg3 ptp pps_core i2c_algo_bit ttm drm_kms_helper drm i2c_i801 i2c_core lpc_ich mfd_core snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_seq_dummy snd_pcm snd_page_alloc snd_seq_oss snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore shpchp intel_agp intel_gtt agpgart acer_wmi sparse_keymap rfkill wmi battery video evdev thermal button acpi_cpufreq processor thermal_sys hwmon ac
[   54.693629] CPU: 0 PID: 7310 Comm: mount-FULL Not tainted 3.12.6 #1
[   54.693677] Hardware name: Acer            TravelMate 5720                /Columbia                       , BIOS V1.35           07/03/2008
[   54.693768] task: f53febe0 ti: f28f0000 task.ti: f28f0000
[   54.693809] EIP: 0060:[<c1184395>] EFLAGS: 00010206 CPU: 0
[   54.693856] EIP is at get_node_page+0xb5/0xd2
[   54.693889] EAX: f29c1000 EBX: f6651820 ECX: f5fd4000 EDX: 000002c0
[   54.693951] ESI: f57e9298 EDI: 00000003 EBP: f28e3000 ESP: f28f1e7c
[   54.693998]  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
[   54.694039] CR0: 8005003b CR2: b757c6bc CR3: 351dc000 CR4: 000007d0
[   54.694085] Stack:
[   54.694105]  f57f5e10 f28e3000 00000003 c117dfd2 f28f1e88 f4999ac0 f28e3000 f49ff9cc
[   54.694197]  f28e3000 00000000 f49ff9cc f49ff800 c117fd92 c145d42d f30aa400 f5413160
[   54.695644]  f49ff800 f5581700 00000083 00000000 c1095045 f5581774 62636d6d 70306b6c
[   54.695741] Call Trace:
[   54.695741]  [<c117dfd2>] ? f2fs_iget+0x301/0x31d
[   54.695741]  [<c117fd92>] ? f2fs_fill_super+0x3d0/0x656
[   54.695741]  [<c1095045>] ? mount_bdev+0xfc/0x13d
[   54.695741]  [<c11afc52>] ? ida_get_new_above+0x14c/0x15f
[   54.695741]  [<c117f116>] ? f2fs_mount+0xe/0x11
[   54.695741]  [<c117f9c2>] ? f2fs_remount+0xbb/0xbb
[   54.695741]  [<c10956fa>] ? mount_fs+0xd/0x8b
[   54.695741]  [<c10a63e1>] ? vfs_kern_mount+0x44/0xaa
[   54.695741]  [<c10a7cda>] ? do_mount+0x646/0x74f
[   54.695741]  [<c107cfb0>] ? memdup_user+0x22/0x3f
[   54.695741]  [<c10a7e59>] ? SyS_mount+0x76/0xa8
[   54.695741]  [<c138728a>] ? sysenter_do_call+0x12/0x26
[   54.695741] Code: 80 8b 03 a8 01 75 02 0f 0b 89 d8 e8 51 a9 ee ff 89 d8 e8 30 26 ef ff e9 65 ff ff ff 89 d8 e8 21 cb ef ff 3b b8 e8 0f 00 00 74 02 <0f> 0b 89 d8 e8 34 28 ef ff eb 0c bb f4 ff ff ff eb 05 bb fb ff
[   54.695741] EIP: [<c1184395>] get_node_page+0xb5/0xd2 SS:ESP 0068:f28f1e7c
[   54.721902] ---[ end trace a79193d99932e929 ]---
I will try again later.

User avatar
ETP
Posts: 1193
Joined: Tue 19 Oct 2010, 19:55
Location: UK

Blue Pup V1, V2 & V3 (Released 2nd April 2014)

#132 Post by ETP »

Hi step,

90 seconds is way too quick for your card to have imaged correctly and I am not clear why you targeted the device node rather than the device letter? Item 3 of the notes on V3 reads as follows:
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:
# xz --decompress --stdout blue_pup_v3_4gb.img.xz > /dev/sdx
# sync
(replace the x at the end with your target device letter)
Depending how your target device appeared on the desktop when you plugged it in, that would typically mean replacing sdx with one of the following:
sdb
sdc
sdd
sde
sdf
sdg

It can also sometimes help to return the target device to its “out of the packet
Attachments
screenshot.26 (Medium).jpg
(47.91 KiB) Downloaded 1353 times
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]

gcmartin

#133 Post by gcmartin »

  1. Create a USB2Stick.sh

    Code: Select all

    #!/bin/bash
    # Future - Check for number of parms passed. If not 2. put up correct use message "missing parms"
    # Future - Check $1 for ending in ".img.xz". If not, put up correct use message "file not xz"
    ImagePath=$1
    USBstick=$2
    echo This utility transfers $ImagePath to $USBstick
    # Future - echo "Please make sure that you are using the correct USB device. If it /dev/$USBstick"
    # Future - pause this utility. wait for user confirmation or abort on timeout.
    date
    echo "xz deompression started to $USBstick"
    xz --decompress --stdout $ImagePath > /dev/$USBstick
    echo "xz deompression complete to $USBstick ... please wait for following message"
    sync
    echo "sync complete. All services completed. Your USB stick on $USBstick in ready for use."
    date
    # Future - Calculate the time to create the USB.
    exit
    # NOTE: This utility should also have a dialogue approach too.
  2. Run USB2Stick.sh

    Code: Select all

    # USB2Stick.sh  blue_pup_v3_4gb.img.xz   sdd
    This utility transfers blue_pup_v3_4gb.img.xz to sdd
    Thu Apr  3 18:36:52 EDT 2014
    xz deompression started to sdd
    xz deompression complete to sdd ... please wait for following message
    sync complete. All services completed. Your USB stick on sdd in ready for use.
    Thu Apr  3 18:50:23 EDT 2014
  3. Enclose Picture of USB outcome as attachment (see below)
    Image
  4. Boot USB stick
    1. No issues on booting using either a laptop/deskPC
    2. wired LAN is not active upon reaching BLUE's desktop
    3. exit browser to desktop and ran FirstRUN to address locality needs
      Image
    4. Message to restart X acknowledged, BUT desktop came back NOT as BLUE but instead Tahr.
    5. wired LAN still not active. Click icon on taskbar to activate.
Hope this is helpful

User avatar
8-bit
Posts: 3406
Joined: Wed 04 Apr 2007, 03:37
Location: Oregon

#134 Post by 8-bit »

gcmartin,
I like your install script a.
I created a script also. But mine was edited to pick the flash drive to install to and also I edited it depending on if I used it for version 2 or version 3 of Blue.
I do wonder if a Blue flash drive would boot on a PC that had UEFI.

I am also trying to see if the latest version of Gparted which is around .18 would allow resizing of an f2fs partition. The latest version of Gparted used with Puppy is .16 and most Puppys are using verision .14 of Gparted.
One echo line I would add to your script would be a usage example showing the script with parameters needed in the correct order.

gcmartin

#135 Post by gcmartin »

Ran GParted in terminal to view USB while BluePUP is running. No changes were attempted in GParted: Just navigated viewing USB's partitions.

Questions
Terminal shows these messages. Are they symbolic of anything?

Code: Select all

# gparted /dev/sdb
======================
libparted : 3.1
======================

(gpartedbin:4847): GLib-CRITICAL **: Source ID 7 was not found when attempting to remove it

(gpartedbin:4847): GLib-CRITICAL **: Source ID 6 was not found when attempting to remove it

(gpartedbin:4847): GLib-CRITICAL **: Source ID 29 was not found when attempting to remove it

(gpartedbin:4847): GLib-CRITICAL **: Source ID 28 was not found when attempting to remove it

(gpartedbin:4847): GLib-CRITICAL **: Source ID 45 was not found when attempting to remove it

(gpartedbin:4847): GLib-CRITICAL **: Source ID 44 was not found when attempting to remove it
#

User avatar
ETP
Posts: 1193
Joined: Tue 19 Oct 2010, 19:55
Location: UK

Blue Pup V3

#136 Post by ETP »

@ gcmartin,

Thanks for your script post.

With regard to your method (a) you will need to explain to users how to execute a script with variables as many will never have done so.
At the end of the script you echo:
Your USB stick on $USBstick in ready for use.
That may or may not be so. It totally ignores the possible need to edit syslinux.cfg.
Your script needs to mirror ALL the instructions given here:

http://www.murga-linux.com/puppy/viewto ... 134#767134

At the end of your post you commented :
BUT desktop came back NOT as BLUE but instead Tahr.
That rather proves my point as you booted into a copy of QT rather than Blue Pup V3.

@ 8-bit,
I do wonder if a Blue flash drive would boot on a PC that had UEFI.
Yes, from legacy USB3 mode, but you will need to enter the BIOS at boot time and select that. The stats at the bottom of my previous post are from a UEFI pc.
I am also trying to see if the latest version of Gparted which is around .18 would allow resizing of an f2fs partition.
http://lmgtfy.com/?q=gparted+features&l=1#
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]

User avatar
Ted Dog
Posts: 3965
Joined: Wed 14 Sep 2005, 02:35
Location: Heart of Texas

md5sum in posts please

#137 Post by Ted Dog »

Hate to be a stick.. but why do you not post md5sum as part of the text block.. Could not get to it without signing in to NSA-Google.. Having it in the same place as download only allows someone to fiddle with BOTH...

other site does not even have md5sum.. :wink: my download jumped from 59% to done way to quickly :shock:

User avatar
ETP
Posts: 1193
Joined: Tue 19 Oct 2010, 19:55
Location: UK

Re: md5sum in posts please

#138 Post by ETP »

Ted Dog wrote:Hate to be a stick.. but why do you not post md5sum as part of the text block.. Could not get to it without signing in to NSA-Google.. Having it in the same place as download only allows someone to fiddle with BOTH...

other site does not even have md5sum.. :wink: my download jumped from 59% to done way to quickly :shock:
Hi Ted Dog,
Done as requested. I think Google was busy as it would not let me view it but is now O/K again.
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]

gcmartin

Re: Blue Pup V3

#139 Post by gcmartin »

ETP wrote:Your script needs to mirror ALL the instructions given here:

http://www.murga-linux.com/puppy/viewto ... 134#767134

At the end of your post you commented :
BUT desktop came back NOT as BLUE but instead Tahr.
That rather proves my point as you booted into a copy of QT rather than Blue Pup V3.
What I offered was an idea for automating a dialogue to add some consistency in user creation of the sticks from the download fileset. Its an idea, only.

The post tries to show a path to get locality that ended changing background from a BLUE to a TAHR background without ever rebooting after FirstRUN use. Thus, there is something wrong as I had not encountered this is any past distros.

Again, this is trying to provide visual and repeatable steps in getting to a working desktop.

BTW, I did read your link even before trying the latest and do not see anything there which is inconsistent with what is shown. If there is something missed in those steps taken, please advise and I will retest and present.

Here to help

gcmartin

#140 Post by gcmartin »

Without taking sides on which sites are better, Google is still the fastest download site in the world. IBM's is the only other in the world, better/equal.
Biggest problem file owner have hit in the past is insuring to set privileges so that anyone can download content they provide.

Again, this is neither a positional or a recommendation.

FYI
Edit: removed reference to class of download sites
Last edited by gcmartin on Fri 04 Apr 2014, 19:31, edited 1 time in total.

Post Reply