Page 21 of 21 « First 111920 21
Reply
Thread Tools
wolke is offline wolke
2020-04-29 , 06:29
Posts: 980 | Thanked: 1,512 times | Joined on Jul 2010
#201
previous problem had an easy solution (just install readline rpm).

now ive got another problem. inner patch seems to apply correctly in chroot, but repacking the image files fails.

(note that the zip file is built, but is only half the size of the source zip file)

Code:
I: Syncing back the patched tree
I: Repacking
/tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.3.0.16-f5121-0.2.1.25/patcher-tmp/work /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.3.0.16-f5121-0.2.1.25
0+0 records in
0+0 records out
0 bytes copied, 0.000164125 s, 0.0 kB/s
  Physical volume "/dev/loop0" successfully created.
  Volume group "sailfish" successfully created
e2fsck 1.43.4 (31-Jan-2017)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/loop1: 25063/116640 files (0.1% non-contiguous), 264442/466176 blocks
We got ourselves root blocks _ 398289 _
after maths size _ 1631391744 _
  Rounding up size to full physical extent 1.52 GiB
  Logical volume "root" created.
  1 logical volume(s) in volume group "sailfish" now active
398289+0 records in
398289+0 records out
1631391744 bytes (1.6 GB, 1.5 GiB) copied, 7.78859 s, 209 MB/s
e2fsck 1.43.4 (31-Jan-2017)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
home: 83/7328 files (3.6% non-contiguous), 13285/16198 blocks
We got ourselves home size _ 13290 _
  Rounding up size to full physical extent 52.00 MiB
  Logical volume "home" created.
  2 logical volume(s) in volume group "sailfish" now active
13290+0 records in
13290+0 records out
54435840 bytes (54 MB, 52 MiB) copied, 0.163591 s, 333 MB/s
  0 logical volume(s) in volume group "sailfish" now active
1+0 records in
1+0 records out
1 byte copied, 0.00015447 s, 6.5 kB/s
Usage: mkfs.ext4 [-c|-l filename] [-b block-size] [-C cluster-size]
	[-i bytes-per-inode] [-I inode-size] [-J journal-options]
	[-G flex-group-size] [-N number-of-inodes] [-d root-directory]
	[-m reserved-blocks-percentage] [-o creator-os]
	[-g blocks-per-group] [-L volume-label] [-M last-mounted-directory]
	[-O feature[,...]] [-r fs-revision] [-E extended-option[,...]]
	[-t fs-type] [-T usage-type ] [-U UUID] [-e errors_behavior][-z undo_file]
	[-jnqvDFSV] device [blocks-count]
e2fsck 1.43.4 (31-Jan-2017)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open fimage.img

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
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>
 or
    e2fsck -b 32768 <device>

resize2fs 1.43.4 (31-Jan-2017)
resize2fs: Bad magic number in super-block while trying to open fimage.img
Couldn't find valid filesystem superblock.
mount: wrong fs type, bad option, bad superblock on /dev/loop1,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
umount: /tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.3.0.16-f5121-0.2.1.25/patcher-tmp/work/tmp.Y3VaMPjpIX: not mounted
rmdir: failed to remove '/tmp/sailfish-image-patcher/Sailfish_OS-Jolla-3.3.0.16-f5121-0.2.1.25/patcher-tmp/work/tmp.Y3VaMPjpIX': Directory not empty
e2fsck 1.43.4 (31-Jan-2017)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open fimage.img

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
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>
 or
    e2fsck -b 32768 <device>

resize2fs 1.43.4 (31-Jan-2017)
resize2fs: Bad magic number in super-block while trying to open fimage.img
Couldn't find valid filesystem superblock.
__________________
~ teleshoes ~
 

The Following User Says Thank You to wolke For This Useful Post:
wolke is offline wolke
2020-04-29 , 19:20
Posts: 980 | Thanked: 1,512 times | Joined on Jul 2010
#202
ok fixed it, see https://github.com/g7/sailfishx-patcher-f5321/pull/14
__________________
~ teleshoes ~
 

The Following User Says Thank You to wolke For This Useful Post:
N77 is offline N77
2020-05-27 , 04:25
Posts: 13 | Thanked: 40 times | Joined on May 2020
#203
Hey guys I need some help if possible.

I am not a software coder but I managed to follow g7 guide from here:
https://github.com/g7/sailfishx-patcher-f5321
and install Sailfish on the X compact.

Now, I was looking at what Vknecht posted on:
http://merproject.org/logs/%23sailfi...05-02.log.html
respectively:

https://build.merproject.org/project...qualcomm:f5121

also a pie based port which works better, but only boots correctly sometimes:
https://build.merproject.org/project...:hw:sony:loire

because of:
https://github.com/sonyxperiadev/dev...6c494ecad6875e

I would like to try any of these ports but I need some guidance like step by step sequence of actions. I have Ubuntu machine which I think is needed (Windows 7 as well). Any help would be appreciated.
 

The Following 3 Users Say Thank You to N77 For This Useful Post:
Sheigorath is offline Sheigorath
2020-09-21 , 20:02
Posts: 1 | Thanked: 2 times | Joined on Mar 2020
#204
Originally Posted by N77 View Post
Hey guys I need some help if possible.

I am not a software coder but I managed to follow g7 guide from here:
https://github.com/g7/sailfishx-patcher-f5321
and install Sailfish on the X compact.

Now, I was looking at what Vknecht posted on:
http://merproject.org/logs/%23sailfi...05-02.log.html
respectively:

https://build.merproject.org/project...qualcomm:f5121

also a pie based port which works better, but only boots correctly sometimes:
https://build.merproject.org/project...:hw:sony:loire

because of:
https://github.com/sonyxperiadev/dev...6c494ecad6875e

I would like to try any of these ports but I need some guidance like step by step sequence of actions. I have Ubuntu machine which I think is needed (Windows 7 as well). Any help would be appreciated.
Is there any news about new ports for Compact?
 

The Following 2 Users Say Thank You to Sheigorath For This Useful Post:
Manatus is offline Manatus
2020-10-01 , 12:06
Posts: 334 | Thanked: 616 times | Joined on Sep 2010
#205
I updated Eugenio's (g7) port to 3.4.0.22 on X Compact. No issues spotted.
 

The Following 3 Users Say Thank You to Manatus For This Useful Post:
smatkovi is offline smatkovi
2020-10-21 , 19:50
Posts: 157 | Thanked: 194 times | Joined on Apr 2012 @ Austria
#206
this should be the solution, at least it helped on my mothers xperia x compact https://together.jolla.com/question/...post-id-199698
Originally Posted by eugenio View Post
What's the output of

Code:
systemctl --user status pulseaudio
Have you tried running the upgrade again via command line?
Code:
devel-su
ssu re 3.3.0.14
version --dup
FWIW my X Compact works fine, even though the upgrade failed mid-way (but it doesn't seem related to the patch).
I also have encryption enabled, but since 3.2.0.

========================
EDIT: Now that I remember, I had to mask pulseaudio's system wide service after enabling encryption back then. Pulseaudio is normally started in the user session, but after encryption is enabled is started system-wide so that it's possible to route audio when taking emergency calls from the encryption unlock screen (I guess).

Not sure what is wrong, I thought it was due to encryption being a work in progress on 3.2.0 so I haven't complained But it seems to be an issue on 3.3.0 too, then.

You can mask pulseaudio using this command:

Code:
systemctl mask pulseaudio
 

The Following User Says Thank You to smatkovi For This Useful Post:
Reply
Page 21 of 21 « First 111920 21

« Previous Thread | Next Thread »
Thread Tools

 
Forum Jump


All times are GMT. The time now is 07:37.

Contact Us - Home - Archive - Top