Puppy Linux Discussion Forum

[icake]

I have created 6 half-Chinese language pets and 2 Chinese language pets for jl64-702 and they are now available for public sharing. For details please see here: http://www.murga-linux.com/puppy/viewtopic.php?t=82937&start=405

[stemsee]

Hi DryFalls

Have you added save directory loading to the initrd by chance? Maybe consider adding it. Save me some work lol.

stemsee

[eztuxer]

Hi dryfalls !

Same problem with alt gr key keyboard over here with azerty be latin 1 belgian keyboard.
I can't remember how to access boot parameter to try to input "pkeys=be", it's been too long ago since I used it last.
Also last versions do not detect my pci and usb wifi hardware.
Last I tried I was able to use a save file on USB stick.
Booting works fine.
On Fat House latest iso booting is dead, but before last updates everything worked fine; keyboard, sound card, wifi, etc... but no save file.
So what is needed is once again a blend of LH & FH
The best of both worlds in one package.
I am really missing Puppy since I had to switch to 64 bit, so far nothing is working for my Lenovo POS.
Except for Linux Mint and windblow$ 10

Thank you guys for all the work, it will work sometime soon.

[Dry Falls]

hey there eztuxer.
pkeys boot parameter goes after 'linux /vmlinuz' in grub2, or after 'append' in the others (syslinux, menu 1st, etc). Also, you might want to run with 5_JL64-702-8.sfs which has extra kbd utilities, including salix tools 'keyboardsetup' you can run from console or gtk wizard from menu. Also, the enlightenment DE runs a different setup/configuration altogether at the first time you run it. Might be worth a try. Meanwhile, here is a package with extra keymaps from fatdog 710...

@Stemsee, I fiddled some with save to directory in the init script, but usually ended up breaking it. As far as I have experienced, the only stable/trouble-free save-to-folder is in fatdog. Lighthouse has always had save-to-partition, quirky style, as an option. It is very well with flash media. A step short of full install. And contrary to what some have said, you can have multiple save-files on the same partition. With two or more (real or dummy) save files, select 0 at prompt and you will boot into pupmode 6 or 7.

df

[Dry Falls]

new host for JL64-update (sfs-update) package list. Click to unzip attached file and drop into /usr/sbin (replaces existing script)...

[eztuxer]

Found again how to enter pkeys=be (F1) and keyboard work fine now.
Also kb change remains in save file.
But still no internet.
oot# lspci
00:00.0 Host bridge: Intel Corporation Device 2280 (rev 35)
00:02.0 VGA compatible controller: Intel Corporation Device 22b1 (rev 35)
00:13.0 SATA controller: Intel Corporation Device 22a3 (rev 35)
00:14.0 USB controller: Intel Corporation Device 22b5 (rev 35)
00:1a.0 Encryption controller: Intel Corporation Device 2298 (rev 35)
00:1b.0 Audio device: Intel Corporation Device 2284 (rev 35)
00:1c.0 PCI bridge: Intel Corporation Device 22c8 (rev 35)
00:1c.2 PCI bridge: Intel Corporation Device 22cc (rev 35)
00:1c.3 PCI bridge: Intel Corporation Device 22ce (rev 35)
00:1f.0 ISA bridge: Intel Corporation Device 229c (rev 35)
00:1f.3 SMBus: Intel Corporation Device 2292 (rev 35)
02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter

root# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 174f:1173 Syntek
Bus 001 Device 005: ID 0bda:0821 Realtek Semiconductor Corp.
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 012: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter
Bus 001 Device 008: ID 0b05:1723 ASUSTek Computer, Inc. WL-167G v2 802.11g Adapter [Ralink RT2571W]
Bus 001 Device 006: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 001 Device 002: ID 05e3:0605 Genesys Logic, Inc. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root#

Xenial pup works fine (except numpad).
Xenialpup64 7.0.8.4 beta
Using it to post this, but I still prefer JLH & LHFD.
I know it will work soon.

[Dry Falls]

Hi ez.

(make sure python sfs module is loaded)

from wizardwizard -> startup | services,
disable (uncheck) Frisbee and restart to see if kernel & X (dhcp & wpa) can find/load your system. you can try frisbee.sh (newer frisbee for wlan) instead. Or disable both and from the menu, select Stemsee;s wifi-connect or another method. experiment. (may want to move frisbee_tray out of ~/Startup!)

Of course there's the 'connect' icon in the Desktop folder ('Launcher") but that is some pretty old stuff.

The kernel is configured pretty heavily for intel, but you could still try the firmware sfs addon in case something's missing.

Another thing to try is the network manager sfs, which contains other networking software as well and auto-loads the networking applet.

If you can find something that works for both eth0 and wifi/wlan, I'll change the default. Unfortunately, I only have eth0 hard-wired to the satellite. No way to test this stuff from here.

Thanks (really!)
df

[eztuxer]

df,

Removed frisbee from startup folder, however after reboot I still get some pesky OSD pop ups claiming "Sucsess" wlan2 connected, etc...

I think some other automatic setup is running in // as I am using the Puppy Network Manager which is working on all other puppies so far.

Also with Firefox I get this :

[Dry Falls]

@ez, sorry to be late coming back to you on this. Been digging out from flood season here. The base file has libraries and some modules for ca-certificates and js-185. Full packages are in sfs addon (js-185). Are you using an old (trusted) ~/.mozilla or new? If the latter, you will have to re-set up your services, passwords, etc. I have one .mozilla directory on the drive which I frugal link to every save file or distro I.m running.

meanwhile, several new sfs modules uploaded (including kodi16.1 (64bit). check sfs-update or browse gdrive (link in opening post - sort by modification date).

JL64-702.v2-delta.tar.gz (57M) contains a delta file to patch the previous iso. some significant changes including cgmanager fix (in rc.sysinit).
Rebuilt kde4 and broke it up into smaller packages.
New Devx to accommodate slackware64 package upgrades.
Kernel is 4.10.7 (although I use 4.7.6) with some changes to .config

Although I have a working plasma5-17.04 (kde5), JL64-702.sfs needs remastered with several slackware-current files which breaks pup_event if it's done right! So, removed alien kde from slapt-get repo. May later make a KLighthouse when slackware-current settles down. Meanwhile sticking with slackware64-14.2 and salix (which provides deps and won't install packages which will break the system).

More and more, I'm going back to xfce4 desktop which just feels sturdier than the other dm's, even with compiz running.

df

[stemsee]

Boot code to mount main sfs, not copytoram?

[Dry Falls]

[stemsee]

Doesn't work! Main file persistently copies to ram. I negated every instance in the init. There is some code for forcing copy2ram when more than 256mb ram is detected I think that is overriding everything else.

COPYEXTRASFS* gets asked during boot anyway and copies or mounts depending on input, so that is ok.

[Dry Falls]

I presume you've tried "pfix=nocopy" ("pfix=noram" is suppose to be the same).
In either case the base file is mounted at /initrd/mnt/tempfs.
Be that as it may, the initrd and init script still needs work, something I've been attempting with great difficulty. As well, event manager doesn't work as it suggests as far as the save dialog on shutdown under pupmode=12. For the time being, I've opted for noautosave, where copy-to-ram seems to make more sense.

df

[stemsee]

yep tried each/both ... !

[Dry Falls]

New iso uploaded (v. JL64-703). see o/p

If you have a save file (or save to partion), the first boot of your save session now correctly runs boot manager when x starts. The bottom of the last dialog box (push sfs) gives the option of ram or mount for future boots. This can be changed later.

df