Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Thu 31 Jul 2014, 20:13
All times are UTC - 4
 Forum index » Advanced Topics » Hardware » Video
Lost screen resolution after updating Slacko to 5.4-4g SCSI
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 2 [17 Posts]   Goto page: 1, 2 Next
Author Message
sharo

Joined: 06 Dec 2012
Posts: 5

PostPosted: Thu 06 Dec 2012, 11:55    Post subject:  Lost screen resolution after updating Slacko to 5.4-4g SCSI
Subject description: Intel GMA500 (Poulsbo) 1366x768 Acer Aspire One-751h (or AO751h)
 

Puppy is a GREAT Job!

I have: Laptop: Acer Aspire One-751h (or AO751h)
Video Driver: Intel GMA500 (Poulsbo) 1366x768 screen resolution

slacko-5.3.3-4g-SCSI is giving me option to load the right Intel driver and I have 1366x768 screen resolution,
but with slacko-5.4-4g-SCSI it is not possible.

I tried to use "slackosave_1366x768.4fs" from slacko-5.3.3-4g-SCSI to upgaded to slacko-5.4-4g-SCSI
but I did not get screen resolution 1366x768.
If someone have the solution...
Thank you.
Back to top
View user's profile Send private message 
Terryphi


Joined: 02 Jul 2008
Posts: 759
Location: West Wales, Britain.

PostPosted: Thu 06 Dec 2012, 12:11    Post subject:  

You could try copying the working xorg.conf from your previous version of Slacko 5.3.3 and then restart X server. This method usually solves resolution problems for me but it sometimes takes a reboot to get the required resolution to stick.

If you have created a new savefile for Slacko 5.4 back it up before you try this.

_________________
Classic Opera 12.16 browser SFS package for Precise, Slacko, Racy, Wary, Lucid, Quirky, etc available here Smile
Back to top
View user's profile Send private message Visit poster's website 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Thu 06 Dec 2012, 20:14    Post subject:  

sharo wrote:
slacko-5.3.3-4g-SCSI is giving me option to load the right Intel driver and I have 1366x768 screen resolution,
but with slacko-5.4-4g-SCSI it is not possible.

That's because Slacko 5.3.3 (PAE and 4G) include the necessary DRM kernel module for Poulsbo graphics; psb_gfx
But in the updated kernel of Slacko 5.4 this driver has been revised - it's now called gma500_gfx
and the developer (01micko) didn't include it.


sharo wrote:
I tryed to use "slackosave_1366x768.4fs" from slacko-5.3.3-4g-SCSI to upgaded to slacko-5.4-4g-SCSI

I suggest you don't use old savefiles when upgrading. This has been known to create a myriad of problems.

EDIT: gma500_gfx-k3.4.17PAE.pet attachment removed, until someone reports whether or not it works.
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 7785
Location: qld

PostPosted: Fri 14 Dec 2012, 20:12    Post subject:  

If you use kernel 3.2.33-4g (for 3.4.17-PAE see down the page) then you should be ok as the the driver is in staging known as psb_gfx. However, it is documented on arch wiki that the intel driver does not work with this chip. Arch recommend the modesetting xorg driver which is included in slacko but in the alternate location as it can conflict with intel,radeon and nouveau. You can run xorgwizard and choose that driver. Please report results.

From Kconfig k3.2.33 wrote:
config DRM_PSB
tristate "Intel GMA5/600 KMS Framebuffer"
depends on DRM && PCI && X86
select FB_CFB_COPYAREA
select FB_CFB_FILLRECT
select FB_CFB_IMAGEBLIT
select DRM_KMS_HELPER
select DRM_TTM
help
Say yes for an experimental 2D KMS framebuffer driver for the
Intel GMA500 ('Poulsbo') and other Intel IMG based graphics
devices.

config DRM_PSB_MRST
bool "Intel GMA600 support (Experimental)"
depends on DRM_PSB
help
Say yes to include support for GMA600 (Intel Moorestown/Oaktrail)
platforms with LVDS ports. HDMI and MIPI are not currently
supported.

config DRM_PSB_MFLD
bool "Intel Medfield support (Experimental)"
depends on DRM_PSB
help
Say yes to include support for Intel Medfield platforms with MIPI
interfaces.

config DRM_PSB_CDV
bool "Intel Cedarview support (Experimental)"
depends on DRM_PSB
help
Say yes to include support for Intel Cedarview platforms
and
.config for slacko wrote:
CONFIG_DRM_PSB=m
CONFIG_DRM_PSB_MRST=y
CONFIG_DRM_PSB_MFLD=y
CONFIG_DRM_PSB_CDV=y

This produces the psb_gfx module which has support for gma500, 600, Medfield and Cedarview.



-------------

Thanks tempestuous for pointing out my error in k3.4.17. I'll compile the gma500_gfx and post soon. There is a reported conflict with poulsbo.ko stub driver, it may need to be blacklisted or removed, more soon. Reference.

-----------------------

LATER (ONLY for 3.4.17-PAE)

http://www.smokey01.com/01micko/pet_packages-slacko14/gma500_gfx-3.4.17-PAE-slacko14.pet 45k

That is the package including an informative pinstall.sh which renames the poulsbo stub driver and installs gma500_gfx. Hopefully a reboot and xorgwizard run (choosing modesetting driver) will be enough to fix most issues. It's all explained in the pinstall.sh.

If you do not have X running and need to install it the run this, assuming the file is downloaded to /root
Code:
/usr/local/petget/installpkg.sh gma500_gfx-3.4.17-PAE-slacko14.pet


If you need to download without X
Code:
wget http://www.smokey01.com/01micko/pet_packages-slacko14/gma500_gfx-3.4.17-PAE-slacko14.pet
will download to /root

If you can't get net and need wireless with no X try
Code:
/usr/sbin/pns-tool


Please report any success or failure


Edit: fixed typo in command

_________________
Woof Mailing List | keep the faith Cool |

Last edited by 01micko on Fri 14 Dec 2012, 22:06; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website 
sharo

Joined: 06 Dec 2012
Posts: 5

PostPosted: Fri 14 Dec 2012, 21:56    Post subject:  

Terryphi wrote:
You could try copying the working xorg.conf from your previous version of Slacko 5.3.3 and then restart X server. This method usually solves resolution problems for me but it sometimes takes a reboot to get the required resolution to stick.

If you have created a new savefile for Slacko 5.4 back it up before you try this.

I already try this, does not work.
Back to top
View user's profile Send private message 
sharo

Joined: 06 Dec 2012
Posts: 5

PostPosted: Fri 14 Dec 2012, 22:07    Post subject:  

01micko wrote:
If you use kernel 3.2.33-4g (for 3.4.17-PAE see down the page) then you should be ok as the the driver is in staging known as psb_gfx. However, it is documented on arch wiki that the intel driver does not work with this chip. Arch recommend the modesetting xorg driver which is included in slacko but in the alternate location as it can conflict with intel,radeon and nouveau. You can run xorgwizard and choose that driver. Please report results.

From Kconfig k3.2.33 wrote:
config DRM_PSB
tristate "Intel GMA5/600 KMS Framebuffer"
depends on DRM && PCI && X86
select FB_CFB_COPYAREA
select FB_CFB_FILLRECT
select FB_CFB_IMAGEBLIT
select DRM_KMS_HELPER
select DRM_TTM
help
Say yes for an experimental 2D KMS framebuffer driver for the
Intel GMA500 ('Poulsbo') and other Intel IMG based graphics
devices.

config DRM_PSB_MRST
bool "Intel GMA600 support (Experimental)"
depends on DRM_PSB
help
Say yes to include support for GMA600 (Intel Moorestown/Oaktrail)
platforms with LVDS ports. HDMI and MIPI are not currently
supported.

config DRM_PSB_MFLD
bool "Intel Medfield support (Experimental)"
depends on DRM_PSB
help
Say yes to include support for Intel Medfield platforms with MIPI
interfaces.

config DRM_PSB_CDV
bool "Intel Cedarview support (Experimental)"
depends on DRM_PSB
help
Say yes to include support for Intel Cedarview platforms
and
.config for slacko wrote:
CONFIG_DRM_PSB=m
CONFIG_DRM_PSB_MRST=y
CONFIG_DRM_PSB_MFLD=y
CONFIG_DRM_PSB_CDV=y

This produces the psb_gfx module which has support for gma500, 600, Medfield and Cedarview.



-------------

Thanks tempestuous for pointing out my error in k3.4.17. I'll compile the gma500_gfx and post soon. There is a reported conflict with poulsbo.ko stub driver, it may need to be blacklisted or removed, more soon. Reference.

-----------------------

LATER (ONLY for 3.4.17-PAE)

http://www.smokey01.com/01micko/pet_packages-slacko14/gma500_gfx-3.4.17-PAE-slacko14.pet 45k

That is the package including an informative pinstall.sh which renames the poulsbo stub driver and installs gma500_gfx. Hopefully a reboot and xorgwizard run (choosing modesetting driver) will be enough to fix most issues. It's all explained in the pinstall.sh.

If you do not have X running and need to install it the run this, assuming the file is downloaded to /root
Code:
/usr/local/petget/usr/local/petget/installpkg.sh gma500_gfx-3.4.17-PAE-slacko14.pet


If you need to download without X
Code:
wget http://www.smokey01.com/01micko/pet_packages-slacko14/gma500_gfx-3.4.17-PAE-slacko14.pet
will download to /root

If you can't get net and need wireless with no X try
Code:
/usr/sbin/pns-tool


Please report any success or failure

Thank you for your respond.
It's a little complicated for me but I'll do my best.
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 7785
Location: qld

PostPosted: Fri 14 Dec 2012, 22:10    Post subject:  

sharo

Only the first paragraph should apply to you if you use slacko-5.4-4g. Try the mentioned "modesetting" driver from the xorgwizard.

_________________
Woof Mailing List | keep the faith Cool |
Back to top
View user's profile Send private message Visit poster's website 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Sat 15 Dec 2012, 01:01    Post subject:  

Mick, well done. I had already compiled the gma500_gfx driver for Slacko 5.4PAE, and forum member JustGreg is currently testing it - we had assumed it would work with the "intel" Xorg driver, so your information about the "modesetting" driver may certainly be the critical piece of the puzzle.

It's worth mentioning that even if we get Cedarview graphics working in this manner, this is a very basic 2D Xorg driver solution, with no hardware acceleration whatsoever.
In MPlayer, for example, you will not be able to use the all-important "xv" video output method, but only the basic "x11" video output method, which means that the main (Atom) CPU will be doing all video decoding and colorspace conversion. Effectively this means you will have lousy video playback performance, which will be most noticeable on high-resolution movie files, and even medium-resolution Flash video, such as on Youtube.

If any GMA3600 (Cedarview) owners out there want to try the full 3D "PowerVR" Xorg driver, which was recently released by Intel, I have successfully compiled this for Slacko 5.3.3PAE.
Unfortunately the compilation failed for Slacko 5.4.
Back to top
View user's profile Send private message 
JustGreg

Joined: 24 May 2005
Posts: 666
Location: Connecticut USA

PostPosted: Sun 16 Dec 2012, 20:43    Post subject:
Subject description: Some Sucess but not a fix
 

01Micko, I tried your pet for Slacko 5.4PAE on my ASUS EeePC 1201HAB. With normal Slacko 5.4PAE, the X server does not start and console mode is presented.

I did test your pet and one from Tempestuous. I found that xorgwizard does not handle the modesetting driver well. I installed your pet using the console. Your instructions were good. The pet installed correctly. However, the X server would still not start. The xorgwizard produced an xorg.conf that did not have the video sections' information.

I did get the x server to start and show the desktop, but, the mouse cursor is a strange 48 by 48 pixel block (the upper left corner does all selecting objects). I tried using xsetroot -cursor_name command to change it, but no luck. The xsetroot -cursor_name command works on my desktop system (intel atom with nvidia video) to change the cursor.

To get the EeePC to display the desktop, I had to first move the modesetting_drv.so from /usr/lib/x/drivers_alternate to /usr/lib/xorg/modules/drivers. This maybe the reason that xorgwizard was not finding the mode setting driver.

I had to manually edit the xorg.conf to the following:

#barry Kauler 2011
#pre-constructed xorg.conf, for use by /usr/sbin/xorgwizard-automatic
#110627 working on mageia1 build, this needs fixing.
#111029 Terryphi reported 1cm screen displacement, changed vert freq range from 56-76 to 59-76.

# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
Load "synaptics" #loadsynaptics

# This loads the DBE extension module.

Load "dbe" # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

# This loads the font modules
# Load "type1"
# Load "freetype"

# This loads xtrap extension, used by xrandr
# Load "xtrap"

# This loads the GLX module (if present). xorg 7.4/5, need explicit disable to disable... change "Disable" to "Load" if reqd...
Disable "glx" #LOADGLX

# This loads dri module (if present). 7.4 loads it by default, have to disable... change "Disable" to "Load" if reqd...
# Disable "dri" #LOADDRI

EndSection

# **********************************************************************
# Files section. This allows default font paths to be set
# **********************************************************************

Section "Files"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)

#FontPath "/usr/share/fonts/X11/misc/"
#FontPath "/usr/share/fonts/liberation/"
FontPath "/usr/share/X11/fonts/misc/"
FontPath "/usr/share/X11/fonts/Type1/"
FontPath "/usr/share/X11/fonts/TTF/"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.

# Option "DontVTSwitch"

# Enables mode switching with xrandr
# There is a report that this can cause Xorg not to work on some
# video hardware, so default is commented-out...
# but i want to use it in xorgwizard so leave on...

Option "RandR" "on"

# With this, Xorg won't talk to HAL to add evdev devices and you'll be back
# with the old Xorg behavior (pre-7.4)...

Option "AutoAddDevices" "false"

# For no-Hal, kirk also suggests this...

# Option "AllowMouseOpenFail" "true"

# Xorg 7.4, Ubuntu Jaunty, CTRL-ALT-BACKSPACE is disabled by default...

Option "DontZap" "false"

EndSection

Section "ServerLayout"
InputDevice "Synaptics Mouse" "AlwaysCore" #serverlayoutsynaptics
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "us" #xkeymap0
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2" #mouse0protocol
Option "Device" "/dev/mouse"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
Option "ZAxisMapping" "4 5" #scrollwheel
EndSection

Section "InputDevice"
Identifier "Synaptics Mouse"
Driver "synaptics"
Option "SHMConfig" "on"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 35-81
VertRefresh 59-76
#UseModes "Modes0" #monitor0usemodes
Option "PreferredMode" "1366x768" #monitor0prefmode
EndSection

Section "Modes"
Identifier "Modes0"
#modes0modeline0
EndSection

#110627 remove...
##server can find BusID automatically, comment out...
Section "Device"
Identifier "Card0"
Driver "modesetting" #card0driver
VendorName "Unknown Vendor"
BoardName "Unknown Board"
## BusID "PCI:0:2:0" #card0busid
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
#Option "metamodes" "1280x800_60 +0+0" #METAMODES_0
Subsection "Display"
Depth 24
Modes "1366x768" #screen0modes
EndSubsection
EndSection
#PuppyHardwareProfile=Intel_r_Poulsbo_Graphics_ChipHSD121PHW1 modified by
#JustGreg 15 Dec. 2012

I added the section (normally commented out) for device card0 and specified the driver as modesetting. This does work but with a very strange mouse cursor. I hope this helps. Any ideas on how to fix the cursor? I will test them out.

_________________
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Mon 17 Dec 2012, 06:59    Post subject:  

JustGreg wrote:
the mouse cursor is a strange 48 by 48 pixel block

It sounds like the the modesetting Xorg driver may not properly support a hardware cursor.
Try modifying your xorg.conf; in Section "Device" add this line -
Code:
Option "SWCursor" "on"

Save. Restart X.
Back to top
View user's profile Send private message 
JustGreg

Joined: 24 May 2005
Posts: 666
Location: Connecticut USA

PostPosted: Mon 17 Dec 2012, 19:56    Post subject:
Subject description: It worked
 

Adding the Option line for "SWCursor" solved the problem. Here is the xorg.conf file that works below:

#barry Kauler 2011
#pre-constructed xorg.conf, for use by /usr/sbin/xorgwizard-automatic
#110627 working on mageia1 build, this needs fixing.
#111029 Terryphi reported 1cm screen displacement, changed vert freq range from 56-76 to 59-76.

# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
Load "synaptics" #loadsynaptics

# This loads the DBE extension module.

Load "dbe" # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

# This loads the font modules
# Load "type1"
# Load "freetype"

# This loads xtrap extension, used by xrandr
# Load "xtrap"

# This loads the GLX module (if present). xorg 7.4/5, need explicit disable to disable... change "Disable" to "Load" if reqd...
Disable "glx" #LOADGLX

# This loads dri module (if present). 7.4 loads it by default, have to disable... change "Disable" to "Load" if reqd...
# Disable "dri" #LOADDRI

EndSection

# **********************************************************************
# Files section. This allows default font paths to be set
# **********************************************************************

Section "Files"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)

#FontPath "/usr/share/fonts/X11/misc/"
#FontPath "/usr/share/fonts/liberation/"
FontPath "/usr/share/X11/fonts/misc/"
FontPath "/usr/share/X11/fonts/Type1/"
FontPath "/usr/share/X11/fonts/TTF/"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.

# Option "DontVTSwitch"

# Enables mode switching with xrandr
# There is a report that this can cause Xorg not to work on some
# video hardware, so default is commented-out...
# but i want to use it in xorgwizard so leave on...

Option "RandR" "on"

# With this, Xorg won't talk to HAL to add evdev devices and you'll be back
# with the old Xorg behavior (pre-7.4)...

Option "AutoAddDevices" "false"

# For no-Hal, kirk also suggests this...

# Option "AllowMouseOpenFail" "true"

# Xorg 7.4, Ubuntu Jaunty, CTRL-ALT-BACKSPACE is disabled by default...

Option "DontZap" "false"

EndSection

Section "ServerLayout"
InputDevice "Synaptics Mouse" "AlwaysCore" #serverlayoutsynaptics
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "us" #xkeymap0
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2" #mouse0protocol
Option "Device" "/dev/mouse"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
Option "ZAxisMapping" "4 5" #scrollwheel
EndSection

Section "InputDevice"
Identifier "Synaptics Mouse"
Driver "synaptics"
Option "SHMConfig" "on"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 35-81
VertRefresh 59-76
#UseModes "Modes0" #monitor0usemodes
Option "PreferredMode" "1366x768" #monitor0prefmode
EndSection

Section "Modes"
Identifier "Modes0"
#modes0modeline0
EndSection

#110627 remove...
##server can find BusID automatically, comment out...
Section "Device"
Identifier "Card0"
Driver "modesetting" #card0driver
Option "SWCursor" "ON"
VendorName "Unknown Vendor"
BoardName "Unknown Board"
## BusID "PCI:0:2:0" #card0busid
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
#Option "metamodes" "1280x800_60 +0+0" #METAMODES_0
Subsection "Display"
Depth 24
Modes "1366x768" #screen0modes
EndSubsection
EndSection
#PuppyHardwareProfile=Intel_r_Poulsbo_Graphics_ChipHSD121PHW1
#modified by JustGreg 17 Dec. 2012

I found a good page here https://wiki.archlinux.org/index.php/Poulsbo that provide a good discussion of what is going on and the differences between the drivers. The page also provides additional information on how to use the driver. This driver is supposed to provide limited video performance. I did visit www.youtube.com to try some videos. They all display OK. In general, the driver performance well in my opinion. Hopefully, the next update of Slacko will have this sorted out.

Thank to all!

_________________
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Tue 18 Dec 2012, 05:07    Post subject:  

OK, that's great.
For anyone who missed what's going on here, this means we now have a working solution for Atom Cedarview graphics displays, under Slacko 5.4PAE.
There are just a few configuration bugs to be worked out, particularly the part about enabling the modesetting Xorg driver.
I will update this information when I can.


JustGreg wrote:
Adding the Option line for "SWCursor" solved the problem.

It's worth mentioning that a software cursor adds another burden to your Atom CPU, unfortunately.
As I said earlier, this graphics driver method is really a low-performance solution.

JustGreg wrote:
I did visit www.youtube.com to try some videos. They all display OK.

That's good ... but I suspect you will not have much success with full 1920x1080 hi-res video playback, or even 1280x720.
Back to top
View user's profile Send private message 
sp0

Joined: 03 Dec 2012
Posts: 5

PostPosted: Wed 26 Dec 2012, 07:51    Post subject:  

Many thanks to those working on a Cedarview solution (hopefully to get basic resolution on my eee x101ch).

I would like to try this latest solution but can't get the instructions above to work (bit of a newbie with X, sorry). I installed the pet from smokey-01.com but installpkg.sh gave the message "cat: /tmp/petget_missing_dbentries-Packages=*: No such file or directory" - can this be safely ignored?

Then I tried editing the xorg.conf using the contents above (and also tried changing the resolutions to 1024x600) but now xwin just exits immediately. Have I missed something?
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Thu 10 Jan 2013, 07:56    Post subject:  

I have just posted a HOWTO for Cedarview graphics support in Slacko, here -
http://www.murga-linux.com/puppy/viewtopic.php?t=83636

sp0 I have sent you a PM about testing the full third-party Xorg driver update.
Back to top
View user's profile Send private message 
sharo

Joined: 06 Dec 2012
Posts: 5

PostPosted: Wed 06 Mar 2013, 08:45    Post subject: Lost screen resolution Slacko-5.5-4G nonPAE
Subject description: Acer Aspire One-751h, Intel GMA500 (Poulsbo) 1366x768
 

01micko wrote:
sharo

Only the first paragraph should apply to you if you use slacko-5.4-4g. Try the mentioned "modesetting" driver from the xorgwizard.

I was supprised again, when Racy-5.5 was able to load the correct video driver for Acer Aspire One-751h, Intel GMA500 (Poulsbo) 1366x768 with correct resolution, but Slacko-5.5-4G non PAE did NOT?!
Is it so hard to borrow this from Racy?
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 2 [17 Posts]   Goto page: 1, 2 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Hardware » Video
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1416s ][ Queries: 12 (0.0041s) ][ GZIP on ]