Opened 10 years ago

Closed 10 years ago

#466 closed defect (fixed)

Only if C2SBX is "supported" by Mindi

Reported by: rob Owned by: Bruno Cornec
Priority: normal Milestone: 2.2.9.6
Component: mondo Version: 2.2.9.4
Severity: normal Keywords:
Cc:

Description

Prior to looking at the log files -- which might be pointless, since when I run the recommended test on mindi, I get the following, in the text on the terminal

WARNING: " No Hardware Support for C2SBX" new line... you can ask your manufacturer to contribute to the mindi project.

a) Mindi boot disk does seem to work, I get a boot prompt, when I boot from this CD.

b) There is no obvious error messages, in mindi.log (attached)

c) is it worth attempting to continue, since the warning seems to be in regard to this Supermicro

motherboard, C2SBX --- which is only compatible with other versions of linux (older) and only

with IDE hard drives, and SATA hard drives (without RAID)

http://www.supermicro.com/support/resources/OS/C2.cfm

Also note I use ECC memory, 4 GB

Note, There is a flash of a message before the blue screen window comes up, I think you have a windows 9x partition. OpenSuse? 11.2 was loaded onto this system.

As for mondo archive, I get get a segmentation error when I try various devices, Hard Drive, DvD, CD, and USB.

Mondo archive -- regardless of which option I chose (HD, USB, DVD, CD) always seems to have an error referencing the CD.

CD-R option (path /dev/sr0) mondoarchiveCDR.log - attached CD-RW same mondoarchiveCDRW.log attached USB default mondoarchriveUSB.log attached. DvD same /sr0 mondoarchiveDvD.log attached.

All these methods bring up a segmentation error.

Change History (2)

comment:1 Changed 10 years ago by Bruno Cornec

Milestone: 2.2.9.52.2.9.6

A Warning is not an error. Only HP ProLiant? do not have that warning at the moment.

Having a prompt at mindi boot is normal.

No log has been attached for mondoarchive so can't really comment.

comment:2 Changed 10 years ago by Bruno Cornec

Resolution: fixed
Status: newclosed

A segfault pb has been indeed solved now as of rev [2747] (and previous ones). Will be in 2.2.9.6.

Note: See TracTickets for help on using tickets.