(In reply to comment #9)
> (In reply to comment #8)
> > (In reply to comment #7)
> > > Is this problem still reproducible in breezy?
> >
> > Yes, this bug is still reproducible in Breezy Preview, even if I add 'nvidia' to
> > /etc/hotplug/blacklist.
>
> That isn't expected to have any effect; hotplug will not load that module
> regardless of whether it is listed in that file. It must be loaded explicitly
> via /etc/modules if you want to use it.
>
> > I have a question: Is there a way to install nVIDIA drivers via a LiveCD? I've a
> > Morphix LiveCD and it came with nVIDIA drivers. By the way, the Morphix LiveCD
> > is (!) 2 years old and it boots perfectly.
>
> You can install the nvidia-glx module using the Ubuntu live CD if you wish.
>
> So far, I see no indication whatsoever that your problem has anything to do with
> the nvidia driver. Boot the system in recovery mode, which should verbosely
> show which modules are being loaded and help narrow the possibilities.
I've run recovery mode a few times, but every time I'll get a different kind of
kernel panic with different kinds of "stacktraces". I've written 3 different
kind of panics. I don't know what it all means, but I hope that it can help you.
(In reply to comment #9) blacklist.
> (In reply to comment #8)
> > (In reply to comment #7)
> > > Is this problem still reproducible in breezy?
> >
> > Yes, this bug is still reproducible in Breezy Preview, even if I add 'nvidia' to
> > /etc/hotplug/
>
> That isn't expected to have any effect; hotplug will not load that module
> regardless of whether it is listed in that file. It must be loaded explicitly
> via /etc/modules if you want to use it.
>
> > I have a question: Is there a way to install nVIDIA drivers via a LiveCD? I've a
> > Morphix LiveCD and it came with nVIDIA drivers. By the way, the Morphix LiveCD
> > is (!) 2 years old and it boots perfectly.
>
> You can install the nvidia-glx module using the Ubuntu live CD if you wish.
>
> So far, I see no indication whatsoever that your problem has anything to do with
> the nvidia driver. Boot the system in recovery mode, which should verbosely
> show which modules are being loaded and help narrow the possibilities.
I've run recovery mode a few times, but every time I'll get a different kind of
kernel panic with different kinds of "stacktraces". I've written 3 different
kind of panics. I don't know what it all means, but I hope that it can help you.
Kernel Panic #1
---------------
apic_timer_ interrupt+ 0x1c/0x24 fault+0x0/ 0x484 to_irq+ 0x4f/0x58 fault+0x67/ 0x484 0x399/0x3a5 fault+0x0/ 0x484 0x4f/0x54
do_page_
add_pin_
do_page_
sys_select+
do_page_
error_code+
Kernel panic = not synching: Attempted to kill init!
---------------
Kernel Panic #2
---------------
__do_irq to_deliver wake_function
do_IRQ
common_interrupt
__mod_page_state
page_remove_rmap
zap_pte_range
unmap_page_range
unmap_vmas
exit_mmap
mmput
do_exit
sys_exit_group
get_signal_
do_signal
sys_select
sys_sysinfo
default_
do_page_fault
do_notify_resume
work_notifysig
Some hexidecimal code
<0>Kernel panic - not synching: Fatal exception in interrupt
---------------
Kernel panic #3
---------------
Modules linked in: intel_agp agpgart dm_mod evdev psmouse cdrom --- and lot of
other modules
CPU: 0
EIP: 0060:[<c010fa46>] Not tainted VLI
EFLAGS: 00010046 (2.6.12-8-386)
A stacktrace
A calltrace
apic_timer_ interrupt
Some hexidecimal code
Kernel panic - not synching: Attempted to kill init!
------- ------- ------- -
regards,
Alexander