Release Engineering

Tasklist

FS#11903 - boot cd install sequence unusable: horribly wide console font or broken framebuffer console

Attached to Project: Release Engineering
Opened by Bill Powell (troubador) - Monday, 27 October 2008, 17:42 GMT
Last edited by Dieter Plaetinck (Dieter_be) - Tuesday, 09 March 2010, 20:09 GMT
Task Type Bug Report
Category Hardware Issues
Status Closed
Assigned To Aaron Griffin (phrakture)
Dieter Plaetinck (Dieter_be)
Architecture All
Severity High
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The boot CD doesn't work, because the console font appears horribly wide. Though the letters are so wide, Arch acts as if they're normal size, resulting in lines that wrap and push the second half of the screen's information down below the bottom of the monitor. The installation scripts are thus practically unusable.

Strangely, the _initial_ screen of the boot CD (the blue background with your first screen of choices) comes up fine. But once you go into the real boot sequence, this horrible font problem comes.

I have used this Overlord core ISO before on another (newer) computer, with no trouble.
I have also tested this computer with the 2008-03 ftp ISO, but had exactly the same problem.

This is an old computer: a Pentium III 450 Mhz with an old AGP video card. However, it's currently running Slackware 11 just fine, and a Ubuntu live CD worked fine too.

Even with the screen in this state, I managed to run the script that installs all the core packages, and also get grub installed. When I rebooted to my newly installed Arch,
I GOT THE SAME PROBLEM. So there is something seriously wrong with the console font handling here, or else something strange toxic interaction between this particular video card and Arch. Or maybe something with kernel 2.6; I know that the Slack 11 I have now is 2.4.

I have tweaked the kernel line in grub and tried the framebuffer console (vga=773, vga=769. etc.). When I boot this way, I just get green boxes; no characters at all.
I have also tried vbeprobe and testvbe in grub. vbeprobe returns a "not found" for every mode I've tried, e.g., 773 and 769. When I testvbe 773 and 769, I get a rainbow screen of unblinking lines ... don't know what this means, if anything.

I'd really like to get Arch on this computer, so please tell me if there's any diagnostic I can run. If I could get the network installed, I might be able to install X and see what happened then. But I'd much rather fix this first. I've never seen this problem; the one thing every install CD can usually do is give you text on a console.

Thanks!







Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Dieter Plaetinck (Dieter_be)
Tuesday, 09 March 2010, 20:09 GMT
Reason for closing:  No response
Additional comments about closing:  no response after more then a year
Comment by Dan McGee (toofishes) - Thursday, 04 December 2008, 13:54 GMT
What is your hardware (video card)? It may be tough to look at, but anything interesting in dmesg output would probably be useful.
Comment by Bill Powell (troubador) - Thursday, 04 December 2008, 15:31 GMT
Hi! Thanks for your help!

All I know offhand about the hardware is that it's some kind of AGP video card.

The problem is that I switched the computer back to Slackware. Would dmesg under a different distro still be helpful? I suppose the hardware would be the same. So I will get the dmesg output and attach it here. Thanks again!




Comment by Spyros (spyk) - Wednesday, 14 January 2009, 12:46 GMT
I have exactly the same problem, leaving me unable to complete the installation.

I am also on an older PC (Pentium III/700), with an NVIDIA TNT2 card (NV5). I can post more information on the hardware if requested.

Is there maybe any way to try different font console settings at the command line prompt?
Comment by Aaron Griffin (phrakture) - Tuesday, 27 January 2009, 04:52 GMT
Does this still happen in the latest ISOs? If so, can you try the isolinux ISOs?
Comment by Aaron Griffin (phrakture) - Tuesday, 27 January 2009, 04:55 GMT
Also, if this occurs, can you maybe take a picture or something so I can see the exact behavior you're talking about?
Comment by Bill Powell (troubador) - Tuesday, 27 January 2009, 12:22 GMT
Good idea. I will try taking a picture and sending that.
Comment by Spyros (spyk) - Tuesday, 27 January 2009, 21:54 GMT
Hello!

I am attaching some quick photos for my case. I should also note that i did notice the same problem during the Xubuntu 8.10 installation bootup sequence, so the problem might not be Arch specific..

Please let me know if you need any more info!
Comment by Spyros (spyk) - Sunday, 08 February 2009, 14:48 GMT
A quick update, I replaced the TNT2 card with a newer Geforce 4 Ti and the problem went away, so this could be some incompatibility with the particular card, or older AGPs in general..
Comment by Alessandro Doro (adoroo) - Wednesday, 11 February 2009, 01:52 GMT
Have you tried to find a working text mode with vga=ask?

By the way I have successfully tested archlinux-2009.02-RC1-ftp-i686.iso in an old PIII with an integrated Aladdin TNT2 (NV5, rev 20) 10de:00a0; boot and setup ran fine in 80x25 mode.
Comment by Spyros (spyk) - Wednesday, 11 February 2009, 09:58 GMT
I will give it a try with 2009.02-RC1 (and vga=ask) and post back results as soon as i can.
Comment by Spyros (spyk) - Saturday, 14 February 2009, 10:57 GMT
I tried with RC1, I also tried several video modes, the vga ones get the wide fonts, while with the VESA modes i get the same green boxes that troubador described above. I plugged in the card in a newer athlon xp as well, and got the same results...

Any other suggestions are welcome! I might try downloading an older Arch version, see if it persists..
Comment by Spyros (spyk) - Saturday, 14 February 2009, 11:39 GMT
no problems with 2007.08. all modes work fine (although i guess there were no vesa modes on this release)
Comment by Aaron Griffin (phrakture) - Monday, 16 February 2009, 18:07 GMT
I imagine this is a kernel issue. Perhaps using an alternate framebuffer driver would help... but I'm not sure if we can do this on the ISO
Comment by Spyros (spyk) - Saturday, 21 February 2009, 12:22 GMT
Thanks for your reply. Is there somewhere we could report this issue?
Comment by Gerardo Exequiel Pozzi (djgera) - Wednesday, 18 November 2009, 07:39 GMT
what is the status of this issue with newer kernels?

Loading...