How to mount opt folder? - maemo.org

Active Topics

Is there a section to talk about Java ME? Apps, etc. (0)
to General by Kalatti - 1 day, 12 hrs ago
Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 3 days, 9 hrs ago
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 4 days, 5 hrs ago
more...

Page 1 of 5

Next >

Last »

Thread Tools

NotMicro	2016-01-05 , 13:18
Posts: 111 \| Thanked: 50 times \| Joined on May 2015	#1

Could anybody write precisely how to mount opt folder from second emmc partition under rescueOS by NIN101? Or how to uninstall package using dpkg -r (or -P) with no access to that folder.

Last edited by NotMicro; 2016-01-05 at 13:38.

Quote & Reply |

michaaa62	2016-01-05 , 22:11
Posts: 2,102 \| Thanked: 1,937 times \| Joined on Sep 2008 @ Berlin, Germany	#2

These commands inside the rescueOS shell mount:
1. first the maemo rootfs,
2. second the optfs partition to the home directory of maemo rootfs,
3. third the opt directory inside the maemo rootfs

Code:

mmr
mount /dev/mmcblk0p2 /mnt/maemo/home
mount -o bind /mnt/maemo/home/opt /mnt/maemo/opt

Quote & Reply |

The Following 4 Users Say Thank You to michaaa62 For This Useful Post:
Halftux, NotMicro, peterleinchen, pichlo

michaaa62	2016-01-06 , 07:22
Posts: 2,102 \| Thanked: 1,937 times \| Joined on Sep 2008 @ Berlin, Germany	#3

Btw. it might be sufficient to erase the file /etc/modprobe.d/fcam.conf according to its content:

~ $ cat /etc/modprobe.d/fcam.conf
# Override configuration file for the FCam camera control API replacement kernel modules for the N900 camera subsystem.
# Remove this file and reboot to restore use of the original kernel modules.

install fcam modprobe fcam-vanilla; modprobe fcam-power; echo "-1" > /proc/sys/kernel/sched_rt_runtime_us

install fcam-vanilla /sbin/insmod /usr/share/fcam/isp-mod.ko && /sbin/insmod /usr/share/fcam/omap34xxcam-mod.ko && /sbin/insmod /usr/share/fcam/omap_previewer_hack.ko && /sbin/insmod /usr/share/fcam/et8ek8.ko && /sbin/insmod /usr/share/fcam/board-rx51-camera.ko

install fcam-power /sbin/insmod /usr/share/fcam/power/isp-mod.ko && /sbin/insmod /usr/share/fcam/power/omap34xxcam-mod.ko && /sbin/insmod /usr/share/fcam/power/omap_previewer_hack.ko && /sbin/insmod /usr/share/fcam/power/et8ek8.ko && /sbin/insmod /usr/share/fcam/power/board-rx51-camera.ko

install isp-mod modprobe fcam
install omap34xxcam-mod modprobe fcam
install omap_previewer_hack modprobe fcam
install et8ek8 modprobe fcam

Quote & Reply |

NotMicro	2016-01-06 , 13:07
Posts: 111 \| Thanked: 50 times \| Joined on May 2015	#4

Originally Posted by michaaa62

These commands inside the rescueOS shell mount:
1. first the maemo rootfs,
2. second the optfs partition to the home directory of maemo rootfs,
3. third the opt directory inside the maemo rootfs
Code:
mmr
mount /dev/mmcblk0p2 /mnt/maemo/home
mount -o bind /mnt/maemo/home/opt /mnt/maemo/opt

Thank you very much. It works. But now I have next problem. When I have tried to remove (commands chroot /mnt/maemo/ then dpkg -P) application blessn900 (which may be the pre-reason of my problems), I got a message as follows:

"dsmesock_connect: No such file or directory
dpkg: error processing blessn900 (--purge)
subprocess pre-removal script returned error exit status 1
Failed to open connection to "session" message bus: (null)
Errors were encountered while processing"

Do you have any suggestions what to do next?

Quote & Reply |

NotMicro	2016-01-06 , 15:40
Posts: 111 \| Thanked: 50 times \| Joined on May 2015	#5

Additional: when I use df command I get information like this: rootfs 1k-blocks used: 11456 available: 0 use%: 100% .

Quote & Reply |

NotMicro	2016-01-06 , 16:01
Posts: 111 \| Thanked: 50 times \| Joined on May 2015	#6

When I have run fsck I got a message:

"The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>".

Quote & Reply |

michaaa62	2016-01-06 , 16:29
Posts: 2,102 \| Thanked: 1,937 times \| Joined on Sep 2008 @ Berlin, Germany	#7

Which file system did you try to repair/check ?

Did you mount additional resources of the running 'rescueOS' to the 'maemo' chroot environment, like that:

Code:

mount -o bind /dev/ /mnt/maemo/dev
mount -o bind /proc/ /mnt/maemo/proc
mount -o bind /sys/ /mnt/maemo/sys
mount -o bind /dev/pts /mnt/maemo/dev/pts

???

Last edited by michaaa62; 2016-01-06 at 18:44. Reason: Typos and mount points corrected...

Quote & Reply |

The Following User Says Thank You to michaaa62 For This Useful Post:
Halftux

NotMicro	2016-01-06 , 16:41
Posts: 111 \| Thanked: 50 times \| Joined on May 2015	#8

Originally Posted by michaaa62

Which file system did you try to repair/check ?

Did you mount additional resources of the running 'rescueOS' to the 'maemo' chroot environment, like that:
Code:
mount --bind /dev/ /mnt/dev
mount --bind /proc/ /mnt/proc
mount --bind /sys/ /mnt/sys
mount --bind /dev/pts /mnt/dev/pts
???

No, I did not. Any of the above.

Quote & Reply |

michaaa62	2016-01-06 , 17:00
Posts: 2,102 \| Thanked: 1,937 times \| Joined on Sep 2008 @ Berlin, Germany	#9

All of them, these are directories, that get created/populated at boot time, so the non-running maemo does not work correctly without.

But note the changes of the mount points in the former post, i edited! Sorry for that.