[gentoo-user] Booting LiveCD iso from hard drive with GRUB legacy

[Mick]

Hi All,

Is there a way of achieving this?

-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Alsa Question (alsaconf R.I.P.)

[Samuli Suominen]

On 17/05/13 21:30, Silvio Siefke wrote:

 (generated by alsaconf)


Gentoo's alsa-guide.xml is outdated and is incorrectly suggesting the 
use of alsaconf


When in reality alsaconf doesn't work at all with sys-apps/kmod because 
it doesn't generate 'modules.pcimap' and 'modules.usbmap' files anymore


And in version 1.0.27 of alsa-utils in ~arch the command is no longer 
being installed


So whatever you do, forget about `alsaconf` right from the start, since 
it's no longer required with modern PCI, USB, ... cards because 
sys-fs/udev automatically loads the required drivers
The `alsaconf` command has been useful only for old PCMCIA and ISA cards 
for years already


Instead you don't do anything else than unmute the mixers using 
alsamixer, and leave the module loading to udev


As in, edit/write /etc/modprobe.d/alsa.conf by hand only if you need to 
pass some options to the modules

Re: [gentoo-user] Logitech MX620 mouse

[Stefan G. Weichinger]

Am 18.05.2013 00:57, schrieb John Campbell:

> Take a look at imwheel.  It's a little unmaintained but it still works.
>  I've used it on an old MX1000 and my current PreformanceMX.
> 
> You can set mouse buttons on a per window/program basis to have
> different effects for whichever window has focus.  Thus "search" for
> Firefox and "paste" for Thunderbird.
> 
> You also might need lomoco to turn on the button.  I remember with my
> MX1000, I had to enable the two scroll wheels as buttons.  Otherwise
> they were used by the mouse to "scroll fast" which I found pretty useless.

thanks for the suggestions!

We were successful with btnx yesterday ... and now we don't touch it
anymore (as long as it still works).

Stefan

Re: [gentoo-user] Booting LiveCD iso from hard drive with GRUB legacy

[tastytea]

On Sat, 18 May 2013 09:15:44 +0100
Mick  wrote:

> Hi All,
> 
> Is there a way of achieving this?
> 

Hi,
Maybe it works with chainloader?
See "info grub" for more information.

-- 
tastytea
GPG-Key: 87984243
Jabber-ID: tasty...@riseup.net


signature.asc
Description: PGP signature

Re: [gentoo-user] Re: gcc4.7.2-r1 to 4.7.3 upgrade - hosed system?

[Adam Carter]

On Sat, May 18, 2013 at 4:18 AM, walt  wrote:

> On 05/17/2013 12:33 AM, Adam Carter wrote:
> > # gcc-config 2 * Switching native-compiler to
> > x86_64-pc-linux-gnu-4.7.3 ... /usr/bin/python2.7: error while loading
> > shared libraries: libgcc_s.so.1: cannot open shared object file: No
> > such file or directory
>
>  #ldconfig -p | grep libgcc
> libgccpp.so.1 (libc6,x86-64) => /usr/lib64/libgccpp.so.1
> libgccpp.so (libc6,x86-64) => /usr/lib64/libgccpp.so
> libgcc_s.so.1 (libc6,x86-64) =>
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so.1
> libgcc_s.so.1 (libc6,x86-64) =>
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so.1
> libgcc_s.so.1 (libc6) =>
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so.1
> libgcc_s.so.1 (libc6) =>
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so.1
> libgcc_s.so (libc6,x86-64) =>
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so
> libgcc_s.so (libc6,x86-64) =>
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so
> libgcc_s.so (libc6) =>
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so
> libgcc_s.so (libc6) =>
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so
>
> What do you have?
>
>
# ldconfig -p | grep libgcc
libgcc_s.so.1 (libc6,x86-64) => /lib64/libgcc_s.so.1
libgcc_s.so.1 (libc6,x86-64) =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so.1
libgcc_s.so.1 (libc6,x86-64) =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so.1
libgcc_s.so.1 (libc6) =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so.1
libgcc_s.so.1 (libc6) =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so.1
libgcc_s.so (libc6,x86-64) =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so
libgcc_s.so (libc6,x86-64) =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so
libgcc_s.so (libc6) =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so
libgcc_s.so (libc6) =>
/usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so

# ls -l /lib64/libgcc_s.so.1
lrwxrwxrwx 1 root root 28 May 17 19:11 /lib64/libgcc_s.so.1 ->
libgcc_s-4.7.2-20121109.so.1

Crufty Will it be safe to delete the link since the file is found in
the other locations?

[gentoo-user] Re: gcc4.7.2-r1 to 4.7.3 upgrade - hosed system?

[walt]

On 05/18/2013 02:53 AM, Adam Carter wrote:
> On Sat, May 18, 2013 at 4:18 AM, walt  > wrote:
> 
> On 05/17/2013 12:33 AM, Adam Carter wrote:
> > # gcc-config 2 * Switching native-compiler to
> > x86_64-pc-linux-gnu-4.7.3 ... /usr/bin/python2.7: error while loading
> > shared libraries: libgcc_s.so.1: cannot open shared object file: No
> > such file or directory
> 
>  #ldconfig -p | grep libgcc
> libgccpp.so.1 (libc6,x86-64) => /usr/lib64/libgccpp.so.1
> libgccpp.so (libc6,x86-64) => /usr/lib64/libgccpp.so
> libgcc_s.so.1 (libc6,x86-64) => 
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so.1
> libgcc_s.so.1 (libc6,x86-64) => 
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so.1
> libgcc_s.so.1 (libc6) => 
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so.1
> libgcc_s.so.1 (libc6) => 
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so.1
> libgcc_s.so (libc6,x86-64) => 
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so
> libgcc_s.so (libc6,x86-64) => 
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so
> libgcc_s.so (libc6) => 
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so
> libgcc_s.so (libc6) => 
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so
> 
> What do you have?
> 
> 
> # ldconfig -p | grep libgcc
> libgcc_s.so.1 (libc6,x86-64) => /lib64/libgcc_s.so.1
> libgcc_s.so.1 (libc6,x86-64) => 
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so.1
> libgcc_s.so.1 (libc6,x86-64) => 
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so.1
> libgcc_s.so.1 (libc6) => 
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so.1
> libgcc_s.so.1 (libc6) => 
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so.1
> libgcc_s.so (libc6,x86-64) => 
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/libgcc_s.so
> libgcc_s.so (libc6,x86-64) => 
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so
> libgcc_s.so (libc6) => 
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/32/libgcc_s.so
> libgcc_s.so (libc6) => 
> /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so
> 
> # ls -l /lib64/libgcc_s.so.1
> lrwxrwxrwx 1 root root 28 May 17 19:11 /lib64/libgcc_s.so.1 -> 
> libgcc_s-4.7.2-20121109.so.1
> 
> Crufty Will it be safe to delete the link since the file is found in the 
> other locations?

Yes, then run ldconfig afterwards.

Re: [gentoo-user] Re: gcc4.7.2-r1 to 4.7.3 upgrade - hosed system?

[Adam Carter]

>
> > # ls -l /lib64/libgcc_s.so.1
> > lrwxrwxrwx 1 root root 28 May 17 19:11 /lib64/libgcc_s.so.1 ->
> libgcc_s-4.7.2-20121109.so.1
> >
> > Crufty Will it be safe to delete the link since the file is found in
> the other locations?
>
> Yes, then run ldconfig afterwards.
>
>
Thanks - gcc-config 2 runs cleanly now.

Re: [gentoo-user] Re: [gentoo-user] Alsa Question

[Silvio Siefke]

Hello,

On Fri, 17 May 2013 22:34:17 +0400 the guard  wrote:

> I beleive that if you build the sound card driver into kernel alsa
> cann have problems detecting the card. but once alsa has detected the
> card it should have no difference weather you built it into kernel or
> not.

That's my kernel config, the relevant stuff:

siefke@gentoo-mobile : ~ $ cat /usr/src/linux/.config | grep CONFIG_SND
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_HWDEP=y
CONFIG_SND_RAWMIDI=y
CONFIG_SND_JACK=y
CONFIG_SND_SEQUENCER=y
CONFIG_SND_OSSEMUL=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_HRTIMER=y
CONFIG_SND_SEQ_HRTIMER_DEFAULT=y
CONFIG_SND_DYNAMIC_MINORS=y
CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
CONFIG_SND_VMASTER=y
CONFIG_SND_KCTL_JACK=y
CONFIG_SND_DMA_SGBUF=y
CONFIG_SND_RAWMIDI_SEQ=y
CONFIG_SND_OPL3_LIB_SEQ=y
CONFIG_SND_OPL4_LIB_SEQ=y
CONFIG_SND_SBAWE_SEQ=y
CONFIG_SND_MPU401_UART=y
CONFIG_SND_OPL3_LIB=y
CONFIG_SND_OPL4_LIB=y
CONFIG_SND_AC97_CODEC=y
CONFIG_SND_DRIVERS=y
CONFIG_SND_PCSP=y
CONFIG_SND_DUMMY=y
CONFIG_SND_ALOOP=y
CONFIG_SND_VIRMIDI=y
CONFIG_SND_AC97_POWER_SAVE=y
CONFIG_SND_AC97_POWER_SAVE_DEFAULT=0
CONFIG_SND_WSS_LIB=y
CONFIG_SND_SB_COMMON=y
CONFIG_SND_SB8_DSP=y
CONFIG_SND_SB16_DSP=y
CONFIG_SND_ISA=y
CONFIG_SND_ADLIB=y
CONFIG_SND_AD1816A=y
CONFIG_SND_AD1848=y
CONFIG_SND_ALS100=y
CONFIG_SND_AZT1605=y
CONFIG_SND_AZT2316=y
CONFIG_SND_AZT2320=y
CONFIG_SND_CMI8330=y
CONFIG_SND_CS4231=y
CONFIG_SND_CS4236=y
CONFIG_SND_ES1688=y
CONFIG_SND_ES18XX=y
CONFIG_SND_SC6000=y
CONFIG_SND_GUSCLASSIC=y
CONFIG_SND_GUSEXTREME=y
CONFIG_SND_GUSMAX=y
CONFIG_SND_INTERWAVE=y
CONFIG_SND_INTERWAVE_STB=y
CONFIG_SND_JAZZ16=y
CONFIG_SND_OPL3SA2=y
CONFIG_SND_OPTI92X_AD1848=y
CONFIG_SND_OPTI92X_CS4231=y
CONFIG_SND_OPTI93X=y
CONFIG_SND_MIRO=y
CONFIG_SND_SB8=y
CONFIG_SND_SB16=y
CONFIG_SND_SBAWE=y
CONFIG_SND_SB16_CSP=y
CONFIG_SND_SSCAPE=y
CONFIG_SND_WAVEFRONT=y
CONFIG_SND_MSND_PINNACLE=y
CONFIG_SND_MSND_CLASSIC=y
CONFIG_SND_PCI=y
CONFIG_SND_HDA_INTEL=y
CONFIG_SND_HDA_PREALLOC_SIZE=64
CONFIG_SND_HDA_HWDEP=y
CONFIG_SND_HDA_RECONFIG=y
CONFIG_SND_HDA_INPUT_BEEP=y
CONFIG_SND_HDA_INPUT_BEEP_MODE=0
CONFIG_SND_HDA_INPUT_JACK=y
CONFIG_SND_HDA_PATCH_LOADER=y
CONFIG_SND_HDA_CODEC_REALTEK=y
CONFIG_SND_HDA_ENABLE_REALTEK_QUIRKS=y
CONFIG_SND_HDA_CODEC_ANALOG=y
CONFIG_SND_HDA_CODEC_SIGMATEL=y
CONFIG_SND_HDA_CODEC_VIA=y
CONFIG_SND_HDA_CODEC_HDMI=y
CONFIG_SND_HDA_CODEC_CIRRUS=y
CONFIG_SND_HDA_CODEC_CONEXANT=y
CONFIG_SND_HDA_CODEC_CA0110=y
CONFIG_SND_HDA_CODEC_CA0132=y
CONFIG_SND_HDA_CODEC_CMEDIA=y
CONFIG_SND_HDA_CODEC_SI3054=y
CONFIG_SND_HDA_GENERIC=y
CONFIG_SND_INTEL8X0=y
CONFIG_SND_SPI=y
CONFIG_SND_USB=y
CONFIG_SND_USB_AUDIO=y
CONFIG_SND_USB_UA101=y
CONFIG_SND_USB_USX2Y=y
CONFIG_SND_USB_CAIAQ=y
CONFIG_SND_USB_CAIAQ_INPUT=y
CONFIG_SND_USB_US122L=y
CONFIG_SND_SOC=y
CONFIG_SND_SOC_I2C_AND_SPI=y
CONFIG_SND_SOC_ALL_CODECS=y
CONFIG_SND_SOC_88PM860X=y
CONFIG_SND_SOC_WM_HUBS=y
CONFIG_SND_SOC_AD1836=y
CONFIG_SND_SOC_AD193X=y
CONFIG_SND_SOC_AD73311=y
CONFIG_SND_SOC_ADAU1373=y
CONFIG_SND_SOC_ADAV80X=y
CONFIG_SND_SOC_ADS117X=y
CONFIG_SND_SOC_AK4104=y
CONFIG_SND_SOC_AK4535=y
CONFIG_SND_SOC_AK4641=y
CONFIG_SND_SOC_AK4642=y
CONFIG_SND_SOC_AK4671=y
CONFIG_SND_SOC_ALC5623=y
CONFIG_SND_SOC_ALC5632=y
CONFIG_SND_SOC_CS42L51=y
CONFIG_SND_SOC_CS42L73=y
CONFIG_SND_SOC_CS4270=y
CONFIG_SND_SOC_CS4271=y
CONFIG_SND_SOC_CX20442=y
CONFIG_SND_SOC_JZ4740_CODEC=y
CONFIG_SND_SOC_L3=y
CONFIG_SND_SOC_DA7210=y
CONFIG_SND_SOC_DFBMCS320=y
CONFIG_SND_SOC_MAX98088=y
CONFIG_SND_SOC_MAX98095=y
CONFIG_SND_SOC_MAX9850=y
CONFIG_SND_SOC_PCM3008=y
CONFIG_SND_SOC_RT5631=y
CONFIG_SND_SOC_SGTL5000=y
CONFIG_SND_SOC_SPDIF=y
CONFIG_SND_SOC_SSM2602=y
CONFIG_SND_SOC_STA32X=y
CONFIG_SND_SOC_TLV320AIC23=y
CONFIG_SND_SOC_TLV320AIC26=y
CONFIG_SND_SOC_TLV320AIC32X4=y
CONFIG_SND_SOC_TLV320AIC3X=y
CONFIG_SND_SOC_TLV320DAC33=y
CONFIG_SND_SOC_UDA134X=y
CONFIG_SND_SOC_UDA1380=y
CONFIG_SND_SOC_WM1250_EV1=y
CONFIG_SND_SOC_WM2000=y
CONFIG_SND_SOC_WM2200=y
CONFIG_SND_SOC_WM5100=y
CONFIG_SND_SOC_WM8350=y
CONFIG_SND_SOC_WM8510=y
CONFIG_SND_SOC_WM8523=y
CONFIG_SND_SOC_WM8580=y
CONFIG_SND_SOC_WM8711=y
CONFIG_SND_SOC_WM8727=y
CONFIG_SND_SOC_WM8728=y
CONFIG_SND_SOC_WM8731=y
CONFIG_SND_SOC_WM8737=y
CONFIG_SND_SOC_WM8741=y
CONFIG_SND_SOC_WM8750=y
CONFIG_SND_SOC_WM8753=y
CONFIG_SND_SOC_WM8770=y
CONFIG_SND_SOC_WM8776=y
CONFIG_SND_SOC_WM8782=y
CONFIG_SND_SOC_WM8804=y
CONFIG_SND_SOC_WM8900=y
CONFIG_SND_SOC_WM8903=y
CONFIG_SND_SOC_WM8904=y
CONFIG_SND_SOC_WM8940=y
CONFIG_SND_SOC_WM8955=y
CONFIG_SND_SOC_WM8960=y
CONFIG_SND_SOC_WM8961=y
CONFIG_SND_SOC_WM8962=y
CONFIG_SND_SOC_WM8971=y
CONFIG_SND_SOC_WM8974=y
CONFIG_SND_SOC_WM8978=y
CONFIG_SND_SOC_WM8983=y
CONFIG_SND_SOC_WM8985=y
CONFIG_SND_SOC_WM8988=y
CONFIG_SND_SOC_WM8990=y
CONFIG_SND_SOC_WM8991=y
CONFIG_SND_SOC_WM8993=y
CONFIG_SND_SOC_WM8994=y
CONFIG_SND_SOC_WM8995=y
CONFIG_SND_SOC_WM8996=y
CONFIG_SND_SOC_WM9081=y
CONFIG_SND_SOC_WM9090=y
CONFIG_SND_SOC_LM4857=y
CONFIG_SND_SOC_MAX9768=y
CONFIG_SND_SOC_MAX9877=y
CONFIG_SND_SOC_TPA6130A2=y

So

Re: [gentoo-user] Booting LiveCD iso from hard drive with GRUB legacy

[Mick]

On Saturday 18 May 2013 10:08:51 tastytea wrote:
> On Sat, 18 May 2013 09:15:44 +0100
> 
> Mick  wrote:
> > Hi All,
> > 
> > Is there a way of achieving this?
> 
> Hi,
> Maybe it works with chainloader?
> See "info grub" for more information.

Thanks, but I don't know if there is a way to point grub legacy to a 
particular partition, other than boot, to select an ISO from it.  My /boot 
partition is not large enough for a LiveDVD ISO file.  Plus, I'm not sure that 
GRUB legacy can mount an ISO as a loopback device.

When I tried:

root (hd0,10)
makeactive
chainloader /KNOPPIX_V7.0.5DVD-2012-12-21-EN.iso


I got:  Error 12, no suitable device found (or similar).  

-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Alsa Question

[Silvio Siefke]

Hello,


i have found the problem, i has create the .asoundrc with content:

siefke@gentoo-mobile : ~ $ cat .asoundrc 
pcm.!default {
type hw
card Intel
}
ctl.!default {
type hw
card Intel
}

Now have sound in Opera and in Mplayer. I have read the Howto from
Arch. 


Thanks all & Nice weekend
Silvio

Re: [gentoo-user] Booting LiveCD iso from hard drive with GRUB legacy

[Michael Hampicke]

Am 18.05.2013 10:15, schrieb Mick:
> Hi All,
> 
> Is there a way of achieving this?
> 

Grub legacy usually cannot boot iso images, but you could try
chainloading another bootloader from grub, which is able to boot an iso
file. Maybe let grub chainload grub2 which can boot isos.



signature.asc
Description: OpenPGP digital signature

RE: [gentoo-user] Booting LiveCD iso from hard drive with GRUB legacy

[Ivan T. Ivanov]

Hi, 

> 
> On Saturday 18 May 2013 10:08:51 tastytea wrote:
> > On Sat, 18 May 2013 09:15:44 +0100
> >
> > Mick  wrote:
> > > Hi All,
> > >
> > > Is there a way of achieving this?
> >
> > Hi,
> > Maybe it works with chainloader?
> > See "info grub" for more information.
> 
> Thanks, but I don't know if there is a way to point grub legacy to a
> particular partition, other than boot, to select an ISO from it.  My /boot
> partition is not large enough for a LiveDVD ISO file.  Plus, I'm not sure that
> GRUB legacy can mount an ISO as a loopback device.
> 
> When I tried:
> 
> root (hd0,10)
> makeactive
> chainloader /KNOPPIX_V7.0.5DVD-2012-12-21-EN.iso
> 
> 
> I got:  Error 12, no suitable device found (or similar).

I do have following in my grub/menu.lst and it is working fine.

title PC-Doctor DOS
root (hd0,0)
kernel /boot/memdisk iso
initrd /boot/pcdoctor.iso

This is sys-boot/grub 0.97-r12

Regards,
Ivan

> 
> --
> Regards,
> Mick

Re: [gentoo-user] Alsa Question (alsaconf R.I.P.)

[Mick]

On Saturday 18 May 2013 09:39:36 Samuli Suominen wrote:
> On 17/05/13 21:30, Silvio Siefke wrote:
> >  (generated by alsaconf)
> 
> Gentoo's alsa-guide.xml is outdated and is incorrectly suggesting the
> use of alsaconf
> 
> When in reality alsaconf doesn't work at all with sys-apps/kmod because
> it doesn't generate 'modules.pcimap' and 'modules.usbmap' files anymore
> 
> And in version 1.0.27 of alsa-utils in ~arch the command is no longer
> being installed
> 
> So whatever you do, forget about `alsaconf` right from the start, since
> it's no longer required with modern PCI, USB, ... cards because
> sys-fs/udev automatically loads the required drivers
> The `alsaconf` command has been useful only for old PCMCIA and ISA cards
> for years already
> 
> Instead you don't do anything else than unmute the mixers using
> alsamixer, and leave the module loading to udev
> 
> As in, edit/write /etc/modprobe.d/alsa.conf by hand only if you need to
> pass some options to the modules

I am still running media-sound/alsa-utils-1.0.26-r2 here and a couple of 
months or so ago I tried rebuilding all sound modules in the kernel, only to 
confirm that some devices were again no longer available.  Building them as 
modules restored them back as they were.  So for my setting at least I have 
stayed with sound built separately as modules.
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Booting LiveCD iso from hard drive with GRUB legacy

[Mick]

On Saturday 18 May 2013 16:11:13 Ivan T. Ivanov wrote:

> I do have following in my grub/menu.lst and it is working fine.
> 
> title PC-Doctor DOS
> root (hd0,0)
> kernel /boot/memdisk iso
> initrd /boot/pcdoctor.iso
> 
> This is sys-boot/grub 0.97-r12

I'm on the same GRUB version.

Unfortunately, I don't have enough space to place the ISO in the /boot 
partition and I don't use an initrd.

Trying this stanza:

title KNOPPIX ISO
root (hd0,9)<-- this is my current boot partition <--
chainloader (hd0,10)/KNOPPIX_V7.0.5DVD-2012-12-21-EN.iso

Gives me this error:  Error 13:  Invalid or unsupported executable format, 
which tells me that it doesn't like/recognise the particular ISO image.

Trying to understand your grub entry - what is /boot/memdisk?  Have you built 
some eltorito image for your purpose?  How does it work?
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Booting LiveCD iso from hard drive with GRUB legacy

[Walter Dnes]

On Sat, May 18, 2013 at 09:15:44AM +0100, Mick wrote
> Hi All,
> 
> Is there a way of achieving this?

  I don't think so.  Can your system boot from a USB stick?  If so, see
https://wiki.archlinux.org/index.php/USB_Installation_Media for
instructions on how to make a CD ISO bootable off a USB stick.  Note
that this is for legacy boot.  For UEFI boot, see
https://wiki.archlinux.org/index.php/UEFI#Create_UEFI_bootable_USB_from_ISO

1) If you haven't already done so "emerge sys-boot/syslinux" to get the
"isohybrid" command.

2) Get a USB stick.  *WARNING* all data on the stick will be erased

3) Assume the ISO is install-amd64-minimal-20130516.iso  Execute the
command

isohybrid install-amd64-minimal-20130516.iso

4) Insert the USB stick.  *DO NOT MOUNT IT*.  Unmount it manually if you
have an automounter.

5) As root, execute the command...

dd bs=4M if=install-amd64-minimal-20130516.iso of=/dev/sdx

...where sdx is the USB stick (e.g. sdb or sdc or whatever)
   - be careful not to overwrite the wrong device
   - yes, it's sdx, not sdx1

6) You now have a bootable USB stick

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] Alsa Question (alsaconf R.I.P.)

[covici]

Mick  wrote:

> On Saturday 18 May 2013 09:39:36 Samuli Suominen wrote:
> > On 17/05/13 21:30, Silvio Siefke wrote:
> > >  (generated by alsaconf)
> > 
> > Gentoo's alsa-guide.xml is outdated and is incorrectly suggesting the
> > use of alsaconf
> > 
> > When in reality alsaconf doesn't work at all with sys-apps/kmod because
> > it doesn't generate 'modules.pcimap' and 'modules.usbmap' files anymore
> > 
> > And in version 1.0.27 of alsa-utils in ~arch the command is no longer
> > being installed
> > 
> > So whatever you do, forget about `alsaconf` right from the start, since
> > it's no longer required with modern PCI, USB, ... cards because
> > sys-fs/udev automatically loads the required drivers
> > The `alsaconf` command has been useful only for old PCMCIA and ISA cards
> > for years already
> > 
> > Instead you don't do anything else than unmute the mixers using
> > alsamixer, and leave the module loading to udev
> > 
> > As in, edit/write /etc/modprobe.d/alsa.conf by hand only if you need to
> > pass some options to the modules
> 
> I am still running media-sound/alsa-utils-1.0.26-r2 here and a couple of 
> months or so ago I tried rebuilding all sound modules in the kernel, only to 
> confirm that some devices were again no longer available.  Building them as 
> modules restored them back as they were.  So for my setting at least I have 
> stayed with sound built separately as modules.

Also, I had to use the install feature of modprobe to get the modules to
load correctly as udev did not load all the required modules.  Before it
was done by an init script.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici
 cov...@ccs.covici.com

[gentoo-user] Re: Logitech MX620 mouse

[Steven J. Long]

On Sat, May 18, 2013 at 10:57:40AM +0200, Stefan G. Weichinger wrote:
> Am 18.05.2013 00:57, schrieb John Campbell:
> 
> > Take a look at imwheel.  It's a little unmaintained but it still works.
> >  I've used it on an old MX1000 and my current PreformanceMX.
> > 
> > You can set mouse buttons on a per window/program basis to have
> > different effects for whichever window has focus.  Thus "search" for
> > Firefox and "paste" for Thunderbird.
> > 
> > You also might need lomoco to turn on the button.  I remember with my
> > MX1000, I had to enable the two scroll wheels as buttons.  Otherwise
> > they were used by the mouse to "scroll fast" which I found pretty useless.
> 
> thanks for the suggestions!
> 
> We were successful with btnx yesterday ... and now we don't touch it
> anymore (as long as it still works).

Just for posterity's sake, would you mind posting how you configured it, for
anyone searching for help on the same thing?

I don't have an MX620, but I do love Logitech trackballs, and am interested in
configuration settings for this stuff. I was looking at the Kensington one
with a turn-wheel, but settled on my old faithful Trackman Marble for recent
replacement. I really just want something like that with a wheel, but the
ones I saw didn't do it for me. In any case, at some point i'm going to have
to deal with a more complex device, so I'd like to see what kind of thing
you needed to configure (never heard of btnx.)

Thanks,
steveL
-- 
#friendly-coders -- We're friendly, but we're not /that/ friendly ;-)