Page 25 of 39
Posted: Fri 28 Jan 2011, 22:17
by Iguleder
Ummm ... I guess it's some download error or something. I tested the whole mechanism with both my packages and packages from other repos and it seems to work fine.
I'll play more with it to see if there's something I can do.
I'm also running Woof now to build a second LZO-compressed spup, this time with my new software center, new dbus/dhcpcd/rox/whatever and extra artwork. Should be the best puplet I've built
Posted: Fri 28 Jan 2011, 22:29
by nooby
cool will be intesting to test.
Posted: Fri 28 Jan 2011, 23:08
by Jim1911
Iguleder wrote:I'm also running Woof now to build a second LZO-compressed spup, this time with my new software center, new dbus/dhcpcd/rox/whatever and extra artwork. Should be the best puplet I've built
Great, looking forward to it. I hope the kernal will still support an 8 core machine.
Cheers,
Jim
Posted: Fri 28 Jan 2011, 23:27
by nooby
Will it be Jwm or Openbox or IceWM or what? Ooops maybe you already described that?
I hope it is not JWM because that one fail to show 1024x768 on my Acer while the others do show it.
Edit
I feel so stupid. There is only JWM for this puppy is it? I fail to find IceWM or how does one activated it?
spup-055 built from latest woof
Posted: Sun 30 Jan 2011, 18:54
by Billtoo
Hi 01micko
I compiled mplayer-export-snapshot.tar.bz2 and smplayer-0.6.9.tar.bz2
and made pets of them but they are too big to attach to this message.
Smplayer needed the qt-everywhere-opensource-src-4.7.1-i686.pet that
I made in Wary 5.0 installed before it would compile, the one that I
made in Spup didn't work for some reason.
Anyhow, SMplayer is pretty cool if you are thinking of adding another
multimedia app to Spup.
Posted: Tue 01 Feb 2011, 15:50
by musher0
Hello all!
Problem booting. Issuing a straight
leads to a kernel panic
It's avoided if I issue:
However, it takes forever to get to the set-up screens.
Once there, if I choose keyboard layout=cf
it can't find it, takes forever, and comes back to the keyboard_layout chooser.
Ok, I'm a patient guy: I choose en_US (the default), spup 055 goes to the xorgwizard options. I choose 1280x1024. But... again takes forever, stays in console mode and issues a warning:
Code: Select all
-sh:warning: setlocale: LC_COLLATE: cannot change locale (en_US): No such directory.
First time this has ever happened, with any puppy, and on any of my computers. I checked the DVD-RW: it's in good condition. As per BK's advice for puppy 4.1, I checked for the presence of any potential spup sfs: obviously none exists yet. As per another help site, I reinitialized the boot and disk sequence in the BIOS. Still no luck!
Omick0, you're a sadist! Showing us all the goodies, and not allowing us to access them!
Posted: Tue 01 Feb 2011, 16:05
by nooby
Many of the puppies that failed to boot for me now boot when I add this to the kernel line.
nosmp
I have no idea what it does though. Maybe does not help you? Each computer different. I use an Acer D250 with Atom N270 CPU
Posted: Tue 01 Feb 2011, 16:08
by musher0
Hi.
Me again.
Furthermore, when I type "exit" from the console screen, it goes to the pupsave file panel -- please note I wasn't able to access the desktop let alone really change any parameter or program. When I want to tab to the "no save" button, oops, I dsicover that the keyboard is jammed.
Looks obvious to me that a little more experimenting on the entrance and exit to this puppy might be required... Not that I want to be harsh, I know that everyone is doing this for free and that 1micko has a tremendous track record in puppy, but jeez...
Did I miss anything? I am not a happy husky just now...
Posted: Tue 01 Feb 2011, 16:11
by DaveS
nooby wrote:Many of the puppies that failed to boot for me now boot when I add this to the kernel line.
nosmp
I have no idea what it does though. Maybe does not help you? Each computer different. I use an Acer D250 with Atom N270 CPU
Hi nooby. nosmp is used when your computer does not have a dual-core processor.
Posted: Tue 01 Feb 2011, 16:15
by musher0
nooby wrote:Many of the puppies that failed to boot for me now boot when I add this to the kernel line.
nosmp
[...]
Fine, but where do you put it in the line?
puppy pfix=ram ... then the nosmp command?
Please provide an example. Thanks in advance.
PS. As an aside, there is no need for such a command in MyWolfe 0.21, for example, which also has a dual-core capable kernel.
Posted: Tue 01 Feb 2011, 16:32
by DaveS
musher0 wrote:
Fine, but where do you put it in the line?
puppy pfix=ram ... then the nosmp command?
Typically at the end of the boot parameters, something like this:
Code: Select all
kernel /spup/vmlinuz pfix=fsck pmedia=atahd psubdir=spup nosmp
Posted: Tue 01 Feb 2011, 17:04
by musher0
DaveS wrote:musher0 wrote:
Fine, but where do you put it in the line?
puppy pfix=ram ... then the nosmp command?
Typically at the end of the boot parameters, something like this:
Code: Select all
kernel /spup/vmlinuz pfix=fsck pmedia=atahd psubdir=spup nosmp
Oh, I see. But that's a grub line, isn't? How do you do it during a regular cd boot?
Posted: Tue 01 Feb 2011, 17:22
by nooby
One have to be fast. Barry set it up so one can do such editing. Very many years me did it so don't remember but either p as in puppy or SPACE bar to stop the boot.
Test small p first as soon as the BIOS goes over to boot the code on the CD.
You see something written on the screen indicating that it starts to boot the content.
Then you hit p and if that was fast enough you cointinue with uppy so it says puppy
And then find the end of the kernel line and add nosmp and hope for the best
Posted: Tue 01 Feb 2011, 17:28
by musher0
Thanks, nooby and DaveS.
I did what you suggested. However, I still get the "kernel panic" message.
Posted: Tue 01 Feb 2011, 17:31
by nooby
Such is sad. Maybe if you start a new thread and then if lucky some expert happen to see it and him get what is going on.
They often recommend that one burn slowly and check that it boot on other computers so one know that it is not about that one actual now.
My Packard Bell did boot on puppy but not another. So it can be about what kernel they use.
Posted: Wed 02 Feb 2011, 00:30
by 01micko
Hello Christian
Thanks for giving spup-055 a spin, even though it didn't seem to spin right for you.
Firstly, the slowness is due to pfix=nocopy, obviously it's reading from the cd (or dvd-rw in your case) very slowly (and my main machine is pretty fast). Now I have just booted into spup with the pfix=ram, nocopy parameter and chose cf keyboard, fr_CA locale and no issue, so this leads me to believe that you have a very localised problem. Let's see if we can't get it sorted.
In my opinion you may be experiencing some sort of read error from the dvd-rw. Can you try an ordinary cd? Or at least blank the dvd-rw and maybe burn slower? We really need to get you running in RAM as the drive will remain mounted for the nocopy option. I really can't think of much else the issue can be since I can't reproduce the problem, sorry I don't have any dvd-rw disks at hand, and if I get a new one it will indeed be just that, new!
Hope this is of some help.
Cheers
Posted: Wed 02 Feb 2011, 01:33
by musher0
Hi!
A burn on a straight CD-R finally did the trick.
Thanks.
Posted: Sat 05 Feb 2011, 10:38
by 01micko
update....
I'm guessing Barry will release a new woof soon, that's why spup is in a bit of a 'hiatus' at the moment.
Stay tuned..
Posted: Sat 05 Feb 2011, 11:14
by Iguleder
01micko, I compiled lots of packages usable by spup, including things like dbus, dhcpcd, coreutils and bash. These seem to work well.
The potential of spup is simply endless ... so ...
do we have a 5.3?
Posted: Sat 05 Feb 2011, 11:43
by 01micko
Iguleder wrote:The potential of spup is simply endless ... so ...
do we have a 5.3?
__________
I'll take a look at dbus, dhcpcd, coreutils and bash.
Cheers
