PDA

View Full Version : EeePC 1000 Fedora 9


masta
29th July 2008, 01:38 AM
Greetings,

I recently purchased the EeePC 1000:

40gb ssd
1gb ram
1.6MHz Intel Atom i686


Because Ubuntu treats users like morons, I prefer to use Fedora 9, despite the fact there seems to be more support for Asus in that user community. So here is a collection of my notes, and issues.


challenges:

1. networking:
# lspci
. . .
01:00.0 Network controller: RaLink Unknown device 0781
03:00.0 Ethernet controller: Attansic Technology Corp. Unknown device 1026 (rev b0)

The stock fedora 9 did not support either Wireless or Ethernet hardware, but fortunately I was able to get my company CDMA card to work, and get the latest software updates online. This would be a big show stopper for most people, freshly installing fedora and not having any networking. My advice is to get a cheap usb-to-ethernet device, or a supported mobile-wireless usb device like I used. Once all the updates to the kernel went in, the Attansic card became functional as ATL1E driver. The wireless driver is still not working which is a RaLink rt2860. I found Linux drivers frm the Ralink website:

http://www.ralinktech.com/ralink/Home/Support/Linux.html

So far I have been unable to compile the driver. =(
As off this writing I'm using:

2.6.25.11-97.fc9.i686 #1 SMP

libgcc-4.3.0-8.i386
gcc-c++-4.3.0-8.i386
gcc-4.3.0-8.i386
glibc-common-2.8-8.i386
glib2-2.16.5-1.fc9.i386
glib-1.2.10-29.fc9.i386
glibc-devel-2.8-8.i386
glibc-2.8-8.i686
glibmm24-2.16.2-1.fc9.i386
glibc-headers-2.8-8.i386


Has anybody been able to compile this driver? If yes, can I have a copy of your .ko file, or instructions that worked for you to compile?

The insulting thing about all this is that the Linux distro that ships pre-installed with EeePC has working wifi driver, and ethernet. I'm considering to use the ndiswrappers, but I find the idea to be undesirable,, so I'm keeping that as an option of last resort.


The next challenge is ACPI related. After all my system updates completed, I tried to hibernate to the SSD drive, and the screen went black with blinking cursor. I shutdown the system by force (power key), and on the next bootup the system resumed to my previous desktop instance. So it partialy works just not all the way. I suspect the kernel module eeepc_laptop had something to do with that. See you lsmod output for modules.

All in all Im extremely happy with fedora 9 core on the EeePC 1000. The Gnome desktop does not overwhelm the device, and even compiz effects work with snappiness, and efficiency. I prefer to use fluxbox which is more suited for a light-weight laptop environment, and more importantly for 1024x600 desktop display. For example, in gnome you have basic gnome preference panels that are too tall to display in 600 pixels vertical. There is no acceptable method to move the window beyond the top boundary to reach the buttons you must "ok" , or "accept", or even "cancel" at the bottom. This is a major usability problem with Gnome in general, and is why Linus himself advocates users to avoid gnome as I suggest Ubuntu thinks users are morons. Anyways, the important ability Fluxbox provides is the capability to press 'alt+right click' to move/drag the window around when they are too big for the screen to get to the region of window you need. Also fluxbox is more efficient and makes Mozilla browsing better.


I hope this helps other EeePC 1000 and 901 users. Also I hope somebody can assist the 1000/901 community to get RaLink drivers working. =)

cheers,
-masta

scottro
29th July 2008, 02:06 AM
The EEE PC uses the AR5007EG card. I'm not sure if the Xandros install uses MadWifi or ndsiwrapper--I think it might be the latter as at least one person I know couldn't connect to a WPA2 network, which has frequently been mentioned in connection with the net5211 driver used with ndiswrapper and that card.

For detaild instructions on getting the wireless working
see
http://home.nyc.rr.com/computertaijutsu/rhwireless.html#5007

NOTE--that page assumes a working internet connection. If running Fedora 9, the livna-testing (note that I said testing) repo might work, which is covered on that page.

masta
29th July 2008, 02:26 AM
The EEE PC uses the AR5007EG card.

The old EeePC used the Atheros wifi driver, And the NEW EeePC 901/1000 uses the RaLink wifi.

Here is the output from lspci:
. . .
01:00.0 Network controller: RaLink Unknown device 0781
03:00.0 Ethernet controller: Attansic Technology Corp. Unknown device 1026 (rev b0)

Madwifi will not work with non-atheros hardware, but thanks for trying to help scott. =)

masta
29th July 2008, 02:38 AM
Again, the new EeePC uses RaLink rt2860 wifi-b/g/n hardware.
The Ralink drivers are open source, and available here:

http://www.ralinktech.com/ralink/Home/Support/Linux.html


When I compile the driver, here is the error output:

[root@localhost 2008_0325_RT2860_Linux_STA_v1.6.1.0]# make
make -C tools
make[1]: Entering directory `/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/tools'
gcc -g bin2h.c -o bin2h
make[1]: Leaving directory `/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/tools'
/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/tools/bin2h
cp -f os/linux/Makefile.6 /home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/Makefile
make -C /lib/modules/2.6.25.11-97.fc9.i686/build SUBDIRS=/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux modules
make[1]: Entering directory `/usr/src/kernels/2.6.25.11-97.fc9.i686'
CC [M] /home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/../../common/rtmp_init.o
CC [M] /home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/../../os/linux/sta_ioctl.o
/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/../../os/linux/sta_ioctl.c: In function ‘rt_ioctl_giwscan’:
. . .
/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/../../os/linux/sta_ioctl.c:1206: error: too few arguments to function ‘iwe_stream_add_event’
. .
/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/../../os/linux/sta_ioctl.c:1222: error: too few arguments to function ‘iwe_stream_add_point’
. . .
/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/../../os/linux/sta_ioctl.c:1249: error: too few arguments to function ‘iwe_stream_add_event’
. . .
/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/../../os/linux/sta_ioctl.c:1269: error: too few arguments to function ‘iwe_stream_add_event’
. . .
/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/../../os/linux/sta_ioctl.c:1284: error: too few arguments to function ‘iwe_stream_add_event’
. . .
/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/../../os/linux/sta_ioctl.c:1302: error: too few arguments to function ‘iwe_stream_add_point’
. . .
/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/../../os/linux/sta_ioctl.c:1332: error: too few arguments to function ‘iwe_stream_add_value’
. . .
/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/../../os/linux/sta_ioctl.c:1357: error: too few arguments to function ‘iwe_stream_add_point’
. . .
/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/../../os/linux/sta_ioctl.c:1378: error: too few arguments to function ‘iwe_stream_add_point’
make[2]: *** [/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/../../os/linux/sta_ioctl.o] Error 1
make[1]: *** [_module_/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux] Error 2
make[1]: Leaving directory `/usr/src/kernels/2.6.25.11-97.fc9.i686'
make: *** [LINUX] Error 2


I omitted the warnings about invalid cast from pointer with the elipes' but if you want those can be preserved for more verbose readers.

scottro
29th July 2008, 04:02 AM
Hrrm, interesting. I missed that the wireless was a Ralink in the first post (I was expecting to see something about wireless in lspci and for some reason, thought both lines were for the wired interface.)

I'm very glad you posted though, I had been considering buying the 900 series. Do you know if the Ubuntu folks have it working, as I might still buy one for my wife to use while traveling? Mandriva probably does, as I think they have had an EEE PC version for awhile.

I've also been looking at the Sylvania Netbook, though the tiny mouse pad seems as if it would be a pain. I've been, so far, unable to find out what card it uses.

It seems to be getting harder and harder to actually find out what hardware a laptop has--even newegg. which I always thought of as Linux friendly, will seldom post more than 802.11 a/b/g/n wlan or the like.

djselbeck
29th July 2008, 08:09 AM
You could also try using ndiswrapper !? As far as I know it should work with Ralink Cards but is absolutely not the best solution.

hdp
29th July 2008, 12:42 PM
I have an eee 901 (same wireless chipset) and have managed to modify the Ralink driver so that it works. I have tested it with an open network, WEP and WPA2 using Network Manager and it was able to connect to all of them.

The patch is attached, and it needs to be applied to os/linux/sta_ioctl.c

After applying that make sure you follow the instructions in the readme, then it should compile and install cleanly.

masta
29th July 2008, 05:09 PM
The patch is attached, and it needs to be applied to os/linux/sta_ioctl.c

After applying that make sure you follow the instructions in the readme, then it should compile and install cleanly.


HDP:

I read your patch to see what you did, and see the fix is trivial, and pretty much exactly what the warnings/errors tell me. I added "info" to the functions to make it work like you did.

One thing about the patch, it does not apply cleanly, so after applying, on the resulting file on line (aprox) 1380 I simply added "info" as the first parameter, and it compiled clean.


Here is a log of my console for those who might like to read an example of how it should work:


[root@localhost linux]# patch sta_ioctl.c sta_ioctl.patch
patching file sta_ioctl.c
Hunk #1 succeeded at 243 with fuzz 2 (offset 33 lines).
Hunk #2 succeeded at 1172 (offset 97 lines).
Hunk #3 succeeded at 1124 (offset 33 lines).
Hunk #4 succeeded at 1215 (offset 97 lines).
Hunk #5 succeeded at 1171 (offset 33 lines).
Hunk #6 succeeded at 1250 (offset 97 lines).
Hunk #7 succeeded at 1204 (offset 33 lines).
Hunk #8 succeeded at 1296 (offset 97 lines).
Hunk #9 FAILED at 1320.
Hunk #10 FAILED at 1338.
Hunk #11 succeeded at 1259 with fuzz 2 (offset -3 lines).
misordered hunks! output would be garbled
Hunk #12 FAILED at 1359.
3 out of 12 hunks FAILED -- saving rejects to file sta_ioctl.c.rej


[root@localhost 2008_0325_RT2860_Linux_STA_v1.6.1.0]# vi os/linux/sta_ioctl.c
[root@localhost 2008_0325_RT2860_Linux_STA_v1.6.1.0]# make
make -C tools
make[1]: Entering directory
`/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/tools'
gcc -g bin2h.c -o bin2h
make[1]: Leaving directory
`/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/tools'
/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/tools/bin2h
cp -f os/linux/Makefile.6
/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/Makefile
make -C /lib/modules/2.6.25.11-97.fc9.i686/build
SUBDIRS=/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux
modules
make[1]: Entering directory `/usr/src/kernels/2.6.25.11-97.fc9.i686'
CC [M] /home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/../../common/rtmp_init.o
CC [M] /home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/../../os/linux/sta_ioctl.o
CC [M] /home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/../../common/2860_rtmp_init.o
CC [M] /home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/../../os/linux/2860_main_dev.o
CC [M] /home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/../../common/cmm_data_2860.o
LD [M] /home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/rt2860sta.o
Building modules, stage 2.
MODPOST 1 modules
CC /home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/rt2860sta.mod.o
LD [M] /home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/rt2860sta.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.25.11-97.fc9.i686'
cp -f /home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux/rt2860sta.ko
/tftpboot
[root@localhost 2008_0325_RT2860_Linux_STA_v1.6.1.0]# make install
make -C /home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux
-f Makefile.6 install
make[1]: Entering directory
`/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux'
rm -rf /etc/Wireless/RT2860STA
mkdir /etc/Wireless/RT2860STA
cp /home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/RT2860STA.dat
/etc/Wireless/RT2860STA/.
install -d /lib/modules/2.6.25.11-97.fc9.i686/kernel/drivers/net/wireless/
install -m 644 -c rt2860sta.ko
/lib/modules/2.6.25.11-97.fc9.i686/kernel/drivers/net/wireless/
/sbin/depmod -a 2.6.25.11-97.fc9.i686
make[1]: Leaving directory
`/home/diz/build/2008_0325_RT2860_Linux_STA_v1.6.1.0/os/linux'

hdp
29th July 2008, 05:17 PM
You seem to be using an older version of the driver, version 1.7.0.0 is available on the RaLink site, which has some fixes if you can be bothered to compile again.

masta
29th July 2008, 06:17 PM
You seem to be using an older version of the driver, version 1.7.0.0 is available on the RaLink site, which has some fixes if you can be bothered to compile again.


Acknowledged. The 1.70 version patched clean.

After reboot network-manager presents to me AP's and works. Before with 1.60 the network manager did not work.

Thanks HDP!
I'm going to add these steps to my eeepc-901/1000 howto, may I cite you?

hdp
29th July 2008, 06:22 PM
Sure. Have you gotten the special/fn buttons working yet?

masta
29th July 2008, 06:46 PM
Sure. Have you gotten the special/fn buttons working yet?


Thanks. No I have not made the buttons work yet, but I've noticed acpi began working mysteriously after the ralink driver issue was resolved. So now the only task left is the special buttons.

masta
29th July 2008, 07:23 PM
Sure. Have you gotten the special/fn buttons working yet?

hdp:

when I use fluxbox instead of gnome, the fn buttons work.


for example, the Fn+F5 (dim) and Fn+F6 (brighten) work.

However, the mute (F10) and volume (F11, and f12 respective) do not work.

I'll see if I can reproduce some of the noob'untu steps.

masta
29th July 2008, 10:41 PM
I can confirm the RaLink driver operates at wireless-N speed.

I'm getting a solid 65Mb/s.

Ever since the RA0 device appeared in ifconfig, acpi hibernate mode started working when I shut the lid.

It would suggest the acpi DSDT needs to be tweaked.

I suspect to get the buttons working we could dump that file and try some modifications.
I'll start working on this now.

hdp
29th July 2008, 11:06 PM
I have most of the buttons working. See: http://fedoraproject.org/wiki/EeePc for more information. The provided scripts needed a few tweaks, I must go to bed now but I can provide what I have done tomorrow.

Fn+F5 and Fn+F6 worked in Gnome for me out of the box as well as suspend, all others had to be configured by me.

scottro
30th July 2008, 03:26 AM
As someone who might purchase the 900 sooner or later, I want to sincerely thank all of you for your efforts. I'm very glad I came across this thread.

hdp
30th July 2008, 03:19 PM
I now have all the special keys working apart from Fn+F6 (which I think is for toggling the performance settings) and the second silver button on the top (to change the resolution of the LCD panel?). This is based upon http://fedoraproject.org/wiki/EeePc

The conf file goes in /etc/acpi/events and the two shell scripts (make sure you take .txt off the end and make them executable) go in /etc/acpi/actions.

If you want the monitor manipulations to work make sure you run the xhost commands listed on the wiki.

In eeepc-hotkeys.sh change the two "su huw ........." lines so that huw is the username to run the programs as (and change firefox and thunderbird to something else, if you want the buttons to do something else).

This seems to work OK, but occasionally acpid seems to crash and needs restarting before it responds to key presses again. Also Fn+F5 can be a bit unpredictable, but that could be to do with the monitor that I was plugging it.

None of the actions has an osd, although http://code.google.com/p/eee-osd/ looks interesting, It appears to be based on Asus source for the 701, to go with the ACPI driver. I was wondering if there was a newer version of this of the 901/1000, but I have not been able to find any Asus source for the 901/1000.

kyled185
2nd August 2008, 10:00 PM
I've downloaded the 1.7 driver and applied the patch, but nothing shows up in network manager. dmesg output shows nothing after loading the driver and ifconfig only shows ra0 when I do ifconfig ra0 up. iwconfig is showing ra0 but configuring wireless without network manager is really not an option, I'm not going to constantly be dealing with configuration files just to log into a new network. What options did you guys apply to the Makefile?

masta
2nd August 2008, 11:00 PM
I've downloaded the 1.7 driver and applied the patch, but nothing shows up in network manager.

Did you follow the steps in the README file, especially the parts about wpa_suplicant?

kyled185
2nd August 2008, 11:34 PM
Ok I thought I had but I missed a step. Thanks.

kyled185
3rd August 2008, 02:25 AM
Has anyone got the webcam working? I followed a tutorial here (http://www.ubuntu-eee.com/index.php5?title=EeePC_901#Webcam_.26_Bluetooth) but all that happens when I run ucview to test it out is a yellow square where the image should be quickly followed by the application crashing. The LED by the camera also turns yellow at this time as well.

(ucview:6970): GConf-CRITICAL **: gconf_client_set_string: assertion `val != NULL' failed
The program 'ucview' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 1582 error_code 11 request_code 140 minor_code 19)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)

masta
3rd August 2008, 03:43 AM
Has anyone got the webcam working? I followed a tutorial here (http://www.ubuntu-eee.com/index.php5?title=EeePC_901#Webcam_.26_Bluetooth) but all that happens when I run ucview to test it out is a yellow square where the image should be quickly followed by the application crashing. The LED by the camera also turns yellow at this time as well.
[code]


Kyled185:

My webcam device shows in UCV as CNF7129, and yes it works.
The other app, "cheese" also works.

I suggest you update your system with yum, or the gnome update applet.

kstuntz
4th August 2008, 05:27 PM
Hey guys, thank you for this! I have an Encore ENLWI-N PCI card that I couldn't get working and this saved the day. Thanks again.

marcelkraan
4th August 2008, 06:07 PM
my girl bought this but gues!!!!
windows xp installed... so i have the driver disk here :-)

kyled185
4th August 2008, 08:45 PM
It turns out that compositing in KDE 4.0 and 4.1 seemed to be the cause of the webcam issue. Since I won't be using the webcam much I'll just disable kwin desktop effects when I need the webcam.

Jaydee
6th August 2008, 03:34 PM
HDP:

I read your patch to see what you did, and see the fix is trivial, and pretty much exactly what the warnings/errors tell me. I added "info" to the functions to make it work like you did.

One thing about the patch, it does not apply cleanly, so after applying, on the resulting file on line (aprox) 1380 I simply added "info" as the first parameter, and it compiled clean.




Hello,

Its great to see that there is an easy fix :rolleyes: to the wireless access problem on the EeePC 901. I have downloaded the new Ralink driver (V. 1.7) but unfortunately, being new to Linux, everything that has been written above is difficult for me to grasp entirely. For instance, I don' t even know if there is a decompression utility included in the kernel. So, I was wondering if someone here would be able to outline the steps required to solve this problem in a way that can be more easily understood by someone with no Linux experience.

Thank you.

masta
6th August 2008, 04:55 PM
I was wondering if someone here would be able to outline the steps required to solve this problem in a way that can be more easily understood by someone with no Linux experience.



mkdir build
cd build
wget http://www.ralinktech.com.tw/data/drivers/2008_0708_RT2860_Linux_STA_v1.7.0.0.tar.bz2
bunzip2 2008_0708_RT2860_Linux_STA_v1.7.0.0.tar.bz2
tar xvf 2008_0708_RT2860_Linux_STA_v1.7.0.0.tar
cd 2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux
cp sta_ioctl.c sta_ioctl.c.orig

(download hpd's patch to this dir)

patch sta_ioctl.c sta_ioctl.patch

follow the README

Jaydee
7th August 2008, 02:31 AM
mkdir build
cd build
wget http://www.ralinktech.com.tw/data/drivers/2008_0708_RT2860_Linux_STA_v1.7.0.0.tar.bz2
bunzip2 2008_0708_RT2860_Linux_STA_v1.7.0.0.tar.bz2
tar xvf 2008_0708_RT2860_Linux_STA_v1.7.0.0.tar
cd 2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux
cp sta_ioctl.c sta_ioctl.c.orig

(download hpd's patch to this dir)

patch sta_ioctl.c sta_ioctl.patch

follow the README

Hey. thanks for your help. Well, I've followed these instruction up to the last line. But there are a few points in the readme file which need to be clarified somewhat. I have outlined them below. To make things clear, the instructions from the readme file appear in blue in the following text, while my comment/question appear in green...


Build Instructions:

1> $tar -xvzf DPB_RT2860_Linux_STA_x.x.x.x.tgz

Due to the procedure you outlined in your previous post, all the files have already been extracted from the archive into the 2008_0708_RT2860_Linux_STA_v1.7.0.0 directory, so I guess I should disregard this instruction, right?


2> In Makefile

set the "MODE = STA" in Makefile and chose the TARGET to Linux by set "TARGET = LINUX"

"MODE = STA" (RT28xx_MODE = STA) and "TARGET = LINUX" are already set, so I guess I should disregard this too...

define the linux kernel source include file path LINUX_SRC

My guess is that since PLATFORM = PC is the uncommented line, the following condition

ifeq ($(PLATFORM),PC)
# Linux 2.6
LINUX_SRC = /lib/modules/$(shell uname -r)/build
...

is the one that executes, and therefore it automatically defines the kernel source include file path. Is this correct, or do I need to modify anything?


3> In os/linux/config.mk
define the GCC and LD of the target machine
define the compiler flags CFLAGS

The config.mk file has the following lines:

CC := $(CROSS_COMPILE)gcc
LD := $(CROSS_COMPILE)ld

Do I need to modify anything on these lines?

Then there is the following instruction

** Build for being controlled by NetworkManager or wpa_supplicant wext functions
Please set 'HAS_WPA_SUPPLICANT=y' and 'HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y'.
=> #>cd wpa_supplicant-x.x
=> #>./wpa_supplicant -Dwext -ira0 -c wpa_supplicant.conf -d

The first line is quite clear, but what about the 2 following lines? My understanding is that "cd wpa_supplicant-x.x" means that I should switch to this directory. But from what I can see, wpa_supplicant is not a directory but a file located in the usr/sbin directory. So I'm a bit confused here.


4> $make

So just typing make at the prompt will do the trick or should I move to a specific directory? And don't I need to provide parameters for that command?


5> $cp RT2860STA.dat /etc/Wireless/RT2860STA/RT2860STA.dat
# !!!check if it is a binary file before loading !!!

RT2860STA.dat looks to me as a text file, as evidenced a bit further in the CONFIGURATION section of the readme file. I do I turn it into a binary?


6> load driver
#[kernel 2.4]
# $/sbin/insmod rt2860sta.o
# $/sbin/ifconfig ra0 inet YOUR_IP up

#[kernel 2.6]
# $/sbin/insmod rt2860sta.ko
# $/sbin/ifconfig ra0 inet YOUR_IP up

Why are these lines commented out and how do I figure out which of the 2 kernels I've got?


7> unload driver
$/sbin/ifconfig ra0 down
$/sbin/rmmod rt2860sta

So I load the driver and then unload it, and then I'm all set?


Thanks again!

masta
7th August 2008, 03:13 AM
Hey. thanks for your help. Well, I've followed these instruction up to the last line. But there are a few points in the readme file which need to be clarified somewhat. I have outlined them below. To make things clear, the instructions from the readme file appear in blue in the following text, while my comment/question appear in green...


Build Instructions:

1> $tar -xvzf DPB_RT2860_Linux_STA_x.x.x.x.tgz

Due to the procedure you outlined in your previous post, all the files have already been extracted from the archive into the 2008_0708_RT2860_Linux_STA_v1.7.0.0 directory, so I guess I should disregard this instruction, right?


2> In Makefile

set the "MODE = STA" in Makefile and chose the TARGET to Linux by set "TARGET = LINUX"

"MODE = STA" (RT28xx_MODE = STA) and "TARGET = LINUX" are already set, so I guess I should disregard this too...



Correct on both counts.
1. My steps extract the files, and get you patched.
2. the Makefile does not require any editing.



define the linux kernel source include file path LINUX_SRC

My guess is that since PLATFORM = PC is the uncommented line, the following condition

ifeq ($(PLATFORM),PC)
# Linux 2.6
LINUX_SRC = /lib/modules/$(shell uname -r)/build
...

is the one that executes, and therefore it automatically defines the kernel source include file path. Is this correct, or do I need to modify anything?



That is right, the make file does a good job of assuming where the correct linux_src location is. You may verify the path with the follwoing cmd:

ls -ld /lib/modules/$(shell uname -r)/build



3> In os/linux/config.mk
define the GCC and LD of the target machine
define the compiler flags CFLAGS

The config.mk file has the following lines:

CC := $(CROSS_COMPILE)gcc
LD := $(CROSS_COMPILE)ld

Do I need to modify anything on these lines?


No!
Leave those alone.



Then there is the following instruction

** Build for being controlled by NetworkManager or wpa_supplicant wext functions
Please set 'HAS_WPA_SUPPLICANT=y' and 'HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y'.
=> #>cd wpa_supplicant-x.x
=> #>./wpa_supplicant -Dwext -ira0 -c wpa_supplicant.conf -d

The first line is quite clear, but what about the 2 following lines? My understanding is that "cd wpa_supplicant-x.x" means that I should switch to this directory. But from what I can see, wpa_supplicant is not a directory but a file located in the usr/sbin directory. So I'm a bit confused here.



I can understand how this might be the most confusing part of the entire process.
YOU WANT TO MAKE THESE CHANGES.

HAS_WPA_SUPPLICANT=y
HAS_NATIVE_WPA_SUPPLICANT_SUPPORT=y

This is very important step. Without this step you will not have an easy time to get the wireless to auto-magically work.
These should be the only two modifications in that file.
After this you have no more items to do except to run "make" and "make install".

HEre are those steps:

cd build/2008_0708_RT2860_Linux_STA_v1.7.0.0/
make
. . .
make install
. . .

(reboot)

Everything will be finished by the reboot, no more steps by you are required.
After reboot the network applciation will inform you that there are wireless networks.

Thanks again!

You welcome, and plz let me know if this helped.
If you get it working I'd like your help to make this process more documented for other new users of linux, ok?

Jaydee
7th August 2008, 06:10 PM
You welcome, and plz let me know if this helped.
If you get it working I'd like your help to make this process more documented for other new users of linux, ok?

If I can help other people, I' ll be glad to contribute. As a matter of fact, my Linux inexperience will enable me to provide easy instructions for equally inexperienced users.

Unfortunately I still haven't completed the process because of some unforeseen difficulties...

First, it is interesting to note that the shell command doesn't work on my device. Trying to execute the following line:

ls -ld /lib/modules/$(shell uname -r)/build

returns:

bash: shell: command not found

However, the uname command runs by itself. Therefore,

ls -ld /lib/modules/$(shell uname -r)/build

becomes

ls -ld /lib/modules/$(uname -r)/build

And this works very well. However, although the /lib/modules/2.6.21.4-eeepc directory exists, it has no subdirectory called build.

From the above, this block of code in the Makefile:

ifeq ($(PLATFORM),PC)
# Linux 2.6
LINUX_SRC = /lib/modules/$(shell uname -r)/build
# Linux 2.4 Change to your local setting
#LINUX_SRC = /usr/src/linux-2.4
LINUX_SRC_MODULE = /lib/modules/$(shell uname -r)/kernel/drivers/net/wireless/
CROSS_COMPILE =
endif

must be modified as follow

ifeq ($(PLATFORM),PC)
# Linux 2.6
LINUX_SRC = /lib/modules/$(uname -r)/???
# Linux 2.4 Change to your local setting
#LINUX_SRC = /usr/src/linux-2.4
LINUX_SRC_MODULE = /lib/modules/$(uname -r)/kernel/drivers/net/wireless/
CROSS_COMPILE =
endif

if it is to execute on the EeePC 901. But there is still an unknown parameter to provide (or is there?). So my question is: what kind of files (.h, .c or .ko) do we need to provide a path for? The readme file says: " define the linux kernel source include file path LINUX_SRC", so I guess this means header files, but I'm not sure about this...

Anyway, if I invoque "make" here is what happens:

/home/user/build/2008_0708_RT2860_Linux_STA_v1.7.0.0> make
make -C tools
make[1]: Entering directory `/home/user/build/2008_0708_RT2860_Linux_STA_v1.7.0.0/tools'
gcc -g bin2h.c -o bin2h
make[1]: gcc: Command not found
make[1]: *** [all] Error 127
make[1]: Leaving directory `/home/user/build/2008_0708_RT2860_Linux_STA_v1.7.0.0/tools'
make: *** [build_tools] Error 2

Since it couldn't find gcc, I looked for it. What I found is the following file located as indicated:

/usr/lib/gcc/i486-linux-gnu/4.1.2/cc1

Which brings me to the second question: what do I do next? :confused:

Best regards.

hdp
7th August 2008, 06:37 PM
The problem seems to be that you don't have the full set of programs required to compile software. If you run:

yum install gcc gcc-c++ make kernel-headers kernel-devel

That should give you everything you need, and you should find that the build folder appears in the right place for the makefile. Changing back to the Makefile provided should now work.

masta
8th August 2008, 12:23 AM
I need for you to install gcc, and the kernel source.

When you type `uname -a` you can see the kernel version you have installed.

When you use the package manager to browse/search for "kernel" you will want to install the kernel develop.

We may need to specify the path to the sources without any of the variables in the path.

scottro
8th August 2008, 12:26 AM
Is yum already working at this point? What about something like (this is what I have in most of my pages that involve some compiling)
yum -y install gcc gcc-c++ make kernel-devel

This usually pulls in the other necessaries, e.g., kernel-headers, as dependencies.

Jaydee
8th August 2008, 02:40 PM
The problem seems to be that you don't have the full set of programs required to compile software. If you run:

yum install gcc gcc-c++ make kernel-headers kernel-devel

That should give you everything you need, and you should find that the build folder appears in the right place for the makefile. Changing back to the Makefile provided should now work.

Thank you.

Well, you may be reassured to know that the good old reliable Peter principle still works (i.e.: If something can go wrong, it will) :D .

So, not having the full set of programs also meant not having yum. But I was able to install it after struggling for a while with the password issue with the " su -" command.

And then, as the "yum install gcc gcc-c++ make kernel-headers kernel-devel" line was executing, I was told that the RPM module was missing :) .

I have now downloaded RPM but haven't installed it yet because I had other stuff to do. RPM is also a tar.gz file, and I was wondering if the installation process is the same as what I have seen so far (i.e.: extract, make, make install)?

Also, I have received the following email from Ralink support. It seems that some people over there are not aware of the problem:

"Dear Sir:

I had check these security function is work well, I don’t know why you can not to establish an encrypted wireless connection.

For EeePC driver package, please contact Asus provide it.

The attached file is the driver image for EeePC 901, please use it to replace the old one.

The step as follow:

Ctrl+Alt+T (call console window out)

sudo –su

cp rt2860sta.ko /lib/modules/2.6.21.4-eeepc/rt2860/rt2860sta.ko"


Any comment?

Best regards.

hdp
8th August 2008, 03:09 PM
I did not think it was possible to install Fedora without yum. How did you install Fedora?

Jaydee
8th August 2008, 03:55 PM
I did not think it was possible to install Fedora without yum. How did you install Fedora?

I do not have Fedora installed. I have an brand new out of the box EeePC 901 with whatever version of Linux it came with.

masta
8th August 2008, 04:16 PM
I do not have Fedora installed. I have an brand new out of the box EeePC 901 with whatever version of Linux it came with.


FYI: Peter Principle means "to rise up, and to reach your own personal level of incompetence"
FYI2: Murphy law means "if something is possible to go wrong, eventually it will"


Regardless, this forum is for users of Fedora Linux. Since you have the EeePC 901 with Xandros Linux (the Linux pre-installed on EeePC), you already have the wireless driver installed. I was unable to get wireless security to work in that version of Linux too.

You may choose to install Fedora if you like, and I would be happy to help you when you do make that step. =)

Jaydee
8th August 2008, 04:34 PM
FYI: Peter Principle means "to rise up, and to reach your own personal level of incompetence"
FYI2: Murphy law means "if something is possible to go wrong, eventually it will"



Oupps! You are absolutely right!

exit
16th August 2008, 09:02 PM
Hi there. I was following those steps , but I got error when I restart pc and linux trays to get up ra0 . Than I go to System ->
Administration -> Network and there is my ra0 Inactive. When I type ifup ra0 I got error:

Error for wireless request "Set Mode" (8B06) : SET failed on device ra0 ; Invalid argument.
Determining IP information for ra0 ... failed.

But when I try iwlist ra0 scanning I got list of wireless connections.
Would you help me please to find out where if problem . Thank you

And another think is: my ifconfig gives me lo and ra0 .
and my iwconfig gives me ra0 .
Is not something wrong there ? I have got for ethernet ra0 and the same name for wireless raO .

Quasar8000
17th August 2008, 10:48 AM
I just opened my new EeePC 901 :-) and naturally I want to remove Xandros and install Fedora 9. I went through this whole thread and must say it's very useful. I just have a couple of questions left though:

1. If I got it right, neither the wired nor the wireless network adapters work out-of-the-box after a clean installation of Fedora 9, is there any way to fix that other than adding a third temporary network adapter to update the Fedora installation?

2. How do I reduce the read/write cycles to the SSD as much as possible? I made up my mind to use Ext3, I'll add noatime to fstab, but I'm not sure whether to create a swap partition and what size to make it.

Any ideas regarding either of the above issues?

nicubunu
18th August 2008, 02:35 PM
A couple of days ago I received my 1000h and the default Xandros was gone in a matter of hours :D

I tested briefly Fedora 9 and the Alpha for Fedora 10 and settled for the later: at least the wired network works here out of the box.

The wireless part is a bit daunting: I installed the live desktop image and I don't have (yet) gcc on the machine. And I am not that comfortable about recompiling drivers each time when a new kernel is pushed into rawhide (which happens quite often).

Quasar8000
18th August 2008, 03:00 PM
I was actually considering trying Fedora 10 but thought it would be better to wait at least till the beta is released (which is in two weeks), but it's good news to know the wired network works out of the box.

D3viL
25th August 2008, 12:49 AM
Hi all,

i tried to download hdp's patch ... but the file is 0kb ... anyone can help me ?

i need to make my eeepc 1000 work with the Ralink device :)
Thx a lot in advance.

D3viL.

hdp
25th August 2008, 09:22 AM
It is odd that you can't download it, so I have copied and pasted it below. When saving it as a file it is important that no new line breaks are introduced.

--- 2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/sta_ioctl.c 2008-07-04 07:01:00.000000000 +0100
+++ rt2860modified/os/linux/sta_ioctl.c 2008-07-29 12:13:01.000000000 +0100
@@ -210,6 +210,8 @@
IN PUCHAR arg);
#endif // EXT_BUILD_CHANNEL_LIST //

+
+
static struct {
CHAR *name;
INT (*set_proc)(PRTMP_ADAPTER pAdapter, PUCHAR arg);
@@ -1073,7 +1075,7 @@
memcpy(iwe.u.ap_addr.sa_data, &pAdapter->ScanTab.BssEntry[i].Bssid, ETH_ALEN);

previous_ev = current_ev;
- current_ev = iwe_stream_add_event(current_ev,end_buf, &iwe, IW_EV_ADDR_LEN);
+ current_ev = iwe_stream_add_event(info,current_ev,end_buf, &iwe, IW_EV_ADDR_LEN);
if (current_ev == previous_ev)
#if WIRELESS_EXT >= 17
return -E2BIG;
@@ -1089,7 +1091,7 @@
iwe.u.data.flags = 1;

previous_ev = current_ev;
- current_ev = iwe_stream_add_point(current_ev,end_buf, &iwe, pAdapter->ScanTab.BssEntry[i].Ssid);
+ current_ev = iwe_stream_add_point(info,current_ev,end_buf, &iwe, pAdapter->ScanTab.BssEntry[i].Ssid);
if (current_ev == previous_ev)
#if WIRELESS_EXT >= 17
return -E2BIG;
@@ -1116,7 +1118,7 @@
iwe.len = IW_EV_UINT_LEN;

previous_ev = current_ev;
- current_ev = iwe_stream_add_event(current_ev, end_buf, &iwe, IW_EV_UINT_LEN);
+ current_ev = iwe_stream_add_event(info,current_ev, end_buf, &iwe, IW_EV_UINT_LEN);
if (current_ev == previous_ev)
#if WIRELESS_EXT >= 17
return -E2BIG;
@@ -1136,7 +1138,7 @@
iwe.u.freq.i = 0;

previous_ev = current_ev;
- current_ev = iwe_stream_add_event(current_ev,end_buf, &iwe, IW_EV_FREQ_LEN);
+ current_ev = iwe_stream_add_event(info,current_ev,end_buf, &iwe, IW_EV_FREQ_LEN);
if (current_ev == previous_ev)
#if WIRELESS_EXT >= 17
return -E2BIG;
@@ -1151,7 +1153,7 @@
iwe.u.qual.level = 0;
iwe.u.qual.noise = 0;
set_quality(pAdapter, &iwe.u.qual, pAdapter->ScanTab.BssEntry[i].Rssi);
- current_ev = iwe_stream_add_event(current_ev, end_buf, &iwe, IW_EV_QUAL_LEN);
+ current_ev = iwe_stream_add_event(info,current_ev, end_buf, &iwe, IW_EV_QUAL_LEN);
if (current_ev == previous_ev)
#if WIRELESS_EXT >= 17
return -E2BIG;
@@ -1169,7 +1171,7 @@
iwe.u.data.flags = IW_ENCODE_DISABLED;

previous_ev = current_ev;
- current_ev = iwe_stream_add_point(current_ev, end_buf,&iwe, (char *)pAdapter->SharedKey[BSS0][(iwe.u.data.flags & IW_ENCODE_INDEX)-1].Key);
+ current_ev = iwe_stream_add_point(info,current_ev, end_buf,&iwe, (char *)pAdapter->SharedKey[BSS0][(iwe.u.data.flags & IW_ENCODE_INDEX)-1].Key);
if (current_ev == previous_ev)
#if WIRELESS_EXT >= 17
return -E2BIG;
@@ -1197,7 +1199,7 @@
iwe.u.bitrate.value = (tmpRate/2) * 1000000;

iwe.u.bitrate.disabled = 0;
- current_val = iwe_stream_add_value(current_ev,
+ current_val = iwe_stream_add_value(info,current_ev,
current_val, end_buf, &iwe,
IW_EV_PARAM_LEN);

@@ -1221,7 +1223,7 @@
pAdapter->ScanTab.BssEntry[i].WpaIE.IELen);
iwe.cmd = IWEVGENIE;
iwe.u.data.length = pAdapter->ScanTab.BssEntry[i].WpaIE.IELen;
- current_ev = iwe_stream_add_point(current_ev, end_buf, &iwe, custom);
+ current_ev = iwe_stream_add_point(info,current_ev, end_buf, &iwe, custom);
if (current_ev == previous_ev)
#if WIRELESS_EXT >= 17
return -E2BIG;
@@ -1239,7 +1241,7 @@
pAdapter->ScanTab.BssEntry[i].RsnIE.IELen);
iwe.cmd = IWEVGENIE;
iwe.u.data.length = pAdapter->ScanTab.BssEntry[i].RsnIE.IELen;
- current_ev = iwe_stream_add_point(current_ev, end_buf, &iwe, custom);
+ current_ev = iwe_stream_add_point(info,current_ev, end_buf, &iwe, custom);
if (current_ev == previous_ev)
#if WIRELESS_EXT >= 17
return -E2BIG;
@@ -1260,7 +1262,7 @@
for (idx = 0; idx < pAdapter->ScanTab.BssEntry[i].WpaIE.IELen; idx++)
sprintf(custom, "%s%02x", custom, pAdapter->ScanTab.BssEntry[i].WpaIE.IE[idx]);
previous_ev = current_ev;
- current_ev = iwe_stream_add_point(current_ev, end_buf, &iwe, custom);
+ current_ev = iwe_stream_add_point(info,current_ev, end_buf, &iwe, custom);
if (current_ev == previous_ev)
#if WIRELESS_EXT >= 17
return -E2BIG;
@@ -1280,7 +1282,7 @@
for (idx = 0; idx < pAdapter->ScanTab.BssEntry[i].RsnIE.IELen; idx++)
sprintf(custom, "%s%02x", custom, pAdapter->ScanTab.BssEntry[i].RsnIE.IE[idx]);
previous_ev = current_ev;
- current_ev = iwe_stream_add_point(current_ev, end_buf, &iwe, custom);
+ current_ev = iwe_stream_add_point(info,current_ev, end_buf, &iwe, custom);
if (current_ev == previous_ev)
#if WIRELESS_EXT >= 17
return -E2BIG;

D3viL
25th August 2008, 03:31 PM
Thank you hdp :)

Nicoal
29th August 2008, 05:48 PM
First let me thank you all of you for these very helpful informations !

I follow all the steps for downloading and compiling drivers. Make and make install succeed and create the .ko file somewhere. I reboot, activated my wireless card in the bios, started fedora and do
# modprobe rt2860sta
no visible problem so far.

but after i did :
# iwlist scann
and here is what it awnser me :
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
ra0 Interface doesn't support scanning : Network is down
pan0 Interface doesn't support scanning.

Well i was asking for help at first but a friend gave me the solution so I post it for others newbe like me :

simply do a
# ifconfig ra0 up

Thanks again for your help !
I'm going to try now how to fix the hotkeys problems ;)

BlackWolf
29th August 2008, 08:10 PM
First post on these forums, but here goes.

I too, am attempting to get the wireless connection working with Fedora 9. However, I do not have an external network adapter. So, I cannot access the internet, and therefore, cannot install gcc or any other required packages.

I have the .ko file which I have compiled on a seperate, Ubuntu laptop. Is there a way to manually install the .ko file once I have the compiled driver, without the need for additional packages? I'm assuming this is a long shot, but if it's possible, it would solve all my issues.

Also note that this is an installation from the Live CD image, installed from a USB key.

Thanks in advance for any replies to this post.

Nicoal
29th August 2008, 10:08 PM
Well Blackwolf I'm not an expert but i'm fairly sure of these :

copy the .ko file on your eeepc and in the directory do a "modprobe file" (without the .ko extension).

/!\ But you should fix your ethernet problem first by upgrading your kernel (the atl1e driver is include in recent version). Because you can't use a .ko file that is compile by a different kernell version. So my advice is : fix your ethernet problem then fix wireless using internet connection (wich much easier) !

You'lle find the rpm of the kernel there : ftp://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/updates/9/i386/kernel-2.6.25.14-108.fc9.i686.rpm

copy it to yor eeepc and do a
# rpm -ivh kernel-2.6.25.14-108.fc9.i686.rpm

personaly i had an error with this : iwl4965-firmware < 228.57.2 entre en conflit avec kernel-2.6.26.2-14.fc9.i686" (you gess it i'm not english ;))

if you have the same simply do this :
$ su -lc 'rpm -e iwl4965-firmware'
(thanks to cenomanien, a french fedora user)

And try to install the kernell again.
It should work !

Hope I helped !

BlackWolf
29th August 2008, 10:16 PM
Excellent, thank you. I'll be sure to give this a try.

Is there a particular directory I should save the .ko file in? Previously with Ubuntu, it was in the /lib/modules/2.6.24xxxxxxxxx/kernel/drivers/net/wireless directory. I presum it should go in this same directory on the Fedora install?

Nicoal
30th August 2008, 09:37 AM
Well the first time I try to fix the ethernet i tried with a ko file and I have not been told to put it in a particular place. But I know it is possible yes, but I'm not sure you have to.

Logik
30th August 2008, 09:09 PM
First let me thank you all of you for these very helpful informations !

I follow all the steps for downloading and compiling drivers. Make and make install succeed and create the .ko file somewhere. I reboot, activated my wireless card in the bios, started fedora and do
# modprobe rt2860sta
no visible problem so far.

but after i did :
# iwlist scann
and here is what it awnser me :
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
ra0 Interface doesn't support scanning : Network is down
pan0 Interface doesn't support scanning.

Well i was asking for help at first but a friend gave me the solution so I post it for others newbe like me :

simply do a
# ifconfig ra0 up

Thanks again for your help !
I'm going to try now how to fix the hotkeys problems ;)
I followed these steps exactly and now my ra0 is up and doesnt say "Network is down" but the RaLink Wifi card isnt showing in my Network or NetworkManager. When I add it, it isnt in the list.

Nicoal
31st August 2008, 03:31 PM
Well actually my wifi problem is not fix yet. Now i see networks with the command "iwlist scann" but Network Manager doesn't work. In the network interface I don't see my ralink card and i can't edit properties for the attansic card. I thought I will fix that by replacing network-manager by wicd but I have problems during the installation.

Does anybody tried wicd ?

Other ideas ?

exit
1st September 2008, 05:59 PM
Hi there. I have eee1000 and I would like to fix up my wired connection but I am having problems.
My dmesg is :
Atheros(R) L2 Ethernet Driver - version 2.0.5
Copyright (c) 2007 Atheros Corporation.
Atheros(R) L2 Ethernet Driver - version 2.0.5
Copyright (c) 2007 Atheros Corporation.
IPv6 over IPv4 tunneling driver
sit0: Disabled Privacy Extensions
My lspci:
01:00.0 Network controller: RaLink Unknown device 0781
03:00.0 Ethernet controller: Attansic Technology Corp. Unknown device 1026 (rev b0)
My ifconfig -a :
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:3408 errors:0 dropped:0 overruns:0 frame:0
TX packets:3408 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:170560 (166.5 KiB) TX bytes:170560 (166.5 KiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
and my modprobe.conf :
alias eth0 atl2

And if I run ifup eth0 I got message :
atl2 device eth0 does not seem to be present, delaying initialization.
Would you help me please to fix it up????
This is what I did :
1.I downloaded atl2-2.0.5.tar.bz2.
2.mkdir Lan
3.cd Lan
4.tar xjvf atl2-2.0.5.tar.bz2
5.cd atl2-2.0.5
6.make
7.cp atl2.ko /lib/modules/`uname -r`/kernel/drivers/net/atl2
8.vi /etc/modprobe.conf ,and there I wrote "alias eth0 atl2"
9.depmod -a
10.modprobe atl2
11.reboot

And now after reboot system-config-network and everything looks ok.
And then ifup eth0 gives me message :
atl2 device eth0 does not to be present delaying initialization .

Thank you.

wirelessmonk
2nd September 2008, 06:33 AM
Hi all. New member here. I'm having a bit of trouble with my 1000H. And by "a bit" I mean "a lot" :)

Like everyone else, I installed F9 and neither of my network interfaces worked. I downloaded the RaLink driver (v. 1.7.0) and the patch posted in this thread. I patched the sta_ioctl.c file, but I'm still getting errors. Here are the error messages I'm getting:
root@localhost 2008_0708_RT2860_Linux_STA_v1.7.0.0]# make
make -C tools
make[1]: Entering directory `/tmp/2008_0708_RT2860_Linux_STA_v1.7.0.0/tools'
gcc -g bin2h.c -o bin2h
make[1]: Leaving directory `/tmp/2008_0708_RT2860_Linux_STA_v1.7.0.0/tools'
/tmp/2008_0708_RT2860_Linux_STA_v1.7.0.0/tools/bin2h
cp -f os/linux/Makefile.6 /tmp/2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/Makefile
make -c /lib/modules/2.6.25-14.fc9.i686/build SUBDIRS=/tmp/2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux modules
make: *** /lib/modules/2.6.25-14.fc9.i686/build: No such file or directory. Stop.
make: *** [LINUX] Error 2



Any idea what the problem might be?

thanks!

Nicoal
4th September 2008, 07:52 AM
Hi all. New member here. I'm having a bit of trouble with my 1000H. And by "a bit" I mean "a lot" :)

Like everyone else, I installed F9 and neither of my network interfaces worked. I downloaded the RaLink driver (v. 1.7.0) and the patch posted in this thread. I patched the sta_ioctl.c file, but I'm still getting errors. Here are the error messages I'm getting:
root@localhost 2008_0708_RT2860_Linux_STA_v1.7.0.0]# make
make -C tools
make[1]: Entering directory `/tmp/2008_0708_RT2860_Linux_STA_v1.7.0.0/tools'
gcc -g bin2h.c -o bin2h
make[1]: Leaving directory `/tmp/2008_0708_RT2860_Linux_STA_v1.7.0.0/tools'
/tmp/2008_0708_RT2860_Linux_STA_v1.7.0.0/tools/bin2h
cp -f os/linux/Makefile.6 /tmp/2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/Makefile
make -c /lib/modules/2.6.25-14.fc9.i686/build SUBDIRS=/tmp/2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux modules
make: *** /lib/modules/2.6.25-14.fc9.i686/build: No such file or directory. Stop.
make: *** [LINUX] Error 2


Well I had the same problem and I just created the directory needed. You'll see the directory used is actually a symbolic link but the destination directory doesn't exist. Just create it.

izzybr
7th September 2008, 01:39 AM
@ hdp & masta

Thanks to both of you. Just got my 1000h and got everything working faster than I thought

SgtBower
8th September 2008, 03:28 AM
Great How-to guys!!! It worked for me once, but now I can't duplicate it.

I had this card working under Ubuntu and then under a trial install on a backup hard drive with F9. I much prefer Fedora and thought it would be an easy thing to make a virgin install and follow the directions again . . .boy was I wrong.

I followed masta's steps exactly as you will see, but I'm getting the same "Make" failure as described a couple posts up. At the end of the terminal window you will see that I went to the required directory to manually make the "build" directory as advised above, but it's already there (in red type if that means anything.

I've already run the recommended "Yum" updates above with no luck and am currently running a full system update since this is a virgin install. Any ideas as to what I'm missing?

[andy@localhost ~]$ su --login
Password:
[root@localhost ~]# pwd
/root
[root@localhost ~]# mkdir build
[root@localhost ~]# cd build
[root@localhost build]# wget http://www.ralinktech.com.tw/data/drivers/2008_0708_RT2860_Linux_STA_v1.7.0.0.tar.bz2
--2008-09-07 21:02:19-- http://www.ralinktech.com.tw/data/drivers/2008_0708_RT2860_Linux_STA_v1.7.0.0.tar.bz2
Resolving www.ralinktech.com.tw... 192.72.83.242
Connecting to www.ralinktech.com.tw|192.72.83.242|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 472698 (462K) [application/octet-stream]
Saving to: `2008_0708_RT2860_Linux_STA_v1.7.0.0.tar.bz2'

100%[======================================>] 472,698 95.3K/s in 5.0s

2008-09-07 21:02:26 (91.5 KB/s) - `2008_0708_RT2860_Linux_STA_v1.7.0.0.tar.bz2' saved [472698/472698]

[root@localhost build]# bunzip2 2008_0708_RT2860_Linux_STA_v1.7.0.0.tar.bz2
[root@localhost build]# tar xvf 2008_0708_RT2860_Linux_STA_v1.7.0.0.tar
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/2860_rtmp_init.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/action.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/ba_action.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/cmm_data.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/cmm_data_2860.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/cmm_info.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/cmm_sanity.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/cmm_sync.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/cmm_wpa.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/dfs.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/eeprom.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/md5.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/mlme.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/netif_block.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/rt2860.bin
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/rtmp_init.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/rtmp_tkip.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/rtmp_wep.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/common/spectrum.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/action.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/aironet.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/ap.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/chlist.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/dfs.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/firmware.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/leap.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/link_list.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/md4.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/md5.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/mlme.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/netif_block.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/oid.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/rt2860.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/rt28xx.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/rtmp.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/rtmp_ckipmic.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/rtmp_def.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/rtmp_type.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/rt_ate.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/rt_config.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/rt_linux.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/spectrum.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/spectrum_def.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/include/wpa.h
2008_0708_RT2860_Linux_STA_v1.7.0.0/iwpriv_usage.txt
2008_0708_RT2860_Linux_STA_v1.7.0.0/Makefile
2008_0708_RT2860_Linux_STA_v1.7.0.0/os/
2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/
2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/2860_main_dev.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/config.mk
2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/Makefile.4
2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/Makefile.6
2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/Module.symvers
2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/rt_ate.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/rt_linux.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/rt_main_dev.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/rt_profile.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/sta_ioctl.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/README_STA
2008_0708_RT2860_Linux_STA_v1.7.0.0/RT2860STA.dat
2008_0708_RT2860_Linux_STA_v1.7.0.0/sta/
2008_0708_RT2860_Linux_STA_v1.7.0.0/sta/aironet.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/sta/assoc.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/sta/auth.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/sta/auth_rsp.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/sta/connect.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/sta/dls.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/sta/rtmp_data.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/sta/sanity.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/sta/sync.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/sta/wpa.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/tools/
2008_0708_RT2860_Linux_STA_v1.7.0.0/tools/bin2h
2008_0708_RT2860_Linux_STA_v1.7.0.0/tools/bin2h.c
2008_0708_RT2860_Linux_STA_v1.7.0.0/tools/Makefile
[root@localhost build]# cd 2008_0708_RT2860_Linux_STA_v1.7.0.0
[root@localhost 2008_0708_RT2860_Linux_STA_v1.7.0.0]# cd os
[root@localhost os]# cd linux
[root@localhost linux]# cp sta_ioctl.c sta_ioctl.c.orig
[root@localhost linux]# pwd
/root/build/2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux
[root@localhost linux]# cp /home/andy/Download/sta_ioctl.patch /root/build/2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux
[root@localhost linux]# patch sta_ioctl.c sta_ioctl.patch
patching file sta_ioctl.c
[root@localhost linux]# ls
2860_main_dev.c Makefile.6 rt_linux.c sta_ioctl.c
config.mk Module.symvers rt_main_dev.c sta_ioctl.c.orig
Makefile.4 rt_ate.c rt_profile.c sta_ioctl.patch
[root@localhost linux]# gedit config.mk
[root@localhost linux]# make
make: *** No targets specified and no makefile found. Stop.
[root@localhost linux]# cd ..
[root@localhost os]# cd ..
[root@localhost 2008_0708_RT2860_Linux_STA_v1.7.0.0]# make
make -C tools
make[1]: Entering directory `/root/build/2008_0708_RT2860_Linux_STA_v1.7.0.0/tools'
gcc -g bin2h.c -o bin2h
make[1]: Leaving directory `/root/build/2008_0708_RT2860_Linux_STA_v1.7.0.0/tools'
/root/build/2008_0708_RT2860_Linux_STA_v1.7.0.0/tools/bin2h
cp -f os/linux/Makefile.6 /root/build/2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/Makefile
make -C /lib/modules/2.6.25-14.fc9.i686/build SUBDIRS=/root/build/2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux modules
make: *** /lib/modules/2.6.25-14.fc9.i686/build: No such file or directory. Stop.
make: *** [LINUX] Error 2
[root@localhost 2008_0708_RT2860_Linux_STA_v1.7.0.0]# uname -r
2.6.25-14.fc9.i686
[root@localhost 2008_0708_RT2860_Linux_STA_v1.7.0.0]# uname -a
Linux localhost.localdomain 2.6.25-14.fc9.i686 #1 SMP Thu May 1 06:28:41 EDT 2008 i686 i686 i386 GNU/Linux
[root@localhost 2008_0708_RT2860_Linux_STA_v1.7.0.0]# cd /lib/modules/2.6.25-14.fc9.i686
[root@localhost 2.6.25-14.fc9.i686]# ls
build modules.alias modules.dep modules.isapnpmap modules.order modules.symbols updates
extra modules.block modules.ieee1394map modules.networking modules.pcimap modules.usbmap vdso
kernel modules.ccwmap modules.inputmap modules.ofmap modules.seriomap source weak-updates
[root@localhost 2.6.25-14.fc9.i686]# cd build
-bash: cd: build: No such file or directory
[root@localhost 2.6.25-14.fc9.i686]#

SgtBower
8th September 2008, 05:09 AM
I'm not sure what the problem was, but as soon as I did the full update and went to the newest install, Make compiled and installed the driver without any problems. I notice that Nicoal is using the same kernel version that I was (2.6.25-14). 2.6.25-108 seemed to cure it immedietly.

Nicoal
9th September 2008, 08:02 AM
Well that is what I was going to say : try to upgrade your kernel !

izzybr
10th September 2008, 02:28 AM
hdp -
I used your scripts for the button setup, and I'm pretty sure I followed what you wrote to a T, but the only buttons that work are screen darker/brighter.
Any ideas?

hdp
10th September 2008, 07:16 PM
Do you see anything in /var/log/messages when pressing the buttons? Have you make sure apcid is started?

hotdog
11th September 2008, 08:02 AM
Thanks to all the helpful posters in this thread I've now got the new Eee PC 901 that my employers got me at the end of last week pretty much working with Fedora 9 :)

A handy tip that I haven't seem mentioned anywhere yet is to install lock-keys-applet. This is a panel applet to display the status of caps-lock, num-lock and scoll-lock (the last doesn't seem to work though), very helpful on Eee PCs without caps-lock LEDs, especially when entering passwords! It's in the standard Fedora 9 repository, but isn't installed by default. Just 'yum install lock-keys-applet' (or the equivalent) then add it to your panel.

RJFUatHOME
11th September 2008, 11:35 PM
I read thru this thread and it seems that most stuff is working for an Eeepc 1000/Linux machine hardware-wise but is Fedora 9 or EeeDora gonna include everything to get the 901 and 1000 machines functional on default install? I'd really rather have repos to hit for easy update and links to Livna for anything non GNU that I need to update on a regular basis.

So far I GNU-ed the default Xandros image as best I could customized tab images usinfgGIMP, replaced Nod32 with Clam from Debian Volitile and updated to the lastest Iceweasel to put FF at a current level, using links to keep default scripts working and uninstalled most proprietary apps - including most google and adobe stuff, with no open ports so a firewall is a secondary concern. But it would be nice to have a complete Fedora replacement for this new hardware. I'd switch in a heartbeat!

I've been playing with the bootable EeeDora image on SD and so far GUI wise and potential minimal install wise it's got great default system stuff and is fun to play with but I don't want to wipe out my SSD's customized image unless I know I got an OS with repos that support all hardware to hit on occasion and stay current. Any chance Fedora 9 or maybe 10 includes an easy install?

nicubunu
12th September 2008, 06:41 AM
You can try a Fedora 9 or in a few days Fedora 10 Beta on a bootable USB stick / SD card. *If* you are happy with it, then you can install to SSD - I am running Rawhide on my 1000h and I am quite happy with it (except wireless).

izzybr
14th September 2008, 01:15 AM
I got it. acpi was on but i hadn't chmod'ed the shell scripts.

does yours sleep when closing the lid?

Nicoal
19th September 2008, 06:51 PM
I now have all the special keys working apart from Fn+F6 (which I think is for toggling the performance settings) and the second silver button on the top (to change the resolution of the LCD panel?). This is based upon http://fedoraproject.org/wiki/EeePc

The conf file goes in /etc/acpi/events and the two shell scripts (make sure you take .txt off the end and make them executable) go in /etc/acpi/actions.

If you want the monitor manipulations to work make sure you run the xhost commands listed on the wiki.

In eeepc-hotkeys.sh change the two "su huw ........." lines so that huw is the username to run the programs as (and change firefox and thunderbird to something else, if you want the buttons to do something else).

This seems to work OK, but occasionally acpid seems to crash and needs restarting before it responds to key presses again. Also Fn+F5 can be a bit unpredictable, but that could be to do with the monitor that I was plugging it.

None of the actions has an osd, although http://code.google.com/p/eee-osd/ looks interesting, It appears to be based on Asus source for the 701, to go with the ACPI driver. I was wondering if there was a newer version of this of the 901/1000, but I have not been able to find any Asus source for the 901/1000.
Hi HDP and everybody !

Thanks to you I have managed to activate the special hotkeys ! Thanks a lot ! (well wifi also and that's brilliant !)
But I've one problem more : when my eeepc get out of sleep mode I can't set brightness down. Do you have the same problem ?

masta
19th September 2008, 08:03 PM
Hi HDP and everybody !

Thanks to you I have managed to activate the special hotkeys ! Thanks a lot ! (well wifi also and that's brilliant !)
But I've one problem more : when my eeepc get out of sleep mode I can't set brightness down. Do you have the same problem ?


I experience the issue, but I can tell you that reducing the brightness does in fact cause the setting to change some where, as a later reboot will experience reduced brightness.

Nicoal
19th September 2008, 10:01 PM
Yes actually I've notice it. But I would like to avoid rebooting each time I put my computer in sleep mode. I've tried different solutions, some software or command line programs to set the brightness but it's like the screen doesn't respond... strange !

hotdog
20th September 2008, 05:17 AM
The loss of LCD brightness control after suspend is discussed in another thread, here (http://forums.fedoraforum.org/showthread.php?t=199324). D-Caf has come up with a temporary workaround to enable you to get brightness control back.

hotdog
20th September 2008, 05:25 AM
There's also a whole bunch of useful hints and tips for getting a Fedora install working nicely in the Fedora 9 on the Eee PC 901 thread (http://forums.fedoraforum.org/showthread.php?t=199434), they'll apply to Eee PC 1000 too as internally they use all the same hardware.

Nicoal
20th September 2008, 10:43 AM
Hi Hotdog !

Thanks a lot for this links ! I admit that since I found this thread which is really good for fixing wifi issue I didn't try to do other search. Shame on me !

hotdog
20th September 2008, 01:45 PM
You're welcome :)

Search? You wouldn't even have to do that, both the threads I linked to are still on the front page of the laptop forum ;)

john.ohare
24th September 2008, 06:39 PM
Key piece of info at:
http://forums.fedoraforum.org/showthread.php?t=199434&mode=linear
Point 5 - see below:

2. Obtain the latest Ralink driver here (1.7.0.0 at the time of writing this post)
3. Unzip the driver to a directory.
4. Open the directory, and go to 2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/rt_main_dev.c
5. Look up "dev->nd_net" and replace it with "dev_net(dev)", then save the file and close it (thanx toCiaran McCreesh’s Blag for this tip).
6. Open 2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux/config.mk and change "HAS_WPA_SUPPLICANT" and "HAS_NATIVE_WPA_SUPPLICANT_SUPPORT" to "y".
7. Download hdp's patch, and copy it to 2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux
8. Open a terminal, cd to 2008_0708_RT2860_Linux_STA_v1.7.0.0/os/linux and type "patch sta_ioctl.c sta_ioctl.patch"
9. From the terminal cd to 2008_0708_RT2860_Linux_STA_v1.7.0.0 and type "make", it should finish without any errors.
10. Type "make install", then when finished, exit the terminal.
11. If you restart the Eee PC and enable the wireless from the BIOS, it should be recognized without problems.

ogetbilo
15th October 2008, 10:00 AM
Hello everyone,
I made rt2860 driver RPMS for the latest version of the drivers from Ralink (1.8.0.0).
I am going to put these RPMS to the rpmfusion repo so that everyone can benefit from them.
But we need testers to see if things work ok.
If you want to help, please see:
http://www.fedoraforum.org/forum/showpost.php?p=1092690&postcount=8
Thanks!

wirelessmonk
15th November 2008, 05:14 PM
Hi all,

Recently I wiped my 1000h and reinstalled Fedora10 (beta, for a few more days). The wired interface worked like a champ out of the box, but I'm still having issues with the wireless. I went to the Ralink site and downloaded the most recent driver (1.8.0. as mentioned by ogetbilo). I followed the directions in the included readme, but I'm not getting... any.. results.

I edited the config.mk file, and then I ran a "sudo make". Beyond this, the Readme says to copy the .ko file over to /etc/Wireless/RT2860STA/

And that's it. It doesn't say to do a make install or anything... I rebooted and still didn't get any wireless interfaces showing up with an iwconfig.

For kicks and giggles, I tried a make install. That just seemed to copy the ko file over into the directory mentioned above.

I haven't tried the patch as it was written for a different version of the driver. Has anyone else reported success with the 1.8.0 driver? If so, how did you get it to work?

Thanks!

Magnus G
16th November 2008, 09:52 AM
RPMfusion now has precompiled rpms of rt2860 v1.8.0 for F10, so just add the RPMfusion repo and install the rt2860 and kmod-rt2860 packages.

wirelessmonk
16th November 2008, 05:09 PM
Actually, I don't think that's quite the case. I enabled the rpmfusion repositories per their configuration page, but yum is unable to get to any of the mirror sites listed in the repo. I checked via a browser and confirmed that none of the mirrors seem to have a directory for f10. The directory structure up until that point is fine, but only directories for F8 and F9 exist.

I would have tried installing the fc9 version, but the mirror doesn't have the dependencies for my kernel version (2.6.27.5-109).

Magnus G
16th November 2008, 07:31 PM
Ah! It's still the development branch (rawhide) but the rpms are now tagged f10.

So follow the instructions for adding the rpmfusion-rawhide repo and you should find the packages you need.

If not, the rt2680 rpm for 2.6.27.5-109 can be found here:
http://download1.rpmfusion.org/free/fedora/development/i386/os/kmod-rt2860-2.6.27.5-109.fc10.i686-1.8.0.0-1.fc10.5.i686.rpm

wirelessmonk
17th November 2008, 02:11 AM
Hmm yeah, that didn't work out so well either... :)

I added the rawhide repo's, but it's the same issue with them. I run a yum update and can't connect to any of the sites. So I tried navigating to the link you gave to dl and install the package "by hand". I downloaded the rt2860 package and tried to install. It said that kmod-rt2860-1.8.0.0-1 was a dependecy. OK, no problem. I download that package and try to install it. It tells me that kmod-rt2860-2.6.27.5-109... is a dependency. Ok, I download that package and try to install. Still no luck. It tells me that the previous two packages are dependencies...? Now I'm really confused. :)

Magnus G
17th November 2008, 01:40 PM
Hmm, I don't know why you can't connect to any of the sites, but the "circle dependancy" should be solved if you install all the packages in the same rpm command.

wirelessmonk
21st November 2008, 03:17 AM
For some reason I was never able to install this by integrating all three packages into one rpm command. However, as of today, the rawhide mirrors work fine. A yum install rt2860 got all three packages. I rebooted and wireless works great now. Thanks Magnus G for all your help!!

cellphone-china
26th November 2008, 07:11 AM
How about this kind MINI laptop?

Quasar8000
2nd December 2008, 08:43 AM
I made an updated tutorial for installing Fedora 10 on the Eee PC 901/1000, it can be found here (http://forums.fedoraforum.org/showthread.php?t=206114) :)

Digras Photos on Instagram - Kutaisi Travel Photos on Instagram - Hoskote Travel Photos