********************************************************
boots from the slackware 12.2 kernel k2.6.27.7
nothing removed from the 4.12 base
tweaks added for stability only
full ROX theme I only added this because
I have used it for a long time on my box
and grew fond of it
hope you like it too

412 but as a lzm compressed sfs
saving size off the iso

make sure you dont have an old 4.12
puppy install because the sfs file
is different and will clash
with the slaxer_pup-4.12

just rename or remove any old sfs
or pupsaves start clean
and enjoy

----------------------------------------------------------------------------------
What is Slaxer_Pup? why post in cutting edge ?

1.)this is a new concept puppy with a focus on a different hardware detection config and kernel from our old friends at slackware 12.2

since they have been around along time you have a lot of hardware detection experience covering your back

2.)using a solid modern base puppy so you feel at home

could it be possible to join the two ?

yep

for those that know my work this is NOT a fatfree version
nothing was removed only more hard ware detection added
so that my focus could be on hardware support

the kernel and initrd.gz does that work for you under the hood

maybe some things wont get detected that gets detected on puppy
maybe somethings that aren't detected on puppy get detected on Slaxer_Pup

you'll never know if you don't try

most people just read a lot and don't post
but enjoy trying new things

so I encourage you to take a spin and report
your results even if its a "simple this worked on my box"
that would help me advance and help others

it would be even more helpful if you list what new hardware gets detected
and what doesn't get detected that got detected in 4.12

Note: everything got detected and works correctly on my box

big_bass_________________debian wheezy ,linux mint, slackware I use them all and they all have good points
Mint would be best for general users thoughEdited_times_total

However, since it has something do do with slackware, I wonder(hope) if it can utilize slackware repository.

I just read about non smp machine running smp puppylinux in this forum.

You mentioned about smp in your post. my computer is old P4 with just 1 cpu. Have you tried your puppy on a single cpu machine?

Please let me know more about your puppy.

Thank you.

John S

1.)every puppy version uses the puppy config even if someone changes the kernel

this slaxer_pup uses the config from slackware
big , big difference

thats like taking the motor out of one car and placing it in a different make car you cant see much difference unless you look under the hood

2.)if your motherboard doesn't have SMP
of course it will still work only you'll not take advantage of SMP

3.) as for slackware packages compatibility
that is and always will be based on what package you need

I compile packages for puppy and I compile packages for slackware
most work well on puppy from slackware if they are simple
not needing a menu entry but you must remember
slackware packages were compiled with different shared libs and
dependencies and you do have to know what are the differences
before jumping in to that so there is no easy black and white answer there I still build packages one at a time compiled from source
mostly

so still as always you should use packages built for puppy
they were hand made for puppys' use

this is puppy learn how to collect ISO's

big_bass_________________debian wheezy ,linux mint, slackware I use them all and they all have good points
Mint would be best for general users though

Ok first bug:
- Created pupsave on reboot on internal hd, not chooesen to copy puppy-files
- Next boot: picks up pupsave, boots well, just before X => than 'Module usbhid is missing' and dropped back to console.
- Tested 3 times => same result.

You may get messages about missing modules, if they are compiled into the kernel.
Usually they can be ignored then, as Puppys scripts just think, they are not available.
In seldom cases though, Puppys hardwaredetection might be irritated by this.

depending on if you selected x16 or x24
----------------
/etc/.XLOADED
true

**we posted at the same time thanks Mark
I always use xvesa_________________debian wheezy ,linux mint, slackware I use them all and they all have good points
Mint would be best for general users though

At the mouse selecter: Detected ps2 mouse OK, confirmed that.
Found k/b ok, this is a usb plug, connected to ps2 socket with adapter.

Also, at this screen, there was a message saying:
lp0: using parport0 (interrupt driven)
lp0: console ready

Rebooted, creating pup-save file. Not asked to save any other files.

First re-boot: mouse selecter came up, and said it has detected a serial mouse. I reselected ps2. But mouse would not work when boot-up was complete, nor would the k/b.

Rebooted again with usb mouse, and k/b plugged in to other usb socket.

Ran the connection wizard. No network detected. Went to do it manually as it suggested- got a long list of modules to choose to install. Huh? How should I know?
EDIT: Clarification: "Cannot see any active network devices"

Hmm...that Slackware hardware detection certainly looks thorough...and I like its comprehensive scsi probing...and, if I boot my rig (see sigblock) without the GeForce in, using the mainboard's built-in ATi Rage XL, it boots and runs OK. It sees both cores.

But...with the GeForce installed...it loads nvidiafb, then atyfb, then hangs. Puppy never did that. Worse, when I tried to reboot to my usual, got an "MBR bootloader missing" or-something-like-that error message.

So, I had to back up menu.lst and then reinstall grub to the mbr of both my first ata-100 drive and my first scsi drive, and then restore my usual menu.lst config files. Back in business.

Also had to reset the boot order in BIOS setup to scsi drives first. Not sure if the BIOS boot drive search order was reset to the default (CD first, then ide drives, then scsi drives) by Slack, or maybe done by my own BIOS when it found no good bootloader on any drive.