gentleman!!!
back to topic:
Whats the pro/con for the new 3.x kernel?
Why did they fork from 2.x?
I really can't see this much of improvement?
Will Slackware ship again with a rich F2 boot screen?

How can I make the OS indicator show Slackware and not just generic Linux?

another release on the go. (hopefully), life is to short to learn

Hi,
Not a relevant topic to this thread.

So!
Open a new tab place about:config in the address bar then search for 'general' then modify this string; to Slackware Linux

This is from memory so buyer beware.

1 members found this post helpful.

Depends on your browser. In firefox 8:
1. Go to whatsmyuseragent.com and copy this string. Mine was:
2. Go to about:config, add new integer "general.useragent.override"
3. Paste the ua string you got in step 1 into value textbox in step 2
4. Insert 'Slackware' before 'Linux' within the parentheses. Mine now reads:
There was a whole thread (now closed) dedicated to testing this out here.

HTH

1 members found this post helpful.

The problem is that eventually they will get rid of this option as well (I read this on the mozilla forums or bug reports). They used to have an OS override, but they got rid of it. I don't see why we can't select the distro we use, instead of auto-detect using user agent.

1 members found this post helpful.

There's also the User Agent Switcher add-on, but we're way off-topic, so I'll shut up now!

1 members found this post helpful.

using the firefox help/troubleshooting information tag will also give you the useragent string to modify

1. The 3.0 kernel series is not that much of a radical departure from the 2.6.x kernel. Linus decided to put in place a new naming convention (3.0) instead of calling the next kernel 2.6.40.

2. PV and the team will make that call. I have no idea if a change in boot screen is in the works.

kind thanks to all contributing to my "Slackware looking" UA tweak (sorry for OT-ing BTW)
:}
kind of redundant (don't ask which instance did trigger it in the end)
I did OT-ed it just to showcase a (silly?) way to advocate Slackware

Re 3.0
did anyone notice any improvement worth a mention?
I only notice new drivers of interest going to "staging" and going broken there
Namely I have a USB WiFi that worked like a charm in 13.0 with two different (out of tree, OEM supplied...) drivers, one worked excellent with kismet/airodump-ng the other had excellent throughput.
I guess the reason for this are two different firmwares the driver uses
Then in 13.1 the other driver failed to compile (sliding ABI of kernel)
Then in 13.37 the only driver working is in staging, and I'm clueless if the other (removed device ID) is able to drive my dongle do I patch tie ID in the source and "give it a shot"...

In the end:
Is it worth to play with the 3.x family or I wait PV and stick to Slackware OEM kernels?
And will the next Slackware have the APM back by default for the i486 single processor build?
pretty please?

Just to say something about that.

I really look forward for a faster version, preferably one focused in Xfce.

May i note a ting here:
I have a running kernel (probably with errors in config) from 3.1.x branch and it does run quite a bit faster than the OEM 2.6.38.4 one
here my config FWIW:
if anyone could find why it oops-es my comp when i pull a USB device
or why it runs faster-leaner than OEM on my 2.5+G (1.83GHz really) barton/DDR1 system?
And, it is intended for a i586 1GHz system (the Gecko from my signature)
Best regards
Stevan C.

Attached Files

config-custom-3.1.5.txt (103.6 KB, 11 views)

As long as the Intel Matrix Array glitch in mdadm is fixed in the next incarnation I'll be happy

I have recently purchased/replaced numerous laptops. All of them sandy bridge second generations with the hd 3000 series video cards (on board). I have i3/i5 and i7. Remember these are only one year old (give or take) processors.

While the kernel in slackware 13.37 does support the processors and video at a basic level of functionality.

Without the 3.0+ kernel you do not get hdmi audio, any of the numerous bug fixes to intel video since that uses kvm.

The 3.0+ kernels also support the intel_backlight for laptops. The stock kernel in Slackware wouldn't allow me to control screen brightness.

Furthermore, the alsa modules for many of these computers are only partly implementing controls for these devices.

Example, intel cougarpoint hd has no ability to toggle on the pc speakers with headphone connect/disconnect.

Also there is numerous wireless drivers added to the 3.0 series especially for broadcom and the realtek. They actually work in the 3.0+ series.

I could give alot more examples why the 3.0+ kernels are needed for anyone with a sandy bridge 2nd gen. Basically anyone with intel across the board will see improvements.

I find graphics performance better on my old intel atom netbooks as well.

Sadly, I have to have the desktop effects off on the sandy bridge computers, as resume from hibernate is not reliable. About 9/10 resumes is a complete lockup. The xorg in slack needs a bump. As I've built new libdrm, latest intel it seems that there must be some underlying $app somewhere in the graphic stack that needs a bump. Most likely the mesa but I haven't gotten around to that yet.

I hope Slackware does not have a boot screen. In an attempt to see if a computer was worth purchasing or not, I tried live cd's from Fedora and Ubuntu 11.10 as they ship with 3.0+ kernels.

And all I can tell you is, that it's ironic that distro's that patch the heck out of their OS because of their prior fiddle futs patching needs a bootsplash to hide all the errors that their distro has.

FWIW my Slack 13.37 with 3.2 kernel and alien bob's kde 4.6.5 runs better than ubuntu 11.10 and Fedora.

Just wish I could take advantage of the fast vid card for desktop effects, but I'm willing to wait for Pat to come back and "hit it hard"

So if you want to try them distro's out just to test a laptop then that's wise. But don't bother running them. There's too many patches for the sandy bridges and them distro's are fundamentally broken for second gen intels.

1 members found this post helpful.

My Slackware, my preciousssss!