Prev: 64 bit question
Next: removing emacs
From: Randy on 4 Mar 2010 18:03 Anyone else having problems with the new udev 151-1 in the latest updates in Slack32. System did not boot and had to downgrade to to 141-3 from Slack32 13.0.
From: A Guy Called Tyketto on 5 Mar 2010 02:11 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Randy <zaphod812(a)yahoo.com> wrote: > Anyone else having problems with the new udev 151-1 in the latest updates > in Slack32. System did not boot and had to downgrade to to 141-3 from > Slack32 13.0. I'm having something similar, but thought it was attributed to the coreutils/libgmp issue that Robby mentioned. It took me dropping back to the latest stock kernel from -current to get my box working. I'll drop back to 141-3 from Slackware64 and see if it works as well. 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) iD8DBQFLkK6tyBkZmuMZ8L8RAiBDAKCEw96MBxGbhVd7JN9BPZpClfrqBwCg9eBU VosM7VDf4DnTK3j2HyQ2yY8= =sIPX -----END PGP SIGNATURE-----
From: A Guy Called Tyketto on 5 Mar 2010 03:11 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Randy <zaphod812(a)yahoo.com> wrote: > Anyone else having problems with the new udev 151-1 in the latest updates > in Slack32. System did not boot and had to downgrade to to 141-3 from > Slack32 13.0. Confirmed. Slackware64-current for me. Robby, if you're reading this, run this back up the flagpole to PV so he at least has some insight. udev-151 is somewhat broken, at least for me on 64-current. Booting to it into an initrd-based kernel with sata and pata support built into the initrd drops you to the maintenance prompt saying that /dev/sda1 isn't available. Logging in shows that /dev/sd* is missing completely. booting to the stock 2.6.33 kernel works fine. Reverting back to udev-141 works, so something is definitely up with udev-151. 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) iD8DBQFLkLyXyBkZmuMZ8L8RAj5ZAJ9VXSs0Q049yTmQuSOp4FtgfQKbywCff5h4 Kmu8mDtQpZYsR+nXlPUFrdw= =CUU3 -----END PGP SIGNATURE-----
From: Randy on 5 Mar 2010 03:26 A Guy Called Tyketto wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Randy <zaphod812(a)yahoo.com> wrote: >> Anyone else having problems with the new udev 151-1 in the latest updates >> in Slack32. System did not boot and had to downgrade to to 141-3 from >> Slack32 13.0. > > I'm having something similar, but thought it was attributed to > the coreutils/libgmp issue that Robby mentioned. It took me dropping > back to the latest stock kernel from -current to get my box working. > I'll drop back to 141-3 from Slackware64 and see if it works as well. > > BL. > - -- > Brad Littlejohn | Email: tyketto(a)sbcglobal.net Thanks Brad, Guess I should have mentioned that I compiled everything I use in to my kernel (2.6.31.6) I don't suppose Pat reads this board anymore, think he may have years ago. I'll consider this as bug report filed. Randy
From: Loki Harfagr on 5 Mar 2010 05:59
Fri, 05 Mar 2010 08:11:05 +0000, A Guy Called Tyketto did cat : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Randy <zaphod812(a)yahoo.com> wrote: >> Anyone else having problems with the new udev 151-1 in the latest >> updates in Slack32. System did not boot and had to downgrade to to >> 141-3 from Slack32 13.0. > > Confirmed. Slackware64-current for me. > > Robby, if you're reading this, run this back up the flagpole to > PV so he at least has some insight. udev-151 is somewhat broken, at > least for me on 64-current. Booting to it into an initrd-based kernel > with sata and pata support built into the initrd drops you to the > maintenance prompt saying that /dev/sda1 isn't available. Logging in > shows that /dev/sd* is missing completely. booting to the stock 2.6.33 > kernel works fine. Reverting back to udev-141 works, so something is > definitely up with udev-151. or with .config *and* udev-151 ? I'm booting a home made .config here and the only trouble I had was related to drm+nouveau (now cured by using the proprietary nvidia driver) but I had *no* trouble with hard disks or missing /dev/ ranges (even with LVM and crypt (not the root)). Robby, if you want I can send you my .config and you could sdiff it with Brad's one in case it'd help and see if it gives a hint? |