Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: ameier on January 27, 2007, 01:42:35 PM
-
hallo to all SME freaks out there......
i´ve just get a new jetway mini-itx board with dual realtek 8169sc lan
onboard. my problem is that the sme release 7.0 and 7.1 could not
detect the lan devices. only under knoppix 5.1 everything works fine.
who could help me out.........pls notice i´m a bloody linux beginner
and my english is not the best !
thx
andreas
-
hallo to all SME freaks out there......
i´ve just get a new jetway mini-itx board with dual realtek 8169sc lan
onboard. my problem is that the sme release 7.0 and 7.1 could not
detect the lan devices. only under knoppix 5.1 everything works fine.
who could help me out
Hi Andreas,
We use the unmodified CentOS 4.4 kernel. If the hardware isn't detected by the kernel, it isn't supported. It is possible to install additional drivers, but I strongly recommend against that as it will cause pain with each kernel upgrade, and you can expect a few of those each year.
........pls notice i´m a bloody linux beginner
and my english is not the best !
Your English is excellent. Oh how I wish my German were that poor :-)
-
hallo to all out there again....... :)
after many hours surfing the web i found some tipps that should fit the problem. some freaks wrote that the 8169sc that is included in the sme
is very outdatet and buggy. so what think you about to compile this module again ? and there´s the next problem. where could i get the
right kernel sources and all the compiler stuff.....? my first try failed :(
thx
Andreas
-
SME gets it's kernels directly from CentOS which in turn gets them from RedHat. We do not compile our own kernels.
If there is a problem with the kernel, it needs to be fixed upstream at RedHat.
SME does not include compiling tools as they can be a security risk. If you want to try to compile a new kernel it is recommended that you install CentOS on a development machine and do it there.
-
well, i´ll try it. the huge download ist just running. witch CD should be taken for any kernel tests.........the workstation with 4 cd´s or the server version that comes only with 1 cd ? i download them all :)
thx
andreas
-
After buying myself 1 of the most appealing MB's for me I stumbled into a problem that seems to be present for more people then only myself.. Hence the fact that I'm placing a reply here..
I solved the problem tho, and I can say... it wasn't even that hard.
First I have to say that the problem is partly created by the fact that the kernel isn't able to detect what VIA processor this mainboard is using and will be fixed in the 2.6.20 (at least, that's what Dave Jones from RH assured me)
Due to the fact that the current kernel doesn't recognize the processor it goes , weird enough, into SMP mode and from what I know it shouldn't.
So.. Before you start doing anything... Place an extra network card. (please use 1 that SME DOES recognize, RTL8139 for example) This will be obsolete later but you need it for updating and installing the proper updates & driver.
Install from the CD as a server-only (all can be changed later) and use the RTL8139.
After the reboot; start in the correct kernel and NOT the SMP, you can do that when the system boots, you have 3 seconds for it.
Once in the proper kernel it becomes easy.
You want your system up2date ofcourse so you run a "yum -y update" and let it take control for now.
After the updates you follow instructions and the system shoull reboot again. Make sure it starts in the correct kernel mode and NOT SMP.
Now you are ready to install the driver.. but you have to compile it. So you need extra libs to do so... easy too
type "yum -y install kernel-devel gcc gcc-c++"
That will install all things needed including the dependencies.
I did a reboot after all this.. but I don't think it's really needed (try for yourself)
now you have to download the driver for the RTL8169SC...there are 2 options.
1 - use the latest from realtek
2 - use a slightly older version that DOES work
because the driver 1.04 is not available anymore from realtek and I wasn't sure the link where I have found it will stay I decided to offer it from my own server. http://www.vexins.com/r1000_v1.04.tgz
The 1.05 is there too.. if you wanne try.
download the driver like so:
"wget http://www.vexins.com/r1000_v1.04.tgz"
unpack the driver
"tar -vzxf r1000_v1.04.tgz"
go into the map
"cd r1000_v1.04"
and start compiling from here with :
"make clean modules"
"make install"
and to make sure all is detected
"depmod -a"
You have a working driver now.
Shutdown your server & take the power off. Take the extra networkcard out. And start your server again.
There are 2 options now.
1 - use kudzu (and stumble into weird responses)
2 - edit manually
I did the 1st and decided the last is safest option
"mcedit /etc/modprobe.conf"
place at the end of the file the lines :
"alias eth0 r1000"
"alias eth1 r1000"
and remove the other line that is an alias to eth0 (the other nic you just took out).
Reboot the server again, wait patiently and see if all worked for you.
For me it did.
BTW: why not the 1.05 ?? Well.. it works.. but less then 5% coming thru is not good enough for me.
Regards,
Harro
-
Additional to my former story, when all works. You can remove the compiling libs to bring your system back into the same security level that you started with.
simply do :
"yum -y remove libstdc++-devel cpp glibc-kernheaders glibc-headers glibc-devel gcc gcc-c++ kernel-devel"
After that your system is restored and still running with the r1000 driver.
Harro
-
There are 2 options now.
1 - use kudzu (and stumble into weird responses)
2 - edit manually
I did the 1st and decided the last is safest option
"mcedit /etc/modprobe.conf"
place at the end of the file the lines :
"alias eth0 r1000"
"alias eth1 r1000"
and remove the other line that is an alias to eth0 (the other nic you just took out).
No, don't do that. Your changes will be removed the next time you do any system updates.
Instead, do:
config set EthernetDriver1 r1000
config set EthernetDriver2 r1000
signal-event post-upgrade
signal-event reboot
Note also that you will need to recompile your kernel module any time an updated kernel arrives with system updates.
-
Thanx Charly,
It does make sense to do it that way. Haven't thought about it at all.
And good u mentioned that the next kernel-update is installed you loose connectivity (or at least it seems most likely the driver will need a rebuild)
Had this in mind but forgot to add it to my small HowTo.
Harro
-
Confucious I would add something. Add the line install for external nic only. That way you'll avoid constant opening of your server and swaping NIC's. Just use one of theese cards as external nic and one that works stoc as internal nic. This way you can rebuild and work faster when you update your sistem.
-
I leave that option open to who wants to do it that way.
Keeping the driver-src on your system and for that matter all libs needed to compile the driver (all nicely tucked away in a corner on your harddisk) you can always rebuild the driver to your needs.
I have been reading that in kernel version 2.6.15 there is already success with loading the correct driver (or I'm mixing it up with other driver issues now, my poor memory these days :roll: )
Fact is that this matter won't always stay this way. Till the kernel has the correct information people will have to do it the way they think suits them best.
Harro
-
Said in a true Confucius manner. :D
-
many thx for the huge postings.........i´ll try all the few steps.
thx
andreas
-
And good u mentioned that the next kernel-update is installed you loose connectivity (or at least it seems most likely the driver will need a rebuild)
The driver will certainly need a rebuild, and you will indeed lose connectivity until that occurs.
-
now the 2 nics are still up and running. my big mistake during the first few tryouts was to forget the first step. without that man errors comes up during compile the thr r1000 driver !
here are the the complete steps for fast copy and paste with putty. let
me they thanks for all help and helpfull comments..... :)
01.) yum -y update
02.) reboot
03.) yum -y install kernel-devel gcc gcc-c++
04.) reboot
05.) wget http://www.vexins.com/r1000_v1.04.tgz
06.) tar -vzxf r1000_v1.04.tgz
07.) cd r1000_v1.04
08.) make clean modules
09.) make install
10.) depmod -a
11.) mcedit /etc/modprobe.conf
alias eth0 r1000
alias eth1 r1000
12.) config set EthernetDriver1 r1000
13.) config set EthernetDriver2 r1000
14.) signal-event post-upgrade
15.) signal-event reboot
16.) reboot
mfg
andreas
-
01.) yum -y update
02.) reboot
03.) yum -y install kernel-devel gcc gcc-c++
04.) reboot
05.) wget http://www.vexins.com/r1000_v1.04.tgz
Those reboots aren't required.
11.) mcedit /etc/modprobe.conf
alias eth0 r1000
alias eth1 r1000
12.) config set EthernetDriver1 r1000
13.) config set EthernetDriver2 r1000
Step 11 is not required.
-
Hallo CharlieBrady,
did you have any kind of problems to get the connection stable ?
i mad some test during the last few hours. sometimes the connection
just dropped........did you modifi settings such as MTU ?
any tipps and hints are welcome !
mfg
andreas
p.s.: did you use a messenger ? - for direct contact.........
-
Andreas,
I don't think Charlie has such a mainboard at hand. He's a general knowledgebase ( :roll: ) when it comes to SME.
I had no connection problems yet. BUT... honestly.. I only run the server in the evening when I'm in the mood to puzzle & fiddle with it. And at this moment a SME 6.0.1 is keeping me connected. But.... during all these hours of playing, using putty, I haven't suffered any disconnects or other weird behaviour. For the record: I still use driver r1000 version 1.04
Harro
-
Many thanks to all of you.
I was looking for a solution to have this brand new J7F4 MB, I bought begining of January from LinITX (UK), working with SME, including trying to install a rpm driver for SL44 (another Linux distro based on RHEL), or install an entire CentOS distro to compile the driver, and I was about to try with a third NIC, when I came back to Contribs.org forums to find this very smart solution.
Just to bring my small contribution to the solution, I tried to patch the source driver from Realtek (the 1.04 available on Confucius website) as indicated in this page on a Gentoo wiki (http://gentoo-wiki.com/HARDWARE_RTL8168, section TROUBLESHOOTING). With the Confucius 1.04 version I had the warning when "making clean modules", and I didn't have anymore warning with the MODULE_PARM_DESC modification in the src/r1000_n.c file.
I hope this could help.
Any news of a 1.05 working driver or do we have to wait for a new kernel fixing the bug?
DaddyTux
-
Before running the sme update (with kernel update) make sure that you installed all libs you need for compiling.
Download the working driver and keep it unpacked in a map u remember.
Then tell your machine to do the "yum update"
Now all your compile libs are also updated.
The only thing you need to do now is make sure the machine starts in the right mode (NOT smp if you have 1 processor only) and start compiling as instructed before. (with the correction from Charlie included ofcourse)
This way I didn't needed to add my extra networkcard anymore. Only needed local access to the server (keyboard & screen) to get all done.
Without too much hassle... a working server that is up2date :D
Harro
-
The only thing you need to do now is make sure the machine starts in the right mode (NOT smp if you have 1 processor only) ...
SMP should work fine no matter how many CPUs you have.
-
hi, i've tried this procedure but doesn't work...
When it tries to compile the module, get the:
make clean modules
make -C src/ clean
make[1]: Entering directory `/tmp/r1000_v1.05/src'
rm -rf *.o *.ko *~ core* .dep* .*.d .*.cmd *.mod.c *.a *.s .*.flags .tmp_versions
make[1]: Leaving directory `/tmp/r1000_v1.05/src'
make -C src/ modules
make[1]: Entering directory `/tmp/r1000_v1.05/src'
make -C /lib/modules/2.6.9-42.0.10.EL/build SUBDIRS=/tmp/r1000_v1.05/src modules
make[2]: Entering directory `/lib/modules/2.6.9-42.0.10.EL/build'
make[2]: *** No rule to make target `modules'. Stop.
make[2]: Leaving directory `/lib/modules/2.6.9-42.0.10.EL/build'
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/tmp/r1000_v1.05/src'
make: *** [modules] Error 2
[root@cube r1000_v1.05]#
[root@cube r1000_v1.05]# make install
make -C src/ install
make[1]: Entering directory `/tmp/r1000_v1.05/src'
install -m 644 -c r1000.ko /lib/modules/2.6.9-42.0.10.EL/kernel/drivers/net/
install: impossibile fare stat di `r1000.ko': No such file or directory
make[1]: *** [install] Error 1
make[1]: Leaving directory `/tmp/r1000_v1.05/src'
make: *** [install] Error 2
[root@cube r1000_v1.05]#
and now?
-
Use the 1.04 as stated.
-
no difference
-
then you didn't follow the steps as described.
You have installed the kernel-headers ??
I have done it 3 times this was on the previous kernel version. Did it 2 times on the current kernel version and tried the 1.05 aswell and all compiles well.... only the 1.05 doesn't connect properly at all.
-
I have installed all the packages demands..
u can send me the module plese?
Linux cube 2.6.9-42.0.10.EL #1 Tue Feb 27 09:32:35 EST 2007 i686 i686 i386 GNU/Linux
-
In your hotmail account. Hope it works for you.
-
tar xvf r1000.tar
r1000.ko
[root@cube net]# ls
3c59x.ko e1000 netconsole.ko r1000.tar sunhme.ko
8139cp.ko e100.ko netdump.ko r8169.ko tg3.ko
8139too.ko eepro100.ko ns83820.ko s2io.ko tlan.ko
82596.ko epic100.ko pcmcia sis900.ko tokenring
8390.ko ethertap.ko pcnet32.ko sk98lin tulip
acenic.ko fealnx.ko ppp_async.ko skge.ko tun.ko
amd8111e.ko forcedeth.ko ppp_deflate.ko sky2.ko typhoon.ko
b44.ko hp100.ko ppp_generic.ko slhc.ko via-rhine.ko
bnx2.ko ixgb pppoe.ko smc9194.ko via-velocity.ko
bonding mii.ko pppox.ko starfire.ko wireless
dl2k.ko natsemi.ko ppp_synctty.ko sungem.ko
dummy.ko ne2k-pci.ko r1000.ko sungem_phy.ko
[root@cube net]# modprobe r1000
FATAL: Error inserting r1000 (/lib/modules/2.6.9-42.0.10.EL/kernel/drivers/net/r1000.ko): Invalid module format
mmh, where is the error?
-
Good question.... I'm puzzled... Will dig into it when I'm back on the spot.
-
invalid module format????
helpppppppppp :(
i've tried the right 644 & 777 but nothing...
what depend? from the packages installed on system?
i've tried at remve the packs for compiling but nothing..
:(
i have this motheboard all in one (http://www.mini-itx.it/product_info.php?info=p14_VIA-Epia-ME6000-LVDS.html)
-
1 thing is at least needed to make it to work.
depmod -a
Don't know if this solves the problem but it certainly is needed
Harro
-
the depmode -a gives back the line..
your sme is update?
my ethernet is DLink DGE-528T
-
No wonder....
You are using another type of card. BUT... there seem to be ways to trick your kernel ( < 2.6.10) to work with this card aswell.
http://www.linux.org.za/Lists-Archives/glug-tech-0611/msg00178.html
Haven't been trying these hints myself. All I know is that the r8169.c can't be found on my test system here. The best option seems to do a hex edit of the driver.
download ftp://ftp.freshrpms.net/pub/dag/redhat/el4/en/i386/dag/RPMS/hexedit-1.2.10-1.2.el4.rf.i386.rpm
install by using "yum localinstall hexedit-1.2.10-1.2.el4.rf.i386.rpm"
and you have you hexeditor.
Harro
-
i follow the guide but the dir /usr/src/linux for edit the r8169.c not exist..
grrrrr
-
that's what I had & expected... follow the 2nd section of that guide.. with the HEXEDIT. That might be your solution. And... since I easy misread the guide...
READ CAREFULLY..
-
my ethernet is DLink DGE-528T
Do not try and modify the drivers because you'll experience blackouts (freezes without error log)!!!
I will post the bug number for reference as soon as i find it.
Edit: http://bugs.contribs.org/show_bug.cgi?id=2361
Check comment #3.
-
i have follow the guida and edit with hexeditor the module..
now the ethernet is recognized!!! the led on switch gigabit is power on at gigabit, BUT my client send files at 12000KB/s !!!
why?
dmesg |grep eth
divert: not allocating divert_blk for non-ethernet device lo
divert: allocating divert_blk for eth0
eth0: VIA Rhine II at 0xe8001000, 00:40:63:c3:8c:17, IRQ 11.
eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1.
divert: allocating divert_blk for eth1
eth1: Identified chip type is 'RTL8169s/8110s'.
eth1: RTL8169 at 0xde85e000, 00:15:e9:f0:18:0f, IRQ 10
divert: freeing divert_blk for eth1
divert: freeing divert_blk for eth0
divert: allocating divert_blk for eth0
eth0: Identified chip type is 'RTL8169s/8110s'.
eth0: RTL8169 at 0xde8e6000, 00:15:e9:f0:18:0f, IRQ 10
r8169: eth0: link up
divert: allocating divert_blk for eth1
eth1: VIA Rhine II at 0xe8001000, 00:40:63:c3:8c:17, IRQ 11.
eth1: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1.
[b]eth1: link up, 100Mbps, full-duplex, lpa 0x45E1[/b]
*bpivk* sorry, i dont understand..
-
@z3n0
I don't have any clue about this card. Can't help you more then I did.
From kernel 2.6.10 you probably can rely on a system that's no longer in need of manual help with this problem. For now we have to rely on what has been figured out already.
As already mentioned by bpivk, this could be resulting in weird behaviour. It's an UNofficial way... Don't use it on a production-server.
@bpivk :
tampering with drivers is NEVER a good thing so I don't recommend to alter all drivers you like to all ppl's here. But when the only option is to do this to make something work... it's a way..
BTW. You were using a 42.0.8 kernel that time while we are already doing 42.0.10 now. Maybe the driver is more stable now ? I hope z3n0 will keep trying it for a few days and report back about blackouts (from the server only :lol: )
-
Well i really don't care because i moved that card and i don't want it anywhere near my server. :lol:
BUT... it is a cheap card and i hope that it works for you. You'll find out that it doesn't work soon enough (had crashes on a 24-48 hour intervals).
-
bpivk the card often goes down (google translate :P)
this card = 20,10€ !!!!!!!!!!!
-
Well 20€ is cheap compared to other computer hardware. :D
But I couldn't find any good cards in my country so i had to buy this card and i had so many problems that i went to a school that had old computers and used one of those nic's (3com) and it performs like a champion. :D
DGE is now degraded to being a NIC in a MS workstation. :twisted:
-
existing other cards with chip recognized in all kernel of all distribution?
what buy?
-
Well 3com and intel NIC's are great with SME.
-
i not found, on the 3com's site, the gigabit cards..
-
AFAIK 3com doesn't make the cards anymore. I said that i got an old card from some computers at a school. :D
Go for the Intel NIC's.
-
hi, the intel it produces ethernet cards, or i must try ethernet card with intel chips?
-
this motherboard is supported from sme server?
http://www.mini-itx.com/store/?c=34#j7f4
-
From what I know (reading the forum frequently) the RTL8110 has the same problems as the RTL8169 chipset. SME Doesn't have support built in yet. It's a kernel issue and that's out of the hands of the SME dev'rs.
Harro
-
we can demand to sme community to resolve this problem?
I cannot use the sme with my dlink gigabit or buy that motherboard! :twisted:
PS: i have format the old sme and i have install a new sme 7.1 clean..
i have compiled the r1000 driver and to modprobe r1000 i don't have error..
but the gigabit's card not use that driver...
why?
-
From what I know (reading the forum frequently) the RTL8110 has the same problems as the RTL8169 chipset. SME Doesn't have support built in yet. It's a kernel issue and that's out of the hands of the SME dev'rs.
Harro
if you search with google for "realtek poor performance" you'll see that this kind of chipset is evil :twisted:
IMHO intel is far better..
Ciao
Stefano
-
i need an ethernet gigabit for my sme server..
my dlink is evil :P
what buy?
-
Hello everyone,
I have recently moved our SME server 7.1 to a new machine, based on a Jetway J7F4 Mini-ITX board with a passively cooled 1200 Mhz VIA C7 processor, CN700 chipset and dual RTL8110SC ethernet adapters onboard. Like others in this thread, I had rather a lot of problems getting SME to work with this hardware.
I played around a bit with the Realtek r1000 driver, but it made the system pretty unstable. Besides, the 2.6.9 kernel used in CentOS 4 / SME 7 doesn't handle the VIA chipset and its buggy ACPI bios very well. So in the end I decided to compile a custom 2.6.21 kernel with extra patches for the VIA C7 processor. I roughly followed this howto and made an RPM package containing the new kernel and modules: http://www.howtoforge.com/kernel_compilation_centos
It took a bit of trial-and-error to select the proper modules to get NAT and a few other things working, but since I switched to the new kernel the machine runs *a lot* faster and the RTL8110 adapters are now working just fine (with the 8169 kernel module)! Plus I now have kernel support for VIA's Padlock encryption engine, which does all the SHA and AES stuff in hardware. :-)
As soon as I have Wiki access I will write a HOWTO on how I did it, and I'll make the RPM with my kernel available as well (although note that I used a highly experimental kernel version, so it might not work for everyone).
Best regards,
Levien
-
We have been trying to compile a Realtek 1Gb NIC card. We have managed to get a r1000.ko file and it will load in the non smp kernel but is very erratic in performance. From 0.1ms to 14000ms on a LAN ping test. Also tried it from a live mephis 6.0.1 CD (2.6.15) and it was perfect so hardware and cabling are fine.
The messages log file has
"Apr 19 17:59:10 ppserver kernel: r1000: disagrees about version of symbol struct_module
Apr 19 18:15:34 ppserver kernel: r1000: disagrees about version of symbol struct_module"
Any clues? Would this message indicate a problem? A ping test to the cards own IP is also good. It is only external response that fails.
MB Gigabyte GA-945G-S3
The loading of the driver
Apr 19 13:56:24 ppserver kernel: ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 19 (level, low) -> IRQ 177
Apr 19 13:56:24 ppserver kernel: PCI: Setting latency timer of device 0000:02:00.0 to 64
Apr 19 13:56:24 ppserver kernel: divert: allocating divert_blk for eth0
Apr 19 13:56:27 ppserver kernel: eth0: Identified chip type is 'RTL8168B/8111B'.
Apr 19 13:56:27 ppserver kernel: eth0: r10001.04, the Linux device driver for Realtek Ethernet Controllers at 0x9000, 00:16:e6:38:c5:4a, IRQ 177
Apr 19 13:56:27 ppserver kernel: Realtek RTL8168/8111 Family PCI-E Gigabit Ethernet Network Adapter
Apr 19 13:56:27 ppserver kernel: Driver version:1.04
Apr 19 13:56:27 ppserver kernel: Released date:2006/07/07
Apr 19 13:56:27 ppserver kernel: Link Status:Linked
Apr 19 13:56:27 ppserver kernel: Link Speed:1000Mbps
Apr 19 13:56:27 ppserver kernel: Duplex mode:Full-Duplex
Apr 19 13:56:27 ppserver kernel: I/O Base:0x9000(I/O port)
Apr 19 13:56:27 ppserver kernel: IRQ:177
Apr 19 13:56:39 ppserver kernel: NET: Registered protocol family 5
Apr 19 13:56:42 ppserver esmith::event[4119]: expanding /etc/sysconfig/kernel
Apr 19 17:57:27 ppserver kernel: divert: freeing divert_blk for eth0
Apr 19 17:59:10 ppserver kernel: r1000: disagrees about version of symbol struct_module
Apr 19 18:15:34 ppserver kernel: r1000: disagrees about version of symbol struct_module
Apr 19 18:16:00 ppserver kernel: ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 19 (level, low) -> IRQ 177
Apr 19 18:16:00 ppserver kernel: PCI: Setting latency timer of device 0000:02:00.0 to 64
Apr 19 18:16:00 ppserver kernel: divert: allocating divert_blk for eth0
Apr 19 18:16:03 ppserver kernel: eth0: Identified chip type is 'RTL8168B/8111B'.
Apr 19 18:16:03 ppserver kernel: eth0: r10001.04, the Linux device driver for Realtek Ethernet Controllers at 0x9000, 00:16:e6:38:c5:4a, IRQ 177
Apr 19 18:16:03 ppserver kernel: Realtek RTL8168/8111 Family PCI-E Gigabit Ethernet Network Adapter
Apr 19 18:16:03 ppserver kernel: Driver version:1.04
Apr 19 18:16:03 ppserver kernel: Released date:2006/07/07
Apr 19 18:16:03 ppserver kernel: Link Status:Linked
Apr 19 18:16:03 ppserver kernel: Link Speed:1000Mbps
Apr 19 18:16:03 ppserver kernel: Duplex mode:Full-Duplex
Apr 19 18:16:03 ppserver kernel: I/O Base:0x9000(I/O port)
Apr 19 18:16:03 ppserver kernel: IRQ:177
-
We now have a module that works very well in the non smp kernel (0.02ms) but not the 2.6.9-42.0.10.ELsmp kernel. It just complains invalid kernel format. Still looking.
-
OK Solved
To compile for the smp kernel
yum install kernel-smp-devel (plus the other modules listed in this post)
Make sure you are booted to the smp kernel
expand out the r1000_v1.04.tgz
tar zxvf r1000_v1.04.tgz
cd r1000_v1.04
Edit the src/r1000_n.c file and change the
MODULE_PARM (speed, "1-" __MODULE_STRING(MAX_UNITS) "i");
MODULE_PARM (duplex, "1-" __MODULE_STRING(MAX_UNITS) "i");
MODULE_PARM (autoneg, "1-" __MODULE_STRING(MAX_UNITS) "i");
To
MODULE_PARM_DESC (speed, "1-" __MODULE_STRING(MAX_UNITS) "i");
MODULE_PARM_DESC (duplex, "1-" __MODULE_STRING(MAX_UNITS) "i");
MODULE_PARM_DESC (autoneg, "1-" __MODULE_STRING(MAX_UNITS) "i");
make clean modules
If no errors then just do make
make
We found we had loading issues with make install command. Ping results on LAN 0.2ms
Have not tried ver 5 in this pattern yet.
Good luck
-
hi all,
Thanks for your how-to!
I have a more general question:
wanna use *CDemu* to mount a CUE/BIN file (similar to ISO). The author's homepage says it needs a kernel module to be compiled.
Would this module stop working with each kernel update?
-
Hi
Can report the 1.0.4 r1000.ko file works fine in the standard 7.1 and 7.1.3 kernels. The only problem en counted was the file was not automatically updated to the new kernel 2.6.9-42.0.10.EL... from 2.6.9-42.0.3.EL.... A simple copy worked. NB 2 .ko files are required for the one for each kernel (smp and std)
Motherboard used Gigabyte GA945-S3 with Core2 Duo CPU. Note this board still uses a ICH7 chipset so is supported by the current kernels.
-
I've written a HowTo on compiling your own kernel for SME 7.x on a Jetway J7F4 series MiniITX board with dual RTL8110SC gigabit ethernet adapters on-board. It's on the contribs.org wiki:
http://wiki.contribs.org/JetwayMiniITX
I also have a ready-made RPM containing the kernel. I'll put it online and add a 'For the impatient' section to the HowTo as soon as I've had a chance to update it to a 2.6.21 stable kernel. (Anyone who's in a hurry and doesn't mind running 2.6.21-rc5-git1, just let me know and I'll send you my current RPM).
-Levien
-
Hello,
I have currently a mtherboard J7F4 with the two gigabyte lan revision 3 bios A04.
I would really enjoy to test your ready rpm kernel as i didn't manage to do it for the first try.
furher more i have my network working with r1000 but never with r8169 under SME kernels
-
Just send me an e-mail at levien AT scum dot org, and I'll mail you the URL. (bandwidth is a bit limited, so I'd rather not post it on the forum)
The kernel I compiled is still not the final version, but our server has been running it without problems for about 3 months now. Just make sure that your board temperature stays below 50 degrees Celsius, as the VIA chipset on board the J7F4 (and many newer Epia boards) seems to have serious stability issues when it gets warmer than that...
Best regards,
Levien
-
Hello, thanks to your how to I have compiled a kernel for my J7F4..but
-my networks card still does not works with r8169 drivers a dhcp ip is attributed to the wan NIC but nothing goes trough
-unable to compile the R1000 v1.06 under 2.6.21-rc5 (it worked just fine under 2.6.9 kernels
- thanks to the new kernel i am able to reboot (with 2.6.9 kernel if no keyboard PS2 was present the system hang up before reboot)
- no more auto creation of the folder in media for removable device is this udev thing ?
the most enoying thing is about the NIC ..... I saw some information on the net about windows that disable the network card, but no windows on the machine and it works just fine with the r1000 driver but older kernel...
JPP
-
Hello, thanks to your how to I have compiled a kernel for my J7F4..but
-my networks card still does not works with r8169 drivers a dhcp ip is attributed to the wan NIC but nothing goes trough
Sounds like a configuration issue. Which drivers are loaded? Did you set up the correct driver in the SMB config database? Or perhaps both the r1000 and the r8169 get loaded? Do you get any error messages in dmesg?
-unable to compile the R1000 v1.06 under 2.6.21-rc5 (it worked just fine under 2.6.9 kernels
Yes, apparently the new Realtek driver doesn't yet compile with newer kernel versions (> 2.6.18 or so). You could try the 1.05 or 1.04 version (I should still have a copy of these somewhere).
- no more auto creation of the folder in media for removable device is this udev thing ?
Hmm, yes I didn't consider that: udev will need to be updated for it to work with a kernel > 2.6.12. I'll look into it.
-Levien
-
Hello, thanks to your how to I have compiled a kernel for my J7F4..but
-my networks card still does not works with r8169 drivers a dhcp ip is attributed to the wan NIC but nothing goes trough
Sounds like a configuration issue. Which drivers are loaded? Did you set up the correct driver in the SMB config database? Or perhaps both the r1000 and the r8169 get loaded? Do you get any error messages in dmesg?
no there is just the one with the kernl that is on and compiled.
dmesg just say that eth 1 and eth0 are up no error during the load of the driver
-unable to compile the R1000 v1.06 under 2.6.21-rc5 (it worked just fine under 2.6.9 kernels
Yes, apparently the new Realtek driver doesn't yet compile with newer kernel versions (> 2.6.18 or so). You could try the 1.05 or 1.04 version (I should still have a copy of these somewhere).
will try with the 1.04 because the 1.05 freeze network with high speed up/download
=> after trying 1.04 do not compil
=> 1.05 compil with some errors but can be installed ....but no more success than with the r8169 ... :(
i can ping ip adresses on wan
- i can't ping with dns name
i can't lynx dns name or ip adresses
the NIC is always blinking
- no more auto creation of the folder in media for removable device is this udev thing ?
Hmm, yes I didn't consider that: udev will need to be updated for it to work with a kernel > 2.6.12. I'll look into it.
-Levien
I have seen lot of update for r8169 on 2.6.22 kernels maybe i should see...
other thing i saw that there is some pb with dual boot with windows where windows disable the NIc at shutdown and the r8169 driver is not able to up it correctly. but it seems that nothing is blinking on it which is not my case
-
bios A07 is released : http://download.jetway.com.tw/download.asp?sorder=Name&sword=J7F4K1G2E
-
[root@gateway drivers]# cd r1000_v1.04
[root@gateway r1000_v1.04]# ls
Makefile README release_note.txt src
[root@gateway r1000_v1.04]# make clean modules
make -C src/ clean
make[1]: Entering directory `/home/e-smith/files/ibays/antreno/drivers/r1000_v1.04/src'
rm -f *.o *.ko *~ core* .dep* .*.d .*.cmd *.mod.c *.a *.s .*.flags
make[1]: Leaving directory `/home/e-smith/files/ibays/antreno/drivers/r1000_v1.04/src'
make -C src/ modules
make[1]: Entering directory `/home/e-smith/files/ibays/antreno/drivers/r1000_v1.04/src'
make -C /lib/modules/2.6.9-55.0.2.ELsmp/build SUBDIRS=/home/e-smith/files/ibays/antreno/drivers/r1000_v1.04/src modules
make: *** /lib/modules/2.6.9-55.0.2.ELsmp/build: No such file or directory. Stop.
make: Entering an unknown directorymake: Leaving an unknown directorymake[1]: *** [modules] Error 2
make[1]: Leaving directory `/home/e-smith/files/ibays/antreno/drivers/r1000_v1.04/src'
make: *** [modules] Error 2
[root@gateway r1000_v1.04]#
This is what happens when i foillow the steps above?
Any suggestions anyone?
-
This is whta happens when I try to do the make commands!!
Any suggestions anyone??
"[root@gateway drivers]# cd r1000_v1.04
[root@gateway r1000_v1.04]# ls
Makefile README release_note.txt src
[root@gateway r1000_v1.04]# make clean modules
make -C src/ clean
make[1]: Entering directory `/home/e-smith/files/ibays/antreno/drivers/r1000_v1.04/src'
rm -f *.o *.ko *~ core* .dep* .*.d .*.cmd *.mod.c *.a *.s .*.flags
make[1]: Leaving directory `/home/e-smith/files/ibays/antreno/drivers/r1000_v1.04/src'
make -C src/ modules
make[1]: Entering directory `/home/e-smith/files/ibays/antreno/drivers/r1000_v1.04/src'
make -C /lib/modules/2.6.9-55.0.2.ELsmp/build SUBDIRS=/home/e-smith/files/ibays/antreno/drivers/r1000_v1.04/src modules
make: *** /lib/modules/2.6.9-55.0.2.ELsmp/build: No such file or directory. Stop.
make: Entering an unknown directorymake: Leaving an unknown directorymake[1]: *** [modules] Error 2
make[1]: Leaving directory `/home/e-smith/files/ibays/antreno/drivers/r1000_v1.04/src'
make: *** [modules] Error 2
[root@gateway r1000_v1.04]#
"
Thanks in advance
-
install the kernel source: kernel-devel
you may think first to boot to the non smp kernel if you have a J7 motherboard with single core then install the kernel-devel
otherwise you will need kernel-smp-devel
yum install kernel-smp-devel --enablerepo=base -y
or
yum install kernel-devel --enablerepo=base -y
as you need
JPP
-
following the How to i get it work perfectly with one interface in server only mode
with server + gateway :
- lan side is ok
- wan side obtain dhcp address or connect with static ip adress BUT
the sme can only ping the gateway with it's ip , and cannot resolve anything
no dns working
no http through the wan interface
only ping ip is possible
AND the LED interface keep flashing , netstats gives a lot of connection on domain port
HELP i need it to work in server gateway what's happens ?
-
iptables problem !!!
on 2.6.21 masquerade needs iptables 1.3.8
at startup SME show an error about masquerade , you need to restart /etc/init.d/iptables restart to access WAN
source : http://www.plouf.fr.eu.org/bazar/netfilter/changements-netfilter-2.6.html#linux-2.6.21
need to correct that , then correct the udev thing: (maybe this is this problem - sorry for french- http://forums.fedora-fr.org/viewtopic.php?id=22876)
-
searching more about the problem it was due to some missing component in the compiled kernel , masq was creating an error due to lack of "state" for iptables and netfilter in the kernel.
so i compile a new one with theses options and tada !
About Udev and HAL
here how i did to make it to workwith 7.1.3: DO NOT DO THIS
db yum_repositories set FC4 repository \
BaseURL http://mirror.aarnet.edu.au/pub/fedora/linux/core/4/i386/os/ \
EnableGroups yes \
GPGCheck no \
Name 'Fedora Core 4' \
Visible yes \
status disabled
expand-template /etc/yum.conf
yum update --enablerepo=FC4 hal
for information what was updated
Updating:
hal i386 0.5.2-2 FC4 207 k
Updating for dependencies:
SysVinit i386 2.85-39 FC4 98 k
dbus i386 0.33-3 FC4 542 k
dbus-glib i386 0.33-3 FC4 57 k
glib2 i386 2.6.4-1 FC4 552 k
initscripts i386 8.11.1-1 FC4 1.1 M
libselinux i386 1.23.10-2 FC4 66 k
libsepol i386 1.5.9-2 FC4 42 k
libstdc++ i386 4.0.0-8 FC4 295 k
libusb i386 0.1.10a-1 FC4 28 k
udev i386 0.58-1 FC4 1.1 M
then i simply did
start_udev
udevd&
hald
you can alternatively just signal-event post upgrade; signal-event reboot
/!\ be carrefull this solution is not good for 7.2 SME version : conflict due to smolt and smeserver-support with dbus, dbus-glib and dbus-python that is needed....
here what to do for 7.2 and 7.1.3 :
wget ftp://fr.rpmfind.net/linux/fedora/core/updates/3/x86_64/hal-0.4.7-1.FC3.i386.rpm
rpm -Uvh hal-0.4.7-1.FC3.i386.rpm
/etc/init.d/haldaemon start
I can also suggest you to update iptable to 1.3.7 from FC7 ( http://ftp.univie.ac.at/systems/linux/fedora/releases/7/Fedora/i386/os/Fedora/iptables-1.3.7-2.i386.rpm ) or 1.3.8-1 ( http://mirror.internode.on.net/pub/fedora/linux/development/i386/os/Fedora/iptables-1.3.8-1.i386.rpm ) in the dev of FC, but it seems to work properly with the one coming with SME.
I ll post her later my .config to compil the kernel and the rpm kernel
JPP
-
My RTL8169SC fix...............
BELKIN - Gigabit Desktop Network PCI Card (Part # F5D5005)
http://catalog.belkin.com/IWCatProductPage.process?Product_Id=183751
After pulling the cute little BELKIN sticker off the chip you would see it's a Realtek chip (RTL8169SC).
-----------------------------------------------------------------------------------
yum -y install kernel-devel gcc gcc-c++
wget ftp://210.51.181.211/cn/nic/r8169-6.002.00.tar.bz2
tar -jzxf r8169-6.002.00.tar.bz2
cd r8169-6.002.00
make clean modules
make install
chmod 744 /lib/modules/2.6.9-55.0.2.EL/kernel/drivers/net/r8169.ko
modprobe -a
Reboot the server
Configure and select the r8169 driver.
System will then prompt again for a reboot.
---------------------------------------------------------------------------------
YOu can find the instruction earlier in the thread if you want to remove the developer files.
Rigger
-
is there anyone who have a rpm binary package with r8169-6.003.00.tar.bz2 (http://ftp://210.51.181.211/cn/nic/r8169-6.003.00.tar.bz2) compiled for kernel-2.6.9-55.0.2.EL.i686. I cannot access the net in order to download any of the required packages so a little help would be awesome :)
-
Doesn't anyone have a "patched" kernel with this driver already installed, that we can just use?
-
I have a standard updated SME 7.2 server, with a unmodified kernel.
(But not the refered hardware.)
Look:
[root@sme72 ~]# modprobe r8169
[root@sme72 ~]# lsmod | grep r8169
r8169 28745 0
**********
dmesg | grep eth ??
dmesg | tail ??
ifconfig eth0 up
ifconfig eth1 up
ifconfig ??
-
is there anyone who have a rpm binary package with r8169-6.003.00.tar.bz2 (http://ftp://210.51.181.211/cn/nic/r8169-6.003.00.tar.bz2) compiled for kernel-2.6.9-55.0.2.EL.i686. I cannot access the net in order to download any of the required packages so a little help would be awesome :)
How about downloading on another machine and using a USB stick or CD to copy your data to the server?
-
is there anyone who have a rpm binary package with r8169-6.003.00.tar.bz2 (http://ftp://210.51.181.211/cn/nic/r8169-6.003.00.tar.bz2) compiled for kernel-2.6.9-55.0.2.EL.i686.
The 2.6.9-55.0.2.EL is long obsolete.
-
http://wiki.centos.org/HardwareList/RealTekr1000
-
you should try dkrms to auto compil the driver for new kernel as soon as a kernel is updated, and add somes commands to the post-update event
if you want an already made kernel go to my contrib space:
http://distro.ibiblio.org/pub/linux/distributions/smeserver/contribs/jppialasse/SME7/kernel2.6.21rc5git1ViaC7/
install the rpm and make the mkinitrd job + add it to grub menu.lst and that's all
only lack the module f71805f to monitor the mobo, everything else work good
-
Tried to compile driver as stated in http://forums.contribs.org/index.php?topic=35435.15
No luck.
[root@testserver r1000_v1.04]# make clean modules
make -C src/ clean
make[1]: Entering directory `/root/r1000_v1.04/src'
rm -f *.o *.ko *~ core* .dep* .*.d .*.cmd *.mod.c *.a *.s .*.flags
make[1]: Leaving directory `/root/r1000_v1.04/src'
make -C src/ modules
make[1]: Entering directory `/root/r1000_v1.04/src'
make -C /lib/modules/2.6.9-55.0.12.EL/build SUBDIRS=/root/r1000_v1.04/src modules
make: *** /lib/modules/2.6.9-55.0.12.EL/build: No such file or directory. Stop.
make: Entering an unknown directorymake: Leaving an unknown directorymake[1]: *** [modules] Error 2
make[1]: Leaving directory `/root/r1000_v1.04/src'
make: *** [modules] Error 2
Searching for directory /lib/modules/2.6.9-55.0.12.EL/build I found it missing
But found /usr/src/kernels/2.6.9-67.0.1.EL-i686/build what kernel is this??!!
-
make: *** /lib/modules/2.6.9-55.0.12.EL/build: No such file or directory. Stop.
make: Entering an unknown directorymake: Leaving an unknown directorymake[1]: *** [modules] Error 2
make[1]: Leaving directory `/root/r1000_v1.04/src'
make: *** [modules] Error 2
Searching for directory /lib/modules/2.6.9-55.0.12.EL/build I found it missing
But found /usr/src/kernels/2.6.9-67.0.1.EL-i686/build what kernel is this??!!
What kernel are you currently running? Try:uname -rCheck that you have the kernel headers/source for this kernelrpm -q kernel-develBoth should report the same number... If not you should try to install the kernel headers/source matching your kernel version: yum install kernel-devel-`uname -r`. It probably does not install with yum from the repositories so search it here (http://rpm.pbone.net/index.php3). Download to your machine and run yum localinstall /path/to/rpm
This is not tested and compiling modules is not advised, no warranties what so ever :-)
-
To be exact:
I've install SME 7.2 from ISO so I've got kernel 2.6.9-55.0.02
Did update from web-panel and got kernel 2.6.9-55.0.12 (always work with EL not ELsmp kernel)
Did yum -y install kernel-devel gcc gcc-c++
Downloaded http://www.vexins.com/r1000_v1.04.tgz (from a topic of the forum) because someone reported a succesfully compile under the same circumstances
After make clean modules got error 2
Using SSH logged in remotely and looked for the missing directory. No luck.
Tried to install kernel-headers. Same situation.
I don't understand what happens. I did compile succesfully in SME 6.0.1 drivers for different network cards, but no luck with 7.2
Thanks anyways
-
This is not tested and compiling modules is not advised, no warranties what so ever :-)
I'd go further and say that compiling modules is strongly discouraged, unless you really know what you are doing and can solve your own problems, when they (inevitably) arise.
-
Thanks for your advice. I agree with avoiding compilation for SME server modules. But we don't have to forget that Gigabyte motherboards are very stable and are a very good choice for small business servers. And Gigabyte begun to use 8111 chipset on meny mobos. Should we avoid tis mobos? I think is annoying to use an extra netwok card when you have a gigabit one onboard. Anyways I'm stuck in this issue and I'll look for a solution after New Year's eve
-
Thanks for your advice. I agree with avoiding compilation for SME server modules. But we don't have to forget that Gigabyte motherboards are very stable and are a very good choice for small business servers. And Gigabyte begun to use 8111 chipset on meny mobos. Should we avoid tis mobos?
Perhaps not, but since SME Server is based on CentOS, which in turn is based on RedHat Enterprise Linux, your best bet would be to go all the way to the RHEL bugtracker (https://bugzilla.redhat.com/index.cgi) and add a feature request for support of this module.
-
And about sme 7.4 ? Is it working or i need to compile a new kernel ?
Regards David
-
And about sme 7.4 ? Is it working or i need to compile a new kernel ?
The same advice applies to all minor releases as no new modules will be implemented in minor releases by our upstream provider(s) so SME Server won't either.
So no, it will not work (without manual modification like compiling modules which you should not do as advised earlier in this thread).
-
In fact i have a jetway mini itx board and wan't to put sme on it .
Any way for sme 8 ?
-
In fact i have a jetway mini itx board and wan't to put sme on it .
Any way for sme 8 ?
what about trying and reporting?
Ciao
Stefano