[Ubuntu Chicago] ubuntu wireless

Tue Aug 28 04:08:36 BST 2007

I deleted the rt73usb line.

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

fuse
lp
rt2500

On 8/27/07, Wally Valters <deepsky99 at gmail.com> wrote:
>
> blow away the line with blacklist rt73usb
>
> still need /etc/modules as that was touched by that script as well
>
> On 8/27/07, jason jenkins < jenkins27 at gmail.com> wrote:
> >
> > # This file lists those modules which we don't want to be loaded by
> > # alias expansion, usually so some other driver will be loaded for the
> > # device instead.
> >
> >
> > # evbug is a debug tool that should be loaded explicitly
> > blacklist evbug
> >
> > # these drivers are very simple, the HID drivers are usually preferred
> > blacklist usbmouse
> > blacklist usbkbd
> >
> > # replaced by e100
> > blacklist eepro100
> >
> > # replaced by tulip
> > blacklist de4x5
> > #causes no end of confusion by creating unexpected network interfaces
> > blacklist eth1394
> >
> > # snd_intel8x0m can interfere with snd_intel8x0, doesn't seem to support
> > much
> > # hardware on its own (Ubuntu bug #2011, #6810)
> > blacklist snd_intel8x0m
> >
> > # causes failure to suspend on HP compaq nc6000 (Ubuntu: #10306)
> > blacklist i2c_i801
> >
> > # buggy driver causes kernel BUG on load (Ubuntu: #78255, #88430)
> > blacklist r818x
> > blacklist r8187
> > blacklist rt73usb
> >
> > On 8/27/07, jason jenkins < jenkins27 at gmail.com> wrote:
> > >
> > > sorry about that.  I will send the output info after work today.
> > >
> > > On 8/26/07, Wally Valters < deepsky99 at gmail.com > wrote:
> > > >
> > > > You need to read twice, type once.  I stated:
> > > > that SHOULD load up the driver (if his script actually did the rest
> > > > of its duties)
> > > > if it does, make it permanent:
> > > >
> > > > 6) in a terminal : echo 'rt2500' | sudo tee -a /etc/modules
> > > >
> > > > so since it did NOT work you should not have added rt2500 to
> > > > etc/modules by doing step 6.
> > > >
> > > > Put the output of the /etc/modprobe.d/blacklist file here (inline
> > > > please, not attached) as well as the /etc/modules.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On 8/25/07, jason jenkins <jenkins27 at gmail.com> wrote:
> > > > >
> > > > > OK, didnt seem to work.  I did gksudo gedit /etc/modprobe.d/blacklist
> > > > > and deleted the blacklist rt2500 line and rebooted and there was no
> > > > > difference.  the I did 4) in a terminal type "sudo depmod -a" & 5)
> > > > > in a terminal type "sudo modprobe rt2500" and lastly 6) in a terminal : echo
> > > > > 'rt2500' | sudo tee -a /etc/modules.  There was no change.
> > > > >
> > > > > Once the wireless is working I am sure much of the newbness will
> > > > > go away very quickly.  If I have working wireless with WPA then I can make
> > > > > ubuntu my daily OS and once I can do that I will really learn stuff quickly.
> > > > >
> > > > >
> > > > > On 8/25/07, Wally Valters < deepsky99 at gmail.com> wrote:
> > > > > >
> > > > > > hehe...
> > > > > > if you want graphical (like notepad only better) you can use
> > > > > > gedit.  since you are using reg ubuntu, and gnome the command would be :
> > > > > >
> > > > > > gksudo gedit /etc/modprobe.d/blacklist  etc...   the gksudo is
> > > > > > just a graphical prompt for your password like sudo is in the terminal.
> > > > > >
> > > > > > After we get wireless working we can try and eliminate some of
> > > > > > your "nubeness", although we are not miracle workers.
> > > > > >
> > > > > >
> > > > > > On 8/24/07, jason jenkins <jenkins27 at gmail.com> wrote:
> > > > > > >
> > > > > > > "( or instead of vim pick your favorite editor) "
> > > > > > > ROFL
> > > > > > > Perhaps you still underestimate my level of newbness with
> > > > > > > linux.  I have never heard of vim or any other editor that I may have
> > > > > > > installed in ubuntu.  Thanks assuming that I have some clue tho, that makes
> > > > > > > me feel better :)
> > > > > > > I will stick with vim and give it a shot later after work and
> > > > > > > let you know how it goes.
> > > > > > > Let me know if you find the guy who wrote the script and need
> > > > > > > help hanging him.
> > > > > > >
> > > > > > > On 8/24/07, Wally Valters <deepsky99 at gmail.com> wrote:
> > > > > > > >
> > > > > > > > Someone ought to hang the dude who wrote this script...
> > > > > > > > basically he blacklists his own driver...
> > > > > > > >
> > > > > > > > ok jason try this...
> > > > > > > >
> > > > > > > > 1) sudo vim /etc/modprobe.d/blacklist. ( or instead of vim
> > > > > > > > pick your favorite editor)
> > > > > > > > 2) remove any line that says:   blacklist rt2500
> > > > > > > > 3) save, reboot, see what happens
> > > > > > > >
> > > > > > > > you still may be without wifi, since your driver is probably
> > > > > > > > not loaded., as he never does a permanent change to the loaded modules
> > > > > > > >
> > > > > > > > 4) in a terminal type "sudo depmod -a"
> > > > > > > > 5) in a terminal type "sudo modprobe rt2500"
> > > > > > > >
> > > > > > > > that SHOULD load up the driver (if his script actually did
> > > > > > > > the rest of its duties)
> > > > > > > > if it does, make it permanent:
> > > > > > > >
> > > > > > > > 6) in a terminal : echo 'rt2500' | sudo tee -a /etc/modules
> > > > > > > > =============================================
> > > > > > > > If it works, you will have wireless, but you may not be able
> > > > > > > > to connect to a protected network, but thats the easy part.
> > > > > > > >
> > > > > > > >
> > > > > > > > On 8/24/07, Wally Valters < deepsky99 at gmail.com> wrote:
> > > > > > > > >
> > > > > > > > > I cant until Tuesday.  If no one else can before then we
> > > > > > > > > should be able to meet up somewhere.
> > > > > > > > >
> > > > > > > > > Brat stop would be ideal, you can feed me beer:)  But I
> > > > > > > > > don't think they have wireless.
> > > > > > > > >
> > > > > > > > > If you want to try remote connection, install ssh
> > > > > > > > > (probably is already) and let me know and we can set that up over the phone
> > > > > > > > > this weekend sometime.  Im not sure how much we can accomplish that way, but
> > > > > > > > > it may be worth a shot.
> > > > > > > > >
> > > > > > > > > btw what link did you get that auto script at that borked
> > > > > > > > > everything up?  Ill try and see if there is anything really wierd in there.
> > > > > > > > >
> > > > > > > > > it was in here (http://ubuntuforums.org/showthread.php?t=525833)
> > > > > > > > > correct?
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On 8/24/07, jason jenkins < jenkins27 at gmail.com > wrote:
> > > > > > > > > >
> > > > > > > > > > can anyone looks at it for me?
> > > > > > > > > >
> > > > > > > > > > On 8/24/07, Wally Valters <deepsky99 at gmail.com > wrote:
> > > > > > > > > > >
> > > > > > > > > > > When the manual process hit errors, you probably
> > > > > > > > > > > should have stopped there.  So unless you can identify what that script did,
> > > > > > > > > > > and reverse any negative affects, there isn't much I can do for you.
> > > > > > > > > > >
> > > > > > > > > > > Either wipe / re-install ubuntu, or get someone to
> > > > > > > > > > > look at the machine.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On 8/24/07, jason jenkins < jenkins27 at gmail.com>
> > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > there is no light.  the manual process error'd out.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On 8/24/07, Wally Valters <deepsky99 at gmail.com>
> > > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > Does it have a light?  When you boot ubuntu does
> > > > > > > > > > > > > the light come on?
> > > > > > > > > > > > >
> > > > > > > > > > > > > You are going to have to find out what that script
> > > > > > > > > > > > > you ran actually did.  That is the one reason I suggested manually doing the
> > > > > > > > > > > > > stuff, because you then have an exact backout procedure.
> > > > > > > > > > > > >
> > > > > > > > > > > > > On 8/23/07, jason jenkins < jenkins27 at gmail.com>
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > yes.  it works fine in windows.
> > > > > > > > > > > > > > Its fubar'd isn't it?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On 8/23/07, Wally Valters < deepsky99 at gmail.com> wrote:
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Is your wireless card turned on?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > On 8/23/07, jason jenkins <jenkins27 at gmail.com
> > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Here is the dmesg file.
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > On 8/23/07, Wally Valters <deepsky99 at gmail.com>
> > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > They will need some way to login, and some
> > > > > > > > > > > > > > > > > credentials to log in with...
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > What about that dmesg output?
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > On 8/22/07, jason jenkins <jenkins27 at gmail.com>
> > > > > > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > I have no idea how to do any of that.  I
> > > > > > > > > > > > > > > > > > was going to plug it right in to the modem so its not behind a firewall.
> > > > > > > > > > > > > > > > > > Shouldn't that be easy enough to hack like that?
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/ubuntu-us-chicago/attachments/20070827/301c257b/attachment.htm 