i downloaded the suse-11.1 iso and burnt cd.
the cd boots up in laptop toshiba tecra 9000
my desktop p4 512mb 945 motherboard the cd video is not ok.i get only vertical colored lines and patches . i cannot even ctl alt F1
no mouse no keyboard nothing.just hard reset.
i have tried various video mode options available but nothing seems to work.
i am posting this from laptop cd bootup suse-11.1 kde-4.1.3 desktop.
does anybody can suggest how i can boot this cd in 845 intel mother board computer?
i tried bootin in runlevel 1
i got login root worked.
startx gives lot of error like frame buffer allocation errors and no X.
any help is appreciated.
now i feel i saved my suse-11.0 install by not doing zypper dup.
seems either my i810 is not supported or frame buffer is giving problem.
help required.
I think you’ve probably run into problems with the new intel graphics driver.
If you’re very keen to play with 11.1 (sooner rather than later, when perhaps fixes tempt someone to update the Live CDs) then try a text mode install (available with Net install CD, or DVD) which should use vesafb, then install X later, using the older method in the intel driver that the developer doesn’t want to support any more (rather than the newer EXA).
There’s been fair amount of discussion in the Factory mail list, about problems with Intel grafix, so you could look for the relevant thread for the details.
i wonder why the text mode in the F3 video selector does try to make X and kde .
ok i can try to install from runlevel 1
what is command for selecting video driver manually?
i find my keyboard and mouse are also not working with the X server with default video it finds.
the plus is i have installed suse-11.1 in my laptop successfully after 5 trials.
the grub install has many hidden and not explained auto selected options which makes the hdd not bootable disk.
i had to make trial and error of the settings to get my laptop boot up and finally into suse-11.1:)
why bootable from extended partition option?
how can i make a bootable hdd bootable from sda2
how the bios can see such a hdd?
Because GRUB can install it’s first stage in the MBR, rather than rely on “generic” boot code, looking for active partitions.
There’s also space in super-block of ext2/ext3 partitions for boot loader, which is a reason why it can be installed in a primary partition to.
With extended partions, either the loader is using some unused blocks, or it’s relying on the super-block of the first logical partition. If you really want to know, you’ll need to check documentation and explanations of GRUB. I can’t rely on memory here, it’s not very relevant in practice.
To select text mode, I think you find an option in the screen resolution menu ]