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


Groups > comp.os.linux.advocacy > #287090

Re: Linux worked while Windows didn't

From Melzzzzz <mel@zzzzz.com>
Newsgroups comp.os.linux.advocacy
Subject Re: Linux worked while Windows didn't
Date 2015-04-01 02:18 +0200
Organization albasani.net
Message-ID <20150401021855.7bdb9e19@maxa-pc> (permalink)
References <551afd97$0$22315$c3e8da3$a9097924@news.astraweb.com> <mffcrj$480$6@dont-email.me>

Show all headers | View raw


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 ;)

Back to comp.os.linux.advocacy | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

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

csiph-web