Announcement

Collapse
No announcement yet.

Using the mainline 3.9 kernel

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Using the mainline 3.9 kernel

    Is anyone using the mainline 3.9 kernel in 13.10? Yes, it isn't available 'normally', but it can be downloaded from The Linux Kernel Archives. What are the risks (if any) of using it?
    Using Kubuntu Linux since March 23, 2007
    "It is a capital mistake to theorize before one has data." - Sherlock Holmes

    #2
    dose not 13.10 use the 3.9 kernel anyway ?
    http://kernel.ubuntu.com/~kernel-ppa/mainline/

    VINNY
    i7 4core HT 8MB L3 2.9GHz
    16GB RAM
    Nvidia GTX 860M 4GB RAM 1152 cuda cores

    Comment


      #3
      Dang! Hate when I post both in the wrong place and with the wrong version in my question!
      I've moved the thread to here.

      Okay, what I meant was, "in 13.04".
      Using Kubuntu Linux since March 23, 2007
      "It is a capital mistake to theorize before one has data." - Sherlock Holmes

      Comment


        #4
        'Fintan' asked (& answers): Kubuntu Discussion > Kubuntu 13.04 Raring Ringtail > Post-installation > kernel 3.9 and sound > http://www.kubuntuforums.net/showthr...-3-9-and-sound
        Before you edit, BACKUP !

        Why there are dead links ?
        1. Thread: Please explain how to access old kubuntu forum posts
        2. Thread: Lost Information

        Comment


          #5
          Im using it to solve a nvidia issue. No problem at all so far.

          Comment


            #6
            Yes I'm running 3.9.0-030900-generic on Kubuntu 13.04. It solved many boot-and nvidia-problems I had with the worst kernel in my linux life: 3.8.0-19 generic.
            Hardware:
            Gigabyte GA-970A-DS3 / F 6200 CPU / 16 Gigs DDR 3 pc-10000 / NVidia GT 640 (driver: nvidia-304.88). Knock on wood.

            Comment


              #7
              Starting with an upgraded 12.04.x yesterday, I upgraded to KDE 4.10.3. I then upgraded to kernel 3.9.030900-generic. Only issue was with VirtualBox. Now running VB 4.2.12.x without problems.
              GigaByte GA-965G-DS3, Core2Duo at 2.1 GHz, 4 GB RAM, ASUS DRW-24B1ST, LiteOn iHAS 324 A, NVIDIA 7300 GS, 500 GB and 80 GB WD HDD

              Comment


                #8
                Originally posted by anamnesis View Post
                Yes I'm running 3.9.0-030900-generic on Kubuntu 13.04. It solved many boot-and nvidia-problems I had with the worst kernel in my linux life: 3.8.0-19 generic.
                Hardware:
                Gigabyte GA-970A-DS3 / F 6200 CPU / 16 Gigs DDR 3 pc-10000 / NVidia GT 640 (driver: nvidia-304.88). Knock on wood.
                Update:

                3.9.2 on Kubuntu 13.04 -> no any probs
                3.9.1-2 (comes with it) on Kubuntu 13.10 nightly -> no probs so far, nvidia 304-88 compiled fine.

                Couldn't get my wintv aero usb stick to work yet. I copied the same hauppauge firmware to /lib/firmware, but:

                $ dmesg | grep usb*
                usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
                [ 1273.648069] usb 1-5: Product: WinTV Aero-T
                [ 1273.648073] usb 1-5: Manufacturer: Hauppauge Computer Works
                [ 1273.648076] usb 1-5: SerialNumber: 4034221818
                [ 1288.665595] smsusb_init_device: line: 382: smscore_start_device(...) failed
                [ 1288.665779] smsusb_onresponse: line: 118: error, urb status -2, 0 bytes
                [ 1288.666029] smsusb_onresponse: line: 118: error, urb status -2, 0 bytes
                [ 1288.666275] smsusb_onresponse: line: 118: error, urb status -2, 0 bytes
                [ 1288.666525] smsusb_onresponse: line: 118: error, urb status -2, 0 bytes
                [ 1288.666776] smsusb_onresponse: line: 118: error, urb status -2, 0 bytes
                [ 1288.667027] smsusb_onresponse: line: 118: error, urb status -2, 0 bytes
                [ 1288.667276] smsusb_onresponse: line: 118: error, urb status -2, 0 bytes
                [ 1288.667525] smsusb_onresponse: line: 118: error, urb status -2, 0 bytes
                [ 1288.667777] smsusb_onresponse: line: 118: error, urb status -2, 0 bytes
                [ 1288.668028] smsusb_onresponse: line: 118: error, urb status -2, 0 bytes
                [ 1288.670755] smsusb: probe of 1-5:1.0 failed with error -62

                So, the stick cannot be initialised for some reason. The stick worked okay in previous Mint/Kubuntu versions. Of course, I can't rule out, that the stick got faulty.

                Comment

                Working...
                X