my remaining problems with 2009.0 rc2 are: - Mandriva

This is a discussion on my remaining problems with 2009.0 rc2 are: - Mandriva ; 1) Whenever I boot up, both wired Ethernet and wireless are OFF and have to be re-connected. 2) Whenever I boot up I get a message saying "The audio playback device doesn't work" 2) Bluetooth routines do not respond to ...

+ Reply to Thread
Results 1 to 12 of 12

Thread: my remaining problems with 2009.0 rc2 are:

  1. my remaining problems with 2009.0 rc2 are:

    1) Whenever I boot up, both wired Ethernet and wireless are OFF and
    have to be re-connected.

    2) Whenever I boot up I get a message saying "The audio playback device
    doesn't work"

    2) Bluetooth routines do not respond to nearby devices.

    3) xsane - This may be unrelated to rc2 but its initial window comes up and
    shows the expected devices but aborts when the network scanner is selected
    although the latter's LCD screen brightens up as it does whenever it is
    addressed.

    This is a Brother device and their network drivers usually work out of the
    box. Access from my desktop worked first time but the EEE/2009.0 rc2 will
    not.

    4) None of the VMware server systems currently available (1.0.6, 1.0.7 or
    2.0 will even configure. Neither would virtualbox.

    Not a huge list but we're very close to final release.



  2. Re: my remaining problems with 2009.0 rc2 are:

    Alan Secker wrote:

    > 1) Whenever I boot up, both wired Ethernet and wireless are OFF and
    > have to be re-connected.
    >
    > 2) Whenever I boot up I get a message saying "The audio playback device
    > doesn't work"
    >
    > 2) Bluetooth routines do not respond to nearby devices.
    >
    > 3) xsane - This may be unrelated to rc2 but its initial window comes up
    > and shows the expected devices but aborts when the network scanner is
    > selected although the latter's LCD screen brightens up as it does whenever
    > it is addressed.
    >
    > This is a Brother device and their network drivers usually work out of the
    > box. Access from my desktop worked first time but the EEE/2009.0 rc2 will
    > not.
    >
    > 4) None of the VMware server systems currently available (1.0.6, 1.0.7 or
    > 2.0 will even configure. Neither would virtualbox.
    >
    > Not a huge list but we're very close to final release.



    KDE4?

  3. Re: my remaining problems with 2009.0 rc2 are:

    F8BOE wrote:

    > Alan Secker wrote:
    >
    >> 1) Whenever I boot up, both wired Ethernet and wireless are OFF and
    >> have to be re-connected.
    >>
    >> 2) Whenever I boot up I get a message saying "The audio playback device
    >> doesn't work"
    >>
    >> 2) Bluetooth routines do not respond to nearby devices.
    >>
    >> 3) xsane - This may be unrelated to rc2 but its initial window comes up
    >> and shows the expected devices but aborts when the network scanner is
    >> selected although the latter's LCD screen brightens up as it does
    >> whenever it is addressed.
    >>
    >> This is a Brother device and their network drivers usually work out of
    >> the box. Access from my desktop worked first time but the EEE/2009.0 rc2
    >> will not.
    >>
    >> 4) None of the VMware server systems currently available (1.0.6, 1.0.7 or
    >> 2.0 will even configure. Neither would virtualbox.
    >>
    >> Not a huge list but we're very close to final release.

    >
    >
    > KDE4?


    See the thread Mandriva 2009.0 and KDE 4.


  4. Re: my remaining problems with 2009.0 rc2 are:

    Alan Secker wrote:

    > 3) xsane - This may be unrelated to rc2 but its initial window comes up
    > and shows the expected devices but aborts when the network scanner is
    > selected although the latter's LCD screen brightens up as it does whenever
    > it is addressed.
    >

    I have a Brother device (mfc) and I use the scanner driver from Brother's
    Web site. *There are RPM and .deb versions available. *It sounds as though
    yours has a printer server built in. *There is an example CUPS config at
    the site for that. *I printed it out for my next printer.

    Doug.
    --
    Success is getting what you want. Happiness is liking what you get.
    - Anonymous


  5. Re: my remaining problems with 2009.0 rc2 are:

    Alan Secker wrote:

    > 1) Whenever I boot up, both wired Ethernet and wireless are OFF and
    > have to be re-connected.
    >
    > 2) Whenever I boot up I get a message saying "The audio playback device
    > doesn't work"
    >
    > 2) Bluetooth routines do not respond to nearby devices.
    >
    > 3) xsane - This may be unrelated to rc2 but its initial window comes up
    > and shows the expected devices but aborts when the network scanner is
    > selected although the latter's LCD screen brightens up as it does whenever
    > it is addressed.
    >
    > This is a Brother device and their network drivers usually work out of the
    > box. Access from my desktop worked first time but the EEE/2009.0 rc2 will
    > not.
    >
    > 4) None of the VMware server systems currently available (1.0.6, 1.0.7 or
    > 2.0 will even configure. Neither would virtualbox.
    >
    > Not a huge list but we're very close to final release.


    I may be a little off topic here, but if you can try this it should show an
    on-going bug that is easy to fix but seems to be ever present in each
    release.
    Plug in any logitech mouse and then review the installed udev rules
    80-logitech-mouse.rules file in /etc/udev/rules.d
    The conditions are using the single '=' but should be using the double '=='
    which produces a whole bunch of 'invalid subsystem' rules errors on boot.

    Example of bad rule:
    BUS="usb", SYSFS{idVendor}="046d", SYSFS{idProduct}="c024",
    PROGRAM="/etc/udev/scripts/logitech-mouse.sh %s{idProduct}"
    ^ single '=' here is correct
    Example of rule thats been fixed:
    BUS=="usb", SYSFS{idVendor}=="046d", SYSFS{idProduct}=="c024",
    PROGRAM="/etc/udev/scripts/logitech-mouse.sh %s{idProduct}"
    Thanks
    Eric


  6. udev rules for logitech usb mice

    On Sun, 28 Sep 2008 22:09:55 -0400, Eric wrote:

    > I may be a little off topic here, but if you can try this it should show an
    > on-going bug that is easy to fix but seems to be ever present in each
    > release.


    It probably would have been better, if you started a new thread.

    > Plug in any logitech mouse and then review the installed udev rules
    > 80-logitech-mouse.rules file in /etc/udev/rules.d
    > The conditions are using the single '=' but should be using the double '=='
    > which produces a whole bunch of 'invalid subsystem' rules errors on boot.


    Have you reported the problem at http://qa.mandriva.com/index.cgi ?

    I suspect it's a problem upstream, rather then a mandriva problem, not
    that a user will care whose problem it is.

    Just fyi, my logitech ps/2 mouse works fine.

    Regards, Dave Hodgins

    --
    Change nomail.afraid.org to ody.ca to reply by email.
    (nomail.afraid.org has been set up specifically for
    use in usenet. Feel free to use it yourself.)

  7. Re: my remaining problems with 2009.0 rc2 are:

    Doug Laidlaw wrote:

    > Alan Secker wrote:
    >
    >> 3) xsane - This may be unrelated to rc2 but its initial window comes up
    >> and shows the expected devices but aborts when the network scanner is
    >> selected although the latter's LCD screen brightens up as it does
    >> whenever it is addressed.
    >>

    > I have a Brother device (mfc) and I use the scanner driver from Brother's
    > Web site. *There are RPM and .deb versions available. *It sounds as though
    > yours has a printer server built in. *There is an example CUPS config at
    > the site for that. *I printed it out for my next printer.
    >
    > Doug.


    Mine is an MFC too. It is connected by Ethernet cable to a Linksys ADSL
    Modem/Router as are the desktop and the EEE. I don't have a USB mouse and
    the EEE does not boast a PS/2 socket. I think a USB mouse would be useful
    anyway, so will add that to my shopping list. Unfortunately I cannot make
    further tests until the end of the week but for other reasons it has been
    suggested that I make a clean reinstall of the o/s and in addition I
    propose to copy the configuration file from the desktop to the EEE. That
    will prove whether it is finger trouble!

    Regards

    Alan




  8. Re: my remaining problems with 2009.0 rc2 are:

    Alan Secker wrote:

    > Doug Laidlaw wrote:
    >
    >> Alan Secker wrote:
    >>
    >>> 3) xsane - This may be unrelated to rc2 but its initial window comes up
    >>> and shows the expected devices but aborts when the network scanner is
    >>> selected although the latter's LCD screen brightens up as it does
    >>> whenever it is addressed.
    >>>

    >> I have a Brother device (mfc) and I use the scanner driver from Brother's
    >> Web site. *There are RPM and .deb versions available. *It sounds as
    >> though yours has a printer server built in. *There is an example CUPS
    >> config at the site for that. *I printed it out for my next printer.
    >>
    >> Doug.

    >
    > Mine is an MFC too. It is connected by Ethernet cable to a Linksys ADSL
    > Modem/Router as are the desktop and the EEE. I don't have a USB mouse and
    > the EEE does not boast a PS/2 socket. I think a USB mouse would be useful
    > anyway, so will add that to my shopping list. Unfortunately I cannot make
    > further tests until the end of the week but for other reasons it has been
    > suggested that I make a clean reinstall of the o/s and in addition I
    > propose to copy the configuration file from the desktop to the EEE. That
    > will prove whether it is finger trouble!
    >


    Alan

    Sort of on-topic: Re the eeePC, consider buying a 'USB to Mouse & Keyboard
    converter', i.e. 1 USB --> 2 PS/2 type sockets - M&K, rather than getting a
    USB mouse. I got a converter cable of that sort here in Australia for about
    AUD 27 - approx GBP 12 - you should be able to get one even cheaper than
    that in the UK given that AU prices tend to be on the high side.

    Rob.


  9. Re: my remaining problems with 2009.0 rc2 are:

    On Monday 29 September 2008 11:59, someone identifying as *Rob* wrote
    in /alt.os.linux.mandriva:/

    > Sort of on-topic: Re the eeePC, consider buying a 'USB to Mouse & Keyboard
    > converter', i.e. 1 USB --> 2 PS/2 type sockets - M&K, rather than getting
    > a USB mouse. I got a converter cable of that sort here in Australia for
    > about AUD 27 - approx GBP 12 - you should be able to get one even cheaper
    > than that in the UK given that AU prices tend to be on the high side.


    Just a FYI, but if you buy a Logitech mouse, those usually do come with a
    USB-to-PS/2 converter plug in the box. ;-)

    I actually find the whole paradigm of keyboards and mice being connected to
    a computer via USB quite silly when the motherboard has PS/2 connectors for
    both and you instead opt to leave them unused and waste one or two USB
    ports on your computer for a keyboard and mouse. ;-)

    I've got a Logitech MX-1000 cordless mouse. It's got a USB connector and it
    came with the PS/2 converter plug in the box. It's connected to the PS/2
    port on that machine. I'm using another converter plug for the Creative
    USB mouse on this one as well, although the Creative mouse did not come
    with the plug in the box. ;-)

    --
    *Aragorn*
    (registered GNU/Linux user #223157)

  10. Re: my remaining problems with 2009.0 rc2 are:

    Aragorn wrote:

    > On Monday 29 September 2008 11:59, someone identifying as *Rob* wrote
    > in /alt.os.linux.mandriva:/
    >
    >> Sort of on-topic: Re the eeePC, consider buying a 'USB to Mouse &
    >> Keyboard converter', i.e. 1 USB --> 2 PS/2 type sockets - M&K, rather
    >> than getting a USB mouse. I got a converter cable of that sort here in
    >> Australia for about AUD 27 - approx GBP 12 - you should be able to get
    >> one even cheaper than that in the UK given that AU prices tend to be on
    >> the high side.

    >
    > Just a FYI, but if you buy a Logitech mouse, those usually do come with a
    > USB-to-PS/2 converter plug in the box. ;-)
    >
    > I actually find the whole paradigm of keyboards and mice being connected
    > to a computer via USB quite silly when the motherboard has PS/2 connectors
    > for both and you instead opt to leave them unused and waste one or two USB
    > ports on your computer for a keyboard and mouse. ;-)
    >


    Aragorn

    I'd have to agree with you about wasting USB ports *if* you've got PS/2
    ports available. However, in the case of the eeePC, there are no PS/2 ports
    of any sort so a USB port is the only possibility if you want to use an
    external mouse and/or keyboard.

    About a new mouse coming with a USB-to-PS/2 converter, I had one of those
    when I bought an optical mouse. A few years ago I loaned it to one of my
    kids and that was the last I saw of it ;-/ [guess who is still using the
    old 'ball' mouse]

    Rob.

  11. Re: udev rules for logitech usb mice

    David W. Hodgins wrote:

    > On Sun, 28 Sep 2008 22:09:55 -0400, Eric wrote:
    >
    >> I may be a little off topic here, but if you can try this it should show
    >> an on-going bug that is easy to fix but seems to be ever present in each
    >> release.

    >
    > It probably would have been better, if you started a new thread.
    >
    >> Plug in any logitech mouse and then review the installed udev rules
    >> 80-logitech-mouse.rules file in /etc/udev/rules.d
    >> The conditions are using the single '=' but should be using the double
    >> '==' which produces a whole bunch of 'invalid subsystem' rules errors on
    >> boot.

    >
    > Have you reported the problem at http://qa.mandriva.com/index.cgi ?
    >
    > I suspect it's a problem upstream, rather then a mandriva problem, not
    > that a user will care whose problem it is.
    >
    > Just fyi, my logitech ps/2 mouse works fine.
    >
    > Regards, Dave Hodgins
    >

    It must be something plus a logitech mouse that causes these to be installed
    or updated, are your 80-logitech-mouse.rules syntactically correct? You
    dont see them using the single '=' in the condition tests?
    Eric

  12. Re: udev rules for logitech usb mice

    On Tue, 30 Sep 2008 19:08:35 -0400, Eric wrote:

    > It must be something plus a logitech mouse that causes these to be installed
    > or updated, are your 80-logitech-mouse.rules syntactically correct? You


    I don't have an 80-logitech-mouse.rules file. My ps/2 logitech wheel mouse
    is handled by /etc/udev/rules.d/50-udev-default.rules.

    The 80-logitech-mouse.rules is from the rpm package logitech-mouse-common,
    which is only for usb mouse devices. I just checked, and this bug has
    been reported. See
    https://qa.mandriva.com/show_bug.cgi?id=31483
    Take note of comment#4 pointing out the need to change
    /etc/udev/scripts/logitech-mouse.sh, as well as the udev rules.

    Regards, Dave Hodgins

    --
    Change nomail.afraid.org to ody.ca to reply by email.
    (nomail.afraid.org has been set up specifically for
    use in usenet. Feel free to use it yourself.)

+ Reply to Thread