Re: Problems on Blade 1000 after etch instalation
I have noticed that the problem of the xserver had to do with a bad configuration of afbinit. El jue, 31-08-2006 a las 12:46 +0200, Luis Martinez escribió: How can I make that the root file system is mounted on the blade1000? The qlogicfc module is not loaded on the boot process even though it is in the initrd.img file. I have modified the initrd.img and added to the modules file the line qlogicfc, now the disks are detected and the system boots. Which is the difference that makes the Ultra60 not to load when specifying the initrd file when this file works on normal booting? I have to add the root=/dev/sdxy to the boot string when specifying the booting string. (I think that this is normal). Now the system is booting but I have some more problems. 1.- The system stops while trying to run the cupsys daemon. I had to take this out from the booting process. 2.- xwindows do not work. The blade is running with a creator 3D M3 adapter, afb code is loaded OK. The x screen starts for 1 or 2 seconds and then dies with signal 11 saying that connection is reset by peer. If I move the mouse while starting the xserver then the x screen lasts less time. The keyboard (sub type 6 spanish) is set like this. Driver kbd Option XkbRules xorg Option XkbModel pc105 Option XkbLayout es The modules for the sunffb (cfb and cfb32) are also included in the xorg.conf Any clue? 3.- The fans of the blade 1000 are runing 100% speed. Is there a kernel module to control the fans out there to solve this? Thanks and best regards, Luis El mié, 30-08-2006 a las 17:51 +0200, Luis Martinez escribió: After more testing it seems that the machine does not wait for ever, at the end it fails to found and mount the root partition. I have also a Ultra 60 with the same instalation that boots. I have copied the initrd in the boot directory with another file name like oldinit when I try to boot with boot:1/vmlinuz initrd=1/oldinit I have the same problem than with the blade 1000 (initrd.img found and scsi module loaded but wait for root file system message and finally dropped to a shell). How can I make that the root file system is mounted on the blade1000? Which is the difference that makes the Ultra60 not to load when specifying the initrd file when this file works on normal booting? I would thank any light on this problem. Luis El mié, 30-08-2006 a las 11:33 +0200, Luis Martinez escribió: Hello, I have been trying to install Debian Etch on a Blade 1000 using a netboot image. The machine has 2 FCAL disks for storage. After the instalation the machine loads silo and when the system is booting it finally stays for ever with a message that says waiting for root filesystem. I have checked the initrd and it has in the module tree the qlogicfc. The qloficfc controller seems to be detected on boot but at the end I have a lot of messages regarding qla2xxx that I dont know if they should be there. Thanks in advance, Luis
Re: Problems on Blade 1000 after etch instalation
How can I make that the root file system is mounted on the blade1000? The qlogicfc module is not loaded on the boot process even though it is in the initrd.img file. I have modified the initrd.img and added to the modules file the line qlogicfc, now the disks are detected and the system boots. Which is the difference that makes the Ultra60 not to load when specifying the initrd file when this file works on normal booting? I have to add the root=/dev/sdxy to the boot string when specifying the booting string. (I think that this is normal). Now the system is booting but I have some more problems. 1.- The system stops while trying to run the cupsys daemon. I had to take this out from the booting process. 2.- xwindows do not work. The blade is running with a creator 3D M3 adapter, afb code is loaded OK. The x screen starts for 1 or 2 seconds and then dies with signal 11 saying that connection is reset by peer. If I move the mouse while starting the xserver then the x screen lasts less time. The keyboard (sub type 6 spanish) is set like this. Driver kbd Option XkbRules xorg Option XkbModel pc105 Option XkbLayout es The modules for the sunffb (cfb and cfb32) are also included in the xorg.conf Any clue? 3.- The fans of the blade 1000 are runing 100% speed. Is there a kernel module to control the fans out there to solve this? Thanks and best regards, Luis El mié, 30-08-2006 a las 17:51 +0200, Luis Martinez escribió: After more testing it seems that the machine does not wait for ever, at the end it fails to found and mount the root partition. I have also a Ultra 60 with the same instalation that boots. I have copied the initrd in the boot directory with another file name like oldinit when I try to boot with boot:1/vmlinuz initrd=1/oldinit I have the same problem than with the blade 1000 (initrd.img found and scsi module loaded but wait for root file system message and finally dropped to a shell). How can I make that the root file system is mounted on the blade1000? Which is the difference that makes the Ultra60 not to load when specifying the initrd file when this file works on normal booting? I would thank any light on this problem. Luis El mié, 30-08-2006 a las 11:33 +0200, Luis Martinez escribió: Hello, I have been trying to install Debian Etch on a Blade 1000 using a netboot image. The machine has 2 FCAL disks for storage. After the instalation the machine loads silo and when the system is booting it finally stays for ever with a message that says waiting for root filesystem. I have checked the initrd and it has in the module tree the qlogicfc. The qloficfc controller seems to be detected on boot but at the end I have a lot of messages regarding qla2xxx that I dont know if they should be there. Thanks in advance, Luis
Re: Problems on Blade 1000 after etch instalation
Luis Martinez wrote: [snip] 2.- xwindows do not work. The blade is running with a creator 3D M3 adapter, afb code is loaded OK. The x screen starts for 1 or 2 seconds and then dies with signal 11 saying that connection is reset by peer. If I move the mouse while starting the xserver then the x screen lasts less time. The keyboard (sub type 6 spanish) is set like this. Driver kbd Option XkbRules xorg Option XkbModel pc105 Option XkbLayout es The modules for the sunffb (cfb and cfb32) are also included in the xorg.conf Any clue? It is possible that you do not need the afb microcode to be loaded. AFAIK this is only for Elite 3D cards, not Creator 3D cards. However, the afbinit package's init script _should_ check this for you. If you have a Creator 3D card it _should_ (silently) do nothing. If you forcibly use the program that loads the microcode with a Creator 3D card, then the card will become unusable until you do a _cold_ boot. I guess you could try de-installing the afbinit package, moving the microcode away from /usr/lib and doing a cold (power turned right off) reboot. If it doesn't work after that, you'll at least have eliminated a possibility and can check /var/log/Xorg.0.log for other clues. [Of course, this removes the possibility of 3-D acceleration. But as I was informed a day or two ago on this list, it doesn't work anyway for Creator 3D cards.] HTH! Hugh -- S=u=p=p=o=r=t===D=e=b=i=a=n===http://www.debian.org = Dr. Hugh C. Pumphrey | Tel. 0131-650-6026,Fax:0131-662-0478 School of GeoSciences | Replace 0131 with +44-131 if outside UK The University of Edinburgh | Email: [EMAIL PROTECTED] EDINBURGH EH9 3JN, Scotland | web: www.geos.ed.ac.uk/contacts/homes/hcp =I==o=f=t=e=n==i=g=n=o=r=e==M=S==W=o=r=d==a=t=t=a=c=h=m=e=n=t=s== -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems on Blade 1000 after etch instalation
On Thu, 31 Aug 2006, Luis Martinez wrote: The qlogicfc module is not loaded on the boot process even though it is in the initrd.img file. I have modified the initrd.img and added to the modules file the line qlogicfc, now the disks are detected and the system boots. Nice to hear that this problems is solved. I don't really know what went wrong there, but there is one important test you could do. In 2.6.17 the qlogicfc module has been removed, and its functionality is supposed to be provided by qla2xxx. Current daily images found at http://www.debian.org/devel/debian-installer have 2.6.17 and no qlogicfc. It would be great if you could try an install using one of the daily builds, and report your experiences. Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problems on Blade 1000 after etch instalation
Hello, I have been trying to install Debian Etch on a Blade 1000 using a netboot image. The machine has 2 FCAL disks for storage. After the instalation the machine loads silo and when the system is booting it finally stays for ever with a message that says waiting for root filesystem. I have checked the initrd and it has in the module tree the qlogicfc. The qloficfc controller seems to be detected on boot but at the end I have a lot of messages regarding qla2xxx that I dont know if they should be there. Thanks in advance, Luis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems on Blade 1000 after etch instalation
After more testing it seems that the machine does not wait for ever, at the end it fails to found and mount the root partition. I have also a Ultra 60 with the same instalation that boots. I have copied the initrd in the boot directory with another file name like oldinit when I try to boot with boot:1/vmlinuz initrd=1/oldinit I have the same problem than with the blade 1000 (initrd.img found and scsi module loaded but wait for root file system message and finally dropped to a shell). How can I make that the root file system is mounted on the blade1000? Which is the difference that makes the Ultra60 not to load when specifying the initrd file when this file works on normal booting? I would thank any light on this problem. Luis El mié, 30-08-2006 a las 11:33 +0200, Luis Martinez escribió: Hello, I have been trying to install Debian Etch on a Blade 1000 using a netboot image. The machine has 2 FCAL disks for storage. After the instalation the machine loads silo and when the system is booting it finally stays for ever with a message that says waiting for root filesystem. I have checked the initrd and it has in the module tree the qlogicfc. The qloficfc controller seems to be detected on boot but at the end I have a lot of messages regarding qla2xxx that I dont know if they should be there. Thanks in advance, Luis
Re: Problems on Blade 1000 after etch instalation
On Wed, 30 Aug 2006, Luis Martinez wrote: After more testing it seems that the machine does not wait for ever, at the end it fails to found and mount the root partition. If it did work during install, but fails to boot from the hard drive, there is likely a problem with initrd. During boot the modules, required for the root partition to operate, are loaded. Since the loading is asynchronous, the process than waits for the devices to show up. If the needed driver was not loaded, or the wrong driver was used, it should just drop you to a shell after a while. From there you can try to check what modules are loaded (cat /proc/modules if lsmod is not available) and manually load the needed module(s) (try insmod qlogicfc, if you are sure that this is the right one). You can also compare the lists of modules during the install (make sure the disks are detected, then press 'Back' a few times to get to the main menu, select 'Start a shell' and run lsmod to get it) with the one you have in the emergency initrd shell. You might also check that all the needed modules are actually available on the initrd. This information should help us to figure out what went wrong. Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
