You are not logged in.
Hello all,
I just finished installing Arch Linux from the core ISO which I downloaded from the site. The install went smoothly and booted up fine. Also I was able to install gnome and its extras fine as well. On the first boot after installing gnome I managed to get my resolution correct also. However later on after I installed compiz fusion everything with the resolution seems to be going wrong . My computer specs are shown below :
AMD 64 3200
Asus M2N MX-SE
2 GB Ram
Geforce 8600 GT
Viewsonic VA1918wm (Native resolution is 1440x900)
At the moment I can only manage to get upto 1024x768 and it looks quite bad at that resolution. I have attached the xorg.conf I have at the moment.
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
Load "dbe"
Load "record"
Load "extmod"
Load "glx"
Load "dri2"
Load "dri"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "G84 [GeForce 8600 GT]"
BusID "PCI:2:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
While I was trying to fix this I noticed I was encountering other problems also. For one I found that sometimes dhcpcd times out on booting up and I cant seemt o connect to the Internet on booting. Although I just thought of trying a static IP and I'll post if that helped later on.
Another problem is I found that I seem to get the following error randomly. Pressing ctrl + D after this just restarts the machine.
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Finally, while I boot up I noticed that it says "Mounting root partition as read only [DONE]" Is the root partition supposed ot be mounted as read only ? Attached my fstab just in case it is needed.
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
/dev/sda3 /boot ext3 defaults 0 1
/dev/sdb1 / ext3 defaults 0 1
/dev/sdb2 swap swap defaults 0 0
/dev/sdb3 /home ext3 defaults 0 1
As you can see I'm quite new to Arch Linux so any help would be deeply appreciated.
Last edited by FilledVoid (2009-09-11 16:28:28)
Offline
Another problem is I found that I seem to get the following error randomly. Pressing ctrl + D after this just restarts the machine.
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>
Finally, while I boot up I noticed that it says "Mounting root partition as read only [DONE]" Is the root partition supposed ot be mounted as read only ? Attached my fstab just in case it is needed.
# # /etc/fstab: static file system information # # <file system> <dir> <type> <options> <dump> <pass> none /dev/pts devpts defaults 0 0 none /dev/shm tmpfs defaults 0 0 #/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0 #/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0 #/dev/fd0 /media/fl auto user,noauto 0 0 /dev/sda3 /boot ext3 defaults 0 1 /dev/sdb1 / ext3 defaults 0 1 /dev/sdb2 swap swap defaults 0 0 /dev/sdb3 /home ext3 defaults 0 1
As you can see I'm quite new to Arch Linux so any help would be deeply appreciated.
Your /boot is on a different drive than the rest of your mountpoints. Is that normal?
And yes, the root partition is supposed to be mounted as read-only at first.
Offline
Your /boot is on a different drive than the rest of your mountpoints. Is that normal?
And yes, the root partition is supposed to be mounted as read-only at first.
I have two hard disks one has Windows on it. The boot partition is on the Windows disks. It worked previously so I naturally assumed it was the right way to do it .
Offline
try this:
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Modes "1440x900"
Depth 24
EndSubSection
EndSection
Last edited by aelfie (2009-09-08 06:39:37)
Offline
try this:
Section "Screen" Identifier "Screen0" Device "Device0" <snip>
His .conf calls his card Card0, not Device0.
I didn't have the problem you describe, so merely guessing, but I remember reading that there's a problem with the nvidia driver and dri, so try commenting out those entries in the "Modules" section.
Also, you could try renaming your .conf and seeing if X/compiz will be able to figure things out. Don't have much experience with Compiz myself, so YMMV. "X -configure" and "nvidia-xconfig" are both good starting points, and since you can get into the gui, "nvidia-settings" will rewrite your .conf as well.
Offline
try this:
Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Modes "1440x900" Depth 24 EndSubSection EndSection
Removed the Screen section and replaced it with the above but its still doign the same. Its even showing the same resolutions as before which are 1024x768, 800x600, 640x480, 512x384 , 400x300, 320x240 .
Offline
Whoops, try Card0 instead like Seleucius said. I edited the post.
Offline
Also, try using nvidia-setting to se what resolutions it detects.
Offline
Thank you for all your suggestions . I tried replacing the ID to Card0 but it didnt seem to fix it . However on the bright side I checked more threads on the forum and found some that helped out . :)
http://bbs.archlinux.org/viewtopic.php?id=75070&p=2
http://bbs.archlinux.org/viewtopic.php?id=72788
http://bbs.archlinux.org/viewtopic.php?id=76938
I copied the xorg.conf file from the third link and just made minor changes to it like removing all the resolutions I didn't need and now its working fine :).
Now Im just stuck with two problems. One is the following message which appears randomly.
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
******************* FILESYSTEM CHECK FAILED *************
* Please repair manually and reboot. Note that the root *
* filesystem is currently mounted read-only. To remount *
* it read-write type: mount -n -o remount,rw / *
* When you exit the mantenance shel the system will *
* reboot automatically. *
*********************************************************
A thread about the same can be found http://bbs.archlinux.org/viewtopic.php?pid=295384 but there isn't a solution on it.
The second is the intermittent problems with the Network being setup. Sometimes when I boot up it just says dhcpcd timedout and I won't be able to connect . However I can connect on another machine at the same time.
Took a look at the drive in question with gparted and it shows the below information:
/dev/sdb1 ext3 / 32.59 GB 4.92 GB 27.68 GB boot
By any chance is any of the above information relevant :x ?
Offline
So are all partitions ext3? The error is talking about ext2... so my guess is your /boot is ext2 and you are mounting as ext3? Paste output of 'fdisk -l' 'df -T' and 'mount'
Last edited by Chrysalis (2009-09-08 10:23:16)
Offline
Sorry for the delay Ill paste in the output of the above once I get home .
Last edited by FilledVoid (2009-09-09 04:27:55)
Offline
fdisk -l
[filledvoid@TheVoid ~]$ sudo fdisk -l
Password:
Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xfae7fae7
Device Boot Start End Blocks Id System
/dev/sda1 * 1 4462 35840983+ 7 HPFS/NTFS
/dev/sda2 4463 9728 42299145 f W95 Ext'd (LBA)
/dev/sda3 * 9562 9729 1349460 83 Linux
/dev/sda5 4463 9561 40957686 7 HPFS/NTFS
Disk /dev/sdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3eb33eb2
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 4255 34178256 83 Linux
/dev/sdb2 4256 4741 3903795 82 Linux swap / Solaris
/dev/sdb3 4742 9729 40066110 83 Linux
df -T
[filledvoid@TheVoid ~]$ df -T
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/sdb1 ext3 33641448 4613320 27319216 15% /
none tmpfs 1029244 144 1029100 1% /dev
none tmpfs 1029244 0 1029244 0% /dev/shm
/dev/sda3 ext3 1328204 44620 1216112 4% /boot
/dev/sdb3 ext3 39436780 449796 36983680 2% /home
/dev/sr0 udf 7608672 7608672 0 100% /media/BULLET
[filledvoid@TheVoid ~]$
mount
[filledvoid@TheVoid ~]$ mount
/dev/sdb1 on / type ext3 (rw)
none on /dev type tmpfs (rw,relatime,mode=755)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /dev/pts type devpts (rw)
none on /dev/shm type tmpfs (rw)
/dev/sda3 on /boot type ext3 (rw)
/dev/sdb3 on /home type ext3 (rw)
gvfs-fuse-daemon on /home/filledvoid/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=filledvoid)
/dev/sr0 on /media/BULLET type udf (ro,nosuid,nodev,uhelper=hal,uid=1000)
By any chance does anyone know if this has somethignt o do with not having UUID's entered for the disks in the fstab ?
Offline
Well, its just different symlinks that point to the same device (ls -lR /dev/disk/), but I've heard of it fixing problems before so i guess give UUID's a try if you want. If its a fresh install i would probably just reformat and reinstall again though while its still early... if you dont like the arch cd partitioner you can use something else to set up your partitions and then just mount when running the installer. Also, use the net install... youll be downloading the same pkgs 5min later after you reboot anyway - saves you from having to upgrade and deal with .pacnews (btw, the problem could also be .pacnews you havent taken care of).
Last edited by Chrysalis (2009-09-09 09:41:22)
Offline
If you have Win. on sda drive you could consider putting Arch's grub in mbr and boot Win and Arch from there. That way there is no need for /boot partition which you have as ext3(sda3) --which doesn't work. I've been doing it this way for years with no problem. That way you make a root and swap partition for Arch. Some create a separate /home partition too. Depending on your needs and experience try the simpler method I suggest. Have fun with Arch:)
Offline
Maybe he put /boot on the first drive so grub can see it? I dont know... Ive never put an OS on a second drive.
Last edited by Chrysalis (2009-09-10 08:45:08)
Offline
Sorry for the late reply. I put the boot partition there cause to be frank its the only way Ive been able to get Arch and WIndows to work without need of changing the boot sequence in the BIOS . Although there might be a way I guess I dont really know better at this point .
On the birght side suddenly my dhcp issues and disk issues seem to be fine after changing the fstab to use UUID's . Not sure why that would fix anything . if anyhting else could have changed it would be the increased boot time I get now after installing a ton of software I need .
Not sure I should mark this as solved at the moment but Im going to anyway just in case someone gets the same resolution problem. Ill post a new thread if the issue persists. Thank you all for the help
Offline