Gentoo Archives: gentoo-user

From: Jeff Cranmer <jcranmer01@×××××××××.net>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] realtek 8197 wireless card setup
Date: Thu, 20 Dec 2007 03:23:36
Message-Id: 200712192214.36959.jcranmer01@earthlink.net
In Reply to: Re: [gentoo-user] realtek 8197 wireless card setup by Jeff Cranmer
1 Final piece of info for the day.
2
3 When I ran dhcpcd wlan0, I get
4 Error, wlan0: timed out
5 Error, wlan0: lease information file '/var/lib/dhcpcd/dhcpcd-wlan0.info' does
6 not exist
7
8 Any assistance gratefully received
9
10 Jeff
11
12
13 On Wednesday 19 December 2007 09:47:55 pm Jeff Cranmer wrote:
14 > I made significant progress today.
15 >
16 > I manually edited the file
17 > /usr/src/linux/drivers/net/wireless/rtl8187_dev.c
18 >
19 > There is a static structure near the top of the code,
20 >
21 > static struct usb_device_id rtl8187_table[] __devinitdata = {
22 > /* Realtek */
23 > {USB_DEVICE(0x0bda, 0x8187)},
24 > /* netgear */
25 > {USB_DEVICE(0x0846, 0x6100)},
26 > {USB_DEVICE(0x0846, 0x6a00)},
27 > {}
28 > };
29 >
30 > I added the line
31 > {USB_DEVICE(0x0bda, 0x8197)},
32 > in the /* Realtek */ area of the structure, then ran
33 > make clean, then
34 > make && make modules_install etc.
35 >
36 > After rebooting into the modified kernel, I now have iwmaster0 and iwlan0
37 > lines showing up when I type iwconfig.
38 >
39 > The applicable lines of iwconfig are
40 >
41 > wmaster0 no wireless extensions
42 >
43 > wlan0 IEEE 802.11g ESSID="mynetworkESSID"
44 > Mode:Managed Frequency=2.417GHz Access Point: Not associated
45 > Retry min limit 7 RTS thr:off Fragment thr=2346B
46 > Encryption key:<not telling you>
47 > Link Quality:0 Signal Level:0 Noise Level:0
48 > Rx Invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
49 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0
50 >
51 > I'm not all the way there yet, but this is significant progress.
52 >
53 > wpa_supplicant gui still is blank, with the message 'could not get status
54 > from WPA_supplicant', but at least now I have an interface showing up
55 >
56 > It appears that it cannot find an access point. The access point is
57 > active, as I can connect my work laptop to it, but so far, the laptop can't
58 > see it.
59 >
60 > Any further advice gratefully received.
61 >
62 > Jeff
63 >
64 > On Wednesday 19 December 2007 06:09:50 pm Jeff Cranmer wrote:
65 > > I've tried to run through the instructions at
66 > > http://gentoo-wiki.com/HARDWARE_rtl8187.
67 > >
68 > > The kernel is configured per that guide, and I get the message:
69 > > usbcore: registered new interface driver rtl8187
70 > >
71 > > When I try to run ifconfig wlan0 up, however, I get:
72 > > wlan0: unknown interface: no such device
73 > >
74 > > I get the same result if I run ifconfig wlan up (net.wlan is the symlink
75 > > that I set up in /etc/init.d)
76 > >
77 > > The wireless section of my /etc/conf.d/net file reads
78 > > mode_wlan="managed"
79 > > wpa_supplicant_wlan="-Dwext -c
80 > > /etc/wpa_supplicant/wpa_supplicant_RTL8187.conf" config_wlan=( "dhcp" )
81 > > dhcp_wlan="-R -G"
82 > >
83 > > wpa_supplicant has been emerged.
84 > >
85 > > Jeff
86 > >
87 > > On Sunday 16 December 2007 12:14:42 pm Mick wrote:
88 > > > On Sunday 16 December 2007, Jeff Cranmer wrote:
89 > > > > All I get for iwconfig is
90 > > > > lo no wireless extensions
91 > > > > eth0 no wireless extensions.
92 > > >
93 > > > This means that the driver has not been loaded yet. In generic terms
94 > > > you'll need to install the necessary driver for your WiFi device
95 > > > (either the new one in the kernel or emerge net-wireless/rtl8187, or
96 > > > ndiswrapper and the MS Windows driver). If you build the driver as a
97 > > > module then you need to modprobe -v rtl8187, while you keep an eye on
98 > > > the logs to see how things go (tail -f /var/log/messages). You have
99 > > > seen this, right?
100 > > >
101 > > > http://gentoo-wiki.com/HARDWARE_rtl8187
102 > > >
103 > > > > I think I need some more info in /etc/conf.d/net, and need somehow to
104 > > > > create the necessary /etc/init.d/net.wlan0 or whatever driver.
105 > > > >
106 > > > > The only 'net.anything' drivers present at the moment are net.lo and
107 > > > > net.eth0
108 > > >
109 > > > You will of course have to manually create a symlink between net.wlan0
110 > > > -> net.lo (or whatever your new WiFi device is recognised as by the
111 > > > kernel) so that you can bring it up by running /etc/init.d/net.wlan0
112 > > > start. But this is only necessary for autoloading the driver through
113 > > > the runlevel scripts. To try it out follow the instructions in the Wiki
114 > > > page above.
115 --
116 gentoo-user@g.o mailing list