This is the error I get if I use a bridged network, but it goes away if I use NAT and works OK. So, there is some problem I guess with my Network Adapter, VirtualBox and Kernel 3.11 that I do not yet understand. Otherwise, I am finding kernel 3.11 to be working just fine for me now.
On 07/29/2013 07:36 PM, jdmcdaniel3 wrote:
>
> lwfinger;2575360 Wrote:
>> On 07/29/2013 05:56 AM, jdmcdaniel3 wrote:
>>>
>>> Our Next Kernel version to test can be found here:
>>> http://tinyurl.com/mgrngxx
>>>
>>> And here is what Linus Had to say:
>> https://lkml.org/lkml/2013/7/29/16
>>>
>>> Since no fixes have been put forward for VirtualBox or nVIDIA, I
>> assume
>>> they still do not work with kernel 3.11, but I have not tried the
>> latest
>>> version yet as it is early here in Austin.
>>
>> VirtualBox continues to work with kernel 3.11 (for me, at least). I
>> have not
>> done any further investigation of what it takes to get the latest
>> nVidia driver
>> to build on 3.11 as my devices do not work with anything later than
>> 310.64, and
>> the machines that I am using to test 3.11-rcX only use the framebuffer
>> driver.
>>
>> One thing I noticed is that kernel 3.10-rc2 turned on tapping on my
>> touchpad. As
>> my personal characteristics always lead to unintended tap actions, I
>> must turn
>> it off. That was done by adding a line ‘Option “TouchpadOff” “2”’ to
>> file
>> /etc/X11/xorg.conf.d/50-synaptics.conf, and logging off/on. That line
>> is in the
>> “Input Class” stanza after the TabButton items.
>
> So tonight I loaded and installed kernel 3.11-rc3 and went further into
> why VirtualBox does not start:
>
> [image: http://paste.opensuse.org/view/download/37259989]
>
> This is the error I get if I use a bridged network, but it goes away if
> I use NAT and works OK. So, there is some problem I guess with my
> Network Adapter, VirtualBox and Kernel 3.11 that I do not yet
> understand. Otherwise, I am finding kernel 3.11 to be working just fine
> for me now.
I almost never use bridged networking as that requires always having the same
active network device. As my network device might be eth0 or wlanX with X
anywhere between 0 and ~25 (I have lots of wifi devices), I find NAT to have a
lot fewer problems.
Nonetheless, when I switched to the proper device for bridging, my VM also
failed to start. Clearly, kernel 3.11 has some kind of problem with bridging.
Perhaps I can make some time to bisect the problem. Am I correct that the
failure happened between 3.10 and 3.11-rc1?
Just for the record, I did just try tonight the new nVIDIA driver 325.15 with kernel 3.11-rc4 and it did not load. This video driver does work with kernel 3.10.5, but does not advance to kernel 3.11 as the kernel machine continues to roll forward leaving nVIDIA behind with almost every new release. The patch to get nVIDIA driver 319.32 to work with kernel 3.10 was very large and so many changes on nVIDIA’s part was required to the driver and I do not know how much difference exists now between the nVIDIA proprietary video driver 325.15 and kernel 3.11-rc4, but I hope we do not have to wait so long for their next fix. While nVIDIA continues to have the fastest driver, the open source version continues to get ever better in the Linux kernel and so I only load the nVIDIA driver on one testing computer.
>
> Just for the record, I did just try tonight the new nVIDIA driver
> 325.15
> with kernel 3.11-rc4 and it did not load. This video driver does
work
> with kernel 3.10.5, but does not advance to kernel 3.11 as the
kernel
> machine continues to roll forward leaving nVIDIA behind with
almost
> every new release. The patch to get nVIDIA driver 319.32 to work
with
> kernel 3.10 was very large and so many changes on nVIDIA’s part
was
> required to the driver and I do not know how much difference
exists
> now between the nVIDIA proprietary video driver 325.15 and kernel
> 3.11-rc4,
> but I hope we do not have to wait so long for their next fix.
While
> nVIDIA continues to have the fastest driver, the open source
version
> continues to get ever better in the Linux kernel and so I only
load
> the nVIDIA driver on one testing computer.
>
> Thank You,
>
James have you tried 325.08 on 3.105?
>
> upscope;2577599 Wrote:
>> jdmcdaniel3 wrote:
>>
>> >
>> > Just for the record, I did just try tonight the new nVIDIA
driver
>> > 325.15
>> > with kernel 3.11-rc4 and it did not load. This video driver
does
>> work
>> > with kernel 3.10.5, but does not advance to kernel 3.11 as the
>> kernel
>> > machine continues to roll forward leaving nVIDIA behind with
>> almost
>> > every new release. The patch to get nVIDIA driver 319.32 to
work
>> with
>> > kernel 3.10 was very large and so many changes on nVIDIA’s part
>> was
>> > required to the driver and I do not know how much difference
>> exists
>> > now between the nVIDIA proprietary video driver 325.15 and
kernel
>> > 3.11-rc4,
>> > but I hope we do not have to wait so long for their next fix.
>> While
>> > nVIDIA continues to have the fastest driver, the open source
>> version
>> > continues to get ever better in the Linux kernel and so I only
>> load
>> > the nVIDIA driver on one testing computer.
>> >
>> > Thank You,
>> >
>> James have you tried 325.08 on 3.105?
>> –
>> openSUSE 12.3(Linux 3.9.8-1.gf3348a8-desktop)|KDE 4.10.5
>> “release 4”|Intel core2duo 2.5 MHZ,|8GB DDR3|GeForce
>> 8400GS(NVIDIA-Linux-x86_64-319.32)
>
> No, I have not given the beta 325.08 driver a try. If in your
> situation you can give it a try, we would like to hear that
report.
>
> Thank You,
>
After I sent this message I decided to try the upgrade. I installed
325.15 on my 12.3 setup using your lnvhw script, then ran nvidia-
xconfig. Rebooted and I then decided ti upgrade from 3.9 to 3.10.5.
reran your script and nivida-xconfig. Rebooted agin and everthing is
now running with openSUSE 3.10.5-1 and 325-15 with no problems so
far. Only need to change signiture below now. Will test futher and
report.
I have installed it and it is working just fine for me so far. Sorry for being late in my post as I have had some recent medical issues to deal with, but here it is online. Consider that anyone can make a post here if they see the next release come up.
Only noticeable observation, Boot times for new kernel seem to be a little longer, on average,
13-08-18 <21:33:26> 3.10.7-1.g771dec3-desktop boot = 4.625s (kernel) + 16.921s (userspace) + kde = 42.676s
13-08-21 <16:51:32> 3.11.0-rc6-1.g771dec3-desktop boot = 5.025s (kernel) + 20.193s (userspace) + kde = 45.421s
System
Mobo: ASRock, model: A780GM-LE Bios: American Megatrends version: P1.10 date: 02/13/2009
AMD Phenom II X4 940, KDE 4.11.00, openSUSE 13.1 Milestone 4 (x86_64)
both kernels are on, Drive2: USB /dev/sdb 00BEVT 160.0GB,
Partitions,
ID: / size: 50GB used: 9.2G (20%) fs: ext4
ID: /home size: 96GB used: 48G (50%) fs: ext4
ID: swap-1 size: 2.15GB used: 0.00GB (0%) fs: swap
ID: swap-2 size: 2.15GB used: 0.00GB (0%) fs: swap
no anomalies noticed so far,
kde, wired network, firefox, libreoffice, googleearth, all ok
any comments wrt make warning, would be appreciated
On 08/21/2013 10:46 AM, keellambert wrote:
>
> FWIW
>
> Updated to latest kernel today,
>
> make warning posted at URL: ‘SUSE Paste’
> (http://paste.opensuse.org/68109454)
–snip–
> any comments wrt make warning, would be appreciated
Ignore them. I doubt that you are actually using any of those drivers. Each new
version of gcc reports new warnings and it takes a while for the patches that
remove them to filter through the system.
Let me say that my boot times were faster with rc6 than the original kernel 3.11-rc1, but I do use a SSD boot disk (not /home) and it always makes for fast boot time of course. Basically I do not think the new kernel is getting slower. I do think we are constantly getting more drivers, building the potential size of the kernel, depending on how your kernel is configured, but speed is very good in my opinion.
On 08/21/2013 05:56 PM, jdmcdaniel3 wrote:
>
> Let me say that my boot times were faster with rc6 than the original
> kernel 3.11-rc1, but I do use a SSD boot disk (not /home) and it always
> makes for fast boot time of course. Basically I do not think the new
> kernel is getting slower. I do think we are constantly getting more
> drivers, building the potential size of the kernel, depending on how
> your kernel is configured, but speed is very good in my opinion.
As long as drivers are built as modules, the main effect of adding new drivers
is mostly due to the kernel growing a little with each module in the table. By
trimming your configuration to utilize only the drivers you need, you can
overcome that effect in the initial loading of the kernel. A much larger effect
will be the reduction in kernel build times.
Once the kernel is loaded and the devices all found, the kernel has little to do
with the boot process. On my laptop with a conventional HDD and a 2.0 GHz dual
CPU, that takes a little over 4 seconds. Everything else that happens after that
is controlled by user space. On my machine that takes about 45 additional
seconds. As a result, I can see boot times changing more with a change in
openSUSE version, or when things in user space like udevd are changed. I would
not, however, expect much difference from kernel to kernel.
When I am debugging a new driver, I get lots of crashes and need a lot of
reboots. Boot time is a consideration; however, it is the file-system recoveries
that are slow. My non-testing systems tend to run for several weeks between
reboots. On those, it makes little difference how long a reboot takes.
Great information Larry and good insight as always. I am loving the newest kernel and except on one test machine, sticking with the open source nVIDIA driver and it is working for everything I use.
Now I know this is the openSUSE forums, but do you have any insights a person such as yourself working with the kernel as they might have on compiling a new Linux kernel on a RaspBerry Pi and/or loading openSUSE arm on the same device? I have interest in making a connection here as I have one model B running at home, they are cheep enough, but things are not so simple there with the Paspbian Wheezy OS I am using. Any help would be appreciated if you had the time.
On 08/21/2013 08:46 PM, jdmcdaniel3 wrote:
> Now I know this is the openSUSE forums, but do you have any insights a
> person such as yourself working with the kernel as they might have on
> compiling a new Linux kernel on a RaspBerry Pi and/or loading openSUSE
> arm on the same device? I have interest in making a connection here as
> I have one model B running at home, they are cheep enough, but things
> are not so simple there with the Paspbian Wheezy OS I am using. Any
> help would be appreciated if you had the time.
I also have a model B that was using Rasbian and I have built a kernel on it so
that I could test the driver for a TP-Link TL-WN725N. The various “tutorials” on
how to set up a cross-compiler were difficult to follow, and/or filled with
outright errors. As I did not have much time, I decided to build the kernel on
the Pi. As I only have a 4 GB SD card, I placed the kernel sources on an
NFS-mounted volume. The build took a long time, but was successful.
I am now testing openSUSE on the Pi as I also prefer it to Debian. I did the
following steps:
Decompress it with ‘gunzip raspberrypi-opensuse-20130407.img.gz’
Place the SD card in your slot. Note the device name in the dmesg output.
Copy it to an SD card with ‘sudo dd if=raspberrypi-opensuse-20130407.img
of=/dev/mmcblk0’. Modify the output file to match what dmesg showed in step 3.
The above got me an SD card that would boot and I could log in as shown on http://en.opensuse.org/HCL:Raspberry_Pi, but I do not seem to be able to get
zypper to add any extra necessary packages as the repo it is addressing does not
seem to be present.