2013-03-31T14:38:56ZFluxBBhttps://bbs.archlinux.org/viewtopic.php?id=160337Starting to "throw stuff at it and see if anything sticks.."

Installed the ATI driver to see if that helped. When I rebooted, it went into sleep mode at startx command. Installed slim, as I thought perhaps the issue was related to initializing the window manager. Results were interesting, to say the least. I'm pretty sure that I have fluxbox listed in ~/.xinitrc already. Can't say for sure, I fat-fingered the verification when I was using nano to check it, and bash froze, for some reason, so I killed the box and restarted. When I did, I got to the same bash shell log-in that has been there since this process started, but when I went to log in, the screen changed to the Fluxbox graphical log-in!

So I thought, "All right, here we go.." and gave my user name, then it asked for the password and I entered that.

Then it went into hibernation (black screen, no keyboard functions, again) instead of loading Fluxbox.

Two steps forward, one step back.

EDIT: I thought the kernel boot parameter setting ( acpi=off ) would be persistent, but apparently it isn't, so I went back and reset that. Still got the same results, user log-in screen, then pitch black screen.

EDIT SOME MORE: I'm trying to use some live cd's from other distros, thought perhaps that would shed some light on what's up with graphics output to my screen. So far, both Semplice and Mint LXDE haven't been able to start any GUI. so perhaps what's happening is that xorg is stopping because there is some hardware or memory problem, completely unrelated to what I've installed, and x would work just fine if I could ante up for enough ram on this Thinkpad. I'd have to get past the idea of spending an extra twenty-five bucks for more memory on a laptop that's worth maybe forty dollars, max, and get the extra 256mb that this needs to work.

Or perhaps I need something else entirely, as the computer I was using to post this just crashed while I was half way through writing this, and it's never crashed before. Perhaps I need to consult a priest as well as upgrading the memory. Either way, not Arch's problem.

I'm marking it "resolved," and saying to hell with it! Thanks for all the help, sorry if I wasted someone else's time.

]]>https://bbs.archlinux.org/profile.php?id=368082013-03-31T14:38:56Zhttps://bbs.archlinux.org/viewtopic.php?pid=1252200#p1252200There are some other kernel boot parameters that may help as well: noapicnomodesetand there are others. Don't really know exactly what you need for that old hardware. Google may help.]]>https://bbs.archlinux.org/profile.php?id=532362013-03-31T04:36:30Zhttps://bbs.archlinux.org/viewtopic.php?pid=1252056#p1252056Still no WM, but X didn't go black, so that's something new. Bash shows "waiting for x server to shut down server terminated successfully (0). closing log file"

/var/log/Xorg.0.log shows first "EE" error at Failed to load module 'ati" (module does not exist), then loads vesa. Next "EE" is "failed to load modeset (module does not exist)." Next "EE" is when it can't load fbdev (doesn't exist). Then it seems to start vesa, shows module "vbe". There were about 40 pages of "stuff" (?), just system info, followed by some more vesa information and saying that "evdev" had unloaded.

I can install the ATI driver and have them both ready when the system boots, but I don't know if that's a fix.

]]>https://bbs.archlinux.org/profile.php?id=368082013-03-31T04:08:43Zhttps://bbs.archlinux.org/viewtopic.php?pid=1252051#p1252051Try setting a kernel boot parameter of acpi=off]]>https://bbs.archlinux.org/profile.php?id=532362013-03-31T02:27:26Zhttps://bbs.archlinux.org/viewtopic.php?pid=1252040#p1252040Aggh! So close!!! Re-installed entire system (twice!! First time went well, only to discover that I'd skipped the 'minor detail' of setting the root password! Then after following the wiki for resetting it using a live cd, finding out that while I could become root using the new password, nothing could be edited with nano - all permissions were lacking. Then gparted wouldn't even load on the monster I'd created, nor would another Linux OS load so I could have something to clear the hard drive and start over! I was getting worried, but the Arch live cd had no problem after wiping out sda1 + 2 and starting over. Whew!)

After all that, all went well, and I had a MUCH better xorg install, must have been the mirror I used before, or the issue with the time/date errors, which haven't returned. A big clue was that I could now get xclock, xterm, etc running. That told me that I was good, and there was a mouse in xclock/xterm as well.

I went with Fluxbox this time, and have done everything I can to get it right. But, alas, when I enter "startx," the Thinkpad goes right into sleep mode ( I assume. The screen goes straight to black. No ctl/alt/f2, etc)

I see an error saying that no screen (again), or something. It's hard to tell because the screen quits almost instantly. Before, I could tell when the screen just wasn't loading properly, the flat-screen would have a dark grey/black color, but I could tell that it was still backlit, just no image information coming to it. When it goes into the sleep/fail mode, there's nothing, period.

Tempted to install dbus, as that seemed to make LXDE appear before, but I'm shying away from installing anything and everything that sounds remotely connected to the screen crash. Openbox comes to mind in that category. I'll reboot it and see if I can get a /var/log

No, that doesn't work. X refused to start, and apparently no log was made. Just saw that David Boston had a reply. I only have the vesa driver installed this time, hoped that would be enough for my needs. If that would be a solution, though, I'm all for it. I was trying to keep this try as bare as possible, so I could sort it out if it failed, which it certainly has.

EDIT: Did a quick run through of Xorg :0 -configure. When it finished, it said to test it by by running (something....) xorg.new. When I did that, the screen again went black immediately.

]]>https://bbs.archlinux.org/profile.php?id=368082013-03-31T01:26:47Zhttps://bbs.archlinux.org/viewtopic.php?pid=1252034#p1252034The "ati" driver appears to be the correct one to use. Thinkwiki.org says: "Display on the internal LCD works as long as you set the monitor settings correct."http://www.thinkwiki.org/wiki/ATI_Rage_Mobility_M

]]>https://bbs.archlinux.org/profile.php?id=532362013-03-30T20:54:02Zhttps://bbs.archlinux.org/viewtopic.php?pid=1251944#p1251944After removing the vesa driver and installing the ATI, I'm getting "no screens found." Tried re-installing the xorg-server packages, still get the same result. Took a look at /var/log/Xorg.0.log, not sure what to make of it. I can copy it to a pastebin, if I can find how to do that, it's been a while.

The log shows loading module "ati," and gives some module information, shows a "II" before it, indicating to me that it was done without any problem. The next line shows loading module "mach64" sounds to me like something for a 64 bit system, maybe a way to probe for a 64 bit system, who knows? That fails with a warning, and it unloads the mach64 module. Next it tries to load vesa, and that's where the first "EE'" error shows, then I get EE at modesetting and fbdev, and it exits with "no drivers available" and "no screens found."

Thinking of just re-installing from scratch and see what happens, if it repeats or if I have clobbered something.

]]>https://bbs.archlinux.org/profile.php?id=368082013-03-30T04:16:58Zhttps://bbs.archlinux.org/viewtopic.php?pid=1251575#p1251575Try to determine the GPU of your A22 and install the appropriate video driver. Try the following command:

]]>https://bbs.archlinux.org/profile.php?id=532362013-03-29T07:16:53Zhttps://bbs.archlinux.org/viewtopic.php?pid=1251083#p1251083Yes, it's just the "red button" in the middle of the keyboard, no touchpad. Then the three mouse keys below the key board.

pacman -Ss xf86 | grep installed shows almost a duplicate list, with the exceptions of xf86-video-vesa instead of intel, and no multilib/lib32-libxxf86vm.

]]>https://bbs.archlinux.org/profile.php?id=368082013-03-29T03:03:01Zhttps://bbs.archlinux.org/viewtopic.php?pid=1251000#p1251000I see that the A22 has the TrackPoint IV, same as my old T42 and my current X220. I believe the Synaptics driver is built into the kernel. Possibly this Gentoo wiki will help.

That said, I wonder instead if your X-server has crashed leaving you with no keyboard or mouse input. To me, this would seem more likely. Especially with those old GPU's (ATI or Savage). Just a thought - maybe you need to enter a kernel boot parameter. You could review your /var/log/Xorg.0.log for errors and clues.

EDIT: I just checked, I do not have any external synaptic driver packages installed for my X220 and the TrackPoint works fine. I did create a file to enable scrolling, but that is not absolutely required.

]]>https://bbs.archlinux.org/profile.php?id=532362013-03-28T06:13:14Zhttps://bbs.archlinux.org/viewtopic.php?pid=1250563#p1250563For the mouse, are you talking about an actual physical mouse or a touchpad? If you mean the touchpad, you will need to install the xf86-input-synaptics package. Additionally, I'm not sure if LXDE requires you to set that yourself; have you tried putting "xsetroot -cursor_name left_ptr &" in .xinitrc?]]>https://bbs.archlinux.org/profile.php?id=511262013-03-28T05:39:22Zhttps://bbs.archlinux.org/viewtopic.php?pid=1250557#p1250557pottzie wrote:

]]>https://bbs.archlinux.org/profile.php?id=285482013-03-28T03:43:51Zhttps://bbs.archlinux.org/viewtopic.php?pid=1250527#p1250527In some window managers, you need to actually set the pointer to be what you want it to be.

As far as the bad packages, I am guessing that what is actually in your package cache is bad, so because they are the newest version, pacman is trying to use those insetad of downloading new ones, and thus you are running into this issue. See if clearing out the package cache helps.

Did you install xorg-xinit, xorg-server-utils, and xorg-server?

]]>https://bbs.archlinux.org/profile.php?id=603122013-03-28T03:38:37Zhttps://bbs.archlinux.org/viewtopic.php?pid=1250526#p1250526After failing at every other option I could find, I've set all signature checking to = Never. I can now get past the "invalid key" problem, but now I have 43 files that xorg-apps needs, and I'm getting "File is corrupted. Invalid or corrupted package (checksum)"

But I can run pacman -Syu with no problem. Seems strange to me that I can update everything, but when I try to re-install or ad anything to xorg, I get red flags and errors up the wazoo.

Just not my day to install anything, evidently.

EDIT: Found someone who had the same problem (from 2009, no less) and it was solved by installing Openbox. So, I installed Openbox.https://bbs.archlinux.org/viewtopic.php?id=71956

Now when I run "startx," the Thinkpad goes black, like maybe it's into hibernation mode. Ctrl/Alt/f2 doesn't work, and I have to power off to get it going again. And if that wasn't enough, when I try and remove Openbox, pacman says no dice, "lxappearance-obconf requires Openbox." So I'm screwed.

The common element is that we're installing to really old stuff. But if you can't do that with LXDE, what else can you do? The reason I went with LXDE is that it's my weapon of choice for old equipment.

EDIT SOME MORE: Installed udev after taking a look at the LXDE wiki. Now I can bring up the LXDE splash screen when I run startx, but still no mousie.

And after all that, I came across the Arch section of the LXDE wiki. It said to install: ttf-dejavu ttf-liberation ttf-bitstream-vera lxde xorg xorg-video-drivers xorg-input-drivers gamin\gnome-icon-theme tango-icon-theme gtk-engines pm-utils udisks

..and I did. By sheer luck I've discovered that the "mouse" is there.....but it's invisible! The post referenced above said that they had the same problem, and by guessing where the mouse should be, they could see that it was there, but there was no pointer on the screen. I have the same thing, I can guess where it should be and open the Applications box by scrolling over it. But without a pointer or anything showing on the screen, this isn't going to be a fun way to surf the web.