Puppy & Gentoo
@xant:
The intel-problem is already solved! Try to update the system from the command line. Look at http://simplux.org for instructions and use wget as a download tool.
The ati-problem is new. Maybe you can specify more details about the exact model of your graphics card - try to run ddcprobe from the command line.
The intel-problem is already solved! Try to update the system from the command line. Look at http://simplux.org for instructions and use wget as a download tool.
The ati-problem is new. Maybe you can specify more details about the exact model of your graphics card - try to run ddcprobe from the command line.
[quote="Leachim"]@xant
Hello, thanks for the quick reply.
The ati card is Mobility Radeon M7 LW (7500)
It's working perfectly with driver MESA DRI Radeon 20061018 AGP in SuSE.
xorg log says:
ATI Proprietary driver...
Version: 8.40.4
Release: UNSUPPORTED-8.402
Build Date: Jul 31 2007
(EE) No devices detected
fatal server error:
No screens found
ddcprobe says only more with the memory which is 32MB, and something about edid:edidfail.
Hello, thanks for the quick reply.
The ati card is Mobility Radeon M7 LW (7500)
It's working perfectly with driver MESA DRI Radeon 20061018 AGP in SuSE.
xorg log says:
ATI Proprietary driver...
Version: 8.40.4
Release: UNSUPPORTED-8.402
Build Date: Jul 31 2007
(EE) No devices detected
fatal server error:
No screens found
ddcprobe says only more with the memory which is 32MB, and something about edid:edidfail.
The proprietary ATI-driver supports all adapters starting from
* Radeon 8500
* Mobility Radeon 9600
Unfortunately this are only "marketing names"! I would need to know the real chipset-names of these (or other adapters). The chipset name should be reported as "product: ..." in the output of ddcprobe.
Here is an example line from the output of ddcprobe from my PC (ATI Radeon 1650):
The minimum requirement for the current nVidia-drivers is GeForce 5 FX. Here, too, I don't know the internal chipset names reported by ddcprobe - help needed!
* Radeon 8500
* Mobility Radeon 9600
Unfortunately this are only "marketing names"! I would need to know the real chipset-names of these (or other adapters). The chipset name should be reported as "product: ..." in the output of ddcprobe.
Here is an example line from the output of ddcprobe from my PC (ATI Radeon 1650):
Code: Select all
product: RV530 01.00
[quote="Leachim"]The proprietary ATI-driver supports all adapters starting from * Radeon 8500
Ok, then what about older ones? Can you please use mesa for them?
I'll check if I get home, but I do remember see only the Radeon 7500 as product...
Good news: after update the xwizard is working for intel, at least for Lattitude D410 I could try now.
Thanks for the hint.
Btw it's a shame, I did not try vmware but that is working also.
Ok, then what about older ones? Can you please use mesa for them?
I'll check if I get home, but I do remember see only the Radeon 7500 as product...
Good news: after update the xwizard is working for intel, at least for Lattitude D410 I could try now.

Btw it's a shame, I did not try vmware but that is working also.

The 7500 does not use mesa for a driver, it uses "radeon". Mesa is some type of interface for OpenGL, I think. "radeon is included, it's just not loaded for the 7500 for some reason. I got my Radeon Mobility 7500 working by copying the xorg.conf from Puppy. I did not check if 3D was working, but I imagine I would have to copy xorg.conf from a copy of Puppy where it was working. I may copy it from my wNOP installation and see if it works.
Leachim, on my machine ddcprobe reports:
and then a bunch of available screen resolutions.
Leachim, on my machine ddcprobe reports:
Code: Select all
vbe: VESA 2.0 detected.
oem: ATI MOBILITY RADEON 7500
memory: 32704kb
Be brave that God may help thee, speak the truth even if it leads to death, and safeguard the helpless. - A knight's oath
Funny how the first idea one has is often close to correct, if not correct. It seems this is especially true if we choose not to try it.xant wrote:Sir, thank you.Funny it was one of my first ideas, but I gave up the idea I don't know why.
That's what alpha versions are for. It took Tombh quite some time to get the video wizard on wNOP to set up 3D correctly on most systems.xant wrote:So if it can work, then the xwizard script needs to be finetuned I believe.
Actually, Leachim, you might want to look at his work if you haven't already.
Be brave that God may help thee, speak the truth even if it leads to death, and safeguard the helpless. - A knight's oath
I actually use wNop as my "rescue system", in case my Simplux doesn't start up again after some heavy changes ...
I will take a look at wNop's Video Wizard. To improve Simplux' wizard I need more infos about the video card signatures reported by ddcprobe.
Unfortunately graphic adapters by different vendors do not only report different signatures they also use different fields to report them!
wNop works fine on nVidia-adapters but I have not seen 3D-acceleration on my two ATI-based PCs yet. This weekend I'm integrating (or starting to do so) a GTK-interface into Simplicity (the scripting language used within Simplux). This will allow for interactive wizards!
I will take a look at wNop's Video Wizard. To improve Simplux' wizard I need more infos about the video card signatures reported by ddcprobe.
Unfortunately graphic adapters by different vendors do not only report different signatures they also use different fields to report them!
wNop works fine on nVidia-adapters but I have not seen 3D-acceleration on my two ATI-based PCs yet. This weekend I'm integrating (or starting to do so) a GTK-interface into Simplicity (the scripting language used within Simplux). This will allow for interactive wizards!
Well, wNOP gets 3D functioning with both my Radeon 7500 and the 9550 in my desktop. Those are both older cards (I think the 9550 is one of the newest cards to use the old "radeon" driver), but that's still something. I know they were working on getting some newer ATI cards working, but I stopped paying attention to the thread, so I don't know if they ever got them working.
As for the card signature, I gave you the full output of ddcprobe for my 7500 (minus the available screen resolutions). I will try to get the info for the 9550 when I get back to the dorm. I went home for the weekend, but I'll be going back tomorrow.
As for the card signature, I gave you the full output of ddcprobe for my 7500 (minus the available screen resolutions). I will try to get the info for the 9550 when I get back to the dorm. I went home for the weekend, but I'll be going back tomorrow.
Be brave that God may help thee, speak the truth even if it leads to death, and safeguard the helpless. - A knight's oath
@Leachim
The version of wNOP for ATI is as follows
http://puppylinux.ca/puppyfiles/wNOP/wNOP-v0.2.iso
The version here http://puppylinux.ca/puppyfiles/wNOP/wNOP.iso is for nVidea cards.
For the new 5th generation ATI cards (Radeon Mobility X1600) I had to install the full ATI driver package from ATI's site and use tweaks to wobble.
My ATI Radeon All-In-Wonder 9800 Pro works perfectly with v0.2.
Thomas has a few new tweaks and the newer ATI cards should soon work out of the box so to speak.
Eric
The version of wNOP for ATI is as follows
http://puppylinux.ca/puppyfiles/wNOP/wNOP-v0.2.iso
The version here http://puppylinux.ca/puppyfiles/wNOP/wNOP.iso is for nVidea cards.
For the new 5th generation ATI cards (Radeon Mobility X1600) I had to install the full ATI driver package from ATI's site and use tweaks to wobble.
My ATI Radeon All-In-Wonder 9800 Pro works perfectly with v0.2.
Thomas has a few new tweaks and the newer ATI cards should soon work out of the box so to speak.
Eric
[color=darkred][i]Be not afraid to grow slowly, only be afraid of standing still.[/i]
Chinese Proverb[/color]
Chinese Proverb[/color]
Dear All,
Thanks for support and ideas.
Finally I got the time to check my D630 and it is _not_ working. Actually I'm not surprised, as it is not working with wNOP1-2 either, from Puppy-s only the Dingo Alpha versions are able to properly detect the card, and I could use with wNOP only by downloading and compiling the latest drivers.
http://www.intellinuxgraphics.org/documentation.html
ddcprobe says:
vbe: VESA 3.0 detected
oem: Intel(r)GM965/PM965/GL960 Graphic Chip Accelerated VGA BIOS
Vendor: Intel Corporation
product: Intel(r)GM965/PM965/GL960 Graphic Controller Hardware Version 0.0
memory:7616kb
Any news about an Alpha 2?
Thanks:
xant
Thanks for support and ideas.
Finally I got the time to check my D630 and it is _not_ working. Actually I'm not surprised, as it is not working with wNOP1-2 either, from Puppy-s only the Dingo Alpha versions are able to properly detect the card, and I could use with wNOP only by downloading and compiling the latest drivers.
http://www.intellinuxgraphics.org/documentation.html
ddcprobe says:
vbe: VESA 3.0 detected
oem: Intel(r)GM965/PM965/GL960 Graphic Chip Accelerated VGA BIOS
Vendor: Intel Corporation
product: Intel(r)GM965/PM965/GL960 Graphic Controller Hardware Version 0.0
memory:7616kb
Any news about an Alpha 2?
Thanks:
xant
Is it not working at all - or is there just no 3D-acceleration? (I have not added automatic 3D-acceleration for Intel yet, but it works if manually configured.)xant wrote:Dear All,
Finally I got the time to check my D630 and it is _not_ working. Actually I'm not surprised, as it is not working with wNOP1-2 either, from Puppy-s only the Dingo Alpha versions are able to properly detect the card, and I could use with wNOP only by downloading and compiling the latest drivers.
At the end of next week Easter holidays will begin. I plan an Alpha 2 for the Tuesday following Easter Sunday.xant wrote:Any news about an Alpha 2?
thx :-)
@Leachim
1. Of course not at all. I got the same error message as usually. (xorg refuses to start). I have tried to use (working in wNOP) xorg.conf file attached, but maybe due to the fact that I have newer driver the screen just turns to blank and I can't even switch to new tty to fix.
2. Thanks for the info. I'm looking forward to see it.
3. The attachment also contains a log I got when I tried to use xorg.conf created by xwizard.
Best Regards:
xant
1. Of course not at all. I got the same error message as usually. (xorg refuses to start). I have tried to use (working in wNOP) xorg.conf file attached, but maybe due to the fact that I have newer driver the screen just turns to blank and I can't even switch to new tty to fix.
2. Thanks for the info. I'm looking forward to see it.

3. The attachment also contains a log I got when I tried to use xorg.conf created by xwizard.
Best Regards:
xant
- Attachments
-
- SIMPLUX.xorg.ZIP
- xorg.conf file and error log
- (8.07 KiB) Downloaded 469 times
well thought I would check in. so from download to me now posting on here with now with simplux, this is what I had to do.
Could not find my cdrom after loading the initrd, so I manually copied the files ot usb and followed your notes on the bootloader.
had to create my own save files, no sure why but when I let the boot script make the save file it would not mount properly. and system would fail.
I have the bcm4138
so I recompiled the kernel, installed the module, cut and installed the firmware. I also emerged wireless-tools and and emerged hotplug.
and presto!
how would I make a new base.sfs to include my configured system so if I wipe out my save.2fs I can always start fresh and ready to go.

Could not find my cdrom after loading the initrd, so I manually copied the files ot usb and followed your notes on the bootloader.
had to create my own save files, no sure why but when I let the boot script make the save file it would not mount properly. and system would fail.
I have the bcm4138

and presto!
how would I make a new base.sfs to include my configured system so if I wipe out my save.2fs I can always start fresh and ready to go.

There is a script called remaster_simplux which is currently far from beeing perfect. You call it someway likemac84 wrote:how would I make a new base.sfs to include my configured system so if I wipe out my save.2fs I can always start fresh and ready to go.
Code: Select all
remaster_simplux sda1
Before calling the remaster script you have to mount /dev/sda1 onto /mnt/sda1 and create an empty folder named remaster_simplux on this drive.
After running the script there are two folders:
/mnt/sda1/remaster_simplux/base
/mnt/sda1/remaster_simplux/root
Now you can create a new base file using
Code: Select all
cd /mnt/sda1/remaster_simplux
mksquashfs base base.sfs
/mnt/sda1/remaster_simplux/root into the new save-file.
I wrote remaster_simplux for my own use to create Simplux-releases stripped of my personal data. So use it at your own risk!
I have compiz-fusion working on my ATI-Radeon 1650! 
wNop2 worked on my Radeon 800 but not on the 1650. I did the complete configuration from scratch with the help of the incredible Gentoo How-To- and Trouble-Shooting-guides!
For Alpha 2 I will try to update the xwizard in the following ways:
* automatic fallback to vesa-rendering if X fails to start
* automatic compiz-fusion configuration for ATI, nVidia and Intel platforms

wNop2 worked on my Radeon 800 but not on the 1650. I did the complete configuration from scratch with the help of the incredible Gentoo How-To- and Trouble-Shooting-guides!
For Alpha 2 I will try to update the xwizard in the following ways:
* automatic fallback to vesa-rendering if X fails to start
* automatic compiz-fusion configuration for ATI, nVidia and Intel platforms
The compiz-fusion installation forced installation of complete new ATI-drivers. A nice side-effekt: the new drivers allow for 50% higher frame rates in openGL-applications!
Yesterday I added support for ext3- and reiserfs-save-files to the initial ramdisk. I also built a new kernel to support reiserfs and PC-cards (PCMCIA) and some other tweaks. Unfortunately the new kernel forced me to rebuild all kernel modules including the proprietary graphics drivers. So updating is not very easy and I didn't offer the update for download yet.
Yesterday I added support for ext3- and reiserfs-save-files to the initial ramdisk. I also built a new kernel to support reiserfs and PC-cards (PCMCIA) and some other tweaks. Unfortunately the new kernel forced me to rebuild all kernel modules including the proprietary graphics drivers. So updating is not very easy and I didn't offer the update for download yet.