Welcome, Guest. Please login or register.
Did you miss your activation email?
Tuesday 19 November 2024, 08:29:38 am

Login with username, password and session length

Visit the Official Endian Reference Manual  HERE
14258 Posts in 4377 Topics by 6515 Members
Latest Member: hulteends
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  Hardware Support
| | |-+  2.3 Developement RPMS please.....
0 Members and 2 Guests are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: 2.3 Developement RPMS please.....  (Read 39026 times)
edgeconsults
Jr. Member
*
Offline Offline

Posts: 9


« on: Friday 30 October 2009, 09:07:13 pm »

After several hours of testing i realized 2.3 is awesome!  but one problem..  NO DEVEL RPMS?  yup i can't find them anywhere.  2.2rc3 had devel rpms so you could compile your own drivers.  unfortunatly for us techies that like to use bleeding edge hardware we can't use 2.3 because it doesn't support new hardware and we can compile our own drivers from source.

can some one please post 2.3 devel rpms so we can compile our own drivers from source?Huh

for example r8168B v2.0 is not compatible with either 2.2 or 2.3 but atleast in 2.2 we have the ability to install the devel rpms so we can compile our own drivers from source.

At first the realtek r8168B v2.0/8111C works but after a few reboots the driver fails and you get random errors with the SSL cert and then finally the DHCP server quits and then everything goes to hell.

If you are experiencing these issues please post so we can hopefully get some good support on the new release of endian.

thank you

Edwin Solares
Desperatley waiting for devel source rpms......
it would make a good birthday present since today is my birthday too bad i haven't slept trying to get 2.3 to work on new hardware... o well back to 2.2 for now....
Logged
mrkroket
Hero Member
*****
Offline Offline

Posts: 495


« Reply #1 on: Saturday 31 October 2009, 03:53:42 pm »

I'm interested on that driver. I think you could make a virtual machine, install 2.2, install 2.2 rpms and compile.
Once compiled, I imagine it fits perfectly on 2.3.

You'll have a clean 2.3 and a testbench virtual 2.2 for test and debugs.
Logged
den64
Full Member
***
Offline Offline

Posts: 28


« Reply #2 on: Monday 02 November 2009, 07:56:45 am »

I hope we do get the devel packages for 2.3 soon,, i had to wait quite some time for 2.2 last time.
Logged
edgeconsults
Jr. Member
*
Offline Offline

Posts: 9


« Reply #3 on: Tuesday 03 November 2009, 03:17:31 pm »

yeah on using 2.2 to compile a driver did not work since the kernel is different and so are the binary sources among other things.  so it's no surprise when i tried that first it only caused the machine to completely not function.

the only way is to get the development rpms and compile the driver for 2.3.

2.3 does not support 8111C.

it may boot fine at first but after several installs your box will quit.
Logged
edgeconsults
Jr. Member
*
Offline Offline

Posts: 9


« Reply #4 on: Tuesday 03 November 2009, 03:20:31 pm »

i did however notice that endian is based off of centos.  as explained here:

http://distrowatch.com/?newsid=05731
Logged
mrkroket
Hero Member
*****
Offline Offline

Posts: 495


« Reply #5 on: Wednesday 04 November 2009, 02:38:49 am »

Sorry to hear that 2.2 has different kernel.

I have that NIC:
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
So far it works fine, 1Gbps full duplex with VLAN support. I have done some reboots and still works well. Do you think it can fail?

I think it uses the /lib/modules/2.6.22.19-72.e18/kernel/drivers/net/r8169.ko.gz driver. I'm not very fond of that linux stuff.
Logged
edgeconsults
Jr. Member
*
Offline Offline

Posts: 9


« Reply #6 on: Friday 06 November 2009, 06:27:57 pm »

yeah actually mine did fail.  i worked fine up until i shut it down.

after that i installed a few more time in a few different boxes with same motherboard.

after a few reboots the system was unresponsive via web gui or ssh.

the dhcp server also was not working.  i tried pinging the endian box and nada.

i'm surprised you have 8111/8618B and you are still functional.

have you tried enabling any of the other features?

what motherboard are you using?



Logged
edgeconsults
Jr. Member
*
Offline Offline

Posts: 9


« Reply #7 on: Monday 09 November 2009, 05:27:44 pm »

i found the issue tracker for the bin utils, headers and make devel rpms.

http://bugs.endian.it/view.php?id=2302

Logged
Mondo1287
Jr. Member
*
Offline Offline

Posts: 3


« Reply #8 on: Saturday 14 November 2009, 08:13:09 am »

So if you need custom kernel modules, is the only current option to run EFW 2.2?  Are they trying to cripple the community version by leaving out the devel RPMS? 
Logged
robdyke
Jr. Member
*
Offline Offline

Posts: 2


« Reply #9 on: Wednesday 18 November 2009, 07:07:22 am »

Another voice for the Dev tools for 2.3. I'd like to add support for the Agere et131x network cards. Without the tools I am unable to do so.

After some searching I discovered that someone had a problem with lack of support for these cards in 2.2 ( http://old.nabble.com/New-PCI-e-NICs-not-supported-p17554165.html ) I have similar output on my 2.3 installation here that I've just tested today.
Logged
WanWizard
Jr. Member
*
Offline Offline

Posts: 3



« Reply #10 on: Wednesday 18 November 2009, 07:23:29 am »

Make that plus one.

I need to install Hyper-V's linux extensions, I'm now running with legacy NIC's, which is so slow that I have to bin Endian if I can't solve this quickly...
Logged
edgeconsults
Jr. Member
*
Offline Offline

Posts: 9


« Reply #11 on: Monday 22 March 2010, 03:31:44 pm »

I am stunned and astonished that to date there has been no effort to release devel rpms.  If we are unable to get headers and kernel dev and install make what is the point of releasing 2.3 when you have a limited amount of hardware you can use it on.

I think this is ridiculous....
Logged
lribeyre
Jr. Member
*
Offline Offline

Gender: Male
Posts: 6


WWW
« Reply #12 on: Monday 12 April 2010, 08:51:45 pm »

This is very annoying ...  Cry

changed IPCOP for Endian for several purpose : (Hardware compatibility, features - QOS, VPN et more ...- ) and i have lots of issues with 2.3 (IPSEC crash that reboot Endian box or cant add NIC PCI-E -> lack of driver)

I can wait the next 2.3.1 release regarding the IPSEC issue; but at last, provide us the "Devel package" .. for the Hardware purpose.

Logged

System Engineer

Activlan - France
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.141 seconds with 19 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com