From: Heiko Z. <he...@zu...> - 2007-10-30 00:28:46
|
Hey, I'm moving this discussion to the develop mailinglist. On Mon, October 29, 2007 18:41, Bruce Smith wrote: > Serge Leschinsky wrote: > >> Thank you! If somebody wants to build custom iso from CVS, the >> following options help him to avoid compilation errors ( all other >> options may be enabled ) >> >> CONFIG_ALSA=n >> CONFIG_CLAMAV_PATCH=n >> CONFIG_DISTCCD=n >> CONFIG_EAGLE_USB=n >> CONFIG_GRSECURITY=n >> CONFIG_L2TPD=n >> CONFIG_NCFTP=n >> CONFIG_PORTSLAVE=n >> CONFIG_RPM=n >> CONFIG_USE_DISTCC=n >> >> > > Thanks for the tips. > > > I just completed a compile, then I did a build and install of ncftp > manually (./build.sh build opt=ncftp) and it appeared to compile fine. Yeah most of the packages compile now. These are the ones I have disabled: CONFIG_ALSA=n CONFIG_AOE6=n CONFIG_CLAMAV_PATCH=n CONFIG_DISABLELOGGING=n CONFIG_DISTCCD=n CONFIG_EAGLE_USB=n CONFIG_GRSECURITY=n CONFIG_L2TPD=n CONFIG_LINUX_SYSRQ=n CONFIG_PORTSLAVE=n CONFIG_RPM=n CONFIG_USE_DISTCC=n > One other problem I ran into was I had to turn set "AOE6=n" since it's > build aborted. Yes that's correct. The package is lacking support for the latest kernel. I got a few updates I have to upload, I'll probably do that tonight. -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Heiko Z. <he...@zu...> - 2007-10-30 18:22:28
|
On Tue, October 30, 2007 13:09, Bruce Smith wrote: > OK, I have the latest 1.3 running on a real PC, connected to the > Internet with a static IP. It didn't have any problem finding my IDE > CDROM drive (/dev/hdc). > > > I have it setup with the standard 2NIC firewall, running a DHCP server > on the internal network. NAT works fine, as I can connect to the internet > with my laptop, using the 1.3 DL box as my firewall. > > I am having a weird problem with networking. sshd wouldn't start. It > kept complaining that the port 0.0.0.0:22 was already in use. I changed > the port it listens on to a high number, and it still gave the same error > (with the new port number). 'netstat -aepn' shows NO TCP > connections listening at all, only UDP and RAW listening for dhcpd. > > I changed sshd_config to manually specify the IP addresses of both NIC's > and now sshd starts fine. > > I tried starting apache2 (std config). It started and I can connect to > it w/Firefox. However a 'netstat -aepn' doesn't show it listening on port > 80, but instead shows a STREAM listening for httpd. > > > I removed IPV6 routing from the config, with no difference. > > > Something is really weird ... Ideas??? I'm using samba and ssh on my virtual machine which is running DL 1.3, no such trouble. Although I don't have the firewall enabled. Can you disconnect the box from the web and try without firewall? -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Serge L. <fi...@in...> - 2007-10-30 18:30:23
|
Hi Bruce, Bruce Smith wrote: > OK, I have the latest 1.3 running on a real PC, connected to the > Internet with a static IP. It didn't have any problem finding my IDE > CDROM drive (/dev/hdc). /dev/hdc ? Are you sure ? I'm requesting because PATA devices which work through libata represent themselvs as SCSI (SATA) /dev/sdx... .... > I tried starting apache2 (std config). It started and I can connect to > it w/Firefox. However a 'netstat -aepn' doesn't show it listening on > port 80, but instead shows a STREAM listening for httpd. > > I removed IPV6 routing from the config, with no difference. > > Something is really weird ... Ideas??? No ideas yet. I'll check it tomorrow. -- Sincerely, Serge Leschinsky |
From: Bruce S. <bw...@ar...> - 2007-10-30 18:34:48
|
> > I have it setup with the standard 2NIC firewall, running a DHCP server > > on the internal network. NAT works fine, as I can connect to the internet > > with my laptop, using the 1.3 DL box as my firewall. > > > > I am having a weird problem with networking. sshd wouldn't start. It > > kept complaining that the port 0.0.0.0:22 was already in use. I changed > > the port it listens on to a high number, and it still gave the same error > > (with the new port number). 'netstat -aepn' shows NO TCP > > connections listening at all, only UDP and RAW listening for dhcpd. > > > > I changed sshd_config to manually specify the IP addresses of both NIC's > > and now sshd starts fine. > > > > I removed IPV6 routing from the config, with no difference. > > > > Something is really weird ... Ideas??? > > I'm using samba and ssh on my virtual machine which is running DL 1.3, no > such trouble. Although I don't have the firewall enabled. > > Can you disconnect the box from the web and try without firewall? I just tried starting sshd in my VMware copy (brand new default config), and got the same error in tty10: Bind to port 22 on 0.0.0.0 failed: Address already in use. I did learn that if I uncomment this line in sshd_config, it works: ListenAddress :: OR, if I add this line in sshd_config (instead), it works: AddressFamily inet OpenSSH problem? Are you running the same version of ssh in your DL 1.3 (4.7p1)? - BS |
From: Bruce S. <bw...@ar...> - 2007-10-30 18:38:36
|
> > OK, I have the latest 1.3 running on a real PC, connected to the > > Internet with a static IP. It didn't have any problem finding my IDE > > CDROM drive (/dev/hdc). > /dev/hdc ? Are you sure ? I'm requesting because PATA devices which work through > libata represent themselvs as SCSI (SATA) /dev/sdx... It says hdc when it boots, and so does 'df' (copy/paste): root@Devil:~ # df Filesystem 1K-blocks Used Available Use% Mounted on rootfs 266046 266046 0 100% / none 257504 9132 248372 4% /shm /dev/hdc 266046 266046 0 100% / none 257504 9132 248372 4% /dev root@Devil:~ # cat /DEVIL-LINUX 1.3.4-2007-10-30 root@Devil:~ # uname -a Linux Devil 2.6.23.1 #1 SMP Tue Oct 30 08:32:52... - BS |
From: Heiko Z. <he...@zu...> - 2007-10-30 18:41:20
|
Hey, yes I have the same version. I checked my config file and I already had the entries commented out, that's probably why it worked. Maybe we should comment it out in our default config (do you have time to do it?). Heiko On Tue, October 30, 2007 13:34, Bruce Smith wrote: >>> I have it setup with the standard 2NIC firewall, running a DHCP >>> server on the internal network. NAT works fine, as I can connect to >>> the internet with my laptop, using the 1.3 DL box as my firewall. >>> >>> I am having a weird problem with networking. sshd wouldn't start. >>> It >>> kept complaining that the port 0.0.0.0:22 was already in use. I >>> changed the port it listens on to a high number, and it still gave the >>> same error (with the new port number). 'netstat -aepn' shows NO TCP >>> connections listening at all, only UDP and RAW listening for dhcpd. >>> >>> I changed sshd_config to manually specify the IP addresses of both >>> NIC's >>> and now sshd starts fine. >>> >>> I removed IPV6 routing from the config, with no difference. >>> >>> >>> Something is really weird ... Ideas??? >>> >> >> I'm using samba and ssh on my virtual machine which is running DL 1.3, >> no such trouble. Although I don't have the firewall enabled. >> >> Can you disconnect the box from the web and try without firewall? >> > > I just tried starting sshd in my VMware copy (brand new default config), > and got the same error in tty10: > > Bind to port 22 on 0.0.0.0 failed: Address already in use. > > > I did learn that if I uncomment this line in sshd_config, it works: > > > ListenAddress :: > > > OR, if I add this line in sshd_config (instead), it works: > > > AddressFamily inet > > > OpenSSH problem? > Are you running the same version of ssh in your DL 1.3 (4.7p1)? > > > - BS > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > > -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Bruce S. <bw...@ar...> - 2007-10-30 18:47:24
|
> yes I have the same version. > I checked my config file and I already had the entries commented out, > that's probably why it worked. > > Maybe we should comment it out in our default config (do you have time to > do it?). They are commented out by default, and they should be. I had to UNCOMMENT them (one or the other, but not both) to make sshd start. Also, when I uncommented 'AddressFamily', I had to change the parameter to 'inet' (IPV4), from the default setting of 'any'. This is some weird IPv4 vs. IPv6 problem with SSH and the way we have our network configured. - BS > >>> I have it setup with the standard 2NIC firewall, running a DHCP > >>> server on the internal network. NAT works fine, as I can connect to > >>> the internet with my laptop, using the 1.3 DL box as my firewall. > >>> > >>> I am having a weird problem with networking. sshd wouldn't start. > >>> It > >>> kept complaining that the port 0.0.0.0:22 was already in use. I > >>> changed the port it listens on to a high number, and it still gave the > >>> same error (with the new port number). 'netstat -aepn' shows NO TCP > >>> connections listening at all, only UDP and RAW listening for dhcpd. > >>> > >>> I changed sshd_config to manually specify the IP addresses of both > >>> NIC's > >>> and now sshd starts fine. > >>> > >>> I removed IPV6 routing from the config, with no difference. > >>> > >>> > >>> Something is really weird ... Ideas??? > >>> > >> > >> I'm using samba and ssh on my virtual machine which is running DL 1.3, > >> no such trouble. Although I don't have the firewall enabled. > >> > >> Can you disconnect the box from the web and try without firewall? > >> > > > > I just tried starting sshd in my VMware copy (brand new default config), > > and got the same error in tty10: > > > > Bind to port 22 on 0.0.0.0 failed: Address already in use. > > > > > > I did learn that if I uncomment this line in sshd_config, it works: > > > > > > ListenAddress :: > > > > > > OR, if I add this line in sshd_config (instead), it works: > > > > > > AddressFamily inet > > > > > > OpenSSH problem? > > Are you running the same version of ssh in your DL 1.3 (4.7p1)? > > > > > > - BS |
From: Bruce S. <bw...@ar...> - 2007-10-30 19:15:27
|
> > > OK, I have the latest 1.3 running on a real PC, connected to the > > > Internet with a static IP. It didn't have any problem finding my IDE > > > CDROM drive (/dev/hdc). > > /dev/hdc ? Are you sure ? I'm requesting because PATA devices which work through > > libata represent themselvs as SCSI (SATA) /dev/sdx... > > It says hdc when it boots, and so does 'df' (copy/paste): > > root@Devil:~ # df > Filesystem 1K-blocks Used Available Use% Mounted on > rootfs 266046 266046 0 100% / > none 257504 9132 248372 4% /shm > /dev/hdc 266046 266046 0 100% / > none 257504 9132 248372 4% /dev > root@Devil:~ # cat /DEVIL-LINUX > 1.3.4-2007-10-30 > root@Devil:~ # uname -a > Linux Devil 2.6.23.1 #1 SMP Tue Oct 30 08:32:52... I just stuck an IDE hard drive in the box, and it shows up as hda: root@Devil:~ # fdisk -l /dev/hda Disk /dev/hda: 4311 MB, 4311982080 bytes 255 heads, 63 sectors/track, 524 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 1 524 4208998+ 8e Linux LVM - BS |
From: Heiko Z. <he...@zu...> - 2007-10-30 20:05:50
|
On Tue, October 30, 2007 14:15, Bruce Smith wrote: >>>> OK, I have the latest 1.3 running on a real PC, connected to the >>>> Internet with a static IP. It didn't have any problem finding my >>>> IDE >>>> CDROM drive (/dev/hdc). >>>> >>> /dev/hdc ? Are you sure ? I'm requesting because PATA devices which >>> work through libata represent themselvs as SCSI (SATA) /dev/sdx... >> >> It says hdc when it boots, and so does 'df' (copy/paste): >> >> >> root@Devil:~ # df >> Filesystem 1K-blocks Used Available Use% Mounted on >> rootfs 266046 266046 0 100% / none >> 257504 9132 248372 4% /shm >> /dev/hdc 266046 266046 0 100% / >> none 257504 9132 248372 4% /dev root@Devil:~ >> # cat /DEVIL-LINUX >> 1.3.4-2007-10-30 >> root@Devil:~ # uname -a >> Linux Devil 2.6.23.1 #1 SMP Tue Oct 30 08:32:52... >> > > > I just stuck an IDE hard drive in the box, and it shows up as hda: > > > > root@Devil:~ # fdisk -l /dev/hda > > > Disk /dev/hda: 4311 MB, 4311982080 bytes > 255 heads, 63 sectors/track, 524 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > > > Device Boot Start End Blocks Id System > /dev/hda1 1 524 4208998+ 8e Linux LVM It probably depends on the chipset. I guess the one Serge is using is only supported by a newer driver which is only in libata. -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Serge L. <fi...@in...> - 2007-11-01 19:09:47
|
Bruce, Bruce Smith wrote: >>> I just stuck an IDE hard drive in the box, and it shows up as hda: >> It probably depends on the chipset. >> I guess the one Serge is using is only supported by a newer driver which >> is only in libata. > > My emulated IDE CDROM drive in VMware-workstation also shows up > as /dev/hda (FWIW). Yes, you are absolutely right. Your hardware doesn't require libata, so you see devices in "non scsi" notation. As for me, my box requires ata_piix module not only for sata but for pata devices as well. Till I don't see your messages I thought that _all_ pata devices are working through libata in 2.6.23.1, that's why I was so surprised when you post your configuration. Sorry for confusing. I found the reason of crashes - it's my own addition. I added it to be able to load my box without usb-drive. It may be useful but I haven't checked in the following code, because the executing of it crashes kernel every time. PS. construction [ -n "$CONFIG_SRC_LIST" ] doesn't work for some reason. ---------------------------------------------------------------------------------- diff -aur ./linuxrc.orig ./linuxrc --- ./linuxrc.orig 2007-10-25 15:37:57.000000000 +0400 +++ ./linuxrc 2007-11-01 12:49:21.000000000 +0300 @@ -231,6 +223,17 @@ CDROMS=$(grep -i "drive name" /proc/sys/dev/cdrom/info) +if echo $CONFIG_SRC_LIST | grep "/dev" > /dev/null ; then + echo "Devices: $CONFIG_SRC_LIST" +else + echo "No devices were found" + echo -n "Would you like to probe for SCSI/ATA controllers now?" + if ask_yes_no ; then + /probe_all_scsi_modules + fi +fi + + # search for configuration information DL_CONFIG_SOURCE="" DL_CONFIG_FILE="" ----------------------------------------------------------------------------------- -- Sincerely Serge Leschinsky |
From: Serge L. <fi...@in...> - 2007-11-01 19:53:23
|
Bruce, > > Is it the /probe_all_scsi_modules script that crashes your system? > Yes. To be more exact, kernel crashes during mount attempt after loading all sata/pata/scsi modules. If I load only one module (ata_piix in my case) everything is ok. -- Sincerely, Serge Leschinsky |
From: Serge L. <fi...@in...> - 2007-10-30 10:33:11
|
Hi, Heiko Zuerker wrote: >> >> I just completed a compile, then I did a build and install of ncftp >> manually (./build.sh build opt=ncftp) and it appeared to compile fine. Ok. I'll add ncftp to my test config file ... >> One other problem I ran into was I had to turn set "AOE6=n" since it's >> build aborted. > > Yes that's correct. > The package is lacking support for the latest kernel. Yes. The support of 2.6.23rc3 only is declared. I'm going to write a message to the AoE list - may be the developers will help me with patch. FYI: I've got an ISO and tried to boot it. There is a problem with PATA devices (my test box is intel based with pata cdrom and hdd). The linuxrc has no possibility to determine device type and load appropriate modules, so I got error "Please check your Hardware!" after media searching. If I am able to find configs I can use INITRD_MODULES config option, but how to find configs.... As a workaround I did the following: - added kernel/drivers/ata/* to initrd - added optional request for probing SCSI/ATA controllers (if $CONFIG_SRC_LIST is empty ) I've got kernel crash at least 3 times :-( So, now I've rebuild kernel (with statically included drivers for intel) and moved forward in my testing. -- Sincerely Serge Leschinsky |
From: Heiko Z. <he...@zu...> - 2007-10-30 12:23:02
|
On Tue, October 30, 2007 05:32, Serge Leschinsky wrote: > Hi, > > > Heiko Zuerker wrote: > > >>> >>> I just completed a compile, then I did a build and install of ncftp >>> manually (./build.sh build opt=ncftp) and it appeared to compile fine. >>> > Ok. I'll add ncftp to my test config file > ... > >>> One other problem I ran into was I had to turn set "AOE6=n" since >>> it's build aborted. >> >> Yes that's correct. >> The package is lacking support for the latest kernel. >> > Yes. The support of 2.6.23rc3 only is declared. I'm going to write a > message to the AoE list - may be the developers will help me with patch. > > FYI: I've got an ISO and tried to boot it. There is a problem with PATA > devices (my test box is intel based with pata cdrom and hdd). The linuxrc > has no possibility to determine device type and load appropriate modules, > so I got error "Please check your Hardware!" after media searching. If I > am able to find configs I can use INITRD_MODULES config option, but how to > find configs.... As a workaround I did the following: - added > kernel/drivers/ata/* to initrd - added optional request for probing > SCSI/ATA controllers (if $CONFIG_SRC_LIST > is empty ) I've got kernel crash at least 3 times :-( > So, now I've rebuild kernel (with statically included drivers for intel) > and moved forward in my testing. The 1.3 is running stable in my system. Should we include all the new PATA and SATA drivers directly in the kernel? Then it would be like 1.2, where only the SCSI drivers are modules. -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Bruce S. <bw...@ar...> - 2007-10-30 13:02:19
|
> > FYI: I've got an ISO and tried to boot it. There is a problem with PATA > > devices (my test box is intel based with pata cdrom and hdd). The linuxrc > > has no possibility to determine device type and load appropriate modules, > > so I got error "Please check your Hardware!" after media searching. If I > > am able to find configs I can use INITRD_MODULES config option, but how to > > find configs.... As a workaround I did the following: - added > > kernel/drivers/ata/* to initrd - added optional request for probing > > SCSI/ATA controllers (if $CONFIG_SRC_LIST > > is empty ) I've got kernel crash at least 3 times :-( > > So, now I've rebuild kernel (with statically included drivers for intel) > > and moved forward in my testing. > > The 1.3 is running stable in my system. I compiled a new 1.3 last night (after Heiko's latest updates), and it booted fine in VMware-workstation this morning with a emulated IDE CD. There were a bunch of udevd & modprobe errors, but it didn't stop it from booting, and it appears to run fine. I might burn a CD and run it on real hardware later. > Should we include all the new PATA and SATA drivers directly in the > kernel? Then it would be like 1.2, where only the SCSI drivers are > modules. IMO, it'd be best to leave them as modules, if possible. - BS |
From: Serge L. <fi...@in...> - 2007-10-30 13:23:26
|
Heiko, Heiko Zuerker wrote: > On Tue, October 30, 2007 05:32, Serge Leschinsky wrote: > The 1.3 is running stable in my system. If I boot the system it works ok. Crashes usually arise during initrd phase. > Should we include all the new PATA and SATA drivers directly in the > kernel? Then it would be like 1.2, where only the SCSI drivers are > modules. It's a way... Basically, I think it will be better to invent possibility to load modules from linuxrc. -- Sincerely Serge Leschinsky |
From: Heiko Z. <he...@zu...> - 2007-10-30 13:41:13
|
On Tue, October 30, 2007 08:23, Serge Leschinsky wrote: > Heiko, > > > Heiko Zuerker wrote: > >> On Tue, October 30, 2007 05:32, Serge Leschinsky wrote: >> > >> The 1.3 is running stable in my system. >> > If I boot the system it works ok. Crashes usually arise during initrd > phase. Hmmm >> Should we include all the new PATA and SATA drivers directly in the >> kernel? Then it would be like 1.2, where only the SCSI drivers are >> modules. > It's a way... Basically, I think it will be better to invent possibility > to load modules from linuxrc. Actually the problem I think already solved itself. When we initialize mdev (the busybox udev version), it seems to auto load all the required modules. We could give it a try and move all the IDE drivers to a module, this may save us quite a bit kernel space. -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Serge L. <fi...@in...> - 2007-10-30 17:38:40
|
Heiko, Heiko Zuerker wrote: >>> Should we include all the new PATA and SATA drivers directly in the >>> kernel? Then it would be like 1.2, where only the SCSI drivers are >>> modules. >> It's a way... Basically, I think it will be better to invent possibility >> to load modules from linuxrc. > > Actually the problem I think already solved itself. > When we initialize mdev (the busybox udev version), it seems to auto load > all the required modules. We could give it a try and move all the IDE > drivers to a module, this may save us quite a bit kernel space. I can be wrong, but I think mdev creates devices after scanning /sys. I checked /sys when was investigating why my box didn't boot. There was no information about HDD or CD, so mdev didn't create devices. As I have rebuilt the kernel I can't reproduce the problem. Just now my box is busy by building the system with recent changes and I hope I'll send the main parts of logs/system settings tomorrow. -- Sincerely Serge Leschinsky |
From: Bruce S. <bw...@ar...> - 2007-10-30 18:09:41
|
OK, I have the latest 1.3 running on a real PC, connected to the Internet with a static IP. It didn't have any problem finding my IDE CDROM drive (/dev/hdc). I have it setup with the standard 2NIC firewall, running a DHCP server on the internal network. NAT works fine, as I can connect to the internet with my laptop, using the 1.3 DL box as my firewall. I am having a weird problem with networking. sshd wouldn't start. It kept complaining that the port 0.0.0.0:22 was already in use. I changed the port it listens on to a high number, and it still gave the same error (with the new port number). 'netstat -aepn' shows NO TCP connections listening at all, only UDP and RAW listening for dhcpd. I changed sshd_config to manually specify the IP addresses of both NIC's and now sshd starts fine. I tried starting apache2 (std config). It started and I can connect to it w/Firefox. However a 'netstat -aepn' doesn't show it listening on port 80, but instead shows a STREAM listening for httpd. I removed IPV6 routing from the config, with no difference. Something is really weird ... Ideas??? - BS |
From: Bruce S. <bw...@ar...> - 2007-10-30 20:14:41
|
> > I just stuck an IDE hard drive in the box, and it shows up as hda: > > It probably depends on the chipset. > I guess the one Serge is using is only supported by a newer driver which > is only in libata. My emulated IDE CDROM drive in VMware-workstation also shows up as /dev/hda (FWIW). - BS |
From: Bruce S. <bw...@ar...> - 2007-11-01 19:31:42
|
> >>> I just stuck an IDE hard drive in the box, and it shows up as hda: > >> It probably depends on the chipset. > >> I guess the one Serge is using is only supported by a newer driver which > >> is only in libata. > > > > My emulated IDE CDROM drive in VMware-workstation also shows up > > as /dev/hda (FWIW). > > Yes, you are absolutely right. Your hardware doesn't require libata, so you see > devices in "non scsi" notation. As for me, my box requires ata_piix module not > only for sata but for pata devices as well. Till I don't see your messages I > thought that _all_ pata devices are working through libata in 2.6.23.1, that's > why I was so surprised when you post your configuration. Sorry for confusing. OK, makes sense. > I found the reason of crashes - it's my own addition. I added it to be able to > load my box without usb-drive. It may be useful but I haven't checked in the > following code, because the executing of it crashes kernel every time. > > PS. construction [ -n "$CONFIG_SRC_LIST" ] doesn't work for some reason. > ---------------------------------------------------------------------------------- > diff -aur ./linuxrc.orig ./linuxrc > --- ./linuxrc.orig 2007-10-25 15:37:57.000000000 +0400 > +++ ./linuxrc 2007-11-01 12:49:21.000000000 +0300 > @@ -231,6 +223,17 @@ > > CDROMS=$(grep -i "drive name" /proc/sys/dev/cdrom/info) > > +if echo $CONFIG_SRC_LIST | grep "/dev" > /dev/null ; then > + echo "Devices: $CONFIG_SRC_LIST" > +else > + echo "No devices were found" > + echo -n "Would you like to probe for SCSI/ATA controllers now?" > + if ask_yes_no ; then > + /probe_all_scsi_modules > + fi > +fi Is it the /probe_all_scsi_modules script that crashes your system? - BS |
From: Bruce S. <bw...@ar...> - 2007-11-01 19:56:33
|
> > Is it the /probe_all_scsi_modules script that crashes your system? > > > Yes. To be more exact, kernel crashes during mount attempt after loading all > sata/pata/scsi modules. If I load only one module (ata_piix in my case) > everything is ok. It's probably not a good idea to just load all the modules and see which ones stick. It'd be better to examine the hardware and only load the correct modules -- although I'm not sure how to code that. - BS |
From: Serge L. <fi...@in...> - 2007-11-01 20:17:11
|
Bruce Smith wrote: >>> Is it the /probe_all_scsi_modules script that crashes your system? >>> >> Yes. To be more exact, kernel crashes during mount attempt after loading all >> sata/pata/scsi modules. If I load only one module (ata_piix in my case) >> everything is ok. > > It's probably not a good idea to just load all the modules and see which > ones stick. It'd be better to examine the hardware and only load the > correct modules -- although I'm not sure how to code that. Agree. Heiko said that it may be done by mdev using. I'd like to play with it and implement correct hardware detection. -- Sincerely, Serge Leschinsky |
From: Heiko Z. <he...@zu...> - 2007-11-01 21:00:16
|
On Thu, November 1, 2007 15:16, Serge Leschinsky wrote: > Bruce Smith wrote: > >>>> Is it the /probe_all_scsi_modules script that crashes your system? >>>> >>>> >>> Yes. To be more exact, kernel crashes during mount attempt after >>> loading all sata/pata/scsi modules. If I load only one module >>> (ata_piix in my case) >>> everything is ok. >> >> It's probably not a good idea to just load all the modules and see >> which ones stick. It'd be better to examine the hardware and only load >> the correct modules -- although I'm not sure how to code that. > > Agree. Heiko said that it may be done by mdev using. I'd like to play > with it and implement correct hardware detection. mdev is already in the current initrd for 1.3. It's the program which creates all the devices in /dev/ for us. So if it doesn't load the module already, you're screwed. ;-) The problem with the hardware detection is pretty big. I know there are a few projects out there, but if they're not actively maintained the won't help us much. -- Regards Heiko Zuerker http://www.devil-linux.org |