Puppy Linux Discussion Forum

[stifiling]

[peebee]

Wifi is working much better in the 12.12.2 version - still need to put b43 into the /etc/rc.d/MODULESCONFIG addlist to get the driver to load and Pwireless2 doesn't manage to re-establish a working connection after a reboot without manual intervention (restart wpa-supplicant on the debug tab seems to do the trick).

Has anybody managed to get a synaptics touchpad working? I've installed xf86-input-synaptics-1.6.2 and its dependency mtdev-1.1.3-1 and edited /etc/X11/xorg.conf.d/50-synaptics.conf as shown on the Arch Linux wiki but I still don't have edge scrolling on my touchpad.....

Finally, I have a problem when I try to load the archdev-12.12.2.sfs - it just hangs on the message that it is running the pinstall script....

Cheers
peebee

[mavrothal]

simargl, stifiling, et al,

this IS the full initrd patch that will allow adding in the fs-union an another (applications for example) sfs.

The name of the additional sfs is defined in DISTRO_SPECS and in this case in "adrv_arch_1212.sfs" but I it could be anything.
The DISTRO_SPECS also uses DISTRO_IDSTRING but this is not necessary for the system to work. Just better.

No changes outside initrd are needed for the system to work.

To be fair I did not do much .
Just adapted jemimah's code from Saluki for the latest woof initrd/init (last comment: 120328).
Should work in any recent puppy with this init and probably others (tried it with today's woof version and works fine)

[stifiling]

mavrothal, can u upload the working initrd.gz file. i don't know how to apply the patch.

[mavrothal]

[stifiling]

thanks man...it's working perfectly and is extremely useful.

[mavrothal]

[simargl]

Thanks mavrothal , now I will test this, but could you just explain is adding DISTRO_IDSTRING really necessary, and in patch is +DISTRO_IDSTRING='l212ARCH09012013XXXXXXXXXXXX1234', maybe it should be 1 not l. What name would you choose for DISTRO_ADRVSFS in archpup, we should choose it now and always use the same. I've made one change in /etc/profile suggested by jamesbond, moved settings for WINDOW_MANAGER to /etc/profile.d/openbox.sh, and added this in /etc/profile.

[stifiling]

my idea is that"

adrv=archpup-DE-*.sfs (or whatever name)
zdrv=archapps.sfs

so that way, if there's an archpup-DE-xfce.sfs...it'll load that one, or if they switch to an archpup-DE-kde.sfs instead...it'll load that one. keeping the archapps.sfs separate, easily upgradeable, and ready to use with any archpup-DE-*.sfs environment.

also moving openbox out of the main.sfs...and into the adrv, will take the .xinitrc and .start scripts with it.

so an xfce.sfs won't have to fight with it...it will have it's on .xinitrc file. which won't exist in the main.sfs

[mavrothal]

[stifiling]

yes the zdrive is traditionally used for the modules. but archpup isn't using it at all. So this is a good way to put it to use. And not just to use it, but using it for a great reason.

so using those 3 sfs files would have the iso set up for any level of user. shed the archapps.sfs if all you want is DE for intermediates. shed the DE.sfs if all you want is base functionality, for experts.

so if the question is ever asked, "Anybody know of a distro for beginners?" the answer is Archpup

"Anybody know of a distro for intermediates?" Archpup

"Anybody know of a distro for experts?" Archpup

[mavrothal]

[stifiling]

[Scooby]

Thought I shared how I got rid of screen tearing on my hardware setup.

I have Intel graphics

Add file /etc/X11/xorg.conf.d/20-intel.conf with the following content:

[Scooby]