create extended partition
by Patrick Dupre
Hello,
TRying to recover one of the disk;
I now have
Disk /dev/sdc: 76.3 GiB, 81964302336 bytes, 160086528 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: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdc1 6008310 6622709 614400 300M 83 Linux
/dev/sdc2 6623232 37242879 30619648 14.6G 83 Linux
/dev/sdc3 * 37244928 49821695 12576768 6G 83 Linux
There is a gap between sdc2 and sdc3,
I guess that it is a partition that I could recover.
But I first need to create an extended partition.
how can I do it?
Thank.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
6 years, 9 months
Anyone with a working GTX 960 video card in f26?
by Tom Horsley
I just tried booting a newly installed workstation fedora 26
system. I have this video card:
01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1)
The gome3 login screen comes up OK, but as soon as I
try to actually login, the screen goes to some wavy
pointilist looking thing and seems to freeze up.
I had to hit the reset button to get the system back.
I've tried no experimenting yet, but for a guess
wayland, nouveau, and the 960 don't hit it off very well
(and maybe the UHD resolution monitor contributes as well).
When I have a chance to fool with this tomorrow, I'll
try forcing an X11 login instead of wayland. Right now
I just set it to multi-user.target and am using the
text console when I boot to f26.
6 years, 9 months
find exec rm
by bruce
hey guys..
i'm missing something. thoughts/comments?
trying to do a rm with find/exec.
ssh crawl_user(a)1.2.3.4 " rm -f '/cloud_nfs/*hash*.dat' ; find
/cloud_nfs -name '*austincc*master*book*.dat' -exec rm {} \; rm -f
'/cloud_nfs_fetch/*hash*.dat' ; "
i get
find: paths must precede expression: rm
Usage: find [-H] [-L] [-P] [-Olevel] [-D
help|tree|search|stat|rates|opt|exec] [path...] [expression]
can't seem to see my error...
however, if I remove the last rm -- the find/exec/rm works..
thanks
6 years, 9 months
Can't change plymouth theme
by Sam Varshavchik
The -R option to plymouth-set-default-theme appears to do absolutely nothing
whatsoever. It grinds away, for a few seconds, but when it's done and over,
the initramfs in /boot remains completely untouched.
Running plymouth-set-default-theme tells me that the theme has been changed.
plymouth simply fails to rebuilt the initramfs.
It looks to me like plymouth is being neglected, to some degree. There are a
bunch of bugs in Bugzilla that's been open for years, with nothing happening
on them.
I am not a big fan of the default plymouth theme. It's quite boring, and
simply reminds me how long it takes for Fedora to boot. At least solar was
somewhat entertaining to watch, while various bits were coming alive…
But in F25, the solar theme was mostly broken. One of my laptops completely
refused to boot, with the solar theme. Had to reluctantly reset it back to
charge.
Another laptop did manage to survive F25's solar, but, basically, solar's
grapics suffered from Tourette's syndrome, all the way through. I reported
that bug. Someone else confirmed it, and that's one of the open plymouth
bugs, gathering dust, that I mentioned.
So now, I wanted to take the laptop that tolerated solar somewhatm in F25,
and see what's up with F26's solar. But, because of another bug, that's so
old that I can't even find it anymore, every time the plymouth rpm gets
updated the default theme gets rather rudely reinstalled, so I have to run
plymouth-set-default-theme -R, to rebuild the initramfs.
But now, -R doesn't work for me. Well it still runs, but simply fails to
rebuild the initramfs, without complaining about anything. I see nothing
with any updated timestamp, in /boot. The initramfs there has not been
rebuilt.
Oh well, just created another plymouth bug, I guess, to join the rest of
them, gathering dust. Since plymouth-set-default-theme did set the default
theme for future kernel installs, I guess I'll discover the results of this
latest experiment the next time I update the kernel.
6 years, 9 months
Fedora 25->26 upgrade kills second monitor: arandr also stops
working
by Ranjan Maitra
Hello,
My second monitor has stopped working after an upgrade to Fedora 26 using dnf system-upgrade.
Also, arandr is busted: here is what I get.
$ arandr
Traceback (most recent call last):
File "/bin/arandr", line 42, in <module>
main()
File "/usr/lib/python2.7/site-packages/screenlayout/gui.py", line 318, in main
force_version=options.force_version
File "/usr/lib/python2.7/site-packages/screenlayout/gui.py", line 157, in __init__
self.widget = widget.ARandRWidget(display=randr_display, force_version=force_version)
File "/usr/lib/python2.7/site-packages/screenlayout/widget.py", line 48, in __init__
self._xrandr = XRandR(display=display, force_version=force_version)
File "/usr/lib/python2.7/site-packages/screenlayout/xrandr.py", line 42, in __init__
raise Exception("XRandR 1.2/1.3 required.")
Exception: XRandR 1.2/1.3 required.
And here is the output from xrandr:
$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 16384 x 16384
DVI-I-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 519mm x 324mm
1920x1200 59.95*+
1600x1200 65.00 60.00
1400x1050 74.76 59.98
1280x1024 75.02 60.02
1280x960 60.00
1152x864 75.00
1024x768 75.05 60.04 75.03 70.07 60.00
960x720 75.00 60.00
928x696 75.00 60.05
896x672 75.05 60.01
832x624 74.55
800x600 75.00 70.00 65.00 60.00 72.19 75.00 60.32 56.25
700x525 74.76 59.98
640x512 75.02 60.02
640x480 60.00 75.00 72.81 75.00 59.94
720x400 70.08
576x432 75.00
512x384 75.03 70.07 60.00
416x312 74.66
400x300 72.19 75.12 60.32 56.34
320x240 72.81 75.00 60.05
DP-1 disconnected (normal left inverted right x axis y axis)
Why is the second one disconnected above? It was fine (and connected) before the upgrade.
Any suggestions as to what I should be trying?
Many thanks for your help, and best wishes,
Ranjan
--
Important Notice: This mailbox is ignored: e-mails are set to be deleted on receipt. Please respond to the mailing list if appropriate. For those needing to send personal or professional e-mail, please use appropriate addresses.
6 years, 9 months
vlc on F25 broken.
by Erik P. Olsen
Running vlc on fully upgraded F25 is broke:
[erik@Erik-PC ~]$ vlc
VLC media player 3.0.0-git Vetinari (revision 2.2.0-git-13163-g351b63f476)
[00005573948351a0] core libvlc: VLC kører med standardbrugerfladen. Brug "cvlc" for at køre VLC uden brugerflade.
[00005573948c7d70] core playlist: playlist is empty
[00005573948c7d70] core playlist: end of playlist, exiting
QObject::~QObject: Timers cannot be stopped from another thread
Downgrading vlc makes it work again.
--
Regards,
Erik P. Olsen
6 years, 9 months
/dev/loop
by Patrick Dupre
Hello,
On the save USB key, I have 3 partitions,
Disk /dev/sdc: 59.6 GiB, 64019759104 bytes, 125038592 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: 0x1780cf97
Device Boot Start End Sectors Size Id Type
/dev/sdc1 * 1050624 5244927 4194304 2G c W95 FAT32 (LBA)
/dev/sdc2 5244928 125038591 119793664 57.1G 5 Extended
/dev/sdc5 5246976 7344127 2097152 1G 83 Linux
/dev/sdc6 7346176 125038591 117692416 56.1G 83 Linux
Why the /dev/sdc6 mount as
/dev/loop3 3883252 7832 3658444 1% /run/media/pdupre/Lexar_encr
which a wrong size ?
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
6 years, 9 months
Oh oh. I screwed up my F26 installation. Help keep me from
destroying everything....
by vendor@billoblog.com
So, I decided to do a clean installation of F26 over my F25
installation. My old configuration was:
Dual boot HP laptop: Win 10, F25.
F25 had an encrypted /home partition, a separate /swap partition (I know
I don't have to have one, but I'm old), and an unencrypted / partition
where, I thought, /boot/efi lived.
I do the installation using the GUI from "Install to Hard Drive" on the
USB live distro ((KDE spin), and choose "delete everything associated
with only F25." I am required to create a /boot/efi partition by the
GUI. So I do (I vaguely remembered that F25 was happy using the system
uefi partition, but I don't remember).
I install, and everything seems to go well.
Then I reboot, and my old F25 boot options come up (i.e. a list of F25
kernels and the Win 10 bootloader). Of course, it can no longer find
the F25 kernel. The Win 10 boots up fine.
So... I'm figuring I mis-configured where to put the boot directory, and
somehow it's finding the old one (which may well be in the system uefi
partition -- I don't remember).
The last time I had a problem with this, I ended up trying to move
directories by hand, and wrote over the Windows boot loader, which
caused me no end of headaches. I don't want to make that mistake again.
Here's what's on my hard drive:
sda1: "EFI system partition", containing BOOTSECT.BAK EFI
FSCK0000.REC FSCK0001.REC FSCK0002.REC FSCK0003.REC FSCK0004.REC
mach_kernel System 'System Volume Information' 260 MB
sda2: Microsoft reserved partition (I can't mount it) 128 MB
sda3: Windows data partition 103.42 GB
sda4: Windows recovery partition 731 MB
sda5: Windows recovery partition (another one, apparently) 25.43 GB
sda6: This looks like my old F25 boot partition (I thought it was
deleted) 18 GB It contains:
config-4.8.16-300.fc25.x86_64
config-4.9.3-200.fc25.x86_64
config-4.9.5-200.fc25.x86_64
efi
elf-memtest86+-5.01
extlinux
grub2
initramfs-0-rescue-95f65550951744038812b588382884c8.img
initramfs-4.8.16-300.fc25.x86_64.img
initramfs-4.9.3-200.fc25.x86_64.img
initramfs-4.9.5-200.fc25.x86_64.img
initrd-plymouth.img
lost+found
memtest86+-5.01
System.map-4.8.16-300.fc25.x86_64
System.map-4.9.3-200.fc25.x86_64
System.map-4.9.5-200.fc25.x86_64
vmlinuz-0-rescue-95f65550951744038812b588382884c8
vmlinuz-4.8.16-300.fc25.x86_64
vmlinuz-4.9.3-200.fc25.x86_64
vmlinuz-4.9.5-200.fc25.x86_64
sda7: "EFI system partition" 23.28 GB. Ut contains:
EFI
mach_kernel
System
sda8: This looks like the F26 boot partition that is not being called.
9 G
9cd45473cdd74075934e438993760520
config-4.11.8-300.fc26.x86_64
efi
elf-memtest86+-5.01
extlinux
grub2
initramfs-0-rescue-ea56b271f5994ca7b63e2028c325a528.img
initramfs-4.11.8-300.fc26.x86_64.img
lost+found
memtest86+-5.01
System.map-4.11.8-300.fc26.x86_64
vmlinuz-0-rescue-ea56b271f5994ca7b63e2028c325a528
vmlinuz-4.11.8-300.fc26.x86_64
sda9: Encrypted /home partition, 760 GB
So, it looks like I've managed to create two System EFI partitions. Who
knew?
Two questions:
Is there a simple fix-by-hand for this?
If I have to re-install from the USB, what mistake did I make and how to
I not do it again?
Thanks!
billo
6 years, 9 months
Green screen error in VLC
by Paul Smith
Dear All,
This happens after upgrading from F25 to F26, when playing a video --
no image; only a green screen. Any ideas?
Thanks in advance,
Paul
6 years, 9 months