DebianThis forum is for the discussion of Debian Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
there is a long delay on my computer (Debian, amd64, testing) after "Loading, please wait" message. On the other, older computer, delay is much shorter. could it be because of software raid or scsi card? is there way to speed it up?
It could be due to the size of the /boot or / partition.
Without knowing all of the details of the software raid setup or the scsi card and configuration of the drives, number of drives, partitioning scheme, bootloader, etc... it's not going to be easy for anyone to help you.
boot and / are on same partition, its size is 25Gb on SSD drive. raid0 is on 3 hdds. bootloader is grub2.
looking at dmesg, biggest delay seems to be here:
[ 4.004172] usbhid: USB HID core driver
[ 16.148458] scsi2 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
edit: I think I've found the solution, nut sure how to use it:
> This sounds like a user configuration error. The adaptec has a bus
> settle time in its initialisation path. Originally it was 20s, hence
> for a D card (twin channel) it would take about 50s to come online
> (extra 5s to scan per channel). There was a lot of argument about this,
> and the value was finally made configurable as
> I suspect you have this set to around 15000. You can make the boot
> sequence shorter by reducing this value. I believe Red Hat configures
> it down to the default 5000.
It's in the kernel configuration, so to change that you would need to rebuild the kernel.
Apparently this was fixed upstream quite some time ago - but it is a only a configuration option, so it could have been configured to the old value in Debian's kernels. You should first check if this is a possible cause:
I doubt it's beyond your linux knowledge, but you're right in that rebuilding the kernel whenever there's an update can be a pain - but for many users a necessary one. I tend to just choose a kernel from kernel.org and stick with it, patching and rebuilding only when something relevant (and/or security related) turns up.