from:"Michael Bonert"

Not booting after motherboard replacement (XPS 15 9500) - (Solution)

2021-08-18 Thread Michael Bonert


Issue: "No bootable devices found" after motherboard replaced
Background: previously functional Debian system where hardware quit  
(so called "No POST").


I spent a few hours on a "No bootable devices found" issue:
The fix was in the Dell BIOS (got to by pressing 'F2'):
-> Boot Configuration
--> Add Boot Option
---> [select the SSD] (the BIOS then reads the "EFI" partition)
> one then needs to select the "grubx64.efi" file + give the "Boot  
Option" a name, e.g. "Debian Linux on SSD"

-> Save changes to BIOS + Exit BIOS

The above presumes: the SSD is intact and has an EFI partition with  
Grub on it.


I was looking at the re-installing GRUB (  
https://wiki.debian.org/GrubEFIReinstall )... that isn't the solution  
here.


The fix is two minutes if one understand what is happening.  Perhaps,
this will save someone else some time.

System: Dell XPS 15 9500
OS: Debian Linux 10.10 (stable) **only**
~~

Other BIOS settings important for Debian Linux on XPS 15:
Boot Configuration
Enable Secure Boot [x] On
--> CHANGE THIS TO 'Off' (from "On")
Storage
SATA Operation -> RAID On
--> CHANGE THIS TO "AHCI" (SATA is configured for AHCI mode)
Pre-boot Behavior
Fastboot [x] Minimal
--> CHANGE THIS TO "Thorough" (from 'Minimal')



Michael

Re: dislocker package broken, fix in 'sid'. How long 'til in backports?

2020-02-02 Thread Michael Bonert


Thank you for the comments!  I emailed the developer.

As the dislocker packages don't seem to have dependencies - that  
aren't part of stable (buster),
I decided to create a so-called "FrankenDebian" (  
https://wiki.debian.org/DontBreakDebian )



Here is hack:

I downloaded the (amd64) debs:
 https://packages.debian.org/sid/amd64/dislocker/download
 https://packages.debian.org/sid/amd64/libdislocker0.7/download

I then in the directory of the '.deb's did this:
# apt install ./dislocker_0.7.1-5_amd64.deb
# apt install ./libdislocker0.7_0.7.1-5_amd64.deb

If done properly - you should see this with 'dpkg --list'
#  dpkg --list |grep dislocker
ii  dislocker  0.7.1-5  
amd64read/write encrypted BitLocker volumes
ii  libdislocker0.70.7.1-5  
amd64read/write encrypted BitLocker volumes  
(shared library)


dislocker now works for me. :-)


If there is an easier more elegant (less hack-ish) way to do the  
above... I am all ears.



Michael

dislocker package broken, fix in 'sid'. How long 'til in backports?

2020-02-01 Thread Michael Bonert


I am running Debian stable (buster).

The dislocker backport doesn't work for files from Windows 10 1903 (as  
noted here:  
https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1710592.html  
)


I noted that the latest version of dislocker in 'sid' (unstable) is  
0.7.1-5 ( https://packages.debian.org/sid/utils/dislocker )


The release notes for 0.7.1-5 (  
https://metadata.ftp-master.debian.org/changelogs//main/d/dislocker/dislocker_0.7.1-5_changelog  
)
say:  "Added new patches to support Support Windows 10 1903 and fix  
build issues.Thanks to haobinnan " - sounds like  
exactly what I'd like to have.


How long will it take for 0.7.1-5 to appear as a backport?

Thanks,
Michael

PS -
I will trying making my own backport (  
https://wiki.debian.org/DontBreakDebian /  
https://wiki.debian.org/SimpleBackportCreation ) but prefer to avoid  
that... if isn't too long a wait.

jessie backports letsencrypt

2016-03-08 Thread Michael Bonert


Has any one managed to installed 'letsencrypt' on jessie?

I note that there are a few bugs... saying it will be available in a week
or so -- a couple of weeks ago.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809018
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805027

(I have the sense that it is stuck in a dependency jungle at the moment.)

Thanks,
Michael

-
What I get when I try installing it:

 apt-get install letsencrypt

The following packages have unmet dependencies:
 letsencrypt : Depends: python-letsencrypt (= 0.4.1-1~bpo8+1) but it  
is not going to be installed

E: Unable to correct problems, you have held broken packages.


 apt-get install python-letsencrypt

The following packages have unmet dependencies:
 python-letsencrypt : Depends: python-acme (>= 0.4.1) but it is not  
going to be installed
  Depends: python-cryptography (>= 0.7) but  
0.6.1-1 is to be installed
  Recommends: letsencrypt but it is not going to  
be installed

E: Unable to correct problems, you have held broken packages.


 apt-get install python-acme

The following packages have unmet dependencies:
 python-acme : Depends: python-openssl (>= 0.15) but 0.14-1 is to be installed
   Depends: python-cryptography (>= 0.8) but 0.6.1-1 is  
to be installed

E: Unable to correct problems, you have held broken packages.

Letsencrypt - Debian?

2015-07-27 Thread Michael Bonert


Is there a time line for releasing a Let's Encrypt ( letsencrypt) package
for Debian?  Will it be backported to Debian stable?

I did note discussion of that here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774387

It is available at github:
https://github.com/letsencrypt/letsencrypt

There is a mailing list archive for letsencrypt development
https://lists.alioth.debian.org/pipermail/letsencrypt-devel/
... but it seems to be inactive.

I would be delighted to go 'https' on the modest website I have helped
to build.  I hope the package comes when 'Let's Encrypt' goes live. :-)

Michael


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: 
https://lists.debian.org/20150727153749.q7670b8lcwgog...@webmail.utoronto.ca

Wireless disabled in Debian after MacOS use (stuck)

2015-07-21 Thread Michael Bonert


I solved the problem!  I was reading the Network Manager how to -- that
is found here: https://wiki.debian.org/NetworkManager

This is what I did:
**

# vi /etc/NetworkManager/NetworkManager.conf
-IT WAS
[ifupdown]
managed=false
-CHANGED TO
[ifupdown]
managed=true
---

# /etc/init.d/network-manager restart

**


I am still baffled about why this happened.  It doesn't make sense to me!

Any how, I hope if someone else encounters wireless problems with the
Broadcom driver ( b43 ) ... my list of things to try
( https://lists.debian.org/debian-user/2015/07/msg00947.html ) is useful.

Michael


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: 
https://lists.debian.org/20150721200416.fw2bl24s0sc8s...@webmail.utoronto.ca

Wireless disabled in Debian after MacOS use (stuck)

2015-07-21 Thread Michael Bonert


I had the wireless (AirPort) working on my MacBook Pro 8.1 with a
dual boot MacOS/Debian setup without any difficulty for a couple of years.
A couple of days ago, I decided to try MacOS to configure a new modem,
as the wired connection in Debian would just show connecting... and
sit there. I very very rarely use MacOS... but I figured I'd try it for this.

To my surprise, the wired connection worked in MacOS, and I also connected
with the wireless to a router in MacOS.  I rebooted into
Debian... and since that the wireless has not worked.  The wireless
continues to work in MacOS.  I am currently connecting with a wired
connection (in Debian).

I previously had the wireless configured with the b43 driver.

The install of the b43 driver is straight forward:
# apt-get install b43-fwcutter firmware-b43-installer

COMMENT:
I tried un-installing and re-installing. It didn't help.

I am running out of ideas of what to try.  The situation is
unusual... as I had the wireless working previously.

I have only found one vaguely similar description related
to VMware (  
http://askubuntu.com/questions/260209/networking-disabled-under-vmware-fusion-on-mac-os-x  
).

I am not using VMware.  The dual boot is done with rEFIt.


Here are a few things I tried/looked at:
-
# rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

COMMENT:
No blocks appear to be present.

I vaguely remember reading that MacOS puts network cards into some sort of
suspended mode... and they don't work afterward.  I read this a couple of
years ago.  I also have a MacMini... not sure it is in association with that.
In any case, I can't find anything for this vague recollection... possibly
imaginary problem.

Working the theory that MacOS screwed the network card... which is my
working theory (due to the temporal association):
  I booted into MacOS -- and disabled the AirPort... rebooted into  
Debian. Wireless still broken.

networksetup -setairportpower en1 off
Described here:  
http://osxdaily.com/2011/05/31/enable-disable-airport-wireless-connections-command-line/
  I booted into MacOS -- enabled the AirPort... rebooted into Debian.  
Wireless still broken.


It should be noted that I rarely booted into MacOS into the past.   
Preceding said, this is the first time since upgrading to Debian  
'jessie'.


Any thoughts on reseting the wireless card from MacOS?
I did find something on that here:
http://macosx.com/threads/howto-reset-the-wireless-airport-card-settings-in-os-x-10-7-x-10-8-x.321879/

-
# lshw -C Network
  *-network
   description: Ethernet interface
   product: NetXtreme BCM57765 Gigabit Ethernet PCIe
   vendor: Broadcom Corporation
   physical id: 0
   bus info: pci@:02:00.0
   logical name: eth0
   version: 10
   serial: 3c:07:54:05:c6:0d
   size: 100Mbit/s
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi msix pciexpress bus_master cap_list  
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd  
autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=tg3  
driverversion=3.137 duplex=full firmware=57765-v1.37 ip=192.168.0.194  
latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s

   resources: irq:16 memory:b040-b040 memory:b041-b041
  *-network
   description: Network controller
   product: BCM4331 802.11a/b/g/n
   vendor: Broadcom Corporation
   physical id: 0
   bus info: pci@:03:00.0
   version: 02
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list
   configuration: driver=bcma-pci-bridge latency=0
   resources: irq:17 memory:b060-b0603fff
  *-network DISABLED
   description: Wireless interface
   physical id: 1
   logical name: wlan0
   serial: b8:8d:12:1c:a4:c4
   capabilities: ethernet physical wireless
   configuration: broadcast=yes driver=b43  
driverversion=3.16.0-4-686-pae firmware=N/A link=no multicast=yes  
wireless=IEEE 802.11bg


COMMENT:
The above shows the network DISABLED.  It show the driver as b43.

-
# lsmod |grep b43
b43   362085  0
mac80211  421532  1 b43
cfg80211  350041  2 b43,mac80211
ssb51408  1 b43
rng_core   12645  1 b43
pcmcia 44245  2 b43,ssb
bcma   36446  1 b43
mmc_core   91803  4 b43,ssb,sdhci,sdhci_pci

COMMENT:
The driver b43 loads.

-
# lspci -vnn -d 14e4:
02:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme  
BCM57765 Gigabit Ethernet PCIe [14e4:16b4] (rev 10)
	Subsystem: Broadcom Corporation NetXtreme BCM57765 Gigabit Ethernet  
PCIe [14e4:16b4]

Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at b040 (64-bit, prefetchable) [size=64K]

Pooched on upgrading to new stable

2015-06-19 Thread Michael Bonert


I decided to upgrade to the latest 'stable'.

On reboot, I see gdm3 launch in the boot sequence which presumably  
starts X11. I then get a black screen.  It is as if X11 loads -- but  
get stuck.  It doesn't crash.  I can't jump to a terminal.


I have tried the key combos to kill X11 (ctrl-alt-bkspace)  that  
didn't do anything.  Interesting is that the mouse lights up when I  
move it.  I don't see a cursor of any kind.  I can adjust the  
backlighting of the keyboard... so, I know the keyboard works.


I tried booting with a i386 netinst disk (version 7.6.0)... I got to  
safe mode and I try to launch a shell -- but that fails?!?!


Preceding said, I'm not sure what to do I did get a prompt in rescue.  
I presume I have to disable gdm3  X11 somehow... so I can get to a  
prompt when I boot the machine from the hard drive.


I've had problems with X11 over the years with different computers on  
Debian... but never anything quite like this. Usually when X11  
fails... you get booted back to the command line and have a shot at  
fixing it.


Any suggestions would be welcome.

Thanks,
Michael

System - MacBookPro 2011 ?
Debian - previous stable i686


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150619064542.okjr5bookgc48...@webmail.utoronto.ca

mediawiki-extensions - package... strongly suspect bug, wonder about adv. of deb packages...

2009-02-23 Thread Michael Bonert

Hi John,

Thanks. ( http://lists.debian.org/debian-user/2009/02/msg01426.html )
I did get one module working (Cite.php).  

Above said, I have the impression that there is an incompatibility, between the
'mediawiki-extensions' package and 'mediawiki' in the stable branch.  I cannot
confirm this... as I cannot find the upstream version information for the 
'mediawiki-extensions (1.4)' package ( 
http://packages.debian.org/source/lenny/mediawiki-extensions ).

However, I note that 'sid' and 'squeeze (testing)' use the '1:1.13.3' branch of 
mediawiki.  I'm quite certain the error I'm getting (see below) arises from a 
packaging problem in Debian, i.e. Debian package 'mediawiki' (1:1.12.0-2lenny2) 
is not compatible with 'mediawiki-extensions' (1.4), as mediawiki-extensions 
(1.4) appears to be derived from extension in the 1.13 branch of mediawiki.

I know that Mediawiki ( http://www.mediawiki.org/wiki/MediaWiki ) specifies 
that the version of
the extensions has to match the program, e.g. Mediawiki version 1.12 has to use 
the extensions
for version 1.12.  I note that there has been a previous bug, which appears to 
be related to
this very issue -- based on the changelog 
http://packages.debian.org/changelogs/pool/main/m/mediawiki-extensions/mediawiki-extensions_1.4/changelog
 -- see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473785 .

I'm having problems with the ParserFunction extension (see error message below).

My set-up --

Versions:
mediawiki: 1:1.12.0-2lenny2
mediawiki-extensions: 1.4

-
As for a fix... 
I think that the 'mediawiki-extensions' package should be clearly 'mediawiki' 
version dependent, i.e.
there ought to be a package 'mediawiki-extensions 1.12-1' (for mediawiki 
version 1.12) and a package 'mediawiki 1.13-1' (for mediawiki version 1.13).

-

In any case, what are the advantages of using Debian's packages for mediawiki?
-I've had the impression it would ease upgrading... but I'm uncertain about 
that.
-I've had the impression that I'd get security updates quickly...

Currently, I'm seeing some disadvantages...
-more limited documentation (see 
http://lists.debian.org/debian-user/2009/02/msg01271.html 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516693 )
-possible additional bugs (see above)

Thanks,
Michael



Error message:
-
array(2) { [LanguageGetMagic]=  array(1) { [0]=  string(33) 
wfParserFunctionsLanguageGetMagic } [ParserClearState]=  array(2) { [0]=  
array(2) { [0]=  NULL [1]=  string(10) clearState } [1]=  array(2) { 
[0]=  object(Cite)#19 (6) { [mRefs]=  array(0) { } [mOutCnt]=  int(0) 
[mInCnt]=  int(0) [mBacklinkLabels]=  NULL [mParser]=  NULL 
[mInCite]=  bool(false) } [1]=  string(10) clearState } } } array(2) { 
[LanguageGetMagic]=  array(1) { [0]=  string(33) 
wfParserFunctionsLanguageGetMagic } [ParserClearState]=  array(2) { [0]=  
array(2) { [0]=  NULL [1]=  string(10) clearState } [1]=  array(2) { 
[0]=  object(Cite)#19 (6) { [mRefs]=  array(0) { } [mOutCnt]=  int(0) 
[mInCnt]=  int(0) [mBacklinkLabels]=  NULL [mParser]=  NULL 
[mInCite]=  bool(false) } [1]=  string(10) clearState } } } MediaWiki 
internal error.

Original exception: exception 'MWException' with message 'Unknown datatype in 
hooks for ParserClearState
' in /usr/share/mediawiki1.7/includes/Hooks.php:85
Stack trace:
#0 /usr/share/mediawiki1.7/includes/Parser.php(230): 
wfRunHooks('ParserClearStat...', Array)
#1 /usr/share/mediawiki1.7/includes/Parser.php(266): Parser-clearState()
#2 /usr/share/mediawiki1.7/includes/OutputPage.php(369): Parser-parse('This 
page has b...', Object(Title), Object(ParserOptions), true, true, NULL)
#3 /usr/share/mediawiki1.7/includes/GlobalFunctions.php(573): 
OutputPage-parse('This page has b...', true, true)
#4 /usr/share/mediawiki1.7/includes/SkinTemplate.php(315): 
wfMsgExt('viewcount', Array, '14')
#5 /usr/share/mediawiki1.7/includes/OutputPage.php(595): 
SkinTemplate-outputPage(Object(OutputPage))
#6 /usr/share/mediawiki1.7/includes/Wiki.php(250): OutputPage-output()
#7 /usr/share/mediawiki1.7/index.php(124): MediaWiki-finalCleanup(Array, 
Object(LoadBalancer), Object(OutputPage))
#8 {main}

Exception caught inside exception handler: exception 'MWException' with message 
'Unknown datatype in hooks for ParserClearState
' in /usr/share/mediawiki1.7/includes/Hooks.php:85
Stack trace:
#0 /usr/share/mediawiki1.7/includes/Parser.php(230): 
wfRunHooks('ParserClearStat...', Array)
#1 /usr/share/mediawiki1.7/includes/Parser.php(3740): Parser-clearState()
#2 /usr/share/mediawiki1.7/includes/MessageCache.php(534): 
Parser-transformMsg('$1 - {{SITENAME...', Object(ParserOptions))
#3 /usr/share/mediawiki1.7/includes/MessageCache.php(476): 
MessageCache-transform('$1 - {{SITENAME...')
#4 /usr/share/mediawiki1.7/includes/GlobalFunctions.php(450): 
MessageCache-get('pagetitle', true, false)
#5 /usr/share/mediawiki1.7/includes/GlobalFunctions.php(409): 
wfMsgGetKey('pagetitle', true, false, true)
#6 /usr/share/mediawiki1.7/includes/GlobalFunctions.php(316):

Wish list... OpenOffice.org reference manager (Bibus)

2008-01-18 Thread Michael Bonert

Hi, 

What is the best way, aside from packaging it oneself, to get some software 
packaged and on debian? 

Where can one post a wish-to-packaged request?

---
I came across a neat little reference manager for OpenOffice.org -- that 
expands on the native OO.org ref manager and can share data with MS-Word.

It exists as a deb package-- 
http://bibus-biblio.sourceforge.net/wiki/index.php/Installation#Debian
I think it would be super if it were in the Debian repository. ;-)

Should one post it as a wishlist 'bug' on OpenOffice.org Writer, Sid version 
--i.e. here: http://packages.debian.org/sid/openoffice.org-writer ?

Thanks,
Michael
-- 
GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

ALSA TV tuner problems persist -- no sound :(

2007-07-12 Thread Michael Bonert

Hi,

I'm still struggling with my tv tuner card.

I described the problem here:
http://lists.debian.org/debian-user/2007/07/msg00340.html
(ALSA problem - TV tuner no sound)

The short of the long of it: sound works-- but
not for the TV tuner.


Chris Lane had a few good suggestions:
http://lists.debian.org/debian-user/2007/07/msg00345.html

My /dev/dsp does exist:
# ls -lat /dev/dsp
crw-rw 1 root audio 14, 3 2007-07-12 18:25 /dev/dsp

Also, I tried doing what a reference in Chris' message said (see:
http://people.debian.org/~terpstra/message/20070705.081707.c4fa712b.en.html ):
# modprobe snd_pcm_oss
# modprobe snd_mixer_oss
# modprobe snd_sec_oss
FATAL: Module snd_sec_oss not found.

(I think snd_sec_oss should actually be snd_seq_oss.)


# modprobe bt878

(Then, I tried launching 'xawtv'. Sound still didn't work.)

I tried unloading and reloading the bttv and bt878 modules.
Nope.

I played with permissions on /dev/dsp
# chmod o=rw /dev/dsp

The above didn't make a difference.


I tried:
$ aoss xawtv
xawtv launched... no sound.


I tried running xawtv as root...
http://www.debian.org/doc/manuals/reference/ch-tune.en.html
$ XAUTHORITY=$HOME/.Xauthority
$ export XAUTHORITY
$ su root
# xawtv
xawtv launched... no sound.

As per 
http://www.linuxforums.org/forum/linux-desktop-x-windows/1265-xawtv-tv-my-linux-pc-picture-but-no-sound.html
I installed kdetv

# apt-get install kdetv
Reading package lists... Done
Building dependency tree... Done
The following NEW packages will be installed:
  kdetv


RUNNING kdetv from the command line gave me more info:

$ kdetv
ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL
Creating vbi proxy client, rev.
$Id: proxy-client.c,v 1.12 2006/05/31 03:54:28 mschimek Exp $
proxy_msg: connect: error 2, No such file or directory
kdetv: WARNING: VBIDecoder: vbi_capture_proxy_new error: Connection via socket 
failed, server not running.
Try to open V4L2 0.20 VBI device, libzvbi interface rev.
  $Id: io-v4l2.c,v 1.33 2006/05/22 09:00:47 mschimek Exp $
Opened /dev/vbi0
libzvbi:capture_v4l2k_new: Try to open V4L2 2.6 VBI device, libzvbi interface 
rev.
  $Id: io-v4l2k.c,v 1.42 2006/09/24 03:10:04 mschimek Exp $.
libzvbi:capture_v4l2k_new: Opened /dev/vbi0.
libzvbi:capture_v4l2k_new: /dev/vbi0 (BT878 video (ATI TV-Wonder)) is a v4l2 
vbi device,
driver bttv, version 0x0910.
libzvbi:capture_v4l2k_new: Using streaming interface.
libzvbi:v4l2_get_videostd: Current scanning system is 525.
libzvbi:v4l2_update_services: Querying current vbi parameters...
libzvbi:v4l2_update_services: ...success.
libzvbi:print_vfmt: VBI capture parameters supported: format 59455247 [GREY], 
28636363 Hz, 2048 bpl, offs 244, F1 10...25, F2 273...288, flags .
libzvbi:print_vfmt: VBI capture parameters granted: format 59455247 [GREY], 
28636363 Hz, 2048 bpl, offs 244, F1 10...25, F2 273...288, flags .
libzvbi:vbi3_raw_decoder_add_services: No services to add.
libzvbi:v4l2_update_services: Nyquist check passed.
libzvbi:v4l2_update_services: Request decoding of services 0x6c7f, strict 
level -1.
libzvbi:_vbi_sampling_par_permit_service: Service 0x0001 (Teletext System B 
625 Level 1.5) requires videostd_set 0x1, have 0x0.
libzvbi:_vbi_sampling_par_permit_service: Service 0x0003 (Teletext System 
B, 625) requires videostd_set 0x1, have 0x0.
libzvbi:_vbi_sampling_par_permit_service: Service 0x0001 (Teletext System B 
625 Level 1.5) requires videostd_set 0x1, have 0x0.
libzvbi:_vbi_sampling_par_permit_service: Service 0x0003 (Teletext System 
B, 625) requires videostd_set 0x1, have 0x0.
libzvbi:_vbi_sampling_par_permit_service: Service 0x0004 (Video Program 
System) requires videostd_set 0x1, have 0x0.
libzvbi:_vbi_sampling_par_permit_service: Service 0x0400 (Wide Screen 
Signalling 625) requires videostd_set 0x1, have 0x0.
libzvbi:_vbi_sampling_par_permit_service: Service 0x0008 (Closed Caption 
625, field 1) requires videostd_set 0x1, have 0x0.
libzvbi:_vbi_sampling_par_permit_service: Service 0x0010 (Closed Caption 
625, field 2) requires videostd_set 0x1, have 0x0.
libzvbi:v4l2_update_services: Will capture services 0x0060, added 0x60 
commit=1.
libzvbi:v4l2_stream_alloc: Requesting 16 streaming i/o buffers.
libzvbi:v4l2_stream_alloc: Mapping 16 streaming i/o buffers.
libzvbi:capture_v4l2k_new: Successfully opened /dev/vbi0 (BT878 video (ATI 
TV-Wonder)).
kdetv: WARNING: MainWindow::setupInfraRed(): Lirc not available
kdetv: WARNING: VolumeController::doSetVolume: AudioManager failed, trying 
SourceManager
kdetv: WARNING: VolumeController::doSetVolume: AudioManager failed, trying 
SourceManager
libzvbi:v4l2_stream: Failed to dequeue buffer, errno 5.
kdetv: WARNING: VbiDecoder: VBI capture error: Input/output error
libzvbi:v4l2_stream_stop: Suspending stream.
Creating vbi proxy client, rev.
$Id: proxy-client.c,v 1.12 2006/05/31 03:54:28 mschimek Exp $
proxy_msg: connect: error 2, No such file or directory
kdetv: WARNING: VBIDecoder:

OSS, ALSA, tv tuner problems persist :(

2007-07-12 Thread Michael Bonert

Addendum to:
http://lists.debian.org/debian-user/2007/07/msg01181.html

I'm a big leap ahead.  I had a silly problem related to the volume (it was near 
zero).  

The fix is:
# apt-get install aumix

$ aumix
The TV tuner volume is influenced by the CD volume setting.  


Currently, I have a feedback problem. I wonder whether OSS and ALSA are 
fighting the background.  Any case, I have to do some more experimentation.  
The feedback goes away if I disable the KDE sound system.  That said, I have 
the sneaky suspicion it might be a driver bug.  I have a vague memory of the tv 
tuner not always playing nice. Several years ago, when I used it under Windows 
it created problems.  If I remember correctly, it also caused some problems in 
Debian at one point.

Michael

My 'dump-mixers' is now...

$ dump-mixers
/dev/mixer = EMU10K1 (SigmaTel STAC9708,11)
  vol( 0) :  stereo  rec   100/100
  bass   ( 1) :  stereo73/73
  treble ( 2) :  stereo70/70
  synth  ( 3) :  stereo100/100
  pcm( 4) :  stereo90/90
  speaker( 5) :  mono  48
  line   ( 6) :  stereo  rec   20/20
  mic( 7) :  monorec   20
  cd ( 8) :  stereo  rec   50/50
  pcm2   (10) :  stereo100/100
  igain  (12) :  stereo0/0
  line1  (14) :  stereo  rec   0/0
  dig1   (17) :  stereo47/47
  phin   (20) :  monorec   0
  phout  (21) :  monorec   100
  video  (22) :  stereo  rec*  0/0
/dev/mixer1 = MPU-401 UART (mixer10)

... earlier it was:
$ dump-mixers
/dev/mixer = EMU10K1 (SigmaTel STAC9708,11)
  vol( 0) :  stereo  rec   94/94
  bass   ( 1) :  stereo50/50
  treble ( 2) :  stereo50/50
  synth  ( 3) :  stereo100/100
  pcm( 4) :  stereo50/50
  speaker( 5) :  mono  0
  line   ( 6) :  stereo  rec   0/0
  mic( 7) :  monorec*  0
  cd ( 8) :  stereo  rec   0/0
  pcm2   (10) :  stereo100/100
  igain  (12) :  stereo0/0
  line1  (14) :  stereo  rec   0/0
  dig1   (17) :  stereo0/0
  phin   (20) :  monorec   0
  phout  (21) :  monorec   100
  video  (22) :  stereo  rec   0/0
/dev/mixer1 = MPU-401 UART (mixer10)

Hardware:

Athlon 2200 XP
ASUS A7N8X (Motherboard)
512 MB RAM

TVCard: ATI-TV Wonder
Sound: Creative Labs Sound Blaster Live!

Software:

Debian GNU/Linux -- testing
Kernel -- Linux version 2.6.18-4-k7 (Debian 2.6.18.dfsg.1-12) ([EMAIL 
PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP 
Mon Mar 26 17:57:15 UTC 2007
KDE -- 3.5.7
-- 
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten 
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

ALSA problem - TV tuner no sound

2007-07-04 Thread Michael Bonert

I recently upgraded kernels (2.6.18-4-k7 - 2.6.11-1-k7) and sound systems (OSS 
- ALSA).

Sound, aside from the TV tuner, works fine.

My TV tuner worked like a snap under OSS and made use of the following drivers:
 bttv
 bt878

I've discovered that 'bttv' is need for 'xawtv' to load.  It appears
to be essential for the video.
bt878, as far as I can tell, is the OSS driver.


I thought replacing 'bt878' with 'snd_bt87x' would be the fix -- NOPE.

I thought things might work with the compatibility package, i.e. 
apt-get install alsa-oss  apt-get install oss-compat -- NOPE.


I ran into this problem about 2 years ago (see: 
http://linux.derkeiler.com/Mailing-Lists/Debian/2005-01/4381.html )
-- gave-up and went back to OSS.  Seems the problem-- still isn't 
resolved cleanly.


I blacklisted 'bt878' as described here:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/29789

# vi /etc/modprobe.d/blacklist
-
# added by MB - 2 Jul 2007
# 
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/29789
blacklist bt878
-

# vi /etc/discover.conf 
-
# the following was added by MB -- to avoid that the OSS driver loads
# see: http://www.linuxmafia.com/faq/Debian/alsa.html
skip bt878
-
The two things above avoided that 'bt878' loads on boot-up... but gots me no 
further ahead on the TV tuner sound.


Software:
-
ALSA version:
$ more /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 
2006 UTC).

Kernel:
$ more /proc/version
Linux version 2.6.18-4-k7 (Debian 2.6.18.dfsg.1-12) ([EMAIL PROTECTED]) 
(gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #
1 SMP Mon Mar 26 17:57:15 UTC 2007
-


I read about a problem with artsd (KDE), bttv and ALSA.  Turning off the KDE 
sound system didn't change things.


Looking at the modules...
$ more /proc/asound/modules
 0 snd_emu10k1
 1 snd_mpu401

-
I haven't figured-out what 'snd_mpu401' is... 


I did try:
# modprobe -r snd_mpu401 snd_mpu401_uart
This didn't make a change I noticed (other sound still worked).


It bothers me that I only find my sound card:
# cat /proc/asound/cards
 0 [Live   ]: EMU10K1 - SBLive 5.1 [SB0060]
  SBLive 5.1 [SB0060] (rev.7, serial:0x80611102) at 0xd400, 
irq 217
 1 [UART   ]: MPU-401 UART - MPU-401 UART
  MPU-401 UART at 0x330, irq 10
-
I'm not sure what 'MPU-401' is. (My sound card uses: 'snd_emu10k1'.)


'lspci' finds the sound hardware:
$ lspci 
snippage
01:07.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture 
(rev 02)
01:07.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 
02)
01:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
01:0a.1 Input device controller: Creative Labs SB Live! Game Port (rev 07)
snippage
-


My impression is that the problem lies at the level of the kernel-- after
looking at the boot log with 'dmesg':

If I block loading of 'bt878' with blacklisting in /etc/modprobe.d/blacklist 
and /etc/discover.conf dmesg looks like:

$ dmesg |grep bt
bttv: driver version 0.9.16 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
bttv0: Bt878 (rev 2) at :01:07.0, irq: 209, latency: 32, mmio: 0xe400
bttv0: detected: ATI TV Wonder [card=63], PCI subsystem ID is 1002:0001
bttv0: using: ATI TV-Wonder [card=63,autodetected]
bttv0: gpio: en=, out= in=00ff [init]
bttv0: using tuner=19
bttv0: i2c: checking for MSP34xx @ 0x80... found
msp3400 2-0040: MSP3430G-A4 found @ 0x80 (bt878 #0 [sw])
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
bttv0: i2c: checking for TDA9887 @ 0x86... not found
tuner 2-0060: chip found @ 0xc0 (bt878 #0 [sw])
bttv0: registered device video0
bttv0: registered device vbi0
bttv0: PLL: 28636363 = 35468950 .. ok
bttv0: PLL can sleep, using XTAL (28636363).
bttv0: PLL: 28636363 = 35468950 .. ok
bttv0: unloading
bttv: driver version 0.9.16 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
bttv0: Bt878 (rev 2) at :01:07.0, irq: 209, latency: 32, mmio: 0xe400
bttv0: detected: ATI TV Wonder [card=63], PCI subsystem ID is 1002:0001
bttv0: using: ATI TV-Wonder [card=63,autodetected]
bttv0: gpio: en=, out= in=00ff [init]
msp3400 2-0040: MSP3430G-A4 found @ 0x80 (bt878 #0 [sw])
tuner 2-0060: chip found @ 0xc0 (bt878 #0 [sw])
bttv0: using tuner=19
bttv0: i2c: checking for MSP34xx @ 0x80... found
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
bttv0: i2c: checking for TDA9887 @ 0x86... not found
bttv0: registered device video0
bttv0: registered device vbi0
bttv0:

Re: Sound problems... had OSS working... now neither ALSA or OSS works(complicated)

2007-05-22 Thread Michael Bonert

This is in follow-up to an earlier post... 
http://lists.debian.org/debian-user/2007/05/msg03451.html

I'm sort of back to where I was before this started... but a bit more confused.

I figured-out the volume wasn't high enough to hear the music. (On that, I 
don't know
what the wisdom is of defaulting the volume to zero is.  It doesn't make a 
whole lot of sense to me.)

I played with 'alsamixer' and 'aumix'.  Both seem to adjust the same things.

Any case, it seems the lines in 'modprobe.conf' added by 'alsaconf' are 
important:
# more /etc/modprobe.conf
install trident /sbin/modprobe --ignore-install trident  /usr/sbin/alsactl 
restore /dev/null 21 || :
remove trident { /usr/sbin/alsactl store /dev/null 21 || : ; }; 
/sbin/modprobe -r --ignore-remove trident
snippage

Without those two lines the KDE sound system isn't happy.


Any case, I'm back to where I was yesterday-- in summary:
* Flash animation in IceWeasel -- kaputt.
* KDE sound -- works.
* xine (sound) -- works.
* XMMS -- works.


That said... when I do:
-
# aplay Bach - Conzona in D minor - BWV 588.mp3
Playing raw data 'Bach - Conzona in D minor - BWV 588.mp3' : Unsigned 8 bit, 
Rate 8000 Hz, Mono
-
I get a whole bunch of random noise.

The same (random noise) results when I do:
# speaker-test


The modules changed a bit with the addition of the lines to 
'/etc/modprobe.conf' (without the two lines):
-
# lsmod |grep snd
snd_pcm_oss53344  0
snd_mixer_oss  19872  1 snd_pcm_oss
snd_ali545123556  0
snd_ac97_codec 78360  1 snd_ali5451
snd_pcm92712  3 snd_pcm_oss,snd_ali5451,snd_ac97_codec
snd_timer  24644  1 snd_pcm
snd55300  6 
snd_pcm_oss,snd_mixer_oss,snd_ali5451,snd_ac97_codec,snd_pcm,snd_timer
soundcore   9664  1 snd
snd_page_alloc 10020  1 snd_pcm
-

Beyond that, I learned that -- the number following the 4 or 5 digit number
signifies use somehow.  When I have XMMS running and producing music the above
looks like this:
-
# lsmod |grep snd
snd_pcm_oss53344  1
snd_mixer_oss  19872  1 snd_pcm_oss
snd_ali545123556  1
snd_ac97_codec 78360  1 snd_ali5451
snd_pcm92712  3 snd_pcm_oss,snd_ali5451,snd_ac97_codec
snd_timer  24644  1 snd_pcm
snd55300  6 
snd_pcm_oss,snd_mixer_oss,snd_ali5451,snd_ac97_codec,snd_pcm,snd_timer
soundcore   9664  2 snd
snd_page_alloc 10020  1 snd_pcm
-

Playing music and with the two lines in '/etc/modprobe.conf' + a reboot:
-
# lsmod |grep snd
snd_seq52560  0
snd_seq_device  8652  1 snd_seq
snd_pcm_oss53344  1
snd_mixer_oss  19872  1 snd_pcm_oss
snd_ali545123556  2
snd_ac97_codec 78360  1 snd_ali5451
snd_pcm92712  3 snd_pcm_oss,snd_ali5451,snd_ac97_codec
snd_timer  24644  2 snd_seq,snd_pcm
snd55300  10 
snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_ali5451,snd_ac97_codec,snd_pcm,snd_timer
soundcore   9664  2 snd
snd_page_alloc 10020  1 snd_pcm
-


At the moment, I'm not sure what to make of the situation.

The OSS driver (trident) isn't loaded. So, I have the impression it is ALSA that
is giving me sound.
1. The use of 'snd_ali5451' suggests ALSA is being used.
2. 'cat /proc/asound/version' suggests ALSA is indeed installed...


That said, I'm bothered by the fact that OSS seems to have devices...
# cat /proc/asound/oss/devices
  0: [0- 0]: mixer
  3: [0- 3]: digital audio

I'm also bothered by the fact that 'speaker-test' and 'aplay' don't work.

I don't know what 'speaker-test' is supposed to sound like-- but I doubt
it is a bunch of noise.

Michael


System/Hardware

Toshiba Satellite A20 -- A20-31Q: 2.53GHz (PSA20C-0231Q)

Processor: Intel Pentium IV, 2.53GHz

Memory: 512 MB

Install log: http://individual.utoronto.ca/bonert/debian_install.html

Debian GNU/Linux release: testing

Kernel: Linux version 2.6.11-1-686 ([EMAIL PROTECTED]) (gcc version 3.3.6
(Debian 1:3.3.6-6)) #1 Mon Jun 20 22:00:38 MDT 2005

KDE: 3.5.5
-- 
Pt! Schon vom neuen GMX MultiMessenger gehört?
Der kanns mit allen: http://www.gmx.net/de/go/multimessenger


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Sound problems... had OSS working... now neither ALSA or OSS works (complicated)

2007-05-21 Thread Michael Bonert

I tried switching to ALSA earlier today... seeing how it is the newer
thing.  Also, I'd hoped of getting sound working in IceWeasel --specifically
in Flash animations.

-
I know the Flash animation problem can be solved with 'Full duplex' i.e.

Full duplex (off) is supposed to fix this problem:
K Menu -- Control Center -- Sound System -- Hardware -- Full duplex (no 
check mark)

Described here:
http://72.14.205.104/search?q=cache:Q1iN5-33Ud4J:www.linuxquestions.org/questions/showthread.php%3Ft%3D453292+video,+no+sound,+debianhl=enct=clnkcd=1gl=us
http://binnyva.blogspot.com/2006/10/no-sound-in-flash-running-on-firefox-in.html

However, it didn't do anything for me.  So, I decided to embark on installing 
ALSA... figuring it might be the bug fix.

-
ALSA seemed to install alright... but sound never worked.
At first it seemed to be a permissions issue... but I think that is now sorted.

To test this definitively I did the following:
$ XAUTHORITY=$HOME/.Xauthority
$ export XAUTHORITY
$ su root
Password:
# xmms
XMMS didn't produce any sound... or any errors.

-
As far as I can tell ALSA is installed:
# cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.8 (Thu Jan 13 09:39:32 
2005 UTC).

-
I hardware is there:
# cat /proc/asound/cards
0 [A5451  ]: ALI5451 - ALI 5451
 ALI 5451 at 0x1000, irq 11

# lspci -v
00:06.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link 
Controller Audio Device (rev 02)
Subsystem: Toshiba America Info Systems Unknown device 0221
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at 1000 [size=256]
Memory at 2000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [dc] Power Management version 2

-
aplay seems to detect the hardware...

# aplay -l
 List of PLAYBACK Hardware Devices 
card 0: A5451 [ALI 5451], device 0: ALI 5451 [ALI 5451]

If I give it a file--it seems to play it... though in mono and I don't hear 
anything.
# aplay Bach - Conzona in D minor - BWV 588.mp3
Playing raw data 'Bach - Conzona in D minor - BWV 588.mp3' : Unsigned 8 bit, 
Rate 8000 Hz, Mono

-
I think the right kernel modules are loaded:

# lsmod |grep snd
snd_pcm_oss53344  0
snd_mixer_oss  19872  1 snd_pcm_oss
snd_ali545123556  0
snd_ac97_codec 78360  1 snd_ali5451
snd_pcm92712  3 snd_pcm_oss,snd_ali5451,snd_ac97_codec
snd_timer  24644  1 snd_pcm
snd55300  6 
snd_pcm_oss,snd_mixer_oss,snd_ali5451,snd_ac97_codec,snd_pcm,snd_timer
soundcore   9664  1 snd
snd_page_alloc 10020  1 snd_pcm

I'm NOT reassured by the numbering above.  I wonder about the '0' behind 
'snd_ali5451'.

The trident driver (OSS) is not load (as shown above)-- I tried different 
variations with and without the driver. 'alsact' (alsactl = advanced controls 
for ALSA soundcard driver) seems to want the OSS driver around... though I 
haven't found a reason why it shouldn't work without it.  

Adding the trident driver seems like a complication at this point.  So, I 
decided not to load it.

In any case, I wondered whether the trident driver blocks the sound-- by 
loading first.  To test this I specified the 'snd_ali5451' ahead of 'trident' 
in my '/etc/modules' files.  This didn't do anything for me.

-
I used ALSA config tool to set-up ALSA, i.e.: 

# alsaconf
Unloading ALSA sound driver modules: snd-ali5451 snd-ac97-codec snd-pcm 
snd-timer snd-page-alloc.
Building card database...


Running update-modules...
Loading driver...
Setting default volumes...
Saving the mixer setup used for this in /var/lib/alsa/asound.state.


===

 Now ALSA is ready to use.
 For adjustment of volumes, use your favorite mixer.

 Have a lot of fun!

-
The above modifies '/etc/modprobe.conf'


The following was my modprobe.conf file:
# more /etc/modprobe.conf
install trident /sbin/modprobe --ignore-install trident  /usr/sbin/alsactl res
tore /dev/null 21 || :
remove trident { /usr/sbin/alsactl store /dev/null 21 || : ; }; /sbin/modprob
e -r --ignore-remove trident
alias usb-controller ehci-hcd
alias usb-controller1 ohci-hcd
alias scsi_hostadapter alim15x3
# 

trident is the OSS driver.  I wondered whether this is creating a conflicit.
I removed the top two lines and removed the trident module.  It didn't help me 
get sound.

-
The one thing it did do is -- give me noise on the speakers when I did the 
following
test (as suggested here -- http://xtronics.com/reference/Debian-sound.html ):

# alsactl store
# speaker-test

speaker-test 1.0.13

Playback device is default
Stream parameters are 48000Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 32 to 32768
Period size range from 32 to 32768
Using max buffer size 32768
Periods = 4
was set period_size

Kernel upgrade problems (again) - 2.6.11 - 2.6.18, video pooched

2007-02-24 Thread Michael Bonert

I tried upgrading the kernel today on my machine and have a problem 
that is very similar to about a year ago... that I never completely 
figured-out.  

I think the problem I'm having is the same as before-- and it's described here:

  http://lists.debian.org/debian-user/2006/07/msg03029.html

I downgraded the kernel to 2.6.11 (in Jul 2006) when I encountered the 
problem-- and the problems all went away.  

Someone suggested the problem is hotplug... this time I purged hotplug with:
# aptitude purge hotplug

-
Today I upgraded to 2.6.18-3-686 from kernel-image-2.6.11-1-686 (image for 
version 2.6.11 on PPro/Celeron/PII/PIII/P4).

# apt-get install linux-image-2.6.18-3-686 
Reading package lists... Done
Building dependency tree... Done
The following extra packages will be installed:
  initramfs-tools
Suggested packages:
  linux-doc-2.6.18
Recommended packages:
  libc6-i686
The following NEW packages will be installed:
  initramfs-tools linux-image-2.6.18-3-686
0 upgraded, 2 newly installed, 0 to remove and 4 not upgraded.
Need to get 16.8MB of archives.
After unpacking 51.2MB of additional disk space will be used.
Do you want to continue [Y/n]? Y   
Get:1 http://ftp.is.debian.org testing/main initramfs-tools 0.85e [62.5kB]
Get:2 http://ftp.is.debian.org testing/main linux-image-2.6.18-3-686 2.6.18-7 
[16.7MB]
Fetched 16.8MB in 30s (541kB/s)
Preconfiguring packages ...
Selecting previously deselected package initramfs-tools.
(Reading database ... 96363 files and directories currently installed.)
Unpacking initramfs-tools (from .../initramfs-tools_0.85e_all.deb) ...
Selecting previously deselected package linux-image-2.6.18-3-686.
Unpacking linux-image-2.6.18-3-686 (from 
.../linux-image-2.6.18-3-686_2.6.18-7_i386.deb) ...
Done.
Setting up initramfs-tools (0.85e) ...
Installing new version of config file /etc/initramfs-tools/initramfs.conf ...
/boot/initrd.img-2.6.11-1-686 has been altered. Cannot update.

Setting up linux-image-2.6.18-3-686 (2.6.18-7) ...

 Hmm. The package shipped with a symbolic link /lib/modules/2.6.18-3-686/source
 However, I can not read the target: No such file or directory
 Therefore, I am deleting /lib/modules/2.6.18-3-686/source

Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
You already have a LILO configuration in /etc/lilo.conf
Running boot loader as requested
Testing lilo.conf ...
Testing successful.
Installing the partition boot sector...
Running /sbin/lilo  ...
Installation successful.

cobalamin:/home/michael#
# apt-get install libc6-i686
Reading package lists... Done
Building dependency tree... Done
The following NEW packages will be installed:
  libc6-i686
0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded.
Need to get 1117kB of archives.
After unpacking 2535kB of additional disk space will be used.
Get:1 http://ftp.is.debian.org testing/main libc6-i686 2.3.6.ds1-11 [1117kB]
Fetched 1117kB in 3s (302kB/s)
Selecting previously deselected package libc6-i686.
(Reading database ... 98546 files and directories currently installed.)
Unpacking libc6-i686 (from .../libc6-i686_2.3.6.ds1-11_i386.deb) ...
Setting up libc6-i686 (2.3.6.ds1-11) ...
cobalamin:/home/michael#  

-copying bootsector
# dd if=/dev/hda3 of=/home/michael/transfer/bootsect-2.6.18-3.lnx bs=512 count=1
1+0 records in
1+0 records out
512 bytes transferred in 0.076084 seconds (6729 bytes/sec)

-boot into windows replace stuff 
-edit C:\boot.ini
-reboot

Upgrade worked but... -- it's new kernel
$  more /proc/version
Linux version 2.6.18-3-686 (Debian 2.6.18-7) ([EMAIL PROTECTED]) (gcc version 
4.1
.2 20061115 (prerelease) (Debian 4.1.1-20)) #1 SMP Mon Dec 4 16:41:14 UTC 2006
[EMAIL PROTECTED]:~$

-sound pooched -- not much of a concern... at the moment.
-video pooched --  there are horizontal line -- that come and go (it sort 
of looks like the refresh rate is too high).  I didn't change any settings in 
X.  
I noticed a fuzziness in the text -- while linux booted up.  The video problem 
were not seen in with the older kernel and were not seen in Windoze XP.


Is this somehow related to libc6 ???
Could this be a driver issue?

Aside from that... I don't understand the consequence of:
---
 Hmm. The package shipped with a symbolic link /lib/modules/2.6.18-3-686/source
 However, I can not read the target: No such file or directory
 Therefore, I am deleting /lib/modules/2.6.18-3-686/source
---


Any suggestions would be much appreciated. -Thanks, Michael


System/Hardware

Toshiba Satellite A20 -- A20-31Q: 2.53GHz (PSA20C-0231Q)
Processor: Intel Pentium IV, 2.53GHz
Memory: 512 MB
Install log: http://individual.utoronto.ca/bonert/debian_install.html

Debian GNU/Linux release: testing
Kernel: Linux version 2.6.11-1-686 ([EMAIL PROTECTED]) (gcc version 3.3.6 
(Debian 1:3.3.6-6)) #1 Mon Jun 20 22:00:38 MDT 2005
-- 
Ist Ihr Browser

fstab entries for external USB hard drives led to fsck.ext3 failure on boot, bug?

2006-11-01 Thread Michael Bonert

I am writing in follow-up to an earlier message called 
'[EMAIL PROTECTED] fsck! On boot it dies... yet drive okay?!?' which can be 
found here:
http://lists.debian.org/debian-user/2006/10/msg03405.html 

and the follow-up:
http://lists.debian.org/debian-user/2006/10/msg03563.html 
 (thanks David for your comments)

I haven't figured-out exactly what the problem is.  However, I 
have narrowed it down and more-or-less resolved it for the 
time being.  

On booting my Debian system got something like:
-
[sbin/fsck.ext3 (1) -- /mnt/mdk] fsck.ext3 -a -C0 /dev/hda11
/dev/hda11: clean, 5765/130048 files, 1425960/2596497 blocks
Reiserfs super block in block 16 on 0x309 of format 3.6 with standard journal
Blocks (total/free): 200800/192582 by 4096 bytes.
Filesystem clear.
Reiserfs super block in block 16 on 0x30a of format 3.6 with standard journal
Blocks (total/free): 200800/192582 by 4096 bytes.
Filesystem clear.
fsck died with exit status 9
File system check failed.
A log is being saved in /var/log/fsck/checkfs if that location is writable.
Please repair the file system manually.
A maintenance shell will now be started.
CONTROL-D will terminate this shell and resume system boot.
Give root password for maintenance (or type Control-D to continue):
-


My '/etc/fstab' was as follows:
-
# /etc/fstab: static file system information.
#
# file system mount point   type  options   dump  pass
proc/proc   procdefaults0   0
/dev/hda2   /mnt/transfer   vfatrw,user,noexec,umask= 0   2
/dev/hda3   /boot   ext3defaults0   2
/dev/hda5   /   reiserfs defaults0   1
/dev/hda6   noneswapsw  0   0
/dev/hda7   /usrreiserfs defaults0   2
/dev/hda8   /varreiserfs defaults0   2
/dev/hda9   /tmpreiserfs defaults0   2
/dev/hda10  /home   reiserfs defaults0   2
# /dev/hda11  /mnt/media  reiserfs defaults0   2
# /dev/hda11  /mnt/mdkreiserfs defaults   0   2
/dev/hda11  /mnt/mdkext3defaults0   2
/dev/hdc/media/cdromiso9660 ro,user,noauto  0   0
/dev/fd0/media/floppy   autorw,user,noauto  0   0
/dev/hdc/cdrom  iso9660 ro,user,noauto  0   0
/dev/hda1   /mnt/winxp  ntfsro,user,noexec,umask=022  0   0
/dev/sda1   /mnt/external   vfatrw,user,noauto,noexec,umask=   
0   2
/dev/sda2   /mnt/f_external ext3rw,user,noauto,noexec0   2
/dev/sda3   /mnt/g_external ext3rw,user,noauto,noexec0   2
-

When I commented-out, i.e. added a # infront of the '/dev/sda2' and 
'/dev/sda3' entries in the fstab file the error did NOT occur.

What this implies is 'fsck.ext' is failing on '/dev/sda2' and '/dev/sda3' 
despite that they aren't being mounted.  The noauto option in the fstab 
file (briefly discussed here 
-- http://www.ibiblio.org/pub/linux/docs/Raven/EyeView/SSR05/SSR05-09.htm ) 
is a setting that I thought should avoid this problem but it 
(1) does NOT avoid the failure of fsck and 
(2) the error message deliver by 'fsck'  'exit status 9' (a combination 
of 'exit status 1' and 'exit status 8', which are File system errors 
corrected and Operational error respectively) does NOT suggest a 
problem with '/dev/sda2' and/or '/dev/sda3'.


There is either a subtility I do not understand about external drives/mount in 
/etc/fstab
  --OR-- 
there is a bug in 'fsck.ext3'.

The objective of the last two line in my fstab i.e.:
-
/dev/sda2   /mnt/f_external ext3rw,user,noauto,noexec 0   2
/dev/sda3   /mnt/g_external ext3rw,user,noauto,noexec 0   2
-
were to allow me to quickly mount an external hard drive (after plugging-in) 
with the two following commands:
-
# mount /dev/sda2
# mount /dev/sda3
-
as described at the following URL under the heading MOUNT EXTERNAL USB HARD 
DRIVE:
http://individual.utoronto.ca/bonert/debian_install.html

If the above fsck.ext3 failure is due to nothing but ignorance of fstab 
settings on my part I have the following to say:
(1) the fsck.ext3 error messages leave a little bit to be desired
(2) the default behaviour of a debian install should be allow writing 
of the error file in '/var/log/fsck/checkfs' or another location 
(i.e. /tmp).  It seems a bit sloppy to me that some executables 
(fsck.ext3) in debian on boot try to write to a position to which 
they ordinarily do not have adequate permissions.

Michael


System/Hardware

Toshiba Satellite A20 -- A20-31Q: 2.53GHz (PSA20C-0231Q)
Processor: Intel Pentium IV, 2.53GHz
Memory: 512 MB
Install log: http://individual.utoronto.ca/bonert/debian_install.html

Debian

[EMAIL PROTECTED] fsck! On boot it dies... yet drive okay?!?

2006-10-29 Thread Michael Bonert

On booting my Debian system I get something like:
-
[sbin/fsck.ext3 (1) -- /mnt/mdk] fsck.ext3 -a -C0 /dev/hda11
/dev/hda11: clean, 5765/130048 files, 1425960/2596497 blocks
Reiserfs super block in block 16 on 0x309 of format 3.6 with standard journal
Blocks (total/free): 200800/192582 by 4096 bytes.
Filesystem clear.
Reiserfs super block in block 16 on 0x30a of format 3.6 with standard journal
Blocks (total/free): 200800/192582 by 4096 bytes.
Filesystem clear.
fsck died with exit status 9
File system check failed.
A log is being saved in /var/log/fsck/checkfs if that location is writable.
Please repair the file system manually.
A maintenance shell will now be started.
CONTROL-D will terminate this shell and resume system boot.
Give root password for maintenance (or type Control-D to continue):
-
( 'dmesg' for some reason doesn't record this... it seems to be pouched-- so, I 
was copying this out by hand...)


If I run fsck manually it says my the drive is clean:
-
# fsck.ext3 -a -C0 /dev/hda11
/dev/hda11: clean, 5765/1300480 files, 1425960/2596497 blocks
-

If I remove the drive '/dev/hda11' from the '/etc/fstab' Debian complains about 
'/dev/hda10'.

Based on what I've read 'exit status 9' is a combination of exit status 1 and 
exit status 8, i.e. File system errors corrected + Operational error -- 
neither of which I really understand.

In any case, I think the error is related to the '/etc/fstab' file somehow.  I 
read somewhere that the order of the entries in the fstab file matter-- how 
though was not explained.  

My '/etc/fstab' is as follows:
-
# /etc/fstab: static file system information.
#
# file system mount point   type  options   dump  pass
proc/proc   procdefaults0   0
/dev/hda2   /mnt/transfer   vfatrw,user,noexec,umask=   0   
2
/dev/hda3   /boot   ext3defaults0   2
/dev/hda5   /   reiserfs defaults0   1
/dev/hda6   noneswapsw  0   0
/dev/hda7   /usrreiserfs defaults0   2
/dev/hda8   /varreiserfs defaults0   2
/dev/hda9   /tmpreiserfs defaults0   2
/dev/hda10  /home   reiserfs defaults0   2
# /dev/hda11  /mnt/media  reiserfs defaults0   2
# /dev/hda11  /mnt/mdkreiserfs defaults   0   2
/dev/hda11  /mnt/mdkext3defaults0   2
/dev/hdc/media/cdromiso9660 ro,user,noauto  0   0
/dev/fd0/media/floppy   autorw,user,noauto  0   0
/dev/hdc/cdrom  iso9660 ro,user,noauto  0   0
/dev/hda1   /mnt/winxp  ntfsro,user,noexec,umask=0220   0
/dev/sda1   /mnt/external   vfatrw,user,noauto,noexec,umask=   
0   2
/dev/sda2   /mnt/f_external ext3rw,user,noauto,noexec   0   2
/dev/sda3   /mnt/g_external ext3rw,user,noauto,noexec   0   2
-
The '/dev/sda1', '/dev/sda2' and '/dev/sda3' are for mounting 
external hard drives.

What totally doesn't make sense to me is the 'reiserfs' bit.  The drive used to 
be formated with reiserfs... but is no longer.  I suppose it could be related 
to one of the other drives-- but if that's true the way the error message is 
presented is pretty strange.

If someone could enlighten me about the boot sequence related to the mounting 
of drives and the exit status and what it could posssibly mean I'd much 
appreciate it.  Thanks.


System/Hardware

Toshiba Satellite A20 -- A20-31Q: 2.53GHz (PSA20C-0231Q)
Processor: Intel Pentium IV, 2.53GHz
Memory: 512 MB
Install log: http://individual.utoronto.ca/bonert/debian_install.html
-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

kernel upgrade disaster, hotplug and linux-image-2.6.15-1-686

2006-07-31 Thread Michael Bonert

I tried upgrading kernels today (from 2.6.11 to 2.6.15).

My motivation was my computer being intermittently and non-reproducibly
unresponsive for long times (30 sec) when viewing large images (example:
http://upload.wikimedia.org/wikipedia/en/0/05/Coronary_artery_bypass_surgery_Image_657B-PH.jpg
) when using Firefox and/or Mozilla. Now, I know that large images are going
to work the computer-- and I can't expect an instant response... but my gut
says what is happening isn't right and there is problem somewhere.

When Firefox deals with these large images I cannot drop to a console and kill
Firefox-- the keyboard is essentially unresponsive and the mouse has a huge
time delay in responsiveness. I don't think this is right-- and my suspicion
was and still is a kernel/memory management problem of some sort (as unlike
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=360079 -- I have keyboard
locking outside of Firefox Mozilla).

Any case, Firefox aside (and perhaps some unrealistic expectations), the
upgrade was disaster.

After the upgrade
-the display was bad-- it looked like the refresh rate was too high
-sound was pooched
-wireless interface was pooch

What happened is below in detail.

My question-- before trying another kernel upgrade or considering taking a stab
at 2.6.14:
1. Is the package 'libc6-i686' essential for replacing the functionality of the
'hotplug' package?
2. Does not purging 'hotplug' cause problems? (During the install of 2.6.15 it
said that ought to be done.)
3. Is anyone aware of issues with 2.6.11 -- and the locking behaviour I get
with Firefox Mozilla?

Thanks,
Michael

===
Kernel UPGRADE 31 July 2006 (attempt)
===

-get a list of kernels that are installed
# COLUMNS=132 dpkg --list |grep kernel
ii initrd-tools0.1.84.1tools to create
initrd image for prepackaged Linux kernel
ii iproute 20051007-4 Professional tools
to control the networking in Linux kernels
ii iptables1.3.3-2 Linux kernel 2.4+
iptables administration tools
rc kcmlinuz3.3.2-1 KDE Frontend for
the Linux kernel configuration
rc kernel-image-2.4.25-1-386 2.4.25-3Linux kernel image
for version 2.4.25 on 386.
ii kernel-image-2.6.11-1-686 2.6.11-7Linux kernel image
for version 2.6.11 on PPro/Celeron/PII/PIII/P4.
rc kernel-image-2.6.5-1-3862.6.5-4 Linux kernel image
for version 2.6.5 on 386.
ii kernel-image-2.6.8-1-6862.6.8-10Linux kernel image
for version 2.6.8 on PPro/Celeron/PII/PIII/PIV.
ii libdrm2 2.0.1-1 Userspace interface
to kernel DRM services -- runtime
ii module-init-tools 3.2.2-3 tools for managing
Linux kernel modules
cobalamin:/home/michael#

-remove back-up kernel --so there is space for a new one
cobalamin:/home/michael# apt-get remove kernel-image-2.6.8-1-686
Reading package lists... Done
Building dependency tree... Done
The following packages will be REMOVED:
kernel-image-2.6.8-1-686
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0B of archives.
After unpacking 43.3MB disk space will be freed.
Do you want to continue [Y/n]? Y
(Reading database ... 92904 files and directories currently installed.)
Removing kernel-image-2.6.8-1-686 ...
The link /vmlinuz.old is a dangling link
Removing symbolic link /vmlinuz.old
Unless you used the optional flag in lilo,
you may need to re-run lilo
The link /initrd.img.old is a dangling link
Removing symbolic link /initrd.img.old
Unless you used the optional flag in lilo,
you may need to re-run lilo
cobalamin:/home/michael#

-find new kernel
cobalamin:/home/michael# apt-cache search kernel-image |grep 2.6

-get new kernel
cobalamin:/home/michael# apt-get install linux-image-2.6.15-1-686
Reading package lists... Done
Building dependency tree... Done
The following extra packages will be installed:
busybox initramfs-tools klibc-utils libklibc libvolume-id0 udev
Suggested packages:
linux-doc-2.6.15 linux-source-2.6.15
Recommended packages:
libc6-i686
The following packages will be REMOVED:
hotplug
The following NEW packages will be installed:
busybox initramfs-tools klibc-utils libklibc libvolume-id0
linux-image-2.6.15-1-686 udev
0 upgraded, 7 newly installed, 1 to remove and 0 not upgraded.
Need to get 16.6MB of archives.
After unpacking 47.1MB of additional disk space will be used.
Do you want to continue [Y/n]? Y
Get:1 http://debian.yorku.ca testing/main busybox 1:1.1.3-2 [286kB]
Get:2 http://debian.yorku.ca testing/main libklibc 1.4.8-1.1 [40.9kB]
Get:3 http://debian.yorku.ca testing/main klibc-utils 1.4.8-1.1 [120kB]
Get:4

Upgrade frustrations (in testing) with shorewall crashes, clock troubles, tomcat4 crashes

2006-03-06 Thread Michael Bonert

I recently upgraded my testing distribution and got a lot of headaches.

-
SHOREWALL
Lately, the shorewall versions changed so much that I couldn't ignore
changes (in the config) anymore.  Shorewall was crashing my computer on
shutdown.  

On shutdown I was getting something like this:
-
Shorewall:net2all:DROP:IN=eth0
OUT=MAC=ff:ff:ff:ff:ff:ff:00:06:25:f0:a9:d3:08:026369 PROTO=UDP SPT=29943
DPT=152 LEN=128
-
I couldn't do anything about it.  It seemed to be stuck in a loop... where
the numbers after 'SPT=' where increasing.  

Unplugging the network cable-- stopped the loop... no more text was printed
to the screen.  That said, I never regained enough control to kill the
process or finish the shutdown and had reach for the power switch to kill
the machine 'cause there was no other way to do ANYTHING.  I could type
things in and they did display in 'tty1' but had no effect-- I didn't have a
command line.  When I switched to the other terminals tty2, tty3 etc... the
keyboard didn't seem to have any effect-- it did not register anything at
the login (I could only switch to another terminal).

I'm sure it was shorewall... 'cause if I did shorewall stop and then
shutdown I didn't have problems with shorewall.

I wish there were better defaults for the shorewall set-up.  At the moment
one gets the 'shorewall.conf' in '/etc/shorewall' -- but nothing else.  The
other config files are hidden away in 
'/usr/share/doc/shorewall/default-config' and need modification to make the
system run.

Why make this complicated?
I think installing shorewall was a big freaking headache and I was annoyed
that I had to redo it lately. 

Quite aside from the above problem, I have the impression shorewall makes me
more insecure-- as judged by Shields Up -- https://grc.com/x/ne.dll?bh0bkyd2
If I shutdown shorewall and run the sequence at Shields Up --- I get all
green.  With the config I copied from Mandrake-- I get one blue port (closed
(green) vs. hidden (blue)).

-
CLOCK TROUBLES
With the recent upgrade there is some sort of universal time eastern
standard time conflict.  My computer when I boot-up has the clock turned
back 5 hours (the difference between Greenwich and where I live --with DST
compensation).

I wish the upgrade were more intelligent... or that the questions that dealt
with this was at higher level.  I remember setting some sort of
configuration for apt-get/package configuration... when I installed Debian. 
I have the impression-- this detail about the clock got buried somewhere in
a lower level.

From my install notes I know that I didn't set the clock to GMT.  However,
it seems Debian (on start-up) now sets my clock back the time difference to
GMT.  It is as if it assumes my computer is set to GMT and it has to turn
the clock back to get eastern daylight savings time (EDT).


-
TOMCAT4
Is giving me grief on shutdown.  Like shorewall... it seems to hang the
machine on shutdown.
I suspect this a problem not many people encounter-- 'cause most people that
run a web server don't restart their machine often.  (I'm not running a web
server-- just using my machine to as a develop platform.)

I haven't figure-out all the details on this one.  I do know that if I kill
the tomcat tasks-- and then shutdown the shutdown goes smoothly.  If I don't
stop tomcat the machine hangs in shutdown.


Michael



System/Hardware

Toshiba Satellite A20 -- A20-31Q: 2.53GHz
(PSA20C-0231Q)
http://www.toshiba.ca/web/specifications.grp?lg=ensection=1group=1product=1912part=1772

Processor: Intel Pentium IV, 2.53GHz
Memory: 512 MB

Linux version 2.6.11-1-686 ([EMAIL PROTECTED]) (gcc version 3.3.6 (Debian
1:3.3.6-6)) #1 Mon Jun 20 22:00:38 MDT 2005

Distribution: Debian GNU/Linux Testing (Etch)
Desktop: KDE 3.5.1

Install details can be found here:
http://individual.utoronto.ca/bonert/debian_install.html


-- 
Bis zu 70% Ihrer Onlinekosten sparen: GMX SmartSurfer!
Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

keyboard lockup at start-up - after kde upgrade (3.4.2)

2005-11-05 Thread Michael Bonert

After upgrading KDE (to 3.4.2).  I started having the keyboard lockup
problem discussed here:
http://lists.debian.org/debian-devel/2005/07/msg01217.html

The work around I found for this annoying problem (reproduced below) does
not work.  

Complicating the situation is that one cannot easily drop to a virtual
console. The new login screen (after the upgrade) doesn't have the option to
drop to a console... and since the keyboard is locked it appears that one is
just plain screwed.  

After rebooting a couple of times and hoping I'd luck-out I realized that if
I frantically tap the keyboard (ctrl-alt-F1 after selecting re-start
X-server) I can sometimes drop to a virtual console.  From there I can kill
'kdm'... and if I re-start kdm the keyboard problem is gone (like in my past
experience).  This is a very crude work around. I'm looking for a definitive
fix for kdm.

Does anyone have a detailed set of instructions for licking the annoying
problem?

Nikita's post ( http://lists.debian.org/debian-devel/2005/07/msg01217.html )
and the follow-up by Enrico Zini (
http://lists.debian.org/debian-devel/2005/07/msg01268.html ) seem to nail
down the problem-- but they don't get me closer to fixing it 'cause I don't
know enough about where the relevant files reside.

Thanks,
Michael



=
KEYBOARD LOCK-UP BUG
=
August 27, 2005

Google
search
http://www.google.com/search?hl=enq=X%2C+keyboard+lock-upbtnG=Google+Search

Keyboard lockup after X startup; possible cause
http://lists.debian.org/debian-devel/2005/07/msg01217.html

bug seems to be avoided with use of 'gdm' ???

this site gives the specific syntax for defining the virtual console
http://lists.freedesktop.org/pipermail/xorg/2004-November/004368.html
---
startx/xinit ... - vt7
---

this talks about where to make the change in debian
http://lists.debian.org/debian-kde/2001/07/msg00238.html

MODIFY THE FILE: /etc/kde3/kdm/Xservers
the following line 
---
:0 [EMAIL PROTECTED] /usr/X11R6/bin/X -nolisten tcp
---
should become
---
:0 [EMAIL PROTECTED] /usr/X11R6/bin/X -nolisten tcp vt7
---
=
http://individual.utoronto.ca/bonert/debian_install.html


--- System Information ---
Software:
Debian Release: testing/unstable
Kernel: Linux version 2.6.11-1-686 ([EMAIL PROTECTED]) (gcc version 3.3.6
(Debian 1:3.3.6-6)) #1 Mon Jun 20 22:00:38 MDT 2005
Desktop Env.: KDE 3.4.2

Hardware:
Athlon 2200 XP
ASUS A7N8X Motherboard
ASUS V8420 - NVIDIA GeForce 4
512 MB RAM

-- 
10 GB Mailbox, 100 FreeSMS/Monat http://www.gmx.net/de/go/topmail
+++ GMX - die erste Adresse für Mail, Message, More +++


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: nvidia kernel + AMD processor = problems with sound tv tuner

2005-07-04 Thread Michael Bonert

I never figured-out the 'In-Reply-To' ... whether that can be done somehow
in web based email... where one doesn't really have fine control over the
header.  
Any case -- this is in reply to
http://lists.debian.org/debian-user/2005/03/msg00335.html

I'm starting to wonder whether it might be a kernel issue.
Nvidia modules un-installed + using the free/open driver (nv), I cannot
adjust the volume in xine with the new kernel.  When I reboot -- and use the
old 2.6.8-1-k7 kernel** it works without a problem.

The following message describes a kernel problem --
http://lists.debian.org/debian-user/2005/03/msg00335.html

I cannot help this is something similar... whereas I didn't find anything on
the xine-ui bug-report list.  The kernel-image package
http://packages.debian.org/testing/base/kernel-image-2.6.11-1-k7
doesn't have any bug reports on this either.  Any one seen this before? 
Ideas?  Could it be something else?

Thanks,
Michael


** Linux version 2.6.8-1-k7 ([EMAIL PROTECTED]) (gcc versi
on 3.3.5 (Debian 1:3.3.5-2)) #1 Thu Nov 25 04:13:37 U
TC 2004


On Sunday 03 July 2005 23:09, Michael Bonert wrote:

I had the problem that after I installed the nvidia driver I could not 
use 
xawtv   I sovled this by using the argument xawtv -noxv

peter colton

 I installed the nvidia kernel (details below) and after that and
rebooting:

 I got the nvidia splash screen (the driver seems to load), but...
 the tv tuner card doesn't work, xine sound doesn't work and totem sound
 doesn't work.  Interesting is that XMMS player sound does work.  Without
 the nvidia stuff... the tv tuner, xine and totem all work (as does xmms).

 -

 Is this an issue between k7 and i386?
 Why is the nvidia driver screwing with the sound?
 I used gcc 3.3.5 to compile the nvidia-kernel (the original kernel was
 compiled with gcc 3.3.6) -- could this be causing all the trouble?

 I found this about the k7 kernels...
 http://lists.debian.org/debian-user/2004/11/msg00022.html
 and wonder whether there is a more general issue here.

SNIPPAGE

 Hardware:
 
 Athlon 2200 XP
 ASUS A7N8X (Motherboard)
 ASUS V8420 - NVIDIA GeForce 4 (Video)
 512 MB RAM

 Software:
 
 Debian GNU/Linux - testing
 base kernel 2.6.11-k7
 KDE 3.3.2

-- 
5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail
+++ GMX - die erste Adresse für Mail, Message, More +++


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

nvidia kernel + AMD processor = problems with sound tv tuner

2005-07-03 Thread Michael Bonert

I installed the nvidia kernel (details below) and after that and rebooting:

I got the nvidia splash screen (the driver seems to load), but...
the tv tuner card doesn't work, xine sound doesn't work and totem sound
doesn't work.  Interesting is that XMMS player sound does work.  Without the
nvidia stuff... the tv tuner, xine and totem all work (as does xmms).

-

Is this an issue between k7 and i386?
Why is the nvidia driver screwing with the sound?
I used gcc 3.3.5 to compile the nvidia-kernel (the original kernel was
compiled with gcc 3.3.6) -- could this be causing all the trouble?

I found this about the k7 kernels...
http://lists.debian.org/debian-user/2004/11/msg00022.html 
and wonder whether there is a more general issue here.


Details of the install
=
July 3, 2005
# apt-get install nvidia-settings

# apt-get install nvidia-kernel-common
# apt-get install nvidia-kernel-source 
PLEASE read /usr/share/doc/nvidia-kernel-source/README.Debian for building
information.

$ cd /usr/src
# su
# tar xzvf nvidia-kernel-source.tar.gz

# more /proc/version
Linux version 2.6.11-1-k7 ([EMAIL PROTECTED]) (gcc version 3.3.6 (Debian
1:3.3.6-5)) #1 Fri May 20 06:54:58 UTC 2005

# uname -r
2.6.11-1-k7
  
# export KSRC=/usr/src/kernel-headers-2.6.11-1-k7
# export KVERS=2.6.11-1-k7

# cd modules/nvidia-kernel

SNIP
dpkg-deb: building package `nvidia-kernel-2.6.11-1-k7' in
`/usr/src/modules/nvidia-kernel/../nvidia-kernel-2.6.11-1-k7_1.0.7174-3_i386.deb'.

# cd ..
# pwd
/usr/src/modules

# dpkg -i nvidia-kernel-2.6.11-1-k7_1.0.7174-3_i386.deb 

# apt-get install nvidia-glx
file:/usr/share/doc/nvidia-glx/README.gz

as per /usr/share/doc/nvidia-glx/README.Debian
# vi /etc/X11/XF86Config-4
make sure it is there - Load glx
remove -Load dri
remove -Load GLcore
change -'Driver nv' to 'Driver nvidia'

RESTART X -- appears to work...
reboot... more testing -- then above problems.




Hardware:

Athlon 2200 XP
ASUS A7N8X (Motherboard)
ASUS V8420 - NVIDIA GeForce 4 (Video)
512 MB RAM

Software:

Debian GNU/Linux - testing
base kernel 2.6.11-k7
KDE 3.3.2

-- 
Weitersagen: GMX DSL-Flatrates mit Tempo-Garantie!
Ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: broken nvidia package, is there a work around?

2004-06-29 Thread Michael Bonert

Nvidia's proprietary driver for some reason just doesn't want to play
nice.

I managed to get it installed -- with the advice given :-) in response
to http://lists.debian.org/debian-user/2004/06/msg03819.html -- but it 
only works sort of.  I get the nvidia splash screen and the display 
seems to be fine... KDE loads as I think it should.  However, a whole 
bunch of applications don't work.

The TV Tuner is busted.  I get a blue screen when I run 'xawtv' -- 
which according to this -- http://www.charmed.com/support9.htm -- 
it means the driver is loaded (and the tuner card was detected).

Then, when running Mozilla I managed to get the error message:  
libmikmod.so.2 is not a registered protocol

I then noticed XMMS doesn't work.  When I try to start it at the command
line I get this:
-
$ xmms
libmikmod.so.2: cannot open shared object file: No such file or directory
Inconsistency detected by ld.so: ../sysdeps/generic/dl-tls.c: 72:
_dl_next_tls_modid: Assertion `result = _rtld_local._dl_tls_max_dtv_idx'
failed!
-

After some more searching I found this post:
http://lists.debian.org/debian-glibc/2003/11/msg00444.html  
It says: ...this bug is almost certainly related to the nvidia-glx
drivers...

I didn't find anything that jumped out at me in '/var/log/XFree86.0.log'

This post suggests it is related to 'libGLcore.so':
http://lists.debian.org/debian-glibc/2003/11/msg00448.html

-
The above seems to suggest problems with the glx drivers.
Has any one encountered a problem like this before?

Does it matter that I'm running the '2.6.6-1-386' kernel (on an Athlon 2200
XP processor)?
Could this be a bug in the proprietary driver?




PACKAGES INSTALLED --- SNIPPAGE OF DESCRIPTION 

$ COLUMNS=132 dpkg --list |grep kernel
ii  adjtimex1.16-1 
ii  initrd-tools0.1.70
ii  iproute 20010824-13.1   
ii  iptables1.2.9-9
ii  kcmlinuz3.2.2-1
ii  kernel-headers-2.6.6-1  2.6.6-1   
ii  kernel-headers-2.6.6-1-386  2.6.6-1
ii  kernel-image-2.6.6-1-3862.6.6-1  
ii  kernel-kbuild-2.6-3 2.6.6-1
ii  kernel-package  8.090 
ii  libdirectfb-0.9-20  0.9.20-1
ii  module-init-tools   3.0-pre10-4
ii  nvidia-kernel-2.6.6-1-386   1.0.5336-6
ii  nvidia-kernel-common1.0.5336-1
ii  nvidia-kernel-source1.0.5336-6 
ii  pciutils2.1.11-11 

$ COLUMNS=132 dpkg --list |grep nvidia
ii  nvidia-glx  1.0.5336-6 
ii  nvidia-kernel-2.6.6-1-386   1.0.5336-6   
ii  nvidia-kernel-common1.0.5336-1 
ii  nvidia-kernel-source1.0.5336-6 
[EMAIL PROTECTED]:~$



Hardware/Software

Athlon 2200 XP
ASUS A7N8X (Motherboard)
ASUS V8420 - NVIDIA GeForce 4 
Viewsonic PF790
512 MB RAM

Debian Sarge
2.6.6-1-386 Kernel
KDE 3.2.2

-- 
+++ Jetzt WLAN-Router für alle DSL-Einsteiger und Wechsler +++
GMX DSL-Powertarife zudem 3 Monate gratis* http://www.gmx.net/dsl


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

broken nvidia package, is there a work around?

2004-06-25 Thread Michael Bonert

I'm running Sarge and I just tried installing nvidia's proprietary
drivers.  Bottom line is it didn't work and I'm 97% sure it is
messed packages.  

I worked through the instructions in nvidia-kernel-source
and then get to a place where I have a deb package I built
from the (kernel) headers--but it doesn't install 'cause of 
a dependency:
-
# dpkg -i nvidia-kernel-2.6.6-1-386_1.0.5336-6_i386.deb
Selecting previously deselected package nvidia-kernel-2.6.6-1-386.
(Reading database ... 68446 files and directories currently installed.)
Unpacking nvidia-kernel-2.6.6-1-386 (from
nvidia-kernel-2.6.6-1-386_1.0.5336-6_i386.deb) ...
dpkg: dependency problems prevent configuration of
nvidia-kernel-2.6.6-1-386:
 nvidia-kernel-2.6.6-1-386 depends on nvidia-kernel-common (=
1.0.5336); however:
  Package nvidia-kernel-common is not installed.
dpkg: error processing nvidia-kernel-2.6.6-1-386 (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 nvidia-kernel-2.6.6-1-386
-
 
# apt-get install nvidia-kernel-common
Reading Package Lists... Done
Building Dependency Tree... Done
Package nvidia-kernel-common is not available, but is referred to by
another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package nvidia-kernel-common has no installation candidate

-


I've found the installation process with the proprietary nvidia/debian 
stuff frustrating.

What is the point of using it any away-- as opposed to installing the
tar ball from nvidia's site?

I hope someone out there can enlighten me.

Thanks,
Michael



Hardware/Software

Athlon 2200 XP
ASUS A7N8X (Motherboard)
ASUS V8420 - NVIDIA GeForce 4 
Viewsonic PF790
512 MB RAM

Debian Sarge
2.6.6-1-386 Kernel
KDE 3.2.2




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

2.6 kernel install, lilo problems in sarge (?)

2004-04-04 Thread Michael Bonert

I'm having some probs with lilo:


# dpkg -i kernel-image-2.6.4_cobalamin.1.0_i386.deb# install of a custom kernel
===
{SNIP}
You already have a LILO configuration in /etc/lilo.conf
Install a boot block using the existing /etc/lilo.conf? [Yes] yes
Testing lilo.conf ...
An error occurred while running lilo in test mode, a log is
available in /var/log/lilo_log.15223. Please edit /etc/lilo.conf
manually and re-run lilo, or make other arrangements to boot
your machine.
 Please hit return to continue

cobalamin:/usr/local/src#
==

cobalamin:/var/log# more lilo_log.15223
Warning: '/proc/partitions' does not match '/dev' directory structure.
Name change: '/dev/ide/host0/bus0/target0/lun0/disc' - '/dev/hda'
Fatal: open /initrd.img: No such file or directory
cobalamin:/var/log#
===

After searching the web I found this:
http://linux.derkeiler.com/Mailing-Lists/Debian/2003-07/0122.html

and this:
http://lists.debian.org/debian-user/2003/debian-user-200312/msg06152.html

Both touch on the subject... neither really clarify it for me.

I'm running testing (sarge) on a Toshiba A20... and trying to install
a build of the 2.6.4 kernel.

-
I mucked around with the 'devfs' option in menuconfig--compiled with 
compiled without.

I don't understand why it doesn't work.  I've compiled and installed
a couple of 2.6 series kernels on a Debian 'Sid' system in the past
without any problems.

QUESTIONS:
Does lilo (in the testing distribution) require (the obsolete) devfs?
Do I need to #apt-get install devfsd ???


Any help would be much appreciated...
Michael


==
OUTLINE OF MY KERNEL COMPILE / INSTALLATION

# apt-get install libstdc++5-3.3-dev
# apt-get install libncurses5-dev

# apt-get install kernel-package fakeroot
# apt-get install kernel-source-2.6.4

# apt-get install module-init-tools # THIS SHOULD GET RID OF THOSE
'/depmod' MESSAGES

# apt-get install gcc
# apt-get install g++-2.95

# cd /usr/src
# bzip2 -d kernel-source-2.6.4.tar.bz2


$ cd /usr/local/src
# su
# chmod o=rwx .
$ tar xf /usr/src/kernel-source-2.6.4.tar

ZIP UP THE PACKAGE AGAIN (now that we've got a copy in /usr/local/src)
# cd /usr/src
# bzip2 kernel-source-2.6.4.tar

$ cd /usr/local/src/kernel-source-2.6.4
$ vi Makefile
CHANGED
--- 
HOSTCC  = gcc
HOSTCXX = g++

SNIP

CC  = $(CROSS_COMPILE)gcc
--- 

TO
--- 
HOSTCC  = gcc-2.95
HOSTCXX = g++-2.95

SNIP

CC  = $(CROSS_COMPILE)gcc-2.95
--- 

(Linus says to use gcc 2.95.3)

$ make menuconfig # edit some stuff here
$ make-kpkg clean
$ script -a cobalamin.1.0-compile-log.txt
$ fakeroot make-kpkg --revision=cobalamin.1.0 kernel_image

$ cd /usr/local/src
$ su
# dpkg -i kernel-image-2.6.4_cobalamin.1.0_i386.deb # installing 2.6.4


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

files corrupt (?) -- ldconfig problems

2004-03-06 Thread Michael Bonert

At what point is a system beyond repair... or not worth repairing?

PROLOG
---
I had some problems installing debhelper and the result is
I had disk errors--which I managed to fix with fsck.reiserfs

I then managed to regenerate /var/lib/dpkg/available
(which fixed an earlier problem --
http://lists.debian.org/debian-user/2004/debian-user-200403/msg00184.html)
---

WHERE I'M STUCK
-
I have persisting ldconfig problems... and I don't have a good idea of how
to fix them.  It seems some libraries and config files were messed (on the
debhelper install) and they need to be re-installed.  I can't get into any
of the two windowing systems (Gnome or KDE)...  so I have to use the
command line exclusively and have to reboot every time I want to search
the web--frustrating.

I renamed /etc/ld.so.cache and found it was re-created when I
rebooted... and thus concluded the problem isn't with 'ldconfig' per se--
but likely related to the libraries it links (libc6 ?).

Is there a way to regenerate the library files automatically... without
having to hunt down the packages they are in?
In other words... can one refresh all the files associated with ldconfig?
(I remember reading about how RPMs systems allow one to check whether the
files in an RPM package are all there... and that one can replace broken
files.)


I had the impression the following line in /etc/apt.conf
-
APT::Get::ReInstall;
-
would make packages I apt-get install that are already installed
re-install... but it doesn't seem to be so ('cause it didn't help).


After reading a bit here... (
http://www.die.net/doc/linux/man/man8/ldconfig.8.html )
I thought the fix might be re-installing libc6 -- so I was going to do
'apt-get remove libc6' then apt-get install ...but a message I got when
doing the remove command convinced me it isn't so wise and I don't really
know what I'm doing...

Help would be much appreciated...

Thanks,
Michael



LDCONFIG COMPLAINING...

stokes:/home/michael# ldconfig
ldconfig: /usr/lib/libkdegames.so.1 is not an ELF file - it has the wrong
magic bytes at the start.

ldconfig: /usr/lib/libkdegames.so.1.1.0 is not an ELF file - it has the
wrong magic bytes at the start.

ldconfig: /usr/lib/libartsgui.so.0 is not an ELF file - it has the wrong
magic bytes at the start.

ldconfig: /usr/lib/libatlantikui.so.1.1.0 is not an ELF file - it has the
wrong magic bytes at the start.

ldconfig: /usr/lib/libartsmidi_idl.so.0.0.0 is not an ELF file - it has
the wrong magic bytes at the start.

ldconfig: /usr/lib/libartsgui_idl.so.0.0.0 is not an ELF file - it has the
wrong magic bytes at the start.

ldconfig: /usr/lib/libartsmidi_idl.so.0 is not an ELF file - it has the
wrong magic bytes at the start.

ldconfig: /usr/lib/libartsgui.so.0.0.0 is not an ELF file - it has the
wrong magic bytes at the start.

ldconfig: /usr/lib/libartsbuilder.so.0.0.0 is not an ELF file - it has the
wrong magic bytes at the start.

ldconfig: file /usr/lib/libapt-inst-libc6.3-5.so.1.0 is truncated

ldconfig: file /usr/lib/libfam.so.0.0.0 is truncated

ldconfig: /usr/lib/libartsmodules.so.0 is not an ELF file - it has the
wrong magic bytes at the start.

ldconfig: /usr/lib/libartsmodules.so.0.0.0 is not an ELF file - it has the
wrong magic bytes at the start.

ldconfig: file /usr/lib/libapt-inst-libc6.3-5.so.1.0.0 is truncated

ldconfig: /usr/lib/libartsgui_idl.so.0 is not an ELF file - it has the
wrong magic bytes at the start.

ldconfig: /usr/lib/libartsgui_kde.so.0 is not an ELF file - it has the
wrong magic bytes at the start.

ldconfig: /usr/lib/libartsgui_kde.so.0.0.0 is not an ELF file - it has the
wrong magic bytes at the start.

ldconfig: /usr/lib/libartsmidi.so.0 is not an ELF file - it has the wrong
magic bytes at the start.

ldconfig: /usr/lib/libartsbuilder.so.0 is not an ELF file - it has the
wrong magic bytes at the start.

ldconfig: /usr/lib/libasound.so.2 is not an ELF file - it has the wrong
magic bytes at the start.

ldconfig: /usr/lib/libxine.so.1.8.1 is not an ELF file - it has the wrong
magic bytes at the start.

ldconfig: /usr/lib/libatlantikclient.so.1.1.0 is not an ELF file - it has
the wrong magic bytes at the start.

ldconfig: file /usr/lib/libfam.so.0 is truncated

ldconfig: /usr/lib/libartsmidi.so.0.0.0 is not an ELF file - it has the
wrong magic bytes at the start.

ldconfig: /usr/lib/libasound.so.2.0.0 is not an ELF file - it has the
wrong magic bytes at the start.

ldconfig: /usr/lib/libatlantikclient.so.1 is not an ELF file - it has the
wrong magic bytes at the start.

ldconfig: /usr/lib/libxine.so.1 is not an ELF file - it has the wrong
magic bytes at the start.

ldconfig: /usr/lib/libatlantikui.so.1 is not an ELF file - it has the
wrong magic bytes at the start.

stokes:/home/michael#


ANOTHER PROBLEM - RELATED I THINK

# apt-get install apt-utils
...

The following

corrupt dpkg + kernel panic --HELP!

2004-03-01 Thread Michael Bonert

My computer locked-up during the install of debhelper as a part of an
update.

On reboot I couldn't get into the only graphical UI I have installed
-- KDE crashes.  Working with the command line I figured out debhelper has
a problem... and tried removing it:

TRYING TO REMOVE DEBHELPER:
-
stokes:/var/cache/apt/archives# dpkg --remove debhelper
dpkg: error processing debhelper (--remove):
 Package is in a very bad inconsistent state - you should
 reinstall it before attempting a removal.
Errors were encountered while processing:
 debhelper
stokes:/var/cache/apt/archives# dpkg --install debhelper_4.2.4_all.deb


RESULT: kernel panic + full lock-up.
-


dpkg LOOKS CORRUPT:
-
stokes:/var/cache/apt/archives# dpkg --list
dpkg-query: parse error, in file `/var/lib/dpkg/available' near line 1:
 newline in field name `125c81'
stokes:/var/cache/apt/archives#
-


I found this in the archive:
---
 ... you've certainly broken /var/lib/dpkg/available
somehow. Fortunately, this is entirely recoverable: 'dselect update'
should fix it.
---
http://www.mail-archive.com/[EMAIL PROTECTED]/msg80966.html

Looked good... but didn't help.


Any one have an idea about how to fix my dpkg problem?
Is there something I'm missing?  


Thanks,
Michael


---

I hope I don't have to manually clean-up the raging dependency problems...
==

stokes:/home/michael/documents/debian_linux# apt-get update

0% [Working]

{SNIP}

84% [Waiting for headers]

Hit http://non-us.debian.org unstable/non-US/non-free Sources
Hit http://non-us.debian.org unstable/non-US/non-free Release

94% [Working]

E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to
correct the problem.
stokes:/home/michael/documents/debian_linux# dpkg --configure -a
Setting up cvs (1.12.5-2) ...

gzip: stdin: not in gzip format
install-info(/usr/share/info/cvsclient.info): read gzip -cd
/usr/share/info/cvsclient.info.gz |: 256
dpkg: error processing cvs (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of fontconfig:
 fontconfig depends on ucf (= 0.29); however:
  Version of ucf on system is 0.26.
dpkg: error processing fontconfig (--configure):
 dependency problems - leaving unconfigured
Setting up gettext (0.14.1-1) ...

gzip: stdin: not in gzip format
install-info(/usr/share/info/gettext.info): read gzip -cd
/usr/share/info/gettext.info.gz |: 256
dpkg: error processing gettext (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of libfontconfig1:
 libfontconfig1 depends on fontconfig; however:
  Package fontconfig is not configured yet.
dpkg: error processing libfontconfig1 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of intltool-debian:
 intltool-debian depends on gettext; however:
  Package gettext is not configured yet.
dpkg: error processing intltool-debian (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of atlantik:
 atlantik depends on libfontconfig1 (= 2.2.1); however:
  Package libfontconfig1 is not configured yet.
dpkg: error processing atlantik (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of amor:
 amor depends on libfontconfig1 (= 2.2.1); however:
  Package libfontconfig1 is not configured yet.
dpkg: error processing amor (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of ark:
 ark depends on libfontconfig1 (= 2.2.1); however:
  Package libfontconfig1 is not configured yet.
dpkg: error processing ark (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libxft1:
 libxft1 depends on libfontconfig1 (= 2.2.1); however:
  Package libfontconfig1 is not configured yet.
dpkg: error processing libxft1 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of artsbuilder:
 artsbuilder depends on libfontconfig1 (= 2.2.1); however:
  Package libfontconfig1 is not configured yet.
dpkg: error processing artsbuilder (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of po-debconf:
 po-debconf depends on gettext; however:
  Package gettext is not configured yet.
 po-debconf depends on intltool-debian (= 0.27.2+20031023); however:
  Package intltool-debian is not configured yet.
dpkg: error processing po-debconf (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libkdegames1:
 libkdegames1 depends on libfontconfig1 (= 2.2.1); however:
  Package libfontconfig1 is not configured yet.
dpkg: error processing libkdegames1 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency

gcc the kernel, supermount (?)

2004-02-02 Thread Michael Bonert

I have a couple of newbie-ish questions.

(1) How does one set the compiler when compiling the (linux) kernel?

I had the impression it was just a few settings in 'Makefile' and that it
just entails changing the following:

--- (Makefile)
HOSTCC  = gcc
HOSTCXX = g++
---

to
---
HOSTCC  = gcc-2.95
HOSTCXX = g++-2.95
---

Beyond that I tried aliasing--both didn't do anything (it compiled 
with gcc 3.3.3).  About the only thing I didn't do was remove the more
recent version of gcc.

ASIDE - What sort of problems arise if one compiles the kernel with gcc
(3.3.3) versus gcc-2.95 (the one Linus recommends)?

Seems as if fakeroot (what I use to compile) does something funny...

---
(2) Is there a supermount patch for the 2.6 series kernel?
(I noticed there is a patch for the 2.4 kernel series.)

If I haven't missed it... are there plans to put it into 
the debian patches (for the kernel-source-2.6.0 package)?

(Call me Micro$oft corrupted... but it seems like a useful feature and I
can't help think mounting CDs and floppys is pretty silly if the computer
can doing it automagically.)

Thanks,
Michael


-- System Information --
Software:
Debian Release: 'Sid'
Kernel: Linux version 2.6.0 ([EMAIL PROTECTED]) (gcc version 3.3.3 20031229
(prerelease) (Debian)) #1 Sun Feb 1 00:34:27 EST 2004
Desktop Env.: KDE 3.1.2

Hardware:
Athlon 2200 XP
ASUS A7N8X Motherboard
ASUS V8420 - NVIDIA GeForce 4
512 MB RAM


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Openoffice.org font problem + strange dependency (?)

2004-01-03 Thread Michael Bonert

I'm having a little problem with fonts in Openoffice.

The menu across the top says:
(F), (E), (V), (I), (O), (T), (W), (H)

Instead of:
File, Edit, View, Insert, Format, Tools, Window, Help

All the submenus are likewise effected.


I'm not sure if that is a good description.  Any case, a picture is worth
a thousand words.  Take a look at a snapshot of the mess:
http://individual.utoronto.ca/bonert/ooo_fonts_kaputt.png


How did I manage this master-piece?

It took me just one command:
# apt-get install kde

After that OOo (OpenOffice.org) was screwed.
Why?  I don't know.

Theories.
---
1. OOo is at fault
The openoffice.org upgrade got screwed.

2. kde is at fault -- (seems like a long shot)
It has something to do with the fact that I installed kde-base and a few
other components first (since the package 'kde' had been broken... for a
few months).
---

What I tried:
1.
$ mv .openoffice .openoffice.old

$ openoffice# restart OOo
It then complains that .sversionrc points to
file:///home/michael/.openoffice/1.0.2 so...
$ mv .sversionrc .sversionrc.old

$ openoffice# restart OOo
result: problem still not solved.

2. -- maybe my kde config is a bit different than the usual.
$ mv .kde .kde.old
logout
log back in (kde -- will regenerate .kde using defaults)

result: nothing

-
I then looked at some of the package info:

stokes:/home/michael# COLUMNS=132 dpkg --list |grep openoffice
ii  openoffice.org  1.1.0-3high-quality office productivity suite
ii  openoffice.org-bin  1.1.0-3OpenOffice.org office suite binary files
ii  openoffice.org-debian-files 1.1.0-3+1  Debian specific parts of OpenOffice.org
ii  openoffice.org-help-en  1.1+20030814-3 OpenOffice.org office suite help 
(English)
rc  openoffice.org-l10n-en  1.1.0-1English (US) language package for 
openoffice.org
ii  openoffice.org-l10n-zh-tw   1.1.0-3Chinese Traditional language package 
for openoffice.org

Any one see a problem here?  I don't.

However, I didn't like the fact that 'openoffice.org-l10n-zh-tw' was
installed; I didn't remember installing it and, also, don't have any use
for it.  

I tried to remove it:
-
stokes:/home/michael# apt-get remove openoffice.org-l10n-zh-tw
Reading Package Lists... Done
Building Dependency Tree... Done
The following packages will be REMOVED:
  oooqs-kde openoffice.org openoffice.org-bin openoffice.org-debian-files
openoffice.org-help-en
  openoffice.org-l10n-zh-tw
0 upgraded, 0 newly installed, 6 to remove and 2 not upgraded.
Need to get 0B of archives.
After unpacking 202MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
-
What strikes me as strange is that basically all the openoffice files
depend on it.  Am I the only one that thinks this
(openoffice.org-l10n-zh-tw) dependency is strange?

--
ASIDE - the two packages not upgraded are 'kdebase' and 'kcontrol'
(kcontrol has given me problems -- I had to go back to an older deb I had
lying around in /var/cache/apt/archives/ --  kdebase was complaining about
a dependency problem with kcontrol)
--

Any help would be much appreciated.




-- System Information --
Software:
Debian Release: testing/unstable
Kernel: Linux version 2.6.0-test7 ([EMAIL PROTECTED]) (gcc version 3.3.2 (Debian)) #1 
Mon Oct 27 21:34:51 EST 2003
Desktop Env.: KDE 3.1.1

Hardware:
Athlon 2200 XP
ASUS A7N8X Motherboard
ASUS V8420 - NVIDIA GeForce 4
512 MB RAM


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

update-modules, sound on boot-up

2003-10-22 Thread Michael Bonert

I have a frustrating little problem with sound on boot-up.

Sound works if I manually load the required sound module:
-
$ su
# modprobe emu10k1

Result: Get great sound. :)

Then I try to make it permanent:
-
# update-modules
-

Then a re-boot to test...

Result: To my surprise on login there is this message:
-
Sound server informational message:  Error while initializing the sound
driver device /dev/dsp can't be opened (Permission denied)  The sound
server will continue, using the null output device
-

I don't think the device is the problem:
-
# ls -lat /dev/dsp
crw-rw-rw-1 root audio 14,   3 Mar 14  2002 /dev/dsp
-

I then decided to look in /etc/modules.conf:
-
--SNIP--
### update-modules: start processing /etc/modutils/sndconfig
alias sound-slot-0 emu10k1
post-install sound-slot-0 /bin/aumix -f /etc/.aumixrc -L /dev/null 21 || :
pre-remove sound-slot-0 /bin/aumix -f /etc/.aumixrc -S /dev/null 21 || :

### update-modules: end processing /etc/modutils/sndconfig
--SNIP--
-

I don't understand what 'sndconfig' is up to.  I ran it when I was
installing the kernel (2.6.0-test6) and it didn't do anything for me; it
said that it couldn't find soundcore.o and suggested I was using an old
kernel ...yeah riiight!

So, 'sndconfig' seemed suspect... the little util that had once helped me
config sound seemed was now getting in the way... ergo:
-
# apt-get remove sndconfig
-

I then tried deleting the bit with 'sndconfig'... and did another
'update-modules' that didn't seem to change anything.  The above tid-bit
in /etc/modules.conf was regenerated which doesn't seem to be
progress... and something bothers me.


I then took a look at the boot log:
# dmesg
-
--SNIP--
Serial: 8250/16550 driver $Revision: 1.90 $ IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Creative EMU10K1 PCI Audio Driver, version 0.20a, 15:00:13 Oct 12 2003
emu10k1: EMU10K1 rev 7 model 0x8061 found, IO at 0xd400-0xd41f, IRQ 16
ac97_codec: AC97 Audio codec, id: 0x8384:0x7608 (SigmaTel STAC9708)
emu10k1: SBLive! 5.1 card detected
#
-
I don't see anything pointing to a problem there.  The computer seems to
know the sound card is there and even talks about the module
(emu10k1) needed to make it work.
I don't get it.


The only other thing I was looking at was /etc/group... 
I tried changing:
---
audio:x:29:
--- 
TO 
---
audio:x:29:1000:
---
Where '1000' is the id of my normal user.


Any tips would be much appreciated.

Thanks,
Michael

PS - Yep... 'emu10k1' is the old sound arch.  I didn't have any luck with
ALSA (advanced linux sound arch).  The only thing I mananged to get it to
do is make my center speaker buzz... and that to me smelled like an issue
with the module; I had something like that once before.

OS/Software:
Debian Sid
2.6.0-test6 kernel (with Debian patches)
KDE 3.1.3

System:
Athlon XP 2200
512 MB RAM
NVIDIA GeForce 4
ASUS A7N8X Motherboard
SoundBlaster Live 5.1


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

A Selection of XMMS Skins?

2003-10-12 Thread Michael Bonert

Is there an apt package of XMMS Skins?  I'm getting sick of the default
one.

I searched with 'apt-cache search xmms', that, however, didn't find
anything.  I then tried googling--that just found me RPMS--yuck!  The
archive (here) doesn't seem to have anything on this either...

Does one have to individually download 'em, if one isn't into disecting
some RPM?

Michael


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Really Stuck (nvidia drivers, X11 problem ???)

2003-08-21 Thread Michael Bonert

I am really stuck on the nvidia drivers install and am starting to wonder
whether I need a kernel upgrade (which I don't know how to do).

I think the nvidia driver I built is choking.
When I 'startx' I get a blank screen.  The last thing I see in 'XFree86.0.log' is:
-
(--) NVIDIA(0): VideoBIOS: 04.25.00.30.00
-
(full log at end)


If I run 'X' as root (which as I understand it is somewhat similar to 'startx'):
I get the following:
-
Script started on Wed Aug 20 23:14:27 2003
stokes:/home/michael# X

This is a pre-release version of XFree86, and is not supported in any
way.  Bugs may be reported to [EMAIL PROTECTED] and patches submitted
to [EMAIL PROTECTED]  Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs)

XFree86 Version 4.2.1.1 (Debian 4.2.1-9 20030630175526 [EMAIL PROTECTED]) / X Window 
System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 18 October 2002
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems.  (See http://www.XFree86.Org/)
Build Operating System: Linux 2.4.21-rc1-ac1-cryptoloop i686 [ELF]
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/XFree86.0.log, Time: Wed Aug 20 23:14:31 2003
(==) Using config file: /etc/X11/XF86Config-4
Segmentation fault

stokes:/home/michael# exit
Script done on Wed Aug 20 23:19:53 2003
-

Does it matter that X was compiled with the 2.4.21 kernel?
Does it matter that X was compiled for the i686 arch?

I'm currently using the out-of-the-box 2.4.18
---
$ /proc/version
Linux version 2.4.18-bf2.4 ([EMAIL PROTECTED]) (gcc version 2.95.4 20011002 (Debian 
prerelease)) #1 Son Apr 14 09:53:28 CEST 2002
---


I've checked whether the module is loading, made the required changes to the 
XF86Config-4
and have satisfied the required dependencies.

The build of 'nvidia-kernel-_1.0.4496-2_i386.deb' seems to be okay.  I have attached 
the output from the build process (it doesn't appear there are any errors and I don't 
see any warnings).

More background (in previous posts) is here:
http://lists.debian.org/debian-user/2003/debian-user-200308/msg02315.html
http://lists.debian.org/debian-user/2003/debian-user-200308/msg02801.html
http://lists.debian.org/debian-user/2003/debian-user-200308/msg03273.html


===
XFree86.0.log
===
This is a pre-release version of XFree86, and is not supported in any
way.  Bugs may be reported to [EMAIL PROTECTED] and patches submitted
to [EMAIL PROTECTED]  Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs)

XFree86 Version 4.2.1.1 (Debian 4.2.1-9 20030630175526 [EMAIL PROTECTED]) / X Window 
System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 18 October 2002
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems.  (See http://www.XFree86.Org/)
Build Operating System: Linux 2.4.21-rc1-ac1-cryptoloop i686 [ELF]
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/XFree86.0.log, Time: Wed Aug 20 23:08:34 2003
(==) Using config file: /etc/X11/XF86Config-4
(==) ServerLayout Default Layout
(**) |--Screen Default Screen (0)
(**) |   |--Monitor Generic Monitor
(**) |   |--Device NVIDIA GeForce 4
(**) |--Input Device Generic Keyboard
(**) Option XkbRules xfree86
(**) XKB: rules: xfree86
(**) Option XkbModel pc104
(**) XKB: model: pc104
(**) Option XkbLayout us
(**) XKB: layout: us
(==) Keyboard: CustomKeycode disabled
(**) |--Input Device Configured Mouse
(**) |--Input Device Generic Mouse
(WW) The directory /usr/lib/X11/fonts/CID does not exist.
Entry deleted from font path.
(WW) The directory /usr/lib/X11/fonts/cyrillic does not exist.
Entry deleted from font path.
(**) FontPath set to 
unix/:7100,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi
(==) RgbPath set to /usr/X11R6/lib/X11/rgb
(==) ModulePath set to /usr/X11R6/lib/modules
(--) using VT number 7

(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.1
XFree86 Video Driver: 0.5
XFree86 XInput driver : 0.3
XFree86 Server Extension : 0.1
XFree86 Font Renderer : 0.3
(II) Loader running on linux
(II) LoadModule: bitmap
(II) Loading

Re: How to upgrade kernel and another question about nvidia driver

2003-08-19 Thread Michael Bonert

Hi Hooman:

I'm currently working on installing the nvidia driver.

I haven't tried it, but it seems that the old way 
(nvidia-kernel-src) is the better way to go.  

---
I've just had trouble with nvidia-kernel-source, which is 
the newer package on the block.

If you want to try the newer package you might want 
to browse through my thread.  It starts with this message:
http://lists.debian.org/debian-user/2003/debian-user-200308/msg02315.html


The following post has the 'nvidia driver' bit from the install log I'm writing:
http://lists.debian.org/debian-user/2003/debian-user-200308/msg03083.html

It lists all the things I did line-for-line and might give you an idea
of what is required (or what not to do).  If you want to compare notes 
send me an email, perhaps we can trade install logs. :)


Michael


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

NVIDIA driver (nvidia-kernel-source)

2003-08-18 Thread Michael Bonert

 I can see a nvidia module in /lib/modules:
 /lib/modules/2.4.18-bf2.4/kernel/drivers/video/nvidia.o

That's the kernel module, you also need the glx driver.
What does dpkg -l nvidia-glx return?

It wasn't installed.  I installed it, but it doesn't work yet.
Annoying is it appears that I'm pretty close now; the 'nvidia'
module isn't unused anymore (when I check it out with 'lsmod')
and XFree86.0.log doesn't give me any errors.  When I 'startx'
I get a blank screen with a square cursor at the top left.

-
Newbie Question:
Why wasn't the nvidia-glx package installed when I grabbed 'nvidia-kernel-source'?

I thought that the whole idea of 'apt-get' was to avoid having to think about 
dependencies and thus avoid the dependency-frustration that is a characteristic of 
RPM-based GNU/Linux distros.

I can't help think this is bug, but don't see a bug report on it.  Is it a bug?
-


Is it possible that 'nvidia-glx' has to be installed before 'nvidia-kernel-source'
or... does it have to be installed before the interface to the driver is installed
(with dpkg -i nvidia-kernel-2.4.18-bf2.4_1.0.4496-2_i386.deb)?

I have to try some more things and do more thinking.

In the mean time I figured I'd post the relevant section of my install log.  I can't 
help wonder if I'm missing something stupid...
==
BINARY NVIDIA DRIVER
http://packages.debian.org/unstable/x11/nvidia-kernel-source.html
# apt-get install debhelper
# apt-get install nvidia-kernel-source

# uname -r  # returns kernel version
# apt-cache search kernel-headers   # check to see if header is there
# apt-get install kernel-headers-2.4.18-bf2.4   # get kernel headers

# cd /usr/src
# mkdir local
# tar zxvf nvidia-kernel-source.tar.gz -C /usr/src/local/   # unpack kernel src
NOTE1 - It would be better to unpack into '/usr/local/src'
ie. # tar zxvf nvidia-kernel-source.tar.gz -C /usr/local/src

# export KSRC=/usr/src/kernel-headers-2.4.18-bf2.4
# export KVERS=2.4.18-bf2.4

# cd /usr/src/local/modules/nvidia-kernel   # see NOTE1

# cat /proc/version # get compiler, release and version info
2.4.18-bf2.4 kernel compiled w/ gcc-2.95

# apt-get install gcc-2.95
The following NEW packages will be installed:
  gcc gcc-2.95 gcc-3.3

in '/usr/src/local/modules/nvidia-kernel'
# debian/rules binary_modules   # watch it compile :)

# adduser michael video

# cd /usr/src/local/modules

# apt-get install nvidia-kernel-common  # package required to avoid 'dpkg' 
having a fit
# dpkg -i nvidia-kernel-2.4.18-bf2.4_1.0.4496-2_i386.deb
---
(Reading database ... 31072 files and directories currently installed.)
Preparing to replace nvidia-kernel-2.4.18-bf2.4 1.0.4496-2 (using 
nvidia-kernel-2.4.18-bf2.4_1.0.4496-2_i386.deb) ...
Unpacking replacement nvidia-kernel-2.4.18-bf2.4 ...
Setting up nvidia-kernel-2.4.18-bf2.4 (1.0.4496-2) ...
---

# apt-get install nvidia-glx# get (nvidia) binary driver

MODIFY '/etc/X11/XF86Config-4':
---
--SNIP--
Section Module
#   Load   GLcore # REMOVED nvidia
Load   bitmap
Load   dbe
Load   ddc
#   Load   dri# REMOVED nvidia

--SECTION REMOVED--

Section Device
Identifier NVIDIA GeForce 4
Driver nvidia
#   Identifier  Generic Video Card
#   Driver  nv
EndSection

--SECTION REMOVED--

Section Screen
Identifier  Default Screen
#   Device  Generic Video Card
Device  NVIDIA GeForce 4
Monitor Generic Monitor
--SNIP--
---


-- System Information
Software:
Debian Release: testing/unstable
Kernel: Linux 2.4.18-bf2.4 ([EMAIL PROTECTED]) (gcc version 2.95.4 20011002
 (Debian prerelease)) #1 Son Apr 14 09:53:28 CEST 2002

Hardware:
Athlon 2200 XP
ASUS A7N8X Motherboard
NVIDIA GeForce 4
512 MB RAM


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

NVIDIA driver (nvidia-kernel-source) :-(

2003-08-18 Thread Michael Bonert

Sridhar:
This may not be relevant but i believe you also should have a

 Loadglx
That is okay.


 When I 'startx' I get a blank screen with a square cursor at the top left.

I'm not sure what is happening at this point.  When you get this screen,
can you switch to another console terminal?  If so, can you provide the
output of ps axf  /tmp/ps.log at the time?  It might help to so what
is running (or not) at the time.

I can switch to a virtual console.  Also, I've notice what I wrote about the
square cursor isn't 100% true.  When X starts I get a blank screen (no blinking
square cursor).  If I switch to a virtual console (e.g. F3-Ctrl-Alt) AND THEN
switch back (F7-Ctrl-Alt) I get the blank screen WITH the blinking square cursor.
I don't see any significance in that, but I thought I'd mention it 'cause someone
else might see something in that.

I did the ps  redirect.
$ ps axf  ~/ps.log # full log at end

A grep of that file for 'X11' ( $ grep X11 ps.log ) yields this result:
---
  244 ?S  0:00 /usr/bin/X11/xfs -daemon
  308 ?S  0:00 /usr/X11R6/bin/Xprt -ac -pn -nolisten tcp -audit 4 -fp 
/usr/X11R6/lib/X11/fonts/Type1,/usr/X11R6/lib/X11/fonts/100dpi,/usr/X11R6/lib/X11/fonts/75dpi,/usr/X11R6/lib/X11/fonts/misc
 :64
---

It is obvious things aren't running properly if one compares it to a 'ps'
when X is working the the open driver (nv):
---
$ ps axf |grep X11
  758 tty4 S  0:00  \_ /bin/sh /usr/bin/X11/startx
  769 tty4 S  0:00  \_ xinit /usr/X11R6/lib/X11/xinit/xinitrc -- 
/usr/X11R6/lib/X11/xinit/xserverrc
  770 ?S 0:10  \_ /usr/bin/X11/X -dpi 100 -nolisten tcp
---


I saw a few warnings in 'XFree86.0.log' file:

$ grep (WW) XFree86.0.log
---
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) The directory /usr/lib/X11/fonts/CID does not exist.
(WW) The directory /usr/lib/X11/fonts/cyrillic does not exist.
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
---
I don't know if they have any significance to the problems I'm having.



I beginning to wonder whether the 'XF86Config-4' has problems.  The way I
installed Debian Sid: (1) installed Woody (2) installed X (configured X)
(3) upgraded to Sid.

I installed Debian a couple of times... interesting is that if you install Woody
then upgrade and then install X the configure routinue (for X) that runs asks
you different questions.  I remember this 'cause when I did it this way I was
asked a few more questions and I wasn't sure how to answer some of 'em.  What
I ended-up doing is abandoning the second install (and doing it a third time
after wiping the partitions) 'cause I had no apparent X problems when installing
X in Woody before doing the upgrade to Sid.

(from an earlier post)
Do you have your kernel's header or source?
Kernel headers.  I'm not sure where to get the source... currently don't care either
if things can be taken care of with the headers.


To require nvidia-glx when you installed
nvidia-kernel-source would be incorrect as nvidia-glx is not needed by
the nvidia-kernel-source package.  However, when the resultant
nvidia-kernel binary package was created it should have required
nvidia-glx.
There is something I don't quite follow, because I tried the install with
the 'nvidia-kernel-source' package and it did NOT appear to have installed
the nvidia driver (nvidia-glx) properly (in a previous post I explained how
'lsmod' showed the 'nvidia' module as unused).

The way I fixed that is:
# apt-get install nvidia-glx

You're suggesting that is wrong?
(It seemed to be doing good things.  The 'nvidia' module was no longer listed
as 'unused.')


Anyway, I went on that hunch, 'cause I can't think of any other ideas.
I removed nvidia-glx (# dpkg -r nvidia-glx) and changed the 'XF86Config-4'
(so it would look for the 'nvidia' driver).  Then I dropped out of X
(with Ctrl-Alt-Bkspc) and *BOOM* my machine locks-up---no consoles... no
killing X... I had to three-finger-salute.  It doesn't seem like that
is progress.  I'm really close to fed-up.

This seems like a long shot:
Is it possible that because I didn't have 'nvidia-kernel-common' installed
when I built the dpkg (# debian/rules binary_modules) it screwed-up the
compile?  Does the order of the install matter?


process list
==
  PID TTY  STAT   TIME COMMAND
6 ?SW 0:15 [kupdated]
5 ?SW 0:00 [bdflush]
4 ?SW 0:00 [kswapd]
3 ?SWN0:01 [ksoftirqd_CPU0]
1 ?S  0:04 init [2]
2 ?SW 0:00 [keventd]
7 ?SW 0:00 [i2oevtd]
9 ?SW 0:00 [kreiserfsd]
   52 ?SW 0:00 [khubd]
   59 ?SW 0:00 [kapmd]
   84 ?SW 0:00 [kjournald]
   85 ?SW 0:00 [kjournald]
   86 ?SW 0:00 [kjournald]
  118 ?SW 0:00 [eth0]
  128 ?S  0:00 dhclient -pf /var/run/dhclient.eth0.pid eth0
  216 ?S  0:00

Re: NVIDIA driver (nvidia-kernel-source)

2003-08-16 Thread Michael Bonert

I'm still having some problems and I think it lies somewhere with the
module configuration.

Screen capture from 'startx':
---SNIP---
(==) Using config file: /etc/X11/XF86Config-4
Skipping
/usr/X11R6/lib/modules/extensions/libGLcore.a:debug_xform.o:  No
symbols found
Skipping /usr/X11R6/lib/modules/fonts/libspeedo.a:spencode.o:  No
symbols
found
(EE) Failed to load module nvidia (module does not exist, 0)
(EE) No drivers available.

Fatal server error:
no screens found

XIO:  fatal IO error 104 (Connection reset by peer) on X server :0.0
  after 0 requests (0 known processed) with 0 events remaining.
-


I can see a nvidia module in /lib/modules:
/lib/modules/2.4.18-bf2.4/kernel/drivers/video/nvidia.o

The module appears to load, but isn't used for some reason:
-
# lsmod
Module  Size  Used byTainted: P
nvidia   1628000   0  (unused)
emu10k155712   0  (autoclean)
sound  52844   0  (autoclean) [emu10k1]
ac97_codec  9568   0  (autoclean) [emu10k1]
soundcore   3204   7  (autoclean) [emu10k1 sound]
apm 9116   0  (unused)
keybdev 1664   0  (unused)
usbkbd  2848   0  (unused)
input   3040   0  [keybdev usbkbd]
usb-ohci   17472   0  (unused)
usbcore48000   0  [usbkbd usb-ohci]
-

I don't understand where I'm going wrong and I feel that I'm stuck. :(


Answering my own question from earlier:
 What is the difference between 'nvidia-kernel-source' and
 'nvidia-kernel-src'?
'nvidia-kernel-src' is older

I did my first bug report--related to was I wrote earlier. :)

==

-- System Information --
Software:
Debian Release: testing/unstable
Kernel: Linux 2.4.18-bf2.4 ([EMAIL PROTECTED]) (gcc version 2.95.4 20011002
 (Debian prerelease)) #1 Son Apr 14 09:53:28 CEST 2002

Hardware:
Athlon 2200 XP
ASUS A7N8X Motherboard
NVIDIA GeForce 4
512 MB RAM



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

NVIDIA driver (nvidia-kernel-source)

2003-08-14 Thread Michael Bonert

I followed the instructions on the 'nvidia-kernel-source 1.0.4496-2' page
(http://packages.debian.org/unstable/x11/nvidia-kernel-source.html).
It suggusts working through instructions in a file called 'README.Debian'
(full path '/usr/share/doc/nvidia-kernel-source/README.Debian')


PROBLEM:

I don't think the installation worked.
The video and sound is distorted -- it skips every few seconds (like an
old LP with a long and nasty scratch).

I know it isn't hardware (video  sound works great in another (GNU/Linux)
distro I have installed).


OBSERVATIONS/SUGGESTIONS:

This suggests kernel package is installed:
---
$ dpkg --list |grep kernel
ii  adjtimex   1.15.1-1   Utility to display or set the kernel time va
ii  kernel-headers 2.4.18-6   Headers for Linux kernel version 2.4.18 (bf
ii  nvidia-kernel- 1.0.4496-2 NVIDIA binary kernel module for Linux 2.4.18
ii  nvidia-kernel- 1.0.4496-1 NVIDIA binary kernel module common files
ii  nvidia-kernel- 1.0.4496-2 NVIDIA binary kernel module source
ii  pciutils   2.1.11-2   Linux PCI Utilities (for 2.[12345].x kernels
---

I was expecting the kernel to change... but it hasn't:
---
$ cat /proc/version
Linux version 2.4.18-bf2.4 ([EMAIL PROTECTED]) (gcc version 2.95.4 20011002
(Debian prerelease)) #1 Son Apr 14 09:53:28 CEST 2002
---
2.4.18-bf2.4 is the out-of-the-box kernel I installed.


'/usr/share/doc/nvidia-kernel-source/README.Debian' IHMO could be
improved.
---
Proposed changes in 'README.Debian':
1. Suggest compile/dpkg build directory
# mkdir /usr/src/local
-- do compile/dpkg build in: '/usr/src/local'

2. Fix directory
change ../modules/nvidia-kernel-1.0.4496 to
../modules/nvidia-kernel

3. Fix dependency to 'nvidia-kernel-common' (???)
I'm think it should download when you:
# apt-get install nvidia-kernel-source

When I ran dpkg to install the nvidia-kernel:
# dpkg -i nvidia-kernel-2.4.18-bf2.4_1.0.4496-2_i386.deb
I got this:
---
Selecting previously deselected package nvidia-kernel-2.4.18-bf2.4.
(Reading database ... 31054 files and directories currently installed.)
Unpacking nvidia-kernel-2.4.18-bf2.4 (from 
nvidia-kernel-2.4.18-bf2.4_1.0.4496-2_i386.deb) ...
dpkg: dependency problems prevent configuration of nvidia-kernel-2.4.18-bf2.4:
 nvidia-kernel-2.4.18-bf2.4 depends on nvidia-kernel-common (= 1.0.4496); 
however:
  Package nvidia-kernel-common is not installed.
dpkg: error processing nvidia-kernel-2.4.18-bf2.4 (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 nvidia-kernel-2.4.18-bf2.4
---

This was fixed after I did this:
# apt-get install nvidia-kernel-common


QUESTIONS:

Is there a detail HOWTO for this?
I found a HOWTO of Woody
(
http://www.madcow404.com/buyle/Nvidia_drivers_Debian_3_0.html#2.4._Edit_your_XF86Config-4_file_
),
but it doesn't seem to be very up-to-date.

Are changes in XF86Config-4 required? (I can't imagine there wouldn't be.)

I'm still uncertain about some of the basics...
Is the kernel supposed to change?  (I think so.)
What happens with my old kernel if the process works?  (Erased?)

What happens if I grab the executable (script) from NVIDIA and run it?
Is this going to make a mess of my system? (This is what I'd guess.)

What am I missing/doing wrong?

Why does something that seems so simple in another distribution
giving me such a headache?

What is the difference between 'nvidia-kernel-source' and 'nvidia-kernel-src'?


COMMENT:
I wish it was as simple as:
# apt-get install non-free-nvidia-driver
---


Thanks in advance for any help,
Michael


My System:
Athlon XP 2200
512 MB RAM
NVIDIA GeForce 4
Debian Sid / Mandrake 9.1



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

39 matches

Mail list logo