My Cr-48 is in dev mode, so I can send the list whatever logs and config files you want. About the only thing you lose by flipping the dev switch is Netflix. That site checks the switch setting and blocks access to dev mode users. I think they are afraid someone will hack their netflix.so file ;)
Your comment about (legally) booting any kernels besides the ones signed by Google is a bit broad in scope. I believe you would void the warranty if you dual/triple boot, but Google is not going to be mad or anything. The chromium.org people are extremely helpful, and welcome people who want to hack the open source version of Chrome OS (Google's signed version). The OS mirrors the browser. Both have open source equivalents, and anyone is welcome to roll their own from the Chromium OS source tree. http://www.chromium.org/chromium-os Like I mentioned before, if you have questions about Chrome or Chromium OS, the best place to ask them is in the cros-discuss mailing list. Send a message to [email protected] to subscribe. (I posted an incorrect address earlier. oops). If subscribe via email fails, there should be join instructions on the site. Here is a link to a thread discussing rootfs verification and signed boot images: https://groups.google.com/a/chromium.org/d/topic/chromium-os-discuss/pLpblmwp5AA/discussion -- steve <http://pirk.com> On Sat, Nov 10, 2012 at 11:05 AM, Ottavio Caruso <[email protected]>wrote: > On 30 October 2012 14:08, Stuart Winter <[email protected]> wrote: > > > > I'm going to wait a month or so to see how people get on with them and > > whether there is support for it in the kernel.org kernel, as I don't use > > other people's kernels. > > So I have finally bought it and at the moment I am going to play with > it in its default mode (just browsing the web with Chrome, that is). > > In the future I'll be switching to dev mode and try to load the > Slackware minimal rootfs in a chroot and see what happens. I don't > think any of the modules or the firmware will be open-sourced, but who > knows? > > I understand Chrome devices cannot (legally) boot any kernels that are > not signed by Google so at the moment any attempt to run Slackware > will be a cheap hack. > > Typing: chrome://system I get a lot of low level info (remember > there's no full shell in standard mode. If anybody is interested I can > copy the content of dmesg or the xorg log on pastebin and link to it > from here. Let me know. > > I would then create a separate thread if I manage to get to something > useful. > _______________________________________________ > ARMedslack mailing list > [email protected] > http://lists.armedslack.org/mailman/listinfo/armedslack >
_______________________________________________ ARMedslack mailing list [email protected] http://lists.armedslack.org/mailman/listinfo/armedslack
