Prev: removing emacs
Next: No sda/sdb devices after halfway through boot
From: Andy on 5 Mar 2010 18:39
Martin wrote:

> On 03/05/2010 11:22 PM, Andy wrote:
>> Martin wrote:
>>
>>> On 03/05/2010 11:00 PM, Andy wrote:
>>>> Martin wrote:
>>>>
>>>>> It seems that the recent updates broke my binary nvidia driver.
>>>>> The kernel and glibc is blacklisted so the slackpkg did not upgrade
>>>>> them. I'm still on 2.6.32.7
>>>>> I did not switch off my computer for a few days. Today I did it and
>>>>> bump - can't startx
>>>>> I got the latest nvidia binary driver from their website. It seems to
>>>>> install fine, but when I startx:
>>>>>
>>>>> Warning: Error inserting agpgart
>>>>> (/lib/modules/2.6.32.7/kernel/drivers/char/agp/agpgart.ko): Invalid
>>>>> module format
>>>>> Fatal: Error inserting nvidia
>>>>> (lib/modules/2.6.32.7/kernel/drivers/video/nvidia.ko): invalid module
>>>>> format EE nvidia: failed to load the nvidia kernel module.
>>>>> Failed to load module 'nvidia' (module-specific error, 0)
>>>>> No drivers available
>>>>> Fatal server error:
>>>>> no screens found
>>>>>
>>>>>
>>>>> How could I solve it?
>>>>>
>>>>> thank you
>>>>> Martin
>>>>
>>>> I had the same problem. As stupid as this sounds, try insmod. Worked
>>>> for
>>>> me. Something in the latest module-init-tools seems to be broken.
>>>>
>>>> Andy
>>> Thanks Andy
>>>
>>> insmod nvidia
>>> insmod: can't read 'nvidia': no such file or directory
>>>
>>>
>>> modprobe nvidia gives me the warning and fatal error from the original
>>> error message I posted.
>>
>> Try insmod /lib/modules/2.6.33/kernel/drivers/video/nvidia.ko
>>
>> Andy
>>
> Brilliant!!! It works. Thanks
> Where would I add it for it to be issued every time I restart the
> computer?

I'm going to put mine in rc.local until the real fix comes out.

Andy

From: Andy on 5 Mar 2010 19:10
Martin wrote:

> On 03/05/2010 11:22 PM, Andy wrote:
>> Martin wrote:
>>
>>> On 03/05/2010 11:00 PM, Andy wrote:
>>>> Martin wrote:
>>>>
>>>>> It seems that the recent updates broke my binary nvidia driver.
>>>>> The kernel and glibc is blacklisted so the slackpkg did not upgrade
>>>>> them. I'm still on 2.6.32.7
>>>>> I did not switch off my computer for a few days. Today I did it and
>>>>> bump - can't startx
>>>>> I got the latest nvidia binary driver from their website. It seems to
>>>>> install fine, but when I startx:
>>>>>
>>>>> Warning: Error inserting agpgart
>>>>> (/lib/modules/2.6.32.7/kernel/drivers/char/agp/agpgart.ko): Invalid
>>>>> module format
>>>>> Fatal: Error inserting nvidia
>>>>> (lib/modules/2.6.32.7/kernel/drivers/video/nvidia.ko): invalid module
>>>>> format EE nvidia: failed to load the nvidia kernel module.
>>>>> Failed to load module 'nvidia' (module-specific error, 0)
>>>>> No drivers available
>>>>> Fatal server error:
>>>>> no screens found
>>>>>
>>>>>
>>>>> How could I solve it?
>>>>>
>>>>> thank you
>>>>> Martin
>>>>
>>>> I had the same problem. As stupid as this sounds, try insmod. Worked
>>>> for
>>>> me. Something in the latest module-init-tools seems to be broken.
>>>>
>>>> Andy
>>> Thanks Andy
>>>
>>> insmod nvidia
>>> insmod: can't read 'nvidia': no such file or directory
>>>
>>>
>>> modprobe nvidia gives me the warning and fatal error from the original
>>> error message I posted.
>>
>> Try insmod /lib/modules/2.6.33/kernel/drivers/video/nvidia.ko
>>
>> Andy
>>
> Brilliant!!! It works. Thanks
> Where would I add it for it to be issued every time I restart the
> computer?

I've discovered that downgrading udev-151 to udev-141 fixes this problem as
well as the other problem I had with booting using an initrd.

Andy
From: Martin on 5 Mar 2010 19:47
On 03/06/2010 12:10 AM, Andy wrote:
> Martin wrote:
>
>> On 03/05/2010 11:22 PM, Andy wrote:
>>> Martin wrote:
>>>
>>>> On 03/05/2010 11:00 PM, Andy wrote:
>>>>> Martin wrote:
>>>>>
>>>>>> It seems that the recent updates broke my binary nvidia driver.
>>>>>> The kernel and glibc is blacklisted so the slackpkg did not upgrade
>>>>>> them. I'm still on 2.6.32.7
>>>>>> I did not switch off my computer for a few days. Today I did it and
>>>>>> bump - can't startx
>>>>>> I got the latest nvidia binary driver from their website. It seems to
>>>>>> install fine, but when I startx:
>>>>>>
>>>>>> Warning: Error inserting agpgart
>>>>>> (/lib/modules/2.6.32.7/kernel/drivers/char/agp/agpgart.ko): Invalid
>>>>>> module format
>>>>>> Fatal: Error inserting nvidia
>>>>>> (lib/modules/2.6.32.7/kernel/drivers/video/nvidia.ko): invalid module
>>>>>> format EE nvidia: failed to load the nvidia kernel module.
>>>>>> Failed to load module 'nvidia' (module-specific error, 0)
>>>>>> No drivers available
>>>>>> Fatal server error:
>>>>>> no screens found
>>>>>>
>>>>>>
>>>>>> How could I solve it?
>>>>>>
>>>>>> thank you
>>>>>> Martin
>>>>>
>>>>> I had the same problem. As stupid as this sounds, try insmod. Worked
>>>>> for
>>>>> me. Something in the latest module-init-tools seems to be broken.
>>>>>
>>>>> Andy
>>>> Thanks Andy
>>>>
>>>> insmod nvidia
>>>> insmod: can't read 'nvidia': no such file or directory
>>>>
>>>>
>>>> modprobe nvidia gives me the warning and fatal error from the original
>>>> error message I posted.
>>>
>>> Try insmod /lib/modules/2.6.33/kernel/drivers/video/nvidia.ko
>>>
>>> Andy
>>>
>> Brilliant!!! It works. Thanks
>> Where would I add it for it to be issued every time I restart the
>> computer?
>
> I've discovered that downgrading udev-151 to udev-141 fixes this problem as
> well as the other problem I had with booting using an initrd.
>
> Andy

I think I'll wait until there's a fix for module-init-tools

Out of curiosity, how did you find out that it's udev?
Obviously, you didn't try to downgrade most of the packages just to see
which one is responsible for that bug, did you?:)


--
regards

Martin
From: Andy on 5 Mar 2010 21:37
Martin wrote:

> On 03/06/2010 12:10 AM, Andy wrote:
>> Martin wrote:
>>
>>> On 03/05/2010 11:22 PM, Andy wrote:
>>>> Martin wrote:
>>>>
>>>>> On 03/05/2010 11:00 PM, Andy wrote:
>>>>>> Martin wrote:
>>>>>>
>>>>>>> It seems that the recent updates broke my binary nvidia driver.
>>>>>>> The kernel and glibc is blacklisted so the slackpkg did not upgrade
>>>>>>> them. I'm still on 2.6.32.7
>>>>>>> I did not switch off my computer for a few days. Today I did it and
>>>>>>> bump - can't startx
>>>>>>> I got the latest nvidia binary driver from their website. It seems
>>>>>>> to install fine, but when I startx:
>>>>>>>
>>>>>>> Warning: Error inserting agpgart
>>>>>>> (/lib/modules/2.6.32.7/kernel/drivers/char/agp/agpgart.ko): Invalid
>>>>>>> module format
>>>>>>> Fatal: Error inserting nvidia
>>>>>>> (lib/modules/2.6.32.7/kernel/drivers/video/nvidia.ko): invalid
>>>>>>> module format EE nvidia: failed to load the nvidia kernel module.
>>>>>>> Failed to load module 'nvidia' (module-specific error, 0)
>>>>>>> No drivers available
>>>>>>> Fatal server error:
>>>>>>> no screens found
>>>>>>>
>>>>>>>
>>>>>>> How could I solve it?
>>>>>>>
>>>>>>> thank you
>>>>>>> Martin
>>>>>>
>>>>>> I had the same problem. As stupid as this sounds, try insmod.
>>>>>> Worked for
>>>>>> me. Something in the latest module-init-tools seems to be broken.
>>>>>>
>>>>>> Andy
>>>>> Thanks Andy
>>>>>
>>>>> insmod nvidia
>>>>> insmod: can't read 'nvidia': no such file or directory
>>>>>
>>>>>
>>>>> modprobe nvidia gives me the warning and fatal error from the original
>>>>> error message I posted.
>>>>
>>>> Try insmod /lib/modules/2.6.33/kernel/drivers/video/nvidia.ko
>>>>
>>>> Andy
>>>>
>>> Brilliant!!! It works. Thanks
>>> Where would I add it for it to be issued every time I restart the
>>> computer?
>>
>> I've discovered that downgrading udev-151 to udev-141 fixes this problem
>> as well as the other problem I had with booting using an initrd.
>>
>> Andy
>
> I think I'll wait until there's a fix for module-init-tools
>
> Out of curiosity, how did you find out that it's udev?
> Obviously, you didn't try to downgrade most of the packages just to see
> which one is responsible for that bug, did you?:)

I had another problem I listed in different thread. Trying the udev fix for
that problem had the bonus of fixing this one too. It was the first and
only package I downgraded. I don't know how udev and module-init-tools are
related. I wasted a lot of time on this already today, so I'm not inclined
to do any more experimenting to try and find out. It might not be the ideal
fix, but it does solve the problem without needing to modify rc.local to
load the driver.

Andy
From: Michael Black on 5 Mar 2010 22:12
On Fri, 5 Mar 2010, Andy wrote:


>> Brilliant!!! It works. Thanks
>> Where would I add it for it to be issued every time I restart the
>> computer?
>
> I'm going to put mine in rc.local until the real fix comes out.
>
Have you notified Slackware that there's a problem? This is the time they
want to know about such things, not when the next release is imminent or
out of the gate.

Michael

First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: removing emacs
Next: No sda/sdb devices after halfway through boot