You are not logged in.

#1 2009-08-03 16:28:45

hjk
Member
From: Wastelands
Registered: 2009-04-27
Posts: 8
Website

Arch64 on Samsung NC20

hi all,
this is my first post and it is the first time that i'm using arch (decade long slackware addict here)

I was wondering whether somebody uses arch on the samsung nc20. i haven't found one single post in the forum about it, is it because no one uses it or because everything runs smoothly?

i got arch64 installed on the machine and everything is working fine, except that the screen won't come up after suspend or hibernate.
I am using openchrome because the proprietary via gfx driver doesn't work with xorg 1.6 (i would be using it anyway since i tend to prefer free software, and the via driver apparently sucks)

I'm using the latest git kernel (2.6.31-rc4-git3) for all the Via Nano goodies to work (padlock for ssl encryption, RNG, cpu frequency scaling).

Has anyone managed to get suspend/hibernate work on this machine?
Does anyone have some experiences to share?

thankyou!

Last edited by hjk (2009-08-27 22:48:34)

Offline

#2 2009-08-06 06:40:02

whiteychs
Member
From: USA
Registered: 2009-02-13
Posts: 39

Re: Arch64 on Samsung NC20

edit: ** I'm stupid and the NC20 doesn't use an Atom processor ** tongue

Is there any noticeable performance difference between x86 and x86-64 on the netbook, considering a RAM max of 2gigs.

- don't mean to hijack your thread -

http://bugs.archlinux.org/task/13651

Similar problem?

Last edited by whiteychs (2009-08-06 06:52:31)

Offline

#3 2009-08-06 17:39:49

raffel
Member
Registered: 2007-09-09
Posts: 5

Re: Arch64 on Samsung NC20

Good to hear others are playing with the nc20 and Arch on it too.

I also installed Arch64 on it and use the openchrome-driver. Decided for now to let the hibernate/suspend rest untill further uprgrades of openchrome, I think it's because of the same reason that when switching to console (ctrl-alt-f1) and then trying to get back to X (one has to kill X first to be able to 'get back'). Not sure...

But what's bothering me most now is that X freezes when using Gimp. I found a few Ubuntu forumposts where users had the same issue, with openchrome, not with the via-driver. Still I'ld like to solve it with openchrome. A sugestion was to set DefaultColorDepth to 32 in xorg.conf. Didn't work in Arch64, do you think better luck on x86 Arch? (don't mind to go 'back', probably you won't notice) Any ideas?

I couldn't find any errors in my logs on it, probably because of the system freezing.

For the rest I'm very happy with my nc20!

Offline

#4 2009-08-12 02:37:12

ElkMonster
Member
Registered: 2008-11-24
Posts: 27

Re: Arch64 on Samsung NC20

Hey, I also have the NC20, but with Arch32 instead of -64 (because I wanted to avoid some trouble that I had with -64 on my other machine).
Suspend and hibernate are working fine for me, the screen always comes back (the problems that used to appear have gone for me with the latest kernel (2.6.30-x); I have to mention, though, that I use sleeping much less often that hibernating). I still have a pretty old revision of the openchrome module, as the newer ones seemed to constantly introduce new bugs or disfunctionalities. This might also play a role.

One thing that annoys me is that the CPU fan constantly blows as soon as more than about 10 wakeups per second are reported by powertop. The CPU becomes warm quickly, and does not seem to cool down again even when there's nearly nothing to do. For example, it is blowing out warm air right now while typing this text, even though Opera with a few text-only tabs is running. I'm using e_powersaver, reloading it during boot in order to enable the correct frequencies (or at least the numbers it displays).

Offline

#5 2009-08-17 23:21:31

hjk
Member
From: Wastelands
Registered: 2009-04-27
Posts: 8
Website

Re: Arch64 on Samsung NC20

hi all!
so, i understand that the suspend/hibernate issue IS actually an issue related to 64bit openchrome. we only need to wait apparently, even though a patch was already submitted to openchrome addressing a similar issue: http://www.openchrome.org/trac/ticket/308

e_powersaver is now deprecated for frequency scaling for via C7/Nano processors (http://lkml.org/lkml/2009/6/8/73). The generic acpi driver manages it in the latest kernel and works fine for me.

I also have to report that i have no issue with gimp using the latest openchrome and NO xorg.conf at all.


bye
hjk

Offline

#6 2009-08-18 22:15:15

ElkMonster
Member
Registered: 2008-11-24
Posts: 27

Re: Arch64 on Samsung NC20

hjk wrote:

e_powersaver is now deprecated for frequency scaling for via C7/Nano processors (http://lkml.org/lkml/2009/6/8/73). The generic acpi driver manages it in the latest kernel and works fine for me.

Which kernel are you refering to - the stable one from the arch repositories or one of the current 2.6.31-RCs?

Last edited by ElkMonster (2009-08-18 22:15:48)

Offline

#7 2009-08-24 22:20:43

raffel
Member
Registered: 2007-09-09
Posts: 5

Re: Arch64 on Samsung NC20

So suspend is working with Arch32. Even the sleep-button (Fn-Esc) works well after changing /etc/acpi/handler.sh:

...
    button/sleep)
        case "$2" in
#            SLPB)   echo -n mem >/sys/power/state ;;
         SLPB)   pm-suspend ;;
        *)      logger "ACPI action undefined: $2" ;;
...

I keep updating my openchrome-svn daily. But unfortunately, Gimp on my system still freezes. Has it something to do with the relation to opengl or xv? I don't know much about that.
Gimp starts up fine. I can select, copy, paste as new, edit pictures that way. But as soon as the pencil or brush comes in ~~~ Freeze.
Or maybe, GTK2 (-theme) related? I use LXDE, openbox, tried about every theme.......

Indeed, can do without the xorg.conf file now.

If someone could point me in the right direction on this Gimp-thing. That would great.

Last edited by raffel (2009-08-25 12:41:34)

Offline

#8 2009-08-25 11:27:53

raffel
Member
Registered: 2007-09-09
Posts: 5

Re: Arch64 on Samsung NC20

So I did find a solution to the Gimp-X-freeze:
It seems I do need xorg.conf to where I add:

Option "AccelMethod" "exa"
Option "EnableAGPDMA" "true"
Option "MigrationHeuristic" "greedy"
Option "ExaScratchSize" "8192"
Option "ExaNoComposite" "true"       # [<bool>]

see: http://bbs.archlinux.org/viewtopic.php?id=64555

Last edited by raffel (2009-08-25 12:40:24)

Offline

#9 2009-08-26 09:51:44

hjk
Member
From: Wastelands
Registered: 2009-04-27
Posts: 8
Website

Re: Arch64 on Samsung NC20

ElkMonster wrote:
hjk wrote:

e_powersaver is now deprecated for frequency scaling for via C7/Nano processors (http://lkml.org/lkml/2009/6/8/73). The generic acpi driver manages it in the latest kernel and works fine for me.

Which kernel are you refering to - the stable one from the arch repositories or one of the current 2.6.31-RCs?

i am using a git kernel (2.6.31-rc4-git3, the latest being 2.6.31-rc7-git3) downloaded from kernel.org.
The 64-bit git version has support for Via PadLock, Via RNG, and ACPI frequency scaling (it scales correctly 800Mhz-1.60Ghz). No luck with suspend though.

I can post my .config in a few hours, if needed.

Offline

#10 2009-08-26 14:59:11

ElkMonster
Member
Registered: 2008-11-24
Posts: 27

Re: Arch64 on Samsung NC20

Thank you.
I think I'll just wait for the final 2.6.31 release. e_powersaver seems to work fine until now, so no need to hurry.

Offline

#11 2009-08-27 06:59:26

hjk
Member
From: Wastelands
Registered: 2009-04-27
Posts: 8
Website

Re: Arch64 on Samsung NC20

Apparently VIA has just released a new version of their proprietary drivers for the VX800 chipset.
Gfx: http://linux.via.com.tw/support/beginDo … 85&fid=585
Bsp (largely useless, consisting of stuff that already works: mmc, cpufreq, bluetooth, ...): http://linux.via.com.tw/support/beginDo … 24&fid=625

The README in the gfx package says the driver supports suspend and hibernation. Anyway the xorg module compiles but doesn't load and the DRM module doesn't compile against a 2.6.31-rc kernel, not sure about stock 2.6.30 hmm

Discussion also over here http://ubuntuforums.org/showthread.php?p=7852888

Last edited by hjk (2009-08-27 13:46:38)

Offline

#12 2009-08-27 14:18:24

thn81
Member
Registered: 2009-08-27
Posts: 88

Re: Arch64 on Samsung NC20

Hi everybody,
I also have installed Arch32 on my NC20 and I am currently using the proprietary VIA binary driver released in December last year. I had to downgrade to Xorg server 1.5, but (almost) everything works (2D, 3D, compositing, XVideo) at a decent speed. The kernel module on VIA's website is outdated, so I picked the most recent DRM patches submitted by the VIA people from the dri-devel mailing list. They can be applied with minor tweaks to a 2.6.30 or .31rc kernel and work with the binary driver.
However, I couldn't get EXA to work and sometimes the driver hangs X or shows strange colors (mostly after suspend2ram). So i tried the new opensource VIA driver released two days ago which is, to be honest, almost unusable. Well, I had some...sort of...success. At first I ran into the five (!) different but all outdated versions of the DRM module (via_chrome9.ko) so I kept my own patched-into-kernel version. Ok, compiling the X driver worked but X only gave me a black screen. It turned out that the driver tried to activate the (of course nonexistant) DVI port. So I added four "Monitor" sections to xorg.conf, with DVI,LCD,CRT and TV as identifiers:

Section "Monitor"
        Identifier      "TV"
        Option          "Ignore"        "true"
EndSection      

Section "Monitor"
        Identifier      "LCD"
        Option          "Enable"            "true"
        Option          "PanelSize"     "1280x800"
EndSection

Section "Monitor"
        Identifier      "CRT"
        Option          "Enable"            "true"
        Option          "PreferredMode"     "1024x768"
EndSection

Section "Monitor"
        Identifier      "DVI"
        Option          "Ignore"        "true"
EndSection

Now X gave me an image which looked alright. So I tried and enabled DRI and EXA acceleration. Bad idea. All my desktop icons were gone and my kernel log started to fill with messages about  DRM memory errors. Of course, any 3D OpenGL acceleration didn't work any more. Disabling DRI and using XAA for 2D acceleration led to a usable but slow desktop.
I don't know why but the driver seems to have problems initializing the video memory manager because the DRM module threw out messages like "PCIE init error using PCI" and "memory manager uninitialized" to the kernel log. These were not there with the old driver.
So finally I gave up with the new driver and reverted back to the old binary one. Let's hope that VIA will solve these problems; they already had a working beta driver but they obviously messed it up. If anyone around here knows how to get around these DRM problems please let me know.

Thanks a lot.

thn81

Offline

#13 2009-08-27 22:45:57

hjk
Member
From: Wastelands
Registered: 2009-04-27
Posts: 8
Website

Re: Arch64 on Samsung NC20

I just tried the newly released official drivers on x86_64. The xorg module loads but X crashes sistematically.
I tried to disable vbe in xorg.conf because i think the issue is related to it, but still no luck.

here is Xorg.0.log

X.Org X Server 1.6.3
Release Date: 2009-7-31
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.30-ARCH x86_64 
Current Operating System: Linux weiss 2.6.31-rc7 #1 PREEMPT Wed Aug 26 20:12:10 UTC 2009 x86_64
Build Date: 25 August 2009  09:11:18PM
 
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Aug 27 20:12:15 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "X.org Configured"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "LCD"
(**) |   |-->Device "Card0"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(**) Option "RandR" "false"
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/X11/misc/" does not exist.
    Entry deleted from font path.
(WW) The directory "/usr/share/fonts/X11/TTF/" does not exist.
    Entry deleted from font path.
(WW) The directory "/usr/share/fonts/X11/OTF" does not exist.
    Entry deleted from font path.
(WW) The directory "/usr/share/fonts/X11/Type1/" does not exist.
    Entry deleted from font path.
(WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
    Entry deleted from font path.
(WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
    Entry deleted from font path.
(**) FontPath set to:
    /usr/share/fonts/misc,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/TTF,
    /usr/share/fonts/Type1,
    built-ins
(**) ModulePath set to "/usr/lib/xorg/modules"
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Mouse0
(WW) Disabling Keyboard0
(II) Loader magic: 0x15c0
(II) Module ABI versions:
    X.Org ANSI C Emulation: 0.4
    X.Org Video Driver: 5.0
    X.Org XInput driver : 4.0
    X.Org Server Extension : 2.0
(II) Loader running on linux
(++) using VT number 7

(--) PCI:*(0:0:1:0) 1106:1122:144d:c04e VIA Technologies, Inc. VX800/VX820 Chrome 9 HC3 Integrated Graphics rev 17, Mem @ 0xd0000000/268435456, 0xf4000000/16777216, 0xf0000000/67108864, BIOS @ 0x????????/65536
(II) Open ACPI successful (/var/run/acpid.socket)
(II) System resource ranges:
    [0] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
    [1] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
    [5] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [6] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [7] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [8] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
    [9] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [10] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [11] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [12] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
    [13] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [14] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [15] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [16] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
    [17] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [18] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [19] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [20] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
    [21] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [22] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [23] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [24] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
    [25] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [26] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [27] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [28] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
    [29] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [30] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [31] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [32] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [33] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    [34] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [35] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    [36] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [37] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    [38] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [39] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    [40] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [41] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    [42] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [43] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    [44] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [45] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    [46] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [47] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
(WW) "vbe" will not be loaded unless you've specified it to be loaded elsewhere.
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "record" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri2" will be loaded by default.
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
    compiled for 1.6.3, module version = 1.0.0
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
    compiled for 1.6.3, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
    compiled for 1.6.3, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
    compiled for 1.6.3, module version = 1.13.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
    compiled for 1.6.3, module version = 1.0.0
    ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "xtrap"
(WW) Warning, couldn't open module xtrap
(II) UnloadModule: "xtrap"
(EE) Failed to load module "xtrap" (module does not exist, 0)
(II) LoadModule: "freetype"
(WW) Warning, couldn't open module freetype
(II) UnloadModule: "freetype"
(EE) Failed to load module "freetype" (module does not exist, 0)
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
    compiled for 1.6.3, module version = 1.1.0
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "via"
(II) Loading /usr/lib/xorg/modules/drivers//via_drv.so
(II) Module via: vendor="X.Org Foundation"
    compiled for 1.6.3, module version = 5.74.255
    Module class: X.Org Video Driver
(II) via: driver for VIA chipsets: P4M800PRO, CX700, K8M890, P4M890,
    P4M900, VX800, VX855
(II) Primary Device is: PCI 00@00:01:0
(II) resource ranges after probing:
    [0] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
    [1] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
    [5] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [6] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [7] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [8] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
    [9] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [10] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [11] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [12] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
    [13] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [14] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [15] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [16] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
    [17] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [18] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [19] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [20] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
    [21] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [22] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [23] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [24] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
    [25] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [26] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [27] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [28] -1    0    0xffffffff - 0xffffffff (0x1) MX[b]
    [29] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [30] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [31] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [32] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [33] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    [34] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [35] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    [36] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [37] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    [38] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [39] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    [40] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [41] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    [42] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [43] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    [44] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [45] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
    [46] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [47] -1    0    0x00000000 - 0x00000000 (0x1) IX[b]
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
    compiled for 1.6.3, module version = 0.1.0
    ABI class: X.Org Video Driver, version 5.0
(II) Loading sub module "viavideo"
(II) LoadModule: "viavideo"
(WW) Warning, couldn't open module viavideo
(II) UnloadModule: "viavideo"
(EE) VIA: Failed to load module "viavideo" (module does not exist, 0)
(WW) VIA(0):  Couldn't open viavideo
(--) VIA(0): Chipset: "VX800"
(--) VIA(0): Chipset Rev.: 0
(**) VIA(0): Depth 24, (--) framebuffer bpp 32
(==) VIA(0): RGB weight 888
(==) VIA(0): Default visual is TrueColor
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules//libint10.so
(II) Module int10: vendor="X.Org Foundation"
    compiled for 1.6.3, module version = 1.0.0
    ABI class: X.Org Video Driver, version 5.0
(II) VIA(0): Primary V_BIOS segment is: 0xc000
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
    compiled for 1.6.3, module version = 1.1.0
    ABI class: X.Org Video Driver, version 5.0
(II) VIA(0): VESA BIOS detected
(II) VIA(0): VESA VBE Version 3.0
(II) VIA(0): VESA VBE Total Mem: 32768 kB
(II) VIA(0): VESA VBE OEM: VIA VX800


(II) VIA(0): VESA VBE OEM Software Rev: 1.0
(II) VIA(0): VESA VBE OEM Vendor: 
(II) VIA(0): VESA VBE OEM Product: 
(II) VIA(0): VESA VBE OEM Product Rev: 
(**) VIA(0): Option "ActiveDevice" "LCD"
(**) VIA(0): Option "LCDPort" "LVDS0"
(**) VIA(0): Option "PanelSize" "1280x800"
(==) VIA(0): Using XAA acceleration architecture.
(II) VIA(0): MergedFB mode forced off.
(**) VIA(0): Active Device is LCD.
(**) VIA(0): LCD Panel Size is 1280x800.
(II) VIA(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) VIA(0): VGA BIOS Version is = 5.0
(II) VIA(0): VGA BIOS Release Date Is: 2008/12/1
(==) VIA(0): Using gamma correction (1.0, 1.0, 1.0)
(--) VIA(0): videoram =  262144k
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Module "i2c" already built-in
(II) VIA(0): I2C bus "I2C bus 1" initialized.
(II) VIA(0): I2C bus "I2C bus 2" initialized.
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
    compiled for 1.6.3, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/lib/xorg/modules//libxaa.so
(II) Module xaa: vendor="X.Org Foundation"
    compiled for 1.6.3, module version = 1.2.1
    ABI class: X.Org Video Driver, version 5.0
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in

Backtrace:
0: /usr/bin/Xorg(xorg_backtrace+0x26) [0x4e9186]
1: /usr/bin/Xorg(xf86SigHandler+0x6f) [0x47612f]
2: /lib/libc.so.6 [0x7fcefeaa2f90]
3: /usr/lib/xorg/modules/drivers//via_drv.so(viaWriteVgaIo+0x24) [0x7fcefd2ae2e4]
4: /usr/lib/xorg/modules/drivers//via_drv.so [0x7fcefd2ae68f]
5: /usr/lib/xorg/modules/drivers//via_drv.so [0x7fcefd2aea47]
6: /usr/lib/xorg/modules/drivers//via_drv.so [0x7fcefd2aeb11]
7: /usr/lib/xorg/modules/drivers//via_drv.so(viaSerialReadBytes+0x48) [0x7fcefd2aecb8]
8: /usr/lib/xorg/modules/drivers//via_drv.so(VIADoEDID+0x13d) [0x7fcefd2dbd1d]
9: /usr/lib/xorg/modules/drivers//via_drv.so [0x7fcefd2dd89d]
10: /usr/bin/Xorg(InitOutput+0x507) [0x468e27]
11: /usr/bin/Xorg(main+0x1fe) [0x42e5be]
12: /lib/libc.so.6(__libc_start_main+0xfd) [0x7fcefea8f9ed]
13: /usr/bin/Xorg [0x42dbf9]

Fatal server error:
Caught signal 11.  Server aborting


Please consult the The X.Org Foundation support 
     at http://wiki.x.org
 for help. 
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

Offline

#14 2009-08-28 09:32:28

ElkMonster
Member
Registered: 2008-11-24
Posts: 27

Re: Arch64 on Samsung NC20

Does the current x86_32 openchrome svn trunk work for anybody with the standard Arch packages, i.e., without any additional patches?
Motivated by this thread, I decided to update my driver (had revision 741 before for quite a long time) but found that every newer revision I tried since then would totally freeze the computer. After startx, it shows a corrupted desktop and nothing works anymore and music playing in a terminal just hangs and loops the last played chunk. All I can do then is to hold the power button and restart. There is nothing in the log files about it, so I cannot even tell what went wrong.
Any ideas? My xorg.conf looks like the ones one finds here or in other places talking about the NC20, and I also tried changing a number of options, but to no avail.

Offline

#15 2009-08-28 19:12:33

raffel
Member
Registered: 2007-09-09
Posts: 5

Re: Arch64 on Samsung NC20

Current openchrome-svn drivers do well without extra patches on my nc20 for Arch32 and Arch64 (that is openchrome-svn-780-1-x86_64 and openchrome-svn-781-1-i686). Both with Exa accellmethod (to prevend Gimp-X-freeze). Never had any X refusing to start up or crash (so far). But even without the xorg.conf file -to add exa- it starts up ok. Never had any problems with previous versions either.
I'm using LXDE.
Maybe some dependencies changed? I'm using the openchrome-svn driver since version 758....

Offline

#16 2009-08-28 20:35:05

thn81
Member
Registered: 2009-08-27
Posts: 88

Re: Arch64 on Samsung NC20

ElkMonster wrote:

After startx, it shows a corrupted desktop and nothing works anymore

Do you have any DRM kernel modules loaded? Especially via.ko or via_chrome9.ko? If you do, remove them as openchrome tries to use them and subsequently crashes the kernel. The Xorg.0.log would also be helpful.

Offline

#17 2009-08-29 09:15:57

Uli_of
Member
Registered: 2009-08-29
Posts: 3

Re: Arch64 on Samsung NC20

The error is in openchrome svn 768. If you comment out in the sourcefiles  via_mode.c line 1623 and compile the souce, svn 781 will work.

If someone is getting the new via driver getting to work, I am interestet to know the framerate with glxgears.
I am running a NC20 with Opensuse factory.

Offline

#18 2009-08-29 09:17:45

Uli_of
Member
Registered: 2009-08-29
Posts: 3

Re: Arch64 on Samsung NC20

Sorry for a typo, error is in svn 764

Offline

#19 2009-09-01 10:39:43

ElkMonster
Member
Registered: 2008-11-24
Posts: 27

Re: Arch64 on Samsung NC20

Uli_of wrote:

The error is in openchrome svn 768. If you comment out in the sourcefiles  via_mode.c line 1623 and compile the souce, svn 781 will work.

Thank you, that worked! cool

Offline

#20 2009-09-18 02:29:47

freeseek
Member
Registered: 2009-09-18
Posts: 1

Re: Arch64 on Samsung NC20

ElkMonster wrote:
Uli_of wrote:

The error is in openchrome svn 768. If you comment out in the sourcefiles  via_mode.c line 1623 and compile the souce, svn 781 will work.

Thank you, that worked! cool

What line is that exactly? I have the same problem, but since openchrome is now svn 787, the line numbers have changed!

Offline

#21 2009-09-18 18:57:39

ElkMonster
Member
Registered: 2008-11-24
Posts: 27

Re: Arch64 on Samsung NC20

freeseek wrote:

What line is that exactly? I have the same problem, but since openchrome is now svn 787, the line numbers have changed!

    ...
    pBIOSInfo->ClockExternal = FALSE;

    /* Enable MMIO & PCI burst (1 wait state) */
--> //ViaSeqMask(hwp, 0x1A, 0x06, 0x06);  <-- this one

    ViaSetPrimaryFIFO(pScrn, mode);
    ...

However, I'm not sure that this solution still applies to the current svn revision, or whether there's a need to change anything at all.

Last edited by ElkMonster (2009-09-18 18:58:23)

Offline

#22 2009-09-19 14:47:29

Uli_of
Member
Registered: 2009-08-29
Posts: 3

Re: Arch64 on Samsung NC20

Use openchrome latest  svn 790 . it works and has removed the change of svn 764.
rgards

Offline

#23 2009-11-10 16:56:58

ak88
Member
Registered: 2009-11-10
Posts: 1

Re: Arch64 on Samsung NC20

Could somebody Vesa user pleas put xorg.conf to use as model?

Offline

#24 2010-05-07 10:53:02

lamek
Member
Registered: 2009-11-29
Posts: 33

Re: Arch64 on Samsung NC20

can someone post xorg.conf file that use openchrome driver?

Offline

Board footer

Powered by FluxBB