I installed 8.2 on a 80G HD for a VIA MVP3 chipset motherboard (K6/2) with ET6x00 video and rtl8139 about 1.5 years ago. I never really used that HD after that. Today, I hooked that HD up to an i915P chipset motherboard (socket 775 P4) with G400 video. This is a board that includes IT8212F IDE as well as ICH6 IDE & SATA, and rtl8169 eth0. It booted right up without a whimper. Amazing! NIC and graphics didn't work initally, but sax2 & YaST fixed those easily! Again amazing! However, when I try to switch the VGA=788 line in grub's menu.lst to VGA=791, I get an invalid video mode message. Does anyone using Matrox know why this is, and if there's a simple way to get a little higher resolution than 800x600 on the consoles? -- "In everything, do to others what you would have them do to you." Matthew 7:12 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
On Monday 14 March 2005 1:21 am, Felix Miata wrote:
However, when I try to switch the VGA=788 line in grub's menu.lst to VGA=791, I get an invalid video mode message. Does anyone using Matrox know why this is, and if there's a simple way to get a little higher resolution than 800x600 on the consoles?
Felix Miata
Invalid Video Mode applies to the monitor not the video card. Since you changed the video card the monitor definition needs to be updated too. Try sax2 and if that doesn't work you may need to use sax2 -l for low resolution, define the monitor then define the video card and resolutions. Stan
Stan Glasoe wrote on Mon, 14 Mar 2005 07:47:02 -0600:
On Monday 14 March 2005 1:21 am, Felix Miata wrote:
However, when I try to switch the VGA=788 line in grub's menu.lst to VGA=791, I get an invalid video mode message. Does anyone using Matrox know why this is, and if there's a simple way to get a little higher resolution than 800x600 on the consoles?
Invalid Video Mode applies to the monitor not the video card. Since you changed the video card the monitor definition needs to be updated too. Try sax2 and if that doesn't work you may need to use sax2 -l for low resolution, define the monitor then define the video card and resolutions.
The actual error message was: "You passed an undefined mode number." I also have a 9.0 system with a G400, and it behaves the same way. :-( However, I get no such error using ET6000 video on Mandrake 10.2 on the same Sony 200GS display, or using ET6000 video on RedHat 6.2 on the same 200GS display, or using ET6100 video on SuSE 9.2 on a 2nd 200GS display, which also does vga=794 just fine. And, all that work AFAIK have never had any special config program run to make 791 or 794 work. In fact, it seems the GUI Linux installers all seem to use either mode 791, or something higher, maybe 794, or some still different framebuffer mode? vga=778 works with the G400 during the first phase of boot, 143x43 I think, but it switches to only 21 lines shortly before "creating /var/log/boot.log" displays. It seems to me the monitors themselves are fine. I read http://www.tldp.org/HOWTO/Framebuffer-HOWTO-5.html#ss5.4 but it isn't clear that it applies to a G400 or that it isn't an optional way to configure for Matrox. I'm not trying to change any X settings here. Are you saying I have to configure *monitor* (display) settings somewhere in Linux config files for use on tty[1-6], and that's what sax2 -l should do? All it seems to affect here is X. -- "In everything, do to others what you would have them do to you." Matthew 7:12 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
On Monday 14 March 2005 11:22 am, Felix Miata wrote:
The actual error message was:
"You passed an undefined mode number."
I also have a 9.0 system with a G400, and it behaves the same way. :-( However, I get no such error using ET6000 video on Mandrake 10.2 on the same Sony 200GS display, or using ET6000 video on RedHat 6.2 on the same 200GS display, or using ET6100 video on SuSE 9.2 on a 2nd 200GS display, which also does vga=794 just fine. And, all that work AFAIK have never had any special config program run to make 791 or 794 work. In fact, it seems the GUI Linux installers all seem to use either mode 791, or something higher, maybe 794, or some still different framebuffer mode? vga=778 works with the G400 during the first phase of boot, 143x43 I think, but it switches to only 21 lines shortly before "creating /var/log/boot.log" displays. It seems to me the monitors themselves are fine. I read http://www.tldp.org/HOWTO/Framebuffer-HOWTO-5.html#ss5.4 but it isn't clear that it applies to a G400 or that it isn't an optional way to configure for Matrox.
I'm not trying to change any X settings here. Are you saying I have to configure *monitor* (display) settings somewhere in Linux config files for use on tty[1-6], and that's what sax2 -l should do? All it seems to affect here is X.
Felix Miata
Based on your original error message it sounded like you needed to configure the monitor. "You passed an undefined mode number." is different. That is the video driver and framebuffer settings you've identified. I see this on a client's server with embedded video (maybe 8MB video memory). I've tried the various vga= settings and none of them work on this machine. X and KDE work just fine when needed. I'd say you are on the right track for fixing this. Is the video card still good? Does it display well in X? High resolutions and 16, 24, 32 bit color? Stan
Stan Glasoe wrote:
On Monday 14 March 2005 11:22 am, Felix Miata wrote:
The actual error message was:
"You passed an undefined mode number."
I also have a 9.0 system with a G400, and it behaves the same way. :-( However, I get no such error using ET6000 video on Mandrake 10.2 on the same Sony 200GS display, or using ET6000 video on RedHat 6.2 on the same 200GS display, or using ET6100 video on SuSE 9.2 on a 2nd 200GS display, which also does vga=794 just fine. And, all that work AFAIK have never had any special config program run to make 791 or 794 work. In fact, it seems the GUI Linux installers all seem to use either mode 791, or something higher, maybe 794, or some still different framebuffer mode? vga=778 works with the G400 during the first phase of boot, 143x43 I think, but it switches to only 21 lines shortly before "creating /var/log/boot.log" displays. It seems to me the monitors themselves are fine. I read http://www.tldp.org/HOWTO/Framebuffer-HOWTO-5.html#ss5.4 but it isn't clear that it applies to a G400 or that it isn't an optional way to configure for Matrox.
I'm not trying to change any X settings here. Are you saying I have to configure *monitor* (display) settings somewhere in Linux config files for use on tty[1-6], and that's what sax2 -l should do? All it seems to affect here is X.
Based on your original error message it sounded like you needed to configure the monitor.
"You passed an undefined mode number." is different. That is the video driver and framebuffer settings you've identified. I see this on a client's server with embedded video (maybe 8MB video memory). I've tried the various vga= settings and none of them work on this machine. X and KDE work just fine when needed.
I'd say you are on the right track for fixing this. Is the video card still good? Does it display well in X? High resolutions and 16, 24, 32 bit color?
I didn't try higher than 1600x1200x16, which works fine in KDE except for blasting the pc speaker repeatedly while initializing. 1600x1050 makes everything too tiny for me on a 17", so I backed down to my customary 1400x1050x16. More bits don't help me - I can't see the difference between 16 and anything higher. It's kinda hard to comprehend this limitation when more primitive hardware doesn't have it. -- "In everything, do to others what you would have them do to you." Matthew 7:12 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
Felix Miata wrote:
The actual error message was:
"You passed an undefined mode number."
Try running hwinfo --framebuffer as root. This should give you valid numbers for your board. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
Joe Morris (NTM) wrote:
Felix Miata wrote:
The actual error message was:
"You passed an undefined mode number."
Try running hwinfo --framebuffer as root. This should give you valid numbers for your board.
:-( Very discouraging to see a board so state of the art when new be so backward here when cheaper older cards with less RAM have no such problem: 02: None 00.0: 11001 VESA Framebuffer [Created at bios.395] Unique ID: rdCR.xpCz25nMUV0 Hardware Class: framebuffer Model: "Matrox G400" Memory Size: 16 MB Memory Range: 0xfa000000-0xfaffffff (rw) Mode 0x0300: 640x400 (+640), 8 bits Mode 0x0301: 640x480 (+640), 8 bits Mode 0x0302: 800x600 (+100), 4 bits Mode 0x0303: 800x600 (+800), 8 bits Mode 0x0310: 640x480 (+1280), 15 bits Mode 0x0311: 640x480 (+1280), 16 bits Mode 0x0312: 640x480 (+2560), 24 bits Mode 0x0313: 800x600 (+1600), 15 bits Mode 0x0314: 800x600 (+1600), 16 bits Mode 0x0315: 800x600 (+3200), 24 bits Config Status: cfg=no, avail=yes, need=no, active=unknown My old Tseng cards give me roughly 10 times as many modes to pick from. Anyone know what the last line means, or the numbers in parens? -- "In everything, do to others what you would have them do to you." Matthew 7:12 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
participants (3)
-
Felix Miata
-
Joe Morris (NTM)
-
Stan Glasoe