users March 2015

users@lists.fedoraproject.org

127 participants
157 discussions

Start a nNew thread

Yum vs Apper
by Jonathan Ryshpan 15 Mar '15

15 Mar '15

Yum reports that there are 121 updates needed but apper reports that the system is up to date. Why? Thanks - jon

4 4

Re: installing fedora on HEWLETT PACKARD pavilion 500
by Angelo Moreschini 15 Mar '15

15 Mar '15

Hi Chris, I send you again this message I followed your suggestion: I tried efibootmgr -v and I got this output: *"efibootmgr: EFI variables are not supported on this system."* because this message I though the installation is not good and found this link: http://unix.stackexchange.com/questions/91620/arch-linux-grub-install-efi-v… where is wrote : The problem was simply that the efivars kernel module was not loaded. I have not so much experience so I would ask you what I can do.. ....perhaps it is enough to install the efivars kernel module. ? Thank you ---------- I cannot send you the content of dmesg. The moderator reject my message because to much size.. but I can find inside it if you say me what to look for. ------------- On Sat, Mar 14, 2015 at 3:43 PM, Angelo Moreschini < mrangelo.fedora(a)gmail.com> wrote: > this the otput of dmesg > > On Sat, Mar 14, 2015 at 9:21 AM, Angelo Moreschini < > mrangelo.fedora(a)gmail.com> wrote: > >> Hi Chris, >> >> I followed your suggestion: >> I tried efibootmgr -v >> and I got this output: >> >> *"efibootmgr: EFI variables are not supported on this system."* >> >> thinking that the installation is not good, I found this link: >> >> >> http://unix.stackexchange.com/questions/91620/arch-linux-grub-install-efi-v… >> >> where is wrote : The problem was simply that the efivars kernel module >> was not loaded. >> >> >> I have not so much experience so I would ask you what to do.. >> >> perhaps it is enough to install the efivars kernel module. ? >> >> Thank you >> >> On Fri, Mar 13, 2015 at 3:43 PM, Chris Murphy <lists(a)colorremedies.com> >> wrote: >> >>> On Fri, Mar 13, 2015 at 11:56 AM, Angelo Moreschini >>> <mrangelo.fedora(a)gmail.com> wrote: >>> > I already had some problem to install fedora on HP pavilion 500, but >>> at last >>> > I was able to finish the installation. >>> > >>> > I got the message: "installation complete" and so I did the shutdown. >>> > >>> > The computer closed regular, >>> > (the system is going down for power out at ...) >>> > but when I try to open it again, I find this message on the screen: >>> > ------------------------- >>> > boot device not found >>> > >>> > please install an operating system on your hard disk >>> > >>> > Hard DISK - (3F0) >>> > F2 - System Diagnostics >>> > >>> > for more information visit the site >>> > http://h18021.www1.hp.com/helpandsupport/hp-self-support.html >>> > ---------------------------- >>> > >>> > The site don't explain nothing about a problem connected with linux >>> > >>> > and after running diagnostic I get the message : >>> > ERROR: no boot disk has been detected >>> >>> Curious. This is the 3rd such report in just a couple months, >>> including myself. In my case it was intermittent though and Dell >>> support concluded either logic board or SSD flakiness; and also mine >>> was a dual boot scenario and sometimes happened even with Windows only >>> installed on the system (and all Fedora NVRAM entries cleared). >>> >>> The fact that your on-board diagnostic doesn't see a drive suggests a >>> hardware problem. But I wonder if there's something (efbootmgr + >>> kernel tickling the firmware's NVRAM?) about Fedora that's instigating >>> this? Or if it's just coincidence. I guess the sample size isn't big >>> enough to know. >>> >>> What happens if you boot from install media, and capture both >>> dmesg >>> efiboomgr -v >>> ? >>> >>> In my case, dmesg clearly showed the lack of proper ACPI >>> initialization, no drive was found at all. >>> >>> -- >>> Chris Murphy >>> -- >>> users mailing list >>> users(a)lists.fedoraproject.org >>> To unsubscribe or change subscription options: >>> https://admin.fedoraproject.org/mailman/listinfo/users >>> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct >>> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines >>> Have a question? Ask away: http://ask.fedoraproject.org >>> >> >> >

1 0

autoconnect bluetooth mouse?
by Neal Becker 14 Mar '15

14 Mar '15

Just got a logitech bt m557 mouse. Using it on F21 (kde). One annoyance, it does not automatically connect when the machine wakes. To connect, I have to go to the bluetooth icon on my panel (without a mouse) and select the mouse, and click 'connect'. Any ideas? -- Those who fail to understand recursion are doomed to repeat it

3 3

installing fedora on HEWLETT PACKARD pavilion 500
by Angelo Moreschini 14 Mar '15

14 Mar '15

I already had some problem to install fedora on HP pavilion 500, but at last I was able to finish the installation. I got the message: "installation complete" and so I did the shutdown. The computer closed regular, (the system is going down for power out at ...) but when I try to open it again, I find this message on the screen: ------------------------- boot device not found please install an operating system on your hard disk Hard DISK - (3F0) F2 - System Diagnostics for more information visit the site http://h18021.www1.hp.com/helpandsupport/hp-self-support.html ---------------------------- The site don't explain nothing about a problem connected with linux and after running diagnostic I get the message : ERROR: no boot disk has been detected For what I can understand the HP computer use UEFI (a standard firmware interface for PCs); and this give problems to use CD live.., but I don't know other that can give problem like the boot loader... I would like to know how to solve this problem thank you Angelo

2 2

[ F21 ] How to remove GNOME
by Martin Cigorraga 13 Mar '15

13 Mar '15

Hi all, I'm a newcomer to Fedora and still learning its ways so excuse me if my question sounds stupid. Now, I want to remove GNOME from my install as I use i3; from what I saw there's no gnome-group or similar goup available, how should I proceed? Regards, -Martin

11 20

Yum update failure -
by Bob Goodwin 13 Mar '15

13 Mar '15

I tried to yum update this computer and got the following error: One of the configured repositories failed (Fedora 21 - x86_64), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: ............. Insufficient space in download directory /var/cache/yum/x86_64/21/fedora * free 0 * needed 100 k ............. It suggests such things as: 3. Disable the repository, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable fedora ............. [root@bobgASRockServer bobg]# du -h /var/cache/yum/x86_64/21/fedora 4.0K /var/cache/yum/x86_64/21/fedora/gen 4.0K /var/cache/yum/x86_64/21/fedora/packages 12K /var/cache/yum/x86_64/21/fedora [root@bobgASRockServer bobg]# du -h /var/cache/yum/x86_64/21/ 4.0K /var/cache/yum/x86_64/21/fedora/gen 4.0K /var/cache/yum/x86_64/21/fedora/packages 12K /var/cache/yum/x86_64/21/fedora 4.0K /var/cache/yum/x86_64/21/updates/gen 40K /var/cache/yum/x86_64/21/updates/packages 48K /var/cache/yum/x86_64/21/updates 68K /var/cache/yum/x86_64/21/ It doesn't look like there are any large files? I don't understand what's going on here. two other F-21 computers updated normally. Bob -- http://www.qrz.com/db/W2BOD box10 Fedora-21/64bit Linux/XFCE

7 13

F21 - skype -- How best to install
by Robert Moskowitz 13 Mar '15

13 Mar '15

I have been puzzling through some old posts here on skype. I need it working for a conference call monday morning. Subject: No sound in Skype on Fedora 64-bit Seems to be talking about installing lpf-skype even on an x86_64 system and it basically works? Some sound problems but work around them? Or: http://www.if-not-true-then-false.com/2012/install-skype-on-fedora-centos-r… I can always run it on my samsung phone, but want to use it on my notebook.

3 7

Booting up to black screen - Log included
by linuxnutster＠videotron.ca 13 Mar '15

13 Mar '15

Greetings, I previously posted that since a fedup to fedora 21, I intermittently boot up to a blank screen. I'm using akmod-nvidia-340xx, but reverting back to nouveau did not solve the issue. One out of every 3 boot results in the problem. I pressed ctrl+alt+F2 and logged in and attempted the startx command. The resulting error message said to check xorg.1.log. The nvidia console ( nvidia xserver settings ) clearly indicates my screen type ( Ancor communications Asus VH196. Would the "no screens found" be the possible source of my headache? This is the error log from /var/log/Xorg.1.log: [ 359.396] (II) FBDEV: driver for framebuffer: fbdev [ 359.396] (II) VESA: driver for VESA chipsets: vesa [ 359.396] (++) using VT number 2 [ 359.396] (WW) Falling back to old probe method for modesetting [ 359.396] (II) Loading sub module "fbdevhw" [ 359.396] (II) LoadModule: "fbdevhw" [ 359.396] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so [ 359.397] (II) Module fbdevhw: vendor="X.Org Foundation" [ 359.397] compiled for 1.16.3, module version = 0.0.2 [ 359.397] ABI class: X.Org Video Driver, version 18.0 [ 359.397] (EE) open /dev/fb0: No such file or directory [ 359.397] (WW) Falling back to old probe method for fbdev [ 359.397] (II) Loading sub module "fbdevhw" [ 359.397] (II) LoadModule: "fbdevhw" [ 359.397] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so [ 359.397] (II) Module fbdevhw: vendor="X.Org Foundation" [ 359.397] compiled for 1.16.3, module version = 0.0.2 [ 359.397] ABI class: X.Org Video Driver, version 18.0 [ 359.397] (EE) open /dev/fb0: No such file or directory [ 359.397] vesa: Ignoring device with a bound kernel driver [ 359.397] (WW) Falling back to old probe method for vesa [ 359.397] (EE) Screen 0 deleted because of no matching config section. [ 359.397] (II) UnloadModule: "modesetting" [ 359.397] (EE) Screen 0 deleted because of no matching config section. [ 359.397] (II) UnloadModule: "fbdev" [ 359.397] (II) UnloadSubModule: "fbdevhw" [ 359.397] (EE) Screen 0 deleted because of no matching config section. [ 359.397] (II) UnloadModule: "vesa" [ 359.397] (EE) Device(s) detected, but none match those in the config file. [ 359.397] (EE) Fatal server error: [ 359.397] (EE) no screens found(EE) [ 359.397] (EE) Please consult the Fedora Project support at http://wiki.x.org for help. [ 359.397] (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. [ 359.397] (EE) [ 359.398] (EE) Server terminated with error (1). Closing log file.

3 3

Problem upgrading VLC
by casimiro barreto 13 Mar '15

13 Mar '15

vlc-core complains about broken dependency (libgpg-error) (looks for libgpg-error.so.0). libgpg-error is installed (x86_64 and i686) libgpg-error-devel is installed but yum fails with: Plugins carregados: langpacks Resolvendo dependências --> Executando verificação da transação ---> O pacote vlc.x86_64 0:2.2.0-1.fc21 será instalado --> Processando dependência: vlc-core(x86-64) = 2.2.0-1.fc21 para o pacote: vlc-2.2.0-1.fc21.x86_64 --> Processando dependência: libvlccore.so.8()(64bit) para o pacote: vlc-2.2.0-1.fc21.x86_64 --> Executando verificação da transação ---> O pacote vlc-core.x86_64 0:2.2.0-1.fc21 será instalado --> Processando dependência: libgpg-error.so.0(GPG_ERROR_1.0)(64bit) para o pacote: vlc-core-2.2.0-1.fc21.x86_64 --> Resolução de dependências finalizada Error: Pacote: vlc-core-2.2.0-1.fc21.x86_64 (rpmfusion-free-updates) Requer: libgpg-error.so.0(GPG_ERROR_1.0)(64bit) Você pode tentar usar o parâmetro --skip-broken para contornar o problema Você pode tentar executar: rpm -Va --nofiles --nodigest -- The information contained in this message is confidential and intended to the recipients specified in the headers. If you received this message by error, notify the sender immediately. The unauthorized use, disclosure, copy or alteration of this message are strictly forbidden and subjected to civil and criminal sanctions.

6 6

sector hard errors
by JD 13 Mar '15

13 Mar '15

Hi all, on a new drive, installed about 3 months ago ... fsck shows: Pass 5: Checking group summary information [ 117.650425] ata5.00: exception Emask 0x0 SAct 0xc0 SErr 0x0 action 0x0 [ 117.650678] ata5.00: irq_stat 0x40000008 [ 117.650840] ata5.00: failed command: READ FPDMA QUEUED [ 117.651523] ata5.00: cmd 60/80:30:68:08:40/00:00:be:00:00/40 tag 6 ncq 65536 in [ 117.651523] res 41/40:00:b0:08:40/00:00:be:00:00/40 Emask 0x409 (media error) <F> [ 117.652872] ata5.00: status: { DRDY ERR } [ 117.653547] ata5.00: error: { UNC } [ 117.655604] ata5.00: configured for UDMA/133 [ 117.655825] sd 4:0:0:0: [sdb] [ 117.655991] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 117.656631] sd 4:0:0:0: [sdb] [ 117.657288] Sense Key : Medium Error [current] [descriptor] [ 117.657966] Descriptor sense data with sense descriptors (in hex): [ 117.658652] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 117.659381] be 40 08 b0 [ 117.660065] sd 4:0:0:0: [sdb] [ 117.660703] Add. Sense: Unrecovered read error - auto reallocate failed [ 117.661349] sd 4:0:0:0: [sdb] CDB: [ 117.661981] Read(10): 28 00 be 40 08 68 00 00 80 00 [ 117.662667] blk_update_request: I/O error, dev sdb, sector 3191867568 [ 117.663323] ata5: EH complete [ 129.095402] ata5.00: exception Emask 0x0 SAct 0x3000000 SErr 0x0 action 0x0 [ 129.095663] ata5.00: irq_stat 0x40000008 [ 129.095826] ata5.00: failed command: READ FPDMA QUEUED [ 129.096434] ata5.00: cmd 60/00:c0:e8:08:00/01:00:c2:00:00/40 tag 24 ncq 131072 in [ 129.096434] res 41/40:00:90:09:00/00:00:c2:00:00/40 Emask 0x409 (media error) <F> [ 129.097727] ata5.00: status: { DRDY ERR } [ 129.098393] ata5.00: error: { UNC } [ 129.100528] ata5.00: configured for UDMA/133 [ 129.100768] sd 4:0:0:0: [sdb] [ 129.100935] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 129.101530] sd 4:0:0:0: [sdb] [ 129.102128] Sense Key : Medium Error [current] [descriptor] [ 129.102728] Descriptor sense data with sense descriptors (in hex): [ 129.103349] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 129.103998] c2 00 09 90 [ 129.104645] sd 4:0:0:0: [sdb] [ 129.105280] Add. Sense: Unrecovered read error - auto reallocate failed [ 129.105911] sd 4:0:0:0: [sdb] CDB: [ 129.106567] Read(10): 28 00 c2 00 08 e8 00 01 00 00 [ 129.107271] blk_update_request: I/O error, dev sdb, sector 3254782352 [ 129.107954] ata5: EH complete So, I am puzzled as to how quickly were the spare sectors consumed so that automatic sector forwarding ran out os spare sectors? So quickly on a brand new drive?? When someone buys a brand new drive, how many spare sectors is it guaranteed to have? ZERO? ONE?? How many?

6 17

← Newer
1
...
8
9
10
11
12
13
14
15
16
Older →

Jump to page: