Shutdown was added after one of the betas. Reboot was never there.Eadwine Rose wrote:Oh yeah.. before I forget.. now I don't have the old ones anymore to test, but I seem to remember (just hit me with a fish when I am wrong) that after the system boots and you get to the login screen there was the opportunity to reboot from there, not just shut down.
Did that option go away or am I seeing ghosts?
RC2 feedback
Re: RC2 feedback
Forum Rules
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
- Eadwine Rose
- Administrator
- Posts: 14470
- Joined: Wed Jul 12, 2006 2:10 am
Re: RC2 feedback
Just something I seem to remember in the top of the login screen when I had a bad harddrive boot and wanted to reboot without logging in. Ah well hehe.
Thanks for clarifying
Thanks for clarifying

MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
- anticapitalista
- Developer
- Posts: 4282
- Joined: Sat Jul 15, 2006 10:40 am
Re: RC2 feedback
Actually, the original betas had both shutdown and reboot. It was decided to change the lightdm menu to include only shutdown.
anticapitalista
Reg. linux user #395339.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - lean and mean.
https://antixlinux.com
Reg. linux user #395339.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - lean and mean.
https://antixlinux.com
Re: RC2 feedback
Yes, now I remember it was a bar at the top, but never in the new lightdm box.
Forum Rules
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
- Eadwine Rose
- Administrator
- Posts: 14470
- Joined: Wed Jul 12, 2006 2:10 am
Re: RC2 feedback
Ahh .. too bad. Ah well, thanks for confirming I was not nuts (this time
)

MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Re: RC2 feedback
Running usb hp 1010 printer.No problemns with setup and use using mx-14 rc2.Thanks John
Re: RC2 feedback
IGNORE BELOW PROBLEM -- THIS WAS CAUSED BY USER ERROR DUE TO A LOOSE CABLE
STOCK R8169 MODULE WORKS FINE WITH THIS CHIPSET
Problem with MX-14 RC2 - No wired Ethernet for Realtek RTL8111/8168B, with no working driver in MX-14 RC2 (at least not running it live).
System: Dell XPS 8500 - Intel H77 chipset with Core i7 3770, 12GB DDR3, Nvidia GT 640
Ethernet Adapter section from lshw:
lspci network adapter section:
hwinfo network adpater section:
lsmod:
Here's an old article that may or may not be pertinent (on building a rtl8111/rtl8198 driver):
http://unixblogger.wordpress.com/2011/1 ... rnet-card/
There may already be modules built in repos somewhere (I don't know), but I don't see anything other than the r8169 module running MX-14 RC2 live from a USB stick, and the r8169 driver doesn't work with this adapter (and I've tried manually removing it and reloading it again with modprobe, reconfiguing it using ifconfig, etc. -- no dice, the r8169 driver doesn't work with it, unless the install is missing firmware needed by it or something similar. But, I get the impression from some articles that a different driver is needed for the rtl8111/rtl8198 (see link above), and then you'd need to blacklist r8169, too. But, that article is from 2011, so things may have changed by now.
BTW, my wireless does work. This machine came with an Atheros AR9485 Wireless Network Adapter (rev 01) installed; and it's detected just fine and using the ath9k driver in MX-14
But, I have no wired Ethernet in MX-14 RC2; and I suspect this Dell is using a fairly common ethernet chipset if it's in this model (and the XPS 8500 has now been replaced by a newer XPS 8700, so the XPS 8500 is not brand new or anything.
STOCK R8169 MODULE WORKS FINE WITH THIS CHIPSET
Problem with MX-14 RC2 - No wired Ethernet for Realtek RTL8111/8168B, with no working driver in MX-14 RC2 (at least not running it live).
System: Dell XPS 8500 - Intel H77 chipset with Core i7 3770, 12GB DDR3, Nvidia GT 640
Ethernet Adapter section from lshw:
Code: Select all
*-network
description: Ethernet interface
product: RTL8111/8168B PCI Express Gigabit Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:03:00.0
logical name: eth0
version: 07
serial: b8:ca:3a:77:4d:86
size: 10Mbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8168e-3_0.0.4 03/27/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s
resources: irq:44 ioport:d000(size=256) memory:f2104000-f2104fff memory:f2100000-f2103fff
Code: Select all
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 07)
Code: Select all
33: PCI 300.0: 0200 Ethernet controller
[Created at pci.318]
Unique ID: rBUF.a3fVRnbG_tF
Parent ID: Z7uZ.cTMhghLM911
SysFS ID: /devices/pci0000:00/0000:00:1c.3/0000:03:00.0
SysFS BusID: 0000:03:00.0
Hardware Class: network
Model: "Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller"
Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
Device: pci 0x8168 "RTL8111/8168B PCI Express Gigabit Ethernet controller"
SubVendor: pci 0x1028 "Dell"
SubDevice: pci 0x0545
Revision: 0x07
Driver: "r8169"
Driver Modules: "r8169"
Device File: eth0
I/O Ports: 0xd000-0xdfff (rw)
Memory Range: 0xf2104000-0xf2104fff (ro,non-prefetchable)
Memory Range: 0xf2100000-0xf2103fff (ro,non-prefetchable)
IRQ: 44 (no events)
HW Address: b8:ca:3a:77:4d:86
Link detected: no
Module Alias: "pci:v000010ECd00008168sv00001028sd00000545bc02sc00i00"
Driver Info #0:
Driver Status: r8169 is active
Driver Activation Cmd: "modprobe r8169"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #25 (PCI bridge)
Code: Select all
Module Size Used by
dm_mod 78611 0
joydev 16847 0
snd_hda_codec_hdmi 35226 2
wl 3942985 0
snd_hda_codec_realtek 40657 1
x86_pkg_temp_thermal 12853 0
snd_hda_intel 35030 1
lib80211 12829 1 wl
ath3k 12605 0
intel_powerclamp 12882 0
snd_hda_codec 130677 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
nouveau 816906 2
snd_hwdep 12910 1 snd_hda_codec
snd_pcm 69436 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc 12882 2 snd_pcm,snd_hda_intel
snd_seq 47432 0
snd_seq_device 12980 1 snd_seq
btusb 21248 0
snd_timer 22187 2 snd_pcm,snd_seq
iTCO_wdt 12727 0
arc4 12453 2
mxm_wmi 12467 1 nouveau
wmi 17147 2 mxm_wmi,nouveau
coretemp 12734 0
ttm 55496 1 nouveau
drm_kms_helper 35224 1 nouveau
drm 198116 4 ttm,drm_kms_helper,nouveau
iTCO_vendor_support 12585 1 iTCO_wdt
bluetooth 199360 3 ath3k,btusb
crc16 12327 1 bluetooth
kvm_intel 128872 0
i2c_algo_bit 12647 1 nouveau
ath9k 84848 0
kvm 321419 1 kvm_intel
ath9k_common 12615 1 ath9k
ath9k_hw 387369 2 ath9k_common,ath9k
snd 50842 11 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec,snd_hda_intel,snd_seq_device
crc32_pclmul 12809 0
psmouse 76603 0
ath 17153 3 ath9k_common,ath9k,ath9k_hw
i2c_i801 16843 0
crc32c_intel 12624 0
mac80211 406021 1 ath9k
soundcore 12890 1 snd
cfg80211 355997 4 wl,ath,ath9k,mac80211
rfkill 18380 3 cfg80211,bluetooth
lpc_ich 16616 0
pcspkr 12531 0
i2c_core 23342 5 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,nouveau
evdev 17172 5
serio_raw 12737 0
r8169 59053 0
mfd_core 12537 1 lpc_ich
aesni_intel 17934 1
aes_i586 16647 1 aesni_intel
xts 12583 1 aesni_intel
mii 12595 1 r8169
lrw 12686 1 aesni_intel
gf128mul 12834 2 lrw,xts
ablk_helper 12508 1 aesni_intel
cryptd 14125 1 ablk_helper
fan 12601 0
processor 27676 0
thermal 17268 0
dcdbas 13080 0
mei_me 13152 0
mei 44836 1 mei_me
video 17513 1 nouveau
button 12824 1 nouveau
thermal_sys 22845 6 fan,video,intel_powerclamp,thermal,processor,x86_pkg_temp_thermal
squashfs 30755 1
nls_utf8 12416 1
nls_cp437 12417 1
vfat 16967 1
fat 52607 1 vfat
hid_generic 12369 0
usbhid 39684 0
hid 76868 2 hid_generic,usbhid
pata_via 12722 0
udf 82501 0
crc_itu_t 12331 1 udf
sg 25573 0
pata_atiixp 12659 0
xhci_hcd 101977 0
wusbcore 35595 0
uwb 60163 1 wusbcore
fuse 72877 2
uhci_hcd 26253 0
ohci_pci 12704 0
ohci_hcd 25681 1 ohci_pci
ehci_pci 12432 0
ahci 25000 0
libahci 26693 1 ahci
ata_piix 29374 0
libata 153279 5 ahci,libahci,pata_via,pata_atiixp,ata_piix
sd_mod 43552 2
crct10dif_generic 12517 1
crc_t10dif 12399 1 sd_mod
crct10dif_common 12340 2 crct10dif_generic,crc_t10dif
sr_mod 21563 0
cdrom 38861 1 sr_mod
usb_storage 43272 1
scsi_mod 151166 5 sg,usb_storage,libata,sd_mod,sr_mod
aufs 162113 2769
isofs 38663 0
loop 21865 3
ehci_hcd 43617 1 ehci_pci
usbcore 133907 11 ath3k,btusb,uhci_hcd,usb_storage,wusbcore,ohci_hcd,ohci_pci,ehci_hcd,ehci_pci,usbhid,xhci_hcd
usb_common 12408 1 usbcore
http://unixblogger.wordpress.com/2011/1 ... rnet-card/
There may already be modules built in repos somewhere (I don't know), but I don't see anything other than the r8169 module running MX-14 RC2 live from a USB stick, and the r8169 driver doesn't work with this adapter (and I've tried manually removing it and reloading it again with modprobe, reconfiguing it using ifconfig, etc. -- no dice, the r8169 driver doesn't work with it, unless the install is missing firmware needed by it or something similar. But, I get the impression from some articles that a different driver is needed for the rtl8111/rtl8198 (see link above), and then you'd need to blacklist r8169, too. But, that article is from 2011, so things may have changed by now.
BTW, my wireless does work. This machine came with an Atheros AR9485 Wireless Network Adapter (rev 01) installed; and it's detected just fine and using the ath9k driver in MX-14
But, I have no wired Ethernet in MX-14 RC2; and I suspect this Dell is using a fairly common ethernet chipset if it's in this model (and the XPS 8500 has now been replaced by a newer XPS 8700, so the XPS 8500 is not brand new or anything.
Last edited by JimC on Mon Mar 17, 2014 8:27 am, edited 2 times in total.
Re: RC2 feedback
@JimC, I did a quick Google(Linux RTL8111/8168B) and saw lots of people had problems with this chipset. The solution seems to involve downloading a driver from the RealTek web site. IMO the big questions are: what is the license on that driver? Are we free to re-distribute it? Maybe there is a solution we can use in those search results.
Re: RC2 feedback
IGNORE PROBLEM -- THIS WAS USER ERROR DUE TO A LOOSE CABLE
STOCK R8169 MODULE WORKS FINE WITH THIS CHIPSET
BTW, the driver from Realtek also works using the installed R8168 module (either way works fine).
Well... I don't know about the licensing. But, that driver is not working with my chipset.
I went ahead and installed MX-14 RC2 to a hard drive for further testing.
I've got the old r8169 driver removed, and even blacklisted it and rebooted after building the new driver, The new driver built fine and loads. But, the my wired ethernet does not work with it for some reason. It appears that realtek firmware is already installed. But, perhaps there is a minor diffrence in my chipset's revision or something.
I tried the latest 8.038 driver from realtek, which built a module named r8168 module I'm loading. I got it from this download page:
http://www.realtek.com.tw/downloads/dow ... wn=false#2
But, no dice (isn't working).
Not a big deal to me, as my wireless is working with MX-14. But, others with the same wired ethernet chipset (in a Dell or similar machine) may have issues.
STOCK R8169 MODULE WORKS FINE WITH THIS CHIPSET
BTW, the driver from Realtek also works using the installed R8168 module (either way works fine).
Well... I don't know about the licensing. But, that driver is not working with my chipset.
I went ahead and installed MX-14 RC2 to a hard drive for further testing.
I've got the old r8169 driver removed, and even blacklisted it and rebooted after building the new driver, The new driver built fine and loads. But, the my wired ethernet does not work with it for some reason. It appears that realtek firmware is already installed. But, perhaps there is a minor diffrence in my chipset's revision or something.
I tried the latest 8.038 driver from realtek, which built a module named r8168 module I'm loading. I got it from this download page:
http://www.realtek.com.tw/downloads/dow ... wn=false#2
But, no dice (isn't working).
Not a big deal to me, as my wireless is working with MX-14. But, others with the same wired ethernet chipset (in a Dell or similar machine) may have issues.
Last edited by JimC on Mon Mar 17, 2014 8:29 am, edited 1 time in total.
Re: RC2 feedback
P.S.
Same thing in OpenSUSE Edu-Life 13.1 (more apps and more repos enabled compared to the standard OpenSUSE release)-- wired adapter not working, wireless is working.
I just finished installing it to another partition on my boot SSD (setup using btrfs so I can make snapshots as desired, so I can easily back out any changes if it gets messed up). I'm using YAST to install all updates to it now. Then, I'll play with the driver issue more as time permits.
Wired works in Windows 8. But, perhaps this chipset just doesn't like most Linux distros.
Same thing in OpenSUSE Edu-Life 13.1 (more apps and more repos enabled compared to the standard OpenSUSE release)-- wired adapter not working, wireless is working.
I just finished installing it to another partition on my boot SSD (setup using btrfs so I can make snapshots as desired, so I can easily back out any changes if it gets messed up). I'm using YAST to install all updates to it now. Then, I'll play with the driver issue more as time permits.
Wired works in Windows 8. But, perhaps this chipset just doesn't like most Linux distros.