Prev: recent updates broke the nvidia binary driver?! (64-current)
Next: Live CD/DVD for SlackWare?
From: Stuart Winter on 6 Mar 2010 05:05
On Sat, 06 Mar 2010 05:30:45 +0000, newsgroups(a)rlworkman.net wrote:

> On 2010-03-06, Andy <andy(a)asjohnson.com> wrote:
>>> I "upgraded" (debatable) to -current today, and the default huge kernel
>>> boots OK. However, my custom 2.6.33 kernel which was working yesterday
>>> with (not-so) -current from December, boots about half way to the
[..]

Look in the other thread about 2.6.33.
Check /usr/doc/udev-151/README
Make sure your kernel config meets the requirements.

--
Stuart Winter
www.slackware.com/~mozes
Slackware for ARM: www.armedslack.org
From: Andy on 6 Mar 2010 10:35
Stuart Winter wrote:

> On Sat, 06 Mar 2010 05:30:45 +0000, newsgroups(a)rlworkman.net wrote:
>
>> On 2010-03-06, Andy <andy(a)asjohnson.com> wrote:
>>>> I "upgraded" (debatable) to -current today, and the default huge kernel
>>>> boots OK. However, my custom 2.6.33 kernel which was working yesterday
>>>> with (not-so) -current from December, boots about half way to the
> [..]
>
> Look in the other thread about 2.6.33.
> Check /usr/doc/udev-151/README
> Make sure your kernel config meets the requirements.

It was CONFIG_SYSFS_DEPRECATED that was getting me.

Andy

From: A Guy Called Tyketto on 6 Mar 2010 13:41
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stuart Winter <not.a.real.address(a)interlude.org.uk> wrote:
> On Sat, 06 Mar 2010 05:30:45 +0000, newsgroups(a)rlworkman.net wrote:
>
>> On 2010-03-06, Andy <andy(a)asjohnson.com> wrote:
>>>> I "upgraded" (debatable) to -current today, and the default huge kernel
>>>> boots OK. However, my custom 2.6.33 kernel which was working yesterday
>>>> with (not-so) -current from December, boots about half way to the
> [..]
>
> Look in the other thread about 2.6.33.
> Check /usr/doc/udev-151/README
> Make sure your kernel config meets the requirements.

Thanks for this. This was what I was alluding to in the other
thread. udev-141 must have been broken, because it also requires
CONFIG_SYSFS_DEPRECATED* to not be set, yet it is set on my custom 2.6.32.9
kernel, and it boots. udev-151 also requires CONFIG_SYSFS_DEPRECATED*
to not be set, and it doesn't boot.

When 2.6.33.1 becomes available, I'll give udev an upgrade and
see what I get.

BL.
- --
Brad Littlejohn | Email: tyketto(a)sbcglobal.net
Unix Systems Administrator, | tyketto(a)ozemail.com.au
Web + NewsMaster, BOFH.. Smeghead! :) | http://www.wizard.com/~tyketto
PGP: 1024D/E319F0BF 6980 AAD6 7329 E9E6 D569 F620 C819 199A E319 F0BF

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFLkqHOyBkZmuMZ8L8RAmZBAKCsGZ7/sdP1aG1ue1Gml+yRSAupdgCgj6+o
e3wW8fol4vR2F2g/+eeVtuQ=
=9gdj
-----END PGP SIGNATURE-----
From: Robby Workman on 7 Mar 2010 02:37
On 2010-03-06, A Guy Called Tyketto <tyketto(a)sbcglobal.net.invalid> wrote:
>
> Stuart Winter <not.a.real.address(a)interlude.org.uk> wrote:
>> On Sat, 06 Mar 2010 05:30:45 +0000, newsgroups(a)rlworkman.net wrote:
>>
>>> On 2010-03-06, Andy <andy(a)asjohnson.com> wrote:
>>>>> I "upgraded" (debatable) to -current today, and the default huge kernel
>>>>> boots OK. However, my custom 2.6.33 kernel which was working yesterday
>>>>> with (not-so) -current from December, boots about half way to the
>> [..]
>>
>> Look in the other thread about 2.6.33.
>> Check /usr/doc/udev-151/README
>> Make sure your kernel config meets the requirements.
>
> Thanks for this. This was what I was alluding to in the other
> thread. udev-141 must have been broken, because it also requires
> CONFIG_SYSFS_DEPRECATED* to not be set, yet it is set on my custom 2.6.32.9
> kernel, and it boots. udev-151 also requires CONFIG_SYSFS_DEPRECATED*
> to not be set, and it doesn't boot.


From memory, when the udev maintainers have been asked something along
the lines of "Exactly what breaks when CONFIG_SYSFS_DEPRECATED is on?"
the response has been something to the effect of "Various things break
in strange ways." Apparently that's exactly what happens; sometimes the
breakage is so strange that it's unbreakage. :-)

-RW
From: kevin on 8 Mar 2010 19:30

I had the same issue, the fix for me was to go into my custom kernel
and turn on the /dev tmpfs and then everything booted fine. It's
located here:

Device Drivers ->
Generic Driver Options ->
Create a kernel maintained /dev tmpfs (EXPERIMENTAL)
Automount devtmpfs at /dev

That was the only change I made and the system boots fine now. Didn't
have to downgrade udev at all.
 |  Next  |  Last
Pages: 1 2
Prev: recent updates broke the nvidia binary driver?! (64-current)
Next: Live CD/DVD for SlackWare?