SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
We're not talking here about graphical consoles. In fact I didn't know before I read your post that shift-page actually works on a graphical console. I never tried it because I was accustomed to using the scrollbar. Well, I just tried it in xterm in 14.2 and it does work. I think I'll cross-post that in the "What have you learned that's new?" thread. Obviously I should also try it in the new Slackware and see if it works there too.
The problem here is with the getty console. That doesn't scroll any more with the new kernels, which doesn't much matter once you have X working but is a hell of a nuisance when X doesn't work and you have to troubleshoot the problem.
I remember a few months ago there was a thread on LQ about this, and I was quite interested. If I remember correctly, it was said an easy way to prevent X from using the Intel software was to remove the xf86-video-intel package.
Well, I have a small laptop (running Slackware 14.2 32bit) I took out of service because of the random crashing which seems to be related to something about the i915 module. So, I removed the xf86-video-intel package, and found that X would not start. I have not yet spent any time diagnosing the problem, because of other tasks of higher priority... Someday, if I can figure this out, then perhaps I can employ the method on all the other computers I tend which have Intel video 'cards'.
I have found X reaching for i965 for anything 3D but intel at times also. The files appear around the place but only once share the same directory. i915, OTOH, has loads in the kernel. My HD4000 works, but I'll invest effort on my next video card whenever. Performance wise, I had a Nvidia MX-440 pci in a 32bit underpowered box from early 2000s and it left the hd4000 for dead.
Thanks for the clarification, hazel. It took me awhile to get it largely because although I always boot to Runlevel 3, for some time now all I do there of any circumstance that also produces a lot of lines is slackpkg+ and I haven't needed to scroll back for that. Mostly I'm using vim or ncurses apps and the nvidia installer anymore. For the past few years I've even switched to building kernels from X. Hope you find a fix.
As I understood it, as the kernel boots the font size sudden shrinks as the kernel module loads and your monitor screen gets used. So the graphical resolution was there. But the system leftovers from the 80x25 dumb terminal days meant that were incompatible with the things done in X.
I never got more than 1 screen back in getty consoles, and if you pressed any key except shift+PgUp, all bets were off. I have a notion you can set the buffer size for each getty tty somewhere (kernel?) but better, smarter software savvy folks have wrestled with this problem and given up. Ncurses does a limited amount of clever graphical stuff but nobody has ever bettered it. I find myself using an xterm purely for the pageback buffer.
We're not talking here about graphical consoles. In fact I didn't know before I read your post that shift-page actually works on a graphical console. I never tried it because I was accustomed to using the scrollbar. Well, I just tried it in xterm in 14.2 and it does work. I think I'll cross-post that in the "What have you learned that's new?" thread. Obviously I should also try it in the new Slackware and see if it works there too.
The problem here is with the getty console. That doesn't scroll any more with the new kernels, which doesn't much matter once you have X working but is a hell of a nuisance when X doesn't work and you have to troubleshoot the problem.
Well maybe it's less of an solution but more of an habit? (there is a well hidden pun right there <-- )
Code:
$ less /var/log/Xorg.0.log
but that is not the most one could get out of such a dire situation.
Code:
$ most /var/log/Xorg.0.log
Then, again, I for one can't imagine there is anything more to ask for?
Code:
$ more /var/log/Xorg.0.log
P.S.
It sucks how we end up missing features due to maintainers "missing the train" of the ever faster kernel development. Are we nearing to an ending crescendo perhaps?
The mesa-21 upgrade on 12 Mar broke wine game war3 on my current 32bit box.
Code:
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
preloader: Warning: failed to reserve range 00010000-00110000
0104:err:ole:com_get_class_object apartment not initialised
0104:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0104:err:winediag:wined3d_dll_init Setting multithreaded command stream to 0.
X Error of failed request: GLXBadFBConfig
Major opcode of failed request: 152 (GLX)
Minor opcode of failed request: 0 ()
Serial number of failed request: 221
Current serial number in output stream: 221
There are still no patches from Mesa git, if someone runs wine programs in issues, a reverting can solve it in temp.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.