From: Andy <an...@co...> - 2014-07-12 05:02:21
|
Hi, I'm having issues with SI and using the UYOK feature. It seems to build the kernel without issue but the network card can't load the firmware. During the image loading on by slave node I get bnx2: Can't load firmware file "bnx2/bnx2-mips-06-6.2.3.fw Since it can't find that then in can't grab and IP and the rest fails. I'm using systemimager 4.3.0.17 When I create the initrd/kernel it seems to work. It creates the /tmp/.systemimage.0 folder and copies all files needed (including the firmware tree) to it. I run: si_prepareclient --server dell01 --include-system-firmware and once that's complete I copy the initrd and kernel to /tftpboot as the official names that are pulled up through PXE. --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com |
From: Pierre B. <pie...@un...> - 2014-07-12 12:05:29
Attachments:
smime.p7s
|
Hi, We have solve this problem by install bnx2 module from the source of broadcrom. The broadcom version works like others modules and not like a "firmware" so it's included with UYOK. Regards Le 12/07/2014 07:02, Andy a écrit : > Hi, > > I'm having issues with SI and using the UYOK feature. It seems to build > the kernel without issue but the network card can't load the firmware. > During the image loading on by slave node I get > > bnx2: Can't load firmware file "bnx2/bnx2-mips-06-6.2.3.fw > > Since it can't find that then in can't grab and IP and the rest fails. > > I'm using systemimager 4.3.0.17 > > When I create the initrd/kernel it seems to work. It creates the > /tmp/.systemimage.0 folder and copies all files needed (including the > firmware tree) to it. > > I run: > > si_prepareclient --server dell01 --include-system-firmware and once > that's complete I copy the initrd and kernel to /tftpboot as the > official names that are pulled up through PXE. > > > > > > ------------------------------------------------------------------------ > <http://www.avast.com/> > > This email is free from viruses and malware because avast! Antivirus > <http://www.avast.com/> protection is active. > > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > sisuite-users mailing list > sis...@li... > https://lists.sourceforge.net/lists/listinfo/sisuite-users > -- ---------------------------------------------- Pierre BLONDEAU Administrateur Systèmes & réseaux Université de Caen Laboratoire GREYC, Département d'informatique tel : 02 31 56 75 42 bureau : Campus 2, Science 3, 406 ---------------------------------------------- |
From: <an...@co...> - 2014-07-13 04:05:21
|
Thanks for the reply! I guess I'm not understanding what you meant. I have a master node (dell01) with CentOS 6.5. This is where I run SI and the UYOK script to generate the initrd/kernel files. Are you saying I should install the "official" network card driver from Broadcom on the master node, create the initrd/kernel and then try imaging on my slave node? Thanks again and you can send to my email if you like also Andy Hi, We have solve this problem by install bnx2 module from the source of broadcrom. The broadcom version works like others modules and not like a "firmware" so it's included with UYOK. Regards Le 12/07/2014 07:02, Andy a écrit : > Hi, > > I'm having issues with SI and using the UYOK feature. It seems to build > the kernel without issue but the network card can't load the firmware. > During the image loading on by slave node I get > > bnx2: Can't load firmware file "bnx2/bnx2-mips-06-6.2.3.fw > > Since it can't find that then in can't grab and IP and the rest fails. > > I'm using systemimager 4.3.0.17 > > When I create the initrd/kernel it seems to work. It creates the > /tmp/.systemimage.0 folder and copies all files needed (including the > firmware tree) to it. > > I run: > > si_prepareclient --server dell01 --include-system-firmware and once > that's complete I copy the initrd and kernel to /tftpboot as the > official names that are pulled up through PXE. > > > > > > ------------------------------------------------------------------------ > <http://www.avast.com/> <http://www.avast.com/%3E>; > > This email is free from viruses and malware because avast! Antivirus > <http://www.avast.com/> <http://www.avast.com/%3E>; protection is active. > > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > sisuite-users mailing list > sisuite-users@... > https://lists.sourceforge.net/lists/listinfo/sisuite-users > -- ---------------------------------------------- |
From: Pierre B. <pie...@un...> - 2014-07-14 10:04:01
Attachments:
smime.p7s
|
Hi, Yes, it's exactly what i try to say. On one cloned client or on the golden client ( or master node if you prefer ) but not image, you install the official driver. For exemple : cd /usr/src/ wget .... unzip bnx2.zip -d bnx2 cd bnx2/Server/Linux/Driver tar zxvf netxtreme2-5.2.55.tar.gz cd netxtreme2-5.2.55 make make install You add the module to the UYOK file : echo "bnx2" >> /etc/systemimager/UYOK.modules_to_include And you regenerate a new initrd with the new driver: LC_ALL=C si_prepareclient --server your.systemimager.server.com --no-rsyncd --my-modules This command is for 4.0.2. If i good remember, it's little change in 4.3 . And you can copy file in /etc/systemimager/boot/* in your tftboot. Remark, it's not necessary to install the driver in "dkms" mode, because when your clone machines restart after the installation of the image, the kernel kernel can use the driver in "firmware mode" because your complete system have it. Regards Le 13/07/2014 06:05, an...@co... a écrit : > Thanks for the reply! I guess I'm not understanding what you meant. I have a master node (dell01) with CentOS 6.5. This is where I run SI and the UYOK script to generate the initrd/kernel files. Are you saying I should install the "official" network card driver from Broadcom on the master node, create the initrd/kernel and then try imaging on my slave node? > > Thanks again and you can send to my email if you like also > > Andy > > > > > Hi, > > We have solve this problem by install bnx2 module from the source of > broadcrom. The broadcom version works like others modules and not like a > "firmware" so it's included with UYOK. > > Regards > > Le 12/07/2014 07:02, Andy a écrit : >> Hi, >> >> I'm having issues with SI and using the UYOK feature. It seems to build >> the kernel without issue but the network card can't load the firmware. >> During the image loading on by slave node I get >> >> bnx2: Can't load firmware file "bnx2/bnx2-mips-06-6.2.3.fw >> >> Since it can't find that then in can't grab and IP and the rest fails. >> >> I'm using systemimager 4.3.0.17 >> >> When I create the initrd/kernel it seems to work. It creates the >> /tmp/.systemimage.0 folder and copies all files needed (including the >> firmware tree) to it. >> >> I run: >> >> si_prepareclient --server dell01 --include-system-firmware and once >> that's complete I copy the initrd and kernel to /tftpboot as the >> official names that are pulled up through PXE. >> >> >> >> >> >> ------------------------------------------------------------------------ >> <http://www.avast.com/> <http://www.avast.com/%3E>; >> >> This email is free from viruses and malware because avast! Antivirus >> <http://www.avast.com/> <http://www.avast.com/%3E>; protection is active. >> >> >> >> >> ------------------------------------------------------------------------------ >> >> >> >> _______________________________________________ >> sisuite-users mailing list >> sisuite-users@... >>https://lists.sourceforge.net/lists/listinfo/sisuite-users >> > > > -- > > ---------------------------------------------- > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > sisuite-users mailing list > sis...@li... > https://lists.sourceforge.net/lists/listinfo/sisuite-users > -- ---------------------------------------------- Pierre BLONDEAU Administrateur Systèmes & réseaux Université de Caen Laboratoire GREYC, Département d'informatique tel : 02 31 56 75 42 bureau : Campus 2, Science 3, 406 ---------------------------------------------- |
From: <an...@co...> - 2014-07-14 14:19:21
|
Thanks, I got it to work just by installing the RPM on the master node. Since Master/Slave nodes are all the same it compiled correctly this time. Now I have one more issue I'm trying to understand. The client connects and starts building. It originally had an issue connecting with RSYNC so I added a statement to allow 192.168.3.0/255.255.255.0 to rsyncd. Well, that statement let the install script format the drives and such and then it comes up again with the access denied. Is there another location where I should put the allow 192.168.3.0/255.255.255.0? I think if I figure that out I'm done! Andy > On July 14, 2014 at 6:03 AM Pierre BLONDEAU <pie...@un...> > wrote: > > > Hi, > > Yes, it's exactly what i try to say. > > On one cloned client or on the golden client ( or master node if you > prefer ) but not image, you install the official driver. > > For exemple : > cd /usr/src/ > wget .... > unzip bnx2.zip -d bnx2 > cd bnx2/Server/Linux/Driver > tar zxvf netxtreme2-5.2.55.tar.gz > cd netxtreme2-5.2.55 > make > make install > > You add the module to the UYOK file : > echo "bnx2" >> /etc/systemimager/UYOK.modules_to_include > > And you regenerate a new initrd with the new driver: > LC_ALL=C si_prepareclient --server your.systemimager.server.com > --no-rsyncd --my-modules > > This command is for 4.0.2. If i good remember, it's little change in 4.3 . > > And you can copy file in /etc/systemimager/boot/* in your tftboot. > > Remark, it's not necessary to install the driver in "dkms" mode, because > when your clone machines restart after the installation of the image, > the kernel kernel can use the driver in "firmware mode" because your > complete system have it. > > Regards > > Le 13/07/2014 06:05, an...@co... a écrit : > > Thanks for the reply! I guess I'm not understanding what you meant. I have a > > master node (dell01) with CentOS 6.5. This is where I run SI and the UYOK > > script to generate the initrd/kernel files. Are you saying I should install > > the "official" network card driver from Broadcom on the master node, create > > the initrd/kernel and then try imaging on my slave node? > > > > Thanks again and you can send to my email if you like also > > > > Andy > > > > > > > > > > Hi, > > > > We have solve this problem by install bnx2 module from the source of > > broadcrom. The broadcom version works like others modules and not like a > > "firmware" so it's included with UYOK. > > > > Regards > > > > Le 12/07/2014 07:02, Andy a écrit : > >> Hi, > >> > >> I'm having issues with SI and using the UYOK feature. It seems to build > >> the kernel without issue but the network card can't load the firmware. > >> During the image loading on by slave node I get > >> > >> bnx2: Can't load firmware file "bnx2/bnx2-mips-06-6.2.3.fw > >> > >> Since it can't find that then in can't grab and IP and the rest fails. > >> > >> I'm using systemimager 4.3.0.17 > >> > >> When I create the initrd/kernel it seems to work. It creates the > >> /tmp/.systemimage.0 folder and copies all files needed (including the > >> firmware tree) to it. > >> > >> I run: > >> > >> si_prepareclient --server dell01 --include-system-firmware and once > >> that's complete I copy the initrd and kernel to /tftpboot as the > >> official names that are pulled up through PXE. > >> > >> > >> > >> > >> > >> ------------------------------------------------------------------------ > >> <http://www.avast.com/> <http://www.avast.com/%3E>; > >> > >> This email is free from viruses and malware because avast! Antivirus > >> <http://www.avast.com/> <http://www.avast.com/%3E>; protection is active. > >> > >> > >> > >> > >> ------------------------------------------------------------------------------ > >> > >> > >> > >> _______________________________________________ > >> sisuite-users mailing list > >> sisuite-users@... > >>https://lists.sourceforge.net/lists/listinfo/sisuite-users > >> > > > > > > -- > > > > ---------------------------------------------- > > > > > > > > ------------------------------------------------------------------------------ > > > > > > > > _______________________________________________ > > sisuite-users mailing list > > sis...@li... > > https://lists.sourceforge.net/lists/listinfo/sisuite-users > > > > > -- > ---------------------------------------------- > Pierre BLONDEAU > Administrateur Systèmes & réseaux > Université de Caen > Laboratoire GREYC, Département d'informatique > > tel : 02 31 56 75 42 > bureau : Campus 2, Science 3, 406 > ---------------------------------------------- > > ------------------------------------------------------------------------------ > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck® > Code Sight™ - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds_______________________________________________ > sisuite-users mailing list > sis...@li... > https://lists.sourceforge.net/lists/listinfo/sisuite-users |