Re: CF Card Adapter White List Candidate

Re: CF Card Adapter White List Candidate

[Tom Denchfield]

Hello,

Tejun, this CF card adapter plugs directly into an IDE socket (Channel 0, in my case) on a desktop computer motherboard.  You can see a picture of the adapter in the following URL01:

URL01: http://preview.tinyurl.com/233u92u

I have to power the adapter with a floppy drive power plug because my motherboard's IDE sockets were intentionally manufactured without the pin that could have supplied power through an IDE cable.

Does anyone have a top of the head opinion as to whether there are inherent usage limitations in either this passive CF card adapter and/or in the Linux kernel used with Ubuntu v10.10 that would prevent users with CF cards faster than UDMA/66 (see URL02 below) from being configured by Linux to work at speeds above UDMA/66?  The reason that I ask this question is that I bought both my UDMA/66 CF card and the adapter from the URL01 seller.  It is foreseeable that a lot of customers might have purchased faster CF cards envisioning that they would work at speeds higher than UDMA/66 with the adapter.  The 'Technical Details' section of URL01 does not state anything about UDMA speed usage limitations. 

URL02: http://www.hjreggel.net/cardspeed/index.html

I think that there are CF card adapters on eBay that are similar to the one pictured in URL01 above, and there are also IDE adapters that will hold two CF cards.

Tom

--- On Wed, 1/5/11, Tejun Heo <htejun@gmail.com> wrote:

> From: Tejun Heo <htejun@gmail.com>
> Subject: Re: CF Card Adapter White List Candidate
> To: "Robert Hancock" <hancockrwd@gmail.com>
> Cc: "Tom Denchfield" <td_denchfield@yahoo.com>, linux-ide@vger.kernel.org
> Date: Wednesday, January 5, 2011, 5:51 AM
> Hello,
> 
> On Tue, Jan 04, 2011 at 10:19:17PM -0600, Robert Hancock
> wrote:
> > On 01/04/2011 04:18 PM, Tom Denchfield wrote:
> >> As you further recommended, in an attempt to get
> the SD-CF-IDE-DI
> >> IDE to CF Adapter that holds my CF card white
> listed, I am
> >> submitting the attached
> >>
> libata_force_80c_CF_card_adapter_whitelist_candidate_information.txt
> >> file that has the output from executing four
> terminal commands to
> >> hopefully supply enough information to get it
> whitelisted.
> 
> Thanks.
> 
> >> Although I expect that my RV280 Radeon 9200 Pro
> video card is too
> >> old to expend much effort on, it would be nice to
> also get it
> >> whitelisted so that future newbie Linux users who
> do not know about
> >> using the radeon.modeset=0 parameter on the kernel
> command line
> >> will not be looking at a black screen with a
> blinking cursor when
> >> they attempt to use a LiveCD for troubleshooting,
> or whatever.
> >>
> >> I purposely did not include the URL of one of the
> Internet sites
> >> that sells the adapter in this email in case this
> is a no no.
> 
> I don't think that's a no no unless the intention is
> commercial.
> 
> >> Tejun, I am not sure that I will have either the
> time or the
> >> interest to learn the intricacies of editing
> >> http://www.thinkwiki.org/wiki/Compact_Flash_boot_drive
> to add
> >> libata.force=80c to this site in lieu of
> force_cbl=80: so that
> >> fewer people will be asking you questions.  I
> have a ThinkPad
> >> without a HDD plus a laptop adapter that will hold
> my CF card, but
> >> my Think Pad is a lot older than the ones
> discussed on
> >> Compact_Flash_boot_drive.  In addition, I did
> not see any recent
> >> updates to this Internet page, but maybe I can
> find someone to
> >> email who will update this page.
> 
> Yeah, just ping someone.
> 
> > Is there actually any way to identify the adapter
> automatically?
> > AFAIK, these CF-IDE adapters are just passive
> circuitry and there's
> > no way to identify them through software.
> 
> Hmmm... I was thinking this was somehing integrated to the
> machine (so
> the dmidecode), in which case we can combine dmi + pci
> function # +
> port # to whitelist the device, which we already do for
> some type of
> quirks.  If it's a plug in device, we obviously can't
> identify it.
> Tom, is the CF slot integrated to the machine or is it
> something you
> put into the PCMCIA slot?
> 
> Thanks.
> 
> -- 
> tejun
>


      

Re: CF Card Adapter White List Candidate

[Robert Hancock]

On Wed, Jan 5, 2011 at 12:18 PM, Tom Denchfield <td_denchfield@yahoo.com> wrote:
> Hello,
>
> Tejun, this CF card adapter plugs directly into an IDE socket (Channel 0, in my case) on a desktop computer motherboard.  You can see a picture of the adapter in the following URL01:
>
> URL01: http://preview.tinyurl.com/233u92u
>
> I have to power the adapter with a floppy drive power plug because my motherboard's IDE sockets were intentionally manufactured without the pin that could have supplied power through an IDE cable.
>
> Does anyone have a top of the head opinion as to whether there are inherent usage limitations in either this passive CF card adapter and/or in the Linux kernel used with Ubuntu v10.10 that would prevent users with CF cards faster than UDMA/66 (see URL02 below) from being configured by Linux to work at speeds above UDMA/66?  The reason that I ask this question is that I bought both my UDMA/66 CF card and the adapter from the URL01 seller.  It is foreseeable that a lot of customers might have purchased faster CF cards envisioning that they would work at speeds higher than UDMA/66 with the adapter.  The 'Technical Details' section of URL01 does not state anything about UDMA speed usage limitations.
>
> URL02: http://www.hjreggel.net/cardspeed/index.html
>
> I think that there are CF card adapters on eBay that are similar to the one pictured in URL01 above, and there are also IDE adapters that will hold two CF cards.

The reason the speed is being limited to 33 is that the cable
detection code is detecting that an 80-wire cable doesn't appear to be
connected. In order for an 80-wire cable to be detected, pin 34 on the
cable is supposed to be grounded at the motherboard end. In the case
of this adapter, since it plugs directly into the motherboard, it
would have to be grounding pin 34 to get an 80-wire detection, but
presumably it's not.

>
> Tom
>
> --- On Wed, 1/5/11, Tejun Heo <htejun@gmail.com> wrote:
>
>> From: Tejun Heo <htejun@gmail.com>
>> Subject: Re: CF Card Adapter White List Candidate
>> To: "Robert Hancock" <hancockrwd@gmail.com>
>> Cc: "Tom Denchfield" <td_denchfield@yahoo.com>, linux-ide@vger.kernel.org
>> Date: Wednesday, January 5, 2011, 5:51 AM
>> Hello,
>>
>> On Tue, Jan 04, 2011 at 10:19:17PM -0600, Robert Hancock
>> wrote:
>> > On 01/04/2011 04:18 PM, Tom Denchfield wrote:
>> >> As you further recommended, in an attempt to get
>> the SD-CF-IDE-DI
>> >> IDE to CF Adapter that holds my CF card white
>> listed, I am
>> >> submitting the attached
>> >>
>> libata_force_80c_CF_card_adapter_whitelist_candidate_information.txt
>> >> file that has the output from executing four
>> terminal commands to
>> >> hopefully supply enough information to get it
>> whitelisted.
>>
>> Thanks.
>>
>> >> Although I expect that my RV280 Radeon 9200 Pro
>> video card is too
>> >> old to expend much effort on, it would be nice to
>> also get it
>> >> whitelisted so that future newbie Linux users who
>> do not know about
>> >> using the radeon.modeset=0 parameter on the kernel
>> command line
>> >> will not be looking at a black screen with a
>> blinking cursor when
>> >> they attempt to use a LiveCD for troubleshooting,
>> or whatever.
>> >>
>> >> I purposely did not include the URL of one of the
>> Internet sites
>> >> that sells the adapter in this email in case this
>> is a no no.
>>
>> I don't think that's a no no unless the intention is
>> commercial.
>>
>> >> Tejun, I am not sure that I will have either the
>> time or the
>> >> interest to learn the intricacies of editing
>> >> http://www.thinkwiki.org/wiki/Compact_Flash_boot_drive
>> to add
>> >> libata.force=80c to this site in lieu of
>> force_cbl=80: so that
>> >> fewer people will be asking you questions.  I
>> have a ThinkPad
>> >> without a HDD plus a laptop adapter that will hold
>> my CF card, but
>> >> my Think Pad is a lot older than the ones
>> discussed on
>> >> Compact_Flash_boot_drive.  In addition, I did
>> not see any recent
>> >> updates to this Internet page, but maybe I can
>> find someone to
>> >> email who will update this page.
>>
>> Yeah, just ping someone.
>>
>> > Is there actually any way to identify the adapter
>> automatically?
>> > AFAIK, these CF-IDE adapters are just passive
>> circuitry and there's
>> > no way to identify them through software.
>>
>> Hmmm... I was thinking this was somehing integrated to the
>> machine (so
>> the dmidecode), in which case we can combine dmi + pci
>> function # +
>> port # to whitelist the device, which we already do for
>> some type of
>> quirks.  If it's a plug in device, we obviously can't
>> identify it.
>> Tom, is the CF slot integrated to the machine or is it
>> something you
>> put into the PCMCIA slot?
>>
>> Thanks.
>>
>> --
>> tejun
>>
>
>
>
>

Re: CF Card Adapter White List Candidate

[Tejun Heo]

Hello,

On Wed, Jan 05, 2011 at 05:47:49PM -0600, Robert Hancock wrote:
> > Tejun, this CF card adapter plugs directly into an IDE socket
> > (Channel 0, in my case) on a desktop computer motherboard.  You
> > can see a picture of the adapter in the following URL01:

Oh, okay, so it's a plugin device.  For some reason, I thought the
machine in question was a laptop and the CF slot was built-in.

> The reason the speed is being limited to 33 is that the cable
> detection code is detecting that an 80-wire cable doesn't appear to be
> connected. In order for an 80-wire cable to be detected, pin 34 on the
> cable is supposed to be grounded at the motherboard end. In the case
> of this adapter, since it plugs directly into the motherboard, it
> would have to be grounding pin 34 to get an 80-wire detection, but
> presumably it's not.

Yeap, it's the device failing to wire cable detection properly.
Unfortunately, it's impossible to detect and work around
automatically.

Thanks.

-- 
tejun

Re: CF Card Adapter White List Candidate

[Tom Denchfield]

Hello,

Michael, this is one of the CF card adapters that has a jumper, JP1, that has the Pin-20 power source option as you suggest below.  The factory default position is external power (floppy disk power plug), and the alternative position is: "IDE Pin-20."  The the settings for the three jumpers are on the jumper's printed circuit board under the CF Card.  Sorry I didn't look at the one-sheet instruction sheet that I cannot find right now, but Michael's email reminded me to look under the CF Card.

Tom 

--- On Sat, 1/8/11, Michael Tokarev <mjt@tls.msk.ru> wrote:

> From: Michael Tokarev <mjt@tls.msk.ru>
> Subject: Re: CF Card Adapter White List Candidate
> To: "Robert Hancock" <hancockrwd@gmail.com>
> Cc: "Tom Denchfield" <td_denchfield@yahoo.com>, "Tejun Heo" <htejun@gmail.com>, linux-ide@vger.kernel.org
> Date: Saturday, January 8, 2011, 4:48 AM
> 07.01.2011 07:22, Robert Hancock
> wrote:
> > On Wed, Jan 5, 2011 at 11:33 PM, Tom Denchfield <td_denchfield@yahoo.com>
> wrote:
> >> The reason that I mentioned powering my CF adapter
> with a floppy drive power plug is that the first time I
> booted after inserting the adapter, I forgot to plug the
> floppy drive power plug into the adapter.  The
> adapter's power on LED did not light, and I think that
> Ubuntu did not see the CF card.
> >>
> >> The reason that I mentioned the pin that was
> intentionally left out of the motherboard IDE socket was
> that I thought that the missing pin might have had something
> to do with needing to power the adapter with the floppy
> drive power plug given my experience with forgetting to plug
> the floppy power plug into the adapter as mentioned in the
> previous paragraph.
> >>
> >> The pin that is missing from the motherboard IDE
> socket is very close to the middle of the IDE socket. 
> My guess is that the pin is in the in the range #18 to
> #24.  It is far away from pin #34.  I am going by
> memory here, but I clearly remember that the missing pin is
> in the middle.  Pin #34 is going into the CF card
> adapter when I insert it.  I do not know whether pin
> #34 is grounded at the mainboard.
> > 
> > If it's pin 20, that's a key pin that's always missing
> and which has
> > the corresponding hole filled in on the cable side
> (from compliant
> > connectors, anyway), to prevent plugging in the cable
> the wrong way
> > around.
> > 
> > Not sure where the adapter would be potentially
> drawing power from on
> > the IDE connector - as far as I know there aren't any
> pins on a
> > standard IDE connector which provide continuous power.
> The adapters
> > I've seen all use an extra power connector.
> 
> The 20th pin is actually used on some VIA EPIA (mini-itx)
> motherboards,
> exactly for this purpose: to provide power for CF cards
> like this.
> Some IDE to CF adaptors can be set up (with a jumper) to
> ger power
> to the card from there.
> 
> /mjt
> 


      

Re: CF Card Adapter White List Candidate

[Robert Hancock]

On Fri, Jan 7, 2011 at 10:51 AM, Tom Denchfield <td_denchfield@yahoo.com> wrote:
> Robert, yes, the IDE socket missing pin was # 20, the Key needed for 80-conductor IDE cables, as you stated below.  I had to take the adapter out so I carefully looked at it and compared it to a photograph on a pin-out Internet site.
>
> I also looked at an enlarged photo of the laptop CF card adapter pictured in URL03, and counted 44 pins - at least counting from the bottom of the socket.
>
> I notice that the dmesg output in my Wednesday, January 5, 2011 11:33 PM email to you guys has been removed from you response below.  I realize that you need to keep emails shorter than those that I write, but I think that the dmesg demonstrates that my particular CF card adapter is indeed capable of being forced (libata.force=80c) to UDMA/66 even though it is not (economically) feasible to insert a 80-wire IDE cable between the CF card adapter and the IDE socket on a desktop computer's motherboard.

Yes, in this case there's likely no issue with using speeds faster
than UDMA33. However, problem is that since these kind of adapters are
essentially passive devices, there's no way for the kernel to detect
them automatically. In this sort of case, the libata.force option is
likely the best one.

>
> Robert, again thank you for helping me, and I hope that I may have contributed at least a little bit of useful information.
>
> Tom
>
>
> --- On Thu, 1/6/11, Robert Hancock <hancockrwd@gmail.com> wrote:
>
>> From: Robert Hancock <hancockrwd@gmail.com>
>> Subject: Re: CF Card Adapter White List Candidate
>> To: "Tom Denchfield" <td_denchfield@yahoo.com>
>> Cc: "Tejun Heo" <htejun@gmail.com>, linux-ide@vger.kernel.org
>> Date: Thursday, January 6, 2011, 10:22 PM
>> On Wed, Jan 5, 2011 at 11:33 PM, Tom
>> Denchfield <td_denchfield@yahoo.com>
>> wrote:
>> > The reason that I mentioned powering my CF adapter
>> with a floppy drive power plug is that the first time I
>> booted after inserting the adapter, I forgot to plug the
>> floppy drive power plug into the adapter.  The adapter's
>> power on LED did not light, and I think that Ubuntu did not
>> see the CF card.
>> >
>> > The reason that I mentioned the pin that was
>> intentionally left out of the motherboard IDE socket was
>> that I thought that the missing pin might have had something
>> to do with needing to power the adapter with the floppy
>> drive power plug given my experience with forgetting to plug
>> the floppy power plug into the adapter as mentioned in the
>> previous paragraph.
>> >
>> > The pin that is missing from the motherboard IDE
>> socket is very close to the middle of the IDE socket.  My
>> guess is that the pin is in the in the range #18 to #24.
>> It is far away from pin #34.  I am going by memory here,
>> but I clearly remember that the missing pin is in the
>> middle.  Pin #34 is going into the CF card adapter when I
>> insert it.  I do not know whether pin #34 is grounded at
>> the mainboard.
>>
>> If it's pin 20, that's a key pin that's always missing and
>> which has
>> the corresponding hole filled in on the cable side (from
>> compliant
>> connectors, anyway), to prevent plugging in the cable the
>> wrong way
>> around.
>>
>> Not sure where the adapter would be potentially drawing
>> power from on
>> the IDE connector - as far as I know there aren't any pins
>> on a
>> standard IDE connector which provide continuous power. The
>> adapters
>> I've seen all use an extra power connector.
>>
>> >
>> > When I asked my question, before I noticed and paid
>> any real attention to the UDMA/100 CF card configured as
>> UDMA/100 in URL03 above, I was concerned that there might be
>> a UDMA/66 speed limit with the type of CF card adapter that
>> I have.  We may never know for sure until someone who has a
>> CF card that is faster than UDMA/66 tries it in the URL01
>> adapter with Linux and the libata.force=80c boot parameter.
>> >
>> > Robert, thank you for helping me.  I hope that my
>> additional comments and the information above will
>> contribute to further Linux kernel development.
>> >
>> > Tom
>> >
>> > --- On Wed, 1/5/11, Robert Hancock <hancockrwd@gmail.com>
>> wrote:
>> >
>> >> From: Robert Hancock <hancockrwd@gmail.com>
>> >> Subject: Re: CF Card Adapter White List Candidate
>> >> To: "Tom Denchfield" <td_denchfield@yahoo.com>
>> >> Cc: "Tejun Heo" <htejun@gmail.com>,
>> linux-ide@vger.kernel.org
>> >> Date: Wednesday, January 5, 2011, 5:47 PM
>> >> On Wed, Jan 5, 2011 at 12:18 PM, Tom
>> >> Denchfield <td_denchfield@yahoo.com>
>> >> wrote:
>> >> > Hello,
>> >> >
>> >> > Tejun, this CF card adapter plugs directly
>> into an IDE
>> >> socket (Channel 0, in my case) on a desktop
>> computer
>> >> motherboard.  You can see a picture of the
>> adapter in the
>> >> following URL01:
>> >> >
>> >> > URL01: http://preview.tinyurl.com/233u92u
>> >> >
>> >> > I have to power the adapter with a floppy
>> drive power
>> >> plug because my motherboard's IDE sockets were
>> intentionally
>> >> manufactured without the pin that could have
>> supplied power
>> >> through an IDE cable.
>> >> >
>> >> > Does anyone have a top of the head opinion as
>> to
>> >> whether there are inherent usage limitations in
>> either this
>> >> passive CF card adapter and/or in the Linux kernel
>> used with
>> >> Ubuntu v10.10 that would prevent users with CF
>> cards faster
>> >> than UDMA/66 (see URL02 below) from being
>> configured by
>> >> Linux to work at speeds above UDMA/66?  The
>> reason that I
>> >> ask this question is that I bought both my UDMA/66
>> CF card
>> >> and the adapter from the URL01 seller.  It is
>> foreseeable
>> >> that a lot of customers might have purchased
>> faster CF cards
>> >> envisioning that they would work at speeds higher
>> than
>> >> UDMA/66 with the adapter.  The 'Technical
>> Details' section
>> >> of URL01 does not state anything about UDMA speed
>> usage
>> >> limitations.
>> >> >
>> >> > URL02: http://www.hjreggel.net/cardspeed/index.html
>> >> >
>> >> > I think that there are CF card adapters on
>> eBay that
>> >> are similar to the one pictured in URL01 above,
>> and there
>> >> are also IDE adapters that will hold two CF
>> cards.
>> >>
>> >> The reason the speed is being limited to 33 is
>> that the
>> >> cable
>> >> detection code is detecting that an 80-wire cable
>> doesn't
>> >> appear to be
>> >> connected. In order for an 80-wire cable to be
>> detected,
>> >> pin 34 on the
>> >> cable is supposed to be grounded at the
>> motherboard end. In
>> >> the case
>> >> of this adapter, since it plugs directly into the
>> >> motherboard, it
>> >> would have to be grounding pin 34 to get an
>> 80-wire
>> >> detection, but
>> >> presumably it's not.
>> >>
>> >> >
>> >> > Tom
>> >> >
>> >> > --- On Wed, 1/5/11, Tejun Heo <htejun@gmail.com>
>> >> wrote:
>> >> >
>> >> >> From: Tejun Heo <htejun@gmail.com>
>> >> >> Subject: Re: CF Card Adapter White List
>> Candidate
>> >> >> To: "Robert Hancock" <hancockrwd@gmail.com>
>> >> >> Cc: "Tom Denchfield" <td_denchfield@yahoo.com>,
>> >> linux-ide@vger.kernel.org
>> >> >> Date: Wednesday, January 5, 2011, 5:51
>> AM
>> >> >> Hello,
>> >> >>
>> >> >> On Tue, Jan 04, 2011 at 10:19:17PM -0600,
>> Robert
>> >> Hancock
>> >> >> wrote:
>> >> >> > On 01/04/2011 04:18 PM, Tom
>> Denchfield
>> >> wrote:
>> >> >> >> As you further recommended, in
>> an attempt
>> >> to get
>> >> >> the SD-CF-IDE-DI
>> >> >> >> IDE to CF Adapter that holds my
>> CF card
>> >> white
>> >> >> listed, I am
>> >> >> >> submitting the attached
>> >> >> >>
>> >> >>
>> >>
>> libata_force_80c_CF_card_adapter_whitelist_candidate_information.txt
>> >> >> >> file that has the output from
>> executing
>> >> four
>> >> >> terminal commands to
>> >> >> >> hopefully supply enough
>> information to
>> >> get it
>> >> >> whitelisted.
>> >> >>
>> >> >> Thanks.
>> >> >>
>> >> >> >> Although I expect that my RV280
>> Radeon
>> >> 9200 Pro
>> >> >> video card is too
>> >> >> >> old to expend much effort on, it
>> would be
>> >> nice to
>> >> >> also get it
>> >> >> >> whitelisted so that future
>> newbie Linux
>> >> users who
>> >> >> do not know about
>> >> >> >> using the radeon.modeset=0
>> parameter on
>> >> the kernel
>> >> >> command line
>> >> >> >> will not be looking at a black
>> screen
>> >> with a
>> >> >> blinking cursor when
>> >> >> >> they attempt to use a LiveCD
>> for
>> >> troubleshooting,
>> >> >> or whatever.
>> >> >> >>
>> >> >> >> I purposely did not include the
>> URL of
>> >> one of the
>> >> >> Internet sites
>> >> >> >> that sells the adapter in this
>> email in
>> >> case this
>> >> >> is a no no.
>> >> >>
>> >> >> I don't think that's a no no unless the
>> intention
>> >> is
>> >> >> commercial.
>> >> >>
>> >> >> >> Tejun, I am not sure that I will
>> have
>> >> either the
>> >> >> time or the
>> >> >> >> interest to learn the
>> intricacies of
>> >> editing
>> >> >> >> http://www.thinkwiki.org/wiki/Compact_Flash_boot_drive
>> >> >> to add
>> >> >> >> libata.force=80c to this site in
>> lieu of
>> >> >> force_cbl=80: so that
>> >> >> >> fewer people will be asking you
>> >> questions.  I
>> >> >> have a ThinkPad
>> >> >> >> without a HDD plus a laptop
>> adapter that
>> >> will hold
>> >> >> my CF card, but
>> >> >> >> my Think Pad is a lot older than
>> the
>> >> ones
>> >> >> discussed on
>> >> >> >> Compact_Flash_boot_drive.  In
>> addition,
>> >> I did
>> >> >> not see any recent
>> >> >> >> updates to this Internet page,
>> but maybe
>> >> I can
>> >> >> find someone to
>> >> >> >> email who will update this
>> page.
>> >> >>
>> >> >> Yeah, just ping someone.
>> >> >>
>> >> >> > Is there actually any way to
>> identify the
>> >> adapter
>> >> >> automatically?
>> >> >> > AFAIK, these CF-IDE adapters are
>> just
>> >> passive
>> >> >> circuitry and there's
>> >> >> > no way to identify them through
>> software.
>> >> >>
>> >> >> Hmmm... I was thinking this was somehing
>> >> integrated to the
>> >> >> machine (so
>> >> >> the dmidecode), in which case we can
>> combine dmi +
>> >> pci
>> >> >> function # +
>> >> >> port # to whitelist the device, which we
>> already
>> >> do for
>> >> >> some type of
>> >> >> quirks.  If it's a plug in device, we
>> obviously
>> >> can't
>> >> >> identify it.
>> >> >> Tom, is the CF slot integrated to the
>> machine or
>> >> is it
>> >> >> something you
>> >> >> put into the PCMCIA slot?
>> >> >>
>> >> >> Thanks.
>> >> >>
>> >> >> --
>> >> >> tejun
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> >
>> >>
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>
>
>
>
>

Re: CF Card Adapter White List Candidate

[Michael Tokarev]

07.01.2011 07:22, Robert Hancock wrote:
> On Wed, Jan 5, 2011 at 11:33 PM, Tom Denchfield <td_denchfield@yahoo.com> wrote:
>> The reason that I mentioned powering my CF adapter with a floppy drive power plug is that the first time I booted after inserting the adapter, I forgot to plug the floppy drive power plug into the adapter.  The adapter's power on LED did not light, and I think that Ubuntu did not see the CF card.
>>
>> The reason that I mentioned the pin that was intentionally left out of the motherboard IDE socket was that I thought that the missing pin might have had something to do with needing to power the adapter with the floppy drive power plug given my experience with forgetting to plug the floppy power plug into the adapter as mentioned in the previous paragraph.
>>
>> The pin that is missing from the motherboard IDE socket is very close to the middle of the IDE socket.  My guess is that the pin is in the in the range #18 to #24.  It is far away from pin #34.  I am going by memory here, but I clearly remember that the missing pin is in the middle.  Pin #34 is going into the CF card adapter when I insert it.  I do not know whether pin #34 is grounded at the mainboard.
> 
> If it's pin 20, that's a key pin that's always missing and which has
> the corresponding hole filled in on the cable side (from compliant
> connectors, anyway), to prevent plugging in the cable the wrong way
> around.
> 
> Not sure where the adapter would be potentially drawing power from on
> the IDE connector - as far as I know there aren't any pins on a
> standard IDE connector which provide continuous power. The adapters
> I've seen all use an extra power connector.

The 20th pin is actually used on some VIA EPIA (mini-itx) motherboards,
exactly for this purpose: to provide power for CF cards like this.
Some IDE to CF adaptors can be set up (with a jumper) to ger power
to the card from there.

/mjt

Re: CF Card Adapter White List Candidate

[Tom Denchfield]

Robert, yes, the IDE socket missing pin was # 20, the Key needed for 80-conductor IDE cables, as you stated below.  I had to take the adapter out so I carefully looked at it and compared it to a photograph on a pin-out Internet site.

I also looked at an enlarged photo of the laptop CF card adapter pictured in URL03, and counted 44 pins - at least counting from the bottom of the socket.

I notice that the dmesg output in my Wednesday, January 5, 2011 11:33 PM email to you guys has been removed from you response below.  I realize that you need to keep emails shorter than those that I write, but I think that the dmesg demonstrates that my particular CF card adapter is indeed capable of being forced (libata.force=80c) to UDMA/66 even though it is not (economically) feasible to insert a 80-wire IDE cable between the CF card adapter and the IDE socket on a desktop computer's motherboard.

Robert, again thank you for helping me, and I hope that I may have contributed at least a little bit of useful information.

Tom


--- On Thu, 1/6/11, Robert Hancock <hancockrwd@gmail.com> wrote:

> From: Robert Hancock <hancockrwd@gmail.com>
> Subject: Re: CF Card Adapter White List Candidate
> To: "Tom Denchfield" <td_denchfield@yahoo.com>
> Cc: "Tejun Heo" <htejun@gmail.com>, linux-ide@vger.kernel.org
> Date: Thursday, January 6, 2011, 10:22 PM
> On Wed, Jan 5, 2011 at 11:33 PM, Tom
> Denchfield <td_denchfield@yahoo.com>
> wrote:
> > The reason that I mentioned powering my CF adapter
> with a floppy drive power plug is that the first time I
> booted after inserting the adapter, I forgot to plug the
> floppy drive power plug into the adapter.  The adapter's
> power on LED did not light, and I think that Ubuntu did not
> see the CF card.
> >
> > The reason that I mentioned the pin that was
> intentionally left out of the motherboard IDE socket was
> that I thought that the missing pin might have had something
> to do with needing to power the adapter with the floppy
> drive power plug given my experience with forgetting to plug
> the floppy power plug into the adapter as mentioned in the
> previous paragraph.
> >
> > The pin that is missing from the motherboard IDE
> socket is very close to the middle of the IDE socket.  My
> guess is that the pin is in the in the range #18 to #24. 
> It is far away from pin #34.  I am going by memory here,
> but I clearly remember that the missing pin is in the
> middle.  Pin #34 is going into the CF card adapter when I
> insert it.  I do not know whether pin #34 is grounded at
> the mainboard.
> 
> If it's pin 20, that's a key pin that's always missing and
> which has
> the corresponding hole filled in on the cable side (from
> compliant
> connectors, anyway), to prevent plugging in the cable the
> wrong way
> around.
> 
> Not sure where the adapter would be potentially drawing
> power from on
> the IDE connector - as far as I know there aren't any pins
> on a
> standard IDE connector which provide continuous power. The
> adapters
> I've seen all use an extra power connector.
> 
> >
> > When I asked my question, before I noticed and paid
> any real attention to the UDMA/100 CF card configured as
> UDMA/100 in URL03 above, I was concerned that there might be
> a UDMA/66 speed limit with the type of CF card adapter that
> I have.  We may never know for sure until someone who has a
> CF card that is faster than UDMA/66 tries it in the URL01
> adapter with Linux and the libata.force=80c boot parameter.
> >
> > Robert, thank you for helping me.  I hope that my
> additional comments and the information above will
> contribute to further Linux kernel development.
> >
> > Tom
> >
> > --- On Wed, 1/5/11, Robert Hancock <hancockrwd@gmail.com>
> wrote:
> >
> >> From: Robert Hancock <hancockrwd@gmail.com>
> >> Subject: Re: CF Card Adapter White List Candidate
> >> To: "Tom Denchfield" <td_denchfield@yahoo.com>
> >> Cc: "Tejun Heo" <htejun@gmail.com>,
> linux-ide@vger.kernel.org
> >> Date: Wednesday, January 5, 2011, 5:47 PM
> >> On Wed, Jan 5, 2011 at 12:18 PM, Tom
> >> Denchfield <td_denchfield@yahoo.com>
> >> wrote:
> >> > Hello,
> >> >
> >> > Tejun, this CF card adapter plugs directly
> into an IDE
> >> socket (Channel 0, in my case) on a desktop
> computer
> >> motherboard.  You can see a picture of the
> adapter in the
> >> following URL01:
> >> >
> >> > URL01: http://preview.tinyurl.com/233u92u
> >> >
> >> > I have to power the adapter with a floppy
> drive power
> >> plug because my motherboard's IDE sockets were
> intentionally
> >> manufactured without the pin that could have
> supplied power
> >> through an IDE cable.
> >> >
> >> > Does anyone have a top of the head opinion as
> to
> >> whether there are inherent usage limitations in
> either this
> >> passive CF card adapter and/or in the Linux kernel
> used with
> >> Ubuntu v10.10 that would prevent users with CF
> cards faster
> >> than UDMA/66 (see URL02 below) from being
> configured by
> >> Linux to work at speeds above UDMA/66?  The
> reason that I
> >> ask this question is that I bought both my UDMA/66
> CF card
> >> and the adapter from the URL01 seller.  It is
> foreseeable
> >> that a lot of customers might have purchased
> faster CF cards
> >> envisioning that they would work at speeds higher
> than
> >> UDMA/66 with the adapter.  The 'Technical
> Details' section
> >> of URL01 does not state anything about UDMA speed
> usage
> >> limitations.
> >> >
> >> > URL02: http://www.hjreggel.net/cardspeed/index.html
> >> >
> >> > I think that there are CF card adapters on
> eBay that
> >> are similar to the one pictured in URL01 above,
> and there
> >> are also IDE adapters that will hold two CF
> cards.
> >>
> >> The reason the speed is being limited to 33 is
> that the
> >> cable
> >> detection code is detecting that an 80-wire cable
> doesn't
> >> appear to be
> >> connected. In order for an 80-wire cable to be
> detected,
> >> pin 34 on the
> >> cable is supposed to be grounded at the
> motherboard end. In
> >> the case
> >> of this adapter, since it plugs directly into the
> >> motherboard, it
> >> would have to be grounding pin 34 to get an
> 80-wire
> >> detection, but
> >> presumably it's not.
> >>
> >> >
> >> > Tom
> >> >
> >> > --- On Wed, 1/5/11, Tejun Heo <htejun@gmail.com>
> >> wrote:
> >> >
> >> >> From: Tejun Heo <htejun@gmail.com>
> >> >> Subject: Re: CF Card Adapter White List
> Candidate
> >> >> To: "Robert Hancock" <hancockrwd@gmail.com>
> >> >> Cc: "Tom Denchfield" <td_denchfield@yahoo.com>,
> >> linux-ide@vger.kernel.org
> >> >> Date: Wednesday, January 5, 2011, 5:51
> AM
> >> >> Hello,
> >> >>
> >> >> On Tue, Jan 04, 2011 at 10:19:17PM -0600,
> Robert
> >> Hancock
> >> >> wrote:
> >> >> > On 01/04/2011 04:18 PM, Tom
> Denchfield
> >> wrote:
> >> >> >> As you further recommended, in
> an attempt
> >> to get
> >> >> the SD-CF-IDE-DI
> >> >> >> IDE to CF Adapter that holds my
> CF card
> >> white
> >> >> listed, I am
> >> >> >> submitting the attached
> >> >> >>
> >> >>
> >>
> libata_force_80c_CF_card_adapter_whitelist_candidate_information.txt
> >> >> >> file that has the output from
> executing
> >> four
> >> >> terminal commands to
> >> >> >> hopefully supply enough
> information to
> >> get it
> >> >> whitelisted.
> >> >>
> >> >> Thanks.
> >> >>
> >> >> >> Although I expect that my RV280
> Radeon
> >> 9200 Pro
> >> >> video card is too
> >> >> >> old to expend much effort on, it
> would be
> >> nice to
> >> >> also get it
> >> >> >> whitelisted so that future
> newbie Linux
> >> users who
> >> >> do not know about
> >> >> >> using the radeon.modeset=0
> parameter on
> >> the kernel
> >> >> command line
> >> >> >> will not be looking at a black
> screen
> >> with a
> >> >> blinking cursor when
> >> >> >> they attempt to use a LiveCD
> for
> >> troubleshooting,
> >> >> or whatever.
> >> >> >>
> >> >> >> I purposely did not include the
> URL of
> >> one of the
> >> >> Internet sites
> >> >> >> that sells the adapter in this
> email in
> >> case this
> >> >> is a no no.
> >> >>
> >> >> I don't think that's a no no unless the
> intention
> >> is
> >> >> commercial.
> >> >>
> >> >> >> Tejun, I am not sure that I will
> have
> >> either the
> >> >> time or the
> >> >> >> interest to learn the
> intricacies of
> >> editing
> >> >> >> http://www.thinkwiki.org/wiki/Compact_Flash_boot_drive
> >> >> to add
> >> >> >> libata.force=80c to this site in
> lieu of
> >> >> force_cbl=80: so that
> >> >> >> fewer people will be asking you
> >> questions.  I
> >> >> have a ThinkPad
> >> >> >> without a HDD plus a laptop
> adapter that
> >> will hold
> >> >> my CF card, but
> >> >> >> my Think Pad is a lot older than
> the
> >> ones
> >> >> discussed on
> >> >> >> Compact_Flash_boot_drive.  In
> addition,
> >> I did
> >> >> not see any recent
> >> >> >> updates to this Internet page,
> but maybe
> >> I can
> >> >> find someone to
> >> >> >> email who will update this
> page.
> >> >>
> >> >> Yeah, just ping someone.
> >> >>
> >> >> > Is there actually any way to
> identify the
> >> adapter
> >> >> automatically?
> >> >> > AFAIK, these CF-IDE adapters are
> just
> >> passive
> >> >> circuitry and there's
> >> >> > no way to identify them through
> software.
> >> >>
> >> >> Hmmm... I was thinking this was somehing
> >> integrated to the
> >> >> machine (so
> >> >> the dmidecode), in which case we can
> combine dmi +
> >> pci
> >> >> function # +
> >> >> port # to whitelist the device, which we
> already
> >> do for
> >> >> some type of
> >> >> quirks.  If it's a plug in device, we
> obviously
> >> can't
> >> >> identify it.
> >> >> Tom, is the CF slot integrated to the
> machine or
> >> is it
> >> >> something you
> >> >> put into the PCMCIA slot?
> >> >>
> >> >> Thanks.
> >> >>
> >> >> --
> >> >> tejun
> >> >>
> >> >
> >> >
> >> >
> >> >
> >>
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>



      

Re: CF Card Adapter White List Candidate

[Robert Hancock]

On Wed, Jan 5, 2011 at 11:33 PM, Tom Denchfield <td_denchfield@yahoo.com> wrote:
> The reason that I mentioned powering my CF adapter with a floppy drive power plug is that the first time I booted after inserting the adapter, I forgot to plug the floppy drive power plug into the adapter.  The adapter's power on LED did not light, and I think that Ubuntu did not see the CF card.
>
> The reason that I mentioned the pin that was intentionally left out of the motherboard IDE socket was that I thought that the missing pin might have had something to do with needing to power the adapter with the floppy drive power plug given my experience with forgetting to plug the floppy power plug into the adapter as mentioned in the previous paragraph.
>
> The pin that is missing from the motherboard IDE socket is very close to the middle of the IDE socket.  My guess is that the pin is in the in the range #18 to #24.  It is far away from pin #34.  I am going by memory here, but I clearly remember that the missing pin is in the middle.  Pin #34 is going into the CF card adapter when I insert it.  I do not know whether pin #34 is grounded at the mainboard.

If it's pin 20, that's a key pin that's always missing and which has
the corresponding hole filled in on the cable side (from compliant
connectors, anyway), to prevent plugging in the cable the wrong way
around.

Not sure where the adapter would be potentially drawing power from on
the IDE connector - as far as I know there aren't any pins on a
standard IDE connector which provide continuous power. The adapters
I've seen all use an extra power connector.

>
> When I asked my question, before I noticed and paid any real attention to the UDMA/100 CF card configured as UDMA/100 in URL03 above, I was concerned that there might be a UDMA/66 speed limit with the type of CF card adapter that I have.  We may never know for sure until someone who has a CF card that is faster than UDMA/66 tries it in the URL01 adapter with Linux and the libata.force=80c boot parameter.
>
> Robert, thank you for helping me.  I hope that my additional comments and the information above will contribute to further Linux kernel development.
>
> Tom
>
> --- On Wed, 1/5/11, Robert Hancock <hancockrwd@gmail.com> wrote:
>
>> From: Robert Hancock <hancockrwd@gmail.com>
>> Subject: Re: CF Card Adapter White List Candidate
>> To: "Tom Denchfield" <td_denchfield@yahoo.com>
>> Cc: "Tejun Heo" <htejun@gmail.com>, linux-ide@vger.kernel.org
>> Date: Wednesday, January 5, 2011, 5:47 PM
>> On Wed, Jan 5, 2011 at 12:18 PM, Tom
>> Denchfield <td_denchfield@yahoo.com>
>> wrote:
>> > Hello,
>> >
>> > Tejun, this CF card adapter plugs directly into an IDE
>> socket (Channel 0, in my case) on a desktop computer
>> motherboard.  You can see a picture of the adapter in the
>> following URL01:
>> >
>> > URL01: http://preview.tinyurl.com/233u92u
>> >
>> > I have to power the adapter with a floppy drive power
>> plug because my motherboard's IDE sockets were intentionally
>> manufactured without the pin that could have supplied power
>> through an IDE cable.
>> >
>> > Does anyone have a top of the head opinion as to
>> whether there are inherent usage limitations in either this
>> passive CF card adapter and/or in the Linux kernel used with
>> Ubuntu v10.10 that would prevent users with CF cards faster
>> than UDMA/66 (see URL02 below) from being configured by
>> Linux to work at speeds above UDMA/66?  The reason that I
>> ask this question is that I bought both my UDMA/66 CF card
>> and the adapter from the URL01 seller.  It is foreseeable
>> that a lot of customers might have purchased faster CF cards
>> envisioning that they would work at speeds higher than
>> UDMA/66 with the adapter.  The 'Technical Details' section
>> of URL01 does not state anything about UDMA speed usage
>> limitations.
>> >
>> > URL02: http://www.hjreggel.net/cardspeed/index.html
>> >
>> > I think that there are CF card adapters on eBay that
>> are similar to the one pictured in URL01 above, and there
>> are also IDE adapters that will hold two CF cards.
>>
>> The reason the speed is being limited to 33 is that the
>> cable
>> detection code is detecting that an 80-wire cable doesn't
>> appear to be
>> connected. In order for an 80-wire cable to be detected,
>> pin 34 on the
>> cable is supposed to be grounded at the motherboard end. In
>> the case
>> of this adapter, since it plugs directly into the
>> motherboard, it
>> would have to be grounding pin 34 to get an 80-wire
>> detection, but
>> presumably it's not.
>>
>> >
>> > Tom
>> >
>> > --- On Wed, 1/5/11, Tejun Heo <htejun@gmail.com>
>> wrote:
>> >
>> >> From: Tejun Heo <htejun@gmail.com>
>> >> Subject: Re: CF Card Adapter White List Candidate
>> >> To: "Robert Hancock" <hancockrwd@gmail.com>
>> >> Cc: "Tom Denchfield" <td_denchfield@yahoo.com>,
>> linux-ide@vger.kernel.org
>> >> Date: Wednesday, January 5, 2011, 5:51 AM
>> >> Hello,
>> >>
>> >> On Tue, Jan 04, 2011 at 10:19:17PM -0600, Robert
>> Hancock
>> >> wrote:
>> >> > On 01/04/2011 04:18 PM, Tom Denchfield
>> wrote:
>> >> >> As you further recommended, in an attempt
>> to get
>> >> the SD-CF-IDE-DI
>> >> >> IDE to CF Adapter that holds my CF card
>> white
>> >> listed, I am
>> >> >> submitting the attached
>> >> >>
>> >>
>> libata_force_80c_CF_card_adapter_whitelist_candidate_information.txt
>> >> >> file that has the output from executing
>> four
>> >> terminal commands to
>> >> >> hopefully supply enough information to
>> get it
>> >> whitelisted.
>> >>
>> >> Thanks.
>> >>
>> >> >> Although I expect that my RV280 Radeon
>> 9200 Pro
>> >> video card is too
>> >> >> old to expend much effort on, it would be
>> nice to
>> >> also get it
>> >> >> whitelisted so that future newbie Linux
>> users who
>> >> do not know about
>> >> >> using the radeon.modeset=0 parameter on
>> the kernel
>> >> command line
>> >> >> will not be looking at a black screen
>> with a
>> >> blinking cursor when
>> >> >> they attempt to use a LiveCD for
>> troubleshooting,
>> >> or whatever.
>> >> >>
>> >> >> I purposely did not include the URL of
>> one of the
>> >> Internet sites
>> >> >> that sells the adapter in this email in
>> case this
>> >> is a no no.
>> >>
>> >> I don't think that's a no no unless the intention
>> is
>> >> commercial.
>> >>
>> >> >> Tejun, I am not sure that I will have
>> either the
>> >> time or the
>> >> >> interest to learn the intricacies of
>> editing
>> >> >> http://www.thinkwiki.org/wiki/Compact_Flash_boot_drive
>> >> to add
>> >> >> libata.force=80c to this site in lieu of
>> >> force_cbl=80: so that
>> >> >> fewer people will be asking you
>> questions.  I
>> >> have a ThinkPad
>> >> >> without a HDD plus a laptop adapter that
>> will hold
>> >> my CF card, but
>> >> >> my Think Pad is a lot older than the
>> ones
>> >> discussed on
>> >> >> Compact_Flash_boot_drive.  In addition,
>> I did
>> >> not see any recent
>> >> >> updates to this Internet page, but maybe
>> I can
>> >> find someone to
>> >> >> email who will update this page.
>> >>
>> >> Yeah, just ping someone.
>> >>
>> >> > Is there actually any way to identify the
>> adapter
>> >> automatically?
>> >> > AFAIK, these CF-IDE adapters are just
>> passive
>> >> circuitry and there's
>> >> > no way to identify them through software.
>> >>
>> >> Hmmm... I was thinking this was somehing
>> integrated to the
>> >> machine (so
>> >> the dmidecode), in which case we can combine dmi +
>> pci
>> >> function # +
>> >> port # to whitelist the device, which we already
>> do for
>> >> some type of
>> >> quirks.  If it's a plug in device, we obviously
>> can't
>> >> identify it.
>> >> Tom, is the CF slot integrated to the machine or
>> is it
>> >> something you
>> >> put into the PCMCIA slot?
>> >>
>> >> Thanks.
>> >>
>> >> --
>> >> tejun
>> >>
>> >
>> >
>> >
>> >
>>
>
>
>
>
>
>
>
>
>
>
>

Re: CF Card Adapter White List Candidate

[Tom Denchfield]

Hello,

Robert, it looks like I may have found an answer to my UDMA speed question (see below) that I asked earlier today.  URL03 below has a picture (top-right) of an Addonics Dual CF-IDE HDD Adapter that looks to me like it can be connected to a motherboard IDE socket via a 80-wire IDE cable.  (This adapter's IDE socket is not shown in the picture.  On second thought, maybe this device does not have a 40-pin IDE socket since the article is about laptop computers.)  The article says to use a (now) outdated patch, even with, I would guess, an 80-conductor IDE cable, to 'force 80c.'  With the outdated patch, URL03 has a dmesg excerpt in a table that shows a UDMA/100 CF card being configured by Linux as a UDMA/100 device.
 
Title: Compact Flash boot drive
URL03: http://www.thinkwiki.org/wiki/Compact_Flash_boot_drive

With my plug-in IDE adapter (pictured in URL01 below) that is plugged directly into a desktop computer's motherboard IDE socket, my UDMA/66 CF Card is configured by the Linux version 2.6.35-22-generic kernel that is used by the Ubuntu v10.10 LiveCD that I use, as a UDMA/33 device.  However, if I add libata.force=80c as a boot parameter, as recommended by Tejun, Linux configures my CF card as a UDMA/66 device.

(In the first email that I sent to linux-ide@vger.kernel.org, I attached a dmesg demonstrating that the added boot parameter produced the UDMA/66 configuration.  I attached two text files that I think totaled about 65KB, and maybe linux-ide@vger.kernel.org strips files of this size from emails.  I also do not expect anyone to remember that far back when answering my questions.)

I do not know whether the following dmesg is the one that I originally sent, but it is typical of what happens with the liabat.forec=80c parameter:

[    0.000000] Kernel command line: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz radeon.modeset=0 libata.force=80c toram --
.
[    5.088368] ata3: FORCE: cable set to 80c
[    5.088452] ata3.00: CFA: TS8GCF133, 20100804, max UDMA/66
[    5.088509] ata3.00: 15662304 sectors, multi 0: LBA 
[    5.104301] ata3.00: configured for UDMA/66
.
[    5.564449] scsi 2:0:0:0: Direct-Access     ATA      TS8GCF133        2010 PQ: 0 ANSI: 5
[    5.564819] sd 2:0:0:0: Attached scsi generic sg1 type 0
[    5.565631] sd 2:0:0:0: [sdb] 15662304 512-byte logical blocks: (8.01 GB/7.46 GiB)

The reason that I mentioned powering my CF adapter with a floppy drive power plug is that the first time I booted after inserting the adapter, I forgot to plug the floppy drive power plug into the adapter.  The adapter's power on LED did not light, and I think that Ubuntu did not see the CF card.

The reason that I mentioned the pin that was intentionally left out of the motherboard IDE socket was that I thought that the missing pin might have had something to do with needing to power the adapter with the floppy drive power plug given my experience with forgetting to plug the floppy power plug into the adapter as mentioned in the previous paragraph.

The pin that is missing from the motherboard IDE socket is very close to the middle of the IDE socket.  My guess is that the pin is in the in the range #18 to #24.  It is far away from pin #34.  I am going by memory here, but I clearly remember that the missing pin is in the middle.  Pin #34 is going into the CF card adapter when I insert it.  I do not know whether pin #34 is grounded at the mainboard.

When I asked my question, before I noticed and paid any real attention to the UDMA/100 CF card configured as UDMA/100 in URL03 above, I was concerned that there might be a UDMA/66 speed limit with the type of CF card adapter that I have.  We may never know for sure until someone who has a CF card that is faster than UDMA/66 tries it in the URL01 adapter with Linux and the libata.force=80c boot parameter.

Robert, thank you for helping me.  I hope that my additional comments and the information above will contribute to further Linux kernel development.    

Tom

--- On Wed, 1/5/11, Robert Hancock <hancockrwd@gmail.com> wrote:

> From: Robert Hancock <hancockrwd@gmail.com>
> Subject: Re: CF Card Adapter White List Candidate
> To: "Tom Denchfield" <td_denchfield@yahoo.com>
> Cc: "Tejun Heo" <htejun@gmail.com>, linux-ide@vger.kernel.org
> Date: Wednesday, January 5, 2011, 5:47 PM
> On Wed, Jan 5, 2011 at 12:18 PM, Tom
> Denchfield <td_denchfield@yahoo.com>
> wrote:
> > Hello,
> >
> > Tejun, this CF card adapter plugs directly into an IDE
> socket (Channel 0, in my case) on a desktop computer
> motherboard.  You can see a picture of the adapter in the
> following URL01:
> >
> > URL01: http://preview.tinyurl.com/233u92u
> >
> > I have to power the adapter with a floppy drive power
> plug because my motherboard's IDE sockets were intentionally
> manufactured without the pin that could have supplied power
> through an IDE cable.
> >
> > Does anyone have a top of the head opinion as to
> whether there are inherent usage limitations in either this
> passive CF card adapter and/or in the Linux kernel used with
> Ubuntu v10.10 that would prevent users with CF cards faster
> than UDMA/66 (see URL02 below) from being configured by
> Linux to work at speeds above UDMA/66?  The reason that I
> ask this question is that I bought both my UDMA/66 CF card
> and the adapter from the URL01 seller.  It is foreseeable
> that a lot of customers might have purchased faster CF cards
> envisioning that they would work at speeds higher than
> UDMA/66 with the adapter.  The 'Technical Details' section
> of URL01 does not state anything about UDMA speed usage
> limitations.
> >
> > URL02: http://www.hjreggel.net/cardspeed/index.html
> >
> > I think that there are CF card adapters on eBay that
> are similar to the one pictured in URL01 above, and there
> are also IDE adapters that will hold two CF cards.
> 
> The reason the speed is being limited to 33 is that the
> cable
> detection code is detecting that an 80-wire cable doesn't
> appear to be
> connected. In order for an 80-wire cable to be detected,
> pin 34 on the
> cable is supposed to be grounded at the motherboard end. In
> the case
> of this adapter, since it plugs directly into the
> motherboard, it
> would have to be grounding pin 34 to get an 80-wire
> detection, but
> presumably it's not.
> 
> >
> > Tom
> >
> > --- On Wed, 1/5/11, Tejun Heo <htejun@gmail.com>
> wrote:
> >
> >> From: Tejun Heo <htejun@gmail.com>
> >> Subject: Re: CF Card Adapter White List Candidate
> >> To: "Robert Hancock" <hancockrwd@gmail.com>
> >> Cc: "Tom Denchfield" <td_denchfield@yahoo.com>,
> linux-ide@vger.kernel.org
> >> Date: Wednesday, January 5, 2011, 5:51 AM
> >> Hello,
> >>
> >> On Tue, Jan 04, 2011 at 10:19:17PM -0600, Robert
> Hancock
> >> wrote:
> >> > On 01/04/2011 04:18 PM, Tom Denchfield
> wrote:
> >> >> As you further recommended, in an attempt
> to get
> >> the SD-CF-IDE-DI
> >> >> IDE to CF Adapter that holds my CF card
> white
> >> listed, I am
> >> >> submitting the attached
> >> >>
> >>
> libata_force_80c_CF_card_adapter_whitelist_candidate_information.txt
> >> >> file that has the output from executing
> four
> >> terminal commands to
> >> >> hopefully supply enough information to
> get it
> >> whitelisted.
> >>
> >> Thanks.
> >>
> >> >> Although I expect that my RV280 Radeon
> 9200 Pro
> >> video card is too
> >> >> old to expend much effort on, it would be
> nice to
> >> also get it
> >> >> whitelisted so that future newbie Linux
> users who
> >> do not know about
> >> >> using the radeon.modeset=0 parameter on
> the kernel
> >> command line
> >> >> will not be looking at a black screen
> with a
> >> blinking cursor when
> >> >> they attempt to use a LiveCD for
> troubleshooting,
> >> or whatever.
> >> >>
> >> >> I purposely did not include the URL of
> one of the
> >> Internet sites
> >> >> that sells the adapter in this email in
> case this
> >> is a no no.
> >>
> >> I don't think that's a no no unless the intention
> is
> >> commercial.
> >>
> >> >> Tejun, I am not sure that I will have
> either the
> >> time or the
> >> >> interest to learn the intricacies of
> editing
> >> >> http://www.thinkwiki.org/wiki/Compact_Flash_boot_drive
> >> to add
> >> >> libata.force=80c to this site in lieu of
> >> force_cbl=80: so that
> >> >> fewer people will be asking you
> questions.  I
> >> have a ThinkPad
> >> >> without a HDD plus a laptop adapter that
> will hold
> >> my CF card, but
> >> >> my Think Pad is a lot older than the
> ones
> >> discussed on
> >> >> Compact_Flash_boot_drive.  In addition,
> I did
> >> not see any recent
> >> >> updates to this Internet page, but maybe
> I can
> >> find someone to
> >> >> email who will update this page.
> >>
> >> Yeah, just ping someone.
> >>
> >> > Is there actually any way to identify the
> adapter
> >> automatically?
> >> > AFAIK, these CF-IDE adapters are just
> passive
> >> circuitry and there's
> >> > no way to identify them through software.
> >>
> >> Hmmm... I was thinking this was somehing
> integrated to the
> >> machine (so
> >> the dmidecode), in which case we can combine dmi +
> pci
> >> function # +
> >> port # to whitelist the device, which we already
> do for
> >> some type of
> >> quirks.  If it's a plug in device, we obviously
> can't
> >> identify it.
> >> Tom, is the CF slot integrated to the machine or
> is it
> >> something you
> >> put into the PCMCIA slot?
> >>
> >> Thanks.
> >>
> >> --
> >> tejun
> >>
> >
> >
> >
> >
>









      

Re: CF Card Adapter White List Candidate

[Tejun Heo]

Hello,

On Tue, Jan 04, 2011 at 10:19:17PM -0600, Robert Hancock wrote:
> On 01/04/2011 04:18 PM, Tom Denchfield wrote:
>> As you further recommended, in an attempt to get the SD-CF-IDE-DI
>> IDE to CF Adapter that holds my CF card white listed, I am
>> submitting the attached
>> libata_force_80c_CF_card_adapter_whitelist_candidate_information.txt
>> file that has the output from executing four terminal commands to
>> hopefully supply enough information to get it whitelisted.

Thanks.

>> Although I expect that my RV280 Radeon 9200 Pro video card is too
>> old to expend much effort on, it would be nice to also get it
>> whitelisted so that future newbie Linux users who do not know about
>> using the radeon.modeset=0 parameter on the kernel command line
>> will not be looking at a black screen with a blinking cursor when
>> they attempt to use a LiveCD for troubleshooting, or whatever.
>>
>> I purposely did not include the URL of one of the Internet sites
>> that sells the adapter in this email in case this is a no no.

I don't think that's a no no unless the intention is commercial.

>> Tejun, I am not sure that I will have either the time or the
>> interest to learn the intricacies of editing
>> http://www.thinkwiki.org/wiki/Compact_Flash_boot_drive to add
>> libata.force=80c to this site in lieu of force_cbl=80: so that
>> fewer people will be asking you questions.  I have a ThinkPad
>> without a HDD plus a laptop adapter that will hold my CF card, but
>> my Think Pad is a lot older than the ones discussed on
>> Compact_Flash_boot_drive.  In addition, I did not see any recent
>> updates to this Internet page, but maybe I can find someone to
>> email who will update this page.

Yeah, just ping someone.

> Is there actually any way to identify the adapter automatically?
> AFAIK, these CF-IDE adapters are just passive circuitry and there's
> no way to identify them through software.

Hmmm... I was thinking this was somehing integrated to the machine (so
the dmidecode), in which case we can combine dmi + pci function # +
port # to whitelist the device, which we already do for some type of
quirks.  If it's a plug in device, we obviously can't identify it.
Tom, is the CF slot integrated to the machine or is it something you
put into the PCMCIA slot?

Thanks.

-- 
tejun

Re: CF Card Adapter White List Candidate

[Robert Hancock]

On 01/04/2011 04:18 PM, Tom Denchfield wrote:
> Tejun,
>
> Using your first recommendation in your 01/04/2010 email, I added libata.force=80c to the Ubuntu v10.10 Live CD (Live-CD) kernel command line, and this succeeded in getting Linux to configure my CompactFlash card as UDMA/66, as opposed to the UDMA/33 it had been using.  The attached dmesg_libata_force_80c.txt (dmesg) file shows the details of doing a warm boot with the LiveCD on my desktop computer that did not have Ubuntu installed on it.
>
> As you further recommended, in an attempt to get the SD-CF-IDE-DI IDE to CF Adapter that holds my CF card white listed, I am submitting the attached libata_force_80c_CF_card_adapter_whitelist_candidate_information.txt file that has the output from executing four terminal commands to hopefully supply enough information to get it whitelisted.
>
> Although I expect that my RV280 Radeon 9200 Pro video card is too old to expend much effort on, it would be nice to also get it whitelisted so that future newbie Linux users who do not know about using the radeon.modeset=0 parameter on the kernel command line will not be looking at a black screen with a blinking cursor when they attempt to use a LiveCD for troubleshooting, or whatever.
>
> I purposely did not include the URL of one of the Internet sites that sells the adapter in this email in case this is a no no.
>
> If you or someone else needs more information in order to get the CF card adapter whitelisted, they can send me an email with further instructions.
>
> Tejun, I am not sure that I will have either the time or the interest to learn the intricacies of editing http://www.thinkwiki.org/wiki/Compact_Flash_boot_drive to add libata.force=80c to this site in lieu of force_cbl=80: so that fewer people will be asking you questions.  I have a ThinkPad without a HDD plus a laptop adapter that will hold my CF card, but my Think Pad is a lot older than the ones discussed on Compact_Flash_boot_drive.  In addition, I did not see any recent updates to this Internet page, but maybe I can find someone to email who will update this page.
>
> Tejun, thank you very much for helping me.

Is there actually any way to identify the adapter automatically? AFAIK, 
these CF-IDE adapters are just passive circuitry and there's no way to 
identify them through software.

CF Card Adapter White List Candidate

[Tom Denchfield]

[-- Attachment #1: Type: text/plain, Size: 2110 bytes --]

Tejun,

Using your first recommendation in your 01/04/2010 email, I added libata.force=80c to the Ubuntu v10.10 Live CD (Live-CD) kernel command line, and this succeeded in getting Linux to configure my CompactFlash card as UDMA/66, as opposed to the UDMA/33 it had been using.  The attached dmesg_libata_force_80c.txt (dmesg) file shows the details of doing a warm boot with the LiveCD on my desktop computer that did not have Ubuntu installed on it.

As you further recommended, in an attempt to get the SD-CF-IDE-DI IDE to CF Adapter that holds my CF card white listed, I am submitting the attached libata_force_80c_CF_card_adapter_whitelist_candidate_information.txt file that has the output from executing four terminal commands to hopefully supply enough information to get it whitelisted.

Although I expect that my RV280 Radeon 9200 Pro video card is too old to expend much effort on, it would be nice to also get it whitelisted so that future newbie Linux users who do not know about using the radeon.modeset=0 parameter on the kernel command line will not be looking at a black screen with a blinking cursor when they attempt to use a LiveCD for troubleshooting, or whatever.

I purposely did not include the URL of one of the Internet sites that sells the adapter in this email in case this is a no no. 

If you or someone else needs more information in order to get the CF card adapter whitelisted, they can send me an email with further instructions.

Tejun, I am not sure that I will have either the time or the interest to learn the intricacies of editing http://www.thinkwiki.org/wiki/Compact_Flash_boot_drive to add libata.force=80c to this site in lieu of force_cbl=80: so that fewer people will be asking you questions.  I have a ThinkPad without a HDD plus a laptop adapter that will hold my CF card, but my Think Pad is a lot older than the ones discussed on Compact_Flash_boot_drive.  In addition, I did not see any recent updates to this Internet page, but maybe I can find someone to email who will update this page. 

Tejun, thank you very much for helping me.

Tom Denchfield


      

[-- Attachment #2: dmesg_libata_force_80c.txt --]
[-- Type: text/plain, Size: 36346 bytes --]

[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.35-22-generic (buildd@rothera) (gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu4) ) #33-Ubuntu SMP Sun Sep 19 20:34:50 UTC 2010 (Ubuntu 2.6.35-22.33-generic 2.6.35.4)
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[    0.000000]  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 000000007fee0000 (usable)
[    0.000000]  BIOS-e820: 000000007fee0000 - 000000007fee3000 (ACPI NVS)
[    0.000000]  BIOS-e820: 000000007fee3000 - 000000007fef0000 (ACPI data)
[    0.000000]  BIOS-e820: 000000007fef0000 - 000000007ff00000 (reserved)
[    0.000000]  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
[    0.000000] NX (Execute Disable) protection: approximated by x86 segment limits
[    0.000000] DMI 2.3 present.
[    0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
[    0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[    0.000000] e820 update range: 0000000000000000 - 0000000000001000 (usable) ==> (reserved)
[    0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
[    0.000000] last_pfn = 0x7fee0 max_arch_pfn = 0x100000
[    0.000000] MTRR default type: uncachable
[    0.000000] MTRR fixed ranges enabled:
[    0.000000]   00000-9FFFF write-back
[    0.000000]   A0000-BFFFF uncachable
[    0.000000]   C0000-CCFFF write-protect
[    0.000000]   CD000-EFFFF uncachable
[    0.000000]   F0000-F7FFF write-through
[    0.000000]   F8000-F8FFF uncachable
[    0.000000]   F9000-FFFFF write-through
[    0.000000] MTRR variable ranges enabled:
[    0.000000]   0 base 000000000 mask F80000000 write-back
[    0.000000]   1 base 0E0000000 mask FF8000000 write-combining
[    0.000000]   2 base 07FF00000 mask FFFF00000 uncachable
[    0.000000]   3 disabled
[    0.000000]   4 disabled
[    0.000000]   5 disabled
[    0.000000]   6 disabled
[    0.000000]   7 disabled
[    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[    0.000000] Scanning 0 areas for low memory corruption
[    0.000000] modified physical RAM map:
[    0.000000]  modified: 0000000000000000 - 0000000000010000 (reserved)
[    0.000000]  modified: 0000000000010000 - 000000000009f800 (usable)
[    0.000000]  modified: 000000000009f800 - 00000000000a0000 (reserved)
[    0.000000]  modified: 00000000000f0000 - 0000000000100000 (reserved)
[    0.000000]  modified: 0000000000100000 - 000000007fee0000 (usable)
[    0.000000]  modified: 000000007fee0000 - 000000007fee3000 (ACPI NVS)
[    0.000000]  modified: 000000007fee3000 - 000000007fef0000 (ACPI data)
[    0.000000]  modified: 000000007fef0000 - 000000007ff00000 (reserved)
[    0.000000]  modified: 00000000fec00000 - 0000000100000000 (reserved)
[    0.000000] initial memory mapped : 0 - 00c00000
[    0.000000] found SMP MP-table at [c00f3490] f3490
[    0.000000] init_memory_mapping: 0000000000000000-00000000377fe000
[    0.000000]  0000000000 - 0000400000 page 4k
[    0.000000]  0000400000 - 0037400000 page 2M
[    0.000000]  0037400000 - 00377fe000 page 4k
[    0.000000] kernel direct mapping tables up to 377fe000 @ 15000-1a000
[    0.000000] RAMDISK: 7f3fe000 - 7fee0000
[    0.000000] Allocated new RAMDISK: 009a5000 - 0148698f
[    0.000000] Move RAMDISK from 000000007f3fe000 - 000000007fedf98e to 009a5000 - 0148698e
[    0.000000] ACPI: RSDP 000f7610 00014 (v00 P4M80P)
[    0.000000] ACPI: RSDT 7fee3040 0002C (v01 P4M80P AWRDACPI 42302E31 AWRD 00000000)
[    0.000000] ACPI: FACP 7fee30c0 00074 (v01 P4M80P AWRDACPI 42302E31 AWRD 00000000)
[    0.000000] ACPI: DSDT 7fee3180 04EF7 (v01 P4M80P AWRDACPI 00001000 MSFT 0100000E)
[    0.000000] ACPI: FACS 7fee0000 00040
[    0.000000] ACPI: APIC 7fee80c0 00068 (v01 P4M80P AWRDACPI 42302E31 AWRD 00000000)
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] 1158MB HIGHMEM available.
[    0.000000] 887MB LOWMEM available.
[    0.000000]   mapped low ram: 0 - 377fe000
[    0.000000]   low ram: 0 - 377fe000
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000010 -> 0x00001000
[    0.000000]   Normal   0x00001000 -> 0x000377fe
[    0.000000]   HighMem  0x000377fe -> 0x0007fee0
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[2] active PFN ranges
[    0.000000]     0: 0x00000010 -> 0x0000009f
[    0.000000]     0: 0x00000100 -> 0x0007fee0
[    0.000000] On node 0 totalpages: 523887
[    0.000000] free_area_init_node: node 0, pgdat c07ffd40, node_mem_map c1488200
[    0.000000]   DMA zone: 32 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 3951 pages, LIFO batch:0
[    0.000000]   Normal zone: 1744 pages used for memmap
[    0.000000]   Normal zone: 221486 pages, LIFO batch:31
[    0.000000]   HighMem zone: 2318 pages used for memmap
[    0.000000]   HighMem zone: 294356 pages, LIFO batch:31
[    0.000000] Using APIC driver default
[    0.000000] ACPI: PM-Timer IO Port: 0x408
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled)
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 2, version 3, address 0xfec00000, GSI 0-23
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[    0.000000] ACPI: IRQ0 used by override.
[    0.000000] ACPI: IRQ2 used by override.
[    0.000000] ACPI: IRQ9 used by override.
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] SMP: Allowing 2 CPUs, 1 hotplug CPUs
[    0.000000] nr_irqs_gsi: 40
[    0.000000] early_res array is doubled to 64 at [16000 - 167ff]
[    0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[    0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
[    0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
[    0.000000] Allocating PCI resources starting at 7ff00000 (gap: 7ff00000:7ed00000)
[    0.000000] Booting paravirtualized kernel on bare hardware
[    0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
[    0.000000] PERCPU: Embedded 14 pages/cpu @c2800000 s36416 r0 d20928 u2097152
[    0.000000] pcpu-alloc: s36416 r0 d20928 u2097152 alloc=1*4194304
[    0.000000] pcpu-alloc: [0] 0 1 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 519793
[    0.000000] Kernel command line: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz radeon.modeset=0 libata.force=80c toram --
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Enabling fast FPU save and restore... done.
[    0.000000] Enabling unmasked SIMD FPU exception support... done.
[    0.000000] Initializing CPU#0
[    0.000000] allocated 10479680 bytes of page_cgroup
[    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[    0.000000] Subtract (46 early reservations)
[    0.000000]   #1 [0000001000 - 0000002000]   EX TRAMPOLINE
[    0.000000]   #2 [0000100000 - 00009a0adc]   TEXT DATA BSS
[    0.000000]   #3 [00009a1000 - 00009a409a]             BRK
[    0.000000]   #4 [00000f34a0 - 0000100000]   BIOS reserved
[    0.000000]   #5 [00000f3490 - 00000f34a0]    MP-table mpf
[    0.000000]   #6 [000009f800 - 00000f1c44]   BIOS reserved
[    0.000000]   #7 [00000f1d64 - 00000f3490]   BIOS reserved
[    0.000000]   #8 [00000f1c44 - 00000f1d64]    MP-table mpc
[    0.000000]   #9 [0000010000 - 0000011000]      TRAMPOLINE
[    0.000000]   #10 [0000011000 - 0000015000]     ACPI WAKEUP
[    0.000000]   #11 [0000015000 - 0000016000]         PGTABLE
[    0.000000]   #12 [00009a5000 - 0001487000]     NEW RAMDISK
[    0.000000]   #13 [0001487000 - 0001488000]         BOOTMEM
[    0.000000]   #14 [0001488000 - 0002488000]         BOOTMEM
[    0.000000]   #15 [0002488000 - 0002488004]         BOOTMEM
[    0.000000]   #16 [0002488040 - 0002488100]         BOOTMEM
[    0.000000]   #17 [0002488100 - 0002488154]         BOOTMEM
[    0.000000]   #18 [0002488180 - 000248b180]         BOOTMEM
[    0.000000]   #19 [000248b180 - 000248b1f0]         BOOTMEM
[    0.000000]   #20 [000248b200 - 0002491200]         BOOTMEM
[    0.000000]   #21 [0002491200 - 0002491227]         BOOTMEM
[    0.000000]   #22 [0002491240 - 000249133c]         BOOTMEM
[    0.000000]   #23 [0002491340 - 0002491380]         BOOTMEM
[    0.000000]   #24 [0002491380 - 00024913c0]         BOOTMEM
[    0.000000]   #25 [00024913c0 - 0002491400]         BOOTMEM
[    0.000000]   #26 [0002491400 - 0002491440]         BOOTMEM
[    0.000000]   #27 [0002491440 - 0002491480]         BOOTMEM
[    0.000000]   #28 [0002491480 - 00024914c0]         BOOTMEM
[    0.000000]   #29 [00024914c0 - 0002491500]         BOOTMEM
[    0.000000]   #30 [0002491500 - 0002491540]         BOOTMEM
[    0.000000]   #31 [0002491540 - 0002491550]         BOOTMEM
[    0.000000]   #32 [0002491580 - 00024915f0]         BOOTMEM
[    0.000000]   #33 [0002491600 - 0002491670]         BOOTMEM
[    0.000000]   #34 [0002800000 - 000280e000]         BOOTMEM
[    0.000000]   #35 [0002a00000 - 0002a0e000]         BOOTMEM
[    0.000000]   #36 [0002493680 - 0002493684]         BOOTMEM
[    0.000000]   #37 [00024936c0 - 00024936c4]         BOOTMEM
[    0.000000]   #38 [0002493700 - 0002493708]         BOOTMEM
[    0.000000]   #39 [0002493740 - 0002493748]         BOOTMEM
[    0.000000]   #40 [0002493780 - 0002493828]         BOOTMEM
[    0.000000]   #41 [0002493840 - 00024938a8]         BOOTMEM
[    0.000000]   #42 [00024938c0 - 00024978c0]         BOOTMEM
[    0.000000]   #43 [00024978c0 - 00025178c0]         BOOTMEM
[    0.000000]   #44 [00025178c0 - 00025578c0]         BOOTMEM
[    0.000000]   #45 [0002a0e000 - 000340c840]         BOOTMEM
[    0.000000] Initializing HighMem for node 0 (000377fe:0007fee0)
[    0.000000] Memory: 2047964k/2096000k available (4928k kernel code, 47584k reserved, 2336k data, 684k init, 1186696k highmem)
[    0.000000] virtual kernel memory layout:
[    0.000000]     fixmap  : 0xfff16000 - 0xfffff000   ( 932 kB)
[    0.000000]     pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
[    0.000000]     vmalloc : 0xf7ffe000 - 0xff7fe000   ( 120 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xf77fe000   ( 887 MB)
[    0.000000]       .init : 0xc0819000 - 0xc08c4000   ( 684 kB)
[    0.000000]       .data : 0xc05d029e - 0xc0818668   (2336 kB)
[    0.000000]       .text : 0xc0100000 - 0xc05d029e   (4928 kB)
[    0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
[    0.000000] SLUB: Genslabs=13, HWalign=128, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
[    0.000000] 	RCU-based detection of stalled CPUs is disabled.
[    0.000000] 	Verbose stalled-CPUs detection is disabled.
[    0.000000] NR_IRQS:2304 nr_irqs:512
[    0.000000] Console: colour VGA+ 80x25
[    0.000000] console [tty0] enabled
[    0.000000] Fast TSC calibration using PIT
[    0.000000] Detected 2926.079 MHz processor.
[    0.004008] Calibrating delay loop (skipped), value calculated using timer frequency.. 5852.15 BogoMIPS (lpj=11704316)
[    0.004126] pid_max: default: 32768 minimum: 301
[    0.004210] Security Framework initialized
[    0.004294] AppArmor: AppArmor initialized
[    0.004351] Yama: becoming mindful.
[    0.004493] Mount-cache hash table entries: 512
[    0.004769] Initializing cgroup subsys ns
[    0.004832] Initializing cgroup subsys cpuacct
[    0.008015] Initializing cgroup subsys memory
[    0.008084] Initializing cgroup subsys devices
[    0.008142] Initializing cgroup subsys freezer
[    0.008199] Initializing cgroup subsys net_cls
[    0.008304] CPU0: Hyper-Threading is disabled
[    0.008363] mce: CPU supports 4 MCE banks
[    0.008433] CPU0: Thermal monitoring enabled (TM1)
[    0.008496] using mwait in idle threads.
[    0.008560] Performance Events: Netburst events, Netburst P4/Xeon PMU driver.
[    0.008715] ... version:                0
[    0.008771] ... bit width:              40
[    0.008826] ... generic registers:      18
[    0.008882] ... value mask:             000000ffffffffff
[    0.008939] ... max period:             0000007fffffffff
[    0.008997] ... fixed-purpose events:   0
[    0.009052] ... event mask:             000000000003ffff
[    0.010650] SMP alternatives: switching to UP code
[    0.024273] ACPI: Core revision 20100428
[    0.036047] ftrace: converting mcount calls to 0f 1f 44 00 00
[    0.036116] ftrace: allocating 21758 entries in 43 pages
[    0.040132] Enabling APIC mode:  Flat.  Using 1 I/O APICs
[    0.044392] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.084153] CPU0: Intel(R) Celeron(R) CPU 2.93GHz stepping 01
[    0.088000] Brought up 1 CPUs
[    0.088000] Total of 1 processors activated (5852.15 BogoMIPS).
[    0.088000] devtmpfs: initialized
[    0.088000] regulator: core version 0.5
[    0.088000] Time: 11:41:59  Date: 01/04/11
[    0.088000] NET: Registered protocol family 16
[    0.088000] EISA bus registered
[    0.088031] ACPI: bus type pci registered
[    0.096374] PCI: PCI BIOS revision 2.10 entry at 0xf9f20, last bus=1
[    0.096434] PCI: Using configuration type 1 for base access
[    0.097890] bio: create slab <bio-0> at 0
[    0.099242] ACPI: EC: Look up EC in DSDT
[    0.107213] ACPI: Interpreter enabled
[    0.107280] ACPI: (supports S0 S1 S4 S5)
[    0.107551] ACPI: Using IOAPIC for interrupt routing
[    0.118107] ACPI: No dock devices found.
[    0.118174] PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug
[    0.118465] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[    0.118924] pci_root PNP0A03:00: host bridge window [io  0x0000-0x0cf7] (ignored)
[    0.118928] pci_root PNP0A03:00: host bridge window [io  0x0d00-0xffff] (ignored)
[    0.118932] pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
[    0.118935] pci_root PNP0A03:00: host bridge window [mem 0x000c0000-0x000dffff] (ignored)
[    0.118939] pci_root PNP0A03:00: host bridge window [mem 0x7ff00000-0xfebfffff] (ignored)
[    0.118974] pci 0000:00:00.0: reg 10: [mem 0xe0000000-0xe7ffffff pref]
[    0.119352] pci 0000:00:01.0: supports D1
[    0.119408] pci 0000:00:0f.0: reg 10: [io  0xb000-0xb007]
[    0.119418] pci 0000:00:0f.0: reg 14: [io  0xb400-0xb403]
[    0.119426] pci 0000:00:0f.0: reg 18: [io  0xb800-0xb807]
[    0.119434] pci 0000:00:0f.0: reg 1c: [io  0xbc00-0xbc03]
[    0.119442] pci 0000:00:0f.0: reg 20: [io  0xc000-0xc00f]
[    0.119450] pci 0000:00:0f.0: reg 24: [io  0xc400-0xc4ff]
[    0.119537] pci 0000:00:0f.1: reg 20: [io  0xc800-0xc80f]
[    0.119637] pci 0000:00:10.0: reg 20: [io  0xcc00-0xcc1f]
[    0.119670] pci 0000:00:10.0: supports D1 D2
[    0.119673] pci 0000:00:10.0: PME# supported from D0 D1 D2 D3hot D3cold
[    0.119679] pci 0000:00:10.0: PME# disabled
[    0.119736] pci 0000:00:10.1: reg 20: [io  0xd000-0xd01f]
[    0.119769] pci 0000:00:10.1: supports D1 D2
[    0.119772] pci 0000:00:10.1: PME# supported from D0 D1 D2 D3hot D3cold
[    0.119777] pci 0000:00:10.1: PME# disabled
[    0.119835] pci 0000:00:10.2: reg 20: [io  0xd400-0xd41f]
[    0.119868] pci 0000:00:10.2: supports D1 D2
[    0.119870] pci 0000:00:10.2: PME# supported from D0 D1 D2 D3hot D3cold
[    0.119876] pci 0000:00:10.2: PME# disabled
[    0.119932] pci 0000:00:10.3: reg 20: [io  0xd800-0xd81f]
[    0.119966] pci 0000:00:10.3: supports D1 D2
[    0.119968] pci 0000:00:10.3: PME# supported from D0 D1 D2 D3hot D3cold
[    0.119974] pci 0000:00:10.3: PME# disabled
[    0.120050] pci 0000:00:10.4: reg 10: [mem 0xf8100000-0xf81000ff]
[    0.120104] pci 0000:00:10.4: supports D1 D2
[    0.120107] pci 0000:00:10.4: PME# supported from D0 D1 D2 D3hot D3cold
[    0.120112] pci 0000:00:10.4: PME# disabled
[    0.120188] HPET not enabled in BIOS. You might try hpet=force boot option
[    0.120315] pci 0000:00:11.5: reg 10: [io  0xdc00-0xdcff]
[    0.120371] pci 0000:00:11.5: supports D1 D2
[    0.120412] pci 0000:00:12.0: reg 10: [io  0xe400-0xe4ff]
[    0.120421] pci 0000:00:12.0: reg 14: [mem 0xf8101000-0xf81010ff]
[    0.120470] pci 0000:00:12.0: supports D1 D2
[    0.120473] pci 0000:00:12.0: PME# supported from D0 D1 D2 D3hot D3cold
[    0.120478] pci 0000:00:12.0: PME# disabled
[    0.120568] pci 0000:01:00.0: reg 10: [mem 0xe8000000-0xefffffff pref]
[    0.120576] pci 0000:01:00.0: reg 14: [io  0xa000-0xa0ff]
[    0.120583] pci 0000:01:00.0: reg 18: [mem 0xf8030000-0xf803ffff]
[    0.120603] pci 0000:01:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
[    0.120629] pci 0000:01:00.0: supports D1 D2
[    0.120659] pci 0000:01:00.1: reg 10: [mem 0xf0000000-0xf7ffffff pref]
[    0.120667] pci 0000:01:00.1: reg 14: [mem 0xf8020000-0xf802ffff]
[    0.120706] pci 0000:01:00.1: supports D1 D2
[    0.120755] pci 0000:00:01.0: PCI bridge to [bus 01-01]
[    0.120817] pci 0000:00:01.0:   bridge window [io  0xa000-0xafff]
[    0.120824] pci 0000:00:01.0:   bridge window [mem 0xf8000000-0xf80fffff]
[    0.120830] pci 0000:00:01.0:   bridge window [mem 0xe8000000-0xf7ffffff pref]
[    0.120841] pci_bus 0000:00: on NUMA node 0
[    0.120853] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[    0.190368] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 *10 11 12)
[    0.191090] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 6 7 10 *11 12)
[    0.191805] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 10 11 12) *5
[    0.192554] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 10 11 12) *0, disabled.
[    0.193321] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12) *0, disabled.
[    0.194075] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 7 10 11 12) *0, disabled.
[    0.194828] ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 6 7 10 11 12) *0, disabled.
[    0.195581] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 6 7 10 11 12) *0, disabled.
[    0.196446] ACPI: PCI Interrupt Link [ALKA] (IRQs *20)
[    0.196909] ACPI: PCI Interrupt Link [ALKB] (IRQs *21)
[    0.197372] ACPI: PCI Interrupt Link [ALKC] (IRQs *22)
[    0.197891] ACPI: PCI Interrupt Link [ALKD] (IRQs *23)
[    0.198133] HEST: Table is not found!
[    0.198344] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
[    0.198415] vgaarb: loaded
[    0.198742] SCSI subsystem initialized
[    0.198920] libata version 3.00 loaded.
[    0.199029] usbcore: registered new interface driver usbfs
[    0.199111] usbcore: registered new interface driver hub
[    0.199231] usbcore: registered new device driver usb
[    0.199567] ACPI: WMI: Mapper loaded
[    0.199630] PCI: Using ACPI for IRQ routing
[    0.199690] PCI: pci_cache_line_size set to 64 bytes
[    0.199786] reserve RAM buffer: 000000000009f800 - 000000000009ffff 
[    0.199790] reserve RAM buffer: 000000007fee0000 - 000000007fffffff 
[    0.199972] NetLabel: Initializing
[    0.200010] NetLabel:  domain hash size = 128
[    0.200066] NetLabel:  protocols = UNLABELED CIPSOv4
[    0.200143] NetLabel:  unlabeled traffic allowed by default
[    0.200303] Switching to clocksource tsc
[    0.215882] AppArmor: AppArmor Filesystem Enabled
[    0.215974] pnp: PnP ACPI init
[    0.216061] ACPI: bus type pnp registered
[    0.222806] pnp: PnP ACPI: found 13 devices
[    0.222870] ACPI: ACPI bus type pnp unregistered
[    0.222930] PnPBIOS: Disabled by ACPI PNP
[    0.223008] system 00:00: [mem 0x000cd000-0x000cffff] has been reserved
[    0.223070] system 00:00: [mem 0x000f0000-0x000f7fff] could not be reserved
[    0.223129] system 00:00: [mem 0x000f8000-0x000fbfff] could not be reserved
[    0.223189] system 00:00: [mem 0x000fc000-0x000fffff] could not be reserved
[    0.223248] system 00:00: [mem 0x7fee0000-0x7fefffff] could not be reserved
[    0.223308] system 00:00: [mem 0xffff0000-0xffffffff] has been reserved
[    0.223368] system 00:00: [mem 0x00000000-0x0009ffff] could not be reserved
[    0.223427] system 00:00: [mem 0x00100000-0x7fedffff] could not be reserved
[    0.223487] system 00:00: [mem 0xfec00000-0xfec00fff] could not be reserved
[    0.223546] system 00:00: [mem 0xfee00000-0xfee00fff] has been reserved
[    0.223634] system 00:00: [mem 0xfff80000-0xfffeffff] has been reserved
[    0.223703] system 00:02: [io  0x0400-0x047f] has been reserved
[    0.223761] system 00:02: [io  0x0500-0x050f] has been reserved
[    0.223825] system 00:03: [io  0x04d0-0x04d1] has been reserved
[    0.223883] system 00:03: [io  0x0800-0x0805] has been reserved
[    0.223941] system 00:03: [io  0x0290-0x0297] has been reserved
[    0.223999] system 00:03: [io  0x0880-0x088f] has been reserved
[    0.261024] pci 0000:01:00.0: BAR 6: assigned [mem 0xf8000000-0xf801ffff pref]
[    0.261099] pci 0000:00:01.0: PCI bridge to [bus 01-01]
[    0.261157] pci 0000:00:01.0:   bridge window [io  0xa000-0xafff]
[    0.261220] pci 0000:00:01.0:   bridge window [mem 0xf8000000-0xf80fffff]
[    0.261281] pci 0000:00:01.0:   bridge window [mem 0xe8000000-0xf7ffffff pref]
[    0.261366] pci 0000:00:01.0: setting latency timer to 64
[    0.261372] pci_bus 0000:00: resource 0 [io  0x0000-0xffff]
[    0.261375] pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffff]
[    0.261379] pci_bus 0000:01: resource 0 [io  0xa000-0xafff]
[    0.261382] pci_bus 0000:01: resource 1 [mem 0xf8000000-0xf80fffff]
[    0.261385] pci_bus 0000:01: resource 2 [mem 0xe8000000-0xf7ffffff pref]
[    0.261455] NET: Registered protocol family 2
[    0.261605] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.262082] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.263448] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[    0.264232] TCP: Hash tables configured (established 131072 bind 65536)
[    0.264302] TCP reno registered
[    0.264366] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.264447] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.264694] NET: Registered protocol family 1
[    0.264796] pci 0000:00:01.0: disabling DAC on VIA PCI bridge
[    0.264960] pci 0000:00:11.0: Bypassing VIA 8237 APIC De-Assert Message
[    0.265032] pci 0000:01:00.0: Boot video device
[    0.265039] PCI: CLS 32 bytes, default 64
[    0.265341] cpufreq-nforce2: No nForce2 chipset.
[    0.265449] Scanning for low memory corruption every 60 seconds
[    0.265719] audit: initializing netlink socket (disabled)
[    0.265796] type=2000 audit(1294141319.260:1): initialized
[    0.276324] Trying to unpack rootfs image as initramfs...
[    3.476366] highmem bounce pool size: 64 pages
[    3.476436] HugeTLB registered 4 MB page size, pre-allocated 0 pages
[    3.478427] VFS: Disk quotas dquot_6.5.2
[    3.478595] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    3.479651] fuse init (API version 7.14)
[    3.479910] msgmni has been set to 1682
[    3.480606] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    3.480681] io scheduler noop registered
[    3.480736] io scheduler deadline registered
[    3.480815] io scheduler cfq registered (default)
[    3.481072] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[    3.481164] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[    3.481521] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
[    3.481597] ACPI: Power Button [PWRB]
[    3.481719] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
[    3.481796] ACPI: Sleep Button [SLPB]
[    3.481930] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[    3.482000] ACPI: Power Button [PWRF]
[    3.482141] ACPI: Fan [FAN] (on)
[    3.482559] ACPI: acpi_idle registered with cpuidle
[    3.488320] thermal LNXTHERM:01: registered as thermal_zone0
[    3.488395] ACPI: Thermal Zone [THRM] (43 C)
[    3.488550] ERST: Table is not found!
[    3.488960] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    3.489168] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[    3.489816] 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[    3.491735] brd: module loaded
[    3.492105] isapnp: Scanning for PnP cards...
[    3.498398] loop: module loaded
[    3.499251] ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 20
[    3.499322]   alloc irq_desc for 20 on node -1
[    3.499326]   alloc kstat_irqs on node -1
[    3.499339] pata_acpi 0000:00:0f.0: PCI INT B -> Link[ALKA] -> GSI 20 (level, low) -> IRQ 20
[    3.499483] pata_acpi 0000:00:0f.0: PCI INT B disabled
[    3.499573] pata_acpi 0000:00:0f.1: PCI INT A -> Link[ALKA] -> GSI 20 (level, low) -> IRQ 20
[    3.499675] pata_acpi 0000:00:0f.1: PCI INT A disabled
[    3.500291] Fixed MDIO Bus: probed
[    3.500405] PPP generic driver version 2.4.2
[    3.500584] tun: Universal TUN/TAP device driver, 1.6
[    3.500644] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    3.500893] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    3.501346] ACPI: PCI Interrupt Link [ALKB] enabled at IRQ 21
[    3.501412]   alloc irq_desc for 21 on node -1
[    3.501415]   alloc kstat_irqs on node -1
[    3.501427] ehci_hcd 0000:00:10.4: PCI INT C -> Link[ALKB] -> GSI 21 (level, low) -> IRQ 21
[    3.501526] ehci_hcd 0000:00:10.4: EHCI Host Controller
[    3.501692] ehci_hcd 0000:00:10.4: new USB bus registered, assigned bus number 1
[    3.501853] ehci_hcd 0000:00:10.4: irq 21, io mem 0xf8100000
[    3.545554] ehci_hcd 0000:00:10.4: USB 2.0 started, EHCI 1.00
[    3.545839] hub 1-0:1.0: USB hub found
[    3.545905] hub 1-0:1.0: 8 ports detected
[    3.546076] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    3.546161] uhci_hcd: USB Universal Host Controller Interface driver
[    3.546297] uhci_hcd 0000:00:10.0: PCI INT A -> Link[ALKB] -> GSI 21 (level, low) -> IRQ 21
[    3.546377] uhci_hcd 0000:00:10.0: UHCI Host Controller
[    3.546535] uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
[    3.546636] uhci_hcd 0000:00:10.0: irq 21, io base 0x0000cc00
[    3.546927] hub 2-0:1.0: USB hub found
[    3.546995] hub 2-0:1.0: 2 ports detected
[    3.547147] uhci_hcd 0000:00:10.1: PCI INT A -> Link[ALKB] -> GSI 21 (level, low) -> IRQ 21
[    3.547224] uhci_hcd 0000:00:10.1: UHCI Host Controller
[    3.547379] uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
[    3.547482] uhci_hcd 0000:00:10.1: irq 21, io base 0x0000d000
[    3.547775] hub 3-0:1.0: USB hub found
[    3.547838] hub 3-0:1.0: 2 ports detected
[    3.547986] uhci_hcd 0000:00:10.2: PCI INT B -> Link[ALKB] -> GSI 21 (level, low) -> IRQ 21
[    3.548114] uhci_hcd 0000:00:10.2: UHCI Host Controller
[    3.548277] uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
[    3.548381] uhci_hcd 0000:00:10.2: irq 21, io base 0x0000d400
[    3.548691] hub 4-0:1.0: USB hub found
[    3.548756] hub 4-0:1.0: 2 ports detected
[    3.548909] uhci_hcd 0000:00:10.3: PCI INT B -> Link[ALKB] -> GSI 21 (level, low) -> IRQ 21
[    3.548987] uhci_hcd 0000:00:10.3: UHCI Host Controller
[    3.549145] uhci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 5
[    3.549246] uhci_hcd 0000:00:10.3: irq 21, io base 0x0000d800
[    3.549526] hub 5-0:1.0: USB hub found
[    3.550154] hub 5-0:1.0: 2 ports detected
[    3.550404] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[    3.551015] serio: i8042 KBD port at 0x60,0x64 irq 1
[    3.551085] serio: i8042 AUX port at 0x60,0x64 irq 12
[    3.551383] mice: PS/2 mouse device common for all mice
[    3.551723] rtc_cmos 00:05: RTC can wake from S4
[    3.551872] rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
[    3.552034] rtc0: alarms up to one year, y3k, 242 bytes nvram
[    3.552285] device-mapper: uevent: version 1.0.3
[    3.552603] device-mapper: ioctl: 4.17.0-ioctl (2010-03-05) initialised: dm-devel@redhat.com
[    3.552803] device-mapper: multipath: version 1.1.1 loaded
[    3.552865] device-mapper: multipath round-robin: version 1.0.0 loaded
[    3.553187] EISA: Probing bus 0 at eisa.0
[    3.553290] EISA: Detected 0 cards.
[    3.553448] cpuidle: using governor ladder
[    3.553507] cpuidle: using governor menu
[    3.553958] TCP cubic registered
[    3.554232] NET: Registered protocol family 10
[    3.554847] lo: Disabled Privacy Extensions
[    3.555188] NET: Registered protocol family 17
[    3.555357] Using IPI No-Shortcut mode
[    3.555605] PM: Resume from disk failed.
[    3.555628] registered taskstats version 1
[    3.555959]   Magic number: 11:565:680
[    3.556187] rtc_cmos 00:05: setting system clock to 2011-01-04 11:42:03 UTC (1294141323)
[    3.556259] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[    3.556316] EDD information not available.
[    3.818126] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
[    3.862012] isapnp: No Plug & Play device found
[    4.373678] Freeing initrd memory: 11144k freed
[    4.390291] Freeing unused kernel memory: 684k freed
[    4.391425] Write protecting the kernel text: 4932k
[    4.391519] Write protecting the kernel read-only data: 1976k
[    4.442306] udev[69]: starting version 163
[    4.771021] Floppy drive(s): fd0 is 1.44M
[    4.795333] sata_via 0000:00:0f.0: version 2.6
[    4.795362] sata_via 0000:00:0f.0: PCI INT B -> Link[ALKA] -> GSI 20 (level, low) -> IRQ 20
[    4.795492] sata_via 0000:00:0f.0: routed to hard irq line 11
[    4.822748] FDC 0 is a post-1991 82077
[    4.847337] scsi0 : sata_via
[    4.862040] scsi1 : sata_via
[    4.862223] ata1: SATA max UDMA/133 cmd 0xb000 ctl 0xb400 bmdma 0xc000 irq 20
[    4.862286] ata2: SATA max UDMA/133 cmd 0xb800 ctl 0xbc00 bmdma 0xc008 irq 20
[    4.862665] pata_via 0000:00:0f.1: version 0.3.4
[    4.862695] pata_via 0000:00:0f.1: PCI INT A -> Link[ALKA] -> GSI 20 (level, low) -> IRQ 20
[    4.863178] Linux agpgart interface v0.103
[    4.880092] scsi2 : pata_via
[    4.892348] via-rhine.c:v1.10-LK1.4.3 2007-03-06 Written by Donald Becker
[    4.892419] via-rhine: Broken BIOS detected, avoid_D3 enabled.
[    4.902075] scsi3 : pata_via
[    4.905305] ata3: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xc800 irq 14
[    4.905371] ata4: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xc808 irq 15
[    4.905547] agpgart: Detected VIA VT3314 chipset
[    4.960584] agpgart-via 0000:00:00.0: AGP aperture is 128M @ 0xe0000000
[    4.961075] ACPI: PCI Interrupt Link [ALKD] enabled at IRQ 23
[    4.961144]   alloc irq_desc for 23 on node -1
[    4.961148]   alloc kstat_irqs on node -1
[    4.961161] via-rhine 0000:00:12.0: PCI INT A -> Link[ALKD] -> GSI 23 (level, low) -> IRQ 23
[    4.996395] eth0: VIA Rhine II at 0xf8101000, 00:e0:4c:e6:e5:62, IRQ 23.
[    4.997173] eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1.
[    5.004307] [drm] Initialized drm 1.1.0 20060810
[    5.064026] ata1: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
[    5.088368] ata3: FORCE: cable set to 80c
[    5.088452] ata3.00: CFA: TS8GCF133, 20100804, max UDMA/66
[    5.088509] ata3.00: 15662304 sectors, multi 0: LBA 
[    5.104301] ata3.00: configured for UDMA/66
[    5.276025] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    5.440209] ata2: FORCE: cable set to 80c
[    5.487947] ata2.00: ATA-7: ST3160811AS, 3.AAE, max UDMA/133
[    5.488024] ata2.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32)
[    5.562926] ata2.00: configured for UDMA/133
[    5.563182] scsi 1:0:0:0: Direct-Access     ATA      ST3160811AS      3.AA PQ: 0 ANSI: 5
[    5.563575] sd 1:0:0:0: Attached scsi generic sg0 type 0
[    5.564449] scsi 2:0:0:0: Direct-Access     ATA      TS8GCF133        2010 PQ: 0 ANSI: 5
[    5.564819] sd 2:0:0:0: Attached scsi generic sg1 type 0
[    5.565631] sd 2:0:0:0: [sdb] 15662304 512-byte logical blocks: (8.01 GB/7.46 GiB)
[    5.565738] sd 1:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
[    5.565974] sd 1:0:0:0: [sda] Write Protect is off
[    5.566035] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    5.566060] sd 2:0:0:0: [sdb] Write Protect is off
[    5.566120] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    5.566183] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    5.566431] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    5.566936]  sda:
[    5.567128]  sdb: sdb1
[    5.569365] sd 2:0:0:0: [sdb] Attached SCSI disk
[    5.610943]  sda1 sda2 < sda5 sda6 sda7 sda8 sda9 sda10 >
[    5.697462] sd 1:0:0:0: [sda] Attached SCSI disk
[    5.744367] ata4: FORCE: cable set to 80c
[    5.744448] ata4.00: ATAPI: SONY    DVD RW DW-G120A, MYS6, max UDMA/66
[    5.776283] ata4.00: configured for UDMA/66
[    5.777946] scsi 3:0:0:0: CD-ROM            SONY     DVD RW DW-G120A  MYS6 PQ: 0 ANSI: 5
[    5.782649] sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray
[    5.782727] Uniform CD-ROM driver Revision: 3.20
[    5.783779] sr 3:0:0:0: Attached scsi CD-ROM sr0
[    5.784248] sr 3:0:0:0: Attached scsi generic sg2 type 5
[    5.898526]   alloc irq_desc for 16 on node -1
[    5.898534]   alloc kstat_irqs on node -1
[    5.898547] pci 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    5.899066] [drm] Initialized radeon 1.33.0 20080528 for 0000:01:00.0 on minor 0
[    7.271816] Btrfs loaded
[    7.283302] xor: automatically using best checksumming function: pIII_sse
[    7.300009]    pIII_sse  :  4482.000 MB/sec
[    7.300020] xor: using function: pIII_sse (4482.000 MB/sec)
[    7.305171] device-mapper: dm-raid45: initialized v0.2594b
[    8.982616] EXT3-fs: barriers not enabled
[    8.992635] kjournald starting.  Commit interval 5 seconds
[    8.992698] EXT3-fs (sda9): mounted filesystem with ordered data mode
[   10.702793] ISO 9660 Extensions: Microsoft Joliet Level 3
[   10.730609] ISO 9660 Extensions: RRIP_1991A
[  169.029581] aufs 2-standalone.tree-35-rcN-20100705
[  169.065066] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[  192.666996] Adding 987960k swap on /dev/sda10.  Priority:-1 extents:1 across:987960k 
[  193.112097] udev[1313]: starting version 163
[  193.716592] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[  194.165049] psmouse serio1: ID: 10 00 64
[  194.235113] parport_pc 00:0a: reported by Plug and Play ACPI
[  194.235165] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[  194.753382] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input4
[  195.137343] ppdev: user-space parallel port driver
[  195.291507] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[  195.955066] ACPI: PCI Interrupt Link [ALKC] enabled at IRQ 22
[  195.955079]   alloc irq_desc for 22 on node -1
[  195.955083]   alloc kstat_irqs on node -1
[  195.955097] VIA 82xx Audio 0000:00:11.5: PCI INT C -> Link[ALKC] -> GSI 22 (level, low) -> IRQ 22
[  195.955280] VIA 82xx Audio 0000:00:11.5: setting latency timer to 64
[  197.163702] lp0: using parport0 (interrupt-driven).
[  202.459449] agpgart-via 0000:00:00.0: AGP 3.5 bridge
[  202.459481] agpgart-via 0000:00:00.0: putting AGP V3 device into 8x mode
[  202.459563] pci 0000:01:00.0: putting AGP V3 device into 8x mode
[  202.822605] [drm] Setting GART location based on new memory map
[  202.822614] [drm] Can't use AGP base @0xe0000000, won't fit
[  202.823705] [drm] Loading R200 Microcode
[  202.912771] [drm] writeback test succeeded in 1 usecs
[  206.312031] eth0: no IPv6 routers present
[  229.805740] ISO 9660 Extensions: Microsoft Joliet Level 3
[  229.866282] ISO 9660 Extensions: RRIP_1991A

[-- Attachment #3: libata_force_80c_CF_card_adapter_whitelist_candidate_information.txt --]
[-- Type: text/plain, Size: 29091 bytes --]

The purpose of this file is to provide information in an attempt to get the direct insertion, SD-CF-IDE-DI IDE to CF Adaptor that holds my CF card whitelisted as recommended by Tejun Heo (htejun AT gmail DOT com) when he advised me in a 01/04/2010 email.

For privacy reasons, I have obscured three digits of part of the serial number of my CF card with XXX. 

The following terminal commands outputs that are included in this file were executed after a warm boot using a Live CD (LiveCD) of Ubuntu v10.10 on a computer that did not have Ubuntu installed on it:

 1) sudo hdparm -I /dev/sdb
 2) sudo lspci -vvv
 3) sudo dmidecode
 4) udevadm info -q all -n /dev/sdb1


To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

ubuntu@ubuntu:~$ dmesg > dmesg_libata_force_80c.txt  {<- This file is also attached to this email.}
ubuntu@ubuntu:~$ date
Tue Jan  4 17:50:19 UTC 2011
ubuntu@ubuntu:~$ sudo hdparm -V
hdparm v9.27
ubuntu@ubuntu:~$ sudo hdparm -I /dev/sdb

/dev/sdb:

CompactFlash ATA device
	Model Number:       TS8GCF133                               
	Serial Number:      20101101    C213XXXE
	Firmware Revision:  20100804
Standards:
	Supported: 7 
	Likely used: 7
Configuration:
	Logical		max	current
	cylinders	15538	15538
	heads		16	16
	sectors/track	63	63
	--
	CHS current addressable sectors:   15662304
	LBA    user addressable sectors:   15662304
	Logical/Physical Sector size:           512 bytes
	device size with M = 1024*1024:        7647 MBytes
	device size with M = 1000*1000:        8019 MBytes (8 GB)
	cache/buffer size  = 1 KBytes (type=DualPort)
Capabilities:
	LBA, IORDY(can be disabled)
	Standby timer values: spec'd by Vendor
	R/W multiple sector transfer: Max = 1	Current = 0
	Advanced power management level: disabled
	DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4 
	     Cycle time: min=120ns recommended=120ns
	PIO: pio0 pio1 pio2 pio3 pio4 
	     Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
	Enabled	Supported:
	   *	SMART feature set
	    	Security Mode feature set
	    	Power Management feature set
	    	Write cache
	    	WRITE_BUFFER command
	    	READ_BUFFER command
	    	NOP cmd
	   *	CFA feature set
	    	Advanced Power Management feature set
	    	Mandatory FLUSH_CACHE
	   *	SMART self-test
	   *	CFA advanced modes: pio5 pio6 mdma3 mdma4 
	   *	CFA Power Level 1  (max 500mA)
Security: 
	Master password revision code = 65534
		supported
	not	enabled
	not	locked
	not	frozen
	not	expired: security count
	not	supported: enhanced erase
	2min for SECURITY ERASE UNIT. 
HW reset results:
	CBLID- above Vih
	Device num = 0
Integrity word not set (found 0x0000, expected 0x34a5)

---=====

ubuntu@ubuntu:~$ sudo lspci -vvv
00:00.0 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
	Subsystem: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 8
	Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
	Capabilities: [80] AGP version 3.5
		Status: RQ=8 Iso- ArqSz=0 Cal=2 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3+ Rate=x4,x8
		Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x8
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: agpgart-via
	Kernel modules: via-agp

00:00.1 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0

00:00.2 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0

00:00.3 Host bridge: VIA Technologies, Inc. PT890 Host Bridge
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Kernel modules: via-agp

00:00.4 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0

00:00.7 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0

00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000a000-0000afff
	Memory behind bridge: f8000000-f80fffff
	Prefetchable memory behind bridge: e8000000-f7ffffff
	Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR+ <PERR-
	BridgeCtl: Parity- SERR+ NoISA+ VGA+ MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [70] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel modules: shpchp

00:0f.0 IDE interface: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) (prog-if 8f [Master SecP SecO PriP PriO])
	Subsystem: Biostar Microtech Int'l Corp Device 3206
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32
	Interrupt: pin B routed to IRQ 20
	Region 0: I/O ports at b000 [size=8]
	Region 1: I/O ports at b400 [size=4]
	Region 2: I/O ports at b800 [size=8]
	Region 3: I/O ports at bc00 [size=4]
	Region 4: I/O ports at c000 [size=16]
	Region 5: I/O ports at c400 [size=256]
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: sata_via
	Kernel modules: sata_via

00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
	Subsystem: Biostar Microtech Int'l Corp Device 3206
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32
	Interrupt: pin A routed to IRQ 20
	Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
	Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
	Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
	Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
	Region 4: I/O ports at c800 [size=16]
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: pata_via
	Kernel modules: pata_via

00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
	Subsystem: Biostar Microtech Int'l Corp Device 3206
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 21
	Region 4: I/O ports at cc00 [size=32]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: uhci_hcd

00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
	Subsystem: Biostar Microtech Int'l Corp Device 3206
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 21
	Region 4: I/O ports at d000 [size=32]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME+
	Kernel driver in use: uhci_hcd

00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
	Subsystem: Biostar Microtech Int'l Corp Device 3206
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 32 bytes
	Interrupt: pin B routed to IRQ 21
	Region 4: I/O ports at d400 [size=32]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: uhci_hcd

00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
	Subsystem: Biostar Microtech Int'l Corp Device 3206
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 32 bytes
	Interrupt: pin B routed to IRQ 21
	Region 4: I/O ports at d800 [size=32]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: uhci_hcd

00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) (prog-if 20 [EHCI])
	Subsystem: Biostar Microtech Int'l Corp Device 3206
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 32 bytes
	Interrupt: pin C routed to IRQ 21
	Region 0: Memory at f8100000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [80] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME+
	Kernel driver in use: ehci_hcd

00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
	Subsystem: VIA Technologies, Inc. DFI KT600-AL / Soltek SL-B9D-FGR Motherboard
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel modules: i2c-viapro

00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
	Subsystem: Biostar Microtech Int'l Corp Device 8212
	Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin C routed to IRQ 22
	Region 0: I/O ports at dc00 [size=256]
	Capabilities: [c0] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: VIA 82xx Audio
	Kernel modules: snd-via82xx

00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
	Subsystem: Biostar Microtech Int'l Corp Device 2200
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (750ns min, 2000ns max), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 23
	Region 0: I/O ports at e400 [size=256]
	Region 1: Memory at f8101000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [40] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: via-rhine
	Kernel modules: via-rhine

01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (rev 01) (prog-if 00 [VGA controller])
	Subsystem: ATI Technologies Inc RV280 [Radeon 9200 PRO]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (2000ns min), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at e8000000 (32-bit, prefetchable) [size=128M]
	Region 1: I/O ports at a000 [size=256]
	Region 2: Memory at f8030000 (32-bit, non-prefetchable) [size=64K]
	[virtual] Expansion ROM at f8000000 [disabled] [size=128K]
	Capabilities: [58] AGP version 3.0
		Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
		Command: RQ=8 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x8
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel modules: radeon, radeonfb

01:00.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (Secondary) (rev 01)
	Subsystem: ATI Technologies Inc Device 5961
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: Memory at f0000000 (32-bit, prefetchable) [disabled] [size=128M]
	Region 1: Memory at f8020000 (32-bit, non-prefetchable) [disabled] [size=64K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-

ubuntu@ubuntu:~$ 


---=====

ubuntu@ubuntu:~$ sudo dmidecode
# dmidecode 2.9
SMBIOS 2.3 present.
35 structures occupying 1056 bytes.
Table at 0x000F0000.

Handle 0x0000, DMI type 0, 20 bytes
BIOS Information
	Vendor: Phoenix Technologies, LTD
	Version: 6.00 PG
	Release Date: 09/16/2005
	Address: 0xE0000
	Runtime Size: 128 kB
	ROM Size: 512 kB
	Characteristics:
		ISA is supported
		PCI is supported
		PNP is supported
		APM is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		BIOS ROM is socketed
		EDD is supported
		5.25"/360 KB floppy services are supported (int 13h)
		5.25"/1.2 MB floppy services are supported (int 13h)
		3.5"/720 KB floppy services are supported (int 13h)
		3.5"/2.88 MB floppy services are supported (int 13h)
		Print screen service is supported (int 5h)
		8042 keyboard services are supported (int 9h)
		Serial services are supported (int 14h)
		Printer services are supported (int 17h)
		CGA/mono video services are supported (int 10h)
		ACPI is supported
		USB legacy is supported
		AGP is supported
		LS-120 boot is supported
		ATAPI Zip drive boot is supported
		BIOS boot specification is supported

Handle 0x0001, DMI type 1, 25 bytes
System Information
	Manufacturer:  
	Product Name:  
	Version:  
	Serial Number:  
	UUID: 00000000-0000-0000-DF3E-0000FF27BF7F
	Wake-up Type: Power Switch

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
	Manufacturer:  
	Product Name: P4M800CE-8237
	Version:  
	Serial Number:  

Handle 0x0003, DMI type 3, 17 bytes
Chassis Information
	Manufacturer:  
	Type: Desktop
	Lock: Not Present
	Version:  
	Serial Number:  
	Asset Tag:  
	Boot-up State: Unknown
	Power Supply State: Unknown
	Thermal State: Unknown
	Security Status: Unknown
	OEM Information: 0x00000000

Handle 0x0004, DMI type 4, 35 bytes
Processor Information
	Socket Designation: Socket 775
	Type: Central Processor
	Family: Celeron
	Manufacturer: Intel
	ID: 41 0F 00 00 FF FB EB BF
	Signature: Type 0, Family 15, Model 4, Stepping 1
	Flags:
		FPU (Floating-point unit on-chip)
		VME (Virtual mode extension)
		DE (Debugging extension)
		PSE (Page size extension)
		TSC (Time stamp counter)
		MSR (Model specific registers)
		PAE (Physical address extension)
		MCE (Machine check exception)
		CX8 (CMPXCHG8 instruction supported)
		APIC (On-chip APIC hardware supported)
		SEP (Fast system call)
		MTRR (Memory type range registers)
		PGE (Page global enable)
		MCA (Machine check architecture)
		CMOV (Conditional move instruction supported)
		PAT (Page attribute table)
		PSE-36 (36-bit page size extension)
		CLFSH (CLFLUSH instruction supported)
		DS (Debug store)
		ACPI (ACPI supported)
		MMX (MMX technology supported)
		FXSR (Fast floating-point save and restore)
		SSE (Streaming SIMD extensions)
		SSE2 (Streaming SIMD extensions 2)
		SS (Self-snoop)
		HTT (Hyper-threading technology)
		TM (Thermal monitor supported)
		PBE (Pending break enabled)
	Version: Intel(R) Celeron(R) CPU
	Voltage: 1.3 V
	External Clock: 133 MHz
	Max Speed: 1500 MHz
	Current Speed: 2933 MHz
	Status: Populated, Enabled
	Upgrade: ZIF Socket
	L1 Cache Handle: 0x0009
	L2 Cache Handle: 0x000B
	L3 Cache Handle: Not Provided
	Serial Number:  
	Asset Tag:  
	Part Number:  

Handle 0x0005, DMI type 4, 35 bytes
Processor Information
	Socket Designation: Socket 775
	Type: Central Processor
	Family: Unknown
	Manufacturer: Unknown
	ID: 00 00 00 00 00 00 00 00
	Version: Intel(R) Celeron(R) CPU
	Voltage: 1.3 V
	External Clock: 133 MHz
	Max Speed: 1500 MHz
	Current Speed: 2933 MHz
	Status: Populated, Disabled By User
	Upgrade: ZIF Socket
	L1 Cache Handle: 0x000A
	L2 Cache Handle: 0x000C
	L3 Cache Handle: Not Provided
	Serial Number:  
	Asset Tag:  
	Part Number:  

Handle 0x0006, DMI type 5, 20 bytes
Memory Controller Information
	Error Detecting Method: None
	Error Correcting Capabilities:
		None
	Supported Interleave: One-way Interleave
	Current Interleave: Four-way Interleave
	Maximum Memory Module Size: 32 MB
	Maximum Total Memory Size: 64 MB
	Supported Speeds:
		70 ns
		60 ns
	Supported Memory Types:
		Standard
		EDO
	Memory Module Voltage: 5.0 V
	Associated Memory Slots: 2
		0x0007
		0x0008
	Enabled Error Correcting Capabilities: None

Handle 0x0007, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: A0
	Bank Connections: 0
	Current Speed: 50 ns
	Type: Other
	Installed Size: 512 MB (Single-bank Connection)
	Enabled Size: 512 MB (Single-bank Connection)
	Error Status: OK

Handle 0x0008, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: A1
	Bank Connections: 2
	Current Speed: 50 ns
	Type: Other
	Installed Size: 134217728 MB (Single-bank Connection)
	Enabled Size: 134217728 MB (Single-bank Connection)
	Error Status: OK

Handle 0x0009, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Internal Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 32 KB
	Maximum Size: 32 KB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x000A, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Internal Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 32 KB
	Maximum Size: 32 KB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x000B, DMI type 7, 19 bytes
Cache Information
	Socket Designation: External Cache
	Configuration: Enabled, Not Socketed, Level 2
	Operational Mode: Write Back
	Location: External
	Installed Size: 256 KB
	Maximum Size: 256 KB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x000C, DMI type 7, 19 bytes
Cache Information
	Socket Designation: External Cache
	Configuration: Enabled, Not Socketed, Level 2
	Operational Mode: Write Back
	Location: External
	Installed Size: 256 KB
	Maximum Size: 256 KB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: PRIMARY IDE
	Internal Connector Type: On Board IDE
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x000E, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: SECONDARY IDE
	Internal Connector Type: On Board IDE
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x000F, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: FDD
	Internal Connector Type: On Board Floppy
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: 8251 FIFO Compatible

Handle 0x0010, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: COM1
	Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
	External Reference Designator:  
	External Connector Type: DB-9 male
	Port Type: Serial Port 16450 Compatible

Handle 0x0011, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: COM2
	Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
	External Reference Designator:  
	External Connector Type: DB-9 male
	Port Type: Serial Port 16450 Compatible

Handle 0x0012, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: LPT1
	Internal Connector Type: DB-25 female
	External Reference Designator:  
	External Connector Type: DB-25 female
	Port Type: Parallel Port ECP/EPP

Handle 0x0013, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Keyboard
	Internal Connector Type: PS/2
	External Reference Designator:  
	External Connector Type: PS/2
	Port Type: Keyboard Port

Handle 0x0014, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: PS/2 Mouse
	Internal Connector Type: PS/2
	External Reference Designator:  
	External Connector Type: PS/2
	Port Type: Mouse Port

Handle 0x0015, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Specified
	Internal Connector Type: None
	External Reference Designator: USB0
	External Connector Type: Other
	Port Type: USB

Handle 0x0016, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI0
	Type: 32-bit PCI
	Current Usage: Available
	Length: Long
	ID: 1
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x0017, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI1
	Type: 32-bit PCI
	Current Usage: Available
	Length: Long
	ID: 2
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x0018, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI2
	Type: 32-bit PCI
	Current Usage: Available
	Length: Long
	ID: 3
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x0019, DMI type 9, 13 bytes
System Slot Information
	Designation: AGP
	Type: 32-bit AGP
	Current Usage: In Use
	Length: Long
	ID: 8
	Characteristics:
		5.0 V is provided

Handle 0x001A, DMI type 13, 22 bytes
BIOS Language Information
	Installable Languages: 3
		n|US|iso8859-1
		n|US|iso8859-1
		r|CA|iso8859-1
	Currently Installed Language: n|US|iso8859-1

Handle 0x001B, DMI type 16, 15 bytes
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: None
	Maximum Capacity: 1 GB
	Error Information Handle: Not Provided
	Number Of Devices: 2

Handle 0x001C, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x001B
	Error Information Handle: Not Provided
	Total Width: Unknown
	Data Width: Unknown
	Size: 512 MB
	Form Factor: DIMM
	Set: None
	Locator: A0
	Bank Locator: Bank0/1
	Type: Unknown
	Type Detail: None
	Speed: Unknown
	Manufacturer: None
	Serial Number: None
	Asset Tag: None
	Part Number: None

Handle 0x001D, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x001B
	Error Information Handle: Not Provided
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: None
	Locator: A1
	Bank Locator: Bank2/3
	Type: Unknown
	Type Detail: None
	Speed: Unknown
	Manufacturer: None
	Serial Number: None
	Asset Tag: None
	Part Number: None

Handle 0x001E, DMI type 19, 15 bytes
Memory Array Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0001FFFFFFF
	Range Size: 512 MB
	Physical Array Handle: 0x001B
	Partition Width: 0

Handle 0x001F, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0001FFFFFFF
	Range Size: 512 MB
	Physical Device Handle: 0x001C
	Memory Array Mapped Address Handle: 0x001E
	Partition Row Position: 1

Handle 0x0020, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00020000000
	Ending Address: 0x0001FFFFFFF
	Range Size: Invalid
	Physical Device Handle: 0x001D
	Memory Array Mapped Address Handle: 0x001E
	Partition Row Position: 1

Handle 0x0021, DMI type 32, 11 bytes
System Boot Information
	Status: No errors detected

Handle 0x0022, DMI type 127, 4 bytes
End Of Table

ubuntu@ubuntu:~$ date
Tue Jan  4 18:18:21 UTC 2011
ubuntu@ubuntu:~$

---=====

ubuntu@ubuntu:~$ date
Tue Jan  4 18:49:49 UTC 2011
ubuntu@ubuntu:~$ udevadm info -q all -n /dev/sdb1
P: /devices/pci0000:00/0000:00:0f.1/host2/target2:0:0/2:0:0:0/block/sdb/sdb1
N: sdb1
S: block/8:17
S: disk/by-id/ata-TS8GCF133_20101101_C213XXXE-part1
S: disk/by-id/scsi-SATA_TS8GCF133_20101101_C213XXXE-part1
S: disk/by-path/pci-0000:00:0f.1-scsi-0:0:0:0-part1
S: disk/by-uuid/FC30-3DA9
S: disk/by-label/TRANSCEND
E: UDEV_LOG=3
E: DEVPATH=/devices/pci0000:00/0000:00:0f.1/host2/target2:0:0/2:0:0:0/block/sdb/sdb1
E: SUBSYSTEM=block
E: DEVNAME=sdb1
E: ID_ATA=1
E: ID_TYPE=disk
E: ID_BUS=ata
E: ID_MODEL=TS8GCF133
E: ID_MODEL_ENC=TS8GCF133\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20
E: ID_REVISION=20100840
E: ID_SERIAL=TS8GCF133_20101101_C213XXXE
E: ID_SERIAL_SHORT=20101101_C213XXXE
E: ID_ATA_WRITE_CACHE=1
E: ID_ATA_WRITE_CACHE_ENABLED=0
E: ID_ATA_FEATURE_SET_PM=1
E: ID_ATA_FEATURE_SET_PM_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY=1
E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0
E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=2
E: ID_ATA_FEATURE_SET_SMART=1
E: ID_ATA_FEATURE_SET_SMART_ENABLED=1
E: ID_ATA_FEATURE_SET_APM=1
E: ID_ATA_FEATURE_SET_APM_ENABLED=0
E: ID_SCSI_COMPAT=SATA_TS8GCF133_20101101_C213XXXE
E: ID_PATH=pci-0000:00:0f.1-scsi-0:0:0:0
E: ID_PART_TABLE_TYPE=dos
E: ID_FS_LABEL=TRANSCEND
E: ID_FS_LABEL_ENC=TRANSCEND
E: ID_FS_UUID=FC30-3DA9
E: ID_FS_UUID_ENC=FC30-3DA9
E: ID_FS_VERSION=FAT32
E: ID_FS_TYPE=vfat
E: ID_FS_USAGE=filesystem
E: UDISKS_PRESENTATION_NOPOLICY=0
E: UDISKS_PARTITION=1
E: UDISKS_PARTITION_SCHEME=mbr
E: UDISKS_PARTITION_NUMBER=1
E: UDISKS_PARTITION_TYPE=0x0b
E: UDISKS_PARTITION_SIZE=8018551296
E: UDISKS_PARTITION_FLAGS=boot
E: UDISKS_PARTITION_SLAVE=/sys/devices/pci0000:00/0000:00:0f.1/host2/target2:0:0/2:0:0:0/block/sdb
E: UDISKS_PARTITION_OFFSET=32256
E: UDISKS_PARTITION_ALIGNMENT_OFFSET=0
E: MAJOR=8
E: MINOR=17
E: DEVTYPE=partition
E: DEVLINKS=/dev/block/8:17 /dev/disk/by-id/ata-TS8GCF133_20101101_C213XXXE-part1 /dev/disk/by-id/scsi-SATA_TS8GCF133_20101101_C213XXXE-part1 /dev/disk/by-path/pci-0000:00:0f.1-scsi-0:0:0:0-part1 /dev/disk/by-uuid/FC30-3DA9 /dev/disk/by-label/TRANSCEND

ubuntu@ubuntu:~$