I was trying to make an image that would work with all our systems, but have run into a problem.
At first I tried building everything, and that seemed to work, but we have a lab with most machines have 3com cards, but some have the on board 8139 cards. The auto script fails with a udpc spript problem. You can press the esc key and go back, and it shows the 8139cp and the 8139too. It you select the 8139too, and click on, it will go thru, and eventually work, but requires enters on everything. I don't think we have anything with 8139cp cards, so I went back and redid the build, but this time I unchecked the 8139cp. Redid the process and got the same results. It doesn't seem to have the 8139cp.ko file, but it still seems to try it.
All the machines had 3com cards, but a couple have failed, so we switched those to use the onboard, which seems to be as good.
+----------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor Guam Community College Computer Center mailto:mikes@kuentos.guam.net mailto:msetzerii@gmail.com http://www.guam.net/home/mikes Guam - Where America's Day Begins +----------------------------------------------------------+
http://setiathome.berkeley.edu (Original) Number of Seti Units Returned: 19,471 Processing time: 32 years, 290 days, 12 hours, 58 minutes (Total Hours: 287,489)
BOINC@HOME CREDITS SETI 6,887,276.9695 | EINSTEIN 2,134,564.5709 | ROSETTA 694,861.8863
Michael D. Setzer II wrote:
I was trying to make an image that would work with all our systems, but have run into a problem.
At first I tried building everything, and that seemed to work, but we have a lab with most machines have 3com cards, but some have the on board 8139 cards. The auto script fails with a udpc spript problem. You can press the esc key and go back, and it shows the 8139cp and the 8139too. It you select the 8139too, and click on, it will go thru, and eventually work, but requires enters on everything. I don't think we have anything with 8139cp cards, so I went back and redid the build, but this time I unchecked the 8139cp. Redid the process and got the same results. It doesn't seem to have the 8139cp.ko file, but it still seems to try it.
All the machines had 3com cards, but a couple have failed, so we switched those to use the onboard, which seems to be as good.
Yes, by default the Udpcast boot menu includes in its suggestion _all_ drivers that match the current card, even if they are not present on the boot media. This was intended to make it possible to have modules on a second disk.
In today's version, I changed it so that all drivers are still listed, but that those that are present on the media come first. So leaving away troublesome drivers should work now
Regards,
Alain
-
Alain Knaff -
Michael D. Setzer II