[SOLVED] kernel panic!

!!! · 09-29-2017, 03:20 PM

I added to #42: post Mint inxi, cuz: From DDG'ing: dell "t3600" install boot panic
even Win7/MacOS seems to have problems with that hardware!!!

Quote:

Only ports 0 and 1 on the motherboard actually recognize connected devices.

Maybe kernel.s can't find dvd drive... @#48: Sorry: pressing my mute button now.

brianL · 09-29-2017, 03:22 PM

Quote:

Originally Posted by Alien Bob

Just for science's sake can you try booting with nouveau blacklisted? So that we can strike one possibility off the list.

Wouldn't lilo have to be installed to do that?

Alien Bob · 09-29-2017, 03:23 PM

Quote:

Originally Posted by !!!

I added: post Mint inxi, cuz: From DDG'ing: dell "t3600" install boot panic
even Win7 seems to have problems with that hardware!!!

PLEASE.
Write your posts in intelligible english. And stay on-topic.

Alien Bob · 09-29-2017, 03:25 PM

Quote:

Originally Posted by brianL

Wouldn't lilo have to be installed to do that?

Bootloaders have an edit mode where you can alter the boot commandline. For (e)lilo that is the <TA> key, for Grub it is the "e" key. Execution of the modified commandline starts by hitting <ENTER> in (e)lilo and by hitting function key <F10> in Grub.

brianL · 09-29-2017, 03:28 PM

Yeah, but they have to be installed, and I can't get anywhere near the install lilo stage.

Alien Bob · 09-29-2017, 04:03 PM

Quote:

Originally Posted by brianL

Yeah, but they have to be installed, and I can't get anywhere near the install lilo stage.

Even the installer has a bootloader that allows the kernel commandline to be edited. It's staring you right in the face on the welcome screen:

Code:

Welcome to Slackware64 version 14.2 (Linux kernel 4.9.50)!

If you need to pass extra parameters to the kernel, enter them at the prompt
below after the name of the kernel to boot (huge.s etc).

brianL · 09-29-2017, 04:05 PM

Yeah, I tried those that !!! suggested.

brianL · 09-29-2017, 04:11 PM

OK, I'll try one more time. What do I enter to stop nouveau loading?

brianL · 09-29-2017, 04:31 PM

Just glanced at the BootPrompt-HOWTO, it says:

Quote:

IMPORTANT NOTE: Driver related boot prompt arguments only apply to
hardware drivers that are compiled directly into the kernel. They have
no effect on drivers that are loaded as modules.

!!! · 09-29-2017, 04:33 PM

See module_blacklist=... which is alphabetically listed here: https://www.kernel.org/doc/Documenta...parameters.txt

Code:

module_blacklist=nouveau

Or did you say ?it? (which distro?) "is running NVidia now", in #44?
(that's why I was saying that Mint's full inxi might be interesting to postbin)

brianL · 09-29-2017, 04:40 PM

Those are mentioned in BootPrompt-HOWTO. But I'm not going to try all of them.

colorpurple21859 · 09-29-2017, 10:06 PM

The ones I would try to blacklist besides nouveau are the network driver e1oooe and/or the firewire driver firewire_ohci

brianL · 09-30-2017, 05:38 AM

Quote:

Originally Posted by colorpurple21859

The ones I would try to blacklist besides nouveau are the network driver e1oooe and/or the firewire driver firewire_ohci

See post #54.
Anyway, I've got Slackware64 14.2 running in VBox, so that will have to suffice, until I'm in the mood to do more research and experimenting. Thanks, everybody, I will get it sorted out...sometime.

colorpurple21859 · 09-30-2017, 07:39 AM

Quote:

See post #54.

On this lapttop the network card was causing problems when I first installed LiveSlack similar to yours and blacklisting it with modprobe.blacklist=r8169 got the lapttop booting.

brianL · 09-30-2017, 08:16 AM

Yeah, but that was probably after you successfully installed & rebooted into it. 14.0 & Live apparently install, but on post install reboot, freeze at various points. (I don't know how many more times I'm going to have to mention that). That module & the e1oooe module are not built into the kernel - read the quote again from post #54. Thanks.