[driverloader] print $1, exit Error

Marc Boucher marc at linuxant.com
Tue Jan 13 18:36:30 EST 2004

Hi Nick,

On Jan 13, 2004, at 6:10 PM, Nick Marques wrote:

> I still can’t set my mode to Ad-hoc… no one can help??

Does it work under 2.4?

In any case, please send the output of dldrconfig --dumpdiag to 
support at linuxant.com
and also the kernel messages generated when trying to set the mode to 
Ad-hoc would be helpful to diagnose the problem.
It might be necessary to boot the system with a serial console and use 
"dmesg -n8"
before the crash to capture these messages.

> I also get an error saying print $1, exit and command not found every 
> time driverloader or dldrconfig is run… I get it like 4 times when the 
> kernel boots… Why??

Under Slackware, dldrconfig's identify_system() function uses the AWK 
variable which unfortunately happens to be initialized after the 
function is called.

As a quick fix, I would suggest editing /usr/sbin/dldrconfig and moving 
the following lines (1521-1525)

if which gawk >/dev/null 2>&1; then

to just before the

identify_system >/dev/null

call (line 1445).

We'll fix this issue in the next version.


More information about the driverloader mailing list