OK, I made the jump from 10.1 to 10.2 and like most of the new upgrade.
Yast seems to work properly, and actually seems efficient again.

However, I am having a real problem with my HP PSC 2210 Scanner/printer
combi. It just does not appear to be seen by the print manager.

It is connected via USB to my SUSE 10.2 m/c and will run a "hello world"
test, ONLY ONCE! Then its as if something locks up and it sits there
with jobs queing up, but no output.

If I reboot into XP, or 10.1 there is no problem with the printer or
connection.

SUSE 10.2 has worked with this printer albeit only during the test
sequence, and nothing since...

Any ideas... I have tried to re-install it with YAST and KDE peripherals....

TIA

Chris

christine wrote:
> OK, I made the jump from 10.1 to 10.2 and like most of the new upgrade.
> Yast seems to work properly, and actually seems efficient again.
>
> However, I am having a real problem with my HP PSC 2210 Scanner/printer
> combi. It just does not appear to be seen by the print manager.
>
> It is connected via USB to my SUSE 10.2 m/c and will run a "hello world"
> test, ONLY ONCE! Then its as if something locks up and it sits there
> with jobs queing up, but no output.
>
> If I reboot into XP, or 10.1 there is no problem with the printer or
> connection.
>
> SUSE 10.2 has worked with this printer albeit only during the test
> sequence, and nothing since...
>
> Any ideas... I have tried to re-install it with YAST and KDE
> peripherals....
>
> TIA
>
> Chris

It may be the USB as such.

I lost USB functionality with 10.2.
I got that on three different machines.

Installing 10.0 back brings back the USB here.

There's a bug filed on this in Bugzilla.


--
Vahis
Motorcycling, Boating and openSUSE: http://waxborg.servepics.com
"Why wait any longer for the world to begin?
You can have your cake and eat it, too." Bob Dylan

Vahis wrote:
> christine wrote:
>> OK, I made the jump from 10.1 to 10.2 and like most of the new upgrade.
>> Yast seems to work properly, and actually seems efficient again.
>>
>> However, I am having a real problem with my HP PSC 2210 Scanner/printer
>> combi. It just does not appear to be seen by the print manager.
>>
>> It is connected via USB to my SUSE 10.2 m/c and will run a "hello world"
>> test, ONLY ONCE! Then its as if something locks up and it sits there
>> with jobs queing up, but no output.
>>
>> If I reboot into XP, or 10.1 there is no problem with the printer or
>> connection.
>>
>> SUSE 10.2 has worked with this printer albeit only during the test
>> sequence, and nothing since...
>>
>> Any ideas... I have tried to re-install it with YAST and KDE
>> peripherals....
>>
>> TIA
>>
>> Chris
>
> It may be the USB as such.
>
> I lost USB functionality with 10.2.
> I got that on three different machines.
>
> Installing 10.0 back brings back the USB here.
>
> There's a bug filed on this in Bugzilla.
>
>
I kinda suspect you may be right. At an earlier point today, I got a
message saying there was a problem with the USB port. The printer is
detected, and like I say, it has "hello world" etc. But then it fails.
ITSELF HAS GONE TO SLEEP.... I will wait a while and watch...

Thanks

Vahis wrote:
> There's a bug filed on this in Bugzilla.

It is always nice to give the bugnumber so people can see and/or follow
and/or participate in the solution. Sometimes one could say that
searching for the bug is an option, yet most of the time when I try to
do that, I end up with following the wrong bug, so please what is the
bugnumber?

houghi
--
> Beware of he who would deny you access to information, <
> for in his heart he dreams himself your master. <
> Commissioner Pravin Lal: "U.N. Declaration of Rights" <

houghi wrote:
> Vahis wrote:
>> There's a bug filed on this in Bugzilla.
>
> It is always nice to give the bugnumber so people can see and/or follow
> and/or participate in the solution. Sometimes one could say that
> searching for the bug is an option, yet most of the time when I try to
> do that, I end up with following the wrong bug, so please what is the
> bugnumber?
>
> houghi

#225135

--
Vahis
Motorcycling, Boating and openSUSE: http://waxborg.servepics.com
"Why wait any longer for the world to begin?
You can have your cake and eat it, too." Bob Dylan

VMware Workstation 5.5.3 (the latest release) does not have USB access
under openSUSE 10.2 because the openSUSE developers have decided to
change the way USB works in the kernel. Apparently, openSUSE 10.2 is the
only distro to have made this decision so far. Security is quoted as the
reason.

I don't know enough to evaluate this decision but I may have to stay
with 10.1 when I get my next PC or go to a distro that has more concern
for its users. Since SuSE went 'open' or 'community', the usual controls
seem to have been abandoned. First, we get a broken package manager;
now, we get broken USB. What next?

All of this reminds me of a company that resides in Redmond...

J L Strider wrote:
> VMware Workstation 5.5.3 (the latest release) does not have USB access
> under openSUSE 10.2 because the openSUSE developers have decided to
> change the way USB works in the kernel. Apparently, openSUSE 10.2 is the
> only distro to have made this decision so far. Security is quoted as the
> reason.

It's not only in VMWare. The USB is crippled also in native 10.2.

In VMWare if the host is 10.0 the guests can use USB as long as they
are not 10.2. If the guest is 10.2 it has not USB.

If the host is 10.2 nobody uses USB, not the host itself or the guests.

>
> I don't know enough to evaluate this decision but I may have to stay
> with 10.1 when I get my next PC or go to a distro that has more concern
> for its users. Since SuSE went 'open' or 'community', the usual controls
> seem to have been abandoned. First, we get a broken package manager;
> now, we get broken USB. What next?
>
> All of this reminds me of a company that resides in Redmond...

I don't know about that, on 10.0 host, the Redmond guest in VMWare uses
USB just like the rest, 10.2 being the only exception.

No USB => no can do.
If USB don't come back, Suse will go.
I still believe that this is a temporary condition.


--
Vahis
Motorcycling, Boating and openSUSE: http://waxborg.servepics.com
"Why wait any longer for the world to begin?
You can have your cake and eat it, too." Bob Dylan

Vahis wrote:
> It's not only in VMWare. The USB is crippled also in native 10.2.

What I find odd is that I see so little complaints about this. If it
were crippled, then almost nobody would have been able to mount their
devices. Also I would think that this would have been noticed in RC1.

So the word 'crippled' is a bit strong. I would say 'a bug'

Bug 225135 talks mainly about automounting. Some devices can be mounted
manualy. I am going to do a 10.2 installation and go after this as well.
See you in a couple of hours.

houghi
--
From the day the male foetus' hands grow long enough to grasp at their 'third
leg', until the man in question is dead and buried, the penis is a constant
source of amusement and amazement to those of the male gender.
http://www.bbc.co.uk/dna/h2g2/A219061

houghi wrote:
> Bug 225135 talks mainly about automounting. Some devices can be mounted
> manualy. I am going to do a 10.2 installation and go after this as well.
> See you in a couple of hours.

This was the fastestest installation EVER. :-) Seriously, I rememberd I
still had a 10.2 installation on HDA that was prety clean, so I loaded
that up, mounted /home and plugged in my two USB devices.

Wassayaknow? They both worked flawlessly. It was a KDE installation (I
ran Windowmaker)
So first it is nice to see that automounter works under Windowmaker. I
thought it wouldn't. Second I have no problem. So now I will do a GNOME
based installation and see if there is any differnce.

houghi
--
From the day the male foetus' hands grow long enough to grasp at their 'third
leg', until the man in question is dead and buried, the penis is a constant
source of amusement and amazement to those of the male gender.
http://www.bbc.co.uk/dna/h2g2/A219061

In the discussion on bug #210899, Greg Kroah-Hartman wrote (2006-10-07
13:56:05 MST):

'As for security issues, it is impossible to properly set the
permissions of the usb devices in the /proc/bus/usb/ directory, that is
why we do not mount it anymore, and have not done so since the last
release. It is simple to just use the /dev/bus/usb/ device nodes
instead, which obtain the proper permissions depending on the user that
is logged into the machine.

All applications that link against libusb already work properly, so
vmware should also work if it uses libusb. If there are still problems,
I suggest you contact them, as there is not much we can do about this.'

As I read this, only USB access that relies on /proc/bus/usb will fail.
That includes VMware Workstation up to and including 5.5.3. If this
really is a security issue, all distros will be affected eventually
(presumably, Linus et al will change _the_ kernel just as openSUSE has -
or will they?).

The way this has been done is rather M$-like: the first we hear about
the problem is when users who have installed 10.2 start complaining that
USB doesn't work in VMware Workstation any more. The problems with
package management in 10.1 came to light in a similar way. To my mind,
the response of the developers is 'purist' rather than user-orientated.

Now, I'm not a guru or expert - I'm just a user who wants to run VMware
under Linux and who has hitherto found that SuSE suited me fine. With
the help of others, I circumvented the package-manager problems in 10.1
by using SMART. Now, I'm faced with another set of problems. Just as
Linux is becoming really useful as a desktop system, just as drivers are
becoming available reasonably quickly, the openSUSE developers decide to
make things difficult again!