Hi All,
Anyone have a favorite PCIe card for USB-C that supports Fedora?
Many thanks,
-T
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
> On 27 Jul 2018 at 10:57, ToddAndMargo wrote:
>
> Subject: Re: clone
> To: users@lists.fedoraproject.org
> From: ToddAndMargo
> Date sent:Fri, 27 Jul 2018 10:57:46 -0700
> Send reply to:Community support for Fedora users
>
>
On 27 Jul 2018 at 10:57, ToddAndMargo wrote:
Subject:Re: clone
To: users@lists.fedoraproject.org
From: ToddAndMargo
Date sent: Fri, 27 Jul 2018 10:57:46 -0700
Send reply to: Community support for Fedora users
> On
On 07/27/2018 11:44 AM, Patrick Dupre wrote:
On 07/27/2018 11:19 AM, Patrick Dupre wrote:
On 07/27/2018 04:14 AM, Patrick Dupre wrote:
If I run a system on VolSys1-root, and if I run grub2-mkconfig
with
GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
in /etc/default/grub
I get in
On 07/27/2018 02:11 PM, Samuel Sieb wrote:
On 07/26/2018 11:42 AM, Frédéric wrote:
Has anyone tested the new kernel 4.17.7? Any issues during backups?
I don't know about backups, but so far I haven't had any random system
lockups like I was getting before.
4.17.7 has been solid for me as
On 07/27/2018 11:38 AM, Patrick Dupre wrote:
On 07/27/2018 08:14 AM, Patrick Dupre wrote:
During a upgdade fedora 26 TO 28, I am receiving a lot of
error messages:
pcieport severity=corrected.
During the upgrade, it is impossible to get the right information
The upgrade finished properly.
I
> On 07/27/2018 11:19 AM, Patrick Dupre wrote:
> >>
> >> On 07/27/2018 04:14 AM, Patrick Dupre wrote:
> >>> If I run a system on VolSys1-root, and if I run grub2-mkconfig
> >>> with
> >>> GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
> >>> in /etc/default/grub
> >>> I get in
>
> On 07/27/2018 08:14 AM, Patrick Dupre wrote:
> > During a upgdade fedora 26 TO 28, I am receiving a lot of
> > error messages:
> > pcieport severity=corrected.
During the upgrade, it is impossible to get the right information
The upgrade finished properly.
Now, things seem OK.
>
> The
On Fri, 2018-07-27 at 11:11 -0700, Samuel Sieb wrote:
> On 07/26/2018 11:42 AM, Frédéric wrote:
> > Has anyone tested the new kernel 4.17.7? Any issues during backups?
>
> I don't know about backups, but so far I haven't had any random system
> lockups like I was getting before.
Same here.
poc
On 07/27/2018 08:14 AM, Patrick Dupre wrote:
During a upgdade fedora 26 TO 28, I am receiving a lot of
error messages:
pcieport severity=corrected.
The full line would be more useful. Also, run "lspci" and see if you
can find out which device matches the id.
You can try adding "pci=noaer"
On 07/27/2018 11:19 AM, Patrick Dupre wrote:
On 07/27/2018 04:14 AM, Patrick Dupre wrote:
If I run a system on VolSys1-root, and if I run grub2-mkconfig
with
GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
in /etc/default/grub
I get in grub.cfg
linux16
On 07/27/2018 02:56 AM, Patrick Dupre wrote:
I just do not understand.
I made the cloned partition again.
The fstab is executed, but then it is stuck.
The relabeling is not executed.
I check the /boot
I get . . . in the graphics part
In the text part
The last displays are
Several Fails to
>
> On 07/27/2018 04:14 AM, Patrick Dupre wrote:
> > If I run a system on VolSys1-root, and if I run grub2-mkconfig
> > with
> > GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
> > in /etc/default/grub
> > I get in grub.cfg
> >
> > linux16 /vmlinuz-4.16.11-100.fc26.x86_64
On 07/27/2018 04:14 AM, Patrick Dupre wrote:
If I run a system on VolSys1-root, and if I run grub2-mkconfig
with
GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
in /etc/default/grub
I get in grub.cfg
linux16 /vmlinuz-4.16.11-100.fc26.x86_64 root=/dev/mapper/VolSys1-root ro
On 07/26/2018 11:42 AM, Frédéric wrote:
Has anyone tested the new kernel 4.17.7? Any issues during backups?
I don't know about backups, but so far I haven't had any random system
lockups like I was getting before.
___
users mailing list --
On 07/26/2018 05:21 PM, Patrick Dupre wrote:
Hello,
I did this ton of times, but this time, it does not work.
I even just did it last week on an EFI system without problem
Before updating my system (now in fedora 26), I cloned by using another live
system.
cp -a /root1 /root2 (after mke2fs)
cp
Hello,
During a upgdade fedora 26 TO 28, I am receiving a lot of
error messages:
pcieport severity=corrected.
Is it normal?
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Laboratoire de
On Tue, Jul 24, 2018 at 12:33:04PM -0700, Samuel Sieb wrote:
On 07/24/2018 12:13 PM, Joe Zeff wrote:
On 07/24/2018 11:55 AM, Samuel Sieb wrote:
Just try running "reboot". If that doesn't work, then run "sync"
and forcefully power off. This should be a very rare occurrence,
you probably
On Fri, 27 Jul 2018 13:20:34 +0200
Patrick Dupre wrote:
> Why I cannot make a chroot?
Because chroot only does the one disk, but a operational
system requires stuff like /dev and /proc.
Here's the critical bits of the chroot script I use
to make a chroot functional:
mount --bind /dev
Hello,
After I cloned (cp -a /root1 /root2).
I boot on /root1 (because I am unable to boot on /boot2).
and run
chroot /boot2 (after monting the partition), but I get:
Error, do this: mount -t proc proc /proc
/bin/basename: missing operand
Try '/bin/basename --help' for more information.
Error,
Hello,
If I run a system on VolSys1-root, and if I run grub2-mkconfig
with
GRUB_CMDLINE_LINUX="rd.lvm.lv=VolSys0/root nouveau.modeset=0"
in /etc/default/grub
I get in grub.cfg
linux16 /vmlinuz-4.16.11-100.fc26.x86_64 root=/dev/mapper/VolSys1-root ro
rd.lvm.lv=VolSys0/root nouveau.modeset=0
I just do not understand.
I made the cloned partition again.
The fstab is executed, but then it is stuck.
The relabeling is not executed.
I check the /boot
I get . . . in the graphics part
In the text part
The last displays are
Several Fails to start Journal Server
Starting Load/Save Screen
>> Has anyone tested the new kernel 4.17.7? Any issues during backups?
>
> Before kernerl 4.17.7, I had issues during my duplicity-based backups.
>
> With kernel 4.17.7, no issue to date.
> I've been testing it since its release in Fedora 28.
thanks, I think I will upgrade.
Regards,
F
>> Has anyone tested the new kernel 4.17.7? Any issues during backups?
> Define "backups.
I refer to the previous posts about broken backups. Personnaly I use
rsnapshot that uses rsync.
> I'm using it and had no issues using rsync to back up
> to an external drive on both a desktop machine and a
>
> On 07/26/2018 05:21 PM, Patrick Dupre wrote:
> > Before updating my system (now in fedora 26), I cloned by using another
> > live system.
> > cp -a /root1 /root2 (after mke2fs)
> > cp -a /boot1 /boot2
>
> > But, I cannot boot on /root2 (using the /boot1 or /boot2)
>
> What happens?
>
A
25 matches
Mail list logo
