| View previous topic :: View next topic |
| Author |
Message |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54824
Location: 56N 3W
|
 Posted: Sun Sep 30, 2012 6:54 pm Post subject: |
 |
|
todd93,
AHCI mode is often faster as IDE mode can leave out DMA support.
| todd93 wrote: | | ... now I realize I'm up against a new problem. |
Well, thats one way to look at it.
Its really another learning opportunity, as you learn very little when everything JustWorks.
Start a new thread for your new 'learning opportunity'.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
 |
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Sun Sep 30, 2012 7:51 pm Post subject: |
|
|
oldconfiging may have lost the graphics config
ensure the boot partition is mounted
| Code: | emerge linux-firmware
cd /usr/src/linux;make menuconfig |
edit menuconfig to include:
| Quote: | Device Drivers --->
-*- Userspace firmware loading support
[*] Include in-kernel firmware blobs in kernel binary
(radeon/R600_rlc.bin radeon/R700_rlc.bin) External firmware blobs
(/lib/firmware) Firmware blobs root directory
Graphics support --->
<*> /dev/agpgart (AGP Support) --->
--- /dev/agpgart (AGP Support)
<*> AMD Opteron/Athlon64 on-CPU GART support
< > Intel 440LX/BX/GX, I8xx and E7x05 chipset support
< > SiS chipset support
< > VIA chipset support
-*- VGA Arbitration
(2) Maximum number of GPUs
[ ] Laptop Hybrid Graphics - GPU switching support
<*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) --->
--- Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
[ ] Allow to specify an EDID data set instead of probing for it
< > 3dfx Banshee/Voodoo3+
< > ATI Rage 128
<*> ATI Radeon
[*] Enable modesetting on radeon by default - NEW DRIVER
< > Nouveau (nVidia) cards
I2C encoder or helper chips --->
< > Matrox g200/g400
< > SiS video cards
< > Via unichrome video cards
< > Savage video cards
< > DRM driver for VMware Virtual GPU
< > Intel GMA5/600 KMS Framebuffer
< > DisplayLink
< > Intel GMA500 Stub Driver
<*> Lowlevel video output switch controls
-*- Support for frame buffer devices --->
--- Support for frame buffer devices
[*] Enable firmware EDID
[ ] Framebuffer foreign endianness support --->
[*] Enable Video Mode Handling Helpers
[*] Enable Tile Blitting Support
*** Frame buffer hardware drivers ***
< > Cirrus Logic support
< > Permedia2 support
< > CyberPro 2000/2010/5000 support
< > Arc Monochrome LCD board support
[ ] Asiliant (Chips) 69000 display support
[ ] IMS Twin Turbo display support
< > VGA 16-color graphics support
< > Userspace VESA VGA graphics support
[ ] VESA VGA graphics support
[ ] EFI-based Framebuffer Support
< > N411 Apollo/Hecuba devkit support
< > Hercules mono graphics support
< > Epson S1D13XXX framebuffer support
< > nVidia Framebuffer Support
< > nVidia Riva support
< > Intel740 support (EXPERIMENTAL)
< > Intel LE80578 (Vermilion) support
< > Matrox acceleration
< > ATI Radeon display support
< > ATI Rage128 display support
< > ATI Mach64 display support
< > S3 Trio/Virge support
< > S3 Savage support
< > SiS/XGI display support
< > VIA UniChrome (Pro) and Chrome9 display support
< > NeoMagic display support
< > IMG Kyro support
< > 3Dfx Banshee/Voodoo3/Voodoo5 display support
< > 3Dfx Voodoo Graphics (sst1) support
< > VIA VT8623 support
< > Trident/CyberXXX/CyberBlade support
< > ARK 2000PV support
< > Permedia3 support (EXPERIMENTAL)
< > Fujitsu carmine frame buffer support
[ ] AMD Geode family framebuffer support (EXPERIMENTAL)
< > SMSC UFX6000/7000 USB Framebuffer support
< > Displaylink USB Framebuffer support
< > Virtual Frame Buffer support (ONLY FOR TESTING!)
< > E-Ink Metronome/8track controller support
< > Fujitsu MB862xx GDC support
< > E-Ink Broadsheet/Epson S1D13521 controller support
[ ] Exynos Video driver support --->
[*] Backlight & LCD device support --->
--- Backlight & LCD device support
<*> Lowlevel LCD controls
< > Platform LCD controls
-*- Lowlevel Backlight controls
< > Generic (aka Sharp Corgi) Backlight Driver
< > Frontpath ProGear Backlight Driver
< > Apple Backlight Driver
< > Tabletkiosk Sahara Touch-iT Backlight Driver
< > Backlight Driver for ADP8860/ADP8861/ADP8863 using WLED
< > Backlight Driver for ADP8870 using WLED
< > Backlight driver for TI LP855X
Console display driver support --->
-*- VGA text console
[*] Enable Scrollback Buffer in System RAM
(256) Scrollback Buffer Size (in KB)
-*- Framebuffer Console support
-*- Map the console to the primary display device
[ ] Framebuffer Console Rotation
[ ] Select compiled-in fonts
[*] Bootup logo --->
--- Bootup logo
[ ] Standard black and white Linux logo
[ ] Standard 16-color Linux logo
[*] Standard 224-color Linux logo |
| Code: | make && make modules_install && make install
reboot |
emerging firmware may provide eth1
lvm is not in my wheelhouse
_________________
Defund the FCC. |
|
| Back to top |
|
|
todd93
l33t
Joined: 30 Oct 2006
Posts: 625
Location: Missouri
|
| Posted: Sun Sep 30, 2012 8:52 pm Post subject: |
|
|
Okay, now I am starting to understand this, however, with emerge linux-firmware, I get the following failure:
| Code: |
# emerge linux-firmware
Calculating dependencies... done!
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) sys-kernel/linux-firmware-20120719
!!! Directory does not exist: '/usr/lib64/ccache/bin'
!!! Disabled FEATURES='ccache'
>>> Downloading 'http://distfiles.gentoo.org/distfiles/linux-firmware-20120719.tar.xz'
--2012-09-30 15:39:28-- http://distfiles.gentoo.org/distfiles/linux-firmware-20120719.tar.xz
Resolving distfiles.gentoo.org... 216.165.129.135, 156.56.247.195, 140.211.166.134, ...
Connecting to distfiles.gentoo.org|216.165.129.135|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 15653904 (15M) [application/x-tar]
Saving to: `/usr/portage/distfiles/linux-firmware-20120719.tar.xz'
100%[======================================>] 15,653,904 358K/s in 45s
2012-09-30 15:40:13 (339 KB/s) - `/usr/portage/distfiles/linux-firmware-20120719.tar.xz' saved [15653904/15653904]
* linux-firmware-20120719.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking linux-firmware-20120719.tar.xz to /var/tmp/portage/sys-kernel/linux-firmware-20120719/work
>>> Source unpacked in /var/tmp/portage/sys-kernel/linux-firmware-20120719/work
>>> Preparing source in /var/tmp/portage/sys-kernel/linux-firmware-20120719/work/linux-firmware-20120719 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/sys-kernel/linux-firmware-20120719/work/linux-firmware-20120719 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/sys-kernel/linux-firmware-20120719/work/linux-firmware-20120719 ...
make -j2
make: Nothing to be done for `all'.
>>> Source compiled.
>>> Test phase [not enabled]: sys-kernel/linux-firmware-20120719
>>> Install linux-firmware-20120719 into /var/tmp/portage/sys-kernel/linux-firmware-20120719/image/ category sys-kernel
* Your configuration for sys-kernel/linux-firmware-20120719 has been saved in
* /etc/portage/savedconfig/sys-kernel/linux-firmware-20120719 for your editing pleasure.
* You can edit these files by hand and remerge this package with
* USE=savedconfig to customise the configuration.
* You can rename this file/directory to one of the following for
* its configuration to apply to multiple versions:
* ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/
* [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}]
>>> Completed installing linux-firmware-20120719 into /var/tmp/portage/sys-kernel/linux-firmware-20120719/image/
>>> Installing (1 of 1) sys-kernel/linux-firmware-20120719
* This package will overwrite one or more files that may belong to other
* packages (see list below). You can use a command such as `portageq
* owners / <filename>` to identify the installed package that owns a
* file. If portageq reports that only one package owns a file then do
* NOT file a bug report. A bug report is only useful if it identifies at
* least two or more packages that are known to install the same file(s).
* If a collision occurs and you can not explain where the file came from
* then you should simply ignore the collision since there is not enough
* information to determine if a real problem exists. Please do NOT file
* a bug report at http://bugs.gentoo.org unless you report exactly which
* two packages install the same file(s). Once again, please do NOT file
* a bug report unless you have completely understood the above message.
*
* package sys-kernel/linux-firmware-20120719 NOT merged
*
* Detected file collision(s):
*
* /lib/firmware/radeon/RV770_me.bin
* /lib/firmware/radeon/RS690_cp.bin
* /lib/firmware/radeon/RS600_cp.bin
* /lib/firmware/radeon/R300_cp.bin
* /lib/firmware/radeon/RV630_me.bin
* /lib/firmware/radeon/RV770_pfp.bin
* /lib/firmware/radeon/R420_cp.bin
* /lib/firmware/radeon/RV610_pfp.bin
* /lib/firmware/radeon/R100_cp.bin
* /lib/firmware/radeon/R600_pfp.bin
* /lib/firmware/radeon/RV635_pfp.bin
* /lib/firmware/radeon/RV730_me.bin
* /lib/firmware/radeon/R520_cp.bin
* /lib/firmware/radeon/RV630_pfp.bin
* /lib/firmware/radeon/RV710_me.bin
* /lib/firmware/radeon/RV620_me.bin
* /lib/firmware/radeon/RV710_pfp.bin
* /lib/firmware/radeon/R200_cp.bin
* /lib/firmware/radeon/RV670_pfp.bin
* /lib/firmware/radeon/RV670_me.bin
* /lib/firmware/radeon/RV635_me.bin
* /lib/firmware/radeon/RV730_pfp.bin
* /lib/firmware/radeon/RS780_pfp.bin
* /lib/firmware/radeon/R600_me.bin
* /lib/firmware/radeon/RS780_me.bin
* /lib/firmware/radeon/RV620_pfp.bin
* /lib/firmware/radeon/RV610_me.bin
* /lib/firmware/tigon/tg3_tso.bin
* /lib/firmware/tigon/tg3.bin
* /lib/firmware/tigon/tg3_tso5.bin
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* None of the installed packages claim the file(s).
*
* Package 'sys-kernel/linux-firmware-20120719' NOT merged due to file
* collisions. If necessary, refer to your elog messages for the whole
* content of the above message.
>>> Failed to install sys-kernel/linux-firmware-20120719, Log file:
>>> '/var/tmp/portage/sys-kernel/linux-firmware-20120719/temp/build.log'
* Messages for package sys-kernel/linux-firmware-20120719:
* Your configuration for sys-kernel/linux-firmware-20120719 has been saved in
* /etc/portage/savedconfig/sys-kernel/linux-firmware-20120719 for your editing pleasure.
* You can edit these files by hand and remerge this package with
* USE=savedconfig to customise the configuration.
* You can rename this file/directory to one of the following for
* its configuration to apply to multiple versions:
* ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/
* [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}]
* This package will overwrite one or more files that may belong to other
* packages (see list below). You can use a command such as `portageq
* owners / <filename>` to identify the installed package that owns a
* file. If portageq reports that only one package owns a file then do
* NOT file a bug report. A bug report is only useful if it identifies at
* least two or more packages that are known to install the same file(s).
* If a collision occurs and you can not explain where the file came from
* then you should simply ignore the collision since there is not enough
* information to determine if a real problem exists. Please do NOT file
* a bug report at http://bugs.gentoo.org unless you report exactly which
* two packages install the same file(s). Once again, please do NOT file
* a bug report unless you have completely understood the above message.
*
* package sys-kernel/linux-firmware-20120719 NOT merged
*
* Detected file collision(s):
*
* /lib/firmware/radeon/RV770_me.bin
* /lib/firmware/radeon/RS690_cp.bin
* /lib/firmware/radeon/RS600_cp.bin
* /lib/firmware/radeon/R300_cp.bin
* /lib/firmware/radeon/RV630_me.bin
* /lib/firmware/radeon/RV770_pfp.bin
* /lib/firmware/radeon/R420_cp.bin
* /lib/firmware/radeon/RV610_pfp.bin
* /lib/firmware/radeon/R100_cp.bin
* /lib/firmware/radeon/R600_pfp.bin
* /lib/firmware/radeon/RV635_pfp.bin
* /lib/firmware/radeon/RV730_me.bin
* /lib/firmware/radeon/R520_cp.bin
* /lib/firmware/radeon/RV630_pfp.bin
* /lib/firmware/radeon/RV710_me.bin
* /lib/firmware/radeon/RV620_me.bin
* /lib/firmware/radeon/RV710_pfp.bin
* /lib/firmware/radeon/R200_cp.bin
* /lib/firmware/radeon/RV670_pfp.bin
* /lib/firmware/radeon/RV670_me.bin
* /lib/firmware/radeon/RV635_me.bin
* /lib/firmware/radeon/RV730_pfp.bin
* /lib/firmware/radeon/RS780_pfp.bin
* /lib/firmware/radeon/R600_me.bin
* /lib/firmware/radeon/RS780_me.bin
* /lib/firmware/radeon/RV620_pfp.bin
* /lib/firmware/radeon/RV610_me.bin
* /lib/firmware/tigon/tg3_tso.bin
* /lib/firmware/tigon/tg3.bin
* /lib/firmware/tigon/tg3_tso5.bin
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* None of the installed packages claim the file(s).
*
* Package 'sys-kernel/linux-firmware-20120719' NOT merged due to file
* collisions. If necessary, refer to your elog messages for the whole
* content of the above message.
* GNU info directory index is up-to-date.
|
I'm not sure why I'm having these collisions, unless it's something I overlooked.
Thanks
Todd |
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Sun Sep 30, 2012 9:32 pm Post subject: |
|
|
you previously added the files in the list; perhaps by emerge radeon-ucode or by direct download from the manufacturer site(s). I would run
| Code: | rm -rf /lib/firmware/radeon
rm -rf /lib/firmware/tigon |
followed by | Code: | | emerge linux-firmware |
to let portage handle my firmware
_________________
Defund the FCC. |
|
| Back to top |
|
|
todd93
l33t
Joined: 30 Oct 2006
Posts: 625
Location: Missouri
|
| Posted: Mon Oct 01, 2012 9:53 am Post subject: |
|
|
| DONAHUE wrote: | you previously added the files in the list; perhaps by emerge radeon-ucode or by direct download from the manufacturer site(s). I would run
| Code: | rm -rf /lib/firmware/radeon
rm -rf /lib/firmware/tigon |
followed by | Code: | | emerge linux-firmware |
to let portage handle my firmware |
okay, now I can report a successful boot! That is fantastic! The only trouble is: I get to the KDM login screen and keyboard or mouse does not work! lol all I could really do is just sit here and laugh.
Thanks
Todd |
|
| Back to top |
|
|
DONAHUE
Watchman
Joined: 09 Dec 2006
Posts: 7651
Location: Goose Creek SC
|
| Posted: Mon Oct 01, 2012 3:33 pm Post subject: |
|
|
menuconfig should have
| Quote: | Device Drivers --->
Input device support --->
<*> Event interface |
| Code: | | emerge xorg-server xf86-input-evdev |
_________________
Defund the FCC. |
|
| Back to top |
|
|
todd93
l33t
Joined: 30 Oct 2006
Posts: 625
Location: Missouri
|
| Posted: Mon Oct 01, 2012 9:42 pm Post subject: |
|
|
DONAHUE, NeddySeagoon, I would like to say a very special THANK YOU!! I am up and running in the new kernel, and I want you both to know how much I deeply appreciate your help. The final hurdle actually was the ohci driver, it wasn't built into the kernel, so I built it after trying the "emerge xorg-server xf86-input-evdev" and failing, and it worked. It was so simple!! Once again, I want to say thank you, I am still having some issues with pulseaudio and lvm, however, they are unrelated and I shall search out a solution for those issues separately!! I definitely owe you guys!!
This one is SOLVED!!
Thanks!!
Todd |
|
| Back to top |
|
|
|
Kernel & Hardware
