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