On 06/16/2012 10:56 AM, jdmcdaniel3 wrote:
>
> It seems that the problem with the openSUSE Firewall has come back in a
> different form and once again, I find Samba will not work when the
> openSUSE Firewall is enabled. Previously in kernel 3.4, we needed to
> add the following kernel configuration to get the Firewall and Samba to
> work together:
>
> CONFIG_NETFILTER_XT_TARGET_LOG=m
>
> Now, I see this parameter is set, but the same old problem result has
> come back again. Disabling the Firewall allows Samba to work properly
> it would seem. Unlike the problem before, being able to turn the
> Firewall on and off at will does work properly. So, its hard to know
> for sure just what the problem might be. Any other comments would be
> helpful to hear if indeed you see the same problem or not. I see this
> issue on three PC’s, but they are all configured the same by me. Since
> we are creatures of habit, we tend to extend the same issue over and
> over if its a user setup problem. So, your input is needed if you use
> Samba and have kernel 3.5-rc2 loaded from any source. Let your voice be
> known.
Is anything logged by the firewall?
Please post your .config on a pastebin site and I’ll have a look. I don’t use
Samba on any 12.2 systems, thus I would not see the problem.
Well on Saturday 6-16-12 kernel 3.5-rc3 was released. I have installed it this morning without any problems. VirtualBox continues to work with the fix supplied by Larry. I have installed the recently released nVIDIA driver 295.59 with no problems.
The issue with Samba I had on Friday does not seem to be present this morning using kernel 3.5-rc3 and in fact after further review I found that the Samba smdb application had stopped for some reason on two different computers. I was able to restart it and so no way to know if it was related to the latest kernel. I had dropped back to kernel 3.4.2 where all was working, switched back to 3.5-rc2 and it stopped working, but I was able to restart smdb and it continued to work. On my main PC I loaded kernel 3.5-rc3 today and found smdb still working fine so perhaps there is nothing wrong with the kernel, only my setup.
I must admit to having a headache this morning after to much celebrating (the upcoming) Fathers day last night and the issue with my broken arm so I am as sharp as a bowling ball this morning. Perhaps things will improve as the day goes on.
The arm is doing OK as long as I don’t try to do too much. Its a broken radius but its not serious as broken bones go. I did do too much yesterday it would seem as it was throbbing when I went to bed. I keep it in a sling, take a anti-inflammatory prescription and go back to the Doctor in July to see how I am doing. Thanks for asking ,
From Linus Torvalds <>
Date Sat, 16 Jun 2012 17:59:39 -0700
Subject Linux 3.5-rc3
So at this stage I always wish there were fewer changes in the -rc
releases, but -rc3 is out and while it could be smaller (it’s just
under 300 non-merge commits), it doesn’t seem too bad.
The week started calm with just a few small pulls, with people
apparently really trying to make my life easier during travels - thank
you. But it kind of devolved at some point, and I think more than half
the pull requests came in the last two days and they were bigger too.
Oh well…
Considering the recent delays with openSUSE 12.2 betas and release candidates, how likely is it that kernel 3.5 will be pushed out with openSUSE 12.2 final? Or will the final releases of each be so out of sync as to not happen?
On 06/21/2012 01:06 PM, funkypigeon wrote:
>
> Considering the recent delays with openSUSE 12.2 betas and release
> candidates, how likely is it that kernel 3.5 will be pushed out with
> openSUSE 12.2 final? Or will the final releases of each be so out of
> sync as to not happen?
It will not happen. With Beta2, the updates have been switched from Factory to
Factory-snapshot. Updates to Factory will each be evaluated to see if that
change belongs in 12.2 or the next major release. As a result, 12.2 is
essentially frozen.
Kernel 3.5 will not be released for at least one month. By that time, changes to
12.2 will be limited to bug fixes.
Well on Sunday 6-24-12 kernel 3.5-rc4 was released. I have installed it this afternoon without any problems. VirtualBox continues to work with the fix supplied by Larry. I have installed the recently released nVIDIA driver 295.59 with no problems using SANDI and DKMS. Samba and the Firewall look good as well as networking in general though I have no wireless on this one to look at. The only thing I noticed was a lot of disk activity after my restart, but not sure what that was about for a full 2 minutes after the desktop was loaded.
**A new packet scheduler is designed to help avoid buffer bloat and “Early Retransmit” offers faster connection recovery after TCP packet loss. The E1000e driver already supports the network chip for Intel’s next-generation desktop and notebook platform.
**
To start the week, Linus Torvalds published the fourth release candidate for Linux 3.5. In the release announcement, Torvalds says that it has more than 200 commits, but notes that “they really are all pretty tiny and insignificant”.
Well on Saturday 6-30-12 kernel 3.5-rc5 was released, just six days since rc4 came out. I have installed it tonight without any problems. VirtualBox continues to work with the fix supplied by Larry. I have installed the recently released nVIDIA driver 295.59 with no problems using SANDI and DKMS. Samba and the Firewall look good as well as networking in general. openSUSE 12.1 seems to be running very well using kernel 3.5 so far.
So there are two ways to get and test kernel 3.5, one is to use my SAKC script you can find here: S.A.K.C., and get the latest kernel from here: The Linux Kernel Archives or you can add the following URL as a repository with no quotes “http://download.opensuse.org/repositories/Kernel:/HEAD/standard/” in YaST / Software / Software repository. Anyone adding in a kernel using the repository method, I suggest that you edit the text file /etc/zypp/zypp.conf as root, find (or add) the line that says “multiversion = provides:multiversion(kernel)” with no comment in front “#”. This action (removing the comment #) will allow YaST to maintain more than one kernel version for an easy switch back to your standard kernel version should you decide to do so. If you use SAKC, your old kernel, added by YaST, will not be removed and is still selectable from grub. I have had no problems using SAKC to use kernel 3.5 while also testing openSUSE 12.2.
I ask that you consider giving the new kernel 3.5 a try on your openSUSE PC system. You may be amazed of just how fast the new 3.5 kernel version is. Please make any remarks about kernel 3.5 here. We want to hear from you so don’t delay and avoid future regret in testing kernel 3.5 before it is too late.
**Linux 3.5 is now capable of the “FireWire Target Disk Mode”, which is a familiar Mac feature. Btrfs logs data errors, allowing unreliable storage media to be detected. Checksums have been implemented to ensure that Ext4 metadata is consistent. **
Together with the Linux-Iscsi.org (LIO) target infrastructure software, the new FireWire SBP-2 fabric module enables Linux 3.5 to export local storage devices via FireWire so that other systems can mount them as an ordinary FireWire storage device. Many Apple systems have offered such a “FireWire target disk mode” for some time; a screenshot by one of the contributing developers shows that MacOS X can mount a device that a Linux system has made available via the new Linux FireWire fabric module. The new TCM_QLA2XXX fabric module, and the required support in the Qla2xxx driver, allow Linux to operate as a SCSI target with Qlogic’s series 2400, 2500 and 2600 fibre channel controllers; the same can also be achieved with the USB gadget target fabric module via UASP (USB Attached SCSI Protocol), provided that the USB controller is capable of the “gadget” features that allow it to operate as a USB master.
Kernel 3.5-rc6 has been released on this Saturday night (Austin Time) on 7-7-12. Its not yet posted at kernel.org (8:35 PM CDT) but you can get it using S.G.T.B. if you like. It compiled without any problems using S.A.K.C. and I loaded it using FastBoot which also works with openSUSE 12.2 and grub 2 now. I am using VirtualBox 4.1.18 presently and it recompiled normally under kernel 3.5-rc6 using DKMS. As you can see above, I installed the nVIDIA driver using DKMS installed using S.A.N.D.I., but you can manually load the nVIDIA driver using LNVHW if you prefer and find the latest driver links here: Installing the nVIDIA Video Driver the Hard Way.
Tonight I decided to use what I call the name dropper format with named small links that you can use. It can be fun formulating these so forgive me if I did so at your expense. The bottom line here is that kernel 3.5-rc6 is working great for me and something you should give a try. For those that would prefer to load the kernel using the repository method would want to add this repository and wait for rc6 to show up there “http://download.opensuse.org/repositories/Kernel:/HEAD/standard/”.
As always, I want to hear any comments you might want to make on using the new kernel 3.5 in in RC version.
Another week, another -rc. And happily, another week of calming down.
Noticeably fewer commits in here than in -rc5, and I think we’re
getting closer to a final release.
That said, it’s also summer (our Australian co-developers may
disagree, but they are in the minority), and with that I also wanted
to talk about the next merge window. Because I suspect that especially
a lot of the European developers have either taken off for vacation or
are getting ready to do so. August tends to be off-season for a lot
of people. I’m hoping summer plans not a huge part of the slowing down
of the rc patches, but I do suspect that the next merge window will
almost inevitably be completely overshadowed for some developers by
their vacation.
Which is fine, and I’m hoping that may just mean that 3.6 will be a
calmer release. I would ask that people who go on vacation do not
plan to send me their merge window stuff before leaving for vacation,
though. I’d really much rather see the merge delayed to 3.7 entirely
than have the developer push me the big changes, and then not be there
at all for the rc series.
Anyway, just keep that in mind, especially those of you planning on
taking all of August off.
Back to the -rc6 stuff: there’s mainly some btrfs and md stuff in
here, with the normal driver changes, arm updates and some networking
changes. And a smattering of random stuff (including docs etc). None
of it looks very scary, it’s all pretty small, and there aren’t even
all that many of those small changes. Shortlog appended.
With the help of uprobes, performance monitoring tools can now monitor userspace software. The ongoing overhaul of the ARM code is showing tangible success.
After years of development, dozens of aborted attempts and some major restructuring, the code for uprobes (userspace probes) has finally been merged into the kernel (1, 2, 3, 4, 5 and others). This enables the kernel to insert breakpoints into code for userspace software at runtime, though currently it can only be used via the kernel’s perf events subsystem. It enables tracing software that makes use of it – such as kernel component perf and version 1.8 of systemtap – to add tracepoints to userspace software, and thus monitor the runtime behaviour of the kernel and programs at the same time.
In conjunction with a new version of X Server, Linux 3.5 will offer better support for hybrid graphics. The Radeon driver will be a bit faster and support HDMI audio transport on more graphics chips. The audio drivers will support the Xonar DGX and Creative’s SoundCore3D.**
Changes in the way the graphics driver stores data in video memory mean that the Radeon driver in Linux 3.5 will now get better performance out of R600 to R900 (Radeon HD 2400 to 7670) GPUs. According to the commit comments, in tests using Lightsmark and Doom 3, frame rates on a Radeon HD 5750 rose by more than a third. The performance boost on other cards can, however, be different or absent altogether.
My only problem with the 3.5 kernel is I can’t get my logitech usb webcam to work. I have used sakc turbo, sakc standard, xconfig, menuconfig, plain old config, and the kernel head repo.
it works fine with the 3.4.4 kernel from the factory distro.
So turbo compile is not the answer as it loads only the kernel drivers for hardware actually working at the time of the compile, even including CD-ROM drives need to have a CD in them and you need to have any thumb drives plugged it. If you thought your config was not right, you can select to use your original default kernel configuration and if you knew what driver the camera used, check that config to see if it is being loaded. After any attempt to use Turbo mode in SAKC, I would go in and on purpose select the default config and let it compile and be loaded. I would do so with kernel 3.4.4, but compiled from SAKC and not loaded from a repository. If you use SAKC to compile an identical named kernel from another source, the old one will be renamed to .old in the /boot folder. For SAKC Turbo to be of any value, ALL devices must be online and working. Every optical drive has a disk, all networks are active, any thumb drive you will use needs to be plugged in. At compile time, only drivers for hardware that exist will be compiled into the kernel. It compiles faster and it loads faster but if it was not online when you did the Turbo Compile, its never going to work with the active kernel config you are using.
The kernel now better isolates containers and suspicious code. Event logging has been optimised and two important Android functions were merged.
When releasing Linux 3.5-rc6, Linus Torvalds made no indication as to when he might publish Linux 3.5, but he had previously pointed out some of implications the holiday period in the northern hemisphere might have on the main development phase of Linux 3.6. It’s possible that the sixth pre-release version may have been the last rc for Linux 3.5; therefore, with a description about the changes to the infrastructure of Linux 3.5, this article will conclude the “Coming in 3.5” Kernel Log mini-series as this kernel version will likely appear soon.
The first four parts of the series already discussed the improvements in networking, filesystems and storage, architecture, and drivers. In the networking area, however, there was one latecomer that should get a mention: the ipheth driver in Linux 3.5 not only supports tethering with various iPhone models, but now also support iPads.
I have just installed it tonight and everything is looking good for me so far. I am still using the nVIDIA driver 295.59 and VirtualBox 4.1.18 which compiled into kernel 3.5-rc7 without any problems at all. Now lets hear those comments as surely you have at least one to make about the next kernel version going to be released?
