AuthorTopic: new 5.9 kernel ready for testers (Read 29378 times)

I found this page yesterday and downloaded some of the stuff. Also, the kernels were finished downloading this morning. Hopefully I can test later tonight. Anyway, the point was that they suggest a different firmware for the 2.6.24 and the 2.6.25 kernels, as well as for b43 legacy and bcm43xx.

Tried the firmware without any luck whatsoever. Modules weren't loading. Loaded them manually and still no sign of the card in iwcong. Did some more searching and finally gave up when I made it to a bcm43xx mailing list post dated June 9. A dev "Larry" who has this card (BCM4310) says it's identified incorrectly and a no go at this time and to use ndiswrapper.

Ok I've downloaded the new kernel and modules and installed same using installpkg but when I run /sbin/lilo it does not find the new kernel what did I do wrong? I know it's early this morning and I had a hard day yesterday but I'm missing something here. Thanks Dave

Installed on my Gateway laptop. Seems to work great. In otherwords... I haven't noticed anything break? The last test kernel worked fine on all my hardware. This one does as well.Although I had a minor sna-foo with acpi and controlling brightness. I knew they were depreciating acpi stuff in /proc and had moved it into /sys. Our kernels are holding on to /proc since it's available. This puts my lcd brightness in two locations. I opted to write my brightness scripts based on /sys so they would work now and in the future. My brightness isn't handled by bios. The keys trigger a acpi event that I need to catch and redirect to my scripts. Turns out they changed the api for brighness in /sys. Rather then echoing the desired value to brightness, you now have to echo the brightness level. So my scripts failed. But... on the bright (no pun) side. It really is a easier way. Especially if you want to use dbus and hal to discover and adjust instead of pure bash. The advantage of using the hal method is huge since the actual location of the brightness can be anywhere depending on the hardware. Hal will find it for you, so the scripts can be generic and work for all. And if you're a Hal hater, you can locate it for yourself and hardcode the path. I love the choices we have with Linux

Someday I'm going to write a howto about brightness keys and provide several ways to tackle them.

Another interesting acpi thing about this kernel...With 2.6.24.3 I had to add "acpi_sleep=s3_bios,s3_mode" to my lilo append (my Gateway laptop). I couldn't resume from suspend or hibernate without it. My video would never turn back on. With this new kernel I added the same things to lilo append and found half of my resumes would result in a partial resume with a frozen screen. I tried removing the append entries and everything resumes great. Faster even.

So far this kernel has been very user friendly, needing no extra tweaks to get things running on this Gateway and the wifes HP laptops. Well... with the exception of loading ndiswrapper for both. But I don't really consider that unusual.