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 have been waiting for 13.0 to put slackware on my crap macbook. Anyway, so here's a brief summary of the hardware in the macbook:
Machine Model: MacBook2,1
Processor Name: Intel Core 2 Duo
Processor Speed: 1.83 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache (per processor): 2 MB
Memory: 512 MB
Bus Speed: 667 MHz
Now aside from possibly upgrading the memory later, that's pretty much what I have to put the 64 bit slackware on. So I installed it with:
10GB = root system
1 GB = swap
Other ~110GB = /usr/local
First time splitting up the system like that, but wanted to try it out.
Anyway, the problem is this: I log into my system for the first time as root, just to see KDE in 64 bit and it freezes almost immediately. In fact, all of the window managers available in a full install freeze. KDE, for example, actually freezes just as a background with white circles comes up and then an image of a hard-drive fades into view. From then on out, I usually can move my mouse, but the system never moves.
If you need to know anything else, just lemme know. I'm eager to get back into slackware, I love it quite a bit, and wouldn't be too discouraged if I had to go back to 32 bit. I just figured since my processor is 64 bit enabled, I would go for an upgrade.
Suggestions? Answers? Help??
[Addition]
Most of the other window managers freeze immediately upon starting, as stated above. Most bring up a window or image or some such thing, before stopping. Sometimes the mouse freezes, other times it doesn't. I believe Window Maker is the only one that does NOT freeze now, but I'm not sure really.
Last edited by aurostre; 08-30-2009 at 12:13 PM.
Reason: Adding Details
When i installed Slackware 13.0(32 bit version) my computer always freezed when i did startx.Later i found out that it was because in the installation I unchecked the box to run HAL at system startup.
Macs often use custom hardware, you may have to change the xorg.conf graphics driver to vesa. You should boot the system using the install disk to run level 3, then modify /etc/inittab to start at run level three and then you will be able to try and fix xorg.
Are you able to switch back to a console? (Ctrl+Alt+F6) or manually force X to close (Ctrl+Alt+Backspace)?
What you need to do is check your /var/log/Xorg.0.log and see what is causing it to lock up.
No, I cannot force it to close or console.
Quote:
Originally Posted by samac
Macs often use custom hardware, you may have to change the xorg.conf graphics driver to vesa. You should boot the system using the install disk to run level 3, then modify /etc/inittab to start at run level three and then you will be able to try and fix xorg.
samac
The graphics drivers are vesa, and I've edited the xorg.conf file, which now is apparently only xorg.conf.vesa or something, before. Usually running "intel" driver allows me to optimize my graphics, though I've tried both by now.
Is it really only an xorg thing? Because changing the graphics doesn't seem to have an affect. The fact that I can bring it to at least a bit of a picture and some effects tells me it's something else, but I'm not a massive Linux expert.
[Addition]
Up to the freeze, Ctrl + Alt + F6 works, but once it gets to the point of freezing, even with mouse still movable, no other commands seem to work.
Last edited by aurostre; 08-30-2009 at 02:39 PM.
Reason: Additional Details
When i installed Slackware 13.0(32 bit version) my computer always freezed when i did startx.Later i found out that it was because in the installation I unchecked the box to run HAL at system startup.
If that's the problem then just type
as root.
Also tried this, to no change. Still having the problem.
I'm not sure what to look for in /var/log/Xorg.0.log.
The last line reads:
Quote:
(WW) Apple Computer Apple Internal Keyboard / Trackpad: unable to handle keycode 464
Aside from that, nothing's on fire or blaring red.
Where is xorg.conf in the new release? All I can find is xorg.conf-vesa in /etc/X11/...
[Addition]
If it matters, I can get into the F Virtual Window Manager. However, running anything with graphics (even the 2D Chess) shows black bars, stretching, and other graphical errors.
I copied the xorg.conf-vesa into xorg.conf alone and changed the graphics driver to intel, however now the resolution is off. Regardless of that, no change to availability of KDE or any other manager. I'm really quite lost here. I'd like to get 64 bit slackware, but it seems like 32 bit is the only answer. Should that not work, it seems there's an incompatibility I have to work with. I'll never be surprised when slackware doesn't exactly work with everything I want to, that's why I'm working to learn it and improve it for what I need.
Anyway, additional suggestions or ideas are appreciated.
Last edited by aurostre; 08-30-2009 at 03:16 PM.
Reason: Additional Details
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.