[Solved]Kerenel26 2.6.30-ARCH uname -r output.

Hello I just compiled from abs tree kernel (ver. 2.6.30-6).
And at login I got:
2.6.30-ARCH-gd258d93-dirty
At kernel ver. place.
WHy i got it I compiled from orginal PKGBUILD from abs tree (I nothing changed).
Last edited by SpeedVin (2009-09-12 08:08:40)

I disable this option in my config and delated src and pkg dir and still the same name
Kernel from repo don't have this issue.
Last edited by SpeedVin (2009-09-11 20:49:13)

Similar Messages

[SOLVED] nouveau error while booting arch

Hi!!! I'm newbie to arch, here is an error I can't solve myself. I search in google for solutions but they didn't solved. Please help me to solve this. I dual booted arch linux with window 8.1. After installation, while booting for the first time, this error occurred.
Here is the error I found.
[0.063411] Ignoring BGRT: Invalid status 0 (expected 1)
starting version 218
Arch_Linux: clean, 70622/18677760 files, 1643393/74703025 blocks
[ 15.759913] nouveau E[ PIBUST][0000:01:00.0] HUBO: 0xffffffff (0x1a
[ 15.759952] nouveau E[ PIBUST][0000:01:00.0] GPCO: 0x00000001 (0x1a
[ 15.823494] nouveau E[ PBUS][0000:01:00.0] MMIO: 0x00000000 FAULT a
[ 15.824050] nouveau E[ DRM]Pointer to TMDS table invalid
[ 15.824072] nouveau E[ DRM]Pointer to flat panel table invalid}
Last edited by aaa234 (2015-02-04 04:18:42)

aaa234 wrote:
runical wrote:
That is a different problem to be honest. I assume that you can login using your normal user? If you set up sudo you might be able to get into root by using
sudo su
and change the password like that.
I'm sorry if this is a noob question. Where do I type sudo su because as soon as the OS is booted, the system asks localhost login and password. I haven't installed any desktop environment yet. I only set up a password under arch-chroot but I can't login with and without that password.
I was assuming a normal installed environment with a normal user. Using "sudo su", you can abuse privileges granted by sudo to circumvent the password required by su. A well configured sudo should not allow this, but in this case it seemed likely that the system was not completely set up yet.
problem has been solved with this https://bbs.archlinux.org/viewtopic.php?id=168879
Then, if there are no more problems, please mark the thread as solved.

[SOLVED] Windows 8.1, lost Arch boot loader, cannot reinstall or boot

Hi all,
Apologies but I am only posting as I have exhausted my (admittedly quite limited) knowledge and have spent hours trying to get it back up and running but nothing seems to work at all. This will probably be quite long, apologies if there is something really obvious that I have missed on the Wiki or anywhere, but I'm only posting as I can't seem to get anywhere with it at all despite reading and trying.
Essentially I had a Toshiba Satellite p850-321 laptop (UEFI, secure boot off, fast boot off) which I had dual booting with Windows 8 and Arch using rEFInd. I then had several moments of madness, starting when for some reason - on very little sleep so didn't think - decided to upgrade Windows 8 to 8.1. Unsurprisingly (but a surprise for me at the time), it then booted straight into Windows 8.1, no rEFInd. In hindsight, it had probably just set itself as boot priority but I thought it had overwritten rEFInd with its own bootloader or set it back to default or something so started on a way to try and get it back.
I then spent many hours trying to get my old bootable Arch USB stick to work with no joy, updating it to the latest arch iso and all sorts. It eventually worked when I updated the laptop BIOS. Booted from the USB, chrooted into arch, reinstalled rEFInd, played around, eventually got it to reboot and display rEFInd but Arch wouldn't start. At this point I noticed that my fstab looked strange (devices/labels mixed up from what I expected), so followed the Beginner's Guide again and recreated the fstab. My disk is partitioned as follows (main partitions of note):
/dev/sda2 - Windows EFI partition
/dev/sda4 Windows 8.1
/dev/sda6 arch swap partition (archswap)
/dev/sda7 arch root partition (archroot)
/dev/sda8 arch home partition (archhome)
Couldn't get rEFInd to work so decided to start again with gummiboot. Installed gummiboot, followed Beginner's Guide to install and configure it. Edited arch.conf and after having to mess about with the location of vmlinuz-arch.efi in the conf file, I have the options part looking like this:
options root=/dev/sda7 rw
Now gummiboot loads on startup but all I get on trying to load Arch from gummiboot is the dreaded:
ERROR: device '' not found. Skipping fsck
ERROR: Unable to find root device ''.
I've tried changing the root in options in arch.conf to UUID, PARTUUID and even different partitions (just to see what happened...) - the same. Is it likely to be due to me recreating the fstab and something is messed up there?
Another problem is that now, whatever I do, I cannot boot from the USB again to get in to even try to fix anything. The laptop on boot just hangs for a while and then loads the gummiboot from the disk drive rather than from the USB (I've set the boot priority, everything) and nothing will allow me to boot from the USB. That is probably a secondary issue, I can probably try to reinstall the BIOS again and see if that helps.
If anyone has had anything similar and has any solutions I'd be really grateful - anything. I don't mind being shown to be incredibly stupid, I get that a lot so have a lot of experience! - just anything that can get me back into Arch again without having to reinstall from scratch!
Thanks.
Last edited by pilf (2013-11-02 19:45:44)

Thanks for replying, very much appreciated. The partitions were numbered sequentially, I only posted up the partitions that I thought were of interest to the issue (which wasn't very helpful!). The partitions are as follows:
Partition No Type
1 Win Recover
2 EFI System (EFI partition)
3 Microsoft Reserved
4 Microsoft Basic (Windows 8.1 installation)
5 Windows Recover
6 Linux Swap
7 Microsoft Basic (Arch root partition)
8 Microsoft Basic (Arch home partition)
9 Windows Recover
It looks like I have managed to solve it, but I admit I'm not sure what of the several changes I made that solved it. I managed to boot into the USB arch disk by resetting my BIOS back to defaults and then changing the boot order back, which was the only way it would boot the USB - without resetting back and putting the boot order back exactly how it was before it wouldn't boot from the USB. Anyway...
Checked the partitions with gdisk, no problems. I did sort the partitions as you mentioned, just in case. Changed the partition names using gdisk to the same names I had before (archroot, archhome, archswap). Changed the types from Microsoft Basic to Linux filesystem (partitions 7 and 8) and wrote the partition.
Mounted everything, chrooted, edited the gummiboot arch.conf file and noticed there were some strange characters in it, a forward slash before /root in the options for example. I had edited the arch.conf file from windows by booting into Windows, mounting the EFI partition (mountvol z: /s) and editing it that way, which would have messed up the formatting. It can't have only been that though as it wasn't booting anyway which is why I went into Windows to edit the file in the first place. Corrected the arch.conf file, rebooted and it booted. Some errors on boot which I need to correct but I can work on those as it boots into my arch installation.
So all solved. I thought I'd update just to say thanks for the advice and in case it helps anyone else in the future.

[SOLVED]Is there anybody using arch linux in coLinux?

Hei,guys!
I'm using arch linux in coLinux.I got the image file from sf and I successfully booted it on my machine,em,everything seemed to be OK.But when I tried to do this:
pacman -Syu
I got this message :
checking package integrity...
error: error while reading package /var/cache/pacman/pkg/gdbm-1.8.3-7-i686.pkg.tar.xz: Unrecognized archive format: Invalid or incomplete multibyte or wide character
error: failed to commit transaction (libarchive error)
Errors occurred, no packages were upgraded.
I think the pacman(maybe just libarchive) is too old to recognize the .pkg.tar.xz files. So dose someone have an idea to work out it?
Last edited by Cristie (2011-05-28 16:03:35)

@twilight0:yeah,I acknowledge that,but it didn't work at all. I guess you didn't understand my problem. You know, the pacman coudn't upgrade (in fact I was unable to install any packages) just because the libarchive package was out of date (it meant that I could do nothing with the .tar.xz files downloaded from the mirrors).So I solved the problem by doing like this(Stupid it is, but it really works):
1.Download libarchive from any of the mirrors around the world.
2.Find a way to access to the files you just downloaded.
3.Replace the original libarchive files.
4.Mofify the local db.It is OK to do this:go to /var/lib/pacman/local,rename the libarchive-VERSION to current version.
Then I found that depences need openssl >= 1.0.0, so try the same proccess with it.
So,now everything is running very well.
Last edited by Cristie (2011-05-28 16:20:03)

[SOLVED]3.18.5-1-ARCH + system-modules-load.service on Macbook Pro 9,2

After upgrading from 3.18.4-1-ARCH to 3.18.5-1-ARCH this weekend, my systemd service system-modules-load fails during bootup. I checked out
# systemctl status system-modules-load
and found nothing but a warning that my journal has been rotated and the log output is incomplete. I have not hunted down the log or rooted through dmesg as of yet - I need my system functional while working during the week, so I downgraded my kernel back to 3.18.4 for now (under which system-modules-load loads fine). I will reinstall 3.18.5 next weekend and see if I can locate the problem - this post is just a feeler to see if anyone else is encountering this problem with the latest kernel.
Last edited by Olorin (2015-02-06 03:08:31)

Yep. It was my own fault. I had been using the b43 driver for my BCM4331 wifi card, and recently switched to broadcom-wl. However, I still was trying to load b43 in /etc/modules-load even though I had removed the driver and module from my system. Not sure why my system only started complaining in 3.18.5, but in any case removing the offending .conf file solved the problem. Thanks, graysky.

[SOLVED] Installed Win 7, now Arch won't boot

Edit: To save anyone reading this all the way, the problem turned out to be a badly edited fstab. Sigh.
PROBLEM:
Grub loads, then loads the kernel, but the boot hangs a few seconds later with no real error messages.
BACKGROUND:
1) I needed to boot a native Windows 7 partition on my 128GB laptop SSD.
2) So, I used gparted in an Ubuntu Live USB to resize my existing Arch partition and create an NTFS partition for Win 7:
sda > sda1=Arch > sda2=ntfs > sda3=linux swap
Arch still booted fine after this (sda1).
3) I then installed windows 7 (BIOS install) onto the second partition (sda2). I don't know where or if it puts some system reserved partition - but I can't see anything in gparted.
4) chrooted from an Arch Live USB, reinstalled GRUB, including mkconfig step
5) *If* I recall, Arch then booted OK.
6) Booted into Windows and applied all updates, set windows to use UTC clock and updated my laptops BIOS. Reboot.
7) Win 7 boots fine from the grub menu from (hd0,2)
8) Arch starts booting, loads the kernel, then hangs after the kernel has loaded, but before gdm appears. With the following on screen:
[2.104597] INFO @wl_cfg80211_attach : Registered CFG80211 phy
I have tried chrooting and reinstalling linux and linux-headers and grub. But so far to no avail.
[SOLVED with face palm]
I installed syslinux using chroot, as it displays more startup messages. The boot was hanging at [a disk task is starting] or words to that effect. It was my USB stick, which I'd foolishly added to fstab with the "auto" option. Editing that out of fstab - and it's all good.
I'll leave this here in case anyone else does something this dumb.
Last edited by sultanoswing (2013-10-30 08:09:03)

fettouhi wrote:
Thanks for the clarification about the DAEMONS list. My DAEMONS list is:
DAEMONS=(!hwclock ntpd syslog-ng !network netfs crond @alsa dbus networkmanager ufw cupsd avahi-daemon samba)
when I try to enable alsa and dbus I get this
[root@andre ~]# systemctl enable alsa-store.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
[root@andre ~]# systemctl enable alsa-restore.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
[root@andre ~]# systemctl enable dbus.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
Is LVM handled automatically by systemd? The reason I ask is because I have the USELVM= set to YES in rc.conf.
I made the permanent transition to systemd and did not start alsa at all - sound works fine - so I never bothered with the alsa-store/alsa-restore service files at all - it just works! Also dbus gets handled by default in systemd so you don't need any starting of dbus service at all... it just works.

[SOLVED] Question about conky-lua-arch.

I've managed to get conky-lua-arch up and working except for one minor issue. When I launch it, it automatically displays on the far right side of my 2nd monitor. This leads me to believe its alignment is pre-configured to run on the right side of the screen, which is fine, but how do I get it to be on the right side of my "primary" monitor instead? I've looked thru /usr/share/conky-lua-arch/clock-rings.lua but could not find an alignment or position parameter. I also could not find any other conky-lua-arch config files to look at. Any tips or suggestions are appreciated, thanks.
EDIT: The config file was located elsewhere. Solved.
Last edited by GunnDawg (2015-05-22 08:53:10)

Please remember to mark the thread as solved https://bbs.archlinux.org/viewtopic.php?id=130309

[solve]android remote control of arch desktop

Hi.... i have been snooping round aur and found a few packages that claim to work as remote controls of an arch linux box with an android phone... unfortunately, none have been updated in over 12 months, and just dont install or work.... is anyone using any thing successfully?
Last edited by ninjaprawn (2012-11-19 17:10:28)

I know this post is solved and getting pretty old but I felt like I should add a few excellent suggestions to the list.
Splashtop 2 and Teamviewer are both nice programs for controlling ones Arch, or other LINUX desktop, with an Android, they both have apps for the iPhone too.. Splashtop is made for Ubuntu, however it is in the AUR and they also give you the source of course. Http://www.splashtop.com that's my favorite one cuz there's many quality options..
Also, there is one called wificheema, this one is not in the repositories as I just did a search and was left empty handed. I'm not quite sure if wificheema worked on Arch or not as it's been awhile since I've used it because of it's lack of a quality zoom feature, I believe that was the only issue and for me it was a deal breaker cuz I have a tiny screen on my phone..
@Maxp, those were brilliant ideas, I have no idea why they never crossed my mind before. So obvious when you think about it.. Thanks for those, I'm definitely gonna give those a shot on my Android cuz there's no splashtop for my model phone.
Have either of you tried with the RDP app. I used to have it for windows but am not sure if it's for LINUX as well..

[SOLVED]Some issues with fresh arch install.

I freshly installed arch after a pretty long period of time of using other distributions and forgot how many issues I have to deal with when using it.
Alsamixer does not detect my headphones when i plug them in...(does not mute / unmute automatically speakers / headphones)
And another issue with the xorg server i think, I have a notebook and after every reboot i have to look up after touchpad with xinput --list then --setprop <id>. How can I make it permanent? It's annoying.
Last edited by dede24ever (2014-12-27 22:11:08)

Add a command to toggle the auto-mute with the same key, perhaps?
Anyway, that command in my i3 set up does not effect the auto-mute mode so there may be something else going on in your system.
Ooops -- my mistake, my system does that as well...
Maybe something to do with pulseaudio -- I didn't have pulseaudio when I used i3 and I didn't notice that problem then.
EDIT: It might be wise to open a fresh thread for this specific problem -- be sure to use a descriptive title to get the attention of the sound experts (not me!).
Last edited by Head_on_a_Stick (2014-12-27 20:26:11)

[SOLVED] (U)EFI dualboot Win7 Arch Linux - partitions gone - recovery?

Hi everybody,
I have a slight problem with my (U)EFI dualboot system (Windows 7 and Arch Linux) which used to be configured using rEFInd like it is described in my previous post:
https://bbs.archlinux.org/viewtopic.php … 6#p1300356
<EFI PARTITION> is /dev/sda1 and I used to boot via <EFI PARTITION>\EFI\Boot\Bootx64.efi which then successfully either loaded Windows or Linux kernel.
Thanks to my own stupidity and a recent update of refind I decided to copy the new driver, font and icon folders to the <EFI PARTITION> in order to be up-to-date.
After doing so, the rEFInd boot menu had a third icon which said "Boot via \EFI\Boot\Bootx64.efi" and if I clicked on it a second rEFInd boot menu appeared with only the two icons for Windows 7 and Arch.
So I figured I could delete Bootx64.efi and ultimately did so, unfortunately. Afterwards I couldn't boot neither Windows nor Linux anymore.
Following this I went through my noumerous USB boot sticks in order to be able to recover the Bootx64.efi. Unfortunately the first USB stick was a Windows XP one which has the plop bootloader alongside:
http://www.plop.at/en/bootmanager/thebootmanager.html
Out of couriousity I entered this bootloader and found HDA and HDB (I assume resembling my SSD and my USB stick).
To my knowledge I didn't change anything but after entering the bootloader again I just found HDA left, HDB seemed to be gone. But I didn't think of anything bad happening yet.
Then I found a working Archiso which I booted and using blkid I couldn't find the partitions of my earlier system anymore, only its device and the USB stick:
/dev/sda: PTUUID="..." PTTYPE="gpt"
/dev/sdb1: UUID="..." LABEL="ARCH_201312" TYPE="..." and so on
/dev/sdb2: SEC_TYPE="msdos" and so on
Even within the EFI shell I could not detect any internal drive anymore (only fs0: which is the USB stick)
Using Archiso onboard tool testdisk I could find the old partitions. The correct result of the GPT from testdisk is:
Fri Jul 4 08:45:25 2014
Command line: TestDisk
TestDisk 6.14, Data Recovery Utility, July 2013
Christophe GRENIER <[email protected]>
http://www.cgsecurity.org
OS: Linux, kernel 3.12.1-3-ARCH (#1 SMP PREEMPT Tue Nov 26 11:17:02 CET 2013) x86_64
Compiler: GCC 4.8
Compilation date: 2013-08-06T08:42:31
ext2fs lib: 1.42.8, ntfs lib: libntfs-3g, reiserfs lib: 0.3.0.5, ewf lib: none
/dev/sda: LBA, HPA, LBA48, DCO support
/dev/sda: size 500118192 sectors
/dev/sda: user_max 500118192 sectors
/dev/sda: native_max 500118192 sectors
/dev/sda: dco 500118192 sectors
Warning: can't get size for Disk /dev/mapper/control - 0 B - 1 sectors, sector size=512
Hard disk list
Disk /dev/sda - 256 GB / 238 GiB - CHS 31130 255 63, sector size=512 - Samsung SSD 840 PRO Series, S/N:S12RNEAD322171L, FW:DXM04B0Q
Disk /dev/sdb - 2013 MB / 1920 MiB - CHS 1022 62 62, sector size=512 - SMI USB DISK, FW:1100
Disk /dev/sdc - 4210 MB / 4015 MiB - CHS 1020 130 62, sector size=512 - Generic Flash Disk, FW:8.07
Disk /dev/mapper/arch_root-image - 1478 MB / 1410 MiB - 2887680 sectors, sector size=512
Disk /dev/dm-0 - 1478 MB / 1410 MiB - 2887680 sectors, sector size=512
Partition table type (auto): Intel
Disk /dev/sda - 256 GB / 238 GiB - Samsung SSD 840 PRO Series
Partition table type: EFI GPT
New options :
Dump : No
Align partition: Yes
Expert mode : Yes
Analyse Disk /dev/sda - 256 GB / 238 GiB - CHS 31130 255 63
hdr_size=92
hdr_lba_self=1
hdr_lba_alt=500118191 (expected 500118191)
hdr_lba_start=34
hdr_lba_end=500118158
hdr_lba_table=2
hdr_entries=128
hdr_entsz=128
hdr_size=92
hdr_lba_self=500118191
hdr_lba_alt=1 (expected 1)
hdr_lba_start=34
hdr_lba_end=500118158
hdr_lba_table=500118159
hdr_entries=128
hdr_entsz=128
Trying alternate GPT
Current partition structure:
Trying alternate GPT
search_part()
Disk /dev/sda - 256 GB / 238 GiB - CHS 31130 255 63
FAT32 at 0/32/33
FAT1 : 4110-6150
FAT2 : 6151-8191
start_rootdir : 8192 root cluster : 2
Data : 8192-2097151
sectors : 2097152
cluster_size : 8
no_of_cluster : 261120 (2 - 261121)
fat_length 2041 calculated 2041
set_FAT_info: name from BS used
FAT32 at 0/32/33
MS Data 2048 2099199 2097152 [NO NAME]
FAT32, blocksize=4096, 1073 MB / 1024 MiB
NTFS at 146/251/42
filesystem size 249593856
sectors_per_cluster 8
mft_lcn 786432
mftmirr_lcn 2
clusters_per_mft_record -10
clusters_per_index_record 1
NTFS part_offset=1209008128, part_size=127792054272, sector_size=512
NTFS partition cannot be added (part_offset<part_size).
NTFS at 146/251/42
filesystem size 249593856
sectors_per_cluster 8
mft_lcn 786432
mftmirr_lcn 2
clusters_per_mft_record -10
clusters_per_index_record 1
MS Data 2361344 251955199 249593856
NTFS, blocksize=4096, 127 GB / 119 GiB
recover_EXT2: s_block_group_nr=0/160, s_mnt_count=1318/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 5242880
recover_EXT2: part_size 41943040
MS Data 251955200 293898239 41943040
ext4 blocksize=4096 Large file Sparse superblock, 21 GB / 20 GiB
recover_EXT2: s_block_group_nr=0/80, s_mnt_count=1317/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2621440
recover_EXT2: part_size 20971520
MS Data 293898240 314869759 20971520
ext4 blocksize=4096 Large file Sparse superblock, 10 GB / 10 GiB
recover_EXT2: s_block_group_nr=0/706, s_mnt_count=1317/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 23156049
recover_EXT2: part_size 185248392
MS Data 314869760 500118151 185248392
ext4 blocksize=4096 Large file Sparse superblock, 94 GB / 88 GiB
Results
P MS Data 2048 2099199 2097152 [NO NAME]
FAT32, blocksize=4096, 1073 MB / 1024 MiB
P MS Data 2361344 251955199 249593856
NTFS, blocksize=4096, 127 GB / 119 GiB
P MS Data 251955200 293898239 41943040
ext4 blocksize=4096 Large file Sparse superblock, 21 GB / 20 GiB
P MS Data 293898240 314869759 20971520
ext4 blocksize=4096 Large file Sparse superblock, 10 GB / 10 GiB
P MS Data 314869760 500118151 185248392
ext4 blocksize=4096 Large file Sparse superblock, 94 GB / 88 GiB
interface_write()
1 P MS Data 2048 2099199 2097152 [NO NAME]
2 P MS Data 2361344 251955199 249593856
3 P MS Data 251955200 293898239 41943040
4 P MS Data 293898240 314869759 20971520
5 P MS Data 314869760 500118151 185248392
simulate write!
TestDisk exited normally.
ext4 blocksize=4096 Large file Sparse superblock, 94 GB / 88 GiB
Now the question is: Can I - using testdisk or any other tool - recover those partitions successfully so I will be able to boot again afterwards? I tested and I could mark them as:
P Primary
Any help will be greately appreciated.
Best regards
Last edited by blablubb1234 (2014-07-08 09:20:08)

Issue resolved If you care to know how, read on:
Looking at the disk using gdisk was doing no good. Neither of the recovery options in gdisk did the trick.
I then returned to testdisk and restored the partitions (successfully). However, afterwards I was greeted by shell telling me the root device was not found (seems like UUIDs get changed when one restores them using testdisk). Adjusting the PARTUUID for root in <EFI SYSTEM PARTIITION>/boot/refind_linux.conf did the trick and I could boot up Archlinux again.
Windows 7 still didn't boot telling me the required device was inaccessible (probably wrong UUID, too). I could however not restore/edit Windows' BCD using bcdedit, see my post Status: 0xc0000225 boot selection failed; required device inaccessible:
To make a long story short: Removing bcd and running autorecovery from withing Windows RE successfully created a new bcd. Unfortunately, Windows writes its backup bootloader at <EFI SYSTEM PARTITION>/boot/EFI/Boot/bootx64.efi. This file originally was a copy of refind_x64.efi which I need to put at that location to be able to dualboot. After chrooting to my Arch system I could restore bootx64.efi, create a new fstab and everything is running fine now again.
Best regards and thanks for the help.

[SOLVED] Installing Windows XP after Arch Linux

I'm not sure at all where to post this, so I've decided to do it here since I have the problem on a laptop... Please move if it should be somewhere else.
I installed Arch Linux on my new laptop a month ago or so, and am very pleased to have found the very kind of distro I've been looking for. However, I'm having trouble with my graphics (either wine doesn't support it, or the drivers don't have 2D/3D acceleration), and now I want to install Windows XP next to Arch Linux.
Using a GParted LiveCD, I've repartitioned the harddrive as such: Unpartitioned Space (27GB), Linux (197GB), SWAP (5GB).
I've also removed the bootable flag from the Linux partition, just to be sure. However, when I try to install Windows XP, it gets stuck after unpacking a bunch of drivers, giving me a bluescreen that tells me to make sure the hardware isn't broken, check my harddrive with CHKDSK /F, or look for viruses. Ofcourse I know none of these are true, since I'm running Arch Linux just fine.
A friend suggested that maybe my hardware isn't supported by Windows XP, which sounds like the most reasonable explanation so far, but I can't find a list of supported hardware. The M$ homepage basicly says
"Pentium 233-megahertz (MHz) processor or faster (300 MHz is recommended)"
for CPU, which doesn't help me at all.
My hardware is:
Processor: Intel Celeron 2.2 Ghz
Memory: 2GB DDR2
Graphics: Intel 4500MHD
And the laptop is called an "eMachines E525", though that doesn't say much since there are very, very many called this.
Can anyone give me any hints as to what I might be doing wrong?
Last edited by Noxic (2010-05-29 18:44:32)

Sounds like something I'll want to do. Where did you download the drivers? Do I have to follow some guide? Thanks for the tip
EDIT:
Indeed I will want to install AHCI drivers, otherwise Arch Linux fails to boot quite badly. There is also a problem preventing me from booting when I'm using AHCI though;
At boot, Arch Linux checks /dev/sda1 (NTFS) for errors, and expects to check an ext2 filesystem. Obviously, however, /dev/sda1 is an NTFS filesystem.
Since it tries to read the NTFS partition as an ext2 filesystem, it panics. Arch Linux then prompts me for the root password (or Ctrl+D to reboot), but I've disabled root login and can therefore do nothing at this point.
I have a GParted livecd and the Arch Linux livecd, so editing files on any of the filesystem isn't a problem at all, but I don't know what to do at this point. Help?
Last edited by Noxic (2010-05-29 12:40:33)

[SOLVED] Booting windows 7 kills Arch

Hi,
I'm dual booting Arch with windows 7 and recently when I boot windows 7, I can't boot Arch afterwards.
After I shutdown windows, I start up my laptop again, I get the grub menu and select Arch. During boot I get a lot of output during the file system check ( I think, it's hard to see because it goes to fast; ) and then Arch freezes. The only thing that I can do is a force shut down with the power button. I boot again and launch the Arch Fallback kernel. That one is then able to boot but freezes when kdm is launched: I get the login screen for tty 1 but when the graphical login managers fires up I only get a black screen and everything freezes ( can't switch to a terminal or use ctrl+alt+backspace ). I have to force shutdown with the power button again. I boot up again, select the Fallback kernel again and everything works fine. After that I can boot with the normal Arch kernel without a problem.
Is there a way to log the output on the screen during boot up ? I've searched the logs in /var/log/ but can't find that output.
This only happens since yesterday. I was looking for CPU scaling modules and loaded the powernow-k8 module according to the wiki. The power manager of KDE needed additional modules, KDE loaded the modules itself and I put all the modules in /etc/rc.conf. Strange thing is that I also lost my wifi yesterday and it still doesn't work, not on Arch nor Windows ( Wired internet does work on both ).
While checking the the daemon.log I found this, don't know if it's really helpfull:
Jul 10 10:40:38 archlinux init: Entering runlevel: 3
Jul 10 10:40:56 archlinux kdm_greet[1959]: Cannot load /usr/share/apps/kdm/faces/.default.face: No such file or directory
Jul 10 10:41:23 archlinux polkitd[2291]: started daemon version 0.96 using authority implementation `local' version `0.96'
Jul 10 10:45:34 archlinux init: Switching to runlevel: 6
Jul 10 10:45:36 archlinux console-kit-daemon[2036]: WARNING: no sender
Jul 10 10:49:44 archlinux init: Entering runlevel: 3
Jul 10 10:50:02 archlinux kdm[1752]: X server startup timeout, terminating
Jul 10 10:50:18 archlinux kdm[1752]: X server termination timeout, killing
Jul 10 10:50:28 archlinux kdm[1752]: X server is stuck in D state; leaving it alone
Jul 10 10:50:28 archlinux kdm[1752]: X server for display :0 cannot be started, session disabled
Jul 10 10:52:00 archlinux init: Entering runlevel: 3
Jul 10 10:52:17 archlinux kdm[1778]: X server startup timeout, terminating
Jul 10 10:52:32 archlinux kdm[1778]: X server termination timeout, killing
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@$
Jul 10 10:55:13 archlinux kdm_greet[1927]: Cannot load /usr/share/apps/kdm/faces/.default.face: No such file or directory
Jul 10 10:55:41 archlinux polkitd[2260]: started daemon version 0.96 using authority implementation `local' version `0.96'
Jul 10 11:01:03 archlinux init: Switching to runlevel: 6
Jul 10 11:01:05 archlinux console-kit-daemon[2001]: WARNING: no sender
Jul 10 11:01:53 archlinux init: Entering runlevel: 3
Jul 10 11:02:08 archlinux kdm_greet[1972]: Cannot load /usr/share/apps/kdm/faces/.default.face: No such file or directory
Jul 10 11:02:36 archlinux polkitd[2296]: started daemon version 0.96 using authority implementation `local' version `0.96'
Jul 10 12:14:55 archlinux init: Switching to runlevel: 6
Jul 10 12:14:56 archlinux console-kit-daemon[2046]: WARNING: no sender
Jul 10 12:15:44 archlinux init: Entering runlevel: 3
Jul 10 12:16:02 archlinux kdm_greet[3950]: Cannot load /usr/share/apps/kdm/faces/.default.face: No such file or directory
Jul 10 12:16:28 archlinux polkitd[4252]: started daemon version 0.96 using authority implementation `local' version `0.96'
Jul 10 12:17:32 archlinux init: Switching to runlevel: 6
Jul 10 12:17:33 archlinux console-kit-daemon[4006]: WARNING: no sender
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@$
Jul 10 12:36:06 archlinux kdm_greet[1940]: Cannot load /usr/share/apps/kdm/faces/.default.face: No such file or directory
Jul 10 12:36:33 archlinux polkitd[2243]: started daemon version 0.96 using authority implementation `local' version `0.96'
Jul 10 13:08:40 archlinux dhcpcd[3147]: dhcpcd not running
Jul 10 13:08:41 archlinux dhcpcd[3153]: dhcpcd not running
Jul 10 13:08:41 archlinux dhcpcd[3160]: dhcpcd not running
Jul 10 13:08:43 archlinux dhcpcd[3164]: version 5.2.5 starting
Jul 10 13:08:43 archlinux dhcpcd[3164]: eth0: broadcasting for a lease
Jul 10 13:08:43 archlinux dhcpcd[3164]: eth0: offered from
Jul 10 13:08:44 archlinux dhcpcd[3164]: eth0: acknowledged from
Jul 10 13:08:44 archlinux dhcpcd[3164]: eth0: checking for
Jul 10 13:08:49 archlinux dhcpcd[3164]: eth0: leased for 259200 seconds
Jul 10 13:08:49 archlinux dhcpcd: eth0: MTU set to 1492
Jul 10 13:08:49 archlinux dhcpcd[3164]: forked to background, child pid 3189
Jul 10 13:34:19 archlinux init: Switching to runlevel: 6
Jul 10 13:34:21 archlinux console-kit-daemon[2006]: WARNING: no sender
Jul 10 13:35:14 archlinux init: Entering runlevel: 3
Jul 10 13:35:30 archlinux kdm_greet[1940]: Cannot load /usr/share/apps/kdm/faces/.default.face: No such file or directory
Jul 10 13:35:31 archlinux dhcpcd[1977]: dhcpcd not running
Jul 10 13:35:31 archlinux dhcpcd[1983]: dhcpcd not running
Jul 10 13:35:31 archlinux dhcpcd[1990]: dhcpcd not running
Jul 10 13:35:33 archlinux dhcpcd[2004]: version 5.2.5 starting
Jul 10 13:35:33 archlinux dhcpcd[2004]: eth0: rebinding lease of
Jul 10 13:35:33 archlinux dhcpcd[2004]: eth0: acknowledged from
Jul 10 13:35:33 archlinux dhcpcd[2004]: eth0: checking for
Jul 10 13:35:39 archlinux dhcpcd[2004]: eth0: leased for 259200 seconds
Jul 10 13:35:39 archlinux dhcpcd: eth0: MTU set to 1492
Jul 10 13:35:39 archlinux dhcpcd[2004]: forked to background, child pid 2182
Jul 10 13:35:58 archlinux polkitd[2280]: started daemon version 0.96 using authority implementation `local' version `0.96'
Jul 10 13:43:28 archlinux init: Switching to runlevel: 0
Jul 10 13:43:29 archlinux console-kit-daemon[2022]: WARNING: no sender
I had windows vista and windows 7 in dual boot with Mandriva linux for a year without any problem and right now I have absolutely no idea what's going on.
EDIT:
Tried it again to see if I could get some more information.
Apparently the first time I boot Arch after a windows boot, it doesn't really freeze. I tried to write down some of the output and after a while it continued for a second and stopped again and this went going on and on. It seems like it keeps looping the same output. I waited some more but I had to force shut down because my laptop was going nuts and overheating, it started to smell like burned electronics...
I was able to capture some of the output:
--[end trace 27ebd855... ]---
Call trace
[<ffffffff8117c420>] ? proc_lookup_de+0x20/0x100
[<ffffffff81009ec2>] ? system_call_fastpath
Code ff .. .. .. and a lot more of pairs of letters and numbers
The output at the beginning was to fast to see but the Call trace and Code kept on repeating.
After this I could boot up the Fallback kernel without a problem, kdm worked fine to, then rebooted using the normal kernel image like nothing happened before.
Any help would be appreciated,
Varg
Last edited by Varg (2010-07-11 10:46:57)

Well since it worked fine first it could only be the powernow-k8 module or the CPU scaling modules required by KDE. I'll check it out and report back.
EDIT:
Narrowed it down to the cpufreq_powersave and cpufreq_userspace modules. Powernow-k8, cpufreq_stats and cpufreq_ondemand work fine.
I disabled all the modules and then turned them back on one by one in rc.conf ( booting w7 everytime ). cpufreq_powersave turned on gave the strange output during boot but only a short version but completely ran down X or kdm after boot. With cpufreq_userspace I could boot but KDE froze right after login. Combination of the two modules resulted in being unable to boot.
Loading the modules after boot while running KDE gives no problem and since I'm a laptop user I could use the powersave module. I'll see if I can make KDE load that module automatically after login.
Thanks a lot for the tip !
Last edited by Varg (2010-07-11 10:42:02)

[SOLVED]pacman -Sf zim makes arch read-only filesystem

Hi,
Last night I was trying to install zim, it looks like there were a couple packages which weren't properly installed before. I googled the error I received and found somewhere on the forum the tip to use
pacman -Sf package
I ran the command and it installed some sort of new kernel, fstab, something with python, and zim of course. While it was installing the packages I noticed it moved a couple files around and I'm not quite sure what it all did. anyway when I booted arch this morning it didn't quite make it to gdm, so I quickly booted into ubuntu, mounted my arch partition changed the inittab to boot to init 3. I then noticed that it mounted the arch / as read-only, I looked around a bit seems like my /etc/fstab was moved to /etc/fstab.pacorig. Now before I start playing around and maybe break things more than they are, anyone have a tip about how to figure out everything that was changed?
I also noticed that I could login as root without having to use a password which I don't like at all, which is a little scary.
Last edited by whitethorn (2010-06-26 13:50:11)

First things first; using the -f/--force flag with pacman is the absolute last resort, when everything else fails, and when you know exactly what you're doing. Using it just because you found a tip on the forum, and clearly without thinking about the potential consequences, is just asking for trouble - and you've got it.
To fix: your pacman log will tall you what packages were installed, and also has a record of any install-time messages. Comb through that, and work out how to revert the major issues.
[edit] overlap with loafer - he was faster because he used fewer words.

[Solved] Can't boot into Arch after deleting some partitons

About 6 months ago I installed Arch on a machine that used to run Ubuntu. Had some trouble at the time getting to boot into Arch but somehow managed. Now eventually decided to delete the old Ubuntu partitons to free up some space using gparted. Arch partition number changed from sda12 to sda6.
On rebooting after deleting ubuntu partitions with gparted, I got an ubuntu splash screen and a whole lot of ubuntu boot options. Somehow these were all contained in my Arch's /boot/grub/menu.lst. Arch is all on one partition and no separate boot partition (which I had with Ubuntu - maybe I haven't deleted that and this is the problem?). Will need to check that out.
I can chroot into Arch and did the following -
grub> find /boot/grub/stage1
(hd0,5)
grub> root (hd0,5)
Filesystem type is ext2fs, partition type 0x83
grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded.
succeeded
Running "install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,5)/boot/grub/stage2 /boot/grub/menu.lst"... succeed
ed
Done.
grub>
The Arch /boot/grub/menu.lst had a whole lot of ubuntu stuff in it but I edited to the following -
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3
## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu
# Pretty colours
#color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
# examples
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,3)
title Arch uuid
#root (hd0,5)
uuid d15cf4f9-18ca-4ec5-95bc-db0f6f264736
kernel /boot/vmlinuz26 root=/dev/sda6 ro vga=775
intrd /boot/kernel26.img
title Arch hd
root (hd0,5)
kernel /boot/vmlinuz26 root=/dev/sda6
intrd /boot/kernel26.img
I have a bootinfo script which gives the following (from the chroot environment) -
Boot Info Script 0.55 dated February 15th, 2010
============================= Boot Info Summary: ==============================
=> Grub 0.97 is installed in the MBR of /dev/sda and looks on the same drive
in partition #6 for /boot/grub/stage2 and /boot/grub/menu.lst.
=> No boot loader is installed in the MBR of /dev/sdb
sda1: _________________________________________________________________________
File system: swap
Boot sector type: -
Boot sector info:
sda2: _________________________________________________________________________
File system: Extended Partition
Boot sector type: -
Boot sector info:
sda5: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Mounting failed:
mount: /dev/sda5 already mounted or sda5 busy
sda6: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Mounting failed:
mount: /dev/sda5 already mounted or sda5 busy
mount: /dev/sda6 already mounted or sda6 busy
sda7: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:
sda3: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 10.04.1 LTS
Boot files/dirs: /etc/fstab
sda4: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs: /grub/menu.lst /grub/grub.cfg /grub/core.img
sdb1: _________________________________________________________________________
File system: xfs
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:
=========================== Drive/Partition Info: =============================
Drive: sda ___________________ _____________________________________________________
Disk /dev/sda: 750.2 GB, 750155292160 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Partition Boot Start End Size Id System
/dev/sda1 417,690 6,554,519 6,136,830 82 Linux swap / Solaris
/dev/sda2 25,414,954 1,465,144,064 1,439,729,111 5 Extended
/dev/sda5 25,414,956 1,360,287,809 1,334,872,854 83 Linux
/dev/sda6 1,360,287,873 1,423,198,349 62,910,477 83 Linux
/dev/sda7 1,423,198,413 1,465,144,064 41,945,652 83 Linux
/dev/sda3 6,554,520 25,414,829 18,860,310 83 Linux
/dev/sda4 * 63 417,689 417,627 83 Linux
Drive: sdb ___________________ _____________________________________________________
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
Partition Boot Start End Size Id System
/dev/sdb1 2,048 1,953,523,711 1,953,521,664 83 Linux
blkid -c /dev/null: ____________________________________________________________
Device UUID TYPE LABEL
/dev/loop0 squashfs
/dev/sda1 2a95d85a-45fe-4584-88dd-0ee20e651ec5 swap
/dev/sda2: PTTYPE="dos" PART_ENTRY_SCHEME="dos" PART_ENTRY_TYPE="0x5" PART_ENTRY_NUMBER="2"
/dev/sda3 32495e1a-227c-4d23-9f63-b1319def0dd9 ext3
/dev/sda4 d6dc69b0-967d-4886-b62d-8c0d6be06b41 ext3
/dev/sda5 37971286-b8d3-4a1b-9f94-4008288fed6d ext3 data
/dev/sda6 d15cf4f9-18ca-4ec5-95bc-db0f6f264736 ext3 30GB-02
/dev/sda7 eb736131-b558-4404-9b83-7f1e6d9e76ae ext3 var
/dev/sda: PTTYPE="dos"
/dev/sdb1 0e83045d-a0bd-4d36-b61d-bdb905130dc2 xfs 1TB-04
/dev/sdb: PTTYPE="dos"
============================ "mount | grep ^/dev output: ===========================
Device Mount_Point Type Options
/dev/sda12 / ext3 (rw,commit=0)
=============================== sda3/etc/fstab: ===============================
# /etc/fstab: static file system information.
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1 = swap
/dev/sda1 none swap sw 0 0
# /dev/sda3 = root
#UUID=32495e1a-227c-4d23-9f63-b1319def0dd9
/dev/sda3 / ext3 relatime,errors=remount-ro 0 1
# /dev/sda4 = boot
# UUID=d6dc69b0-967d-4886-b62d-8c0d6be06b41
/dev/sda4 /boot ext3 relatime 0 2
# /dev/sda5 = home
# UUID=670eee83-0a3e-429c-863f-b9ecced9f97e
/dev/sda5 /home ext3 relatime 0 2
#/dev/sda6
#UUID=37971286-b8d3-4a1b-9f94-4008288fed6d
/dev/sda6 /home/ben/Data ext3 defaults,relatime 0 0
# /dev/sda7
# UUID=fdb14ca4-d71d-489f-a00e-6e608770674c
/dev/sda7 /var ext3 relatime 0 2
# /dev/sda8
/dev/sda8 /opt ext3 relatime 0 2
# /dev/sda10 - Arch
/dev/sda10 /mnt/arch ext3 relatime 0 2
# Not sure what this is doing here
# Have commented it out - May be the reason why xbmc and mythtv were crashing on dvd insert and play
# /dev/hda /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
# /dev/sde1
# uuid appears to be 644406B3570C1846 -> ../../sde1
#/dev/sde1 /home/ben/Data/TVRecordings-1TB01 xfs defaults,relatime 0 0
#1TB-01
UUID=76f3823a-81dc-45c9-a0b7-2bc6c3beb2f8 /media/1TB-01 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
d defaults, relatime
# 1TB-02
UUID=59cbf7a1-7008-40d0-96ed-c6f231823d4f /media/1TB-02 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
d defaults, relatime
# 1TB-03
UUID=0e936800-3c53-4b87-abc8-19be0ffca7f9 /media/1TB-03 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
d defaults, relatime
# 750GB-02 ext3 Partition
# UUID giving problems, trying with dev
# UUID=c23b9c9a-66fc-4256-9211-73156c1ac64a /media/750GB-02_ext3 ext3 defaults,relatime 0 0
/dev/sde2 /media/750GB-02_ext3 ext3 defaults,relatime 0 0
============================= sda4/grub/menu.lst: =============================
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3
## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu
# Pretty colours
#color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
# examples
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below
## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,3)
## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true
## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false
## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash
## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false
## Xen hypervisor options to use with the default Xen boot option
# xenhopt=
## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single
## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all
## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true
## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false
## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false
## ## End Default Options ##
title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-26-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-26-generic
title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-24-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-24-generic
title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-23-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-23-generic
title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-22-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-22-generic
title Ubuntu 10.04.1 LTS, memtest86+
root (hd0,3)
kernel /memtest86+.bin
quiet
### END DEBIAN AUTOMAGIC KERNELS LIST
============================= sda4/grub/grub.cfg: =============================
# DO NOT EDIT THIS FILE
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
function recordfail {
set recordfail=1
if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set 32495e1a-227c-4d23-9f63-b1319def0dd9
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
set locale_dir=($root)/grub/locale
set lang=en
insmod gettext
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.32-26-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-26-generic
menuentry 'Ubuntu, with Linux 2.6.32-26-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-26-generic ...'
linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-26-generic
menuentry 'Ubuntu, with Linux 2.6.32-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-24-generic
menuentry 'Ubuntu, with Linux 2.6.32-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-24-generic ...'
linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-24-generic
menuentry 'Ubuntu, with Linux 2.6.32-23-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-23-generic
menuentry 'Ubuntu, with Linux 2.6.32-23-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-23-generic ...'
linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-23-generic
menuentry 'Ubuntu, with Linux 2.6.32-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-22-generic
menuentry 'Ubuntu, with Linux 2.6.32-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-22-generic ...'
linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-22-generic
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux16 /memtest86+.bin
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux16 /memtest86+.bin console=ttyS0,115200n8
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Arch Linux (on /dev/sda10)" {
insmod ext2
set root='(hd0,10)'
search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
linux /boot/vmlinuz26 root=/dev/sda10 ro
initrd /boot/kernel26.img
menuentry "Arch Linux Fallback (on /dev/sda10)" {
insmod ext2
set root='(hd0,10)'
search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
linux /boot/vmlinuz26 root=/dev/sda10 ro
initrd /boot/kernel26-fallback.img
#### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
# From Arch grub menu.lst
# (0) Arch Linux
#title Arch Linux [/boot/vmlinuz26]
#root (hd0,0)
#kernel /vmlinuz26 root=/dev/sda3 ro
#initrd /kernel26.img
#Note: With a separate boot partition, omit /boot from the path, (i.e. type set prefix=(hdX,Y)/grub and insmod
(hdX,Y)/grub/linux.mod).
#This introduces the "linux" and "initrd" commands, which should be familiar (see #Configuration).
#An example, booting Arch Linux:
#set root=(hd0,5)
#linux /boot/vmlinuz26 root=/dev/sda5
#initrd /boot/kernel26.img
#boot
###menuentry "Arch1" {
###insmod ext2
###set root='(hd0,10)'
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
PARTITION
#linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
UBUNTU THIS IS THE ROOT PARTITION
#initrd /initrd.img-2.6.32-26-generic
###search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UU
ID
###linux /boot/vmlinuz-26 root=635d7d02-3f5b-4af6-9c74-16b2af8cc7fd ro quiet splash # ARCH'S ROOT UUID
###initrd /boot/kernel26.img
# /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
###menuentry "Arch2" {
###insmod ext2
###set root='(hd0,4)' #= TRYING UBUNTU'S BOOT
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
PARTITION
#linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
UBUNTU THIS IS THE ROOT PARTITION
#initrd /initrd.img-2.6.32-26-generic
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
###initrd /boot/kernel26.img
# /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
###menuentry "Arch3" {
###insmod ext2
###set root='(hd0,10)' #= TRYING UBUNTU'S BOOT IN HD FORMAT
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
PARTITION
#linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
UBUNTU THIS IS THE ROOT PARTITION
#initrd /initrd.img-2.6.32-26-generic
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
###initrd /boot/kernel26.img
# /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
### END /etc/grub.d/40_custom ###
=================== sda4: Location of files loaded by Grub: ===================
.0GB: grub/core.img
.0GB: grub/grub.cfg
.0GB: grub/menu.lst
.0GB: grub/stage2
.0GB: initrd.img-2.6.32-22-generic
.0GB: initrd.img-2.6.32-23-generic
.1GB: initrd.img-2.6.32-24-generic
.1GB: initrd.img-2.6.32-26-generic
.0GB: vmlinuz26
.0GB: vmlinuz-2.6.32-22-generic
.0GB: vmlinuz-2.6.32-23-generic
.1GB: vmlinuz-2.6.32-24-generic
.0GB: vmlinuz-2.6.32-26-generic
=============================== StdErr Messages: ===============================
No volume groups found
mdadm: No arrays found in config file or automatically
[/quote]
Output of fdisk -l from chroot is -
[quote]Disk /dev/sda: 750.2 GB, 750155292160 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0000b084
Device Boot Start End Blocks Id System
/dev/sda1 417690 6554519 3068415 82 Linux swap / Solaris
/dev/sda2 25414954 1465144064 719864555+ 5 Extended
/dev/sda3 6554520 25414829 9430155 83 Linux
/dev/sda4 * 63 417689 208813+ 83 Linux
/dev/sda5 25414956 1360287809 667436427 83 Linux
/dev/sda6 1360287873 1423198349 31455238+ 83 Linux
/dev/sda7 1423198413 1465144064 20972826 83 Linux
Partition table entries are not in disk order
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00025bd3
Device Boot Start End Blocks Id System
/dev/sdb1 2048 1953523711 976760832 83 Linux
I need to post this now and come back from a different machine to note the error messages I am now getting on boot. ...
Note that when I boot and press esc to get the menu I get the menu.lst I created (in the second quote) above in /dev/sda6, ie the one with the Arch hd and uuid entries - so grub is looking there and finding that menu.lst, but something goes wrong after that.
OK. Have now booted the machine and after pressing esc and selecting the uuid entry (the same thing happens with the hd entry) I get a whole lot of stuff, but what seems relevant is (typing it out) -
List of all partitions:
No filesystem could mount root, tried:
Kernel panic - not syncing: VS: Unable to mount root fs on unknown-block(0,0)
Pid: 1, comm: swapper Not tainted 2.6.39-Arch #1
If anyone can help I'd really appreciate it. This is my MythTV machine so the WAF is about to take a big dive!
If I could just install grub to the MBR as if this was a new installation of Arch that would be great.
I am really lost as to what is going on, which I'm sure is evident.
Thanks a lot
belbo
Last edited by belbo (2011-08-12 13:31:23)

Hi. Unfortunately that didn't help.
So next, based on this post https://wiki.archlinux.org/index.php/Ke … el_version I chrooted into Arch and (a) rolled back and (b) reinstalled my kernel but that didn't help either. I suspected it wouldn't because the kernel was working fine before I deleted the partitions in question.
[2011-08-08 23:32] ==> Image generation successful
[2011-08-08 23:32] upgraded kernel26 (2.6.39.3-1 -> 2.6.39.3-1)
I then did a pacman -Suy and the linux package has now replaced kernel26. ( See this wiki entry http://www.archlinux.org/news/changes-t … filenames/). I didn't change anything in menu.lst owing to this and it seems there is no need to. Unfortunately this hasn't helped either - still getting the kernel panic.
Pacman.log relating to the new kernel package below -
[2011-08-09 00:22] Running 'pacman -Suy'
[2011-08-09 00:22] synchronizing package lists
[2011-08-09 00:23] starting full system upgrade
[2011-08-09 00:23] Running 'pacman -Suy'
[2011-08-09 00:23] synchronizing package lists
[2011-08-09 00:23] starting full system upgrade
[2011-08-09 00:26] removed python-mygpoclient (1.5-1)
[2011-08-09 00:26] removed kernel26 (2.6.39.3-1)
[2011-08-09 00:26] warning: /boot/grub/menu.lst installed as /boot/grub/menu.lst.pacnew
[2011-08-09 00:26] upgraded grub (0.97-17 -> 0.97-19)
[2011-08-09 00:26] upgraded icu (4.8-1 -> 4.8.1-1)
[2011-08-09 00:26] upgraded linux-firmware (20110512-2 -> 20110727-1)
[2011-08-09 00:26] >>> Updating module dependencies. Please wait ...
[2011-08-09 00:26] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2011-08-09 00:26] ==> Building image from preset: 'default'
[2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2011-08-09 00:26] ==> Starting build: 3.0-ARCH
[2011-08-09 00:26] -> Parsing hook: [base]
[2011-08-09 00:26] -> Parsing hook: [udev]
[2011-08-09 00:26] -> Parsing hook: [autodetect]
[2011-08-09 00:26] -> Parsing hook: [pata]
[2011-08-09 00:26] -> Parsing hook: [scsi]
[2011-08-09 00:26] -> Parsing hook: [sata]
[2011-08-09 00:26] -> Parsing hook: [filesystems]
[2011-08-09 00:26] -> Parsing hook: [usbinput]
[2011-08-09 00:26] ==> Generating module dependencies
[2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2011-08-09 00:26] 7079 blocks
[2011-08-09 00:26] ==> Image generation successful
[2011-08-09 00:26] ==> Building image from preset: 'fallback'
[2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2011-08-09 00:26] ==> Starting build: 3.0-ARCH
[2011-08-09 00:26] -> Parsing hook: [base]
[2011-08-09 00:26] -> Parsing hook: [udev]
[2011-08-09 00:26] -> Parsing hook: [pata]
[2011-08-09 00:26] -> Parsing hook: [scsi]
[2011-08-09 00:26] -> Parsing hook: [sata]
[2011-08-09 00:26] -> Parsing hook: [filesystems]
[2011-08-09 00:26] -> Parsing hook: [usbinput]
[2011-08-09 00:26] ==> Generating module dependencies
[2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2011-08-09 00:26] 23360 blocks
[2011-08-09 00:26] ==> Image generation successful
[2011-08-09 00:26] installed linux (3.0.1-1)
I don't think I've mentioned that my old menu.lst seems to have disappeared and so must have been on one of the partitions that were deleted. I did have 2 Arch installations when I was setting things up months ago and that menu.lst may have been on the other partition but pointing to this partiton's kernel for booting. Presumably that's possible since this partiton is definitely the one I have been using for the last several months (confirmed by log and other files updated in the last few days etc). Even so, I suppose that probably wouldn't be relevant to this issue, since grub is finding the menu.lst on this partition when it boots so it is looking in the intended place now.
It seems I'm at a bit of a dead end. It seems these kernel panics are usually because there is something wrong with the kernel - which there wasn't with mine (and presumably the kernel in the new linux package is fine) or there is a typo in menu.lst (I can't see one and nobody has pointed one out yet) or menu.lst is pointing to the wrong partition (mine is pointing to the same partition and /boot directory that is found by grub - which is where my boot image is located - so it seems to be correct). I have nevertheless tried editing the menu.lst entry when booting to boot from different partitions but so far that hasn't worked either.
If anybody has other ideas I'd really appreciate it.
If not, some suggestions on re-installing would also be appreciated. I have a recent tar archive of the partition, but presumably reinstalling that wouldn't be of much use since it would just put back what is currently there. I guess that I need to format the partition, create a separate boot partition, do a fresh install of Arch into the formatted partition (and with boot in the new boot partition). And then restore my tar backup (excluding the boot directory) into the formatted partition?
Any assistance greatly appreciated.
Thanks
belbo
Last edited by belbo (2011-08-08 23:17:49)

[SOLVED] Grub Problems Can boot Arch w/ grub edits only

I had 3 Linux OS's installed on this computer, Arch and 2 versions of Ubuntu on one hard drive.
The MBR belonged to Ubuntu, using grub2. I decided to get rid of the older Ubuntu (sda8 and 9) and add it's HDD space to my Arch home (sda12). Used the current Gparted live to modify the partitions and all went well, but of course, the numbers changed getting rid of 2 partitions.
No boot upon restart so I decided to get Arch's grub back to the MBR with the new partition numbering scheme.
Using a live CD, I used the grub shell, find /boot/grub/stage1.....etc, etc. and after a bit of fumbling, grub indicated success in the shell. When I was through though, a reboot was not successful, although the current stable grub was now written to the MBR. I edited the lines using grub edit option, and got Arch to boot, and figured out the correct partition numbers. Next I edited the menu.lst to reflect the new sda numbers.
Now rebooting results in a long delay when grub should be on the screen, and the numbers on the Arch entries reflect the old numbers still!! I double checked thinking I forgot to save the edits to the menu.lst file, but they are correct. I can boot Arch, but have to edit the lines each time.
The current partitions are as follows. I edited the terminal output to show details.
[jeff@Arch2009p2 ~]$ sudo fdisk -l
Password:
Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000383e7
Device Boot Start End Blocks Id System
/dev/sda1 * 1 91201 732572001 5 Extended
/dev/sda5 1 255 2048224+ 82 Linux swap / Solaris
/dev/sda6 (ubuntu /) 256 1471 9767488+ 83 Linux
/dev/sda7 (ubuntu /home) 1472 22321 167477593+ 83 Linux
/dev/sda8 (arch boot) 22322 22325 32098+ 83 Linux
/dev/sda9 (arch /) 22326 23627 10458283+ 83 Linux
/dev/sda10 (arch /home) 23628 91201 542788123+ 83 Linux
I have a few questions regarding a separate boot partition for Arch.
Should the grub> root (hd0.0) command be directed to the root or boot partition.
My handy printed emergency guide says: Set grubs root device to the partition containing the boot directory.
OK.....Writing it out now, it seems clear, so I'll try reinstalling grub from a live CD.
Why does grub have incorrect partition numbers even though the menu.lst is correct?
There are only 2 OS's on this box now, and one contains grub2.
Is current grub able to interact with grub 2 if I screwed something up on the install?
Last edited by jeff story (2010-05-24 20:05:06)

OK
I managed to fix the problem of grub not reading/using the menu.lst file. Not sure WTF it was reading and where that file was located!
The problem seems to have been the most insignificant detail.
When using the grub terminal, I did not execute the quit command when I was through. I just closed the terminal and rebooted.
After repeating the following code via live CD a few times:
$ sudo grub
grub> find /grub/stage1
grub> root (hd0,7)
grub> setup (hd0)
Grub still didn't read the current menu.lst.
This morning I got things to work correctly and grub to read the current menu.lst by adding a quit command and returning to the linux shell prior to rebooting.
I used the following commands:
$ sudo grub
grub> find /grub/stage1
grub> root (hd0,7)
grub> setup (hd0)
grub> quit

[Solved]Kerenel26 2.6.30-ARCH uname -r output.

Similar Messages

Maybe you are looking for