|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Wireless Questions about wireless networking setup, use, and wireless specific applications |
![]() |
|
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
went to yast, searched kernel-pae and it says deees
Code:
#### YaST2 conflicts list - generated 2009-05-19 13:13:07 ####
kernel-pae-2.6.27.21-0.1.2.i586 conflicts with libc.so.6()(64bit) provided by glibc-2.9-2.9.x86_64
[ ] do not install kernel-pae-2.6.27.21-0.1.2.i586
#### YaST2 conflicts list END ###
|
|
|||
|
jeez im an idiot. 586 is pentium isnt it.
|
|
|||
|
1) Webpin
2) Search for "broadcom-wl" 3) Read Choosing the correct kmp-package for your installation - openSUSE Forums (If you can connect to the internet via cable, run a conmplete online update first to get the latest kernel updates for 11.1)
__________________
“Never attribute to malice that which can be adequately explained by stupidity.” (R.J. Hanlon) |
|
|||
|
Quote:
|
|
|||
|
Can anybody, please, comment on the post #33 at
[all variants] Known Jaunty Wireless/Ethernet workarounds - Page 4 - Ubuntu Forums In my case it works until Code:
sudo ifup wlan0 Code:
Interface wlan0 is not available Code:
eth0 Link encap:Ethernet HWaddr 00:21:9B:D2:D8:8B
inet addr:85.222.121.60 Bcast:85.222.121.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:85730 errors:0 dropped:0 overruns:0 frame:0
TX packets:80152 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:70111276 (66.8 Mb) TX bytes:7976169 (7.6 Mb)
Interrupt:17
eth1 Link encap:Ethernet HWaddr 00:1F:E1:71:0F:E1
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:629
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:17 Base address:0xc000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:152 errors:0 dropped:0 overruns:0 frame:0
TX packets:152 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10616 (10.3 Kb) TX bytes:10616 (10.3 Kb)
Code:
lo no wireless extensions.
eth0 no wireless extensions.
pan0 no wireless extensions.
eth1 IEEE 802.11abgn ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:14 Mb/s Tx-Power:32 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Power Managementmode:All packets received
Link Quality=5/5 Signal level=0 dBm Noise level=-92 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
|
|
|||
|
On 10/19/2009 03:06 PM, gdzie wrote:
> > Can anybody, please, comment on the post #33 at > > '[all variants] Known Jaunty Wireless/Ethernet workarounds - Page 4 - > Ubuntu Forums' > (http://ubuntuforums.org/showthread.php?t=1176117&page=4) > > In my case it works until > > > Code: > -------------------- > > sudo ifup wlan0 > > -------------------- > > > when I get > > > Code: > -------------------- > > Interface wlan0 is not available > > -------------------- > > > Of course it is not, because "ifconfig" gives > > > Code: > -------------------- > > eth0 Link encap:Ethernet HWaddr 00:21:9B 2 8:8B> inet addr:85.222.121.60 Bcast:85.222.121.255 Mask:255.255.254.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:85730 errors:0 dropped:0 overruns:0 frame:0 > TX packets:80152 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:70111276 (66.8 Mb) TX bytes:7976169 (7.6 Mb) > Interrupt:17 > > eth1 Link encap:Ethernet HWaddr 00:1F:E1:71:0F:E1 > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:629 > 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:17 Base address:0xc000 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:152 errors:0 dropped:0 overruns:0 frame:0 > TX packets:152 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:10616 (10.3 Kb) TX bytes:10616 (10.3 Kb) > > -------------------- > > > and "iwconfig" gives > > > Code: > -------------------- > > lo no wireless extensions. > > eth0 no wireless extensions. > > pan0 no wireless extensions. > > eth1 IEEE 802.11abgn ESSID:"" > Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated > Bit Rate:14 Mb/s Tx-Power:32 dBm > Retry min limit:7 RTS thr ff Fragment thr ff> Power Managementmode:All packets received > Link Quality=5/5 Signal level=0 dBm Noise level=-92 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > -------------------- > > > Should I simply change "wlan0" to "eth1" in "ifup"? What do you think? Hint, the answer is yes as long as you are using the traditional ifup method. If you are using NetworkManager, which you should, then just add a new connection on eth1. You obviously did not read the stickies in this forum, or you would not have posted under the title that you used. Normally, I refuse to comment on such generic titles, particularly that one, which I specifically mentioned in the stickie! |
|
|||
|
You constantly go wrong by violating rules of netiquette and breaking forums rules you explicitly acknowledged on registration.
STOP crossposting! http://forums.opensuse.org/network-i...id-driver.html http://forums.opensuse.org/network-i...2-11b-g-2.html Only because you are the "helpless newbie" does _NOT_ mean you are the center of the world and have the right to waste volunteers' time by crossposting.
__________________
“Never attribute to malice that which can be adequately explained by stupidity.” (R.J. Hanlon) |
|
|||
|
Both lwfinger and Akoellh (and all others) please, accept the apologies for my misconduct. I 100% mean it. I appreciate your expertise and willing to help all of us out of our problems.
I finally managed to configure my wireless connection. However the device is recognized as "eth1" not "wlan0". Is it because of the hybrid driver? Once again, sorry for my misconduct at the forum and thank you for your guide through this 'non-working-wireless' obstacle. |
|
|||
|
On 10/20/2009 08:56 AM, gdzie wrote:
> > Both lwfinger and Akoellh (and all others) please, accept the apologies > for my misconduct. I 100% mean it. I appreciate your expertise and > willing to help all of us out of our problems. > > I finally managed to configure my wireless connection. However the > device is recognized as "eth1" not "wlan0". Is it because of the hybrid > driver? Device renaming is handled by udev. Check /etc/udev/rules.d/70-persistent-net.rules for a rule that renames wireless to eth1. |
|
|||
|
Quote:
|
![]() |
|
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|