I picked up as Dynex usb2serial converter to use with my cisco router/switch. The dongle works fine if plugged into a windows box & puTTy, but I cannot get it to work with Fedora 14. When I try to use cute, mini or command line it tells me it cannot open the connection. Here is the output from lsusb and dmesg. susb output:
[code]....
I am using a Prolific pl2303 USB<=>Serial adapter. dmesg reports everything seems ok when I plug it in (see below) but when I open the ttyUSB0 port in minicom, it is always offline and nothing works. Also, minicom reports:
[code]....
If I plug the adapter into a different machine (Windows) everything works fine. The serial port is setup correctly (9600-8-N-1) What can I do to get this working?
usb 5-2: new full speed USB device using uhci_hcd and address 3
usb 5-2: configuration #1 chosen from 1 choice
pl2303 5-2:1.0: pl2303 converter detected
usb 5-2: pl2303 converter now attached to ttyUSB0
usb 5-2: New USB device found, idVendor=067b, idProduct=2303
[Code]....
I am hoping to be able to get an old serial-touchscreen to work with a usb/serial adapter. I had this touchscreen working some years ago on different hardware. I would like to hook it to the machine I am setting up as a multimedia host with mythtv among other things.
Following the instructions I left behind when I got this to work way back when does not work. See [URL] ....
This info is a work around to get the xserver to see the touchscreen. [URL] ....
I do know that the touchscreen works as I am able to get garbage on the screen as in the first part of my howto. But I have not had any success getting xorg to see it. I wish I had posted a copy of the xorg.conf at the time, but......
There is an issue with the current xserver in testing that I am hoping the next update (in unstable) will fix when it gets pushed to testing. That is that Code: Select all# X -configure fails with a segfault. So I am not able to generate the xorg.conf needed to get it to work. I was going to post a bugreport, that is when I found out there is an update in unstable, so I am waiting for it to get pushed at the moment.
Anyway I am hoping that I can link /dev/ttyUSB0 to /dev/tty0 and get it to work. I would like some kind of guess as to my chances of success before I go to all the work of getting the monitor hooked to the host.
Does an have Mocship MCS9901 adapter in use. I cannot even install driver. Is ti the PC adapter between since this is express card. What to do?.
make[1]: *** [_module_/home/Xx_Xxx/Desktop/MCS9901_Linux/version1.6/starex] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.31.12-174.2.3.fc12.i686'
make: *** [default] Error 2
Well this my first time working with linux and openSUSE, and I love it. But one problem I can't overcome is my network card is not working. I went to bestbuy and bought the dynex enchanced wireless G card.
Model # dx-ebnbc
ver. 1011
I installed wine to run the .exe but that did nothing and gave me that the dll is not registered. openSUSE detects that the card is plugged in but the card does not light up or activate in anyway. The only way I can connect to the net is through an Ethernet cable.
I have a hp zd 7000, i really like this laptop, the onboard ethernet will not work at all. i purchased a dynex wired ethernet pcmcia card to get on the internet with. i have had no luck getting on the internet with it it will light up so i am getting power but no transmitting light works at all i have three net work cards listed in the system. one is the wireless. and the other two are the wired eth0 is the onboard and eth2 is the dynex what can i do next to determine the problem i do not use the wireless at all.
View 1 Replies View RelatedI have a 10 year old Dell Latitude CPx that has no ethernet or modem ports, and the only way to connect to the internet is the Dynex Wireless G DX-BNBC PCMCIA card. It came with Windows 98, and I put Xubuntu on it for a while. I believe it was Xubuntu 8 or 9. Back then I had no clue what to do whatsoever, so after a couple weeks removed it and put Windows 2000 on it. It worked, I used it for a while, but it was slow and 2000 took up a lot of space on the 12gb hard drive after all the updates. I left it forgotten and gathering dust for the past year.
Then a few days ago I discovered Lubuntu 10.10, and from what I've seen so far it is definitely a lot more compact and faster than 2000. However, the wireless card still won't work. It's somewhat recognized, because whenever I unplug it and plug it in a bubble pops up saying "you've been disconnected from the network"... which is odd, since it never says I'm connected, and says that the firmware is missing for this card. Anyway, I discovered something this time. By running "lspci -nn | grep -i 14e4":
[Code]....
i need a usb to rs-232 converter to get into the console port i have an aten uc-232a converter and i have downloaded a .gz file called uplcom.4freebsd.gz i have unpacked it but i do not know what to do from here could some one please help i need to do some practice for the external icnd 2 exam and i have left it to the last minute as per usual.
View 2 Replies View RelatedI need a to add a usb serial port adapter. Are they all basically the same? Do I need to find a Linux compatibility list before I go shopping?
View 1 Replies View RelatedI am using a Sealink PN 2202 USB serial adapter on a linux box (Ubuntu 10.4) running kernel 2.6.32-28-generic. I have written a perl script to simply log the incoming RS232 data (9600 8N2) and it works fine when I start it from a bash shell:
perl /home/pk/PerlCode/RS232_D4_v11.pl
However, I need the computer to boot and start logging after a POR. If I try to use Startup Manager to execute my script everything seems ok but I randomly loose about 20% of the incoming RS232 data. In Startup Manager I use the command
gnome-terminal --title="D4 RS232 Log" --execute bash -c "perl
/home/pk/PerlCode/RS232_D4_v11.pl"
If I close the automatically-started script and restart it from a bash shell, I again will randomly loose about 20% of the incoming RS232 data. It almost seems like I have screwed up the driver by using the Startup Manager. The only way I can get reliable logging again is to remove the script from Startup Manager, then restart the computer and manually launch the perl script. I was thinking that maybe the order in which the driver was loaded and perl script started might be an issue. So I tried a bash script that sleeps for 15seconds, then starts the perl script. Again, I loose random pieces of incoming data when this is initiated by Startup Manager.
Here is some more info:
lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 004: ID 0c52:2223 Sealevel Systems, Inc.
Bus 002 Device 003: ID 0c52:2213 Sealevel Systems, Inc.
Bus 002 Device 002: ID 03eb:3301 Atmel Corp. at43301 4-Port Hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub .....
sudo cat /proc/tty/driver/usbserial
usbserinfo:1.0 driver:2.0
0: module:ftdi_sio name:"FTDI USB Serial Device" vendor:0c52
product:2213 num_ports:1 port:1 path:usb-0000:00:1d.0-2.1
1: module:ftdi_sio name:"FTDI USB Serial Device" vendor:0c52
product:2223 num_ports:1 port:1 path:usb-0000:00:1d.0-2.2
ls -al /dev/ttyUSB*
crw-rw---- 1 root dialout 188, 0 2011-03-08 09:56 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 1 2011-03-08 09:56 /dev/ttyUSB1
I am a member of the group dialout.
I though it may have something to do with su vs my ownership of files. If I do a sudo chmod 777 /dev/ttyUSB* then
ls -al /dev/ttyUSB*
crwxrwxrwx 1 root dialout 188, 0 2011-03-08 09:56 /dev/ttyUSB0
crwxrwxrwx 1 root dialout 188, 1 2011-03-08 09:56 /dev/ttyUSB1
However, after rebooting it reverts to
ls -al /dev/ttyUSB*
crw-rw---- 1 root dialout 188, 0 2011-03-08 09:56 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 1 2011-03-08 09:56 /dev/ttyUSB1
Im a very basic Linux/ Centos user. I have Putty installed and a USB to serial adapter. All settings seem to be right as far as speed, etc, but I'm not sure how to list the device to open for the program. The default location it gives is "/dev/ttyS0" Trying to find where the USB is located using the "/sbin/lsusb" command gives me-
Bus 001 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 004 Device 002: ID 0557:2008 ATEN International Co., Ltd UC-232A Serial Port [pl2303]
Bus 004 Device 001: ID 0000:0000
So I think this means that it is on bus 4 correct? So how do I list this for putty to open the device.
I have a usb serial adapter and was happily using minicom with it under openSUSE 11.2. I've upgraded to openSUSE 11.3 and I can only use minicom with this serial adapter as root. I had previously had problems writing to /var/lock under openSUSE 11.2 which I worked around by changing the minicom config to use /tmp as its lock file location.
Unfortunately my laptop doesn't have a built in serial port so I can't tell if its a general problem or something specific to the /dev/ttyUSB0 device. This is the output I get when I run minicom with my regular user account. I get the same output whether the lock file location is set to /tmp or /var/lock
Code:minicom usb0 Device /dev/ttyUSB0 lock failed: Permission denied. Before I started tinkering my user belonged to the following groups groups=16(dialout),33(video),100(users) I've since added 5(tty),14(uucp),21(console) but still no joy.
after installing the OS my mouse was not working. After searching in net for a day, I made it working. Shall give the details hereIf its a repeat thread please ignore it.1. Go to Terminal.2. Login as root.3. su -c 'yum install -y system-config-display'This step will take some 2 to 5 mins 4. su -c 'system-config-display --reconfig'After Fedora 9/10, the xorg.conf is not available and it uses HAL to detect the hardwares. The above steps create the config file.
5. su -c 'cp /etc/X11/xorg.conf /etc/X11/xorg.conf.bak'
back up
6. su - -c 'gedit /etc/X11/xorg.conf'
[code]....
I've just had to change the MOBO and trying to get the serial port working, I see from previous posts there are some problems lurking in the past.
setserial -g /dev/ttyS*
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
/dev/ttyS1, UART: unknown, Port: 0x02f8, IRQ: 3
/dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4
/dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3
but I'm not seeing anything from a GPS receiver in NMEA at 4800 no par 1 stp I know that was working about a year ago. I think udev was not helping ,as I was getting permission denied to the com port, I added myself to group dialout. and no message on startup now
I need to be able to talk to a piece of kit with 9600 baud and nothing. I have win32 s/w to drive it , but it falls over in wine. My laptop still has win7 on it in a tiny partition but no 9w d connector and I'm waiting for a USB converter cable. Too many variables ! I'd forgotten all the hassle of having to install drivers just to get basic things running. But as the stupid thing couldn't manage using the driver for my NIC, I was stuck with hyper-terminal, and nothing from the GPS board @4800 or another piece of equipment running at 9600. I suspect the com port on the new mobo doesn't wan to play
I tried connecting my Debian laptop to a vintage Apple //e using a Super Serial Card on the Apple side and a USB to serial adapter on the laptop side. It kind of works -- I can send data over to the Apple using e.g. echo "foobar" > /dev/ttyUSB0 or via minicom --, but every 20 seconds (quite exactly!) some 4 random characters appear on the Apple's screen (mostly tildes, sometimes a pipe). This does *not* happen when booting the laptop into Debian rescue mode; so I guess it must be some (daemon?) process messing around with the usb serial device in regular intervals.
I tried to disable quite some services, but the problem remains.I don't have any clue how I might catch the evil-doer in the act -- virtually all serial monitors I've so far read about allow only monitoring the interaction of a known program/process with a serial port. But in this case I first have to actually find out which process is talking to the serial port in the first place.
Now that the xorg.conf file seems to be a thing of the past, where do I put my serverlayout commands etc in order to get the serial touchscreen working? It responds to touchcal but doesn't work in normal use, so I presume it just needs X to be forced into loading it at startup.
View 2 Replies View RelatedI have bought a so-called web'n'walk stick, which identifies itself as a "Globetrotter HSDPA Model". I managed to get it identified as a serial device (initially, it is detected as a USB drive), but I fail to get it working.
Things that might be of interest:
Code:
Code:
i have dell inspiron n4010 having widdcomm bluetooth device and i am using fedora 14. it shows bluez-daemon not working when i start kbluetooth and it shows bluetooth adapter not detected.
View 6 Replies View RelatedI recently got Fedora 14 installed and much to my dismay my Ethernet adapter (Intel 82566DC) didn't work. This is left me disconnected from the internet and made it impossible to install any packages. Googling and searching the forums got me these bits of information: [URL]. From what I gather, the 2.6.35 kernel is at fault. So I can solve this by installing the most recent e1000e ethernet drivers. Long story cut short, it didn't work too well for me. I couldn't simply make+make install it, which demanded other packages to be installed first. These in turn had other dependencies. After several failed attempts and ideas I'm at my wits and end and left with two options:
1. Installing an RPM (hopefully it shouldn't have any dependencies). Is there a site where I can download the driver RPM directly? I can't install and use rpmbuild, because I can't even connect to the internet.
2. Waiting for a newer version of the kernel. How long will I have to wait and how easy will it be to update it, without internet connectivity?
I use Fedora now for 2 days and all worked fine, but now I have a problem:My wireless internet doesn't work anymore. Normally I see a icon at topbar that tells me I'm connected but now it doesn't.I connected my laptop to my router directly and downloaded WiFi radar to see if that works. That program says: "Not connected".I'm sure the internet card is connected and the switch on my laptop is on. I only deleted BlueTooth, but I don't think that's the problem.
View 1 Replies View RelatedI am running Fedora 14. I've had an ASUS wireless adapter working for a few months now, with no problems. Today, I installed updates, one of which required a computer reboot (not just logging out and back in). I rebooted the computer, and when it came back up, the wireless adapter did not work.The adapter is visible after lsusb, but there is no wireless showing after iwconfig. What happened? How do I fix it?
View 10 Replies View RelatedThis is my startup routine:
I log on and Network Manager shows no wireless adapter.
I go to System > Administration > Network:
There are two entries in the Devices tab: Wireless and Ethernet
As soon as I double click the Wireless device and the configuration pops up, the device starts working (no changes to the settings are made)
I have the following set to ON:
- Controlled by Network Manager
- Activate device when computer starts
- Allow all users to enable and disable this device
I have a logitech c310 webcam. When I open cheese, I get a blank. Also my wifi adapter stops working - it doesn't show up on lsusb anymore. How do I fix this? How do I get both my wifi adapter and camera to work at the same time and how do I get my webcam to work? The adapter is D-Link DWA-125. Here are the outputs for lsusb:
[Code]...
I'm trying my to get my 3-year-old Dynex wireless dongle to work in Ubuntu 10.04 (64-bit). Borrowing a similar linksys adapter from another computer running Ubuntu, I was able to install NDISGTK and transfer the same drivers that work in my 64-bit Windows 7 installation into my home folder.
Despite the fact that the dongle does not appear at all using lshw -C Network, ndiswrapper -l indicates that the driver is installed and the device is present. I think I found something interesting, though, when I tried this command:
Code:
jimmy@ubuntu:~$ dmesg | grep -e ndis -e wlan
[ 9.321323] ndiswrapper version 1.55 loaded (smp=yes, preempt=no)
[ 10.021542] ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisMIndicateReceiveNetBufferLists'
[ 10.021549] ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisAllocateIoWorkItem'
[ 10.021554] ndiswrapper (import:242): unknown symbol: NDIS.SYS:'NdisFreeIoWorkItem'
[Code]...
I just installed it along side of Windows 7. I have a Dynex wireless PCI card that I cannot get to work. I am also new to using a Command Prompt
View 7 Replies View RelatedI have RHEL 5.3 installed on HP ProLiant DL320 Generation 5 but i cant get serial port workingdmesg | grep ttyserial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
setserial -g /dev/ttyS[0123]
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
/dev/ttyS1, UART: unknown, Port: 0x02f8, IRQ: 3
[code]...
I'm new to ubuntu. I'm trying to get my US Robotics external serial modem working so I can use Ubuntu.
I copied
wvdial & dependencies:
libuniconf4.6
libwvstreams4.6-extras
libwvstreams4.6-base
to a flash drive.
How do I get them to /var/cache/apt/archives? I tried to copy and drag&drop wont work.
I am using linux 2.6.20 from ltib-mpc8313erdb-20070824 on my development board having MPC8313 powerpc processor. Whenever I plug-in the USB device, the serial port starts mal-functioning. It does not receive all the packets.
View 1 Replies View RelatedI am trying to get two way serial communications going between a Windows XP system and a Linux system (RHEL 5).I have /sbin/agetty -L 9600 ttyS0
in /etc/inittab. I am using a generic USB to serial adaptor on Windows (Unitek) and a null modem cable. I have putty configured for 9600 baud, 8 bits, no parity, one stop bit, no flow control.I get the login prompt from agetty in the putty window but input does not work; I see weird characters in the putty screen. I can echo output into the device from windows and see it, but
cat < /dev/ttyS0. just prints out weird characters from what I type.
On my CentOS 5.2 install I've installed a dual-port serial card based on the NetMOS 9835 chipset. I've followed the serial instructions, but everything they tell me to do is already done - see setserial outputs below. I've compared these values to the lspci output (below, NetMos card is at the bottom of the output) for the card and it appears right. Problem being, I can't use the serial ports. Oh and I did use search, and looked at every 9835-related article before posting this :)
[Code]....