Puppy Linux Discussion Forum

Hello. I inherited a "new" computer, ASUS UX360U, installed fossapup64 (dual boot with windows, installed through LICK)

At boot up, I get this error message (pict attached, I couldn't find the text file after booting). I wait those 60 seconds and the bootup continues and the machine seems to work fine.

Could you help me to solve or debug this problem?

Thanks very much.

I don't use installers myself.
If i were you i would format the puppy partition on your drive and copy the fossapup files over manually.

I am wondering about those kernel modules being loaded at that stage in the boot cycle. I'll eventually boot up a Fossapup64 and watch carefully what modules are getting loaded.

The error reports the module doesn't exist so it can not be loaded.

I see... The error referes to a fossapup64initmodules.txt file.

Content of that file is the following:

hid_sensor_custom,hid_sensor_hub,intel_ishtp_hid,hid_multitouch,intel_ish_ipc,intel_ishtp,i2c_hid

I could comment that line and see what happens...

Another detail I see: the computer has a touch screen , it's not working now.

UPDATE: removed the intel_ishtp_hid module (the one not found), using the Puppy Boot Manager, and the error went away, and the computer seems to work. I'm not sure about the effects of removing that module.

I'll see what's happening with the touch screen later.

If you have a USB stick, I believe this will allow your PC to boot FossaPUP64.. It is a pre-confiured, pre-made solution for booting any PUP/DOG including its enclosed FossaPup64

Further the solution I am offering ALSO offers to boot FATDOG which will navigate the desktop via its touchscreen, as well.

YOU will NOT need to install any of the PUPs/DOGs. It allows running all forum distros without the headaches of installs.

Pretty simple if you have a USB stick to do this booting for you. Post back here should you have any problems.

You could need to use a newer Linux kernel that has the support for your newer hardware.

The newer kernel may have the module that is needed.

Changing the kernel is not that hard.
This tells you how:
viewtopic.php?t=317

Touchscreen support in Puppy Linux, is not kept updated, until a newer version of Puppy, gets produced.
But a newer kernel may help.

No one Puppy version works on all computers.
May have to try a few to find the best fit for your hardware.
Always best to install to a USB stick, boot with that install, and see how it works, before doing an install to internal drive.

Thanks.

How can I get a newer kernel, newer than the fossapup or bionicpup kernels?

EDITED: Similar hardware (Asus Zenbook UX360C Notebook), same problem, same solution (removing one module from boot sequence):
viewtopic.php?t=5252&start=10

Get newer kernels here:
viewforum.php?f=65

When you click on one of the kernel topics. it will usually offer several ones compiled for different type puppies.
for Fossapup64 9.5 you want to use the ones compiled for it or Ubuntu Derivative Kernels.

I switched to Bionicpup by now, more familiar to me, and because the 1st thing I've tried to do with fossapup (to setup the touchpad) didn't work.

Would you mind to suggest me one newer kernel to try? I'm not sure what to look for.

The issue most likely is trying to load the module results in the module failing, specifically because there is *no* such device. Leave it be. The linux kernel will generally guess right as to what modules are needed. If the module being probed in is because of default configuration, I suppose that will have to be fixed by the maintainer of the puppy.

Try changing to this kernel:
viewtopic.php?t=6871

Thanks! Tried the 5.19 kernel, 1st thing I see is the wifi card not detected. Renamed the files again, back to the default 4,19 kernel.

I deleted the intel_ishtp_hid entry in the bionicpup64initmodules.txt file, no more errors at startup.

btw, this is the content of that file, created by the default save after 1st boot:

hid_sensor_custom,hid_sensor_hub,intel_ishtp_hid,hid_multitouch,intel_ish_ipc,intel_ishtp,i2c_hid

When you changed to the 5.19 kernel.
Did you also get the fdrv.sfs file and use it?

Yes, renamed both files vmlinuz and zdrv... and the system booted with those files. Original vmlinuz and zdrv were renamed too to avoid conflicts, but they were in the same folder.

The computer has some weird behaviors when I close the lid and open again, the "touchpad" seems to become crazy. But I'll face the ACPI problems later. It seems the computer never goes to sleep, it wakes up again after 1 second, but that problem has been reported many times in the forum, with different solutions.

Check /proc/acpi/wakeup. Although the names are cryptic, if you use a USB look for XHC or EHC(I). Depending on the uniqueness of the computer, your keyboard may no longer work to wakeup the machine if you disable the USB as a wakeup source. If it's a touchscreen generally touching it or pressing the special 'Windows' button will wake it up as an alternative to the keyboard..

It seems the suspend behavior is solved by now, adding this script:

viewtopic.php?f=4&t=3904&p=35872#p35872

to the /root/Startup folder

It sets everything inside the /proc/acpi/wakeup file to "disabled"

Actually I've edited the /root/Startup/acpi script and added those lines at the end.