[Unattended] Downloading Drivers with config.pl Returns unmatch Hardware

[Pierre Bourgin]

Hi,

hello,

However, I follow this guide and try to reduce space but no drivers were
Please note that I use the ../unattended-4.9/install/site/sample-config.pl and
renamed config.pl to make it work. However, due to "unmatch(ed)" hardware, no
drivers were downloaded? I have tried in two (foxconn D51S & Jetway NF77) MBs
and that the results are the same.
Q1. What am I doing wrong?
Q2. How can I make config.pl to match?
Thanks!

Wrong: you try to mix different solutions.

search-win-drivers.pl, that produces the file netinst/logs/drivers.log
is a kind of hardware scanner (as shown in the drivers.log output file).

What you have to do for using search-win-drivers.pl is to download and
install DriverPacks.net archive files and unpack them onto your
installation server, below /z/drivers/.

Then, search-win-drivers.pl will scan your hardware platform and try to
figure out which drivers, among the one present below /z/drivers/, may
match.
All these "good candidates" drivers (and only those) will then be copied
onto the hard drive by Unattended, in order that Windows setup uses them
during Windows installation.

Once Windows finished gets installed, check again file
C:\netinst\logs\drivers.log to see the differences.
Also check which drivers may miss in the /z/drivers repository for your
hardware platform by checking compmgmt.msc (hardware devices).


See also this link for more informations regarding search-win-drivers.pl:

http://sourceforge.net/apps/trac/unattended/wiki/AutodetectDrivers


Regards,

Pierre Bourgin

# Check root paths of Windows drivers...
# Windows drivers collections to use: /z/drivers
# - Check PCI devices (via lspci output command)...
# found 15 PCI device(s) on current hardware platform.
# - Check HDAUDIO devices...
# found 1 HDaudio codec (on 1 sound card).
# - Check USB devices...
# found 0 USB usable devices on current hardware platform.
# - desc=Intel Corporation Pineview DMI Bridge (rev 02)
# bustype=PCI busid=00:00.0 vendor=8086 device=a000 class=0600 subsys=0d55105b
# infstr=PCI\VEN_8086&DEV_a000&SUBSYS_0d55105b
# - desc=Intel Corporation Pineview Integrated Graphics Controller (rev 02)
# bustype=PCI busid=00:02.0 vendor=8086 device=a001 class=0300 subsys=0d55105b
# infstr=PCI\VEN_8086&DEV_a001&SUBSYS_0d55105b
# - <snip>
# - desc=Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit
Ethernet controller (rev 03)
# bustype=PCI busid=02:00.0 vendor=10ec device=8168 class=0200 subsys=0d55105b
# infstr=PCI\VEN_10ec&DEV_8168&SUBSYS_0d55105b
# - desc=Realtek ALC662 rev1
# bustype=HDAUDIO busid=2 vendor=10ec device=0662 class= subsys=105b0d55
# infstr=HDAUDIO\FUNC_01&VEN_10ec&DEV_0662&SUBSYS_105b0d55
# 16 distinct hardware devices to consider.
#
# loading INF strings from Windows drivers collection...
# - path: /z/drivers
# Parse .INF files below folder /z/drivers ...
# - parsed 0 .INF files, added 0 INF strings. (no cache)
#
# Search matching drivers for current hardware platform...
#
# Unmatched devices: 16 devices
# - They do not match even without their SubSystem part
# - they might be handled directly by Windows or indirectly by the matching
drivers.
# unmatch: PCI\VEN_8086&DEV_a000&SUBSYS_0d55105b (desc: 'Intel Corporation
Pineview DMI Bridge (rev 02)')
# unmatch: PCI\VEN_8086&DEV_a001&SUBSYS_0d55105b (desc: 'Intel Corporation
Pineview Integrated Graphics Controller (rev 02)')
# unmatch: PCI\VEN_8086&DEV_27d8&SUBSYS_0d55105b (desc: 'Intel Corporation
82801G (ICH7 Family) High Definition Audio Controller (rev 02)')
# unmatch: PCI\VEN_8086&DEV_27d0 (desc: 'Intel Corporation 82801G (ICH7 Family)
PCI Express Port 1 (rev 02)')
# <snip>
# unmatch: PCI\VEN_8086&DEV_27c8&SUBSYS_0d55105b (desc: 'Intel Corporation
82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)')
# <snip>
# unmatch: PCI\VEN_10ec&DEV_8168&SUBSYS_0d55105b (desc: 'Realtek Semiconductor
Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)')
# unmatch: HDAUDIO\FUNC_01&VEN_10ec&DEV_0662&SUBSYS_105b0d55 (desc: 'Realtek
ALC662 rev1')

[n22e113]

Hi, Pierre, Thanks for your detailed reply.

Post by Pierre Bourgin
search-win-drivers.pl, that produces the file netinst/logs/drivers.log
is a kind of hardware scanner (as shown in the drivers.log output file).

Okay! I reinstalled unattended-4.9 on our samba server as follows:
cd /usr/src/ && unzip unattended-4.9.zip && unzip
unattended-4.9-linuxboot.zip
cd /usr/src/unattended-4.9/install/tools/
./script-update && ./prepare && cd ../drives
# Extract using 7zr all dp_*.7z files

If I run search-win-drivers.pl on my samba server:
cd /usr/src/unattended-4.9/install/dosbin
./search-win-drivers.pl -d ../drivers

I was successful in getting the following:
# 16 distinct hardware devices to consider.
#
# loading INF strings from Windows drivers collection...
# - path: /usr/src/unattended-4.9/install/dosbin/../drivers
# Parse .INF files below folder
/usr/src/unattended-4.9/install/dosbin/../drivers ...
# - parsed 592 .INF files, added 17587 INF strings. (no cache)
#
# Search matching drivers for current hardware platform...
# 7 driver folders to use:
/usr/src/unattended-4.9/install/dosbin/../drivers/D/C/U
/usr/src/unattended-4.9/install/dosbin/../drivers/D/C/V
/usr/src/unattended-4.9/install/dosbin/../drivers/D/C/V2
/usr/src/unattended-4.9/install/dosbin/../drivers/D/C/V3
/usr/src/unattended-4.9/install/dosbin/../drivers/D/C/VX
/usr/src/unattended-4.9/install/dosbin/../drivers/D/L/V1
/usr/src/unattended-4.9/install/dosbin/../drivers/D/M/V3

It tells me that the search-win-drivers.pl works as expected. However,
if I try to install using the pxe + linuxboot method, it fails to search
for drivers and return 0 driver/folder to use:
# Search matching drivers for current hardware platform...
# 0 driver folders to use:

I also copied ../os/winxpsp3/I386 and using a pristine OEM version of XP
+ SP3 (no nLite, RyanVM, etc.) with sample-config.pl copied to
../site/config.pl. Contents of unattend.txt didn't matter at this point
as nt5x-install has not been called yet, no?
Thanks,
Kwon

[n22e113]

Houston, I found the problem:
My {unattended}/install/drivers/D has permission 700! After extracting
(7zr x dp_*.7z) and changing the directory access:
chmod 2755 -R {unattended}/install/drivers/D
It now works as expected. Hope this help someone else!
Q. Is there an existing utility of which can automatically extract
dp_*.7z drivers and set their proper permissions in /z/drivers/D? Thanks!
Cheers,
Kwon

[Juanjo Pablos]

Post by n22e113
Q. Is there an existing utility of which can automatically extract
dp_*.7z drivers and set their proper permissions in /z/drivers/D? Thanks!

try :
cd unattended
ant extract-drivers

That is what I use

[n22e113]

Post by Juanjo Pablos

Post by n22e113
Q. Is there an existing utility of which can automatically extract
dp_*.7z drivers and set their proper permissions in /z/drivers/D? Thanks!

cd unattended
ant extract-drivers
That is what I use

Hi, Juanjo,
But don't have ant and don't have extract-drivers in the 4.9 distro? I
am using Pierre Bourgin's method which works nicely. Thanks again.

[Pierre Bourgin]

Post by n22e113
My {unattended}/install/drivers/D has permission 700! After extracting
chmod 2755 -R {unattended}/install/drivers/D
It now works as expected. Hope this help someone else!
Q. Is there an existing utility of which can automatically extract
dp_*.7z drivers and set their proper permissions in /z/drivers/D?

No, I have the same problem: in my notes, I have:
$ find <driverPackDir> -type d -exec chmod 755 {} \;
$ find <driverPackDir> -type f -exec chmod 644 {} \;

By the way, did you generate a cache file for your drivers ?
It provides a significant increase of driver search speed:

$ cd <driverPackDir>
$ /path/to/unattended/dosbin/search-win-drivers.pl -g . > ./search-win-drivers.cache

(The cache file has to be regenerated each time you modify anything in the corresponding folder).

Cheers,
Pierre,

[n22e113]

$ find<driverPackDir> -type d -exec chmod 755 {} \;
$ find<driverPackDir> -type f -exec chmod 644 {} \;
By the way, did you generate a cache file for your drivers ?
$ cd<driverPackDir>
$ /path/to/unattended/dosbin/search-win-drivers.pl -g .> ./search-win-drivers.cache
(The cache file has to be regenerated each time you modify anything in the corresponding folder).

Hi, Pierre,
Spent the whole weekend as according to your instructions. All works now
and thanks.

[Juanjo Pablos]

It would be nice if this info get added to the wiki

https://sourceforge.net/apps/trac/unattended/wiki/AutodetectDrivers

Post by n22e113

$ find<driverPackDir> -type d -exec chmod 755 {} \;
$ find<driverPackDir> -type f -exec chmod 644 {} \;
By the way, did you generate a cache file for your drivers ?
$ cd<driverPackDir>
$ /path/to/unattended/dosbin/search-win-drivers.pl -g .> ./search-win-drivers.cache
(The cache file has to be regenerated each time you modify anything in the corresponding folder).

Hi, Pierre,
Spent the whole weekend as according to your instructions. All works now
and thanks.
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
unattended-info mailing list
https://lists.sourceforge.net/lists/listinfo/unattended-info