You are not logged in.

#1 2006-12-04 08:28:37

ravisghosh
Member
From: Intergalactic Spaces
Registered: 2006-10-12
Posts: 516
Website

kernel panic after kernel upgrade/ X server not starting

First of all, there was an filesystem check error on my arch drive and it asked me to do fsck manually and i did that with "yes" evertime it asked me to ignore, etc. I dont remember exactly what errors were there.. Then after rebooting, X would not start (xorg). Then I did "pacman -Syu" and along with few other things, it upgrade to the latest kernel. But after that I'm unable to get my box working. It says something like this:

kernel panic - not syncing - attempted to kill init
atkbd.c: spurious ACK on Isa0060/serio0. some program might be trying to access hardware directly.

I googled adn got this:
http://www.google.com/search?hl=en&lr=& … tnG=Search

but could not make out what to do to get things working again. Please suggest what to do.

Offline

#2 2006-12-04 11:24:57

rztka
Member
From: Czech Republic
Registered: 2006-03-10
Posts: 37

Re: kernel panic after kernel upgrade/ X server not starting

hi ravi
i also get the kernel panic after the upgrade, not sure about your message, but with the last kernel, the names of devices (harddrive) can change (hd > sd)... it has happend to me i think :cry:
this could be the solution: http://bbs.archlinux.org/viewtopic.php?t=27441
i'm going to try it this afternoon,
good luck, hope it will helps, t.

Offline

#3 2006-12-05 03:43:56

ravisghosh
Member
From: Intergalactic Spaces
Registered: 2006-10-12
Posts: 516
Website

Re: kernel panic after kernel upgrade/ X server not starting

@rztka

Did u get the solution. How did u changed the names of devices and where. Actualy, I am unable to go into single user mode (fallback) as I had set timeout in menu.lst to 0 sec. Any solutions for that.

Offline

#4 2006-12-05 03:47:23

iphitus
Forum Fellow
From: Melbourne, Australia
Registered: 2004-10-09
Posts: 4,927

Re: kernel panic after kernel upgrade/ X server not starting

another way to boot to a fallback, and have a look at what devices are now called is to add "break=y" to your bootloader line, you can do this at boot time.

ravighosh: i *think* grub still allows a tiny bit of a second for you to stop it booting, so try mashing directional keys and see if you can get the menu -- otherwise jsut boot a livecd and edit it.

edit: I put some preliminary instructions of fixing this up easily here: http://wiki.archlinux.org/index.php/Fix … _subsystem

James

Offline

#5 2006-12-05 06:22:11

ravisghosh
Member
From: Intergalactic Spaces
Registered: 2006-10-12
Posts: 516
Website

Re: kernel panic after kernel upgrade/ X server not starting

I solved it by using the following. I'm keeping it simple for newB's like me.

1. Boot using arch cd.
2. type > arch
3. type > mount /dev/hdXY /mnt (# where hdXY is your root partition where arch is installed, mine is hda9)
4. type > mount /dev/hdXZ /mnt/boot (# where hdXZ is your boot partition, I dont have one as my boot is /dev/hda9/boot, so I dont have to do this line)
5. type > cd /mnt
6. type > nano ./etc/fstab
7. change "hd" to "sd" throughout the file, do "ctrl + x" to exit, it asks you to save, say yes (y  + enter).
8. type > nano ./boot/grub/menu.lst
9. Go down to this line "kernel        /boot/vmlinuz26 root=/dev/hdXY ro" and changed hdXY to sdXY and do the same as above to save and exit (ctrl + x and then y + enter)
10. type > exit

note: This post has been edited based on recommendation of next few posts.

Offline

#6 2006-12-05 07:42:36

brazzmonkey
Member
From: between keyboard and chair
Registered: 2006-03-16
Posts: 818

Re: kernel panic after kernel upgrade/ X server not starting

why do you need to chroot just to edit fstab and menu.lst ? i guess you only need to follow steps 1-4 and 9-13, unmount your disks and reboot.


what goes up must come down

Offline

#7 2006-12-05 08:15:01

ravisghosh
Member
From: Intergalactic Spaces
Registered: 2006-10-12
Posts: 516
Website

Re: kernel panic after kernel upgrade/ X server not starting

Thanks brazzmonkey. I have edited that. actually, I'm a newB too... smile

Now, I can log in CLI but cannot get X working..
When arch starts i get this error

updating module dependencies
EXT3-fs error (device sda9): ext3-readdir: directory #311731 contains a hole at offset 0

then i get the login prompt, but after logging in when i do startx or startxfce4, I get the following

Starting X server
waiting for X server to begin accepting connections
. .
. .
. .

after a lot of dots, i get the following

givingup
xinit: No such file or directory (errno 2): unable to connect to X server
waiting for X server to shut down
xinit: X server slow to shut down, sending kill signa
waiting for X server to die
xinit: Can't kill server

Any solutions???

Offline

#8 2006-12-05 08:17:01

roguetr
Member
Registered: 2006-10-15
Posts: 26

Re: kernel panic after kernel upgrade/ X server not starting

Just thought I would note something about the fsck ...

When you do a manual fsck, make sure the filesystem is unmounted or you will encounter a whole heap of inexplicable wierdness. Obviously you will have to ignore locked files and some fs activity can be interpreted as errors.

If you can't umount the fs use a live cd. Single user mode normally facilitates this process as well. In a year of using arch I have yet to actually use the fallback image though so I am guessing it is sufficient.

Offline

#9 2006-12-05 09:48:31

ravisghosh
Member
From: Intergalactic Spaces
Registered: 2006-10-12
Posts: 516
Website

Re: kernel panic after kernel upgrade/ X server not starting

then i got clue to do

chmod -c -R 777 /tmp

And after that i got some different messages.. here is my Xorg.0.log

_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/bluehead:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: UNKNOWN 
Current Operating System: Linux bluehead 2.6.19-ARCH #1 SMP PREEMPT Sun Dec 3 11:58:46 CET 2006 i686
Build Date: 25 November 2006
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Dec  5 15:02:28 2006
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Simple Layout"
(**) |-->Screen "Screen 1" (0)
(**) |   |-->Monitor "Samsung Samtron 45Bn"
(**) |   |-->Device "Intel i810 Video Card"
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "Keyboard1"
(**) FontPath set to:
    /usr/share/fonts/misc,
    /usr/share/fonts/75dpi,
    /usr/share/fonts/100dpi,
    /usr/share/fonts/TTF,
    /usr/share/fonts/Type1
(**) RgbPath set to "/usr/share/X11/rgb"
(==) ModulePath set to "/usr/lib/xorg/modules"
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) Module ABI versions:
    X.Org ANSI C Emulation: 0.3
    X.Org Video Driver: 1.0
    X.Org XInput driver : 0.6
    X.Org Server Extension : 0.3
    X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so
(II) Module bitmap: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.0.0
    Module class: X.Org Font Renderer
    ABI class: X.Org Font Renderer, version 0.5
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules/libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.0.0
    ABI class: X.Org Video Driver, version 1.0
(--) using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,7124 card 0000,0000 rev 03 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 8086,7125 card 8086,4333 rev 03 class 03,00,00 hdr 00
(II) PCI: 00:1e:0: chip 8086,244e card 0000,0000 rev 02 class 06,04,00 hdr 01
(II) PCI: 00:1f:0: chip 8086,2440 card 0000,0000 rev 02 class 06,01,00 hdr 80
(II) PCI: 00:1f:1: chip 8086,244b card 8086,4333 rev 02 class 01,01,80 hdr 00
(II) PCI: 00:1f:2: chip 8086,2442 card 8086,4333 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1f:3: chip 8086,2443 card 8086,4333 rev 02 class 0c,05,00 hdr 00
(II) PCI: 00:1f:4: chip 8086,2444 card 8086,4333 rev 02 class 0c,03,00 hdr 00
(II) PCI: 00:1f:5: chip 8086,2445 card 8086,4333 rev 02 class 04,01,00 hdr 00
(II) PCI: 01:08:0: chip 8086,2449 card 8086,3013 rev 01 class 02,00,00 hdr 00
(II) PCI: End of PCI scan
(II) Intel Bridge workaround enabled
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
    [0] -1    0    0x00000000 - 0x0000ffff (0x10000) IX[b]
(II) Bus 0 non-prefetchable memory range:
    [0] -1    0    0x00000000 - 0xffffffff (0x0) MX[b]
(II) Bus 0 prefetchable memory range:
    [0] -1    0    0x00000000 - 0xffffffff (0x0) MX[b]
(II) Subtractive PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x0002 (VGA_EN is cleared)
(II) Bus 1 I/O range:
    [0] -1    0    0x0000d000 - 0x0000dfff (0x1000) IX[b]
(II) Bus 1 non-prefetchable memory range:
    [0] -1    0    0xff800000 - 0xff8fffff (0x100000) MX[b]
(II) Bus 1 prefetchable memory range:
    [0] -1    0    0xf6a00000 - 0xf6afffff (0x100000) MX[b]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(--) PCI:*(0:1:0) Intel Corporation 82810E DC-133 CGC [Chipset Graphics Controller] rev 3, Mem @ 0xf8000000/26, 0xffa80000/19
(II) Addressable bus resource ranges are
    [0] -1    0    0x00000000 - 0xffffffff (0x0) MX[b]
    [1] -1    0    0x00000000 - 0x0000ffff (0x10000) IX[b]
(II) OS-reported resource ranges:
    [0] -1    0    0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1    0    0x00000000 - 0x000000ff (0x100) IX[b]
(II) Active PCI resource ranges:
    [0] -1    0    0xff8ff000 - 0xff8fffff (0x1000) MX[b]
    [1] -1    0    0xffa80000 - 0xffafffff (0x80000) MX[b](B)
    [2] -1    0    0xf8000000 - 0xfbffffff (0x4000000) MX[b](B)
    [3] -1    0    0x0000df00 - 0x0000df3f (0x40) IX[b]
    [4] -1    0    0x0000ef00 - 0x0000ef3f (0x40) IX[b]
    [5] -1    0    0x0000e800 - 0x0000e8ff (0x100) IX[b]
    [6] -1    0    0x0000ef80 - 0x0000ef9f (0x20) IX[b]
    [7] -1    0    0x0000efa0 - 0x0000efaf (0x10) IX[b]
    [8] -1    0    0x0000ef40 - 0x0000ef5f (0x20) IX[b]
    [9] -1    0    0x0000ffa0 - 0x0000ffaf (0x10) IX[b]
(II) Active PCI resource ranges after removing overlaps:
    [0] -1    0    0xff8ff000 - 0xff8fffff (0x1000) MX[b]
    [1] -1    0    0xffa80000 - 0xffafffff (0x80000) MX[b](B)
    [2] -1    0    0xf8000000 - 0xfbffffff (0x4000000) MX[b](B)
    [3] -1    0    0x0000df00 - 0x0000df3f (0x40) IX[b]
    [4] -1    0    0x0000ef00 - 0x0000ef3f (0x40) IX[b]
    [5] -1    0    0x0000e800 - 0x0000e8ff (0x100) IX[b]
    [6] -1    0    0x0000ef80 - 0x0000ef9f (0x20) IX[b]
    [7] -1    0    0x0000efa0 - 0x0000efaf (0x10) IX[b]
    [8] -1    0    0x0000ef40 - 0x0000ef5f (0x20) IX[b]
    [9] -1    0    0x0000ffa0 - 0x0000ffaf (0x10) IX[b]
(II) OS-reported resource ranges after removing overlaps with PCI:
    [0] -1    0    0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1    0    0x00000000 - 0x000000ff (0x100) IX[b]
(II) All system resource ranges:
    [0] -1    0    0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1    0    0xff8ff000 - 0xff8fffff (0x1000) MX[b]
    [5] -1    0    0xffa80000 - 0xffafffff (0x80000) MX[b](B)
    [6] -1    0    0xf8000000 - 0xfbffffff (0x4000000) MX[b](B)
    [7] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [8] -1    0    0x00000000 - 0x000000ff (0x100) IX[b]
    [9] -1    0    0x0000df00 - 0x0000df3f (0x40) IX[b]
    [10] -1    0    0x0000ef00 - 0x0000ef3f (0x40) IX[b]
    [11] -1    0    0x0000e800 - 0x0000e8ff (0x100) IX[b]
    [12] -1    0    0x0000ef80 - 0x0000ef9f (0x20) IX[b]
    [13] -1    0    0x0000efa0 - 0x0000efaf (0x10) IX[b]
    [14] -1    0    0x0000ef40 - 0x0000ef5f (0x20) IX[b]
    [15] -1    0    0x0000ffa0 - 0x0000ffaf (0x10) IX[b]
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.3
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.3
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts/libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
    compiled for 7.1.1, module version = 2.1.0
    Module class: X.Org Font Renderer
    ABI class: X.Org Font Renderer, version 0.5
(II) Loading font FreeType
(II) LoadModule: "i810"
(II) Loading /usr/lib/xorg/modules/drivers/i810_drv.so
(II) Module i810: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.6.5
    Module class: X.Org Video Driver
    ABI class: X.Org Video Driver, version 1.0
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.1.1
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 0.6
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input/kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.1.0
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 0.6
(II) I810: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100,
    i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G, E7221 (i915),
    915GM, 945G, 945GM, 965G, 965G, 965Q, 946GZ
(II) Primary Device is: PCI 00:01:0
(--) Assigning device section with no busID to primary device
(--) Chipset i810e found
(II) resource ranges after xf86ClaimFixedResources() call:
    [0] -1    0    0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1    0    0xff8ff000 - 0xff8fffff (0x1000) MX[b]
    [5] -1    0    0xffa80000 - 0xffafffff (0x80000) MX[b](B)
    [6] -1    0    0xf8000000 - 0xfbffffff (0x4000000) MX[b](B)
    [7] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [8] -1    0    0x00000000 - 0x000000ff (0x100) IX[b]
    [9] -1    0    0x0000df00 - 0x0000df3f (0x40) IX[b]
    [10] -1    0    0x0000ef00 - 0x0000ef3f (0x40) IX[b]
    [11] -1    0    0x0000e800 - 0x0000e8ff (0x100) IX[b]
    [12] -1    0    0x0000ef80 - 0x0000ef9f (0x20) IX[b]
    [13] -1    0    0x0000efa0 - 0x0000efaf (0x10) IX[b]
    [14] -1    0    0x0000ef40 - 0x0000ef5f (0x20) IX[b]
    [15] -1    0    0x0000ffa0 - 0x0000ffaf (0x10) IX[b]
(II) resource ranges after probing:
    [0] -1    0    0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1    0    0xff8ff000 - 0xff8fffff (0x1000) MX[b]
    [5] -1    0    0xffa80000 - 0xffafffff (0x80000) MX[b](B)
    [6] -1    0    0xf8000000 - 0xfbffffff (0x4000000) MX[b](B)
    [7] 0    0    0x000a0000 - 0x000affff (0x10000) MS[b]
    [8] 0    0    0x000b0000 - 0x000b7fff (0x8000) MS[b]
    [9] 0    0    0x000b8000 - 0x000bffff (0x8000) MS[b]
    [10] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [11] -1    0    0x00000000 - 0x000000ff (0x100) IX[b]
    [12] -1    0    0x0000df00 - 0x0000df3f (0x40) IX[b]
    [13] -1    0    0x0000ef00 - 0x0000ef3f (0x40) IX[b]
    [14] -1    0    0x0000e800 - 0x0000e8ff (0x100) IX[b]
    [15] -1    0    0x0000ef80 - 0x0000ef9f (0x20) IX[b]
    [16] -1    0    0x0000efa0 - 0x0000efaf (0x10) IX[b]
    [17] -1    0    0x0000ef40 - 0x0000ef5f (0x20) IX[b]
    [18] -1    0    0x0000ffa0 - 0x0000ffaf (0x10) IX[b]
    [19] 0    0    0x000003b0 - 0x000003bb (0xc) IS[b]
    [20] 0    0    0x000003c0 - 0x000003df (0x20) IS[b]
(II) Setting vga for screen 0.
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules/libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 0.1.0
    ABI class: X.Org Video Driver, version 1.0
(**) I810(0): Depth 24, (--) framebuffer bpp 24
(==) I810(0): RGB weight 888
(==) I810(0): Default visual is TrueColor
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/lib/xorg/modules/libxaa.so
(II) Module xaa: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.2.0
    ABI class: X.Org Video Driver, version 1.0
(**) I810(0): DRI is disabled because it runs only at 16-bit depth.
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules/libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.1.0
    ABI class: X.Org Video Driver, version 1.0
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules/libint10.so
(II) Module int10: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.0.0
    ABI class: X.Org Video Driver, version 1.0
(II) I810(0): initializing int10
(II) I810(0): Primary V_BIOS segment is: 0xc000
(II) I810(0): VESA BIOS detected
(II) I810(0): VESA VBE Version 3.0
(II) I810(0): VESA VBE Total Mem: 1024 kB
(II) I810(0): VESA VBE OEM: Intel(R) 8xx Chipset Video BIOS
(II) I810(0): VESA VBE OEM Software Rev: 34.103
(II) I810(0): VESA VBE OEM Vendor: Intel Corporation
(II) I810(0): VESA VBE OEM Product: Intel(R) 8xx Chipset
(II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Loading /usr/lib/xorg/modules/libddc.so
(II) Module ddc: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.0.0
    ABI class: X.Org Video Driver, version 1.0
(II) I810(0): VESA VBE DDC supported
(II) I810(0): VESA VBE DDC Level 2
(II) I810(0): VESA VBE DDC transfer in appr. 1 sec.
(II) I810(0): VESA VBE DDC read successfully
(II) I810(0): Manufacturer: SAM  Model: 1034  Serial#: 1146106164
(II) I810(0): Year: 2001  Week: 9
(II) I810(0): EDID Version: 1.1
(II) I810(0): Analog Display Input,  Input Voltage Level: 0.700/0.700 V
(II) I810(0): Sync:  Separate
(II) I810(0): Max H-Image Size [cm]: horiz.: 27  vert.: 20
(II) I810(0): Gamma: 2.13
(II) I810(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
(II) I810(0): redX: 0.633 redY: 0.351   greenX: 0.289 greenY: 0.614
(II) I810(0): blueX: 0.142 blueY: 0.065   whiteX: 0.283 whiteY: 0.298
(II) I810(0): Supported VESA Video Modes:
(II) I810(0): 720x400@70Hz
(II) I810(0): 720x400@88Hz
(II) I810(0): 640x480@60Hz
(II) I810(0): 640x480@67Hz
(II) I810(0): 640x480@72Hz
(II) I810(0): 640x480@75Hz
(II) I810(0): 800x600@56Hz
(II) I810(0): 800x600@60Hz
(II) I810(0): 800x600@72Hz
(II) I810(0): 800x600@75Hz
(II) I810(0): 832x624@75Hz
(II) I810(0): 1024x768@87Hz (interlaced)
(II) I810(0): 1024x768@60Hz
(II) I810(0): Manufacturer's mask: 0
(II) I810(0): Supported Future Video Modes:
(II) I810(0): #0: hsize: 640  vsize 480  refresh: 85  vid: 22833
(II) I810(0): #1: hsize: 800  vsize 600  refresh: 85  vid: 22853
(II) I810(0): #2: hsize: 1024  vsize 768  refresh: 60  vid: 16481
(II) I810(0): Supported additional Video Mode:
(II) I810(0): clock: 36.0 MHz   Image Size:  255 x 191 mm
(II) I810(0): h_active: 640  h_sync: 696  h_sync_end 752 h_blank_end 832 h_border: 0
(II) I810(0): v_active: 480  v_sync: 481  v_sync_end 484 v_blanking: 509 v_border: 0
(II) I810(0): Supported additional Video Mode:
(II) I810(0): clock: 56.2 MHz   Image Size:  255 x 191 mm
(II) I810(0): h_active: 800  h_sync: 832  h_sync_end 896 h_blank_end 1048 h_border: 0
(II) I810(0): v_active: 600  v_sync: 601  v_sync_end 604 v_blanking: 631 v_border: 0
(II) I810(0): Ranges: V min: 50  V max: 120 Hz, H min: 30  H max: 55 kHz,
(II) I810(0): Serial No: HMER248863
(--) I810(0): Chipset: "i810e"
(--) I810(0): Linear framebuffer at 0xF8000000
(--) I810(0): IO registers at addr 0xFFA80000
(II) I810(0): Kernel reported 51712 total, 1 used
(II) I810(0): I810CheckAvailableMemory: 206844k available
(==) I810(0): Will alloc AGP framebuffer: 8192 kByte
(==) I810(0): Using gamma correction (1.0, 1.0, 1.0)
(II) I810(0): Samsung Samtron 45Bn: Using hsync range of 30.00-55.00 kHz
(II) I810(0): Samsung Samtron 45Bn: Using vrefresh range of 50.00-120.00 Hz
(II) I810(0): Clock range:   9.50 to 136.00 MHz
(WW) (640x350,Samsung Samtron 45Bn) mode clock 31.5MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan)
(WW) (640x400,Samsung Samtron 45Bn) mode clock 31.5MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan)
(WW) (720x400,Samsung Samtron 45Bn) mode clock 35.5MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "360x200" (bad mode clock/interlace/doublescan)
(WW) (640x480,Samsung Samtron 45Bn) mode clock 25.2MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
(WW) (640x480,Samsung Samtron 45Bn) mode clock 31.5MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
(WW) (640x480,Samsung Samtron 45Bn) mode clock 31.5MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
(WW) (640x480,Samsung Samtron 45Bn) mode clock 36MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
(WW) (800x600,Samsung Samtron 45Bn) mode clock 36MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(WW) (800x600,Samsung Samtron 45Bn) mode clock 40MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(WW) (800x600,Samsung Samtron 45Bn) mode clock 50MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(WW) (800x600,Samsung Samtron 45Bn) mode clock 49.5MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(WW) (800x600,Samsung Samtron 45Bn) mode clock 56.3MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1024x768" (unknown reason)
(II) I810(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(WW) (1024x768,Samsung Samtron 45Bn) mode clock 65MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(WW) (1024x768,Samsung Samtron 45Bn) mode clock 75MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1024x768" (hsync out of range)
(II) I810(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(WW) (1024x768,Samsung Samtron 45Bn) mode clock 78.8MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1024x768" (hsync out of range)
(II) I810(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(WW) (1024x768,Samsung Samtron 45Bn) mode clock 94.5MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1024x768" (hsync out of range)
(II) I810(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
(WW) (1152x864,Samsung Samtron 45Bn) mode clock 108MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1152x864" (hsync out of range)
(II) I810(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
(WW) (1280x960,Samsung Samtron 45Bn) mode clock 108MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1280x960" (hsync out of range)
(II) I810(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1280x960" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan)
(WW) (1280x1024,Samsung Samtron 45Bn) mode clock 108MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1280x1024" (hsync out of range)
(II) I810(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan)
(WW) (1280x1024,Samsung Samtron 45Bn) mode clock 135MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1280x1024" (hsync out of range)
(II) I810(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1280x1024" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1600x1200" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1792x1344" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1792x1344" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1856x1392" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1856x1392" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
(WW) (832x624,Samsung Samtron 45Bn) mode clock 57.284MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "416x312" (bad mode clock/interlace/doublescan)
(WW) (1152x768,Samsung Samtron 45Bn) mode clock 64.995MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "576x384" (bad mode clock/interlace/doublescan)
(WW) (1152x864,Samsung Samtron 45Bn) mode clock 121.5MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1152x864" (hsync out of range)
(II) I810(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
(WW) (1400x1050,Samsung Samtron 45Bn) mode clock 122MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1400x1050" (hsync out of range)
(II) I810(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1400x1050" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1400x1050" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1400x1050" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
(WW) (1600x1024,Samsung Samtron 45Bn) mode clock 106.91MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1600x1024" (hsync out of range)
(II) I810(0): Not using default mode "800x512" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1920x1200" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "960x600" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) I810(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) I810(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "2048x1536" (insufficient memory for mode)
(II) I810(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(WW) (848x480,Samsung Samtron 45Bn) mode clock 31.49MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "424x240" (bad mode clock/interlace/doublescan)
(WW) (848x480,Samsung Samtron 45Bn) mode clock 37.52MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "424x240" (bad mode clock/interlace/doublescan)
(WW) (848x480,Samsung Samtron 45Bn) mode clock 40.96MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "424x240" (bad mode clock/interlace/doublescan)
(WW) (848x480,Samsung Samtron 45Bn) mode clock 47.39MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "424x240" (bad mode clock/interlace/doublescan)
(WW) (1152x864,Samsung Samtron 45Bn) mode clock 81.62MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
(WW) (1152x864,Samsung Samtron 45Bn) mode clock 96.77MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1152x864" (hsync out of range)
(II) I810(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
(WW) (1152x864,Samsung Samtron 45Bn) mode clock 104.99MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1152x864" (hsync out of range)
(II) I810(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
(WW) (1152x864,Samsung Samtron 45Bn) mode clock 119.65MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1152x864" (hsync out of range)
(II) I810(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1400x1050" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1400x1050" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
(WW) (1280x800,Samsung Samtron 45Bn) mode clock 83.46MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "640x400" (bad mode clock/interlace/doublescan)
(WW) (1280x800,Samsung Samtron 45Bn) mode clock 98.89MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1280x800" (hsync out of range)
(II) I810(0): Not using default mode "640x400" (bad mode clock/interlace/doublescan)
(WW) (1280x800,Samsung Samtron 45Bn) mode clock 107.21MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1280x800" (hsync out of range)
(II) I810(0): Not using default mode "640x400" (bad mode clock/interlace/doublescan)
(WW) (1280x800,Samsung Samtron 45Bn) mode clock 123.38MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1280x800" (hsync out of range)
(II) I810(0): Not using default mode "640x400" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1680x1050" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "840x525" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1680x1050" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "840x525" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1680x1050" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "840x525" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1680x1050" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "840x525" (bad mode clock/interlace/doublescan)
(WW) (1280x720,Samsung Samtron 45Bn) mode clock 74.48MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "640x360" (bad mode clock/interlace/doublescan)
(WW) (1280x720,Samsung Samtron 45Bn) mode clock 89.04MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "640x360" (bad mode clock/interlace/doublescan)
(WW) (1280x720,Samsung Samtron 45Bn) mode clock 95.65MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1280x720" (hsync out of range)
(II) I810(0): Not using default mode "640x360" (bad mode clock/interlace/doublescan)
(WW) (1280x720,Samsung Samtron 45Bn) mode clock 110.01MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1280x720" (hsync out of range)
(II) I810(0): Not using default mode "640x360" (bad mode clock/interlace/doublescan)
(WW) (1280x768,Samsung Samtron 45Bn) mode clock 80.14MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "640x384" (bad mode clock/interlace/doublescan)
(WW) (1280x768,Samsung Samtron 45Bn) mode clock 94.98MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1280x768" (hsync out of range)
(II) I810(0): Not using default mode "640x384" (bad mode clock/interlace/doublescan)
(WW) (1280x768,Samsung Samtron 45Bn) mode clock 102.98MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1280x768" (hsync out of range)
(II) I810(0): Not using default mode "640x384" (bad mode clock/interlace/doublescan)
(WW) (1280x768,Samsung Samtron 45Bn) mode clock 118.53MHz exceeds DDC maximum 0MHz
(II) I810(0): Not using default mode "1280x768" (hsync out of range)
(II) I810(0): Not using default mode "640x384" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1920x1200" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "960x600" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1920x1200" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "960x600" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1920x1200" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "960x600" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "1920x1200" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "960x600" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "2560x1600" (insufficient memory for mode)
(II) I810(0): Not using default mode "1280x800" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "2560x1600" (insufficient memory for mode)
(II) I810(0): Not using default mode "1280x800" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "2560x1600" (insufficient memory for mode)
(II) I810(0): Not using default mode "1280x800" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using default mode "2560x1600" (insufficient memory for mode)
(II) I810(0): Not using default mode "1280x800" (bad mode clock/interlace/doublescan)
(II) I810(0): Not using mode "1280x1024" (no mode of this name)
(II) I810(0): Not using default mode "1280x800" (width too large for virtual size)
(II) I810(0): Not using default mode "1152x864" (width too large for virtual size)
(II) I810(0): Not using default mode "1280x768" (width too large for virtual size)
(II) I810(0): Not using default mode "1280x720" (width too large for virtual size)
(II) I810(0): Not using default mode "1280x720" (width too large for virtual size)
(II) I810(0): Not using default mode "1152x768" (width too large for virtual size)
(--) I810(0): Virtual size is 1024x768 (pitch 1024)
(**) I810(0): *Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
(II) I810(0): Modeline "1024x768"   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync
(**) I810(0): *Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz
(II) I810(0): Modeline "800x600"   56.30  800 832 896 1048  600 601 604 631 +hsync +vsync
(**) I810(0): *Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz
(II) I810(0): Modeline "640x480"   36.00  640 696 752 832  480 481 484 509 -hsync -vsync
(**) I810(0):  Default mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz
(II) I810(0): Modeline "832x624"   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync
(**) I810(0):  Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
(II) I810(0): Modeline "800x600"   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync
(**) I810(0):  Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz
(II) I810(0): Modeline "800x600"   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync
(**) I810(0):  Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(II) I810(0): Modeline "800x600"   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync
(**) I810(0):  Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
(II) I810(0): Modeline "800x600"   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync
(**) I810(0):  Default mode "848x480": 47.4 MHz, 42.9 kHz, 85.0 Hz
(II) I810(0): Modeline "848x480"   47.39  848 888 976 1104  480 481 484 505 -hsync +vsync
(**) I810(0):  Default mode "848x480": 41.0 MHz, 37.6 kHz, 75.0 Hz
(II) I810(0): Modeline "848x480"   40.96  848 880 968 1088  480 481 484 502 -hsync +vsync
(**) I810(0):  Default mode "848x480": 37.5 MHz, 35.0 kHz, 70.0 Hz
(II) I810(0): Modeline "848x480"   37.52  848 872 960 1072  480 481 484 500 -hsync +vsync
(**) I810(0):  Default mode "848x480": 31.5 MHz, 29.8 kHz, 60.0 Hz
(II) I810(0): Modeline "848x480"   31.49  848 864 952 1056  480 481 484 497 -hsync +vsync
(**) I810(0):  Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
(II) I810(0): Modeline "640x480"   31.50  640 656 720 840  480 481 484 500 -hsync -vsync
(**) I810(0):  Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz
(II) I810(0): Modeline "640x480"   31.50  640 664 704 832  480 489 491 520 -hsync -vsync
(**) I810(0):  Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz
(II) I810(0): Modeline "640x480"   25.20  640 656 752 800  480 490 492 525 -hsync -vsync
(**) I810(0):  Default mode "720x400": 35.5 MHz, 37.9 kHz, 85.0 Hz
(II) I810(0): Modeline "720x400"   35.50  720 756 828 936  400 401 404 446 -hsync +vsync
(**) I810(0):  Default mode "640x400": 31.5 MHz, 37.9 kHz, 85.1 Hz
(II) I810(0): Modeline "640x400"   31.50  640 672 736 832  400 401 404 445 -hsync +vsync
(**) I810(0):  Default mode "640x350": 31.5 MHz, 37.9 kHz, 85.1 Hz
(II) I810(0): Modeline "640x350"   31.50  640 672 736 832  350 382 385 445 +hsync -vsync
(--) I810(0): Display dimensions: (270, 200) mm
(--) I810(0): DPI set to (96, 97)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.3
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Loading /usr/lib/xorg/modules/libramdac.so
(II) Module ramdac: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 0.1.0
    ABI class: X.Org Video Driver, version 1.0
(II) I810(0): XvMC is Disabled: use XvMCSurfaces config option to enable.
(==) Depth 24 pixmap format is 32 bpp
(II) do I need RAC?  No, I don't.
(II) resource ranges after preInit:
    [0] 0    0    0xffa80000 - 0xffafffff (0x80000) MS[b]
    [1] 0    0    0xf8000000 - 0xfbffffff (0x4000000) MS[b]
    [2] -1    0    0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [3] -1    0    0x000f0000 - 0x000fffff (0x10000) MX[b]
    [4] -1    0    0x000c0000 - 0x000effff (0x30000) MX[b]
    [5] -1    0    0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [6] -1    0    0xff8ff000 - 0xff8fffff (0x1000) MX[b]
    [7] -1    0    0xffa80000 - 0xffafffff (0x80000) MX[b](B)
    [8] -1    0    0xf8000000 - 0xfbffffff (0x4000000) MX[b](B)
    [9] 0    0    0x000a0000 - 0x000affff (0x10000) MS[b](OprD)
    [10] 0    0    0x000b0000 - 0x000b7fff (0x8000) MS[b](OprD)
    [11] 0    0    0x000b8000 - 0x000bffff (0x8000) MS[b](OprD)
    [12] -1    0    0x0000ffff - 0x0000ffff (0x1) IX[b]
    [13] -1    0    0x00000000 - 0x000000ff (0x100) IX[b]
    [14] -1    0    0x0000df00 - 0x0000df3f (0x40) IX[b]
    [15] -1    0    0x0000ef00 - 0x0000ef3f (0x40) IX[b]
    [16] -1    0    0x0000e800 - 0x0000e8ff (0x100) IX[b]
    [17] -1    0    0x0000ef80 - 0x0000ef9f (0x20) IX[b]
    [18] -1    0    0x0000efa0 - 0x0000efaf (0x10) IX[b]
    [19] -1    0    0x0000ef40 - 0x0000ef5f (0x20) IX[b]
    [20] -1    0    0x0000ffa0 - 0x0000ffaf (0x10) IX[b]
    [21] 0    0    0x000003b0 - 0x000003bb (0xc) IS[b](OprU)
    [22] 0    0    0x000003c0 - 0x000003df (0x20) IS[b](OprU)
(==) I810(0): Write-combining range (0xf8000000,0x4000000)
(II) I810(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) I810(0): Setting dot clock to 65.0 MHz [ 0x3f 0xa 0x30 ] [ 65 12 3 ]
(II) I810(0): chose watermark 0x22214000: (tab.freq 65.0)
(II) I810(0): xf86BindGARTMemory: bind key 0 at 0x00000000 (pgoffset 0)
(WW) I810(0): xf86AllocateGARTMemory: allocation of 1024 pages failed
    (Cannot allocate memory)
(II) I810(0): No physical memory available for 4194304 bytes of DCACHE
(II) I810(0): xf86BindGARTMemory: bind key 1 at 0x00800000 (pgoffset 2048)
(II) I810(0): Allocated of 4096 bytes for HW cursor
(II) I810(0): xf86BindGARTMemory: bind key 2 at 0x00801000 (pgoffset 2049)
(II) I810(0): Allocated of 16384 bytes for ARGB HW cursor
(II) I810(0): Adding 512 scanlines for pixmap caching
(II) I810(0): Allocated Scratch Memory
(II) I810(0): Using XFree86 Acceleration Architecture (XAA)
    Screen to screen bit blits
    Solid filled rectangles
    8x8 mono pattern filled rectangles
    Indirect CPU to Screen color expansion
    Solid Horizontal and Vertical Lines
    Offscreen Pixmaps
    Setting up tile and stipple cache:
        16 128x128 slots
        4 256x256 slots
(==) I810(0): Backing store disabled
(==) I810(0): Silken mouse enabled
(WW) I810(0): Direct rendering disabled
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(**) Option "Protocol" "Microsoft"
(**) Mouse1: Device: "/dev/ttyS0"
(**) Mouse1: Protocol: "Microsoft"
(**) Option "CorePointer"
(**) Mouse1: Core Pointer
(**) Option "Device" "/dev/ttyS0"
(**) Option "BaudRate" "1200"
(**) Option "StopBits" "1"
(**) Option "DataBits" "7"
(**) Option "Parity" "None"
(**) Option "Vmin" "1"
(**) Option "Vtime" "0"
(**) Option "FlowControl" "None"
(**) Option "Emulate3Buttons"
(**) Mouse1: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5 6 7"
(**) Mouse1: ZAxisMapping: buttons 4, 5, 6 and 7
(**) Mouse1: Buttons: 11
(**) Mouse1: BaudRate: 1200
(**) Option "CoreKeyboard"
(**) Keyboard1: Core Keyboard
(**) Option "Protocol" "standard"
(**) Keyboard1: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard1: XkbRules: "xorg"
(**) Option "XkbModel" "pc104"
(**) Keyboard1: XkbModel: "pc104"
(**) Option "XkbLayout" "us"
(**) Keyboard1: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) Keyboard1: CustomKeycodes disabled
(II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)
(II) I810(0): xf86UnbindGARTMemory: unbind key 0
(II) I810(0): xf86UnbindGARTMemory: unbind key 1
(II) I810(0): xf86UnbindGARTMemory: unbind key 2
FreeFontPath: FPE "/usr/share/fonts/misc" refcount is 2, should be 1; fixing.

Offline

#10 2006-12-05 10:13:26

roguetr
Member
Registered: 2006-10-15
Posts: 26

Re: kernel panic after kernel upgrade/ X server not starting

Do you know why your /tmp had incorrect permissions?

A quick google seems to point to additional problems with /tmp. Was /tmp ever deleted?

Also, in the post you recently edited, you are missing /mnt on lines 6 and 8 now you are not chrooting.

Offline

#11 2006-12-05 10:19:47

roguetr
Member
Registered: 2006-10-15
Posts: 26

Re: kernel panic after kernel upgrade/ X server not starting

or put ./ to indicate a relative path.

I thought this might be useful to you incase it is still a /tmp issue, with regards to required dirs and perms:

[root@portal tmp]# ls -Al
total 39
drwxrwxrwt 2 root    root   1024 2006-12-04 14:45 .ICE-unix
-r--r--r-- 1 root    root     11 2006-12-04 14:45 .X0-lock
drwxrwxrwt 2 root    root   1024 2006-12-04 14:45 .X11-unix
drwx------ 3 roguetr users  1024 2006-12-05 16:10 gconfd-roguetr
drwx------ 2 roguetr users  1024 2006-12-04 14:45 gpg-iD7bbN
drwxr-xr-x 2 roguetr users  1024 2006-12-05 12:10 hsperfdata_roguetr
drwx------ 2 roguetr users  1024 2006-12-05 21:15 kde-roguetr
-rw------- 1 roguetr users 27899 2006-12-05 21:13 krellkam0yYHSq
drwx------ 3 roguetr users  1024 2006-12-05 21:15 ksocket-roguetr
drwx------ 2 roguetr users  1024 2006-12-05 19:54 orbit-roguetr
drwx------ 2 roguetr users  1024 2006-12-04 14:45 ssh-QDqZK13993

Offline

#12 2006-12-05 13:29:21

ravisghosh
Member
From: Intergalactic Spaces
Registered: 2006-10-12
Posts: 516
Website

Re: kernel panic after kernel upgrade/ X server not starting

@roguetr
B4 line 6 and 8, i'm doing cd /mnt. So, do i still need /mnt in 6 and 8.

also there is lot of disk activity (orange light) when I do startxfce4 and it continues after that

Once, i was able to get X and xfce4 work, but there was lot of disk activity and all the apps were very slow. After that, again the same story. X is not working again and huge disk activity.

Offline

#13 2006-12-05 23:52:51

ravisghosh
Member
From: Intergalactic Spaces
Registered: 2006-10-12
Posts: 516
Website

Re: kernel panic after kernel upgrade/ X server not starting

no solution yet.... ;(

Offline

#14 2006-12-06 00:25:52

roguetr
Member
Registered: 2006-10-15
Posts: 26

Re: kernel panic after kernel upgrade/ X server not starting

Hey ravisghosh,

nano /etc/fstab is an absolute path which means you will be editing the fstab of the boot cd.

If you cd /mnt first then the command would be:

 nano ./etc/fstab 

to indicate a relative path. Note the '.' before the slash.

As for X, not having ever had your problem nor being aware of what is causing it makes it difficult for me to help but ...

The command for chmodding the /tmp should be:

 chmod 1777 /tmp

Resulting in an entry such as:

 drwxrwxrwt 11 root   root    2048 2006-12-06 11:07 tmp

And reboot (not necessarily required but the easiest way for now without sussing out your entire config).

If problems persist and assuming the tmp dir was deleted at some point, ensuring these entry exists in /tmp:

 drwxrwxrwt 2 root root 1024 2006-12-04 14:45 .X11-unix 
drwxrwxrwt 2 root    root   1024 2006-12-04 14:45 .ICE-unix

May help. As you can see, they are all owned by root and all have the perms 1777.

Offline

#15 2006-12-06 11:41:52

ravisghosh
Member
From: Intergalactic Spaces
Registered: 2006-10-12
Posts: 516
Website

Re: kernel panic after kernel upgrade/ X server not starting

I did

chmod 1777 /tmp

But that returned nothing and everything remained the same.

I guess the X thing is a hardware error related to:

updating module dependencies 
EXT3-fs error (device sda9): ext3_readdir: directory #311731 contains a hole at offset 0

I get this every time i boot and also ever other time i boot, i have to do manual fsck.

Then I did

[root@bluehead~]# find / -inum 311731
/lib/modules/2.6.19-ARCH/kernel/sound/pcmcia/vx
EXT3-fs error (device sda9): ext3_readdir: directory #311731 contains a hole at offset 0
find: /proc/2146/task/2146/fd/4: No such file or directory.
find: /proc/2146/fd/4: No such file or directory.

This was suggested in some forum to check which directory or file has problem, but i could not make out what it meant now.

Any suggestions please.. sad

Offline

#16 2006-12-06 22:51:16

roguetr
Member
Registered: 2006-10-15
Posts: 26

Re: kernel panic after kernel upgrade/ X server not starting

OK, so you still have a fs error.

When you are doing a manual fsck, are all reported errors being corrected or are you ignoring some?

The potential here is that you may have a faulty hard disk or controller.

Offline

#17 2006-12-07 00:22:39

ravisghosh
Member
From: Intergalactic Spaces
Registered: 2006-10-12
Posts: 516
Website

Re: kernel panic after kernel upgrade/ X server not starting

I'm ignoring all the errors and doing "yes" when it asks me to fix it. Will doing fsck after booting from CD work?

Offline

#18 2006-12-07 00:35:29

roguetr
Member
Registered: 2006-10-15
Posts: 26

Re: kernel panic after kernel upgrade/ X server not starting

From CD is really the only way to do it (single user mode/fallback image with unmounted filesystem aswell but CD will sort you out). You haven't been providing a lot of information but whatever you do, you should not fsck a mounted filesystem.

Boot from cd and fsck /dev/sda1 or whatever directly. Do not mount the filesystem.

And ... do not ignore anything ... make sure everything is accomplished successfully otherwise it is unlikely you will ever get this going.

Offline

#19 2006-12-07 12:48:25

ravisghosh
Member
From: Intergalactic Spaces
Registered: 2006-10-12
Posts: 516
Website

Re: kernel panic after kernel upgrade/ X server not starting

I booted with CD and then I did:

#fsck /dev/sda9
fsck 1.38 (30-Jun-2005)
fsck: fsck.ext2: not found
fsck: Error 2 while executing fsck.ext2 for /dev/sda9

Thinking that since the CD is old, it identifies the partitions as hda instead of sda, I changed the command and got this:

#fsck /dev/hda9
fsck 1.38 (30-Jun-2005)
fsck: fsck.ext3: not found
fsck: Error 2 while executing fsck.ext3 for /dev/hda9

Note the change from fsck.ext2 to fsck.ext3.

Since it was not working, I did:

 e2fsck -c /dev/hda9
fsck 1.38 (30-Jun-2005)
Checking for bad blocks (read only test)
Buffer I/O error on device hda9 logical block 527968

And I kept getting that buffer I/O error one after another. Then I removed the CD and botted from hard disk and got again it asked me to do manual fsck (to give root password for maintenance). Now I did this:

[root@(none)~]# umount /
[root@(none)~]# fsck /dev/sda9
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
/dev/sda9 contains a file system with errors, check forced
Pass 1: Checking inodes, blocks, and sizes
Error reading block 659172 (attempt to read block from file system resulted in short read) while reading indirect blocks of inode 311349. Ignore error <y>? no
Error while iterating over blocks in inode 311349: Attempt to read block from file system resulted in short read
e2fsck: aborted

@roguetr, you said not to ignore errors, but here if you do not ignore them, it aborts the fsck.

Does all the above mean that my HD is at risk. Is there any process to stop using defected blocks and use the rest of disk?

Offline

#20 2006-12-07 18:19:34

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,868

Re: kernel panic after kernel upgrade/ X server not starting

Some versions of the arch installer cd didn't have ext3.fsck included, try the latest ftp-iso from tpowa .


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#21 2006-12-07 23:57:25

ravisghosh
Member
From: Intergalactic Spaces
Registered: 2006-10-12
Posts: 516
Website

Re: kernel panic after kernel upgrade/ X server not starting

@lone wolf,

that leaves me with downloading the whole iso. Is there any other way around?

Offline

#22 2006-12-08 01:26:05

roguetr
Member
Registered: 2006-10-15
Posts: 26

Re: kernel panic after kernel upgrade/ X server not starting

I concur with lone_wolf. tpowa's images are awesomely up-to-date and very functional.

Failing that, I would say your HD or controller (possibly the MB or the HD controller) is fubar.

Try a new or spare disc and see if you come across the same issue. if so, it's new motherboard time.

Offline

#23 2006-12-08 01:27:03

roguetr
Member
Registered: 2006-10-15
Posts: 26

Re: kernel panic after kernel upgrade/ X server not starting

ravisghosh wrote:

@lone wolf,

that leaves me with downloading the whole iso. Is there any other way around?

Yes, do you have knoppix? or any other usable rescue type environment?

So long as it has the required fs tools ... and is up-to-date you should have no worries at least determining if it is the hardware.

Offline

#24 2006-12-08 13:15:13

ravisghosh
Member
From: Intergalactic Spaces
Registered: 2006-10-12
Posts: 516
Website

Re: kernel panic after kernel upgrade/ X server not starting

okay, i will check with ubuntu 6.06 livecd and fedora core 5.

Offline

Board footer

Powered by FluxBB