Same thing here with a new desktop that works fine with slacko 533 PAErjbrewer wrote: Same result on all 3 listed intel laptops.
Not sure what command to issue in 533 to determine more information that would be of assistance to you.
Thom
If I boot "pfix=nox,ram" I can run xorgwizard and take the vesa option to get to desktop. But, other desktop navigation issues arise.Same results on my intel video laptops.
Thanks peebee for persisting.peebee wrote:Hi Mick
Got a working 5.3.5alpha by using the grub4dos edit facility to temporarily add nox to the boot line - and then selecting the vesa driver.
Found that I am unable to blacklist a module - see attached where b43 is both blacklisted and loaded simultaneously.....
Cheers
peebee
Hi Mick01micko wrote:I wonder if it's really loaded? I did have a similar issue with nouveau being reported as loaded but I knew it wasn't (with lsmod). The nvidia driver still installed fine, if nouveau is loaded it can't install.
Can you please zip (or gzip) your /etc/rc.d/MOSULESCONFIG file to make sure it made the skip list, or just post the 'skiplist' variable.
Cheers
Code: Select all
MODULE="`/sbin/modprobe -i -b --show-depends $MODALIAS 2>/dev/null | tail -n 1 | rev | cut -f 1 -d '/' | rev | cut -f 1 -d '.' | tr '\-' '_'`" #120809
Thanks Richard.rerwin wrote:My interpretation of all this is that until now the -b option was the default, and that now it is required. Otherwise, why have it?
To keep things simple, I attach the corrected module loader, including other woof fixes for firmware loading and modules loaded specifically by udev rules. Please test with it. Thank you.
Richard
NEW • Development Release: Slackware Linux 14.0 RC1
Slackware Linux In the most recent changelog entry, Patrick Volkerding declares the Slackware "Current" tree, the distribution's development branch, release-candidate quality: "Good hello and happy Thursday! Mercury went direct early yesterday morning and it was like the bugs started to fix themselves. It's almost enough to get me believing in that hocus-pocus nonsense. So, here's a bunch of updates that fix all of the reported issues in the beta and we'll call this the 14.0 release candidate 1.
Richard's fix pet works for me - thanks Richard01micko wrote:Thanks Richard.rerwin wrote:Please test with it. Thank you.
Richard
I'm sure this is to do with the new "kmod" implementation which replaces "modules-init-tools", mentioned in the first post under the "developer" heading. There were sure to be some bugs turn up with that and I'm glad you found the cause. I'll put your fixes in the next version.
Cheers
One letter answer ... "Y" . That was the first thing I checked when I saw the report, but I do think it's the bug rerwin fixed.01micko. Did you remember that logitech wireless receiver fix in kernel DOTconfig. There was that hid section need for compile that locitech receiver in, not as module. I posted about it in some of your thread, maybe this one. I can dig the needed DOTconfig configuration again.