Re: [Unattended] unattended-gui boot-cd 0.5.1
Hi have you try the force options? http://unattended.technikz.de/index.php/Bootcd:options#force Ah, wonderful, thanks. This did the trick. :) Now it finally finds the harddrive. Now I'm facing the next bunch of problems though. -.- Will post to the list if I can't fix them myself. ;) - jens - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] unattended-gui boot-cd 0.5.1
Hi have you try the force options? http://unattended.technikz.de/index.php/Bootcd:options#force greetings mario Am Mittwoch, den 05.12.2007, 15:33 +0100 schrieb Jens Geile: Is it having problems finding the SATA device during the linux portion of unattended setup, or during the Windows portion? During the Linux portion... if it was during the Windows portion I'd know what to do... The message I get is: Unable to determine boot device at /usr/bin/find-boot-device line 212. - Please enter only the device string (e.g. hda or sdb) A fdisk -l also returns no drives. When using an older unattended boot-cd (sadly not compatible with other changes to the system, thus i kinda need the new boot-cd) or a Knoppix 5.1 CD the drive is properly found and identified. - jens - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] unattended-gui boot-cd 0.5.1
Is it having problems finding the SATA device during the linux portion of unattended setup, or during the Windows portion? During the Linux portion... if it was during the Windows portion I'd know what to do... The message I get is: Unable to determine boot device at /usr/bin/find-boot-device line 212. - Please enter only the device string (e.g. hda or sdb) A fdisk -l also returns no drives. When using an older unattended boot-cd (sadly not compatible with other changes to the system, thus i kinda need the new boot-cd) or a Knoppix 5.1 CD the drive is properly found and identified. - jens - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] unattended-gui boot-cd 0.5.1
A nicer way of fixing this problem (I remember now - I fixed a similar problem with our Dell systems), is to extract the uaroot file onto a linux filesystem, and edit etc/master. Under the function setup_hw () heading, insert a modprobe module_name line for each module that needs to load but doesn't get detected by hqsetup (you'll need to put these lines after hwsetup -a -v). You'll then need to recompile uaroot and then reburn the disc/remaster to ISO. That's my way - I think it's better than force loading all modules... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jens Geile Sent: 05 December 2007 15:06 To: unattended-info@lists.sourceforge.net; Mario Gzuk; [EMAIL PROTECTED] Subject: Re: [Unattended] unattended-gui boot-cd 0.5.1 Hi have you try the force options? http://unattended.technikz.de/index.php/Bootcd:options#force Ah, wonderful, thanks. This did the trick. :) Now it finally finds the harddrive. Now I'm facing the next bunch of problems though. -.- Will post to the list if I can't fix them myself. ;) - jens - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] unattended-gui boot-cd 0.5.1
Is it having problems finding the SATA device during the linux portion of unattended setup, or during the Windows portion? If it's during the Windows portion, you need to 'hack' WINNT.SIF and insert your SATA drivers in there, so that Windows thinks it's one of the build-in drivers and installs it during Textmode setup. It's equivalent to pressing F6 during setup. See my attached email to Markus Progl on the same subject - you'll need to modify my changes for your own SATA device. Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jens Geile Sent: 05 December 2007 10:17 To: unattended-info@lists.sourceforge.net; Sebastian Mellmann; [EMAIL PROTECTED] Subject: Re: [Unattended] unattended-gui boot-cd 0.5.1 Hi, sorry for the delay. Just came back to work. I've just tried the unattended-gui boot-cd 0.5.1 and immediately ran into a major problem ... it doesn't find my sata hdd. The board is a MSI K9VGM-V (http://global.msi.com.tw/index.php?func=proddescprod_no=260maincat_no =1) with a VIA VT8237A chipset. I'd really appreciate it if I/we could get an updated version of the boot cd asap (it's kinda urgent for me since I have a presentation on the 14th and everything has to work at that point -.-). Try switching to SATA legacy mode in the BIOS. This option doesn't seem to exist in this BIOS. On the other hand the kernel should know that chipset. Yeah, thought that too. And with older Boot-CDs it worked like a charm... never change a running system :/ What does 'dmesg' say? Nothing too suspicious... http://pastebin.com/f5474f0bd - jens - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info ---BeginMessage--- Hi Markus, Yes, I have just about got the 755s working now. I am currently using Mario's ua-0.5.0 ISO image (because the 0.5.1 has a kernel bug which cuts off characters from the APPEND string, which is how I pass the unattended username, password and location to unattended). To get the SATA drivers working correctly, you'll need to set the SATA device to AHCI mode (the default when it comes from Dell I think), and then hack the TXTSETUP.SIF file to make Windows think it already has drivers for the SATA device (this is equivalent to pressing F6 while starting text-mode setup). TXTSETUP.SIF can be found in the I386 folder. The following additions should be made to the file (you do not need to add the headings in square brackets - but you do need to ensure that the correct lines go under the correct headings (preferably at the end so it's easy to see)): [SourceDisksFiles] iaStor.sys = 100,,3_,4,1,,,1,4 [HardwareIdsDatabase] PCI\VEN_8086DEV_2922CC_0106 = iaStor PCI\VEN_8086DEV_282ACC_0104 = iaStor PCI\VEN_8086DEV_2829CC_0106 = iaStor PCI\VEN_8086DEV_2822CC_0104 = iaStor PCI\VEN_8086DEV_2821CC_0106 = iaStor PCI\VEN_8086DEV_2682CC_0104 = iaStor PCI\VEN_8086DEV_2681CC_0106 = iaStor PCI\VEN_8086DEV_27C3CC_0104 = iaStor PCI\VEN_8086DEV_27C6CC_0104 = iaStor PCI\VEN_8086DEV_27C1CC_0106 = iaStor PCI\VEN_8086DEV_27C5CC_0106 = iaStor PCI\VEN_8086DEV_2653CC_0106 = iaStor [SCSI.Load] iastor = iastor.sys,4 [SCSI] iastor = Intel(R) ICH9 SATA AHCI Controller (Desktop/Server/Workstation) iastor = Intel(R) 82801HEM SATA RAID Controller (Mobile ICH8M-E) iastor = Intel(R) 82801HEM/HBM SATA AHCI Controller (Mobile ICH8M-E/M) iastor = Intel(R) ICH8R/ICH9R SATA RAID Controller (Desktop/Server/Workstation) iastor = Intel(R) 82801HR/HH/HO SATA AHCI Controller (Desktop/Server/Workstation) iastor = Intel(R) 631xESB/632xESB SATA RAID Controller (Server/Workstation ESB2) iastor = Intel(R) 631xESB/632xESB SATA AHCI Controller (Server/Workstation ESB2) iastor = Intel(R) 82801GHM SATA RAID Controller (Mobile ICH7MDH) iastor = Intel(R) 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH) iastor = Intel(R) 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH) iastor = Intel(R) 82801GBM SATA AHCI Controller (Mobile ICH7M/DH) iastor = Intel(R) 82801FBM SATA AHCI Controller (Mobile ICH6M) You can copy and paste the extracts above into your TXTSETUP.SIF, and that should work for your 755s. If not, you can extract the information needed for above from the TXTSETUP.OEM file which is found in the same folder as the Windows XP drivers for the SATA device. The drivers for the SATA device should then be placed in the I386\$oem$\$1\Drivers\01 folder. You will then need to add a line to the unattended answer file (usually WINNT.SIF, but with unattended-gui, it's in the Web interface, under [Unattended] -- OEM PNP Drivers path - make sure you enclose in quotes
