Asus Zenbook 14X Touchpad and DPI issues in BookwormPup64_10.0.4

[vtpup]

Hi all,
After trying other Puppy versions with a recent gift laptop (Asus zenbook 14X OLED) it seems Bookworm is the most likely to be successful. The other Pups are not recent enough.

Tap issue: Bookworm displays full resolution on startup. Touchpad works for scrolling the cursor, but the tap function does not work to select anything. I tried adjusting through the touchpad/mouse wizard but it does not seem to be an adjustment issue. It's just non-responsive to tapping altogether.

Native resolution for this laptop is 2880x1800

Hardinfo reports:
Mesa Intel Graphics (RPL-P),
ASUE140D:00 04F3:31B9 Touchpad
ELAN9008:00 04F3:40C3 UNKNOWN

DPI issue: Another problem I'm having is that the resolution is so high that text is practically unreadably tiny on startup. As a quick fix I tried changing the overall resolution via the display wizard but that doesn't seem to be able to actually change the resolution. I tried 1440 x 900 but there's actually no change when I switch to it.

Elsewhere I can change the screen DPI to 150 -- the maximum -- that helps a little but everything still is painfully small for my eyes, and when I measure across the screen the actual measured true DPI is 240. Ideally I should be able to change the DPI to 240 or more to solve the readability problem, but that's not an available choice.

Any help on the touchpad tap and DPI issues would be greatly appreciated. Thanks!

[vtpup]

Well I feel dumb -- the notebook has a clickpad, I assumed it was just a touchpad, based on Chromebooks I've used. There's no mention of click function on the quick start guide or stickers. A lot on using the pad as a numeric keypad, etc.

And the physical pad clicks do work in Bookworm. That's sufficient and preferred to tapping for me. So I'm okay with that and the pad is now usable. Still, others might want tapping enabled, and I haven't got that working yet.

Next in importance though is getting 240 DPI resolution. Bookworm offers up to only 150 DPI via the Font adjustment.

Help would still be appreciated for increasing the available settings to 240 (or more)

[wizard]

display wizard but that doesn't seem to be able to actually change the resolution. I tried 1440 x 900 but there's actually no change when I switch to it.

Did you try changing in both xorg and xandr?

wizard

[vtpup]

I tried the graphical Display Settings app from the Desktop menu, which seems to be eDP-1 (lxrandr) just now and tried a setting of 800x600. Screen changed to black very briefly and returned to original resolution, though indicating that 800x600 was in effect, and asked if I wanted to save this.

My greater need is not to actually change the number of screen pixels, but to change the DPI to more than 150 -- which is the limit offered.

Ideally DPI should be 240. Then the actual pixel counts can stay at high res, which is a nice feature otherwise.

[vtpup]

It looks like I can change /.Xresources line

Code: Select all

 Xft.dpi: 150

to 240, and that will increase the font size.

After fiddling with a number of Tray, Drive Icon, and Windows settings in Menu>PupControl I've got most things looking normal with the increased font size.

However the ROX control icons at the top border of a ROX window are still tiny. And the icons on the JWM desktop are also very small, though usable. I can't find a way to increase the size of the JWM desktop icons in the PupControl settings -- am I missing something?

[wizard]

@vtpup

I change the res with Menu>Setup>Puppy Setup>Graphics/Screen>xrandr

wizard

[vtpup]

Thanks Wizard, that worked if I chose 1440 X 810 60 Hz. The refresh rates were not visible for higher resolutions because the dropdown menu was too narrow to show all the digits.

I did some more tests just to check possibilities.

1.) Xorg resolution settings do not work on this computer.

2.) The reason the Display Settings app from the Desktop menu ( eDP-1 lxrandr) did not work earlier was because the refresh rate was set by default to auto. I was able to get it to work if I set it to 1440 x 810, and if I changed the refresh rate to 60.

Native resolution on this computer is 2880 X 1800 120 Hz refresh. 60 works because it's an even divisor.

[wizard]

@vtpup

Native resolution on this computer is 2880 X 1800 120 Hz

That would be good for a 32 inch laptop

You could avoid all this by trading for a 2015-18 Dell or Lenovo

Thanks for updates
wizard

[TerryH]

2.) The reason the Display Settings app from the Desktop menu ( eDP-1 lxrandr) did not work earlier was because the refresh rate was set by default to auto. I was able to get it to work if I set it to 1440 x 810, and if I changed the refresh rate to 60.

Just wondering why you didn't use 1440 x 900, which would keep the same ratio of 16:10 as the original dimensions? Using 1440 x 810 gives a 16:9 ratio.

[dimkr]

X.Org doesn't support fractional scaling, you'll run into many issues, especially if you don't use 100% or 200% scaling. Try to put 192 in Xft.dpi (it's in units of 96) and use the native resolution, that will double the size of text but icons will still be small compared to text.

[vtpup]

2.) The reason the Display Settings app from the Desktop menu ( eDP-1 lxrandr) did not work earlier was because the refresh rate was set by default to auto. I was able to get it to work if I set it to 1440 x 810, and if I changed the refresh rate to 60.

Just wondering why you didn't use 1440 x 900, which would keep the same ratio of 16:10 as the original dimensions? Using 1440 x 810 gives a 16:9 ratio.

It wasn't available in the dropdown for xrandr.

[vtpup]

X.Org doesn't support fractional scaling, you'll run into many issues, especially if you don't use 100% or 200% scaling. Try to put 192 in Xft.dpi (it's in units of 96) and use the native resolution, that will double the size of text but icons will still be small compared to text.

After a lot of experimentation I'm presently running 1680 x 1050 with 114DP. which gives me reasonably high resolution, and reasonably large icons. So far I've tested Kdenlive video editor, MPV videos, and Seamonkey on Youtube, Just installed Wine, and going to try Google's old SketchUp CAD in that. These are all demanding graphics applications. And commonly used programs for me. So far no problems with anything tested. I'll report back if I run into anything.

I don't like the feel of the touchpad so far after lots of adjustments to speeds pressures, etc. One problem is if you are touching the physical click button area of the pad with one finger it makes scrolling with the other hesitate the cursor movement. My older computer had separate buttons, not under the touchpad and I'm used to using left hand for buttons and right for scrolling simultaneously.

I'd really like it if I could map the touchpad so the scroll area doesn't overlay the button area.

[vtpup]

Well so far it's a no-go for getting Google SketchUp7 or SketchUp8 8 running on Wine. I think the main problem is which version or type of wine to use on BookwormPup64. Both SketchUps I use are old 32 bit versions. They run fine on my old Acer laptop running Bionicpup64 with Wine version 3.15.

For this new computer and BookwormPup64 I tired installing Wine through Synaptics, and that yields version 8. That may be too much. I also tried the Mikeslr Wine portables -- one was Wine 3.x the othe Wine 7.x. They didn't seem to install right -- or not as I would have expected. They put a Wine directory (not hidden) up on / . I'm used to /root/.wine . Other problems arose -- installation wasn't persistent across reboots -- the wine command in terminal couldn't be found.

Sketchup7&8 are must haves for me. I might have to return this computer to my nephew -- I hope he can return it -- it was new, and undoubtedly expensive. This is very upsetting for me, I really don't want to make him feel bad after he did this amazing thing for me.

[Zimpler]

On one of my Asus laptops, had the same desire to tap, but couldn't. I found that in the bios setup, buried where I wasn't even looking for it, I found a setting for Mouse: Windows or Mouse: Normal.

I never would have thunk it, but changing it to normal resolved that issue. I was tearing my hair out with synaptic etc, and only saw this later by looking for something else. Just saying - if you have a laptop, look at all the bios settings!