[gentoo-user] headphone does not work in windows After logging to linux

[gentoo-user] headphone does not work in windows After logging to linux

[behrouz khosravi]

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

Hi. My problem is that when I log off from gentoo and login to windows, my
headphone does not work in windows.
Has anyone encountered the same problem?

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

Re: [gentoo-user] headphone does not work in windows After logging to linux

[Matti Nykyri]

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

> On Nov 21, 2014, at 14:08, behrouz khosravi <bz.khosravi@gmail.com> wrote:
> 
> Hi. My problem is that when I log off from gentoo and login to windows, my headphone does not work in windows. 
> Has anyone encountered the same problem?
> 
Do you reboot in the between or are you running somekind of virtual machine? Usb headphones or what? What sound driver? I've had problems with NIC between reboots. They were cleared by removing power cord for multiple minutes while rebooting. I got rid of the problem when i updated NIC's driver (bug in driver).

-- 
-Matti

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

Re: [gentoo-user] headphone does not work in windows After logging to linux

[the]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 21/11/14 16:07, Matti Nykyri wrote:
> Do you reboot in the between or are you running somekind of
> virtual machine? Usb headphones or what? What sound driver? I've
> had problems with NIC between reboots. They were cleared by
> removing power cord for multiple minutes while rebooting. I got rid
> of the problem when i updated NIC's driver (bug in driver).

Hmm, I have a similar problem with my SiS 190 ethernet adapter.
It works fine under gentoo, but after reboot from windows
it stops working. Pulling the plug and waiting helps.
Very peculiar imo.



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJUbzqXAAoJEK64IL1uI2haX6UIAIrCPnbhgQIkbnFhPfckEmt8
rPTg7upzjLnwpFOdQWbiLjrD01QCvcuCsxU6j2s/tT1uRnKGOQFKLhGcdLQIUUfn
jCzZVJdDLG89nO/iMEB3x5nBNaDH9KIorkMXOSfWVi4EYGhc/IHQJKrqDHtOEvAj
E5MOijKVLnH6vKXfI80YtaUcYSgAziDk3cOFANU68HqBaaNAV8vWghFl0e0FwAtH
pUubqD3XtqEMDFtKsBOiFxz02ZSQ8Lnb/MLDxvegWYxNWVqurv/O3BCTt+8DmJTD
a5v8ClnWWMFFW1y3s50m5ifqgxVkUzaNtG/zT7i24unP+8chQQSVUDGcT+neXiU=
=EQtE
-----END PGP SIGNATURE-----

Re: [gentoo-user] headphone does not work in windows After logging to linux

[behrouz khosravi]

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

> Do you reboot in the between or are you running somekind of virtual
machine? Usb headphones or what? What sound driver? I've had problems with
NIC between reboots. They were cleared by removing power cord for multiple
minutes while rebooting. I got rid of the problem when i updated NIC's
driver (bug in driver).
>
> --
> -Matti

No. It happen every time I boot into linux. Gentoo or Arch.
removing power helps but is annoying.
its not usb, but I dont know what is called! the ordinary type!
Its a realtek chip .
The bug that you mentioned is related to linux driver or windows driver?

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

Re: [gentoo-user] headphone does not work in windows After logging to linux

[Matti Nykyri]

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

> On Nov 21, 2014, at 16:15, behrouz khosravi <bz.khosravi@gmail.com> wrote:
> 
> 
> > Do you reboot in the between or are you running somekind of virtual machine? Usb headphones or what? What sound driver? I've had problems with NIC between reboots. They were cleared by removing power cord for multiple minutes while rebooting. I got rid of the problem when i updated NIC's driver (bug in driver).
> >
> > -- 
> > -Matti
> 
> No. It happen every time I boot into linux. Gentoo or Arch.
> removing power helps but is annoying.
> its not usb, but I dont know what is called! the ordinary type!
> Its a realtek chip .
> The bug that you mentioned is related to linux driver or windows driver?
> 

I have realtek R6168/6111/6169 NIC. It works in Linux with realtek's driver not with the one included in kernel. Windows fails to initialize the NIC properly when I reboot from linux to windows. When NIC is reset by recycling power windows will be able to initialize it. Downgrading windows (7 64bit) dirver to an ancient one fixed the problem. The up-to-date realtek driver didn't work correctly. 

lspci -v

You can check what driver kernel uses for you audio. Also the bug can be in alsa. The ways of alsa quite complicated... You are using alsa right? What error message does alsa give when you try to play audio?

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

Re: [gentoo-user] headphone does not work in windows After logging to linux

[behrouz khosravi]

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

On Nov 21, 2014 6:23 PM, "Matti Nykyri" <matti.nykyri@iki.fi> wrote:
>
> On Nov 21, 2014, at 16:15, behrouz khosravi <bz.khosravi@gmail.com> wrote:
>
>>
>> > Do you reboot in the between or are you running somekind of virtual
machine? Usb headphones or what? What sound driver? I've had problems with
NIC between reboots. They were cleared by removing power cord for multiple
minutes while rebooting. I got rid of the problem when i updated NIC's
driver (bug in driver).
>> >
>> > --
>> > -Matti
>>
>> No. It happen every time I boot into linux. Gentoo or Arch.
>> removing power helps but is annoying.
>> its not usb, but I dont know what is called! the ordinary type!
>> Its a realtek chip .
>> The bug that you mentioned is related to linux driver or windows driver?
>
>
> I have realtek R6168/6111/6169 NIC. It works in Linux with realtek's
driver not with the one included in kernel. Windows fails to initialize the
NIC properly when I reboot from linux to windows. When NIC is reset by
recycling power windows will be able to initialize it. Downgrading windows
(7 64bit) dirver to an ancient one fixed the problem. The up-to-date
realtek driver didn't work correctly.
>
> lspci -v
>
> You can check what driver kernel uses for you audio. Also the bug can be
in alsa. The ways of alsa quite complicated... You are using alsa right?
What error message does alsa give when you try to play audio?
Well I have no problem with it in linux. It always works in linux but I
think there is a problem with alsa or some other linux related part.
Because I have enabled the after post sound in bios. When I power in on the
headphone work. Then I login to linux and when I reboot to login to
windows, the bios post sound does not come from headphone.
It seems something is wrong in the linux part!

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

Re: [gentoo-user] headphone does not work in windows After logging to linux

[Ivan T. Ivanov]

On Fri, 2014-11-21 at 18:38 +0330, behrouz khosravi wrote:
> 
> Well I have no problem with it in linux. It always works in linux but I think there is a problem 
> with alsa or some other linux related part. Because I have enabled the after post sound in bios. 
> When I power in on the headphone work. Then I login to linux and when I reboot to login to 
> windows, the bios post sound does not come from headphone.

So the question is about BIOS beep after some sort of self test, 
and not the audio in general?

Out of curiosity. Once it is working, is it still work if you
reboot several(2) times to Windows?

Ivan

Re: [gentoo-user] headphone does not work in windows After logging to linux

[behrouz khosravi]

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

On Nov 21, 2014 6:50 PM, "Ivan T. Ivanov" <iivanov@mm-sol.com> wrote:
>
>
> On Fri, 2014-11-21 at 18:38 +0330, behrouz khosravi wrote:
> >
> > Well I have no problem with it in linux. It always works in linux but I
think there is a problem
> > with alsa or some other linux related part. Because I have enabled the
after post sound in bios.
> > When I power in on the headphone work. Then I login to linux and when I
reboot to login to
> > windows, the bios post sound does not come from headphone.
>
> So the question is about BIOS beep after some sort of self test,
> and not the audio in general?
>
> Out of curiosity. Once it is working, is it still work if you
> reboot several(2) times to Windows?
>
> Ivan
>
>

Actually I wanted to point out that something is happening in linux and the
windows is a victim this time!

Booting several times into windows is ok and no sign of that problem.

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

Re: [gentoo-user] headphone does not work in windows After logging to linux

[Matti Nykyri]

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

> On Nov 21, 2014, at 17:37, behrouz khosravi <bz.khosravi@gmail.com> wrote:
> 
> 
> On Nov 21, 2014 6:50 PM, "Ivan T. Ivanov" <iivanov@mm-sol.com> wrote:
> >
> >
> > On Fri, 2014-11-21 at 18:38 +0330, behrouz khosravi wrote:
> > >
> > > Well I have no problem with it in linux. It always works in linux but I think there is a problem
> > > with alsa or some other linux related part. Because I have enabled the after post sound in bios.
> > > When I power in on the headphone work. Then I login to linux and when I reboot to login to
> > > windows, the bios post sound does not come from headphone.
> >
> > So the question is about BIOS beep after some sort of self test,
> > and not the audio in general?
> >
> > Out of curiosity. Once it is working, is it still work if you
> > reboot several(2) times to Windows?
> >
> > Ivan
> >
> >
> 
> Actually I wanted to point out that something is happening in linux and the windows is a victim this time!
> 
> Booting several times into windows is ok and no sign of that problem.
With those symptoms you can not tell which element is not following the spec. Problem can be within linux driver, windows driver, card firmware or in bios. 

-- 
-Matti

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

Re: [gentoo-user] headphone does not work in windows After logging to linux

[Alan McKinnon]

On 21/11/2014 17:08, behrouz khosravi wrote:
> 
> On Nov 21, 2014 6:23 PM, "Matti Nykyri" <matti.nykyri@iki.fi
> <mailto:matti.nykyri@iki.fi>> wrote:
>>
>> On Nov 21, 2014, at 16:15, behrouz khosravi <bz.khosravi@gmail.com
> <mailto:bz.khosravi@gmail.com>> wrote:
>>
>>>
>>> > Do you reboot in the between or are you running somekind of virtual
> machine? Usb headphones or what? What sound driver? I've had problems
> with NIC between reboots. They were cleared by removing power cord for
> multiple minutes while rebooting. I got rid of the problem when i
> updated NIC's driver (bug in driver).
>>> >
>>> > -- 
>>> > -Matti
>>>
>>> No. It happen every time I boot into linux. Gentoo or Arch.
>>> removing power helps but is annoying.
>>> its not usb, but I dont know what is called! the ordinary type!
>>> Its a realtek chip .
>>> The bug that you mentioned is related to linux driver or windows driver?
>>
>>
>> I have realtek R6168/6111/6169 NIC. It works in Linux with realtek's
> driver not with the one included in kernel. Windows fails to initialize
> the NIC properly when I reboot from linux to windows. When NIC is reset
> by recycling power windows will be able to initialize it. Downgrading
> windows (7 64bit) dirver to an ancient one fixed the problem. The
> up-to-date realtek driver didn't work correctly. 
>>
>> lspci -v
>>
>> You can check what driver kernel uses for you audio. Also the bug can
> be in alsa. The ways of alsa quite complicated... You are using alsa
> right? What error message does alsa give when you try to play audio?
> Well I have no problem with it in linux. It always works in linux but I
> think there is a problem with alsa or some other linux related part.
> Because I have enabled the after post sound in bios. When I power in on
> the headphone work. Then I login to linux and when I reboot to login to
> windows, the bios post sound does not come from headphone.
> It seems something is wrong in the linux part!


This kind of thing is quite common actually, more so in days gone past.

Speaking conceptually, what happens is something like this:

Consider a driver for a hardware on any OS. That driver knows how it
shuts down the hardware. It expects the hardware to be in the same state
(registers, sleep state, etc) when powered back up; if so then all is
good. There are supposed to be standards for these things and drivers
are supposed to obey them to avoid these problems when booting other
OSes (or even upgrading a driver that needs a reboot).

One of your drivers (Windows or Linux) or the hardware itself is not
obeying the standard, so Windows doesn't find the hardware in the state
it expects and doesn't properly initialize the hardware. There are 3
ways this can go wrong:

1. The Linux driver is buggy (not 100% per spec) and doesn't shut
down/power up the device properly.
2. Same with the Windows driver.
3. The hardware might not be per standard (the Windows driver will have
been coded to work around it if this is the case).

Usually, the Linux driver is coded per spec. Hardware often doesn't do
what the spec says and Windows drivers are often shocking. It's not
always true, but I find it's a good assumption to start from.

You need to find a combination of various drivers in both OSes that work
nice together and with the hardware. It's a trial and error process so
unless someone has already solved this for you, expect to try lots of
combinations.



-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] headphone does not work in windows After logging to linux

[Mick]

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

On Friday 21 Nov 2014 15:24:43 Alan McKinnon wrote:
> On 21/11/2014 17:08, behrouz khosravi wrote:
> > On Nov 21, 2014 6:23 PM, "Matti Nykyri" <matti.nykyri@iki.fi
> > 
> > <mailto:matti.nykyri@iki.fi>> wrote:
> >> On Nov 21, 2014, at 16:15, behrouz khosravi <bz.khosravi@gmail.com
> > 
> > <mailto:bz.khosravi@gmail.com>> wrote:
> >>> > Do you reboot in the between or are you running somekind of virtual
> > 
> > machine? Usb headphones or what? What sound driver? I've had problems
> > with NIC between reboots. They were cleared by removing power cord for
> > multiple minutes while rebooting. I got rid of the problem when i
> > updated NIC's driver (bug in driver).
> > 
> >>> No. It happen every time I boot into linux. Gentoo or Arch.
> >>> removing power helps but is annoying.
> >>> its not usb, but I dont know what is called! the ordinary type!
> >>> Its a realtek chip .
> >>> The bug that you mentioned is related to linux driver or windows
> >>> driver?
> >> 
> >> I have realtek R6168/6111/6169 NIC. It works in Linux with realtek's
> > 
> > driver not with the one included in kernel. Windows fails to initialize
> > the NIC properly when I reboot from linux to windows. When NIC is reset
> > by recycling power windows will be able to initialize it. Downgrading
> > windows (7 64bit) dirver to an ancient one fixed the problem. The
> > up-to-date realtek driver didn't work correctly.
> > 
> >> lspci -v
> >> 
> >> You can check what driver kernel uses for you audio. Also the bug can
> > 
> > be in alsa. The ways of alsa quite complicated... You are using alsa
> > right? What error message does alsa give when you try to play audio?
> > Well I have no problem with it in linux. It always works in linux but I
> > think there is a problem with alsa or some other linux related part.
> > Because I have enabled the after post sound in bios. When I power in on
> > the headphone work. Then I login to linux and when I reboot to login to
> > windows, the bios post sound does not come from headphone.
> > It seems something is wrong in the linux part!
> 
> This kind of thing is quite common actually, more so in days gone past.
> 
> Speaking conceptually, what happens is something like this:
> 
> Consider a driver for a hardware on any OS. That driver knows how it
> shuts down the hardware. It expects the hardware to be in the same state
> (registers, sleep state, etc) when powered back up; if so then all is
> good. There are supposed to be standards for these things and drivers
> are supposed to obey them to avoid these problems when booting other
> OSes (or even upgrading a driver that needs a reboot).
> 
> One of your drivers (Windows or Linux) or the hardware itself is not
> obeying the standard, so Windows doesn't find the hardware in the state
> it expects and doesn't properly initialize the hardware. There are 3
> ways this can go wrong:
> 
> 1. The Linux driver is buggy (not 100% per spec) and doesn't shut
> down/power up the device properly.
> 2. Same with the Windows driver.
> 3. The hardware might not be per standard (the Windows driver will have
> been coded to work around it if this is the case).
> 
> Usually, the Linux driver is coded per spec. Hardware often doesn't do
> what the spec says and Windows drivers are often shocking. It's not
> always true, but I find it's a good assumption to start from.
> 
> You need to find a combination of various drivers in both OSes that work
> nice together and with the hardware. It's a trial and error process so
> unless someone has already solved this for you, expect to try lots of
> combinations.

On a Dell XPS laptop on occasions I used to find that there was no sound.  If 
I booted into MSWindows the OS would reset the sound, without having to login 
to a desktop and all would be fine thereafter.  Quite a random event, but 
thankfully I haven't had this problem for a few months now.  Perhaps the alsa 
drivers got better with time.  Now if this Radeon kernel regression problem 
were to go away too so that I can hibernate, I would be quite happy.  :-p
-- 
Regards,
Mick

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