Re: complete shutdown impossible (fedora 24)
Le 15/01/2017 21:30, stan a écrit : > On Sun, 15 Jan 2017 18:33:12 +0100 > François Patte wrote: > > >> No! Even after half an hour, the computer is still "on", the screen is >> black, fan is running, I cannot do anything with the keyboard. >> >> I think that there something wrong with encryption (my system use >> encrypted RAID1 partitions); here is what reports logwatch: > [snip] >> I don't know if I can trust that system! Things used to run smoothly >> before fedora 22 > > I think I agree with you. Your case is very different than mine. If > it was my system, I would save any unique information, reinstall from > scratch, then reintroduce the unique information. > > Maybe you could paste it somewhere on the web (twice to be redundant) in > encrypted form, and recover it after the new install. But it is a *new* install: I first installed f25 and it was awfull: some app like firefox were unable to read properly html pages, and I could read one mail out of three with thunderbird! So I installed fedora 24 and it works normally (up to now!) except this shutdown problem. I don't know where to report this problem, I think that devellopers and packagers don't care about this. To proove this, try to install with anaconda an encrypted raid system, preserving your home and opt directories. It took me 3 hours before the install could begin: anaconda hanged or crashed many times. So my thoughts are that these fedora version (>21) are only done for standard instalations not for secure ones! -- François Patte UFR de mathématiques et informatique Laboratoire CNRS MAP5, UMR 8145 Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)1 8394 5849 http://www.math-info.univ-paris5.fr/~patte signature.asc Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
ACPI errors at boot
I just updated to kernel 4.9.3-200.fc25.x86_64 and am now seeing this on boot: Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359) Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT2._GTF] (Node 8e820d0ce5c8), AE_NOT_FOUND (20160831/psparse-543) Jan 16 11:07:14 bree kernel: ata3.00: ATA-8: TOSHIBA DT01ACA100, MS2OA750, max UDMA/133 Jan 16 11:07:14 bree kernel: ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359) Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT0._GTF] (Node 8e820d0ce410), AE_NOT_FOUND (20160831/psparse-543) Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359) Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node 8e820d0cea78), AE_NOT_FOUND (20160831/psparse-543) Jan 16 11:07:14 bree kernel: ata2.00: ATAPI: TSSTcorp CDDVDW SH-224BB, SB00, max UDMA/100 Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359) Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT2._GTF] (Node 8e820d0ce5c8), AE_NOT_FOUND (20160831/psparse-543) Jan 16 11:07:14 bree kernel: ata1.00: supports DRM functions and may not be fully accessible Jan 16 11:07:14 bree kernel: ata3.00: configured for UDMA/133 Jan 16 11:07:14 bree kernel: ata1.00: NCQ Send/Recv Log not supported Jan 16 11:07:14 bree kernel: ata1.00: ATA-9: Samsung SSD 840 EVO 120GB, EXT0BB6Q, max UDMA/133 Jan 16 11:07:14 bree kernel: ata1.00: 234441648 sectors, multi 1: LBA48 NCQ (depth 31/32), AA Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359) Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node 8e820d0cea78), AE_NOT_FOUND (20160831/psparse-543) Jan 16 11:07:14 bree kernel: ata2.00: configured for UDMA/100 Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359) Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT0._GTF] (Node 8e820d0ce410), AE_NOT_FOUND (20160831/psparse-543) However the boot proceeds and the system seems OK for the moment. I'm mentioning this because it's new for me, but Google shows a number of similar reports going back several years. Should I worry? poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: ACPI errors at boot
On 01/16/17 19:16, Patrick O'Callaghan wrote: > I just updated to kernel 4.9.3-200.fc25.x86_64 and am now seeing this > on boot: > > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, > AE_NOT_FOUND (20160831/psargs-359) > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed > [\_SB.PCI0.SAT0.SPT2._GTF] (Node 8e820d0ce5c8), AE_NOT_FOUND > (20160831/psparse-543) > Jan 16 11:07:14 bree kernel: ata3.00: ATA-8: TOSHIBA DT01ACA100, MS2OA750, > max UDMA/133 > Jan 16 11:07:14 bree kernel: ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ > (depth 31/32), AA > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, > AE_NOT_FOUND (20160831/psargs-359) > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed > [\_SB.PCI0.SAT0.SPT0._GTF] (Node 8e820d0ce410), AE_NOT_FOUND > (20160831/psparse-543) > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, > AE_NOT_FOUND (20160831/psargs-359) > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed > [\_SB.PCI0.SAT0.SPT1._GTF] (Node 8e820d0cea78), AE_NOT_FOUND > (20160831/psparse-543) > Jan 16 11:07:14 bree kernel: ata2.00: ATAPI: TSSTcorp CDDVDW SH-224BB, SB00, > max UDMA/100 > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, > AE_NOT_FOUND (20160831/psargs-359) > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed > [\_SB.PCI0.SAT0.SPT2._GTF] (Node 8e820d0ce5c8), AE_NOT_FOUND > (20160831/psparse-543) > Jan 16 11:07:14 bree kernel: ata1.00: supports DRM functions and may not be > fully accessible > Jan 16 11:07:14 bree kernel: ata3.00: configured for UDMA/133 > Jan 16 11:07:14 bree kernel: ata1.00: NCQ Send/Recv Log not supported > Jan 16 11:07:14 bree kernel: ata1.00: ATA-9: Samsung SSD 840 EVO 120GB, > EXT0BB6Q, max UDMA/133 > Jan 16 11:07:14 bree kernel: ata1.00: 234441648 sectors, multi 1: LBA48 NCQ > (depth 31/32), AA > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, > AE_NOT_FOUND (20160831/psargs-359) > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed > [\_SB.PCI0.SAT0.SPT1._GTF] (Node 8e820d0cea78), AE_NOT_FOUND > (20160831/psparse-543) > Jan 16 11:07:14 bree kernel: ata2.00: configured for UDMA/100 > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup failure, > AE_NOT_FOUND (20160831/psargs-359) > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed > [\_SB.PCI0.SAT0.SPT0._GTF] (Node 8e820d0ce410), AE_NOT_FOUND > (20160831/psparse-543) > > However the boot proceeds and the system seems OK for the moment. I'm > mentioning this because it's new for me, but Google shows a number of > similar reports going back several years. > > Should I worry? > > Depends on what you've learned from your googling. If you found that folks had failures after seeing these messages and ended up replacing HW to fix it, yes by all means worry. If you found out that folks got the messages but experienced no ill effects or they changed a setting or something else and the issue went awaythen probably no need to worry. I suppose it is safe to assume you've booted again into an earlier kernel and didn't see those errors? So, just something that the latest kernel is checking that wasn't being checked before and is harmless is likely. -- Fedora Users List - The place to go to get others to do the work for you ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: ACPI errors at boot
The real problem is not only that acpi faliures, else that Intel 915 fifo buffer underrun error has came back, and returns every time when I get kernel update. Worse, because WMI is also messed up, and I needed to return 3 kernel versions back and run the whole system on X instead of wayland. I don't know, I really annoying that every kernel has this flickering bug, and freezing out my machine so deeply that I loose my monitors when it gets sleep or suspend. Z 2017-01-16 14:50 GMT+01:00 Ed Greshko : > > > On 01/16/17 19:16, Patrick O'Callaghan wrote: > > I just updated to kernel 4.9.3-200.fc25.x86_64 and am now seeing this > > on boot: > > > > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup > failure, AE_NOT_FOUND (20160831/psargs-359) > > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed > [\_SB.PCI0.SAT0.SPT2._GTF] (Node 8e820d0ce5c8), AE_NOT_FOUND > (20160831/psparse-543) > > Jan 16 11:07:14 bree kernel: ata3.00: ATA-8: TOSHIBA DT01ACA100, > MS2OA750, max UDMA/133 > > Jan 16 11:07:14 bree kernel: ata3.00: 1953525168 sectors, multi 16: > LBA48 NCQ (depth 31/32), AA > > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup > failure, AE_NOT_FOUND (20160831/psargs-359) > > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed > [\_SB.PCI0.SAT0.SPT0._GTF] (Node 8e820d0ce410), AE_NOT_FOUND > (20160831/psparse-543) > > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup > failure, AE_NOT_FOUND (20160831/psargs-359) > > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed > [\_SB.PCI0.SAT0.SPT1._GTF] (Node 8e820d0cea78), AE_NOT_FOUND > (20160831/psparse-543) > > Jan 16 11:07:14 bree kernel: ata2.00: ATAPI: TSSTcorp CDDVDW SH-224BB, > SB00, max UDMA/100 > > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup > failure, AE_NOT_FOUND (20160831/psargs-359) > > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed > [\_SB.PCI0.SAT0.SPT2._GTF] (Node 8e820d0ce5c8), AE_NOT_FOUND > (20160831/psparse-543) > > Jan 16 11:07:14 bree kernel: ata1.00: supports DRM functions and may not > be fully accessible > > Jan 16 11:07:14 bree kernel: ata3.00: configured for UDMA/133 > > Jan 16 11:07:14 bree kernel: ata1.00: NCQ Send/Recv Log not supported > > Jan 16 11:07:14 bree kernel: ata1.00: ATA-9: Samsung SSD 840 EVO 120GB, > EXT0BB6Q, max UDMA/133 > > Jan 16 11:07:14 bree kernel: ata1.00: 234441648 sectors, multi 1: LBA48 > NCQ (depth 31/32), AA > > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup > failure, AE_NOT_FOUND (20160831/psargs-359) > > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed > [\_SB.PCI0.SAT0.SPT1._GTF] (Node 8e820d0cea78), AE_NOT_FOUND > (20160831/psparse-543) > > Jan 16 11:07:14 bree kernel: ata2.00: configured for UDMA/100 > > Jan 16 11:07:14 bree kernel: ACPI Error: [DSSP] Namespace lookup > failure, AE_NOT_FOUND (20160831/psargs-359) > > Jan 16 11:07:14 bree kernel: ACPI Error: Method parse/execution failed > [\_SB.PCI0.SAT0.SPT0._GTF] (Node 8e820d0ce410), AE_NOT_FOUND > (20160831/psparse-543) > > > > However the boot proceeds and the system seems OK for the moment. I'm > > mentioning this because it's new for me, but Google shows a number of > > similar reports going back several years. > > > > Should I worry? > > > > > Depends on what you've learned from your googling. If you found that > folks had failures > after seeing these messages and ended up replacing HW to fix it, yes by > all means worry. > > If you found out that folks got the messages but experienced no ill > effects or they > changed a setting or something else and the issue went awaythen > probably no need to worry. > > I suppose it is safe to assume you've booted again into an earlier kernel > and didn't see > those errors? So, just something that the latest kernel is checking that > wasn't being > checked before and is harmless is likely. > > > -- > Fedora Users List - The place to go to get others to do the work for you > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > -- PGP: 06853DF7 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
unexpected dual monitor behavior
I have a laptop to which I have attached an external monitor via hdmi. I have the system configured such that the external monitor is a clone of the laptop display. This works fine once I login, however, when I boot the system and have the initial user login the external monitor is not a clone of the laptop display. If I move the mouse off the right side of the laptop display it shows up on the external monitor as does the login dialog. The laptop display just displays the background image. If I move the mouse off the left side of the external monitor it shows up on the laptop display as does the login dialog. Is this the expected behavior? I expected the display cloning to apply at boot time as well. Paolo ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: complete shutdown impossible (fedora 24)
On Mon, 16 Jan 2017 11:00:33 +0100 François Patte wrote: > But it is a *new* install: I first installed f25 and it was awfull: > some app like firefox were unable to read properly html pages, and I > could read one mail out of three with thunderbird! This doesn't sound like a software problem. If thunderbird reads one mail, it should be able to read all mails. An email is an email. And the same for firefox. An html page is an html page (sort of, it's a lot more complicated than email). But if thousands of other people can read an html page with firefox that you can't, it sounds like there is a problem with the system that firefox is running on, not with firefox. > So I installed fedora 24 and it works normally (up to now!) except > this shutdown problem. > > I don't know where to report this problem, I think that devellopers I think you should report it against anaconda. > and packagers don't care about this. To proove this, try to install > with anaconda an encrypted raid system, preserving your home and opt > directories. It took me 3 hours before the install could begin: > anaconda hanged or crashed many times. > > So my thoughts are that these fedora version (>21) are only done for > standard instalations not for secure ones! > I expect you are right that the secure installations aren't tested as thoroughly as the standard installations, though I don't know that, and might be completely wrong. But if they are tested at all they should have caught problems like yours, if those problems aren't somehow hardware related. Is it possible you are experiencing hardware problems? Overheating because of ventilation, dust shorting, loose memory sticks, failing memory, etc.? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: unexpected dual monitor behavior
I believe this is expected behavior based on my experience. I think you have to go into the display settings (under system settings in KDE) and specify if you want mirrored (unified) displays. On 01/16/2017 09:23 AM, Paolo Galtieri wrote: I have a laptop to which I have attached an external monitor via hdmi. I have the system configured such that the external monitor is a clone of the laptop display. This works fine once I login, however, when I boot the system and have the initial user login the external monitor is not a clone of the laptop display. If I move the mouse off the right side of the laptop display it shows up on the external monitor as does the login dialog. The laptop display just displays the background image. If I move the mouse off the left side of the external monitor it shows up on the laptop display as does the login dialog. Is this the expected behavior? I expected the display cloning to apply at boot time as well. Paolo ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Build .rpm for X64_64 only
On Sun, 15 Jan 2017 13:39:33 +, arnaud gaboury wrote:
> EDIT : reading more on the Arch topic, I must add my application is built
> with go. Rfering to Go packaging binaries[0], it seems I must use:
> BuildArch: noarch
> ExclusiveArch: %{go_arches} noarch
>
> Is this correct?
No. You seem to refer to an application, not a library of source files.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Networkmanagre Refuses to use my Dlink DWA-192 USB Wifi Device in F24
Hi, Some time ago I was using this device on the 2.4GHz channel (Linux has always refused to use the 5GHz channel, I say Linux, because Ubuntu has always refused to use the 5GHz channel as Fedora has always refused to) and when it was working it was via the ATH9K driver. I switched the network to using Ethernet devices which are still working fine, but I wanted to go back to wifi again because the wifi throughput is potentially faster (the Ethernet devices sends/receives at 500Mbps whereas the 2.4GHz channel on wifi sends/receives at 600Mbps, if I could ever get the 5GHz channel working it sends/receives at 1300Mbps), but Networkmanager refuses to activate the wifi device now. How do I identify whether its the 4.8 kernels which are the issue or whether its Networkmanager and how do I rectify the situation? I am using kde at the moment and I have cut and pasted the wifi password back into the Networkmanager definition, and had the new password stored in Kwallet, but Networkmanager still refuses to recognize that the device is a device it can connect to. I should also add that the device works fine under Windows 10. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Networkmanagre Refuses to use my Dlink DWA-192 USB Wifi Device in F24
On 01/16/2017 12:17 PM, Stephen Morris wrote: I am using kde at the moment and I have cut and pasted the wifi password back into the Networkmanager definition, and had the new password stored in Kwallet, but Networkmanager still refuses to recognize that the device is a device it can connect to. Therefor the password isn't the issue. And, as it works under Windows, it's not hardware. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Mount of NAS Ethernet Connect to Router Fails at Boot Time for CIFS Interface in F24
Hi, My Nas device now fails to mount at boot time via the CIFS definition in fstab but the corresponding NFS definition mounts quite happily. Also after the system comes up and I log into KDE I can manually mount the CIFS device. As far as I am aware the only difference between when it was mounting at boot time and now is several system updates, also the system update I did yesterday morning (which updated several hundred packages, which included a new kernel) has not rectified the issue. The systemctl output is below, I have blanked out the userid and password for security reasons. Does anyone have any ideas why this has now stopped working? systemctl status mnt-nas.mount ● mnt-nas.mount - /mnt/nas Loaded: loaded (/etc/fstab; bad; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2017-01-17 06:40:15 AEDT; 40min ago Where: /mnt/nas What: //192.168.1.12/Volume_1 Docs: man:fstab(5) man:systemd-fstab-generator(8) Process: 1299 ExecMount=/usr/bin/mount //192.168.1.12/Volume_1 /mnt/nas -t cifs -o username=,password=,cache=strict,_netdev,rw (code=exited, status=32) Jan 17 06:40:15 localhost.localdomain systemd[1]: Mounting /mnt/nas... Jan 17 06:40:15 localhost.localdomain mount[1299]: mount error(101): Network is unreachable Jan 17 06:40:15 localhost.localdomain mount[1299]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) Jan 17 06:40:15 localhost.localdomain systemd[1]: mnt-nas.mount: Mount process exited, code=exited status=32 Jan 17 06:40:15 localhost.localdomain systemd[1]: Failed to mount /mnt/nas. Jan 17 06:40:15 localhost.localdomain systemd[1]: mnt-nas.mount: Unit entered failed state. I have also listed below the fstab definition for the CIFS interface and the NFS interface. 192.168.1.12:/mnt/HD/HD_a2/mnt/nfs nfs users,noatime,nolock,bg,sec=sys,tcp,timeo=1800,_netdev,rw 0 0 //192.168.1.12/Volume_1 /mnt/nas cifs auto,username=,password=,cache=strict,_netdev,rw 0 0 regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Mount of NAS Ethernet Connect to Router Fails at Boot Time for CIFS Interface in F24
On Mon, Jan 16, 2017 at 3:36 PM, Stephen Morris wrote: > Jan 17 06:40:15 localhost.localdomain mount[1299]: mount error(101): > Network is unreachable > At first look it seems the network is not fully up and running during boot when the call the mount "/mnt/nas" is made. If you can delay the call till a bit later to let the network finish setting up you should be OK. Been too long since I have messed with this so procedurally I am not sure what you would need to do. Just ran into this before myself and that was the issue. -- Fred ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Networkmanagre Refuses to use my Dlink DWA-192 USB Wifi Device in F24
On 01/16/2017 12:22 PM, Joe Zeff wrote: > On 01/16/2017 12:17 PM, Stephen Morris wrote: >> I am using kde at the moment and I have cut and pasted the wifi password >> back into the Networkmanager definition, and had the new password stored >> in Kwallet, but Networkmanager still refuses to recognize that the >> device is a device it can connect to. > > Therefor the password isn't the issue. And, as it works under Windows, > it's not hardware. First try "ethtool -i " to see what driver is loaded (if any). If you get data back then try "iwlist wlan0 scan" (replace "wlan0" with your device) to see what access points are in the area. If all that works, then the wireless itself is working under Linux and there's something odd about the way NetworkManager (NM) and your device talk to each other. At that point you could try to disable NM and use the wpa_supplicant programs directly to try to get it up (such as running wpa_supplicant in the background and using something like wpa_supplicant_gui to manipulate it). If you're successful there, then try to get NM to talk nice or bugzilla it to the NM list. -- - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - - AIM/Skype: therps2ICQ: 226437340 Yahoo: origrps2 - -- - The moving cursor writes, and having written, blinks on. - -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Asterisk and dahdi-tools with fedora25
Hi, I've just upgraded a server we use for asterisk to fedora25 and noticed asterisk-dahdi doesn't install and the dahdi-tools package is missing. There also seems to be an existing bug report for this, dating back all the way to October. https://bugzilla.redhat.com/show_bug.cgi?id=1384718 I think I also saw a reference about it being deprecated? Perhaps it's been replaced by something else? Any ideas would be greatly appreciated. Thanks, Alex ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Mount of NAS Ethernet Connect to Router Fails at Boot Time for CIFS Interface in F24
On 01/17/17 04:36, Stephen Morris wrote: > Hi, > > My Nas device now fails to mount at boot time via the CIFS definition in > fstab but > the corresponding NFS definition mounts quite happily. Also after the system > comes up > and I log into KDE I can manually mount the CIFS device. As far as I am aware > the only > difference between when it was mounting at boot time and now is several > system updates, > also the system update I did yesterday morning (which updated several hundred > packages, > which included a new kernel) has not rectified the issue. The systemctl > output is below, > I have blanked out the userid and password for security reasons. > > Does anyone have any ideas why this has now stopped working? > > > systemctl status mnt-nas.mount > ● mnt-nas.mount - /mnt/nas >Loaded: loaded (/etc/fstab; bad; vendor preset: disabled) >Active: failed (Result: exit-code) since Tue 2017-01-17 06:40:15 AEDT; > 40min ago > Where: /mnt/nas > What: //192.168.1.12/Volume_1 > Docs: man:fstab(5) >man:systemd-fstab-generator(8) > Process: 1299 ExecMount=/usr/bin/mount //192.168.1.12/Volume_1 /mnt/nas -t > cifs -o > username=,password=,cache=strict,_netdev,rw (code=exited, > status=32) > > Jan 17 06:40:15 localhost.localdomain systemd[1]: Mounting /mnt/nas... > Jan 17 06:40:15 localhost.localdomain mount[1299]: mount error(101): Network > is unreachable > Jan 17 06:40:15 localhost.localdomain mount[1299]: Refer to the mount.cifs(8) > manual > page (e.g. man mount.cifs) > Jan 17 06:40:15 localhost.localdomain systemd[1]: mnt-nas.mount: Mount > process exited, > code=exited status=32 > Jan 17 06:40:15 localhost.localdomain systemd[1]: Failed to mount /mnt/nas. > Jan 17 06:40:15 localhost.localdomain systemd[1]: mnt-nas.mount: Unit entered > failed state. > > I have also listed below the fstab definition for the CIFS interface and the > NFS interface. > > > 192.168.1.12:/mnt/HD/HD_a2/mnt/nfs nfs > users,noatime,nolock,bg,sec=sys,tcp,timeo=1800,_netdev,rw 0 0 > //192.168.1.12/Volume_1 /mnt/nas cifs > auto,username=,password=,cache=strict,_netdev,rw 0 0 > One question Did you write your own systemd units for mounting CIFS shares? I ask since I don't have any mnt-nas.mount unit on my system and my mounts work just fine with a similar fstab entry. -- Fedora Users List - The place to go to get others to do the work for you ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
volumeicon error
Hi, On a fully updated F25 system, I get the following error upon boot: $ volumeicon ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused volumeicon: alsa_backend.c:86: asound_get_volume: Assertion `m_elem != NULL' failed. Aborted (core dumped) The problem persists for an undetermined amount of time after which it goes away (i.e. volumeicon works as advertised with no error messages and with the icon showing up on my system tray). The problem appears to me that I can not determine the amount of time. Sometimes it is 8 minutes, sometimes not even 30 minutes does it, and another time it was 15 minutes. Any suggestions as to what the error is, and/or how I can track/fix the error. 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. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
