Partha's Home

Fedora Core 5 (Bordeaux) on a dv8000

First Boot

Once the computer rebooted, we went through the first boot procedure. It did not give stall or hiccup. Of course, during the install process, it had detected the wired Ethernet connection and so it could not find the wired connection as my computer was not connected to the router with a wire. Any way, it continued after complaining that it could not find the cable. It also complained that

Kernel: PCI: Cannot allocate resource region 7 of bridge 0000:00:04.0
kernel: PCI: Cannot allocate resource region 8 of bridge 0000:00:04.0
kernel: powernow-k8: ph2 null fid transition 0xc

Once, it finished booting, I was presented with a glorious 800x600 screen on my 1680x1050 widescreen monitor! Well, that was OK as I would fix that during the selection of the monitor. It correctly recognized my video card!! This was definitely an improvement over the Fedora Core 5 Test 3 where it did not for a long time use the radeon driver for my video card. It said my card was

01:05.0 VGA compatible controller: ATI Technologies Inc ATI Radeon XPRESS 200M 5955 (PCIE)

which it is. So, then I changed the monitor section from a generic unknown CRT to generic unknown LCD with a screen size of 1680x1050. Next it wanted me to configure the firewall which I did and then it asked me if I wanted to setup rules for SeLinux. I opted to disable SeLinux whereupon I got an ominous message

Disabling SeLinux requires relabeling the whole system which can take a long time - will require a reboot. Do I want to Continue

I said, "Sure". Then it correctly discovered my sound card which is

00:14.5 Multimedia audio controller: ATI Technologies Inc IXP SB400 AC'97 Audio Controller (rev 02)

Next, it set up the username and then it rebooted the system.

Once we rebooted, I had my full widescreen back! This was wonderful. The beginning of Test 3 required me to juggle this stuff manually. I am liking FC5 already!! :) . There were some Kudzu errors that went by too quickly for me to capture. In any case, it did not seem to be a cause for concern. Next, I had to get my wireless up and running before I could do anything serious with the laptop. I had of course saved my firmware in my download directory. So, I copied that over to

/lib/firmware

since my wireless (as I have described elsewhere) is

06:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)

...Wireless| ...Home