From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: fso-console-image problems
Date: Sat, 03 Dec 2011 16:37:34 +0000 [thread overview]
Message-ID: <4EDA504E.7070304@googlemail.com> (raw)
In-Reply-To: <201112031046.44018.GNUtoo@no-log.org>
> Instead of trying to edit the file manually, try "make xconfig" in the
> directory where the kernel is extracted(something like work/htcdream*/linux-
> leviathan*/git/ ) and do it manually trough the GUI, then save back the
> resulting defconfig, increase PR in the recipe and rebuild your console-image.
>
That as a very good advice, thank you! The versioning "magic" is
something I didn't know about (I always used to delete all related files
in the tmp/stamp directory in the futile hope that the process/steps
will be repeated at the next run).
OK, since I use rm_work, the git directory is no longer there, but I've
had the git tar archive, so unpacked it, copied defconfig, renamed it to
.config and ran "make ARCH=arm menuconfig" (I prefer ncurses myself),
then switched the appropriate option on and saved the new file. I wasn't
sure whether I should also switch the FRAMEBUFFER_CONSOLE_DETECT_PRIMARY
option as I was not sure of its meaning and whether I actually need
this, so left it as the default (empty/No). When I ran diff to see what
has been changed the following has been altered:
--- defconfig 2011-11-19 16:35:46.000000000 +0000
+++ .config 2011-12-03 15:42:13.123656047 +0000
@@ -1,7 +1,7 @@
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.32.9
-# Fri Aug 27 19:32:05 2010
+# Sat Dec 3 15:42:13 2011
#
CONFIG_ARM=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
@@ -1199,7 +1199,12 @@
#
# CONFIG_VGA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
-# CONFIG_FRAMEBUFFER_CONSOLE is not set
+CONFIG_FRAMEBUFFER_CONSOLE=y
+# CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
+CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
+# CONFIG_FONTS is not set
+CONFIG_FONT_8x8=y
+CONFIG_FONT_8x16=y
# CONFIG_LOGO is not set
CONFIG_SOUND=y
CONFIG_SOUND_OSS_CORE=y
@@ -1233,11 +1238,9 @@
CONFIG_SND_SOC=y
#
-# MSM SoC Audio support
+# SoC Audio support Qualcomm
#
CONFIG_SND_MSM_SOC=y
-CONFIG_SND_MSM_DAI_SOC=y
-CONFIG_SND_MSM_SOC_MSM7K=y
CONFIG_SND_SOC_I2C_AND_SPI=y
# CONFIG_SND_SOC_ALL_CODECS is not set
# CONFIG_SOUND_PRIME is not set
Interesting! In addition to a few extra options, the two SND_MSM_*
options shown above are now gone - don't know why.
Anyway, I copied this back to the appropriate directory and bumped the
version number, then ran bitbake again. No problems and I've had my new
image, kernel modules (recompiled) and a few other things. Installed it
and fastbooted my phone. The screen appeared this time - rotated as well
- and I've had my login prompt. Brilliant!
Duly logged in, but there were a few further problems:
1. The keyboard I now have is completely unusable as the "alt" register
(the blue row of keys) is completely unusable/inaccessible with the
exception of the top row (where the numbers are). That means I cannot
type/use vital keys like the pipe symbol ('|'), dash ('-') etc. There is
also no "repeat" - i.e. when I press a key and keep pressing it, it
doesn't continue typing the same key. is there any way I could fix this?
2. My ssh login is also problematic - when I try to log in from the PC
host (via usb) this time I get the following error on that (PC) end:
"PTY allocation request failed on channel 0". Don't know why that is,
any ideas?
I cannot properly scroll/see what is happening on the phone system and
neither can I see any of the log files as the keyboard is all screwed
up, so I can't post any of these file in order to further help resolve
the above issues.
next prev parent reply other threads:[~2011-12-03 16:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 1:57 fso-console-image problems Mr Dash Four
2011-12-02 10:20 ` Denis 'GNUtoo' Carikli
2011-12-02 14:08 ` Mr Dash Four
2011-12-02 14:52 ` Martin Jansa
2011-12-02 15:12 ` Mr Dash Four
2011-12-02 15:46 ` Martin Jansa
2011-12-02 16:20 ` Mr Dash Four
2011-12-02 16:25 ` Martin Jansa
2011-12-02 17:27 ` Denis 'GNUtoo' Carikli
2011-12-02 17:42 ` Mr Dash Four
2011-12-02 20:06 ` Mr Dash Four
2011-12-02 22:24 ` Denis 'GNUtoo' Carikli
2011-12-02 23:35 ` Mr Dash Four
2011-12-02 23:50 ` Mr Dash Four
2011-12-03 9:46 ` Denis 'GNUtoo' Carikli
2011-12-03 16:37 ` Mr Dash Four [this message]
2011-12-03 16:52 ` Martin Jansa
2011-12-03 17:47 ` Mr Dash Four
2011-12-03 18:03 ` Martin Jansa
2011-12-03 18:35 ` Mr Dash Four
2011-12-04 12:39 ` Mr Dash Four
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EDA504E.7070304@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=GNUtoo@no-log.org \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox