Develop Bugs

[Q] Data transfer via MTP on ubuntu

Hi there,
has anyone tried to use the MTP file transfer option of the Fairphone with Ubuntu (I'm using 13.04 at the moment). It seems that the phone is recognized by my system:
Code:
[49875.145923] usb 1-1.2: new high-speed USB device number 12 using ehci-pci
[49875.240046] usb 1-1.2: New USB device found, idVendor=0bb4, idProduct=0c02
[49875.240057] usb 1-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[49875.240063] usb 1-1.2: Product: MT65xx Android Phone
[49875.240068] usb 1-1.2: Manufacturer: MediaTek
[49875.240072] usb 1-1.2: SerialNumber: ...
but the device is not shown in Nautilus.
Who knows how to fix that?
Thanks,
Tobi

prinz.z said:
Hi there,
has anyone tried to use the MTP file transfer option of the Fairphone with Ubuntu (I'm using 13.04 at the moment). It seems that the phone is recognized by my system. but the device is not shown in Nautilus.
Who knows how to fix that?
Thanks,
Tobi
Click to expand...
Click to collapse
I guess this is more an Ubuntu issue/question than Fairphone's..
You can follow instructions here
Code:
$ sudo mtpfs -o allow_other /media/MTPdevice
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=0bb4 and PID=2008) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
0bb4:2008 @ bus 2, dev 20
Attempting to connect device
Android device detected, assigning default bug flags
Listing File Information on Device with name: FP1
Nautilus gave me read-only access to content under the custom mount point /media/MTPdevice. dmesg gave me the same log as yours when recognizing the device...

It doesn't work for me either. But this is an issue that is usual in Ubuntu. Even though it is not an issue in Ubuntu.
* libMTP with a detailed description
* gvfs-mtp
* go-mtpfs
I use either the USB storage or PTP.
(MTP is buggy.)

Okay, I see.. With my former phone (LG O4x, cm-11) it was working flawlessly with mtp on Ubuntu, that's the rason I asked.. With the fairphone, I'm simply using adb for the moment to copy single files..
elchi1234 said:
It doesn't work for me either. But this is an issue that is usual in Ubuntu. Even though it is not an issue in Ubuntu.
* libMTP with a detailed description
* gvfs-mtp
* go-mtpfs
I use either the USB storage or PTP.
(MTP is buggy.)
Click to expand...
Click to collapse

[Q] Phone doesn't boot

Hey community,
I have big problems with my Fairphone.
It doesn't boot, it happens nothing, totally black screen, no fairphone logo, no system popup...
I turned it off yesterday and since then I've got this issues.
I tried :
-every key combination but nothing happened
-to connect it with my computer and charger but nothing happened, no sign, no LED signal
-removed battery and sim card
I didn't make something unusual, only turned it off, so can anyone please help me?
Thanks in advance

DarkerTimes said:
Hey community,
I have big problems with my Fairphone.
It doesn't boot, it happens nothing, totally black screen, no fairphone logo, no system popup...
I turned it off yesterday and since then I've got this issues.
I tried :
-every key combination but nothing happened
-to connect it with my computer and charger but nothing happened, no sign, no LED signal
-removed battery and sim card
I didn't make something unusual, only turned it off, so can anyone please help me?
Thanks in advance
Click to expand...
Click to collapse
Hi can you try if the recovery mode still works? (e.g turn off the phone and power it on by keeping the power and volume up button pressed).
If that doesn't work try removing the battery and connecting the device to a Linux PC and see if a new device appears (by running dmesg). Do you see a device appear?

_keesj said:
Hi can you try if the recovery mode still works? (e.g turn off the phone and power it on by keeping the power and volume up button pressed).
If that doesn't work try removing the battery and connecting the device to a Linux PC and see if a new device appears (by running dmesg). Do you see a device appear?
Click to expand...
Click to collapse
Hi,
recovery mode doesn't work, the phone is completely dead.
Then I will try your tip with the Linux PC. But first I have to find one^^
I will tell you when i have access to a linux computer and when it gets the device.
Thanks for your help
Gesendet von meinem GT-I9505 mit Tapatalk

DarkerTimes said:
Hi,
recovery mode doesn't work, the phone is completely dead.
Then I will try your tip with the Linux PC. But first I have to find one^^
I will tell you when i have access to a linux computer and when it gets the device.
Thanks for your help
Gesendet von meinem GT-I9505 mit Tapatalk
Click to expand...
Click to collapse
You might like to know that you can run many versions of Linux directly from a DVD drive or USB drive. A popular one, and probably the easiest, is: http://www.ubuntu.com/desktop
To "run dmesg", as suggested by @_keesj, do the following:
Start Ubuntu
When the desktop is open, press the Windows key.
Connect your phone.
Type "Terminal".
Press Enter or click the Terminal icon.
Type dmesg, press Enter.

Vinnl said:
You might like to know that you can run many versions of Linux directly from a DVD drive or USB drive. A popular one, and probably the easiest, is: http://www.ubuntu.com/desktop
To "run dmesg", as suggested by @_keesj, do the following:
Start Ubuntu
When the desktop is open, press the Windows key.
Connect your phone.
Type "Terminal".
Press Enter or click the Terminal icon.
Type dmesg, press Enter.
Click to expand...
Click to collapse
Thank you very much, I will try
Gesendet von meinem GT-I9505 mit Tapatalk

Vinnl said:
You might like to know that you can run many versions of Linux directly from a DVD drive or USB drive. A popular one, and probably the easiest, is: http://www.ubuntu.com/desktop
To "run dmesg", as suggested by @_keesj, do the following:
Start Ubuntu
When the desktop is open, press the Windows key.
Connect your phone.
Type "Terminal".
Press Enter or click the Terminal icon.
Type dmesg, press Enter.
Click to expand...
Click to collapse
View attachment 2925701
I got this message when i connect my Phone to a 32bit Ubuntu VM (VMWare-Player)
Do you know an option for dmesg to make the text shorter? Its such a huge text, larger than the Terminal is able to display.

DarkerTimes said:
View attachment 2925701
I got this message when i connect my Phone to a 32bit Ubuntu VM (VMWare-Player)
Do you know an option for dmesg to make the text shorter? Its such a huge text, larger than the Terminal is able to display.
Click to expand...
Click to collapse
Congratulation for your first GNU/linux use !:highfive:
Yeah dmesg is super huge, it contains record of all that happened on your system since your started it up. (it s a bit more complicated in fact).
I dont know any option to make it shorter, but there are ways
- to only get the bottom of it,
- to save its output in a file
Code:
dmesg > ~/Desktop/dmesg-output.txt
- or to increase the amount of message your terminal can display (right click, profile, profile preferences, scrolling, unlimited).
However here you only need to look at what happened recently (i.e when you connected your phone)
If you connecte your phone and then run the dmesg command the end of the output should show the device detection in the last 50 lines.
I cant acces your attachement, is this only me ?
With a working phone on a non VM ubuntu you should see something like this.
(It may be different on your system, as long as you can read som usb lines, further more containing MT65xx or Mediateck, you are good to go !
....
...
[ 237.437926] usb 2-1.6: new high-speed USB device number 5 using ehci-pci
[ 237.530804] usb 2-1.6: New USB device found, idVendor=0e8d, idProduct=2000
[ 237.530809] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 237.530812] usb 2-1.6: Product: MT65xx Preloader
[ 237.530814] usb 2-1.6: Manufacturer: MediaTek
[ 237.637040] cdc_acm 2-1.6:1.1: ttyACM0: USB ACM device
[ 237.692248] usbcore: registered new interface driver cdc_acm
[ 237.692250] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapter
....
That would means that your OS detected that a new device was connected to USB and that it recognise a mediateck phone.
I hope it's also the case with your phone !
BTW I don't know vmware so well, but sometimes virtual machine prevent virtualised operating system to acces usb port. Maybe someone can confirm that this issue wont appear here ? Or you can check it out by plugging some working usb device and look if some lines get added to dmesg

MoreThanADev said:
I cant acces your attachement, is this only me ?
Click to expand...
Click to collapse
Nope, apparently the attachment wasn't uploaded correctly.

MoreThanADev said:
I cant acces your attachement, is this only me ?
Click to expand...
Click to collapse
hope it works now
View attachment 2927858
here is the output from dmesg:
first run:
[ 5.270990] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 5.271001] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.271010] usb usb1: Product: EHCI Host Controller
[ 5.271019] usb usb1: Manufacturer: Linux 3.13.0-35-generic ehci_hcd
[ 5.271027] usb usb1: SerialNumber: 0000:02:03.0
[ 5.272005] hub 1-0:1.0: USB hub found
[ 5.272231] hub 1-0:1.0: 6 ports detected
[ 5.273333] ehci-platform: EHCI generic platform driver
[ 5.273386] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 5.273404] ohci-pci: OHCI PCI platform driver
[ 5.273465] ohci-platform: OHCI generic platform driver
[ 5.273494] uhci_hcd: USB Universal Host Controller Interface driver
[ 5.273813] uhci_hcd 0000:02:00.0: UHCI Host Controller
[ 5.273822] uhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
[ 5.274010] uhci_hcd 0000:02:00.0: irq 18, io base 0x000020c0
[ 5.274349] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[ 5.274351] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.274352] usb usb2: Product: UHCI Host Controller
[ 5.274353] usb usb2: Manufacturer: Linux 3.13.0-35-generic uhci_hcd
[ 5.274355] usb usb2: SerialNumber: 0000:02:00.0
[ 5.274492] hub 2-0:1.0: USB hub found
[ 5.274546] hub 2-0:1.0: 2 ports detected
second run
[ 201.982468] usb 2-2.1: new full-speed USB device number 4 using uhci_hcd
[ 202.310781] usb 2-2.1: New USB device found, idVendor=0e8d, idProduct=0003
[ 202.310840] usb 2-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 202.448421] cdc_acm 2-2.1:1.0: ttyACM0: USB ACM device
[ 202.456529] usbcore: registered new interface driver cdc_acm
[ 202.456544] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 202.471104] usbcore: registered new interface driver usbserial
[ 202.471210] usbcore: registered new interface driver usbserial_generic
[ 202.471344] usbserial: USB Serial support registered for generic
[ 202.481866] usbcore: registered new interface driver option
[ 202.482531] usbserial: USB Serial support registered for GSM modem (1-port)
[ 241.102849] usb 2-2.1: USB disconnect, device number 4
[ 266.180249] usb 2-2.1: new full-speed USB device number 5 using uhci_hcd
[ 266.581692] usb 2-2.1: New USB device found, idVendor=0e8d, idProduct=0003
[ 266.581747] usb 2-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 266.660505] cdc_acm 2-2.1:1.0: ttyACM0: USB ACM device
what to do now?
btw, every 50-60 seconds i got the pluggin and unplugg sound from my windows system
Edit:
i have a second Fairphone now and tried to turn on the first one with tha accu of the second one and the second phone with the accu of the first one. both doesn´t start. only the second one with the second accu is working.

DarkerTimes said:
second run
[ 266.180249] usb 2-2.1: new full-speed USB device number 5 using uhci_hcd
[ 266.581692] usb 2-2.1: New USB device found, idVendor=0e8d, idProduct=0003
[ 266.581747] usb 2-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 266.660505] cdc_acm 2-2.1:1.0: ttyACM0: USB ACM device
what to do now?
Click to expand...
Click to collapse
These lines are your phone so there is still some life in it. But it doesnt even start the preloader which appears after these lines if I plug in my phone (powered off).
Maybe this low level mode is enough for the SP flash tool and you can try the unbrick guide: http://forum.xda-developers.com/wik...o_restore_Fairphone_if_you_totally_bricked_it
Make sure to chose the correct image (FUSE for upgraded partition layout, 1G13G for the old layout)
You might want to uncheck "userdata", this might give you a chance of keeping your apps and settings.
Other than that you could contact Fairphone support.

My Solution
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I had the same Problem while trying install CM11.
What works for me @ a Win7 PC:
- remove the Battery (Force shutdown the phone)
- plugin the Battery
- Turn on the Phone while pressing the power-button and the volume-UP button. (release power button after 6 Secs)
- Now you're in the recovery menu
- If you have CWM (like me) goto --> install zip --> install zip from sideload
If you have another bootloader you'll find the "install zip from sideload" somewhere...
- Download the Original zip-file from Fairphone (Fairphone Website --> SUPPORT --> SOFTWARE --> UPDATES --> SOFTWARE --> DOWNLOADS)
- Download / install the MTK6589 ADB Driver (http://forum.xda-developers.com/showthread.php?t=2247537)
- now download a tool which contains the adb.exe (I tooked the "MTK droid root & tools" http://forum.xda-developers.com/showthread.php?t=2160490)
- Start the MTK tool as Admin and press "ADB-Terminal"
- in the Terminal write: "adb push NAMEOFTHEZIPFILE.zip"
- now your phone should start transfer, reboot and install the original OS
Hope this works for you too...
* More about ADB and Sideload (http://forum.xda-developers.com/showthread.php?t=2318497
Regards

_tmp said:
These lines are your phone so there is still some life in it. But it doesnt even start the preloader which appears after these lines if I plug in my phone (powered off).
Maybe this low level mode is enough for the SP flash tool and you can try the unbrick guide: http://forum.xda-developers.com/wik...o_restore_Fairphone_if_you_totally_bricked_it
Make sure to chose the correct image (FUSE for upgraded partition layout, 1G13G for the old layout)
You might want to uncheck "userdata", this might give you a chance of keeping your apps and settings.
Other than that you could contact Fairphone support.
Click to expand...
Click to collapse
shooter_92 said:
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I had the same Problem while trying install CM11.
What works for me @ a Win7 PC:
- remove the Battery (Force shutdown the phone)
- plugin the Battery
- Turn on the Phone while pressing the power-button and the volume-UP button. (release power button after 6 Secs)
- Now you're in the recovery menu
- If you have CWM (like me) goto --> install zip --> install zip from sideload
If you have another bootloader you'll find the "install zip from sideload" somewhere...
- Download the Original zip-file from Fairphone (Fairphone Website --> SUPPORT --> SOFTWARE --> UPDATES --> SOFTWARE --> DOWNLOADS)
- Download / install the MTK6589 ADB Driver (http://forum.xda-developers.com/showthread.php?t=2247537)
- now download a tool which contains the adb.exe (I tooked the "MTK droid root & tools" http://forum.xda-developers.com/showthread.php?t=2160490)
- Start the MTK tool as Admin and press "ADB-Terminal"
- in the Terminal write: "adb push NAMEOFTHEZIPFILE.zip"
- now your phone should start transfer, reboot and install the original OS
Hope this works for you too...
* More about ADB and Sideload (http://forum.xda-developers.com/showthread.php?t=2318497
Regards
Click to expand...
Click to collapse
Hey guys,
sry that I've been away for this long period of time.
The problem is that i can't enter recovery mode, so the only way to try it would be with the SP flash tool but I decided to contact the fairphone support and sent it back for repairing it.
But thanks all for your help!!
Edit: I got my phone back now. The issues were caused by damaged mainboard, they change it completely.
Sent from my Galaxy S4 using Tapatalk

I have the same problem
Hey,
I have the same problem, did it fall under warranty or did you have to pay for the repair?

hewitje240 said:
Hey,
I have the same problem, did it fall under warranty or did you have to pay for the repair?
Click to expand...
Click to collapse
Hi, did fall under warranty
Sent from my GT-I9505 using XDA Free mobile app

OTG

Does Nokia N1 got OTG support? I have Tried to connect my USB Flash through OTG cable but doesn't work for me ....

Doesn't work for me either >_<

I don't have an otg cable myself (yet) but can you try to use USB Host Diagnostics (available in play store) and post the report?

FYI I got an OTG cable myself and it didn't work. I dug a bit deeper and found out that OTG is most likely not implemented because Nokia N1 is using legacy usb controller over usb C - see below:
Converting USB 2.0 OTG SoCs to USB Type-C
While existing Device, Host, and DRD devices can be converted to support the USB Type-C connection with some effort, it is not practical to convert existing OTG SoCs. OTG requires a new state machine using the configuration channel to support USB Type-C. Host Negotiation Protocol is used to swap host and device role for OTG, while Power Delivery communication is used to change roles for USB Type-C. Combined, these challenges preclude simple upgrades of OTC SoCs to USB Type-C. - See more at: https://www.synopsys.com/Company/Pu...esign-type-c-2015q1.aspx#sthash.Ri02Guwe.dpuf
Click to expand...
Click to collapse
The only chance to get otg to work is most likely preparing a kernel patch (are the sources even available?) to manually switch the connector to host mode and power the attached device externally

After a bit of hacking around I was able to enable usb otg on my N1!
I've had a look at kernel sources for device with similar SoC (Nexus Player) and saw an interesting debugfs entry. To my surprise it worked like a charm and immediately detected the attached usb hub with a thumb drive, it even powered the hub so I didn't have to use an external power source!
To enable host mode, the following command has to be enterted in root console:
echo A > /sys/kernel/debug/usb/dwc3_debugfs_root/otg_id
Caveats (will try to find a way to resolve them):
- after enabling host mode N1, won't charge from the usb port - a reboot is required to enable the charging again
- probably same is true for pheripherial mode (connecting n1 to a pc). In theory, changing a to b in the above echo command should bring the tablet back to normal mode but for some reason it won't charge without a reboot so I'm assuming that same is true for non otg usb connectivity. Will have a look at the sources and debug messages to find out what's going on

wodz69 said:
After a bit of hacking around I was able to enable usb otg on my N1!
I've had a look at kernel sources for device with similar SoC (Nexus Player) and saw an interesting debugfs entry. To my surprise it worked like a charm and immediately detected the attached usb hub with a thumb drive, it even powered the hub so I didn't have to use an external power source!
To enable host mode, the following command has to be enterted in root console:
echo A > /sys/kernel/debug/usb/dwc3_debugfs_root/otg_id
Caveats (will try to find a way to resolve them):
- after enabling host mode N1, won't charge from the usb port - a reboot is required to enable the charging again
- probably same is true for pheripherial mode (connecting n1 to a pc). In theory, changing a to b in the above echo command should bring the tablet back to normal mode but for some reason it won't charge without a reboot so I'm assuming that same is true for non otg usb connectivity. Will have a look at the sources and debug messages to find out what's going on
Click to expand...
Click to collapse
Thanks for your hard job.
I have tried on my N1. It is amazing that otg did work. However, the otg can not coexist with charging function as yours. Hope someone could find a solution.

adagiov said:
Thanks for your hard job.
I have tried on my N1. It is amazing that otg did work. However, the otg can not coexist with charging function as yours. Hope someone could find a solution.
Click to expand...
Click to collapse
Hey,
Are you on Android 5.1.1 or 5.0 ?
I've had a look at the code of the usb driver of the a phone with similar chipset (asus zenfone 5) and it seems that the source of the problem is that the tablet fails to detect an appropriate charger type, which could mean either that the otg cable does not support this or the code of the driver does not work properly with usb C. Was wondering if something changed around this after the update?

wodz69 said:
Hey,
Are you on Android 5.1.1 or 5.0 ?
I've had a look at the code of the usb driver of the a phone with similar chipset (asus zenfone 5) and it seems that the source of the problem is that the tablet fails to detect an appropriate charger type, which could mean either that the otg cable does not support this or the code of the driver does not work properly with usb C. Was wondering if something changed around this after the update?
Click to expand...
Click to collapse
Hi, mine N1 is still running the android 5.0.
I am afraid Root is the prerequisite to hack otg. Unfortunately, root is not available on android 5.1.1 till now, so even the android 5.1.1 driver support it, that won't help.
Thanks,dude.

Yeah exactly for that reason I haven't upgraded my tablet yet

[D855P] Model "Unknow" in LGUP, after use LG FlashTool

Hi everybody.
I try to install Cyanogenmod on my LG G3 (model D855P bought on Brazil), but the install stopped after some minutes before finish.
I received the LG loop logo. After read some topic's about this error, I try to write a original firmware (.TOT D855AT European). The install runing with any problems. But now, my smartphone is show in LGUP with "Unknow" in the model, but show me the connection port is COM3.
I used the Boarddiag to verify the phone and any error founded. I try to re-write the SDRAM with files extract from LGD855PAT-01-V10a-370-02-JUN-10-2014-16G-32G+3, but not work. I install, but the problem continue the same.
I try the process when you change the COMxx port to COM41 and using a specified .dll, but the process stop in the first steps of validation.
Now, when I turn-on my phone, after some minutes I receive the message: Kernel Crash Handler. If I press Power+Down, the fastboot interface is started, but when I try to access using ADB (in Linux or Windows 10), the device is not listed with command ADB DEVICES. In the Windows 10, my device is recognize in "Manager Devices" with the name "Kedacom USB Device > Android Bootloader Interface".
I try to create the file on .android folder, but not work.
When run the command DMESG in the Linux, my device have this information:
usb 1-5: new high-speed USB device number 3 using ehci-pci
usb 1-5: New USB device found, idVendor=18d1, idProduct=d00d
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-5: Product: Android
usb 1-5: Manufacturer: Google
Anyone have some idea to help me about this problem???

fdelago said:
Hi everybody.
I try to install Cyanogenmod on my LG G3 (model D855P bought on Brazil), but the install stopped after some minutes before finish.
I received the LG loop logo. After read some topic's about this error, I try to write a original firmware (.TOT D855AT European). The install runing with any problems. But now, my smartphone is show in LGUP with "Unknow" in the model, but show me the connection port is COM3.
I used the Boarddiag to verify the phone and any error founded. I try to re-write the SDRAM with files extract from LGD855PAT-01-V10a-370-02-JUN-10-2014-16G-32G+3, but not work. I install, but the problem continue the same.
I try the process when you change the COMxx port to COM41 and using a specified .dll, but the process stop in the first steps of validation.
Now, when I turn-on my phone, after some minutes I receive the message: Kernel Crash Handler. If I press Power+Down, the fastboot interface is started, but when I try to access using ADB (in Linux or Windows 10), the device is not listed with command ADB DEVICES. In the Windows 10, my device is recognize in "Manager Devices" with the name "Kedacom USB Device > Android Bootloader Interface".
I try to create the file on .android folder, but not work.
When run the command DMESG in the Linux, my device have this information:
usb 1-5: new high-speed USB device number 3 using ehci-pci
usb 1-5: New USB device found, idVendor=18d1, idProduct=d00d
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-5: Product: Android
usb 1-5: Manufacturer: Google
Anyone have some idea to help me about this problem???
Click to expand...
Click to collapse
Any luck unbricking your device?
I have the same problem here

Support for Nvidia SATA?

I'm trying to install Bliss os in an old PC with a nvidia sata but it doesnt detect my hard drives(2 sata HDD), it works very well in an USB drive in live mode. I installed it in a notebook, make a copy with dd in manjaro and copy it in the nvidia sata pc but it stuck in "Detecting Android x86...". So my conclusion is that the module "SATA_NV" is not included in the original kernel, there is a kernel that include it?