Comment # 36 on bug 898395 from Bit Juggler

(In reply to Takashi Iwai from comment #35)
> I guess the reporter tries to compile from SUSE kernel git tree.  It's
> different from the upstream Linux kernel git tree.  SUSE kernel git contains
> only SUSE-specific patches, and doesn't contain the base kernel source
> itself.

I did (as a normal user in my HOME directory):

user@MACHINE:~> git clone git://kernel.opensuse.org/kernel-source.git
Klone nach 'kernel-source'...
remote: Counting objects: 307224, done.
remote: Compressing objects: 100% (102272/102272), done.
remote: Total 307224 (delta 203030), reused 302318 (delta 199515)
Empfange Objekte: 100% (307224/307224), 886.14 MiB | 1.19 MiB/s, Fertig.
L�se Unterschiede auf: 100% (203030/203030), Fertig.
Pr�fe Konnektivit�t... Fertig.
user@MACHINE:~>

> 
> There is an expanded SUSE kernel tree that contains the whole Linus kernel
> tree, too.  You may use this tree, or just use Linus tree instead.
> 
> FYI, the Linus tree is found at
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> 

Will i get the Linus tree by doing "git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git"?

Can i do this as a user in my HOME directory or must i be root and go to
/usr/src/linux?

I have the openSUSE kernel-source-3.17.2-1.1.g1afb260-package installed on my
system. Does that interfere with the source which i will get via the procedur
mentioned above?

Can i use the kernel-source-package instead of downloading sources from a git
repository?

> Also, you can create a minimal kernel config matching for the running system
> via "make localmodconfig".  That is,
> 
> 1. boot the working SUSE 3.8 kernel
> 2. Confirm BT is working there
> 3. On the Linus git tree:
> 
>    % git checkout v3.8

My last attempt to use something like "v3.8" resulted in an error message
"Ung�ltige Referenz-Eingabe: v3.9".
How can i find out which version string is valid / can be used?

>    % make localmodconfig
> 
>    Then edit .config file, especially better to modify CONFIG_LOCALVERSION
> to something unique, e.g. "-test".
>    
> 4. Build, install and test.
> 
> After confirming this self-made 3.8 kernel works, save your .config file
> once.  Then do "git checkout v3.9", and "make localconfig", press many
> RETURN keys until all satisfied, build, install and retest 3.9 kernel.
> 
> Once when confirming this 3.9 kernel is really broken, you can start
> bisection there.  Save .config file for 3.9 kernel as well.  Then do "git
> bisect start", "git bisect good v3.8", "git bisect bad v3.9".
> 
> You may need to copy the backup .config either from 3.8 or 3.9 during
> bisection.
> 

Thank you very much for your help !


> Have fun :)

There might be a remote chance that i buy a new bluetooth dongle in the near
future ;-)