SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'll boot into it again later and try getting xorg sorted out. It's not gone too badly for a first use of Qemu. I'll probably get VMWare and try that too. I look forward to reading your progress on your blog.
Just looked at your blog, I'll edit my XF86Config, see if that sorts my problem out later.
As well as that mix up with X, I also missed setting my keyboard layout during the install - in too much of a hurry. So I think I'll start again, and think before I act this time.
I'll leave 'til after my evening meal. Never install Slack on an empty stomach.
This could be the root of my problems, from the Xfree86 HOWTO:
Configuring XFree86 to use your mouse, keyboard, monitor, and video card
correctly used to be something of a black art, requiring extensive
hand-hacking of a complex configuration file. No more; recent releases have
made the process nearly trivial. It simplifies matters a lot that there are
no longer separate servers for different kinds of cards, just modules loaded
by a common server.
Seems getting X working was a lot different then. I was trying on my laptop before, but will try on my desktop next time.
Just downloaded the install-guide-2.3.pdf from the site where I got the 3.5 iso, it gives info on the different xservers, configuration, and so on. Quite a bit of work involved. Mmm, has Brian bitten off more than he can chew? See the next thrilling episde!!!
Mmm, has Brian bitten off more than he can chew? See the next thrilling episde!!!
Hey, don't give up yet!
Configuring X was something of a black art in those days. I fondly remember how I suffered configuring X with my first installations. And in those days there was no LinuxQuestions.org to check
But I guess I suffered so much in those days that it all came back to me installing 3.5 again.
Some basic tips:
1) Choose your X server
This is done by changing the symbolic link /var/X11R6/bin/X to one of the servers in /usr/X11R6/bin/
There are several to choose from but for me only the XF86_VGA16 worked in VMware.
2) Configure your mouse in /etc/XF86Config
Since I opted to use gpm in the CLI, X has to be configured using a special "repeater" mouse. Use:
3) VGA setup in /etc/XF86Config
You'll find the standard VGA device in there with the 'generic' driver that should be ok. Now find the lines for the VGA server (not SVGA) and set the virtual size to 640 480 (or else you'll get a scrolling screen that is horrible to work with.
It should point to the "Generic VGA" device and to a monitor you configured.
This is all for Slackware 3.5.
Slackware 1.1.2 is slightly different, but uses the same concept of a symbolic link to a server.
I hope you'll get it to work so that you can tell me how Qemu behaves, especially the graphic part...
No, I'm not giving up yet.
I think I know what's going wrong. During the installation (I always do a full install), a link is created from each of the xservers in turn to /usr/X11R6/bin/X, so the last one installed is linked, whether it's the one wanted or not. So if I remove that link and make a link to the right one, edit XF86Config, and swear a lot at my computer - things might work out OK.
I remember using usenet at the time, but I was at a complete loss, knowing almost nothing about Linux. Didn't even know what to ask exactly and felt I had to find things out for myself. My local ISP had its own news server with all of the computer-related lists.
I simply read all the man pages and bought some books to study. Help was harder to find in those days (talking about 1996 by the way).
I had an ISDN line that I couldn't get to work (it used some strange ISA card that came with a Windows driver). I ended up (believe it or not) using a Windows NT server as a router to connect my Linux box to the internet.
OK, I confess: I was a MCSE on those days But Windows was my job, Slackware / Linux was my new challenge.
It's a good thing I'm bald, otherwise I'd be tearing my hair out
I did what I said I'd do in my previous post, but on running startx- it came up with an error. So I re-edited XF86Config to hopefully clear that up. A different error. Re-edit. Yet another error!! Aaaaaaaaaaaaaaaargh! Can't post the errors, tried and failed copy and paste. I shall prevail...Nil desperandum.
Is it at least starting the correct server?
If the errors fly by too fast, try
startx 2> x.log
Might be complaining about clock-modes that are not found etc...
Yeah, clock-modes was one of the errors. It's starting the correct server: XF86_VGA16, but it seems to be looking for a particular chipset or something it can't find through emulation. I'll have another of the HOWTO I downloaded, and the Qemu docs - after a break for coffee, nicotine, tranquillisers, and psychotherapy.
Success! Well, nearly. After reading the HOWTO (RTFM, Brian!), I ran SuperProbe, which told me I should be using the XF86_SVGA server. So I changed the link to X, logged in as brian, and ran startx. A pale turquoise desktop appeared, empty except for a black square. I pressed Alt-F1 and a menu popped up. Trouble is now I can't use the menu, but things are progressing.
First I got the X fine grid pattern with the "X" cursor, then fvwm. I think I pressed Alt-F1 to get the menu to pop up, but couldn't get any response clicking on the menu items. I've never used fvwm before, so that's something else I'll have to RTFM about. Now I've got the menu to go, and can't get it back again.
Just checked htop. I'm on my laptop with a Pentium Dual Core, and number 1 core is running at 0.7%, number 2 at 100% due to qemu.
Just got it going on my desktop, up to the same stage as I had it on my laptop - but different. Using the XF86_SVGA server again. I've got the fvwm desktop, with a taskbar with penguin button at the left corner, and above that a deeper bar with icons for a clock, a monitor, calculator, filing cabinet, fish(?), and some more off screen because it's too far over to the right. No mouse use available. 100% CPU use (Sempron 2600+).