Trying to dig the pony
Forum rules
We don't support installations in VirtualBox, VMWare, qemu or others. We ignore posts about WINE, PlayOnLinux, Steam and Skype. We don't support btrfs, lvm, UEFI, side-by-side installations with GPT or dualboot with anything newer than Windows XP.
Google your problem first. Check the Wiki. Read the existing threads. It's okay to "hijack" an existing thread, yes! If your problem is not yet covered, open a new thread. To get the quickest possible help, mention the exact release codename in your post (uname -a is a good idea, too). Due to the lack of crystal balls, attach the output of lspci -nnk if you encounter hardware problems.
We don't support installations in VirtualBox, VMWare, qemu or others. We ignore posts about WINE, PlayOnLinux, Steam and Skype. We don't support btrfs, lvm, UEFI, side-by-side installations with GPT or dualboot with anything newer than Windows XP.
Google your problem first. Check the Wiki. Read the existing threads. It's okay to "hijack" an existing thread, yes! If your problem is not yet covered, open a new thread. To get the quickest possible help, mention the exact release codename in your post (uname -a is a good idea, too). Due to the lack of crystal balls, attach the output of lspci -nnk if you encounter hardware problems.
- ivanovnegro
- Minister of Truth
- Posts: 5450
- Joined: Wed Oct 17, 2012 11:12 pm
Re: Trying to dig the pony
^ Thanks Sector, now I see it, ok, let's work on this. What is the kernel on your self titled Sid system?
- wuxmedia
- Grasshopper
- Posts: 6454
- Joined: Wed Oct 17, 2012 11:32 am
- Location: Back in Blighty
- Contact:
Re: Trying to dig the pony
oh - I didn't see it either...
Re: Trying to dig the pony
It's Debian SID actuallyivanovnegro wrote:^ Thanks Sector, now I see it, ok, let's work on this. What is the kernel on your self titled Sid system?
Code: Select all
30 Oct 13 | 21:07:28 ~
$ s11
System: Host: sector11 Kernel: 3.9-1-amd64 x86_64 (64 bit) Desktop: Openbox 3.5.2 Distro: Sector11 0.01 Sector11
Machine: Mobo: ECS model: MCP61M-M3 version: 7.0 Bios: American Megatrends version: 080015 date: 11/03/2010
CPU: Triple core AMD Athlon II X3 450 (-MCP-) cache: 1536 KB flags: (lm nx sse sse2 sse3 sse4a svm)
Clock Speeds: 1: 3214.368 MHz 2: 3214.368 MHz 3: 3214.368 MHz
Graphics: Card: NVIDIA GT218 [GeForce 210] X.Org: 1.14.3 driver: nvidia Resolution: [email protected]
GLX Renderer: N/A GLX Version: N/A
Audio: Card-1: NVIDIA MCP61 High Definition Audio driver: snd_hda_intel Sound: ALSA ver: k3.9-1-amd64
Card-2: NVIDIA High Definition Audio Controller driver: snd_hda_intel
Network: Card: NVIDIA MCP61 Ethernet driver: forcedeth
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 250.1GB (39.4% used) 1: id: /dev/sda model: WDC_WD2500AAJS size: 250.1GB
Partition: ID: / size: 15G used: 5.3G (38%) fs: ext4 ID: /home size: 15G used: 4.5G (33%) fs: ext4
Sensors: System Temperatures: cpu: 41.0C mobo: 35.0C gpu: 45C
Fan Speeds (in rpm): cpu: 2262 fan-2: 0 fan-3: 0
Info: Processes: 170 Uptime: 29 min Memory: 532.5/5987.7MB Client: Shell (bash) inxi: 1.9.16
30 Oct 13 | 21:09:07 ~
$
Ivan WM and all here - Thank you ...
I am THE resident noob, hands down no discussion. ... and
I wear my soap on a rope.
I wear my soap on a rope.
- wuxmedia
- Grasshopper
- Posts: 6454
- Joined: Wed Oct 17, 2012 11:32 am
- Location: Back in Blighty
- Contact:
Re: Trying to dig the pony
I couldn't find much either.
only solution (very old thread) was to remove power for 5 mins...
try
see if it comes up there.
only solution (very old thread) was to remove power for 5 mins...
try
Code: Select all
dmesg | grep eth0
- wuxmedia
- Grasshopper
- Posts: 6454
- Joined: Wed Oct 17, 2012 11:32 am
- Location: Back in Blighty
- Contact:
Re: Trying to dig the pony
then try
then try ceni.
Code: Select all
ifconfig eth0 up
Re: Trying to dig the pony
Off to bed --- will unplug modem over night and try that first thing in the AMwuxmedia wrote:then trythen try ceni.Code: Select all
ifconfig eth0 up
Thanks for everything today.
I am THE resident noob, hands down no discussion. ... and
I wear my soap on a rope.
I wear my soap on a rope.
Re: Trying to dig the pony
OK, I gotta go with the idea of the kernel and ethernet card not liking each other. Because the modem was off all night, and first thing I did was there. Ran ifcoinfig eth0 up no error .... ran ceni ... still no net. :(
Damn do I gave to stay with this 3-9-1-amd64 kernel forever?
Damn do I gave to stay with this 3-9-1-amd64 kernel forever?
I am THE resident noob, hands down no discussion. ... and
I wear my soap on a rope.
I wear my soap on a rope.
Re: Trying to dig the pony
Post output of
please. If it is too much for one post, limit it to todays output.
Perhaps there is something in there that can help you furher.
Code: Select all
sudo grep -Ei 'eth|wlan|net|dhc|wpa|firm' /var/log/syslog
Perhaps there is something in there that can help you furher.
Connected. Take this REPL, brother, and may it serve you well.
Re: Trying to dig the pony
OH OH!!! This is not good ... not that it's too much ...xaos52 wrote:Post output ofplease. If it is too much for one post, limit it to todays output.Code: Select all
sudo grep -Ei 'eth|wlan|net|dhc|wpa|firm' /var/log/syslog
Perhaps there is something in there that can help you furher.
Code: Select all
Thu Oct 31 13:08:39 ART 2013
└────╼ sudo grep -Ei 'eth|wlan|net|dhc|wpa|firm' /var/log/syslog>syslog.txt && leafpad syslog.txt
[sudo] password for sector11:
grep: /var/log/syslog: No such file or directory
[]─[13:09]─[~]
└────╼
Code: Select all
/var/log/ConsoleKit
/var/log/btmp
/var/log/dmesg
/var/log/dmesg.0
/var/log/dmesg.1.gz
/var/log/dmesg.2.gz
/var/log/dmesg.3.gz
/var/log/dmesg.4.gz
/var/log/dpkg.log
/var/log/gnustep-back-common.log
/var/log/lastlog
/var/log/wtmp
/var/log/Xorg.0.log
/var/log/Xorg.0.log.old
I didn't do am MD5SUM check (have to see if I can find it) but it installed so it has to be OK right?
I am THE resident noob, hands down no discussion. ... and
I wear my soap on a rope.
I wear my soap on a rope.
Re: Trying to dig the pony
I haven't got pony installed, but it seems like the syslog service is not started, or it is using the systemd syslog facility..
Try the command on dmesg:
Though there will be less info available than with syslog.
Try the command on dmesg:
Code: Select all
dmesg | grep -Ei 'eth|wlan|net|dhc|wpa|firm'
Connected. Take this REPL, brother, and may it serve you well.
- wuxmedia
- Grasshopper
- Posts: 6454
- Joined: Wed Oct 17, 2012 11:32 am
- Location: Back in Blighty
- Contact:
Re: Trying to dig the pony
FYI - 95% of bacon's spins use systemd.