http://bugzilla.opensuse.org/show_bug.cgi?id=898395 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(suse.junky@t-onli | |ne.de) --- Comment #37 from Takashi Iwai <tiwai@suse.com> --- (In reply to Bit Juggler from comment #36)

...

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"?

Yes.

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

Yes. You don't have to be root at all except for the installation. All git tasks, and the build (via make) itself *should* be performed by normal user.

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?

No, kernel-source package is totally irrelevant here. We just need kernel-desktop or whatever kernel-binary package with the corresponding kernel version. Boot with 3.8 kernel. Then run "make localmodconfig". This is an important step. The later step, the build and install, can be done on any kernel, though.

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

No.

...

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?

Then something wrong in your git repo. You must use Linus' git tree, not SUSE's one. -- You are receiving this mail because: You are on the CC list for the bug.