Generic titles on DVR - why no title or specifics?
I record several series, and I find that sometimes I get a description.. sometimes not. Actually - most of the time, not. Why not episode title? I used to get this all the time with Cox - so I think it is put out by the individual shows.
The problem is when you go to watch it later.. you have no idea which episode is what, or if you have duplicate episodes. You have to play the beginning of each recording to figure out which one is which. I've ended up writing it down so I don't have duplicate episodes.. it is too hard to bring up each one and check it out every time.
This is not at all user friendly or consistent. Verizon needs to include more than the generic description when a customer uses the DVR to make it worth a customer's time and money to have this feature.
Plus it seems like I have to record all episodes, because checking for duplicates checks what? the title - which is always the same for a series? It is the episode title that changes.
What is the problem? why do I have this problem with Verizon, when I didn't have it with Cox?
Thanks.
Are you trying to tell us you have a problem reading long or repetitive "subject" lines?
I believe the main culprit is contained right here:
It very clearly says "ask your question"......... so they do...... and this is the window that one is presented with after choosing a community.
Similar Messages
-
Photos does not display generic title of image (ex: IMG_2234) as actual title. Is there a way to batch rename all photos using the generic title?
If you launch Script Editor and open the Help menu, you will see the APpleScript Help and a Language Guide:
To see, which commands an application understands, open the File menu in Script editor and select Open Dictionary. In the list locate "Photos".
You will see examples how o script Photos. -
IPhoto: Export videos with titles
All of my videos are in iPhoto, and I've added titles to all of the videos within iPhoto.
However, when I EXPORT these videos to my desktop, iPhoto doesn't export them with the titles that I've assigned to them in iPhoto.
iPhoto exports them with their generic title (such as "img_0015.mov") that they originally had when I first shot the videos.
How can I get iPhoto to export all of these videos with their titles intact?Are you checking this checkbox in the slideshow settings pane?
which will give you this in the slide:
OT -
Solution Manager Project Title
Is anyone aware of a method to get the project name in the title of the screen when an associate runs Solution Manager? If you look at the standard screen it displays a generic title like "Maintenance Cycle M000000010" or "Implementation Project I000000054".
Is anyone aware of a way (other than modifying SAP code) to get the screen to display the project title. Yes, I realize the project name is displayed in the body of the screen. We have a request to see if there's a way to make the project title more pronounced.Hi,
Additiion to the above, please check this blogs
Best Practice: Business Process Monitoring for Order to Cash
Best Practice: Business Process Monitoring for Procure to Pay
Thanks
Jansi -
Re-connecting titles to thumbnails
In the near past, when I changed the title of a thumbnail, the title on the page also changed. Somehow I've broken the link. How can I reestablish the link, please?
ThanksActually, I tried it on the delinquent chapter title and it didn't work. Then I copied a chapter title that did work, pasted it into the offending title page (where it immediately took on the title of that page, rather than what I'd copied). I deleted the title that wasn't cooperative and this one now works.
I think I had deleted the generic title text box that loads with "chapters" and substituted a normal text box, which wasn't linked.
Anyway, it works. Thanks. -
Not importing titles with photos
My wife recieves numerous emails with photos and imports them to iPhoto 9.1.5. The preferences are selected to import the titles but the pictures come in with generic titles only. When checking the mail download folder the titles are displayed correctly.
If you drag the photo from the email to the Desktop what is the file name that displays? If it's the title you want then import from there and see if it is kept.
OT -
I don't see a reason why we need generics.
i downloaded the current specification of generics in java and noticed that they do not work with primitive datatypes, only with Objects. so iam wondering why generics?
Generics which do only work with Objects is so stupid! all i can do with them is what i could also do with polyphormism! adding generics means to introduce a lot of bugs, incompatibility, making the language much more complicated (the compiler must get more complicated, more documents, the programmer need more knowledge).
SO WHY????? i do not see a reasonable reason for that!!!Basically generics add a significant
amount of additional compile time i think so too.
I would guess that at least 80% of typical commercial
code would benefit from generics over objects and have
little or no need for generics over primitive types.why will they benefit? and from what? generics will only restrict the flexibility and gain nothing!
for example it was possible to add Objects, Integers and Strings in one and the same Collection and extract them later with instanceof tests and there where now problems. you could also sort the whole collection with different kinds of objects stored in it(as long as they implement Comparable interface). with generics you don't have this flexibility anymore.
in c++, templates (a kind of generics) were very useful because they cold used together with operator overloading to program each algorithm unbeatable flexible and efficient. this will never be possible in java so what?
Finally yes the programmer will need to know a bit
more, but to paraphrase a great man, if you are tired
of learning you are tired of life.100% ACK! i will have no problems with it but others will. some things planned for the java 1.5 tiger released sounds very interesting (foreach loops, typesafe enums, covariant return types, etc.) but generics? why? -
Generic data extraction and loading to cube
Hello guys, I am trying to load R3 data thru Gernic extraction to infocube in bw3.5.
I just created generic DS and activated it and also Replicated in BW side.
I am trying to extract transaction data - from FI , DS has Ship Info Table fields in the extraction structure.
Everything got activated and now i am in BW side, just assigned DS to infosource.
But i am stuck in Transfer rules, all infoobjects on the left are empty and it wont let me activate.
I am really confused, Should i be creating infoobjects first , because i havent created infocube yet.
My DS has about 12 fields , I really need someone to tell me why its not activating Transfer rules, Comm structure is still empty.
Should i be creating INfocube first with KF and Chars?or how am i supposed to map these DS fields in the Infocube (my data target)?
I guess i am not clear at this point, even with LO extraction I could get create DS and replicate in BW , but once i am in BW i become clueless i should say.I did search other posts here but couldnt find anything that help me understand this.if someone could explain me in a simple terms i would appreciate it.
I have created DS with extraction structure, i am in BW , so whatever field i selected in extract structure in R3 side f rom the table , is that going to be Chars and Key figures in my Infocube once i complete Loading ? or how would that work? Why would we need to chose specific Table when creating view , assuming that we already know the data that we need for reporting purposes, we would know those data should be on what table correct?
please drop some lines to help me thankshello again, i am writing this since i didnt get any response. I would really appreciate it if someone could give me little hint , i have been practicing on my own using bw system and need help from you Pros.
My previous question was regarding Transfer rule . I am still not able to get through that steps.
This is what i have done so far:
-created DS generic for transaction data, using View VBAK table (not sure if this was the right table, i just wanted to see if i would be successful loading data in the cube).
- ACtivated DS, replicated in BW, Assigned INfosource.
- I selected 15 Fields from DS (extraction structure ) from that VBAK table.
- But when i am in Transfer rule ./structure screen, there are many fields appearing.
- It will let me active the Transfer Rules, however i also created InfoCube , it asked me to chose at least one Time Chars, and KF. But i used Template using my infosource, there were no KFs . so i figured i need to change Transfer rule. I tried to create Key figure infoobject on the right side of the screen in Transfer rules, but it will not move to the right when i tried to transfer it.
My question is, why there are more fields in this screen and some fields are not appearing the one i selected.
Since i chose transaction Generic DS,is that why i have to have Key figures? did i chose worng table VBAK for practice purpose? i dont really see much Keyfigures when i looked the content of this table using SE16.
Guys please suggest me , what route should i take to get through this confusion.
My main objective here is to simply load R3 data using Genric DS(transacitonal) into a customized infocube.
I get error when creating Update rule, infosource and infocube wouldn not link, i think its becoz i didnt have any keyfigures available when creating Infocube ? how would i chose one?
anyone please throw me some suggestions ..i would really appreciate it.thanks again for reading -
How do i keep imported clips in order?
I am using Premiere Essentials 13, Windows 8.1, 64
Canon Elura 100
Because I need to use a fire wire (which my new computer doesn't have), I downloaded my film to an older computer (Windows 7, 64 bit). I have 63 .avi files. They are date and time stamped, and I added a generic title after that info to each clip. I burned a DVD, then imported the files to my new computer to Adobe Premier Essentials 13. The files were all renamed to variations of VTS_01_0.BUP with a lot of redundancies. The files were then reordered according to the new names, which means they are completely out of order. What am I doing wrong?
Looking at the below info gleaned from an Adobe site, I tried importing with FileName, which seemed to be the right choice. Wondering if I should rename all 63 files consecutively, 01, 02 etc.
Thanks.
Select a naming convention for the downloaded files using the Presets menu.
FilenameRetains the filenames the camcorder assigns.
Folder Name - NumberIf your folder name is Wedding Pics, the clips are assigned the names Wedding Pics-001, Wedding Pics-002, and so on.
Date - filenameAdds a timestamp to the filename the camcorder assigns. The timestamp is the current date and time - the date and time on which the movies were transferred to your computer.note: To rename files, delete them from the Project Assets panel in the Expert view, and reimport them.
Custom Name - NumberEnter a custom name in the Name field. For example, if you enter My Holiday in the field, the clips are named My Holiday-001, My Holiday-002, and so on.aperture14
Could we go over your details to make sure that we are together on them?
You did a DV data (standard or widescreen) capture firewire using a program other than Premiere Elements for the capture. And, that resulted in 63 dv.avi files.
You mention burning those files to DVD disc. With your mention of file name such as VTS_01_0.BUP, it sounds to me that you burned one or more of the 63 dv.avi to DVD-VIDEO format on DVD disc. Why? If you wanted to save the .dv.avi files, why did you not just burn them to a DVD disc as a data disc so that you would have 63 dv.avi saved on the DVD disc instead of the VIDEO_TS Folder with all the structures of DVD-VIDEO format on that DVD disc?
If Premiere Elements 13 did still have the DV Capture feature, you would have been putting dv.avi type 2 on the Timeline as a result of the capture firewire. Also, do you know if whatever you used for the DV data capture produced dv.avi type 1 or dv.avi type 2. Did you use Movie Maker 2012?
Also, I wanted to make sure that you were not dealing with some special version of Premiere Elements 13.
When you wrote
"I am using Premiere Essentials 13, Windows 8.1, 64"
Did you mean Premiere Elements 13?
Please review and consider and then we can discuss this further.
Thank you.
ATR -
[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) -
My LR2 HD is dying and I need help!
Hi,
Sorry for the very generic title. I searched but didn't find a solution. 2 Days ago, my HD where all my photos are on started making a clicking sound. I have noticed since then that it only happens when LR2 is running and I'm working on stuff, there's nothing else stored on that ext HD. I back up every time that I start LR2 to another external HD.
Searching around, it looks like the LR2 catalog is located on my iMac and not on the LR2 drive and folder where all the photos are. So my question is, what is the best way to use the back up to use that drive as the "new" LR2 catalog? I will be buying a new HD to use as a backup. Also, I had uploaded some vacation shots prior to noticing the hard drive clicking noise. I just noticed it after another trip recently, so should I backup from an earlier backup? and how would I do that? thanks.
RichardRemove the bad drive. Open LR. You should now see ? next to files and folders previously linked to the files on the bad drive. Right click on the highest level folder in LR. Select locate folder and find the corresponding folder on the back up drive. LR will now update the location of the files. This works if your folder structure is consistent between the old drive and the back up drive. If it isn't you may have to follow this procedure folder by folder or even worse file by file.
Back ups are best kept in the same structure as the originals for this very reason. It is also why it is best to use a very simple folder structure for your image files and manage stuff using LR rather than the OS's folder structure. In my case everything is imported into one folder called Originals by date. This is backed up to a separate drive at time of import. The originals are converted to DNG on import and the back ups also using a separate back up catalog. The backup is then itself backed up to an on line service.
By the way, if the failing drive is an external drive connected by usb, you can always remove it from the housing and try directly connecting it as an internal drive. Sometimes this will allow you to at least copy the files over...however once a drive starts clicking it is best to bin it I am afraid after saving what you can. -
[SOLVED] Grub error 18 - cannot boot to Windows
Earlier today I tried to install Arch 64bit (I had 32bit earlier) with kdemod to test new KDE4.2. However, after installation I could not boot neither Arch nor Windows. Grub appeared, but every single option gave me an error. I can't remember anymore which error it was, but It doesn't matter anymore. I thought I had made a really stupid and basic mistake while installing, I just didn't know what.
I wanted to test KDE4.2 so much so I installed Kubuntu (yeah, this topic is not related to Arch Linux, I hope that somebody can help me though, move this topic to somewhere else if it doesn't belong here ). Installation was fine, booting to Kubuntu was fine (and upgrading to KDE4.2 was fine), but booting to Windows was not. It gave me a following error:
Error 18: Selected cylinder exceeds maximum supported by BIOS
I googled a bit and found this: http://wiki.linuxquestions.org/wiki/GRUB#Error_18 I reinstalled Kubuntu using /dev/sdb1 as /boot and /dev/sdb2 as / (/dev/sdb3 is windows and /dev/sdb4 is my game partition, ntfs). Before this I had /dev/sdb1 as / and /dev/sdb2 as swap (now I have no swap at all, my 4GB RAM should be enough). The only difference was that at first grub gave me error 15 (I fixed it with Kubuntu LiveCD). After that - no difference.
I need Windows for playing. That's why it's very important that I can use it. [SOLVED] In addition, I should say that /dev/sda is a separated hard drive which is encrypted with Truecrypt. (I said this because I think that Kubuntu tried to install grub on (hd0)...) When I tried to mount this hard drive with Kubuntu, it couldn't do it. I wanted to test mounting on Windows to check if it is just Kubuntu's problem. If not, I'm fucked because this hard drive contains VERY VERY VERY IMPORTANT files. [/SOLVED]
I really need help, please. If somebody can help me, (s)he is my hero.
Last edited by Exitium (2009-01-29 14:42:32)Oops, I forgot:
menu.lst:
(Yup, a lot of comments, Ubuntu style)
# 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 10
## 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=e85e83e5-0f7c-419e-8cad-1fe5d9128e8f ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=504fab5b-7bb6-4b20-af58-83677386de37
## 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 8.10, kernel 2.6.27-11-generic
uuid 504fab5b-7bb6-4b20-af58-83677386de37
kernel /vmlinuz-2.6.27-11-generic root=UUID=e85e83e5-0f7c-419e-8cad-1fe5d9128e8f ro quiet splash
initrd /initrd.img-2.6.27-11-generic
quiet
title Ubuntu 8.10, kernel 2.6.27-11-generic (recovery mode)
uuid 504fab5b-7bb6-4b20-af58-83677386de37
kernel /vmlinuz-2.6.27-11-generic root=UUID=e85e83e5-0f7c-419e-8cad-1fe5d9128e8f ro single
initrd /initrd.img-2.6.27-11-generic
title Ubuntu 8.10, memtest86+
uuid 504fab5b-7bb6-4b20-af58-83677386de37
kernel /memtest86+.bin
quiet
title Wintoosa
root (hd1,2)
savedefault
makeactive
map (hd0) (hd1)
map (hd1) (hd0)
chainloader +1
fdisk -l
(Note: These results are mainly in Finnish. It could be hard to you to read it... But whatever... I'll translate these only if necessary)
Levy /dev/sda: 640.1 Gt, 640135028736 tavua
255 päätä, 63 sektoria/ura, 77825 sylinteriä
Yksiköt = 16065 * 512 = 8225280 -tavuiset sylinterit
Levyn tunniste: 0xcc5d88e2
Laite Käynn Alku Loppu Lohkot Id Järjestelmä
/dev/sda1 * 244091 485122 1936074870+ b8 BSDI sivutus
Osion 1 loppu ei ole sylinterin rajalla.
/dev/sda2 176430 394864 1754572509+ 43 Tuntematon
Osion 2 loppu ei ole sylinterin rajalla.
/dev/sda3 177329 413105 1893868925 29 Tuntematon
Osion 3 loppu ei ole sylinterin rajalla.
/dev/sda4 57435 309703 2026342066 5c Priam Edisk
Osion 4 loppu ei ole sylinterin rajalla.
Osiotaulumerkinnät eivät ole levyjärjestyksessä
Levy /dev/sdb: 500.1 Gt, 500107862016 tavua
255 päätä, 63 sektoria/ura, 60801 sylinteriä
Yksiköt = 16065 * 512 = 8225280 -tavuiset sylinterit
Levyn tunniste: 0x0007a52a
Laite Käynn Alku Loppu Lohkot Id Järjestelmä
/dev/sdb1 1 128 1028128+ 83 Linux
/dev/sdb2 129 13185 104880352+ 83 Linux
/dev/sdb3 13186 26239 104856255 7 HPFS/NTFS
/dev/sdb4 26240 60801 277619265 7 HPFS/NTFS
Last edited by Exitium (2009-01-28 21:05:33) -
*I'm absolutely loving iPhoto '08.* Here's why:
• *It's SNAPPY* – much more responsive than '06, even with the 15K photos. The library loads instantly when I start up, even on my old MDD G4 tower and my sister's ancient iBook G4 with a paltry 768MB of memory.
• EVENTS - let me reorganize the last 10 years of digital photos (since my Apple QuickTake 150) in 2 hours. Seriously. I renamed all the Events with relevant titles and did a quick skim before settling on a key photo that helped me remember the context of my photos. I ended up merging certain events with relevant pictures instead of my previous "sea of rolls." I've found the visual cues from the key photo plus the title very useful in quickly locating the photo set I'm searching for. I think this is the best new feature of the suite.
• BOOKS – anyone else notice you can now have *FULL-BLEED book covers!?* No more forced color bars and generic title fonts. Oh and you can remove the Apple logo from the back. And no more gross canvas cover with those cheap design pasties! I find all this *especially useful for presenting iPhoto-printed portfolios to clients of my design work*. The page layouts look equally as flexible for creating full-bleed layouts in Photoshop and importing them. Has anyone been able to figure out how the pages handle bleed and trim? Does iPhoto account for bleed around the entire page even in the spine gutter?
Anyway... those are my thoughts for now... still picking through the nuances and undocumented "new features." Very exciting. Well worth the wait.
Anyone else uncover anything relevant or exciting that wasn't featured in the unveiling?ow about simple things - like being able to select which photos you bring in from your camera now? That is one giant step for me.
-
Ubuntu installed fine, Arch did, but won't boot.
Hello, I am trying out Arch Linux alongside Ubuntu Linux on my external USB drive. Ubuntu boots fine, but after I install Arch, GRUB comes up giving me error 17. I don't know what could be different between my two installations except that I installed Arch while my internal HD was in, while I installed Ubuntu while it wasn't. Help?
I set Ubuntu's menu.lst back for now, but still can't boot to Arch. I think I figured out why I can't (the install messes up when using GRUB, as GRUB can't figure out what file system it is on). Also, I think I may need to take out my internal HD to install it to the external (I had to do that with Ubuntu, but I was told it was just in case). Anyway, here is my menu.lst for my working Ubuntu (where the Arch Linux entry doesn't work because it says that that one is not supported by my BIOS for some odd reason), and the one for arch.
Ubuntu:
# 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 5
## 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=d76897f5-a728-4f06-b3d6-7291b03100fe ro vga=791 splash
## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)
## 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 7.10, kernel 2.6.22-14-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=d76897f5-a728-4f06-b3d6-7291b03100fe ro vga=791 splash quiet splash
initrd /boot/initrd.img-2.6.22-14-generic
quiet
title Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=d76897f5-a728-4f06-b3d6-7291b03100fe ro vga=791 splash single
initrd /boot/initrd.img-2.6.22-14-generic
title Ubuntu 7.10, kernel 2.6.22-13-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.22-13-generic root=UUID=d76897f5-a728-4f06-b3d6-7291b03100fe ro vga=791 splash quiet splash
initrd /boot/initrd.img-2.6.22-13-generic
quiet
title Ubuntu 7.10, kernel 2.6.22-13-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.22-13-generic root=UUID=d76897f5-a728-4f06-b3d6-7291b03100fe ro vga=791 splash single
initrd /boot/initrd.img-2.6.22-13-generic
title Ubuntu 7.10, kernel 2.6.22-12-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.22-12-generic root=UUID=d76897f5-a728-4f06-b3d6-7291b03100fe ro vga=791 splash quiet splash
initrd /boot/initrd.img-2.6.22-12-generic
quiet
title Ubuntu 7.10, kernel 2.6.22-12-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.22-12-generic root=UUID=d76897f5-a728-4f06-b3d6-7291b03100fe ro vga=791 splash single
initrd /boot/initrd.img-2.6.22-12-generic
title Ubuntu 7.10, kernel 2.6.22-10-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.22-10-generic root=UUID=d76897f5-a728-4f06-b3d6-7291b03100fe ro vga=791 splash quiet splash
initrd /boot/initrd.img-2.6.22-10-generic
quiet
title Ubuntu 7.10, kernel 2.6.22-10-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.22-10-generic root=UUID=d76897f5-a728-4f06-b3d6-7291b03100fe ro vga=791 splash single
initrd /boot/initrd.img-2.6.22-10-generic
title Ubuntu 7.10, memtest86+
root (hd0,0)
kernel /boot/memtest86+.bin
quiet
### END DEBIAN AUTOMAGIC KERNELS LIST
title Arch Linux
root /dev/sdb3
chainloader +1
Arch:
# Config file for GRUB - The GNU GRand Unified Bootloader
# /boot/grub/menu.lst
# DEVICE NAME CONVERSIONS
# Linux Grub
# /dev/fd0 (fd0)
# /dev/hda (hd0)
# /dev/hdb2 (hd1,1)
# /dev/hda3 (hd0,2)
# FRAMEBUFFER RESOLUTION SETTINGS
# +-------------------------------------------------+
# | 640x480 800x600 1024x768 1280x1024
# ----+--------------------------------------------
# 256 | 0x301=769 0x303=771 0x305=773 0x307=775
# 32K | 0x310=784 0x313=787 0x316=790 0x319=793
# 64K | 0x311=785 0x314=788 0x317=791 0x31A=794
# 16M | 0x312=786 0x315=789 0x318=792 0x31B=795
# +-------------------------------------------------+
# general configuration:
timeout 5
default 0
color light-blue/black light-cyan/blue
# boot sections follow
# each is implicitly numbered from 0 in the order of appearance below
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
# (0) Arch Linux
title Arch Linux
root (hd1,2)
kernel /boot/vmlinuz26 root=/dev/sdb3 ro
initrd /boot/kernel26.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd1,2)
kernel /boot/vmlinuz26 root=/dev/sdb3 ro
initrd /boot/kernel26-fallback.img
# (1) Windows
title Ubuntu Linux 7.10
rootnoverify (hd1,0)
makeactive
chainloader +1 -
ITMS Ignoring FeedBurner Link and Pulling Underlying Feed
Hello all,
I am running several podcasts in the iTMS via FeedBurner.
My blogging software is WordPress 2.04. I am using the PodPress plugin 6.7 for adding mp3 files into posts. I then take the WordPress / PodPress generated feed and hand it over to FeedBurner. I then have the FeedBurner feed toss over to the iTMS.
So, for example, the Criminal Law podcast is generated by WP / PP at http://www.lifeofalawstudent.com/category/1l/criminal-law/feed/ , tossed over to FeedBurner via http://feeds.feedburner.com/LoaLSCriminalLaw , and that FeedBurner feed is linked to the iTMS at http://phobos.apple.com/WebObjects/MZStore.woa/wa/viewPodcast?id=215665692 .
I actually have about 20 feeds, but unfortunately PodPress is built with the assumption you are only using your blog for a single podcast. As such, I must specify a single title for all feeds. For now, I have "Life of a Law Student" as the title supplied by WP / PP.
Within FeedBurner, I have Title Burner activated on all of the feeds. For Criminal Law, I have "LoaLS: Criminal Law" as the desired title, as opposed to the generic "Life of a Law Student".
When I look at the XML of FeedBurner, the title is set as "LoaLS: Criminal Law". However, when I look in the iTMS, all of my podcasts have "Life of a Law Student" as the title. Additionally, when I subscribe to the FeedBurner feed via the iTunes player (ie Advanced -> Subscribe to Podcast), I am also given the generic "Life of a Law Student" title. (However, if I subscribe via Google Reader or BlogLines, I get the correct title of LoaLS: Criminal Law.)
As a side-note, even though Apple sent me the confirmation email stating that http://feeds.feedburner.com/LoaLSCriminalLaw was the podcast feed, when I ping the feed at https://phobos.apple.com/WebObjects/MZFinance.woa/wa/pingPodcast?id=215665692 the WP feed is listed, instead of the FeedBurner feed. (This does not explain why I'm getting the generic title when I subscribe to the feed manually, though.)
Any help would be greatly appreciated. Additionally, let me know if you need more technical details.
- Neil
PowerBook G4 12" Mac OS X (10.4.8)The image is correctly referenced in the feed and there is a suitable image at that address. It's not unusual for the Store to take some days to show the image after the podcast has been accepted - it's cached, and for some reason it's slower than updating episodes. Unfortunately changing the image URL may have delayed things. I should just wait it out - it will probably turn up eventually.
Maybe you are looking for
-
My ipod shuffle 4th generation cannot be reset
Hi I have an ipod shuffle 4th generation. It was working perfectly fine when suddenly it wouldnt charge and also it is not being detected by pc. I have windows 7 installed on my pc. I thought it would be frozen so I followed the resetting steps on th
-
can any1 help me out with my ipod touch....I had my ipod in my pocket on lock and when i pulled it out to use it,it had ipod disabled and underneath that it had connect to itunes....unfortunately i am unable to get into my ipod its like locked me out
-
Script Alert: "Sorry I could not process the following files" (Error Message using Image Processor)
I'm a seasoned Photoshop/Bridge CS5 user who recently upgraded to CS6. In Bridge I just ran my first Image Processor batch, trying to convert a set of RAW .NEF files to .PSD files with a basic editing action I created applied to them. Photoshop CS6
-
Mac OS locking Time Capsule files
I've put a bunch of video files on my Time Capsule so they're accessible both from my iMac and MacBook. They're in folder /videos. When I try to play them from my MacBook, I usually get the message "Item xxx.avi is used by Mac OS X and cannot be open
-
I used the code snippets to create a custom cursor and it works well. What if I want that cursor to change when it's clicked? Can I do that easy enough? Thanks.