Skip to contentSkip to conversation

problems with mtp , better to make a command-line option to can switch off mtp device search on booting

DISCUSSION werner 2 participants 3 messages Jun 13, 2011 – Jun 18, 2011

lore
Share & tools
lore

werner

author
#0 lore raw

I get yesterday an acer laptop with big problems to install Linux

booting stopped with error messages like:

physmap_flash.0 failed claim ressource 0

L440GX flash mapping failed to find PIIX4 ISA bridge, cannot continue

Then the computer stopped, but not crashed, the cursor stopped to blink, but reboot with CTRL-ALT-DEL didn't work, one had to press the reboot button

I recompiled the kernel with all MTP things switched off, and that booted.

However, normally it should be compiled everything in the kernel, and the kernel during booting should manage it to see and to use what is existent in the computer of the user, without to stick or to crash.

Probably that is an error already sine time in the kernel, not a recent regression.

Better to make a command-line option to can switch off mtp device search on booting

wl

=================================================
I have problems to post something from my home computer site guyane.yi.org or SYS-Linux.yi.org :

Deferred: 451 4.7.1 Hello [93.121.138.180], for recipient address the policy analysis reported: Greylisted, see http://isg.ee.ethz.ch/tools/postgrey/help/vger.kernel.org.html
---
Professional hosting for everyone - http://www.host.ru

#1 lore raw

So I still think you're crazy to compile in MTD support at all, but hey, I do agree that it is supposed to work.

The "L440GX flash mapping failed" message isn't new, and I doubt that that particular driver is the problem. Can you try to narrow it down to _which_ MTD driver causes problems? Enable MTD again, and try to enable about half the devices to "bisect" the issue.

Linus

Quoted 39 lines · werner

I get yesterday an acer laptop with big problems to install Linux

booting stopped with error messages like:

physmap_flash.0 failed claim ressource 0

L440GX flash mapping failed to find PIIX4 ISA bridge, cannot continue

Then the computer stopped, but not crashed, the cursor stopped to blink, but reboot
with CTRL-ALT-DEL didn't work, one had to press the reboot button

I recompiled the kernel with all MTP things switched off, and that booted.

However, normally it should be compiled everything in the kernel, and the kernel
during booting should manage it to see and to use what is existent in the computer
of the user, without to stick or to crash.

Probably that is an error already sine time in the kernel, not a recent regression.

Better to make a command-line option to can switch off mtp device search on booting

wl

=================================================
I have problems to post something from my home computer site  guyane.yi.org or SYS-Linux.yi.org :

Deferred: 451 4.7.1 Hello [93.121.138.180], for recipient address the policy analysis reported: Greylisted, see
http://isg.ee.ethz.ch/tools/postgrey/help/vger.kernel.org.html
---
Professional hosting for everyone - http://www.host.ru

author
#2 lore raw

3.0 version number: good to make links ; linux utils: correct fdisk, rdev

I read people have problems with the 3.0 vs. 3.0.0 kernel version.

I also think that the version of the package and internelly that of the kernel should be equal.

However, that's not a real problem. It's suficient to make just links. With this, everything works completely normal, also depmod etc. , since 3.0-rc1

Although this is trivial, because of the big discusion about this, one should tell this the people. Simply put in the kernel slackbuild script, to make such links, always if the package / source .bz2 number is diferent to the version number in makefile. Also in the kernel source makefile should be included to make auch links automatically always if the package and kernel version numbers are different.

What however seems to be removed from the linux kernel tools, is rdev . That should be put back, because that's important, specially for building distro kernels, to put in vmlinuz the bootdev to 0x80 and videomod 0 as default (and also for the installer on the user's computer, which adapt it to the user's computer)

There is a next problem that recent versions of fdisk starts only with sector 2048 for the 1st partition. This gives problems, because some systems needs to start with sector 63 or 129. This also should be return as it was.

wl

in /usr/src:
0 lrwxrwxrwx 1 root root 23 Jun 14 00:55 linux-3 ->
linux-3.0-rc3-i486-1sys
0 lrwxrwxrwx 1 root root 23 Jun 14 00:55 linux-3.0
-> linux-3.0-rc3-i486-1sys
4 drwxr-xr-x 2 root root 4096 Jun 14 01:16
linux-3.0-rc2-i486-1sys
0 lrwxrwxrwx 1 root root 23 Jun 14 00:55
linux-3.0-rc3 -> linux-3.0-rc3-i486-1sys
4 drwxr-xr-x 24 root root 4096 Jun 14 00:55
linux-3.0-rc3-i486-1sys
0 lrwxrwxrwx 1 root root 23 Jun 14 00:55
linux-3.0.0 -> linux-3.0-rc3-i486-1sys
0 lrwxrwxrwx 1 root root 23 Jun 14 00:55
linux-3.0.0-rc3 -> linux-3.0-rc3-i486-1sys
0 lrwxrwxrwx 1 root root 23 Jun 14 00:55
linux-3.0.0-rc3-i486-1sys -> linux-3.0-rc3-i486-1sys in /lib/modules

0 lrwxrwxrwx 1 root root   19 Jun 14 00:55 3 -> 3.0.0-rc3-i486-1sys
0 lrwxrwxrwx 1 root root   30 Jun 14 00:55 3.0 -> /lib/modules/3.0-rc3-i486-1sys
0 lrwxrwxrwx 1 root root   19 Jun 14 00:55 3.0-rc3 -> 3.0.0-rc3-i486-1sys
0 lrwxrwxrwx 1 root root   19 Jun 14 00:55 3.0-rc3-i486-1sys -> 3.0.0-rc3-i486-1sys
0 lrwxrwxrwx 1 root root   19 Jun 14 00:55 3.0.0 -> 3.0.0-rc3-i486-1sys
0 lrwxrwxrwx 1 root root   19 Jun 14 00:55 3.0.0-rc3 -> 3.0.0-rc3-i486-1sys

4 drwxr-xr-x 3 root root 4096 Jun 14 22:09 3.0.0-rc3-i486-1sys

bash-4.1# depmod -av | less
WARNING: terminal is not fully functional /lib/modules/3.0.0-rc3-i486-1sys/kernel/drivers/bluetooth/bluecard_cs.ko needs "hci_free_dev":
/lib/modules/3.0.0-rc3-i486-1sys/kernel/net/bluetooth/bluetooth.ko /lib/modules/3.0.0-rc3-i486-1sys/kernel/drivers/bluetooth/bluecard_cs.ko needs "hci_alloc_dev":
/lib/modules/3.0.0-rc3-i486-1sys/kernel/net/bluetooth/bluetooth.ko
/lib/modules/3.0.0-rc3-i486-1sys/kernel/drivers/bluetooth/bluecard_cs.ko needs "hci_unregister_ dev": /lib/modules/3.0.0-rc3-i486-1sys/kernel/net/bluetooth/bluetooth.ko /lib/modules/3.0.0-rc3-i486-1sys/kernel/drivers/bluetooth/bluecard_cs.ko needs "hci_recv_frame" : /lib/modules/3.0.0-rc3-i486-1sys/kernel/net/bluetooth/bluetooth.ko /lib/modules/3.0.0-rc3-i486-1sys/kernel/drivers/bluetooth/bluecard_cs.ko needs "hci_register_de v": /lib/modules/3.0.0-rc3-i486-1sys/kernel/net/bluetooth/bluetooth.ko /lib/modules/3.0.0-rc3-i486-1sys/kernel/drivers/bluetooth/bfusb.ko needs "hci_free_dev": /lib/m odules/3.0.0-rc3-i486-1sys/kernel/net/bluetooth/bluetooth.ko /lib/modules/3.0.0-rc3-i486-1sys/kernel/drivers/bluetooth/bfusb.ko needs "hci_alloc_dev": /lib/ modules/3.0.0-rc3-i486-1sys/kernel/net/bluetooth/bluetooth.ko /lib/modules/3.0.0-rc3-i486-1sys/kernel/drivers/bluetooth/bfusb.ko needs "hci_unregister_dev":
/lib/modules/3.0.0-rc3-i486-1sys/kernel/net/bluetooth/bluetooth.ko /lib/modules/3.0.0-rc3-i486-1sys/kernel/drivers/bluetooth/bfusb.ko needs "hci_recv_frame": /lib /modules/3.0.0-rc3-i486-1sys/kernel/net/bluetooth/bluetooth.ko /lib/modules/3.0.0-rc3-i486-1sys/kernel/drivers/bluetooth/bfusb.ko needs "hci_register_dev": /l ib/modules/3.0.0-rc3-i486-1sys/kernel/net/bluetooth/bluetooth.ko /lib/modules/3.0.0-rc3-i486-1sys/kernel/drivers/bluetooth/btusb.ko needs "hci_free_dev": /lib/m odules/3.0.0-rc3-i486-1sys/kernel/net/bluetooth/bluetooth.ko /lib/modules/3.0.0-rc3-i486-1sys/kernel/drivers/bluetooth/btusb.ko needs "hci_alloc_dev": /lib/ modules/3.0.0-rc3-i486-1sys/kernel/net/bluetooth/bluetooth.ko /lib/modules/3.0.0-rc3-i486-1sys/kernel/drivers/bluetooth/btusb.ko needs "hci_unregister_dev":
/lib/modules/3.0.0-rc3-i486-1sys/kernel/net/bluetooth/bluetooth.ko /lib/modules/3.0.0-rc3-i486-1sys/kernel/drivers/bluetooth/btusb.ko needs "hci_recv_fragment": / lib/modules/3.0.0-rc3-i486-1sys/kernel/net/bluetooth/bluetooth.ko /lib/modules/3.0.0-rc3-i486-1sys/kernel/drivers/bluetooth/btusb.ko needs "hci_register_dev": /l ib/modules/3.0.0-rc3-i486-1sys/kernel/net/bluetooth/bluetooth.ko /lib/modules/3.0.0-rc3-i486-1sys/kernel/drivers/bluetooth/btmrvl.ko needs "hci_free_dev": /lib/ bash-4.1#

(only the first lines, via konsole)
---
Professional hosting for everyone - http://www.host.ru