g0kth

Hi Danleff The router does indeed have 4 ethernet ports and a USB port. My motherboard is an ASRock 939 Dual SATA 2 with built in LAN (which according to the manual is a 802.3u 10/100 Ethernet. Onlooking at the properties of the LAN through the Win XP Control Panel it says that it is a ULi PCI Fast Ethernet Controller). I am using a DSL provider and as I said in my initial post it all works under Windows XP 64. When I set the router up I had to go to a configuration page to enter my user ID and password. If you need anymore info let me know.

I'm running a dual boot machine (FC4 64 and Win XP 64 Pro) and when I'm using FC4 I can't connect to either the Internet or see the other PC on my home network. When I'm using Win XP everything works fine. The PC is connected to an Edimax AR-6024 Router and I suspect that this is where my problem lies. I think the problem is in the lack of a suitable Linux driver for this router. I have been trying to find a Linux driver for this Router but drawn a blank so far. Is there anyone out there using this Router or can give me any pointers as to whether this is the root of my problem. I have also tried using Knoppix, booted from a CD, and that can't find the network / internet either. Any help would be appreciated.

Danleff, You're right too many different things going on now on this topic. Okay we have finally had success and I can now boot up from the PATA drive with FC4 installed, choose either FC4 or Win XP from the grub menu and run the chosen OS. So thanks for your help. Just for completeness and future info I have answered your questions below: You wrote: What happens when you change the Windows entry to; title Windows XP map (hd0) (hd1) map (hd1) (hd0) rootnoverify (hd0,0) chainloader +1 OUTCOME: I get the following dislayed on the screen: Booting 'Win XP64' map (hd0) (hd1) map (hd1) (hd0) rootnoverify (hd0,0) chainloader +1 GRUB _ (where _ is a flashing cursor). You wrote: or; title Windows XP map (hd0) (hd1) map (hd1) (hd0) rootnoverify (hd1,0) chainloader +1 OUTCOME: This will successfully launch the chosen OS from the grub menu. You wrote: If it still fails, you need to alter your boot,ini file for Windows.......... what is the boot.ini designation for Windows? multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP... Specifically, what is the rdisk value? THE RDISK VALUE IS rdisk(0), the rest of the values are as listed in your question. Hope that helps. Thanks again for your help and from my point of view this topic has now been resolved and can be closed.

Hi Danleff Ok just to recap on my system I have three hard drives: 160GB SATA holds the Windows XP 64 OS 80GB PATA holds the Fedora Core 4 OS 3GB PATA holds all my data files - docs, pics etc Under Windows XP these drives are identified as: 160GB - C, E & F 80GB - H 3GB - G Floppy - A CD/DVD - D Under FC4 these drives are identified as: 160GB - sda (sda1, sda5, sda6) or hd2 80GB - hda or hd0 3GB - hdb or hd1 Floppy - fd0 The BIOS boot sequence is: 1st Boot Device - FLOPY DRIVE 2nd Boot Device - CD/DVD 3rd Boot Device - PATA 80GB (FC4) The Hard Disk boot sequence is : 1 PATA 80GB (FC4) 2 SATA 160GB (Win XP) 3 PATA 3GB (Data) Note to use Win XP at the moment I have to go into BIOS and swap 1 & 2 of the Hard disk boot sequence around but ultimately the boot sequence above is what I want with the start up menu allowing me to default to FC4 with the option to select Win XP. In FC4 starting with the 'Computer' folder I select the following folders to get to grub.conf / menu.lst and the device.map: Filesystem boot grub The grub.conf file contains the following: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/hda1 default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu password --md5 ********************** title Fedora Core (2.6.11-1.1369_FC4) root (hd0,0) kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.11-1.1369_FC4.img title Win XP64 rootnoverify (hd1,0) chainloader +1 The device.map file contains the following: # this device map was generated by anaconda (fd0) /dev/fd0 (hd0) /dev/hda (hd1) /dev/sda When I boot up the PC and select FC4 from the menu it loads FC4 ok, if I select Win XP it just hangs. So that's the current situation. hope that makes things clearer. If you need any other info let me know. Cheers Dave

Danleff Not had much time this year so far to try and resolve my dual boot problems. You sent the following message on this thread: 2006-01-04 10:59:12 g0kth, I just switched my system over to sata only. If you are still having the problem, I may be able to resolve it, as I have my drives set up close to yours. Following this message I gave you an update on what I had tried, still to no avail. Can you give me details of your SATA setup to see if this will help solve my problems. Cheers Dave.

Hi Danleff First of all a belated happy new year and secondly apologies for the delay in resonding to your question. My setup is still the same with Win XP on the SATA drive and FC4 on the PATA drive. Since my last post the only thing I have tried is following Chapter 4 'Boot Methods' in Linux in a Nutshell. Here under the section on 'Dual-booting Linux and Windows NT/2000/XP' I have copied 'bootsect.lnx' from my Linux PATA drive across to the C drive on the Win XP SATA drive and modified the boot.ini file for Win XP to have a menu item for Linux. Now with the SATA drive as the boot drive I get the menu and on selecting Win XP it boots ok but if I select Linux it just hangs, so in effect it is the reverse of when the PATA drive is the boot drive in which case I can run Linux but not Win XP. So to run the required operating system I currently have to select the appropriate drive in the BIOS. Not ideal but at least I can select one or the other. So if you have a solution I can try fire away and I'll give it a go.

I used Nero to burn my CD's, if you use this make sure to select 'Disk Image' and not 'Data CD'. Once you have burnt your discs, put disk 1 into your pc and when you start the installation process you will have an option to check your cd's before you start instalation.

No worries about the delay in replying, I been finding my way around FC4 and finding a few more problems !! Nothing to worry about for now though. Ok, I have tried the changes that you suggested and now when the pc starts up I get the menu screen, so I select Window XP, the screen goes blank momentarily before returning to the menu screen, which if I'm not quick enough (timeout currently =5) then boots up into FC4. If I select Windows again it just goes back to the menu and so on. So at least I'm not now hanging up at the Booting 'Windows XP' rootnoverify (hd2,0) chainloader +1 screen!! Anyway hope you have a good Xmas and may all you linux problems in 2006 be easy ones

Hi again danleff, Ok here's where I'm now at: I have changed the bios so that the boot sequence is now: Floppy drive DVD/Cd drive 80GB PATA drive (Linux) The hard drive sequence in the bios is now: 80GB PATA (shown as hd0 in grub-install --recheck) 160GB SATA (shown as hd2 in grub-install --recheck) 3GB PATA (shown as hd1 in grub-install --recheck) The grub.conf file was change to: # grub.conf generated by anaconda # #Note that you do not have to rerun grub after making changes to this file #NOTICE: You have a /boot partion. This means that # all kernel and initrd paths are relative to /boot/, eg # root (hd1,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/sda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu password --md5 .................... (random letters/numbers here) title Fedora Core (2.6.11-1.1369_FC4) root (hd0,0) kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.11-1.1369_FC4.img title Window XP rootnoverify (hd2,0) chainloader +1 This hopefully sorted out the difference I mentioned in my last post. I then rebooted the pc and now I get the menu screen If I select Fedora Core it all boots up ok and I arrive at the user log in screen. If however I select Windows XP I get: Booting 'Windows XP' rootnoverify (hd2,0) chainloader +1 and it just hangs there From reading one of the other posts I amended the grub.conf file to read: title Window XP rootnoverify (hd2,0) map (hd2)(hd0) map (hd0)(hd2) makeactive chainloader +1 Then when I select Windows XP from the menu I get: Booting 'Windows XP' rootnoverify (hd2,0) makeactive chainloader +1 and it just hangs there. From reading another post I amended the grub.conf file to read: title Window XP rootnoverify (hd2,0) map (hd2)(hd0) map (hd0)(hd2) makeactive chainloader (hd2)+1 Then when I select Windows XP from the menu I get: Booting 'Windows XP' rootnoverify (hd2,0) makeactive chainloader (hd2)+1 Missing operating system and it just hangs there. If I amended the grub.conf file to read: title Window XP rootnoverify (hd2,0) map (hd2)(hd0) map (hd0)(hd2) makeactive chainloader (hd0)+1 Then when I select Windows XP from the menu I get: Booting 'Windows XP' rootnoverify (hd2,0) makeactive chainloader (hd2)+1 GRUB _ and it just hangs there. So at least I can now get into FC. I just need to get into XP now so any thoughts would be appreciated. As an aside what is the difference between grub.conf and menu.lst? From what I have seen so far they both contain the same info. Thanks for your help so far. Dave

Hi danleff, Thanks for the reply. First of all the bios is set to boot in the following order: Floppy Drive DVD/CD Drive SATA Drive Under Hard Drives within the bios the order is: SATA Drive 80GB PATA Drive 3GB PATA Drive This is the first time I have used a SATA drive and did not realise that this would not be the MBR. The 80GB PATA drive (Linux) was partitioned during the install process, although I did setup some of those partitions during the installation based on a Fedora book I had been reading prior to installation, I don't recall setting up the /boot partition. Going through 'linux rescue' I have had a look in the /boot partition and grub.conf is there along with other files. Because I was blinkered by thinking that the MBR was on the SATA drive I never even thought about switching the drive sequence in the bios to boot the linux HD first. I will try this later today and let you know what happens. Presumably I would still need to amend the grub.conf file to show that for example the splashimage is actually on hd0 (the 80GB HD) and not hd1 (the 3GB HD) as is currently shown or is the drive numbering in grub.conf different to that given under grub-install --recheck? Cheers Dave

Hi, I'm a Linux newbie and having looked through the various threads relating to my problem I still don't have a solution so would appreciate some pointers. First of all my setup is an Asrock 939 Dual Sata2 mobo, with AMD Athlon 64 3200 cpu, 1GB of RAM, 160GB SATA HD, 80GB PATA HD and 3GB PATA HD, Asus DVD/CD R/W and of course a floppy drive. The 160GB HD has Windows XP Pro 64-bit installed and the drive is split into 3 partions, 100GB for windows os and windows programmes, 40GB & 20GB for user files. The 3GB HD is also used for user files with the intention of these being accessible to windows and linux. The 80GB HD has Fedora Core 4 (64-bit version) installed. The windows installation was done first and was working ok. I then installed FC4. During the installation process it said that it was going to load GRUB in the MBR on /dev/sda which is the 160GB SATA drive. The installation process identified that 'sda' was the 160GB SATA drive which it split into sda1 and sda2 (which appeared to be further split into sda5 and sda6 which matched the 40GB/20Gb split), 'hda' was the 80GB HD and 'hdb' was the 3GB HD. During installation the 80GB HD (hda) was split in to: 1 /boot ext3 102MB 2 VolGroup00 LVM PV 78058MB The VolGroup00 was then split in to: LogVol00 / ext3 78016MB LogVol01 swap 1984MB LogVol02 /home ext3 17152MB LogVol03 /tmp ext3 1056MB LogVol04 /usr ext3 17152MB After installation and on reboot the pc restarted and went straight into windows. Then I looked on the web for pointers on what might be the problem. Restarting the pc with the 1st FC4 disk and selecting linux rescue I tried 'grub-install --recheck /dev/sda' with the following result: (fd0) /dev/fd0 (hd0) /dev/hda 80GB HD (hd1) /dev/hdb 3GB HD (hd2) /dev/sda 160GB HD SATA I then rebooted the pc and this time got a blank screen with GRUB_ in the top left hand corner. I then went back into linux rescue and tried 'grub-install /dev/sda' and 'grub-install /dev/hda' but got the same results. So I can't even get into windows at the moment. I then took a look at the grub.conf file and got the following: # grub.conf generated by anaconda # #Note that you do not have to rerun grub after making changes to this file #NOTICE: You have a /boot partion. This means that # all kernel and initrd paths are relative to /boot/, eg # root (hd1,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/sda default=0 timeout=5 splashimage=(hd1,0)/grub/splash.xpm.gz hiddenmenu password --md5 .................... (random letters/numbers here) title Fedora Core (2.6.11-1.1369_FC4) root (hd1,0) kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=/dev/VolGroup00/LogVol00 rhgb quiet initrd /initrd-2.6.11-1.1369_FC4.img title Window XP rootnoverify (hd0,0) chainloader +1 The first thing that I notice is that the hd references in the grub.conf do not match with the hd references from the grub-install --recheck operation e.g in grub.conf it refers to Fedora Core root hd1 and Windows XP hd0 where as Fedora Core is actually on hd0 and Windows XP is actually on hd2 in the --recheck list. Apologies for the long listing but hopefully there is enough info to allow you to point me in the right direction rather than you having to ask more questions first. Thanks for your help. Dave.