#! crunchbang pruning

crunchbang is nicely setup, but as per my previous post it still has bloatwares lurking about.

i'll expand this post further, but meanwhile here's something to-do:

remove gdm
trayer to replace {...}
rxvt + tmux to replace terminator

when i need to be more productive and not get distracted:

add ratpoison
add opera

Display XML/HTML code tags in Blog posts

I had trouble displaying my previous post, containing xml tags. This blog post here helped me get over my difficulty. Basically you need to transcode "<" and ">" with "&lt;" and "&gt;" respectively, or they will be rendered as code tags and your post will not be displayed as expected.

I used centricle's online encode/decode tool to easily convert my code, rather than manually transcode, a rather cumbersome task. I still had to manually convert leading spaces.

#! crunchbang openbox menus

#! default menu opens with a right click on desktop. This menu is static and needs to be maintained by the user. Middle click opens an auto-populated window/desktop menu. Left click has no associated menu.

Debian menu, although installed, is not configured/enabled. This is what I targetted. Left click -> Debian menu.

I kept the right click and middle click menus undisturbed, but added the debian-menu to the left click.

Confirm debian-menu exists.
$ dpkg -l menu

$ vi .config/openbox/rc.xml

First, we enable the Debian menu. Look for this section, and uncomment the following lines, as under:

<!-- default menu file (or custom one in $HOME/.config/openbox/) -->
<!-- system menu files on Debian systems -->
<file>/var/lib/openbox/debian-menu.xml</file>
<file>debian-menu.xml</file>
<file>menu.xml</file>


Next, we trigger the Debian menu on Left click. In the same file, look for this section, and add entry for left click, as under.

<context name="Root">
  <!-- Menus -->
  <mousebind button="Left" action="Press">
    <action name="ShowMenu">
      <menu>/Debian</menu>
    </action>
  </mousebind>
  <mousebind button="Middle" action="Press">
    <action name="ShowMenu">
      <menu>client-list-combined-menu</menu>
    </action>
  </mousebind>
  <mousebind button="Right" action="Press">
    <action name="ShowMenu">
      <menu>root-menu</menu>
    </action>
  </mousebind>
</context>


Save the file, and restart Openbox. Or
$ openbox --reconfigure

Left click anywhere on the desktop... Voila!

We can also configure a Keyboard Shortcut, like the other menus activated by Super (aka Windows) key combinations.
Super+Space Main Menu
Super+Tab Client Menu


Super+Menu Debian Menu
We will use the Menu key, found to the right of SpaceBar among the right AltGr/Ctrl keys on my GB keyboard. Your keyboard might have a slightly different layout. If you can't find the Menu key, or don't want to use the Menu key, simply substitute your preferred key wherever I mention the Menu key.

So, we reopen the same file again.
$ vi .config/openbox/rc.xml

And look for the following section, to add an entry for Debian Menu among the othe menu keybindings, as under:

<keybind key="W-Menu">
  <action name="ShowMenu">
    <menu>/Debian</menu>
  </action>
</keybind>
<keybind key="W-Tab">
  <action name="ShowMenu">
    <menu>client-list-combined-menu</menu>
  </action>
</keybind>
<keybind key="W-space">
  <action name="ShowMenu">
    <menu>root-menu</menu>
  </action>
</keybind>


Now save the file and restart OpenBox. Hit Super+Menu from anywhere, not just in front of an empty desktop, but even when your desktop might be hidden under various windows. No need to minimise all windows to find some space to click to get your Menu!

Have fun...!

#! crunchbang 10 statler r20110207

For a while now, I have been hearing and thinking about crunchbang linux, or #! as the community calls it. So finally, I decided to dive in and install crunchbang-10-20110207-openbox-i686 on my spare laptop.

I have been recommending Linux Mint Debian XFCE lately to newbies. I am rethinking that now. It seems LMDX still has a lot of dependencies on Gnome and other bloatwares hanging on from its legacy days. For example, the XFCE Edition uses Gnome-Terminal rather than XFCE-Terminal. IMHO, that defeats the purpose of not wanting to use Gnome.

#! seems to be smoother and slicker at first glance. I like what I see, although the initial install used almost 2G of diskspace. There is a lot of gnome/etc bloatware which shouldn't have made it to this supposedly minimalist openbox distribution. Mint seems not much worse compared to this. (But compare this to my debian-wheezy laptop setup, with everything I need, on about 650M diskspace!!)

dd if=crunchbang-10-20110207-openbox-i686.iso of=/dev/{usb-drive}
was sufficient and simple to make a usb key for testing or install.

For some strange reason, I had trouble booting #! cd/usb. Apparently, it could be due to my screen - max resolution 1024x768. I almost gave up before I understood the issue. Wonder who the #! developers are targetting?

So I edit the grub boot menu, and append vga=773, and only then was I able to boot #! cd/usb to test or install. The install was fairly smooth with no major concerns, except that the drive partitioner seemed to be creating partitions not ending on cylinder boundaries. I reinstalled, after manually partitioning my drive with fdisk.

So, now I have a pristine install of #! waiting to be devoured.

Initial tasks were to update the system:
$ sudo apt-get update
$ sudo apt-get upgrade


#! /etc/apt/sources.list points to German servers, instead of UK ones, which lagged, due to about twice the network distance/time. It was fairly simple to replace de with uk. Since, #! tracks debian-stable (squeeze), and the installer contents are about 8mths old, about ~250M of initial upgrades were waiting. Squeeze is stable and updates shouldn't be frequent, except the security ones.

Then, I installed some of my missing favourites:
- rdate
- localepurge
- ncdu
- tmux
- most

Keep an eye here for my #! adventures... :-)

cyanogenmod 7.1.0

Finally, after a long wait, CM 7.1 has been released for my ZTE Blade. The last (supposedly) stable release CM 7.0.3 wasn't that stable. 7.1.0-RC1, the subsequent Release Candidate was more stable. Even this had Battery drain issues, Apps leaking, GPS reboots, etc.

Check out the CM Change Log. I am well pleased with this release. It seems stable, and I have a nice feeling about this. My battery is still going strong (65%) after 2 days, although admittedly I haven't used it much. Before this, the phone would have died in two days.

Ideally, I would like to get out of the Android loop, and would like emdebian or a similar mainstream OS to take over. Android seems getting deeper in the Java sh!t and other patent issues, and becoming bloatware with each update. Google Apps are being closed source and very network/memory/disk hog with consequent battery drain. All I need is my contacts/calendar to be cloud-synced on an ad-hoc basis. I can get rid of all other Google Apps from my phone.

Opera cpu/memory leaks and Flash

i have been a long term user of opera, as i like it's light resource demands. one particular concern has been the long running issue of cpu/memory leaks. opera seems to continue consuming cpu/memory as it runs longer. so you need to periodically *restart* it. this problem exacerbates after visiting websites with flash. sometimes, it gets so bad, that i have to kill -9 ... i usually disable plugins, or only enable on-demand. but there are times when i need flash.

$ ps ux | grep opera
gives some clue. seems to me that opera plugin handling is badly written, when I see
.../lib/opera//operapluginwrapper
.../lib/opera//operaplugincleaner
note the double slashes in the path, instead of a single slash.

i found some others having similar problems. perhaps they might help. although, they seem to be historical issues, i still have problems with opera 11.51, the latest release.

>> extremely high CPU usage by opera plugin wrapper process http://ubuntuforums.org/showthread.php?t=1288274

>> build 4464 (intel linux) and operapluginwrapper http://www.archivum.info/opera.beta/2009-07/00030/build-4464-(intel-linux)-and-operapluginwrapper.html

prism p54 wireless usb

each time i tried to use this, i have had to trawl through and research quite a bit. i have just had to do so again. so i am documenting this here.

download the latest version of your softmac firmware from
http://daemonizer.de/prism54/prism54-fw/

identify what it should be called, and where the firmware needs to go.

openwrt backfire asked for /lib/firmware/isl3886usb.

alternatively, on a debian derivative, get the firmware-linux-nonfree. i don't like this, as it contains a lot of garbage, none of which i use except one single item.

debian net-install

(32bit) http://ftp.uk.debian.org/debian/dists/testing/main/installer-i386/current/images/netboot/debian-installer/i386/
(64bit) http://ftp.uk.debian.org/debian/dists/testing/main/installer-amd64/current/images/netboot/debian-installer/amd64/

substitute uk with {your country-code}, and testing with {stable/unstable}, as per your preference.

download these two files - linux and initrd.gz - to your bootable usb (or cd) and boot.

my usb bootloader is extlinux
# vi /boot/extlinux/extlinux.conf
LINUX linux
INITRD initrd.gz
APPEND root=/dev/null vga=791 priority=low hw-detect/start_pcmcia=false eject=false install-recommends=false rescue=true language=en country=GB locale=en_GB.UTF-8 time/zone=Europe/London

install directly from internet, downloading only the latest updates of those files that you actually need. no need to waste time/bandwidth downloading the whole install cd. you don't need all of it. and then, you still need to download all the latest updates again.

if you are installing to multiple computers, use a caching proxy and automated net-install for the most efficient way to install linux. you could even net-boot, serving these two files over tftp.
or simply walk around booting each computer with your cd/usb into ram, so your cd/usb media is not locked in there for the duration of the entire install. after initial boot, eject your cd/usb, and do the same to the next computer.

my e100 nic was not included in the net-installer, as that is presumably proprietary closed source, violating dfsg (debian free software guidelines).
check-missing-firmware was looking for
/media/firmware-linux-non-free_0.33_all.deb

debian wiki has instructions at
http://wiki.debian.org/Firmware#Firmware_during_the_installation.

to download the firmware (.tar.gz or .zip) and uncompress to extract the required file(s)
http://cdimage.debian.org/cdimage/unofficial/non-free/firmware/testing/current/

openwrt internet radio

Since my openwrt is on a thinclient with embedded soundcard, I don't need any extra hardware. A set of unpowered speakers are enough. Now I have a router playing internet radio stations!

It can be controlled remotely for changing stations, etc. from
- client installed on PC or Android
- web browser on any device

The how-to link below is a good start. I might add detailed instructions, if needed.
http://tomatousb.org/doc:play-audio-with-usb-audio-adapter

openwrt backfire x86 install

vision: portable internet router, to carry on my travels, or use at home.
openwrt on a portable (thin-client/netbook) device. internet sourced from ethernet-port or 3g-dongle or wifi. internet served via ethernet-port or wifi.

latest openwrt x86 sources:
http://downloads.openwrt.org/backfire/{latest}/x86_generic/
download openwrt-x86-generic-combined-ext2.img.gz

$ gunzip openwrt-x86-generic-combined-ext2.img.gz
# dd if=openwrt-x86-generic-combined-ext2.img of=/dev/sda {disk not partition}
# e2fsck /dev/sda1
# e2fsck /dev/sda2
# reboot


i could not telnet or ssh. but discovered the web interface http://192.168.1.1 up and open, ie no password. now i could set a password, and ssh into my openwrt. all systems go...

ref: my previous post on this topic needed an update, and instead of rewriting the whole thing, i decided to create a new post.

http://open-wrt.ru/forum/viewtopic.php?id=20478
https://forum.openwrt.org/viewtopic.php?id=31695
http://macbruins.wordpress.com/2011/09/01/easy-live-usb-for-x86-openwrt/

linux roadmap

just read a comment by Tomáš Pospíšek in a blog. I have been thinking about this recently and couldn't have put it much better. So I quote verbatim:

I can see that additional daemons running idle in the background (“background”, for “the casual” user and D-Bus seem lately to be indicative of “without any no documentation at all”) are even further cluttering up the system. I can also see, that it will add a few layers of communications, and hard to see protocols. Unfortunately I fail to see, what good such a daemon is good for at all.

$ ps auxw|wc
186 2242 18356


Very far from KISS. And since KISS is also a aesthetic system quality, having 186 processes running on a plain desktop system with only 11 user visible applications is quite ugly.

I’d argue that one of the main dangers of Linux is that it is acquiring all the bad properties that Windows had in the past: nothing is documented, nothing is transparent, everything is binary or in some undocumented protocol that can’t be dumped into a text editor, nothing is meant to be touched by the user directly, but only through some GUI thing( which connects to a message bus, which connects to a daemon, which changes some registry, which triggers some helper, that … etc.)

local.prop

i used to change my /system/build.prop, each time i found a hack. frequent changes were cumbersome, as /system partition is read-only. also, any rom updates would wipe that clean.

/data/local.prop is a more efficient way of keeping all these hacks together, and maintaining them across rom updates. also, /data partition is mounted read-write. so i can push the changes anytime.

i will keep this post updated with my current settings. if you can suggest any others or better settings, please do.


# set locale and date format
ro.product.locale.region=GB
ro.com.android.dateformat=dd-MM-yy

#ro.ril.hsxpa=1
#ro.ril.gprsclass=10

#wifi.supplicant_scan_interval=15

# Smaller number = smaller icons, text, etc.
#ro.sf.lcd_density=240 #default
#ro.sf.lcd_density=220 #medium
#ro.sf.lcd_density=200 #small

# This is a high density device with more memory
# so larger vm heaps for it.
dalvik.vm.heapsize=32m

# set default sound
ro.config.ringtone=Pyxis.ogg
ro.config.notification_sound=Altair.ogg
ro.config.alarm_alert=Alarm_Beep_02.ogg

# disable boot animation, saving time and battery
ro.kernel.android.bootanim=0
debug.sf.nobootanimation=1

# Render UI through GPU instead of CPU
# Comment out if this causes laggy UI (it should speed up UI)
debug.sf.hw=1

# Battery Savings (Sleep Mode)
ro.ril.disable.power.collapse=0
pm.sleep_mode=1

# disable debugger
ro.kernel.android.checkjni=false
dalvik.vm.checkjni=false

# When moving through zones or losing signal
# having a delay smooths out constant disconnects and reconnects
# which in turn saves a ton of battery life!
ro.mot.eri.losalert.delay=1000

# Allows the system to start at a lower heap size and rank up as needed.
dalvik.vm.startheapsize=8m

#use black buttons
ro.config.BlackButton=true

# disable camera shutter sound
persist.camera.shutter.disable=1

fennec: firefox mobile

The Mozilla Blog caught my eye with a post on Firefox Mobile for Android. http://blog.mozilla.com/blog/2011/08/16/firefox-for-android-has-a-new-look-and-tools-that-empower-developers-to-build-rich-mobile-web-experiences/

Exploring from there, I reached here: http://mozilla.com/mobile

The section Developer Tools says: You can install the mobile version of Firefox to your desktop computer in order to test, provide feedback, and build add-ons.

Which made me wonder, if perhaps I could use this on my low-end laptop running debian wheezy. The latest portable version for each OS is available as a zip from here: http://ftp.mozilla.org/pub/mozilla.org/mobile/releases/latest/

The last time I looked at Firefox Mobile for Android was a while ago. My initial thoughts were of Mozilla developing bloatware for thin clients. I didn't even want to try it! I think Mozilla is still paying lip-service to a mobile browser... It doesn't hold a candle to Opera Mini or any of the other browsers that I've tried before.

magic display

invert display:
$ xcalib -i -a

rotate display:
$ xrandr -o left
$ xrandr -o right
$ xrandr -o inverted
$ xrandr -o normal

mint xfce time & sync

for default installs out of the box, time seems to be an hour out. when i tried to configure internet sync, i got a message that something was not installed, or some such thing. no other details including what needs be installed.

utc seems to be on. to disable it:

/etc/default/rcS
UTC=no


to-do:
install/configure ntp to work with mint clock sync.

update:

# apt-get install ntp

now i can configure internet sync.

mint xfce menu

mint updates break mint's elegant xfce menu. first login asks whether you want to keep, migrate or replace the old menu. it doesn't matter what you choose. apparently the old menu in incompatible with the new update.

i did not want to manually code the xfce menu, to avoid incompatibilities with future mint updates. reluctantly, i had to use the memory-hungry but presentable gnome-menu instead.

edit: just discovered the bug and solution here:
https://bugs.launchpad.net/linuxmint/+bug/806859
http://forums.linuxmint.com/viewtopic.php?t=74615

linux mint debian xfce

http://blog.linuxmint.com/?p=1725
very impressed with the neat and sleek looks, light requirements and speed, i'm starting to recommend this over ubuntu, to my newbie-linux windows converts.

http://www.linuxmint.com/torrent/linuxmint-xfce-201104-dvd-32bit.iso.torrent
not impressed that the only way to install is via dvd only. mint could learn from debian in having a minimal netinstall, and pulling required packages after basic install.

installation was a breeze. very clean. system reboot. restart is quite quick. desktop looks elegant.

the first update+upgrade pulls in quite a lot, and makes very noticable changes.

cm6 kernel issues

http://android.modaco.com/topic/328661-cm6-kernel-issues/page__view__findpost__p__1548363

some observations and comments from me, based on boot logs from my phone

<5>[0, swapper] [ 0.000000] Kernel command line: mem=128M  console=ttyMSM2,9600n8 androidboot.hardware=qcom console=ttyUSBCONSOLE0 androidboot.console=ttyUSBCONSOLE0 androidboot.localproppath=t-mobile/uk
<3>[0, swapper] [ 0.000000] Unknown boot option `androidboot.hardware=qcom': ignoring
<3>[0, swapper] [ 0.000000] Unknown boot option `androidboot.console=ttyUSBCONSOLE0': ignoring
<3>[0, swapper] [ 0.000000] Unknown boot option `androidboot.localproppath=t-mobile/uk': ignoring

i think the kernel boot options weren't working with the original t-mobile/huawei supplied roms either. these seem to be some left-over garbage from older development/testing labs, which haven't been cleansed before release.

normal users certainly wouldn't be using serial consoles or usb consoles, more so for mobile phones. these are used mostly in embedded devices.

<6>[1, swapper] [ 0.272906] ACPU running at 528000 KHz
<6>[1, swapper] [ 0.272933] Id CPU-KHz PLL DIV AHB-KHz ADIV AXI-KHz D0 D1 D2 U0 U1 U2
<6>[1, swapper] [ 0.272966]  0   19200  -1   1   19200 1   30720 -1 -1 -1  4  1  3
<6>[1, swapper] [ 0.272998]  1  120000   1   8   60000 2   61440 -1 -1 -1  4  5  6
<6>[1, swapper] [ 0.273028]  2  122880   0   2   61440 2   61440 -1  1 -1  4  5  6
<6>[1, swapper] [ 0.273058]  3  176000   2   6   88000 2   61440  2  1 -1  4  5  6
<6>[1, swapper] [ 0.273088]  4  245760   0   1   81920 3   61440  2  1  3 -1  7  6
<6>[1, swapper] [ 0.273120]  5  320000   1   3  107000 3  120000  2  1  3 -1  7  9
<6>[1, swapper] [ 0.273150]  6  352000   2   3   88000 4  120000  2  1  3 -1  7 10
<6>[1, swapper] [ 0.273181]  7  480000   1   2  120000 4  120000  4  5  6 -1 -1 16
<6>[1, swapper] [ 0.273211]  8  528000   2   2  132000 4  160000 -1  5  6 -1 -1 16
<6>[1, swapper] [ 0.273243]  9  576000   2   2  132000 4  160000 -1  5  6 -1 -1 16
<6>[1, swapper] [ 0.273273] 10  595200   2   2  132000 4  160000 -1  7  6 -1 -1 16
<6>[1, swapper] [ 0.273305] 11  614400   2   2  132000 4  160000 -1  7  8 -1 -1 16
<6>[1, swapper] [ 0.273335] 12  633600   2   2  132000 4  160000 -1  7  8 -1 -1 16
<6>[1, swapper] [ 0.273366] 13  652800   2   2  132000 4  160000 -1  7  8 -1 -1 16
<6>[1, swapper] [ 0.273396] 14  672000   2   2  132000 4  160000 -1  7  8 -1 -1 16
<6>[1, swapper] [ 0.273426] 15  691200   2   2  132000 4  160000 -1  7  8 -1 -1 16
<6>[1, swapper] [ 0.273458] 16  710400   2   2  132000 4  160000 -1  7  8 -1 -1 -1
<6>[1, swapper] [ 0.273483] 13 scaling frequencies supported.
shows the cpu clock. cpu also supports the various scaling frequencies requested by this kernel. great!

<3>[1, swapper] [ 0.273766] vendor:t-mobile,country:uk
<3>[1, swapper] [ 0.273785] USB setting is TMO
i don't think this should be set by the kernel. this is more a userspace setting.
as is the next bit.

<6>[1, swapper] [ 0.357926] cfg80211: Using static regulatory domain info
<6>[1, swapper] [ 0.357968] cfg80211: Regulatory domain: US
<6>[1, swapper] [ 0.357990]  (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
<6>[1, swapper] [ 0.358018]  (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
<6>[1, swapper] [ 0.358043]  (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
<6>[1, swapper] [ 0.358070]  (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
<6>[1, swapper] [ 0.358095]  (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
<6>[1, swapper] [ 0.358120]  (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
<6>[1, swapper] [ 0.358145]  (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
<6>[1, swapper] [ 0.358173] cfg80211: Calling CRDA for country: US
same as above.

<6>[1, swapper] [ 0.457945] smd probe
<6>[1, swapper] [ 0.457985] smd_core_init()
<6>[1, swapper] [ 0.458116] smd_core_init() done
<6>[4, events/0] [ 0.458565] smd_alloc_channel() 'DS' cid=0
<3>[1, swapper] [ 0.459233] _smem_log_init: no power log or log_idx allocated, smem_log disabled
<6>[4, events/0] [ 0.460298] smd_alloc_channel() 'DIAG' cid=1
<6>[4, events/0] [ 0.461438] smd_alloc_channel() 'RPCCALL' cid=2
<6>[4, events/0] [ 0.462358] smd_alloc_channel() 'DATA1' cid=7
<6>[4, events/0] [ 0.463461] smd_alloc_channel() 'DATA2' cid=8
<6>[4, events/0] [ 0.464556] smd_alloc_channel() 'DATA3' cid=9
<6>[4, events/0] [ 0.465650] smd_alloc_channel() 'DATA4' cid=10
<6>[4, events/0] [ 0.466716] smd_alloc_channel() 'DATA5' cid=11
<6>[4, events/0] [ 0.467663] smd_alloc_channel() 'DATA6' cid=12
<6>[4, events/0] [ 0.468575] smd_alloc_channel() 'DATA7' cid=13
<6>[4, events/0] [ 0.469706] smd_alloc_channel() 'DATA11' cid=17
<6>[4, events/0] [ 0.471493] smd_alloc_channel() 'DATA5_CNTL' cid=38
<6>[4, events/0] [ 0.472596] smd_alloc_channel() 'DATA6_CNTL' cid=39
<6>[4, events/0] [ 0.473586] smd_alloc_channel() 'DATA7_CNTL' cid=40
<6>[1, swapper] [ 0.476328] SMD Control Port Driver Initialized.
<6>[1, swapper] [ 0.478485] SMD: ch 2 CLOSED -> OPENING
<6>[1, swapper] [ 0.478610] SMD: ch 2 OPENING -> OPENED
<3>[1, swapper] [ 0.481250] Using very old AMSS modem firmware.
<3>[1, swapper] [ 0.481375] Using very old AMSS modem firmware.
i don't know, what is happening here...

<6>[1, swapper] [ 0.482580] ADSP: rs3000000a:00010000 -- 0
<3>[261, rpcrouter] [ 0.512656] rpcrouter: Server create rejected, version = 0, program = 30000012
<3>[261, rpcrouter] [ 0.512711] rpcrouter: Server create rejected, version = 0, program = 3000fe00
<3>[261, rpcrouter] [ 0.523406] rpcrouter: Server create rejected, version = 0, program = 30000066
<6>[266, krpcserversd] [ 0.524930] RPC_TIME_TOD_SET_APPS_BASES:
<6>[266, krpcserversd] [ 0.524950]  tick = 164384
<6>[266, krpcserversd] [ 0.524960]  stamp = 794911488
<4>[266, krpcserversd] [ 0.525030] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
i'm not sure, but i think we haven't selected the correct rtc drivers

<4>[1, swapper] [ 1.407706] smc91x: not found (-19).
<6>[1, swapper] [ 1.408531] rmnet0 (): not using net_device_ops yet
<6>[1, swapper] [ 1.409673] rmnet1 (): not using net_device_ops yet
<6>[1, swapper] [ 1.410958] rmnet2 (): not using net_device_ops yet
not sure, wifi???
/
<3>[1, swapper] [ 1.555413] msm_i2c msm_i2c.0: Error during data xfer (-5)
<6>[1, swapper] [ 1.558114] msm_nand: phys addr 0xa0a00000 dmac 0x7
<6>[1, swapper] [ 1.558188] allocated dma buffer at ffa2e000, dma_addr 17aee000
<6>[1, swapper] [ 1.558593] ONFI probe : CRC Check failed on ONFI Parameter data 
<6>[1, swapper] [ 1.558689] status: e00020
<6>[1, swapper] [ 1.558709] nandid: 5510baad maker ad device ba
this might potentially cause us troubles later somewhere else.
have we got the sizes correctly identified? it seems so down the later boot stages.

<6>[1, swapper] [ 1.558731] Found a supported NAND device
<6>[1, swapper] [ 1.558749] NAND Id  : 0x5510baad
<6>[1, swapper] [ 1.558764] Buswidth : 16 Bits 
<6>[1, swapper] [ 1.558779] Density  : 256 MByte
<6>[1, swapper] [ 1.558794] Pagesize : 2048 Bytes
<6>[1, swapper] [ 1.558809] Erasesize: 131072 Bytes
<6>[1, swapper] [ 1.558826] Oobsize  : 64 Bytes
<6>[1, swapper] [ 1.558841] CFG0 Init  : 0xa85408c0 
<6>[1, swapper] [ 1.558858] CFG1 Init  : 0x0004745e 
<6>[1, swapper] [ 1.558874] ECCBUFCFG  : 0x00000203 
<5>[1, swapper] [ 1.558906] Creating 6 MTD partitions on "msm_nand":
<5>[1, swapper] [ 1.558938] 0x000002600000-0x000002880000 : "boot"
<5>[1, swapper] [ 1.561813] 0x000002880000-0x000008c80000 : "system"
<5>[1, swapper] [ 1.563826] 0x000008c80000-0x00000e6c0000 : "userdata"
<5>[1, swapper] [ 1.565893] 0x00000e6c0000-0x00000fac0000 : "cache"
<5>[1, swapper] [ 1.567986] 0x00000fac0000-0x00000ff80000 : "recovery"
<5>[1, swapper] [ 1.570023] 0x00000ff80000-0x000010000000 : "misc"
<6>[1, swapper] [ 1.572903] msm_hsusb_rpc_connect: rpc connect success vers = 10001
<6>[1, swapper] [ 1.572956] msm_chg_rpc_connect: connected to rpc vers = 10001
see previous comment

<6>[1, swapper] [ 1.573163] usb_set_composition: composition set to product id = 1501
<6>[1, swapper] [ 1.573194] phy info:(2)
<6>[1, swapper] [ 1.573348] usb_probe() io=c8874000, irq=47, dma=ffa2f000(17bd0000)
<6>[1, swapper] [ 1.581601] msm_hsusb_reset_rework_installed: rework: (16777216)
<6>[1, swapper] [ 1.581644] usb_probe: reset rework is installed
<6>[1, swapper] [ 1.581954] Created the sysfs entry successfully 
<6>[1, swapper] [ 1.584379] usb_function_register: name = 'adb',  map = 3
<6>[1, swapper] [ 1.585599] usb_function_register: name = 'mass_storage',  map = 2
<6>[1, swapper] [ 1.586353] usb_function_register: name = 'diag',  map = 4
<6>[1, swapper] [ 1.588123] usb_function_register: name = 'modem',  map = 0
<3>[1, swapper] [ 1.588168] usb_function_register: unsupported function = nmea
<3>[1, swapper] [ 1.588193] gs_module_init: cannot register Function driver, ret = -22
<3>[1, swapper] [ 1.588224] usb_function_register: unsupported function = ethernet
<6>[1, swapper] [ 1.588244] cdcecm init:usb function register failed 
<3>[1, swapper] [ 1.591368] usb_start: pm_app_rpc connect failed
<6>[4, events/0] [ 2.052736] msm_chg_usb_i_is_not_available
usb driver issues

<6>[568, usb_work] [ 2.859093] msm_chg_usb_i_is_available
<3>[1, swapper] [ 2.859831] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 2.860014] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 2.860171] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 2.860323] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 2.860653] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 2.860823] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 2.860978] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 2.861129] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 2.861281] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 2.861428] msm_i2c msm_i2c.0: Error during data xfer (-5)
<4>[1, swapper] [ 2.861493] cpt_ts: probe of 0-000a failed with error -5
<3>[1, swapper] [ 3.164484] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.164694] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.164858] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.165013] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.165161] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.165308] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.165453] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.165601] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.165748] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.165896] msm_i2c msm_i2c.0: Error during data xfer (-5)
<4>[1, swapper] [ 3.165959] melfas-ts: probe of 0-0022 failed with error -5
<3>[1, swapper] [ 3.267109] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.267299] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.267458] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.267609] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.267758] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.267904] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.268048] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.268194] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.268339] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.268484] msm_i2c msm_i2c.0: Error during data xfer (-5)
is this due to a potential size mismatch?

<4>[1, swapper] [ 3.268521] no cypress_ts device
<4>[1, swapper] [ 3.268533]  <4>cypress-innolux-ts: probe of 0-0025 failed with error -5
<6>[1, swapper] [ 3.273229] input: gsensor as /devices/virtual/input/input1
<6>[1, swapper] [ 3.274794] gs_probe: Start gs_adixl345  in polling mode
<3>[1, swapper] [ 3.275619] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.275659] i2c_smbus_write_byte_data failed
<3>[1, swapper] [ 3.275681] i2c_smbus_write_byte_data failed
<4>[1, swapper] [ 3.275733] gs_st: probe of 0-001d failed with error -5
<3>[1, swapper] [ 3.276488] msm_i2c msm_i2c.0: Error during data xfer (-5)
<3>[1, swapper] [ 3.276533] i2c_smbus_write_byte_data failed d
<4>[1, swapper] [ 3.276584] freescale: probe of 0-001c failed with error -5
driver issues

<3>[1, swapper] [ 3.295698] mmc0: No card detect facilities available
<6>[1, swapper] [ 3.296569] mmc0: Qualcomm MSM SDCC at 0x00000000a0400000 irq 24,0 dma 8
<6>[1, swapper] [ 3.296606] mmc0: 8 bit data mode disabled
<6>[1, swapper] [ 3.296626] mmc0: 4 bit data mode enabled
<6>[1, swapper] [ 3.296643] mmc0: polling status mode disabled
<3>[1, swapper] [ 3.297231] mmc1: No card detect facilities available
<6>[1, swapper] [ 3.298456] mmc1: Qualcomm MSM SDCC at 0x00000000a0500000 irq 26,0 dma 8
<6>[1, swapper] [ 3.298494] mmc1: 8 bit data mode disabled
<6>[1, swapper] [ 3.298516] mmc1: 4 bit data mode enabled
<6>[1, swapper] [ 3.298533] mmc1: polling status mode disabled
??? card seems to be working though...

<6>[1, swapper] [ 3.311463] ALSA device list:
<6>[1, swapper] [ 3.311499]   No soundcards found.
??? sound seems to be working...

<6>[1, swapper] [ 3.321028] clock_late_init() disabled 17 unused clocks
<6>[1, swapper] [ 3.323653] input: msm-handset as /devices/virtual/input/input4
<3>[1, swapper] [ 3.324371] hs_rpc_cb_init: couldn't open rpc client with version 2 err -113
<3>[1, swapper] [ 3.324419] hs_rpc_cb_init: couldn't open rpc client with version 1 err -113
<3>[1, swapper] [ 3.324439] hs_rpc_init: failed to initialize rpc client
???

<4>[1, swapper] [ 4.079599] Warning: unable to open an initial console.
<3>[1, init] [ 4.452036] init: cannot open '/initlogo.rle'
:-)
i still get the pink t-mobile logo though... :-(

<3>[1, init] [   14.845796] init: service 'console' requires console
<3>[1, init] [   15.158059] init: cannot find '/system/bin/port-bridge', disabling 'port-bridge'
dependency issues from earlier boot stages

<3>[1, init] [   15.229979] init: cannot find '/system/bin/syncsdr', disabling 'syncsdr'
<6>[1206, rild] [   15.314119] warning: `rild' uses 32-bit capabilities (legacy support in use)
<3>[1, init] [   15.656818] init: untracked pid 1265 exited

<4>[266, krpcserversd] [   17.200006] ######### report_hs_key ###### -1
<3>[266, krpcserversd] [   17.200031] report_hs_key: No mapping for remote handset event 120
<6>[1215, mediaserver] [   17.201186] snd_set_volume 3 0 7
<4>[266, krpcserversd] [   17.201716] ######### report_hs_key ###### -1
<3>[266, krpcserversd] [   17.201749] report_hs_key: No mapping for remote handset event 156
<4>[266, krpcserversd] [   22.105078] ######### report_hs_key ###### -1
<3>[266, krpcserversd] [   22.105116] report_hs_key: No mapping for remote handset event 136
???

hopefully, this might be useful in further kernel compiles.

kernel hacking

... Continued from previous post: Modified kernel with netfilter enabled for droidwall

antonio, i'm looking at both the kernels, and i think your kernel is too big, and that's why we get a write error at the end. since, it hasn't completely written, the boot can't find the kernel intact. if you can reduce your kenel size, i think that should solve the problem.

AntonioPT: Yeah my latest kernel does not work in a U8220 (only in 8230). The latest working kernel is from commit 9795cb6.

I'm sorry for not being around in the forums helping people out and working on the .29 and the .32 kernel port.

http://android.modaco.com/topic/328661-cm6-kernel-issues/page__view__findpost__p__1548291

antonio replied back in another thread to confirm that his "commit 9795cb6" kernel should work on u8220.

i have just flashed that kernel, and tested droidwall. everything seems to be working so far. i'll recommend using this kernel for its frewall support with netfilter enabled.

this kernel is much smaller, whereas his latest kernel is much bigger than the standard u8220 kernel. this leads me to suspect that kernel size bigger than the actuall flash will fail. i'll do a few more tests and report here...

Modified kernel with netfilter enabled for droidwall

http://android.modaco.com/topic/328661-cm6-kernel-issues/page__view__findpost__p__1548175

AntonioPT: My modified kernel enables netfilter owner module for droidwall support. Download boot.img from here (it's in the prebuilt folder). Flash it with fastboot.

I flashed Antonio's boot.img.
$ sudo fastboot flash boot /tmp/boot.img
sending 'boot' (2596 KB)... OKAY
writing 'boot'... FAILED (remote: flash write failure)

$ sudo fastboot reboot


My phone boots back into fastboot blue-screen, and at the end, I see this message
CANNOT READ RAMDISK IMAGE

I can't boot up my phone now...
Please someone help. URGENT!!!

most popular posts