Puppy Linux Discussion Forum

I went searching and found this: https://wiki.gentoo.org/wiki/USB_mobile_broadband_modem

Perhaps it'll help?

There are flags available on the boot entry for puppy's init to configure where to locate a savefile, etc.

F96-CE can work, it has Geany.

Should make it immutable

You can use this instead if you insert it at the very top of each entry. Everything else can remain as-is.
search --no-floppy --set=root --fs-uuid UUID

Do you mean the savefile itself is expanding, or the contents inside?
Use GDMap to get an examination of where the storage space is going at /initrd/pup_ro1 or /initrd/pup_rw (It depends on some boot configuration so try both)

The EFI files should be located on the FAT32 partition flagged esp under /EFI/boot.

AUFS transparently handles this. It will always write to the RW layer and if there is none then it will fail as usual.

Filesystem type does not prohibit the ability to enter sleep. Remember, sleep saves in-memory contents of RAM, and makes the general assumption that whatever devices were connected will be connected when the machine wakes up.

The address change does not suggest any sort of auto reassignment by the local router. Are you sure you are not simply having automatic switching to another network?

Have you tried modprobe toshiba_acpi? Also please re-enable acpi while you're at it.
Otherwise I cannot think of much. I would suggest trying a newer kernel and see if perhaps it is fixed there.

I meant to say, upload it. Alternatively open them with a text editor and paste giant walls of text. Or use a paste service.

Once you get it to freeze again when resuming, please post the output of /var/log/previous.messages.

You need the devx and kernel sources usually. After that you can locate broadcom releasing the source code for the driver, and you can build that. Alternatively there may be pets available on the forum.

EDIT: Try quickpet updates. It may pull in the driver.

I may be wrong, but don't you need ACPI for various power-off states?

hm. i see the interface name is not wlan0, its eth0 it seems. To make sure, just do ip link show to verify it is eth0.
Replace wlan0 in the command with eth0 then. Or whatever its named. (Do not use lo)

If you want an android emulator use android x86 with libhoudini enabled in QEMU.
If you want wine, use a WINE appimage. Those should work out of the box, although you may want to specify WINEPREFIX.

F96-CE is the puppy being used. I believe that is the PKG being used, yes.

Hey, I'd like to suggest for the next release, to update the kernel config to have these options + modules enabled. This would allow battery management for some ASUS devices.

CONFIG_HOTPLUG_PCI=y
CONFIG_ASUS_WMI=m
CONFIG_ASUS_NB_WMI=m