The ralink modules in Suse 10.2 does not work! To make it work at least for the PCI cards (that is the only cards I have). You should do the following. Go to http://linux.wordpress.com/2006/05/14/suse-101-and-rt2500-wi-fi/ Read the instructions an do what it says. You will need the kernel source to make this work. You can stop after make install. Then go into Yast network card config, you should see the card there, select the card and click on edit, click on advanced and hardware details and change the name to rt2500 After that you can cofigure the card normally and it will work. this is not the only thing in 10.2 that does not work but one step at a time. Regards /Lennart -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
You can stop after make install.
Then go into Yast network card config, you should see the card there, select the card and click on edit, click on advanced and hardware details and change the name to rt2500
This is not required. Each module has a list of PCI/USB/etc. IDs it supports. In fact, if I both have rt2500 and rt2500pci in /lib/modules, udev happily loads both of them and I am to guess which one is in use. -`J' -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 14 December 2006 14:19, Jan Engelhardt wrote:
You can stop after make install.
Then go into Yast network card config, you should see the card there, select the card and click on edit, click on advanced and hardware details and change the name to rt2500
This is not required. Each module has a list of PCI/USB/etc. IDs it supports. In fact, if I both have rt2500 and rt2500pci in /lib/modules, udev happily loads both of them and I am to guess which one is in use.
-`J' Lennart Jan
Before I read your posts I had started another thread Railink rt2500 10.2, its probaby easier to continue here. I followed Lennarts suggestion which was what I was used to doing in 10.1 and although I can select the rt2500 module in Yast it will not connect. Jan, I am not sure what you mean, but I can select either in Knetworkmanager, and in neither case will it retain the settings after I have entered the WEP key. If either of you or anybody else have managed to get the card to connect I'd love to know exactly how you have done it. Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Dec 14 2006 17:28, michael norman wrote:
On Thursday 14 December 2006 14:19, Jan Engelhardt wrote:
You can stop after make install.
Then go into Yast network card config, you should see the card there, select the card and click on edit, click on advanced and hardware details and change the name to rt2500
This is not required. Each module has a list of PCI/USB/etc. IDs it supports. In fact, if I both have rt2500 and rt2500pci in /lib/modules, udev happily loads both of them and I am to guess which one is in use.
I am not sure what you mean, but I can select either in Knetworkmanager, and in neither case will it retain the settings after I have entered the WEP key.
I was talking at a level below yast, where there is only modprobe, so I might messed that up. -`J' -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 14 December 2006 17:50, Jan Engelhardt wrote:
On Dec 14 2006 17:28, michael norman wrote:
On Thursday 14 December 2006 14:19, Jan Engelhardt wrote:
You can stop after make install.
Then go into Yast network card config, you should see the card there, select the card and click on edit, click on advanced and hardware details and change the name to rt2500
This is not required. Each module has a list of PCI/USB/etc. IDs it supports. In fact, if I both have rt2500 and rt2500pci in /lib/modules, udev happily loads both of them and I am to guess which one is in use.
I am not sure what you mean, but I can select either in Knetworkmanager, and in neither case will it retain the settings after I have entered the WEP key.
I was talking at a level below yast, where there is only modprobe, so I might messed that up.
But have you got the card working, and if so, what exactly did you do ?
-- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I was talking at a level below yast, where there is only modprobe, so I might messed that up.
But have you got the card working, and if so, what exactly did you do ?
In short: I have a kernel patchset that adds rt2400, rt2500, and others to the tree (so I have everything in once place - compiling a ton of out-of-tree modules is just no fun). Then I compiled that tree and wrapped it up in rpms called kernel-XYZ-2.6.18.5-jen40b.i586.rpm for example (SUSE-compliant). So I did not really do something special besides taking rt2500-1.1.0-b4 (more precisely: CVS snapshot) and compiling it. [ rt2x00 CVS (aka rt2500pci aka rt2x00-2.0...) did not worked for me for long time and I don't use it atm. I anyway only get 5 mbit/s from most wireless APs instead of 11 (some fluke number like Ethernet has?) so I don't think rt2x00 supporting 54 would help me. But even if, I'd rather want a stable driver. ] -`J' -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
The rt2500pci module does not work, the module that works is named only as rt2500. the modules that comes with suse is rt2500pci.ko and rt2500usb.ko they does not work, the module that works is the module created by your compilation rt2500.ko /lib/modules/2.6.18.2-34-default/extra/rt2500.ko ....... works /lib/modules/2.6.18.2-34-default/updates/rt2500pci.ko .......no /lib/modules/2.6.18.2-34-default/updates/rt2500usb.ko .......no look in /etc/modprobe.conf and see if you have alias ra0 rt2500 there, it is at the end of the file, then it should work. You can do a lsmod | grep rt2500 from a console and if you can see it there the module is loaded. /Lennart On Thursday 14 December 2006 19:14, Jan Engelhardt wrote:
I was talking at a level below yast, where there is only modprobe, so I might messed that up.
But have you got the card working, and if so, what exactly did you do ?
In short: I have a kernel patchset that adds rt2400, rt2500, and others to the tree (so I have everything in once place - compiling a ton of out-of-tree modules is just no fun). Then I compiled that tree and wrapped it up in rpms called kernel-XYZ-2.6.18.5-jen40b.i586.rpm for example (SUSE-compliant).
So I did not really do something special besides taking rt2500-1.1.0-b4 (more precisely: CVS snapshot) and compiling it.
[ rt2x00 CVS (aka rt2500pci aka rt2x00-2.0...) did not worked for me for long time and I don't use it atm. I anyway only get 5 mbit/s from most wireless APs instead of 11 (some fluke number like Ethernet has?) so I don't think rt2x00 supporting 54 would help me. But even if, I'd rather want a stable driver. ]
-`J' -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Lennart G Peterson wrote:
The rt2500pci module does not work, the module that works is named only as rt2500.
the modules that comes with suse is rt2500pci.ko and rt2500usb.ko they does not work, the module that works is the module created by your compilation rt2500.ko /lib/modules/2.6.18.2-34-default/extra/rt2500.ko ....... works /lib/modules/2.6.18.2-34-default/updates/rt2500pci.ko .......no /lib/modules/2.6.18.2-34-default/updates/rt2500usb.ko .......no
look in /etc/modprobe.conf and see if you have alias ra0 rt2500 there, it is at the end of the file, then it should work.
You can do a lsmod | grep rt2500 from a console and if you can see it there the module is loaded.
/Lennart
On Thursday 14 December 2006 19:14, Jan Engelhardt wrote:
I was talking at a level below yast, where there is only modprobe, so I might messed that up.
But have you got the card working, and if so, what exactly did you do ?
In short: I have a kernel patchset that adds rt2400, rt2500, and others to the tree (so I have everything in once place - compiling a ton of out-of-tree modules is just no fun). Then I compiled that tree and wrapped it up in rpms called kernel-XYZ-2.6.18.5-jen40b.i586.rpm for example (SUSE-compliant).
So I did not really do something special besides taking rt2500-1.1.0-b4 (more precisely: CVS snapshot) and compiling it.
[ rt2x00 CVS (aka rt2500pci aka rt2x00-2.0...) did not worked for me for long time and I don't use it atm. I anyway only get 5 mbit/s from most wireless APs instead of 11 (some fluke number like Ethernet has?) so I don't think rt2x00 supporting 54 would help me. But even if, I'd rather want a stable driver. ]
-`J' --
You are topposting!
-- Med venlig hilsen / Best regards Erik Jakobsen eja@urbakken.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 14 December 2006 20:44, Erik Jakobsen wrote: Have no idea but I wont post anything more /Lennart
Lennart G Peterson wrote:
The rt2500pci module does not work, the module that works is named only as rt2500.
the modules that comes with suse is rt2500pci.ko and rt2500usb.ko they does not work, the module that works is the module created by your compilation rt2500.ko /lib/modules/2.6.18.2-34-default/extra/rt2500.ko ....... works /lib/modules/2.6.18.2-34-default/updates/rt2500pci.ko .......no /lib/modules/2.6.18.2-34-default/updates/rt2500usb.ko .......no
look in /etc/modprobe.conf and see if you have alias ra0 rt2500 there, it is at the end of the file, then it should work.
You can do a lsmod | grep rt2500 from a console and if you can see it there the module is loaded.
/Lennart
On Thursday 14 December 2006 19:14, Jan Engelhardt wrote:
I was talking at a level below yast, where there is only modprobe, so I might messed that up.
But have you got the card working, and if so, what exactly did you do ?
In short: I have a kernel patchset that adds rt2400, rt2500, and others to the tree (so I have everything in once place - compiling a ton of out-of-tree modules is just no fun). Then I compiled that tree and wrapped it up in rpms called kernel-XYZ-2.6.18.5-jen40b.i586.rpm for example (SUSE-compliant).
So I did not really do something special besides taking rt2500-1.1.0-b4 (more precisely: CVS snapshot) and compiling it.
[ rt2x00 CVS (aka rt2500pci aka rt2x00-2.0...) did not worked for me for long time and I don't use it atm. I anyway only get 5 mbit/s from most wireless APs instead of 11 (some fluke number like Ethernet has?) so I don't think rt2x00 supporting 54 would help me. But even if, I'd rather want a stable driver. ]
-`J' --
You are topposting!
-- Med venlig hilsen / Best regards Erik Jakobsen eja@urbakken.dk openSuSE 10.2 (i586) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 14 December 2006 19:09, Lennart G Peterson wrote:
The rt2500pci module does not work, the module that works is named only as rt2500.
the modules that comes with suse is rt2500pci.ko and rt2500usb.ko they does not work, the module that works is the module created by your compilation rt2500.ko /lib/modules/2.6.18.2-34-default/extra/rt2500.ko ....... works /lib/modules/2.6.18.2-34-default/updates/rt2500pci.ko .......no /lib/modules/2.6.18.2-34-default/updates/rt2500usb.ko .......no
look in /etc/modprobe.conf and see if you have alias ra0 rt2500 there, it is at the end of the file, then it should work.
You can do a lsmod | grep rt2500 from a console and if you can see it there the module is loaded.
/Lennart
I have compiled and installed the rt2500 driver as per the procedure I used for 10.1. The module is installed. I have configured the card in YAST selecting the correct module in the Advanced settings. I have added alias ra0 rt2500 to /etc/modprobe.conf/local. I still cannot get it to connect. /var/log/boot/msg reports doneSetting up network interfaces: lo lo IP address: 127.0.0.1/8 done wlan0 device: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01) wlan0 configuration: wlan-bus-pci-0000:00:0b.0 wlan0 (DHCP) . <notice>startproc: execve (/opt/kde3/bin/kdm) [ /opt/kde3/bin/kdm ], [ CONSOLE=/dev/console ROOTFS_FSTYPE=ext3 TERM=linux SHELL=/bin/sh ROOTFS_FSCK=0 INIT_VERSION=sysvinit-2.86 KDEROOTHOME=/root/.kdm REDIRECT=/dev/tty1 COLUMNS=156 PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x31a RUNLEVEL=5 SPLASHCFG=/etc/bootsplash/themes/SuSE/config/bootsplash-1280x1024.cfg PWD=/ LANG=en_GB.UTF-8 PREVLEVEL=N LINES=60 QT_SYSTEM_DIR=/usr/share/desktop-data SHLVL=2 HOME=/ XCURSOR_THEME=crystalwhite WINDOWMANAGER=/usr/bin/kde SPLASH=yes splash=verbose ROOTFS_BLKDEV=/dev/sda3 _=/sbin/startproc DAEMON=/opt/kde3/bin/kdm ] . . . . no IP address yet... backgrounding. waiting Waiting for mandatory devices: wlan-bus-pci-0000:00:0b.0 __NSC__ 12 11 10 <notice>checkproc: /opt/kde3/bin/kdm 3296 8 7 6 4 3 2 1 wlan0 device: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01) wlan0 configuration: wlan-bus-pci-0000:00:0b.0 wlan0 dhcpcd is still waiting for data waiting wlan0 interface could not be set up until now failedSetting up service network . . . . . . . . . . . . . . . .failed DMESG reports rt2500 EEPROM: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Channel rt2500 EEPROM: 7 7 7 7 7 7 7 7 7 7 6 6 6 6 dBm Maximum NET: Registered protocol family 17 audit(1166185504.158:3): audit_pid=4258 old=0 by auid=4294967295 NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver Time: acpi_pm clocksource has been installed. wlan0: no IPv6 routers present Are there clues there as to what is wrong ? FWIW the card works fine in 10.0 and 10.2 Thanks Mike -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Erik Jakobsen -
Jan Engelhardt -
Lennart G Peterson -
michael norman