[indiana-discuss] OpenSolaris installation: -kdv brought the installation to kmdb

[Jingci Wang]

FYI

The errors were due to wireless driver was not able to be connected as 
its switch was off.
Errors disappeared after turn on the switch on the lab top.

Jingci


On 05/04/09 09:15, Jingci Wang wrote:
> Hi Mary,
>
> Please see below.
>
> On 05/02/09 10:40, mary ding wrote:
>> Jingci:
>>
>> If you boot kmdb with the -d option, then you can do this:
>>
>> This will cause the kernel debugger to load
>>
>> Loading kmdb...
>>
>> Welcome to kmdb
>> kmdb: unable to determine terminal type: assuming `vt100'
>> Loaded modules: [ unix krtld genunix ]
>> [0]>
>>
>> At the prompt, enter "moddebug/W 0x80000000", <return> and then ":c",
>> <return> which will then print out each module as it's being loaded.
>> Hopefully it might give more data on why there is warning in iwk_init
>
> Many stuffs appeared on the screen by doing the above, then moved to 
> the installation the next step.
> How to get those data out?
>
> Thanks,
> Jingci
>
>>
>>
>> Jingci Wang wrote:
>>> Hi,
>>>
>>> I work for Soalris Cluster QA team and I am working on b111a 
>>> installation on notebooks.
>>> As I am seeing errors at the very beginning of the process:
>>>
>>> WARNING: iwk_int():Radio transmitter is off
>>> WARNING: iwk_m_start(): failed to initialize hardware
>>> WARNING: iwk_int():Radio transmitter is off
>>> WARNING: iwk_m_start(): failed to initialize hardware
>>>
>>> And tried to boot in verbose mode with kernel debugger enabled by 
>>> adding -kdv to kernel parameters via GRUB.
>>> Then only seeing the boot (via x86 installation DVD) drops to kmdb.
>>>
>>> Is it expected?
>>> If not, how to find a way to collect info from screen ......?
>>>
>>> Thanks,
>>> Jingci
>>> _______________________________________________
>>> indiana-discuss mailing list
>>> indiana-discuss at opensolaris.org
>>> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
>>
>
>