My system already had one serial port, ttyS0 which is working.
I've installed a Dynamode 2-port serial card and the kernel sees the two
ports. This provides two ports is:
PCI Spec Revision 2 compliant
Compatible with 16C550 UART
and says that it supports Linux.
However, I can't use them. I've tried using both minicom and faxxaddmodem (I'm
setting up a Hylafax modem bank).
Can anyone suggest what I need to do please.
[root@stan2 ~]# dmesg|grep tty
[ 0.000000] console [tty0] enabled
[ 0.690683] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.711711] 00:04: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.712208] 0000:00:09.0: ttyS1 at I/O 0xec00 (irq = 17) is a XScale
[ 0.712602] 0000:00:09.0: ttyS2 at I/O 0xe880 (irq = 17) is a XScale
[root@stan2 ~]# lspci|grep -i serial
00:09.0 Serial controller: Device 4348:3253 (rev 10)
[root@stan2 ~]# setserial /dev/ttyS1
/dev/ttyS1, UART: undefined, Port: 0xec00, IRQ: 17
[root@stan2 ~]# ll /dev/ttyS*
crw-------. 1 uucp dialout 4, 64 Oct 31 14:33 /dev/ttyS0
crw-rw----. 1 root dialout 4, 65 Oct 31 14:34 /dev/ttyS1
crw-rw----. 1 root dialout 4, 66 Oct 31 14:34 /dev/ttyS2
crw-rw----. 1 root dialout 4, 67 Oct 31 2012 /dev/ttyS3
Group I.T. Manager
I just bought a fast Intel series 520 SSD (240 GB, 550 MBytes/sec) to
replace my slower series 320 SSD (120 GB, 250MBytes/sec). I was
expecting the speed when reading the ssd to jump from my current read
speeds of around 250 MBytes/sec to (hopefully) something at least twice
that speed. The specs say the 520 does 550 MBytes/sec for read and
almost that for write. To my surprise the series 520 was only ~130
MBytes/sec. This is observed under Fedora-17 using "dd if=/dev/sdb2
of=/dev/null bs=64k count=1000". The board is an older Asus M3A78T and
has been happily running the 320 at full rated speed for 1.5 years.
Intel series 320:
dd if=/dev/sda2 of=/dev/null bs=64K count=1000
1000+0 records in
1000+0 records out
65536000 bytes (66 MB) copied, 0.254144 s, 258 MB/s
Intel series 520:
dd if=/dev/sdb2 of=/dev/null bs=64K count=1000
1000+0 records in
1000+0 records out
65536000 bytes (66 MB) copied, 0.494915 s, 132 MB/s
These number stay relatively constant, no matter how many seconds of
transfer I do. Ditto for changing block size (bs=...) up to 1MByte. I
see these numbers for the 520 when I attach it on the same SATA
3Gbit/sec link as the 320 or if I attach it on a new SATA 6Gbit/sec
controller (Highpoint Rocket 620, a Marvel 88SE9125 PCIe SATA 6.0 Gb/s
controller). I do see it attach at 3 Gbit/sec on the old controller and
6 Gbit/sec on the new controller. (So it isn't going down to SATA-1
speeds as far as the printf's I can see indicate.)
Is the 520 defective? Ideas? The reviews of the 520 all show it
really truly doing > 500MBytes/sec. These suckers can really fly.
Just not for me...
Google searches show that some folks running MS software have had
similar problems and they managed to fix things by downgrading their
BIOS setting to use IDE settings for the SSD. Other hits mentioned
something about power management on the SATA being the culprit and IDE
drivers nailed the power on instead of letting it flap in the wind. Is
this something I can turn off from userland without recompiling the
Running FC17 with LXDE -- I did not load any gnome packages off the install
I want two or three X11 sessions running simultaneously as user1 on tty1
user 2 on tty2, user 3 on tty3 ...
1) I have one active LXDE desktop on pts/0 as user1 running perfectly from
the startup scripts
2) Switching over to tty2 -- I login into user2 and type startx -- :1 ...
3) "failed to load session gnome" appears X windows error screen.
... later the error messages are:
a) xauth: file /home/user2/.serverauth.xxxx does not exist"
b) config dir /etc/X11/X0rg.conf.d
c) system config dir: /usr/share/X!!/xorg.conf.d
I'm guessing the problem is in the /etc/X11/xinit directory ... based
find /etc/X11/ -type f | xargs grep -i3 gnome
... reveals a lot of specific code for gnome but not LXDE
What do I need to change ?? Or .. I'm always up for the better idea to get
these multiple sessions up and running. :-)
I was installing fresh copy of fedora 17. I used /dev/sda, where the windows 7 exists, as bootloader drive. At the end of the installation of packages, error is coming "There was an error installing the bootloader. The system may not be bootable"