[gentoo-user] Are those "green" drives any good?

[gentoo-user] Are those "green" drives any good?

[Dale]

Hi,

As some know, I'm planning to buy me a LARGE hard drive to put all my
videos on, eventually.  The prices are coming down now.  I keep seeing
these "green" drives that are made by just about every company nowadays.
 When comparing them to a non "green" drive, do they hold up as good?
Are they as dependable as a plain drive?  I guess they are more
efficient and I get that but do they break quicker, more often or no
difference?

I have noticed that they tend to spin slower and are cheaper.  That much
I have figured out.  Other than that, I can't see any other difference.
 Data speeds seem to be about the same.

Please, no brand wars.  I may get a WD, Maxtor, Samsung or some other
brand.  I haven't picked that part yet.  So far, I have had good luck
with drives.  I think I have one doorstop so far.  I have at least one
of each of the brands above too.  Don't jinx me.  I'm sure someone has a
horror story about some brand.

Thanks much.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Re: [gentoo-user] Are those "green" drives any good?

[Alan McKinnon]

On Wed, 09 May 2012 03:47:09 -0500
Dale <rdalek1967@gmail.com> wrote:

> Hi,
> 
> As some know, I'm planning to buy me a LARGE hard drive to put all my
> videos on, eventually.  The prices are coming down now.  I keep seeing
> these "green" drives that are made by just about every company
> nowadays. When comparing them to a non "green" drive, do they hold up
> as good? Are they as dependable as a plain drive?  I guess they are
> more efficient and I get that but do they break quicker, more often
> or no difference?
> 
> I have noticed that they tend to spin slower and are cheaper.  That
> much I have figured out.  Other than that, I can't see any other
> difference. Data speeds seem to be about the same.
> 
> Please, no brand wars.  I may get a WD, Maxtor, Samsung or some other
> brand.  I haven't picked that part yet.  So far, I have had good luck
> with drives.  I think I have one doorstop so far.  I have at least one
> of each of the brands above too.  Don't jinx me.  I'm sure someone
> has a horror story about some brand.


Green drives are basically just low power drives. It's a branding
gimmick. Like you noticed already, they tend to spin slower (uses less
power).

I stuck 4 of them in my media server for 12TB of cheap storage. And
they are silent. I can barely hear them running even when I'm sitting
next to the server and the kids are running the telly full tilt :-)

I haven't heard any mention from anyone at all that they are less
reliable in any way. I'd expect them to be more reliable than
super-fast drives because they are lower power, but drive models have
so many things affecting reliability it's hard to tell.

One thing we have noticed is that Samsung's recent model are not very
"green", they spin up slowly, use lots of power and make a racket when
spinning. But they do work.



-- 
Alan McKinnnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Are those "green" drives any good?

[Dale]

Alan McKinnon wrote:
> On Wed, 09 May 2012 03:47:09 -0500
> Dale <rdalek1967@gmail.com> wrote:
> 
>> Hi,
>>
>> As some know, I'm planning to buy me a LARGE hard drive to put all my
>> videos on, eventually.  The prices are coming down now.  I keep seeing
>> these "green" drives that are made by just about every company
>> nowadays. When comparing them to a non "green" drive, do they hold up
>> as good? Are they as dependable as a plain drive?  I guess they are
>> more efficient and I get that but do they break quicker, more often
>> or no difference?
>>
>> I have noticed that they tend to spin slower and are cheaper.  That
>> much I have figured out.  Other than that, I can't see any other
>> difference. Data speeds seem to be about the same.
>>
>> Please, no brand wars.  I may get a WD, Maxtor, Samsung or some other
>> brand.  I haven't picked that part yet.  So far, I have had good luck
>> with drives.  I think I have one doorstop so far.  I have at least one
>> of each of the brands above too.  Don't jinx me.  I'm sure someone
>> has a horror story about some brand.
> 
> 
> Green drives are basically just low power drives. It's a branding
> gimmick. Like you noticed already, they tend to spin slower (uses less
> power).
> 
> I stuck 4 of them in my media server for 12TB of cheap storage. And
> they are silent. I can barely hear them running even when I'm sitting
> next to the server and the kids are running the telly full tilt :-)
> 
> I haven't heard any mention from anyone at all that they are less
> reliable in any way. I'd expect them to be more reliable than
> super-fast drives because they are lower power, but drive models have
> so many things affecting reliability it's hard to tell.
> 
> One thing we have noticed is that Samsung's recent model are not very
> "green", they spin up slowly, use lots of power and make a racket when
> spinning. But they do work.
> 

I was thinking the same thing about the speed and them lasting longer
because of the slower speed.  I mean, it's less wear and less heat.  I'd
just hate to buy one and it be a piece of junk or something else I
wasn't expecting to be wrong.   I wish I could afford server grade.
Weeeeee!!

I'm going to give this a shot.  It's not like the OS is on it and I will
be putting a lot of wear on it or be making those heads sing.  It's just
going to store videos, music and other stuff.  I plan to set it up with
LVM and put /home on it.  Then I'm going to get rid of this legacy /data
directory I have been carrying around for the past 7 or 8 years.  Just
put it all in /home where it should have been to begin with.

I also forgot to mention, this rig runs 24/7 for the most part.  It's
usually only off when the power has failed and my UPS is a bit low.
I'll be glad when they get our new wires ran for power.  They been
working on it for at least a month.  It's ONLY 12 miles or so.  ;-)
They are replacing poles, wires, hardware and everything.  I been here
for 40 years, I have never seen them replace all this.  Bad thing is,
the lights go out when they do a major switch over.   I bet the lines
won't be breaking so much when this is done, at least not until some nut
wrecks and hits the stinking pole.   :/

Thanks for the info.  At least I know it won't be junk.  lol

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Re: [gentoo-user] Are those "green" drives any good?

[Daniel Troeder]

I'm using big WD Caviar Green (WDxxEAxx) SATA HDDs for some years now in
my home 24/7 server, and haven't had any issues - they run cool and
low-noise, and the performance is good. Low power and heat was what was
important for me when choosing. HDD performance isn't an issue anyway,
when storing media files over a home network :)

Re: [gentoo-user] Are those "green" drives any good?

[Tanstaafl]

On 2012-05-09 4:47 AM, Dale <rdalek1967@gmail.com> wrote:
> As some know, I'm planning to buy me a LARGE hard drive to put all my
> videos on, eventually.  The prices are coming down now.  I keep seeing
> these "green" drives that are made by just about every company nowadays.
>   When comparing them to a non "green" drive, do they hold up as good?

As long as you don't use them in any kind of RAID setup you they should 
be fine.

The biggest difference between them and 'enterprise' class drives is the 
enterprise class drives are designed for multi-drive RAID setups... you 
don't want drives to spin down independently when working in a RAID setup...

Re: [gentoo-user] Are those "green" drives any good?

[Dale]

Daniel Troeder wrote:
> I'm using big WD Caviar Green (WDxxEAxx) SATA HDDs for some years now in
> my home 24/7 server, and haven't had any issues - they run cool and
> low-noise, and the performance is good. Low power and heat was what was
> important for me when choosing. HDD performance isn't an issue anyway,
> when storing media files over a home network :)
> 
> 



Sounds like these drives are going to be OK then.  My concern was that
they would be made "cheaper" and not be as reliable but it seems folks
are happy with them which is good.

I like WD drives.  The one drive I have had fail was a WD.  I have a few
of them so maybe it is just a bad apple or is it a lemon?  Anyway.

I'm getting quite a collection of videos and stuff.  I'm thinking 2Tb or
3Tb.  The 3Tb is more expensive but it will take longer to fill it up.
Decisions.  Decisions.  Maybe newegg will have a BIG sale soon.

While on the thread.  Has anyone had any sort of luck with the
recertified drives?  I see them sometimes and wonder what the deal is.
Are they repaired drives or just returned drives?  Anyone have any
experience, good or bad, with those?

Thanks for the replies.  Sounds good so far.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Re: [gentoo-user] Are those "green" drives any good?

[mike]

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

On 05/09/2012 07:47 AM, Tanstaafl wrote:
> As long as you don't use them in any kind of RAID setup you they should
> be fine.
> 
> The biggest difference between them and 'enterprise' class drives is the
> enterprise class drives are designed for multi-drive RAID setups... you
> don't want drives to spin down independently when working in a RAID
> setup...

AFAIK, the only technical difference between a consumer drive and an
enterprise one is that the enterprise one doesn't tell lies.  Or at
least, it isn't supposed to.

Consumer drives will acknowledge writes before they have hit the
platter, even if the cache is disabled on the drive (and some consumer
drives do not even allow the cache to be disabled).

The only scenario this seriously guards against is unexpected power
loss, where the drive has told the OS that the data has been written to
disk, but it is somewhere in-between (e.g., on cache, but not on the
platter) and then the power is disconnected from the unit (specifically,
the drive itself).  Even an unexpected reboot from the computer won't
affect this, unless the computer removes power to the device during
early boot (and on x86 systems, that is a virtual impossibility).

	--- Mike

-- 
A man who reasons deliberately, manages it better after studying Logic
than he could before, if he is sincere about it and has common sense.
                                   --- Carveth Read, “Logic”


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 729 bytes --]

Re: [gentoo-user] Are those "green" drives any good?

[Mark Knecht]

On Wed, May 9, 2012 at 4:47 AM, Tanstaafl <tanstaafl@libertytrek.org> wrote:
> On 2012-05-09 4:47 AM, Dale <rdalek1967@gmail.com> wrote:
>>
>> As some know, I'm planning to buy me a LARGE hard drive to put all my
>> videos on, eventually.  The prices are coming down now.  I keep seeing
>> these "green" drives that are made by just about every company nowadays.
>>  When comparing them to a non "green" drive, do they hold up as good?
>
>
> As long as you don't use them in any kind of RAID setup you they should be
> fine.
>
> The biggest difference between them and 'enterprise' class drives is the
> enterprise class drives are designed for multi-drive RAID setups... you
> don't want drives to spin down independently when working in a RAID setup...
>

+1

I use the WD 1TB Green drive for storing video outside my machine
using both USB & eSATA. Works fine. Very quite, cool. Way faster than
necessary for streaming movies. Nice.

As for RAID, +100 to not use them. The WD Green drives do not support
time-limited error recovery (TLER) and spin down based on their view
of trying to save power. For me anyway they simply didn't work well in
any RAID configuration. I switched my home compute server to
Enterprise drives which have worked perfectly for 2+ years.

HTH,
Mark

Re: [gentoo-user] Are those "green" drives any good?

[Volker Armin Hemmann]

Am Mittwoch, 9. Mai 2012, 03:47:09 schrieb Dale:
> Hi,
> 
> As some know, I'm planning to buy me a LARGE hard drive to put all my
> videos on, eventually.  The prices are coming down now.  I keep seeing
> these "green" drives that are made by just about every company nowadays.
>  When comparing them to a non "green" drive, do they hold up as good?
> Are they as dependable as a plain drive?  I guess they are more
> efficient and I get that but do they break quicker, more often or no
> difference?
> 
> I have noticed that they tend to spin slower and are cheaper.  That much
> I have figured out.  Other than that, I can't see any other difference.
>  Data speeds seem to be about the same.
> 
> Please, no brand wars.  I may get a WD, Maxtor, Samsung or some other
> brand.  I haven't picked that part yet.  So far, I have had good luck
> with drives.  I think I have one doorstop so far.  I have at least one
> of each of the brands above too.  Don't jinx me.  I'm sure someone has a
> horror story about some brand.
> 
> Thanks much.
> 
> Dale
> 
> :-)  :-)

samsung here. Put that beast into an esata case. Sometimes I forget to turn it 
off, because it is so silent. And cool. The others should be similar. They are 
slower, yes, but fast enough to watch video.

7200 for stuff that needs some speed.
5400 for video and backups.

just fine.

-- 
#163933

Re: [gentoo-user] Are those "green" drives any good?

[Tanstaafl]

On 2012-05-09 8:06 AM, mike@trausch.us <mike@trausch.us> wrote:
> AFAIK, the only technical difference between a consumer drive and an
> enterprise one is that the enterprise one doesn't tell lies.  Or at
> least, it isn't supposed to.

There's a bit more to it than that...

http://download.intel.com/support/motherboards/server/sb/enterprise_class_versus_desktop_class_hard_drives_.pdf

Re: [gentoo-user] Are those "green" drives any good?

[Pandu Poluan]

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

On May 9, 2012 7:36 PM, "Mark Knecht" <markknecht@gmail.com> wrote:
>
> As for RAID, +100 to not use them. The WD Green drives do not support
> time-limited error recovery (TLER) and spin down based on their view
> of trying to save power. For me anyway they simply didn't work well in
> any RAID configuration. I switched my home compute server to
> Enterprise drives which have worked perfectly for 2+ years.
>

I can understand how 'green' drives can fcuk up hardware RAID arrays.

But what about software RAID, e.g., dmraid? Can't we just configure it to
be 'more forgiving'?

Rgds,

[-- Attachment #2: Type: text/html, Size: 756 bytes --]

Re: [gentoo-user] Are those "green" drives any good?

[Mark Knecht]

On Wed, May 9, 2012 at 9:39 AM, Pandu Poluan <pandu@poluan.info> wrote:
>
> On May 9, 2012 7:36 PM, "Mark Knecht" <markknecht@gmail.com> wrote:
>>
>> As for RAID, +100 to not use them. The WD Green drives do not support
>> time-limited error recovery (TLER) and spin down based on their view
>> of trying to save power. For me anyway they simply didn't work well in
>> any RAID configuration. I switched my home compute server to
>> Enterprise drives which have worked perfectly for 2+ years.
>>
>
> I can understand how 'green' drives can fcuk up hardware RAID arrays.
>
> But what about software RAID, e.g., dmraid? Can't we just configure it to be
> 'more forgiving'?
>
> Rgds,

Possibly. Someone with more experience with mdadm probably could do a
better job but I'd never done RAID of any type at that time (I'm just
a home user who taught myself whatever little I know about Linux
through this list) and built this server with 5 drives to run a number
of Windows VMs so I was pretty sure I wanted RAID. I bought the WD
Green 1TB drives a little over 2 years ago and had multiple problems.
First problem was the 4K sector size issue which was fairly new at
that time, and then once I got past that I tried RAID and it still
didn't work well at all.

The best answer at the time was some piece of low level software from
WD called something like wdtwiddle or something silly as I remember it
but I decided to cut my storage in half and replaced the 1TB Green
drives with 500GB Enterprise drives.

Since then I've heard of people using Green drives for RAID and doing
fine but it didn't work with the ones I purchased.

- Mark

Re: [gentoo-user] Are those "green" drives any good?

[Paul Hartman]

On Wed, May 9, 2012 at 12:28 PM, Mark Knecht <markknecht@gmail.com> wrote:
> The best answer at the time was some piece of low level software from
> WD called something like wdtwiddle or something

WDTLER  :)

Re: [gentoo-user] Are those "green" drives any good?

[Mark Knecht]

On Wed, May 9, 2012 at 11:42 AM, Paul Hartman
<paul.hartman+gentoo@gmail.com> wrote:
> On Wed, May 9, 2012 at 12:28 PM, Mark Knecht <markknecht@gmail.com> wrote:
>> The best answer at the time was some piece of low level software from
>> WD called something like wdtwiddle or something
>
> WDTLER  :)
>

Hey, I wasn't that far off! ;-)

Re: [gentoo-user] Are those "green" drives any good?

[Alan McKinnon]

On Wed, 09 May 2012 04:52:57 -0500
Dale <rdalek1967@gmail.com> wrote:

> I was thinking the same thing about the speed and them lasting longer
> because of the slower speed.  I mean, it's less wear and less heat.
> I'd just hate to buy one and it be a piece of junk or something else I
> wasn't expecting to be wrong.   I wish I could afford server grade.
> Weeeeee!!

My thoughts these days is that nobody really makes a bad drive anymore.
Like cars[1], they're all good and do what it says on the box. Same
with bikes[2].

A manufacturer may have some bad luck and a product range is less than
perfect, but even that is quite rare and most stuff ups can be fixed
with new firmware. So it's all good.

For video, I would advise you invest in gobs and gobs of RAM (the stuff
is dirt cheap these days). Have more RAM than the biggest video you
will watch (so go for 8G minimum) and the entire video will fit in
memory = read the disc once and watch.

Funny lags in video just go away. That's what I did with my HP
MicroServers - maxed out the RAM to 8G and bought 4 x 3T WD 5400
drives. It runs FreeNAS (built on FreeBSD) with ZFS = shove the drives
in and let them software figure out what the blazes to do. Over the
years I've gotten sick and tired of pampering with disk arrays and
treating them like fragile china that must be molly-coddled. What I
want is lots of storage that will mail me when it detects issues.

-- 
Alan McKinnnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Are those "green" drives any good?

[Dale]

Alan McKinnon wrote:
> On Wed, 09 May 2012 04:52:57 -0500
> Dale <rdalek1967@gmail.com> wrote:
> 
>> I was thinking the same thing about the speed and them lasting longer
>> because of the slower speed.  I mean, it's less wear and less heat.
>> I'd just hate to buy one and it be a piece of junk or something else I
>> wasn't expecting to be wrong.   I wish I could afford server grade.
>> Weeeeee!!
> 
> My thoughts these days is that nobody really makes a bad drive anymore.
> Like cars[1], they're all good and do what it says on the box. Same
> with bikes[2].
> 
> A manufacturer may have some bad luck and a product range is less than
> perfect, but even that is quite rare and most stuff ups can be fixed
> with new firmware. So it's all good.


That's my thoughts too.  It doesn't matter what brand you go with, they
all have some sort of failure at some point.  They are not built to last
forever and there is always the random failure, even when a week old.
It's usually the loss of important data and not having a backup that
makes it sooooo bad.  I'm not real picky on brand as long as it is a
company I have heard of.

Now if someone posts that there is a bad design for some set of drives,
I would avoid that.  If there are people that have a unusual high
failure rate then maybe an exception to the rule is needed.  That's rare
tho.  Anyone want to buy a Yugo for full price?  lol  I wouldn't.


> 
> For video, I would advise you invest in gobs and gobs of RAM (the stuff
> is dirt cheap these days). Have more RAM than the biggest video you
> will watch (so go for 8G minimum) and the entire video will fit in
> memory = read the disc once and watch.
> 
> Funny lags in video just go away. That's what I did with my HP
> MicroServers - maxed out the RAM to 8G and bought 4 x 3T WD 5400
> drives. It runs FreeNAS (built on FreeBSD) with ZFS = shove the drives
> in and let them software figure out what the blazes to do. Over the
> years I've gotten sick and tired of pampering with disk arrays and
> treating them like fragile china that must be molly-coddled. What I
> want is lots of storage that will mail me when it detects issues.
> 


I got that beat a long time ago.  I started out with 4Gbs originally.  I
found out that a 64 bit OS uses a bit more memory so, I got another
4Gbs.  Then newegg had a sale on a pair of 4gb sticks and I got them.
I'm at 16Gbs right now.  I need to ramp up drive space to match up with
my memory space.  I'm maxed out on ram but I got SATA ports that are
empty.   We can't have that can we?   lol

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Re: [gentoo-user] Are those "green" drives any good?

[Dale]

Volker Armin Hemmann wrote:
> Am Mittwoch, 9. Mai 2012, 03:47:09 schrieb Dale:
>> Hi,
>>
>> As some know, I'm planning to buy me a LARGE hard drive to put all my
>> videos on, eventually.  The prices are coming down now.  I keep seeing
>> these "green" drives that are made by just about every company nowadays.
>>  When comparing them to a non "green" drive, do they hold up as good?
>> Are they as dependable as a plain drive?  I guess they are more
>> efficient and I get that but do they break quicker, more often or no
>> difference?
>>
>> I have noticed that they tend to spin slower and are cheaper.  That much
>> I have figured out.  Other than that, I can't see any other difference.
>>  Data speeds seem to be about the same.
>>
>> Please, no brand wars.  I may get a WD, Maxtor, Samsung or some other
>> brand.  I haven't picked that part yet.  So far, I have had good luck
>> with drives.  I think I have one doorstop so far.  I have at least one
>> of each of the brands above too.  Don't jinx me.  I'm sure someone has a
>> horror story about some brand.
>>
>> Thanks much.
>>
>> Dale
>>
>> :-)  :-)
> 
> samsung here. Put that beast into an esata case. Sometimes I forget to turn it 
> off, because it is so silent. And cool. The others should be similar. They are 
> slower, yes, but fast enough to watch video.
> 
> 7200 for stuff that needs some speed.
> 5400 for video and backups.
> 
> just fine.
> 


My videos and such is on a Samsung 750Gb drive now.  I'm pretty sure it
is a 7200rpm drive tho.  My whole system is quiet.  I have a Cooler
Master HAF-932 case with those LARGE fans and you can't hear anything.
Even if I cut everything else off in this room, I can't hear the system
at all.  Let's keep in mind that I am getting older tho.  ;-)

One reason I am considering the green drives is that I can buy a larger
drive for about the same price.  I use LVM so I added a 250Gb drive to
the 750Gb to get 1Tb.  Thing is, I'll have that full to before to long.
 I need to go ahead and get a large drive.  Even a 2Tb drive will be
about half full if I transfer it all over.  Of course I'm keeping the
750Gb to tho.  Here is where I am with all drives in use.

/dev/mapper/data-data1  923G  619G  297G  68% /data

I start looking when I get to about 70% and by 85%, I want some hardware
or a plan to move things around or something.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Re: [gentoo-user] Are those "green" drives any good?

[Paul Hartman]

On Wed, May 9, 2012 at 5:24 PM, Dale <rdalek1967@gmail.com> wrote:
>  It doesn't matter what brand you go with

Especially true since there are only 2 companies actually making
consumer hard drives anymore: WD and Seagate. Both of them seem to
know what they are doing, for the most part...

Some hard drives fail at the beginning of their life. All hard drives
fail at the end of their life. :)

Re: [gentoo-user] Are those "green" drives any good?

[Mark Knecht]

On Wed, May 9, 2012 at 3:24 PM, Dale <rdalek1967@gmail.com> wrote:
> Alan McKinnon wrote:
<SNIP>
>> My thoughts these days is that nobody really makes a bad drive anymore.
>> Like cars[1], they're all good and do what it says on the box. Same
>> with bikes[2].
>>
>> A manufacturer may have some bad luck and a product range is less than
>> perfect, but even that is quite rare and most stuff ups can be fixed
>> with new firmware. So it's all good.
>
>
> That's my thoughts too.  It doesn't matter what brand you go with, they
> all have some sort of failure at some point.  They are not built to last
> forever and there is always the random failure, even when a week old.
> It's usually the loss of important data and not having a backup that
> makes it sooooo bad.  I'm not real picky on brand as long as it is a
> company I have heard of.
>

One thing to keep in mind is statistics. For a single drive by itself
it hardly matters anymore what you buy. You cannot predict the
failure. However if you buy multiple identical drives at the same time
then most likely you will either get all good drives or (possibly) a
bunch of drives that suffer from similar defects and all start failing
at the same point in their life cycle.  For RAID arrays it's
measurably best to buy drives that come from different manufacturing
lots, better from different factories, and maybe even from different
companies. Then, if a drive fails, assuming the failure is really the
fault of the drive and not some local issue like power sources or ESD
events, etc., it's less likely other drives in the box will fail at
the same time.

Cheers,
Mark

Re: [gentoo-user] Are those "green" drives any good?

[Dale]

Paul Hartman wrote:
> On Wed, May 9, 2012 at 5:24 PM, Dale <rdalek1967@gmail.com> wrote:
>>  It doesn't matter what brand you go with
> 
> Especially true since there are only 2 companies actually making
> consumer hard drives anymore: WD and Seagate. Both of them seem to
> know what they are doing, for the most part...
> 
> Some hard drives fail at the beginning of their life. All hard drives
> fail at the end of their life. :)
> 
> 


I'm about to show my age so please close your eyes.  Pretty please.  -_-

Way back in the stone age, there was a guy that released a curve for
electronics life.  The failure rate is high at the beginning, especially
for the first few minutes, then falls to about nothing, then after
several years it goes back up again.  At the beginning of the curve, the
thought was it could be a bad solder job, bad components or some other
problem.  At the other end was just when age kicked in.  Sweat spot is
in the middle.

I try to keep these things in mind.  Example.  I bought a TV a couple
years ago.  My old TV was about 20 years old and the power supply had
some sort of issue.  It was either a diode getting weak or a capacitor
was going bad.  It had the little sine waves going up the screen.  It
was hard to see but was visible when the screen was all the same colour.
  Age was creeping up on this thing.

Anyway, when my DirecTv box went out, it was years old too, I went to
get me a new one.  While there I saw this nice LCD TV sitting on a shelf
and I might add, it looked so lonesome.  lol  It was marked down about
half price.  Hmmm, was it repaired or what?  I asked a guy what the deal
was.  He said it was their display model.  My first thought was that
this could have already went through the first part of the curve.  So, I
asked how long it was on display.  He said about 9 or 10 months.  He
thinks I am buying used and I'm thinking that this thing has already
went through the bad part of its life.

I walked out with a $800 TV for about $400.  I think I got the better
deal myself.

Most of the drives, or other electronics, that I have either die under
warranty or die when I am past caring.  It has been a good long while
since I had to return anything under warranty.

I'm done showing my age, open your eyes again.  LOL

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Re: [gentoo-user] Are those "green" drives any good?

[Dale]

Mark Knecht wrote:
> On Wed, May 9, 2012 at 3:24 PM, Dale <rdalek1967@gmail.com> wrote:
>> Alan McKinnon wrote:
> <SNIP>
>>> My thoughts these days is that nobody really makes a bad drive anymore.
>>> Like cars[1], they're all good and do what it says on the box. Same
>>> with bikes[2].
>>>
>>> A manufacturer may have some bad luck and a product range is less than
>>> perfect, but even that is quite rare and most stuff ups can be fixed
>>> with new firmware. So it's all good.
>>
>>
>> That's my thoughts too.  It doesn't matter what brand you go with, they
>> all have some sort of failure at some point.  They are not built to last
>> forever and there is always the random failure, even when a week old.
>> It's usually the loss of important data and not having a backup that
>> makes it sooooo bad.  I'm not real picky on brand as long as it is a
>> company I have heard of.
>>
> 
> One thing to keep in mind is statistics. For a single drive by itself
> it hardly matters anymore what you buy. You cannot predict the
> failure. However if you buy multiple identical drives at the same time
> then most likely you will either get all good drives or (possibly) a
> bunch of drives that suffer from similar defects and all start failing
> at the same point in their life cycle.  For RAID arrays it's
> measurably best to buy drives that come from different manufacturing
> lots, better from different factories, and maybe even from different
> companies. Then, if a drive fails, assuming the failure is really the
> fault of the drive and not some local issue like power sources or ESD
> events, etc., it's less likely other drives in the box will fail at
> the same time.
> 
> Cheers,
> Mark
> 
> 



You make a good point too.  I had a headlight to go out on my car once
long ago.  I, not thinking, replaced them both since the new ones were
brighter.  Guess what, when one of the bulbs blew out, the other was out
VERY soon after.  Now, I replace them but NOT at the same time.  Keep in
mind, just like a hard drive, when one headlight is on, so is the other
one.  When we turn our computers on, all the drives spin up together so
they are basically all getting the same wear and tear effect.

I don't use RAID, except to kill bugs, but that is good advice.  People
who do use RAID would be wise to use it.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Re: [gentoo-user] Are those "green" drives any good?

[Pandu Poluan]

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

On May 10, 2012 6:54 AM, "Dale" <rdalek1967@gmail.com> wrote:
>
> Paul Hartman wrote:
> > On Wed, May 9, 2012 at 5:24 PM, Dale <rdalek1967@gmail.com> wrote:
> >>  It doesn't matter what brand you go with
> >
> > Especially true since there are only 2 companies actually making
> > consumer hard drives anymore: WD and Seagate. Both of them seem to
> > know what they are doing, for the most part...
> >
> > Some hard drives fail at the beginning of their life. All hard drives
> > fail at the end of their life. :)
> >
> >
>
>
> I'm about to show my age so please close your eyes.  Pretty please.  -_-
>
> Way back in the stone age, there was a guy that released a curve for
> electronics life.  The failure rate is high at the beginning, especially
> for the first few minutes, then falls to about nothing, then after
> several years it goes back up again.  At the beginning of the curve, the
> thought was it could be a bad solder job, bad components or some other
> problem.  At the other end was just when age kicked in.  Sweat spot is
> in the middle.
>
> I try to keep these things in mind.  Example.  I bought a TV a couple
> years ago.  My old TV was about 20 years old and the power supply had
> some sort of issue.  It was either a diode getting weak or a capacitor
> was going bad.  It had the little sine waves going up the screen.  It
> was hard to see but was visible when the screen was all the same colour.
>  Age was creeping up on this thing.
>
> Anyway, when my DirecTv box went out, it was years old too, I went to
> get me a new one.  While there I saw this nice LCD TV sitting on a shelf
> and I might add, it looked so lonesome.  lol  It was marked down about
> half price.  Hmmm, was it repaired or what?  I asked a guy what the deal
> was.  He said it was their display model.  My first thought was that
> this could have already went through the first part of the curve.  So, I
> asked how long it was on display.  He said about 9 or 10 months.  He
> thinks I am buying used and I'm thinking that this thing has already
> went through the bad part of its life.
>
> I walked out with a $800 TV for about $400.  I think I got the better
> deal myself.
>

Heeey, that's a good point! Now I know that buying display units might be
the best deal.

Thanks, again! I'll now be keeping an eye open for such deals ;-)

Rgds,

[-- Attachment #2: Type: text/html, Size: 2932 bytes --]

Re: [gentoo-user] Are those "green" drives any good?

[Adam Carter]

>> Way back in the stone age, there was a guy that released a curve for
>> electronics life.  The failure rate is high at the beginning, especially
>> for the first few minutes, then falls to about nothing, then after
>> several years it goes back up again.

That concept is much more general than just electronics;
https://en.wikipedia.org/wiki/Bathtub_curve

Re: [gentoo-user] Are those "green" drives any good?

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2897 bytes --]

On Thursday 10 May 2012 00:58:47 Dale wrote:
> Mark Knecht wrote:
> > On Wed, May 9, 2012 at 3:24 PM, Dale <rdalek1967@gmail.com> wrote:
> >> Alan McKinnon wrote:
> > <SNIP>
> > 
> >>> My thoughts these days is that nobody really makes a bad drive anymore.
> >>> Like cars[1], they're all good and do what it says on the box. Same
> >>> with bikes[2].
> >>> 
> >>> A manufacturer may have some bad luck and a product range is less than
> >>> perfect, but even that is quite rare and most stuff ups can be fixed
> >>> with new firmware. So it's all good.
> >> 
> >> That's my thoughts too.  It doesn't matter what brand you go with, they
> >> all have some sort of failure at some point.  They are not built to last
> >> forever and there is always the random failure, even when a week old.
> >> It's usually the loss of important data and not having a backup that
> >> makes it sooooo bad.  I'm not real picky on brand as long as it is a
> >> company I have heard of.
> > 
> > One thing to keep in mind is statistics. For a single drive by itself
> > it hardly matters anymore what you buy. You cannot predict the
> > failure. However if you buy multiple identical drives at the same time
> > then most likely you will either get all good drives or (possibly) a
> > bunch of drives that suffer from similar defects and all start failing
> > at the same point in their life cycle.  For RAID arrays it's
> > measurably best to buy drives that come from different manufacturing
> > lots, better from different factories, and maybe even from different
> > companies. Then, if a drive fails, assuming the failure is really the
> > fault of the drive and not some local issue like power sources or ESD
> > events, etc., it's less likely other drives in the box will fail at
> > the same time.
> > 
> > Cheers,
> > Mark
> 
> You make a good point too.  I had a headlight to go out on my car once
> long ago.  I, not thinking, replaced them both since the new ones were
> brighter.  Guess what, when one of the bulbs blew out, the other was out
> VERY soon after.  Now, I replace them but NOT at the same time.  Keep in
> mind, just like a hard drive, when one headlight is on, so is the other
> one.  When we turn our computers on, all the drives spin up together so
> they are basically all getting the same wear and tear effect.

Unless you're driving something out of the 60's before halogen bulbs came out, 
you didn't by any chance touched them with your greasy fingers - did you?  
Because that's a promoter of early failure (unequal temperature tension caused 
by impurities on the glass).

It's better to use a clean tissue or the foam wrapper they are packed in and 
take care not to touch them with your fingers at all.  Should you 
inadvertently do so, then you'll need to clean them with meths or similar 
degreaser.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Are those "green" drives any good?

[napalm]

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

On Wed, May 09, 2012 at 06:58:47PM -0500, Dale wrote:
> Mark Knecht wrote:
> > On Wed, May 9, 2012 at 3:24 PM, Dale <rdalek1967@gmail.com> wrote:
> >> Alan McKinnon wrote:
> > <SNIP>
> >>> My thoughts these days is that nobody really makes a bad drive anymore.
> >>> Like cars[1], they're all good and do what it says on the box. Same
> >>> with bikes[2].
> >>>
> >>> A manufacturer may have some bad luck and a product range is less than
> >>> perfect, but even that is quite rare and most stuff ups can be fixed
> >>> with new firmware. So it's all good.
> >>
> >>
> >> That's my thoughts too.  It doesn't matter what brand you go with, they
> >> all have some sort of failure at some point.  They are not built to last
> >> forever and there is always the random failure, even when a week old.
> >> It's usually the loss of important data and not having a backup that
> >> makes it sooooo bad.  I'm not real picky on brand as long as it is a
> >> company I have heard of.
> >>
> > 
> > One thing to keep in mind is statistics. For a single drive by itself
> > it hardly matters anymore what you buy. You cannot predict the
> > failure. However if you buy multiple identical drives at the same time
> > then most likely you will either get all good drives or (possibly) a
> > bunch of drives that suffer from similar defects and all start failing
> > at the same point in their life cycle.  For RAID arrays it's
> > measurably best to buy drives that come from different manufacturing
> > lots, better from different factories, and maybe even from different
> > companies. Then, if a drive fails, assuming the failure is really the
> > fault of the drive and not some local issue like power sources or ESD
> > events, etc., it's less likely other drives in the box will fail at
> > the same time.
> > 
> > Cheers,
> > Mark
> > 
> > 
> 
> 
> 
> You make a good point too.  I had a headlight to go out on my car once
> long ago.  I, not thinking, replaced them both since the new ones were
> brighter.  Guess what, when one of the bulbs blew out, the other was out
> VERY soon after.  Now, I replace them but NOT at the same time.  Keep in
> mind, just like a hard drive, when one headlight is on, so is the other
> one.  When we turn our computers on, all the drives spin up together so
> they are basically all getting the same wear and tear effect.
> 
> I don't use RAID, except to kill bugs, but that is good advice.  People
> who do use RAID would be wise to use it.
> 
> Dale
> 
> :-)  :-)
> 

hum hum!
I know that Windows does this by default (it annoys me so I disable it)
but does linux disable or stop running the disks if they're inactive?
I'm assuming there's an option somewhere - maybe just `unmount`!


[-- Attachment #2: Type: application/pgp-signature, Size: 316 bytes --]

Re: [gentoo-user] Are those "green" drives any good?

[Dale]

napalm@squareownz.org wrote:
> On Wed, May 09, 2012 at 06:58:47PM -0500, Dale wrote:
>> Mark Knecht wrote:
>>> On Wed, May 9, 2012 at 3:24 PM, Dale <rdalek1967@gmail.com> wrote:
>>>> Alan McKinnon wrote:
>>> <SNIP>
>>>>> My thoughts these days is that nobody really makes a bad drive anymore.
>>>>> Like cars[1], they're all good and do what it says on the box. Same
>>>>> with bikes[2].
>>>>>
>>>>> A manufacturer may have some bad luck and a product range is less than
>>>>> perfect, but even that is quite rare and most stuff ups can be fixed
>>>>> with new firmware. So it's all good.
>>>>
>>>>
>>>> That's my thoughts too.  It doesn't matter what brand you go with, they
>>>> all have some sort of failure at some point.  They are not built to last
>>>> forever and there is always the random failure, even when a week old.
>>>> It's usually the loss of important data and not having a backup that
>>>> makes it sooooo bad.  I'm not real picky on brand as long as it is a
>>>> company I have heard of.
>>>>
>>>
>>> One thing to keep in mind is statistics. For a single drive by itself
>>> it hardly matters anymore what you buy. You cannot predict the
>>> failure. However if you buy multiple identical drives at the same time
>>> then most likely you will either get all good drives or (possibly) a
>>> bunch of drives that suffer from similar defects and all start failing
>>> at the same point in their life cycle.  For RAID arrays it's
>>> measurably best to buy drives that come from different manufacturing
>>> lots, better from different factories, and maybe even from different
>>> companies. Then, if a drive fails, assuming the failure is really the
>>> fault of the drive and not some local issue like power sources or ESD
>>> events, etc., it's less likely other drives in the box will fail at
>>> the same time.
>>>
>>> Cheers,
>>> Mark
>>>
>>>
>>
>>
>>
>> You make a good point too.  I had a headlight to go out on my car once
>> long ago.  I, not thinking, replaced them both since the new ones were
>> brighter.  Guess what, when one of the bulbs blew out, the other was out
>> VERY soon after.  Now, I replace them but NOT at the same time.  Keep in
>> mind, just like a hard drive, when one headlight is on, so is the other
>> one.  When we turn our computers on, all the drives spin up together so
>> they are basically all getting the same wear and tear effect.
>>
>> I don't use RAID, except to kill bugs, but that is good advice.  People
>> who do use RAID would be wise to use it.
>>
>> Dale
>>
>> :-)  :-)
>>
> 
> hum hum!
> I know that Windows does this by default (it annoys me so I disable it)
> but does linux disable or stop running the disks if they're inactive?
> I'm assuming there's an option somewhere - maybe just `unmount`!
> 


The default is to keep them all running and to not spin them down.  I
have never had a Linux OS to spin down a drive unless I set/told it to.
 You can do this tho.  The command and option is:

hdparm -S /dev/sdX

X would be the drive number.  There is also the -s option but it is not
recommended.

There is also the -y and -Y options.  Before using ANY of these, read
the man page.  Each one has it uses and you need to know for sure which
one does what you want.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Re: [gentoo-user] Are those "green" drives any good?

[Todd Goodman]

* Dale <rdalek1967@gmail.com> [120509 19:54]:
[..]
> Way back in the stone age, there was a guy that released a curve for
> electronics life.  The failure rate is high at the beginning, especially
> for the first few minutes, then falls to about nothing, then after
> several years it goes back up again.  At the beginning of the curve, the
> thought was it could be a bad solder job, bad components or some other
> problem.  At the other end was just when age kicked in.  Sweat spot is
> in the middle.

C. Gordon Bell has that curve in his book "Computer Engineering."

Available online at:

http://research.microsoft.com/en-us/um/people/gbell/Computer_Engineering/index.html

for HTML and:

http://research.microsoft.com/en-us/um/people/gbell/CGB%20Files/Computer%20Engineering%207809%20c.pdf

for the PDF.

Todd

Re: [gentoo-user] Are those "green" drives any good?

[napalm]

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

On Thu, May 10, 2012 at 07:38:34AM -0500, Dale wrote:
> 
> The default is to keep them all running and to not spin them down.  I
> have never had a Linux OS to spin down a drive unless I set/told it to.
>  You can do this tho.  The command and option is:
> 
> hdparm -S /dev/sdX
> 
> X would be the drive number.  There is also the -s option but it is not
> recommended.
> 
> There is also the -y and -Y options.  Before using ANY of these, read
> the man page.  Each one has it uses and you need to know for sure which
> one does what you want.
> 
> Dale
> 

Awesome thanks very much, if I need to power down one of my drives I
shall use hdparam!

Does the kernel keep even unmounted drives spinning by default?

Thank you Dale!

[-- Attachment #2: Type: application/pgp-signature, Size: 316 bytes --]

[gentoo-user] make of gentoo-sources-3.2.12 fails

[Michael Scherer]

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

Hi all,

after downloading the 3.2.12-sources everything went fine
for a couple of weeks, I compiled them a couple of times,
but suddenly, maybe because of some world-updates, errors
started to accumulate, first it could do make but no modules,
then kernel make made it almost and now I'm stuck with this
rather short make output:

  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  HOSTCC  scripts/kconfig/zconf.tab.o
scripts/kconfig/zconf.tab.c: In function ‘header_print_comment’:
scripts/kconfig/confdata.c:540:10: warning: ignoring return value of
  ‘fwrite’, declared with attribute warn_unused_result
  scripts/kconfig/zconf.tab.c: In function ‘kconfig_print_comment’:
  scripts/kconfig/confdata.c:467:10: warning: ignoring return value of
  ‘fwrite’, declared with attribute warn_unused_result HOSTLD
  scripts/kconfig/conf scripts/kconfig/conf --silentoldconfig Kconfig
  CHK     include/linux/version.h CHK     include/generated/utsrelease.h
  CC      kernel/bounds.s
  GEN     include/generated/bounds.h
  CC      arch/x86/kernel/asm-offsets.s
  GEN     include/generated/asm-offsets.h
  CALL    scripts/checksyscalls.sh
  CC      scripts/mod/empty.o
  HOSTCC  scripts/mod/mk_elfconfig
  MKELF   scripts/mod/elfconfig.h
  HOSTCC  scripts/mod/file2alias.o
  HOSTCC  scripts/mod/modpost.o
  HOSTCC  scripts/mod/sumversion.o
  HOSTLD  scripts/mod/modpost
  HOSTCC  scripts/kallsyms
  HOSTCC  scripts/pnmtologo
  HOSTCC  scripts/conmakehash
  HOSTCC  scripts/bin2c
  CC      init/main.o
  CHK     include/generated/compile.h
  CC      init/version.o
  CC      init/do_mounts.o
  CC      init/do_mounts_initrd.o
  LD      init/mounts.o
ls -Al -m elf_x86_64 -r -o init/mounts.o init/do_mounts.o
  init/do_mounts_initrd.o init/mounts.o: No such file or directory
make[1]: *** [init/mounts.o] Error 1
make: *** [init] Error 2

glibc is 2.14.1-r3, which otherwise works perfectly, so I don't
think it's the reason.
I cleared ccache and rebuilt the kernel sources, to no avail.

.config is in attachments.

Maybe someone could give me a hint, I need that kernel really
badly and hopefully soon.

kind regards

michael


[-- Attachment #2: config-3.2.12-gentoo --]
[-- Type: application/octet-stream, Size: 67566 bytes --]

#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 3.2.12-gentoo Kernel Configuration
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_ARCH_CLOCKSOURCE_DATA=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_CPU_IDLE_WAIT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_DEFAULT_IDLE=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ZONE_DMA32=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_AUDIT_ARCH=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_X86_64_SMP=y
CONFIG_X86_HT=y
CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11"
# CONFIG_KTIME_SCALAR is not set
CONFIG_ARCH_CPU_PROBE_RELEASE=y
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_HAVE_IRQ_WORK=y
CONFIG_IRQ_WORK=y

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
CONFIG_DEFAULT_HOSTNAME="(none)"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
# CONFIG_POSIX_MQUEUE is not set
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
# CONFIG_FHANDLE is not set
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
CONFIG_AUDIT=y
# CONFIG_AUDITSYSCALL is not set
CONFIG_HAVE_GENERIC_HARDIRQS=y

#
# IRQ subsystem
#
CONFIG_GENERIC_HARDIRQS=y
CONFIG_HAVE_SPARSE_IRQ=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y

#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_PREEMPT_RCU is not set
# CONFIG_RCU_TRACE is not set
CONFIG_RCU_FANOUT=64
# CONFIG_RCU_FANOUT_EXACT is not set
# CONFIG_TREE_RCU_TRACE is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=18
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
# CONFIG_CGROUPS is not set
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
# CONFIG_USER_NS is not set
CONFIG_PID_NS=y
CONFIG_NET_NS=y
# CONFIG_SCHED_AUTOGROUP is not set
# CONFIG_SYSFS_DEPRECATED is not set
# CONFIG_RELAY is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_RD_XZ=y
CONFIG_RD_LZO=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
# CONFIG_EXPERT is not set
CONFIG_UID16=y
# CONFIG_SYSCTL_SYSCALL is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_PCSPKR_PLATFORM=y
CONFIG_HAVE_PCSPKR_PLATFORM=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
# CONFIG_EMBEDDED is not set
CONFIG_HAVE_PERF_EVENTS=y

#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
# CONFIG_PERF_COUNTERS is not set
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_PCI_QUIRKS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not set
CONFIG_SLUB=y
# CONFIG_PROFILING is not set
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
CONFIG_JUMP_LABEL=y
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_HAVE_IOREMAP_PROT=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_OPTPROBES=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_ATTRS=y
CONFIG_USE_GENERIC_SMP_HELPERS=y
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
CONFIG_HAVE_DMA_API_DEBUG=y
CONFIG_HAVE_HW_BREAKPOINT=y
CONFIG_HAVE_MIXED_BREAKPOINTS_REGS=y
CONFIG_HAVE_USER_RETURN_NOTIFIER=y
CONFIG_HAVE_PERF_EVENTS_NMI=y
CONFIG_HAVE_ARCH_JUMP_LABEL=y
CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=y

#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
# CONFIG_HAVE_GENERIC_DMA_COHERENT is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_BLK_DEV_BSG=y
CONFIG_BLK_DEV_BSGLIB=y
# CONFIG_BLK_DEV_INTEGRITY is not set
CONFIG_BLOCK_COMPAT=y

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
# CONFIG_IOSCHED_DEADLINE is not set
CONFIG_IOSCHED_CFQ=y
CONFIG_DEFAULT_CFQ=y
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="cfq"
# CONFIG_INLINE_SPIN_TRYLOCK is not set
# CONFIG_INLINE_SPIN_TRYLOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK is not set
# CONFIG_INLINE_SPIN_LOCK_BH is not set
# CONFIG_INLINE_SPIN_LOCK_IRQ is not set
# CONFIG_INLINE_SPIN_LOCK_IRQSAVE is not set
CONFIG_INLINE_SPIN_UNLOCK=y
# CONFIG_INLINE_SPIN_UNLOCK_BH is not set
CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
# CONFIG_INLINE_SPIN_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_READ_TRYLOCK is not set
# CONFIG_INLINE_READ_LOCK is not set
# CONFIG_INLINE_READ_LOCK_BH is not set
# CONFIG_INLINE_READ_LOCK_IRQ is not set
# CONFIG_INLINE_READ_LOCK_IRQSAVE is not set
CONFIG_INLINE_READ_UNLOCK=y
# CONFIG_INLINE_READ_UNLOCK_BH is not set
CONFIG_INLINE_READ_UNLOCK_IRQ=y
# CONFIG_INLINE_READ_UNLOCK_IRQRESTORE is not set
# CONFIG_INLINE_WRITE_TRYLOCK is not set
# CONFIG_INLINE_WRITE_LOCK is not set
# CONFIG_INLINE_WRITE_LOCK_BH is not set
# CONFIG_INLINE_WRITE_LOCK_IRQ is not set
# CONFIG_INLINE_WRITE_LOCK_IRQSAVE is not set
CONFIG_INLINE_WRITE_UNLOCK=y
# CONFIG_INLINE_WRITE_UNLOCK_BH is not set
CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
# CONFIG_INLINE_WRITE_UNLOCK_IRQRESTORE is not set
CONFIG_MUTEX_SPIN_ON_OWNER=y
# CONFIG_FREEZER is not set

#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
# CONFIG_NO_HZ is not set
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y
CONFIG_SMP=y
# CONFIG_X86_MPPARSE is not set
# CONFIG_X86_EXTENDED_PLATFORM is not set
CONFIG_X86_SUPPORTS_MEMORY_FAILURE=y
# CONFIG_SCHED_OMIT_FRAME_POINTER is not set
# CONFIG_PARAVIRT_GUEST is not set
CONFIG_NO_BOOTMEM=y
# CONFIG_MEMTEST is not set
CONFIG_MK8=y
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_MATOM is not set
# CONFIG_GENERIC_CPU is not set
CONFIG_X86_INTERNODE_CACHE_SHIFT=7
CONFIG_X86_CMPXCHG=y
CONFIG_CMPXCHG_LOCAL=y
CONFIG_CMPXCHG_DOUBLE=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_XADD=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_TSC=y
CONFIG_X86_CMPXCHG64=y
CONFIG_X86_CMOV=y
CONFIG_X86_MINIMUM_CPU_FAMILY=64
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_CPU_SUP_AMD=y
CONFIG_CPU_SUP_CENTAUR=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_DMI=y
CONFIG_GART_IOMMU=y
# CONFIG_CALGARY_IOMMU is not set
CONFIG_SWIOTLB=y
CONFIG_IOMMU_HELPER=y
# CONFIG_MAXSMP is not set
CONFIG_NR_CPUS=3
# CONFIG_SCHED_SMT is not set
# CONFIG_SCHED_MC is not set
# CONFIG_IRQ_TIME_ACCOUNTING is not set
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
# CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS is not set
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_INTEL is not set
CONFIG_X86_MCE_AMD=y
CONFIG_X86_MCE_THRESHOLD=y
# CONFIG_X86_MCE_INJECT is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
CONFIG_ARCH_PHYS_ADDR_T_64BIT=y
CONFIG_ARCH_DMA_ADDR_T_64BIT=y
CONFIG_DIRECT_GBPAGES=y
CONFIG_NUMA=y
CONFIG_AMD_NUMA=y
CONFIG_X86_64_ACPI_NUMA=y
CONFIG_NODES_SPAN_OTHER_NODES=y
# CONFIG_NUMA_EMU is not set
CONFIG_NODES_SHIFT=6
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_DEFAULT=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_PROC_KCORE_TEXT=y
CONFIG_ILLEGAL_POINTER_VALUE=0xdead000000000000
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_SPARSEMEM_MANUAL=y
CONFIG_SPARSEMEM=y
CONFIG_NEED_MULTIPLE_NODES=y
CONFIG_HAVE_MEMORY_PRESENT=y
CONFIG_SPARSEMEM_EXTREME=y
CONFIG_SPARSEMEM_VMEMMAP_ENABLE=y
CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER=y
CONFIG_SPARSEMEM_VMEMMAP=y
CONFIG_HAVE_MEMBLOCK=y
# CONFIG_MEMORY_HOTPLUG is not set
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_COMPACTION=y
CONFIG_MIGRATION=y
CONFIG_PHYS_ADDR_T_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_KSM=y
CONFIG_DEFAULT_MMAP_MIN_ADDR=65536
CONFIG_ARCH_SUPPORTS_MEMORY_FAILURE=y
# CONFIG_MEMORY_FAILURE is not set
CONFIG_TRANSPARENT_HUGEPAGE=y
# CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS is not set
CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y
CONFIG_CLEANCACHE=y
# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set
CONFIG_X86_RESERVE_LOW=64
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=7
CONFIG_X86_PAT=y
CONFIG_ARCH_USES_PG_UNCACHED=y
CONFIG_ARCH_RANDOM=y
CONFIG_EFI=y
CONFIG_SECCOMP=y
CONFIG_CC_STACKPROTECTOR=y
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
# CONFIG_HZ_300 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
CONFIG_SCHED_HRTICK=y
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x1000000
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_ALIGN=0x1000000
CONFIG_HOTPLUG_CPU=y
# CONFIG_COMPAT_VDSO is not set
# CONFIG_CMDLINE_BOOL is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_USE_PERCPU_NUMA_NODE_ID=y

#
# Power management and ACPI options
#
# CONFIG_SUSPEND is not set
# CONFIG_HIBERNATION is not set
# CONFIG_PM_RUNTIME is not set
CONFIG_ACPI=y
# CONFIG_ACPI_PROCFS is not set
# CONFIG_ACPI_PROCFS_POWER is not set
# CONFIG_ACPI_EC_DEBUGFS is not set
# CONFIG_ACPI_PROC_EVENT is not set
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
# CONFIG_ACPI_DOCK is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_HOTPLUG_CPU=y
# CONFIG_ACPI_PROCESSOR_AGGREGATOR is not set
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_NUMA=y
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
# CONFIG_ACPI_PCI_SLOT is not set
CONFIG_X86_PM_TIMER=y
CONFIG_ACPI_CONTAINER=y
# CONFIG_ACPI_SBS is not set
# CONFIG_ACPI_HED is not set
# CONFIG_ACPI_CUSTOM_METHOD is not set
# CONFIG_ACPI_APEI is not set
# CONFIG_SFI is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
CONFIG_CPU_IDLE=y
CONFIG_CPU_IDLE_GOV_LADDER=y
# CONFIG_INTEL_IDLE is not set

#
# Memory power savings
#
# CONFIG_I7300_IDLE is not set

#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
# CONFIG_PCI_CNB20LE_QUIRK is not set
CONFIG_PCIEPORTBUS=y
CONFIG_PCIEAER=y
# CONFIG_PCIE_ECRC is not set
# CONFIG_PCIEAER_INJECT is not set
CONFIG_PCIEASPM=y
# CONFIG_PCIEASPM_DEBUG is not set
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
# CONFIG_PCI_DEBUG is not set
# CONFIG_PCI_STUB is not set
CONFIG_HT_IRQ=y
CONFIG_PCI_ATS=y
CONFIG_PCI_IOV=y
# CONFIG_PCI_PRI is not set
# CONFIG_PCI_PASID is not set
CONFIG_PCI_IOAPIC=y
CONFIG_PCI_LABEL=y
CONFIG_ISA_DMA_API=y
CONFIG_AMD_NB=y
CONFIG_PCCARD=y
CONFIG_PCMCIA=y
CONFIG_PCMCIA_LOAD_CIS=y
CONFIG_CARDBUS=y

#
# PC-card bridges
#
CONFIG_YENTA=y
CONFIG_YENTA_O2=y
CONFIG_YENTA_RICOH=y
CONFIG_YENTA_TI=y
CONFIG_YENTA_ENE_TUNE=y
CONFIG_YENTA_TOSHIBA=y
# CONFIG_PD6729 is not set
# CONFIG_I82092 is not set
CONFIG_PCCARD_NONSTATIC=y
# CONFIG_HOTPLUG_PCI is not set
# CONFIG_RAPIDIO is not set

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
CONFIG_COMPAT_BINFMT_ELF=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
# CONFIG_HAVE_AOUT is not set
CONFIG_BINFMT_MISC=y
CONFIG_IA32_EMULATION=y
CONFIG_IA32_AOUT=y
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
CONFIG_SYSVIPC_COMPAT=y
CONFIG_HAVE_TEXT_POKE_SMP=y
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=y
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
CONFIG_XFRM_IPCOMP=y
CONFIG_NET_KEY=y
# CONFIG_NET_KEY_MIGRATE is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
# CONFIG_IP_FIB_TRIE_STATS is not set
# CONFIG_IP_MULTIPLE_TABLES is not set
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
# CONFIG_IP_PNP_BOOTP is not set
CONFIG_IP_PNP_RARP=y
CONFIG_NET_IPIP=y
CONFIG_NET_IPGRE_DEMUX=y
CONFIG_NET_IPGRE=y
# CONFIG_NET_IPGRE_BROADCAST is not set
CONFIG_IP_MROUTE=y
# CONFIG_IP_MROUTE_MULTIPLE_TABLES is not set
# CONFIG_IP_PIMSM_V1 is not set
# CONFIG_IP_PIMSM_V2 is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
CONFIG_INET_AH=y
CONFIG_INET_ESP=y
CONFIG_INET_IPCOMP=y
CONFIG_INET_XFRM_TUNNEL=y
CONFIG_INET_TUNNEL=y
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
CONFIG_INET_LRO=y
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
# CONFIG_IPV6 is not set
# CONFIG_NETLABEL is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETWORK_PHY_TIMESTAMPING is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_NETFILTER_ADVANCED=y

#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_NETLINK=y
# CONFIG_NETFILTER_NETLINK_QUEUE is not set
CONFIG_NETFILTER_NETLINK_LOG=y
CONFIG_NF_CONNTRACK=y
# CONFIG_NF_CONNTRACK_MARK is not set
# CONFIG_NF_CONNTRACK_EVENTS is not set
# CONFIG_NF_CONNTRACK_TIMESTAMP is not set
# CONFIG_NF_CT_PROTO_DCCP is not set
CONFIG_NF_CT_PROTO_GRE=y
# CONFIG_NF_CT_PROTO_SCTP is not set
# CONFIG_NF_CT_PROTO_UDPLITE is not set
# CONFIG_NF_CONNTRACK_AMANDA is not set
CONFIG_NF_CONNTRACK_FTP=y
# CONFIG_NF_CONNTRACK_H323 is not set
CONFIG_NF_CONNTRACK_IRC=y
CONFIG_NF_CONNTRACK_BROADCAST=y
CONFIG_NF_CONNTRACK_NETBIOS_NS=y
# CONFIG_NF_CONNTRACK_SNMP is not set
CONFIG_NF_CONNTRACK_PPTP=y
# CONFIG_NF_CONNTRACK_SANE is not set
CONFIG_NF_CONNTRACK_SIP=y
# CONFIG_NF_CONNTRACK_TFTP is not set
CONFIG_NF_CT_NETLINK=y
# CONFIG_NETFILTER_TPROXY is not set
CONFIG_NETFILTER_XTABLES=y

#
# Xtables combined modules
#
# CONFIG_NETFILTER_XT_MARK is not set
# CONFIG_NETFILTER_XT_CONNMARK is not set

#
# Xtables targets
#
# CONFIG_NETFILTER_XT_TARGET_AUDIT is not set
# CONFIG_NETFILTER_XT_TARGET_CHECKSUM is not set
# CONFIG_NETFILTER_XT_TARGET_CLASSIFY is not set
# CONFIG_NETFILTER_XT_TARGET_CONNMARK is not set
# CONFIG_NETFILTER_XT_TARGET_DSCP is not set
# CONFIG_NETFILTER_XT_TARGET_HL is not set
# CONFIG_NETFILTER_XT_TARGET_IDLETIMER is not set
# CONFIG_NETFILTER_XT_TARGET_MARK is not set
CONFIG_NETFILTER_XT_TARGET_NFLOG=y
# CONFIG_NETFILTER_XT_TARGET_NFQUEUE is not set
# CONFIG_NETFILTER_XT_TARGET_RATEEST is not set
# CONFIG_NETFILTER_XT_TARGET_TEE is not set
CONFIG_NETFILTER_XT_TARGET_TCPMSS=y
# CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP is not set

#
# Xtables matches
#
# CONFIG_NETFILTER_XT_MATCH_ADDRTYPE is not set
# CONFIG_NETFILTER_XT_MATCH_CLUSTER is not set
# CONFIG_NETFILTER_XT_MATCH_COMMENT is not set
# CONFIG_NETFILTER_XT_MATCH_CONNBYTES is not set
# CONFIG_NETFILTER_XT_MATCH_CONNLIMIT is not set
# CONFIG_NETFILTER_XT_MATCH_CONNMARK is not set
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y
# CONFIG_NETFILTER_XT_MATCH_CPU is not set
# CONFIG_NETFILTER_XT_MATCH_DCCP is not set
# CONFIG_NETFILTER_XT_MATCH_DEVGROUP is not set
# CONFIG_NETFILTER_XT_MATCH_DSCP is not set
# CONFIG_NETFILTER_XT_MATCH_ESP is not set
# CONFIG_NETFILTER_XT_MATCH_HASHLIMIT is not set
# CONFIG_NETFILTER_XT_MATCH_HELPER is not set
# CONFIG_NETFILTER_XT_MATCH_HL is not set
# CONFIG_NETFILTER_XT_MATCH_IPRANGE is not set
# CONFIG_NETFILTER_XT_MATCH_LENGTH is not set
# CONFIG_NETFILTER_XT_MATCH_LIMIT is not set
# CONFIG_NETFILTER_XT_MATCH_MAC is not set
# CONFIG_NETFILTER_XT_MATCH_MARK is not set
# CONFIG_NETFILTER_XT_MATCH_MULTIPORT is not set
# CONFIG_NETFILTER_XT_MATCH_OSF is not set
# CONFIG_NETFILTER_XT_MATCH_OWNER is not set
CONFIG_NETFILTER_XT_MATCH_POLICY=y
# CONFIG_NETFILTER_XT_MATCH_PKTTYPE is not set
# CONFIG_NETFILTER_XT_MATCH_QUOTA is not set
# CONFIG_NETFILTER_XT_MATCH_RATEEST is not set
# CONFIG_NETFILTER_XT_MATCH_REALM is not set
# CONFIG_NETFILTER_XT_MATCH_RECENT is not set
# CONFIG_NETFILTER_XT_MATCH_SCTP is not set
CONFIG_NETFILTER_XT_MATCH_STATE=y
# CONFIG_NETFILTER_XT_MATCH_STATISTIC is not set
# CONFIG_NETFILTER_XT_MATCH_STRING is not set
# CONFIG_NETFILTER_XT_MATCH_TCPMSS is not set
# CONFIG_NETFILTER_XT_MATCH_TIME is not set
# CONFIG_NETFILTER_XT_MATCH_U32 is not set
# CONFIG_IP_SET is not set
# CONFIG_IP_VS is not set

#
# IP: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV4=y
CONFIG_NF_CONNTRACK_IPV4=y
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=y
CONFIG_IP_NF_MATCH_AH=y
CONFIG_IP_NF_MATCH_ECN=y
# CONFIG_IP_NF_MATCH_TTL is not set
CONFIG_IP_NF_FILTER=y
CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_NF_TARGET_LOG=y
CONFIG_IP_NF_TARGET_ULOG=y
CONFIG_NF_NAT=y
CONFIG_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=y
# CONFIG_IP_NF_TARGET_NETMAP is not set
CONFIG_IP_NF_TARGET_REDIRECT=y
CONFIG_NF_NAT_PROTO_GRE=y
CONFIG_NF_NAT_FTP=y
CONFIG_NF_NAT_IRC=y
# CONFIG_NF_NAT_TFTP is not set
# CONFIG_NF_NAT_AMANDA is not set
CONFIG_NF_NAT_PPTP=y
# CONFIG_NF_NAT_H323 is not set
CONFIG_NF_NAT_SIP=y
CONFIG_IP_NF_MANGLE=y
# CONFIG_IP_NF_TARGET_CLUSTERIP is not set
# CONFIG_IP_NF_TARGET_ECN is not set
# CONFIG_IP_NF_TARGET_TTL is not set
# CONFIG_IP_NF_RAW is not set
# CONFIG_IP_NF_SECURITY is not set
# CONFIG_IP_NF_ARPTABLES is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_RDS is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
CONFIG_L2TP=y
# CONFIG_L2TP_DEBUGFS is not set
# CONFIG_L2TP_V3 is not set
# CONFIG_BRIDGE is not set
# CONFIG_NET_DSA is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_PHONET is not set
# CONFIG_IEEE802154 is not set
CONFIG_NET_SCHED=y

#
# Queueing/Scheduling
#
# CONFIG_NET_SCH_CBQ is not set
# CONFIG_NET_SCH_HTB is not set
# CONFIG_NET_SCH_HFSC is not set
# CONFIG_NET_SCH_PRIO is not set
# CONFIG_NET_SCH_MULTIQ is not set
# CONFIG_NET_SCH_RED is not set
# CONFIG_NET_SCH_SFB is not set
# CONFIG_NET_SCH_SFQ is not set
# CONFIG_NET_SCH_TEQL is not set
# CONFIG_NET_SCH_TBF is not set
# CONFIG_NET_SCH_GRED is not set
# CONFIG_NET_SCH_DSMARK is not set
# CONFIG_NET_SCH_NETEM is not set
# CONFIG_NET_SCH_DRR is not set
# CONFIG_NET_SCH_MQPRIO is not set
# CONFIG_NET_SCH_CHOKE is not set
# CONFIG_NET_SCH_QFQ is not set
# CONFIG_NET_SCH_INGRESS is not set

#
# Classification
#
CONFIG_NET_CLS=y
# CONFIG_NET_CLS_BASIC is not set
# CONFIG_NET_CLS_TCINDEX is not set
# CONFIG_NET_CLS_ROUTE4 is not set
# CONFIG_NET_CLS_FW is not set
# CONFIG_NET_CLS_U32 is not set
# CONFIG_NET_CLS_RSVP is not set
# CONFIG_NET_CLS_RSVP6 is not set
# CONFIG_NET_CLS_FLOW is not set
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
# CONFIG_NET_EMATCH_CMP is not set
# CONFIG_NET_EMATCH_NBYTE is not set
# CONFIG_NET_EMATCH_U32 is not set
# CONFIG_NET_EMATCH_META is not set
# CONFIG_NET_EMATCH_TEXT is not set
CONFIG_NET_CLS_ACT=y
# CONFIG_NET_ACT_POLICE is not set
# CONFIG_NET_ACT_GACT is not set
# CONFIG_NET_ACT_MIRRED is not set
# CONFIG_NET_ACT_IPT is not set
# CONFIG_NET_ACT_NAT is not set
# CONFIG_NET_ACT_PEDIT is not set
# CONFIG_NET_ACT_SIMP is not set
# CONFIG_NET_ACT_SKBEDIT is not set
# CONFIG_NET_ACT_CSUM is not set
CONFIG_NET_SCH_FIFO=y
# CONFIG_DCB is not set
# CONFIG_BATMAN_ADV is not set
CONFIG_RPS=y
CONFIG_RFS_ACCEL=y
CONFIG_XPS=y
CONFIG_HAVE_BPF_JIT=y
# CONFIG_BPF_JIT is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
# CONFIG_WIRELESS is not set
# CONFIG_WIMAX is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set
# CONFIG_CAIF is not set
# CONFIG_CEPH_LIB is not set
# CONFIG_NFC is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER_PATH=""
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_STANDALONE=y
# CONFIG_PREVENT_FIRMWARE_BUILD is not set
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE="radeon/R600_rlc.bin"
CONFIG_EXTRA_FIRMWARE_DIR="/lib64/firmware"
# CONFIG_DEBUG_DRIVER is not set
CONFIG_DEBUG_DEVRES=y
# CONFIG_SYS_HYPERVISOR is not set
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
# CONFIG_MTD is not set
# CONFIG_PARPORT is not set
CONFIG_PNP=y
CONFIG_PNP_DEBUG_MESSAGES=y

#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_DRBD is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
# CONFIG_BLK_DEV_RAM is not set
CONFIG_CDROM_PKTCDVD=y
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_BLK_DEV_HD is not set
# CONFIG_BLK_DEV_RBD is not set
# CONFIG_SENSORS_LIS3LV02D is not set
# CONFIG_MISC_DEVICES is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set

#
# SCSI device support
#
CONFIG_SCSI_MOD=y
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
# CONFIG_SCSI_NETLINK is not set
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
# CONFIG_CHR_DEV_SCH is not set
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
CONFIG_SCSI_SCAN_ASYNC=y
CONFIG_SCSI_WAIT_SCAN=m

#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
# CONFIG_SCSI_LOWLEVEL is not set
# CONFIG_SCSI_LOWLEVEL_PCMCIA is not set
# CONFIG_SCSI_DH is not set
# CONFIG_SCSI_OSD_INITIATOR is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
CONFIG_ATA_VERBOSE_ERROR=y
CONFIG_ATA_ACPI=y
# CONFIG_SATA_PMP is not set

#
# Controllers with non-SFF native interface
#
CONFIG_SATA_AHCI=y
# CONFIG_SATA_AHCI_PLATFORM is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_SATA_ACARD_AHCI is not set
# CONFIG_SATA_SIL24 is not set
CONFIG_ATA_SFF=y

#
# SFF controllers with custom DMA interface
#
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_SX4 is not set
CONFIG_ATA_BMDMA=y

#
# SATA SFF controllers with BMDMA
#
# CONFIG_ATA_PIIX is not set
# CONFIG_SATA_MV is not set
# CONFIG_SATA_NV is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_SVW is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set

#
# PATA SFF controllers with BMDMA
#
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_ATP867X is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CS5520 is not set
# CONFIG_PATA_CS5530 is not set
# CONFIG_PATA_CS5536 is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RDC is not set
# CONFIG_PATA_SC1200 is not set
# CONFIG_PATA_SCH is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_TOSHIBA is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set

#
# PIO-only SFF controllers
#
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_PCMCIA is not set
# CONFIG_PATA_RZ1000 is not set

#
# Generic fallback / legacy drivers
#
# CONFIG_PATA_ACPI is not set
# CONFIG_ATA_GENERIC is not set
# CONFIG_PATA_LEGACY is not set
# CONFIG_MD is not set
# CONFIG_TARGET_CORE is not set
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_FIREWIRE is not set
# CONFIG_FIREWIRE_NOSY is not set
# CONFIG_I2O is not set
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
CONFIG_NET_CORE=y
# CONFIG_BONDING is not set
# CONFIG_DUMMY is not set
# CONFIG_EQUALIZER is not set
# CONFIG_NET_FC is not set
CONFIG_MII=y
# CONFIG_IFB is not set
# CONFIG_MACVLAN is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
CONFIG_TUN=y
# CONFIG_VETH is not set
# CONFIG_ARCNET is not set

#
# CAIF transport drivers
#
CONFIG_ETHERNET=y
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_NET_VENDOR_ADAPTEC is not set
# CONFIG_NET_VENDOR_ALTEON is not set
# CONFIG_NET_VENDOR_AMD is not set
# CONFIG_NET_VENDOR_ATHEROS is not set
# CONFIG_NET_VENDOR_BROADCOM is not set
# CONFIG_NET_VENDOR_BROCADE is not set
# CONFIG_NET_VENDOR_CHELSIO is not set
# CONFIG_NET_VENDOR_CISCO is not set
# CONFIG_DNET is not set
# CONFIG_NET_VENDOR_DEC is not set
# CONFIG_NET_VENDOR_DLINK is not set
# CONFIG_NET_VENDOR_EMULEX is not set
# CONFIG_NET_VENDOR_EXAR is not set
# CONFIG_NET_VENDOR_FUJITSU is not set
# CONFIG_NET_VENDOR_HP is not set
# CONFIG_NET_VENDOR_INTEL is not set
# CONFIG_IP1000 is not set
# CONFIG_JME is not set
CONFIG_NET_VENDOR_MARVELL=y
# CONFIG_SKGE is not set
CONFIG_SKY2=y
# CONFIG_SKY2_DEBUG is not set
# CONFIG_NET_VENDOR_MELLANOX is not set
# CONFIG_NET_VENDOR_MICREL is not set
# CONFIG_NET_VENDOR_MYRI is not set
# CONFIG_FEALNX is not set
# CONFIG_NET_VENDOR_NATSEMI is not set
# CONFIG_NET_VENDOR_NVIDIA is not set
# CONFIG_NET_VENDOR_OKI is not set
# CONFIG_ETHOC is not set
# CONFIG_NET_PACKET_ENGINE is not set
# CONFIG_NET_VENDOR_QLOGIC is not set
# CONFIG_NET_VENDOR_REALTEK is not set
# CONFIG_NET_VENDOR_RDC is not set
CONFIG_NET_VENDOR_SEEQ=y
# CONFIG_SEEQ8005 is not set
CONFIG_NET_VENDOR_SILAN=y
# CONFIG_SC92031 is not set
# CONFIG_NET_VENDOR_SIS is not set
# CONFIG_SFC is not set
# CONFIG_NET_VENDOR_SMSC is not set
# CONFIG_NET_VENDOR_STMICRO is not set
# CONFIG_NET_VENDOR_SUN is not set
# CONFIG_NET_VENDOR_TEHUTI is not set
# CONFIG_NET_VENDOR_TI is not set
# CONFIG_NET_VENDOR_VIA is not set
# CONFIG_NET_VENDOR_XIRCOM is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_NET_SB1000 is not set
# CONFIG_PHYLIB is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_TR is not set

#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
CONFIG_USB_USBNET=m
# CONFIG_USB_NET_AX8817X is not set
# CONFIG_USB_NET_CDCETHER is not set
# CONFIG_USB_NET_CDC_EEM is not set
# CONFIG_USB_NET_CDC_NCM is not set
CONFIG_USB_NET_DM9601=m
# CONFIG_USB_NET_SMSC75XX is not set
# CONFIG_USB_NET_SMSC95XX is not set
# CONFIG_USB_NET_GL620A is not set
# CONFIG_USB_NET_NET1080 is not set
# CONFIG_USB_NET_PLUSB is not set
# CONFIG_USB_NET_MCS7830 is not set
# CONFIG_USB_NET_RNDIS_HOST is not set
# CONFIG_USB_NET_CDC_SUBSET is not set
# CONFIG_USB_NET_ZAURUS is not set
# CONFIG_USB_NET_CX82310_ETH is not set
# CONFIG_USB_NET_KALMIA is not set
# CONFIG_USB_NET_INT51X1 is not set
# CONFIG_USB_IPHETH is not set
# CONFIG_USB_SIERRA_NET is not set
# CONFIG_WLAN is not set

#
# Enable WiMAX (Networking options) to see the WiMAX drivers
#
# CONFIG_WAN is not set
# CONFIG_VMXNET3 is not set
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
CONFIG_INPUT_POLLDEV=y
CONFIG_INPUT_SPARSEKMAP=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1920
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=1080
CONFIG_INPUT_JOYDEV=y
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
# CONFIG_KEYBOARD_ADP5588 is not set
# CONFIG_KEYBOARD_ADP5589 is not set
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_QT1070 is not set
# CONFIG_KEYBOARD_QT2160 is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_TCA6416 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_MCS is not set
# CONFIG_KEYBOARD_MPR121 is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_ELANTECH is not set
# CONFIG_MOUSE_PS2_SENTELIC is not set
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_MOUSE_SYNAPTICS_I2C is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_SERIO_ALTERA_PS2 is not set
# CONFIG_SERIO_PS2MULT is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_VT_HW_CONSOLE_BINDING=y
CONFIG_UNIX98_PTYS=y
# CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set
# CONFIG_LEGACY_PTYS is not set
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_NOZOMI is not set
# CONFIG_N_GSM is not set
# CONFIG_TRACE_SINK is not set

#
# KCopy
#
# CONFIG_KCOPY is not set
CONFIG_DEVKMEM=y

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_SERIAL_8250_PCI=y
CONFIG_SERIAL_8250_PNP=y
# CONFIG_SERIAL_8250_CS is not set
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_RSA=y

#
# Non-8250 serial port support
#
# CONFIG_SERIAL_MFD_HSU is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
# CONFIG_SERIAL_TIMBERDALE is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
# CONFIG_SERIAL_PCH_UART is not set
# CONFIG_SERIAL_XILINX_PS_UART is not set
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=y
# CONFIG_HW_RANDOM_TIMERIOMEM is not set
# CONFIG_HW_RANDOM_INTEL is not set
CONFIG_HW_RANDOM_AMD=y
# CONFIG_HW_RANDOM_VIA is not set
CONFIG_NVRAM=y
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set

#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
# CONFIG_CARDMAN_4000 is not set
# CONFIG_CARDMAN_4040 is not set
# CONFIG_IPWIRELESS is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
CONFIG_HPET_MMAP=y
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
# CONFIG_RAMOOPS is not set
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
CONFIG_I2C_CHARDEV=y
# CONFIG_I2C_MUX is not set
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_ALGOBIT=y

#
# I2C Hardware Bus support
#

#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
CONFIG_I2C_AMD756=y
# CONFIG_I2C_AMD756_S4882 is not set
CONFIG_I2C_AMD8111=y
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_ISCH is not set
CONFIG_I2C_PIIX4=y
# CONFIG_I2C_NFORCE2 is not set
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set

#
# ACPI drivers
#
CONFIG_I2C_SCMI=y

#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_DESIGNWARE_PCI is not set
# CONFIG_I2C_INTEL_MID is not set
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PCA_PLATFORM is not set
# CONFIG_I2C_PXA_PCI is not set
# CONFIG_I2C_SIMTEC is not set
# CONFIG_I2C_XILINX is not set
# CONFIG_I2C_EG20T is not set

#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_DIOLAN_U2C is not set
# CONFIG_I2C_PARPORT_LIGHT is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set

#
# Other I2C/SMBus bus drivers
#
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# CONFIG_SPI is not set

#
# PPS support
#
# CONFIG_PPS is not set

#
# PPS generators support
#

#
# PTP clock support
#

#
# Enable Device Drivers -> PPS to see the PTP clock options.
#
CONFIG_ARCH_WANT_OPTIONAL_GPIOLIB=y
# CONFIG_GPIOLIB is not set
# CONFIG_W1 is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
# CONFIG_PDA_POWER is not set
# CONFIG_TEST_POWER is not set
# CONFIG_BATTERY_DS2780 is not set
# CONFIG_BATTERY_DS2782 is not set
# CONFIG_BATTERY_BQ20Z75 is not set
# CONFIG_BATTERY_BQ27x00 is not set
# CONFIG_BATTERY_MAX17040 is not set
# CONFIG_BATTERY_MAX17042 is not set
# CONFIG_CHARGER_MAX8903 is not set
CONFIG_HWMON=y
CONFIG_HWMON_VID=m
CONFIG_HWMON_DEBUG_CHIP=y

#
# Native drivers
#
# CONFIG_SENSORS_ABITUGURU is not set
# CONFIG_SENSORS_ABITUGURU3 is not set
# CONFIG_SENSORS_AD7414 is not set
# CONFIG_SENSORS_AD7418 is not set
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1026=m
CONFIG_SENSORS_ADM1029=m
CONFIG_SENSORS_ADM1031=m
CONFIG_SENSORS_ADM9240=m
# CONFIG_SENSORS_ADT7411 is not set
# CONFIG_SENSORS_ADT7462 is not set
# CONFIG_SENSORS_ADT7470 is not set
CONFIG_SENSORS_ADT7475=m
CONFIG_SENSORS_ASC7621=m
# CONFIG_SENSORS_K8TEMP is not set
CONFIG_SENSORS_K10TEMP=m
CONFIG_SENSORS_FAM15H_POWER=m
# CONFIG_SENSORS_ASB100 is not set
# CONFIG_SENSORS_ATXP1 is not set
CONFIG_SENSORS_DS620=m
CONFIG_SENSORS_DS1621=m
# CONFIG_SENSORS_I5K_AMB is not set
CONFIG_SENSORS_F71805F=m
CONFIG_SENSORS_F71882FG=m
CONFIG_SENSORS_F75375S=m
CONFIG_SENSORS_FSCHMD=m
CONFIG_SENSORS_G760A=m
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_GL520SM=m
# CONFIG_SENSORS_CORETEMP is not set
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_JC42=m
# CONFIG_SENSORS_LINEAGE is not set
CONFIG_SENSORS_LM63=m
CONFIG_SENSORS_LM73=m
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM87=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_LM92=m
CONFIG_SENSORS_LM93=m
CONFIG_SENSORS_LTC4151=m
# CONFIG_SENSORS_LTC4215 is not set
# CONFIG_SENSORS_LTC4245 is not set
# CONFIG_SENSORS_LTC4261 is not set
CONFIG_SENSORS_LM95241=m
# CONFIG_SENSORS_LM95245 is not set
CONFIG_SENSORS_MAX16065=m
CONFIG_SENSORS_MAX1619=m
# CONFIG_SENSORS_MAX1668 is not set
# CONFIG_SENSORS_MAX6639 is not set
# CONFIG_SENSORS_MAX6642 is not set
# CONFIG_SENSORS_MAX6650 is not set
# CONFIG_SENSORS_NTC_THERMISTOR is not set
CONFIG_SENSORS_PC87360=m
CONFIG_SENSORS_PC87427=m
CONFIG_SENSORS_PCF8591=m
# CONFIG_PMBUS is not set
CONFIG_SENSORS_SHT21=m
CONFIG_SENSORS_SIS5595=m
# CONFIG_SENSORS_SMM665 is not set
# CONFIG_SENSORS_DME1737 is not set
CONFIG_SENSORS_EMC1403=m
CONFIG_SENSORS_EMC2103=m
CONFIG_SENSORS_EMC6W201=m
CONFIG_SENSORS_SMSC47M1=m
CONFIG_SENSORS_SMSC47M192=m
# CONFIG_SENSORS_SMSC47B397 is not set
CONFIG_SENSORS_SCH56XX_COMMON=m
CONFIG_SENSORS_SCH5627=m
CONFIG_SENSORS_SCH5636=m
CONFIG_SENSORS_ADS1015=m
CONFIG_SENSORS_ADS7828=m
# CONFIG_SENSORS_AMC6821 is not set
CONFIG_SENSORS_THMC50=m
# CONFIG_SENSORS_TMP102 is not set
# CONFIG_SENSORS_TMP401 is not set
# CONFIG_SENSORS_TMP421 is not set
CONFIG_SENSORS_VIA_CPUTEMP=m
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_VT1211=m
CONFIG_SENSORS_VT8231=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83791D=m
CONFIG_SENSORS_W83792D=m
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83795 is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83L786NG is not set
CONFIG_SENSORS_W83627HF=m
CONFIG_SENSORS_W83627EHF=m
# CONFIG_SENSORS_APPLESMC is not set

#
# ACPI drivers
#
CONFIG_SENSORS_ACPI_POWER=m
# CONFIG_SENSORS_ATK0110 is not set
CONFIG_THERMAL=y
CONFIG_THERMAL_HWMON=y
# CONFIG_WATCHDOG is not set
CONFIG_SSB_POSSIBLE=y

#
# Sonics Silicon Backplane
#
# CONFIG_SSB is not set
CONFIG_BCMA_POSSIBLE=y

#
# Broadcom specific AMBA
#
# CONFIG_BCMA is not set

#
# Multifunction device drivers
#
CONFIG_MFD_CORE=m
# CONFIG_MFD_88PM860X is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_TPS6105X is not set
# CONFIG_TPS6507X is not set
# CONFIG_TWL4030_CORE is not set
# CONFIG_MFD_STMPE is not set
# CONFIG_MFD_TC3589X is not set
# CONFIG_MFD_TMIO is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_MAX8925 is not set
# CONFIG_MFD_MAX8997 is not set
# CONFIG_MFD_MAX8998 is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X_I2C is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_WM8994 is not set
# CONFIG_MFD_PCF50633 is not set
# CONFIG_ABX500_CORE is not set
# CONFIG_MFD_CS5535 is not set
CONFIG_LPC_SCH=m
# CONFIG_MFD_RDC321X is not set
# CONFIG_MFD_JANZ_CMODIO is not set
# CONFIG_MFD_VX855 is not set
# CONFIG_MFD_WL1273_CORE is not set
# CONFIG_REGULATOR is not set
CONFIG_MEDIA_SUPPORT=y

#
# Multimedia core support
#
# CONFIG_MEDIA_CONTROLLER is not set
CONFIG_VIDEO_DEV=y
CONFIG_VIDEO_V4L2_COMMON=y
# CONFIG_DVB_CORE is not set
CONFIG_VIDEO_MEDIA=y

#
# Multimedia drivers
#
# CONFIG_RC_CORE is not set
CONFIG_MEDIA_ATTACH=y
CONFIG_MEDIA_TUNER=y
# CONFIG_MEDIA_TUNER_CUSTOMISE is not set
CONFIG_MEDIA_TUNER_SIMPLE=y
CONFIG_MEDIA_TUNER_TDA8290=y
CONFIG_MEDIA_TUNER_TDA827X=y
CONFIG_MEDIA_TUNER_TDA18271=y
CONFIG_MEDIA_TUNER_TDA9887=y
CONFIG_MEDIA_TUNER_TEA5761=y
CONFIG_MEDIA_TUNER_TEA5767=y
CONFIG_MEDIA_TUNER_MT20XX=y
CONFIG_MEDIA_TUNER_XC2028=y
CONFIG_MEDIA_TUNER_XC5000=y
CONFIG_MEDIA_TUNER_XC4000=y
CONFIG_MEDIA_TUNER_MC44S803=y
CONFIG_VIDEO_V4L2=y
CONFIG_VIDEOBUF_GEN=y
CONFIG_VIDEOBUF_VMALLOC=y
CONFIG_VIDEO_TVEEPROM=y
CONFIG_VIDEO_TUNER=y
CONFIG_VIDEO_CAPTURE_DRIVERS=y
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
CONFIG_VIDEO_HELPER_CHIPS_AUTO=y

#
# Audio decoders, processors and mixers
#
CONFIG_VIDEO_MSP3400=y

#
# RDS decoders
#

#
# Video decoders
#
CONFIG_VIDEO_SAA711X=y
CONFIG_VIDEO_TVP5150=y

#
# Video and audio decoders
#

#
# MPEG video encoders
#

#
# Video encoders
#

#
# Camera sensor devices
#
CONFIG_VIDEO_MT9V011=y

#
# Flash devices
#

#
# Video improvement chips
#

#
# Miscelaneous helper chips
#
# CONFIG_VIDEO_VIVI is not set
# CONFIG_VIDEO_CPIA2 is not set
# CONFIG_VIDEO_ZORAN is not set
# CONFIG_VIDEO_SAA7134 is not set
# CONFIG_VIDEO_MXB is not set
# CONFIG_VIDEO_HEXIUM_ORION is not set
# CONFIG_VIDEO_HEXIUM_GEMINI is not set
# CONFIG_VIDEO_CAFE_CCIC is not set
# CONFIG_SOC_CAMERA is not set
CONFIG_V4L_USB_DRIVERS=y
# CONFIG_USB_VIDEO_CLASS is not set
# CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV is not set
# CONFIG_USB_GSPCA is not set
# CONFIG_VIDEO_PVRUSB2 is not set
# CONFIG_VIDEO_HDPVR is not set
CONFIG_VIDEO_EM28XX=y
CONFIG_VIDEO_EM28XX_ALSA=y
# CONFIG_VIDEO_USBVISION is not set
# CONFIG_USB_ET61X251 is not set
# CONFIG_USB_SN9C102 is not set
# CONFIG_USB_PWC is not set
# CONFIG_USB_ZR364XX is not set
# CONFIG_USB_STKWEBCAM is not set
# CONFIG_USB_S2255 is not set
# CONFIG_V4L_MEM2MEM_DRIVERS is not set
# CONFIG_RADIO_ADAPTERS is not set

#
# Graphics support
#
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_VIA is not set
CONFIG_VGA_ARB=y
CONFIG_VGA_ARB_MAX_GPUS=16
# CONFIG_VGA_SWITCHEROO is not set
CONFIG_DRM=y
CONFIG_DRM_KMS_HELPER=y
CONFIG_DRM_TTM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=y
CONFIG_DRM_RADEON_KMS=y
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
# CONFIG_DRM_VMWGFX is not set
# CONFIG_STUB_POULSBO is not set
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
# CONFIG_FB_DDC is not set
# CONFIG_FB_BOOT_VESA_SUPPORT is not set
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
# CONFIG_FB_SYS_FILLRECT is not set
# CONFIG_FB_SYS_COPYAREA is not set
# CONFIG_FB_SYS_IMAGEBLIT is not set
# CONFIG_FB_FOREIGN_ENDIAN is not set
# CONFIG_FB_SYS_FOPS is not set
# CONFIG_FB_WMT_GE_ROPS is not set
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set

#
# Frame buffer hardware drivers
#
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_UVESA is not set
# CONFIG_FB_VESA is not set
# CONFIG_FB_EFI is not set
# CONFIG_FB_N411 is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_VIA is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_TMIO is not set
# CONFIG_FB_SMSCUFX is not set
# CONFIG_FB_UDL is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
# CONFIG_FB_BROADSHEET is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_GENERIC is not set
# CONFIG_BACKLIGHT_PROGEAR is not set
# CONFIG_BACKLIGHT_APPLE is not set
# CONFIG_BACKLIGHT_SAHARA is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
# CONFIG_BACKLIGHT_ADP8870 is not set

#
# Display device support
#
CONFIG_DISPLAY_SUPPORT=y

#
# Display hardware drivers
#

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VGACON_SOFT_SCROLLBACK is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
# CONFIG_FB_CON_DECOR is not set
CONFIG_FONTS=y
# CONFIG_FONT_8x8 is not set
CONFIG_FONT_8x16=y
# CONFIG_FONT_6x11 is not set
CONFIG_FONT_7x14=y
# CONFIG_FONT_PEARL_8x8 is not set
# CONFIG_FONT_ACORN_8x8 is not set
# CONFIG_FONT_MINI_4x6 is not set
# CONFIG_FONT_SUN8x16 is not set
# CONFIG_FONT_SUN12x22 is not set
CONFIG_FONT_10x18=y
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y
CONFIG_SOUND=y
CONFIG_SOUND_OSS_CORE=y
CONFIG_SOUND_OSS_CORE_PRECLAIM=y
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_HWDEP=y
CONFIG_SND_RAWMIDI=y
CONFIG_SND_SEQUENCER=y
CONFIG_SND_SEQ_DUMMY=y
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_HRTIMER=y
CONFIG_SND_SEQ_HRTIMER_DEFAULT=y
# CONFIG_SND_DYNAMIC_MINORS is not set
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
CONFIG_SND_DMA_SGBUF=y
CONFIG_SND_RAWMIDI_SEQ=y
CONFIG_SND_OPL3_LIB_SEQ=y
# CONFIG_SND_OPL4_LIB_SEQ is not set
# CONFIG_SND_SBAWE_SEQ is not set
# CONFIG_SND_EMU10K1_SEQ is not set
CONFIG_SND_MPU401_UART=y
CONFIG_SND_OPL3_LIB=y
CONFIG_SND_DRIVERS=y
# CONFIG_SND_PCSP is not set
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_ALOOP is not set
CONFIG_SND_VIRMIDI=y
# CONFIG_SND_MTPAV is not set
CONFIG_SND_SERIAL_U16550=y
CONFIG_SND_MPU401=y
CONFIG_SND_PCI=y
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ASIHPI is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AW2 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
CONFIG_SND_CMIPCI=y
# CONFIG_SND_OXYGEN is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS5530 is not set
# CONFIG_SND_CS5535AUDIO is not set
# CONFIG_SND_CTXFI is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
# CONFIG_SND_INDIGOIOX is not set
# CONFIG_SND_INDIGODJX is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_HDA_INTEL is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_LOLA is not set
# CONFIG_SND_LX6464ES is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VIRTUOSO is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_USB is not set
# CONFIG_SND_PCMCIA is not set
# CONFIG_SND_SOC is not set
# CONFIG_SOUND_PRIME is not set
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
CONFIG_HIDRAW=y

#
# USB Input Devices
#
CONFIG_USB_HID=y
# CONFIG_HID_PID is not set
CONFIG_USB_HIDDEV=y

#
# Special HID drivers
#
CONFIG_HID_A4TECH=y
# CONFIG_HID_ACRUX is not set
CONFIG_HID_APPLE=y
CONFIG_HID_BELKIN=y
CONFIG_HID_CHERRY=y
CONFIG_HID_CHICONY=y
# CONFIG_HID_PRODIKEYS is not set
CONFIG_HID_CYPRESS=y
# CONFIG_HID_DRAGONRISE is not set
# CONFIG_HID_EMS_FF is not set
CONFIG_HID_EZKEY=y
# CONFIG_HID_HOLTEK is not set
# CONFIG_HID_KEYTOUCH is not set
CONFIG_HID_KYE=y
# CONFIG_HID_UCLOGIC is not set
# CONFIG_HID_WALTOP is not set
# CONFIG_HID_GYRATION is not set
# CONFIG_HID_TWINHAN is not set
CONFIG_HID_KENSINGTON=y
# CONFIG_HID_LCPOWER is not set
CONFIG_HID_LOGITECH=y
CONFIG_HID_LOGITECH_DJ=m
# CONFIG_LOGITECH_FF is not set
# CONFIG_LOGIRUMBLEPAD2_FF is not set
# CONFIG_LOGIG940_FF is not set
# CONFIG_LOGIWHEELS_FF is not set
CONFIG_HID_MICROSOFT=y
CONFIG_HID_MONTEREY=y
# CONFIG_HID_MULTITOUCH is not set
# CONFIG_HID_NTRIG is not set
# CONFIG_HID_ORTEK is not set
# CONFIG_HID_PANTHERLORD is not set
# CONFIG_HID_PETALYNX is not set
# CONFIG_HID_PICOLCD is not set
# CONFIG_HID_PRIMAX is not set
# CONFIG_HID_QUANTA is not set
# CONFIG_HID_ROCCAT is not set
# CONFIG_HID_SAMSUNG is not set
# CONFIG_HID_SONY is not set
# CONFIG_HID_SPEEDLINK is not set
# CONFIG_HID_SUNPLUS is not set
# CONFIG_HID_GREENASIA is not set
# CONFIG_HID_SMARTJOYPLUS is not set
# CONFIG_HID_TOPSEED is not set
# CONFIG_HID_THRUSTMASTER is not set
# CONFIG_HID_ZEROPLUS is not set
# CONFIG_HID_ZYDACRON is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_COMMON=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB_ARCH_HAS_XHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
# CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set

#
# Miscellaneous USB options
#
# CONFIG_USB_DEVICEFS is not set
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_DWC3 is not set
CONFIG_USB_MON=y
# CONFIG_USB_WUSB is not set
# CONFIG_USB_WUSB_CBAF is not set

#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
# CONFIG_USB_XHCI_HCD is not set
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1760_HCD is not set
# CONFIG_USB_ISP1362_HCD is not set
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_WHCI_HCD is not set
# CONFIG_USB_HWA_HCD is not set

#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=y
# CONFIG_USB_WDM is not set
# CONFIG_USB_TMC is not set

#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#

#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_REALTEK is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_USBAT is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
# CONFIG_USB_STORAGE_ALAUDA is not set
# CONFIG_USB_STORAGE_ONETOUCH is not set
# CONFIG_USB_STORAGE_KARMA is not set
# CONFIG_USB_STORAGE_CYPRESS_ATACB is not set
# CONFIG_USB_STORAGE_ENE_UB6250 is not set
CONFIG_USB_UAS=y
# CONFIG_USB_LIBUSUAL is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set

#
# USB port drivers
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_SEVSEG is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_ISIGHTFW is not set
# CONFIG_USB_YUREX is not set
# CONFIG_USB_GADGET is not set

#
# OTG and related infrastructure
#
# CONFIG_NOP_USB_XCEIV is not set
# CONFIG_UWB is not set
CONFIG_MMC=y
# CONFIG_MMC_DEBUG is not set
# CONFIG_MMC_UNSAFE_RESUME is not set
# CONFIG_MMC_CLKGATE is not set

#
# MMC/SD/SDIO Card Drivers
#
CONFIG_MMC_BLOCK=y
CONFIG_MMC_BLOCK_MINORS=8
CONFIG_MMC_BLOCK_BOUNCE=y
# CONFIG_SDIO_UART is not set
# CONFIG_MMC_TEST is not set

#
# MMC/SD/SDIO Host Controller Drivers
#
CONFIG_MMC_SDHCI=y
CONFIG_MMC_SDHCI_PCI=y
CONFIG_MMC_RICOH_MMC=y
# CONFIG_MMC_SDHCI_PLTFM is not set
# CONFIG_MMC_WBSD is not set
# CONFIG_MMC_TIFM_SD is not set
# CONFIG_MMC_SDRICOH_CS is not set
# CONFIG_MMC_CB710 is not set
CONFIG_MMC_VIA_SDMMC=y
CONFIG_MMC_VUB300=y
# CONFIG_MMC_USHC is not set
# CONFIG_MEMSTICK is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
CONFIG_EDAC=y

#
# Reporting subsystems
#
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_DECODE_MCE=y
# CONFIG_EDAC_MCE_INJ is not set
# CONFIG_EDAC_MM_EDAC is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
# CONFIG_RTC_HCTOSYS is not set
# CONFIG_RTC_DEBUG is not set

#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set

#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_DS3232 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_ISL12022 is not set
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8563 is not set
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_BQ32K is not set
# CONFIG_RTC_DRV_S35390A is not set
# CONFIG_RTC_DRV_FM3130 is not set
# CONFIG_RTC_DRV_RX8581 is not set
# CONFIG_RTC_DRV_RX8025 is not set
# CONFIG_RTC_DRV_EM3027 is not set
# CONFIG_RTC_DRV_RV3029C2 is not set

#
# SPI RTC drivers
#

#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=y
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_MSM6242 is not set
# CONFIG_RTC_DRV_BQ4802 is not set
# CONFIG_RTC_DRV_RP5C01 is not set
# CONFIG_RTC_DRV_V3020 is not set

#
# on-CPU RTC drivers
#
# CONFIG_DMADEVICES is not set
# CONFIG_AUXDISPLAY is not set
# CONFIG_UIO is not set

#
# Virtio drivers
#
# CONFIG_VIRTIO_PCI is not set
# CONFIG_VIRTIO_BALLOON is not set
# CONFIG_VIRTIO_MMIO is not set
# CONFIG_STAGING is not set
# CONFIG_X86_PLATFORM_DEVICES is not set

#
# Hardware Spinlock drivers
#
CONFIG_CLKEVT_I8253=y
CONFIG_I8253_LOCK=y
CONFIG_CLKBLD_I8253=y
CONFIG_IOMMU_API=y
CONFIG_IOMMU_SUPPORT=y
CONFIG_AMD_IOMMU=y
CONFIG_AMD_IOMMU_STATS=y
# CONFIG_INTEL_IOMMU is not set
# CONFIG_IRQ_REMAP is not set
# CONFIG_VIRT_DRIVERS is not set
# CONFIG_HYPERV is not set
# CONFIG_PM_DEVFREQ is not set

#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_FIRMWARE_MEMMAP=y
# CONFIG_EFI_VARS is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_DMIID=y
CONFIG_DMI_SYSFS=y
# CONFIG_ISCSI_IBFT_FIND is not set
# CONFIG_SIGMA is not set
# CONFIG_GOOGLE_FIRMWARE is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT2_FS_XIP is not set
# CONFIG_EXT3_FS is not set
CONFIG_EXT4_FS=y
CONFIG_EXT4_USE_FOR_EXT23=y
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
# CONFIG_EXT4_FS_SECURITY is not set
# CONFIG_EXT4_DEBUG is not set
CONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_BTRFS_FS is not set
# CONFIG_NILFS2_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_FILE_LOCKING=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_FANOTIFY=y
# CONFIG_FANOTIFY_ACCESS_PERMISSIONS is not set
# CONFIG_QUOTA is not set
# CONFIG_QUOTACTL is not set
# CONFIG_AUTOFS4_FS is not set
CONFIG_FUSE_FS=y
# CONFIG_CUSE is not set
CONFIG_GENERIC_ACL=y

#
# Caches
#
CONFIG_FSCACHE=y
# CONFIG_FSCACHE_STATS is not set
# CONFIG_FSCACHE_HISTOGRAM is not set
# CONFIG_FSCACHE_DEBUG is not set
# CONFIG_FSCACHE_OBJECT_LIST is not set
# CONFIG_CACHEFILES is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_TMPFS_XATTR=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_CONFIGFS_FS=y
# CONFIG_MISC_FILESYSTEMS is not set
CONFIG_NETWORK_FILESYSTEMS=y
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_CEPH_FS is not set
CONFIG_CIFS=y
CONFIG_CIFS_STATS=y
# CONFIG_CIFS_STATS2 is not set
CONFIG_CIFS_WEAK_PW_HASH=y
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_FSCACHE is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_LDM_PARTITION is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not set
CONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="utf8"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=y
CONFIG_NLS_CODEPAGE_852=y
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
CONFIG_NLS_CODEPAGE_862=y
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
CONFIG_NLS_CODEPAGE_869=y
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
CONFIG_NLS_ISO8859_8=y
CONFIG_NLS_CODEPAGE_1250=y
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
CONFIG_NLS_ISO8859_15=y
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=y
# CONFIG_DLM is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
CONFIG_DEFAULT_MESSAGE_LOGLEVEL=7
CONFIG_ENABLE_WARN_DEPRECATED=y
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=2048
CONFIG_MAGIC_SYSRQ=y
CONFIG_STRIP_ASM_SYMS=y
# CONFIG_UNUSED_SYMBOLS is not set
CONFIG_DEBUG_FS=y
CONFIG_HEADERS_CHECK=y
CONFIG_DEBUG_SECTION_MISMATCH=y
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_SHIRQ=y
CONFIG_LOCKUP_DETECTOR=y
CONFIG_HARDLOCKUP_DETECTOR=y
# CONFIG_BOOTPARAM_HARDLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_HARDLOCKUP_PANIC_VALUE=0
# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
CONFIG_DETECT_HUNG_TASK=y
CONFIG_DEFAULT_HUNG_TASK_TIMEOUT=120
# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set
CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0
CONFIG_SCHED_DEBUG=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_TIMER_STATS is not set
# CONFIG_DEBUG_OBJECTS is not set
CONFIG_SLUB_DEBUG_ON=y
# CONFIG_SLUB_STATS is not set
# CONFIG_DEBUG_KMEMLEAK is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_PROVE_LOCKING is not set
# CONFIG_SPARSE_RCU_POINTER is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_ATOMIC_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_VIRTUAL is not set
# CONFIG_DEBUG_WRITECOUNT is not set
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_LIST is not set
# CONFIG_TEST_LIST_SORT is not set
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
# CONFIG_DEBUG_CREDENTIALS is not set
CONFIG_ARCH_WANT_FRAME_POINTERS=y
CONFIG_FRAME_POINTER=y
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
CONFIG_RCU_CPU_STALL_TIMEOUT=60
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
# CONFIG_DEBUG_PER_CPU_MAPS is not set
# CONFIG_LKDTM is not set
# CONFIG_CPU_NOTIFIER_ERROR_INJECT is not set
# CONFIG_FAULT_INJECTION is not set
# CONFIG_LATENCYTOP is not set
# CONFIG_SYSCTL_SYSCALL_CHECK is not set
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_USER_STACKTRACE_SUPPORT=y
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y
CONFIG_HAVE_FUNCTION_GRAPH_FP_TEST=y
CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_HAVE_C_RECORDMCOUNT=y
CONFIG_TRACING_SUPPORT=y
# CONFIG_FTRACE is not set
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
# CONFIG_BUILD_DOCSRC is not set
# CONFIG_DYNAMIC_DEBUG is not set
# CONFIG_DMA_API_DEBUG is not set
# CONFIG_ATOMIC64_SELFTEST is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
CONFIG_HAVE_ARCH_KMEMCHECK=y
# CONFIG_KMEMCHECK is not set
# CONFIG_TEST_KSTRTOX is not set
# CONFIG_STRICT_DEVMEM is not set
CONFIG_X86_VERBOSE_BOOTUP=y
CONFIG_EARLY_PRINTK=y
CONFIG_EARLY_PRINTK_DBGP=y
CONFIG_DEBUG_STACKOVERFLOW=y
# CONFIG_X86_PTDUMP is not set
CONFIG_DEBUG_RODATA=y
CONFIG_DEBUG_RODATA_TEST=y
# CONFIG_DEBUG_SET_MODULE_RONX is not set
# CONFIG_DEBUG_NX_TEST is not set
# CONFIG_IOMMU_DEBUG is not set
# CONFIG_IOMMU_STRESS is not set
CONFIG_HAVE_MMIOTRACE_SUPPORT=y
CONFIG_IO_DELAY_TYPE_0X80=0
CONFIG_IO_DELAY_TYPE_0XED=1
CONFIG_IO_DELAY_TYPE_UDELAY=2
CONFIG_IO_DELAY_TYPE_NONE=3
CONFIG_IO_DELAY_0X80=y
# CONFIG_IO_DELAY_0XED is not set
# CONFIG_IO_DELAY_UDELAY is not set
# CONFIG_IO_DELAY_NONE is not set
CONFIG_DEFAULT_IO_DELAY_TYPE=0
# CONFIG_DEBUG_BOOT_PARAMS is not set
# CONFIG_CPA_DEBUG is not set
# CONFIG_OPTIMIZE_INLINING is not set
# CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is not set

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY_DMESG_RESTRICT is not set
CONFIG_SECURITY=y
# CONFIG_SECURITYFS is not set
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_NETWORK_XFRM=y
CONFIG_SECURITY_PATH=y
# CONFIG_SECURITY_SELINUX is not set
# CONFIG_SECURITY_TOMOYO is not set
# CONFIG_SECURITY_APPARMOR is not set
# CONFIG_IMA is not set
CONFIG_DEFAULT_SECURITY_DAC=y
CONFIG_DEFAULT_SECURITY=""
CONFIG_CRYPTO=y

#
# Crypto core or helper
#
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
CONFIG_CRYPTO_AEAD=y
CONFIG_CRYPTO_AEAD2=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_BLKCIPHER2=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
CONFIG_CRYPTO_RNG2=y
CONFIG_CRYPTO_PCOMP2=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
# CONFIG_CRYPTO_USER is not set
CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
# CONFIG_CRYPTO_GF128MUL is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_PCRYPT is not set
CONFIG_CRYPTO_WORKQUEUE=y
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_AUTHENC=y
# CONFIG_CRYPTO_TEST is not set

#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
# CONFIG_CRYPTO_GCM is not set
# CONFIG_CRYPTO_SEQIV is not set

#
# Block modes
#
CONFIG_CRYPTO_CBC=y
# CONFIG_CRYPTO_CTR is not set
# CONFIG_CRYPTO_CTS is not set
CONFIG_CRYPTO_ECB=y
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_PCBC is not set
# CONFIG_CRYPTO_XTS is not set

#
# Hash modes
#
CONFIG_CRYPTO_HMAC=y
# CONFIG_CRYPTO_XCBC is not set
# CONFIG_CRYPTO_VMAC is not set

#
# Digest
#
# CONFIG_CRYPTO_CRC32C is not set
# CONFIG_CRYPTO_CRC32C_INTEL is not set
# CONFIG_CRYPTO_GHASH is not set
CONFIG_CRYPTO_MD4=y
CONFIG_CRYPTO_MD5=y
# CONFIG_CRYPTO_MICHAEL_MIC is not set
# CONFIG_CRYPTO_RMD128 is not set
# CONFIG_CRYPTO_RMD160 is not set
# CONFIG_CRYPTO_RMD256 is not set
# CONFIG_CRYPTO_RMD320 is not set
CONFIG_CRYPTO_SHA1=y
# CONFIG_CRYPTO_SHA1_SSSE3 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_TGR192 is not set
# CONFIG_CRYPTO_WP512 is not set
# CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL is not set

#
# Ciphers
#
CONFIG_CRYPTO_AES=y
# CONFIG_CRYPTO_AES_X86_64 is not set
# CONFIG_CRYPTO_AES_NI_INTEL is not set
# CONFIG_CRYPTO_ANUBIS is not set
CONFIG_CRYPTO_ARC4=y
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_BLOWFISH_X86_64 is not set
# CONFIG_CRYPTO_CAMELLIA is not set
# CONFIG_CRYPTO_CAST5 is not set
# CONFIG_CRYPTO_CAST6 is not set
CONFIG_CRYPTO_DES=y
# CONFIG_CRYPTO_FCRYPT is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_SALSA20 is not set
# CONFIG_CRYPTO_SALSA20_X86_64 is not set
# CONFIG_CRYPTO_SEED is not set
# CONFIG_CRYPTO_SERPENT is not set
# CONFIG_CRYPTO_TEA is not set
# CONFIG_CRYPTO_TWOFISH is not set
# CONFIG_CRYPTO_TWOFISH_X86_64 is not set
# CONFIG_CRYPTO_TWOFISH_X86_64_3WAY is not set

#
# Compression
#
CONFIG_CRYPTO_DEFLATE=y
# CONFIG_CRYPTO_ZLIB is not set
# CONFIG_CRYPTO_LZO is not set

#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not set
# CONFIG_CRYPTO_USER_API_HASH is not set
# CONFIG_CRYPTO_USER_API_SKCIPHER is not set
# CONFIG_CRYPTO_HW is not set
CONFIG_HAVE_KVM=y
# CONFIG_VIRTUALIZATION is not set
# CONFIG_BINARY_PRINTF is not set

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_GENERIC_FIND_FIRST_BIT=y
CONFIG_CRC_CCITT=m
CONFIG_CRC16=y
CONFIG_CRC_T10DIF=y
CONFIG_CRC_ITU_T=y
CONFIG_CRC32=y
# CONFIG_CRC7 is not set
# CONFIG_LIBCRC32C is not set
# CONFIG_CRC8 is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_LZO_DECOMPRESS=y
CONFIG_XZ_DEC=y
CONFIG_XZ_DEC_X86=y
CONFIG_XZ_DEC_POWERPC=y
CONFIG_XZ_DEC_IA64=y
CONFIG_XZ_DEC_ARM=y
CONFIG_XZ_DEC_ARMTHUMB=y
CONFIG_XZ_DEC_SPARC=y
CONFIG_XZ_DEC_BCJ=y
# CONFIG_XZ_DEC_TEST is not set
CONFIG_DECOMPRESS_GZIP=y
CONFIG_DECOMPRESS_BZIP2=y
CONFIG_DECOMPRESS_LZMA=y
CONFIG_DECOMPRESS_XZ=y
CONFIG_DECOMPRESS_LZO=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y
CONFIG_CPU_RMAP=y
CONFIG_NLATTR=y
CONFIG_AVERAGE=y
# CONFIG_CORDIC is not set

Re: [gentoo-user] make of gentoo-sources-3.2.12 fails

[Pandu Poluan]

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

On May 10, 2012 9:27 PM, "Michael Scherer" <a6702894@unet.univie.ac.at>
wrote:
>
> Hi all,
>
> after downloading the 3.2.12-sources everything went fine
> for a couple of weeks, I compiled them a couple of times,
> but suddenly, maybe because of some world-updates, errors
> started to accumulate, first it could do make but no modules,
> then kernel make made it almost and now I'm stuck with this
> rather short make output:
>
>  HOSTCC  scripts/basic/fixdep
>  HOSTCC  scripts/kconfig/conf.o
>  HOSTCC  scripts/kconfig/zconf.tab.o
> scripts/kconfig/zconf.tab.c: In function ‘header_print_comment’:
> scripts/kconfig/confdata.c:540:10: warning: ignoring return value of
>  ‘fwrite’, declared with attribute warn_unused_result
>  scripts/kconfig/zconf.tab.c: In function ‘kconfig_print_comment’:
>  scripts/kconfig/confdata.c:467:10: warning: ignoring return value of
>  ‘fwrite’, declared with attribute warn_unused_result HOSTLD
>  scripts/kconfig/conf scripts/kconfig/conf --silentoldconfig Kconfig
>  CHK     include/linux/version.h CHK     include/generated/utsrelease.h
>  CC      kernel/bounds.s
>  GEN     include/generated/bounds.h
>  CC      arch/x86/kernel/asm-offsets.s
>  GEN     include/generated/asm-offsets.h
>  CALL    scripts/checksyscalls.sh
>  CC      scripts/mod/empty.o
>  HOSTCC  scripts/mod/mk_elfconfig
>  MKELF   scripts/mod/elfconfig.h
>  HOSTCC  scripts/mod/file2alias.o
>  HOSTCC  scripts/mod/modpost.o
>  HOSTCC  scripts/mod/sumversion.o
>  HOSTLD  scripts/mod/modpost
>  HOSTCC  scripts/kallsyms
>  HOSTCC  scripts/pnmtologo
>  HOSTCC  scripts/conmakehash
>  HOSTCC  scripts/bin2c
>  CC      init/main.o
>  CHK     include/generated/compile.h
>  CC      init/version.o
>  CC      init/do_mounts.o
>  CC      init/do_mounts_initrd.o
>  LD      init/mounts.o
> ls -Al -m elf_x86_64 -r -o init/mounts.o init/do_mounts.o
>  init/do_mounts_initrd.o init/mounts.o: No such file or directory
> make[1]: *** [init/mounts.o] Error 1
> make: *** [init] Error 2
>
> glibc is 2.14.1-r3, which otherwise works perfectly, so I don't
> think it's the reason.
> I cleared ccache and rebuilt the kernel sources, to no avail.
>
> .config is in attachments.
>
> Maybe someone could give me a hint, I need that kernel really
> badly and hopefully soon.
>
> kind regards
>
> michael
>

Make sure you're not running out of space or inodes on the mounted
filesystem.

(I once ran out of inodes even when freespace is still large. Now I do
compiles -- kernel or otherwise -- on reiserfs)

Rgds,

[-- Attachment #2: Type: text/html, Size: 3209 bytes --]

Re: [gentoo-user] Are those "green" drives any good?

[Norman Invasion]

On 9 May 2012 04:47, Dale <rdalek1967@gmail.com> wrote:
> Hi,
>
> As some know, I'm planning to buy me a LARGE hard drive to put all my
> videos on, eventually.  The prices are coming down now.  I keep seeing
> these "green" drives that are made by just about every company nowadays.
>  When comparing them to a non "green" drive, do they hold up as good?
> Are they as dependable as a plain drive?  I guess they are more
> efficient and I get that but do they break quicker, more often or no
> difference?
>
> I have noticed that they tend to spin slower and are cheaper.  That much
> I have figured out.  Other than that, I can't see any other difference.
>  Data speeds seem to be about the same.
>

They have an ugly tendency to nod off at 6 second intervals.
This runs up "193 Load_Cycle_Count" unacceptably: as many
as a few hundred thousand in a year & a million cycles is
getting close to the lifetime limit on most hard drives.  I end
up running some iteration of
# hdparm -B 255 /dev/sda
every boot.

Re: [gentoo-user] Are those "green" drives any good?

[Mark Knecht]

On Thu, May 10, 2012 at 9:20 AM, Norman Invasion
<invasivenorman@gmail.com> wrote:
> On 9 May 2012 04:47, Dale <rdalek1967@gmail.com> wrote:
>> Hi,
>>
>> As some know, I'm planning to buy me a LARGE hard drive to put all my
>> videos on, eventually.  The prices are coming down now.  I keep seeing
>> these "green" drives that are made by just about every company nowadays.
>>  When comparing them to a non "green" drive, do they hold up as good?
>> Are they as dependable as a plain drive?  I guess they are more
>> efficient and I get that but do they break quicker, more often or no
>> difference?
>>
>> I have noticed that they tend to spin slower and are cheaper.  That much
>> I have figured out.  Other than that, I can't see any other difference.
>>  Data speeds seem to be about the same.
>>
>
> They have an ugly tendency to nod off at 6 second intervals.
> This runs up "193 Load_Cycle_Count" unacceptably: as many
> as a few hundred thousand in a year & a million cycles is
> getting close to the lifetime limit on most hard drives.  I end
> up running some iteration of
> # hdparm -B 255 /dev/sda
> every boot.
>

Very true about the 193 count. Here's a drive in a system that was
built in Jan., 2010 so it's a bit over 2 years old at this point. It's
on 24/7 and not rebooted except for more major updates, etc. My tests
say the drive spins down and starts back up every 2 minutes and has
been doing so for about 28 months. IIRC the 193 spec on this drive was
something like 300000 max with the drive currently clocking in at
700488. I don't see any evidence that it's going to fail but I am
trying to make sure it's backed up often. Being that it's gone >2x at
this point I will swap the drive out in the early summer no matter
what. This week I'll be visiting where the machine is so I'm going to
put a backup drive in the box to get ready.

- Mark


gandalf ~ # smartctl -a /dev/sda
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.2.12-gentoo] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Green (Adv. Format)
Device Model:     WDC WD10EARS-00Y5B1
Serial Number:    WD-WCAV55464493
LU WWN Device Id: 5 0014ee 2ae6b5ffe
Firmware Version: 80.00A80
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Thu May 10 10:53:59 2012 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (19800) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection
on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 228) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x3031) SCT Status supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE
UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail
Always       -       0
  3 Spin_Up_Time            0x0027   131   128   021    Pre-fail
Always       -       6441
  4 Start_Stop_Count        0x0032   100   100   000    Old_age
Always       -       65
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail
Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age
Always       -       0
  9 Power_On_Hours          0x0032   074   074   000    Old_age
Always       -       19316
 10 Spin_Retry_Count        0x0032   100   253   000    Old_age
Always       -       0
 11 Calibration_Retry_Count 0x0032   100   253   000    Old_age
Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age
Always       -       63
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age
Always       -       14
193 Load_Cycle_Count        0x0032   001   001   000    Old_age
Always       -       700488
194 Temperature_Celsius     0x0022   120   113   000    Old_age
Always       -       27
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age
Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age
Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age
Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age
Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age
Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining
LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     11655         -
# 2  Extended offline    Completed without error       00%      8797         -
# 3  Short offline       Completed without error       00%      8794         -
# 4  Extended offline    Completed without error       00%      1009         -
# 5  Extended offline    Completed without error       00%       388         -
# 6  Short offline       Completed without error       00%       376         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

gandalf ~ #

Re: [gentoo-user] Are those "green" drives any good?

[Norman Invasion]

On 10 May 2012 14:01, Mark Knecht <markknecht@gmail.com> wrote:
> On Thu, May 10, 2012 at 9:20 AM, Norman Invasion
> <invasivenorman@gmail.com> wrote:
>> On 9 May 2012 04:47, Dale <rdalek1967@gmail.com> wrote:
>>> Hi,
>>>
>>> As some know, I'm planning to buy me a LARGE hard drive to put all my
>>> videos on, eventually.  The prices are coming down now.  I keep seeing
>>> these "green" drives that are made by just about every company nowadays.
>>>  When comparing them to a non "green" drive, do they hold up as good?
>>> Are they as dependable as a plain drive?  I guess they are more
>>> efficient and I get that but do they break quicker, more often or no
>>> difference?
>>>
>>> I have noticed that they tend to spin slower and are cheaper.  That much
>>> I have figured out.  Other than that, I can't see any other difference.
>>>  Data speeds seem to be about the same.
>>>
>>
>> They have an ugly tendency to nod off at 6 second intervals.
>> This runs up "193 Load_Cycle_Count" unacceptably: as many
>> as a few hundred thousand in a year & a million cycles is
>> getting close to the lifetime limit on most hard drives.  I end
>> up running some iteration of
>> # hdparm -B 255 /dev/sda
>> every boot.
>>
>
> Very true about the 193 count. Here's a drive in a system that was
> built in Jan., 2010 so it's a bit over 2 years old at this point. It's
> on 24/7 and not rebooted except for more major updates, etc. My tests
> say the drive spins down and starts back up every 2 minutes and has
> been doing so for about 28 months. IIRC the 193 spec on this drive was
> something like 300000 max with the drive currently clocking in at
> 700488. I don't see any evidence that it's going to fail but I am
> trying to make sure it's backed up often. Being that it's gone >2x at
> this point I will swap the drive out in the early summer no matter
> what. This week I'll be visiting where the machine is so I'm going to
> put a backup drive in the box to get ready.
>

Yes, I just learned about this problem in 2009 or so, &
checked on my FreeBSD laptop, which turned out to be
at >400000.  It only made it another month or so before
having unrecoverable errors.

Now, I can't conclusively demonstrate that the 193
Load_Cycle_Count was somehow causitive, but I
gots my suspicions.  Many of 'em highly suspectable.

Re: [gentoo-user] Are those "green" drives any good?

[Mark Knecht]

On Thu, May 10, 2012 at 11:13 AM, Norman Invasion
<invasivenorman@gmail.com> wrote:
> On 10 May 2012 14:01, Mark Knecht <markknecht@gmail.com> wrote:
>> On Thu, May 10, 2012 at 9:20 AM, Norman Invasion
>> <invasivenorman@gmail.com> wrote:
>>> On 9 May 2012 04:47, Dale <rdalek1967@gmail.com> wrote:
>>>> Hi,
>>>>
>>>> As some know, I'm planning to buy me a LARGE hard drive to put all my
>>>> videos on, eventually.  The prices are coming down now.  I keep seeing
>>>> these "green" drives that are made by just about every company nowadays.
>>>>  When comparing them to a non "green" drive, do they hold up as good?
>>>> Are they as dependable as a plain drive?  I guess they are more
>>>> efficient and I get that but do they break quicker, more often or no
>>>> difference?
>>>>
>>>> I have noticed that they tend to spin slower and are cheaper.  That much
>>>> I have figured out.  Other than that, I can't see any other difference.
>>>>  Data speeds seem to be about the same.
>>>>
>>>
>>> They have an ugly tendency to nod off at 6 second intervals.
>>> This runs up "193 Load_Cycle_Count" unacceptably: as many
>>> as a few hundred thousand in a year & a million cycles is
>>> getting close to the lifetime limit on most hard drives.  I end
>>> up running some iteration of
>>> # hdparm -B 255 /dev/sda
>>> every boot.
>>>
>>
>> Very true about the 193 count. Here's a drive in a system that was
>> built in Jan., 2010 so it's a bit over 2 years old at this point. It's
>> on 24/7 and not rebooted except for more major updates, etc. My tests
>> say the drive spins down and starts back up every 2 minutes and has
>> been doing so for about 28 months. IIRC the 193 spec on this drive was
>> something like 300000 max with the drive currently clocking in at
>> 700488. I don't see any evidence that it's going to fail but I am
>> trying to make sure it's backed up often. Being that it's gone >2x at
>> this point I will swap the drive out in the early summer no matter
>> what. This week I'll be visiting where the machine is so I'm going to
>> put a backup drive in the box to get ready.
>>
>
> Yes, I just learned about this problem in 2009 or so, &
> checked on my FreeBSD laptop, which turned out to be
> at >400000.  It only made it another month or so before
> having unrecoverable errors.
>
> Now, I can't conclusively demonstrate that the 193
> Load_Cycle_Count was somehow causitive, but I
> gots my suspicions.  Many of 'em highly suspectable.
>

It's part of the 'Wear Out Failure' part of the Bathtub Curve posted
in the last few days. That said, some Toyotas go 100K miles, and
others go 500K miles. Same car, same spec, same production line,
different owners, different roads, different climates, etc.

It's not possible to absolutely know when any drive will fail. I
suspect that the 300K spec is just that, a spec. They'd replace the
drive if it failed at 299,999 and wouldn't replace it at 300,001. That
said, they don't want to spec thing too tightly, and I doubt many
people make a purchasing decision on a spec like this, so for the vast
majority of drives most likely they'd do far more than 300K.

At 2 minutes per count on that specific WD Green Drive, if a home
machine is turned on for instance 5 hours a day (6PM to 11PM) then
300K count equates to around 6 years. To me that seems pretty generous
for a low cost home machine. However for a 24/7 production server it's
a pretty fast replacement schedule.

Here's data for my 500GB WD RAID Edition drives in my compute server
here. It's powered down almost every night but doesn't suffer from the
same firmware issues. The machine was built in April, 2010, so it's a
bit of 2 years old.  Note that it's been powered on less than 1/2 the
number of hours but only has a 193 count of 907 vs > 700000!

Cheers,
Mark


c2stable ~ # smartctl -a /dev/sda
smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.2.12-gentoo] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital RE3 Serial ATA
Device Model:     WDC WD5002ABYS-02B1B0
Serial Number:    WD-WCASYA846988
LU WWN Device Id: 5 0014ee 2042c3477
Firmware Version: 02.03B03
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Thu May 10 11:45:45 2012 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x84) Offline data collection activity
                                        was suspended by an
interrupting command from host.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                ( 9480) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection
on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test
supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before
entering
                                        power-saving mode.
                                        Supports SMART auto save
timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging
supported.
Short self-test routine
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 112) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x303f) SCT Status supported.
                                        SCT Error Recovery Control
supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE
UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail
Always       -       0
  3 Spin_Up_Time            0x0027   239   235   021    Pre-fail
Always       -       1050
  4 Start_Stop_Count        0x0032   100   100   000    Old_age
Always       -       935
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail
Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age
Always       -       0
  9 Power_On_Hours          0x0032   091   091   000    Old_age
Always       -       7281
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age
Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age
Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age
Always       -       933
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age
Always       -       27
193 Load_Cycle_Count        0x0032   200   200   000    Old_age
Always       -       907
194 Temperature_Celsius     0x0022   106   086   000    Old_age
Always       -       41
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age
Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age
Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age
Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age
Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age
Offline      -       0

Re: [gentoo-user] Are those "green" drives any good?

[David Haller]

Hello,

On Thu, 10 May 2012, Mark Knecht wrote:
>On Thu, May 10, 2012 at 9:20 AM, Norman Invasion
><invasivenorman@gmail.com> wrote:
>> They have an ugly tendency to nod off at 6 second intervals.
>> This runs up "193 Load_Cycle_Count" unacceptably: as many
>> as a few hundred thousand in a year & a million cycles is
>> getting close to the lifetime limit on most hard drives.  I end
>> up running some iteration of
>> # hdparm -B 255 /dev/sda
>
>Very true about the 193 count.

There was some bug, IIRC.
http://jeanbruenn.info/2011/01/23/wd-green-discs-and-the-problem-in-linux-load-cycle-count/

and search for 'linux Load_Cycle_Count' using your favorite search site.

HTH,
-dnh

-- 
Well, merry frelling christmas!    -- Aeryn Sun, Farscape - 4x13 - Terra Firma

Re: [gentoo-user] Are those "green" drives any good?

[David Haller]

Hello,

On Wed, 09 May 2012, Dale wrote:
>As some know, I'm planning to buy me a LARGE hard drive to put all my
>videos on, eventually.  The prices are coming down now.  I keep seeing
>these "green" drives that are made by just about every company nowadays.
> When comparing them to a non "green" drive, do they hold up as good?
>Are they as dependable as a plain drive?  I guess they are more
>efficient and I get that but do they break quicker, more often or no
>difference?

Basically: they run a 5400 min^-1, the "normal" ones at 7200 min^-1
and the green use less power. Years ago, a normal drive took 10-13W
running, up to 27W during spinup. Now it's IIRC 4-6W running and some
more during spinup (haven't seen any figures lately).

>I have noticed that they tend to spin slower and are cheaper.  That much
>I have figured out.  Other than that, I can't see any other difference.
> Data speeds seem to be about the same.

Yes.

>Please, no brand wars.  I may get a WD, Maxtor, Samsung or some other
>brand.

Hm. You've been out of the loop. Of those 3, only one remains.
Maxtor was bought by Seagate some years ago and Samsung this year,
there's now appearing the first Samsung drives from Seagate (I got one
of those, odd labeling, sold as
2000GB Seagate Barracuda Green ST2000DL004 (HD204UI)

So, now there's only 3.5 to 4 Manufacturers left: WD, Seagate, Hitachi
and Toshiba (and Fujitsu?) manufacturing only 2.5" laptop drives.

Other sellers like cnMemory etc. used to repackage Samsung drives
(IIRC the othere Manufatureres did not allow that), I wonder what
those will do now that Samsung is bought up by Seagate.

HTH,
-dnh

-- 
I am supposed to be the info provider, so here is my answer:
42
By the way: What is the question?         -- Johannes Meixner
        in https://bugzilla.novell.com/show_bug.cgi?id=190173

Re: [gentoo-user] Are those "green" drives any good?

[David Haller]

Hello,

On Wed, 09 May 2012, Alan McKinnon wrote:
>One thing we have noticed is that Samsung's recent model are not very
>"green", they spin up slowly, use lots of power and make a racket when
>spinning. But they do work.

Which ones? I've got one of all Models of the last years, and to none
applies what you're saying.

-dnh

-- 
If breathing required conscious thought, the world population would be
on a sharp decline.                                    -- Greg Andrews

Re: [gentoo-user] Are those "green" drives any good?

[David Haller]

Hello,

On Wed, 09 May 2012, Dale wrote:
>While on the thread.  Has anyone had any sort of luck with the
>recertified drives?

Avoid them.

-dnh

-- 
Well I wish you'd just tell me rather than try to engage my enthusiasm.
                                                             -- Marvin

Re: [gentoo-user] make of gentoo-sources-3.2.12 fails

[Michael Scherer]

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

my /usr-partition is at 17% and all other ebuilds, like a new install of netbeans 7.1, run just fine,
so I doubt this could be the reason, but I'll check anyway.

thanks

michael

-- 
Michael Scherer
Univ.klinik f. Psychiatrie
email: michael.scherer@meduniwien.ac.at
phone: +43 6991 941 22 54

  ----- Original Message ----- 
  From: Pandu Poluan 
  To: gentoo-user@lists.gentoo.org 
  Sent: Thursday, 10 May, 2012 16:50
  Subject: Re: [gentoo-user] make of gentoo-sources-3.2.12 fails



  On May 10, 2012 9:27 PM, "Michael Scherer" <a6702894@unet.univie.ac.at> wrote:
  >
  > Hi all,
  >
  > after downloading the 3.2.12-sources everything went fine
  > for a couple of weeks, I compiled them a couple of times,
  > but suddenly, maybe because of some world-updates, errors
  > started to accumulate, first it could do make but no modules,
  > then kernel make made it almost and now I'm stuck with this
  > rather short make output:
  >
  >  HOSTCC  scripts/basic/fixdep
  >  HOSTCC  scripts/kconfig/conf.o
  >  HOSTCC  scripts/kconfig/zconf.tab.o
  > scripts/kconfig/zconf.tab.c: In function ‘header_print_comment’:
  > scripts/kconfig/confdata.c:540:10: warning: ignoring return value of
  >  ‘fwrite’, declared with attribute warn_unused_result
  >  scripts/kconfig/zconf.tab.c: In function ‘kconfig_print_comment’:
  >  scripts/kconfig/confdata.c:467:10: warning: ignoring return value of
  >  ‘fwrite’, declared with attribute warn_unused_result HOSTLD
  >  scripts/kconfig/conf scripts/kconfig/conf --silentoldconfig Kconfig
  >  CHK     include/linux/version.h CHK     include/generated/utsrelease.h
  >  CC      kernel/bounds.s
  >  GEN     include/generated/bounds.h
  >  CC      arch/x86/kernel/asm-offsets.s
  >  GEN     include/generated/asm-offsets.h
  >  CALL    scripts/checksyscalls.sh
  >  CC      scripts/mod/empty.o
  >  HOSTCC  scripts/mod/mk_elfconfig
  >  MKELF   scripts/mod/elfconfig.h
  >  HOSTCC  scripts/mod/file2alias.o
  >  HOSTCC  scripts/mod/modpost.o
  >  HOSTCC  scripts/mod/sumversion.o
  >  HOSTLD  scripts/mod/modpost
  >  HOSTCC  scripts/kallsyms
  >  HOSTCC  scripts/pnmtologo
  >  HOSTCC  scripts/conmakehash
  >  HOSTCC  scripts/bin2c
  >  CC      init/main.o
  >  CHK     include/generated/compile.h
  >  CC      init/version.o
  >  CC      init/do_mounts.o
  >  CC      init/do_mounts_initrd.o
  >  LD      init/mounts.o
  > ls -Al -m elf_x86_64 -r -o init/mounts.o init/do_mounts.o
  >  init/do_mounts_initrd.o init/mounts.o: No such file or directory
  > make[1]: *** [init/mounts.o] Error 1
  > make: *** [init] Error 2
  >
  > glibc is 2.14.1-r3, which otherwise works perfectly, so I don't
  > think it's the reason.
  > I cleared ccache and rebuilt the kernel sources, to no avail.
  >
  > .config is in attachments.
  >
  > Maybe someone could give me a hint, I need that kernel really
  > badly and hopefully soon.
  >
  > kind regards
  >
  > michael
  >

  Make sure you're not running out of space or inodes on the mounted filesystem.

  (I once ran out of inodes even when freespace is still large. Now I do compiles -- kernel or otherwise -- on reiserfs)

  Rgds,


[-- Attachment #2: Type: text/html, Size: 5351 bytes --]

Re: [gentoo-user] Are those "green" drives any good?

[Mark Knecht]

On Wed, May 9, 2012 at 1:47 AM, Dale <rdalek1967@gmail.com> wrote:
> Hi,
>
> As some know, I'm planning to buy me a LARGE hard drive to put all my
> videos on, eventually.

Hi Dale,
   One thing I wanted to point out about the task you have in front of
you. There is a problem in your work statement here and it really
comes down to one single one letter word. That word was 'a', as in
"buy me _a_ LARGE hard drive"

   No matter what drive you purchase, and no matter how well you treat
it, they all fail eventually and you lose your movies & all the time
it takes to put it back together again. At a minimum, if you plan on
buying one to use then you need to buy a _second_ drive to do backups
of the first. You need to rsync that second drive on a regular basis
and then disconnect it and put it in a different place in the house,
or even better, store it in a safety deposit box to protect against
theft or your house burning down, etc.

   This sort of comment certainly goes for the system as a whole, but
at a seasoned Gentoo user I'm sure you're doing that already. ;-) Just
don't forget to do the same for this new drive.

Have fun,
Mark

Re: [gentoo-user] make of gentoo-sources-3.2.12 fails

[Stroller]

On 10 May 2012, at 15:20, Michael Scherer wrote:
> 
> References: <4FAA2F0D.8080900@gmail.com>
>         <4FAA595A.4040202@libertytrek.org>
>         <CAK2H+ec30vQ09U22vAc72hSQBJb2ZN5b25snH6-D3cDXrReHSA@mail.gmail.com>
>         <CAA2qdGW8UuF3H-CBiqn48f+Pboj3AhCT2WhDd1SwzE-g7z_MJg@mail.gmail.com>
> 
> after downloading the 3.2.12-sources everything went fine
> for a couple of weeks, I compiled them a couple of times,
> but suddenly, maybe because of some world-updates, errors
> started to accumulate, …


Please don't hijack threads like this:
 http://en.wikipedia.org/wiki/Thread_hijacking
 http://groups.google.com/group/linux.gentoo.user/msg/8a540add45e7e9b8?

 "It is irritating for people using thread-aware e-mail clients...
 In case you didn't know, it happens when you use "reply" for sending
 a new question instead of composing a "new" message."

Stroller.

Re: [gentoo-user] Are those "green" drives any good?

[Alan McKinnon]

On Thu, 10 May 2012 21:38:20 +0200
David Haller <gentoo@dhaller.de> wrote:

> Hello,
> 
> On Wed, 09 May 2012, Alan McKinnon wrote:
> >One thing we have noticed is that Samsung's recent model are not very
> >"green", they spin up slowly, use lots of power and make a racket
> >when spinning. But they do work.
> 
> Which ones? I've got one of all Models of the last years, and to none
> applies what you're saying.
> 
> -dnh
> 

I wasn't talking from my experience, I was talking from my developer
colleagues' experience. I'll find out which drive models they used.

-- 
Alan McKinnnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Are those "green" drives any good?

[Neil Bothwick]

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

On Thu, 10 May 2012 21:36:46 +0200, David Haller wrote:

> Basically: they run a 5400 min^-1, the "normal" ones at 7200 min^-1
> and the green use less power.

Some green drives run at 5900rpm.


-- 
Neil Bothwick

WinErr 01E: Timing error - Please wait. And wait. And wait. And wait.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Are those "green" drives any good?

[Dale]

napalm@squareownz.org wrote:
> On Thu, May 10, 2012 at 07:38:34AM -0500, Dale wrote:
>>
>> The default is to keep them all running and to not spin them down.  I
>> have never had a Linux OS to spin down a drive unless I set/told it to.
>>  You can do this tho.  The command and option is:
>>
>> hdparm -S /dev/sdX
>>
>> X would be the drive number.  There is also the -s option but it is not
>> recommended.
>>
>> There is also the -y and -Y options.  Before using ANY of these, read
>> the man page.  Each one has it uses and you need to know for sure which
>> one does what you want.
>>
>> Dale
>>
> 
> Awesome thanks very much, if I need to power down one of my drives I
> shall use hdparam!
> 
> Does the kernel keep even unmounted drives spinning by default?
> 
> Thank you Dale!


From my experience, as I posted I have never had Linux spin down a drive
without me telling it to or setting it up to do so.  If you want that to
be disabled as you have it in windows, the default settings should be
fine.

If you have a drive that is not being used, then you can use one of
those commands to shut it down to save power, wear and tear or whatever.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Re: [gentoo-user] Are those "green" drives any good?

[Paul Hartman]

On Thu, May 10, 2012 at 6:55 AM,  <napalm@squareownz.org> wrote:
>
> hum hum!
> I know that Windows does this by default (it annoys me so I disable it)
> but does linux disable or stop running the disks if they're inactive?
> I'm assuming there's an option somewhere - maybe just `unmount`!

Some drives cannot have this spindown "feature" disabled, because it
is a fixed value in their firmware in order to be "green"...

You can adjust the power management setting with hdparm, and on some
drives this allows disabling the spindown or disabling power
management altogether.

On my HDDs, I cannot disable APM but I can disable spindown by
changing the power-saving level to 254. I have a script in
/etc/local.d/ which calls:

hdparm -B 254 /dev/sd[abcdef]

at boot time.

To quote the hdparm manpage:

"A low value means aggressive power  management and a high value means
better performance.  Possible settings range from values 1 through 127
(which permit spin-down), and values 128 through 254 (which do not
permit spin-down).  The highest degree of power  management is
attained  with  a setting of 1, and the highest I/O performance with a
setting of 254.  A value of 255 tells hdparm to disable Advanced Power
Management altogether on the drive (not all drives support  disabling
it,  but most do)."

Re: [gentoo-user] Are those "green" drives any good?

[Neil Bothwick]

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

On Thu, 10 May 2012 17:53:27 -0500, Paul Hartman wrote:

> On my HDDs, I cannot disable APM but I can disable spindown by
> changing the power-saving level to 254. I have a script in
> /etc/local.d/ which calls:

You don't need a script, add the options you need to /etc/conf.d/hdparm
and add hdparm to the default runlevel.

> hdparm -B 254 /dev/sd[abcdef]

That doesn't work with my WD WD20EARX drives, which just report APM
disabled when I run it.


-- 
Neil Bothwick

Eagles may soar, but Wombles don't get sucked into jet engines

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] make of gentoo-sources-3.2.12 fails

[Michael Scherer]

I'm always replying to gentoo-user@lists.gentoo.org and I'm not aware I ever used
one of the addresses you mentioned below. I'm rather new to this forum, so it's
entirely possible I did something wrong somewhere, so please tell me where else
I should post my replies.
And if you feel the urge to correct me on my postings you might as well post some
advice on my problem too.

michael

-- 
Michael Scherer
Univ.klinik f. Psychiatrie
email: michael.scherer@meduniwien.ac.at
phone: +43 6991 941 22 54

----- Original Message ----- 
From: "Stroller" <stroller@stellar.eclipse.co.uk>
To: <gentoo-user@lists.gentoo.org>
Sent: Thursday, 10 May, 2012 23:08
Subject: Re: [gentoo-user] make of gentoo-sources-3.2.12 fails



On 10 May 2012, at 15:20, Michael Scherer wrote:
>
> References: <4FAA2F0D.8080900@gmail.com>
>         <4FAA595A.4040202@libertytrek.org>
>         <CAK2H+ec30vQ09U22vAc72hSQBJb2ZN5b25snH6-D3cDXrReHSA@mail.gmail.com>
>         <CAA2qdGW8UuF3H-CBiqn48f+Pboj3AhCT2WhDd1SwzE-g7z_MJg@mail.gmail.com>
>
> after downloading the 3.2.12-sources everything went fine
> for a couple of weeks, I compiled them a couple of times,
> but suddenly, maybe because of some world-updates, errors
> started to accumulate, …


Please don't hijack threads like this:
 http://en.wikipedia.org/wiki/Thread_hijacking
 http://groups.google.com/group/linux.gentoo.user/msg/8a540add45e7e9b8?

 "It is irritating for people using thread-aware e-mail clients...
 In case you didn't know, it happens when you use "reply" for sending
 a new question instead of composing a "new" message."

Stroller.

Re: [gentoo-user] Are those "green" drives any good?

[David Haller]

Hello,

On Fri, 11 May 2012, Neil Bothwick wrote:
>On Thu, 10 May 2012 17:53:27 -0500, Paul Hartman wrote:
>> On my HDDs, I cannot disable APM but I can disable spindown by
>> changing the power-saving level to 254. I have a script in
>> /etc/local.d/ which calls:
>
>You don't need a script, add the options you need to /etc/conf.d/hdparm
>and add hdparm to the default runlevel.
>
>> hdparm -B 254 /dev/sd[abcdef]
>
>That doesn't work with my WD WD20EARX drives, which just report APM
>disabled when I run it.

Oh boy, we did get confused in this thread, did we?

RTFM hdparm.

a) Disk APM has usually only 3 settings, and only controls the
   "agressiveness" or the speed of how seeks are done, i.e. how fast
   the head moves seeking from track to track.
    0-127       slow
    128-254     fast
    255         default
   At least some manufacturers disable this (IIRC e.g. Seagate,
   lock it to "slow" on the "green" disks and fast on enterprise.

b) spindown is a totally unrelated feature, which is can be set by
   using 'hdparm -S'. I have about 20 disks in two boxen, one of them
   a WD 20xxEARS, and _NONE_ spin down (until shutdown).

   Have a look into your /etc/pm-profiler/{YOUR_PROFILE} (not sure if
   that's gentoo standard, I only have a very minimal gentoo
   installed). I've e.g. copied the "Balanced Low Latency" profile but
   set
    SATA_ALPM="max_performance"
   In the "powersaving" you get
    SATA_ALPM="min_power"
   which sets (via hdparm -S) the disks to spindown after whatever
   seconds (20s? I don't know).

Anyway, there is some stuff setting disk-spindown timeouts. So, choose
and/or adjust pm/upower config and/or set spindown time via 'hdparm
-S', with pm-profiler, upower, init-script, whatever.

BTW: 'hdparm -S 0' disables spindown.

HTH,
-dnh, with a seriously outdated gentoo installed only in parallel, but
    I have a lot of disks and know hdparm a bit ;)

-- 
When the SysAdmin answers the phone politely, say "sorry", hang up and
run awaaaaay!
        Informal advice to users at Karolinska Institutet, 1993-1994

Re: [gentoo-user] Are those "green" drives any good?

[Bill Kenworthy]

On Thu, 2012-05-10 at 12:20 -0400, Norman Invasion wrote:
> On 9 May 2012 04:47, Dale <rdalek1967@gmail.com> wrote:
> > Hi,
> >
> > As some know, I'm planning to buy me a LARGE hard drive to put all my
> > videos on, eventually.  The prices are coming down now.  I keep seeing
> > these "green" drives that are made by just about every company nowadays.
> >  When comparing them to a non "green" drive, do they hold up as good?
> > Are they as dependable as a plain drive?  I guess they are more
> > efficient and I get that but do they break quicker, more often or no
> > difference?
> >
> > I have noticed that they tend to spin slower and are cheaper.  That much
> > I have figured out.  Other than that, I can't see any other difference.
> >  Data speeds seem to be about the same.
> >
> 
> They have an ugly tendency to nod off at 6 second intervals.
> This runs up "193 Load_Cycle_Count" unacceptably: as many
> as a few hundred thousand in a year & a million cycles is
> getting close to the lifetime limit on most hard drives.  I end
> up running some iteration of
> # hdparm -B 255 /dev/sda
> every boot.
> 

hdparm installs an init script with a /etc/conf.d/hdparm file which
allows you to set things up at whatever run level you are using.  Also
beware things like "laptopmode" which take over rewriting the kernel and
harddrive parameters for dynamic power saving (i.e., different between
running on battery as to from mains) - really does work but can kill a
drive with Load_Cycle_Counts so drive life can be foreshortened if you
get too zealous (i.e., very short spindown times and using a journalled
file system.

BillK

Re: [gentoo-user] make of gentoo-sources-3.2.12 fails

[Joshua Murphy]

On Thu, May 10, 2012 at 9:01 PM, Michael Scherer
<a6702894@unet.univie.ac.at> wrote:
> I'm always replying to gentoo-user@lists.gentoo.org and I'm not aware I ever
> used
> one of the addresses you mentioned below. I'm rather new to this forum, so
> it's
> entirely possible I did something wrong somewhere, so please tell me where
> else
> I should post my replies.
> And if you feel the urge to correct me on my postings you might as well post
> some
> advice on my problem too.
>
>
> michael
>
> --
> Michael Scherer
> Univ.klinik f. Psychiatrie
> email: michael.scherer@meduniwien.ac.at
> phone: +43 6991 941 22 54
>
>> ----- Original Message ----- From: "Stroller"
>> <stroller@stellar.eclipse.co.uk>
>> To: <gentoo-user@lists.gentoo.org>
>> Sent: Thursday, 10 May, 2012 23:08
>>
>> Subject: Re: [gentoo-user] make of gentoo-sources-3.2.12 fails
>>
>>
>>
>> On 10 May 2012, at 15:20, Michael Scherer wrote:
>>>
>>>
>>> References: <4FAA2F0D.8080900@gmail.com>
>>>        <4FAA595A.4040202@libertytrek.org>
>>>
>>>  <CAK2H+ec30vQ09U22vAc72hSQBJb2ZN5b25snH6-D3cDXrReHSA@mail.gmail.com>
>>>
>>>  <CAA2qdGW8UuF3H-CBiqn48f+Pboj3AhCT2WhDd1SwzE-g7z_MJg@mail.gmail.com>
>>>
>>> after downloading the 3.2.12-sources everything went fine
>>> for a couple of weeks, I compiled them a couple of times,
>>> but suddenly, maybe because of some world-updates, errors
>>> started to accumulate, …
>>
>>
>>
>> Please don't hijack threads like this:
>> http://en.wikipedia.org/wiki/Thread_hijacking
>> http://groups.google.com/group/linux.gentoo.user/msg/8a540add45e7e9b8?
>>
>> "It is irritating for people using thread-aware e-mail clients...
>> In case you didn't know, it happens when you use "reply" for sending
>> a new question instead of composing a "new" message."
>>
>> Stroller.
>>
>>

He pulled those addresses from the message headers that went out with
your initial question, which it appears you sent, aiming to start a
new thread of discussion on, by hitting reply in the midst of
"[gentoo-user] Are those "green" drives any good?" and changing the
subject. It's a quick way to get a message headed towards the list,
but it *does* throw clients that are better at thread tracking for a
bit of a loop (and makes it easy for your question to get lost in an
already 40+ message long thread). As for your initial question,
building from your config on a clean (distclean, no ccache, etc)
3.1.12 gentoo patched tree built rather quick and problem free on my
box here (using -j5 at that. My first guess was a race issue in a
parallel build)... You might find something notably different in your
versions of things, so here's what I'm running on there.

lanos linux-3.2.12-gentoo # emerge --info
Portage 2.1.10.49 (default/linux/amd64/10.0, gcc-4.5.3,
glibc-2.14.1-r3, 3.2.1-gentoo-r2-lanos x86_64)
=================================================================
System uname: Linux-3.2.1-gentoo-r2-lanos-x86_64-Intel-R-_Core-TM-2_Quad_CPU_Q6600_@_2.40GHz-with-gentoo-2.0.3
Timestamp of tree: Mon, 07 May 2012 17:30:01 +0000
app-shells/bash:          4.2_p20
dev-lang/python:          2.7.2-r3, 3.1.4-r3, 3.2.2
dev-util/pkgconfig:       0.26
sys-apps/baselayout:      2.0.3
sys-apps/openrc:          0.9.8.4
sys-apps/sandbox:         2.5
sys-devel/autoconf:       2.13, 2.68
sys-devel/automake:       1.11.1
sys-devel/binutils:       2.21.1-r1
sys-devel/gcc:            4.5.3-r2
sys-devel/gcc-config:     1.5-r2
sys-devel/libtool:        2.4-r1
sys-devel/make:           3.82-r1
sys-kernel/linux-headers: 3.1 (virtual/os-headers)
sys-libs/glibc:           2.14.1-r3

If you're running something newer somewhere, or vanilla-sources, or
somesuch I can poke around a bit and see if I can replicate your
troubles here, but I can't guarantee short timeframes... I've around
1k miles of travelling this weekend, half of which will be learning
quickly whether the car I just grabbed on ebay was a good idea or not.

-- 
Poison [BLX]
Joshua M. Murphy

Re: [gentoo-user] make of gentoo-sources-3.2.12 fails

[Alan McKinnon]

On Fri, 11 May 2012 03:01:39 +0200
"Michael Scherer" <a6702894@unet.univie.ac.at> wrote:

> I'm always replying to gentoo-user@lists.gentoo.org and I'm not aware
> I ever used one of the addresses you mentioned below. I'm rather new
> to this forum, so it's entirely possible I did something wrong
> somewhere, so please tell me where else I should post my replies.
> And if you feel the urge to correct me on my postings you might as
> well post some advice on my problem too.
> 
> michael
> 

gentoo-user@lists.gentoo.org is the correct address, but that's not the
mistake you made.

You started an entirely new thread of discussion by replying to an
existing message and changing the Subject line. Now, this doesn't do
what you thought it does. It continues an existing thread where the
Subject line just happens to have changed. Almost everyone here uses
intelligent mailers and this new thread is mixed up inside something
completely unrelated.

The correct thing to do when starting a new thread is to compose an
entirely new mail (not reply to an existing one and remove bits)

-- 
Alan McKinnnon
alan.mckinnon@gmail.com

Re: [gentoo-user] make of gentoo-sources-3.2.12 fails

[Michael Scherer]

On Fri, 11 May 2012 01:18:18 -0400
Joshua Murphy <poisonbl@gmail.com> wrote:

> On Thu, May 10, 2012 at 9:01 PM, Michael Scherer
> <a6702894@unet.univie.ac.at> wrote:
> > I'm always replying to gentoo-user@lists.gentoo.org and I'm not
> > aware I ever used
> > one of the addresses you mentioned below. I'm rather new to this
> > forum, so it's
> > entirely possible I did something wrong somewhere, so please tell
> > me where else
> > I should post my replies.
> > And if you feel the urge to correct me on my postings you might as
> > well post some
> > advice on my problem too.
> >
> >
> > michael
> >
> > --
> > Michael Scherer
> > Univ.klinik f. Psychiatrie
> > email: michael.scherer@meduniwien.ac.at
> > phone: +43 6991 941 22 54
> >
> >> ----- Original Message ----- From: "Stroller"
> >> <stroller@stellar.eclipse.co.uk>
> >> To: <gentoo-user@lists.gentoo.org>
> >> Sent: Thursday, 10 May, 2012 23:08
> >>
> >> Subject: Re: [gentoo-user] make of gentoo-sources-3.2.12 fails
> >>
> >>
> >>
> >> On 10 May 2012, at 15:20, Michael Scherer wrote:
> >>>
> >>>
> >>> References: <4FAA2F0D.8080900@gmail.com>
> >>>        <4FAA595A.4040202@libertytrek.org>
> >>>
> >>>  <CAK2H+ec30vQ09U22vAc72hSQBJb2ZN5b25snH6-D3cDXrReHSA@mail.gmail.com>
> >>>
> >>>  <CAA2qdGW8UuF3H-CBiqn48f+Pboj3AhCT2WhDd1SwzE-g7z_MJg@mail.gmail.com>
> >>>
> >>> after downloading the 3.2.12-sources everything went fine
> >>> for a couple of weeks, I compiled them a couple of times,
> >>> but suddenly, maybe because of some world-updates, errors
> >>> started to accumulate, …
> >>
> >>
> >>
> >> Please don't hijack threads like this:
> >> http://en.wikipedia.org/wiki/Thread_hijacking
> >> http://groups.google.com/group/linux.gentoo.user/msg/8a540add45e7e9b8?
> >>
> >> "It is irritating for people using thread-aware e-mail clients...
> >> In case you didn't know, it happens when you use "reply" for
> >> sending a new question instead of composing a "new" message."
> >>
> >> Stroller.
> >>
> >>
> 
> He pulled those addresses from the message headers that went out with
> your initial question, which it appears you sent, aiming to start a
> new thread of discussion on, by hitting reply in the midst of
> "[gentoo-user] Are those "green" drives any good?" and changing the
> subject. It's a quick way to get a message headed towards the list,
> but it *does* throw clients that are better at thread tracking for a
> bit of a loop (and makes it easy for your question to get lost in an
> already 40+ message long thread). As for your initial question,
> building from your config on a clean (distclean, no ccache, etc)
> 3.1.12 gentoo patched tree built rather quick and problem free on my
> box here (using -j5 at that. My first guess was a race issue in a
> parallel build)... You might find something notably different in your
> versions of things, so here's what I'm running on there.
> 
> lanos linux-3.2.12-gentoo # emerge --info
> Portage 2.1.10.49 (default/linux/amd64/10.0, gcc-4.5.3,
> glibc-2.14.1-r3, 3.2.1-gentoo-r2-lanos x86_64)
> =================================================================
> System uname:
> Linux-3.2.1-gentoo-r2-lanos-x86_64-Intel-R-_Core-TM-2_Quad_CPU_Q6600_@_2.40GHz-with-gentoo-2.0.3
> Timestamp of tree: Mon, 07 May 2012 17:30:01 +0000
> app-shells/bash:          4.2_p20 dev-lang/python:          2.7.2-r3,
> 3.1.4-r3, 3.2.2 dev-util/pkgconfig:       0.26
> sys-apps/baselayout:      2.0.3
> sys-apps/openrc:          0.9.8.4
> sys-apps/sandbox:         2.5
> sys-devel/autoconf:       2.13, 2.68
> sys-devel/automake:       1.11.1
> sys-devel/binutils:       2.21.1-r1
> sys-devel/gcc:            4.5.3-r2
> sys-devel/gcc-config:     1.5-r2
> sys-devel/libtool:        2.4-r1
> sys-devel/make:           3.82-r1
> sys-kernel/linux-headers: 3.1 (virtual/os-headers)
> sys-libs/glibc:           2.14.1-r3
> 
> If you're running something newer somewhere, or vanilla-sources, or
> somesuch I can poke around a bit and see if I can replicate your
> troubles here, but I can't guarantee short timeframes... I've around
> 1k miles of travelling this weekend, half of which will be learning
> quickly whether the car I just grabbed on ebay was a good idea or not.
> 

Hi all,

thanks for advice, I wont make the same error again.

I use plain old gentoo-sources, but for once I'll have a shot at
some other kernel, maybe this could give me at least a hint.
I'll check your versions, I already thought some update broke
the kernel compile. Hope I'll find something.

thanks again

michael

Re: [gentoo-user] make of gentoo-sources-3.2.12 fails

[Michael Scherer]

On Fri, 11 May 2012 01:18:18 -0400
Joshua Murphy <poisonbl@gmail.com> wrote:

> On Thu, May 10, 2012 at 9:01 PM, Michael Scherer
> <a6702894@unet.univie.ac.at> wrote:
> > I'm always replying to gentoo-user@lists.gentoo.org and I'm not
> > aware I ever used
> > one of the addresses you mentioned below. I'm rather new to this
> > forum, so it's
> > entirely possible I did something wrong somewhere, so please tell
> > me where else
> > I should post my replies.
> > And if you feel the urge to correct me on my postings you might as
> > well post some
> > advice on my problem too.
> >
> >
> > michael
> >
> > --
> > Michael Scherer
> > Univ.klinik f. Psychiatrie
> > email: michael.scherer@meduniwien.ac.at
> > phone: +43 6991 941 22 54
> >
> >> ----- Original Message ----- From: "Stroller"
> >> <stroller@stellar.eclipse.co.uk>
> >> To: <gentoo-user@lists.gentoo.org>
> >> Sent: Thursday, 10 May, 2012 23:08
> >>
> >> Subject: Re: [gentoo-user] make of gentoo-sources-3.2.12 fails
> >>
> >>
> >>
> >> On 10 May 2012, at 15:20, Michael Scherer wrote:
> >>>
> >>>
> >>> References: <4FAA2F0D.8080900@gmail.com>
> >>>        <4FAA595A.4040202@libertytrek.org>
> >>>
> >>>  <CAK2H+ec30vQ09U22vAc72hSQBJb2ZN5b25snH6-D3cDXrReHSA@mail.gmail.com>
> >>>
> >>>  <CAA2qdGW8UuF3H-CBiqn48f+Pboj3AhCT2WhDd1SwzE-g7z_MJg@mail.gmail.com>
> >>>
> >>> after downloading the 3.2.12-sources everything went fine
> >>> for a couple of weeks, I compiled them a couple of times,
> >>> but suddenly, maybe because of some world-updates, errors
> >>> started to accumulate, …
> >>
> >>
> >>
> >> Please don't hijack threads like this:
> >> http://en.wikipedia.org/wiki/Thread_hijacking
> >> http://groups.google.com/group/linux.gentoo.user/msg/8a540add45e7e9b8?
> >>
> >> "It is irritating for people using thread-aware e-mail clients...
> >> In case you didn't know, it happens when you use "reply" for
> >> sending a new question instead of composing a "new" message."
> >>
> >> Stroller.
> >>
> >>
> 
> He pulled those addresses from the message headers that went out with
> your initial question, which it appears you sent, aiming to start a
> new thread of discussion on, by hitting reply in the midst of
> "[gentoo-user] Are those "green" drives any good?" and changing the
> subject. It's a quick way to get a message headed towards the list,
> but it *does* throw clients that are better at thread tracking for a
> bit of a loop (and makes it easy for your question to get lost in an
> already 40+ message long thread). As for your initial question,
> building from your config on a clean (distclean, no ccache, etc)
> 3.1.12 gentoo patched tree built rather quick and problem free on my
> box here (using -j5 at that. My first guess was a race issue in a
> parallel build)... You might find something notably different in your
> versions of things, so here's what I'm running on there.
> 
> lanos linux-3.2.12-gentoo # emerge --info
> Portage 2.1.10.49 (default/linux/amd64/10.0, gcc-4.5.3,
> glibc-2.14.1-r3, 3.2.1-gentoo-r2-lanos x86_64)
> =================================================================
> System uname:
> Linux-3.2.1-gentoo-r2-lanos-x86_64-Intel-R-_Core-TM-2_Quad_CPU_Q6600_@_2.40GHz-with-gentoo-2.0.3
> Timestamp of tree: Mon, 07 May 2012 17:30:01 +0000
> app-shells/bash:          4.2_p20 dev-lang/python:          2.7.2-r3,
> 3.1.4-r3, 3.2.2 dev-util/pkgconfig:       0.26
> sys-apps/baselayout:      2.0.3
> sys-apps/openrc:          0.9.8.4
> sys-apps/sandbox:         2.5
> sys-devel/autoconf:       2.13, 2.68
> sys-devel/automake:       1.11.1
> sys-devel/binutils:       2.21.1-r1
> sys-devel/gcc:            4.5.3-r2
> sys-devel/gcc-config:     1.5-r2
> sys-devel/libtool:        2.4-r1
> sys-devel/make:           3.82-r1
> sys-kernel/linux-headers: 3.1 (virtual/os-headers)
> sys-libs/glibc:           2.14.1-r3
> 
> If you're running something newer somewhere, or vanilla-sources, or
> somesuch I can poke around a bit and see if I can replicate your
> troubles here, but I can't guarantee short timeframes... I've around
> 1k miles of travelling this weekend, half of which will be learning
> quickly whether the car I just grabbed on ebay was a good idea or not.
> 

I have the exact same hard- and software as described in your list,
but the result doesn't change. Below is the command that should create
mounts.o but for some reason can't make it:

init/.do_mounts.o.cmd:cmd_init/do_mounts.o := gcc -Wp,-MD,init/.do_mounts.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/include -I/usr/src/linux-3.2.12-gentoo/arch/x86/include -Iarch/x86/include/generated -Iinclude  -include /usr/src/linux-3.2.12-gentoo/include/linux/kconfig.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -march=k8 -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -fstack-protector -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -Wframe-larger-than=2048 -fno-omit-frame-pointer -fno-optimize-sibling-calls -fno-inline-functions-called-once -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -DCC_HAVE_ASM_GOTO    -D"KBUILD_STR(s)=\#s" -D"KBUILD_BASENAME=KBUILD_STR(do_mounts)"  -D"KBUILD_MODNAME=KBUILD_STR(mounts)" -c -o init/do_mounts.o init/do_mounts.c

The define for making mounts.o is there, but maybe you can find
something wrong where I can't.

Thanks

michael

[gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[walt]

On 05/10/2012 07:20 AM, Michael Scherer wrote:
> Hi all,
> 
> after downloading the 3.2.12-sources everything went fine
> for a couple of weeks, I compiled them a couple of times,
> but suddenly, maybe because of some world-updates, errors
> started to accumulate,

Yes, sounds like something is wrong with your build environment.

Have you run revdep-rebuild lately?  What about etc-update or
something equivalent to it?

Very unlikely suspects but very easy to rule out:
Correct /usr/src/linux symlink?  Recent fsck?

Hm, what else?

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Michael Scherer]

Yes, all of those. Other ebuilds run without troubles. That's what makes this failed
kernel build all the more mysterious. I've run out of options. Maybe a new kernel
release will help, but I need my box and the tweaks to .config, and I don't want
to wait, especially as I fear things might not go better even then.

regards

michael

-- 
Michael Scherer
Univ.klinik f. Psychiatrie
email: michael.scherer@meduniwien.ac.at
phone: +43 6991 941 22 54

----- Original Message ----- 
From: "walt" <w41ter@gmail.com>
To: <gentoo-user@lists.gentoo.org>
Sent: Saturday, 12 May, 2012 00:48
Subject: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails


> On 05/10/2012 07:20 AM, Michael Scherer wrote:
>> Hi all,
>> 
>> after downloading the 3.2.12-sources everything went fine
>> for a couple of weeks, I compiled them a couple of times,
>> but suddenly, maybe because of some world-updates, errors
>> started to accumulate,
> 
> Yes, sounds like something is wrong with your build environment.
> 
> Have you run revdep-rebuild lately?  What about etc-update or
> something equivalent to it?
> 
> Very unlikely suspects but very easy to rule out:
> Correct /usr/src/linux symlink?  Recent fsck?
> 
> Hm, what else?
> 
> 
>

Re: [gentoo-user] Are those "green" drives any good?

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 10045 bytes --]

On Thursday 10 May 2012 19:51:14 Mark Knecht wrote:
> On Thu, May 10, 2012 at 11:13 AM, Norman Invasion
> 
> <invasivenorman@gmail.com> wrote:
> > On 10 May 2012 14:01, Mark Knecht <markknecht@gmail.com> wrote:
> >> On Thu, May 10, 2012 at 9:20 AM, Norman Invasion
> >> 
> >> <invasivenorman@gmail.com> wrote:
> >>> On 9 May 2012 04:47, Dale <rdalek1967@gmail.com> wrote:
> >>>> Hi,
> >>>> 
> >>>> As some know, I'm planning to buy me a LARGE hard drive to put all my
> >>>> videos on, eventually.  The prices are coming down now.  I keep seeing
> >>>> these "green" drives that are made by just about every company
> >>>> nowadays. When comparing them to a non "green" drive, do they hold up
> >>>> as good? Are they as dependable as a plain drive?  I guess they are
> >>>> more efficient and I get that but do they break quicker, more often
> >>>> or no difference?
> >>>> 
> >>>> I have noticed that they tend to spin slower and are cheaper.  That
> >>>> much I have figured out.  Other than that, I can't see any other
> >>>> difference. Data speeds seem to be about the same.
> >>> 
> >>> They have an ugly tendency to nod off at 6 second intervals.
> >>> This runs up "193 Load_Cycle_Count" unacceptably: as many
> >>> as a few hundred thousand in a year & a million cycles is
> >>> getting close to the lifetime limit on most hard drives.  I end
> >>> up running some iteration of
> >>> # hdparm -B 255 /dev/sda
> >>> every boot.
> >> 
> >> Very true about the 193 count. Here's a drive in a system that was
> >> built in Jan., 2010 so it's a bit over 2 years old at this point. It's
> >> on 24/7 and not rebooted except for more major updates, etc. My tests
> >> say the drive spins down and starts back up every 2 minutes and has
> >> been doing so for about 28 months. IIRC the 193 spec on this drive was
> >> something like 300000 max with the drive currently clocking in at
> >> 700488. I don't see any evidence that it's going to fail but I am
> >> trying to make sure it's backed up often. Being that it's gone >2x at
> >> this point I will swap the drive out in the early summer no matter
> >> what. This week I'll be visiting where the machine is so I'm going to
> >> put a backup drive in the box to get ready.
> > 
> > Yes, I just learned about this problem in 2009 or so, &
> > checked on my FreeBSD laptop, which turned out to be
> > at >400000.  It only made it another month or so before
> > having unrecoverable errors.
> > 
> > Now, I can't conclusively demonstrate that the 193
> > Load_Cycle_Count was somehow causitive, but I
> > gots my suspicions.  Many of 'em highly suspectable.
> 
> It's part of the 'Wear Out Failure' part of the Bathtub Curve posted
> in the last few days. That said, some Toyotas go 100K miles, and
> others go 500K miles. Same car, same spec, same production line,
> different owners, different roads, different climates, etc.
> 
> It's not possible to absolutely know when any drive will fail. I
> suspect that the 300K spec is just that, a spec. They'd replace the
> drive if it failed at 299,999 and wouldn't replace it at 300,001. That
> said, they don't want to spec thing too tightly, and I doubt many
> people make a purchasing decision on a spec like this, so for the vast
> majority of drives most likely they'd do far more than 300K.
> 
> At 2 minutes per count on that specific WD Green Drive, if a home
> machine is turned on for instance 5 hours a day (6PM to 11PM) then
> 300K count equates to around 6 years. To me that seems pretty generous
> for a low cost home machine. However for a 24/7 production server it's
> a pretty fast replacement schedule.
> 
> Here's data for my 500GB WD RAID Edition drives in my compute server
> here. It's powered down almost every night but doesn't suffer from the
> same firmware issues. The machine was built in April, 2010, so it's a
> bit of 2 years old.  Note that it's been powered on less than 1/2 the
> number of hours but only has a 193 count of 907 vs > 700000!
> 
> Cheers,
> Mark
> 
> 
> c2stable ~ # smartctl -a /dev/sda
> smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.2.12-gentoo] (local build)
> Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
> 
> === START OF INFORMATION SECTION ===
> Model Family:     Western Digital RE3 Serial ATA
> Device Model:     WDC WD5002ABYS-02B1B0
> Serial Number:    WD-WCASYA846988
> LU WWN Device Id: 5 0014ee 2042c3477
> Firmware Version: 02.03B03
> User Capacity:    500,107,862,016 bytes [500 GB]
> Sector Size:      512 bytes logical/physical
> Device is:        In smartctl database [for details use: -P show]
> ATA Version is:   8
> ATA Standard is:  Exact ATA specification draft version not indicated
> Local Time is:    Thu May 10 11:45:45 2012 PDT
> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled
> 
> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: PASSED
> 
> General SMART Values:
> Offline data collection status:  (0x84) Offline data collection activity
>                                         was suspended by an
> interrupting command from host.
>                                         Auto Offline Data Collection:
> Enabled. Self-test execution status:      (   0) The previous self-test
> routine completed without error or no self-test has ever been run.
> Total time to complete Offline
> data collection:                ( 9480) seconds.
> Offline data collection
> capabilities:                    (0x7b) SMART execute Offline immediate.
>                                         Auto Offline data collection
> on/off support.
>                                         Suspend Offline collection upon new
>                                         command.
>                                         Offline surface scan supported.
>                                         Self-test supported.
>                                         Conveyance Self-test
> supported.
>                                         Selective Self-test supported.
> SMART capabilities:            (0x0003) Saves SMART data before
> entering
>                                         power-saving mode.
>                                         Supports SMART auto save
> timer.
> Error logging capability:        (0x01) Error logging supported.
>                                         General Purpose Logging
> supported.
> Short self-test routine
> recommended polling time:        (   2) minutes.
> Extended self-test routine
> recommended polling time:        ( 112) minutes.
> Conveyance self-test routine
> recommended polling time:        (   5) minutes.
> SCT capabilities:              (0x303f) SCT Status supported.
>                                         SCT Error Recovery Control
> supported.
>                                         SCT Feature Control supported.
>                                         SCT Data Table supported.
> 
> SMART Attributes Data Structure revision number: 16
> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE
> UPDATED  WHEN_FAILED RAW_VALUE
>   1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail
> Always       -       0
>   3 Spin_Up_Time            0x0027   239   235   021    Pre-fail
> Always       -       1050
>   4 Start_Stop_Count        0x0032   100   100   000    Old_age
> Always       -       935
>   5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail
> Always       -       0
>   7 Seek_Error_Rate         0x002e   200   200   000    Old_age
> Always       -       0
>   9 Power_On_Hours          0x0032   091   091   000    Old_age
> Always       -       7281
>  10 Spin_Retry_Count        0x0032   100   100   000    Old_age
> Always       -       0
>  11 Calibration_Retry_Count 0x0032   100   100   000    Old_age
> Always       -       0
>  12 Power_Cycle_Count       0x0032   100   100   000    Old_age
> Always       -       933
> 192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age
> Always       -       27
> 193 Load_Cycle_Count        0x0032   200   200   000    Old_age
> Always       -       907
> 194 Temperature_Celsius     0x0022   106   086   000    Old_age
> Always       -       41
> 196 Reallocated_Event_Count 0x0032   200   200   000    Old_age
> Always       -       0
> 197 Current_Pending_Sector  0x0032   200   200   000    Old_age
> Always       -       0
> 198 Offline_Uncorrectable   0x0030   200   200   000    Old_age
> Offline      -       0
> 199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age
> Always       -       0
> 200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age
> Offline      -       0

Is this 193 Load_Cycle_Count an issue only on the green drives?

I have a very old Compaq laptop here that shows:

# smartctl -A /dev/sda | egrep "Power_On|Load_Cycle"
  9 Power_On_Hours          0x0012   055   055   000    Old_age   Always       
-       19830
193 Load_Cycle_Count        0x0012   001   001   000    Old_age   Always       
-       1739734

Admittedly, there are some 60 errors on it (having been used extensively on 
bouncy trains, buses, aeroplanes, etc) but it is still refusing to die ...  
O_O

It is a Hitachi 20G 

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi Travelstar 80GN
Device Model:     IC25N020ATMR04-0
Serial Number:    MRX107K1DS623H
Firmware Version: MO1OAD5A
User Capacity:    20,003,880,960 bytes [20.0 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   6
ATA Standard is:  ATA/ATAPI-6 T13 1410D revision 3a
Local Time is:    Sat May 12 10:30:13 2012 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Are those "green" drives any good?

[Volker Armin Hemmann]

Am Samstag, 12. Mai 2012, 10:34:12 schrieb Mick:
> On Thursday 10 May 2012 19:51:14 Mark Knecht wrote:
> > On Thu, May 10, 2012 at 11:13 AM, Norman Invasion
> > 
> > <invasivenorman@gmail.com> wrote:
> > > On 10 May 2012 14:01, Mark Knecht <markknecht@gmail.com> wrote:
> > >> On Thu, May 10, 2012 at 9:20 AM, Norman Invasion
> > >> 
> > >> <invasivenorman@gmail.com> wrote:
> > >>> On 9 May 2012 04:47, Dale <rdalek1967@gmail.com> wrote:
> > >>>> Hi,
> > >>>> 
> > >>>> As some know, I'm planning to buy me a LARGE hard drive to put all my
> > >>>> videos on, eventually.  The prices are coming down now.  I keep
> > >>>> seeing
> > >>>> these "green" drives that are made by just about every company
> > >>>> nowadays. When comparing them to a non "green" drive, do they hold up
> > >>>> as good? Are they as dependable as a plain drive?  I guess they are
> > >>>> more efficient and I get that but do they break quicker, more often
> > >>>> or no difference?
> > >>>> 
> > >>>> I have noticed that they tend to spin slower and are cheaper.  That
> > >>>> much I have figured out.  Other than that, I can't see any other
> > >>>> difference. Data speeds seem to be about the same.
> > >>> 
> > >>> They have an ugly tendency to nod off at 6 second intervals.
> > >>> This runs up "193 Load_Cycle_Count" unacceptably: as many
> > >>> as a few hundred thousand in a year & a million cycles is
> > >>> getting close to the lifetime limit on most hard drives.  I end
> > >>> up running some iteration of
> > >>> # hdparm -B 255 /dev/sda
> > >>> every boot.
> > >> 
> > >> Very true about the 193 count. Here's a drive in a system that was
> > >> built in Jan., 2010 so it's a bit over 2 years old at this point. It's
> > >> on 24/7 and not rebooted except for more major updates, etc. My tests
> > >> say the drive spins down and starts back up every 2 minutes and has
> > >> been doing so for about 28 months. IIRC the 193 spec on this drive was
> > >> something like 300000 max with the drive currently clocking in at
> > >> 700488. I don't see any evidence that it's going to fail but I am
> > >> trying to make sure it's backed up often. Being that it's gone >2x at
> > >> this point I will swap the drive out in the early summer no matter
> > >> what. This week I'll be visiting where the machine is so I'm going to
> > >> put a backup drive in the box to get ready.
> > > 
> > > Yes, I just learned about this problem in 2009 or so, &
> > > checked on my FreeBSD laptop, which turned out to be
> > > at >400000.  It only made it another month or so before
> > > having unrecoverable errors.
> > > 
> > > Now, I can't conclusively demonstrate that the 193
> > > Load_Cycle_Count was somehow causitive, but I
> > > gots my suspicions.  Many of 'em highly suspectable.
> > 
> > It's part of the 'Wear Out Failure' part of the Bathtub Curve posted
> > in the last few days. That said, some Toyotas go 100K miles, and
> > others go 500K miles. Same car, same spec, same production line,
> > different owners, different roads, different climates, etc.
> > 
> > It's not possible to absolutely know when any drive will fail. I
> > suspect that the 300K spec is just that, a spec. They'd replace the
> > drive if it failed at 299,999 and wouldn't replace it at 300,001. That
> > said, they don't want to spec thing too tightly, and I doubt many
> > people make a purchasing decision on a spec like this, so for the vast
> > majority of drives most likely they'd do far more than 300K.
> > 
> > At 2 minutes per count on that specific WD Green Drive, if a home
> > machine is turned on for instance 5 hours a day (6PM to 11PM) then
> > 300K count equates to around 6 years. To me that seems pretty generous
> > for a low cost home machine. However for a 24/7 production server it's
> > a pretty fast replacement schedule.
> > 
> > Here's data for my 500GB WD RAID Edition drives in my compute server
> > here. It's powered down almost every night but doesn't suffer from the
> > same firmware issues. The machine was built in April, 2010, so it's a
> > bit of 2 years old.  Note that it's been powered on less than 1/2 the
> > number of hours but only has a 193 count of 907 vs > 700000!
> > 
> > Cheers,
> > Mark
> > 
> > 
> > c2stable ~ # smartctl -a /dev/sda
> > smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.2.12-gentoo] (local build)
> > Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
> > 
> > === START OF INFORMATION SECTION ===
> > Model Family:     Western Digital RE3 Serial ATA
> > Device Model:     WDC WD5002ABYS-02B1B0
> > Serial Number:    WD-WCASYA846988
> > LU WWN Device Id: 5 0014ee 2042c3477
> > Firmware Version: 02.03B03
> > User Capacity:    500,107,862,016 bytes [500 GB]
> > Sector Size:      512 bytes logical/physical
> > Device is:        In smartctl database [for details use: -P show]
> > ATA Version is:   8
> > ATA Standard is:  Exact ATA specification draft version not indicated
> > Local Time is:    Thu May 10 11:45:45 2012 PDT
> > SMART support is: Available - device has SMART capability.
> > SMART support is: Enabled
> > 
> > === START OF READ SMART DATA SECTION ===
> > SMART overall-health self-assessment test result: PASSED
> > 
> > General SMART Values:
> > Offline data collection status:  (0x84) Offline data collection activity
> > 
> >                                         was suspended by an
> > 
> > interrupting command from host.
> > 
> >                                         Auto Offline Data Collection:
> > Enabled. Self-test execution status:      (   0) The previous self-test
> > routine completed without error or no self-test has ever been run.
> > Total time to complete Offline
> > data collection:                ( 9480) seconds.
> > Offline data collection
> > capabilities:                    (0x7b) SMART execute Offline immediate.
> > 
> >                                         Auto Offline data collection
> > 
> > on/off support.
> > 
> >                                         Suspend Offline collection upon
> >                                         new
> >                                         command.
> >                                         Offline surface scan supported.
> >                                         Self-test supported.
> >                                         Conveyance Self-test
> > 
> > supported.
> > 
> >                                         Selective Self-test supported.
> > 
> > SMART capabilities:            (0x0003) Saves SMART data before
> > entering
> > 
> >                                         power-saving mode.
> >                                         Supports SMART auto save
> > 
> > timer.
> > Error logging capability:        (0x01) Error logging supported.
> > 
> >                                         General Purpose Logging
> > 
> > supported.
> > Short self-test routine
> > recommended polling time:        (   2) minutes.
> > Extended self-test routine
> > recommended polling time:        ( 112) minutes.
> > Conveyance self-test routine
> > recommended polling time:        (   5) minutes.
> > SCT capabilities:              (0x303f) SCT Status supported.
> > 
> >                                         SCT Error Recovery Control
> > 
> > supported.
> > 
> >                                         SCT Feature Control supported.
> >                                         SCT Data Table supported.
> > 
> > SMART Attributes Data Structure revision number: 16
> > Vendor Specific SMART Attributes with Thresholds:
> > ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE
> > UPDATED  WHEN_FAILED RAW_VALUE
> > 
> >   1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail
> > 
> > Always       -       0
> > 
> >   3 Spin_Up_Time            0x0027   239   235   021    Pre-fail
> > 
> > Always       -       1050
> > 
> >   4 Start_Stop_Count        0x0032   100   100   000    Old_age
> > 
> > Always       -       935
> > 
> >   5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail
> > 
> > Always       -       0
> > 
> >   7 Seek_Error_Rate         0x002e   200   200   000    Old_age
> > 
> > Always       -       0
> > 
> >   9 Power_On_Hours          0x0032   091   091   000    Old_age
> > 
> > Always       -       7281
> > 
> >  10 Spin_Retry_Count        0x0032   100   100   000    Old_age
> > 
> > Always       -       0
> > 
> >  11 Calibration_Retry_Count 0x0032   100   100   000    Old_age
> > 
> > Always       -       0
> > 
> >  12 Power_Cycle_Count       0x0032   100   100   000    Old_age
> > 
> > Always       -       933
> > 192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age
> > Always       -       27
> > 193 Load_Cycle_Count        0x0032   200   200   000    Old_age
> > Always       -       907
> > 194 Temperature_Celsius     0x0022   106   086   000    Old_age
> > Always       -       41
> > 196 Reallocated_Event_Count 0x0032   200   200   000    Old_age
> > Always       -       0
> > 197 Current_Pending_Sector  0x0032   200   200   000    Old_age
> > Always       -       0
> > 198 Offline_Uncorrectable   0x0030   200   200   000    Old_age
> > Offline      -       0
> > 199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age
> > Always       -       0
> > 200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age
> > Offline      -       0
> 
> Is this 193 Load_Cycle_Count an issue only on the green drives?
> 
> I have a very old Compaq laptop here that shows:
> 
> # smartctl -A /dev/sda | egrep "Power_On|Load_Cycle"
>   9 Power_On_Hours          0x0012   055   055   000    Old_age   Always
> -       19830
> 193 Load_Cycle_Count        0x0012   001   001   000    Old_age   Always
> -       1739734
> 
> Admittedly, there are some 60 errors on it (having been used extensively on
> bouncy trains, buses, aeroplanes, etc) but it is still refusing to die ...
> O_O
> 
> It is a Hitachi 20G
> 
> === START OF INFORMATION SECTION ===
> Model Family:     Hitachi Travelstar 80GN
> Device Model:     IC25N020ATMR04-0
> Serial Number:    MRX107K1DS623H
> Firmware Version: MO1OAD5A
> User Capacity:    20,003,880,960 bytes [20.0 GB]
> Sector Size:      512 bytes logical/physical
> Device is:        In smartctl database [for details use: -P show]
> ATA Version is:   6
> ATA Standard is:  ATA/ATAPI-6 T13 1410D revision 3a
> Local Time is:    Sat May 12 10:30:13 2012 BST
> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled
> 
> === START OF READ SMART DATA SECTION ===

SAMSUNG HD502IJ
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  
WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   100   100   051    Pre-fail  Always       
-       0
  3 Spin_Up_Time            0x0007   085   085   011    Pre-fail  Always       
-       5480
  4 Start_Stop_Count        0x0032   098   098   000    Old_age   Always       
-       1864
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       
-       0
  7 Seek_Error_Rate         0x000f   100   100   051    Pre-fail  Always       
-       0
  8 Seek_Time_Performance   0x0025   100   100   015    Pre-fail  Offline      -       
10814
  9 Power_On_Hours          0x0032   096   096   000    Old_age   Always       
-       20178
 10 Spin_Retry_Count        0x0033   100   100   051    Pre-fail  Always       
-       0
 11 Calibration_Retry_Count 0x0012   100   100   000    Old_age   Always       
-       0
 12 Power_Cycle_Count       0x0032   098   098   000    Old_age   Always       
-       1854
 13 Read_Soft_Error_Rate    0x000e   100   100   000    Old_age   Always       
-       0
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       
-       8
184 End-to-End_Error        0x0033   100   100   099    Pre-fail  Always       
-       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       
-       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       
-       0
190 Airflow_Temperature_Cel 0x0022   082   065   000    Old_age   Always       
-       18 (Min/Max 13/18)
194 Temperature_Celsius     0x0022   079   061   000    Old_age   Always       
-       21 (Min/Max 13/21)
195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   Always       
-       2587
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       
-       0
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       
-       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       
0
199 UDMA_CRC_Error_Count    0x003e   100   100   000    Old_age   Always       
-       0
200 Multi_Zone_Error_Rate   0x000a   100   100   000    Old_age   Always       
-       0
201 Soft_Read_Error_Rate    0x000a   253   253   000    Old_age   Always       
-       0


SAMSUNG HD753LJ:

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  
WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   100   100   051    Pre-fail  Always       
-       0
  3 Spin_Up_Time            0x0007   075   075   011    Pre-fail  Always       
-       8330
  4 Start_Stop_Count        0x0032   099   099   000    Old_age   Always       
-       1399
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       
-       0
  7 Seek_Error_Rate         0x000f   100   100   051    Pre-fail  Always       
-       0
  8 Seek_Time_Performance   0x0025   100   100   015    Pre-fail  Offline      -       
10041
  9 Power_On_Hours          0x0032   097   097   000    Old_age   Always       
-       16941
 10 Spin_Retry_Count        0x0033   100   100   051    Pre-fail  Always       
-       0
 11 Calibration_Retry_Count 0x0012   100   100   000    Old_age   Always       
-       0
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       
-       1397
 13 Read_Soft_Error_Rate    0x000e   100   100   000    Old_age   Always       
-       0
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       
-       0
184 End-to-End_Error        0x0033   100   100   000    Pre-fail  Always       
-       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       
-       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       
-       0
190 Airflow_Temperature_Cel 0x0022   081   065   000    Old_age   Always       
-       19 (Min/Max 12/19)
194 Temperature_Celsius     0x0022   077   064   000    Old_age   Always       
-       23 (Min/Max 12/23)
195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   Always       
-       1412
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       
-       0
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       
-       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       
0
199 UDMA_CRC_Error_Count    0x003e   100   100   000    Old_age   Always       
-       0
200 Multi_Zone_Error_Rate   0x000a   100   100   000    Old_age   Always       
-       0
201 Soft_Read_Error_Rate    0x000a   253   253   000    Old_age   Always       
-       0

i have some more disks, but those clocked the most hours.


-- 
#163933

[gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[walt]

On 05/10/2012 07:20 AM, Michael Scherer wrote:
>   LD      init/mounts.o
> ls -Al -m elf_x86_64 -r -o init/mounts.o init/do_mounts.o
>   init/do_mounts_initrd.o init/mounts.o: No such file or directory

Maybe that step is correct but it sure looks strange to me.  Looks
like 'ls' is being substituted for 'ld', maybe?  Is that a cut-and-
paste error?

Re: [gentoo-user] Are those "green" drives any good?

[Frank Steinmetzger]

On Thu, May 10, 2012 at 12:20:57PM -0400, Norman Invasion wrote:
> On 9 May 2012 04:47, Dale <rdalek1967@gmail.com> wrote:
> > Hi,
> >
> > As some know, I'm planning to buy me a LARGE hard drive to put all my
> > videos on, eventually.  The prices are coming down now.  I keep seeing
> > these "green" drives that are made by just about every company nowadays.
> >  When comparing them to a non "green" drive, do they hold up as good?
> > Are they as dependable as a plain drive?  I guess they are more
> > efficient and I get that but do they break quicker, more often or no
> > difference?
> >
> > I have noticed that they tend to spin slower and are cheaper.  That much
> > I have figured out.  Other than that, I can't see any other difference.
> >  Data speeds seem to be about the same.
> >
> 
> They have an ugly tendency to nod off at 6 second intervals.
> This runs up "193 Load_Cycle_Count" unacceptably: as many
> as a few hundred thousand in a year & a million cycles is
> getting close to the lifetime limit on most hard drives.  I end
> up running some iteration of
> # hdparm -B 255 /dev/sda
> every boot.

I bought my current internal laptop disk for Christmas 2008.  It's a Samsung
HM500JI (with 500 GB).  Early on I noticed that, according to smartctl, its
Load_Cycle_Count is increasing every 2 or 3 seconds.  I even asked Samsung
about this, but they either couldn't give any clue or didn't want to, b/c the
Serial Number is from Turkey, so not from the European market.

Anyhoo... I just checked the values:
Power on hours:    11500
Start/stop count:   2797
Power cycle count:  2197

But the load cycle count is at almost 12.3 million(!).  That just can't be
right.  I stopped believing that number a good while ago.


OTOH, I just became a bit nervous when looking at smartctl's output...
Reallocated sectors:        7 (threshold 10)
Calibration retry count: 1631
Load retry count:        1631
-- 
Gruß | Greetings | Qapla'
Please do not share anything from, with or about me with any Facebook service.

Humans lose most of their time trying to gain time.

Re: [gentoo-user] Are those "green" drives any good?

[David Haller]

Hello,

On Sat, 12 May 2012, Mick wrote:
>Is this 193 Load_Cycle_Count an issue only on the green drives?

AFAIK it was a firmware bug on some models.

>I have a very old Compaq laptop here that shows:
>
># smartctl -A /dev/sda | egrep "Power_On|Load_Cycle"
>  9 Power_On_Hours          0x0012   055   055   000    Old_age   Always       
>-       19830
>193 Load_Cycle_Count        0x0012   001   001   000    Old_age   Always       
>-       1739734

Laptop drives are _built_ for unloading frequently to protect the
drive from bumps and also to save power. Desktop drives are _not_
built for that.

So, don't worry.

HTH,
-dnh

-- 
Death: I am last minute stuff!

Re: [gentoo-user] Are those "green" drives any good?

[David Haller]

Hello,

On Sat, 12 May 2012, Frank Steinmetzger wrote:
>On Thu, May 10, 2012 at 12:20:57PM -0400, Norman Invasion wrote:
>> On 9 May 2012 04:47, Dale <rdalek1967@gmail.com> wrote:
>> > Hi,
>> >
>> > As some know, I'm planning to buy me a LARGE hard drive to put all my
>> > videos on, eventually.  The prices are coming down now.  I keep seeing
>> > these "green" drives that are made by just about every company nowadays.
>> >  When comparing them to a non "green" drive, do they hold up as good?
>> > Are they as dependable as a plain drive?  I guess they are more
>> > efficient and I get that but do they break quicker, more often or no
>> > difference?
>> >
>> > I have noticed that they tend to spin slower and are cheaper.  That much
>> > I have figured out.  Other than that, I can't see any other difference.
>> >  Data speeds seem to be about the same.
>> >
>> 
>> They have an ugly tendency to nod off at 6 second intervals.
>> This runs up "193 Load_Cycle_Count" unacceptably: as many
>> as a few hundred thousand in a year & a million cycles is
>> getting close to the lifetime limit on most hard drives.  I end
>> up running some iteration of
>> # hdparm -B 255 /dev/sda
>> every boot.
>
>I bought my current internal laptop disk for Christmas 2008.  It's a Samsung
>HM500JI (with 500 GB).  Early on I noticed that, according to smartctl, its
>Load_Cycle_Count is increasing every 2 or 3 seconds.  I even asked Samsung
>about this, but they either couldn't give any clue or didn't want to, b/c the
>Serial Number is from Turkey, so not from the European market.
>
>Anyhoo... I just checked the values:
>Power on hours:    11500
>Start/stop count:   2797
>Power cycle count:  2197
>
>But the load cycle count is at almost 12.3 million(!).  That just can't be
>right.  I stopped believing that number a good while ago.

As I said in another mail: laptop drives are built for frequent
unloading. Your number does seem a bit high though, that's about 1000
load cycles per hour...

>OTOH, I just became a bit nervous when looking at smartctl's output...
>Reallocated sectors:        7 (threshold 10)
>Calibration retry count: 1631
>Load retry count:        1631

That's not healty. c.f. http://en.wikipedia.org/wiki/S.M.A.R.T.

HTH,
-dnh

-- 
To resist the influence of others, knowledge of one's self is
most important.   -- Teal'C, Stargate SG-1, 9x14 - Stronghold

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Michael Scherer]

regrettably no. at this point make (correctly) assumes that mounts.o
should have been built, but it didn't.
sorry for my delayed replay, I've tried I lot of possibilities, needless
to say without success.

thanks

michael

-- 
Michael Scherer
Univ.klinik f. Psychiatrie
email: michael.scherer@meduniwien.ac.at
phone: +43 6991 941 22 54

----- Original Message ----- 
From: "walt" <w41ter@gmail.com>
To: <gentoo-user@lists.gentoo.org>
Sent: Saturday, 12 May, 2012 20:17
Subject: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails


> On 05/10/2012 07:20 AM, Michael Scherer wrote:
>>   LD      init/mounts.o
>> ls -Al -m elf_x86_64 -r -o init/mounts.o init/do_mounts.o
>>   init/do_mounts_initrd.o init/mounts.o: No such file or directory
> 
> Maybe that step is correct but it sure looks strange to me.  Looks
> like 'ls' is being substituted for 'ld', maybe?  Is that a cut-and-
> paste error?
> 
> 
> 
> 
> 
> 
> 
>

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[ny6p01]

A: Because it messes up the order in which people normally read text.

On Mon, May 14, 2012 at 03:44:31AM +0200, Michael Scherer wrote:

> regrettably no. at this point make (correctly) assumes that mounts.o
> should have been built, but it didn't.
> sorry for my delayed replay, I've tried I lot of possibilities, needless
> to say without success.
> 
> thanks
> 
> michael
> 
> -- 
> Michael Scherer
> Univ.klinik f. Psychiatrie
> email: michael.scherer@meduniwien.ac.at
> phone: +43 6991 941 22 54
> 
> ----- Original Message ----- 
> From: "walt" <w41ter@gmail.com>
> To: <gentoo-user@lists.gentoo.org>
> Sent: Saturday, 12 May, 2012 20:17
> Subject: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails
> 
> 
> > On 05/10/2012 07:20 AM, Michael Scherer wrote:
> >>   LD      init/mounts.o
> >> ls -Al -m elf_x86_64 -r -o init/mounts.o init/do_mounts.o
> >>   init/do_mounts_initrd.o init/mounts.o: No such file or directory
> > 
> > Maybe that step is correct but it sure looks strange to me.  Looks
> > like 'ls' is being substituted for 'ld', maybe?  Is that a cut-and-
> > paste error?

Q: Why is top-posting such a bad thing?

Terry

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Michael Scherer]

in my opinion it isn't. with top posting I see the newest message
immidiately, while otherwise I need page through sometimes
huge amounts of mostly obsolete comments.
where it's possible, I put my messages on top, and I've found
more than once forum-rules that require or at least recommend
top posting.
but I garantee that I will get flames, why I do this and urge me
to change my habits.
obviously this is an ingrained habit on gentoo-users, but from
now on I'm going follow my habits and damn the flames.

regards

michael

-- 
Michael Scherer
Univ.klinik f. Psychiatrie
email: michael.scherer@meduniwien.ac.at
phone: +43 6991 941 22 54

----- Original Message ----- 
From: <ny6p01@gmail.com>
To: <gentoo-user@lists.gentoo.org>
Sent: Monday, 14 May, 2012 04:13
Subject: Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails


> A: Because it messes up the order in which people normally read text.
> 
> On Mon, May 14, 2012 at 03:44:31AM +0200, Michael Scherer wrote:
> 
>> regrettably no. at this point make (correctly) assumes that mounts.o
>> should have been built, but it didn't.
>> sorry for my delayed replay, I've tried I lot of possibilities, needless
>> to say without success.
>> 
>> thanks
>> 
>> michael
>> 
>> -- 
>> Michael Scherer
>> Univ.klinik f. Psychiatrie
>> email: michael.scherer@meduniwien.ac.at
>> phone: +43 6991 941 22 54
>> 
>> ----- Original Message ----- 
>> From: "walt" <w41ter@gmail.com>
>> To: <gentoo-user@lists.gentoo.org>
>> Sent: Saturday, 12 May, 2012 20:17
>> Subject: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails
>> 
>> 
>> > On 05/10/2012 07:20 AM, Michael Scherer wrote:
>> >>   LD      init/mounts.o
>> >> ls -Al -m elf_x86_64 -r -o init/mounts.o init/do_mounts.o
>> >>   init/do_mounts_initrd.o init/mounts.o: No such file or directory
>> > 
>> > Maybe that step is correct but it sure looks strange to me.  Looks
>> > like 'ls' is being substituted for 'ld', maybe?  Is that a cut-and-
>> > paste error?
> 
> Q: Why is top-posting such a bad thing?
> 
> Terry
> 
>

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Alan McKinnon]

On Mon, 14 May 2012 17:26:44 +0200
"Michael Scherer" <a6702894@unet.univie.ac.at> wrote:

> in my opinion it isn't. with top posting I see the newest message
> immidiately, while otherwise I need page through sometimes
> huge amounts of mostly obsolete comments.
> where it's possible, I put my messages on top, and I've found
> more than once forum-rules that require or at least recommend
> top posting.
> but I garantee that I will get flames, why I do this and urge me
> to change my habits.
> obviously this is an ingrained habit on gentoo-users, but from
> now on I'm going follow my habits and damn the flames.


That is rather rude and completely ignores the stated preference of
many other people who were here before you. They set the de-facto
standard, not you.

You are running the risk of being plonked which strikes me as being
silly. You post here to get good answers, not to be ignored.

-- 
Alan McKinnnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[ny6p01]

On Mon, May 14, 2012 at 05:26:44PM +0200, Michael Scherer wrote:
> in my opinion it isn't. with top posting I see the newest message
> immidiately, while otherwise I need page through sometimes
> huge amounts of mostly obsolete comments.
> where it's possible, I put my messages on top, and I've found
> more than once forum-rules that require or at least recommend
> top posting.
> but I garantee that I will get flames, why I do this and urge me
> to change my habits.
> obviously this is an ingrained habit on gentoo-users, but from
> now on I'm going follow my habits and damn the flames.
> 
> regards
> 
> michael
> 
> -- 
> Michael Scherer
> Univ.klinik f. Psychiatrie
> email: michael.scherer@meduniwien.ac.at
> phone: +43 6991 941 22 54
> 
> ----- Original Message ----- 
> From: <ny6p01@gmail.com>
> To: <gentoo-user@lists.gentoo.org>
> Sent: Monday, 14 May, 2012 04:13
> Subject: Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails
> 
> 
> > A: Because it messes up the order in which people normally read text.
> > 
> > On Mon, May 14, 2012 at 03:44:31AM +0200, Michael Scherer wrote:
> > 
> >> regrettably no. at this point make (correctly) assumes that mounts.o
> >> should have been built, but it didn't.
> >> sorry for my delayed replay, I've tried I lot of possibilities, needless
> >> to say without success.
> >> 
> >> thanks
> >> 
> >> michael
> >> 
> >> -- 
> >> Michael Scherer
> >> Univ.klinik f. Psychiatrie
> >> email: michael.scherer@meduniwien.ac.at
> >> phone: +43 6991 941 22 54
> >> 
> >> ----- Original Message ----- 
> >> From: "walt" <w41ter@gmail.com>
> >> To: <gentoo-user@lists.gentoo.org>
> >> Sent: Saturday, 12 May, 2012 20:17
> >> Subject: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails
> >> 
> >> 
> >> > On 05/10/2012 07:20 AM, Michael Scherer wrote:
> >> >>   LD      init/mounts.o
> >> >> ls -Al -m elf_x86_64 -r -o init/mounts.o init/do_mounts.o
> >> >>   init/do_mounts_initrd.o init/mounts.o: No such file or directory
> >> > 
> >> > Maybe that step is correct but it sure looks strange to me.  Looks
> >> > like 'ls' is being substituted for 'ld', maybe?  Is that a cut-and-
> >> > paste error?
> > 
> > Q: Why is top-posting such a bad thing?

http://linux.sgms-centre.com/misc/netiquette.php

*******

Below are a set of rules by which you should try and abide whenever posting
to a public area such as USENET or a mailing list.  They are designed with
one thing in mind: being polite to your fellow netizens.  Failure to do so
can make you look at best inconsiderate, if not plain stupid, or even lead
more "seasoned" netizens to believe that you're trolling (deliberately
stirring up a fuss in order to draw attention to yourself and/or start up a
fight - or flamefest).  In the long run you'll just get yourself PLONKED
(added to people's killfiles so they no longer have to read what you have to
say), which is fairly counter-productive if your intentions are worthy.

You can avoid yourself this embarrassment (and everybody else's displeasure)
by following the basic rules described here:

...

9. DO NOT TOP-POST and DO trim your replies!!! Top-posting is the annoying
practice of replying to a message by typing your response above that to
which you are responding.  This is a _Bad Thing_ because your readers will
have to scroll down and extract the essential of the existing thread in
order to grasp the context of your reply, and then scroll back up again to
read your reply.  Posting a "me too" comment at the bottom of a 100+ line
message is no better because people, have to scroll all the way down through
100+ lines they've already read in order to see your one-liner.  One word
comes to mind for that: frustrating.  The generally accepted "right way" of
doing things is called "inline posting", whereby you insert your comments
straight after that on which you are commenting, having stripped  
unnecessary text from the original quoted text.  The end result is something
which makes much more sense because it reads like a conversation.

********

Remember, in a list, you are not only writing for the person who you are
responding to.  You are posting for whoever may be interested in the topic. 
While I appreciate that you may not benefit from top posting since you know
the context, this is not true for someone who has linked to your message or
who is reading it days, weeks or years later.  :)

Terry

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Allan Gottlieb]

On Mon, May 14 2012, Michael Scherer wrote:

> in my opinion it isn't. with top posting I see the newest message
> immidiately, while otherwise I need page through sometimes
> huge amounts of mostly obsolete comments.
> where it's possible, I put my messages on top, and I've found
> more than once forum-rules that require or at least recommend
> top posting.
> but I garantee that I will get flames, why I do this and urge me
> to change my habits.
> obviously this is an ingrained habit on gentoo-users, but from
> now on I'm going follow my habits and damn the flames.

You have forgotten that gentoo-user is a valuable archive site.
I keep many old msgs to use much later.  At that point a top to bottom
reading order is preferred.

Moreover, those who are most helpful here all prefer bottom (or in-line)
posting.  If you shun the wishes of a majority of the group and a vast
majority of the most-helpful users, you fate is not flames but
"ignoredom".  That seems to be a poor idea.

Your call
allan

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Dale]

Allan Gottlieb wrote:
> On Mon, May 14 2012, Michael Scherer wrote:
> 
>> in my opinion it isn't. with top posting I see the newest message
>> immidiately, while otherwise I need page through sometimes
>> huge amounts of mostly obsolete comments.
>> where it's possible, I put my messages on top, and I've found
>> more than once forum-rules that require or at least recommend
>> top posting.
>> but I garantee that I will get flames, why I do this and urge me
>> to change my habits.
>> obviously this is an ingrained habit on gentoo-users, but from
>> now on I'm going follow my habits and damn the flames.
> 
> You have forgotten that gentoo-user is a valuable archive site.
> I keep many old msgs to use much later.  At that point a top to bottom
> reading order is preferred.
> 
> Moreover, those who are most helpful here all prefer bottom (or in-line)
> posting.  If you shun the wishes of a majority of the group and a vast
> majority of the most-helpful users, you fate is not flames but
> "ignoredom".  That seems to be a poor idea.
> 
> Your call
> allan
> 
> 


I agree.  I have read even on here, been a while tho, where a email
address is blacklisted.  So OP, if you top post often enough then later
post a question, the person with the answer may never see your question
hence you will likely get no reply.   I have one person blacklisted
myself.  I have no clue if they come here or not.  It goes straight to
delete.  I think it bypasses the trash even.

For example:  Alan, Mike, Pandu, Mark, Neil and me are the top posters
on this list.  I will admit, if just Neil and Alan ignore your posts,
you got issues.  They are two VERY knowledgeable, and more importantly,
helpful people.  Most of their posts are helping others too, unlike some
of mine.   Another thing, they have been on this mailing for a long time
and they don't like top posting either if memory serves me well.  Me, I
will forgive if it is a cell phone thingy that can't be helped.
Otherwise, after a couple times, I'm not scrolling all over the place to
try to figure out what order the posts are in and all that.  I may not
blacklist but I will hit the "next" button.

OP.  You be well advised to reconsider.  Other wise, you will be on the
forums asking for help and in my opinion, this mailing list is the best
place for help.  Lifes full of choices tho.  Some good, some bad.

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Tanstaafl]

On 2012-05-14 11:26 AM, Michael Scherer <a6702894@unet.univie.ac.at> wrote:
> in my opinion it isn't. with top posting I see the newest message
> immediately, while otherwise I need page through sometimes
> huge amounts of mostly obsolete comments.

This is only the case if the person who replies doesn't trim their 
quoted text - which is often the case when brain-dead top-posters try 
bottom (aka inline) posting...

> where it's possible, I put my messages on top, and I've found
> more than once forum-rules that require or at least recommend
> top posting.

This isn't one of them...

> but I garantee that I will get flames, why I do this and urge me
> to change my habits.
> obviously this is an ingrained habit on gentoo-users, but from
> now on I'm going follow my habits and damn the flames.

Then you will not get much help here and your participation will be null 
and void.

You should always strive to adjust you habits to the rules of the forum 
you are participating in...

I loathe top-posting, but there are a few forums I participate in where 
that is the norm, so I just grin and bear it...

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Alecks Gates]

On Mon, May 14, 2012 at 1:25 PM, Tanstaafl <tanstaafl@libertytrek.org> wrote:
> This is only the case if the person who replies doesn't trim their quoted
> text - which is often the case when brain-dead top-posters try bottom (aka
> inline) posting...
>
>
> You should always strive to adjust you habits to the rules of the forum you
> are participating in...
>
> I loathe top-posting, but there are a few forums I participate in where that
> is the norm, so I just grin and bear it...
>

Personally, gmail has given me a bad habit.  It defaults to
top-posting in the web client, which I don't see how to change.  But
at least on the desktop I can easily move formatting around.  On the
Android client it seems rather archaic.  Does anyone know how to
change to bottom-posting on either client?

Thankfully, I don't go to any forums that enforce top-posting.  I
would probably get myself banned from all the complaining I would do.

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Michael Mol]

On Mon, May 14, 2012 at 3:11 PM, Alecks Gates <alecks.g@gmail.com> wrote:
> On Mon, May 14, 2012 at 1:25 PM, Tanstaafl <tanstaafl@libertytrek.org> wrote:
>> This is only the case if the person who replies doesn't trim their quoted
>> text - which is often the case when brain-dead top-posters try bottom (aka
>> inline) posting...
>>
>>
>> You should always strive to adjust you habits to the rules of the forum you
>> are participating in...
>>
>> I loathe top-posting, but there are a few forums I participate in where that
>> is the norm, so I just grin and bear it...
>>
>
> Personally, gmail has given me a bad habit.  It defaults to
> top-posting in the web client, which I don't see how to change.  But
> at least on the desktop I can easily move formatting around.  On the
> Android client it seems rather archaic.  Does anyone know how to
> change to bottom-posting on either client?

In Android, you can press "Reply in-line", but then you've got to
navigate potentially large email threads using a tiny screen to get to
the right place to reply. It's an ugly scenario.


-- 
:wq

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Alan McKinnon]

On Mon, 14 May 2012 14:11:25 -0500
Alecks Gates <alecks.g@gmail.com> wrote:

> On Mon, May 14, 2012 at 1:25 PM, Tanstaafl
> <tanstaafl@libertytrek.org> wrote:
> > This is only the case if the person who replies doesn't trim their
> > quoted text - which is often the case when brain-dead top-posters
> > try bottom (aka inline) posting...
> >
> >
> > You should always strive to adjust you habits to the rules of the
> > forum you are participating in...
> >
> > I loathe top-posting, but there are a few forums I participate in
> > where that is the norm, so I just grin and bear it...
> >
> 
> Personally, gmail has given me a bad habit.  It defaults to
> top-posting in the web client, which I don't see how to change.  But
> at least on the desktop I can easily move formatting around.  On the
> Android client it seems rather archaic.  Does anyone know how to
> change to bottom-posting on either client?

So around here we say don't top post rather bottom bottom, but what we
actually mean is inline post with your contribution below the portion
you are replying to and extraneous bits of the quoted text removed.
Also liberal use of [snip] tags is encouraged.

We generally tolerate gmail webapp users (trying to inline post on that
is hard to do but possible) and reluctantly accept the smartphone users
often have no choice as it's impossible to do anything other than top
post on many devices (especially BlackBerrys). Such users should leave
the nice "Sent from my BlackBerry" comment at the bottom, it helps
indicate you can't avoid the top-post.

All of these "rules" are like any other form of good manners - designed
to smooth communication and make it a pleasant thing to do. Just like
in real life, it's equally good manners to indicate up-front if you
can't do the norm. Example: some places it's expected that men stand up
when a lady enters the room. But not if the man has a broken leg, in
which case he should make sure the plaster cast and crutches can be
seen. 

See how it works? :-)


-- 
Alan McKinnnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Alan McKinnon]

On Mon, 14 May 2012 12:13:18 -0500
Dale <rdalek1967@gmail.com> wrote:

> For example:  Alan, Mike, Pandu, Mark, Neil and me are the top posters
> on this list.

Yo Dale,

You might want to re-calibrate your stats engine :-)

I've been quiet for a while (getting old...)[1] and fifty bucks says
Michael, Canek, Pandu and a couple more have all posted more than me
this year

[1] Well, that's my story and I'm sticking with it



-- 
Alan McKinnnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Michael Mol]

On Mon, May 14, 2012 at 4:51 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:

[snip]

> We generally tolerate gmail webapp users (trying to inline post on that
> is hard to do but possible) and reluctantly accept the smartphone users
> often have no choice as it's impossible to do anything other than top
> post on many devices (especially BlackBerrys). Such users should leave
> the nice "Sent from my BlackBerry" comment at the bottom, it helps
> indicate you can't avoid the top-post.

You may have noticed I usually have ":wq" at the ends of my emails.
That's when I'm posting from, e.g. GMail's web app. When you see "ZZ",
that's my phone or tablet.

-- 
:wq

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Alan McKinnon]

On Mon, 14 May 2012 17:01:59 -0400
Michael Mol <mikemol@gmail.com> wrote:

> On Mon, May 14, 2012 at 4:51 PM, Alan McKinnon
> <alan.mckinnon@gmail.com> wrote:
> 
> [snip]
> 
> > We generally tolerate gmail webapp users (trying to inline post on
> > that is hard to do but possible) and reluctantly accept the
> > smartphone users often have no choice as it's impossible to do
> > anything other than top post on many devices (especially
> > BlackBerrys). Such users should leave the nice "Sent from my
> > BlackBerry" comment at the bottom, it helps indicate you can't
> > avoid the top-post.
> 
> You may have noticed I usually have ":wq" at the ends of my emails.
> That's when I'm posting from, e.g. GMail's web app. When you see "ZZ",
> that's my phone or tablet.
> 

True's bob, whaddaya know. It's there right enough :-)

I still think Neil has the best sigs in the entire universe.
It's spooky the way his fortunes work.

-- 
Alan McKinnnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Neil Bothwick]

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

On Mon, 14 May 2012 23:24:57 +0200, Alan McKinnon wrote:

> I still think Neil has the best sigs in the entire universe.
> It's spooky the way his fortunes work.

They're totally random and chosen by software, I have no influence over
them.


-- 
Neil Bothwick

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Neil Bothwick]

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

On Mon, 14 May 2012 17:26:44 +0200, Michael Scherer wrote:

> obviously this is an ingrained habit on gentoo-users, but from

Not a habit, a preference grown from years of experience and the
practicalities of lists like this.

> now on I'm going follow my habits and damn the flames.

Do you act like that in real life? If you see a no smoking sign, do you
light up anyway because that's what you want to do and damn everyone else?

Help lists like this become significantly less useful once you are
killfiled for being an arrogant and ignorant ****.


-- 
Neil Bothwick

Computer apathy error: don't bother striking any key.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Alan McKinnon]

On Mon, 14 May 2012 22:53:40 +0100
Neil Bothwick <neil@digimed.co.uk> wrote:

> On Mon, 14 May 2012 23:24:57 +0200, Alan McKinnon wrote:
> 
> > I still think Neil has the best sigs in the entire universe.
> > It's spooky the way his fortunes work.
> 
> They're totally random and chosen by software, I have no influence
> over them.
> 
> 

Piffle :-)

Spooky action at a distance, that's what it is!

-- 
Alan McKinnnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Michael Mol]

On Mon, May 14, 2012 at 5:53 PM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Mon, 14 May 2012 23:24:57 +0200, Alan McKinnon wrote:
>
>> I still think Neil has the best sigs in the entire universe.
>> It's spooky the way his fortunes work.
>
> They're totally random and chosen by software, I have no influence over
> them.
>
>
> --
> Neil Bothwick
>
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing on usenet and in e-mail?

Spooky indeed.

-- 
:wq

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Michael Mol]

On Mon, May 14, 2012 at 7:23 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On Mon, 14 May 2012 22:53:40 +0100
> Neil Bothwick <neil@digimed.co.uk> wrote:
>
>> On Mon, 14 May 2012 23:24:57 +0200, Alan McKinnon wrote:
>>
>> > I still think Neil has the best sigs in the entire universe.
>> > It's spooky the way his fortunes work.
>>
>> They're totally random and chosen by software, I have no influence
>> over them.
>
> Piffle :-)
>
> Spooky action at a distance, that's what it is!

I do believe you're overestimating the gravity of the situation.

-- 
:wq

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Pandu Poluan]

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

On May 15, 2012 2:16 AM, "Alecks Gates" <alecks.g@gmail.com> wrote:
>
> Personally, gmail has given me a bad habit.  It defaults to
> top-posting in the web client, which I don't see how to change.  But
> at least on the desktop I can easily move formatting around.  On the
> Android client it seems rather archaic.  Does anyone know how to
> change to bottom-posting on either client?
>
> Thankfully, I don't go to any forums that enforce top-posting.  I
> would probably get myself banned from all the complaining I would do.
>

Android user here!

With the Android Gmail client, tap on "Respond inline", swipe up
repeatedly, and tap on the blank line underneath the message.

I found Swype (the virtual keyboard) to be most helpful when trimming
fluff; it has honest-to-goodness cursor keys (including PgUp and PgDn), and
a *very* helpful "Select Text" button to start selection.

Rgds,

[-- Attachment #2: Type: text/html, Size: 1110 bytes --]

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Pandu Poluan]

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

On May 15, 2012 2:27 AM, "Michael Mol" <mikemol@gmail.com> wrote:
>
> On Mon, May 14, 2012 at 3:11 PM, Alecks Gates <alecks.g@gmail.com> wrote:
> >
> > Personally, gmail has given me a bad habit.  It defaults to
> > top-posting in the web client, which I don't see how to change.  But
> > at least on the desktop I can easily move formatting around.  On the
> > Android client it seems rather archaic.  Does anyone know how to
> > change to bottom-posting on either client?
>
> In Android, you can press "Reply in-line", but then you've got to
> navigate potentially large email threads using a tiny screen to get to
> the right place to reply. It's an ugly scenario.
>

Meh, just saw your post and realized you've beaten me :-\

Again, please allow me to plug the goodness of Swype... like I posted
before, it has *complete* cursor keys. Plus one very powerful key called
"Cursor Jump" that allows one to very quickly go to the topmost (or bottom
most) line.

Rgds,

[-- Attachment #2: Type: text/html, Size: 1273 bytes --]

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Alecks Gates]

On Mon, May 14, 2012 at 7:03 PM, Pandu Poluan <pandu@poluan.info> wrote:
>
> On May 15, 2012 2:27 AM, "Michael Mol" <mikemol@gmail.com> wrote:
>>
>> On Mon, May 14, 2012 at 3:11 PM, Alecks Gates <alecks.g@gmail.com> wrote:
>> >
>> > Personally, gmail has given me a bad habit.  It defaults to
>> > top-posting in the web client, which I don't see how to change.  But
>> > at least on the desktop I can easily move formatting around.  On the
>> > Android client it seems rather archaic.  Does anyone know how to
>> > change to bottom-posting on either client?
>>
>> In Android, you can press "Reply in-line", but then you've got to
>> navigate potentially large email threads using a tiny screen to get to
>> the right place to reply. It's an ugly scenario.
>>
>
> Meh, just saw your post and realized you've beaten me :-\
>
> Again, please allow me to plug the goodness of Swype... like I posted
> before, it has *complete* cursor keys. Plus one very powerful key called
> "Cursor Jump" that allows one to very quickly go to the topmost (or bottom
> most) line.
>
> Rgds,

I've been quite set on my hardware keyboard for a while now (HTC G2).
But perhaps I'll try out Swype eventually....

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Pandu Poluan]

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

On May 15, 2012 7:11 AM, "Alecks Gates" <alecks.g@gmail.com> wrote:
>
> On Mon, May 14, 2012 at 7:03 PM, Pandu Poluan <pandu@poluan.info> wrote:
> >
> > On May 15, 2012 2:27 AM, "Michael Mol" <mikemol@gmail.com> wrote:
> >>
> >> On Mon, May 14, 2012 at 3:11 PM, Alecks Gates <alecks.g@gmail.com>
wrote:
> >> >
> >> > Personally, gmail has given me a bad habit.  It defaults to
> >> > top-posting in the web client, which I don't see how to change.  But
> >> > at least on the desktop I can easily move formatting around.  On the
> >> > Android client it seems rather archaic.  Does anyone know how to
> >> > change to bottom-posting on either client?
> >>
> >> In Android, you can press "Reply in-line", but then you've got to
> >> navigate potentially large email threads using a tiny screen to get to
> >> the right place to reply. It's an ugly scenario.
> >>
> >
> > Meh, just saw your post and realized you've beaten me :-\
> >
> > Again, please allow me to plug the goodness of Swype... like I posted
> > before, it has *complete* cursor keys. Plus one very powerful key called
> > "Cursor Jump" that allows one to very quickly go to the topmost (or
bottom
> > most) line.
> >
> > Rgds,
>
> I've been quite set on my hardware keyboard for a while now (HTC G2).
> But perhaps I'll try out Swype eventually....
>

You can still use the hardware keyboard, after using Swype to mangle the
replied-to email :-)

Rgds,

[-- Attachment #2: Type: text/html, Size: 2072 bytes --]

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Dale]

Alan McKinnon wrote:
> On Mon, 14 May 2012 12:13:18 -0500
> Dale <rdalek1967@gmail.com> wrote:
> 
>> For example:  Alan, Mike, Pandu, Mark, Neil and me are the top posters
>> on this list.
> 
> Yo Dale,
> 
> You might want to re-calibrate your stats engine :-)
> 
> I've been quiet for a while (getting old...)[1] and fifty bucks says
> Michael, Canek, Pandu and a couple more have all posted more than me
> this year
> 
> [1] Well, that's my story and I'm sticking with it
> 
> 
> 


Maybe like me, you blabber more than you think:

http://archives.gentoo.org/stats/gentoo-user-per-year.xml

I didn't put them in any certain order but you have fallen a bit tho.
Someone put alum in your water or something?

ROFL

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Mark Knecht]

On Mon, May 14, 2012 at 5:46 PM, Dale <rdalek1967@gmail.com> wrote:
> Alan McKinnon wrote:
>> On Mon, 14 May 2012 12:13:18 -0500
>> Dale <rdalek1967@gmail.com> wrote:
>>
>>> For example:  Alan, Mike, Pandu, Mark, Neil and me are the top posters
>>> on this list.
>>
>> Yo Dale,
>>
>> You might want to re-calibrate your stats engine :-)
>>
>> I've been quiet for a while (getting old...)[1] and fifty bucks says
>> Michael, Canek, Pandu and a couple more have all posted more than me
>> this year
>>
>> [1] Well, that's my story and I'm sticking with it
>>
>>
>>
>
>
> Maybe like me, you blabber more than you think:
>
> http://archives.gentoo.org/stats/gentoo-user-per-year.xml
>
> I didn't put them in any certain order but you have fallen a bit tho.
> Someone put alum in your water or something?
>
> ROFL
>
> Dale
>

Jeez.... Am I _STILL_ showing up on this list of high posting people?
I've honestly worked to get below number 10 and I cannot get there
apparently... (Too many posts like this I suppose!) ;-)

- Mark

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Dale]

Mark Knecht wrote:
> On Mon, May 14, 2012 at 5:46 PM, Dale <rdalek1967@gmail.com> wrote:
>> Alan McKinnon wrote:
>>> On Mon, 14 May 2012 12:13:18 -0500
>>> Dale <rdalek1967@gmail.com> wrote:
>>>
>>>> For example:  Alan, Mike, Pandu, Mark, Neil and me are the top posters
>>>> on this list.
>>>
>>> Yo Dale,
>>>
>>> You might want to re-calibrate your stats engine :-)
>>>
>>> I've been quiet for a while (getting old...)[1] and fifty bucks says
>>> Michael, Canek, Pandu and a couple more have all posted more than me
>>> this year
>>>
>>> [1] Well, that's my story and I'm sticking with it
>>>
>>>
>>>
>>
>>
>> Maybe like me, you blabber more than you think:
>>
>> http://archives.gentoo.org/stats/gentoo-user-per-year.xml
>>
>> I didn't put them in any certain order but you have fallen a bit tho.
>> Someone put alum in your water or something?
>>
>> ROFL
>>
>> Dale
>>
> 
> Jeez.... Am I _STILL_ showing up on this list of high posting people?
> I've honestly worked to get below number 10 and I cannot get there
> apparently... (Too many posts like this I suppose!) ;-)
> 
> - Mark
> 
> 


I'm wondering on this myself.  Should I take more meds or are the meds
causing it?   < scratches head >

o_O

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[john]

On Mon, 14 May 2012 19:46:39 -0500
Dale <rdalek1967@gmail.com> wrote:

> Alan McKinnon wrote:
> > On Mon, 14 May 2012 12:13:18 -0500
> > Dale <rdalek1967@gmail.com> wrote:
> > 
> >> For example:  Alan, Mike, Pandu, Mark, Neil and me are the top
> >> posters on this list.
> > 
> > Yo Dale,
> > 
> > You might want to re-calibrate your stats engine :-)
> > 
> > I've been quiet for a while (getting old...)[1] and fifty bucks says
> > Michael, Canek, Pandu and a couple more have all posted more than me
> > this year
> > 
> > [1] Well, that's my story and I'm sticking with it
> > 
> > 
> > 
> 
> 
> Maybe like me, you blabber more than you think:
> 
> http://archives.gentoo.org/stats/gentoo-user-per-year.xml
> 
> I didn't put them in any certain order but you have fallen a bit tho.
> Someone put alum in your water or something?
> 
> ROFL
> 
> Dale
> 
> :-)  :-)
> 

Would like to thank all guys and girls for posting. Even though I post
very little myself your posts are always excellent and there is plenty
to learn from just reading them.

There are things I can do now which I never thought possible. Thanks

-- 
John D Maunder

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Alan McKinnon]

On Tue, 15 May 2012 10:01:00 -0700
Mark Knecht <markknecht@gmail.com> wrote:

> > Maybe like me, you blabber more than you think:
> >
> > http://archives.gentoo.org/stats/gentoo-user-per-year.xml
> >
> > I didn't put them in any certain order but you have fallen a bit
> > tho. Someone put alum in your water or something?
> >
> > ROFL
> >
> > Dale
> >  
> 
> Jeez.... Am I _STILL_ showing up on this list of high posting people?
> I've honestly worked to get below number 10 and I cannot get there
> apparently... (Too many posts like this I suppose!) ;-)

This gentoo stuff is addictive :-)

Must be the personalities around here. I reckon that anyone who sticks
around here and becomes a regular (regardless of their skill level) has
something special going on inside.

Gentoo-ers all have that DIY attitude, as if they would rather not wait
around for someone else to do all their lifting for them.


-- 
Alan McKinnnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Peter Humphrey]

On Tuesday 15 May 2012 18:25:57 john wrote:

> Would like to thank all guys and girls for posting. Even though I
> post very little myself your posts are always excellent and there is
> plenty to learn from just reading them.
> 
> There are things I can do now which I never thought possible. Thanks

Is this one case in which a me-too message is acceptable? Anyway, I 
second John's gratitude to you all.

-- 
Rgds
Peter

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Pandu Poluan]

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

On May 15, 2012 7:50 AM, "Dale" <rdalek1967@gmail.com> wrote:
>
> Maybe like me, you blabber more than you think:
>
> http://archives.gentoo.org/stats/gentoo-user-per-year.xml
>
> I didn't put them in any certain order but you have fallen a bit tho.
> Someone put alum in your water or something?
>

I blabbed that much??

Gee... I purposefully stay away from piping up in threads related to CUPS,
KDE, Gnome, and other desktop-only stuff, and still end up in the top 5??
o_O

Rgds,

[-- Attachment #2: Type: text/html, Size: 708 bytes --]

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Michael Scherer]

On Wed, 16 May 2012 07:41:32 +0700
Pandu Poluan <pandu@poluan.info> wrote:

> On May 15, 2012 7:50 AM, "Dale" <rdalek1967@gmail.com> wrote:
> >
> > Maybe like me, you blabber more than you think:
> >
> > http://archives.gentoo.org/stats/gentoo-user-per-year.xml
> >
> > I didn't put them in any certain order but you have fallen a bit
> > tho. Someone put alum in your water or something?
> >
> 
> I blabbed that much??
> 
> Gee... I purposefully stay away from piping up in threads related to
> CUPS, KDE, Gnome, and other desktop-only stuff, and still end up in
> the top 5?? o_O
> 
> Rgds,

OK, OK. May I remind you what started this thread?
If bottom-most is really that important to you, I will
of course comply, though with outlook express which I'm
forced to use most of the time this is a bit tedious.
I had no idea what a flood of angry comments my post
on preferring top-most would start off.

My original problem (see title) is as yet unsolved. Any one
out there with an idea what might be causing this?
I'm grateful to those 3 or 4 who tried to help, but
by now I'm rather desperate and in the whole of internet
pages there is nothing even coming near.

bugzilla told me this wasn't a bug and go to the forums.
So you are really my last resort.

regards, michael

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Dale]

Michael Scherer wrote:
> On Wed, 16 May 2012 07:41:32 +0700
> Pandu Poluan <pandu@poluan.info> wrote:
> 
>> On May 15, 2012 7:50 AM, "Dale" <rdalek1967@gmail.com> wrote:
>>>
>>> Maybe like me, you blabber more than you think:
>>>
>>> http://archives.gentoo.org/stats/gentoo-user-per-year.xml
>>>
>>> I didn't put them in any certain order but you have fallen a bit
>>> tho. Someone put alum in your water or something?
>>>
>>
>> I blabbed that much??
>>
>> Gee... I purposefully stay away from piping up in threads related to
>> CUPS, KDE, Gnome, and other desktop-only stuff, and still end up in
>> the top 5?? o_O
>>
>> Rgds,
> 
> OK, OK. May I remind you what started this thread?
> If bottom-most is really that important to you, I will
> of course comply, though with outlook express which I'm
> forced to use most of the time this is a bit tedious.
> I had no idea what a flood of angry comments my post
> on preferring top-most would start off.
> 
> My original problem (see title) is as yet unsolved. Any one
> out there with an idea what might be causing this?
> I'm grateful to those 3 or 4 who tried to help, but
> by now I'm rather desperate and in the whole of internet
> pages there is nothing even coming near.
> 
> bugzilla told me this wasn't a bug and go to the forums.
> So you are really my last resort.
> 
> regards, michael
> 
> 


I would start with running make -j1 && make modules_install.  Someone
else posted it could be a race condition.

Are you editing the config by hand or are you using menuconfig or some
such tool?  If editing by hand maybe one thing is enabled but something
else it needs is not.

Still thinking.

Dale

:-)  :-)


-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Neil Bothwick]

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

On Thu, 17 May 2012 18:14:20 +0200, Michael Scherer wrote:

> I had no idea what a flood of angry comments my post
> on preferring top-most would start off.

It wasn't your preference, it was your attitude, with this comment

"from now on I'm going follow my habits and damn the flames."

Did you really have no idea that such an arrogant and inflammatory
statement would produce a reaction?


-- 
Neil Bothwick

She's fine, upstanding, and wonderful laying down.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Tanstaafl]

On 2012-05-17 12:14 PM, Michael Scherer <a6702894@unet.univie.ac.at> wrote:
> If bottom-most is really that important to you, I will of course
> comply, though with outlook express which I'm forced to use most of
> the time this is a bit tedious.

Interesting... so, you have someone standing next to you most of the 
time, pointing a gun at your head, forcing you to use one of the worst 
mail clients that ever existed?

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Pandu Poluan]

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

On May 17, 2012 11:19 PM, "Michael Scherer" <a6702894@unet.univie.ac.at>
wrote:
>
> On Wed, 16 May 2012 07:41:32 +0700
> Pandu Poluan <pandu@poluan.info> wrote:
>
> > On May 15, 2012 7:50 AM, "Dale" <rdalek1967@gmail.com> wrote:
> > >
> > > Maybe like me, you blabber more than you think:
> > >
> > > http://archives.gentoo.org/stats/gentoo-user-per-year.xml
> > >
> > > I didn't put them in any certain order but you have fallen a bit
> > > tho. Someone put alum in your water or something?
> > >
> >
> > I blabbed that much??
> >
> > Gee... I purposefully stay away from piping up in threads related to
> > CUPS, KDE, Gnome, and other desktop-only stuff, and still end up in
> > the top 5?? o_O
> >
> > Rgds,
>
> OK, OK. May I remind you what started this thread?
> If bottom-most is really that important to you, I will
> of course comply, though with outlook express which I'm
> forced to use most of the time this is a bit tedious.
> I had no idea what a flood of angry comments my post
> on preferring top-most would start off.
>
> My original problem (see title) is as yet unsolved. Any one
> out there with an idea what might be causing this?
> I'm grateful to those 3 or 4 who tried to help, but
> by now I'm rather desperate and in the whole of internet
> pages there is nothing even coming near.
>
> bugzilla told me this wasn't a bug and go to the forums.
> So you are really my last resort.
>
> regards, michael
>

Based on the information you've given, there can be only 2 possible cause:

1. The Makefile is somehow b0rken.

Evidence : 'ls' instead of 'ld'

2. Some file creation failed, causing the next step to fail.

Please post the output of 'df -i'. I once ran out of inodes during kernel
compile, even when the filesystem (ext4) was created with IIRC
100'000-something inodes (and still having several gigabytes of free
space).

Nowadays, I put /usr/src and portage's tempdir on a reiserfs to prevent
running out of inodes.

3. Something is wrong with your filesystem.

Especially if /usr/src is *already* on reiserfs. In this case, boot using
SystemRescueCD and do an offline fsck on the partition containing /usr/src

4. Swapfile / Swap partition problems.

Even with enough RAM, sometimes gcc just wants a swap. Post the output of
'swapon -s' please.

And there's also the possibility that somehow the swap gets b0rked. Try
turning off swap, rebuild the swap, and turning it back on.

Rgds,

[-- Attachment #2: Type: text/html, Size: 3176 bytes --]

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Michael Scherer]

On Thu, 17 May 2012 18:13:14 +0100
Neil Bothwick <neil@digimed.co.uk> wrote:

> On Thu, 17 May 2012 18:14:20 +0200, Michael Scherer wrote:
> 
> > I had no idea what a flood of angry comments my post
> > on preferring top-most would start off.
> 
> It wasn't your preference, it was your attitude, with this comment
> 
> "from now on I'm going follow my habits and damn the flames."
> 
> Did you really have no idea that such an arrogant and inflammatory
> statement would produce a reaction?
> 
> 

That line was indeed ill conceived, and is usually not my style.
Probably I was very tired and the frustration about not being
able to solve my problem expressed itself in the wrong context.

regards, michael
 

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Michael Scherer]

On Thu, 17 May 2012 12:05:07 -0500
Dale <rdalek1967@gmail.com> wrote:

> Michael Scherer wrote:
> > On Wed, 16 May 2012 07:41:32 +0700
> > Pandu Poluan <pandu@poluan.info> wrote:
> > 
> >> On May 15, 2012 7:50 AM, "Dale" <rdalek1967@gmail.com> wrote:
> >>>
> >>> Maybe like me, you blabber more than you think:
> >>>
> >>> http://archives.gentoo.org/stats/gentoo-user-per-year.xml
> >>>
> >>> I didn't put them in any certain order but you have fallen a bit
> >>> tho. Someone put alum in your water or something?
> >>>
> >>
> >> I blabbed that much??
> >>
> >> Gee... I purposefully stay away from piping up in threads related
> >> to CUPS, KDE, Gnome, and other desktop-only stuff, and still end
> >> up in the top 5?? o_O
> >>
> >> Rgds,
> > 
> > OK, OK. May I remind you what started this thread?
> > If bottom-most is really that important to you, I will
> > of course comply, though with outlook express which I'm
> > forced to use most of the time this is a bit tedious.
> > I had no idea what a flood of angry comments my post
> > on preferring top-most would start off.
> > 
> > My original problem (see title) is as yet unsolved. Any one
> > out there with an idea what might be causing this?
> > I'm grateful to those 3 or 4 who tried to help, but
> > by now I'm rather desperate and in the whole of internet
> > pages there is nothing even coming near.
> > 
> > bugzilla told me this wasn't a bug and go to the forums.
> > So you are really my last resort.
> > 
> > regards, michael
> > 
> > 
> 
> 
> I would start with running make -j1 && make modules_install.  Someone
> else posted it could be a race condition.
> 
> Are you editing the config by hand or are you using menuconfig or some
> such tool?  If editing by hand maybe one thing is enabled but
> something else it needs is not.
> 
> Still thinking.
> 
> Dale
> 
> :-)  :-)
> 
> 

Same result as ever. I use make nconfig, which is somewhat easier
to navigate around. Only once I tried to manually change .config,
because revdep-rebuild wanted to rebuild sys-fs/udisks, which
complained about CONFIG_USB_SUSPEND not being set, but a silent
make oldconfig removed the line automatically. I did the change
manually because CONFIG_USB_SUSPEND doesn't seem to exist in 3.2.12.

Anyway, thank you for thinking about it.

regards, michael

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[ny6p01]

On Thu, May 17, 2012 at 01:47:56PM -0400, Tanstaafl wrote:
> On 2012-05-17 12:14 PM, Michael Scherer <a6702894@unet.univie.ac.at> wrote:
> > If bottom-most is really that important to you, I will of course
> > comply, though with outlook express which I'm forced to use most of
> > the time this is a bit tedious.
> 
> Interesting... so, you have someone standing next to you most of the 
> time, pointing a gun at your head, forcing you to use one of the worst 
> mail clients that ever existed?
> 

How befitting that MS's flagship email client top posts by default...

Terry

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Alan McKinnon]

On Thu, 17 May 2012 12:14:08 -0700
ny6p01@gmail.com wrote:

> On Thu, May 17, 2012 at 01:47:56PM -0400, Tanstaafl wrote:
> > On 2012-05-17 12:14 PM, Michael Scherer
> > <a6702894@unet.univie.ac.at> wrote:
> > > If bottom-most is really that important to you, I will of course
> > > comply, though with outlook express which I'm forced to use most
> > > of the time this is a bit tedious.
> > 
> > Interesting... so, you have someone standing next to you most of
> > the time, pointing a gun at your head, forcing you to use one of
> > the worst mail clients that ever existed?
> > 
> 
> How befitting that MS's flagship email client top posts by default...


Outlook Express? Not even MS would attach the label "flagship" to
Outlook Express.

Mind you, Outlook is infernally difficult to make it inter-port or
bottom-post. Like gmail's web clientt, there's a lot of fiddling with
backspace, delete, undo and cursor keys involved.



-- 
Alan McKinnnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Michael Scherer]

On Thu, 17 May 2012 13:47:56 -0400
Tanstaafl <tanstaafl@libertytrek.org> wrote:

> On 2012-05-17 12:14 PM, Michael Scherer <a6702894@unet.univie.ac.at>
> wrote:
> > If bottom-most is really that important to you, I will of course
> > comply, though with outlook express which I'm forced to use most of
> > the time this is a bit tedious.
> 
> Interesting... so, you have someone standing next to you most of the 
> time, pointing a gun at your head, forcing you to use one of the
> worst mail clients that ever existed?
> 

thunderbird under windows has problems with imap accounts and outlook
is still much worse, not to speak of gmail and the like. With "forced"
I actually meant "forced to work with windows", where I use outlook
express which may be bad but I am used to it.

regards, michael

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Michael Scherer]

On Fri, 18 May 2012 01:06:02 +0700
Pandu Poluan <pandu@poluan.info> wrote:

> On May 17, 2012 11:19 PM, "Michael Scherer"
> <a6702894@unet.univie.ac.at> wrote:
> >
> > On Wed, 16 May 2012 07:41:32 +0700
> > Pandu Poluan <pandu@poluan.info> wrote:
> >
> > > On May 15, 2012 7:50 AM, "Dale" <rdalek1967@gmail.com> wrote:
> > > >
> > > > Maybe like me, you blabber more than you think:
> > > >
> > > > http://archives.gentoo.org/stats/gentoo-user-per-year.xml
> > > >
> > > > I didn't put them in any certain order but you have fallen a bit
> > > > tho. Someone put alum in your water or something?
> > > >
> > >
> > > I blabbed that much??
> > >
> > > Gee... I purposefully stay away from piping up in threads related
> > > to CUPS, KDE, Gnome, and other desktop-only stuff, and still end
> > > up in the top 5?? o_O
> > >
> > > Rgds,
> >
> > OK, OK. May I remind you what started this thread?
> > If bottom-most is really that important to you, I will
> > of course comply, though with outlook express which I'm
> > forced to use most of the time this is a bit tedious.
> > I had no idea what a flood of angry comments my post
> > on preferring top-most would start off.
> >
> > My original problem (see title) is as yet unsolved. Any one
> > out there with an idea what might be causing this?
> > I'm grateful to those 3 or 4 who tried to help, but
> > by now I'm rather desperate and in the whole of internet
> > pages there is nothing even coming near.
> >
> > bugzilla told me this wasn't a bug and go to the forums.
> > So you are really my last resort.
> >
> > regards, michael
> >
> 
> Based on the information you've given, there can be only 2 possible
> cause:
> 
> 1. The Makefile is somehow b0rken.
> 
> Evidence : 'ls' instead of 'ld'
> 
> 2. Some file creation failed, causing the next step to fail.
> 
> Please post the output of 'df -i'. I once ran out of inodes during
> kernel compile, even when the filesystem (ext4) was created with IIRC
> 100'000-something inodes (and still having several gigabytes of free
> space).
> 
> Nowadays, I put /usr/src and portage's tempdir on a reiserfs to
> prevent running out of inodes.
> 
> 3. Something is wrong with your filesystem.
> 
> Especially if /usr/src is *already* on reiserfs. In this case, boot
> using SystemRescueCD and do an offline fsck on the partition
> containing /usr/src
> 
> 4. Swapfile / Swap partition problems.
> 
> Even with enough RAM, sometimes gcc just wants a swap. Post the
> output of 'swapon -s' please.
> 
> And there's also the possibility that somehow the swap gets b0rked.
> Try turning off swap, rebuild the swap, and turning it back on.
> 
> Rgds,

1) make output:

  CHK     include/linux/version.h
  CHK     include/generated/utsrelease.h
  CALL    scripts/checksyscalls.sh
  CHK     include/generated/compile.h
  LD      init/mounts.o
ls -Al -m elf_x86_64 -r -o init/mounts.o init/do_mounts.o
init/do_mounts_initrd.o init/mounts.o: No such file or directory
make[1]: *** [init/mounts.o] Error 1
make: *** [init] Error 2

There is an LD, the ls line is part of the error message.

2) df -i

Filesystem      Inodes  IUsed   IFree IUse% Mounted on
rootfs         1313280   5652 1307628    1% /
/dev/root      1313280   5652 1307628    1% /
devtmpfs        385505    785  384720    1% /dev
rc-svcdir       385724     63  385661    1% /lib64/rc/init.d
/tmpfs          385724      1  385723    1% /dev/shm
/dev/sda12      130560     23  130537    1% /boot
/dev/sda15     3932656 363434 3569222   10% /usr
/dev/sda16     6119424 275818 5843606    5% /var

3) /usr/src is ext4, and all ebuilds run without problems.
If something is wrong with the file system, maybe an fsck would
show it, so I'll try that.

4) swapon -s

Filename				Type		Size
Used	Priority /dev/sda13
partition	10482376	0	-1

immediately after running make.

Remaking the swap area resulted in the same line as above.

But without doubt you are right that mounts.o is not built, for
whatever reason. The build command

init/.do_mounts.o.cmd:cmd_init/do_mounts.o := gcc
-Wp,-MD,init/.do_mounts.o.d -nostdinc
-isystem /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/include
-I/usr/src/linux-3.2.12-gentoo/arch/x86/include
-Iarch/x86/include/generated -Iinclude
-include /usr/src/linux-3.2.12-gentoo/include/linux/kconfig.h
-D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs
-fno-strict-aliasing -fno-common -Werror-implicit-function-declaration
-Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -march=k8
-mno-red-zone -mcmodel=kernel -funit-at-a-time
-maccumulate-outgoing-args -fstack-protector -DCONFIG_AS_CFI=1
-DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1
-DCONFIG_AS_FXSAVEQ=1 -pipe -Wno-sign-compare
-fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow
-Wframe-larger-than=2048 -fno-omit-frame-pointer
-fno-optimize-sibling-calls -fno-inline-functions-called-once
-Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow
-fconserve-stack -DCC_HAVE_ASM_GOTO -D"KBUILD_STR(s)=\#s"
-D"KBUILD_BASENAME=KBUILD_STR(do_mounts)"
-D"KBUILD_MODNAME=KBUILD_STR(mounts)" -c -o init/do_mounts.o
init/do_mounts.c

contains a directive to build mounts.o, see second last line, but
it for some reason this is ignored.
Maybe there is a flaw in that command, only I can't find it.

regards, michael

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Hinnerk van Bruinehsen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 17.05.2012 22:13, Michael Scherer wrote:

> 
> 1) make output:
> 
> CHK     include/linux/version.h CHK
> include/generated/utsrelease.h CALL    scripts/checksyscalls.sh CHK
> include/generated/compile.h LD      init/mounts.o ls -Al -m
> elf_x86_64 -r -o init/mounts.o init/do_mounts.o 
> init/do_mounts_initrd.o init/mounts.o: No such file or directory 
> make[1]: *** [init/mounts.o] Error 1 make: *** [init] Error 2
> 
> There is an LD, the ls line is part of the error message.
> 

> 
> contains a directive to build mounts.o, see second last line, but 
> it for some reason this is ignored. Maybe there is a flaw in that
> command, only I can't find it.
> 
> regards, michael
> 
> 

Have you tried a make clean on your sourcetree?

CHK     include/linux/version.h

IS for me one of the first lines I get at all. It seems strange to me
that you get a call to the linker (LD) before even a call to the
compiler (CC).

I'd suggest you try a make clean first and try to build again
afterwards (with -j1 or without a statement for jobs) to rule out race
conditions.

If that doesn't help, move your kernel sources to another directory
and reemerge the sources. Copy your .config (ideally one of a working
tree) and try again. If that doesn't help, try to get a working
default config (like from /proc/config.gz from a live distro).

WKR

Hinnerk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPtWSXAAoJEJwwOFaNFkYc8tAH/iV59mb5MsH0pJ28dXUqe0X6
tcbKB18vIQYmjG9gecGX4lVtgXCIhTqVeHEKbQVN4xRMo9u7D7FxygHtRY7sfYrk
dvR9fs4RfIoykVeCF/0uVSNZnoXhixarYtr8FGvIKCxvUJnY/ws4W+k5tP8Ju8lJ
wM5ldQ/eD8H4vFm4fIStQheTGERZlueNBVf77cLx8K/8p0XBvVM85V/epg+fC4I4
bfWG1JtXrh1MUmaE+Y26aNOXGkUZiHax49CBiOUQLZNjk6f5idGppWV03HTL4mCV
+dI6lNaUqU0AhnoG3yIOK8lY4kFu3QmNw4h1r+OCctASMJe8dUOTnF53TjJzYQk=
=TguL
-----END PGP SIGNATURE-----

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Michael Scherer]

On Thu, 17 May 2012 22:13:02 +0200
Michael Scherer <a6702894@unet.univie.ac.at> wrote:

> On Fri, 18 May 2012 01:06:02 +0700
> Pandu Poluan <pandu@poluan.info> wrote:
> 
> > On May 17, 2012 11:19 PM, "Michael Scherer"
> > <a6702894@unet.univie.ac.at> wrote:
> > >
> > > On Wed, 16 May 2012 07:41:32 +0700
> > > Pandu Poluan <pandu@poluan.info> wrote:
> > >
> > > > On May 15, 2012 7:50 AM, "Dale" <rdalek1967@gmail.com> wrote:
> > > > >
> > > > > Maybe like me, you blabber more than you think:
> > > > >
> > > > > http://archives.gentoo.org/stats/gentoo-user-per-year.xml
> > > > >
> > > > > I didn't put them in any certain order but you have fallen a
> > > > > bit tho. Someone put alum in your water or something?
> > > > >
> > > >
> > > > I blabbed that much??
> > > >
> > > > Gee... I purposefully stay away from piping up in threads
> > > > related to CUPS, KDE, Gnome, and other desktop-only stuff, and
> > > > still end up in the top 5?? o_O
> > > >
> > > > Rgds,
> > >
> > > OK, OK. May I remind you what started this thread?
> > > If bottom-most is really that important to you, I will
> > > of course comply, though with outlook express which I'm
> > > forced to use most of the time this is a bit tedious.
> > > I had no idea what a flood of angry comments my post
> > > on preferring top-most would start off.
> > >
> > > My original problem (see title) is as yet unsolved. Any one
> > > out there with an idea what might be causing this?
> > > I'm grateful to those 3 or 4 who tried to help, but
> > > by now I'm rather desperate and in the whole of internet
> > > pages there is nothing even coming near.
> > >
> > > bugzilla told me this wasn't a bug and go to the forums.
> > > So you are really my last resort.
> > >
> > > regards, michael
> > >
> > 
> > Based on the information you've given, there can be only 2 possible
> > cause:
> > 
> > 1. The Makefile is somehow b0rken.
> > 
> > Evidence : 'ls' instead of 'ld'
> > 
> > 2. Some file creation failed, causing the next step to fail.
> > 
> > Please post the output of 'df -i'. I once ran out of inodes during
> > kernel compile, even when the filesystem (ext4) was created with
> > IIRC 100'000-something inodes (and still having several gigabytes
> > of free space).
> > 
> > Nowadays, I put /usr/src and portage's tempdir on a reiserfs to
> > prevent running out of inodes.
> > 
> > 3. Something is wrong with your filesystem.
> > 
> > Especially if /usr/src is *already* on reiserfs. In this case, boot
> > using SystemRescueCD and do an offline fsck on the partition
> > containing /usr/src
> > 
> > 4. Swapfile / Swap partition problems.
> > 
> > Even with enough RAM, sometimes gcc just wants a swap. Post the
> > output of 'swapon -s' please.
> > 
> > And there's also the possibility that somehow the swap gets b0rked.
> > Try turning off swap, rebuild the swap, and turning it back on.
> > 
> > Rgds,
> 
> 1) make output:
> 
>   CHK     include/linux/version.h
>   CHK     include/generated/utsrelease.h
>   CALL    scripts/checksyscalls.sh
>   CHK     include/generated/compile.h
>   LD      init/mounts.o
> ls -Al -m elf_x86_64 -r -o init/mounts.o init/do_mounts.o
> init/do_mounts_initrd.o init/mounts.o: No such file or directory
> make[1]: *** [init/mounts.o] Error 1
> make: *** [init] Error 2
> 
> There is an LD, the ls line is part of the error message.
> 
> 2) df -i
> 
> Filesystem      Inodes  IUsed   IFree IUse% Mounted on
> rootfs         1313280   5652 1307628    1% /
> /dev/root      1313280   5652 1307628    1% /
> devtmpfs        385505    785  384720    1% /dev
> rc-svcdir       385724     63  385661    1% /lib64/rc/init.d
> /tmpfs          385724      1  385723    1% /dev/shm
> /dev/sda12      130560     23  130537    1% /boot
> /dev/sda15     3932656 363434 3569222   10% /usr
> /dev/sda16     6119424 275818 5843606    5% /var
> 
> 3) /usr/src is ext4, and all ebuilds run without problems.
> If something is wrong with the file system, maybe an fsck would
> show it, so I'll try that.
> 
> 4) swapon -s
> 
> Filename				Type		Size
> Used	Priority /dev/sda13
> partition	10482376	0	-1
> 
> immediately after running make.
> 
> Remaking the swap area resulted in the same line as above.
> 
> But without doubt you are right that mounts.o is not built, for
> whatever reason. The build command
> 
> init/.do_mounts.o.cmd:cmd_init/do_mounts.o := gcc
> -Wp,-MD,init/.do_mounts.o.d -nostdinc
> -isystem /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/include
> -I/usr/src/linux-3.2.12-gentoo/arch/x86/include
> -Iarch/x86/include/generated -Iinclude
> -include /usr/src/linux-3.2.12-gentoo/include/linux/kconfig.h
> -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs
> -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration
> -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64
> -march=k8 -mno-red-zone -mcmodel=kernel -funit-at-a-time
> -maccumulate-outgoing-args -fstack-protector -DCONFIG_AS_CFI=1
> -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1
> -DCONFIG_AS_FXSAVEQ=1 -pipe -Wno-sign-compare
> -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow
> -Wframe-larger-than=2048 -fno-omit-frame-pointer
> -fno-optimize-sibling-calls -fno-inline-functions-called-once
> -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow
> -fconserve-stack -DCC_HAVE_ASM_GOTO -D"KBUILD_STR(s)=\#s"
> -D"KBUILD_BASENAME=KBUILD_STR(do_mounts)"
> -D"KBUILD_MODNAME=KBUILD_STR(mounts)" -c -o init/do_mounts.o
> init/do_mounts.c
> 
> contains a directive to build mounts.o, see second last line, but
> it for some reason this is ignored.
> Maybe there is a flaw in that command, only I can't find it.
> 
> regards, michael
> 
> 

And this is the makefile for mounts.o:

#
# Makefile for the linux kernel.
#

obj-y                          := main.o version.o mounts.o
ifneq ($(CONFIG_BLK_DEV_INITRD),y)
obj-y                          += noinitramfs.o
else
obj-$(CONFIG_BLK_DEV_INITRD)   += initramfs.o
endif
obj-$(CONFIG_GENERIC_CALIBRATE_DELAY) += calibrate.o

mounts-y                        := do_mounts.o
mounts-$(CONFIG_BLK_DEV_RAM)    += do_mounts_rd.o
mounts-$(CONFIG_BLK_DEV_INITRD) += do_mounts_initrd.o
mounts-$(CONFIG_BLK_DEV_MD)     += do_mounts_md.o

# dependencies on generated files need to be listed explicitly
$(obj)/version.o: include/generated/compile.h

# compile.h changes depending on hostname, generation number, etc,
# so we regenerate it always.
# mkcompile_h will make sure to only update the
# actual file if its content has changed.

       chk_compile.h = :
 quiet_chk_compile.h = echo '  CHK     $@'
silent_chk_compile.h = :
include/generated/compile.h: FORCE
        @$($(quiet)chk_compile.h)
        $(Q)$(CONFIG_SHELL) $(srctree)/scripts/mkcompile_h $@ \
        "$(UTS_MACHINE)" "$(CONFIG_SMP)" "$(CONFIG_PREEMPT)" "$(CC)
       $(KBUILD_CFLAGS)"

Seems to be OK, but then I don't know what to make of the last part
starting with "# compile.h changes..."
Maybe something wrong here.

regards, michael

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Alex Schuster]

Michael Scherer writes:

> 1) make output:
> 
>   CHK     include/linux/version.h
>   CHK     include/generated/utsrelease.h
>   CALL    scripts/checksyscalls.sh
>   CHK     include/generated/compile.h
>   LD      init/mounts.o
> ls -Al -m elf_x86_64 -r -o init/mounts.o init/do_mounts.o
> init/do_mounts_initrd.o init/mounts.o: No such file or directory
> make[1]: *** [init/mounts.o] Error 1
> make: *** [init] Error 2
> 
> There is an LD, the ls line is part of the error message.

But the options look really more like ld options to me. How this could
possibly happen, I don't know. Some overriding of $(LD) perhaps? Does
"env | egrep -i 'ls|ld'" show something weird? Does it also fail as a
non-root user, after you copied the stuff over to somewhere where this
user can write? Just grasping at straws here.


> But without doubt you are right that mounts.o is not built, for
> whatever reason.

Because ld should build it from init/do_mounts.o, but ls is being called
instead?

> The build command
> 
> init/.do_mounts.o.cmd:cmd_init/do_mounts.o := gcc
> -Wp,-MD,init/.do_mounts.o.d -nostdinc
> -isystem /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/include
> -I/usr/src/linux-3.2.12-gentoo/arch/x86/include
> -Iarch/x86/include/generated -Iinclude
> -include /usr/src/linux-3.2.12-gentoo/include/linux/kconfig.h
> -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs
> -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration
> -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -march=k8
> -mno-red-zone -mcmodel=kernel -funit-at-a-time
> -maccumulate-outgoing-args -fstack-protector -DCONFIG_AS_CFI=1
> -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1
> -DCONFIG_AS_FXSAVEQ=1 -pipe -Wno-sign-compare
> -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow
> -Wframe-larger-than=2048 -fno-omit-frame-pointer
> -fno-optimize-sibling-calls -fno-inline-functions-called-once
> -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow
> -fconserve-stack -DCC_HAVE_ASM_GOTO -D"KBUILD_STR(s)=\#s"
> -D"KBUILD_BASENAME=KBUILD_STR(do_mounts)"
> -D"KBUILD_MODNAME=KBUILD_STR(mounts)" -c -o init/do_mounts.o
> init/do_mounts.c
> 
> contains a directive to build mounts.o, see second last line, but
> it for some reason this is ignored.
> Maybe there is a flaw in that command, only I can't find it.

Neither can I. Is this command executed at all? If you maybe replace the
'gcc' by 'gccXXX', does this give an error? Or put an 'echo' in
front of the gcc'.
You can try 'make -d', this will give you LOTS of debug output, but I
don't think you will see the actual commands then.

	Wonko

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Michael Mol]

On Thu, May 17, 2012 at 1:47 PM, Tanstaafl <tanstaafl@libertytrek.org> wrote:
> On 2012-05-17 12:14 PM, Michael Scherer <a6702894@unet.univie.ac.at> wrote:
>>
>> If bottom-most is really that important to you, I will of course
>> comply, though with outlook express which I'm forced to use most of
>> the time this is a bit tedious.
>
>
> Interesting... so, you have someone standing next to you most of the time,
> pointing a gun at your head, forcing you to use one of the worst mail
> clients that ever existed?

That's generally called a job.


-- 
:wq

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Peter Humphrey]

On Thursday 17 May 2012 20:25:01 Alan McKinnon wrote:

> Outlook Express? Not even MS would attach the label "flagship" to
> Outlook Express.

A recent experience has suggested a reason for OE to work the way it 
does. Using it the way it's designed to be used, the entire conversation 
so far is included in every message; this will save mucho casho for 
those organisations that don't want to store e-mails - they rely on 
being able to scan an incoming e-mail to find out what it's all about.

Not an efficient use of bandwidth. In fact it's an abuse of network 
operators to relieve user companies of their responsibilities.

-- 
Rgds
Peter

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Willie WY Wong]

On Tue, May 15, 2012 at 10:01:00AM -0700, Penguin Lover Mark Knecht squawked:
> > Maybe like me, you blabber more than you think:
> >
> > http://archives.gentoo.org/stats/gentoo-user-per-year.xml
> >
> Jeez.... Am I _STILL_ showing up on this list of high posting people?
> I've honestly worked to get below number 10 and I cannot get there
> apparently... (Too many posts like this I suppose!) ;-)
> 

Ah, another year, yet another new e-mail address. This certainly
helped keep me under the radar. I am quite surprised that I appeared
at all on that list, though I suppose my verbosity level has decreased
as I aged. 

Cheers,

W
-- 
Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire 
         et vice versa   ~~~  I. Newton

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Volker Armin Hemmann]

Am Montag, 14. Mai 2012, 19:46:39 schrieb Dale:
> Alan McKinnon wrote:
> > On Mon, 14 May 2012 12:13:18 -0500
> > 
> > Dale <rdalek1967@gmail.com> wrote:
> >> For example:  Alan, Mike, Pandu, Mark, Neil and me are the top posters
> >> on this list.
> > 
> > Yo Dale,
> > 
> > You might want to re-calibrate your stats engine :-)
> > 
> > I've been quiet for a while (getting old...)[1] and fifty bucks says
> > Michael, Canek, Pandu and a couple more have all posted more than me
> > this year
> > 
> > [1] Well, that's my story and I'm sticking with it
> 
> Maybe like me, you blabber more than you think:
> 
> http://archives.gentoo.org/stats/gentoo-user-per-year.xml
> 
> I didn't put them in any certain order but you have fallen a bit tho.
> Someone put alum in your water or something?
> 
> 

while I am somehow glad to be part of the Top 20 since 2005, I am even more 
happy, that I am not a regular Top5 poster. 



-- 
#163933

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Arttu V.]

I have no surefire solution, but so far everyone and their $PET seems
to have taken for granted that your toolchain is just fine and sane.
Perhaps "emerge -e @system" (without ccache, distcc or other
distractions) would jiggle those bits again?

-- 
Arttu V.

On 5/19/12, Volker Armin Hemmann <volkerarmin@googlemail.com> wrote:
> Am Montag, 14. Mai 2012, 19:46:39 schrieb Dale:
>> Alan McKinnon wrote:
>> > On Mon, 14 May 2012 12:13:18 -0500
>> >
>> > Dale <rdalek1967@gmail.com> wrote:
>> >> For example:  Alan, Mike, Pandu, Mark, Neil and me are the top posters
>> >> on this list.
>> >
>> > Yo Dale,
>> >
>> > You might want to re-calibrate your stats engine :-)
>> >
>> > I've been quiet for a while (getting old...)[1] and fifty bucks says
>> > Michael, Canek, Pandu and a couple more have all posted more than me
>> > this year
>> >
>> > [1] Well, that's my story and I'm sticking with it
>>
>> Maybe like me, you blabber more than you think:
>>
>> http://archives.gentoo.org/stats/gentoo-user-per-year.xml
>>
>> I didn't put them in any certain order but you have fallen a bit tho.
>> Someone put alum in your water or something?
>>
>>
>
> while I am somehow glad to be part of the Top 20 since 2005, I am even more
>
> happy, that I am not a regular Top5 poster.
>
>
>
> --
> #163933
>
>

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Joshua Murphy]

On Thu, May 17, 2012 at 4:50 PM, Hinnerk van Bruinehsen
<h.v.bruinehsen@fu-berlin.de> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 17.05.2012 22:13, Michael Scherer wrote:
>
>>
>> 1) make output:
>>
>> CHK     include/linux/version.h CHK
>> include/generated/utsrelease.h CALL    scripts/checksyscalls.sh CHK
>> include/generated/compile.h LD      init/mounts.o ls -Al -m
>> elf_x86_64 -r -o init/mounts.o init/do_mounts.o
>> init/do_mounts_initrd.o init/mounts.o: No such file or directory
>> make[1]: *** [init/mounts.o] Error 1 make: *** [init] Error 2
>>
>> There is an LD, the ls line is part of the error message.
>>
>
>>
>> contains a directive to build mounts.o, see second last line, but
>> it for some reason this is ignored. Maybe there is a flaw in that
>> command, only I can't find it.
>>
>> regards, michael
>>
>>
>
> Have you tried a make clean on your sourcetree?
>
> CHK     include/linux/version.h
>
> IS for me one of the first lines I get at all. It seems strange to me
> that you get a call to the linker (LD) before even a call to the
> compiler (CC).
>
> I'd suggest you try a make clean first and try to build again
> afterwards (with -j1 or without a statement for jobs) to rule out race
> conditions.
>
> If that doesn't help, move your kernel sources to another directory
> and reemerge the sources. Copy your .config (ideally one of a working
> tree) and try again. If that doesn't help, try to get a working
> default config (like from /proc/config.gz from a live distro).
>
> WKR
>
> Hinnerk
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJPtWSXAAoJEJwwOFaNFkYc8tAH/iV59mb5MsH0pJ28dXUqe0X6
> tcbKB18vIQYmjG9gecGX4lVtgXCIhTqVeHEKbQVN4xRMo9u7D7FxygHtRY7sfYrk
> dvR9fs4RfIoykVeCF/0uVSNZnoXhixarYtr8FGvIKCxvUJnY/ws4W+k5tP8Ju8lJ
> wM5ldQ/eD8H4vFm4fIStQheTGERZlueNBVf77cLx8K/8p0XBvVM85V/epg+fC4I4
> bfWG1JtXrh1MUmaE+Y26aNOXGkUZiHax49CBiOUQLZNjk6f5idGppWV03HTL4mCV
> +dI6lNaUqU0AhnoG3yIOK8lY4kFu3QmNw4h1r+OCctASMJe8dUOTnF53TjJzYQk=
> =TguL
> -----END PGP SIGNATURE-----
>

I'd be more active and vocal in trying to help sort this out, but it's
been a busy week since the 1k mile trip to get a car and working on
getting it into the shape I want it in... that aside, I *did* manage
to, without any changes, drop in the config provided at the start of
all this into a gentoo-sources 3.2.12 tree (after a quick mrproper)
and it built without issues. To me, that indicates that the toolchain,
particular copy of the sources, or hardware have an issue. That the
problem is as consistent as it is while the rest of the system isn't
failing in horrifying ways implies it's not the hardware. The
resulting modules and kernel from my building it can be grabbed from
http://poisonbl.freeshell.org/3.2.12_test.tar.bz2

-- 
Poison [BLX]
Joshua M. Murphy

Re: [gentoo-user] Are those "green" drives any good?

[Frank Steinmetzger]

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

On Sun, May 13, 2012 at 11:38:34AM +0200, David Haller wrote:

> >I bought my current internal laptop disk for Christmas 2008.  It's a Samsung
> >HM500JI (with 500 GB).  Early on I noticed that, according to smartctl, its
> >Load_Cycle_Count is increasing every 2 or 3 seconds.  I even asked Samsung
> >about this, but they either couldn't give any clue or didn't want to, b/c the
> >Serial Number is from Turkey, so not from the European market.
> >
> >Anyhoo... I just checked the values:
>>[…]
> >But the load cycle count is at almost 12.3 million(!).  That just can't be
> >right.  I stopped believing that number a good while ago.
> 
> As I said in another mail: laptop drives are built for frequent
> unloading. Your number does seem a bit high though, that's about 1000
> load cycles per hour...

My Pa bought the same HDD model for his laptop a few months back. Last weekend
I visited him and loaded a diag tool on his Windows. It showed 20 or 30.000
cycle counts. So I guess my model just has a bad firmware or summit like that.
Perhaps that's why it was so cheap back then (only ~62€ for a 500 GB drive by
the end of 2008).

Oh well, I'll just have to remember to do backups a bit more often.
-- 
Gruß | Greetings | Qapla'
Please do not share anything from, with or about me with any Facebook service.

A boss is a human just like everyone else, he just doesn’t know.

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Are those "green" drives any good?

[Andrew Hoffman]

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

You guys might find this study from google interesting:
http://static.googleusercontent.com/external_content/untrusted_dlcp/research.google.com/en/us/archive/disk_failures.pdf


On Mon, May 21, 2012 at 3:05 PM, Frank Steinmetzger <Warp_7@gmx.de> wrote:

> On Sun, May 13, 2012 at 11:38:34AM +0200, David Haller wrote:
>
> > >I bought my current internal laptop disk for Christmas 2008.  It's a
> Samsung
> > >HM500JI (with 500 GB).  Early on I noticed that, according to smartctl,
> its
> > >Load_Cycle_Count is increasing every 2 or 3 seconds.  I even asked
> Samsung
> > >about this, but they either couldn't give any clue or didn't want to,
> b/c the
> > >Serial Number is from Turkey, so not from the European market.
> > >
> > >Anyhoo... I just checked the values:
> >>[…]
> > >But the load cycle count is at almost 12.3 million(!).  That just can't
> be
> > >right.  I stopped believing that number a good while ago.
> >
> > As I said in another mail: laptop drives are built for frequent
> > unloading. Your number does seem a bit high though, that's about 1000
> > load cycles per hour...
>
> My Pa bought the same HDD model for his laptop a few months back. Last
> weekend
> I visited him and loaded a diag tool on his Windows. It showed 20 or 30.000
> cycle counts. So I guess my model just has a bad firmware or summit like
> that.
> Perhaps that's why it was so cheap back then (only ~62€ for a 500 GB drive
> by
> the end of 2008).
>
> Oh well, I'll just have to remember to do backups a bit more often.
> --
> Gruß | Greetings | Qapla'
> Please do not share anything from, with or about me with any Facebook
> service.
>
> A boss is a human just like everyone else, he just doesn’t know.
>

[-- Attachment #2: Type: text/html, Size: 2325 bytes --]

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Michael Scherer]

On Thu, 17 May 2012 22:59:41 +0200
Alex Schuster <wonko@wonkology.org> wrote:

> Michael Scherer writes:
> 
> > 1) make output:
> > 
> >   CHK     include/linux/version.h
> >   CHK     include/generated/utsrelease.h
> >   CALL    scripts/checksyscalls.sh
> >   CHK     include/generated/compile.h
> >   LD      init/mounts.o
> > ls -Al -m elf_x86_64 -r -o init/mounts.o init/do_mounts.o
> > init/do_mounts_initrd.o init/mounts.o: No such file or directory
> > make[1]: *** [init/mounts.o] Error 1
> > make: *** [init] Error 2
> > 
> > There is an LD, the ls line is part of the error message.
> 
> But the options look really more like ld options to me. How this could
> possibly happen, I don't know. Some overriding of $(LD) perhaps? Does
> "env | egrep -i 'ls|ld'" show something weird? Does it also fail as a
> non-root user, after you copied the stuff over to somewhere where this
> user can write? Just grasping at straws here.
> 
> 
> > But without doubt you are right that mounts.o is not built, for
> > whatever reason.
> 
> Because ld should build it from init/do_mounts.o, but ls is being
> called instead?
> 
> > The build command
> > 
> > init/.do_mounts.o.cmd:cmd_init/do_mounts.o := gcc
> > -Wp,-MD,init/.do_mounts.o.d -nostdinc
> > -isystem /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/include
> > -I/usr/src/linux-3.2.12-gentoo/arch/x86/include
> > -Iarch/x86/include/generated -Iinclude
> > -include /usr/src/linux-3.2.12-gentoo/include/linux/kconfig.h
> > -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs
> > -fno-strict-aliasing -fno-common
> > -Werror-implicit-function-declaration -Wno-format-security
> > -fno-delete-null-pointer-checks -O2 -m64 -march=k8 -mno-red-zone
> > -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args
> > -fstack-protector -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1
> > -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -pipe
> > -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx
> > -mno-sse2 -mno-3dnow -Wframe-larger-than=2048
> > -fno-omit-frame-pointer -fno-optimize-sibling-calls
> > -fno-inline-functions-called-once -Wdeclaration-after-statement
> > -Wno-pointer-sign -fno-strict-overflow -fconserve-stack
> > -DCC_HAVE_ASM_GOTO -D"KBUILD_STR(s)=\#s"
> > -D"KBUILD_BASENAME=KBUILD_STR(do_mounts)"
> > -D"KBUILD_MODNAME=KBUILD_STR(mounts)" -c -o init/do_mounts.o
> > init/do_mounts.c
> > 
> > contains a directive to build mounts.o, see second last line, but
> > it for some reason this is ignored.
> > Maybe there is a flaw in that command, only I can't find it.
> 
> Neither can I. Is this command executed at all? If you maybe replace
> the 'gcc' by 'gccXXX', does this give an error? Or put an 'echo' in
> front of the gcc'.
> You can try 'make -d', this will give you LOTS of debug output, but I
> don't think you will see the actual commands then.
> 
> 	Wonko
> 

Now at last there is some kind of "progress". Last thing I tried was
replacing my current .config with that of my previous kernel (3.2.1-r2)
and at least the make ran all the way up to the point where it should
link everything to build vmlinux, only now it tells me it couldn't
find vmlinux.o.

The last couple of lines from the make output:

  CC      arch/x86/lib/cache-smp.o
  CC      arch/x86/lib/msr.o
  AS      arch/x86/lib/msr-reg.o
  CC      arch/x86/lib/msr-reg-export.o
  AS      arch/x86/lib/iomap_copy_64.o
  LD      arch/x86/lib/built-in.o
ls -Al -m elf_x86_64 -r -o arch/x86/lib/built-in.o
arch/x86/lib/msr-smp.o arch/x86/lib/cache-smp.o arch/x86/lib/msr.o
arch/x86/lib/msr-reg.o arch/x86/lib/msr-reg-export.o
arch/x86/lib/iomap_copy_64.o
  AS      arch/x86/lib/clear_page_64.o
  AS      arch/x86/lib/cmpxchg16b_emu.o
  AS	  arch/x86/lib/copy_page_64.o
  AS      arch/x86/lib/copy_user_64.o
  AS      arch/x86/lib/copy_user_nocache_64.o
  AS	  arch/x86/lib/csum-copy_64.o
  CC      arch/x86/lib/csum-partial_64.o
  CC      arch/x86/lib/csum-wrappers_64.o
  CC      arch/x86/lib/delay.o
  AS      arch/x86/lib/getuser.o
  GEN     arch/x86/lib/inat-tables.c
  CC      arch/x86/lib/inat.o
  CC      arch/x86/lib/insn.o
  AS      arch/x86/lib/memcpy_64.o
  AS      arch/x86/lib/memmove_64.o
  AS      arch/x86/lib/memset_64.o
  AS      arch/x86/lib/putuser.o
  AS      arch/x86/lib/rwlock.o
  AS      arch/x86/lib/rwsem.o
  AS      arch/x86/lib/thunk_64.o
  CC      arch/x86/lib/usercopy.o
  CC      arch/x86/lib/usercopy_64.o
  AR      arch/x86/lib/lib.a
  LD      vmlinux.o
ls -Al -m elf_x86_64 -r -o vmlinux.o arch/x86/kernel/head_64.o
arch/x86/kernel/head64.o arch/x86/kernel/head.o
arch/x86/kernel/init_task.o init/built-in.o --start-group
usr/built-in.o arch/x86/built-in.o kernel/built-in.o mm/built-in.o
fs/built-in.o ipc/built-in.o security/built-in.o crypto/built-in.o
block/built-in.o lib/lib.a arch/x86/lib/lib.a lib/built-in.o
arch/x86/lib/built-in.o drivers/built-in.o sound/built-in.o
firmware/built-in.o arch/x86/pci/built-in.o arch/x86/power/built-in.o
arch/x86/video/built-in.o net/built-in.o --end-group
 MODPOST vmlinux.o
  vmlinux.o: No such file or directory make[1]: ***
  [vmlinux.o] Error 1 make: *** [vmlinux.o] Error 2


Essentially the same error as previously with mounts.o, and after
every LD comes an ls -Al ... line like above, which I never saw
before in my make outputs. Don't know where that comes from.

I'm now back where the troubles began, the vmlinux.o error was
the first I encountered after my last successful build.
Maybe a careful search of a diff of the .config files will
give me some idea.

By now you're probably somewhat tired of devoting your time
to this problem, so thank you for all your efforts to help me.
If I ever solve this, you'll hear from me (which doesn't mean
the thread is closed. If someone is still curious... ;-) )

Kind regards, Michael

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[Pandu Poluan]

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

On May 23, 2012 9:14 AM, "Michael Scherer" <a6702894@unet.univie.ac.at>
wrote:
>
> On Thu, 17 May 2012 22:59:41 +0200
> Alex Schuster <wonko@wonkology.org> wrote:
>
> > Michael Scherer writes:
> >
> > > 1) make output:
> > >
> > >   CHK     include/linux/version.h
> > >   CHK     include/generated/utsrelease.h
> > >   CALL    scripts/checksyscalls.sh
> > >   CHK     include/generated/compile.h
> > >   LD      init/mounts.o
> > > ls -Al -m elf_x86_64 -r -o init/mounts.o init/do_mounts.o
> > > init/do_mounts_initrd.o init/mounts.o: No such file or directory
> > > make[1]: *** [init/mounts.o] Error 1
> > > make: *** [init] Error 2
> > >
> > > There is an LD, the ls line is part of the error message.
> >
> > But the options look really more like ld options to me. How this could
> > possibly happen, I don't know. Some overriding of $(LD) perhaps? Does
> > "env | egrep -i 'ls|ld'" show something weird? Does it also fail as a
> > non-root user, after you copied the stuff over to somewhere where this
> > user can write? Just grasping at straws here.
> >
> >
> > > But without doubt you are right that mounts.o is not built, for
> > > whatever reason.
> >
> > Because ld should build it from init/do_mounts.o, but ls is being
> > called instead?
> >
> > > The build command
> > >
> > > init/.do_mounts.o.cmd:cmd_init/do_mounts.o := gcc
> > > -Wp,-MD,init/.do_mounts.o.d -nostdinc
> > > -isystem /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/include
> > > -I/usr/src/linux-3.2.12-gentoo/arch/x86/include
> > > -Iarch/x86/include/generated -Iinclude
> > > -include /usr/src/linux-3.2.12-gentoo/include/linux/kconfig.h
> > > -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs
> > > -fno-strict-aliasing -fno-common
> > > -Werror-implicit-function-declaration -Wno-format-security
> > > -fno-delete-null-pointer-checks -O2 -m64 -march=k8 -mno-red-zone
> > > -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args
> > > -fstack-protector -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1
> > > -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -pipe
> > > -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx
> > > -mno-sse2 -mno-3dnow -Wframe-larger-than=2048
> > > -fno-omit-frame-pointer -fno-optimize-sibling-calls
> > > -fno-inline-functions-called-once -Wdeclaration-after-statement
> > > -Wno-pointer-sign -fno-strict-overflow -fconserve-stack
> > > -DCC_HAVE_ASM_GOTO -D"KBUILD_STR(s)=\#s"
> > > -D"KBUILD_BASENAME=KBUILD_STR(do_mounts)"
> > > -D"KBUILD_MODNAME=KBUILD_STR(mounts)" -c -o init/do_mounts.o
> > > init/do_mounts.c
> > >
> > > contains a directive to build mounts.o, see second last line, but
> > > it for some reason this is ignored.
> > > Maybe there is a flaw in that command, only I can't find it.
> >
> > Neither can I. Is this command executed at all? If you maybe replace
> > the 'gcc' by 'gccXXX', does this give an error? Or put an 'echo' in
> > front of the gcc'.
> > You can try 'make -d', this will give you LOTS of debug output, but I
> > don't think you will see the actual commands then.
> >
> >       Wonko
> >
>
> Now at last there is some kind of "progress". Last thing I tried was
> replacing my current .config with that of my previous kernel (3.2.1-r2)
> and at least the make ran all the way up to the point where it should
> link everything to build vmlinux, only now it tells me it couldn't
> find vmlinux.o.
>
> The last couple of lines from the make output:
>
>  CC      arch/x86/lib/cache-smp.o
>  CC      arch/x86/lib/msr.o
>  AS      arch/x86/lib/msr-reg.o
>  CC      arch/x86/lib/msr-reg-export.o
>  AS      arch/x86/lib/iomap_copy_64.o
>  LD      arch/x86/lib/built-in.o
> ls -Al -m elf_x86_64 -r -o arch/x86/lib/built-in.o
> arch/x86/lib/msr-smp.o arch/x86/lib/cache-smp.o arch/x86/lib/msr.o
> arch/x86/lib/msr-reg.o arch/x86/lib/msr-reg-export.o
> arch/x86/lib/iomap_copy_64.o
>  AS      arch/x86/lib/clear_page_64.o
>  AS      arch/x86/lib/cmpxchg16b_emu.o
>  AS      arch/x86/lib/copy_page_64.o
>  AS      arch/x86/lib/copy_user_64.o
>  AS      arch/x86/lib/copy_user_nocache_64.o
>  AS      arch/x86/lib/csum-copy_64.o
>  CC      arch/x86/lib/csum-partial_64.o
>  CC      arch/x86/lib/csum-wrappers_64.o
>  CC      arch/x86/lib/delay.o
>  AS      arch/x86/lib/getuser.o
>  GEN     arch/x86/lib/inat-tables.c
>  CC      arch/x86/lib/inat.o
>  CC      arch/x86/lib/insn.o
>  AS      arch/x86/lib/memcpy_64.o
>  AS      arch/x86/lib/memmove_64.o
>  AS      arch/x86/lib/memset_64.o
>  AS      arch/x86/lib/putuser.o
>  AS      arch/x86/lib/rwlock.o
>  AS      arch/x86/lib/rwsem.o
>  AS      arch/x86/lib/thunk_64.o
>  CC      arch/x86/lib/usercopy.o
>  CC      arch/x86/lib/usercopy_64.o
>  AR      arch/x86/lib/lib.a
>  LD      vmlinux.o
> ls -Al -m elf_x86_64 -r -o vmlinux.o arch/x86/kernel/head_64.o
> arch/x86/kernel/head64.o arch/x86/kernel/head.o
> arch/x86/kernel/init_task.o init/built-in.o --start-group
> usr/built-in.o arch/x86/built-in.o kernel/built-in.o mm/built-in.o
> fs/built-in.o ipc/built-in.o security/built-in.o crypto/built-in.o
> block/built-in.o lib/lib.a arch/x86/lib/lib.a lib/built-in.o
> arch/x86/lib/built-in.o drivers/built-in.o sound/built-in.o
> firmware/built-in.o arch/x86/pci/built-in.o arch/x86/power/built-in.o
> arch/x86/video/built-in.o net/built-in.o --end-group
>  MODPOST vmlinux.o
>  vmlinux.o: No such file or directory make[1]: ***
>  [vmlinux.o] Error 1 make: *** [vmlinux.o] Error 2
>
>
> Essentially the same error as previously with mounts.o, and after
> every LD comes an ls -Al ... line like above, which I never saw
> before in my make outputs. Don't know where that comes from.
>
> I'm now back where the troubles began, the vmlinux.o error was
> the first I encountered after my last successful build.
> Maybe a careful search of a diff of the .config files will
> give me some idea.
>
> By now you're probably somewhat tired of devoting your time
> to this problem, so thank you for all your efforts to help me.
> If I ever solve this, you'll hear from me (which doesn't mean
> the thread is closed. If someone is still curious... ;-) )
>
> Kind regards, Michael
>

If the problem is due to .config, run make oldconfig first.

Rgds,

[-- Attachment #2: Type: text/html, Size: 8056 bytes --]

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[luis jure]

on 2012-05-14 at 08:52 ny6p01@gmail.com wrote:

>9. DO NOT TOP-POST and DO trim your replies!!! 

why don't you observe these yourself? you quoted the whole message you
replied to, which itself contained another full quote, which itself...

many people here complain against top-posting, but few observe the "DO
trim your replies" rule. see below, from your own post:

>Posting a "me too" comment at the bottom of a 100+ line message is no
>better because people, have to scroll all the way down through 100+ lines
>they've already read in order to see your one-liner. One word comes to
>mind for that: frustrating.

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[luis jure]

on 2012-05-14 at 22:54 Alan McKinnon wrote:

> (getting old...)

you don't say, really? what a coincidence, it's happening to me too.
anyone else getting older around here? is anyone actually getting
*younger*?

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails

[ny6p01]

On Sat, May 26, 2012 at 08:18:32AM -0300, luis jure wrote:
> on 2012-05-14 at 08:52 ny6p01@gmail.com wrote:
> 
> >9. DO NOT TOP-POST and DO trim your replies!!! 
> 
> why don't you observe these yourself? you quoted the whole message you
> replied to, which itself contained another full quote, which itself...
> 
> many people here complain against top-posting, but few observe the "DO
> trim your replies" rule. see below, from your own post:
> 
> >Posting a "me too" comment at the bottom of a 100+ line message is no
> >better because people, have to scroll all the way down through 100+ lines
> >they've already read in order to see your one-liner. One word comes to
> >mind for that: frustrating.
> 

Thank you for the timely reminder. It _was_ an error on my part.

Terry

Re: [gentoo-user] Re: make of gentoo-sources-3.2.12 fails [SOLVED]

[Michael Scherer]

Hi all,

I promised to tell you when I cracked this nasty little
problem of mine, though it's somewhat embarrassing
for me:

in short, don't put shell scripts called ld or cc in your
/usr/local/bin.
I had an ld script to give me lists of directories
in a certain format and then forgot about its
existence, until I had the happy idea to type 'ld'
on the command line to see what would happen.

at least now I know that I've really grown old.

again, thank you for all your efforts to help me.

kind regards, michael