Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
accessing cdrom slows down the system [SOLVED]
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2  
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
sonicbhoc
Veteran
Veteran


Joined: 24 Oct 2005
Posts: 1805
Location: In front of the computer screen

PostPosted: Sun Apr 22, 2007 12:29 pm    Post subject: Reply with quote

Yes, it was hald's fault but after fixing this it doesn't happen anymore. Thank you!

Also, should I enable jmicron support, and if I should, I don't know which driver is right for my hardware...
_________________
I'm too lazy to keep this stupid signature up to date, so here's something more interesting:
My friend Hetdegon can draw if you ask me.
Now using PClinuxOS on my laptop and Gentoo on my desktop and new laptop.
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Sun Apr 22, 2007 3:05 pm    Post subject: Reply with quote

From the previous post: JMicron 20360/20363 support is provided by pata_jmicron in the same group ["Serial ATA ..."]. There is also an old PATA driver, jmicron, under ATA/ATAPI/MFM/RLL if the new PATA one doesn't work.

There are two entries in /usr/share/misc/pic.ids for JMicron 20360/20363
Code:
        2360  JMicron 20360/20363 AHCI Controller
        2363  JMicron 20360/20363 AHCI Controller
pata_jmicron and jmicron only support the second, "2363", the other, "2360", is probably an old version of the chipset which is no longer around but you could check with "lspci -n".
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details.
Back to top
View user's profile Send private message
sonicbhoc
Veteran
Veteran


Joined: 24 Oct 2005
Posts: 1805
Location: In front of the computer screen

PostPosted: Sun Apr 22, 2007 3:38 pm    Post subject: Reply with quote

lspci -n | grep 236 returned:
Code:
04:00.0 0106: 197b:2360 (rev 02)

So, mine is old. But, everything works just fine, so I don't care about it. :lol:
_________________
I'm too lazy to keep this stupid signature up to date, so here's something more interesting:
My friend Hetdegon can draw if you ask me.
Now using PClinuxOS on my laptop and Gentoo on my desktop and new laptop.
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Sun Apr 22, 2007 3:55 pm    Post subject: Reply with quote

That's odd. It seems to overthrow a few dearly held theories.

What kernel are you running?

[Edit] Nope, can't make it out: according to my bible (Greg Kroah-Hartman's "Linux Kernel in a Nutshell") "All PCI drivers contain a list of the different devices they support. That list is contained in a structure of struct pci_device_id values".

In the jmicron old PATA driver from 2.6.19-gentoo-r5, the first with either jmicron.c or pata_jmicron.c, the list is
Code:
static const struct pci_device_id jmicron_pci_tbl[] = {
   { PCI_VDEVICE(JMICRON, PCI_DEVICE_ID_JMICRON_JMB361), 361},
   { PCI_VDEVICE(JMICRON, PCI_DEVICE_ID_JMICRON_JMB363), 363},
   { PCI_VDEVICE(JMICRON, PCI_DEVICE_ID_JMICRON_JMB365), 365},
   { PCI_VDEVICE(JMICRON, PCI_DEVICE_ID_JMICRON_JMB366), 366},
   { PCI_VDEVICE(JMICRON, PCI_DEVICE_ID_JMICRON_JMB368), 368},

   { }   /* terminate list */
};
which shows that only the JMicron controllers with Device IDs 2361, 2363, 2365, 2366 or 2368 should be supported. But your controller says it is 2360.

One last request: could you run
Code:
cat /sys/bus/pci/devices/0000:04:00.0/device
it will probably say the same as lspci but it would be interesting to know, if you can spare the time.

[Edit] If you're minded to do a last request could you cancel that one and do this instead?

I am assuming you have your optical drive(s) plugged into the JMicron controller.

If you run "ls -l /sys/block" you will get a list of the block devices on your system: your SATA disk or disks will be sdX and your optical drive or drives will be hdX, if an old PATA driver has got hold of them, or sr0, sr1, if a new PATA driver has them.

Could you run the following on the optical drive device
Code:
udevinfo -a -p /sys/block/hda | grep DRIVER
(replace hda by the appropriate device name) and post the output?

Thanks.
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details.


Last edited by wynn on Sun Apr 22, 2007 7:07 pm; edited 1 time in total
Back to top
View user's profile Send private message
sonicbhoc
Veteran
Veteran


Joined: 24 Oct 2005
Posts: 1805
Location: In front of the computer screen

PostPosted: Sun Apr 22, 2007 7:00 pm    Post subject: Reply with quote

wynn wrote:
sonicbhoc wrote:
So, does this mean that I should install ATA/ATAPI/MFM/RLL Support after all?
No, (I believe) it was just for the case where there is a single Intel SATA controller which has to provide both IDE and SATA.

sonicbhoc wrote:
EDIT: By the way, just to make sure I'm not missing anything, my lspci is like so:
Code:
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02)
...
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
04:00.0 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 02)
...
05:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet (rev 10)
Is there anything else I'll need? The JMicron IDE interface looks like it could need some extra stuff. Pretty much everything else works but I haven't tested the card Ricoh reader or firewire yet.
The Intel 82801GBM/GHM SATA support is provided by ata_piix under "Serial ATA ...", JMicron 20360/20363 support is provided by pata_jmicron in the same group. There is also an old PATA driver, jmicron, under ATA/ATAPI/MFM/RLL if the new PATA one doesn't work.

Firewire should be generic (I think), the Intel Wireless 3945ABG you will have to dig through the Forums for. NeddySeagoon's tip using " 3945 site:forums.gentoo.org" with Google should make it painless :) (had to try the tip, found ipw3945 wireless drivers which says ther's an ebuild)

The driver for Realtek's RTL-8110SC/8169SC is r8169.

I think you know your way around menuconfig so you shouldn't need more detail, should you?


I already had all that working, though, just the ATA thing was giving me a headache. I think, with your help, I figured it out. However, the last time I tried to burn a CD, my computer went haywire: GkrellM showed everything normal, but the GUI was completely unresponsive. I could view events just fine, but I couldn't interface with anything (no clicking, no keyboards, I couldn't switch to a VT, I didn't have sshd on so I couldn't save the system...). The problem is probably that I mucked with some of the CD settings that warned me not to change them in the kernel config, and maybe I should turn on support for that jmicron thing? I'll post my device information after I reboot the computer...

Here it is:
Code:
0x2360


Does this mean that the driver will not work on my controller or what?
_________________
I'm too lazy to keep this stupid signature up to date, so here's something more interesting:
My friend Hetdegon can draw if you ask me.
Now using PClinuxOS on my laptop and Gentoo on my desktop and new laptop.
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Sun Apr 22, 2007 7:14 pm    Post subject: Reply with quote

The edit to my last post and your new post crossed.

I think it will sort things out if you could run that last last request:
Quote:
I am assuming you have your optical drive(s) plugged into the JMicron controller.

If you run "ls -l /sys/block" you will get a list of the block devices on your system: your SATA disk or disks will be sdX and your optical drive or drives will be hdX, if an old PATA driver has got hold of them, or sr0, sr1, if a new PATA driver has them.

Could you run the following on the optical drive device
Code:
udevinfo -a -p /sys/block/hda | grep DRIVER
(replace hda by the appropriate device name) and post the output?
This should show what driver the CD/DVD writer is using, please post the /sys/block/xxx, the device name, which you have used. This would be another clue to what is going on.
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details.
Back to top
View user's profile Send private message
sonicbhoc
Veteran
Veteran


Joined: 24 Oct 2005
Posts: 1805
Location: In front of the computer screen

PostPosted: Sun Apr 22, 2007 7:30 pm    Post subject: Reply with quote

wynn wrote:
The edit to my last post and your new post crossed.

I think it will sort things out if you could run that last last request:
Quote:
I am assuming you have your optical drive(s) plugged into the JMicron controller.

(I still don't know what a JMicron controller is)
Nope, or it doesn't look like it at least. I don't have a single thing plugged into my laptop but a mouse.

wynn wrote:

If you run "ls -l /sys/block" you will get a list of the block devices on your system: your SATA disk or disks will be sdX and your optical drive or drives will be hdX, if an old PATA driver has got hold of them, or sr0, sr1, if a new PATA driver has them.

Not a single hdX in there anywhere. Everything is sda, sdb and sr0. sdb used to be sg0 but I chagned the bios in my computer to only use ATA stuff.

wynn wrote:

Could you run the following on the optical drive device
Code:
udevinfo -a -p /sys/block/hda | grep DRIVER
(replace hda by the appropriate device name) and post the output?
This should show what driver the CD/DVD writer is using, please post the /sys/block/xxx, the device name, which you have used. This would be another clue to what is going on.


Every drive in my computer (two of them) use the ati_piix driver.
_________________
I'm too lazy to keep this stupid signature up to date, so here's something more interesting:
My friend Hetdegon can draw if you ask me.
Now using PClinuxOS on my laptop and Gentoo on my desktop and new laptop.
Back to top
View user's profile Send private message
wynn
Advocate
Advocate


Joined: 01 Apr 2005
Posts: 2421
Location: UK

PostPosted: Sun Apr 22, 2007 8:04 pm    Post subject: Reply with quote

In your lspci you have
Code:
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02)
04:00.0 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 02)
The second one is the JMicron controller, although it says "AHCI" it does both SATA and PATA.

From posts I've seen, it appears that this controller is used on the motherboard to provide PATA.

Therefore I assumed that your PATA optical drive would be plugged into this controller but, from what you say, there is an old-type IDE socket which is connected to the Intel SATA IDE controller.

If that is so, this Intel controller is capable of providing both and you are in the same position as the original poster, ham_se17, and the solution he posted should work for you.

With the corrections that have appeared since that post, the solution is:

1) Enable "ATA/ATAPI/MFM/RLL support", you need CONFIG_IDE=y in your config but you don't need anything else under this heading. This contradicts ham_se17's first point but it is required.

2) Add SATA support under "Serial ATA ..." for Intel PIIX/ICH SATA support (which you already have)

3) You don't need to add "libata.atapi_enabled=1" to the kernel command line as it is already enabled by default.

The last step you have already verified, you've got a /dev/sr0: could you please post the output from
Code:
udevinfo -a -p /sys/block/sr0 | grep DRIVER


If everything is seizing up when you try and write a CD, it shows that DMA is not enabled on the CD writer but, if you have all the above points, your result should be the same as ham_se17's.

Can you check /var/log/messages to see if it is setting DMA in the CD writer?

Other posts have suggested running sdparm on the device to check that DMA is enabled.
_________________
The avatar is jorma, a "duck" from "Elephants Dream": the film and all the production materials have been made available under a Creative Commons Attribution 2.5 License, see orange.blender.org for details.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Goto page Previous  1, 2
Page 2 of 2

 
Jump to:  
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