You are not logged in.

#1 2007-05-30 04:37:37

Thrillhouse
Member
From: Arlington, VA, USA
Registered: 2007-05-29
Posts: 175

Messed up menu.lst

I successfully installed Arch and Gnome but when I went to reboot I got this error message:

kernel panic - not syncing: VFS: Unable to mount root fs on unknown block (0,0)

I googled the error message but none of the answers that other people had worked for me.  Most of them involved editing menu.lst and I have done it so many times now that I'm not sure what was in there originally.  I'm getting different errors now, stuff like "file not found" in reference to the kernel.  I know the install is good.  I was using it perfectly before I rebooted.  Both / and /boot are located in /dev/hda5.  This is what I have in /boot/grub/menu.lst:

(0) Arch Linux
title Arch
root(hd0,4)
kernel /vmlinuz26 root=/dev/hda5
initrd /initrd26-full.img

(1) Windows
title Windows
rootnoverify (hd0,1)
makeactive
chainloader +1

The Windows entry is correct.  I can boot into there fine.  I just need to know what to put for Arch.  I'm not familiar enough with GRUB or the kernel or init to know what should be there.  Your help would be greatly appreciated.  I was really loving Arch when I had it going.


For the strength of the pack is the wolf, and the strength of the wolf is the pack.

Offline

#2 2007-05-30 05:02:04

dawei
Member
From: China
Registered: 2007-05-02
Posts: 29

Re: Messed up menu.lst

First, if you are using the default kernel, the initrd file name should be "kernel26.img".

Second, your root device should be /dev/sda5.

Is your menu.lst file generated by arch setup?

Offline

#3 2007-05-30 10:25:01

Dheart
Member
From: Sofia, Bulgaria
Registered: 2006-10-26
Posts: 956

Re: Messed up menu.lst

The newer kernel versions change the hd* to sd* therefor when you installed arch you had no problems. But you updated it and installed the new kernel, which changes the names of the devises, menu.lst doesn't change by itself so you need to do that manually. Your archlinux entry should look like this:

(0) Arch Linux
title Arch
root(hd0,4)
kernel /vmlinuz26 root=/dev/sda5
initrd /kernel26.img

(I also think that you are using wrong initrd...)


My victim you are meant to be
No, you cannot hide nor flee
You know what I'm looking for
Pleasure your torture, I will endure...

Offline

#4 2007-05-30 11:29:29

deathadder
Member
From: UK
Registered: 2007-04-18
Posts: 8
Website

Re: Messed up menu.lst

Isn't it only sdxx for SCSI based hard drives? Which includes SATA.

I'm going to make another vote for the initrd being wrong.

Last edited by deathadder (2007-05-30 11:30:52)


#define QUESTION ((bb) || !(bb))

Offline

#5 2007-05-30 12:20:04

paul_au
Member
Registered: 2006-04-13
Posts: 38

Re: Messed up menu.lst

it seems that you don't have a separate boot partition, so should the kernel and initrd point to the correct location of the files which would be:

kernel /boot/vmlinuz26 root=/dev/sda5
initrd /boot/kernel26.img

Offline

#6 2007-05-30 12:20:17

sjg
Member
From: UK
Registered: 2007-02-10
Posts: 63

Re: Messed up menu.lst

With recent kernel versions IDE drives also appear as sdxx - see this thread:

http://bbs.archlinux.org/viewtopic.php?pid=247174

Offline

#7 2007-05-30 13:37:22

Leigh
Member
From: USA
Registered: 2004-06-25
Posts: 533

Re: Messed up menu.lst

I'm not sure if this will help because I have a raid setup, but...

My /boot is on sda1 and sdb1
My / is on sda3 and sdb3

This is my menu.lst for the stock kernel...

# (4) Arch Linux
title  Arch Linux pci=conf1 [kernel26.img]
root   (hd0,0)
kernel /vmlinuz26 pci=conf1 root=/dev/md0 ro md=0,/dev/sda3,/dev/sdb3 md=1,/dev/sda1,/dev/sdb1 md=2,/dev/sda2,/dev/sdb2 vga=773
initrd /kernel26.img

# (5) Arch Linux Fallback
title  Arch Linux pci=conf1 [kernel26-fallback.img]
root   (hd0,0)
kernel /vmlinuz26 pci=conf1 root=/dev/md0 ro md=0,/dev/sda3,/dev/sdb3 md=1,/dev/sda1,/dev/sdb1 md=2,/dev/sda2,/dev/sdb2 vga=773
initrd /kernel26-fallback.img


So in your case, beside changing hda5 to sda5 in the kernel line as Dheart mentioned, I think the only mistake you had was in the initrd line, where kernel26.img should be in your /boot dir. Also, I'm not sure if it matters, but I think you need to have a space between "root" and "(hd0,4)".

I would think your menu.lst should read....

(0) Arch Linux
title Arch
root (hd0,4)
kernel /vmlinuz26 root=/dev/sda5
initrd /kernel26.img

Last edited by Leigh (2007-05-30 13:51:24)


-- archlinux 是一个极好的 linux

Offline

#8 2007-05-30 19:27:46

Thrillhouse
Member
From: Arlington, VA, USA
Registered: 2007-05-29
Posts: 175

Re: Messed up menu.lst

Thanks everybody for your help.  After trying some of your suggestions, I finally got menu.lst the way it needs to be.  Turns out this is the correct configuration:

(0) Arch Linux
title Arch
root(hd0,4)
kernel /boot/vmlinuz26 root=/dev/sda5
initrd /boot/kernel26.img

Unfortunately, now I have a new problem.  I'm hoping you can help me with this one too.  As Arch boots, it gets to the point of "Checking filesystems" and then it throws this error:

/dev/hda5
The superblock could not be read or does not describe a correct ext2 filesystem.  If the device is valid and it contains an ext2 filesystem(and not swap and not ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

File System Check Failed
Please repair manually and reboot.  Note that the root file system is currently mounted read-only.  To mount it type ... When you exit the maintenance shell the system will reboot automatically.

I ran e2fsck -b 8193 /dev/hda5 and /dev/sda5 but that didn't seem to do anything.  I know that when I installed Arch, I stipulated ext3 file system and not ext2.  Was that a mistake?  I didn't think it would be a problem.  I'm just more familiar with ext3 and that's why I did it.  Any ideas on this one.  I appreciate all your help so far.

Last edited by Thrillhouse (2007-05-30 19:30:00)


For the strength of the pack is the wolf, and the strength of the wolf is the pack.

Offline

#9 2007-05-30 20:03:32

insane
Member
Registered: 2006-06-04
Posts: 106

Re: Messed up menu.lst

Try

 fsck.ext3 -fv

In your /etc/fstab the type is set to ext2 or ext3?

Offline

#10 2007-05-30 21:13:56

Thrillhouse
Member
From: Arlington, VA, USA
Registered: 2007-05-29
Posts: 175

Re: Messed up menu.lst

Found it.  fstab was mounting /dev/hda5 instead of /dev/sda5.  Didn't even check for that.  You got me going in the right direction, insane.  Of course now, I have yet another error.  I wanted to put my /home directory on a separate partition so I could share it between distros so I did that during the install process but I think I may have fudged it up.  The entry in fstab right now is:

/dev/sda3 /home/myUser ext3 defaults 0 0

When I log in to run level 3, it logs me in with HOME=/.  If I change the fstab entry to mount the partition to a different user's directory then everything is fine.  I have all the directories and files that I had in home when I first started using Arch.  But that makes me think that my home is not actually on sda3 but sda5. 

I also have a problem with trying to log in at Gnome's login screen.  I get these errors:

User's $HOME/.dmrc file is being ignored.  This prevents the default session and language from being saved.  File should be owned by user and have 644 permissions.  User's $HOME directory must be owned by user and not writeable by any other users.

I click OK on that and then get this second error:

Your session only lasted less than 10 seconds.  If you have not logged out yourself this could mean that there is some installation problem or that you may be out of disk space.  Try logging in with one of the failsafe sessions to see if you can fix this problem.

I'm thinking this is probably related to the problem above but I can't figure out how to fix it.  I've tried deleting and recreating the user but that gives me the same error.  I've tried chmod 644 /home/myUser but that doesn't do anything either.  Again, your help is greatly appreciated and sorry for being such a noob.

Last edited by Thrillhouse (2007-05-30 21:14:52)


For the strength of the pack is the wolf, and the strength of the wolf is the pack.

Offline

#11 2007-05-30 23:26:43

loserveg
Member
From: Pittsburgh, Pa
Registered: 2006-12-22
Posts: 45

Re: Messed up menu.lst

hi thrillhouse, i did the same thing when i created my home partition, your fstab should actually only mount the home directory

my fstab for home directory:

/dev/sda4 /home ext3 defaults,noatime 0 1

not sure if youll have to recreate your user or not, if you get taht session error again just go ahead and try recreating it next.
~matt

Last edited by loserveg (2007-05-30 23:27:27)

Offline

#12 2007-05-31 00:52:56

Thrillhouse
Member
From: Arlington, VA, USA
Registered: 2007-05-29
Posts: 175

Re: Messed up menu.lst

OK.  I changed it.  Rebooted, tried to log in and got an error message something along the lines of "Your home directory is /home/myUser but does not appear to exist." Then it asks me if I want to log in with / as my home directory.  I did that but it won't let me cd into /home and I'm afraid that if I create the directory as root, it won't have the right permissions.  What to do?


For the strength of the pack is the wolf, and the strength of the wolf is the pack.

Offline

#13 2007-05-31 03:45:12

loserveg
Member
From: Pittsburgh, Pa
Registered: 2006-12-22
Posts: 45

Re: Messed up menu.lst

did you try to remove your user and recreate it with your fstab like mine? i mean, the way youre going, using / as your home directory, its just not the way to go if you have a separate /home partition.

really all you should have to do after you remove your user is:

useradd -m -s /bin/bash myUser

and you should be set, it should create your /home/myUser directory on the /home partition with no errors.

right now its looking for /home/myUser which doesnt exist because you had set it up earlier that your /home directory was actually /home/myUser...so if you look at it that way, your user directory was setup up to be /home/myUser/myUser which isnt right...so if you delete the user and recreate it with the correct mounting of the /home directory you should be solid.

^^that is my thought process^^

~matt

Offline

#14 2007-05-31 04:00:51

Thrillhouse
Member
From: Arlington, VA, USA
Registered: 2007-05-29
Posts: 175

Re: Messed up menu.lst

Yeah.  That's basically what I did.  I fixed fstab, rebooted, then used userdel to get rid of the user and then ran the same command you posted to re-create it.  Rebooted again, tried to log in with that user and got the error.  The weird thing is that the directory does exist.


For the strength of the pack is the wolf, and the strength of the wolf is the pack.

Offline

#15 2007-05-31 05:51:32

loserveg
Member
From: Pittsburgh, Pa
Registered: 2006-12-22
Posts: 45

Re: Messed up menu.lst

yeah i dont know man, the only other thing i can think of is reformatting the /home partition and trying again.

i mean, its either some kind of config file that is still linked to the wrong thing or saying yes to using / as home could have done something.

im sorry i dont have a "concrete" solution, when it happened to me i did like i told you, come to think of it i deleted everything in /home, dot-files and all before recreating my user...so maybe that is it.

***throws hands in the air

yeah try either of those, see if it works
~matt

Offline

#16 2007-05-31 14:18:01

insane
Member
Registered: 2006-06-04
Posts: 106

Re: Messed up menu.lst

Maybe the partition you are trying to use is totally empty. Try to mount it somewhere else and the copy in that partition the contents of /home directory. Make sure you use cp with  -R -p switches. When you mount a device to a folder then the contents of the folder are hidden and can't be accessed.

Offline

#17 2007-05-31 17:40:22

Thrillhouse
Member
From: Arlington, VA, USA
Registered: 2007-05-29
Posts: 175

Re: Messed up menu.lst

It wasn't totally empty but it only had the barebones in it: .bash_profile, .bashrc, .xinitrc and .xsession.  I remounted to a different directory and tried copying the contents over but it didn't get all of the hidden files and directories with it and I can't find an option in the cp man page to do that.  I also don't have scp to do it and can't get it because the machine is not connected to the internet.  AHH.


For the strength of the pack is the wolf, and the strength of the wolf is the pack.

Offline

#18 2007-05-31 20:34:30

loserveg
Member
From: Pittsburgh, Pa
Registered: 2006-12-22
Posts: 45

Re: Messed up menu.lst

this is a pain huh lol

im stuck on fixing the fstab and then:

userdel -r myUser
sudo rm -R /home/myUser
useradd -m -s /bin/bash myUser

and even that is a bit redundant cuz userdel -r should clear out all the files connected with myUser and then the rm -R should basically do the same thing (hell it probably will throw an error saying that the directory is not found), so there shouldnt be any files/users connected with myUser at that point. then you create the user with fresh directory.

who knows, try again maybe? lol

im really hoping that someone will see some small thing that we're missing so we can get this working for you
~matt

Last edited by loserveg (2007-05-31 20:35:17)

Offline

#19 2007-05-31 21:42:30

Thrillhouse
Member
From: Arlington, VA, USA
Registered: 2007-05-29
Posts: 175

Re: Messed up menu.lst

Aha!  Got it.  I wasn't using the -r option when deleting my user and I think that's what might have saved it.  I can now log in graphically and am sharing /home between arch and fedora 7.  Thanks a lot loserveg.  Maybe you wouldn't mind helping me with this pesky resolution problem.  Haha, I know it seems like my problems never end but this one I just can't get straightened out and probably shouldn't be too much trouble.  I can log in graphically now but it's at 1024x768.  I have a 24 inch monitor that supports up to 1920x1200.  I'm trying to get to that resolution but just adding that resolution to the default depth in xorg.conf throws an error saying to set the monitor to 1920x1200 at 60 hz.  I looked up the specs of the monitor and found this:

Max Sync Rate (V x H)
   
76 Hz x 81 kHz

I tried setting horizsync and vertrefresh to those values but it gave me another, different X error.  I've been running hwd -x to generate new xorg.conf's and have been tinkering with them but I can't find a configuration that works for me.  Any ideas?


For the strength of the pack is the wolf, and the strength of the wolf is the pack.

Offline

#20 2007-05-31 22:15:16

loserveg
Member
From: Pittsburgh, Pa
Registered: 2006-12-22
Posts: 45

Re: Messed up menu.lst

well i googled a bit and it seems that you cant put 1920x1200 in the xorg.conf but rather Modes "1920x1200_60.00" which tells it to set it to 1920x1200@60Hz

dont know if that will work and dont come after me if some unforseen thing happens to your monitor lol but you can always try

Offline

#21 2007-06-01 17:47:39

Thrillhouse
Member
From: Arlington, VA, USA
Registered: 2007-05-29
Posts: 175

Re: Messed up menu.lst

Hmmm, that didn't work.  I added it as a mode to the default depth and restarted X.  The GUI came up fine but 1920x1200 was not listed as a resolution when I went to change it.  And not for any refresh rate.  I'll post my xorg.conf in case anybody can find something that might be wrong.

Section "ServerLayout"
    Identifier     "Xorg Configured"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
# PS/2 Mouse not detected
# Serial Mouse not detected
        InputDevice    "USB Mouse" "CorePointer"
EndSection

Section "ServerFlags"
    Option "AllowMouseOpenFail"  "true"
    
EndSection

Section "Files"
    RgbPath      "/usr/share/X11/rgb"
    ModulePath   "/usr/lib/xorg/modules"
    FontPath     "/usr/share/fonts/misc:unscaled"
    FontPath     "/usr/share/fonts/misc"
    FontPath     "/usr/share/fonts/75dpi:unscaled"
    FontPath     "/usr/share/fonts/75dpi"
    FontPath     "/usr/share/fonts/100dpi:unscaled"
    FontPath     "/usr/share/fonts/100dpi"
    FontPath     "/usr/share/fonts/PEX"
# Additional fonts: Locale, Gimp, TTF...
    FontPath     "/usr/share/fonts/cyrillic"
#    FontPath     "/usr/share/lib/X11/fonts/latin2/75dpi"
#    FontPath     "/usr/share/lib/X11/fonts/latin2/100dpi"
# True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
    FontPath     "/usr/share/fonts/Type1"
    FontPath     "/usr/share/fonts/ttf/western"
    FontPath     "/usr/share/fonts/ttf/decoratives"
    FontPath     "/usr/share/fonts/truetype"
    FontPath     "/usr/share/fonts/truetype/openoffice"
    FontPath     "/usr/share/fonts/truetype/ttf-bitstream-vera"
    FontPath     "/usr/share/fonts/latex-ttf-fonts"
    FontPath     "/usr/share/fonts/defoma/CID"
    FontPath     "/usr/share/fonts/defoma/TrueType"
EndSection

Section "Module"
        Load  "ddc"  # ddc probing of monitor
    Load  "dbe"
    Load  "dri"
    Load  "extmod"
    Load  "glx"
        Load  "bitmap" # bitmap-fonts
    Load  "type1"
    Load  "freetype"
    Load  "record"
EndSection

Section "InputDevice"
    Identifier  "Keyboard0"
    Driver      "keyboard"
        Option      "CoreKeyboard"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    Option "XkbLayout" ""
    Option "XkbVariant" ""
EndSection

Section "InputDevice"
    Identifier  "Serial Mouse"
    Driver      "mouse"
    Option      "Protocol" "Microsoft"
    Option      "Device" "/dev/ttyS0"
    Option      "Emulate3Buttons" "true"
    Option      "Emulate3Timeout" "70"
    Option        "SendCoreEvents"  "true"
EndSection

Section "InputDevice"
    Identifier  "PS/2 Mouse"
    Driver      "mouse"
    Option      "Protocol" "auto"
    Option          "ZAxisMapping"          "4 5"
    Option      "Device" "/dev/psaux"
    Option      "Emulate3Buttons" "true"
    Option      "Emulate3Timeout" "70"
    Option        "SendCoreEvents"  "true"
EndSection

Section "InputDevice"
        Identifier      "USB Mouse"
        Driver          "mouse"
        Option          "Device"                "/dev/input/mice"
    Option        "SendCoreEvents"    "true"
        Option          "Protocol"              "IMPS/2"
        Option          "ZAxisMapping"          "4 5"
        Option          "Buttons"               "5"
EndSection

# Auto-generated by Archie mkxcfg

Section "Monitor"
    Identifier "Monitor0"
        Option "DPMS" "true"
#    HorizSync    28.0 - 78.0 # Warning: This may fry very old Monitors
    HorizSync    28.0 - 96.0 # Warning: This may fry old Monitors
    VertRefresh  50.0 - 75.0 # Very conservative. May flicker.
#    VertRefresh  50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
    #  Default modes distilled from
    #      "VESA and Industry Standards and Guide for Computer Display Monitor
    #       Timing", version 1.0, revision 0.8, adopted September 17, 1998.
    #  $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
    # 640x350 @ 85Hz (VESA) hsync: 37.9kHz
    ModeLine "640x350"    31.5  640  672  736  832    350  382  385  445 +hsync -vsync
    # 640x400 @ 85Hz (VESA) hsync: 37.9kHz
    ModeLine "640x400"    31.5  640  672  736  832    400  401  404  445 -hsync +vsync
    # 720x400 @ 85Hz (VESA) hsync: 37.9kHz
    ModeLine "720x400"    35.5  720  756  828  936    400  401  404  446 -hsync +vsync
    # 640x480 @ 60Hz (Industry standard) hsync: 31.5kHz
    ModeLine "640x480"    25.2  640  656  752  800    480  490  492  525 -hsync -vsync
    # 640x480 @ 72Hz (VESA) hsync: 37.9kHz
    ModeLine "640x480"    31.5  640  664  704  832    480  489  491  520 -hsync -vsync
    # 640x480 @ 75Hz (VESA) hsync: 37.5kHz
    ModeLine "640x480"    31.5  640  656  720  840    480  481  484  500 -hsync -vsync
    # 640x480 @ 85Hz (VESA) hsync: 43.3kHz
    ModeLine "640x480"    36.0  640  696  752  832    480  481  484  509 -hsync -vsync
    # 800x600 @ 56Hz (VESA) hsync: 35.2kHz
    ModeLine "800x600"    36.0  800  824  896 1024    600  601  603  625 +hsync +vsync
    # 800x600 @ 60Hz (VESA) hsync: 37.9kHz
    ModeLine "800x600"    40.0  800  840  968 1056    600  601  605  628 +hsync +vsync
    # 800x600 @ 72Hz (VESA) hsync: 48.1kHz
    ModeLine "800x600"    50.0  800  856  976 1040    600  637  643  666 +hsync +vsync
    # 800x600 @ 75Hz (VESA) hsync: 46.9kHz
    ModeLine "800x600"    49.5  800  816  896 1056    600  601  604  625 +hsync +vsync
    # 800x600 @ 85Hz (VESA) hsync: 53.7kHz
    ModeLine "800x600"    56.3  800  832  896 1048    600  601  604  631 +hsync +vsync
    # 1024x768i @ 43Hz (industry standard) hsync: 35.5kHz
    ModeLine "1024x768"   44.9 1024 1032 1208 1264    768  768  776  817 +hsync +vsync Interlace
    # 1024x768 @ 60Hz (VESA) hsync: 48.4kHz
    ModeLine "1024x768"   65.0 1024 1048 1184 1344    768  771  777  806 -hsync -vsync
    # 1024x768 @ 70Hz (VESA) hsync: 56.5kHz
    ModeLine "1024x768"   75.0 1024 1048 1184 1328    768  771  777  806 -hsync -vsync
    # 1024x768 @ 75Hz (VESA) hsync: 60.0kHz
    ModeLine "1024x768"   78.8 1024 1040 1136 1312    768  769  772  800 +hsync +vsync
    # 1024x768 @ 85Hz (VESA) hsync: 68.7kHz
    ModeLine "1024x768"   94.5 1024 1072 1168 1376    768  769  772  808 +hsync +vsync
    # 1152x864 @ 75Hz (VESA) hsync: 67.5kHz
    ModeLine "1152x864"  108.0 1152 1216 1344 1600    864  865  868  900 +hsync +vsync
    # 1280x960 @ 60Hz (VESA) hsync: 60.0kHz
    ModeLine "1280x960"  108.0 1280 1376 1488 1800    960  961  964 1000 +hsync +vsync
    # 1280x960 @ 85Hz (VESA) hsync: 85.9kHz
    ModeLine "1280x960"  148.5 1280 1344 1504 1728    960  961  964 1011 +hsync +vsync
    # 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz
    ModeLine "1280x1024" 108.0 1280 1328 1440 1688   1024 1025 1028 1066 +hsync +vsync
    # 1280x1024 @ 75Hz (VESA) hsync: 80.0kHz
    ModeLine "1280x1024" 135.0 1280 1296 1440 1688   1024 1025 1028 1066 +hsync +vsync
    # 1280x1024 @ 85Hz (VESA) hsync: 91.1kHz
    ModeLine "1280x1024" 157.5 1280 1344 1504 1728   1024 1025 1028 1072 +hsync +vsync
    # 1600x1200 @ 60Hz (VESA) hsync: 75.0kHz
    ModeLine "1600x1200" 162.0 1600 1664 1856 2160   1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 65Hz (VESA) hsync: 81.3kHz
    ModeLine "1600x1200" 175.5 1600 1664 1856 2160   1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 70Hz (VESA) hsync: 87.5kHz
    ModeLine "1600x1200" 189.0 1600 1664 1856 2160   1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 75Hz (VESA) hsync: 93.8kHz
    ModeLine "1600x1200" 202.5 1600 1664 1856 2160   1200 1201 1204 1250 +hsync +vsync
    # 1600x1200 @ 85Hz (VESA) hsync: 106.3kHz
    ModeLine "1600x1200" 229.5 1600 1664 1856 2160   1200 1201 1204 1250 +hsync +vsync
    # 1792x1344 @ 60Hz (VESA) hsync: 83.6kHz
    ModeLine "1792x1344" 204.8 1792 1920 2120 2448   1344 1345 1348 1394 -hsync +vsync
    # 1792x1344 @ 75Hz (VESA) hsync: 106.3kHz
    ModeLine "1792x1344" 261.0 1792 1888 2104 2456   1344 1345 1348 1417 -hsync +vsync
    # 1856x1392 @ 60Hz (VESA) hsync: 86.3kHz
    ModeLine "1856x1392" 218.3 1856 1952 2176 2528   1392 1393 1396 1439 -hsync +vsync
    # 1856x1392 @ 75Hz (VESA) hsync: 112.5kHz
    ModeLine "1856x1392" 288.0 1856 1984 2208 2560   1392 1393 1396 1500 -hsync +vsync
    # 1920x1440 @ 60Hz (VESA) hsync: 90.0kHz
    ModeLine "1920x1440" 234.0 1920 2048 2256 2600   1440 1441 1444 1500 -hsync +vsync
    # 1920x1440 @ 75Hz (VESA) hsync: 112.5kHz
    ModeLine "1920x1440" 297.0 1920 2064 2288 2640   1440 1441 1444 1500 -hsync +vsync
    # Additional modelines
    ModeLine "1800x1440"  230    1800 1896 2088 2392  1440 1441 1444 1490 +HSync +VSync
    ModeLine "1800x1440"  250    1800 1896 2088 2392  1440 1441 1444 1490 +HSync +VSync
    # Extended modelines with GTF timings
    # 640x480 @ 100.00 Hz (GTF) hsync: 50.90 kHz; pclk: 43.16 MHz
    ModeLine "640x480"  43.16  640 680 744 848  480 481 484 509  -HSync +Vsync
    # 768x576 @ 60.00 Hz (GTF) hsync: 35.82 kHz; pclk: 34.96 MHz
    ModeLine "768x576"  34.96  768 792 872 976  576 577 580 597  -HSync +Vsync
    # 768x576 @ 72.00 Hz (GTF) hsync: 43.27 kHz; pclk: 42.93 MHz
    ModeLine "768x576"  42.93  768 800 880 992  576 577 580 601  -HSync +Vsync
    # 768x576 @ 75.00 Hz (GTF) hsync: 45.15 kHz; pclk: 45.51 MHz
    ModeLine "768x576"  45.51  768 808 888 1008  576 577 580 602  -HSync +Vsync
    # 768x576 @ 85.00 Hz (GTF) hsync: 51.42 kHz; pclk: 51.84 MHz
    ModeLine "768x576"  51.84  768 808 888 1008  576 577 580 605  -HSync +Vsync
    # 768x576 @ 100.00 Hz (GTF) hsync: 61.10 kHz; pclk: 62.57 MHz
    ModeLine "768x576"  62.57  768 816 896 1024  576 577 580 611  -HSync +Vsync
    # 800x600 @ 100.00 Hz (GTF) hsync: 63.60 kHz; pclk: 68.18 MHz
    ModeLine "800x600"  68.18  800 848 936 1072  600 601 604 636  -HSync +Vsync
    # 1024x768 @ 100.00 Hz (GTF) hsync: 81.40 kHz; pclk: 113.31 MHz
    ModeLine "1024x768"  113.31  1024 1096 1208 1392  768 769 772 814  -HSync +Vsync
    # 1152x864 @ 60.00 Hz (GTF) hsync: 53.70 kHz; pclk: 81.62 MHz
    ModeLine "1152x864"  81.62  1152 1216 1336 1520  864 865 868 895  -HSync +Vsync
    # 1152x864 @ 85.00 Hz (GTF) hsync: 77.10 kHz; pclk: 119.65 MHz
    ModeLine "1152x864"  119.65  1152 1224 1352 1552  864 865 868 907  -HSync +Vsync
    # 1152x864 @ 100.00 Hz (GTF) hsync: 91.50 kHz; pclk: 143.47 MHz
    ModeLine "1152x864"  143.47  1152 1232 1360 1568  864 865 868 915  -HSync +Vsync
    # 1280x960 @ 72.00 Hz (GTF) hsync: 72.07 kHz; pclk: 124.54 MHz
    ModeLine "1280x960"  124.54  1280 1368 1504 1728  960 961 964 1001  -HSync +Vsync
    # 1280x960 @ 75.00 Hz (GTF) hsync: 75.15 kHz; pclk: 129.86 MHz
    ModeLine "1280x960"  129.86  1280 1368 1504 1728  960 961 964 1002  -HSync +Vsync
    # 1280x960 @ 100.00 Hz (GTF) hsync: 101.70 kHz; pclk: 178.99 MHz
    ModeLine "1280x960"  178.99  1280 1376 1520 1760  960 961 964 1017  -HSync +Vsync
    # 1280x1024 @ 100.00 Hz (GTF) hsync: 108.50 kHz; pclk: 190.96 MHz
    ModeLine "1280x1024"  190.96  1280 1376 1520 1760  1024 1025 1028 1085  -HSync +Vsync
    # 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz
    ModeLine "1400x1050"  122.61  1400 1488 1640 1880  1050 1051 1054 1087  -HSync +Vsync
    # 1400x1050 @ 72.00 Hz (GTF) hsync: 78.77 kHz; pclk: 149.34 MHz
    ModeLine "1400x1050"  149.34  1400 1496 1648 1896  1050 1051 1054 1094  -HSync +Vsync
    # 1400x1050 @ 75.00 Hz (GTF) hsync: 82.20 kHz; pclk: 155.85 MHz
    ModeLine "1400x1050"  155.85  1400 1496 1648 1896  1050 1051 1054 1096  -HSync +Vsync
    # 1400x1050 @ 85.00 Hz (GTF) hsync: 93.76 kHz; pclk: 179.26 MHz
    ModeLine "1400x1050"  179.26  1400 1504 1656 1912  1050 1051 1054 1103  -HSync +Vsync
    # 1400x1050 @ 100.00 Hz (GTF) hsync: 111.20 kHz; pclk: 214.39 MHz
    ModeLine "1400x1050"  214.39  1400 1512 1664 1928  1050 1051 1054 1112  -HSync +Vsync
    # 1600x1200 @ 100.00 Hz (GTF) hsync: 127.10 kHz; pclk: 280.64 MHz
    ModeLine "1600x1200"  280.64  1600 1728 1904 2208  1200 1201 1204 1271  -HSync +Vsync
EndSection

# Auto-generated by Archie mkxcfg

Section "Device"
    Identifier  "Card0"
    Driver      "ati"
    VendorName  "All"
    BoardName   "All"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device     "Card0"
    Monitor    "Monitor0"
    DefaultColorDepth 16
    SubSection "Display"
        Depth     1
        Modes "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
        Depth     4
        Modes "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
        Depth     8
        Modes "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
        Depth     15
        Modes "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
        Depth     16
        Modes "1920x1200_60.00" "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
        Depth     24
        Modes "1920x1200_60.00" "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
        Depth     32
        Modes "1024x768" "800x600" "640x480"
    EndSubSection
EndSection

Section "DRI"
    Mode 0666
EndSection

For the strength of the pack is the wolf, and the strength of the wolf is the pack.

Offline

#22 2007-06-01 20:27:30

loserveg
Member
From: Pittsburgh, Pa
Registered: 2006-12-22
Posts: 45

Re: Messed up menu.lst

shouldnt there be a ModeLine for "1920x1200"?

Offline

#23 2007-06-01 20:34:32

Thrillhouse
Member
From: Arlington, VA, USA
Registered: 2007-05-29
Posts: 175

Re: Messed up menu.lst

I don't know.  That's the xorg.conf that hwd -x generated.  I've never used the ModeLine sections in an xorg.conf before on this monitor.  If I added a line for it, I wouldn't know what values to put in for everything.


For the strength of the pack is the wolf, and the strength of the wolf is the pack.

Offline

#24 2007-06-01 20:44:18

loserveg
Member
From: Pittsburgh, Pa
Registered: 2006-12-22
Posts: 45

Re: Messed up menu.lst

i used http://www.bohne-lang.de/spec/linux/modeline/ to calculate the modeline for 1920x1200@60Hz it gave me this

Horizontal Resolution:   1920
  Vertical Resolution:     1200
  Vertical Refresh Rate:   60.00 Hz
  Horizontal Refresh Rate: 74.69 KHz
  Dot Clock Frequence:     204.95 MHz

# V-freq: 60.00 Hz  // h-freq: 74.69 KHz
Modeline "1920x1200" 204.95  1920 2024 2272 2744  1200 1200 1203 1244

you might be able to get it to work using that

~matt

Offline

#25 2007-06-01 21:21:28

Thrillhouse
Member
From: Arlington, VA, USA
Registered: 2007-05-29
Posts: 175

Re: Messed up menu.lst

I added it but when I go to System -> Preferences -> Screen Resolution in Gnome, it doesn't list 1920x1200 as a resolution, only 1024x768, 800x600, 640x480 and 832x624.


For the strength of the pack is the wolf, and the strength of the wolf is the pack.

Offline

Board footer

Powered by FluxBB