Jump to content

An experimental CM7 Kernel


Guest t0mm13b

Recommended Posts

Guest johnsmithx

A bit off topic, but it is strange that the new accelerometer works in Ginger Stir Fry considering that kernel does not appear to have support for the newer sensors

In reality GSF kernel of course does have support otherwise it wouldn't have worked. It has the very same "multisensor" driver as the 20110624 branch CM kernel does have, even including those grammar mistakes ("gsenors" etc.).

So there is really nothing to fix in any kernel. I backported this driver to the previous CM kernel which I am using, so even there is no problem.

And no problem is in CM itself (except that cosmetic nonsense accelerometer name), so nothing to fix there either.

Just obsolete incompatible proprietary files.

Link to comment
Share on other sites

Guest DB_Runner

with the new kernel my phone reboots when i plugin the OTG cable

my test setting: Blade -- powered USB Hub --- USB Stick/Mouse/Keyboard

Link to comment
Share on other sites

Guest FelixL

<6>[08-05 18:27:00.098085] ID -> (B)

<6>[08-05 18:27:02.352298] ID -> (A)

<6>[08-05 18:27:02.358060] [4: events/0]msm_hsusb_host msm_hsusb_host.0: Qualcomm On-Chip EHCI Host Controller

<6>[08-05 18:27:02.358060] [4: events/0]msm_hsusb_host msm_hsusb_host.0: new USB bus registered, assigned bus number 1

<6>[08-05 18:27:02.358060] [4: events/0]msm_hsusb_host msm_hsusb_host.0: irq 47, io base 0xa0800000

<6>[08-05 18:27:02.358060] [4: events/0]usb usb1: configuration #1 chosen from 1 choice

<6>[08-05 18:27:02.358060] [4: events/0]hub 1-0:1.0: USB hub found

<6>[08-05 18:27:02.358060] [4: events/0]hub 1-0:1.0: 1 port detected

<6>[08-05 18:27:05.388071] [12: ksuspend_usbd]msm_otg_suspend: usb in low power mode

Did not find the USB-Stick at the hub. Hub was powered, USB-stick glowed. Keyboard did not get power and was not found, too.

Link to comment
Share on other sites

Guest t0mm13b

So here are 2 files - a diff against the latest defconfig of 2.6.32-zte branch, and a full config file.

I tried to keep there only relevant features, but still you will surely find there a lot of not necessary things. It's hard for me to just switch everything off as I am used back from kernel 2.0 days (mid 90') to build rather monolithic kernel with everything what would look even remotely useful and doesn't affect reliability or performance turned on.

I hope soon there will be many happy people OTGing around B)

Why are you using that kernel instead of the newer one which is used by CM7?

The 2.6.32-zte branch is somewhat obsolete and replaced by the newer branch 20110624.

Any reason why?

Link to comment
Share on other sites

Guest johnsmithx

I picked an older version of my build before I started destroying it with sensors research. You can download it here.

Maybe editing .config file from memory wasn't the best idea. I am sorry for that, I just wanted to make it easier for you. Now you will have to grab the .config from this kernel a select the options responsible for this to work.

Here is a log with this particular build I just tried on my phone few minutes ago:

<6>[08-05 19:42:09.398623] msm_otg_resume: usb exited from low power mode

<6>[08-05 19:42:09.398623] [4: events/0]msm_hsusb_host msm_hsusb_host.0: Qualcomm On-Chip EHCI Host Controller

<6>[08-05 19:42:09.398623] [4: events/0]msm_hsusb_host msm_hsusb_host.0: new USB bus registered, assigned bus number 1

<6>[08-05 19:42:09.398623] [4: events/0]msm_hsusb_host msm_hsusb_host.0: irq 47, io base 0xa0800000

<6>[08-05 19:42:09.398623] [4: events/0]usb usb1: New USB device found, idVendor=1d6b, idProduct=0002

<6>[08-05 19:42:09.398623] [4: events/0]usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

<6>[08-05 19:42:09.398623] [4: events/0]usb usb1: Product: Qualcomm On-Chip EHCI Host Controller

<6>[08-05 19:42:09.398623] [4: events/0]usb usb1: Manufacturer: Linux 2.6.32.9-perf ehci_hcd

<6>[08-05 19:42:09.398623] [4: events/0]usb usb1: SerialNumber: msm_hsusb_host.0

<6>[08-05 19:42:09.398623] [4: events/0]usb usb1: configuration #1 chosen from 1 choice

<6>[08-05 19:42:09.718638] [14: khubd]usb 1-1: new high speed USB device using msm_hsusb_host and address 2

<6>[08-05 19:42:09.868636] [14: khubd]usb 1-1: New USB device found, idVendor=0457, idProduct=0151

<6>[08-05 19:42:09.868636] [14: khubd]usb 1-1: New USB device strings: Mfr=1, Product=5, SerialNumber=3

<6>[08-05 19:42:09.868636] [14: khubd]usb 1-1: Product: ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ

<6>[08-05 19:42:09.868636] [14: khubd]usb 1-1: Manufacturer: ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ

<6>[08-05 19:42:09.868636] [14: khubd]usb 1-1: SerialNumber: 01234567890123

<6>[08-05 19:42:09.868636] [14: khubd]usb 1-1: configuration #1 chosen from 1 choice

<6>[08-05 19:42:09.878639] [14: khubd]scsi0 : SCSI emulation for USB Mass Storage devices

<7>[08-05 19:42:09.878639] [1489: usb-stor-scan]usb-storage: device found at 2

<7>[08-05 19:42:09.878639] [1489: usb-stor-scan]usb-storage: waiting for device to settle before scanning

<7>[08-05 19:42:14.878623] [1489: usb-stor-scan]usb-storage: device scan complete

<5>[08-05 19:42:14.878623] [1491: scsi_scan_0]scsi 0:0:0:0: Direct-Access USBest USB2FlashStorage 0.00 PQ: 0 ANSI: 2

<5>[08-05 19:42:14.878623] [1491: scsi_scan_0]sd 0:0:0:0: Attached scsi generic sg0 type 0

<5>[08-05 19:42:14.888636] [1492: async/0]sd 0:0:0:0: [sda] 2048000 512-byte logical blocks: (1.04 GB/1000 MiB)

<5>[08-05 19:42:14.888636] [1492: async/0]sd 0:0:0:0: [sda] Write Protect is off

<7>[08-05 19:42:14.888636] [1492: async/0]sd 0:0:0:0: [sda] Mode Sense: 00 00 00 00

<3>[08-05 19:42:14.888636] [1492: async/0]sd 0:0:0:0: [sda] Assuming drive cache: write through

<3>[08-05 19:42:14.888636] [1492: async/0]sd 0:0:0:0: [sda] Assuming drive cache: write through

<6>[08-05 19:42:14.888636] [1492: async/0] sda: sda1

<3>[08-05 19:42:14.898638] [1492: async/0]sd 0:0:0:0: [sda] Assuming drive cache: write through

<5>[08-05 19:42:14.898638] [1492: async/0]sd 0:0:0:0: [sda] Attached SCSI removable disk

Why are you using that kernel instead of the newer one which is used by CM7?

The 2.6.32-zte branch is somewhat obsolete and replaced by the newer branch 20110624.

Any reason why?

I believe I already explained it quite clearly. Besides, there is nothing in this newer branch what is not in mine. On the very contrary.

//EDIT: I see from this log that there is no such line as I mentioned in one of my previous post so to not confuse anyone I deleted that part.

Btw, in this setup both Blade and Flash drive are powered from original Blade charger and Blade is charging:

<6>[08-05 19:51:56.648623] [75: msm_battery]charger_status = good, charger_type = USB PC, batt_status = good , batt_level = good, batt_volt = 4076, batt_cap = 92, batt_temp = 31, chg_fulled = 0

<6>[08-05 19:52:42.648621] [75: msm_battery]charger_status = good, charger_type = USB PC, batt_status = good , batt_level = good, batt_volt = 4081, batt_cap = 93, batt_temp = 32, chg_fulled = 0

<6>[08-05 19:53:26.648621] [75: msm_battery]charger_status = good, charger_type = USB PC, batt_status = good , batt_level = good, batt_volt = 4084, batt_cap = 93, batt_temp = 33, chg_fulled = 0

<6>[08-05 19:54:56.648623] [75: msm_battery]charger_status = good, charger_type = USB PC, batt_status = good , batt_level = good, batt_volt = 4091, batt_cap = 94, batt_temp = 33, chg_fulled = 0

<6>[08-05 19:55:12.648624] [75: msm_battery]charger_status = good, charger_type = USB PC, batt_status = good , batt_level = good, batt_volt = 4091, batt_cap = 94, batt_temp = 34, chg_fulled = 0

<6>[08-05 19:57:26.648621] [75: msm_battery]charger_status = good, charger_type = USB PC, batt_status = good , batt_level = good, batt_volt = 4100, batt_cap = 95, batt_temp = 34, chg_fulled = 0

<6>[08-05 19:58:26.648623] [75: msm_battery]charger_status = good, charger_type = USB PC, batt_status = good , batt_level = good, batt_volt = 4110, batt_cap = 96, batt_temp = 34, chg_fulled = 0

<6>[08-05 19:59:56.648621] [75: msm_battery]charger_status = good, charger_type = USB PC, batt_status = good , batt_level = good, batt_volt = 4121, batt_cap = 97, batt_temp = 34, chg_fulled = 0

<6>[08-05 20:01:26.648621] [75: msm_battery]charger_status = good, charger_type = USB PC, batt_status = good , batt_level = good, batt_volt = 4131, batt_cap = 98, batt_temp = 34, chg_fulled = 0

<6>[08-05 20:02:56.648621] [75: msm_battery]charger_status = good, charger_type = USB PC, batt_status = good , batt_level = good, batt_volt = 4137, batt_cap = 98, batt_temp = 35, chg_fulled = 0

<6>[08-05 20:06:26.648621] [75: msm_battery]charger_status = good, charger_type = USB PC, batt_status = good , batt_level = good, batt_volt = 4140, batt_cap = 99, batt_temp = 35, chg_fulled = 0

<6>[08-05 20:06:56.648621] [75: msm_battery]charger_status = good, charger_type = USB PC, batt_status = good , batt_level = good, batt_volt = 4141, batt_cap = 99, batt_temp = 34, chg_fulled = 0

<6>[08-05 20:09:12.648623] [75: msm_battery]charger_status = good, charger_type = USB PC, batt_status = good , batt_level = good, batt_volt = 4150, batt_cap = 100, batt_temp = 34, chg_fulled = 0

<6>[08-05 20:11:58.648623] [75: msm_battery]charger_status = good, charger_type = USB PC, batt_status = good , batt_level = good, batt_volt = 4157, batt_cap = 100, batt_temp = 33, chg_fulled = 0

Edited by johnsmithx
Link to comment
Share on other sites

Guest t0mm13b

Here's a refreshed kernel recompiled again. I have made some additional configuration changes to the binary... simply reflash the kernel again and please report back.

Link to comment
Share on other sites

Guest DB_Runner

my results with Kernel v2 (usb stick and keyboard connected):

<6>[08-06 10:09:44.819168] [56: kpmapp_usbclntc]msm_otg_resume: usb exited from low power mode

<6>[08-06 10:09:44.829165] VBUS - (ON)

<6>[08-06 10:09:44.869163] [225: er.ServerThread][ZYF@pmic-leds]DISABLE green led blink

<6>[08-06 10:09:45.189156] [13: khubd]usb 1-1: new high speed USB device using msm_hsusb_host and address 8

<6>[08-06 10:09:45.339155] [13: khubd]usb 1-1: New USB device found, idVendor=05e3, idProduct=0608

<6>[08-06 10:09:45.339155] [13: khubd]usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0

<6>[08-06 10:09:45.339155] [13: khubd]usb 1-1: Product: USB2.0 Hub

<6>[08-06 10:09:45.339155] [13: khubd]usb 1-1: configuration #1 chosen from 1 choice

<6>[08-06 10:09:45.339155] [13: khubd]hub 1-1:1.0: USB hub found

<6>[08-06 10:09:45.339155] [13: khubd]hub 1-1:1.0: 4 ports detected

<6>[08-06 10:09:45.629166] [13: khubd]usb 1-1.3: new low speed USB device using msm_hsusb_host and address 9

<6>[08-06 10:09:45.739155] [13: khubd]usb 1-1.3: New USB device found, idVendor=046a, idProduct=0023

<6>[08-06 10:09:45.739155] [13: khubd]usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0

<6>[08-06 10:09:45.739155] [13: khubd]usb 1-1.3: configuration #1 chosen from 1 choice

<6>[08-06 10:09:45.839155] [13: khubd]usb 1-1.4: new high speed USB device using msm_hsusb_host and address 10

<6>[08-06 10:09:45.949158] [13: khubd]usb 1-1.4: New USB device found, idVendor=0781, idProduct=5406

<6>[08-06 10:09:45.949158] [13: khubd]usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3

<6>[08-06 10:09:45.949158] [13: khubd]usb 1-1.4: Product: U3 Cruzer Micro

<6>[08-06 10:09:45.949158] [13: khubd]usb 1-1.4: Manufacturer: SanDisk

<6>[08-06 10:09:45.949158] [13: khubd]usb 1-1.4: SerialNumber: ####

<6>[08-06 10:09:45.949158] [13: khubd]usb 1-1.4: configuration #1 chosen from 1 choice

<6>[08-06 10:09:45.949158] [13: khubd]scsi4 : SCSI emulation for USB Mass Storage devices

<7>[08-06 10:09:45.959170] [1568: usb-stor-scan]usb-storage: device found at 10

<7>[08-06 10:09:45.959170] [1568: usb-stor-scan]usb-storage: waiting for device to settle before scanning

<6>[08-06 10:09:46.759158] [68: msm_battery]charger_status= good, charger_type= USB PC,batt_status= good , batt_level= good,batt_volt= 4146,batt_cap= 99,batt_temp= 37,full= 0,allow2shutdown(1?y;n)= 1

<6>[08-06 10:09:48.759158] [68: msm_battery]charger_status= good, charger_type= USB PC,batt_status= good , batt_level= good,batt_volt= 4145,batt_cap= 99,batt_temp= 37,full= 0,allow2shutdown(1?y;n)= 1

<7>[08-06 10:09:50.959158] [1568: usb-stor-scan]usb-storage: device scan complete

<5>[08-06 10:09:50.959158] [1569: scsi_scan_4]scsi 4:0:0:0: Direct-Access SanDisk Cruzer 7.01 PQ: 0 ANSI: 0 CCS

<5>[08-06 10:09:50.969169] [1569: scsi_scan_4]sd 4:0:0:0: Attached scsi generic sg0 type 0

<5>[08-06 10:09:50.969169] [1570: async/0]sd 4:0:0:0: [sda] 31355391 512-byte logical blocks: (16.0 GB/14.9 GiB)

<5>[08-06 10:09:50.969169] [1570: async/0]sd 4:0:0:0: [sda] Write Protect is off

<7>[08-06 10:09:50.979204] [1570: async/0]sd 4:0:0:0: [sda] Mode Sense: 45 00 00 08

<3>[08-06 10:09:50.979204] [1570: async/0]sd 4:0:0:0: [sda] Assuming drive cache: write through

<3>[08-06 10:09:50.979204] [1570: async/0]sd 4:0:0:0: [sda] Assuming drive cache: write through

<6>[08-06 10:09:50.979204] [1570: async/0] sda: sda1

<3>[08-06 10:09:50.989173] [1570: async/0]sd 4:0:0:0: [sda] Assuming drive cache: write through

<5>[08-06 10:09:50.989173] [1570: async/0]sd 4:0:0:0: [sda] Attached SCSI removable disk

still random reboots when connecting/disconnecting the usb otg cable

keyboard doesnt work (cause no power supply)

Edited by DB_Runner
Link to comment
Share on other sites

Guest t0mm13b

Am getting reboots as well....

Checking it out the logs... if things were that simple... :rolleyes:

P.S: It looks like as if its a power surge in the usb hub that's what causing it reboot - that's my initial impression...

Edited by t0mm13b
Link to comment
Share on other sites

Guest t0mm13b

Well, today is a sad day, my blade died as result of USB OTG experiment which went horribly wrong.

Listen up, do not plug in the mains adapter into the usb hub, and with the straight cable coming out of hub plugged into the OTG adaptor - that's what killed it (I failed to use the hub's micro 5 pin to usb end plugged into OTG adaptor) into the blade directly (which is what I did and the screen went all funny with a rather ominous smell of death)

Sob sob... RIP Blade..... :(

Link to comment
Share on other sites

Guest t0mm13b

This is the

video that explains how it went wrong....

The part where I explained about the 4 port Hub's own micro 5pin<->usb male cable, I had that plugged into the blade's OTG adaptor, and the mains cable plugged into the 4port hub, the blade rebooted.

Then I thought to myself, okie, take out the Hub's own micro 5pin<->usb male cable. Get a straight through cable, plug it into hub, with other end plugged into usb otg adaptor, the mains cable being plugged into the hub to provide power, then the screen went sort of ... and funny burning smells....

Oh! And btw, the USB OTG adaptor came from dealextreme.com so ..... ?????

On IRC, Phoenix_Silver, mentioned that it could have been the OTG adaptor that could have switched the 5v and ground and boom and also FelixL mentioned that the straight male-male usb cable could have switched the 5v and ground as well... not 100% sure...

Edited by t0mm13b
Link to comment
Share on other sites

Guest FelixL

I don't know how this A-A-cable has it's pins set, but even then there is a clear rule for all usb cables where the +5V must be and where not. Even with this cable, if you hold the two plugs side by side the pins should be connected with the same pins on the other side. The left pin with the left on the other plug, and so on. Maybe you can check this with a multimeter?

johnsmithx: Your kernel should be usable for everybody, right? We've got a few guys in Germany with the new accelerometer, and I could try if my Blade just doesn't like the hub I use.

Link to comment
Share on other sites

Guest targetbsp

Look at the dates of this stuff. :D I think it'd go pear-shaped if you attempted to put kernels intended for a March build of Cm7 into a current CM7. And a lot of the stuff that was experimental here is in Cm7 now I think? The radio is.

Whilst looking for info on the smartass governor today I actually realised I mistook this thread for the other experimental kernel thread: http://android.modaco.com/topic/334310-kernel-cm7-experimental-branch/ It's that one that has all been merged in CM7. Sorry for any confusion I caused. :D

Link to comment
Share on other sites

Guest johnsmithx

johnsmithx: Your kernel should be usable for everybody, right? We've got a few guys in Germany with the new accelerometer, and I could try if my Blade just doesn't like the hub I use.

Well, it contains many additional things probably not useful for most people, but it should be usable nevertheless. But this one is an older version before I started dealing with the accelerometer issue, so it doesn't contain the backported multiaccelerometer driver yet.

If you need support for newer accelerometer, just take kernel from CM and sort out the old incompatible proprietary files.

If you need OTG, you can take this kernel or reconfigure accordingly the current branch CM kernel.

If you need OTG and support for newer accelerometer at the same time, then combine those options.

Link to comment
Share on other sites

Guest johnsmithx

As for the killing hub, I don't think that either the hub or the usb cable switched +5V and gnd, in that case nothing you would use it with wouldn't work. I mean sure it may have switched it but because it's junk not because it was intentionally built to do that.

Was this cable and hub new? Have you never ever used them before? Because if you did and it worked then it can't just all of sudden change its mind and start sending 5V where should be gnd and vice versa.

Anyway, burning anything (with even burning smell) with 5V, all the way via the board to the lcd and microsd card, doesn't seem very likely to me. Are you really sure your power input into the hub was really only 5V? If you have plugged there 12V, that would make sense more.

In any case, as FelixL says, a multimeter should give some better answers.

//EDIT: people here say that even reversing the polarity might have possibly done something like that..

Edited by johnsmithx
Link to comment
Share on other sites

Guest h4z7d

T0m13b - I'm really sorry to hear that your phone and SD have died. That's really terrible news.

USB Host is working on my phone. Keyboard and Mouse work. The new patch has stopped my phone rebooting on connection/disconnection. I'm trying it with CM7-07242011- Nightly. Sometimes I have to reboot my phone for it to detect the USB hub.

I rebooted into Clockwork and ran the two zips.

I was wondering what the limitations are with USB storage devices. Do they need to be formatted to FAT32, or will NTFS work?

The command I have tried was from SVENS site:

mount -t vfat /dev/block/sda1 /mnt/sdcard/usb-storage

doing ls on /dev/block shows sda1 being present.

Edit: Sorry it appears that FAT32 works fine. So I dont have NTFS support.

Edited by h4z7d
Link to comment
Share on other sites

Guest t0mm13b

That USB-Micro adaptor looks very like the one from DealExtreme or is likely sourced from them? 5 in pack for that price iirc.... :) :D

But thanks for the linkys to the amazon site - much appreciated :)

Link to comment
Share on other sites

Guest h4z7d

I probably paid over the odds but I brought the phone , 16gb sdcard, usb hub and adapter at the same time so I was being lazy.

I have noticed that the phone occasionally "freezes" but I think this is linked to when I'm running certain apps e.g. teamviewer with a mouse attached. When this happens I have to remove the battery. Also the phone often reboots when I remove/add the cable while a mouse is attached.

I've not tried anything else yet. Ideally I would get USB/Serial and USB/Ethernet working. It would remove the need for me to use a laptop at work.

I'm thinking about subsituting the USB Hubs power supply with battery powererd alternative. Any sugestions? I have a powerchimp but I thinks it possibly the worst thing I've ever brought.

Link to comment
Share on other sites

Guest FelixL

h4z7d:

You can try the serial modules from here: http://sven.killig.de/android/Blade/usb_host/

There should be three different modules in the package, for different USB-to-serial converters.

DB_Runner:

I cant explain why USB OTG doesnt work at my blade.

+1.

Plus I lost my adapter yesterday, can't find it anymore....probably my cat stole it -.-

johnsmithx:

Could you upload your backported kernel for the people with the accelerometer issue here?

Edited by FelixL
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.