[rivviepop]

Upgraded my laptop from F7 to F8 over the weekend, lo and behold my 8320 just plugs in, charges and works fine - no actual real work needed. It even resets the device to put it into the mode the barry tools will be looking for - here's the lsusb -v:

Bus 003 Device 003: ID 0fca:0004 Research In Motion, Ltd. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        16
  idVendor           0x0fca Research In Motion, Ltd.
  idProduct          0x0004 
  bcdDevice            1.06
  iManufacturer           1 Research In Motion
  iProduct                5 RIM Composite Device
  iSerial                 3 XXXXXXXXXXXXXXXXXXXXXXXXXXXX
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           97
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           8
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      1 
      bInterfaceProtocol    255 
      iInterface              2 BlackBerry
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x06  EP 6 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x87  EP 7 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x08  EP 8 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk (Zip)
      iInterface              4 RIM Mass Storage Device
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x89  EP 9 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x0a  EP 10 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0

I haven't gotten around to barry yet, but dang - I love the out of the box 'it just works' support we've got going on.

[*&))]

I have an 8830 and just upgrade to Fedora 8 and did not have the same results. I get the usual unable to charge message. "USB charging current is not sufficient. Verify that your handheld is connected to a powered USB charging source and that the proper USB driver is installed."

[rivviepop]

Originally Posted by *&))

I have an 8830 and just upgrade to Fedora 8 and did not have the same results. I get the usual unable to charge message. "USB charging current is not sufficient. Verify that your handheld is connected to a powered USB charging source and that the proper USB driver is installed."

Maybe (maybe) because the device ID is not recognized by the "berry_charge" kernel module, so you should submit a bug report (if there isn't one already) and Greg the maintainer will add it. Plug in your device and run (as root) 'lsusb -v >lsusb_output.txt" then take a look at that text file. What does the line "idProduct" say under the appropriate "Research in Motion" device entry?

For a Pearl and Curve that value is 0x0006 and for 8700 and older it's 0x0001; these are (to my knowledge) the only two idProducts the driver knows about. Is the 8830 a 0x0006 device?

Also, are you plugging into a hub or directly into the computer? If you're plugging intoa hub, try a direct connect to the PC as a test.

[rivviepop]

I didn't find any 8830 specific bugs in the bugbase, however you may wish to read this:

https://bugzilla.redhat.com/show_bug.cgi?id=379341

[LunkHead]

I am really liking openSuse 10.3 but cant resist giving FC8 a spin... DL'in the ISO as we speak... Should be done when I get off work, then gonna fire the bad boy up!!!

I love new distro releases

:woot: :woot:

How do you like rivvie....?

[rivviepop]

Originally Posted by LunkHead

How do you like rivvie....?

Not bad! Of course there are some initial dot-oh release headaches here and there that need to get ironed out, but I like the underpinnings. The new font system that ditches XFS completely is really nice, it's controlled now by a more traditional "SysV-like" method with an /etc/fonts/conf.d/ and /etc/X11/fontpath.d/ that is easier to tweak and grasp. I use a lot of fonts, it's really helping.

I don't care for the default theme, it lags a little - I created a minor custom hybrid version of it that uses the Clearlooks window decorations on top of the Nadoka theme (new default) and it's much better. I also replace the default fonts with the "Luxi" versions +1 point (so "Sans 10" becomes "Luxi Sans 11") for much enhanced readability on LCD screens.

Now that I've gotten things ironed out (I never upgrade, always wipe & install using an external USB drive to hold my home directory temporarily) I think it's a keeper.

[LunkHead]

Burning the ISO now and will be installing soon... I never upgrade anything either but then again, I change distro's almost as often as my underwear...

[LunkHead]

Wirelessly posted (BlackBerry 8320: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) BlackBerry8320/4.2.2 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/100)

Very impressed with FC8! Nice distro..

Had massive issues getting the DVD ISO to boot, it kept freezing up after grub.. Downloaded the GNOME live CD and it booted right up and installed with no further issues..

Spent a few hours downloading apps and setting everything up...

Will try hooking the BB up and see how it acts later tonight..

Overall, its a sweet distro and I plan on keeping it over openSuse...

Kris

[rivviepop]

Originally Posted by LunkHead

Had massive issues getting the DVD ISO to boot, it kept freezing up after grub.. Downloaded the GNOME live CD and it booted right up and installed with no further issues..

Same here! I used some combination of "noacpi acpi=off" type stuff on the boot commandline before it finally worked, and after install it didn't have any problems. I only experienced this boot issue on a Dell laptop (and others are as well), on my Thinkpad the install DVD booted right up and ran like a champ.

I haven't run into something like that in a long time, it's weird it made it past QA. Some of the people reporting the problem mentioned that it didn't happen in the 'Test' releases, so it looks like something done right before release. :-/

[LunkHead]

Update:

Plugged the BB into FC8 and..... Walla! It's a charging away!!!! SWEET!

[LunkHead]

Update:

Working like a champ in Linux Mint as well!!

Kris

[*&))]

Originally Posted by LunkHead

Update:

Working like a champ in Linux Mint as well!!

Kris

I have made the switch to Mint from Ubuntu and i must say I love it so thus far. Everything works, is a very sold performer and the community is great in two ways, you have a great mint community as well as being able to fall back on the Ubuntu community as well.

[LunkHead]

Mint is a very, very nice distro!

I am running E17 on top of it and it's works very nice as well... All the Mint extras are working well in E17...

Kris

[LunkHead]

Not that it would not BUT... Working like a CHAMP on E17 (Mint / Ubuntu 7.10) under the hood as well!!

Kris

[rivviepop]

Originally Posted by LunkHead

Not that it would not BUT... Working like a CHAMP on E17 (Mint / Ubuntu 7.10) under the hood as well!!

What's your uname -a output on that there Mint rig?

[LunkHead]

Ahhhhh....

Well now.... After double checking your request I see that if I log into gnome Mint 4.0 that it an a-ok with charging the BB...

However, if I am running the E17 it's a NO GO....

My bad.... Open mouth and insert my foot... I booted gnome and noticed I was a charging away... Saw your post and DUH....

I am NOT the brightest bulb in the pack!

You want me to post my Mint uname -a output???


Here is my E17:

 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

Kris

[LunkHead]

I wonder if I ran the standard Mint kernel with E17 on top (not compile the generic) if the BB would charge on E17 ...

Hummmm...... I have a mission for my days off....

Kris

[rivviepop]

Yeah you need 2.6.23+ kernel which has the latest berry_charge kernel module. E17 is just a window manager ("just" - hah) so I don't see any reason it couldn't run on top of Mint. Once you got all the bits installed into Mint you'd just have to start E17 instead of GNOME (I am not familiar with Ubuntu's take on "startx" but I'm sure it's similar to Fedora). I vaguely remember messing with E.... E14? a very, very (very) long time ago. That's about as close as I come to knowing much about it.

Another thought for E17: grab the latest berry_charge.c source code file from the kernel version control (or an official release tarball) and try hand compiling it, then hand copying it overtop the old one. I bet that might work, it sounds reasonable...

[LunkHead]

Yes I see your point... I will give it a try this weekend... I am running E17 (generic kernel) on a separate partition than Mint...

I will try the install E17 over the Mint kernel and see what I get... If not I will compile berry and see what I get wih the generic kernel...

I will post back with my results...

Kris

[LunkHead]

Originally Posted by rivviepop

I vaguely remember messing with E.... E14? a very, very (very) long time ago. That's about as close as I come to knowing much about it.

Never used E14... Tried E15 and E16 and am now sporting E17...

Amazingly enough E17 is STILL considered an alpha development...

Was that way on E15....

BUT..... Even though it is considered an alpha it's amazingly very, very stable... I have had a few burps, errors, and FUBR's but it's really pretty solid for still being in alpha state....

I will play with the kernel on my days off (Fri, sat, sun) and let ya know how it worked out....

I am thinking I will try generic kernel 1st with barry and if that no work or I get tired of compiling, then I will try the Mint kernel with E17 plastered over the top....

Kris