8.44 problems in creating debs for debian unstable

**deepsmoke** · 01-12-2008, 06:41 AM

Originally Posted by Kano

You xorg.conf is a bit too short. You have got no entry like:

Section "ServerLayout"
...
Screen 0 "Screen0" 0 0
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultColorDepth 24
SubSection "Display"
Depth 24
Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

You could try Kanotix Thorhammer RC7 and boot with fglrx option then copy /etc/X11/xorg.conf to your hd. Btw. your old config is /etc/X11/xorg.conf.1st (which is always used for input for my script if there).

This xorg.conf is the default I've found once the installation was complete and correctly working. I also thought it was a little too short and searching for answers I realized that X 7.3 wants to minimize the usage of xorg.conf. I was used to launch sudo dpkg-reconfigure xserver-xorg to set driver,monitor, depth and others... But in X 7.3 the choose affects the keyboard only. Now I'll try to complete the xorg.conf and see the result. Thanks for the help.

BTW How comes that Ubuntu packaging achieve the goal while Debian fails, on a Debian unstable?!

**Kano** · 01-12-2008, 06:56 AM

That has nothing to do if you use Debian or Ubuntu packages, you just have several drawbacks when you create Debian ones: These will be updated as soon as Debian has the driver itself packaged and often the Debian create scripts have been broken (I did not like to patch the Debian target for each release). Basically only the package names are different.

Btw. I just tested the new sid reconfigure tool, the file is really extra short... When I have a bit more time i will add a workaround, right now edit manually or use

aticonfig --initial

this even worked with an empty xorg.conf (just touch xorg.conf) when you use -f option. It has some problems to parse the standard Debian file.

**deepsmoke** · 01-12-2008, 08:27 AM

This is the actual state of the system:

Thanks to Kano I was able to complete the xorg.conf so that looked more "verbose" as it was before X 7.3:

Code:

Section "InputDevice"
	Identifier	"Generic Keyboard"
	Driver		"kbd"
	Option		"XkbRules"	"xorg"
	Option		"XkbModel"	"pc105"
	Option		"XkbLayout"	"it"
EndSection

Section "InputDevice"
	Identifier	"Configured Mouse"
	Driver		"mouse"
EndSection

Section "Device"
	Identifier	"Configured Video Device"
        Driver          "radeon"
EndSection

Section "Monitor"
	Identifier	"Configured Monitor"
EndSection

Section "Screen"
	Identifier	"Default Screen"
	Monitor		"Configured Monitor"
EndSection
Section "ServerLayout"
	Identifier	"Default Layout"
	Screen	0	"Default Screen"	0	0
EndSection

Section "Screen"
	Identifier	"Default Screen"
	Device		"Configured Video Device"
	Monitor		"Configured Monitor"
	DefaultColorDepth	24
	SubSection "Display"
		Depth	24
		Modes	"1280x1024"
	EndSubSection
EndSection

This xorg.conf doesn't obviously invoke fglrx as driver and returns the same behaviour of the default one but shows more infos. I have executed Kano's script and noticed something related to the module (last time screens were too fast to let me understand the whole thing). The module experiences problems while being built and I cannot install it with sudo m-a install fglrx-kernel-src. It suggests to take a look at:

/var/cache/modass/fglrx-kernel-src.buildlog.2.6.23-1-686.1200146510

Code:

dh_testroot
rm -f configure-stamp
rm -f fglrx.ko fglrx.mod.c *.o libfglrx_ip.a
rm -f .version .*.o.flags .*.o.d .*.o.cmd .*.ko.cmd
rm -rf .tmp_versions
rm -rf patch
dh_clean
rm /usr/src/modules/fglrx/debian/control
rm /usr/src/modules/fglrx/debian/dirs
if [ -f /usr/src/modules/fglrx/debian/control.template ]; then \
		cat /usr/src/modules/fglrx/debian/control.template > /usr/src/modules/fglrx/debian/control; \
	fi
if [ -f /usr/src/modules/fglrx/debian/postinst ]; then \
		mv /usr/src/modules/fglrx/debian/postinst /usr/src/modules/fglrx/debian/fglrx-kernel-2.6.23-1-686.postinst; \
	fi
dh_testdir
touch configure-stamp
dh_testdir
/usr/bin/make -C /lib/modules/2.6.23-1-686/build SUBDIRS=/usr/src/modules/fglrx modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.23-1-686'
  CC [M]  /usr/src/modules/fglrx/firegl_public.o
/usr/src/modules/fglrx/firegl_public.c: In function ‘__ke_check_pci’:
/usr/src/modules/fglrx/firegl_public.c:1953: warning: ‘pci_find_slot’ is deprecated (declared at include/linux/pci.h:481)
/usr/src/modules/fglrx/firegl_public.c: In function ‘__ke_pci_find_slot’:
/usr/src/modules/fglrx/firegl_public.c:2842: warning: ‘pci_find_slot’ is deprecated (declared at include/linux/pci.h:481)
  LD [M]  /usr/src/modules/fglrx/fglrx.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /usr/src/modules/fglrx/fglrx.mod.o
  LD [M]  /usr/src/modules/fglrx/fglrx.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.23-1-686'
dh_testdir
dh_testroot
dh_clean -k
rm -f /usr/src/modules/fglrx/debian/control /usr/src/modules/fglrx/debian/dirs
sed -e 's/#KVERS#/2.6.23-1-686/g' \
	    -e 's/#VERSION#/8.443.1-1/g' debian/control.template > /usr/src/modules/fglrx/debian/control
sed -e 's/#KVERS#/2.6.23-1-686/g' debian/dirs.template > /usr/src/modules/fglrx/debian/dirs
dh_installdirs
dh_install fglrx.ko lib/modules/2.6.23-1-686/misc
dh_testdir
dh_testroot
dh_installdocs
dh_installmodules
dh_link
dh_strip
dh_compress
dh_fixperms
dh_installdeb
dh_gencontrol -- -v8.443.1-1+2.6.23-2 -VXSERVER=xorg
dh_md5sums
dh_builddeb --destdir=/usr/src
dpkg-deb: costruisco il pacchetto `fglrx-kernel-2.6.23-1-686' in `/usr/src/fglrx-kernel-2.6.23-1-686_8.443.1-1+2.6.23-2_i386.deb'.
dh_testroot
rm -f configure-stamp
rm -f fglrx.ko fglrx.mod.c *.o libfglrx_ip.a
rm -f .version .*.o.flags .*.o.d .*.o.cmd .*.ko.cmd
rm -rf .tmp_versions
rm -rf patch
dh_clean
rm /usr/src/modules/fglrx/debian/control
rm /usr/src/modules/fglrx/debian/dirs
Build time: 8 seconds

I didn't catch what's wrong in the building of the module. Any hint?

Thanks I owe you a lot

**Kano** · 01-12-2008, 08:35 AM

The module was build. Thats not the problem. But why do you use now the old debian packages?

**deepsmoke** · 01-12-2008, 08:39 AM

Originally Posted by Kano

The module was build. Thats not the problem. But why do you use now the old debian packages?

Excuse me but I didn't understand the last suggestion. What do you mean by saying "do you use now the old Debian packages?". Am I using something old or do I have to use something older?

Thanks in advance, I'm not very good with this stuff!

Besides sudo m-a install fglrx-kernel-src returns saying the module wasn't built correctly but I also had the impression the module was built.

**Kano** · 01-12-2008, 02:29 PM

You m-a command is wrong. When you use my script the module is build too. Your command would try to install the old fglrx source which is from debian then builds it fine but the last step goes wrong as it could not be installed because there is the other module package already installed. Please revert your change with fglrx in /etc/modules, thats wrong. If you want to switch from Ubuntu packages to Debian packages you need to do first

apt-get remove --purge $(dpkg -l|awk '/fglrx/{print $2}')

A similar command is in my script.

**deepsmoke** · 01-12-2008, 03:04 PM

Originally Posted by Kano

You m-a command is wrong. When you use my script the module is build too. Your command would try to install the old fglrx source which is from debian then builds it fine but the last step goes wrong as it could not be installed because there is the other module package already installed. Please revert your change with fglrx in /etc/modules, thats wrong. If you want to switch from Ubuntu packages to Debian packages you need to do first

apt-get remove --purge $(dpkg -l|awk '/fglrx/{print $2}')

A similar command is in my script.

Maybe I've got it this time. Anyway, that bad command was suggested by module-assistant after it worked on the tarball and the rest. I didn't notice this dual existence of the module, sorry, I apologize.

When an installation doesn't seems to be correct, I always purge the module by sudo m-a purge --force [module], check /etc/modules to be sure it will not be loaded, then remove the packages purging them and finally copy the old xorg.conf. I think that nothing should survive and locate fgrlx after updatedb seems to agree.

Thanks as always, now I'll try out again.
I really appreciate your help and once the system will be ok, you can ask whatever you like (as developer maybe you need some sort of collaboration sometimes). I'm not a guru but I swear I'll follow your instructions, you helped me out a lot and somehow I want to return the help.

**Kano** · 01-12-2008, 03:07 PM

Btw booting Thorhammer with fglrx option would be much faster

**deepsmoke** · 01-12-2008, 04:06 PM

Originally Posted by Kano

Btw booting Thorhammer with fglrx option would be much faster

Faster probably...But now I've received the best payment of every configuration...IT WORKS

(Really, Thank you a lot! Without your script I would have been lost in the swamp, or in a swap

.

This specific problem was solved thanks to the suggestions of Kano and here I will briefly expose the matter:

solved installation proprietary drivers ati 8.443-1 also known as 7.12 on debian sid unstable kernel 2.6.23-1 Xorg 7.3

1) X 7.3 doesn't like xorg.conf that much and the file is very short. However the generic ATI user has now strong opportunities to have his video card auto detected. If the video card is quite old, like my 9550 r300, the MESA drivers enable a little OpenGL Rendering but poor acceleration. This is the free driver radeon. For those who own r500 and later, there's a new open driver from X called radeonhd. Cannot say anything about configuration and stats of radeonhd.

2) It would be nice to install the proprietary drivers. Once downloaded the 8.443-1 installer from ATI's site, trying to create the *.deb packages with the flag of the installer through command line, returned errors.

3) Put the installer in /usr/bin and downloaded the script made by Kano. Once executed, it correctly creates the module fglrx. Edit /etc/modules and add the voice fglrx so that the module is loaded after rebooting.

4) To get all the stuff working correctly, xorg.conf must be edited. It should have changed after the launching of Kano's script. Following are the two stages of xorg.conf:

Before Kano's script execution:

Code:

Section "InputDevice"
        Identifier      "Generic Keyboard"
        Driver          "kbd"
        Option          "XkbRules"      "xorg"
        Option          "XkbModel"      "pc105"
        Option          "XkbLayout"     "it"
EndSection

Section "InputDevice"
	Identifier	"Configured Mouse"
	Driver		"mouse"
EndSection

Section "Device"
	Identifier	"Configured Video Device"
	Driver		"radeon" #Added by me, else the script won't work
EndSection

Section "Monitor"
	Identifier	"Configured Monitor"
EndSection

Section "Screen"
	Identifier	"Default Screen"
	Monitor		"Configured Monitor"
EndSection
Section "DRI"
	Mode 0666
EndSection

After Kano's script:

Code:

Section "InputDevice"
	Identifier	"Generic Keyboard"
	Driver		"kbd"
	Option		"XkbRules"	"xorg"
	Option		"XkbModel"	"pc105"
	Option		"XkbLayout"	"it"
EndSection

Section "InputDevice"
	Identifier	"Configured Mouse"
	Driver		"mouse"
EndSection

Section "Device"
	Identifier	"Configured Video Device"
	Driver      "fglrx"
	Option      "UseInternalAGPGART" "no"
	Option      "VideoOverlay" "on"
	Option      "OpenGLOverlay" "off"
	Option      "MonitorLayout" "AUTO, AUTO"
EndSection

Section "Monitor"
	Identifier	"Configured Monitor"
EndSection

Section "Screen"
	Identifier	"Default Screen"
	Device		"Configured Video Device" #Added
	Monitor		"Configured Monitor"
	DefaultColorDepth	24 #Added
	SubSection "Display"#Added
		Depth 24#Added
		Modes "1280x1024"#Added
	EndSubSection#Added
EndSection
Section "ServerLayout" #Added
	Identifier	"Default Layout"#Added
	Screen	0	"Default Screen"	0	0 #Added
EndSection
Section "DRI"
	Mode 0666
EndSection

Section "Extensions"
	Option	"Composite"	"1"
#	Option	"RENDER"	"1"
EndSection

Be sure to have entered all the lines or X will probably complaining about Screens with no usable configuration due to the Depth 8 unsupported, giving a PreInitDial failure or something like that. This worked for me. I had to add those lines not because Kano's script is bad, simply it's not used to work on xorg.confs so poor like the one I've found as default in X 7.3.

Hope this post will be useful to someone and still want to thank Kano.

**Kano** · 01-12-2008, 04:16 PM

Nobody needs to edit /etc/modules to load fglrx, thats absolutely wrong. The module is outloaded when you start the X server.

Thread: 8.44 problems in creating debs for debian unstable

Thread Tools

Search Thread

Display

Posting Permissions