| View previous topic :: View next topic |
| Author |
Message |
DesertFox
n00b
Joined: 14 Nov 2002
Posts: 53
|
 Posted: Fri Dec 13, 2002 9:24 pm Post subject: /dev/hda not keeping dma settings |
 |
|
Running Gentoo 1.4rc1 for over a month now.
I have the following in my /etc/conf.d/local.start
hdparm -qX udma4 -qd 1 -qu 1 -qc 3 /dev/cdroms/cdrom0
hdparm -qX mdma2 -qd 1 -qu 1 -qc 3 /dev/cdroms/cdrom1
hdparm -qu 1 -gm 16 -qc 3 -qX udma2 -qd 1 /dev/hda
To enable the settings I want for my different drives
The cdrom's take the settings without question, but the hard drive (an IBM 40 gig) will not maintain using_dma
I am running kernel 2.4.20 (and had the same problem in 2.4.19). I know that I have the chipset support enabled statically in the kernel (I have an Abit KT7A, which is on the VIA KT133A chip, with the HPT370 chipset). I have use dma enabled in the kernel as well.
Even with those settings in the local.start, the hard drive doesn't keep the dma settings. If I su - and change it, it keeps dma until I close the su terminal, and then it goes back to 0.
hdparm /dev/hda shows this:
/dev/hda:
multcount = 16 (on)
IO_support = 3 (32-bit w/sync)
unmaskirq = 1 (on)
using_dma = 0 (off)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 5005/255/63, sectors = 80418240, start = 0
and hdparm -i /dev/hda shows this:
/dev/hda:
Model=IC35L040AVER07-0, FwRev=ER4OA44A, SerialNo=SXPTXND0861
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40
BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=80418240
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 *udma2 udma3 udma4 udma5
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: ATA/ATAPI-5 T13 1321D revision 1: 2 3 4
the hard drive is ATA 100, and the motherboard has ATA 100 support, and I am using the appropriate cables. DMA works fine in windows, but I would really like to get this working. I believe it is what is causing some unexplained errors in the runtime. If I ever download anything, and have xmms playing at the same time, it will begin to skip. If I compile anything, the mouse freezes and is very jerky, especially while unpacking tarbells.
Any Ideas?
Last edited by DesertFox on Sat Dec 14, 2002 12:09 am; edited 1 time in total |
|
| Back to top |
|
 |
DesertFox
n00b
Joined: 14 Nov 2002
Posts: 53
|
| Posted: Fri Dec 13, 2002 9:34 pm Post subject: |
|
|
Another Bit of Info:
I ran dmesg and got the following:
Linux version 2.4.20 () (gcc version 3.2) #2 SMP Thu Dec 12 21:50:41 Local time zone must be set--see zic
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000000fff0000 (usable)
BIOS-e820: 000000000fff0000 - 000000000fff3000 (ACPI NVS)
BIOS-e820: 000000000fff3000 - 0000000010000000 (ACPI data)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
255MB LOWMEM available.
On node 0 totalpages: 65520
zone(0): 4096 pages.
zone(1): 61424 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/hda7 append="hdd=ide-scsi"
Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
Initializing CPU#0
Detected 800.045 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 1595.80 BogoMIPS
Memory: 255136k/262080k available (2429k kernel code, 6560k reserved, 708k data, 128k init, 0k highmem)
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes)
Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 64K (64 bytes/line)
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: After generic, caps: 0183fbff c1c7fbff 00000000 00000000
CPU: Common caps: 0183fbff c1c7fbff 00000000 00000000
Enabling fast FPU save and restore... 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
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 64K (64 bytes/line)
Intel machine check reporting enabled on CPU#0.
CPU: After generic, caps: 0183fbff c1c7fbff 00000000 00000000
CPU: Common caps: 0183fbff c1c7fbff 00000000 00000000
CPU0: AMD Duron(tm) Processor stepping 01
per-CPU timeslice cutoff: 182.79 usecs.
SMP motherboard not detected.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 800.0313 MHz.
..... host bus clock speed is 200.0078 MHz.
cpu: 0, clocks: 2000078, slice: 1000039
CPU0<T0:2000064,T1:1000016,D:9,S:1000039,C:2000078>
Waiting on wait_init_idle (map = 0x0)
All processors have done init_idle
PCI: PCI BIOS revision 2.10 entry at 0xfb430, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router VIA [1106/0686] at 00:07.0
Applying VIA southbridge workaround.
PCI: Disabling Via external APIC routing
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
IA-32 Microcode Update Driver: v1.11 <tigran@veritas.com>
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16)
Starting kswapd
Journalled Block Device driver loaded
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
NTFS driver v1.1.22 [Flags: R/O]
udf: registering filesystem
parport0: PC-style at 0x378 [PCSPP(,...)]
parport_pc: Via 686A parallel port: io=0x378
Detected PS/2 Mouse Port.
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-0 with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
lp0: using parport0 (polling).
gameport0: Emu10k1 Gameport at 0xe400 size 8 speed 1242 kHz
ppdev: user-space parallel port driver
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: detected chipset, but driver not compiled in!
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:DMA, hdd:DMA
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide0: reset: success
Which Has quite a few errors in it
Last edited by DesertFox on Sun Dec 15, 2002 5:37 am; edited 1 time in total |
|
| Back to top |
|
|
darktux
Veteran
Joined: 16 Nov 2002
Posts: 1086
Location: Coimbra, Portugal
|
| Posted: Sat Dec 14, 2002 12:01 am Post subject: |
|
|
| Quote: | VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: detected chipset, but driver not compiled in!
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
|
UH OH! Check your kernel's setting... You're saying one thing, but the kernel is spitting out another 
_________________
Lego my ego, and I'll lego your knowledge
www.tuxslare.org - My reborn website  |
|
| Back to top |
|
|
DesertFox
n00b
Joined: 14 Nov 2002
Posts: 53
|
| Posted: Sat Dec 14, 2002 12:10 am Post subject: |
|
|
| Quote: | | UH OH! Check your kernel's setting... You're saying one thing, but the kernel is spitting out another |
Yes, I know.. Thats why I posted it. So I could get help, not fairly clear observations about what I already posted. |
|
| Back to top |
|
|
Malakin
Veteran
Joined: 14 Apr 2002
Posts: 1692
Location: Victoria BC Canada
|
| Posted: Sat Dec 14, 2002 3:06 am Post subject: |
|
|
| So you're saying you have "VIA82CXXX chipset support" enabled in the kernel? |
|
| Back to top |
|
|
DesertFox
n00b
Joined: 14 Nov 2002
Posts: 53
|
| Posted: Sat Dec 14, 2002 6:25 am Post subject: |
|
|
| Is that the one I need? HPT370 is what I found was the module for the motherboard, but it obviously isn't. |
|
| Back to top |
|
|
darktux
Veteran
Joined: 16 Nov 2002
Posts: 1086
Location: Coimbra, Portugal
|
| Posted: Sat Dec 14, 2002 3:24 pm Post subject: |
|
|
| Quote: | I am running kernel 2.4.20 (and had the same problem in 2.4.19). I know that I have the chipset support enabled statically in the kernel (I have an Abit KT7A, which is on the VIA KT133A chip, with the HPT370 chipset). I have use dma enabled in the kernel as well.
|
| Quote: |
Quote:
UH OH! Check your kernel's setting... You're saying one thing, but the kernel is spitting out another
Yes, I know.. Thats why I posted it. So I could get help, not fairly clear observations about what I already posted. |
First you told us that the module was enabled, then I told you that your dmesg was saying that it wasn't, now you're telling me that you already knew that  and that I'm just pointing out the obvious?
Sorry if I was trying to help. My mistake.....
Malakin, take it from here 
_________________
Lego my ego, and I'll lego your knowledge
www.tuxslare.org - My reborn website |
|
| Back to top |
|
|
DesertFox
n00b
Joined: 14 Nov 2002
Posts: 53
|
| Posted: Sun Dec 15, 2002 12:06 am Post subject: |
|
|
| ehh, sry. i am in the middle of finals week here, and am a little burned out. What i meant was that, as far as I knew, the hpt370 module was the module for the motherboard i had. according to my boot messages, it isn't. I was wondering what the correct module would be. |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Sun Dec 15, 2002 12:10 am Post subject: |
|
|
A total shot in the dark, but how about trying a 2.4.18 kernel? See Problems booting - Kernel Panic. for details.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
DesertFox
n00b
Joined: 14 Nov 2002
Posts: 53
|
| Posted: Sun Dec 15, 2002 5:29 am Post subject: |
|
|
well, i got it working by simply compiling every chipset into the kernel, but i would still like to know exactly which chipset it is using. ( so it can work with 2.4.20)
good suggestion though |
|
| Back to top |
|
|
darktux
Veteran
Joined: 16 Nov 2002
Posts: 1086
Location: Coimbra, Portugal
|
| Posted: Sun Dec 15, 2002 4:59 pm Post subject: |
|
|
| Malakin wrote: | | So you're saying you have "VIA82CXXX chipset support" enabled in the kernel? |
Have you tried the VIA chipset DesertFox? What does your dmesg say now?
_________________
Lego my ego, and I'll lego your knowledge
www.tuxslare.org - My reborn website |
|
| Back to top |
|
|
iKiddo
Guru
Joined: 27 Jun 2002
Posts: 329
Location: Europe?
|
| Posted: Sun Dec 15, 2002 8:04 pm Post subject: |
|
|
| DesertFox wrote: | well, i got it working by simply compiling every chipset into the kernel, but i would still like to know exactly which chipset it is using. ( so it can work with 2.4.20)
good suggestion though |
Why, that would be simple, now wouldn't it? Either check your output from boot (or dmesg) to see for which chipset the kernel enables/detects stuff. Or (might be a little time-consuming) unable a random module, recompile, move bzImage/enable correct modules, and see if it still works, if so, unable another one etc. etc.
Last edited by iKiddo on Sun Dec 15, 2002 10:10 pm; edited 1 time in total |
|
| Back to top |
|
|
darktux
Veteran
Joined: 16 Nov 2002
Posts: 1086
Location: Coimbra, Portugal
|
| Posted: Sun Dec 15, 2002 9:24 pm Post subject: |
|
|
| iKiddo wrote: | | DesertFox wrote: | well, i got it working by simply compiling every chipset into the kernel, but i would still like to know exactly which chipset it is using. ( so it can work with 2.4.20)
good suggestion though |
Why, that would be simple, now wouldn't it? Either check your output from boot (or dmesg) to see for which chipset the kernel enables/detects stuff. Or (
might be a little time-consuming) unable a random module, recompile, move bzImage/enable correct modules, and see if it still works, if so, unable another one etc. etc. |
As I have told him, watching the kernel log, should be enough.. Recompiling and trying isn't a very _smart_ thing to do..
_________________
Lego my ego, and I'll lego your knowledge
www.tuxslare.org - My reborn website |
|
| Back to top |
|
|
iKiddo
Guru
Joined: 27 Jun 2002
Posts: 329
Location: Europe?
|
| Posted: Sun Dec 15, 2002 10:13 pm Post subject: |
|
|
I understand it will be time consuming ( as I noted above ), but I see no way of breaking stuff. ... Wait a sec, I've seen the light 80
When you reach the setting you actually want to compile the kernel will break and you won't be able to log into your system!! AAAAAHHHHH
..
Oops, I forgot the darn thing wasn't enabled to start with... |
|
| Back to top |
|
|
darktux
Veteran
Joined: 16 Nov 2002
Posts: 1086
Location: Coimbra, Portugal
|
| Posted: Sun Dec 15, 2002 11:49 pm Post subject: |
|
|
And then again, as I've said before, the kernel always spits out some usefull info
| Quote: | ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 89
PCI: Hardcoded IRQ 14 for device 00:11.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci00:11.1
ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:pio, hdd:DMA
|
_________________
Lego my ego, and I'll lego your knowledge
www.tuxslare.org - My reborn website |
|
| Back to top |
|
|
Pigeon
Guru
Joined: 21 Jun 2002
Posts: 307
|
| Posted: Mon Dec 16, 2002 12:24 am Post subject: |
|
|
| You should have the Generic IDE support, HPT366/368/370, and VIA82CXXX support enabled in the kernel for that motherboard. Also include the Highpoint 370 software RAID support if you plan on using RAID, but it's not necessary if you plan on using it as a normal IDE controller. |
|
| Back to top |
|
|
DesertFox
n00b
Joined: 14 Nov 2002
Posts: 53
|
| Posted: Mon Dec 16, 2002 6:34 am Post subject: |
|
|
| Quote: | | You should have the Generic IDE support, HPT366/368/370, and VIA82CXXX support enabled in the kernel for that motherboard. Also include the Highpoint 370 software RAID support if you plan on using RAID, but it's not necessary if you plan on using it as a normal IDE controller. |
Thanks.
and thanks for all your comments
I haven't been running linux for a super long time and am still learning it inside and out |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Other Things Gentoo
