Re: [gentoo-amd64] radeon driver problems
my Graphics support section is attached from a 4.6 kernel# Graphics support # CONFIG_AGP=y CONFIG_AGP_AMD64=m # CONFIG_AGP_INTEL is not set # CONFIG_AGP_SIS is not set # CONFIG_AGP_VIA is not set CONFIG_VGA_ARB=y CONFIG_VGA_ARB_MAX_GPUS=6 # CONFIG_VGA_SWITCHEROO is not set CONFIG_DRM=m # CONFIG_DRM_DP_AUX_CHARDEV is not set CONFIG_DRM_KMS_HELPER=m CONFIG_DRM_KMS_FB_HELPER=y CONFIG_DRM_FBDEV_EMULATION=y # CONFIG_DRM_LOAD_EDID_FIRMWARE is not set CONFIG_DRM_TTM=m # # I2C encoder or helper chips # # CONFIG_DRM_I2C_ADV7511 is not set # CONFIG_DRM_I2C_CH7006 is not set # CONFIG_DRM_I2C_SIL164 is not set # CONFIG_DRM_I2C_NXP_TDA998X is not set # CONFIG_DRM_TDFX is not set # CONFIG_DRM_R128 is not set CONFIG_DRM_RADEON=m CONFIG_DRM_RADEON_USERPTR=y CONFIG_DRM_AMDGPU=m CONFIG_DRM_AMDGPU_CIK=y CONFIG_DRM_AMDGPU_USERPTR=y # CONFIG_DRM_AMD_POWERPLAY is not set # # ACP (Audio CoProcessor) Configuration # # CONFIG_DRM_AMD_ACP is not set # CONFIG_DRM_NOUVEAU is not set # CONFIG_DRM_I915 is not set # CONFIG_DRM_MGA is not set # CONFIG_DRM_SIS is not set # CONFIG_DRM_VIA is not set # CONFIG_DRM_SAVAGE is not set # CONFIG_DRM_VGEM is not set # CONFIG_DRM_VMWGFX is not set # CONFIG_DRM_GMA500 is not set # CONFIG_DRM_UDL is not set # CONFIG_DRM_AST is not set # CONFIG_DRM_MGAG200 is not set # CONFIG_DRM_CIRRUS_QEMU is not set # CONFIG_DRM_QXL is not set # CONFIG_DRM_BOCHS is not set CONFIG_DRM_BRIDGE=y # # Display Interface Bridges # # # Frame buffer Devices # CONFIG_FB=y CONFIG_FIRMWARE_EDID=y CONFIG_FB_CMDLINE=y CONFIG_FB_NOTIFY=y # CONFIG_FB_DDC is not set # CONFIG_FB_BOOT_VESA_SUPPORT is not set CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set CONFIG_FB_SYS_FILLRECT=m CONFIG_FB_SYS_COPYAREA=m CONFIG_FB_SYS_IMAGEBLIT=m # CONFIG_FB_FOREIGN_ENDIAN is not set CONFIG_FB_SYS_FOPS=m # CONFIG_FB_SVGALIB is not set # CONFIG_FB_MACMODES is not set # CONFIG_FB_BACKLIGHT is not set CONFIG_FB_MODE_HELPERS=y CONFIG_FB_TILEBLITTING=y # # Frame buffer hardware drivers # # CONFIG_FB_CIRRUS is not set # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_ARC is not set # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set # CONFIG_FB_VGA16 is not set # CONFIG_FB_UVESA is not set # CONFIG_FB_VESA is not set CONFIG_FB_EFI=y # CONFIG_FB_N411 is not set # CONFIG_FB_HGA is not set # CONFIG_FB_OPENCORES is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set # CONFIG_FB_I740 is not set # CONFIG_FB_LE80578 is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON is not set # CONFIG_FB_ATY128 is not set # CONFIG_FB_ATY is not set # CONFIG_FB_S3 is not set # CONFIG_FB_SAVAGE is not set # CONFIG_FB_SIS is not set # CONFIG_FB_NEOMAGIC is not set # CONFIG_FB_KYRO is not set # CONFIG_FB_3DFX is not set # CONFIG_FB_VOODOO1 is not set # CONFIG_FB_VT8623 is not set # CONFIG_FB_TRIDENT is not set # CONFIG_FB_ARK is not set # CONFIG_FB_PM3 is not set # CONFIG_FB_CARMINE is not set # CONFIG_FB_SMSCUFX is not set # CONFIG_FB_UDL is not set # CONFIG_FB_IBM_GXT4500 is not set # CONFIG_FB_VIRTUAL is not set # CONFIG_FB_METRONOME is not set # CONFIG_FB_MB862XX is not set # CONFIG_FB_BROADSHEET is not set # CONFIG_FB_AUO_K190X is not set # CONFIG_FB_SIMPLE is not set # CONFIG_FB_SM712 is not set CONFIG_BACKLIGHT_LCD_SUPPORT=y CONFIG_LCD_CLASS_DEVICE=y # CONFIG_LCD_PLATFORM is not set CONFIG_BACKLIGHT_CLASS_DEVICE=y # CONFIG_BACKLIGHT_GENERIC is not set # CONFIG_BACKLIGHT_PWM is not set # CONFIG_BACKLIGHT_APPLE is not set # CONFIG_BACKLIGHT_PM8941_WLED is not set # CONFIG_BACKLIGHT_SAHARA is not set # CONFIG_BACKLIGHT_ADP8860 is not set # CONFIG_BACKLIGHT_ADP8870 is not set # CONFIG_BACKLIGHT_LM3630A is not set # CONFIG_BACKLIGHT_LM3639 is not set # CONFIG_BACKLIGHT_LP855X is not set # CONFIG_BACKLIGHT_LV5207LP is not set # CONFIG_BACKLIGHT_BD6107 is not set # CONFIG_VGASTATE is not set CONFIG_HDMI=y # # Console display driver support # CONFIG_VGA_CONSOLE=y CONFIG_VGACON_SOFT_SCROLLBACK=y CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=256 CONFIG_DUMMY_CONSOLE=y CONFIG_DUMMY_CONSOLE_COLUMNS=80 CONFIG_DUMMY_CONSOLE_ROWS=25 CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y # CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set CONFIG_LOGO=y # CONFIG_LOGO_LINUX_MONO is not set # CONFIG_LOGO_LINUX_VGA16 is not set CONFIG_LOGO_LINUX_CLUT224=y CONFIG_SOUND=m
Re: [gentoo-amd64] radeon driver problems
On Sun, 2016-10-09 at 08:03 +1100, Daiajo Tibdixious wrote: > On 9 Oct 2016 7:45 am, "Daiajo Tibdixious" <dai...@gmail.com> wrote: > > > > On 9 Oct 2016 12:09 am, "Drake Donahue" <donahu...@comcast.net> > wrote: > > > > > > On Sat, 2016-10-08 at 20:35 +1100, Daiajo Tibdixious wrote: > > > This relates to my ATI driver conflict with xorg-server problem. > > > > Sorry if this comes though in html format I did not realise the > last > > > > one was in html mode. > > > > I'm trying the solution to stop using fglrx and just use the > radeon > > > > driver, > > > > however I'm getting weird problems. > > > > > > > > I removed fglrx from VIDEO_CARDS. Enabled radeon driver as a > module i > > > > > > > > the kernel, > > > > plus several other options recommended by the wiki. > > > > First I hacked \etc\X11\xorg.conf to removed the ATI specific > code, > > > > however I get the same problem with X -configure code. > > > > > > > > Googling the actual error "Screen 0 deleted because of no > matching > > > > config section" > > > > shows that its not that, its some kind of driver problem. > > > > > > > > Any hints on what else I can try? I don't want to try the other > > > > alternative (use fglrx with old versions of xorg-server and the > > > > input-evdev,video-ati drivers) yet. > > > > > > Assuming you run udev or eudev and dbus, recommend you delete or > rename > > > /etc/X11/xorg.conf and allow the xorg server provided script to > run and > > > do the configuration for you. > > > If xorg still fails, recommend you run > > > awk > > > '/CONFIG_LOCALVERSION_AUTO/,/CONFIG_SOUND/' > /usr/src/linux/.config > > > and > > > provide the result here or in a pastebin. > > > > > With no xorg. conf get > > Open /dev/dri/card0: no such file or directory > > I do have udev with no custom setup. > > There is no output from that awk, CONFIG_LOCALVERSION_AUTO is not > in .config > It finds PCI:*(0:1:0:0) then later says Device(s) detected, but none > match those in config file > (I would have cut heaps of included text but cut/paste not working > well on phone) I'll send log file later Sorry, my copy and paste slipped and I lost the ability to read: awk '/Graphics support/,/CONFIG_SOUND/' /usr/src/linux/.config Same suspicion as Duncan--kernel config at fault.
Re: [gentoo-amd64] radeon driver problems
On Sat, 2016-10-08 at 20:35 +1100, Daiajo Tibdixious wrote: > This relates to my ATI driver conflict with xorg-server problem. > Sorry if this comes though in html format I did not realise the last > one was in html mode. > I'm trying the solution to stop using fglrx and just use the radeon > driver, > however I'm getting weird problems. > > I removed fglrx from VIDEO_CARDS. Enabled radeon driver as a module i > > the kernel, > plus several other options recommended by the wiki. > First I hacked \etc\X11\xorg.conf to removed the ATI specific code, > however I get the same problem with X -configure code. > > Googling the actual error "Screen 0 deleted because of no matching > config section" > shows that its not that, its some kind of driver problem. > I've tried everything I can think of (except putting the driver in > kernel with firmware blobs). > > Instead of my phone I borrowed another computer and can transfer > stuff > to it via USB. > > I have enclosed xorg.conf (from X -configure) and /var/log/Xorg.0.log > > Any hints on what else I can try? I don't want to try the other > alternative (use fglrx with old versions of xorg-server and the > input-evdev,video-ati drivers) yet. Assuming you run udev or eudev and dbus, recommend you delete or rename /etc/X11/xorg.conf and allow the xorg server provided script to run and do the configuration for you. If xorg still fails, recommend you run awk '/CONFIG_LOCALVERSION_AUTO/,/CONFIG_SOUND/' /usr/src/linux/.config and provide the result here or in a pastebin.
Re: [gentoo-amd64] Re: Stop keyboard after emerge
On Wed, 2015-08-26 at 18:34 +0200, mr_L4N wrote: Python updater updated only openoffice.bin, xorg log don't shows problems and all services active and running Il mercoledì 26 agosto 2015, Drake Donahue donahu...@comcast.net ha scritto: On Wed, 2015-08-26 at 17:23 +0200, mr_L4N wrote: hi, yesterday i,ve switched from Python 2 to 3 and upgraded all packages with emerge -uDn --changed-use @world. After this keyboard (mouse ok) works only to console and not GUI I've emerged the xorg drivers, rebuild module, evdev, and all xorg. I use xorg 1.16 with gnome 3.14 and systemd. Thanks in advance have you run python-updater have you read /var/log/Xorg.0.log? Have you checked dbus and udev status? fx8150 ~ # systemctl | grep udev systemd-udev-trigger.service loaded active exitedudev Coldplug all Devices systemd-udevd.service loaded active running udev Kernel Device Manager systemd-udevd-control.socket loaded active running udev Control Socket systemd-udevd-kernel.socket loaded active running udev Kernel Socket fx8150 ~ # systemctl | grep dbus dbus.service loaded active running D-Bus System Message Bus dbus.socket loaded active running D-Bus System Message Bus Socket do eselect opengl list and eselect opencl list yield appropriate results Try X -retro from the bootup terminal; Should get a black and white stippled screen with a movable mouse cursor
Re: [gentoo-amd64] Stop keyboard after emerge
On Wed, 2015-08-26 at 17:23 +0200, mr_L4N wrote: hi, yesterday i,ve switched from Python 2 to 3 and upgraded all packages with emerge -uDn --changed-use @world. After this keyboard (mouse ok) works only to console and not GUI I've emerged the xorg drivers, rebuild module, evdev, and all xorg. I use xorg 1.16 with gnome 3.14 and systemd. Thanks in advance have you run python-updater have you read /var/log/Xorg.0.log? Have you checked dbus and udev status? fx8150 ~ # systemctl | grep udev systemd-udev-trigger.service loaded active exitedudev Coldplug all Devices systemd-udevd.service loaded active running udev Kernel Device Manager systemd-udevd-control.socket loaded active running udev Control Socket systemd-udevd-kernel.socket loaded active running udev Kernel Socket fx8150 ~ # systemctl | grep dbus dbus.service loaded active running D-Bus System Message Bus dbus.socket loaded active running D-Bus System Message Bus Socket
Re: [gentoo-amd64] Nvidia or Xorg Problem with GLX [Solved]
On Tue, 2015-01-20 at 12:27 -0500, Frank Peters wrote: On Mon, 19 Jan 2015 13:56:40 -0500 Frank Peters frank.pet...@comcast.net wrote: NVIDIA(0): Failed to initialize the GLX module; It seems that the order of the module paths in xorg.conf makes all the difference. By placing the nvidia GLX directory before the xorg GLX directory the problem disappears and the nvidia GLX drivers are loaded correctly. Before (in xorg.conf): ModulePath /usr/lib64/xorg/modules ModulePath /usr/lib64/opengl/nvidia After: ModulePath /usr/lib64/opengl/nvidia ModulePath /usr/lib64/xorg/modules Now things work as expected. Apparently this path ordering was not necessary before some change was made either to either to xorg-server or nvidia-drivers. I had not experienced the problem until very recently even though my xorg.conf contained the reverse ordering. This is the proper solution that I was seeking. Now there is no need for deleting/renaming files as a workaround. Frank Peters IMHO, whoever is assigned to maintain the eselect-opengl ebuild has been having trouble for about 3 months now. Your solution to your problem is lovely.
Re: [gentoo-amd64] Re: Please get me straight about sysvinit vs. systemd, udev vs eudev vs mdev, virtuals and other things...
On Mon, 2014-03-03 at 10:38 -0800, Mark Knecht wrote: If I understand this all then systemd, in it's current state, is going to require removing udev as a stand-along package, will remove sysvinit as systemd provides /sbin/init, and will also replace OpenRC with it's own code for starting and stopping services? It's a big change but it's one of the reasons why I built the backup install on the SSD. None of this really touches my spinning rust install I use daily. Two systems - one upgraded to systemd, one new install with systemd: Two kernels for each system: - CONFIG_GENTOO_LINUX_INIT_SYSTEMD=y is enabled on one kernel for each system and #CONFIG_GENTOO_LINUX_INIT_SYSTEMD is not set disabled on one kernel for each system Both kernels boot for each system. Systemd initializes gentoo for the systemd enabled kernels Openrc initializes gentoo for the systemd disabled kernels BTW Gnome 3.8 runs on both systemd initialized and openrc initialized systems. http://wiki.gentoo.org/wiki/Systemd https://wiki.gentoo.org/wiki/Systemd/upgrade http://wiki.gentoo.org/wiki/GNOME/3.8-upgrade-guide
Re: [gentoo-amd64] Can't connect to internet from Live DVD.
snip support for the 5390 is probably not on the livedvd a system rescue cd may provide from my menuconfig: I use several rotating usb ralinks --- Ralink driver support Ralink rt2400 (PCI/PCMCIA) support Ralink rt2500 (PCI/PCMCIA) support Ralink rt2501/rt61 (PCI/PCMCIA) support Ralink rt27xx/rt28xx/rt30xx (PCI/PCIe/PCMCIA) support Ralink rt2500 (USB) support Ralink rt2501/rt73 (USB) support M Ralink rt27xx/rt28xx/rt30xx (USB) support [*] rt2800usb - Include support for rt33xx devices [*] rt2800usb - Include support for rt35xx devices (EXPERIMENTAL) [*] rt2800usb - Include support for rt53xx devices (EXPERIMENTAL) [*] rt2800usb - Include support for rt55xx devices (EXPERIMENTAL) [*] rt2800usb - Include support for unknown (USB) devices [ ] Ralink debug output Menuconfig help for RT53XX: CONFIG_RT2800USB_RT53XX: This adds support for rt53xx wireless chipset family to the rt2800usb driver. Supported chips: RT5370 Symbol: RT2800USB_RT53XX [=y] Type : boolean Prompt: rt2800usb - Include support for rt53xx devices (EXPERIMENTAL) Location: - Device Drivers - Network device support (NETDEVICES [=y]) - Wireless LAN (WLAN [=y]) - Ralink driver support (RT2X00 [=m]) - Ralink rt27xx/rt28xx/rt30xx (USB) support (RT2800USB [=m]) Defined at drivers/net/wireless/rt2x00/Kconfig:169 Depends on: NETDEVICES [=y] WLAN [=y] RT2X00 [=m] \ RT2800USB [=m]
Re: [gentoo-amd64] early boot failure, not sure how to diagnose
On Fri, 2013-08-09 at 09:07 +1000, Daiajo Tibdixious wrote: Logged in after failed boot. /home /boot are mounted, but nothing in them when I ls. ls of / shows all the normal things there. While logged in, I'm still getting boot messages, where USB devices, eg the mouse, disconnect and reconnect. There are a ridiculous number of sd devices in /dev. sda, sdb, sdc, sdd all go to 15. sda is the hard drive, sdb/sdc for USB devices. Never had sdd. Did see some errors, notably cannot mount /run bad superblock or something like that. Its hard to scroll back with USB messages constantly appearing, half a screenful each time. On Fri, Aug 9, 2013 at 6:40 AM, Volker Armin Hemmann volkerar...@googlemail.com wrote: Am 08.08.2013 10:43, schrieb Daiajo Tibdixious: I got new hardware for a home desktop a few days ago. Downloaded install-amd64-minimal-20130801.iso and am still booting from that cd as hard drive boot fails. I turned on logging in /etc/rc.conf, but no /var/log/rc.log is produced. The disks are mounted but readonly. I guess from this the problem is occurring before the root partition is mounted. I only have 4 partitions: boot, swap, root, and home. Since everything important is on the root partition, I'm not using an initramfs. I have many times tried to catch the error by watching the screen, but it scrolls past way to fast. The last part of the boot messages before things go crazy is Switching to clocksource TSC. I've been reading up on grub, but don't see anyway to get more info on what is going wrong. If I boot from the cd and chroot to the disk, everything seems to work fine. /boot is ext2 fs and this is my grug.conf: default 0 timeout 20 splashimage=(hd0,0)/boot/grub/splash.xpm.gz title Gentoo Linux 3.8.13 root (hd0,0) kernel /boot/3.8/13-0/bzImage root=/dev/sda3 and what is happening? does your kernel config have: CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y CONFIG_HOTPLUG=y CONFIG_FSNOTIFY=y CONFIG_DNOTIFY=y CONFIG_INOTIFY_USER=y CONFIG_NET=y CONFIG_PROC_FS=y CONFIG_SIGNALFD=y CONFIG_SYSFS=y CONFIG_SYSFS_DEPRECATED is not set CONFIG_UEVENT_HELPER_PATH= CONFIG_BLK_DEV_BSG=y CONFIG_TMPFS=y CONFIG_TMPFS_POSIX_ACL=y CONFIG_TMPFS_XATTR=y
Re: [gentoo-amd64] early boot failure, not sure how to diagnose
On Fri, 2013-08-09 at 09:07 +1000, Daiajo Tibdixious wrote: Logged in after failed boot. /home /boot are mounted, but nothing in them when I ls. ls of / shows all the normal things there. While logged in, I'm still getting boot messages, where USB devices, eg the mouse, disconnect and reconnect. There are a ridiculous number of sd devices in /dev. sda, sdb, sdc, sdd all go to 15. sda is the hard drive, sdb/sdc for USB devices. Never had sdd. Did see some errors, notably cannot mount /run bad superblock or something like that. Its hard to scroll back with USB messages constantly appearing, half a screenful each time. On Fri, Aug 9, 2013 at 6:40 AM, Volker Armin Hemmann volkerar...@googlemail.com wrote: Am 08.08.2013 10:43, schrieb Daiajo Tibdixious: I got new hardware for a home desktop a few days ago. Downloaded install-amd64-minimal-20130801.iso and am still booting from that cd as hard drive boot fails. I turned on logging in /etc/rc.conf, but no /var/log/rc.log is produced. The disks are mounted but readonly. I guess from this the problem is occurring before the root partition is mounted. I only have 4 partitions: boot, swap, root, and home. Since everything important is on the root partition, I'm not using an initramfs. I have many times tried to catch the error by watching the screen, but it scrolls past way to fast. The last part of the boot messages before things go crazy is Switching to clocksource TSC. I've been reading up on grub, but don't see anyway to get more info on what is going wrong. If I boot from the cd and chroot to the disk, everything seems to work fine. /boot is ext2 fs and this is my grug.conf: default 0 timeout 20 splashimage=(hd0,0)/boot/grub/splash.xpm.gz title Gentoo Linux 3.8.13 root (hd0,0) kernel /boot/3.8/13-0/bzImage root=/dev/sda3 and what is happening? Does kernel config have: CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y CONFIG_HOTPLUG=y CONFIG_FSNOTIFY=y CONFIG_DNOTIFY=y CONFIG_INOTIFY_USER=y CONFIG_NET=y CONFIG_PROC_FS=y CONFIG_SIGNALFD=y CONFIG_SYSFS=y CONFIG_SYSFS_DEPRECATED is not set CONFIG_UEVENT_HELPER_PATH= CONFIG_BLK_DEV_BSG=y CONFIG_TMPFS=y CONFIG_TMPFS_POSIX_ACL=y CONFIG_TMPFS_XATTR=y also this problem frequently results from graphics support attempting to invoke kms support with: modules instead of builtins with frame buffers enabled with the radeon driver enabled without building in appropriate firmware
Re: [gentoo-amd64] /run not mounting on 3.7.10 kernel
On Tue, 2013-04-30 at 18:30 +1000, Daiajo Tibdixious wrote: During the startup on 3.7.10 /run fails to mount with this error: mount: wrong fs type, bad option, bad superblock on tmpfs, missing codepage or helper program, or other error Googling shows many people getting this error, and its something to do with openrc and moving from /var/run to /run. What I can't understand is why I can boot 3.7.9 without any problems, while 3.7.10 bombs. I have DEVTMPFS enabled in the kernel. Obviously there is something else wrong with my 3.7.10 kernel but I just can't figure what. Is /run supposed to be a physical directory? I thought it was supposed to be in ram. I got lrwxrwxrwx 1 root root 4 Dec 5 14:13 /var/run - /run drwxr-xr-x 11 root root 360 Apr 30 18:17 /run Before the last upgrade of openrc (to 0.11.8) my 3.7.10 kernel was working fine. mounting devtmpfs at /dev has helped some victims, menuconfig: Device Drivers --- Generic Driver Options --- (/sbin/hotplug) path to uevent helper [*] Maintain a devtmpfs filesystem to mount at /dev [*] Automount devtmpfs at /dev, after the kernel mounted the rootfs
Re: [gentoo-amd64] keymap broken
On Tue, 2011-09-06 at 22:21 -0400, Mansour Al Akeel wrote: I got a newer laptop, and rather than installing gentoo, I just swapped the hard disks. Now when I boot into the new one, it works up to the level I am expecting (still need some drivers), but the keyboard act wierd. When I press m it types 0, and some other keys don't send anything at all. This issue starts when I start my xdm (configured to start slim). With the text run level (console), there's no issues until I start and stop xdm. I am not sure if I modified something long time ago in the config, to use different keymaps, but this issue didn't exist on the older laptop. What files could have such a configuration, that I need to look into ? Thank you. http://www.gentoo.org/doc/en/xorg-config.xml Configuring your keyboard To setup X to use an international keyboard, you just have to create the appropriate config file in /etc/X11/xorg.conf.d/. This example features a Czech keyboard layout: # nano -w /etc/X11/xorg.conf.d/30-keyboard.conf Section InputClass Identifier keyboard-all Driver evdev Option XkbLayout us,cz Option XkbModel logitech_g15 Option XkbRules xorg Option XkbOptions grp:alt_shift_toggle,grp:switch,grp_led:scroll,compose:rwin,terminate:ctrl_alt_bksp Option XkbVariant ,qwerty MatchIsKeyboard on EndSection
Re: [gentoo-amd64] Can't Emerge Thunderbird-5.0/6.0
On Tue, 2011-08-23 at 16:45 -0400, Frank Peters wrote: On Tue, 23 Aug 2011 16:02:58 -0400 Frank Peters frank.pet...@comcast.net wrote: Possibly these errors are related to USE=-alsa. Thanks to all respondents. Thunderbird-6 builds now. The problem was too little tmpfs space and the USE=-alsa flag. The new question is why is alsa required for the build to succeed? I don't follow thunderbird development but there is a previous bug report on this (https://bugs.gentoo.org/show_bug.cgi?id=308363) and there is also a noalsa-fixup patch in the current portage tree. Also, from the gentoo Changelog: 21 Oct 2010; Jory A. Pratt anar...@gentoo.org thunderbird-3.1.5.ebuild, +files/bug-606109.patch: Address build failure with -alsa Anyway, I'll use thunderbird with alsa until I can find more about this. Frank Peters How else can you enjoy a singing email?? :-)
Re: [gentoo-amd64] unsubscribe
On Fri, 2010-10-22 at 15:26 -0200, Daniel de Oliveira wrote: I have the same problem, I've tried to unsubscribe (to subscribe in another mail) and nothing happens. 2010/10/13 Thanasis thana...@asyr.hopto.org send mail to gentoo-amd64+unsubscr...@lists.gentoo.org -- Daniel de Oliveira Network and System Analyst Security Specialist IBM RISC Specialist IBM Storage Specialist Linux/Unix Specialist Linux User #: 405334 Read the direct6ions at: http://www.gentoo.org/main/en/lists.xml which say: To unsubscribe from a list, send an empty email to: listname+unsubscr...@lists.gentoo.org
Re: [gentoo-amd64] Unable to mount USB and CD on Gnome
On Thu, 2010-07-08 at 15:15 +0100, Clemente Aguiar wrote: For a while now when I insert a CD / DVD or a USB pen drive on my PC, it will not mount, and GNOME gives an error. If it is the DVD the error is as follows: Unable to mount DVDLABEL Not Authorized If it is the USB pen drive the error is similar: Unable to mount File System 1,0GB Not Authorized If I login as root then there is no problem, the disks will mount (and automount correctly), but if I login as a normal user it will not automount, and even if I go through the menu and select the drive it will not mount giving exactly the same error. One interesting note is that I can mount and unmount using gnome-mount and gnome-unmount utilities, for example: $ gnome-mount -d /dev/sdb1 $ gnome-umount -d /dev/sdb1 Can anybody help me with this problem? add the user to plugdev
Re: [gentoo-amd64] Re: Intel integrated graphics and Xorg
On Wed, 2010-02-24 at 02:13 -0400, Mansour Al Akeel wrote: Mark, thank you. Yes, this is new intel based system. Here's the link I got from gateway: http://support.gateway.com/s/notebook/2009/gateway/nv/nv59/NV59sp2.shtml I tried to recompile kernel without framebuffer, like you suggested. # Graphics support # CONFIG_AGP=y # CONFIG_AGP_AMD64 is not set CONFIG_AGP_INTEL=y # CONFIG_AGP_SIS is not set # CONFIG_AGP_VIA is not set CONFIG_VGA_ARB=y CONFIG_DRM=y CONFIG_DRM_KMS_HELPER=m # CONFIG_DRM_TDFX is not set # CONFIG_DRM_R128 is not set # CONFIG_DRM_RADEON is not set # CONFIG_DRM_I810 is not set CONFIG_DRM_I830=m CONFIG_DRM_I915=m CONFIG_DRM_I915_KMS=y # CONFIG_DRM_MGA is not set # CONFIG_DRM_SIS is not set # CONFIG_DRM_VIA is not set # CONFIG_DRM_SAVAGE is not set # CONFIG_VGASTATE is not set CONFIG_VIDEO_OUTPUT_CONTROL=m CONFIG_FB=m # CONFIG_FIRMWARE_EDID is not set # CONFIG_FB_DDC is not set # CONFIG_FB_BOOT_VESA_SUPPORT is not set CONFIG_FB_CFB_FILLRECT=m CONFIG_FB_CFB_COPYAREA=m CONFIG_FB_CFB_IMAGEBLIT=m # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set # CONFIG_FB_SYS_FILLRECT is not set # CONFIG_FB_SYS_COPYAREA is not set # CONFIG_FB_SYS_IMAGEBLIT is not set # CONFIG_FB_FOREIGN_ENDIAN is not set # CONFIG_FB_SYS_FOPS is not set # CONFIG_FB_SVGALIB is not set # CONFIG_FB_MACMODES is not set # CONFIG_FB_BACKLIGHT is not set # CONFIG_FB_MODE_HELPERS is not set # CONFIG_FB_TILEBLITTING is not set # # Frame buffer hardware drivers # # CONFIG_FB_CIRRUS is not set # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_ARC is not set # CONFIG_FB_VGA16 is not set # CONFIG_FB_N411 is not set # CONFIG_FB_HGA is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set # CONFIG_FB_LE80578 is not set # CONFIG_FB_INTEL is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON is not set # CONFIG_FB_ATY128 is not set # CONFIG_FB_ATY is not set # CONFIG_FB_S3 is not set # CONFIG_FB_SAVAGE is not set # CONFIG_FB_SIS is not set # CONFIG_FB_VIA is not set # CONFIG_FB_NEOMAGIC is not set # CONFIG_FB_KYRO is not set # CONFIG_FB_3DFX is not set # CONFIG_FB_VOODOO1 is not set # CONFIG_FB_VT8623 is not set # CONFIG_FB_TRIDENT is not set # CONFIG_FB_ARK is not set # CONFIG_FB_PM3 is not set # CONFIG_FB_CARMINE is not set # CONFIG_FB_GEODE is not set # CONFIG_FB_VIRTUAL is not set # CONFIG_FB_METRONOME is not set # CONFIG_FB_MB862XX is not set # CONFIG_FB_BROADSHEET is not set # CONFIG_BACKLIGHT_LCD_SUPPORT is not set CONFIG_BACKLIGHT_CLASS_DEVICE=m CONFIG_BACKLIGHT_GENERIC=m # CONFIG_BACKLIGHT_PROGEAR is not set # CONFIG_BACKLIGHT_MBP_NVIDIA is not set # CONFIG_BACKLIGHT_SAHARA is not set # # Display device support # # CONFIG_DISPLAY_SUPPORT is not set # # Console display driver support # CONFIG_VGA_CONSOLE=y CONFIG_VGACON_SOFT_SCROLLBACK=y CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=1024 CONFIG_DUMMY_CONSOLE=y # CONFIG_FRAMEBUFFER_CONSOLE is not set CONFIG_LOGO=y # CONFIG_LOGO_LINUX_MONO is not set # CONFIG_LOGO_LINUX_VGA16 is not set CONFIG_LOGO_LINUX_CLUT224=y When I boot, I get a blank screen, and can not control anything. From sshd, when I do startx: localhost linux # startx xauth: creating new authority file /root/.serverauth.3638 X.Org X Server 1.6.5 Release Date: 2009-10-11 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.31-gentoo-r6 x86_64 Current Operating System: Linux localhost 2.6.33-rc8 #5 SMP Wed Feb 24 08:24:27 AST 2010 x86_64 Build Date: 22 February 2010 07:09:57PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. 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: Wed Feb 24 09:42:51 2010 (==) Using config file: /etc/X11/xorg.conf FATAL: Module fbcon not found. Setting master expected keysym, got XF86TouchpadToggle: line 122 of inet /etc/X11/xinit/xinitrc: line 58: twm: command not found /etc/X11/xinit/xinitrc: line 59: xclock: command not found /etc/X11/xinit/xinitrc: line 62: exec: xterm: not found /etc/X11/xinit/xinitrc: line 60: xterm: command not found waiting for X server to shut down Dropping master localhost linux # = Where to move from here ? It looks like you have a running xserver. Recent improvements in xorgserver have removed xdm and twm and the old stipple screen as well as ctrl-alt-backspace as a way out of X. There is an xdm script which provides some functionality. If you have emerged a display manager-window manager-desktop manager and you have xdm in a run level: in /etc/conf.d/xdm set DISPLAYMANAGER=your display manager or take xdm out and put your display manager in a
Re: [gentoo-amd64] Re: Intel integrated graphics and Xorg
On Thu, 2010-02-25 at 00:26 -0400, Mansour Al Akeel wrote: Hello all, It's working. I think I was missing the fbcon in /etc/make.conf Any how, I am working to customize it, and yes i noticed they removed the old ctrl-alt-backspase, and I have been looking for a nice way to acheive the same. Alt-Sysreq-K just kills X. My login manager is SLim and DisplayManger is xmonad. The link you gave me is very usefull, and was what I am looking for. I added this merge key=input.xkb.options type=stringterminate:ctrl_alt_bksp/merge, but still not luck. I will continue looking. Thank you all. On Wed, Feb 24, 2010 at 12:16 PM, Drake Donahue donahu...@comcast.net wrote: On Wed, 2010-02-24 at 02:13 -0400, Mansour Al Akeel wrote: Mark, thank you. Yes, this is new intel based system. Here's the link I got from gateway: http://support.gateway.com/s/notebook/2009/gateway/nv/nv59/NV59sp2.shtml I tried to recompile kernel without framebuffer, like you suggested. # Graphics support # CONFIG_AGP=y # CONFIG_AGP_AMD64 is not set CONFIG_AGP_INTEL=y # CONFIG_AGP_SIS is not set # CONFIG_AGP_VIA is not set CONFIG_VGA_ARB=y CONFIG_DRM=y CONFIG_DRM_KMS_HELPER=m # CONFIG_DRM_TDFX is not set # CONFIG_DRM_R128 is not set # CONFIG_DRM_RADEON is not set # CONFIG_DRM_I810 is not set CONFIG_DRM_I830=m CONFIG_DRM_I915=m CONFIG_DRM_I915_KMS=y # CONFIG_DRM_MGA is not set # CONFIG_DRM_SIS is not set # CONFIG_DRM_VIA is not set # CONFIG_DRM_SAVAGE is not set # CONFIG_VGASTATE is not set CONFIG_VIDEO_OUTPUT_CONTROL=m CONFIG_FB=m # CONFIG_FIRMWARE_EDID is not set # CONFIG_FB_DDC is not set # CONFIG_FB_BOOT_VESA_SUPPORT is not set CONFIG_FB_CFB_FILLRECT=m CONFIG_FB_CFB_COPYAREA=m CONFIG_FB_CFB_IMAGEBLIT=m # CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set # CONFIG_FB_SYS_FILLRECT is not set # CONFIG_FB_SYS_COPYAREA is not set # CONFIG_FB_SYS_IMAGEBLIT is not set # CONFIG_FB_FOREIGN_ENDIAN is not set # CONFIG_FB_SYS_FOPS is not set # CONFIG_FB_SVGALIB is not set # CONFIG_FB_MACMODES is not set # CONFIG_FB_BACKLIGHT is not set # CONFIG_FB_MODE_HELPERS is not set # CONFIG_FB_TILEBLITTING is not set # # Frame buffer hardware drivers # # CONFIG_FB_CIRRUS is not set # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_ARC is not set # CONFIG_FB_VGA16 is not set # CONFIG_FB_N411 is not set # CONFIG_FB_HGA is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set # CONFIG_FB_LE80578 is not set # CONFIG_FB_INTEL is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON is not set # CONFIG_FB_ATY128 is not set # CONFIG_FB_ATY is not set # CONFIG_FB_S3 is not set # CONFIG_FB_SAVAGE is not set # CONFIG_FB_SIS is not set # CONFIG_FB_VIA is not set # CONFIG_FB_NEOMAGIC is not set # CONFIG_FB_KYRO is not set # CONFIG_FB_3DFX is not set # CONFIG_FB_VOODOO1 is not set # CONFIG_FB_VT8623 is not set # CONFIG_FB_TRIDENT is not set # CONFIG_FB_ARK is not set # CONFIG_FB_PM3 is not set # CONFIG_FB_CARMINE is not set # CONFIG_FB_GEODE is not set # CONFIG_FB_VIRTUAL is not set # CONFIG_FB_METRONOME is not set # CONFIG_FB_MB862XX is not set # CONFIG_FB_BROADSHEET is not set # CONFIG_BACKLIGHT_LCD_SUPPORT is not set CONFIG_BACKLIGHT_CLASS_DEVICE=m CONFIG_BACKLIGHT_GENERIC=m # CONFIG_BACKLIGHT_PROGEAR is not set # CONFIG_BACKLIGHT_MBP_NVIDIA is not set # CONFIG_BACKLIGHT_SAHARA is not set # # Display device support # # CONFIG_DISPLAY_SUPPORT is not set # # Console display driver support # CONFIG_VGA_CONSOLE=y CONFIG_VGACON_SOFT_SCROLLBACK=y CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=1024 CONFIG_DUMMY_CONSOLE=y # CONFIG_FRAMEBUFFER_CONSOLE is not set CONFIG_LOGO=y # CONFIG_LOGO_LINUX_MONO is not set # CONFIG_LOGO_LINUX_VGA16 is not set CONFIG_LOGO_LINUX_CLUT224=y When I boot, I get a blank screen, and can not control anything. From sshd, when I do startx: localhost linux # startx xauth: creating new authority file /root/.serverauth.3638 X.Org X Server 1.6.5 Release Date: 2009-10-11 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.31-gentoo-r6 x86_64 Current Operating System: Linux localhost 2.6.33-rc8 #5 SMP Wed Feb 24 08:24:27 AST 2010 x86_64 Build Date: 22 February 2010 07:09:57PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. 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: Wed Feb 24 09:42:51 2010 (==) Using config file: /etc/X11/xorg.conf FATAL: Module fbcon not found. Setting master expected keysym, got XF86TouchpadToggle: line 122 of inet /etc/X11/xinit
Re: [gentoo-amd64] Re: video driver / system state question
On Tue, 2010-01-26 at 09:30 -0800, Mark Knecht wrote: On Tue, Jan 26, 2010 at 2:59 AM, Peter Humphrey pe...@humphrey.ukfsn.org wrote: On Tuesday 26 January 2010 01:13:59 Mark Knecht wrote: mtrr: type mismatch for c000,1000 old: write-back new: write-combining [drm] MTRR allocation failed. Graphics performance may suffer. This rings a bell. Your kernel line in grub.conf has something like video=inteldrmfb:mtrr:3,ywrap, no? The 3 is causing the error above, or you may have a 4. Google should be able to find you the docs on this. The options are write-combining and write-back; if one doesn't work the other should. -- Rgds Peter. Hi all, OK - it's working and gentoo-amd64 is the first email recipient from my new i5-661 running Gentoo Linux and XFCE4. THANKS TO EVERYONE! I'll need to document what I did to get it going as well as archive files so as to protect myself from some sort of infant mortality or operator error. None the less at least it's up and usable. This seems to be one of those cases where I cannot recognize exactly who had the final answer as there were a lot of things I did last night to get the machine going, both based on information from this thread as well as a thread at intel-gfx. Clearly I'm still learning/confused about the exact technology here so I want to iron that out over the next few days. The main points, subject to me getting schooled on what's really happening here: 1) The new i5-661 processor and i915 running X are ONLY supported using KMS so there seem to be two ways to do this: a) Build the kernel with AGP, DRM and KMS into the kernel, or b) Build the kernel with AGP, DRM and KMS modular and then use i915.modeset=1 on the boot command line I am using b) at this time. 2) Use drm.debug=0x06 to get lots of nice messages from DRM about what's going on. 3) Configure the kernel to support frame buffers but turn off everything except these 4, and possibly only the first and last ones: (grep for FB and FRAMEBUFFER) CONFIG_FB=y CONFIG_FB_CFB_FILLRECT=m CONFIG_FB_CFB_COPYAREA=m CONFIG_FB_CFB_IMAGEBLIT=m CONFIG_FRAMEBUFFER_CONSOLE=y The CFB entries are probably not necessary but I haven't figured out where they are in the kernel yet to turn them off. They do load modules so they might be required. 4) In make.conf use these lines among others: CFLAGS=-O2 -march=native -pipe USE=hal dts mmx sse sse2 ssse3 sse4 -gnome -kde INPUT_DEVICES=evdev VIDEO_CARDS=intel fbdev to set up for X and get a normal text boot which I think is taking place in the frame buffer. 5) As root run Xorg -configure Xorg -config /root/xorg.conf.new If things go right I'm to the point where Drake was correct. X is up but the screen is blank. Copy xorg.conf.new to /etc/X/xorg.conf X -retro does work. Thanks Drake! 6) emerge xfce4-meta and then as user put exec startxfce4 in .xinitrc, and then startx Assuming I haven't made any omissions or stupid mistakes that gets me into xfce4. I don't know if I'm running X over a frame buffer or using a more native VGA. I will of course review this in more depth as I document it for real but I wanted to say thanks for the answers as they were all helpful. Cheers, Mark Attachment to circumvent mail client text wrapping Attachment provided to circumvent mail client text wrapping If you want CTRL ALT BACKSPACE to be able to shutdown X: If you don't have /etc/hal/fdi/policy/10-keymap.fdi: run: 'cp /usr/share/hal/fdi/policy/10osvendor/10-keymap.fdi /etc/hal/fdi/policy/10-keymap.fdi' open /etc/hal/fdi/policy/10-keymap.fdi and add as the last merge key: 'merge key=input.xkb.options type=stringgrp:alt_shift_toggle,terminate:ctrl_alt_bksp/merge' here the modified /etc/hal/fdi/policy/10-keymap.fdi looks like: ?xml version=1.0 encoding=ISO-8859-1? !-- -*- SGML -*- -- deviceinfo version=0.2 device match key=info.capabilities contains=input.keymap append key=info.callouts.add type=strlisthal-setup-keymap/append /match match key=info.capabilities contains=input.keys merge key=input.xkb.rules type=stringbase/merge !-- If we're using Linux, we use evdev by default (falling back to keyboard otherwise). -- merge key=input.xkb.model type=stringkeyboard/merge match key=/org/freedesktop/Hal/devices/computer:system.kernel.name string=Linux merge key=input.xkb.model type=stringevdev/merge /match merge key=input.xkb.layout type=stringus/merge merge key=input.xkb.variant type=string / merge key=input.xkb.options type=stringterminate:ctrl_alt_bksp/merge /match /device /deviceinfo If you want CTRL ALT BACKSPACE to be able to shutdown X: If you don't have /etc/hal/fdi/policy/10-keymap.fdi: run: 'cp /usr/share/hal/fdi/policy/10osvendor/10-keymap.fdi /etc/hal/fdi/policy/10-keymap.fdi' open /etc/hal/fdi/policy/10-keymap.fdi and add as the
Re: [gentoo-amd64] video driver / system state question
On Mon, 2010-01-25 at 16:09 -0800, Bob Sanders wrote: Mark Knecht, mused, then expounded: far no luck but I'm learning so it's interesting. My quick question goes like this - if I boot with no drivers I get a VGA console. If I modprobe a frame buffer driver at boot time then I get a nice looking but slow frame buffer console. All good so far. However my graphics adapter is supposed to use the i915 driver and when I modprobe that - either in auto-load or at the command like after logging in - my screen goes 'black'. I'm wondering what I do - other than look at what's in dmesg - to figure out what state the machine is in. Is the screen turned off? Is the driver running and putting out 'black'? The black is the monitor being driven beyond it's spec in either vertical or horitizontal or both. For it to work, you'll need a proper mode line that can be stolen from some other Linux system via a google search or by downloading puppy linux and using that to work out what X is doing. With X and gfx, /var/log/Xorg.0.log is your friend. Especially when used with a google search on the error message. Bob - have you emerged a window manager/desktop? twm and xterm are no longer provided with the server.
Re: [gentoo-amd64] video driver / system state question
On Mon, 2010-01-25 at 19:09 -0800, Mark Knecht wrote: On Mon, Jan 25, 2010 at 4:23 PM, Drake Donahue donahu...@comcast.net wrote: On Mon, 2010-01-25 at 16:09 -0800, Bob Sanders wrote: Mark Knecht, mused, then expounded: far no luck but I'm learning so it's interesting. My quick question goes like this - if I boot with no drivers I get a VGA console. If I modprobe a frame buffer driver at boot time then I get a nice looking but slow frame buffer console. All good so far. However my graphics adapter is supposed to use the i915 driver and when I modprobe that - either in auto-load or at the command like after logging in - my screen goes 'black'. I'm wondering what I do - other than look at what's in dmesg - to figure out what state the machine is in. Is the screen turned off? Is the driver running and putting out 'black'? The black is the monitor being driven beyond it's spec in either vertical or horitizontal or both. For it to work, you'll need a proper mode line that can be stolen from some other Linux system via a google search or by downloading puppy linux and using that to work out what X is doing. With X and gfx, /var/log/Xorg.0.log is your friend. Especially when used with a google search on the error message. Bob - have you emerged a window manager/desktop? twm and xterm are no longer provided with the server. No - I haven't since I cannot even startx and see anything. - Mark I believe the black screen is in fact a running xserver that has no display manager no window manager no desktop and thus nothing to display. Recommend you emerge your favorites. Alternate run: X -retro to start xserver that will show the old black/white stipple and a mouse cursor. Note: you will have to do a power off to get out of X.
Re: [gentoo-amd64] xorgconfig?
On Sun, 2010-01-24 at 10:51 -0800, Mark Knecht wrote: Did xorgconfig go away? http://www.gentoo.org/doc/en/xorg-config.xml gives a pretty up to date status. You might want to go with the flow (dbus,hal,udev) vice swimming upstream.
Re: [gentoo-amd64] [gentoo-user] my gentoo amd64 does not have sound
On Tue, 2009-12-15 at 20:15 +0800, Xi Shen wrote: hi, my laptop is thinkpad t61. according to the output of lspci -k 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel the driver is already loaded. and i have use alsaconf, and alsamixer to set the configuration. /etc/init.d/alsasound is started, but my system still does not have sound. what have i missed? Do you have codecs selected under: --- Intel HD Audio [*] Build hwdep interface for HD-audio driver [ ] Allow dynamic codec reconfiguration (EXPERIMENTAL) [ ] Support digital beep via input layer [*] Build Realtek HD-audio codec support [*] Build Analog Device HD-audio codec support [*] Build IDT/Sigmatel HD-audio codec support [*] Build VIA HD-audio codec support [*] Build ATI HDMI HD-audio codec support [*] Build NVIDIA HDMI HD-audio codec support [*] Build INTEL HDMI HD-audio codec support [*] Build Conexant HD-audio codec support [*] Build C-Media HD-audio codec support [*] Build Silicon Labs 3054 HD-modem codec support [*] Enable generic HD-audio codec parser [ ] Aggressive power-saving on HD-audio
[gentoo-amd64] Emerge problems involving kde and qt
Trying to help a friend update a stale system. Anyone know what all this
means?
I don't recognize the nomenclature of :4 as in qt-sql-4.5.1:4 (nor does
emerge)
emerge -uNDa --keep-going world yields
!!! Multiple package instances within a single package slot have been
pulled
!!! into the dependency graph, resulting in a slot conflict:
x11-libs/qt-sql:4
('installed', '/', 'x11-libs/qt-sql-4.5.3', 'nomerge') pulled in by
=x11-libs/qt-sql-4.5.0:4[sqlite,mysql] required by ('ebuild', '/',
'app-office/akonadi-server-1.2.1', 'merge')
(and 243 more)
('ebuild', '/', 'x11-libs/qt-sql-4.5.3', 'merge') pulled in by
x11-libs/qt-sql required by world
=x11-libs/qt-sql-4.5.1:4[qt3support] required by ('ebuild', '/',
'kde-base/kcminit-4.3.1', 'merge')
=x11-libs/qt-sql-4.5.1:4[qt3support] required by ('ebuild', '/',
'kde-base/kdeartwork-kscreensaver-4.3.1', 'merge')
(and 240 more)
Explanation:
New USE for 'x11-libs/qt-sql:4' are incorrectly set. In order to solve
this, adjust USE to satisfy '=x11-libs/qt-sql-4.5.0:4[sqlite,mysql]'.
Anyone know what all this means?
I don't recognize the nomenclature of :4 as in qt-sql-4.5.1:4 (nor does
emerge)
What needs to be typed where to
New USE for 'x11-libs/qt-sql:4' are incorrectly set. In order to solve
this, adjust USE to satisfy '=x11-libs/qt-sql-4.5.0:4[sqlite,mysql]'.
'nomerge') pulled in by 243+ packages whie 'nomerge pulled in by 240+
packages seems insane.
I'm thinking that unmerging all kde* packages and all qt* and then
USE=-kde -qt -qt3 -qt4 -qt3support emerge uND world may be needed?
Re: [gentoo-amd64] Emerge problems involving kde and qt
On Thu, 2009-11-19 at 17:29 -0600, Paul Hartman wrote: On Thu, Nov 19, 2009 at 5:18 PM, Drake Donahue donahu...@comcast.net wrote: Trying to help a friend update a stale system. Anyone know what all this means? I don't recognize the nomenclature of :4 as in qt-sql-4.5.1:4 (nor does emerge) The :4 means it is slot 4 (as opposed to the Qt 3.x stuff). The error is telling you to enable the sqlite and mysql USE flags for x11-libs/qt-sql which you can do by adding/editing a line like this in your /etc/portage/package.use file: x11-libs/qt-sql:4 sqlite mysql and then try your emerge operation again. Hopefully it will help. :) Thanks he says he is rolling now. would swear we tried '=qt-sql-4.5.1:4 sqlite mysql' earlier. maybe he typoed. Thanks from a gnome.
Re: [gentoo-amd64] Re: Warning Message After Emerge
On Sat, 2009-10-17 at 23:59 +, Duncan wrote: Frank Peters posted on Sat, 17 Oct 2009 19:02:15 -0400 as excerpted: Recently, after an emerge I will sometimes see this message in bold red colors: !!! CANNOT IMPORT HTTP.CLIENT: cannot import name HTTPSConnection Everything functions normally and there are no problems with anything else. But why the message? The source of the message is the portage getbinpkg.py file, but I don't know the purpose of this file. getbinpkg.py would do what its name implies, check for binary packages. Standard from-source emerging should work fine, as you noted it seems to, but if you run FEATURES=buildpkg as I do, or otherwise have binary packages available, it's likely you'll have trouble merging them when you try. The problem is likely related to portage's interaction with python. Do you have both python-3 and python 2.5 or 2.6 merged? The newest versions of python packages and portage itself should work fine in that case, but the fixes necessary to make it work are fairly recent, so you may have to remerge various python packages (some may require the newest ~arch version) so they setup modules for both python 3 and python 2.x -- formerly they only setup modules in whatever python happened to be the system python at the time. But if you don't bother with binary packages anyway, at least that message shouldn't be an issue for you, you should be able to simply ignore it. will running python-updater help this?
Re: [gentoo-amd64] Re: Kernel Config for /proc/self/smaps
On Sat, 2009-09-19 at 21:32 +, Duncan wrote: P.V.Anthony posted on Mon, 14 Sep 2009 01:54:53 +0800 as excerpted: Currently configuring kernel version 2.6.26 using make menuconfig. Went to filesystems and then to pseudo filesystems. The proc has already been activated. On this system, I cannot even de-activate the proc. I did that for testing. Under proc there is /proc/kcore support. That is also activated. Tried reading the help for the /proc/kcore but nothing there. I can manually set CONFIG_PROC_PAGE_MONITOR=y in the .config file. I would really like to learn how to set this using make menuconfig. Please bear with me and guide me on how to set CONFIG_PROC_PAGE_MONITOR=y using make menuconfig. [I've been offline for a week due to using bad memory while trying to flash a BIOS. Naturally it crashed, and I couldn't boot my main machine. I ended up ordering a pre-flashed BIOS chip from two states a way... and waiting the few days for it to ship. I feel like I'm just back from the dead! =:^) ] Hmm... perhaps it's elsewhere in the 2.6.26 kernel config. I'm now running 2.6.31, and will be starting on the 2.6.32 rcs in a week or two... It's also possible it's turned off and not even available to you due to some other dependency. I'd try tracing it if I hadn't just fallen a week behind, just to see. You can grep PROC__PAGE_MONITOR in the kernel sources and see what comes up if you want. That's what I'd do, tho having done stuff like that before I might be better equipped to filter out the uninteresting entries. But you gotta start somewhere. =:^) In menuconfig / is a shortcut to a find utility into which entering config_proc_page_monitor takes one to a help page with the following info: Symbol: PROC_PAGE_MONITOR [=y] Prompt: Enable /proc page monitoring Defined at fs/proc/Kconfig:61 Depends on: PROC_FS MMU EMBEDDED Location: - File systems - Pseudo filesystems - /proc file system support (PROC_FS [=y]
Re: [gentoo-amd64] linux-2.6.30-gentoo-r4 won't boot
On Thu, 2009-09-03 at 18:25 -0600, scotthathc...@comcast.net wrote: I am having trouble getting linux-2.6.30-gentoo-r4 to boot on an Asus K8V Deluxe. It starts the boot process and then spits out a bunch of similar lines which I did not write down and don't find their way into any logs. It then halts. I have tried starting with my previous config file and starting from scratch with similar results. The processor is an Atholon 64 3200. Does anyone have a config file that has worked on this board with this kernel? Does anyone know of the offending setting? Thanks, Scott For an a8v deluxe: http://pastebin.ca/1553335 you probably lost your hard drive controller drivers in the upgrade. libata drivers are now preferred for all drive types. ext2fs is no longer configured by default.
Re: [gentoo-amd64] Video for Linux - webcam
On Sun, 2009-08-09 at 10:33 -0300, Mansour Al Akeel wrote: I have been trying to get the webcam to work on: Linux mars 2.6.29-gentoo-r5 #1 SMP Sat Aug 8 13:33:30 ADT 2009 x86_64 AMD Athlon(tm) 64 X2 Dual-Core Processor TK-53 AuthenticAMD GNU/Linux lsusb Bus 002 Device 001: ID 1d6b:0001 Bus 001 Device 002: ID 05ca:1810 Ricoh Co., Ltd Bus 001 Device 001: ID 1d6b:0002 I enabled V4L in the Kernel and enabled API 1.0. Then I installed the driver as in : http://forums.gentoo.org/viewtopic-t-768893.html?sid=57e3dbf52a9be44c18f4f779069802ab Now, when I try this: == mplayer -fps 15 tv:// -tv driver=v4l2:device=/dev/v4l/video0 MPlayer 29040-4.1.2 (C) 2000-2009 MPlayer Team Playing tv://. TV file format detected. No such driver: v4l2 Exiting... (End of file) == So I tried without specifying a driver: $ mplayer -fps 25 tv:// -tv device=/dev/video MPlayer 29040-4.1.2 (C) 2000-2009 MPlayer Team Playing tv://. TV file format detected. Selected driver: dummy name: NULL-TV author: alex comment: Selected input hasn't got a tuner! == Opening video decoder: [raw] RAW Uncompressed Video VDec: vo config request - 320 x 200 (preferred colorspace: Planar YV12) VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is undefined - no prescaling applied. VO: [xv] 320x200 = 320x200 Planar YV12 Selected video codec: [rawyv12] vfm: raw (RAW YV12) == Audio: no sound FPS forced to be 25.000 (ftime: 0.040). Starting playback... V: 1.0 73/ 73 0% 6% 0.0% 0 0 V: 1.0 82/ 82 0% 6% 0.0% 0 0 Exiting... (End of file) I got a small window, with a green color and nothing else. I will appreciate any advice, as I don't want to keep booting to windows, only for this. :) Thanks Just guessing, don't have ricoh, but: In menu config the following choices (just for the camera, other multimedia devices not considered by me) and recompile kernel: Device Drivers --- Multimedia devices --- *** Multimedia core support *** M Video For Linux [*] Enable Video For Linux API 1 (DEPRECATED) (NEW) *** Multimedia drivers *** [ ] Load and attach frontend and tuner driver modules as needed [*] Video capture adapters (NEW) --- --- Video capture adapters [*] V4L USB devices (NEW) --- --- V4L USB devices M USB OV511 Camera support (NEW)
Re: [gentoo-amd64] Video for Linux - webcam
snip Saphirus Sage wrote: Mansour Al Akeel wrote: I have been trying to get the webcam to work on: Linux mars 2.6.29-gentoo-r5 #1 SMP Sat Aug 8 13:33:30 ADT 2009 x86_64 AMD Athlon(tm) 64 X2 Dual-Core Processor TK-53 AuthenticAMD GNU/Linux lsusb Bus 002 Device 001: ID 1d6b:0001 Bus 001 Device 002: ID 05ca:1810 Ricoh Co., Ltd Bus 001 Device 001: ID 1d6b:0002 I enabled V4L in the Kernel and enabled API 1.0. Then I installed the driver as in : http://forums.gentoo.org/viewtopic-t-768893.html?sid=57e3dbf52a9be44c18f4f779069802ab snip http://en.gentoo-wiki.com/wiki/Webcam#Kernel_configuration maybe a more useful reference.
Re: [gentoo-amd64] emerge -eav system failed with ati-drivers
snip I'm guessing you did an emerge --depclean sometime after compiling the 2.6.22-r2 kernel and after emerging a new gentoo-sources that erased your make files, This is something depclean loves to do while leaving 99% of the older kernel source files intact. I think depclean leaves your .config file in place. Been a few weeks since I burned myself last with this one. If you were following directions back in 2007 you should have a stored 2.6.22-r2 config in the /boot directory. Try emerge =sys-kernel/gentoo-sources-2.6.22-r2 to re-emerge the old package and regain the make files. What the osmp is about beats me. or Emerge a new gentoo-sources, eselect it, configure, compile, install a new (current) kernel.
Re: [gentoo-amd64] emerge -eav system failed with ati-drivers
On Sat, 2009-06-20 at 19:01 -0400, John P. Burkett wrote: Today on an amd64 machine I tried emerge -eav system. The process ended with the following message: Emerging (267 of 281) x11-drivers/ati-drivers-8.552-r2 * ati-driver-installer-8-11-x86.x86_64.run RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Could not find a Makefile in the kernel source directory. * Please ensure that /usr/src/linux points to a complete set of Linux sources * * ERROR: x11-drivers/ati-drivers-8.552-r2 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * ati-drivers-8.552-r2.ebuild, line 70: Called linux-mod_pkg_setup * linux-mod.eclass, line 578: Called linux-info_pkg_setup * linux-info.eclass, line 696: Called die * The specific snippet of code: *get_version || die Unable to calculate Linux Kernel version * The die message: * Unable to calculate Linux Kernel version Doing ls -lad /usr/src/linux elicits lrwxrwxrwx 1 root root 22 Sep 3 2007 /usr/src/linux - linux-2.6.22-gentoo-r2 Doing uname -r elicits 2.6.22-gentoo-r2-osmp snip I'm guessing you did an emerge --depclean sometime after compiling the 2.6.22-r2 kernel that erased your make files, This is something depclean loves to do while leaving 99% of the older kernel source files intact when a new kernel source has been emerged. I think it leaves your .config file. Been a few weeks since I burned myself last with this one. If you were following directions back in 2007 you should have a stored config in /boot Try emerge =sys-kernel/gentoo-sources-2.6.22-r2 to re-emerge the old package to regain the make files. What the osmp is about beats me. or Emerge a new gentoo-sources, eselect it, configure, compile, install a new kernel.
Re: [gentoo-amd64] trouble with both 32bit 64bit java in firefox
On Sat, 2009-05-09 at 14:59 +0200, Beso wrote: 2009/5/9 Daiajo Tibdixious dai...@gmail.com # eselect java-nsplugin list Available 32-bit Java browser plugins [1] emul-linux-x86-java-1.6 current [2] emul-linux-x86-java-1.6-plugin2 Available 64-bit Java browser plugins [1] sun-jdk-1.6 I have blackdown java installed but it does not show up in eselect. Why is that? When I start firefox-bin goto about:plugins it says no plugins installed, despite this symlink: /usr/lib32/nsbrowser/plugins/javaplugin.so - /usr/share/java-config-2/nsplugin/emul-linux-x86-java-1.6-javaplugin.so When I use 64 bit firefox with the sun jdk it comes up and 'sort of' works, sort of doesn't. In general I hate it because its flaky, consistently fails on 1 big applet. I was previously using the blackdown plugin, however if I manually create the symlink, firefox will not start up, it Segmentation fault's. This is the symlink I setup: /usr/lib64/nsbrowser/plugins/javaplugin.so - /opt/blackdown-jre-1.4.2.03/plugin/amd64/mozilla/libjavaplugin_oji.so I also tried pointing it to /opt/blackdown-jre-1.4.2.03/lib/amd64/libjavaplugin_jni.so which also causes a Segmentation fault. I dont care whether I use 32 or 64 bit firefox, I just want java to work reliably. Googling, a lot of people are getting Segmentation faults, with the suggestion use blackdown. However even mozilla's plugin page does not give the symlinks to use. This page http://fedora64.org/desktop-64-posts/java-x86_64/ says to make the source libjavaplugin_oji.so If I use that or javaplugin_oji.so firefox starts but about:plugins shows no plugins installed. My googling isn't turning up much helpful, I suspect I just don't know enough to provide good keywords. drop the blackdown java and use the official 1.6 release. the latest one provides 32 and 64 bit plugins. the blackdown java is really a bad piece of code now. -- dott. ing. beso java-config not eselect with java
Re: [gentoo-amd64] trouble with both 32bit 64bit java in firefox
On Sun, 2009-05-10 at 01:39 +, Daiajo Tibdixious wrote: On Sat, May 9, 2009 at 1:35 PM, Drake Donahue donahu...@comcast.net wrote: On Sat, 2009-05-09 at 14:59 +0200, Beso wrote: 2009/5/9 Daiajo Tibdixious dai...@gmail.com # eselect java-nsplugin list Available 32-bit Java browser plugins [1] emul-linux-x86-java-1.6 current [2] emul-linux-x86-java-1.6-plugin2 Available 64-bit Java browser plugins [1] sun-jdk-1.6 I have blackdown java installed but it does not show up in eselect. Why is that? When I start firefox-bin goto about:plugins it says no plugins installed, despite this symlink: /usr/lib32/nsbrowser/plugins/javaplugin.so - /usr/share/java-config-2/nsplugin/emul-linux-x86-java-1.6-javaplugin.so When I use 64 bit firefox with the sun jdk it comes up and 'sort of' works, sort of doesn't. In general I hate it because its flaky, consistently fails on 1 big applet. I was previously using the blackdown plugin, however if I manually create the symlink, firefox will not start up, it Segmentation fault's. This is the symlink I setup: /usr/lib64/nsbrowser/plugins/javaplugin.so - /opt/blackdown-jre-1.4.2.03/plugin/amd64/mozilla/libjavaplugin_oji.so I also tried pointing it to /opt/blackdown-jre-1.4.2.03/lib/amd64/libjavaplugin_jni.so which also causes a Segmentation fault. I dont care whether I use 32 or 64 bit firefox, I just want java to work reliably. Googling, a lot of people are getting Segmentation faults, with the suggestion use blackdown. However even mozilla's plugin page does not give the symlinks to use. This page http://fedora64.org/desktop-64-posts/java-x86_64/ says to make the source libjavaplugin_oji.so If I use that or javaplugin_oji.so firefox starts but about:plugins shows no plugins installed. My googling isn't turning up much helpful, I suspect I just don't know enough to provide good keywords. drop the blackdown java and use the official 1.6 release. the latest one provides 32 and 64 bit plugins. the blackdown java is really a bad piece of code now. -- dott. ing. beso java-config not eselect with java I java-config bacl top the sun one: The following VMs are avilable for generation-2: 1) Blackdown JRE 1.4.2.03 (blackown-jre-1.4.2) 2) Sun 32bit JRE 1.6.0.13 (emul-linux-x86-java-1.6) *) Sun JRE 1.6.0.13 (sun-jdk-1.6) Started firefox about:plugins shows no plugins. So I also did eslect java-nsplugin: : Avialble 64-bit Java browser plugins [1] sun-jdk-1.6 current Started firefox no plugins. I traced the symbolic links manually set it to /opt/sun-jdk-1.6.0.13/jre/lib/amd64/libnpjp2.so which also did not work. This is all really weird because I had it working with sun-jdk earlier. I also found /opt/firefox/plugins was point to /usr/lib32/nsbrowser/plugins. I repointed this to lib64 got this error: LoadPlugin: failed to initialize shared library /opt/sun-jdk-1.6.0.13/jre/lib/amd64/libnpjp2.so [...: wrong ELF class: ELFCLASS64 from firefox-bin (which I'm using for mail so I can start/stop firefox at will. I suspect that /opt/firefox/plugins is just for firefox-bin. You can install a Java plugin for your web browser by emerging a Java VM with the nsplugin USE flag set. Perhaps the use flag got lost?
Re: [gentoo-amd64] Change Install Prefix
On Thu, 2009-04-30 at 21:09 +0200, Justin wrote: Frank Peters wrote: Is there a way, aside from writing a custom ebuild script, of changing the install prefix for a package? What I want to do is install some packages under /usr/local or /opt rather than the default of /usr. Unless I am mistaken, there does not seem to be a way of doing this with either portage variables or with portage profiles. Using the ROOT variable is not feasible because the resulting emerge will create an independent tree of packages. I just want to shift some packages out of /usr without losing any dependency or linking information. Linux is a flexible system in that it will allow libraries, include files, and configure information to be stored in a variety of places without losing any interaction. Modification of PATH, PKG_CONFIG_PATH, CPPFLAGS, LDFLAGS, and other variables as well as the /etc/ld.so.conf file will keep a system integrated no matter where things are stored. Yet, unless I am missing something, Gentoo does not seem to embody this same flexibility, at least not in a simple manner. All packages have to go under /usr only. Is this actually the case or is there a way to change the installation prefix? Frank Peters perhaps you like to go with a prefixed portage: http://www.gentoo.org/proj/en/gentoo-alt/prefix/ From http://linuxreviews.org/gentoo/ebuilds/ Make a folder where you will store your own ebuilds mkdir -p /usr/local/portage and set that folder in /etc/make.conf: PORTDIR_OVERLAY=/usr/local/portage The folder structure in your overlay folder should be the same as found in /usr/portage.
Re: [gentoo-amd64] dvdrw drive not visible
On Tue, 2009-04-28 at 22:02 +, Daiajo Tibdixious wrote: When I boot off the live CD there is a /dev/hda /dev/cdrom /dev/cdrw /dev/dvd /dev/dvdrw etc it works just fine. When I boot off my kernel there are no such devices I can't use the drive. This is the same drive as in my old system, which just worked with no tweaking before. Obviously I am missing some driver, yet I have grovelled thru menuconfig to no avail. Google turns up many similar problems, however none have been helpful. If I boot off the live cd, is there a way to see what options I need? The drive shows as PIONEER DVD-RW DVR-109 on the live cd. if you have evdev support in your kernel, and dbus and hald in the boot or default run level, your cd/dvd should automount in /media. If you have gone with the current kernel trend it will be /dev/sr0 (sr_ something anyway) all hard drives will be sd_ and there will be no hd_. Aliasing will probably allow you to umount /dev/sr0 and then mount /dev/hda /mnt/cdrom. Easier to go with the flow and leave cd/dvd out of fstab and up to auto.
Re: [gentoo-amd64] Bug in Cooledit-3.17.17 - Patch Included
On Sat, 2009-04-25 at 22:23 -0400, Frank Peters wrote: Hello, I am not sure if this list is the appropriate place to file a bug report, but the problem does need confirmation before I go through bugzilla. After building a working amd64 system using the latest portage tree, I emerged my favorite text editor, cooledit, version 3.17.17 To my surprise, any cut/copy/paste operation immediately caused a crash. Fortunately, the error messages were quite informative and allowed me to quickly find the cause. A call to open in the file widget/editcmd.c of the cooledit source does not include the mode parameter. Somehow, with the latest libraries, this missing parameter causes the crash. The attached patch file, missing_mode.patch, will fix the problem. Apply with: patch -p1 missing_mode.patch. The gentoo sources include a few other patches as well that are also necessary, especially the gcc4 patch. But, as I mentioned, it would be beneficial if this problem could be confirmed. Cooledit is not the most popular text editor but maybe someone also uses it or is willing to test it. If someone can confirmn this, then I can file a bugreport with gentoo bugzilla. Frank Peters more problems than that: oddman ~ # cooledit cooledit: display :0.0 cannot load font -*-fixed-bold-r-*--13-120-*-*-*-80-* as a font set - trying raw load. cooledit: display :0.0 cannot load font -*-fixed-bold-r-*--13-120-*-*-*-80-* And crashed. And did not get picked up in gnome apps office
Re: [gentoo-amd64] Re: grub and maximum kernel file size
- Original Message - From: Duncan 1i5t5.dun...@cox.net To: gentoo-amd64@lists.gentoo.org Sent: Thursday, April 09, 2009 1:36 PM Subject: [gentoo-amd64] Re: grub and maximum kernel file size flockm...@gmx.at posted 200904091859.12109.flockm...@gmx.at, excerpted below, on Thu, 09 Apr 2009 18:59:11 +0200: thanks for the answer, i'm already running grub-0.97-r9. perhaps it is time to switch back to good old lilo, or to play with grub2 ;) I don't know then. Did you check the bugs mentioned in the changelog? I think at least one of them was a size bug. It may or may not apply. The other possible alternative might be to consider whether you actually need that initramfs or not. Often, you won't, provided you build the appropriate modules into the kernel and/or use an appropriate kernel command line. One exception is root on lvm2, since that requires userspace. However, here, while I run both kernel md/mdp RAID and LVM2, I deliberately kept my root filesystem off of LVM, thus avoiding an initramfs. root is on RAID (mdp), but that can be assembled by the kernel directly, using parameters fed to it at the commandline (or since 2.6.28 IIRC, as compiled in command line parameters). No initramfs seriously decomplicates things. But who am I to say? It's your system, not mine. It's worth considering tho. What exacly is the error message you get? -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman
Re: [gentoo-amd64] External HD to work with Gentoo and Vista.
On Mon, 2009-03-16 at 09:17 -0500, Chris Faulkner wrote: when i plug my external in, it automatically mounts for me.. I just used the ntfs-3g wiki and i think there's another one.. On Mon, Mar 16, 2009 at 9:09 AM, Paul Stear gen...@appjaws.plus.com wrote: On Monday 16 March 2009 10:08:03 Chris Faulkner wrote: oh and here's a link for ya too: http://en.gentoo-wiki.com/wiki/NTFS-3G Thanks to Chris and Duncan for your help. I now have it working and am currently copying all my mp3 files. I had to manually mount the external HD which is straight forward but it would be wonderful if kde/hal/dbus would take care of it for me. I have tried various things but always get the error message that I don't have the correct permissions. Is it possible do you think? Paul -- This message has been sent using kmail with gentoo linux is your user in plugd?
Re: [gentoo-amd64] Trying gentoo-sources - getting segfaults
On Fri, 2009-01-30 at 17:56 -0800, Mark Knecht wrote: Hi, I've been running rt-sources for quite a long time but with a small desire to try out vmware or one of the alternatives and some problems with emerging them I thought I'd take a look at gentoo-sources as a baseline. It's up and running - I'm writing this from it - but X just crashed and I'm seeing a couple of issues in dmesg: [ 76.601881] gnome-keyring-d[4606]: segfault at 73676e ip 0073676e sp 7fffcc1e6728 error 14 [ 149.819713] X[3804]: segfault at 1 ip 7f21248f397c sp 7fff388c1080 error 4 in libgcc_s.so.1[7f21248ec000+d000] m...@lightning ~ $ m...@lightning ~ $ uname -a Linux lightning 2.6.27-gentoo-r8 #4 SMP Fri Jan 30 17:42:08 PST 2009 x86_64 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux m...@lightning ~ $ I think Duncan mentioned something earlier this week about problems with emerges of gcc and some tool chain problems. Is it possible that something like that could be the cause of this? I don't think that in general a kernel change should cause X to segfault but do I need to emerge X again? If so then I'd like to get an gcc issues cleaned up before doing that if possible. Note that under rt-sources-2.6.24-rt1 I saw a radeon driver loaded. Under gentoo-sources-2.6.26.8-r12 I do not: m...@lightning ~ $ lsmod Module Size Used by snd_seq_midi7424 0 snd_pcm_oss38592 0 snd_mixer_oss 14912 1 snd_pcm_oss snd_seq_dummy 3396 0 snd_seq_oss29888 0 snd_seq_midi_event 7040 2 snd_seq_midi,snd_seq_oss snd_seq50144 6 snd_seq_midi,snd_seq_dummy,snd_seq_oss,snd_seq_midi_event uhci_hcd 31648 0 firewire_sbp2 15832 0 snd_hdsp 47812 1 snd_rawmidi20992 2 snd_seq_midi,snd_hdsp snd_seq_device 6996 5 snd_seq_midi,snd_seq_dummy,snd_seq_oss,snd_seq,snd_rawmidi snd_pcm72136 2 snd_pcm_oss,snd_hdsp snd_timer 20560 2 snd_seq,snd_pcm snd_page_alloc 8336 2 snd_hdsp,snd_pcm snd_hwdep 8072 1 snd_hdsp firewire_ohci 21828 0 snd56392 12 snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_hdsp,snd_rawmidi,snd_seq_device,snd_pcm,snd_timer,snd_hwdep soundcore 7008 1 snd ehci_hcd 47384 0 firewire_core 37152 2 firewire_sbp2,firewire_ohci crc_itu_t 2304 1 firewire_core i2c_nforce2 6976 0 i2c_core 21408 1 i2c_nforce2 ohci_hcd 37220 0 m...@lightning ~ $ Thanks in advance for any ideas. Cheers, Mark Sometimes more enlightening than lsmod is lspci -nnk which links hardware to built in drivers as well as to module drivers
Re: [gentoo-amd64] Re: can not install nvidia driver
echo x11-drivers/nvidia-drivers ~amd64 /etc/portage/package.keywords fixed this problem for me when I upgraded to kernel 2.6.27-r5 from 2.6.25-r7 - Original Message - From: Peter Bleszynski To: gentoo-amd64@lists.gentoo.org Sent: Saturday, December 13, 2008 2:53 AM Subject: Re: [gentoo-amd64] Re: can not install nvidia driver I was able to install nvidia-drivers while running gentoo-sources-2.6.27-r4 using the ebuild posted here: http://bugs.gentoo.org/show_bug.cgi?id=246425 On Fri, Dec 12, 2008 at 11:01 PM, Duncan 1i5t5.dun...@cox.net wrote: Mansour Al Akeel mansour.alak...@gmail.com posted 49433267.1090...@gmail.com, excerpted below, on Fri, 12 Dec 2008 23:56:23 -0400: In file included from /var/tmp/portage/x11-drivers/nvidia-drivers-173.14.09/work/NVIDIA-Linux- x86_64-173.14.09-pkg2/usr/src/nv/nv.c:14: /var/tmp/portage/x11-drivers/nvidia-drivers-173.14.09/work/NVIDIA-Linux- x86_64-173.14.09-pkg2/usr/src/nv/nv-linux.h:107:27: error: asm/semaphore.h: No such file or directory The arch-x86 (including 64-bit) header files were reorganized in kernel 2.6.27, and as that says, asm/semaphore.h (or more like asm-x86/ semaphore.h) no longer exists in .27. I won't install proprietaryware so no nvidia for me and no direct experience with it to help you with, but it's likely nVidia hasn't updated to take account of that yet (or if so it'd probably be with the newest drivers, which may not even be in portage yet let alone stable). You did mention switching your running kernel back to 2.6.26.x, which should work, but did you switch your kernel symlink back to it as well? If not, it's probably still pointing at the 2.6.27.x kernel, thus you'd still be getting the error. -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman
Re: [gentoo-amd64] Re: eselect problems
- Original Message - From: Mark Knecht [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Monday, November 24, 2008 9:35 AM Subject: Re: [gentoo-amd64] Re: eselect problems On Mon, Nov 24, 2008 at 6:12 AM, Tonko Mulder [EMAIL PROTECTED] wrote: Op maandag 24-11-2008 om 06:00 uur [tijdzone -0800], schreef Mark Knecht: On Sun, Nov 23, 2008 at 10:26 PM, Duncan [EMAIL PROTECTED] wrote: Mark Knecht [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Sun, 23 Nov 2008 14:35:42 -0800: The root cause of this is I wanted to emerge the newest version of Ardour from the pro-audio overlay and ran into a new message about it being masked by something called EAPI 2 which according to the message requires a 'newer' version of portage. (No revision given.) That's all this was about, and there's absoutely no rush to fix it as I'm not likely to really use Ardour. Just wanted to take a look at what sort of headway they are making with their feature set so it's really nothing but pure curiosity. OK. FWIW, for EAPI-2, you need the new ~arch portage-2.2-rcX series. EAPI-2 is allowed in various overlays and now in ~arch, but not in stable until a stable portage supports it. It'll bring a number of new features including full set support, per-package use-defaults (previously a USE flag could be defaulted to on per profile, but not per package, off being the unset default, of course), and IIRC use dependencies (if a package requires say C++ support and gcc has been built without it, it must now die with an error message telling the user to make the change, with use- deps, it could force gcc to be recompiled with C++ instead of dying, thus avoiding somebody leaving a 200-package emerge going overnight, only to come back the next day to find out it stopped with package #2 due to a USE dependency death). So there are some nice things coming in EAPI-2 and a number of packages can really use them. But an EAPI-2 supporting portage, while now in the tree, remains unstable, as there are still a few bugs to work out before it goes fully stable. So if you prefer a stable portage, you'll have to wait for EAPI-2, and any packages requiring it (which by definition can't be stabilized until an EAPI-2 portage is stable too). -- Duncan - List replies preferred. No HTML msgs. Thanks Duncan. I basically understand the portage stuff, in the sense that it's a new feature. I read a few eamils form the portage developers, etc., and got a sense of some of what it is supposed to do. that part I'm OK with, as I am, I guess, with the idea that someone who wrote the Ardour ebuild is requiring these new features. My real question is what is required to build that portage on an ~amd64 machine so that I can build Ardour? Is anyone on this list using portage-2.2.x? If so how did they get it to build? I run sys-apps/portage-2.2_rc15 But that just got installed with the updates. Not sure if there are special requirements or not. Thanks Tonko. Watch out for a portage downgrade if you haven't unmasked 2.2-rcX. Reading on the 32-bit list there are others who are getting downgraded due to developers wanting more testing on 2.1... Cheers, Mark The wisdom of making currently existing and useful packages depend on some future incomplete package management system (so that updates become arduous and/or impossible)?? Anyone discovered a way to cope with 'masked by eapx '? sys-apps/portage-2.2_rc15 did not relieve a 'masked by eap2'
Re: [gentoo-amd64] Problem with ethernet configuration
On Fri, 2008-11-07 at 13:59 +0100, manuel wrote: Daniel Matei ha scritto: Excuse me if my answer might be stupid but did you set up routes_eth0 and made a default gw? DANIEL MATEI ADMINISTRATOR SISTEME, TECHNET CONSULTING +4 021 2553636 (w) | +4 0732 770071 (m) | [EMAIL PROTECTED] Technically yours...! http://www.technet.ro -Original Message- From: manuel [mailto:[EMAIL PROTECTED] Sent: Friday, November 07, 2008 1:27 PM To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] Problem with ethernet configuration Drake Donahue ha scritto: On Thu, 2008-11-06 at 17:38 -0500, Drake Donahue wrote: On Thu, 2008-11-06 at 21:54 +, Beso wrote: 2008/11/6 manuel [EMAIL PROTECTED]: Hi All, I have two gentoo os on my pc, same HD, different partitions. Now they are both 2008! I really don't understand why on the first system I can get a static IP address working, the same configuration does not work on the second os and I must set it to dhcp to get it working! I need to get a static Ip address 'cause I would like to map ports on my router! I've tried a lot of configurations but it still does not work and at the moment i've no Ideas!!! if you have the same identical configuration one connects and the other doesn't. you cannot assign the same ip to 2 different boards at the same time. also if your router has saved the mac addresses and binded the ips for some time (usually routers can be set to do this) then you cannot bind the same ip for another pc. an alternative is to set the static bind routes in the dhcp configuration panel of your router and use dhcp. in this way you're able to use dhcp on the pcs that will still get the same ip address and so you'll be able to use them as they would have got the static route. you'll just have to bind without lease the mac address to an ip and then enable the dhcp in the router. i use this way of routing in my network. same pc same card same mac address for most of us who do this kind of thing. can does not work be made more specific? error/failure messages? wireless or wired connection? If the problem is an inability to use the internet and not one of net.eth0 failed to being reported at startup; check that /etc/resolv.conf contains a valid nameserver xxx.xxx.xxx.xxx type entry. I've checked router configuration, and seems to be ok! even If I restart my router I get the same issue! I checked: no mac is associated with ips! I've tried different Ip addresses but nothing, I've checked /etc/resolv.conf they are Identical in both oses! When I assign the static IP address to my second os and I start it I don't receive any error messages: gentoo manu # /etc/init.d/net.eth0 start * Caching service dependencies ... [ ok ] * Starting eth0 * Bringing up eth0 * 192.168.0.109 next couple of lines here tell if you have gateway [ ok ] Everything seems to be ok but I sill can't connect to the internet! I've two Macintosh too in my home net with static ip addresses assigned (both working!) and I usually use Samba to comunicate beetween them and my gentoo box. When i'm using static IP on my gentoo box it becomes no more available on the net, but I can connect from it to the other cmptrs using Ftp! I'm really getting mad. Thanks for your help This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. If you have received this email in error please notify the sender immediately by e-mail and delete this e-mail from your system. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Although the company has taken reasonable precautions to ensure no viruses are present in this email, the company will not accept responsibility for any loss or damage arising from the use of this email or attachments. The recipient should check this email and any attachments for the presence of viruses. Yes I did, I've just retried but nothing! manuel
Re: [gentoo-amd64] Problem with ethernet configuration
On Thu, 2008-11-06 at 21:54 +, Beso wrote: 2008/11/6 manuel [EMAIL PROTECTED]: Hi All, I have two gentoo os on my pc, same HD, different partitions. Now they are both 2008! I really don't understand why on the first system I can get a static IP address working, the same configuration does not work on the second os and I must set it to dhcp to get it working! I need to get a static Ip address 'cause I would like to map ports on my router! I've tried a lot of configurations but it still does not work and at the moment i've no Ideas!!! if you have the same identical configuration one connects and the other doesn't. you cannot assign the same ip to 2 different boards at the same time. also if your router has saved the mac addresses and binded the ips for some time (usually routers can be set to do this) then you cannot bind the same ip for another pc. an alternative is to set the static bind routes in the dhcp configuration panel of your router and use dhcp. in this way you're able to use dhcp on the pcs that will still get the same ip address and so you'll be able to use them as they would have got the static route. you'll just have to bind without lease the mac address to an ip and then enable the dhcp in the router. i use this way of routing in my network. same pc same card same mac address for most of us who do this kind of thing. can does not work be made more specific? error/failure messages? wireless or wired connection?
Re: [gentoo-amd64] Problem with ethernet configuration
On Thu, 2008-11-06 at 17:38 -0500, Drake Donahue wrote: On Thu, 2008-11-06 at 21:54 +, Beso wrote: 2008/11/6 manuel [EMAIL PROTECTED]: Hi All, I have two gentoo os on my pc, same HD, different partitions. Now they are both 2008! I really don't understand why on the first system I can get a static IP address working, the same configuration does not work on the second os and I must set it to dhcp to get it working! I need to get a static Ip address 'cause I would like to map ports on my router! I've tried a lot of configurations but it still does not work and at the moment i've no Ideas!!! if you have the same identical configuration one connects and the other doesn't. you cannot assign the same ip to 2 different boards at the same time. also if your router has saved the mac addresses and binded the ips for some time (usually routers can be set to do this) then you cannot bind the same ip for another pc. an alternative is to set the static bind routes in the dhcp configuration panel of your router and use dhcp. in this way you're able to use dhcp on the pcs that will still get the same ip address and so you'll be able to use them as they would have got the static route. you'll just have to bind without lease the mac address to an ip and then enable the dhcp in the router. i use this way of routing in my network. same pc same card same mac address for most of us who do this kind of thing. can does not work be made more specific? error/failure messages? wireless or wired connection? If the problem is an inability to use the internet and not one of net.eth0 failed to being reported at startup; check that /etc/resolv.conf contains a valid nameserver xxx.xxx.xxx.xxx type entry.
Re: [gentoo-amd64] Problems customizing gentoo
On Thu, 2008-10-02 at 19:42 -0500, Rick Meredith wrote:
On Thursday 02 October 2008 04:35:03 pm Greg wrote:
I've been having problems customizing gentoo on my Acer Aspire T180-UA380B
AMD Desktop PC.
I've been using i686 versions of gentoo for years on my pentium3 with no
problems.
Here are further specs and what I've tried:
Acer Aspire T180-UA380B AMD Desktop PC - AMD Athlon 64
3800+ 2.4GHz, 2GB DDR2, 160GB SATA, DL DVD±RW, Gigabit LAN, Flash
Reader, running off of a 2007.0 AMD64 live cd chrooted environment.
I keep running into the same issue no matter what USE flags I have
specified in make.conf, what make.profile I have specified (attempted
2007.0, 2008.0, hardened, 2007.0 x86 under a 32bit chrooted environment and
chost set accordingly in make.conf.
The error I get follows:
* ERROR: sys-libs/glibc-2.6.1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 3362: Called eblit-run 'src_compile'
* environment, line 1087: Called eblit-glibc-src_compile
* src_compile.eblit, line 181: Called toolchain-glibc_src_compile
* src_compile.eblit, line 122: Called die
* The specific snippet of code:
* make PARALLELMFLAGS=${MAKEOPTS} || die make for ${ABI} failed
* The die message:
* make for default failed
*
* If you need support, post the topmost build error, and the call stack if
relevant. * A complete build log is located at
'/var/log/portage/sys-libs:glibc-2.6.1:20081002-111002.log'. * The ebuild
environment file is located at
'/var/build/portage/sys-libs/glibc-2.6.1/temp/environment'. *
If I start off with a stage3-amd64-2007.0 tarvol, don't try to customize my
system by trying to make a stage1, and just do emerge --update system, I
end up with errors upgrading grep regarding libpcre.
Anythoughts would be greatly appreciated as I've been struggling with this
for months trying to find a solution.
If I need to provide more information or need to post this to a more
appropriate list, please let me know.
Very best,
Greg Osborne
What do you have in your /etc/make.conf
Regards Rick
TRY using 2008.0 minimal livecd following the handbook in detail as
though you were a gentoo first timer. A lot of knowledge is also a
dangerous thing.
Re: [gentoo-amd64] no boot screen, cannot see options.
snip splash.xpm.gz was removed from /boot/grub by person or persons unknown presumably incident to an update. splash.xpm.gz still exists at /usr/share/grub/splash.xpm.gz so running: cp /usr/share/grub/splash.xpm.gz /boot/grub/splash.xpm.gz will restore the status quo ante running: emerge grub-splashes will add 8 new .xpm.gz files to /boot/grub/, as none of these is named splash.xpm.gz, simply emerging grub-splashes will not restore the boot screen. To use one of the new splashes requires editing grub.conf 's splashimage= line to reflect one of the (no doubt) wonderfully decorative splashes.. Alternatively, delete or comment the splashimage= line and fallback to a plain undecorated boot options menu.
Re: [gentoo-amd64] wxSVGXML?
On Wed, 2008-06-04 at 12:50 -0400, Mark Haney wrote: Sebastian Redl wrote: Mark Haney wrote: Looking at the source code and the ebuild for wxSVG, I see no reason why the file wouldn't be installed. Are you sure you don't have the wxSVGXML directory in /usr/include? xmlsvg.h should be in there. Sebastian That directory doesn't exist in my system: octavian dvdstyler # ls /usr/include/wx* -d /usr/include/wx-2.6 /usr/include/wx-2.8 /usr/include/wxSVG /usr/include/wxXML Which I don't get. Is there a USE flag that would account for this? FWIW nothing installed in 2 of 2 systems here, but a masked wxsvg ebuild is in /usr/portage/media-libs on both -- Libenter homines id quod volunt credunt -- Caius Julius Caesar Mark Haney Sr. Systems Administrator ERC Broadband (828) 350-2415 Call (866) ERC-7110 for after hours support -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] multicore strange issue
On Tue, 2008-06-03 at 15:15 +, Beso wrote: 2008/6/3 Drake Donahue [EMAIL PROTECTED]: On Tue, 2008-06-03 at 09:01 +, Beso wrote: hi, i've got a strange problem with my new notebook pc. i've bought a pc with an amd athlon 64 x2 processor with 2 cores, an atheros board and an rs690 ati. my old pc was a turion 64 with an atheros board and an rs480. now the components inside are all about the same so i've just copied the old gentoo system into the new pc and tried to recompile the kernel to have it tuned for the new processor. so the thing i've done was to activate the symetric multiprocessing and set to compiled into the kernel of md4, md5, md6 and aes x86_64 chipers for a luks /home chipering. the problem is that with the old normal config the kernel detects one processor and one core and it works, loading the modules, but when enabling simetric multiprocessing the kernel detects just one processor and one core and then it fails to load modules because of a different executable format in the modules. the strange thing is that opensuse livecd and mandriva live cd recognize the double processor (/proc/cpuinfo has 2 lines) and is able to step it in the right way. does anyone has a hint on what to control in the kernel config to see what's wrong?! thanks. -- dott. ing. beso If the attempt to boot does not end in a kernel panic; use shift-page up to get to the top of the console output produced during boot. If the boot loader has started an SMP kernel, a line similar to this: Linux Version 2.6.24-gentoo-r8 ([EMAIL PROTECTED]) (gcc version 4.1.1 (gentoo 4.1.1-r3)) #1 SMP Sat May 24 14:06:10 EDT 2008 should appear. The key word being SMP. No key word, SMP, means that make menuconfig (or whatever kernel configuration tool you use needs to be redone. As far as I know under, Processor type and features,: [*] Symmetric multi-processing support Subarchitecture Type (PC-compatible) --- Processor family (Opteron/Athlon64/Hammer/K8) --- produces an appropriate SMP kernel. A shift-page down should reveal a line like: CPU has two num_cores A couple more shift-page down: Initializing CPU#0 About 3 more shift-page down: Brought up 2 CPU's. About modules, I'm guessing modules compiled for single cpu have differences from those compiled for multiple cpu. Also guessing that /etc/modules/autoload.d and/or udev is trying to load single cpu module(s) that were not written to adjust to a single cpu kernel. so grub needs a different line at startup when using multicor I had assumed you had established a multiboot grub with one entry pointed to the old kernel and another entry pointed to a newly compiled SMP kernel. -- dott. ing. beso -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] multicore strange issue
On Tue, 2008-06-03 at 09:01 +, Beso wrote: hi, i've got a strange problem with my new notebook pc. i've bought a pc with an amd athlon 64 x2 processor with 2 cores, an atheros board and an rs690 ati. my old pc was a turion 64 with an atheros board and an rs480. now the components inside are all about the same so i've just copied the old gentoo system into the new pc and tried to recompile the kernel to have it tuned for the new processor. so the thing i've done was to activate the symetric multiprocessing and set to compiled into the kernel of md4, md5, md6 and aes x86_64 chipers for a luks /home chipering. the problem is that with the old normal config the kernel detects one processor and one core and it works, loading the modules, but when enabling simetric multiprocessing the kernel detects just one processor and one core and then it fails to load modules because of a different executable format in the modules. the strange thing is that opensuse livecd and mandriva live cd recognize the double processor (/proc/cpuinfo has 2 lines) and is able to step it in the right way. does anyone has a hint on what to control in the kernel config to see what's wrong?! thanks. -- dott. ing. beso If the attempt to boot does not end in a kernel panic; use shift-page up to get to the top of the console output produced during boot. If the boot loader has started an SMP kernel, a line similar to this: Linux Version 2.6.24-gentoo-r8 ([EMAIL PROTECTED]) (gcc version 4.1.1 (gentoo 4.1.1-r3)) #1 SMP Sat May 24 14:06:10 EDT 2008 should appear. The key word being SMP. No key word, SMP, means that make menuconfig (or whatever kernel configuration tool you use needs to be redone. As far as I know under, Processor type and features,: [*] Symmetric multi-processing support Subarchitecture Type (PC-compatible) --- Processor family (Opteron/Athlon64/Hammer/K8) --- produces an appropriate SMP kernel. A shift-page down should reveal a line like: CPU has two num_cores A couple more shift-page down: Initializing CPU#0 About 3 more shift-page down: Brought up 2 CPU's. About modules, I'm guessing modules compiled for single cpu have differences from those compiled for multiple cpu. Also guessing that /etc/modules/autoload.d and/or udev is trying to load single cpu module(s) that were not written to adjust to a single cpu kernel. -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] new clean rebuild
- Original Message - From: Beso To: gentoo-amd64@lists.gentoo.org Sent: Saturday, May 17, 2008 2:04 PM Subject: Re: [gentoo-amd64] new clean rebuild snipbeso discussed rebuild 2008/5/17 Mark Knecht [EMAIL PROTECTED] said in part in reply: 1) Mask grub-0.97.r4 for now. Recommend not doing the step above. In contrast to my experience a week ago when ext2/ext3 filesystems were being built with INODE_SIZE=128 (in spite of a default INODE_SIZE=256 in the /etc/mke2fs.conf file}; yesterday, an up-to-date mke2fs was honoring the default setting and producing ext2/ext3 filesystems with INODE_SIZE=256. If one runs mke2fs as suggested in the handbook to create a filesystem for use as /boot the filesystem will have INODE_SIZE=256. Therefore grub-0.97.r4 and older will not be able to setup a stage 1/stage1.5/stage2 capable of loading /boot. At the point the handbook follower finds that grub 0.97.4 is reporting: quote grub setup (hd0) Checking if /boot/grub/stage1 exists... no Checking if /grub/stage1 exists... no Error 2: Bad file or directory type unquote The valid recovery choices then will be: a) unmask grub, emerge grub (version 0.97.5 or newer), run grub and setup the desired drive or b) move or copy /boot and subdirectories to another partition, remake the filesystem specifying INODE_SIZE=128, return /boot and subdirectories to the remade partition, run grub setup the desired drive. snipMark suggested rebuild techniquesbeso further discussed/replied Beso said in part in reply: ps. i've never had any problems with grub, unless the fact that i'm not able to rebuild it with the grubfx image (as the opensuse version). I've played extensively with grub 0.97-r5 in the last 10 days and it is not a problem. Should also be noted that emerging/installing grub has no affect on the ability to boot an existing installation. Effects are not felt until grub or grub-install is run or grub.conf is edited. -- dott. ing. beso -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] Can't install Grub 0.97-r5
- Original Message - From: Raffaele BELARDI [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Wednesday, May 07, 2008 6:22 AM Subject: Re: [gentoo-amd64] Can't install Grub 0.97-r5 On Wed, 2008-05-07 at 10:34 +0200, [EMAIL PROTECTED] wrote: I emerged grub's last version. So stage 1, 1.5 2 are in /boot/grub allright. But trying to install the new mbr gives: grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub setup (hd0) Checking if /boot/grub/stage1 exists... no Checking if /grub/stage1 exists... no Error 15: File not found Of course, /boot/grub/stage1 is there. So I'm stuck with a half installed grub and dare not reboot. I re-emerged the last version to no avail. Any practical advice before I re-emerge previous grub version? There was a related issue discussed on this list recently, search the archives for email from Duncan with subject boot Gentoo from USB key dated May, 2. I don't know if this really applies to you, in my case I had that problem on a newly formatted (USB) drive. Newer mkfs.ext2 by default build 256 bytes I-nodes, and these are not recognized by grub. I re-formatted the drive using 128 bytes I-nodes (option -I to mkfs.ext2), and it ran smoothly. The symptoms were exactly as you describe, I could see the stage* files on the disk with ls, but grub told me Error 15. Did you re-create the filesystem on (hd0,0) recently? If so, you'll probably have the 256 byte I-Nodes that grub doesn't like. You can check I-node size with dumpe2fs. Grub 0.97.5 handles 256 inodes. Handling 256 inodes was a major reason that 0.97.5 was written. raf -- gentoo-amd64@lists.gentoo.org mailing list -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] Can't install Grub 0.97-r5
- Original Message - From: Beso To: gentoo-amd64@lists.gentoo.org Sent: Wednesday, May 07, 2008 8:31 AM Subject: Re: [gentoo-amd64] Can't install Grub 0.97-r5 2008/5/7 Volker Armin Hemmann [EMAIL PROTECTED]: On Mittwoch, 7. Mai 2008, [EMAIL PROTECTED] wrote: I emerged grub's last version. So stage 1, 1.5 2 are in /boot/grub allright. But trying to install the new mbr gives: grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub setup (hd0) Checking if /boot/grub/stage1 exists... no Checking if /grub/stage1 exists... no Error 15: File not found Of course, /boot/grub/stage1 is there. So I'm stuck with a half installed grub and dare not reboot. I re-emerged the last version to no avail. Any practical advice before I re-emerge previous grub version? emmm... I did nothing when I updated grub - and it just worked fine -- gentoo-amd64@lists.gentoo.org mailing list you have left the old version in use. to fully update grub not only you need to update it via portage but also you should reinstall the bootloader. maybe portage does it itself but i'm not sure about this last affirmation. confirm that the last affirmation is true dott. ing. beso
Re: [gentoo-amd64] Can't install Grub 0.97-r5
- Original Message - From: Andrew Long [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Wednesday, May 07, 2008 9:18 AM Subject: Re: [gentoo-amd64] Can't install Grub 0.97-r5 On Wed, May 7, 2008 at 4:34 AM, [EMAIL PROTECTED] wrote: I emerged grub's last version. So stage 1, 1.5 2 are in /boot/grub allright. But trying to install the new mbr gives: grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub setup (hd0) Checking if /boot/grub/stage1 exists... no Checking if /grub/stage1 exists... no Error 15: File not found Of course, /boot/grub/stage1 is there. So I'm stuck with a half installed grub and dare not reboot. I re-emerged the last version to no avail. Any practical advice before I re-emerge previous grub version? -- gentoo-amd64@lists.gentoo.org mailing list Is /boot mounted? Grub has made a guess as to which drive to call hd0. Perhaps it guessed wrong? running: grub find /boot/grub/stage1 will tell where grub sees the specified file Unrelated thought: if you had an inode_size problem the error would be: grub setup (hd1) Checking if /boot/grub/stage1 exists... no Checking if /grub/stage1 exists... no Error 2: Bad file or directory type -- gentoo-amd64@lists.gentoo.org mailing list -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] Can't install Grub 0.97-r5
- Original Message - From: Volker Armin Hemmann [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Wednesday, May 07, 2008 7:05 AM Subject: Re: [gentoo-amd64] Can't install Grub 0.97-r5 On Mittwoch, 7. Mai 2008, [EMAIL PROTECTED] wrote: I emerged grub's last version. So stage 1, 1.5 2 are in /boot/grub allright. But trying to install the new mbr gives: grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub setup (hd0) Checking if /boot/grub/stage1 exists... no Checking if /grub/stage1 exists... no Error 15: File not found Of course, /boot/grub/stage1 is there. So I'm stuck with a half installed grub and dare not reboot. I re-emerged the last version to no avail. Any practical advice before I re-emerge previous grub version? emmm... I did nothing when I updated grub - and it just worked fine same here on two systems. Did a reboot to test before reinstalling grub. I think the situation being warned about is one in which: a) /boot filesystem is added or is remade as ext2/ext3 with inode_size=256 and b) the failure to reinstall grub has left the old stages 1, (1.5), and 2 in place in the MBR which will fail to handle the inode_size=256 file system. -- gentoo-amd64@lists.gentoo.org mailing list -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] Grub upgrade note.
- Original Message - From: Michael George [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Tuesday, May 06, 2008 1:50 PM Subject: Re: [gentoo-amd64] Grub upgrade note. On Tue, May 06, 2008 at 08:49:13AM -0500, Barry Schwartz wrote: Mark Haney [EMAIL PROTECTED] skribis: I've done some grub installs in the past, but this is a new one on me. What exactly does install the new version's 'stage1' mean? How do I do what this is telling me to do? That's the part where you write a new MBR. It's explained in the Gentoo GRUB Install howto. This is why I leave grub out of my world file. I upgraded grub and when I start it, it doesn't seem to see any disks. I am trying to run: root (hd0,2) setup (hd0) But hitting the TAB key at root ( doesn't report any options back to me. Why would that be? tab working fine here now used to not work here but grub worked fine nonetheless what results when you enter root (hd0,2)? I guess I'd better downgrade back to what I had prior until I figure that out... -- -M There are 10 kinds of people in this world: Those who can count in binary and those who cannot. -- gentoo-amd64@lists.gentoo.org mailing list -- gentoo-amd64@lists.gentoo.org mailing list
[gentoo-amd64] ext2, ext3, inodes, and grub
It appears that an up to date unaltered /etc/mke2fs.conf file will look
like:
[defaults]
base_features = sparse_super,filetype,resize_inode,dir_index,ext_attr
blocksize = 4096
inode_size = 256
inode_ratio = 16384
[fs_types]
small = {
blocksize = 1024
inode_size = 128
inode_ratio = 4096
}
floppy = {
blocksize = 1024
inode_size = 128
inode_ratio = 8192
}
news = {
inode_ratio = 4096
}
largefile = {
inode_ratio = 1048576
}
largefile4 = {
inode_ratio = 4194304
}
But the default, inode_size = 256, is currently being ignored.
running:
mke2fs /dev/sdb1
will produce an ext2 file system with inode_size = 128
running:
mke2fs -j /dev/sdb1 (or mkfs.ext3 or mkfs -t ext3)
will produce an ext3 file system with inode_size = 128
How this happens is a puzzle.
Running:
mke2fs -I 256 /dev/sdb1 or mke2fs -j -I 256 /dev/sdb1 will produce ext2 or
ext3 file systems with inode_size=256.
The /dev/sbd1, inode_size=256, file system so produced can be mounted and
will function normally.
However if I try to install grub 0.97.4 on it, I will see:
umount /dev/sdb1
grub
Probing devices to guess BIOS drives. This may take a long time.
GNU GRUB version 0.97 (640K lower / 3072K upper memory)
[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the
possible
completions of a device/filename. ]
grub root (hd1,0)
Filesystem type is ext2fs, partition type 0x83
grub setup (hd1)
Checking if /boot/grub/stage1 exists... no
Checking if /grub/stage1 exists... no
Error 2: Bad file or directory type
To fix this and other bugs, grub 0.97.5 is coming currently masked ~amd64.
Installing grub 0.97.5 does in fact allow grub to setup inode_size=256
ext2/ext3 file systems. (Even though they seem not to be being written just
now.)
grub 0.97.5 comes with a warning:
* Messages for package sys-boot/grub-0.97-r5:
* *** IMPORTANT NOTE: you must run grub and install
* the new version's stage1 to your MBR. Until you do,
* stage1 and stage2 will still be the old version, but
* later stages will be the new version, which could
* cause problems such as an unbootable system.
This seemed exciting since I have not always read all the messages produced
by major updates. After I emerged grub 0.97.5, I tried not running grub and
not reinstalling stage 1 and 2 before rebooting. Nothing bad happened.
However it might be ell to put a grub reinstall on the to do list as marking
grub 0.97.5 stable is supposed to be imminent and the next emerge -uND world
may bring it on.
--
gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] Re: boot Gentoo from USB key
- Original Message - From: Duncan [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Friday, May 02, 2008 7:22 AM Subject: [gentoo-amd64] Re: boot Gentoo from USB key Raffaele BELARDI [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Wed, 30 Apr 2008 08:43:53 +0200: In the process of building an amd64 diskless box, I am trying to make a bootable USB key with no success up to now. The first problem I encountered was related to ext2/vfat. I initially tried to format the key as ext2, but grub refuses to install on it. Even though I copied the /boot/grub/* directory into the key, and I see it is there, grub does not see it. The problem does not happen with vfat Still betting pen drive maker (or card reader maker) did some kind of equivalent to 'low level formatting'. . I think I might have come across the problem you experienced here. I'd put the chances at pretty good the below covers the problem here, but I believe the invisible USBkey @ boot issue is different, so you'll likely have to address it separately (but luckily there are plenty of posts with suggestions). If I'm correct you're running into the ext3 large inode issue. Briefly, old versions used 128 byte inodes, while newer versions use 256 byte inodes by default, in ordered to be ready for the improvements coming in ext4. The problem is that legacy grub doesn't support the larger inodes, and isn't being developed any longer so that isn't going to change, while new grub isn't even scheduled for format compatibility stability until late this year! One solution is a command line option to mke2fs as detailed in the article below. Or... There's a Gentoo patched grub-0.97-r5 that'll handle the new inodes hard masked for testing, but I don't believe it's even ~arch yet (I'm on the no-multilib profile here, where grub is masked and grub-static is used, so wouldn't see it go to ~arch and thus can't say for sure). Here's the article I just found detailing the issue in general. It's well worth reading but a word of warning. LinuxPlanet tends to be a bit ad-heavy... and weirdly formatted if you are using an ad-blocker (unless you use a custom filter to cut out the weirdness, as I do with privoxy). Still, for those using both grub and an ext3 /boot, it's DEFINITELY worth the read, as it may prevent (or in your case fix) some serious issues later (now, for you). http://www.linuxplanet.com/linuxplanet/tutorials/6480/1/ Meanwhile, here's the developer list thread (via gmane) asking for testing of the new version with the large-inode patch, among other fixes. http://comments.gmane.org/gmane.linux.gentoo.devel/55463 Finally, the Gentoo-grub ext3 large inodes bug: http://bugs.gentoo.org/show_bug.cgi?id=214563 An interesting find. Were the inodes for ext2 also defaulted to 256 or only those for ext3? This question relevant as Raffaele only talked about using ext2 and vfat partitions on the pen drive. In a quick search I found no indications. If ext2 inode structure was also changed much more should be heard about this. -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- gentoo-amd64@lists.gentoo.org mailing list -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] boot Gentoo from USB key
- Original Message -
From: Drake Donahue [EMAIL PROTECTED]
To: gentoo-amd64@lists.gentoo.org
Sent: Wednesday, April 30, 2008 2:03 PM
Subject: Re: [gentoo-amd64] boot Gentoo from USB key
- Original Message -
From: Raffaele BELARDI [EMAIL PROTECTED]
To: gentoo-amd64 gentoo-amd64@lists.gentoo.org
Sent: Wednesday, April 30, 2008 2:43 AM
Subject: [gentoo-amd64] boot Gentoo from USB key
In the process of building an amd64 diskless box, I am trying to make a
bootable USB key with no success up to now.
The first problem I encountered was related to ext2/vfat. I initially
tried to format the key as ext2, but grub refuses to install on it. Even
though I copied the /boot/grub/* directory into the key, and I see it is
there, grub does not see it. The problem does not happen with vfat.
So I worked around that and created two partitions in the key, a small
vfat for the /boot and a 2Gb ext2 for the /. I copied the stage3 into
the / with no problem. In the /boot I put the kernel image which I am
already using on the same box, for now with discs still connected. All
the modules are compiled in.
When I boot from the key, grub enters the shell (although I did create
the grub.conf and menu.1st, so I don't understand why it doesn't show
the menu). I manually specify the kernel file location and root
parameter:
kernel /linux-2.6.24-gentoo-r4 root=/dev/sdg1
boot
The kernel starts to load, but panics because it is unable to find the
root partition. When it stops it shows the available partitions, these
include all the hard disk partitions but no USB key partition. In fact,
if I omit the 'root' parameter from the grub shell the boot works fine
but it uses the hard disk root partition instead of the USB one.
From the log on the screen the USB controller seems correctly detected,
so I don't understand why it is not finding the root. While writing this
one idea comes to my mind, maybe it is failing because I attach the key
to a SDC/MMC/USB card reader? This evening I'll try to plug it into a
different USB slot.
Any other ideas welcome.
raffaele
--
gentoo-amd64@lists.gentoo.org mailing list
Other ideas and SWAGS:
This link may be useful:
http://www.bootdisk.com/pendrive.htm
Perhaps the pen drive manufacturer did you favors and added some control
software?
I had a similar problem with fdisk results that I attributed to the
helpful manufacturer putting some extra software on the drive to add
features for the windows user (the bootable flag would have disappeared
upon reboot, the pen drive would not appear in BIOS). I may have been
right. I used the HP utilities referenced in the link to rewrite the
recalcitrant pen drive into a psuedo floppy drive with linux on board (HP
provides a linux based windows computer troubleshooting tool!).
Instead of HP utilities, maybe, quoting:
Solution:
snipWhen you boot into a command shell, as root, simply pick the drive you
want to fill [with zeros], sdg presumed, and use the command:
Code:
dd if=/dev/zero of=/dev/sdg bs=1MWARNING! This will destroy ALL data on the
hard (pen) drive, all boot sector info and all data on all partitions. It
will not however render the disk useless, you simply have a clean disk that
only needs to have partitions created and a new boot sector installed, which
will happen when you install any OS including Linux or Windows. This is a
good way to clean up any bad partitions, viruses, botched installs or data
that you don't want to be seen (OK, it is theoretically possible to
forensically retrieve data after using this method, but not likely and not
doable by the average computer user) and it is simple to do with existing
GNU/Linux!
After verifying that I could boot the pen
drive as though it were a huge floppy, I rebooted to my hard drive and
used fdisk to delete existing partitions on the pen drive, created a
bootable partition, wrote the new partition table, exited fdisk, and
formatted it ext2. On reboot it showed as a bootable hard drive in BIOS.
Encouraged, I rebooted to the hard drive. Mounted the pen drive and copied
/boot from the hard drive to it. Create dummy directory on the pendrive:
mkdir {pendrive path}/pendrive
Keeping the problem simple, the machine had one sata hard drive, one ide
dvd, and the one pen drive.
The major problems at this point were identifying which (hd?) to use in
editing the grub.conf and in running grub itself.
umount {pendrive}
grub
root (hd0,1)
root (hd1,1)
find /pendrive
quit
As the pen drive first (0) partition was the only ext2 partition on the
machine, only one of the two commands would expose an ext2 filesystem; in
my case (hd1,1). Find should provide the same information.
If the pen drive is the selected boot drive for my motherboard it will be
(hd0) for bios and grub.
So the pen drive grub.conf edits to:
timeout 5
default 0
fallback 1
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
title USB Flash boot
root (hd0,0)
kernel (hd0,0)/boot/bzImage root=/dev/sdb1
Re: [gentoo-amd64] USB TV stick (wintv)
- Original Message - From: Drake Donahue [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Sunday, April 06, 2008 1:16 PM Subject: Re: [gentoo-amd64] USB TV stick (wintv) - Original Message - From: Paul Stear [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Sunday, April 06, 2008 12:22 PM Subject: [gentoo-amd64] USB TV stick (wintv) Hello all, Can anybody point me in the right direction so that I can get this TV stick set up and working. Thanks Paul -- This message has been sent using kmail with gentoo linux -- gentoo-amd64@lists.gentoo.org mailing list who made it and what model is it? Start here: http://gentoo-wiki.com/HOWTO_Setup_MythTV -- if USB questions: http://www.gentoo.org/doc/en/usb-guide.xml gentoo-amd64@lists.gentoo.org mailing list -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] USB TV stick (wintv)
- Original Message - From: Paul Stear [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Sunday, April 06, 2008 12:22 PM Subject: [gentoo-amd64] USB TV stick (wintv) Hello all, Can anybody point me in the right direction so that I can get this TV stick set up and working. Thanks Paul -- This message has been sent using kmail with gentoo linux -- gentoo-amd64@lists.gentoo.org mailing list who made it and what model is it? Start here: http://gentoo-wiki.com/HOWTO_Setup_MythTV -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] USB TV stick (wintv)
- Original Message - From: Paul Stear [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Sunday, April 06, 2008 1:27 PM Subject: Re: [gentoo-amd64] USB TV stick (wintv) On Sunday 06 April 2008, Drake Donahue wrote: - Original Message - From: Paul Stear [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Sunday, April 06, 2008 12:22 PM Subject: [gentoo-amd64] USB TV stick (wintv) Hello all, Can anybody point me in the right direction so that I can get this TV stick set up and working. Thanks Paul -- This message has been sent using kmail with gentoo linux -- gentoo-amd64@lists.gentoo.org mailing list who made it and what model is it? snip Hi, Thanks for the response its a Hauppauge winTV nova-T usb stick Paul -- Some specific guidance: http://www.mythtv.org/wiki/index.php/Hauppauge_WinTV_Nova-T_USB2 This message has been sent using kmail with gentoo linux -- gentoo-amd64@lists.gentoo.org mailing list -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] USB TV stick (wintv)
- Original Message - From: Drake Donahue [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Sunday, April 06, 2008 2:17 PM Subject: Re: [gentoo-amd64] USB TV stick (wintv) - Original Message - From: Paul Stear [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Sunday, April 06, 2008 1:27 PM Subject: Re: [gentoo-amd64] USB TV stick (wintv) On Sunday 06 April 2008, Drake Donahue wrote: - Original Message - From: Paul Stear [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Sunday, April 06, 2008 12:22 PM Subject: [gentoo-amd64] USB TV stick (wintv) Hello all, Can anybody point me in the right direction so that I can get this TV stick set up and working. Thanks Paul -- This message has been sent using kmail with gentoo linux -- gentoo-amd64@lists.gentoo.org mailing list who made it and what model is it? snip Hi, Thanks for the response its a Hauppauge winTV nova-T usb stick Paul -- Some specific guidance: http://www.mythtv.org/wiki/index.php/Hauppauge_WinTV_Nova-T_USB2 Better looking specific guidance: http://gentoo-wiki.com/HOWTO_Setup_Kernel/System_for_MythTV#Hauppauge_WinTV-Nova-T This message has been sent using kmail with gentoo linux -- gentoo-amd64@lists.gentoo.org mailing list -- gentoo-amd64@lists.gentoo.org mailing list -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] RE: BT8x8
- Original Message - From: Chris Brennan [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Saturday, February 16, 2008 2:43 PM Subject: Re: [gentoo-amd64] RE: BT8x8 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 xawtv: I know where to set grabdisplay, but I don't see an option for dga. Module: I will have to recompile my kernel for that as modules. When I had it as modules, it wasn't creating /dev/video0 xorg.corf: I'll fix v4l asap. reiserfs: how/where do I turn this option off? This is a kernel build option. Under make menuconfig - file systems - reiserfs support - [ ] Enable reiserfs debug mode uncheck and recompile kernel # # NOTICE: The contents of this e-mail and any attachments to it may # # contain privileged and confidential information from XaeroLimit # # Industries or its affiliates. This information is only for the viewing # # or use of the intended recipient. If you are not the intended recipient, # # you are hereby notified that any disclosure, copying, distribution or use # # of, or the taking of any action in reliance upon, the information # # contained in this e-mail, or any of the attachments to this e-mail, # # is strictly prohibited. If you have received this e-mail in error, # # please immediately notify the sender by replying to this message and # # delete it from your system. # # Volker Armin Hemmann wrote: On Samstag, 16. Februar 2008, Chris Brennan wrote: ### ## oh and: ReiserFS: hdh1: warning: CONFIG_REISERFS_CHECK is set ON ReiserFS: hdh1: warning: - it is slow mode for debugging. why don't you turn debugging of? it is really, really slow. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHtzzf8hUIAnGfls4RAlClAJ0SG9ZyRW9bTtKUC/XU38mCtOqKzwCeKkQv Prv4T55j0/EyJ3NTBUC64DA= =jhXG -END PGP SIGNATURE- -- gentoo-amd64@lists.gentoo.org mailing list -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] Problem with latest timezone update?
- Original Message - From: Mark Knecht [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Thursday, January 17, 2008 10:08 AM Subject: Re: [gentoo-amd64] Problem with latest timezone update? On Jan 17, 2008 2:15 AM, Nicolas Litchinko [EMAIL PROTECTED] wrote: Hi, On Wed, Jan 16, 2008 at 05:37:21PM -0800, Mark Knecht wrote: On Jan 16, 2008 4:56 PM, Drake Donahue [EMAIL PROTECTED] wrote: Thus etc-update and/or dispatch-conf can't change localtime; but can change whether localtime runs or not. Humm...seems like what you say is true but doesn't explain how emerge -DuN system changed the file. It was clearly changed since I could look inside with vi and compare to the Los_Angeles file and see that they were clearly different... There's a variable in /etc/conf.d/clock that controls whether or not /etc/localtime should be updated when a new version of sys-libs/timezone-data is merged: TIMEZONE. If this variable is set, the specified timezone data file is copied over /etc/localtime. as you can read in /etc/conf.d/clock: # Select the proper timezone. For valid values, peek inside of the # /usr/share/zoneinfo/ directory. For example, some common values are # America/New_York or EST5EDT or Europe/Berlin. If you want to # manage /etc/localtime yourself, set this to . If TIMEZONE is not set, /etc/localtime is not updated by sys-libs/timezone-data. However, if TIMEZONE is set to an invalid value, then /etc/localtime is overwritten by the Factory timezone data file. etc-update has probably changed the value of this variable after a baselayout update. Then a timezone-data update used the wrong value to update /etc/localtime. In your, case, the value of TIMEZONE should be TIMEZONE=America/Los_Angeles. -- Nicolas Litchinko BOFH excuse #348: We're on Token Ring, and it looks like the token got loose. -- gentoo-amd64@lists.gentoo.org mailing list OK, I buy it. My setup was missing the underscore: dragonfly ~ # cat /etc/conf.d/clock | grep TIMEZONE TIMEZONE=America/LosAngeles dragonfly ~ # However time on the machine has been fine for the 2 years we've had the machine. Has this been wrong the whole time and I jsut got lucky or did someone possibly change the formatting? Postulated sequence: 2 years ago, most probably, TIMEZONE=PST8PDT was used. All went well until a recent oops with etc-update or dispatch-conf, an inadvertent CLOCK=UTC, which caused the clock to start keeping universal time. A similar problem discussed here reported a solution which included using TIMEZONE=America/New_York (I think, maybe America/Los_Angeles, maybe ...). Having the same universal time problem, you adopted the geographic idea but were then bitten by a typo. Of note, the old TIMEZONE=EST5EDT continues to work fine here. Thanks for the clarification! Cheers, Mark -- gentoo-amd64@lists.gentoo.org mailing list -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] Problem with latest timezone update?
- Original Message -
From: Mark Knecht [EMAIL PROTECTED]
To: gentoo-amd64@lists.gentoo.org
Sent: Wednesday, January 16, 2008 8:37 PM
Subject: Re: [gentoo-amd64] Problem with latest timezone update?
On Jan 16, 2008 4:56 PM, Drake Donahue [EMAIL PROTECTED] wrote:
- Original Message -
From: Steev Klimaszewski [EMAIL PROTECTED]
To: gentoo-amd64@lists.gentoo.org
Sent: Wednesday, January 16, 2008 6:01 PM
Subject: Re: [gentoo-amd64] Problem with latest timezone update?
snip
Except that neither etc-update nor dispatch-conf touch
the /etc/localtime file...
True, but...
The files that are (maybe) affected directly by etc-update and/or
dispatch-conf are /etc/conf.d/clock and /etc/init.d/clock. ('maybe' is
used
because: an emerge update must have affected one or both files;
etc-update
and/or dispatch-conf must have been invoked by the user; the user must
have
chosen action that resulted in a change to one or both files.
/etc/conf.d/clock is the configuration file for /etc/init.d/clock.
When /etc/init.d/clock runs (normally at boot), /etc/conf.d/clock is
read.
If CLOCK=UTC is not set in /etc/conf.d/clock,
UTC was set...
Now CLOCK=LOCAL ?
the option --localtime is
used and TBLURB=Local Time is set.
The /etc/localtime file is a copy of one of the binary files in
/usr/share/zoneinfo made by the system installer
installer == Mark, me the guy who built the system, correct?
yes.
initially; it is subject to
update by repeating the manual copy process anytime after system install.
Which is what I did today to fix this problem.
Thus etc-update and/or dispatch-conf can't change localtime; but can
change
whether localtime runs or not.
Humm...seems like what you say is true but doesn't explain how emerge
-DuN system changed the file. It was clearly changed since I could
look inside with vi and compare to the Los_Angeles file and see that
they were clearly different...
Probably the previous /etc/localtime file was a copy of PST8PDT.
IIRC the geographic file names are relatively recent in origin.
If the old localtime had PST8PDT and the new had Los_Angeles in the few
readable characters the difference is explained.
Alternatively:
The start and end of US daylight savings time changed effective 2007-2008.
This resulted in an update to PST8PDT and its cousins ( to Los_Angeles and
its geographic cousins also, if they existed before the change). The
timezone-data ebuild also has a series of more recent bugfixes.
As Nicholas explains the /sys-libs/timezone-data update ebuild should have
updated /usr/share/zoneinfo files to new versions.
The /sys-libs/timezone-data update ebuild should then have copied the new
version of the file named in /etc/conf/clock's TIMEZONE= statement from
/usr/share/zoneinfo to /etc/localtime.
If it did not succeed in updating /etc/localtime because TIMEZONE= was
blank, invalid, or not set, the old /etc/localtime would have contained
readable characters: ' Local time zone must be set -- see zic manual page'.
Thanks,
Mark
--
gentoo-amd64@lists.gentoo.org mailing list
--
gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] Problem with latest timezone update?
OOPS and duh! Just reread your original! You want to be on universal time! Abject apologies and nevermind. As I read /etc/init.d/clock, setting CLOCK=UTC should make /etc/localtime irrelevant and unused. If you are still having problems after the Los_Angeles change maybe TIMEZONE=UTC ? -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] Problem with latest timezone update?
- Original Message -
From: Steev Klimaszewski [EMAIL PROTECTED]
To: gentoo-amd64@lists.gentoo.org
Sent: Wednesday, January 16, 2008 6:01 PM
Subject: Re: [gentoo-amd64] Problem with latest timezone update?
snip
Except that neither etc-update nor dispatch-conf touch
the /etc/localtime file...
True, but...
The files that are (maybe) affected directly by etc-update and/or
dispatch-conf are /etc/conf.d/clock and /etc/init.d/clock. ('maybe' is used
because: an emerge update must have affected one or both files; etc-update
and/or dispatch-conf must have been invoked by the user; the user must have
chosen action that resulted in a change to one or both files.
/etc/conf.d/clock is the configuration file for /etc/init.d/clock.
When /etc/init.d/clock runs (normally at boot), /etc/conf.d/clock is read.
If CLOCK=UTC is not set in /etc/conf.d/clock, the option --localtime is
used and TBLURB=Local Time is set.
The /etc/localtime file is a copy of one of the binary files in
/usr/share/zoneinfo made by the system installer initially; it is subject to
update by repeating the manual copy process anytime after system install.
Thus etc-update and/or dispatch-conf can't change localtime; but can change
whether localtime runs or not.
--
gentoo-amd64@lists.gentoo.org mailing list
--
gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] Problem with latest timezone update?
- Original Message - From: Mark Haney [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Tuesday, January 15, 2008 10:22 AM Subject: [gentoo-amd64] Problem with latest timezone update? Okay, here's something I can't seem to figure out. My laptop time doesn't want to stay sync'd. I always run ntpd at boot time to keep it in sync, but now, when I boot without an ethernet cable hooked up, it's over 5 hours off. It didn't do this until I updated the timezone just after Christmas. /etc/conf.d/clock is set to my timezone (EST5EDT) and /etc/localtime is symlinked to the correct timezone. I thought maybe the BIOS clock was wrong, but it's not 5 hours off, maybe a minute or so. I tried setting the HWclock to system time and that didn't fix it. Any ideas on what else to try? Could it be this simple? Quoting: # /etc/conf.d/clock # Set CLOCK to UTC if your system clock is set to UTC (also known as # Greenwich Mean Time). If your clock is set to the local time, then # set CLOCK to local. Note that if you dual boot with Windows, then # you should set it to local. CLOCK=local -- Recedite, plebes! Gero rem imperialem! Mark Haney Sr. Systems Administrator ERC Broadband (828) 350-2415 Call (866) ERC-7110 for after hours support -- gentoo-amd64@lists.gentoo.org mailing list -- gentoo-amd64@lists.gentoo.org mailing list
Re: [gentoo-amd64] Re: NVIDIA 100.14.19 + xorg-server 1.4.0.90 + xorg-x11 7.3 = blackscreen after every restart
- Original Message - From: Enrico Weigelt [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Tuesday, January 01, 2008 7:18 PM Subject: Re: [gentoo-amd64] Re: NVIDIA 100.14.19 + xorg-server 1.4.0.90 + xorg-x11 7.3 = blackscreen after every restart * Hemmann, Volker Armin [EMAIL PROTECTED] wrote: For this year I've already wasted too much resources on that. Maybe I'll have a try in a few month. 3D stuff isnt't that important for me - for 2D stuff the free driver works very fine. yeah, just copying an ebuild and replacing nv with nvidia in xorg.conf costs so much time and is so hard to do. Whining on the other hand does not take any time at all. It's more than that. Rebuilding the kernel, loosing fb and ovz, etc. I prefer spending that amount of time on disassambling the binary module ... ;-o BTW: the ebuild conflicts between kernel and nvidia-drivers are also annoying. The kernel parts should be handled differently. what are you talking about? conflicts? kernel parts? which kernel parts handled by what and why? The problem comes from NV's (broken) package. Their sanity checks seem to go against the *running* kernel, instead the one to build for. So, in my case, it denies compiling, as the currently running kernel has rivafb (but the target kernel won't). Package is not broken. It is designed to install and activate kernel modules (while running) and to modify the kernel module boot load list so of course it goes against the running kernel. (which must be the same as the kernel pointed at by /usr/src/linux. You should read http://www.gentoo.org/doc/en/nvidia-guide.xml and http://gentoo-wiki.com/HOWTO_nVidia_Drivers carefully. You need to rebuild your kernel to eliminate the rivafb (rivafb obsolete on all gpu newer than riva128). And eliminate nvidiafb if you did that also. These two modules are documented as preventing proper function of nvidia-drivers. VESA VGA graphics support is the choice you should have for FB support. Quoting: Kernel Configuration As mentioned above, the nVidia kernel driver installs and runs against your current kernel. It builds as a module, so it makes sense that your kernel must support the loading of kernel modules. If you used genkernel all to configure the kernel for you, then you're all set. If not, double check your kernel configuration so that this support is enabled: Code Listing 3.1: Enabling the Loading of Kernel Modules Loadable module support --- [*] Enable loadable module support You also need to enable Memory Type Range Register in your kernel: Code Listing 3.2: Enabling MTRR Processor and Features --- [*] MTRR (Memory Type Range Register) support Also, if you have an AGP graphics card, you can optionally enable agpgart support to your kernel, either compiled in or as a module. If you do not use the in-kernel agpgart, then the drivers will use their own agpgart implementation, called NvAGP. On certain systems, this performs better than the in-kernel agpgart, and on others, it performs worse. You will need to evaluate this on your own system to get the best performance. If you are unsure what to do, use the in-kernel agpgart: Code Listing 3.3: Enabling agpgart Device Drivers --- Character devices --- * /dev/agpgart (AGP Support) Note: On amd64, the IOMMU controls the agpgart setting. Arch-specific notes Important: For x86 and AMD64 processors, the in-kernel driver conflicts with the binary driver provided by nVidia. If you will be compiling your kernel for these CPUs, you must completely remove support for the in-kernel driver as shown: Code Listing 3.4: Remove the in-kernel driver Device Drivers --- Graphics Support --- nVidia Framebuffer Support nVidia Riva support A good framebuffer alternative is VESA: Code Listing 3.5: Enable VESA support Device Drivers --- Graphics Support --- * VESA VGA graphics support cu -- - Enrico Weigelt== metux IT service - http://www.metux.de/ - Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ - -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] NVIDIA 100.14.19 + xorg-server 1.4.0.90+xorg-x11 7.3 = blackscreen after every restart
- Original Message - From: B Vance [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Saturday, December 22, 2007 9:23 AM Subject: Re: [gentoo-amd64] NVIDIA 100.14.19 + xorg-server 1.4.0.90+xorg-x11 7.3 = blackscreen after every restart After the system restarts, it shows [1] nvidia * [2] xorg-x11. I'm hoping that the asterix by nvidia indicates that it isn't dropping the opengl setting from nvidia that is causing this. B Vance Apologies for my top posting earlier. You might try finding and renaming every instance of xorg.conf on your machine to something else and then reboot the machine. If no xorg.conf exists, the current X will run through its own script (not named xorg.conf) and usually automagically produce a working windowed environment (or fail). I believe that if you have an old xorg.conf, emerge nvidia-drivers will edit it retaining part, deleting part, and adding part. If this is correct the possibility exists that the edited xorg.conf will have internal inconsistencies. BTW, being a slob I use the terms terminal, console, and command line interface pretty much interchangeably (sorry again). I presume you boot directly to a windowed environment (desktop) when all goes well. And that currently the boot gets to the point of trying to start X, fails, and drops you to a command line prompt at which you login and then type: emerge nvidia-drivers, after the emerge nvidia-drivers, you type some form of a 'startx' or 'start a display manager command' which then works to take you to a desktop. If these assumptions are coreect, an eselect opengl list after the crash and before the emerge nvidia-drivers could be informative. After emerge nvidia-drivers the list should be as you found it and it should still be that way for the next start of X. On Fri, 2007-12-21 at 18:00 -0500, Drake Donahue wrote: After a failure and while in console, what output does: eselect opengl list give? - Original Message - From: B Vance [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Friday, December 21, 2007 4:41 PM Subject: Re: [gentoo-amd64] NVIDIA 100.14.19 + xorg-server 1.4.0.90 +xorg-x11 7.3 = blackscreen after every restart The only version that I haven't tried it with is Nvidia-drivers 100.14.23, I try to avoid hard masked ebuilds if at all possible. The last driver that worked properly was 1.0.9639, with the previous stable ABI of xorg-server. I'm assuming that the 169.04 you're referring to is Nvidia-settings. I haven't tried the masked version yet. Would that have this kind of effect? I thought it just modified xorg.conf if you ran it. Thanks for the info and assistance. B. Vance On Fri, 2007-12-21 at 22:06 +0100, Hemmann, Volker Armin wrote: Hi, what about 169.04 or the latest releasse .07? -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] NVIDIA 100.14.19 + xorg-server 1.4.0.90 +xorg-x11 7.3 = blackscreen after every restart
After a failure and while in console, what output does: eselect opengl list give? - Original Message - From: B Vance [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Friday, December 21, 2007 4:41 PM Subject: Re: [gentoo-amd64] NVIDIA 100.14.19 + xorg-server 1.4.0.90 +xorg-x11 7.3 = blackscreen after every restart The only version that I haven't tried it with is Nvidia-drivers 100.14.23, I try to avoid hard masked ebuilds if at all possible. The last driver that worked properly was 1.0.9639, with the previous stable ABI of xorg-server. I'm assuming that the 169.04 you're referring to is Nvidia-settings. I haven't tried the masked version yet. Would that have this kind of effect? I thought it just modified xorg.conf if you ran it. Thanks for the info and assistance. B. Vance On Fri, 2007-12-21 at 22:06 +0100, Hemmann, Volker Armin wrote: Hi, what about 169.04 or the latest releasse .07? -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] firefox-bin crashing a few times every day
- Original Message -
From: Mark Knecht [EMAIL PROTECTED]
To: gentoo-amd64@lists.gentoo.org
Sent: Monday, November 12, 2007 1:35 PM
Subject: Re: [gentoo-amd64] firefox-bin crashing a few times every day
On Nov 12, 2007 12:36 AM, Beso [EMAIL PROTECTED] wrote:
2007/11/12, Mark Knecht [EMAIL PROTECTED]:
On Nov 11, 2007 2:52 PM, Beso [EMAIL PROTECTED] wrote:
SNIP
the system configs are normal too the only thing that i can
advise
you
to do is try the mozilla-firefox instead of mozilla-firefox-bin.
don't
uninstall the bin since it can coexhist with the non bin package
try
that (some hours of compilation) and see what it does.
Hummmozilla-firefox hasn't been much of an option for me in the
past. Too many problems with web-based media not playing without all
the wincodecs stuff. Maybe this has improved? I've used firefox-bin
really to get Flash, Java and wincodecs. I don't care which one I use.
I just want a good user experience when I'm browsing around and run
into something interesting.
the only stuff on amd64 that needs some more things to do is:
1. firefox 32 bit plugins
2. win32codecs.
at the end of the email i'll tell you how to install them and make them
work
flawlessly.
I really only run the AMD64 version of Gentoo because a few years ago
when I bought this system it seemed like an interesting thing to try
out and at the time I had a Linux laptop running 32-bit Gentoo in case
I ran into problems. Then a guy on the web found me and wanted to buy
my 2 year old laptop for more than I paid for it (he wanted a backup
machine) so I sold it and no longer have that backup.
As an everyday, normal desktop user-type I really don't know that
running 64bit Gentoo offers me any advantages and has shown to have
significant disadvantages, at least the way I build the comparison
list. I wonder in what usage model do people here see a measurable
advantage running 64-bit over 32-bit Gentoo?
it depends. for example i like to have the software that runs on my
machine
to use all of its capabilities.
I've stuck with it for a long time, and I hate to give up, but maybe
it's time to just pack it in and rebuild the machine.
I'll keep poking around at this.
for win32codecs you just have to emerge the win32codecs and you've done.
there's really no other real thing to do.
for the mediaplayer plugin install mplayer + mplayer-plugin and you'll
have
firefox run it without issues. mplayer is also useful for some videos
that
xine plays in the wrong way (mainly h264 with ac3 that has some issues
with
the subtitles and mplayer doesn't).
install mozilla-firefox (not bin).
as for java and firefox: install emul-linux-java (that you already have)
for flash and firefox: install netscape-flash and nspluginwrapper and
then
do:
nspluginwrapper -v -i /usr/lib32/nsbrowser/plugins/libflashplayer.so
restart your mozilla-firefox (not the bin version). and you should be
able
to run flash, java, mediaplayer plugins on firefox amd64.
if you still have problems just ask.
Thanks Beso, and Jeffery also.
OK, I'm doing a little catch up on system maintenance. I did an emerge
-DuN mozilla-firefox and picked up a few new updates. I did a
revdep-rebuild on some libraries and it looks like I'm ready to roll
with Firefox itself.
Now, should I rebuild Firefox? Here's how it is currently built:
lightning ~ # emerge -pvDuN mozilla-firefox
These are the packages that would be merged, in order:
Calculating dependencies... done!
Total: 0 packages, Size of downloads: 0 kB
lightning ~ # emerge -pv mozilla-firefox
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] www-client/mozilla-firefox-2.0.0.9 USE=gnome java
-bindist -debug -filepicker -ipv6 -mozdevelop -moznopango
-restrict-javascript -xforms -xinerama -xprint LINGUAS=-af -ar -be
-bg -ca -cs -da -de -el -en_GB -es -es_AR -es_ES -eu -fi -fr -fy
-fy_NL -ga -ga_IE -gu -gu_IN -he -hu -it -ja -ka -ko -ku -lt -mk -mn
-nb -nb_NO -nl -nn -nn_NO -pa -pa_IN -pl -pt -pt_BR -pt_PT -ro -ru -sk
-sl -sv -sv_SE -tr -zh -zh_CN -zh_TW 0 kB
Total: 1 package (1 reinstall), Size of downloads: 0 kB
lightning ~ #
QUESTION: Will the mplayerplug-in support Yahoo Video?
http://video.yahoo.com/
That's telling me I need Flash 8.0. I have Flash 9.0 installed so I'm
not clear what the problem is here:
lightning ~ # eix -I flash
[I] net-www/netscape-flash
Available versions: [M]7.0.68 {M}9.0.48.0!m 9.0.48.0-r1!m
{M}(~)9.0.60.0_beta082207!m (~)9.0.60.0_beta100107!m {debug}
Installed versions: 9.0.60.0_beta100107!m(05:54:44 PM 10/19/2007)
Homepage:http://labs.adobe.com/technologies/flashplayer9/
Description: Adobe Flash Player
lightning ~ #
type about:plugins in the firefox url window and enter, see if Shockwave
Flash is listed followed by File name npwrapper.libflashplayer.so --you
haven't mentioned installing nspluginwrapper
thanks,
Re: [gentoo-amd64] firefox-bin crashing a few times every day
- Original Message - From: Mark Knecht [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Monday, November 12, 2007 4:03 PM Subject: Re: [gentoo-amd64] firefox-bin crashing a few times every day Hi all, Just a thanks up front for all your help so far. Possibly the crashing is behind me. I appreciate all the attention. Now, on to Flash and Java... On Nov 12, 2007 11:32 AM, Drake Donahue [EMAIL PROTECTED] wrote: SNIP type about:plugins in the firefox url window and enter, see if Shockwave Flash is listed followed by File name npwrapper.libflashplayer.so --you haven't mentioned installing nspluginwrapper Drake, Indeed, somewhere along the way Beso suggested removing things to look for what might be causing the crash. nspluginwrapper was one I had removed. I reinstalled it and now going to the video.yahoo.com page doesn't cause a warning anymore. However when I try to play any video I see the first couple of frames and then I see a gray box drawn over the top. Audio continues as the video plays but I no longer see any video. Lest I sound like I'm complaining I do think we're making progress. I rebooted the machine and started the 64-bit browser. Always before if I created a second tab and tried to rearrange tabs the browser crashed. It no longer does that. (Maybe simply because I;m using the 64-bit version. I don't know...) I wonder if I should be deleting the .mozilla directory to properly test this stuff? OK, so here's what I'm currently seeing in about:plugins: Shockwave Flash npwrapper.libflashplayer.so Helix DNA Plugin: RealPlayer G2 Plug-In Compatible npwrapper.nphelix.so NPAPI Plugins Wrapper 0.9.91.4 npwrapper.so VLC Multimedia Plugin libvlcplugin.so QuickTime Plug-in 6.0 / 7 mplayerplug-in-qt.so mplayerplug-in 3.45 mplayerplug-in.so I think that you have now gotten Firefox to connect to a Flash plug-in; however the plugin has a problem. Suggestion: Visit http://www.adobe.com/shockwave/download/static/Linux/ShockwaveFlash/English.html and download Option 1, the tar.gz file extract libflashplayer.so from the downloaded file and place it in /opt/netscape/plugins ( in other words, create /opt/netscape/plugins/libflashplayer.so ) then run nspluginwrapper -i /opt/netscape/plugins/libflashplayer.so This should produce a nice new up to date file: /usr/lib64/nsbrowser/plugins/npwrapper.libflashplayer.so for firefox to use. This is based on how i got flash to work in 64 bit firefox (including at video.yahoo.com). Btw my experience with helix/realplayer has been more positive than Beso's. I emerged realplayer and the nspluginwrapper in sequence followed by the flash steps above and all went well. My only real player complaint is not bewing able to get full screen. May be related to not doing a java plugin. Currently if I go to this page Java isn't working at all. http://www.prophet.net/analyze/javacharts.jsp Not my biggest problem but I need to solve it. STATUS: 1) Firefox crashing - Possibly fixed. Thanks! 2) Flash video - gray box. This is what I'd like to solve first if possible. 3) Java - not seen by the browser. Have done very little work on it yet but building a little on Jeffery's idea I tried to do it with the currently installed version of Java: lightning ~ # slocate libjavaplugin_oji.so /opt/emul-linux-x86-java-1.6.0.03/plugin/i386/ns7/libjavaplugin_oji.so /opt/emul-linux-x86-java-1.6.0.03/plugin/i386/ns7-gcc29/libjavaplugin_oji.so lightning ~ # [EMAIL PROTECTED] ~ $ ls -la .mozilla/plugins ls: cannot access .mozilla/plugins: No such file or directory [EMAIL PROTECTED] ~ $ So I have no .mozilla/plugins directory to build the link. I tried adding a plugins directory and creating a link as shown but the Prophet web site still says no Java. [EMAIL PROTECTED] ~/.mozilla/plugins $ ls -la total 12 drwxr-xr-x 2 mark users 4096 2007-11-12 12:56 . drwx-- 4 mark users 4096 2007-11-12 12:56 .. lrwxrwxrwx 1 mark users 70 2007-11-12 12:56 libjavaplugin_oji.so - /opt/emul-linux-x86-java-1.6.0.03/plugin/i386/ns7/libjavaplugin_oji.so [EMAIL PROTECTED] ~/.mozilla/plugins $ I used the first link but maybe that's wrong since it points at the emul-linux directory? Thanks, Mark -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] firefox-bin crashing a few times every day
- Original Message - From: Mark Knecht [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Monday, November 12, 2007 7:35 PM Subject: Re: [gentoo-amd64] firefox-bin crashing a few times every day snip Java: Well worth reading and doing as they tell you: http://www.gentoo.org/proj/en/java/java-upgrade.xml http://www.gentoo.org/doc/en/java.xml A major key point the second reference makes, which can be confirmed at the Sun web site, -- There is no java plugin for 64 bit mozilla browsers. Unfortunately nspluginwrapper cannot handle java 32 bit plugins. So-- You can run the Konqueror browser which does not need a plugin but uses the java virtual machine directly. You can use mozilla-firefox-bin with emul-linux-x86-java as the java plugin. Konqueror worked on your analyze site some months ago; being a gnome I have not retried more recently. I did emerge mozilla-firefox-bin followed by emerging emul-linux-x86-java. Automagically firefox-bin picked up helix(real player), flash, and java plugins. The first two plugins were on board from the actions described earlier which used nspluginwrapper to install them in 64 bit firefox. Firefox-bin displays jsp pages at www.prophet.net very well. Were I in your shoes I would do the updating, probably including kernel, unmerge browsers and plugins, do the java references above, emerge firefox-bin, emul-linux-x86-java, realplayer, netscape-flash. Check operation of firefox-bin. If flash failed to load up or fails to work, unmerge it, and use the direct download and manual install method discussed on the download site. Thanks, Mark -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] emerge --sync failed
- Original Message - From: Paul Stear [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Monday, October 29, 2007 12:15 PM Subject: Re: [gentoo-amd64] emerge --sync failed On Monday 29 October 2007, Beso wrote: please use names and not ip addresses remove 64.127.121.98 and add in its place rsync.gentoo.org. the rsync server rotates so the simple ip might not work. remove it and use rsync.gentoo.org and use that. and try not rsyncing more than once per 24hours or you can be temporary banned snip I am not using ip addresses. (I think). I thought that rsync reads the mirror sites from make.conf, this is mine. GENTOO_MIRRORS=http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ ftp://mirror.qubenet.net/mirror/gentoo/ ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo http://pandemonium.tiscali.de/pub/gentoo/; Would rsync itself be using ip addresses? the line Starting rsync with rsync://64.127.121.98/gentoo-portage... is produced after dns resolution so yes it is. mirror choices 1 and 4 above are currently dead when I try them, choices 2 and 3 are responding to my browser. Suggest you remove the GENTOO_MIRRORS= line from /etc/make.conf If there is a lot of turbulence in the rsync servers near you, your mirror select choices and/or your dns cache values may be overtaken by events and be invalid today although good yesterday. thanks Paul -- This message has been sent using kmail with gentoo linux -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] Re: gnome installation problem: unreslved references in the gst libraries
- Original Message - From: Nadav Horesh [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Wednesday, October 10, 2007 1:13 AM Subject: RE: [gentoo-amd64] Re: gnome installation problem: unreslved references in the gst libraries Thank you for the detailed answer. I set the compilation flags to the recommended (-O2 -march=k -pipe) and the make option to J1, re-emerged the whole gstreamfriends packages. But it did not help. It looks that the problem is that when trying to emerge media-related gnome packages they are not linked against the right gstxxx libraries. maybe with the conservative flags and a lot of time try emerge -uNDe gnome ?? Nadav. N.B. 1. I am a speed freak, thus I use XFCE. I use the gnome package mainly for its utilities. 2. I did use your recommended flags as you mentioned. Please continue to educate us. -Original Message- From: news on behalf of Duncan Sent: Tue 09-Oct-07 12:05 To: gentoo-amd64@lists.gentoo.org Subject: [gentoo-amd64] Re: gnome installation problem: unreslved references in the gst libraries Nadav Horesh [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Tue, 09 Oct 2007 08:55:16 +0200: I have an ongoing problem with gnome installation started somewhere in one of the gnome-2.14.x upgrades, and it became worse on every upgrade till it prevented the upgrade to the recent gnome version (with a serious side effect of preventing upgrade to python 2.5.1). The problem is that in some stage of the build it stops because of an unresolved reference to some routine in the gstreamerfriends libraries. It is not a problem of a specific function/library because: 1. At different versions of gnome I got different unresolved link. 2. At the last upgrade, I added a (gstxxx) library that contained the missing link, what led to error of another missing link in a gstxxx library. I tried revdep-rebuild at several stages but it did not help. My questions are: 1. Is there something wrong in my configuration files that might couse the problem? 2. Is there a way to rebuild the whole gnome package from scratch? CFLAGS=-march=k8 -O2 -pipe -frename-registers -fweb -freorder-blocks -funit-at-a-time -ftree-pre -fgcse-sm -fgcse-las -fgcse-after-reload -fmerge-all-constants -mfpmath=sse -msse3 -m3dnow -ftree-vectorize -falign-functions=64 -fomit-frame-pointer CXXFLAGS=-march=k8 -Os -pipe -frename-registers -fweb -freorder-blocks -funit-at-a-time -ftree-pre -fgcse-sm -fgcse-las -fgcse-after-reload -fmerge-all-constants -combine -mfpmath=sse -msse3 -ftree-vectorize MAKEOPTS=-j2 USE=[snip] gstreamer [snip] Revdep-rebuild can help so trying it was a good idea, but doesn't always help if there's something else wrong. FWIW, personally, as an admitted control freak when it comes to the desktop I choose to run, I prefer KDE's exposure of options, and despise GNOME's lack of them, so you won't find GNOME on my system and I'm not familiar with it, so there's little I can help if the problem turns out to be GNOME specific. However, it's quite possible the problem is generic enough that the following general hints and techniques may be of help. CFLAGS/CXXFLAGS: Some (but not all) of those C(XX)FLAGS look pretty close to mine. There's nothing wrong with running a big string like that, as long as you understand it may cause problems with some ebuilds, and are willing to try recompiling with something simpler if you do run into issues. In particular -combine doesn't work well at all with CXXFLAGS, and still occasionally (altho much less frequently) causes issues with CFLAGS as well. As I mentioned, some of your flags look like mine, and you may have taken that flag from a discussion here some months ago. Only however it happened, it appears you have -combine in your CXXFLAGS instead of your CFLAGS. I'd reverse that. The problem I've run into is that while -combine is in theory safe for both CFLAGS and CXXFLAGS, because gcc knows when it can't be used (with exceptions for one thing, and they are pretty common in C++/CXX code, thus it's generally not worth even trying there), when gcc removes it, it spits a warning about it. Some of the configure scripts are setup to interpret any warning as an error, and thus decide that whatever they were testing for with that test-compile doesn't work on the system in question. At least in some cases, that causes them to turn OFF something that turns out to be needed later on, thus causing the problem to show up NOT by stopping the configure, but later in the process, during the compile or linking steps. So... try removing -combine from your CXXFLAGS (where as I said gcc normally turns it off anyway), and if you want to continue to use it (I use it), put it in CFLAGS instead. However, the bigger picture message is that sometimes, you may need to try compiling without some of the stuff in your C(XX)FLAGS. You can try one of two things. If you just want to get it to work, or want to
Re: [gentoo-amd64] Re: Disk boot order in grub
- Original Message - From: Duncan [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Thursday, August 30, 2007 9:07 AM Subject: [gentoo-amd64] Re: Disk boot order in grub snip and Duncan opined: Any insights into why nobody seems to be doing the LiveCD/DVD GRUB boot now, and why everyone's using ISOLinux instead? Is it just that ISOLinux is the tried and true method that everyone was using before GRUB became an option, and new guys are simply copying stuff from other LiveCDs that obviously works? Seems to me the direct-boot emulation-less way would be MUCH simpler and more flexible, so why isn't everyone (or even a suitable number of anyones) using it? I've on my list of things to do to go ask the Gentoo releng team as well. Why aren't /they/ using grub, since it's the default once the system is installed. Seems it would be more efficient than shipping ISOLinux and then using it for nothing other than the CD/DVD boot, since grub could at least potentially be dual-purposed both to booting the CD, and to installing directly from there to the new system, as well. The Gparted LiveCD has switched from isolinux to grub sometime in the last few months. Perhaps a trend is starting? The grub boot menu on this latest Gparted LiveCD does what I set out to do when I got into writing a grub boot cd. In explanation, it will act as a rescue CD with premade menu choices that will boot the first hard drive MBR, first hard drive's first, second, third, or fourth partition, second hard drive MBR. or the second hard drive's first partition. Thus, without advertising it, the Gparted gang have produced a grub rescue cd. The only lack is premade menu entry(ies) to setup grub on the hard drive(s). However dropping from the gparted boot menu into the command line to type : root (hd0,0) setup (hd0) with the knowledge that BIOS and grub are in agreement as to which drive is hd0 does not seem to be a big deal. Clonezilla, which claims Norton ghost type powers to clone drives and make drive images (including over the network) is also now on the Gparted LiveCD. Gparted LiveCD is really really on my must have list with this edition. -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] Re: Disk boot order in grub
- Original Message - From: Duncan [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Thursday, August 30, 2007 9:07 AM Subject: [gentoo-amd64] Re: Disk boot order in grub Drake Donahue [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Wed, 29 Aug 2007 15:34:03 -0400: So if you could writeup a brief HOWTO or at least some notes on the process and what did and didn't work, put it up somewhere and post a link to it (or post it here in entirety if not too big), I'd be VERY interested. Even just posting the ISO somewhere where I can download it and study the layout would be useful. Attached are scripts. The annotated script explains what is mostly obvious. I placed the mkgrubcd file in my home directory, made it owned by my username, made it executable, ran it using /home/drake/mkgrubcd terminal command and by doubleclick in the gui. After it runs a directory iso and a file grub.iso will appear in your home directory. grub.iso is ready to write to a blank cd. The directory, iso, will contain a near clone of the current system's /boot and subdirectories. Note you can see the code before you run it. :) Any insights into why nobody seems to be doing the LiveCD/DVD GRUB boot now, and why everyone's using ISOLinux instead? Is it just that ISOLinux is the tried and true method that everyone was using before GRUB became an option, and new guys are simply copying stuff from other LiveCDs that obviously works? Seems to me the direct-boot emulation-less way would be MUCH simpler and more flexible, so why isn't everyone (or even a suitable number of anyones) using it? I like your theory but deny any knowledge. That is how I ended up emulating and isolinux. I've on my list of things to do to go ask the Gentoo releng team as well. Why aren't /they/ using grub, since it's the default once the system is installed. Seems it would be more efficient than shipping ISOLinux and then using it for nothing other than the CD/DVD boot, since grub could at least potentially be dual-purposed both to booting the CD, and to installing directly from there to the new system, as well. -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- [EMAIL PROTECTED] mailing list mkgrubcdannotatedfile Description: Binary data mkgrubcd Description: Binary data
Re: [gentoo-amd64] Re: Disk boot order in grub
- Original Message -
From: Peter Humphrey [EMAIL PROTECTED]
To: gentoo-amd64@lists.gentoo.org
Sent: Tuesday, August 28, 2007 10:43 AM
Subject: Re: [gentoo-amd64] Re: Disk boot order in grub
On Tuesday 28 Aug 2007, I wrote:
So now I have the BIOS disk order, the boot-time grub disk order, the
device.map file order and the grub on-line disk order all the same. That
must be the end of the exercise, I hope.
Also, I forgot to say, the disk order implied in grub.conf.
Quote from earlier:
The BIOS setup program gives me three pages where I can set values. The
first
is the IDE setup page, where I can mark the several IDE and SATA interfaces
as active (auto) or inactive; I can also say whether IDE or SATA is to be
the
first disk to boot from.
The second page is the disk-order page, which has four fields declaring the
order in which the four disks are to be examined; each field has a drop-down
list in which I can select a disk or declare it Not Available.
The third page is the boot devices page, where I can specify the order of
devices to be tried: floppy disk, optical disk, hard disk, USB device etc.
On
this page the hard disk is identified specifically by quoting the disk I've
put first on the second page.
Questions:
You have selected:
first page; sata first disk to boot from;
second page; disk order 'raid sata 1', 'raid sata 2', 'old sata', ide; ?
Currently, after a boot/reboot to BIOS setup, does the third page still show
the hard disk is 'raid sata 1'? Does the disk order remain as set? ('raid
sata 1', 'raid sata 2', 'old sata', 'ide'.
--
Rgds
Peter.
Linux Counter 5290, Aug 93
--
[EMAIL PROTECTED] mailing list
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] Re: Disk boot order in grub
- Original Message - From: Peter Humphrey [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Sunday, August 26, 2007 7:24 AM Subject: Re: [gentoo-amd64] Re: Disk boot order in grub On Saturday 25 Aug 2007, Drake Donahue wrote: dumb questions time: after editing /boot/grub/device.map did you reinstall grub using either grub-install --device-map (hd1) [where hd1 can be hd0 or hd2 or hd3] or grub --device-map=/boot/grub/device.map to invoke grub command line using the device.map. I had run grub after editing the device map, but simply with the command grub. After reading your advice I ran grub --device-map=/boot/grub/device.map and finished up with an unbootable system! (It couldn't find stage 1.5.) So from my rescue system I re-created /dev/md1 on /dev/sd[ab]1, made a new e2fs on /dev/md1, copied its files back in from backup, chrooted to the production system and reran grub to install to /dev/sd[ab]1. Before taking that last step I removed all device maps from the SATA disks. Installing grub did not re-create one anywhere that I can see, but the system boots just the same as before. This part of the action is in accord with the grub manual. if there is no device.map and --device.map is invoked a device.map should be generated. if there is no device.map and --device.map is not invoked a device.map should not be generated. if there is a device.map and --device.map is not invoked the device.map should not be used. if there is a device.map and --device.map is invoked the device.map should be used. could you post the result of running grub-install --recheck hd1 and cat of /boot/grub/device.map and cat of /boot/grub/grub.conf # grub-install --recheck hd1 Probing devices to guess BIOS drives. This may take a long time. /dev/md/3 does not have any corresponding BIOS drive. theory: grub-install --recheck fails to an error message when a device file in /etc/mtab can not be mapped to a BIOS device without trying/reporting other mapping probes. As md is not a BIOS device the inability to map md drive file to BIOS device is logical. grub-install can not handle a kernel raid system so kernel raid people must use grub command line. end theory. # cat /boot/grub/device.map cat: /boot/grub/device.map: No such file or directory # cat /boot/grub/grub.conf [significant lines only] timeout 10 default 0 fallback 2 color white/blue black/light-gray splashimage (hd0,0)/grub/splash.xpm.gz title=Gentoo Linux 2.6.22-r2 root (hd1,0) kernel /boot/kernel-x86_64-2.6.22-gentoo-r2 root=/dev/md3 vga=0x31A video=vesafb:mtrr:3,ywrap splash=silent udev title=Gentoo Linux 2.6.22-r2, no X root (hd1,0) kernel /boot/kernel-x86_64-2.6.22-gentoo-r2 root=/dev/md3 vga=0x31A video=vesafb:mtrr:3,ywrap splash=silent udev softlevel=no-x title=Gentoo Linux 2.6.21-r4 root (hd1,0) kernel /boot/kernel-x86_64-2.6.21-gentoo-r4 root=/dev/md3 vga=0x31A video=vesafb:mtrr:3,ywrap splash=silent udev title=Gentoo Linux 2.6.21-r4 no X root (hd1,0) kernel /boot/kernel-x86_64-2.6.21-gentoo-r4 root=/dev/md3 vga=0x31A video=vesafb:mtrr:3,ywrap splash=silent udev softlevel=no-x title=Gentoo Linux 2.6.20-r8 (sdc) root (hd3,0) kernel /boot/kernel-x86_64-2.6.20-gentoo-r8 root=/dev/sdc3 vga=0x31A video=vesafb:mtrr:3,ywrap splash=silent udev title=Gentoo Linux 2.6.20-r8 (sdc, no X) root (hd3,0) kernel /boot/kernel-x86_64-2.6.20-gentoo-r8 root=/dev/sdc3 vga=0x31A video=vesafb:mtrr:3,ywrap splash=silent udev softlevel=no-x title=Gentoo Linux 2.6.21-r4 (32-bit system) root (hd3,0) kernel /boot/kernel-x86-2.6.21-gentoo-r4 root=/dev/sdc10 vga=0x31A video=vesafb:mtrr:3,ywrap splash=silent udev title=Gentoo Linux 2.6.20-r8 (32-bit system), no X root (hd3,0) kernel /boot/kernel-x86-2.6.21-gentoo-r4 root=/dev/sdc10 vga=0x31A video=vesafb:mtrr:3,ywrap splash=silent udev softlevel=no-x title=Rescue System root (hd0,0) kernel /boot/kernel-x86_64-2.6.20-gentoo-r8-rescue root=/dev/hda9 vga=0x31A splash=silent -- Current theory (pending further data): This problem relates to the problem discussed in another thread, possible MBR corruption. Theory: Kernel 2.6.22 (perhaps because of the options selected in menuconfig), caused a departure from the usual practice of keeping the first 63 sectors after the master boot record clear and starting the partition data table at sector 64. The first partof this area is normally used by stage 1.5. As an example: Grub outputs something like: 'Running embed /boot/grub/e2fs_stage1_5 (hd0)... 16 sectors are embedded. succeeded Running install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,0)/boot/grub/stage2 /boot/ grub/menu.lst... succeeded Done. ' Variations (device identifier,number of sectors, file system type) depend on the device and the file system found at the location where stage 2 is to be found, this was specified by the root command, root (hd0,0
Re: [gentoo-amd64] Re: Disk boot order in grub
- Original Message - From: Peter Humphrey [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Sunday, August 26, 2007 7:24 AM Subject: Re: [gentoo-amd64] Re: Disk boot order in grub snip of my comments that resulted in an unbootable system I had run grub after editing the device map, but simply with the command grub. After reading your advice I ran grub --device-map=/boot/grub/device.map and finished up with an unbootable system! (It couldn't find stage 1.5.) So from my rescue system More dumb questions: The rescue system used is the one on the IDE drive? You booted the rescue system by setting up the BIOS boot order to boot the ide first? You booted the rescue system by setting up the BIOS boot order to boot the old sata first? You booted the rescue system by using a rescue floppy/cd/usb? Is grub installed on the ide drive? If the ide has grub installed, are the boot file system and grub.conf the same as those on the sata's? Are any of your partitions flagged as bootable? The fdisk -l data provided earlier for the sata disks had no asterisks in the boot column. As an alternate check for bootable flag (besides fdisk), dump a copy of the MBR to screen: as root or sudo: example: dd if=/dev/sda count=1 | hexdump -C and look for 55 aa(meaning bootable)as the last two words. I re-created /dev/md1 on /dev/sd[ab]1, made a new e2fs on /dev/md1, copied its files back in from backup, chrooted to the production system and reran grub to install to /dev/sd[ab]1. Before taking that last step I removed all device maps from the SATA disks. Installing grub did not re-create one anywhere that I can see, but the system boots just the same as before. You reported earlier that the /boot directory used was that on the old sata. How can you tell that? snip # cat /boot/grub/grub.conf [significant lines only] timeout 10 default 0 fallback 2 color white/blue black/light-gray splashimage (hd0,0)/grub/splash.xpm.gz title=Gentoo Linux 2.6.22-r2 root (hd1,0) kernel /boot/kernel-x86_64-2.6.22-gentoo-r2 root=/dev/md3 vga=0x31A video=vesafb:mtrr:3,ywrap splash=silent udev title=Gentoo Linux 2.6.22-r2, no X root (hd1,0) kernel /boot/kernel-x86_64-2.6.22-gentoo-r2 root=/dev/md3 vga=0x31A video=vesafb:mtrr:3,ywrap splash=silent udev softlevel=no-x title=Gentoo Linux 2.6.21-r4 root (hd1,0) kernel /boot/kernel-x86_64-2.6.21-gentoo-r4 root=/dev/md3 vga=0x31A video=vesafb:mtrr:3,ywrap splash=silent udev title=Gentoo Linux 2.6.21-r4 no X root (hd1,0) kernel /boot/kernel-x86_64-2.6.21-gentoo-r4 root=/dev/md3 vga=0x31A video=vesafb:mtrr:3,ywrap splash=silent udev softlevel=no-x title=Gentoo Linux 2.6.20-r8 (sdc) root (hd3,0) kernel /boot/kernel-x86_64-2.6.20-gentoo-r8 root=/dev/sdc3 vga=0x31A video=vesafb:mtrr:3,ywrap splash=silent udev title=Gentoo Linux 2.6.20-r8 (sdc, no X) root (hd3,0) kernel /boot/kernel-x86_64-2.6.20-gentoo-r8 root=/dev/sdc3 vga=0x31A video=vesafb:mtrr:3,ywrap splash=silent udev softlevel=no-x title=Gentoo Linux 2.6.21-r4 (32-bit system) root (hd3,0) kernel /boot/kernel-x86-2.6.21-gentoo-r4 root=/dev/sdc10 vga=0x31A video=vesafb:mtrr:3,ywrap splash=silent udev title=Gentoo Linux 2.6.20-r8 (32-bit system), no X root (hd3,0) kernel /boot/kernel-x86-2.6.21-gentoo-r4 root=/dev/sdc10 vga=0x31A video=vesafb:mtrr:3,ywrap splash=silent udev softlevel=no-x title=Rescue System root (hd0,0) kernel /boot/kernel-x86_64-2.6.20-gentoo-r8-rescue root=/dev/hda9 vga=0x31A splash=silent -- Rgds Peter. Linux Counter 5290, Aug 93 -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] Re: Disk boot order in grub
- Original Message - From: Duncan [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Saturday, August 25, 2007 7:59 PM Subject: [gentoo-amd64] Re: Disk boot order in grub Peter Humphrey [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Sat, 25 Aug 2007 09:00:55 +0100: BTW, when you cat'ed the old device.map it appeared that the old sata was being seen as an ide device. I don't think so. Just in case the GP wasn't aware, GRUB uses hd for both IDE and SATA/ SCSI drives. You may be and are picking up on something else, but thought I'd throw that out, just in case. First report was the system had 1 ide, one old sata, and 2 new sata. The device.map was later reported as: # cat /boot/grub/device.map (fd0) /dev/fd0 (hd0) /dev/hda (hd1) /dev/hdb (hd2) /dev/sda (hd3) /dev/sdb That device.map has 2 ((hdo) and (hd1)) devices mapped to ide drives and 2 ((hd2)and (hd3)) devices mapped to sata drives. The inconsistency was under discussion. In the complete text, the inconsistency was explained by: I don't think so. When that device.map was created, this box had two IDE and two SATA disks; the map looks right to me - it just wasn't updated when the arrangement of disks was changed, since it didn't occur to me that I ought to do so. I've now fixed that but it's made no difference (of course) to the order in which the BIOS looks on the disks for boot code. -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] Re: Disk boot order in grub
- Original Message - From: Peter Humphrey [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Friday, August 24, 2007 5:19 AM Subject: Re: [gentoo-amd64] Re: Disk boot order in grub On Thursday 23 Aug 2007, Peter Humphrey wrote: That's the answer - thanks! I spoke too soon. Correcting the device.map file made no difference; my problem is clearly in the BIOS. What follows refers exclusively to the BIOS setup process; grub is not involved, let alone Gentoo. The BIOS setup program gives me three pages where I can set values. The first is the IDE setup page, where I can mark the several IDE and SATA interfaces as active (auto) or inactive; I can also say whether IDE or SATA is to be the first disk to boot from. The second page is the disk-order page, which has four fields declaring the order in which the four disks are to be examined; each field has a drop-down list in which I can select a disk or declare it Not Available. The third page is the boot devices page, where I can specify the order of devices to be tried: floppy disk, optical disk, hard disk, USB device etc. On this page the hard disk is identified specifically by quoting the disk I've put first on the second page. (I may have to reboot for this disk to be identified correctly, I'm not sure.) I mention this page for completeness; I haven't had to change anything here. This is what I did: I said boot SATA first, with disks in the order I wanted (the two identical disks first, then the other SATA disk, then the IDE disk), with floppy first, CD second and hard disk third. On saving these values and booting back into BIOS setup, the disk order had been changed; it had the old SATA disk first, then the IDE, then the two identical disks. This was repeatable. The only way I can get the BIOS to look first on the two identical disks is by marking the old SATA disk unavailable on the second page. This only marks it unavailable to the boot process - it's still accessible after Gentoo boots. Next I tried booting from the oldest disk, the IDE one that has Windows on it among other things. I thought that just setting boot-from-IDE on the first BIOS page should do the trick, but no - it still ran grub on one of the SATA disks. To get Windows booted I had to mark the SATA interfaces down in the BIOS. (I've just thought of another possibility - I might get the same effect by setting the IDE disk first on the second page. I'll try that.) All of this leaves me in the somewhat unsatisfactory position of having to run the BIOS setup if I want to run Windows (that's because it's on the third partition on the disk, so grub can't boot it). Naturally, I don't often want to run Windows, but I'd still prefer not to have to burn the eeprom twice every time I do. One hopes only CMOS not EEPROM. As I said, I have problems with the BIOS. I'd better go and seek out an upgrade. Your board is Supermicro H8DCE? If so, the User's Manual does hurt. I suspect BIOS upgrade will not change the behavior you've seen. All I've seen says grub must adapt to BIOS vice any other choice. If so, may I suggest: Enter BIOS setup and Load Optimal Defaults. Make note of the boot device choices but make no changes. Make no other changes to BIOS just save changes and exit. Reboot. Reenter BIOS setup and verify the boot options are stable. Exit BIOS setup. Allow something to boot if it will. Points of information will be: what booted (if anything}? was there a grub boot screen? If there was a grub boot screen, scribble down the choices, and see if they are as you expect. Edit the choice selected, scribble down the lines invoked, and see if they are as you expect. If the lines are as you expected but the result was no boot or the wrong boot, repeated manual editing of root (hd?,0) and manual boot may get you to the kernel that supports raid and lvm by trial and error. BTW, when you cat'ed the old device.map it appeared that the old sata was being seen as an ide device. Thanks to those who've helped. -- Rgds Peter. Linux Counter 5290, Aug 93 -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] possible MBR corruption?
- Original Message - From: Marc Joliet [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Friday, August 24, 2007 4:50 PM Subject: Re: [gentoo-amd64] possible MBR corruption? http://en.wikipedia.org/wiki/GNU_GRUB is a well written and short explanation of things grub. It also has a good set of links for further detailed explanations. If what you saw was really grub followed by a blinking cursor grub stage 1 was most likely unable to find stage 2 and had dropped out to a command line. This normally results from a typo in grub.conf, kernel name, or symlink. If GRUB _ (blinking underscore) was exactly what you saw: I would believe that Stage 1 was in the master boot record. Stage 1 should call stage 1.5. Stage 1.5 should call stage 2. http://www.gnu.org/software/grub/manual/html_node/Images.html refers. By observation, when all goes normally(using a boot floppy to slow the the action}: GRUB _ to GRUB Loading stage1.5 ._ to GRUB Loading stage1.5 ._ to GRUB Loading stage1.5 . _ to GRUB Loading stage2 ._ to GRUB Loading stage2 ._ to GRUB Loading stage2 . _ is printed. (underscores blinking, dots as progress bar). I would guess that that some change in the file system(s) incident to the update obliterated, damaged, or moved stage 1.5. This is based on guesses that initial GRUB _ is generated by stage 1, Loading stage1.5 is generated by stage 1.5, and a drop out to command line is generated by stage 1.5. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] Re: Disk boot order in grub
- Original Message - From: Peter Humphrey [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Wednesday, August 22, 2007 4:35 AM Subject: Re: [gentoo-amd64] Re: Disk boot order in grub On Sunday 19 Aug 2007, Duncan wrote: Peter Humphrey [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Sun, 19 Aug 2007 11:34:56 +0100: This box now has a slightly odd arrangement of disks. It has two new SATA disks on the first two SATA interfaces, another SATA disk on the third SATA interface, and it also has the original IDE disk for the odd occasion when I want to run Windows. The two new disks have been set up with LVM2 and contain my usual Gentoo system. I followed the Gentoo LVM quick-install guide and created /dev/md1 for my boot partition, putting the logical volumes into /dev/md3. I can't boot via /dev/md1. grub-install --recheck hd0 grub-install --recheck hd1 grub-install --recheck hd2 grub-install --recheck hd3 should all give the same device map which may look like: (fd0) /dev/fd0 (hd0) /dev/hda (hd1) /dev/sda (hd2) /dev/sdb (hd3) /dev/sdc if the device maps are different or not what you thought when you wrote grub.conf . quoting www.gnu.org/software/grub/manual/html_node/Device-map.html : (googling -bios grub device map- gives more stuff) 15.3 The map between BIOS drives and OS devices sata optical drives can also confuse things When you specify the option --device-map (see Basic usage), the grub shell creates the device map file automatically unless it already exists. The file /boot/grub/device.map is preferred. If the device map file exists, the grub shell reads it to map BIOS drives to OS devices. This file consists of lines like this: device file device is a drive specified in the GRUB syntax (see Device syntax), and file is an OS file, which is normally a device file. The reason why the grub shell gives you the device map file is that it cannot guess the map between BIOS drives and OS devices correctly in some environments. . For example, if you exchange the boot sequence between IDE and SCSI in your BIOS, it gets the order wrong Thus, edit the file if the grub shell makes a mistake. You can put any comments in the file if needed, as the grub shell assumes that a line is just a comment if the first character is `#' -- Rgds Peter. Linux Counter 5290, Aug 93 -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] CONFIG_VIDEO_V4L1_COMPAT Kernel Option
- Original Message - From: sean [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Friday, June 22, 2007 6:10 PM Subject: [gentoo-amd64] CONFIG_VIDEO_V4L1_COMPAT Kernel Option Unable to find CONFIG_VIDEO_V4L1_COMPAT option in Make Menuconfig. So I went and looked over the .config file and still do not see such an option. Did a search, several in fact, and found the mentioned CONFIG_VIDEO_V4L1_COMPAT=y mentioned many times and that it would appear to be located in Device Drivers Multimedia Devices, but it still seems to be missing. Is anyone able to give me an idea as to where this kernel option is located? located in Device Drivers, Multimedia Devices, Video for Linux,Enable Video For Linux API 1 (DEPRECATED} Note that you won't see the last unless you 'y' or 'm' the next to last. Thanks Sean -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] CONFIG_VIDEO_V4L1_COMPAT Kernel Option
- Original Message - From: sean [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Friday, June 22, 2007 11:20 PM Subject: Re: [gentoo-amd64] CONFIG_VIDEO_V4L1_COMPAT Kernel Option Drake Donahue wrote: - Original Message - From: sean [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Friday, June 22, 2007 6:10 PM Subject: [gentoo-amd64] CONFIG_VIDEO_V4L1_COMPAT Kernel Option Unable to find CONFIG_VIDEO_V4L1_COMPAT option in Make Menuconfig. So I went and looked over the .config file and still do not see such an option. Did a search, several in fact, and found the mentioned CONFIG_VIDEO_V4L1_COMPAT=y mentioned many times and that it would appear to be located in Device Drivers Multimedia Devices, but it still seems to be missing. Is anyone able to give me an idea as to where this kernel option is located? located in Device Drivers, Multimedia Devices, Video for Linux,Enable Video For Linux API 1 (DEPRECATED} Note that you won't see the last unless you 'y' or 'm' the next to last. Thanks Sean -- [EMAIL PROTECTED] mailing list Thanks Drake and Mike, The problem of the kernel option was caused by the fact that I was running an older kernel and the option was not included. Upgraded the kernel, and the option is now available, though now fails with other problems. Sean -- [EMAIL PROTECTED] mailing list scpa5xx may be wrong choice now: from http://gentoo-wiki.com/HOWTO_Install_a_webcam#USB_support gspcav1 - Kernel 2.6.11 or newer spca5xx - Kernel 2.6.11 or older -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] Can't build kernel
- Original Message - From: Peter Hoff To: gentoo-amd64 Sent: Saturday, May 19, 2007 2:02 PM Subject: [gentoo-amd64] Can't build kernel I haven't been able to build 2.6.21. I was hoping it was maybe just a -0 release problem, but I'm getting the same error with -r1. Here it is: snip FWIW 2.6.21 built here a couple weeks ago and is still running fine. May be equipment or configuration specific problem. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] Re: Old package in portage ?
- Original Message - From: Vladimir Strycek [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Wednesday, May 16, 2007 4:43 PM Subject: Re: [gentoo-amd64] Re: Old package in portage ? Duncan wrote / napísal(a): Vladimir Strycek [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Wed, 16 May 2007 07:45:53 +0200: I was told that this issue has been fixed in new version of rrd tool rrdtool 1.2.23-r1 but this one isnt in portage.. It's in portage. I'm guessing you either haven't synced in awhile, or you aren't seeing it as you are running stable arch (amd64 in this case) and the package in question isn't stabilized yet, tho it's keyworded ~arch (unstable, ~amd64 in our case). Assuming you've synced, it's almost certainly the latter. You'll need to add the package to your package.keywords file as appropriate. See the portage documentation in the Gentoo handbook (installation is just one section of several, you know, and there's a LOT of stuff in the other sections, particularly the working with Gentoo and working with Portage sections, that make a Gentoo sysadmin's job FAR easier than it'd be otherwise) and portage and emerge manpages. There's a script, earch, that I picked up on the dev list some time ago, that lists the versions of a package and the latest stable and ~arch versions for each arch. Here's what it reports for rrdtool: $earch rrdtool rrdtool-1.0.49[0]: rrdtool-1.2.15-r3[0]: alpha amd64 arm hppa ia64 mips ppc ppc64 sh sparc x86 rrdtool-1.2.19[0]: rrdtool-1.2.23[0]: rrdtool-1.2.23-r1[0]: ~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~sh ~sparc ~x86 So rrdtool-1.2.23-r1 is keyworded ~amd64, while 1.2.15-r3 is the latest stable. earch looks like good candidate for gentoolkit Thanks i look into it -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] mythfrontend on AMD64 - will it work with qt-4? (cannot connect to database)
- Original Message - From: Mark Knecht [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Tuesday, May 15, 2007 11:12 AM Subject: Re: [gentoo-amd64] mythfrontend on AMD64 - will it work with qt-4? (cannot connect to database) It seems that re-emerging qt3 solved this problem. My remote frontend is working fine. Now to solve the remaining problems on the backend. thanks all! Cheers, Mark snip http://gentoo-wiki.com/HOWTO_Setup_MythTV -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] Quick Portage How to
- Original Message - From: Jack Lloyd [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Thursday, March 22, 2007 8:42 AM Subject: Re: [gentoo-amd64] Quick Portage How to On Wed, Mar 21, 2007 at 10:24:37PM +, Peter Humphrey wrote: On Wednesday 21 March 2007 18:45:39 Mark Haney wrote: Is there a way I can get portage to show me all the listed kernel sources I've installed? And one more they haven't mentioned: equery l gentoo-sources Another, related one that I use a lot is equery l sys-kernel/ (since I use a mix of gentoo-sources and vanilla-sources on my machines, depending on which contains fixes for the bugs that happen to be bothering me that day). or as mentioned in Gentoo Linux Kernel Upgrade Guide: eselect kernel list -J -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Re: fsck seems to screw up my harddisk
- Original Message -
From: Duncan [EMAIL PROTECTED]
To: gentoo-amd64@lists.gentoo.org
Sent: Sunday, December 03, 2006 12:04 PM
Subject: [gentoo-amd64] Re: fsck seems to screw up my harddisk
Guido Doornberg [EMAIL PROTECTED] posted
[EMAIL PROTECTED], excerpted
below, on Sun, 03 Dec 2006 14:40:11 +0100:
Well, I downloaded and started a fresh 2006.1 livecd, repartitioned de
hdd, started mke2fs and this time with the -c option.
So, it started checking and after about 15 minutes this kept on showing
up
on my screen:
ata1: error=ox40 {uncorrectable error} ata1: translated ATA stat/err
0X51/40 SCSI SK/ASC/ASCQ 0x3/11/04
after a while i got a couple of other messages, and now it keeps on
talking about Buffer I/O error on device sda3, and after that various
sectors and blocks are called.
I did look after my power supply and I'm for 99% sure that's not the
problem. So, correct me if i'm wrong but that would mean my harddisk is
the problem? But how than is it possible that I can use it normally if I
don't let fsck check it?
I know this isn't really gentoo specific anymore, but if anyone knows
what
to do i'm happy to hear it.
visit
http://www.samsung.com/Products/HardDiskDrive/warranty/index.htm
and get replacement
current crop of spinpoint is getting bad reports for reliability
--
gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Re: Problems emerging Gnome
- Original Message -
From: Daniele Salatti [EMAIL PROTECTED]
To: gentoo-amd64@lists.gentoo.org
Sent: Sunday, September 17, 2006 5:35 AM
Subject: Re: [gentoo-amd64] Re: Problems emerging Gnome
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Drake Donahue wrote:
Just finished a successful install up to and including gnome.
At the end of this install, emerge --info produced an output that
included the not present items from your initial emerge --info.(Items
that you manually emerged such as glibc).
I used LiveCD 2006.1. At the boot option I used the default.
When it loaded a Gnome desktop I chose the Gentoo Linux Installer
(GTK+). Then:
1.type: standard
2.network:default -- misc: default
3.partitioning: selected a disk, clear partions, click recommended
layout 4.network mounts: default
5.stage: stage3, grp install, dynamic
6.portage tree: default
7.make.conf: default
8.kernel: livecd kernel
9.bootloader: grub, install in mbr, select a drive
extra kernel parameters-
10.time zone: pick one
11.networking: interface: eth0, configuration: dhcp
hostname etc: -as needed 12.daemons: default
13.extra packages: gnome and as desired; be generous
14.Startup servicse: as desired; be generous
15.other settings: {display manager:gdm, clock: local (cause i
dual boot windows), Xsession: Gnome (cause I like it),
others: default}
16.users: as desired, ensure you do root password
17.review: install
This should give you a working install including gnome.
This way it works...the only difference is in step 5 (I used stage3 from
the net) and 6 (sync from the net)...
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFDRa501cxVogLZp4RAsWjAKCDsCicWTdcXGgLm3MM7LAW8oRAMwCdHt0f
NLZnmkb1tipfREBKkM0E59g=
=ppSO
-END PGP SIGNATURE-
--
gentoo-amd64@gentoo.org mailing list
Good for you. Saved some updating.
You might want to resolve the bug as an unidentified gentoo system install
problem instead of a gnome problem.
--
gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Re: Problems emerging Gnome
- Original Message -
From: Daniele Salatti [EMAIL PROTECTED]
To: gentoo-amd64@lists.gentoo.org
Sent: Friday, September 15, 2006 2:44 AM
Subject: Re: [gentoo-amd64] Re: Problems emerging Gnome
Drake Donahue wrote:
What was the source for your install?
Minimal, Universal, LiveCD, LiveDVD?? 2006.0? 2006.1?
something else? I'll try to duplicate your installand see if the missing
or wrong component will appear for me.
(something used by the gnome-doc-utils in compiling xslt
components is missing or wrong)
I used LiveCD 2006.1. Let me know if it works ;)
Daniele
--
gentoo-amd64@gentoo.org mailing list
Just finished a successful install up to and including gnome.
At the end of this install, emerge --info produced an output
that included the not present items from your initial
emerge --info.(Items that you manually emerged such as glibc).
I used LiveCD 2006.1. At the boot option I used the default.
When it loaded a Gnome desktop I chose the
Gentoo Linux Installer (GTK+). Then:
1.type: standard
2.network:default -- misc: default
3.partitioning: selected a disk, clear partions, click recommended layout
4.network mounts: default
5.stage: stage3, grp install, dynamic
6.portage tree: default
7.make.conf: default
8.kernel: livecd kernel
9.bootloader: grub, install in mbr, select a drive
extra kernel parameters-
10.time zone: pick one
11.networking: interface: eth0, configuration: dhcp
hostname etc: -as needed
12.daemons: default
13.extra packages: gnome and as desired; be generous
14.Startup servicse: as desired; be generous
15.other settings: {display manager:gdm, clock: local (cause i
dual boot windows), Xsession: Gnome (cause I like it),
others: default}
16.users: as desired, ensure you do root password
17.review: install
This should give you a working install including gnome.
--
gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Re: Problems emerging Gnome
- Original Message - From: Daniele Salatti [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Thursday, September 14, 2006 5:50 PM Subject: Re: [gentoo-amd64] Re: Problems emerging Gnome Anothe emerge --info: # emerge --info Portage 2.1.1 (default-linux/amd64/2006.1, gcc-4.1.1, glibc-2.4-r3, 2.6.17-gentoo-r8 x86_64) = System uname: 2.6.17-gentoo-r8 x86_64 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.12.4 Last Sync: Thu, 14 Sep 2006 15:00:06 + app-admin/eselect-compiler: [Not Present] dev-lang/python: 2.4.3-r1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox:1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r3 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS=amd64 AUTOCLEAN=yes CBUILD=x86_64-pc-linux-gnu CFLAGS=-march=athlon64 -Os -pipe CHOST=x86_64-pc-linux-gnu CONFIG_PROTECT=/etc /usr/share/X11/xkb CONFIG_PROTECT_MASK=/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo CXXFLAGS=-march=athlon64 -Os -pipe DISTDIR=/usr/portage/distfiles FEATURES=autoconfig distlocks metadata-transfer sandbox sfperms strict GENTOO_MIRRORS=http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo; LINGUAS= MAKEOPTS=-j2 PKGDIR=/usr/portage/packages PORTAGE_RSYNC_OPTS=--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages' PORTAGE_TMPDIR=/var/tmp PORTDIR=/usr/portage SYNC=rsync://rsync.gentoo.org/gentoo-portage USE=X alsa amd64 arts avi berkdb bitmap-fonts cairo cdr cli crypt cups dbus dlloader dri dvd dvdr eds elibc_glibc emboss encode esd fam firefox fortran gdbm gif gnome gpm gstreamer gtk gtk2 hal input_devices_evdev input_devices_keyboard input_devices_mouse ipv6 isdnlog jpeg kernel_linux ldap libg++ mad mikmod mp3 mpeg ncurses nls nptl nptlonly ogg opengl oss pam pcre pdflib perl png ppds pppd python qt3 qt4 quicktime readline reflection sdl session spell spl ssl tcpd truetype truetype-fonts type1-fonts udev unicode userland_GNU video_cards_radeon vorbis xml xorg xv zlib Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY emerge --search xslt: Searching... [ Results for search key : xslt ] [ Applications found : 6 ] * app-xemacs/xslt-process Latest version available: 1.11 Latest version installed: 1.11 Size of files: 195 kB Homepage: http://xemacs.org/ Description: XSLT processing support. License: GPL-2 * dev-libs/libxslt Latest version available: 1.1.17 Latest version installed: 1.1.17 Size of files: 1,865 kB Homepage: http://www.xmlsoft.org/ Description: XSLT libraries and tools License: MIT * dev-perl/XML-LibXSLT Latest version available: 1.58 Latest version installed: 1.58 Size of files: 30 kB Homepage: http://search.cpan.org/~msergeant/XML-LibXSLT-1.58/ Description: A Perl module to parse XSL Transformational sheets using gnome's libXSLT License: Artistic * dev-perl/XML-XSLT Latest version available: 0.48 Latest version installed: [ Not Installed ] Size of files: 257 kB Homepage: http://search.cpan.org/~jstowe/XML-XSLT-0.48/ Description: A Perl module to parse XSL Transformational sheets License: Artistic * dev-ruby/ruby-xslt [ Masked ] Latest version available: 0.9.2 Latest version installed: [ Not Installed ] Size of files: 53 kB Homepage: http://www.rubyfr.net/ Description: A Ruby class for processing XSLT License: GPL-2 * net-www/mod_xslt Latest version available: 2.0.4 Latest version installed: [ Not Installed ] Size of files: 15 kB Homepage: http://www.mod-xslt.com/ Description: An xslt filtering DSO module for Apache2. License: GPL-2 Still giving the same error at the same point... -- gentoo-amd64@gentoo.org mailing list Another difference: the only xslt package I have installed is libxslt Perhaps: emerge --unmerge xslt-process emerge --unmerge XML-LibXSLT Just tryed...still not working...same error at the same point... :( Daniele -- gentoo-amd64@gentoo.org mailing list What was the source for your install? Minimal, Universal, LiveCD, LiveDVD?? 2006.0? 2006.1? something else? I'll try to duplicate your installand see if the missing or wrong component will appear for me. (something used by the gnome-doc-utils in compiling xslt components is missing or wrong) -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Re: Problems emerging Gnome
- Original Message - From: Daniele Salatti [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Wednesday, September 13, 2006 6:03 PM Subject: Re: [gentoo-amd64] Re: Problems emerging Gnome The problem is that my make.conf doesn't contains all these USE flags as reported by emerge --info...I can't figure out where all the reported mess came from... -- gentoo-amd64@gentoo.org mailing list there is a thing called a profile provided by the developers for an architecture which provides a standard set of packages and use flags (in /etc/make.profile). This base set of flags is modified by use flags in packages you emerge, by entries you may make in /etc/portage/package.use, and by entries you make in /etc/make.conf. I think emerge --info USE= summarizes all these sources. I'm guessing you used genkernel and/or the 2006.1 LiveCD or 2006.1 LiveDVD and got lots of extra stuff. Try: (I think you got a bad package) empty the following directories and remove them: /var/db/pkg/app-text/gnome-doc-utils-0.6.1 /usr/share/doc/gnome-doc-utils-0.6.1 /usr/share/gnome-doc-utils /usr/portage/app-text/gnome-doc-utils then: rm /usr/portage/distfiles/gnome-doc-utils-0.6.1.tar.bz2 rm /usr/portage/distfiles/gnome-doc-utils-0.4.4.tar.bz2 Then: emerge gnome-doc-utils if it works, great. Emerge gnome. If not: emerge -v gnome-doc-utils /stuff /stuff will be a long detailed report on the compile process. will send you mine for comparison purposes off list. line 14 checking for XML::PARSER...ok may be important you should not have any http: 's in your output --- looks like run happened before compiling completed. -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] How to rescue to lost ext3 partition ??
- Original Message - From: jai kumar To: gentoo-amd64@lists.gentoo.org Sent: Tuesday, August 15, 2006 5:37 PM Subject: [gentoo-amd64] How to rescue to lost ext3 partition ?? hi all , I tried to resize my gentoo (ext3) partion with the help of partition magic. everything goes correct but in the completion it gave some error. didn't know exactly what was that. Then i reboot the system and find out that grub was lost and giving error 17. === error 17 This error is returned if the partition requested exists, but the filesystem type cannot be recognized by GRUB. === Now after some efforts I somehow manage to install grub again with the help of a Gentoo live cd. But I have no clue for how to get back my gentoo partition. Is there any way to rescue that parition?? following are some useful info. === gentoo ext partion is /dev/sda13 - Using /dev/sda (parted) p Disk geometry for /dev/sda: 0kB - 160GB Disk label type: msdos Number Start End SizeType File system Flags 1 32kB11GB11GBprimary fat32boot, lba 2 11GB160GB 149GB extended lba 5 11GB24GB13GBlogical fat32 6 24GB45GB21GBlogical ntfs 7 45GB67GB21GBlogical ntfs 8 67GB88GB21GBlogical ntfs 9 88GB108GB 19GBlogical fat32 10 108GB 140GB 32GBlogical ntfs 11 140GB 141GB 1077MB logical linux-swap 12 141GB 148GB 7230MB logical ext3 boot 13 148GB 156GB 7830MB logical (parted) - [EMAIL PROTECTED]:/home/flukebox# dmesg|tail |grep sda13 [17182864.744000] VFS: Can't find ext3 filesystem on dev sda13. [EMAIL PROTECTED]:/home/flukebox# please let me know if there is anyway to rescue ?? Thanks in advance. ~jaiks Are you sure that your system is not on /dev/sda12? I would boot an install cd and mount /mnt/gentoo /dev/sda12 and take a look before the action gets drastic. Here's a new way to find what you're looking for - Yahoo! Answers Send FREE SMS to your friend's mobile from Yahoo! Messenger Version 8. Get it NOW -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] USB-Serial Converter?
snip Peter Davoust wrote: # CONFIG_USB_SERIAL_FTDI_SIO is not set A quick check of google tells me that CONFIG_USB_SERIAL_FTDI_SIO=Y needs tyo be set in the kernel for this device to work. Rebuild your kernel with this support and try it. - -- Kirby Walborn There is a manual. http://www.gentoo.org/doc/en/usb-guide.xml Gentoo Linux USB Guide, says: (If you have a serial to USB converter like the Prolific 2303, you'll need this) USB Serial Converter support --- * USB Serial Converter support * USB Prolific 2303 Single Port Serial Driver (NEW) snip -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Re: Re: Problems with Serial ATA disc
apparently vt8251 was not a well supported chipset even in windows. http://forums.viaarena.com/messageview.aspx?catid=28threadid=71754enterthread=y provides following: - Original Message - This topic serves to inform you of the status of real support for the VIA VT8251. In short, full support for the chipset and all features will be in Linux-2.6.18. But if you'd like to use it now, read on for details.. PATA | Driver name: blk_dev_via82cxxx: a.. fully supported in Linux-2.6.15 and onwards. SATA | Driver name: scsi_ahci_sata: a.. will be fully* supported in Linux-2.6.18 and onwards. a.. and patches are available for Linux-2.6.15, 2.6.16 and 2.6.17 *: There is no support for NCQ, unfortunately, as the VT8251 does not implement the AHCI specification correctly. Until VIA tells us how exactly they screwed up (so we may work around the issue), this situation is not likely to change. Audio: AC'97 | Driver name: snd_via82xx: a.. fully supported in Linux-2.6.17 (and ALSA 1.0.12rc1) and onwards. a.. For older kernels this patch is available. Audio: Intel HDA | Driver name: snd_hda_intel: a.. fully supported in Linux-2.6.15 (and ALSA-1.0.8) and onwards. When using the drivers listed above, you will not need to install any packages, proprietary or otherwise, provided by VIA or your motherboard manufacturer. In fact, I would recommend against doing so. A couple of credits: a.. PATA DMA support was sent to the libata maintainer independently by VIA and Daniel Drake. These patches utilise the 82Cxxx driver written by Vojtech Pavlik(SUSE), based upon the work of Michel Aubry, Jeff Garzik (Red Hat) and Andre Hedrick. a.. SATA support was initially provided by VIA. The patch has been modified by Geoff Rivell for 2.6.15.1, by Cristian Olar for 2.6.16, and reworked for inclusion in the mainline kernel by yours truly (Bastiaan Jacques). a.. AC'97 support has been added by yours truly. This is based upon the work by Jaroslav Kysela (SUSE) and Tjeerd Mulder (Fujitsu-Siemens). a.. Intel HDA support was written by Takashi Iwai (SUSE). I'll try to keep this post updated. Please send me a private message if you'd like something changed or added. Edited: Wed Jun 28, 2006 at 00:42 by bjacques -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] ASUS A8V-MX, with vt8251 chipset.
http://forums.viaarena.com/messageview.aspx?catid=28threadid=71754enterthread=y Este tema sirve para informarle de la posición de apoyo verdadero para el VIA VT8251. En resumen, apoyo repleto para el chipset y todas características estará en Linux-2.6.18. Pero si usted querría utilizarlo ahora, leyó en para detalles.. PATA | el nombre de Conductor: blk_dev_via82cxxx: # sostuvo completamente en Linux-2.6.15 y adelante. SATA | el nombre de Conductor: scsi_ahci_sata: # será completamente* sostuvo en Linux-2.6.18 y adelante. # y los parches están disponibles para Linux-2.6.15, 2.6.16 y 2.6.17 *: No hay apoyo para NCQ, desgraciadamente, como el VT8251 no aplica la especificación de AHCI correctamente. Hasta que VIA nos diga cuán exactamente ellos enroscaron arriba (tan podemos trabajar alrededor del asunto), esta situación no es probable de cambiar. La audiofrecuencia: C.A.' 97 | el nombre de Conductor: snd_via82xx: # sostuvo completamente en Linux-2.6.17 (y ALSA 1.0.12rc1) y adelante. # Para los meollos más viejos que este parche está disponible. La audiofrecuencia: Intel HDA | el nombre de Conductor: snd_hda_intel: # sostuvo completamente en Linux-2.6.15 (y ALSA-1.0.8) y adelante. Cuando se usa los conductores listaron arriba, usted no necesitará instalar ningún paquete, propietario ni de otro modo, proporcionado por VIA ni VIA su fabricante del tablero de sistema. De hecho, yo recomendaría contra hacer así. Un par de créditos: # apoyo de PATA DMA fue mandado al maintainer del libata independientemente por VIA y VIA Pato de Daniel. Estos parches utilizan al conductor 82Cxxx escrito por Vojtech Pavlik (SUSE), basado sobre el trabajo de Michel Aubry, Jeff Garzik (el Sombrero Rojo) y Andre Hedrick. # apoyo de SATA fue proporcionado inicialmente por VIA. El parche ha sido modificado por Geoff Rivell para 2.6.15.1, por Cristian Olar para y rehecho para la inclusión en el se inyecta en vena el meollo por le saluda atentamente (Bastiaan Jacques). # C.A.' 97 apoyo ha sido agregado por le saluda atentamente. Esto es basado sobre el trabajo por Jaroslav Kysela (SUSE) y Tjeerd Mulder (Fujitsu-Siemens). # apoyo de Intel HDA fue escrito por Takashi Iwai (SUSE). Trataré de mantener este poste actualizado. Mándeme por favor un mensaje privado si usted querría que algo cambiara o agregara. Redactado: Cásese junio 28, 2006 en 00:42 por el Fondo de la Cima de la Cita de Contestación de bjacques - Original Message - From: Mario A Wojcik [EMAIL PROTECTED] To: gentoo-amd64@lists.gentoo.org Sent: Tuesday, July 04, 2006 3:28 PM Subject: [gentoo-amd64] ASUS A8V-MX, with vt8251 chipset. My mobo is an ASUS a8v-mx with vt8251 chipset. Gentoo that not recognize the SATA Western Digital. I test with doscsi and noapic parameters but don´t results. Please help me!! Wojcik, Mario A. Alquimia Informática Tambor de Tacuarí 780 Leandro N. Alem Misiones - Argentina [EMAIL PROTECTED] [EMAIL PROTECTED] Cel (+54) 03754-15498713 Tel (+54) 03754-422181 -- gentoo-amd64@gentoo.org mailing list -- gentoo-amd64@gentoo.org mailing list
