Quirky SlaQ 8.1.6 x86_64 released

[linuxcbon]

Code: Select all

# sfdisk -F /dev/sdb 
Unpartitioned space /dev/sdb: 2 GiB, 2109210624 bytes, 4119552 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Start     End Sectors Size
18432 4137983 4119552   2G

[BarryK]

I have tested with a flash stick, /dev/sdd:

Code: Select all

# cat /sys/block/sdd/sdd2/start
1064960
# cat /sys/block/sdd/sdd2/size
13418496
# expr 1064960 + 13418496
14483456
# sfdisk -F /dev/sdd
Unpartitioned space /dev/sdd: 327 MiB, 342867456 bytes, 669663 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

   Start      End Sectors  Size
    2048     2048       0    0B
 1050624  1064959   14336    7M
14483456 15138782  655327  320M
# 

And I get exactly what I expect, and what is correct. /sys reports a start sector and size of sdd2, add those together and have the start of the unused space, 14483456.

Then I ran "sfdisk -F /dev/sdd", which reports all the unused spaces, and you can see the section of unused space starting at sector 14483456.

QuickSetup thus works for me.

I request more feedback on this. From anyone who does not get that checkbox offering to resize the partition, can you please run the same as I have done above, substituting the correct drive letters.

[linuxcbon]

Code: Select all

# cat /sys/block/sdb/sdb2/start 
136
# cat /sys/block/sdb/sdb2/size 
16384
# expr 136 + 16384
16520
# sfdisk -F /dev/sdb
Unpartitioned space /dev/sdb: 2 GiB, 2109210624 bytes, 4119552 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Start     End Sectors Size
18432 4137983 4119552   2G

[BarryK]

T2 for Pi? How many hours are there in the day? I do have a life, apart from Quirky development. I will get back to the Pi sometime.

I need to unwind. The bugs have been never ending, and for the last week i have been thinking that SlaQ is ready for release, then find more bugs, then more... and of course after releasing, yet more...

But then Quirky was never really intended to be a polished "final product". A big break is immanent, then will continue thinking about the next-gen Quirky.

[Sage]

8.1.6 .iso:
Already advised BK. They (supra) are correct; RoW runs on CD/DVD .iso and will continue to do so for reasons given and many more.

Very long delay ~10min at video command during boot up. Eventually got a black screen. First attempt at CTL-ALT-BKSPCE did nothing initially then the cursor came up at ~5min. Second C_T_B brought up the xorgwizard option . With a bit of juggling was able to get a successful opening screen. Nearly everything seems to be working - even FlashPlayer!
Sound not working, though, and couldn't coax it to do so using available utilities - neither hdmi nor ALSA.
Unfortunately didn't have anything connected nor available to connect to install a version so will have to suffer a new restart.

Incidentally, ref. to pfix above should now be qfix?

[BarryK]

Code: Select all

# cat /sys/block/sdb/sdb2/start 
136
# cat /sys/block/sdb/sdb2/size 
16384
# expr 136 + 16384
16520
# sfdisk -F /dev/sdb
Unpartitioned space /dev/sdb: 2 GiB, 2109210624 bytes, 4119552 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Start     End Sectors Size
18432 4137983 4119552   2G

Very interesting, thanks for reporting that promptly. Would you also report the result of this:

# fdisk -u -l /dev/sdb

...that's fdisk, not sfdisk!

[linuxcbon]

Code: Select all

# fdisk -u -l /dev/sdb 
Disk /dev/sdb: 2 GiB, 2118647808 bytes, 4137984 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x71039dee

Device     Boot Start    End Sectors  Size Id Type
/dev/sdb1  *        0 622591  622592  304M  0 Empty
/dev/sdb2         136  16519   16384    8M ef EFI (FAT-12/16/32)

[Billtoo]

I installed the devx pet and have compiled a few
programs,lxterminal,cmus,mplayer-1.3.0,Smplayer and Smtube.
I found that some SlackBuilds from my Slackware64-14.2 install and work,
also lxrandr from Fatdog64-710.
I couldn't get Google Chrome from Fatdog working though.

I haven't tried the snapshot utility yet.

Thanks.

I took a snapshot, it seems to have worked fine, it created a 3.5GB sys file.

[Rodney Byne]

Hi to Sage,

Re your earlier line about Flashplayer working, while hoping
I've got your meaning correctly, I see that Seamonkey 2.46
already has flashplayer built in for browsing, so there's no need
anymore to install to Tools/Add-on, the version obtainable in
Menu/Internet or from OscarTalks Index.

I found out recently that FirefoxESR has the same facility now,
so it seems some browsers are following Chromium's lead with Pepperflash.

For me that's great because I can watch UK's BBC News Channel
without effort.

Best regards.

[Sage]

RB: yes, built-in, ootb. BBC iPlayer works.
Still unable to activate sound. Retrovol doesn't show options with sliders like the previous versions?

[TeX Dog]

Whoa there, Hoss! seem to kick over a hornets nest. Snapshot= (pic of desktop) not the new fangled reuse of the term. Can’t find the resulting pic,gif,png etc to upload.
T2 and LFS are the only built systems I have good use/knowledge of inter-workings, T2 is setup-ible for distributed compile across multiple hardware, surprised it takes more than a day, unless you like to single computer compile.
DVD multisession existed in older Puppylinux worked well, BIOS problems do not exist in my desktop DVDs or Macs, which is what I use most for evaluations. My ‘post count’ does not equal my decade + work with PuppyLinux.
I kinda know more about multi session and optical drives, came out of forced Forum retirement just to post fixes for BluRay/DVD multisession in FatDog.

[BarryK]

Code: Select all

# fdisk -u -l /dev/sdb 
Disk /dev/sdb: 2 GiB, 2118647808 bytes, 4137984 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x71039dee

Device     Boot Start    End Sectors  Size Id Type
/dev/sdb1  *        0 622591  622592  304M  0 Empty
/dev/sdb2         136  16519   16384    8M ef EFI (FAT-12/16/32)

Very interesting! This is confirming, the second partition has last sector 16519, which means the unused space starts at 16520, which agrees with your earlier post.

But sfdisk is reporting unused space starts at sector 18432.

Hmmm. I wonder what Gparted reports?

Anyway, I can probably take this error into account.

Got it!

What sfdisk is doing, is rounding-up to the nearest 1MB boundary.

16520 sectors is 8.066MB
18432 sectors is 9.0MB

Good, I can handle that in the code. Thanks for posting that info, it enabled me to solve the mystery.

At least in your case. For the others who did not get the resize-checkbox, I still don't know why, as the 8GB drive image has the second partition ending on a 8MB boundary, so sfdisk will not do any rounding up.

[linuxcbon]

Hmmm. I wonder what Gparted reports?.

gparted also reports unused space starts at 16520, like fdisk. Mystery solved for me

[prehistoric]

Here's a clue about that other mystery. Gparted has a strange report when it looks at a 32 GB flash drive used for installing SlaQ via that commandline. The partition is said to be 27.12 GB, but the sum of used and unused is what I would expect if the filesystem had not been expanded. I'm also a little mystified about the 1.26 GB left at the end of the device.

[BarryK]

Here's a clue about that other mystery. Gparted has a strange report when it looks at a 32 GB flash drive used for installing SlaQ via that commandline. The partition is said to be 27.12 GB, but the sum of used and unused is what I would expect if the filesystem had not been expanded. I'm also a little mystified about the 1.26 GB left at the end of the device.

Yeah, that 1.2GB is another odd thing. It is something to do with sfdisk again. I am using sfdisk to determine the size of unused space, which is used to resize the partition. However, in the case of 32GB Flash drives, sfdisk is getting it wrong.

If you run, before having done the resizing:

# sfdisk -F /dev/sdf

it is misreporting the size of unused space after partition#2.

prehistoric,
With your current sdf drive, with that 1.2GB left over, what does that sfdisk command report about unused space?

[BarryK]

Here's a clue about that other mystery. Gparted has a strange report when it looks at a 32 GB flash drive used for installing SlaQ via that commandline. The partition is said to be 27.12 GB, but the sum of used and unused is what I would expect if the filesystem had not been expanded. I'm also a little mystified about the 1.26 GB left at the end of the device.

Oh, and that other thing. Your partition has been increased, but not the filesystem.

The resize operation first deletes the second partition then recreates it, bigger.

It then does a f.s. check, and then runs 'resize2fs' to increase the ext4 f.s. to fill the partition.

Somehow, this latter step has not worked for you. Which puzzles me immensely, as it works for me.

The script that does this magic is /sbin/fscheck, found by clicking on /boot/easyinit

[Sage]

Above refers: apart from sound issue, other delays, etc seem to be machine specific. Shouldn't happen, but as we all know - it does. [Nothing intrinsically wrong with machine, though.]

[linuxcbon]

Quirky SlaQ 8.1.6 x86_64

- jwmrc not correct. That's why startup programs (network tray, retrovol) don't appear in tray.

Code: Select all

Generating /root/.icewm/menu...
mv: cannot move '/root/.icewm/menu' to a subdirectory of itself, '/root/.icewm/menu-previous'
Generating /root/.jwmrc...
mv: cannot move '/root/.jwmrc' to a subdirectory of itself, '/root/.jwmrc-previous'

Code: Select all

# jwm -p    
JWM: warning: /root/.jwmrc[423]: close tag "Program" does not match open tag "?xml" 

[prehistoric]

Here's the output from sfdisk. I was careful to use the sfdisk actually in SlaQ.

Code: Select all

# sfdisk -F /dev/sdg
Unpartitioned space /dev/sdg: 1.3 GiB, 1355005440 bytes, 2646495 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

   Start      End Sectors  Size
    2048     2048       0    0B
 1050624  1064959   14336    7M
57933824 60565982 2632159  1.3G
#

Another possible complication, this flash drive was not pristine, it had been used for previous installations. I ran the command line code exactly as shown, except for the change in filename and drive. I did sync afterward, and I unmounted the drive before removing it. I did not zero everything as that takes a long time on a 32 GB drive.

[prehistoric]

Here's another clue: this machine is one of those which reports it was unable to access the hardware clock. Also reports errors about not being able to delete two directories because not empty.

I ran dmesg to see the state during boot, and found a problem with syncing the cache on a scsi device. There is only one block device on the test machine, the flash drive, as I have disconnected hard drive and SSD.