That is very strange indeed, as all is normal today with rc3. Where are you seeing the list of fixes that have been made to rc3 Larry?
Thank You,
That is very strange indeed, as all is normal today with rc3. Where are you seeing the list of fixes that have been made to rc3 Larry?
Thank You,
On 09/30/2013 04:36 PM, jdmcdaniel3 wrote:
>
> lwfinger;2588662 Wrote:
>> On 09/30/2013 02:26 PM, jdmcdaniel3 wrote:
>>>
>>> I am not sure how long one should wait to decide an issue is fixed,
>> but
>>> with kernel 3.12-rc3, I have seen no video issues today at all. That
>> is
>>> why I had wondered if a video fix had been put through which might
>> show
>>> in a change log for the new kernel.
>>
>> Between 3.12-rc2 and -ec3, there are no patches for nouveau. The fix
>> could,
>> however, have been in some other component.
>>
>> There are several fixes in drm/i915 and drm/radeon.
>
> That is very strange indeed, as all is normal today with rc3. Where are
> you seeing the list of fixes that have been made to rc3 Larry?
I see the commit messages using ‘git log’. I do not download the tarball update
On 09/30/2013 05:02 PM, Larry Finger wrote:
> On 09/30/2013 04:36 PM, jdmcdaniel3 wrote:
>>
>> lwfinger;2588662 Wrote:
>>> On 09/30/2013 02:26 PM, jdmcdaniel3 wrote:
>>>>
>>>> I am not sure how long one should wait to decide an issue is fixed,
>>> but
>>>> with kernel 3.12-rc3, I have seen no video issues today at all. That
>>> is
>>>> why I had wondered if a video fix had been put through which might
>>> show
>>>> in a change log for the new kernel.
>>>
>>> Between 3.12-rc2 and -ec3, there are no patches for nouveau. The fix
>>> could,
>>> however, have been in some other component.
>>>
>>> There are several fixes in drm/i915 and drm/radeon.
>>
>> That is very strange indeed, as all is normal today with rc3. Where are
>> you seeing the list of fixes that have been made to rc3 Larry?
>
> I see the commit messages using ‘git log’. I do not download the tarball update
> - I have the full git repo.
You can see the patch subject lines in the posting at
http://lkml.indiana.edu/hypermail/linux/kernel/1309.3/03680.html.
Thanks Larry. Silly me not to look at the end of the rc3 announcement by Linus.
Thank You,
This morning we find that kernel 3.11-rc4 has been released and can be found here: https://www.kernel.org/pub/linux/kernel/v3.x/testing/linux-3.12-rc4.tar.xz
And this is what Linus had to say about the rc4 release: https://lkml.org/lkml/2013/10/6/148 (including the changes made)
I have not loaded it yet, but it will happen today after I finish installing a new hard drive for /home and for my VM’s.
Thank You,
I finished installing this morning the only glitch I see and this has been happening since kernel 3.11.3 is that my netgear usb wireless no longer works
16423.095520] usb 2-1.2.2: New USB device strings: Mfr=16, Product=32, SerialNumber=48
[16423.095525] usb 2-1.2.2: Product: WNA1100
[16423.095530] usb 2-1.2.2: Manufacturer: NETGEAR WNA
[16423.095535] usb 2-1.2.2: SerialNumber: 12345
[16423.096281] usb 2-1.2.2: ath9k_htc: Firmware htc_9271.fw requested
[16423.100409] usb 2-1.2.2: ath9k_htc: Failed to get firmware htc_9271.fw
[16423.100571] usb 2-1.2.2: ath9k_htc: USB layer deinitialized
On 10/07/2013 09:36 AM, dale14846 wrote:
>
> jdmcdaniel3;2589743 Wrote:
>> This morning we find that kernel 3.11-rc4 has been released and can be
>> found here: http://tinyurl.com/oorssmv
>>
>> And this is what Linus had to say about the rc4 release:
>> https://lkml.org/lkml/2013/10/6/148 (including the changes made)
>>
>> I have not loaded it yet, but it will happen today after I finish
>> installing a new hard drive for /home and for my VM’s.
>>
>> Thank You,
> I finished installing this morning the only glitch I see and this has
> been happening since kernel 3.11.3 is that my netgear usb wireless no
> longer works
>
>
> Code:
> --------------------
> 16423.095520] usb 2-1.2.2: New USB device strings: Mfr=16, Product=32, SerialNumber=48
> [16423.095525] usb 2-1.2.2: Product: WNA1100
> [16423.095530] usb 2-1.2.2: Manufacturer: NETGEAR WNA
> [16423.095535] usb 2-1.2.2: SerialNumber: 12345
> [16423.096281] usb 2-1.2.2: ath9k_htc: Firmware htc_9271.fw requested
> [16423.100409] usb 2-1.2.2: ath9k_htc: Failed to get firmware htc_9271.fw
> [16423.100571] usb 2-1.2.2: ath9k_htc: USB layer deinitialized
You need to install the kernel-firmware package. Perhaps the firmware file name
changed in 3.11.
I downloaded the tarball untar ed the thing and did
make toolchain
make firmware
got errors then found Index of /ath9k-htc/version-1.3.2
downloaded the two *.fw files and copied them to /lib/firmware.
problem solved
On 10/07/2013 04:06 PM, dale14846 wrote:
>
> lwfinger;2589793 Wrote:
>> On 10/07/2013 09:36 AM, dale14846 wrote:
>>>
>>> jdmcdaniel3;2589743 Wrote:
>>>> This morning we find that kernel 3.11-rc4 has been released and can
>> be
>>>> found here: http://tinyurl.com/oorssmv
>>>>
>>>> And this is what Linus had to say about the rc4 release:
>>>> https://lkml.org/lkml/2013/10/6/148 (including the changes made)
>>>>
>>>> I have not loaded it yet, but it will happen today after I finish
>>>> installing a new hard drive for /home and for my VM’s.
>>>>
>>>> Thank You,
>>> I finished installing this morning the only glitch I see and this
>> has
>>> been happening since kernel 3.11.3 is that my netgear usb wireless no
>>> longer works
>>>
>>>
>>> Code:
>>> --------------------
>>> 16423.095520] usb 2-1.2.2: New USB device strings: Mfr=16,
>> Product=32, SerialNumber=48
>>> [16423.095525] usb 2-1.2.2: Product: WNA1100
>>> [16423.095530] usb 2-1.2.2: Manufacturer: NETGEAR WNA
>>> [16423.095535] usb 2-1.2.2: SerialNumber: 12345
>>> [16423.096281] usb 2-1.2.2: ath9k_htc: Firmware htc_9271.fw
>> requested
>>> [16423.100409] usb 2-1.2.2: ath9k_htc: Failed to get firmware
>> htc_9271.fw
>>> [16423.100571] usb 2-1.2.2: ath9k_htc: USB layer deinitialized
>>
>> You need to install the kernel-firmware package. Perhaps the firmware
>> file name
>> changed in 3.11.
>
> I downloaded the tarball untar ed the thing and did
>
> Code:
> --------------------
> make toolchain
> make firmware
> --------------------
>
>
> got errors then found ‘Index of /ath9k-htc/version-1.3.2’
> (http://www.jxself.org/ath9k-htc/version-1.3.2/)
> downloaded the two *.fw files and copied them to /lib/firmware.
> problem solved
“sudo zypper install kernel-firmware” would have been a lot easier.
So, today, after a local hard drive replacement (1 TB to 2 TB) for two Partitions, now both double in size, I have installed kernel 3.12-rc4 and it is working like a champ, no problems at all.
Thank You,
Found the next release of the kernek 3.12-rc5: https://www.kernel.org/pub/linux/kernel/v3.x/testing/linux-3.12-rc5.tar.xz
I did not find any post yet from Linus on the new rc.
Thank You,
Thanks for the help noee. I did get around to compiling and installing kernel 3.12-rc5 this morning and its working just fine for me.
Thank You,
I just posted in your “kernel” blog, so not to x-post here, but I’m having trouble with SAKC…PM me or take it to the blog?
So do you use a non-stand disk setup? Let me say this looks like an openSUSE 13.1 bug and I would make a separate post on the problem in the 13.1 RC1 thread.
Thank You,
Yes, I do, is that it? Either way, I ended up hosing the system (boots now but get no video, have to alt-ctrl-f1 to reboot), even in recovery mode. I have no idea how to fix this (tried zypper dup, etc.) so I’m going to just re-install from RC1 and use a standard disk setup.
Well the bottom line is that it is best to keep openSUSE 13.1 as it is released as you are testing it, not the ability to change the kernel version. That does not mean I would not give it a try, but in your case, your best bet is to reload openSUSE 13.1 if that is what you want to use or switch back to openSUSE 12.3 where kernel updates work just fine.
In the mean time it looks like an openSUSE 13.1 bug which should be reported at: https://bugzilla.novell.com/index.cgi
Thank You,
Do you mean the fact that I was using a non-stand disk setup causing kernel update to fail? I’m not sure how to verify that.
Yes, but it sounds like a bug on the new version of openSUSE 13.1 that needs to be reported as a bug. Verification could be a standard disk setup, depending on the trouble you want to go through.
Thank You,
@jdmc:
roger, wilco. Installs take only about 15 minutes on this machine, of course, the kernel build takes about an hour…