In /proc/scsi/scsi, we can see the scsi host no. (scsi identifier no.). for e.g. Host: scsi4 Channel: 00 Id: 01 Lun: 00 In above e.g., scsi identifier no. is 4. Whenever we modprobe a particular module associated with scsi devices, we can see new entry in/proc/scsi/scsi with a greater identifier no. When we do rmmod on that module, the entry from /proc/scsi/scsi wipes off but still the counter of scsi identifier no. doesn't decreases. is is there any way to reset or decrement this counter so that next time when I do modprobe on scsi related module, it will assign no.s starting with 0 ? I found that during registering a scsi device, scsi_register() method gets value from "next_host" (which is a static int initialized to 0) and then increments next_host counter. Also, during scsi_unregister(), it decrements next_host counter. rmmod internally calls scsi_unregister(). So, if it is true then why the scsi host id. doesn't decrement during rmmod?
i am writing block deriver for usb device in linux i want to read and write data to/from usb device i already registered usb device with my driver and opened the handle for the usb device now i need to send scsi command to usb device to make it work but i dont have knowledge about scsi commands and how and where to use them now i need to know which scsi command i need to pass to the usb device and how can i pass that command to usb device also i need some information like how to register host controller with my usb driver
if anyone knows about this or where can find the tutorials / documentation/ framework for the same.
I've just put together a Centos 5.2 system using an old Future Domain SCSI card which would allow me to hook up an external DAT drive. On its BIOS screen it advertises itself as an AHA-2920 which should be handled by the aic7xxx module. However, the module doesn't even get loaded unless I force it in /etc/rc.modules and even then it doesn't pick up the card.
I have a virtual machine with Solaris 10. On this virtual machine I have to configure an iSCSI initiator.
The problem is that i have no physical SCSI devices to connect to my LAN
Therefore I have to create a Virtual SCSI device on my host laptop and configure it as an iSCSI server (iSCSI target) and share this virtual disk on the LAN.
I'm trying to ssh from my laptop to my desktop (both fedora 14) over a local network. I can ping my desktop and get responses, but if I ssh to it, I receive
ssh: connect to host 192.168.100.xxx port 22: No route to host
i m facing same error in most of the HCL servers. the problem is that it throws error while booting and sometimes not throws error. the error is :-
Feb 13 13:17:25 fe13s kernel: Adapter 0: Bus A: The SCSI controller was reset due to SCSI BUS noise or an invalid signal. Check cables, termination, termpower, LVDS operation, etc.
Feb 13 13:17:30 fe13s kernel: Adapter 0: Bus B: The SCSI controller successfully recovered from a SCSI BUS issue. The issue may still be present on the BUS. Check cables, termination, termpower, LVDS operation, etc
Feb 13 13:29:15 fe13s kernel: Adapter 0: Bus B: The SCSI controller successfully recovered from a SCSI BUS issue. The issue may still be present on the BUS. Check cables, termination, termpower, LVDS operation, etc code....
In my understanding, the way /proc/scsi/scsi gets populated, /proc/paritions also gets populated in the same fashion. i.e. the description for first entry of /proc/scsi/scsi can be seen in the first entry of /proc/partitions and same for rest.
So, With this assumption, in my project, I used to relate first entry of /proc/scsi/scsi with first entry of /proc/partitions to get its total size and same for all entries.
But, I observed some differences in following scenario, where
1) The first 4 entries in /proc/scsi/scsi are SAN luns attached to my system and for which the actual device names in /dev/ are sda,sdb,sdc and sdd.
2) The last 4 entries are the internal HDDs on same system. In /dev/, their respective device names are sde,sdf,sdg & sdh.
(Output attached at end of the thread)
But in /proc/partitions, the device order is different.
You can see their respective sizes in /proc/partition output as well.
So, my question is, in this particular scenario, I can't relate the first entry of /proc/scsi/scsi with first entry of /proc/partition. i.e. scsi0:00:00:00 is not /dev/sde, because it is actually /dev/sda.
It seems that my assumption is wrong in this scenario.
Is there any way or mechanism to figure out actual device name for an entry in /proc/scsi/scsi in /dev/ directory?
How can my application should relate /proc/scsi/scsi entries with their respective device names and sizes?
When I enter "cat /proc/scsi/scsi" I'm returned with "cat: /proc/scsi/scsi: No such file or directory". I've tried this on two different installs on two different machines.
Some of our workstations have LTO's attached and they seem to drop off every now and again, the only thing which picks them up again (besides a reboot) is the famous rescan-scsi-bus script from here
The thing is that I'd like non-root users to be able to run this script, which in turn needs root to /proc/scsi/scsi
Right now I have a machine set up running Fedora. I have configured inittab to accept Console Logins, but I am having problems getting my netbook running PuTTY to connect. How would I go about finding the Host Name and Port to connect to?
1. Microsoft Windows 7 64-bit Professional HOST Operating System 2. Oracle VirtualBox 4.0.6r71416 on top of Windows 7 3. Ubuntu 10.04 Lucid Lynx 32-bit GUEST Operating System in VirtualBox
I successfully installed the above configuration on May 15, 2011. I had some difficulty getting the Host-Only VirtualBox Adapter to work. I was forced to make a subtle change to the Windows Registry in order to get the Adapter to work correctly. I was successful. I used the Debian Update Manager to update my installation of Ubuntu. Nothing changed on the Windows 7 side. Now, Windows 7 says that the Host-only adapter is enabled, but I don't have a connection to the Ubuntu OS. I can't use PuTTY or WinSCP. When I invoke ipconfig on the Windows side, 192.168.56.101 is the IPv4 address. When I invoke ifconfig on the Ubuntu side, there isn't anything.
I install and configure the vncserver following and reading 1000papers, but all of this present the same problem; when i try to connect to my vncserver,recive this mesage: unable connect to socket: No route to host (113) The OS version is Fedora Core 14 and tigervnc-server i try different solutions including:Allow TCP connection modifing files /etc/gdm/custom.conf and /usr/share/gdm/gdm.chemas Disable SELinux removing iptables Here follow the vncserver configuration:
[code].....
The ip address of the vncserver is correct because i can do ssh on it. Where or what can i do?
WG111v2 USB that works just fine on my Ubuntu 12.04 Dell can't connect on my Debian Gigabyte. It finds the network name just fine, remembers its password, and tries to connect 3 times before giving up. This tower is 4 days old, as is the OS.
I have a Belkin N150 USB Wireless Network Adapter and a Belkin N150 Wireless Router. I cannot seem to get NetworkManager to connect to the internet. I have blacklisted the 9.10 staging driver and associated rt files. I have downloaded and built the ralink 2.3.0.0 driver. The light flashes on the usb but I cannot connect to internet.
lsusb output: jerry@jerry-desktop:~$ lsusb Bus 002 Device 003: ID 413c:2105 Dell Computer Corp. Model L100 Keyboard Bus 002 Device 002: ID 046d:c50e Logitech, Inc. MX-1000 Cordless Mouse Receiver Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 046d:09c2 Logitech, Inc. Bus 001 Device 005: ID 050d:935b Belkin Components Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lsmod output: jerry@jerry-desktop:~$ sudo lsmod Module Size Used by rt2870sta 554908 1
iwconfig output: jerry@jerry-desktop:~$ sudo iwconfig lo no wireless extensions. eth0 no wireless extensions. ra0 Ralink STA ESSID:"11n-AP" Nickname:"RT2870STA" Mode: Auto Frequency=2.412 GHz Access Point: Not-Associated Bit Rate:1 Mb/s RTS thrff Fragment thrff Encryption keyff Link Quality=10/100 Signal level:0 dBm Noise level:-97 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
I am not sure what the ra0 is telling me but what about the Access Point: Not-Associated statement? Does that mean that the network adapter is not connecting to the router?
We need to fina a wireles adapter that works with Ubuntu.We have a netgear adapter but the OS doesn't recognize it when we plug it into the USB port and there isn't software to install so it will recognize it - only Windows documentation.My daughter loves this OS and wants to keep it but can't connect to our wireless network without an adapter.
I recently moved out of state and don't have access to the net, however the neighbor of where I am staying is nice enough to let me leech off of her network till I get going. I know next to nothing about slackware and wireless networks since I have never had to mess with it. I have done my reading and have gotten this far.
1) wirelss card is installed and recognized, its a PCI b/g card that uses the ath5 module. The module is loaded and seems to be working.
2) I have heard wicd is easy so I installed it from /extra and it found my essid and accepted the wep password and it says connected at 45% and shows an IP.
however when I launch firefox or try to ping out nothing happens.
My laptop has an internal wifi adapter, but I recently purchased another one because of its extended range.susb, shows that the new adapter is:
Code: Bus 002 Device 027: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter After disconnecting my internal adapter from the wireless network, I can scan for networks
I have Ubuntu 9.10, which I just now installed on my Dell Dimension 3000. The computer has all of its USB ports working perfectly; tested in Windows. I plugged in my SMC USB Ez Connect g wireless adapter, and it isn't even recognized by the system. I used lsusb, and nothing except the USB keyboard and mouse shows up. Every time I boot or shut down, I get tons of errors saying that it's "unable to enumerate USB device on Port...," then the port number of whichever port I plug the wireless adapter into. I've tried using ndiswrapper, and have completely installed the Windows drivers using that (which were the same ones that worked perfectly in Windows XP Pro). I've tried looking into compat-wireless and Linux Wireless, and have successfully installed the zd1211rw drivers and everything. The drivers install completely and work, there is just no hardware present, or so it says. This is what the terminal says when I type dmesg, and also part of what shows up on booting and shutdown:
[code]....
I hope I've given enough information. Oh, and I downloaded Ubuntu a few days ago from their website, burned to a CD-R, installed, and downloaded all updates that it asked me to. Other than that and the ndiswrapper and driver installation, I've done nothing on the system.
I have an HP Pavilion dv5 1002nr laptop running Vista. I decided to install Ubuntu using the windows installer, which did install well, but I decided that it wasn't for me, and uninstalled it. Now, my wireless adapter which is a Atheros AR5007 802.11b/g can see the network, find networks by itself, and is supposedly installed correctly according to Vista, cannot connect to any networks at all despite being able to see them and acquire a signal strength. Up until installing Ubuntu I have never had an issue like this. Other devices have no trouble connecting to this network, and I am currently using a Netgear wireless usb dongle to connect to the very network that my Atheros can not connect to.
I've just upgraded my old laptop from xubuntu to ubuntu 10.10 and I have some connectivity problems with my usb adapter Netgear WG111v3. On xubuntu I had no problems with connecting on the network but with ubuntu, it says I have good reception but it doesn't connect on the network (rarely it does, but for a very short time). I have another laptop currently running on ubuntu 10.04 and it has no problems at all (however it has an internal usb card).
I'm having some trouble getting my Zyxel NWD271N usb wireless adapter to connect.I'm using Ubuntu Desktop 64bit 10.10 What happens is that i'm always asked to enter the wpa key, and i've double and tripple checked that it's entered correctly. The wierd thing is that it has connected once or twice, but lost connection quickly, but i saw that i got an ip. I'm not sure about the maximum range on the adapter but i would estimate the distance to be no more than 4-5 meters from the wireless point. Also the signal indicator on the list of wireless networks shows strong, if not full. when i run lsusb i get:
Code:
Bus 001 Device 007: ID 0586:3417 ZyXEL Communications Corp. NWD271N 802.11n Wireless Adapter [Atheros AR9001U-(2)NG] when i run lsmod |grep ar9170 (saw the command on a german forum so i didn't understand what was talked about, but i got that it was about the same adapter) i get:
I felt the urge to build my own "Incredible PBX" system, and in the process downloaded pbxinaflash-i386-5.4.iso which is based on CentOS 5.4. The PC that I'm using is an old desktop, and the onboard ethernet adapter is not working, so I installed Trendnet PCI Adapter (te100-pciwn h/w : 2.2 R), which used to work greatly under Windows XP. Since my on-board ethernet adapater doesn't work, I disabled "eth0" device, and I modified eth1 device to load during boot. But, for whatever reasons, eth1 fails to get the IP address. I thought the driver that is part of CentOS 5.4 may not be working, so I thought of building the driver from the files provided in the CD (that came with TrendNet adapter box).. and unfortunately my attempts to build the driver have also failed.
Following files are attached in the zip file - basedata.R3721 (info collected by ./getinfo.sh all ) - Directory 2.2.X has "te100.c, makefile, kern_compat.h copying.txt" (These files came with the Trendnet CD) - errors (makefile errors when tried to build te100 driver) From what I understand, TrendNet TE100-PCIWN is based on "Realtek Semiconductor Co., Ltd. RTL-8139" chipset. How to get my ethernet adapater (eth1) connected to internet.
I am using the Belkin wireless g usb adapter f5d7050 v1000 or at least that is what ubuntu says when I lsusb.
Code:
ceegee@Valar1:~$ lsusb Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 019: ID 050d:7050 Belkin Components F5D7050 ver 1000 WiFi
I want to run snort through a web application with exec("snort -v -i eth0 ") php function.for example when start button was pressed snort should be run,but the execution failed with this error:but when I run snort command via command line as root it will execute successfully.I think this problem is for that apache user haven't access to network adapter, is my guess correct? I have no experience with apache, should I change apache configuration? what is the configuration for this problem.I think I should find a way to allow apache to access but I don't know how?
I currently have a Nexxt Lynx 150 Wireless USB adapter attatched to one of my home destops to recieve my wifi signal, however, i have run into a speed bump in terms of getting it connected to my ubuntu 11.04. This adapter works perfectly in windows and on the ubuntu live cd, but, when i install ubuntu to my hard drive and try to connect to my network,
it just takes a very long time, then says, disconnected. My signal is WPA2-Personal protected. Here is a link to the adapter's home page > [URL] It seems to me that this is a driver problem. The cd that my adapter came with has drivers for linux on it, but i havent the slightest clue how to use them.
I recently tried to install Crunchbang on my IBM Thinkpad T20 laptop. Everything went OK as far as I can tell (I still have to adjust acpi and display settings), but I cannot get my laptop to connect to the internet via wireless (wired connection works fine). I've done a good deal of searching online, and I realize that my wireless adapter (wpc54gs, bcm4318 chipset) is problematic in linux, and that b43-fwcutter is typically required. I did install b43-fwcutter, and it seemed to install OK, but nothing subsequently happened when I opened networkmanager. I'm not sure at this point if my problem is that I don't know how to configure any wireless adapter in crunchbang, or if it is that my particular adapter is not being recognized.