Wi-Fi Network Preference Ordering
by Christopher Thielen
Hi Fedora community,
I have Fedora 23 and am using the default Gnome 3 desktop environment.
I have two wi-fi networks within reach of my laptop and Fedora always
auto-joins with the network with a weaker signal. I believe it is
choosing to do so because the weaker signal is the one I first provided
a password for months ago.
I have not been able to determine a way to set the wi-fi network
auto-join order preference. Is it possible to change the preference order?
Thanks for any tips,
Christopher Thielen
8 years
kernel config.gz file on livecd?
by thibaut noah
Hi guys, i'm looking for the path of the kernel config.gz on the livecd, i
thought it was in /proc/config.gz but there is nothing there.
Since i assume this is a mandatory file even for the live os it has to be
on the system, any idea where it is? I googled it but all my research
points the /proc/config.gz
I need this file to make a diff with my arch config.gz so i can customize
it the fedora way and improve my vga passthrough gaming performances.
Have a good weekend
8 years
Fedora 23 installation failed and symptoms destroyed
by D. Hugh Redelmeier
The system is a newly assembled and installing Fedora 23 from live DVD is
its first use. The processor is Skylake (I guess that might matter).
GPT partitioning and UEFI firmware are being used.
Fedora 23 installation seems to work fine until it says that it is
installing the bootloader. At this point, some error message is probably
produced but it gets completely lost in SPAM from journald.
The desktop becomes unresponsive. All the consoles are filled with
messages like this:
[TIMESTAMP] systemd-journald[PID]: Failed to write entry (N items, N bytes), ignoring: Read-only file system
In one of the many attempts to install, there was a message about an
I/O error. But it didn't seem to say anything beyond ERRNO=5.
Before the desktop becomes completely unresponsive, it is unable to launch
any programs (including GNOME Terminal).
I assume that journald is trying to log to a RAMdisk. This shouldn't
be a problem: the system has 32G of RAM.
Is there a way to stop journald messing up the record with its own
(possibly recursive) complaints? That would help us figure out what the
original problem is.
Permutations attempted:
- installing to HDD vs SSD
- pre-partitioning with gparted vs specifying partitions to the
installer vs giving the installer a free had at choosing the partitioning.
A subsequent Ubuntu installation succeeded. I don't know which
version. But Fedora 23 is preferred.
(I'm not present for all this -- I'm helping via phone. So I might easily
be missing some important observation.)
8 years
google cloud printer?
by Neal Becker
I have a couple of epson printers that use google cloud. I can print to
them from chrome. I need to add them as system printers to cups so other
apps can print.
I've used:
https://www.niftiestsoftware.com/cups-cloud-print/
But suddenly it's stopped working. If I try to delete the printers from
cups, and then re-add them:
sudo /usr/share/cloudprint-cups/setupcloudprint.py
...
Error adding: EPSON_XP-410_Series_EPSONE5B487 (1280, u'server-error-
internal-error')
Error adding: EPSON_XP-420_Series_EPSON3E7898 (1280, u'server-error-
internal-error')
Is there any other solution?
8 years
DVD writer firmware upgrade
by Glenn Holmer
I have a Samsung SH-S223B DVD writer and want to upgrade its firmware,
but the firmware upgrade is only provided as an .exe file for W*****s,
which I don't and won't have. Is there a way to install this from Linux?
--
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."
8 years
smplayer volume control
by Andre Robatino
For a long time now, the smplayer (from RPMFusion) volume control is
vertical, instead of horizontal, with a negligible height, so it's
essentially useless. This is still true with the latest version
smplayer-16.1.0-1.fc23, and even after deleting ~/.config/smplayer. Do all
Fedora users see this, and can it be fixed?
8 years
Using Grig
by Antonio M
I am an Ham and I would to use Grig connected to my receiver (Icom
821H).When I start Grig I get:
grig -m 334 -r /dev/ttyUSB0
2016/04/05 17:22:07;;GRIG;;4;;grig_debug_init: Debug handler initialised.
2016/04/05 17:22:07;;GRIG;;4;;Checking GRIG configuration.
2016/04/05 17:22:07;;GRIG;;4;;..Configuration directory: OK
2016/04/05 17:22:07;;GRIG;;4;;..Radio config files:
2016/04/05 17:22:07;;GRIG;;5;;rig_daemon_start entered
2016/04/05 17:22:07;;GRIG;;5;;rig_daemon_start: Initializing rig (id=334)
2016/04/05 17:22:07;;HAMLIB;;4;;rig:rig_init called
2016/04/05 17:22:07;;HAMLIB;;4;;icom: _init called
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (355)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (309)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (310)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (311)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (313)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (314)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (315)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (319)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (320)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (321)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (322)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (367)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (323)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (346)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (324)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (328)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (330)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (326)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (327)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (347)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (357)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (363)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (329)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (362)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (345)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (356)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (360)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (370)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (361)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (331)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (312)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (316)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (332)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (334)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (344)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (368)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (335)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (369)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (336)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (358)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (337)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (338)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (339)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (340)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (341)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (342)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (343)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (366)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (303)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (304)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (306)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (307)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (302)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (352)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (353)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (351)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (364)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (365)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (354)
2016/04/05 17:22:07;;HAMLIB;;4;;rig_register (371)
2016/04/05 17:22:07;;HAMLIB;;4;;rig:rig_open called
2016/04/05 17:22:07;;GRIG;;5;;rig_daemon_start: Init successfull, executing
post-init
2016/04/05 17:22:07;;HAMLIB;;5;;write_block(): TX 6 bytes
2016/04/05 17:22:07;;HAMLIB;;5;;0000 fe fe 4c e0 04
fd ..L...
2016/04/05 17:22:07;;HAMLIB;;5;;read_string(): RX 6 characters
2016/04/05 17:22:07;;HAMLIB;;5;;0000 fe fe 4c e0 04
fd ..L...
2016/04/05 17:22:07;;HAMLIB;;5;;read_string(): RX 8 characters
2016/04/05 17:22:07;;HAMLIB;;5;;0000 fe fe e0 4c 04 05 01
fd ...L....
2016/04/05 17:22:07;;HAMLIB;;5;;write_block(): TX 7 bytes
2016/04/05 17:22:07;;HAMLIB;;5;;0000 fe fe 4c e0 1a 03
fd ..L....
2016/04/05 17:22:07;;HAMLIB;;5;;read_string(): RX 7 characters
2016/04/05 17:22:07;;HAMLIB;;5;;0000 fe fe 4c e0 1a 03
fd ..L....
2016/04/05 17:22:07;;HAMLIB;;5;;read_string(): RX 6 characters
2016/04/05 17:22:07;;HAMLIB;;5;;0000 fe fe e0 4c fa
fd ...L..
2016/04/05 17:22:07;;GRIG;;1;;rig_daemon_check_mode: Can not find frequency
range for this mode (32)! Bug in backend?
2016/04/05 17:22:07;;GRIG;;5;;rig_daemon_post_init: GET bits:
0000000000000000
2016/04/05 17:22:07;;GRIG;;5;;rig_daemon_post_init: SET bits:
0000000000000XXX
2016/04/05 17:22:07;;GRIG;;5;;rig_daemon_start: Starting rig daemon
2016/04/05 17:22:07;;GRIG;;4;;rig_daemon_start: Daemon thread started
2016/04/05 17:22:07;;GRIG;;4;;Initialising key press handler
the graphic interface starts but it doesn't work.
If I use hamlib rigctl -vvvvv -r /dev/ttyUSB0 -m 334 -L
rigctl, Hamlib 3.0.1
Report bugs to <hamlib-developer(a)lists.sourceforge.net>
rig:rig_init called
icom: _init called
rig_register (355)
rig_register (309)
rig_register (310)
rig_register (311)
rig_register (313)
rig_register (314)
rig_register (315)
rig_register (319)
rig_register (320)
rig_register (321)
rig_register (322)
rig_register (367)
rig_register (323)
rig_register (346)
rig_register (324)
rig_register (328)
rig_register (330)
rig_register (326)
rig_register (327)
rig_register (347)
rig_register (357)
rig_register (363)
rig_register (329)
rig_register (362)
rig_register (345)
rig_register (356)
rig_register (360)
rig_register (370)
rig_register (361)
rig_register (331)
rig_register (312)
rig_register (316)
rig_register (332)
rig_register (334)
rig_register (344)
rig_register (368)
rig_register (335)
rig_register (369)
rig_register (336)
rig_register (358)
rig_register (337)
rig_register (338)
rig_register (339)
rig_register (340)
rig_register (341)
rig_register (342)
rig_register (343)
rig_register (366)
rig_register (303)
rig_register (304)
rig_register (306)
rig_register (307)
rig_register (302)
rig_register (352)
rig_register (353)
rig_register (351)
rig_register (364)
rig_register (365)
rig_register (354)
rig_register (371)
rig_pathname: "Path name to the device file of the rig"
Default: /dev/rig, Value: /dev/ttyUSB0
String.
write_delay: "Delay in ms between each byte sent out"
Default: 0, Value: 0
Range: 0.0..1000.0, step 1.0
post_write_delay: "Delay in ms between each command sent out"
Default: 0, Value: 0
Range: 0.0..1000.0, step 1.0
timeout: "Timeout in ms"
Default: 0, Value: 1000
Range: 0.0..10000.0, step 1.0
retry: "Max number of retry"
Default: 0, Value: 3
Range: 0.0..10.0, step 1.0
itu_region: "ITU region this rig has been manufactured for (freq. band
plan)"
Default: 0, Value: 2
Range: 1.0..3.0, step 1.0
vfo_comp: "VFO compensation in ppm"
Default: 0, Value: 0.000000
Range: 0.0..1000.0, step 0.0
poll_interval: "Polling interval in millisecond for transceive emulation"
Default: 500, Value: 500
Range: 0.0..1000000.0, step 1.0
ptt_type: "Push-To-Talk interface type override"
Default: RIG, Value:
Combo: RIG, DTR, RTS, Parallel, CM108, None
ptt_pathname: "Path name to the device file of the Push-To-Talk"
Default: /dev/rig, Value:
String.
ptt_bitnum: "Push-To-Talk GPIO bit number"
Default: 2, Value:
Range: 0.0..7.0, step 1.0
dcd_type: "Data Carrier Detect (or squelch) interface type override"
Default: RIG, Value:
Combo: RIG, DSR, CTS, CD, Parallel, CM108, None
dcd_pathname: "Path name to the device file of the Data Carrier Detect (or
squelch)"
Default: /dev/rig, Value:
String.
serial_speed: "Serial port baud rate"
Default: 0, Value: 19200
Range: 300.0..115200.0, step 1.0
data_bits: "Serial port data bits"
Default: 8, Value: 8
Range: 5.0..8.0, step 1.0
stop_bits: "Serial port stop bits"
Default: 1, Value: 1
Range: 0.0..3.0, step 1.0
serial_parity: "Serial port parity"
Default: None, Value: None
Combo: None, Odd, Even, Mark, Space
serial_handshake: "Serial port handshake"
Default: None, Value: None
Combo: None, XONXOFF, Hardware
rts_state: "Serial port set state of RTS signal for external powering"
Default: Unset, Value: Unset
Combo: Unset, ON, OFF
dtr_state: "Serial port set state of DTR signal for external powering"
Default: Unset, Value: Unset
Combo: Unset, ON, OFF
civaddr: "Transceiver's CI-V address"
Default: 0, Value: 76
Range: 0.0..255.0, step 1.0
mode731: "CI-V operating frequency data length, needed for IC731 and IC735"
Default: 0, Value: 1
Check button.
no_xchg: "Don't Use VFO XCHG to set other VFO mode and Frequency"
Default: 0, Value: 0
Check button.
rig:rig_open called
Opened rig model 334, 'IC-821H'
Backend version: 0.7, Status: Alpha
Rig command: f
write_block(): TX 6 bytes
0000 fe fe 4c e0 03 fd ..L...
read_string(): RX 6 characters
0000 fe fe 4c e0 03 fd ..L...
read_string(): RX 11 characters
0000 fe fe e0 4c 03 00 00 35 45 01 fd ...L...5E..
icom_get_freq: freq len (5) differs from expected
Frequency: 145350000
I can talk with my rig as f command gets the frequency.
What is wrong??
--
Antonio Montagnani
Skype : amontag52
Linux Fedora 23 (Workstation)
inviato da Gmail
8 years
OT: Samsung NX3000 file system
by Geoffrey Leach
Having entered the age of digital photography with the purchase of a Samsung NX3000, I would like to be able to mount it. Fedora 23 sees the device on USB, but I can't find anywhere the file system type. Any clues on how to discover this? Thanks.
8 years
Changing partition sizes on dual boot disks.
by JD
Hi all.
I have a dos partitioned drive.
partition 1 has windoze
there is no partition 2 (it was deleted and it's space added to partition 1,
using the old software called "Partition Magic".
partition 3 is fedora
partition 4 is fedora's swap.
Fedora partition is only using 3% of it's available space:
$ df -k /
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda3 903432024 24820728 832696536 3% /
$ df -k /sda1
/dev/sda1 42015740 41972804 42936 100% /sda1
Can parted handle
1. shrinking partition 3 (i.e. starts at a numerically higher block
number)
2. fixing the installed grub so that I can still boot fedora,
or would I have to boot a live fedora and install grub from
live fedora?
3. adding the freed space to partition 1 so that windoze can
see it and use it as part of it's partition 1?
P.S: I will be backing up sda3, so no fear there. Ditto with sda1.
Thanx.
8 years