Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.advocacy > #287028 > unrolled thread

Linux worked while Windows didn't

Back to article view | Back to comp.os.linux.advocacy

Contents

  Linux worked while Windows didn't vallor <vallor@cultnix.org> - 2015-03-31 13:03 -0700
    Re: Linux worked while Windows didn't Slimer <slvrslmr@lv.c> - 2015-03-31 16:15 -0400
    Re: Linux worked while Windows didn't owl <owl@rooftop.invalid> - 2015-03-31 20:30 +0000
    Re: Linux worked while Windows didn't Chris Ahlstrom <OFeem1987@teleworm.us> - 2015-03-31 20:08 -0400
      Re: Linux worked while Windows didn't Melzzzzz <mel@zzzzz.com> - 2015-04-01 02:18 +0200
        Re: Linux worked while Windows didn't Chris Ahlstrom <OFeem1987@teleworm.us> - 2015-04-01 06:09 -0400
    Re: Linux worked while Windows didn't ronb <ronb02NOSPAM@gmail.com> - 2015-04-01 00:11 +0000
      Re: Linux worked while Windows didn't Slimer <slvrslmr@lv.c> - 2015-03-31 21:37 -0400

#287028 — Linux worked while Windows didn't

So there I was, dual-booted into Windows 7 64-bit Home Premium playing
_Just Cause 2_, when the program exited with an exception.

"That's weird", I thought.  "Maybe it was the graphics driver I just
upgraded to."

So I back-graded the graphics driver, and played some more.  A few
minutes later -- Pop!  goes the exception.

I was streaming on twitch with a bunch of friends looking on, and we all
agreed that JC2 just doesn't do this sort of thing.  Clearly, there was
something odd about my machine.

After verifying the game cache in Steam, I started looking at hardware.
 And hey, wasn't that weird that the ASUS monitoring app wasn't
registering any chassis fans?

So I looked -- and NONE OF THE CHASSIS FANS WERE SPINNING.

Booted to Linux, fans started spinning.

I'd seen a message over the last few days, whenever booted to Windows,
that the Core1 temperature was 80C.  I'd only been playing
Elite:Dangerous, which didn't seem to mind the situation.  Additionally,
I'd been a bonehead and not investigated why my machine seemed so much
quieter while booted to Win7.

The fix?  Hard power cycle.  Now the fans spin in Windows.

Now, about the subject line above, "Linux worked while Windows didn't".
 These wintroll clowns are always talking about their hardware works
properly in Windows, but not Linux.  Thus, I feel justified blaming
Windows for what is clearly a chipset driver failure -- after all, it's
a Windows driver!

Toodles.

-- 
 -v

Griffin's Thought:
	When you starve with a tiger, the tiger starves last.

[toc] | [next] | [standalone]

#287032

On 2015-03-31 4:03 PM, vallor wrote:
> So there I was, dual-booted into Windows 7 64-bit Home Premium playing
> _Just Cause 2_, when the program exited with an exception.
>
> "That's weird", I thought.  "Maybe it was the graphics driver I just
> upgraded to."
>
> So I back-graded the graphics driver, and played some more.  A few
> minutes later -- Pop!  goes the exception.
>
> I was streaming on twitch with a bunch of friends looking on, and we all
> agreed that JC2 just doesn't do this sort of thing.  Clearly, there was
> something odd about my machine.
>
> After verifying the game cache in Steam, I started looking at hardware.
>   And hey, wasn't that weird that the ASUS monitoring app wasn't
> registering any chassis fans?
>
> So I looked -- and NONE OF THE CHASSIS FANS WERE SPINNING.
>
> Booted to Linux, fans started spinning.
>
> I'd seen a message over the last few days, whenever booted to Windows,
> that the Core1 temperature was 80C.  I'd only been playing
> Elite:Dangerous, which didn't seem to mind the situation.  Additionally,
> I'd been a bonehead and not investigated why my machine seemed so much
> quieter while booted to Win7.
>
> The fix?  Hard power cycle.  Now the fans spin in Windows.
>
> Now, about the subject line above, "Linux worked while Windows didn't".
>   These wintroll clowns are always talking about their hardware works
> properly in Windows, but not Linux.  Thus, I feel justified blaming
> Windows for what is clearly a chipset driver failure -- after all, it's
> a Windows driver!
>
> Toodles.

Just before you waste any more your time, you should know that Just 
Cause 2 is one of the worst games I've purchased in the past few years. 
It's shockingly bad, especially the parachute side missions.

-- 
Slimer
OpenMedia, GreenPeace Supporter & SPCA Paw Partner
Encrypt.

[toc] | [prev] | [next] | [standalone]

#287034

vallor <vallor@cultnix.org> wrote:
> So there I was, dual-booted into Windows 7 64-bit Home Premium playing
> _Just Cause 2_, when the program exited with an exception.

> "That's weird", I thought.  "Maybe it was the graphics driver I just
> upgraded to."

> So I back-graded the graphics driver, and played some more.  A few
> minutes later -- Pop!  goes the exception.

> I was streaming on twitch with a bunch of friends looking on, and we all
> agreed that JC2 just doesn't do this sort of thing.  Clearly, there was
> something odd about my machine.

> After verifying the game cache in Steam, I started looking at hardware.
>  And hey, wasn't that weird that the ASUS monitoring app wasn't
> registering any chassis fans?

> So I looked -- and NONE OF THE CHASSIS FANS WERE SPINNING.

> Booted to Linux, fans started spinning.

> I'd seen a message over the last few days, whenever booted to Windows,
> that the Core1 temperature was 80C.  I'd only been playing
> Elite:Dangerous, which didn't seem to mind the situation.  Additionally,
> I'd been a bonehead and not investigated why my machine seemed so much
> quieter while booted to Win7.

> The fix?  Hard power cycle.  Now the fans spin in Windows.

> Now, about the subject line above, "Linux worked while Windows didn't".
>  These wintroll clowns are always talking about their hardware works
> properly in Windows, but not Linux.  Thus, I feel justified blaming
> Windows for what is clearly a chipset driver failure -- after all, it's
> a Windows driver!

> Toodles.

So Linux blows and Windoze doesn't?

[toc] | [prev] | [next] | [standalone]

#287086

vallor wrote this copyrighted missive and expects royalties:

> So there I was, dual-booted into Windows 7 64-bit Home Premium playing
> _Just Cause 2_, when the program exited with an exception.
>
> "That's weird", I thought.  "Maybe it was the graphics driver I just
> upgraded to."
>
> So I back-graded the graphics driver, and played some more.  A few
> minutes later -- Pop!  goes the exception.
>
> I was streaming on twitch with a bunch of friends looking on, and we all
> agreed that JC2 just doesn't do this sort of thing.  Clearly, there was
> something odd about my machine.
>
> After verifying the game cache in Steam, I started looking at hardware.
>  And hey, wasn't that weird that the ASUS monitoring app wasn't
> registering any chassis fans?
>
> So I looked -- and NONE OF THE CHASSIS FANS WERE SPINNING.
>
> Booted to Linux, fans started spinning.
>
> I'd seen a message over the last few days, whenever booted to Windows,
> that the Core1 temperature was 80C.  I'd only been playing
> Elite:Dangerous, which didn't seem to mind the situation.  Additionally,
> I'd been a bonehead and not investigated why my machine seemed so much
> quieter while booted to Win7.
>
> The fix?  Hard power cycle.  Now the fans spin in Windows.
>
> Now, about the subject line above, "Linux worked while Windows didn't".
>  These wintroll clowns are always talking about their hardware works
> properly in Windows, but not Linux.  Thus, I feel justified blaming
> Windows for what is clearly a chipset driver failure -- after all, it's
> a Windows driver!
>
> Toodles.

I had an issue that was more "democratic" recently.  I hooked up my Canon
LiDE 210 to my relatively new ASUS laptop.  (1920x1080 matte screen,
i7, added an SSD drive, and it screams!)  The Preview function worked,
mostly.  But the scans would error out.  WTF?

I googled and saw that disabling the xHCI preboot mode would help.
And it worked.  Apparently an issue with USB 3.0, which is what this
laptop has, and the hub I use for connecting MIDI, USB audio, Bluetooth
dongles, wireless peripherals, also has.

Did Linux screw up?   Well, if it did, then so did Windows 8, where I found
a post that stated that the same kind of fix worked.

No matter, it was a 5-minute fix.

-- 
We have met the enemy, and he is us.
		-- Walt Kelly

[toc] | [prev] | [next] | [standalone]

#287090

On Tue, 31 Mar 2015 20:08:08 -0400
Chris Ahlstrom <OFeem1987@teleworm.us> wrote:

> vallor wrote this copyrighted missive and expects royalties:
> 
> > So there I was, dual-booted into Windows 7 64-bit Home Premium
> > playing _Just Cause 2_, when the program exited with an exception.
> >
> > "That's weird", I thought.  "Maybe it was the graphics driver I just
> > upgraded to."
> >
> > So I back-graded the graphics driver, and played some more.  A few
> > minutes later -- Pop!  goes the exception.
> >
> > I was streaming on twitch with a bunch of friends looking on, and
> > we all agreed that JC2 just doesn't do this sort of thing.
> > Clearly, there was something odd about my machine.
> >
> > After verifying the game cache in Steam, I started looking at
> > hardware. And hey, wasn't that weird that the ASUS monitoring app
> > wasn't registering any chassis fans?
> >
> > So I looked -- and NONE OF THE CHASSIS FANS WERE SPINNING.
> >
> > Booted to Linux, fans started spinning.
> >
> > I'd seen a message over the last few days, whenever booted to
> > Windows, that the Core1 temperature was 80C.  I'd only been playing
> > Elite:Dangerous, which didn't seem to mind the situation.
> > Additionally, I'd been a bonehead and not investigated why my
> > machine seemed so much quieter while booted to Win7.
> >
> > The fix?  Hard power cycle.  Now the fans spin in Windows.
> >
> > Now, about the subject line above, "Linux worked while Windows
> > didn't". These wintroll clowns are always talking about their
> > hardware works properly in Windows, but not Linux.  Thus, I feel
> > justified blaming Windows for what is clearly a chipset driver
> > failure -- after all, it's a Windows driver!
> >
> > Toodles.
> 
> I had an issue that was more "democratic" recently.  I hooked up my
> Canon LiDE 210 to my relatively new ASUS laptop.  (1920x1080 matte
> screen, i7, added an SSD drive, and it screams!)  The Preview
> function worked, mostly.  But the scans would error out.  WTF?
> 
> I googled and saw that disabling the xHCI preboot mode would help.
> And it worked.  Apparently an issue with USB 3.0, which is what this
> laptop has, and the hub I use for connecting MIDI, USB audio,
> Bluetooth dongles, wireless peripherals, also has.
> 
> Did Linux screw up?   Well, if it did, then so did Windows 8, where I
> found a post that stated that the same kind of fix worked.
> 
> No matter, it was a 5-minute fix.
> 

This is known problem with sane driver and USB3. Vuescan works but 
it is not free. I did same as you, as I scan page once in three
months ;)

[toc] | [prev] | [next] | [standalone]

#287113

Melzzzzz wrote this copyrighted missive and expects royalties:

> On Tue, 31 Mar 2015 20:08:08 -0400
> Chris Ahlstrom <OFeem1987@teleworm.us> wrote:
>
>> vallor wrote this copyrighted missive and expects royalties:
>> 
>> > So there I was, dual-booted into Windows 7 64-bit Home Premium
>> > playing _Just Cause 2_, when the program exited with an exception.
>> >
>> > "That's weird", I thought.  "Maybe it was the graphics driver I just
>> > upgraded to."
>> >
>> > So I back-graded the graphics driver, and played some more.  A few
>> > minutes later -- Pop!  goes the exception.
>> >
>> > I was streaming on twitch with a bunch of friends looking on, and
>> > we all agreed that JC2 just doesn't do this sort of thing.
>> > Clearly, there was something odd about my machine.
>> >
>> > After verifying the game cache in Steam, I started looking at
>> > hardware. And hey, wasn't that weird that the ASUS monitoring app
>> > wasn't registering any chassis fans?
>> >
>> > So I looked -- and NONE OF THE CHASSIS FANS WERE SPINNING.
>> >
>> > Booted to Linux, fans started spinning.
>> >
>> > I'd seen a message over the last few days, whenever booted to
>> > Windows, that the Core1 temperature was 80C.  I'd only been playing
>> > Elite:Dangerous, which didn't seem to mind the situation.
>> > Additionally, I'd been a bonehead and not investigated why my
>> > machine seemed so much quieter while booted to Win7.
>> >
>> > The fix?  Hard power cycle.  Now the fans spin in Windows.
>> >
>> > Now, about the subject line above, "Linux worked while Windows
>> > didn't". These wintroll clowns are always talking about their
>> > hardware works properly in Windows, but not Linux.  Thus, I feel
>> > justified blaming Windows for what is clearly a chipset driver
>> > failure -- after all, it's a Windows driver!
>> >
>> > Toodles.
>> 
>> I had an issue that was more "democratic" recently.  I hooked up my
>> Canon LiDE 210 to my relatively new ASUS laptop.  (1920x1080 matte
>> screen, i7, added an SSD drive, and it screams!)  The Preview
>> function worked, mostly.  But the scans would error out.  WTF?
>> 
>> I googled and saw that disabling the xHCI preboot mode would help.
>> And it worked.  Apparently an issue with USB 3.0, which is what this
>> laptop has, and the hub I use for connecting MIDI, USB audio,
>> Bluetooth dongles, wireless peripherals, also has.
>> 
>> Did Linux screw up?   Well, if it did, then so did Windows 8, where I
>> found a post that stated that the same kind of fix worked.
>> 
>> No matter, it was a 5-minute fix.
>
> This is known problem with sane driver and USB3. Vuescan works but 
> it is not free. I did same as you, as I scan page once in three
> months ;)

I don't believe that, Melzzz.  This exact same setup worked fine on
my previous Linux laptop.  But maybe the xHCI controller introduces
issues.

But it looks like disabling this UEFI entry puts the ports back into
USB 2.0.   (Some people say it disables the port entirely, which is
dead wrong.)

That is an issue.

-- 
The misnaming of fields of study is so common as to lead to what might be
general systems laws.  For example, Frank Harary once suggested the law that
any field that had the word "science" in its name was guaranteed thereby
not to be a science.  He would cite as examples Military Science, Library
Science, Political Science, Homemaking Science, Social Science, and Computer
Science.  Discuss the generality of this law, and possible reasons for its
predictive power.
		-- Gerald Weinberg, "An Introduction to General Systems
		   Thinking"

[toc] | [prev] | [next] | [standalone]

#287088

On Tue, 31 Mar 2015 13:03:34 -0700, vallor wrote:

> The fix?  Hard power cycle.  Now the fans spin in Windows.

Ah the old Windows reboot ... then re-install "fix." The real fix for the 
Windows virus is installing Linux over it.

-- 
To WinDrones and iCultists obsessed with Linux. Get a life.

[toc] | [prev] | [next] | [standalone]

#287102

On 2015-03-31 8:11 PM, ronb wrote:
> On Tue, 31 Mar 2015 13:03:34 -0700, vallor wrote:
>
>> The fix?  Hard power cycle.  Now the fans spin in Windows.
>
> Ah the old Windows reboot ... then re-install "fix." The real fix for the
> Windows virus is installing Linux over it.

Linsux "fixed" my desktop by providing it with excellent new features 
like screen tearing, an inability to wake from sleep or shutdown as well 
as inexplicable freeze-ups every so often. That sure was a lot better 
than a working Windows 8 install.

-- 
Slimer
OpenMedia, GreenPeace Supporter & SPCA Paw Partner
Encrypt.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.advocacy

csiph-web