Re: [Unattended] having some problems using v4.3
Adriel Navarro [EMAIL PROTECTED] writes: I tried adding these lines to my unattended file: [MassStorageDrivers] DELL PERC 4/Di RAID Driver for Windows 2000 = OEM [OEMBootFiles] TXTSETUP.OEM MRAID2K.CAT MRAID2K.SYS OEMSETUP.INF NODEV.INF OEMSETUP.INF But I then get this error once I choose what OS to install: do z/site/install failed: Can't use string (See comments for [MassStorageDrivers]) as ARRAY ref while string refs in use at /z/lib/Unattend/IniFile.Pm line 197. Ooops, that is bug. (And thank you for the thorough report.) Fixed in next release. Meanwhile, you can work around it by deleting this line from Z:\dosbin\install.pl: $u-comments ('OEMBootFiles') = 'See comments for [MassStorageDrivers]'; However, you should not need to add any lines to Z:\site\unattend.txt at all. Just populate Z:\os\whatever\i386\$oem$\TEXTMODE with the proper drivers and txtsetup.oem file. Unattended will parse txtsetup.oem and offer to generate the [OEMBootFiles] and [MassStorageDrivers] sections for you automatically. - Pat --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
[Unattended] Compaq/HP DL360/380 Gig interfaces
Title: Compaq/HP DL360/380 Gig interfaces I have two question/problems. 1. I am successfully able to run unattended using a dos floppy with an add on NIC (e10b). This is on a Compaq/HP DL360/380 G3. However when I try to do the same thing with the linux boot cd, it is unable to recognize the hard drive. I Get an error message that states: Found no hard drives (amiraid/ar0 ataraid/d0 cciss/c0d0 iz0/had ida/c0d0 rd/c0d0 had sda hdc) under /sys/block Your /sys/block contains ram0 ram 15. How can I get the linux boot up cd to recognize the hard drives? 2. When I use the dos boot disk on the same servers as above with the integrated gig NICs, I am able to get the DHCP address, but then the server hangs. It is not able to go any further. It displays the ip address and the MAC address and thats all. When I try to do the same thing with the linux boot disk, I am able to make the connection, I just cant see the hard drives. Why does the dos startup hang, but the linux startup work? This is using the Tigon chip, b57, choice for dos and that is what linux cd autodetect. Thanks for whatever help you are able to give. Glen * If you are not the intended recipient of this e-mail, please notify the sender immediately. The contents of this e-mail do not amend any existing disclosures or agreements unless expressly stated. *
Re: [Unattended] Compaq/HP DL360/380 Gig interfaces
Bunting, Glen, IG [EMAIL PROTECTED] writes: I have two question/problems. 1.I am successfully able to run unattended using a dos floppy with an add on NIC (e10b). This is on a Compaq/HP DL360/380 G3. However when I try to do the same thing with the linux boot cd, it is unable to recognize the hard drive. I Get an error message that states: Found no hard drives (amiraid/ar0 ataraid/d0 cciss/c0d0 iz0/had ida/c0d0 rd/c0d0 had sda hdc) under /sys/block Your /sys/block contains ram0 - ram 15. How can I get the linux boot up cd to recognize the hard drives? Is this using a Compaq RAID? My script to decide which drivers to load was buggy. Please try 4.4-test4 at http://unattended.sourceforge.net/testing/ and let me know if it works any better. Failing that, please send me the output of this command: lspci -n | grep 'Class 01' 2. When I use the dos boot disk on the same servers as above with the integrated gig NICs, I am able to get the DHCP address, but then the server hangs. It is not able to go any further. It displays the ip address and the MAC address and that's all. When I try to do the same thing with the linux boot disk, I am able to make the connection, I just can't see the hard drives. Why does the dos startup hang, but the linux startup work? This is using the Tigon chip, b57, choice for dos and that is what linux cd autodetect. Basically, FreeDOS is broken six ways to Sunday. But we cannot distribute MS-DOS. You can copy the files to your own MS-DOS based disk, or you can try messing with the UMB providers in config.sys. (Using umbpci.sys instead of emm386.exe, or *neither*, might help.) I would rather work with you to fix our Linux boot disk. - Pat --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Compaq/HP DL360/380 Gig interfaces
Bunting, Glen, IG [EMAIL PROTECTED] writes: Booting from the 4.4-test cd, I was able to get an ip address, but when I tried to connect to the share, I was unable to. I received a: Unable to connect to share smbmount did not work mount.cifs did not work mount error: could not find target server TCP name not found rc=4 Sorry; I left in some debugging stuff (skipping smbmount to test mount.cifs). Try giving the fully-qualified DNS name of the server, or just using 4.4-test5 which I just uploaded to http://unattended.sourceforge.net/testing/. - Pat --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
RE: [Unattended] Compaq/HP DL360/380 Gig interfaces
Thanks for your quick response. I downloaded the 4.4-test files and burned a new linux boot disk. I copied over the linuxboot zip and extracted it to our Samba server. Booting from the 4.4-test cd, I was able to get an ip address, but when I tried to connect to the share, I was unable to. I received a: Unable to connect to share smbmount did not work mount.cifs did not work mount error: could not find target server TCP name not found rc=4 Booting from the 4.3 linux boot cd, I was able to connect to the share and received the same error as before. Here is the output from lspci -n | grep 'Class 01' 00:0f.1 Class 0101: 1166:0212 (rev93) 01:03.0 Class 0104: 0e11:b178 (rev01) 03:01.0 Class 0104: 0e11:b060 (rev02) Thanks Glen -Original Message- From: Patrick J. LoPresti [mailto:[EMAIL PROTECTED] Sent: Friday, July 30, 2004 12:13 PM To: Bunting, Glen, IG Cc: [EMAIL PROTECTED] Subject: Re: [Unattended] Compaq/HP DL360/380 Gig interfaces Bunting, Glen, IG [EMAIL PROTECTED] writes: I have two question/problems. 1.I am successfully able to run unattended using a dos floppy with an add on NIC (e10b). This is on a Compaq/HP DL360/380 G3. However when I try to do the same thing with the linux boot cd, it is unable to recognize the hard drive. I Get an error message that states: Found no hard drives (amiraid/ar0 ataraid/d0 cciss/c0d0 iz0/had ida/c0d0 rd/c0d0 had sda hdc) under /sys/block Your /sys/block contains ram0 - ram 15. How can I get the linux boot up cd to recognize the hard drives? Is this using a Compaq RAID? My script to decide which drivers to load was buggy. Please try 4.4-test4 at http://unattended.sourceforge.net/testing/ and let me know if it works any better. Failing that, please send me the output of this command: lspci -n | grep 'Class 01' 2. When I use the dos boot disk on the same servers as above with the integrated gig NICs, I am able to get the DHCP address, but then the server hangs. It is not able to go any further. It displays the ip address and the MAC address and that's all. When I try to do the same thing with the linux boot disk, I am able to make the connection, I just can't see the hard drives. Why does the dos startup hang, but the linux startup work? This is using the Tigon chip, b57, choice for dos and that is what linux cd autodetect. Basically, FreeDOS is broken six ways to Sunday. But we cannot distribute MS-DOS. You can copy the files to your own MS-DOS based disk, or you can try messing with the UMB providers in config.sys. (Using umbpci.sys instead of emm386.exe, or *neither*, might help.) I would rather work with you to fix our Linux boot disk. - Pat * If you are not the intended recipient of this e-mail, please notify the sender immediately. The contents of this e-mail do not amend any existing disclosures or agreements unless expressly stated. * --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info