Page 1 of 7 123 ... LastLast
Results 1 to 10 of 63

Thread: Wireless Woes in Hardy 8.04

  1. #1
    Join Date
    Jun 2008
    Beans
    60

    Wireless Woes in Hardy 8.04

    Hi, I'm having trouble getting Ubuntu to recognize wireless cards on my laptop (Sony VAIO PCG-9G1L). I have tried several cards (Netgear WPN111, Microsoft Wireless Notebook Adapter MN-520, and Dynex DX-E201) without Ubuntu recognizing them. I would prefer to use the Dynex card, but my main priority is getting online.

    Is there a straightforward way to set up my wireless card in Ubuntu? I have browsed blogs, forums, and official documentation, but all I have found is a jumble of suggestions to install packets, drivers, and enter various command-prompt operations. I've attempted to follow all the relevant instructions without success.

    My network connections icon says "No network connections", and no connections appear under Network Settings (System > Administration > Network).

    I installed ndiswrapper on my system to no avail: My Dynex installation CD includes a folder entitled "LINUX" which contains a document "dxe201.c" written in C that is supposed to be the driver for the wireless card, but ndiswrapper (presumably System > Administration > Windows Wireless Drivers) wants an .inf file. When I tell the C file to run on its own, nothing happens. There is no useful help information on the Dynex CD or on their website. Someone had a similar problem in this thread, but the suggestions didn't work. According to pytheas22, my Dynex card has an rtl8129 chipset (whatever that means!).

    Below are the results of the lsmod, ifconfig, and iwconfig commands. I'm not sure if my card is recognized to begin with.

    Code:
    taylor@taylor-laptop:~$ lsmod
    Module                  Size  Used by
    isofs                  36388  1 
    udf                    88612  0 
    nls_iso8859_1           4992  1 
    nls_cp437               6656  1 
    vfat                   14464  1 
    fat                    54556  1 vfat
    usb_storage            73664  1 
    usbhid                 31872  0 
    libusual               19108  1 usb_storage
    hid                    38784  1 usbhid
    ipv6                  267780  8 
    rfcomm                 41744  2 
    l2cap                  25728  13 rfcomm
    bluetooth              61156  4 rfcomm,l2cap
    sony_laptop            35292  0 
    sonypi                 23192  0 
    ppdev                  10372  0 
    powernow_k7             9000  0 
    cpufreq_ondemand        9740  1 
    cpufreq_powersave       2688  0 
    cpufreq_stats           7104  0 
    cpufreq_conservative     8712  0 
    cpufreq_userspace       5284  0 
    freq_table              5536  3 powernow_k7,cpufreq_ondemand,cpufreq_stats
    container               5632  0 
    sbs                    15112  0 
    sbshc                   7680  1 sbs
    dock                   11280  0 
    iptable_filter          3840  0 
    ip_tables              14820  1 iptable_filter
    x_tables               16132  1 ip_tables
    sbp2                   24072  0 
    lp                     12324  0 
    joydev                 13120  0 
    pcmcia                 40876  0 
    snd_via82xx            29464  3 
    gameport               16008  1 snd_via82xx
    snd_via82xx_modem      16264  0 
    snd_ac97_codec        101028  2 snd_via82xx,snd_via82xx_modem
    ac97_bus                3072  1 snd_ac97_codec
    evdev                  13056  6 
    snd_pcm_oss            42144  0 
    snd_mixer_oss          17920  1 snd_pcm_oss
    snd_pcm                78596  4 snd_via82xx,snd_via82xx_modem,snd_ac97_codec,snd_pcm_oss
    snd_mpu401_uart         9728  1 snd_via82xx
    serio_raw               7940  0 
    psmouse                40336  0 
    video                  19856  0 
    output                  4736  1 video
    snd_seq_dummy           4868  0 
    snd_seq_oss            35584  0 
    snd_seq_midi            9376  0 
    snd_rawmidi            25760  2 snd_mpu401_uart,snd_seq_midi
    pcspkr                  4224  0 
    snd_seq_midi_event      8320  2 snd_seq_oss,snd_seq_midi
    snd_seq                54224  6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
    battery                14212  0 
    snd_timer              24836  2 snd_pcm,snd_seq
    snd_seq_device          9612  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
    ac                      6916  0 
    button                  9232  0 
    snd                    56996  19 snd_via82xx,snd_via82xx_modem,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_mpu401_uart,snd_seq_dummy,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
    yenta_socket           27276  2 
    snd_page_alloc         11400  3 snd_via82xx,snd_via82xx_modem,snd_pcm
    rsrc_nonstatic         13696  1 yenta_socket
    pcmcia_core            40596  3 pcmcia,yenta_socket,rsrc_nonstatic
    i2c_viapro              9876  0 
    soundcore               8800  1 snd
    i2c_core               24832  1 i2c_viapro
    via686a                15244  0 
    shpchp                 34452  0 
    pci_hotplug            30880  1 shpchp
    via_agp                11136  1 
    agpgart                34760  1 via_agp
    parport_pc             36260  1 
    parport                37832  3 ppdev,lp,parport_pc
    ext3                  136712  1 
    jbd                    48404  1 ext3
    mbcache                 9600  1 ext3
    sg                     36880  0 
    sr_mod                 17956  1 
    cdrom                  37408  1 sr_mod
    sd_mod                 30720  5 
    8139too                27520  0 
    floppy                 59588  0 
    ohci1394               33584  0 
    8139cp                 24704  0 
    mii                     6400  2 8139too,8139cp
    uhci_hcd               27024  0 
    pata_via               13316  3 
    ata_generic             8324  0 
    pata_acpi               8320  0 
    ieee1394               93752  2 sbp2,ohci1394
    usbcore               146028  5 usb_storage,usbhid,libusual,uhci_hcd
    libata                159344  3 pata_via,ata_generic,pata_acpi
    scsi_mod              151436  6 usb_storage,sbp2,sg,sr_mod,sd_mod,libata
    thermal                16796  0 
    processor              36872  3 powernow_k7,thermal
    fan                     5636  0 
    fbcon                  42912  0 
    tileblit                3456  1 fbcon
    font                    9472  1 fbcon
    bitblit                 6784  1 fbcon
    softcursor              3072  1 bitblit
    fuse                   50580  5
    Code:
    taylor@taylor-laptop:~$ ifconfig
    eth0      Link encap:Ethernet  HWaddr 08:00:46:6f:7d:1d  
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
              Interrupt:10 Base address:0x1800 
    
    lo        Link encap:Local Loopback  
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:4378 errors:0 dropped:0 overruns:0 frame:0
              TX packets:4378 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0 
              RX bytes:219148 (214.0 KB)  TX bytes:219148 (214.0 KB)
    Code:
    taylor@taylor-laptop:~$ iwconfig
    lo        no wireless extensions.
    
    eth0      no wireless extensions.
    I tried the command-line suggestions in the thread I linked to above; here are the commands that returned anything at all:
    Code:
    taylor@taylor-laptop:~$ sudo ifconfig eth0 up
    eth0: ERROR while getting interface flags: No such device
    
    taylor@taylor-laptop:~$ mii-tool -F 10baseT-HD
    no MII interfaces found
    
    taylor@taylor-laptop:~$ mii-tool -R
    no MII interfaces found
    I presume that means Ubuntu doesn't know the card exists at all? Any help would be appreciated. I'm using a portable hard drive to shuttle information from my desktop computer (online) to my laptop (offline) on which I'm running my Ubuntu experiment.

    Any help would be appreciated. Thanks in advance!

    May all beings be well and happy!~

  2. #2
    Join Date
    Aug 2007
    Location
    Paris
    Beans
    5,538
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Wireless Woes in Hardy 8.04

    Incidentally I just happened upon your post while looking through the unanswered list (I am in the thread you link to above).

    Let's first make sure that the interface definitely isn't being recognized by the system at all. If you type:
    Code:
    iconfig -a
    do you see anything besides an entry for 'lo?' I realize it's hard for you to copy and paste (since you don't have an Internet connection) so I won't ask you to do that, but let me know if there's anything there other than a block of text that looks similar to:

    Code:
    lo        Link encap:Local Loopback  
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:2150 errors:0 dropped:0 overruns:0 frame:0
              TX packets:2150 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0 
              RX bytes:112861 (110.2 KB)  TX bytes:112861 (110.2 KB)
    If you don't see anything besides lo, please try running:

    Code:
    sudo rmmod 8139cp
    sudo modprobe 8139too
    and then look at ifconfig again. Anything else there?

    If not, try:
    Code:
    sudo rmmod 8139too
    sudo modprobe 8139cp
    and please look again.

    If none of the stuff above yields anything interesting, then the next thing to do I think is to look at dmesg. Run:
    Code:
    dmesg | grep -e eth -e rlt
    and please copy the output here. If the output is too much to type, you can pipe it into a text file by adding a > to the command, e.g.:

    Code:
    dmesg | grep -e eth -e rlt > ~/Desktop/output.txt
    would cause the output from dmesg to be dumped to a file on your desktop called 'output.txt.' Then you could copy it onto a USB stick and bring it to a machine where you have Internet access and copy and paste on there into this thread.

    Please try these things and post your results. As I wrote in the first thread, I really don't think it's necessary to have to compile the source code that you have on your CD. I think it's just a matter of figuring out why the driver won't recognize your card, which shouldn't be too hard really.

    Also, which version of *Ubuntu are you using?

  3. #3
    Join Date
    Aug 2007
    Location
    Paris
    Beans
    5,538
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Wireless Woes in Hardy 8.04

    After reading your post more thoroughly, I have some more questions. I didn't realize that your goal is to get wireless.

    First, isn't the Dynex card just an ethernet (wired) interface, not wireless? I don't own one but that was the impression I got from helping the user in the other thread. Also from your iwconfig output, it looks like the Dynex card is recognized as an ethernet interface and should work if you plug a cable into it.

    Second, if you plug in all three of your wireless devices and run these commands:
    Code:
    lspci > ~/Desktop/lspci.txt
    lsusb > ~/Desktop/lsusb.txt
    and copy the text files that they create on your Desktop onto your Windows machine so that you can post them here, it would be helpful. This will display the chipsets of the devices, and with that information it shouldn't be hard to figure out what you need to do to make them work.

    Also, to answer your question about a straightforward way to set up wireless: unfortunately, if your card doesn't just work out of the box (as many do, depending on how friendly their manufacturers are towards Linux/open-source), then no, there's really not a simple way to configure it. There are lots of different kinds of drivers and the procedures for each is different. But once you figure out which driver you need (which is the point of seeing the lspci and lsusb output), it's usually not hard to find instructions on how to configure it.

  4. #4
    Join Date
    Jun 2008
    Beans
    60

    Re: Wireless Woes in Hardy 8.04

    Hmm, well it would make it hard to find information on how to get wireless on my Dynex card if it isn't a wireless card!

    That was the problem with Dynex.

    Now trying the Microsoft card...

    Recall that it is a Microsoft Wireless Notebook Adapter MN-520.

    ifconfig:
    Code:
    lo        Link encap:Local Loopback  
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:3200 errors:0 dropped:0 overruns:0 frame:0
              TX packets:3200 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0 
              RX bytes:160000 (156.2 KB)  TX bytes:160000 (156.2 KB)
    iwconfig: no output

    lsmod:
    Code:
    Module                  Size  Used by
    isofs                  36388  1 
    udf                    88612  0 
    ipv6                  267780  8 
    rfcomm                 41744  2 
    l2cap                  25728  13 rfcomm
    bluetooth              61156  4 rfcomm,l2cap
    sony_laptop            35292  0 
    sonypi                 23192  0 
    ppdev                  10372  0 
    powernow_k7             9000  0 
    cpufreq_ondemand        9740  1 
    cpufreq_powersave       2688  0 
    cpufreq_stats           7104  0 
    cpufreq_conservative     8712  0 
    cpufreq_userspace       5284  0 
    freq_table              5536  3 powernow_k7,cpufreq_ondemand,cpufreq_stats
    container               5632  0 
    sbs                    15112  0 
    sbshc                   7680  1 sbs
    dock                   11280  0 
    iptable_filter          3840  0 
    ip_tables              14820  1 iptable_filter
    x_tables               16132  1 ip_tables
    sbp2                   24072  0 
    lp                     12324  0 
    joydev                 13120  0 
    pcmcia                 40876  0 
    snd_via82xx            29464  3 
    gameport               16008  1 snd_via82xx
    evdev                  13056  6 
    snd_via82xx_modem      16264  0 
    snd_ac97_codec        101028  2 snd_via82xx,snd_via82xx_modem
    ac97_bus                3072  1 snd_ac97_codec
    snd_pcm_oss            42144  0 
    snd_mixer_oss          17920  1 snd_pcm_oss
    serio_raw               7940  0 
    snd_pcm                78596  4 snd_via82xx,snd_via82xx_modem,snd_ac97_codec,snd_pcm_oss
    snd_mpu401_uart         9728  1 snd_via82xx
    psmouse                40336  0 
    video                  19856  0 
    output                  4736  1 video
    snd_seq_dummy           4868  0 
    snd_seq_oss            35584  0 
    snd_seq_midi            9376  0 
    pcspkr                  4224  0 
    snd_rawmidi            25760  2 snd_mpu401_uart,snd_seq_midi
    snd_seq_midi_event      8320  2 snd_seq_oss,snd_seq_midi
    snd_seq                54224  6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
    battery                14212  0 
    ac                      6916  0 
    snd_timer              24836  2 snd_pcm,snd_seq
    snd_seq_device          9612  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
    button                  9232  0 
    snd                    56996  19 snd_via82xx,snd_via82xx_modem,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_mpu401_uart,snd_seq_dummy,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
    yenta_socket           27276  2 
    rsrc_nonstatic         13696  1 yenta_socket
    snd_page_alloc         11400  3 snd_via82xx,snd_via82xx_modem,snd_pcm
    pcmcia_core            40596  3 pcmcia,yenta_socket,rsrc_nonstatic
    soundcore               8800  1 snd
    i2c_viapro              9876  0 
    i2c_core               24832  1 i2c_viapro
    via686a                15244  0 
    shpchp                 34452  0 
    pci_hotplug            30880  1 shpchp
    via_agp                11136  1 
    agpgart                34760  1 via_agp
    parport_pc             36260  1 
    parport                37832  3 ppdev,lp,parport_pc
    ext3                  136712  1 
    jbd                    48404  1 ext3
    mbcache                 9600  1 ext3
    sg                     36880  0 
    sr_mod                 17956  1 
    cdrom                  37408  1 sr_mod
    sd_mod                 30720  3 
    floppy                 59588  0 
    ohci1394               33584  0 
    8139cp                 24704  0 
    mii                     6400  1 8139cp
    uhci_hcd               27024  0 
    pata_via               13316  3 
    ata_generic             8324  0 
    pata_acpi               8320  0 
    ieee1394               93752  2 sbp2,ohci1394
    usbcore               146028  2 uhci_hcd
    libata                159344  3 pata_via,ata_generic,pata_acpi
    scsi_mod              151436  5 sbp2,sg,sr_mod,sd_mod,libata
    thermal                16796  0 
    processor              36872  3 powernow_k7,thermal
    fan                     5636  0 
    fbcon                  42912  0 
    tileblit                3456  1 fbcon
    font                    9472  1 fbcon
    bitblit                 6784  1 fbcon
    softcursor              3072  1 bitblit
    fuse                   50580  3
    lspci (with only the Microsoft card inserted):
    Code:
    00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03)
    00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
    00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
    00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
    00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a)
    00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a)
    00:07.4 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
    00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 50)
    00:07.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 30)
    00:0a.0 CardBus bridge: Texas Instruments PCI1420 PC card Cardbus Controller
    00:0a.1 CardBus bridge: Texas Instruments PCI1420 PC card Cardbus Controller
    00:0e.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394 Controller (Link)
    00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
    01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64)
    According to this post at AMDZone.com, the MN-520 card is supported by Linux, and binds the orinoco_cs (again, whatever that means!). The card is supposed to work out of the box

    Following the example in another thread (for I don't really know what I'm doing, if you haven't figured it out already!), I edited the file /etc/pcmcia/config.opts to include these lines:
    Code:
    card "Microsoft Wireless Notebook Adapter MN-520 1.0.3"
    version "Microsoft", "Wireless Notebook Adapter MN-520", "", "1.0.3"
    bind "orinoco_cs"
    I restarted Ubuntu, but the Microsoft card still doesn't appear to be recognized. Neither the "Wireless" nor the "Power" light is on or blinking. There's nothing new in "Network Settings".

    Thanks~!

  5. #5
    Join Date
    Jul 2006
    Location
    Castrum, Germania Secunda
    Beans
    1,071

    Re: Wireless Woes in Hardy 8.04

    Tips, tweaks and how-to's for Ubuntu and Mint:
    http://sites.google.com/site/easylinuxtipsproject
    In for a pleasant surprise? Give Xubuntu a try:
    http://sites.google.com/site/easylin...roject/xubuntu

  6. #6
    Join Date
    Aug 2007
    Location
    Paris
    Beans
    5,538
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Wireless Woes in Hardy 8.04

    From what I can tell from other threads, the Microsoft card should just work, and it if it doesn't, editing /etc/pcmcia/config.opts as you did should solve the problem. So the only advice I have for that is first to make sure that the card is definitely firmly in the pcmcia slot (you'd be surprised how many problems come down to stuff like this). I don't see your card being detected by lspci so I wonder if it's really in place.

    If you're sure that it is, then I'd look at dmesg output to see why the card isn't being brought up. In other words, what does:
    Code:
    dmesg | grep -e eth -e wlan
    tell you?

    Or if you want to give it a shot with your third card instead of this Microsoft one, please post the lspci and ifconfig -a information after you've inserted that

  7. #7
    Join Date
    Jan 2008
    Beans
    43

    Re: Wireless Woes in Hardy 8.04 - ndiswrapper

    A note on ndiswrapper: You need ndiswrapper only if your wireless card isn't supported, or properly supported, natively in Linux. If you do need it, what it needs is the Windows driver for your card, not a Linux driver. You'll find this on the CD that came with the card.

    ndiswrapper has both a kernel module and a run-time binary for configuring the kernel module. Browse the CD that came with the card and find the directory containing the Windows driver for it. You'll see a .inf file there, as well as a .sys file, possibly some .hlp files and others as well. The .inf file is the one you want. Then execute:

    Code:
    ndiswrapper -i /full/path/to/the/inf/file [... so to speak]
    ndiswrapper will read and stash the .inf file and the .sys file which is referenced in the .inf file, and thereafter it should just work. If you're using a laptop, make sure you have wireless turned on from your keyboard.

    BTW, Linux drivers that come with proprietary hardware in the form of C files are often pretty lame. Compiling them isn't hard - usually there's a README or INSTALL for them somewhere - but compiles often fail based on the kernel version, and even if they compile they won't install or work. Many proprietary hardware makers don't give a rat's behinder about Linux, and they throw on a C file just so they can say they support Linux, but don't keep up with whether or not it works in current versions of the kernel.

  8. #8
    Join Date
    Jun 2008
    Beans
    60

    Re: Wireless Woes in Hardy 8.04

    I checked the Microsoft card and it wasn't firmly in place. Now it is, but the "Wireless" and "Power" lights still aren't blinking, even after restarting the computer. There is nothing new in "Network Settings".

    ifconfig (eth0 is new):
    Code:
    eth0      Link encap:Ethernet  HWaddr 08:00:46:6f:7d:1d  
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
              Interrupt:10 Base address:0x1800 
    
    lo        Link encap:Local Loopback  
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:2956 errors:0 dropped:0 overruns:0 frame:0
              TX packets:2956 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0 
              RX bytes:147876 (144.4 KB)  TX bytes:147876 (144.4 KB)
    lspci (nothing new here):
    Code:
    00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03)
    00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
    00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
    00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
    00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a)
    00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a)
    00:07.4 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
    00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 50)
    00:07.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 30)
    00:0a.0 CardBus bridge: Texas Instruments PCI1420 PC card Cardbus Controller
    00:0a.1 CardBus bridge: Texas Instruments PCI1420 PC card Cardbus Controller
    00:0e.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394 Controller (Link)
    00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
    01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64)
    dmesg (the same, whether card is in or not):
    Code:
    [  208.874581] eth0: RealTek RTL8139 at 0x1800, 08:00:46:6f:7d:1d, IRQ 10
    [  208.874585] eth0:  Identified 8139 chip type 'RTL-8139C'
    [  209.488134] Driver 'sd' needs updating - please use bus_type methods
    [  209.488515]  sda:<4>Driver 'sr' needs updating - please use bus_type methods
    [  336.193334] eth0: link down
    [  707.391315] ADDRCONF(NETDEV_UP): eth0: link is not ready
    It appears that there is no power going to the card, or that it is not recognized... but it worked when Windows XP was installed on the laptop.

  9. #9
    Join Date
    Jun 2008
    Beans
    60

    Re: Wireless Woes in Hardy 8.04

    This may be irrelevant, but before I installed Ubuntu I ran Darik's Boot and Nuke (Hard Drive Disk Wipe). Could that've messed something up?

  10. #10
    Join Date
    Aug 2007
    Location
    Paris
    Beans
    5,538
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Wireless Woes in Hardy 8.04

    Was the Dynex card inserted when you were gathering the output for your last post? Because I see an ethernet card (eth0) but still no wireless device, even in the output of lspci. If the Dynex card wasn't in the machine, are you sure that the device that was inserted is a wireless card? I know it has wireless in its name, but maybe you're confusing it with another device or something? If the Dynex card was in the computer, though, then that explains it all...

    But please let me know.

    Also is there any way you can test the device in a Windows machine just to make sure it still works?

Page 1 of 7 123 ... LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •