Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 49382 - 2004.1 smp and smp-nofb locks up
Summary: 2004.1 smp and smp-nofb locks up
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Release Media
Classification: Unclassified
Component: Everything (show other bugs)
Hardware: x86 Linux
: High blocker
Assignee: Gentoo LiveCD Package Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-29 08:05 UTC by Lloyd H. Meinholz
Modified: 2004-11-15 08:52 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lloyd H. Meinholz 2004-04-29 08:05:46 UTC
When I boot smp and smp-nofb, the screen locks up (after a couple of verticle color bars are displayed) and I have to do a hard reboot. I did not have this problem with 2004.0. I have an HP ProLiant ML350 using the cciss driver for my raid controller card and the broadcom tigon3 nic.

Additionally, I have to modprobe cciss and tigon3 from the gentoo-nofb kernel. I didn't have to do this with 2004.0

Reproducible: Always
Steps to Reproduce:
1. turn the computer on with 2004.1 in the cdrom
2. select smp or smp-nofb kernel
3.

Actual Results:  
screen locks up, have to hard reboot. sometimes verticle color bars on the left
side of the screen.

Expected Results:  
kernel loads, installation process begins...
Comment 1 Grahame Cooper 2004-04-30 02:18:23 UTC
I am having the same problem. I am a new user of Gentoo (this morning) but experienced with Linux.
The gentoo kernel seems to be fine, but the smp and smp-nofb kernels get as far as:
Loading smp .............................................
Loading smp.igz .......................
Then the screen goes blank and the system seems to be doing nothing. (I haven't seen any vertical colour bars though.)
I am trying to install on a new Viglen LX260 server with an Intel SE7501BR2 motherboard and dual Xeon 2.4GHz processors.
Comment 2 Quentin Hartman 2004-04-30 12:15:27 UTC
*me too* Installing on a Supermicro P4DP6 board, running a single Xeon. The machine doesn't actually freeze, as entering commands blindly gets a response. For instance after setting up my NIC (*cough* bug 49230 ;) *cough*), setting a password,  and starting sshd, I can ssh to the machine. It seems to be limited to being a video problem...
Comment 3 roger55 (RETIRED) gentoo-dev 2004-05-02 10:56:28 UTC
same here.

I don't know what is causing this, but I suspect the livecds kernel config. especially frambuffer drivers.

vesafb should work for everyone.
Comment 4 Kevin 2004-05-12 09:50:34 UTC
I think I know what's causing it.  I was actually stubborn enough
to (with a blank screen thus no visual feedback) start the network with a
static IP address, start up sshd, and ssh into the box which is how I
discovered at least some of the problems (perhaps not all).  I mentioned this
on the gentoo-user list on May 1 with the minimal liveCD, and now I'm trying
again with the universal liveCD and I have the same results.

Bottom line, one cannot use the SMP kernel on the 2004.1 liveCDs.

Some probable reasons:
(1) the kernel is v2.6 and the only modules available on the iso image are for the 2.4.(25?) kernel.
(2) it's impossible to use the SMP kernel at all from the console because it seems to lack framebuffer support and plain old VGA console support.  As soon as the kernel is read, my screen blanks out and doesn't come back.
(3) maybe others?
Comment 5 l0rd4gu1 2004-05-12 21:45:48 UTC
same here!! and i buy the CD! :(
with smp/2004.0 i have no problem, but smp/2004.1 blanks the screen, i tried many options (-nofb, nodetect, nohotplug, etc) but the result is always the same.

My HW is a Dell 8200
Comment 6 Chris Gianelloni (RETIRED) gentoo-dev 2004-05-18 13:23:48 UTC
I am working to ensure that the next release works out-of-the-box with SMP machines.  I have several myself and have started the livecd herd to take the lead in ensuring QA on the livecds.
Comment 7 Chris Gianelloni (RETIRED) gentoo-dev 2004-10-12 19:50:21 UTC
Did 2004.2 fix this for everyone?
Comment 8 Chris Gianelloni (RETIRED) gentoo-dev 2004-11-15 08:52:19 UTC
Well, I got no response.  That and we've had 2 releases since the original bug was posted.