framebuffer shenanigans Virgin hp evectra

[wuxmedia]

i got virgin to install, i'm wondering about the framebuffer, because right now i'm on 640x480 which i can live with (it's only a irc/links box atm

no /dev/fb0
modprobe i810/fb=
module not found.
do i have to compile a custom kernel?
bit beyond me so anyway;

lspci;
VGA compatible controller: intel 82810E DC-133

will post lspci-nnk in a min.
googled for days now.
(ubuntu kosmic koala=fail, archbbs=fail, linuxkerneldocs=too old kernel 2.6?)

any thoughts?

not stopping my enjoyment... i know it can display 1024x768 in X...

[wuxmedia]

Code: Select all

00:00.0 Host bridge [0600]: Intel Corporation 82810E DC-133 (GMCH) Graphics Memory Controller Hub [8086:7124] (rev 03)
        Subsystem: Intel Corporation 82810E DC-133 (GMCH) Graphics Memory Controller Hub [8086:7124]
        Kernel driver in use: agpgart-intel
00:01.0 VGA compatible controller [0300]: Intel Corporation 82810E DC-133 (CGC)
Chipset Graphics Controller [8086:7125] (rev 03)
        Subsystem: Hewlett-Packard Company Device [103c:1243]

agpgart-intel? hmm more googleing

[machinebacon]

Take a look at the boot entries on the stick:

Code: Select all

video=uvesafb:mode_option=1024x768-16@60 vga=current init=/bin/systemd

the uvesafb entry stands for the resolution per refresh rate. You should also add

Code: Select all

scroll=ywrap

These things can be placed into the GRUB boot line. Out of convenience, I'd run it from the stick first and make notes which resolution works well. I did get it to work, and the entries are remainders of that. This makes it easier for users to enable fb.

To find the highest resolution, run

Code: Select all

sudo hwinfo --framebuffer

Good luck!

[rhowaldt]

cannot help you, but one thing is for sure Wux: you are definitely progressing in Linuxland here. keep up the good work :)

[wuxmedia]

thanks, been trying the grub entries.
vga=ask seems to be depreciated in grub2.
all the modes on the stick entry - vga are rubbish.
hwinfo gives some mad error.
going out now - post some details later.

[machinebacon]

yep, skip the vga but use the video entry. That's what it's for (fb). You'll get it. Show us the hwinfo later ;)

[wuxmedia]

thanks, cheers rhow - linuxland is a wonderful place with a bunch of bbqers around 8)
I tried a few things, nothing much joy wise...

hwinfo --gfxcard:

Code: Select all

SysFS ID: /devices/pci0000:00/0000:00:01.0
  SysFS BusID: 0000:00:01.0
  Hardware Class: graphics card
  Model: "Intel 82810E CGC [Chipset Graphics Controller]"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x7125 "82810E CGC [Chipset Graphics Controller]"
  SubVendor: pci 0x103c "Hewlett-Packard Company"
  SubDevice: pci 0x1243
  Revision: 0x03
  Memory Range: 0xe8000000-0xebffffff (ro,non-prefetchable)
  Memory Range: 0xeff80000-0xefffffff (rw,non-prefetchable)
  IRQ: 10 (no events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v00008086d00007125sv0000103Csd00001243bc03sc00i00"
  Driver Info #0:
    XFree86 v4 Server Module: intel
    Color Depths: 8, 16, 24
    Extensions:
    Options:
  Driver Info #1:
    XFree86 v4 Server Module: intel
    3D Support: yes
    Color Depths: 16
    Extensions: dri
    Options:
  Config Status: cfg=new, avail=yes, need=no, active=unknown

hwinfo --framebuffer dumps this nothing more;

Code: Select all

cmo@vectra ~ % sudo hwinfo --framebuffer
> hal.1: read hal dataprocess 6232: arguments to dbus_move_error() were incorrect, assertion "(dest) == NULL || !dbus_error_is_set ((dest))" failed in file ../../dbus/dbus-errors.c line 282.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files
cmo@vectra ~ %

so i think i might be stuck in lowres. it's ok not that i do much apart from jabber away on IRC...which it does superbly. actually easier to read 8)

[machinebacon]

Code: Select all

ins hal

try this, maybe it rocks.

and for the resolution something like

Code: Select all

video=uvesafb:mode_option=1280x800-16@60

[wuxmedia]

^ 1280x800 8-O
you gotta be kidding, this card is like 10 years old. on X it never went that high, maybe at 8bbp
I will install hal...
i would be happy just to post a scrot at 640x480-4 just to prove i'm not mucking you around...
i've seen nothing but bad things on google about this ancient gfx card...
i'm thinking i have no framebuffer driver, only freex86 drivers.
i have seen a i810fb driver floating around on sourceforge, but wtf do i do with a .diff file?

[rhowaldt]

maybe i missed it but wux, have you tried just changing font-settings through

Code: Select all

sudo dpkg-reconfigure console-setup

there, pick the Terminus font and set your font settings to the lowest setting. this gave me a beautiful terminal (might be somewhat small for some, and no idea what your personal lowest setting is, but try it out :)

or was this not what you were aiming at?

[machinebacon]

wux, you mean the console-setup? i thought you wanted fbdev and stuff like xlinks2 being displayed at higher resolution (don't know where i got this shit from). My fault. sudo dpkg-reconfigure console-setup and change the fonts there. That's probably what you want.

(ah just noticed rho's reply before, so consider jumping back 1 page)

[wuxmedia]

thanks rhow and bacon, no - i've done that - had to for the ceni issue. and i'm not a massive fan of ibm vga font...
remember the scrot Bacon posted for boner, or virgin? very very large fonts. even on 8x8 or 8x13 etc...
and i have not yet enabled a /dev/fb0 device...

i actually tried this; http://frontseed.com/entry/enable-framb ... sing-grub2

which did something - not what i wanted, made the screen font look more like hieroglyphs 8( i had to reinstall... 8(

anyway - slight waste of time as the machine is 10 years old... it'd be quicker to drop a light WM on it and get xorg to do the work...

oh i tried a bunch of things using the grub commands you suggested - no joy, boots ok but vga=ask (which refuses to run on grub2) has a load of bad modes.
I will play a bit more, but it's more a lost cause...
it's really ok to IRC with and links2 (text mode) if i try links2 -g it gives me a load of errors and quits...although i haven't yet tried on a non tmux/byubo session.

[machinebacon]

yep, the scrot of boner with tmux is the 'maximum' res. with IIRC 640x480, so the same as in GRUB.
but let's go back half step:

Code: Select all

ins hal
sudo hwinfo --framebuffer

[wuxmedia]

nothing.
it enquires about hal then happily exits ,

Code: Select all

cmo@vectra ~ % sudo hwinfo --framebuffer                                        
cmo@vectra ~ %             

i'm in a ssh session right now.

[pidsley]

FWIW, virgin runs at 1280x1024 on my test machine.

scrot is here: http://linuxnoob.freeforums.org/post8003.html#p8003

[wuxmedia]

^ nobody else is complaining, you know it's gonna be only me with problems - pidsley 8)
hang everybody else has machines from this side of the millenium 8)

[machinebacon]

Code: Select all

sudo nano /etc/default/grub

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

so, you boot to grub and go into the command mode, run vbeinfo to find the possible resolutions. then you edit the /etc/default/grub accordingly and remove the # in front of GRUB_GFXMODE=yourXresolution
update-grub as root, afterwards to make this sticky.

[wuxmedia]

seriously guys, i'm sorry i opened this thread.
i do almost everytime 8(
i tried vbeinfo - the machine 'crashes' or freezes for ever, well 10 mins.
vbetool kinda works (shows a couple a square or something) but no information.
plus i tried a few classic res' 800x600, 1024x768 etc just went ahead and booted into 640x480 anyway.

please re-direct your talents to other more important areas...

[machinebacon]

what's the matter ;)

we know now that the native fb resolution of the intel 8xxxx card is 640x480 and that higher ones are not supported, at least not without using illegal methods (whatever they might be)

no worries, that's what the barbie is for. we tried all methods that came to mind, and as long as we did it, it doesn't really matter that we couldn't solve it - because there is nothing to solve :)

[wuxmedia]

thank you - i think so - through normal channels i have a bad'un
not to worry wasn't like i needed it to run GIMP on or anything crazy.

well cheers to being on the road with me guys!

btw i'm always up for a few illegal methods 8)