Upup Precise 3.7.2 with kernel 3.7.2, no pae

For talk and support relating specifically to Puppy derivatives
Message
Author
User avatar
OscarTalks
Posts: 2196
Joined: Mon 06 Feb 2012, 00:58
Location: London, England

#31 Post by OscarTalks »

Hello again Pemasu,

Have downloaded the updated kernel sources and tried installing Nvidia 173.14.36 driver again and now getting:

Code: Select all

ERROR: Unable to determine the NVIDIA kernel module filename.
With this FX 5200 card and this Puppy unfortunately nv doesn't work, vesa doesn't work and nouveau doesn't display properly at all so none of the on-board xorg drivers are really suitable.

Remind me again what exactly nouveau.modeset=0 does. That sometimes works on initial boot but then if you try to change resolutions afterwards you can end up in a pickle.
Oscar in England
Image

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#32 Post by 01micko »

OscarTalks wrote:Hello again Pemasu,

Have downloaded the updated kernel sources and tried installing Nvidia 173.14.36 driver again and now getting:

Code: Select all

ERROR: Unable to determine the NVIDIA kernel module filename.
With this FX 5200 card and this Puppy unfortunately nv doesn't work, vesa doesn't work and nouveau doesn't display properly at all so none of the on-board xorg drivers are really suitable.

Remind me again what exactly nouveau.modeset=0 does. That sometimes works on initial boot but then if you try to change resolutions afterwards you can end up in a pickle.
In your case nouveau.modeset=0 is essential to get the nv driver working. What driver loads automaticaly? I suspect vesa if res is bad. Try xorgwizard and choosing nv. Vesa has gotten terrible with nvidia cards lately, only one that works for me is the slackbones version by Q5sys (64bit), and I have only 1 pc with nvidia capable of 64 bit.
Puppy Linux Blog - contact me for access

User avatar
OscarTalks
Posts: 2196
Joined: Mon 06 Feb 2012, 00:58
Location: London, England

#33 Post by OscarTalks »

Hello 01micko

With Precise it is nouveau that loads automatically with menus and graphics missing. None of the others work at all from xorgwizard, not even vesa. Is nouveau.modeset=0 (which gives me menus and graphics but seems to lock me into 1280 x 1024 resolution) forcing nv to work somehow or is this nouveau in a different mode, I am confused? I thought nv was just not working at all in Precise.

Things are pretty much the same on this machine with Slacko 5.4 by the way (I just tried it) except that I see the Nvidia 173.14.36 drivers are in the repo in PPM. I noticed that the names are different but the descriptions are the same for 4g and PAE, is this correct?

I thought that it might be helpful if this legacy driver could be in the Precise repo also because inexperienced users might be able to grab it from there much more easily than having to install it from the nvidia website
Oscar in England
Image

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#34 Post by 01micko »

The only way to get nv or vesa to load is with nouveau.modeset=0 or nomodeset parameter. They disable drm and KMS such that any KMS enabled kernel driver wont load, such as nouveau.ko (and radeon, intel in their specific cases).

Anyway, I've loaded this version up on my nvidia, have kernel source and devx so I'll see if 173 will play nice.

Oh, nearly forgot, report-video is still buggy:

# report-video
VIDEO REPORT: Upup Precise, version 3.7.2

Chip description:
oem: NVIDIA
product: G98 Board - 5610002u Chip Rev

Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1024x768x16
Depth (bits, or planes): 24
Modules requested to be loaded: dbe

Probing Xorg startup log file (/var/log/Xorg.0.log):
Loaded modules: dbe dri dri2 exa extmod fb glx kbd mouse record shadowfb

Actual rendering on monitor:
Resolution: 1366x768 pixels (361x203 millimeters)
Depth: 24 planes

...the above also recorded in /tmp/report-video


Nouveau nowhere to be seen, though I get good glxgears numbers..

EDIT:

Sorry OscarTalks but I get the same error as you. Nvidia haven't updated from 173.14.36 for at least 2 months, it's the same version that's in Slacko so probably isn't compatible with 3.7 series kernels. I did compile an alternate NV driver some time back, I think BK compiled his own, you are welcome to try it.. http://www.murga-linux.com/puppy/viewto ... 467#649467
Puppy Linux Blog - contact me for access

User avatar
James C
Posts: 6618
Joined: Thu 26 Mar 2009, 05:12
Location: Kentucky

#35 Post by James C »

Just as a test, I'm using the "nv" driver live pfix=ram on the old Athlon xp box.

# report-video
VIDEO REPORT: Upup Precise, version 3.7.2

Chip description:
oem: NVidia
product: NV18 () Board Chip Rev A2

Requested by /etc/X11/xorg.conf:
Depth (bits, or planes): 24
24
24
Modules requested to be loaded: dbe
Drivers requested to be loaded: nv fbdev vesa

Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nv
Loaded modules: dbe ddc dri dri2 extmod fb glx i2c int10 kbd mouse ramdac record vgahw xaa

Actual rendering on monitor:
Resolution: 1440x900 pixels (411x263 millimeters)
Depth: 24 planes

...the above also recorded in /tmp/report-video
# glxgears
89 frames in 5.0 seconds = 17.786 FPS
127 frames in 5.0 seconds = 25.306 FPS
138 frames in 5.0 seconds = 27.561 FPS
135 frames in 5.0 seconds = 26.846 FPS
136 frames in 5.0 seconds = 27.058 FPS
127 frames in 5.0 seconds = 25.279 FPS

Correct resolution......low,low results from "glxgears".

VGA compatible controller : NVIDIA Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1) (prog-if 00 [VGA controller])

Driver is working (confirmed in xorg.0.log) but think I'll stick with "nouveau".
Attachments
nv.png
(106.92 KiB) Downloaded 1242 times

User avatar
RoDoN
Posts: 10
Joined: Fri 09 Sep 2011, 10:34
Location: Russia

gma500

#36 Post by RoDoN »

pemasu wrote:I decided to try to create a pet of the needed xorg graphics libs. It makes easier to test the intel cedarview gma graphics.
Link to the pet: http://www.smokey01.com/pemasu/pet_pack ... -0.0.1.pet
Resolution only 640x480 on Acer Aspire One AO751h-52Br :(

Install xf86-video-modesetting-0.6.0-i486_upup.pet, restart X, resolution 1366x768 :)
Image

P.S. For normal work gma500_gfx + modesettting_drv driver poulsbo.ко need to delete or rename to the poulsbo.ko.not
Attachments
xf86-video-modesetting-0.6.0-i486_upup.pet
modesetting-0.6.0
(15.06 KiB) Downloaded 461 times
Last edited by RoDoN on Tue 15 Jan 2013, 06:07, edited 2 times in total.

User avatar
charlie6
Posts: 1230
Joined: Mon 30 Jun 2008, 04:03
Location: Saint-Gérard / Walloon part of Belgium

#37 Post by charlie6 »

Hi pemasu,
pemasu wrote:Charlie6. I wonder what I have uploaded. The firefox-18 which was meant to be there didnt have pinstall.sh script at all. Only puninstall.sh
:oops: ooops !... sorry ... i should "update" my glasses
charlie 8)

User avatar
charlie6
Posts: 1230
Joined: Mon 30 Jun 2008, 04:03
Location: Saint-Gérard / Walloon part of Belgium

wacom tablet driver

#38 Post by charlie6 »

Hi,
compiled xf86-input_k.3.7.2-upup-wacom-0.17.0.pet Xorg wacom driver for kernel k3.7.2.
Download here:
http://www.murga-linux.com/puppy/viewto ... 611#677611
please test and report
Charlie

User avatar
Keef
Posts: 987
Joined: Thu 20 Dec 2007, 22:12
Location: Staffordshire

#39 Post by Keef »

Runs very well on my Armada M700 850mhz laptop - better than expected.
Tried it as I was after something to use with my Wacom Bamboo tablet without too much fiddling. It works straight away with this Upup, and just needed a couple of amendments to Xorg.conf to get pressure sensitivity working. Now if MyPaint worked as well, that would be wonderful.

As with all recent pups, it takes forever to probe for drives when setting up save file on first shutdown.

User avatar
charlie6
Posts: 1230
Joined: Mon 30 Jun 2008, 04:03
Location: Saint-Gérard / Walloon part of Belgium

#40 Post by charlie6 »

Hi Keef, :shock:
use with my Wacom Bamboo tablet without too much fiddling. It works straight away with this Upup, and just needed a couple of amendments to Xorg.conf to get pressure sensitivity working
hmm! ... very interesting ....would you mind posting a copy of your /etc/X11/xorg.conf file ... and tell if you have installed some wacom Xorg driver ?
thanks in advance
Charlie

anikin
Posts: 994
Joined: Thu 10 May 2012, 06:16

#41 Post by anikin »

Hi pemasu,

a couple quick questions, if you don't mind. The first one is about font rendering in upupPrecise vs dpupExprimo. In Precise fonts render a bit differently. I'm not saying better or worse, so please don't get me wrong here. What I'm seeing in Exprimo is that fonts seem to be more 'tangible', with more meat on their stems. In Precise they are slightly thinner and slimmer. BCI thing applied in one and missing in the other build?

And one more, about powersave mode and running cool

Code: Select all

#!/bin/bash
killall acpid
 if [ -f /root/.acpid_on ] ; then 
 exec acpid &
 acpitool -a |grep off-line
  if [[ $? == 0 ]] ; then
  /etc/acpi/powersave.sh
  else
  /etc/acpi/performance.sh
  fi
	exec ppower &
 fi
/etc/acpi/powersave.sh
is this the right way to always boot into powersave mode? It seems to work fine both here and in Exprimo builds, but I'm uncertain about the last line (goes beyond fi). The trick was suggested by elroy in the Saluki thread.

Thank you in advance

User avatar
pemasu
Posts: 5474
Joined: Wed 08 Jul 2009, 12:26
Location: Finland

#42 Post by pemasu »

RoDon. Thanks. From where did you get that 0.6.0 version modesetting driver. I managed to find only 0.5.0 version. Did you compile it yourself.
Could you post also your comp specs where you used that modesetting driver succesfully. And did you need that my attempted pet at all.

Yeah. I am quite newbie with this graphics problem.

Anikin. Just copy content of /etc/fonts from dpup exprimo over precise existing ones. You get dpup exprimo experience. As you said, there isnt right and wrong about font hinting and other lookout features.

About /root/Startup/0acpid script.
You get powersave.sh with that setup when you boot or restart X. If it is what you want, then it is fine. Simpler way would be:

Code: Select all

#!/bin/bash
killall acpid
 if [ -f /root/.acpid_on ] ; then
 exec acpid &
 acpitool -a |grep off-line
  if [[ $? == 0 ]] ; then
  /etc/acpi/powersave.sh
  else
  /etc/acpi/performance.sh
  fi
   exec ppower &
 fi
This is default 0acpid code in Upup Precise. Just change /etc/acpi/powersave.sh and /etc/acpi/performance.sh both as powersave.sh and you get powersave ie crippled cpu perfomance all the time for battery saving and cooling needs. If you want top cpu speed all the time, just change the rows as /etc/acpi/turbo.sh in both locations....and if you want ondemand behavior, change the rows as /etc/acpi/performance.sh in both locations....or create whole new behavior with mixing those above settings. Simple isnt it. It is question of what you want. Powersave, ondemand or top speed all the time or different behavior when on battery and on ac/dc. There isnt again the one right answer. What is good for me, can be disaster to someone else.

User avatar
RoDoN
Posts: 10
Joined: Fri 09 Sep 2011, 10:34
Location: Russia

#43 Post by RoDoN »

pemasu wrote:RoDon. Thanks. From where did you get that 0.6.0 version modesetting driver. I managed to find only 0.5.0 version. Did you compile it yourself.
http://cgit.freedesktop.org/xorg/driver ... odesetting

http://cgit.freedesktop.org/xorg/driver ... 6.0.tar.gz
Acer Aspire One AO751h-52Br (Atom Z520 1.33GHz, 2 Gb, Intel GMA500 1366x768)
WinXP Home, LupuRus-Bit (JWM), PuppyRus 2.1x, [url=http://rodon.tk/news/lupurus-520-r1-kill-bill-.html]LuPuRus 5.2.0 R1 KB[/url]
[url=http://docs.rodon.tk/doku.php]Wiki[/url]

User avatar
pemasu
Posts: 5474
Joined: Wed 08 Jul 2009, 12:26
Location: Finland

#44 Post by pemasu »

RoDon. Thanks again. I test compiled it and it compiled fine. But there is no need to upload my product since you have done the whole work yourself. Thank you.

Okay...you have Acer Aspire One AO751h-52Br and it has intel gma500.
I try to get experience what works and what not.

User avatar
Keef
Posts: 987
Joined: Thu 20 Dec 2007, 22:12
Location: Staffordshire

Wacom Bamboo tablet

#45 Post by Keef »

charlie6

I tried this again from scratch, just to make sure.
With the tablet already plugged, it is active from first boot, and will do the job of a mouse. Did not need to load any drivers.
MTpaint and GIMP do not recognise it as an input device (other than a mouse), so although I could draw, there was no way to use pressure sensitivity.
Just amended etc/X11/Xorg.conf with info I got from the Wacom HOWTO thread:

Code: Select all

Section "ServerLayout" 
   Identifier     "X.org Configured" 
   Screen      0  "Screen0" 0 0 
   InputDevice    "Mouse0" "CorePointer" 
   InputDevice    "Keyboard0" "CoreKeyboard" 
#from kernel 2.6.35 and later the "SendCoreEvents" after InputDevice is no longer required 
   InputDevice    "stylus"  # <<< INSERTED THIS LINE
    EndSection 
and added this section:

Code: Select all

Section "InputDevice" 
      Identifier    "stylus" 
      Driver        "wacom" 
      Option        "Device" "/dev/input/wacom" 
      Option        "Type" "stylus" 
     Option        "USB" "on" 
     Option        "Mode" "Absolute" 
EndSection 
After that the paint programmes listed "stylus" as an input device, so I could enable it and pressure worked.

To be specific, my tablet is a CTL-470K-EN, which is pen only, no touch, and does not have an eraser, so added 'stylus' only.

User avatar
charlie6
Posts: 1230
Joined: Mon 30 Jun 2008, 04:03
Location: Saint-Gérard / Walloon part of Belgium

#46 Post by charlie6 »

Hi Keef,
thanks a lot for your post !
i surely have learned something !
would you mind:
1) add:
1.1)

Code: Select all

Section "ServerLayout"
   Identifier     "X.org Configured"
   Screen      0  "Screen0" 0 0
   InputDevice    "Mouse0" "CorePointer"
   InputDevice    "Keyboard0" "CoreKeyboard"
#from kernel 2.6.35 and later the "SendCoreEvents" after InputDevice is no longer required
   InputDevice    "stylus"
   InputDevice    "eraser"  # <<< please do INSERT THIS LINE
EndSection
and modify
1.2)

Code: Select all

Section "InputDevice"
      Identifier    "stylus"
      Driver        "wacom"
      Option        "Device" "/dev/input/wacom"
      Option        "Type" "stylus"
      Option        "USB" "on"
      Option        "Mode" "Relative"
#      Option        "Mode" "Absolute"
EndSection
and add this to get the eraser (i.e. the pens tail tip end...) working:
1.3)

Code: Select all

Section "InputDevice"
      Identifier    "eraser"
      Driver        "wacom"
      Option        "Device" "/dev/input/wacom"
      Option        "Type" "eraser"
      Option        "USB" "on"
      Option        "Mode" "Relative"
#     Option        "Mode" "Absolute"
EndSection 
some cursors arrows behaviour might change ...maybe better ! if not, please disregard.

charlie

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#47 Post by 01micko »

Just an FYI post...

Regarding the "modesetting" Xorg driver.

In my Slacko tests I did find that this can conflict with some other xorg drivers. It is included in Slacko but it is hidden away in /usr/lib/x with possibly other alternate drivers. There is a problem (bug) with that approach though as xorgwizard does not know about the modesetting driver. Consequently, it is not moved to /usr/lib/xorg/modules/drivers and so is unavailable to xorg.

I am going to add a case to xorgwizard that handles this scenario such modesetting is moved if chosen. Possibly udev rules should be written that on the detection of a cedaview or poulsbo graphics card that the modesetting driver is automatically moved. Jury is out on that one. I am already doing preliminary work on this.


pemasu, sorry for brief off topic here...

@ aarf, who unfortunately can't post here. Good you got modesetting to work in Upup with RoDoN's compile. Regarding Slacko, you must uninstall the Upup version. Then run this command

Code: Select all

mv /usr/lib/x/drivers-alternate/modesetting_drv.so /usr/lib/xorg/modules/drivers/
Then run xorgwizard, choose modesetting driver, that should work. Modesetting is known working with cedarview in Slacko.
Puppy Linux Blog - contact me for access

User avatar
pemasu
Posts: 5474
Joined: Wed 08 Jul 2009, 12:26
Location: Finland

#48 Post by pemasu »

01micko. Thank you of the input. Intel gma 500 (Poulsbo), gma 600, gma 3600 (Cedarview) and 3650 (Cedarview) which uses gma500_gfx.ko and can use xorg modesetting driver have been troublesome PowerVR based graphics.

The graphics support in linux is only usable. No 3D acceleration. But it is better than nothing and intel atom based notebooks are not for power hungry usage anyway.

If you can edit xorgwizard so that gma500_gfx.ko can be used with included xorg modesetting driver, it would be great thing for these intel atom comps with above gma graphics.
Xorgwizard handled xorg driver translocation from alternate to normal location so that the xorg modesetting driver would be in use would be great.

I would include that xorgwizard of course to my builds. Thanks of your initiative. And thanks to aarf who brought this need to my attention. I didnt know of the work done in Slacko. Now I know.

Cheers.

User avatar
pemasu
Posts: 5474
Joined: Wed 08 Jul 2009, 12:26
Location: Finland

#49 Post by pemasu »

I am still quite newbie for compiling ati-amd-fglrx-drivers for petting. But...I have learnt to compile and create them inside extracted ati folder and have learnt to patch the kernel module source before running the installer. So....these might even work.
I created ati-12.10 pet for modern graphics, like mine. Tested the pet with my dual graphics. And then I created ati-12.6-legacy pet.

Cave out. For me suspending does not result working waking up.
There is ati own fixes for that inside: /usr/share/doc/fglrx/examples/etc
You can try to copy the stuff to right places and test them. I havent had time to do so....maybe next time when I boot with ati and watch movies through hdmi from my 42 inch lcd tv. Then I have a reason to try them with suspending.

I created quickpet for this 3.7.2 kernel version. Under drivers sections you find those ati-amd-fglrx pets and also newest nvidia 310.19 pet.

They are in upup repo, so those who want to scan it...find them there. Nvidia 310.19 is there as sfs also. You can download it with Precise sfs downloader also...There are now quite many ways to install stuff...

Test...enjoy...or blame me...
Attachments
quickpet_upup-precise-kernel-3.7.2-0.2.pet
(104 KiB) Downloaded 423 times

User avatar
01micko
Posts: 8741
Joined: Sat 11 Oct 2008, 13:39
Location: qld
Contact:

#50 Post by 01micko »

Further to gma/poulsbo/cedarview issues I have patched xorgwizard to move the modesetting driver from the alternate location to the real location where Xorg can find it, I have also patched xorgwizard-automatic to move the modesetting driver if it detects one of these cards based on device ID, now my database may be incomplete, I don't know. But if your machine is over 6 months old it will almost certainly be listed. Newer ones might be too.

I have not packaged this as a pet as it is only if you have an intel atom infected with the gma 500 (Poulsbo), gma 600, gma 3600 (Cedarview) and 3650 (Cedarview) which uses gma500_gfx.ko.
The package is structured just like a pet to easily merge into the filesystem. The packages contains: a patched /usr/sbin/xorgwizard, a patched /usr/sbin/xorgwizard-automatic and a new script called xcedarview.sh, called from xorgwizard-automatic.

Get the package here:
http://01micko.no-ip.org/testing/xorgwi ... 15.tar.bz2 25.1kb

If you know what you are doing you can do it with no X. Ideally that's how it should be done, but for testing purposes there are 2 things to test.
  • 1.drop to prompt (yau may already be there :P ) and run xorgwizard
    Choose the "modesetting" driver, start x with xwin

    2. From the prompt delete or move /etc/X11/xorg.conf
    If you have ordinary Intel a test will be performed to see if you have a gma device and you will be informed. If you have the device you will then be informed that "modesetting" driver is moved to it's proper location or if it's not there then a "NOT FOUND" message occurs. .
NOTE: you'll also need the modesetting driver in the correct location for the test!! Here it is:
http://01micko.no-ip.org/testing/xf86-v ... T_upup.pet

This is RoDoN's pet just moved. Why is this necessary? Well .. if you have an nvidia and use xorgwizard then it's "modesetting" gets chosen and X crashes unrecoverably! That's why I moved in the first place.

Good Luck!
Puppy Linux Blog - contact me for access

Post Reply