Hi All Today I restarted my SuSE 8.2 box and a red message came up : "'failed". I looked in the startup log and below you can see the result. Although there seems to be nothing wrong , I'm still curious to find out what and why this message came up. Anybody an idea? Thanks. Options: -a get/set fs readahead -A set drive read-lookahead flag (0/1) -b get/set bus state (0 == off, 1 == on, 2 == tristate) -B set Advanced Power Management setting (1-255) -c get/set IDE 32-bit IO setting -C check IDE power mode status -d get/set using_dma flag -D enable/disable drive defect-mgmt -E set cd-rom drive speed -f flush buffer cache for device on exit -g display drive geometry -h display terse usage information -i display drive identification -I detailed/current information directly from drive -Istdin similar to -I, but wants /proc/ide/*/hd?/identify as input -k get/set keep_settings_over_reset flag (0/1) -K set drive keep_features_over_reset flag (0/1) -L set drive doorlock (0/1) (removable harddisks only) -M get/set acoustic management (0-254, 128: quiet, 254: fast) (EXPERIMENTAL) -m get/set multiple sector count -n get/set ignore-write-errors flag (0/1) -p set PIO mode on IDE interface chipset (0,1,2,3,4,...) -P set drive prefetch count -q change next setting quietly -Q get/set DMA tagged-queuing depth (if supported) -r get/set readonly flag (DANGEROUS to set) -R register an IDE interface (DANGEROUS) -S set standby (spindown) timeout -t perform device read timings -T perform cache read timings -u get/set unmaskirq flag (0/1) -U un-register an IDE interface (DANGEROUS) -v defaults; same as -mcudkrag for IDE drives -V display program version and exit immediately -w perform device reset (DANGEROUS) -W set drive write-caching flag (0/1) (DANGEROUS) -x tristate device for hotswap (0/1) (DANGEROUS) -X set IDE xfer mode (DANGEROUS) -y put IDE drive in standby mode -Y put IDE drive to sleep -Z disable Seagate auto-powersaving mode -z re-read partition table failed -- Greetings from /bill at 169 west , 19 south. Disclaimer: Any errors in spelling, tact, or fact are transmission errors."
Bill Wisse wrote:
Today I restarted my SuSE 8.2 box and a red message came up : "'failed". I looked in the startup log and below you can see the result. Although there seems to be nothing wrong , I'm still curious to find out what and why this message came up. Anybody an idea?
This is from hdparm. It looks like, you're starting it automatically while booting, but with wrong arguments. Maybe /etc/init.d/boot.local ? -- Andreas
On Friday 29 August 2003 22:10, Andreas Winkelmann wrote:
Bill Wisse wrote:
Today I restarted my SuSE 8.2 box and a red message came up : "'failed". I looked in the startup log and below you can see the result. Although there seems to be nothing wrong , I'm still curious to find out what and why this message came up. Anybody an idea?
This is from hdparm. It looks like, you're starting it automatically while booting, but with wrong arguments. Maybe /etc/init.d/boot.local ?
-- Andreas
Ok thanks for that. Just recently I have changed DMA to "on", manually by putting on between the quotation marks. Can this have anything to do with it? I haven't changed anything in the boot process ( not that I know of anyway). I also have used "hdparm -v /dev/dvd" and then "hdparm -X <udma mode> -d 1 /dev/dvd. Could it be that the udma mode is set wrong? Thanks for your help, including Charles and del. -- Greetings from /bill at 169 west , 19 south. Disclaimer: Any errors in spelling, tact, or fact are transmission errors."
Bill Wisse wrote:
This is from hdparm. It looks like, you're starting it automatically while booting, but with wrong arguments. Maybe /etc/init.d/boot.local ?
Ok thanks for that. Just recently I have changed DMA to "on", manually by putting on between the quotation marks. Can this have anything to do with it?
Where? In /etc/sysconfig/hardware->DEVICES_FORCE_IDE_DMA ? Then not only "on", better: "/dev/hda:on". There is a description in the file.
I haven't changed anything in the boot process ( not that I know of anyway). I also have used "hdparm -v /dev/dvd" and then "hdparm -X <udma mode> -d 1 /dev/dvd. Could it be that the udma mode is set wrong?
To enable DMA use -d1 without space. -- Andreas
On Saturday 30 Aug 2003 12:46, Bill Wisse wrote:
On Friday 29 August 2003 22:10, Andreas Winkelmann wrote:
Bill Wisse wrote:
Today I restarted my SuSE 8.2 box and a red message came up : "'failed". I looked in the startup log and below you can see the result. Although there seems to be nothing wrong , I'm still curious to find out what and why this message came up. Anybody an idea?
This is from hdparm. It looks like, you're starting it automatically while booting, but with wrong arguments. Maybe /etc/init.d/boot.local ?
-- Andreas
Ok thanks for that. Just recently I have changed DMA to "on", manually by putting on between the quotation marks. Can this have anything to do with it? I haven't changed anything in the boot process ( not that I know of anyway). I also have used "hdparm -v /dev/dvd" and then "hdparm -X <udma mode> -d 1 /dev/dvd. Could it be that the udma mode is set wrong?
Try to set DMA for the DVD with yast2, watch for errors in the message log with tail -f, you won't need to reboot to check if it's worked. (Or use alt+F10.) Keep trying the different settings, the default setting works on this PC but on another machine DMA66 works. The other machine has a new Asus DVD which supports UDMA100 but the mobo only goes up to 66. Somewhere in Yast there is a boot.idedma setting, in runlevel properties, should be set as B. Also check that the BIOS has enabled DMA for the DVD. Not meaning any disrespect to the advice from Andreas, which has just arrived while writing this, but I would see what Yast can do for you first of all before trying to manualy edit startup files. -- del suse-linux-e
On Saturday 30 August 2003 01:06, del wrote:
On Saturday 30 Aug 2003 12:46, Bill Wisse wrote:
On Friday 29 August 2003 22:10, Andreas Winkelmann wrote:
Snip>>
Try to set DMA for the DVD with yast2, watch for errors in the message log with tail -f, you won't need to reboot to check if it's worked. (Or use alt+F10.) Keep trying the different settings, the default setting works on this PC but on another machine DMA66 works. The other machine has a new Asus DVD which supports UDMA100 but the mobo only goes up to 66. Somewhere in Yast there is a boot.idedma setting, in runlevel properties, should be set as B. Also check that the BIOS has enabled DMA for the DVD.
I changed the setting in Yast to B. Enabled it and "start now". When I restarted to check , the "failed" message has disappeared, but when I looked again in Yast runlevel, boot.idedma it has option B and also runlevel 5 but it says "not running". Start up log says : Setting up IDE DMA mode /dev/hda: setting using_dma to 1 (on) using_dma = 1 (on) done Is there anything else I should do? Thank you very much for trying to help me. -- Greetings from /bill at 169 west , 19 south. Disclaimer: Any errors in spelling, tact, or fact are transmission errors."
Bill Wisse wrote:
I changed the setting in Yast to B. Enabled it and "start now". When I restarted to check , the "failed" message has disappeared, but when I looked again in Yast runlevel, boot.idedma it has option B and also runlevel 5 but it says "not running".
This is ok, because boot.idedma is no service or daemon. It is only a script which is started once on booting.
Start up log says :
Setting up IDE DMA mode
/dev/hda:
setting using_dma to 1 (on)
using_dma = 1 (on)
done
Is there anything else I should do?
Maybe you want to check if dma is enabled with "hdparm /dev/hda", if it is activated (1) everything is oki. -- Andreas
On Saturday 30 August 2003 10:31, Andreas Winkelmann wrote:
Bill Wisse wrote:
I changed the setting in Yast to B. Enabled it and "start now". When I restarted to check , the "failed" message has disappeared, but when I looked again in Yast runlevel, boot.idedma it has option B and also runlevel 5 but it says "not running".
This is ok, because boot.idedma is no service or daemon. It is only a script which is started once on booting.
Start up log says :
Setting up IDE DMA mode
/dev/hda:
setting using_dma to 1 (on)
using_dma = 1 (on)
done
Is there anything else I should do?
Maybe you want to check if dma is enabled with "hdparm /dev/hda", if it is activated (1) everything is oki.
Checked , but it says DMA = 0 (off). -- Greetings from /bill at 169 west , 19 south. Disclaimer: Any errors in spelling, tact, or fact are transmission errors."
Bill Wisse wrote:
Start up log says :
Setting up IDE DMA mode
/dev/hda:
setting using_dma to 1 (on)
using_dma = 1 (on)
done
Is there anything else I should do?
Maybe you want to check if dma is enabled with "hdparm /dev/hda", if it is activated (1) everything is oki.
Checked , but it says DMA = 0 (off).
Which Mainboard do you have? And which kernel-version? -- Andreas
On Saturday 30 August 2003 10:53, Andreas Winkelmann wrote:
Bill Wisse wrote:
Start up log says :
Setting up IDE DMA mode
/dev/hda:
setting using_dma to 1 (on)
using_dma = 1 (on)
done
Is there anything else I should do?
Maybe you want to check if dma is enabled with "hdparm /dev/hda", if it is activated (1) everything is oki.
Checked , but it says DMA = 0 (off).
Which Mainboard do you have? And which kernel-version?
Intel 82801BA-ICH2 Kernel 2-4-20 -- Greetings from /bill at 169 west , 19 south. Disclaimer: Any errors in spelling, tact, or fact are transmission errors."
Bill Wisse wrote:
Start up log says :
Setting up IDE DMA mode
/dev/hda:
setting using_dma to 1 (on)
using_dma = 1 (on)
done
Is there anything else I should do?
Maybe you want to check if dma is enabled with "hdparm /dev/hda", if it is activated (1) everything is oki.
Checked , but it says DMA = 0 (off).
Which Mainboard do you have? And which kernel-version?
Intel 82801BA-ICH2 Kernel 2-4-20
Hmm, i have found nothing interesting of this combination. Do a "hdparm -d1 /dev/hda" then a "hdparm /dev/hda" in the running system. Works it then? Please send the Output of "dmesg" after booting up. -- Andreas
On Saturday 30 August 2003 12:11, Andreas Winkelmann wrote:
Bill Wisse wrote:
Intel 82801BA-ICH2 Kernel 2-4-20
Hmm, i have found nothing interesting of this combination.
Do a "hdparm -d1 /dev/hda" then a "hdparm /dev/hda" in the running system. Works it then?
Yes, it works but it doesn't save it. On the next start up it is not running.
Please send the Output of "dmesg" after booting up.
Linux version 2.4.20-4GB (root@Pentium.suse.de) (gcc version 3.3 20030226
(prerelease) (SuSE Linux)) #1 Wed Aug 6 18:26:21 UTC 2003
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001fec0000 (usable)
BIOS-e820: 000000001fec0000 - 000000001fef8000 (ACPI data)
BIOS-e820: 000000001fef8000 - 000000001ff00000 (ACPI NVS)
BIOS-e820: 00000000ffb80000 - 00000000ffc00000 (reserved)
BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
Scanning bios EBDA for MXT signature
0MB HIGHMEM available.
510MB LOWMEM available.
ACPI: have wakeup address 0xc0001000
On node 0 totalpages: 130752
zone(0): 4096 pages.
zone(1): 126656 pages.
zone(2): 0 pages.
ACPI: RSDP (v000 AMI ) @ 0x000ff980
ACPI: RSDT (v001 D815EA D815EEA2 08193.01028) @ 0x1fef0000
ACPI: FADT (v001 D815EA EA81510A 08193.01028) @ 0x1fef1000
ACPI: DSDT (v001 D815E2 EA81520A 00000.00033) @ 0x00000000
ACPI: BIOS passes blacklist
Building zonelist for node : 0
Kernel command line: auto BOOT_IMAGE=linux ro root=303 hdd=ide-scsi
hdd=ide-scsi hdd=ide-scsi hddlun=0 splash=silent
ide_setup: hdd=ide-scsi
ide_setup: hdd=ide-scsi
ide_setup: hdd=ide-scsi
ide_setup: hddlun=0
bootsplash: silent mode.
Initializing CPU#0
Detected 996.788 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 1985.74 BogoMIPS
Memory: 513164k/523008k available (1571k kernel code, 9456k reserved, 574k
data, 160k init, 0k highmem)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes)
Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: After generic, caps: 0383f9ff 00000000 00000000 00000000
CPU: Common caps: 0383f9ff 00000000 00000000 00000000
CPU: Intel Pentium III (Coppermine) stepping 06
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
ACPI: Subsystem revision 20030228
PCI: PCI BIOS revision 2.10 entry at 0xfda95, last bus=1
PCI: Using configuration type 1
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: System [ACPI] (supports S0 S1 S4 S5)
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
Transparent bridge - Intel Corp. 82801BA/CA/DB PCI Bridge
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
ACPI: Power Resource [URP1] (off)
ACPI: Power Resource [URP2] (off)
ACPI: Power Resource [FDDP] (off)
ACPI: Power Resource [LPTP] (off)
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *9 10 11 12)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 12, disabled)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12, disabled)
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11 12, disabled)
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 *10 11 12)
PCI: Probing PCI hardware
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 10
ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 9
PCI: Using ACPI for IRQ routing
PCI: if you experience problems, try using option 'pci=noacpi' or even
'acpi=off'
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
apm: overridden by ACPI.
mxt_scan_bios: enter
Starting kswapd
bigpage subsystem: allocated 0 bigpages (=0MB).
kinoded started
VFS: Disk quotas vdquot_6.5.1
aio_setup: num_physpages = 32688
aio_setup: sizeof(struct page) = 48
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT
SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10e
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
loop: loaded (max 16 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00beta-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH2: IDE controller at PCI slot 00:1f.1
ICH2: chipset revision 2
ICH2: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DMA
hda: ST340824A, ATA DISK drive
blk: queue c03ac500, I/O limit 4095Mb (mask 0xffffffff)
hdc: ASUS DVD-ROM E616, ATAPI CD/DVD-ROM drive
hdd: Hewlett-Packard CD-Writer Plus 9300, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: 78165360 sectors (40021 MB) w/2048KiB Cache, CHS=4865/255/63, UDMA(100)
ide-floppy driver 0.99.newide
Partition check:
hda: hda1 hda2 hda3
ide-floppy driver 0.99.newide
SCSI subsystem driver Revision: 1.00
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 424k freed
VFS: Mounted root (ext2 filesystem).
reiserfs: found format "3.6" with standard journal
reiserfs: enabling write barrier flush mode
reiserfs: using ordered data mode
reiserfs: checking transaction log (ide0(3,3)) for (ide0(3,3))
Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Trying to move old root to /initrd ... failed
Unmounting old root
Trying to free ramdisk memory ... okay
Freeing unused kernel memory: 160k freed
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
LVM version 1.0.5+(mp-v6a)(22/07/2002) module loaded
Adding Swap: 658656k swap-space (priority 42)
hdc: attached ide-cdrom driver.
hdc: ATAPI 48X DVD-ROM drive, 512kB Cache
Uniform CD-ROM driver Revision: 3.12
hdd: attached ide-scsi driver.
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: HP Model: CD-Writer+ 9300 Rev: 1.0c
Type: CD-ROM ANSI SCSI revision: 02
hermes.c: 4 Dec 2002 David Gibson
Bill Wisse wrote:
Kernel command line: auto BOOT_IMAGE=linux ro root=303 hdd=ide-scsi hdd=ide-scsi hdd=ide-scsi hddlun=0 splash=silent ide_setup: hdd=ide-scsi ide_setup: hdd=ide-scsi ide_setup: hdd=ide-scsi ide_setup: hddlun=0 bootsplash: silent mode.
Uniform Multi-Platform E-IDE driver Revision: 7.00beta-2.4 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx ICH2: IDE controller at PCI slot 00:1f.1 ICH2: chipset revision 2 ICH2: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DMA hda: ST340824A, ATA DISK drive blk: queue c03ac500, I/O limit 4095Mb (mask 0xffffffff) hdc: ASUS DVD-ROM E616, ATAPI CD/DVD-ROM drive hdd: Hewlett-Packard CD-Writer Plus 9300, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: attached ide-disk driver. hda: 78165360 sectors (40021 MB) w/2048KiB Cache, CHS=4865/255/63, UDMA(100)
Don't no if you can figure out what it is ,otherwise I just leave it. I don't do reboots that often so when it is set.......it stays on. Still, it's annoying that it won't work at start up.
Ok, then last try: Delete two of "hdd=ide-scsi" from your kernel-commandline-options. And add "ide0=dma hdb=none". Am i correct, you have no hdb? If you use lilo, don't forget "lilo" after changing. -- Andreas
On Sunday 31 Aug 2003 04:43, Bill Wisse wrote:
hda: ST340824A, ATA DISK drive blk: queue c03ac500, I/O limit 4095Mb (mask 0xffffffff) hdc: ASUS DVD-ROM E616, ATAPI CD/DVD-ROM drive hdd: Hewlett-Packard CD-Writer Plus 9300, ATAPI CD/DVD-ROM drive
This is a very similar setup to one of mine, although I've also got hdb which matches hda. They are also Maxtor drives and the DVD is the same as this one, but I've got a Memorex CD-RW on hdd. Yast will set this up so that DMA for hda is on. However, I don't think that having DMA on/off isn't going to make much difference unless you also have the 40 pin, 80 wire IDE cable on hda ( assuming you want UDMA 66/100/133 ). Are you sure that the BIOS has DMA enabled for hda and hdc? -- del suse-linux-e
On Sunday 31 Aug 2003 09:39, del wrote:
Are you sure that the BIOS has DMA enabled for hda and hdc?
This is a PS. Bill, check the output of hdparm /dev/hda hdparm /dev/hda /dev/hda: using_dma = 1 (on) That's a snippet from another Maxtor drive I have. -- del suse-linux-e
On Saturday 30 August 2003 21:39, del wrote:
On Sunday 31 Aug 2003 04:43, Bill Wisse wrote:
hda: ST340824A, ATA DISK drive blk: queue c03ac500, I/O limit 4095Mb (mask 0xffffffff) hdc: ASUS DVD-ROM E616, ATAPI CD/DVD-ROM drive hdd: Hewlett-Packard CD-Writer Plus 9300, ATAPI CD/DVD-ROM drive
This is a very similar setup to one of mine, although I've also got hdb which matches hda. They are also Maxtor drives and the DVD is the same as this one, but I've got a Memorex CD-RW on hdd. Yast will set this up so that DMA for hda is on. However, I don't think that having DMA on/off isn't going to make much difference unless you also have the 40 pin, 80 wire IDE cable on hda ( assuming you want UDMA 66/100/133 ).
Are you sure that the BIOS has DMA enabled for hda and hdc?-
No , actually I'm not. I went to the BIOS but couldn't find it. -- Greetings from /bill at 169 west , 19 south. Disclaimer: Any errors in spelling, tact, or fact are transmission errors."
On Sunday 31 Aug 2003 20:09, Bill Wisse wrote:
Are you sure that the BIOS has DMA enabled for hda and hdc?-
No , actually I'm not. I went to the BIOS but couldn't find it.
What mobo or BIOS do you have there? A lot of times you'll find it on the first screen or the first option on that screen. If the mobo is, I would guess, 3 years old or newer and auto detect is used then DMA is enabled, UDMA if the cable is 40pin x 80wire. -- del suse-linux-e
On Sunday 31 August 2003 08:36, del wrote:
On Sunday 31 Aug 2003 20:09, Bill Wisse wrote:
Are you sure that the BIOS has DMA enabled for hda and hdc?-
No , actually I'm not. I went to the BIOS but couldn't find it.
What mobo or BIOS do you have there? A lot of times you'll find it on the first screen or the first option on that screen. If the mobo is, I would guess, 3 years old or newer and auto detect is used then DMA is enabled, UDMA if the cable is 40pin x 80wire.
OK. Here are my results so far. When I reboot now and do a hdparm /dev/hda I get result: DMA = 1 (on). However what I really want is to have /dev/dvd DMA =1 (on). I still have to enable this manually every time I reboot. Thanks again for all the help. -- Greetings from /bill at 169 west , 19 south. Disclaimer: Any errors in spelling, tact, or fact are transmission errors."
* Bill Wisse (wiswp@niue.nu) [030901 13:34]:
On Sunday 31 August 2003 08:36, del wrote:
On Sunday 31 Aug 2003 20:09, Bill Wisse wrote:
Are you sure that the BIOS has DMA enabled for hda and hdc?-
No , actually I'm not. I went to the BIOS but couldn't find it.
What mobo or BIOS do you have there? A lot of times you'll find it on the first screen or the first option on that screen. If the mobo is, I would guess, 3 years old or newer and auto detect is used then DMA is enabled, UDMA if the cable is 40pin x 80wire.
OK. Here are my results so far. When I reboot now and do a hdparm /dev/hda I get result: DMA = 1 (on). However what I really want is to have /dev/dvd DMA =1 (on). I still have to enable this manually every time I reboot. Thanks again for all the help.
You can put this in /etc/init.d/boot.local or I'm pretty sure you can set this in YaST2 and have the system force this state to your DVD player. -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org ----- If two men agree on everything, you can be sure that only one of them is doing the thinking.
Bill Wisse wrote:
Are you sure that the BIOS has DMA enabled for hda and hdc?-
No , actually I'm not. I went to the BIOS but couldn't find it.
What mobo or BIOS do you have there? A lot of times you'll find it on the first screen or the first option on that screen. If the mobo is, I would guess, 3 years old or newer and auto detect is used then DMA is enabled, UDMA if the cable is 40pin x 80wire.
OK. Here are my results so far. When I reboot now and do a hdparm /dev/hda I get result: DMA = 1 (on). However what I really want is to have /dev/dvd DMA =1 (on). I still have to enable this manually every time I reboot. Thanks again for all the help.
And what did you have done, that /dev/hda is now "dma=1" after reboot? It wasn't so before, right? -- Andreas
On Sat, 30 Aug 2003 16:43:42 -1100
Bill Wisse
Yes, it works but it doesn't save it. On the next start up it is not running.
I much prefer just sticking the hdparm commands in boot.local. This way you can fine tune it more. For example this is what I use on my old machine here: /sbin/hdparm -d1 -m16 -X udma2 -u1 -W1 -A1 -c3 -k1 /dev/hda /sbin/hdparm -d1 -m16 -X udma2 -u1 -W1 -A1 -c3 -k1 /dev/hdb /sbin/hdparm -d1 -c3 -W1 -X udma2 -u1 -k1 /dev/hdc Please refer to the hdparm manpage. Charles -- "Oh, I've seen copies [of Linux Journal] around the terminal room at The Labs." (By Dennis Ritchie)
On Fri, 29 Aug 2003 22:19:45 -1100
Bill Wisse
I'm still curious to find out what and why this message came up. Anybody an idea?
Somewhere in your configs there is a wrong hdparm command. Charles -- We come to bury DOS, not to praise it. (Paul Vojta, vojta@math.berkeley.edu, paraphrasing a quote of Shakespeare)
participants (5)
-
Andreas Winkelmann -
Ben Rosenberg -
Bill Wisse -
Charles Philip Chan -
del