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."
4 years, 3 months
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?
4 years, 3 months
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
4 years, 3 months
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.
4 years, 3 months
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.
4 years, 3 months
F23 install from hard disk
by Amadeus W.M.
I haven't upgraded my machines in a while and I couldn't find any
reference on how to install directly from the hard disk, without media.
Is this still possible? None of my pcs boot off of a usb stick and the
cdrom I think is failing on one of them, so I really need to install from
the disk. Any suggestions? Thanks!
4 years, 3 months
any simpler option to overlaying header file dirs than funionfs?
by Robert P. J. Day
a project i was recently introduced to uses, quite heavily, the
notion of overlaying header file directories with the now-obsolete gcc
"-I-" option, and i'm curious if there are equivalent solutions that
don't use that feature.
summary: sizable C (and possibly, not sure, some C++) code base
contains numerous, quote-surrounded header file includes of the form:
h1.h;
#include "h2.h"
... etc etc ...
where the header file "h2.h" is frequently in the same directory as
"h1.h" *but* it may not be the one that should be included.
instead, the build system is currently replete with gcc build
commands of the form:
$ gcc -I- -Id1/ -Id2/ -Id3/ ... and so on and so on ...
and "-I-" is used to force the preprocessor to resolve references to
"headerfile.h" not by looking in the current directory first, but by
scanning a list of "overlay" directories to see if someone has
registered a "higher-priority" header file by that name. it's not the
most intuitive build structure i've ever seen but it's been around for
quite some time and it works and its users really don't want to have
to mess with it.
[SIDE NOTE: the current usage of "-I-" in this project is not so much
to "split" the header file search path as that option is used right at
the *beginning* of all the "-I" options, so its use is to simply
refuse to look locally for header files and immediately start scanning
the "-I" directories. but that doesn't really change the problem to be
solved.]
predictably, now that gcc 5 has obsoleted the "-I-" option, one
would like to find an alternative that doesn't require a wholesale
reworking of the build system. since the build system runs on centos,
my current thought is to use "funionfs" to unionize those overlay
directories in the same priority sequence.
i just tried a trivial funionfs example and it seems to work, but is
there a simpler solution? the gcc folks, in deprecating, then
obsoleting, the "-I-" option, insist that one can use "-iquote"
instead, but that is clearly incorrect -- the requirement here is that
resolving a preprocessor include of the form:
#include "rday.h"
*must* *not* look in the current directory first. if there is some way
to get that effect without "-I-" and without some sort of unionfs, i'd
like to know what it is.
thank you kindly.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
4 years, 4 months
cpio Digest mismatch error?
by Tom Horsley
Anyone have any idea why only fedora systems would give this
error installing an rpm?
Installing : ccur-ntrace-ai-7.5-0.beta.75.x86_64 19/32
Error unpacking rpm package ccur-ntrace-ai-7.5-0.beta.75.x86_64
error: unpacking of archive failed on file
/usr/lib/NightTrace/illuminators/ccur_rt/ccur_rt.h;56fd10d8: cpio: Digest
mismatch
error: ccur-ntrace-ai-7.5-0.beta.75.x86_64: install failed
The exact same rpm installs fine on a centos 7.2 system.
Even on fedora, if I use rpm2cpio and extract the files, there is
absolutely nothing wrong with the ccur_rt.h header file.
4 years, 4 months
Getting rtl8192eu driver.
by Michael D. Setzer II
I just got 4 usb 802.11n nics, and they were not recognized by fedora 23??
Windows 10 did seem to have no problems, and they are rtl8192eu.
Did find a page that talked about getting them to work, but the install script
failed with errors. First Error was about __DATE__ and __TIME__ macros,
so found an option to add to the Makefile to ignore that.
The second error involved strnicmp issues, and eventually found a reference
to replace that with strncasecmp. With that change the script does seem to
complete. First time it didn't seem to work, but then the wlassistant was able
to see the device and was able to connect to a wireless hub.
Wondering if someone knows of a better solution?
Thanks.
+----------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor
Guam Community College Computer Center
mailto:mikes@kuentos.guam.net
mailto:msetzerii@gmail.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+----------------------------------------------------------+
http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned: 19,471
Processing time: 32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)
BOINC@HOME CREDITS
ABC 16613838.513356 | EINSTEIN 93508184.955695
ROSETTA 42378641.476131 | SETI 78948334.109332
4 years, 4 months
