Re: [Cooker] /usr/lib/libDrakX/detect_devices.pm bug ?

2002-08-11 Thread Pixel

rcc [EMAIL PROTECTED] writes:

 85:eval { modules::load(floppy) };

[...]

 this is just a quick hack but it works here, draktools used to segfault
 before, they don't anymore and floppy gets loaded if present,

i just fixed it in CVS.

it goes along with latest modules.pm which ignores unknown modules.
so my pb regarding floppy.o not existing in the kernel goes away.




Re: [Cooker] /usr/lib/libDrakX/detect_devices.pm bug ?

2002-08-11 Thread Xavier Granier

Le Dimanche 11 Août 2002 11:39, Pixel a écrit :
 rcc [EMAIL PROTECTED] writes:
  85:eval { modules::load(floppy) };

 [...]

  this is just a quick hack but it works here, draktools used to segfault
  before, they don't anymore and floppy gets loaded if present,

 i just fixed it in CVS.

 it goes along with latest modules.pm which ignores unknown modules.
 so my pb regarding floppy.o not existing in the kernel goes away.

it's working now : thanks a lot (I will be more confident to do an updgrade
to 9.0) and good job

X

-- 
+-
|Xavier Granier, IMAGER, Post-doc
|Department of Computer Science, The University of British Columbia
|Address : 201-2366 Main Mall Vancouver, B.C. V6T 1Z4 , Canada
|Mail: [EMAIL PROTECTED], Phone: 1-604-822-8158 , Fax: 1-604-822-5485
|http://www.cs.ubc.ca/~xgranier/
+-




Re: [Cooker] /usr/lib/libDrakX/detect_devices.pm bug ?

2002-08-10 Thread Pixel

rcc [EMAIL PROTECTED] writes:

 detect_devices.pm:
 
 83: sub floppies() {
 84:require modules;
 85:eval { modules::load(floppy) };
return if $@; --- new
 
 
 this is just a quick hack but it works here, draktools used to segfault
 before, they don't anymore and floppy gets loaded if present,

rcc does it still do the same with the new kernel?

i've been trying to reproduce, but no luck (disabling the floppy
controller in bios makes the floppy unusable, but floppy.o still
modprobes)

otherwise i'll go the way to check if the module exist and the
insmod fails.




Re: [Cooker] /usr/lib/libDrakX/detect_devices.pm bug ?

2002-08-10 Thread rcc

On 10 Aug 2002 14:21:15 +0200
Pixel [EMAIL PROTECTED] wrote:

 rcc [EMAIL PROTECTED] writes:
  detect_devices.pm:
  
  83: sub floppies() {
  84:require modules;
  85:eval { modules::load(floppy) };
 return if $@; --- new

that's the old version, doing this will prevent zip and scsi stuff, but
you know that
 
 rcc does it still do the same with the new kernel?

partly, yes
 
 i've been trying to reproduce, but no luck (disabling the floppy
 controller in bios makes the floppy unusable, but floppy.o still
 modprobes)

I've tried two things with the new kernel:

1) disable just the controller in bios, ie Onboard FDD - disabled
- insmod fails and drakconf enters an endless loop

2) disable the floppy too, ie Floppy A - none
- insmod fails but drakconf starts

 otherwise i'll go the way to check if the module exist and the
 insmod fails.

I think checking if insmod failed and if yes subsequently skipping all
floppy.o related stuff might be good. The problem is not that relevant
for me but the other poster told of Laptops that have those drive slots
that hold either a floppy or a cdrom. I cannot tell what bios does on
these machines.

- Mark





Re: [Cooker] /usr/lib/libDrakX/detect_devices.pm bug ?

2002-08-10 Thread Xavier Granier

Le Samedi 10 Août 2002 05:21, Pixel a écrit :
 rcc [EMAIL PROTECTED] writes:
  detect_devices.pm:
 
  83: sub floppies() {
  84:require modules;
  85:eval { modules::load(floppy) };
 return if $@; --- new
 
 
  this is just a quick hack but it works here, draktools used to segfault
  before, they don't anymore and floppy gets loaded if present,

 rcc does it still do the same with the new kernel?

 i've been trying to reproduce, but no luck (disabling the floppy
 controller in bios makes the floppy unusable, but floppy.o still
 modprobes)

 otherwise i'll go the way to check if the module exist and the
 insmod fails.

the problems is still here
with kernel 2.4.19-1

# harddrake start
Recherche de nouveaux périphériquesHint: insmod errors can be caused by 
incorrect module parameters, including invalid IO or IRQ parameters.
  You may find more information in syslog or the output from dmesg
/etc/init.d//harddrake: line 53:  1976 Segmentation fault  
/usr/share/harddrake/service_harddrake 2/dev/null
[ERREUR]

one solution that I've found is (after the suggestion of rcc) is
sub floppies() {
require modules;
eval { modules::load(floppy) };
if (!$@) {
my @fds = map {
my $info = (!dev_is_devfs() || -e /dev/fd$_)  
c::floppy_info(devices::make(fd$_));
if_($info  $info ne '(null)', { device = fd$_, devfs_device 
= floppy/$_, media_type = 'fd', info = $info })
} qw(0 1);
}

# harddrake start
Recherche de nouveaux périphériquesHint: insmod errors can be caused by 
incorrect module parameters, including invalid IO or IRQ parameters.
  You may find more information in syslog or the output from dmesg
[  OK  ]


-- 
+-
|Xavier Granier, IMAGER, Post-doc
|Department of Computer Science, The University of British Columbia
|Address : 201-2366 Main Mall Vancouver, B.C. V6T 1Z4 , Canada
|Mail: [EMAIL PROTECTED], Phone: 1-604-822-8158 , Fax: 1-604-822-5485
|http://www.cs.ubc.ca/~xgranier/
+-