Graphics with fedora 22
by Patrick Dupre
Hello,
After I update from 20 to 22. there is a graphics issue.
It works fine with a Live version.
This what I did in the past (2013). Should I do the same?
Xorg -configure
cvt 1440 900
xrandr -q
create /etc/X11/xorg.conf.d/40-monitor.conf and
/etc/X11/xorg.conf.d/50-screen.conf
Check /var/log/Xorg.0.log
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
5 years, 7 months
Fedora 21 Install: Stuck at "Installing software 12%"
by Steven P. Ulrick
Hello, Everyone
Just put a new Seagate 2TB hard drive in the computer that I use as a
media server. I proceeded to install the KDE spin of Fedora 21 from a
flash drive. Everything went fine, but the progress indicator is
stuck at "Installing software 12%" Has been stuck there for about 10
minutes or more.
So, I WAS wondering what was wrong... Then I saw the following at the
bottom of the screen:
Fedora is now successfully installed and ready for you to use!
Go ahead and reboot to start using it!
In the lower right hand corner is a button that says "Quit"
So, I'm going to click that button and see what happens...
Steven P. Ulrick
5 years, 7 months
chromecast: Fedora vs Windows
by Timothy Murphy
Sadly, I find that chromecast (under google chrome) performs much better
under Windows 7 than under Fedora-22 (on the same laptop).
Under Fedora the reception is very jumpy.
Admittedly this is with a rather low - 6.5Mb/s - internet speed.
I wonder if this is a common experience?
--
Timothy Murphy
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin
5 years, 7 months
Re: fedup 20 -> 21 -> xinit -> KDE -> open /dev/fb0: No such file or directory
by Ed Greshko
On 07/28/15 11:41, richard emberson wrote:
> ]# journalctl -b 0 | grep -i mouse
> Jul 27 19:52:02 localhost.localdomain kernel: mousedev: PS/2 mouse device common for all mice
> Jul 27 19:52:02 localhost.localdomain kernel: usb 7-1: Product: USB Optical Mouse
> Jul 27 19:52:02 localhost.localdomain kernel: input: PixArt USB Optical Mouse as /devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1:1.0/0003:093A:2510.0001/input/input6
> Jul 27 19:52:02 localhost.localdomain kernel: hid-generic 0003:093A:2510.0001: input,hidraw0: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:1d.1-1/input0
> Jul 27 19:52:02 localhost.localdomain kernel: psmouse serio1: synaptics: Touchpad model: 1, fw: 6.2, id: 0x81a0b1, caps: 0xa04711/0x200000/0x0, board id: 0, fw id: 496485
> Jul 27 19:52:49 localhost.localdomain kernel: input: MCE IR Keyboard/Mouse (ene_ir) as /devices/virtual/input/input10
> Jul 27 19:52:49 localhost.localdomain kernel: IR MCE Keyboard/mouse protocol handler initialized
> # journalctl -b 0 | grep -i keyb
> Jul 27 19:52:02 localhost.localdomain kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
> Jul 27 19:52:49 localhost.localdomain kernel: input: MCE IR Keyboard/Mouse (ene_ir) as /devices/virtual/input/input10
> Jul 27 19:52:49 localhost.localdomain kernel: IR MCE Keyboard/mouse protocol handler initialized
>
> I appreciate the help. I've been downloading the fedora 22
> workstation and server dvds just in case.
> Re-installing my laptops is not much of a problem, its my home
> servers where I want to be sure prior to going from fedora x to x+1.
> Also, I'd like to keep using KDE, but, at least for this laptop,
> that may not be possible.
Well, that all looks in order.
So, you are able to boot and you do get a graphical login screen, but you don't get a cursor and you can't type a password.
You looked in the fedup log, located in /var/log, and see no errors.
I'm fairly sure the lack of XINPUT lines in the Xorg log is telling....just have no idea what could be the issue.
I've not had a failure in fedup such as this and I've been using it for the past several releases.
--
If I wanted a blog or social media I'd go elsewhere
5 years, 7 months
Help. KDE Dolphin cannot read home directory, smbclient reads it fine
by Javier Perez
Hi
Fedora 22 both machines, the server and the client.
I have been looking for something on this problem but maybe my Google-Fu is
not good enough.
I set up Samba on my home server to share my home directory and a few other
directories.
Finally I got it all working except for Dolphin.
I can do smbclient //server/homedirectory and I get the listing of my home
directory.
On the other hand if I go to Network->Samba Shares->Workgroup->server and
try to open the Homes entry, I get an error: "The file or folder
smb://server/homes does not exist
What am I doing wrong?
Thanks
--
------------------------------
/\_/\
|O O| pepebuho(a)gmail.com
~~~~ Javier Perez
~~~~ While the night runs
~~~~ toward the day...
m m Pepebuho watches
from his high perch.
5 years, 7 months
Re: fedup 20 -> 21 -> xinit -> KDE -> open /dev/fb0: No such file or directory
by Ed Greshko
On 07/28/15 10:57, richard emberson wrote:
> See below
>
> On 07/27/2015 07:33 PM, Ed Greshko wrote:
>> On 07/28/15 09:50, richard emberson wrote:
>>>
>>> grep "input device" /var/log/Xorg.0.log | grep XINPUT
>>> <nothing found>
>>>
>>> Its a Jetta laptop with touch pad (which, like the usb optical mouse, also does not work) and builtin keyboard.
>>
>> What is in your /etc/X11/xorg.conf ? It should only contain....
> I do not have a xorg.conf file, but I do have a nvidia-xorg.conf
> which is the same as your xorg.conf file you showed below.
> (but, if I change the name of it from nvidia-xorg.conf to
> xorg.conf, I still have no mouse/keyboard).
>>
>> # RPM Fusion - nvidia-xorg.conf
>> #
>> Section "Device"
>> Identifier "Videocard0"
>> Driver "nvidia"
>> EndSection
>>
>> Also, what files do you have in the /etc/X11/xorg.conf.d directory?
>
> # ls -l xorg.conf.d/
> total 12
> -rw-r--r--. 1 root root 108 Jan 11 2015 00-avoid-glamor.conf
> -rw-r--r--. 1 root root 232 Jan 13 2015 00-keyboard.conf
> -rw-r--r--. 1 root root 178 Jan 11 2015 99-nvidia.conf
>
FWIW, all of my systems report something for XINPUT in the Xorg log...
Also, what do you get for these commands?
journalctl -b 0 | grep -i mouse
journalctl -b 0 | grep -i keyb
Sadly, I'm running out of ideas...
--
If I wanted a blog or social media I'd go elsewhere
5 years, 7 months
Re: fedup 20 -> 21 -> xinit -> KDE -> open /dev/fb0: No such file or directory
by Ed Greshko
On 07/28/15 09:50, richard emberson wrote:
>
> grep "input device" /var/log/Xorg.0.log | grep XINPUT
> <nothing found>
>
> Its a Jetta laptop with touch pad (which, like the usb optical mouse, also does not work) and builtin keyboard.
What is in your /etc/X11/xorg.conf ? It should only contain....
# RPM Fusion - nvidia-xorg.conf
#
Section "Device"
Identifier "Videocard0"
Driver "nvidia"
EndSection
Also, what files do you have in the /etc/X11/xorg.conf.d directory?
[egreshko@meimei X11]$ ls -l xorg.conf.d/
total 12
-rw-r--r--. 1 root root 161 Dec 26 2012 00-anaconda-keyboard.conf
-rw-r--r--. 1 root root 108 Dec 2 2013 00-avoid-glamor.conf
-rw-r--r--. 1 root root 178 Feb 7 2014 99-nvidia.conf
I find the following odd in your log file....
>
> [ 10029.383] (==) Matched nvidia as autoconfigured driver 0
> [ 10029.383] (==) Matched nouveau as autoconfigured driver 1
> [ 10029.383] (==) Matched nv as autoconfigured driver 2
> [ 10029.383] (==) Matched nouveau as autoconfigured driver 3
> [ 10029.383] (==) Matched nv as autoconfigured driver 4
> [ 10029.383] (==) Matched modesetting as autoconfigured driver 5
> [ 10029.383] (==) Matched fbdev as autoconfigured driver 6
> [ 10029.383] (==) Matched vesa as autoconfigured driver 7
I don't see any mention of nouveau in my log files except in the kernel command line.
--
If I wanted a blog or social media I'd go elsewhere
5 years, 7 months
fedup 20 -> 21 -> xinit -> KDE -> open /dev/fb0: No such file or directory
by Rich Emberson
Still no mouse or keyboard. Don't know if this is the problem.
from /var/log/Xorg.0.log
START
[ 96.019] (II) Loading sub module "fb"
[ 96.019] (II) LoadModule: "fb"
[ 96.020] (II) Loading /usr/lib64/xorg/modules/libfb.so
[ 96.030] (II) Module fb: vendor="X.Org Foundation"
[ 96.030] compiled for 1.17.2, module version = 1.0.0
[ 96.030] ABI class: X.Org ANSI C Emulation, version 0.4
[ 96.030] (WW) Unresolved symbol: fbGetGCPrivateKey
[ 96.030] (II) Loading sub module "wfb"
[ 96.030] (II) LoadModule: "wfb"
[ 96.030] (II) Loading /usr/lib64/xorg/modules/libwfb.so
[ 96.041] (II) Module wfb: vendor="X.Org Foundation"
[ 96.041] compiled for 1.17.2, module version = 1.0.0
[ 96.041] ABI class: X.Org ANSI C Emulation, version 0.4
[ 96.041] (II) Loading sub module "ramdac"
[ 96.041] (II) LoadModule: "ramdac"
[ 96.041] (II) Module "ramdac" already built-in
[ 96.068] (WW) Falling back to old probe method for modesetting
[ 96.068] (WW) Falling back to old probe method for fbdev
[ 96.068] (II) Loading sub module "fbdevhw"
[ 96.068] (II) LoadModule: "fbdevhw"
[ 96.068] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[ 96.082] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 96.082] compiled for 1.17.2, module version = 0.0.2
[ 96.082] ABI class: X.Org Video Driver, version 19.0
[ 96.082] (EE) open /dev/fb0: No such file or directory
[ 96.082] (WW) Falling back to old probe method for vesa
[ 96.082] (II) NVIDIA(0): Creating default Display subsection in Screen
section
"Default Screen Section" for depth/fbbpp 24/32
[ 96.082] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 96.082] (==) NVIDIA(0): RGB weight 888
[ 96.082] (==) NVIDIA(0): Default visual is TrueColor
......
END
Thanks
Richard
5 years, 7 months
fedup 20 -> 21 -> xinit -> KDE -> No mouse/keyboard input
by Rich Emberson
Thanks for the suggestion.
Contents of /var/cache/akmods/akmods.log
START
2015/07/25 16:06:18 akmods: Checking kmods exist for 4.0.8-200.fc21.x86_64
2015/07/25 16:06:18 akmods: Building and installing nvidia-340xx-kmod
2015/07/25 16:06:18 akmods: Building RPM using the command
'/bin/akmodsbuild --target x86_64 --kernels 4.0.8-200.fc21.x86_64
/usr/src/akmods/nvidia-340xx-kmod.latest'
2015/07/25 16:07:03 akmods: Installing newly built rpms
2015/07/25 16:07:03 akmods: DNF detected
2015/07/25 16:07:20 akmods: Successful.
2015/07/25 17:22:20 akmods: Checking kmods exist for 4.0.8-300.fc22.x86_64
2015/07/25 17:22:20 akmods: Building and installing nvidia-340xx-kmod
2015/07/25 17:22:20 akmods: Building RPM using the command
'/bin/akmodsbuild --target x86_64 --kernels 4.0.8-300.fc22.x86_64
/usr/src/akmods/nvidia-340xx-kmod.latest'
2015/07/25 18:07:53 akmods: Checking kmods exist for 4.0.8-300.fc22.x86_64
2015/07/25 18:07:53 akmods: Building and installing nvidia-340xx-kmod
2015/07/25 18:07:54 akmods: Building RPM using the command
'/bin/akmodsbuild --target x86_64 --kernels 4.0.8-300.fc22.x86_64
/usr/src/akmods/nvidia-340xx-kmod.latest'
2015/07/26 14:05:01 akmods: Checking kmods exist for 4.0.8-300.fc22.x86_64
2015/07/26 14:05:01 akmods: Building and installing nvidia-340xx-kmod
2015/07/26 14:05:01 akmods: Building RPM using the command
'/bin/akmodsbuild --target x86_64 --kernels 4.0.8-300.fc22.x86_64
/usr/src/akmods/nvidia-340xx-kmod.latest'
2015/07/26 14:05:47 akmods: Installing newly built rpms
2015/07/26 14:05:47 akmods: DNF detected
2015/07/26 14:06:00 akmods: Successful.
END
ran:
/usr/sbin/akmods --force
and now the file has the additional line:
2015/07/27 14:54:21 akmods: Checking kmods exist for 4.0.8-300.fc22.x86_64
Still no mouse or keyboard.
Thanks
Richard
5 years, 7 months
dnf failed
by Patrick Dupre
Hello,
I run dnf update.
At package 3935/4000, it failed, probably because a network issue
(timeout)
I am surprise than all the downloaded packages have be erased.
When I restarted dnf update, it restart from scratch.
Why?
It could have just restart and continue downloading the missing
65 packages!
Regards.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
5 years, 7 months
