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.
So I went through the Slackware install, going the recommended route of installing all packages in the groups I selected.
I've logged in as root and created a new user, no problems. However, running 'startx' yields a blank screen.
I ran Xorgsetup and Xorgconfig, answering the questions to the best of my ability. Neither worked.
The more pressing problem is I stupidly went and edited my /etc/inittab to make it boot to runlevel 4, which means it boots straight to a black screen now.
Anyone got any suggestions as to how I can go about fixing this?
It's a laptop with a Trident CyberBlade i1, currently configured with 4MB RAM.
Use your slack 10.1 cd #1 and boot from cdrom. there are instructions on screen how to use it as a rescue disk (basically copy the line verbatim). This should boot you into the system. From here you can edit your /etc/inittab file back to runlevel 3
Also you could probably use ctrl +alt + backspace to kill X from your regular login, not sure if this will work.
Once you fix that problem then it's onto the other one. What type of video card do you have? The output from lspci should give you some info on it. Once you figure this out you probably need to change the driver in the /etc/X11/xorg.conf file to change the driver.
For an ati radeon card, just change the vesa framebuffer device to "radeon" for nvidia it's either nv or nvidia, i'm not sure. But this might be one of your problems. (it looks like your laptop might use a via integrated device, search around for the name of the via driver name for linux).
Originally posted by kriton12 Use your slack 10.1 cd #1 and boot from cdrom. there are instructions on screen how to use it as a rescue disk (basically copy the line verbatim). This should boot you into the system. From here you can edit your /etc/inittab file back to runlevel 3
Also you could probably use ctrl +alt + backspace to kill X from your regular login, not sure if this will work.
Once you fix that problem then it's onto the other one. What type of video card do you have? The output from lspci should give you some info on it. Once you figure this out you probably need to change the driver in the /etc/X11/xorg.conf file to change the driver.
For an ati radeon card, just change the vesa framebuffer device to "radeon" for nvidia it's either nv or nvidia, i'm not sure. But this might be one of your problems. (it looks like your laptop might use a via integrated device, search around for the name of the via driver name for linux).
Thanks. I was able to get back to the command line by hard-rebooting and typing "Linux 3" at the LILO prompt.
lspci lists the video card as "Trident Microsystems CyberBlade i1 (rev 6a)".
Did a bit more research and found Xorg's log file at /var/log/Xorg.0.log .
It said the X server was shutting down because it couldn't find a pointer device. Looking in "man xorg.conf" pointed me to a ServerFlag that makes it ignore mouse device errors. Put that in the xorg.conf file, and now X works fine. But with no mouse.
How can I get this to recognize the Synaptics touchpad I have on this laptop?
I have a synaptics touch device as well and it works find under the PS/2 protocol and also the IMPS/2 protocol.
Back to the Xorg display thing, you might also want to try the drivers "trident" or "cyberblade" I don't know if they were included in the kernel modules support but I've seen this in XFree86 conf files so you might luck out. You're probably just using the generic VESA device which won't be able to give you great screen resolutions or video speed.
But for the mouse, again, i'd try the ps/2 protocol. Find the section in the xorg.conf file for the mouse and make sure it says option ps/2. If that doesn't work try the imps/2
Option "Protocol" "ps/2"
or
Option "Protocol" "imps/2"
Originally posted by kriton12 I have a synaptics touch device as well and it works find under the PS/2 protocol and also the IMPS/2 protocol.
Back to the Xorg display thing, you might also want to try the drivers "trident" or "cyberblade" I don't know if they were included in the kernel modules support but I've seen this in XFree86 conf files so you might luck out. You're probably just using the generic VESA device which won't be able to give you great screen resolutions or video speed.
But for the mouse, again, i'd try the ps/2 protocol. Find the section in the xorg.conf file for the mouse and make sure it says option ps/2. If that doesn't work try the imps/2
Option "Protocol" "ps/2"
or
Option "Protocol" "imps/2"
Hey, one other thing I happened to come across last night. If you want to enable the tap-clicking property (tapping the touchpad constitutes a mouse click) and you are compiling your own kernel, make sure the evdev driver is loaded, it's in device files - Input devices - listed as something like event something or other. As long as this is enabled you should be able to use the tap for mouseclick feature.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.