WRT310N V1 - How to fix firmware after installing firmware v2 on v1 hardware. ** SOLVED **

Hello,
WARNING! THIS IS AN ADVANCED FIX FOR TECHNICAL TECHS WITH OUT OF WARENTEE ROUGHTERS. IF LINKSYS SUPPORT CAN HELP YOU, USE THERE SERVICES FIRST! THIS PROCEDURE MAY RESULT IF PURMADENT LOSS OF USE OF YOUR ROUGHER. THIS WORKED FOR ME, IT MAY NOT FOR YOU!
Situation:
Linksys WRT310n V1
Power LED on solid
LAN Ports LED on solid
Wireless LED off 
NO RESPONCE AT ALL!
PC hardware tested (only one is needed):
Vista laptop gigibit card.
Vista desktop gigibit card.
Software to download / install:
Installed vista TFTP client from control pannel
download TFTP from linksys
download firmware from linksys ( Proper firmware for v1 hardware!!!! )
Method and Procedure:
Plug in the power and the lan cable to the computer.
Open a dos prompt start pinging the roughter.
ping 192.168.1.1 -t -w 5
No responce is to be expected at this point.
On the computer open your network connections folder
Disable ALL OTHER network interfaces! (ALL OTHER)
open the settings of the lan interfacess.
disable (uncheck) all options other then tcp/ip v4
set the manual address of the card to
192.168.1.10 ip
255.255.255.0 sub
192.168.1.1 gate
192.168.1.1 dns
now in the network card properties above configure the network card for 10 half duplex speed mine was called line speed and duplex.
save and close.
NOTE: Do not release the reset button untill told to! You will need to hold it in for a long time!
NOTE: when holding the reset for 30 seconds, the LAN port may flash around 5 and 15 seconds, do not pull the power until the lan is off around 25 to 35 seconds of holding  
On the rougher, with the power on and the lan cable connected. 
Hold the reset button for 30 secconds you will see the lan cable port turn off arround this point pull the power.
Hold the reset and wait 10 seconds.
Hold the reset and power up for 30 seconds until the lan cable turns off around then  
Ok so with the power off you can release the reset button.
from now own you can start from here with the reset if first attempts of sending the new firmware to the linksys fails.
Open a NEW dos prompt.
type tftp -i 192.168.1.1 put C:\linksysfirmware.bin
if you hit enter it will fail ... so let it time out... if you did type it again and wait to hit enter.
while holding in the reset button power on the roughter release the reset after 5 secconds.
press enter on the dos prompt. you may send this a couple of time arround now it took three tryes to get the "SENT COMPLETE" message from tftp! you will also magicaly see your pings from the other window start working! if working WAIT 2 min before doing anything next.
If you fail for more then 1 min, unplug your roughter and start the send firmware part.
ok so it's pinging thats all? yes!
ok so you waited 2 min, now pull the power normaly and wait 10 secconds return the power with our the restart! start it normaly.
after 20 secconds the roughter should be able to ping ... nothing else yet!
use the Linksys TFTP program now ... and install the full firmware to the roughter!
when the message says firmware complete wait two min then pull the power and reboot.
DONE! 
Solved!
Go to Solution.

[email protected] wrote:
Hello,
WARNING! THIS IS AN ADVANCED FIX FOR TECHNICAL TECHS WITH OUT OF WARENTEE ROUGHTERS. IF LINKSYS SUPPORT CAN HELP YOU, USE THERE SERVICES FIRST! THIS PROCEDURE MAY RESULT IF PURMADENT LOSS OF USE OF YOUR ROUGHER. THIS WORKED FOR ME, IT MAY NOT FOR YOU!
Situation:
Linksys WRT310n V1
Power LED on solid
LAN Ports LED on solid
Wireless LED off 
NO RESPONCE AT ALL!
PC hardware tested (only one is needed):
Vista laptop gigibit card.
Vista desktop gigibit card.
Software to download / install:
Installed vista TFTP client from control pannel
download TFTP from linksys
download firmware from linksys ( Proper firmware for v1 hardware!!!! )
Method and Procedure:
Plug in the power and the lan cable to the computer.
Open a dos prompt start pinging the roughter.
ping 192.168.1.1 -t -w 5
No responce is to be expected at this point.
On the computer open your network connections folder
Disable ALL OTHER network interfaces! (ALL OTHER)
open the settings of the lan interfacess.
disable (uncheck) all options other then tcp/ip v4
set the manual address of the card to
192.168.1.10 ip
255.255.255.0 sub
192.168.1.1 gate
192.168.1.1 dns
now in the network card properties above configure the network card for 10 half duplex speed mine was called line speed and duplex.
save and close.
NOTE: Do not release the reset button untill told to! You will need to hold it in for a long time!
NOTE: when holding the reset for 30 seconds, the LAN port may flash around 5 and 15 seconds, do not pull the power until the lan is off around 25 to 35 seconds of holding  
On the rougher, with the power on and the lan cable connected. 
Hold the reset button for 30 secconds you will see the lan cable port turn off arround this point pull the power.
Hold the reset and wait 10 seconds.
Hold the reset and power up for 30 seconds until the lan cable turns off around then  
Ok so with the power off you can release the reset button.
from now own you can start from here with the reset if first attempts of sending the new firmware to the linksys fails.
Open a NEW dos prompt.
type tftp -i 192.168.1.1 put C:\linksysfirmware.bin
if you hit enter it will fail ... so let it time out... if you did type it again and wait to hit enter.
while holding in the reset button power on the roughter release the reset after 5 secconds.
press enter on the dos prompt. you may send this a couple of time arround now it took three tryes to get the "SENT COMPLETE" message from tftp! you will also magicaly see your pings from the other window start working! if working WAIT 2 min before doing anything next.
If you fail for more then 1 min, unplug your roughter and start the send firmware part.
ok so it's pinging thats all? yes!
ok so you waited 2 min, now pull the power normaly and wait 10 secconds return the power with our the restart! start it normaly.
after 20 secconds the roughter should be able to ping ... nothing else yet!
use the Linksys TFTP program now ... and install the full firmware to the roughter!
when the message says firmware complete wait two min then pull the power and reboot.
DONE! 
hi 
i tried ur all steps but couldn't success, and the different thing is my when I connect my wrt310n to computer I show the IP 169.254.*.* is there any different steps for it. plz help me.

Similar Messages

  • How to fix iPhoto after installing idvd

    how do I fix iPhoto after installing idvd?

    That's because you didin't do a custom install and installed only iDVD.
    OT

  • Any ideas on how to fix ipad after the new iOS 7 update? My battery will not charge, my ipad is hot to the touch, the iTunes Store won't open, and my messages on Facebook aren't showing up when I chat and pintrest won't pin to my boards.

    Any ideas on how to fix ipad after the new iOS 7 update? My battery will not charge, my ipad is hot to the touch, the iTunes Store won't open, and my messages on Facebook aren't showing up when I chat and pintrest won't pin to my boards.

    If you have all your music on the cmputer then i would connect up my phone uncheck the Sync Music option and apply.
    This should take all the music off your phone .Then you can resync the music back on to it.
    If this doesn't work maybe a restore to factory settings and start from scratch is the way to go

  • No connection after installing firmware 1.10.03 on brand new Zen Nano P

    Hi all,
    After I installed the new firmware, .0.03, my Zen Nano Plus is no longer recognised by my computer (it seems to work fine otherwise). What should I do?
    I have tried this on not just one, but three different computers, with no luck, even though all three computers recognise another Zen Nano Plus (my son's) which still runs on .03.02.
    I followed the instructions for installation of new firmware, so I have installed a "Player Recovery Device", but I don't know how to access/activate it in order to get back to the older version of the firmware. As far as I can tell, the relevant page on the discussion forum
    (http://forums.creative.com/creativelabs/board/message?board.id=dap&message.id=3)
    and the relevant page on the Creative Knowledge Base (SID4794) do not actually tell you how to ACCESS the recovery mode but only how to INSTALL it (whereas the info for other players, e.g. MuVo2, does tell you how to access recovery mode).
    I seem to be pretty much in the situation described by "takabanana" (post dated 0-04-2006),
    http://forums.creative.com/creativelabs/board/
    message?board.id=dap&message.id=9493&query.id=9573 9#M9493,
    but I do not understand how he fixed his problem (What do you mean by "until it caught"? What happens when it "catches"?).
    So I would be extremely happy about any advice you might have on
    - . how to get my Zen Nano Plus back to Firmware .03.02, and/or
    - 2. how to make my computer recognise my Zen Nano Plus with Firmware .0.03.
    yours, Sten

    Thanks to both responses so far.
    I did what PB suggested and everything is fine now (running .03.02 again).
    Apart from the obvious problems with .0.03 that almost everybody seems to be having, my particular problem was that I did not understand that the Zen Nano Plus is in Recovery Mode (and thus accessible to the loading of different firmware) AS SOON AS it turns up in the Device manager as "Player Recovery Device". I thought that something more had to happen.
    yours, Sten

  • How to fix Grub after moving arch to new drive [SOLVED]

    I moved my Arch install (/ and /home partitions) to a new drive and I was wondering how to fix Grub so that it knows /boot is on the new drive.  What I've done thus far is
    create partitions on the new drive and dd my current / and /home partitions to them.  The new partitions are bigger than the current ones, so I also re-sized the filesystems to fill the new partitions.  My disk/partition setup is the following
    /dev/sda1        2048 488392703 488390656 232.9G  7 HPFS/NTFS/exFAT   (Storage)
    /dev/sdb1  *         2048    206847    204800  100M  7 HPFS/NTFS/exFAT   (System reserved)
    /dev/sdb2          206848 102402047 102195200 48.7G  7 HPFS/NTFS/exFAT   (Windows 7)
    /dev/sdb3  *    102402048 141472127  39070080 18.6G 83 Linux   (Current Arch /)
    /dev/sdb4       141472128 250069679 108597552 51.8G 83 Linux   (Current Arch /home)
    /dev/sdc2  *       206848 105064447 104857600   50G 83 Linux   (New Arch /)
    /dev/sdc3       105064448 234441647 129377200 61.7G 83 Linux   (New Arch /home)
    After I resized the filesystems, I then created a new grub.cfg file (on /dev/sdb3) that is aware of the new Arch system.  I can boot to both my current and new Arch installs and run them fine, but ultimately I want to remove the current Arch install so I can make more room for my Windows 7 install.  What do I need to do to grub, so it knows to use the new Arch system.
    Last edited by tlawren (2014-08-17 21:42:46)

    @Xyne - Thanks!  Installing grub on my /dev/sdc did the trick.  Because I dd'ed my old setup to a new drive, /boot/grub was already populated, so all I had to do was install and configure grub on the new drive via the following. 
    grub-install --target=i386-pc --recheck --debug /dev/sdx
    grub-mkconfig -o /boot/grub/grub.cfg
    I used os-prober to find the other OS's (Windows 7 and my old Arch).  After some testing, I will wipe my old Arch setup and then resize Windows into the free space.

  • How setup LDAP Sync After Install in OIM 11g  ver, 11.1.1.5.0

    Hi guys, I'm trying to find how to setup LDAP Sync After Install in OIM 11g (ver, 11.1.1.5)....
    I found on Metalink an interesting article "*How to Setup LDAP Sync After Install in OIM 11g [ID 1272682.1]*", but inside there is a Note that says:
    Note: This article is applicable to OIM version 11.1.1.3 only. Steps for 11.1.1.5 are not the same, and product manual has documented steps to setup LDAP sync after install.
    So, that the steps for 11.1.1.5 are not the same, it's clear.....
    and I tried to look for these steps in the manual:
    Oracle® Fusion Middleware Quick Installation Guide for Oracle Identity Management
    11g Release 1 (11.1.1)
    Part Number E10033-06
    but I didn't still find nothing for the specific 11.1.1.5.0 version....only for the 11.1.1.3.0 version
    Can anyone help me to find where these steps are ? I need this information as soon as possible ti start the development
    Thanks in advance for the help
    Alex

    If you are creating Before and After Create Opeation script, you would be able to access all the variables in the process form. Now obvious question, what are the names of these variables? The answer is: the name of the variable is same as that mentioned in the "decode" column of the provisioning attribute map lookup or in other words, the variable name is same as the AD attribute name. In the example mentioned in the documentation, the variable "%givenName% was used in the script. On the similar lines you can use other variables like "sn", "samAccountName", etc.
    Hope the information helps.

  • Zen Nano Plus: How to resolve issues with installing firmware 1.14

    So .... I managed to kill my Zen Nano Plus when installing firmware version .4.03, but fortunately I've managed to bring it back to life again. :-)
    Here's what I did wrong, and how you can avoid the mistakes that I made ...
    I attempted to install the newly released "Creative ZEN Nano Plus Firmware .4.03" from my Windows 2000 system. However, I had not previously installed the "Creative Mass Storage Driver .07.00.250". In fact there seemed to be no reason to install these mass storage drivers as the Nano Plus player was always recognized by my system. However, while installing the firmware upgrade, it seems that the player is set to recovery mode and therefore the mass storage driver needs to be installed prior to upgrading the firmware.
    I realized this partway through the firmware upgrade when prompted for the "StMp3Rec.sys" driver. I then successfully installed the mass storage driver then attempted to continue with the firmware upgrade. Unfortunately, the firmware software "froze" and the process had to be killed. My Nano Plus player now wouldn't turn on and my system would not recognize it. I then read how to set the player in recovery mode, and was able to see the player listed as "STMP3500" when examining my attached USB hardware (using the "Unplug or Eject Hardware" dialog).
    To install the driver, I then looked at all hardware in my "Device Manager" (right click on "My Computer", select "Properties", choose the "Hardware" tab, click on the "Device Manager" button) then selected the "STMP3500" device. Right clicking and selecting "Properties" (or double clicking) brings up the properties dialog and from there I chose the "Reinstall Driver" button. I specified the driver location: "C:\Program Files\Creative\Creative Mass Storage Drivers\StMp3Rec.sys" and the driver then successfully installed. Finally, I successfully installed the firmware upgrade and all is now working well.
    Here's the bottom line:
    Be sure to install the "Creative Mass Storage Driver .07.00.250" prior to upgrading to the "Creative ZEN Nano Plus Firmware .4.03".
    Maybe it is because I beta tested six or seven different Rio MP3 player models (until D&M Holdings discontinued the Rio brand), or because I have worked as a software developer for eight years - but I tend not to install any software that does not appear to be required. The Creative firmware upgrade software could be greatly improved by including a simple check to see if the Creative mass storage drivers are installed before accessing the player.

    This has been answered many times here. Delete a few files on the player. Create a few folders on the player. Move the songs on the player into the folders. Now add more songs to the player into the folders. There is a limit on how many items the player will allow in the root.

  • Can not start x after installing nvidia 173.14.x drivers [SOLVED]

    After installing nvidia-beta (version 173.14.05-5) I am unable to start x. I receive the errors:
    (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device PCI:1:0:0.
    (EE) NVIDIA(0): Please see the COMMON PROBLEMS section in the README for
    (EE) NVIDIA(0): additional information.
    (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
    I have tried the installer directly from nVidia itself and I receive the same results. Any help is appreciated. Thanks.
    Last edited by vytalelementz (2008-08-26 16:11:11)

    nvidia-utils-beta was installed, also my GPU is listed as supported on nvidia's site.
    Here's the whole xorg log file just in case:
    This is a pre-release version of the X server from The X.Org Foundation.
    It is not supported in any way.
    Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
    Select the "xorg" product for bugs you find in this release.
    Before reporting bugs in pre-release versions please check the
    latest version in the X.Org Foundation git repository.
    See http://wiki.x.org/wiki/GitPage for git access instructions.
    X.Org X Server 1.4.0.90
    Release Date: 5 September 2007
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 2.6.25-ARCH i686
    Current Operating System: Linux ve1.vytalworld.org 2.6.25-ARCH #1 SMP PREEMPT Fri May 16 14:52:43 CEST 2008 i686
    Build Date: 22 May 2008 06:09:07PM
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Module Loader present
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jun 2 13:29:09 2008
    (==) Using config file: "/etc/X11/XF86Config"
    (==) ServerLayout "Layout0"
    (**) |-->Screen "Screen0" (0)
    (**) | |-->Monitor "Monitor0"
    (**) | |-->Device "Device0"
    (**) |-->Input Device "Keyboard0"
    (**) |-->Input Device "Mouse0"
    (==) Automatically adding devices
    (==) Automatically enabling devices
    (==) FontPath set to:
    /usr/share/fonts/misc,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/TTF,
    /usr/share/fonts/Type1
    (**) RgbPath set to "/usr/lib/X11/rgb"
    (==) ModulePath set to "/usr/lib/xorg/modules"
    (II) Open ACPI successful (/var/run/acpid.socket)
    (II) Loader magic: 0x81e0900
    (II) Module ABI versions:
    X.Org ANSI C Emulation: 0.3
    X.Org Video Driver: 2.0
    X.Org XInput driver : 2.0
    X.Org Server Extension : 0.3
    X.Org Font Renderer : 0.5
    (II) Loader running on linux
    (II) LoadModule: "pcidata"
    (II) Loading /usr/lib/xorg/modules//libpcidata.so
    (II) Module pcidata: vendor="X.Org Foundation"
    compiled for 1.4.0.90, module version = 1.0.0
    ABI class: X.Org Video Driver, version 2.0
    (--) using VT number 7
    (II) PCI: PCI scan (all values are in hex)
    (II) PCI: 00:00:0: chip 10de,005e card 147b,1c12 rev a3 class 05,80,00 hdr 00
    (II) PCI: 00:01:0: chip 10de,0050 card 147b,1c12 rev a3 class 06,01,00 hdr 80
    (II) PCI: 00:01:1: chip 10de,0052 card 147b,1c12 rev a2 class 0c,05,00 hdr 80
    (II) PCI: 00:02:0: chip 10de,005a card 147b,1c12 rev a2 class 0c,03,10 hdr 80
    (II) PCI: 00:02:1: chip 10de,005b card 147b,1c12 rev a3 class 0c,03,20 hdr 80
    (II) PCI: 00:04:0: chip 10de,0059 card 147b,1c12 rev a2 class 04,01,00 hdr 00
    (II) PCI: 00:06:0: chip 10de,0053 card f47b,1c12 rev a2 class 01,01,8a hdr 00
    (II) PCI: 00:07:0: chip 10de,0054 card 147b,1c12 rev a3 class 01,01,85 hdr 00
    (II) PCI: 00:08:0: chip 10de,0055 card 147b,1c12 rev a3 class 01,01,85 hdr 00
    (II) PCI: 00:09:0: chip 10de,005c card 0000,0000 rev a2 class 06,04,01 hdr 01
    (II) PCI: 00:0a:0: chip 10de,0057 card 147b,1c12 rev a3 class 06,80,00 hdr 00
    (II) PCI: 00:0b:0: chip 10de,005d card 0000,0000 rev a3 class 06,04,00 hdr 01
    (II) PCI: 00:0c:0: chip 10de,005d card 0000,0000 rev a3 class 06,04,00 hdr 01
    (II) PCI: 00:0d:0: chip 10de,005d card 0000,0000 rev a3 class 06,04,00 hdr 01
    (II) PCI: 00:0e:0: chip 10de,005d card 0000,0000 rev a3 class 06,04,00 hdr 01
    (II) PCI: 00:18:0: chip 1022,1100 card 0000,0000 rev 00 class 06,00,00 hdr 80
    (II) PCI: 00:18:1: chip 1022,1101 card 0000,0000 rev 00 class 06,00,00 hdr 80
    (II) PCI: 00:18:2: chip 1022,1102 card 0000,0000 rev 00 class 06,00,00 hdr 80
    (II) PCI: 00:18:3: chip 1022,1103 card 0000,0000 rev 00 class 06,00,00 hdr 80
    (II) PCI: 01:00:0: chip 10de,0291 card 3842,c564 rev a1 class 03,00,00 hdr 00
    (II) PCI: 05:07:0: chip 104c,8023 card 147b,1c12 rev 00 class 0c,00,10 hdr 00
    (II) PCI: End of PCI scan
    (II) PCI-to-ISA bridge:
    (II) Bus -1: bridge is at (0:1:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
    (II) Subtractive PCI-to-PCI bridge:
    (II) Bus 5: bridge is at (0:9:0), (0,5,5), BCTRL: 0x0204 (VGA_EN is cleared)
    (II) Bus 5 I/O range:
    [0] -1 0 0x00009000 - 0x000090ff (0x100) IX[b]
    [1] -1 0 0x00009400 - 0x000094ff (0x100) IX[b]
    [2] -1 0 0x00009800 - 0x000098ff (0x100) IX[b]
    [3] -1 0 0x00009c00 - 0x00009cff (0x100) IX[b]
    (II) Bus 5 non-prefetchable memory range:
    [0] -1 0 0xfea00000 - 0xfeafffff (0x100000) MX[b]
    (II) Bus 5 prefetchable memory range:
    [0] -1 0 0xfe900000 - 0xfe9fffff (0x100000) MX[b]
    (II) PCI-to-PCI bridge:
    (II) Bus 4: bridge is at (0:11:0), (0,4,4), BCTRL: 0x0004 (VGA_EN is cleared)
    (II) Bus 4 I/O range:
    [0] -1 0 0x00006000 - 0x000060ff (0x100) IX[b]
    [1] -1 0 0x00006400 - 0x000064ff (0x100) IX[b]
    [2] -1 0 0x00006800 - 0x000068ff (0x100) IX[b]
    [3] -1 0 0x00006c00 - 0x00006cff (0x100) IX[b]
    (II) Bus 4 non-prefetchable memory range:
    [0] -1 0 0xfe500000 - 0xfe5fffff (0x100000) MX[b]
    (II) Bus 4 prefetchable memory range:
    [0] -1 0 0xfe400000 - 0xfe4fffff (0x100000) MX[b]
    (II) PCI-to-PCI bridge:
    (II) Bus 3: bridge is at (0:12:0), (0,3,3), BCTRL: 0x0004 (VGA_EN is cleared)
    (II) Bus 3 I/O range:
    [0] -1 0 0x00007000 - 0x000070ff (0x100) IX[b]
    [1] -1 0 0x00007400 - 0x000074ff (0x100) IX[b]
    [2] -1 0 0x00007800 - 0x000078ff (0x100) IX[b]
    [3] -1 0 0x00007c00 - 0x00007cff (0x100) IX[b]
    (II) Bus 3 non-prefetchable memory range:
    [0] -1 0 0xfe700000 - 0xfe7fffff (0x100000) MX[b]
    (II) Bus 3 prefetchable memory range:
    [0] -1 0 0xfe600000 - 0xfe6fffff (0x100000) MX[b]
    (II) PCI-to-PCI bridge:
    (II) Bus 2: bridge is at (0:13:0), (0,2,2), BCTRL: 0x0004 (VGA_EN is cleared)
    (II) Bus 2 I/O range:
    [0] -1 0 0x00008000 - 0x000080ff (0x100) IX[b]
    [1] -1 0 0x00008400 - 0x000084ff (0x100) IX[b]
    [2] -1 0 0x00008800 - 0x000088ff (0x100) IX[b]
    [3] -1 0 0x00008c00 - 0x00008cff (0x100) IX[b]
    (II) Bus 2 non-prefetchable memory range:
    [0] -1 0 0xfe300000 - 0xfe3fffff (0x100000) MX[b]
    (II) Bus 2 prefetchable memory range:
    [0] -1 0 0xfe800000 - 0xfe8fffff (0x100000) MX[b]
    (II) PCI-to-PCI bridge:
    (II) Bus 1: bridge is at (0:14:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set)
    (II) Bus 1 I/O range:
    [0] -1 0 0x0000a000 - 0x0000a0ff (0x100) IX[b]
    [1] -1 0 0x0000a400 - 0x0000a4ff (0x100) IX[b]
    [2] -1 0 0x0000a800 - 0x0000a8ff (0x100) IX[b]
    [3] -1 0 0x0000ac00 - 0x0000acff (0x100) IX[b]
    (II) Bus 1 non-prefetchable memory range:
    [0] -1 0 0xfc000000 - 0xfdffffff (0x2000000) MX[b]
    (II) Bus 1 prefetchable memory range:
    [0] -1 0 0xb0000000 - 0xcfffffff (0x20000000) MX[b]
    (II) Host-to-PCI bridge:
    (II) Bus 0: bridge is at (0:24:0), (0,0,5), BCTRL: 0x0008 (VGA_EN is set)
    (II) Bus 0 I/O range:
    [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
    (II) Bus 0 non-prefetchable memory range:
    [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
    (II) Bus 0 prefetchable memory range:
    [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
    (--) PCI:*(1:0:0) nVidia Corporation G71 [GeForce 7900 GT/GTO] rev 161, Mem @ 0xfc000000/24, 0xb0000000/28, 0xfd000000/24, I/O @ 0xac00/7
    (II) Addressable bus resource ranges are
    [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
    [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
    (II) OS-reported resource ranges:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    (II) Active PCI resource ranges:
    [0] -1 0 0xfeaf8000 - 0xfeafbfff (0x4000) MX[b]
    [1] -1 0 0xfeaff000 - 0xfeaff7ff (0x800) MX[b]
    [2] -1 0 0xfebff000 - 0xfebfffff (0x1000) MX[b]
    [3] -1 0 0xfebfe000 - 0xfebfefff (0x1000) MX[b]
    [4] -1 0 0xfebfd000 - 0xfebfdfff (0x1000) MX[b]
    [5] -1 0 0xfebfc000 - 0xfebfcfff (0x1000) MX[b]
    [6] -1 0 0xfebf9000 - 0xfebf90ff (0x100) MX[b]
    [7] -1 0 0xfebfa000 - 0xfebfafff (0x1000) MX[b]
    [8] -1 0 0xfd000000 - 0xfdffffff (0x1000000) MX[b](B)
    [9] -1 0 0xb0000000 - 0xbfffffff (0x10000000) MX[b](B)
    [10] -1 0 0xfc000000 - 0xfcffffff (0x1000000) MX[b](B)
    [11] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
    [12] -1 0 0x0000e800 - 0x0000e80f (0x10) IX[b]
    [13] -1 0 0x00000b60 - 0x00000b63 (0x4) IX[b]
    [14] -1 0 0x00000960 - 0x00000967 (0x8) IX[b]
    [15] -1 0 0x00000be0 - 0x00000be3 (0x4) IX[b]
    [16] -1 0 0x000009e0 - 0x000009e7 (0x8) IX[b]
    [17] -1 0 0x0000d400 - 0x0000d40f (0x10) IX[b]
    [18] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[b]
    [19] -1 0 0x00000970 - 0x00000977 (0x8) IX[b]
    [20] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[b]
    [21] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[b]
    [22] -1 0 0x0000d000 - 0x0000d00f (0x10) IX[b]
    [23] -1 0 0x0000c800 - 0x0000c8ff (0x100) IX[b]
    [24] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[b]
    [25] -1 0 0x00001c40 - 0x00001c7f (0x40) IX[b]
    [26] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[b]
    [27] -1 0 0x0000bc00 - 0x0000bc1f (0x20) IX[b]
    [28] -1 0 0x0000ac00 - 0x0000ac7f (0x80) IX[b](B)
    (II) Active PCI resource ranges after removing overlaps:
    [0] -1 0 0xfeaf8000 - 0xfeafbfff (0x4000) MX[b]
    [1] -1 0 0xfeaff000 - 0xfeaff7ff (0x800) MX[b]
    [2] -1 0 0xfebff000 - 0xfebfffff (0x1000) MX[b]
    [3] -1 0 0xfebfe000 - 0xfebfefff (0x1000) MX[b]
    [4] -1 0 0xfebfd000 - 0xfebfdfff (0x1000) MX[b]
    [5] -1 0 0xfebfc000 - 0xfebfcfff (0x1000) MX[b]
    [6] -1 0 0xfebf9000 - 0xfebf90ff (0x100) MX[b]
    [7] -1 0 0xfebfa000 - 0xfebfafff (0x1000) MX[b]
    [8] -1 0 0xfd000000 - 0xfdffffff (0x1000000) MX[b](B)
    [9] -1 0 0xb0000000 - 0xbfffffff (0x10000000) MX[b](B)
    [10] -1 0 0xfc000000 - 0xfcffffff (0x1000000) MX[b](B)
    [11] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
    [12] -1 0 0x0000e800 - 0x0000e80f (0x10) IX[b]
    [13] -1 0 0x00000b60 - 0x00000b63 (0x4) IX[b]
    [14] -1 0 0x00000960 - 0x00000967 (0x8) IX[b]
    [15] -1 0 0x00000be0 - 0x00000be3 (0x4) IX[b]
    [16] -1 0 0x000009e0 - 0x000009e7 (0x8) IX[b]
    [17] -1 0 0x0000d400 - 0x0000d40f (0x10) IX[b]
    [18] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[b]
    [19] -1 0 0x00000970 - 0x00000977 (0x8) IX[b]
    [20] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[b]
    [21] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[b]
    [22] -1 0 0x0000d000 - 0x0000d00f (0x10) IX[b]
    [23] -1 0 0x0000c800 - 0x0000c8ff (0x100) IX[b]
    [24] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[b]
    [25] -1 0 0x00001c40 - 0x00001c7f (0x40) IX[b]
    [26] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[b]
    [27] -1 0 0x0000bc00 - 0x0000bc1f (0x20) IX[b]
    [28] -1 0 0x0000ac00 - 0x0000ac7f (0x80) IX[b](B)
    (II) OS-reported resource ranges after removing overlaps with PCI:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    (II) All system resource ranges:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xfeaf8000 - 0xfeafbfff (0x4000) MX[b]
    [5] -1 0 0xfeaff000 - 0xfeaff7ff (0x800) MX[b]
    [6] -1 0 0xfebff000 - 0xfebfffff (0x1000) MX[b]
    [7] -1 0 0xfebfe000 - 0xfebfefff (0x1000) MX[b]
    [8] -1 0 0xfebfd000 - 0xfebfdfff (0x1000) MX[b]
    [9] -1 0 0xfebfc000 - 0xfebfcfff (0x1000) MX[b]
    [10] -1 0 0xfebf9000 - 0xfebf90ff (0x100) MX[b]
    [11] -1 0 0xfebfa000 - 0xfebfafff (0x1000) MX[b]
    [12] -1 0 0xfd000000 - 0xfdffffff (0x1000000) MX[b](B)
    [13] -1 0 0xb0000000 - 0xbfffffff (0x10000000) MX[b](B)
    [14] -1 0 0xfc000000 - 0xfcffffff (0x1000000) MX[b](B)
    [15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [16] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [17] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
    [18] -1 0 0x0000e800 - 0x0000e80f (0x10) IX[b]
    [19] -1 0 0x00000b60 - 0x00000b63 (0x4) IX[b]
    [20] -1 0 0x00000960 - 0x00000967 (0x8) IX[b]
    [21] -1 0 0x00000be0 - 0x00000be3 (0x4) IX[b]
    [22] -1 0 0x000009e0 - 0x000009e7 (0x8) IX[b]
    [23] -1 0 0x0000d400 - 0x0000d40f (0x10) IX[b]
    [24] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[b]
    [25] -1 0 0x00000970 - 0x00000977 (0x8) IX[b]
    [26] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[b]
    [27] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[b]
    [28] -1 0 0x0000d000 - 0x0000d00f (0x10) IX[b]
    [29] -1 0 0x0000c800 - 0x0000c8ff (0x100) IX[b]
    [30] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[b]
    [31] -1 0 0x00001c40 - 0x00001c7f (0x40) IX[b]
    [32] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[b]
    [33] -1 0 0x0000bc00 - 0x0000bc1f (0x20) IX[b]
    [34] -1 0 0x0000ac00 - 0x0000ac7f (0x80) IX[b](B)
    (II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
    (II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
    (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
    (II) "freetype" will be loaded. This was enabled by default and also specified in the config file.
    (II) "record" will be loaded by default.
    (II) "dri" will be loaded by default.
    (II) LoadModule: "dbe"
    (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
    (II) Module dbe: vendor="X.Org Foundation"
    compiled for 1.4.0.90, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension DOUBLE-BUFFER
    (II) LoadModule: "extmod"
    (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
    (II) Module extmod: vendor="X.Org Foundation"
    compiled for 1.4.0.90, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension SHAPE
    (II) Loading extension MIT-SUNDRY-NONSTANDARD
    (II) Loading extension BIG-REQUESTS
    (II) Loading extension SYNC
    (II) Loading extension MIT-SCREEN-SAVER
    (II) Loading extension XC-MISC
    (II) Loading extension XFree86-VidModeExtension
    (II) Loading extension XFree86-Misc
    (II) Loading extension XFree86-DGA
    (II) Loading extension DPMS
    (II) Loading extension TOG-CUP
    (II) Loading extension Extended-Visual-Information
    (II) Loading extension XVideo
    (II) Loading extension XVideo-MotionCompensation
    (II) Loading extension X-Resource
    (II) LoadModule: "freetype"
    (II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
    (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
    compiled for 1.4.0.90, module version = 2.1.0
    Module class: X.Org Font Renderer
    ABI class: X.Org Font Renderer, version 0.5
    (II) Loading font FreeType
    (II) LoadModule: "glx"
    (II) Loading /usr/lib/xorg/modules/extensions//libglx.so
    (II) Module glx: vendor="NVIDIA Corporation"
    compiled for 4.0.2, module version = 1.0.0
    Module class: X.Org Server Extension
    (II) NVIDIA GLX Module 173.14.05 Mon May 19 00:30:52 PDT 2008
    (II) Loading extension GLX
    (II) LoadModule: "record"
    (II) Loading /usr/lib/xorg/modules/extensions//librecord.so
    (II) Module record: vendor="X.Org Foundation"
    compiled for 1.4.0.90, module version = 1.13.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension RECORD
    (II) LoadModule: "dri"
    (II) Loading /usr/lib/xorg/modules/extensions//libdri.so
    (II) Module dri: vendor="X.Org Foundation"
    compiled for 1.4.0.90, module version = 1.0.0
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension XFree86-DRI
    (II) LoadModule: "nvidia"
    (II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
    (II) Module nvidia: vendor="NVIDIA Corporation"
    compiled for 4.0.2, module version = 1.0.0
    Module class: X.Org Video Driver
    (II) LoadModule: "kbd"
    (II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
    (II) Module kbd: vendor="X.Org Foundation"
    compiled for 1.4.0, module version = 1.2.2
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 2.0
    (II) LoadModule: "mouse"
    (II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
    (II) Module mouse: vendor="X.Org Foundation"
    compiled for 1.4.0, module version = 1.2.3
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 2.0
    (II) NVIDIA dlloader X Driver 173.14.05 Mon May 19 00:10:20 PDT 2008
    (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    (II) Primary Device is: PCI 01:00:0
    (--) Assigning device section with no busID to primary device
    (--) Chipset NVIDIA GPU found
    (II) Loading sub module "fb"
    (II) LoadModule: "fb"
    (II) Loading /usr/lib/xorg/modules//libfb.so
    (II) Module fb: vendor="X.Org Foundation"
    compiled for 1.4.0.90, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.3
    (II) Loading sub module "wfb"
    (II) LoadModule: "wfb"
    (II) Loading /usr/lib/xorg/modules//libwfb.so
    (II) Module wfb: vendor="NVIDIA Corporation"
    compiled for 7.1.99.2, module version = 1.0.0
    (II) Loading sub module "ramdac"
    (II) LoadModule: "ramdac"(II) Module "ramdac" already built-in
    (II) resource ranges after xf86ClaimFixedResources() call:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xfeaf8000 - 0xfeafbfff (0x4000) MX[b]
    [5] -1 0 0xfeaff000 - 0xfeaff7ff (0x800) MX[b]
    [6] -1 0 0xfebff000 - 0xfebfffff (0x1000) MX[b]
    [7] -1 0 0xfebfe000 - 0xfebfefff (0x1000) MX[b]
    [8] -1 0 0xfebfd000 - 0xfebfdfff (0x1000) MX[b]
    [9] -1 0 0xfebfc000 - 0xfebfcfff (0x1000) MX[b]
    [10] -1 0 0xfebf9000 - 0xfebf90ff (0x100) MX[b]
    [11] -1 0 0xfebfa000 - 0xfebfafff (0x1000) MX[b]
    [12] -1 0 0xfd000000 - 0xfdffffff (0x1000000) MX[b](B)
    [13] -1 0 0xb0000000 - 0xbfffffff (0x10000000) MX[b](B)
    [14] -1 0 0xfc000000 - 0xfcffffff (0x1000000) MX[b](B)
    [15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [16] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [17] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
    [18] -1 0 0x0000e800 - 0x0000e80f (0x10) IX[b]
    [19] -1 0 0x00000b60 - 0x00000b63 (0x4) IX[b]
    [20] -1 0 0x00000960 - 0x00000967 (0x8) IX[b]
    [21] -1 0 0x00000be0 - 0x00000be3 (0x4) IX[b]
    [22] -1 0 0x000009e0 - 0x000009e7 (0x8) IX[b]
    [23] -1 0 0x0000d400 - 0x0000d40f (0x10) IX[b]
    [24] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[b]
    [25] -1 0 0x00000970 - 0x00000977 (0x8) IX[b]
    [26] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[b]
    [27] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[b]
    [28] -1 0 0x0000d000 - 0x0000d00f (0x10) IX[b]
    [29] -1 0 0x0000c800 - 0x0000c8ff (0x100) IX[b]
    [30] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[b]
    [31] -1 0 0x00001c40 - 0x00001c7f (0x40) IX[b]
    [32] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[b]
    [33] -1 0 0x0000bc00 - 0x0000bc1f (0x20) IX[b]
    [34] -1 0 0x0000ac00 - 0x0000ac7f (0x80) IX[b](B)
    (II) resource ranges after probing:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xfeaf8000 - 0xfeafbfff (0x4000) MX[b]
    [5] -1 0 0xfeaff000 - 0xfeaff7ff (0x800) MX[b]
    [6] -1 0 0xfebff000 - 0xfebfffff (0x1000) MX[b]
    [7] -1 0 0xfebfe000 - 0xfebfefff (0x1000) MX[b]
    [8] -1 0 0xfebfd000 - 0xfebfdfff (0x1000) MX[b]
    [9] -1 0 0xfebfc000 - 0xfebfcfff (0x1000) MX[b]
    [10] -1 0 0xfebf9000 - 0xfebf90ff (0x100) MX[b]
    [11] -1 0 0xfebfa000 - 0xfebfafff (0x1000) MX[b]
    [12] -1 0 0xfd000000 - 0xfdffffff (0x1000000) MX[b](B)
    [13] -1 0 0xb0000000 - 0xbfffffff (0x10000000) MX[b](B)
    [14] -1 0 0xfc000000 - 0xfcffffff (0x1000000) MX[b](B)
    [15] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
    [16] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
    [17] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
    [18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [19] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [20] -1 0 0x0000fc00 - 0x0000fc07 (0x8) IX[b]
    [21] -1 0 0x0000e800 - 0x0000e80f (0x10) IX[b]
    [22] -1 0 0x00000b60 - 0x00000b63 (0x4) IX[b]
    [23] -1 0 0x00000960 - 0x00000967 (0x8) IX[b]
    [24] -1 0 0x00000be0 - 0x00000be3 (0x4) IX[b]
    [25] -1 0 0x000009e0 - 0x000009e7 (0x8) IX[b]
    [26] -1 0 0x0000d400 - 0x0000d40f (0x10) IX[b]
    [27] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[b]
    [28] -1 0 0x00000970 - 0x00000977 (0x8) IX[b]
    [29] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[b]
    [30] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[b]
    [31] -1 0 0x0000d000 - 0x0000d00f (0x10) IX[b]
    [32] -1 0 0x0000c800 - 0x0000c8ff (0x100) IX[b]
    [33] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[b]
    [34] -1 0 0x00001c40 - 0x00001c7f (0x40) IX[b]
    [35] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[b]
    [36] -1 0 0x0000bc00 - 0x0000bc1f (0x20) IX[b]
    [37] -1 0 0x0000ac00 - 0x0000ac7f (0x80) IX[b](B)
    [38] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
    [39] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
    (II) Setting vga for screen 0.
    (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
    (==) NVIDIA(0): RGB weight 888
    (==) NVIDIA(0): Default visual is TrueColor
    (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    (**) NVIDIA(0): Enabling RENDER acceleration
    (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
    (II) NVIDIA(0): enabled.
    (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device PCI:1:0:0.
    (EE) NVIDIA(0): Please see the COMMON PROBLEMS section in the README for
    (EE) NVIDIA(0): additional information.
    (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
    (II) UnloadModule: "nvidia"
    (II) UnloadModule: "wfb"
    (II) UnloadModule: "fb"
    (EE) Screen(s) found, but none have a usable configuration.
    Fatal server error:
    no screens found

  • [Solved]How to fix grub after Windows XP install?

    I installed Windows XP on top of Arch in a different partition.
    It looks something like this:
    /dev/sda1 - XP
    /dev/sda2 - Arch
    /dev/sda3 - Swap
    Grub is located on /dev/sda2/ in /boot/grub/
    Windows XP obviously overwritten the mbr like it normally does.
    I tried loading the arch live install cd, and trying grub-install /dev/sda and /dev/sda1 and /dev/sda2 but it doesn't do anything.
    I want to overwrite Windows XP's boot loader with grub and add XP as an option to boot. Can someone please give me noob friendly instructions on how to accomplish this with minimal effort? It's important I don't damage the XP or Arch partitions. Thanks for any help.
    Last edited by PrimoTurbo (2008-07-30 18:06:43)

    I fixed it! Nearly the same instructions as lucke gave but I just used the Arch Live cd. All I did was boot Arch Live cd, it presented me with grub and bunch of options. (I didn't even boot into the cd) just pressed C so it loaded the grub terminal.
    Then:
    find /boot/grub/stage1
    Which outputs:
    root (hdX,Y)
    (In my case it was hd0,1)
    Then:
    root (hdX,Y)
    [Don't forget there is space after root and (hdX,Y)]
    Finally:
    setup hd0

  • At a total loss on how to fix PSCS6 after CSCC Install

    I am assuming that the CC version of Photoshop had something to do with this as it started just after the install and they are both doing this.
    The very next image I edited after the install was gif_01.gif.  I saved it to: project/005885/site/image/gif_01.gif.
    Soon I started working on another graphic and went to save it, say....  desktop\graphic.jpg
    The warning box pops up, Warning, saving this image will overwrite the image gif_01.gif do you want to continue.
    Now, everytime I save a jpeg it has this message.  No other images do it, except of course gif_01.gif if in that folder.
    Not a huge deal except for it is having a bit of a water board effect and is starting to feel like someone died every time it pops. 
    Shift+Ctrl+Alt+DBLClick = Reseting up my whole work environment and still having the gif issue.  Oh ya, another issue with it is every time I save a jpeg to any file it also save that gif image to the file.  It is an 1800x2400 pixel image so it will really suck to have a few thousand extra on the drives.
    Any clues would be great.  I hate to uninstall and reinstall as I am software heavy on this machine and it is used for many tasks.  Sometime reinstalling a single program turns into setting the machine back up and it is a 3 day process.
    Windows 8 Enterprise
    CS6 - All Apps +(
    MS Visual Studio Ultimate
    Netbeans
    Eclipse
    MS Office Professional 2013 +Skype +Sharepoint Builder +Forms Tools
    Core FTP
    PUTTY (3 app pack)
    Windows Defender
    Spybot (dormat-manual scans and immunizations)
    Windows Firewall
    Everything file searcing app
    Skype
    Custom Apps (In House, Air Apps)
    All of the internet browsers (at least the most popular dozen or so)
    Mobile simulator, graphics pad software, video capture etc.  Several more apps but none that should effect this)
    AMD 8 Core
    2xGTX 570 (Quadro 6K soon)
    64gb Ram
    SSD eSata III 512gb x 4 in Raid 10
    1200watt PSU
    Also, I have cleared as many of the temp files and etc.  I use 2 256gb SSD eSata II disks for scratch and temp files for CS6 with a 300GB HDD for video
    Every program system wide and all drivers are 100% up to date with the latest versions.
    Also, I just realized it only does it when Save for the WEB is chosen and not when Save As and then JPEG is picked.

    I would hazard a guess you copied your plugins from cs6 to the cc installation which is not recommended!
    Don't think the advice to reformat and reinstall is the best way and don't know why it was suggested!

  • Can't find Range Extender after installing firmware upgrade to fix the 802.11n bug

    I got my RE1000 shortly after Christmas but had trouble after a while where devices would claim they were connected to my wifi network but not really have a connection.
    I discovered by doing a network scan that my router was broacasting/accepting B/G/N... all of my devices support N, so they were connecting on N... but the RE1000 wasn't broadcasting/accepting N... only G.
    Since the RE was on G, this caused major issues trying to connect.
    So in late Jan / early Feb I updated the firmware on the device as per instructions from the Cisco rep... but didn't have a chance to plug it back in and test until now.
    Now when I plug it in, it lights up all solid green... but in the setup (Windows 7 / PC) the setup can't find the device.  My laptop and the RE are within 25 feet of the router... and the laptop and RE are about 6-10 feet apart (I tested different distances to ensure it wasn't too close)
    So now I'm stuck... I can't even verify if the RE1000 is properly updated.
    What can I do or do I need to return this unit?

    scunliffe,
    What is the model number of your router? Is it a Linksys device too? You can configure the RE1000 manually, you will have to connect your laptop straight to the RE1000 via ethernet cable and access its setup page by typing 192.168.1.1 on your browser.
    Check this link: http://kb.linksys.com/Linksys/ukp.aspx?vw=1&docid=76055e8973f5487f82d2d3f610da4c02_Accessing_the_web...
    Title: Accessing the web-based setup page of the Linksys range extender
    Article ID: 24379
    Scenario 1 is applicable for you: Using a wired computer.
    You may need to disable the WiFi capability on your laptop while doing this to make sure that it is not connected wirelessly to any network. You may need to have both the RE1000 and the laptop at least 6-10 feet away from your router.
    I would say you are fmiliar with the wireless settings on your router, right? You will need those information to configure the RE1000 (SSID, Channel Width, Security Mode, and Passphrase).
    For the steps, check this link: http://kb.linksys.com/Linksys/ukp.aspx?vw=1&docid=bc79b0ee350f404d82f231d729bc9530_Manually_Configur...
    Title: Manually configuring the wireless security settings of the Linksys RE1000
    Article ID: 24344

  • How to fix problem with installed and working add-ons disappearing after update to 20.0.1?

    I updated to version 20.0.1 of Firefox the other day. I had the theme Qute 3++ 1.19 installed and it took 3 restarts of the browser before it kicked in and worked again, for some reason.
    Then I noticed that my MillBar Community toolbar 3.18.0.7 had disappeared, which I use for the feature of collecting my email accounts to get fast notifications about new emails. Also my Adblock Plus 2.2.3 seems to not be working because all of a sudden I see ads everywhere and I also discovered a bunch of pop-ups from nowhere. I used these add-ons for such a long time that I was shocked.
    When i went to type a message to a friend, I also noticed that my american-english dictionary/spellchecker was not working.
    The first thing I checked was that none of these add-ons was inactivated or said to need updates. The dictionary had disappeared, so i re-installed that. I also reinstalled Adblock Plus. Still it doesn't work.
    When i entered the email information into the toolbar options, it collects my emails for a while, but suddenly it stops and the information is not there anymore. If I restart the browser it also disappears.
    Same thing with the dictionary. it works for a while, and then suddenly it's like it's disabled.
    And the add-ons are still in what seems like working conditions in my lists. No errors that I can see, no updates available.
    I'm really at a loss as to what to do, I've never had problems like this before that couldn't be solved with an update of the add-on. So I'd be very grateful for help with this and hope that I have provided enough information.

    this help is not useful.
    Since the new firefox version 20.0.1, '''no more of my add-ons work''' (except firebug ). They are installed '''but not visible '''(no toolbar, no menus) !!! same for the new add - ons that I installed. I tried everything: to reinstall add-on, to reinstall firefox.
    this new version of firefox is really horrible, '''thank you for making a corrective because I cannot work any more with'''

  • I know how to fix the iTunes 7 / firmware ver. 1.2 freeze problem

    Many of you (like me) are having major headaches because of the new updates that Apple has been releasing (i.e. iTunes 7). So far I only know that this affects the Video iPod, but this could very well fix other models too.
    Here are some symptoms of what the following will fix, and what you most likely have already done to try and fix it.
    - iPod keeps freezing after a few seconds ever since you updated to iTunes 7 and/or iPod software ver. 1.2.
    - iPod will remain in Do Not Disconnect mode even after ejecting or disconnecting
    - A forced reset does not fix it, as it repeats the above.
    - Restoring the iPod through iTunes does not help
    So, here's what to do.
    The old iPod updater software is how you will fix all of this. Unfortunately, because iTunes 7 thinks that it's better and more up to date, it will prevent you from opening the old version of the software if you still have it on your machine.
    So first of all, uninstall iTunes 7.0. (You do not have to remove your library information, just the software.) Restart the computer.
    If you still have the old iPod updater, try it and see if it runs. If it does, read on. If not, skip to the next paragraph. So, if it does run, simply hit Restore and you can go back to a previous version of the firmware. I believe that Apple discontinued the firmware page since releasing iTunes 7. Look around some search engines like Google if you really want the latest firmware.
    Take out the installation CD that came with your iPod. Run it and it should install the old iPod updater along with iTunes 6.x. iTunes 6.x cannot run since iTunes 7 changed your libary's formatting, but that will not be a problem. Run the Restore process in the old updater and it should be alright for you to start loading your stuff on again without problems.
    Since iTunes 7 reformatted your libary listing, iTunes 6 will no longer work. However, you can still use it by reinstalling iTunes 7. Just make sure you do the following.
    TO KEEP THE SAME THING FROM HAPPENING AGAIN
    iTunes 7 is actually alright. It's the updater part of it that will screw up your iPod.
    - iTunes 7 will tell you that a new iPod software version is available when you open it.
    - Check the "Never Ask Again" box and click Don't Install.
    - When you sync your iPod to your computer, NEVER touch the Version section when you're changing your iPod's settings. Everything else is alright to work with.
    - Everything will work fine as long as you never update the iPod's software via iTunes, at least until the programmers can fix this issue in a later release or patch.
    I hope this helps out a lot of you. Pretty lame of Apple to miss something this big during debugging.
    Custom Windows XP

    Listen to this person, he knows exactly what he's talking about. My unit had the freezing problem, the visual artifact problem, and eventually would only show a blank white screen after I had tinkered too long. Luckily I have another computer that I hadn't yet upgraded to itunes 7 and it had the last firmware upgrade before the itunes 7 one. From disk mode I was able to restore it to the previous firmware version, and now the ipod works perfectly.
    I too am almost disqusted with Apple for 1) missing this problem and 2) not letting people know!
    I wonder how many more people are going to have lots of problems so apple can protect their PR.
    Anyways, what would be really helpful would be if someone could upgrade the latest firmware installer before itunes 7 (it's an individual ipod updating program, not itunes 6.xx)somewhere on the internet so users could download it and do away with this evil 1.2 firmware.

  • How to fix InDesign CS5 install/program-opening problems the "right" way?

    After my second install of CS5 Design Premium, I was still having all sorts of problems with opening programs. InDesign was especially troublesome and I posted my woes at the bottom of this thread: http://forums.adobe.com/thread/661059?tstart=0
    John Hawkinson (presumably an Adobe employee) kindly replied suggested I start a new thread so he could help me debug properly. So while the iron is hot...I'm ready...let's debug. Can it be done in an hour?
    Other comments from John H.:
    "You should realize that removing the welcome screen plugin is not  supported and can come back to bite you later on. It would be better to  fix it properly. Probably by reinstalling InDesign."

    After about a minute though, the program opened, welcome screen and all...
    Oh dear. Well, then I guess it's not stuck.
    So, we know it's not specific to your customizations from CS3 or otherwise, since it doens't affect your new user. So it's either something about InDesign's installation on your machine, or something about your machine in general.
    I forgot to ask: Do you have any font management software installed? Have you tried disabling it? That has been the source of a variety of problems... One of the things InDesign does at startup is enumerate all the fonts on your system. Do you have a really large number?
    How about any plugins for InDesign or other software that modifies its behavior?
    I am mostly out of ideas. Your Sample Process output is not very informative to me. It looks like it is in the midst of calls to the operating system (all the CF* stuff is Apple's CoreFoundation code), rather than inside InDesign's code itself. Which could implicate...the operating system's font subsystem, graphics subsystem, or, well, almost anything.
    I'm afraid I'm almost out of ideas. It would seem pointless to suggest you replace your preferences, since you started out with a clean user account.
    You can certainly de-install CS5 and run the CS5 Cleaner Tool and then reinstall. No promises that it would work, though, it might just be a waste of your time
    If you're feeling really exciting, the only other thing (other than the above) that I would try would be to go the Activity Monitor, and choose View > Send Signal to Process and choose Abort (SIGABRT). That will force InDesign to crash. The crash report may be a bit more insightful than the call graph from the Sample Process. Though it'll be frozen at an instant in time, so it might not reflect what's going on during the bulk of the rainbow-wheeling. Anyhow, the relevant section is the "Thread 0 Crashed: " portion and the lines that follow until Thread 1.
    I suppose it might be possible to instrument the CoreFoundation calls with dtrace. That's definitely not something I've done and it's probably easier to take out the WelcomeScreen plugin and soldier on. Hopefully something along the way will help before you get that far.
    And of course, you can open an official support case with Adobe...

  • How to move files after installing new hard drive

    I am considering the installation of a new 80 or 100 GB hard drive. I purchased the new iLife 06 program but I do not have enough space to install on my present 60 GB unit. I only have 3 GB available. I've read all the posts involving the possible brands, downloaded the instructions how to swap out the units. My question is how to backup and install my files and applications so I may reinstall onto the new drive. Can I just copy my hard drive volume onto my external Lacie storage unit and then drag the volume back to the new hard drive after booting off my OS disk? Any advice on how to move my apps and files? Do I need to purchase cloning software?

    The easiest way is buy an external firewire enclosure and put your new drive in it. Then format your new drive. then use Carbon Copy Cloner to copy your internal drive onto your new drive. Then install your new drive and put your old one in the enclosure. You are now in business with an external backup on your old drive.

Maybe you are looking for