Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
vesafb Not Working with Correct VESA modes
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
RichardGv
n00b
n00b


Joined: 26 Jan 2010
Posts: 43
Location: People's Republic of China

PostPosted: Fri Jul 30, 2010 4:11 am    Post subject: vesafb Not Working with Correct VESA modes Reply with quote

Environment:
Gentoo amd64;
zen-sources-2.6.34_p1-r2, compiled with the vesafb support; (I posted this thread here because zen-sources is unsupported.)
(The whole configuration file of my kernel: http://pastebin.com/zdCdDVYC )
x11-drivers/nvidia-drivers 195.36.31;
grub 0.97-r10.

Problem:
I just migrated from nouveau to the official NVidia driver due to a GPU overheating issue. I planned to use vesafb for framebuffer support. In the output of hwinfo --framebuffer (given below), I learned that VESA mode 0x0365 (1440x900x24) is the mode I need.
(My graphic card is a NVidia GeForce 8400 GS, by the way.)
So I tried starting the kernel with "vga=0x365". However, the result was a normal VGA 80x24 screen showed up:
Code:

Jul 30 17:15:01 [kernel] [    0.000000] Linux version 2.6.34-zen1 (root@home) (gcc version 4.4.4 (Gentoo 4.4.4-r1 p1.0, pie-0.4.5) ) #2 ZEN SMP PREEMPT Thu Jul 29 21:08:44 CST 2010
Jul 30 17:15:01 [kernel] [    0.000000] Command line: root=/dev/sda3 vga=0x365
Jul 30 17:15:01 [kernel] [    0.000000] BIOS-provided physical RAM map:
Jul 30 17:15:01 [kernel] [    0.000000]  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
Jul 30 17:15:01 [kernel] [    0.000000]  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
Jul 30 17:15:01 [kernel] [    0.000000]  BIOS-e820: 00000000000e7000 - 0000000000100000 (reserved)
Jul 30 17:15:01 [kernel] [    0.000000]  BIOS-e820: 0000000000100000 - 000000003ffc0000 (usable)
Jul 30 17:15:01 [kernel] [    0.000000]  BIOS-e820: 000000003ffc0000 - 000000003ffce000 (ACPI data)
Jul 30 17:15:01 [kernel] [    0.000000]  BIOS-e820: 000000003ffce000 - 000000003fff0000 (ACPI NVS)
Jul 30 17:15:01 [kernel] [    0.000000]  BIOS-e820: 000000003fff0000 - 0000000040000000 (reserved)
Jul 30 17:15:01 [kernel] [    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
Jul 30 17:15:01 [kernel] [    0.000000]  BIOS-e820: 00000000fecc0000 - 00000000fecc1000 (reserved)
Jul 30 17:15:01 [kernel] [    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
Jul 30 17:15:01 [kernel] [    0.000000]  BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved)
Jul 30 17:15:01 [kernel] [    0.000000] NX (Execute Disable) protection: active
Jul 30 17:15:01 [kernel] [    0.000000] DMI present.
Jul 30 17:15:01 [kernel] [    0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it.
Jul 30 17:15:01 [kernel] [    0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
Jul 30 17:15:01 [kernel] [    0.000000] e820 update range: 0000000000000000 - 0000000000001000 (usable) ==> (reserved)
Jul 30 17:15:01 [kernel] [    0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
Jul 30 17:15:01 [kernel] [    0.000000] last_pfn = 0x3ffc0 max_arch_pfn = 0x400000000
Jul 30 17:15:01 [kernel] [    0.000000] MTRR default type: uncachable
Jul 30 17:15:01 [kernel] [    0.000000] MTRR fixed ranges enabled:
Jul 30 17:15:01 [kernel] [    0.000000]   00000-9FFFF write-back
Jul 30 17:15:01 [kernel] [    0.000000]   A0000-DFFFF uncachable
Jul 30 17:15:01 [kernel] [    0.000000]   E0000-EFFFF write-through
Jul 30 17:15:01 [kernel] [    0.000000]   F0000-FFFFF write-protect
Jul 30 17:15:01 [kernel] [    0.000000] MTRR variable ranges enabled:
Jul 30 17:15:01 [kernel] [    0.000000]   0 base 000000000 mask FC0000000 write-back
Jul 30 17:15:01 [kernel] [    0.000000]   1 disabled
Jul 30 17:15:01 [kernel] [    0.000000]   2 disabled
Jul 30 17:15:01 [kernel] [    0.000000]   3 disabled
Jul 30 17:15:01 [kernel] [    0.000000]   4 disabled
Jul 30 17:15:01 [kernel] [    0.000000]   5 disabled
Jul 30 17:15:01 [kernel] [    0.000000]   6 disabled
Jul 30 17:15:01 [kernel] [    0.000000]   7 disabled
Jul 30 17:15:01 [kernel] [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
...
Jul 30 17:15:01 [kernel] [    0.000000] Memory: 1025140k/1048320k available (3808k kernel code, 452k absent, 22728k reserved, 1840k data, 424k init)
Jul 30 17:15:01 [kernel] [    0.000000] Experimental preemptable hierarchical RCU implementation.
Jul 30 17:15:01 [kernel] [    0.000000] NR_IRQS:320
Jul 30 17:15:01 [kernel] [    0.000000] Console: colour VGA+ 80x25
Jul 30 17:15:01 [kernel] [    0.000000] console [tty0] enabled
Jul 30 17:15:01 [kernel] [    0.000000] Fast TSC calibration using PIT
...

So I tried starting with the "vga=869" (the decimal representation of 0x0365). The result was not much better:
Code:

Jul 30 11:28:35 [kernel] [    0.000000] Linux version 2.6.34-zen1 (root@home) (gcc version 4.4.4 (Gentoo 4.4.4-r1 p1.0, pie-0.4.5) ) #2 ZEN SMP PREEMPT Thu Jul 29 21:08:44 CST 2010
Jul 30 11:28:35 [kernel] [    0.000000] Command line: root=/dev/sda3 vga=869
Jul 30 11:28:35 [kernel] [    0.000000] BIOS-provided physical RAM map:
Jul 30 11:28:35 [kernel] [    0.000000]  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
Jul 30 11:28:35 [kernel] [    0.000000]  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
Jul 30 11:28:35 [kernel] [    0.000000]  BIOS-e820: 00000000000e7000 - 0000000000100000 (reserved)
Jul 30 11:28:35 [kernel] [    0.000000]  BIOS-e820: 0000000000100000 - 000000003ffc0000 (usable)
Jul 30 11:28:35 [kernel] [    0.000000]  BIOS-e820: 000000003ffc0000 - 000000003ffce000 (ACPI data)
Jul 30 11:28:35 [kernel] [    0.000000]  BIOS-e820: 000000003ffce000 - 000000003fff0000 (ACPI NVS)
Jul 30 11:28:35 [kernel] [    0.000000]  BIOS-e820: 000000003fff0000 - 0000000040000000 (reserved)
Jul 30 11:28:35 [kernel] [    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
Jul 30 11:28:35 [kernel] [    0.000000]  BIOS-e820: 00000000fecc0000 - 00000000fecc1000 (reserved)
Jul 30 11:28:35 [kernel] [    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
Jul 30 11:28:35 [kernel] [    0.000000]  BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved)
Jul 30 11:28:35 [kernel] [    0.000000] NX (Execute Disable) protection: active
Jul 30 11:28:35 [kernel] [    0.000000] DMI present.
Jul 30 11:28:35 [kernel] [    0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it.
Jul 30 11:28:35 [kernel] [    0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
Jul 30 11:28:35 [kernel] [    0.000000] e820 update range: 0000000000000000 - 0000000000001000 (usable) ==> (reserved)
Jul 30 11:28:35 [kernel] [    0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
Jul 30 11:28:35 [kernel] [    0.000000] last_pfn = 0x3ffc0 max_arch_pfn = 0x400000000
Jul 30 11:28:35 [kernel] [    0.000000] MTRR default type: uncachable
Jul 30 11:28:35 [kernel] [    0.000000] MTRR fixed ranges enabled:
Jul 30 11:28:35 [kernel] [    0.000000]   00000-9FFFF write-back
Jul 30 11:28:35 [kernel] [    0.000000]   A0000-DFFFF uncachable
Jul 30 11:28:35 [kernel] [    0.000000]   E0000-EFFFF write-through
Jul 30 11:28:35 [kernel] [    0.000000]   F0000-FFFFF write-protect
Jul 30 11:28:35 [kernel] [    0.000000] MTRR variable ranges enabled:
Jul 30 11:28:35 [kernel] [    0.000000]   0 base 000000000 mask FC0000000 write-back
Jul 30 11:28:35 [kernel] [    0.000000]   1 disabled
Jul 30 11:28:35 [kernel] [    0.000000]   2 disabled
Jul 30 11:28:35 [kernel] [    0.000000]   3 disabled
Jul 30 11:28:35 [kernel] [    0.000000]   4 disabled
Jul 30 11:28:35 [kernel] [    0.000000]   5 disabled
Jul 30 11:28:35 [kernel] [    0.000000]   6 disabled
Jul 30 11:28:35 [kernel] [    0.000000]   7 disabled
Jul 30 11:28:35 [kernel] [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 30 11:28:35 [kernel] [    0.000000] initial memory mapped : 0 - 20000000
Jul 30 11:28:35 [kernel] [    0.000000] init_memory_mapping: 0000000000000000-000000003ffc0000
Jul 30 11:28:35 [kernel] [    0.000000]  0000000000 - 003fe00000 page 2M
Jul 30 11:28:35 [kernel] [    0.000000]  003fe00000 - 003ffc0000 page 4k
Jul 30 11:28:35 [kernel] [    0.000000] kernel direct mapping tables up to 3ffc0000 @ 12000-15000
...
Jul 30 11:28:35 [kernel] [    0.000000] Memory: 1025140k/1048320k available (3808k kernel code, 452k absent, 22728k reserved, 1840k data, 424k init)
Jul 30 11:28:35 [kernel] [    0.000000] Experimental preemptable hierarchical RCU implementation.
Jul 30 11:28:35 [kernel] [    0.000000] NR_IRQS:320
Jul 30 11:28:35 [kernel] [    0.000000] Console: colour dummy device 80x25
Jul 30 11:28:35 [kernel] [    0.000000] console [tty0] enabled
...

I tried "vga=ask" to get a list of supported VESA modes, and 0x0365 did not show up in the list.
Have I done something wrong? I wonder why 0x0365 VESA mode refuses to work.

Thanks in advance. Please tell me if there's any additional information needed. I'm still a newbie in Linux, so please forgive me if I do/say something silly.

Additional things:
lspci:
Code:

00:00.0 Host bridge: VIA Technologies, Inc. P4M890 Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. P4M890 Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. P4M890 Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. P4M890 Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. P4M890 Host Bridge
00:00.5 PIC: VIA Technologies, Inc. P4M890 I/O APIC Interrupt Controller
00:00.6 Host bridge: VIA Technologies, Inc. P4M890 Security Device
00:00.7 Host bridge: VIA Technologies, Inc. P4M890 Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge
00:02.0 PCI bridge: VIA Technologies, Inc. P4M890 PCI to PCI Bridge Controller
00:03.0 PCI bridge: VIA Technologies, Inc. P4M890 PCI to PCI Bridge Controller
00:0f.0 IDE interface: VIA Technologies, Inc. VT8237A SATA 2-Port Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev a0)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237A PCI to ISA Bridge
00:11.7 Host bridge: VIA Technologies, Inc. VT8251 Ultra VLINK Controller
00:13.0 PCI bridge: VIA Technologies, Inc. VT8237A Host Bridge
00:13.1 PCI bridge: VIA Technologies, Inc. VT8237A PCI to PCI Bridge
02:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8400 GS] (rev a1)
04:01.0 Audio device: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (rev 10)
05:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

hwinfo --framebuffer:
Code:

02: None 00.0: 11001 VESA Framebuffer
  [Created at bios.464]
  Unique ID: rdCR.p2HAKYrCCp1
  Hardware Class: framebuffer
  Model: "NVIDIA G86 Board - p413h04 "
  Vendor: "NVIDIA Corporation"
  Device: "G86 Board - p413h04 "
  SubVendor: "NVIDIA"
  SubDevice:
  Revision: "Chip Rev"
  Memory Size: 14 MB
  Memory Range: 0xfb000000-0xfbdfffff (rw)
  Mode 0x0300: 640x400 (+640), 8 bits
  Mode 0x0301: 640x480 (+640), 8 bits
  Mode 0x0303: 800x600 (+800), 8 bits
  Mode 0x0305: 1024x768 (+1024), 8 bits
  Mode 0x0307: 1280x1024 (+1280), 8 bits
  Mode 0x030e: 320x200 (+640), 16 bits
  Mode 0x030f: 320x200 (+1280), 24 bits
  Mode 0x0311: 640x480 (+1280), 16 bits
  Mode 0x0312: 640x480 (+2560), 24 bits
  Mode 0x0314: 800x600 (+1600), 16 bits
  Mode 0x0315: 800x600 (+3200), 24 bits
  Mode 0x0317: 1024x768 (+2048), 16 bits
  Mode 0x0318: 1024x768 (+4096), 24 bits
  Mode 0x031a: 1280x1024 (+2560), 16 bits
  Mode 0x031b: 1280x1024 (+5120), 24 bits
  Mode 0x0330: 320x200 (+320), 8 bits
  Mode 0x0331: 320x400 (+320), 8 bits
  Mode 0x0332: 320x400 (+640), 16 bits
  Mode 0x0333: 320x400 (+1280), 24 bits
  Mode 0x0334: 320x240 (+320), 8 bits
  Mode 0x0335: 320x240 (+640), 16 bits
  Mode 0x0336: 320x240 (+1280), 24 bits
  Mode 0x033d: 640x400 (+1280), 16 bits
  Mode 0x033e: 640x400 (+2560), 24 bits
  Mode 0x0345: 1600x1200 (+1600), 8 bits
  Mode 0x0346: 1600x1200 (+3200), 16 bits
  Mode 0x0347: 1400x1050 (+1400), 8 bits
  Mode 0x0348: 1400x1050 (+2800), 16 bits
  Mode 0x0349: 1400x1050 (+5600), 24 bits
  Mode 0x034a: 1600x1200 (+6400), 24 bits
  Mode 0x0352: 2048x1536 (+8192), 24 bits
  Mode 0x0360: 1280x800 (+1280), 8 bits
  Mode 0x0361: 1280x800 (+5120), 24 bits
  Mode 0x0362: 768x480 (+768), 8 bits
  Mode 0x0364: 1440x900 (+1440), 8 bits
  Mode 0x0365: 1440x900 (+5760), 24 bits
  Mode 0x0368: 1680x1050 (+1680), 8 bits
  Mode 0x0369: 1680x1050 (+6720), 24 bits
  Mode 0x037c: 1920x1200 (+1920), 8 bits
  Mode 0x037d: 1920x1200 (+7680), 24 bits
  Config Status: cfg=new, avail=yes, need=no, active=unknown


Last edited by RichardGv on Fri Jul 30, 2010 2:54 pm; edited 2 times in total
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2511
Location: Canada

PostPosted: Fri Jul 30, 2010 6:39 am    Post subject: Reply with quote

I though the kernel option is video=vesafb:vga=0x365 to use vesafb ?

At least that is what I am using :)
Back to top
View user's profile Send private message
RichardGv
n00b
n00b


Joined: 26 Jan 2010
Posts: 43
Location: People's Republic of China

PostPosted: Fri Jul 30, 2010 9:46 am    Post subject: Reply with quote

dmpogo wrote:
I though the kernel option is video=vesafb:vga=0x365 to use vesafb ?

At least that is what I am using :)


Unfortunately, the trick did not work for me:
Code:

Jul 30 17:13:32 [kernel] [    0.000000] Kernel command line: root=/dev/sda3 video=vesafb:vga=0x365
Jul 30 17:13:32 [kernel] [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 30 17:13:32 [kernel] [    0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Jul 30 17:13:32 [kernel] [    0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 30 17:13:32 [kernel] [    0.000000] Subtract (41 early reservations)
...
Jul 30 17:13:32 [kernel] [    0.000000] Memory: 1025140k/1048320k available (3808k kernel code, 452k absent, 22728k reserved, 1840k data, 424k init)
Jul 30 17:13:32 [kernel] [    0.000000] Experimental preemptable hierarchical RCU implementation.
Jul 30 17:13:32 [kernel] [    0.000000] NR_IRQS:320
Jul 30 17:13:32 [kernel] [    0.000000] Console: colour VGA+ 80x25
Jul 30 17:13:32 [kernel] [    0.000000] console [tty0] enabled
Jul 30 17:13:32 [kernel] [    0.000000] Fast TSC calibration using PIT
...

I tried "video=vesafb:mtrr:2,ywrap vga=0x365", but it did not work, either.
Code:

Jul 30 17:03:04 [kernel] [    0.000000] Linux version 2.6.34-zen1 (root@home) (gcc version 4.4.4 (Gentoo 4.4.4-r1 p1.0, pie-0.4.5) ) #2 ZEN SMP PREEMPT Thu Jul 29 21:08:44 CST 2010
Jul 30 17:03:04 [kernel] [    0.000000] Command line: root=/dev/sda3 video=vesafb:mtrr:2,ywrap vga=0x365
Jul 30 17:03:04 [kernel] [    0.000000] BIOS-provided physical RAM map:
...
Jul 30 17:03:04 [kernel] [    0.000000] Memory: 1025140k/1048320k available (3808k kernel code, 452k absent, 22728k reserved, 1840k data, 424k init)
Jul 30 17:03:04 [kernel] [    0.000000] Experimental preemptable hierarchical RCU implementation.
Jul 30 17:03:04 [kernel] [    0.000000] NR_IRQS:320
Jul 30 17:03:04 [kernel] [    0.000000] Console: colour VGA+ 80x25
Jul 30 17:03:04 [kernel] [    0.000000] console [tty0] enabled

Also, GRUB is constantly notifying me "Undefined video mode: 0x365".
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2511
Location: Canada

PostPosted: Fri Jul 30, 2010 2:13 pm    Post subject: Reply with quote

Are vesafb support and 'console on framebuffer' option compiled in the kernel ? I would assume the first yes, but the second one ( CONFIG_FRAMEBUFFER_CONSOLE=y ) ?
Back to top
View user's profile Send private message
RichardGv
n00b
n00b


Joined: 26 Jan 2010
Posts: 43
Location: People's Republic of China

PostPosted: Fri Jul 30, 2010 2:53 pm    Post subject: Reply with quote

dmpogo wrote:
Is vesafb support and 'console on framebuffer' option compiled in the kernel ?


Yes, I believe they are:
Code:

CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FB_VESA=y

And actually some VESA modes work correctly, but 0x0365 does not.
This is the whole configuration file of my kernel: http://pastebin.com/zdCdDVYC
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2511
Location: Canada

PostPosted: Fri Jul 30, 2010 4:17 pm    Post subject: Reply with quote

Hm, I looked more accurately at what I have in the command line

and it is

video=vesafb, vga=0x361

with comma, rather than colon. Try that
Back to top
View user's profile Send private message
Anon-E-moose
Advocate
Advocate


Joined: 23 May 2008
Posts: 3836
Location: Dallas area

PostPosted: Fri Jul 30, 2010 9:49 pm    Post subject: Reply with quote

Well, a couple of things

1. this is from my kernel line
Code:
kernel /boot/kernel-2.6.34-zen0 root=/dev/sda3 vga=792 video=vesafb:mtrr:3,ywrap iommu....


2. not every vesa mode will work, don't know why, but some that should work with my system don't.
_________________
Asus m5a99fx, FX 8320 - nouveau, oss4, rx550 for qemu passthrough
Acer laptop E5-575, i3-7100u - i965, alsa
---both---
5.0.13 zen kernel, profile 17.0 (no-pie) amd64-no-multilib
gcc 8.2.0, eudev, openrc, openbox, palemoon
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2511
Location: Canada

PostPosted: Fri Jul 30, 2010 9:57 pm    Post subject: Reply with quote

Anon-E-moose wrote:

2. not every vesa mode will work, don't know why, but some that should work with my system don't.



Yes, support for VESA modes besides standard is very card dependent, but one would think that ones that are shown by hwinfo --framebuffer are supported ?
(I never had example to the contrary)
Back to top
View user's profile Send private message
Gusar
Advocate
Advocate


Joined: 09 Apr 2005
Posts: 2664
Location: Slovenia

PostPosted: Fri Jul 30, 2010 10:54 pm    Post subject: Reply with quote

dmpogo wrote:
Yes, support for VESA modes besides standard is very card dependent, but one would think that ones that are shown by hwinfo --framebuffer are supported ?

I too think those should be supported. A question: have you tried uvesafb?
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2511
Location: Canada

PostPosted: Sat Jul 31, 2010 12:31 am    Post subject: Reply with quote

Gusar wrote:
dmpogo wrote:
Yes, support for VESA modes besides standard is very card dependent, but one would think that ones that are shown by hwinfo --framebuffer are supported ?

I too think those should be supported. A question: have you tried uvesafb?


No, I found suitable vesafb modes for all my 3 nvidia cards and one intel. All 4 computers are with wide-screen displays. Intel laptop has 1440x900 native resolution mode,
old Nvidia Quadro did not have anything above 1600x1200, but there was something widscreen at lower resolution,
Geforce 8500GT has full selection - all widescreens up to 1920x1200 (I needed 1680x1050 which was there), and new Geforce 240 has a very skimpy selection - only
up to 1600x1200 and the only widescreen mode - 1280x800, which is the one I am running now on my 1920x1200 display.

But whatever hwinfo --framebuffer showed, those I always had working
Back to top
View user's profile Send private message
RichardGv
n00b
n00b


Joined: 26 Jan 2010
Posts: 43
Location: People's Republic of China

PostPosted: Sat Jul 31, 2010 2:33 am    Post subject: Reply with quote

Thanks for all the replies firstly.
I know the nonstandard modes largely depend on the graphic card. However, since VESA mode 0x365 is listed in the output of hwinfo --framebuffer, it should work -- however it does not.
I tried "vga=ask" too, but looks like it listed only the standard modes (640x480, 800x600, 1024x768, 1280x1024, 1600x1200, etc.), but the nonstandard widescreen modes disappeared. The modes listed when using "vga=ask" do work correctly.
I did not try uvesafb because it's harder to set up and I'm afraid the initramfs it uses will affect my boot speed.

dmpogo wrote:
Hm, I looked more accurately at what I have in the command line

and it is

video=vesafb, vga=0x361

with comma, rather than colon. Try that


Well, it did not make any difference, either:
Code:

Jul 31 10:18:41 [kernel] [    0.000000] Kernel command line: root=/dev/sda3 video=vesafb, vga=0x365
Jul 31 10:18:41 [kernel] [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 31 10:18:41 [kernel] [    0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Jul 31 10:18:41 [kernel] [    0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 31 10:18:41 [kernel] [    0.000000] Subtract (41 early reservations)
...
Jul 31 10:18:41 [kernel] [    0.000000] Memory: 1025140k/1048320k available (3808k kernel code, 452k absent, 22728k reserved, 1840k data, 424k init)
Jul 31 10:18:41 [kernel] [    0.000000] Experimental preemptable hierarchical RCU implementation.
Jul 31 10:18:41 [kernel] [    0.000000] NR_IRQS:320
Jul 31 10:18:41 [kernel] [    0.000000] Console: colour VGA+ 80x25
Jul 31 10:18:41 [kernel] [    0.000000] console [tty0] enabled
Jul 31 10:18:41 [kernel] [    0.000000] Fast TSC calibration using PIT
..
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2511
Location: Canada

PostPosted: Sat Jul 31, 2010 2:40 am    Post subject: Reply with quote

So there is no trace of any attempt to even setup framebuffer in dmesg ?

Could you look at dmesg | grep vesafb ?

BTW, could also check with other modes that work, that vesafb is loaded ?
Back to top
View user's profile Send private message
RichardGv
n00b
n00b


Joined: 26 Jan 2010
Posts: 43
Location: People's Republic of China

PostPosted: Sat Jul 31, 2010 4:53 am    Post subject: Reply with quote

dmpogo wrote:
So there is no trace of any attempt to even setup framebuffer in dmesg ?

Could you look at dmesg | grep vesafb ?

BTW, could also check with other modes that work, that vesafb is loaded ?


dmesg shows nothing about loading of vesafb, if I use vga=0x365:
Code:
$ fgrep vesafb /var/log/dmesg
[    0.000000] Command line: root=/dev/sda3 video=vesafb, vga=0x365
[    0.000000] Kernel command line: root=/dev/sda3 video=vesafb, vga=0x365

I did not enable Direct Rendering Manager in the kernel (largely because I don't know what it is used for). It does not affect vesafb, does it?

And it looks like I'm not the only person stuck in it. Somebody met the same issue, and they said it's probably related to a BIOS limitation:
https://bbs.archlinux.org/viewtopic.php?pid=473707#p473707
https://forums.gentoo.org/viewtopic-t-649511-highlight-uvesafb.html
(Looks like uvesafb will be affected, as well.)

With a working VESA mode, kernel logs showed vesafb is loaded correctly:
(In this example I changed the VESA mode to 1024x768 when GRUB (or the kernel?) complained "undefined mode number", so the "Command line" was somehow not correct.)
Code:

Jul 30 10:43:28 [kernel] [    0.000000] Linux version 2.6.34-zen1 (root@home) (gcc version 4.4.4 (Gentoo 4.4.4-r1 p1.0, pie-0.4.5) ) #2 ZEN SMP PREEMPT Thu Jul 29 21:08:44 CST 2010
Jul 30 10:43:29 [kernel] [    0.000000] Command line: root=/dev/sda3 vga=0x365
Jul 30 10:43:29 [kernel] [    0.000000] BIOS-provided physical RAM map:
Jul 30 10:43:29 [kernel] [    0.000000]  BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
Jul 30 10:43:29 [kernel] [    0.000000]  BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
Jul 30 10:43:29 [kernel] [    0.000000]  BIOS-e820: 00000000000e7000 - 0000000000100000 (reserved)
Jul 30 10:43:29 [kernel] [    0.000000]  BIOS-e820: 0000000000100000 - 000000003ffc0000 (usable)
Jul 30 10:43:29 [kernel] [    0.000000]  BIOS-e820: 000000003ffc0000 - 000000003ffce000 (ACPI data)
Jul 30 10:43:29 [kernel] [    0.000000]  BIOS-e820: 000000003ffce000 - 000000003fff0000 (ACPI NVS)
Jul 30 10:43:29 [kernel] [    0.000000]  BIOS-e820: 000000003fff0000 - 0000000040000000 (reserved)
Jul 30 10:43:29 [kernel] [    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
Jul 30 10:43:29 [kernel] [    0.000000]  BIOS-e820: 00000000fecc0000 - 00000000fecc1000 (reserved)
Jul 30 10:43:29 [kernel] [    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
Jul 30 10:43:29 [kernel] [    0.000000]  BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved)
Jul 30 10:43:29 [kernel] [    0.000000] NX (Execute Disable) protection: active
Jul 30 10:43:29 [kernel] [    0.000000] DMI present.
Jul 30 10:43:29 [kernel] [    0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it.
Jul 30 10:43:29 [kernel] [    0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
Jul 30 10:43:29 [kernel] [    0.000000] e820 update range: 0000000000000000 - 0000000000001000 (usable) ==> (reserved)
Jul 30 10:43:29 [kernel] [    0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
Jul 30 10:43:29 [kernel] [    0.000000] last_pfn = 0x3ffc0 max_arch_pfn = 0x400000000
Jul 30 10:43:29 [kernel] [    0.000000] MTRR default type: uncachable
Jul 30 10:43:29 [kernel] [    0.000000] MTRR fixed ranges enabled:
Jul 30 10:43:29 [kernel] [    0.000000]   00000-9FFFF write-back
Jul 30 10:43:29 [kernel] [    0.000000]   A0000-DFFFF uncachable
Jul 30 10:43:29 [kernel] [    0.000000]   E0000-EFFFF write-through
Jul 30 10:43:29 [kernel] [    0.000000]   F0000-FFFFF write-protect
Jul 30 10:43:29 [kernel] [    0.000000] MTRR variable ranges enabled:
Jul 30 10:43:29 [kernel] [    0.000000]   0 base 000000000 mask FC0000000 write-back
Jul 30 10:43:29 [kernel] [    0.000000]   1 disabled
Jul 30 10:43:29 [kernel] [    0.000000]   2 disabled
Jul 30 10:43:29 [kernel] [    0.000000]   3 disabled
Jul 30 10:43:29 [kernel] [    0.000000]   4 disabled
Jul 30 10:43:29 [kernel] [    0.000000]   5 disabled
Jul 30 10:43:29 [kernel] [    0.000000]   6 disabled
Jul 30 10:43:29 [kernel] [    0.000000]   7 disabled
Jul 30 10:43:29 [kernel] [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 30 10:43:29 [kernel] [    0.000000] initial memory mapped : 0 - 20000000
Jul 30 10:43:29 [kernel] [    0.000000] init_memory_mapping: 0000000000000000-000000003ffc0000
Jul 30 10:43:29 [kernel] [    0.000000]  0000000000 - 003fe00000 page 2M
Jul 30 10:43:29 [kernel] [    0.000000]  003fe00000 - 003ffc0000 page 4k
Jul 30 10:43:29 [kernel] [    0.000000] kernel direct mapping tables up to 3ffc0000 @ 12000-15000
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: RSDP 00000000000f8f50 00014 (v00 ACPIAM)
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: RSDT 000000003ffc0000 00038 (v01 FOUNDR FOUNDRPC 06000729 MSFT 00000097)
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: FACP 000000003ffc0200 00084 (v02 FOUNDR FOUNDRPC 06000729 MSFT 00000097)
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: DSDT 000000003ffc05d0 04971 (v01 FOUNDR FOUNDRPC 00000011 INTL 02002026)
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: FACS 000000003ffce000 00040
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: APIC 000000003ffc0390 00078 (v01 FOUNDR OEMAPIC  06000729 MSFT 00000097)
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: MCFG 000000003ffc0410 0003C (v01 FOUNDR OEMMCFG  06000729 MSFT 00000097)
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: SLIC 000000003ffc0450 00176 (v01 FOUNDR FOUNDRPC 06000729 MSFT 00000097)
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: OEMB 000000003ffce040 00061 (v01 FOUNDR AMI_OEM  06000729 MSFT 00000097)
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 30 10:43:29 [kernel] [    0.000000]  [ffffea0000000000-ffffea0000dfffff] PMD -> [ffff880002000000-ffff880002dfffff] on node 0
Jul 30 10:43:29 [kernel] [    0.000000] Zone PFN ranges:
Jul 30 10:43:29 [kernel] [    0.000000]   DMA      0x00000010 -> 0x00001000
Jul 30 10:43:29 [kernel] [    0.000000]   DMA32    0x00001000 -> 0x00100000
Jul 30 10:43:29 [kernel] [    0.000000]   Normal   empty
Jul 30 10:43:29 [kernel] [    0.000000] Movable zone start PFN for each node
Jul 30 10:43:29 [kernel] [    0.000000] early_node_map[2] active PFN ranges
Jul 30 10:43:29 [kernel] [    0.000000]     0: 0x00000010 -> 0x0000009f
Jul 30 10:43:29 [kernel] [    0.000000]     0: 0x00000100 -> 0x0003ffc0
Jul 30 10:43:29 [kernel] [    0.000000] On node 0 totalpages: 261967
Jul 30 10:43:29 [kernel] [    0.000000]   DMA zone: 56 pages used for memmap
Jul 30 10:43:29 [kernel] [    0.000000]   DMA32 zone: 254456 pages, LIFO batch:31
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: PM-Timer IO Port: 0x808
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
Jul 30 10:43:29 [kernel] [    0.000000] IOAPIC[0]: apic_id 2, version 3, address 0xfec00000, GSI 0-23
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: IOAPIC (id[0x03] address[0xfecc0000] gsi_base[24])
Jul 30 10:43:29 [kernel] [    0.000000] IOAPIC[1]: apic_id 3, version 3, address 0xfecc0000, GSI 24-47
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: IRQ0 used by override.
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: IRQ2 used by override.
Jul 30 10:43:29 [kernel] [    0.000000] ACPI: IRQ9 used by override.
Jul 30 10:43:29 [kernel] [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 30 10:43:29 [kernel] [    0.000000] 4 Processors exceeds NR_CPUS limit of 2
Jul 30 10:43:29 [kernel] [    0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs
Jul 30 10:43:29 [kernel] [    0.000000] nr_irqs_gsi: 48
Jul 30 10:43:29 [kernel] [    0.000000] Allocating PCI resources starting at 40000000 (gap: 40000000:bec00000)
Jul 30 10:43:29 [kernel] [    0.000000] setup_percpu: NR_CPUS:2 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:1
Jul 30 10:43:29 [kernel] [    0.000000] early_res array is doubled to 64 at [13000 - 137ff]
Jul 30 10:43:29 [kernel] [    0.000000] PERCPU: Embedded 26 pages/cpu @ffff880001800000 s74024 r8192 d24280 u1048576
Jul 30 10:43:29 [kernel] [    0.000000] pcpu-alloc: s74024 r8192 d24280 u1048576 alloc=1*2097152
Jul 30 10:43:29 [kernel] [    0.000000] pcpu-alloc: [0] 0 1
Jul 30 10:43:29 [kernel] [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 258383
Jul 30 10:43:29 [kernel] [    0.000000] Kernel command line: root=/dev/sda3 vga=0x365
Jul 30 10:43:29 [kernel] [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 30 10:43:29 [kernel] [    0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Jul 30 10:43:29 [kernel] [    0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 30 10:43:29 [kernel] [    0.000000] Subtract (41 early reservations)
Jul 30 10:43:29 [kernel] [    0.000000]   #1 [0001000000 - 0001667078]   TEXT DATA BSS
Jul 30 10:43:29 [kernel] [    0.000000]   #2 [000009fc00 - 0000100000]   BIOS reserved
Jul 30 10:43:29 [kernel] [    0.000000]   #3 [0001668000 - 00016680f1]             BRK
Jul 30 10:43:29 [kernel] [    0.000000]   #4 [0000010000 - 0000012000]      TRAMPOLINE
Jul 30 10:43:29 [kernel] [    0.000000]   #5 [0000012000 - 0000013000]         PGTABLE
Jul 30 10:43:29 [kernel] [    0.000000]   #6 [0001668100 - 0001669100]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #7 [0001667080 - 0001667100]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #8 [0001e6a000 - 0001e6b000]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #9 [0001e6b000 - 0001e6c000]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #10 [0002000000 - 0002e00000]        MEMMAP 0
Jul 30 10:43:29 [kernel] [    0.000000]   #11 [0001667100 - 0001667280]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #12 [0001669100 - 000166f100]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #13 [0001670000 - 0001671000]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #14 [0001667280 - 0001667306]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #15 [0001667340 - 00016675e0]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #16 [0001667600 - 0001667668]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #17 [0001667680 - 00016676e8]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #18 [0001667700 - 0001667768]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #19 [0001667780 - 00016677e8]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #20 [0001667800 - 0001667868]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #21 [0001667880 - 00016678e8]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #22 [0001667900 - 0001667968]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #23 [0001667980 - 00016679e8]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #24 [0001667a00 - 0001667a68]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #25 [0001667a80 - 0001667ae8]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #26 [0001667b00 - 0001667b68]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #27 [0001667b80 - 0001667b99]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #28 [0001667bc0 - 0001667bd9]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #33 [0001667c80 - 0001667c88]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #34 [0001667cc0 - 0001667cd0]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #35 [0001667d00 - 0001667e40]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #36 [0001667e40 - 0001667ea0]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #37 [0001667ec0 - 0001667f20]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #38 [0001671000 - 0001679000]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #39 [0001679000 - 0001779000]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000]   #40 [0001779000 - 00017f9000]         BOOTMEM
Jul 30 10:43:29 [kernel] [    0.000000] Memory: 1025140k/1048320k available (3808k kernel code, 452k absent, 22728k reserved, 1840k data, 424k init)
Jul 30 10:43:29 [kernel] [    0.000000] Experimental preemptable hierarchical RCU implementation.
Jul 30 10:43:29 [kernel] [    0.000000] NR_IRQS:320
Jul 30 10:43:29 [kernel] [    0.000000] Console: colour dummy device 80x25
Jul 30 10:43:29 [kernel] [    0.000000] console [tty0] enabled
Jul 30 10:43:29 [kernel] [    0.000000] Fast TSC calibration failed
Jul 30 10:43:29 [kernel] [    0.000000] TSC: PIT calibration matches PMTIMER. 1 loops
Jul 30 10:43:29 [kernel] [    0.000000] Detected 1596.012 MHz processor.
Jul 30 10:43:29 [kernel] [    0.002011] Calibrating delay loop (skipped), value calculated using timer frequency.. 3192.02 BogoMIPS (lpj=1596012)
Jul 30 10:43:29 [kernel] [    0.002067] Mount-cache hash table entries: 256
Jul 30 10:43:29 [kernel] [    0.002255] CPU: Physical Processor ID: 0
Jul 30 10:43:29 [kernel] [    0.002261] CPU: Processor Core ID: 0
Jul 30 10:43:29 [kernel] [    0.002267] mce: CPU supports 6 MCE banks
Jul 30 10:43:29 [kernel] [    0.003003] CPU0: Thermal monitoring enabled (TM2)
Jul 30 10:43:29 [kernel] [    0.003012] using mwait in idle threads.
Jul 30 10:43:29 [kernel] [    0.003016] Performance Events: Core2 events, Intel PMU driver.
Jul 30 10:43:29 [kernel] [    0.003032] ... version:                2
Jul 30 10:43:29 [kernel] [    0.003036] ... bit width:              40
Jul 30 10:43:29 [kernel] [    0.003041] ... generic registers:      2
Jul 30 10:43:29 [kernel] [    0.003046] ... value mask:             000000ffffffffff
Jul 30 10:43:29 [kernel] [    0.003051] ... max period:             000000007fffffff
Jul 30 10:43:29 [kernel] [    0.003056] ... fixed-purpose events:   3
Jul 30 10:43:29 [kernel] [    0.003060] ... event mask:             0000000700000003
Jul 30 10:43:29 [kernel] [    0.003114] Freeing SMP alternatives: 28k freed
Jul 30 10:43:29 [kernel] [    0.003152] ACPI: Core revision 20100121
Jul 30 10:43:29 [kernel] [    0.011589] Setting APIC routing to flat
Jul 30 10:43:29 [kernel] [    0.011999] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 30 10:43:29 [kernel] [    0.022140] CPU0: Genuine Intel(R) CPU            2140  @ 1.60GHz stepping 02
Jul 30 10:43:29 [kernel] [    0.022999] Booting Node   0, Processors  #1 Ok.
Jul 30 10:43:29 [kernel] [    0.094011] Brought up 2 CPUs
Jul 30 10:43:29 [kernel] [    0.094020] Total of 2 processors activated (6383.37 BogoMIPS).
Jul 30 10:43:29 [kernel] [    0.094362] NET: Registered protocol family 16
Jul 30 10:43:29 [kernel] [    0.095060] ACPI: bus type pci registered
Jul 30 10:43:29 [kernel] [    0.095060] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
Jul 30 10:43:29 [kernel] [    0.095060] PCI: not using MMCONFIG
Jul 30 10:43:29 [kernel] [    0.095060] PCI: Using configuration type 1 for base access
Jul 30 10:43:29 [kernel] [    0.099075] bio: create slab <bio-0> at 0
Jul 30 10:43:29 [kernel] [    0.101291] ACPI: EC: Look up EC in DSDT
Jul 30 10:43:29 [kernel] [    0.104173] ACPI: Executed 1 blocks of module-level executable AML code
Jul 30 10:43:29 [kernel] [    0.113870] ACPI Warning: Incorrect checksum in table [SSDT] - C5, should be CC (20100121/tbutils-314)
Jul 30 10:43:29 [kernel] [    0.113953] ACPI: SSDT 000000003ffc4f50 002E3 (v01    AMI   CPU1PM 00000001 INTL 20051117)
Jul 30 10:43:29 [kernel] [    0.114473] ACPI: SSDT 000000003ffc5240 002DA (v01    AMI   CPU2PM 00000001 INTL 20051117)
Jul 30 10:43:29 [kernel] [    0.114871] ACPI: Interpreter enabled
Jul 30 10:43:29 [kernel] [    0.114877] ACPI: (supports S0 S5)
Jul 30 10:43:29 [kernel] [    0.114891] ACPI: Using IOAPIC for interrupt routing
Jul 30 10:43:29 [kernel] [    0.114956] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
Jul 30 10:43:29 [kernel] [    0.118687] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
Jul 30 10:43:29 [kernel] [    0.184178] PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug
Jul 30 10:43:29 [kernel] [    0.184178] ACPI: PCI Root Bridge [PCI0] (0000:00)
Jul 30 10:43:29 [kernel] [    0.185261] pci_root PNP0A03:00: host bridge window [io  0x0000-0x0cf7] (ignored)
Jul 30 10:43:29 [kernel] [    0.185265] pci_root PNP0A03:00: host bridge window [io  0x0d00-0xffff] (ignored)
Jul 30 10:43:29 [kernel] [    0.185268] pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
Jul 30 10:43:29 [kernel] [    0.185271] pci_root PNP0A03:00: host bridge window [mem 0x000d0000-0x000dffff] (ignored)
Jul 30 10:43:29 [kernel] [    0.185311] pci 0000:00:00.0: reg 10: [mem 0xf0000000-0xf7ffffff pref]
Jul 30 10:43:29 [kernel] [    0.185938] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 30 10:43:29 [kernel] [    0.185943] pci 0000:00:02.0: PME# disabled
Jul 30 10:43:29 [kernel] [    0.186091] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 30 10:43:29 [kernel] [    0.186097] pci 0000:00:03.0: PME# disabled
Jul 30 10:43:29 [kernel] [    0.186171] pci 0000:00:0f.0: reg 10: [io  0xec00-0xec07]
Jul 30 10:43:29 [kernel] [    0.186179] pci 0000:00:0f.0: reg 14: [io  0xe880-0xe883]
Jul 30 10:43:29 [kernel] [    0.186187] pci 0000:00:0f.0: reg 18: [io  0xe800-0xe807]
Jul 30 10:43:29 [kernel] [    0.186195] pci 0000:00:0f.0: reg 1c: [io  0xe480-0xe483]
Jul 30 10:43:29 [kernel] [    0.186203] pci 0000:00:0f.0: reg 20: [io  0xe400-0xe40f]
Jul 30 10:43:29 [kernel] [    0.186211] pci 0000:00:0f.0: reg 24: [io  0xe000-0xe0ff]
Jul 30 10:43:29 [kernel] [    0.186295] pci 0000:00:0f.1: reg 20: [io  0xfc00-0xfc0f]
Jul 30 10:43:29 [kernel] [    0.186394] pci 0000:00:10.0: reg 20: [io  0xdc00-0xdc1f]
Jul 30 10:43:29 [kernel] [    0.186427] pci 0000:00:10.0: supports D1 D2
Jul 30 10:43:29 [kernel] [    0.186429] pci 0000:00:10.0: PME# supported from D0 D1 D2 D3hot D3cold
Jul 30 10:43:29 [kernel] [    0.186434] pci 0000:00:10.0: PME# disabled
Jul 30 10:43:29 [kernel] [    0.186490] pci 0000:00:10.1: reg 20: [io  0xd880-0xd89f]
Jul 30 10:43:29 [kernel] [    0.186522] pci 0000:00:10.1: supports D1 D2
Jul 30 10:43:29 [kernel] [    0.186525] pci 0000:00:10.1: PME# supported from D0 D1 D2 D3hot D3cold
Jul 30 10:43:29 [kernel] [    0.186530] pci 0000:00:10.1: PME# disabled
Jul 30 10:43:29 [kernel] [    0.186585] pci 0000:00:10.2: reg 20: [io  0xd800-0xd81f]
Jul 30 10:43:29 [kernel] [    0.186618] pci 0000:00:10.2: supports D1 D2
Jul 30 10:43:29 [kernel] [    0.186620] pci 0000:00:10.2: PME# supported from D0 D1 D2 D3hot D3cold
Jul 30 10:43:29 [kernel] [    0.186625] pci 0000:00:10.2: PME# disabled
Jul 30 10:43:29 [kernel] [    0.186680] pci 0000:00:10.3: reg 20: [io  0xd480-0xd49f]
Jul 30 10:43:29 [kernel] [    0.186713] pci 0000:00:10.3: supports D1 D2
Jul 30 10:43:29 [kernel] [    0.186715] pci 0000:00:10.3: PME# supported from D0 D1 D2 D3hot D3cold
Jul 30 10:43:29 [kernel] [    0.186720] pci 0000:00:10.3: PME# disabled
Jul 30 10:43:29 [kernel] [    0.186754] pci 0000:00:10.4: reg 10: [mem 0xfebffc00-0xfebffcff]
Jul 30 10:43:29 [kernel] [    0.186808] pci 0000:00:10.4: supports D1 D2
Jul 30 10:43:29 [kernel] [    0.186810] pci 0000:00:10.4: PME# supported from D0 D1 D2 D3hot D3cold
Jul 30 10:43:29 [kernel] [    0.186815] pci 0000:00:10.4: PME# disabled
Jul 30 10:43:29 [kernel] [    0.187257] pci 0000:00:01.0: PCI bridge to [bus 01-01]
Jul 30 10:43:29 [kernel] [    0.187267] pci 0000:00:01.0:   bridge window [io  0xf000-0x0000] (disabled)
Jul 30 10:43:29 [kernel] [    0.187273] pci 0000:00:01.0:   bridge window [mem 0xfff00000-0x000fffff] (disabled)
Jul 30 10:43:29 [kernel] [    0.187278] pci 0000:00:01.0:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
Jul 30 10:43:29 [kernel] [    0.187364] pci 0000:02:00.0: reg 10: [mem 0xfd000000-0xfdffffff]
Jul 30 10:43:29 [kernel] [    0.187377] pci 0000:02:00.0: reg 14: [mem 0xc0000000-0xcfffffff 64bit pref]
Jul 30 10:43:29 [kernel] [    0.187390] pci 0000:02:00.0: reg 1c: [mem 0xfa000000-0xfbffffff 64bit]
Jul 30 10:43:29 [kernel] [    0.187398] pci 0000:02:00.0: reg 24: [io  0xbc00-0xbc7f]
Jul 30 10:43:29 [kernel] [    0.187405] pci 0000:02:00.0: reg 30: [mem 0xfe8e0000-0xfe8fffff pref]
Jul 30 10:43:29 [kernel] [    0.187450] pci 0000:00:02.0: PCI bridge to [bus 02-02]
Jul 30 10:43:29 [kernel] [    0.187458] pci 0000:00:02.0:   bridge window [io  0xb000-0xbfff]
Jul 30 10:43:29 [kernel] [    0.187463] pci 0000:00:02.0:   bridge window [mem 0xf8800000-0xfe8fffff]
Jul 30 10:43:29 [kernel] [    0.187470] pci 0000:00:02.0:   bridge window [mem 0xbff00000-0xdfefffff 64bit pref]
Jul 30 10:43:29 [kernel] [    0.187539] pci 0000:00:03.0: PCI bridge to [bus 03-03]
Jul 30 10:43:29 [kernel] [    0.187547] pci 0000:00:03.0:   bridge window [io  0xf000-0x0000] (disabled)
Jul 30 10:43:29 [kernel] [    0.187553] pci 0000:00:03.0:   bridge window [mem 0xfff00000-0x000fffff] (disabled)
Jul 30 10:43:29 [kernel] [    0.187561] pci 0000:00:03.0:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
Jul 30 10:43:29 [kernel] [    0.187631] pci 0000:04:01.0: reg 10: [mem 0xfe9fc000-0xfe9fffff 64bit]
Jul 30 10:43:29 [kernel] [    0.187684] pci 0000:04:01.0: PME# supported from D0 D3hot D3cold
Jul 30 10:43:29 [kernel] [    0.187688] pci 0000:04:01.0: PME# disabled
Jul 30 10:43:29 [kernel] [    0.187746] pci 0000:00:13.0: PCI bridge to [bus 04-04]
Jul 30 10:43:29 [kernel] [    0.187754] pci 0000:00:13.0:   bridge window [io  0xf000-0x0000] (disabled)
Jul 30 10:43:29 [kernel] [    0.187759] pci 0000:00:13.0:   bridge window [mem 0xfe900000-0xfe9fffff]
Jul 30 10:43:29 [kernel] [    0.187766] pci 0000:00:13.0:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
Jul 30 10:43:29 [kernel] [    0.187839] pci 0000:05:05.0: reg 10: [io  0xc800-0xc8ff]
Jul 30 10:43:29 [kernel] [    0.187847] pci 0000:05:05.0: reg 14: [mem 0xfeaffc00-0xfeaffcff]
Jul 30 10:43:29 [kernel] [    0.187897] pci 0000:05:05.0: supports D1 D2
Jul 30 10:43:29 [kernel] [    0.187904] pci 0000:05:05.0: PME# disabled
Jul 30 10:43:29 [kernel] [    0.187951] pci 0000:00:13.1: PCI bridge to [bus 05-05] (subtractive decode)
Jul 30 10:43:29 [kernel] [    0.187960] pci 0000:00:13.1:   bridge window [io  0xc000-0xcfff]
Jul 30 10:43:29 [kernel] [    0.187965] pci 0000:00:13.1:   bridge window [mem 0xfea00000-0xfeafffff]
Jul 30 10:43:29 [kernel] [    0.187973] pci 0000:00:13.1:   bridge window [mem 0xfff00000-0x000fffff pref] (disabled)
Jul 30 10:43:29 [kernel] [    0.187976] pci 0000:00:13.1:   bridge window [io  0x0000-0xffff] (subtractive decode)
Jul 30 10:43:29 [kernel] [    0.187979] pci 0000:00:13.1:   bridge window [mem 0x00000000-0xffffffffffffffff] (subtractive decode)
Jul 30 10:43:29 [kernel] [    0.188014] pci_bus 0000:00: on NUMA node 0
Jul 30 10:43:29 [kernel] [    0.188020] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Jul 30 10:43:29 [kernel] [    0.188192] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
Jul 30 10:43:29 [kernel] [    0.188248] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NBPG._PRT]
Jul 30 10:43:29 [kernel] [    0.188323] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.NBP0._PRT]
Jul 30 10:43:29 [kernel] [    0.188449] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P9._PRT]
Jul 30 10:43:29 [kernel] [    0.188510] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0PA._PRT]
Jul 30 10:43:29 [kernel] [    0.206129] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 10 11 12 14 15)
Jul 30 10:43:29 [kernel] [    0.206278] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 30 10:43:29 [kernel] [    0.206418] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 30 10:43:29 [kernel] [    0.207100] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 30 10:43:29 [kernel] [    0.207241] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 30 10:43:29 [kernel] [    0.207457] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 30 10:43:29 [kernel] [    0.207607] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 30 10:43:29 [kernel] [    0.207756] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 30 10:43:29 [kernel] [    0.208030] vgaarb: device added: PCI:0000:02:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 30 10:43:29 [kernel] [    0.208041] vgaarb: loaded
Jul 30 10:43:29 [kernel] [    0.208178] SCSI subsystem initialized
Jul 30 10:43:29 [kernel] [    0.208178] libata version 3.00 loaded.
Jul 30 10:43:29 [kernel] [    0.208178] usbcore: registered new interface driver usbfs
Jul 30 10:43:29 [kernel] [    0.208178] usbcore: registered new interface driver hub
Jul 30 10:43:29 [kernel] [    0.208178] usbcore: registered new device driver usb
Jul 30 10:43:29 [kernel] [    0.208178] Advanced Linux Sound Architecture Driver Version 1.0.22.1.
Jul 30 10:43:29 [kernel] [    0.208178] PCI: Using ACPI for IRQ routing
Jul 30 10:43:29 [kernel] [    0.208178] PCI: pci_cache_line_size set to 64 bytes
Jul 30 10:43:29 [kernel] [    0.208178] reserve RAM buffer: 000000000009fc00 - 000000000009ffff
Jul 30 10:43:29 [kernel] [    0.208178] reserve RAM buffer: 000000003ffc0000 - 000000003fffffff
Jul 30 10:43:29 [kernel] [    0.209086] Switching to clocksource tsc
Jul 30 10:43:29 [kernel] [    0.209435] pnp: PnP ACPI init
Jul 30 10:43:29 [kernel] [    0.209449] ACPI: bus type pnp registered
Jul 30 10:43:29 [kernel] [    0.218482] pnp: PnP ACPI: found 14 devices
Jul 30 10:43:29 [kernel] [    0.218490] ACPI: ACPI bus type pnp unregistered
Jul 30 10:43:29 [kernel] [    0.218510] system 00:06: [io  0x03e0-0x03e7] has been reserved
Jul 30 10:43:29 [kernel] [    0.218517] system 00:06: [io  0x04d0-0x04d1] has been reserved
Jul 30 10:43:29 [kernel] [    0.218525] system 00:06: [io  0x0800-0x087f] has been reserved
Jul 30 10:43:29 [kernel] [    0.218531] system 00:06: [io  0x0400-0x041f] has been reserved
Jul 30 10:43:29 [kernel] [    0.218539] system 00:06: [mem 0xff380000-0xff3fffff] has been reserved
Jul 30 10:43:29 [kernel] [    0.218550] system 00:08: [io  0x0a00-0x0a0f] has been reserved
Jul 30 10:43:29 [kernel] [    0.218556] system 00:08: [io  0x0a10-0x0a1f] has been reserved
Jul 30 10:43:29 [kernel] [    0.218563] system 00:08: [io  0x0a20-0x0a2f] has been reserved
Jul 30 10:43:29 [kernel] [    0.218569] system 00:08: [io  0x0a30-0x0a3f] has been reserved
Jul 30 10:43:29 [kernel] [    0.218580] system 00:09: [mem 0xfec00000-0xfec00fff] could not be reserved
Jul 30 10:43:29 [kernel] [    0.218587] system 00:09: [mem 0xfee00000-0xfee00fff] has been reserved
Jul 30 10:43:29 [kernel] [    0.218598] system 00:0c: [mem 0xe0000000-0xefffffff] has been reserved
Jul 30 10:43:29 [kernel] [    0.218609] system 00:0d: [mem 0x00000000-0x0009ffff] could not be reserved
Jul 30 10:43:29 [kernel] [    0.218616] system 00:0d: [mem 0x000c0000-0x000cffff] has been reserved
Jul 30 10:43:29 [kernel] [    0.218623] system 00:0d: [mem 0x000e0000-0x000fffff] could not be reserved
Jul 30 10:43:29 [kernel] [    0.218630] system 00:0d: [mem 0x00100000-0x3fffffff] could not be reserved
Jul 30 10:43:29 [kernel] [    0.218637] system 00:0d: [mem 0xff780000-0xffffffff] has been reserved
Jul 30 10:43:29 [kernel] [    0.223300] pci 0000:00:03.0: BAR 8: assigned [mem 0x40000000-0x401fffff]
Jul 30 10:43:29 [kernel] [    0.223310] pci 0000:00:03.0: BAR 9: assigned [mem 0x40200000-0x403fffff 64bit pref]
Jul 30 10:43:29 [kernel] [    0.223318] pci 0000:00:03.0: BAR 7: assigned [io  0x1000-0x1fff]
Jul 30 10:43:29 [kernel] [    0.223325] pci 0000:00:01.0: PCI bridge to [bus 01-01]
Jul 30 10:43:29 [kernel] [    0.223330] pci 0000:00:01.0:   bridge window [io  disabled]
Jul 30 10:43:29 [kernel] [    0.223340] pci 0000:00:01.0:   bridge window [mem disabled]
Jul 30 10:43:29 [kernel] [    0.223347] pci 0000:00:01.0:   bridge window [mem pref disabled]
Jul 30 10:43:29 [kernel] [    0.223359] pci 0000:00:02.0: PCI bridge to [bus 02-02]
Jul 30 10:43:29 [kernel] [    0.223366] pci 0000:00:02.0:   bridge window [io  0xb000-0xbfff]
Jul 30 10:43:29 [kernel] [    0.223375] pci 0000:00:02.0:   bridge window [mem 0xf8800000-0xfe8fffff]
Jul 30 10:43:29 [kernel] [    0.223384] pci 0000:00:02.0:   bridge window [mem 0xbff00000-0xdfefffff 64bit pref]
Jul 30 10:43:29 [kernel] [    0.223397] pci 0000:00:03.0: PCI bridge to [bus 03-03]
Jul 30 10:43:29 [kernel] [    0.223404] pci 0000:00:03.0:   bridge window [io  0x1000-0x1fff]
Jul 30 10:43:29 [kernel] [    0.223414] pci 0000:00:03.0:   bridge window [mem 0x40000000-0x401fffff]
Jul 30 10:43:29 [kernel] [    0.223423] pci 0000:00:03.0:   bridge window [mem 0x40200000-0x403fffff 64bit pref]
Jul 30 10:43:29 [kernel] [    0.223437] pci 0000:00:13.0: PCI bridge to [bus 04-04]
Jul 30 10:43:29 [kernel] [    0.223442] pci 0000:00:13.0:   bridge window [io  disabled]
Jul 30 10:43:29 [kernel] [    0.223451] pci 0000:00:13.0:   bridge window [mem 0xfe900000-0xfe9fffff]
Jul 30 10:43:29 [kernel] [    0.223460] pci 0000:00:13.0:   bridge window [mem pref disabled]
Jul 30 10:43:29 [kernel] [    0.223471] pci 0000:00:13.1: PCI bridge to [bus 05-05]
Jul 30 10:43:29 [kernel] [    0.223478] pci 0000:00:13.1:   bridge window [io  0xc000-0xcfff]
Jul 30 10:43:29 [kernel] [    0.223487] pci 0000:00:13.1:   bridge window [mem 0xfea00000-0xfeafffff]
Jul 30 10:43:29 [kernel] [    0.223495] pci 0000:00:13.1:   bridge window [mem pref disabled]
Jul 30 10:43:29 [kernel] [    0.223520] pci 0000:00:01.0: setting latency timer to 64
Jul 30 10:43:29 [kernel] [    0.223535] pci 0000:00:02.0: PCI INT A -> GSI 27 (level, low) -> IRQ 27
Jul 30 10:43:29 [kernel] [    0.223544] pci 0000:00:02.0: setting latency timer to 64
Jul 30 10:43:29 [kernel] [    0.223554] pci 0000:00:03.0: enabling device (0104 -> 0107)
Jul 30 10:43:29 [kernel] [    0.223564] pci 0000:00:03.0: PCI INT A -> GSI 31 (level, low) -> IRQ 31
Jul 30 10:43:29 [kernel] [    0.223573] pci 0000:00:03.0: setting latency timer to 64
Jul 30 10:43:29 [kernel] [    0.223581] pci 0000:00:13.0: setting latency timer to 64
Jul 30 10:43:29 [kernel] [    0.223589] pci 0000:00:13.1: setting latency timer to 64
Jul 30 10:43:29 [kernel] [    0.223594] pci_bus 0000:00: resource 0 [io  0x0000-0xffff]
Jul 30 10:43:29 [kernel] [    0.223596] pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffffffffffff]
Jul 30 10:43:29 [kernel] [    0.223600] pci_bus 0000:02: resource 0 [io  0xb000-0xbfff]
Jul 30 10:43:29 [kernel] [    0.223602] pci_bus 0000:02: resource 1 [mem 0xf8800000-0xfe8fffff]
Jul 30 10:43:29 [kernel] [    0.223605] pci_bus 0000:02: resource 2 [mem 0xbff00000-0xdfefffff 64bit pref]
Jul 30 10:43:29 [kernel] [    0.223608] pci_bus 0000:03: resource 0 [io  0x1000-0x1fff]
Jul 30 10:43:29 [kernel] [    0.223610] pci_bus 0000:03: resource 1 [mem 0x40000000-0x401fffff]
Jul 30 10:43:29 [kernel] [    0.223613] pci_bus 0000:03: resource 2 [mem 0x40200000-0x403fffff 64bit pref]
Jul 30 10:43:29 [kernel] [    0.223616] pci_bus 0000:04: resource 1 [mem 0xfe900000-0xfe9fffff]
Jul 30 10:43:29 [kernel] [    0.223619] pci_bus 0000:05: resource 0 [io  0xc000-0xcfff]
Jul 30 10:43:29 [kernel] [    0.223621] pci_bus 0000:05: resource 1 [mem 0xfea00000-0xfeafffff]
Jul 30 10:43:29 [kernel] [    0.223624] pci_bus 0000:05: resource 4 [io  0x0000-0xffff]
Jul 30 10:43:29 [kernel] [    0.223626] pci_bus 0000:05: resource 5 [mem 0x00000000-0xffffffffffffffff]
Jul 30 10:43:29 [kernel] [    0.223669] NET: Registered protocol family 2
Jul 30 10:43:29 [kernel] [    0.223741] IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
Jul 30 10:43:29 [kernel] [    0.224038] TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
Jul 30 10:43:29 [kernel] [    0.226856] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 30 10:43:29 [kernel] [    0.228696] TCP: Hash tables configured (established 131072 bind 65536)
Jul 30 10:43:29 [kernel] [    0.228712] TCP reno registered
Jul 30 10:43:29 [kernel] [    0.228723] UDP hash table entries: 512 (order: 2, 16384 bytes)
Jul 30 10:43:29 [kernel] [    0.228759] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
Jul 30 10:43:29 [kernel] [    0.228977] NET: Registered protocol family 1
Jul 30 10:43:29 [kernel] [    0.229040] pci 0000:00:01.0: disabling DAC on VIA PCI bridge
Jul 30 10:43:29 [kernel] [    0.229188] pci 0000:02:00.0: Boot video device
Jul 30 10:43:29 [kernel] [    0.229199] PCI: CLS 32 bytes, default 64
Jul 30 10:43:29 [kernel] [    0.230582] Intel AES-NI instructions are not detected.
Jul 30 10:43:29 [kernel] [    0.231309] msgmni has been set to 2002
Jul 30 10:43:29 [kernel] [    0.232162] alg: No test for fcrypt (fcrypt-generic)
Jul 30 10:43:29 [kernel] [    0.234368] alg: No test for lzf (lzf-generic)
Jul 30 10:43:29 [kernel] [    0.234450] alg: No test for stdrng (krng)
Jul 30 10:43:29 [kernel] [    0.240772] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
Jul 30 10:43:29 [kernel] [    0.240783] io scheduler noop registered
Jul 30 10:43:29 [kernel] [    0.240796] io scheduler bfq registered (default)
Jul 30 10:43:29 [kernel] [    0.240949] pcieport 0000:00:02.0: setting latency timer to 64
Jul 30 10:43:29 [kernel] [    0.241016] pcieport 0000:00:02.0: irq 48 for MSI/MSI-X
Jul 30 10:43:29 [kernel] [    0.241244] pcieport 0000:00:03.0: setting latency timer to 64
Jul 30 10:43:29 [kernel] [    0.241313] pcieport 0000:00:03.0: irq 49 for MSI/MSI-X
Jul 30 10:43:29 [kernel] [    0.244898] Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds).
Jul 30 10:43:29 [kernel] [    0.244910] Hangcheck: Using get_cycles().
Jul 30 10:43:29 [kernel] [    0.246462] vesafb: framebuffer at 0xfb000000, mapped to 0xffffc90010180000, using 6144k, total 14336k
Jul 30 10:43:29 [kernel] [    0.246473] vesafb: mode is 1024x768x32, linelength=4096, pages=1
Jul 30 10:43:29 [kernel] [    0.246479] vesafb: scrolling: redraw
Jul 30 10:43:29 [kernel] [    0.246485] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 30 10:43:29 [kernel] [    0.270588] Console: switching to colour frame buffer device 128x48
Jul 30 10:43:29 [kernel] [    0.294822] fb0: VESA VGA frame buffer device
...
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2511
Location: Canada

PostPosted: Sat Jul 31, 2010 5:43 am    Post subject: Reply with quote

Hm,

Direct Rendering Manager does not affect framebuffer. It is for 3D accelerated stuff, needed if you use in-kernel drivers for that. If one uses proprietary nvidia drives then it should be disabled.
I have it disabled because of that
Back to top
View user's profile Send private message
RichardGv
n00b
n00b


Joined: 26 Jan 2010
Posts: 43
Location: People's Republic of China

PostPosted: Tue Aug 03, 2010 12:47 pm    Post subject: Reply with quote

Here's some updates:

  1. I tried using vbespy to detect the available VESA modes again. The result it returned was basically the same as what hwinfo returned.
    Code:

    $ ./vbetest 2> /dev/null
    [256] 640x400 (256 color palette)
    [257] 640x480 (256 color palette)
    [259] 800x600 (256 color palette)
    [261] 1024x768 (256 color palette)
    [263] 1280x1024 (256 color palette)
    [270] 320x200 (5:6:5)
    [271] 320x200 (8:8:8)
    [273] 640x480 (5:6:5)
    [274] 640x480 (8:8:8)
    [276] 800x600 (5:6:5)
    [277] 800x600 (8:8:8)
    [279] 1024x768 (5:6:5)
    [280] 1024x768 (8:8:8)
    [282] 1280x1024 (5:6:5)
    [283] 1280x1024 (8:8:8)
    [304] 320x200 (256 color palette)
    [305] 320x400 (256 color palette)
    [306] 320x400 (5:6:5)
    [307] 320x400 (8:8:8)
    [308] 320x240 (256 color palette)
    [309] 320x240 (5:6:5)
    [310] 320x240 (8:8:8)
    [317] 640x400 (5:6:5)
    [318] 640x400 (8:8:8)
    [325] 1600x1200 (256 color palette)
    [326] 1600x1200 (5:6:5)
    [327] 1400x1050 (256 color palette)
    [328] 1400x1050 (5:6:5)
    [329] 1400x1050 (8:8:8)
    [330] 1600x1200 (8:8:8)
    [338] 2048x1536 (8:8:8)
    [352] 1280x800 (256 color palette)
    [353] 1280x800 (8:8:8)
    [354] 768x480 (256 color palette)
    [356] 1440x900 (256 color palette)
    [357] 1440x900 (8:8:8)
    [360] 1680x1050 (256 color palette)
    [361] 1680x1050 (8:8:8)
    [380] 1920x1200 (256 color palette)
    [381] 1920x1200 (8:8:8)

  2. Meanwhile I reverted back to GRUB 2 ( sys-boot/grub-1.98 ). The vbeinfo in GRUB 2 fails to detect the additional VESA modes. Its output ends at 1600x1200. GRUB 2 cannot correctly make use of the nonstandard modes, either. (If I try to use gfxmode=1440x900x24, my monitor will complain "input out of range". Of course, the standard modes work just as expected.)
  3. There's a detail that I forgot: The minimal installation CD can use a 1440x900 framebuffer on my computer. Does it utilize nouveau to do this? I know I should have somehow try to find it out myself, but the ISO image of minimal installation CD of amd64 is not available right now, and I don't have a CD image at hand.
Back to top
View user's profile Send private message
dmpogo
Advocate
Advocate


Joined: 02 Sep 2004
Posts: 2511
Location: Canada

PostPosted: Tue Aug 03, 2010 3:08 pm    Post subject: Reply with quote

Yes, I realised the vbespy (which I always used) and hwinfo give the same modes, the advantage is that hwinfo give alrady vesa codes, while with vbespy you need to recalculate them. I don't think noveau or any other drivers have anything to do framebuffer, but I may be mistaken. I though for framebuffer you have vesa, uvesa, some card specific drivers (usually poorly maintained) and KMS. It is so much looks like your kernel is compiled differently
Back to top
View user's profile Send private message
Anon-E-moose
Advocate
Advocate


Joined: 23 May 2008
Posts: 3836
Location: Dallas area

PostPosted: Tue Aug 03, 2010 4:04 pm    Post subject: Reply with quote

KMS in Nouveau is supported and actually the only way to go. It automatically offers nouveaufb, an integrated (into the DRM driver) framebuffer driver for the virtual console. Most notably this gives you a high resolution text console. More information about framebuffer console is in Documentation/fb/fbcon.txt. KMS and nouveaufb are inseparable.

from http://nouveau.freedesktop.org/wiki/KernelModeSetting
_________________
Asus m5a99fx, FX 8320 - nouveau, oss4, rx550 for qemu passthrough
Acer laptop E5-575, i3-7100u - i965, alsa
---both---
5.0.13 zen kernel, profile 17.0 (no-pie) amd64-no-multilib
gcc 8.2.0, eudev, openrc, openbox, palemoon
Back to top
View user's profile Send private message
RichardGv
n00b
n00b


Joined: 26 Jan 2010
Posts: 43
Location: People's Republic of China

PostPosted: Sat Aug 07, 2010 10:34 am    Post subject: Reply with quote

I was finally able to download a minimal CD image of amd64, but the result looks pretty disappointing: I discovered that it uses vesafb, too, and it displays with the resolution of 1024x768. I just remembered it wrongly beforehand. So... Currently no solution is found and I'm using "video=vesafb:mtrr:3,ywrap vga=0x318" for a not-so-great 1024x768 framebuffer.
Back to top
View user's profile Send private message
paziu
Tux's lil' helper
Tux's lil' helper


Joined: 24 Nov 2006
Posts: 78
Location: Phlorida

PostPosted: Mon Nov 22, 2010 12:51 am    Post subject: Reply with quote

I am not trying to hijack this thread but this is a potential uvesafb nightmare fix:

After almost 2 days of reading, recompiling etc, I got uvesafb to work, in my case, it was showing only about 12 modes, 800x600 was the highest 8O
I also thought it is a BIOS prioblem of my P55 board or 8800GT - but, bioses are OK.

all FB in the kernel is disabled, beside UVESAFB compiled in OR as a module, with and without initramfs ( initramfs not required )

The problem was: DVI to HDMI adapter attached - the VESA modes on HDMI adapter do show up ONLY in vbespy, but not in /proc and not in hwinfo --framebuffer
so basically, replacing DVI2HDMI adapter with a DVI cable gave me 1920x1200-32 resolution
took 2 days to FINALLY replace the cable.... ( I thought a keyboard is enough to fix UVESAFB )

From what I read, HD15 VGA cable might also give some unwanted results ( on widescreens )... so before you start to rip out all your hair, get on your feet ( or knees ) and check the cable...

paziu
Back to top
View user's profile Send private message
Logicien
Veteran
Veteran


Joined: 16 Sep 2005
Posts: 1366
Location: Montréal

PostPosted: Mon Nov 22, 2010 1:14 am    Post subject: Reply with quote

Hello,
as I know, the Linux vesafb driver do not support mode higher than 1280x1024 in 24 bits (0x31B). Look at /usr/src/linux/Documentation/fb/vesafb.txt. You need to try the nvidiafb driver to get the native resolution of your screen. No KMS support is available for Nvidia graphics cards at that time, if I am right.

:D
_________________
Paul
Back to top
View user's profile Send private message
RichardGv
n00b
n00b


Joined: 26 Jan 2010
Posts: 43
Location: People's Republic of China

PostPosted: Mon Nov 22, 2010 12:14 pm    Post subject: Reply with quote

paziu wrote:
I am not trying to hijack this thread but this is a potential uvesafb nightmare fix:

After almost 2 days of reading, recompiling etc, I got uvesafb to work, in my case, it was showing only about 12 modes, 800x600 was the highest 8O
I also thought it is a BIOS prioblem of my P55 board or 8800GT - but, bioses are OK.

all FB in the kernel is disabled, beside UVESAFB compiled in OR as a module, with and without initramfs ( initramfs not required )

The problem was: DVI to HDMI adapter attached - the VESA modes on HDMI adapter do show up ONLY in vbespy, but not in /proc and not in hwinfo --framebuffer
so basically, replacing DVI2HDMI adapter with a DVI cable gave me 1920x1200-32 resolution
took 2 days to FINALLY replace the cable.... ( I thought a keyboard is enough to fix UVESAFB )

From what I read, HD15 VGA cable might also give some unwanted results ( on widescreens )... so before you start to rip out all your hair, get on your feet ( or knees ) and check the cable...

paziu


Thanks for the suggestion, but it does not apply to my situation: Been a relatively poor eastern, I still use the old-fashioned DVI interface designed some 11 years ago. I actually have never even touched a HDMI cable myself.

Logicien wrote:
Hello,
as I know, the Linux vesafb driver do not support mode higher than 1280x1024 in 24 bits (0x31B). Look at /usr/src/linux/Documentation/fb/vesafb.txt. You need to try the nvidiafb driver to get the native resolution of your screen. No KMS support is available for Nvidia graphics cards at that time, if I am right.

:D


Hmm, as far as I know there are many nonstandard VBE modes that different graphic card manufacturers provided, they work with vesafb, and lots of graphic cards do support 1440x900 framebuffer.
http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Other_commonly_available_modes
In the binary blob nvidia-drivers there's no KMS support indeed. nVidia developers claimed they did not implement KMS due to a license issue.. We have nouveau that supports KMS and I love it, but I cannot use it since it's constantly causing overheating and crashes, even in the winter.
nvidiafb has been having conflicts with nvidia-drivers since 2004, they said.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Unsupported Software All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum