Hi,
I have msc-q7-mb board and tried to install SuSE12.2 on sd card.
Installation performed succesfully but it doesnt start properly.
Does suse12.2 support SD Card installation?
I’m not sure that the problem is whether Suse or BIOS?
Here, in this forum. It is claimed that it is possible but not explained how.
Installing openSUSE Linux 12.1-GNOME
Furthermore,
https://bugzilla.novell.com/show_bug.cgi?id=425367
pointed some drivers .
I haven’t succeeded yet
I got some screen shots about error messages during boot
*Serial ATA AHCI BIOS , Version 1.8
This version support only Hard Dsic and CDROM Devices
*
*error: file ’ /boot/grub2/locale/en.mo.gz’ not found
*
So, I’m not sure the problem is SuSE or BIOS ?
On 01/18/2013 01:46 PM, roll84 wrote:
> I’m not sure that the problem is whether Suse or BIOS?
i can’t imagine why openSUSE would care if the boot code is stored on a
rotating hard drive, or a solid state device, or which exact format of
solid state device (i know it will boot from a rotating hard drive, and
a solid-state drive, and a UBS stick) so i have to assume the problem is
in the bios…
why not ask other msc-q7-mb board users…
is there a forum for those folks?
(sure someone might wander through here, but . . .)
hmmmmmm: can you during boot get to the BIOS set up screen and see if it
offers a setting to boot from SD? (maybe it defaults to boot from ROM or
an SATA/USB connected hard drive)
Thanks for your advices,
I configured bios personally by my self. It is set to boot from SD.
I also can see /dev/mmcblk mount operations during installation.
However,I doubt Bıos like you
I am going to try Fedora next week.And I’ll write results.
I realized several initrd error while I am installing 12.2. Inıtrd does not configured properlly.
If I success Fedora installation on the system, it means that the problem is opensuse
On 01/19/2013 10:56 AM, roll84 wrote:
> I realized several initrd error while I am installing 12.2. Inıtrd
> does not configured properlly.
you might try installing openSUSE using systemv rather than the newer
systemd…
info on the old and new: http://tinyurl.com/75vrr52
how to switch from systemd to systemv in one of my older posts, here
http://tinyurl.com/c6rpdn6
on the other hand, if Fedora installs ok then use it–always use what
works! (by the way, i’m pretty sure the latest Fedora also uses
systemd…and, if it installs ok there, YIPEE for you…and, let us
know…otherwise, try the switch from d to v above…
You may have to take a look at the BIOS settings on handling disks. I remember seeing a BIOS set to use " IDE ", changing that to " AHCI " was the option to choose IIRC.
Here, this post says
*at the first green screen press F5 and select to boot with systemV…
*However, I havent seen green screen. It is freezing before
On 2013-01-21 09:16, roll84 wrote:
> Here, this post says
>
> -at the first green screen press F5 and select to boot with systemV…
>
> -However, I havent seen green screen. It is freezing before
But… on post #3, you say:
> error: file ’ /boot/grub2/locale/en.mo.gz’ not found
What you are asked to should happen a second before or after that
message. If you don’t see it, it is grub which is crashing.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
On installation details I got errors about mkinitrd, device mapper (dev/map) errors
And after installation finish
I am getting this error on the black screen during start up
- 1.955953] i8042 No controller found
doing fast boot
Creating device nodes with udev
Waiting for device /dev/disk/by-id/mmc-SU08G_0x18388229-part2 to appear:
Want me to fall back to /dev/disk/by-id/mmc-SU08G_0x18388229-part2? (Y/n)
Y
Waiting for device /dev/disk/by-id/mmc-SU08G_0x18388229-part2 to appear
sh:cannot set terminal process group (-1): Inappropriate ioctl for device
sh: no job control in this shell*
On the other hand,
I suceeced to install SuSE 12.2 on SD Card in my Desktop PC( i5 Intel Core)
Unfortunately it isnt q7 board.
The difference i realized that while Atom Q7 mounts SD as **/dev/mmcblk **, Desktop system mounts SD as /dev/sdc.
So mkinitrd can properly configured with** */dev/sdc during installation.
Do you have any idea , how does it differ mmcblk between sdc ?
Looks like drivers for your SD card are missing in initrd. You should open bug report about it. In the meantime if you can boot into rescue mode from installation DVD and access your SD card from there, it can (attempted to) be worked around by rebuilding initrd from rescue shell with manually added drivers.
If it was missing driver problem, I shouldnt have installed SuSE on the same SD Card in my Desktop PC , should I ?
Do you think that the drivers in Q7 board are much different than Desktop board ?
So you installed system on one hardware and try to boot on another, right? In this case at least SD controller may be of course completely different model.
Right, I told this @post #12
It is the same SD Card.
From this post it was not clear whether you tried to boot the same SD card.
It is the same SD Card.
You understand the difference between SD card and SD controller used to access this card?
Please provide “lspci -nnvk” output from both systems.
Ok, sorry for confusion.
First, I installed suse 12.2 on Q7 board (atom) within SD card and I can not suceed to boot. Failed
Second, I installed 12.2 on my Desktop (intel i5) within the same SD Card and I can suceed to boot. Ok.
Third, I moved the same Card Q7 board and it doesnt boot. Failed.
Thanks, Actually I have just understood the difference. I will check.
Probably they are different as you say. Because memory blocks are mapped with different names. First one is dev/mmcblk the other one is **/dev/sdc
**Whereas first one is seen as MEMORY device , latter is seen as IDE.
I have the same problems as yours. Were you able to install SuSE on SD card on Q7?