My experience with printers is that of all the peripherals, regardless of OS, they are the trickiest to install, configure, and use. So I'm expecting a battle here.
What I have is a Canon Pixus iP3100. It's a Japanese model, but it's the same model as the US Canon Pixma iP3000, just a different name.
First, I plugged in the USB cable. CentOS seemed to detect it, and gave me a list of options. Neither the US model number nor Japanese model number was there, so I selected "Canon (unknown)". It spent a while installing, and then finished without any message to say for sure if it had installed successfully. I tried to print from a number of application, but nothing happened. Just nothing. No error messages, no printer noises, nothing.
So, I figured the driver didn't take hold.
I looked around the net, and first I cam across "Turboprint for Linux". At first it seemed promising. But my first snag was that after installing the RPM, I didn't seem to have any printer configuration dialogues or anything. I went on the net to see about a manual, and *then* I discovered that in the free, consumer use version, they stamp a logo onto whatever you print. I was a little annoyed that they didn't make that really clear up front, they just tell you that commercial users must pay and consumers can use for free.
Anyway, I decided to look for different alternatives. I came across a web site that said that my printer model could work under a different Canon driver: http://www.linuxprinting.org/pipermail/canon-list/2004q4/001797.html
But, and here's the heart of my question, I can't find any place to make changes to my printer configuration. According to some web sites I looked at, I should have a printer configuration application in my menu, under "Preferences". But all I have is a "printer settings" application which, despite the promising name, doesn't have any menu options at all for configuring the printer or it's drivers. It looks more like a print spool manager for when you have print jobs lined up.
Where/how do I configure my printer and try alternate drivers?
Dave
On Fri, 2005-08-19 at 14:08 +0900, Dave Gutteridge wrote:
My experience with printers is that of all the peripherals, regardless of OS, they are the trickiest to install, configure, and use.
Not if they have some on-board intelligence and do Postscript. Then it solves the problem for _every_ OS. ;->
Yeah, it means I pay $200-400 for a laser printer, but I use it for 5+ years. My latest is a Postscript Level 3 Dell 3100cn that I just picked up for $352 (shipped to my door and including tax). Before that it was a $299 Postscript Level 2 LaserJet 1220se (also scans and copies, including XSane support) as well as a $249 Postscript Level 2 Lexmark E310.
Postscript = eternally supported + 0 headaches in any OS
On Fri, 2005-08-19 at 14:08 +0900, Dave Gutteridge wrote:
My experience with printers is that of all the peripherals, regardless of OS, they are the trickiest to install, configure, and use. So I'm expecting a battle here.
What I have is a Canon Pixus iP3100. It's a Japanese model, but it's the same model as the US Canon Pixma iP3000, just a different name.
First, I plugged in the USB cable. CentOS seemed to detect it, and gave me a list of options. Neither the US model number nor Japanese model number was there, so I selected "Canon (unknown)". It spent a while installing, and then finished without any message to say for sure if it had installed successfully. I tried to print from a number of application, but nothing happened. Just nothing. No error messages, no printer noises, nothing.
So, I figured the driver didn't take hold.
I looked around the net, and first I cam across "Turboprint for Linux". At first it seemed promising. But my first snag was that after installing the RPM, I didn't seem to have any printer configuration dialogues or anything. I went on the net to see about a manual, and *then* I discovered that in the free, consumer use version, they stamp a logo onto whatever you print. I was a little annoyed that they didn't make that really clear up front, they just tell you that commercial users must pay and consumers can use for free.
Anyway, I decided to look for different alternatives. I came across a web site that said that my printer model could work under a different Canon driver: http://www.linuxprinting.org/pipermail/canon-list/2004q4/001797.html
But, and here's the heart of my question, I can't find any place to make changes to my printer configuration. According to some web sites I looked at, I should have a printer configuration application in my menu, under "Preferences". But all I have is a "printer settings" application which, despite the promising name, doesn't have any menu options at all for configuring the printer or it's drivers. It looks more like a print spool manager for when you have print jobs lined up.
Where/how do I configure my printer and try alternate drivers?
---- linuxprinting.org shows nothing (not surprising)
HP is working hard developing linux drivers for their stuff so I am not sure of the wisdom of buying a Canon that is largely unsupported. If you are to have any luck, it would seem that Turbo Print would be your best option.
Suggest that if you intend to buy a printer to use on Linux, you consult the resources before you buy a printer
Craig
On Thu, 2005-08-18 at 22:36 -0700, Craig White wrote:
Suggest that if you intend to buy a printer to use on Linux, you consult the resources before you buy a printer
Actually, given that Windows Vista is around the corner (next year), it's very likely the printer you buy now will not work on it, or will require you to pay for a driver upgrade. In fact, XP 64-bit has that problem right now (dearth of peripheral drivers).
It's all about the "Superstore Model." 90% of American consumers believe that if they upgrade any one of their computer, OS, software or peripheral, that if it forces an upgrade of any of the other 3, then they might as well get new for all 4. That's what peripherals now cater too, and that's why the BIOS-less PC and the host-based/software-driven peripheral are almost as Windows version-specific as the OS and applications these days.
Again, just an OT rambling. But the investments in Best Buy by Microsoft previously, and the immediate distribution changes that occurred as a result, were not coincidence. And it's not coincidence that most peripheral vendors are more than happy to work with this "superstore model," and even other software vendors have gotten in on it (e.g., AOL investments in Circuit City, etc...).
Let the buyer beware, for _any_ OS. ;->
Suggest that if you intend to buy a printer to use on Linux, you consult the resources before you buy a printer
This is not an option. I already have my printer, that I've had since long before the descision to switch to Linux. I do not have the finances to switch printers on a whim.
In any case, please note: I am not asking if Linux can or should support the printer I have. I've already read web sites which indicate it's possible. What I am asking is how and where I access printer configuration commands so that I may try the drivers that are suggested on the web sites I've read.
Dave
On Fri, 2005-08-19 at 14:53 +0900, Dave Gutteridge wrote:
This is not an option. I already have my printer, that I've had since long before the descision to switch to Linux. I do not have the finances to switch printers on a whim.
We understand this. I just let you know that you should consider researching to minimize your finances with Windows too.
In any case, please note: I am not asking if Linux can or should support the printer I have. I've already read web sites which indicate it's possible. What I am asking is how and where I access printer configuration commands so that I may try the drivers that are suggested on the web sites I've read.
This article seems step-by-step in setting up CUPS for your _exact_ model (Canon PIXUS iP3100, correct?): http://www.techbuilder.org/recipes/showArticle.jhtml?articleId=167600449
Understand your printer relies on 100% _Windows_only_ software. Not only that, but it seems to be 100% tied to _specific_ versions of Windows (I see many people complaining about it not being supported in a few versions of Windows).
Luckily, the CUPS wizards have been busy creating an emulation layer. As such, you can use a nice Postscript Printer Definition (PPD) file into this emulation layer so it can spit back out all that nasty, CPU/software driven printer code that makes your printer unable to print anywhere near the actual pages per minute (God I want to get vendors for "false advertising" on speeds due to 0 intelligence on the printer).
Now if the Cannon drivers don't work for you, I don't know what to tell you. But understand they probably won't look perfect, because CUPS is emulating the Windows Graphical Display Interface (GDI) layer. In fact, printouts between Windows versions probably won't match either.
[ Let alone Windows Vista chucks the GDI, meaning it will probably be quite useless for it. ;-]
This article seems step-by-step in setting up CUPS for your _exact_ model (Canon PIXUS iP3100, correct?): http://www.techbuilder.org/recipes/showArticle.jhtml?articleId=167600449
Thank you for that excellent article. And what a stroke of luck that the person us using my exact model.
All went well until the author of the article instructed to go to "Start Menu > Control Center > peripherals > printers". I have neither a "Control Center", nor a "Peripherals", let alone a "printers" anywhere in my menu. The author of the article is using KDE, but shouldn't there be something similar in Gnome?
Which, although I'm probably many steps ahead, I'm sort of back to my original question. Where do I access printer settings? Is there a GUI in Gnome for this? Is there one I can install?
Apparently I'm looking for an "add printer wizard", or anything that lets me properly install the "ppd" file that I've created for my printer.
Where can I administrate my printer settings?
Dave
Hi, I usually go Applications --> System Settings --> Printing that is the same as the command line /usr/bin/printconf-gui, included in the package system-config-printer-gui. To check if you have that package installed, just run the command
rpm -q system-config-printer-gui
if it is not installed, then you can easily get it via yum or up2date.
Cheers, have a nice day
Simone
Dave Gutteridge wrote:
This article seems step-by-step in setting up CUPS for your _exact_ model (Canon PIXUS iP3100, correct?): http://www.techbuilder.org/recipes/showArticle.jhtml?articleId=167600449
Thank you for that excellent article. And what a stroke of luck that the person us using my exact model.
All went well until the author of the article instructed to go to "Start Menu > Control Center > peripherals > printers". I have neither a "Control Center", nor a "Peripherals", let alone a "printers" anywhere in my menu. The author of the article is using KDE, but shouldn't there be something similar in Gnome?
Which, although I'm probably many steps ahead, I'm sort of back to my original question. Where do I access printer settings? Is there a GUI in Gnome for this? Is there one I can install?
Apparently I'm looking for an "add printer wizard", or anything that lets me properly install the "ppd" file that I've created for my printer.
Where can I administrate my printer settings?
Dave _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
system-config-printer-gui
Ah! There it is.
Well, Everything went according to plan as far as the web site instructions went.
However, when trying to print a test page, I got the following error output:
I [19/Aug/2005:18:07:16 +0900] Adding start banner page "none" to job 3. I [19/Aug/2005:18:07:16 +0900] Adding end banner page "none" to job 3. I [19/Aug/2005:18:07:16 +0900] Job 3 queued on 'Canon' by 'root'. I [19/Aug/2005:18:07:16 +0900] Started filter /usr/lib/cups/filter/pstops (PID 6160) for job 3. I [19/Aug/2005:18:07:16 +0900] Started filter /usr/lib/cups/filter/foomatic-rip (PID 6161) for job 3. I [19/Aug/2005:18:07:16 +0900] Started backend /usr/lib/cups/backend/usb (PID 6162) for job 3.
And at the command prompt where I had originally started system-config-printer-gui, I got these error messages:
No match for USB device: mfr "Canon" model "iP_3100" desc "Canon iP_3100" cmdset "BJL,BJRaster3,BSCCe" Please report this message in Bugzilla: https://bugzilla.redhat.com/bugzilla Choose 'foomatic' as the component.
Does anyone smarter than me (which is anyone) have any idea if there are any potential clues in this? Note that I'm fully prepared for my printer to not work. But I'm not ready to give up quite yet.
Dave
On Fri, Aug 19, 2005 at 06:11:07PM +0900, Dave Gutteridge enlightened us:
system-config-printer-gui
Ah! There it is.
Well, Everything went according to plan as far as the web site instructions went.
However, when trying to print a test page, I got the following error output:
I [19/Aug/2005:18:07:16 +0900] Adding start banner page "none" to job 3. I [19/Aug/2005:18:07:16 +0900] Adding end banner page "none" to job 3. I [19/Aug/2005:18:07:16 +0900] Job 3 queued on 'Canon' by 'root'. I [19/Aug/2005:18:07:16 +0900] Started filter /usr/lib/cups/filter/pstops (PID 6160) for job 3. I [19/Aug/2005:18:07:16 +0900] Started filter /usr/lib/cups/filter/foomatic-rip (PID 6161) for job 3. I [19/Aug/2005:18:07:16 +0900] Started backend /usr/lib/cups/backend/usb (PID 6162) for job 3.
And at the command prompt where I had originally started system-config-printer-gui, I got these error messages:
No match for USB device: mfr "Canon" model "iP_3100" desc "Canon iP_3100" cmdset "BJL,BJRaster3,BSCCe" Please report this message in Bugzilla: https://bugzilla.redhat.com/bugzilla Choose 'foomatic' as the component.
Does anyone smarter than me (which is anyone) have any idea if there are any potential clues in this? Note that I'm fully prepared for my printer to not work. But I'm not ready to give up quite yet.
First thing I would do is open /etc/cups/cupsd.conf and change LogLevel to debug2. Restart cups with a "service cups restart". Try printing again and you should get much more verbose output that should point you in the right direction.
Matt
Hi, really think you shouldn't give up. In fact I tryied to configure a Pixma IP3000 just now and it works (at least printed the test page).
These my steps: installed libxml package for fedora3 (since bjfilter was complaining about it and I couldn't find rpm for centos4/rhel4) ftp://ftp.nluug.nl/pub/os/Linux/distr/fedora/core/updates/3/i386/libxml-1.8.17-12.i386.rpm
installed bjfilter-common-2.50-2.i386.rpm bjfilter-pixusip3100-lprng-2.50-2.i386.rpm bjfilter-pixusip3100-2.50-2.i386.rpm
Then I fortunately missed how to import PPD from the printing GUI so I switched to KDE and installed correctly using the control panel, printed the test page, all working (edited the ppd file as indicated on the article). Went back to gnome, found the Action-->import PPD in the GUI, added the correct ppd and happily tryied to print, but I got your same error, or better, nothing was coming out. Found that the 2 files (one added by KDE the other by gnome) in /etc/cups/ppd/ where different, so copied and pasted the working one to the other, restarted cups and now it is working. This is my working /etc/cups/ppd/pixma.ppd file:
*PPD-Adobe: "4.3" *% CUPS add-on PPD file for Canon Bubble Jet Printer. *% Copyright CANON INC. 2001-2005 *% All Rights Reserved. *% *% This program is free software; you can redistribute it and/or modify *% it under the terms of the GNU General Public License as published by *% the Free Software Foundation; either version 2 of the License, or *% (at your option) any later version. *% *% This program is distributed in the hope that it will be useful, *% but WITHOUT ANY WARRANTY; without even the implied warranty of *% MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the *% GNU General Public License for more details. *% *% You should have received a copy of the GNU General Public License *% along with this program; if not, write to the Free Software *% Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
*FileVersion: "1.0" *FormatVersion: "4.3" *LanguageEncoding: ISOLatin1 *LanguageVersion: English *Manufacturer: "Canon" *ModelName: "Canon PIXUS iP3100" *NickName: "Canon PIXUS iP3100 Ver.2.50x" *PCFileName: "CNPX3100.PPD" *Product: "(pixusip3100)" *PSVersion: "(3010.000) 550" *PSVersion: "(3010.000) 651" *PSVersion: "(3010.000) 705" *ShortNickName: "PIXUSIP3100"
*ColorDevice: True *DefaultColorSpace: RGB *Throughput: "1" *LandscapeOrientation: Plus90
*cupsFilter: "application/vnd.cups-postscript 0 pstocanonbj" *cupsManualCopies: True *cupsModelNumber: 180 *cupsVersion: 1.1
*MaxMediaWidth: "612" *MaxMediaHeight: "1656" *CenterRegistered: False *HWMargins: 9.64 14.17 9.64 8.50 *LeadingEdge Short: "" *DefaultLeadingEdge: Short *VariablePaperSize: True *ParamCustomPageSize Width: 1 points 255.12 612.0 *ParamCustomPageSize Height: 2 points 340.16 1656.0 *ParamCustomPageSize WidthOffset: 3 points 0 0 *ParamCustomPageSize HeightOffset: 4 points 0 0 *ParamCustomPageSize Orientation: 5 int 1 1 *CustomPageSize True: "pop pop pop <</PageSize [5 -2 roll] /ImagingBBox null>>setpagedevice"
*OpenUI *PageSize/Paper Size: PickOne *DefaultPageSize: a4 *PageSize a5/A5: "<</CNPageSizeName(a5)/PageSize[420 595]/ImagingBBox null>>setpagedevice" *PageSize a4/A4: "<</CNPageSizeName(a4)/PageSize[595 842]/ImagingBBox null>>setpagedevice" *PageSize b5/B5: "<</CNPageSizeName(b5)/PageSize[516 729]/ImagingBBox null>>setpagedevice" *PageSize letter/Letter: "<</CNPageSizeName(letter)/PageSize[612 792]/ImagingBBox null>>setpagedevice" *PageSize legal/Legal: "<</CNPageSizeName(legal)/PageSize[612 1008]/ImagingBBox null>>setpagedevice" *PageSize postcard/Hagaki 100x148mm: "<</CNPageSizeName(postcard)/PageSize[283 420]/ImagingBBox null>>setpagedevice" *PageSize postdbl/Hagaki 2 148x200mm: "<</CNPageSizeName(postdbl)/PageSize[567 420]/ImagingBBox null>>setpagedevice" *PageSize envj4p/Youkei 4 105.5x235mm: "<</CNPageSizeName(envj4p)/PageSize[298 666]/ImagingBBox null>>setpagedevice" *PageSize envj6p/Youkei 6 98x190mm: "<</CNPageSizeName(envj6p)/PageSize[278 539]/ImagingBBox null>>setpagedevice" *PageSize l/L 89x127mm: "<</CNPageSizeName(l)/PageSize[252 360]/ImagingBBox null>>setpagedevice" *PageSize 2l/2L 127x178mm: "<</CNPageSizeName(2l)/PageSize[360 505]/ImagingBBox null>>setpagedevice" *PageSize panorama/P 89x254mm: "<</CNPageSizeName(panorama)/PageSize[252 720]/ImagingBBox null>>setpagedevice" *PageSize businesscard/Card 2.16x3.58in 55x91mm: "<</CNPageSizeName(businesscard)/PageSize[156 256]/ImagingBBox null>>setpagedevice" *PageSize creditcard/Credit Card 2.13x3.39in 54x86mm: "<</CNPageSizeName(creditcard)/PageSize[153 244]/ImagingBBox null>>setpagedevice" *CloseUI: *PageSize
*OpenUI *PageRegion: PickOne *DefaultPageRegion: a4 *PageRegion a5/A5: "<</CNPageSizeName(a5)/PageSize[420 595]/ImagingBBox null>>setpagedevice" *PageRegion a4/A4: "<</CNPageSizeName(a4)/PageSize[595 842]/ImagingBBox null>>setpagedevice" *PageRegion b5/B5: "<</CNPageSizeName(b5)/PageSize[516 729]/ImagingBBox null>>setpagedevice" *PageRegion letter/Letter: "<</CNPageSizeName(letter)/PageSize[612 792]/ImagingBBox null>>setpagedevice" *PageRegion legal/Legal: "<</CNPageSizeName(legal)/PageSize[612 1008]/ImagingBBox null>>setpagedevice" *PageRegion postcard/Hagaki 100x148mm: "<</CNPageSizeName(postcard)/PageSize[283 420]/ImagingBBox null>>setpagedevice" *PageRegion postdbl/Hagaki 2 148x200mm: "<</CNPageSizeName(postdbl)/PageSize[567 420]/ImagingBBox null>>setpagedevice" *PageRegion envj4p/Youkei 4 105.5x235mm: "<</CNPageSizeName(envj4p)/PageSize[298 666]/ImagingBBox null>>setpagedevice" *PageRegion envj6p/Youkei 6 98x190mm: "<</CNPageSizeName(envj6p)/PageSize[278 539]/ImagingBBox null>>setpagedevice" *PageRegion l/L 89x127mm: "<</CNPageSizeName(l)/PageSize[252 360]/ImagingBBox null>>setpagedevice" *PageRegion 2l/2L 127x178mm: "<</CNPageSizeName(2l)/PageSize[360 505]/ImagingBBox null>>setpagedevice" *PageRegion panorama/P 89x254mm: "<</CNPageSizeName(panorama)/PageSize[252 720]/ImagingBBox null>>setpagedevice" *PageRegion businesscard/Card 2.16x3.58in 55x91mm: "<</CNPageSizeName(businesscard)/PageSize[156 256]/ImagingBBox null>>setpagedevice" *PageRegion creditcard/Credit Card 2.13x3.39in 54x86mm: "<</CNPageSizeName(creditcard)/PageSize[153 244]/ImagingBBox null>>setpagedevice" *CloseUI: *PageRegion
*OpenUI *MediaType/Media Type: PickOne *DefaultMediaType: plain *MediaType plain/Plain Paper: "<</MediaType(plain)>>setpagedevice" *MediaType prophoto/Photo Paper Pro: "<</MediaType(prophoto)>>setpagedevice" *MediaType superphoto/Photo Paper Plus Glossy: "<</MediaType(superphoto)>>setpagedevice" *MediaType doublesidephoto/Photo Paper Plus Double Sided: "<</MediaType(doublesidephoto)>>setpagedevice" *MediaType matte/Matte Photo Paper: "<</MediaType(matte)>>setpagedevice" *MediaType glossypaper/Glossy Photo Paper: "<</MediaType(glossypaper)>>setpagedevice" *MediaType highres/High Resolution Paper: "<</MediaType(highres)>>setpagedevice" *MediaType ijpostcard/Inkjet Hagaki: "<</MediaType(ijpostcard)>>setpagedevice" *MediaType postcard/Hagaki: "<</MediaType(postcard)>>setpagedevice" *MediaType tshirt/T-Shirt Transfer: "<</MediaType(tshirt)>>setpagedevice" *MediaType ohp/Transparency: "<</MediaType(ohp)>>setpagedevice" *MediaType envelope/Envelope: "<</MediaType(envelope)>>setpagedevice" *CloseUI: *MediaType
*OpenUI *InputSlot/Paper Feed: PickOne *DefaultInputSlot: asf *InputSlot asf/Auto Feeder: "" *InputSlot cassette/Cassette: "" *CloseUI: *InputSlot
*OpenUI *Resolution/Output Resolution: PickOne *DefaultResolution: 1200 *Resolution 600/600 dpi: "<>setpagedevice" *Resolution 1200/1200 dpi: "<>setpagedevice" *Resolution 2400/2400 dpi: "<>setpagedevice" *CloseUI: *Resolution
*OpenUI *CNQuality/Quality: PickOne *DefaultCNQuality: 3 *CNQuality 2/High: "2" *CNQuality 3/Normal: "3" *CNQuality 4/Standard: "4" *CNQuality 5/Economy: "5" *CloseUI: *CNQuality
*OpenUI *ColorModel/Color Model: PickOne *DefaultColorModel: rgb *ColorModel rgb/RGB: "<</cupsColorOrder 0/cupsColorSpace 1/cupsCompression 0/cupsBitsPerColor 8>>setpagedevice" *CloseUI: *ColorModel
*DefaultImageableArea: a4 *ImageableArea a5: "9.64 14.17 409.89 586.77" *ImageableArea a4: "9.64 14.17 585.64 833.39" *ImageableArea b5: "9.64 14.17 506.27 720.00" *ImageableArea letter: "18.14 14.17 594.14 783.50" *ImageableArea legal: "18.14 14.17 594.14 999.50" *ImageableArea postcard: "9.64 14.17 273.83 411.02" *ImageableArea postdbl: "9.64 14.17 557.29 411.02" *ImageableArea envj4p: "9.64 75.12 288.00 657.64" *ImageableArea envj6p: "9.64 75.12 268.16 530.08" *ImageableArea l: "9.64 14.17 242.65 351.50" *ImageableArea 2l: "9.64 14.17 350.36 496.06" *ImageableArea panorama: "9.64 14.17 242.65 711.50" *ImageableArea businesscard: "9.64 14.17 146.27 249.45" *ImageableArea creditcard: "9.64 14.17 143.43 235.28"
*DefaultPaperDimension: a4 *PaperDimension a5: "420 595" *PaperDimension a4: "595 842" *PaperDimension b5: "516 729" *PaperDimension letter: "612 792" *PaperDimension legal: "612 1008" *PaperDimension postcard: "283 420" *PaperDimension postdbl: "567 420" *PaperDimension envj4p: "298 666" *PaperDimension envj6p: "278 539" *PaperDimension l: "252 360" *PaperDimension 2l: "360 505" *PaperDimension panorama: "252 720" *PaperDimension businesscard: "156 258" *PaperDimension creditcard: "153 244"
*%CNPpdToOptKey PageSize --papersize *%CNPpdToOptKey MediaType --media *%CNPpdToOptKey InputSlot --paperload *%CNPpdToOptKey CNCartridge --cartridge *%CNPpdToOptKey CNQuality --quality *%CNPpdToOptKey CNHalftoning --halftoning *%CNPpdToOptKey CNRenderIntent --renderintent *%CNPpdToOptKey CNGamma --gamma *%CNPpdToOptKey CNBalanceC --balance_c *%CNPpdToOptKey CNBalanceM --balance_m *%CNPpdToOptKey CNBalanceY --balance_y *%CNPpdToOptKey CNBalanceK --balance_k *%CNPpdToOptKey CNDensity --density *%CNPpdToOptKey CNGrayscale --grayscale *%CNPpdToOptKey CNLocation --location *%CNPpdToOptKey CNPercent --percent *%CNPpdToOptKey CNCopies --copies *%CNPpdToOptKey CNPaperGap --papergap
Hope this helps.
Ciao
Dave Gutteridge wrote:
system-config-printer-gui
Ah! There it is.
Well, Everything went according to plan as far as the web site instructions went.
However, when trying to print a test page, I got the following error output:
I [19/Aug/2005:18:07:16 +0900] Adding start banner page "none" to job 3. I [19/Aug/2005:18:07:16 +0900] Adding end banner page "none" to job 3. I [19/Aug/2005:18:07:16 +0900] Job 3 queued on 'Canon' by 'root'. I [19/Aug/2005:18:07:16 +0900] Started filter /usr/lib/cups/filter/pstops (PID 6160) for job 3. I [19/Aug/2005:18:07:16 +0900] Started filter /usr/lib/cups/filter/foomatic-rip (PID 6161) for job 3. I [19/Aug/2005:18:07:16 +0900] Started backend /usr/lib/cups/backend/usb (PID 6162) for job 3.
And at the command prompt where I had originally started system-config-printer-gui, I got these error messages:
No match for USB device: mfr "Canon" model "iP_3100" desc "Canon iP_3100" cmdset "BJL,BJRaster3,BSCCe" Please report this message in Bugzilla: https://bugzilla.redhat.com/bugzilla Choose 'foomatic' as the component.
Does anyone smarter than me (which is anyone) have any idea if there are any potential clues in this? Note that I'm fully prepared for my printer to not work. But I'm not ready to give up quite yet.
Dave _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Simone simone72@email.it wrote:
Then I fortunately missed how to import PPD from the printing GUI ... Went back to gnome, found the Action-->import PPD in the GUI, added the correct ppd and happily tryied to print, but I got your same error, or better, nothing was coming out. Found that the 2 files (one added by KDE the other by gnome) in /etc/cups/ppd/ where different, so copied and pasted the working one to the other, restarted cups and now it is working.
I'd definitely open a Red Hat Bugzilla report. The GNOME configuration tool is Red Hat's, and they need to know they are not configuring things correctly for the Canon (at least compared to KDE).
On Fri, 2005-08-19 at 17:02 +0900, Dave Gutteridge wrote:
Thank you for that excellent article. And what a stroke of luck that the person us using my exact model.
He actually got into messing with the PPD, which you probably need not do.
All went well until the author of the article instructed to go to "Start Menu > Control Center > peripherals > printers". I have neither a "Control Center", nor a "Peripherals", let alone a "printers" anywhere in my menu. The author of the article is using KDE, but shouldn't there be something similar in Gnome? Which, although I'm probably many steps ahead, I'm sort of back to my original question. Where do I access printer settings? Is there a GUI in Gnome for this? Is there one I can install? Apparently I'm looking for an "add printer wizard",
System Settings -> Printing
Do you not have it???
It's basically a "wizard" that steps you through.
or anything that lets me properly install the "ppd" file that I've created for my printer.
Well, the PPD is just a description. The fact that you added the BubbleJet drivers is the big help.
Where can I administrate my printer settings?
Again, System Settings -> Printing.
On 08/19/2005 01:02 AM, Dave Gutteridge wrote:
Which, although I'm probably many steps ahead, I'm sort of back to my original question. Where do I access printer settings? Is there a GUI in Gnome for this? Is there one I can install?
Apparently I'm looking for an "add printer wizard", or anything that lets me properly install the "ppd" file that I've created for my printer.
Where can I administrate my printer settings?
Hi Dave,
You may have already solved the problem with other people's help. However, I thought I'd mention my favorite way to take care of CUPS printer administration: I use the CUPS web interface, which I believe exists regardless of your Linux distribution and certainly regardless of the desktop you use (which is nice if you ever decide to change desktops or even distributions).
Point your browser to http://localhost:631. If asked to log-in you probably will need to log-in as root. The web interface will allow you to take care of tasks like adding printers and viewing queues. The "add printer" feature is a nice, easy "wizard" type series of steps. To get there, click "Do Administration Tasks" at the main menu.
Marc
Wow, I'm so psyched. My printer works!
For me, the winning combination was to follow the web page suggested by Bryan, but to install the ppd file that Simone created, and then to use http://localhost:631 as suggested by Marc to do the printer administration.
The one trick was that in the CUPS web interface, there was no way of figuring out the printer location. There was no device scanning feature or suggested locations for it. But since I had already tried using Gnome's printer GUI, I knew my printer was at /dev/usb/lp0.
Just before posting here I successfully printed out a CUPS test page, and also a page from some random web site in Firefox.
Thanks to everyone for making a potentially horrific task and making it very easy. Installing this printer was just slighly less painful than getting my Palm Pilot to connect.
Dave
I have downloaded the current iso files and burned the cd's for Centos. I am trying to do an inplace upgrade to my Centos 4.0 server. I have tried booting from the cd and it wants to wipe out my original partitions. I don't see an upgrade current version option. Where am I missing it?
Thanks in advance for your help.
Dave
Oh.. I forgot to mention that my rpm database on the server seems to be corrupted and it refuses to install the current kernel and updates. (one reason I want to upgrade from cd)
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of David Campbell Sent: Saturday, August 20, 2005 10:00 AM To: CentOS mailing list Subject: [CentOS] trying to upgrade from Centos 4.0 to current
I have downloaded the current iso files and burned the cd's for Centos. I am trying to do an inplace upgrade to my Centos 4.0 server. I have tried booting from the cd and it wants to wipe out my original partitions. I don't see an upgrade current version option. Where am I missing it?
Thanks in advance for your help.
Dave
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sat, 2005-08-20 at 10:14 -0400, David Campbell wrote:
Oh.. I forgot to mention that my rpm database on the server seems to be corrupted and it refuses to install the current kernel and updates. (one reason I want to upgrade from cd)
Execute: # rm /var/lib/rpm __db.00? # rpm --initdb
And optionally (as of RHL9+/RHEL3+) # rpm --rebuilddb
BTW, Berkeley Sleepycat DB (which RPM uses) has a tendency to do that from time-to-time. It was worse early on when RPM 4.0 first came out (circa Red Hat Linux 8), but I rarely see it now days.
Hi,
On Sat, Aug 20, 2005 at 10:03:17AM -0500, Bryan J. Smith wrote:
EMERGING NOTE =============
Execute: # rm /var/lib/rpm __db.00? # rpm --initdb
Oh please, don't do that :)
man page ========
'Use --initdb to create a new database, use --rebuilddb to rebuild the database indices from the installed package headers.'
As in --initdb would efectively nuke all your bookkeeping about installed RPMS.
how can I force an upgrade to a newer kernel... I am on 2.6.9-5.0.3.EL but it is showing that2.6.9-11.EL is available... I get the message that I should reboot to test, but it never shows up in my boot list. The only instance available is 2.6.9-5.0.3.EL Thanks
Dave -----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Pasi Pirhonen Sent: Saturday, August 20, 2005 12:16 PM To: CentOS mailing list Subject: Re: [CentOS] RE: trying to upgrade from Centos 4.0 to current --repair RPM database
Hi,
On Sat, Aug 20, 2005 at 10:03:17AM -0500, Bryan J. Smith wrote:
EMERGING NOTE =============
Execute: # rm /var/lib/rpm __db.00? # rpm --initdb
Oh please, don't do that :)
man page ========
'Use --initdb to create a new database, use --rebuilddb to rebuild the database indices from the installed package headers.'
As in --initdb would efectively nuke all your bookkeeping about installed RPMS.
-- Pasi Pirhonen - upi@iki.fi - http://iki.fi/upi/ _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
ohh and it does not show up as an available install inthe alert notification tool
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of David Campbell Sent: Saturday, August 20, 2005 1:22 PM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgrade from Centos 4.0 to current--repair RPM database
how can I force an upgrade to a newer kernel... I am on 2.6.9-5.0.3.EL but it is showing that2.6.9-11.EL is available... I get the message that I should reboot to test, but it never shows up in my boot list. The only instance available is 2.6.9-5.0.3.EL Thanks
Dave -----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Pasi Pirhonen Sent: Saturday, August 20, 2005 12:16 PM To: CentOS mailing list Subject: Re: [CentOS] RE: trying to upgrade from Centos 4.0 to current --repair RPM database
Hi,
On Sat, Aug 20, 2005 at 10:03:17AM -0500, Bryan J. Smith wrote:
EMERGING NOTE =============
Execute: # rm /var/lib/rpm __db.00? # rpm --initdb
Oh please, don't do that :)
man page ========
'Use --initdb to create a new database, use --rebuilddb to rebuild the database indices from the installed package headers.'
As in --initdb would efectively nuke all your bookkeeping about installed RPMS.
-- Pasi Pirhonen - upi@iki.fi - http://iki.fi/upi/ _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sat, 2005-08-20 at 19:15 +0300, Pasi Pirhonen wrote:
man page
'Use --initdb to create a new database, use --rebuilddb to rebuild the database indices from the installed package headers.' As in --initdb would efectively nuke all your bookkeeping about installed RPMS.
Last time I checked --initdb just creates an empty database. -- rebuilddb creates an empty database and re-populates it. You can run the latter after former. In fact, I typically had to do that back with early RPM 4.0.
Furthermore, RPM 4 can get RPM database info from outside the database. Remember, the db is just an index. The RPM information is stored outside of it too.
the --initdb and then --rebuilddb solved all of the problem except the kernel issue...
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Bryan J. Smith Sent: Saturday, August 20, 2005 3:29 PM To: CentOS mailing list Subject: Re: [CentOS] RE: trying to upgrade from Centos 4.0 to current --repair RPM database
On Sat, 2005-08-20 at 19:15 +0300, Pasi Pirhonen wrote:
man page
'Use --initdb to create a new database, use --rebuilddb to rebuild the database indices from the installed package headers.' As in --initdb would efectively nuke all your bookkeeping about installed RPMS.
Last time I checked --initdb just creates an empty database. -- rebuilddb creates an empty database and re-populates it. You can run the latter after former. In fact, I typically had to do that back with early RPM 4.0.
Furthermore, RPM 4 can get RPM database info from outside the database. Remember, the db is just an index. The RPM information is stored outside of it too.
-- Bryan J. Smith b.j.smith@ieee.org http://thebs413.blogspot.com ---------------------------------------------------------------------- The best things in life are NOT free - which is why life is easiest if you save all the bills until you can share them with the perfect woman
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
You probably have the kernel exempted in the method you are using to do the update.
up2date normally exempts the kernel ... click on the
Menu -> System Settings -> CentOS Network Settings
Click on the "Package Exceptions" tab ... and remove kernel* from the "Package Names to Skip" section and save.
Then you can run up2date and upgrade your kernel.
On Sat, 2005-08-20 at 15:45 -0400, David Campbell wrote:
the --initdb and then --rebuilddb solved all of the problem except the kernel issue...
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Bryan J. Smith Sent: Saturday, August 20, 2005 3:29 PM To: CentOS mailing list Subject: Re: [CentOS] RE: trying to upgrade from Centos 4.0 to current --repair RPM database
On Sat, 2005-08-20 at 19:15 +0300, Pasi Pirhonen wrote:
man page
'Use --initdb to create a new database, use --rebuilddb to rebuild the database indices from the installed package headers.' As in --initdb would efectively nuke all your bookkeeping about installed RPMS.
Last time I checked --initdb just creates an empty database. -- rebuilddb creates an empty database and re-populates it. You can run the latter after former. In fact, I typically had to do that back with early RPM 4.0.
Furthermore, RPM 4 can get RPM database info from outside the database. Remember, the db is just an index. The RPM information is stored outside of it too.
-- Bryan J. Smith b.j.smith@ieee.org http://thebs413.blogspot.com
The best things in life are NOT free - which is why life is easiest if you save all the bills until you can share them with the perfect woman
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
you are exactly right.. Thanks to all of you for your help..
Dave
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Saturday, August 20, 2005 4:28 PM To: CentOS ML Subject: RE: [CentOS] RE: trying to upgrade from Centos 4.0 to current--repair RPM database
You probably have the kernel exempted in the method you are using to do the update.
up2date normally exempts the kernel ... click on the
Menu -> System Settings -> CentOS Network Settings
Click on the "Package Exceptions" tab ... and remove kernel* from the "Package Names to Skip" section and save.
Then you can run up2date and upgrade your kernel.
On Sat, 2005-08-20 at 15:45 -0400, David Campbell wrote:
the --initdb and then --rebuilddb solved all of the problem except the kernel issue...
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Bryan J. Smith Sent: Saturday, August 20, 2005 3:29 PM To: CentOS mailing list Subject: Re: [CentOS] RE: trying to upgrade from Centos 4.0 to current --repair RPM database
On Sat, 2005-08-20 at 19:15 +0300, Pasi Pirhonen wrote:
man page
'Use --initdb to create a new database, use --rebuilddb to rebuild the database indices from the installed package headers.' As in --initdb would efectively nuke all your bookkeeping about installed RPMS.
Last time I checked --initdb just creates an empty database. -- rebuilddb creates an empty database and re-populates it. You can run the latter after former. In fact, I typically had to do that back with early RPM 4.0.
Furthermore, RPM 4 can get RPM database info from outside the database. Remember, the db is just an index. The RPM information is stored outside of it too.
-- Bryan J. Smith b.j.smith@ieee.org http://thebs413.blogspot.com
The best things in life are NOT free - which is why life is easiest if you save all the bills until you can share them with the perfect woman
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
ummm I may have spoken too soon.. lol. It still does not show the available update in up2date. I have rebooted the server to verify that everything has been refreshed. Still there are no options to upgrade the kernel.. Although initially, you were right, it was in the exceptions list.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of David Campbell Sent: Saturday, August 20, 2005 5:37 PM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgrade from Centos 4.0 to current--repairRPM database
you are exactly right.. Thanks to all of you for your help..
Dave
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Saturday, August 20, 2005 4:28 PM To: CentOS ML Subject: RE: [CentOS] RE: trying to upgrade from Centos 4.0 to current--repair RPM database
You probably have the kernel exempted in the method you are using to do the update.
up2date normally exempts the kernel ... click on the
Menu -> System Settings -> CentOS Network Settings
Click on the "Package Exceptions" tab ... and remove kernel* from the "Package Names to Skip" section and save.
Then you can run up2date and upgrade your kernel.
On Sat, 2005-08-20 at 15:45 -0400, David Campbell wrote:
the --initdb and then --rebuilddb solved all of the problem except the kernel issue...
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Bryan J. Smith Sent: Saturday, August 20, 2005 3:29 PM To: CentOS mailing list Subject: Re: [CentOS] RE: trying to upgrade from Centos 4.0 to current --repair RPM database
On Sat, 2005-08-20 at 19:15 +0300, Pasi Pirhonen wrote:
man page
'Use --initdb to create a new database, use --rebuilddb to rebuild the database indices from the installed package headers.' As in --initdb would efectively nuke all your bookkeeping about installed RPMS.
Last time I checked --initdb just creates an empty database. -- rebuilddb creates an empty database and re-populates it. You can run the latter after former. In fact, I typically had to do that back with early RPM 4.0.
Furthermore, RPM 4 can get RPM database info from outside the database. Remember, the db is just an index. The RPM information is stored outside of it too.
-- Bryan J. Smith b.j.smith@ieee.org http://thebs413.blogspot.com
The best things in life are NOT free - which is why life is easiest if you save all the bills until you can share them with the perfect woman
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I think that it is installed, just not the default ...
When booting, at the grub screen (first light blue screen), press a key (like the arrow key) ... you should see all the installed kernels, likely the new kernel is installed.
You may need to edit the file:
/boot/grub/grub.conf
to make it the default
On Sat, 2005-08-20 at 17:48 -0400, David Campbell wrote:
ummm I may have spoken too soon.. lol. It still does not show the available update in up2date. I have rebooted the server to verify that everything has been refreshed. Still there are no options to upgrade the kernel.. Although initially, you were right, it was in the exceptions list.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of David Campbell Sent: Saturday, August 20, 2005 5:37 PM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgrade from Centos 4.0 to current--repairRPM database
you are exactly right.. Thanks to all of you for your help..
Dave
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Saturday, August 20, 2005 4:28 PM To: CentOS ML Subject: RE: [CentOS] RE: trying to upgrade from Centos 4.0 to current--repair RPM database
You probably have the kernel exempted in the method you are using to do the update.
up2date normally exempts the kernel ... click on the
Menu -> System Settings -> CentOS Network Settings
Click on the "Package Exceptions" tab ... and remove kernel* from the "Package Names to Skip" section and save.
Then you can run up2date and upgrade your kernel.
On Sat, 2005-08-20 at 15:45 -0400, David Campbell wrote:
the --initdb and then --rebuilddb solved all of the problem except the kernel issue...
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Bryan J. Smith Sent: Saturday, August 20, 2005 3:29 PM To: CentOS mailing list Subject: Re: [CentOS] RE: trying to upgrade from Centos 4.0 to current --repair RPM database
On Sat, 2005-08-20 at 19:15 +0300, Pasi Pirhonen wrote:
man page
'Use --initdb to create a new database, use --rebuilddb to rebuild the database indices from the installed package headers.' As in --initdb would efectively nuke all your bookkeeping about installed RPMS.
Last time I checked --initdb just creates an empty database. -- rebuilddb creates an empty database and re-populates it. You can run the latter after former. In fact, I typically had to do that back with early RPM 4.0.
Furthermore, RPM 4 can get RPM database info from outside the database. Remember, the db is just an index. The RPM information is stored outside of it too.
-- Bryan J. Smith b.j.smith@ieee.org http://thebs413.blogspot.com
The best things in life are NOT free - which is why life is easiest if you save all the bills until you can share them with the perfect woman
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Only the 2.6.9-5.0.3.EL kernel is listed there.. That was my first thought too. but no joy
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Saturday, August 20, 2005 5:55 PM To: CentOS ML Subject: RE: [CentOS] RE: trying to upgrade from Centos 4.0 tocurrent--repairRPM database
I think that it is installed, just not the default ...
When booting, at the grub screen (first light blue screen), press a key (like the arrow key) ... you should see all the installed kernels, likely the new kernel is installed.
You may need to edit the file:
/boot/grub/grub.conf
to make it the default
On Sat, 2005-08-20 at 17:48 -0400, David Campbell wrote:
ummm I may have spoken too soon.. lol. It still does not show the available update in up2date. I have rebooted the server to verify that everything has been refreshed. Still there are no options to upgrade the kernel.. Although initially, you were right, it was in the exceptions
list.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of David Campbell Sent: Saturday, August 20, 2005 5:37 PM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgrade from Centos 4.0 to current--repairRPM database
you are exactly right.. Thanks to all of you for your help..
Dave
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Saturday, August 20, 2005 4:28 PM To: CentOS ML Subject: RE: [CentOS] RE: trying to upgrade from Centos 4.0 to current--repair RPM database
You probably have the kernel exempted in the method you are using to do the update.
up2date normally exempts the kernel ... click on the
Menu -> System Settings -> CentOS Network Settings
Click on the "Package Exceptions" tab ... and remove kernel* from the "Package Names to Skip" section and save.
Then you can run up2date and upgrade your kernel.
On Sat, 2005-08-20 at 15:45 -0400, David Campbell wrote:
the --initdb and then --rebuilddb solved all of the problem except the kernel issue...
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Bryan J. Smith Sent: Saturday, August 20, 2005 3:29 PM To: CentOS mailing list Subject: Re: [CentOS] RE: trying to upgrade from Centos 4.0 to current --repair RPM database
On Sat, 2005-08-20 at 19:15 +0300, Pasi Pirhonen wrote:
man page
'Use --initdb to create a new database, use --rebuilddb to rebuild the database indices from the installed package headers.' As in --initdb would efectively nuke all your bookkeeping about installed RPMS.
Last time I checked --initdb just creates an empty database. -- rebuilddb creates an empty database and re-populates it. You can run the latter after former. In fact, I typically had to do that back with early RPM 4.0.
Furthermore, RPM 4 can get RPM database info from outside the database. Remember, the db is just an index. The RPM information is stored outside of it too.
-- Bryan J. Smith b.j.smith@ieee.org http://thebs413.blogspot.com
The best things in life are NOT free - which is why life is easiest if you save all the bills until you can share them with the perfect woman
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Hey, you may be right .. I went to boot\ and there are several config files that show up there.. Now, only the 2.6.9-5.0.3.EL config shows up in the screen when you boot and hit the arrow key, but the 2.6.9-11 shows in the boot directory.. I havent looked in grub yet.
Ok. IN GRUB, only the 2.6.9-5.0.3.EL is listed -----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of David Campbell Sent: Saturday, August 20, 2005 6:08 PM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgrade from Centos 4.0tocurrent--repairRPM database
Only the 2.6.9-5.0.3.EL kernel is listed there.. That was my first thought too. but no joy
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Saturday, August 20, 2005 5:55 PM To: CentOS ML Subject: RE: [CentOS] RE: trying to upgrade from Centos 4.0 tocurrent--repairRPM database
I think that it is installed, just not the default ...
When booting, at the grub screen (first light blue screen), press a key (like the arrow key) ... you should see all the installed kernels, likely the new kernel is installed.
You may need to edit the file:
/boot/grub/grub.conf
to make it the default
On Sat, 2005-08-20 at 17:48 -0400, David Campbell wrote:
ummm I may have spoken too soon.. lol. It still does not show the available update in up2date. I have rebooted the server to verify that everything has been refreshed. Still there are no options to upgrade the kernel.. Although initially, you were right, it was in the exceptions
list.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of David Campbell Sent: Saturday, August 20, 2005 5:37 PM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgrade from Centos 4.0 to current--repairRPM database
you are exactly right.. Thanks to all of you for your help..
Dave
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Saturday, August 20, 2005 4:28 PM To: CentOS ML Subject: RE: [CentOS] RE: trying to upgrade from Centos 4.0 to current--repair RPM database
You probably have the kernel exempted in the method you are using to do the update.
up2date normally exempts the kernel ... click on the
Menu -> System Settings -> CentOS Network Settings
Click on the "Package Exceptions" tab ... and remove kernel* from the "Package Names to Skip" section and save.
Then you can run up2date and upgrade your kernel.
On Sat, 2005-08-20 at 15:45 -0400, David Campbell wrote:
the --initdb and then --rebuilddb solved all of the problem except the kernel issue...
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Bryan J. Smith Sent: Saturday, August 20, 2005 3:29 PM To: CentOS mailing list Subject: Re: [CentOS] RE: trying to upgrade from Centos 4.0 to current --repair RPM database
On Sat, 2005-08-20 at 19:15 +0300, Pasi Pirhonen wrote:
man page
'Use --initdb to create a new database, use --rebuilddb to rebuild the database indices from the installed package headers.' As in --initdb would efectively nuke all your bookkeeping about installed RPMS.
Last time I checked --initdb just creates an empty database. -- rebuilddb creates an empty database and re-populates it. You can run the latter after former. In fact, I typically had to do that back with early RPM 4.0.
Furthermore, RPM 4 can get RPM database info from outside the database. Remember, the db is just an index. The RPM information is stored outside of it too.
-- Bryan J. Smith b.j.smith@ieee.org http://thebs413.blogspot.com
The best things in life are NOT free - which is why life is easiest if you save all the bills until you can share them with the perfect woman
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
unfortunately, only the 2.6.9-5.0.3.EL kernel is available but the new 2.6.9-11 conf file is in the boot directory... is there a way to force a reinstall?
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of David Campbell Sent: Saturday, August 20, 2005 6:16 PM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgrade from Centos4.0tocurrent--repairRPM database
Hey, you may be right .. I went to boot\ and there are several config files that show up there.. Now, only the 2.6.9-5.0.3.EL config shows up in the screen when you boot and hit the arrow key, but the 2.6.9-11 shows in the boot directory.. I havent looked in grub yet.
Ok. IN GRUB, only the 2.6.9-5.0.3.EL is listed -----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of David Campbell Sent: Saturday, August 20, 2005 6:08 PM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgrade from Centos 4.0tocurrent--repairRPM database
Only the 2.6.9-5.0.3.EL kernel is listed there.. That was my first thought too. but no joy
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Saturday, August 20, 2005 5:55 PM To: CentOS ML Subject: RE: [CentOS] RE: trying to upgrade from Centos 4.0 tocurrent--repairRPM database
I think that it is installed, just not the default ...
When booting, at the grub screen (first light blue screen), press a key (like the arrow key) ... you should see all the installed kernels, likely the new kernel is installed.
You may need to edit the file:
/boot/grub/grub.conf
to make it the default
On Sat, 2005-08-20 at 17:48 -0400, David Campbell wrote:
ummm I may have spoken too soon.. lol. It still does not show the available update in up2date. I have rebooted the server to verify that everything has been refreshed. Still there are no options to upgrade the kernel.. Although initially, you were right, it was in the exceptions
list.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of David Campbell Sent: Saturday, August 20, 2005 5:37 PM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgrade from Centos 4.0 to current--repairRPM database
you are exactly right.. Thanks to all of you for your help..
Dave
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Saturday, August 20, 2005 4:28 PM To: CentOS ML Subject: RE: [CentOS] RE: trying to upgrade from Centos 4.0 to current--repair RPM database
You probably have the kernel exempted in the method you are using to do the update.
up2date normally exempts the kernel ... click on the
Menu -> System Settings -> CentOS Network Settings
Click on the "Package Exceptions" tab ... and remove kernel* from the "Package Names to Skip" section and save.
Then you can run up2date and upgrade your kernel.
On Sat, 2005-08-20 at 15:45 -0400, David Campbell wrote:
the --initdb and then --rebuilddb solved all of the problem except the kernel issue...
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Bryan J. Smith Sent: Saturday, August 20, 2005 3:29 PM To: CentOS mailing list Subject: Re: [CentOS] RE: trying to upgrade from Centos 4.0 to current --repair RPM database
On Sat, 2005-08-20 at 19:15 +0300, Pasi Pirhonen wrote:
man page
'Use --initdb to create a new database, use --rebuilddb to rebuild the database indices from the installed package headers.' As in --initdb would efectively nuke all your bookkeeping about installed RPMS.
Last time I checked --initdb just creates an empty database. -- rebuilddb creates an empty database and re-populates it. You can run the latter after former. In fact, I typically had to do that back with early RPM 4.0.
Furthermore, RPM 4 can get RPM database info from outside the database. Remember, the db is just an index. The RPM information is stored outside of it too.
-- Bryan J. Smith b.j.smith@ieee.org http://thebs413.blogspot.com
The best things in life are NOT free - which is why life is easiest if you save all the bills until you can share them with the perfect woman
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Saturday 20 August 2005 19:52, David Campbell wrote:
unfortunately, only the 2.6.9-5.0.3.EL kernel is available but the new 2.6.9-11 conf file is in the boot directory... is there a way to force a reinstall?
You can download the kernel RPM and rpm -i it. Don't rpm -u; you want to install, not upgrade. But, for grins and giggles, what does the output of 'rpm -qa|grep kern' tell you?
Output is as follows
kernel-2.6.9-11.EL kernel-2.6.9-5.0.3.EL kernel-2.6.9-5.0.5.EL kernel-utils-2.4-13.1.66 kernel-utils-2.4-13.1.48
The only available kernel that shows in the boot is the 2.6.9-5.0.3EL
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Lamar Owen Sent: Saturday, August 20, 2005 8:11 PM To: CentOS mailing list Subject: Re: [CentOS] RE: trying to upgrade from Centos4.0tocurrent--repairRPMdatabase
On Saturday 20 August 2005 19:52, David Campbell wrote:
unfortunately, only the 2.6.9-5.0.3.EL kernel is available but the new 2.6.9-11 conf file is in the boot directory... is there a way to force a reinstall?
You can download the kernel RPM and rpm -i it. Don't rpm -u; you want to install, not upgrade. But, for grins and giggles, what does the output of 'rpm -qa|grep kern' tell you?
hey, I am running a Celeron 650 mhz processor.. I wonder if the kernel-2.6.9-11.EL will run on it.. could that be why it is unavailable?
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of David Campbell Sent: Saturday, August 20, 2005 8:22 PM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgrade fromCentos4.0tocurrent--repairRPMdatabase
Output is as follows
kernel-2.6.9-11.EL kernel-2.6.9-5.0.3.EL kernel-2.6.9-5.0.5.EL kernel-utils-2.4-13.1.66 kernel-utils-2.4-13.1.48
The only available kernel that shows in the boot is the 2.6.9-5.0.3EL
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Lamar Owen Sent: Saturday, August 20, 2005 8:11 PM To: CentOS mailing list Subject: Re: [CentOS] RE: trying to upgrade from Centos4.0tocurrent--repairRPMdatabase
On Saturday 20 August 2005 19:52, David Campbell wrote:
unfortunately, only the 2.6.9-5.0.3.EL kernel is available but the new 2.6.9-11 conf file is in the boot directory... is there a way to force a reinstall?
You can download the kernel RPM and rpm -i it. Don't rpm -u; you want to install, not upgrade. But, for grins and giggles, what does the output of 'rpm -qa|grep kern' tell you? -- Lamar Owen Director of Information Technology Pisgah Astronomical Research Institute 1 PARI Drive Rosman, NC 28772 (828)862-5554 www.pari.edu _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sat, 2005-08-20 at 21:08 -0400, David Campbell wrote:
hey, I am running a Celeron 650 mhz processor.. I wonder if the kernel-2.6.9-11.EL will run on it.. could that be why it is unavailable?
All Celerons are genuine Pentium Pro (i686) cores.
ok, I tried the rpm-i kernel.2.6.9-11.EL.i586.rpm and got conflicts with package from file 2.6.9-11.EL errors.
was trying to use the lowest common denominator as I used the 386 iso's for original install
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Bryan J. Smith Sent: Saturday, August 20, 2005 9:33 PM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgradefromCentos4.0tocurrent--repairRPMdatabase
On Sat, 2005-08-20 at 21:08 -0400, David Campbell wrote:
hey, I am running a Celeron 650 mhz processor.. I wonder if the kernel-2.6.9-11.EL will run on it.. could that be why it is unavailable?
All Celerons are genuine Pentium Pro (i686) cores.
-- Bryan J. Smith b.j.smith@ieee.org http://thebs413.blogspot.com ---------------------------------------------------------------------- The best things in life are NOT free - which is why life is easiest if you save all the bills until you can share them with the perfect woman
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sat, 2005-08-20 at 20:21 -0400, David Campbell wrote:
Output is as follows
kernel-2.6.9-11.EL kernel-2.6.9-5.0.3.EL kernel-2.6.9-5.0.5.EL kernel-utils-2.4-13.1.66 kernel-utils-2.4-13.1.48
The only available kernel that shows in the boot is the 2.6.9-5.0.3EL
---- why not 'cat /boot/grub/grub.conf' and 'ls -l /boot' and we'll give you the changes to make to /boot/grub/grub.conf
Craig
Here is what grub.conf says..
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS 4.0 (2.6.9-5.0.3.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.9-5.0.3.EL.img ~
Thanks
Dave
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Craig White Sent: Sunday, August 21, 2005 12:12 AM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgrade fromCentos4.0tocurrent--repairRPMdatabase
On Sat, 2005-08-20 at 20:21 -0400, David Campbell wrote:
Output is as follows
kernel-2.6.9-11.EL kernel-2.6.9-5.0.3.EL kernel-2.6.9-5.0.5.EL kernel-utils-2.4-13.1.66 kernel-utils-2.4-13.1.48
The only available kernel that shows in the boot is the 2.6.9-5.0.3EL
---- why not 'cat /boot/grub/grub.conf' and 'ls -l /boot' and we'll give you the changes to make to /boot/grub/grub.conf
Craig
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sun, 2005-08-21 at 05:59 -0400, David Campbell wrote:
Here is what grub.conf says..
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS 4.0 (2.6.9-5.0.3.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.9-5.0.3.EL.img ~
Thanks
Dave
Dave, You need the i686 kernel and not the i586 kernel.
Make your grub.conf look like this (leave all the remarked stuff, that begins with #, alone) :
default=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS 4.0 (2.6.9-5.0.3.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.9-5.0.3.EL.img
title CentOS 4 (2.6.9-11.EL) root (hd0,0) kernel /vmlinuz-2.6.9-11.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.9-11.EL.img
#-----------------------------------------------
If, for some reason the new kernel doesn't boot, shift to default=0 in grub.conf.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Craig White Sent: Sunday, August 21, 2005 12:12 AM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgrade fromCentos4.0tocurrent--repairRPMdatabase
On Sat, 2005-08-20 at 20:21 -0400, David Campbell wrote:
Output is as follows
kernel-2.6.9-11.EL kernel-2.6.9-5.0.3.EL kernel-2.6.9-5.0.5.EL kernel-utils-2.4-13.1.66 kernel-utils-2.4-13.1.48
The only available kernel that shows in the boot is the 2.6.9-5.0.3EL
why not 'cat /boot/grub/grub.conf' and 'ls -l /boot' and we'll give you the changes to make to /boot/grub/grub.conf
Craig
-- Johnny Hughes < http://www.hughesjr.com/ >
Ok, thanks.. is there a way I can tell for sure which kernels I have installed. I have tried rpm -i and the 686 kernel name and it says already installed.. tried it with the 586 also and got same results... also tried rpm -e for each and it said "not installed" though I did the rpm -i again and it said it was, so I found it strange.
Thanks
Dave
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Sunday, August 21, 2005 6:22 AM To: CentOS ML Subject: RE: [CentOS] RE: trying to upgradefromCentos4.0tocurrent--repairRPMdatabase
On Sun, 2005-08-21 at 05:59 -0400, David Campbell wrote:
Here is what grub.conf says..
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this
file
# NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS 4.0 (2.6.9-5.0.3.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00
rhgb
quiet initrd /initrd-2.6.9-5.0.3.EL.img ~
Thanks
Dave
Dave, You need the i686 kernel and not the i586 kernel.
Make your grub.conf look like this (leave all the remarked stuff, that begins with #, alone) :
default=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS 4.0 (2.6.9-5.0.3.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.9-5.0.3.EL.img
title CentOS 4 (2.6.9-11.EL) root (hd0,0) kernel /vmlinuz-2.6.9-11.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.9-11.EL.img
#-----------------------------------------------
If, for some reason the new kernel doesn't boot, shift to default=0 in grub.conf.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Craig White Sent: Sunday, August 21, 2005 12:12 AM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgrade fromCentos4.0tocurrent--repairRPMdatabase
On Sat, 2005-08-20 at 20:21 -0400, David Campbell wrote:
Output is as follows
kernel-2.6.9-11.EL kernel-2.6.9-5.0.3.EL kernel-2.6.9-5.0.5.EL kernel-utils-2.4-13.1.66 kernel-utils-2.4-13.1.48
The only available kernel that shows in the boot is the 2.6.9-5.0.3EL
why not 'cat /boot/grub/grub.conf' and 'ls -l /boot' and we'll give you the changes to make to /boot/grub/grub.conf
Craig
-- Johnny Hughes < http://www.hughesjr.com/ >
On Sun, 2005-08-21 at 06:29 -0400, David Campbell wrote:
Ok, thanks.. is there a way I can tell for sure which kernels I have installed. I have tried rpm -i and the 686 kernel name and it says already installed.. tried it with the 586 also and got same results... also tried rpm -e for each and it said "not installed" though I did the rpm -i again and it said it was, so I found it strange.
Thanks
Dave
Use the following commands to see the arches of your installed kernels:
rpm -q --qf '[%{name}-%{version}-%{release}.%{arch}\n]' kernel
and
rpm -q --qf '[%{name}-%{version}-%{release}.%{arch}\n]' kernel-devel
(you would substitute kernel-smp and kernel-smp-devel if you had an smp kernel installed)
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Sunday, August 21, 2005 6:22 AM To: CentOS ML Subject: RE: [CentOS] RE: trying to upgradefromCentos4.0tocurrent--repairRPMdatabase
On Sun, 2005-08-21 at 05:59 -0400, David Campbell wrote:
Here is what grub.conf says..
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this
file
# NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS 4.0 (2.6.9-5.0.3.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00
rhgb
quiet initrd /initrd-2.6.9-5.0.3.EL.img ~
Thanks
Dave
Dave, You need the i686 kernel and not the i586 kernel.
Make your grub.conf look like this (leave all the remarked stuff, that begins with #, alone) :
default=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS 4.0 (2.6.9-5.0.3.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.9-5.0.3.EL.img
title CentOS 4 (2.6.9-11.EL) root (hd0,0) kernel /vmlinuz-2.6.9-11.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.9-11.EL.img
#-----------------------------------------------
If, for some reason the new kernel doesn't boot, shift to default=0 in grub.conf.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Craig White Sent: Sunday, August 21, 2005 12:12 AM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgrade fromCentos4.0tocurrent--repairRPMdatabase
On Sat, 2005-08-20 at 20:21 -0400, David Campbell wrote:
Output is as follows
kernel-2.6.9-11.EL kernel-2.6.9-5.0.3.EL kernel-2.6.9-5.0.5.EL kernel-utils-2.4-13.1.66 kernel-utils-2.4-13.1.48
The only available kernel that shows in the boot is the 2.6.9-5.0.3EL
why not 'cat /boot/grub/grub.conf' and 'ls -l /boot' and we'll give you the changes to make to /boot/grub/grub.conf
Craig
-- Johnny Hughes < http://www.hughesjr.com/ >
wow... that was scary.. I did the edit, verified that I had no typos. save and rebooted... said "file not found". So had to manually type the load sequence in at command line to get the server back up... will verify the installed kernels now...
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Sunday, August 21, 2005 6:40 AM To: CentOS ML Subject: RE: [CentOS] RE: trying toupgradefromCentos4.0tocurrent--repairRPMdatabase
On Sun, 2005-08-21 at 06:29 -0400, David Campbell wrote:
Ok, thanks.. is there a way I can tell for sure which kernels I have installed. I have tried rpm -i and the 686 kernel name and it says already installed.. tried it with the 586 also and got same results... also tried rpm -e for each and it said "not installed" though I did the rpm -i again and it said it was, so I found it strange.
Thanks
Dave
Use the following commands to see the arches of your installed kernels:
rpm -q --qf '[%{name}-%{version}-%{release}.%{arch}\n]' kernel
and
rpm -q --qf '[%{name}-%{version}-%{release}.%{arch}\n]' kernel-devel
(you would substitute kernel-smp and kernel-smp-devel if you had an smp kernel installed)
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Sunday, August 21, 2005 6:22 AM To: CentOS ML Subject: RE: [CentOS] RE: trying to upgradefromCentos4.0tocurrent--repairRPMdatabase
On Sun, 2005-08-21 at 05:59 -0400, David Campbell wrote:
Here is what grub.conf says..
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this
file
# NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS 4.0 (2.6.9-5.0.3.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00
rhgb
quiet initrd /initrd-2.6.9-5.0.3.EL.img ~
Thanks
Dave
Dave, You need the i686 kernel and not the i586 kernel.
Make your grub.conf look like this (leave all the remarked stuff, that begins with #, alone) :
default=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS 4.0 (2.6.9-5.0.3.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00
rhgb
quiet initrd /initrd-2.6.9-5.0.3.EL.img
title CentOS 4 (2.6.9-11.EL) root (hd0,0) kernel /vmlinuz-2.6.9-11.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.9-11.EL.img
#-----------------------------------------------
If, for some reason the new kernel doesn't boot, shift to default=0 in grub.conf.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Craig White Sent: Sunday, August 21, 2005 12:12 AM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgrade fromCentos4.0tocurrent--repairRPMdatabase
On Sat, 2005-08-20 at 20:21 -0400, David Campbell wrote:
Output is as follows
kernel-2.6.9-11.EL kernel-2.6.9-5.0.3.EL kernel-2.6.9-5.0.5.EL kernel-utils-2.4-13.1.66 kernel-utils-2.4-13.1.48
The only available kernel that shows in the boot is the 2.6.9-5.0.3EL
why not 'cat /boot/grub/grub.conf' and 'ls -l /boot' and we'll give you the changes to make to /boot/grub/grub.conf
Craig
-- Johnny Hughes < http://www.hughesjr.com/ >
Hey, Johnny, I have a newbie question for you... not that the previous stuff isn't but what is the difference between a regular kernel and an smb kernel?
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of David Campbell Sent: Sunday, August 21, 2005 7:01 AM To: CentOS mailing list Subject: RE: [CentOS] RE: tryingtoupgradefromCentos4.0tocurrent--repairRPMdatabase
wow... that was scary.. I did the edit, verified that I had no typos. save and rebooted... said "file not found". So had to manually type the load sequence in at command line to get the server back up... will verify the installed kernels now...
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Sunday, August 21, 2005 6:40 AM To: CentOS ML Subject: RE: [CentOS] RE: trying toupgradefromCentos4.0tocurrent--repairRPMdatabase
On Sun, 2005-08-21 at 06:29 -0400, David Campbell wrote:
Ok, thanks.. is there a way I can tell for sure which kernels I have installed. I have tried rpm -i and the 686 kernel name and it says already installed.. tried it with the 586 also and got same results... also tried rpm -e for each and it said "not installed" though I did the rpm -i again and it said it was, so I found it strange.
Thanks
Dave
Use the following commands to see the arches of your installed kernels:
rpm -q --qf '[%{name}-%{version}-%{release}.%{arch}\n]' kernel
and
rpm -q --qf '[%{name}-%{version}-%{release}.%{arch}\n]' kernel-devel
(you would substitute kernel-smp and kernel-smp-devel if you had an smp kernel installed)
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Sunday, August 21, 2005 6:22 AM To: CentOS ML Subject: RE: [CentOS] RE: trying to upgradefromCentos4.0tocurrent--repairRPMdatabase
On Sun, 2005-08-21 at 05:59 -0400, David Campbell wrote:
Here is what grub.conf says..
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this
file
# NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS 4.0 (2.6.9-5.0.3.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00
rhgb
quiet initrd /initrd-2.6.9-5.0.3.EL.img ~
Thanks
Dave
Dave, You need the i686 kernel and not the i586 kernel.
Make your grub.conf look like this (leave all the remarked stuff, that begins with #, alone) :
default=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS 4.0 (2.6.9-5.0.3.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00
rhgb
quiet initrd /initrd-2.6.9-5.0.3.EL.img
title CentOS 4 (2.6.9-11.EL) root (hd0,0) kernel /vmlinuz-2.6.9-11.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.9-11.EL.img
#-----------------------------------------------
If, for some reason the new kernel doesn't boot, shift to default=0 in grub.conf.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Craig White Sent: Sunday, August 21, 2005 12:12 AM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgrade fromCentos4.0tocurrent--repairRPMdatabase
On Sat, 2005-08-20 at 20:21 -0400, David Campbell wrote:
Output is as follows
kernel-2.6.9-11.EL kernel-2.6.9-5.0.3.EL kernel-2.6.9-5.0.5.EL kernel-utils-2.4-13.1.66 kernel-utils-2.4-13.1.48
The only available kernel that shows in the boot is the 2.6.9-5.0.3EL
why not 'cat /boot/grub/grub.conf' and 'ls -l /boot' and we'll give you the changes to make to /boot/grub/grub.conf
Craig
-- Johnny Hughes < http://www.hughesjr.com/ >
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
OK I did the rpm -q --qf '[%{name}-%{version}-%{release}.%{arch}\n]' kernel
and got the following
kernel-2.6.9-5.0.3.EL.i686 kernel-2.6.9-5.0.5.EL.i686 kernel-2.6.9-11.EL.i686
Thanks Dave
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of David Campbell Sent: Sunday, August 21, 2005 7:13 AM To: CentOS mailing list Subject: RE: [CentOS] RE:tryingtoupgradefromCentos4.0tocurrent--repairRPMdatabase
Hey, Johnny, I have a newbie question for you... not that the previous stuff isn't but what is the difference between a regular kernel and an smb kernel?
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of David Campbell Sent: Sunday, August 21, 2005 7:01 AM To: CentOS mailing list Subject: RE: [CentOS] RE: tryingtoupgradefromCentos4.0tocurrent--repairRPMdatabase
wow... that was scary.. I did the edit, verified that I had no typos. save and rebooted... said "file not found". So had to manually type the load sequence in at command line to get the server back up... will verify the installed kernels now...
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Sunday, August 21, 2005 6:40 AM To: CentOS ML Subject: RE: [CentOS] RE: trying toupgradefromCentos4.0tocurrent--repairRPMdatabase
On Sun, 2005-08-21 at 06:29 -0400, David Campbell wrote:
Ok, thanks.. is there a way I can tell for sure which kernels I have installed. I have tried rpm -i and the 686 kernel name and it says already installed.. tried it with the 586 also and got same results... also tried rpm -e for each and it said "not installed" though I did the rpm -i again and it said it was, so I found it strange.
Thanks
Dave
Use the following commands to see the arches of your installed kernels:
rpm -q --qf '[%{name}-%{version}-%{release}.%{arch}\n]' kernel
and
rpm -q --qf '[%{name}-%{version}-%{release}.%{arch}\n]' kernel-devel
(you would substitute kernel-smp and kernel-smp-devel if you had an smp kernel installed)
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Sunday, August 21, 2005 6:22 AM To: CentOS ML Subject: RE: [CentOS] RE: trying to upgradefromCentos4.0tocurrent--repairRPMdatabase
On Sun, 2005-08-21 at 05:59 -0400, David Campbell wrote:
Here is what grub.conf says..
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this
file
# NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS 4.0 (2.6.9-5.0.3.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00
rhgb
quiet initrd /initrd-2.6.9-5.0.3.EL.img ~
Thanks
Dave
Dave, You need the i686 kernel and not the i586 kernel.
Make your grub.conf look like this (leave all the remarked stuff, that begins with #, alone) :
default=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS 4.0 (2.6.9-5.0.3.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00
rhgb
quiet initrd /initrd-2.6.9-5.0.3.EL.img
title CentOS 4 (2.6.9-11.EL) root (hd0,0) kernel /vmlinuz-2.6.9-11.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.9-11.EL.img
#-----------------------------------------------
If, for some reason the new kernel doesn't boot, shift to default=0 in grub.conf.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Craig White Sent: Sunday, August 21, 2005 12:12 AM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgrade fromCentos4.0tocurrent--repairRPMdatabase
On Sat, 2005-08-20 at 20:21 -0400, David Campbell wrote:
Output is as follows
kernel-2.6.9-11.EL kernel-2.6.9-5.0.3.EL kernel-2.6.9-5.0.5.EL kernel-utils-2.4-13.1.66 kernel-utils-2.4-13.1.48
The only available kernel that shows in the boot is the 2.6.9-5.0.3EL
why not 'cat /boot/grub/grub.conf' and 'ls -l /boot' and we'll give you the changes to make to /boot/grub/grub.conf
Craig
-- Johnny Hughes < http://www.hughesjr.com/ >
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
At some point, your RPM database was screwed, right? Why don't you see if those three kernels are really installed:
[root@mavis ~]# ls -l /boot | grep vmlinuz -rw-r--r-- 1 root root 1435513 Jun 8 17:39 vmlinuz-2.6.9-11.EL -rw-r--r-- 1 root root 1401894 Jun 8 18:33 vmlinuz-2.6.9-11.ELsmp -rw-r--r-- 1 root root 1433883 Feb 19 19:18 vmlinuz-2.6.9-5.0.3.EL -rw-r--r-- 1 root root 1400375 Feb 19 20:30 vmlinuz-2.6.9-5.0.3.ELsmp -rw-r--r-- 1 root root 1434068 Apr 19 18:09 vmlinuz-2.6.9-5.0.5.EL -rw-r--r-- 1 root root 1400547 Apr 19 18:35 vmlinuz-2.6.9-5.0.5.ELsmp [root@mavis ~]#
According to your query below, you should have the three files above that DO NOT end with "smp" and you should be able to boot any of the three. (Which you indicated earlier didn't work.) Based on the indications you're giving, that RPM data is still out of touch with reality.
David Campbell wrote:
OK I did the rpm -q --qf '[%{name}-%{version}-%{release}.%{arch}\n]' kernel
and got the following
kernel-2.6.9-5.0.3.EL.i686 kernel-2.6.9-5.0.5.EL.i686 kernel-2.6.9-11.EL.i686
Thanks Dave
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of David Campbell Sent: Sunday, August 21, 2005 7:13 AM To: CentOS mailing list Subject: RE: [CentOS] RE:tryingtoupgradefromCentos4.0tocurrent--repairRPMdatabase
Hey, Johnny, I have a newbie question for you... not that the previous stuff isn't but what is the difference between a regular kernel and an smb kernel?
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of David Campbell Sent: Sunday, August 21, 2005 7:01 AM To: CentOS mailing list Subject: RE: [CentOS] RE: tryingtoupgradefromCentos4.0tocurrent--repairRPMdatabase
wow... that was scary.. I did the edit, verified that I had no typos. save and rebooted... said "file not found". So had to manually type the load sequence in at command line to get the server back up... will verify the installed kernels now...
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Sunday, August 21, 2005 6:40 AM To: CentOS ML Subject: RE: [CentOS] RE: trying toupgradefromCentos4.0tocurrent--repairRPMdatabase
On Sun, 2005-08-21 at 06:29 -0400, David Campbell wrote:
Ok, thanks.. is there a way I can tell for sure which kernels I have installed. I have tried rpm -i and the 686 kernel name and it says already installed.. tried it with the 586 also and got same results... also tried rpm -e for each and it said "not installed" though I did the rpm -i again and it said it was, so I found it strange.
Thanks
Dave
Use the following commands to see the arches of your installed kernels:
rpm -q --qf '[%{name}-%{version}-%{release}.%{arch}\n]' kernel
and
rpm -q --qf '[%{name}-%{version}-%{release}.%{arch}\n]' kernel-devel
(you would substitute kernel-smp and kernel-smp-devel if you had an smp kernel installed)
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Sunday, August 21, 2005 6:22 AM To: CentOS ML Subject: RE: [CentOS] RE: trying to upgradefromCentos4.0tocurrent--repairRPMdatabase
On Sun, 2005-08-21 at 05:59 -0400, David Campbell wrote:
Here is what grub.conf says..
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this
file
# NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS 4.0 (2.6.9-5.0.3.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00
rhgb
quiet initrd /initrd-2.6.9-5.0.3.EL.img ~
Thanks
Dave
Dave, You need the i686 kernel and not the i586 kernel.
Make your grub.conf look like this (leave all the remarked stuff, that begins with #, alone) :
default=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS 4.0 (2.6.9-5.0.3.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00
rhgb
quiet initrd /initrd-2.6.9-5.0.3.EL.img
title CentOS 4 (2.6.9-11.EL) root (hd0,0) kernel /vmlinuz-2.6.9-11.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.9-11.EL.img
#-----------------------------------------------
If, for some reason the new kernel doesn't boot, shift to default=0 in grub.conf.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Craig White Sent: Sunday, August 21, 2005 12:12 AM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgrade fromCentos4.0tocurrent--repairRPMdatabase
On Sat, 2005-08-20 at 20:21 -0400, David Campbell wrote:
Output is as follows
kernel-2.6.9-11.EL kernel-2.6.9-5.0.3.EL kernel-2.6.9-5.0.5.EL kernel-utils-2.4-13.1.66 kernel-utils-2.4-13.1.48
The only available kernel that shows in the boot is the 2.6.9-5.0.3EL
why not 'cat /boot/grub/grub.conf' and 'ls -l /boot' and we'll give you the changes to make to /boot/grub/grub.conf
Craig
-- Johnny Hughes < http://www.hughesjr.com/ >
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
ok here is the list [root@mail /]# ls -l /boot |grep vmlinuz -rw-r--r-- 1 root root 1435513 Jun 8 18:39 vmlinuz-2.6.9-11.EL -rw-r--r-- 1 root root 1433883 Feb 19 20:18 vmlinuz-2.6.9-5.0.3.EL -rw-r--r-- 1 root root 1434068 Apr 19 19:09 vmlinuz-2.6.9-5.0.5.EL [root@mail /]#
they appear to be there..could they be corrupted?
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Robert Sent: Sunday, August 21, 2005 8:44 AM To: CentOS mailing list Subject: Re: [CentOS] RE:tryingtoupgradefromCentos4.0tocurrent--repairRPMdatabase
At some point, your RPM database was screwed, right? Why don't you see if those three kernels are really installed:
[root@mavis ~]# ls -l /boot | grep vmlinuz -rw-r--r-- 1 root root 1435513 Jun 8 17:39 vmlinuz-2.6.9-11.EL -rw-r--r-- 1 root root 1401894 Jun 8 18:33 vmlinuz-2.6.9-11.ELsmp -rw-r--r-- 1 root root 1433883 Feb 19 19:18 vmlinuz-2.6.9-5.0.3.EL -rw-r--r-- 1 root root 1400375 Feb 19 20:30 vmlinuz-2.6.9-5.0.3.ELsmp -rw-r--r-- 1 root root 1434068 Apr 19 18:09 vmlinuz-2.6.9-5.0.5.EL -rw-r--r-- 1 root root 1400547 Apr 19 18:35 vmlinuz-2.6.9-5.0.5.ELsmp [root@mavis ~]#
According to your query below, you should have the three files above that DO NOT end with "smp" and you should be able to boot any of the three. (Which you indicated earlier didn't work.) Based on the indications you're giving, that RPM data is still out of touch with reality.
David Campbell wrote:
OK I did the rpm -q --qf '[%{name}-%{version}-%{release}.%{arch}\n]' kernel
and got the following
kernel-2.6.9-5.0.3.EL.i686 kernel-2.6.9-5.0.5.EL.i686 kernel-2.6.9-11.EL.i686
Thanks Dave
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of David Campbell Sent: Sunday, August 21, 2005 7:13 AM To: CentOS mailing list Subject: RE: [CentOS] RE:tryingtoupgradefromCentos4.0tocurrent--repairRPMdatabase
Hey, Johnny, I have a newbie question for you... not that the previous stuff isn't but what is the difference between a regular kernel and an smb kernel?
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of David Campbell Sent: Sunday, August 21, 2005 7:01 AM To: CentOS mailing list Subject: RE: [CentOS] RE: tryingtoupgradefromCentos4.0tocurrent--repairRPMdatabase
wow... that was scary.. I did the edit, verified that I had no typos. save and rebooted... said "file not found". So had to manually type the load sequence in at command line to get the server back up... will verify the installed kernels now...
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Sunday, August 21, 2005 6:40 AM To: CentOS ML Subject: RE: [CentOS] RE: trying toupgradefromCentos4.0tocurrent--repairRPMdatabase
On Sun, 2005-08-21 at 06:29 -0400, David Campbell wrote:
Ok, thanks.. is there a way I can tell for sure which kernels I have installed. I have tried rpm -i and the 686 kernel name and it says already installed.. tried it with the 586 also and got same results... also tried rpm -e for each and it said "not installed" though I did the rpm -i again and it said it was, so I found it strange.
Thanks
Dave
Use the following commands to see the arches of your installed kernels:
rpm -q --qf '[%{name}-%{version}-%{release}.%{arch}\n]' kernel
and
rpm -q --qf '[%{name}-%{version}-%{release}.%{arch}\n]' kernel-devel
(you would substitute kernel-smp and kernel-smp-devel if you had an smp kernel installed)
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Sunday, August 21, 2005 6:22 AM To: CentOS ML Subject: RE: [CentOS] RE: trying to upgradefromCentos4.0tocurrent--repairRPMdatabase
On Sun, 2005-08-21 at 05:59 -0400, David Campbell wrote:
Here is what grub.conf says..
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this
file
# NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS 4.0 (2.6.9-5.0.3.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00
rhgb
quiet initrd /initrd-2.6.9-5.0.3.EL.img ~
Thanks
Dave
Dave, You need the i686 kernel and not the i586 kernel.
Make your grub.conf look like this (leave all the remarked stuff, that begins with #, alone) :
default=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS 4.0 (2.6.9-5.0.3.EL) root (hd0,0) kernel /vmlinuz-2.6.9-5.0.3.EL ro root=/dev/VolGroup00/LogVol00
rhgb
quiet initrd /initrd-2.6.9-5.0.3.EL.img
title CentOS 4 (2.6.9-11.EL) root (hd0,0) kernel /vmlinuz-2.6.9-11.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.9-11.EL.img
#-----------------------------------------------
If, for some reason the new kernel doesn't boot, shift to default=0 in grub.conf.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Craig White Sent: Sunday, August 21, 2005 12:12 AM To: CentOS mailing list Subject: RE: [CentOS] RE: trying to upgrade fromCentos4.0tocurrent--repairRPMdatabase
On Sat, 2005-08-20 at 20:21 -0400, David Campbell wrote:
Output is as follows
kernel-2.6.9-11.EL kernel-2.6.9-5.0.3.EL kernel-2.6.9-5.0.5.EL kernel-utils-2.4-13.1.66 kernel-utils-2.4-13.1.48
The only available kernel that shows in the boot is the 2.6.9-5.0.3EL
why not 'cat /boot/grub/grub.conf' and 'ls -l /boot' and we'll give you the changes to make to /boot/grub/grub.conf
Craig
-- Johnny Hughes < http://www.hughesjr.com/ >
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sun, 2005-08-21 at 09:38 -0400, David Campbell wrote:
ok here is the list [root@mail /]# ls -l /boot |grep vmlinuz -rw-r--r-- 1 root root 1435513 Jun 8 18:39 vmlinuz-2.6.9-11.EL -rw-r--r-- 1 root root 1433883 Feb 19 20:18 vmlinuz-2.6.9-5.0.3.EL -rw-r--r-- 1 root root 1434068 Apr 19 19:09 vmlinuz-2.6.9-5.0.5.EL [root@mail /]#
they appear to be there..could they be corrupted?
Also do:
ls -l /boot | grep initrd
ok [root@mail /]# ls -l /boot | grep initrd -rw-r--r-- 1 root root 969674 Apr 16 15:39 initrd-2.6.9-5.0.3.EL.img [root@mail /]#
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Sunday, August 21, 2005 9:56 AM To: CentOS ML Subject: RE:[CentOS] RE:tryingtoupgradefromCentos4.0tocurrent--repairRPMdatabase
On Sun, 2005-08-21 at 09:38 -0400, David Campbell wrote:
ok here is the list [root@mail /]# ls -l /boot |grep vmlinuz -rw-r--r-- 1 root root 1435513 Jun 8 18:39 vmlinuz-2.6.9-11.EL -rw-r--r-- 1 root root 1433883 Feb 19 20:18 vmlinuz-2.6.9-5.0.3.EL -rw-r--r-- 1 root root 1434068 Apr 19 19:09 vmlinuz-2.6.9-5.0.5.EL [root@mail /]#
they appear to be there..could they be corrupted?
Also do:
ls -l /boot | grep initrd
On Sun, 2005-08-21 at 10:08 -0400, David Campbell wrote:
ok [root@mail /]# ls -l /boot | grep initrd -rw-r--r-- 1 root root 969674 Apr 16 15:39 initrd-2.6.9-5.0.3.EL.img [root@mail /]#
OK ... that is the problem ...
For some reason, your initrd images are not being generated during the kernel RPM installs.
try downloading the latest kernel and manually:
http://mirror.centos.org/centos/4/os/i386/CentOS/RPMS/kernel-2.6.9-11.EL.i68...
and install it with the command:
rpm -ivh --force kernel-2.6.9-11.EL.i686.rpm
pay particular attention to any errors on the screen in the text
When finished, see if there is an initrd-2.6.9-11.EL.img in /boot
That did the trick.. it installed cleanly and I have rebooted in the kernel-2.6.9-11.EL everything seems ok now.. Thank you for your help... it is greatly appreciated
Dave
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org]On Behalf Of Johnny Hughes Sent: Sunday, August 21, 2005 10:25 AM To: CentOS ML Subject: RE:[CentOS] RE:tryingtoupgradefromCentos4.0tocurrent--repairRPMdatabase
On Sun, 2005-08-21 at 10:08 -0400, David Campbell wrote:
ok [root@mail /]# ls -l /boot | grep initrd -rw-r--r-- 1 root root 969674 Apr 16 15:39 initrd-2.6.9-5.0.3.EL.img [root@mail /]#
OK ... that is the problem ...
For some reason, your initrd images are not being generated during the kernel RPM installs.
try downloading the latest kernel and manually:
http://mirror.centos.org/centos/4/os/i386/CentOS/RPMS/kernel-2.6.9-11.EL.i68 6.rpm
and install it with the command:
rpm -ivh --force kernel-2.6.9-11.EL.i686.rpm
pay particular attention to any errors on the screen in the text
When finished, see if there is an initrd-2.6.9-11.EL.img in /boot
Hi,
On Sat, Aug 20, 2005 at 02:29:27PM -0500, Bryan J. Smith wrote:
On Sat, 2005-08-20 at 19:15 +0300, Pasi Pirhonen wrote:
man page
'Use --initdb to create a new database, use --rebuilddb to rebuild the database indices from the installed package headers.' As in --initdb would efectively nuke all your bookkeeping about installed RPMS.
Last time I checked --initdb just creates an empty database. -- rebuilddb creates an empty database and re-populates it. You can run the latter after former. In fact, I typically had to do that back with early RPM 4.0.
Furthermore, RPM 4 can get RPM database info from outside the database. Remember, the db is just an index. The RPM information is stored outside of it too.
Sorry. You're actually right. --initdb don't nuke the RPM database. I've actually not done it ever on live system, but usually used it to make empty one for chroot. Obviously i assumed it writing over the current RPM database as it _should do init_
Just tested and it does not nuke the RPM database.
-
Bryan J. Smith -
Craig White -
Dave Gutteridge -
David Campbell -
Johnny Hughes -
Lamar Owen -
Marc D. Field -
Matt Hyclak -
Pasi Pirhonen -
Robert -
Simone