[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#420299: marked as done (Jmicron Harddrive Controller Issue on Boot, Sometimes loads jmicron361 and other times loads jmicron363)

Your message dated Thu, 25 Dec 2008 20:12:39 +0100
with message-id <20081225191239.GA7001@galadriel.inutil.org>
and subject line Bounces
has caused the Debian Bug report #420299,
regarding Jmicron Harddrive Controller Issue on Boot, Sometimes loads jmicron361 and other times loads jmicron363
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

420299: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=420299
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: kernel

Version: 2.6.18-4-amd64 and 32bit

Hardware: Gigabyte 965P-S3 e.g. any motherboard im assuming that uses the jmicron controller.

Hardware Setup: 3 x HDD, 2 drivers are sata2 drives and 1 drive is a IDE drive, all these drives use the jmicron controller.


On boot up debian will sometimes load the jmicron361 driver and on other times will load the jmicron363 driver.

This issue will cause the system to get stuck with the "control d" as it cannot locate the IDE when it has used the 361 driver after several reboots it will use the 363 driver and the issue has gone until another reboot and the 361 driver has been loaded again than more reboots will be needed until the 363 driver has been loaded.

This issue is only with the IDE drive not being picked up by debian, i should say debian still loads the drive but changes from hdf5 to hdb5 depending on what driver is loaded 363 or 361 but as you know the fstab will have to be changed every time but you cannot do this as you do not know which driver will be loaded.


--- End Message ---
--- Begin Message ---
The mail address of the submitter bounces, closing the bug.


--- End Message ---

Reply to: