Internet Connectivity through Dlink wireless dogle in Cent OS 5

nishil032 · 12-02-2014, 11:01 PM

Can Somebody help me to connect my Dlink DM 156 Dogle to my PC installed with Cent OS-5 because I'm a newbie to Linux and I have no Idea of making it out

ondoho · 12-03-2014, 12:22 PM

hello, i'm no expert myself, but i do know that centos 5 is pretty old!
it probably can't recognize your hardware because of that.

if you want to solve your problem and need help from others, please supply some real information, like what is suggested in this thread.

nishil032 · 12-04-2014, 03:58 AM

Dear ondoho,

Thanks for your quick display:

In this iam really need to connect my Dlink dwm 156 dogle with my desktop (intel dual core,1GB ram,160 HDD,no graphic card...) loaded with the Cent OS 5
The need for my intention is to connect to internet with this dogle (http://www.dlink.co.in/products/?pid=459)

Thank You,
Nishil

ondoho · 12-12-2014, 01:08 AM

sorry it took so long to reply.

if you still have the problem, please plug in the dongle, wait 10 seconds, then post output of

Code:

lsusb
dmesg

nishil032 · 12-12-2014, 08:06 PM

Code:

[root@localhost nishil]# /sbin/lsusb 

Bus 005 Device 001: ID 0000:0000 

Bus 002 Device 001: ID 0000:0000

Bus 003 Device 001: ID 0000:0000  

Bus 001 Device 002: ID 2001:a80b D-Link Corp. [hex]              ###This is my Device

Bus 001 Device 001: ID 0000:0000

Bus 004 Device 001: ID 0000:0000

For dmesg it seems such a big output:::

Code:

[root@localhost nishil]# dmesg 

Linux version 2.6.18-194.el5xen (mockbuild@builder16.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Fri Apr 2 16:16:54 EDT 2010
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000036d98000 (usable)
149MB HIGHMEM available.
727MB LOWMEM available.
NX (Execute Disable) protection: active
On node 0 totalpages: 224664
  DMA zone: 186366 pages, LIFO batch:31
  HighMem zone: 38298 pages, LIFO batch:7
found SMP MP-table at 000fe200
DMI 2.4 present.
ACPI: RSDP (v000 INTEL                                 ) @ 0x000fe020
ACPI: RSDT (v001 INTEL  D945GCR  0x00000032      0x01000013) @ 0x3f6fd038
ACPI: FADT (v001 INTEL  D945GCR  ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode:  Flat.  Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Built 1 zonelists.  Total pages: 224664
Kernel command line: ro root=LABEL=/ rhgb quiet
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
CPU 0 irqstacks, hard=c0758000 soft=c0738000
PID hash table entries: 4096 (order: 12, 16384 bytes)
Xen reported: 1995.063 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Software IO TLB enabled: 
 Aperture:     2 megabytes
 Kernel range: 0x00000000c17c6000 - 0x00000000c19c6000
vmalloc area: ee000000-f4ffe000, maxmem 2d7fe000
Memory: 867660k/898656k available (2184k kernel code, 22132k reserved, 897k data, 176k init, 153192k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 4989.30 BogoMIPS (lpj=9978600)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
SELinux:  Starting in permissive mode
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 1fc99371 00100000 00000000 00000000 00000281 00000000 00000000
CPU: After vendor identify, caps: 1fc99371 00100000 00000000 00000000 00000281 00000000 00000000
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 1024K
CPU: After all inits, caps: 1fc99371 00100000 00000000 00000140 00000281 00000000 00000000
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
ACPI: Core revision 20060707
CPU 1 irqstacks, hard=c0759000 soft=c0739000
ENABLING IO-APIC IRQs
SMP alternatives: switching to SMP code
Brought up 2 CPUs
Initializing CPU#1
sizeof(vma)=88 bytes
sizeof(page)=32 bytes
sizeof(inode)=340 bytes
sizeof(dentry)=136 bytes
sizeof(ext3inode)=492 bytes
sizeof(buffer_head)=52 bytes
sizeof(skbuff)=176 bytes
migration_cost=12
checking if image is initramfs... it is
Freeing initrd memory: 5670k freed
Grant table initialized
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Not using MMCONFIG.
PCI: Using configuration type 1
Setting up standard PCI resources
Allocating PCI resources starting at 50000000 (gap: 40000000:bff80000)
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: No dock devices found.
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI quirk: region 0400-047f claimed by ICH6 ACPI/GPIO/TCO
PCI quirk: region 0500-053f claimed by ICH6 GPIO
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P32_._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 *9 10 11 12)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT]
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 12 devices
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
pnp: 00:06: ioport range 0x500-0x53f has been reserved
pnp: 00:06: ioport range 0x400-0x47f could not be reserved
pnp: 00:06: ioport range 0x680-0x6ff has been reserved
PCI: Bridge: 0000:00:1c.0
  IO window: 1000-0000
  MEM window: 50000000-00000000
  PREFETCH window 0x0000000050200000-0x00000000502fffff
PCI: Bridge: 0000:00:1e.0
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 17 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1c.0 to 64
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
type=2000 audit(1418419354.684:1): initialized
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
SELinux:  Registering netfilter hooks
Initializing Cryptographic API
alg: No test for crc32c (crc32c-generic)
ksign: Installing public key data
Loading keyring
- Added public key 285B5C47ED7A1E8E
- User ID: CentOS (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Boot video device is 0000:00:02.0
PCI: Setting latency timer of device 0000:00:1c.0 to 64
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Real Time Clock Driver v1.12ac
hpet_acpi_add: no address or irqs in _CRS
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 945G Chipset.
agpgart: Detected 7932K stolen memory.
agpgart: AGP aperture is 256M @ 0x40000000
brd: module loaded
Xen virtual console successfully installed as ttyS0
Event-channel device installed.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH7: IDE controller at PCI slot 0000:00:1f.1
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 17
ICH7: chipset revision 1
ICH7: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x20b0-0x20b7, BIOS settings: hda:DMA, hdb:pio
Probing IDE interface ide0...
hda: HL-DT-STDVD-RAM GH22NP20, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
Initalizing network drop monitor service
Freeing unused kernel memory: 176k freed
Write protecting the kernel read-only data: 394k
input: AT Translated Set 2 keyboard as /class/input/input0
logips2pp: Detected unknown logitech mouse model 89
ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 18, io mem 0x501c4000
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 18
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: irq 18, io base 0x00002080
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 19
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: irq 19, io base 0x00002060
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: irq 17, io base 0x00002040
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
input: ImExPS/2 Logitech Explorer Mouse as /class/input/input1
ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:1d.3 to 64
uhci_hcd 0000:00:1d.3: UHCI Host Controller
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1d.3: irq 20, io base 0x00002020
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
SCSI subsystem initialized
libata version 3.00 loaded.
ata_piix 0000:00:1f.2: version 2.12
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
PCI: Setting latency timer of device 0000:00:1f.2 to 64
scsi0 : ata_piix
scsi1 : ata_piix
ata1: SATA max UDMA/133 cmd 0x20c8 ctl 0x20ec bmdma 0x20a0 irq 19
ata2: SATA max UDMA/133 cmd 0x20c0 ctl 0x20e8 bmdma 0x20a8 irq 19
ata1.00: ATA-7: Hitachi HDS721616PLA320, P22OABGA, max UDMA/133
ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32)
ata1.00: configured for UDMA/133
  Vendor: ATA       Model: Hitachi HDS72161  Rev: P22O
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
 sda: sda1 sda2 < sda5 sda6 sda7 sda8 > sda3 sda4
sd 0:0:0:0: Attached scsi disk sda
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised: dm-devel@redhat.com
device-mapper: dm-raid45: initialized v0.2594l
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
type=1404 audit(1418419378.433:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
type=1403 audit(1418419378.777:3): policy loaded auid=4294967295 ses=4294967295
intel_rng: FWH not detected
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:01:00.0 to 64
eth0: RTL8101e at 0xee0d4000, 00:19:d1:7c:b9:de, XID 14000000 IRQ 254
hda: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, UDMA(66)
Uniform CD-ROM driver Revision: 3.20
input: PC Speaker as /class/input/input2
ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 19 (level, low) -> IRQ 19
sd 0:0:0:0: Attached scsi generic sg0 type 0
ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 21
PCI: Setting latency timer of device 0000:00:1b.0 to 64
hda_codec: ALC662 rev1: BIOS auto-probing.
floppy0: no floppy controllers found
lp: driver loaded but no devices found
SELinux: initialized (dev ramfs, type ramfs), uses genfs_contexts
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
ACPI: Power Button (FF) [PWRF]
ACPI: Sleep Button (CM) [SLPB]
ACPI: Mapper loaded
dell-wmi: No known WMI GUID found
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
device-mapper: multipath: version 1.0.5 loaded
loop: loaded (max 8 devices)
EXT3 FS on sda8, internal journal
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SELinux: initialized (dev sda3, type ext3), uses xattr
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
Adding 1052248k swap on /dev/sda4.  Priority:-1 extents:1 across:1052248k
SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts
IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com>
Loading iSCSI transport class v2.0-871.
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
cxgb3i: tag itt 0x1fff, 13 bits, age 0xf, 4 bits.
iscsi: registered transport (cxgb3i)
Broadcom NetXtreme II CNIC Driver cnic v2.1.0 (Oct 10, 2009)
Broadcom NetXtreme II iSCSI Driver bnx2i v2.1.0 (Dec 06, 2009)
iscsi: registered transport (bnx2i)
iscsi: registered transport (tcp)
iscsi: registered transport (iser)
iscsi: registered transport (be2iscsi)
ip6_tables: (C) 2000-2006 Netfilter Core Team
ip_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
ip_conntrack version 2.4 (7020 buckets, 56160 max) - 228 bytes per conntrack
PCI-DMA: Out of SW-IOMMU space for 16383 bytes at device 0000:01:00.0
PCI-DMA: Out of SW-IOMMU space for 16383 bytes at device 0000:01:00.0
PCI-DMA: Out of SW-IOMMU space for 16383 bytes at device 0000:01:00.0
PCI-DMA: Out of SW-IOMMU space for 16383 bytes at device 0000:01:00.0
PCI-DMA: Out of SW-IOMMU space for 16383 bytes at device 0000:01:00.0
PCI-DMA: Out of SW-IOMMU space for 16383 bytes at device 0000:01:00.0
PCI-DMA: Out of SW-IOMMU space for 16383 bytes at device 0000:01:00.0
PCI-DMA: Out of SW-IOMMU space for 16383 bytes at device 0000:01:00.0
PCI-DMA: Out of SW-IOMMU space for 16383 bytes at device 0000:01:00.0
PCI-DMA: Out of SW-IOMMU space for 16383 bytes at device 0000:01:00.0
r8169: eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
SELinux: initialized (dev rpc_pipefs, type rpc_pipefs), uses genfs_contexts
Bluetooth: Core ver 2.10
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
Bluetooth: HIDP (Human Interface Emulation) ver 1.1
SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
SELinux: initialized (dev autofs, type autofs), uses genfs_contexts
Bridge firewalling registered
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
device vif0.0 entered promiscuous mode
xenbr0: topology change detected, propagating
xenbr0: port 1(vif0.0) entering forwarding state
r8169: peth0: link down
ADDRCONF(NETDEV_UP): peth0: link is not ready
virbr0: no IPv6 routers present
device peth0 entered promiscuous mode
eth0: no IPv6 routers present
[drm] Initialized drm 1.0.1 20051102
ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 20
[drm] Initialized i915 1.8.0 20060929 on minor 0
usb 1-8: new high speed USB device using ehci_hcd and address 2
usb 1-8: configuration #1 chosen from 1 choice
Initializing USB Mass Storage driver...
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
  Vendor: HSPA USB  Model: SCSI CD-ROM       Rev: 6229
  Type:   CD-ROM                             ANSI SCSI revision: 00
scsi 2:0:0:0: Attached scsi generic sg1 type 5
usb-storage: device scan complete
sr0: scsi3-mmc drive: 0x/0x caddy
sr 2:0:0:0: Attached scsi CD-ROM sr0

[root@localhost nishil]#

qlue · 12-13-2014, 02:57 PM

Quote:

Originally Posted by nishil032

[root@localhost nishil]# /sbin/lsusb

Bus 005 Device 001: ID 0000:0000

Bus 002 Device 001: ID 0000:0000

Bus 003 Device 001: ID 0000:0000

Bus 001 Device 002: ID 2001:a80b D-Link Corp. [hex] ###This is my Device

Bus 001 Device 001: ID 0000:0000

Bus 004 Device 001: ID 0000:0000

For dmesg it seems such a big output:::

usb 1-8: new high speed USB device using ehci_hcd and address 2
usb 1-8: configuration #1 chosen from 1 choice
Initializing USB Mass Storage driver...
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
Vendor: HSPA USB Model: SCSI CD-ROM Rev: 6229
Type: CD-ROM ANSI SCSI revision: 00
scsi 2:0:0:0: Attached scsi generic sg1 type 5
usb-storage: device scan complete
sr0: scsi3-mmc drive: 0x/0x caddy
sr 2:0:0:0: Attached scsi CD-ROM sr0

[root@localhost nishil]#

Based on this last part of dmesg It looks like the device is registering as a fake cd-rom. This is normal, however, most devices are switched automatically using usb-modeswitch.

In my experience it is merely needed to eject the fake cd-rom. Try;

Code:

eject /dev/sr0

I have also found that most modern hybrid devices will automatically start in modem mode if they are plugged in before you boot up.

This also seems to work better for getting the kernel to register the correct modules etc. on boot-up.

When the device switches, the product number shown in lsusb will change and the new product number should, hopefully, be recognised as a modem.

Try this and let us know what happens. (post the new lsusb output if the numbers change please)

nishil032 · 12-13-2014, 09:38 PM

I've connected the device before the system boot up but seems like no change of action
I ran lsusb command:

[root@localhost nishil]# /sbin/lsusb
Bus 001 Device 001: ID 0000:0000
Bus 001 Device 002: ID 2001:a80b D-Link Corp. [hex]
Bus 003 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000

the numbers remain same

result of eject /dev/sr0 :

[root@localhost nishil]# eject /dev/sr0
eject: unable to find or open device for: `/dev/sr0'
[root@localhost nishil]#

unSpawn · 12-14-2014, 02:41 AM

To elaborate on the first reply given: CentOS is an Enterprise-ready Linux distribution. Its aim is to provide secure, stable services, not "bleeding edge" versions of the kernel and user land. So you likely will require a more recent version of kernel, drivers and usb_modeswitch than CentOS 5 offers. You could try Fedora 20 (21 soon) or any other recent release of a Linux distribution of choice. *You could try and see if a Live CD version would pick up the device before committing to installing it.

John VV · 12-14-2014, 03:04 AM

i would use a newer OS

CentOS 5.0 came out in April of 2007

it will have NO support for hardware made in the last 7 years

now
if this is the Current ( legacy hardware Support) cent 5 CentOS 5.11
it ??? might have some support for newish hardware
--- do to the normal updates

But CentOS LOCKED the software versions back in 2007 for Cent5
and it will STILL have the same major version of software in 2017 when it goes end of life

about 8 months ago ACTIVE support for cent5 ENDED!!!!!
only maintenance and security fixes from now on
-- so in 2017 CentOS5 will be running 10 year old software when it goes end of life

If you REALLY MUST!!! install Cent
install the current CentOS 6.6 or CentOS 7.0

but you might still have issues with wireless dongles

unSpawn · 12-14-2014, 04:23 AM

Quote:

but you might still have issues with wireless dongles

@OP: let me translate that for you. Unless the RHEL HCL shows you the device works OK go for Fedora 20 (21 soon) or any other recent release of a non-Enterprise Linux distribution of choice.

nishil032 · 12-14-2014, 08:25 AM

So rather than going for up-gradation or change of OS don't I have any option to continue with my existing system to work the device...????

unSpawn · 12-14-2014, 10:28 AM

Linux is about freedom and that also means the freedom to read the relevant documentation, diagnose, tinker with and break things. So by all means go right ahead!

John VV · 12-14-2014, 02:41 PM

Do not get me wrong
i like RHEL/CentOS/SL
the OS's are G R E A T !!!
for the intended use

-- that is the cravat

however for using with very NEW hardware , that use is outside the normal average intended use

1)
the server ( all )
2)
the laboratory ( SL and Fermi linux )
3)
The OFFICE ( rhel and cent )

while some usb wireless dongles do work
the OS was not intended to use them

then add to this you are using a legacy hardware support CentOS5
we still do not know if it is the current CentOS 5.11
or the very OLD centOS 5.0

now CentOS 5 is fine for a older intel dual core and 1 gig ram
it will have MORE support for computers with pentium 3 and 4 cpu's

CentOS 6 would be a bit better for the slightly newer intel dual core ( frpm 2005 )
but
to get that to work with a usb dongle that was DESIGNED AFTER!!! centOS 5's software was LOCKED

while can be done

it might be rather hard to do

nishil032 · 12-15-2014, 07:39 AM

Here is my pc spec:

Intel Pentium Dual Core 2GHz,1GB RAM,160 GB HDD,Dual Boot with WIndows 7 and Cent OS version 5.5,32bit pc

ondoho · 12-20-2014, 10:25 AM

nishil032, it is 100% possible to get your dongle working under centos. however it might require fairly complicated steps.

i am pretty sure that your dongle will Just Work with sth like ubuntu or linux mint; so it's up to you to decide what is less hassle:
- many hours of frustration with the command line
- an hour of backing up your data and installing a more suitable system.