Laptops :: No X Display pm ThinkPad - Out of Ideas

Quote (doobit @ Feb. 08 2006,16:12)

You may have corrupted something in your file system, or you don't have a complete install if it can't find /opt/bootlocal.sh

Thanks for this info - I was unaware.

Question: I copied the KNOPPIX and BOOT directories over to the computer's C: drive as per the "alternative poorman's install, boot from floppy" method (in the DSL wiki IIRC).

But I think I copied these directories from the isolinux version of the DSL CD. Given that my machine is very old, and given that the boot floppy appears to use syslinux to boot, should I try again by copying over the KNOPPIX and BOOT directories from the syslinux version of the DSL CD? Do you think that might make a difference?

Matt

No, it should not make a difference. The booting is actually done from the files on the floppy and then the knoppix file is used. So the isolinux files are ignored unless you choose to run the frugal or hd install scripts.

I also doubt that your filesystem is corrupted. Usually, you get something like "cloop error" messages when your knoppix file is corrupted, and you did not see these messages.

My guess is that you get some kinda error message like

"undefined mode selected" or something like that and then you press space and boot in NON-framebuffer mode, which would explain why the fb0 error happens when you try to use the framebuffer for X-Windows.

Try a bunch of alternative framebuffer resolutions like 771 or 785

Quote (cbagger01 @ Feb. 08 2006,23:40)

Thanks for the clarification. This is extremely helpful.

But I am still confused on one point of your response:

- I understand how to specify alternative framebuffer resolutions - I use "dsl vga=771" type cheatcodes at boot, yes?

- I do indeed get the "machine has passed an undefined mode" error early on in the boot process. Sometimes I press space, and other times I press enter and select 0 for 80x25 text display.

What I don't understand is how these two are related. For example, when I press Enter and 0 to choose 80x25, am I booting in framebuffer mode or not? If not, would I boot in framebuffer mode if I made another choice (i.e. 80x28 or something)?

Relatedly, the reason I've been using 769 as my vga= value is because I thought that was a display parameter for the actual screen, as opposed to a framebuffer value - in other words, I haven't yet tried the vga=788 that many people use, because that's for a resolution (800x600) not supported by the 701c's video circuitry (its screen is 640x480-only).

So - then is it true that the vga= cheatcode controls only the framebuffer resolution/size?

And - other than not pressing space - how do I ensure I'm booting in framebuffer mode after I get the "undefined mode" error?

I think I'm getting close to figuring this out.

TIA again for any further assistance. Sorry to be such a bother.

Best,
Matt

Let me explain a little further.

It is possible to boot DSL with a VGA text mode console. You can do this by either booting with:

dsl vga=normal

or by NOT entering a graphical framebuffer resolution code at the Undefined Mode prompt.

However, you DO need a valid graphical frame buffer up and running in order to use the xfbdev server.

The easiest way to tell if you are using a graphical frame buffer mode that is valid for your computer is:

1) You don't get the "Undefined Mode" message.
2) When the bootup text appears on your screen, a small image of a penguin will appear in the upper left hand corner of your monitor screen.

So you need to try other vga=xxx codes until you find one that is supported by your PC. Or maybe search google for your laptop model and linux and framebuffer or "frame buffer".

Once you get this far, you can then boot with your new xxx code like this:

dsl vga=xxx xsetup

and choose the xfbdev server when prompted.

Hope this helps.

Thanks again, cbagger01. Very helpful, and I think I'm finally zeroing in on the problem.

You're correct about the framebuffer - I don't get the little Penguin graphic, and I get the undefined mode error. I haven't exhausted every single vga= cheatcode, but I've tried several and it makes no difference.

From doing a little Googling on the TP701c with other flavors of Linux, one recurrent theme is that users seem to have to specify the graphics chip in their XFree86 Config files, under a "device" heading, like this:

Section "Device"
Identifier "Card0"
Driver "chips"
ChipSet "ct65545"
VideoRam 1024
BusID "ISA"
EndSection

For some reason, according to the sites I've checked, the installer misidentifies the graphics chip.

So either the graphics chip needs to be specified via a dsl cheatcode somehow, or else support for that chip isn't in the compile of the linux kernel used by dsl (which I sort of doubt) - or I need to be able to call up the X86Config file at the DSL terminal prompt, edit it, save it, and then try starting X again.

Ugh. Any suggestions? A dsl cheatcode would obviously be easiest, but somehow I doubt I could do that.

It's a shame - I really like what I've seen of DSL so far. The booter recognizes the TP's PCMCIA slot, and the ancient IBM enet PC card in the slot (more than I can for Windows 3 and OS/2 Warp on this particular model of Thinkpad), and it even starts DHCP broadcasting, all of which I find absolutely amazing for an uncustomized *nix running "live".

So anyway, if anyone has any ideas I'd love to hear them.

Thanks!

Matt

Next Page...
original here.