ubuntu 7.10 won't boot

[Christopher Aitken]

Lennart Sorensen wrote:
> On Wed, Jan 23, 2008 at 04:01:36PM -0500, chris-n/jUll39koHNgV/OU4+dkA at public.gmane.org wrote:
>   
>> I can't boot my ubuntu 7.10 system. 
>>
>> I'm getting this: 
>>
>> Starting up...
>> Loading, please wait...
>> usplash: Setting mode 1280X1024 failed
>> usplash: Setting mode 1152X864 failed
>> usplash: Setting mode 1024X768 failed
>> usplash: Using mode 800X600
>> kinit: name_to_dev_t (/dev/md1) + md1(9,7)
>> kinit: trying to resume from /dev/md1
>> kinit: No resume image, doing normal boot... 
>>
>> Ubuntu 7.10 cpc tty1 
>>
>> I don't know if my (brand-new) hard drive is crashing or what. I went into 
>> the BIOS to see if there was any IRQ conflict with my emu1212m pci card (I 
>> haven't been able to initialize it under alsa) - I made a change and 
>> rebooted and got the above. So, I went innto the BIOS and restored default 
>> settings. I'm still getting the above error. At the prompt I logged in as 
>> root and tried to run init 5 - that did nothing - same for init 3. init 1 
>> got me to another screen but I don't know what to do in init 1 anyway. 
>>
>> Any ideas? I'm emailing this through webmail on another machine. i guess 
>> you can tell from the above that I have set up RAID not that I would know 
>> how to restore from RAID but I thought the point of RAID is that if a hard 
>> drive goes the other will take over. 
>>     
>
> Did you change the controller settings in the BIOS?  That could make
> Linux unable to see your HD which would make booting fail.
>   
Well, I was in the PCI Devices section. There seems to be, like, six 
things on IRQs 5, 10, and 11.
> Maybe you should try loading the default settings in the BIOS and see if
> that solves anything.
>   
I did that (see above) - it didn't help.
> And your emu1212m problems are not IRQ related, they are caused by the
>   
I don't know if you saw the other thread but after my crazy boot (drops 
down to command-line and I have to log in user then run 'startx' and I 
don't have Shut Down privilege) I tried alsamixer and this time it sees 
the emu1212m card! Either my flailing in the BIOS, or my removal then 
re-installation of all things alsa (since the correct repo is now in 
apt/sources.list) corerct6ed the problem.
> driver for some unknown reason not being able to find the firmware file
> that is clearly on the disk (so it must be looking somewhere else).
>
> I suppose it is possible whatever hte problem is was fixed in alsa
> 1.0.15, but I am not sure.  Didn't you have all this working under
> fedora before?  If you did what version of alsa was that?
>   
I don't remember. Alsa sees the emu1212m fine now.

Chris
> --
> Len Sorensen
> --
> The Toronto Linux Users Group.      Meetings: http://gtalug.org/
> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
> How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
>
>
>   

--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists