ALARM on Samsung ARM Chromebook

Install Arch Linux ARM on other devices.

Re: ALARM on Samsung ARM Chromebook

Postby simonbp » Fri Feb 22, 2013 2:43 am

Right, but that won't work if you need to use WPA/WPA2, which I do.

Ultimately, I think it's just the recent version of wpa_supplicant is incompatible with the 3.4.0 kernel, meaning that I need to install nv-u-boot to get a more recent kernel.
simonbp
 
Posts: 8
Joined: Thu Feb 21, 2013 7:25 pm

Re: ALARM on Samsung ARM Chromebook

Postby relghuar » Fri Feb 22, 2013 5:55 am

simonbp wrote:Right, but that won't work if you need to use WPA/WPA2, which I do.

Ultimately, I think it's just the recent version of wpa_supplicant is incompatible with the 3.4.0 kernel, meaning that I need to install nv-u-boot to get a more recent kernel.


Hi, 3.4.0 kernel can't be the problem - even with nv-u-boot, the kernel in alarm repository is still the same version. Besides, latest wpa_supplicant and original chromeos kernel worked for me (see my post a few days back with full configuration), just NetworkManager didn't. Now, however, even that works fine - that must be either thanks to the alarm kernel, or the udev renaming mlan0->wlan0 (see another post 2-3 days back), as I didn't change anything else. As others reported, wicd should work with this wlan0 renaming as well.
Regards,
Peter
relghuar
 
Posts: 18
Joined: Sun Nov 18, 2012 3:51 pm

Re: ALARM on Samsung ARM Chromebook

Postby strata » Sat Feb 23, 2013 3:37 am

relghuar wrote:I have a much simpler way - at least for flash reading it works like a charm... I found a modified flashrom binary on my original chromeos partition (in /tmp/fwupd) - this one can work with built-in SPI flash directly from linux, with verification and everything . . .


This has been added as alarm/flashrom-google
strata
 
Posts: 6
Joined: Wed Jan 23, 2013 8:21 pm

Re: ALARM on Samsung ARM Chromebook

Postby relghuar » Sat Feb 23, 2013 11:27 am

strata wrote:This has been added as alarm/flashrom-google


:-D actually, I just saw it has been added as alarm/flashroom-google... I wonder what's Google flashing there?
relghuar
 
Posts: 18
Joined: Sun Nov 18, 2012 3:51 pm

Re: ALARM on Samsung ARM Chromebook

Postby byrdman » Tue Feb 26, 2013 12:42 am

jkirby wrote:I installed the ARM image file fresh and did a pacman -Syu. It trashed the system. After five or six tries, I got it working. I have to make a few updates first before making the full upgrade:

1) C runtime libraries
2) Bash
3) coreutils

I may have updated a few other less significant things, but the runtime libraries and the coreutils are required first.

Then I upgraded chromeos with pacman -S linux and selected option 2 (linux-chromeos).

Reboot.
Bring up network.

pacman -Syu

You still have to setup wifi or ethernet yourself. Netcfg works.

I notice that suspend and sleep are working great now.


I tried this exactly as you said but my wifi wouldn't connect on reboot (even with netcfg)

2 questions:
1) What were the other packages you installed?
2) Option number 2 from pacman -S linux is now linux-chromebook. Would that cause any problems?
byrdman
 
Posts: 2
Joined: Thu Feb 21, 2013 7:49 pm

Re: ALARM on Samsung ARM Chromebook

Postby pepedog » Tue Feb 26, 2013 10:20 am

I shouldn't post here as I don't have one of these devices, but there seems to be a "bug" where some modules are not loaded before netcfg is swinging into action. I have to do similar on an eee701 and wireless dongles on raspberry pi.
What is the wireless module called? Let's call it cbwireless, substitute that with real module name
Code: Select all
echo "cbwireless" > /etc/modules-load.d/cbwireless.conf

If wireless doesn't work on reboot, here is a simple (no scanning) config example
Code: Select all
cp /etc/network.d/examples/wireless-wpa /etc/network.d/examples/mywireless

Edit just ESSID and KEY
Now
Code: Select all
systemctl enable netcfg@mywireless

Disable any other network services if this works.
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: ALARM on Samsung ARM Chromebook

Postby Gary13579 » Fri Mar 08, 2013 9:34 am

I can't get the armsoc driver working. Here's my xorg config:

Code: Select all

Section "Device"
        Identifier      "Mali FBDEV"
        Driver          "armsoc"
        Option          "fbdev"                 "/dev/fb0"
        Option          "Fimg2Dexa"             "false"
        Option          "DRI2"                  "true"
        Option          "DRI2_PAGE_FLIP"        "false"
        Option          "DRI2_WAIT_VSYNC"       "true"
        Option          "SWcursorLCD"           "false"
EndSection

Section "Screen"
        Identifier      "DefaultScreen"
        Device          "Mali FBDEV"
        DefaultDepth    24
EndSection


Here's the Xorg log:

Code: Select all
[gary@alarm ~]$ cat Xorg.0.log
[  1860.712]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[  1860.713]
X.Org X Server 1.13.2.901 (1.13.3 RC 1)
Release Date: 2013-02-15
[  1860.716] X Protocol Version 11, Revision 0
[  1860.717] Build Operating System: Linux 3.2.34-1-FARM armv7l
[  1860.718] Current Operating System: Linux alarm 3.4.0 #1 SMP Fri Oct 19 00:55:31 PDT 2012 armv7l
[  1860.718] Kernel command line: cros_secure console= console=tty1 debug verbose root=/dev/mmcblk1p3 rootwait rw
[  1860.720] Build Date: 24 February 2013  12:25:58AM
[  1860.721] 
[  1860.722] Current version of pixman: 0.28.2
[  1860.724]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[  1860.724] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1860.729] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar  8 03:34:38 2013
[  1860.731] (==) Using config directory: "/etc/X11/xorg.conf.d"
[  1860.731] (==) No Layout section.  Using the first Screen section.
[  1860.731] (**) |-->Screen "DefaultScreen" (0)
[  1860.731] (**) |   |-->Monitor "<default monitor>"
[  1860.732] (**) |   |-->Device "Mali FBDEV"
[  1860.732] (==) No monitor specified for screen "DefaultScreen".
        Using a default monitor configuration.
[  1860.732] (==) Automatically adding devices
[  1860.732] (==) Automatically enabling devices
[  1860.732] (==) Automatically adding GPU devices
[  1860.732] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[  1860.732]    Entry deleted from font path.
[  1860.732] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[  1860.732]    Entry deleted from font path.
[  1860.732] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[  1860.732]    Entry deleted from font path.
[  1860.732]    (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[  1860.732] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[  1860.732]    Entry deleted from font path.
[  1860.732]    (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[  1860.732] (==) FontPath set to:
        /usr/share/fonts/misc/,
        /usr/share/fonts/TTF/
[  1860.732] (==) ModulePath set to "/usr/lib/xorg/modules"
[  1860.732] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[  1860.732] (II) Loader magic: 0x1bf958
[  1860.732] (II) Module ABI versions:
[  1860.732]    X.Org ANSI C Emulation: 0.4
[  1860.732]    X.Org Video Driver: 13.1
[  1860.732]    X.Org XInput driver : 18.0
[  1860.732]    X.Org Server Extension : 7.0
[  1860.733] (II) config/udev: Adding drm device (/dev/dri/card0)
[  1860.735] Initializing built-in extension Generic Event Extension
[  1860.736] Initializing built-in extension SHAPE
[  1860.737] Initializing built-in extension MIT-SHM
[  1860.739] Initializing built-in extension XInputExtension
[  1860.740] Initializing built-in extension XTEST
[  1860.742] Initializing built-in extension BIG-REQUESTS
[  1860.743] Initializing built-in extension SYNC
[  1860.744] Initializing built-in extension XKEYBOARD
[  1860.746] Initializing built-in extension XC-MISC
[  1860.747] Initializing built-in extension SECURITY
[  1860.749] Initializing built-in extension XINERAMA
[  1860.750] Initializing built-in extension XFIXES
[  1860.751] Initializing built-in extension RENDER
[  1860.753] Initializing built-in extension RANDR
[  1860.754] Initializing built-in extension COMPOSITE
[  1860.756] Initializing built-in extension DAMAGE
[  1860.757] Initializing built-in extension MIT-SCREEN-SAVER
[  1860.759] Initializing built-in extension DOUBLE-BUFFER
[  1860.760] Initializing built-in extension RECORD
[  1860.762] Initializing built-in extension DPMS
[  1860.763] Initializing built-in extension X-Resource
[  1860.764] Initializing built-in extension XVideo
[  1860.766] Initializing built-in extension XVideo-MotionCompensation
[  1860.767] Initializing built-in extension XFree86-VidModeExtension
[  1860.769] Initializing built-in extension XFree86-DGA
[  1860.770] Initializing built-in extension XFree86-DRI
[  1860.771] Initializing built-in extension DRI2
[  1860.771] (II) LoadModule: "glx"
[  1860.772] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  1860.772] (II) Module glx: vendor="X.Org Foundation"
[  1860.772]    compiled for 1.13.2.901, module version = 1.0.0
[  1860.772]    ABI class: X.Org Server Extension, version 7.0
[  1860.772] (==) AIGLX enabled
[  1860.773] Loading extension GLX
[  1860.773] (II) LoadModule: "armsoc"
[  1860.774] (II) Loading /usr/lib/xorg/modules/drivers/armsoc_drv.so
[  1860.774] (II) Module armsoc: vendor="X.Org Foundation"
[  1860.774]    compiled for 1.13.2, module version = 0.83.0
[  1860.774]    Module class: X.Org Video Driver
[  1860.774]    ABI class: X.Org Video Driver, version 13.1
[  1860.774] (II) ARMSOC: Driver for TI OMAP: OMAP3430 with PowerVR SGX530,
        OMAP3630 with PowerVR SGX530, OMAP4430 with PowerVR SGX540,
        OMAP4460 with PowerVR SGX540, OMAP5430 with PowerVR SGX544 MP,
        OMAP5432 with PowerVR SGX544 MP, Mali-T60x
[  1860.774] (++) using VT number 1

[  1860.774] (WW) Falling back to old probe method for armsoc
[  1860.775] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[  1860.775] (II) ARMSOC(0): Creating default Display subsection in Screen section
        "DefaultScreen" for depth/fbbpp 24/32
[  1860.775] (**) ARMSOC(0): Depth 24, (--) framebuffer bpp 32
[  1860.775] (==) ARMSOC(0): RGB weight 888
[  1860.775] (==) ARMSOC(0): Using gamma correction (1.0, 1.0, 1.0)
[  1860.775] (==) ARMSOC(0): Default visual is TrueColor
[  1860.775] (II) ARMSOC(0): Found chipset: Mali-T60x
[  1860.775] (II) ARMSOC(0): Using HW cursor
[  1860.775] (II) ARMSOC(0): Setting the video modes ...
[  1860.775] (II) ARMSOC(0): Output eDP-1 has no monitor section
[  1860.775] (II) ARMSOC(0): Output HDMI-1 has no monitor section
[  1860.775] (II) ARMSOC(0): Printing probed modes for output eDP-1
[  1860.775] (II) ARMSOC(0): Modeline "1366x768"x59.9   70.50  1366 1406 1438 1478  768 780 786 796 (47.7 kHz eP)
[  1860.775] (II) ARMSOC(0): EDID for output HDMI-1
[  1860.776] (II) ARMSOC(0): Output eDP-1 connected
[  1860.776] (II) ARMSOC(0): Output HDMI-1 disconnected
[  1860.776] (II) ARMSOC(0): Using exact sizes for initial modes
[  1860.776] (II) ARMSOC(0): Output eDP-1 using initial mode 1366x768
[  1860.776] (II) ARMSOC(0): Got KMS resources
[  1860.776] (==) ARMSOC(0): DPI set to (96, 96)
[  1860.776] (II) Loading sub module "dri2"
[  1860.776] (II) LoadModule: "dri2"
[  1860.776] (II) Module "dri2" already built-in
[  1860.776] (II) Loading sub module "exa"
[  1860.776] (II) LoadModule: "exa"
[  1860.776] (II) Loading /usr/lib/xorg/modules/libexa.so
[  1860.776] (II) Module exa: vendor="X.Org Foundation"
[  1860.776]    compiled for 1.13.2.901, module version = 2.6.0
[  1860.776]    ABI class: X.Org Video Driver, version 13.1
[  1860.776] (II) Loading sub module "fb"
[  1860.776] (II) LoadModule: "fb"
[  1860.776] (II) Loading /usr/lib/xorg/modules/libfb.so
[  1860.777] (II) Module fb: vendor="X.Org Foundation"
[  1860.777]    compiled for 1.13.2.901, module version = 1.0.0
[  1860.777]    ABI class: X.Org ANSI C Emulation, version 0.4
[  1860.777] (--) Depth 24 pixmap format is 32 bpp
[  1860.778] (II) ARMSOC(0): Soft EXA mode
[  1860.778] (II) EXA(0): Driver allocated offscreen pixmaps
[  1860.778] (II) EXA(0): Driver registered support for the following operations:
[  1860.778] (II)         Solid
[  1860.778] (II)         Copy
[  1860.778] (II)         Composite (RENDER acceleration)
[  1860.778] (II) ARMSOC(0): [DRI2] Setup complete
[  1860.778] (II) ARMSOC(0): [DRI2]   DRI driver: armsoc
[  1860.778] (==) ARMSOC(0): Backing store disabled
[  1860.778] (==) ARMSOC(0): Silken mouse enabled
[  1860.778] (II) ARMSOC(0): HW cursor initialized
[  1860.785] (II) ARMSOC(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[  1860.785] (==) ARMSOC(0): DPMS enabled
[  1860.786] (EE) DRM_IOCTL_EXYNOS_GEM_CPU_ACQUIRE failed: -1(EE) DRM_IOCTL_EXYNOS_GEM_CPU_RELEASE failed: -1(--) RandR disabled
[  1860.834] (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/armsoc_dri.so failed (/usr/lib/xorg/modules/dri/armsoc_dri.so: cannot open shared object file: No such file or directory)
[  1860.834] (EE) AIGLX: reverting to software rendering
[  1860.834] (II) AIGLX: Screen 0 is not DRI capable
[  1860.845] (II) AIGLX: Loaded and initialized swrast
[  1860.845] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[  1860.846] (II) ARMSOC(0): Setting screen physical size to 361 x 203
[  1860.846] (EE) DRM_IOCTL_EXYNOS_GEM_CPU_ACQUIRE failed: -1
Fatal server error:
[  1860.846] Driver failed PrepareAccess on a pinned pixmap.
[  1860.846]
[  1860.846] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[  1860.846] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[  1860.846] (EE)
[  1860.853] Server terminated with error (1). Closing log file.
[gary@alarm ~]$
Gary13579
 
Posts: 30
Joined: Tue Feb 28, 2012 9:21 am

Re: ALARM on Samsung ARM Chromebook

Postby Gary13579 » Fri Mar 08, 2013 11:00 am

It looks like there's two versions of xf86-video-armsoc in the alarm repo. I'm guessing the newer version requires the latest linux-chromebook kernel, which requires nv-u-boot (I haven't installed it yet). Using the older armsoc works.

But performance is god-awful. fbdev driver provides much better performance, but is still ridiculously slow. Is there something I am missing to get better performance out of the Chromebook? Watching a small gif in my IRC client eats up 80% of one core of the CPU.. trying to watch a 360p video in HTML5 YouTube is impossible (it's like 1 frame every 5 seconds).
Gary13579
 
Posts: 30
Joined: Tue Feb 28, 2012 9:21 am

Re: ALARM on Samsung ARM Chromebook

Postby stronnag » Fri Mar 08, 2013 3:01 pm

I find that with the linux-chromebook kernel and xf86-video-armsoc I can watch typical internet videos and even DVDs ripped to mkv/mp4. This may be because I added a udev rule to allow members of the video group to access the mali device, thusly (as //etc/udev/rules.d/50-mali.rules):
Code: Select all
$ cat /etc/udev/rules.d/50-mali.rules
KERNEL=="mali0", MODE="0660", GROUP="video"
$
Or perhaps coincidence.
However, there are downsides to using xf86-video-armsoc, in particular the lack of a usable X after suspend / resume, without restarting the lxdm service (clues on a workaround gratefully accepted).
stronnag
 
Posts: 42
Joined: Sat Sep 22, 2012 6:51 am

Re: ALARM on Samsung ARM Chromebook

Postby dutra » Sat Mar 09, 2013 1:23 am

I followed the steps from here http://craigerrington.com/blog/installi ... hromebook/

Then, I followed similar steps and zcat the tarball from the SD card into mmcblk0. When I try to boot into my system without a sd card, it boots but searches for the rootfs in mmcblk1p3 (sd card), and stops there. It only works if I also insert my sd card.

How can I change the rootfs variable and set it to mmcblk0p3?
dutra
 
Posts: 15
Joined: Sat Dec 03, 2011 3:01 am

PreviousNext

Return to [Please read announcement] Community-Supported Devices

Who is online

Users browsing this forum: No registered users and 1 guest