Re: USB-live
> > On 6/26/20 2:14 PM, Patrick Dupre wrote: > > > Yes, that sounds right. > > >From here I have to choose: > > legacy external device boot > > USB Storage Device > > Does it give any more info than that? Most computers I've used give at > least the manufacturer name of the USB device. And selecting that > doesn't boot from the flash drive? > ___ > >>> Yes, it also gives the name of the USB key > >>> > >>> I guess that I understand > >>> To boot properly on the USB key, the UEFI: has to come, in the booting > >>> list, before Fedora, > >>> even if the first in the list is USB Key (not UEFI) > >>> UEFI: KingstonDataTraveler 3.0PMAP > >>> PciRoot(0x0)/Pci(0x14,0x0)/USB(0x9,0x0)/HD(1,MBR,0x000CBB49) > >>> or > >>> UEFI: General UDisk 5.00 (twice) > >>> PciRoot(0x0)/Pci(0x14,0x0)/USB(0x8,0x0)/CDROM(0x1) > >>> PciRoot(0x0)/Pci(0x14,0x0)/USB(0x8,0x0)/HD(2,MBR,0x2EBDC43A) > >> > >> You don't need to change the boot order in the BIOS settings. Just pick > >> it from the boot menu. What happens if you do that. > > Nothing, > > I would be surprised if it was actually nothing. Something must happen > when you press enter on that boot entry from the F12 boot menu. For sure, from F12, it works ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: User no boot -
On Fri, Jun 26, 2020 at 09:51:50PM -0400, Bob Goodwin wrote: > > > On 2020-06-26 19:55, Ed Greshko wrote: > > On 2020-06-27 07:50, Bob Goodwin wrote: > > > > > > On 2020-06-26 19:29, Ed Greshko wrote: > > > > I think you mean > > > > > > > > 1. Connected monitor and keyboard and booted to a command line login > > > > prompt. > > > > 2. Logged in as root > > > > 3. Used startx and got an xfce desktop > > > > 4. Created a new user using "useradd". > > > . > > > Yes exactly as you say, But I have not logged out, I will try that since > > > you suggest it. It is almost supper time here so it may be some time > > > before I get back to report the result. Thanks, > > OK > > > > Just a comment. If you didn't logout of the root account then what did you > > mean by "they could not do anything". > > > > > > > > 5. Logged out of the xfce session and logged out of the root account. > > > > 6. Tried to login as the user created in #4 > > > > > > > > .? > > . > So I tried the following: > > Logout root via ssh: > [root@box48 ~]# logout > Connection to 192.168.50.148 closed. > > Log in bobg: > [bobg@WS1 ~]$ ssh bobg@192.168.50.148 > bobg@192.168.50.148's password: > Last login: Tue May 26 15:16:50 2020 from 192.168.50.57 > /bin/bash: Permission denied > Connection to 192.168.50.148 closed. > > Login bob: > > [bobg@WS1 ~]$ ssh bob@192.168.50.148 > bob@192.168.50.148's password: > Last login: Tue May 26 15:20:58 2020 from 192.168.50.57 > /bin/bash: Permission denied > Connection to 192.168.50.148 closed. > > Both are refused. Maybe user/group settings? Tomorrow will be soon enough. > None of this really matters since a reinstall will replace the existing > system. > Note you are succesfully logging in. You get a message about the last login and start a shell. Otherwise /bin/bash would not be sending error messages. There must be something wrong in your start up scripts or environment that cause your shell to exit before giving a prompt. You may get more info by logging in as root and using "su" and "su -" to switch user to bob or bobg. Jon -- Jon H. LaBadie jo...@jgcomp.com ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: USB-live
On 6/26/20 11:57 PM, Patrick Dupre wrote: I would be surprised if it was actually nothing. Something must happen when you press enter on that boot entry from the F12 boot menu. For sure, from F12, it works Then I don't understand where the problem is. If it boots, then what doesn't work? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: User no boot -
On 6/27/20 12:01 AM, Jon LaBadie wrote: On Fri, Jun 26, 2020 at 09:51:50PM -0400, Bob Goodwin wrote: [bobg@WS1 ~]$ ssh bob@192.168.50.148 bob@192.168.50.148's password: Last login: Tue May 26 15:20:58 2020 from 192.168.50.57 /bin/bash: Permission denied Connection to 192.168.50.148 closed. Both are refused. Maybe user/group settings? Tomorrow will be soon enough. None of this really matters since a reinstall will replace the existing system. Note you are succesfully logging in. You get a message about the last login and start a shell. Otherwise /bin/bash would not be sending error messages. I'm not convinced. /bin/login prints that "Last login" message. If it was bash giving that error message, it would say what executable was denied. That really looks like the login process failing to execute bash. You can see the same thing by giving the user a non-executable shell and then doing "su - user". It will print the "Last login message and then fail executing the shell. However, I also can't figure out how to reproduce the issue with ssh. Something along the way checks that the shell is valid and executable. That's why I suspect an selinux issue, but I can't figure out how to change the labels on the file to make it not executable, but still be attempted. This is the message if you try to run something that isn't executable: # /etc/passwd -bash: /etc/passwd: Permission denied There must be something wrong in your start up scripts or environment that cause your shell to exit before giving a prompt. You may get more info by logging in as root and using "su" and "su -" to switch user to bob or bobg. That should provide more information either way. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: How do I change the grub kernel boot parameters in F32 ?
On 2020-06-19 09:33, Stephen Morris wrote: My issue with BLS is the way it displays the kernel menu entries in grub, it is exactly the same as the way grubby showed the entries which I also hated, consequently I refuse to use BLS until such time as they provide an option to get the menus displayed as an entry for the current kernel and an expandable menu for all other kernels and the recovery entries. You are lucky to see kernel versions because in my case I just have Fedora 32 (Thirty Two) Fedora 32 (Thirty Two) Fedora 32 (Thirty Two) Fedora Memtest memtest86+-5.01 I've tried debugging that a bit and the scripts are just taking the PRETTY_NAME var from /etc/os-release. This is on BLS, without EFI. Regards. -- Roberto Ragusamail at robertoragusa.it ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: USB "insertion" for permanently-connected devices
On Fri, 2020-06-26 at 16:00 -0700, Samuel Sieb wrote: > On 6/26/20 2:45 PM, Patrick O'Callaghan wrote: > > On Fri, 2020-06-26 at 13:56 -0700, Samuel Sieb wrote: > > > On 6/26/20 1:33 PM, Patrick O'Callaghan wrote: > > > > udisksctl power-off -b /dev/sdd > > > > > > > > This works too, but unfortunately also removes the /sys/block/sdd > > > > files, meaning I can't turn the thing on again. However, if I > > > > physically switch it on and off, it reappears, IOW it causes a USB > > > > "insertion" event. > > > > > > Isn't that command telling the drive to disconnect and turn off? If so, > > > there's no way you can get its attention again without power cycling it. > > > > In theory, yes, however the drive doesn't actually turn off (though it > > will spin down after 30 minutes). It's not powered by the USB interface > > but has its own power cable. In fact even after the drives go into idle > > mode the dock itself is still powered (the lights are on). Think of a > > thumb drive that's still in the socket (though that may not be the best > > analogy). I'm asking if there's a way to reactivate it without > > physically pulling it out and reinserting it. > > Can you show the log messages from running that command? > > When I tested it with a USB flash drive, it disconnected from the USB > bus and trying the rescan idea didn't do anything. That sounds like what I see. > I messed around > enough that I confused that USB controller and that entire bus was dead. > Fortunately, I managed to reset the controller and got it back by > telling the driver to remove it and then add it back. How did you do that? Did it involve physically pulling and reinserting the drive? FWIW, this is what happens when I power on the dock: Jun 27 11:33:55 Bree kernel: usb 3-3: new high-speed USB device number 4 using xhci_hcd Jun 27 11:33:55 Bree kernel: usb 3-3: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00 Jun 27 11:33:55 Bree kernel: usb 3-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1 Jun 27 11:33:55 Bree kernel: usb 3-3: Product: ASM1156-PM Jun 27 11:33:55 Bree kernel: usb 3-3: Manufacturer: ASMT Jun 27 11:33:55 Bree kernel: usb 3-3: SerialNumber: Jun 27 11:33:55 Bree kernel: scsi host6: uas Jun 27 11:33:55 Bree mtp-probe[6798]: checking bus 3, device 4: "/sys/devices/pci:00/:00:14.0/usb3/3-3" Jun 27 11:33:55 Bree mtp-probe[6798]: bus: 3, device: 4 was not an MTP device Jun 27 11:33:55 Bree mtp-probe[6803]: checking bus 3, device 4: "/sys/devices/pci:00/:00:14.0/usb3/3-3" Jun 27 11:33:55 Bree mtp-probe[6803]: bus: 3, device: 4 was not an MTP device Jun 27 11:33:55 Bree kernel: scsi 6:0:0:0: Direct-Access ASMT ASM1156-PM 0PQ: 0 ANSI: 6 Jun 27 11:33:55 Bree kernel: scsi 6:0:0:1: Direct-Access ASMT ASM1156-PM 0PQ: 0 ANSI: 6 Jun 27 11:33:55 Bree kernel: sd 6:0:0:0: Attached scsi generic sg4 type 0 Jun 27 11:33:55 Bree kernel: sd 6:0:0:1: Attached scsi generic sg5 type 0 Jun 27 11:33:55 Bree kernel: sd 6:0:0:0: [sdd] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB) Jun 27 11:33:55 Bree kernel: sd 6:0:0:0: [sdd] 4096-byte physical blocks Jun 27 11:33:55 Bree kernel: sd 6:0:0:0: [sdd] Write Protect is off Jun 27 11:33:55 Bree kernel: sd 6:0:0:0: [sdd] Mode Sense: 43 00 00 00 Jun 27 11:33:55 Bree kernel: sd 6:0:0:1: [sde] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB) Jun 27 11:33:55 Bree kernel: sd 6:0:0:1: [sde] 4096-byte physical blocks Jun 27 11:33:55 Bree kernel: sd 6:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 27 11:33:55 Bree kernel: sd 6:0:0:1: [sde] Write Protect is off Jun 27 11:33:55 Bree kernel: sd 6:0:0:1: [sde] Mode Sense: 43 00 00 00 Jun 27 11:33:55 Bree kernel: sd 6:0:0:1: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 27 11:33:55 Bree kernel: sd 6:0:0:0: [sdd] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes) Jun 27 11:33:55 Bree kernel: sd 6:0:0:1: [sde] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes) Jun 27 11:33:55 Bree systemd[1747]: dbus-:1.2-org.gnome.ChromeGnomeShell@0.service: Succeeded. Jun 27 11:33:55 Bree kernel: sd 6:0:0:0: [sdd] Attached SCSI disk Jun 27 11:33:55 Bree kernel: sd 6:0:0:1: [sde] Attached SCSI disk Jun 27 11:33:55 Bree kernel: md/raid1:md127: active with 2 out of 2 mirrors Jun 27 11:33:55 Bree kernel: md127: detected capacity change from 0 to 169595136 Jun 27 11:33:55 Bree kernel: md127: p1 Jun 27 11:33:56 Bree systemd[1]: Condition check resulted in Software RAID monitoring and management being skipped. Jun 27 11:33:56 Bree systemd[1]: Condition check resulted in Software RAID monitoring and management being skipped. (Those last two lines always appear, but the RAID system seems to be working correctly). When using powering off with 'udisksctl power-off ...' (having previously stopped
Re: USB "insertion" for permanently-connected devices
On Sat, 2020-06-27 at 07:56 +0800, Ed Greshko wrote: > On 2020-06-27 07:50, Tim via users wrote: > > On Fri, 2020-06-26 at 21:33 +0100, Patrick O'Callaghan wrote: > > > Is there a way to cause an insertion event without physically doing > > > anything to the dock? > > There are USB hubs with power switches on each port. > > > > I think he really wants to do these things without manual intervention. :-) Exactly. The idea is to do this all with a script running my nightly backup, but leaving the disks spun down once it's finished. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: USB "insertion" for permanently-connected devices
On Sat, 2020-06-27 at 13:46 +0930, Tim via users wrote: > Tim: > > > There are USB hubs with power switches on each port. > > > Ed Greshko: > > I think he really wants to do these things without manual > > intervention. :-) > > Well it avoids having to unplug and replug. ;-) As I said earlier, the dock has a power switch. I want to avoid using it so I can script the whole thing. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: User no boot -
On 2020-06-26 22:33, Ed Greshko wrote: Oh, when are you planning to do the install? Are you going to do a fresh install of F32, or?? I would hope this weekend if I can get help. My equipment arrangement has grown over the years and the computers are in rack and panel type enclosures secured only at the front panel to aluminum angle verticals I drilled and tapped for screws, it is heavy and the server is near the bottom of the stack. I can't just pull it out without fear the aluminum angles will give and bend so a block of wood will need to be cut to fill the vacant space. I need a helper to do things that require good vision ... Additional the FC24 is stuck as root, and root is not allowed to do certain things, among them is setting the screensaver parameters, namely setting the delay to start sleep, I set to 720 minutes, as high as it will go. It tells me root can't do that and ignores the setting, sleeps, actually more like a coma, in a short time, as it has been doing since yesterday afternoon. The server wants the power cycled off/on to wake it. That is why ssh is most convenient. I believe I created the new user shown directly from the console but I've gone back and forth so many times I may be confused and will check again this morning. The server rarely gets shut down and I have to go around to the other side and push a button, can't tell it to reboot or shutdown, it does not respond to the keyboard when it goes into that sleep/coma condition! a -- Bob Goodwin - Zuni, Virginia, USA http://www.qrz.com/db/W2BOD FEDORA-32/64bit LINUX XFCE Fastmail POP3 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: User no boot -
On Jun 26, 2020, at 21:52, Bob Goodwin wrote: > So I tried the following: > > Logout root via ssh: > [root@box48 ~]# logout > Connection to 192.168.50.148 closed. > > Log in bobg: > [bobg@WS1 ~]$ ssh bobg@192.168.50.148 > bobg@192.168.50.148's password: > Last login: Tue May 26 15:16:50 2020 from 192.168.50.57 > /bin/bash: Permission denied > Connection to 192.168.50.148 closed. > > Login bob: > > [bobg@WS1 ~]$ ssh bob@192.168.50.148 > bob@192.168.50.148's password: > Last login: Tue May 26 15:20:58 2020 from 192.168.50.57 > /bin/bash: Permission denied > Connection to 192.168.50.148 closed. > > Both are refused. Maybe user/group settings? Tomorrow will be soon enough. > None of this really matters since a reinstall will replace the existing > system. You are successfully logging in as those other users, but the login process is launching the users’ login shell, and when /bin/bash is executed, the login session returns: “/bin/bash: Permission denied”. Then the login session exits and you log out My first guess is that either /bin/bash’s permissions are broken, and root either uses a different shell or the permissions only allows root. The output of “rpm -V bash” should tell you what is wrong with the package. Now, personally, I see a long out of date system with ssh access and broken bash, and I immediately think “compromised system”. So I’d suggest caution. -- Jonathan Billings ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: User no boot -
On 2020-06-27 18:47, Bob Goodwin wrote: > > > On 2020-06-26 22:33, Ed Greshko wrote: >> Oh, when are you planning to do the install? Are you going to do a fresh >> install of F32, or?? > I would hope this weekend if I can get help. My equipment arrangement has > grown over the years and the computers are in rack and panel type enclosures > secured only at the front panel to aluminum angle verticals I drilled and > tapped for screws, it is heavy and the server is near the bottom of the > stack. I can't just pull it out without fear the aluminum angles will give > and bend so a block of wood will need to be cut to fill the vacant space. I > need a helper to do things that require good vision ... > > Additional the FC24 is stuck as root, and root is not allowed to do certain > things, among them is setting the screensaver parameters, namely setting the > delay to start sleep, I set to 720 minutes, as high as it will go. It tells > me root can't do that and ignores the setting, sleeps, actually more like a > coma, in a short time, as it has been doing since yesterday afternoon. The > server wants the power cycled off/on to wake it. That is why ssh is most > convenient. I believe I created the new user shown directly from the console > but I've gone back and forth so many times I may be confused and will check > again this morning. The server rarely gets shut down and I have to go around > to the other side and push a button, can't tell it to reboot or shutdown, it > does not respond to the keyboard when it goes into that sleep/coma condition! > Well, root should be able to do *everything*. So, it sounds as if that system has much more issues than just new users not "working". It sounds, to me, as if it would be a waste of effort to try to get it working only to do a fresh install. So, I would just wait until you can get the help you need to move stuff and then do a fresh install of F32. -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: USB "insertion" for permanently-connected devices
26.06.20, 22:33 CEST, Patrick O'Callaghan: > In other threads I've mentioned I have a USB-powered external SATA > dock, which I'm using mainly as a backup device. Currently, I have a > script to power it down by doing this sort of thing: > >echo 1 > /sys/block/sdd/device/delete > > I can then turn it on again using: > >echo "- - -" > /sys/class/scsi_host/host6/scan > > This works, but is a kludge. A cleaner way would be to use: > > udisksctl power-off -b /dev/sdd > > This works too, but unfortunately also removes the /sys/block/sdd > files, meaning I can't turn the thing on again. However, if I > physically switch it on and off, it reappears, IOW it causes a USB > "insertion" event. > > Is there a way to cause an insertion event without physically doing > anything to the dock? eject -t /dev/sdd might be worth a try. At least this (device node adapted, of course) works for me with USB thumb drives which I "safely removed" using the GUI. If the udiskctl command you use internally does something similar to the GUI function, eject -t might also work for you. -- Regards mks ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: 5.6 kernel is slower to boot
Ok, I know this is an older thread but I have upgraded to the latest kernel. The boot happens relatively fast but hibernation takes a long time to restore. On Mon, May 11, 2020 at 5:23 PM Sreyan Chakravarty wrote: > FWIW, you can ignore anything that takes less than a second. You can >> probably mask NetworkManager-wait-online and can definitely mask >> ModemManager unless you're actually using a modem. Not much, but it's a >> start. > > > I don't think that will help but I have no idea why dracut suddenly is now > taking so much time now. It didn't use to be like this. > > On Mon, May 11, 2020 at 12:28 AM Joe Zeff wrote: > >> On 05/10/2020 05:52 AM, Sreyan Chakravarty wrote: >> > Ok here is my full systemd-blame: >> > >> > https://pastebin.com/raw/ngsF5NUv >> > >> >> FWIW, you can ignore anything that takes less than a second. You can >> probably mask NetworkManager-wait-online and can definitely mask >> ModemManager unless you're actually using a modem. Not much, but it's a >> start. >> ___ >> users mailing list -- users@lists.fedoraproject.org >> To unsubscribe send an email to users-le...@lists.fedoraproject.org >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org >> > > > -- > Regards, > Sreyan Chakravarty > -- Regards, Sreyan Chakravarty ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: USB "insertion" for permanently-connected devices
On Sat, 2020-06-27 at 14:15 +0200, Markus Schönhaber wrote: > 26.06.20, 22:33 CEST, Patrick O'Callaghan: > > > In other threads I've mentioned I have a USB-powered external SATA > > dock, which I'm using mainly as a backup device. Currently, I have a > > script to power it down by doing this sort of thing: > > > >echo 1 > /sys/block/sdd/device/delete > > > > I can then turn it on again using: > > > >echo "- - -" > /sys/class/scsi_host/host6/scan > > > > This works, but is a kludge. A cleaner way would be to use: > > > > udisksctl power-off -b /dev/sdd > > > > This works too, but unfortunately also removes the /sys/block/sdd > > files, meaning I can't turn the thing on again. However, if I > > physically switch it on and off, it reappears, IOW it causes a USB > > "insertion" event. > > > > Is there a way to cause an insertion event without physically doing > > anything to the dock? > > eject -t /dev/sdd > > might be worth a try. At least this (device node adapted, of course) > works for me with USB thumb drives which I "safely removed" using the > GUI. If the udiskctl command you use internally does something similar > to the GUI function, eject -t might also work for you. The problem is that the device node (/dev/sdd) is removed by the udisksctl power-off command, so this doesn't work. Thanks anyway. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: User no boot -
On 2020-06-27 07:16, Ed Greshko wrote: Well, root should be able to do*everything*. So, it sounds as if that system has much more issues than just new users not "working". ° Definitely not true, try the Thunar File Manager as root, well I guess you can force it but it protests. However,I only know what happened when I did it and assumed it was the way it is. It sounds, to me, as if it would be a waste of effort to try to get it working only to do a fresh install. So, I would just wait until you can get the help you need to move stuff and then do a fresh install of F32. ° Yes it is not a productive effort, I just don't like being beaten by the damned samba server. Anyway it looks like I will be able to get to this shortly. I would have referred 33 beta but FC32 will be it. ... -- Bob Goodwin - Zuni, Virginia, USA http://www.qrz.com/db/W2BOD FEDORA-32/64bit LINUX XFCE Fastmail POP3 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: User no boot -
On 2020-06-27 07:16, Ed Greshko wrote: Well, root should be able to do*everything*. So, it sounds as if that system has much more issues than just new users not "working". ° Definitely not true, try the Thunar File Manager as root, well I guess you can force it but it protests. However,I only know what happened when I did it and assumed it was the way it is. It sounds, to me, as if it would be a waste of effort to try to get it working only to do a fresh install. So, I would just wait until you can get the help you need to move stuff and then do a fresh install of F32. ° Yes it is not a productive effort, I just don't like being beaten by the damned samba server. Anyway it looks like I will be able to get to this shortly. I would have referred 33 beta but FC32 will be it. ... -- Bob Goodwin - Zuni, Virginia, USA http://www.qrz.com/db/W2BOD FEDORA-32/64bit LINUX XFCE Fastmail POP3 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: USB "insertion" for permanently-connected devices
27.06.20, 14:55 CEST, Patrick O'Callaghan: > On Sat, 2020-06-27 at 14:15 +0200, Markus Schönhaber wrote: >> 26.06.20, 22:33 CEST, Patrick O'Callaghan: >> >>> This works too, but unfortunately also removes the /sys/block/sdd >>> files, meaning I can't turn the thing on again. However, if I >>> physically switch it on and off, it reappears, IOW it causes a USB >>> "insertion" event. >>> >>> Is there a way to cause an insertion event without physically doing >>> anything to the dock? >> >> eject -t /dev/sdd >> >> might be worth a try. At least this (device node adapted, of course) >> works for me with USB thumb drives which I "safely removed" using the >> GUI. If the udiskctl command you use internally does something similar >> to the GUI function, eject -t might also work for you. > > The problem is that the device node (/dev/sdd) is removed by the > udisksctl power-off command, so this doesn't work. Did you try it? Doing "safely remove" (for example in Dolphin) also removes the corresponding device node. eject -t for me, removes the necessity to pull an re-insert the thumb drive to re-create the device node and to be able to access it again. That's the whole point in issuing eject -t. -- Regards mks ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Mount samba share using pam_mount
Fedora Workstation 32 I'm trying to mount a samba share at login using pam_mount. The steps I've taken so far after googling and man-page reading are: 1. In /etc/security/pam_mount.conf.xml I uncommented the line: 2. Created the file ~/.pam_mount.conf.xml containing: 3. To add pam_mount.so to pam.d I changed /etc/pam.d/login to: #%PAM-1.0 auth substack system-auth auth optional pam_mount.so auth include postlogin accountrequired pam_nologin.so accountinclude system-auth password include system-auth # pam_selinux.so close should be the first session rule sessionrequired pam_selinux.so close sessionoptional pam_mount.so sessionrequired pam_loginuid.so sessionoptional pam_console.so # pam_selinux.so open should only be followed by sessions to be executed in the user context sessionrequired pam_selinux.so open sessionrequired pam_namespace.so sessionoptional pam_keyinit.so force revoke sessioninclude system-auth sessioninclude postlogin -session optional pam_ck_connector.so and /etc/pam.d/gdm-password to: auth [success=done ignore=ignore default=bad] pam_selinux_permit.so authsubstack password-auth authoptional pam_mount.so authoptional pam_gnome_keyring.so authinclude postlogin account required pam_nologin.so account include password-auth passwordsubstack password-auth -password optional pam_gnome_keyring.so use_authtok session required pam_selinux.so close session optional pam_mount.so session required pam_loginuid.so session optional pam_console.so session required pam_selinux.so open session optional pam_keyinit.so force revoke session required pam_namespace.so session include password-auth session optional pam_gnome_keyring.so auto_start session include postlogin I log out and back in again and... it does not work. (I can mount this share from the command line using the mount command.) So my question is... what am I doing wrong? Simon ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: USB "insertion" for permanently-connected devices
On Sat, 2020-06-27 at 16:55 +0200, Markus Schönhaber wrote: > 27.06.20, 14:55 CEST, Patrick O'Callaghan: > > > On Sat, 2020-06-27 at 14:15 +0200, Markus Schönhaber wrote: > > > 26.06.20, 22:33 CEST, Patrick O'Callaghan: > > > > > > > This works too, but unfortunately also removes the /sys/block/sdd > > > > files, meaning I can't turn the thing on again. However, if I > > > > physically switch it on and off, it reappears, IOW it causes a USB > > > > "insertion" event. > > > > > > > > Is there a way to cause an insertion event without physically doing > > > > anything to the dock? > > > > > > eject -t /dev/sdd > > > > > > might be worth a try. At least this (device node adapted, of course) > > > works for me with USB thumb drives which I "safely removed" using the > > > GUI. If the udiskctl command you use internally does something similar > > > to the GUI function, eject -t might also work for you. > > > > The problem is that the device node (/dev/sdd) is removed by the > > udisksctl power-off command, so this doesn't work. > > Did you try it? > > Doing "safely remove" (for example in Dolphin) also removes the > corresponding device node. > eject -t > for me, removes the necessity to pull an re-insert the thumb drive to > re-create the device node and to be able to access it again. That's the > whole point in issuing eject -t. 'eject -t' does not signal the dock to spin down the drives. Only by using the power-down option to udisksctl, or by the kludgy method of writing '1' to the sys/.../delete file does this happen. The latter does allow me to power them up again, so I guess I'll be sticking with that. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: 5.6 kernel is slower to boot
On 6/27/20 5:47 AM, Sreyan Chakravarty wrote: Ok, I know this is an older thread but I have upgraded to the latest kernel. The boot happens relatively fast but hibernation takes a long time to restore. That's just how hibernation works. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: USB "insertion" for permanently-connected devices
On 6/27/20 3:43 AM, Patrick O'Callaghan wrote: On Fri, 2020-06-26 at 16:00 -0700, Samuel Sieb wrote: I messed around enough that I confused that USB controller and that entire bus was dead. Fortunately, I managed to reset the controller and got it back by telling the driver to remove it and then add it back. How did you do that? Did it involve physically pulling and reinserting the drive? Somehow I ended up in /sys/bus/pci/drivers/ehci-pci, but in your case it might need to be /sys/bus/pci/drivers/xhci-pci since you're dealing with a USB 3 device. In there are links to the USB pci devices that are managed by this driver. From the logs you included, it would be ":00:14.0" in your case. Doing "echo :00:14.0 > unbind" will disconnect the entire usb bus on that device and "echo :00:14.0 > bind" will re-initialize it. (Note the message from mdadm. The RAID array has /dev/sdd and /dev/sde, but, again, RAID has already been stopped before running udisksctl.) I really have my doubts about that. Something definitely still has the drives open at this point. How did you stop it? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: USB "insertion" for permanently-connected devices
On Sat, 2020-06-27 at 12:07 -0700, Samuel Sieb wrote: > On 6/27/20 3:43 AM, Patrick O'Callaghan wrote: > > On Fri, 2020-06-26 at 16:00 -0700, Samuel Sieb wrote: > > > I messed around > > > enough that I confused that USB controller and that entire bus was dead. > > >Fortunately, I managed to reset the controller and got it back by > > > telling the driver to remove it and then add it back. > > > > How did you do that? Did it involve physically pulling and reinserting > > the drive? > > Somehow I ended up in /sys/bus/pci/drivers/ehci-pci, but in your case it > might need to be /sys/bus/pci/drivers/xhci-pci since you're dealing with > a USB 3 device. In there are links to the USB pci devices that are > managed by this driver. From the logs you included, it would be > ":00:14.0" in your case. Doing "echo :00:14.0 > unbind" will > disconnect the entire usb bus on that device and "echo :00:14.0 > > bind" will re-initialize it. Interesting. I'll look into that. > > (Note the message from mdadm. The RAID array has /dev/sdd and /dev/sde, > > but, again, RAID has already been stopped before running udisksctl.) > > I really have my doubts about that. Something definitely still has the > drives open at this point. How did you stop it? echo 1 > /sys/block/sdd/device/delete echo 1 > /sys/block/sde/device/delete poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: USB "insertion" for permanently-connected devices
27.06.20, 20:00 CEST, Patrick O'Callaghan: > 'eject -t' does not signal the dock to spin down the drives. No, it doesn't - and I never said it did. On the contrary: as I have tried to explain to you twice, it might help to re-create the removed device node of an already spun down disk and make it accessible again. -- Regards mks ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: USB "insertion" for permanently-connected devices
On 6/27/20 2:29 PM, Patrick O'Callaghan wrote: On Sat, 2020-06-27 at 12:07 -0700, Samuel Sieb wrote: On 6/27/20 3:43 AM, Patrick O'Callaghan wrote: (Note the message from mdadm. The RAID array has /dev/sdd and /dev/sde, but, again, RAID has already been stopped before running udisksctl.) I really have my doubts about that. Something definitely still has the drives open at this point. How did you stop it? echo 1 > /sys/block/sdd/device/delete echo 1 > /sys/block/sde/device/delete I meant how did you stop the RAID array before doing that? And how did you verify that it really was stopped? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: USB "insertion" for permanently-connected devices
On 6/27/20 7:55 AM, Markus Schönhaber wrote: Doing "safely remove" (for example in Dolphin) also removes the corresponding device node. eject -t for me, removes the necessity to pull an re-insert the thumb drive to re-create the device node and to be able to access it again. That's the whole point in issuing eject -t. Are you sure the device node is removed? At least in Gnome when you press the eject button on a flash drive, it appears to do an internal "eject", which seems really weird to me. The drive size goes to zero, but the device node is still there. When you do the "eject -t", it reconnects the media and the drive size comes back. There's no way you can do an "eject -t" on a non-existent device node. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: questions about the Athenaeum game manager
This is a follow-up to my post last night about the new Athenaeum game manager.I say "new" only because it is a fairly recent project. I ran an update via terminal in both dnf and flatpak, and the Athenaeum-installed-apps did not update. But Gnome Software said all the twenty-four games ( that I had installed last night ) had updates available ( most in the 694.8 MB range ). So I clicked on "Update All" with my slow but reliable ethernet connection of 40 Mbps. David Locklear After about 20 minutes, nothing has happened. The boxes read "Installing" in light grey letters. So is there a way to do this from terminal ?They are just regular flatpaks. Right ?? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
