Thanks! Will keep my eyes on them ...Ray MK wrote:Hi edoc
Sickgut is making a pARMy pUSSy-pUPPy from a debian arm source and I think that there is a reasonable chance that it could be made to work.
BK’s ARM puppy may also be a possible candidate in time.
HTH - very best regards - Ray
Dpup Exprimo 5.X.15
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
5X15 on my Panasonic Toughbook CF29 looks good ... except ...
Every now and then when I do a cold start I get a blank desktop and have to Restart X to get the proper display of background and icons.
Any idea where to look for the source of this anomaly?
This is how it is booted as Frugal from GRUB:
Every now and then when I do a cold start I get a blank desktop and have to Restart X to get the proper display of background and icons.
Any idea where to look for the source of this anomaly?
This is how it is booted as Frugal from GRUB:
# Linux bootable partition config begins
title Puppy Linux Squeeze Exprimo 5X15 (on /dev/sda2)
root (hd0,1)
kernel (hd0,1)/dpup5x15/vmlinuz pfix=fsck PMEDIA=idehd PDEV=sda2 psubdir=dpup5x15 acpi=noirq nosmp vga=normal
initrd (hd0,3)/dpup5x15/initrd.gz
# Linux bootable partition config ends
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Edoc. I dont use grub, but insted grub4dos...so I cant comment all your definitions, but....
PMEDIA accepts and understands these parameters: pmedia= usbflash|usbhd|usbcd|ataflash|atahd|atacd|atazip|scsihd|scsicd|cda
Above is straight from Puppy init script so...you can count that above is correct. There is no idehd.
I suggest you to use PMEDIA=atahd parameter
PDEV is wrong also, it should be PDEV1=
again from init script: [ $pdev1 ] && PDEV1=$pdev1 #boot parameter, partition have booted off. ex: hda3
You seem to have kernel and initrd.gz in different partitions ?
kernel (hd0,1)
initrd (hd0,3)
Should it be initrd (hd0,1) also, if you boot from sda2 partition.
acpi=noirq nosmp vga=normal ----> are you sure you need these ? They are kernel boot parameters, and possibly they are valid, you know better than me.
My suggestion as whole:
kernel (hd0,1)/dpup5x15/vmlinuz pfix=fsck PMEDIA=atahd PDEV1=sda2 psubdir=dpup5x15 acpi=noirq nosmp vga=normal
initrd (hd0,1)/dpup5x15/initrd.gz
or
kernel (hd0,1)/dpup5x15/vmlinuz pfix=fsck PMEDIA=atahd PDEV1=sda2 psubdir=dpup5x15
initrd (hd0,1)/dpup5x15/initrd.gz
But cant be sure...you had so strange boot parameters....
PMEDIA accepts and understands these parameters: pmedia= usbflash|usbhd|usbcd|ataflash|atahd|atacd|atazip|scsihd|scsicd|cda
Above is straight from Puppy init script so...you can count that above is correct. There is no idehd.
I suggest you to use PMEDIA=atahd parameter
PDEV is wrong also, it should be PDEV1=
again from init script: [ $pdev1 ] && PDEV1=$pdev1 #boot parameter, partition have booted off. ex: hda3
You seem to have kernel and initrd.gz in different partitions ?
kernel (hd0,1)
initrd (hd0,3)
Should it be initrd (hd0,1) also, if you boot from sda2 partition.
acpi=noirq nosmp vga=normal ----> are you sure you need these ? They are kernel boot parameters, and possibly they are valid, you know better than me.
My suggestion as whole:
kernel (hd0,1)/dpup5x15/vmlinuz pfix=fsck PMEDIA=atahd PDEV1=sda2 psubdir=dpup5x15 acpi=noirq nosmp vga=normal
initrd (hd0,1)/dpup5x15/initrd.gz
or
kernel (hd0,1)/dpup5x15/vmlinuz pfix=fsck PMEDIA=atahd PDEV1=sda2 psubdir=dpup5x15
initrd (hd0,1)/dpup5x15/initrd.gz
But cant be sure...you had so strange boot parameters....
Here's my menu lst for 5.X.15 with legacy Grub.....
I use the same basic entry with just the name and location different for all 15 frugal installs I'm presently running. Had to count 'em, didn't realize there were so many.....
Code: Select all
title Puppy Exprimo 5.X.15 frugal (2.6.39) in sda2
rootnoverify (hd0,1)
kernel /dpup/vmlinuz pfix=fsck pdev=sda2 pmedia=atahd psubdir=dpup nosmp acpi=force
initrd /dpup/initrd.gz
Is there a reason to prefer grub4dos over GRUB, please?pemasu wrote: I dont use grub, but insted grub4dos.
I think I have that on one of the laptops here but I don't recall why.
I don't recall when it was along the way that I had to use "PMEDIA=idehd" and whether it was hardware-related (specific to the Toughbooks or a Netbook anomaly or what) and then just was copied from there.pemasu wrote: I suggest you to use PMEDIA=atahd parameter
I will try "PMEDIA=atahd" and see how that works.
Oddly, I have the "1" in the menu.lst for the laptop but had cut and pasted from the file on this netbook where I do not. It has been working OK on the netbook - I wonder what is the purpose?pemasu wrote: PDEV is wrong also, it should be PDEV1=
I have added the "1" to the netbook menu.lst and will see what happens when I reboot.
That was a typo, sorry.pemasu wrote: You seem to have kernel and initrd.gz in different partitions ?
Those are all recommendations from the past when chasing various hardware problems. I don't recall if they are BIOS or hardware specific. Most of the same hardware has been in use here for several years.pemasu wrote: acpi=noirq nosmp vga=normal ----> are you sure you need these ?
JamesC has a recommendation as well.pemasu wrote: My suggestion as whole:
kernel (hd0,1)/dpup5x15/vmlinuz pfix=fsck PMEDIA=atahd PDEV1=sda2 psubdir=dpup5x15 acpi=noirq nosmp vga=normal
initrd (hd0,1)/dpup5x15/initrd.gz
or
kernel (hd0,1)/dpup5x15/vmlinuz pfix=fsck PMEDIA=atahd PDEV1=sda2 psubdir=dpup5x15
initrd (hd0,1)/dpup5x15/initrd.gz
I will experiment ... thanks!
David
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
That works too..... it boots with that section removed..... a smaller entry is better anyway.....new entry.
Code: Select all
title Puppy Exprimo 5.X.15 frugal (2.6.39) in sda2
rootnoverify (hd0,1)
kernel /dpup/vmlinuz pfix=fsck pmedia=atahd psubdir=dpup nosmp acpi=force
initrd /dpup/initrd.gz
I have grub4dos grldr and menu.lst in ntfs partition and I boot windows 7 (when I need it) and all my Puppies from that ntfs partition.Is there a reason to prefer grub4dos over GRUB, please?
It was easier for me and I also use Shinobar`s grub4dos bootloader config when I need. It has worked for me. It is just question of preferences. Use grub or grub4dos which ever you knows best. It is grub4dos for me.
Is there a functional difference between these two ways of handling the kernel part of the code?
Are they two equal ways to accomplish the same thing?
Or is it related to some difference between grub and grub4dos?
... and ...
... please?
Are they two equal ways to accomplish the same thing?
Or is it related to some difference between grub and grub4dos?
Code: Select all
kernel (hd0,1)/dpup5x15/vmlinuz
initrd (hd0,1)/dpup5x15/initrd.gz
Code: Select all
rootnoverify (hd0,1)
kernel /dpup/vmlinuz
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
- charlie6
- Posts: 1230
- Joined: Mon 30 Jun 2008, 04:03
- Location: Saint-Gérard / Walloon part of Belgium
PCTel modem chip 789 driver k2.6.39.4
Hi,
here is the PCTel modem chip 789 driver k2.6.39.4 driver
enjoy!
http://www.murga-linux.com/puppy/viewtopic.php?t=80394
here is the PCTel modem chip 789 driver k2.6.39.4 driver
enjoy!
http://www.murga-linux.com/puppy/viewtopic.php?t=80394
vlc don't work on my computer, which vlc pet works in Dpup Exprimo 5.X.15?
edited: i got it by getting qt-4.8.0-basic-with-qtwebkit-dpup.pet as instructed by pemasu.
here http://murga-linux.com/puppy/viewtopic. ... 508#636508
thanks
edited: i got it by getting qt-4.8.0-basic-with-qtwebkit-dpup.pet as instructed by pemasu.
here http://murga-linux.com/puppy/viewtopic. ... 508#636508
thanks
Re: Dpup Exprimo 5.X.15
pemasu wrote: First of all. This woof build is based on Iguleders work. He has single-handed done all the work for reviving dpup <snip snip>
ooooOOOOOOooo... I just noticed, multiple instances are working in this one !
pemasu... I think Iguleder fixed it while you werent looking : -)
The multiple instances were always a favorite feature of mine in the older dpup
series... so useful when experimenting with recent apps which might break the
good install... for other special uses too.
Thanks to both of you for getting dpup modernized and back together... for debian
people who use puppylinux, this is a real help. Ive been using it for over a month.
soundNICK
- Iguleder
- Posts: 2026
- Joined: Tue 11 Aug 2009, 09:36
- Location: Israel, somewhere in the beautiful desert
- Contact:
soundNICK, Exprimo is (IMHO) the strongest-going puplet I've seen and I think it has a very bright future ahead - it could be the next mainline Puppy.
But ... I believe it's just the beginning. It has endless potential! Before you give it the warm compliments it deserves, let's think of what the future holds for it.
I implemented Raspbian support in roar-ng (my distro building kit) while I'm waiting for Raspberry Pi to arrive. My next plan for the dpup world is to port it to ARM: Puppy for ARM exists and Debian for ARM exists, too. I just want to see how wonderful it could be if we fused the two together.
The first step is to build highly optimized ARMv6 packages - the rest will follow. That's the first thing I'm going to do when I get my Pi already. Using dpup as a platform for porting Puppy looks like a great idea to me - it could be any of Debian's supported architectures, you name it
By the way, today I got my distro to build for x86_64 against Slackware 14.0 packages - I don't see why it couldn't be Exprimo for ARMv6.
But ... I believe it's just the beginning. It has endless potential! Before you give it the warm compliments it deserves, let's think of what the future holds for it.
I implemented Raspbian support in roar-ng (my distro building kit) while I'm waiting for Raspberry Pi to arrive. My next plan for the dpup world is to port it to ARM: Puppy for ARM exists and Debian for ARM exists, too. I just want to see how wonderful it could be if we fused the two together.
The first step is to build highly optimized ARMv6 packages - the rest will follow. That's the first thing I'm going to do when I get my Pi already. Using dpup as a platform for porting Puppy looks like a great idea to me - it could be any of Debian's supported architectures, you name it
By the way, today I got my distro to build for x86_64 against Slackware 14.0 packages - I don't see why it couldn't be Exprimo for ARMv6.
[url=http://dimakrasner.com/]My homepage[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
Iguleder wrote:soundNICK, Exprimo is (IMHO) the strongest-going puplet I've seen and I think it has a very bright future ahead - it could be the next mainline Puppy.
But ... I believe it's just the beginning. It has endless potential! Before you give it the warm compliments it deserves, let's think of what the future holds for it.
I implemented Raspbian support in roar-ng (my distro building kit) while I'm waiting for Raspberry Pi to arrive. My next plan for the dpup world is to port it to ARM: Puppy for ARM exists and Debian for ARM exists, too. I just want to see how wonderful it could be if we fused the two together.
The first step is to build highly optimized ARMv6 packages - the rest will follow. That's the first thing I'm going to do when I get my Pi already. Using dpup as a platform for porting Puppy looks like a great idea to me - it could be any of Debian's supported architectures, you name it
By the way, today I got my distro to build for x86_64 against Slackware 14.0 packages - I don't see why it couldn't be Exprimo for ARMv6.
Iguleder - I couldnt agree more about Exprimo being a strongest contender... part of this...
a lot of it... is the debian connection. However much slower the debian development
cycle [appears] to be, debian remains one of the best developed most refined and
consistently working distros_ adding puppylinux scalability / flexibility to this has to be
a total win.
I -am- anxious to try your woof alternative, and build my own custom-pl sometime soon.
I am certain pemasu would concur - while it takes a devoted user-base to keep any
distro afloat, Exprimo and the success of dpup evolution has been largely due to your
persistence and insight.
best of luck with your projects
soundNICK
pemasu I installed the nvidia driver 295 from the repo but it appears to have been compiled against the wrong kernel. I'm in 5.x.15
See screeny.
See screeny.
- Attachments
-
- nvidia-problem.png
- (6.85 KiB) Downloaded 476 times
Smokey01. Yep, the nvidia driver...as the pet name says: http://smokey01.com/pemasu/pet_packages ... -[b]k3.4.2[/b]...is for kernel 3.4.2 version.
My dpups have tendency to have different kernels...
So...just use getnvidia pet and compile almost automatically nvidia pet by yourself.
Install from the repo getnvidia, load devx sfs and kernel source sfs and let the getnvidia do the job.
My dpups have tendency to have different kernels...
So...just use getnvidia pet and compile almost automatically nvidia pet by yourself.
Install from the repo getnvidia, load devx sfs and kernel source sfs and let the getnvidia do the job.
It's all good. The only reason I mentioned it was maybe there is a way we can make the PPM only download the appropriate packages for the distro, kernel specific.
BTW, CatDude and I have modified puppyluvr Multipup. It now works with FatDog, Slacko and Saluki providing Rox is installed.
I will try it on Exprimo, I would expect it to work now.
http://www.smokey01.com/software/Fatdog ... Hacked.pet
Cheers
BTW, CatDude and I have modified puppyluvr Multipup. It now works with FatDog, Slacko and Saluki providing Rox is installed.
I will try it on Exprimo, I would expect it to work now.
http://www.smokey01.com/software/Fatdog ... Hacked.pet
Cheers
pemasu wrote:Smokey01. Yep, the nvidia driver...as the pet name says: http://smokey01.com/pemasu/pet_packages ... -[b]k3.4.2[/b]...is for kernel 3.4.2 version.
My dpups have tendency to have different kernels...
So...just use getnvidia pet and compile almost automatically nvidia pet by yourself.
Install from the repo getnvidia, load devx sfs and kernel source sfs and let the getnvidia do the job.
Smokey01. I think there is mechanism in PPM not to show inappropriate packages. I think all goes how you create pet.specs file. I should dig Barry Kaulers blog. I remember there was post how to do it. I have been just lazy.
Or...not lazy...just hands full with other thing. Posting this from debian wheezy packages based dpup. But this is just very pre-alpha construct. Dont ask me to post this for a long time. But it works now. A lot of missing packages, I am sure when I start to debug applications.
Or...not lazy...just hands full with other thing. Posting this from debian wheezy packages based dpup. But this is just very pre-alpha construct. Dont ask me to post this for a long time. But it works now. A lot of missing packages, I am sure when I start to debug applications.
Cheers pemasu,
I second iguleder's recent sentiment about Exprimo's future potential - please don't feel too lonely that you seem to be the only Dpup developer and therefore demand for this main derivative is in decline . It is my go-to pupplet on my Lenovo T60 - and I have about 6 others to choose from - because I find it the most stable and pleasurable to use, so my compliments to you!
I missed the notice that you'd upgraded to 5.X.15, so will overhaul my 5.X.14 setup presently. In the meantime, I was casting an eye over your pet repository and wonder if I might post a few requests for pets please? These may well work just as fine as the native linux (deb, tar.gz) formats that I have cobbled together, but perhaps a proper pet packaging might smooth out the odd glitch when running in Puppy/dpup:
1) Docear http://www.docear.org/software/download/. Research tool: mindmapping, pdf file management and bibliography creation, with planner features included. Just gone to beta v.5 and nearly ready for the Big Release. I haven't the nous to package it into a pet myself, but would love to see someone compile it for dpup. However, it really needs a pdf reader with annotation support. I've gone straight to Foxit Reader (a habit from my daze in XP) but the linux version doesn't support annotations. Searching on the forums I found that muggins (I think) recommended XPDF+Xournal as a great open-source alternative. You already have created a pet of the latest Xournal 0.4.5 I see, so could I also request:
2) XPDF 3.0.3. ftp://ftp.foolabs.com/pub/xpdf/ [abushcrafter created pets yonks ago, but I can't find any live links to his efforts]
Thanks in advance to anyone who can compile and post pets for the dpup (and wider) collective,
Cheers
UPDATE: XPDF was a relatively simple exercise of copying the relevant files from the tar.gz to their locations outlined in the 'READ ME' - works fine in 5.X.14 and just some cosmetics required to nominate it as the default PDF reader. Docear is similarly working very sweetly straight from the tar.gz extracted into the root directory - just menu entries, desktop icons etc lacking, but I bet I can whip up a hotkey combo to have it running immediately on command. Xournal I see has recently been updated to 0.4.7, but your 0.4.5 version works fine, pemasu.
I second iguleder's recent sentiment about Exprimo's future potential - please don't feel too lonely that you seem to be the only Dpup developer and therefore demand for this main derivative is in decline . It is my go-to pupplet on my Lenovo T60 - and I have about 6 others to choose from - because I find it the most stable and pleasurable to use, so my compliments to you!
I missed the notice that you'd upgraded to 5.X.15, so will overhaul my 5.X.14 setup presently. In the meantime, I was casting an eye over your pet repository and wonder if I might post a few requests for pets please? These may well work just as fine as the native linux (deb, tar.gz) formats that I have cobbled together, but perhaps a proper pet packaging might smooth out the odd glitch when running in Puppy/dpup:
1) Docear http://www.docear.org/software/download/. Research tool: mindmapping, pdf file management and bibliography creation, with planner features included. Just gone to beta v.5 and nearly ready for the Big Release. I haven't the nous to package it into a pet myself, but would love to see someone compile it for dpup. However, it really needs a pdf reader with annotation support. I've gone straight to Foxit Reader (a habit from my daze in XP) but the linux version doesn't support annotations. Searching on the forums I found that muggins (I think) recommended XPDF+Xournal as a great open-source alternative. You already have created a pet of the latest Xournal 0.4.5 I see, so could I also request:
2) XPDF 3.0.3. ftp://ftp.foolabs.com/pub/xpdf/ [abushcrafter created pets yonks ago, but I can't find any live links to his efforts]
Thanks in advance to anyone who can compile and post pets for the dpup (and wider) collective,
Cheers
UPDATE: XPDF was a relatively simple exercise of copying the relevant files from the tar.gz to their locations outlined in the 'READ ME' - works fine in 5.X.14 and just some cosmetics required to nominate it as the default PDF reader. Docear is similarly working very sweetly straight from the tar.gz extracted into the root directory - just menu entries, desktop icons etc lacking, but I bet I can whip up a hotkey combo to have it running immediately on command. Xournal I see has recently been updated to 0.4.7, but your 0.4.5 version works fine, pemasu.
Last edited by Puppyt on Mon 20 Aug 2012, 13:20, edited 1 time in total.
Search engines for Puppy
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...
[url]http://puppylinux.us/psearch.html[/url]; [url=https://cse.google.com/cse?cx=015995643981050743583%3Aabvzbibgzxo&q=#gsc.tab=0]Google Custom Search[/url]; [url]http://wellminded.net63.net/[/url] others TBA...
There is but I hadn't noticed it before. I will give it a try.pemasu wrote:Smokey01. I think there is mechanism in PPM not to show inappropriate packages. I think all goes how you create pet.specs file. I should dig Barry Kaulers blog. I remember there was post how to do it. I have been just lazy.
Thanks