Joined: Sat Oct 02, 2010 4:07 pm Posts: 2
eeePC model: 900
Aurora version: NBR 3.0.1
Hi,
We have been using an Asus Eee PC 900 for about a year. It showed up with Debian(?) which I replaced with Eeebuntu NBR 3.0. I've forgotten all the details, but I'm pretty sure it came from the Eeebuntu website (before Aurora).
Uname -a leads me to believe that grub has been running 2.6.29-1-netbook since my original installation over a year ago, but the update manager keeps updating 2.6.28-xx-generic.
Does the update manager need to be fixed so it updates 2.6.29-1-netbook or should I have done something to grub so that it runs the latest and greatest version of 2.6.28 even though it is generic? 29 seems new/better than 28, but that's just me.
The BIOS doesn't appear to have an option to boot from the new SDHC card, though it is visible from the linux.
Is there a way to make the BIOS boot from a partition on the SDHC card? How do I update the menu.lst in the internal card to point to the new operating system on the external SDHC card? Maybe uuid .... needs to be replaced with root(hd?,?). How do I determine what (hd?,?) should be?
The goal is to boot from a larger partition which can support more applications than is possible with the original 4GB card. Any advice would be appreciated. Would it be smarter/easier to dump/restore the 4GB partition onto the 16GB card? How would I do that? Should I take a chance on Aurora EB4 rather than pressing ahead with Eeebuntu NBR 3.0.1?
This is the /boot/grub/menu.lst from the 4GB internal card.
Code:
# 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=1a791cab-8d76-4cb7-a4e2-f0e092e204df ro
## default grub root device ## e.g. groot=(hd0,0) # groot=1a791cab-8d76-4cb7-a4e2-f0e092e204df
## 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
## specify if running in Xen domU or have grub detect automatically ## update-grub will ignore non-xen kernels when running in domU and vice versa ## e.g. indomU=detect ## indomU=true ## indomU=false # indomU=detect
## 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
title Eeebuntu 3.0, kernel 2.6.28-11-generic (recovery mode) root (hd1,4) kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=1a791cab-8d76-4cb7-a4e2-f0e092e204df ro single initrd /boot/initrd.img-2.6.28-11-generic
Update manager then installed 2.6.28-12-netbook. My original question about whether 2.6.29.1-generic would be superior to 2.6.28-xx still remains. It would be nice if the BIOS would boot directly to the new operating system, but at least it's working.
Users browsing this forum: No registered users and 2 guests
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum