processor details missing at ubuntu 16.04

[img][/home/ali/Downloads/IMG_20161001_145844.jpg]
why theirs a missing info about processor ???

Hi AliNada,

Processor field in Ubuntu System Setting -> Details was empty because of missing model name in /proc/cpuinfo.
We will add this support in coming release, and user still could move onto other things without this info.

Thanks

thanks kayccc

but theirs also a problem in the stability of ubuntu 16.04 , i couldn’t open the browser , theirs some lag in the system , generally it was a bad experience why is that , and another question if you mind :D
i want to connect to i2s to aux port , how should i do that ???

Hi AliNada,

i want to connect to i2s to aux port , how should i do that ???
I don’t 100% understand your question. Could you give me more detail.
Jetson TX1 does not have aux port and you can find the pins of i2s on I/O expansion header.
and which browser are you using?

There have been issues with firefox crashing on anything but simple web pages (I suspect javascript being an issue). “chromium-browser” should work well until firefox gets figured out (the first time run of chromium-browser will prompt for password to set up permissions).

If you are connected directly to the internet without a router or firewall then you need to have the password chaged…else activity could be malicious from the outside world (definitely would imply sluggish behavior). If you are using purely WiFi networking then wireless could also be a reason for sluggish behavior over the internet, although it would not account for general sluggish behavior. You can run “top” or “htop” (my favorite) to see what’s using CPU.

hello tedc
i need to connect a mic to tegra board , and i am kindly new to tegra environment , so i need a clear straight way to do it , and also i need to connect it to speaker, this is the first part
the second part i need to know how to control the perphails exist in /sys/class

and Thanks in Advance

thanks Linux dev

i think you know what i was talking about , but how to fix it ???

Patching firefox on aarch64 is probably not easy. Here is a partial stack frame of the crash (and the stack frame itself goes on for at least 3 pages…this is only part of one stack frame):

Thread 1 "firefox" received signal SIGSEGV, Segmentation fault.
mozilla::dom::CanvasRenderingContext2D::EnsureErrorTarget ()
    at /build/firefox-qukfp0/firefox-49.0+build4/dom/canvas/CanvasRenderingContext2D.cpp:5382
5382    /build/firefox-qukfp0/firefox-49.0+build4/dom/canvas/CanvasRenderingContext2D.cpp: No such file or directory.
(gdb) bt
#0  0x0000007f8baff6a0 in mozilla::dom::CanvasRenderingContext2D::EnsureErrorTarget() ()
    at /build/firefox-qukfp0/firefox-49.0+build4/dom/canvas/CanvasRenderingContext2D.cpp:5382
#1  0x0000007f8bb174d8 in mozilla::dom::CanvasRenderingContext2D::EnsureTarget(mozilla::dom::CanvasRenderingContext2D::RenderingMode) (this=this@entry=0x7f5ee7a800, aRenderingMode=aRenderingMode@entry=mozilla::dom::CanvasRenderingContext2D::DefaultBackendMode)
    at /build/firefox-qukfp0/firefox-49.0+build4/dom/canvas/CanvasRenderingContext2D.cpp:1545
#2  0x0000007f8bb1ab70 in mozilla::dom::CanvasRenderingContext2D::Save() (this=0x7f5ee7a800)
    at /build/firefox-qukfp0/firefox-49.0+build4/dom/canvas/CanvasRenderingContext2D.cpp:1788
#3  0x0000007f8b842518 in mozilla::dom::CanvasRenderingContext2DBinding::save(JSContext*, JS::Handle<JSObject*>, mozilla::dom::CanvasRenderingContext2D*, JSJitMethodCallArgs const&) (cx=<optimized out>, obj=..., self=<optimized out>, args=...)
    at /build/firefox-qukfp0/firefox-49.0+build4/obj-aarch64-linux-gnu/dom/bindings/CanvasRenderingContext2DBinding.cpp:1910
#4  0x0000007f8bad6180 in mozilla::dom::GenericBindingMethod(JSContext*, unsigned int, JS::Value*) (cx=0x7f84b26400, argc=<optimized out>, vp=<optimized out>)
    at /build/firefox-qukfp0/firefox-49.0+build4/dom/bindings/BindingUtils.cpp:2784
#5  0x0000007f8c9f886c in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (args=..., native=<optimized out>, cx=0x7f84b26400)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/jscntxtinlines.h:240
#6  0x0000007f8c9f886c in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (cx=0x7f84b26400, args=..., construct=<optimized out>)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:452
#7  0x0000007f8c9f4c3c in Interpret(JSContext*, js::RunState&) (args=..., cx=<optimized out>)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:503
#8  0x0000007f8c9f4c3c in Interpret(JSContext*, js::RunState&) (cx=0x7f84b26400, state=...)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:2840
#9  0x0000007f8c9f8604 in js::RunScript(JSContext*, js::RunState&) (cx=cx@entry=0x7f84b26400, state=...) at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:398
#10 0x0000007f8c9f87cc in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (cx=cx@entry=0x7f84b26400, args=..., construct=construct@entry=js::NO_CONSTRUCT)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:470
#11 0x0000007f8c9f8a90 in InternalCall(JSContext*, js::AnyInvokeArgs const&) (cx=cx@entry=0x7f84b26400, args=...) at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:497
#12 0x0000007f8c9f8af8 in js::Call(JSContext*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, js::AnyInvokeArgs const&, JS::MutableHandle<JS::Value>) (cx=cx@entry=0x7f84b26400, fval=..., 
    fval@entry=..., thisv=..., args=..., rval=...)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:516
#13 0x0000007f8c99cc00 in js::Wrapper::call(JSContext*, JS::Handle<JSObject*>, JS::CallArgs const&) const (this=this@entry=0x7f8d2eef98 <js::CrossCompartmentWra
pper::singleton>, cx=cx@entry=0x7f84b26400, proxy=..., proxy@entry=..., args=...)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/proxy/Wrapper.cpp:165
0x0000007f8c992574 in js::CrossCompartmentWrapper::call(JSContext*, JS::Handle<JSObject*>, JS::CallArgs const&) const (this=0x7f8d2eef98 <js::CrossCompartmentWrapper::singleton>, cx=0x7f84b26400, wrapper=..., args=...)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/proxy/CrossCompartmentWrapper.cpp:313
#15 0x0000007f8c98c7ec in js::proxy_Call(JSContext*, unsigned int, JS::Value*) (args=..., proxy=..., cx=0x7f84b26400)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/proxy/Proxy.cpp:401
#16 0x0000007f8c98c7ec in js::proxy_Call(JSContext*, unsigned int, JS::Value*) (cx=0x7f84b26400, argc=<optimized out>, vp=<optimized out>)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/proxy/Proxy.cpp:693
#17 0x0000007f8c9f886c in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (args=..., native=<optimized out>, cx=0x7f84b26400) at /build/firefox-qukfp0/firefox-49.0+build4/js/src/jscntxtinlines.h:240
#18 0x0000007f8c9f886c in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (cx=0x7f84b26400, args=..., construct=<optimized out>) at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:452
#19 0x0000007f8c9f4c3c in Interpret(JSContext*, js::RunState&) (args=..., cx=<optimized out>)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:503
#20 0x0000007f8c9f4c3c in Interpret(JSContext*, js::RunState&) (cx=0x7f84b26400, state=...)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:2840
#21 0x0000007f8c9f8604 in js::RunScript(JSContext*, js::RunState&) (cx=cx@entry=0x7f84b26400, state=...)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:398
#22 0x0000007f8c9f87cc in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (cx=cx@entry=0x7f84b26400, args=..., construct=construct@entry=js::NO_CONSTRUCT) at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:470
#23 0x0000007f8c9f8a90 in InternalCall(JSContext*, js::AnyInvokeArgs const&) (cx=cx@entry=0x7f84b26400, args=...)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:497
#24 0x0000007f8c9f8af8 in js::Call(JSContext*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, js::AnyInvokeArgs const&, JS::MutableHandle<JS::Value>) (cx=cx@entry=0x7f84b26400, fval=..., fval@entry=..., thisv=..., args=..., rval=...)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:516
#25 0x0000007f8c99cc00 in js::Wrapper::call(JSContext*, JS::Handle<JSObject*>, JS::CallArgs const&) const (this=this@entry=0x7f8d2eef98 <js::CrossCompartmentWrapper::singleton>, cx=cx@entry=0x7f84b26400, proxy=..., proxy@entry=..., args=...)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/proxy/Wrapper.cpp:165
#26 0x0000007f8c992574 in js::CrossCompartmentWrapper::call(JSContext*, JS::Handle<JSObject*>, JS::CallArgs const&) const (this=0x7f8d2eef98 <js::CrossCompartmentWrapper::singleton>, cx=0x7f84b26400, wrapper=..., args=...)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/proxy/CrossCompartmentWrapper.cpp:313
#27 0x0000007f8c98c7ec in js::proxy_Call(JSContext*, unsigned int, JS::Value*) (args=..., proxy=..., cx=0x7f84b26400)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/proxy/Proxy.cpp:401
#28 0x0000007f8c98c7ec in js::proxy_Call(JSContext*, unsigned int, JS::Value*) (cx=0x7f84b26400, argc=<optimized out>, vp=<optimized out>)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/proxy/Proxy.cpp:693
#29 0x0000007f8c9f886c in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (args=..., native=<optimized out>, cx=0x7f84b26400) at /build/firefox-qukfp0/firefox-49.0+build4/js/src/jscntxtinlines.h:240
#30 0x0000007f8c9f886c in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (cx=0x7f84b26400, args=..., construct=<optimized out>) at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:452
#31 0x0000007f8c9f4c3c in Interpret(JSContext*, js::RunState&) (args=..., cx=<optimized out>)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:503
#32 0x0000007f8c9f4c3c in Interpret(JSContext*, js::RunState&) (cx=0x7f84b26400, state=...)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:2840
#33 0x0000007f8c9f8604 in js::RunScript(JSContext*, js::RunState&) (cx=cx@entry=0x7f84b26400, state=...)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:398
#34 0x0000007f8c9f87cc in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (cx=cx@entry=0x7f84b26400, args=..., construct=construct@entry=js::NO_CONSTRUCT) at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:470
#35 0x0000007f8c9f8a90 in InternalCall(JSContext*, js::AnyInvokeArgs const&) (cx=cx@entry=0x7f84b26400, args=...)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:497
#36 0x0000007f8c9f8af8 in js::Call(JSContext*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, js::AnyInvokeArgs const&, JS::MutableHandle<JS::Value>) (cx=cx@entry=0x7f84b26400, fval=..., fval@entry=..., thisv=..., args=..., rval=...)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:516
#37 0x0000007f8c927734 in js::fun_call(JSContext*, unsigned int, JS::Value*) (cx=0x7f84b26400, argc=<optimized out>, vp=0x7f81e1d500)
    at /build/firefox-qukfp0/firefox-49.0+build4/js/src/jsfun.cpp:1186
#38 0x0000007f8c9f886c in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (args=..., native=<optimized out>, cx=0x7f84b26400) at /build/firefox-qukfp0/firefox-49.0+build4/js/src/jscntxtinlines.h:240
#39 0x0000007f8c9f886c in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (cx=0x7f84b26400, args=..., construct=<optimized out>) at /build/firefox-qukfp0/firefox-49.0+build4/js/src/vm/Interpreter.cpp:452

It does seem like it is a javascript (ECMAscript) related error when javascript uses a CanvasRenderingContext2D object. I do not know if this is a fault of code in firefox, or if it is a fault of an external system call for rendering. The only quick workaround is to use a different browser, e.g., “chromium-browser”.

Hi AliNada,

Looks like you need to have a codec for mic and speaker. There are two ways I think you can go. using rt5659 as your codec which is native support on TX1 or bringup a new codec or adc. What kind of codec depends on your use case and bringup the codec on TX1/ASoC.( https://devtalk.nvidia.com/default/topic/960938/, this topic is bringing up the codec he selected. could be a reference for you.) Then you can use the tools in alsa-utils to play to/record from/set up your codec. Most of things you can control via the tools in alsa-utils like routing or volume … So you don’t need to deal with sysfs actually.

linuxdev, do you know of a way to make it possible to “sign in” to chromium so that sync of bookmarks, etc can take place? the browser works well and because i use it on several devices to add this instance of chromium to being able to share bookmarks, settings,etc would be nice. i get an error message "uh, ohh, the services is not available now try again latter. but i have spent many hours looking for a solution. yet, no joy However, i did want to say , as best as i have witnessed, to all involved with the last builds problem of no resume from sleep that the wake from sleep has been fixed with build 24.2 this has been a much needed function for me and i appreciate all the hard work to get it running right again. any thoughts/ideas on the current chromium sign-in problem so sync can be put back online would be worthy of company recognition for task completed. it has reached status of significant reward. yes, i would certainly create a prize of $25 donation to an individuals choice of beverage. perhaps other chromium users can chime in and also give an additional donation. join the challenge.

hello tedc
i saw the topic you have sent , i think the problem is very specific in form , or i cant pick any useful information because may be i am not that kind of expert , so simply and straight way or steps how could i use i2s to connect a mic with aux port and what components i need ,
and thanks in advance

hello Linuxdev

thanks for your informations you give , i hope if you find some sort of solution to post it right away

I am not familiar with the chromium-browser sign in/sync…are you speaking of signing in to google? If so, then it may be a network setup issue.

Describe exactly the steps to reach the chromium-browser sign in menu or command/URL required…then reproducing the issue would be possible. FYI, when I ran chromium-browser a second time, and it offered to make it the default browser, I answered yes; this resulted in getting an import ability for firefox. Although I did not have any customization of this firefox, this succeeded. I suspect you are interested in a similar feature which is via google login for importing from a remote source.

Unfortunately I do not believe the firefox issue is going to be an easy fix. The code there is very complicated, and I am not set up to build and debug firefox from source. If it is a firefox issue, then it will take some time with a report of the issue to mozilla.org. If it is a rendering bug in the L4T video driver (the failure occurs in CanvasRenderingContext2D), then it would require either an strace or ltrace to show that the related system or library call was correct or not (if not, then it was probably a version mismatch somewhere in the chain of app->library->kernel or app->kernel). If the calls to library and kernel are correct, then it would require access to the nVidia video driver source (which I do not have).

linuxdev, signing in to chromium is not the same as signing into google. to sign into chromium simply goto settings and then i think the very first option on the top left is
'sign in to chromium".
you will use your google account email but it is a totally separate process which allows you to keep your chromium settings and bookmarks saved and able to be sync’ed across all chromium/chrome installs on all devices. i think firefox offers similar but the two do not sync across firefox/chromium. anyway, if you have time and a necessary google acct i do appreciate you checking it.

It seems to be a bug in chromium-browser. I’m able to sign in under my host’s chromium-browser, but not under the JTX1’s chromium-browser. If I just go to my gmail account via chromium, it lets me sign in to that without problem on the Jetson.

I noticed that on the Jetson version I had not set up a key ring…and it wanted to add this. On my host where it works I have the key ring already set up. I don’t have this set up on Jetson because it is just for default user ubuntu. I’m thinking perhaps there is a bug where key ring must be set up first, but it fails to say this (I did not test if this would “fix” the problem, but if you go into software search and look for “key” there is a “passwords and keys” setup…try setting this up and then do the sign in again).

the keyring would be useful if the password was actually accepted by chromium as valid. that is the function of the keyring, storing valid , or accepted, passwords. in this instance the keyring has no value since if i used it to store the password chromium would still decline it. yes, i agree it is a bug in this particular install of chromium. i thought perhaps a necessary file in the install was missing or not set up correctly. anyway, whomever maintains the build would need to review the code. i thought perhaps since the source was provided by nvidia that it was in-house rather than a package from ubuntu. if that is the case i was hoping notification of the bug would be made to the responsible party. do you know if there is a bug reporting system for this build? like you, other builds i use do not have this issue so it would be good to know where exactly the bug report needs to go so maybe it can get fixed.

Almost all of what you see as source is just the source as provided by Ubuntu. Firmware specific to Jetson and binary drivers are provided by nVidia. Kernel source is provided, but is more or less just standard…nVidia has work in that kernel which it maintains, but mostly it is just a stock kernel with a custom configuration (by “stock” I mean you don’t have to patch it versus what is out in the wild).

The real problem with a fix for chromium-browser key ring issues is that the people who do maintain it may not have an arm64 platform to debug it on. I don’t know of a package for adding debug symbols without rebuilding the entire app from scratch, otherwise I’d probably add that and run it and poke around. Anyone know of a debug/symbol package for this?

interesting development this morning. i was doing a debug symbol search on synaptic and a build of chromium that had not previously been listed , appeared . it’s a 53 so fairly recent and maintained by ubuntu developers, so official. and the sign in process works. so, very happy. problem solved. thanks for your efforts on this matter, linuxdev.

I had a similar crash in Seamonkey, and the patch on this page fixed it for me:
https://bugzilla.mozilla.org/show_bug.cgi?id=1269960
Probably worth checking if it fixes the firefox crash as well.