spinynorman

If you give up on gcover and kcdlabel, you may like to check out Disc-Cover at http://home.wanadoo.nl/jano/disc-cover.html.

 

This seems to do a lot of the donkey-work; won an award from linux.com in 1999(!); and lets you try it out on-line. 8)

If you use the Google Linux search (www.google.com/linux), ' cd labels' does it, or 'cd covers'.

 

I presume it will work as long as you have Gnome installed as well as KDE.

I've come across this while googling - haven't tried it tho.

 

http://gcover.sourceforge.net/

The BBC reports that the UN is training Afghan civil servants to use Linux!

 

http://news.bbc.co.uk/1/hi/technology/3067871.stm

Thanks cjc. Having looked more closely at the cable, I have discovered that the 'expert' who installed the printer, had connected it to the RJ-45 socket instead of the usb.

 

Printer is now working nicely! :D

The Epson C62 is explicitly supported in Mandrake 9.1, but I can't get it to work. I have installed the latest updates. The printer isn't auto-detected, so I have set it up manually via PrinterDrake. There are 3 drivers to try and none of them gives a test print. The printer does nothing and there is no error message. In CUPS, the status is shown as "processing...".

 

As suggested in another thread, I have tried

echo "hello" > /dev/lp0

which firstly fails with 'permission denied'. As root, it gives 'device or resource busy', although the failed job was deleted, and CUPS shows the printer as idle, accepting jobs.

 

BTW, when trying to changing permissions with UserDrake, I got

cannot lock user lib, file /etc/ptmp or /etc/gtmp exist

Can I just delete these files?

You might want to put a seperate topic under SECURITY in the meantime.

I think you're right. Many thanks to everyone who helped to get my monitor and modem working.

 

 

:unsure: . . . . . :banghead: . . . . . 8)

You must have missed this:

I took down the firewall  to get speedtouch working, as several people suggested... and it worked!   :D  How do I configure the firewall to keep it going?   :?:

You should just try vga=normal

I did this and can now boot into a normal linux session with no problem! :D

 

Why not delete the 'c' config (just comment out) and see if the same thing happens.

Tried this too, and got an error, but commenting out 'b' config worked. Can now <Ctrl><Alt><-> without errors! :D

 

I can now concentrate on the modem/firewall conundrum. From what I've been reading on other forums, Shorewall is basically a GUI for iptables. I used iptables on RH7.3 with my dialup modem, copying the instructions from a magazine. The original is at http://www.netfilter.org/unreliable-guides...linuxdoc-5.html:

 

• ## Insert connection-tracking modules (not needed if built into kernel).

# insmod ip_conntrack

# insmod ip_conntrack_ftp

 

## Create chain which blocks new connections, except if coming from inside.

# iptables -N block

# iptables -A block -m state --state ESTABLISHED,RELATED -j ACCEPT

# iptables -A block -m state --state NEW -i ! ppp0 -j ACCEPT

# iptables -A block -j DROP

 

## Jump to that chain from INPUT and FORWARD chains.

# iptables -A INPUT -j block

# iptables -A FORWARD -j block

Could this be modified for ADSL? I've found a sophisticated version of this at http://beyond.linuxfromscratch.co.uk/view/...s/firewall.html. I could just about understand the simple version but I'm not sure about this. Any ideas? :?:

 

• cat > /etc/rc.d/init.d/firewall << "EOF"

#!/bin/sh

 

# Begin $rc_base/init.d/firewall

 

# Insert connection-tracking modules (not needed if built into the kernel).

modprobe ip_tables

modprobe iptable_filter

modprobe ip_conntrack

modprobe ip_conntrack_ftp

modprobe ipt_state

modprobe ipt_LOG

 

# allow local-only connections

iptables -A INPUT -i lo -j ACCEPT

# free output on any interface to any ip for any service (equal to -P ACCEPT)

iptables -A OUTPUT -j ACCEPT

 

# permit answers on already established connections

# and permit new connections related to established ones (eg active-ftp)

iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT

 

# Log everything else: What's Windows' latest exploitable vulnerability?

iptables -A INPUT -j LOG --log-prefix "FIREWALL:INPUT "

 

# set a sane policy: everything not accepted > /dev/null

iptables -P INPUT DROP

iptables -P FORWARD DROP

iptables -P OUTPUT DROP

 

# be verbose on dynamic ip-addresses (not needed in case of static IP)

echo 2 > /proc/sys/net/ipv4/ip_dynaddr

 

# disable ExplicitCongestionNotification - too many routers are still ignorant

echo 0 > /proc/sys/net/ipv4/tcp_ecn

 

# End $rc_base/init.d/firewall

EOF

• Thanks. :)

Here is the lilo.conf. I tried commenting out 'vga=791', but still got the usual 'out of range' message. Any suggestions? :?:

• boot=/dev/hda

map=/boot/map

vga=normal

default="linux"

keytable=/boot/uk.klt

prompt

nowarn

timeout=100

message=/boot/message

menu-scheme=wb:bw:wb:bw

image=/boot/vmlinuz

label="linux"

root=/dev/hda1

initrd=/boot/initrd.img

append="quiet devfs=mount hdc=ide-scsi acpi=off"

vga=791

read-only

image=/boot/vmlinuz

label="linux-nonfb"

root=/dev/hda1

initrd=/boot/initrd.img

append="devfs=mount hdc=ide-scsi acpi=off"

read-only

image=/boot/vmlinuz

label="failsafe"

root=/dev/hda1

initrd=/boot/initrd.img

append="failsafe devfs=nomount hdc=ide-scsi acpi=off"

read-only

other=/dev/fd0

label="floppy"

unsafe

• I took down the firewall to get speedtouch working, as several people suggested... and it worked! :D How do I configure the firewall to keep it going? :?:

 

I see light at the end of the tunnel... :wink:

Between testing the monitor and tearing my hair out, I found time to try some modem commands, seeking some meaningful error messages. 'drakconnect' gave the message

Starting ADSL connection      [FAILED]

modem_run -v -f /usr/share/speedtouch/mgmt.o

pppd call adsl

displayed modem_run help, and not surprisingly the second line did nothing. Any more suggestions, please? :)

I tried some more of your recommendations. Xf86cfg gave me an 'out of range' message on entry, which I cleared using <Ctrl><Alt><->, but this got rid of the control panel as well! Xvidtune wouldn't run giving an 'error: can't open display:' message. :(

 

However, other suggestions were more fruitful. :) I set the boot option in MCC to not load graphical environment. Using the XF86Config-4 listed below, I booted in failsafe mode and used startx, which got me into KDE with no error messages. Using <Ctrl><Alt><-> refreshed the screen again with no error. Using <Ctrl><Alt><-> a second time gave 'out of range Fh 55.7 Fv 69.1 Pixel 73.1'. Using <Ctrl><Alt><-> again got rid of the error. This suggests to me that 2 of the modelines are working. :?:

 

On booting into a standard linux session, I'm not presented with the command line, but with the old 'out of range Fh 35.4 Fv 86.9 Pixel 23.5' message straight after the lilo menu, which persists until I switch off. What is going on? :?: :unsure:

• # File generated by XFdrake.

 

# **********************************************************************

# Refer to the XF86Config man page for details about the format of

# this file.

# **********************************************************************

 

Section "Files"

# Multiple FontPath entries are allowed (they are concatenated together)

# By default, Mandrake 6.0 and later now use a font server independent of

# the X server to render fonts.

FontPath "unix/:-1"

EndSection

 

Section "ServerFlags"

#DontZap # disable <Crtl><Alt><BS> (server abort)

#DontZoom # disable <Crtl><Alt><KP_+>/<KP_-> (resolution switching)

AllowMouseOpenFail # allows the server to start up even if the mouse doesn't work

EndSection

 

Section "Module"

Load "dbe" # Double-Buffering Extension

Load "v4l" # Video for Linux

Load "extmod"

Load "type1"

Load "freetype"

Load "glx" # 3D layer

EndSection

 

Section "InputDevice"

Identifier "Keyboard1"

Driver "Keyboard"

Option "XkbModel" "pc105"

Option "XkbLayout" "gb"

Option "XkbCompat" ""

Option "XkbOptions" ""

EndSection

 

Section "InputDevice"

Identifier "Mouse1"

Driver "mouse"

Option "Protocol" "IMPS/2"

Option "Device" "/dev/psaux"

Option "ZAxisMapping" "4 5"

EndSection

 

Section "Monitor"

Identifier "monitor1"

VendorName "HSL"

ModelName "H530"

# Option "DPMS"

HorizSync 30-61

VertRefresh 56-76

 

ModeLine "1024x768a" 78.75 1024 1040 1136 1312 768 769 772 800 -hsync -vsync

ModeLine "1024x768b" 75 1024 1032 1176 1344 768 771 777 806 -hsync -vsync

 

ModeLine "1024x768c" 65 1024 1032 1176 1344 768 771 777 806 -hsync -vsync

 

# TV fullscreen mode or DVD fullscreen output.

# 768x576 @ 79 Hz, 50 kHz hsync

# ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630

 

# 768x576 @ 100 Hz, 61.6 kHz hsync

# ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616

EndSection

 

Section "Device"

Identifier "card1"

Driver "sis"

VendorName "Silicon Integrated Systems [sIS]"

BoardName "SIS650/651/M650/740 PCI/AGP VGA Display Adapter"

BusID "PCI:1:0:0"

EndSection

 

Section "Screen"

Identifier "screen1"

Device "card1"

Monitor "monitor1"

DefaultColorDepth 16

 

# Subsection "Display"

# Depth 8

# Modes "1024x768" "800x600" "640x480"

# EndSubsection

 

# Subsection "Display"

# Depth 15

# Modes "1024x768" "800x600" "640x480"

# EndSubsection

 

Subsection "Display"

Depth 16

Modes "1024x768a" "1024x768b" "1024x768c"

EndSubsection

 

# Subsection "Display"

# Depth 24

# Modes "1024x768" "800x600" "640x480"

# EndSubsection

EndSection

 

Section "ServerLayout"

Identifier "layout1"

InputDevice "Keyboard1" "CoreKeyboard"

InputDevice "Mouse1" "CorePointer"

Screen "screen1"

EndSection

Does that mean your USB modems working by the way?

Don't be silly! :roll:

 

When I get the monitor fixed this weekend, I can concentrate on the modem. :lol:

Another questrion, did you install the mandrake updates?  Given the problem with your modem I'm guessing not.

Yes, I did. It got rid of the ISDN label on the speedtouch, but I haven't noticed any other changes.

 

I just bought a ADSL ethernet one. it cost me an extra 30 quid over the usb but theres no messing about or driver issues since its directly from the NIC which is already working fine.

Knowing my luck, the built-in NIC will be incompatible! :lol:

 

I probably have the config for the speedtouch on my ISP CD though so I can mail it if you can't find it elsewhere....

That sounds useful. Thanks. :)

Thanks for the detailed instructions. As you say, I'm learning a lot, but it never seems enough! :)

 

Just to clear up a few points.

You said Hs 48hz and Vf 60 so this isn't going to work  

I think you've picked up these figures by mistake. The manual only has max values (H 60 & V 75), so I've been trying to use the ranges specified in the log, viz:

• (II) SIS(0): Supported additional Video Mode:

(II) SIS(0): clock: 78.8 MHz Image Size: 304 x 228 mm

(II) SIS(0): h_active: 1024 h_sync: 1040 h_sync_end 1136 h_blank_end 1312 h_border: 0

(II) SIS(0): v_active: 768 v_sync: 769 v_sync_end 772 v_blanking: 800 v_border: 0

(II) SIS(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 61 kHz, PixClock max 100 MHz

• Also I forgot to post the contents of /boot:

• total 2248

4 boot.0300

0 config@

48 config-2.4.21-0.13mdk

4 grub/

116 initrd-2.4.21-0.13mdk.img

0 initrd.img@

0 kernel.h@

4 kernel.h-2.4.21-0.13mdk

160 map

0 message@

100 message-graphic

4 message-text

0 System.map@

576 System.map-2.4.21-0.13mdk

4 uk.klt

0 vmlinuz@

1228 vmlinuz-2.4.21-0.13mdk

I tried out the modelines I mentioned a couple of posts ago. This produced the usual 'out of range' message in normal linux mode. I will send the files to Gowator, in case there's anything of interest.

 

On the question of SMP, during one of my reinstalls - possibly the latest - I selected 'network (client)' (or something like it) from the packages for installation. I did this in the hope that it might help with my modem problem. Could this be responsible for the SMP? Would it easier to reinstall again? I should point out that the monitor problem existed before I used this option.

 

BTW, while searching for inspiration, I came across a Linux Kernel menu option (Configuration/KDE/System/Linux Kernel), which gave the following error message:

The kernel configuration could not be read due to the following error:

     cannot open /usr/src/linux/arch/config.in for reading

Either your kernel sources contain invalid configuration rules or you have just found a bug in KDE Kernel Configurator.

I'm confused (as ever). :?

According to the XF86config its reporting the fact you are using SMP (symetrical mutli processor)  

When you comile from source and run configure you get to choose which options to compile in.

I haven't done any manual compilations, especially not of the kernel.

 

SMP gives the option for multi processors.  Its a don't use unless you have to option!

Was there an option during installation which caused this to happen? :?:

 

You can add the stock kernel from the cd's

Does this mean I just have to install Linux 2.4.21-0.13mdk_i686, if it isn't in /boot? Will it become the default? :?:

 

Sorry, but you have to spell things out for a newbie! :roll:

You still have the timings for the sony Viao screen but notice this is 1024x480 NOT 1024x768

Yes, I'm sorry. When I saw 1024x... I must have switched off. :? The 2 modelines I thought I had pasted in from 'XF86Config.test.old' were:

• ModeLine "1024x768" 75 1024 1048 1184 1328 768 771 777 806 -hsync -vsync; and

ModeLine "1024x768" 65 1024 1032 1176 1344 768 771 777 806 -hsync -vsync

• Your monitor is specified as

HorizSync 30-61

VertRefresh 56-76

Whereas you say its

HorizSync 48

VertRefresh 60

I think the 48/60 values originated in your previous posting.

 

I'll try again with the values I intended to use. If that fails, I'll try xf86cfg. :)

You can tell which XF86Config its using from the log file in /var/log/XF*  

Have examined the logs after running in normal and linux-failsafe mode, as suggested. The output is basically the same: both use /etc/X11/XF86Config-4 and record the same warning:

 

(WW) VESA(0): config file vrefresh range 40-70Hz not within DDC vrefresh range 56-76Hz

The only difference is that the failsafe session fails to display the 'out of range' message.

 

The logs contain information that doesn't appear in the Hansol manual, including the required frequency ranges rather than just the maximums. While looking through various config files, I came across 'XF86Config.test.old'. I don't know where this came from, but it has a list of standard mode timings. With this and the newly discovered ranges, I shall run some more tests tonight.

 

On the subject of the Speedtouch modem, can anyone suggest commands I can use to connect to the internet outside MCC, and hopefully get some meaningful error messages? :?:

 

Thanks for your help so far.

by FAILSAFE, do you mean the linux-failsafe option which appears in lilo during boot?

 

Yes. Sorry for not making it clear.

Welcome back, Gowator. :D - Just to bring you up to speed:

 

I only have Mandrake on the machine now, so can't check RH.

 

I have updated the system with my update CD. This has eliminated the ISDN reference on the Speedtouch. Still unable to connect - can I test the connection outside MCC to get a proper error message? :?:

 

My latest XF86Config-4 conforms with the Hansol manual (1024 x 768; HF 48.363 VF 60.004 Clock 65.000):

 

• Section "Monitor"

Identifier "monitor1"

VendorName "Generic"

ModelName "Flat Panel 1024x768"

HorizSync 31.5-48.5

VertRefresh 40-70

 

# Sony Vaio C1(X,XS,VE,VN)?

# 1024x480 @ 85.6 Hz, 48 kHz hsync

ModeLine "1024x480" 65.00 1024 1032 1176 1344 480 488 494 563 -hsync -vsync

 

# TV fullscreen mode or DVD fullscreen output.

# 768x576 @ 79 Hz, 50 kHz hsync

ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630

 

# 768x576 @ 100 Hz, 61.6 kHz hsync

ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616

EndSection

 

Section "Device"

Identifier "device1"

Driver "vesa"

Option "DPMS"

EndSection

 

Section "Screen"

Identifier "screen1"

Device "device1"

Monitor "monitor1"

DefaultColorDepth 16

 

Subsection "Display"

Depth 8

Modes "1024x768" "800x600" "640x480"

EndSubsection

 

Subsection "Display"

Depth 15

Modes "1024x768" "800x600" "640x480"

EndSubsection

 

Subsection "Display"

Depth 16

Modes "1024x768" "800x600" "640x480"

EndSubsection

 

Subsection "Display"

Depth 24

Modes "1024x768" "800x600" "640x480"

EndSubsection

EndSection

This works in FAILSAFE mode but in a normal session gives 'out of range Fh 35.4 Fv 86.9 Pixel 23.5'. I will look at the log file this evening, but it's difficult to believe that the XF86Config-4 is being used for the normal session, as the 'out of range' message reports the same figures whatever we put in the file. :?

First the latest on the modem. The dealer demonstrated it on a Windows machine on a non-ISDN line, so it would seem to be a standard Speedtouch model, which is being wrongly identified. Are there commands I can use outside MCC to try and connect and hopefully get some meaningful error message? :?:

 

As far as the monitor is concerned, I removed the modelines and the frequency timings and left just the 16bpp option. This generated the values listed below. The VR range goes to 76 and the max is 75, which could be a problem I suppose; but the old 'out of range' still appeared - Fh 35.4 Fv 86.9 Pixel 23.5. HOWEVER, when I tried failsafe mode and let the time run out on the Linuxconf menu, I got into KDE without error messages. Is this using the XF86Config-4 file? :?:

 

• Section "Monitor"

Identifier "monitor1"

VendorName "Plug'n Play"

ModelName "Flat Panel 1024x768"

HorizSync 30-61

VertRefresh 56-76

 

# Sony Vaio C1(X,XS,VE,VN)?

# 1024x480 @ 85.6 Hz, 48 kHz hsync

ModeLine "1024x480" 65.00 1024 1032 1176 1344 480 488 494 563 -hsync -vsync

 

# TV fullscreen mode or DVD fullscreen output.

# 768x576 @ 79 Hz, 50 kHz hsync

ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630

 

# 768x576 @ 100 Hz, 61.6 kHz hsync

ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616

EndSection

 

Section "Device"

Identifier "device1"

Driver "vesa"

Option "DPMS"

EndSection

 

Section "Screen"

Identifier "screen1"

Device "device1"

Monitor "monitor1"

DefaultColorDepth 16

 

Subsection "Display"

Depth 8

Modes "1024x768" "800x600" "640x480"

EndSubsection

 

Subsection "Display"

Depth 15

Modes "1024x768" "800x600" "640x480"

EndSubsection

 

Subsection "Display"

Depth 16

Modes "1024x768" "800x600" "640x480"

EndSubsection

 

Subsection "Display"

Depth 24

Modes "1024x768" "800x600" "640x480"

EndSubsection

EndSection

I also did a full reinstall to try and use XFree3, as I was given a choice on the original install. However, I found that this only appears with certain cards, and if you can't use the card, it reverts to XFree4.

 

In the time I had available, I made a couple of attempts to run Mandrake Update with my update CD, but it was looking for an internet connection. I've set up /mnt/cdrom2 as a 'security update' source, but perhaps I have to uncheck all the other sources? :?:

I was going to keep Red Hat so I could try dual-booting, but when it didn't appear on the boot list on my first install, I zapped it.

 

Only have the one monitor. I will try some of your suggestions over the weekend. If all else fails, I may try XFree3.

 

This afternoon I'm going to swap my ISDN modem. Wish me luck. 8)

Just to recap the facts according to the Hansol handbook:

• Max Resolution: 1024 X 768 @ 75 Hz

Horizontal Frequency: 60 kHz (max)

Vertical Frequency: 75 Hz (max)

Pixel Range: 0.297 mm x 0.297 mm

In the 'standard signal table', there are settings for VGA, SVGA, XGA and MAC. There are two lots of figures for XGA - the only ones for 1024 x 768. The higher of these is:

• Horizontal Frequency: 60.023

Vertical Frequency: 75.029

Clock Frequency: 78.750

I created and ran a sample XFConfig file as suggested. This produced a different 'out of range' message:

• Fh: 59.9 kHz

Fv: 59.9 Hz

Pixel: 108.9 MHz

The Horizontal & vertical values are within range, so the 'pixel' one must be wrong. Is this the same as the clock frequency? If so, how do I change it? Does the mm pixel range in the manual (above) relate to this?

 

I have been using 16bpp & 1024 x 768. The spec for the ASUS Terminator P4 is at http://www.pctekonline.com/aspenbarsyst.html.

 

Thank you for your patience.

 

Just a further thought: the monitor worked perfectly with RH 7.3 (largely unamended because of slow modem). Would the version of XFree or something else make the difference?