nVidia 1.6111 (x86) and Kernel 2.6.9 - X

This is a discussion on nVidia 1.6111 (x86) and Kernel 2.6.9 - X ; Haven't seen any posts here about trouble with the new kernel and nVidia driver, but I guess people will soon start posting about problems (did myself first today upgrade my kernel to 2.6.9) Here is a good link, with a ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: nVidia 1.6111 (x86) and Kernel 2.6.9

  1. nVidia 1.6111 (x86) and Kernel 2.6.9

    Haven't seen any posts here about trouble with the new kernel and nVidia
    driver, but I guess people will soon start posting about problems (did myself
    first today upgrade my kernel to 2.6.9)

    Here is a good link, with a solution untill nVidia releases a new driver:
    http://ngc891.blogdns.net/index.php?...9/19-linux-269


    //Aho

  2. Re: nVidia 1.6111 (x86) and Kernel 2.6.9

    J.O. Aho wrote:
    > Haven't seen any posts here about trouble with the new kernel and nVidia
    > driver, but I guess people will soon start posting about problems (did
    > myself first today upgrade my kernel to 2.6.9)
    >
    > Here is a good link, with a solution untill nVidia releases a new driver:
    > http://ngc891.blogdns.net/index.php?...9/19-linux-269
    >
    >
    > //Aho

    there was no need for the post. as soon as i had the problem i got the
    answer by googling which i always do before posting. but the good thing
    is that patch worked like a magic.
    but i'm having some other problem which is not related to x,
    my syslog is flooded with this following messages, after i upgraded to 2.6.9

    drivers/usb/input/hid-core.c: input irq status -84 received

    i even posted this a week back, but didn't get any response
    just wondering
    jc

  3. Re: nVidia 1.6111 (x86) and Kernel 2.6.9

    > there was no need for the post. as soon as i had the problem i got the
    > answer by googling which i always do before posting. but the good thing
    > is that patch worked like a magic.
    > but i'm having some other problem which is not related to x,
    > my syslog is flooded with this following messages, after i upgraded to
    > 2.6.9
    >
    > drivers/usb/input/hid-core.c: input irq status -84 received
    >
    > i even posted this a week back, but didn't get any response
    > just wondering


    I've booted my machine last night with 2.6.9 + con kolivas patches , and
    found strange things at usb site also.
    Using fc2, my mobo is gigabyte with Intel 875 chipset and sata controller
    uses piix sata driver.
    usb-stick - usb 1.1
    Example : usb-stick plugged in. Seems that everything is ok, /mnt/flash
    created , I can mount stick w/o problems.Umount /mnt/flash .. passed ok.
    Now: Plug same stick again ... hej....there's no /mnt/flash ...hm... ok...I
    can mount it regulary, but 2.6.8-1 works ok with this. Umount / Plug-Off
    Now I've plugged-in another usb-stick (2.0).
    /var/log/messages says that everything is ok, udev created
    devices /udev/sdc1 etc... I cannot mount stick !, replug stick again...****
    no respond from usb..it's dead...

    Another machine w/o sata controller , kernel 2.6.8-1 works like a charm with
    those different usb-sticks and I can plug them in-out thousand times w/o
    problem.

    this is some kernel output from 2.6.9-ck2-smp (preempt is off) , when
    preempt is on it's painfull (ooops).

    Nov 1 22:43:15 houston kernel: usb 3-1: new full speed USB device using
    address 3
    Nov 1 22:43:15 houston kernel: usb 3-1: Product: USB FLASH DISK
    Nov 1 22:43:15 houston kernel: usb 3-1: Manufacturer: 3SYSTEM
    Nov 1 22:43:15 houston kernel: scsi2 : SCSI emulation for USB Mass Storage
    devices
    Nov 1 22:43:15 houston kernel: Vendor: 3SYSTEM Model: USB FLASH DISK
    Rev: 1.00
    Nov 1 22:43:15 houston kernel: Type: Direct-Access
    ANSI SCSI revision: 02
    Nov 1 22:43:15 houston kernel: SCSI device sdc: 511744 512-byte hdwr
    sectors (262 MB)
    Nov 1 22:43:15 houston kernel: sdc: Write Protect is off
    Nov 1 22:43:15 houston kernel: sdc: assuming drive cache: write through
    Nov 1 22:43:15 houston kernel: sdc:<7>usb-storage: queuecommand called
    Nov 1 22:43:15 houston kernel: sdc1
    Nov 1 22:43:15 houston kernel: Attached scsi removable disk sdc at scsi2,
    channel 0, id 0, lun 0
    Nov 1 22:43:15 houston kernel: Attached scsi generic sg2 at scsi2, channel
    0, id 0, lun 0, type 0
    Nov 1 22:43:16 houston scsi.agent[3647]: disk
    at /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/host2/2:0:0:0
    Nov 1 22:43:17 houston udev[3708]: creating device node '/udev/sg2'
    Nov 1 22:43:17 houston udev[3706]: creating device node '/udev/sdc1'
    Nov 1 22:43:17 houston udev[3705]: creating device node '/udev/sdc'
    Nov 1 22:44:28 houston kernel: usb 3-1: USB disconnect, address 3
    Nov 1 22:44:28 houston udev[3739]: removing device node '/udev/sg2'
    Nov 1 22:44:28 houston udev[3761]: removing device node '/udev/sdc1'
    Nov 1 22:44:28 houston udev[3764]: removing device node '/udev/sdc'
    Nov 1 22:44:38 houston kernel: usb 1-3: new high speed USB device using
    address 5
    Nov 1 22:44:38 houston kernel: usb 1-3: Product: Mass storage
    Nov 1 22:44:38 houston kernel: usb 1-3: Manufacturer: USB
    Nov 1 22:44:38 houston kernel: usb 1-3: SerialNumber: 142E194149844E7C
    Nov 1 22:44:39 houston kernel: scsi3 : SCSI emulation for USB Mass Storage
    devices
    Nov 1 22:44:39 houston kernel: Vendor: 256MB Model: USB2.0FlashDrive
    Rev: 2.00
    Nov 1 22:44:39 houston kernel: Type: Direct-Access
    ANSI SCSI revision: 02
    Nov 1 22:44:39 houston kernel: sdc: Unit Not Ready, sense:
    Nov 1 22:44:39 houston kernel: Current : sense key Unit Attention
    Nov 1 22:44:39 houston kernel: Additional sense: Not ready to ready change,
    medium may have changed
    Nov 1 22:44:39 houston kernel: sdc : READ CAPACITY failed.
    Nov 1 22:44:39 houston kernel: sdc : status=1, message=00, host=0,
    driver=08
    Nov 1 22:44:39 houston kernel: Current sd: sense key Unit Attention
    Nov 1 22:44:39 houston kernel: Additional sense: Not ready to ready change,
    medium may have changed
    Nov 1 22:44:39 houston kernel: sdc: Write Protect is off
    Nov 1 22:44:39 houston kernel: sdc: assuming drive cache: write through
    Nov 1 22:44:39 houston kernel: sdc:<7>usb-storage: queuecommand called
    Nov 1 22:44:49 houston scsi.agent[3853]: Attribute
    /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host3/3:0:0:0/type
    does not exist
    Nov 1 22:44:49 houston udev[3877]: creating device node '/udev/sdc'
    Nov 1 22:45:03 houston kernel: SCSI error : <3 0 0 0> return code = 0x70000
    Nov 1 22:45:03 houston kernel: end_request: I/O error, dev sdc, sector
    2097144
    Nov 1 22:45:03 houston kernel: Buffer I/O error on device sdc, logical
    block 262143
    Nov 1 22:45:03 houston kernel: eping.
    Nov 1 22:45:03 houston kernel: sdc : READ CAPACITY failed.
    Nov 1 22:45:03 houston kernel: sdc : status=0, message=00, host=7,
    driver=00
    Nov 1 22:45:03 houston kernel: sdc : sense not available.
    Nov 1 22:45:03 houston kernel: sdc: Write Protect is off
    Nov 1 22:45:03 houston kernel: sdc: assuming drive cache: write through
    Nov 1 22:45:03 houston kernel: sdc : READ CAPACITY failed.
    Nov 1 22:45:03 houston kernel: sdc : status=0, message=00, host=7,
    driver=00
    Nov 1 22:45:03 houston kernel: sdc : sense not available.
    Nov 1 22:45:03 houston kernel: sdc: Write Protect is off
    Nov 1 22:45:03 houston kernel: sdc: assuming drive cache: write through
    Nov 1 22:45:03 houston kernel: sdc:<3>Buffer I/O error on device sdc,
    logical block 0
    Nov 1 22:45:03 houston kernel: Buffer I/O error on device sdc, logical
    block 0
    Nov 1 22:45:03 houston kernel: Buffer I/O error on device sdc, logical
    block 262143
    Nov 1 22:45:03 houston kernel: Buffer I/O error on device sdc, logical
    block 262143
    Nov 1 22:45:03 houston kernel: Buffer I/O error on device sdc, logical
    block 0
    Nov 1 22:45:03 houston kernel: ldm_validate_partition_table(): Disk read
    failed.
    Nov 1 22:45:03 houston kernel: Buffer I/O error on device sdc, logical
    block 0
    Nov 1 22:45:03 houston kernel: unable to read partition table
    Nov 1 22:45:03 houston kernel: usb 1-3: USB disconnect, address 5
    Nov 1 22:48:03 houston syslogd 1.4.1: restart.

    Here I have to restart since I cannot use USB anymore (it's dead).






  4. Re: nVidia 1.6111 (x86) and Kernel 2.6.9

    jayachandran kamaraj wrote:
    > J.O. Aho wrote:
    >
    >> Haven't seen any posts here about trouble with the new kernel and
    >> nVidia driver, but I guess people will soon start posting about
    >> problems (did myself first today upgrade my kernel to 2.6.9)
    >>
    >> Here is a good link, with a solution untill nVidia releases a new driver:
    >> http://ngc891.blogdns.net/index.php?...9/19-linux-269


    > there was no need for the post. as soon as i had the problem i got the
    > answer by googling which i always do before posting. but the good thing
    > is that patch worked like a magic.


    You never know, not everyone has discovered google yet.


    > my syslog is flooded with this following messages, after i upgraded to
    > 2.6.9
    >
    > drivers/usb/input/hid-core.c: input irq status -84 received
    >
    > i even posted this a week back, but didn't get any response


    Nothing like that, but then I don't have compile support for USB
    mouse/keyboard, as I don't have such. Could be that the device you have
    connected isn't really following the standards (in the linux point of view),
    or in the worst case it could be that the usb on the mainboard is breaking down.


    //Aho

  5. Re: nVidia 1.6111 (x86) and Kernel 2.6.9

    > Here I have to restart since I cannot use USB anymore (it's dead).

    fixed ... I was stupid, now everything works like a charm , no problems with
    nvidia,usb etc.... I've setted up HZ_100 instead of HZ_1000 , now with
    HZ_1000 works like a rocket

+ Reply to Thread