From: Heiko Z. <he...@zu...> - 2009-04-16 15:02:48
|
Hey guys, not sure if you saw it, but I changed the version of 1.3 into 1.4RC1. I'm compiling a version right now which I'll upload as the official 1.4RC1 (hopefully this weekend). -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Philippe W. <phi...@ae...> - 2009-04-16 15:31:56
|
Heiko Zuerker a écrit : > Hey guys, > > not sure if you saw it, but I changed the version of 1.3 into 1.4RC1. > I'm compiling a version right now which I'll upload as the official > 1.4RC1 (hopefully this weekend). > did you put bind 9.6 on 1.4rc1 ? -- Weill Philippe - Administrateur Systeme et Reseaux CNRS/UPMC/IPSL LATMOS (UMR 8190) Tour 45/46 3e Etage B302 - 4 Place Jussieu - 75252 Paris Cedex 05 - FRANCE Email:phi...@la... | tel:+33 0144274759 Fax:+33 0144273776 |
From: Heiko Z. <he...@zu...> - 2009-04-16 15:46:14
|
Quoting Philippe Weill <phi...@ae...>: > Heiko Zuerker a écrit : >> Hey guys, >> >> not sure if you saw it, but I changed the version of 1.3 into 1.4RC1. >> I'm compiling a version right now which I'll upload as the official >> 1.4RC1 (hopefully this weekend). >> > did you put bind 9.6 on 1.4rc1 ? No. I'll update it and give it a try. -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Andrzej O. <an...@ma...> - 2009-04-17 02:54:23
|
Heiko Zuerker wrote: > not sure if you saw it, but I changed the version of 1.3 into 1.4RC1. > I'm compiling a version right now which I'll upload as the official > 1.4RC1 (hopefully this weekend). Fresh system, created from scratch. No nice. No parallel... But for now is not compiling... broken in prepare. Maybe we need wait to monday... There is prepare log: > `/build/scripts/config/linux-2.6/config_linux' -> `/build/tmp/linux-2.6.29/.config' > applying patch: /build/tmp/kernel-patches-2.6/004-extra_optimization.patch > patching file Makefile > Hunk #1 succeeded at 560 (offset 11 lines). > applying patch: /build/tmp/kernel-patches-2.6/050-frandom.patch > patching file arch/um/Kconfig.char > Hunk #1 succeeded at 230 with fuzz 2 (offset 2 lines). > patching file drivers/char/Kconfig > Hunk #1 succeeded at 66 (offset 9 lines). > patching file drivers/char/Makefile > Hunk #1 succeeded at 9 with fuzz 2. > patching file drivers/char/frandom.c > patching file drivers/char/random.c > Hunk #1 succeeded at 1269 (offset 38 lines). > patching file include/linux/sysctl.h > Hunk #1 succeeded at 242 (offset -6 lines). > applying patch: /build/tmp/kernel-patches-2.6/140-netfilter_time.patch > patching file include/linux/netfilter_ipv4/ipt_time.h > patching file net/ipv4/netfilter/ipt_time.c > patching file net/ipv4/netfilter/Kconfig > Hunk #1 FAILED at 57. > 1 out of 1 hunk FAILED -- saving rejects to file net/ipv4/netfilter/Kconfig.rej > patching file net/ipv4/netfilter/Makefile > Hunk #1 succeeded at 52 with fuzz 2 (offset 2 lines). Regards -- Andrzej Odyniec <an...@ma...> Rada Nadzorcza Macrologic SA ul. Chroscickiego 49, 02-414 Warszawa tel. +48(22)8637681x132, fax: +48(22)8639861 ul. Jagiellonska 36, 03-719 Warszawa tel. +48(22)5118115, fax: +48(22)5118117 |
From: Serge L. <fi...@in...> - 2009-04-17 07:02:52
|
Hi Andrzej, Andrzej Odyniec wrote: > Heiko Zuerker wrote: >> not sure if you saw it, but I changed the version of 1.3 into 1.4RC1. >> I'm compiling a version right now which I'll upload as the official >> 1.4RC1 (hopefully this weekend). kernel-patches is old: > ... >> applying patch: /build/tmp/kernel-patches-2.6/140-netfilter_time.patch >> patching file include/linux/netfilter_ipv4/ipt_time.h >> patching file net/ipv4/netfilter/ipt_time.c >> patching file net/ipv4/netfilter/Kconfig >> Hunk #1 FAILED at 57. >> 1 out of 1 hunk FAILED -- saving rejects to file net/ipv4/netfilter/Kconfig.rej >> patching file net/ipv4/netfilter/Makefile >> Hunk #1 succeeded at 52 with fuzz 2 (offset 2 lines). > Regards > [root@sjcspare8 tmp]# ll kernel-patches-2.6/ total 48 -rw-r--r-- 1 root root 365 Dec 10 14:06 004-extra_optimization.patch -rw-r--r-- 1 root root 15311 Jan 10 19:26 050-frandom.patch -rw-r--r-- 1 root root 24484 Dec 10 14:06 150-netfilter_imq.patch -rw-r--r-- 1 root root 1106 Dec 10 19:32 151-imq-2.6.27-hotfix.patch |
From: Heiko Z. <he...@zu...> - 2009-04-17 11:59:51
|
Mine compiled fine last night, so I'm not sure why yours fails. I used the default config with 4 parallel jobs. I'm uploading the build right now, it would be great if folks could double check it before I create an official version. Heiko Quoting Serge Leschinsky <fi...@in...>: > Hi Andrzej, > > Andrzej Odyniec wrote: >> Heiko Zuerker wrote: >>> not sure if you saw it, but I changed the version of 1.3 into 1.4RC1. >>> I'm compiling a version right now which I'll upload as the official >>> 1.4RC1 (hopefully this weekend). > > kernel-patches is old: >> > ... >>> applying patch: /build/tmp/kernel-patches-2.6/140-netfilter_time.patch >>> patching file include/linux/netfilter_ipv4/ipt_time.h >>> patching file net/ipv4/netfilter/ipt_time.c >>> patching file net/ipv4/netfilter/Kconfig >>> Hunk #1 FAILED at 57. >>> 1 out of 1 hunk FAILED -- saving rejects to file >>> net/ipv4/netfilter/Kconfig.rej >>> patching file net/ipv4/netfilter/Makefile >>> Hunk #1 succeeded at 52 with fuzz 2 (offset 2 lines). >> Regards >> > > [root@sjcspare8 tmp]# ll kernel-patches-2.6/ > total 48 > -rw-r--r-- 1 root root 365 Dec 10 14:06 004-extra_optimization.patch > -rw-r--r-- 1 root root 15311 Jan 10 19:26 050-frandom.patch > -rw-r--r-- 1 root root 24484 Dec 10 14:06 150-netfilter_imq.patch > -rw-r--r-- 1 root root 1106 Dec 10 19:32 151-imq-2.6.27-hotfix.patch > > ------------------------------------------------------------------------------ > Stay on top of everything new and different, both inside and > around Java (TM) technology - register by April 22, and save > $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. > 300 plus technical and hands-on sessions. Register today. > Use priority code J9JMT32. http://p.sf.net/sfu/p > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Andrzej O. <an...@ma...> - 2009-04-17 12:33:10
|
Heiko Zuerker wrote: > Mine compiled fine last night, so I'm not sure why yours fails. I used > the default config with 4 parallel jobs. > > I'm uploading the build right now, it would be great if folks could > double check it before I create an official version. I'm sure, You right. Maybe my build process get files to early. I used the following in /usr/src directory, where was no lfssystem subdirectory: > tar -xjvf /mnt/lfs/sources/devil/lfssystem-SVN-20070314-cleaned.tar.bz2 > cd lfssystem > cvs -d:pserver:ano...@de...:/cvsroot/devil-linux login </dev/null > cvs -z3 -d:pserver:ano...@de...:/cvsroot/devil-linux co build > cd build > ./update_src and after proper chroot change (cr) and make menuconfig and after make unpack prepare makefile This sequence always worked Maybe in time, I get files, it wasn't be fresh on cvs or in source package repository. I will repeat all process again to new lfssystem directory Regards -- Andrzej Odyniec <an...@ma...> Rada Nadzorcza Macrologic SA ul. Chroscickiego 49, 02-414 Warszawa tel. +48(22)8637681x132, fax: +48(22)8639861 ul. Jagiellonska 36, 03-719 Warszawa tel. +48(22)5118115, fax: +48(22)5118117 |
From: Heiko Z. <he...@zu...> - 2009-04-17 13:10:36
|
Quoting Andrzej Odyniec <an...@ma...>: > Heiko Zuerker wrote: > >> Mine compiled fine last night, so I'm not sure why yours fails. I used >> the default config with 4 parallel jobs. >> >> I'm uploading the build right now, it would be great if folks could >> double check it before I create an official version. > > I'm sure, You right. Maybe my build process get files to early. I used the > following in /usr/src directory, where was no lfssystem subdirectory: > >> tar -xjvf /mnt/lfs/sources/devil/lfssystem-SVN-20070314-cleaned.tar.bz2 >> cd lfssystem >> cvs >> -d:pserver:ano...@de...:/cvsroot/devil-linux >> login </dev/null >> cvs -z3 >> -d:pserver:ano...@de...:/cvsroot/devil-linux >> co build >> cd build >> ./update_src > > and after proper chroot change (cr) and > make menuconfig and after > make unpack prepare makefile > > This sequence always worked > > Maybe in time, I get files, it wasn't be fresh on cvs or in source package > repository. I will repeat all process again to new lfssystem directory Did you run the update_src against our main ftp server? Maybe the mirror is not updated completely. -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Andrzej O. <an...@ma...> - 2009-04-17 17:33:09
|
Heiko Zuerker: > Did you run the update_src against our main ftp server? Maybe the > mirror is not updated completely. I always do update_src against: (1) Devil-Linux FTP-Server Luxembourg-Kirchberg The one trick I'm doing is copying all sources from my private repository before doing update_src, for not overloading FTP-Server in Luxemburg. After update_src I'm copying differences again to my private repository. But... now I see, contents of kernel patches package is different. Always update_src removed old package and downoladed new one. But this package was NOT replaced. Maybe because has this same name as old one? Message from lftp was: Verifying md5 checksums src/kernel-patches-2.6.tar.bz2: FAILED but was immediately covered by mc window. So I have new experience: -- look for messages of this kind and eventually remove packages with bad sum -- and after repeat update_src again Thanks for help Regards -- Andrzej Odyniec <an...@ma...> Rada Nadzorcza Macrologic SA ul. Chroscickiego 49, 02-414 Warszawa tel. +48(22)8637681x132, fax: +48(22)8639861 ul. Jagiellonska 36, 03-719 Warszawa tel. +48(22)5118115, fax: +48(22)5118117 |
From: Serge L. <fi...@in...> - 2009-04-18 02:52:40
|
Andrzej Odyniec wrote: > > now I see, contents of kernel patches package is different. > Always update_src removed old package and downoladed new one. > But this package was NOT replaced. Maybe because has this same name as old one? There is a chance to check it once again. I've updated dst package without changing its name. On my box the update was successful (timestamps?). Please pay attention to the update of dst on your system Serge |
From: Andrzej O. <an...@ma...> - 2009-04-19 00:03:27
|
Serge Leschinsky wrote: > There is a chance to check it once again. I've updated dst package without > changing its name. On my box the update was successful (timestamps?). Please pay > attention to the update of dst on your system I will check this after weekend. Especially because Intel e1000 is not compiling. I need e1000 --- in my router I have four port Intel server card and as I remember, standard kernel drivers has problems with this card. Look into build log, please: > make[2]: Entering directory `/build/tmp/e1000-8.0.6/src' > make[2]: warning: -jN forced in submake: disabling jobserver mode. > make -C /build/tmp/linux-2.6.29 SUBDIRS=/build/tmp/e1000-8.0.6/src modules > make[3]: Entering directory `/build/tmp/linux-2.6.29' > CC [M] /build/tmp/e1000-8.0.6/src/e1000_main.o > /build/tmp/e1000-8.0.6/src/e1000_main.c: In function 'e1000_io_error_detected': > /build/tmp/e1000-8.0.6/src/e1000_main.c:4894: error: 'struct net_device' has no member named 'priv' > /build/tmp/e1000-8.0.6/src/e1000_main.c: In function 'e1000_io_slot_reset': > /build/tmp/e1000-8.0.6/src/e1000_main.c:4916: error: 'struct net_device' has no member named 'priv' > /build/tmp/e1000-8.0.6/src/e1000_main.c: In function 'e1000_io_resume': > /build/tmp/e1000-8.0.6/src/e1000_main.c:4944: error: 'struct net_device' has no member named 'priv' > make[4]: *** [/build/tmp/e1000-8.0.6/src/e1000_main.o] Error 1 > make[3]: *** [_module_/build/tmp/e1000-8.0.6/src] Error 2 > make[3]: Leaving directory `/build/tmp/linux-2.6.29' > make[2]: *** [default] Error 2 > make[2]: Leaving directory `/build/tmp/e1000-8.0.6/src' In Sourceforge there are no newer Intel drivers. Maybe there is option correcting this problem. I need read comments about it. But as we see, there are changed struct net_device in headers. With 2.6.27 kernel Intel e1000 compiled and work correct. Best Regards Andrzej Odyniec |
From: Andrzej O. <an...@ma...> - 2009-04-19 00:52:17
|
I wrote: > I will check this after weekend. Especially because Intel e1000 is not > compiling. I need e1000 --- in my router I have four port Intel server card > and as I remember, standard kernel drivers has problems with this card. Look > into build log, please: > >>make[2]: Entering directory `/build/tmp/e1000-8.0.6/src' >>make[2]: warning: -jN forced in submake: disabling jobserver mode. >>make -C /build/tmp/linux-2.6.29 SUBDIRS=/build/tmp/e1000-8.0.6/src modules >>make[3]: Entering directory `/build/tmp/linux-2.6.29' >> CC [M] /build/tmp/e1000-8.0.6/src/e1000_main.o >>/build/tmp/e1000-8.0.6/src/e1000_main.c: In function 'e1000_io_error_detected': >>/build/tmp/e1000-8.0.6/src/e1000_main.c:4894: error: 'struct net_device' has no member named 'priv' >>/build/tmp/e1000-8.0.6/src/e1000_main.c: In function 'e1000_io_slot_reset': >>/build/tmp/e1000-8.0.6/src/e1000_main.c:4916: error: 'struct net_device' has no member named 'priv' >>/build/tmp/e1000-8.0.6/src/e1000_main.c: In function 'e1000_io_resume': >>/build/tmp/e1000-8.0.6/src/e1000_main.c:4944: error: 'struct net_device' has no member named 'priv' >>make[4]: *** [/build/tmp/e1000-8.0.6/src/e1000_main.o] Error 1 >>make[3]: *** [_module_/build/tmp/e1000-8.0.6/src] Error 2 >>make[3]: Leaving directory `/build/tmp/linux-2.6.29' >>make[2]: *** [default] Error 2 >>make[2]: Leaving directory `/build/tmp/e1000-8.0.6/src' I compared include/linux/netdevice.h in 2.6.27 and 2.6.29 And answer is simple: in 2.6.29 kernel structure net_device has changed. There is no pointer priv (used in Intel 8.0.6 drivers) but for getting private data function call is used. So 8.0.6 version of Intel driver will not be compilling with 2.6.29 kernel. All hope in standard e1000 drivers --- maybe they will work now with server Intel Ethernet cards. If not --- we must wait for newer version (or try e1000e?). Current e1000 conf option is unusable. Best Regards Andrzej Odyniec |
From: Heiko Z. <he...@zu...> - 2009-04-19 03:24:19
|
Hey, > -----Original Message----- > From: Andrzej Odyniec [mailto:an...@ma...] > Sent: Saturday, April 18, 2009 7:03 PM > To: dev...@li... > Subject: Re: [Devil-linux-develop] 1.4rc1 > > Serge Leschinsky wrote: > > There is a chance to check it once again. I've updated dst package > without > > changing its name. On my box the update was successful (timestamps?). > Please pay > > attention to the update of dst on your system > > I will check this after weekend. Especially because Intel e1000 is not > compiling. I need e1000 --- in my router I have four port Intel server > card > and as I remember, standard kernel drivers has problems with this card. We're using the drivers from the Intel website. There's a slightly newer one, but it got created way before the 2.6.29 kernel. http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProductID=838&DwnldID =9180&strOSs=39&OSFullName=Linux*&lang=eng Try the Kernel driver, maybe it's working now with your card. Heiko |
From: Andrzej O. <an...@ma...> - 2009-04-20 15:33:58
|
Heiko, I wrote: >>I will check this after weekend. Especially because Intel e1000 is not >>compiling. I need e1000 --- in my router I have four port Intel server >>card and as I remember, standard kernel drivers has problems with this card. And You wrote: > We're using the drivers from the Intel website. There's a slightly newer > one, but it got created way before the 2.6.29 kernel. > > Try the Kernel driver, maybe it's working now with your card. I will check it in near future, but as for now, I tried to compile other Intel driver dedicated to new Intel circuits: e1000e This diver was updated last days, and they (Intel engineers?) write, that is good for new controllers. In 1.4RC1 build environment I copied script e1000 to e1000e and corrected (de facto adding "e" letter after e1000 in some places). Into source directory I inserted driver package (actually from Intel page on Sourceforge: http://downloads.sourceforge.net/e1000/e1000e-0.5.18.3.tar.gz) and unpacked manually into tmp directory. After this in .config I set variable CONFIG_INTEL_E1000E=y checked in altered script and did "make prepare" and "make build". As effect I obtained in e1000e log: > make[1]: Entering directory `/build/tmp/e1000e-0.5.18.3/src' > make -C /build/tmp/linux-2.6.29 SUBDIRS=/build/tmp/e1000e-0.5.18.3/src modules > make[2]: Entering directory `/build/tmp/linux-2.6.29' > CC [M] /build/tmp/e1000e-0.5.18.3/src/netdev.o > CC [M] /build/tmp/e1000e-0.5.18.3/src/ethtool.o > CC [M] /build/tmp/e1000e-0.5.18.3/src/param.o > CC [M] /build/tmp/e1000e-0.5.18.3/src/e1000_82571.o > CC [M] /build/tmp/e1000e-0.5.18.3/src/e1000_ich8lan.o > CC [M] /build/tmp/e1000e-0.5.18.3/src/e1000_80003es2lan.o > CC [M] /build/tmp/e1000e-0.5.18.3/src/e1000_mac.o > CC [M] /build/tmp/e1000e-0.5.18.3/src/e1000_nvm.o > CC [M] /build/tmp/e1000e-0.5.18.3/src/e1000_phy.o > CC [M] /build/tmp/e1000e-0.5.18.3/src/e1000_manage.o > CC [M] /build/tmp/e1000e-0.5.18.3/src/kcompat.o > LD [M] /build/tmp/e1000e-0.5.18.3/src/e1000e.o > Building modules, stage 2. > MODPOST 1 modules > WARNING: modpost: Found 23 section mismatch(es). > To see full details build your kernel with: > 'make CONFIG_DEBUG_SECTION_MISMATCH=y' > CC /build/tmp/e1000e-0.5.18.3/src/e1000e.mod.o > LD [M] /build/tmp/e1000e-0.5.18.3/src/e1000e.ko > make[2]: Leaving directory `/build/tmp/linux-2.6.29' > make[1]: Leaving directory `/build/tmp/e1000e-0.5.18.3/src' > removing debug symbols from binaries Supposing that "section mismatches" are properly serviced I burn new iso and boot. All seems is working. In boot log (dmesg) I have: > e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k6 > e1000e: Copyright (c) 1999-2008 Intel Corporation. > e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 > e1000e 0000:00:19.0: setting latency timer to 64 > e1000e 0000:00:19.0: irq 29 for MSI/MSI-X > parport_pc 00:07: reported by Plug and Play ACPI > parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA] > 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:18:f3:f0:0f:94 > 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection > 0000:00:19.0: eth0: MAC: 5, PHY: 6, PBA No: ffffff-0ff > e1000e 0000:03:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > e1000e 0000:03:00.0: setting latency timer to 64 > e1000e 0000:03:00.0: irq 30 for MSI/MSI-X > ata5: SATA link down (SStatus 0 SControl 300) > ohci1394 0000:07:01.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 > ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[20] MMIO=[febff800-febfffff] Max Packet=[2048] IR/IT contexts=[4/8] > 0000:03:00.0: eth1: (PCI Express:2.5GB/s:Width x4) 00:15:17:33:f9:34 > 0000:03:00.0: eth1: Intel(R) PRO/1000 Network Connection > 0000:03:00.0: eth1: MAC: 0, PHY: 4, PBA No: d47316-004 > e1000e 0000:03:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17 > e1000e 0000:03:00.1: setting latency timer to 64 > e1000e 0000:03:00.1: irq 31 for MSI/MSI-X > 0000:03:00.1: eth2: (PCI Express:2.5GB/s:Width x4) 00:15:17:33:f9:35 > 0000:03:00.1: eth2: Intel(R) PRO/1000 Network Connection > 0000:03:00.1: eth2: MAC: 0, PHY: 4, PBA No: d47316-004 > e1000e 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > e1000e 0000:04:00.0: setting latency timer to 64 > e1000e 0000:04:00.0: irq 32 for MSI/MSI-X > ata6: SATA link down (SStatus 0 SControl 300) > 0000:04:00.0: eth3: (PCI Express:2.5GB/s:Width x4) 00:15:17:33:f9:36 > 0000:04:00.0: eth3: Intel(R) PRO/1000 Network Connection > 0000:04:00.0: eth3: MAC: 0, PHY: 4, PBA No: d47316-004 > e1000e 0000:04:00.1: PCI INT B -> GSI 18 (level, low) -> IRQ 18 > e1000e 0000:04:00.1: setting latency timer to 64 > e1000e 0000:04:00.1: irq 33 for MSI/MSI-X > 0000:04:00.1: eth4: (PCI Express:2.5GB/s:Width x4) 00:15:17:33:f9:37 > 0000:04:00.1: eth4: Intel(R) PRO/1000 Network Connection > 0000:04:00.1: eth4: MAC: 0, PHY: 4, PBA No: d47316-004 > ieee1394: Host added: ID:BUS[0-00:1023] GUID[0011d8000103f9cb] > end_request: I/O error, dev fd0, sector 0 > end_request: I/O error, dev fd0, sector 0 > Buffer I/O error on device fd0, logical block 0 > end_request: I/O error, dev fd0, sector 0 > Buffer I/O error on device fd0, logical block 0 > kjournald starting. Commit interval 5 seconds > EXT3 FS on sdg4, internal journal > EXT3-fs: mounted filesystem with ordered data mode. > 802.1Q VLAN Support v1.8 Ben Greear <gr...@ca...> > All bugs added by David S. Miller <da...@re...> > e1000e 0000:00:19.0: irq 29 for MSI/MSI-X > e1000e 0000:00:19.0: irq 29 for MSI/MSI-X > e1000e 0000:03:00.0: irq 30 for MSI/MSI-X > e1000e 0000:03:00.0: irq 30 for MSI/MSI-X > e1000e 0000:03:00.1: irq 31 for MSI/MSI-X > e1000e 0000:03:00.1: irq 31 for MSI/MSI-X > e1000e 0000:04:00.0: irq 32 for MSI/MSI-X > e1000e 0000:04:00.0: irq 32 for MSI/MSI-X > NET: Registered protocol family 10 Intel script: netdriverinfo.sh gives this output: > root@Devil:/var # ./netdriverinfo.sh > eth0 : 00:19.0 > Make/Model = ASUSTeK Computer Inc. Device 8268 > Ethernet controller = Intel Corporation 82566DM Gigabit Network Connection > VenID:DevID = 8086:104a > Driver name = e1000e > Driver version = 0.3.3.3-k6 > eth1 : 03:00.0 > Make/Model = Intel Corporation PRO/1000 PT Quad Port Server Adapter > Ethernet controller = Intel Corporation 82571EB Gigabit Ethernet Controller > VenID:DevID = 8086:10a4 > Driver name = e1000e > Driver version = 0.3.3.3-k6 > eth2 : 03:00.1 > Make/Model = Intel Corporation PRO/1000 PT Quad Port Server Adapter > Ethernet controller = Intel Corporation 82571EB Gigabit Ethernet Controller > VenID:DevID = 8086:10a4 > Driver name = e1000e > Driver version = 0.3.3.3-k6 > eth3 : 04:00.0 > Make/Model = Intel Corporation PRO/1000 PT Quad Port Server Adapter > Ethernet controller = Intel Corporation 82571EB Gigabit Ethernet Controller > VenID:DevID = 8086:10a4 > Driver name = e1000e > Driver version = 0.3.3.3-k6 > eth4 : 04:00.1 > Make/Model = Intel Corporation PRO/1000 PT Quad Port Server Adapter > Ethernet controller = Intel Corporation 82571EB Gigabit Ethernet Controller > VenID:DevID = 8086:10a4 > Driver name = e1000e > Driver version = 0.3.3.3-k6 ethtool -p blinks on all RJ45 sockets correctly. All sockets detects link. For example: > root@Devil:/var # ethtool eth1 > Settings for eth1: > Supported ports: [ TP ] > Supported link modes: 10baseT/Half 10baseT/Full > 100baseT/Half 100baseT/Full > 1000baseT/Full > Supports auto-negotiation: Yes > Advertised link modes: 10baseT/Half 10baseT/Full > 100baseT/Half 100baseT/Full > 1000baseT/Full > Advertised auto-negotiation: Yes > Speed: 1000Mb/s > Duplex: Full > Port: Twisted Pair > PHYAD: 1 > Transceiver: internal > Auto-negotiation: on > Supports Wake-on: pumbag > Wake-on: g > Current message level: 0x00000001 (1) > Link detected: yes I can connect to box via ssh. So I think: If Intel is not upgrading e1000 to 2.6.29 net structures, there is time to replace e1000 -> e1000e in 1.4RC1. Best regards -- Andrzej Odyniec <an...@ma...> Rada Nadzorcza Macrologic SA ul. Chroscickiego 49, 02-414 Warszawa tel. +48(22)8637681x132, fax: +48(22)8639861 ul. Jagiellonska 36, 03-719 Warszawa tel. +48(22)5118115, fax: +48(22)5118117 |
From: Andrzej O. <an...@ma...> - 2009-04-22 17:59:54
|
Andrzej Odyniec wrote: > I will check it in near future, but as for now, I tried to compile other Intel > driver dedicated to new Intel circuits: e1000e First! ====== OPS! All I wrote was true except report from netdriverinfo. Should be (after today's second compilation): > root@Devil # ./netdriverinfo.sh > eth0 : 00:19.0 > Make/Model = ASUSTeK Computer Inc. Device 8268 > Ethernet controller = Intel Corporation 82566DM Gigabit Network Connection > VenID:DevID = 8086:104a > Driver name = e1000e > Driver version = 0.5.18.3-NAPI > eth1 : 03:00.0 > Make/Model = Intel Corporation PRO/1000 PT Quad Port Server Adapter > Ethernet controller = Intel Corporation 82571EB Gigabit Ethernet Controller > VenID:DevID = 8086:10a4 > Driver name = e1000e > Driver version = 0.5.18.3-NAPI > eth2 : 03:00.1 > Make/Model = Intel Corporation PRO/1000 PT Quad Port Server Adapter > Ethernet controller = Intel Corporation 82571EB Gigabit Ethernet Controller > VenID:DevID = 8086:10a4 > Driver name = e1000e > Driver version = 0.5.18.3-NAPI > eth3 : 04:00.0 > Make/Model = Intel Corporation PRO/1000 PT Quad Port Server Adapter > Ethernet controller = Intel Corporation 82571EB Gigabit Ethernet Controller > VenID:DevID = 8086:10a4 > Driver name = e1000e > Driver version = 0.5.18.3-NAPI > eth4 : 04:00.1 > Make/Model = Intel Corporation PRO/1000 PT Quad Port Server Adapter > Ethernet controller = Intel Corporation 82571EB Gigabit Ethernet Controller > VenID:DevID = 8086:10a4 > Driver name = e1000e > Driver version = 0.5.18.3-NAPI Previus was from original kernel driver (because of little bug in my script compiled driver was not properly installed in CD image). As we can see, kernel has e1000e driver but in older version than this from Intel. In Ubuntu forums I found, that this old driver is not working correctly in some situations and guys used Intel 0.5.18.3 instead. I need this DL installation for my main router, so I will compile actual Intel driver using my script, reducing (I hope) risk. Second! ======= But I detected second problem in default config compiled DL 1.4RC1. I have in /etc/sysconfig/config RUNFROMRAM=yes. Look, please, onto console display: > ******************************************************************************** > * * > * Welcome to Devil-Linux * > * * > ******************************************************************************** > http://www.devil-linux.org/ > > Version 1.4RC1-2009-04-22 > Kernel 2.6.29.1-grsec > Mounting SHM FS on /shm > waiting until usb-storage driver has initialized all devices ... > Creating devices in /dev > > Searching for configuration media > Checking for "etc-mods.tar.bz2" on "/dev/sdb2" ... file not found > Checking for "etc-mods.tar.bz2" on "/dev/sdb1" ... success! > loading configuration > Searching for Devil-Linux CD-ROM > Search list: /dev/hdb > checking /dev/hdb Found on /dev/hdb > System is configured to run from ram > Copying system image (327 MB) to ramdisk...|done. > ERROR: ramdisk size calculation error > the image to copy was bigger than expected > > Please report to bu...@de... > > Falling back to standard mount... > Mounting SHM FS on /cdrom/shm > Unmounting proc > Starting up final system... > Using AUFS for /etc/ > aufs 2-standalone.tree-29-20090413 > Changed Root > Un-Mounting old Filesystems > Freeing InitRD memory I don't know, why? Do You have this same effect or not? Best regards -- Andrzej Odyniec <an...@ma...> Rada Nadzorcza Macrologic SA ul. Chroscickiego 49, 02-414 Warszawa tel. +48(22)8637681x132, fax: +48(22)8639861 ul. Jagiellonska 36, 03-719 Warszawa tel. +48(22)5118115, fax: +48(22)5118117 |
From: Serge L. <fi...@in...> - 2009-04-22 19:01:23
|
Hello Andrzej, Andrzej Odyniec wrote: >> eth4 : 04:00.1 >> Make/Model = Intel Corporation PRO/1000 PT Quad Port Server Adapter >> Ethernet controller = Intel Corporation 82571EB Gigabit Ethernet Controller >> VenID:DevID = 8086:10a4 >> Driver name = e1000e >> Driver version = 0.5.18.3-NAPI > > Previus was from original kernel driver (because of little bug in my script > compiled driver was not properly installed in CD image). As we can see, kernel > has e1000e driver but in older version than this from Intel. AFAIK there are the both drivers in the kernel - e1000 and e1000e. I think these drivers are not identical, so if you need not only Intel's original e1000 but e1000e as well we caт just add it. > In Ubuntu forums > I found, that this old driver is not working correctly in some situations and > guys used Intel 0.5.18.3 instead. I need this DL installation for my main > router, so I will compile actual Intel driver using my script, reducing (I > hope) risk. So, you suggest to update e1000e driver to the latest e1000e, do you? If you have tested it and it's working, I suppose it may be done. >> System is configured to run from ram >> Copying system image (327 MB) to ramdisk...|done. >> ERROR: ramdisk size calculation error >> the image to copy was bigger than expected >> ... > > I don't know, why? Do You have this same effect or not? I have a version. It's a result of rounding... As a hotfix I'd remove the following code (mount_cdrom): # get size of the copied image local REAL_SIZE=$(du -k ${RAMDISK}/${IMAGE} | awk '{print $1}') let REAL_SIZE=REAL_SIZE*10/1024+5 # do correct rounding let REAL_SIZE=REAL_SIZE/10 # check if we at least match the image size estimated before if [ ${REAL_SIZE} -lt ${IMAGE_SIZE_MB} ]; then $RED; echo "FATAL-ERROR: copying failed - only ${REAL_SIZE} MB out of ${IMAGE_SIZE_MB} MB copied" echo ' a possible source of this problem could be:' echo ' * read errors - media defective?' echo ' * out of RAM - need to install more RAM?' echo $NORMAL run_from_ram_cleanup return 1 fi And you will completely rely on error handling during "copy" operation. To guarantee the image integrity we can implement checksumming (size calculation is not reliable parameter anyway). -- Serge |
From: Andrzej O. <an...@ma...> - 2009-04-23 10:28:09
|
Hello Serge, > AFAIK there are the both drivers in the kernel - e1000 and e1000e. I think > these drivers are not identical, so if you need not only Intel's original e1000 > but e1000e as well we caт just add it. I again read and analysed Intel documents about e1000 and e1000e drivers. Both drivers are for near all Intel ethernet controllers, not only gigabit. They call e1000e "a new driver". Maybe is coded from scratch again? But letter "e" at end suggest, driver is coded especially for PCIe bus. They loss compatibility with old 82546GB PCI-X circuit, so they leaved e1000 driver in use. But for many chips both should be working. On machine identical with this from my examples identical 4 port card is working on driver e1000 (DL compiled year ago). Response to netdriverinfo.sh script is: > eth4 : 04:00.1 > Make/Model = Intel Corporation PRO/1000 PT Quad Port Server Adapter > Ethernet controller = Intel Corporation 82571EB Gigabit Ethernet Controller > VenID:DevID = 8086:10a4 > Driver name = e1000 > Driver version = 7.3.20-k2-NAPI But as I remember, year ago standard kernel driver was not working with my card. > So, you suggest to update e1000e driver to the latest e1000e, do you? If you > have tested it and it's working, I suppose it may be done. I think, driver e1000 in kernel is mature and for compatibility with old chips, not supported by e1000e, is sufficient. As for now, we haven't alternative, because Intel e1000 is not compiling with 2.6.29 kernel. Looking on dates (http://sourceforge.net/project/showfiles.php?group_id=42302) we can see, that e1000e is touched 19 March -- and is working with changed driver interface in 2.6.29. But Intel e1000 driver is left unchanged and (probably) will never compile with new kernels. So Intel e1000 driver and "Intel e1000" configuration option is now obsolete. For warranty to work (kernel can change again in this place) I suggest to left kernel driver e1000e working. For eventual differences, changes, corrections and adoptions for new Intel Circuits I think, is needed alternaive: e1000e from Intel --- choosen as today e1000. Another question is: what should be default? I dont'n know. Maybe (as today) -- kernel driver. > I have a version. It's a result of rounding... As a hotfix I'd remove the > following code (mount_cdrom): Big thanks for solution. I will try. Serge, Heiko. Big thanks for Devil-Linux initiative. Is great. I use as for now 3 routers on DL (one with BGP) an one separate spam filtering MTA. I think to run separate Kerberos server on it. It is great work. Best Regards Andrzej Odyniec Warsaw, Poland |