Kevin Steffer Outloud – web, business and opinions

In my problems with installing Fedora Core 4 on my laptop because of a kernel panic and installation boot-up I researched http://www.fedoraforum.org/ and the suggestions to me was reporting a bug.I then went to the bugzilla and wanted to create a bug when I found one exactly explaining my problem about the kernel panic screen right after trying to boot the installation.
I registrered at bugzilla and commented on the bug and almost instantly I got a mail from a debugger at bugzilla telling me it's a dublicate of other bug which I obviously couldn't find by searching. He gave me the link to the bug and I read it imediately.

I came to the where someone writes:

Works !This is the WEIRDEST thing I've ever seen ina Linux install !

Still, explonation appreciate here for me too

Well this is weird because he's referring to a guy that try to boot the installation with a wrong kernel (say: somewrongkernel ) and then it reported

Could not find kernel image: somewrongkernel

And then he just pressed again to boot the default kernel (eg. linux). AND IT WORKED for me also!!!
I tried to boot my Fedora Core 4 DVD and at the first initial boot options I wrote the following:

boot: kevin
Could not find kernel image: kevin
boot:
Loading ..... etc.

And now I actually write this on my Fedora Core 4 installation - Happy me.

If you've got a Intel 915GM Chipset and can't boot the Fedora Core 4 installation - try the above and you can see more information here.

In my problems with installing Fedora Core 4 on my laptop because of a kernel panic and installation boot-up I decided to install Fedora Core 3. Here you can read about how I configured the nasty hardware pieces, my Audio device and my Intel Pro/Wireless 2200BG WiFi device.My hardware:
Model: ASUS M6V
Processor: 2.0GHz Intel Centrino
GFX: ATI Mobility Radeon x600 128MB (64 shared)
NIC 1: Marvell Yukon Gigabit Ethernet 10/100/1000Base-T
Wifi NIC: Intel Pro/Wireless 2200BG
DVD-RW: MATSHITAU J-831B
Firewire: Ricoh R5C552 IEEE 1394 Controller
Audio: Intel Corp. 82801FB/FBM/FR/FRW (ICH6 Family) High Definition Audio Controller
RAM: 1024MB
HD: 60GB
Monitor: 1680x1050 WSXGA+ 15,4'' Widescreen

The installation of Fedora Core 3 went smooth and here comes my explanation on where to go and what to get and how to install the Audio driver, WiFi driver. Simply these 'cause FC3 detected everything else automatically.

I got my Audio driver here from Realtek - Go visit
I got my WiFi driver here - Go visit (I downloaded driver 1.0.0 which is stable and used firmware 2.2)

The audio driver comes with a complete install script and driver for ALSA so I just executed the install script and then restarted my PC and woula kudzu found a new Audio device. I configured it with kudzu and everything worked properly.

The WiFi driver was a bit more tricky.
First i installed some wireless tool (get it here) and then I checked my kernel for supporting some crypto stuff so that the driver kan connect using a WEP key.
FC3 did have support for the correct crypto modules. By following the install instructions given by ipw2200.sf.net you can see which modules the kernel must support.
After installing the driver after the instructions I started up my system-config-network tool in X and there was a Wireless connection I configured my wireless settings in the wireless tab as:
Mode: Managed
Specified: <My network name>
Key: <secret>

I save the configuration and tried to Activate it, but determing IP failed.
The wireless tools installed erlier now had to tell what I did wrong. And all of the sudden by running the iwconfig tool I saw that eth1 was set to connect to my neighbours network so I typed "man iwconfig" and found out how I manually could set eth1 to use my own Access Point.
So I made a small bash script:
iwconfig eth1 essid <my network name (SSID)>
iwconfig eth1 channel 6
iwconfig eth1 mode Managed
iwconfig eth1 key s:<secret>

I ran the script and typed iwconfig again and yuhoo now I could see that eth1 was set to my own network.
I launched system-config-network again and typed Activate and now it got an IP perfectly!

Now everything is up and running thanks to http://ipw2200.sf.net for great work!