Cntrl-Alt-F[2,3,4,5,6,7,8,9,10,11,12] do not work
by JD
Using Mate on FC20, with latest updates.
Cntrl-Alt-F keys never worked from the very first login into Mate Desktop.
These are the installed mate packages. Am I missing something?
It my be worthwhile to note that at the login screen, Cntrl-Alt-F keys DO
WORK!!
After login, into mate desktop, they stop working.
imsettings-mate-1.6.7-1.fc20.x86_64
libmatekbd-1.6.1-2.fc20.x86_64
libmateweather-1.6.2-3.fc20.x86_64
libmateweather-data-1.6.2-3.fc20.noarch
libmatewnck-1.6.1-2.fc20.x86_64
mate-applets-1.6.2-1.fc20.x86_64
mate-backgrounds-1.6.1-1.fc20.noarch
mate-calc-1.6.1-1.fc20.x86_64
mate-character-map-1.6.1-0.1.git2464a6c.fc20.x86_64
mate-control-center-1.6.2-2.fc20.x86_64
mate-control-center-filesystem-1.6.2-2.fc20.x86_64
mate-desktop-1.6.2-2.fc20.x86_64
mate-desktop-libs-1.6.2-2.fc20.x86_64
mate-dialogs-1.6.2-1.fc20.x86_64
mate-document-viewer-1.6.2-3.fc20.x86_64
mate-document-viewer-caja-1.6.2-3.fc20.x86_64
mate-document-viewer-libs-1.6.2-3.fc20.x86_64
mate-file-archiver-1.6.2-1.fc20.x86_64
mate-file-manager-1.6.4-4.fc20.x86_64
mate-file-manager-extensions-1.6.4-4.fc20.x86_64
mate-file-manager-image-converter-1.6.0-2.fc20.x86_64
mate-file-manager-schemas-1.6.4-4.fc20.x86_64
mate-file-manager-sendto-1.6.0-2.fc20.x86_64
mate-icon-theme-1.6.3-1.fc20.noarch
mate-image-viewer-1.6.2-2.fc20.x86_64
mate-media-1.6.1-1.fc20.x86_64
mate-menu-editor-1.6.1-1.fc20.noarch
mate-menus-1.6.0-5.fc20.x86_64
mate-menus-libs-1.6.0-5.fc20.x86_64
mate-menus-preferences-category-menu-1.6.0-5.fc20.x86_64
mate-netspeed-1.6.1-1.fc20.x86_64
mate-notification-daemon-1.6.1-2.fc20.x86_64
mate-panel-1.6.2-1.fc20.x86_64
mate-panel-libs-1.6.2-1.fc20.x86_64
mate-polkit-1.6.1-1.fc20.x86_64
mate-power-manager-1.6.3-2.fc20.x86_64
mate-screensaver-1.6.2-1.fc20.x86_64
mate-screensaver-devel-1.6.2-1.fc20.x86_64
mate-screenshot-1.6.1-1.fc20.x86_64
mate-search-tool-1.6.1-1.fc20.x86_64
mate-session-manager-1.6.1-4.fc20.x86_64
mate-settings-daemon-1.6.2-2.fc20.x86_64
mate-system-monitor-1.6.1-1.fc20.x86_64
mate-terminal-1.6.2-1.fc20.x86_64
mate-text-editor-1.6.2-1.fc20.x86_64
mate-themes-1.8.1-1.fc20.noarch
mate-utils-common-1.6.1-1.fc20.noarch
mate-window-manager-1.6.2-6.fc20.x86_64
10 years
how to keep firmware loaded
by lee
Hi,
how do I make it so that the firmware for a particular device doesn't
get unloaded when the device is no longer in use?
Apparently the firmware is unloaded when the device becomes unused. At
least it is loaded again when the device is used again; messages in
dmesg show that the firmware is loaded again. There are no messages
about unloading the firmware, so I don't know whether it is actually
unloaded or not.
Loading the firmware again (or unloading it) seems to cause problems
with the device. So I would like to load the firmware once and keep it
loaded, without any more attempts to load it once it has been loaded.
--
Fedora release 20 (Heisenbug)
10 years
Install Problem with Fedora 20 (No Local Standard Disks)
by Gregory P. Ennis
Everyone,
I purchased a used (refurbished) Dell Optiplex 755 that came with
Windows 7 installed. I am trying to install Fedora 20, but when I get
to the "Installation Destination" screen the fedora installer is not
finding any "Local Standard Discs", which means I have been unable to
start any installation.
The system boots to Windows without any problem. I was planning on
overwriting the disc and getting rid of the windows product entirely. I
have checked sum the installation disc, and have even created a second
Fedora 20 installation disc and have the same problem.
Sure would appreciate some guidance from someone on the list that has
solved a similar or same problem.
Thanks,
Greg Ennis
10 years
f20 - audio problem
by Mike Wright
Hi all,
Exploring f20 and have a self inflicted wound.
While trying to get flash to play on vlc I found a conflict between
libvpx and some other libraries so the resident genius yum removed it,
and all of the other packages dependent upon it, thinking they'd be easy
to reinstall.
Not the best idea. Now I've got all sorts of video but not a peep of audio.
I yum installed alsa* and pulseaudio*. The ALSA mixer I have now looks
nothing like the one here before. Pulseaudio volume control->Playback
says "ALSA plug-in [plugin-container (deleted)]: ALSA Playback" but yum
list reports alsa-plugins-pulseaudio-x86_64 as an installed package.
I couldn't find an Audio Group. Does anybody know how to reinstall the
standard f20 audio packages or where I can find a list of packages
installed into a fresh f20 system (from the live xfce spin)?
Thanks,
Mike Wright
10 years
Burning Blu-Ray media on fedora20
by Alex
Hi,
Does anyone know what happened to the Shilling cdrecord? I've tried to
download it from several locations, and the domain appears to no longer
exist.
How are people burning BD-R media these days?
These links no longer exists:
ftp://ftp.berlios.de/pub/cdrecord/alpha/
http://cdrecord.berlios.de/private/cdrecord.html
Any ideas greatly appreciated.
Thanks,
Alex
10 years
Fedora Lounge
by Robert Moskowitz
A bit OT.
In a taxi in Chicago going down Clark st and there was:
Fedora Lounge
Sounds like the place where this crowd might like to gather for an evening.
Of course I was heading for Union Station for my train home at the
time............
10 years
Netcat anomaly
by CLOSE Dave
I have a Fedora 20 machine which is receiving UDP broadcast packets at
regular intervals on a strange high port. No program is presently
listening for these packets. If I run, "tcpdump -i eth0 port 29531", I
see each of the packets arriving just as I expect. Note, the packets are
not empty and contain mostly ASCII characters.
But if I then run, "nc -lu 29531", I don't see anything! Why not? What
obvious thing am I missing?
This same operation works better (but still not as I expect) on Fedora
14. NC shows one packet arriving but then doesn't show any more.
Running NC under strace on both machines, I see F14 NC seems to use
poll(2). It outputs one packet then hangs on poll. F20 NC seems to use
select(2). It hangs on the first call.
SELinux and the firewall are disabled on both machines.
--
Dave Close
10 years
Installing fedora on an arm chromebook (the old one)
by Rafael Espíndola
I had in the past followed the instructions in
https://www.berrange.com/posts/2013/03/31/automated-install-of-fedora-18-...
But I wanted to try to install fedora 20 and have a a simpler
partition layout. In the process I found out a bit on how the system
works.
I first upgraded chrome os to get a new kernel (3.8.11) and copied the
kernel partition, /lib/modules and /lib/firmware.
I then got a f19 ssd image and booted from that.
The usb boot being enable flag is stored in the internal flash. The
flags listed in vboot_reference/firmware/lib/vboot_nvstorage.c are
storred in the first 16 bytes of the disk. To clear chromeos and keep
the machine booting from USB I did
$ dd if=/dev/zero of=/dev/mmcblk0
Create a nvram.txt file with
7000000001000000000000000000003f
The 1 in the middle is the usb boot flag.
$ xxd -r -p nvram.txt nvram
$ dd if=nvram of=/dev/mmcblk0
I then created 2 partitions, one for the kernel and one for the root.
To get the kernel to boot, I checked
firmware/lib/cgptlib/include/cgptlib_internal.h
and noticed that what was needed was:
Correct type: sgdisk -t1:7f00 /dev/mmcblk0
Setting attribute bits 48 and 56: sgdisk -A1:set:48 /dev/mmcblk0;
sgdisk -A1:set:56 /dev/mmcblk0
Repack the kernel with vbutil_kernel and point it to the new root
partition. I then got the fedora20 root image, extracted the files for
/ and replaced /lib/modules and /lib/firmware.
I tried to get X running with both the armsoc and fbdev drivers, but
so far no success, which is fine for me since I use the machine as an
arm devboard.
Cheers,
Rafael
10 years
