next »

[anthill]

No, it is not working with the external monitor - have a look at the X.org log I edited into my previous post.  I think the GLX module is complaining?

If you look at /etc/rc.d/rc.local lines 7-25 you'll see how the xorg.conf is set depending on the dongle being present or not.
As, I said theoritically it should just work. You are to tell us if it does

Aha, I see!  Well commented to boot!  

The problem is that my machine still has a /dev/sisusbvga0 entry, despite having been rebooted without the dongle.  Perhaps the file gets saved as part of my Puppy Save File?

Maybe it would be better to grep lsmod for sisusbvga?  Or is there something in /sys that would give an indication?

[mavrothal]

No, it is not working with the external monitor - have a look at the X.org log I edited into my previous post.  I think the GLX module is complaining?

I do not see any Xorg.log. Please reattach

The problem is that my machine still has a /deb/sisusbvga0 entry, despite having been rebooted without the dongle.  Perhaps the file gets saved as part of my Puppy Save File?

Maybe it would be better to grep lsmod for sisusbvga?  Or is there something in /sys that would give an indication?

You are probably right.
Try replacing line 9 of /etc/rc.d/rc.local from

Code:

if [ -e /dev/sisusbvga0 ]; then

to

Code:

if [ "`dmesg | grep sisusb`" != "" ] ; then

or

Code:

if [ "`lsmod | grep sisusbvga`" != "" ] ; then

[anthill]

Here's the X log!

I'll use the lsmod version?  I also changed line 69 (controlling the power saving)

[mavrothal]

Here's the X log!

I see. I think the issue is the /etc/X11/sisusb.conf file. It does not have configurations for keyboard and mouse
Try the attached one (remove the .txt from the name) and  see what the Xorg log says then (if it does not work)

I'll use the lsmod version?  I also changed line 69 (controlling the power saving)

wise

[anthill]

OK, victory!  Sort of.  I've switched from modelines to auto-filled modes, and used XRandR (even if the SisUSB driver doesn't support rotation)

The xorg video wizard lets me change resolutions on-the-fly, and things look good.

Only problem: by default, JWM starts with a virtual desktop of the full 1280x1024, with an 800x600 'porthole' I can scroll around in.  After the first resolution switch, everything behaves as expected.

Now, is there a way to quickly switch between USB dongle and built-in display? 

[mavrothal]

OK, victory!  Sort of.  I've switched from modelines to auto-filled modes, and used XRandR (even if the SisUSB driver doesn't support rotation)

Excellent!

The xorg video wizard lets me change resolutions on-the-fly, and things look good.

Only problem: by default, JWM starts with a virtual desktop of the full 1280x1024, with an 800x600 'porthole' I can scroll around in.  After the first resolution switch, everything behaves as expected.

Did you use the sisusb.conf I posted or you edited your own one? (Mine should default to 1024x786, which fits nice the XO screen)
Is the one you posted generated by xorgwizard?

Would be nice to make a pet that will fix that automatically, so let me know please and post one generated by xorgwizard if this one is not. Will be the current /etc/X11/xorg.conf when the dongle is working after you run the wizard.

Now, is there a way to quickly switch between USB dongle and built-in display?  

I think the best that can be done is to write a little script that will exit to prompt, modprobe the driver change the xorg conf and startx. Something similar to 'switch Openbox-JWM.
should be fast enough. I could write one but you do the testing  
Could go into the aforementioned pet at the end

Edit OK, here is a "sisusb_switch.sh" script. Copy/paste, make it executable and run it from the terminal to see how it goes.
If it works I can make a menu entry and add some icons.

Code:

#!/bin/sh

start_xo()
{
XOVER=`uname -r | cut -f 1 -d '-' | rev | cut -f 1 -d '_'| rev`
if [ "$XOVER" = "xo1.5" ] ; then
cp -a /etc/X11/xorg.conf.XO-1.5 /etc/X11/xorg.conf
else  
cp -a /etc/X11/xorg.conf.XO-1 /etc/X11/xorg.conf
fi
rm /var/run/powerd-inhibit-suspend/* &
chmod 755 /root/Startup/powerdfix
rmmod -f sisusbvga 2>/dev/null
restartwm &
}

start_sisusb()
{
modprobe sisusbvga
cp -a /etc/X11/sisusb.conf /etc/X11/xorg.conf
touch /var/run/powerd-inhibit-suspend/$$ &
chmod 000 /root/Startup/powerdfix
restartwm &
}

Xdialog  --buttons-style text --title "Sisusb-XO switch" --ok-label "XO" --cancel-label "External" --yesno \
"You are about to switch between the XO screen and an external motitor. \n Make sure that your sisusb adapter is connected. \nPlease save your work before switching. Any unsaved work will be lost  "  0 0
case $? in
0) start_xo & ;;
1) start_sisusb & ;;
255) exit ;;
esac

Later I went ahead and made a pet for the all these. However I have no idea if it works . For the brave ones here it is: sisusb.pet

[anthill]

Hi Mavrothal,

The sisusb-switch script works, with only two error messages:

Code:

Pango: Invalid UTF-8 String passed to Pango-Layout-Text
Line 8: Command not found

I'll look into a correct sisusb.conf file.  I generated mine by modifying the xorg.conf.XO-1 file.  If you're confident that xorgwizard generates the 'best' config files I will give that a try.

I would like to preserve XRandR since it is convenient to be able to switch resolutions on-the-fly when using a projector.

[anthill]

Well, it's close.  The xorg wizard crashes if I try to run it with the sisusb driver.  So instead I grafted together the standard Puppy template with some custom settings. It works fine.

Ideally, the X server would start in 1024x768, but with XRandR having detected all the modes up to 1280x1024.  This way, you would be sure of getting something displayed, but would have an easy way to switch to higher resolutions.

To force detection of higher modes, I've added the "Virtual 1280 1024" line in the "Display" section.  To force starting with a lower resolution, I've declared the "1024x768" mode.  However, the X server seems to interpret this as "use a scrolling viewport", which is clumsy and useless.

One option could be to give up in higher resolutions and just limit it to 1024x768 in xorg.conf.  Another option would be to run "xrandr -s 1024x768" on X startup.  I'm not sure how to go on this.

[mavrothal]

Hi Mavrothal,

The sisusb-switch script works, with only two error messages:

Code:

Pango: Invalid UTF-8 String passed to Pango-Layout-Text
Line 8: Command not found

I'll look into a correct sisusb.conf file.  I generated mine by modifying the xorg.conf.XO-1 file.  If you're confident that xorgwizard generates the 'best' config files I will give that a try.

I would like to preserve XRandR since it is convenient to be able to switch resolutions on-the-fly when using a projector.

The pango error is not critical I believe. Puppy has issues with UTF-8 in general...

Di you try the sisusb.pet that I posted (at the bottom of the script post)?
Did it give any problems? (what? Xorg.0.log?)

If you want you can "tar xzvf" it instead of installing it. Will generate a local folder with the files in it. You can modify them to a working stage (if not OK) and then run "dir2pet folder_name" to generate a pet  

[mavrothal]

A moth ago I made a pet that would put your applications in an autohiden applications tray. However, was a bit cumbersome (editing a text file) to make any changes to it.
Now there is a new pet  that includes a panel configuration application.
It can be installed over the previous one (and will preserve your changes) or independently.
Works nice with the new JWM 2.1.1  

[anthill]

Hi Mavrothal, sorry for the delay in testing the sisusb.pet file.  I have gotten back on my XO-1 and set up the programs I need (Firefox 11) from the ibiblio.org puppy lucid repository.  However, today I went to test the SIS USB package, and puppy package manager wouldn't start!

Code:

# ppm
find: paths must precede expression: Packages-puppy-3-official
Usage: find [-H] [-L] [-P] [-Olevel] [-D help|tree|search|stat|rates|opt|exec] [path...] [expression]

** ERROR **: gtkdialog: Error in line 72, near token '</vbox>': syntax error

aborting...

I don't think I messed with its database files...

Code:

# ls -al /root/.packages/
total 7963
drwxr-xr-x  3 root root    4096 2012-04-04 17:41 .
drwxr-xr-x 46 root root    4096 2012-04-05 13:06 ..
drwxr-xr-x  2 root root    7058 2011-07-31 02:46 builtin_files
-rw-r--r--  1 root root    1282 2010-09-02 13:02 DISTRO_COMPAT_REPOS
-rw-r--r--  1 root root    3523 2010-06-26 16:47 DISTRO_PET_REPOS
-rw-r--r--  1 root root   36993 2010-09-02 13:02 DISTRO_PKGS_SPECS
-rw-r--r--  1 root root    5994 2012-04-04 17:41 Firefox-11-Lucid-2.files
-rw-r--r--  1 root root   25217 2010-09-02 13:02 inline_get_compat
-rw-r--r--  1 root root   11720 2010-09-02 13:02 inline_get_pet
-rw-r--r--  1 root root      89 2012-03-07 09:11 jwm-2.1.1_2.files
-rw-r--r--  1 root root      26 2012-03-07 09:12 jwm_apps_panel-1.files
-rw-r--r--  1 root root   25980 2009-04-01 07:33 Packages-puppy-2-official
-rw-r--r--  1 root root   29048 2009-08-05 23:10 Packages-puppy-3-official
-rw-r--r--  1 root root   91572 2010-02-07 09:39 Packages-puppy-4-official
-rw-r--r--  1 root root   24727 2011-02-19 20:11 Packages-puppy-5-official
-rw-r--r--  1 root root   37700 2011-07-03 03:58 Packages-puppy-lucid-official
-rw-r--r--  1 root root   87176 2011-05-28 15:50 Packages-puppy-quirky-official
-rw-r--r--  1 root root  116731 2010-09-02 13:02 Packages-puppy-wary5-official
-rw-r--r--  1 root root   24994 2010-01-25 07:48 Packages-puppy-woof-official
-rw-r--r--  1 root root 1644926 2011-07-11 23:35 Packages-ubuntu-lucid-main
-rw-r--r--  1 root root  171885 2011-07-12 00:38 Packages-ubuntu-lucid-multiverse
-rw-r--r--  1 root root 5435600 2011-07-12 00:36 Packages-ubuntu-lucid-universe
-rw-r--r--  1 root root  122669 2010-06-30 19:31 PKGS_HOMEPAGES
-rw-r--r--  1 root root    8499 2012-04-04 17:27 PKGS_MANAGEMENT
-rw-r--r--  1 root root     376 2012-04-05 13:25 user-installed-packages
-rw-r--r--  1 root root  217090 2010-09-02 13:03 woof-installed-packages

Any ideas?

[mavrothal]

Hi Mavrothal, sorry for the delay in testing the sisusb.pet file.  I have gotten back on my XO-1 and set up the programs I need (Firefox 11) from the ibiblio.org puppy lucid repository.  However, today I went to test the SIS USB package, and puppy package manager wouldn't start!

Code:

# ppm
find: paths must precede expression: Packages-puppy-3-official
Usage: find [-H] [-L] [-P] [-Olevel] [-D help|tree|search|stat|rates|opt|exec] [path...] [expression]

** ERROR **: gtkdialog: Error in line 72, near token '</vbox>': syntax error

aborting...

I don't think I messed with its database files...

Any ideas?

You may have messed up with ppm though
This is going to get both back to their original state

Code:

cp -a --remove-destination /initrd/pup_ro2/root/.packages/* /root/.packages/
cp -a --remove-destination /initrd/pup_ro2/usr/local/petget/* /usr/local/petget/

I guess petget works since clicking on a pet installs it. Correct?

[anthill]

Thanks, Mavrothal, back in action.  I installed the sisusb.pet, and found most things work.  The one bug is that xrandr is disabled, since the sisusb xorg.conf file enables Xinerama (which is incompatible).

I used my xorg.conf and rebuilt the pet file using dir2pet.  It's attached, please have a look and see what you think.

It still falls short of my ultimate goal for the SiS USB dongle, but after a LOT of fiddling with xrandr, xorg.conf, and banging my head against the wall I've concluded that there's no tidy way to start up X at a low (projector-safe) resolution, while having xrandr populate higher resolution modes (e.g up to 720p).  Setting xorg.conf to read

Code:

SubSection "Display"
Depth 16
Modes "1024x768"
Virtual 1280 1024
EndSubSection

will populate all video modes up to 1280x1024, and persuade xrandr to have 1024x768 as the default mode, but the darn thing still starts X in a 'Scrolling Viewport' mode (a large 'virtual desktop' with a small porthole view), which is useless.  It's possible to use xrandr (or the xorg GUI) to change the resolution properly to 1024x768, but JWM's menus then behave badly - scrolling off-screen.

The slightly uglier way I've found is to add a line to the already messy /root/.xinitrc to run

Code:

xrandr -s 0

before launching the window manager.  This tells xrandr to set the screen to the default resolution.  This should does work even with the on-board 1200x900 video mode.  JWM then draws the menus to fit the default (smaller) resolution so they behave properly.

I'd really rather avoid messing with .xinitrc, but it seems to be the only way.  Scripts in Xsession.d seem to be ignored in this version of Puppy linux?

[anthill]

Ha, it seems that very little in JWM behaves properly when resolutions are switched 'on-the-fly' using xrandr.  Here's screenshots of how the JWM App Panel's auto-hide behaves when JWM is started at 1024x768, and then xrandr is used to expand it to 1280x1024.

The panel hovers in the bottom-middle of the screen (at the limit of the 'old' resolution), but on mouse-over it 'appears' at the bottom of the screen.  Thus, you can never actually click on it!  Ah well. 

[mavrothal]

Ha, it seems that very little in JWM behaves properly when resolutions are switched 'on-the-fly' using xrandr.

I just compiled the latest jwm from the repo that suposingly handles xrandr better. Give it a try. Works fine at my end but I have no sisusb adapter
The jwm-579 pet is HERE

Setting xorg.conf to read

Code:

SubSection "Display"
Depth 16
Modes "1024x768"
Virtual 1280 1024
EndSubSection

will populate all video modes up to 1280x1024, and persuade xrandr to have 1024x768 as the default mode, but the darn thing still starts X in a 'Scrolling Viewport' mode (a large 'virtual desktop' with a small porthole view), which is useless. 

Did you try "Virtual 1200 1200" ?
I remeber the XO-1 feaking out with higher virtual resolutions