I've screwed up badly...please help.
Ok. I have really big issue. I had an Asus A7V that had a Promise IDE raid controller on it. I had both my hard drives on it and the CDROM's on the regular ATA controller. I've switched to a P4PE board that doesn't have a Promise or any other raid controller on it. I think my /dev/ directory is frelled up because I can't set dma mode to either hda or hdb because the devices are configured as if they were cdrom's and not hd's. I say this because of this.. Where the first hd is now: brw-rw---- 1 root disk 3, 0 Apr 12 2002 /dev/hda Where the first hd was: brw-rw---- 1 root disk 33, 0 Apr 12 2002 /dev/hde Notice that hda has a 3, and hde has the 33, in the lines above. I think I need to remake (if that's the correct term) the devices hda and hdb so that I can enable DMA mode. Not using DMA mode is frelling painful..oh God is it painful. So if anyone can help a poor dumbass out and help me fix this. I would be eternally grateful. Thanks to anyone who can help. -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I'll tell you what you should see.
On Monday 07 April 2003 08:36, Ben Rosenberg wrote:
I can't set dma mode to either hda or hdb because the devices are configured as if they were cdrom's and not hd's.
As far as I know there's no difference in how they're configured in /dev. You may need to use hdparm to set device specific settings.
I say this because of this..
Where the first hd is now:
brw-rw---- 1 root disk 3, 0 Apr 12 2002 /dev/hda
Where the first hd was:
brw-rw---- 1 root disk 33, 0 Apr 12 2002 /dev/hde
Notice that hda has a 3, and hde has the 33, in the lines above.
Yes, hda is major 3, minor 0 and hde is major 33, minor 0. Those are constant, regardless of what devices are actually connected to them.
I think I need to remake (if that's the correct term) the devices hda and hdb so that I can enable DMA mode.
Are you sure the kernel has support for dma on that mobo? When I recently set up a dvd player, I had problems configuring DMA. When I set it, the kernel kept turning it off again. What I eventually discovered was that the kernel wasn't detecting that the device was using udma2. After telling it, with "hdparm -Xudma2" everything worked. Check the boot messages and see if the disks are detected with dma. You may need to do something similar to get dma running. But you shouldn't have to touch the device nodes. Those are always the same. regards Anders
* Anders Johansson (andjoh@rydsbo.net) [030406 23:53]: -> ->Are you sure the kernel has support for dma on that mobo? -> ->When I recently set up a dvd player, I had problems configuring DMA. When I ->set it, the kernel kept turning it off again. What I eventually discovered ->was that the kernel wasn't detecting that the device was using udma2. After ->telling it, with "hdparm -Xudma2" everything worked. -> ->Check the boot messages and see if the disks are detected with dma. You may ->need to do something similar to get dma running. -> ->But you shouldn't have to touch the device nodes. Those are always the same. No. I'm not sure that it has support for DMA on this motherboard. I'm using 8.0 so of course it may very well not have it. I used "hdparm -Xudma2" on hda and it says "-X: missing value" and doesn't do squat to the device. This kinda sucks. I kinda jumped the gun on this upgrade. I was going to wait for 8.2 to hit the Oakland SuSE office before doing this and I was just going to do a fresh install. *sigh* -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I'll tell you what you should see.
On Monday 07 April 2003 08:58, Ben Rosenberg wrote:
I used "hdparm -Xudma2" on hda and it says "-X: missing value" and doesn't do squat to the device.
Sorry, my mistake. It should be "hdparm -X udma2". But check first that the device actually is udma2. Setting the wrong value with hdparm could physically harm the device.
* Anders Johansson (andjoh@rydsbo.net) [030407 00:02]: ->On Monday 07 April 2003 08:58, Ben Rosenberg wrote: ->> I used "hdparm -Xudma2" on hda and it says "-X: missing value" and ->> doesn't do squat to the device. -> ->Sorry, my mistake. It should be "hdparm -X udma2". -> ->But check first that the device actually is udma2. Setting the wrong value ->with hdparm could physically harm the device. According to Mads Joergensen and Jens Axboe..2.4.18 doesn't know what the hell my IDE controller is. I'm downloading Huberts 2.4.20 kernel. I'll tell ya if it works. -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I'll tell you what you should see.
* Ben Rosenberg <ben@whack.org> [Apr 07. 2003 09:14]:
According to Mads Joergensen and Jens Axboe..2.4.18 doesn't know what the hell my IDE controller is. I'm downloading Huberts 2.4.20 kernel. I'll tell ya if it works.
Just talked to Ben before he went to sleep. Everything works fine now. -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogical, with just a little bit more effort?" -- A. P. J.
participants (3)
-
Anders Johansson -
Ben Rosenberg -
Mads Martin Jorgensen