IcePuppy-014 for newer and Ice Puppy-015 for older computers

[wuwei]

double post in error.

The forum's reaction time is looooong.

[wuwei]

Me too.

Fresh frugal install of 012, compiled nvidia driver as per previous instructions and all went very well.

Just a question:

In ICE the installed version of vlc is 1.0.6.
In Lucid's quickpet one can find version 1.1.7.
Is there a known problem with 117, that I am unaware of?

Very good job pemasu. Thank you.

[gcmartin]

But report-video-glx gives me a black screen. When going to the X prompt (ctrl-alt-backsp) and typing xwin gives the desktop.

Will ask @TazOC for comment about this.

Also (didn't report it yet) on 1st run I have 800*600 with the vesa driver and have to go to xorwizard to get the 1024*768 with the nv driver.

Although its not a bug or a show stopper, what @Béèm reports here, I have on all of my ICE starts. That is, Vesa is the selected driver. Shinobar may be able to help on this.

Hope this helps

[pemasu]

Wuwei. Yes, I have tried couple of newer VLC versions and they have lacked some of format supports 1.0.6 had. I am not sure if I have tried 1.1.7 yet. I have in fact waited for newer one which I could test again. I have become a little wary of updating VLC after my 2 failed attempts. The format support with this 1.0.6 is fine, I just stripped it down from Lucid repo offering. There were dev files included which are not needed when using VLC.

About vesa as default driver. I have got always intel, so didnt know there is problem with right graphics driver selection.

I would like to get more reports of this.

[pemasu]

I have tested new spup by 01micko and compiled some stuff for it. You could call it small vacation from Ice Puppy. Posting from spup now.

[pemasu]

Beem.

Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder

seems to be tv tuner card. I remember adding all tv tuner cards as modules in my kernel.

Why it picks that up, I dont understand.

[pemasu]

About VLC 1.1.7. There was something which nagged me, I remembered vaguely Playdayz had something to say about it.
I searched the lucid dev thread and found the posts:

666philb wrote:

also, there may be a bug in the new vlc1.1.7 when i go full screen the controls don't work., i can't move the progress bar. It maybe my puppy being bad as i've installed and uninstalled lots of things recently. Can someone check this on their luci,.

Someone:
I can confirm.......went fullscreen with VLC and none of the controls worked here either.Luci 254 and JWM.

Someone:

there are a few other issues with the vlc 1.1.7 , it's slow reacting at times, also if i click on one of the top menus, like 'media' in older vlc's if i moved the cursor along to to 'tools', each menu will pop open in turn. In vlc 1.1.7 you have to click each one, to open them.

Playdayz:

Hopefully someone might take it on themselves to build a good vlc 1.1.7 package. The ones I have built are not good.

I know that Billtoo has compiled VLC several times. I need to figure out, how could I pribe him to make an attempt for newer VLC for lucid puppies. I havent so far played with Qt4 libs and I would need some guidance. And VLC is not the easiest compile, far from it.

[Béèm]

Beem.

Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder

seems to be tv tuner card. I remember adding all tv tuner cards as modules in my kernel.

Why it picks that up, I dont understand.

Correct, it is a tv tuner card.

[gcmartin]

I feel awkward posting multimedia tool use here, but, this may be of use somehow.

I am NOT a multimedia expert by any means. But, as a user, I have not found any Linux tool, yet, that meats my needs like Xine does. It has ONE feature which I find extremely user friendly: "A detached on screen remote control". I find this interesting as I expect that somewhere in our/their future, we should expect to be using HDMI monitor connected to our video cards where Xine is providing some content that a "real" remote control works with it.

I have looked at VLC and even though you can get some of those features via its menu system, it does not present me with the kinds of user controls that a "remote" does. So I find the on-screen remote control allowing me to speed-up/slow-down/pause/eject/skip/etc to be more in line as how I expect to control media. And, until we ever get to "gestures usage", the remote is still a good means for control of media enjoyment.

Feel free to move this somewhere appropriate
P.S. Since this subject has surfaced, is any familiar with any remotes+TV cards that Xine works with?
AND are there other Multimedia tools with on-screen remotes?

[Billtoo]

About VLC 1.1.7. There was something which nagged me, I

I know that Billtoo has compiled VLC several times. I need to figure out, how could I pribe him to make an attempt for newer VLC for lucid puppies. I havent so far played with Qt4 libs and I would need some guidance. And VLC is not the easiest compile, far from it.

Hi pemasu,

I managed to compile 117 in fatdog 64 and spup but have had no success in lupu.
Sorry that I can't help you out.

[jim3630]

I have tested new spup by 01micko and compiled some stuff for it. You could call it small vacation from Ice Puppy. Posting from spup now.

pemasu hey enjoy your time off. I tried spup doesn't come with a wl driver and the wl pets for Ice Puppy don't work. darn.

[pemasu]

Jim3630. Do you mean wl.ko module does not load from the broadcom hybrid pet. If you try load the module in console modprobe wl, or first rmmod wl and then modrobe wl, what you get. It is possible that the modules compiled in lupe22 does not work. If you get error due to unknown symbols, I need to compile the wl module again.
Or do you mean wl module loads ok, but does not work after installing the pet.
And has the broadcom hybrid pet worked before.
Many questions.

[Béèm]

Beem.

Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder

seems to be tv tuner card. I remember adding all tv tuner cards as modules in my kernel.

Why it picks that up, I dont understand.

Correct, it is a tv tuner card.

Code: Select all

sh-4.1# lspci
00:00.0 Host bridge: VIA Technologies, Inc. P4M890 Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. P4M890 Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. P4M890 Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. P4M890 Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. P4M890 Host Bridge
00:00.5 PIC: VIA Technologies, Inc. P4M890 I/O APIC Interrupt Controller
00:00.6 Host bridge: VIA Technologies, Inc. P4M890 Security Device
00:00.7 Host bridge: VIA Technologies, Inc. P4M890 Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge
00:02.0 PCI bridge: VIA Technologies, Inc. P4M890 PCI to PCI Bridge Controller
00:03.0 PCI bridge: VIA Technologies, Inc. P4M890 PCI to PCI Bridge Controller
00:0f.0 IDE interface: VIA Technologies, Inc. VT8251 Serial ATA Controller (rev 20)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 91)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 91)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 91)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 91)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 90)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8251 PCI to ISA Bridge
00:11.7 Host bridge: VIA Technologies, Inc. VT8251 Ultra VLINK Controller
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c)
00:13.0 PCI bridge: VIA Technologies, Inc. VT8251 Host Bridge
00:13.1 PCI bridge: VIA Technologies, Inc. VT8251 PCI to PCI Bridge
02:00.0 VGA compatible controller: nVidia Corporation G73 [GeForce 7650 GS] (rev a1)

[jim3630]

Jim3630. Do you mean wl.ko module does not load from the broadcom hybrid pet. If you try load the module in console modprobe wl, or first rmmod wl and then modrobe wl, what you get. It is possible that the modules compiled in lupe22 does not work. If you get error due to unknown symbols, I need to compile the wl module again.
Or do you mean wl module loads ok, but does not work after installing the pet.
And has the broadcom hybrid pet worked before.
Many questions.

Yes the broadcom pet lupe22 works in IP 12, 11, and maybe 10. I tried lupe22,18,15 broadcom pets in spup and none worked.

The wl.ko module doesn't load from the broadcom hybird. at the console rmmod wl =wl doesnot exist in /proc/modules and modprobe wl =module wl not found.

[James C]

Jim3630. Do you mean wl.ko module does not load from the broadcom hybrid pet. If you try load the module in console modprobe wl, or first rmmod wl and then modrobe wl, what you get. It is possible that the modules compiled in lupe22 does not work. If you get error due to unknown symbols, I need to compile the wl module again.
Or do you mean wl module loads ok, but does not work after installing the pet.
And has the broadcom hybrid pet worked before.
Many questions.

Yes the broadcom pet lupe22 works in IP 12, 11, and maybe 10. I tried lupe22,18,15 broadcom pets in spup and none worked.

The wl.ko module doesn't load from the broadcom hybird. at the console rmmod wl =wl doesnot exist in /proc/modules and modprobe wl =module wl not found.

Those Ice Puppy modules won't work in Spup because of the different kernel in Spup ........drivers are kernel specific.
They'll need to be compiled for the specific Spup kernel version. HTH.

[jim3630]

Jim3630. Do you mean wl.ko module does not load from the broadcom hybrid pet. If you try load the module in console modprobe wl, or first rmmod wl and then modrobe wl, what you get. It is possible that the modules compiled in lupe22 does not work. If you get error due to unknown symbols, I need to compile the wl module again.
Or do you mean wl module loads ok, but does not work after installing the pet.
And has the broadcom hybrid pet worked before.
Many questions.

Yes the broadcom pet lupe22 works in IP 12, 11, and maybe 10. I tried lupe22,18,15 broadcom pets in spup and none worked.

The wl.ko module doesn't load from the broadcom hybird. at the console rmmod wl =wl doesnot exist in /proc/modules and modprobe wl =module wl not found.

Those Ice Puppy modules won't work in Spup because of the different kernel in Spup ........drivers are kernel specific.
They'll need to be compiled for the specific Spup kernel version. HTH.

yeah, thought as much. would need source code to start? Is there a DIY tutorial somewhere? thanks jim

[smokey01]

jim3630 I'm sure 01micko would compile the drivers if you asked him nicely in the spup thread.

[jim3630]

jim3630 I'm sure 01micko would compile the drivers if you asked him nicely in the spup thread.

thanks for the lead and just did.

[Béèm]

Without nolapic and with
In spite of the errors I tried again without nolapic so as to have the two processors and then again with nolapic
There isn't very much difference when I run glxgears. In fact with the dual processors Htop doesn't indicate much usage of the second processor.
Interesting to know

Code: Select all

Booting without nolapic, thus dual processor
sh-4.1# glxgears
1848 frames in 5.0 seconds
1833 frames in 5.0 seconds
1848 frames in 5.0 seconds
1837 frames in 5.0 seconds
1833 frames in 5.0 seconds
1834 frames in 5.0 seconds
1839 frames in 5.0 seconds
1835 frames in 5.0 seconds
1844 frames in 5.0 seconds
1825 frames in 5.0 seconds
1833 frames in 5.0 seconds
^C
sh-4.1# 
Booting with nolapic, thus single processor.
sh-4.1# glxgears
874 frames in 5.0 seconds
1235 frames in 5.0 seconds
1211 frames in 5.0 seconds
1212 frames in 5.0 seconds
1210 frames in 5.0 seconds
1228 frames in 5.0 seconds
922 frames in 5.0 seconds
1121 frames in 5.0 seconds
1201 frames in 5.0 seconds
1295 frames in 5.0 seconds
1264 frames in 5.0 seconds
1299 frames in 5.0 seconds
1282 frames in 5.0 seconds
1290 frames in 5.0 seconds
1270 frames in 5.0 seconds
1307 frames in 5.0 seconds
1261 frames in 5.0 seconds
1304 frames in 5.0 seconds
1277 frames in 5.0 seconds
1305 frames in 5.0 seconds
1238 frames in 5.0 seconds
1312 frames in 5.0 seconds
1228 frames in 5.0 seconds
^C
sh-4.1# 

[Béèm]

Until now I didn't report it.
The last puppy that worked on this laptop was 003.
I just tried the 011, but got a message of incompatibility between the kernel and the CPU. Something with pae, but I didn't quite understand if the kernel you compiled lacks this pae or if it is the CPU of the R40 that lacks it.

Do you have plans to do a follow-on on the 003, pemasu?