On 6/6/19 1:22 PM, Richard Ryniker wrote:
Are either of those using EFI with secure boot? According to the bug
report, that's the trigger.
I believe you are right. To my surprise, after inspection of the BIOS
displays in the machine that does allow data access, I find no mention at
all of
>Are either of those using EFI with secure boot? According to the bug
>report, that's the trigger.
I believe you are right. To my surprise, after inspection of the BIOS
displays in the machine that does allow data access, I find no mention at
all of secure boot capability.
The machine that
On 6/6/19 11:34 AM, Richard Ryniker wrote:
This seems to depend on kernel version. On one F30 system it works:
while on another, with the latest (non-test) kernel, it fails:
Are either of those using EFI with secure boot? According to the bug
report, that's the trigger.
On 6/6/19 11:32 AM, pmkel...@frontier.com wrote:
On 6/6/19 14:25, Samuel Sieb wrote:
On 6/6/19 11:11 AM, pmkel...@frontier.com wrote:
On 6/6/19 13:45, Adam Williamson wrote:
Try it with enforcing=0 ?
I just tried permissive mode with the same result. I've just looked
through of the "files"
This seems to depend on kernel version. On one F30 system it works:
[root@yoga ryniker]# uname -r
5.0.17-300.fc30.x86_64
[root@yoga ryniker]# ls -l /sys/kernel/debug/usb/devices
-r--r--r--. 1 root root 0 May 30 09:59 /sys/kernel/debug/usb/devices
[root@yoga ryniker]# cat
On 6/6/19 14:25, Samuel Sieb wrote:
On 6/6/19 11:11 AM, pmkel...@frontier.com wrote:
On 6/6/19 13:45, Adam Williamson wrote:
On Thu, 2019-06-06 at 11:15 -0600, Chris Murphy wrote:
On Thu, Jun 6, 2019 at 9:49 AM Richard Ryniker
wrote:
I think you will find the file is not truly empty. /sys
On 6/6/19 11:11 AM, pmkel...@frontier.com wrote:
On 6/6/19 13:45, Adam Williamson wrote:
On Thu, 2019-06-06 at 11:15 -0600, Chris Murphy wrote:
On Thu, Jun 6, 2019 at 9:49 AM Richard Ryniker
wrote:
I think you will find the file is not truly empty. /sys is not an
actual
file system, merely
On 6/6/19 13:45, Adam Williamson wrote:
On Thu, 2019-06-06 at 11:15 -0600, Chris Murphy wrote:
On Thu, Jun 6, 2019 at 9:49 AM Richard Ryniker wrote:
I think you will find the file is not truly empty. /sys is not an actual
file system, merely an interface to kernel information. There is no
On Thu, 06 Jun 2019 10:45:23 -0700
Adam Williamson wrote:
> On Thu, 2019-06-06 at 11:15 -0600, Chris Murphy wrote:
> > On Thu, Jun 6, 2019 at 9:49 AM Richard Ryniker
> > wrote:
> > > I think you will find the file is not truly empty. /sys is not
> > > an actual file system, merely an interface
On Thu, 2019-06-06 at 11:15 -0600, Chris Murphy wrote:
> On Thu, Jun 6, 2019 at 9:49 AM Richard Ryniker wrote:
> > I think you will find the file is not truly empty. /sys is not an actual
> > file system, merely an interface to kernel information. There is no
> > directory structure that
On 6/6/19 13:11, Chris Murphy wrote:
On Thu, Jun 6, 2019 at 6:05 AM pmkel...@frontier.com
wrote:
I discovered something strange. In both F30 and Rawhide (F31) the file
/sys/kernel/debug/usb/devices is empty. That is it's a file of 0 bytes.
This file used to contain all the information about
On Thu, Jun 6, 2019 at 9:49 AM Richard Ryniker wrote:
>
> I think you will find the file is not truly empty. /sys is not an actual
> file system, merely an interface to kernel information. There is no
> directory structure that records the length or other attributes of a file,
> as is the case
On Thu, Jun 6, 2019 at 6:05 AM pmkel...@frontier.com
wrote:
>
> I discovered something strange. In both F30 and Rawhide (F31) the file
> /sys/kernel/debug/usb/devices is empty. That is it's a file of 0 bytes.
> This file used to contain all the information about connected USB
> devices. Does
I think you will find the file is not truly empty. /sys is not an actual
file system, merely an interface to kernel information. There is no
directory structure that records the length or other attributes of a file,
as is the case for data on real media such as disks.
If you read the
I discovered something strange. In both F30 and Rawhide (F31) the file
/sys/kernel/debug/usb/devices is empty. That is it's a file of 0 bytes.
This file used to contain all the information about connected USB
devices. Does anyone know if this is part of an intended change or is it
a bug? If it
15 matches
Mail list logo
