(old)Puppy Linux Discussion Forum

Posted: **Fri 18 Jan 2013, 20:19**

well X still won't load, even with the adrv, so I'll never know if the wifi works or not.

Posted: **Fri 18 Jan 2013, 20:23**

bark_bark_bark wrote:well X still won't load, even with the adrv, so I'll never know if the wifi works or not.

is the adrv loading?

try from that tty prompt:

sfs_load adrv-12.12.sfs
archpupx

and see if x will start.

Posted: **Fri 18 Jan 2013, 20:27**

That didn't work at all.

Posted: **Fri 18 Jan 2013, 20:31**

I have a laptop with Elantech touchpad

I think it is detected as mouse??(How do you make sure?)

The solution then would be to install psmouse-elantech from AUR
I did.

I had to add link 3.6.8 to 3.6.8-1-ARCH in /usr/lib/modules

it compiles OK and put new psmouse,ko in /usr/lib/modules/3.6.8-1-ARCH/update dir

When I restart nothing new? Is it auto-loaded?

can I please get some input?

Posted: **Fri 18 Jan 2013, 20:33**

bark_bark_bark wrote:That didn't work at all.

when you do:

Code: Select all

sfs_load adrv-12.12.sfs

from the tty prompt, does it say that the sfs file successfully loaded?

Posted: **Fri 18 Jan 2013, 20:35**

Actually the adrv automatically loads at start up, it's the fact that the main sfs gives a error when it is being copied to RAM, that could be causing errors.

Posted: **Fri 18 Jan 2013, 20:37**

Scooby wrote:it compiles OK and put new psmouse,ko in /usr/lib/modules/3.6.8-1-ARCH/update dir

i'd try moving psmouse.ko file inside the folder /lib/modules/3.6.8/misc and:

Code: Select all

depmod -a
modprobe psmouse

and see if modprobe loads it without an error. if so add psmouse to the addlist line in /etc/rc.d/MODULESCONFIG...and reboot, and hopefully it works.

Posted: **Fri 18 Jan 2013, 20:40**

bark_bark_bark wrote:Actually the adrv automatically loads at start up, it's the fact that the main sfs gives a error when it is being copied to RAM, that could be causing errors.

dammit, all that hard work no pay off. i'm not sure what to try next man.

Posted: **Fri 18 Jan 2013, 22:33**

I am thinking right now though that this could be3 the scenario here.

These are the (most likely) components that are conflicting with each other:

-The archpup.sfs/adrv.sfs - fighting over mount points
-mount points - explains why the archpup.sfs won't mount
-the kernel - not sure why
-the init system? - maybe

Hopefully someone could explain why a lot better...

EDIT: Also there is most likely a missing environment variable that is preventing from X from loading at start up. I think the variable deals with the window manager. Not sure though...

Posted: **Fri 18 Jan 2013, 23:28**

well let's test that theory....rename the adrv-12.12.sfs to xadrv-12.12.sfs....and see if the archpup-12.12.sfs loads to ram, now that the adrv doesn't exist. if so, afterwards try from the tty prompt:

Code: Select all

sfs_load xadrv-12.12.sfs
archpupx

Posted: **Fri 18 Jan 2013, 23:31**

I am not sure if it makes a difference. X should load on start-up pending that all the environment variables are there.

Posted: **Sat 19 Jan 2013, 07:22**

You are to be commended. With Hippie Peace

Posted: **Sat 19 Jan 2013, 08:12**

stifiling,
Think I fixed sfs_load to support different adrv names. Here is simple patch, with one line -
every sfs file beggining with adrv will be hidden.

Posted: **Sat 19 Jan 2013, 13:18**

You may want to reconsider both the adrv-* in DIDRTO_SPECS and adrv_* hiding in SFS_load
No time to test but I believe presence of multiple adrv SFSs may crash the system with adrv-* in DIDRTO_SPECS.
At the same time hiding adrv_* from SFS_load will make impossible to load and test, say, adrv_kde while you are running adrv_openbox.
"Because we can" does not apply to everything (hopefully you all follow US politics

)

adrv and ydrv are for the archpup developer/user to easier build and modify the total OS. Is not part of the user interface to be changed on the fly. For that you have SFS_load.
Mixing the 2 can end up in more confusion than "solutions".
People actually may want to use the system instead of just keep modifying it.

Posted: **Sat 19 Jan 2013, 13:49**

stifiling wrote:
Scooby wrote:it compiles OK and put new psmouse,ko in /usr/lib/modules/3.6.8-1-ARCH/update dir
i'd try moving psmouse.ko file inside the folder /lib/modules/3.6.8/misc and:
Code: Select all
depmod -a
modprobe psmouse
and see if modprobe loads it without an error. if so add psmouse to the addlist line in /etc/rc.d/MODULESCONFIG...and reboot, and hopefully it works.

tried the above, no complaints from modprobe
I didnt have the misc dir so I created it.

During startup there is a line saying module psmouse loaded.

This however changes nothing. Still doesnt read config files in /etc/X11/xorg.conf/10-synaptics

I have read a lot on arch forums but cannot get my head around this
I can add that basic touchpad works, buttons and moving cursor,
But no two-finger scroll and wot is worse every time I type I accidentally
graze touchpad, sensitivity is to high.

any suggestions? writing rule for udev concerning touchpad?
I am from windows and feel a little bit lost here in LInux-land,

See below info

from udevadm

Code: Select all

looking at device '/devices/platform/i8042/serio4/input/input1/mouse0':
    KERNEL=="mouse0"
    SUBSYSTEM=="input"
    DRIVER==""

  looking at parent device '/devices/platform/i8042/serio4/input/input1':
    KERNELS=="input1"
    SUBSYSTEMS=="input"
    DRIVERS==""
    ATTRS{name}=="ETPS/2 Elantech Touchpad"
    ATTRS{phys}=="isa0060/serio4/input0"
    ATTRS{uniq}==""
    ATTRS{properties}=="1"

  looking at parent device '/devices/platform/i8042/serio4':
    KERNELS=="serio4"
    SUBSYSTEMS=="serio"
    DRIVERS=="psmouse"
    ATTRS{resolution}=="200"
    ATTRS{rate}=="100"
    ATTRS{bind_mode}=="auto"
    ATTRS{resync_time}=="0"
    ATTRS{debug}=="0x01"
    ATTRS{description}=="i8042 AUX3 port"
    ATTRS{paritycheck}=="0x01"
    ATTRS{resetafter}=="5"
    ATTRS{reg_07}=="0x00"
    ATTRS{reg_10}=="0x0b"
    ATTRS{reg_11}=="0x00"
    ATTRS{reg_20}=="0x45"
    ATTRS{reg_21}=="0xff"
    ATTRS{reg_22}=="0xff"
    ATTRS{reg_23}=="0x00"
    ATTRS{reg_24}=="0x00"
    ATTRS{reg_25}=="0x00"
    ATTRS{reg_26}=="0x00"
    ATTRS{protocol}=="ETPS/2"

from /var/log/Xorg.0.log

Code: Select all

   103 [    36.282] (II) LoadModule: "mouse"
    104 [    36.282] (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
    105 [    36.282] (II) Module mouse: vendor="X.Org Foundation"
    106 [    36.282]    compiled for 1.13.0, module version = 1.8.1
    107 [    36.282]    Module class: X.Org XInput Driver
    108 [    36.282]    ABI class: X.Org XInput driver, version 18.0



253 [    37.181] (II) Using input driver 'mouse' for '<default pointer>'
    254 [    37.181] (**) Option "CorePointer" "on"
    255 [    37.181] (**) <default pointer>: always reports core events
    256 [    37.181] (WW) <default pointer>: No Device specified, looking for one...
    257 [    37.246] (II) <default pointer>: Setting Device option to "/dev/psaux"
    258 [    37.246] (--) <default pointer>: Device: "/dev/psaux"
    259 [    37.246] (==) <default pointer>: Protocol: "Auto"
    260 [    37.246] (**) <default pointer>: always reports core events
    261 [    37.246] (**) Option "Device" "/dev/psaux"
    262 [    37.290] (==) <default pointer>: Emulate3Buttons, Emulate3Timeout: 50
    263 [    37.290] (**) <default pointer>: ZAxisMapping: buttons 4 and 5
    264 [    37.290] (**) <default pointer>: Buttons: 9
    265 [    37.290] (II) XINPUT: Adding extended input device "<default pointer>" (type: MOUSE, id 6)
    266 [    37.290] (**) <default pointer>: (accel) keeping acceleration scheme 1
    267 [    37.290] (**) <default pointer>: (accel) acceleration profile 0
    268 [    37.290] (**) <default pointer>: (accel) acceleration factor: 2.000
    269 [    37.290] (**) <default pointer>: (accel) acceleration threshold: 4
    270 [    37.290] (II) <default pointer>: Setting mouse protocol to "ExplorerPS/2"
    271 [    37.581] (II) <default pointer>: ps2EnableDataReporting: succeeded

from xinput list

Code: Select all

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ <default pointer>                       	id=6	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ <default keyboard>                      	id=7	[slave  keyboard (3)]

Posted: **Sat 19 Jan 2013, 13:56**

mav,

if you see an idea you don't think will work....wouldn't it saves time if you'd just, voice your issues with it.......sooner?

i mentioned the * in DISTRO_SPECS 2 days ago.

another example of this was in the last thread, after you got the adrv working, and sim implemented it. you mentioned...2 days later "forget the adrive" and gave your reasons, but it's still like..........why'd u wait so long.

"Well now that you've got it all set up, here's some good reasons why you shouldn't use it."

come on man. that deserves a reply of, "Well after all this hard work, I think I'm going to just use it." The same reply as last time.

Posted: **Sat 19 Jan 2013, 14:29**

Scooby wrote:any suggestions? writing rule for udev concerning touchpad?

only thing i could suggest Scooby, which isn't much help, is...if it works in a traditional puppy, trying to probe that system to find what's making it 'tick'. and then trying to fit those pieces into archpup to see if it works.

is the two finger scrolling a feature on 'newer' laptops? it's not a feature that i use, so i'm not sure if any of my machines are even able to do it.

Posted: **Sat 19 Jan 2013, 15:00**

stifiling wrote:mav,

if you see an idea you don't think will work....wouldn't it saves time if you'd just, voice your issues with it.......sooner?

i mentioned the * in DISTRO_SPECS 2 days ago.

another example of this was in the last thread, after you got the adrv working, and sim implemented it. you mentioned...2 days later "forget the adrive" and gave your reasons, but it's still like..........why'd u wait so long.

"Well now that you've got it all set up, here's some good reasons why you shouldn't use it."

come on man. that deserves a reply of, "Well after all this hard work, I think I'm going to just use it." The same reply as last time.

stif, (

)
I'm kind of busy these days (and certainly can not reply or even see every post).

Regarding the older adrv discussion, was in the context of an app-less iso, if I remember correctly and not on a/ydrv itself.

Posted: **Sat 19 Jan 2013, 15:27**

mavrothal wrote:stif, ( )
I'm kind of busy these days (and certainly can not reply or even see every post).

ok. didn't know the * idea had gone unnoticed. this reply, from 2 days ago, had me thinking maybe u'd seen it.

mavrothal wrote:Regarding the older adrv discussion, was in the context of an app-less iso, if I remember correctly and not on a/ydrv itself.

whatever it was on, if you see a bad idea is being worked on, it would be appreciated if u'd voice the issues with it, 'before' it's finished....instead of 'afterwards'.

Posted: **Sat 19 Jan 2013, 15:48**

stifiling wrote:
only thing i could suggest Scooby, which isn't much help, is...if it works in a traditional puppy, trying to probe that system to find what's making it 'tick'. and then trying to fit those pieces into archpup to see if it works.

is the two finger scrolling a feature on 'newer' laptops? it's not a feature that i use, so i'm not sure if any of my machines are even able to do it.

First off, thanks for feedback

Two finger scrolling and mouse geastures is a question of driver and I got
a new machine - 1 year old anyway.

I tried Carolina puppy linux - vertical two finger scroll does work out of the
box. They dont have the same setup with xorg.conf.d though.

I will try copying it to archpuppy and adjust it.

One question in carolina they have a in xorg.conf

Code: Select all


Section "Module"

Load "synaptics"

EndSection

how is this opposed to loading drivers from MODULESCONFIG

(old)Puppy Linux Discussion Forum

ArchPup - First Puppy with pacman for installing apps

simargl --<>-- I salute you