Matthew Johnson <matthew@psychohorse.com> writes:
This might have been mentioned before, but I was wondering what happened to dma transfer in SuSE? Used to be able to start and stop this via rcdma or soemhting similer, has this been integrated now?
The following is from the SuSE Linux System and Reference Manual: 12.2.4 From 7.2 to 7.3 ... Kernel 2.4 which is included in SuSE Linux has IDE-DMA turned on by default. The YaST2 module System tuning (package yast2-config-tune) as well as the back end idedma have, therefore, become obsolete. If you have any problems related to DMA, you can always fall back on the Installation -- Safe Settings boot option. -- Alexandr.Malusek@imv.liu.se
Does this mean that I must reinstall from scratch? I cannot find anywhere in yast or yast2 which allows me to select Safe Setting boot mode. Thanks for the note, I would like to try this to see if it resolves the strange messages. Jim 12/29/01 12:16:25 PM, Alexandr Malusek <Alexandr.Malusek@imv.liu.se> wrote:
Matthew Johnson <matthew@psychohorse.com> writes:
This might have been mentioned before, but I was wondering what happened to dma transfer in SuSE? Used to be able to start and stop this via rcdma or soemhting similer, has this been integrated now?
The following is from the SuSE Linux System and Reference Manual:
12.2.4 From 7.2 to 7.3 ... Kernel 2.4 which is included in SuSE Linux has IDE-DMA turned on by default. The YaST2 module System tuning (package yast2-config-tune) as well as the back end idedma have, therefore, become obsolete. If you have any problems related to DMA, you can always fall back on the Installation -- Safe Settings boot option.
-- Alexandr.Malusek@imv.liu.se
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
On Saturday 29 December 2001 09:43 pm, James Bliss wrote:
Does this mean that I must reinstall from scratch? I cannot find anywhere in yast or yast2 which allows me to select Safe Setting boot mode.
The safe setting boot mode is one of the menu selections while booting, not a yast2 selection. If you're not getting "safe setting" or (pre-7.3 distribution) "suse" as a selection when you boot, check your lilo.conf file to see if it's there, or adjust it in YAST2 / system / bootloader configuration if you prefer menus.
I was not sure, I did testto see if suse may have been the menu option to select to get into this. When I selected it I still got the dma_intr errors. Ah well, as I said before, they only appear on boot before the first run level is reached. Everything works fine but for these error messages so I will just follow the various threads and see if this can be nailed down over time. Thanks for your help. Jim 12/29/01 10:52:29 PM, Joshua Lee <edlin@mochamail.com> wrote:
On Saturday 29 December 2001 09:43 pm, James Bliss wrote:
Does this mean that I must reinstall from scratch? I cannot find anywhere in yast or yast2 which allows me to select Safe Setting boot mode.
The safe setting boot mode is one of the menu selections while booting, not a yast2 selection.
If you're not getting "safe setting" or (pre-7.3 distribution) "suse" as a selection when you boot, check your lilo.conf file to see if it's there, or adjust it in YAST2 / system / bootloader configuration if you prefer menus.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
On Sunday 30 December 2001 09:54 am, James Bliss wrote:
I was not sure, I did testto see if suse may have been the menu option to select to get into this. When I selected it I still got the dma_intr errors. Ah well, as I said before, they only appear on boot before the
Hmm.. Have you upgraded your kernel or operating system lately? I remember SuSE 7.2 and earlier didn't have DMA enabled by default, later kernels such as the ones shipped with SuSE 7.3 has it enabled and it must be disabled explicitly (ide=nodma) within /etc/lilo.conf.
Thank you for your help Joshua. I put that line in the append line in lilo.conf, ran lilo, rebooted and no errors. In the past, whenever I booted I got at least a half dozen of them, if not more. My configuration is: clean 7,2 personal install upgraded to 7.3 professional using CDs. Kernel has been upgraded to 2.4.16-4GB via the SuSE rpm. The upgrade is probably the reason 'Safe Mode' does not appear on the boot screen and SuSE does. I know that I can change this in lilo.conf if I desire. Again, thanks for your help Joshua, perhaps this will resolve the problem several other participants on this list were having with the same basic error messages. Jim 12/30/01 09:17:17 AM, Joshua Lee <edlin@mochamail.com> wrote:
On Sunday 30 December 2001 09:54 am, James Bliss wrote:
I was not sure, I did testto see if suse may have been the menu option to select to get into this. When I selected it I still got the dma_intr errors. Ah well, as I said before, they only appear on boot before the
Hmm.. Have you upgraded your kernel or operating system lately? I remember SuSE 7.2 and earlier didn't have DMA enabled by default, later kernels such as the ones shipped with SuSE 7.3 has it enabled and it must be disabled explicitly (ide=nodma) within /etc/lilo.conf.
participants (3)
-
Alexandr Malusek -
James Bliss -
Joshua Lee