site  contact  subhomenews

Spup14: plain-vanilla 14.0

March 23, 2013 — BarryK
01micko has sent me fixes for Woof to build Slacko 5.5, however I have not yet integrated them into Woof. Will do that soon.

What I have done now, though, is create a "plain vanilla" Spup build. This is without many enhancements that are in Slacko. It also still uses module-init-tools.

In woof, when you run 'merge2out', choose "slackware" then "spup14".

I did a test build, but can only run the Xorg 'vesa' driver. Same problem as for the Arch Puppy build, with the 'intel' driver I get a black screen.
In both cases, /var/log/Xorg.0.log has some error message about drm. I will need to do a search with google. Maybe it is something to do with more-recent xorg xerver and/or intel driver.

I have not yet tried Slacko 5.5. The previous Slacko release worked on my laptop.

Another mystery to solve.

Anyway, Woof commit:

I think that I might rewrite the Xorg Wizard from scratch. It has become too cumbersome.
One fundamental problem, if you get a black screen, and you then boot up with "pfix=nox", then run 'xorgwizard' and choose the 'vesa' driver, it might not work, as it is incompatible with the already-loaded KMS-enabled i915 kernel driver.
KMS has to be disabled and/or the i915 kernel module blacklisted, then reboot, then run xorgwizard and choose vesa.
...which is too complicated for newbies.


Slacko 5.5 works
Username: BarryK
I have downloaded Slacko 5.5, running it now. The Xorg 'intel' driver is working. I had better make that the next on my to-do list to integrate 01micko's Slacko-fixes into Woof. And then try and figure out why my plain-vanilla Spup is broken.

Username: Raffy
"PHATslacko uses the 3.8.2 kernel and handles nicely the Intel NM10 chip coupled with a 1024x600 screen. Upup Precise 3.8.x does, too. See [url=]this. NM10 is able to support fanless laptops and board-processor combo, which are the "proper" Puppy machines. :)

black screens
Username: aarf
"this is for newbs that can read AND who get black screens. havent tried yet,

drm failure
Username: BarryK
"For Spup, this is the elevant part of /var/log/Xorg.0.log: [code][ 110.882] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [ 110.883] drmOpenDevice: node name is /dev/dri/card0 [ 110.887] drmOpenByBusid: Searching for BusID pci:0000:00:02.0 [ 110.887] drmOpenDevice: node name is /dev/dri/card0 [ 110.891] drmOpenByBusid: drmOpenMinor returns -1 [ 110.891] drmOpenDevice: node name is /dev/dri/card1 [ 110.895] drmOpenByBusid: drmOpenMinor returns -1 [ 110.895] drmOpenDevice: node name is /dev/dri/card2 [ 110.899] drmOpenByBusid: drmOpenMinor returns -1 [ 110.899] drmOpenDevice: node name is /dev/dri/card3 [ 110.903] drmOpenByBusid: drmOpenMinor returns -1 [ 110.903] drmOpenDevice: node name is /dev/dri/card4 [ 110.907] drmOpenByBusid: drmOpenMinor returns -1 [ 110.907] drmOpenDevice: node name is /dev/dri/card5 [ 110.911] drmOpenByBusid: drmOpenMinor returns -1 [ 110.911] drmOpenDevice: node name is /dev/dri/card6 [ 110.915] drmOpenByBusid: drmOpenMinor returns -1 [ 110.915] drmOpenDevice: node name is /dev/dri/card7 [ 110.919] drmOpenByBusid: drmOpenMinor returns -1 [ 110.919] drmOpenDevice: node name is /dev/dri/card8 [ 110.923] drmOpenByBusid: drmOpenMinor returns -1 [ 110.923] drmOpenDevice: node name is /dev/dri/card9 [ 110.927] drmOpenByBusid: drmOpenMinor returns -1 [ 110.927] drmOpenDevice: node name is /dev/dri/card10 [ 110.931] drmOpenByBusid: drmOpenMinor returns -1 [ 110.931] drmOpenDevice: node name is /dev/dri/card11 [ 110.935] drmOpenByBusid: drmOpenMinor returns -1 [ 110.935] drmOpenDevice: node name is /dev/dri/card12 [ 110.939] drmOpenByBusid: drmOpenMinor returns -1 [ 110.939] drmOpenDevice: node name is /dev/dri/card13 [ 110.943] drmOpenByBusid: drmOpenMinor returns -1 [ 110.943] drmOpenDevice: node name is /dev/dri/card14 [ 110.947] drmOpenByBusid: drmOpenMinor returns -1 [ 110.947] drmOpenDevice: node name is /dev/dri/card15 [ 110.951] drmOpenByBusid: drmOpenMinor returns -1 [ 110.951] drmOpenDevice: node name is /dev/dri/card0 [ 110.955] drmOpenDevice: node name is /dev/dri/card0 [ 110.959] drmOpenDevice: node name is /dev/dri/card1 [ 110.963] drmOpenDevice: node name is /dev/dri/card2 [ 110.967] drmOpenDevice: node name is /dev/dri/card3 [ 110.971] drmOpenDevice: node name is /dev/dri/card4 ......deleted...... [ 111.017] drmOpenDevice: node name is /dev/dri/card15 [ 111.021] (EE) intel(0): [drm] Failed to open DRM device for pci:0000:00:02.0: No such file or directory [ 111.021] (EE) intel(0): Failed to become DRM master.[/code] A google search gives a [i]lot[/i] of hits!

drm compare
Username: BarryK
"Running Precise Puppy, this is what it is supposed to look like: [code] 43.241] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [ 43.241] drmOpenDevice: node name is /dev/dri/card0 [ 43.241] drmOpenDevice: open result is 7, (OK) [ 43.241] drmOpenByBusid: Searching for BusID pci:0000:00:02.0 [ 43.241] drmOpenDevice: node name is /dev/dri/card0 [ 43.241] drmOpenDevice: open result is 7, (OK) [ 43.241] drmOpenByBusid: drmOpenMinor returns 7 [ 43.241] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0 [ 43.241] drmOpenDevice: node name is /dev/dri/card1 [ 43.241] drmOpenDevice: open result is 7, (OK) [ 43.241] drmOpenByBusid: drmOpenMinor returns 7 [ 43.241] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0 [/code]

Spup solved
Username: BarryK
"OK, solved it. The problem is the 'eudev' package, the alternative to 'udev'. It is not creating some device nodes. Especially, not creating /dev/dri/* needed by intel video. I went back to our old udev 167, and everything works. The same solution will apply to my earlier build of Arch Puppy.

crazy/quirky idea
Username: technosaurus
"I wonder if anyone has ever thought of building a Slack-arch-bunt-drake-bian-??? system that contains binaries and libraries for multiple distros simultaneously and controlled by the user based on preference by changing $PATH and $LD_LIBRARY_PATH such as: PATH=/ubuntu/bin:/ubuntu/sbin ... etc... (hopefully not too many warnings about changed path due to compiling with rpath) This is not within puppy's normal target by any means, but could be _EXTREMELY_ useful for hosting a large number of systems on a single server using lxc and linux containers while still giving users a choice of what distro to use. This could allow thousands of users simultaneously and, compared to other virtualization targeted distros, relatively lightweight

re crazy/quirky idea
Username: scsijon
"nice idea technosaurus, but, with the different release versions and builds between packages, especially libs I suspect you would always be chasing your tail with problems. I don't say it would not be do-able but whoever builds the pup would have to have a big team to support packages, as a lot of packages I think would have to have the matching source dependancies and that could be a problem when two apps need the same libset when they have been compiled differently on the source distributions.

Service Pack?
Username: Raffy
"Re "..I went back to our old udev 167, and everything works." - is a service pack needed for the 5.5 puppies?

Re udev 167
Username: BarryK
"Raffy, All the 5.5 pups have udev 167. This problem is only for this latest experimental Spup build.

Tags: puppy