Hardy Heron

[potatoehead64]

I've just heard the the latest Ubuntu version (Hardy Heron..... [phew... managed to say that without spoonerising the words! ] has been officially been released for general use and a friend has given me a copy on disk.
Now..... before I go intstall/upgrade from Gutsy Gibbon, are there any conflict issues with PlaneShift that anyone knows about? Has anyone or is anyone running PlaneShift under Hairy...... oops ...... I mean Hardy Heron already without problems? The last think I want to do is install this and then find I can't play my very favourite game.

Would be interested any feedback.

Marty
IC = Marthron Decksar

[Akashani]

I have Hardy Heron and I have absolut no problems with PlaneShift 

[Rizin]

Same here, no issues.

[Kemex]

Great to read that, cause today i  will broke my Vista's partnership (  )and end my little feud with Linux (    ) and i will install Xubuntu 8.4.   

[Lanarel]

I spent most of yesterday trying to get my wifi working again No luck so far.

[Kemex]

May can i help with.. Just answer the follow:

 -What kind of WiFi Card do you Have
 -PC/Laptop Model
- I asume that you are you Hardy Heron

Also will be insteresting know your PC/Laptop archictecture.

[Fesek Basidey]

From the people I have spoken to there seems to be no problems with PS in 8.04 and it works great for me

[Velh Krome]

*buntu? sudo! 

[Lanarel]

May can i help with.. Just answer the follow:

 -What kind of WiFi Card do you Have
 -PC/Laptop Model
- I asume that you are you Hardy Heron

Also will be insteresting know your PC/Laptop archictecture.

hehe, this is my old PC, far below specs for Hardy Heron (500Mhz pentium3 I think maybe 4, 128Mb memory). I use it mainly as a network server (for music and such) and to run a psserver for testing. It cannot handle npcclient (>750Mb) or psclient (16mb voodoo card does give really funny images ).

The wifi card is a sitecom wl-114 (or is it 115). Anyway, it has the rt61 ralink chipset, for which I already found several how-to's. It has been trouble since ever. I had it running in feisty. with WPA (which seems to be the problem), but requiring doing ifdown; ifup until it had encryption (usually after doing this 100 times). But when it worked, it worked for months. I upgraded to gutsy few weeks ago, and it did not work, until I opened the network manager, fiddled around a bit, gave up, had a cup of coffee, and then it worked. But now I am stuck again after upgrading to Hardy Heron. I am trying to compile the driver again now, but even after installing the linux-headers, it still complains "do not know how to make target 'modules'" or something. Google does not help anymore (going around in circles with all how-to's referring to each other), since the error seems to occur when you do not have the linux-headers, but they are really there now.

If you can help me solve this (and get the noisy PC back to the other room, where my UTP cable does not reach) I would be really grateful


You would think if they want to convince people that Ubuntu is as useful as windows, they would not require you to build your own drivers

[Prolix]

You may be having trouble with the sources. I do not know about ubuntu in particular but I have seen strange things like sources not being updated when the kernel is, several sets of sources -- stripped, unstripped, etc. I think I had a problem with that in ubuntu once, it is supposed to just work so they make it difficult to compile your own drivers or recompile the kernel. That is my impression, anyway,  although it seems now that the major distros are all going in that direction.

[Kemex]

Well as far as i know, if u are sure that you've just downloaded the latest kernel headers..
do you have made the simbolik link to those headers?

im refers to /usr/src/linux-(header version)-(architecture) to /usr/src/linux ? // Replace (Header) and (archictecture) with your specs. you can obtain that info with  uname -v

most drivers out there uses that location to be more compatible with all distros out there.
Anyway, i will try to give you more info later (if that doesnt help), since im not currently in a  Linux Box.

[Lanarel]

im refers to /usr/src/linux-(header version)-(architecture) to /usr/src/linux ? // Replace (Header) and (archictecture) with your specs. you can obtain that info with  uname -v

that directory contains files since I installed the linux-header files. When I do 'sudo make all' in the install dir for the driver, it goes to /lib/modules/2.6.24-16-386/build (which did not exist first, but I created it), and then it complains:
 *** No rule to make target `modules'.  Stop.

So it seems this build directory was supposed to be containing something
I know I had this problem before, but have no clue what I did to solve this.

[Kemex]

Damm.. im out of shape with Linux Boxes ( i had a feud with    )
Such errors are related with.:

• Invalid header configurations.
• Dirty sources ( you need to do a "make clean" before try to compile them)
• ldconfig  library dependences.
• make deps at the kernel sources dir. As far as i know ubuntu doesnt need it, but who knows   

Really all that i can say is speculation since i havent right now a linbox... i will try later when i get one.

[Lanarel]

I am trying to get a driver build from http://rt2x00.serialmonkey.com
Somewhere I found that such a build directory should be a link:
sudo ln -s /usr/src/linux-headers-2.6.24-16-386 build
did seem to help a bit, but then I get:
make[1]: Entering directory `/usr/src/linux-headers-2.6.24-16-386'
scripts/Makefile.build:46: *** CFLAGS was changed in "/home/myname/tmp/2007_1210_RT61_Linux_STA_v1.1.2.0/Module/Makefile". Fix it to use EXTRA_CFLAGS.  Stop.

I did not get this before.
Also, according to the serial monkey site I may have to use another version of driver (the legacy driver), but I did get it working in Gutsy without using that one (which I did download but not unpack). The legacy driver gives compile errors:
make[2]: *** No rule to make target `arch/x86/kernel/asm-offsets.c', needed by `arch/x86/kernel/asm-offsets.s'.  Stop.

header versions seem to be OK (apt-get says they are up to date), make clean did not help, ldconfig does not help me yet

[ThomPhoenix]

Is it a wireless? If so you could use ndiswrapper and wpasupplicant. Works for me on Hardy.