• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 220
  • Last Modified:

Oddities during Linux Install

I am trying to install RHL6.1 on a laptop that is built by my company and having limited success. The software is downloaded and burned from red hat - not bought. The machine has a 2 GB HDD and 32 MB of RAM with a 200Mhz Pentium. I am attempting a normal install.

The first odd thing is that when I am configuring the video the software can auto detect my video card and I then have to manually choose LCD 800X600.  After a long install I reboot and get nothing but random colors on the screen.  I have tried several different combnations of screens but to no avail.

The second odd error I get is after I see those many odd colors I reboot and see that the machine is scrolling boot text.  After it tries to detect new harware, it scrolls seemingly random hex numbers all over the screen. Here is one example of the text: [<c2890c40>].  After about five minutes of this, the numbers stop and the system is frozen.

I put all of these oddidties in the same question because I believe they are related.  If y'all think that they are separate issues, let me know and I will split them up.  Thank you.
0
Schandor
Asked:
Schandor
  • 6
  • 6
1 Solution
 
mmipsCommented:
Have you verified that your video hardware is actually supported? there are many different types of laptop video hardware that are not supported...
0
 
SchandorAuthor Commented:
I have chosen several different types of display (it auto detects my video chipset) and all of them worked when I told it to test the config.  The latest one I am choosing is LCD 800X600 since that is what we choose in Windows (95,98,NT).
0
 
mmipsCommented:
Check the chipset type in the supported hardware db at redhat...There are types of chipsets that are detected that really are 3rd party clones that are not specifically supported...
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
SchandorAuthor Commented:
The S3 Aurora64V+ (my chipset) is on the list.
0
 
SchandorAuthor Commented:
The S3 Aurora64V+ (my chipset) is on the list.
0
 
mmipsCommented:
Have you tried to bring it up with the standard VGA Xserver?
0
 
mmipsCommented:
You micht also try the following ...

If LCD is active the CRT will always output 1024x768 (or whatever is the _physical_ LCD size) and smaller modes are zoomed to fit on the LCD unless you specify Option "lcd_center" in the device section.

The pixel clock for this physical size (e.g. 1024x768) mode...

....can explicitly set in the config file (device section) with e.g. `Set_LCDClk 70' (resulting 70 MHz pixel clock being used for all modes when LCD is on)
....is taken from the _first_ mode in the modes line iff this mode's display size is the same as the physical LCD size
....the default LCD pixel clock of BIOS initialisation setup is used. This value is output at server startup in the line `LCD size ...' unless you're specifying a value using `Set_LCDClk ...'

If LCD is _not_ active, the normal mode lines and pixel clocks are used for the VGA output.

Whenever you switch output sources with Fn-F5, the Xserver won't get informed and pixel clock and other settings are wrong. Because of this you have to switch modes _after_ switch output sources! Then the server will check which outputs are active and select the correct clocks etc. So the recommended key sequence to switch output is

Fn-F5 Ctrl-Alt-Plus Ctrl-Alt-Minus

and everything should be ok..

on the Toshiba keypad you can first hold down Ctrl-Alt, then press `Fn' additionally before pressing Plus/Minus too to avoid to explicitly enable/disable the numeric keypad for mode switching.

0
 
SchandorAuthor Commented:
Here is some more stuff that I have found.  If, instead of doing a reboot after the install, I cut the power and do a cold boot, I do not get the funky colors.  However, I do still run into the hex codes.

Also, on my latest attempt I went in and set my partitions manually, I also created a boot disk.  When I boot to this disk and tell it to go into "rescue" mode, I get the following error on the last two lines before it freezes.

Warning: unable to open an initial console.
Kernal panic: No init found.  Try passing init=option to kernal.

This may not be a video problem after all.  Thoughts?
0
 
SchandorAuthor Commented:
More news from the front.  I went throught the services one by one and the codes popped up when I asked it to start the "apmd" service.  Any more thoughts?
0
 
mmipsCommented:
That is the power management daemon...Try configuring for no power management...
0
 
psimationCommented:
mmips is definately right, the scrolling hex numbers are your apmd service, ie. power management, my notebook did the same.use the interactive startup, DON't load the apmd service, once booted through to the prompt, run setup and remove the apmd service from the list of start-up services. regarding your monitor, I also had a bit of trouble getting mine to function . try the IBM tft panels, and lastly, switch between crt/lcd when you get the garbled display. works for me...
0
 
mmipsCommented:
Have you solved your boot problem yet???
0
 
SchandorAuthor Commented:
I did not have time to try today, but I will tomorrow.  Thanx.
0

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

  • 6
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now