4 USB TTL uarts on a USB hub - keeping them straight
by Robert Moskowitz
Well, if I had a hub with more ports, I would have more of these, as I
have more systems to interface with the serial console....
Anyway it seems that the dev assignment changes. They are
/dev/ttyUSB[0-3] But at different times they are a different number
which makes it hard to consistantly connect to the desired system.
Is there someway to identify the units and assign them permenant device
names. Much like is done with ethernet?
9 years, 7 months
HD Video editing
by Anders Wegge Keller
Which video editing software is capable of editing HD video? I understand
that there are complications wrt. patents, so I know I'll probably have to
build it myself. That's not a big deal, but I'd rather not have to try out
several different packages, before finding somethuing that's suitable.
The files are made with a Sony handycam (HDR-CX115E), and for reference,
I've uploaded a short clip of raindrops on my patio table, in case there are
more than one HD format to choose from:
<http://wegge.dk/Sample.CPI> -- Clip information.
<http://wegge.dk/Sample.MTS> (10MB) -- The actual clip.
I'd be happy to hear what others are using to edit similar files.
--
//Wegge
9 years, 7 months
WiFi permanently disappeared after booting test kernel
by Mike Fleetwood
Hi,
On my netbook I booted a test kernel 3.8.0-rc4+ I compiled. Now after
booting back into my regular Fedora kernel 3.6.11-5.fc17.i686.PAE my
wifi network device remains permanently disappeared. No wifi networks
displayed in Network Manager gui. Also the Network Manager syslog
messages make it look like the device has completely disappeared.
Suggestions for restoring wifi welcome.
Thanks
Mike
Fragment of Network Manager syslog messages when working before
--8<--
Jan 18 23:01:53 edge NetworkManager[479]: <info> monitoring kernel
firmware directory '/lib/firmware'.
Jan 18 23:01:53 edge NetworkManager[479]: <info> rfkill2: found WiFi
radio killswitch (at
/sys/devices/pci0000:00/0000:00:1c.3/0000:01:00.0/ieee80211/phy0/rfkill2)
(driver ath9k)
Jan 18 23:01:53 edge NetworkManager[479]: <info> rfkill0: found WiFi
radio killswitch (at /sys/devices/platform/eeepc/rfkill/rfkill0)
(platform driver eeepc)
Jan 18 23:01:53 edge NetworkManager[479]: <info> rfkill4: found WWAN
radio killswitch (at /sys/devices/platform/eeepc/rfkill/rfkill4)
(platform driver eeepc)
Jan 18 23:01:53 edge NetworkManager[479]: <info> WiFi enabled by radio
killswitch; enabled by state file
Jan 18 23:01:53 edge NetworkManager[479]: <info> WWAN enabled by radio
killswitch; enabled by state file
Jan 18 23:01:53 edge NetworkManager[479]: <info> WiMAX enabled by
radio killswitch; enabled by state file
Jan 18 23:01:53 edge NetworkManager[479]: <info> Networking is enabled
by state file
...
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): using
nl80211 for WiFi device control
Jan 18 23:01:53 edge NetworkManager[479]: <warn> (wlan0): driver
supports Access Point (AP) mode
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): new 802.11
WiFi device (driver: 'ath9k' ifindex: 3)
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): exported as
/org/freedesktop/NetworkManager/Devices/1
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): now managed
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): device state
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jan 18 23:01:53 edge NetworkManager[479]: <info> (wlan0): bringing up device.
...
Jan 18 23:01:59 edge NetworkManager[479]: <info> Activation (wlan0)
successful, device activated.
Jan 18 23:01:59 edge NetworkManager[479]: <info> Activation (wlan0)
Stage 5 of 5 (IPv4 Commit) complete.
Fragment of Network Manager syslog messages when broken after
--8<--
Jan 28 18:43:26 edge NetworkManager[466]: <info> monitoring kernel
firmware directory '/lib/firmware'.
Jan 28 18:43:26 edge NetworkManager[466]: <info> rfkill0: found WiFi
radio killswitch (at /sys/devices/platform/eeepc/rfkill/rfkill0)
(platform driver eeepc)
Jan 28 18:43:26 edge NetworkManager[466]: <info> rfkill2: found WWAN
radio killswitch (at /sys/devices/platform/eeepc/rfkill/rfkill2)
(platform driver eeepc)
Jan 28 18:43:26 edge NetworkManager[466]: <info> WiFi disabled by
radio killswitch; enabled by state file
Jan 28 18:43:26 edge NetworkManager[466]: <info> WWAN enabled by radio
killswitch; enabled by state file
Jan 28 18:43:26 edge NetworkManager[466]: <info> WiMAX enabled by
radio killswitch; enabled by state file
Jan 28 18:43:26 edge NetworkManager[466]: <info> Networking is enabled
by state file
No (wlan0) related NetworkManager syslog messages afterwards at all.
9 years, 7 months
USB monitor refresh
by CS DBA
Hi All;
I bought a usb powered portable monitor (AOC e1649Fwu) for when I travel...
If I plug in the usb connections before I boot my laptop it works
(Fedora 20, Lenovo W540)
however the refresh rate is slow (I'm guessing) as it doesnt refresh the
screen until I pass the mouse cursor over that area.
It is usable but sortof a pain... thoughts on how to debug/fix this?
Thanks in advance
9 years, 7 months
creating 70-persistent-net.rules
by Robert Moskowitz
This is on a f20 arm system, but it should be like any F20 system. Yeah,
famous last words.
So I want a 70-persistent-net.rules so I can specify the MAC address to
the device name. Then in the ifcfg-xxxx I can change the MACADDR to
what I want.
I got this working on my Redsleeve arm system, but now I need it on my
F20 arm system.
So I have done a little searching on creating 70-persistent-net.rules,
and I come up with two commands:
udevadm trigger
udevadm trigger --action=add
I have run both and no 70-persistent-net.rules
help please...
9 years, 7 months
System starts in emergency mode...how do I recover ?? (as a newbie)
by antonio montagnani
Suddenly my laptop when rebooted doesn't start in the usual way After
six months of hard work) but it stops when bootib with this message
drm:cpt-serr_int_handler ERROR PCH transcoder a FIFO underrun
and the appears some lines with request for password for maintenance
mode or CTRL-D option...
If I open journalctl -xb I see some errors in particular saying that
fsck failed with error code 4 on dev/mapper/fedora and suggestint to use
fsck.
How do I revover from this situation?? (I am writing from this machine
started with CTRL-D option)
Tnx
--
Antonio M
Skype: amontag52
Linux Fedora F20 (Heisenbug)
on Fujitsu Lifebook A512
http://lugsaronno.altervista.org
http://www.campingmonterosa.com
9 years, 7 months
Fedora - client server networking configuration.
by Angelo Moreschini
Hi,
I am using Fedora 20 on two computers and I have also one computer that
use Windows 8.
I wont realize a local network with these computers, but I am a little
confused about the way to arrange my (client server) network configuration .
I understood that DHCP is the core to do the network configuration, but I
have some doubts about how I have to arrange it.
Reading the documentation, I got the opinion that nothing need to do in
the computers that have the role of Clients on the net; instead on the
computer with the role of Server it need to write the file /etc/dhcpd.conf.
That is exact ?
What other important operation need to do to do becouse my local network
works correctly?
It exists a good PRACTICAL tutorial to accomplish this task?
Thank you
regards
Angelo
9 years, 7 months
Get rid of F20G3 screen locker??
by Beartooth
I'm giving Gnome 3 another try, and still find it very annoying
to have to keep re-entering my password. (The machine I have it on is one
of four on a KVM switch.)
I tried removing Gnome's own screensaver and installing
xscreensaver, but that hasn't worked -- yet at least. (I've been too busy
configuring this and another machine to find time yet for a log out and
back in, much less a reboot.)
What I'm trying to eliminate is clearly not part of any
screensaver, but merely a needless defense imposed by some other part of
the OS.
--
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
Remember I have precious (very precious!) little idea where up is.
9 years, 8 months
Latest USB3 Memory Sticks and TRIM
by Dr J Austin
Hi
I have a Corsair Flash Voyager GTX USB3 memory stick which is
advertised as supporting TRIM.
I assume there are several other manufacturers with similar devices
My device is working well (ext4) and is very fast but does not appear to
respond to the TRIM command even though hdparm suggests it should
I have found the same problem referenced here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1336541
but following the kernel link I am not totally convinced things
are happening upstream
Should I bugzilla this against Fedora this or just wait?
John
On fully updated F20
ja@paxos ~ 1$ uname -a
Linux paxos 3.15.10-200.fc20.x86_64 #1 SMP Thu Aug 14 15:39:24 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
[root@paxos:~]$ hdparm -I /dev/sdb
ATA device, with non-removable media
Model Number: Voyager GTX
Serial Number: FF1807470C0800110923
Firmware Revision: S9FM01.7
Transport: Serial, ATA8-AST, SATA 1.0a, SATA II
Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
...
* Data Set Management TRIM supported (limit 8 blocks)
...
root@paxos:~]$ mount -o noatime,discard /dev/sdb1 /media/gtx
[root@paxos:~]$ mount |grep sd
...
/dev/sdb1 on /media/gtx type ext4 (rw,noatime,seclabel,discard,data=ordered)
However dmesg shows
[Aug19 21:21] EXT4-fs (sdb1): mounting with "discard" option, but the device does not support discard
[ +0.000004] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: discard
[ +0.000005] SELinux: initialized (dev sdb1, type ext4), uses xattr
[Aug19 21:24] SELinux: initialized (dev 0:47, type nfs4), uses genfs_contexts
and
[root@paxos:~]$ fstrim -v /media/gtx
fstrim: /media/gtx: discard operation not supported.
9 years, 8 months