Blue Pup V6 Released 11th Oct 2014 32-bit

For talk and support relating specifically to Puppy derivatives
Message
Author
step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

Re: Blue

#151 Post by step »

ETP wrote:Your second screen shot tells me that the Metro extension has updated to 1.02 which has some improvements. You can induce an update by entering developer mode if it fails to do so.
Can you elaborate on that? What are the steps to update the Metro extension? I'm new to Chromium.
EDIT: never mind, found it under Settings/Extensions (left side).

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

Blue Pup

#152 Post by ETP »

Hi step,

It is good to hear that you are now up and running.
I wonder if I could boot blue pup from a USB2 key targeting the f2fs partition on a USB3 key plugged into the express port card... Time to experiment.
Anyway, thank you again for blue pup!
Yes, but you may as well put it on the SSD. That is one way that I run it on both my XP box and a recent 8.1 box with an 840.

It is very easy to do and is described here:

http://www.murga-linux.com/puppy/viewto ... 231#763231

Have fun. :)
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

#153 Post by gcmartin »

High Step! :lol:
step wrote: ... I recently got a Samsung 840 evo 128GB SSD and I'm trying to decide which OS/fs combo is best for it. ... USB3 is available as an add-in express port card, but the BIOS can't boot from it. I wonder if I could boot blue pup from a USB2 key targeting the f2fs partition on a USB3 key plugged into the express port card... Time to experiment. ...
Over last weekend, I did just that...experiment. This is what I found out.
Modifying the config found in the /boot folder of USB partition1 you'll need to point to the correct partitions where the full-install partition is. Standard is "sdb2". In my case, I duplicated sdb2 to a logical partition "sdb6". And, it booted. Be sure that rootwait and rw remain as they are REQUIRED. One example allow system to boot sdb6 is as follows:

Code: Select all

# Boot Blue Pup ETP 25th March 2014
default /vmlinuz root=/dev/sdb6 rootwait rw
# Original systemboot instruction follows
# default /vmlinuz root=/dev/sdb2 rootwait rw 
I see no reason you could not replicate sdb2 to any other partition your system could see at boot time and have your system boot by modifying the bootmanager config appropriately.

Here to help

User avatar
charlie6
Posts: 1230
Joined: Mon 30 Jun 2008, 04:03
Location: Saint-Gérard / Walloon part of Belgium

[not SOLVED]

#154 Post by charlie6 »

Hi ETP,
thanks for these Blue Tahr derivatives !
i got Blue v.2 running nice (installed on an 8GB USB stick from the image as described on page 1 this thread; the whole 8GB stick has been f2fs formated before install);
- booted nice on a COMPAQ desktop, and now does not boot anymore on the very same desktop ...just a flashing dash prompt without any message;
- now it continues booting on a Dell620 laptop;
- it does not boot on other PC's where another USB stick with syslinux 3.73 boots nice;

Now i'm a bit puzzled as it has booted on the COMPAQ PC, and now it does'nt anymore ...

Thnsk for ant advice,
Charlie

last edited:
reading the above post (thanks gcmartin !!)

editing the syslinux.cfg file in sdb1 like this:
syslinux.cfg was

Code: Select all

# Boot Blue Pup ETP March 2014
default /vmlinuz root=PARTUUID=123456-78 rootwait rw 
edited syslinux.cfg:

Code: Select all

# Boot Blue Pup ETP March 2014
#default /vmlinuz root=PARTUUID=123456-78 rootwait rw
default /vmlinuz root=/dev/sdb2 rootwait rw 
does not solve that question ...see next post

User avatar
charlie6
Posts: 1230
Joined: Mon 30 Jun 2008, 04:03
Location: Saint-Gérard / Walloon part of Belgium

#155 Post by charlie6 »

Hi again,
(continuing my above post)
the new syslinux.cfg allowed to boot only once on the COMPAQ PC;

i afterwards plugged the USB stick on another desktop (also booting on anther stick having syslinux3.73 in /sdb1), and got nothing but tre fashing dash prompt;

back again on the COMPAQ desktop ...and does not boot (only got the flashing dash prompt)

...??
thanks for any advice
charlie

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

Blue V2

#156 Post by ETP »

Hi Charlie,

Gcmartin’s post does not apply to your problem which is BIOS related rather than a failure to find the second partition. PARTUUID ensures (in V1 & V2) that it does regardless of the drive letter. You should return syslinux.cfg to its original state then proceed as follows:

The flashing prompt indicates that the BIOS is no longer seeing the stick as a bootable device. Try removing all mains power to the COMPAQ desktop for a couple of minutes then try again. As it boots enter the BIOS to see how it perceives the stick.
On the other PCs try the same thing.

If no joy, try V3 which is intended to boot on awkward BIOSs. Edit: Return your stick to its virgin state before targeting it with V3. :)

General Comment:
Step’s last post has reminded me to cover how to upgrade Thunderbird.
I have therefore added to the FAQ which can be found here:

http://www.murga-linux.com/puppy/viewto ... 234#762234
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

Re: Blue Pup

#157 Post by step »

ETP wrote:Yes, but you may as well put it on the SSD. That is one way that I run it on both my XP box and a recent 8.1 box with an 840.
It is very easy to do and is described here:
http://www.murga-linux.com/puppy/viewto ... 231#763231
Bookmarked and I will definitely experiment it. Are you actually dual booting Win and blue pup from your SSD, or is your SSD reserved for blue pup? If dual booting, are you doing that with syslinux and how?

One of the reasons I really like this thread is because you and other members are enriching it with wonderful and clear how-to's related to booting and QT in general.

One more question. Would you please share the performance testing scripts that you used to make the list in your post here http://www.murga-linux.com/puppy/posting.php?p=768942?

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

#158 Post by step »

gcmartin wrote:High Step! :lol:
Modifying the config found in the /boot folder of USB partition1 you'll need to point to the correct partitions where the full-install partition is. Standard is "sdb2". In my case, I duplicated sdb2 to a logical partition "sdb6". And, it booted. Be sure that rootwait and rw remain as they are REQUIRED.
Hi gcmartin! Thank you for your advice. I'm not clear what rootwait is for. For HDD/SSD install ETP wrote elsewhere that it isn't needed anymore. So I'm guessing that rootwait is required to boot any kind of USB/SD portable media. Am I on the right track?

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

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

#159 Post by Billtoo »

I added the devx for Quirky Tahr 6.0.5 and then compiled wine 1.7.16,
it's working well.
Blue Pup is working well too.
Attachments
image-4.jpg
(63.64 KiB) Downloaded 469 times
image-5.jpg
(59.23 KiB) Downloaded 387 times

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

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

#160 Post by ETP »

Hi step,

To take your last query first. You do not need “rootwait
Last edited by ETP on Mon 07 Apr 2014, 05:50, 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]

gcmartin

#161 Post by gcmartin »

step wrote:... So I'm guessing that rootwait is required to boot any kind of USB/SD portable media. Am I on the right track?
I found to the contrary when testing. Failure without it on my Dell laptop where current tests are done. It required both parms to boot sdb6.

My steps on 8GB stick:
    1. Gparted /dev/sdb
    2. Turn "Unallocated" area into an extended partition
    3. created a formatted f2fs partition in the extended area
    4. Exit Gparted
    5. Remove stick, count to 3 re-insert stick
    6. mount sdb2 AND sdb6
    7. Open 1 ROX window to sdb2 and a 2nd ROX window to sdb6
    8. Insure that you can see hidden files in sdb2 window
    9. Drag-copy all folders-files seen in sdb2 to sdb6 (be patient, USB is a slow asynchronous device)
    10. edit the bootmanager config in /mnt/sdb1/boot/syslinux as indicated earlier, here
    Reboot with stick.
Hope this helps

When done, would you post your final bootmanager config.

Here to help

User avatar
charlie6
Posts: 1230
Joined: Mon 30 Jun 2008, 04:03
Location: Saint-Gérard / Walloon part of Belgium

#162 Post by charlie6 »

Hi ETP,
- disconecting the PC's main power did not fix the above reported boot difficulties;
- i now wonder how my above reported boot difficulties could be BIOS dependent ...
i indeed experienced the following on the very same COMPAQ desktop.
On that PC, i have installed among others:
- dPup Wheezy 3.5.2.11, frugal install on sda2
(note: dPup Wheezy3.5.2.11 cannot open or mount f2fs partitions ... but sdb1 is fat16 formated)
- quirky 6.0.3, full install on sda5

BluePup v2 is installed on a 8GB USB stick.

step1: USB stick plugged and start PC: let's assume it doesn't boot ; then a flashing dash prompt is displayed; then unplug the USB stick and boot PC on quirky6.0.3;
once booted, plug the USB stick, and just mount sdb1 by clicking on its icon;
afterwards, unmount it, and restart the PC with the stick left plugged;
then BluePupv2 boots OK.
(note: while the flashing dash prompt is displayed, if waiting over 60-70sec, then Grub starts and display the boot menu.)

step2: from above step1, switch off PC, and unplug the USB stick.
Then boot PC choosing dPup Wheezy 3.5.2.11;
plug the USB stick, and just mount sdb1; once mounted, unmount it
then reboot PC with USB stick left plugged;
BluePupv2 does'nt boot.

To get the USB stick booting again, i have to perform step1.

I could reproduce all this several times .
Are there explanations to such a behaviour?
Cheers, Charlie

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

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

#163 Post by ETP »

Hi Charlie,

The good news is that your COMPAQ BIOS is capable of booting from a USB stick so you can disregard my previous comment about trying V3. What is does need is a little persuasion. :)
Start by putting your syslinux.cfg back to its original state.

When Grub started after 60-70secs it means that your BIOS must have booted from the hard disc rather than the USB. In order to try to get the better of it try the following:
1. Shutdown the box & remove all mains power to it for a couple of minutes.

2. Plug your Blue V2 stick in then power up pressing the appropriate key to access your BIOS settings as you do so.

3. Place the stick at the top of the boot order (Before any CD or HDD) then SAVE your BIOS settings. Hopefully it will then proceed to boot from the stick.

4. Once you have played around with Blue and set up the network connection if need be, rather than shutting down, select re-boot from the JWM menu to check whether Blue once again boots.

5. Shutdown completely but leave the stick plugged in and the mains power connected.

6. Give it 10 seconds or so then turn on again to see whether it still boots into Blue or defaults to booting from the HDD.

7. If it defaults to the HDD, it means that you are going to have to repeat steps 2 & 3 each time you want to boot Blue from the USB stick.

I note that you have a full install of 6.0.3 on sda5 which I suspect is not an f2fs partition.

Good luck.
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
charlie6
Posts: 1230
Joined: Mon 30 Jun 2008, 04:03
Location: Saint-Gérard / Walloon part of Belgium

#164 Post by charlie6 »

Hi ETP,
(from page 1 ...)
ETP wrote:
Ted Dog wrote:Why just why would someone want a windows8 work a like...
Hi Ted Dog,
...
My thinking behind this release is to offer the bling that is fashionable and likely to attract youngsters to try and experience the benefits of Linux. Witness their obsession with smart-phones and fondle slabs. If we fail to keep pace with the times and only major on code and functionality at the expense of form, we will stand little chance of attracting the next generation to Linux who will perceive the traditional desktop as something archaic only suited to geeks or grandfathers.
just to mention ...
«Woooow ... :D ! that's Linux ...!? :shock: » asked me my 18 y.o. daughter watching to the BluePup's Metro screen this morning at office...
«Nice colours ...» ... my wife's comment yesterday before watching a video ..
Thanks again ETP !
Charlie

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

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

#165 Post by Billtoo »

After using xbmc under wine I checked QPM and saw that the latest xbmc
12.3 is available so I installed that.
XBMC is working great but only if your graphics card supports direct
rendering, ati and nvidia don't (on computers that I've tested Quirky
and Blue Pup on),all intel that I've tested do with 1 exception which was intel
ivybridge mobile.

This pc has:
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ironlake Desktop x86/MMX/SSE2
OpenGL version string: 2.1 Mesa 10.0.1

The xbmc in QPM uses less resources compared to the windows version
running under wine.

EDIT:
I moved my Blue Pup V2 flashdrive to a pc with a Radeon HD 8570
graphics card, direct rendering is working with this card:

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits)
OpenGL version string: 2.1 Mesa 10.0.1

Screenshot 2 shows xbmc running on this pc.

Older ati cards that I've tried use the modesetting driver which is
the only option given when xorgwizard is run.
Attachments
screenshot2.jpg
(50.32 KiB) Downloaded 253 times
screenshot.jpg
(53.75 KiB) Downloaded 361 times

gcmartin

#166 Post by gcmartin »

@BillToo, thanks. I was just looking at this site just before clicking into this BLUE thread where I find your post. XBMC would be an excellent native application for this distro it could be, OOTB.

What an idea.

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

A sticky wicket.

#167 Post by ETP »

If anyone is curious about the construction of the 8GB USB stick GPT layout that BarryK issued for QT and is used in Blue V1 & V2 but not in V3, this is the relevant link:

http://bkhome.org/news/?viewDetailed=00015

Blue V3 attempts to address two issues that emerged in testing by forum members. The first is that some sticks are in reality less than 8x1000x1000x1000 bytes. The second is that some BIOSs will not boot from a USB stick without using some trickery.

When I first issued Blue I failed to anticipate the first problem and although aware of the second, did not realise just how common that problem is.

The above observations have been added to the second (FAQ) post in this thread which now contains 9 items as opposed to the original 4.
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

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

#168 Post by Billtoo »

I moved my flashdrive once again, this time to a pc with an nvidia
graphics card.
video-info-glx 1.5.3 Tue 8 Apr 2014 on Quirky Tahr 6.0.5 Linux 3.12.6 i686
0.0 VGA compatible controller: NVIDIA Corporation GT216 [GeForce GT 220] (rev a2)
oem: NVIDIA
product: GT216 Board - 0682vb12 Chip Rev
X Server: Xorg Driver: nouveau
X.Org version: 1.15.0
dimensions: 1920x1080 pixels (507x285 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: nouveau
OpenGL renderer string: Gallium 0.4 on NVA5
OpenGL core profile version string: 3.1 (Core Profile) Mesa 10.0.1
Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
Core 0: @2003 1: @2003 MHz

It booted to the desktop, I needed to run alsamixer in the terminal to
adjust the sound but that was it.
Attachments
screenshot3.jpg
(65.62 KiB) Downloaded 751 times

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

#169 Post by step »

One success, one failure + question.
Success: blue pup runs from my SDD. Got a V3 blue pup working on 8GB USB key. Prepared f2fs partition on SSD. Copied files from USB key f2fs partition to SSD. Edited config file in USB key vfat partition to point to the SSD f2fs partition /dev/sda5.
Failure: I have an old HP usb 1.1 memory key, 30MB, and I thought I could use it instead of my other 8GB USB key to hold the vfat boot partition. So, formatted hp key vfat, cloned vfat partition from 8GB USB key to 30MB hp key using gnost option 6, http://www.murga-linux.com/puppy/viewtopic.php?t=54231, shut down, replaced 8GB key with 30MB key, reboot. I can see the progress indicator "vmlinuz....<ready>" but then my PC reboots followed by the progress indicator again in an endless loop.
Questions: Where did I go wrong? What should happen, technically, after the progress indicator says "<ready>"?

gcmartin

#170 Post by gcmartin »

Hello @Step.

The problem, I think, is that the MBR does not contain the proper program to config file on the partition you formated on the USB1.1 stick. Changing the bootmanager to GRUB4DOS might help here.

I've never done the following with BLUE. But, its an idea.
While running your PUP
  • insert your USB1.1 stick.
  • blanks your stick
  • go to Menu>system>GRUB4DOS
  • Let GRUB4DOS setup stick
Try again.

You may have to set parms on the Blue entry in the config file to boot.
Here to help
Edited: to add problem thoughts
Last edited by gcmartin on Tue 08 Apr 2014, 20:31, edited 1 time in total.

Post Reply