A while back I asked about upgrading Mandriva to openSuse and wondered how smart the installer was. was told that cross distribution upgrades normally didn't work, but that Mageia was written by people that had left mandrake when it became Mandriva and that Mageia could update Mandrake/Mandriva. See early post for my reasons.
Well thank you guys, I did upgrade to Mageia 2 and am happy with that.
But I also put Mageia on a scratch machine and pushed it around in was that I wouldn't dream of for a production machine .... you know the kind of abuse .... :-) And then I decided to put openSuse 12.2 on the scratch machine. In went the DVD, reboot and when it do the the screen where I said "probing ..." it then offered "Install or upgrade". WTF I picked upgrade and Lo And Behold the installer was smart enough to upgrade my Mageia to openSuse !
Well almost. When it got to the bootloader it tried to install LILO.
Nonono, I'd been using grub. I went back and it did not offer me a choice of the bootloader. It then muffed Lilo and and I had a system that wouldn't boot.
You can, I found, "upgrade" all over again, but it still doesn't want to use grub.
Close .... so close ....
On 2012-12-31 17:59 (GMT-0500) Anton Aylward composed:
I also put Mageia on a scratch machine and pushed it around in was that I wouldn't dream of for a production machine .... you know the kind of abuse .... :-) And then I decided to put openSuse 12.2 on the scratch machine. In went the DVD, reboot and when it do the the screen where I said "probing ..." it then offered "Install or upgrade". WTF I picked upgrade and Lo And Behold the installer was smart enough to upgrade my Mageia to openSuse !
Well almost. When it got to the bootloader it tried to install LILO.
Nonono, I'd been using grub. I went back and it did not offer me a choice of the bootloader. It then muffed Lilo and and I had a system that wouldn't boot.
You can, I found, "upgrade" all over again, but it still doesn't want to use grub.
Close .... so close ....
Closer than you think. Upgrading means not formatting, which means not wiping existing bootloader. All you needed to do was install no bootloader while upgrading, then boot openSUSE with the old bootloader, then install your choice of openSUSE bootloader.
Don't forget, Grub Legacy doesn't need a menu to get you booted, just as Grub2 shouldn't need a grub.cfg to get you booted. To boot with wrong kernel & initrd in the stanzas you only need edit an existing stanza, or drop to Grub prompt and do manually what the menu would do if set up properly. openSUSE makes this easy to, by making symlinks to the kernel and initrd called vmlinuz and initrd, easy to remember, and easy to type at a Grub prompt.
Of course if you're configured to multiboot, you can boot and/or repair via HD.
Even on a brand new or freshly wiped HD you don't need to install a bootloader while installing. What can be done from any live Linux boot where the bootloader you want is on the live media. With wiped or new HDs, I do if first using a Knoppix CD. Sounds like that's an option for you right now.
After upgrading the Mageia to openSuse 12.2 I did a 'zypper up'. I really love the suse admin suite, zypper/yast and the repository management/prioritization tools. They really are superior to all the other distros!
But the 'zypper up' resulted in a number of runs of 'mkinitrd'. Obviously one of the kernel upgrade, but also for things related to the kernel and boot such as 'plymouth'. It was time consuming on the dinky, underpowered scratch machine.
Worse, the initrd files are enormous! Up around 15M. Is there any way to bring them down?
Mageia used 'drakut'. I see that there has been presentations on it at the suse conferences and while its still under-documented it seems well integrated and the config files are very understandable. Mkinitrd seems lots and lots and lots and lots and lots of scripts and little in the way of the include/exclude config lists that drakut has.
So how can I get the initrd size down?
On 2012-12-31 22:04 (GMT-0500) Anton Aylward composed:
'zypper up' resulted in a number of runs of 'mkinitrd'. Obviously one of the kernel upgrade, but also for things related to the kernel and boot such as 'plymouth'. It was time consuming on the dinky, underpowered scratch machine.
https://bugzilla.novell.com/show_bug.cgi?id=786318
Worse, the initrd files are enormous! Up around 15M. Is there any way to bring them down?
Change your hardware? What do you have? Mine are around half that size.
Cristian Rodríguez said the following on 01/01/2013 01:01 AM:
El 01/01/13 00:04, Anton Aylward escribió:
So how can I get the initrd size down?
Using dracut of course. I have it working but in Factory/12.3
I've tried dracut on Mageia and fedora and I like it, but when will we see it in core openSuse?
Anton Aylward wrote:
Cristian Rodríguez said the following on 01/01/2013 01:01 AM:
El 01/01/13 00:04, Anton Aylward escribió:
So how can I get the initrd size down?
Using dracut of course. I have it working but in Factory/12.3
I've tried dracut on Mageia and fedora and I like it, but when will we see it in core openSuse?
When all of the accumulated "knowledge" in mkinitrd has been transplanted to dracut.
Felix Miata said the following on 12/31/2012 06:35 PM:
Close .... so close ....
Closer than you think. Upgrading means not formatting, which means not wiping existing bootloader. All you needed to do was install no bootloader while upgrading, then boot openSUSE with the old bootloader, then install your choice of openSUSE bootloader.
That's what I *thought*. What I found was that the suse installer had insisted on _not_ asking me first and had zapped the bootloader and screwed up the attempted lilo.
I repeat: it didn't ask; it didn't offer me a choice of which bootloader (as it might in a normal install) and didn't offer me a choice to edit the menu (as it might in a normal install). It just attempted to create a lilo and made a mess of that.
I'm now out of time to experiment any further. This was supposed to be a 'get the file server working so I can finish my year end accounts for the revenue' holiday project and now I've just one day to do all the accounts!
If I get to revisit this I'll let you know. :-0
Felix Miata wrote:
On 2012-12-31 22:04 (GMT-0500) Anton Aylward composed:
'zypper up' resulted in a number of runs of 'mkinitrd'. Obviously one of the kernel upgrade, but also for things related to the kernel and boot such as 'plymouth'. It was time consuming on the dinky, underpowered scratch machine.
https://bugzilla.novell.com/show_bug.cgi?id=786318
Worse, the initrd files are enormous! Up around 15M. Is there any way to bring them down?
Change your hardware? What do you have? Mine are around half that size.
Mine are about 4M.
Per Jessen said the following on 01/01/2013 06:02 AM:
Felix Miata wrote:
On 2012-12-31 22:04 (GMT-0500) Anton Aylward composed:
'zypper up' resulted in a number of runs of 'mkinitrd'. Obviously one of the kernel upgrade, but also for things related to the kernel and boot such as 'plymouth'. It was time consuming on the dinky, underpowered scratch machine.
https://bugzilla.novell.com/show_bug.cgi?id=786318
Worse, the initrd files are enormous! Up around 15M. Is there any way to bring them down?
Change your hardware? What do you have? Mine are around half that size.
Mine are about 4M.
How did you achieve that?
On 2013-01-01 06:01 (GMT-0500) Anton Aylward composed:
What I found was that the suse installer had insisted on _not_ asking me first and had zapped the bootloader and screwed up the attempted lilo.
I repeat: it didn't ask; it didn't offer me a choice of which bootloader (as it might in a normal install) and didn't offer me a choice to edit the menu (as it might in a normal install). It just attempted to create a lilo and made a mess of that.
This has never happened to me, but I don't use LVM. IIRC, Lilo is either the only option, or the default option, for openSUSE installations to LVM, at least for certain configurations I don't use.
Anton Aylward wrote:
Per Jessen said the following on 01/01/2013 06:02 AM:
Felix Miata wrote:
On 2012-12-31 22:04 (GMT-0500) Anton Aylward composed:
'zypper up' resulted in a number of runs of 'mkinitrd'. Obviously one of the kernel upgrade, but also for things related to the kernel and boot such as 'plymouth'. It was time consuming on the dinky, underpowered scratch machine.
https://bugzilla.novell.com/show_bug.cgi?id=786318
Worse, the initrd files are enormous! Up around 15M. Is there any way to bring them down?
Change your hardware? What do you have? Mine are around half that size.
Mine are about 4M.
How did you achieve that?
I don't think I do anything in particular - I just build it with mkinitrd. The size will depend on the system/functionality though - on a xen guest (12.2) I see an initrd of about 4Mb, on a physical server (11.0) I see about 5Mb, on my newish 12.2 mythtv box, it's about 16Mb.
If you want to know what it's made up of:
mkdir ~/gg cd gg gzip -dc initrd | cpio --extract -d
Per Jessen wrote:
Anton Aylward wrote:
Per Jessen said the following on 01/01/2013 06:02 AM:
Felix Miata wrote:
On 2012-12-31 22:04 (GMT-0500) Anton Aylward composed:
'zypper up' resulted in a number of runs of 'mkinitrd'. Obviously one of the kernel upgrade, but also for things related to the kernel and boot such as 'plymouth'. It was time consuming on the dinky, underpowered scratch machine.
https://bugzilla.novell.com/show_bug.cgi?id=786318
Worse, the initrd files are enormous! Up around 15M. Is there any way to bring them down?
Change your hardware? What do you have? Mine are around half that size.
Mine are about 4M.
How did you achieve that?
I don't think I do anything in particular - I just build it with mkinitrd. The size will depend on the system/functionality though - on a xen guest (12.2) I see an initrd of about 4Mb, on a physical server (11.0) I see about 5Mb, on my newish 12.2 mythtv box, it's about 16Mb.
The latter has a much larger usr/ directory of about 23M, the xen initrd only has 3.3M.
On 2013-01-01 17:38 (GMT+0100) Per Jessen composed:
Worse, the initrd files are enormous! Up around 15M. Is there any way to bring them down?
Change your hardware? What do you have? Mine are around half that size.
If you want to know what it's made up of:
mkdir ~/gg cd gg gzip -dc initrd | cpio --extract -d
Or since 11.1, the short way:
lsinitrd /boot/initrd
Since it's a part of mkinitrd rpm, let's hope it doesn't get lost when dracut obsoletes it.
Felix Miata said the following on 01/01/2013 01:54 PM:
On 2013-01-01 17:38 (GMT+0100) Per Jessen composed:
Worse, the initrd files are enormous! Up around 15M. Is there any way to bring them down?
Change your hardware? What do you have? Mine are around half that size.
If you want to know what it's made up of:
Or since 11.1, the short way:
lsinitrd /boot/initrd
WOW! An incredible amount of stuff I don't need or don't thin I don't need. All those languages and keyboard mappings and drivers for video cards I don't have and more!
I can see how to exclude then under dracut - really nice config system there! But what about exclusions under the traditional mkinitrd of suse. What I see in /etc/sysconfig/kernel is more about _including_ that excluding.
On Tue, 01 Jan 2013 13:54:10 -0500 Felix Miata mrmazda@earthlink.net wrote:
lsinitrd /boot/initrd
It would be useful to have: lsinitrd /boot/initrd | less as my initrd listing has over 500 lines, so having 'less' in the game gives ability to search listing instead to read line by line :)
On Tue, 01 Jan 2013 14:05:37 -0500 Anton Aylward opensuse@antonaylward.com wrote:
I can see how to exclude then under dracut - really nice config system there! But what about exclusions under the traditional mkinitrd of suse. What I see in /etc/sysconfig/kernel is more about _including_ that excluding.
man 8 mkinitd
is informative on general design of mkinitrd.
Rajko said the following on 01/01/2013 03:53 PM:
On Tue, 01 Jan 2013 14:05:37 -0500 Anton Aylward opensuse@antonaylward.com wrote:
I can see how to exclude then under dracut - really nice config system there! But what about exclusions under the traditional mkinitrd of suse. What I see in /etc/sysconfig/kernel is more about _including_ that excluding.
man 8 mkinitd
is informative on general design of mkinitrd.
Well, I don't know about "design" in the sense of architecture. And it makes clear my point that it is about what to include rather than what to exclude.
Man pages aside, just going by config files, dracut is going to be easier to configure to do what you want. heck, I've run dracut interactively on fedora and it will tell you what the stuff it can include and exclude will do!
If its design we're talking about then dracut is a lot easier to work with for non-specialists. and lets face it, there are a lot of people who want to customise their kernel ONCE and don't want to have a long learning curve. When it gets here for Suse I think dracut will do that.
Anton Aylward wrote:
Rajko said the following on 01/01/2013 03:53 PM:
On Tue, 01 Jan 2013 14:05:37 -0500 Anton Aylward opensuse@antonaylward.com wrote:
I can see how to exclude then under dracut - really nice config system there! But what about exclusions under the traditional mkinitrd of suse. What I see in /etc/sysconfig/kernel is more about _including_ that excluding.
man 8 mkinitd
is informative on general design of mkinitrd.
Well, I don't know about "design" in the sense of architecture. And it makes clear my point that it is about what to include rather than what to exclude.
Man pages aside, just going by config files, dracut is going to be easier to configure to do what you want. heck, I've run dracut interactively on fedora and it will tell you what the stuff it can include and exclude will do!
If its design we're talking about then dracut is a lot easier to work with for non-specialists. and lets face it, there are a lot of people who want to customise their kernel ONCE and don't want to have a long learning curve. When it gets here for Suse I think dracut will do that.
Hmm, I think I would still count building a new initrd as a job for a specialist. openSUSE ought to cater for every other non-specialist use case.
Felix Miata wrote:
On 2013-01-01 17:38 (GMT+0100) Per Jessen composed:
Worse, the initrd files are enormous! Up around 15M. Is there any way to bring them down?
Change your hardware? What do you have? Mine are around half that size.
If you want to know what it's made up of:
mkdir ~/gg cd gg gzip -dc initrd | cpio --extract -d
Or since 11.1, the short way:
lsinitrd /boot/initrd
Thanks, I'll have to try to remember that one :-)
One of the problems I'm having is that the 12.2 DVD seems to do odd EDID behaviour. When I boot from the 12.2 DVD I get
Analog Out of range 46.4kHz / 43 Hz
Yes, I know there should be a "F3" for screen size. I don't even see that. This out of range is immediate.
A few notes:
1. It happens with *All* my LCD screens.
2. If I dig out an old CRT from my closet and plug that in, then I see the boot screen and can work with the install.
3. If I try installing an old version of openSuse, 11.2 or 11.4 for example, I don't have this problem with the LCD screens.
4. I've tried a few other distributions and they don't have this problem either.
My primary LCD monitor is an LG1953. Fedora 15/16/17 seem to boot in (when I use text-mode) 1024x768 (that what the gfxmode is set to for grub) the see the EDID and jump to the higher resolution.
I see articles like this http://ubuntuguide.net/monitor-signal-out-of-range-problem-in-ubuntu-12-04-p... but that only applies AFTER the system is up.
Any ideas, guys?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
El 2013-01-02 a las 07:51 -0500, Anton Aylward escribió:
- It happens with *All* my LCD screens.
Any ideas, guys?
Cable or card.
- -- Cheers
Carlos E. R. (from 11.4, with Evergreen, x86_64 "Celadon" (Minas Tirith))
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
El 2013-01-02 a las 09:04 +0100, Per Jessen escribió:
Hmm, I think I would still count building a new initrd as a job for a specialist. openSUSE ought to cater for every other non-specialist use case.
Right. I do not see why I should learn how to configure mkinird or dracut or whatever. I expect they do the right thing, and I mostly do not care if the resulting image has 5 megs or 20 - as long as it fits inside a boot partition.
- -- Cheers
Carlos E. R. (from 11.4, with Evergreen, x86_64 "Celadon" (Minas Tirith))
On Wed, 2 Jan 2013 14:17:09 +0100 (CET) "Carlos E. R." robin.listas@telefonica.net wrote:
El 2013-01-02 a las 07:51 -0500, Anton Aylward escribió:
- It happens with *All* my LCD screens.
Any ideas, guys?
Cable or card.
or default in CMOS setting?
Carlos E. R. said the following on 01/02/2013 08:17 AM:
El 2013-01-02 a las 07:51 -0500, Anton Aylward escribió:
- It happens with *All* my LCD screens.
Any ideas, guys?
Cable or card.
RWIS: Same card, same cable; change LCD for CRT.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
El 2013-01-02 a las 08:43 -0500, Anton Aylward escribió:
Carlos E. R. said the following on 01/02/2013 08:17 AM:
El 2013-01-02 a las 07:51 -0500, Anton Aylward escribió:
- It happens with *All* my LCD screens.
Any ideas, guys?
Cable or card.
RWIS: Same card, same cable; change LCD for CRT.
Well, that is what I say, try a different cable.
- -- Cheers
Carlos E. R. (from 11.4, with Evergreen, x86_64 "Celadon" (Minas Tirith))
On 2013-01-02 07:51 (GMT-0500) Anton Aylward composed:
One of the problems I'm having is that the 12.2 DVD seems to do odd EDID behaviour. When I boot from the 12.2 DVD I get
Analog Out of range 46.4kHz / 43 Hz
Yes, I know there should be a "F3" for screen size. I don't even see that. This out of range is immediate.
Meaning what, screen goes black as soon as POST messages finish? Or does it happen when the first anything from booting the DVD should be drawing?
A few notes:
- It happens with *All* my LCD screens.
- If I dig out an old CRT from my closet and plug that in, then I see
the boot screen and can work with the install.
Since you can, does it really matter if the 12.2 DVD doesn't like your display?
- If I try installing an old version of openSuse, 11.2 or 11.4 for
example, I don't have this problem with the LCD screens.
- I've tried a few other distributions and they don't have this problem
either.
My primary LCD monitor is an LG1953. Fedora 15/16/17 seem to boot in (when I use text-mode) 1024x768 (that what the gfxmode is set to for grub) the see the EDID and jump to the higher resolution.
I do not understand what last clause is supposed to communicate.
I see articles like this http://ubuntuguide.net/monitor-signal-out-of-range-problem-in-ubuntu-12-04-p... but that only applies AFTER the system is up.
Any ideas, guys?
Assuming DVD is OK, could be some bug in the installation kernel's KMS function that only shows up with your display's particular EDID. Did you md5sum the iso and the burned DVD?
Is only one PC doing this?
What video chip? You may have mentioned upthread, but I don't remember. Can you add or remove a video card to retry?
Do you have another cable you could try, especially one with EDID function inoperable due to a missing pin?
Can that PC already boot something else from Grub? If it can, load the installation kernel and initrd with Grub instead of starting from the DVD, from which you can use vga=791 and/or video=1366x768@60 and/or any number of other options from http://en.opensuse.org/SDB:Linuxrc .
Felix Miata said the following on 01/02/2013 07:09 PM:
On 2013-01-02 07:51 (GMT-0500) Anton Aylward composed:
One of the problems I'm having is that the 12.2 DVD seems to do odd EDID behaviour. When I boot from the 12.2 DVD I get
Analog Out of range 46.4kHz / 43 Hz
Yes, I know there should be a "F3" for screen size. I don't even see that. This out of range is immediate.
Meaning what, screen goes black as soon as POST messages finish? Or does it happen when the first anything from booting the DVD should be drawing?
As soon as the POST finishes ... well as soon as the DVD boots. I never see anything past the POST; except the "out of range" notice on the monitor. I don't see the welcome screen, I don't see the screen offering F1, F2, F3 and the menu of install/boot from hard dis and whatever else.
Perhaps the ISOLINUX notice flashes by too quickly ... but as soon as the DVD boots the screen blanks.
A few notes:
- It happens with *All* my LCD screens.
- If I dig out an old CRT from my closet and plug that in, then I
see the boot screen and can work with the install.
Since you can, does it really matter if the 12.2 DVD doesn't like your display?
Its a crappy old 15" that buzzes ..
- If I try installing an old version of openSuse, 11.2 or 11.4
for example, I don't have this problem with the LCD screens.
So what is it with the ISOLINUX on the 12.2 DVD? Is it booting from a late model - grub2 - version of ISOLINUX or something?
Any ideas, guys?
Assuming DVD is OK, could be some bug in the installation kernel's KMS function that only shows up with your display's particular EDID. Did you md5sum the iso and the burned DVD?
Yes, the MD5 is OK.
As I say, its specific to LCDs
Do you have another cable you could try, especially one with EDID function inoperable due to a missing pin?
Same cable, same card/machine with Fedora and Mageia works. I can set them nosplash and watch the messages and see the 'jump' when they see EDID and change resolution.
Can that PC already boot something else from Grub? If it can, load the installation kernel and initrd with Grub instead of starting from the DVD, from which you can use vga=791 and/or video=1366x768@60
Ah, this LG1952 only goes to 1280x1024@60.
And I'm not sure what you're asking/how to do that. This is an INSTALL. Unless I'm using another distribution .. Think of it as a blank disk.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
El 2013-01-02 a las 20:52 -0500, Anton Aylward escribió:
Same cable, same card/machine with Fedora and Mageia works. I can set them nosplash and watch the messages and see the 'jump' when they see EDID and change resolution.
Nevertheless, get another cable and try it.
- -- Cheers
Carlos E. R. (from 11.4, with Evergreen, x86_64 "Celadon" (Minas Tirith))
On 2013-01-02 20:52 (GMT-0500) Anton Aylward composed:
Felix Miata composed:
On 2013-01-02 07:51 (GMT-0500) Anton Aylward composed:
One of the problems I'm having is that the 12.2 DVD seems to do odd EDID behaviour. When I boot from the 12.2 DVD I get
Analog Out of range 46.4kHz / 43 Hz
Yes, I know there should be a "F3" for screen size. I don't even see that. This out of range is immediate.
Meaning what, screen goes black as soon as POST messages finish? Or does it happen when the first anything from booting the DVD should be drawing?
As soon as the POST finishes ... well as soon as the DVD boots. I never see anything past the POST; except the "out of range" notice on the monitor. I don't see the welcome screen, I don't see the screen offering F1, F2, F3 and the menu of install/boot from hard dis and whatever else.
Did you try the auto-adjust function while it displayed the out of range message?
Perhaps the ISOLINUX notice flashes by too quickly ... but as soon as the DVD boots the screen blanks.
A few notes:
- It happens with *All* my LCD screens.
More than one I don't recall you mentioning previously, not that my recall is anything to be proud of. :-p
- If I dig out an old CRT from my closet and plug that in, then I
see the boot screen and can work with the install.
Since you can, does it really matter if the 12.2 DVD doesn't like your display?
Its a crappy old 15" that buzzes ..
So it buzzes an hour or two until you finish installing. Is that a real problem?
- If I try installing an old version of openSuse, 11.2 or 11.4
for example, I don't have this problem with the LCD screens.
So what is it with the ISOLINUX on the 12.2 DVD? Is it booting from a late model - grub2 - version of ISOLINUX or something?
Pretty sure only ISOLINUX on DVD boot. But, the installation kernel makes it go, and KMS could well be the culprit if it is a KMS kernel.
Any ideas, guys?
Assuming DVD is OK, could be some bug in the installation kernel's KMS function that only shows up with your display's particular EDID. Did you md5sum the iso and the burned DVD?
Yes, the MD5 is OK.
As I say, its specific to LCDs
Oh, so you tried more than one LCD, and all you tried are LG195x models?
Do you have another cable you could try, especially one with EDID function inoperable due to a missing pin?
Same cable, same card/machine with Fedora and Mageia works.
The point was to see if a different video card or cable changes anything. Now that we know you have a garage full of LG LCDs it probably doesn't matter. :-)
http://www.badcaps.net/forum/showthread.php?t=15217 implies you may have tried those longer than a short time ago. What you could be experiencing is what http://en.wikipedia.org/wiki/Capacitor_plague describes. ISTR out of range might have been what clued me that my ViewSonic was exhibiting that problem, since solved in about 30 minutes with a soldering iron and less than $3 in parts already on hand.
I can set them nosplash and watch the messages and see the 'jump' when they see EDID and change resolution.
Can that PC already boot something else from Grub? If it can, load the installation kernel and initrd with Grub instead of starting from the DVD, from which you can use vga=791 and/or video=1366x768@60
Ah, this LG1952 only goes to 1280x1024@60.
In http://lists.opensuse.org/opensuse/2013-01/msg00026.html you wrote LG1953. Offlist you wrote LG1953S after which Google found me http://www.digi.co.id/lcd-lg-1953s.html that told me what you have is 1366x768. LG1952 is indeed 1280x1024, so if 1952 is in fact what you have, put video=1280x1024@60 on cmdline and see what happens, even if it means you must first boot Knoppix, install Grub, and put the installation kernel and initrd on it so you can initiate installation without a DVD.
And I'm not sure what you're asking/how to do that.
I didn't know whether or not you were trying to install to an empty HD.
This is an INSTALL. Unless I'm using another distribution .. Think of it as a blank disk.
OK, but that needn't stop you from installing without using a DVD that doesn't work as expected. I rarely install from OM, and almost as infrequently even download an iso.
Felix Miata said the following on 01/02/2013 11:06 PM:
On 2013-01-02 20:52 (GMT-0500) Anton Aylward composed:
Meaning what, screen goes black as soon as POST messages finish? Or does it happen when the first anything from booting the DVD should be drawing?
As soon as the POST finishes ... well as soon as the DVD boots. I never see anything past the POST; except the "out of range" notice on the monitor. I don't see the welcome screen, I don't see the screen offering F1, F2, F3 and the menu of install/boot from hard dis and whatever else.
Did you try the auto-adjust function while it displayed the out of range message?
The LG tries to be smart, but look at those numbers -- this is too far out of range.
Perhaps the ISOLINUX notice flashes by too quickly ... but as soon as the DVD boots the screen blanks.
A few notes:
- If I dig out an old CRT from my closet and plug that in,
then I see the boot screen and can work with the install.
Since you can, does it really matter if the 12.2 DVD doesn't like your display?
Its a crappy old 15" that buzzes ..
So it buzzes an hour or two until you finish installing. Is that a real problem?
And then I carry the machine up from the basement and plug it in in the office with the 'production' setting, the LCD, and ... well, no, it won't see the EDID and settles for 800x600 and won't shift. I've tried editing the boot line, the grub/gfxboot and the xorg.conf to include 1024, 1280 with various modelines. NADA.
So what is it with the ISOLINUX on the 12.2 DVD? Is it booting from a late model - grub2 - version of ISOLINUX or something?
Pretty sure only ISOLINUX on DVD boot. But, the installation kernel makes it go, and KMS could well be the culprit if it is a KMS kernel.
Any ideas, guys?
Assuming DVD is OK, could be some bug in the installation kernel's KMS function that only shows up with your display's particular EDID. Did you md5sum the iso and the burned DVD?
Yes, the MD5 is OK.
As I say, its specific to LCDs
Oh, so you tried more than one LCD, and all you tried are LG195x models?
No, I've tried 3 generations including one that won't go beyond 1024, and old Philips. I'll see if I can get a HP to try...
Do you have another cable you could try, especially one with EDID function inoperable due to a missing pin?
Same cable, same card/machine with Fedora and Mageia works.
The point was to see if a different video card or cable changes anything. Now that we know you have a garage full of LG LCDs it probably doesn't matter. :-)
http://www.badcaps.net/forum/showthread.php?t=15217 implies you may have tried those longer than a short time ago. What you could be experiencing is what http://en.wikipedia.org/wiki/Capacitor_plague describes. ISTR out of range might have been what clued me that my ViewSonic was exhibiting that problem, since solved in about 30 minutes with a soldering iron and less than $3 in parts already on hand.
LOL! Yes I know abut that. People were throwing out LGs by the cartload and some of us 'rescued' them and, as you say, applied 'hit iron'.
No, this LG is solid. As I say, it works just fine with Fedora 15 though 17.
As I said:
I can set them nosplash and watch the messages and see the 'jump' when they see EDID and change resolution.
Can that PC already boot something else from Grub? If it can, load the installation kernel and initrd with Grub instead of starting from the DVD, from which you can use vga=791 and/or video=1366x768@60
Ah, this LG1952 only goes to 1280x1024@60.
In http://lists.opensuse.org/opensuse/2013-01/msg00026.html you wrote LG1953. Offlist you wrote LG1953S after which Google found me http://www.digi.co.id/lcd-lg-1953s.html that told me what you have is 1366x768. LG1952 is indeed 1280x1024, so if 1952 is in fact what you have, put video=1280x1024@60 on cmdline and see what happens, even if it means you must first boot Knoppix, install Grub, and put the installation kernel and initrd on it so you can initiate installation without a DVD.
My typo. I just crept round the back and the label says 1953TS. The manual I have says 1280x1024 http://www.lg.com/uk/monitors/lg-L1953S-lcd-monitor
Hmm.
When I look at the boot command line I see edd=off highres=off nomodeset nohz=off Now why did it put all that in there?
I just tried editing the command line as you suggested. No change.
On 2013-01-03 06:32 (GMT-0500) Anton Aylward composed:
Its a crappy old 15" that buzzes ..
So it buzzes an hour or two until you finish installing. Is that a real problem?
And then I carry the machine up from the basement and plug it in in the office with the 'production' setting, the LCD, and ... well, no, it won't see the EDID and settles for 800x600 and won't shift. I've tried editing the boot line, the grub/gfxboot and the xorg.conf to include 1024, 1280 with various modelines. NADA.
So this isn't about installation any more? If so, you should be using either xorg.conf or xorg.conf.d/, but not both, unless you're really up on how they work together or not. What's your video chip, and if not Intel, which driver is actually used according to Xorg.0.log?
Try http://fm.no-ip.com/Share/xorg.conf-minimal-EDID-workaround and if it doesn't help as is, uncomment the refresh and/or sync lines. Or, instead of xorg.conf, use that file as a guide to configuring via xorg.conf.d/.
No, this LG is solid. As I say, it works just fine with Fedora 15 though 17.
Today? Or a month or three ago?
When I look at the boot command line I see edd=off highres=off nomodeset nohz=off Now why did it put all that in there?
If in the default kernel stanza, they may have been what were used for installation with the old CRT. Normally they only show up on installed systems in failsafe stanzas. Maybe it's time you examined your Grub menu file, and /etc/sysconfig/bootloader. It could be you are suffering from a mangled bootloader installation and/or configuration. Nomodeset is a fallback/failsafe that is capable of causing more trouble than it solves.
I just tried editing the command line as you suggested. No change.
Try an opposite editing approach: delete everything on the kernel line except "kernel vmlinuz-3.4.6-xxx-desktop", and at least try without using any xorg.conf* if you get booted without the LCD going to sleep.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
El 2013-01-03 a las 06:32 -0500, Anton Aylward escribió:
So it buzzes an hour or two until you finish installing. Is that a real problem?
And then I carry the machine up from the basement and plug it in in the office with the 'production' setting, the LCD, and ... well, no, it won't see the EDID and settles for 800x600 and won't shift. I've tried editing the boot line, the grub/gfxboot and the xorg.conf to include 1024, 1280 with various modelines. NADA.
So, not even the CRT works.
What's the thing that on all those test failures remain the same? One the cable, two the card. All those failures have that hardware in common. Either your cable or your card is broken, so change at least one of them to try! Gosh!
- -- Cheers
Carlos E. R. (from 11.4, with Evergreen, x86_64 "Celadon" (Minas Tirith))
On 2013-01-03 18:54 (GMT+0100) Carlos E. R. composed:
Anton Aylward composed:
And then I carry the machine up from the basement and plug it in in the office with the 'production' setting, the LCD, and ... well, no, it won't see the EDID and settles for 800x600 and won't shift. I've tried editing the boot line, the grub/gfxboot and the xorg.conf to include 1024, 1280 with various modelines. NADA.
So, not even the CRT works.
What's the thing that on all those test failures remain the same? One the cable, two the card. All those failures have that hardware in common. Either your cable or your card is broken, so change at least one of them to try! Gosh!
As previously reported, Mageia, multiple Fedoras and pre-12.2 openSUSE have no such trouble. A change of one of the components you listed might have a useful impact, but I would be unsurprised if none do - except for the gfx - his gfxchip is SiS. Nuff said.
Carlos E. R. said the following on 01/03/2013 12:54 PM:
El 2013-01-03 a las 06:32 -0500, Anton Aylward escribió:
So it buzzes an hour or two until you finish installing. Is that a real problem?
And then I carry the machine up from the basement and plug it in in the office with the 'production' setting, the LCD, and ... well, no, it won't see the EDID and settles for 800x600 and won't shift. I've tried editing the boot line, the grub/gfxboot and the xorg.conf to include 1024, 1280 with various modelines. NADA.
So, not even the CRT works.
What's the thing that on all those test failures remain the same? One the cable, two the card. All those failures have that hardware in common. Either your cable or your card is broken, so change at least one of them to try! Gosh!
Perhaps I didn't make it clear - there are TWO environments
1. The "bench" in the basement" with the "closet of anxieties", that is a cupboard full of odds and sods. There's an anecdote related to that which is not relevant here. The crappy old monitor(s) and other retired equipment of dubious quality lives there, hence the name.
2. The "Office" (or pig-pen or cubicle farm...). That's where work gets done, when it does. See Scott Adams and Dilbert cartoons. Good looking equipment (aka dust free). There's supposed to be a dress code. No CRTs here, all LCDs.
Most places I've worked have had a "production" and "workbench" setting.
-
Anton Aylward -
Carl Hartung -
Carlos E. R. -
Cristian Rodríguez -
Felix Miata -
Per Jessen -
Rajko